How To Fix UX387 - Condition header data of record & in the sequence not correct

SAP Error Message - Details

• Message type: E = Error

• Message class: UX - TR: Business Partner and Loan Conversion

• Message number: 387

• Message text: Condition header data of record & in the sequence not correct

What causes this issue?

The condition data contains a plausibility error.

System Response

The system refuses to transfer the data.

How to fix this error?

Check the content of the following fields for the record specified:
BZUSAGE

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

The commitment capital must be greater than zero.
DGUEL_KK
No "Start of term" or "Fixed to" values have been entered.
DEFSZ
The "Effective to" date is greater than DGUEL_KK.
DELFZ
The "End of term" is before the "Effective to" date (DEFSZ).
The "End of term" is before the "Start of term" (DEFSZ).

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message UX387 - Condition header data of record & in the sequence not correct ?

  The SAP error message UX387, which states "Condition header data of record & in the sequence not correct," typically occurs in the context of pricing conditions in sales documents, such as sales orders or billing documents. This error indicates that there is an issue with the sequence of condition records, which can lead to inconsistencies in pricing calculations.
  Cause:
  
  Incorrect Sequence of Condition Records: The condition records for pricing may not be in the expected sequence. SAP expects condition records to be processed in a specific order, and if they are not, it can lead to this error.
  Missing or Incorrect Condition Types: If certain condition types are missing or incorrectly configured, it can disrupt the expected flow of condition records.
  Custom Logic or Enhancements: If there are custom enhancements or user exits that manipulate condition records, they may inadvertently cause the sequence to be incorrect.
  Data Integrity Issues: There may be issues with the underlying data in the condition tables, such as duplicates or missing entries.
  
  Solution:
  
  Check Condition Records: Review the condition records for the relevant pricing procedure. Ensure that they are correctly defined and in the expected sequence.
  
  Use transaction codes like VK13 (Display Condition) to check the condition records.
  
  
  Review Pricing Procedure: Ensure that the pricing procedure assigned to the document is correctly configured and that all necessary condition types are included.
  
  Use transaction code V/08 to review and adjust the pricing procedure.
  
  
  Check for Custom Logic: If there are any custom enhancements or user exits that affect pricing, review them to ensure they are not causing the issue.
  Data Consistency Check: Run consistency checks on the condition tables to identify any data integrity issues. You can use transaction codes like SE11 to check the database tables directly.
  Recreate Condition Records: If the issue persists, consider recreating the condition records to ensure they are correctly set up.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) for managing condition records.
  Pricing Procedure Configuration: Understanding how pricing procedures work in SAP is crucial. Review the configuration of pricing procedures in the system.
  SAP Documentation: Refer to SAP Help documentation for detailed information on pricing conditions and procedures.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, it may be beneficial to involve your SAP support team or consult with an SAP expert for further assistance.