P-S4FIN-2021 Sample Questions & Answers

For New Asset Accounting to function correctly, it must be explicitly activated for the company code (transaction FAA_ACTIVATION). If it is not activated, the system may fall back to legacy-like behavior where depreciation is not posted in real-time with asset transactions but requires the periodic AFAB run. The other options relate to configuration details within an already active New AA environment, but the fundamental activation is the most likely root cause for the described system-wide behavior.

The Business Data Toolset (BDT) is the standard, designated framework for extending the Business Partner data model in SAP. It allows developers to add new fields, screens (tabs), and checks to the BP transaction in a modification-free way. Using BDT ensures that custom fields are correctly integrated into the BP architecture, including its APIs and change document logs. Directly appending to standard tables like BUT000 is not supported and can cause system inconsistencies.

ACDOCA, the Universal Journal, is the central table in SAP S/4HANA Finance. It serves as the single line item table for General Ledger, Controlling, Asset Accounting, and Material Ledger, eliminating many previous aggregate and index tables and providing a harmonized, granular data model.

Analytical Fiori apps, particularly Multidimensional Reports, are built on Core Data Services (CDS) views and are designed for complex, real-time data analysis. They provide powerful features like slice-and-dice, drill-down, and visualization capabilities, making them the ideal choice for financial controllers who need to explore and analyze financial data from various perspectives.

This is the optimal solution. Standard non-leading ledgers are correct for the distinct US and German GAAP requirements as they need to store a full set of postings. For management adjustments, an Extension Ledger is perfect. It inherits all data from the leading ledger (0L) without physical duplication and only stores the specific manual adjustment postings. This meets the requirement to minimize the data footprint while allowing for comprehensive management reporting by combining data from 0L and the extension ledger.

The primary purpose of compatibility views is to minimize the disruption to custom code during an S/4HANA conversion. Many legacy tables (like BSIS, BSAS, COEP) have been eliminated. Compatibility views are created with the same names as these old tables. When custom code attempts to read from an obsolete table, the view intercepts the request and reads the corresponding data from the new data model (primarily ACDOCA), ensuring the custom program can run without modification. This provides a transitional path, although SAP recommends adapting the code to read directly from the new tables or CDS views for optimal performance.

This statement is false. While account-based CO-PA is the strategically recommended approach in S/4HANA due to its direct integration with the Universal Journal, costing-based CO-PA is still available. SAP provides the option to run both types in parallel (Combined Profitability Analysis) to leverage the benefits of each. However, for new implementations, account-based CO-PA is heavily favored.

In New Asset Accounting, the integration with the General Ledger is managed through the assignment of depreciation areas to ledger groups. This allows for true parallel valuation, where the values from one depreciation area (e.g., for IFRS) post exclusively to the IFRS ledger group, and values from another area (e.g., for local GAAP) post to the local GAAP ledger group. This replaces the older concept of delta depreciation areas.