How To Fix FDC_POSTING_001072 - No recurring schedule entry is between first and last occurrence date.

SAP Error Message - Details

• Message type: E = Error

• Message class: FDC_POSTING_001 - FI Postings

• Message number: 072

• Message text: No recurring schedule entry is between first and last occurrence date.

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 FDC_POSTING_001072 - No recurring schedule entry is between first and last occurrence date. ?

  The SAP error message FDC_POSTING_001072 indicates that there is no recurring schedule entry found between the specified first and last occurrence dates for a recurring posting. This typically occurs in the context of financial document processing, particularly when dealing with recurring entries in SAP.
  Cause:
  The error can be caused by several factors:
  
  Incorrect Date Range: The first and last occurrence dates specified do not match any existing recurring entries in the system.
  Missing Recurring Entries: There may be no recurring entries created for the specified period.
  Configuration Issues: The recurring entry might not be properly configured or activated in the system.
  Data Entry Errors: There could be typographical errors in the dates or other related fields.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check the Date Range:
  
  Verify that the first and last occurrence dates you are using are correct and fall within the range of existing recurring entries.
  
  
  
  Review Recurring Entries:
  
  Navigate to the relevant transaction (e.g., transaction code FBD1 for creating recurring entries) and check if there are any recurring entries set up for the specified period.
  Ensure that the entries are active and correctly configured.
  
  
  
  Adjust Configuration:
  
  If necessary, adjust the configuration of the recurring entries to ensure they are set up correctly for the intended period.
  
  
  
  Create Missing Entries:
  
  If no recurring entries exist for the specified dates, you may need to create them. Use the appropriate transaction to set up the recurring entries.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for additional guidance on managing recurring entries and troubleshooting related errors.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FBD1 (Create Recurring Entry), FBD2 (Change Recurring Entry), and FBD3 (Display Recurring Entry).
  SAP Notes: Check SAP Notes for any known issues or patches related to recurring entries and this specific error message.
  User Roles: Ensure that you have the necessary permissions to view and create recurring entries in the system.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.