How To Fix FML_CUST013 - Company code skipped because of wrong PERIV, BUKRS &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FML_CUST - Message Class for ML Customizuing

• Message number: 013

• Message text: Company code skipped because of wrong PERIV, 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_CUST013 - Company code skipped because of wrong PERIV, BUKRS &1 ?

  The SAP error message FML_CUST013 indicates that a company code (BUKRS) has been skipped due to an incorrect period (PERIV) associated with it. This error typically arises during financial transactions or postings when the system cannot find a valid configuration for the specified company code and period.
  Cause:
  
  Incorrect Period: The specified period (PERIV) may not be open for posting in the company code (BUKRS). This can happen if the period is closed in the financial settings.
  Configuration Issues: There may be a misconfiguration in the financial settings for the company code, such as missing or incorrect settings in the fiscal year variant.
  Company Code Not Active: The company code may not be active for the specified period.
  Posting Period Settings: The posting period settings in the controlling area or company code may not allow postings for the specified period.
  
  Solution:
  
  
  Check Posting Period:
  
  Go to the transaction code OB52 (Maintain Posting Periods) and verify if the period you are trying to post to is open for the specified company code.
  If the period is closed, you may need to open it for posting or adjust your posting date.
  
  
  
  Verify Company Code Configuration:
  
  Check the configuration for the company code in the transaction code OBY6 (Define Company Code) to ensure it is set up correctly.
  Ensure that the fiscal year variant assigned to the company code is correct and that the periods are defined properly.
  
  
  
  Review Fiscal Year Variant:
  
  Use transaction code OB29 to check the fiscal year variant settings. Ensure that the periods are defined correctly and that the variant is assigned to the company code.
  
  
  
  Check for Active Company Code:
  
  Ensure that the company code is active and not in a status that would prevent postings.
  
  
  
  Consult with Finance Team:
  
  If you are unsure about making changes, consult with your finance team or SAP administrator to ensure that any changes made are in line with your organization's financial policies.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  OB52: Maintain Posting Periods
  OBY6: Define Company Code
  OB29: Fiscal Year Variant
  
  
  SAP Notes: Check SAP Notes for any known issues or updates related to this error message.
  Documentation: Review SAP documentation on financial posting periods and company code configuration for more detailed guidance.
  
  By following these steps, you should be able to resolve the FML_CUST013 error and successfully post transactions for the specified company code and period.