Do you have any question about this error?
Message type: E = Error
Message class: SI - Implementation Guide - Status control
Message number: 079
Message text: ****** Reserved for DDIC foreign key ************************************
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
SI079
- ****** Reserved for DDIC foreign key ************************************ ?The SAP error message "SI079 ** Reserved for DDIC foreign key ****" typically indicates an issue related to the Data Dictionary (DDIC) in SAP, specifically concerning foreign key relationships. This error can arise when there is an attempt to use a reserved key or when there is a problem with the foreign key definition in the data dictionary.
Cause:
- Reserved Keys: The error suggests that the key you are trying to use is reserved for the Data Dictionary and cannot be modified or used in the way you are attempting.
- Foreign Key Definition Issues: There may be a problem with how the foreign key is defined in the database table or structure. This could include incorrect references to primary keys or issues with the data types.
- Data Integrity Violations: If there are existing records that violate the foreign key constraints, this error may also occur.
Solution:
- Check Foreign Key Definitions: Review the foreign key definitions in the Data Dictionary (transaction SE11). Ensure that the foreign key is correctly defined and that it references the appropriate primary key in the related table.
- Avoid Reserved Keys: Ensure that you are not trying to use a key that is reserved for the Data Dictionary. If you are unsure, consult the SAP documentation or your system administrator.
- Data Consistency Check: Run a consistency check on the database tables involved to ensure that there are no orphaned records or data integrity issues. You can use transaction codes like SE14 (Database Utility) to check and repair inconsistencies.
- Transport Requests: If this error occurs after a transport, ensure that all necessary objects have been transported correctly and that there are no missing dependencies.
- Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional guidance.
Related Information:
If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or ABAP team for further investigation.
Get instant SAP help. Start your 7-day free trial now.
SI078
****** Reserved for DDIC foreign key ************************************
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SI077
****** Reserved for DDIC foreign key ************************************
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SI080
At least 1 project must be chosen
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SI081
Planned start & is earlier than project start date &
What causes this issue? You specified a planned starting date which is before the project start time &V2&. The planned starting date must be ...
Click on this link to search all SAP messages.