How To Fix 67_RFC319 - Condition header &1/&2 with Rollover number &3 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: 67_RFC - Message Class for RFC Modules

• Message number: 319

• Message text: Condition header &1/&2 with Rollover number &3 not found

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 67_RFC319 - Condition header &1/&2 with Rollover number &3 not found ?

  The SAP error message "67_RFC319 Condition header &1/&2 with Rollover number &3 not found" typically relates to issues with condition records in the pricing procedure, particularly when dealing with condition types that have a rollover mechanism. This error can occur in various scenarios, such as during pricing determination, when trying to access condition records, or when executing certain transactions that involve pricing.
  Cause:
  
  Missing Condition Records: The most common cause of this error is that the condition record for the specified condition type and key combination does not exist in the system.
  Incorrect Rollover Number: The rollover number specified in the error message may not correspond to any existing condition records.
  Data Inconsistencies: There may be inconsistencies in the data, such as missing or incorrect entries in the condition tables.
  Configuration Issues: The pricing procedure or condition type may not be configured correctly, leading to the inability to find the required condition records.
  
  Solution:
  
  
  Check Condition Records:
  
  Use transaction code VK13 (Display Condition) to check if the condition records for the specified condition type and key combination exist.
  If they do not exist, you may need to create them using transaction code VK11 (Create Condition).
  
  
  
  Verify Rollover Number:
  
  Ensure that the rollover number specified in the error message is correct and corresponds to an existing condition record.
  If necessary, adjust the rollover number or create the appropriate condition records.
  
  
  
  Review Configuration:
  
  Check the configuration of the pricing procedure and the relevant condition types in the SPRO transaction (Customizing).
  Ensure that the condition types are correctly set up to allow for rollover and that all necessary settings are in place.
  
  
  
  Data Consistency Check:
  
  Perform a data consistency check to identify any discrepancies in the condition records or related tables.
  You may need to consult with your SAP Basis or technical team to run consistency checks or to analyze the database.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific condition type and pricing procedure for any additional guidance or known issues.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  VK11: Create Condition
  VK12: Change Condition
  VK13: Display Condition
  SPRO: Customizing Implementation Guide
  
  
  Condition Tables: Familiarize yourself with the relevant condition tables (e.g., KONV, KONP) to understand how condition records are stored.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  If the issue persists after following these steps, it may be beneficial to engage with SAP support or your internal SAP team for further assistance.