Previous | Next | Contents | Index | Navigation | Glossary | Library |
If you define a single order line as a ship set, Oracle Order Entry/Shipping waits until the entire order quantity is available to ship before releasing that line for picking. If you define an order line for a configured product as a ship set, Oracle Order Entry/Shipping waits until all items you ordered in each configuration are available before releasing the line for picking.
Because the lines in a ship set must ship together, they must share the same schedule group attributes: schedule date, warehouse, ship-to location, shipment priority, freight carrier, and demand class. If you put a model or several order lines in a ship set, the values for the Schedule Group Attributes cascade from the first line in the ship set, overriding what you entered for the other lines and schedule details. On the other hand, if you further modify the scheduling attributes on the order header, these attributes will not cascade to the ship set lines, since ship sets contain different lines that might have different defaulting rules.
If you confirm partial shipment of a ship set, Oracle Order Entry/Shipping treats the remaining quantity as a ship set until it is backordered.
Attention: If the profile option OE: Reservations is set to No, Pick Release only verifies that all lines in a ship set are eligible for Pick Release and are not on hold. Available inventory is not verified. Manually backordered ship set lines are released as they meet the appropriate Pick Release criteria.
Note: If you do not check Allow Partial in the Sales Orders header block, Oracle Order Entry/Shipping automatically defaults the same ship set number to each order line as you enter them, resulting in one ship set for the entire order. Oracle Order Entry/Shipping waits until all lines in a ship set are available for picking before releasing any line.
Defining Schedule Group Attributes
Previous | Next | Contents | Index | Navigation | Glossary | Library |