SAP Basis A high sense of responsibility - SAP Basis

Direkt zum Seiteninhalt
A high sense of responsibility
Quick check of your SAP security settings with the Xiting Authorizations Management Suite (XAMS)
Ten years ago, there wasn't much more for SAP Basis experts than SAP Solution Manager. And most Basis administrators only used it at all because SAP virtually forced them to use SolMan to download updates.

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_?
Client management
Among other things, it determines which application server a user logs on to in order to distribute the workload (load balancing). The message server also enables the individual application servers to communicate with each other.

The SAP Basis Plug-In is backward compatible and follows the release and maintenance strategy of the SAP R/3 Plug-In. SAP delivers it together with the SAP R/3 Plug-In. For more information, see SAP Service Marketplace at basis-plug-in → SAP Plug-In → SAP Basis Plug-In → Releases.

For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.

In this case, the workprocess goes into PRIV mode.

This person ensures the trouble-free operation of the SAP system.
SAP BASIS
Zurück zum Seiteninhalt