How To Fix GL622 - Company code &1 already assigned message type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: GL - FI-SL Rollup

• Message number: 622

• Message text: Company code &1 already assigned message type &2

What causes this issue?

You tried to send data for company code &v1& using a rollup.
The company code already assigned message type &v2& in the distribution
model.

System Response

The rollup cannot be completed because there is a risk of duplicate
data being transferred.

How to fix this error?

Check your distribution model for company code &v1&.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GL622 - Company code &1 already assigned message type &2 ?

  The SAP error message GL622 indicates that a company code is already assigned to a specific message type. This typically occurs in the context of financial accounting, particularly when dealing with General Ledger (GL) accounts and their configurations.
  Cause:
  The error arises when you attempt to assign a company code to a message type that has already been assigned. This can happen during the configuration of financial documents, where the system prevents duplicate assignments to maintain data integrity.
  Solution:
  To resolve the GL622 error, you can follow these steps:
  
  
  Check Existing Assignments:
  
  Go to the relevant configuration area in SAP (usually in the Financial Accounting module).
  Navigate to the section where message types are assigned to company codes (e.g., through transaction codes like OBA7 or similar).
  Verify if the company code is already assigned to the message type you are trying to configure.
  
  
  
  Remove or Modify Existing Assignment:
  
  If the company code is already assigned and you need to change it, you may need to remove the existing assignment first.
  If the assignment is correct and you need to add a new one, consider whether you need to create a new message type instead.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files related to message types and company code assignments to ensure you are following the correct procedures.
  
  
  
  Check for Customizations:
  
  If your organization has custom configurations or enhancements, check with your SAP Basis or ABAP team to see if there are any custom logic or validations that might be causing this issue.
  
  
  
  Testing:
  
  After making changes, test the configuration to ensure that the error does not reoccur and that the system behaves as expected.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBA7 (for message type configuration) and OBA5 (for document types).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Roles: Ensure that you have the necessary authorizations to make changes to company code assignments in the system.
  Documentation: Refer to the SAP Help Portal for detailed information on financial accounting configurations.
  
  If the issue persists after following these steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.