/IWFND/MAINT_SERVICE Activate and manage services
Use of the Security Audit Log
The SAP NetWeaver Integration Technology part of the course covers the basic areas of use and properties of the various integration technologies. Interrelationships between the integration technologies, Web Services, ALE, BAPI, Process Integration, Web Application Server are taught. Further contents are the basic communication technologies: IDoc, RFC, http and SOAP.
Customers with such a case regularly contact us. Creating a Permission Concept from the ground up is often a time-consuming task. Furthermore, the know-how, which aspects should be dealt with in an authorisation concept and how the corresponding processes can look practical and at the same time audit-proof is often lacking. Our solution: tool-based generation of an individual, written authorisation concept In this situation, we have recommended to our customers the tool-based generation of a written authorisation concept directly from the SAP system. We use the XAMS Security Architect tool, with which we have had good experiences. This includes a template for a revision-proof and comprehensible, written authorisation concept. It includes established best practices for role and entitlement management. The template covers all relevant areas in a permission concept. The included text of the authorisation concept is completely customisable, so that the concept can be tailored to your situation without creating a permission concept from scratch. Dynamically update the written authorisation concept One of the biggest challenges after the development of an authorisation concept is to keep it up to date in the long term and to measure the sustainable implementation in the system. This is achieved by integrating live data such as configuration settings and defined rules directly from the connected system. For example, lists of existing roles or user groups and tables are read from the system each time the document is generated and updated in the permission concept. The following screenshot shows an example of what the appearance in the concept document might look like. Automatically check and monitor compliance with the concept To check compliance with the concept, the XAMS Security Architect includes extensive inspection tools. These cover the rules formulated in the concept and are suitable for measuring the extent to which the reality in the system meets the requirements formulated in the concept.
DBACOCKPIT DBA Cockpit: Maintaining the System Configuration
There are the following reasons that may lead to the termination of this step: CANNOT_SKIP_ATTRIBUTE_RECORD: The attributes cannot be read in the OCS file. The file probably cannot be opened for reading because it has been deleted in the meantime, or the permissions at the operating system level are insufficient. CANNOT_DETERMINE_EPS_PARCEL: The OCS file does not exist in the EPS inbox; presumably it was deleted.
The SAP Basis team takes care of the entire administration of an SAP system. As a company, you have to decide whether you want to leave the support of your system within your company or place the "Basis" in the hands of an SAP expert.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
User name without restrictions - critical? Depending on the release of the SAP_BASIS component in your system, invisible special characters may end up in the user name.
If you want to get more information about SAP basis, visit the website www.sap-corner.de.
This article discusses the permissions required to launch a Fiori application.