Log in history of users using SAL
Best Practice SAP Basis Administration: Batch Control
You wanted to rush to release a transport order in the quality system of your SAP landscape and accidentally clicked on "Reject" instead of "Approve"? Now the order cannot be transported any further and will soon be cleared by job from the queue? Don't despair: In this blog post, I'm going to tell you a simple way to get rejected transportation to the production system anyway. As a reader of our blog, you are certainly interested in tricks and tricks that will make your SAP system easier to handle. You may be aware of the situation where you want to approve a transport order quickly after the test has been completed and you have clicked in the system when the order was released. The problem now is that the transport order in the system now has a status of "rejected" and can therefore no longer be transported. In total, a transport order may receive important changes that you would have liked to have transported to the production system. Approach to release rejected transport orders The screenshot below shows the situation in the STMS transaction where a transport order in the quality assurance area was rejected. Therefore, an import into the production system is no longer possible. The transport job can be removed either manually or through a job. The question here, however, is how the amendments which were wrongly rejected can be transferred to the subsequent system. Rejected Transport Order Tip: Leave the status on Rejected, remove the rejected transport order from the import queue, if necessary, and follow the next steps. Switch to the import queue in your quality system. Go there via Additions -> More Orders -> Attach to the modal window where you can perform further steps.
In the SAP product world, the presentation layer is based on several modules that are grouped under the collective term SAP GUI. SAP GUI for Windows, SAP GUI for Java, Web Dynpro for ABAP (WDA) and SAP GUI for HTML ("Web GUI") are widely used.
BD83 Reprocessing of faulty IDocs in outbound queue
To ensure audit-proof traceability, you should only allow software components and namespaces to be changed on a production system in exceptional cases and for a limited period of time. This should only be done restrictively to prevent manipulation at the production level.
Once you have met all the requirements described above, you can begin to prepare your system for processing digitally signed notes. To do this, the SAP Note with the number 2408073 must be recorded. This consists of a few steps for manual preparation, some automatically executable activities, and steps to rework the note. It is recommended not to change the file name after downloading. Note 2408073 has a file extension of "sar" and will first be unpacked with SAPCAR. There is a zip archive in it. The text file in it can be loaded into the Note Assistant with the SNOTE transaction via the Note upload. Once you have completed these steps, you can begin to install the note. The steps are detailed in the note itself and in a document attached to the note. Therefore, only a few points that need to be considered are highlighted below. When creating and clicking on Save the "CWBDS" object, a message may appear prompting you to select an object from the permitted namespace. Here the cursor can be placed in the object field and confirmed with Enter, then the query is made after a transport order. When creating the message texts in the "SCWN" message class, it is normal that after saving the changes several times (as many times as messages have been created) the question about the transport order must be confirmed. In addition, when creating the message texts, it should be noted that the texts provided in the tutorial attached to the note are available in English. If you are working on a German system, you should translate the texts into the German language when inserting them. The English texts can then be inserted as translations in the same window. To do this, select "Jump -> Translate". Conclusion It is a popular approach among hackers to use updates that are usually intended to fix bugs or increase security to inject malicious code into the system.
"Shortcut for SAP Systems" is a PC application that simplifies or even facilitates many activities in the SAP basis.
Tasks such as the update of components, the insertion of security updates or monitoring should be further automated.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
The following dialogue will open: The transaction code must be specified here first.