Order Split (SAP Library - Production Orders (PP-SFC))

Order Split

Use

Order split enables you to split an existing production order, for which processing may have already begun, into two separate production orders. These production orders are then executed separately from a logistics perspective. You might want to perform an order split for the following reasons:

When a partial lot of a production order has to be handled differently than the rest due to quality reasons, you can create a separate order to do this.
If capacity bottlenecks occur, the portion of the order quantity that is required immediately can be processed separately.
The material availability can only be confirmed for part of the order quantity. You split the order to create an order with full material availability.
If the required date for a partial quantity of the finished material has changed, this portion can be split off in a different order.
If a production order cannot be completed on time, you can split the order to reduce the order quantity. The reduced order quantity then requires less time to produce.

Features

When you split an order, you split off part of the order quantity (split quantity) of a production order (parent order) from a certain operation of the standard sequence (split operation). The quantity that is split off is produced in a separate production order (child order). In the process, the operations from the split operation onwards are copied from the parent order to the child order, along with the assigned material components. The system automatically recalculates all the quantities affected by the order split, as well as dates at header, operation, and component level.

The following functions are provided:

Structure

The structure of the parent order does not change. The structure of the child order is a copy of the partial quantity of the objects from the parent order. All assigned components, production resources and tools, and trigger points are copied for the operations included in the child order. In addition, the sequences that contain the selected operations are also copied.

Parallel Sequences

If the parent order has parallel sequences and they are parallel in the split operation, you can decide which operations from these parallel sequences are copied to the child order.

Quantities

The quantities (header, operation, component) are determined automatically, based on the selected split quantity. The order quantity of the parent order is modified by the expected yield variance. In this process, the yield variance is reduced by the split quantity.

The split quantity must be less than the split operation quantity, to ensure that the split operation retains a remaining quantity. Quantities confirmed in the parent order cannot be split. If the sum of split quantity and confirmed quantity in the split operation (or maximum confirmed quantity in a successor) exceeds the split operation quantity, a warning message informs you of this fact. If you ignore the warning message, the order quantity is increased accordingly.

Dates

The parent order is rescheduled after the order split. The child order is scheduled in accordance with the specified scheduling data.

Order type

The order type from the parent order is proposed for the child order. You can give the child order a different order type if necessary.

Costs

Actual costs

The costs of the parent and child orders are collected in a common Product Cost Collector. This is because the parent order, as a rule, has already caused actual costs before the split took place. If the actual costs were collected in the parent order before the split, and separately in the parent/child orders after the split, then the materials of the parent order would have excessively high costs per piece, and the child order correspondingly lower costs. As a result, settlement for each order would result in unwanted variances in controlling.

Planned Costs

Temporary planned costs can be determined and analyzed within split orders (applies only to orders with product cost collectors).

A general cost analysis, with target costs and variances, can be performed for product cost collectors in reporting for periodic product controlling.

System Status

There are various system status values that indicate that an order has been split:

SPLT (split) for the parent order
SPLE (generated through a split) for the child order
SPLT (split) for a split operation

Multi-level order split

Orders (including child orders) can be split several times. The dependencies can be seen in the split hierarchy.

Split hierarchy

The split hierarchy displays the dependencies between the parent and child orders in an overview tree. During order maintenance, the split hierarchy and the selected order from the split hierarchy are displayed. You can navigate to any order in the split hierarchy (tree structure).

In the default setting, the split hierarchy appears to the left, and the order to the right. To change their position, choose This graphic is explained in the accompanying text (move counter-clockwise) or select the position directly.

The split hierarchy provides other standard functions: Managing display variants, expanding and collapsing subhierarchies, and printing.

Inspection Lots

Order processing with QM integration is supported together with the order split. After order release, a separate inspection lot is created for the child order, just like for the parent order, and planned inspection characteristics are copied to the order.

Serial number assignment

Serial number assignment in the production order and the order split are integrated.

If serial numbers have already been assigned before the split, you must select the serial numbers that are to be reassigned from the parent order to the child order. This is important, for example, when certain pieces are to be processed separately, depending on the inspection results.

On the other hand, if you assign the serial numbers after an order split, the required number of serial numbers to assign is adjusted to fit the order quantity minus the split quantity. Inspection results that were entered for individual pieces before the split are retained after the split, even if the serial numbers of these individual pieces are assigned to a child order after the split. Inspection results for the split-off individual pieces can subsequently be recorded in the inspection lot for the child order.

For more information, refer to Serial Number Assignment During Order Split.

Alternative sequences

Alternative sequences that are parallel to the split operation or come before the split operation are not copied to the child order. Alternative sequences that come after the split operation are copied to the child order.

Confirmation

Orders that are part of a split hierarchy can only be confirmed through operation confirmations – that is, confirmations for the document header are not supported. Operations in a parent order that lie before the split operation cannot automatically be confirmed through Milestone Confirmation or Progress Confirmation. Manual confirmations must be entered for these operations.

Example

An order has operations 10 to 40. Operation 40 is a milestone. You split an order from operation 10. When you confirm operation 40, operations 10 through 30 are confirmed automatically in the parent and child orders.

Example

An order has operations 10 to 40. Operation 40 is a milestone. You split an order from operation 20. When you confirm operation 40, operations 20 through 30 are confirmed automatically in the parent order. Operation 10 in the parent order must be manually confirmed. When you confirm operation 40, operations 20 through 30 are confirmed automatically in the child order. The child order does not have an operation 10 because the order was split from operation 20.

Restrictions

The following restrictions apply to the order split:

The parent order and child order must both be settled to the same product cost collector
You cannot read master data for the orders in a split hierarchy
Orders in a collective order cannot be split
Orders of a split hierarchy cannot be supplemented with a subtree
The parent and child order must both have the same header material
You cannot perform confirmations at order header level
The batch where-used list is not updated during order split