Pricing date category

Hello coworkers,
Is there anyone use pricing date category 5 in purchase order before?I found when I use this selection, the goods receipt price will incude tax amount together with the goods net price, therefore, the goods cost is containing tax amount. While per accounting report, the tax amount should not be calculated into cost of goods. Can anyone help to put some light on this issue?Thanks a lot
Joanna
MM consultant
E-mail:[email protected]

Hi,
Pricing date category is noting to do with tax calculation. This indicates 5 help to post condition price which is valid on GR date.
Issue could be in Tax code. Check tax code I guess in your case tax type (sales tax) is inventories by key NVV. Or Account key which you have define for tax is inventories.
Thanks
Yogi

Similar Messages

Scheduling agreement pricing date category

Hi
i have a situation where the pricing date category in the additional data tab in scheduling agreement is defaulted to value 5 in display mode while i create a PO for certain vendors.
At first i checked for authorizations,but that wasn't helpful.
The field is in display mode when creating/changing an agreement.
pricing date category wasn't maintained in vendor master or info record for these vendors.
It happens only for certain vendors.
can someone tell me,how this is happening.

Hi,
The field price control cannot be changed for scheduling agreements
with time-dependent conditions, it is always set to '5' (GR date).
The reason is that the delivery from the vendor does not necessarily
cover exactly one scheduling line; in many cases several scheduling
lines with different delivery dates are affected - which delivery date
should the system take in such a situation? In other words: there is
no scheduling line based GR in the SAP system - therefore it does
not make sense to change the field.
Best Regards,
Arminda Jack

Need help in Pricing Date Category in Purchase info Record

Hi Friends,
Need your help to solve the below issue
I had created PO for a material with PO price as Rs 100 /-
The info record price for the material for current period is R150/-. Th pricing Date catergory in Info record is selected as "GR Date"
When I do GR for for today's date , system is still taking the PO price of Rs100/- . System supposed to consider the Info record price for today's date i.e. Rs150/-. But it is not taking Info record price
Could some one help what could be the reason ?
Deva

Dear Deva,
The price determination usually based on the field EKPO-MEPRF
price date category for the PO but not the price date category
in the info record. Please kindly check if you have EKPO-MEPRF = 5.
If you subsequent change the price category at info record, the GR still take
the value from the PO stored at table level.
Best Regards,
Ian Wong

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

HELP!! - Pricing Date Control error

Hello experts,
I have a problem with pricing date control.
I would like to set Pricnig date control=5(GR Date)in Vendor master.
However, if I do so, I get an error in MIGO-GO said"Transaction cannot be posted due to errors in price determination:MSG no. ME573"
I don't have a problem if I set Pricing Date Control anything other than "5".
Where should I customize(IMG) to fix this problem?
This is very important, so I would like to rewards points to those who give me valuable answers.
Thanks in advance,
YO

Hi,
Please check info record Pricing date control and Purchase order Price date control in Item details>more functions
Following will help you tounderstand more on this
In the automatic price determination process, the price can be calculated as at the document date of the PO, or as at another date (such as the current days date, the delivery date, or the goods receipt date). You can specify the date to which the price that is determined relates at the following points:
In the vendor master record, in the Pricing date control field, if you wish to use the same price determination date for all a vendors materials.
In the purchasing info record, in the Pricing date category field, if you wish to use a different pricing date for a certain material supplied by a particular vendor.
The value in the purchasing info record takes precedence over the value in the vendor master record.
In the purchase order, in the Pricing date category field (found via Item > More functions> Additional data).
The value from the info or vendor master record is preset when a purchase order is created. However, this is only used if you change it in the purchase order and carry out a new price determination process.
The pricing date category in the PO takes precedence.
Example:
In the info record, you have specified that the price determination process is to be carried out with the conditions that are valid on the delivery date (pricing date category 2). Furthermore, you have created two validity periods (from 04. 01.1997 until 04. 31.1997 and from 05. 01.1997 until 12. 31.1997), each with different conditions.
You create a purchase order with the delivery date 05.05.1997. The pricing date category from the info record is adopted. In the course of the price determination process, the info record conditions from the validity period 05. 01.1997 until 12. 31.1997 are then adopted.
If you wish to adopt the info record conditions from the first validity period in the purchase order, you must change the pricing date category in the PO to blank and carry out a new price determination process.
Hope this will help to resolve your issue
BR
Diwakar
reward if useful

Pricing date catefory

tcode me21n
item detail level tab condition control
i am unable to find pricing date category field here
only 2 options are coming
1>estimated price
2> print price
i have even marked the field price date category as required for the field selction key NBF and ME21N in po backend
can anyone please give me the required settings to get price date category field in po

Hi.
Recently I got the same problem.
I solved it as follow:
Due to Field selection KEy must be homogenous in order to fields works as we need, is necessary you maintain
AKTH, AKTV, ME21N, ME22, NBF and PT0F .
If one of them are not checked box for the field pricing date control, this one will not appear in tab condition control of your PO.
I know is too late, but I'm new member.
Best Regards.
Juan B.

No Control / Manual in Pricing Date Control/Category?

Hi Experts,
There're 5 options in the pricing date control in the PIR (Purchase info record),
How does the "No Control"(Blank) and the "Manual"(4) work?
The system's default option is the Blank.
Thanks,
John.Z

Ramesh Babu Nagarajan wrote:
In case of blank - pricing will be always as that of posting date in the GR transaction.
>
> In case of "Manual" - you can provide a pricing date manually during GR transaction.
Thanks for the reply.
As I tested, "No control"(Blank) the pricing date is the PO document date.
And as the option "Manual", I find nowhere to maintain or change the pricing date.

Free goods condition is not deleted when pricing date changes

Hi experts,
we want to use the free goods condition type 'NA00' / 'NRAB' with category '3' (inclusive rebate). The condition records are valid a certain period ( 1 month e.g.).
The system inserts the condtion 'NRAB' in the calculation scheme and calculates the rebate. So far, so good.
The problem begins, when you change the pricing date into a date when no condition record is valid.
The system should remove the rebate.
But it does not.
The rebate is still there. Wen you change the standard customizing of condition type ''NRAB' you can delete the condition line.
any ideas?
SAP-Mistake?

Hi Bernhard,
You are changing teh pricing date but as per y understanding th condition record consider the "Serv.rendered date".
Better go to Condition tab page --> Click at "Analysis" tab --> on next screen you can find there are so many condition type on your left side --> select your rebate condition type --> once you open the tree of condition type --> sysytem will show the detail on right hand side
See the details that system consider which date "Pricing date" or "Serv.rendered date".
Hope this helps.
Regards,
MT

Can we change pricing date for line item in billing

Hi Expert,
Can we change pricing date , while raising inoice for particular line iteam

Hi,
We can not change the pricing date for perticular line item at billing document level, the only option is we can enter the required date at the time of invoice creation in VF01 screen.
If your requirement is copying the same pricing date that is entered at sales order, then do the following.
Go to T Code:VTFL and choose your DElivery Type and Billing Type, then choose your item category and then change the pricing type as 'D' .
Regards,
Pasapula.

Pass pricing date to advanced pricing

Hi ,
What would i need to do to send a date which is passed as part of configuration to be the pricing date which is used by advanced pricing. For e.g. if the date is in past customer would be charged at a different price which was prevaliing at that time.
Thanks
Arun

Dear venkat
Go to VTFL, select your billing type and delivery type and click on "Item". There select your item category and click on magnifying lens on top so that you will be taken to a screen where there is a field "PricingExchRate type". Maintain "C" there and save.
thanks
G. Lakshmipathi

Customize ALE PO change to let SO pricing date the same

HI all,
Our customers use ALE change their Purchase Order(PO) to us. Then, by means of ALE, our Sales Order(SO) changed accordingly.
According to system standard,Sales Order(SO) pricing date would be modified to present date. But in our industry scenario, pricing date is unchangeable once the Sales Order(SO) has been created.
I have experimented on function module(use [se37]) EXIT_SAPLVEDB_007 and confirmed that this could intervene to let SO item's pricing date stay the same.
However, something odd happened. In my experiment, only SO with one item can let pricing date unchanged; in other case where SO is with multiple items still changed. And SO header is still changed as well.
Any help would be appreciated.
JayChan

Hi Experts,
I am passing the required structure as below .
CALL FUNCTION 'BAPI_PO_CHANGE'
EXPORTING
    purchaseorder = v_po
TABLES
    return        = lt_return
    poitem        = lt_poitem
    poitemx       = lt_poitemx
    polimits      = lt_polimits
    poaccount     = lt_poaccount
    poaccountx    = lt_poaccountx
    POSRVACCESSVALUES = lt_POSRVACCESSVALUES
    POCONTRACTLIMITS = lt_POCONTRACTLIMITS
    POSERVICES    = lt_POSERVICES.
Now i am getting a message below messages from BAPI :
S     06     023     Indirect PO (ZSTA) 4506000481 changed
I     ME     664     Change Item Category could not be effected
I     ME     664     Change Item Category could not be effected
I can see that the PO is not got updated with any of values.Please help me to resolve this issue.
Thanks
PRavee.

Invoice pricing date

Hi my clint requirement is.
Present the pricing date flowing to the invoice PGI date as invoice pricing date. Now our requirement is sales order pricing date we need in invoice pricing date. How we con configure this?
I have one doubt As per our standard SAP invoice pricing date is delivery PGI date or sales order pricing date?
Thanks

Dear YS Rao
As you would be aware, in sale order both at header level and item level, you can see the field Pricing Date. In normal circumstances, both these fields will be the date on which you create sale order.
Meanwhile, based on the copy control in VTFL, the pricing in billing will flow. For your item category in VTFL, for the field Pricing Type, if you maintain other than B, the pricing conditions will be considered from sale order. If you maintain B, then system will consider from VK11 in billing.
thanks
G. Lakshmipathi

Price date category in PIR

Hi gurus,
Could you please let me know the significance of price date category: current date
what is meant by current date, is it the date of posting of GR or IR
If it is the date of GR then what is diff between Price date category GR date and current date

Hi
price date category: Determines which date is to be used for price determination (pricing) purposes.
If you choose the date of goods receipt, for example, a new price will be determined upon the arrival of the goods, causing the item to be revaluated at this time.
current date; this is the date when tou are creating documant.
GR date : this is the date when your are receiving the goods

Pricing date problem

I found price in sales order and its billing document was different. After checking i came to know the reason is pricing date of sales order is different from billing date of billing document, and we changed price between price date and billing date.
so experts please tell me is it possible to keep price in billing doc same as its sales order? What kind of configuration we need to do for this.

Dear SD,
1)Do you mean to say that doc pricing procedure of billing and sales order is same? that is the reason it is comming like this
As, you have already explained that in T. Code: OVKK; Pricing Procedure could be assigned, based upon:
sales area+doc pri proc+cust pricing proc+pricing pro+cond type
Now, If you have different Doc. pric. procedure (under Tab: Account Assignment/Pricing) for Sales Order (VOV8) and Billing Doc. (VOFA); you can maintain different Pricing Procedure, respectively.
I want to restrict to a particular sales area this kind of setting, i dont want this to effect other documents even though the same item category is used. is there any settings available other than routines.
To do So, configure a Z-Delivery Type (OVLK) and Z-Billing Type (VOFA) and attach both (Z-Delivery and Z-Billing) to Z-Sales Order (VOV8) under Tab: Billing --> Field: Order-rel.bill.type
Also, under VOV8 --> Z-Sales Order --> Tab: Shipping -> Field: delivery Type; assign the same Z-Delivery.
Now,
Path: SPRO --> IMG --> Sales and Distribution --> Sales --> Sales Document --> Sales Document Header --> Assign Sales Area to Sales Document Type --> Assign sales order types permitted for sales areas
Here, maintain entry for required Sales Area and Z-Sales Documents (Sales Order, Delivery, Billing)
Also,
Path: SPRO --> IMG --> Sales and Distribution --> Sales --> Sales Document --> Sales Document Item --> Assign Item Categories
assign your Item Category (s) to your Z-Sales Order.
Finally, In T. Code: VTFL
Maintain Copy Control Settings between Z-Delivery and Z-Billing and for your item Category, set Pricing Type as "G- Copy pricing elements unchanged and redetermine taxes"
This will restrict Price change setting (as reqd.) to a particular sales area.
3)one more question . in ovkk we have condition type field. what is the actual use of this ,plese tell me business example if possible.
The use of this field is to enter Condition Type (for Pricing Procedure that is assigned to the combination), the system automatically proposes in the double-line entry screen during sales document processing.
(I will explain this point with suitable example, later-on)
Best Regards,
Amit

Pricing date category

Similar Messages

Maybe you are looking for