How To Fix LTR2_ES070 - Object &1 does not exist but is contained in the embedded specification

LTR2_ES070 - Overview

• Message type: E = Error

• Message class: LTR2_ES -

• Message number: 070

• Message text: Object &1 does not exist but is contained in the embedded specification

What causes this issue?

The database table LTR2_WS_ROBJ which stores all objects contained in an
embedded specificiation has an inconsistency. Currently, object &V1& is
referenced in this table but this object (business object, data model,
link, etc.) does not exist in this system.

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?

The embedded specification has been created in a different system and
has been transported into this system. Ensure in this case, that all
objects added to the embedded specification are also transported into
this system.
If there is a different inconsistency existing , then fix table
LTR2_WS_ROBJ. Currently, there is no repair report existing.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message LTR2_ES070 - Object &1 does not exist but is contained in the embedded specification ?

  The SAP error message LTR2_ES070 indicates that there is an issue with an object that is referenced in an embedded specification but does not exist in the system. This typically occurs in the context of SAP's Logistics and Transportation Management modules, particularly when dealing with embedded specifications for transportation planning or logistics execution.
  
  Cause:
  The error can be caused by several factors:
  
  Missing Object: The object (e.g., a material, vendor, or location) that is referenced in the embedded specification has been deleted or does not exist in the system.
  Incorrect Configuration: There may be a configuration issue where the object is not properly defined or linked in the system.
  Transport Issues: If the object was recently transported from another system (e.g., from a development to a production environment), it may not have been included in the transport request.
  Data Inconsistency: There may be inconsistencies in the database or issues with data synchronization.
  
  
  Solution:
  To resolve the error, you