Scenario practice questions

Refer to the exhibit. You are reviewing the configuration of an extension ledger. Which of the following is a capability of this ledger type in S/4HANA?

Exhibit

JSON: { 'valuation_method': 'FIFO', 'parallel_valuation': true, 'ledger_type': 'Extension', 'currency_type': '10' }

Trap 1: It can store all raw data from the source ledger.

Extension ledgers only store the delta (the difference) between the base ledger and the desired valuation. They do not duplicate the source ledger's data. This design is specifically intended to optimize database size and performance, making it an efficient choice for managing specific accounting adjustments without full data redundancy.

Trap 2: It requires a separate fiscal year variant.

An extension ledger must share the same fiscal year variant as its underlying base ledger. This dependency ensures that the financial periods are aligned across both ledgers, preventing timing differences that would otherwise make reporting and reconciliation impossible between the extension and the base ledger data sets.

Trap 3: It supports physical inventory valuation postings.

Physical inventory valuation typically requires full ledger integration to update material stocks and values. Extension ledgers are intended for financial adjustments and are not suitable for inventory management processes that require tight integration with the Materials Management module and real-time updates to stock master data and quantities.

A
It can store all raw data from the source ledger.
Why it fails: Extension ledgers only store the delta (the difference) between the base ledger and the desired valuation. They do not duplicate the source ledger's data. This design is specifically intended to optimize database size and performance, making it an efficient choice for managing specific accounting adjustments without full data redundancy.
B
It can be used to store manual valuation adjustments.
Extension ledgers are designed for adjustments that should not affect the base ledger. By storing these entries separately, companies can easily report on the adjusted values while maintaining the original, unadjusted base values, which is essential for audit compliance and local vs. global reporting requirements in modern finance.
C
It requires a separate fiscal year variant.
Why it fails: An extension ledger must share the same fiscal year variant as its underlying base ledger. This dependency ensures that the financial periods are aligned across both ledgers, preventing timing differences that would otherwise make reporting and reconciliation impossible between the extension and the base ledger data sets.
D
It supports physical inventory valuation postings.
Why it fails: Physical inventory valuation typically requires full ledger integration to update material stocks and values. Extension ledgers are intended for financial adjustments and are not suitable for inventory management processes that require tight integration with the Materials Management module and real-time updates to stock master data and quantities.

Question 2hardmultiple choice

A financial accountant is executing the foreign currency valuation run in SAP S/4HANA Financial Accounting. The run is configured to use the 'Always Valuate' indicator for a specific G/L account. After the run, the accountant notices that the valuation difference was posted even though the exchange rate did not change from the previous valuation. What is the effect of the 'Always Valuate' indicator in the valuation run?

Trap 1: It reverses previous valuation postings before revaluing.

The 'Always Valuate' indicator does not automatically reverse previous postings. Reversal of previous valuation postings is controlled by separate settings in the valuation run, such as the 'Reverse Postings' indicator. The 'Always Valuate' indicator only forces valuation when the rate is unchanged, but it does not handle reversal.

Trap 2: It only valuates accounts with a changed exchange rate.

This describes the default behavior without the 'Always Valuate' indicator. By default, the system only valuates accounts if the exchange rate has changed. The 'Always Valuate' indicator overrides this default and forces valuation even when the rate is unchanged, which is the opposite of what this option states.

Trap 3: It skips valuation for accounts with no balance.

The 'Always Valuate' indicator does not affect whether accounts with zero balances are valuated. It controls whether valuation occurs when the exchange rate has not changed. Accounts with no balance are typically not valuated regardless of this indicator, as there is no amount to revalue.

A
It reverses previous valuation postings before revaluing.
Why it fails: The 'Always Valuate' indicator does not automatically reverse previous postings. Reversal of previous valuation postings is controlled by separate settings in the valuation run, such as the 'Reverse Postings' indicator. The 'Always Valuate' indicator only forces valuation when the rate is unchanged, but it does not handle reversal.
B
It forces valuation regardless of whether the exchange rate has changed.
The 'Always Valuate' indicator ensures that the system performs valuation for the selected accounts even if the exchange rate has not changed since the last valuation. This is useful for accounts where you want to revalue based on a new rate or when you need to reverse and re-post valuation differences. In this scenario, the indicator caused the valuation difference to be posted despite no rate change.
C
It only valuates accounts with a changed exchange rate.
Why it fails: This describes the default behavior without the 'Always Valuate' indicator. By default, the system only valuates accounts if the exchange rate has changed. The 'Always Valuate' indicator overrides this default and forces valuation even when the rate is unchanged, which is the opposite of what this option states.
D
It skips valuation for accounts with no balance.
Why it fails: The 'Always Valuate' indicator does not affect whether accounts with zero balances are valuated. It controls whether valuation occurs when the exchange rate has not changed. Accounts with no balance are typically not valuated regardless of this indicator, as there is no amount to revalue.

Question 3easymultiple choice

Which of the following scenarios best represents the use of 'Special General Ledger' indicators?

Trap 1: Processing regular vendor invoice payments.

Regular invoice payments are standard transactions and do not require special G/L indicators. These use the standard reconciliation account for accounts payable. Special G/L indicators are reserved for non-standard transactions that need to be separated from the primary invoice postings for specific accounting or balance sheet reporting purposes.

Trap 2: Managing fixed asset depreciation runs.

Asset depreciation is an automated process within the Asset Accounting module and is not related to special G/L indicators. It uses specific asset accounts and depreciation keys to record the value consumption of fixed assets, a process entirely separate from sub-ledger transaction classification for vendors or customers.

Trap 3: Creating new business partner master records.

Creating master records is an administrative task handled by the BP transaction and is not related to posting transactions or financial reporting indicators. Special G/L indicators are strictly for transaction-level classification and have no role in the creation or maintenance of master data entities within the SAP system.

A
Processing regular vendor invoice payments.
Why it fails: Regular invoice payments are standard transactions and do not require special G/L indicators. These use the standard reconciliation account for accounts payable. Special G/L indicators are reserved for non-standard transactions that need to be separated from the primary invoice postings for specific accounting or balance sheet reporting purposes.
B
Recording down payments to vendors.
Down payments are a classic use case for special G/L indicators. They must be tracked separately from regular vendor payables on the balance sheet for auditing and reporting. The special indicator ensures that the amount is correctly posted to a specific down payment G/L account instead of the standard account.
C
Managing fixed asset depreciation runs.
Why it fails: Asset depreciation is an automated process within the Asset Accounting module and is not related to special G/L indicators. It uses specific asset accounts and depreciation keys to record the value consumption of fixed assets, a process entirely separate from sub-ledger transaction classification for vendors or customers.
D
Creating new business partner master records.
Why it fails: Creating master records is an administrative task handled by the BP transaction and is not related to posting transactions or financial reporting indicators. Special G/L indicators are strictly for transaction-level classification and have no role in the creation or maintenance of master data entities within the SAP system.

Question 4easymultiple choice

A financial accountant is configuring the payment terms for a new vendor in SAP S/4HANA. The vendor should receive a 2% discount if the invoice is paid within 10 days, otherwise the full amount is due within 30 days. Which configuration object is used to define these payment terms?

Trap 1: Dunning procedure

A dunning procedure is used for accounts receivable to remind customers of overdue payments. It defines the dunning levels, charges, and intervals. Dunning procedures are not used for vendor payment terms. They are relevant for customer collections, not for defining discounts or payment due dates for vendors. Therefore, dunning procedures are not the correct object for this scenario.

Trap 2: House bank

A house bank represents the company's own bank accounts used for outgoing and incoming payments. It is configured in Bank Accounting and linked to payment methods. House banks do not define payment terms or discount conditions. They are used to specify the bank account from which payments are made or to which they are received. Therefore, house banks are not the correct object for configuring payment terms.

Trap 3: Payment method

Payment methods define how payments are made, such as check, bank transfer, or direct debit. They are used in automatic payment programs to determine the payment medium. Payment methods do not define discount terms or due dates. They are separate from payment terms and are assigned to vendor master records in addition to payment terms. Therefore, payment methods are not the correct object for defining discount and due date conditions.

A
Payment terms
Payment terms define the conditions under which a customer or vendor must pay an invoice, including discount percentages and due dates. They are configured in Customizing and assigned to vendor master records. The payment terms specify the cash discount period, discount percentage, and net payment period. Therefore, payment terms are the correct object to configure the 2% discount within 10 days and net due in 30 days.
B
Dunning procedure
Why it fails: A dunning procedure is used for accounts receivable to remind customers of overdue payments. It defines the dunning levels, charges, and intervals. Dunning procedures are not used for vendor payment terms. They are relevant for customer collections, not for defining discounts or payment due dates for vendors. Therefore, dunning procedures are not the correct object for this scenario.
C
House bank
Why it fails: A house bank represents the company's own bank accounts used for outgoing and incoming payments. It is configured in Bank Accounting and linked to payment methods. House banks do not define payment terms or discount conditions. They are used to specify the bank account from which payments are made or to which they are received. Therefore, house banks are not the correct object for configuring payment terms.
D
Payment method
Why it fails: Payment methods define how payments are made, such as check, bank transfer, or direct debit. They are used in automatic payment programs to determine the payment medium. Payment methods do not define discount terms or due dates. They are separate from payment terms and are assigned to vendor master records in addition to payment terms. Therefore, payment methods are not the correct object for defining discount and due date conditions.

Question 5mediummultiple choice

A financial accountant at a company using SAP S/4HANA needs to post a vendor invoice that includes a withholding tax amount. The company has activated extended withholding tax. The accountant creates the invoice with transaction code MIRO and expects the system to automatically calculate and post the withholding tax. However, upon simulation, no withholding tax is calculated. Which of the following is the most likely reason for this behavior?

Trap 1: The withholding tax code is not maintained in the company code's…

Payment terms determine due dates and cash discount periods; they do not control withholding tax calculation. Withholding tax codes are assigned to vendors, not to payment terms. Configuring payment terms with withholding tax codes is not a standard practice and would not resolve the issue. Therefore, this option is incorrect.

Trap 2: The invoice item does not have a tax code assigned, so the system…

In extended withholding tax, the withholding tax base is typically the gross amount or net amount depending on configuration, and it is derived from the invoice line item amount. A tax code is used for input tax calculation, not for withholding tax base. Even without a tax code, withholding tax can be calculated if the vendor master is set up correctly. So this is not the primary reason.

Trap 3: The withholding tax type is not activated in the relevant company…

While activating the withholding tax type in Customizing is necessary, it is a broader setting that applies to all vendors. If the type were not activated, no vendor would have withholding tax calculated. The scenario implies that other vendors might work correctly, so the issue is more likely vendor-specific. Thus, this is less likely than a missing vendor master configuration.

A
The withholding tax code is not maintained in the company code's payment terms configuration.
Why it fails: Payment terms determine due dates and cash discount periods; they do not control withholding tax calculation. Withholding tax codes are assigned to vendors, not to payment terms. Configuring payment terms with withholding tax codes is not a standard practice and would not resolve the issue. Therefore, this option is incorrect.
B
The invoice item does not have a tax code assigned, so the system cannot determine the withholding tax base amount.
Why it fails: In extended withholding tax, the withholding tax base is typically the gross amount or net amount depending on configuration, and it is derived from the invoice line item amount. A tax code is used for input tax calculation, not for withholding tax base. Even without a tax code, withholding tax can be calculated if the vendor master is set up correctly. So this is not the primary reason.
C
The vendor master record does not have the withholding tax type and code maintained in the company code segment.
For extended withholding tax to be calculated during invoice posting, the vendor master record must have the withholding tax type and withholding tax code assigned in the company code segment. Without this configuration, the system does not know which tax type and rate to apply. This is a common oversight when setting up new vendors or when migrating from classic withholding tax.
D
The withholding tax type is not activated in the relevant company code in Customizing.
Why it fails: While activating the withholding tax type in Customizing is necessary, it is a broader setting that applies to all vendors. If the type were not activated, no vendor would have withholding tax calculated. The scenario implies that other vendors might work correctly, so the issue is more likely vendor-specific. Thus, this is less likely than a missing vendor master configuration.

Question 6mediummultiple choice

In a parallel accounting scenario, a company needs to produce financial statements according to both local GAAP and IFRS. The accounting principle for IFRS requires a specific ledger, while local GAAP uses the leading ledger. Which configuration element directly enables the system to automatically post values to the additional ledger for IFRS?

Trap 1: Create a substitution rule that derives the accounting principle…

Substitution rules can derive values for fields, but they do not automatically post to additional ledgers. The accounting principle must be assigned to the ledger group to direct postings. Substitution is used for field derivation, not for ledger selection in parallel accounting.

Trap 2: Define a separate document type for IFRS postings and activate it…

Document types control number ranges and posting keys, not ledger selection. Creating a separate document type does not automatically direct postings to the IFRS ledger; it only affects document classification and numbering. The ledger determination is based on accounting principles and ledger groups, not document types.

Trap 3: Activate the 'Parallel Accounting' checkbox in the company code…

There is no 'Parallel Accounting' checkbox in company code settings. Parallel accounting is configured through ledgers, ledger groups, and accounting principles. Enabling a generic flag would not specify which ledger to update or how to apply the accounting principle.

A
Create a substitution rule that derives the accounting principle from the G/L account.
Why it fails: Substitution rules can derive values for fields, but they do not automatically post to additional ledgers. The accounting principle must be assigned to the ledger group to direct postings. Substitution is used for field derivation, not for ledger selection in parallel accounting.
B
Define a separate document type for IFRS postings and activate it in the leading ledger.
Why it fails: Document types control number ranges and posting keys, not ledger selection. Creating a separate document type does not automatically direct postings to the IFRS ledger; it only affects document classification and numbering. The ledger determination is based on accounting principles and ledger groups, not document types.
C
Activate the 'Parallel Accounting' checkbox in the company code settings.
Why it fails: There is no 'Parallel Accounting' checkbox in company code settings. Parallel accounting is configured through ledgers, ledger groups, and accounting principles. Enabling a generic flag would not specify which ledger to update or how to apply the accounting principle.
D
Assign the accounting principle to the ledger group that contains the IFRS ledger.
Assigning the accounting principle to the ledger group that contains the IFRS ledger ensures that all postings relevant to that principle are automatically recorded in the IFRS ledger. The system uses the principle to determine which ledger group to update, enabling parallel accounting without manual intervention.

Question 7hardmultiple choice

A financial accountant is configuring document splitting in SAP S/4HANA to enable segment reporting. The company requires that all documents are split by segment, and they want to ensure that the splitting is active for all relevant document types. Which configuration step is mandatory to activate document splitting for a ledger?

Trap 1: Activate the 'Segment Reporting' checkbox in the company code…

There is no 'Segment Reporting' checkbox in company code settings that activates document splitting. Segment reporting is enabled through the combination of document splitting configuration and the assignment of a splitting method to the ledger. Company code settings include other parameters like fiscal year variant and currency, but not document splitting activation.

Trap 2: Enable the 'Online Split' indicator in the general ledger…

The 'Online Split' indicator is not a standard configuration option for activating document splitting in SAP S/4HANA. Document splitting is activated by assigning a splitting method to the ledger. While online splitting is the default behavior, it is not controlled by a simple indicator in general ledger accounting configuration; it is inherent in the splitting method.

Trap 3: Define a document type for splitting in the document type…

Document types control number ranges and posting keys, but they do not activate document splitting. While you can exclude certain document types from splitting, the primary activation is done via the ledger settings. Defining a document type alone does not enable splitting; it is a separate configuration that governs document entry and processing.

A
Activate the 'Segment Reporting' checkbox in the company code settings.
Why it fails: There is no 'Segment Reporting' checkbox in company code settings that activates document splitting. Segment reporting is enabled through the combination of document splitting configuration and the assignment of a splitting method to the ledger. Company code settings include other parameters like fiscal year variant and currency, but not document splitting activation.
B
Enable the 'Online Split' indicator in the general ledger accounting configuration.
Why it fails: The 'Online Split' indicator is not a standard configuration option for activating document splitting in SAP S/4HANA. Document splitting is activated by assigning a splitting method to the ledger. While online splitting is the default behavior, it is not controlled by a simple indicator in general ledger accounting configuration; it is inherent in the splitting method.
C
Define a document type for splitting in the document type configuration.
Why it fails: Document types control number ranges and posting keys, but they do not activate document splitting. While you can exclude certain document types from splitting, the primary activation is done via the ledger settings. Defining a document type alone does not enable splitting; it is a separate configuration that governs document entry and processing.
D
Assign a splitting method to the ledger in the ledger settings.
To activate document splitting for a ledger, you must assign a splitting method to that ledger in the ledger settings. The splitting method defines the rules for how documents are split, such as by segment, profit center, or other dimensions. Without this assignment, document splitting does not occur for that ledger, even if other configurations are in place.

Question 8mediummultiple choice

A financial accountant is reviewing a supplier invoice posted in SAP S/4HANA. The invoice has a baseline date of July 1, payment terms of 14 days with a 2% discount, and a net due date of July 31. The supplier offers a cash discount if payment is made by July 15. The accountant wants to verify the discount basis date that the system uses to determine the cash discount deadline. Which date does the system use as the discount basis date?

Trap 1: The document date of the invoice

The document date is the date the invoice was originally created by the supplier, but it does not control the cash discount deadline. The system uses the baseline date for payment terms to calculate the discount period. Using the document date could lead to an incorrect discount calculation if the invoice is processed later than the document date.

Trap 2: The entry date of the invoice

The entry date is the date the document was entered into the system, which may differ from the baseline date. It does not affect the cash discount calculation. Payment terms are based on the baseline date for payment, which is typically derived from the invoice date or a default value from the vendor master record.

Trap 3: The posting date of the invoice

The posting date determines the fiscal period in which the invoice is recorded, but it does not drive the cash discount deadline. Payment terms use the baseline date to calculate due dates and discount periods. If the posting date were used, the discount period would shift based on when the accountant posts, which is not the intended behavior.

A
The document date of the invoice
Why it fails: The document date is the date the invoice was originally created by the supplier, but it does not control the cash discount deadline. The system uses the baseline date for payment terms to calculate the discount period. Using the document date could lead to an incorrect discount calculation if the invoice is processed later than the document date.
B
The baseline date for payment
The baseline date for payment is the starting point for calculating payment terms, including the cash discount period and the net due date. In this scenario, the baseline date of July 1 plus 14 days gives July 15 as the discount deadline with a 2% discount. The system uses this date to determine the discount amount and the net due date.
C
The entry date of the invoice
Why it fails: The entry date is the date the document was entered into the system, which may differ from the baseline date. It does not affect the cash discount calculation. Payment terms are based on the baseline date for payment, which is typically derived from the invoice date or a default value from the vendor master record.
D
The posting date of the invoice
Why it fails: The posting date determines the fiscal period in which the invoice is recorded, but it does not drive the cash discount deadline. Payment terms use the baseline date to calculate due dates and discount periods. If the posting date were used, the discount period would shift based on when the accountant posts, which is not the intended behavior.

Question 9mediummultiple choice

Which of the following is a key advantage of the SAP S/4HANA 'Central Finance' deployment scenario?

Trap 1: It migrates all legacy data to S/4HANA.

Central Finance replicates financial transactions from source systems to the central S/4HANA system, but it does not perform a full migration of all legacy operational data. The original source systems continue to run their business processes, while the central system focuses on financial consolidation and centralized reporting capabilities.

Trap 2: It forces all systems to use the same chart of accounts.

Central Finance uses mapping tools to convert different charts of accounts from source systems into the central system's format. This flexibility is a key advantage, as it avoids the need to force all legacy systems to adopt the same chart of accounts during the initial deployment phase.

Trap 3: It requires the decommissioning of all source systems.

One of the key benefits of Central Finance is that source systems can continue to operate as they are. This allows for a phased approach, reducing business risk by avoiding the need to shut down and decommission legacy systems immediately upon implementing the new central reporting financial hub.

A
It migrates all legacy data to S/4HANA.
Why it fails: Central Finance replicates financial transactions from source systems to the central S/4HANA system, but it does not perform a full migration of all legacy operational data. The original source systems continue to run their business processes, while the central system focuses on financial consolidation and centralized reporting capabilities.
B
It enables centralized reporting from multiple systems.
The main purpose of Central Finance is to provide a single view of financial data across a fragmented system landscape. By replicating documents in real-time, it allows for consolidated reporting, central financial processes, and uniform financial oversight without requiring immediate decommissioning of the source systems across the enterprise.
C
It forces all systems to use the same chart of accounts.
Why it fails: Central Finance uses mapping tools to convert different charts of accounts from source systems into the central system's format. This flexibility is a key advantage, as it avoids the need to force all legacy systems to adopt the same chart of accounts during the initial deployment phase.
D
It requires the decommissioning of all source systems.
Why it fails: One of the key benefits of Central Finance is that source systems can continue to operate as they are. This allows for a phased approach, reducing business risk by avoiding the need to shut down and decommission legacy systems immediately upon implementing the new central reporting financial hub.

Question 10mediummultiple choice

Which scenario best describes the purpose of the 'Document Type' in financial accounting?

Trap 1: It determines the fiscal year variant for the document.

The fiscal year variant is assigned at the company code level, not the document type level. The document type manages the document-specific behavior during posting, but it does not influence the fiscal structure or the time-based reporting periods defined for the organization's financial system.

Trap 2: It is used to assign the posting period variant.

Posting period variants are assigned to company codes to manage open and closed periods. The document type has no authority over the posting period; it is merely an indicator for how the entry itself should be processed, stored, and numbered within the chosen period.

Trap 3: It identifies the ledger group for all postings.

While ledger groups can be linked to document types, the document type's primary purpose remains the classification of the transaction type and the control of entry parameters. Ledger group assignment is a separate configuration setting within the document splitting or ledger activation process, not the defining purpose.

A
It determines the fiscal year variant for the document.
Why it fails: The fiscal year variant is assigned at the company code level, not the document type level. The document type manages the document-specific behavior during posting, but it does not influence the fiscal structure or the time-based reporting periods defined for the organization's financial system.
B
It controls the number range and account type access.
Document types define the number range that will be assigned to a posting and restrict which account types (e.g., vendor, customer, G/L) can be used. This control is essential for ensuring that only appropriate entries are made in specific business processes, such as invoice receipts or journal vouchers.
C
It is used to assign the posting period variant.
Why it fails: Posting period variants are assigned to company codes to manage open and closed periods. The document type has no authority over the posting period; it is merely an indicator for how the entry itself should be processed, stored, and numbered within the chosen period.
D
It identifies the ledger group for all postings.
Why it fails: While ledger groups can be linked to document types, the document type's primary purpose remains the classification of the transaction type and the control of entry parameters. Ledger group assignment is a separate configuration setting within the document splitting or ledger activation process, not the defining purpose.