Free Practice Questions for SAP C_TS422_2023 Exam

Cost Object Controlling (COC) in SAP S/4HANA for production orders can be configured as order-related (each order is a cost object) or product-related (costs are collected at the product level via a product cost collector). Key considerations include:

In product-related COC, all costs are debited and credited to a product cost collector(B): In this approach (configured via transaction KKF6N or Customizing: Production > Product Cost Controlling > Product Cost Collectors), all production costs (material, labor, overhead) for a material are aggregated on a single cost collector, regardless of individual orders. This simplifies cost tracking for repetitive manufacturing scenarios.

Order-related COC is beneficial in a flexible production environment(D): In flexible or make-to-order production, where each order has unique specifications or costs (e.g., varying BOMs or routings), order-related COC (configured in the order type, OPL8) assigns costs to individual production orders, providing detailed visibility and control.

Product-related COC for co-products(A) is incorrect—co-products typically use order-related COC with a settlement rule to apportion costs, not product-related collectors.In order-related COC, individual production orders do NOT have cost segments(C) is false—each order has its own cost segments (e.g., material, activity) for detailed analysis. This aligns with SAP’s cost controlling documentation.

In SAP S/4HANA’sgraphical planning table(e.g., CM21 or PP/DS Planning Board, /SAPAPO/CDPS0), inserting an operation withforward planning direction(start from a fixed date and schedule forward) at a specific time on a work center with an existing operation:

The new operation is inserted at the desired time; the previously dispatched operation is moved forward(C): With forward scheduling (configured in the strategy profile, e.g., /SAPAPO/CDPSC11, Planning Direction: Forward), the system inserts the new operation at the specified time (e.g., via drag-and-drop). To maintain capacity feasibility, the previously dispatched operation is shifted forward (later in time) to avoid overlap, respecting the work center’s finite capacity (CR02, "Relevant to Finite Scheduling" checked).

Options A and B (leaving the existing operation unchanged) would violate finite scheduling rules, causing overlaps. Option D (moving backward) contradicts forward planning, which schedules from the start point onward. This is per SAP’s dispatching behavior in graphical tools.

Dependent requirements in SAP S/4HANA represent the demand for components or assemblies triggered by the production of higher-level materials. These arecreated on assembly level during the planning run(B) in classic MRP when the system explodes the bill of material (BOM) of afinished product or assembly, calculating requirements based on independent requirements (e.g., sales orders or planned independent requirements) and the BOM structure. This occurs in transactions like MD01/MD02, where MRP generates dependent requirements for all relevant levels.

InAdvanced Planning (PP/DS), dependent requirements arecreated with exact times(C) due to the detailed scheduling capabilities of PP/DS. Unlike classic MRP, which uses daily or weekly buckets, PP/DS schedules requirements with precise timestamps, aligning them with production and procurement timelines. Option A is incorrect because dependent requirements are derived from independent requirements, not created simultaneously. Option D is false, as dependent requirements apply to any BOM structure, not just multilevel ones.

In SAP S/4HANA Cloud Private Edition, thetabular planning tablefor capacity planning (transaction CM22) offers chart-based views to analyze capacity:

Capacity requirements chart(B): This chart (accessible in CM22, graphical view) displays the capacity requirements (e.g., in hours) for operations across work centers over time, showing demand against available capacity to identify overloads or gaps.

Work center capacities chart(D): This chart shows the available capacity of work centers (defined in CR02, Capacity tab) over a time period, allowing planners to compare it with requirements and adjust dispatching (e.g., visible in the capacity overview tab).

Order (pool) chart(A) represents undispatched orders in the pool (e.g., in CM21), not a specific tabular chart type in CM22, which focuses on dispatched operations.Orders (dispatched) chart(C) isn’t a distinct chart—dispatched orders are part of the requirements chart. This is per SAP’s capacity planning table documentation.

In SAP S/4HANA, the validity of a bill of material (BOM) (transaction CS01/CS02) can be restricted as follows:

By plant(B): BOMs are plant-specific by default (field: Plant in CS01). A BOM created for one plant (e.g., 0001) is not valid in another (e.g., 0002) unless copied or extended (CS07), limiting its applicability to the specified plant.

By period(C): The BOM header (CS02) includes "Valid From" and "Valid To" dates, restricting its use to a specific time range. MRP and production orders only select BOMs valid on the required date, allowing versioning or phase-outs (e.g., engineering changes via ECM).

By material type(A) influences which materials can be included in a BOM (e.g., FERT for finished goods), but it doesn’t limit the BOM’s validity—it’s a material attribute.By material status(D) (material master, Basic Data) can block a material from use, but it affects the material, not the BOM’s validity directly. This aligns with SAP’s BOM management rules.

In SAP S/4HANA Cloud Private Edition, alternative items in a BOM (transaction CS01/CS02) allow substitution of components based on predefined strategies. These are maintained in the BOM item data (Alternative Item Group and Strategy fields). The available strategies are:

Manual maintenance(C): This strategy (Strategy field: "1" - Manual Maintenance) allows planners to manually select which alternative item to use during production order processing (e.g., in CO02). The system does not automate selection, relying on user intervention based on availability or preference.

100% check(D): This strategy (Strategy field: "2" - 100% Check) ensures that only one alternative item is used per order, with the system checking availability (via ATP) for 100% of the required quantity. If the first item isn’t fully available, it moves to the next in the priority sequence (Priority field).

First in first out (FIFO)(A) is a stock management concept (e.g., in WM or batch determination),not a BOM alternative item strategy.Simultaneous(B) is not a standard strategy—alternative items are sequential or selective, not used simultaneously unless custom-developed. This aligns with SAP’s BOM functionality documentation.

In SAP S/4HANA process manufacturing (using process orders, transaction COR1), managing production flow for liquid chemicals in physically connected tanks requires:

Resource selection(B): In the master recipe (C201) or process order (COR2), you can define resource selection conditions (e.g., via classification in the resource, CRC1, Basic Data tab). This ensures only suitable tanks (e.g., based on attributes like material compatibility or capacity) are selected for operations, restricting production to physically appropriate resources.

Resource network(D): A resource network (Customizing, Production > Process Order > Master Data > Define Resource Networks) defines the physical connections between resources (e.g., tanks, pipes) in a plant. It specifies valid flow paths (e.g., Tank A to Tank B), ensuring process orders (COR1) schedule operations only on connected tanks, enforced during scheduling or dispatching.

Resource hierarchy(A) (CR21) aggregates capacities for planning, not physical connections.Resource matrix(C) isn’t a standard SAP term—it might refer to custom setups, but it’s not a defined feature for tank connectivity. This is per SAP’s process manufacturing controls.

In SAP S/4HANA Cloud Private Edition, tracking materials with varying characteristics across manufacturing processes and logistics requires:

Batch management(D): Batch management (activated in material master, MM01, General Plant Data/Storage view, field: Batch Management) assigns unique batch numbers to materials (e.g., via MSC1N). It tracks characteristics (e.g., viscosity, color) via classification (CL02, linked in MSC2N), ensuring this information is available in all logistics areas—production (e.g., CO11N goods issue), inventory (MMBE), and sales (VA01 batch determination). This is ideal for materials like chemicals with process-specific traits.

Process order management(A) (COR1) executes production but relies on batch management for characteristic tracking—it’s not the tracking tool itself.Engineering change management(B) (CC01) manages design changes, not runtime characteristics.Quality management(C) (e.g., QA01) inspects batches but doesn’t track characteristics across logistics—batch management underpins it. This is per SAP’s batch management capabilities.

In SAP S/4HANA, a routing (transaction CA01/CA02) defines operation times for production, calculated using standard values and work center formulas. The time elements include:

Wait time(A): Defined in the routing (Operation Details, Standard Values), wait time is the duration an operation must wait after processing before moving to the next step (e.g., drying time). It’s part of interoperation times and affects scheduling.

Processing time(C): Also in the routing (Standard Values, e.g., Machine Time), this is the core time to perform the operation (e.g., machining), calculated via the work center’s processing formula (CR02, Capacity tab). It’s quantity-dependent and critical for lead time.

Setup time(E): Entered in the routing (Standard Values), setup time is the duration to prepare the work center (e.g., tool change), independent of quantity. It’s calculated using the setup formula in the work center and impacts total operation duration.

Float before production(B) is a scheduling margin in the material master (MRP 2 view) or production order, not an operation-specific time in the routing.Pick time(D) is not a standard routing term—it may relate to warehouse processes (e.g., WM), not production operations. This is per SAP’s routing structure.