SWE2 Event type linkage
SPAM permissions
The implementation of a cross-sectional function will promote and safeguard the operation of the SAP systems that form the backbone of the company. By coordinating the SAP basis with other IT departments, the optimisation is always done in the overall context of the company or the IT organisation. Eliminating the separation of SAP and non-SAP topics in areas where it is considered useful will lead to expert groups and synergy effects through centralisation.
The CodeProfiler prevents poor-quality code or programs with security vulnerabilities from entering a productive SAP system landscape in the first place. It is therefore important to use the CodeProfiler throughout the entire lifecycle of a software. Already during programming, the CodeProfiler helps the developer to identify and correct errors and vulnerabilities in the SAP landscape. The CodeProfiler automatically ensures that only "clean" code is transported to the next level (development system -> test system -> quality assurance system -> production system). The CodeProfiler can also be used for regular review cycles.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
SM14 Update administration
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.
To configure the SAL, please use transaction RSAU_CONFIG (formerly SM19) as of SAP Release 7.50. It is recommended to activate the cross-user logging with minimum settings and to record all audit classes for users with extensive authorizations, such as SAP standard and emergency users. These settings should always be configured on a cross-client basis.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
This also ensures full audit and operational security (compliance).
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
The transaction SM51 will then be called.