Free SAP C_TS422_2023 Practice Exam with Questions & Answers | Set: 2

In SAP S/4HANA PP/DS, theInsert Operationscheduling mode (configured in the strategy profile, e.g., /SAPAPO/CDPSC11) is a finite scheduling option that inserts a new operation into an existing schedule while respecting capacity constraints. Effects include:

Scheduling of an operation takes place as close as possible to the desired date(A): The system schedules the operation (e.g., in /SAPAPO/PPDS_DISP) at the earliest feasible time slot near the desired date (specified in the order or planning parameters), considering finite capacity and resource availability.

Neighboring operations can be moved in both directions in order to create a slot(C): To accommodate the new operation, the system shifts existing operations forward or backward (within tolerances defined in the strategy profile), ensuring a feasible slot without overloading the resource.

Sequencing on multi-activity resources(B) isn’t automatically updated—this requires a separate heuristic (e.g., /SAPAPO/HEUR_SEQUENCE).Changes in the complete collective order(D) don’t occur automatically—collective orders require explicit rescheduling of linked orders, not an inherent feature of Insert Operation. This is per SAP’s PP/DS scheduling documentation.

In SAP S/4HANA, the MRP planning file (table MDVM, visible via MD05) tracks changes that trigger MRP to re-evaluate a material’s planning situation. Entries are created when:

Changing the procurement type in the product master(C): The procurement type (material master, MRP 2 view, field: Procurement Type) determines whether a material is produced in-house ("E"), procured externally ("F"), or both ("X"). Changing it (e.g., via MM02) affects how MRP generates planned orders or purchase requisitions, so an entry is added to the planning file (e.g., NETCH or NETPL indicator) to prompt recalculation.

Changing the stock in inventory management(D): Any stock change (e.g., goods receipt via MIGO, goods issue via MB1A) updates the available stock (MD04). This triggers an MRP planning file entry because it alters the net requirements calculation, requiring MRP (MD01/MD02) to reassess supply versus demand.

Changing the delivery address in transportation management(A) affects logistics execution (e.g., shipment documents), not MRP planning directly—no entry is created.Changing the storage bin in warehouse management(B) (e.g., via LT10) is a WM-level movement that doesn’t impact MRP unless stock quantity changes, which falls under (D). This is per SAP’s MRP planning file logic.

In SAP S/4HANA, planning strategies (material master, MRP 3 view, Strategy Group) determine how production aligns with demand. The scenario describes a pure make-to-stock (MTS) environment where goods are produced based on forecasts (planned independent requirements, PIRs) and held in stock, with excess customer orders not affecting the production program:

Make-to-stock production (10)(D): Strategy 10 uses PIRs (entered via MD61) to drive production, and finished goods are stocked (goods receipt via CO15). Sales orders (VA01) are fulfilled from stock, and excess demand beyond the forecast does not trigger additional production or consume PIRs—it’s handled separately (e.g., via backorder or rejection). Thisensures the production program remains stable, based solely on the forecast.

Assembly processing with production orders (82)(A) is a make-to-order (MTO) strategy tied to sales orders, not forecasts.Planning with final assembly (40)(B) allows sales orders to consume PIRs, potentially impacting production if demand exceeds the forecast.Planning without final assembly (50)(C) plans subassemblies based on PIRs, with final assembly triggered by sales orders, also affecting production. Strategy 10 meets the requirement per SAP’s MTS planning logic.

In SAP S/4HANA, MRP determines whether to createplanned orders(for in-house production) orpurchase requisitions(for external procurement) based on specific master data settings in the material master. Theprocurement type(A), maintained in the MRP 2 view (field: ProcurementType), is a key determinant. For example, procurement type "E" (In-house production) triggers planned orders, while "F" (External procurement) generates purchase requisitions, and "X" (Both) allows MRP to decide based on additional settings like quotas.

Thematerial type(B), defined during material creation and linked to configuration (Logistics - General > Material Master > Basic Settings > Define Material Types), also influences this decision indirectly. For instance, material types like "FERT" (Finished Goods) are typically produced in-house, favoring planned orders, while "ROH" (Raw Materials) are procured externally, favoring purchase requisitions.MRP type(C) controls whether MRP runs (e.g., "PD" for MRP planning), but it does not directly determine the order type.MRP group(D) groups materials for planning parameters but does not directly dictate planned orders versus purchase requisitions.

In an SAP S/4HANA Cloud brownfield project,clean core principlesemphasize minimizing customizations, leveraging standard processes, and ensuring extensibility. SAP Signavio tools support process remodeling:

SAP Signavio Process Governance(C): This tool (part of the Signavio suite) enables process execution and monitoring, ensuring compliance with redesigned standard processes. It supports workflow automation and governance, aligning remodeled processes with clean core by enforcing best practices and reducing custom code.

SAP Signavio Process Manager(D): This tool is used for process modeling and documentation (e.g., BPMN 2.0). It allows the customer to redesign existing processes visually, map them to S/4HANA standard capabilities, and identify deviations, supporting a clean core approach by aligning with SAP’s reference processes.

SAP Signavio Process Insights(A) provides analytics on current process performance (e.g., bottlenecks), not remodeling.SAP Signavio Process Intelligence(B) focuses on process mining and data-driven insights, not direct remodeling. This is per SAP’s Signavio and clean core documentation.

Material Requirements Planning (MRP) in SAP S/4HANA calculates net requirements to determine material shortages or surpluses by comparing the available stock and scheduled receipts against requirements. During this calculation, MRP considers existingproduction orders(A) because they represent firm commitments to produce materials, and their quantities directly influence the availability of components and finished goods. Similarly,planned orders (firmed)(B) are included as they are confirmed planning proposals that have been manually or automatically fixed, ensuring they are treated as reliable supply elements in the net requirement calculation.

Planned orders (unfirmed)(C) are not considered firm receipts because they are still tentative and subject to change during subsequent MRP runs, so they are excluded from the net calculation unless firmed.ATP (Available-to-Promise) quantities(D) are used in availability checks for sales orders, not directly in MRP’s net requirement calculation, which focuses on stock and scheduled receipts rather than promise-based quantities. This aligns with SAP’s MRP logic as outlined in the SAP S/4HANA Production Planning documentation, emphasizing firm supply elements.

Engineering Change Management (ECM) in SAP S/4HANA (transaction CC01/CC02) manages changes to objects like BOMs, routings, and materials with a structured process:

To save multiple changes for an object(C): ECM allows multiple changes (e.g., to a BOM’s components) to be grouped under one change number (field: Change Number in CS01). These changes are saved and applied together on a specified date (Valid From), ensuring coordinated updates across objects.

To monitor document object changes(D): ECM tracks changes to objects (e.g., materials, BOMs) linked to a change number, providing an audit trail (transaction CC03, History tab). This monitors who changed what and when, supporting compliance and traceability.

To monitor document table changes(A) is vague—“document” likely means BOM or routing, but ECM focuses on object changes, not table-level monitoring (e.g., database logs).To enable integration into a sales order(B) is incorrect—ECM integrates with production or procurement, not directly with sales orders (VA01). This is per SAP’s ECM functionality.

Thelow-level codein SAP S/4HANA (visible in MD04 or calculated during MRP) indicates the deepest level at which a material appears in any BOM across all products, starting from 000 (finished goods) downward. Its key features are:

To determine how costs are rolled up by product costing(B): In Product Costing (CO-PC), the low-level code ensures costs are calculated bottom-up, starting with the lowest-level components (e.g., raw materials) and rolling up through assemblies to the finished product (transaction CK11N). This guarantees accurate cost aggregation.

To determine the sequence in which materials are planned in MRP(C): During MRP (MD01/MD02), the system plans materials in ascending order of low-level codes (lowest first), ensuring dependent requirements for lower-level components are calculated before higher-level assemblies, avoiding planning gaps.

Priority of alternative components in ATP(A) is managed by BOM alternative item strategies (e.g., 100% check), not low-level codes.Use of sub-items in BOM(D) is defined by item categories (e.g., "R"), not influenced by low-level codes. This is per SAP’s planning and costing logic.

In SAP S/4HANA, an operation withDispatchedstatus (set in CM21 or PP/DS after scheduling) is assigned a fixed time slot on a work center. Options for rescheduling include:

You can reschedule the operation using finite scheduling in a planning table(C): In the capacity planning table (CM21) or PP/DS Planning Board (/SAPAPO/CDPS0), you can manually drag-and-drop or use heuristics to reschedule a dispatched operation, respecting finite capacity constraints (work center, CR02, "Relevant to Finite Scheduling").

You can reschedule the operation in the Manage Work Center Capacity app(D): This Fiori app (SAP GUI equivalent: CM25) allows planners to adjust dispatched operations’ schedules by shifting them within available capacity slots, maintaining finite scheduling rules and updating the operation’s time.

Lead time scheduling(A) (e.g., in CO02) recalculates the entire order’s basic dates, not individualdispatched operations—it’s not used post-dispatch.Infinite scheduling in a planning table(B) (e.g., ignoring capacity) isn’t typical for dispatched operations, which are already capacity-constrained. This is per SAP’s dispatching options.

In SAP S/4HANA, MRP can be configured to exclude certain materials from planning runs to optimize processing or reflect specific business needs. One method is to use aspecific material status(B), maintained in the material master (e.g., under the MRP view). A status such as "Blockedfor Procurement/Production" (configured in Customizing under Logistics - General > Material Master > Settings for Key Fields > Define Material Statuses) prevents the material from being planned in MRP, effectively excluding it from the run.

Another method is to assign aspecific MRP type(D), such as "ND" (No Planning), in the material master (MRP 1 view). This MRP type instructs the system not to generate requirements or planned orders for the material, excluding it from MRP processing.Using a specific MRP list(A) is not a valid exclusion method, as the MRP list is an output of the MRP run, not a control mechanism. Similarly,using a specific material group(C) does not inherently exclude materials from MRP, as material groups are for classification and reporting, not MRP control. These options align with SAP’s standard MRP configuration settings.