SAP C_TS4FI_2023 Exam Questions & Answers

SAP S/4HANA Cloud, Financial Accounting Exam Notes

This document provides a structured overview of key concepts and configurations within SAP S/4HANA Cloud Private Edition, Financial Accounting, based on common exam questions.

Organizational Elements and Master Data

• Company Code: The smallest organizational unit for which a complete, self-contained set of accounts can be drawn up for external reporting. Required for legal financial statements in different countries.

• Controlling Area: An organizational unit that structures the internal accounting activities. Multiple company codes can be assigned to the same controlling area if they share common settings like fiscal year variant and operating chart of accounts.

• Client: The highest organizational unit in SAP, representing a legal entity.

• Chart of Accounts: A list of all G/L accounts used by one or more company codes.

  • Operating Chart of Accounts: Used for daily postings.

  • Group Chart of Accounts: Used for consolidation across multiple company codes. Assigned to the operating chart of accounts.

  • Country-Specific Chart of Accounts: Used for country-specific legal reporting.

• Fiscal Year Variant: Defines the number of posting periods and the start and end dates of these periods. It is common to all company codes within the same controlling area.

• Functional Area: Defines how the Profit & Loss (P&L) statement is structured according to cost-of-sales accounting. Defined at the Client level.

• Segment and Profit Center: Used for internal segment reporting (e.g., IFRS). Can be shared by several company codes.

• Business Area: Can be shared by several company codes for internal reporting across different product lines or regions.

Universal Journal (ACDOCA)

The Universal Journal (table ACDOCA) is the single source of truth in SAP S/4HANA, recording all financial line items.

• It records primary costs (e.g., from a distribution), secondary costs (e.g., from an assessment), and intercompany postings.

• Budgeted costs for a cost center and plan depreciation amounts are generally not recorded in ACDOCA directly as actual financial postings.

Currencies and Exchange Rates

• Default Currency Types in SAP S/4HANA:

  • 00 = Document Currency: The currency of the transaction.

  • 10 = Company Code Currency: The local currency of the company code.

• Additional Currency Types:

  • 30 = Group Currency: Used for group-level reporting.

  • 60 = Global Company Currency: Another currency type that can be defined for a specific ledger.

  • 40 = Hard Currency: Can be defined for a specific ledger.

• Currency Type Assignment: Assigned at the Ledger level.

• Exchange Rate Type: Controls whether to use direct or indirect quotation. Also defines how currency translation ratios between two currencies are maintained.

Asset Accounting (FI-AA)

• Technical Clearing Account for Integrated Asset Acquisition: Posted in scenarios like direct asset acquisition posting with a vendor invoice (not linked to a purchase order) and valuated goods receipt on a purchase order with an asset as account assignment.

  • Prerequisites: Must be a balance sheet account and defined as a reconciliation account for fixed assets.

  • Definition Levels: Defined at the Account determination and Chart of Accounts levels.

• Depreciation Areas:

  • Depreciation Area 01: Must be linked to the leading ledger OL and cannot take over values from other areas. It must always post in real time.

  • Parallel Currency Depreciation Area: For parallel currencies, the depreciation area often does not post to G/L directly but derives values from other areas or posts periodically.

• Posting Depreciation Costs to Multiple Cost Centers: Achieved by assigning a real internal order in the asset master data and settling it periodically to the desired cost centers. Assigning two real cost centers directly is not possible.

• Unplanned Depreciation: Posting is done in FI-AA in real time and in FI-GL once the depreciation posting program has run.

• Asset Acquisition Vendor Invoice (without PO): Generates multiple accounting documents: one document per accounting principle and one document for all accounting principles.

• Statistical Account Assignment for Asset Cost Postings: A profit center is only a statistical account assignment for cost postings to an asset.

• WBS Element as Account Assignment (with "balance sheet" and "identical" active):

  • The WBS Element is available for input in the asset master record.

  • The WBS Element cannot be changed in the asset master record once the asset is capitalized.

• Changing Depreciation Cost Center: If you want to post depreciation costs to a different cost center than specified in the asset master data, you can do this by creating a substitution in Financial Accounting line items.

• Legacy Data Transfer (via transaction AS91): Used for creation of master data and posting of take over values.

• Segment Reporting Activation Consequences: The segment appears in the screen layout for asset master data and in the additional account assignment configuration. It is not automatically updated in existing asset master data.

General Ledger (FI-GL)

• Assigning Alternative Account to G/L Account Error: Can occur if the alternative account is already assigned to another G/L account for the company code.

• Document Splitting: If document splitting is activated, the general ledger view may have more items than the entry view due to the detailed display of sub-ledger accounts or the splitting of lines to balance segments/profit centers.

• P&L Statement G/L Account Types: Values are shown from Non-operating Expense or Income, Primary Costs or Revenue, and Secondary Costs. Balance Sheet Accounts and Cash Accounts are not typically used for P&L presentation.

• Switching off Open Item Management: A G/L account must not have been posted to to switch off open item management.

• G/L Account Number Range Extension: To extend the number range, you need to customize the account group.

• Leading Ledger Differentiation: It does not derive values from other ledgers.

• Reposting a Document After Reversal (due to wrong number range): You need to change the document type.

• G/L Account Extension to New Company Code: When extending, account currency and field status group must always be maintained.

• Fields on Chart of Accounts Level for G/L Account: Group account number, Short text, and Account group are maintained at this level.

• GR/IR Account Not Zero Balance: Possible causes include a partial goods receipt for which an invoice has not yet been received or a partial invoice receipt but no goods receipt yet.

Foreign Currency Valuation

• Items Taken into Account: Balance valuation on items for balance sheet accounts not defined as open item management and line item valuation for balance sheet accounts defined as open item management.

• Role of Valuation Method: Defines the document type for the valuation posting, the valuation procedure, and determines the exchange rate type. It also determines the G/L accounts for the valuation posting and defines the posting and reversal date.

• Determining Accounting Principle: The relevant accounting principle is determined via the valuation area.

• Posting Valuation Differences (for period-end reporting, to be reversed): The system uses an adjustment G/L account for foreign currency.

Intercompany Matching and Reconciliation (ICMR)

• Purpose of ICMR: Useful for generating automatic posting to correct intercompany discrepancy and to highlight and solve intercompany data discrepancies, triggering a workflow.

• ICMR Definition: A solution that facilitates transaction matching between systems in Central Finance and can be integrated with Group Reporting.

• Matching Results: Can be seen in an application-specific table (ICADOCM).

Financial Statement Reporting

• Net Profit Discrepancy: Can be caused by adding an account to the wrong node (e.g., assets section) or by having accounts not assigned in the financial statement version.

• Consolidated Financial Report: To accommodate consolidation for 15 legal entities (10 in S/4HANA, 5 in legacy systems), you should define 5 companies in your SAP S/4HANA system (one for each legacy system entity, plus perhaps a single company representing all 10 S/4HANA entities).

• Object for Consolidation Preparation: Company/Trading Partner is used to directly support preparation for consolidation.

Customer/Vendor Accounting (Accounts Receivable & Accounts Payable)

• Customer Balance Confirmation (Discrepancy expected): Use a balance notification.

• Restricting Postings: Posting period variants can restrict postings at the G/L account and supplier account levels.

• Dunning Process Mandatory Steps: Maintain the parameters of the dunning program, start the dunning printout, and schedule the dunning run.

• Noted Items Characteristics: They can be accessed by the payment program and the dunning program, themanaged as open items on customer and vendor accounts, and they generate statistical postings. They do not update the general ledger in Entry View only and don't generally generate postings that do not balance.

• Guarantee Recording: Recording a guarantee of EUR 10000 in SAP S/4HANA results in two statistical line items.

• Multiple Company Codes in Payment Run Prerequisites: The company codes must have the same configuration for payment transactions and must be located in the same country.

• Undoing Customer Open Item Clearing: Options include reset and reverse the clearing document or merely reset the clearing document.

• Credit Memo Ignoring Payment Terms: Reasons include the credit memo being created without reference to an invoice or the due date determined based on entered payment terms being in the past.

• Regrouping Receivables and Payables: You configure the Sort Method for this.

• Reason Code in Accounts Receivable Control: Controls the type of payment notice sent to a customer, the account where a residual item is posted, and the exclusion of disputed residual items from credit limit checks.

• Dunning Level Parameters: You can configure days in arrears and payment deadline.

• Incoming Payment with Residual Item Consequences: The residual item becomes a new receivable, and the original document and the payment are cleared. The residual item is typically not written off to a cost account automatically at this stage.

• Payment Method Parameters (Company Code Level): Foreign currency allowed and minimum and maximum payment amounts are defined at this level.

• Purchase Order Accruals Use Cases: Applicable for purchase of services and purchase of consumable materials.

• COGS Posting in Standard Sales Process: Generated in Financial Accounting during the Post Goods Issue (PGI) step.

• Invoice Payment Date Determination: The system determines the baseline date when entering an invoice that needs to be paid.

SAP S/4HANA Technologies and Concepts

• SAP Business Network: Builds on solutions like Contingent Workforce, Travel, and Procurement.

• Industry Cloud: A component of the Intelligent Enterprise allowing customers to discover and deploy vertical solutions from SAP and partners.

• SAP Fiori Apps on Any Database: Make Bank Transfers and Manage Chart of Accounts can run on any database.

• SAP Fiori Launchpad Page Assignment: Pages are assigned to users via spaces assigned to business roles which are assigned to users.

• SAP Business Technology Platform (BTP) Features: Provides data management and analytics and supports application development and integration.

• 3-Way Match in Procurement: In SAP S/4HANA, the invoice needs to be created in reference to the goods receipt. This typically refers to the matching of Purchase Order, Goods Receipt, and Invoice Receipt to ensure accurate payments.

• Correspondence Type Assignment: The print program and its variant can be assigned to the correspondence type at the Client and Company Code levels.

Integration and Clean Core

• Recommended API Types for Clean Core Integrations: SOAP and OData.

• Exploring Released APIs: Use the SAP Business Accelerator Hub.

• SAP Recommended Guiding Principles for Clean Core Operations:

  1. Establish regular housekeeping tasks and procedures.

  2. Establish an organizational structure, technical foundation, and transformation methodology for clean core.

  3. Integrate clean core practices in the end-to-end value process chain.

• ABAP Cloud-Native Development Model: The ABAP RESTful Application Programming Model can be used for this.

Key Takeaways

• Organizational structures like company codes and controlling areas form the foundation of financial accounting in SAP.

• The Universal Journal (ACDOCA) ensures a single source of truth for all financial postings.

• Understanding currency types, exchange rates, and their configuration is crucial for global operations.

• Asset accounting has specific rules for depreciation, acquisitions, and technical clearing accounts.

• G/L account master data and customizing (e.g., account groups, field status) are vital for proper financial reporting.

• Foreign currency valuation and intercompany reconciliation involve specific processes and configurations to manage cross-currency and intercompany transactions.

• SAP S/4HANA leverages the Fiori Launchpad and modern integration technologies (APIs, BTP) for an improved user experience and system landscape.

• "Clean Core" principles guide development and integration practices to maintain system standardisation and reduce complexity.

SAP S/4HANA Finance Essentials

This document provides a concise overview of key concepts and configurations within SAP S/4HANA Financial Accounting, covering organizational elements, currency management, asset accounting, general ledger, and various financial processes.

1. Organizational Elements and Hierarchy

Understanding the SAP organizational structure is fundamental for financial reporting and business operations.

• Company Code: The smallest organizational unit for which a complete, self-contained set of accounts can be drawn up for external reporting purposes. It is legally independent.
• Client: The highest organizational unit in an SAP system, representing a self-contained commercial, organizational, and technical unit.
• Controlling Area: An organizational unit that represents a closed system for cost accounting. One or more company codes can be assigned to a single controlling area, provided they share specific common settings.
• Segment: Used for segment reporting, especially for IFRS. Multiple company codes can share segments.
• Business Area: An organizational unit within financial accounting that classifies business operations according to different areas of responsibility or lines of business. Several company codes can share business areas.
• Profit Center: An organizational unit in controlling used for internal reporting and profit analysis. It can be shared across multiple company codes.
• Functional Area: An organizational unit used in cost-of-sales accounting to categorize expenses based on their function (e.g., production, sales, administration). Defined at the Client level.
• Plant: An organizational unit within Logistics, representing a facility where goods are produced or stored. Can be shared by several company codes.

Common Settings for Company Codes in a Controlling Area

When multiple company codes are assigned to the same controlling area, they must share the following common settings:

• Fiscal Year Variant
• Operating Chart of Accounts

Creating a Company Code

To establish a new company code, especially for legal reporting in a different country (e.g., Switzerland as per local legal requirements), the following steps are typically performed:

1. Define Company Code (Transaction Code: OX02):
   • Enter a four-character alphanumeric code.
   • Fill in details like company name, city, country, currency, and language.
2. Assign Company Code to Company (Transaction Code: OX16): Select the company code and assign it to the appropriate company entity.
3. Define Additional Settings:
   • Fiscal Year Variant (Transaction Code: OB29 and OB37): Define and assign if different from the main variant.
   • Field Status Variant (Transaction Code: OBC4 and OBC5): To control data entry for fields.
   • Open and Close Posting Periods (Transaction Code: OB52): Define periods for allowing postings.

2. Currency Management

SAP S/4HANA handles multiple currencies to support diverse reporting and transaction needs.

• Default Currency Types (SAP S/4HANA):
  • 00 = Document Currency: The currency in which the transaction is originally posted.
  • 10 = Company Code Currency: The local currency of the company code.
• Additional Currency Types for Ledgers:
  • 30 = Group Currency: Used for group-level reporting.
  • 60 = Global company currency.
  • 40 = Hard currency.

Currency Translation Ratio

The currency translation ratio between two currencies is maintained at the Exchange Rate Type level.

Direct vs. Indirect Quotation

The choice between direct and indirect quotation for exchange rates is made at the following levels:

• Exchange rate type
• Client

3. General Ledger (G/L) and Universal Journal

The Universal Journal (ACDOCA table) is the single source of truth in SAP S/4HANA, consolidating financial and controlling data.

Line Items in ACDOCA

The following line items are recorded in table ACDOCA:

• Primary costs resulting from a distribution.
• Secondary costs resulting from an assessment.
• Intercompany postings.

G/L Account Management

• G/L Account Number Range: Customized through the Account group.
• G/L Account Extension: When extending a G/L account to a new company code, Account currency and Sort key must always be maintained.
• G/L Account Fields (Chart of Accounts Level):
  • Group account number
  • Short text
  • Account group
• Open Item Management: A G/L account can only switch off open item management if it has not been posted to.
• Currency Type Assignment: Currency types are assigned at the Ledger level.
• Leading Ledger Property: The leading ledger does not derive values from other ledgers; instead, other ledgers derive from it.
• G/L Account Types in P&L Statement: Values shown in the P&L statement are derived from Non-operating Expense or Income, Primary Costs or Revenue, and Secondary Costs G/L account types.

Document Splitting

Document splitting ensures that a complete financial statement can be generated for entities like segments or profit centers. If document splitting is activated, the general ledger view may show more items than the entry view due to the detailed splitting information.

4. Asset Accounting (FI-AA)

FI-AA manages fixed assets from acquisition to retirement, integrating closely with the General Ledger.

Purchase Order Accruals

Relevant use cases for purchase order accruals in SAP S/4HANA include:

• Purchase of services
• Purchase of consumable materials

Technical Clearing Account for Integrated Asset Acquisition

• This account is posted in scenarios like:
  • Direct asset acquisition posting with a vendor invoice (not linked to a purchase order).
  • Valuated goods receipt on a purchase order with an asset as account assignment.
• Prerequisites for Definition:
  • The account is a balance sheet account.
  • The account is defined as a reconciliation account for fixed assets.
• Definition Levels: Can be defined at the Account determination and Chart of Accounts levels.

Depreciation

• Unplanned Depreciation: Posting is done in FI-AA in real time and in FI-GL once the depreciation posting program has run.
• Depreciation Area 01 Characteristics:
  • Cannot take over values from other areas.
  • Must always post in real time.
• Posting Depreciation Costs to Two Cost Centers: Assign a real internal order in the asset master data which you settle periodically to two cost centers.
• Balance Carry Forward Error (Asset-related): An error log might indicate incomplete asset master records or that depreciation has not been posted completely.
• Parallel Currency Depreciation Area: For a parallel currency, the depreciation area typically does not post to G/L.

Asset Account Assignment

• Statistical Account Assignment for Cost Postings to an Asset: A Profit center is only a statistical account assignment.
• Vendor Invoice for Asset Acquisition (without PO): Generates one document per accounting principle and one document for all accounting principles.
• WBS Element Activation (with "balance sheet" and "identical" active):
  • The WBS Element is available for input in the asset master record.
  • The WBS Element cannot be changed in the asset master record once the asset is capitalized.
• Posting Depreciation to a Different Cost Center: Achieved by creating a substitution in Financial Accounting line items.

Legacy Data Transfer (via Transaction AS91)

Used for the creation of master data.

Segment Reporting Activation

Consequences of activating segment reporting:

• The segment appears in the screen layout for asset master data.
• The segment appears in the additional account assignment configuration.

FI-AA Account Determination Levels

FI-AA account determination is defined at the:

• Chart of depreciation
• Chart of accounts

5. Period-End Closing Activities

Efficient period-end processing is crucial for accurate financial reporting.

Foreign Currency Valuation

• Items Taken into Account:
  • Balance valuation on items for balance sheet accounts not defined as open item management.
  • Line item valuation for balance sheet accounts defined as open item management.
• Role of Valuation Method:
  • Define the document type for the valuation posting.
  • Define the valuation procedure.
  • Determine the exchange rate type.
• Determining Relevant Accounting Principle: The system determines the relevant accounting principle via the valuation area.
• Posting Valuation Differences (for period-end reports and reversals): The system uses an Adjustment G/L account for foreign currency.

SAP Intercompany Matching and Reconciliation (ICMR)

• Purpose:
  • To generate automatic posting to correct intercompany discrepancy.
  • To highlight and solve intercompany data discrepancy triggering a workflow.
• Definition:
  • It is a solution that facilitates transaction matching between systems in Central Finance.
  • It is a solution that can be integrated with Group Reporting.
• Matching Results Location: Matching results are seen in an application specific table (ICADOCM).

Financial Statement Reporting

Issues with calculated net profit in a financial statement report can be caused by:

• Adding an account to the wrong node, including it in the assets section.
• Having accounts that are not assigned in the financial statement version.

Fiscal Year Variant

The fiscal year variant defines:

• The number of posting periods.
• The start and end date of posting periods.

Consolidation Preparation

The Company/Trading Partner object is used to directly support the preparation for consolidation.

Corporate Group Consolidation Scenario

If a corporate group has 15 legal entities (10 in S/4HANA, 5 in legacy systems) and wants to prepare a consolidated financial report, 5 companies should be defined in the SAP S/4HANA system to accommodate the consolidation scenario, representing the entities outside the S/4HANA system.

Group Chart of Accounts Assignment

The group chart of accounts is assigned to the Operating chart of accounts.

6. Accounts Payable and Receivable

Managing customer and vendor accounts efficiently is critical for cash flow and vendor relationships.

Noted Items

Characteristics specific to noted items:

• They can be accessed by the payment program and the dunning program.
• They are managed as open items on customer and vendor accounts.
• They generate statistical postings.

For example, recording a customer guarantee of EUR 10,000 results in Two statistical line items.

Payment Run Prerequisites (Multiple Company Codes)

For multiple company codes in a single payment run, they must have the same configuration for payment transactions.

Clearing Customer Open Items

To undo a clearing action for a customer open item, the available options are:

• Reset and reverse the clearing document.
• Reset the clearing document.

3-Way Match (Procurement)

The 3-way match in SAP S/4HANA for procurement transactions works as follows:

• The invoice needs to be created in reference to the goods receipt.

Correspondence Type Assignment

The print program and its variant can be assigned to the correspondence type at the Client and Company Code levels.

Credit Memo (Financial Accounting)

Payment terms may be ignored for credit memos entered in Financial Accounting if:

• The credit memo was created without reference to an invoice.
• The due date determined based on the entered payment terms is in the past.

Regrouping Receivables and Payables

To configure regrouping of receivables and payables, you need to define the Sort Method.

Reason Code (Accounts Receivable)

The reason code in Accounts Receivable can control:

• The account where a residual item is posted.
• The type of payment notice sent to a customer.
• The exclusion of disputed residual items from credit limit checks.

Dunning Configuration

• Mandatory Steps:
  1. Maintain the parameters of the dunning program.
  2. Schedule the dunning run.
  3. Start the dunning printout.
• Dunning Level Parameters: You can configure Days in arrears and Payment deadline at the dunning level.
• Reversal with Different Date: To allow a reversal with a date different from the original document for a posted document in a closed period, configure the Reversal reason.

Incoming Payment with Residual Item

Consequences of an incoming payment from a customer with a residual item for a payment difference:

• The residual item becomes a new receivable.
• The original document and the payment are cleared.

Payment Method Definition (Company Code Level)

On the company code level, you define the following for payment methods:

• Foreign currency allowed.
• Minimum and maximum payment amounts.

COGS Posting (Standard Sales Process)

The Cost of Goods Sold (COGS) posting is generated in Financial Accounting when you Do PGI (Post Goods Issue).

Baseline Date (Invoice Entry)

When entering an invoice that needs to be paid, the system must determine the Baseline date.

Posting Period Variant Restrictions

Postings can be restricted using the posting period variant at the G/L account and Supplier account levels.

7. SAP Technology and Integration

SAP S/4HANA leverages modern technologies for integration and user experience.

SAP Fiori Launchpad

Pages are assigned to users on the SAP Fiori Launchpad via spaces assigned to business roles which are assigned to users.

SAP Fiori Apps (Database Independent)

SAP Fiori apps that can run on any database include:

• Make Bank Transfers
• Manage Chart of Accounts

SAP Business Technology Platform (BTP)

Features of SAP BTP include:

• It provides data management and analytics.
• It supports application development and integration.

Intelligent Enterprise Components

The Industry Cloud component allows customers to discover and deploy vertical solutions from SAP and partners.

SAP Business Network

The SAP Business Network builds on solutions like:

• Contingent Workforce
• Travel
• Procurement

Clean Core Integrations

• Recommended API Types: SAP recommends using SOAP and OData for clean core integrations.
• Exploring Released APIs: The SAP Business Accelerator Hub can be used to explore released APIs.
• Guiding Principles for Clean Core Operations:
  • Establish regular housekeeping tasks and procedures.
  • Establish an organizational structure, technical foundation, and transformation methodology for clean core.
  • Integrate clean core practices in the end-to-end value process chain.

ABAP Cloud-Native Development Model

The ABAP RESTful Application Programming Model can be used for ABAP cloud-native development.