Update of purchase order based on Pr. Date Cat

[former_member660738]

Hi

We have an issue with updates of Purchase order based on purchasing info record.

When we have two condition PB00:

1.       Price 10 – valid from 13.09.2012 to 15.09.2012

2.       Price 50 – valid from 16.09.2012 to 31.12.9999

At the purchasing info record the Pr. Date Cat is 2 for delivery date

Then a Purchase order is created with delivery date 20.09.2012. The purchase order creation date is 13.09.2012. The net price will be calculated to price 50.

Now we are changing Pr. Date Cat to 1 for purchase order date.

I will expect that when the user press “Update prices” at the condition tab at the purchase order then the price will be 10, because the price will be based on the purchase order creation date.

Please help!

Thanks a lot:-)

[former_member210560]

Dear Sune,

You have to change the field EKPO-PRDATand follow by the "Update" button.

Regards,

ian Wong Loke Foong

[Former Member]

This message was moderated.

[former_member291927]

This message was moderated.

[JL23]

you are missing one point. the price date category is copied over from info record into the PO.

A change of the pricing date category in info record does not effect existing POs

you have to change the price date category in the PO and then carry out a new price determination.

[former_member660738]

Hi

Thanks - in my version of Purchase order I have no price category date field at the PO. However I found it in MEMASSPO, but I could NOT change it. I get meassage:

Change Pr. Date Cat. could not be effected

Message no. ME664

[Former Member]

refer to this thread too http://scn.sap.com/thread/1899838

[JL23]

you can usually only change those fields with MEMASSPO that are enabled in the field selection and can be changed in ME22N as well.

Please go to the following path:

IMG -> Purchasing -> Purchase Order -> Define Screen Layout at Document Level

Select and double click on the ME21n item

in the the Quantity and Price , set the Pricing date control as optional.

see as well this blog:

http://scn.sap.com/community/erp/logistics-mm/blog/2010/02/08/are-you-having-problems-with-fields-th...

[JL23]

you can usually only change those fields with MEMASSPO that are enabled in the field selection and can be changed in ME22N as well.

Please go to the following path:

IMG -> Purchasing -> Purchase Order -> Define Screen Layout at Document Level

Select and double click on the ME21n item

in the the Quantity and Price , set the Pricing date control as optional.

[hannelindbergchristensen]

Hi Jürgen

Do you perhaps know how to carry out the PO condition "Update" using a program ? We have several hundred PO lines to update due to change in the "price date control" from  2 to 1 - it's very time consuming to update line by line. I tried with LSMW- recording using the old transaction ME22, but I didn't succeed

Thanks in advance

[JL23]

No, unfortunatly I dont know from experience what could be done. I would have tried with LSMW as well. Alternative a BAPI.

But as I had never done this myself, I cannot tell you if that will work

[Former Member]

there is an SAP standard functionality to mass update prices. It is found under :

MM > PO > Follow On Functions > Automatic Document Adjustments > MEIx codes

This is response to your inquiry if you are referring to an alternative instead of doing it via ME22n price update button for each individual PO per line item.

Also, watch out for the ff (as far as i can recall, pls confirm your findings too):

1. if there is already a PO history, price update will not work. If you need to make it work, you need to reverse past history (GR and AP) to effect price change on the PO. Even if you do it via MEIx mass update or via me22n price update button, i believe it will have same effect of price not being updated if there is PO history.

2. if PO price (net price) has been manually changed prior to performing this MEIx document adjustment programs. This price update condition will not work anymore.

[hannelindbergchristensen]

I  just found a solution in the LSMW-recording

Thanks for your input.

[hannelindbergchristensen]

I know about the Automatic adjustment functionality but it dosen't work for this kind of change - belive me, we have used several hours playing around with the Tcodes MEIx.

For information, I just found a solution with LSMW-recording using the old Tcode ME22.

Thanks for all your inputs.

[Former Member]

noted. i also had same situation with MEIx tests. I just figured out on how to make it work by ensuring that proper sequence execution and document index refresh.

anyway, good to hear you got a solution via LSMW. do share us the steps and findings for reference.

[shailaja_karne]

Hi Raymar,

I am trying to update PO prices using MEI* T-codes. For some reason not bale to make it work. I would greatly appreciate if you could share the exact steps and sequence of the steps you performed to make this work.

Also, have you noticed any peformance issues with this approach. Does it adversaly affect system performance?

Thanks and regards,

-Shaila

[Former Member]

As far as i know the PO net price does not change once the user updates via condition tab update ONLY IF there is already a past GR / AP invoice on this PO.

PO net price can be changed with the condition tab update if no history.

Even though SAP PO behaves differently on the above two instances i mentioned above, the most important part is really on the price used once you post MIGO and AP invoice.

It's been awhile that i encountered and tested this scenario BUT better if you can also run a test on the following (to confirm).

Test Data (verify and document the EKPO - MEPRF)

1. PO1       Price Cat 1    

2. PO2       Price Cat 2

3. PO3       Price Cat 1 then modify PIR with Price Cat 2, then update PO net price by press cond tab (i know this will update PO net price since there is no PO history)

4. PO4       Price Cat 1 then MIGO then update PO net price by press condition tab  (it will not update PO net price due to PO history)

Test Execution

1. PO creation in reference to PIR

2. MIGO

TEST RESULT

1. verify EKPO-MEPRF

2. verify if PO net price got changed once you press the condition update tab

3. verify the MIGO posted amount (price if it used the PIR price as per validity vis-a-vis price controls)

share the results pls.

[former_member660738]

Hi

many thanks - I have already tried this and it does not work. Still same price when I try to update condition

[Former Member]

ok noted. so same net price on PO when you update condition?

how about when you post the MIGO document ? what was the price as per test scenarios? what was the EKPO-MEPRF indicator?

[former_member660738]

Actually my concern is about the change from Purchase order date and delviery date, so my scenario does not include MIGO. I fully agree that when GR is made no price adjustments must be made, but it is not relevant for my scanario.

[shyam_shinde2]

Hi,

validity dates are relate to system date in purchasing info record,thus change in po creation date,delivery date do not affect on net price appearing.

Regards