Invoice price determination based on sales order pricing date

[Former Member]

Hello Gurus,

I have come across a lot of discussions regarding invoice pricing determination based on sales order pricing date.  I saw options for V/06 condition record and also VTFL for copy control at the item category level.  However, I did not come across a clean or confirmed solution to do this.  We are looking to go away from SAP standards where the invoice pricing date is based on the PGI date.  I think the best option is to utilize pricing date on the pricing condition.  Can you please tell me which one of these options refers to Pricing date of a Sales order

A - Date of Services Rendered (KOMK-FBUDA)

B - Pricing Date (KOMK-PRSDT)

C - Billing Date (KOMK-FKDAT)

D - Creation Date (KOMK-ERDAT)

E - Order Date (KOMK-AUDAT)

As I understand the meaning of these:

A  = PGI date

B = ?

C  = Billing date - in our case, same as PGI date as we create invoices after PGI most likely on the same date

D - is it sales order creation date or invoice creation date?  if it is invoice creation date, then it will be the same as A or C.

E = ?

so what is the difference between B and E?  is either one of these related to sales order pricing date?

thank you in advance.

[sez41 · Accepted solution]

Durga,

Komk-erdat is the document's creation date and filled internally by SAP. For sales orders this is order creation date in SAP and for billing documents it is billing document creation date in SAP.

Komk-audat is the document date. You can manually input a date for this field in sales orders (The purpose? To track the sales order date in case of late entries to SAP by salespersons).

Komk-prsdt is the pricing date. The meaning of this field speaks for itself. Pricing records are read specifically for this date.

Komk-fbuda is PGI date if it's not a service sale. In service sales, this field equals to sales order date.

what does your vtfl settings look like for pricing? Can you share screenshots for relevant item categories?

[Former Member · Accepted solution]

Hi Kvanc,

Thanks for the reply.  attached two screen shots.  one for v/06 and second one from VTFl. 

I expect the condition record / condition price be driven based on sales order pricing date and "Copy manual pricing and redetermine others".   I believe it is only respecting the manual price but it there is a new price that is valid at the time of PGI, it is using the latest price.

what we want is that for our contract price, whatever the valid price is for the "pricing date" of the slaes order, we would want the invoice to be created with that..

example:

there is an existing condition price for $ 5.00 from 01/01/2016 to 07/31//2016.

a future condition price of $ 7 from 8/1 to 12/31.

sales order is created on 7/21, pricing date 7/31.

let's say we early expire the previous condition  for $5 and create a new condition from 7/22 to 7/31 for $6.  PGi happens for  this order on 8/1.

Currently, because the PGI happened on 8/1, it is using $7.  what we want is for invoice to determine price of $6 as it is the condition price for the pricing date on the sales order.

thanks

[Former Member · Accepted solution]

Hi Durga,

While creating invoice (VF01) you need to mention pricing date as 7/31, then it will pick $6 rather than $7. During invoice creation system did not pick the price date from sales order. It picks the current date (in your case PGI date) of invoice creation. So it picks a condition record of $7 rather than $6. If you mention the pricing date as 7/31 in the initial screen of VF01 then it will be copied to line item so as your condition record will determine based on this date. Try this out and let us know if any difficulties you are having.

[Former Member · Accepted solution]

Hi,

this would certainly work if we were creating one invoice at a time manually.  However, we do use VF04 periodic jobs to create invoices so picking a pricing date there would not be feasible as they would vary depending on the invoice being created.  thx

[Former Member · Accepted solution]

Hi Durga,

In that case create a custom routine and assign it to Data VBRK/VBRP in VTFL. So that the system should pick the pricing date from sales order rather than service rendered date or PGI date.

[prashant_sharma21]

Hello Durga,

Basically Pricing date in condition type V/06 specifies that we want to take the value of  condition based on which date.

A - Date of Services Rendered (KOMK-FBUDA)

B - Pricing Date (KOMK-PRSDT)

C - Billing Date (KOMK-FKDAT)

D - Creation Date (KOMK-ERDAT)

E - Order Date (KOMK-AUDAT)

suppose our pricing condition records of pricing condition PR00 change every month.

PR00 Jan = 100

PR00 Feb = 105

PR00 Mar = 110

PR00 Apr = 115

A - Date of Services Rendered (KOMK-FBUDA): Usually system consider this date when we are delivering some goods/services to our customer. in this case system consider PGI date and based on PGI date system take the value of respective condition record of PGI date.

suppose we create the sales order in Jan but PGI is happend on March in this case system picks 110.

K005	Jan	20%
K005	Feb	15%
K005	Mar	10%
K005	Apr	20%

B - Pricing Date (KOMK-PRSDT): suppose for Discount condition K005 we assign pricing date: (KOMK-PRSDT): We could see Pricing date field in our sales order at main window/ Header/item > sales tab. we create the order in Feb so customer is eligible for 15% discount but we want to give him 20% then we will change the Pricing date to Jan month  hence system will pick 20% discount only

C - Billing Date (KOMK-FKDAT): we usually use it in contracts, hence according to Billing date system will pick the value of condition type based on Billing date only.

D - Creation Date (KOMK-ERDAT): suppose we want to give Material discount K004 based on Sales Order Creation date only in this case system consider sales order creation date only and material discount will be applicable based on sales order creation date.

K007	Jan	20%
K007	Feb	15%
K007	Mar	10%
K007	Apr	20%

E - Order Date (KOMK-AUDAT): suppose order is coming from some third party system and it was created on 31 Jab but due to some technical issue it could not come on same day. later issue wan resolved and SAP received the sales order on 1st Feb only. now in this case Order date is 31st Jan but Order creation date is 1 Feb. suppose we are giving Customer Discount K007 based on Order Date only in this case system will pick value from the condition record of 31 jan Not of Feb month.

Thanks,

Prashant sharma

[Former Member]

Hi Durga,

B - Pricing Date (KOMK-PRSDT) - It means system will determine condition records for condition types based on pricing date. In sales order you have a field for pricing date so as in VF01.

A- Service Rendered Date- You can mention service rendered date in sale order or during invoice creation  (VF01).

C- Billing Date - It is the date on which invoice is created.

D- Creation Date- You have two different creation date for sales order and invoice. The determination of condition records for condition types based on condition type will depend on copy control (VTFL) Pricing Type.

E- Order Date- It is the document date of sales order. 

[jignesh_mehta3]

Hello Durga,

Option B KOMK- PRDST is the pricing date in the Sales orders. But generally this field is available for edit in Sales Order creation and change mode and prone to misuse by end users if you keep this date as Invoice Pricing date.

What is the Business reason for going away from PGI date as Invoice Pricing date? Specially for Taxation determination PGI date is important because Sales Taxes are applied on the date the good leave your factory. For example if the Sales Order is entered today and delivery happens after 60 days, ideally the taxes should be applied as applicable on PGI date.

Once again the basic question remains - is there a strong reasoning for going away from PGI date as Pricing date in Invoice? Also has this been discussed with finance and taxation teams?

Thanks,

Jignesh Mehta

[Former Member]

Jignesh, thanks for the reply.

I understand the tax criteria - will look into that.. 

the business reason is that if there is a price difference between what we quoted the customer based on the pricing date vs. pgi date.. we have a difference in pricing.

Thus, if invoice condition is created based on the pricing date,  we will not have a discrepancy between what we quoted the customer vs. what was invoiced because there was a different condition pricing during PGI.