When clients are copied without application tables, the addresses for the following customizing objects are missing in the target client:
- Company codes (Table T001) transaction OX02
- Address data specific to company codes (T001E) FSAP
- Plants/Branches (T001W) OX10
- Org. unit: Sales offices (TVBUR) OVX1
- Routes: Transport nodes (TVKN) VORD
- Org. unit: Sales organizations (TVKO) OVX5
- Org. unit: Shipping points (TVST) OVXD
Additionally in 2.2 and 3.0:
- Sales tax group Address OBCM
Address tax office (T007F) OBCF
Additionally in 3.0
- Personnel areas (T500P)
- Org. unit: Transport scheduling points (TTDS)
Addresses are stored in the central address file. This file is not copied since it is an application table.
Please also refer to note 25180.
You can transport the addresses (except for transport nodes) to the target client using the correction and transport system.
To do this, enter the customizing objects concerned in a transport request using the transport function within Customizing in the source client.
Export the transport request.
Log on to the (new) target client and import the transport request with transaction SCC1 (prior to 3.0: execute the report RSCLCCOP).
The copied customizing objects are overwritten by the same versions from the source client. In addition, the associated addresses are copied to the target client.
You have to ensure that the status of the address number range (Transaction SNRO, Object ADRNR, Interval 01) in the target client is not reset to 0 (otherwise the numbers of the copied addresses would be used again later, which would lead to DUPLICATE RECORD run-time errors when inserting in the DB table).
Also refer to note 25182 "Address number range: Several systems or clients".
Additional key words
Address, number range
BAS_OLD
No comments:
Post a Comment