Troubleshooting and support
Update & Upgrade
Another important example is the reading permission for TemSe objects. The temporary files are often forgotten, because it is often not considered that cached (strictly) sensitive data, which is intended for only one user (owner), can be viewed by another user without permission - and across clients. The examples mentioned show us how important it is to carefully assign permissions for client-independent transactions. Download Transaction tables The transactions that enable the examples above, including certain expressions of the associated permission objects and our recommendations for them, can be found in the file "Critical cross-client permissions" for download. Other client-independent transactions are located in the Cross Clients TCODES file. The criticality of these transactions should be assessed according to the context. I recommend always being careful and keeping these transactions in mind.
The consistent implementation of the role concept enables a manageable complexity of the tasks per employee. At the same time, through the respective SMEs, the concept creates expertise in specific topics and enables communication on an equal footing with upstream or downstream IT departments as well as with external service providers. The establishment of technology architects also ensures that the overall picture is not left out of sight in the context of the SAP product portfolio. Deficits can also be addressed on issues such as policies and security. Overall, the role concept provides guidance for the employees and their career planning as well as guidance regarding the range of tasks and contacts for IT departments and business areas.
Migration
A first important step was the introduction of playbooks to professionalize our work. Back then, SAP installation manuals were real tomes with hundreds of pages that often went around in circles and were anything but easy to understand....
Some useful tips about SAP basis can be found on www.sap-corner.de.
In addition to the database, the SAP system itself is installed. This installation is planned using a tool from SAP, the "Maintenance Planner", and then carried out using the SWPM (Software Provisioning Manager) and SUM (Software Update Manager) tools.
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
The result also shows which transaction is included in which role.
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.
Note that starting with SPAM/SAINT version 11, you cannot delete the queue after the DDIC_IMPORT step and following.