cancel
Showing results for 
Search instead for 
Did you mean: 

KONP Table did not get updated with the correct value & decimals

0 Kudos

Hi...

The Condition Record values maintained in VK11 is stored in KONP table. But the value stored are the same decimal length in KONP table compared to VK13 record. We never faced any issue in Sales documents created in SAP, however there is an other system calling the Pricing Condition Record via RFC using a FM which picks the value from KONP table which is two field length less than the actual value.

Example - VK13 has INR 20,000.50 whereas KONP stores as INR 200.00.

It seems to be a std behavior. So we need to write a separate logic multiplying by 100 whenever we use KONP table entries or is there any other std approach. I tried to search, but only bits & pieces of info available. Hence posted.

Accepted Solutions (0)

Answers (1)

Answers (1)

Jelena
Active Contributor
0 Kudos

Can you share a screenshot?