C_TS422_2023 Exam Dumps : SAP Certified Associate - SAP S/4HANA Cloud Private Edition, Production Planning and Manufacturing

In SAP S/4HANA PP/DS, theFinite Scheduling with Reversestrategy (configured in the strategy profile, transaction /SAPAPO/CDPSC11) schedules operations backward from a fixed end date, respecting finite capacity. To allow scheduling in the past (e.g., before today’s date):

Specify a negative offset time(A): In the strategy profile (Detailed Scheduling tab, field: Scheduling Offset), a negative value (e.g., -2 days) shifts the scheduling reference point into the past. This allows operations to be scheduled before the current date, accommodating scenarios where late planning or historical adjustments are needed, while still respecting capacity constraints.

Negative opening period(B) isn’t a standard PP/DS parameter—it’s a production order term (MRP 2 view) for order start buffers, not scheduling control.Negative planning horizon(C) (Planning Horizon in /SAPAPO/CDPSC11) defines the future planning scope, not past scheduling.Negative PP/DS horizon(D) refers to the PP/DS planning horizon (Customizing), which limits planning scope forward, not backward. This is per SAP’s PP/DS scheduling configuration.

In SAP S/4HANA,co-productsandby-productsare outputs of a production process, but they differ in purpose, valuation, and system handling:

Only co-products have movement type 101(C): Co-products are intentionally produced alongside the main product and are goods receipted into inventory using movement type 101 (transaction MIGO or CO11N confirmation) as part of the production order. This reflects their status as primary outputs with planned quantities in the BOM (marked with a negative quantity and co-product indicator in CS01). By-products, conversely, use movement type 531 for goods receipt, as they are secondary outputs.

Only co-products appear in the process or production order settlement rule(D): Co-products are included in the settlement rule of the production order (visible in CO02, Settlement Rule) because their costs are apportioned based on apportionment structures (e.g., equivalence numbers in the material master, MRP 2 view). By-products do not appear in the settlement rule; their costs are typically offset against the main product via a cost credit (configured in the BOM).

Only co-products have non-zero inventory valuation(A) is incorrect—by-products can also have inventory valuation (e.g., standard price), though often lower.Only co-products have movement type 531(B) is false—531 is specific to by-products, not co-products. This aligns with SAP’s co/by-product handling in production.

In SAP S/4HANA,lead time schedulingfor a production order (e.g., in CO01, Scheduling Type: Lead Time Scheduling) calculates detailed operation dates using routing data and buffers. Relevant time elements include:

Float after production(C): Defined in the material master (MRP 2 view, field: Float After Production) or scheduling margin key (Customizing, OPPT), this buffer time after the last operation ensures flexibility before the order’s end date (e.g., for quality checks), extending the total lead time.

Setup time(D): Maintained in the routing (CA01, Standard Values, field: Setup Time), this is the time to prepare the work center for an operation. It’s included in the operation duration (calculated via work center formulas, CR02), directly impacting the lead time schedule.

Opening period(A) (MRP 2 view) is a buffer before production starts, relevant for order release, not lead time scheduling within the order.Total replenishment lead time(B) (MRP 2 view) is a high-level estimate for MRP, not detailed operation scheduling. This is per SAP’s lead time scheduling rules.