How do you test and validate the configuration of these variants in SAP FICO ?

Testing involves performing transactions across different modules (GL,AP,AR, etc) using various document types and ensuring that the configured variants enforce the desired behavior.

Validation is done by comparing the actual results with the expected outcomes and making necessary adjustments.

First — Understand the Situation

Senior consultant finished configuration.

Now they ask you:

“Test whether everything works.”

You don’t test by looking at SPRO.

You test by posting transactions.

This is called End-to-End Testing (E2E).

Golden Rule of SAP Testing

Configuration is correct only if business transactions work correctly.

So testing = simulate real business scenarios.

Step-by-Step Testing Approach

Step 1 — Test GL Posting (FB50 / FB01)

Post simple journal entry:

Dr Expense GL
Cr Bank GL

Verify:

  • Posting allowed? → Posting Period Variant ✔

  • Fiscal year correct? → Fiscal Year Variant ✔

  • Correct GL available? → Chart of Accounts ✔

  • Mandatory fields appear? → Field Status ✔

If entry posts successfully → global settings working.

Step 2 — Test Accounts Payable (Vendor)

Create vendor invoice (FB60).

Check:

  • Posting period open?

  • Vendor fields mandatory?

  • Tax fields appear?

  • Correct fiscal year?

Then post vendor payment (F-53).

This validates AP configuration.

Step 3 — Test Accounts Receivable (Customer)

Create customer invoice (FB70).

Check:

  • Revenue posting works

  • Customer fields appear correctly

  • Period control works

Then post customer receipt (F-28).

This validates AR flow.

Step 4 — Test Period Control

Try posting in:

  • Current month → should work ✔

  • Previous closed month → should fail ❌

This confirms OB52 working.

Step 5 — Test Field Status

Try posting without mandatory fields.

Example:

  • Skip cost center for expense GL → should error ❌

  • Skip value date for bank GL → should error ❌

This confirms Field Status working.

Final Step — Compare Expected vs Actual

Testing always ends with:

ExpectedActualResult
Period closedErrorPass
Mandatory field missingErrorPass
Valid postingSuccessPass

If mismatch → configuration fix required.

Interview Answer Version

If asked:

How do you test SAP FI configuration?

Answer:

By performing end-to-end business transactions such as G/L postings, vendor invoices, customer invoices, and payments, and verifying that the system behavior matches the expected configuration.

That answer shows real project understanding.

Next topic logically: Document Types & Posting Keys — the core of posting.

Continue?

Comments

Post a Comment

Popular posts from this blog

What is General Ledger Master Data creation and deletion ?

Image
SAP FICO Global Parameters refer to a set of mandatory variants and control parameters that must be maintained for every company code to enable smooth financial accounting and integration with Controlling. These parameters define the basic accounting framework of a company code, such as: Chart of Accounts Fiscal Year Variant Posting Period Variant Field Status Variant All these are maintained based on the Variant Principle. Master Data O Master Data is the information which remains in the system for a long period of time and does not change so often such as G/L Master Data, Customer Master Data, Vendor Master Data, Bank Master Data, Item Master, User Master Data etc. O It represents the business objects that contains agreed upon information which is shared across an organization O It is non-transactional in nature but is used in transactional documents as an information about a G/L account, Customer/Vendor or an item etc. O G/L Master data (Centrally) - Both chart of accounts level/seg...
Read more

What is a Chart of Account and how to assign to company code in SAP FICO ?

Image
Chart of accounts  A Chart of Account is assigned to a company code in SAP Configuration by specifying the chart of accounts key in the company code settings. Each company code can be assigned to only one operational chart of accounts, but one chart of accounts can be assigned to multiple company codes. O Highest level of hierarchy for all the G/L accounts O It is created by following the 3-method variant principle O Create Chart of Accounts: T-code: OB13 O Define the properties to the chart of accounts O Assign company code to the chart of accounts: T-code: OB62 Menu path: Display IMG -> Financial Accounting -> General Ledger Accounting -> Master Data -> G/L Accounts -> Preparations -> Edit Chart of Accounts List O Table: SKAI can be viewed through T-code: SE16N to display the relevant information III. Defining Chart of Accounts in SAP S/4HANA – A Step-by-Step Configuration Guide In every SAP S/4HANA implementation, the Chart of Accounts (COA) is one of the most ...
Read more

Reconciliation Accounts and G/L Master Data Creation in SAP S/4HANA – A Complete Beginner’s Guide

Image
If you are learning SAP S/4HANA Finance , understanding Reconciliation Accounts and G/L Master Data is critical. These concepts form the backbone of FI postings, sub-ledger integration, and real-time financial reporting . This blog explains everything clearly, practically, and in simple terms . 1. General Ledger in SAP S/4HANA The General Ledger (GL) is the central repository of financial data in SAP. A G/L account consists of two segments: Chart of Accounts (CoA) segment – global level Company Code segment – company-specific level Business transactions are: Recorded using the double-entry accounting principle (Debit = Credit) Classified into Assets, Liabilities, Income, and Expenses Used to generate Balance Sheet and Profit & Loss statements All transactions with business partners are first posted to sub-ledgers , and their totals are automatically updated in the General Ledger . 1. What Is a Reconciliation Account? A Reconciliation Account is a s...
Read more