2024 Updated Verified C-TS422-2023 Q&As – Pass Guarantee or Full Refund [Q39-Q55]

Backward scheduling is a method of determining the order dates for components from dependent requirements by starting from the requirement date of the finished product and working backwards through the production structure. Backward scheduling considers the following time elements:
Operation duration: This is the time required to perform an operation on a resource, such as a work center or a machine. Operation duration is influenced by various factors, such as the quantity, the lot size, the setup time, the processing time, the teardown time, and the operation scrap. Operation duration is subtracted from the requirement date of the finished product to determine the start date of the operation.
In-house production time: This is the time required to produce a material in-house, from the start of the first operation to the end of the last operation. In-house production time is influenced by various factors, such as the routing, the work center, the production version, and the scheduling margin key. In-house production time is subtracted from the start date of the first operation to determine the order start date of the material.
Backward scheduling does not consider the following time elements:
Total replenishment lead time: This is the time required to procure a material externally, from the creation of the purchase requisition to the receipt of the goods. Total replenishment lead time is influenced by various factors, such as the planned delivery time, the goods receipt processing time, the release time, and the scheduling margin key. Total replenishment lead time is used in forward scheduling, not backward scheduling, to determine the order dates for externally procured materials.
Planned delivery time: This is the time required to deliver a material from the vendor to the receiving plant. Planned delivery time is maintained in the purchasing info record or the material master record. Planned delivery time is a component of the total replenishment lead time, which is used in forward scheduling, not backward scheduling, to determine the order dates for externally procured materials. Reference: Backward Scheduling | SAP Help Portal, Scheduling | SAP Help Portal, SAP S/4HANA Production Planning and Manufacturing Certification Guide, page 77-78.

The difference between order-related and product-related COC is mainly in the level of cost object that is used to collect and analyze the costs of production. In order-related COC, each production order is a cost object that carries its own plan, target, and actual costs. In product-related COC, a product cost collector is a cost object that aggregates the costs of multiple production orders for the same product or product variant. The advantages and disadvantages of each approach depend on the production scenario and the reporting requirements. Some of the factors to consider are:
In product-related COC, all costs are debited and credited to a product cost collector. This means that the production orders linked to the product cost collector do not have any cost segments and do not show any variances. The product cost collector is used for variance calculation and settlement. This simplifies the cost accounting process and reduces the number of cost objects to be managed. However, this also means that the cost details of individual production orders are not available for analysis. Product-related COC is suitable for mass production of standard products with low variance and high volume12.
Order-related COC is beneficial in a flexible production environment where each production order has different characteristics, such as lot size, routing, material components, or quality specifications. Order-related COC allows for a detailed analysis of the cost and performance of each production order and enables a more accurate allocation of overhead costs. However, order-related COC also requires more effort and resources to maintain and process the cost segments and variances of each production order. Order-related COC is suitable for make-to-order or engineer-to-order scenarios where each production order is unique and customized12.
Product-related COC is used in manufacturing for co-products, which are products that are produced simultaneously from the same production process and have a relatively high sales value. Co-products share the joint costs of the production process based on a predefined apportionment structure. Product-related COC allows for a consistent and transparent allocation of the joint costs to the co-products and avoids the problem of negative variances that may occur in order-related COC. Product-related COC is suitable for process industries where co-products are common, such as chemical, pharmaceutical, or food industries34.
Reference:
1: SAP Help Portal: Production Orders in Cost Object Controlling
2: SAP S/4HANA Production Planning and Manufacturing Certification Guide, Chapter 6: Product Cost by Order
3: SAP Help Portal: Product Cost by Period
4: SAP S/4HANA Production Planning and Manufacturing Certification Guide, Chapter 7: Product Cost by Period

A line hierarchy in repetitive manufacturing represents the structure of a production line that consists of multiple work centers. A line hierarchy is a master data object that defines the sequence and the relationship of the work centers that are involved in producing a material. A line hierarchy can be split into different levels, such as line segments, processing stations, or takt areas, to reflect the complexity and the variability of the production line. A line hierarchy can be used for planning and scheduling operations, controlling material flow, and monitoring production performance12.
The other options are not correct for the following reasons:
A production line with prioritized work centers (B): This is not correct. A line hierarchy does not define the priority of the work centers, but the order and the dependency of the work centers. The priority of the work centers can be determined by other factors, such as the capacity availability, the production rate, or the scheduling parameters.
A production line with a parallel sequence in the routing (C): This is not correct. A line hierarchy does not represent the parallel sequence in the routing, but the linear sequence of the work centers. A parallel sequence in the routing means that two or more operations can be performed simultaneously on different work centers for the same material. A parallel sequence in the routing can be modeled by using alternative sequences or parallel sequences in the line hierarchy3.
A production line with an alternative sequence in the routing (D): This is not correct. A line hierarchy does not represent the alternative sequence in the routing, but the main sequence of the work centers. An alternative sequence in the routing means that there are different options for performing an operation on different work centers for the same material. An alternative sequence in the routing can be modeled by using alternative sequences or parallel sequences in the line hierarchy3.
Reference:
https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/f899ce30af9044299d573ea30b533f1c/9231f9504a62eb5ee10000000a44538d.html

Planning with final assembly (40) is a planning strategy that supports the consumption of planned independent requirements for the semi-finished material. This strategy is used when the production of the finished product is triggered by the sales order, but the production of the semi-finished product is not. The semi-finished product is produced in advance based on the forecast and stored in stock. When the sales order is received, the planned independent requirements for the finished product are reduced by the sales order quantity, and the planned independent requirements for the semi-finished product are reduced by the corresponding component quantity. This way, the semi-finished product is consumed by the sales order and the production order for the finished product only requires the assembly of the components. This strategy allows for a shorter lead time and a higher flexibility for the finished product, while reducing the risk of excess stock for the semi-finished product. Reference: Planning with Final Assembly | SAP Help Portal, Planning Strategies | SAP Help Portal, SAP S/4HANA Production Planning and Manufacturing Certification Guide, page 53-54

Consumption-based planning is a planning procedure that uses past consumption data to calculate the future requirements of materials. It does not consider the dependent requirements of higher-level materials, but only the independent requirements from sales orders, forecasts, or stock transfers. Consumption-based planning is suitable for B and C materials, which have low value, low demand variability, and high availability. Consumption-based planning reduces the planning efforts for these materials, as it does not require the maintenance of BOMs, routings, or production versions. Consumption-based planning can be further divided into reorder point planning, forecast-based planning, and time-phased planning, depending on the method of determining the reorder point and the lot size12 Reference:
Consumption-Based Planning – SAP Help Portal
SAP S/4HANA Production Planning and Manufacturing Certification Guide, Chapter 3: Material Requirements Planning, Section 3.1: Planning Procedures, Page 67

The planning strategy settings in the Capacity Scheduling Table determine how the system schedules the operations or orders on the resources. You can select the following settings:
Finiteness level: This setting defines how strictly the system considers the capacity availability of the resources when scheduling. You can choose between infinite, finite, and optimized scheduling. Infinite scheduling ignores the capacity availability and schedules the operations or orders as early as possible. Finite scheduling respects the capacity availability and schedules the operations or orders only in the free slots of the resources. Optimized scheduling tries to find the best compromise between infinite and finite scheduling by minimizing the delays and overloads12 Scheduling control: This setting defines how the system handles the scheduling conflicts that may arise when scheduling the operations or orders. You can choose between rescheduling, shifting, and splitting. Rescheduling means that the system moves the conflicting operations or orders to a later date. Shifting means that the system moves the conflicting operations or orders to another resource within the same resource network. Splitting means that the system splits the conflicting operations or orders into smaller parts and schedules them on different resources or dates13 Direction: This setting defines the direction of the scheduling. You can choose between forward and backward scheduling. Forward scheduling means that the system schedules the operations or orders from the start date to the end date. Backward scheduling means that the system schedules the operations or orders from the end date to the start date14 Reference:
Planning Strategy Settings – SAP Help Portal
Finiteness Level – SAP Help Portal
Scheduling Control – SAP Help Portal
Direction – SAP Help Portal

In reorder point planning, the system compares the available stock with the reorder point to determine the net requirements. If the available stock falls below the reorder point, the system triggers a procurement proposal for the material. The quantity of the procurement proposal depends on the lot size procedure that is defined in the material master. The lot size procedure determines how the system calculates the order quantity based on factors such as demand, costs, and storage space. There are different types of lot size procedures, such as static, periodic, or optimum lot size. Reference: [Production Planning with SAP S/4HANA], page 156; [SAP Help Portal: Lot Size Calculation].

Mode selection is a feature that allows the system to choose the best mode for an activity based on the mode priority and the available capacity of the resources. A mode is a combination of a resource and a formula that determines the duration and quantity of an activity. An operation can have multiple activities, each with multiple modes. Mode selection can be used when an operation contains several activities, each of which is assigned several modes for different resources, and the system needs to determine which resource to use for each activity. Mode selection can also be used when an activity has several modes for the same resource, and the system needs to determine which formula to use for the activity. Mode selection can be performed during the planning explosion or during the interactive planning. Reference: Mode Selection | SAP Help Portal, Mode Selection | SAP Help Portal