In SAP S/4HANA PP/DS, user access to specific resources is controlled through the standard authorization concept. Resources can be organized into a "resource group" in the resource master data. This resource group can then be specified in the authorization object CAPORES (APO-Resource). By creating roles with this authorization object and assigning specific resource group values, you can restrict a production planner's ability to view, change, or execute planning functions to only those resources belonging to their assigned group. This is the standard and intended method for achieving such a requirement.

B. Use a planning group.

A planning group is used to group location products for the production planning run (MRP Live), not for managing user authorizations for resources.

C. Use a propagation range.

A propagation range defines the scope of resources and locations to be considered by the planning engine during a planning run, not to restrict a user's access rights.

D. Use a planning area.

A planning area is a core data structure in Demand Planning or Supply Network Planning, not the mechanism for controlling user access to specific resources in PP/DS.

1. SAP S/4HANA 2023 Help Portal

"Authorizations for Resources": This official documentation details the authorization object CAPORES. It explicitly lists the authorization field APORESGRP (Resource Group)

which allows for authorization checks based on the resource group assigned to a resource. This confirms that using a resource group is the designed method for this type of access control. (Path: SAP Help Portal -> SAP S/4HANA 2023 -> Product Assistance -> Enterprise Business Applications -> Manufacturing -> Production Planning and Detailed Scheduling (PP/DS) -> Security -> Authorization Concept in PP/DS -> Authorizations for Master Data -> Authorizations for Resources).

2. Liebich

M.

et al. (2022). Production Planning with SAP S/4HANA. SAP Press. In Chapter 4

Section 4.2.1

"Resource Master Data

" the concept of a resource group is introduced as a freely definable attribute for grouping resources. In Chapter 16

on system configuration

the use of authorization objects to control user activities is discussed

which leverages master data attributes like the resource group for segregation of duties.

The material type is a fundamental control object in the SAP S/4HANA material master. It dictates several key attributes and system behaviors for materials grouped under it. Specifically, it determines which user department views (screens) are available for data entry and the sequence in which they appear. This ensures that only relevant data is maintained for a specific type of material (e.g., raw materials vs. finished goods). Additionally, the material type configuration directly controls the procurement type, defining whether a material is exclusively for in-house production, external procurement, or can be sourced through both methods.

A. Which document types class categories are allowed

The material type does not control which purchasing or sales document types can be used, nor does it restrict the available class categories for classification.

B. Which plantspecific plantindependent statuses are allowed

The material type can define a default cross-plant material status, but it does not control the complete list of statuses that are allowed to be assigned to the material.

---

1. SAP S/4HANA Product Assistance - Material Type:

Reference: SAP Help Portal

SAP S/4HANA 2023

Enterprise Business Applications -> R&D / Engineering -> Product Master Data -> Material Master -> Material Master Record -> Material Type.

Content: The documentation explicitly states that the material type determines "...which user departments (views) can be maintained for a material of this type" (supporting answer C) and "...whether the material is intended for in-house production

external procurement

or both" (supporting answer D).

2. SAP S/4HANA Customizing Guide (IMG):

Reference: Transaction SPRO -> Logistics - General -> Material Master -> Basic Settings -> Material Types -> Define Attributes of Material Types (Transaction OMS2).

Content: In this configuration activity

for each material type

you can select the "User departments" (which determines the views/screens) and set the "Internal/external purchase orders" indicator

which defines the allowed procurement type (e.g.

external

internal

or both). This directly confirms the control functions mentioned in answers C and D.

The "Advanced Planning" flag is a critical setting within SAP S/4HANA master data that designates an object as relevant for advanced planning and scheduling functionalities, such as Production Planning and Detailed Scheduling (PP/DS). This flag must be set in the Material master (on the 'Advanced Planning' tab) to include the product in advanced planning processes. Similarly, the flag must be set in the Work Center master (on the 'Basic Data' tab) for it to be transferred and used as a finite capacity resource in the advanced planning system.

B. Plant: The plant is an organizational unit. While advanced planning is activated for a plant in customizing, the plant master data itself does not have this specific integration flag.

C. Production Version: Although the production version also has an "Advanced Planning" flag and is essential for creating the Production Data Structure (PDS), the Material and Work Center represent the most fundamental master data objects: the product to be planned and the resource providing capacity.

1. SAP Help Portal

SAP S/4HANA 2023

"Material": "To plan a material in PP/DS

you must set the Advanced Planning indicator in the material master on the Advanced Planning tab page. You also define the planning-relevant parameters for the material here." (This supports option D).

2. SAP Help Portal

SAP S/4HANA 2023

"Resource": "To use a work center from SAP S/4HANA as a resource in PP/DS

you must set the Advanced Planning indicator in the work center on the Basic data tab page." (This supports option A).

3. SAP Help Portal

SAP S/4HANA 2023

"Production Data Structure (PDS)": "To transfer a production version from SAP S/4HANA to create a production data structure (PDS) in PP/DS

you must set the Advanced Planning indicator in the production version." (This explains why option C is also technically correct but considered less fundamental than A and D for the purpose of a two-answer question).

The low-level code represents the lowest level at which a material appears in any Bill of Material (BOM) structure within the system. Its primary purpose is to control the processing sequence in multi-level manufacturing scenarios. In Material Requirements Planning (MRP), the system plans materials sequentially, starting from the lowest code (0 for finished products) and proceeding to higher codes (components, raw materials). This ensures that demand for a component is calculated only after the requirements for all its parent materials have been determined. Similarly, in Product Costing, the cost roll-up process calculates costs from the bottom up, and the low-level code dictates this sequence to ensure a component's cost is known before it is included in its parent assembly's cost.

A. The priority of alternative components in an ATP check is typically managed by settings within the BOM item, such as usage probability, or by advanced methods like Rules-Based ATP, not by the low-level code.

D. The use and functionality of subitems within a BOM are determined by the BOM item category and specific data entered for the subitem itself, not by the material's overall low-level code.

1. SAP S/4HANA Help Portal

"Low-Level Code": "The low-level code controls the sequence in which the materials are planned in a planning run. The system plans materials with the low-level code 0 first

then materials with the low-level code 1

and so on. This ensures that the system plans a material only when the requirements for it from all other higher-level materials have been taken into account." (This supports answer C).

2. SAP S/4HANA Help Portal

"Product Cost Planning (CO-PC-PCP)

Cost Rollup": "The system uses the low-level codes in the material master records to determine the costing sequence. It costs the materials with the lowest code (such as raw materials) first

and the materials with the highest code (such as finished products) last. This ensures that all the costs for the materials in a cost estimate are included." (This supports answer B).

3. Dick

K.

& Vallo

R. (2021). Materials Management with SAP S/4HANA: Business Processes and Configuration. SAP Press. In the chapter on Material Requirements Planning

the text explains: "The low-level code determines the sequence in which materials are planned during the MRP run... The same logic applies to product costing

where costs are rolled up from the lowest-level components to the finished product." (Section 6.2.3

"Low-Level Code").

The planning table (Transaction MF50) is the central control instrument for planners in Repetitive Manufacturing (REM). Its primary purpose is to manage and schedule production quantities on a period basis. A planner can directly create new production quantities (which generates planned orders of a specific type for REM) within the table for a material in a given period. Additionally, a core function is to distribute and balance the production load by assigning these quantities to the available production lines, which are represented by different production versions.

C. Dispatch operations to work centers.

This describes detailed scheduling and capacity leveling for discrete manufacturing (production orders), typically done using the capacity planning board (CM25), not the REM planning table.

D. Reschedule deallocate operations.

This is also a function of detailed capacity planning for discrete manufacturing, where individual operations are de-allocated from a work center's schedule. This is not applicable to REM's rate-based planning.

1. SAP S/4HANA Documentation - SAP Help Portal:

Source: Planning Table (Repetitive Manufacturing)

Reference: In the section "Features

" the documentation explicitly states the planner can

"Create and change planned orders" (supporting option B) and "assign the production quantities to the various production lines on which the material can be produced" (supporting option A). The document distinguishes this from the detailed scheduling of discrete manufacturing.

2. SAP S/4HANA Documentation - SAP Help Portal:

Source: Processing the Planning Table

Reference: This section details the procedures for using the planning table. It describes how to "Create planned orders manually" by entering a quantity in an input-ready row. It also explains how to "Change the assignment to a production line" by selecting a quantity and choosing a different production version (line). This directly confirms options A and B as primary functions.

3. SAP Press (2022). Production Planning with SAP S/4HANA.

Reference: Chapter 7

"Repetitive Manufacturing

" Section 7.4

"Planning and Control." This chapter describes the use of the planning table (MF50) for scheduling and leveling production quantities across different production lines. It contrasts this period-based approach with the order-based

detailed operation dispatching (options C and D) used in discrete manufacturing.

SAP Signavio Process Manager is the dedicated solution for business process modeling and design. The task of "remodeling" a business process involves creating a new "to-be" process model, which is the core function of the Process Manager. It uses industry standards like Business Process Model and Notation (BPMN 2.0) to visually design, document, simulate, and collaborate on new process flows. In a brownfield project aiming for a clean core, this tool is essential for designing standardized, optimized processes that align with SAP best practices before implementation.

A. SAP Signavio Process Insights: This tool analyzes the performance of existing ("as-is") processes in a live SAP system and provides recommendations. It identifies what to remodel but is not the tool for designing the new process.

B. SAP Signavio Process Intelligence: This is a process mining tool that discovers and analyzes the actual execution of existing processes based on system data. It provides deep insights into process deviations but is not a process design tool.

C. SAP Signavio Process Governance: This solution manages the lifecycle of process models, including review, approval, and publication workflows. It governs the remodeling effort but is not the tool where the actual modeling takes place.

1. SAP Help Portal

SAP Signavio Process Manager Documentation: "SAP Signavio Process Manager is a professional process modeling tool that provides a central repository for your process landscape. It allows you to document

design

and simulate processes collaboratively." This confirms its role as the primary design and modeling tool. (Source: SAP Help Portal

"What Is SAP Signavio Process Manager?")

2. SAP Activate Methodology for RISE with SAP S/4HANA Cloud

private edition: In the Explore phase

the task "Business Process Design" involves documenting the to-be business processes. The accelerator documentation specifies using a process modeling tool for this activity

for which SAP Signavio Process Manager is the designated solution within the Signavio suite. (Source: SAP Activate Roadmap Viewer

Explore Phase

Deliverable: "Business Process Design").

3. SAP Learning

Course S4CP01 - SAP S/4HANA Cloud

private edition Onboarding Fundamentals: Unit 5

Lesson 2 ("SAP Signavio") describes the solution portfolio. It positions SAP Signavio Process Manager as the tool to "design and document processes" after gaining initial understanding through SAP Signavio Process Insights. This aligns with the flow of a remodeling project.

Finite scheduling mode “Insert Operation” tries to keep the operation on (or very close to) its requested date while still respecting finite capacity.

If no free capacity exists at that date, the system searches the existing sequence for a gap large enough for the operation and – if necessary – shifts already-scheduled neighbouring operations forward or backward to open the gap. This bi-directional movement is characteristic of “Insert Operation”; no other orders in a collective order and no multi-activity sequencing rules are changed automatically.

B. Sequencing on multi-activity resources is not recalculated; only the single chosen capacity slot is shifted.

D. Propagation to the entire collective order does not take place; changes stay within the resource’s sequence where the operation is inserted.

1. SAP S/4HANA 2023 Help Portal → Manufacturing for Planning and Scheduling → Detailed Scheduling → Finite Scheduling Modes → “Insert Operation” (section: Behaviour

bullets 1–3).

2. SAP SCM 7.0 APO PP/DS Online Documentation

IMG path: Advanced Planning and Optimization → Production Planning and Detailed Scheduling → Scheduling → Scheduling Modes → “Insert Operation” (para. “Moves neighbouring operations forward/backward”).

3. University of Mannheim

Chair of Production Management

Lecture “Advanced Planning with SAP APO PP/DS”

WS2022/23

Slide deck 6 “Detailed Scheduling”

slides 18–19 (description of “Insert Operation”: “schedule as close as possible … neighbouring ops may be moved in both directions”).

When a production order operation has the status 'Dispatched' (DS), it means the operation has been firmly scheduled to a specific capacity at a specific time, typically through capacity leveling. To change this schedule, you must use a tool that can interact with this detailed, capacity-constrained plan.

The classic tool for this is the capacity planning table (e.g., transaction CM25), which allows for graphical rescheduling of dispatched operations based on finite scheduling. In SAP S/4HANA, the modern equivalent is the Fiori app Manage Work Center Capacity, which also provides the functionality to view, de-allocate, and reschedule dispatched operations.

A. You can reschedule the operation using lead time scheduling.

Lead time scheduling (e.g., in transaction CO02) does not overwrite dispatched operations, as they are considered fixed by the detailed capacity plan.

B. You can reschedule the operation using infinite scheduling in a planning table.

Dispatching is an act of finite scheduling (allocating limited capacity). Using an infinite scheduling profile would ignore these capacity constraints, defeating the purpose of dispatching.

1. SAP S/4HANA 2023 Help Portal

Fiori Apps Library

"Manage Work Center Capacity": The documentation for this app explicitly lists its key features

including the ability to "Dispatch or deallocate operations that are scheduled for a specific date" and "Reschedule dispatched operations". This directly supports option D. (Access the Fiori Apps Library for SAP S/4HANA 2023 and search for the app ID F1524).

2. SAP S/4HANA 2023 Help Portal

"Capacity Planning Table (Graphical)": The documentation describes the function of the graphical planning table in capacity leveling. It states

"You can dispatch operations that have been scheduled... You can change the dispatch sequence of operations that have already been dispatched." This process of changing the sequence or time is rescheduling within a finite context

supporting option C. (Navigate to SAP Help Portal -> SAP S/4HANA -> Product Assistance -> Enterprise Business Functions -> Manufacturing -> Production Planning and Control (PP) -> Capacity Planning (PP-CRP) -> Capacity Leveling -> Working with the Capacity Planning Table -> Capacity Planning Table (Graphical)).

3. SAP Course S4520 - Advanced Planning in SAP S/4HANA: Unit 3

"Capacity Evaluation and Leveling

" details the process of dispatching. It clarifies that dispatched operations are fixed for MRP and lead time scheduling. It presents the Capacity Planning Table and Fiori apps like "Manage Work Center Capacity" as the designated tools for manipulating (rescheduling) these dispatched operations using finite scheduling strategies. This supports the correctness of C and D and the incorrectness of A and B. (Refer to official SAP Learning Hub for course S4520

Unit 3).

A production planning run in Production Planning and Detailed Scheduling (PP/DS) is designed to create procurement proposals to cover net requirements. For requirements to be fulfilled via in-house production, the system generates planned orders. For requirements to be met through external procurement where a scheduling agreement is the designated source of supply, the system creates scheduling agreement schedule lines. These proposals are temporary planning elements that are subsequently converted into executable orders (like production orders or purchase orders) in a separate business step.

C. Production order: A production order is an execution-level document. It is created by converting a planned order, not directly by the planning run itself.

D. Purchase order: A purchase order is a firm commitment to a vendor. The planning run creates a purchase requisition, which is then converted into a purchase order.

1. SAP S/4HANA 2023 Help Portal

"Procurement Proposal": "In a planning run

the system creates procurement proposals to cover product requirements. The following types of procurement proposals exist: Planned orders for in-house production

Purchase requisitions for external procurement

Scheduling agreement schedule lines for external procurement." This document explicitly lists planned orders and scheduling agreement schedule lines as outputs.

2. SAP S/4HANA 2023 Help Portal

"Production Planning Run": "The production planning run is the central planning function of Production Planning and Detailed Scheduling (PP/DS) that executes procurement planning for products... The system creates PP/DS planned orders for in-house production and purchase requisitions for external procurement." This confirms the creation of planned orders as a primary result.

3. SAP S/4HANA 2023 Help Portal

"Scheduling Agreement in PP/DS": "If a scheduling agreement exists for a product that is procured externally

the production planning run creates scheduling agreement schedule lines." This directly confirms that schedule lines are a possible result of the planning run.

4. SAP S/4HANA 2023 Help Portal

"Conversion of Procurement Proposals": "You convert procurement proposals to create manufacturing orders (production orders or process orders) and purchasing documents (purchase orders)." This section clarifies that production orders and purchase orders are the result of a separate conversion step

not the initial planning run.

During an MRP run, backward scheduling is used to calculate the basic dates for procurement proposals (like planned orders or purchase requisitions) for components. This process starts from the component's requirement date.

For components that are produced internally (in-house), the system uses the In-house production time defined in the material master (MRP 2 view) to calculate the basic start date of the planned order.

For components that are procured externally, the system uses the Planned delivery time, also from the material master (MRP 2 view), along with the goods receipt processing time, to determine when the purchase requisition must be converted into a purchase order.

B. Total replenishment lead time: This is a more general time used primarily for the availability check (ATP) and is not the specific element used by MRP for basic date scheduling.

C. Operation duration: This is used in detailed scheduling (lead time scheduling), which calculates precise production dates based on routings, not for calculating the high-level basic dates.

1. SAP S/4HANA Help Portal

"Scheduling for External Procurement": "In basic date scheduling

the system uses the planned delivery time from the material master record or purchasing info record and the goods receipt processing time from the material master record." (This supports option A).

2. SAP S/4HANA Help Portal

"Scheduling for In-House Production": "In basic date scheduling

the system always calculates the basic dates using the in-house production time that has been entered in the material master record." (This supports option D).

3. SAP S/4HANA Help Portal

"Basic Date Scheduling vs. Lead Time Scheduling": This document distinguishes the two methods

clarifying that basic date scheduling uses times from the material master (in-house production time

planned delivery time)

while lead time scheduling uses detailed data from the routing (like operation durations). (This supports the exclusion of option C).