How To Fix GI587 - User table & does not match the target ledger

GI587 - Overview

• Message type: E = Error

• Message class: GI - FI-SL update

• Message number: 587

• Message text: User table & does not match the target ledger

What causes this issue?

The user table (&V1&) you entered for the field selection of the
account assignment uses table &V2& as the basis table.
The target ledger you entered belongs however to (summary) table &V3&.
This combination is not useful, since you would be making assignments
to fields not contained in the target ledger.

System Response

The target ledger/user table combination is not accepted.

How to fix this error?

Enter a user table that uses the summary table of target ledger (&V3&)
as the basis ledger or the line item table of target ledger (&V4&). By
selecting the F4 help, you can obtain a list of valid user tables.
You also have the option of not entering a user table. If this case,
the system automatically uses the entire line item table of your target
ledger (&V4&) as the user table.
<DS:SIMG.SIMG_CFMENUGCU0GCUT>Maintain User Tables</>

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GI587 - User table & does not match the target ledger ?

  The SAP error message GI587 indicates that there is a mismatch between the user table and the target ledger in the context of financial postings or document processing. This error typically arises when there is an inconsistency in the configuration or data between the user-defined settings and the target ledger settings in the system.
  
  Cause:
  
  Configuration Mismatch: The user table settings (like document types, account types, etc.) do not align with the settings of the target ledger. This can happen if the ledger has been changed or if the user table has not been updated accordingly.
  Missing Authorizations: The user may not have the necessary authorizations to post to the specified ledger.
  Incorrect Posting Period: The posting period may be closed or not open for the target ledger.
  Data Inconsistencies: There may be inconsistencies in the data being posted, such as incorrect account assignments or missing required fields.
  
  
  Solution:
  
  Check Configuration: Review the configuration settings for both