How To Fix FML_CUST031 - Run must not post to ledgers for material inventory

SAP Error Message - Details

• Message type: E = Error

• Message class: FML_CUST - Message Class for ML Customizuing

• Message number: 031

• Message text: Run must not post to ledgers for material inventory

What causes this issue?

In company &V2& the material values and quantities are managed by the
following ledgers of the Universal Journal: &V4&.
For the standard cost scenario, the actual costing run must not post to
these ledgers.
However, the actual costing run you started posts with accounting
principle &V1& which in company &V2& refers to the ledgers: &V3&.

System Response

The closing step is not allowed.

How to fix this error?

Check the customizing settings for parallel COGM valuation of company
&V2&:

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

<DS:SIMG.FCML_MLCO_DC>Set Up Parallel Valuation of Cost of Goods
Manufactured for Company Codes</>

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 FML_CUST031 - Run must not post to ledgers for material inventory ?

  The SAP error message FML_CUST031 indicates that a run (such as a posting or a transaction) is attempting to post to ledgers for material inventory, which is not allowed based on the configuration settings in your SAP system. This error typically arises in the context of financial postings related to materials and inventory management.
  Cause:
  The error is usually caused by one of the following reasons:
  
  Configuration Settings: The system is configured to prevent postings to certain ledgers for material inventory. This is often a deliberate design choice to maintain the integrity of financial data.
  Posting Period: The posting period may be closed, preventing any further postings to the ledgers.
  Transaction Type: The specific transaction type being used may not be allowed to post to the material inventory ledgers.
  Custom Settings: Customizations or enhancements in the system may restrict postings to certain ledgers.
  
  Solution:
  To resolve the FML_CUST031 error, consider the following steps:
  
  
  Check Configuration:
  
  Review the configuration settings in the Financial Accounting (FI) and Controlling (CO) modules to ensure that the ledgers are set up correctly for material inventory postings.
  Navigate to the configuration path: SPRO > Financial Accounting > General Ledger > Ledger > Define Ledgers and check the settings for the relevant ledgers.
  
  
  
  Review Posting Period:
  
  Ensure that the posting period is open. You can check this in the transaction code OB52 (Maintain Posting Periods) to see if the period is closed for the relevant company code.
  
  
  
  Transaction Type:
  
  Verify that the transaction type you are using is allowed to post to the material inventory ledgers. You may need to consult with your SAP functional consultant to understand the allowed transaction types.
  
  
  
  Consult Documentation:
  
  Review any documentation or notes related to the specific error message. SAP Notes may provide additional insights or solutions.
  
  
  
  Custom Code Review:
  
  If there are any custom developments or enhancements in your SAP system, review them to ensure they are not causing the restriction on postings.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide specific guidance based on your system configuration.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MB1A, MB1B, MB1C for material postings, and FB50 for general ledger postings.
  SAP Notes: Search for SAP Notes related to FML_CUST031 for any patches or updates that may address the issue.
  Documentation: Review SAP Help documentation for Financial Accounting and Material Management for best practices and configuration guidelines.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.