Order Split Usage in Production Orders Applies to: SAP Shop Floor Control (Production Orders) R/3 and ECC 6.0. For more information, visit the Enterprise Resource Planning homepage. Summary: This is an article explaining the functionality of Order Split in Production Orders. In this article, required configuration settings and process are explained with an example. Author: Rajarao Chitturi Company: Intelligroup Asia Pvt Ltd Created on: 05 April 2010 Author Bio: Rajarao Chitturi has 11 years of experience in planning & manufacturing sector. Currently he has been working with Intelligroup Asia Pvt Ltd as a Consultant for 03 years. 2010 SAP AG 1
Table of Contents Introduction... 3 Configuration Settings... 4 Process Flow Steps... 5 Step 1: Create a production order (T-Code CO01)... 5 Step 2: Change production Order (T-Code CO02)... 7 Step 3: Confirm production Order (T-Code CO11N)... 11 Step 4: Goods Receipt for Production Order (T-Code MB31)... 12 Restrictions... 14 Related Content... 15 Disclaimer and Liability Notice... 16 2010 SAP AG 2
Introduction Order split enables us 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. We 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. When we split an order, we 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. In this article process steps are explained with an example considering following assumptions. There is only a standard sequence in use and no alternative sequences. There is no in process inspection. No Serial Number assignment. 2010 SAP AG 3
Configuration Settings Define Order Type dependant parameters (T- Code OPL8) SPRO Production Shop Floor Control Master Data Order Define order type-dependent parameters For required order type, flag product cost collector check box and define default distribution rule as Production Mat.Period.Settlement (PP2). Materials used to explain the process are FINISH01 (Finish material), RAW1, RAW5, RAW7 & RAW8 (Components) Assume that product cost collector is already created for FINISH01 material. 2010 SAP AG 4
Process Flow Steps Step 1: Create a production order (T-Code CO01) Create production order for FINISH01 material with order type PP01 and with quantity 10 PCs. 2010 SAP AG 5
Out of total five operations, confirm first two operations with actual operation quantity. Order split is allowed with following system status: Header Status: Partially released, released, partially confirmed. Operation Status of the split operation and all successors: Created, released, partially confirmed The order split is not allowed with the following status: Header status: Created, delivered, finally confirmed, locked, technically complete, closed, deletion indicator set Operation status of the split operation and all successors: Finally confirmed, dispatched, partially dispatched, capacity split, capacity requirement assigned, capacity requirement partially allocated Operation status of the split operation: Deleted. 2010 SAP AG 6
Step 2: Change production Order (T-Code CO02) Split the production order with split quantity 04 PCs from operation 0030. In production order operation overview, select the operation 0030 and go to functions menu and click on split order. System will display a screen to enter parameters for order split. 2010 SAP AG 7
Enter required split qty in split quantity field. Here we can select different order type for child order. And further system will also allow us to schedule the child order with different dates. After entering all parameters, execute split (click on split order execute button). System will create a child order with specified parameters and it will be displayed along with parent order in 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. We can navigate to any order in the split hierarchy (tree structure). Orders (including child orders) can be split several times. The dependencies can be seen in the split hierarchy. 2010 SAP AG 8
After splitting, system will set the status SPLT (Split) at header and operation levels for parent order and split qty. as expect yield variance. Operation qty. will be reduced to 06 PCs. from operation 0030 to the succeeding operations. System will set the status CSPL (created by splitting) at header level for child order (60004232). 2010 SAP AG 9
All successive operations from split operation (including split operation) will be copied to the child order along with all assignments (for example material components, PRTc etc...) For child order we can check the reference order (60004230) in controlling data tab. 2010 SAP AG 10
Step 3: Confirm production Order (T-Code CO11N) Confirm the both production orders (parent and child) individually. For parent order, repeat confirmation for reaming operations also (i.e. for 0040 & 0050 operations). 2010 SAP AG 11
For child order, repeat confirmation for remaining operations also (i.e. for 0040 & 0050 operations) Step 4: Goods Receipt for Production Order (T-Code MB31) Perform goods receipt for both orders with their respected yield quantities. In this case delivered quantity for the parent order (60004230) is 06 PCs. 2010 SAP AG 12
For child order (60004232) final delivered quantity is 04 PCs. 2010 SAP AG 13
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 We 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 sub tree The parent and child order must both have the same header material We cannot perform confirmations at order header level The batch where-used list is not updated during order split 2010 SAP AG 14
Related Content Order Split For more information, visit the Enterprise Resource Planning homepage. 2010 SAP AG 15
Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document. 2010 SAP AG 16