User Exits Part 6: RV60AFZZ — Billing User Exit Patterns

📌 KEY POINTS
✅ Billing (SAPLV60A) exits live in RV60AFZZ (header/item fields, number range) and RV60AFZC (e.g. account determination, invoice split-related exits).
✅ USEREXIT_FILL_VBRK_VBRP fills billing header and item fields from reference documents.
✅ Many billing requirements are better solved with copy control data transfer routines (VOFM) — configured per billing type.
⚠️ Billing runs (VF04, billing jobs) process thousands of documents — every SELECT in a billing exit is multiplied.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 4–5 covered order and delivery exits. Billing is the last step of order-to-cash — and the most volume-sensitive.

━━━━━━━━━━━━━━━━━━━━
▶ 1. KEY FORMS (RV60AFZZ)

• USEREXIT_FILL_VBRK_VBRP — set VBRK/VBRP fields during billing document creation (e.g. custom fields, reference texts). XVBRK/XVBRP tables and the reference data (VBAK/VBAP/LIKP/LIPS in work areas) are available depending on the processing point.
• USEREXIT_NUMBER_RANGE — choose a different number range for billing documents (e.g. per company code or country) via US_RANGE_INTERN.
• USEREXIT_PRINT_ITEM / _HEAD — rarely used.

━━━━━━━━━━━━━━━━━━━━
▶ 2. RV60AFZC
Contains exits used in account determination and other billing processes (e.g. USEREXIT_ACCOUNT_PREP_KOMKCV / KOMPCV to fill account determination communication structures) — used together with customizing of account determination.

━━━━━━━━━━━━━━━━━━━━
▶ 3. COPY CONTROL (VOFM)

• Data transfer routines (VTFL/VTFA copy control, Data VBRK/VBRP) — e.g. routine 9xx copies a field from the order to the billing document.
• Split criteria: invoice split via the ZUKRI field in data transfer routines — the correct place for custom split rules.
• Routines are client-independent code objects assigned in customizing — cleaner than user exits for these tasks.

━━━━━━━━━━━━━━━━━━━━
▶ 4. VOLUME

• VF04 and billing jobs run for all due documents; exits run per document/item.
• Use data from reference documents already in memory; buffer additional reads.
• Error messages stop billing for that document and appear in the billing log (VFX3 for incomplete accounting).

━━━━━━━━━━━━━━━━━━━━
▶ 5. S/4HANA NOTE
Billing exits still exist; in S/4HANA, billing documents may be created via the billing due list and Fiori apps — test those paths. Released BAdIs exist for some billing extensions.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. SE38: display RV60AFZZ and RV60AFZC.
2. VTFL/VTFA: display a copy control item and its data transfer routine.
3. Implement a custom number range rule in a sandbox and test with VF01.

✅ CHECKPOINT: you choose between billing exits and VOFM routines and write volume-safe billing logic.

A company needed one invoice per customer project, but VF04 combined deliveries of different projects into one invoice. A developer first tried to split in RV60AFZZ by manipulating tables, which caused inconsistent billing documents in tests.
The correct solution was a data transfer routine for VBRK adding the project to ZUKRI, assigned in copy control VTFL for the relevant billing types. Invoices split correctly, and no user exit code was needed.

• Implementing invoice split logic in user exits instead of ZUKRI routines.
• SELECTs per item in billing exits.
• Hard-coding number ranges without VN01 setup.
• Forgetting billing due list/background paths in tests.
• Changing accounting-relevant fields without FI alignment.

• Use copy control routines for data transfer and split.
• Keep billing exits minimal and buffered.
• Align number range changes with FI/legal requirements.
• Test VF01, VF04 and billing jobs with volume.
• Document routines and exits in a register.

Questions: "Which billing user exits do you know?", "How do you split invoices by a custom field?", "How do you change the billing number range?"
Strong answer: RV60AFZZ (USEREXIT_FILL_VBRK_VBRP, USEREXIT_NUMBER_RANGE with US_RANGE_INTERN), RV60AFZC for account determination preparation; invoice split via data transfer routine filling VBRK-ZUKRI in VOFM assigned in copy control; watch volume in VF04; test background paths.