Solution : https://service.sap.com/sap/support/notes/323700 (SAP Service marketplace login required)
Summary :
SAP Note highlights issues with transporting organizational units with addresses from systems with Release <4.6 to systems with Release >=4.6 where addresses are not imported. This occurs because from Release 4.6 onward, a new logical transport object (R3TR TDAT ADDRESS_4.6) is utilized, replacing the older object (R3TR TDAT ADDRESS). SAP advises against such transports due to potential inconsistencies. If unavoidable, manual entry of addresses in the target system or creating a dedicated transport including all R3TR TABU entries for address tables with generic keys is recommended. Attention must be paid to specific corrective measures to mitigate data loss risks.
Key words :
additional key words address address_4, logical transport object r3tr tdat address, solution sap basically recommends, r3tr tdat address_4, r3tr tdat address, logical transport object, r3tr tabu entries, extra work required, pay careful attention, symptom organizational units
Related Notes :
| 119780 | HR-CA-ALE: HR and Application Link Enabling (ALE) |
| 25182 | Inconsistencies due to address transport |