Preparation of migration to SAP HANA
Why does your company need an SAP Basis admin?
If you want to skip the backgrounds and prefer a direct step-by-step guide, you can jump directly into the last section. Preparation For this workaround, you need access to both the source system and the BW system. In addition, they shall have the possibility to access the SE37 and execute functional modules there. Especially in production systems this is a very critical justification. So assume that you may need a Firefighter user for this action. Working in the BW system Now that the preparations have been completed, you have to call a FuBa on the BW system and on the source system, which solves the connection on the respective page. Beginning on the BW system, go into the transaction SE37 and call the function block "RSAR_LOGICAL_SYSTEM_DELETE": RSAR_LOGICAL_SYSTEM_DELETE Enter the required values here. The following table helps you fill in: Field Description I_LOGSYS The logical name of the source system. The name of the source system, as found in RSA1, will be entered here. In addition, this name can also be found in the DB table TBDLT. I_FORCE_DELETE Boolean, X = Delete despite error messages I_NO_TRANSPORT Boolean, X = This change should not be transported to subsequent systems I_NO_AUTHORITY Boolean, X = Ignore Permission Checks Work in the source system In the source system, go to transaction SE37 and call the function block "RSAP_BIW_DISCONNECT" : The descriptions of the fields are as follows. These can be found in the RSBASIDOC source system connection table Field Description I_BIW_LOGSYS The logical name of the BW system. In the RSBASIDOC table, find the correct value in the column "RLOGSYS". I_OLTP_LOGSYS The logical name of the source system. The column ‘SLOGSYS’ in the table RSBASIDOC. I_FORCE_DELETE The logical name of the BW system. In the RSBASIDOC table, find the correct value in the column "RLOGSYS". Completion In the end, you have to call the respective function block in the BW and source system, fill in the parameters and execute the function block.
This point may sound a little trivial at first. Who tests, surely documents this? Experience shows: Yes, but often patchy. In the case of unsuccessful tests, where subsequent or additional developments are due and the cause of the error is not directly apparent at first glance, good result documentation often pays off. This saves developers time in communication and effort by re-imagining the scenario. At this point, the SAP Solution Manager offers extensive opportunities to manage templates and result documents centrally and in the individual test plans. Automated testing only Automated testing offers many advantages, whether it is a higher software quality through more comprehensive test coverage or reusability of test cases. However, it does not always make sense to use only automated test scripts. A less good choice is the test automation for frequently changing software or processes, because the maintenance effort can be enormous. At this point, it is often more effective to run manual test runs instead of spending a lot of time customising test scripts. Poor test preparation The relevant processes have been defined, the test plans have been created and the test period has begun - so can testing begin? Not always. Lack of test preparation often leads to unplanned additional time costs. Sometimes the testers were not familiar with the test environment or no one thought about taking care of a sufficient and current test data set (master data, movement data). Make sure you have thought of everything you need! (missing test data, unrepresentative test environment, unstable).
Archiving and DART
If you look at everything I've described up front in its entirety, it quickly becomes clear which direction things are headed: the SAP basis will increasingly move toward an SRE-centric environment over the next decade. This is what the future of SAP looks like, and I look forward to an exciting journey.
SAP Basis is structured as a classic three-tier model. It contains the following components:
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
The optimization of time-critical processes guarantees a smooth process.
Once you have performed these steps, the treated role has the necessary permissions on the front-end side.