The Import Process
Importing TRs into the target system
- After the request owner releases the Transport Requests from Source system, changes should appear in quality and production system; however this is not an automatic process.
- As soon as the export process completes (releasing of TRs), relevant files (Cofiles and Data files) are created in the common transport directory at OS level and the entry is made in the Import Buffer (OS View) / Import Queue (SAP App. View) of the QAS and PRD.
- Now to perform the import, we need to access the import queue and for that we need to execute transaction code STMS -> Import Button OR select Overview -> Imports
- It will show the list of systems in the current domain, description and number of requests available in Import Queue and the status.
Import Queue -> is the list of TRs available in the common directory and are ready to be imported in the target system, this is the SAP Application View, at the OS level it is also known as Import Buffer.
The Import status
Import Queue shows some standard 'status icons' in the last column, here are the icons with their meanings, as defined by SAP:
In case, a request is not added automatically in the import queue/buffer, even though the OS level files are present, then we can add such requests by the following method, however, we should know the name of intended TR:
We can also check the previous imports that happened in the system as follows:
Transport logs and return codes
- After the transport has been performed, system administrator must check whether it was performed properly or not, for that SAP has provided us with the following type of logs (SE01 -> GOTO -> Transport Logs) :
- Action Log – which displays actions that have taken place: exports, test import, import and so forth.
- Transport Logs – which keep a record of the transport log files.
- One of the important information provided by logs are the return codes:
- 0: The export was successful.
- 4: Warning was issued but all objects were transported successfully.
- 8: A warning was issued and at least one object could not be transported successfully.
- 12 or higher: A critical error had occurred, generally not caused by the objects in the request.