How To Fix KI351 - Account assignment check in parallel GL ledgers like leading ledger

SAP Error Message - Details

• Message type: E = Error

• Message class: KI -

• Message number: 351

• Message text: Account assignment check in parallel GL ledgers like leading ledger

What causes this issue?

A posting for a parallel general ledger is created.

System Response

If the message type is "E" (error), the account assignment is checked
when posting to parallel ledgers of the general ledger just as with
posting to the leading ledger. If the message type is W, S, or I, or if
the message is deactivated, the account assignment is not checked as
rigorously when posting to parallel ledgers only. For example, in such
cases you can use an account with a cost element without specifying an
account assignment object, because the postings are not transferred to
Controlling.

How to fix this error?

In the standard system configuration, this message is issued as a
warning message. However, you can change the message type or deactivate
the message in Customizing.

Procedure for System Administrators

To change the message type of message KI351, go to the Implementation
Guide (IMG) under General Controlling,
<DS:SIMG.SIMG_CFMENUORK3OBA5>Change Message Control</>
(work area KI, message number
351).

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KI351 - Account assignment check in parallel GL ledgers like leading ledger ?

  The SAP error message KI351, which states "Account assignment check in parallel GL ledgers like leading ledger," typically occurs in the context of controlling (CO) and financial accounting (FI) when there is a mismatch or inconsistency in account assignments between the leading ledger and parallel ledgers.
  Cause:
  
  
  Inconsistent Account Assignments: The error often arises when the account assignment in the controlling document does not match the account assignment in the financial document. This can happen if the settings for the parallel ledgers are not aligned with the leading ledger.
  
  
  Missing Configuration: If the configuration for the parallel ledgers is not set up correctly, it can lead to discrepancies in how account assignments are validated.
  
  
  Document Type Issues: The document type used may not be compatible with the account assignment settings in the parallel ledgers.
  
  
  Master Data Issues: There may be issues with the master data (e.g., cost centers, internal orders) that are being used in the transaction.
  
  
  Solution:
  
  
  Check Account Assignments: Review the account assignments in both the controlling and financial documents to ensure they match. Make sure that the same cost centers, internal orders, or other account assignments are used in both ledgers.
  
  
  Configuration Review: Verify the configuration settings for the parallel ledgers in the SAP system. Ensure that the account assignment settings are consistent across the leading and parallel ledgers.
  
  
  Document Type Configuration: Check the configuration of the document types being used. Ensure that they are set up to allow the necessary account assignments.
  
  
  Master Data Validation: Validate the master data being used in the transaction. Ensure that all relevant master data (cost centers, internal orders, etc.) is correctly set up and active.
  
  
  Transaction Type: Ensure that the transaction type being used is appropriate for the account assignment being made.
  
  
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on resolving it.
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like OBY6 (for ledger settings) or OKB9 (for account assignment) to review and adjust settings.
  SAP Documentation: Refer to SAP Help documentation for detailed information on account assignment checks and parallel ledgers.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the root cause of the KI351 error and implement the necessary solutions to resolve it.