Migration from a change of operating system, homogeneous/heterogeneous database
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)
Have you ever wondered what there is actually a tab personalisation for role maintenance in the PFCG or for user data maintenance in the SU01? I will answer this question for you in this blog post. What do we need the Personalisation tab for? This tab gives you access to the central repository for personalisation data. The purpose of this repository is to create a storage facility for user- and role-specific data without the need to create additional database tables. This data should then be taken into account in all manipulations of users and roles. The functionality initially includes a generic repository for user- and role-specific data and centralised access to that data by user and role maintenance. It also provides the ability to connect existing tables with user-specific data to the central access via a defined interface. To store personalisation data in the central repository, a key must be assigned to the data: This is done via the registration transaction PERSREG. The personalisation data that you create is stored in the generic drop table. Access to it is provided by the class methods of the CL_PERS_ADMIN class. Different levels of personalisation The data can be stored either to the user, to roles or to the system. A user can then read all data assigned to him (via role or his own settings) at once.
You can view them using the RSPUTPRT report or the AL11 transaction. AUTO_MOD_SPAU This step checks whether modifications can be adjusted automatically. RUN_SPAU_? This step prompts you to customise your modifications to Repository objects by calling the transaction SPAU. EPILOGUE In this step the insertion is completed. Checks whether the queue is fully processed. In this case, transport buffer entries should no longer exist for the Queue. There are the following reasons that may lead to the termination of this step: TP_INTERFACE_FAILURE: Unable to call tp interface. TP_FAILURE: The tp programme could not be run. For more information, see the SLOG or ALOG log file.
Resource management such as memory, buffers, etc
In the authorization environment, in addition to assigning authorizations to SAP users, there are a number of important SAP Basis settings that you should check regularly to ensure that your SAP system is fully protected, both internally and externally. For example, particularly in the context of an audit, it is important to ensure that changes to the SAP system always remain traceable. In this blog, I would like to show you how you can best implement this and what to look out for.
Some useful tips about SAP basis can be found on www.sap-corner.de.
By using a code scanner, it is now possible for every developer to scan for complex security patterns during the extended check of his program, which tell him whether he has built vulnerabilities into his program. These vulnerabilities are detected and can now be addressed in a workflow-driven process. Currently, there are two products that can support customers in the area of scanning their own SAP programs.
Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.
Within the framework of an innovation team or test laboratory to be created, it is necessary to admit ideas outside of the SAP basis or to consciously use other sources of ideas within and outside the company.
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.
Associating the SPAM steps with log files Step Log file DISASSEMBLE_PATCH Generate Cofile TEST_IMPORT Testimport IMPORT_OBJECT_LIST Commandfile Import DDIC-IMPORT DD-Import IMPORT_PROPER DD-Activation Import ADO-Import Verification Versions Method Execution ABAP/Dynpro Generation Procedure To get to the log display, select Image Jump Log Queue.