T001-ADRNR is not regenerated, ADRC entry is missing

[Former Member]

Dear Experts,

We came across an issue during importing customizing of T001W entries with addresses to another client.

For some of the entries the T001W-ADRNR value of the customizing client (010) have been directly copied to other clients, so we have an ADRNR there that points to nowhere. (The entry is not existing in ADRC).

Example:

Client 010 (cust.):

T001W-WERKS=4444

T001W-ADRNR=12345

ADRC-ADRNR exists

ADRV-ADRNR=12345

Client 050 (test; imported from 010):

T001W-WERKS=4444

T001W-ADRNR=12345 (Exactly the same nr as on 010!)

ADRC-ADRNR doesnt exist

ADRV-ADRNR=556677 (Newly generated)

Any idea how to force SAP to use the newly generated ADRNR during import and update it in T001W-ADRNR?

Thanks

Barna

[former_member183424 · Accepted solution]

You may can read this OSS note 385440 - Repairing inconsistencies in Customizing addresses

It explains the transport procedure for address.

[Former Member · Accepted solution]

Hello,

Note was helpful, thank you for that.

After some analysis we found that only those ADDRESS_4.6 entries fail that are assigned to an IMG activity. When we copied these entries as R3TR/TDAT/ADDRESS_4.6 without IMG assignment it worked. Probably there is a kind of sorting implemented in AFTER_IMP_CUST_ADDRESS that caused the issue...

BR
Barna

[Prasoon]

Hi,

   Please check the note: 1471331 - OX18: Address data of T001W incorrect which explains the reason and the solution.

Regards,

AKPT