 (2).jpg)
1 week ago
3
Hello,
In SAP standard, the tract NETPR has been defined with magnitude 11 (9 digits + 2 decimals), and this cannot beryllium changed, arsenic this would impact each programs and tables that usage it. Every programme would request to beryllium adjusted to grip the caller tract magnitude and existing information would request to beryllium converted.
This is the modular behaviour and can't beryllium changed from SAP end.
Refer the SAP Note: 456691 - FAQ: Price determination successful purchasing question 38: -
Question : Can I usage nett prices that person much than 11 digits (including decimal places)?
Answer : The tract for the nett terms tin beryllium filled lone with 11 characters (including 2 decimal places). A larger worth usually leads to an overflow mistake ('price overflow error'). You tin debar this mistake by i) reducing the related quantity, ii) splitting the worldly point into respective items, iii) changing the terms portion of measurement accordingly. The aforesaid applies for effectual prices, which cannot transcend 13 digits (including 2 decimal places).
See besides KBA 2437956 - EKPO-NETPR has 11 (9+2) digits successful magnitude - SAP ERP & SAP S/4HANA - EKPO-NETPR has 11 (9+2) digits successful magnitude - SAP ERP & SAP S/4HANA.
- Possible workarounds include:
- split the worth into aggregate items or
- define a caller portion of measurement for this product. This portion A of measurement should be, for illustration 10 A = 1 unit, and past make the acquisition documents with lone 1 unit.
