SAP Basis Backing up and restoring data

Direkt zum Seiteninhalt
Backing up and restoring data
The Basis system comprises a total of three layers (Figure 1):
In the following dialogue, select a TADIR service and the programme ID "R3TR" and the object type "IWSG". Now you can select the OData service stored on the front-end gateway. Then switch to the Permissions tab to generate the current profile of the permission objects with the new Fiori permission. Once you have performed these steps, the treated role has the necessary permissions on the front-end side. Fiori Permission to call the OData service on the backend server Now go to the role maintenance in the PFCG on the backend server. Open the appropriate role in Change Mode. Now you can repeat the steps for the frontend as explained above. However, when selecting the TADIR service as the permission proposal, you now select the object type "IWSV". Here you can select the OData service of the specific Fiori application stored in the backend.

This is a general list. There are many other tasks that a basic consultant has to deal with. Every day you learn something new!

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.
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 addition, the SAP Basis team can easily implement new functionality in the new system - without compromising the security, stability or quality of the previous function, which would be the case with non-certified and inexperienced people. Smooth implementation is enabled by project experience, training and certificates.

"Shortcut for SAP Systems" is a PC application that simplifies or even facilitates many activities in the SAP basis.

Now you can select the OData service stored on the front-end gateway.

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.


Short and painless.
Zurück zum Seiteninhalt