How To Fix G5760 - The intercompany partner & from the old EG is not in the new EG

SAP Error Message - Details

• Message type: E = Error

• Message class: G5 - IS-Oil /Joint Venture/ Material transfer pricing

• Message number: 760

• Message text: The intercompany partner & from the old EG is not in the new EG

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message G5760 - The intercompany partner & from the old EG is not in the new EG ?

  The SAP error message G5760 indicates that there is an issue with intercompany partner assignments when transitioning from an old Enterprise Group (EG) to a new one. This error typically arises during processes such as intercompany billing, where the system expects certain partner assignments to be valid and present in the new configuration.
  Cause:
  
  Missing Partner Assignment: The intercompany partner that was valid in the old Enterprise Group is not defined or assigned in the new Enterprise Group.
  Configuration Changes: Changes in the configuration of the Enterprise Groups may have led to the removal or alteration of partner assignments.
  Data Migration Issues: If data was migrated from the old EG to the new EG, there may have been issues during the migration process that resulted in missing or incorrect partner assignments.
  
  Solution:
  
  
  Check Partner Assignments: Verify the intercompany partner assignments in the new Enterprise Group. Ensure that all necessary partners from the old EG are also defined in the new EG.
  
  Navigate to the relevant configuration settings in SAP (e.g., transaction codes like OBY6 for company code settings or OBB2 for intercompany settings).
  
  
  
  Update Configuration: If the partner is missing, you may need to add the intercompany partner to the new Enterprise Group configuration.
  
  Use the appropriate transaction codes to add or modify partner assignments.
  
  
  
  Data Consistency Check: Perform a consistency check on the data to ensure that all necessary intercompany relationships are correctly set up.
  
  You can use transaction codes like SE16 or SE11 to check the relevant tables for intercompany partner data.
  
  
  
  Consult Documentation: Review any documentation related to the changes made during the transition from the old EG to the new EG. This may provide insights into what changes were made and how they affect partner assignments.
  
  
  Testing: After making the necessary changes, conduct tests to ensure that the intercompany processes work as expected without triggering the error.
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Transaction Codes: Familiarize yourself with relevant transaction codes for managing intercompany settings, such as OBY6, OBB2, and OBD2.
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to view and modify intercompany partner assignments.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.