SAP Basis SPAD Spool administration

Direkt zum Seiteninhalt
SPAD Spool administration
SWDM Business Workflow Explorer
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.

Reduce resources: depending on the agreement of the contract, you can ask for the service resources only when needed. This will save you some costs.
Defined service level agreements (SLAs)
The SAP NetWeaver Application Server Add-on for Code Vulnerability Analysis tool, also known as Code Vulnearability Analyzer (CVA), is a tool that performs a static analysis of user-defined ABAP source code to detect possible security risks. The tool is available in the NetWeaver ABAP stack and is based on versions from: 7.0 NetWeaver: in EHP2 SP 14 or higher / 7.0 NetWeaver: in EHP3 SP 09 or higher / 7.3 NetWeaver: in EHP1 SP 09 or higher / 7.4 NetWeaver: in SP05 or higher To use the CVA tool, the execution of system-wide security controls must be enabled with the RSLIN_SEC_LICENSE_SETUP report. Afterwards, the security checks are available in standard ABAP code checking tools such as ABAP Test Cockpit (ATC) or Code Inspector (SCI). The option of these checks is usually referred to as "security analysis in extended program check". Note that the use of the security check feature for custom code separation is licensed and incurs additional costs. The older program that has been around for years is Virtual Forge's "Code Profiler". It is one of the first products in this segment of SAP security and was used by SAP itself for many years. It is very comprehensive and is also able to track individual variables across the entire control flow. This leads to very precise statements and a reduction of false positives.

To view the software components installed in your SAP system with their respective package levels, select Status Package Levels. A dialogue box appears listing the installed software components with additional information. For more information on this dialogue, please refer to the Online Manual. SPAM: ABAP/Dynpro Generation Usage For performance reasons, the SPAM is set by default to prevent ABAP/Dynpro generation from occurring during the commit. The corresponding programmes are not generated until they are called. However, you can set the SPAM so that the generation takes place during the recording. It is quite possible that the SPAM will report errors during generation because, for example, a self-written or modified report is syntactically wrong and refers to an object that is being played over the cue. Often it is desirable to ignore the generation errors for the time being and to fix them after inserting them. Prerequisites to play Support Packages.

Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.

The website www.sap-corner.de offers many useful information about SAP basis.

Log in with the following user: Operating system users UNIX adm AS/400 OFR Windows NT adm Go to the following subdirectory in your system: Operating system UNIX and AS/400 usr/sap/trans/tmp Windows NT :\usr\sap\TRANS\TMP Unzip the archive containing the support packages with the following command: Operating system command UNIX CAR -xvf ///_CAR AS/400 CAR '-xvf /QOPT///_CAR' Windows NT CAR -xvf :\\ CHIVE>.CAR Put the unpacked support packages in the EPS inbox of your transport directory: Operating system EPS-Inbox of the transport directory UNIX /usr/sap/trans/EPS/in AS/400 /usr/sap/trans/EPS/in Windows NT :\usr\sap\trans\EPS\in Now bring the support packages into your system with Support Package Upload.

To influence the ABAP/Dynro generation, select Additions in the entry screen of the SPAM.
SAP Corner
Zurück zum Seiteninhalt