C_TS422_2023 Questions and Answers

In SAP S/4HANA, a material availability check ensures components are available before production proceeds. This check can be triggered automatically:

By order release(C): When a production order is released (transaction CO02 or mass release via CO05N), the system can perform an availability check based on settings in the order type-dependent parameters (Customizing: Production > Shop Floor Control > Define Order Types). The "Availability Check" field (e.g., "2 - Check at Release") triggers this automatically, ensuring materials are reserved or shortages are flagged.

By mass processing(D): Using transaction COHV (Mass Processing of Production Orders), planners can execute availability checks for multiple orders simultaneously. The function "Check Material Availability" can be scheduled or run manually, automating the process across orders.

By capacity planning(A) focuses on work center capacity, not material availability.By order confirmation(B) may trigger a check for remaining quantities, but it’s not a standard automatic trigger point—it’s more relevant for backflushing or goods issue. This is outlined in SAP’s production order management documentation.

In SAP S/4HANA PP/DS,standard heuristicsare predefined algorithms (e.g., SAP_PP_002 for planning standard lots) executed in the planning run (/SAPAPO/CDPSB0) or interactively (/SAPAPO/RRP3). Their purpose is:

To solve planning problems for defined objects(C): Heuristics address specific planning tasks for objects like materials, resources, or orders. For example, SAP_PP_002 creates planned orders to cover shortages, SAP_PP_020 sequences operations, and SAP_PP_007 adjusts schedules—each solving a distinct problem (e.g., demand coverage, capacity conflicts) based on defined parameters.

Automate material movements in staging(A) is handled by WM or Kanban, not PP/DS heuristics.Set default values in production master data(B) is a master data maintenance task (e.g., MM02), not a heuristic function.Optimize costs and times(D) is possible with optimization tools (e.g., PP/DS Optimizer), not standard heuristics, which focus on rule-based planning. This is per SAP’s PP/DS heuristic documentation.

In SAP S/4HANA, theplanning table for repetitive manufacturing(transaction MF50) is a tool for managing production quantities and schedules in a repetitive production environment. Planners can:

Change the assignments of production quantities to production lines(A): In MF50, planners can reassign planned production quantities (e.g., run schedule quantities) from one production line (defined in the production version, MRP 4 view) to another within the same material, adjusting the distribution based on capacity or availability (visible in the "Assignment" view).

Reschedule and deallocate operations(D): Planners can reschedule production quantities to different dates (e.g., drag-and-drop in the graphical view) or deallocate them from a line (e.g., by setting quantities to zero or removing assignments), providing flexibility to adapt to changes in demand or capacity.

Create new production quantities(B) is typically done via demand management (MD61) or MRP, not directly in MF50, which adjusts existing plans.Dispatch operations to work centers(C) applies to discrete manufacturing (e.g., in CM21 or PP/DS), not repetitive manufacturing, where operations are tied to production lines in the planning table. This is per SAP’s repetitive manufacturing documentation.

In SAP S/4HANA repetitive manufacturing, confirming a finished product (e.g., via transaction MFBF) triggers default actions based on the REM profile (Customizing, OSP2):

Post the goods receipt for the finished product(A): When saving a confirmation (MFBF,Backflush tab), the system posts a goods receipt (movement type 101) for the finished product into stock (e.g., unrestricted use), assuming backflushing is active in the REM profile (field: Backflush Mandatory).

Reduce run schedule quantities(B): The confirmed quantity reduces the openrun schedule quantities(planned orders in MD04 or MF50), aligning the planned production with actual output to prevent overproduction.

Update statistics for the Business Information Warehouse(D): Confirmation data (e.g., quantity, time) updates statistical tables (e.g., S031, S032) for reporting in SAP BW or embedded analytics, providing insights into production performance (enabled by default in standard settings).

Post production costs to the planned order(C) is incorrect—costs are posted to aproduct cost collector(KKF6N) in REM, not planned orders, based on the REM profile’s costing settings.Create associated capacity requirements(E) occurs during planning (e.g., MRP), not confirmation—capacity is consumed, not created, at this stage. This is per SAP’s REM confirmation process.

Planning withplanned independent requirements(PIRs) in SAP S/4HANA (entered via MD61) for finished materials offers benefits in a make-to-stock or forecast-driven environment:

Reduced delivery times(A): By planning PIRs in advance (e.g., strategy 10 or 40), production can start before sales orders arrive, ensuring finished goods are available in stock. This shortens the time between order receipt and delivery, improving customer service levels.

Reduced times for final assembly(B): In strategies like 40 (Planning with Final Assembly), PIRs trigger procurement and production of components early. When sales orders arrive, only final assembly is needed, reducing the overall lead time for completion.

Option to forecast planning for production resources(C) is a byproduct of capacity planning (e.g., CM01), not a direct benefit of PIRs—PIRs focus on material demand.Option to use make-to-order production(D) contradicts PIRs, which are for make-to-stock or forecast-based planning (e.g., strategies 10, 40), not MTO (e.g., strategy 20). This is per SAP’s demand management benefits.

In SAP S/4HANA repetitive manufacturing,reporting point confirmation(e.g., via transaction MFBF) tracks progress at specific milestones. Prerequisites include:

Activating the reporting point backflush in the work centers(B): The work center (transaction CR02, Basic Data tab, field: Backflush) must have backflushing activated (e.g., "Reporting Point Backflush" indicator). This enables goods movements (e.g., component consumption) at reporting points during confirmation, a key REM feature.

Defining the operations as reporting points using the control key(D): In the rate routing (CA21), operations designated as reporting points require a control key (field: Control Key) with the "Reporting Point" indicator checked (configured in OPJ8). This marks the operation as a confirmation milestone (e.g., RP01 control key).

Order-dependent parameters(A) apply to discrete manufacturing (OPL8), not REM, where the REM profile (OSP2) governs backflushing, not reporting points specifically.Defining work centers in the routing(C) is standard but insufficient without the control key specifying reporting points. This is per SAP’s REM confirmation process.

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 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 an SAP S/4HANA Cloud Greenfield project,clean corefocuses on a standardized, extensible system with high-quality data. Key aspects for data quality include:

Efficiency(A): Clean core principles prioritize efficient processes and data structures, minimizing customizations that could degrade performance or complicate upgrades. Efficient data quality ensures streamlined operations (e.g., fast MRP runs) and leverages standard SAP functionalities effectively.

Stability(D): Maintaining a stable core with consistent, reliable data (e.g., master data integrity in MM03) prevents disruptions during updates or extensions. Stability ensures the system remains robust and predictable, a cornerstone of clean core in a Greenfield implementation.

Accuracy(B) is critical for data quality in general (e.g., correct BOM quantities), but clean core emphasizes systemic qualities over content accuracy, which is assumed.Timeliness(C) matters for operational data (e.g., stock updates), but it’s less tied to clean core’s structural focus. This is per SAP’s clean core guidelines.

A production version in SAP S/4HANA (material master, MRP 4 view) links a BOM and routing for production. For it to be valid and consistent:

The deletion flag must NOT be set for the bill of material (BOM) or the routing(A): If the BOM (CS02) or routing (CA02) has a deletion flag, it cannot be used in production planning or execution, rendering the production version invalid. This is a basic integrity check in SAP.

The assigned routing and bill of material (BOM) must be valid in the entire validity period(C): The production version’s validity period (e.g., Valid From/To dates) must align with the BOM and routing’s validity. If either expires or is invalid during the version’s timeframe, the system cannot use it (checked in MRP or order creation).

The lot size range must be within the lot size range of the assigned routing(E): The production version’s lot size (MRP 4 view) must fall within the routing’s lot size range (CA02, header data). If the order quantity exceeds this range, the version is inconsistent for planning.

The consistency check(B) (transaction C252) is a manual validation tool, not a requirement for validity—it’s optional.Same validity period(D) is not mandatory; overlapping validity is sufficient, as long as both are valid when needed. This is per SAP’s production version documentation.

The Alert Monitor in SAP S/4HANA PP/DS (transaction /SAPAPO/AMON1) highlights planning issues. Configuration steps include:

Assign the alert profile to the overall profile(A): In Customizing (/SAPAPO/ALERT_PROFILE), you define an alert profile (e.g., specifying alert types like capacity overload) and assign it to an overall profile (e.g., in /SAPAPO/CDPSC11). This links alert settings to planning applications (e.g., Planning Board).

Create an object selection variant for production-planning-related alerts(D): You create a variant (e.g., in /SAPAPO/AMON_SETTING) to filter objects (e.g., materials, resources) for which alerts are monitored, tailoring it to production planning issues (e.g., late orders, shortages).

Assign the overall profile to the authorization profile(B) is incorrect—overall profiles link to planning, not authorization (handled via PFCG roles).Object selection variant for ATP categories(C) relates to availability checks, not production planning alerts, which focus on PP/DS issues. This is per SAP’s Alert Monitor setup.

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, a "multiple BOM" refers to alternative BOMs (transaction CS01, field: Alternative) for the same material, allowing different component combinations. Reasons for these variations include:

Manufacturing date(A): Alternative BOMs can have different validity periods (Valid From/To dates in CS01 header). For example, a new BOM might replace an old one due to design changes effective from a specific date, resulting in different components based on when production occurs (checked in MRP or CO01).

Lot size(D): Each alternative BOM can specify a lot size range (CS01, header data, field: Lot Size From/To). Different component combinations might be optimal for small versus large production runs (e.g., bulk packaging for larger lots), leading to distinct BOMs tied to quantity.

BOM header status(B) (e.g., Active/Inactive) controls usability but doesn’t define component combinations—it’s a single status per BOM.BOM component status(C) isn’t a standard field—component relevance is managed via item category or deletion flags, not status, and doesn’t explain multiple BOMs. This is per SAP’s multiple BOM functionality.

In classic MRP within SAP S/4HANA, scheduling agreements can be leveraged to automatically generate schedule lines for external procurement when a material shortage occurs. To enable this, the scheduling agreement must be maintained in thesource listand marked asMRP-relevant(B). This is done in transaction ME01 (Maintain Source List), where the scheduling agreement number is entered, and the "MRP" indicator (field: Source List Usage in MRP) is set to "1" (Relevant for MRP). This ensures MRP recognizes the agreement as a valid supply source.

Additionally, on the initial screen of the MRP run (e.g., transaction MD01 or MD02), you mustset the creation indicator for delivery schedule lines(C) to "1" (Create Schedule Lines). This parameter (field: Create Purchase Reqs) instructs MRP to generate schedule lines directly against the scheduling agreement instead of purchase requisitions. Option A (purchase requisitions) would create requisitions instead of schedule lines, which is not the goal. Option D (quota arrangement) is an alternative sourcing method but not required for scheduling agreements in this scenario.

In SAP S/4HANA Cloud Private Edition, supporting aGood Manufacturing Practice (GMP)compliant production process (common in industries like pharmaceuticals) involves features to ensure traceability, quality, and regulatory adherence:

Digital signature(A): SAP supports digital signatures (configured in Customizing, Cross-Application Components > General Application Functions > Digital Signature) for critical process steps (e.g., order release in CO02 or confirmation in CO11N). This ensures authorized personnel approve actions, meeting GMP requirements for accountability andaudit trails.

Recipe approval(C): In process manufacturing, recipes (process orders use Production Process Models or Master Recipes, transaction C201) require approval (status change, e.g., from "Created" to "Released" via ECM or C202). This ensures only validated production instructions are used, a key GMP compliance step.

Batch record(E): The electronic batch record (EBR, transaction COEBR or integrated in process order management) documents all production details (e.g., materials, quantities, quality checks). It’s mandatory for GMP to provide a complete, auditable history of each batch (configured via process order settings).

Approved resources(B) isn’t a standard SAP term—resources (work centers, CR02) can be quality-checked, but approval is process-driven, not a distinct feature.GMP-compliant flag(D) doesn’t exist as a specific field—GMP compliance is achieved through process controls, not a single indicator. This is per SAP’s GMP support documentation.

In SAP S/4HANA, the goal is to plan in-house production of a semi-finished material using planned independent requirements (PIRs), with those PIRs consumed by dependent requirements from the finished good’s production:

Planning at assembly level (70)(D): Strategy 70 (material master, MRP 3 view, Strategy Group: 70) is designed for subassemblies or semi-finished materials. PIRs are entered for the semi-finished material (MD61), triggering in-house production (planned orders via MRP). When a sales order for the finished good is received, the dependent requirements (from BOM explosion) consume these PIRs within the consumption period (MRP 3 view), aligning production of the semi-finished material with higher-level demand.

Assembly processing with production orders (82)(A) is an MTO strategy tied to sales orders, not PIRs.Planning with final assembly (40)(B) applies to finished goods, where PIRs are consumed by sales orders, not dependent requirements of semi-finished items.Production by lot size (30)(C) focuses on lot-size-based production without consumption logic. Strategy 70 is explicitly designed for this scenario per SAP documentation.

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, dispatching operations (e.g., in CM21 or PP/DS Planning Board) assigns them to work centers. Multiple commitments on the same date indicate overlapping schedules, caused by:

The Finite Scheduling indicator is NOT set in the strategy profile(A): In PP/DS (strategy profile, /SAPAPO/CDPSC11) or capacity planning (OPU5), if finite scheduling isn’t active (e.g., work center CR02, Capacity tab, "Relevant to Finite Scheduling" unchecked), the system schedules operations infinitely, ignoring capacity limits and allowing overlaps on the same date.

The work center has several individual capacities(B): If the work center (CR02, Capacity tab) has multiple individual capacities (e.g., 3 machines, field: No. of Individual Capacities), operations can be scheduled in parallel on the same date, each assigned to a separate capacity, resulting in multiple commitments.

Alternative work centers fully occupied(C) might force scheduling onto one center but doesn’t inherently cause overlaps—it’s a capacity issue, not a scheduling logic flaw.Change Planning Direction indicator(D) (e.g., Forward/Backward in strategy profile) affects sequence, not overlapping commitments. This is per SAP’s scheduling behavior.

In SAP S/4HANA repetitive manufacturing, the production line is represented by a work center, and this is maintained in:

Production version(B): The production version (material master, MRP 4 view, transaction C223) links a material to a specific production line by referencing a work center (via the routing or rate routing). The "Production Line" field explicitly identifies the work center used for repetitive production, tying it to the planning table (MF50).

Routing(D): In repetitive manufacturing, a rate routing (transaction CA21) or standard routing (CA01) defines the operations and assigns the work center (field: Work Center) thatrepresents the production line. This work center is then referenced in the production version for planning and execution.

Production cost collector(A) (transaction KKF6N) collects costs for repetitive production but doesn’t define the work center—it uses the production version’s data.Repetitive manufacturing profile(C) (Customizing, transaction OSP2) controls REM settings (e.g., backflushing), not the specific work center assignment. This is per SAP’s REM master data setup.