Question Re: Error message no 06217 - Net Price in XXX becomes to large. in Enterprise Resource Planning Q&A

Error message no 06217 - Net Price in XXX becomes to large.

Former Member — Tue, 31 Aug 2010 16:01:20 GMT

Hi,

I am creating PO in currency EUR and company code currency is different.

While saving PO I am getting the error message as Net Price in XXX becomes to large. message no 06217.

Why system is giving this error?

Regards

Re: Error message no 06217 - Net Price in XXX becomes to large.

Former Member — Tue, 31 Aug 2010 16:23:52 GMT

Hello Sachin ,

Error message 06 217 is issued in order to avoid an overflow in an amount field.

If in the purchase order the order unit differs from the purchase order price unit , the internal conversion of the effective value

into the purchase order price unit using the conversion factor can cause an overflow of the field "net price".

According to the system design , amount fields are restricted to a maximum length of 13 positions (11 integers and 2 decimal places).

Here is a possible solution but this code change would be considered a modification to the standard system and would not be supported by SAP:

mm06ef0e_ekpo-netpr

...

*- Überlauf prüfen

IF F1 > MAXPREIS.

MESSAGE E217 WITH T001-WAERS. "delete

f1 = maxpreis. "insert

ENDIF.

A work-around is to use smaller orders in an effort to keep the price

(f1) below the maximum allowable (maxpreis).

I hope this information has been helpful for you.

Best Regards,

Frank

Re: Error message no 06217 - Net Price in XXX becomes to large.

Former Member — Tue, 31 Aug 2010 17:24:55 GMT

SAP doesn't support item prices larger than 999.999.999,99. This is a limit of the system.

The field has a length of 11 and output length of 16 for the commas and dots. Therefore, values entered in that field cannot exceed the total length of the field.

Increasing the field length of the field is challenging. This would

cause inconsistencies in the existing dataset and more problems in

in Finance modules.

You have to look for possible workarounds to resolve this. You may

choose to split the documents, line items or quantities - what suits

your business requirements best.

You may choose to:

1. Split the line items.

This is applicable when your company wants to procure 1 single item

with say 1 Billion value.

for example:

Qty Unit Net price

1 EA 1,000,000,000.00

This may be cost of one machine or asset.

You may split this into accessories or mountings used for this as

separate line items, so that the cost of the line item will be less

than 1 Billion.

2. Splitting the quantities,

This is appliable when you are procuring more quantities with higher

value items.

For example:

QTy Unit Net price

1000000 EA 100000.00

You may split this quantity into 250000 EA * 4 = 1000000. With this

you may consider having four line items in the same PO or 4 differant

PO's.

3. Consider using pricing unit.

If you use currencies in which higher values become necessary, SAP

recommends to use smaller units of measure (for example "box"

"pallet").

For Example:

Qty Unit Net price

1 Pallet 1000000000.00

In this case you may split this into Boxes. May be the Pallet contains

more than 1 boxes. The net price of the box will be less than

the Pallet.

If your prices is not larger than 999.999.999,99 then please open a ticket in SAP, as this would be a bug and you would need a correction, that at the moment does not exist.

Re: Error message no 06217 - Net Price in XXX becomes to large.

Former Member — Tue, 31 Aug 2010 17:40:31 GMT

Probably what may be happened in your case

price will be increased in your vendor invoice or

Check exchange rate is maintained for 'EURX' exchange rate type and also it will be maintained for indirect method.

Simply compute Price * exchange rate of EUR for local currency see results

Re: Error message no 06217 - Net Price in XXX becomes to large.

Former Member — Mon, 06 Sep 2010 07:53:07 GMT

solved

Re: Error message no 06217 - Net Price in XXX becomes to large.

Former Member — Thu, 20 Dec 2012 06:19:33 GMT

Dear Team,

Please raise this request to SAP as High Priority:

"When we raise the PO through ME21N with 44Crores the system throws error "Net Price in INR becomes to large" which is attached, as per our analysis the system is calculating Taxes internally which is exceeding 999.999.999,99 (1Billion) & the system is not accepting 44Crores when we tested the same with 33Crores it accepts, Please let us know the solution from your side on this issue"

SAP REPLY :

Are you convinced that the tax value is correct? I understand that PO
net value is 44 Crores. It mean 440000000 INR. It has legnth of 9 beforedecimal. Value fields have length of 11 which includes 2 decimal places.So if tax is tax is not more than 100%, it should not exceed the length.
Anyway bigger values than 9 digits are exceptional. If you have any
such requirement, please create a duplicate currency key. say IND...
Please keep it's decimal places as zero. Then you would be able to
utilize full field length (11) for storing the value. System would
divide PO value by 100 to store it. But when these values would be drawnfrom table, system would automatically multiply with 100 before using it

Please reply to SAP as below:

"Since you are pointing to create the Duplicate Currency Key, this is not possible when Material ledger is active which is the not the right way to do as well, please let us know any other feasible solution for these kind of issue"

Hi SAP Community,

Please let me know the how to go about on this issue as the amount 44Crores is not allowed to be posted through ME21N

Regards,

Vijay

Re: Error message no 06217 - Net Price in XXX becomes to large.

former_member379458 — Tue, 18 May 2021 15:18:17 GMT

Hello Sachin

Would you mind explaining how the issue was solved?

Re: Error message no 06217 - Net Price in XXX becomes to...

DCORONEL — Mon, 23 Sep 2024 18:11:57 GMT

Buenas tardes,

El error puede generarse por el maestro del material utilizado.

Por favor verifique el material con la MM03 en la vista CONTABILIDAD 1

Sap multiplica el valor del campo marcado por la cantidad y cotizacion ingresada y alli se produce el error.

Deberia corregir la cantidad, recomiendo dejarlo en cantidad base 1

Debe cambiar el precio por el valor unitario y con ello no deberia presentar el error

Saludos,