Cost price determining wrongly

Dear all,
I have one issue.
I have created one service order In which one component is issued.
The problem is that at the time of creation of DMR The Actual Costs(EK01) of the component is determining wroungly.
Say actual cost of the component is 1Rs But it is determining 10Rs.
No manual changes happened at the time of DMR.
Please suggest for the above issue.
Thanks.

I got the solution

Similar Messages

Wrong cost price in good receipt

Hello,
I try to to make good receipt, but when the document is done, there is wrong cost price. I tried to set various properties but I haven't found any solution.
Price and PriceAfterVat is Ok, only Cost Price is wrong.
Is there any way how, can I set the Cost Price, or how it is being calculated by the SBO ?
Thanks
Peter Bordac

HI,
way to modify the price of a material in the good receipt without a purchase order?
I am not sure what you want price of goods receipt means material price
try following
MR21 and change material price
Regards
Kailas Ugale

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

Updating the Price Determination Field in the Material Master (MBEW-MLAST)

I'm doing a material conversion into an existing SAP system and the program to load the materials didn't load a value in the price determination field (MBEW-MLAST). Normally this field is required but because the conversion BAPI doesn't do as much validation as MM01 it was possible to create the record without a value. The field is not open to input when I use MM02, and even though it appears to work, when I do MM17 mass change the field is also not updated. Finally I tried transaction CKMM - Change Material Price Determination for Material Ledger but it required an entry in the Old Price Determination field and it won't let me enter blank.
We've since corrected the program but my problem is that I've converted about 5000 materials without a value in the field meaning the FI guys can't release cost estimates which is causing a bunch of problems for the testing that we want to do in this system. We've taken about 3 weeks to do this conversion so going back and doing it again is a terrible option. Does anybody know a way to get a value into this field other than what I've mentioned above (MM02, MM17, CKMM)?
Suggestions please.

have a look into OSS Note 1491364 - BAdI CKML_SET_VPRSV: Price determination cannot be changed

VPRS - Cost price from sales to billing not valuation record

Hi,
I need to get the cost to flow from the sales document to the billing document for the cost price.
We allow selected users to change the cost price at the time of the sales order. But when I create a billing document the moving average price is determined and not the cost price on the sales order.
In copy control pricing is 'G' and price source is order.
Is there a way around this via configuration ?

Dear Javaid
Can you confirm that the sale order quantity and the billing quantity are same. In most of the cases, these would be different and hence the cost also.
Meanwhile, in V/06, for this condition type VPRS, ensure that the Calculation Type is "C"
thanks
G. Lakshmipathi

Cost price in migo

Hi,
We have mapped a specific scenario where stock transfer process are happening between mfg
plants to sales plants where billing price (STO price) are plant and material specific.
I made the price determination at delivery level by assigning the pricing procedure
with "NL" delivery type which is working as per the previouns requirement.
Now clients wants that material cost of MFG plant which is "S" should be update at
receiving plant with "S"freightother charges.Receiving plant price control is "V".
for example :
M1 material at mfg plant VPRS price "S" is - Rs 130.95 per sqm
M1 material at receiving plant vprs price "V" should be update at the time of
MIGO Rs 130.955025=Rs 205.95 per sqm, we are doing MIGO with ref to delivery not to PO.
I want to know is it possible through standard SAP by adding new condition types in PO
pricing procedure? Plz advice how to do this.
Regards,
SPS

Dear friend,
In your scenario, based on your requirement - you can create your own calculation Schema(pricing procedure), which is nothing but a parametric releationn between the condition types.
The condition types can also be created in respect to your needs.
In your case, you're referring th delivery(OBD) for MIGO, which in turn already teh OBD id referred to the STO (PO). Hence the Purchase price will get updated from the PO.
Also, based on your MMR (Material Master record) price control, the price will get updated in respect to the Stock Values.
You can define your calculation schema/Pricing procedure thru M/08, and teh condition types can be creatd thru M/06.
Hope this helps.
Njpy SAP
-Saravanaganesh

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,

Cost/Price diffrences posting (PRD)

Dear ALL,
I am facing the issue in (PRD)Cost price diffrence account postings.
In Article Master (Retail) using Moving avg price while doing GR price diffrence posting to PRD account due to negative stock indicator in Article master.
Ex : In Article master having negative quantity 1 at MAP 10.
Now i am procurring 2 qty at MAP 20 with purchase record. while doing GR for the qty 2 system calculating for 1 qty at 20 and 1 qty calculating 10 at old MAP diffrence 10 rupees posting to PRD account .
This is wrong this needs to go Inventory but it is going to PRD, please let me know how to avoid this with out unchecking negtive qty in Article master.
Please respond
Cheer's
Ram
Edited by: Ram on Mar 19, 2010 11:02 AM
Edited by: Ram on Mar 19, 2010 11:07 AM
Edited by: Ram on Mar 24, 2010 4:39 PM

Hi,
Check your settings in OBYC.
Regards,
Mohan.

Cost price in TTPO flow

hello,
in our TPPO flow (sales order - purchase requistion - purchase order - invoice on purchase order - SD invoice to customer), we seem to have a problem with the cost price.
in the sales order, a cost price is correctly determined
price in the purchase order correctly determined.
But once the incoming invoice is posted, the cost price in the outgoing invoice has the purchase VAT value added to it. It should take the net price here.
Anybody any idea where this is triggered?
kr
NIco

Can you check whether OSS Note 988692 - VPRS incorrect in third-party order processing and cross-co helps you?
Regards,

Price control V and price determination 3

In the material master record 'price control is given as V and price determination indicator as 3 . With this combination , in the sale order pricing, which price would be picked up by VPRS condition ? Material ledger is activated for this material .
Regards
Mahesh .

hi,
For Make to order scenerio, the price of finished goods will be Standard price ' s'. for Raw material it will be Moving average price"v".
For VPRS condition it will take Standard price of product.
if ur using with Quantity structure, then the price of Raw material in BOM and routing will be shown in ck11n.
Better to take EK02 Condition in pricing procedure with maitaining Requirement class and type.
It will automatically show the price of finished product when u click on cost calculation tab in sales order.
Regards,
Sreekanth Munipally

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

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.

Error: Transaction cannot be posted due to errors in price determination

Hi,
I am facing below error when i try to post GR for a SA. I checked out all the configurations, these worked on GR for PO but not on SA.
I have seen other posts which recommend to view OSS note 447374 and 446831. I am not sure where to find these and how to use these notes.
Please help!.
Thanks
Ramya

Here you go
Transaction cannot be posted due to errors in price determination
Message no. ME573
Diagnosis
The error marked with 'X' occurred during the price determination process for purchasing document 201 00010:
[ ] Net price is 0.
[ ] Net price is negative.
and/or there are no valid conditions or the duration of the
contract has ended.
[ ] Effective value is negative.
[X] Mandatory condition missing.
[ ] Negative delivery costs.
[ ] Delivery costs have been recorded although invoice
receipts are not defined for the item.
[ ] Error during quantity conversion
[ ] Error during currency translation
[ ] Field overflow
[ ] A condition involving delivery costs exists without a
transaction/event key.
[ ]Error during maint. of delivery costs in master conditions
Delivery cost conditions in different validity periodsnot identical
System Response
The transaction cannot be posted without successful price determination.
Procedure
Check the purchasing document and the associated conditions:
Display purchase order
Display scheduling agreement
If the problem cannot be resolved in this way, contact your system administrator.
The latter can check the Customizing settings for price determination in Purchasing under Conditions -> Define Price Determination Process
When the foregoing steps have been carried out, try posting the transaction again.

Cost is showing wrongly in CK11N due to Unit of Measurment (UOM)

Dear Experts,
Cost is showing wrongly in CK11N Std cost estimates. I maintained 95 INR in Material Master per KG, but 9.5 INR Per KG in CK11N. How to maintain Unit of measurement settings correctly.
Regards,
KBR.

Hello Karru,
I recommend these notes:
526780     Cost estimate: units of measure for activity types
72442      Unit conversion in product costing
30658      Price in info record: rounding errors
207628     Unit of operation times changes
Cheers

CKMM Change Material Price Determination

Hello all,
Under what conditions or scenarios CKMM (Change material price determination) is used in Material Ledger/Actual Costing
Thanks

Nasir,
I presume that you are aware of the two price controls prevailing in Product Costing. (1) Standard Price S is constant price without considering usage or invoices; Material stock valued at the same price over an extended period; Price variances are posted to price difference accounts; not affecting the standard price. (2) Moving Average Price V is the price that changes in consequence of usage and entry of invoices; Calculated by dividing the value of material by the quantity in stock; Automatically recalculated based on activity.
Thru' CKMM transaction, you can inter-switch material from one price control to another. However, as I have been observing clients dont move from one price control to another just like that. In my many years of SAP experience, I have moved so far only one material from V to S.
Even within Standard Price S, the standard price can be adjusted from single / multilevel pricing to transaction based pricing. CKMM transaction can also be used for making that kind of change.
Thanks.

Cost price determining wrongly

Similar Messages

Maybe you are looking for