SAP S/4HANA FICO — Full Certification Course (24 Modules) | Upskeeling

Module 01 · Foundation · C_TS4FI

Introduction to SAP &
SAP S/4HANA

Build the conceptual and project-level foundation every SAP FICO consultant must have before configuration begins. Tested in C_TS4FI under the SAP S/4HANA Overview topic area.

Topics

~3 hrs

Study Time

Practice MCQs

~8%

Exam Weight

Module Progress0%

🎯

Learning Objectives

What you will master

Understand ERP concepts and the role of SAP in modern enterprises
Explain SAP S/4HANA architecture and its evolution from SAP ECC
Differentiate between implementation, support, rollout, and upgrade projects
Navigate SAP systems using both Classic GUI and SAP Fiori
Identify core SAP modules: FI, CO, MM, SD and how they integrate
Explain the role of Finance within integrated SAP processes
Distinguish master data, transaction data, and configuration data
Apply SAP Activate methodology concepts — all 6 phases
Explain DEV, QAS, and PRD system landscape and transport requests
Understand the SAP Implementation Guide (IMG – SPRO)

📖

Core Concepts

Encyclopedia — understand before you configure

Enterprise Resource Planning (ERP)

A software system that integrates all core business functions — finance, procurement, sales, manufacturing, HR — into a single unified platform with a shared database, enabling real-time data flow and centralized control across the organization.

SAP (Systems, Applications & Products in Data Processing)

Founded in 1972 in Germany, SAP is the world's leading enterprise software company. Its ERP platform is used by over 80% of the world's largest companies across 180+ countries. SAP S/4HANA is SAP's latest generation platform.

SAP S/4HANA

SAP's next-generation ERP platform built entirely on the SAP HANA in-memory database. It delivers real-time processing, a simplified data model with no aggregates or redundant tables, and a modern Fiori UX. Successor to SAP ECC (ERP Central Component). First released 2015.

Universal Journal (ACDOCA)

The single most important S/4HANA concept. In ECC, FI and CO had separate tables. In S/4HANA, all accounting entries — GL, AR, AP, AA, CO — are stored in one table: ACDOCA. This eliminates the need for period-end FI-CO reconciliation entirely.

🏢

What is ERP & Why SAP?

The business problem SAP solves

The Problem with Disconnected Systems

A growing organization using spreadsheets and standalone accounting tools faces reporting delays, data inconsistencies across departments, inability to get real-time financial visibility, and reconciliation errors between Finance, Sales, and Procurement. Manual reconciliation wastes time and introduces audit risk.

How SAP Solves This

SAP integrates all business functions into one system with a single source of truth. When a sales order is created in SD, it immediately affects inventory in MM and revenue in FI — automatically, in real time. No manual entries. No duplication. No delays.

📌

C_TS4FI Exam Tip: The exam often asks about the business driver for implementing SAP. Key answers include real-time reporting, process integration, statutory compliance, and eliminating data silos between Finance, Procurement, and Sales.

SAP ECC vs SAP S/4HANA — Key Differences

SAP ECC (Legacy)

Traditional RDBMS (Oracle, SQL Server)

Aggregates & index tables required

Complex data model, redundant tables

Batch-based reporting

SAP GUI only (classic Dynpro)

Separate New GL activation required

FI and CO reconcile periodically

End of maintenance: 2027

SAP S/4HANA (Current)

SAP HANA in-memory database only

Simplified data model — no aggregates

Universal Journal (ACDOCA) — single table

Real-time analytics & reporting

SAP Fiori — web-based, mobile-ready

New GL active by default

FI and CO unified — no reconciliation

Future roadmap through 2040+

Universal Journal (ACDOCA): In ECC, FI and CO had separate tables requiring periodic reconciliation. In S/4HANA, all accounting entries — GL, AR, AP, AA, CO — are stored in one table: ACDOCA. This is the most tested S/4HANA concept in the C_TS4FI exam.

🖥️

SAP Fiori — Modern User Interface

The UX layer of SAP S/4HANA

What is SAP Fiori?

SAP Fiori is SAP's design language and application framework for building role-based, responsive web applications. It replaces the traditional SAP GUI (Dynpro) for most business transactions. Fiori apps run in any modern browser and on mobile devices, making SAP accessible anywhere.

Fiori App Types — Three Categories

Transactional Apps: Used to create, change, or display business objects (post journals, create BPs). | Analytical Apps: Real-time reports and dashboards built on HANA Live views. | Fact Sheet Apps: Display key information about a business object (customer, material, vendor).

SAP Fiori Launchpad

🔍 Search in SAP...

🔔

Home

Finance

Controlling

Reports

Finance — My Apps

📒

Post General Journal Entry

📄

Display G/L Account Balances

🏦

Manage Bank Accounts

📤

Post Outgoing Payments

📥

Post Incoming Payments

📊

Financial Statements

⚙️

Manage Cost Centers

🔄

Run Payment Program

📌

Exam Tip: SAP Fiori runs on SAP Business Technology Platform (SAP BTP) or embedded in the S/4HANA system itself (embedded Fiori). Know the three Fiori app types — Transactional, Analytical, Fact Sheet — they are tested directly.

🖱️

SAP GUI Navigation

Classic GUI — still used for all SPRO configuration

Edit Chart of Accounts List — SAP S/4HANA [DEV — Client 100]

▶

■

↺

Transaction:

OB13

Chart of Accounts Overview

Properties

Additional Info

Edit Chart of Accounts List — GIM Group India

Chart of Accounts

CAIN

Description

Chart of Accounts – India

Maintenance Language

Length of G/L Account No.

Controlling Integration

Manual Creation of Cost Elements

Save (Ctrl+S)

Back (F3)

Cancel (F12)

Chart of Accounts CAIN created successfullyClient 100 | DEV | EN

Key / Action	Function
Enter (Return)	Confirm a selection or move to the next screen
F3	Back — go to previous screen
F12	Cancel — discard and exit
Ctrl + S	Save the current document or configuration
/n + T-Code	Navigate to a transaction in the same session
/o + T-Code	Open transaction in a new session window
/nend	Log off the SAP system

📌

Exam Tip: The prefix /n replaces the current session. /o opens a new session. SAP allows up to 6 sessions simultaneously per user. This is frequently tested.

📋

Types of SAP Projects

What consultants work on in the real world

🔧 Greenfield Implementation▼

A brand-new SAP implementation from scratch. The organization has no prior SAP system. All configuration, master data migration, testing, and training is done from the ground up. Longest project type — typically 12–24 months. Highest risk, highest reward for consultants.

🔄 System Conversion (Brownfield)▼

Converting an existing SAP ECC system to SAP S/4HANA. Historical data and configurations are migrated. Existing processes are mapped to S/4HANA equivalents. Custom code must be checked for compatibility. Most common globally as organizations migrate from ECC (end of mainstream maintenance: 2027).

🌍 Rollout Project▼

SAP already exists in one country or entity (the template). A rollout extends the template to new countries, plants, or company codes. Country-specific requirements (tax, language, currency) are configured locally while reusing global settings.

🛠️ Support / AMS▼

Post go-live support. Consultants handle incident tickets, service requests, and minor enhancements. Tickets are classified by priority: P1 (Critical), P2 (High), P3 (Medium), P4 (Low). Entry-level consultants often start in AMS roles.

⬆️ Upgrade Project▼

Moving from one SAP version to a higher version (e.g., S/4HANA 2020 to S/4HANA 2023). Focuses on regression testing, deprecated functionality analysis, and adopting new features.

🗺️

SAP System Landscape

DEV → QAS → PRD — the three-system landscape

🔨

DEV

Development

All configuration is done here. Consultants make changes in DEV. Transport requests are created and released from DEV.

🔎

QAS

Quality / Testing

Transports are imported here for testing. UAT (User Acceptance Testing) happens in QAS. No direct changes allowed.

🏭

PRD

Production

Live business system. Only approved, tested changes are imported here. Business transactions happen daily in PRD.

DEV → (Transport Request) → QAS → (Approval) → PRD

Transport Request (TR)

A package in SAP that contains configuration or development changes. TRs are released in DEV, imported to QAS for testing, then imported to PRD after approval. Transaction SE10 is used to manage transport requests. The Transport Management System (STMS) controls the movement process.

📌

Exam Tip: Configuration changes should NEVER be made directly in PRD. This is a golden rule in SAP projects. Changes must always flow DEV → QAS → PRD through transport requests. Direct PRD changes cause audit failures.

🧩

SAP Modules & Integration

FI is the financial backbone — all modules post to FI

Module	Full Name	Primary Function	FI Integration Point
FI	Financial Accounting	External financial reporting, GL, AR, AP, AA	Core module — all other modules post to FI
CO	Controlling	Internal management reporting, cost centers, profit centers	Real-time posting via Universal Journal (ACDOCA)
MM	Materials Management	Procurement, goods receipt, inventory management	GR/IR clearing, vendor invoice posting to AP
SD	Sales & Distribution	Sales orders, delivery, billing	Customer invoice posting to AR during billing
AA	Asset Accounting	Fixed asset management, depreciation	Sub-ledger of FI — posts to GL automatically
HR/HCM	Human Capital Management	Payroll, employee master	Payroll postings create FI documents
PP	Production Planning	Manufacturing orders, BOM	Goods issues/receipts create FI postings

📌

Exam Tip: In SAP S/4HANA, FI and CO share the Universal Journal (table ACDOCA). This means real-time FI-CO recording — no period-end reconciliation needed. This is a key difference from ECC and a frequently tested concept.

💾

Types of Data in SAP

Master data · Transaction data · Configuration data

Master Data

Long-lived business objects reused across transactions

Examples: G/L Account master, Customer master (Business Partner), Vendor master, Material master, Asset master, Cost Center, Profit Center. Master data is created once and reused across thousands of transactions. Incorrect master data causes systematic posting errors across all transactions that use it.

Transaction Data

Data generated from day-to-day business activity

Examples: Journal entries, Purchase orders, Sales orders, Payment documents, Goods receipts. Each transaction creates an accounting document with a unique document number per company code and fiscal year. Transaction data cannot be deleted — only reversed.

Configuration Data

System settings that control how SAP behaves

Examples: Chart of Accounts, Fiscal Year Variant, Document Types, Posting Keys, Tax Codes. Configuration is done through the Implementation Guide (SPRO / IMG). All config changes must go through DEV → QAS → PRD via transport requests.

🚀

SAP Activate Methodology

The official SAP implementation framework

What is SAP Activate? SAP's official project delivery methodology for S/4HANA implementations. It combines best practices, guided configuration, and agile delivery principles into a structured 6-phase framework.

Discover

Initial project scoping. Define business requirements, evaluate SAP Best Practices, identify gaps. Produce a business case. No system access yet.

Prepare

Project setup, team onboarding, infrastructure setup. SAP system provisioned. Project standards defined. Fit-to-standard analysis begins.

Explore

Fit-to-standard workshops with business. Delta requirements (gaps) documented. Blueprint / BBP produced. Key configuration decisions finalized.

Realize

System configuration in DEV. Integration testing. Data migration preparation. User training material developed. Iterative sprints (agile). Longest phase.

Deploy

UAT (User Acceptance Testing) in QAS. Final data migration cutover. Transport of config to PRD. Go-live preparation. Business sign-off.

Run

Post go-live support. Hypercare period (intensive support immediately after go-live). Transition to AMS. Continuous improvement.

📌

Exam Tip: Memorize: Discover → Prepare → Explore → Realize → Deploy → Run. Fit-to-Standard workshops occur in the Explore phase. System configuration happens in Realize. UAT and go-live in Deploy. This sequence is tested every year.

✍️

Assignment 1 — SAP & S/4HANA Fundamentals

GIM Group Business Scenario

Assignment — SAP & S/4HANA Fundamentals

Business Scenario

GIM Group is a growing manufacturing and distribution conglomerate currently managing accounting using spreadsheets and disconnected systems. Management experiences reporting delays, data inconsistencies, and limited real-time financial visibility. The organization plans to implement SAP S/4HANA Finance.

Task — Configure or Prepare:

Explain limitations of Excel-based accounting as organizations grow
Describe how SAP enables integration and real-time reporting vs. standalone systems
List at least 4 key differences between SAP ECC and SAP S/4HANA
Explain the role of SAP Fiori in modern SAP environments
Describe the purpose of DEV, QAS, and PRD in a 3-system landscape
Name all 6 SAP Activate phases in correct sequence with brief description of each
Define master data, transaction data, and configuration data with one example each

Expected Output

A 1–2 page document in clear business language
No technical jargon — write as if explaining to a Finance Director
Use GIM Group as the business context throughout

Validation Criteria

Correct explanation of SAP in non-technical terms
At least 4 accurate ECC vs S/4HANA differences identified
All 6 SAP Activate phases named in correct sequence
Clear understanding of the 3-system landscape and transport requests
Correct examples for all three data types

🧠

Knowledge Check — C_TS4FI Style MCQs

Select an option to reveal the answer & explanation

Q1Which database is mandatory for SAP S/4HANA? Select one correct answer.

Correct: C — SAP HANA. SAP S/4HANA exclusively runs on the SAP HANA in-memory database. Unlike SAP ECC which supported Oracle, SQL Server, DB2 and others, S/4HANA only supports SAP HANA. This is a fundamental architectural requirement and the most common exam trap in Module 1.

Q2In SAP S/4HANA, which single table stores all accounting entries across FI and CO, replacing multiple ECC tables?

Correct: B — ACDOCA. The Universal Journal table ACDOCA is the single source of truth in S/4HANA. In ECC, FI data was in BKPF/BSEG and CO data was in separate tables requiring periodic reconciliation. ACDOCA eliminates FI-CO reconciliation entirely.

Q3A consultant needs to make a configuration change to a Fiscal Year Variant. In which system should this be done first?

Correct: C — DEV. All configuration changes must follow the transport path DEV → QAS → PRD. Changes are made in DEV, packaged into a transport request, tested in QAS, then imported to PRD. Direct PRD changes are strictly prohibited and lead to audit failures.

Q4During which phase of SAP Activate methodology do Fit-to-Standard workshops take place?

Correct: B — Explore. Fit-to-Standard workshops occur in the Explore phase where business requirements are compared against SAP standard processes. Gap analysis is documented here. Configuration begins only in the Realize phase.

Q5Which of the following is an example of Master Data in SAP Finance?

Correct: C — A G/L Account. G/L Accounts, Business Partners (Customer/Vendor), Cost Centers, and Profit Centers are master data — created once and reused across thousands of transactions. A vendor invoice is transaction data. A Fiscal Year Variant is configuration data.

💼

Interview Preparation

Most frequently asked Module 1 questions

📋 Interview Q&A

Q1. What is SAP S/4HANA and how is it different from SAP ECC?

SAP S/4HANA is SAP's next-generation ERP system built entirely on the SAP HANA in-memory database. Unlike SAP ECC, which supported multiple databases and required separate FI and CO tables, S/4HANA uses the Universal Journal (ACDOCA) to store all accounting entries in one place, enabling real-time reporting without batch processing. It also introduces a simplified data model, mandatory Fiori user interface, and in-built analytics.

Q2. What is a Transport Request in SAP and why is it critical?

A Transport Request (TR) is a package that captures configuration or development changes made in DEV. It is released from DEV and imported into QAS for testing, then into PRD using the Transport Management System (STMS). Every consultant's configuration change is recorded in a TR to ensure auditability, traceability, and controlled movement across systems. Direct PRD changes without TRs violate SOX compliance requirements.

Q3. What are the 6 phases of SAP Activate?

SAP Activate has six phases: Discover (scoping and business case), Prepare (project setup and infrastructure), Explore (Fit-to-Standard workshops and gap analysis — Business Blueprint produced here), Realize (system configuration in DEV and integration testing — longest phase), Deploy (UAT in QAS, data migration cutover, go-live), and Run (post go-live hypercare and AMS support).

Q4. Explain the difference between master data, transaction data, and configuration data.

Master data is long-lived business objects reused across transactions — e.g., G/L accounts, customers, vendors, cost centers. Transaction data is generated from business activity and cannot be deleted — e.g., journal entries, invoices, payments. Configuration data controls how SAP behaves — e.g., Chart of Accounts, Fiscal Year Variant, Document Types. Configuration is maintained in IMG (SPRO) and transported via TRs through DEV→QAS→PRD.

Module 02 · Foundation · C_TS4FI

Enterprise Structure
in SAP S/4HANA

SAP represents an organization through a structured hierarchy called the Enterprise Structure. This is the first and most critical configuration step in any SAP implementation — all financial transactions depend on it.

Config Objects

~2 hrs

Study Time

Practice MCQs

~10%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand the Client concept — the highest level in SAP
Define and configure Company Code as the legal accounting entity
Understand Company (group level) vs Company Code distinction
Configure Business Areas for cross-company-code reporting
Define Segments for IFRS 8 compliant segment reporting
Assign Company Code to Company and understand the hierarchy
Know all T-codes: OX02, OX15, OX16, OX03 and their IMG paths

📖

Core Concepts

The organizational hierarchy in SAP FI

Client

The highest organizational level in SAP. A client is an independent, self-contained unit with its own master data, configuration, and user settings. Data cannot cross clients. In a 3-system landscape, each system (DEV, QAS, PRD) typically has one client for production use (e.g., Client 100). Client 000 is SAP's reference client.

Company Code

The MOST IMPORTANT organizational element in Financial Accounting. A Company Code represents a legally independent accounting unit with its own complete set of accounts. All financial postings — GL, AR, AP, AA — occur at the Company Code level. Each Company Code has its own Chart of Accounts, Fiscal Year Variant, Currency, and Posting Period Variant. T-code: OX02.

Company (Group Level)

Represents a corporate group for consolidation purposes. One Company can have multiple Company Codes assigned to it. The Company is used for group financial reporting and intercompany scenarios — NOT for day-to-day accounting postings. Do not confuse Company with Company Code. T-code: OX15.

Business Area

An organizational unit used for internal reporting across multiple Company Codes. Allows segment-wise P&L and Balance Sheet reporting. Optional in S/4HANA — Segments with Document Splitting are preferred for IFRS compliance. T-code: OX03.

Segment

Used for IFRS 8 compliant segment reporting in S/4HANA. Assigned to Profit Centers. With Document Splitting active, every accounting document is automatically attributed to the correct segment, enabling a complete Balance Sheet and P&L per segment.

⚙️

Step-by-Step Configuration

IMG paths, T-codes, and GIM Group scenario

Edit Company Code Data — SAP S/4HANA [DEV — Client 100]

▶

■

↺

Transaction:

OX02

Address

Currency

Additional Data

Technical Settings

Company Code: IN01 — GIM Group India Private Limited

Company Code

IN01

Company Name

GIM Group India Pvt Ltd

Country

Currency

INR

Language

Save (Ctrl+S)

Back (F3)

Cancel (F12)

Company Code IN01 saved — GIM Group India configuredClient 100 | DEV | EN

Define Company — Group Level

OX15

SPRO → Enterprise Structure → Definition → Financial Accounting → Define Company

Create company key GIMC (GIM Group Corporate). Enter the company name and address. This is the group-level entity used for consolidation. It is NOT where accounting postings occur — that is the Company Code.

Create Company Code

OX02

SPRO → Enterprise Structure → Definition → Financial Accounting → Edit, Copy, Delete, Check Company Code

Create Company Code IN01 for GIM Group India. Set Country = IN, Currency = INR, Language = EN. This is the legal entity where all FI postings (GL, AR, AP, AA) will be recorded. Key fields: 4-character Company Code key, country key (determines tax procedure), company currency.

Assign Company Code to Company

OX16

SPRO → Enterprise Structure → Assignment → Financial Accounting → Assign Company Code to Company

Link Company Code IN01 to Company GIMC. This creates the legal-to-group hierarchy. Multiple Company Codes (IN01, UK01, US01) can be assigned to one Company (GIMC) for group consolidation reporting.

Define Business Areas

OX03

SPRO → Enterprise Structure → Definition → Financial Accounting → Define Business Area

Create Business Areas: BA01 (Retail Division), BA02 (Manufacturing Division). Business Areas are cross-company-code organizational units for internal reporting. Optional in S/4HANA — Segments are preferred.

Define Segments

SPRO → Financial Accounting → Financial Accounting Global Settings → Segments → Define Segments

Create Segments: SEG_RET (Retail), SEG_MFG (Manufacturing). Segments are assigned to Profit Centers. With Document Splitting, every posting is automatically split to the correct segment for IFRS 8 compliance.

Assign Company Code to Fiscal Year Variant

OBY6

SPRO → Financial Accounting → Financial Accounting Global Settings → Ledgers → Fiscal Year and Posting Periods → Assign Company Code to a Fiscal Year Variant

Assign Fiscal Year Variant (e.g., V3 for April–March) to Company Code IN01. Without this assignment, no postings are possible in the Company Code.

📌

Exam Trap: Company Code ≠ Company. Company Code is the legal entity for accounting (where G/L, AR, AP, AA posts occur). Company is the group entity for consolidation only. Business Area is for cross-company-code internal reporting. Segment is for IFRS 8 segment reporting with Document Splitting. These four are frequently confused in MCQs.

🧩

Enterprise Structure Hierarchy

Understanding the full SAP organizational model

SAP Enterprise Structure — Top to Bottom

Client: Highest level. All data is client-specific. One SAP system can have multiple clients (DEV, QAS, PRD each have their own client 100).
Company: Group-level entity for consolidation (e.g., GIMC = GIM Group Corporate). Multiple Company Codes can belong to one Company.
Company Code: Legal accounting entity. All FI postings occur here. Has own CoA, FYV, currency (e.g., IN01 = GIM Group India).
Business Area: Cross-Company Code internal reporting division (e.g., BA01 = Retail, BA02 = Manufacturing). Optional.
Segment: IFRS 8 reporting unit assigned to Profit Centers via Document Splitting (e.g., SEG_RET, SEG_MFG). Preferred in S/4HANA.

🧠

Knowledge Check — C_TS4FI Style MCQs

Q1Which organizational element in SAP FI represents a legally independent accounting unit where all G/L, AR, AP, and AA postings occur?

Correct: C — Company Code. The Company Code is the central organizational element in FI. All financial postings occur at Company Code level. The Company is the group entity used for consolidation — it does NOT receive financial postings directly.

Q2What is the T-code used to create a Company Code in SAP S/4HANA?

Correct: C — OX02. OX02 is used to create and edit Company Codes. OX15 = Define Company (group). OX16 = Assign Company Code to Company. OX03 = Define Business Area.

Q3In SAP S/4HANA, which organizational element is used for IFRS 8 compliant segment reporting?

Correct: C — Segment. Segments are the preferred element in S/4HANA for IFRS 8 compliance. They are assigned to Profit Centers and, with Document Splitting active, every posting is automatically attributed to the correct segment for Balance Sheet and P&L reporting per segment.

Q4GIM Group has subsidiaries in India, UK, and USA. All three need to report separately AND consolidate at group level. How would you structure this in SAP?

Correct: B — Three Company Codes under one Company. Each country entity is a separate Company Code (legal accounting unit). All three are assigned to Company GIMC for group-level consolidation. This is the standard multi-national enterprise structure in SAP.

✍️

Assignment 2 — Enterprise Structure Configuration

GIM Group SAP S/4HANA Implementation

Assignment — Enterprise Structure Configuration

Business Scenario

GIM Group is implementing SAP S/4HANA and requires a single SAP system with clear legal entity separation and group-level reporting. GIM Group operates as GIM Group Corporate (GIMC) with one Indian legal entity (GIM Group India Pvt Ltd) as a starting point.

Task — Configure or Prepare:

Understand the role of the Client (conceptual clarity only — do not create)
Create Company Code IN01 for GIM Group India (Country: IN, Currency: INR)
Create Company GIMC at group level (GIM Group Corporate)
Assign Company Code IN01 to Company GIMC
Create two Business Areas: BA01 (Retail) and BA02 (Manufacturing)
Create two Segments: SEG_RET (Retail Segment) and SEG_MFG (Manufacturing Segment)

Expected Output

Company Code IN01 legally represented in SAP with correct country and currency
Company GIMC created and correctly linked to IN01
Business Areas BA01 and BA02 available for posting
Segments SEG_RET and SEG_MFG available for Profit Center assignment

Validation Criteria

Company Code IN01 can be selected during document entry
Company Code IN01 correctly assigned to Company GIMC
Business Areas available in document entry (Business Area field)
Segments visible in Profit Center configuration for assignment
Able to explain the difference between Company and Company Code clearly

💼

Interview Preparation

📋 Interview Q&A

Q1. What is the difference between a Company and a Company Code in SAP?

A Company represents a corporate group entity used for consolidation reporting (e.g., GIM Group Corporate — GIMC). A Company Code represents a legally independent entity where all financial accounting postings occur (e.g., GIM Group India Pvt Ltd — IN01). Multiple Company Codes can be assigned to one Company. All G/L, AR, AP, and AA postings happen at the Company Code level, not at the Company level.

Q2. Why is the Company Code the most important organizational element in FI?

The Company Code is the basic organizational unit of Financial Accounting. It represents a legally independent accounting unit that produces its own complete set of accounts (Balance Sheet, P&L, Trial Balance). All financial postings — GL journal entries, vendor invoices, customer invoices, asset postings — are linked to a specific Company Code. Without a correctly configured Company Code, no financial posting is possible in the system.

Q3. What is the purpose of Business Areas vs Segments in S/4HANA?

Business Areas are optional cross-Company Code organizational units used for internal divisional reporting. They were widely used in SAP ECC. In S/4HANA, Segments with Document Splitting are preferred because Segments provide IFRS 8 compliant segment reporting with automatically balanced line items per segment. Segments are assigned to Profit Centers, and with Document Splitting active, every accounting document is automatically split to the correct segment.

Module 03 · GL Configuration · C_TS4FI

Fiscal Year Variant &
Posting Period Variant

SAP enforces strict financial period control. Postings are only allowed in open, approved accounting periods — critical for compliance, month-end control, and audit trail integrity.

Config Objects

~2 hrs

Study Time

Practice MCQs

~8%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand the Variant Principle in SAP — configure once, assign to many
Configure Fiscal Year Variant (FYV) for calendar and non-calendar fiscal years
Understand year shift and period-date assignments in FYV
Assign Fiscal Year Variant to Company Code
Configure Posting Period Variant (PPV) and control open/closed periods per account type
Open and close posting periods for specific account types in OB52
Know all T-codes: OB29, OBY6, OBBO, OBBP, OB52 and their IMG paths
Understand special periods 13–16 for year-end closing adjustments

📖

Core Concepts

The Variant Principle and Period Control

Variant Principle

SAP uses a 'configure once, assign to many' approach called the Variant Principle. Instead of configuring settings per Company Code individually, you create a Variant (e.g., Fiscal Year Variant V3 for April–March) and assign it to one or multiple Company Codes. Changing the variant automatically updates all assigned Company Codes simultaneously — critical for multi-entity implementations.

Fiscal Year Variant (FYV)

Defines the financial year's structure: number of posting periods (usually 12 regular + up to 4 special), start/end dates for each period, and year shift values for non-calendar years. SAP delivers standard variants: K4 (Jan–Dec, calendar year), V3 (Apr–Mar, India), V6 (Jul–Jun). Custom variants can also be created (e.g., Z1). T-code: OB29.

Year Shift

For non-calendar fiscal years, a 'year shift' value tells SAP how calendar periods relate to fiscal periods. For an April–March year, periods April–December fall in the previous calendar year (year shift = -1) and periods January–March fall in the current calendar year (year shift = 0). This is essential for correct period determination.

Posting Period Variant (PPV)

Controls which periods are open for posting, per account type. Account types: A (Assets), D (Customers/Debtors), K (Vendors/Creditors), S (G/L Accounts), M (Materials), + (applies to all). Created in OBBO. Open/close periods in OB52. Assigned to Company Code in OBBP. The '+' account type acts as a default catch-all.

Special Periods (13–16)

Up to 4 special periods (periods 13–16) can be configured for year-end closing adjustments. These allow auditors or management to make adjustment entries AFTER the regular year-end close without reopening standard periods 1–12. Special periods must be explicitly opened in OB52 using the + account type or specific account types.

⚙️

Step-by-Step Configuration

OB29, OBY6, OBBO, OBBP, OB52

Maintain Fiscal Year Variant — SAP S/4HANA [DEV — Client 100]

▶

■

↺

Transaction:

OB29

Fiscal Year Variant

Periods

Year-End

Fiscal Year Variant: Z1 — GIM Group India (April–March)

FYV Key

Description

GIM India — April to March

No. of Posting Periods

No. of Special Periods

Calendar Year

No — Non-Calendar FY

Save (Ctrl+S)

Back (F3)

Cancel (F12)

Fiscal Year Variant Z1 created — April to March fiscal yearClient 100 | DEV | EN

Create Fiscal Year Variant

OB29

SPRO → Financial Accounting → Financial Accounting Global Settings → Ledgers → Fiscal Year and Posting Periods → Maintain Fiscal Year Variant

Create FYV key Z1 for GIM Group (April–March). Set 12 regular periods + 4 special periods. Define period start/end dates: Period 1 = April 1, Period 12 = March 31. Set year shift = -1 for periods April–December (these fall in the previous calendar year in SAP's counting).

Assign FYV to Company Code

OBY6

SPRO → Financial Accounting → Financial Accounting Global Settings → Ledgers → Fiscal Year and Posting Periods → Assign Company Code to a Fiscal Year Variant

Assign Fiscal Year Variant Z1 to Company Code IN01. This tells SAP which fiscal year calendar to use when posting documents in IN01. Critical: Without this assignment, no postings are possible in the Company Code.

Create Posting Period Variant

OBBO

SPRO → Financial Accounting → Financial Accounting Global Settings → Ledgers → Fiscal Year and Posting Periods → Posting Periods → Define Variants for Open Posting Periods

Create PPV key IN01 (best practice: use same key as Company Code). This is just the container — the actual period control (which periods are open) is maintained in OB52.

Assign PPV to Company Code

OBBP

SPRO → Financial Accounting → Financial Accounting Global Settings → Ledgers → Fiscal Year and Posting Periods → Posting Periods → Assign Variants to Company Code

Assign PPV IN01 to Company Code IN01. Now the period control from OB52 will apply when postings are attempted in IN01.

Open and Close Posting Periods

OB52

SPRO → Financial Accounting → Financial Accounting Global Settings → Ledgers → Fiscal Year and Posting Periods → Posting Periods → Open and Close Posting Periods

For each account type (+, A, D, K, S), define the open period range (From Period/Year → To Period/Year). To open Period 4 of FY2025 (July 2025 in V3): set From 4/2025 To 4/2025. During year-end: open Special Period 13 for closing adjustment entries. Keep previous periods closed.

Account Type	Code	Purpose	Example Usage
+	+ (Default)	Applies to ALL account types as catch-all	Open period 4/2025 for all accounts
Assets	A	Asset Accounting sub-ledger	Control period for fixed asset postings
Customers	D	AR sub-ledger (Debtors)	Control period for customer invoices
Vendors	K	AP sub-ledger (Kreditors)	Control period for vendor invoices
Materials	M	Materials Management MM	Control period for goods movements
G/L Accounts	S	General Ledger accounts	Control period for GL journal entries

📌

Exam Tip: The '+' account type in OB52 acts as a DEFAULT for all account types. If a specific D, K, or S rule is not defined, SAP falls back to '+'. If a period is closed, the system rejects the posting with error 'Posting period X/YYYY is not open for account type Y in ledger Z'. Know all 5 T-codes: OB29, OBY6, OBBO, OBBP, OB52 — they are tested individually.

🗓️

Fiscal Year Variants — Standard SAP Variants

Key variants to memorize for the exam

Variant	Description	Example Countries	Year Shift Needed?
K4	Calendar year Jan–Dec. Period 1=Jan, Period 12=Dec	USA, Germany, most EU	No — calendar year
V3	April–March. Period 1=Apr, Period 12=Mar	India (standard Indian FY)	Yes — Apr-Dec shift -1
V6	July–June. Period 1=Jul, Period 12=Jun	Australia, New Zealand	Yes — Jul-Dec shift -1
Z1	Custom — created by consultant for specific requirements	Any country	Depends on definition

📌

Exam Tip: For the GIM Group India scenario, the Fiscal Year Variant is April–March, matching the standard Indian Financial Year. The closest standard SAP variant is V3. The exam may ask you to identify the correct FYV for a given business scenario.

🧠

Knowledge Check — C_TS4FI Style MCQs

Q1GIM Group India follows an April–March fiscal year. Which standard SAP Fiscal Year Variant matches this requirement?

Correct: B — V3. V3 represents an April–March non-calendar fiscal year, which is the standard Indian financial year. K4 = calendar year Jan–Dec. V6 = July–June. V9 does not exist as a standard variant.

Q2Which T-code is used to open and close posting periods for specific account types?

Correct: D — OB52. OB52 is used to open and close posting periods by account type and variant. OBY6 = assign FYV to Company Code. OBBO = create PPV container. OBBP = assign PPV to Company Code.

Q3A consultant wants to make year-end audit adjustment entries AFTER period 12 has been closed. Which periods should be opened in OB52?

Correct: B — Special Periods 13–16. SAP provides up to 4 special periods (13–16) for year-end closing adjustments. These allow audit entries to be posted without reopening the regular fiscal periods 1–12, maintaining the integrity of month-end closing.

Q4In OB52, which account type setting acts as a default catch-all when no specific account type rule is defined?

Correct: C — + (All account types). The '+' entry in OB52 applies to ALL account types as a default. If a specific rule for D, K, S, A, or M is not defined for a period, SAP falls back to the '+' rule. Always maintain a '+' line as the baseline period control.

✍️

Assignment 3 — Fiscal Year & Posting Period Configuration

GIM Group — April–March Fiscal Year

Assignment — Fiscal Year & Posting Period Configuration

Business Scenario

GIM Group India (Company Code IN01) follows a non-calendar financial year from April to March (Indian financial year). The company requires strict control over posting periods — only the current month should be open for normal postings, and year-end adjustments must be possible without reopening regular periods.

Task — Configure or Prepare:

Create Fiscal Year Variant Z1 for April–March with 12 regular + 4 special periods
Set correct period dates (Period 1 = April 1 to April 30, Period 12 = March 1 to March 31)
Set year shift values: -1 for periods April–December, 0 for January–March
Assign Fiscal Year Variant Z1 to Company Code IN01 (OBY6)
Create Posting Period Variant IN01 (OBBO)
Assign PPV IN01 to Company Code IN01 (OBBP)
Open current posting period (e.g., Period 4/2025 for July) in OB52 for all account types
Verify that posting in a closed period (e.g., Period 3/2025) is rejected

Expected Output

FYV Z1 configured with correct April–March period dates
FYV Z1 assigned to Company Code IN01
Posting Period Variant IN01 created and assigned to IN01
Period 4/2025 open for posting — documents can be posted
Period 3/2025 closed — system rejects postings with appropriate error message

Validation Criteria

Correct period dates and year shift values in FYV Z1
Document posted successfully in Period 4/2025
Error message received when attempting to post in Period 3/2025
System correctly identifies fiscal period for documents posted in July (Period 4)
Able to explain the year shift concept for non-calendar fiscal years

💼

Interview Preparation

📋 Interview Q&A

Q1. What is the Variant Principle in SAP and how does it apply to Fiscal Year Variants?

The Variant Principle in SAP means 'configure once, assign to many.' You create a Fiscal Year Variant (e.g., V3 for April–March) once and then assign it to multiple Company Codes. All assigned Company Codes share the same fiscal year structure. If you need to change the fiscal year, you update the variant and all assigned Company Codes are updated simultaneously — no need to reconfigure each one individually.

Q2. What are special periods in SAP Finance and when are they used?

Special periods (13, 14, 15, 16) are additional posting periods available after the regular 12 fiscal periods. They are used for year-end closing adjustment entries — for example, audit adjustments, management provisions, or correction entries that need to be made after period 12 is closed but before the financial statements are finalized. Opening special periods in OB52 does not reopen the regular periods 1–12, maintaining the integrity of month-end closing.

Q3. A user reports they cannot post a vendor invoice for the previous month. What could be the cause and how do you fix it?

The most likely cause is that the previous posting period is closed in OB52. To investigate: check OB52 for the Posting Period Variant assigned to the user's Company Code and verify if the account type K (Vendors) or '+' (all types) is open for that period. To fix: open the required period in OB52 by setting the From Period/Year and To Period/Year to include the previous period. After the posting is complete, close the period again.

Module 04 · GL Configuration · C_TS4FI

Account Types, Document Types
& Posting Keys

Every financial transaction in SAP Finance is recorded as an accounting document. Account Types, Document Types, and Posting Keys form the control framework that governs how every posting is structured and validated.

Core Controls

~2 hrs

Study Time

Practice MCQs

~8%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand ledger and sub-ledger concepts in SAP Finance
Identify all five SAP account types and their purposes
Configure Document Types and understand what they control
Configure number ranges for accounting documents (FBN1)
Understand Posting Keys and how they control debit/credit and account type
Know the most important Document Types and Posting Keys by memory
Understand Field Status Groups and how they control screen fields
Know T-codes: OBA7, FBN1, OB41

📖

Core Concepts

Account Types, Document Types, and Posting Keys

Ledger vs Sub-Ledger

SAP Finance uses a two-tier structure. The General Ledger (GL) holds summary balances for all accounts. Sub-ledgers (AR, AP, Asset Accounting) hold detailed individual item records (individual customer invoices, individual vendor invoices, individual assets). Sub-ledgers are connected to GL via Reconciliation Accounts — when a sub-ledger posting is made, the reconciliation account in GL is automatically updated simultaneously.

Account Types

SAP uses 5 account types to categorize G/L accounts: A = Assets (Fixed Assets sub-ledger), D = Customers/Debtors (AR sub-ledger), K = Vendors/Kreditors (AP sub-ledger), M = Materials (Material Ledger in MM), S = General Ledger (G/L accounts). Account types control which sub-ledger an account belongs to and how it behaves in postings.

Document Type

Controls the properties of an accounting document: which account types can be posted in one document, the number range for document numbering, whether net posting is allowed, and whether exchange rate differences are posted. Each document type is assigned a number range. Configured in OBA7. Key document types use German abbreviations (SAP was founded in Germany).

Number Ranges

Each Document Type is assigned a Number Range that determines the sequence of document numbers. Number ranges can be Internal (system assigns the next number) or External (user specifies the number). Number ranges are company-code-specific and fiscal-year-specific. Maintained in FBN1. Must be created/extended for each new fiscal year.

Posting Key

A two-digit numeric code that controls: (1) which side of the account is posted (Debit or Credit), (2) which account type is allowed (A, D, K, M, S), and (3) the field status for that line item. Posting keys are less prominent in S/4HANA's Enjoy transaction screens but remain critical for understanding document structure. Configured in OB41.

📋

Key Document Types Reference

Memorize these — they appear in every C_TS4FI exam

Doc Type	German Meaning	Description	Account Types Allowed
SA	Sachkonten (GL accounts)	G/L account document (journal entry)	S (GL only)
KR	Kreditor Rechnung	Vendor Invoice	K + S
KZ	Kreditor Zahlung	Vendor Payment	K + S
KG	Kreditor Gutschrift	Vendor Credit Memo	K + S
DR	Debitor Rechnung	Customer Invoice	D + S
DZ	Debitor Zahlung	Customer Payment/Receipt	D + S
DG	Debitor Gutschrift	Customer Credit Memo	D + S
AB	Accounting/Buchung	General accounting document	All types
AA	Asset Accounting	Asset transaction document	A + S
RV	Revenue	SD billing document transfer to FI	D + S

📌

Exam Tip: The document type abbreviations are derived from German: K = Kreditor (Vendor), D = Debitor (Customer), R = Rechnung (Invoice), Z = Zahlung (Payment), G = Gutschrift (Credit), S = Sachkonto (GL account). Understanding the German logic helps memorize all document types quickly.

🔑

Posting Keys Reference

Debit/Credit control and account type assignment

Posting Key	Description	Dr/Cr	Account Type	Common Usage
01	Customer Invoice	Debit	D	AR invoice posting
11	Customer Credit Memo	Credit	D	AR credit note
06	Customer Payment Difference	Debit	D	Cash discount/payment diff
16	Customer Payment Difference	Credit	D	Cash discount/payment diff
21	Vendor Credit Memo	Credit	K	AP credit note
31	Vendor Invoice	Credit	K	AP invoice posting
25	Vendor Payment Difference	Credit	K	Cash discount/payment diff
35	Vendor Payment Difference	Debit	K	Cash discount/payment diff
40	G/L Account Debit	Debit	S	Standard GL journal entry
50	G/L Account Credit	Credit	S	Standard GL journal entry
70	Asset Debit (Acquis.)	Debit	A	Asset acquisition
75	Asset Credit (Retire)	Credit	A	Asset retirement

📌

Exam Trap: Posting key 31 is used for Vendor Invoices — the vendor account is CREDITED (liability increases). Posting key 01 is used for Customer Invoices — the customer account is DEBITED (asset/receivable increases). The debit/credit direction for sub-ledger accounts (D, K) is counterintuitive and frequently tested.

⚙️

Configuration Steps

OBA7 and FBN1

Maintain Document Types — SAP S/4HANA [DEV — Client 100]

▶

■

↺

Transaction:

OBA7

Document Types

Properties

Number Ranges

Document Type: KR — Vendor Invoice (Kreditor Rechnung)

Document Type

Description

Vendor Invoice

Number Range

Account Types Allowed

K, S

Net Document Type

(blank)

Reverse Document Type

Save (Ctrl+S)

Back (F3)

Cancel (F12)

Document Type KR configured — Vendor InvoiceClient 100 | DEV | EN

Define Document Types

OBA7

SPRO → Financial Accounting → Financial Accounting Global Settings → Document → Document Types → Define Document Types

Review and configure document types for GIM Group. Key settings per document type: Description, Number Range assignment, Account Types Allowed (checkboxes for A/D/K/M/S), Reverse Document Type (for reversals), Net Document Type (for net posting). Verify KR (Vendor Invoice), DR (Customer Invoice), SA (GL document), AB (General).

Define Number Ranges for Documents

FBN1

Financial Accounting → Financial Accounting Global Settings → Document → Document Number Ranges → Define Document Number Ranges for Entry View

Create number ranges for each document type in Company Code IN01. Example: Number Range 01 = 0100000000–0199999999 (Internal, GL documents SA). Number Range 19 = 1900000000–1999999999 (Internal, Vendor documents KR, KZ). Extend number ranges to the new fiscal year each year.

Configure Posting Keys

OB41

SPRO → Financial Accounting → Financial Accounting Global Settings → Document → Line Item → Controls → Define Posting Keys

Posting keys are SAP-delivered — rarely need modification. Review field status for each posting key to understand which fields are mandatory (M), optional (O), or suppressed (S) for each line item type. Custom posting keys can be created if required for specific business scenarios.

📌

Important: In SAP S/4HANA Enjoy transaction screens (FB50, FB60, FB70), the posting key is often determined automatically by the system based on the account type selected. However, for F-01 (general document entry) and in ABAP programs, explicit posting keys are still required. The exam tests knowledge of posting keys extensively.

🧠

Knowledge Check — C_TS4FI Style MCQs

Q1A vendor invoice needs to be posted in SAP Finance. Which document type should be used?

Correct: C — KR (Kreditor Rechnung = Vendor Invoice). SA = G/L account document (journal entry). AB = General accounting document (all account types). DR = Customer invoice. KR is specifically for vendor invoices and allows account types K (Vendor) and S (G/L) — not D (Customer).

Q2When posting a standard G/L journal entry (debit an expense account, credit a bank account), which posting keys are used?

Correct: C — 40 (G/L Debit) and 50 (G/L Credit). Posting key 40 = G/L Debit for account type S. Posting key 50 = G/L Credit for account type S. These are used for standard journal entries between G/L accounts.

Q3What is the purpose of a Number Range in the context of Document Types?

Correct: B — Determines the document number sequence. Number ranges define the pool of document numbers available for each document type. They can be internal (system assigns) or external (user enters). Number ranges are company-code-specific and fiscal-year-specific, maintained in FBN1.

Q4A consultant notices that when posting a vendor invoice (KR), the field 'Asset' is greyed out and cannot be entered. What controls this behavior?

Correct: B — Document Type KR does not allow account type A (Assets). Document Type KR is configured to allow account types K (Vendor) and S (G/L) only. Since Asset accounts (type A) are not permitted in KR, the Asset field is suppressed. To post to an asset account, document type AA or AB would be required.

Q5What is the difference between a Ledger and a Sub-ledger in SAP Finance?

Correct: B — GL holds summaries; Sub-ledgers hold details. The General Ledger holds summary balances. Sub-ledgers (AR for customers, AP for vendors, AA for assets) hold individual item details. They are connected via Reconciliation Accounts — every sub-ledger posting automatically updates the corresponding reconciliation account in the GL in real time.

✍️

Assignment 4 — Accounting Document Basics

GIM Group Payment Scenario

Assignment — Accounting Document Basics

Business Scenario

GIM Group India (IN01) needs to process daily financial transactions. The accounting team receives a vendor invoice for office rent of INR 50,000 from vendor HDFC Properties. Payment will be made from the HDFC bank account. The Finance Controller needs to understand which SAP document type, posting keys, and accounts are involved.

Task — Configure or Prepare:

Identify the correct Document Type for the vendor invoice posting
Identify the posting keys for the vendor account line and the expense account line
Identify which account type is used for the vendor account (K, D, S, A, or M)
Determine which account is debited (Rent Expense GL account) and which is credited (Vendor account)
Identify the correct Document Type for the subsequent vendor payment
Identify the posting keys for the payment: vendor debit and bank credit

Expected Output

Correct document type selected: KR for vendor invoice
Correct posting keys identified: 31 (vendor credit/invoice) and 40 (expense debit)
Account types correctly classified: K for vendor, S for GL accounts
Correct posting logic: Dr Rent Expense (40), Cr Vendor (31)
Payment: KZ document type, Dr Vendor (25), Cr Bank (50)

Validation Criteria

Correct document type for vendor invoice: KR
Correct posting key for vendor in invoice: 31 (Credit)
Correct posting key for expense account: 40 (Debit)
Correct document type for payment: KZ
Ability to explain the document structure clearly in an interview

💼

Interview Preparation

📋 Interview Q&A

Q1. What does a Document Type control in SAP Finance?

A Document Type controls: (1) which account types can be posted in one document (e.g., KR allows only K and S), (2) the number range for document numbering, (3) whether net posting is allowed, (4) the reverse document type for cancellations, and (5) whether the document is relevant for payment (payment document type). Document Types are configured in OBA7 and are a key organizational control in SAP Finance.

Q2. Explain Posting Keys and their significance.

Posting keys are two-digit numeric codes (01–99) that control three things for each line item: (1) whether the line is a Debit or Credit, (2) which account type is allowed (A, D, K, M, S), and (3) the field status for that line item (which fields are mandatory, optional, or suppressed). Key posting keys to memorize: 40/50 for G/L Debit/Credit, 01/11 for Customer Invoice/Credit, 31/21 for Vendor Invoice/Credit, 70/75 for Asset Debit/Credit.

Q3. What is a Reconciliation Account and how does it connect sub-ledgers to the General Ledger?

A Reconciliation Account is a G/L account that is automatically updated whenever a posting is made in the corresponding sub-ledger (AR, AP, or Asset Accounting). When a vendor invoice (KR) is posted, the vendor account in the AP sub-ledger is credited AND the Trade Payables Reconciliation Account in the GL is simultaneously credited. Direct postings to Reconciliation Accounts are blocked — all postings must go through the sub-ledger. This ensures the GL and sub-ledgers are always in sync without manual reconciliation.

Module 05 · GL Configuration · C_TS4FI

G/L Accounts &
Document Splitting

The General Ledger is the financial backbone of SAP. Document Splitting ensures segment-level Balance Sheet and P&L reporting — mandatory for IFRS 8 compliance in S/4HANA.

Config Steps

~3 hrs

Study Time

Practice MCQs

~12%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand Chart of Accounts types — Operative, Country, Group CoA
Configure Chart of Accounts in OB13 and assign to Company Code via OBY6
Define G/L Account Groups with number ranges in OBD4
Configure the Retained Earnings Account (OB53) for year-end carryforward
Create G/L Account master records at CoA level and Company Code level (FS00)
Configure and activate Document Splitting for Profit Center/Segment reporting
Understand Field Status Groups and their effect on document entry screens
Know T-codes: OB13, OBY6, OBD4, OB53, FS00, FSP0, FSS0

📖

Core Concepts

Chart of Accounts, G/L Master Data, Document Splitting

Chart of Accounts (CoA)

The master list of all G/L accounts. Three types: Operative CoA — used for day-to-day postings (e.g., CAIN for India). Country CoA — parallel account numbers for local statutory reporting. Group CoA — for group consolidation. One Company Code can only have ONE operative CoA. Multiple Company Codes can share the same CoA. Created in OB13.

Account Groups

Control the number range and field status for G/L account master records. Every G/L account must be assigned to one account group. Examples: BASC (Balance Sheet accounts 100000–199999), PLAC (P&L accounts 200000–299999), CASH (Cash/Bank 110000–119999). Configured in OBD4. The account group also controls whether the account is a Balance Sheet type or P&L type.

Retained Earnings Account

At fiscal year-end, SAP automatically transfers the net P&L result (profit or loss) to a designated Retained Earnings account in the Balance Sheet. Configured in OB53 — assign P&L account type identifier 'X' to a G/L account (e.g., 300000). During year-end balance carryforward (F.16), all P&L accounts are zeroed and the net is posted to 300000. Only ONE retained earnings account per CoA.

Document Splitting

An S/4HANA feature that automatically splits accounting line items by a characteristic — Profit Center or Segment. Enables a complete, balanced Balance Sheet and P&L per Profit Center/Segment for IFRS 8. SAP generates zero-balance clearing lines automatically. Configured in SPRO under Document Splitting.

Field Status Group

Controls which fields are mandatory, optional, or suppressed on accounting document line items. Assigned to each G/L account master record. Example: G001 (GL accounts — cost center optional), G005 (bank accounts — value date mandatory). Field status from the Posting Key and from the G/L account are combined — the more restrictive rule wins.

⚙️

Step-by-Step Configuration

Create G/L Account — FS00 — SAP S/4HANA [DEV — Client 100]

▶

■

↺

Transaction:

FS00

Type/Description

Control Data

Create/Bank/Interest

G/L Account 113000 — HDFC Bank Current Account (IN01)

G/L Account

113000

Chart of Accounts

CAIN

Account Group

CASH

Balance Sheet Account

Yes

Short Description

HDFC Current Account

Company Code

IN01

Account Currency

INR

Open Item Management

Line Item Display

Yes

Field Status Group

G005

Save (Ctrl+S)

Back (F3)

Cancel (F12)

G/L Account 113000 created in CAIN and Company Code IN01Client 100 | DEV | EN

Create Chart of Accounts

OB13

SPRO → Financial Accounting → GL Accounting → GL Accounts → Master Data → Preparations → Edit Chart of Accounts List

Create CoA key CAIN (Chart of Accounts India). Set: Maintenance language = EN, Length of G/L account number = 6 digits. This is the Operative CoA that will be used for all daily postings in GIM Group India.

Assign CoA to Company Code

OBY6

SPRO → Financial Accounting → GL Accounting → GL Accounts → Master Data → Preparations → Assign Company Code to Chart of Accounts

Assign operative CoA CAIN to Company Code IN01. A Company Code can only have ONE operative CoA. Without this assignment, no G/L accounts can be created for IN01 and no postings are possible.

Define Account Groups

OBD4

SPRO → Financial Accounting → GL Accounting → GL Accounts → Master Data → Preparations → Define Account Group

Create: BASC (Balance Sheet 100000–199999), PLAC (P&L 200000–299999), CASH (Cash/Bank 110000–119999), RECC (Reconciliation Accounts 140000–169999). Each group controls number range and field status for G/L account creation screens.

Configure Retained Earnings Account

OB53

SPRO → Financial Accounting → GL Accounting → GL Accounts → Master Data → Preparations → Define Retained Earnings Account

Assign P&L account type X to G/L account 300000 (Retained Earnings / Reserves & Surplus). When F.16 (year-end balance carryforward) is run, all P&L accounts are zeroed and the net profit/loss is posted to 300000.

Create G/L Account Master

FS00

Accounting → Financial Accounting → General Ledger → Master Records → G/L Accounts → Individual Processing → Centrally

Create required G/L accounts for GIM Group: 110000 (Cash), 113000 (HDFC Bank), 141000 (Trade Receivables — Reconciliation type D), 161000 (Trade Payables — Reconciliation type K), 200000 (Sales Revenue — P&L type P), 400000 (Office Rent Expense — P&L type P, cost element category 1).

Activate Document Splitting

SPRO → Financial Accounting → GL Accounting → Business Transactions → Document Splitting → Activate Document Splitting

Enable Document Splitting for Company Code IN01. Splitting method: 0000000012 (standard S/4HANA). Splitting characteristic: Profit Center. Activate Inheritance. With this active, every accounting document line is automatically attributed to a Profit Center and Segment.

📌

Exam Tip: The 'Balance' node in the Financial Statement Version (F.01 report) should always equal ZERO — Assets = Liabilities + Equity. If it is non-zero, one or more G/L accounts with balances are not assigned in the FSV. All active G/L accounts must be assigned to FSV nodes. Document Splitting generates zero-balance clearing lines automatically — these are not manual entries.

🧠

Knowledge Check — C_TS4FI MCQs

Q1Which T-code is used to create and maintain a G/L Account master record centrally in SAP S/4HANA?

Correct: C — FS00. FS00 is the central G/L account maintenance transaction (CoA + Company Code data in one screen). OB13 = create Chart of Accounts. OBD4 = define Account Groups. OB53 = configure Retained Earnings account.

Q2At fiscal year-end, transaction F.16 (Balance Carryforward) is run. What happens to P&L account balances?

Correct: B — Zeroed and transferred to Retained Earnings (OB53 account). F.16 zeros all P&L (Income Statement) account balances and posts the net profit/loss to the Retained Earnings account. Balance Sheet accounts carry their closing balances forward as new year opening balances.

Q3A user tries to post directly to G/L account 141000 (Trade Receivables Reconciliation Account) and receives an error. Why?

Correct: B — Direct posting to reconciliation accounts is blocked. Reconciliation accounts link sub-ledgers (AR, AP, AA) to the GL. Direct posting would break the synchronization between the sub-ledger and GL. All postings must go through the sub-ledger transactions (FB60 for vendors, FB70 for customers).

Q4Document Splitting in SAP S/4HANA primarily enables which capability?

Correct: B — Segment-level Balance Sheet and P&L for IFRS 8. Document Splitting distributes every document line item to a Profit Center and Segment. This enables a complete, balanced financial statement per segment — required for IFRS 8 (Segment Reporting) compliance.

Q5For G/L account 400000 (Office Rent Expense — P&L type), which additional CO property must be assigned for FI-CO integration to work?

Correct: B — Cost element category. P&L accounts that should post to Controlling (CO) must have a cost element category assigned in the G/L account master (FS00). Category 1 = primary costs. Without this, postings to account 400000 will succeed in FI but will NOT update any CO cost center or profit center.

✍️

Assignment 5 — G/L Master & Reporting Setup

GIM Group Chart of Accounts

Assignment — G/L Master & Reporting Setup

Business Scenario

GIM Group India needs to set up the Chart of Accounts and create the foundational G/L accounts for financial reporting. The Finance team requires Balance Sheet accounts, P&L accounts, and reconciliation accounts to be available before any transactions can be posted.

Task — Configure or Prepare:

Create Chart of Accounts CAIN with G/L account length 6 digits and assign to IN01
Create Account Groups: BASC (100000–199999 Balance Sheet), PLAC (200000–299999 P&L), CASH (110000–119999), RECC (140000–169999 Reconciliation)
Configure Retained Earnings Account: assign P&L type X to G/L account 300000
Create G/L accounts via FS00: 110000 (Cash), 113000 (HDFC Bank Current), 141000 (Trade Receivables — Reconciliation, account type D), 161000 (Trade Payables — Reconciliation, account type K), 200000 (Sales Revenue, P&L type P), 400000 (Office Rent, P&L type P, Cost Element Category 1)
Activate Document Splitting for IN01 with Profit Center as splitting characteristic
Post a test journal entry (FB50): Dr 400000 INR 50,000 / Cr 113000 INR 50,000 — verify Profit Center split

Expected Output

CoA CAIN successfully assigned to IN01
All 6 G/L accounts created and available for posting
141000 and 161000 correctly configured as reconciliation accounts (blocked for direct posting)
Document Splitting active — system generates split lines for multi-PC postings

Validation Criteria

G/L accounts created with correct account types (B=Balance Sheet, P=P&L)
Reconciliation accounts 141000 and 161000 cannot be posted to directly
F.16 transfers P&L to account 300000 at year-end
Document Splitting generates correct Profit Center attribution on test posting

💼

Interview Preparation

📋 Interview Q&A

Q1. What is the difference between the CoA level and Company Code level of a G/L account?

A G/L account master has two sections. The CoA Level (maintained in FSP0) contains settings applicable across all Company Codes using that CoA — account number, account group, description, and account type (B=Balance Sheet or P=P&L). The Company Code Level (maintained in FSS0) contains company-specific settings — currency, tax category, open item management, line item display, field status group, and CO relevance. Both levels must be maintained before a G/L account can accept any postings.

Q2. What is Document Splitting and why is it important for IFRS 8 reporting?

Document Splitting automatically distributes accounting document line items across Profit Centers and Segments so that each segment's entries balance independently. This enables a complete, balanced Balance Sheet and P&L per segment — required for IFRS 8 (Segment Reporting) compliance. In S/4HANA, Document Splitting works through the Universal Journal (ACDOCA) and generates zero-balance clearing lines automatically. No manual splitting is needed.

Q3. What happens if a G/L account with a balance is not assigned in the Financial Statement Version?

If a G/L account with a balance is not assigned to any node in the Financial Statement Version (FSV configured in OB58), that account's balance will appear in the 'Not Assigned' section when running the financial statement report (F.01). This means the 'Balance' node of the FSV will not equal zero — indicating Assets ≠ Liabilities + Equity. This is a configuration error. All active G/L accounts must be assigned to appropriate FSV nodes for correct financial statement reporting.

Module 06 · GL Configuration · C_TS4FI

G/L Tolerances &
Default User Parameters

SAP enforces financial discipline through posting limit controls and automatic default values. These mechanisms prevent posting errors, enforce authorization limits, and speed up daily transaction entry.

Config Objects

~1.5 hrs

Study Time

Practice MCQs

~6%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Configure G/L Tolerance Groups for maximum posting amounts (OBA4)
Configure Customer and Vendor Tolerance Groups for payment differences (OBA3)
Assign Tolerance Groups to SAP user master records (SU01)
Understand the meaning of a blank (empty) tolerance group
Configure default user parameters BUK, KOA, GJA in SU3 and SU01
Know the German parameter IDs and what they pre-fill

📖

Core Concepts

Tolerances and User Defaults

G/L Tolerance Group

Restricts the maximum amounts a user can post: maximum document amount, maximum amount per open item, and maximum permitted cash discount percentage. Configured in OBA4. A blank (empty) tolerance group means NO limits — the user can post any amount. Company-code-specific. Assigned to users in SU01.

Customer / Vendor Tolerance Group

Controls the maximum permitted payment difference amounts during clearing — the amount SAP will automatically write off to a gain/loss account. Configured in OBA3. Example: if a customer pays INR 9,990 for a INR 10,000 invoice, the INR 10 difference can be auto-posted to a rounding difference account if within the tolerance.

Default User Parameters

User-level settings that pre-populate fields automatically during transaction entry. Key parameters: BUK = Buchungskreis (Company Code), KOA = Kostenrechnungskreis (Controlling Area), GJA = Geschäftsjahr (Fiscal Year). Maintained by the user in SU3 (own data) or by administrators in SU01.

⚙️

Step-by-Step Configuration

OBA4, OBA3, SU3

Define Tolerance Groups — G/L Accounts — SAP S/4HANA [DEV — Client 100]

▶

■

↺

Transaction:

OBA4

Tolerance Group

Posting Limits

Discount Tolerance

Tolerance Group: JNRA — Junior Accountant (Company Code IN01)

Company Code

IN01

Tolerance Group

JNRA

Max Document Amount

100,000 INR

Max Per Open Item

50,000 INR

Max Cash Discount %

2.0%

Max Payment Difference

500 INR

Save (Ctrl+S)

Back (F3)

Cancel (F12)

Tolerance Group JNRA saved — junior accountant limits appliedClient 100 | DEV | EN

Create G/L Tolerance Groups

OBA4

SPRO → Financial Accounting → Financial Accounting Global Settings → Document → Tolerance Groups → Define Tolerance Groups for G/L Accounts

Create group JNRA (Junior Accountant, IN01): Max document = 100,000 INR, Max per item = 50,000 INR, Max cash discount = 2%. Create group SNRA (Senior): leave all limits BLANK = unlimited posting authority.

Create Customer/Vendor Tolerance Groups

OBA3

SPRO → Financial Accounting → Financial Accounting Global Settings → Business Transactions → Open Item Clearing → Clearing Differences → Define Tolerance Groups for Employees

Configure maximum permitted clearing difference: Max amount = 50 INR, Max percentage = 1%. SAP auto-posts differences within this tolerance to a gain/loss account during clearing.

Assign Tolerance Group to User

SU01

System Administration → User Maintenance → Users

Open user JUSER01 in SU01. In the 'Logon Data' tab, assign Tolerance Group = JNRA. Save. Now JUSER01 cannot post documents exceeding 100,000 INR. Leave tolerance blank for senior users = no limits.

Set Default User Parameters

SU3

SAP Easy Access → System → User Profile → Own Data

Each user sets in SU3 → Parameters tab: BUK = IN01 (Company Code auto-fills in FB50/FB60), KOA = GIM1 (Controlling Area auto-fills), GJA = 2025 (Fiscal Year auto-fills). Saves significant time in daily posting transactions.

Parameter ID	German Meaning	English Meaning	Pre-fills Field
BUK	Buchungskreis	Company Code	Company Code in all FI transactions
KOA	Kostenrechnungskreis	Controlling Area	Controlling Area in CO transactions
GJA	Geschäftsjahr	Fiscal Year	Fiscal Year in reporting transactions
GSB	Geschäftsbereich	Business Area	Business Area in FI transactions
VKO	Verkaufsorganisation	Sales Organization	Sales Org in SD transactions

📌

Exam Tip: A blank tolerance group = UNLIMITED posting authority (no restrictions). OBA4 = G/L tolerance groups. OBA3 = Customer/Vendor tolerance groups. BUK = Company Code (Buchungskreis in German). SU3 = user maintains own parameters. SU01 = admin maintains other users' parameters. These are frequently tested.

🧠

Knowledge Check

Q1A junior accountant tries to post a vendor invoice for INR 200,000. Their tolerance group JNRA has a maximum document amount of INR 100,000. What happens?

Correct: B — System rejects the posting. Tolerance groups enforce hard limits. When the posting amount exceeds the configured maximum, the system immediately rejects it with an error message. The user must get a senior accountant with higher limits to post, or the tolerance group must be increased.

Q2What does assigning a blank (empty) tolerance group to a SAP user mean?

Correct: B — Unlimited posting authority. A blank/empty tolerance group means no restrictions whatsoever. Senior finance staff and system administrators typically have a blank tolerance group. This is the most frequently tested fact about tolerance groups.

Q3Which T-code allows a user to set their OWN default parameters (Company Code, Controlling Area)?

Correct: C — SU3. SU3 (Own Data) lets users set personal default parameters in the Parameters tab. SU01 is the administrator transaction for managing other users. OBA4 configures tolerance groups. PFCG manages authorization roles.

Q4Which parameter ID pre-fills the Company Code field (Buchungskreis) during document entry?

Correct: C — BUK. BUK = Buchungskreis (German for Company Code). KOA = Controlling Area (Kostenrechnungskreis). GJA = Fiscal Year (Geschäftsjahr). SAP uses German abbreviations for parameter IDs — understanding their German origin helps memorize them.

💼

Interview Preparation

📋 Interview Q&A

Q1. What is a Tolerance Group in SAP Finance and how does it control postings?

A Tolerance Group defines the maximum amounts a user can post: the maximum total document amount, the maximum amount per open item line, the maximum cash discount percentage they can grant, and the maximum permitted payment difference for clearing. These limits are configured in OBA4 per company code and assigned to users in SU01. If a user attempts to exceed their tolerance limit, SAP rejects the posting with an error message. A blank tolerance group means no restrictions — unlimited authority.

Q2. Why are default user parameters important in SAP Finance?

Default user parameters (configured in SU3/SU01) pre-populate commonly used fields during transaction entry — such as Company Code (BUK = IN01), Controlling Area (KOA = GIM1), and Fiscal Year (GJA = 2025). This significantly reduces data entry time for finance staff who work with the same company code every day, minimizes input errors caused by selecting the wrong company code, and ensures consistency across the team. For a finance department processing hundreds of documents daily, these defaults provide meaningful efficiency gains.

Module 07 · Controlling · C_TS4FI

Controlling Area &
FI–CO Integration

Financial Accounting supports external reporting requirements. Controlling supports internal management reporting. The Controlling Area is the foundation of FI-CO integration — enabling cost tracking, profitability analysis, and real-time management decisions.

Config Objects

~3 hrs

Study Time

Practice MCQs

~10%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Configure the Controlling Area organizational element (OKKP)
Assign Company Code to Controlling Area (OX19)
Activate Profit Center Accounting within the Controlling Area
Create Cost Center Standard Hierarchy and Cost Centers (KS01, OKEON)
Create Profit Center Standard Hierarchy and Profit Centers (KE51)
Assign default Profit Centers to G/L accounts
Understand Cost Elements and their categories in S/4HANA
Know T-codes: OKKP, OX19, KS01, KE51, KSB1, KE5Z

📖

Core Concepts

FI vs CO — Why Both Exist

Controlling Area

The central organizational unit in Controlling (CO). One Controlling Area can span multiple Company Codes (cross-company-code controlling). The Controlling Area MUST share the same Chart of Accounts AND the same Fiscal Year Variant as all assigned Company Codes — a mismatch prevents the assignment. Configured in OKKP.

Cost Center

Organizational unit representing a location of cost responsibility — a department, machine, or cost pool. Collects COSTS ONLY (no revenues). Arranged in a mandatory Standard Hierarchy (one per Controlling Area). Examples: CC_HR (HR Dept), CC_IT (IT Dept), CC_MFG (Manufacturing). Created in KS01.

Profit Center

Organizational unit for internal profitability analysis. Collects BOTH revenues AND costs to produce an internal P&L view. In S/4HANA with Document Splitting, Profit Centers are mandatory on all postings. Examples: PC_RETAIL (Retail Division), PC_MFG (Manufacturing). Created in KE51.

Cost Elements in S/4HANA

In S/4HANA, cost elements ARE G/L accounts — the CO properties (cost element category) are maintained directly in the G/L account master (FS00). There is no separate cost element master as in ECC. Category 1 = Primary costs. Category 11 = Revenue. Category 21 = Internal settlement. Category 42 = Assessment.

FI vs CO — The Core Distinction

FI (Financial Accounting) answers: 'What is the company's external financial position?' — produces Balance Sheet and P&L for shareholders, banks, and tax authorities. Follows statutory accounting standards.

CO (Controlling) answers: 'Where is money spent internally and who is responsible?' — produces Cost Center reports, Profit Center P&L for internal management. Follows management accounting principles.

S/4HANA key fact: The Universal Journal (ACDOCA) stores both FI and CO in ONE table — zero reconciliation needed.

S/4HANA vs ECC: In ECC, FI and CO had separate database tables requiring periodic KALC reconciliation. In S/4HANA, ACDOCA stores both FI and CO data in a single table. Every cost-relevant FI posting instantly and automatically updates CO — no batch job, no reconciliation. This is a key exam concept.

⚙️

Step-by-Step Configuration

Maintain Controlling Area — OKKP — SAP S/4HANA [DEV — Client 100]

▶

■

↺

Transaction:

OKKP

Basic Data

Activate Components

Assignment

Currencies

Controlling Area: GIM1 — GIM Group India

Controlling Area

GIM1

Description

GIM Group — India Controlling Area

Chart of Accounts

CAIN

Currency Type

10 (Company Code currency)

Fiscal Year Variant

Profit Center Accounting

Activated

Cost Center Accounting

Activated

Save (Ctrl+S)

Back (F3)

Cancel (F12)

Controlling Area GIM1 saved with Profit Center Accounting activeClient 100 | DEV | EN

Create Controlling Area

OKKP

SPRO → Controlling → General Controlling → Organization → Maintain Controlling Area

Create Controlling Area GIM1. Critical settings: Chart of Accounts = CAIN (must match Company Codes assigned), Fiscal Year Variant = Z1 (must match), Currency Type = 10 (Company Code currency INR). Activate: Cost Center Accounting = Active, Profit Center Accounting = Active.

Assign Company Code to Controlling Area

OX19

SPRO → Enterprise Structure → Assignment → Controlling → Assign Company Code to Controlling Area

Assign IN01 to GIM1. This enables FI-CO integration — all cost-relevant FI postings in IN01 will automatically update CO in GIM1 through ACDOCA.

Create Cost Center Standard Hierarchy

OKEON

SPRO → Controlling → Cost Center Accounting → Master Data → Cost Centers → Define Standard Hierarchy

Create mandatory Standard Hierarchy GIM1_HIER. Structure: GIM1_HIER → Admin (CC_FIN, CC_HR, CC_IT) → Operations (CC_MFG, CC_WARE). All Cost Centers must be assigned to a hierarchy node.

Create Cost Centers

KS01

Accounting → Controlling → Cost Center Accounting → Master Data → Cost Centers → Individual Processing → Create

Create: CC_FIN (Finance Dept), CC_HR (Human Resources), CC_IT (IT Dept), CC_MFG (Manufacturing). Set valid-from date, responsible person, cost center category (A=Administration, P=Production), and Profit Center assignment.

Create Profit Center Standard Hierarchy and Profit Centers

KE51

Accounting → Controlling → Profit Center Accounting → Master Data → Profit Center → Individual Processing → Create

Create Standard Hierarchy GIM1_PC_HIER first. Then create Profit Centers: PC_RET (Retail Division, Segment=SEG_RET) and PC_MFG (Manufacturing Division, Segment=SEG_MFG). Deactivate the 'Lock' flag on each Profit Center — they must be active to receive postings.

Assign Default Profit Centers to G/L Accounts

SPRO → Controlling → Profit Center Accounting → Assignments of Account Assignment Objects → Assign G/L Accounts

Assign default Profit Centers to G/L accounts: Revenue account 200000 → PC_RET (default). This ensures that even if a user forgets to enter a Profit Center on a revenue posting, the correct one is automatically defaulted.

📌

Exam Tip: The Controlling Area and ALL assigned Company Codes MUST share the same Chart of Accounts AND Fiscal Year Variant. Mismatch = assignment fails. Cost Centers collect COSTS ONLY. Profit Centers collect REVENUES and COSTS. In S/4HANA, ACDOCA table means FI and CO are always in sync — no reconciliation ever needed.

🧠

Knowledge Check

Q1What is the critical requirement when assigning a Company Code to a Controlling Area?

Correct: B — Same CoA AND FYV. Both the Chart of Accounts and Fiscal Year Variant must match. A mismatch on either will prevent the assignment in OX19 and cause a technical error. This is the most common configuration mistake in FI-CO setup.

Q2A Cost Center report for CC_MFG shows zero costs even though vendor invoices have been posted to account 400000 (Office Rent). What is the most likely cause?

Correct: B — No cost element category on account 400000. In S/4HANA, P&L accounts must have a cost element category assigned (in FS00) to be CO-relevant. Without it, postings succeed in FI but never update any CO object. Assigning Category 1 (primary costs) to account 400000 will resolve the issue.

Q3What is the key difference between a Cost Center and a Profit Center in SAP Controlling?

Correct: B — Cost Center = costs only; Profit Center = revenues + costs. A Cost Center represents a department cost pool (e.g., IT Dept — only has costs). A Profit Center represents an internal business unit (e.g., Retail Division — has both sales revenue and operating costs for internal P&L measurement).

Q4In SAP S/4HANA, when does an FI posting automatically update CO (Controlling)?

Correct: C — Real-time, immediately. In S/4HANA, the Universal Journal (ACDOCA) stores FI and CO data in the same table. Every FI posting to a cost-relevant account automatically updates CO in real-time — no batch job, no manual trigger, no period-end reconciliation.

Q5Which T-code is used to create a Controlling Area in SAP S/4HANA?

Correct: C — OKKP. OKKP = Maintain Controlling Area. OX19 = Assign Company Code to Controlling Area. KS01 = Create Cost Center. KE51 = Create Profit Center.

✍️

Assignment 7 — FI-CO Structure Setup

GIM Group Management Reporting

Assignment — FI-CO Structure Setup

Business Scenario

GIM Group wants to track expenses by department (Cost Centers) and monitor profitability by business division (Profit Centers). Create the complete CO structure for GIM Group India.

Task — Configure or Prepare:

Create Controlling Area GIM1 with CoA=CAIN, FYV=Z1, Currency Type=10, activate Cost Center and Profit Center Accounting
Assign Company Code IN01 to Controlling Area GIM1 (OX19)
Create Cost Center Standard Hierarchy GIM1_HIER
Create 4 Cost Centers: CC_FIN (Finance), CC_HR (HR), CC_IT (IT), CC_MFG (Manufacturing)
Create Profit Center Standard Hierarchy GIM1_PC_HIER
Create 2 Profit Centers: PC_RET (Retail, Segment=SEG_RET) and PC_MFG (Manufacturing, Segment=SEG_MFG)
Assign cost element category 1 to G/L account 400000 (Office Rent) in FS00
Post test expense (FB60): Vendor invoice INR 30,000 to account 400000, Cost Center CC_FIN, Profit Center PC_RET
Verify Cost Center report KSB1 shows INR 30,000 for CC_FIN

Expected Output

Controlling Area GIM1 active with Cost Center and Profit Center Accounting
All Cost Centers and Profit Centers created and active
FI test posting automatically visible in Cost Center report (KSB1)
Profit Center report (KE5Z) shows the entry with correct Segment

Validation Criteria

Controlling Area GIM1 assigned to IN01 without errors
All Cost Centers created and visible in hierarchy OKEON
Both Profit Centers created with Segment assignments
KSB1 report shows expense in CC_FIN without any manual CO update

💼

Interview Preparation

📋 Interview Q&A

Q1. What is the difference between Financial Accounting (FI) and Controlling (CO) in SAP?

Financial Accounting (FI) handles external reporting — producing Balance Sheet, P&L Statement, Trial Balance for shareholders, tax authorities, banks, and regulators. It follows statutory accounting standards (Indian GAAP, IFRS, US GAAP). Controlling (CO) handles internal management reporting — Cost Center reports, Profit Center P&L, product costing — for management decision-making. It follows management accounting principles. In S/4HANA, both share the Universal Journal (ACDOCA), meaning every FI expense posting automatically updates CO in real time without any separate reconciliation process.

Q2. Why must the Controlling Area share the same Chart of Accounts and Fiscal Year Variant as its Company Codes?

The Controlling Area and its assigned Company Codes must share the same Chart of Accounts because CO uses G/L accounts as cost elements. If the CoA were different, the account structures would be incompatible and cost flows from FI to CO would be impossible. The Fiscal Year Variant must match because CO periods are based on FI fiscal periods — different fiscal years would make period-based cost reporting impossible. SAP technically enforces both requirements and will reject the Company Code assignment if either mismatches.

Q3. How does FI-CO integration work differently in S/4HANA vs ECC?

In SAP ECC, FI and CO had separate database tables (FI in BKPF/BSEG, CO in COSP/COSS). A periodic reconciliation transaction (KALC) was required to align both. This was a significant administrative burden. In SAP S/4HANA, the Universal Journal (ACDOCA) stores both FI and CO data in a single table. Every cost-relevant FI posting simultaneously and instantly updates CO — the FI and CO 'views' are simply different filter perspectives on the same ACDOCA record. This eliminates KALC entirely and enables real-time management reporting.

Module 08 · Parallel Accounting · C_TS4FI

Leading & Non-Leading Ledgers
Parallel Accounting

Organizations operating globally must comply with multiple accounting standards simultaneously — e.g., Indian GAAP and IFRS. SAP S/4HANA supports this through a multi-ledger architecture without data duplication.

Config Objects

~2 hrs

Study Time

Practice MCQs

~6%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand currency types in SAP (Type 10, 30, 40, 50)
Understand the Leading Ledger (0L) concept and its role
Understand when and why Non-Leading Ledgers are used
Understand Ledger Groups and how they direct postings to specific ledgers
Explain parallel accounting scenarios: Indian GAAP + IFRS
Know key T-codes for ledger configuration

📖

Core Concepts

Ledgers, Currencies, and Parallel Accounting

Leading Ledger (0L)

The primary, mandatory ledger in every SAP S/4HANA system. Always uses key '0L'. Receives ALL postings by default. Uses the Company Code currency (Currency Type 10). Reports under the primary accounting standard (e.g., Indian GAAP for IN01). Every SAP system has exactly ONE Leading Ledger per Company Code — it cannot be deactivated, deleted, or bypassed.

Non-Leading Ledger

An additional ledger that can be activated for specific Company Codes to maintain a parallel accounting view. Used ONLY when an organization must comply with TWO different accounting standards simultaneously (e.g., Indian GAAP in 0L and IFRS in L1). Transactions identical under both standards post to Ledger Group 'All'. Transactions that differ (e.g., different depreciation) are posted specifically to the relevant ledger only.

Currency Types

Type 10 = Company Code currency (INR for IN01). Type 30 = Group/consolidation currency (e.g., EUR or USD for parent reporting). Type 40 = Hard currency (used in high-inflation countries). Type 50 = Index currency (regulatory requirement). S/4HANA supports up to 10 parallel currencies per ledger for comprehensive multi-currency reporting.

Ledger Groups

A Ledger Group is a collection of ledgers that receive the same posting simultaneously. Standard Ledger Group '0L' = Leading Ledger only. Ledger Group 'All' = all active ledgers. When posting a transaction identical under both GAAP and IFRS, use Ledger Group 'All' — both 0L (GAAP) and L1 (IFRS) are updated. For IFRS-only adjustments (e.g., IFRS 16 lease), post specifically to L1 only.

⚙️

Parallel Accounting Scenario

GIM Group India + German Parent

Business Requirement

GIM Group India (IN01) prepares accounts under Indian GAAP for statutory filing with Ministry of Corporate Affairs. The German parent company requires consolidated IFRS financial statements. SAP S/4HANA handles this with: Leading Ledger 0L = Indian GAAP (INR), Non-Leading Ledger L1 = IFRS (INR with IFRS-specific adjustments).

How Postings Flow

Regular vendor invoice (same under both standards) → Post to Ledger Group 'All' → Updates both 0L and L1 automatically. IFRS 16 lease adjustment (only required under IFRS) → Post specifically to Ledger L1 → Only L1 is updated, 0L unchanged. Year-end result: 0L has complete Indian GAAP financials; L1 has complete IFRS financials. No duplication of common entries.

Currency Type	Key	Used For	Example
Company Code	10	Standard local currency postings	INR for GIM India
Group Currency	30	Group/parent consolidation reporting	EUR for German parent
Hard Currency	40	Supplement in high-inflation countries	USD in Argentina
Index Currency	50	Regulatory index-based reporting	Inflation-indexed currency

📌

Exam Tip: The Leading Ledger is ALWAYS '0L' — this cannot change. A Non-Leading Ledger is ONLY required when an organization must maintain TWO different accounting standards simultaneously. Single-standard organizations use only 0L. Currency Type 10 = Company Code currency. Currency Type 30 = Group currency. These distinctions are directly tested.

🧠

Knowledge Check

Q1What is the standard key for the Leading Ledger in SAP S/4HANA?

Correct: C — 0L. The Leading Ledger always uses key '0L' in SAP S/4HANA. Every Company Code has exactly one Leading Ledger. Non-Leading Ledgers use keys like L1, L2, etc. The Leading Ledger cannot be deactivated.

Q2GIM Group India files under Indian GAAP locally and must also provide IFRS statements for its German parent. Which SAP configuration is required?

Correct: B — Non-Leading Ledger L1 for IFRS. When two accounting standards apply simultaneously, a Non-Leading Ledger is required. 0L handles Indian GAAP; L1 handles IFRS. Common transactions post to Ledger Group 'All'; IFRS-only entries post specifically to L1.

Q3Which currency type represents the Company Code local currency in SAP Finance?

Correct: B — Currency Type 10. Type 10 = Company Code local currency (e.g., INR for IN01). Type 30 = Group/consolidation currency (e.g., EUR). Type 40 = Hard currency. Type 50 = Index currency. Type 10 is used for all standard financial postings.

Q4GIM Group India complies with only Indian GAAP. How many ledgers does it need?

Correct: C — Only the Leading Ledger (0L). Non-Leading Ledgers are only required when TWO different accounting standards must be maintained simultaneously. Single-standard organizations use only 0L, which receives all postings by default.

✍️

Assignment 8 — Parallel Accounting Concepts

GIM Group International Setup

Assignment — Parallel Accounting — Conceptual Understanding

Business Scenario

GIM Group India is required to prepare financial statements under both Indian GAAP (for domestic statutory filing) and IFRS (for its German parent company GIM Group GmbH). This assignment focuses on conceptual understanding of how SAP S/4HANA handles this requirement.

Task — Configure or Prepare:

Identify the local currency (INR) and group currency (EUR) for GIM Group India
Explain which ledger handles Indian GAAP and which handles IFRS
Describe how a common vendor invoice (same treatment under both standards) would be posted
Identify at least 2 scenarios where Indian GAAP and IFRS treatment differs (e.g., IFRS 16 leases, depreciation methods)
Explain what Ledger Group 'All' means and when it is used vs. ledger-specific posting

Expected Output

Clear explanation of Leading Ledger (0L) for Indian GAAP and Non-Leading Ledger (L1) for IFRS
Correct description of how common transactions flow to both ledgers simultaneously
At least 2 examples of transactions that require IFRS-only posting to L1
Correct explanation of Ledger Groups and how they direct postings

Validation Criteria

Correct identification of which ledger handles each accounting standard
Understanding of when Ledger Group 'All' vs. ledger-specific posting is used
Currency type 10 and 30 correctly explained
Ability to articulate the benefit: full parallel accounting without data duplication

💼

Interview Preparation

📋 Interview Q&A

Q1. What is parallel accounting in SAP S/4HANA and when is it required?

Parallel accounting in SAP S/4HANA allows an organization to maintain complete financial records under two different accounting standards simultaneously without duplicating data. It is required when a company must comply with both local statutory requirements (e.g., Indian GAAP) and international standards (e.g., IFRS) for a parent company or for global reporting. The Leading Ledger (0L) holds the primary standard. A Non-Leading Ledger (e.g., L1) holds the second standard. Common transactions post to both ledgers simultaneously via Ledger Group 'All'; only the differences are posted specifically to the relevant ledger.

Q2. What is the difference between Currency Type 10 and Currency Type 30?

Currency Type 10 is the Company Code currency — the local currency in which the Company Code operates (e.g., INR for GIM Group India). It is used for all standard financial postings and statutory reporting. Currency Type 30 is the Group currency — the reporting currency used for group consolidation at the parent company level (e.g., EUR for GIM Group GmbH in Germany). S/4HANA can maintain both currency types simultaneously in the same ledger, automatically translating amounts using exchange rates maintained in OB08.

Module 09 · FI-CO Integration · C_TS4FI

Finance & Controlling Integration
FI–CO Deepening

FI and CO must operate in integrated synchronization. Every cost-relevant financial posting must automatically update management reporting in real time. This module deepens FI-CO integration knowledge from both functional and configuration perspectives.

Config Objects

~2 hrs

Study Time

Practice MCQs

~8%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand FI-CO integration principles and ACDOCA in S/4HANA
Configure document types relevant to Controlling postings
Understand default CO account assignments per G/L account
Understand Internal Orders and their CO role
Configure and validate CO Version 0 for actual postings
Perform a complete FI posting and verify CO update in KSB1

📖

Core Concepts

CO Account Assignment Objects

When posting to a P&L account (cost/revenue account), SAP requires a CO account assignment: Cost Center (for departmental costs), Profit Center (mandatory in S/4HANA with Document Splitting), Internal Order (for project-specific costs), or WBS Element (for project system). Without a CO assignment on a cost-relevant account, the posting is rejected.

Internal Order

A temporary CO object for monitoring costs of a specific project, event, or activity. Examples: a marketing campaign, a trade show, a building renovation. Costs are collected on the Internal Order during execution, then settled (allocated) to a Cost Center or Asset at the end. Created in KO01. Budget can be assigned and monitored.

CO Version 0

The standard version in SAP Controlling for capturing ACTUAL postings. All real cost center, profit center, and internal order transactions post to Version 0. Planning versions (1, 2, 3...) are used separately for budget and forecast. Version 0 is mandatory and cannot be deleted or deactivated.

Default Account Assignments

Instead of requiring users to manually enter a Cost Center or Profit Center on every posting, you can configure default account assignments per G/L account. Example: Office Rent account 400000 → default Cost Center CC_FIN. When a user posts to 400000 without specifying a Cost Center, CC_FIN is automatically used. Reduces errors and speeds up daily postings.

S/4HANA vs ECC FI-CO Integration: ECC required periodic reconciliation (KALC transaction) between FI and CO tables. S/4HANA's Universal Journal (ACDOCA) merges FI and CO into one table. Every FI expense posting simultaneously updates CO in real time — no reconciliation, no batch jobs, no lag. This is a major S/4HANA selling point and a frequently tested exam concept.

⚙️

Configuration & Validation Steps

Verify CO Version 0

OKEQ

SPRO → Controlling → General Controlling → Multiple Valuation Approaches/Transfer Prices → Edit Versions

Verify that Version 0 exists and is active for actual postings. Set Version 0 as default actual version. Planning versions (1+) are separate. Version 0 captures all real-world FI-CO postings.

Configure Default Account Assignments

SPRO → Controlling → Cost Center Accounting → Actual Postings → Manual Actual Postings → Edit Default Account Assignments

Assign default CO objects to G/L accounts: Account 400000 (Office Rent) → Default Cost Center CC_FIN, Default Profit Center PC_RET. Account 401000 (Travel Expenses) → Default Cost Center CC_HR. These defaults reduce manual input errors during daily posting.

Create Internal Order for Special Project

KO01

Accounting → Controlling → Internal Orders → Master Data → Special Functions → Order → Create

Create Internal Order IO_MKT_2025 for GIM Group Q4 Marketing Campaign: Order Type = GIM (custom), Controlling Area = GIM1, Company Code = IN01, Profit Center = PC_RET. Set budget and activate budget monitoring. All campaign expenses (vendor invoices, employee expenses) will reference this order.

Post FI Document and Verify CO Update

FB60 then KSB1

Accounting → Financial Accounting → Accounts Payable → Document Entry

Post vendor invoice: Account 400000, Amount INR 50,000, Cost Center CC_FIN, Profit Center PC_RET. After posting, run Cost Center report KSB1 for CC_FIN — the INR 50,000 expense should appear immediately without any batch job or manual trigger. This proves real-time FI-CO integration via ACDOCA.

📌

Exam Tip: In S/4HANA, cost elements ARE G/L accounts (no separate KA01). A P&L account must have a cost element category assigned in FS00 to update CO. Without a category, postings succeed in FI but are invisible in CO reports. Default account assignments reduce manual CO entry errors. Version 0 captures all actual postings.

🧠

Knowledge Check

Q1In SAP S/4HANA, where is the cost element category (CO relevance) of a G/L account maintained?

Correct: B — In the G/L account master (FS00). This is a key S/4HANA change from ECC. In ECC, cost elements were separate master data objects (KA01). In S/4HANA, the CO category is maintained directly in the G/L account master. This simplifies configuration and maintenance.

Q2What is an Internal Order in SAP Controlling and how does it differ from a Cost Center?

Correct: B — Cost Center permanent; Internal Order temporary. CC_FIN (Finance Dept) is a permanent Cost Center that collects ongoing costs indefinitely. IO_MKT_2025 (Marketing Campaign) is a temporary Internal Order that collects campaign costs until the campaign ends, then all costs are settled to a Cost Center or Asset.

Q3In SAP S/4HANA, when is FI-CO period-end reconciliation required?

Correct: C — Never in S/4HANA. In ECC, FI and CO had separate tables requiring periodic KALC reconciliation. In S/4HANA, ACDOCA stores both FI and CO in a single table — FI-CO are always in sync by design. Transaction KALC is obsolete in S/4HANA.

Q4Which CO Version captures actual (real-world) financial postings in SAP Controlling?

Correct: B — Version 0. CO Version 0 is the standard version for actual postings (real costs and revenues). Versions 1, 2, 3, etc., are used for budget planning and forecasting. Version 0 is mandatory and cannot be deleted.

💼

Interview Preparation

📋 Interview Q&A

Q1. How does FI-CO integration work in SAP S/4HANA vs ECC?

In SAP ECC, FI and CO had separate database tables (BKPF/BSEG for FI, COSP/COSS for CO) requiring a periodic reconciliation transaction (KALC). In S/4HANA, the Universal Journal table ACDOCA stores both FI and CO data in a single row. Every FI posting to a cost-relevant account automatically and simultaneously updates CO — no batch processing, no reconciliation, no lag. The FI view and CO view are simply different filters on the same ACDOCA entry.

Q2. A user posts to expense account 400000 but the Cost Center report shows nothing. What are the possible causes?

Two possible causes: (1) G/L account 400000 has no cost element category assigned in FS00 — without a CO category, the posting succeeds in FI but has no CO relevance and will never appear in CO reports. Fix: assign Cost Element Category 1 (primary costs) to account 400000 in FS00. (2) The posting was made without a CO account assignment (Cost Center or Internal Order) on the line item — without a CO object, the system doesn't know where to attribute the cost. Fix: enter the Cost Center on the posting line or configure a default account assignment.

Module 10 · AR & AP · C_TS4FI

Accounts Receivable & Payable
Business Partner — Customer & Vendor

SAP S/4HANA manages all customers and vendors through a unified Business Partner (BP) concept. This simplifies master data, eliminates duplicate records, and strengthens integration across Finance, MM, and SD.

Config Objects

~3 hrs

Study Time

Practice MCQs

~12%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand the Business Partner concept and its roles in S/4HANA
Configure BP number ranges and groupings
Configure Customer Account Groups (OBD2) and Vendor Account Groups (OBD3)
Understand and configure CVI (Customer-Vendor Integration)
Create a Business Partner with FI Customer (FLCU00) and Vendor (FLVN00) roles
Configure Customer and Vendor Tolerance Groups (OBA3)
Know T-codes: BP, OBD2, OBD3, FLCU, FLVN

📖

Core Concepts

Business Partner (BP)

In SAP S/4HANA, customers and vendors are managed as Business Partners (transaction BP). A single BP can simultaneously hold multiple roles: FI Customer role (FLCU00), FI Vendor role (FLVN00), SD Customer, MM Supplier. This replaces XD01/XD02 (customer) and XK01/XK02 (vendor) from ECC. One BP for one real-world entity — eliminates duplicates.

Customer-Vendor Integration (CVI)

The mandatory S/4HANA configuration linking the BP framework to classic FI customer/vendor structures. CVI maps BP Groupings to Customer Account Groups and Vendor Account Groups. Without CVI, creating a BP with FI roles (FLCU00/FLVN00) fails with an error. Configured in SPRO under Business Partner Integration settings.

Account Groups (Customer/Vendor)

Control number ranges, field status (mandatory/optional/hidden fields), and account type (regular vs one-time) for Business Partner master records. Customer account groups: OBD2. Vendor account groups: OBD3. Examples: 0001 (regular domestic customers), 0002 (one-time customers), KRED (regular domestic vendors), LIEF (vendor/supplier for MM).

Reconciliation Account (AR/AP)

Assigned in BP Company Code FI data. Links the AR or AP sub-ledger to the General Ledger. Customer BP → AR reconciliation account (e.g., 141000 Trade Receivables). Vendor BP → AP reconciliation account (e.g., 161000 Trade Payables). Every customer/vendor posting simultaneously updates this GL account. Direct posting to reconciliation accounts is blocked.

⚙️

Step-by-Step Configuration

Create Business Partner — FI Customer — SAP S/4HANA [DEV — Client 100]

▶

■

↺

Transaction:

General Data

Company Code Data

Payment Transactions

Correspondence

Business Partner: C-100001 — GIM Retail Solutions Pvt Ltd

BP Number

C-100001

BP Role

FLCU00 — FI Customer

Name

GIM Retail Solutions Pvt Ltd

Country

Reconciliation Account

141000 — Trade Receivables

Payment Terms

NT30

Dunning Procedure

ZDUN

Tolerance Group

CUST1

Save (Ctrl+S)

Back (F3)

Cancel (F12)

BP C-100001 created with role FLCU00 — FI CustomerClient 100 | DEV | EN

Configure BP Number Ranges and Groupings

SPRO → Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings

Create number ranges: C1 = 0000100001–0000199999 (customers), V1 = 0000200001–0000299999 (vendors). Create BP Groupings: CUST (linked to C1), VEND (linked to V1).

Configure Customer Account Groups

OBD2

SPRO → Financial Accounting → Accounts Receivable and Payable → Customer Accounts → Master Data → Preparations → Define Account Groups with Screen Layout (Customers)

Configure account group 0001 (Domestic Customers). Set: Number range = C1, Field status: Name = Required, Reconciliation Account = Required, Payment Terms = Optional. This controls how the customer BP master screens look.

Configure Vendor Account Groups

OBD3

SPRO → Financial Accounting → Accounts Receivable and Payable → Vendor Accounts → Master Data → Preparations → Define Account Groups with Screen Layout (Vendors)

Configure account group KRED (Domestic Vendors). Set: Number range = V1, Reconciliation Account = Required, Payment Terms = Optional.

Configure CVI — Customer-Vendor Integration

SPRO → Cross-Application Components → SAP Business Partner → Business Partner → Integration → Customer Integration → Define Number Assignment for Direction BP to Customer

Map BP Grouping CUST → Customer Account Group 0001. Map BP Grouping VEND → Vendor Account Group KRED. This is the mandatory CVI link. Without it, BP creation with FI roles FLCU00/FLVN00 will fail.

Create Business Partner as FI Customer

SAP Easy Access → Cross-Application Components → Business Partner → BP

Create: Role = FLCU00, Grouping = CUST, Name = 'GIM Retail Solutions Pvt Ltd', Country = IN. Company Code View (IN01): Reconciliation Account = 141000, Payment Terms = NT30, Dunning Procedure = ZDUN. Save — system assigns BP number C-100001 automatically.

BP Role Key	Role Description	Sub-Ledger	FI Transaction
FLCU00	FI Customer (Debitor)	Accounts Receivable (AR)	FB70 — Customer Invoice
FLVN00	FI Vendor (Kreditor)	Accounts Payable (AP)	FB60 — Vendor Invoice
FLBP	General Business Partner	None	No direct FI impact
BUP003	Employee	HR/Travel Mgmt	Travel expenses

📌

Exam Tip: In S/4HANA, XD01/XK01 are DEPRECATED — use transaction BP only. CVI is MANDATORY — without it, BP creation with FI roles fails. FLCU00 = FI Customer role. FLVN00 = FI Vendor role. One BP can have BOTH roles simultaneously for intercompany entities. Reconciliation accounts in BP master link the sub-ledger to GL automatically.

🧠

Knowledge Check

Q1In SAP S/4HANA, which transaction is used to create Customer and Vendor master records?

Correct: C — BP (Business Partner). Transaction BP is the unified master data transaction in S/4HANA. XD01/XD02/XK01/XK02 still exist for backward compatibility but are deprecated. All new S/4HANA implementations should use BP exclusively.

Q2What is CVI (Customer-Vendor Integration) and why is it mandatory in S/4HANA?

Correct: B — Customer-Vendor Integration. CVI is mandatory because S/4HANA uses Business Partner as the master data object, but the underlying FI architecture still requires traditional account group structures. CVI maps BP Groupings to Account Groups so that creating a BP with role FLCU00/FLVN00 automatically creates the required FI customer/vendor data. Without CVI, this creation fails.

Q3A BP with reconciliation account 141000 (Trade Receivables) is assigned to customer C-100001. A customer invoice for INR 100,000 is posted. What happens in the General Ledger?

Correct: B — 141000 is automatically debited. The reconciliation account is updated simultaneously with every sub-ledger posting. When a customer invoice (FB70) is posted, the AR sub-ledger is debited AND G/L account 141000 (Trade Receivables) is automatically debited at the same time — keeping GL and sub-ledger always in sync.

Q4Which BP role key creates a vendor (creditor) in SAP S/4HANA Finance?

Correct: B — FLVN00 (FI Vendor / Kreditor). FLCU00 = FI Customer role. FLVN00 = FI Vendor role. A single BP can have both roles assigned simultaneously — common for intercompany partners that are both customers and vendors.

Q5What is the PRIMARY benefit of the Business Partner concept in SAP S/4HANA compared to separate customer/vendor master records in ECC?

Correct: B — Eliminates duplicates and provides unified 360-degree view. With separate XD01/XK01 in ECC, a company that was both customer and vendor had two completely separate master records — inconsistencies were common. The BP concept gives one master record with all roles, ensuring consistent address, payment terms, and contact information across all business transactions.

✍️

Assignment 10 — Business Partner Configuration

GIM Group AR/AP Master Data

Assignment — Business Partner Configuration

Business Scenario

GIM Group India buys goods from vendors and sells products to customers. Configure the complete Business Partner infrastructure and create the first customer and vendor.

Task — Configure or Prepare:

Configure BP Number Ranges: C1 (100001–199999 customers), V1 (200001–299999 vendors)
Create BP Groupings: CUST (linked to C1), VEND (linked to V1)
Configure Customer Account Group 0001 (Domestic Customers) in OBD2 with reconciliation account field as required
Configure Vendor Account Group KRED (Domestic Vendors) in OBD3
Configure CVI: map CUST → Account Group 0001, map VEND → Account Group KRED
Create BP C-100001 (GIM Retail Solutions): role FLCU00, Reconciliation Account 141000, Payment Terms NT30, Dunning Procedure ZDUN
Create BP V-200001 (RP Industries Ltd): role FLVN00, Reconciliation Account 161000, Payment Terms NT30
Post a test customer invoice (FB70): C-100001, INR 100,000, verify GL 141000 is debited automatically

Expected Output

BP C-100001 and V-200001 created without errors
Customer invoice updates GL account 141000 automatically
Vendor invoice updates GL account 161000 automatically
Both BPs available for selection in FB60 and FB70

Validation Criteria

BP C-100001 created with correct reconciliation account 141000
BP V-200001 created with correct reconciliation account 161000
CVI link working — no errors during BP creation with FI roles
Test invoices update reconciliation accounts automatically

💼

Interview Preparation

📋 Interview Q&A

Q1. What changed with Business Partner in S/4HANA compared to ECC?

In SAP ECC, customers were created with XD01/FD01 and vendors with XK01/MK01 as completely separate master data objects with no link between them. In S/4HANA, both are managed through the Business Partner (transaction BP). One BP can have multiple roles simultaneously — FLCU00 (FI Customer) and FLVN00 (FI Vendor) — eliminating duplicate records for entities that are both customer and vendor. XD01 and XK01 are deprecated. CVI (Customer-Vendor Integration) is a mandatory new configuration in S/4HANA that links the BP framework to classic FI structures.

Q2. A new SAP S/4HANA project team reports that creating a Business Partner with role FLCU00 fails with an error. What is the most likely cause and how do you fix it?

The most likely cause is missing CVI (Customer-Vendor Integration) configuration. In S/4HANA, CVI must map the BP Grouping to a Customer Account Group before the system can create the FI-specific customer data during BP creation. To fix: go to SPRO → Cross-Application Components → SAP Business Partner → Business Partner → Integration → Customer Integration → Define Number Assignment. Map the BP Grouping being used (e.g., CUST) to the Customer Account Group (e.g., 0001). After this mapping, BP creation with role FLCU00 will succeed.

Module 11 · Currency Management · C_TS4FI

Currencies &
Exchange Rates

Global organizations transact in multiple currencies. SAP manages foreign currency automatically using predefined exchange rate types — ensuring accurate valuation, consistent reporting, and proper period-end revaluation.

Config Objects

~2 hrs

Study Time

Practice MCQs

~6%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand exchange rate types in SAP (M, B, G and custom types)
Maintain exchange rates in OB08 with correct valid-from dates
Understand how SAP determines the exchange rate at document posting time
Post a foreign currency document and understand automatic currency conversion
Run period-end foreign currency revaluation (FAGL_FC_VAL)
Know T-codes: OB07, OB08, FAGL_FC_VAL

📖

Core Concepts

Exchange Rate Types, Rates, and Revaluation

Exchange Rate Types

SAP uses different rate types for different purposes: M = Average/Middle rate — standard for most business transactions. B = Bank buying rate (bank purchases foreign currency from company). G = Bank selling rate (bank sells foreign currency to company). Custom types like BUDG can be created for planning. Configured in OB07.

Exchange Rate Maintenance (OB08)

Exchange rates are maintained as currency pairs (e.g., USD/INR) with a valid-from date. SAP uses the POSTING DATE of the document (not document date or entry date) to determine the applicable rate. If no rate exists for the exact posting date, SAP searches backward for the most recent valid rate. Rates can be manually entered or uploaded via interfaces.

Foreign Currency Revaluation (FAGL_FC_VAL)

At period-end, open items in foreign currency (unpaid vendor invoices in USD, outstanding customer invoices in EUR) must be revalued at the current exchange rate to comply with accounting standards. FAGL_FC_VAL calculates the difference between the booking rate and the current rate, posts unrealized exchange rate gains/losses, and creates an automatic reversal entry for the first day of the next period.

⚙️

Configuration Steps

Maintain Exchange Rates — OB08 — SAP S/4HANA [DEV — Client 100]

▶

■

↺

Transaction:

OB08

Enter Rates

Rate History

Translation Ratios

Exchange Rate: USD to INR — Type M (Average Rate)

Exchange Rate Type

M — Average/Middle Rate

Valid From

01.04.2025

From Currency

USD — US Dollar

To Currency

INR — Indian Rupee

Exchange Rate

84.5000

Indirect Quotation

No — Direct

Save (Ctrl+S)

Back (F3)

Cancel (F12)

Exchange Rate M — USD/INR = 84.50 valid from 01.04.2025Client 100 | DEV | EN

Define Exchange Rate Types

OB07

SPRO → General Settings → Currencies → Check Exchange Rate Types

Review standard types M (Average), B (Bank Buy), G (Bank Sell). Create custom type BUDG (Budget Rate) for planning transactions if needed. Enable 'Inversion Allowed' so SAP can auto-calculate inverse rates.

Maintain Exchange Rates

OB08

SPRO → General Settings → Currencies → Enter Exchange Rates

Enter: Type M, Valid From 01.04.2025, USD/INR = 84.5000. Enter EUR/INR = 90.2000 for the same date. SAP will use these rates for all foreign currency postings where the posting date falls on or after 01.04.2025.

Post Foreign Currency Vendor Invoice

FB60

Post vendor invoice in USD: Vendor V-US001, Invoice Amount = USD 10,000, Posting Date = 15.05.2025. SAP looks up OB08 and finds rate 84.50 (valid from 01.04.2025 — still the most recent). Automatically converts: USD 10,000 × 84.50 = INR 845,000. Both USD and INR amounts are stored in ACDOCA.

Period-End: Run Foreign Currency Revaluation

FAGL_FC_VAL

Accounting → Financial Accounting → General Ledger → Periodic Processing → Closing → Valuate → Foreign Currency Valuation

At May 31 month-end: Update OB08 — new rate M USD/INR = 85.20 (01.05.2025). Run FAGL_FC_VAL for IN01. The open USD invoice is revalued: Current value = 10,000 × 85.20 = INR 852,000. Original = INR 845,000. Difference = INR 7,000 unrealized loss. SAP posts the INR 7,000 loss entry and a reversal document for 01.06.2025.

Exchange Rate Type	Key	Used For	Example
Average Rate	M	Standard vendor/customer invoices	1 USD = 84.50 INR
Bank Buying Rate	B	Bank purchases FC from company	1 USD = 84.20 INR
Bank Selling Rate	G	Bank sells FC to company	1 USD = 84.80 INR
Budget Rate	BUDG	Planning and budgeting	1 USD = 85.00 INR (fixed)

📌

Exam Tip: SAP uses the POSTING DATE — not document date, not entry date — to look up the exchange rate from OB08. This is the most tested fact in Module 11. Also: open foreign currency items must be revalued at period-end (FAGL_FC_VAL). Unrealized gain/loss entries are automatically reversed on the first day of the next period.

🧠

Knowledge Check

Q1Which exchange rate type is used by default for most business transactions (vendor invoices, customer invoices) in SAP Finance?

Correct: C — M (Average/Middle Rate). Type M is the SAP standard default for most business transactions. It represents the mid-market rate. B and G are used for bank-specific foreign currency transactions. BUDG is a custom type for planning.

Q2A vendor invoice is dated March 1, 2025 (document date) but is entered into SAP on April 5, 2025 (posting date). Which date does SAP use to determine the exchange rate?

Correct: C — April 5, 2025 (posting date). SAP ALWAYS uses the posting date for exchange rate determination in OB08 — not the document date, not the entry date. The posting date controls both the fiscal period AND the exchange rate lookup.

Q3At period-end, an open USD vendor invoice exists in SAP. The original posting rate was 84.50 INR/USD. The new month-end rate is 85.20 INR/USD. What does FAGL_FC_VAL post?

Correct: B — Unrealized LOSS of INR 7,000. When USD/INR rate increases from 84.50 to 85.20, an open vendor liability (payable) becomes MORE expensive in INR terms — that is an unrealized loss for the company. FAGL_FC_VAL posts this INR 7,000 loss and automatically creates a reversal for the first day of next period.

Q4Which T-code is used to maintain exchange rates in SAP Finance?

Correct: B — OB08. OB08 = maintain exchange rates (actual rate values). OB07 = define exchange rate types. FAGL_FC_VAL = foreign currency revaluation. OBBS = default translation ratios.

💼

Interview Preparation

📋 Interview Q&A

Q1. How does SAP determine which exchange rate to use when posting a foreign currency document?

SAP uses the POSTING DATE of the document to look up the applicable exchange rate in OB08. The system finds the most recent exchange rate entry with a valid-from date on or before the posting date, using the exchange rate type specified in the document (default = M, average rate). The document date (invoice date) and entry date are not used for rate determination. This means two documents with the same invoice date but different posting dates may use different exchange rates if the rates were updated between those posting dates.

Q2. What is foreign currency revaluation (FAGL_FC_VAL) and why is it required?

FAGL_FC_VAL is a period-end process that adjusts the book value of open foreign currency items — unpaid vendor invoices, outstanding customer invoices, foreign currency bank balances — to reflect the current closing exchange rate. This is required by both Indian GAAP and IFRS: monetary items denominated in foreign currency must be reported at the balance sheet date's closing rate. FAGL_FC_VAL posts unrealized exchange rate gains or losses for the period and creates automatic reversal entries for the first day of the next period, so the effect is reflected in the period-end financial statements but does not permanently change the recorded transaction value.

Module 12 · Document Processing · C_TS4FI

Document Posting
in SAP Finance

All business transactions in SAP Finance are recorded as accounting documents. This module covers day-to-day posting, document lifecycle management, open item clearing, and the essential T-codes every FICO consultant must know by heart.

Key T-codes

~3 hrs

Study Time

Practice MCQs

~10%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Post G/L, vendor, and customer documents using Enjoy transactions (FB50, FB60, FB70)
Understand the difference between Parked and Held documents
Create and execute Recurring Documents (FBD1, F.14)
Display line items for GL, AR, and AP (FBL3N, FBL5N, FBL1N)
Perform manual and automatic clearing (F-03, F-32, F-44, F.13)
Understand Open Item Management in SAP
Know the key financial tables: BKPF, BSEG, ACDOCA

📖

Core Concepts

SAP Accounting Document

Every financial transaction in SAP creates an accounting document with a header (BKPF: document type, company code, posting date, document date, reference, currency) and line items (BSEG/ACDOCA: account, amount, debit/credit, cost assignment, tax). Documents are immutable once posted — corrections are made via reversal only, never deletion.

Parked Document

Saved but NOT posted. Receives a document number and is visible to authorized users in FBV0. Can have incomplete data (missing mandatory fields). Used in approval workflows — a junior staff parks, a senior posts. No accounting impact until finally posted. T-code to create: FB50/FB60/FB70 with Park function. T-code to post: FBV0.

Held Document

Temporary personal draft. Does NOT receive a document number. Visible only to the creating user. Cannot be processed by others. Used as a personal 'save' to continue later. No accounting impact. T-code: FB00 Hold function.

Recurring Document

A template for repetitive postings — monthly rent, quarterly insurance, annual depreciation provision. Created once with FBD1 with a run schedule (start date, end date, run frequency). Executed periodically with F.14, which creates actual posting documents based on the template on each scheduled date.

Open Item Management

When activated for an account, individual line items remain 'open' (uncleared) until matched with an equal and opposite entry. Examples: vendor invoices remain open until a payment clears them. Cleared items are no longer shown in the open items list. Clearing is done manually (F-03, F-32, F-44) or automatically (F.13).

📋

Essential T-Code Reference

Memorize all 15 — they appear in exams and interviews

T-Code	Description	Account Type	Notes
FB50	Post G/L Account Document (Enjoy)	S — GL	Standard journal entry
FB60	Post Vendor Invoice (Enjoy)	K — Vendor	Updates AP sub-ledger + GL simultaneously
FB70	Post Customer Invoice (Enjoy)	D — Customer	Updates AR sub-ledger + GL simultaneously
FBV0	Post / Edit Parked Document	All	Shows parked docs for posting
FBD1	Create Recurring Entry Template	All	Template only — no posting yet
F.14	Execute Recurring Entries	All	Posts actual docs from template
FBL3N	GL Account Line Item Display	S — GL	Open, cleared, and all items
FBL5N	Customer Line Item Display	D — Customer	Aged receivables equivalent
FBL1N	Vendor Line Item Display	K — Vendor	Aged payables equivalent
F-03	Clear GL Account (Manual)	S — GL	Manual matching of GL open items
F-32	Clear Customer Items (Manual)	D — Customer	Match receipts to invoices
F-44	Clear Vendor Items (Manual)	K — Vendor	Match payments to invoices
F.13	Automatic Clearing	All	Auto-matches by assignment field
FB08	Reverse Document	All	Creates equal and opposite reversal
FBRA	Reset Cleared Items	All	Resets cleared items back to open

📌

Memory Aid for Line Item T-codes: FBL3N = G/L (3 = Sachkonto in old numbering). FBL5N = Customer/Debitor (5). FBL1N = Vendor/Kreditor (1). Parked = HAS document number (visible to all authorized). Held = NO document number (private draft). These distinctions appear in every C_TS4FI exam.

⚙️

Document Posting Walkthrough

FB60 — Vendor Invoice

Enter Vendor Invoice — FB60 (Enjoy) — SAP S/4HANA [DEV — Client 100]

▶

■

↺

Transaction:

FB60

Basic Data

Payment

Details

Tax

Notes

Vendor Invoice: RP Industries Ltd — Office Supplies

Vendor

V-200001 — RP Industries Ltd

Invoice Date

15.05.2025

Posting Date

15.05.2025

Document Type

KR — Vendor Invoice

Amount

50,000.00 INR

Tax Code

V1 — 18% GST Input

G/L Account

400100 — Office Supplies

Cost Center

CC_FIN

Save (Ctrl+S)

Back (F3)

Cancel (F12)

Document 1900000001 posted — KR INR 59,000 (50,000 + 9,000 GST)Client 100 | DEV | EN

Post Vendor Invoice

FB60

Accounting → Financial Accounting → Accounts Payable → Document Entry → Invoice

Enter vendor, dates, amount, tax code. In line items: G/L account 400100, cost center CC_FIN. SAP automatically calculates tax (18% of 50,000 = 9,000 INR) and posts to input tax account. Total document = INR 59,000. Accounting entry: Dr Office Supplies 50,000 + Dr GST Input 9,000 / Cr Vendor (V-200001) 59,000.

Post Customer Invoice

FB70

Accounting → Financial Accounting → Accounts Receivable → Document Entry → Invoice

Enter customer, dates, amount, tax code A1 (output tax). G/L account 200000 (Sales Revenue), Profit Center PC_RET. Document: Dr Customer 118,000 / Cr Revenue 100,000 + Cr GST Output 18,000.

Display Vendor Open Items

FBL1N

Run FBL1N for Vendor V-200001. Select 'Open Items'. The INR 59,000 vendor invoice shows as an open item. After payment is posted, run FBL1N again — item status changes from Open to Cleared.

Clear Vendor Open Items After Payment

F-44

Accounting → Financial Accounting → Accounts Payable → Account → Clear

After posting vendor payment (F-53): Run F-44, enter vendor V-200001. System shows both the invoice (credit, open) and the payment (debit, open). Select both — net = 0. Click Process Open Items → Save. Both items are now cleared and show 'Cleared' status in FBL1N.

📌

Exam Tip: You CANNOT reverse a cleared document without first resetting the clearing in FBRA. Correct sequence: FBRA (reset) → FB08 (reverse). F.13 automatic clearing uses the 'Assignment' field to match open items — items with the same assignment number are matched. Clearing is ESSENTIAL for accurate AR/AP aging reports.

🧠

Knowledge Check

Q1What is the key difference between a Parked document and a Held document in SAP Finance?

Correct: B — Parked has number (visible); Held has no number (private). Neither creates accounting entries until finally posted. Parked = collaborative workflow. Held = personal draft. This distinction appears in every C_TS4FI exam.

Q2A monthly office rent of INR 50,000 must be posted on the 1st of every month. Which T-code creates the recurring document template?

Correct: C — FBD1. FBD1 creates the Recurring Document TEMPLATE. F.14 EXECUTES the recurring entries (posts actual documents on scheduled dates). FB60 is one-time vendor invoice entry. FBV0 posts parked documents.

Q3Which T-code displays ALL line items (open, cleared, reversed) for a VENDOR account?

Correct: C — FBL1N. FBL1N = Vendor line items (1 = Kreditor). FBL3N = GL account line items (3 = Sachkonto). FBL5N = Customer line items (5 = Debitor). In FBL1N you filter by Open Items, Cleared Items, or All Items.

Q4After posting a vendor payment that cleared a vendor invoice, the accountant realizes the wrong vendor was paid. What is the CORRECT sequence of steps in SAP?

Correct: B — FBRA → FB08 → Repost. A cleared document CANNOT be reversed directly. First FBRA resets the clearing (restores invoice and payment to open status). Then FB08 reverses the payment document. Then repost the payment to the correct vendor. Audit trail is fully preserved throughout.

Q5What is 'Open Item Management' in SAP Finance and why is it important?

Correct: B — Items remain open until cleared. Open Item Management keeps outstanding invoices and payments visible until they are matched (cleared). It ensures the AR/AP aging reports accurately reflect what is actually owed/owing. Without it, paid invoices and received payments would all accumulate without any way to know what is still outstanding.

💼

Interview Preparation

📋 Interview Q&A

Q1. What is document clearing in SAP Finance and why is it important?

Document clearing matches equal and opposite open items and marks them as 'cleared.' For example: a customer invoice (debit, open) of INR 100,000 is cleared against a customer payment receipt (credit, open) of INR 100,000. After clearing, both items move from 'Open' to 'Cleared' status. This is important because: it accurately shows what is genuinely outstanding in AR/AP, prevents the same invoice from being paid twice, reduces noise in aging reports, and is required for correct cash flow and working capital reporting.

Q2. Explain the complete document lifecycle in SAP Finance.

A document progresses through these states: Held (personal draft, no number, no accounting impact) → Parked (has document number, incomplete, no accounting impact, visible to authorized users for workflow) → Posted (complete, accounting entries created, immutable) → Cleared (matched against equal/opposite entry, marked as settled) → Reversed (equal and opposite entry created, original preserved for audit). Documents cannot be deleted at any stage after saving — only reversed. This lifecycle ensures a complete, unbreakable audit trail for all financial transactions.

Module 13 · Payments · C_TS4FI

Payments &
House Bank Configuration

After invoices are posted, organizations must process payments efficiently. SAP manages this through payment terms, House Banks representing the company's real bank accounts, and structured payment processing workflows.

Config Objects

~2 hrs

Study Time

Practice MCQs

~8%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Configure Payment Terms and understand net due date calculation (OBB8)
Understand Installment Payment Terms
Configure House Banks and Bank Accounts (FI12 / Fiori)
Understand the link between House Bank account and GL bank account
Post manual customer and vendor payments (F-28, F-53)
Know T-codes: OBB8, FI12, F-28, F-53, F-54

📖

Core Concepts

Payment Terms

Define the conditions under which a customer pays (or a vendor expects payment): baseline date for calculation, cash discount periods and percentages, net due date. Examples: NT30 = net 30 days (full payment due 30 days after baseline). 2/10 N30 = 2% discount if paid within 10 days, else full amount due in 30 days. Configured in OBB8. Assigned in Business Partner Company Code data.

Baseline Date

The starting date from which payment due dates are calculated. Can be set to: Posting date (most common), Document date (invoice date), Entry date (date entered in SAP), or a fixed day of the month. Configured per payment term in OBB8. SAP calculates the net due date as: Baseline Date + Net Payment Days.

House Bank

Represents the company's own real-world bank account within SAP. Each House Bank is identified by a Bank Key (IFSC code in India, ABA routing number in USA), a House Bank ID, and a Bank Account ID. Multiple bank accounts can exist under one House Bank (e.g., HDFC current account, HDFC savings account). Each bank account is linked to a GL account. Created via SAP Fiori 'Manage Banks' app or T-code FI12.

Bank Account to GL Account Link

Each House Bank account must be linked to a specific GL bank account (e.g., House Bank HDFC + Account HDFC_CUR → GL account 113000). When a payment is posted via APP or manually, the GL bank account is automatically updated — Dr/Cr to account 113000 — without any manual GL posting required.

⚙️

Configuration Steps

Create House Bank — FI12 — SAP S/4HANA [DEV — Client 100]

▶

■

↺

Transaction:

FI12

Bank Data

Bank Accounts

GL Account Assignment

House Bank: HDFC — HDFC Bank Ltd (Company Code IN01)

Company Code

IN01

House Bank ID

HDFC

Bank Key

HDFC0000001 — HDFC Bank IFSC

Bank Name

HDFC Bank Ltd

Account ID

HDFC_CUR

Account Number

12345678901234

GL Account

113000 — HDFC Current Account

Save (Ctrl+S)

Back (F3)

Cancel (F12)

House Bank HDFC created — Account HDFC_CUR linked to GL 113000Client 100 | DEV | EN

SAP Fiori Launchpad

🔍 Search in SAP...

🔔

Home

Finance

Controlling

Reports

Finance — My Apps

🏦

Manage Banks

💳

Manage House Banks

📤

Post Outgoing Payments

📥

Post Incoming Payments

📋

Payment Run F110

🔄

Automatic Payment

📊

Bank Account Overview

🔍

Check Open Items

Configure Payment Terms

OBB8

SPRO → Financial Accounting → Accounts Receivable and Payable → Business Transactions → Outgoing Payments/Incoming Payments → Maintain Payment Terms

Create payment term NT30: Description = Net 30 Days, Baseline Date = Posting Date, Payment Terms = 0% discount on day 0 / Net Due in 30 days. Create 2/10NT30: 2% discount within 10 days / Net due in 30 days. Assign NT30 to vendor BP master Company Code data.

Create House Bank via Fiori

FI12 or Fiori

SAP Fiori Launchpad → Finance → Manage Banks → Create Bank Account

In Fiori 'Manage Banks': Create Bank HDFC with IFSC HDFC0000001. Create Account HDFC_CUR (Current Account), Account Number 12345678901234. Assign GL Account 113000 (HDFC Current Account). Link to Company Code IN01. In S/4HANA, the Fiori app is preferred over the classic FI12 transaction.

Post Manual Vendor Payment

F-53

Accounting → Financial Accounting → Accounts Payable → Document Entry → Outgoing Payment → Post

Enter: Company Code IN01, Posting Date, Document Date, Amount INR 59,000, Bank Account GL 113000 (HDFC), Value Date. In 'Open Item Selection' enter vendor V-200001. Select the open invoice. Post. Accounting: Dr Vendor V-200001 59,000 / Cr GL 113000 (HDFC Bank) 59,000.

Post Manual Customer Receipt

F-28

Accounting → Financial Accounting → Accounts Receivable → Document Entry → Incoming Payments

Enter: Company Code IN01, Posting Date, Amount INR 118,000, Bank Account GL 113000. In 'Open Item Selection' enter customer C-100001. Select the open invoice. Post. Accounting: Dr GL 113000 (HDFC Bank) 118,000 / Cr Customer C-100001 118,000.

📌

Exam Tip: Payment Terms are assigned in the Business Partner master record (Company Code data view). The BASELINE DATE for payment term calculation defaults to the posting date but can be configured. In S/4HANA, House Banks should be created using the Fiori 'Manage Banks' app rather than classic FI12. A House Bank ID and Bank Account ID are separate — one House Bank can have multiple accounts.

🧠

Knowledge Check

Q1What does the payment term '2/10 N30' mean in SAP Finance?

Correct: B — 2% discount if paid within 10 days; full amount due in 30 days. This is the standard 'two-ten-net-thirty' payment term used globally. The customer earns a 2% early payment discount by paying within 10 days. Otherwise the full invoice amount is due within 30 days.

Q2What does a House Bank represent in SAP Finance?

Correct: B — The company's own real bank account in SAP. A House Bank represents one of the organization's actual bank accounts (e.g., HDFC Current Account). It is linked to a GL account (113000). When the Automatic Payment Program runs, it uses House Bank configuration to determine which bank account to use and updates the linked GL account automatically.

Q3Which T-code is used to post a manual vendor outgoing payment in SAP Finance?

Correct: C — F-53. F-53 = Manual Outgoing Payment (vendor). F-28 = Manual Incoming Payment (customer). F-44 = Clear vendor open items manually. FB60 = enter vendor invoice.

Q4In SAP, the payment term baseline date is typically set to which date by default?

Correct: C — Posting date (most common default). The baseline date for payment term calculation is configured in OBB8. While it can be set to document date, entry date, or posting date, the posting date is the most common default in SAP implementations.

✍️

Assignment 13 — Manual Payments Setup

GIM Group Payment Processing

Assignment — Manual Payments Setup

Business Scenario

GIM Group India needs to configure its payment infrastructure and process the first round of vendor payments and customer receipts.

Task — Configure or Prepare:

Create payment term NT30 (Net 30 Days, baseline = posting date) in OBB8
Create payment term 2/10NT30 (2% discount within 10 days, net 30) in OBB8
Assign payment term NT30 to vendor BP V-200001 and customer BP C-100001
Create House Bank HDFC (IFSC: HDFC0000001, Account: HDFC_CUR) linked to GL 113000
Post a manual vendor payment (F-53): Pay vendor V-200001 INR 59,000 from HDFC_CUR
Post a manual customer receipt (F-28): Receive INR 118,000 from customer C-100001
Verify GL account 113000 balance reflects both transactions

Expected Output

Payment terms NT30 and 2/10NT30 configured and visible in BP master
House Bank HDFC created and linked to GL 113000
Vendor payment posted — vendor balance cleared, GL 113000 reduced
Customer receipt posted — customer balance cleared, GL 113000 increased

Validation Criteria

Payment terms correctly configured with baseline date = posting date
Due date calculated correctly (posting date + 30 days = net due date)
House Bank HDFC available for selection in F-53 and F-28
GL 113000 balance correctly reflects all bank movements

💼

Interview Preparation

📋 Interview Q&A

Q1. What is a payment term in SAP Finance and how does it affect cash management?

A payment term in SAP Finance defines the conditions for invoice settlement — including the baseline date for calculation, any early payment discount periods and percentages, and the final net due date. Payment terms are configured in OBB8 and assigned to Business Partner master records. They are critical for cash management because they determine when invoices become due for payment, which invoices the Automatic Payment Program (F110) selects in each payment run, when dunning notices are triggered, and whether early payment discounts should be applied.

Q2. A House Bank is created but the GL bank account balance does not update when payments are posted. What is the likely cause?

The most likely cause is that the House Bank Account ID is not correctly linked to a GL account. Each House Bank Account (e.g., HDFC_CUR) must have a GL account assigned (e.g., 113000) in the House Bank configuration (FI12 or Fiori 'Manage Banks'). Without this link, SAP does not know which GL account to update when the House Bank is used for payments. To fix: open FI12, navigate to House Bank HDFC → Account HDFC_CUR → assign GL account 113000. After this, all payment postings using HDFC_CUR will automatically update GL 113000.

Module 14 · Payments · C_TS4FI

Automatic Payment Program
(APP — F110)

Organizations with high transaction volumes cannot process payments manually. The SAP Automatic Payment Program (F110) automates vendor and customer payments — selecting due invoices, generating payment proposals, posting payment documents, and creating bank transfer files.

Config Areas

~2 hrs

Study Time

Practice MCQs

~8%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand the APP concept and its 5 central configuration areas (FBZP)
Configure payment methods per country and per company code
Configure bank determination and bank ranking in FBZP
Execute a complete APP run in F110 — Parameters, Proposal, Payment Run
Understand DME (Data Medium Exchange) for bank file generation
Know T-codes: FBZP, F110

📖

Core Concepts

Automatic Payment Program (APP)

SAP's automated payment processing engine. Instead of manually posting each vendor payment, the APP selects all open invoices that are due, groups them by payment method and bank, creates a payment proposal for review, and after approval posts all payment documents in one run. Also generates bank transfer files (DME) for electronic payment submission to the bank. Main configuration: FBZP. Execution: F110.

FBZP — Central APP Configuration

The APP is configured in 5 areas within FBZP: (1) All Company Codes — which company codes participate and paying company setup. (2) Paying Company Codes — minimum payment amount, payment forms, foreign payment settings. (3) Payment Methods per Country — check, wire transfer, bank transfer settings. (4) Payment Methods per Company Code — House Bank assignment for each method. (5) Bank Determination — ranking of banks, available amounts, and charges.

Payment Proposal

The APP first generates a PROPOSAL showing all invoices selected for payment — the due date, vendor, amount, House Bank to be used, and payment method. The accountant reviews this proposal, can modify or exclude items, then approves it for the actual payment run. The proposal can be deleted and regenerated if errors are found.

DME (Data Medium Exchange)

The bank transfer file generated by the APP after the payment run. Contains all payment instructions in the format required by the bank (SEPA XML, NACHA ACH, SWIFT MT103, etc.). The DME file is uploaded to the bank's electronic payment system to initiate actual fund transfers.

⚙️

APP Configuration & Execution

Automatic Payment Transactions — F110 — SAP S/4HANA [DEV — Client 100]

▶

■

↺

Transaction:

F110

Parameters

Status

Proposal

Exception List

APP Run: GIM Group India — May 2025 Vendor Payments

Run Date

31.05.2025

Identification

MAY2025

Company Codes

IN01

Payment Methods

T — Wire Transfer

Vendors from / to

All Vendors

Next Payment Date

01.07.2025

Status

Parameters maintained — Proposal not yet generated

Save (Ctrl+S)

Back (F3)

Cancel (F12)

APP Run MAY2025 configured — ready to generate proposalClient 100 | DEV | EN

Configure APP — All Company Codes

FBZP

SPRO → Financial Accounting → Accounts Receivable and Payable → Business Transactions → Outgoing Payments → Automatic Outgoing Payments → Payment Method/Bank Selection for Payment Program → Set Up All Company Codes for Payment Transactions

For Company Code IN01: Sending Company = IN01 (pays own invoices). Set paying company code = IN01. This is the basic setup that enables IN01 to participate in APP runs.

Configure Payment Methods per Country

FBZP

SPRO → ... → Set Up Payment Methods per Country for Payment Transactions

For Country IN: Create payment method T (Wire Transfer). Set: Outgoing payment = Yes, Bank transfer = Yes. Document type for posting = ZP. No check printing required.

Configure Payment Methods per Company Code

FBZP

SPRO → ... → Set Up Payment Methods per Company Code for Payment Transactions

For IN01 + Method T: Assign House Bank HDFC as the paying bank. Set minimum/maximum payment amounts. This links the payment method to the specific House Bank account that will be debited.

Configure Bank Determination

FBZP

SPRO → ... → Set Up Bank Determination for Payment Transactions

Rank House Banks: Rank 1 = HDFC (primary bank), Rank 2 = SBI (backup). Set available amounts per bank. If HDFC has insufficient funds, APP automatically falls to SBI.

Execute APP Run — F110

F110

Accounting → Financial Accounting → Accounts Payable → Periodic Processing → Payments

Step 1: Enter Run Date (31.05.2025) and Identification (MAY2025). Step 2: Edit Parameters — Company Code IN01, Payment Method T, all vendors, Next Payment Date 01.07.2025. Step 3: Schedule Proposal → review → verify 47 invoices totaling INR 8,45,000. Step 4: Schedule Payment Run → SAP posts payment documents. Step 5: Print → Generate DME bank file.

APP Step	Action	T-Code / Function	Description
Step 1	Enter Parameters	F110 — Parameters tab	Define which company, vendors, payment methods, date range
Step 2	Generate Proposal	F110 — Schedule Proposal	SAP selects all due invoices — review for accuracy
Step 3	Review Proposal	F110 — Display Proposal	Check amounts, vendors, House Banks — modify if needed
Step 4	Run Payments	F110 — Schedule Payment	Post payment documents — cannot easily reverse after this
Step 5	Generate Bank File	F110 — Printout/DME	Create DME file for bank electronic transfer

📌

Exam Tip: The APP run sequence must be followed in order: Parameters → Proposal → Review → Payment Run → DME/Printout. The proposal CAN be deleted and regenerated. After the Payment Run, documents are posted and the bank account GL is debited. Bank Determination in FBZP controls which House Bank is used when multiple banks are available.

🧠

Knowledge Check

Q1Where is the central configuration for the Automatic Payment Program (APP) maintained?

Correct: B — FBZP. FBZP is the central APP configuration transaction covering all 5 configuration areas. F110 is the EXECUTION transaction for running the actual payment program. OBB8 = payment terms. FI12 = House Bank setup.

Q2In the APP (F110), what is the CORRECT sequence of steps?

Correct: B — Parameters → Proposal → Review → Payment Run → DME/Printout. This sequence is mandatory. You cannot run payments without first creating and reviewing the proposal. The proposal step is a critical control point where the accountant verifies what will be paid before money leaves the bank.

Q3In FBZP Bank Determination, you have House Banks HDFC (Rank 1) and SBI (Rank 2). HDFC has an available amount limit of INR 500,000. The current payment run requires INR 800,000. What happens?

Correct: B — HDFC processes up to its limit, SBI handles the remainder. Bank Determination ranking allows the APP to automatically overflow to the next-ranked bank when the available amount is exceeded. This ensures all payments are processed even when one bank account has limited funds.

Q4After a payment proposal is generated in F110, the accountant spots an error — a vendor that should NOT be paid this run is included. What should they do?

Correct: B — Edit the proposal to exclude the vendor. The payment proposal can be modified before the Payment Run. Individual vendor lines can be excluded, amounts adjusted, or payment methods changed. This is exactly why the proposal step exists — as a review and correction opportunity before payments are actually posted.

💼

Interview Preparation

📋 Interview Q&A

Q1. Explain the Automatic Payment Program (APP) in SAP Finance and how it works.

The APP (transaction F110) automates vendor and customer payment processing. Configuration is maintained centrally in FBZP (payment methods, bank determination, company code settings). The execution sequence is: (1) Parameters — define which company codes, vendors, payment methods, and date range to include. (2) Proposal — SAP selects all qualifying open invoices and shows what will be paid and from which bank. (3) Review — the accountant reviews and can modify the proposal. (4) Payment Run — SAP posts all payment documents and debits the bank GL accounts. (5) DME/Printout — generates bank transfer files for submission to the bank. The entire process eliminates manual posting of individual payments for high-volume environments.

Q2. What is Bank Determination in FBZP and how does it control which bank account is used for payments?

Bank Determination in FBZP defines which House Bank account should be used for each combination of payment method, currency, and company code. It includes a ranking system — if multiple banks are available, SAP uses the highest-ranked bank first. Available amount limits can be set per bank account — when the limit is reached, APP automatically overflows to the next-ranked bank. This ensures payment runs are fully processed even when primary bank accounts have limited funds, and gives the finance team control over which bank accounts are used for different types of payments.

Module 15 · Payments · C_TS4FI

Down Payments
Customer & Vendor

Down payments are advance payments made or received before the final invoice is issued. SAP handles these through Special G/L accounts to ensure correct Balance Sheet presentation and accurate clearing against final invoices.

Config Objects

~2 hrs

Study Time

Practice MCQs

~6%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand the Special G/L Indicator concept and why it is used for down payments
Configure Special G/L Indicators for vendor and customer down payments
Process the complete vendor down payment cycle (F-47, F-48, F-54)
Process the complete customer down payment cycle (F-29, F-39)
Understand how down payment clearing works against final invoices
Know T-codes: F-47, F-48, F-54, F-29, F-39, OBYR, OBXR

📖

Core Concepts

Special G/L Indicator

Down payments use Special G/L Indicators to redirect the posting to an ALTERNATIVE reconciliation account instead of the normal trade payables/receivables account. This keeps advance payments separate on the Balance Sheet as required by accounting standards. Common indicators: A = Down Payment Request (statistical), F = Down Payment Made (actual posting). Configured in OBYR (vendor) and OBXR (customer).

Why Alternative Reconciliation Accounts?

Accounting standards (Indian GAAP and IFRS) require advance payments to be shown separately on the Balance Sheet — NOT mixed with normal trade payables or receivables. Example: Advance to Vendors (an asset) must be shown separately from Trade Payables (a liability). The Special G/L indicator ensures the posting goes to the 'Advance to Vendors' account (e.g., 165000) instead of 'Trade Payables' (161000).

Vendor Down Payment Process

Step 1: Create a down payment REQUEST (F-47) — statistical, no accounting impact. Step 2: APP can use the request to make the actual down payment (F-48) — this IS an accounting posting. Step 3: Vendor delivers goods and sends final invoice → post invoice (FB60). Step 4: Clear the down payment against the final invoice (F-54) — transfers amount from alternative account back to normal payables. Step 5: Pay the remaining balance.

Customer Down Payment Process

Step 1: Receive down payment from customer (F-29) — posts to alternative account 'Advances Received from Customers'. Step 2: Deliver goods and post final customer invoice (FB70). Step 3: Clear the down payment against the final invoice (F-39) — transfers amount from 'Advances Received' to normal 'Trade Receivables'. Step 4: Customer pays the remaining balance.

⚙️

Configuration and Process

Configure Special G/L Indicators for Vendors

OBYR

SPRO → Financial Accounting → Accounts Receivable and Payable → Business Transactions → Down Payments Made → Define Reconciliation Accounts for Customer Down Payments

Assign Special G/L indicator F (Down Payment) to: Normal reconciliation account = 161000 (Trade Payables), Alternative reconciliation account = 165000 (Advance Payments to Vendors). When a vendor down payment is posted with indicator F, it goes to 165000 instead of 161000.

Configure Special G/L Indicators for Customers

OBXR

SPRO → Financial Accounting → Accounts Receivable and Payable → Business Transactions → Down Payments Received → Define Reconciliation Accounts for Customer Down Payments

Assign Special G/L indicator A (Advance Received) to: Normal reconciliation account = 141000 (Trade Receivables), Alternative reconciliation account = 145000 (Advances Received from Customers). Customer down payments received post to 145000, not 141000.

Post Vendor Down Payment Request (Statistical)

F-47

Accounting → Financial Accounting → Accounts Payable → Document Entry → Down Payment → Request

Create a Down Payment Request to vendor V-200001 for INR 25,000 (advance for a bulk order). Request only — no accounting posting yet. The request can be used by APP to automatically make the payment.

Post Vendor Down Payment (Actual Payment)

F-48

Accounting → Financial Accounting → Accounts Payable → Document Entry → Down Payment → Post

Post the actual down payment: Vendor V-200001, INR 25,000, Special G/L indicator F, Bank account 113000. Posting: Dr Advance to Vendor 165000 INR 25,000 / Cr Bank 113000 INR 25,000. Note: account 165000 (asset) shows on Balance Sheet under 'Advances and Prepayments', NOT under Payables.

Clear Down Payment Against Final Invoice

F-54

Accounting → Financial Accounting → Accounts Payable → Document Entry → Down Payment → Clearing

After receiving the final vendor invoice (FB60, total INR 100,000): Run F-54 to clear the down payment. Posting: Dr Trade Payables 161000 INR 25,000 / Cr Advance to Vendor 165000 INR 25,000. Net: Vendor balance now shows INR 75,000 (100,000 - 25,000) as the remaining amount to pay.

📌

Exam Tip: Down payments use an ALTERNATIVE reconciliation account (Special GL account) — NOT the normal trade payables/receivables account. This is required by accounting standards to show advances separately on the Balance Sheet. Key T-codes: F-47 (request — no posting), F-48 (post vendor DP), F-54 (clear vendor DP against invoice), F-29 (post customer DP received), F-39 (clear customer DP against invoice).

🧠

Knowledge Check

Q1Why does SAP use a Special G/L Indicator for down payments instead of posting directly to the normal Trade Payables account?

Correct: B — Accounting standards require separate Balance Sheet presentation. Indian GAAP and IFRS both require advance payments to vendors to be shown under 'Advances and Prepayments' (an asset), not under 'Trade Payables' (a liability). The Special G/L indicator redirects the posting to an alternative reconciliation account (e.g., 165000) to achieve this correct Balance Sheet classification.

Q2Which T-code is used to post an ACTUAL vendor down payment (not just a request) in SAP Finance?

Correct: B — F-48. F-47 = Create a Down Payment REQUEST (statistical only, no accounting posting). F-48 = Post the ACTUAL down payment (creates an accounting document with Dr Advance account, Cr Bank). F-54 = Clear the down payment against the final invoice. FB60 = regular vendor invoice.

Q3Which T-code is used to CLEAR a vendor down payment against the final invoice?

Correct: C — F-54. F-54 transfers the down payment amount from the Special GL (alternative) reconciliation account (165000 — Advances to Vendors) back to the normal trade payables reconciliation account (161000). After F-54, the vendor balance in the normal payables shows only the remaining unpaid amount.

Q4A customer pays an advance of INR 50,000 before the goods are delivered. Which T-code posts this customer down payment RECEIVED?

Correct: C — F-29. F-29 posts a customer down payment received. The posting goes to the alternative reconciliation account (145000 — Advances Received from Customers) instead of the normal Trade Receivables (141000). F-39 clears the customer down payment against the final invoice. F-28 is a standard customer incoming payment. FB70 is a customer invoice.

💼

Interview Preparation

📋 Interview Q&A

Q1. What is a down payment in SAP Finance and why does it use a Special G/L Indicator?

A down payment is an advance payment made to a vendor or received from a customer before the final invoice is issued. In SAP, down payments use Special G/L Indicators (configured in OBYR for vendors, OBXR for customers) to redirect the posting to an alternative reconciliation account instead of the normal Trade Payables or Trade Receivables account. This is required because accounting standards (Indian GAAP and IFRS) mandate that advance payments be classified separately on the Balance Sheet — advances paid to vendors are an asset (Advances and Prepayments), while advances received from customers are a liability (Advances Received). Mixing them with normal payables/receivables would misrepresent the Balance Sheet.

Q2. Walk me through the complete vendor down payment cycle in SAP Finance.

The complete vendor down payment cycle: (1) F-47 — Create a Down Payment Request (statistical only, no accounting entry, can be used by APP). (2) F-48 — Post the actual Down Payment: Dr Advance to Vendor 165000 / Cr Bank 113000. The vendor balance shows on the Balance Sheet under Advances, not under Payables. (3) FB60 — Receive the vendor invoice and post normally: Dr Expense / Cr Trade Payable 161000. (4) F-54 — Clear the down payment against the invoice: Dr Trade Payable 161000 / Cr Advance to Vendor 165000. Now the vendor's normal payables account shows only the remaining balance (invoice minus advance). (5) F-53 or F110 — Pay the remaining balance. (6) F-44 — Clear the payment against the remaining open invoice.

Module 16 · Controls & Compliance · C_TS4FI

Document Reversal
& Reset of Cleared Items

SAP Finance never allows deletion of posted documents — it maintains a complete audit trail at all times. Errors are corrected through controlled reversal mechanisms that create offsetting entries while fully preserving the original document.

Key Processes

~1.5 hrs

Study Time

Practice MCQs

~6%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand why SAP never deletes posted documents (audit trail principle)
Perform individual document reversal using FB08
Perform mass reversal of multiple documents using F.80
Configure and use reversal reasons (OB83)
Reset cleared items and understand FBRA
Understand the correct sequence: FBRA → FB08 for cleared documents
Understand negative posting and when it is used
Know T-codes: FB08, F.80, FBRA, OB83

📖

Core Concepts

SAP Audit Trail Principle

SAP Finance never deletes accounting documents. Every posting creates a permanent record in the system. Errors are corrected by creating a REVERSAL document — an equal and opposite entry — not by changing or deleting the original. Both the original document and its reversal remain in the system permanently, linked to each other. This provides an unbreakable audit trail required for SOX compliance, statutory audits, and financial controls.

Document Reversal (FB08)

Creates a mirror-image offsetting entry that cancels the original posting. The original document is marked as 'reversed' and the reversal document references the original. Requires a reversal reason (configured in OB83). Can be posted with: (a) the same posting date as the original, or (b) an alternative reversal date (needed when the original period is closed). Mass reversal of multiple documents: F.80.

Negative Posting

Instead of creating a debit to reverse a credit (which inflates gross transaction totals), negative posting creates a NEGATIVE credit entry. The net effect is identical but gross figures remain clean. Available only for reversal reasons configured with the 'Negative Posting Permitted' flag in OB83. Particularly useful for reversing month-end accruals.

Reset Cleared Items (FBRA)

If a cleared document (e.g., a paid vendor invoice) needs to be reversed, the clearing must be RESET first before reversal is possible. FBRA (Reset Cleared Items and Reverse) reopens both the invoice and payment document back to 'open item' status. After resetting, each document can be reversed individually with FB08, or re-cleared with different items.

⚙️

Process Steps

Configure Reversal Reasons

OB83

SPRO → Financial Accounting → Financial Accounting Global Settings → Document → Document Change Rules, Document Header → Define Reversal Reasons

Create reversal reasons: 01 = Reversal in Current Period (no negative posting), 02 = Reversal in Previous Period (no negative posting), AB = Accrual Reversal (negative posting permitted). The reversal reason controls whether the reversal can be posted in a previous period and whether negative posting is used.

Reverse an Individual Document

FB08

Accounting → Financial Accounting → General Ledger → Document → Reverse → Individual Reversal

Enter the document number, company code, fiscal year. Select reversal reason. Enter reversal posting date (same period or alternative if original period is closed). Post — SAP creates an equal and opposite document linked to the original. Both documents show reversal references.

Mass Reversal of Multiple Documents

F.80

Accounting → Financial Accounting → General Ledger → Document → Reverse → Mass Reversal

Enter a list of document numbers or use selection criteria. Set reversal reason and posting date. SAP reverses all selected documents in one run — useful for reversing an entire month's accruals or batch of incorrectly posted documents.

Reset Cleared Items Before Reversal

FBRA

Accounting → Financial Accounting → General Ledger → Document → Reset Cleared Items

Enter the clearing document number (the payment document that cleared the invoice). FBRA offers: 'Only Reset' (reopens items to open status without reversal) or 'Reset and Reverse' (resets AND immediately reverses the clearing document). After reset, the invoice and payment are back to open items and can be reversed individually.

📌

Exam Tip: You CANNOT directly reverse a CLEARED document. The correct sequence is: (1) FBRA — reset the clearing (reopens invoice and payment to open status). (2) FB08 — reverse each document individually. Also: a document can only be reversed in an OPEN posting period. If the original period is closed, enter an alternative reversal date in the current open period.

🧠

Knowledge Check

Q1Why does SAP Finance never allow deletion of posted accounting documents?

Correct: B — Audit trail and compliance. SAP's no-deletion principle ensures that every financial transaction has a permanent, traceable record. This is a fundamental requirement for SOX (Sarbanes-Oxley) compliance, statutory financial audits, tax authority reviews, and internal financial controls. Document reversal creates equal and opposite entries while preserving both original and reversal permanently.

Q2A vendor invoice has been paid and the items are cleared. The accountant realizes the wrong G/L account was used on the invoice. What is the CORRECT sequence of steps?

Correct: B — FBRA → FB08 → Repost. Posted SAP documents cannot be edited — only reversed. Since the invoice was cleared (paid), the clearing must be reset first (FBRA), which restores both the invoice and payment to open item status. Then reverse the invoice (FB08). Then repost the invoice with the correct G/L account. Finally reprocess the payment.

Q3Which T-code is used for MASS REVERSAL of multiple accounting documents in SAP Finance?

Correct: B — F.80. FB08 reverses ONE document at a time. F.80 reverses multiple documents in a single batch run — useful for reversing all month-end accruals or a batch of incorrectly posted documents. FBRA resets cleared items. OB83 configures reversal reasons.

Q4What is 'Negative Posting' in the context of document reversal in SAP Finance?

Correct: B — Negative credit instead of a debit (clean gross figures). Negative posting avoids inflating gross transaction totals. Example: reversing a credit of INR 50,000 using normal reversal creates a debit of INR 50,000 (total gross = 100,000). Using negative posting creates a negative credit of -50,000 (total gross remains 50,000). Only available for reversal reasons with 'Negative Posting Permitted' flag.

💼

Interview Preparation

📋 Interview Q&A

Q1. How are errors corrected in SAP Finance if documents cannot be deleted?

Since SAP never deletes posted accounting documents (audit trail principle), errors are corrected through a two-step process: (1) Post a REVERSAL document using FB08 (individual) or F.80 (mass) — this creates an equal and opposite entry that cancels the original posting. Both the original and reversal documents remain in the system permanently, linked to each other. (2) If necessary, post a new correct document. If the incorrect document was already cleared (paid), the clearing must be reset first using FBRA before reversal is possible.

Q2. What is the difference between FBRA 'Only Reset' and 'Reset and Reverse' options?

FBRA (Reset Cleared Items) offers two options: 'Only Reset' reopens the cleared items back to open item status without creating any reversal — the clearing document is cancelled but the original invoice and payment are simply reopened as unmatched open items. 'Reset and Reverse' both resets the clearing AND immediately posts a reversal of the clearing document. 'Only Reset' is used when you want to re-clear the items differently (e.g., match against a different payment). 'Reset and Reverse' is used when the entire clearing transaction needs to be undone — for example, if the payment was posted incorrectly.

Module 17 · Controls & Compliance · C_TS4FI

Validations &
Substitutions

SAP enforces business rules automatically through Validations and Substitutions. Validations reject incorrect postings at entry time. Substitutions automatically fill or replace field values — ensuring data quality and policy compliance without manual checks.

Core Tools

~1.5 hrs

Study Time

Practice MCQs

~5%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand the structure of a Validation: Prerequisite, Check, Message
Understand the structure of a Substitution: Prerequisite, Substitution
Configure a Validation rule using GGB0
Configure a Substitution rule using GGB1
Understand Callup Points and where rules are evaluated
Know the difference between Validation (reject) and Substitution (fill)

📖

Core Concepts

Validation (GGB0)

A rule that CHECKS document data BEFORE posting and REJECTS the document if conditions are not met. Structure: Prerequisite (when to apply the check — a Boolean condition) → Check (the condition that must be true) → Message (error or warning text shown to the user). Example: If Cost Center begins with 'CC_MFG', then Business Area must NOT be blank. If the check fails, SAP displays the configured error message and blocks the posting.

Substitution (GGB1)

A rule that AUTOMATICALLY FILLS or REPLACES a field value based on conditions — transparently, without requiring user action. Structure: Prerequisite (when to apply) → Substitution (the field and the value to fill). Example: If Company Code = IN01 and G/L Account = 400000, then automatically set Business Area = BA01. The user does not need to manually enter this field — SAP fills it during document processing.

Callup Points

Define WHEN during document processing the Validation or Substitution rule is evaluated: Callup Point 1 = Document Header level (before line items are entered). Callup Point 2 = Line Item level (each line is checked individually). Callup Point 3 = Complete Document level (after all line items entered, checking cross-line conditions like overall balance).

Validation vs Substitution — Quick Comparison

Validation: CHECKS data → REJECTS if wrong → Protects data quality → Configured in GGB0.

Substitution: CHANGES data → FILLS automatically → Improves efficiency and consistency → Configured in GGB1.

Both are activated per Application (Application 2 = FI document posting) and assigned to a specific Company Code. The sequence number determines evaluation order when multiple rules exist.

⚙️

Configuration Examples

Configure a Validation Rule

GGB0

Accounting → Financial Accounting → General Ledger → Environment → Current Settings → Define Validation

Create validation ZVAL01: Prerequisite: Company Code = 'IN01' AND BSEG-HKONT (G/L account) = '400000' (Office Rent). Check: BSEG-KOSTL (Cost Center) is NOT initial (not blank). Message: Error E001 — 'Cost Center is mandatory for Office Rent postings'. Now, any posting to account 400000 in IN01 without a Cost Center is rejected.

Configure a Substitution Rule

GGB1

Accounting → Financial Accounting → General Ledger → Environment → Current Settings → Define Substitution

Create substitution ZSUB01: Prerequisite: Company Code = 'IN01' AND BSEG-HKONT (G/L account) = '141000' (Trade Receivables). Substitution: Set BSEG-GSBER (Business Area) = 'BA01' automatically. Now, every posting to account 141000 automatically defaults Business Area to BA01 without the user entering it manually.

Activate Validation/Substitution for Company Code

SPRO → Financial Accounting → Financial Accounting Global Settings → Document → Document Control → Activate Validations/Activate Substitutions

Activate validation ZVAL01 for Company Code IN01, Callup Point 2 (line item level). Activate substitution ZSUB01 for IN01, Callup Point 2. Without activation, the rules exist but are not applied during document entry.

📌

Exam Tip: GGB0 = Validations (memory aid: '0' = zero-tolerance, the posting is REJECTED if it fails). GGB1 = Substitutions (memory aid: '1' = fills ONE field automatically). Both use the same Boolean logic structure (Prerequisite + Check/Substitution). Callup Point 2 (line item) is the most commonly used point for FI validations and substitutions.

🧠

Knowledge Check

Q1What is the fundamental difference between a Validation and a Substitution in SAP Finance?

Correct: B — Validation rejects; Substitution fills. A Validation checks data and stops the posting if the condition fails. A Substitution automatically populates a field value based on a condition — the posting proceeds, just with an auto-filled field.

Q2Which T-code is used to configure Validation rules in SAP Finance?

Correct: A — GGB0 (Validations). GGB1 is for Substitutions. Memory aid: '0' represents zero-tolerance (the system rejects the posting). '1' represents filling in one value (Substitution).

Q3At which point during document processing does a Substitution typically occur?

Correct: B — Automatically during entry at the Callup Point. Substitutions fire during document entry at the configured Callup Point (header, line item, or complete document level) and fill the target field value automatically. The user often does not realize the substitution occurred unless they check the field value afterward.

Q4A company wants to enforce that every posting to the Office Rent account (400000) MUST have a Cost Center entered. Which tool should be configured?

Correct: B — A Validation that rejects if Cost Center is blank. Since the requirement is to ENFORCE (mandate, not default) a Cost Center entry, a Validation is the correct tool — it checks the condition and rejects the posting with an error if Cost Center is missing. A Substitution would only fill a default value silently, which does not enforce user diligence.

💼

Interview Preparation

📋 Interview Q&A

Q1. Give a real business example of when you would use a Validation vs. a Substitution.

Validation example: A company requires that every posting to a high-value expense account (over INR 1,00,000) must have an Internal Order assigned for project tracking. A Validation checks this condition and rejects the posting with an error if the Internal Order is missing — forcing the user to provide the required information. Substitution example: A company wants every posting to a specific bank account to automatically default to Business Area 'BA01' (Treasury). A Substitution fills this value automatically — the user doesn't need to remember or manually enter it, and it can't be entered incorrectly.

Q2. How are Validations and Substitutions activated and what controls their evaluation order?

Validations and Substitutions are configured with: an Application (Application 2 = FI document posting), a Callup Point (1=Header, 2=Line Item, 3=Complete Document), the Boolean logic (Prerequisite + Check or Substitution), and assigned to specific Company Codes via activation in SPRO. When multiple rules are configured for the same Callup Point, a sequence number determines the order of evaluation — rules with lower sequence numbers are evaluated first.

Module 18 · AR Management · C_TS4FI

Dunning Procedure

Dunning automates customer payment reminders for overdue invoices, helping organizations manage receivables proactively, reduce Days Sales Outstanding (DSO), and improve cash collection — all without manual intervention.

Config Objects

~1.5 hrs

Study Time

Practice MCQs

~5%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand the Dunning Procedure concept and dunning levels
Configure a Dunning Procedure with multiple levels (FBMP)
Assign Dunning Procedure to customer Business Partner master
Execute a Dunning Run and generate dunning notices (F150)
Understand dunning blocks and how they prevent dunning for specific items
Know T-codes: FBMP, F150

📖

Core Concepts

Dunning Procedure

A configured set of rules that automate customer payment reminders for overdue invoices. Defines multiple escalating levels — each with a minimum days overdue threshold, a dunning charge (late fee), interest calculation rules, and a dunning letter template (text/form). Configured in FBMP. Assigned to the customer Business Partner master record (Company Code AR data).

Dunning Levels

Typical dunning procedure has up to 4 levels: Level 1 = Friendly Reminder (e.g., 10 days overdue, no charge). Level 2 = Second Notice (e.g., 30 days overdue, small fee). Level 3 = Final Notice (e.g., 60 days overdue, higher fee, formal tone). Level 4 = Legal Collection Referral (e.g., 90 days overdue, account flagged for legal action). Each subsequent dunning run can only escalate to the next level if the minimum days threshold for that level has been met since the last run.

Dunning Run (F150)

Executes the dunning process: selects overdue open items per customer, determines the correct dunning level based on overdue days and prior dunning history, generates a dunning proposal for review, and after approval prints/sends dunning notices. The dunning level and last dunning date are recorded in the customer BP master after each run.

Dunning Block

A flag that can be set on the customer BP master or on a specific document to EXCLUDE it from dunning. Used when a customer dispute is in progress, or when a specific invoice should not be dunned while under review. The dunning run will skip blocked customers/items entirely.

⚙️

Configuration & Execution

Dunning Run — F150 — SAP S/4HANA [DEV — Client 100]

▶

■

↺

Transaction:

F150

Parameters

Schedule

Status

Dunning Run: GIM Group — May 2025 Customer Dunning

Run Date

31.05.2025

Identification

MAY2025_DUN

Dunning Date

31.05.2025

Company Codes

IN01

Customer Range

All Customers

Status

Parameters maintained — ready for proposal

Save (Ctrl+S)

Back (F3)

Cancel (F12)

Dunning Run MAY2025_DUN configured — proposal pendingClient 100 | DEV | EN

Configure Dunning Procedure

FBMP

SPRO → Financial Accounting → Accounts Receivable and Payable → Business Transactions → Dunning → Dunning Procedures → Define Dunning Procedures

Create procedure ZDUN: Dunning Interval = 7 days, Number of dunning levels = 4. Level 1: 10 days overdue, no charge, friendly text. Level 2: 30 days overdue, charge = 500 INR, second notice text. Level 3: 60 days overdue, charge = 1000 INR, final notice text. Level 4: 90 days overdue, charge = 2000 INR, legal referral text.

Assign Dunning Procedure to Customer

Cross-Application Components → Business Partner → BP

Open Business Partner C-100001 → Company Code AR data → assign Dunning Procedure = ZDUN. Now all open invoices for this customer will be evaluated by the dunning program when overdue.

Execute Dunning Run

F150

Accounting → Financial Accounting → Accounts Receivable → Periodic Processing → Dunning

Step 1: Enter Run Date and Identification. Step 2: Maintain Parameters — Company Code IN01, Dunning Date, Customer range = all. Step 3: Schedule Dunning Proposal — SAP identifies all customers with overdue items and calculates the appropriate dunning level for each. Step 4: Review and edit proposal if needed. Step 5: Print Dunning Notices — generates letters/emails to send to customers.

📌

Exam Tip: The dunning procedure is assigned in the CUSTOMER Business Partner master (Company Code AR data) — not at the system or company code level. The dunning run sequence (F150) mirrors the APP structure: Parameters → Proposal → Review → Print. If a dunning block is set in the BP master or a specific document, the dunning program SKIPS that customer/item entirely.

🧠

Knowledge Check

Q1Which T-code is used to CONFIGURE Dunning Procedures in SAP Finance?

Correct: A — FBMP. FBMP = Define Dunning Procedures (configuration). F150 = Execute the dunning run. FBZP = configures the Automatic Payment Program. OBB8 = configures payment terms.

Q2Where is the Dunning Procedure assigned in SAP S/4HANA?

Correct: B — Customer BP master data. The dunning procedure is assigned per customer in their Business Partner Company Code AR data. This means different customers can have completely different dunning procedures based on their risk profile or business relationship.

Q3After a successful dunning run for a customer, what is updated in the customer's Business Partner master?

Correct: B — Dunning level and last dunning date recorded. SAP tracks the highest dunning level reached and the date of the last dunning run. In the next dunning run, SAP checks if enough days have passed since the last dunning (per the level's minimum days requirement) before escalating to the next level.

Q4A specific customer invoice is currently under formal dispute. The Finance team does NOT want this invoice to receive a dunning notice while the dispute is being resolved. What should be configured?

Correct: B — Set a Dunning Block. A Dunning Block can be applied at the document level (excludes just that specific invoice) or at the customer master level (excludes all items for that customer). The dunning run will completely skip blocked items/customers, preventing inappropriate reminders during a dispute.

💼

Interview Preparation

📋 Interview Q&A

Q1. Explain the Dunning process in SAP Finance from configuration to execution.

Dunning is SAP's automated process for sending escalating payment reminders to customers with overdue invoices. Configuration starts with FBMP, where a Dunning Procedure is defined with multiple levels — each specifying minimum days overdue, dunning charges, interest, and letter text. The procedure is then assigned to relevant customer Business Partners in their AR Company Code data. During execution, the dunning run (F150) identifies overdue open items, calculates the appropriate dunning level for each customer based on overdue days and prior dunning history, generates a proposal for review, and after approval, prints or sends dunning notices. The customer's dunning level and last dunning date are updated for tracking.

Q2. How does SAP determine which dunning level to apply to a customer in a given run?

SAP checks the customer's open items and finds the oldest overdue invoice (the one with the most days past due). It compares the days overdue against the minimum days threshold for each configured dunning level. SAP also checks the customer's CURRENT dunning level (recorded from the last run) and verifies that the minimum interval (e.g., 7 or 30 days) has elapsed since the last dunning before escalating to the next level. This prevents a customer from receiving Level 4 (legal referral) immediately if they were only at Level 1 last week — escalation happens gradually through the configured levels.

Module 19 · AR Management · C_TS4FI

Correspondence

SAP supports generation of formal financial communication with customers and vendors — account statements, balance confirmations, and other correspondence — directly from system data for professional, accurate communication.

Correspondence Types

~1 hr

Study Time

Practice MCQs

~4%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand the purpose of correspondence in SAP Finance
Configure correspondence types (OB77)
Generate individual correspondence (FB12)
Print/process correspondence requests (F.64)
Generate customer account statements and balance confirmations

📖

Core Concepts

Correspondence

Formal financial communication generated from SAP data — account statements, open item lists, balance confirmations, payment notices. Ensures accurate, system-generated communication with customers and vendors rather than manually drafted letters that could contain errors. Configured types in OB77.

Individual Correspondence (FB12)

A two-step process: (1) REQUEST — using FB12, the user selects a correspondence type and the relevant account/document, creating a correspondence request. (2) PRINT — using F.64, the system processes all pending correspondence requests and generates the output (printed letter, PDF, or email).

📋

Standard Correspondence Types

Type	Name	Description
SAP01	Account Statement	Shows all line items (open and cleared) within a specified date range
SAP02	Open Item List	Shows only currently open items for a customer/vendor
SAP03	Balance Confirmation	Formal confirmation of account balance — often required for statutory audits
SAP06	Payment Notice	Notifies a vendor or customer of a specific payment made/received

Configure Correspondence Type

OB77

SPRO → Financial Accounting → Financial Accounting Global Settings → Correspondence → Define Correspondence Types

Review standard types SAP01-SAP06. Each type links to a print program and a SAPscript/Smart Form/Adobe Form template that controls the visual layout of the document.

Request Individual Correspondence

FB12

Accounting → Financial Accounting → Accounts Receivable → Account → Correspondence → Request

Select Correspondence Type = SAP01 (Account Statement). Enter Customer = C-100001, date range = 01.04.2025 to 31.05.2025. Save — this creates a correspondence request in the queue.

Print/Process Correspondence

F.64

Accounting → Financial Accounting → Accounts Receivable → Periodic Processing → Print Correspondence → Print Letters

Run F.64 to process all queued correspondence requests for the period. SAP generates the actual account statement document for C-100001 and routes it to the configured output device (printer, PDF, or email via BCS).

📌

Exam Tip: Correspondence is a TWO-STEP process: Request (FB12) creates the request, Print (F.64) generates the actual output. SAP01 = Account Statement is the most commonly tested correspondence type. In S/4HANA, correspondence can also be sent via email using BCS (Business Communication Services).

🧠

Knowledge Check

Q1Which T-code is used to REQUEST individual correspondence (e.g., an account statement) for a customer?

Correct: A — FB12. FB12 requests individual correspondence — it queues the request. F.64 actually prints/generates the output. OB77 configures correspondence types. The sequence is always Request (FB12) then Print (F.64).

Q2Which standard SAP correspondence type generates a customer's Account Statement?

Correct: A — SAP01 (Account Statement). SAP01 shows all items within a period. SAP02 = Open Item List (only currently outstanding). SAP03 = Balance Confirmation. SAP06 = Payment Notice.

💼

Interview Preparation

📋 Interview Q&A

Q1. Explain the correspondence process in SAP Finance.

Correspondence is a two-step process. First, individual correspondence is REQUESTED using transaction FB12 — the user selects the correspondence type (e.g., SAP01 for Account Statement), the relevant customer or vendor, and a date range. This creates a correspondence request in a print queue. Second, the correspondence is PRINTED or generated using F.64, which processes all pending requests and produces the actual document — printed letter, PDF, or email. This separation allows batch processing of multiple correspondence requests together at period-end.

Module 20 · Reporting · C_TS4FI

Financial Statement Version
(FSV)

The Financial Statement Version defines how the Balance Sheet and Profit & Loss statement are structured and presented in SAP — the critical link between raw G/L account balances and the formal financial reports management and regulators see.

Config Steps

~2 hrs

Study Time

Practice MCQs

~8%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand FSV hierarchy levels and structure
Create a Financial Statement Version (OB58)
Assign G/L accounts to FSV nodes
Execute financial statements using the FSV (F.01)
Understand the 'Not Assigned' and 'Balance' validation checks
Know T-codes: OB58, F.01

📖

Core Concepts

Financial Statement Version (FSV)

A configurable reporting hierarchy that organizes G/L accounts into the formal structure of a Balance Sheet and Profit & Loss statement. The FSV does NOT change the underlying G/L accounts — it is purely a presentation/reporting layer that groups accounts into meaningful categories for external reporting. Created in OB58.

FSV Hierarchy Levels

Level 1: The Financial Statement Version itself (e.g., GIND = India GAAP format). Level 2: Major Balance Sheet/P&L groupings (Assets, Liabilities & Equity / Revenue, Expenses). Level 3: Main line items (Fixed Assets, Current Assets, Share Capital, Reserves & Surplus, Sales Revenue, Cost of Goods Sold). Level 4+: Individual G/L account number ranges or specific accounts assigned to each line item.

⚙️

Configuration Steps

Create Financial Statement Version

OB58

SPRO → Financial Accounting → General Ledger Accounting → Business Transactions → Closing → Document → Define Financial Statement Versions

Create FSV key GIND (GIM Group India GAAP). Define the top-level hierarchy: 'Assets', 'Liabilities & Equity' (Balance Sheet) and 'Revenue', 'Expenses' (P&L). Build sub-nodes within each — e.g., 'Assets' → 'Fixed Assets', 'Current Assets', 'Cash and Bank Balances'.

Assign G/L Accounts to FSV Nodes

OB58

Same transaction — Edit Financial Statement Items

Under each node, assign specific G/L account number ranges. Example: 'Fixed Assets' node → accounts 100000–109999. 'Cash and Bank Balances' node → accounts 110000–119999. 'Sales Revenue' node → accounts 200000–209999. Every active G/L account with a balance must be assigned somewhere in the FSV.

Execute Financial Statement Report

F.01

Accounting → Financial Accounting → General Ledger → Information System → General Ledger Reports → Balance Sheet/Profit and Loss Statement → General → Actual/Actual Comparison → Financial Statement

Run F.01 with: Company Code IN01, Fiscal Year 2025, Reporting Period current, FSV = GIND. SAP generates the complete Balance Sheet and P&L in the GIND structure, with drill-down capability to individual G/L account balances and line items.

📌

Exam Tip: Every G/L account with a non-zero balance MUST be assigned to the FSV. Unassigned accounts appear in a 'Not Assigned' section of the F.01 report — this signals a configuration error. The 'Balance' node of the FSV should ALWAYS equal zero (because Total Assets = Total Liabilities + Equity, the fundamental accounting equation). A non-zero Balance node means accounts are missing assignments.

🧠

Knowledge Check

Q1Which T-code is used to create a Financial Statement Version in SAP Finance?

Correct: A — OB58. OB58 creates and maintains Financial Statement Versions, including the hierarchy structure and G/L account assignments. F.01 EXECUTES the financial statement report using a previously configured FSV.

Q2What does it mean when G/L accounts appear in the 'Not Assigned' section when running F.01?

Correct: B — Configuration error: unmapped accounts. Every active G/L account with a balance must be assigned to an FSV node. If it is not, F.01 shows it under 'Not Assigned' — flagging a configuration gap that needs to be corrected before the financial statement is complete and accurate.

Q3In a correctly configured Financial Statement Version, what should the 'Balance' node value always equal?

Correct: B — Zero. The fundamental accounting equation states Assets = Liabilities + Equity. If the FSV is correctly configured with all accounts properly assigned, the 'Balance' check node will always equal zero. A non-zero value signals missing account assignments or an incorrectly structured FSV.

💼

Interview Preparation

📋 Interview Q&A

Q1. What is a Financial Statement Version and why is it important?

The Financial Statement Version (FSV) is a configurable reporting hierarchy that organizes the company's G/L accounts into the formal structure of a Balance Sheet and Profit & Loss statement. It does NOT change the underlying accounting data — it is purely a presentation layer used for external financial reporting. The FSV is critical because it allows the same G/L account structure to be presented differently for different audiences — for example, a statutory FSV for tax authorities and a management FSV with different groupings for internal review — without duplicating any data.

Q2. A finance manager reports the financial statement report doesn't 'balance' — Assets don't equal Liabilities plus Equity. How would you diagnose this?

I would run F.01 and check the 'Not Assigned' section — this almost always reveals G/L accounts with balances that haven't been mapped to any FSV node. Common causes: a new G/L account was created but never assigned in OB58, or an account range used in the FSV doesn't cover a newly created account number. I would identify the specific unassigned accounts, determine their correct classification (Asset, Liability, Revenue, Expense), and assign them to the appropriate FSV node in OB58. After the assignment, I would rerun F.01 to confirm the Balance node returns to zero.

Module 21 · Cross-Module Integration · C_TS4FI

FI Integration with MM
Procure-to-Pay (P2P)

SAP integrates procurement activities with Finance automatically. Procurement transactions in Materials Management generate accounting entries in real time without manual intervention — understanding this flow is essential for every FICO consultant.

Process Steps

~2.5 hrs

Study Time

Practice MCQs

~10%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand the Procure-to-Pay (P2P) business process end-to-end
Understand Material Master and Valuation Class
Configure Automatic Account Determination using OBYC
Understand GR/IR (Goods Receipt/Invoice Receipt) clearing account
Trace the complete accounting flow from PO to Payment
Know T-codes: ME21N, MIGO, MIRO, OBYC

📖

Core Concepts

Procure-to-Pay Process

The complete cycle from requesting goods/services to paying the vendor: Purchase Requisition → Purchase Order (ME21N) → Goods Receipt (MIGO) → Invoice Verification (MIRO) → Vendor Payment (F110/F-53). Each step has distinct system impact — only certain steps create FI accounting documents.

Material Master and Valuation Class

Every material in SAP has a Material Master with a Valuation Class — a key that links the material to specific G/L accounts via the account determination configuration. Different valuation classes (e.g., raw materials, finished goods, trading goods) can post to different inventory G/L accounts even within the same chart of accounts.

Automatic Account Determination (OBYC)

Configures which G/L accounts are automatically used for MM-related postings, based on Valuation Class and Chart of Accounts. Key transaction keys: BSX = Inventory posting (stock account). WRX = GR/IR Clearing account. PRD = Price difference (variance between PO price and standard price). KON = Consignment liabilities.

GR/IR Clearing Account

A temporary clearing account that bridges the time gap between Goods Receipt and Invoice Receipt. At Goods Receipt, the GR/IR account is CREDITED (liability — goods received but invoice not yet processed). At Invoice Receipt (MIRO), GR/IR is DEBITED and the vendor account is credited. After both steps are complete, the GR/IR account nets to zero for that transaction. A non-zero balance indicates unmatched goods receipts or invoices requiring investigation.

⚙️

P2P Accounting Flow — Step by Step

P2P Step	T-Code	FI Document Created?	Accounting Entry
Purchase Requisition	ME51N	No	No accounting impact
Purchase Order	ME21N	No	Commitment/statistical only
Goods Receipt	MIGO	Yes	Dr Inventory (Stock) / Cr GR/IR Clearing
Invoice Verification	MIRO	Yes	Dr GR/IR Clearing / Cr Vendor (AP)
Vendor Payment	F-53 / F110	Yes	Dr Vendor (AP) / Cr Bank

Create Purchase Order

ME21N

Logistics → Materials Management → Purchasing → Purchase Order → Create

Buyer creates PO for 1,000 units of Raw Material RM-001 from vendor V-200001 at INR 50/unit (total INR 50,000). NO FI accounting document is created — only a commitment in MM, visible as a statistical figure in budget reports.

Post Goods Receipt

MIGO

Logistics → Materials Management → Inventory Management → Goods Movement → Goods Receipt → For Purchase Order

Warehouse receives the 1,000 units. Posting GR creates the FIRST FI accounting document: Dr Inventory/Stock account (e.g., 130000) INR 50,000 / Cr GR/IR Clearing account (e.g., 195000) INR 50,000. Stock quantity and value increase immediately.

Post Invoice Verification

MIRO

Logistics → Materials Management → Logistics Invoice Verification → Document Entry → Enter Invoice

Accounts Payable team enters the vendor's invoice for INR 50,000 + GST. Posting MIRO creates the SECOND FI document: Dr GR/IR Clearing 50,000 + Dr GST Input Tax 9,000 / Cr Vendor (AP) 59,000. After this posting, the GR/IR clearing account nets to zero (it was credited 50,000 at GR, debited 50,000 at MIRO).

Pay the Vendor

F110 or F-53

The Automatic Payment Program or manual payment clears the vendor's open invoice: Dr Vendor (AP) 59,000 / Cr Bank 59,000. The P2P cycle is complete.

📌

Exam Tip: Purchase Order creates NO FI document — only Goods Receipt and Invoice Verification create FI documents. GR/IR clearing nets to zero after both GR and IR are processed for the same quantity/amount. OBYC transaction key BSX = inventory posting. WRX = GR/IR. This P2P flow appears as both standalone questions and integrated FICO scenarios in C_TS4FI.

🧠

Knowledge Check

Q1At which step in the Procure-to-Pay process is the FIRST FI accounting document created?

Correct: C — Goods Receipt (MIGO). Purchase Requisitions and Purchase Orders create no FI accounting document — only commitments/statistical figures. The first real FI document is created at Goods Receipt: Dr Inventory, Cr GR/IR Clearing.

Q2Which T-code configures automatic G/L account determination for MM postings based on Valuation Class?

Correct: A — OBYC. OBYC (Configure Automatic Postings) maps transaction keys (BSX, WRX, PRD, etc.) to G/L accounts based on Chart of Accounts and Valuation Class. VKOA is used for SD revenue account determination (a different integration area).

Q3In the P2P process, what does the GR/IR clearing account represent?

Correct: B — Temporary clearing account. GR/IR is credited at Goods Receipt (goods received, invoice not yet processed) and debited at Invoice Receipt/MIRO (invoice now matched). Once both GR and MIRO are posted for the same transaction, GR/IR nets to zero. Open balances indicate unmatched receipts or invoices requiring follow-up.

Q4Which OBYC transaction key controls the G/L account used for inventory (stock) postings during Goods Receipt?

Correct: B — BSX. BSX = Inventory posting (stock account). WRX = GR/IR clearing account. PRD = Price difference (PO price vs. standard price variance). KON = Consignment liabilities. These transaction keys are central to MM-FI integration configuration.

💼

Interview Preparation

📋 Interview Q&A

Q1. Explain the accounting impact at each step of the Procure-to-Pay process.

Purchase Order (ME21N): No FI document — only a commitment/statistical entry. Goods Receipt (MIGO): First FI document — Dr Inventory account / Cr GR/IR Clearing account. The stock value increases on the Balance Sheet. Invoice Verification (MIRO): Second FI document — Dr GR/IR Clearing / Cr Vendor (AP) account. This matches the goods received against the vendor invoice; the GR/IR account nets to zero. Vendor Payment (F-53 or F110): Third FI document — Dr Vendor (AP) / Cr Bank account. This completes the cycle.

Q2. What causes an open balance in the GR/IR clearing account and how is it investigated?

An open GR/IR balance occurs when goods have been received (GR posted) but the vendor invoice has not yet been processed (MIRO not posted), or vice versa — an invoice was received and posted before the goods receipt. To investigate, run the GR/IR Analysis report (transaction MB5S) which shows all open GR/IR items by purchase order. For goods received but not invoiced, follow up with the vendor for the invoice. For invoices posted without a matching goods receipt, verify with the warehouse if goods were actually received and post the missing MIGO entry.

Module 22 · Cross-Module Integration · C_TS4FI

FI Integration with SD
Order to Cash (O2C)

Sales activities are executed in Sales and Distribution, while their financial impact is automatically recorded in Finance. SAP integrates SD with FI so that billing transactions generate accounting documents without manual postings.

Process Steps

~2.5 hrs

Study Time

Practice MCQs

~10%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand the Order-to-Cash (O2C) business process end-to-end
Understand Customer Master Sales Area data and Material Master SD views
Understand Revenue Account Determination using VKOA
Understand the role of Condition Records and Pricing Procedures
Trace the complete accounting flow from Sales Order to Customer Payment
Know T-codes: VA01, VL01N, VF01, VKOA

📖

Core Concepts

Order-to-Cash Process

The complete cycle from receiving a customer order to collecting payment: Sales Order (VA01) → Outbound Delivery (VL01N) → Goods Issue → Billing/Invoice (VF01) → Customer Payment (F-28/F110). Critically — accounting entries are generated during BILLING, not during sales order creation or delivery.

Revenue Account Determination (VKOA)

Configures which G/L revenue account is used during billing, based on the combination of: Sales Organization, Distribution Channel, Customer Account Assignment Group (from customer master), Material Account Assignment Group (from material master), and Account Key (determined by the pricing procedure). This ensures revenue is automatically posted to the correct G/L account without manual intervention.

Condition Records and Pricing Procedure

Condition Records store pricing information (base price, discounts, surcharges, taxes) for specific combinations of customer, material, and sales area. The Pricing Procedure determines the sequence in which these conditions are applied to calculate the final invoice price. Each condition type can be linked to an Account Key, which VKOA uses to determine the G/L posting.

Why Billing (Not Order) Creates the FI Document

A Sales Order represents intent — the customer has ordered, but no value has been delivered or earned yet. Even Goods Delivery does not create revenue (only inventory movement). Revenue recognition occurs at BILLING because this is when the company has a legally enforceable right to payment — the goods/services have been delivered/rendered and invoiced. This matches the accounting principle of revenue recognition.

⚙️

O2C Accounting Flow — Step by Step

O2C Step	T-Code	FI Document Created?	Accounting Entry
Sales Order	VA01	No	Credit check/commitment only
Outbound Delivery & Goods Issue	VL01N	Yes (Goods Issue)	Dr Cost of Goods Sold / Cr Finished Goods Inventory
Billing (Customer Invoice)	VF01	Yes	Dr Customer (AR) / Cr Revenue / Cr Output Tax
Customer Payment	F-28 / F110	Yes	Dr Bank / Cr Customer (AR)

Create Sales Order

VA01

Logistics → Sales and Distribution → Sales → Order → Create

Sales team creates SO for customer C-100001 ordering 100 units of Product X at INR 1,000/unit. NO FI document is created — only a credit limit check is performed against the customer's available credit.

Post Goods Issue at Delivery

VL01N

Logistics → Sales and Distribution → Shipping and Transportation → Outbound Delivery → Create

Warehouse picks, packs, and ships the goods. Posting Goods Issue creates an FI document: Dr Cost of Goods Sold (COGS) account / Cr Finished Goods Inventory account — at the cost value (not the selling price). This recognizes the expense of fulfilling the order.

Create Billing Document (Invoice)

VF01

Logistics → Sales and Distribution → Billing → Billing Document → Create

Billing department generates the customer invoice based on the delivery. This is the MAIN FI document of the O2C process: Dr Customer (AR) account INR 118,000 / Cr Sales Revenue account INR 100,000 / Cr Output Tax account INR 18,000. Revenue is recognized HERE — not at order creation.

Receive Customer Payment

F-28 or F110

Customer pays the invoice via bank transfer. Posting clears the open item: Dr Bank account INR 118,000 / Cr Customer (AR) INR 118,000. The O2C cycle is complete.

📌

Exam Tip: Accounting entries in SD are created during BILLING (VF01), NOT during Sales Order creation. This is a heavily tested rule. The COGS entry at Goods Issue is at the COST value, separate from the revenue posting at billing (at the SELLING price). VKOA = revenue account determination — based on Sales Org, Distribution Channel, Account Assignment Groups, and Account Key.

🧠

Knowledge Check

Q1In the Order-to-Cash process, at which step is the FI accounting document for REVENUE created?

Correct: C — Billing (VF01). Accounting entries for revenue are created during BILLING, not at Sales Order or Delivery. This is because revenue is only recognized when the company has a legally enforceable right to payment — i.e., when the invoice is issued.

Q2What accounting entry is created at Goods Issue during the O2C process?

Correct: B — Dr COGS / Cr Finished Goods Inventory. Goods Issue at delivery recognizes the cost of the goods leaving inventory — at the COST value (not selling price). This is separate from the revenue recognition that occurs later at billing.

Q3Which transaction is used to configure Revenue Account Determination for SD billing documents?

Correct: B — VKOA. VKOA configures revenue account determination based on Sales Organization, Distribution Channel, Account Assignment Groups (customer and material), and Account Key. OBYC is for MM account determination — the parallel mechanism for procurement integration.

Q4Why does a Sales Order NOT create an FI accounting document, even though the customer has formally committed to purchase?

Correct: B — Revenue recognition principle. Accounting standards require revenue to be recognized only when the performance obligation is satisfied — typically when goods are delivered/services rendered and the company has a right to payment. A sales order alone does not meet this criterion; only delivery and billing represent actual fulfillment of the transaction.

💼

Interview Preparation

📋 Interview Q&A

Q1. Explain the accounting impact at each step of the Order-to-Cash process.

Sales Order (VA01): No FI document — credit check only. Outbound Delivery/Goods Issue (VL01N): First FI document — Dr Cost of Goods Sold / Cr Finished Goods Inventory, posted at cost value. Billing (VF01): Main FI document — Dr Customer (AR) / Cr Sales Revenue / Cr Output Tax, posted at selling price including tax. This is where revenue is officially recognized. Customer Payment (F-28 or F110): Final FI document — Dr Bank / Cr Customer (AR), clearing the open receivable.

Q2. What is the role of VKOA in FI-SD integration and what factors determine the revenue G/L account?

VKOA (Configure Revenue Account Determination) is the central transaction mapping SD billing conditions to FI G/L revenue accounts. The revenue G/L account is determined by a combination of factors: Sales Organization (which selling entity), Distribution Channel (e.g., wholesale vs. retail), Customer Account Assignment Group (from the customer master — classifies customer type), Material Account Assignment Group (from the material master — classifies product type), and the Account Key from the pricing procedure (which condition type drives the revenue recognition). Without correct VKOA configuration, billing documents will fail to determine a revenue account and the billing run will error out.

Module 23 · Tax Configuration · C_TS4FI

Taxes on Sales
& Purchases (A/R & A/P)

Tax calculation must be automatic and accurate to meet statutory requirements. SAP manages all taxes using tax procedures, tax codes, and dedicated tax G/L accounts — eliminating manual tax calculation errors.

Config Steps

~2 hrs

Study Time

Practice MCQs

~8%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand the Tax Calculation Procedure concept
Configure Tax Codes with base amount and rate (FTXP)
Configure Input Tax and Output Tax G/L accounts (OB40)
Post vendor and customer invoices with automatic tax calculation
Understand Input Tax vs Output Tax
Know T-codes: FTXP, OB40, OBCL, OBYZ

📖

Core Concepts

Tax Calculation Procedure

Defines the sequence of steps and condition types used to calculate tax on a document. For India: typically uses procedure TAXINN (condition-based) with GST condition types. The procedure is assigned to a country in the Company Code configuration. Determines base amount, tax rate application, and whether tax is calculated on net or gross amount.

Tax Code

A two-character code (e.g., V1, A1) representing a specific tax rate and type. Created and maintained in FTXP. Each tax code is linked to: the tax percentage, the G/L accounts for posting (via OB40), and whether it represents Input Tax (purchases) or Output Tax (sales).

Input Tax vs Output Tax

Input Tax is the tax paid on PURCHASES (e.g., GST paid to a vendor on a purchase). It represents a tax credit/recoverable amount — posted to an Input Tax G/L account (asset-like). Output Tax is the tax COLLECTED on SALES (e.g., GST charged to a customer). It represents a tax liability owed to the government — posted to an Output Tax G/L account (liability).

⚙️

Configuration Steps

Maintain Tax Code — FTXP — SAP S/4HANA [DEV — Client 100]

▶

■

↺

Transaction:

FTXP

Tax Code

Tax Percentage

Account Assignment

Tax Code: V1 — GST Input Tax 18% (Country IN)

Country

IN — India

Tax Code

Description

GST Input Tax 18% — Goods

Tax Type

V — Input Tax

CGST Rate

SGST Rate

Total Rate

18%

Account Key

VST — Input Tax

Save (Ctrl+S)

Back (F3)

Cancel (F12)

Tax Code V1 saved — 18% GST Input split as 9% CGST + 9% SGSTClient 100 | DEV | EN

Define Tax Calculation Procedure

OBYZ / Assign to Country

SPRO → Financial Accounting → Financial Accounting Global Settings → Tax on Sales/Purchases → Basic Settings → Assign Country to Calculation Procedure

Assign Tax Procedure TAXINN to Country IN. This determines how GST (CGST, SGST, IGST) is calculated for all Company Codes in India, including IN01.

Create Tax Codes

FTXP

Accounting → Financial Accounting → General Ledger → Environment → Current Settings → Tax on Sales/Purchases → Maintain Tax Code

Create Tax Code V1: Input Tax, 18% GST (9% CGST + 9% SGST), used for purchases. Create Tax Code A1: Output Tax, 18% GST, used for sales. Tax rates are entered as percentages for each condition type within the procedure.

Assign G/L Accounts to Tax Codes

OB40

SPRO → Financial Accounting → Financial Accounting Global Settings → Tax on Sales/Purchases → Posting → Define Tax Accounts

For Account Key VST (Input Tax): assign G/L account 154000 (GST Input Receivable). For Account Key MWS (Output Tax): assign G/L account 154100 (GST Output Payable). These G/L accounts automatically receive the tax postings whenever V1 or A1 tax codes are used.

Post Vendor Invoice with Tax

FB60

Post vendor invoice: Amount = INR 50,000, Tax Code = V1. SAP automatically calculates GST = INR 9,000 (18% of 50,000). Posting: Dr Expense 50,000 + Dr GST Input 154000 = 9,000 / Cr Vendor 59,000. The tax amount is calculated and posted automatically — no manual entry required.

📌

Exam Tip: Input Tax = tax PAID on purchases (asset/recoverable). Output Tax = tax COLLECTED on sales (liability/payable). Tax codes (V1, A1, etc.) are mandatory fields on vendor and customer invoices when tax is applicable. OB40 links tax Account Keys to specific G/L accounts. India uses TAXINN as the standard tax procedure for GST in S/4HANA.

🧠

Knowledge Check

Q1What is the definition of Input Tax in SAP Finance?

Correct: B — Tax paid on purchases. Input Tax (e.g., GST paid to a vendor when buying goods) is a recoverable amount — it can typically be offset against Output Tax liability. Output Tax is the opposite — tax collected from customers on sales, representing a liability owed to the government.

Q2Which T-code is used to create and maintain Tax Codes in SAP Finance?

Correct: B — FTXP. FTXP creates and maintains tax codes with their associated rates. OB40 assigns G/L accounts to tax Account Keys. OBYZ defines/assigns the tax calculation procedure to countries.

Q3A vendor invoice for INR 100,000 is posted with Tax Code V1 (18% GST Input). What is the TOTAL document amount?

Correct: B — INR 118,000. Tax is calculated on the base amount: 18% of INR 100,000 = INR 18,000. Total document amount = base + tax = INR 100,000 + INR 18,000 = INR 118,000. The vendor account is credited the full INR 118,000 while the expense and tax accounts are debited separately.

Q4Which configuration transaction links a tax Account Key (e.g., VST for Input Tax) to a specific G/L account?

Correct: B — OB40. OB40 (Define Tax Accounts) maps each tax Account Key to a specific G/L account. This ensures that whenever a tax code using that Account Key is applied, the tax amount automatically posts to the correct G/L account.

💼

Interview Preparation

📋 Interview Q&A

Q1. Explain the difference between Input Tax and Output Tax in SAP Finance.

Input Tax is the tax paid when purchasing goods or services from a vendor — for example, GST paid on raw material purchases. It is typically recoverable (a tax credit) and is posted to an Input Tax G/L account (an asset-like account, e.g., GST Input Receivable 154000). Output Tax is the tax collected from customers when selling goods or services — for example, GST charged on a sales invoice. It represents a liability owed to the tax authorities and is posted to an Output Tax G/L account (e.g., GST Output Payable 154100). At period-end, companies typically offset Input Tax against Output Tax to determine the net tax liability payable to the government.

Q2. A vendor invoice is posted but no tax is calculated even though a tax code was entered. What could be the cause?

Several possible causes: (1) The tax code's percentage rate may not be configured correctly in FTXP — check the condition records for the tax type. (2) The tax procedure assigned to the Company Code's country may be incorrect or missing condition types. (3) The G/L account used on the invoice line may be configured as 'tax not relevant' (no tax category in FS00) — the field 'Tax Category' on the G/L account master controls whether tax is applicable. (4) The posting date may fall outside the validity period of the tax code's rate. I would check all four areas systematically to diagnose the issue.

Module 24 · Period-End Closing · C_TS4FI

SAP S/4HANA Finance
Closing Operations

During month-end and year-end closing, organizations must ensure accurate valuation, controlled postings, and correct financial reporting. SAP provides structured tools to support efficient, error-free closing activities.

Closing Activities

~2.5 hrs

Study Time

Practice MCQs

~8%

Exam Weight

Module Progress0%

🎯

Learning Objectives

Understand the standard month-end closing sequence
Perform Foreign Currency Valuation at period-end (FAGL_FC_VAL)
Understand and use special periods for closing adjustments
Understand the Financial Closing Cockpit and its benefits
Perform year-end Balance Carryforward (F.16)
Know T-codes: FAGL_FC_VAL, F.16, OB52, F.01

📖

Core Concepts

Foreign Currency Valuation

At period-end, all open items in foreign currency (unpaid vendor/customer invoices, foreign currency bank balances) must be revalued at the current exchange rate per accounting standards. FAGL_FC_VAL calculates unrealized gains/losses and posts adjustment entries, which are automatically reversed at the start of the next period.

Postings in Special Periods

Closing adjustment entries — audit corrections, management provisions — can be posted in Special Periods (13-16) without reopening the regular periods 1-12. This protects the integrity of the standard monthly close while still allowing year-end adjustments. Special periods are opened specifically in OB52.

Financial Closing Cockpit

An SAP tool that provides a structured, task-based view of all period-end closing activities. Tracks task status, dependencies between tasks, responsible owners, and provides an audit trail of the entire closing process. Replaces ad-hoc spreadsheet-based closing checklists with a system-driven workflow.

Year-End Balance Carryforward (F.16)

At fiscal year-end, F.16 performs two functions: (1) Balance Sheet accounts — carries forward closing balances as the new year's opening balances. (2) P&L accounts — zeros all balances and transfers the net result to the Retained Earnings account configured in OB53. This must be run before any postings can occur in the new fiscal year for certain validations.

📅

Standard Month-End Closing Sequence

Close Sub-Ledgers and Perform Reconciliations

Ensure all vendor invoices, customer invoices, and goods receipts for the period have been posted. Reconcile GR/IR clearing account (run MB5S to check open items). Reconcile bank accounts against bank statements.

Run Foreign Currency Valuation

FAGL_FC_VAL

Accounting → Financial Accounting → General Ledger → Periodic Processing → Closing → Valuate → Foreign Currency Valuation

Update OB08 exchange rates to current month-end rates. Run FAGL_FC_VAL for Company Code IN01, selecting open AR, AP, and GL foreign currency items. Review and post the unrealized gain/loss adjustments.

Post Accruals and Provisions

FB50

Post any necessary accrual entries for expenses incurred but not yet invoiced (e.g., utility bills not yet received). These are typically reversed at the start of the next period using a reversal posting with reason 'AB' (accrual reversal, negative posting permitted).

Close the Current Posting Period

OB52

Once all postings for the period are complete, close the current period (e.g., Period 4/2025) and open the next period (Period 5/2025) in the Posting Period Variant configuration.

Generate Financial Statements

F.01

Accounting → Financial Accounting → General Ledger → Information System → ... → Financial Statement

Run F.01 using the appropriate Financial Statement Version (GIND) to generate the Balance Sheet and P&L for management review and statutory reporting.

Year-End: Run Balance Carryforward

F.16

Accounting → Financial Accounting → General Ledger → Periodic Processing → Closing → Carrying Forward → Balance Carryforward

At fiscal year-end only: run F.16 to carry forward Balance Sheet account balances and zero out P&L accounts, transferring the net result to the Retained Earnings account (configured in OB53).

📌

Exam Tip: Foreign currency revaluation postings are AUTOMATICALLY REVERSED at the start of the next period — this is standard SAP behavior, not a manual step. Special periods (13-16) allow closing adjustments without reopening regular periods. F.16 must be run before P&L accounts can be properly reported in the new fiscal year. The Financial Closing Cockpit is a task management tool, not an accounting transaction itself.

🧠

Knowledge Check

Q1What happens automatically to a Foreign Currency Valuation (FAGL_FC_VAL) adjustment posting at the start of the next period?

Correct: B — Automatically reversed. Since foreign currency revaluation reflects an UNREALIZED (not yet settled) gain or loss, the adjustment is for period-end reporting purposes only. SAP automatically generates a reversal posting effective the first day of the next period, so the original transaction's recorded value is not permanently changed.

Q2Why would a company use Special Periods (13-16) during year-end closing?

Correct: B — Year-end adjustments without reopening regular periods. Special periods (13-16) allow auditors and management to post necessary year-end correcting entries after the regular fiscal periods have been closed, without compromising the integrity of the monthly closing process for periods 1-12.

Q3What does F.16 (Balance Carryforward) do for Profit & Loss accounts at year-end?

Correct: B — Zeros and transfers to Retained Earnings. Unlike Balance Sheet accounts (which carry forward their closing balance as the new year's opening balance), P&L (Income Statement) accounts are zeroed at year-end. The net profit or loss for the year is transferred to the Retained Earnings account configured in OB53.

Q4What is the primary purpose of the Financial Closing Cockpit in SAP S/4HANA?

Correct: B — Task-based closing activity management. The Financial Closing Cockpit is a workflow and tracking tool — it does not perform accounting calculations itself, but organizes, sequences, and tracks the status of all the individual closing tasks (FAGL_FC_VAL, F.13, accrual postings, etc.) that must be completed during the period-end close.

💼

Interview Preparation

📋 Interview Q&A

Q1. Walk me through a typical month-end closing process in SAP S/4HANA Finance.

A typical month-end close includes: (1) Ensure all sub-ledger transactions for the period are posted (vendor invoices, customer invoices, goods receipts). (2) Reconcile GR/IR clearing accounts and bank accounts. (3) Update exchange rates and run Foreign Currency Valuation (FAGL_FC_VAL) for open foreign currency items. (4) Post necessary accrual entries for unbilled expenses or unrecognized revenue. (5) Run depreciation posting for fixed assets if applicable. (6) Close the current posting period and open the next period (OB52). (7) Generate and review financial statements using the configured FSV (F.01). At year-end, an additional step (8) Run Balance Carryforward (F.16) to zero P&L accounts and transfer the net result to Retained Earnings.

Q2. What is the difference between regular periods and special periods in the SAP fiscal year, and when are special periods used?

Regular periods (typically 1-12) represent the normal monthly accounting cycle. Special periods (13-16) are additional periods available exclusively for year-end closing adjustments — entries that need to be posted after the regular periods are closed but before the final financial statements are issued. Examples include audit adjustments, late-discovered errors, and management provisions. Using special periods preserves the integrity of the regular monthly close (periods 1-12 remain closed and unaltered) while still allowing necessary year-end corrections, which are clearly identifiable as occurring in a special closing period rather than mixed into regular operational periods.

🎓

Course Complete — C_TS4FI Certification Ready

All 24 Modules of the Upskeeling SAP S/4HANA FICO Program

🏆

Congratulations — You Are C_TS4FI Ready!

You have completed all 24 modules of the SAP S/4HANA FICO Consultant Lifecycle Program by Upskeeling, covering everything from enterprise structure to closing operations. You are now prepared for the C_TS4FI certification exam and real-world SAP FICO implementation projects.

📱 WhatsApp +91 87631 89057 ✉️ sessions@upskeeling.com

Introduction to SAP &SAP S/4HANA

The Problem with Disconnected Systems

How SAP Solves This

SAP ECC vs SAP S/4HANA — Key Differences

What is SAP Fiori?

Fiori App Types — Three Categories

Long-lived business objects reused across transactions

Data generated from day-to-day business activity

System settings that control how SAP behaves

Assignment — SAP & S/4HANA Fundamentals

📋 Interview Q&A

Enterprise Structurein SAP S/4HANA

SAP Enterprise Structure — Top to Bottom

Assignment — Enterprise Structure Configuration

📋 Interview Q&A

Fiscal Year Variant &Posting Period Variant

Assignment — Fiscal Year & Posting Period Configuration

📋 Interview Q&A

Account Types, Document Types& Posting Keys

Assignment — Accounting Document Basics

📋 Interview Q&A

G/L Accounts &Document Splitting

Assignment — G/L Master & Reporting Setup

📋 Interview Q&A

G/L Tolerances &Default User Parameters

📋 Interview Q&A

Controlling Area &FI–CO Integration

FI vs CO — The Core Distinction

Assignment — FI-CO Structure Setup

📋 Interview Q&A

Leading & Non-Leading LedgersParallel Accounting

Business Requirement

How Postings Flow

Assignment — Parallel Accounting — Conceptual Understanding

📋 Interview Q&A

Finance & Controlling IntegrationFI–CO Deepening

📋 Interview Q&A

Accounts Receivable & PayableBusiness Partner — Customer & Vendor

Assignment — Business Partner Configuration

📋 Interview Q&A

Currencies &Exchange Rates

📋 Interview Q&A

Document Postingin SAP Finance

📋 Interview Q&A

Payments &House Bank Configuration

Assignment — Manual Payments Setup

📋 Interview Q&A

Automatic Payment Program(APP — F110)

📋 Interview Q&A

Down PaymentsCustomer & Vendor

📋 Interview Q&A

Document Reversal& Reset of Cleared Items

📋 Interview Q&A

Validations &Substitutions

Validation vs Substitution — Quick Comparison

📋 Interview Q&A

Dunning Procedure

📋 Interview Q&A

Correspondence

📋 Interview Q&A

Financial Statement Version(FSV)

📋 Interview Q&A

FI Integration with MMProcure-to-Pay (P2P)

📋 Interview Q&A

FI Integration with SDOrder to Cash (O2C)

Why Billing (Not Order) Creates the FI Document

📋 Interview Q&A

Taxes on Sales& Purchases (A/R & A/P)

📋 Interview Q&A

SAP S/4HANA FinanceClosing Operations

📋 Interview Q&A

Introduction to SAP &
SAP S/4HANA

Enterprise Structure
in SAP S/4HANA

Fiscal Year Variant &
Posting Period Variant

Account Types, Document Types
& Posting Keys

G/L Accounts &
Document Splitting

G/L Tolerances &
Default User Parameters

Controlling Area &
FI–CO Integration

Leading & Non-Leading Ledgers
Parallel Accounting

Finance & Controlling Integration
FI–CO Deepening

Accounts Receivable & Payable
Business Partner — Customer & Vendor

Currencies &
Exchange Rates

Document Posting
in SAP Finance

Payments &
House Bank Configuration

Automatic Payment Program
(APP — F110)

Down Payments
Customer & Vendor

Document Reversal
& Reset of Cleared Items

Validations &
Substitutions

Financial Statement Version
(FSV)

FI Integration with MM
Procure-to-Pay (P2P)

FI Integration with SD
Order to Cash (O2C)

Taxes on Sales
& Purchases (A/R & A/P)

SAP S/4HANA Finance
Closing Operations