How To Fix EK502 - G/L account &1 is not maintained in the transaction relevant data

SAP Error Message - Details

• Message type: E = Error

• Message class: EK - IS-U Accounts Receivable and Payable

• Message number: 502

• Message text: G/L account &1 is not maintained in the transaction relevant data

What causes this issue?

You defined the general ledger account &V1& in Customizing. However this
account is not maintained in the account assignment data for
transactions.

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?

If you want to post items to an account that was defined for Bollo
postings in the <ZH>account assignment data for transactions</>, you
must also define the account in <LS>Bollo expenses</>.
The system posts items to the accounts for Bollo postings defined in the
<DS:TRAN.EK02>account assignment data for transactions in IS-U
</> if the threshold amount for Bollo postings is exceeded during a
posting or process. If this happens for a residential customer, the
Bollo charge is passed on. The system generates a document with a
business partner and a general ledger item.
If you want to post debit items to the general ledger account of this
general ledger by paying over Bollo charges, you must enter it in
<LS>Bollo expenses</>.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EK502 - G/L account &1 is not maintained in the transaction relevant data ?

  The SAP error message EK502 indicates that a General Ledger (G/L) account is not maintained in the transaction relevant data for a particular purchasing document or transaction. This error typically arises in the context of purchasing documents such as purchase orders or purchase requisitions when the system cannot find the necessary G/L account information to process the transaction.
  Cause:
  
  Missing G/L Account Assignment: The G/L account that should be associated with the purchasing document is not maintained in the relevant configuration settings.
  Incorrect Account Assignment: The account assignment for the material or service being procured may not be set up correctly in the material master or vendor master data.
  Account Determination Issues: The account determination settings in the configuration may not be set up correctly, leading to the system being unable to find the appropriate G/L account.
  Transaction Type: The transaction type being used may not have a corresponding G/L account defined.
  
  Solution:
  
  
  Check Material Master: Ensure that the material master record has the correct account assignment category and that the relevant G/L accounts are maintained.
  
  Go to the material master (MM01/MM02) and check the accounting view.
  
  
  
  Check Vendor Master: Verify that the vendor master data has the correct G/L account assignments.
  
  Use transaction code XK02 to check the vendor master data.
  
  
  
  Account Determination Configuration: Review the account determination settings in the configuration.
  
  Use transaction code SPRO to access the configuration menu.
  Navigate to Materials Management > Valuation and Account Assignment > Account Determination and ensure that the necessary settings are in place.
  
  
  
  Check Purchase Order/Document Type: Ensure that the purchase order or document type being used has the correct account assignment settings.
  
  Check the configuration for the specific document type in SPRO.
  
  
  
  Consult with Finance Team: If you are unsure about the correct G/L accounts to use, consult with your finance or accounting team to ensure that the correct accounts are being used for the transactions.
  
  
  Testing: After making the necessary changes, test the transaction again to ensure that the error is resolved.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME21N (Create Purchase Order), ME22N (Change Purchase Order), and ME23N (Display Purchase Order) to troubleshoot the issue.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Documentation: Review SAP documentation related to account determination and G/L account assignments for purchasing documents.
  
  By following these steps, you should be able to identify and resolve the EK502 error in SAP.