SLG0 / SLG1 Evaluate application log
Overview of used transactions
To influence the ABAP/Dynro generation, select Additions in the entry screen of the SPAM. Function Menu Path Turn Generation on or off Settings Ignore generation errors during the commit. Ignore error in SPAM steps If an error is detected in one step, the transaction SPAM stops processing until the error is resolved. You can always check with Status to see in which step and for what reason the abortion took place. Types of errors There are the following types of error messages: Security checks of the transaction SPAM A typical example is the OBJECTS_LOCKED_? step. The SPAM transaction interrupts processing when objects are still locked in jobs to be overwritten by the queue. Error messages of the programmes tp and R3trans The cause of error can always be found in the corresponding transport log. A typical example is the TEST_IMPORT step. This checks to see if there are unconfirmed repairs to objects overwritten by the queue. The affected objects are listed in the Testimport log. Incorrect setup of the Change and Transport System Common errors are the lack of appropriate rights to the files of the Change and Transport System or the use of old programme versions of tp or R3trans. Verify that the transport tools are working correctly with Transp Tool. Check Tool. A typical example is the DISASSEMBLE step. If adm does not have write permissions for the /usr/sap/trans/data (UNIX) directory, SPAM will cancel DISASSEMBLE with CANNOT_DISASSEMBLE_R_DATA_FILE. The transaction SPAM requires that the Change and Transport System [External] is set up correctly. For more information on known problems, see Notes 97630 and 97620.
In order for your SAP system landscape to function permanently, it requires error-free installation and regular support. You can rely on these services:
Knowledge or experience in SAP NetWeaver technologies (e.g. AS-Java, AS-ABAP, S/4HANA SAP PI, SAP BI, SAP Gateway or SAP folder management)
In the case of distributed or local SAP systems, it can also be helpful if departments or decentralized IT units can schedule their own jobs themselves. It is important that the associated approval processes can also be mapped and easily tracked. This brings convenience, flexibility and a degree of freedom without neglecting operational security. The integration of the business departments can relieve the IT administrator and turn background processing into an end-to-end process integrated into the organization.
If you now want to change the permission data, you will be asked for values for the appropriate organisation levels. First enter a tilde (~) and define the value later in the derived roles. Maintain the permissions you want and then generate the master role. Adding the organisational level to the master role Step 2: Define derived roles Create derived roles Assign the master role After you have created the master role, it is the derived roles that are in the process. To do this, re-enter a suitable role name via the PFCG. In our example, it is called "findepartment_d01". For a better overview, it is usually useful to name and number the derivatives after the master roles. You can also define the roles according to a different scheme. After you have created the role, you must then enter the master role in the Derive from Role field in the Description tab. Confirm the Auto Enquiries. Customise the Organisation Levels Now go to the "Menu" tab. There you can see that the data from the master role was automatically copied. Since the role has not yet been generated, the Permissions tab is currently highlighted in red. Therefore, call "Change Permissions Data". The first call should automatically open a dialogue to maintain the organisational levels, as they are still empty. If this is not the case, or if you would like to adjust the organisational levels again in a later case, you can also access them via the button Ordende (see screenshot). If everything worked well, you can now see that the permissions were also automatically taken from the master role. If you generate the role, the permission tab will also appear green. Congratulations, you have successfully created a derived role! Repeat step 2 with the additional derivatives to adjust the organisation levels accordingly.
"Shortcut for SAP Systems" is a PC application that simplifies or even facilitates many activities in the SAP basis.
Support Packages from SAPNet - Web Frontend or Collection CDs are available in a compressed format.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
It is of great importance to keep the knowledge of SAP Basis experts in the company transparent.