How To Fix 69790 - Condition type & does not have a reference condition type

SAP Error Message - Details

• Message type: E = Error

• Message class: 69 - Central Functions of Financial Asset Management

• Message number: 790

• Message text: Condition type & does not have a reference condition type

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 69790 - Condition type & does not have a reference condition type ?

  The SAP error message 69790, which states "Condition type & does not have a reference condition type," typically occurs in the context of pricing conditions in SAP, particularly when working with the pricing procedure in Sales and Distribution (SD) or Materials Management (MM).
  Cause:
  This error indicates that the specified condition type is missing a reference condition type. In SAP, condition types are used to define how prices, discounts, surcharges, and other pricing elements are calculated. A reference condition type is often required for certain calculations or for the proper functioning of the pricing procedure.
  Possible Reasons:
  
  Configuration Issue: The condition type may not be properly configured in the pricing procedure.
  Missing Reference: The reference condition type may not have been defined in the system for the specified condition type.
  Custom Condition Types: If you are using custom condition types, they may not have been set up correctly to reference existing condition types.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Condition Type Configuration:
  
  Go to the transaction code V/06 (for SD) or M/06 (for MM) to check the configuration of the condition type.
  Ensure that the condition type in question has a reference condition type assigned.
  
  
  
  Assign Reference Condition Type:
  
  If the reference condition type is missing, you can assign it by editing the condition type configuration.
  Make sure to save your changes.
  
  
  
  Review Pricing Procedure:
  
  Check the pricing procedure where the condition type is used (transaction code V/08 for SD).
  Ensure that the condition type is included in the pricing procedure and that it is correctly configured.
  
  
  
  Transport Requests:
  
  If changes were made in a development environment, ensure that the transport requests are moved to the quality and production environments.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test transaction to ensure that the error no longer occurs.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  V/06: Maintain Condition Types (SD)
  M/06: Maintain Condition Types (MM)
  V/08: Maintain Pricing Procedures (SD)
  M/08: Maintain Pricing Procedures (MM)
  
  
  
  Documentation: Refer to SAP Help documentation for detailed information on pricing procedures and condition types.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to condition types and pricing procedures.
  
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation.