The bundle parent indicates how the bundle needs to be scheduled.
A bundle is represented as multiple order lines with components and parents. An individual line can be both a parent of a bundle as well as a child of another bundle on the order. Each component indicates its parent. The possible values for the constraint are Ship Together, Deliver Together, and Independent. This constraint is obtained from the catalog. Kit ratios are enforced during scheduling.
The logic described in this section is considered when performing scheduling activity.
Shipping constraints are obtained from the catalog. If the catalog is not defined, a bundle is shipped together. These constraints are applied to the components at all levels of a bundle.
If the parent indicates "ship independently", no constraints are applied and the components are treated as independent lines.
If the parent indicates "ship together", the components are shipped together from the same node. However, they can be procured from different nodes and then merged at the shipping node to be shipped as a single shipment.
If the parent indicates "deliver together", the expected delivery date drives the ship schedule, and the components have their shipment dates pushed out to meet the same delivery date in ratio.
When one or more of the components in a bundle are cancelled, the components fall out of ratio. In this scenario, the constraint ’ship together’ is not applied while scheduling the lines that are out of ratio. For example, consider the following:
Ski Package- P1
Skies- C1 (Qty 2)
Poles- C2 (Qty 2)
Helmet- C3 (Qty 1).
Availability:
4C1, 4C2 available at N1, 2C1, 2 C2 available at N2.
The order is created for two Ski Packages and one helmet is manually cancelled. While scheduling, C1 and C2 are completely scheduled against N1, while C3 is backordered. If one helmet is available at N2, it is scheduled against N2, while C1 and C2 are scheduled against N1. Similarly, if the bundle is scheduled against a node, and one of the components is manually backordered, the ’ship together’ constraint is not applied. So in the example above, if N2 backorders the second helmet, it schedules C1 and C2 to N1 because it is closer. As a result, all skies and poles ship from N1, while one helmet ships from N2.
A few components are reserved when the components cannot be scheduled in ratio and the ratio is necessary. In order to reserve, scheduling runs in two iterations. First, it attempts to schedule all the components and the components that are not scheduled are passed through scheduling again. In the second iteration, lines that have already been scheduled as a part of first iteration are passed through scheduling to be used only for optimizations and ship or deliver together constraints. For example,
Scheduling optimizes on number of shipments:
L1 P1 2 (Ship Together)
L2 C1 Kit Ratio 3 (Total Qty 6 (2*3))
L3 C2 Kit Ratio 2 (Total Qty 4 (2*2))
L4 Item1 (Qty 2)
Inv: Item1 2 N1, C1 - 5 N1, 5 N2
During the first iteration, it schedules L4 against N1, L2 and L3 are backordered. In the second iteration L2 (Qty 5) is scheduled against N1 - not N2. This is because the number of shipments is less when compared to N2.