Assignment of Development Projects to Transport Layers
At the start of a development project,Packages are created for the Repository objects that are to be created as part of the project. When you create the package, you assign it to a transport layer. The SAP System proposes the standard transport layer. All Repository objects that you later create in this package belong to the transport layer of this package and are transported according to the routes set up for this layer.
Customizing settings are generally not Repository objects listed in theObject Directory and do not belong to a package. This means that you cannot assign them directly to a transport layer.
Customizing settings are always assigned to the standard transport layer of the SAP System in which they are valid (or of the client, if extended transport control is activated). They are then transported from this system (or client) according to the transport routes set up for the standard transport layer.
Repository objects of the SAP standard delivered by SAP or from SAP add-on components installed in your SAP Systems always belong to the pre-installed "SAP" transport layer. You cannot assign these objects to one of your own transport layers. If you want to patch or modify SAP standard objects in your development system, SAP recommends transporting these changes along the same routes as for your own developments. To do this, you need to set up the same consolidation route for the "SAP" layer as for the standard transport layer of the development system; this means that the source and destination of the two consolidation routes must be the same. (For more information, seeChanging the SAP Standard.) When a two- or three-system group is configured automatically, this consolidation route is created for the "SAP" layer.
The following graphic shows the transport routes of an automatically configured three-system group: