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, changing the material type (transaction MMAM) is restricted if stocks, reservations, or purchasing documents exist, but it’s allowed under specific conditions:

The quantity and value updates are the same(A): The old and new material types must have identical quantity and value update settings in their valuation areas (configured in OMS2, Material Type Customizing). For example, both must update quantity and value (e.g., "FERT" to "HALB"), or neither (e.g., "NLAG" to "DIEN"). If these differ, the change is blocked due to inconsistencies in stock valuation.

The same base unit of measure is used(C): The base unit (material master, Basic Data 1 view) must remain unchanged between material types. Changing it (e.g., from "PC" to "KG") would invalidate existing stock or document quantities, so the system requires consistency to allow the type change.

The same batch management level(B) (e.g., plant or material level, configured in OMCT) is not a strict requirement—batch settings can differ as long as other conditions are met.The same account category(D) (e.g., General Ledger account determination) influences posting but isn’t a prerequisite—account assignment can be adjusted post-change. This is per SAP’s material type change rules.

In SAP S/4HANA,midpoint scheduling(used in capacity planning, e.g., CM21, or PP/DS) schedules operations around a fixed midpoint (e.g., a critical operation), adjusting other operations forward or backward. Thereduction strategy(configured in Customizing, transaction OPU3, or work center CR02, Scheduling tab) reduces certain interoperation times to compress the schedule when dispatching:

Queue time(A): Defined in the routing (CA01, Interoperation Times tab, field: Queue Time), this is the buffer time before an operation starts. The reduction strategy (e.g., Level 1 to 6 in OPU3) can reduce queue time progressively (e.g., by percentage or to a minimum), allowing tighter scheduling.

Move time(C): Also in the routing (Interoperation Times tab, field: Move Time), this is the transport time between work centers. The reduction strategy can shorten move time to fit operations within capacity constraints, optimizing the overall schedule.

Teardown time(B) (routing, Standard Values, e.g., Teardown Time) is part of the operation’s base duration, not an interoperation time, so it’s not reduced by the strategy—it’s fixed unless manually adjusted.Setup time(D) (Standard Values) is similarly operation-specific and not typically reduced by interoperation-focused strategies. This is per SAP’s scheduling and reduction logic.