ST06 Operating System Monitor
Migration from a change of operating system, homogeneous/heterogeneous database
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.
When I began my career administering SAP ERP on Oracle in the early 1990s, running a database required far more knowledge. An Oracle administration expert with a decade of experience understood perhaps only about 5% of what the database required.
Implementing applications
In addition to internal security requirements, national and international guidelines sometimes require all audit and security-related user actions to be recorded. With the Security Audit Log (SAL) you have the possibility to log all changes, e.g. for users, user master records, but also roles and groups.
Will Blockchain's Economy and Administration Revolutionise? What is a blockchain? A blockchain is a complete and unchanging transaction history of all transactions of a decentralised community that everyone who is part of it agrees to. The word blockchain first fell in connection with Bitcoin as a decentralised network for payments in the digital currency of the same name. The blockchain describes an underlying technology in which all transactions are publicly and unchangeably recorded. This transaction history is updated periodically. Each participant in the decentralised community accepts it as a reality, stores it on their computer, and can thus ensure at any time that no one can duplicate expenditure, as this would lead to a conflict in the transaction history elsewhere. A peculiarity of blockchain technology is that it has solved the "Double Spending Problem". Double-spending means something that can be doubled, and by 2008, only one central institution was considered to be sustainable. Double Spending can best be understood using the example of an image on a mobile phone. When I upload it to Facebook, I made a copy of it and I can upload it to Instagram, for example. So I used my picture "double". This effect made it impossible to establish a trustworthy, decentralised digital currency by 2008.
The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.
Some useful tips about SAP basis can be found on www.sap-corner.de.
A degree in computer science is usually a prerequisite and is now almost compulsory.
If you want to know what steps are being performed for which scenario, run RSSPAM10.