Transports as of Release 4.6

As of Release 4.6, BAS use a new transport logic that eliminates potential problems which may arise as a result of transporting the addresses together with their address numbers (see Transports Prior to Release 4.6). It is now no longer the address tables themselves that are transported but rather shadow tables containing the address data. These shadow tables are not productive tables but dummy tables that have all the fields of the original tables. Before the transport, method BEFORE_EXP_CUST_ADDRESS is called. This method writes the addresses to be transported into the shadow tables and creates the associated where-used list.

The transport takes place using the logical transport object R3TR TDAT ADDRESS_4.6.

Once the transport request has been imported into the target system, the address objects that have been transported are processed by calling method AFTER_IMP_CUST_ADDRESS. Since the address numbers are normally not identical in the source and the target systems (they are only valid locally), address objects are identified by their owners, as are addresses distributed using ALE. This requires that 1:1 (1:c) relations exist between objects and addresses. Several Customizing objects cannot point to the same address number.

The references to the application object stored in the key of the shadow tables are used to determine the where-used lists for the addresses. The where-used lists are then used to determine the address numbers for the transported addresses that are valid in the target system. The addresses are updated with the address data from the transported shadow tables. If an address does not exist, it is created and the new address number is updated for all references of the primary tables.

If the shadow table does not contain an address entry, the address was deleted in the source system or the source client. In this case, the address is also deleted in the target system together with the pointers of the application tables.