How To Fix O5152 - Unable to delete - alternative ship-to partners exist in table OIDMP.

SAP Error Message - Details

• Message type: E = Error

• Message class: O5 - IS-Oil: MCOE message pool

• Message number: 152

• Message text: Unable to delete - alternative ship-to partners exist in table OIDMP.

What causes this issue?

It is not possible to delete the last ship-to partner if alternative
ship-to partners exist in table OIDMP.

System Response

The ship-to partner has not been deleted.

How to fix this error?

Choose the <ZK>Ship-to partnrs</> pushbutton (or edit table OIDMP using
transaction O5G2) and remove the alternative ship-to partner entries in
this table for the current document and item number.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message O5152 - Unable to delete - alternative ship-to partners exist in table OIDMP. ?

  The SAP error message O5152 "Unable to delete - alternative ship-to partners exist in table OIDMP" typically occurs when you attempt to delete a ship-to party (customer) that is still associated with other records in the system, specifically in the OIDMP table, which stores alternative ship-to partners.
  Cause:
  The error arises because the ship-to partner you are trying to delete has alternative ship-to addresses linked to it. SAP prevents the deletion to maintain data integrity, as there are dependencies that need to be resolved first.
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check for Alternative Ship-To Partners:
  
  Use transaction code SE16 or SE16N to access the OIDMP table.
  Search for the ship-to partner you are trying to delete to see if there are any alternative ship-to partners associated with it.
  
  
  
  Remove Alternative Ship-To Partners:
  
  If you find alternative ship-to partners linked to the ship-to party, you will need to remove or update these associations before you can delete the original ship-to partner.
  You can do this by navigating to the relevant customer master data in transaction XD02 (Change Customer) or VD02 (Change Customer - Sales Area) and removing the alternative ship-to partners.
  
  
  
  Delete the Ship-To Partner:
  
  Once all alternative ship-to partners have been removed, you can attempt to delete the original ship-to partner again.
  
  
  
  Check for Other Dependencies:
  
  If the issue persists, ensure that there are no other dependencies or references to the ship-to partner in other tables or transactions.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  XD02 / VD02: Change Customer
  SE16 / SE16N: Data Browser for table access
  
  
  Tables:
  
  OIDMP: Table for alternative ship-to partners
  
  
  Documentation:
  
  Refer to SAP Help documentation for customer master data management for more details on managing ship-to partners.
  
  
  
  Additional Tips:
  
  Always ensure you have the necessary authorizations to make changes to customer master data.
  Consider backing up any important data before making deletions or significant changes.
  If you are unsure about the implications of deleting a ship-to partner, consult with your SAP administrator or a functional consultant.