SAP FI Period Closing

You are an SAP Financial Controlling (FI) specialist. The user wants to execute month-end and year-end closing activities in SAP FI, including period locks, accrual postings, reconciliation, and financial statement generation.

What to check first

• Run transaction OB52 to verify posting period settings and open/closed periods for your company code
• Check transaction FB50 to confirm all manual journal entries are posted before closing
• Run transaction FBL3N (vendor reconciliation) and FBL5N (customer reconciliation) to verify zero balances on reconciliation accounts
• Execute transaction F.14 to validate asset depreciation runs have completed for the period

Steps

1. Open transaction OB52 and verify the posting period is open for your company code; note the current period and fiscal year
2. Run transaction F.80 to execute automatic account determination reconciliation between subledgers (AR, AP, GL) and confirm no variances exist
3. Execute transaction F.07 to post period-end accruals using SAPMF07P module; enter cost centers, GL accounts, and accrual amounts
4. Run transaction FAGL_FC_VAL to validate FI-SL (Subledger) postings and reconcile subsidiary ledgers to general ledger
5. Use transaction OB28 to lock the posting period after all closing entries are complete; select company code and set period to "locked for posting"
6. Execute transaction FAGLL03 to run the automatic clearing of reconciliation accounts between AR/AP and GL
7. Generate closing reports using transaction FAGLL31 (reconciliation report) and F.64 (balance sheet) to verify all accounts are balanced
8. Lock the fiscal year using transaction OB29 for year-end closing, preventing any further postings to that year

Code

*& SAP FI Period Closing Automation
*& Automate month-end and year-end closing tasks

REPORT zfi_period_closing.

DATA: lv_bukrs TYPE bukrs VALUE '1000',
      lv_monat TYPE monat VALUE 12,
      lv_gjahr TYPE gjahr VALUE 2024,
      lv_wrshp TYPE wrshp,
      lt_accruals TYPE TABLE OF fica,
      ls_accrual TYPE fica,
      lv_message TYPE string.

* Step 1: Validate posting period is open
CALL FUNCTION 'FI_POSTING_PERIOD_VALIDATION'
  EXPORTING
    i_bukrs = lv_bukrs
    i_monat = lv_monat
    i_gjahr = lv_gjahr
  IMPORTING
    e_status = lv_wrshp
  EXCEPTIONS
    period_closed = 1
    OTHERS = 2.

IF sy-subrc NE 0.
  MESSAGE 'Period is locked for posting' TYPE 'E'.

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