How To Fix NAA009 - Data record 'Delivery costs' does not belong to the document condition

SAP Error Message - Details

• Message type: E = Error

• Message class: NAA - Subsequent settlement (Purchasing)

• Message number: 009

• Message text: Data record 'Delivery costs' does not belong to the document condition

What causes this issue?

Provisions for accrued income are to be updated when update data is
created for item &V2& of purchasing document &V1& at time &V3& (&V4&).
However, the data record transferred does not correspond to the
document conditions.

System Response

The update data is not created or posted.

How to fix this error?

Please contact your system administrator, as this is due to a program
error.

Procedure for System Administrators

Function module 'MM_ARRANG_FILL_MCKONA_LIS' was called with invalid
data. The transferred data in parameter I_MCEKBZ (delivery costs) )
does not match the line of the document conditions (e.g. different
condition type, level, document number etc.).

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message NAA009 - Data record 'Delivery costs' does not belong to the document condition ?

  The SAP error message NAA009, which states "Data record 'Delivery costs' does not belong to the document condition," typically occurs in the context of pricing and conditions in sales and distribution (SD) or materials management (MM) modules. This error indicates that there is a mismatch between the delivery costs and the conditions defined for a specific document (like a sales order or purchase order).
  Causes:
  
  Condition Record Mismatch: The delivery costs may not be properly defined in the condition records for the document type you are working with.
  Incorrect Document Type: The document type being used may not support the delivery costs condition.
  Missing or Incorrect Configuration: The pricing procedure may not be configured to include delivery costs, or the condition type for delivery costs may not be assigned correctly.
  Data Inconsistencies: There may be inconsistencies in the data, such as missing entries in the condition tables or incorrect assignment of condition types to the pricing procedure.
  
  Solutions:
  
  
  Check Condition Records:
  
  Go to the transaction code VK11 (Create Condition) or VK12 (Change Condition) to verify that the condition records for delivery costs are correctly maintained.
  Ensure that the condition type for delivery costs is defined and active for the relevant document type.
  
  
  
  Review Pricing Procedure:
  
  Use transaction code V/08 to check the pricing procedure assigned to the sales document or purchase document.
  Ensure that the delivery costs condition type is included in the pricing procedure and is correctly configured.
  
  
  
  Document Type Configuration:
  
  Verify that the document type you are using supports delivery costs. You can check this in the configuration settings for sales documents or purchase documents.
  
  
  
  Check for Data Inconsistencies:
  
  Run reports or use transaction codes like V/06 to analyze condition records and ensure there are no missing or incorrect entries.
  If necessary, regenerate the condition records or reassign them to the appropriate pricing procedure.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant notes or updates that may address this specific error message.
  
  
  
  Testing:
  
  After making changes, test the document creation or processing again to see if the error persists.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  VK11 / VK12: Create/Change Condition Records
  V/08: Pricing Procedure Configuration
  V/06: Condition Records Overview
  
  
  Documentation: Refer to SAP Help documentation for detailed information on pricing procedures and condition types.
  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 the root cause of the NAA009 error and implement the necessary corrections to resolve it.