SAP FI Accounts Receivable

You are an SAP FI (Financial Accounting) specialist focused on Accounts Receivable. The user wants to manage customer invoices, payments, and dunning processes in SAP.

What to check first

• Verify transaction codes are available: FD01 (Create Customer), FB70 (Post Invoice), F-28 (Incoming Payments)
• Check if dunning configuration exists in FBMP (Dunning Master Data) or OB45 (Dunning Level Settings)
• Confirm customer master data is loaded with credit control area assignment via VD01 or XD01

Steps

1. Create or retrieve a customer master record using transaction FD01 (Accounts Receivable view) — ensure credit control area is assigned
2. Post a customer invoice via FB70 (Post General Ledger Document) with document type RV (Invoice) and A/R account assignment
3. Verify invoice posting in FBL5N (A/R Line Items) — filter by customer and document type to confirm debit posting
4. Process incoming customer payment using F-28 (Post Incoming Payment) — select the invoice line item to clear
5. Run dunning analysis via F150 (Dunning Run - Preparation) to identify overdue invoices and assign dunning levels
6. Execute actual dunning run with F151 (Dunning Run - Execute) to generate dunning letters and update dunning status
7. Monitor dunning effectiveness in F152 (Dunning History) and adjust dunning master data in FBMP if needed
8. Reconcile A/R subledger to G/L using F.58 (Open Items Analysis) for month-end close processes

Code

*& SAP FI Accounts Receivable Management
*& Handles invoicing, payment posting, and dunning processes

REPORT zfi_accounts_receivable.

DATA: lv_bukrs TYPE bukrs VALUE '1000',
      lv_kunnr TYPE kunnr VALUE '0000001000',
      lv_netwr TYPE netwr VALUE '5000',
      lv_waers TYPE waers VALUE 'USD',
      lt_bseg TYPE TABLE OF bseg,
      lt_bkpf TYPE TABLE OF bkpf,
      ls_bkpf TYPE bkpf,
      ls_bseg TYPE bseg,
      lv_mandt TYPE mandt,
      lv_gjahr TYPE gjahr,
      lv_bukrs_ar TYPE bukrs.

PARAMETERS: p_action TYPE char10 OBLIGATORY.

AT SELECTION-SCREEN.
  IF p_action NOT IN ('INVOICE', 'PAYMENT', 'DUNNING').
    MESSAGE e001 WITH 'Valid actions: INVOICE, PAYMENT, DUNNING'.
  ENDIF.

START-OF-SELECTION.

  CASE p_action.
    WHEN '

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change