The fiscal year variant is a fundamental setting in SAP Financial Accounting that defines the structure of the fiscal year for a company code. Its primary functions are to specify the total number of posting periods (both normal and special periods for closing) and to determine the start and end dates for each of these periods. For example, a standard calendar year variant would have 12 normal posting periods and 4 special periods, with each normal period's start and end date corresponding to a calendar month.

B. The authorization to post to special periods: Authorization is controlled by user roles and specific authorization objects (e.g., FBKPFBUP), not by the fiscal year variant itself.

D. The posting periods open for posting: This is controlled by the Posting Period Variant (PPV) and its associated rules (transaction OB52), which is a separate configuration object from the Fiscal Year Variant (FYV).

1. SAP S/4HANA Documentation - SAP Help Portal: In the implementation guide for S/4HANA

the activity "Define Fiscal Year Variant" states: "A fiscal year variant contains the number of posting periods and special periods

and it determines how the system is to determine the posting periods... For each posting period

you must define the last day of the period." This directly supports that the variant defines the number of periods (C) and their start/end dates (A).

Source: SAP Help Portal

SAP S/4HANA

Implementation Guide for SAP S/4HANA -> Financial Accounting -> Financial Accounting Global Settings -> Ledgers -> Fiscal Year and Posting Periods -> Maintain Fiscal Year Variant.

2. SAP Press (Official Vendor Publication): In "Configuring Financial Accounting in SAP S/4HANA" by Stoil Jotev

Chapter 3

Section 3.3.1 states: "The fiscal year variant defines the number of posting periods (normal and special) in a fiscal year. For each posting period

you also define its start and end dates." This explicitly confirms options A and C.

Source: Jotev

S. (2021). Configuring Financial Accounting in SAP S/4HANA. SAP Press. Chapter 3

Section 3.3.1

"Fiscal Year Variant"

p. 89.

3. SAP Training Courseware (Official Vendor Documentation): The official SAP training course TS4F01

"Financial Accounting in SAP S/4HANA

" explains in Unit 2

"General Ledger Accounting

" that the fiscal year variant defines the number of periods and their boundaries. It explicitly distinguishes this from the posting period variant

which controls the opening and closing of these periods.

Source: SAP Training Course TS4F01

Financial Accounting in SAP S/4HANA

Unit 2

Lesson: "Organizational Units in Financial Accounting".

Transaction AS91 (Create Old Asset) is used during legacy data migration in Asset Accounting to enter and post historical acquisition and accumulated depreciation amounts—so-called “take-over values.” When the legacy transfer date is reached, these values are automatically posted to the G/L, bringing the asset balances in SAP in line with the previous system. AS91 is not used to set company-code transfer status, to post summary write-offs, or to create normal (new) asset master data records; it is reserved for importing legacy balances.

A. Company-code transfer status is set in Customizing (transaction OAYC), not with AS91.

B. Summary write-offs are recorded with specific FI postings, not via AS91.

C. Standard asset master data is created with AS01; AS91 is intended for legacy balance entry, not ordinary master-data creation.

1. SAP S/4HANA 2022 Help Portal

Financial Accounting → Asset Accounting → Legacy Data Transfer → “Create Old Asset (Transaction AS91)” – paras. 1-2.

2. SAP Press

Stoilov & Bell

“Asset Accounting in SAP S/4HANA

” 2nd ed.

2023

Chap. 6.1.2

pp. 236-238.

3. SAP University Alliances Course FIN300

Unit 9 “Legacy Asset Migration

” Slide 12: “AS91 – enter take-over values; postings generated on transfer date.”

To manually post a general journal entry to a specific standard ledger (particularly a non-leading ledger), the ledger must be part of a ledger group. In SAP S/4HANA, manual posting transactions (like the Fiori app 'Post General Journal Entries') require specifying a ledger group to direct the posting to the intended ledger(s). When a new standard ledger is created, the system automatically generates a corresponding ledger group with the same name containing only that ledger. This mechanism is essential for enabling targeted manual postings.

A. Assign the ledger to a company code

This is a mandatory prerequisite for any postings within a company code, not an action specific to enabling manual, targeted journal entries.

B. Assign a chart of accounts to the ledger

A chart of accounts is assigned at the company code level, not directly to a ledger. The ledger inherits the chart of accounts from the company code.

C. Define the underlying ledger

The concept of an underlying ledger applies only to extension ledgers, not to standard ledgers as specified in the question.

1. SAP S/4HANA 2023 Product Assistance

Finance -> General Ledger Accounting (G/L) -> Ledgers -> Ledger Groups: "To post a document to one or more specific ledgers

you enter the relevant ledger group in the header of the posting document... When you create a ledger

the system automatically creates a ledger group with the same name." This section confirms that ledger groups are the mechanism for manual

targeted postings.

2. SAP S/4HANA 2023 Product Assistance

Finance -> General Ledger Accounting (G/L) -> Ledgers -> Settings for Ledgers: "You need to assign your ledgers to your company codes... This is a prerequisite for being able to post to the ledgers in these company codes." This supports that option A is a general prerequisite

not the specific action for manual posting.

3. SAP S/4HANA 2023 Product Assistance

Finance -> Organizational Structure -> Chart of Accounts: "You must assign a chart of accounts to each company code." This documentation clarifies that the Chart of Accounts is assigned to the company code

making option B incorrect.

4. SAP S/4HANA 2023 Product Assistance

Finance -> General Ledger Accounting (G/L) -> Ledgers -> Extension Ledgers: "An extension ledger must always have an underlying ledger." This statement confirms that the concept of an underlying ledger is exclusive to extension ledgers

invalidating option C for standard ledgers.

The leading ledger (0L) functions as the primary and definitive record for all financial transactions in an SAP S/4HANA system. All integrated postings from other modules (like Sales, Procurement, etc.) are posted to the leading ledger by default. While non-leading ledgers can have their values derived from the leading ledger to represent parallel accounting principles, the leading ledger itself is the ultimate source of truth. It does not derive its values from any other ledger. This functional role as the non-derivative, primary source of data is a core principle that fundamentally separates it from other parallel standard ledgers.

A. It is used for performing segment reporting.

Segment reporting is a capability enabled by document splitting, which can be configured for and utilized with any standard ledger, not just the leading one.

C. It is used to represent the group valuation.

This describes the most common business use case for the leading ledger, but it is a configurable choice (assignment of an accounting principle), not an inherent technical characteristic.

D. It is assigned to all company codes.

While factually correct and a key feature, this can be a less precise separator in a system with only one company code, where any active non-leading ledger would also be assigned to all existing company codes.

1. SAP Help Portal

SAP S/4HANA

"Ledgers": The documentation outlines that all data is posted to the leading ledger

which serves as the basis for valuations. It states

"The leading ledger contains the complete set of line items." This establishes its role as the primary

complete data source from which other views can be derived. (Refer to SAP S/4HANA -> Finance -> General Ledger Accounting (G/L) -> Ledgers).

2. SAP Learning Hub

Course TS4F01

"Financial Accounting in SAP S/4HANA": Unit 3

"General Ledger Accounting

" explains the concept of parallel ledgers. It details how postings are made to the leading ledger and how non-leading ledgers are used for adjustments or alternative valuations

reinforcing the idea that the leading ledger is the baseline and does not derive its values from these parallel ledgers.

3. Stobbe

J.

et al. (2022). Financial Accounting with SAP S/4HANA: Business User Guide. SAP PRESS. In Chapter 2

Section 2.3.1

"Ledgers and Parallel Accounting

" the text clarifies

"All business transactions are always posted to the leading ledger." This confirms its status as the primary recipient of postings

not a ledger that derives data from others.

For consolidation purposes within SAP S/4HANA, every legal entity that is part of the corporate group must be represented as a consolidation unit. This is true regardless of whether the entity is managed as a company code within the SAP S/4HANA system or on an external legacy system.

In this scenario, the corporate group consists of 15 legal entities. To perform a complete consolidation, you must define a corresponding "Company" (in classic terminology) or "Consolidation Unit" (in S/4HANA Group Reporting) for each of the 15 entities. This allows the system to process financial data from both the 10 internal company codes and the 5 external entities to produce a single, consolidated financial report.

A. 1: Defining a single company would incorrectly aggregate all entities, making it impossible to perform necessary intercompany eliminations and produce accurate consolidated statements.

B. 5: This number only represents the external entities on legacy systems. The 10 entities managed within SAP S/4HANA must also be defined as companies for consolidation.

D. 10: This number only accounts for the entities already existing as company codes in SAP S/4HANA, incorrectly excluding the 5 external entities from the consolidation scope.

1. SAP S/4HANA Help Portal

"Consolidation Units": In the context of SAP S/4HANA Group Reporting

the documentation states: "A consolidation unit represents an operational unit of a corporate group that must be included in the consolidation process... You can create consolidation units for company codes of your SAP S/4HANA system and for companies that are not integrated in your system." This confirms that all 15 entities (10 integrated

5 non-integrated) must be created as consolidation units. (Accessed under SAP S/4HANA 2023 -> Product Assistance -> English -> Enterprise Business Applications -> Finance -> Accounting and Financial Close -> Group Reporting -> Master Data for Group Reporting -> Consolidation Units).

2. SAP S/4HANA Help Portal

"Organizational Unit Company": In classic Financial Accounting

the "Company" is used for consolidation. The documentation explains that company codes are assigned to a company. For entities outside the system

a company master record is still created to represent them in the consolidation structure

enabling the collection of their financial data for the group report. (Accessed under SAP S/4HANA 2023 -> Product Assistance -> English -> Enterprise Business Applications -> Finance -> General Ledger Accounting (G/L) -> Master Data -> G/L Accounts -> Company Code-Specific Master Data Settings).

The technical clearing account for integrated asset acquisitions is a fundamental concept in SAP S/4HANA Asset Accounting. It ensures real-time reconciliation between the general ledger and the asset subledger during integrated transactions. The system splits the business transaction into an operational part (e.g., goods/invoice receipt) and a valuating part (the asset capitalization). The technical clearing account is posted in both parts, with a net zero balance upon completion. This mechanism is used specifically for acquisitions that originate from other SAP modules, such as Materials Management (MM) or Controlling (CO), ensuring data consistency across ledgers throughout the process.

B. Asset transfer posting between asset classes: This is a purely internal FI-AA transaction (e.g., ABUMN) and does not involve integration with external modules, hence the technical clearing account is not used.

C. Direct asset acquisition posting with a vendor invoice (not linked to a purchase order): This is a non-integrated acquisition posted directly in FI (e.g., F-90). The posting is a single-step transaction and does not require the split logic of the technical clearing account.

1. Official SAP S/4HANA Documentation:

Source: SAP Help Portal

SAP S/4HANA 2023

Finance > Accounting and Financial Close > Asset Accounting (FI-AA) > Postings > Integrated Asset Acquisition Posting.

Reference: The documentation explicitly states: "For an integrated asset acquisition posting

the system divides the business transaction into an operational part and a valuating part... In the operational part of the document

the system posts against the technical clearing account for integrated asset acquisitions." It lists "Acquisition with a purchase order" (Option A) and "Settlement of an internal order or WBS element to an asset" (related to Option D) as primary examples.

2. SAP Learning Hub Courseware (CTS4FI2023 preparation):

Source: S4F13 - Asset Accounting in SAP S/4HANA.

Reference: Unit 3: Acquisitions

Lesson: "Integrated Asset Acquisitions." This lesson details the posting logic for integrated scenarios. It confirms that the technical clearing account is used for goods receipts against purchase orders with asset account assignment and for the settlement of investment measures (like investment orders) to assets

including Assets under Construction (AuC).

3. SAP Press Publication:

Source: Jotev

S. (2020). Asset Accounting with SAP S/4HANA. Rheinwerk Publishing.

Reference: Chapter 4

Section 4.1.2

"Integrated Asset Acquisition." This section explains that the technical clearing account is exclusively used for integrated processes to decouple the operational event (like a goods receipt) from the asset valuation. It provides detailed examples for both the MM-FI-AA integration (procurement) and the CO-FI-AA integration (settlement of investment measures).

SAP S/4HANA provides several standard procedures for conducting physical inventory to meet both legal requirements and internal controlling needs. The three primary methods available are:

1. Periodic Inventory: This is the traditional annual physical inventory where all stocks in the warehouse are physically counted on a specific key date.

2. Continuous Inventory: This method allows for the counting of stocks continuously throughout the fiscal year, distributing the workload and avoiding a complete shutdown for an annual count.

3. Cycle Counting: A specific type of continuous inventory where materials are counted at regular, predefined intervals. The frequency is often determined by an ABC analysis, with high-value (A) items counted more frequently than low-value (C) items.

A. Actual inventory method: This is a general accounting term, not a specific, named physical inventory procedure within the SAP S/4HANA standard system.

D. Standard inventory method: This is a generic phrase. While the available methods are 'standard' SAP functionalities, this is not the official name of any specific procedure.

1. SAP Help Portal

SAP S/4HANA 2023

"Physical Inventory Procedures": This official documentation outlines the main methods. It states

"The following physical inventory procedures are supported: Periodic inventory

Continuous inventory

Cycle counting

Inventory sampling." This directly supports the correctness of options B

C

and E.

2. SAP Help Portal

SAP S/4HANA 2023

"Cycle Counting": This section provides a detailed description of the cycle counting method

confirming it as a distinct procedure. It explains

"Cycle counting is a method of physical inventory whereby inventory is counted at regular intervals within a fiscal year."

3. SAP Help Portal

SAP S/4HANA 2023

"Periodic Inventory": This document details the annual physical inventory count (Stichtagsinventur)

which corresponds to the periodic method. It describes the process of counting the total valuated stock of a material on the balance sheet key date.

In SAP S/4HANA, New Asset Accounting is fundamentally integrated with the Universal Journal (table ACDOCA). A core design principle is that all depreciation areas relevant for financial reporting, including those for parallel currencies linked to non-leading ledgers, must post in real time. This ensures data consistency across all valuations and eliminates the need for periodic reconciliation postings that were common in SAP ERP. Both Asset Acquisition and Production Cost (APC) transactions and depreciation expenses are posted simultaneously to the respective ledgers, providing a real-time financial view.

A. Does not post to G/L: This setting is used for statistical or information-only depreciation areas, not for areas required for parallel currency reporting.

C. Posts to G/L periodically: This describes the obsolete posting logic from classic Asset Accounting in SAP ERP, which has been replaced by real-time posting in S/4HANA.

D. Posts APC real time and depreciation periodically: This is the behavior of a "delta depreciation area" in SAP ERP, a concept that is no longer used in S/4HANA's real-time posting architecture.

1. SAP Help Portal for S/4HANA 2023

Asset Accounting (FI-AA)

"Posting in General Ledger": "In new Asset Accounting

the posting logic has been completely redesigned. All postings for a valuation area (for both the leading valuation and for parallel valuations) are now made in real time. The system posts the documents directly to the G/L; a separate posting run is no longer necessary."

2. SAP Note 2270388 - "FAQ: New Asset Accounting in S/4HANA": This note clarifies the architectural changes. In section 2

"Postings"

it states: "In new Asset Accounting

all depreciation areas post to the general ledger in real time. The periodic posting run (RAPERB2000) is no longer available." This confirms that periodic posting is obsolete for parallel currency areas.

3. SAP S/4HANA 2023 Documentation

"Parallel Valuation in Asset Accounting": The documentation on setting up parallel currencies and ledgers specifies that each accounting principle (and its associated ledger group) requires a corresponding depreciation area that posts its values in real time to ensure consistent and immediate reporting.

In SAP S/4HANA, a guarantee is a contingent liability. It is recorded using a Special G/L transaction classified as a statistical posting. The standard procedure for posting a guarantee creates a document with two line items: a debit to a statistical account for guarantees and a credit to a corresponding statistical offsetting account. These line items do not affect the G/L trial balance but are visible in the customer's account line item display and are used for tracking and reporting contingent liabilities. This ensures the document is balanced from a technical standpoint while remaining purely statistical.

A. One statistical line item: The standard posting for a guarantee requires an offsetting entry to create a technically balanced document, resulting in two line items, not one.

B. Two noted items: A "noted item" is the classification for this type of statistical transaction, not the resulting line items. A single transaction is posted, which generates line items.

C. One noted item: While a guarantee is a type of noted item, this term often refers to single-line entries like down payment requests. Guarantees typically generate two lines to include an offsetting entry.

1. SAP S/4HANA Documentation

SAP Help Portal:

Document: Special G/L Transactions

Reference: In the section describing different types of Special G/L transactions

it is explained that certain statistical postings

such as guarantees

are posted with an automatic offsetting entry. This process generates a document with two statistical line items that do not update the G/L account balances but are noted on the customer or vendor account. This contrasts with single-entry noted items like down payment requests. (Accessed under Financial Accounting -> Accounts Receivable and Accounts Payable -> Special G/L Transactions).

2. SAP Training Courseware:

Document: TS4F01 - Financial Accounting in SAP S/4HANA

Reference: Unit 4: Accounts Payable & Accounts Receivable

Lesson: Special G/L Transactions. The course material distinguishes between "Noted Items" (e.g.

down payment requests

which create a single line item) and other "Statistical Postings" (e.g.

guarantees)

which are posted with an offsetting entry

thus creating two line items.

3. SAP Press Publication (reflects official methodology):

Book: Financial Accounting with SAP S/4HANA: Business User Guide (2nd Edition) by Jonas Tritschler

et al.

Reference: Chapter 5

Section 5.5.2 "Statistical Postings". The text explicitly states: "For guarantees that you’ve granted to a customer

you post a statistical document with two line items: a debit to a statistical account for guarantees and a credit to a statistical offsetting account." This confirms the creation of two statistical line items for a guarantee.

In SAP S/4HANA, the valuation area is the central configuration object that links the foreign currency valuation process to a specific accounting principle. When you define a valuation area, you must assign it to an accounting principle (e.g., IFRS, GAAP). This assignment ensures that the valuation run posts the exchange rate differences to the correct ledger(s) associated with that accounting principle, thereby enabling parallel accounting and reporting according to different standards. The valuation method, which dictates the specific valuation rules, is subsequently assigned within the valuation area's settings.

A. Via the valuation type: This is used in Materials Management (MM) for the split valuation of materials, not for foreign currency valuation in Financial Accounting (FI).

C. Via the valuation class: This is an MM concept used to group materials for automatic G/L account determination during goods movements.

D. Via the valuation method: The valuation method defines how to valuate (e.g., lowest value principle), but it is the valuation area that provides the direct link to the accounting principle.

1. SAP S/4HANA Help Portal: Configuration for Foreign Currency Valuation. The documentation outlines the configuration steps

stating: "In the Define Valuation Areas step

you define your valuation areas. [...] In the Assign Valuation Areas and Accounting Principles step

you assign an accounting principle to each of your valuation areas." This directly confirms the link between the valuation area and the accounting principle. (Accessed under SAP S/4HANA 2023 -> Finance -> General Ledger Accounting (FI-GL) -> Periodic Processing -> Foreign Currency Valuation).

2. SAP S/4HANA Finance: An Introduction (3rd Edition) by J. Wood

et al.: Chapter 4

"General Ledger Accounting

" details the configuration for parallel accounting. It explains that for processes like foreign currency valuation

the valuation area is created and then explicitly assigned to an accounting principle to direct postings to the correct ledgers. (Refer to sections on configuring foreign currency valuation).

3. SAP Learning Hub Courseware (TS4F02 - Financial Accounting in SAP S/4HANA): Unit 6

"Closing Operations in General Ledger Accounting

" Lesson: "Configure Foreign Currency Valuation." The course material demonstrates the configuration path in the IMG (Implementation Guide) where the valuation area is defined first and then assigned to an accounting principle. This assignment is presented as the critical step for determining which accounting standard the valuation applies to.