Ordinary supposition that will be that Unit ought to accompany regard to 1 ( 10.00$ per EA and so on). Yet, KONV-KPEIN (PER) isn’t equivalent to 1 in many events ( it very well may be 3626.19 per 10 EA). Why is PER in conditions not always 1? The purpose for is, SAP attempts to save the PER as exact as workable for computation.
Why is PER in conditions not always 1? SAP does a two-way approval. It ascertains the Unit regarding PER. And afterward back ascertains Absolute with that PER. On the off chance that 1 For each doesn’t give the exact outcome, it goes for next higher PER in various of 10.
Example:
Total = 4351.43; Quantity = 12
Rate Calculation With PER 1
KBETR = PER * KWERT / QTY
= 1 * 4351.43/12
= 362.62 (Price of 1 Unit, i.e PER 1)
KWERT = KBETR * QTY / PER
= 362.62 * 12 / 1
= 4351.44 (back calculated Total)
4351.44 is NOT equal to original 4351.43. So PER 1 is not considered
Rate Calculation WITH PER 10
KBETR = PER * KWERT / QTY
= 10 * 4351.43/12
= 3626.19 ( Price of 10 Unit, i.e PER 10)
KWERT = KBETR * QTY / PER
= 3626.19 * 12 / 10
= 4351.43 (back calculated Total)
Determined absolute 4351.43 is equivalent to unique complete 4351.43. So PER 10 is thought of. PER can be 100, 1000 and so forth for certain restrictions.
I gave the above hypothesis to my client, yet they needed to see this occurrence clearly. Thus, I needed to put on my troubleshooting cap and chase where SAP does this. With some work, I had the option to find the fortune..
SAP is doing this in standard daily practice, CORRECT_ROUNDING_ERROR (program LVPKSDF23)
On the off chance that for reasons unknown, your client believes the framework should drive the PER to 1. You can execute the under two s-notes to keep up with PER as 1 generally.
YOU MAY BE INTERESTED IN
SAP ABAP Checkpoint Group – Chase the Mysterious SAP Issues with a Smile
Building Cloud-Native ABAP Applications: A Guide to Modern SAP Development
4 Useful Tips on ABAP and ABAP on HANA
WhatsApp us