Datasheet
A new APProAch to SyStem cuStomIzAtIon 11
NOTE
Most transports record only the changes to the table. However, some trans-
ports created by a small number of tables copy the entire table, not just the changes. It
is very important that these whole table transports are watched and managed carefully
so that only the latest changes are reected in the target clients. This is especially impor-
tant once a project is “live” and in maintenance mode. When dealing with whole table
transports, you always run the risk of moving into other environments’ conguration that
shouldn’t be moved. You can also very easily “leapfrog” transports moved by other devel-
opers and overwrite new conguration with old conguration. To avoid the leapfrogging
of values in a table, the conguration team should be organized in a way that one person
owns a specic area of functionality or business process. This structure should include the
review of transports to ensure that common tables are being carefully monitored.
You can use the change request query screen to create a transport automatically in a
conguration client. A transport number is assigned automatically, but you are free
to add the description yourself.
ere are two types of transports: client dependent and client independent. When
an environment such as the development environment is created with multiple cli-
ents, most objects are copied one for one to be used for each individual client. For
example, table T030 contains the settings for automatic account assignment. In the
development environment, the sandbox, conguration, and development-testing
clients each have its own copy of table T030. Any change to table T030 results in
a client-dependent transport—all the T030 tables in the various places reect the
change only aer it is transported.
23288c01.indd 11 2/19/09 10:55:34 PM