How To Fix GJ520 - Can not Get Field Status for GL Account &

GJ520 - Overview

• Message type: E = Error

• Message class: GJ - Joint Venture Accounting

• Message number: 520

• Message text: Can not Get Field Status for GL Account &

To adjust the field status for the account &V1&:
Go to IMG -> Financial Accounting -> Financial Accounting Global
Settings -> Document -> Line Item -> Controls -> Allocate Company Code
to <DS:TRAN.OBC5>field status variants</>
Find out the field status variant for the company
Go to Accounting -> Financial Accounting -> General Ledger -> Master
records -> display <DS:TRAN.FS03>GL master records display</>
Find out the field status group
Go to IMG -> Financial Accounting -> Financial Accounting Global
Settings -> Document -> Line Item -> Controls ->
<DS:TRAN.OBC4>Maintain field status variants</>
Use the field status variant and field status group to view what is
missing in field status of the account &V1&

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GJ520 - Can not Get Field Status for GL Account & ?

  The SAP error message GJ520, which states "Can not Get Field Status for GL Account &," typically occurs when there is an issue with the field status configuration for a General Ledger (GL) account in the system. This error can arise in various scenarios, such as during document posting or when trying to access certain transactions that involve GL accounts.
  
  Cause:
  
  Field Status Group Configuration: The GL account in question may not have a properly defined field status group. Field status groups control which fields are mandatory, optional, or suppressed during document entry.
  Missing or Incorrect Assignment: The GL account may not be assigned to a field status group, or the assignment may be incorrect.
  Account Type Issues: The account type (e.g., asset, liability, revenue, expense) may not align with the field status group settings.
  Customizations or Changes: Recent changes or customizations in the configuration of field status groups or GL accounts may have led