Datasheet

A new APProAch to SyStem cuStomIzAtIon 13
activity, and this transport movement can happen once the system is in production.
Remember that it is only necessary to release and move client-dependent trans-
ports to the development-testing client. Client-independent transports are already
reected in all clients in the environment. Client-independent transports need to
be released and moved only when sending changes from environment to environ-
ment. Figure 1.2 shows the listing of transports created by an individual consultant
or developer. is screen is obtained by proceeding through the screen displayed by
transaction code SE10 shown earlier in Figure 1.1.
FIgurE 1.2 The transports “owned” by John Burger
Each transport in the list (as shown in Figure 1.2) can be expanded to show the
tasks included in it. Each transport has at least one related task assigned to it. e
tasks actually contain the table changes. e upper-level transport acts only as a
container for these tasks. When you release transports for the Basis group, you must
release the individual tasks related to the transport before releasing the upper-level
transport. It is important to note that each task always has objects attached to it.
It is not necessary to release objects to the Basis group, only the tasks themselves.
is is because the tasks carry the objects with them. When you release a task, a
snapshot is taken of the key that is contained in the task. e conguration that
resides in the snapshot is what is written to the operating system to be transported.
It is very important to understand this timing and how it aects your transports if
other consultants are conguring the same key. For example, consultant X makes a
change to object key 123 on May 1st; on May 30th, consultant Y makes a change to
the same object key 123. When consultant X releases his task on June 1st, it contains
the changes that consultant Y made on May 30th, not the changes that consultant X
made on May 1st. As you can see, communication is a key success factor on any SAP
project. Transports are released using the same screen that is generated by following
23288c01.indd 13 2/19/09 10:55:35 PM