C-TS4CO-2023 SAP Practice Questions

The Distribution method is correct because it allocates costs using the original primary cost elements, which is desirable for maintaining cost transparency. Statistical Key Figures (SKFs) are the standard mechanism for defining the tracing factors for such allocations. The number of tickets is a quantifiable measure that should be posted as an SKF of category 'Total values' (category 2) to each receiving cost center. The distribution cycle will then use these SKF values to proportionally allocate the sender's costs. Assessment uses secondary cost elements, which obscures the original cost detail. Manual activity allocation is for direct service consumption, not overhead allocation. Periodic reposting is for correcting initial postings, not for planned allocations.

A side-by-side application on SAP BTP is a recommended clean core approach, especially when dealing with external API calls and logic that changes frequently. It keeps the custom logic completely separate from the S/4HANA core system, ensuring upgrade stability.

Using the 'Custom Logic' Fiori app to implement a cloud-ready BAdI is a valid in-app extensibility method that is part of the clean core paradigm. SAP provides specific released BAdIs for this purpose, which are upgrade-stable. This is suitable for tightly coupled logic that needs to run synchronously within the transaction.

For investment measures managed via internal orders, assigning an investment profile is the key configuration step. The investment profile controls the automatic creation of an associated Asset under Construction (AuC) when the internal order is created. During periodic settlement, costs from the internal order are settled to this AuC. Upon completion of the project, a final settlement is performed from the AuC to the final fixed asset(s). This automates the entire capitalization process in line with standard asset accounting procedures.

The 'Transfer Control' setting within the costing variant is a critical parameter that dictates how the system treats existing cost estimates for lower-level materials during a multi-level costing run. If it's configured to 'Use existing cost estimate if available', and an old cost estimate for the semi-finished good exists (perhaps one created before the routing was complete), the system will not re-explode the BOM and routing for that component. It will simply transfer the cost from the old estimate, which would explain why the labor costs are missing. To fix this, the transfer control should be set to always recost the material, or the existing incorrect cost estimate must be deleted before the new run.

This is the standard SAP best practice. Product Cost by Period using Product Cost Collectors is ideal for repetitive, high-volume manufacturing where costs are analyzed on a periodic basis (e.g., monthly) rather than per individual order. It simplifies period-end closing. Conversely, Product Cost by Order using discrete Production Orders (or Process Orders) is designed for job-order or complex manufacturing where costs must be tracked and analyzed for each specific production lot or order. This provides detailed cost analysis for unique, high-value products like custom machinery.

For event-based WIP to function, it must be explicitly activated at the company code level within the controlling area configuration. If this setting is not active, the system defaults to the traditional period-end WIP calculation process. The results analysis key controls WIP calculation but not the real-time posting mechanism. The settlement profile is relevant for settling the order, not for real-time WIP posting. Business process variants are related to document splitting, not the activation of event-based posting.

The 'Custom Fields and Logic' Fiori app is the standard, upgrade-safe method for in-app extensibility, which is a key pillar of the clean core strategy. This tool allows key users to add custom fields, define value helps (code lists), and even implement custom logic without modifying standard SAP objects. Modifying the data dictionary directly (SE11), using classic BAdIs, or screen variants are considered legacy or less compliant methods that can introduce technical debt and complicate future upgrades.

The valuation variant in SAP Product Cost Planning allows for a prioritized sequence of strategies for material valuation. By setting 'Planned Price 1' as the first strategy and 'Standard Price' as the second, the system will first attempt to find a valid planned price. Only if one is not found will it proceed to the next strategy in the sequence, which is to use the standard price from the material master. This standard configuration achieves the requirement without custom code (user exit) or inefficient processes.

When Profit Center Accounting is active for a controlling area, the system requires a profit center for all relevant postings to ensure a complete balance sheet and P&L at the profit center level. If a profit center cannot be derived from the assigned cost object (like a cost center), the system attempts to post to a 'dummy profit center'. If no dummy profit center is defined in the controlling area settings, the posting will fail with an error. The field status group controls field display at the G/L account level, but the PCA activation is the root cause. Document splitting rules and validation rules are related but secondary to the fundamental PCA activation setting.