SAP FICO Enterprise Structure

 Parallel Valuation involves maintaining multiple sets of accounting principles or standards (eg. IFRS and local GAAP) within separate ledgers, While Parallel Currency involves reporting financial data in multiple currencies within the same ledger. Good — now we’re getting into parallel valuation vs parallel currency . This is where interviewers check whether you really understand the dimensions of parallel accounting. Difference: Parallel Valuation vs Parallel Currency They sound similar but are completely different. 1️⃣ Parallel Valuation Parallel valuation = Different accounting principles You value the SAME transaction differently. Example: Asset purchase = ₹10,00,000 Accounting Standard Depreciation Method Indian GAAP Straight line US GAAP Accelerated IFRS Component depreciation Same asset → different valuation . This is handled using: 👉 Parallel Ledgers So: 0L → Indian GAAP valuation L1 → US GAAP valuation This is parallel valuation . 2️⃣ Parallel Currency Parallel currency ...

 A Parallel Ledger in SAP is an additional ledger that runs in parallel with the primary ledger (Leading Ledger 0L), allowing for the simultaneous recording of financial transaction according to different accounting principles or standards. Good. Now we move from what is parallel accounting → to how SAP technically supports it . This is where you move from theory to configuration understanding. This slide is reinforcing one very important default fact about SAP ledgers. Let’s lock it properly. Default Ledger in SAP SAP automatically provides: 👉 0L — Leading Ledger This exists in every SAP system. You do not create it manually. It comes pre-delivered and active. What Makes 0L Special? 0L is: Leading ledger Default active ledger Assigned to all company codes Integrated with Controlling (CO) Used for local statutory reporting Think of it as the main accounting book . What Are Parallel Ledgers Then? If business needs additional reporting (IFRS, US GAAP, Group reporting): You create...

 SAP provides functionalities such as parallel ledger, parallel currencies, valuation areas, and group valuation to facilitate Parallel Accounting. Good. Now we move from what is parallel accounting → to how SAP technically supports it . This is where you move from theory to configuration understanding. How Does SAP Support Parallel Accounting? SAP supports parallel accounting mainly through: 1️⃣ Multiple Ledgers 2️⃣ Multiple Currencies 3️⃣ Different Valuation Areas Let’s break each properly. 1️⃣ Multiple Ledgers (Primary Mechanism) This is the core method. You create: Leading Ledger (0L) → Local GAAP Non-Leading Ledger (L1, L2, etc.) → IFRS / US GAAP Each ledger can have: Different accounting principles Different fiscal year variants Different postings (ledger-specific adjustments) Example: Depreciation: Indian GAAP → Straight Line US GAAP → Accelerated Same asset → different ledger values. That’s ledger-based parallel accounting. 2️⃣ Multiple Currencies Parallel accounting is ...

Local Reporting refers to financial reporting based on local accounting standards, whereas Group Reporting involves consolidating financial data from multiple entities based on group accounting standards. Parallel Accounting encompasses both local and group reporting, allowing for the simultaneous management of multiple reporting standards. . Local vs Group Reporting — Final Clarity Local Reporting (Statutory) Financial statements prepared as per country law where the company operates. Example: Indian entity → Indian GAAP / Companies Act Required for: Tax filing Statutory audit Government compliance Audience: 👉 Government, tax authorities, local auditors Ledger: 👉 Usually Leading Ledger (0L) Group Reporting (Consolidation) Financial statements prepared for parent company / global group . Parent company wants: Same accounting rules across all subsidiaries Same reporting format Consolidated financial statements Example: Indian subsidiary reporting to US HQ using US GAAP or IFRS . Audi...

 Parallel Acconting is commonly used in scenarios such as legal reporting requirements (e.g. International Financial Reporting Standards(IFRS) and local Generally Accepted Accounting Principles(GAAP), statutory reporting for tax purposes, and management reporting for internal analysis. Good — this is a classic follow-up to parallel accounting. Difference Between Local Reporting vs Group Reporting This is about who the financial statements are for. 1️⃣ Local Reporting (Statutory Reporting) Local reporting = Financial statements prepared as per country law . Example: India company → Indian GAAP / Companies Act Germany → HGB US → US GAAP Purpose: Tax filing Statutory compliance Government reporting Local audits This is mandatory by law. In SAP: 👉 Usually maintained in Leading Ledger (0L) . 2️⃣ Group Reporting (Consolidation Reporting) Group reporting = Financial statements prepared for parent company / global group . Example: Indian subsidiary of US company must send data to HQ. HQ w...

Parallel Accounting in SAP allows companies to manage multiple sets of accounting principles or standards within the same system simultaneously. It enables organizations to report financial data according to different accounting rules or regulations. What is Parallel Accounting? Parallel accounting means: 👉 Maintaining multiple accounting principles in the same company code, in the same SAP system, simultaneously. Example: India entity must report as per Indian GAAP Parent company requires reporting as per US GAAP Group requires IFRS Instead of maintaining three separate systems, SAP allows you to maintain them in parallel. That is parallel accounting. Why Is It Required? Because accounting rules differ across: Countries Regulatory frameworks Group reporting requirements Example differences: Depreciation methods Revenue recognition Lease accounting Asset valuation Provisions Same transaction → different accounting treatment. How SAP Handles Parallel Accounting Through Ledger Concept ...

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 suc...

Yes, SAP allows customization of these variants to align with specific business needs, such as different fiscal years for different Company Codes or additional fields required for certain transaction types. Can We Customize COA, FY Variant, PP Variant, FSV? Short answer: YES. SAP gives standard templates , but real projects always customize based on business requirements. If you ever say “we just use SAP standard” in an interview → weak answer. Consultants customize. What Can Be Customized? 1️⃣ Chart of Accounts Business decides: How many charts of accounts? Group vs local COA? Industry-specific GL structure? Example: Global COA Country-specific COA Industry COA 2️⃣ Fiscal Year Variant Business decides: Jan–Dec? Apr–Mar? 4-4-5 calendar? Short fiscal year during merger? SAP supports all of this. 3️⃣ Posting Period Variant Business decides: How long previous period remains open? Which account types can post? Month-end closing rules? Example: Vendors closed early GL open longer 4️⃣ Field...

 The Fiscal year variant determines the number and duration of posting periods within a fiscal year. While the configuration of the posting period defines the open and closed periods for posting. Difference Between Fiscal Year Variant vs Posting Period Variant If you don’t answer this cleanly, interviewers assume weak fundamentals. Let’s make it bulletproof. Core Idea (One Sentence Each) Fiscal Year Variant → defines the structure of the financial year. Posting Period Variant → controls whether posting is allowed in that year. Structure vs Control. 1️⃣ Fiscal Year Variant (FYV) Answers questions like: When does the financial year start? When does it end? How many posting periods exist? How many special periods exist? Example: Apr → Mar 12 periods + 4 special periods So FYV defines the calendar framework . Think: Timeline creation. 2️⃣ Posting Period Variant (PPV) Answers questions like: Which periods are OPEN? Which periods are CLOSED? Which account types can post? Example: March o...

These variants are integrated by assigning them to the relevant organizational units (Company Codes), ensuring consistency in financial reporting , data entry, and controlling.. Core Question How are Chart of Accounts, Fiscal Year Variant, Posting Period Variant, and Field Status Variant integrated in SAP? Short answer: 👉 All of them are assigned to the Company Code . Company Code is the integration point. Step 1 — Company Code Is the Hub Company Code = Legal entity for which financial statements are prepared. Everything important in FI is linked to it. Step 2 — What Gets Assigned to Company Code? Here’s the structure: Configuration Object Assigned To Purpose Chart of Accounts Company Code Defines GL structure Fiscal Year Variant Company Code Defines financial year Posting Period Variant Company Code Controls open/close periods Field Status Variant Company Code Controls posting fields This assignment ensures consistency in: Financial reporting Period control Data entry validation Acco...

Below are the 4 field statuses. -Hidden/Suppresses(Highest Priority) - Display Only - Required/Mandatory -Optional (Lowest Priority) Field status controls through GL Level & Posting Key level Combination of Hidden (GL) & Required (Posting Key) will generate a error.. Field Status Comes From TWO Places During posting, field control comes from: 1️⃣ Posting Key 2️⃣ Field Status Group (G/L account) Both try to control the same fields. SAP must decide the final behavior → this is called Field Status Priority . Priority Order (Memorize) Highest → Lowest: 1️⃣ Suppress (Hidden) 2️⃣ Display 3️⃣ Required 4️⃣ Optional Remember shortcut: SDRO The Famous Interview Scenario ⚠️ This is exactly what your slide describes. Situation: Source Field Status Posting Key Hidden Field Status Group (GL) Required One says: Field must be filled Other says: Field must not exist So what happens? 👉 System throws ERROR . Why? Because: System says field is mandatory But system also hides the field User cannot...

Field status determines which fields must be filled in during transaction entry. It ensures data consistency and accuracy by enforcing the required fields for different types of transactions. Impact of Field Status on Transaction Entry Field status decides: Which fields user must fill Which fields user may fill Which fields user cannot see Which fields are display only Goal: 👉 Data consistency + accuracy Examples you must remember: Account Type Mandatory Field Bank GL Value date Expense GL Cost center Customer/Vendor Business area / Payment terms etc This is real project usage. Now the Important Question Field Status Priority (Very Important ⚠️) This is what the slide is hinting at. During posting, field status comes from two places : 1️⃣ Posting Key 2️⃣ Field Status Group (from GL account) Both try to control the same fields. So SAP needs a priority rule . The Golden Rule Suppress (Hidden) has the highest priority. If any configuration says “Hide this field” → it disappears. Priority...

Field Status Variant O Field status variant controls the fields of a transaction at a line item level O For example, if you want to hide, display, required entry, optional entry for a field, then you can use it through field status variant / group assigned in company code segment of a G/L master O Field status variant can be created by following the 3-step method of variant principle O It is 4-digit alphanumeric key O SAP provides pre-defined field status group which can be copied to create your own O Define field status variant: T-code: OBC4 O Menu path: Display IMG -> Financial Accounting -> Financial Accounting Global Settings -> Ledgers -> Fields -> Define Field Status Variants O If you do not maintain the field status, all fields will be hidden O Assign company code to the field status variant: T-code: OBC5 O Menu path: Display IMG -> Financial Accounting -> Financial Accounting Global Settings -> Ledgers -> Fields -> Assign Company Code to Field Stat...

Open posting periods allow transactions to be posted with in those periods, while closed posting periods prevent any further postings. This helps in maintaining data integrity and ensuring compliance with reporting timelines. Significance of Open & Closed Posting Periods This is not technical. This is financial control + governance . What Happens If Periods Are Not Controlled? Imagine this real scenario: 1️⃣ February books are closed 2️⃣ Financial statements are prepared 3️⃣ Reports sent to management/auditors Then someone posts a new February invoice. Now: Trial balance changes P&L changes Balance sheet changes Your published financial statements become wrong . This is a huge compliance failure. Why Companies Close Posting Periods Posting period control ensures: Financial statements remain stable No backdated postings after closing Month-end close discipline Audit compliance Data integrity This is core internal control . Real Company Policy Example Typical rule in companies: C...

In SAP, Special periods are additional periods that can be defined at the end of a fiscal year to accommodate specific accounting requirements such as adjustments, accruals, or corrections without affecting regular posting periods. Special Periods are typically used for year-end closing activities and adjustments. SAP allows up to 4 special periods. Special Periods — The Part Candidates Get Wrong Many people say: Special periods are for quarterly adjustments. ❌ Wrong. Special periods are ONLY for year-end adjustments. You must be clear on this. Recap First Normal posting periods = 1 to 12 (monthly periods) Special periods = 13 to 16 Maximum SAP allows = 4 special periods Critical Rule Most People Miss Special period postings can happen ONLY in the last month of the fiscal year. Example (Calendar year company): Fiscal year ends in December You can post in: Period 13 → December Period 14 → December Period 15 → December Period 16 → December You CANNOT post special periods in: March quart...

 No, each Company Code in SAP can be assigned only one posting period variant, while one posting period variant can be assigned to multiple company codes. Good — this slide contains two important interview questions mixed together: Can a company code have multiple Posting Period Variants? 1️⃣ Can a Company Code Have Multiple Posting Period Variants? Rule is EXACTLY same pattern as Fiscal Year Variant. Memorize this. 👉 One company code → only ONE Posting Period Variant 👉 One Posting Period Variant → can be assigned to multiple company codes Why? Because the company code must follow one period opening/closing rule . You cannot have one entity where: Half users post in March Half users post in January That would break financial control. Interview Answer Version If asked: Can a company code have multiple posting period variants? Answer: No. A company code can be assigned only one posting period variant, but a posting period variant can be shared by multiple company codes. This is a ...

A Posting Period Variant controls which periods can be open for posting in a Company Code. First — What is a Posting Period? A posting period = the month in which financial transactions are allowed to be posted. Simple rule in SAP: 👉 You can post only in open periods 👉 You cannot post in closed periods This protects financial data. Why This Control Is Needed (Real Finance Reason) Imagine chaos if this didn’t exist: Today is March 2026 User posts invoice in Jan 2024 Financial statements already audited 😑 Financial reporting would collapse. So SAP enforces period control . What Controls Posting Periods? 👉 Posting Period Variant (PPV) This tells SAP: Which periods are open Which periods are closed For which account types This is configured via OB52 (very famous T-code). Key Concept Flow (Memorize This Chain) Configuration sequence: 1️⃣ Create Posting Period Variant 2️⃣ Assign Posting Period Variant to Company Code 3️⃣ Open/Close periods in OB52 This flow is frequently asked. What Exa...

A shortened fiscal year refers to a fiscal year that does not align with the standard twelve-month period. Instead, it covers a period shorter than twelve months. This might occur due to various reasons such as a change in reporting requirements, legal regulations, or corporate restructuring. Example: Let's say a company typically operates on a standard fiscal year from January 1st to December 31st. However, due to a merger with another company, they decide to change their fiscal year to align with the new parent company's fiscal year, which runs from April 1st to March 31st. What is a Shortened Fiscal Year? Normally: A fiscal year = 12 months If a fiscal year has less than 12 months , it is called a Shortened Fiscal Year . That’s the whole definition. But the real value is understanding why it happens. Why Shortened Fiscal Year Exists (Real Business Scenario) It happens when a company changes its fiscal year . Example: Company currently follows: Jan → Dec But after merger with...

The standard Fiscal Year Variants include: K4(calendar year), V3(fiscal year variant with 4 special periods), and V6 (fiscal year variant with 12 posting periods).. SAP Standard Fiscal Year Variants SAP gives some FY variants pre-delivered so you don’t always create from scratch. The two most important ones: Variant Period Type K4 Jan → Dec Calendar year V3 Apr → Mar Non-calendar year These two are asked in interviews very frequently . 1️⃣ K4 – Calendar Year Variant K4 = Jan → Dec Characteristics: Year-independent 12 normal posting periods 4 special periods Used in US, Europe, many global companies This is the default SAP fiscal year. If you create a new system, K4 already exists. 2️⃣ V3 – April to March Variant V3 = Apr → Mar Characteristics: Year-independent 12 posting periods 4 special periods Commonly used in India This is why trainers always mention V3. Why Interviewers Ask This They want to check whether you know: SAP provides standard content Consultants don’t always configure e...

In a year-independent fiscal year, the fiscal year is fixed and remains the same every year. The start and end dates of the fiscal year & number of periods do not change from year to year. In a year-dependent fiscal year, the fiscal year can vary from year to year based on specific criteria. The start and end dates of the fiscal year or number of period can change dynamically, depending on organizational requirements or business cycles. Year-Independent Fiscal Year Variant (Deep Version) Definition is not just “same every year”. There are two strict conditions . A fiscal year is year-independent only if BOTH stay constant: 1️⃣ Start and end date remain same every year 2️⃣ Number of posting periods remain same every year Example: Apr → Mar with 12 periods + 4 special periods. Year Start End Periods 2023 01.04.2023 31.03.2024 12 + 4 2024 01.04.2024 31.03.2025 12 + 4 2025 01.04.2025 31.03.2026 12 + 4 Nothing changes except the year number. SAP automatically generates future years. Th...

 Yes, A Fiscal year variant can be shared among multiple Company Codes in SAP, allowing for consistency in reporting across different organizational units. This slide is basically repeating and reinforcing the same point. Nothing new technically — but interviewers still ask this, so we tighten your understanding. The One Idea This Slide Is Hammering Fiscal Year Variant can be shared across multiple company codes. That’s the whole message. Let’s make it crystal clear and interview-ready. Why SAP Allows Sharing FY Variant In real companies, many legal entities follow the same financial year. Example: A group has 10 Indian subsidiaries. All must follow Apr → Mar (Indian law). If SAP forced you to create 10 fiscal year variants: Maintenance nightmare Higher risk of errors Inconsistent reporting So SAP allows reuse. How It Works Practically You create one fiscal year variant : Example: Variant: V3 Period: Apr → Mar Then assign V3 to multiple company codes: Company Code Fiscal Year Vari...

While a Calendar Year follows the traditional January 1st to December 31st period. A Fiscal Year Variant allows organizations to define their financial year differently to align with business cycles or regulatory requirements. Example April to March.. Core Question How is Fiscal Year different from Calendar Year? The screenshot explanation is correct but too basic. We need to make it professional. Step 1 — Calendar Year (Simple) Calendar year is fixed: Jan → Dec (12 months) It never changes. Used for: Personal taxation Global reference timeline Some countries’ statutory reporting (US, many EU countries) You cannot configure calendar year. It’s universal. Step 2 — Fiscal Year (Business Concept) Fiscal year = Financial reporting period defined by a company/government. It can start in any month . Examples: Country Fiscal Year India Apr → Mar USA Jan → Dec Australia Jul → Jun UK Govt Apr → Mar Why? Because businesses don’t always align with Jan–Dec cycles. Step 3 — Why Companies Don’t Alw...

No, each Company Code in SAP can be assigned only one Fiscal Year Variant. If required to report in multiple fiscal year variants for different accounting principles, we need to create multiple ledgers with different Fiscal Year Variant. The Big Question in the Screenshot Can one company code follow two fiscal years? Example: Statutory reporting in India → Apr–Mar Group reporting (US parent) → Jan–Dec Can the same company code produce both? At first glance → NO. And this is where beginners stop thinking. Consultants must go deeper. Step 1 — The Basic Rule (Still True) A company code can have only ONE fiscal year variant . So normally: Indian company code → Apr–Mar only You cannot assign Jan–Dec also. So how do multinational companies survive? Because they must report in multiple calendars. Step 2 — The Real Business Problem Imagine: Indian subsidiary of a US company. Requirement Fiscal Year Statutory (India law) Apr → Mar Group reporting (US parent) Jan → Dec IFRS reporting Jan → Dec ...

A Fiscal Year Variant is assigned to a Company Code in SAP through transaction code OB37 . We can assign same fiscal year variant to multiple company codes. Step 2 — What is Fiscal Year Variant? Fiscal Year Variant defines: Financial year start & end Number of posting periods (usually 12) Special periods (usually 4) Example: India companies → April to March US/EU companies → Jan to Dec Step 3 — The Key Rule (Interview Question ⚠️) One Fiscal Year Variant can be assigned to multiple company codes. But… One Company Code can have only ONE Fiscal Year Variant. This is a classic exam/interview trap. Step 4 — What the Screenshot Scenario Means They gave an enterprise example: You have 10 company codes . Split like this: Country Company Codes Fiscal Year India 7 company codes Apr → Mar Other countries 3 company codes Jan → Dec Now think like a consultant: Would you create 10 fiscal year variants? That would be stupid and unnecessary. Instead: You create only TWO fiscal year variants. Fisc...

A Fiscal Year Variant defines the organization's financial year, specifying the start and end dates of the fiscal year and the number of posting periods within it.  This slide is explaining Fiscal Year Variant (the text says “Financial year”, but it actually means Fiscal Year in SAP). This is another very common interview question . Fiscal Year Variant in SAP Simple Meaning A Fiscal Year Variant (FYV) defines the financial year structure for a company in SAP. It tells SAP: When the financial year starts When it ends How many posting periods exist Why Fiscal Year Is Needed Different countries follow different financial years. Examples: India → April to March USA → January to December Australia → July to June SAP must know which financial calendar your company follows. That is why we configure Fiscal Year Variant and assign it to the Company Code . Example If company follows Indian financial year: Financial Year 2024 = 📅 01-Apr-2024 → 31-Mar-2025 SAP needs this to: Post transac...