How To Fix FSH_DEM_PIR095 - PIR consumption not found from date &1 to &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FSH_DEM_PIR - Fashion specific Planned Independent Requirements

• Message number: 095

• Message text: PIR consumption not found from date &1 to &2

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 FSH_DEM_PIR095 - PIR consumption not found from date &1 to &2 ?

  The SAP error message FSH_DEM_PIR095 indicates that there is a problem with the consumption of a Planned Independent Requirement (PIR) in the system. Specifically, it states that the PIR consumption could not be found for the specified date range (from date &1 to date &2). This error typically arises in the context of demand management and production planning.
  Causes:
  
  No PIR Data: There may be no planned independent requirements defined for the specified date range.
  Incorrect Date Range: The date range specified may not align with the periods for which PIRs have been created.
  Consumption Settings: The consumption settings for the PIRs may not be configured correctly, leading to issues in recognizing the consumption.
  Master Data Issues: There could be issues with the material master data or the planning strategy that affect how PIRs are processed.
  Planning Run Issues: If the planning run has not been executed properly, it may not have updated the PIR consumption data.
  
  Solutions:
  
  Check PIR Data: Verify that there are planned independent requirements for the material in question for the specified date range. You can do this by using transaction code MD61 or MD62.
  Adjust Date Range: Ensure that the date range you are querying is correct and that it falls within the periods where PIRs exist.
  Review Consumption Settings: Check the consumption settings in the material master (transaction code MM02) to ensure they are set up correctly for the relevant planning strategy.
  Run Planning: If necessary, execute a planning run (transaction code MD02 or MD03) to ensure that the system has processed the PIRs and updated the consumption data.
  Check Master Data: Review the material master data and ensure that all relevant fields are correctly filled out, especially those related to planning and consumption.
  Consult Logs: Check the logs for any errors or warnings that may provide additional context for the issue.
  
  Related Information:
  
  Transaction Codes:
  
  MD61: Create Planned Independent Requirements
  MD62: Change Planned Independent Requirements
  MD03: Display Planned Independent Requirements
  MD02: MRP Run
  
  
  Planning Strategies: Understand the planning strategies being used (e.g., Make to Stock, Make to Order) as they can affect how PIRs are consumed.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on this error message.
  
  If the issue persists after checking these areas, it may be beneficial to consult with your SAP support team or refer to SAP documentation for further troubleshooting steps.