SAP Basis This definition was last updated in June 2014 - SAP Admin

Direkt zum Seiteninhalt
This definition was last updated in June 2014
Call SPAM
Basis is a set of programs and tools that interface with databases, operating systems, communication protocols, and business applications (such as FI, CO, MM, etc). The full form of BASIS is "Business Application Software Integrated Solution".

The application layer is the core of an R/3 SAP Basis system. This layer communicates in both directions, to the presentation layer and to the database layer. The application programs on the application servers request the required data from the database layer, process it, prepare it for the user and pass it on to the presentation layer. Data that the user enters in the SAP GUI is passed on to the database via the application servers.

SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis: www.sap-corner.de.
STAUTHTRACE System trace for authorization checks
SAP Basis is also known as module BC or application Basis. SAP Basis refers to all transactions, programs and objects that control the functions of the overall system. This includes, among other things, user and authorization management as well as the configuration of interfaces via RFC.

Automation of processes In an IDM, IT business processes, creating, modifying and deleting a user are defined centrally by means of a unique set of rules. All the necessary steps are then completed using automated workflows. User administration no longer has to be administered separately for each system, but only in a single point of administration. Data Consistency Employee data is created only once in a leading system in an IDM architecture. All attached systems use this data in their user management on demand. In a change of department or a new activity, permissions are automatically adjusted. Security and Documentation In a centralised user administration, users can be locked down efficiently on all systems or access rights can be changed. The connection to the personnel process automatically initiates the change process as soon as the master record is adjusted in the Human Resources Department. Documentation solutions can also be used to archive all processes without any gaps. This creates transparency which also facilitates the detection of a functioning and secure authorisation concept during audit tests. Requirements for IDM systems People get electronic identity attributes describe the role of the person Quality requirements Reliability: Abuse prevention Readability: Documentation and logging Failover: Back-up systems in compliance with legal requirements Data Protection Act What should be taken into account in application processes? When implementing an IDM and also in the day-to-day operation of an IDM, there are certain things that should be taken into account when applying. I have summarised the most important points in the form of a checklist.

"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.

Improved performance reduces runtime and hardware utilization.

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.


The rest will be awarded automatically.
Zurück zum Seiteninhalt