Dear customer,
Some import steps are not linked directly to a transport request. For example "Activate inactive runtime objects", "ABAP Dictionary Distribution" and "Feedback after export or import".
For example, during the step "Activate inactive runtime objects", the inactive nametabs are activated and there is nowhere a link to the transport that imported the DDIC change, this phase is listed under "Import steps not specific to transport request".
So the title "Import steps not specific to transport request" means that the system does not know to which request the steps belong to. The fact that many steps are listed in the "Import steps not specific to transport request" section of a transport request does not mean that all of them belong to this request.
When any kind of import is performed on the system (transports, Support Packages) a mass activation, distribution, conversion and movenametabs can be carried out on the system. The contents of the transport may be imported successfully but you may have outstanding conversions or activations related to objects independent of the transpor request. Until these inconsistencies are completed you will continue to see logs written under "Import steps not specific to transport" of all future transports. That is why it is written again to the transport log.
Kind regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.