Perform Shop Order Split
Explanation
This activity is used to split shop orders. Shop order splits are used to
respond to material and schedule changes in the manufacturing environment. CRO
pegged shop orders cannot be split via this activity.
To split a shop order click Merges and Splits and then Split
Shop Order.
In the dialog:
- Select either Discrete Split or Percentage Split.
- Create a new record in the table.
- Enter a shop order number. If this field is left blank, the system will
assign one.
- Enter value in the Split Reason field.
- For a discrete split, enter a value in the Lot Size field. For
a percentage split, enter values in the Split Percentage and Rounding
Precision fields.
- You can define more than one order that split will create in the table,
as long as the total lot size amount is less then original lot size.
You can use the Shop Order Split Structure
page to view the split shop orders in a graphical way, navigate to each
split shop order and handled the shop orders.
Prerequisites
This activity requires that:
- A shop order in status Planned or Released
must exist.
- The split reason must have been defined on the Split Reason
Codes page.
- A shop order should not have automatic pegging against customer order.
- If a material order line is manually pegged against a purchase order
line or a shop order, the pegging has to be removed first.
- If the parent part is manually pegged against a customer order line
or a shop order, the pegging has to be removed first.
- If the shop order is connected to a split checklist, the split checklist
status has to be approved e.g. all split checklist items have to be approved.
- The shop order must not contain split operations.
System Effects
- A new shop order will be created by the system in the status of Planned.
The original part number, material and operations are used by default, but
you can modify the shop order after the split.
- If the shop order is manually connected to a project activity or the
shop order is connected via project delivery, the new shop orders will be
connected to the project/activity the same way as the original shop order
was before the split. The planned committed cost of the shop order is also
split and the project activity is updated accordingly.
- If the parent part is multilevel-tracked and if the as-built structures
exist, the as-built structures of the serials/lot batch numbers assigned
to the child shop order will be lost as the child shop order is created
in the Planned status.