How many Refer to the Exhibit Practice Questions questions are on this page?

This page has 13 Refer to the Exhibit Practice Questions scenario questions for the C_TS4FI exam, each with detailed explanations and wrong-answer analysis.

How should I approach C_TS4FI scenario questions?

Read the full scenario before looking at the answer options. Identify the constraint or requirement in the scenario, then eliminate options that are generally true but wrong for this specific case. Scenario questions reward careful reading over pattern matching.

← Back to SAP Certified Associate - SAP S/4HANA for Financial Accounting questions

Scenario-based practice

Refer to the Exhibit Practice Questions

Practise SAP Certified Associate - SAP S/4HANA for Financial Accounting practice questions — original exam-style scenarios covering every exam domain, with detailed explanations, wrong-answer analysis, and common exam traps.

Start full practice test Read exam guide

scenario questions

C_TS4FI

exam code

SAP

vendor

Scenario guide

How to approach refer to the exhibit practice questions

Practise exhibit-style questions that ask you to read a topology, table, command output or diagram before choosing the best answer.

Quick answer

Exhibit-style questions test whether you can read a topology, command output, diagram or table before choosing the best answer.

How to extract the relevant detail from an exhibit.

How topology, command output or routing information affects the answer.

How to avoid answering from memory before reading the evidence.

How to map the exhibit back to the exam objective.

Practice scenarios

Question 1hardmultiple choice

Full question →

Refer to the exhibit. A user attempts a manual journal entry to an account governed by this policy. What is the expected system behavior?

Exhibit

JSON Policy: { "allow_manual_entry": false, "source": "automatic", "validation": "strict" }

A
The entry will be parked for future approval.
Why it fails: A policy set to disallow manual entry does not permit parking. Parking still constitutes a form of manual entry. The system will block the transaction immediately because the account configuration prohibits manual interaction, regardless of whether the entry is intended for immediate posting or temporary parking.
B
The system will return an error and block the posting.
The 'allow_manual_entry: false' parameter acts as a hard control. Any attempt to record a manual journal entry (FB50 or similar) against such an account triggers an immediate validation error, preventing the user from completing the posting to maintain the integrity of the automated data feed.
C
The entry will be allowed but flagged for audit.
Why it fails: When manual entry is disabled at the account level, the system does not provide a bypass for audit flags. The policy is designed to enforce systemic integrity, meaning the transaction is rejected entirely. There is no mechanism to override this via an audit flag for account-level restrictions.
D
The system will automatically convert the entry to an automated one.
Why it fails: The system cannot automatically convert a user-inputted document into an automated one, as it lacks the context and origin data required for an automated transaction. The restriction is meant to stop users from bypassing system-generated processes, so the entry is simply rejected by the validation logic.

Full breakdown with real-world context →

Question 2mediummultiple choice

Full question →

Refer to the exhibit. If you post an asset acquisition, how does the system ensure the value is recorded in both ledgers correctly?

Exhibit

Config: Ledger 0L (Leading), Ledger L1 (Non-Leading). Mapping: Ledger L1 -> IFRS.

A
It requires a manual journal entry in each ledger.
Why it fails: Manual entries are error-prone and defeat the purpose of S/4HANA's automated parallel accounting. The system is designed to handle this automatically through the Ledger Group and Accounting Principle framework, which routes the postings correctly to the appropriate ledgers without requiring human intervention for every asset movement.
B
It uses the assigned Accounting Principle to determine the ledger.
The Accounting Principle acts as the bridge. When a document is posted, the system identifies the relevant ledger group based on the assigned accounting principle. This allows the system to determine which ledgers need to be updated, ensuring that valuation differences are captured according to the local or international standards.
C
The asset only records values in the leading ledger.
Why it fails: If the asset only recorded values in the leading ledger, you would be unable to meet reporting requirements for other accounting standards. S/4HANA supports multi-ledger asset accounting, meaning assets can hold different values in different depreciation areas, which map to different ledgers for full compliance.
D
It requires an additional document type for each ledger.
Why it fails: While document types are used to categorize postings, you do not need unique document types for each ledger. The routing logic is handled by the ledger group and accounting principle configuration, which separates the data at the database level without complicating the user's document entry process.

Full breakdown with real-world context →

Question 3hardmultiple choice

Full question →

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' }

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.

Full breakdown with real-world context →

Question 4mediummultiple choice

Full question →

Refer to the exhibit. Which ledger is being referenced in this configuration snippet?

Exhibit

JSON: { "ledger": "0L", "fiscal_year": "2023", "valuation": "Group" }

A
A non-leading ledger.
Why it fails: Non-leading ledgers are identified by custom codes, not '0L'. The '0L' code is reserved exclusively for the leading ledger in SAP S/4HANA. Understanding this naming convention is basic but essential for consultants to correctly distinguish between the main ledger and any additional ledgers used for parallel accounting requirements.
B
The Leading Ledger.
The code '0L' is the standard system identifier for the leading ledger. It is the primary ledger that serves as the foundation for financial reporting, ensuring all company codes share the same fiscal year and currency settings, which is essential for accurate group-level financial statement preparation in S/4HANA.
C
A special purpose ledger.
Why it fails: Special purpose ledgers were a feature of older SAP ERP systems. In S/4HANA, they have been superseded by the universal journal architecture and the multi-ledger concept. '0L' denotes the leading ledger, which is a structural part of the new architecture, not a special purpose ledger object.
D
A ledger for tax accounting.
Why it fails: Tax accounting is handled within the existing ledgers using specific G/L accounts or tax reporting configurations. There is no standard 'tax ledger' identified by the '0L' code. '0L' is the global leading ledger, which serves as the core record for all mandatory financial reporting for the company.

Full breakdown with real-world context →

Question 5hardmultiple choice

Full question →

Refer to the exhibit. What is the impact on a user attempting to post a document to a G/L account assigned to field status group G001?

Exhibit

JSON Config Snippet:
{
  "field_status_group": "G001",
  "cost_center": "Optional",
  "assignment": "Required"
}

A
The user will be prompted to enter a cost center.
Why it fails: The exhibit shows that the cost center is marked as 'Optional' in the configuration. Therefore, the system will not force the user to provide a cost center value, meaning the posting will proceed even if the cost center field remains blank during the document entry process for the transaction.
B
The user must enter a value in the assignment field.
Since the configuration explicitly marks 'assignment' as 'Required' for field status group G001, the system will raise an error if the user attempts to post without providing a value in this field. This ensures that the necessary data is collected for future reporting or reconciliation of the account.
C
The system will automatically generate an assignment value.
Why it fails: Field status settings define user input requirements, not automatic value derivation logic. The system expects the user to manually enter a value in the required field; it does not contain built-in logic to auto-populate the assignment field based on the field status configuration alone during a manual G/L posting.
D
The posting will be rejected due to an error in G001.
Why it fails: The field status configuration shown is valid and consistent with standard SAP functionality. It does not cause a system error itself; it merely enforces the defined input rules. The posting will only be rejected if the user fails to fulfill the specific 'Required' condition for the assignment field.

Full breakdown with real-world context →

Question 6mediummultiple choice

Full question →

Refer to the exhibit. Why does the system return an error when attempting to post to period 12?

Exhibit

LOG_FILE: { "PostDate": "2023-12-31", "Ledger": "0L", "Period": "12", "Status": "CLOSED" }

A
The document date is outside the defined fiscal year variant.
Why it fails: The issue relates specifically to the period status in the posting period variant, not the fiscal year variant definition itself. If the fiscal year variant were incorrect, the system would throw a different error regarding the period calculation. The log clearly indicates the period is closed, which is the primary cause.
B
The posting period is closed in the Posting Period Variant.
Transaction OB52 controls the status of posting periods for company codes. When a period is marked as closed, the system blocks any further postings to that period to maintain the integrity of financial results. This is a standard closing process step to prevent accidental adjustments to finalized financial records.
C
The user does not have authorization to post to the ledger 0L.
Why it fails: While authorization issues can prevent posting, the error indicates a period status conflict. If it were an authorization issue, the error message would explicitly state 'Insufficient authorization' or refer to a specific authorization object failure. The provided exhibit points directly to the period status, making it the definitive reason.
D
The ledger 0L is not active for the company code.
Why it fails: If the ledger were not active, the system would block document posting entirely, regardless of the period status. The existence of a status in the log file suggests the ledger is active but is restricted by the period configuration. Period status is a common control, whereas ledger activation is a global setting.

Full breakdown with real-world context →

Question 7hardmultiple choice

Full question →

Refer to the exhibit. A user posts a document using an account assigned to Field Status Group 0001. What happens if the 'Cost Center' field is left empty?

Exhibit

LOG_CONFIG: 'Field_Status_Group_0001' | 'Assignment_Field' = 'Optional' | 'Cost_Center' = 'Required'.

A
The document is posted with a default cost center.
Why it fails: SAP does not automatically fill required fields with defaults unless specifically configured through substitution rules. If a field is set to 'Required' in the field status group, the system strictly enforces user entry, and the document will not post without valid, user-provided input in that specific field.
B
The system issues an error and prevents posting.
Because the field status group defines the Cost Center as 'Required', the system performs a validation check. If the field is empty, the check fails, and the system issues an error message to ensure data integrity, blocking the document from being processed until the required information is entered.
C
The document is posted, but a warning is logged.
Why it fails: Required fields do not trigger warnings; they trigger hard errors that stop the posting process. A warning would imply that the field is optional, allowing the user to bypass the entry. Since the configuration explicitly requires the field, the system must enforce this strictly through an error message.
D
The system prompts the user to enter the cost center later.
Why it fails: SAP does not allow document posting with incomplete required fields to be resolved later. Once a document is posted, it is immutable in terms of its core structure. The system requires all mandatory fields to be filled during the creation of the document, ensuring that financial data is complete and accurate.

Full breakdown with real-world context →

Question 8hardmultiple choice

Full question →

Refer to the exhibit. Why are users unable to post to account 400000?

Exhibit

Config: 
GL Account: 400000
Field Status Group: G001
Text field: Required
Error Log: 
'Field 'Text' is not filled in entry.'

A
The G/L account is blocked for posting.
Why it fails: If the account were blocked, the error message would explicitly state that the account is blocked for posting. The error provided clearly points to a field-level validation issue, specifically regarding the 'Text' field requirement defined in the field status group assigned to the G/L account.
B
The field status group requires the Text field.
The field status group G001 requires the Text field during document entry. Because the user failed to enter a value, the document validation logic stops the posting to maintain data quality. This configuration is a common control measure to ensure that all manual postings contain descriptive information.
C
The posting key is set to hide the text field.
Why it fails: Field status settings are a combination of posting key and field status group. Even if a posting key hides a field, the field status group's requirement overrides it. However, the error log confirms the requirement is active and unfulfilled, pointing to the field status group configuration primarily.
D
The fiscal year variant is not defined.
Why it fails: A missing fiscal year variant would prevent the system from knowing which period to post to, resulting in a system-level initialization error, not a field-level error. Field status errors are strictly related to the data provided within the specific line items of the accounting document.

Full breakdown with real-world context →

Question 9hardmultiple choice

Full question →

Refer to the exhibit. Why is this error occurring during a journal entry posting?

Exhibit

Error: Account 600000 requires an assignment to a CO object.
Message: KI235
Technical Context: Cost Element 600000 is a primary cost element.

A
The G/L account is not defined as a cost element.
Why it fails: If the account were not a cost element, the system would not trigger the CO object requirement check (KI235). The fact that the error message explicitly references the CO object requirement confirms that the account is already correctly maintained as a primary cost element in the system's configuration.
B
The posting date is outside the open fiscal period.
Why it fails: Period-related errors generate messages like 'Period not open' rather than CO-specific assignment errors. The KI235 message specifically points to the missing assignment of a cost object, not the validity of the accounting period, which would be handled by the FI period control settings in transaction OB52.
C
A primary cost element requires a valid account assignment object.
Primary cost elements transfer costs from FI to CO. When these accounts are posted, they must be linked to a cost center, internal order, or WBS element to ensure the costs are accurately captured in Controlling, allowing for precise management reporting and performance measurement of the specific business activity.
D
The company code is not assigned to a controlling area.
Why it fails: If the company code were not assigned to a controlling area, the system would prevent the assignment of any cost element entirely. The error specifically demands an assignment, implying that the controlling area is active and expecting cost information to be passed from the general ledger to the controlling module.

Full breakdown with real-world context →

Question 10hardmultiple choice

Full question →

Refer to the exhibit. You are setting up a new Asset Class in SAP S/4HANA. Which object is mandatory to link the asset class to the General Ledger?

Exhibit

JSON_CONFIG: { "AssetClass": "3000", "DepreciationKey": "LIN1", "UsefulLife": "10", "AssetAccount": "160000" }

A
The Depreciation Area.
Why it fails: Depreciation areas control how valuations are calculated for different reporting purposes, such as local GAAP or IFRS. While they are crucial for asset accounting, they do not directly perform the mapping of the asset class to the G/L account; that task is the primary responsibility of the account determination key.
B
The Account Determination Key.
The account determination key is the bridge between the asset class and the G/L accounts. By assigning a specific key to an asset class, you define which G/L accounts will be debited or credited during asset transactions like acquisition or depreciation, ensuring that all postings are recorded in the correct ledger accounts.
C
The Screen Layout Rule.
Why it fails: The screen layout rule defines which fields are visible or mandatory in the asset master record. While it is important for data entry consistency, it has no role in the accounting integration or the derivation of G/L accounts for financial postings. It is strictly a user interface configuration tool.
D
The Number Range Interval.
Why it fails: Number ranges define the sequence and format of asset numbers. While essential for managing the master data records, they do not influence the financial accounting postings or the G/L account derivation. They are strictly an administrative setting for organizing asset master records within the system's database, not for financial integration.

Full breakdown with real-world context →

Question 11hardmultiple choice

Full question →

Refer to the exhibit. In the context of S/4HANA multi-ledger architecture, what does the '0L' ledger represent?

Exhibit

JSON config: { 'ledger_id': '0L', 'valuation_view': '0', 'company_code': 'DE01', 'posting_period': '001/2024' }

A
A non-leading ledger for local GAAP reporting.
Why it fails: Non-leading ledgers are typically identified by two-character codes other than '0L'. They are used for parallel accounting to satisfy local reporting requirements that differ from the global accounting standards applied in the Leading Ledger. '0L' is reserved specifically for the mandatory leading ledger functionality in S/4HANA.
B
The mandatory leading ledger for global reporting.
The '0L' ledger is the default leading ledger in S/4HANA. It is mandatory because it serves as the foundation for the entire company's financial accounting. It ensures that the group-wide accounting standards are applied consistently across all company codes, providing the central truth for all financial reporting activities.
C
A specialized ledger for budget planning.
Why it fails: Budgeting is handled by the Budget Control System (BCS) or Financial Planning components within SAP, not by the ledger definitions. While ledgers can hold statistical data, '0L' is the financial ledger for actual transaction postings and is not designed for budget planning or forecasting activities.
D
A temporary ledger for data migration.
Why it fails: The leading ledger is not temporary; it is the permanent record-keeping structure for the company. Temporary ledgers do not exist in the standard S/4HANA ledger configuration. Migration is performed into the existing ledger structure, as the leading ledger remains the consistent source of financial data throughout the system's life.

Full breakdown with real-world context →

Question 12hardmultiple choice

Full question →

Refer to the exhibit. A user attempts to post a vendor invoice in company code 1000 for period 01 2023. Given the configuration state, what is the outcome of the posting attempt?

Exhibit

TABLE: T001
BUKRS: 1000
PERIV: K4
OPVAR: 1000
CURR: EUR

TABLE: T001B
BUKRS: 1000
PERIOD: 01 2023
STATUS: LOCKED

A
The system allows the posting but generates a warning message in the application log.
Why it fails: The status 'LOCKED' in the posting period maintenance implies a restriction that prevents any activity for the specified interval. SAP does not treat this as a warning because allowing postings into locked periods would compromise the accuracy of financial statements prepared for that specific accounting interval during the month-end.
B
The document is posted successfully because the fiscal year variant K4 is active.
Why it fails: The fiscal year variant determines the structure of the periods but does not override the posting period status. Even with a valid fiscal year variant, the explicit lock on the period via transaction OB52 takes precedence, rendering the posting attempt invalid regardless of the underlying calendar setup.
C
The system rejects the posting and triggers an error message regarding the closed period.
The system checks the T001B table during the posting process. Because the period is set to 'LOCKED', the validation logic encounters a block. This prevents the user from committing the invoice to the Universal Journal, ensuring that no unauthorized entries are made into a period that is already officially closed.
D
The document is saved in the parked status for later approval by the accounting manager.
Why it fails: Parking a document still requires the period to be open for the document date and posting date provided. The system validation logic applies to both parked and posted documents to prevent inconsistencies. Therefore, even parking is blocked when the fiscal period is locked to prevent data manipulation.

Full breakdown with real-world context →

Question 13hardmultiple choice

Full question →

Refer to the exhibit. Why does the system trigger this error during a manual G/L posting?

Exhibit

Error Log: 
ACDOCA-GLACC: 100000
Error: Account 100000 requires a cost element.
Context: Manual posting to G/L account via FB50.

A
The G/L account is missing a posting key configuration.
Why it fails: Posting keys define the debit or credit nature of a line item but do not govern the requirement for a cost object. This error is specific to the master data attributes of the G/L account, specifically its role as a cost element within the Controlling module integration.
B
The G/L account is a primary cost element and requires a cost object.
The system identifies the G/L account as a primary cost element, which requires a cost object to ensure proper integration with the Controlling module. Since the user failed to provide a cost center or order, the document validation fails to maintain consistency between Financial and Management Accounting.
C
The fiscal year is not open for the company code.
Why it fails: If the period were closed, the system would return a specific error message stating that the posting period is not open. The provided error specifically mentions the requirement for a cost element, which pertains to master data and Controlling configuration rather than period status control settings.
D
The company code is not assigned to a controlling area.
Why it fails: If the company code lacked a controlling area, the system would raise a different error concerning the inability to initialize the controlling module. The error specifically relates to the missing requirement for a cost element entry, confirming that the Controlling integration is active but incorrectly handled.

Full breakdown with real-world context →

Study guide

C_TS4FI study guide

Read the full exam guide to reinforce the concepts behind these scenario questions.

Read now

Scored practice sessions

Quick scored rounds with instant marking and a written explanation per question.

Exam simulator

Take a full practice exam

75–120 questions · 120-min timer · PBQs first · Pearson VUE–style score (300–1000)

Start exam

Domain-focused practice

Each domain maps to a weighted exam section. Focus on the domain where you are weakest.

Financial Accounting

Practice by scenario

Practise one question format at a time: exhibits, multi-select, drag-and-drop, troubleshooting.

Browse scenarios

Topic-level practice

Each topic page collects the questions that test one concept, plus the theory behind it.

Financial Accounting practice questions C_TS4FI fundamentals practice questions C_TS4FI scenario practice questions C_TS4FI troubleshooting practice questions

Common exam traps

•Skipping the exhibit and answering from memory.
•Reading the wrong device, interface, VLAN, route or service.
•Missing a small detail such as a subnet mask, allowed VLAN or next hop.
•Choosing an answer that is generally true but not true for the exhibit.

Where to go next

SAP Certified Associate - SAP S/4HANA for Financial Accounting exam guide All C_TS4FI questions All practice sets

These C_TS4FI practice questions are part of Courseiva's free SAP certification practice question bank. Courseiva provides original exam-style C_TS4FI questions with detailed explanations, topic-based practice, mock exams, readiness tracking, and study analytics.

Refer to the Exhibit Practice Questions

How to approach refer to the exhibit practice questions

Quick answer

Related C_TS4FI topic practice pages

Financial Accounting practice questions

C_TS4FI fundamentals practice questions

C_TS4FI scenario practice questions

C_TS4FI troubleshooting practice questions

Practice scenarios

Refer to the exhibit. A user attempts a manual journal entry to an account governed by this policy. What is the expected system behavior?

Exhibit

Refer to the exhibit. If you post an asset acquisition, how does the system ensure the value is recorded in both ledgers correctly?

Exhibit

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

Refer to the exhibit. Which ledger is being referenced in this configuration snippet?

Exhibit

Refer to the exhibit. What is the impact on a user attempting to post a document to a G/L account assigned to field status group G001?

Exhibit

Refer to the exhibit. Why does the system return an error when attempting to post to period 12?

Exhibit

Refer to the exhibit. A user posts a document using an account assigned to Field Status Group 0001. What happens if the 'Cost Center' field is left empty?

Exhibit

Refer to the exhibit. Why are users unable to post to account 400000?

Exhibit

Refer to the exhibit. Why is this error occurring during a journal entry posting?

Exhibit

Refer to the exhibit. You are setting up a new Asset Class in SAP S/4HANA. Which object is mandatory to link the asset class to the General Ledger?

Exhibit

Refer to the exhibit. In the context of S/4HANA multi-ledger architecture, what does the '0L' ledger represent?

Exhibit

Refer to the exhibit. A user attempts to post a vendor invoice in company code 1000 for period 01 2023. Given the configuration state, what is the outcome of the posting attempt?

Exhibit

Refer to the exhibit. Why does the system trigger this error during a manual G/L posting?

Exhibit