on 02-21-2014 3:08 PM
Hello guys!
I'm working on Retro-billing with VFRB.
The scenario is working perfectly fine for our normal sales.
But... we also have a type of sales which include a labor percentage. This percentage is maintained in a condition.
Our main price condition is ZB00 and the percentage is maintained in ZB02. For each material the percentage is different.
Now, when I do the retro-billing for this scenario, what happens is:
SAP compares the total calculated value of the original invoice versus the total calculated value of what would be the price today, and creates the debit memo with that ammount. But... since there is a percentage in there, this difference comes out incorrect.
Example, if old price in VK11 for ZB00 was $100 and new price is $120, the debit memo for 1 quantity should be $20
Instead, SAP is not using the raw VK11 price, it is using the whole calculated price including the percentage. Let's say percentage is 5% - and 5% of 100 is 5, but 5% of 120 is 6.
So instead of creating debit memo with $20, it is creating debit memo with $26.
I don't want it to do that, since the price difference should be calculated only based on the raw value in VK11.
I think I might need to use VOFM and formulas for this kind of situation since its a special one, but I'm not a specialist in pricing and I'm a bit lost.
Anyone have any orientation or suggestions of how I should proceed in this case?
Thanks!!
Gabriel Andrade
Hi Gabriel,
I don't think any special enhancement required for this. It can simply handle through correct placemnt of Condition Type PDIF in your pricing for debit memo. Thus, for your the debit memo pricing procedure place Cond PDIF after sales base price, instead of placing after total of price & discount.
Existing Pricing Procedure in Debit Memo | Revised Pricing Procedure in Debit Memo |
---|---|
1. Conditions for Base Price | 1. Conditions for Base Price |
2. Conditions for Discount/Surcharge | 2. Condition Type - PDIF |
3. Condition Type - PDIF | 3. Conditions for Discount/Surcharge |
Thanks, JP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello JP!
Yes, I forgot to mention that PDIF is already there in that spot, right after ZB00 which is my VK11 price.
All taxes, discounts, etc are after. I placed it in position 20 of my pricing procedure, at the very top.
As I said, it works fine for normal sales, but it does not work fine for the other pricing procedure that has a percentage condition in the middle.
When VBRF runs and calculates the value that the debit memo should be issued, it is always a higher value than it should be, because of the percentage, as explained above.
Thanks!
Gabriel
JP, ok, I'll do better.
I'll attach an screenshot of an excel with two whole pricings, one with old price and one with new price. None are from a Debit Memo, both are full price.
The reason I put two with full but different prices is so we can see what the system compares when he's running VFRB
Notice in the red columns the differences (pricing 2 minus pricing 1), and in the last column my notes.
The total price for these 4 materials for the debit memo should be, including taxes, 24,39 BRL but it ends up being 24,59 as you can see in the excel file because of Labor %
Note that these 15 extra cents is what is causing my problem. It exists because the new value is bigger than old one, and so the percentage calculated is bigger as well.
Regards,
Gabriel
Hello JP,
I think I thought of a solution... I think it may be the only way of doing this.
Everytime sales is going to retroactively change a price, they will then create a new condition (ex ZOLD) and put the original price there, so I can then create a formula and calculate the difference and force it into PDIF instead of using the one calculated by SAP.
But I'm not yet sure how I can make this ZOLD condition obligatory/mandatory when in a Debit Note but not mandatory when invoicing a normal sale.
The PDIF already hides itself when in a normal invoice, do you know how I can do that with a condition created by myself?
Thanks!
Gabriel
That's what I mentioned in my previous post. Placement of condition type PDIF plays critical role in retro-billing VFRB. Thus, PDIF should be placed after pricing, in you case after Valor Negoclado.
We too face similar sort of situation in VFRB for India localisation. And that is way it was handled. You can Google with search term, "SCN PDIF excise JP" for my other response for similar sort of requirements.
Thanks, JP
JP,
I have solved the problem.
I created another condition which will have the old price and will be inside my pricing only as a reference.
Then in PDIF I created a formula which recalculates the difference properly, without applying the percentage.
That way the billing document is generated properly.
Now I will try to enhance the VFRB report to not allow retro-billing for that type of document (the one that has percentages) in case the new condition type is empty in VK11.
Thanks for your help.
Regards,
Gabriel
User | Count |
---|---|
86 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.