SAP Basis Administrative tasks - SAP Basis

Direkt zum Seiteninhalt
Administrative tasks
USE OF SECURE NETWORK COMMUNICATION
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.

SAP Basis Administrators ensure smooth operation of your SAP landscape. Our administrators take care of the databases, operating systems and your applications.
SWDM Business Workflow Explorer
SAP Basis consulting can start with general consulting on SAP deployment and installation and configuration. In addition, the SAP consulting can transition to an external takeover of updates and upgrades of SAP components or even the complete takeover of the administration of the SAP system.

Understanding the structure and functioning of the system is especially important for IT administration. It is not for nothing that "SAP Basis Administrator" is a separate professional field. On the page www.sap-corner.de you will find useful information on this topic.

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.

Strategically, completely self-hosted SAP systems are becoming rarer and the proportion of customers using an SAP system from the cloud is increasing.

The time period for which users can request an emergency user should be limited.

So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
SAP BASIS
Zurück zum Seiteninhalt