SAP FI New GL

You are an SAP FI configuration specialist. The user wants to configure the New General Ledger (New GL) with document splitting and parallel ledgers in SAP.

What to check first

• Run transaction SPRO and navigate to Financial Accounting → General Ledger Accounting → Master Data to verify current GL configuration
• Execute FINS_LEDGER_SETUP transaction or check table T881 to see existing ledger structures
• Verify client-wide settings in OB62 (Maintain Currencies) and OB26 (Document types) are active

Steps

1. In transaction SPRO, navigate to Implementation Guide → Financial Accounting → General Ledger Accounting → Ledgers and activate New GL by setting "Use new general ledger" to "X" in OB58 (New GL Switch)
2. Create parallel ledgers in FINS_LEDGER_SETUP (or SPRO → New GL → Ledgers) with specific ledger types: Non-Leading Ledger for GAAP, Consolidation, or Local GAAP variants
3. Configure document splitting rules in SPRO → New GL → Document Splitting → Maintain Splitting Method, assigning splitting logic to cost centers, profit centers, or segments
4. Activate document splitting in table T881LFLDS by setting flag for each ledger requiring split; execute transaction ADSO_SETUP if using Analytics (BW/4HANA)
5. Define ledger groups in SPRO → New GL → General Settings → Ledger Groups using transaction FINS_LEDGER_GROUP_SETUP to organize parallel ledgers for reporting
6. Configure posting variant in OBC4 (Posting without Tax Code) or OB74 (Posting Keys) ensuring document splitting is triggered for each posting type
7. Run pre-implementation check in SPRO → Tools → Pre-Implementation Test → Execute on tables T881, T881LFLDS, T001L to validate configuration
8. Execute transaction RFINS_ACTIVATE_NEWGL or run batch job FINS_LEDGER_ACTIVATE to activate New GL across all company codes in ledger group

Code

*& Purpose: SAP FI New GL Configuration Setup
*& Activate New GL with Document Splitting and Parallel Ledgers

REPORT z_new_gl_config.

DATA: lt_ledger      TYPE TABLE OF fins_ledger_s,
      ls_ledger      TYPE fins_ledger_s,
      lt_split_rule  TYPE TABLE OF fins_split_rule_s,
      ls_split_rule  TYPE fins_split_rule_s,
      lv_msgty       TYPE symsgty,
      lv_msgid       TYPE symsgid,
      lv_msgno       TYPE symsgno,
      lv_msgv1       TYPE symsgv,
      rv_subrc       TYPE sy-subrc.

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