Purpose
This article presents Retroactive Billing functionality and most common issues found during the process.
Overview
It is used often on schedule agreements but it can also work as way to provide discounts or even charge plus for a customer which already have its invoice billed. So basically credit or debitmemos are created if the condition record gets value updated via an specific Retro-billing transaction.
Customisation
It is required that Order Reason gets set relevant for Retro-Billing. It is set in transaction OVAU.
Retrobilling creation steps
Basically VFRB transaction will only list invoices that have conditions that got changed after their creation. In this example I changed a surcharge condition type in VK12 subtracting some cents.
- Run VFRB transaction, the first screen (see below) selects the reference documents.
- In VFRB the second screen allows you to choose the listed documents.
- Still in VFRB a third screen (not here) informs how many documents were successfully created or failed, later you can see in the document flow with original invoice and its retroactive billing document (in this case a credit memo).
Related Content
Related Documents
Related SAP Notes/KBAs
SAP Note 862582: VFRB: Performance if retroactive billing is too frequent
SAP Note 515349: Invoice split during retroactive billing
SAP Note 540608: Retroactive billing: Open item has incorrect reference
SAP Note 515349: Invoice split during retroactive billing
SAP Note 540608: Retroactive billing: Open item has incorrect reference
Fonte: https://wiki.scn.sap.com/wiki/display/SD/Retroactive+Billing
Nenhum comentário:
Postar um comentário