VERPR, STPRS field length, moving average price and standard price field lengh is not enough

[former_member587343]

Dear Experts

I'm working for a company (R3 version) and their material prices is very high and some of them exceed 11 characters and even some of these materials are row materials and are used in production orders so the price valuation for the whole product is effected. Do you have any idea how can i handle this problem?

[RAF]

Hi,

try to use another price unit. For example per 1000 KG instead of per 1 KG.

Another thing could be to check the currency: intead for USD try to create tUS (thousand USD)..

Kind Regards

Robert

[former_member587343]

thank you for your answer but suppose this example, i am producing cars and the price of one part(for example the motor) is 400000000000(12 characters). even if i change the unit from each to other units i have to GI the motor in the in production order to make the car so i have assigned all the price to the order of the next level and i have to GR it too which makes another material with this problem. then i have to GI the semi finished to another semi-finished and you see... all these materials prices are effected. 😞

Also the currency im talking about is company code currency and as you know its used to translated all the prices and after going live its not advised to change it and i dont know what the effects would be. so im not sure how the second solution will help me.

[FredericGirod]

VERPR / STPRS : are price with length 11, decimals 2 but there is also the PEINH, the number of unit for this price. And there is the MARM table to convert Unit of Quantity.

1.234.567 USD / 1.000 Kg = 1.234,567 USD / Kg (PEINH help you to manage the coma precision)

1.234.567 USD / G + 1 To = 1000 KG + 1 To = 1.000.000 g => 1.234.567.000.000 USD / To (MARM help you to add a conversion level)

do you have an example of your company ?

[former_member587343]

sure. for example there is a material 2031107 and its price is about 400000000000 $ (as you see 12 characters) so if you want to enter standard price you have problem, and also for ML it cant valuate it because its price is more than 11 characters and so ML doesn't work on it and price doesn't get updated.

[former_member587343]

Hello

thank you for your kind attention. I think your solution works when prices are small and not in this case. here i attach an example and it be grateful

if you take a look at it.

[FredericGirod]

Look the structure of table MBEW:

there is VERPR / STPRS and PEINH in 5 positions

So, you could create :

VERPR or STPRS : 85 900 000 USD for 10 000 Unit same thing as 859 000 000 000 for 1 Unit