Use of the Security Audit Log
System copy
In the case of client settings, you should ensure that the production client is protected against overwriting and that changes are only approved via the transport management system (TMS) to ensure traceability. In the interests of system security, changes to repository and client-independent objects should also not be permitted. The use of eCATT and CATT should also be at least restricted, as allowing them can lead to significant database changes.
If you need to reinstall a Support Package because of errors or because a SPAM update is required, reset its status. Resetting does not mean that the system is at an old state. Note that your system is inconsistent when you reset the status after items have already been imported (for example, after the DDIC_IMPORT step and following). Resetting the status should only be used to troubleshoot the issue and you should repeat the playback as soon as possible. Procedure To reset the status of a Support Package or Queue, select Add Status Reset. Result After updating the status, the corresponding entries in the cofile and in the log file are deleted. The support package must then be fully reloaded. The transaction SPAM starts the insertion with the step CHECK_REQUIREMENTS [page 26].
How to create a parameter transaction for the SM30
Support Packages from SAPNet - Web Frontend or Collection CDs are available in a compressed format. Note that you must unpack the support packages before processing. Download the support packages from the SAPNet - Web Frontend or mount the appropriate CD. 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. You will see a list of uploaded support packages that are now known with all their attributes in the SAP system and can be handled in the right way by the SAP Patch Manager. Select Back to return to the SPAM entry screen.
On www.sap-corner.de you will also find useful information about SAP basis.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
QUEUE_STILL_IN_BUFFER: The queue is not fully processed because incomplete support packages of the queue are still in the transport buffer. CANNOT_RESET_FCS_FLAG: If there is an FCS Support Package (FFD) in the queue, the system will be marked as being at the generally available release level after this support package is inserted. In this case, this operation could not be performed successfully.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
The reasons are the same as for CANNOT_DISASSEMBLE_R_DATA_FILE.
Analysis: Our security experts analyse the data, evaluate the results and prepare your report.