Plant address change issue

[vijaykumar_gadhe]

Hi Gurus,

We are having X and Y plants, i have change x plant address in dev and we moved that TP to quality ,address changed successfully ,then we moved to production the its changes X address and Y plant address ,,i checked in production both plant having same address number ,in quality and dev both plant having diffrent Address number ,we are using ECC 6.0 system,please help me out from this issue.

[Prasoon · Accepted solution]

Hi,

   Could you check the note: 1471331 - OX18: Address data of T001W incorrect

Regards,

AKPT

[vijaykumar_gadhe · Accepted solution]

Hi ,

Thanks for your reply ,1471331 note applicable for us.

Regards

G.Vijay kumar

[Former Member · Accepted solution]

I guess you should wait for your ticket response..

[vijaykumar_gadhe · Accepted solution]

Dear gurus,

Our issue resolved after moving a TP of all plants,in our production system t001w table having wrong address number with correct address details,when we checked that address number in ADRVtable we came to know wrong application in that table,after moving TP system will check ARDV table using application key and plant if system gets number system will update for the same ,if system would not find any number its generates new number,our case after moving the TP system searched ARDV table and updating the same,but that address number already assigned to another plant so that address  change affecting an other plant.

Thanks and regards

g vijay

[vijaykumar_gadhe]

Dear Juren,

we have raised customer message to SAP ,still now they didn't provide any route cause ,they said refer note 385440,as per note 25182,385440 after  Release 4.6 the address data is transported via shadow tables, we are using ECC 6 I have checked transport request it is having shadow table (address 4.6),     

I have checked address number range for all client (dev ,quality , production )

number range are same ,is this route cause for over writing address number ,can please provide some inputs related this issue.

Thanks and regards

G.Vijay Kumar

[JL23]

Having just one number range for address, yes, I am pretty sure this is one root cause for your issue.

Just imagine in your production system every hour you get new addresses because of new customers, vendors, delivery addresses.

This happens less often in your development system, hence you are already at a address number 1000 in production while you still are 75 in the development system. If you then create a new plant in development it gets address number 76, you transport it to production, and there 76 is already used by a customer master. And your conflict starts.

Having different number ranges for data that is coming from development to production than for data that is directly entered in production will help to avoid this conflict.

Still IMHO I think the shadow table technic was designed exactly for this case, and it worked for me many years for more than 450 plants without any issue, and this issue came up without having changed any number ranges before, and this makes me think that something on the programs was changed with upgrade to ECC6. It costs a lot of energy and numerous days to argue against SAP support, and it is just a few minutes you can get away with this issue by using different number ranges. A number which is anyway invisible for the normal users and just there for a technical pleasure of the programs and database.

[JL23]

Please read this older discussion, I pretty sure it is same issue with overlapping number ranges

Read the OSS notes mentioned in that discussion:

[vijaykumar_gadhe]

Dear juren,

i have checked note 25182 - Inconsistencies due to address transport ,that note is applicable 4.5B,we are using ECC 6.0 can please suggest another solution.

Regards

vijay

[JL23]

it is a mix of consulting note and correction note, the correction part is only for the early releases, but the consulting part is still valid. Try it yourself and report your issue in SAP marketplace

[Former Member]

Dear Vijay,

Are you sure that there was no other TR after the current CR had been created again after earlier TR went to production.

Check the same might there was one more TR created and is lying in QA and not transported to production.............

[Former Member]

Hi,

Please check in quality server both plant address, please check in production server previous Y-plant POs prints for plant address

[former_member183424]

Hi,

When you create the TR. Have you used existing one or you have created new one?

Address for X and Y is remaining old or getting new address to both plant?

Thanks

DEV

[vijaykumar_gadhe]

Hi Dev ,

I have created new TR for Plant address change.

Regards

vijay

[Former Member]

Hi,

Please check you request no

800 my clint v001my fest plant, v002 is my second plant please check your said

[former_member183424]

Hi,

If your Dev and Qua client is fine. Then please ask basis consultant to re-transport the TR again.

Check the dev client again.

Thanks

DEV