How To Fix 28712 - Net node number: &1 / condition index: &2

SAP Error Message - Details

• Message type: E = Error

• Message class: 28 - Configuration

• Message number: 712

• Message text: Net node number: &1 / condition index: &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 28712 - Net node number: &1 / condition index: &2 ?

  The SAP error message 28712, which states "Net node number: &1 / condition index: &2," typically relates to issues in the pricing procedure or condition records in the SAP system. This error often occurs when there is a problem with the condition records for pricing, particularly in the context of sales and distribution (SD) or materials management (MM).
  Cause:
  
  Missing Condition Records: The condition records for the specified condition type may not exist in the system.
  Incorrect Configuration: There may be an issue with the configuration of the pricing procedure or condition types.
  Data Inconsistency: There could be inconsistencies in the data related to the pricing conditions, such as missing or incorrect entries in the condition tables.
  Invalid Condition Index: The condition index specified may not be valid or may not correspond to the expected data.
  
  Solution:
  
  
  Check Condition Records:
  
  Go to the transaction code VK13 (Display Condition) and check if the condition records for the specified condition type exist.
  If they do not exist, create the necessary condition records using VK11 (Create Condition).
  
  
  
  Review Pricing Procedure:
  
  Ensure that the pricing procedure is correctly configured. You can check this in the transaction code V/08 (Maintain Pricing Procedures).
  Verify that the condition types are correctly assigned to the pricing procedure.
  
  
  
  Check Condition Index:
  
  Use transaction code V/06 (Maintain Condition Index) to review the condition index settings.
  Ensure that the condition index is correctly defined and that it corresponds to the condition types being used.
  
  
  
  Data Consistency Check:
  
  Run a consistency check on the condition records to identify any discrepancies. This can often be done through standard SAP reports or tools.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the pricing procedure to identify where the error is occurring. This may require assistance from a technical consultant.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  VK11: Create Condition
  VK13: Display Condition
  V/08: Maintain Pricing Procedures
  V/06: Maintain Condition Index
  
  
  
  SAP Documentation: Refer to the SAP Help Portal for detailed documentation on pricing procedures and condition records.
  
  
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to identify and resolve the cause of the SAP error message 28712.