Transports Prior to Release 4.6


It has been possible to transport Customizing objects together with their addresses since Release 1.1. The view maintenance of Customizing objects provides a direct link to address maintenance. This function is automatically activated if the Customizing object has a table field with the domain AD_ADDRNUM (up to Release 3.1I: domain CADRNR or ADRNR).

Up to Release 3.1I, Customizing addresses were stored in table SADR using function module ADDRESS_MAINTAIN. This table was also used as an address file for other applications. As of Release 4.0, Customizing addresses are stored in the new table ADRC and are assigned to address group CA01. When you upgrade from Release 3.x to Release 4.0 or higher, Customizing addresses are converted from table SADR to ADRC using the XPRA RSXADR01 or the prestep report RSXADR05 (see Data Conversion).

For Releases 4.0 and 4.5, the transport takes place using the logical transport object R3TR TDAT ADDRESS. Prior to 4.0, R3TR TABU SADR/SADR2/SADR3/SADR4/SADR5 is used.

Special Features for Release 4.0

A new feature implemented for Release 4.0 is the OBJH-OBJHASADDR indicator, which shows whether a Customizing object has address functions (indicator is set) or not. You can use this indicator to reset the attribute "Object has an address" when maintaining the attributes of a Customizing object.

Uniqueness of Address Numbers

Up to and including Release 4.5, the table keys from the source system, that is, the internal address numbers assigned there, are used to transport address data. When assigning the address numbers, BAS retrieve a number from a number range. You define the number range interval for the number range object ADRNR in Customizing for Business Address Services under SAP NetWeaver ® Basis Services  ® Address Management  ® Maintain Address and Person Number Range.

Since address numbers are only unique in one client of a system, conflicts may arise during the transport of addresses:

·        The address number of an transported address already exists in the target system.

·        The address number does not yet exist in the target system but is reassigned at a later time.

To ensure that the address numbers for addresses are unique across multiple systems, you have to define number range intervals that do not overlap.

See also Note 25182 in SAPNet. This note describes how you define the number range intervals. The note is valid up to Release 4.5. As of Release 4.6, the new transport procedure takes effect, which automatically ensures consistency.