Price determination after historical simulation

I am confused about price determination after value at risk historical simulation run, my evaluation day is 2014.March.31, for commodity forward, the floating leg is based on price 42.17286 (the eighth shift for VaR calculation, my holding period is 10 days), which is shown in the attached picture, but my commodity price curve is showing 41.***,if I click "commodity price" under calcuation basis tab, it shows in March.31.2014, my commodity price is 41.57 USD. thus I will like to know how 42.17286 derived, is it from commodity price curve or commodity price? at which point of time? and the difference between commodity price curve and commodity price, if in March.26 , commodity price curve show 42.68, but commodity price shows 41.57, is it inconsistent?

hi,
it s really interesting issue!
this may not be the right solution but i ve tried and it worked right.
1-go to ME12 click the conditions tab on header line.
2-click the scales and click the details for scale type and choose "B" "last scale" for the scale type.
save and exit..
you ll be able to do PO-migo-and miro.
i hope it ll help.
regards.

Similar Messages

New price det. after changing INCO2 in orders

Hi experts,
After changing INCO2 in an ordrer, the system automatically makes a new price determinatión for freight conditions ( Tipe F ).
But in my case, when you change INCO2, the system deletes type B conditions.
1: Is it possible to avoidthis price determination after modifying INCOs?
2: Is it possible to avoid deletion of type B conditions after modifying INCOs?
Thanks

Re: New price det. after changing INCO2 in orders
Posted: Oct 2, 2009 1:34 PM in response to: Jordi Morros Reply
1: Is it possible to avoidthis price determination after modifying INCOs?
If the freight is based on INCO2, then it will change. To check this, go to VK12, key in the freight condition type and execute. Check for what combination, the freight is maintained. If you wish to change this combination, go to V/06, select this freight condition type and execute. There on top right check what access sequence is assigned. Next go to V/07, select this access sequence and include the table whichever combination you want by pressing F4 button.
The conditions that disappear are not based on INCO2, and have no access sequence.
2: Is it possible to avoid deletion of type B conditions after modifying INCOs?
In normal circumstances, no condition type will be deleted once some condition type is modified. Check in debug mode whether any user exit is applied
I'll debug.
thanks
G. Lakshmipathi

How the Purchase Price determination process works in sap-mm?

Hi,
Can anybody tell in detail or have step by step document on Purchase Price determination process?
Thanks,
Pradip

Hi,
You can go for pricing manually or automatic. If you need pricing automatic you have to go for use of Access Sequences and Schema Group of Vendor. You can customize your pricing procedure according to your requirement such as like Domestic, Import and Stock transport.
For the above individually you have to configure Pricing Procedure and the following steps are:
SPRO->MM->Purchasing->Conditions->Define Price determination process
1. Define Condition Table:
2.Define Access Sequence,
3.Define Condition Type,
4.Define Calculating Schema,
5.Assign Calculation Schema, Access Sequence and Condition Type,
6.Define Schema Group Of Vendor,
7. Define Schema Group Of Purchasing Organization,
8.Assign Schema Group Of Vendor to Purchasing Organization,
9.Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organization and Calculation Schema.
10. Assign Vendor to Schema Group of Vendor (XK02)
11.Maintain Condition record (MEK1)
after above steps, you can go for create PO in ME21N.
In the case of Import PO, you have to activate Import PO.
SPRO->Materials Management -> Purchasing -> Foreign Trade/Customs ->Control Foreign Trade Data in MM and SD Documents -
Regards,
Biju K

Using formula in price determination process for PO

Hi, dear experts,
I would like to define some conditions types for purchasing orders that allow me to calculate an insurance amount using the formula:
Insurance = [CF)((C+F)10%)]T
Where: C is the Gross price, F is the Freight and T is a factor that the user has to input
For that, I define a condition type for gross price, for the freight and for the T value
How can I have to define a condition type to do this operation?
On the other hand, the freight is a percentage of the gross price, but for this operation I need the amount, how can I make reference to this amount? (Result of gross price * freight (%))
Also, there is a link where can I find information regarding the price determination process?
Thanks in advance,
Mairo.

Hi,
You can store (surely you have them in data) the data for C and F in values that you can config in pricing procedure in the field 'SubTo'. After, you can obtain the amount with a formula VOFM and set it in M/08 in field 'AltCTy'. You can check this links to know how to do it:
http://saptechsolutions.com/pdf/InsideVOFM.pdf
http://saptechsolutions.com/pdf/VOFMFormulaRoutines.pdf (althouth it's for SD, pricing procedure in SD (tcode V/08) and in MM (M/08) are the same.
I hope this helps you.
Regards,
Eduardo

Transaction cannot be posted due to errors in price determination - MIGO

Hi,
I have made PO with reference to the contract. While posting the MIGO error message displays as "Transaction cannot be posted due to errors in price determination. But with same combination ( Materials and Vendor which were used in Po from Contarct) was used to prepare a PO with out any reference, subsequent MIGO transaction was saved without any error msg. This problem is happening the MIGO through PO reference of Contract or MIGO for schedule line agreement. So your help pls.
Veera.

hi
u have to check Note 1059878 - Error after the Note 1043857
Summary
Symptom
1.When you try to post a goods receipt (MB01/MIGO) against the purchase order, you get an error ME 573 "Transaction cannot be posted due to errors in price determination". This is caused by the code from the Note 1043857.
2.Also,when you have note 1043857 implemented and then try to do a price comparison (ME49)among the RFQ,you see the message 06 616 'selected quotations not directly comparable'.This is again caused by the code from the Note 1043857
Other terms
UNICODE, GTKOMK-KEY_UC, GTKOMK, MIGO, ME49,Price comparison, 06 616, ME 573
Reason and Prerequisites
This happens after the code from the Note 1043857.
Solution
Please apply the code correction below.
regards
KI

Modify consignment stock price determination

Hello,
We have a vendor consignment stock that must be evaluated with the current price at the reception of the goods in the system, not the price at the date of transfer to own stock or consumption.
Weu2019ve been advised that in standard SAP system this is not possible.
The requirement is to change the price determination at TCode MB1B when the liability is created.
Iu2019ve tried a user exit from MB1B, but I was only able to modify the value at the material document generated and not the accounting documents.
Is there a user exit or any other suggestion to achieve this?
Thank you,
Edited by: tania_ztrn on Jun 15, 2011 3:08 PM

Hi,
It's not clear to me why you are talking about special procurement key and stock determination togehter.
In SPRO > MM > IM > Stock Determination > Define Startegies for stockDetermiantion
Here you have to maintain a stock determiantion group, rule and plant / group / rule combination as well as a stock determiantion table.
In SPRO > MM > IM > Stock Determination > Assign SDR in the Applications
- IM > assign the rule to mvt 261
- Production order > assign it to the proper plant/order type combination
In MM02 > Plant data view 2 > assign the stock determiantion group to the amterial master under proper plant/sloc comination.
After these settings it should work.
Regards,
Csaba

Price determination from purchase info with scale

Hello.
I have a problem on price determination result of SAP.
I am trying to set up purchase price determinaton as below;
[ Purchase Info Condition record ]
   item: A
scale
       0 kg          1000 yen
     20 kg            900 yen
[ Purchase Order ]
    item     matnr       quantity           price
     10       A                90 Kg             900 yen
      20      A                10 Kg           1000 yen
item 10 and 20 have same material number.
Entering line one by one, at that time, price is as above I expected.
but after pushing final check button or save button,
price changed like below,
    item     matnr       quantity           price
     10       A                90 Kg             900 yen
      20      A                10 Kg             900 yen
I expected item 20's price is 1000yen , but final check just before save
document, item 20 price changed to 900 yen.
Maybe because of total quantity exceeds threshold of 20kg.
Are there any way to change this behavior?
PS. incase of Sales order, different from Purchase order, the result is
item 10 is 900 yen and item 20 is 1000 yen.
Thank you for any help.

hi,
it s really interesting issue!
this may not be the right solution but i ve tried and it worked right.
1-go to ME12 click the conditions tab on header line.
2-click the scales and click the details for scale type and choose "B" "last scale" for the scale type.
save and exit..
you ll be able to do PO-migo-and miro.
i hope it ll help.
regards.

Price determination 2 and S -- No material selected for CKMLCP

Dear all,
We have a case here that raw materials have price determination 2V, semi-finished and finished goods are 2S.
The MM period is now 2011/07. We tried to run CKMLCP for 2011/06 and system reponded "C+114 list contains no items".
I have searched forum and SAP OSS. What I found is CKMLCP will not process for 2V. How about 2S? Should I change all the settings to 3S instead?
Please let me know if you have faced the same issue before and how you solved it.
Thanks~
Best regards,
Sharon Chen

Hi,
The materials 2S (price determination 2, price control S)
will NOT be selected for the actual price determination in CKMLCP.
In Material Ledger you may use materials with price determination 2,
price control V or materials with price determination 3,
price control S. In the first case (2V), actual price will be calculated
after each material movement, while in the second case (3S), actual
price will be calculated with the cockpit (CKMLCP) at the end of the
period. Only in this case, price differences are rolled-up to finished
materials when multi-level price determination is run.
Regarding to your problem with transaction CKMM, please keep in mind
that CKMM was created to maintain the Price determination control field and
not the price control only. The reason is a design issue.
If you want to change the material from 2S to 2V you can overcome the
change in two steps:
1- change 2S to 3S and
2- afterwards 3S to 2V
or you can also use transaction MM02 to change the price control from
S to V.
Please check the notes about transaction CKMM which provide very useful information:
703604 CKMM: When to change price determination '2' to '3'
384553 Data inconsistencies after CKMM
Best regards,
MLM

Condition Types in Price Determination Process

Hi
Can any one explain me about in Detail about the VARIOUS TABS that work in the CONDITION TYPE of PRICE DETERMINATION PROCESS
Thanks & Regards,
Senmani.

hi
hi
control data 1 :
Condition Class is a grouping that lets you control each condition type differently.
For example, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.
Condition category (examples: tax, freight, price, cost)
A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).
Condition category basically identifies the type pf cost the Condition type is being used for & can be used for .
Calculation type
Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.
The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record
Rounding rule
The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
Example
In the standard rounding rule '_', values are rounded off according to business standards:
10.454 -> 10.45 DEM
10.455 -> 10.46 DEM
In rounding rule 'A', values are always rounded up:
10.459 -> 10.46 DEM
10.451 -> 10.46 DEM
In rounding rule 'B', values are always rounded down:
1045.9 -> 1045 LIT
1045.1 -> 1045 LIT
In this example, the currency of the condition rate is Italian Lira. The Italian Lira does not have any places after the point.
Structure condition
controls whether the condition type should be a duplicated condition or a cumulated condition.
This control is only helpful when you use bill of materials or configurable materials.
Aduplicated condition is duplicated into all assigned items.
A cumulated condition contains the net value of all assigned items.
control data 2 :
promotions
Specifies that the condition type in question is only valid for Promotions.
Use
Conditions for which this indicator has been set can only be maintained via the 'Promotion' menu - not via the Purchasing menu.
Accrual (e.g. Freight)
Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.
Use
If you mark this indicator, the condition appears in the document as a statistical condition.
Before Release 4.0 variant conditions (VA00) had to be created with the condition category 'O'
Problem: It was not possible to indicate a 'Variant condition' at the same time as 'Internal costing condition' and 'Freight'.
Solution: For this reason more indicators are being set up in 4.0 for the condition type:
'Variant condition' (KVARC)
'Internal costing condition' (KFKIV)
The characteristic values O and I for the condition category must no longer be used.
For more information, see the note 93426.
inv.list condi
Condition for invoice list
Marks the condition type as relevant for internal costing.
Quantity conversion
This field controls the quantity conversion during determination of the condition basis.
The field is only relevant for calculation rule 'C' (quantity- dependent.
It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).
Deactivated: The condition basis quantity is converted via the quantity to the stockkeeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.
Rounding errors can occur during quantity conversion.
Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.
Condition for inter-company billing
Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
Problem: It was not possible to indicate 'Freight condition' at the same time as 'Internal costing condition' and 'Variant condition'.
Solution: Therefore a new indicator 'Internal costing condition' (KFKIV) has been set up. You can use this to indicate a freight condition as an internal costing condition. For more information, see note 93426.
Scale :
Scale basis indicator
Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume
Checking rule for scale rates
Indicates whether the scale rates must be entered in ascending or descending order.
Scale Type
Indicator that controls the validity of the scale value or percentage:
From a certain quantity or value (base scale)
Up to a certain quantity or value (to-scale)
Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
Formula for scale base value
Formula for determining the scale base value.
Use
You can use this formula to specify calculation methods that are not provided in the standard system.
reward points if helpful
thanks and regards
ravikant dewangan

***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

Purchase order price determination

Hi Gurus.
Please help on below Inquiries
In Purchase order, how is the net price determined?
Is it from the agreement? the info record? RFQ? Is there a sequence for this?
If there is, where is this configured?
Thanks!

Hi,
Purchase order price determination takes place with help of Access Sequences and Schema Group of Vendor.
You can go for pricing manually or automatic. If you need pricing automatic you have to go for use of Access Sequences and Schema Group of Vendor. You can customize your pricing procedure according to your requirement such as like Domestic, Import and Stock transport.
For the above individually you have to configure Pricing Procedure and the following steps are:
SPRO->MM->Purchasing->Conditions->Define Price determination process
1. Define Condition Table:
2.Define Access Sequence,
3.Define Condition Type,
4.Define Calculating Schema,
5.Assign Calculation Schema, Access Sequence and Condition Type,
6.Define Schema Group Of Vendor,
7. Define Schema Group Of Purchasing Organization,
8.Assign Schema Group Of Vendor to Purchasing Organization,
9.Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organization and Calculation Schema.
10. Assign Vendor to Schema Group of Vendor (XK02)
11.Maintain Condition record (MEK1)
after above steps, you can go for create PO in ME21N.
In the case of Import PO, you have to activate Import PO.
SPRO->Materials Management -> Purchasing -> Foreign Trade/Customs ->Control Foreign Trade Data in MM and SD Documents ->>>>>>
Regards,
Biju K

Material ledger Price determination change

For the FERT materials - we have material ledger active, price determination 2 and price control S setup as of now. We have the standard cost for the group and Moving average is calculated for information purposes - now we want the moving average to be periodic.
I changed the price determiation from 2 to 3 in ML activation but had no impact.
My questions are:
1. Should we do this at the material level - so that moving avg does not get updated for each transaction and instead by period.
2. what are the steps/tcodes to be taken before and after changing the price determination. I understand we need to run ckmlcp - but need clarity on all the steps I have to do both from config and master data perspective.
3. Test script steps

Hi!
A+ 1st point. Other decision is when you do MMPV.
B+ I think its better do MMPV on 01/may before do CKMM, so in point iii, you close of April. If you do CKMM with MMPV active period April, ML will be active for March and April. Again this is just a personal point of view.
C+ Well, the procedure is correct, Keep in mind the following: The system consider in your scenario S2 > S3 as Actual Cost of April the value in the standard at the moment of CKMM, so the flow:
> CKMM > Release Standard> At the release, system create a price diff (UMB), that is part of your actual cost (initial of may). The value is the diff of your previews and new standard.
In the ML Close of april, UMB of MAY will be cleared and converted in PRY/PRV. If you want details of this, check Standard Cost Release with ML Active.
Its important you validate it, because if the system dont select this materials, UMB $$ will be part of your P&L account.
In the ML close of May, this value will be consider part of the actual of May.
D+ What will happen if the run (iii) above after point (i ) will the ML revaluation will have impact on the material changes to 3S.
The ML close of april have impact if you post (GM, IR, Settlement) for this materials on April. If this materials are produced, its common that you do the settlement of its order the 1 or 2nd day of may with posting date of april, but as i toldyou is a common procedure.
E+ Just thinking, Its a good idea you do the ML close for this materials in April (status set to 70)
If for any reason your ML close dont select them there are some workaround eg check this oss 1602599 - Additional selection options for selection
PS1. Wish this give you more ideas. This topic is interesting and difficult to explain, because have some `depends on`. Again, i recomend you test in your QAS system!
PS2. This post maybe give you other ideas Material Ledger Activation - Lot of Questions in startup.
Arturo.

Price determination as per delivery date

Hi All,
I have created a PO in which the PO is picking up the dalivery date as the current date. when i change the delivery date as some other date there is a message saying Delivery date changed (new price determination process may be necessary).. I worked with my ABAP guy and solved this problem and now the PO is not picking the current date.
Now, the user wants me to configure how to determine the Price for different delvery dates.
That is if i change the delivery date to some other how to check if the PO is picking the price determined by that delivery date.
I checked the info record and the validity date is 12/31/9999. and this is the message iam getting
Delivery date changed (new price determination process may be necessary)
Message no. 06484
Diagnosis
If the price determination date is the delivery date and other conditions are valid on the new delivery date than those that are valid on the old one, the price is no longer valid.
Procedure
If this is the case, and you wish to see the price that is valid as at the delivery date, carry out a new price determination process.
And u said to define on the basis of which Date of Price Determination system should select the price. where can i define the price determination for delivery date. This is the first time iam working on such issue of price determination.
Thanks,
Sameer

Dear Sameer
There is no relevance of pricing date with delivery date. For information, while creating sale order in VA01 after giving your sales area and execute, there is a field "Pricing Date" in Sales tab and the date will flow into this field by default the date on which you are creating sale order.
So irrespective of your delivery, your invoice pricing will be effective based on this field. Unless you change the date here, your pricing condition will not change, if you have a different pricing in VK11. Of course, you can also change the pricing date at item level for which click on "Goto -- Item -- Sales A".
thanks
G. Lakshmipathi

MIGO : Price determination

Hi all,
I got a problem when I try to do the good receipt for a purchse order in MIGO. SAP occures an error :
"Transaction cannot be posted due to errors in price determination
[X]Error during maint. of delivery costs in master conditions
Delivery cost conditions in different validity periods not identical "
What does it mean ? Where can I find the place where those validity periods are customized ?
I've already checked in the RFQ, and the period value of the delivery cost condition seems to be OK for all the costs...
Someone got another idea ?
Thanks all !

Hi Prasad,
Indeed this PO already has a GR, but this GR was cancelled.
Now when we try to do again the GR, we get that error.
But I check the PO and the delivery costs are still here. If I erase the delivery cost from the PO, I can do the GR. If I put back manually the delivery costs, I get the error during the GR.
So, do you have a solution ?
Thanks,
Mathieu

Price determination after historical simulation

Similar Messages

Maybe you are looking for