How To Fix FSH_DEM_PIR064 - Could not determine cond. record

SAP Error Message - Details

• Message type: E = Error

• Message class: FSH_DEM_PIR - Fashion specific Planned Independent Requirements

• Message number: 064

• Message text: Could not determine cond. record

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_PIR064 - Could not determine cond. record ?

  The SAP error message FSH_DEM_PIR064: Could not determine cond. record typically occurs in the context of pricing or condition records in SAP, particularly within the SAP Fashion Management (FSH) module. This error indicates that the system was unable to find a valid condition record for a pricing condition that is required for processing a transaction.
  Causes:
  
  Missing Condition Records: The most common cause is that the required condition records for pricing are not maintained in the system.
  Incorrect Condition Types: The condition type being used may not be set up correctly or may not be applicable for the transaction.
  Data Inconsistencies: There may be inconsistencies in the master data or transaction data that prevent the system from finding the correct condition record.
  Pricing Procedure Issues: The pricing procedure assigned to the document may not be configured correctly, leading to the inability to determine the condition records.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the condition records.
  
  Solutions:
  
  
  Check Condition Records: 
  
  Go to the transaction code VK11 (Create Condition) or VK12 (Change Condition) to check if the necessary condition records exist for the relevant condition type.
  Ensure that the condition records are maintained for the correct combination of key fields (like customer, material, etc.).
  
  
  
  Review Pricing Procedure:
  
  Check the pricing procedure assigned to the sales document or purchase order. Ensure that it includes the necessary condition types.
  Use transaction code V/08 to review and adjust the pricing procedure if needed.
  
  
  
  Validate Master Data:
  
  Ensure that the master data (like customer master, material master, etc.) is correctly maintained and that there are no missing or incorrect entries.
  
  
  
  Check Condition Type Configuration:
  
  Use transaction code V/06 to review the configuration of the condition types and ensure they are set up correctly.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary authorizations to access and maintain condition records.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the pricing procedure to identify where the determination process is failing.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  VK11: Create Condition Record
  VK12: Change Condition Record
  VK13: Display Condition Record
  V/08: Maintain Pricing Procedures
  V/06: Maintain Condition Types
  
  
  
  Documentation: Refer to SAP Help documentation for detailed information on pricing procedures and condition records.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  
  
  If the problem continues after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in pricing and condition records.