VF02 — Change Billing Document
VF02 is used to change permitted billing-document header or output-related fields and handle certain release/correction actions after billing creation. It is most useful when a billing document exists but permitted attributes or accounting-release issues require follow-up without recreating the invoice. Work from the exact document, organizational level and business date, then verify downstream status or accounting evidence before changing master data or configuration.
This page explains VF02 — Change Billing Document — as a practitioner reference: what it does, when it belongs in the process, the fields that matter, how to prove the result in SAP data, and the mistakes that create the most rework.
Published 19 Sept 2026· 593 words
Esta página ainda não está disponível em português.
Purpose
change permitted billing-document header or output-related fields and handle certain release/correction actions after billing creation. The key is to treat VF02 as one step in an end-to-end process. What users see here is often determined earlier by master data, document status, organizational assignments or configuration, so always capture those inputs before changing the transaction result.
When it is used
VF02 is typically used when a billing document exists but permitted attributes or accounting-release issues require follow-up without recreating the invoice. It is also valuable in integration and regression testing because the resulting document/status provides objective evidence of whether upstream data and configuration are aligned. Narrow the working population first so any change can be reconciled safely.
How to use it in practice
- Display document flow and accounting status first.
- Determine whether the requested field is legally/change-technically permitted after billing.
- Change only non-value fields allowed by the process.
- For value/tax/pricing errors, use cancellation/rebilling rather than editing history.
- Verify accounting and output status afterward.
Key data objects
These fields and business objects usually explain the result in VF02. Put them into support tickets and test evidence so another consultant can reproduce the same state instead of working from a generic symptom.
- billing document — verify the exact value, status, organizational context and date relevance.
- billing status — verify the exact value, status, organizational context and date relevance.
- accounting status — verify the exact value, status, organizational context and date relevance.
- output/status fields — verify the exact value, status, organizational context and date relevance.
- document flow — verify the exact value, status, organizational context and date relevance.
How to prove it in the data
Prove the issue through document flow and chronology. Start with the source requirement or document, identify the exact master/configuration keys used, then inspect the generated logistics or accounting document and its status. For quantity issues, reconcile ordered, received, delivered, invoiced and current/historical stock; for value issues, reconcile pricing, account determination and the FI document.
ECC vs S/4HANA
VF02 remains available in S/4HANA. Output Management and compliance requirements make it increasingly important to distinguish a permitted document change from a required cancellation/rebill. In an S/4HANA program, keep valid GUI transactions as support tools but use the strategic Fiori, workflow, embedded analytics and clean-core integration patterns where they provide the preferred business surface.
Common pitfalls and how to diagnose them
- Trying to change commercial values that require cancellation and rebilling. Check the complete document flow before applying a workaround.
- Fixing accounting-release errors by editing unrelated billing fields. Check the complete document flow before applying a workaround.
- Assuming a saved billing change automatically reissues customer output. Check the complete document flow before applying a workaround.
Whose problem this is
Primary ownership sits with SD/O2C or FI/CO depending on the transaction, with Finance joining where accounting is created and EWM/integration teams joining where execution happens outside core ERP. Escalate with document numbers, organizational keys, date, expected result and proven status.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/vf02ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.