SAP Authorization Concept
Then contact us now!
The so-called SAP message server also belongs to the application layer. Only one instance of this server exists in the system. It mediates between the services and applications. In concrete terms, this means that the message server takes care of load balancing and determines, for example, on which application server a user logs on. Communication between application servers is also the domain of this message server.
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.
Decommissioning/uninstallation of SAP systems and their databases
The decision to outsource a task or service should be taken not only in terms of cost, but also by assessing the competitive differentiation and strategic importance. Characteristics for describing the costs are the specificity of the task and the embossing by unit cost degression, i.e. decreasing costs with increasing number of tasks or performance. Of strategic importance are, in particular, those tasks and services which are difficult to imitate by competing companies. Figure 4 compares the strategic importance and cost advantages in order to arrive at fundamentally valid statements regarding the usefulness of outsourcing for certain IT tasks and services. In addition to this, as already discussed by Recommendation [A2], it is then worthwhile to establish a catalogue of criteria for evaluating and looking in detail at certain characteristics of the application or services. An exemplary catalogue of criteria can be found in chapter 9.6 of the Master thesis. Figure 4: IT Outsourcing Decision Matrix THE DECISION TO OUTSOURCE A TASK OR PERFORMANCE SHOULD BE MADE NOT ONLY IN TERMS OF COSTS BUT ALSO BY ASSESSING COMPETITION DIFFERENTIATION AND STRATEGIC IMPORTANCE.
This option is useful if several transactions are to be checked simultaneously for their existing assignment to a particular user. This variant must first identify all roles that have already been assigned to the user. This is done in the transaction SE16N by entering the table AGR_USERS. In addition, the limit of the maximum hit number can be set in this image. The user concerned must now be entered here. Furthermore, the output should be limited to the roles only. After the query is executed, all the roles assigned to the previously entered user are displayed. These are now completely marked and copied. Then in the transaction SE16N a step back is taken and this time the table AGR_1251 is selected. Now all the roles that have been copied previously are inserted here. In addition, the object S_TCODE and the transactions to be searched for are filtered. Warning: When entering transaction codes, be sure to be case-sensitive! At this point, the output can also be limited to the roles and object values (in this case, the transactions). After the query is executed, the transactions entered will now show those that the user can already perform. In addition, the role assigned to the transaction is shown. In conclusion, the SUIM is only partially suitable for identifying certain transactions with user assignment. Although the search using the S_TCODE permission object also allows you to view multiple transactions. However, since the result is missing the assignment of transactions considered to roles, the SUIM transaction can only be usefully used to check a single transaction for its existing assignment to a particular user.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
At times, the user context may exceed the value of abap/heaplimit.
For the database, we use Cloud SQL.