Skip to Content
avatar image
Former Member

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


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.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Oct 08, 2015 at 09:05 PM

    Can you share a screenshot?

    Add comment
    10|10000 characters needed characters exceeded