Transports copying address jey when making plant changes (T001W-ADRNR)

[former_member443668]

When we transport plant changes from our development (DEV) system to our QA (TST) or production (PRD) systems, the transport moves the entire table entry. This would not be an issue except that out DEV system as address keys (ADRNR) in the 11000000000 range and our PRD system in 30000000 ranges.

Also, the Vendor number plant (LIFNR) is blank and also overwriting the correct value in PRD.

I am open that somehow we screwed up our DEV instance. My question is, how the address key can be transported up to PRD without screwing up the link. If we add a plant and get the key of 11000001234 in DEV, there is no guarantee that the same number would be used in PRD.

So I have two questions.

1. Is the transport function supposed to pass the address keys (ADRNR) with T001W changes?

2. Has anyone experienced a similar situation and if so, what you did to correct it?

We are currently on ECC 6 (enhancement pack 5) and implemented in 1997 on 3.5

Thanks

[sjeevan · Accepted solution]

You may want to look at this note : [25182|https://service.sap.com/sap/support/notes/25182]

[former_member443668]

Thanks all for the help.

We will be making the appropriate fixes

[former_member443668]

Thanks, but the OSS note is only good up through 4.5

We are on ECC 6 EHP5

We used note 25182 through 4.5 and did not need it anymore after that.

It appears that something change in ECC 6 EHP4

Thanks

[JL23]

As of Release 4.6 the problem with transporting address with internal numbers is solved by using a shadow table.

this is a statement in OSS note 385440

your problem is because you are using different number ranges in prod and dev. so a good portion (the consulting portion) of OSS note 25182 is still valid for you.

get your number ranges right, then you should not have any issue in the release you are.