How To Fix FI_E158 - SGL transaction code not found although line has been defined as relevant

SAP Error Message - Details

• Message type: E = Error

• Message class: FI_E - Message Class for FM English Developers

• Message number: 158

• Message text: SGL transaction code not found although line has been defined as relevant

What causes this issue?

You have activated the budgetary ledger (BL) integrated with the Funds
Management system for company code &V1&. The company code is assigned
to an FM area with an update profile active for the BL.
To be able to post in the BL, you must define relevant line items by
using transaction FMSGLCODER. In this case, the line item has been
defined as relevant for the BL based on the document type and account
number; however, it has not been customized for the puprose of deriving
the SGL transaction code.
The SGL transaction code must also be defined using transaction
FMSGLCODER, so that when a line is defined as relevant for the BL, it
has a corresponding SGL transaction code based on the source fields for
derivation.

System Response

This posting cannot be performed until the error has been corrected.
The line has been defined as relevant for the budgetary ledger for
document type &V2& and FI-GL account &V3& in company code &V1&.

How to fix this error?

If you think that this error should not occur because the line is not
relevant for budgetary ledger postings, correct the customizing using
transaction FMSGLCODER. Otherwise, if this line <ZH>is</>relevant for
the budgetary ledger, check the derivation of the SGL transaction code
using the same SAP transaction code.

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 FI_E158 - SGL transaction code not found although line has been defined as relevant ?

  The SAP error message FI_E158 indicates that a specific SGL (Subledger) transaction code is not found, even though the line has been defined as relevant. This error typically arises in the context of financial accounting and can be related to various configuration issues. Here’s a breakdown of the potential causes, solutions, and related information:
  Causes:
  
  
  Missing Configuration: The SGL transaction code may not be properly configured in the system. This could mean that the transaction code is not defined in the relevant customizing settings.
  
  
  Incorrect Assignment: The transaction code might not be assigned to the appropriate account or document type, leading to the system not recognizing it as valid.
  
  
  Authorization Issues: The user may not have the necessary authorizations to access the specific SGL transaction code.
  
  
  Data Inconsistencies: There may be inconsistencies in the master data or transaction data that prevent the system from recognizing the transaction code.
  
  
  Version or Release Issues: The error could also arise if there are discrepancies between different versions of the software or if the system has not been updated properly.
  
  
  Solutions:
  
  
  Check Configuration:
  
  Go to the customizing settings (transaction code SPRO) and navigate to the relevant section for defining SGL transaction codes.
  Ensure that the transaction code is defined and correctly configured.
  
  
  
  Verify Assignments:
  
  Check the assignment of the SGL transaction code to the relevant account or document type.
  Ensure that the line item is correctly marked as relevant for the transaction code in question.
  
  
  
  Review Authorizations:
  
  Ensure that the user has the necessary authorizations to execute the transaction code.
  You can check this using transaction code SU53 to see if there are any authorization issues.
  
  
  
  Data Consistency Check:
  
  Run consistency checks on the master data and transaction data to identify any discrepancies.
  Use transaction codes like FBL1N (Vendor Line Item Display) or FBL3N (G/L Account Line Item Display) to review the data.
  
  
  
  Consult Documentation:
  
  Review SAP notes and documentation related to the specific error message for any known issues or patches that may need to be applied.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO (Customizing), SU53 (Authorization Check), and others that may help in troubleshooting.
  SAP Notes: Search for SAP Notes related to FI_E158 for any specific patches or updates that may address the issue.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the root cause of the FI_E158 error and implement the necessary solutions to resolve it.