How To Fix G3564 - Partner unit &2 does not exist in dimension &1

SAP Error Message - Details

• Message type: E = Error

• Message class: G3 - Messages for SAP Consolidation: Integration

• Message number: 564

• Message text: Partner unit &2 does not exist in dimension &1

What causes this issue?

The current data record should have been posted in
<DS:GLOS.dimension>dimension</> <ZH>&V1&</> with the assignment of
<DS:GLOS.partner_unit>partner unit</> <ZH>&V2&</>. However, no
<DS:GLOS.consolidation_unit>consolidation unit</> exists with the ID
<ZH>&V2&</>. The consolidation unit ID is determined by the active ID
combination rule for integrated consolidation type <ZH>&V3&</>.

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?

One of the following has caused the error:
Incorrect ID combination rules
Change the rules for integrated consolidation type <ZH>&V3&</> in
Consolidation Customizing.
Missing consolidation unit
Create cons unit <ZH>&V2&</> in Consolidation Customizing.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message G3564 - Partner unit &2 does not exist in dimension &1 ?

  The SAP error message G3564, which states "Partner unit &2 does not exist in dimension &1," typically occurs in the context of SAP's Financial Accounting (FI) or Controlling (CO) modules, particularly when dealing with partner units in a business transaction or reporting scenario.
  Cause:
  This error generally arises due to one of the following reasons:
  
  
  Missing Partner Unit: The partner unit (e.g., a vendor, customer, or cost center) specified in the transaction does not exist in the specified dimension (e.g., company code, controlling area).
  
  
  Incorrect Configuration: The configuration settings for the partner unit or dimension may not be set up correctly in the system.
  
  
  Data Inconsistency: There may be inconsistencies in the master data, such as the partner unit being deleted or not properly maintained.
  
  
  Authorization Issues: The user may not have the necessary authorizations to view or access the partner unit in the specified dimension.
  
  
  Solution:
  To resolve the G3564 error, you can take the following steps:
  
  
  Check Partner Unit: Verify that the partner unit (e.g., vendor, customer) specified in the transaction exists in the system. You can do this by navigating to the relevant master data transaction (e.g., vendor master, customer master) and checking if the partner unit is correctly defined.
  
  
  Verify Dimension: Ensure that the dimension (e.g., company code, controlling area) is correctly set up and that the partner unit is assigned to it. You can check the configuration settings in the relevant customizing transaction (e.g., SPRO).
  
  
  Review Master Data: If the partner unit is supposed to exist, check for any inconsistencies in the master data. This may involve looking for any recent changes or deletions that could have affected the partner unit.
  
  
  Check Authorizations: Ensure that the user has the necessary authorizations to access the partner unit in the specified dimension. This may involve checking user roles and authorizations in the system.
  
  
  Consult Documentation: If the issue persists, refer to SAP documentation or support notes related to the specific error message for additional troubleshooting steps.
  
  
  Contact SAP Support: If you are unable to resolve the issue, consider reaching out to SAP support for further assistance, providing them with the error message details and any relevant transaction information.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE16 (Data Browser), and SPRO (Customizing) to help you navigate through the system.
  SAP Notes: Search for SAP Notes related to error G3564 in the SAP Support Portal for any known issues or patches.
  User Forums: Consider checking SAP community forums or user groups for discussions related to this error, as other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.