Planning
SP02 Output control: Overview of spool requests
When I began my career administering SAP ERP on Oracle in the early 1990s, running a database required far more knowledge. An Oracle administration expert with a decade of experience understood perhaps only about 5% of what the database required.
A BW system often plays a very central role in larger companies. Here the data from the various connected source systems are analysed and reported centrally. A previous customer of mine had a BW system, to which a total of over 20 other SAPP production systems were connected. With such a large and mostly living system landscape, it is normal that individual systems are dismantled from time to time. However, especially with large SAP landscapes, there are strict regulations regarding the permissions of technical RFC users. For this reason, the simple "right-click —> delete" of a source system in RSA1 will often not lead to the target, but rather to a failed permission check. With this blog post, I'll show you a workaround on how to clean a source system from a BW system using the RSAR_LOGICAL_SYSTEM_DELETE and RSAP_BIW_DISCONNECT function blocks.
Error analysis and correction in the databases and the SAP system
The positioning depends strongly on the previously identified target groups and must be justified accordingly. Positioning is extremely important for the SAP basis. It is primarily a matter of positioning within the IT organisation and defining or positioning the other IT departments that can be considered as competitors in the context of this step. STEP 6: OWN EMPLOYEES This step will identify the necessary skills and training of their own employees necessary to fulfil the objectives and provide the service. The necessary skills and roles for the SAP basis are explained in detail in the recommendation Skills & Roles.
There are the following reasons that may lead to the termination of this step: CANNOT_GET_OBJECT_LIST: The Object List for a Support Package could not be found because the Support Package does not exist. CANNOT_CHECK_LOCKS: An error occurred while detecting the locks of an object in the queue. OBJECTS_LOCKED_IN_REQUESTS: Objects found in unreleased jobs. Release these jobs before you resume playing. SCHEDULE_RDDIMPDP In this step the transport daemon (programme RDDIMPDP) is planned. There are the following reasons that may lead to the termination of this step: CANNOT_SCHEDULE_RDDIMPDP: The RDDIMPDP job could not be scheduled. Enter the transaction SM37 (job selection), enter the following parameters, and select Next: Job Name RDDIMPDP Username Start by Event SAP_TRIGGER_RDDIMPDP Select the job that was cancelled and view the job log.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
An SAP landscape is made up of numerous individual modules that are fully compatible with each other and can be used to map the business processes of all areas of a company.
One possible consequence would be, for example, the registration of an external system on which malicious programmes exist.