When you transport an object in a request, the object’s transport attributes must match the transport attributes of the request (local or transportable).
Different object types have different transport attributes:
Each Repository object has an
If a
consolidation route leading from the current system is defined in the TMS for this transport layer, then the object is recorded in a task belonging to a transportable change request.If no consolidation route leading from the current system is defined in the TMS for this transport layer, then the object is recorded in a task belonging to a local change request.
If the change request is transportable, the target of the request must be the same as the consolidation target of the object.
If the current system is the
original system of the object, the object will be assigned to a task of the type correction.If the current system is not the original system of the object, the object will be assigned to a task of the type
repair.Client-specific Customizing objects are recorded in tasks that belong to
If a consolidation route leading from the current system is defined in the TMS for the standard transport layer of the system or the current client, then the object is recorded in a task belonging to a transportable Customizing request.
The system uses the consolidation route of the standard transport layer to determine the transport target of the Customizing request. However, you can change this target.
If no consolidation route leading from the current system is defined in the TMS for the standard transport layer of the system or the current client, then the object is recorded in a task belonging to a Customizing request without transport target.