Contents Introduction .................................................................................................................................................. 2 Configuration ................................................................................................................................................ 2 System Demo ................................................................................................................................................ 3 Create condition master records with validity periods ............................................................................ 3 Create a contract to demonstrate the functionality of "Pricing date" field ............................................. 4 “Pricing date” in the sales document type Vs. “Pricing date” in the Condition type ................................... 8 Who has priority?...................................................................................................................................... 9 System demo ................................................................................................................................................ 9 Technical details.......................................................................................................................................... 14
Introduction The "Pricing Date" in the sales document is used to determine correct prices (Based on condition master records with validity periods) for the sales order. For example, let's say you adjust prices in the beginning of every year. This year you are going to create a contract for a customer which is valid from next year. Therefore the prices which should appear in the contract have to be next year prices, not this year prices. In such a scenario, "Pricing date" field plays a key role. When you create the pricing condition records in transaction VK11, you have to specify the validity periods. When determining correct prices in the sales order, the pricing date works in conjunction with these validity periods. Let's look at how this works in SAP!
Configuration You can define a default pricing date based on the sales document type in the sales document type customizing. IMG Path:
Go in to relevant sales document type. Let's take contract order type "CQ" as an example Go to "Requested delivery date/pricing date/purchase order date" section You have below options available o BLANK Proposal based on today's date o A Proposal based on requested dlv.date (header) o B Proposal based on valid-from date (header) o C Proposal based on contract start (header/item)
Since we want to propose the pricing date based on the valid from date of the contract, I will put "B" here.
Save your settings
System Demo Create condition master records with validity periods Transaction: VK11
Create 2 condition records with different prices for different validity periods.
As per above condition record, from 01.01.2012 to 31.12.2012, price of the article "AW01" will be 100 USD.
As per above condition record, from 01.01.2013 to 31.12.2013, price of the article "AW01" will be 150 USD.
Save both condition records
Let's create a contract (Order type - "CQ") with different validity periods and see how the "Pricing Date" field determined in the header.
Create a contract to demonstrate the functionality of "Pricing date" field Transaction: VA41 Create a contract with validity periods within 2012. If you go to sales document header / Sales tab, you can see the proposed pricing date in the header as below; As you see below, the "Pricing Date" was determined based on the "Valid From" date of the contract. (Based on sales document type (CQ) customizing)
Now let's add a line item and see how the price is determined.
Price determined as 100, based on the "validity period" of the condition master records and the "pricing date" in the contract.
Now if you change the "valid from date" in the contract to a date in 2013, you should be able to see the "pricing date" also change accordingly.
Now let's add a line item and see how the price is determined.
Price determined as 150 USD, based on the "validity period" of the condition master record and the "pricing date" in the contract.
Please note, the "Pricing date" in the sales document header also get copied to the line item as well. ""Pricing Date" in the line item is available in the "Sales A" tab
“Pricing date” in the sales document type Vs. “Pricing date” in the Condition type Like the “pricing date” field in the Sales document type, you have “pricing date” field in the Condition type customizing as well. IMG Path:
-> Details of the condition type MWST is as follows;
Who has priority? Priority – Condition type customizing has the priority over sales document type customizing
System demo Let’s look at an example to understand the concept of it.
Sales document type is configured as “BLANK – i.e: “Proposal based on today's date” for the pricing date Therefore when creating sales order, system will propose the system date in the header / sales tab as well as Item / Sales A tab Let’s consider our sales document type as “OR” shown below;
Condition type “PR00” and “MWST” are customized with “BLANK – i.e: “Standard (KOMK-PRSDT; tax and rebate KOMK-FBUDA)” for the pricing date -> Therefore when creating a sales order, based on the condition category (Eg: Price or tax) system takes it as follows o
Price condition -> Pricing date - KOMK-PRSDT (i.e. pricing date in the sales order header)
o
Tax condition -> Pricing date - KOMK-FBUDA (Requested delivery date will be taken here)
Let’s take price condition “PR00” and Tax condition “MWST” as an example
Price condition - PR00
Tax condition - MWST
Now let’s create a sales order and see how the “pricing date” in the sales order header and the “pricing date” in the condition records get calculated; Now I will create a sales order with sales document type “OR” with the “Requested delivery Date” 15.08.2012. Please note, today’s date is 10/08/2012
In the sales order header I see the pricing date is set as “10.08.2012”
Same can be seen in the sales order line item / Sales A tab as well
Now let’s look at the pricing date in those two condition types. o Price condition – PR00
System take today’s date as pricing date.
o
Tax condition – MWST
System determined requested delivery date here. As you can clearly see in the above example, when calculating the pricing date in the condition type, system works as per the condition type customizing settings.
Technical details If you want to do any changes with respect to pricing date field, you can do it via below user exit
Field Name: VBKD / PRSDT Include - MV45AFZZ User Exit - FORM USEREXIT_MOVE_FIELD_TO_VBKD
Author: Anupa Wijesinghe E-Mail:
[email protected] /
[email protected] Website: www.learnsaptips.com View my profile in LinkedIn Follow me on Twitter
Disclaimer This article is done based on my research and readings, unless otherwise stated. The views expressed are my own and not of anyone else. Author accepts no liability for the content of the articles in this website or for the consequences of any actions taken on the basis of the information provided. Using this information is at the users own discretion and responsibility.
