Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member

Document Detail:-

This document enlist the solution step by step when an user/consultant mistakenly or without proper checking delete the existing storage location from the system.

Scenario details:-

Below can be the sequence scenario where we can implement this solution:-

a. End user requested deletion of storage location without checking if there is any existing document linked to storage location requested for deletion

b. End user has checked that there is no document linked to storage location to be deleted and some other end users posted the document in system

c. Requested storage location is deleted and transport request is moved to production system and existing purchase order is now impacted as user can not open it

d. New TR is moved to re-create the deleted storage location in step c.

Possible Impact:-

Due to the above scenarios listed, user is no longer can access the purchase order or purchase requisition and they are stuck for further processing.

Error Details:-

Message no. AM010

Description: Address does not exists

Root Cause of Error:-

When ever we create a new storage location in system, a running number is generated for the address we create. This is updated in field: ADRN2 and in standard table: ADRC. So, when we create a PO with storage location: S1 (for exampe) with an entry in ADRC table. this address number gets updated in field: ADRN2 under "Delivery" tab of line item.

Let say someone mistakenly or without proper checking delete the storage location: S1, system will not allow the further movement of goods. Hence, we re-creates the storage location S1 with same address but this will get updated in table: ADRC with different ADRN2 number.

So, here is the problem, we have a PO with storage location- S1 and address number- ADRN2 and this field: ADRN2 value does not exists in system. Entry for S1 is updated with different ADRN2 value. So, system will give error ~ Address number does not exists~ and will not allow opening the PO.

Solution:-

Implement SAP note # 91001. After Implementation, you have to create a program: ZCORADDR from the instruction provided in note. Here you have to take your ABAP help.

Once program: ZCORADDR is created, we can input PO number and line item where storage location- S1 is maintained. It will wipe of the address number from the field and you will be able to use the PO.

Enter PO number and Line item number

Execute (F8)

After above steps, we need to go back in purchase order and open it in change mode and insert the correct storage location number.

The good part of report is that it will not work for the purchase order which are correct. It is only executable for the PO with incorrect storage location.

Conclusion

For code/Technical code related information, please check SAP note # 91001

Labels in this area