SAP General Ledger in S/4HANA: Master Data, Chart of Accounts, and Setup (Part 1)

Book: Financial Accounting in SAP S/4HANA Finance Simplified: Questions & Answers by Narayanan Veeriah | ISBN 978-93-65898-675

Chapter 15 is where the book stops talking about finance in the abstract and starts getting into the guts of SAP General Ledger. This first half covers questions 363 through about 412. If you have been reading the earlier chapters on parallel ledgers and company codes, this is the payoff. G/L is the hub everything else posts into.

Why G/L matters in S/4HANA

The book opens with a simple but important point: SAP G/L exists to record every business transaction in one integrated place. Sales, purchasing, production, HR, treasury, all of it feeds financial accounting. In S/4HANA Finance, G/L is not the old fragmented R/3 ledger setup. It is the single source of truth with real-time posting, parallel accounting, segment reporting, and cost of sales built in.

Compared to classic SAP ERP, the difference is night and day. Old R/3 needed multiple ledgers and manual reconciliation between FI and CO. S/4HANA Finance folds management and financial accounting into one interface. Leading and non-leading ledgers handle parallel and segment accounting without the painful reconciliation cycles.

Before you touch any G/L functionality, the book lists the customizing checklist: company codes, fiscal year and posting periods, currencies, ledgers, parallel accounting, and FI-CO integration. Skip any of that and you will hit walls later.

Three kinds of data and G/L master structure

SAP stores three data types: table data (customizing), transaction data (daily postings), and master data (long-lived control info). G/L master data sits in that third bucket and controls how postings behave.

G/L master records split into three areas in S/4HANA:

• Chart of accounts area (valid across company codes): account number, type, account group, descriptions
• Company code area: currency, tax category, tolerance group, line item display, interest indicator
• CO area (new in S/4HANA): cost element category for primary and secondary costs

That third area is a big shift from R/3. Cost elements now live inside the G/L master instead of separate CO master records.

Chart of accounts: the foundation

A chart of accounts is the list of G/L accounts for one or more company codes. The book walks through three chart types:

1. Operating (standard) chart: used for daily FI and CO postings, assigned to company codes
2. Country (alternate) chart: for local statutory reporting, linked via alternate account number
3. Group (corporate) chart: consolidation universe, not assigned to company codes

One chart of accounts can serve multiple company codes, but each company code gets only one operative chart. The book stresses reviewing your existing chart before migration. Rationalize redundant accounts, fix numbering length, consolidate legal entities onto one chart. Do this before creating thousands of accounts you will regret.

Account groups, screen layouts, and creation tools

Account groups are mandatory. They control number ranges, screen layouts, and field status. SAP delivers standard groups like AS, CASH, GL, MAT. Copy and tweak rather than building from scratch.

The book compares three creation helpers:

• Reference account: copies all fields from an existing G/L account
• Sample account: template with data transfer rules controlling which fields copy over
• Account group: mandatory, controls numbering and field visibility

For bulk work, collective processing (OB_GLACC11 through OB_GLACC14) edits many accounts at once. Individual processing creates or changes one account centrally, in chart of accounts area only, or company code area only.

Practical field tips I picked up

A few details stood out as things consultants actually trip over:

• Changing B/S to P&L account type works technically, but run balance carry forward afterward
• Tax category and reconciliation account flags cannot change after postings exist
• Clearing accounts need “balances in local currency only” to avoid exchange rate difference postings on multi-currency clearing
• Line item display must be on for open item management
• Blocking stops postings or blocks creation entirely at chart or company code level

Financial statement versions (FSV) get a solid treatment too. FSV is the hierarchical layout for balance sheet and P&L. Up to ten hierarchy levels, special nodes auto-generated (Assets, Liabilities, Net Result, etc.). Copy standard versions like BAIN and customize rather than building from zero.

Document splitting preview

The chapter ends by introducing document splitting, which splits line items by dimensions like segment or profit center to produce zero-balance financial statements per dimension. Passive splitting (clearing, reversal) runs automatically. Active splitting follows your customizing rules. Wizards in S/4HANA simplify the IMG configuration.

That topic continues in part 2, along with posting, clearing, interest calculation, and Fiori apps.

Previous: FI Global Settings Inflation Accounting Chapter 14 | Next: SAP General Ledger Part 2