How To Fix UD704 - Explicit attributes and attribute types of DDIC attributes were deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: UD - EDM - Enterprise Data Model

• Message number: 704

• Message text: Explicit attributes and attribute types of DDIC attributes were deleted

What causes this issue?

There are 3 different attribute categories.
- inherited attributes
- attributes transferred from the ABAP/4 Dictionary
- explicit attributes
Inherited attributes and attributes transferred from the ABAP/4
Dictionary cannot be deleted.
The attribute types are simply deleted for attributes which are
transferred from the ABAP/4 Dictionary.

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?

If you want to delete the attributes which were transferred from the
ABAP/4 Dictionary, you can delete the assignment of the table or view
to the entity types.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message UD704 - Explicit attributes and attribute types of DDIC attributes were deleted ?

  The SAP error message UD704, which states "Explicit attributes and attribute types of DDIC attributes were deleted," typically occurs in the context of data modeling or when working with the ABAP Dictionary (DDIC) in SAP. This error indicates that there is a mismatch or inconsistency in the data model, particularly concerning the attributes of a data element or structure.
  Cause:
  
  
  Deletion of Attributes: The error is often triggered when explicit attributes or their types that were previously defined in the Data Dictionary (DDIC) have been deleted or modified. This can happen if:
  
  A developer manually deletes or alters attributes in the DDIC.
  Changes are made to the underlying data model that are not reflected in dependent objects.
  There are inconsistencies between the data model and the actual database schema.
  
  
  
  Transport Issues: If changes were transported from one system to another (e.g., from development to production) and the transport did not include all necessary objects or dependencies, this error may arise.
  
  
  Inconsistent Data Model: If the data model has been altered without proper adjustments to all dependent objects, it can lead to this error.
  
  
  Solution:
  
  
  Check for Deletions: Review the DDIC to ensure that the attributes and types that are being referenced still exist. If they have been deleted, you may need to restore them or adjust the data model accordingly.
  
  
  Recreate Attributes: If the attributes were deleted unintentionally, you can recreate them in the DDIC. Ensure that the data types and properties match the original definitions.
  
  
  Adjust Data Model: If the data model has been changed, ensure that all dependent objects (like views, tables, or structures) are updated to reflect these changes. This may involve modifying or regenerating these objects.
  
  
  Transport Consistency: If the issue arose after a transport, check the transport logs to ensure that all necessary objects were included. You may need to re-transport missing objects or manually adjust the target system.
  
  
  Check for Dependencies: Use transaction codes like SE11 (Data Dictionary) or SE80 (Object Navigator) to analyze the dependencies and relationships between the objects. This can help identify what might be causing the inconsistency.
  
  
  Regenerate Objects: In some cases, regenerating the affected objects (like views or programs) can resolve the issue. This can be done through the respective transaction codes.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE80 (Object Navigator), and SE37 (Function Builder) to navigate and troubleshoot the issue effectively.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Documentation: Review SAP documentation on data modeling and the Data Dictionary to understand best practices and avoid similar issues in the future.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or ABAP development team for further assistance.