SAP Updated C_TS422_2023 Exam Questions and Answers by leonidas

In SAP S/4HANA Advanced Planning (Production Planning and Detailed Scheduling, PP/DS), a production planning run (transaction /SAPAPO/CDPSB0 or heuristics) generates supply elements to cover demand. Possible results include:

Planned order(A): PP/DS creates planned orders (visible in /SAPAPO/RRP3) for in-house production to meet requirements (e.g., sales orders, dependent requirements). These are detailed with exact timings and can be converted to production orders later (e.g., via /SAPAPO/PROD).

Scheduling agreement schedule line(B): For external procurement with a scheduling agreement (maintained in ME31L), PP/DS generates schedule lines (visible in ME38 or /SAPAPO/RRP3) to request delivery from vendors, aligning with precise scheduling needs.

Production order(C) is not a direct result—PP/DS creates planned orders, which are then converted to production orders manually or via a separate process (e.g., CO41).Purchase order(D) is possible in classic MRP for external procurement, but PP/DS typically generates purchase requisitions or schedule lines, not direct POs. This is per SAP’s PP/DS planning output documentation.

In SAP S/4HANA, acollective orderis a network of production orders where a top-level order (for a finished product) is directly linked to subordinate orders (for assemblies), created automatically via special procurement key 52 (material master, MRP 2 view). The advantages include:

To perform availability checks across the entire collective order(A): When a collective order is created (e.g., via CO01 with "Collective Order" indicator), the system performs a material availability check (configured in OPL8) across all levels of the order hierarchy. This ensures components are available for the entire structure before release, reducing partial shortages.

To post confirmations for the entire collective order(D): Confirmations (e.g., via CO11N or CO15) for the top-level order can automatically trigger goods movements (goods receipt for the finished product, goods issue for components) across all linked orders. This streamlines shop floor processing by consolidating confirmations.

To coordinate orders in the planning board(B) is not specific to collective orders—it’s a general PP/DS or capacity planning feature (e.g., DS Planning Board), not an inherent advantage.To show the flow of batches(C) is possible via batch tracing (e.g., MB56), but it’s not a unique benefit of collective orders, which focus on production linkage, not batch visibility. This aligns with SAP’s collective order documentation.

In SAP S/4HANA Demand Management,planned independent requirements(PIRs) represent forecasted demand for finished products. Their consumption by other requirements (e.g., sales orders) depends on settings in the material master:

Requirements type(C): This is determined by the planning strategy and specifies the type of PIR (e.g., VSF for forecast-based planning). It is maintained in the material master (MRP 3 view) or derived from the planning strategy. The requirements type dictates how PIRs are consumed (e.g., by sales orders) and is visible in demand management (transaction MD61). For example, requirements type "LSF" (from strategy 40) allows consumption by sales orders.

Planning strategy(D): Defined in the material master (MRP 3 view, field: Strategy Group), the planning strategy (e.g., 40 - Planning with Final Assembly) controls whether and how PIRs are consumed. For instance, strategy 10 (Make-to-Stock) does not allow consumption, while strategy 40 reduces PIRs based on incoming sales orders within the consumption period.

Order type(A) relates to production or sales order processing, not PIR consumption logic.Requirements profile(B) is not a standard SAP term in this context and does not directly influence consumption (it may refer to custom settings, but it’s not part of SAP’s standard demand management). This is detailed in SAP’s official Demand Management documentation.

In SAP S/4HANA, the item category in a BOM (transaction CS01/CS02, field: Item Category) classifies components and determines their handling in production and procurement. Standard item categories include:

Variable-size item(A): Item category "R" (Variable-Size Item) is used for components with dimensions (e.g., sheets, pipes) where quantity is calculated based on size data (entered in the Variable-Size Item Data tab). It’s common in manufacturing for materials cut or sized during production.

Preliminary item(C): Item category "V" (Preliminary Item) is a placeholder for components not yet fully specified (e.g., during design phase). It allows BOM creation to proceed, with details added later, and is valid for planning purposes.

Work item(B) is not a standard BOM item category—"L" (Stock Item) or "N" (Non-Stock Item) might apply to work-related components, but "Work Item" isn’t a defined term.WBS item(D) (Work Breakdown Structure, category "W") relates to Project Systems (PS) BOMs, not standard production BOMs in PP, requiring PS integration. This is per SAP’s BOM item category definitions.