SM58 Transactional RFC
SUGR Maintain user groups
In every company with several SAP systems, there is a person responsible for the complete SAP Basis topics, usually there is even a separate department for this. This person ensures the trouble-free operation of the SAP systems. The person responsible also accompanies maintenance work or upgrades and intervenes in special situations, such as poor performance. Even for companies that hand over the operation of the SAP Basis to an external service provider, there are often still tasks from the environment of user and authorization management at this point.
This step prompts you to customise your modifications to Repository objects by calling the transaction SPAU. EPILOGUE In this step the insertion is completed. Among other things, it is checked that the queue has been fully processed. SPAM: Troubleshooting The SAP Patch Manager performs several steps during the recording. If errors occur, SPAM will interrupt the playback to ensure consistency of the recording. After fixing the error, you can resume playback. When you cancel, a dialogue box appears with the information on which step and why the editing failed. This dialogue box is also available when you select Jump Status and then Queue, Support Package or SPAM Update (View Support Package Status (page 29)). Depending on the processing step in which the error occurred, the dialogue box will provide you with additional specific assistance to correct the error. You may also need to reset the status of a Support Package [page 36]. If you are having problems downloading Support Packages from the SAPNet - R/3 frontend, please see Note 34376. If you are having problems working with SPAM, read the note 17381This note gives you an overview of known problems and their solutions. For a list of the most important information about Online Correction Support (OCS), see Note 97620, which is updated regularly. If you are unable to resolve your issue with the information provided or with the following information, then record a problem message in the SAPNet - R/3 frontend with the information from the error dialogue box and send it to the BC-UPG-OCS topic group. Note 97660 when capturing the problem message. See also: Generation Error [Page 30].
Preparation of the migration to the SAP HANA database
The application layer is the central component of the SAP R/3 system. This layer is therefore also referred to by SAP as the actual base system. Within the layer there are application servers and a message server.
A partner agreement must be entered into for each supplier in the transaction WE20. Such an agreement shall determine how the electronic data are processed. Select the vendor partner type LI and create a new partner agreement. In this example, a new partner agreement is created for IDES AG as a supplier. Enter the vendor's partner number in the appropriate input field and select LI as the vendor's partner type. The next step is to define the output parameters. These specify how the outgoing data should be processed. The message type defines what kind of messages should be processed. The Output Options tab specifies the port to send the message to and the IDoc type. The IDoc base type ORDERS05 matches the ORDERS message. The Message Control tab defines which application should generate a message. In this case a message should be generated when a new order is created. If an order is placed for a product of IDES AG in the transaction ME21N, this order will be automatically sent in electronic form.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
Now all the roles that have been copied previously are inserted here.
With respect to the SAP basis, this step is concerned with product portfolio analysis and the creation of IT products and a product catalogue.