SAP Knowledge Base Article - Public

3537565 - Duplicate condition types are determined in one invoice

Symptom

Duplicate condition types are determined in one invoice. One condition type marked as Application "M" is automatically fetched and overrides the previous condition type with Application "V", resulting in an inaccurate overall net value.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

Environment

SAP S/4HANA Cloud Public Edition

Cause

Among these duplicated entries for condition type, one of them is coming from MM side (KAPPL=M) and the other is being determined when billing document is tried to be created (KAPPL=V). This is occurring due to settings in copy control. The pricing type is ‘B’, that will redetermine taxes. And price source is configured as ‘A’ - purchase order. Then, it will have condition type being copied from Purchase Order and also the same ones will be redetermined in SD side.

Resolution

Consider the following according to business requirement:

  • To avoid copying condition type from purchase order, change the pricing source to blank or ensure the condition type in the purchase order is different from the billing document.
  • To prevent the condition type from being redetermined in invoice, use pricing type 'A' or 'D'.

Keywords

duplicate, same, condition type, invoice, application, M, V, inaccurate, net value, MM, KAPPL, SD, copy control, pricing type, price source, purchase order , KBA , SD-BIL-IV-2CL , Processing Billing Documents (Public Cloud) , SD-BF-PR-2CL , Pricing (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions ; SAP S/4HANA Cloud all versions