Pricing Date determination

2.      is it possible to have a calculation rule for each customer. For example Customer A pricing date based on delivery date; Customer B pricing date based on goods issue I date

Hi,
The pricing date is proposed based on the setting you make in the Sales document configuration. ( T code : VOV8)
You have a field" Prop.f.pricing date " in the Requested delivery date /  pricing date /  purchase order date  segment.
Then you can choose the follwoing options:
Blank - Indicates the current date as the pricing date
A -  Indicates the date based on the requested delivery date
B - Indicates the date based on the order validity start from date
And the pricing in the billing document is copied from thte sales order / Delivery document..
It again depends on the setting u have in the copy control from order - billng or delivery - billing.
In the copy control, in the item settings you have two fields relavant for this.
One is pricing source and the other is pricing type.
The pricing sources are generally the order.   But if you want you can change it to other values mentioned in the drop down,
but this values have no effect if the pricing type is B.
Any other value other than B in the pricing type will take the reference document price mentioned in the pricing source field.
but for the pricing type B.  The new price is determined in the billing order.
Prerequisites
To activate automatic determination of the pricing date or the settlement date, you must make the following settings in Customizing:
Definition of the date rule
When you define the date rule, you specify a sequence of shipping deadlines (for example, end of transportation planning or planned start of loading) which are used to determine the pricing date or the settlement date. The sequence of the deadlines reflects their priority for access. If there is no value for the first deadline, then the next deadline is checked, etc.
You make these settings in Customizing: Logistics Execution ® Transportation ® Shipment Costs ® Basic Shipping Functions ® Define date rules.
Assigning the date rule
In the definition of shipment cost item categories, you can assign a date rule to the pricing date and one to the settlement date.
You make these settings in Customizing: Logistics Execution ® Transportation ® Shipment Costs ® Shipment Cost Document ® Shipment Cost Types and Item cats ® Define item categories.
Regards,
Saju.s

Similar Messages

  • User exit for pricing date determination

    Hi Friends
    I want to have a custom validation at pricing date determination at billing document creation. Please anybody can help me which exit available at VF01 for this purpose.
    Regards,
    Ramindu

    Hello,
    Check for the below link:
    http://help.sap.com/saphelp_46c/helpdata/en/18/f62c7dd435d1118b3f0060b03ca329/content.htm
    Prase

  • DP90 pricing date missing in DMR item data

    Background:  Im implementing sales pricing discounts for sales orders generated from service orders via RRB.  Currently, we create service orders to capture costs then use RRB (DP90/DP95) to create DMR documents to bill customers for the services.  Costs are transferred to DMR as condition types EK01 actual costs.
    Issue:  In DP90/DP95, if I leave the pricing date blank..the DMR creates with a blank item pricing date.  The DMR header pricing date is populated with current date.  Since the item pricing date is blank, the system does not find the discount condition records.
    F1 help on the DP90/DP95 field says "If you want to use the internal date determination facility in SD, leave the field empty."
    If I create the DMR manually in SD, the pricing dates determine correctly...nothing remains blank.  Our SD doc type config uses a "blank" for the pricing determination (current date).
    My concern is that end users will forget to enter the pricing date in DP90/DP95 resulting in the customer being overcharged.  Are we missing config somewhere?  As an alternative, is there a way to make the pricing date on DP90/DP95 a required field? Since this only happens from DP90/DP95...Im trying this forum first. 
    All help is greatly appreciated.
    Allison

    Hi,
    Make it required field on initial screen of DP90 by screen & transaction variant
    T-code SHD0
    Put t-code DP90 and click on tab screen variant and maintain below
    Screen variant       ZDP90
    Program              SAPLVPK_GUI_INTRO
    Screen               300
    Then click on create button then initial screen will appear then click on expenses or sales price then FILED SCREEN will pop up
    Make PRICING DATE as REQUIRED and click on exit & save again save it.
    Come back and click on tab TRANSACTION VARIENT
    Put Transaction Variant - ZDP90 and click on change icon
    put screen variant ZDP90 enter and save
    If you want test is then test by clicking TEST (F8)
    Now assign this transaction varient in SE93
    Put Transaction Code  -  ZDP90 and click on create
    Then enter short text and select option 4 i.e TRANSACTION WITH VARIANT
    Then enter
    Transaction             DP90
    Transaction variant     ZDP90
    And save
    Now instead of DP90 use ZDP90 in this pricing date will appear as required field.
    Kapil

  • Price Determination (Pricing) Date Control - Purchase Order

    Hi,
    We are exploring the Price Determination (Pricing) Date Control in the Purchase Order.
    Clientu2019s requiring  is, correct me if it is a wrong requirement:
    We have created Tax Codes:
    C2 -  CST 2% valid from 01.04.2010
    C3 -  CST 3% valid from 01.04.2010
    We have created a purchase order with Tax Code C2 - CST 2% on 30.03.2010 as we are in doing back log entries. Since the tax code is valid from 01.04.2010 only , the purchase order is not displaying the Tax Code Value .
    Now we are doing the Goods Receipt on 01.04.2010, the system will not pass the entry for the CST as at time of GR, the System picks up the Tax data from the Purchase Order.
    Now we want that the System should pick up the Data at the Goods Receipt, not from the Purchase Order. Some one advised me to use put GR Date in Pr. Date Cat. Under Item-> Condition Control tab. We are able to view the Pr. Date Cat by changing the Screen Layout of ME21N.
    We want to know what use of the same & under what condition is, we use this.
    Our suggestion:
    1. We are of the view that we should create the Tax Codes with Valid Date from 01.01.2010 (not from 01.04.2010 as currently maintained)
    2. Or since we are doing the back log entry, we should create all the Open Purchase Orders dated 01.04.2010.
    Is this the correct way which we are suggesting?
    Please note that we are dealing with Excise Materials also?
    Please guide.

    Thanks for the reply,
    While testing the same, I also encountered the somewhat same problem.
    You are suggesting that we should change the Tax Code Valid From Date.
    What do mean by the follwoing:
    Pricing date category "GR date" can't be set in PO if price is entered manually (with condition type PBXX). This also means manually entered conditions at Po will not be used.
    Regards,

  • Purchase Info Record - Price Determination (Pricing) Date Control

    Dear Guru,
    Can i get some advice here for the "Price Determination (Pricing) Date Control" (Pr. Date. Cat ) setting which is maintain in the Purchase Info Record --> Purchasing Organization Data 1.
    Can anyone advice me on the purpose and where is the configuration?
    Thank You very much,
    Regards,
    Chee Wee

    Hi
    If you maintain Pricing date category in info record then different pricing date can be considered for a certain material supplied by a particular vendor.
    If you maintain in the Vendor master then the same price determination date will be considered for all the vendors materials.
    For example,
    If you want to maintain two pricing for the materials with different periods then you can use the validity periods according to the requirement.
    Validity periods,
    1. 01.11.2010 to 31.12.2010
    2. 01.01.2011 to 31.01.2011
    Regards,
    BK

  • ***Price Determination (Pricing) Date Control

    Hi Experts,
    The client requirement is that it has a contract maintained for different months with different prices. PO is created for a certain date and price. But they want to do the GR with a later date may be after 5 months for the service they have received. They want to post the GR in the open period but the price should be picked up depending on the contract price maintained for that date in past.
    In contract and in Vendor we have a field called Price Determination (Pricing) Date Control which determines which date is to be used for price determination (pricing) purposes.
    My issue is if i use manual which is # 5 in contract and in Vendor still when i do the GR i am getting the price with the present posting date or the present date which has been maintained in the contract. Where should i maintain the manual date on GR so that my contract price gets picked up.
    Thanks for your support.
    Mavrik

    Dear Mavrik,
    The price always follow the date maintained in the price date field in the condition control tab at ME21N during
    creation of the PO. If you want during GR, the price follow a specific date, please kindly check and change
    again the date in the particular PO at the same tab and at the condition tab, click the update button after
    change the date.
    Best Regards,
    Ian Wong Loke Foong

  • Price Determination (Pricing) Date Control in Info Record

    Hi,
    Can anyone help me with the use of
    Price Determination (Pricing) Date Control = 5 GR Date in Purchasing Info Record
    Does this help in the following case
    I have a PO for an year
    Each month vendor delivers @ different amount and it is known only @ the time of delivery(with the bill)
    We are ready to accept the price from vendor
    So if i set Price Determination (Pricing) Date Control = 5 GR Date in Purchasing Info Record
    and change the price in Info Record every time before GRN for that particular date,
    will it pick the new price or the PO price
    We are doing GRN wrt PO.
    Thanks and Regards
    sapmmlearner

    Hi,
    Please Help
    From what Esther posted i think my requirement can be met, but its not working
    My requirement is
    PO : 1000 qty, @ 10 inr per pc, for a year
    first delivery they send 250 @ 10 inr per pc , GRN done wrt PO
    invoice is posted
    @nd delivery say after 4 months
    they send another 250 this time @ 12 inr per pc
    we are accepting the price too , we do GRN wrt PO but 10 inr is adopted
    but we need to do it at 12 inr per pc
    I am asking whethr this can be done by maintaining '5' in price determination date contol in info record and editing the price(earlier it was 10 , now am editing it to 12) each time before GRN, will this price be adopted during GRN.
    (is there any other alternative)
    note: am editing after PO and each time before GRN
    sapmmlearner

  • Pricing Conditions and how the pricing date is determined

    Hi all,
    Small question, i ahve some pricing conditions that use the Serives Rendered date and others that use the Pricing Date from an order, how is the condition decided on what date it uses?
    Hope i have expplained this ok, if not and you need more info let me know.
    Regards
    Steve

    Hi
    There is a difference between Service Rendered Data and Pricing Date.
    Normally Freight Conditions are maintained on Service Rendered Date so the freight will be picked on the basis of date on which the Actual Delivery done, whereas Pricing date is used for other conditions so that price will be based on the date on which the document created and the Pricing Date maintained in that.
    In the same way there is a Billing Date which came in Invoice so price will be based on the date of Invoicing.
    If you maintain the record in VK11 and test a cycle you will be able to find the difference easily.
    Regards
    Amitesh

  • Price Determination (Pricing) Date Control in PO

    Hi,
        We have feature in PO for price date control. Following are available in drop down:
    1. Purchase order date
    2. Delivery Date
    3. Current date
    4. Manual date
    5. GR date
    no control.
    I did F1 to find details how to use this functionality but there is not much explaination to it except with GR control.
    Also below to it there is a field Price Date.
    1.Please explain in which scenarios these all are used and what is the accounting impact of it.
    2. Is there any study material to take deep understanding of this concept.
    Regards

    hi,
    The pricing date is the date defined by date-dependent pricing elements such as conditions and the foreign currency rate.
    As we know that the prices of foreign currency  changes day by day..so if you post your PO today and make IR some other day then there may changes in prices from date to date...
    so this field is used to ref. to date for the price applied...
    can see the link for more details:
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/93/7440fa546011d1a7020000e829fd11/frameset.htm
    hope it helps....
    Regards
    Priyanka.P
    Edited by: Priyanka Paltanwale on Sep 25, 2008 6:24 AM

  • Pricing date and free goods

    Hello Folks,
    My understanding is Free goods is determined basically based on quantity as in quantity ordered.
    The system re-reads free goods condition record in the sales order when quantities of the main item changes or when Pricing Date changes.
    Based on the above, I need to clarify :
    1. If free goods is based on quantity, how does a change in the pricing date affect the determination? I assume the by pricing date change, it is referring to the pricing date setting in a free goods condition record.
    So, I am not sure why pricing date change requires a re-determination of the condition record for free goods.
    Or is it because free goods is determined based on  $ amount of goods ordered?
    Moreover, its said that when Pricing is Re-Run, free goods determination is un-affected.
    Cheers.
    John

    Hi,
    Free goods can be of two types. Inclusive and Exclusive.
    Inclusive discount are always value discount. What I mean is, if you buy 10 qty of an item, say 2 qty is free, then, it means, 20% off on the original price. i.e. only 8 are billed and 2 are discounted from pricing.
    In exclusive free goods, you are shipping 10 qty of an item + 2 qty of the same item in addition to 10. So, 10 are billed.
    When the pricing date in the sales order is changed, how will the system know whether the item being priced on a particular day should allow the free goods or not. So, free goods determination becomes necessary. Hence, it goes thro' free goods determination when you change the pricing date on the sales order.
    Hope this helps.
    Regards,
    Mukund S

  • Service Desk: Pricing data for partner could not be read

    Hi all,
    I am trying to configure the Service Desk functionality for Service Providers (on EHP1).
    I follow the SAP Documentation (SAP Solution Manager: Service Desk for Service Providers) and SLA's made easy in SAP Solution Manager. Also some discussion threads helped me with some steps (I applied e.g. the recommendation from Pricing data for partner 106 could not be read. , but it didn't help).
    I am facing some errors related to the CRM part of the configuration.
    When I create Service Desk Contract (SLFV) in CRMD_ORDER, the error appears Pricing data for partner xxx could not be read. I checked the setting of BP and I am not able to find the reason, for customer's (sold-to-party) BP the sold-to-party > Sales Area Data the Sales Organization/Distribution Channel/Division are maintained. Which information for pricing is needed and where can it be configured?
    Another error - I am sure it is related to the first one - the service contract cannot be determined in the service message (in Item details view under product). The error messages are about sales area/organization, so I suppose there is something wrong with the link Service Contract -> Business Partner definition.
    Could you please help me what can cause the error?
    Thanks in advance,
    Vaclav

    Hi Balaji.S,
    my problem was solved when I double checked the settings of org structure. That means there must be a consistent setting for sales organization / distribution channel / division in businness partner (tcode BP), organizational model (PPOMA_CRM), product workbench (COMMPR01). The setting must be same for both the sales department of the service provider and the customer's company (I am sorry I am not CRM, so I am following just this simple logic)
    In the long text of the error (in CRMD_ORDER) I could see "expected" combination for sales organization / distribution channel / division (message e.g. The access was carried out with sales organization 'O 50000613', distribution channel '01' and division '') -> when the org model was set up everywhere in this way, the contract was automatically filled by the organization data and in the next step the contract could be determined in the service desk message.
    Anyway it took some time to find out the correct combination. Deeper CRM knowledge would help me much.
    Vaclav

  • Sale order date determination

    hi friends,
    kindly explain,how the sale order date is determined.
    on what criteia it is determined?

    Hi Divya,
    Go to TCODE VOV8--in the functionality of sales document go to Requested Delivery date/Pricing Date/Purchase order date.
    in it there is a field called "Propose PO Date".if we chk this the system will take current date as the PO date.
    Rgds,
    Raj..

  • Pricing data for partner 300027 could not be found

    Hi guys,
    We have ECC6 and CRM5,both are IDES.I have fulfilled some exercises on training document,for example,I can create sales order in CRM,then this sales order can be transported into ECC.
    now I want to extend the sales area,so I made these operations:
    1. create sales area Z009/71/71 in ECC
    2. copy this sales area to CRM
    3. extend the sales view(Z009/71/71 ) of BP 300027 in ECC
    4. check this sales view for BP 300027 exists in CRM
    than I create sales order in CRM,I use sales organizaion Z009/71/71,BP 300027,but when I press ENTER,the error occurs.
    Could anybody help me and give me some advices,many thanks!

    Hi Curry
    Shalini has correctly pointed out the essentials required for price determination am using the same below:
    Sales Org...........................Z009
    Distribution Channel............71
    Division..............................71
    Customer Pricing Procedure ( can be seen in the transaction type Customizing)
    Document Pricing procedure.( Can be ssen in the business partner-sales area data)
    You need to check all these perameters, if the correct values are maintained for them. However if you are using your CRM installation for the first time then there is one important thing which you need to check. In the above mentioned essentials the Division plays a major role as dispite of the fact that the sales area is available in CRM system it is important to check if the Division is activated for the Sales Order Header or not. If the division is not activated then even if you maintain all the values system will throw the error that pricing data could not be read for the respective BP.
    Following is the process to check the same and maintain the necessary values:
    1. follow the path IMG -> CRM -> Master Data -> Organization Management -> Division Settings -> Define Use of Division and Dummy Division.
    2. Put a tick mark in the check box Header Div. Act. and save your settings. Now check the transaction again.
    Hope this help.
    Cheers
    Avi

  • Pricing procedure determination in sales order

    Hi Experts,
    In our business scenario, we have three plants and all plants have different pricing procedure. And we are using same sales area and sales document type for all plants.
    Currently one customer is purchasing goods from only one plant. So in our system, pricing procedure determination in sales order based on customer pricing procedure.
    Now as per new requirement, same customer will purchase goods from different plant. And we can’t change or create new sales area and sales document type as per our existing system design.
    So can we change customer pricing procedure at a time of SO creation level? If yes than how?
    Regards,
    Haresh

    Are you a functional or developer?
    Hope are aware that as per SAP standard,  pricing procedure(OVKK) is determined based on
    (1)
    Sales Org
    (2)
    Distribution Channel
    (3)
    Division
    Customer Pricing Procedure
    (5)
    Document Pricing Procedure
    Sales area determined in your sales order or billing doc
    Determines from Sales Data of Customer Master
    Determines from sales(VOV8)/billing(VOFA) doc type
    In addition to that sales order is created for only sales area, which you select based on your customer sales area while creating the sales order.
    Now, keeping above facts in mind, can elaborate your requirement again.
    Thanks, JP

  • Control Sales order Pricing Date with Delivery GI Date

    Is it possible to have a control that ensures the Actual GI date in a delivery is not more than a number of days from the sales order pricing date?

    Hi,
    To have restriction in actual GI date in transaction VL01N . Please find the user exit for VL01N , you can use one which are marked as bold . Kindly take the help of abaper to put the validation or logic as required.
    V02V0001   - Sales area determination for stock transport order 
    V02V0002   - User exit for storage location determination 
    V02V0003   - User exit for gate + matl staging area determination 
    V02V0004   - User Exit for Staging Area Determination (Item) 
    V50PSTAT  - Delivery: Item Status Calculation 
    V50Q0001   - Delivery Monitor: User Exits for Filling Display Fields
    V50R0001    -  Collective processing for delivery creation 
    V50R0002    - Collective processing for delivery creation 
    V50R0004    - Calculation of Stock for POs for Shipping Due Date List
    V50S0001    - User Exits for Delivery Processing 
    V53C0001    - Rough workload calculation in time per item 
    V53C0002    - W&S: RWE enhancement - shipping material type/time slot
    V53W0001   - User exits for creating picking waves 
    VMDE0001  - Shipping Interface: Error Handling - Inbound IDoc 
    VMDE0002  - Shipping Interface: Message PICKSD (Picking, Outbound) 
    VMDE0003  - Shipping Interface: Message SDPICK (Picking, Inbound) 
    VMDE0004  - Shipping Interface: Message SDPACK (Packing, Inbound) 
    Hope this will help you to resolve your issue!!!!
    Regards,
    Krishna O

Maybe you are looking for