How To Fix FML_CUST012 - Company code skipped because of missing leading ledger, BUKRS &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FML_CUST - Message Class for ML Customizuing

• Message number: 012

• Message text: Company code skipped because of missing leading ledger, BUKRS &1

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FML_CUST012 - Company code skipped because of missing leading ledger, BUKRS &1 ?

  The SAP error message FML_CUST012 indicates that a company code (BUKRS) is being skipped due to a missing leading ledger. This typically occurs in the context of Financial Accounting (FI) and is related to the configuration of ledgers in the system.
  Cause:
  
  Missing Leading Ledger: The leading ledger is a primary ledger that is used for financial reporting. If the company code does not have a leading ledger assigned, the system cannot process transactions for that company code.
  Configuration Issues: The company code may not be properly configured in the system, or the leading ledger may not be defined in the configuration settings.
  Data Migration Issues: If data has been migrated from another system, there may be inconsistencies or missing configurations related to ledgers.
  
  Solution:
  
  
  Check Ledger Configuration:
  
  Go to the SAP Customizing Implementation Guide (SPRO).
  Navigate to Financial Accounting (New) > Financial Accounting Global Settings > Ledgers > Define Ledgers.
  Ensure that a leading ledger is defined and assigned to the relevant company code.
  
  
  
  Assign Leading Ledger to Company Code:
  
  In the same configuration area, check if the company code is assigned to the leading ledger.
  If not, assign the leading ledger to the company code.
  
  
  
  Review Company Code Settings:
  
  Check the company code settings to ensure that all necessary configurations are in place.
  Go to Financial Accounting (New) > Financial Accounting Global Settings > Company Code > Edit, Copy, Delete, Check Company Code.
  
  
  
  Check for Data Migration Issues:
  
  If the issue arose after a data migration, review the migration process to ensure that all necessary configurations were carried over correctly.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the error message for any additional guidance or specific steps that may be required.
  
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like OBY6 (to check company code settings) and OB22 (to check ledger assignments) to navigate directly to the relevant configuration areas.
  SAP Notes: Check for any SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Support: If the issue persists after checking the configurations, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  By following these steps, you should be able to resolve the error message FML_CUST012 and ensure that the company code is properly configured with a leading ledger.