cancel
Showing results for 
Search instead for 
Did you mean: 

Net price for migrated PO's

former_member627351
Contributor
0 Kudos

HI All,

We are migrating PO's from SAP 4.7 to Ecc 6.00 as business is scrapping the old SAP 4.7. During our PO migration NETPR field in the PO is populating correctly but the same value when we check in the EKPO table for the PO it is showing incorrectly. Please see the below example

In PO NETPR 35.466 per 1000 EA ordered quantity 1300 EA and in EKPO NETPR value for the PO is showing as 354.66 not sure why is it showing in this way

All the PO's are migrated through a BDC recording

Pavan

Accepted Solutions (1)

Accepted Solutions (1)

former_member183424
Active Contributor
0 Kudos

Hi,

In standard, PO doesn't allow net price 35.466 .

It should 2 decimals.

Can you share the screen shot?

Thanks

DEV

former_member627351
Contributor
0 Kudos

Hi Dev,

Sorry i have rechecked the PO the currency is HUF so no decimal places are allowed.

In PO NETPR 35,466 per 1000 EA ordered quantity 1300 EA and in EKPO NETPR value for the PO is showing as 354.66 for price unit (PEINH) 1000 EA .not sure why is it showing in this way

Ideally it should show 35,466 NETPR in EKPO table

former_member183424
Active Contributor
0 Kudos

Hi Pavan,

See, Normally it cant happens, because both are standard ME23N and EKPO table.

Whatever you have seen in ME22N, you can also see this in EKPO table.

It cant be different.

Please check it correctly.

Can you post the screen shot please.

Thanks

DEV

JL23
Active Contributor
0 Kudos

the price field in EKPO table is technically a field with 2 decimals, hence any value will be stored with 2 decimals. It is a SAP logic that in case of currency with less than 2 decimals the value is just moved into this field as is (no decimals are added), the program logic (function module) takes care that SAP operates right and uses the value in the right form. Only in SE16 and own developed programs that make not use of the standard function modules the user has to be careful in interpreting what he is seeing.

former_member627351
Contributor
0 Kudos

Hi Juren,

One question when i check in my SAP 4.7 system i do not see this issue. However i have this issue in ECC 6.0

When i checked further in transaction OY04 HUF currency is not available in SAP 4.7 however it is avaialble in ECC 6.0

Could the above difference be the reason

Answers (2)

Answers (2)

former_member627351
Contributor
0 Kudos

HI All,

I am closing the ticket. As i was able to find some similar posts relating to my issue. (posted by Juren)

For currencies like HUF,JPY & OMR where they do not have decimal places they will have this issue. As the table expects to have two decimal places it places the decimal at table level.

As i understand this is a standarrd behaviour.. Nice learinig i had

Thank you all for the inputs.

Former Member
0 Kudos

Hi,

Please check decimal Places  T.code CUNI & OY04 in SAP 4.7 to Ecc 6.0