Version upgrades
Fiori Permissions for tile groups in PFCG
The following list explains the steps in the order they are performed by SPAM: PROLOGUE This step will check if you are eligible to play Support Packages. CHECK_REQUIREMENTS In this step, different requirements for inserting are checked, e.g. the login of the transport control programme tp to your system. DISASSEMBLE In this step, the data files are unpacked from the corresponding EPS packages and placed in the transport directory. ADD_TO_BUFFER In this step, the queue is placed in the transport buffer of your system. TEST_IMPORT This step checks whether there are any objects that are overridden during the commit and are in unreleased tasks. IMPORT_OBJECT_LIST In this step, the object lists for the support packages that are in the queue are fed into the system. OBJECTS_LOCKED_? This step checks to see if there are any objects that are overwritten during the commit and that are in unreleased jobs. SCHEDULE_RDDIMPDP In this step the transport daemon (programme RDDIMPDP) is planned. ADDON_CONFLICTS_? This step checks to see if there are conflicts between objects in the queue and add-ons installed. SPDD_SPAU_CHECK This step will check if a modification match (transactions SPDD/SPAU) is necessary. DDIC_IMPORT In this step, all ABAP Dictionary objects of the queue are imported. AUTO_MOD_SPDD This step checks whether modifications to ABAP Dictionary objects can be adjusted automatically. RUN_SPDD_? This step prompts you to customise your modifications to ABAP Dictionary objects by calling the transaction SPDD. IMPORT_PROPER In this step, all repository objects and table entries are fed. Then actions such as distribution, implementation, activation and generation take place. AUTO_MOD_SPAU This step checks whether modifications can be adjusted automatically. RUN_SPAU_?
Due to the technology diversity, including in the SAP product portfolio, the support by a single silo unit SAP basis is almost impossible. Likewise, there are many activities that are located for historical reasons in the SAP basis and in parallel in the non-SAP area. In this respect, the separation between SAP and Non-SAP must be examined and, if possible, eliminated by standardisation, integration and centralisation. For example, the issue of output management can be set up in a team that has knowledge in the SAP printing area as well as in the non-SAP printing area and has contact points in the SAP basis. From the SAP basis, tools must be made available to the non-SAP areas to support them in their work in the SAP environment.
Extension of the SAP system landscape
Constant further development and growing complexity are placing ever-increasing demands on the SAP infrastructure in terms of performance and feasibility. In addition, SAP Basis is the technological driving force for the implementation of new applications and innovations in your business environment.
On www.sap-corner.de you will also find useful information about SAP basis.
The freeware Scribble Papers puts an end to the confusing paper chaos. The tool is also suitable for storing, structuring and quickly finding text documents and text snippets of all kinds in addition to notes.
This saves us a lot of time and ensures that no checks are overlooked when performing manually. Security Automation via HR Permissions HR permissions are a very risky topic in many companies and are often only touched with silk gloves.
For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.
All topics are relevant, which may also be of interest to a customer.
This creates transparency which also facilitates the detection of a functioning and secure authorisation concept during audit tests.