Message type: E = Error
Message class: /ACCGO/IC_MSG -
Message number: 038
Message text: Parent child inconsistency
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.
The SAP error message
/ACCGO/IC_MSG038 Parent child inconsistency
typically occurs in the context of the SAP General Ledger (G/L) accounting module, particularly when dealing with intercompany transactions. This error indicates that there is an inconsistency between parent and child entities in the intercompany structure, which can lead to issues in financial reporting and consolidation.Cause:
Data Inconsistency: The parent-child relationship in the intercompany setup may not be correctly defined. This can happen if:
- The parent company code is not properly assigned to the child company code.
- There are missing or incorrect entries in the configuration of the intercompany structure.
- Changes in the organizational structure have not been reflected in the system.
Missing Master Data: The necessary master data for either the parent or child company code may be incomplete or missing.
Configuration Issues: Incorrect settings in the configuration of intercompany transactions can lead to this error.
Solution:
Check Configuration:
- Go to the configuration settings for intercompany accounting and ensure that the parent-child relationships are correctly defined.
- Verify that all necessary company codes are properly assigned and that the hierarchy is correctly set up.
Review Master Data:
- Ensure that all relevant master data (such as company codes, profit centers, and cost centers) is complete and correctly maintained.
- Check for any missing entries in the master data that could lead to inconsistencies.
Data Consistency Check:
- Use transaction codes like
OBY6
(for company code settings) andOBY1
(for intercompany settings) to review and correct any inconsistencies.- Run consistency checks or reports to identify any discrepancies in the intercompany setup.
Consult Documentation:
- Refer to SAP documentation or notes related to intercompany accounting for any specific guidelines or troubleshooting steps.
Testing:
- After making changes, perform test transactions to ensure that the error does not reoccur and that the intercompany transactions are processed correctly.
Related Information:
OBY6
, OBY1
, and FBICR
(for intercompany reconciliation).By following these steps, you should be able to identify and resolve the parent-child inconsistency error in your SAP system.
/ACCGO/IC_MSG037 Unknown error
Self-Explanatory Message Since SAP believes that this specific error message is ...
/ACCGO/IC_MSG036 Enter job log name
Self-Explanatory Message Since SAP believes that this specific error message is ...
/ACCGO/IC_MSG039 Job incomplete ;forPOD details check JobLog in sm37 for Job /accgo/&1_&2
Self-Explanatory Message Since SAP believes that this specific error message is ...
/ACCGO/IC_MSG040 Select an entry and then choose POD
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.