Advice on hardware, database, operating system, type of installation (physical or virtual)
USE OF THE SECURITY AUDIT LOG
EDI enables companies to exchange business data such as purchase orders or invoices electronically. This data exchange is known as Electronic Data Interchange (EDI). What steps are needed to exchange data between two systems? In this post, I'd like to show you how to configure your SAP system so that an order, after it has been released, is sent electronically to your supplier. Data exchange between two systems requires a valid RFC connection to the receiver system and a transactional RFC IDoc port.
Every SAP system architecture is as individual as the company itself. Full planning, including hardware sizing, is therefore essential. These services are included here:
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.
Especially in larger companies, which also have multiple locations in different countries, it is often necessary to grant different employees the same permissions for different levels of organisation, such as accounting circles. In order to make maintenance and maintenance of the system easy in such a situation, it is useful to set the inheritance principle for SAP permissions. How does SAP Permissions Inheritance work? An inheritance is always about a master object passing certain properties to a derived (sub) object. Therefore, these properties do not need to be maintained several times. Also, changes to the master object are passed directly to the derived objects. This allows easier maintenance and drastically minimises the error rate. In the case of SAP Permission Inheritance, the required permissions are bundled in a Upper or Master role. Only the organisational levels have to be maintained in the roles derived from them. The permissions are automatically pulled from the master role. Create Inheritance for SAP Permissions The following shows how to create and use inheritances for SAP permissions. This requires only two steps: Creating a master role and defining derived roles. Step 1: Create a master role Inheritance always requires a parent role, because all properties are inherited from it. If this role, in which all shared permissions are bundled, is missing, the first step is to create this master role. To do this, open the PFCG transaction and enter the desired name of the master role in the Name field. It is possible to identify master and derived roles by using naming conventions. The "Single Role" button will then be used to create the desired role. In the following example I create the master role "findepartment_r".
The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.
If you want to set the queue for another software component, select New Component.
In addition, users do not initially know the new technology well.