cancel
Showing results for 
Search instead for 
Did you mean: 

EKPO-NETPR value too long - message 00089

ros_pennefather
Explorer
0 Kudos

Hi there

An EKPO-NETPR entry is restricted to 13 digits - in most cases this is 11 digits, and then 2 for the decimal points. I know that this has been a problem in countries like Zimbabwe, where the value of the Zim dollar is so low. I know that you can change code, but this is not supported by SAP. Does anyone have a work around for this problem?

Thanks and regards

Roz

View Entire Topic
ros_pennefather
Explorer
0 Kudos

Hi Rajesh

Thanks for your reply. The question is really related to where the value of the currency is so low, that combined with SAP field length limitations, it is not possible to post values. I seem to recall that in Zimbabwe they resolved this issue via Accounting, but cannot remember the work around. Does anyone know the Zim solution, or have any idea on a solution?

Thanks

Roz

Former Member
0 Kudos

He all!

This question is actual for me now. Does anyone find any appropriate solution?

I've tried to use unit of measure 0,0001 ST but get an error in GR

M7302 "Field overflow in routine WERT_SIMULIEREN in field NEUER_PREIS".

JL23
Active Contributor
0 Kudos

Why dont you create your own thread, your problem has not much to do with the issue of this thread.

the subject here has the message 00 089, you have the error M7 302

Former Member
0 Kudos

I think this is a very tightly connected problem: when I guess how to avoid the message 00089 which was mentioned at the top of the thread and save puchase order with price more than 1 billion I've got the following error message in GR.

Also I hope to get an answer from the author of this thread becase It's old enough to find an answer or suitable workaround.

JL23
Active Contributor
0 Kudos

I guess you know already why you have this error, or?

What about posting your values.

What is the order quantity, what is the price and its currency? what is your home currency?

Is it really a realistic scenario or just one to see where the technical boundaries of SAP are?

Former Member
0 Kudos

I know - It's all from price field length not only in purchase order but when MAP recalculation:

SAPLMBGB / LMBGBFST:

-


Form Wert_Simulieren

...

preis = w-salk3 * w-peinh * 1000 / w-lbkum.

...

if preis > maximum_gld or preis < minimum_gld.

message e302 with 'WERT_SIMULIEREN' 'NEUER_PREIS'.**

endif.

neuer_preis = preis.

-


Where maximum_gld = 9.9999999999000000E+10 = 99'999'999'999

No such a problem exist in amount fields:

EKPO-NETPR is CURR(11,2) while EKPO-NETWR is CURR(13,2)

So It inexplicably to have possible 1'000 untis for 1'000'000 price for each but no 1 unit for price of 1'000'000'000 each.

This is a very realistic scenario. It is about buying one unit of assets under construction (AuC) for the 1 billion price in russian rubles and above (for winter olympic games http://sochi2014.com/en/ ).

Parameters of purchase order:

- PO quantinty is 1 PC (1 unit of AuC).

- Net price is over 1 billion (1-10 billion really).

- order currency is russian rubles (RUB).

- home currency (CoCd) is ruble too (RUB).

Changing of home currency is not possible due to system is many years as going live.

Changing PO quantity - entering 1000 PC instead of 1 PC (with corresponding deduction of price) is not suitable too.

Changing the order currency to some equivalent of 1000 RUB is not working too because of MAP which is calculated in home currency. The same error is issued - M7302 "Field overflow in routine WERT_SIMULIEREN in field NEUER_PREIS".

I've tried to use subitems in PO but with no success.

Do you have any new ideas?

JL23
Active Contributor
0 Kudos

Note 456691 - FAQ: Price determination in purchasing

Can I use net prices that have more than 11 digits (including decimal places)?

Answer:

The field for the net price can be filled only with 11 characters (including 2 decimal places). A larger value usually leads to an overflow error ('price overflow error'). You can avoid this error by i) reducing the related quantity, ii) splitting the material item into several items, or iii) changing the price unit of measure accordingly.

The same applies for effective prices, which cannot exceed 13 digits (including 2 decimal places).

If you have further questions about this, we recommend that you open a customer message and forward it to SAP Development Support.

See also Note 584997.

Former Member
0 Kudos

Thank you for finding the note. I couldn't find it myself. But even before reading it I've found out that suitable solution for my case is №3 "changing the price unit of measure accordingly".

So I've made new base unit of measure for items (despite of unreal meaning 0.01 of item) which is smaller than Purchase order unit of measure (PO UoM) and set conversion factor in material master that 100 Base UoM = 1 PO UoM. It's important to fill field PO UoM in material master. In purchase order you should specify Order Price Unit as Base UoM. So you can enter up to 999'999'999.99 in the field Net price for 1/100 of 1 PO UoM. So you get multiplier of 100 and amount of 1 item is 99'999'999'999.00

Due to the fact that amount cannot exceed 13 digits and price cannot exceed 11 digits (both including 2 decimal places) the conversion factor 100 is the maximum which is possible.