Solution : https://service.sap.com/sap/support/notes/385440 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues in environments running Release 4.6 or later where Customizing object addresses in production or quality assurance systems are incorrect or non-existent. The problem stems from changes in the address transport mechanism post-Release 4.6, moving from table entries to shadow tables. The note outlines the transport process for address data involving several steps—from writing keys in a Customizing transaction to transferring address data from shadow tables in the target client after import. Solutions include re-transporting all incorrect objects and ensuring the correct execution of after import methods.
Key words :
v_001_b company codesv_tvko sales organizationsv_tvst shipping pointsv_tvbur sales officesyou, r3tr vdat v_t001w kr3tr tdat address kr3tr tdat address_4, 444t001w adrnr 444us01444t001w adrnr 444us02444t001w adrnr 444gb01, determine additional view names, test/quality assurance system, locally valid address number, entries r3tr tdat address, r3tr vdat v_t001w, r3tr tdat address_4, select table view -> transport
Related Notes :
| 1340144 | VC_T5N9R: Inconsistencies when transporting CAM-data |
| 1228176 | GCB1: Address data not transported |
| 620253 | Problems when you transport Customizing addresses (6.20) |
| 529710 | Warning message in front of the transporting of Addressen wi |
| 480824 | OX18: Address data of T001W incorrect |
| 417809 | Customizing objects display incorrect addresses |
| 368630 | Address transport in Cust.: incorrect assignment II |
| 329732 | Addresses transport in Customizing: incorrect assignment |
| 186910 | Customers / vendors with incorrect address |
| 25182 | Inconsistencies due to address transport |