How To Fix FVD_EXTSKIP153 - No items exist in period

SAP Error Message - Details

• Message type: E = Error

• Message class: FVD_EXTSKIP - Message for Extension and Skip

• Message number: 153

• Message text: No items exist in 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 FVD_EXTSKIP153 - No items exist in period ?

  The SAP error message FVD_EXTSKIP153: No items exist in period typically occurs in the context of financial transactions or reporting, particularly when dealing with external data or financial documents. This error indicates that the system could not find any relevant items or transactions for the specified period in the context of the operation you are trying to perform.
  Causes:
  
  No Transactions in the Specified Period: The most common cause is that there are simply no financial transactions or items recorded in the specified period.
  Incorrect Date Range: The date range specified in the report or transaction might be incorrect or not aligned with the periods in which transactions were recorded.
  Data Posting Issues: Transactions may not have been posted correctly, or there may be issues with the data transfer from external systems.
  Selection Criteria: The selection criteria used in the report or transaction might be too restrictive, leading to no results being returned.
  Period Locking: The financial period may be locked for posting, preventing any transactions from being recorded.
  
  Solutions:
  
  Check Transaction Data: Verify that there are indeed transactions recorded in the specified period. You can do this by running a report or checking the relevant tables.
  Adjust Date Range: Ensure that the date range you are using is correct and encompasses the periods where transactions exist.
  Review Posting Status: Check if the transactions have been posted correctly and if there are any issues with data transfer from external systems.
  Modify Selection Criteria: If applicable, broaden the selection criteria to include more items or periods.
  Unlock Period: If the period is locked, consult with your finance team to see if it can be unlocked for necessary postings.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like FBL1N (Vendor Line Item Display), FBL3N (G/L Account Line Item Display), or FBL5N (Customer Line Item Display) to check for transactions.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation for the specific module you are working with (e.g., FI, CO) for more context on how periods and transactions are managed.
  
  If the issue persists after checking these aspects, it may be beneficial to consult with your SAP support team or a functional consultant who can provide more tailored assistance based on your specific configuration and data.