How To Fix 69143 - Error during determination of posting period

SAP Error Message - Details

• Message type: E = Error

• Message class: 69 - Central Functions of Financial Asset Management

• Message number: 143

• Message text: Error during determination of posting period

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 69143 - Error during determination of posting period ?

  The SAP error message 69143, "Error during determination of posting period," typically occurs when there is an issue with the posting period settings in the system. This error can arise in various scenarios, such as during document posting, invoice processing, or when executing financial transactions.
  Causes:
  
  Closed Posting Period: The posting period for the transaction date may be closed, preventing any postings to that period.
  Incorrect Configuration: The configuration settings for the posting periods may not be set up correctly in the system.
  Document Type Restrictions: Certain document types may have restrictions on the posting periods they can use.
  Authorization Issues: The user may not have the necessary authorizations to post in the specified period.
  Fiscal Year Variant Issues: The fiscal year variant may not be correctly assigned to the company code or may not match the posting date.
  
  Solutions:
  
  
  Check Posting Periods:
  
  Go to the transaction code OB52 to check the open and closed posting periods. Ensure that the posting period for the transaction date is open.
  If necessary, extend the open periods to allow postings.
  
  
  
  Review Configuration:
  
  Check the configuration settings in SPRO under Financial Accounting (FI) > Financial Accounting Global Settings > Document > Document Types > Define Document Types. Ensure that the document types are correctly configured to allow postings in the desired periods.
  
  
  
  Verify Document Type Settings:
  
  Ensure that the document type being used allows postings in the specified period. You can check this in the document type configuration.
  
  
  
  User Authorizations:
  
  Verify that the user has the necessary authorizations to post in the specified period. This can be checked in the user roles and authorizations.
  
  
  
  Fiscal Year Variant:
  
  Check the fiscal year variant assigned to the company code in OB29. Ensure that it is correctly set up and that the posting date falls within the allowed range.
  
  
  
  Consult SAP Notes:
  
  If the issue persists, consult SAP Notes or the SAP Support Portal for any known issues or patches related to this error.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  OB52: Change Posting Periods
  SPRO: SAP Reference IMG for configuration
  OB29: Define Fiscal Year Variants
  
  
  
  Documentation: Review SAP documentation related to financial accounting and posting periods for more detailed guidance.
  
  
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to identify the cause of the error and implement the appropriate solution.