How To Fix WE068 - The previous EAN will be overwritten

SAP Error Message - Details

• Message type: E = Error

• Message class: WE - Messages for EAN Customizing and for EAN management in MM_BD

• Message number: 068

• Message text: The previous EAN will be overwritten

What causes this issue?

You have overwritten the previous EAN manually. Since EANs are normally
used for identification within logistics, changing it may have
far-reaching consequences for management of the material.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Make sure you really want to change the EAN.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WE068 - The previous EAN will be overwritten ?

  Certainly! Here's a detailed explanation regarding the SAP error message WE068 - The previous EAN will be overwritten:
  
  SAP Error Message: WE068
  Text: The previous EAN will be overwritten
  
  Cause:
  The error message WE068 occurs during the processing of IDoc segments related to material master data or similar master data where EAN (European Article Number) or GTIN (Global Trade Item Number) is involved.
  
  The system detects that an incoming EAN (barcode) value for a material or product is going to overwrite an existing EAN value already stored in the system.
  This typically happens during IDoc inbound processing (e.g., message type MATMAS, INVOIC, or similar) when the EAN is updated or maintained.
  The message is a warning or error to prevent unintentional overwriting of existing EANs, which could lead to data inconsistencies or incorrect product identification.
  
  
  When does it occur?
  
  When an inbound IDoc tries to update the EAN/GTIN for a material that already has an EAN assigned.
  The system is configured to check for existing EANs and warns if the new EAN differs from the old one.
  It can also occur if the EAN is maintained in the material master or in the EAN/GTIN tables and the IDoc tries to change it.
  
  
  Solution:
  
  
  Check the incoming data:
  
  Verify the EAN number in the inbound IDoc segment.
  Confirm if the new EAN is correct and intended to replace the old one.
  
  
  
  Check existing EAN data:
  
  Use transaction MM03 (Display Material) and navigate to the EAN/UPC tab to see the current EANs assigned.
  Alternatively, check table MARA or EANLH for existing EAN assignments.
  
  
  
  Decide on action:
  
  If the new EAN is correct and should replace the old one, you can allow the overwrite.
  If the new EAN is incorrect or a duplicate, correct the inbound data or reject the IDoc.
  
  
  
  Adjust system behavior (if appropriate):
  
  The message WE068 can be configured as a warning or error in the IDoc processing function module or user exit.
  If overwriting EANs is a normal business process, you can adjust the logic to allow overwriting without error.
  This might involve modifying the user exit or BAdI used in IDoc processing (e.g., EXIT_SAPLMGMU_001 or similar).
  
  
  
  Manual correction:
  
  If necessary, manually update or delete the old EAN in the system before processing the IDoc.
  
  
  
  
  Related Information:
  
  IDoc Segment: The EAN is usually found in segments like E1MARAM or E1MARAM_EAN in MATMAS IDocs.
  Tables involved:  
  
  MARA (General Material Data)  
  EANLH (EAN/UPC Codes)  
  MARC (Plant Data for Material)  
  
  
  Transactions:  
  
  MM03 - Display Material  
  MM02 - Change Material (to update EAN manually)  
  WE02 / WE05 - IDoc display and analysis  
  
  
  User Exits / BAdIs:  
  
  Check for any custom logic in IDoc inbound processing that handles EAN updates.
  
  
  
  
  Summary:
  
  Cause: Incoming IDoc tries to overwrite an existing EAN for a material.
  Solution: Verify if overwrite is intended; correct data or adjust processing logic accordingly.
  Check: Material master EAN data, IDoc inbound data, and custom enhancements.
  
  
  If you want, I can help you with specific steps to debug or adjust the IDoc processing logic related to this message.