Planning of SAP environments
SM58 Transactional RFC
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.
Depending on whether the user should edit or display the table, either "UPDATE" or "SHOW" can be used here. Enter an X as the value. It is important to use either"'SHOW" or "UPDATE" because a combination will cause an error when calling the parameter transaction. In addition, the table must set the view to be called. Use the "VIEW" field. Finally, the parameter transaction can be created using the "Save" button. As usual, it must be assigned to a package and a workbench order to become available. If a person's role is now assigned permission for this parameter transaction, it can open the specified view above it and does not have the ability to enter all possible views in the SM30.
CMC Tabs Advantage
I recommend that you schedule the background job PFCG_TIME_DEPENDENCY with the report RHAUTUPD_NEW. Scheduling the RHAUTUPD_NEW report with two variants has proven to be a best practice: Once a day before users log on for the first time (e.g. midnight or very early in the morning). This way the users are synchronized once a day. Once a month (or even once a week) with the option "Perform cleanup", so that obsolete profiles and user mappings are regularly cleaned up. Also handy: If the naming conventions of your roles allow it, you can also align the report according to different time zones. For example, I have a customer who runs the user synchronization for his users in the USA and Asia at different times, so that the daily business of the respective users is not disturbed.
The dataowner should be the adm of the target system, which you can change (in the Unix console) with "chown adm K12345.DEV" (respectively R12345.DEV for the data file). To change the access permissions, you can use the command "chmod 664 K12345.DEV". Attach transport jobs in the SAP system Once this has been done, you can attach the transport orders in your SAP system to the import queue. This is done by using the STMS -> Import Overview (F5) to display the import queues. Select the import queue of the target system with a double click. After that, you will receive a pop-up under "Additions"->"More orders"->"Attach", which you can use to attach the transport orders to the import queue. In the pop-up you have to name the exact transport order. The correct name for this is as follows: The first three characters are the file extension of the two files you copied into the transport directory. The last characters consist of the file name of the cofiles file. In our example transport the transport would be called "DEVK12345" (deriving from the cofiles file K12345.DEV) This should now return a positive message from SAP and the transport is attached to the import queue. Now you can import this transport into the system just like any ordinary transport order. Step-by-step Summary Copy Cofiles/data file to transport directory Normally /usr/sap/trans, if not —> AL11 -> DIR_TRANS Customise file owners and permissions chown adm chmod 664 In SAP system: STMS -> Import Overview -> Select Import Queue -> Additions -> Additional Jobs -> Attach Enter Transport Jobs ().
The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.
IMPORT_PROPER In this step, all repository objects and table entries are fed.
The trend towards internationalization, outsourcing and mixed operation with on-premise and on-demand systems means that SAP landscapes are often widely distributed.