Skip to Content
author's profile photo Former Member
Former Member

Invoice price determination based on sales order pricing date

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.

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Best Answer
    Posted on Jul 19, 2016 at 11:13 PM

    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?

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 20, 2016 at 06:39 AM

    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

    Add a comment
    10|10000 characters needed characters exceeded

    • 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.

  • author's profile photo Former Member
    Former Member
    Posted on Jul 20, 2016 at 07:09 AM

    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.






    VF01.PNG (5.2 kB)
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 20, 2016 at 07:14 AM

    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

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.