Shipping Execution

This chapter covers the following topics:

Change Orders in Oracle Shipping Execution

Order Line Change in Shipping Execution

In the course of business, Customer Sales Representatives (CSR) enter sales order changes in Oracle Order Management (OM) or Oracle Project Contracts. Changes are required when customers ask to change quantity or shipping information, reschedule or cancel a sales order.

The OM Change Management in Shipping design improves the synchronization of delivery lines and reservations with the order lines when they are changed.

The objective of the Line Change Management design is to allow most of the sales order changes up until the delivery lines are Staged or Ship Confirmed.

Only changes entered after the sales order lines are booked and interfaced to Shipping Execution are validated by the change logic in Shipping Execution. Order Attribute changes propagate in Shipping Execution based on the Shipping Execution change logic.

Change Management Core Functionalities

Delivery Line Split

When an interfaced order line is split, Order Management requests a delivery line split by setting the OM-WSH interface API action flag to S for Split.

As Shipping splits a delivery line, it also synchronizes the Inventory reservation and splits and the move order line.

Split is allowed for delivery lines that have not been ship confirmed.

Change Management Setups

There are no mandatory setups to enable the Change Management functionality. Order Management provides constraints that can be changed during implementation. These constraints are used to prevent sales order changes after the associated delivery lines have been pick confirmed in Shipping.

If you choose to remove these constraints, it is recommended that you implement a two-step shipping process (Confirm/Close Delivery then Ship Confirm) or to always make sure that the deliveries are ship confirmed as soon they are loaded or picked up by the carrier. If the system is not accurately updated in real-time, changes may be allowed after the deliveries are far-gone.

OM Constraints

Order Management provides constraints at pick confirm for users who physically ship deliveries before confirming them in the system. Without these constraints, this process can allow changes between the time items are shipped and the ship confirmation update in the system.

By default these constraints are active to disable order line changes after pick confirm/stage step. Seeded constraints will not allow Order Management user to change, cancel or split order lines once delivery lines have been pick confirmed/staged in Shipping Execution.

Disabling Constraints

Some users require changing order lines after the delivery is pick confirmed/staged and until the ship confirmation stage. The system supports flexibility of removing some or all the Order Management- Shipping constraints.

Note: In the event the system was not updated and changes are committed after the deliveries are physically shipped, users may have to handle exceptions manually (revert changes, move inventory, and adjust inventory).

Changing Defaults

To access the Order Management constraints window

  1. Navigate to the Processing Constraints window.

  2. In the Application field, query Oracle Order Management.

  3. In the Entity field, query Order Line.

    List of OM Constraints at Pick Confirm/Stage

    The Order Management constraints control the following types of Order Line changes once deliveries are Pick Confirmed/Staged:

    • Update order line

    • Cancel order line

    • Delete order line

    • Split order line

    In turn, Order Line update is controlled for 22 different shipping attributes as shown in the following table:

    Order Management - Shipping Execution Constraints
    Actions Fields
    Update Authorized to Ship
    Update Customer
    Update Customer PO
    Update Customer PO Line Number
    Update Deliver To Contact
    Update Deliver To Org
    Update FOB Point
    Update Freight Carrier
    Update Freight Terms
    Update Item Type
    Update Order Quantity UOM
    Update Ordered Quantity
    Update Packing Instructions
    Update Request Date
    Update Schedule Arrival Date
    Update Schedule Ship Date
    Update Ship To
    Update Ship To Contact
    Update Shipment Priority
    Update Shipping Instructions
    Update Subinventory (cannot be removed)
    Update Warehouse
    Cancel Not allowed if pick confirmed
    Delete Not allowed if pick confirmed
    Split Not allowed if pick confirmed

Shipping Execution Workflows

Oracle Shipping Execution enables you to utilize Oracle Workflow to enhance your day-to-day business. Using Oracle Workflow with Oracle Shipping Execution is optional; however, if you choose to enable Oracle Workflow with Oracle Shipping Execution, specific tasks and output are enabled through the use of customized business objects. For example, the workflow can be configured so that specific users receive a notification email when an overship or backorder occurs. The following Shipping Execution-specific workflows are available:

You can customize any of the Shipping Execution-specific workflows and any of the wokflows can be used in any organization. Workflows are customized by Oracle Workflow Builder. You can copy an existing workflow, rename it, save it, then add the customized workflow to the lookup specific to that workflow. For example, the internal name of Trip Flow - Generic is R_TRIP_GEN. After customizing the workflow by adding a new notification activity, if you save it as NOTIFY_TRIP_GEN and add it to the R_TRIP_GEN lookup. With the lookup code as organization code for the organization, the workflow must be triggered in and Meaning as NOTIFY_TRIP_GEN. If the workflow needs to be triggered for all organizations, then the lookup code must be All.

See: Oracle Workflow User's Guide

Extending Shipping Workflows

Delivery and trip workflows enable limited extensions. That is, only those activities that do not required intervention and are not deferred, are allowed. All Oracle Workflow supported extensions are supported by the Ship to Delivery Process Flow. This includes response based notifications.

Shipping Workflow Lookups

The following are the lookups used to customize the Oracle Shipping Workflow:

Shipping Workflow Profile Option

When set to Yes, the profile option WSH: Override Ship to Deliver Workflow enables you to bypass the Ship to Deliver workflow as well as any extensions to the workflow, and continue the delivery through ship confirm.

The default value of this profile option is No.

Workflow-Specific Shipping and Global Parameters

The Shipping Parameters window and Global Parameters window both include the following Workflow-specific parameters:

Enable Workflows must be enabled in the Global Parameters window before Enable Workflows, Raise Business Events, and Enable Ship to Delivery Workflow are enabled in the Shipping Parameters window. Enabling Workflows in the Global Parameters does not enable workflows in each organization. The Shipping Parameters are used to enable workflows for each organization.

Shipping Execution-Specific Business Events

The Oracle Workflow Business Event System is an application service that leverages the Oracle Advanced Queuing (AQ) infrastructure to communicate business events between systems. The Business Event System consists of the Event Manager and workflow process event activities.

The Event Manager contains a registry of business events, systems, named communication agents within those systems, and subscriptions indicating that an event is significant to a particular system. Events can be raised locally or received from an external system or the local system through AQ. When a local event occurs, the subscribing code is executed in the same transaction as the code that raised the event, unless the subscriptions are deferred. Subscriptions can include the following types of processing:

Business events are represented within workflow processes by event activities. By including event activities in a workflow process, you can model complex processing or routing logic for business events beyond the options of directly running a predefined function or sending the event to a predefined recipient.

Shipping Execution-specific business events include:

Business event subscription specific to Shipping Workflow are:

Purging Shipping Execution Workflows

The concurrent program Purge Obsolete Workflow Runtime Data is used to purge Shipping Execution workflows. Shipping Purge also purges workflows associated with deliveries and trips that have met the purging criteria and are purged.

See Oracle Shipping User's Guide and Purging Shipping Records for information on Shipping Purge.

See Oracle Workflow Administrator's Guide for information on Purge Obsolete Workflow Runtime Data.

XML Publisher Enabled Shipping Documents

Oracle XML Publisher enables you to extend various Oracle Shipping Execution reports by customizing the report templates and printing reports in PDF. The following list represents those seeded Oracle Shipping Execution report templates within Oracle XML Publisher:

Customizing Templates

Templates can be customized in many ways. Depending on your business needs, customize your report templates by:

Template Flow

the picture is described in the document text

Creating Templates for Shipping Documents

There are two ways to create a custom report template:

It is suggested that you edit existing templates rather than create new templates.

Once defined or modified, templates are used when printing reports from the Reports and Processes window, Shipping Transactions form, Quick Ship window, and through document sets.

The management of shipping document templates is performed in Oracle XML Publisher.

Note: Editing software can be used to modify and customize templates. For example, Microsoft Word and Adobe Acrobat.

The XML templates are assigned to document sets in the Shipping Document Sets window. See: Defining Shipping Document Sets.

See: Oracle XML Publisher User's Guide

Purging Shipping Records

The Shipping Purge concurrent process is used to purge or report and purge records that are no longer needed. The process identifies records that are eligible to be purged and purges them or generates a report on records that are candidates for purge and then purges them. Entities that can be purged are trips, trip stops, deliveries, delivery details (lines), and LPNs/containers.

The following is a list of exceptions to purging Shipping Execution entities:

See Oracle Shipping Execution User's Guide for information on running the Shipping Purge concurrent process.

Purging Trips and Trip Stops

The following list includes restrictions associated with purging trips and trip stops:

Purging Deliveries

The following list includes restrictions associated with purging deliveries:

Purging LPNs

The following list includes restrictions associated with purging LPNs:

Parallel Pick Release

Parallel pick release enables multiple pick release processes to run simultaneously as child processes through the Pick Release SRS Parameters window and Release Sales Orders window through the concurrent mode. Parallel pick release is available when pick releasing from the Tools menu on the Shipping Transactions form through the concurrent mode.

Parallel pick release enables you to set a default number of child processes by defining the profile option: WSH: Number of Pick Release Child Processes.

Parallel pick release cannot be executed from the Shipping Transactions form action Launch Pick Release. Parallel pick release does not run when Pick Release is executed Online.

Parallel pick release distributes the pick release workload across multiple child processes, reducing the overall length of time it takes to run pick release.

Parallel Pick Release Profile Option

The profile option WSH: Number of Pick Release Child Processes determines the maximum number of child processes that will run. If the number of items in the batch is less than the profile option, then only as many processes will run as there are items. If the number of items is greater than the profile, then the profile will be honored. Although this profile option is the default, the Number of Child Processes field, on the Pick Release SRS window, can be modified. For example, if you set the profile option to four, then each time pick release is run, four child processes run concurrently based on (and grouped by) item and organization if you do not change the Number of Child Processes field.

The actual number of pick release child processes spawned by pick release depends on each individual pick release batch and the profile setting.

Message Configuration

Oracle Shipping Execution enables you to determine the configuration (Error or Warning) of the following ship confirm actions:

You determine whether these Shipping events display an Error or Warning message during ship confirm (for all entities, including trips and deliveries). Warning messages enable you to continue, whereas Error messages stop the process until the error is fixed.

Automated ship confirm is not affected by the configuration of these messages.

See Roles and Users for information on configuring ship confirm error/warning messages.

Exception Messages

The following messages have been created to provide feedback to Order Management users when an order line change is rejected.

Update Not Allowed

Message: The update is not allowed because the source line is under WMS control.

This message is returned if the update cannot be executed because the source line is under Oracle Warehouse Management (WMS) control.

Update Cannot Split Quantities

Message: The source line cannot be split because quantity conversion has an error.

This message is returned if the update is rejected because the source line cannot be split due to a quantity conversion issue. This exception happens when the result of a split would create a null or negative quantity.

Attribute Update Not Allowed

Message: The update requested cannot be executed now because the source line has at least one delivery line that is in a confirmed delivery or has been shipped.

This message is returned when the update cannot be executed because the source order line is only partially eligible for a change. The order line is associated at least with a confirmed delivery line or has already been shipped. For a change to be allowed, all delivery lines related to the source order line must be eligible for the change.

Invalid Source Code

Message: The Source code 'Source_code_name_string' is not recognized.

This message is returned when a delivery line update was rejected because it was requested by a product other than Order Management. The source code allowed is restricted to 'OE'. Other products cannot request Shipping changes.

Invalid Packing Condition Caused by Shipment Attribute Change

Message: One or more shipment attributes have been changed for delivery line &DETAIL. Please manually unassign the delivery line from container &CONTAINER_ID.

This packing exception message is returned when Order Management has changed at least one non-enforced Shipment attribute for a delivery line packed in an LPN (container.)

The update was executed but may require an additional manual step to unassign the delivery line from the LPN.

Change Management Frequently Asked Questions

How are inventory reservations handled?

Order Management creates Inventory reservations by calling internal Inventory APIs before interfacing sales order lines into Shipping.

Shipping manages reservation changes for all lines interfaced to Shipping that have reached an Order Management workflow status of Awaiting Shipping. Reservation changes for allocated or staged lines are allowed through backordering.

Do overpicked quantities have reservations?

Yes, Shipping creates reservations for overpicked delivery line quantities. Initially overpicked quantities do not have matching reservations. Shipping creates additional material reservations so that the whole picked inventory is effectively reserved.

How do individual serial numbers and ranges get split?

Shipping splits serial numbers ranges and assigns individual numbers when splitting delivery lines with serially controlled items. Serial numbers already assigned to items are kept during splitting. When splitting delivery lines, Shipping handles splits then updates the MTL_SERIAL_NUMBERS_TEMP table. The serial numbers are exploded at Inventory Interface time. Serial numbers assigned to Backorders are deleted during split changes.

What happens when OM makes a change to a shipping delivery grouping attribute?

The result of changing a delivery grouping attribute depends if the attribute changed is enforced. There are two types of grouping attributes: mandatory and optionally enforced. Shipment attributes are a sub-category of optional attributes.

There are five optionally enforced Shipping delivery grouping attributes. The first four are Shipment attributes:

  1. Customer Name

  2. Freight Terms

  3. FOB Code

  4. Ship Method

  5. Intermediate Ship To Location

There are two mandatory grouping attributes: Ship From Location and Ship To Location.

When Order Management requests to change any of the mandatory or optional attributes, Shipping will check the Shipping Parameters' grouping attributes to identify any optional attributes to enforce and perform the following actions:

What happens to the requested quantity when OM requests an ordered quantity change?

Shipping looks up all the delivery lines related to the source order line in a sequence governed by the line status and makes changes to the requested quantity if possible.

The line status order ranking criteria is as follows:

How are changes in source line quantity propagated to the delivery line requested quantity?

For the related source order line, Shipping looks up the delivery lines in the sequence described and makes a decision as follows:

Increase in Quantity: Line is updatable: The line is updated if it is unassigned from a delivery or if the delivery is Opened, line is not packed in a LPN container, delivery (if present) is Not Firmed and the line release status is one of Not Ready to be released, Ready to be released and Non Transactable.

New delivery line: For all cases except updatable delivery line as mentioned, a new delivery line is created with the increased quantity.

Decrease in Quantity: Ship partial updatable: Lines requested quantity is updatable except for any line part of a shipped delivery (confirmed, closed or in transit). In that case the requested reduction in quantity can be accepted only if it is not more than the sum of those lines that are not shipped.

Move order line update: The Inventory Move Order Line needs to be updated for lines in status Released to Warehouse.

Multiple lines: The shipment lines are looked up in sequence and their requested quantities are reduced until the sum of the reduced quantity reaches the requested reduction in the source line quantity.

Exceptions: An exception is logged along with the reduction in requested quantity for the shipment lines that are either staged, part of a planned delivery, or packed in a container.

What happens if Order Management tries to make changes to a ship confirmed delivery?

Changes to Shipped Confirmed or Closed delivery lines are not allowed. Instead a sales order line quantity increase creates a new delivery line.

How does Shipping handle a change in allocated/picked ship set delivery line?

For a Ship Set delivery line Allocated or Picked, the Order Management change request is fulfilled according to the Shipping parameter Enforce Ship Set at Picking.

What happens during an organization change?

When a delivery line is transferred to a different organization, the Move Order Line (MOL) is reset to Ready to Release for the target organization. The reservations in the original organization are deleted

Inventory reservations are created in the target organization.

How are reservations handled during split line requests?

During a delivery line split request the change logic retains and splits existing Inventory reservations. Reservations are associated with the delivery details. The delivery lines are sequenced according to their release status so that the shipped/staged lines with the specified inventory control will retain their reservations. The delivery lines not yet associated with a reservation (Ready to Release, Backordered, or Released to Warehouse) have their reservations split arbitrarily.

What happens to changes on partially shipped deliveries (split lines)?

What happens when a change is requested for an order line that spans across two or more deliveries, one of which is ship confirmed or closed but not OM interfaced? Regardless of other delivery lines eligibility for changes, no changes are allowed until the Order Management interface has updated the source order line. This is to prevent data corruption since the source order line has not been updated by the shipped line. The change request can be manually resubmitted successfully once the source order line has been updated by the shipped delivery line.

Are non-proportional split changes supported?

Yes, both Order Management and Shipping Execution support non-proportional splits. The delivery lines are kept synchronized with the order lines during Order Management non-proportional set splits by propagating changed attributes to the ship set delivery lines.

Change Effects

Order is Booked/Scheduled

Once eligible booked sales orders are interfaced from Order Management to Shipping Execution, the delivery lines are accessible from the Shipping Transactions form. The initial delivery line status is Ready to Release.

Change the organization or subinventory

These changes are supported; changes can be made with no restriction.

Change a line item

Changing customer item is supported as long as the Inventory item is not changed on an existing delivery line. There is no change restriction if there is no delivery line.

Cancel an order line

This change is supported. The delivery lines are set as Canceled.

Decrease delivery line quantity

This change is supported. The delivery line quantity is reduced.

Increase delivery line quantity

This change is supported. The delivery line quantity is increased accordingly.

Move the schedule date later or earlier

This change is supported. The delivery detail is updated with the new scheduling information.

Unschedule a Delivery Line

This change is supported. The delivery line status is set to Ready to Release.

Changes to a ship set

If the Shipping Parameter Enforce Ship Set is active, changes to ship sets are allowed in Order Management before the inventory is allocated or before the delivery lines are picked. You can remove an order line from a ship set, regardless of the Shipping Parameter Enforce Ship Sets or the delivery line status prior to ship confirm.

Change ship-to location

This change is supported if the delivery line is not assigned to delivery or a container. If the delivery line is assigned, an exception is logged and the delivery line is unassigned from the delivery.

Split an order line

This change is supported. The delivery line detail is split.

Delivery Lines are Pick Released

The following details show how the order changes are supported after delivery lines get pick released. The inventory is allocated when a move order is created during pick release.

Change the organization or subinventory

These changes are supported. The delivery move order allocation status is changed to Canceled, the delivery detail is updated with the new organization and the status is reset to Ready to Release. A new reservation is created only if a reservation existed prior to pick release in previous org.

Change a line item

This change is not directly supported. An item cannot simply be changed for a different one at this stage. The CSR will need to cancel the order line. A new order line should be created with the replacement item.

Cancel an order line

This change is supported. The delivery line is set to status Canceled and the move order line is deleted.

Decrease delivery line quantity

This change is supported identically for backordered lines. The Move Order line quantity is updated and if applicable, the extra serial numbers are unassigned.

Increase delivery line quantity

This change is supported. A new delivery detail with status Ready to Release is created for the extra quantity.

Move the schedule date later or earlier

This change is supported. The delivery detail is updated with the new scheduling information.

Unschedule a delivery line

This change is supported. The move order line status is set to Canceled and the delivery detail status is changed to Ready To Release.

Change within a ship set

This change is supported unless the Ship Set profile option is set to Enforce Ship Set in Shipping. The delivery details are updated with the changes.

Change ship-to location

This change is supported if the delivery line is not assigned to delivery or a container. If the delivery line is assigned, an exception is logged and the delivery line is unassigned from the delivery.

Split an order line

This change is supported. The delivery line detail is split.

Delivery Lines Released to Warehouse

This status reflects that the move order lines were created and the delivery lines have been released to the warehouse. Lines may have been successfully allocated but not pick confirmed.

In this step, the inventory items are picked from inventory location. The picking operation ends with a pick confirmation to progress the delivery line to Staged status.

Change the organization or subinventory

These changes are supported. The delivery move order allocations are deleted, the delivery detail is update with the new organization, and the status is reset to Ready to Release. New reservations are created only if a reservation existed prior to being Released to Warehouse.

Change a line item

This change is not directly supported. An item cannot simply be changed for a different one at this stage. The order line will have to be canceled. A new order line should be created with the replacement item.

Cancel an order line

This change is supported. The delivery details are set as Canceled and the move order line is deleted.

Decrease delivery line quantity

This change is supported. The move order line quantity is updated and if applicable, the extra serial numbers are unassigned.

Increase delivery line quantity

This change is supported. A new delivery detail with status Ready to Release is created for the extra quantity. A new reservation assignment is not added.

Move the schedule date later or earlier

This change is supported. The delivery detail is updated with the new scheduling information.

Unschedule a delivery line

This change is supported. The move order line is deleted and the release status of the delivery detail is changed to Ready To Release.

Change within a ship set

This change is supported unless the Ship Set profile option is set to Enforce Ship Set in Shipping. Both the delivery details and the move order lines are updated with the changes.

Change ship-to location

This change is supported if the delivery line is not assigned to delivery or a container. If the delivery line is assigned, an exception is logged and the delivery line is unassigned from the delivery.

Split an order line

This change is supported. The delivery line detail is split.

Staged Delivery Lines

Occurs after pick confirm to reflect the subinventory transfer from source inventory location to staging area has completed. The picked items have been dropped in the staging inventory area. Delivery lines remain staged until they are ship confirmed.

Change the organization or subinventory

These changes are supported. The inventory control information is cleared and the delivery detail is set to status Ready to Release. An exception is logged.

Change a line item

This change is not directly supported. An item cannot simply be changed for a different one at this stage. The order line will have to be canceled. A new order line should be created with the replacement item.

Cancel an order line

This change is supported. The delivery lines are set to Canceled and an exception is logged.

Decrease line quantity

This change is supported. The delivery line quantity is adjusted, if applicable the serial numbers are unassigned. An exception is logged.

Increase delivery line quantity

This change is supported. A new delivery detail with status Ready to Release is created for the extra quantity. A new reservation is not created.

Move the schedule date later or earlier

This change is supported. The delivery detail is updated with the new scheduling information.

Unschedule a delivery line

This change is supported. The status of the delivery detail is changed to become Ready to Release.

Change within a ship set

This change is supported unless the Ship Set profile option is set to Enforce Ship Set in Shipping. The delivery details are updated with the changes.

Change ship-to location

This change is supported if the delivery line is not assigned to delivery or a container. If the delivery line is assigned, an exception is logged and the delivery line is unassigned from the delivery.

Split an order line

The delivery lines are split and remain in Staged status.

Ship Confirmed, In Transit, or Closed

Note: Companies that choose to support order changes after staging should ship confirm all deliveries in the system as they are moved across the loading dock or before. Ship confirming deliveries after loading or departure can enable you to make changes based on outdated status.

Note: You should ship confirm deliveries at the point when order changes should no longer be allowed through the system. This may be as the inventory is moved through the loading dock or when a seal is applied to the truck trailer door. Failure to update the order status while the order is being loaded will mislead CSRs to believe the delivery is still in house when it is actually in transit.

Delivery at the loading dock

The deliveries have not been and should not be loaded on board the truck.

Delivery on board the truck at the loading dock

The truck should be unloaded or if not practical the delivery drop-off should be canceled and dropped off back at the pick up stop.

Delivery truck in Transit

The delivery carrier should be called and asked not to deliver the goods or turn the truck around.

Delivery dropped off

An RMA should be issued, the delivery should be returned. A separate replacement order should be created.

Change Management and Shipping Execution Actions

In this section, you can find status tables to quickly capture the results of an Order Management change.

Sales order line changes in Order Management are not allowed if any related delivery line is either Confirmed or Shipped.

Shipping Actions for a Requested Quantity Change
Detail Status Packed Firmed Sequence of Selection Increase Line Quantity Decrease Quantity (but not to zero) Decrease Quantity to Zero
Line unassigned from a delivery or delivery is open No No Not ready to be released Increase fully, consider no more shipment lines Decrease requested quantity; if not sufficient for the change request, proceed to the next shipment line Cancel delivery details
Line unassigned from a delivery or delivery is open No No Ready to be released or non- transactable Increase fully, consider no more shipment lines Decrease requested quantity; if not sufficient for the change request, proceed to the next shipment line Cancel delivery details
Line unassigned from a delivery or delivery is open No No Backordered New delivery detail with full change, consider no more shipment lines Decrease requested quantity; if not sufficient for the change request, proceed to the next shipment line Cancel delivery details
Line unassigned from a delivery or delivery is open No No Released to warehouse New delivery details with full change, reservations are not created Update move order line
Unassign serial numbers
Decrease requested quantity; if not sufficient for the change request, proceed to the next shipment line		 Delete move order line
Cancel delivery details
Line unassigned from a delivery or delivery is open No No Staged/Pick Confirmed New delivery detail with full change, consider no more shipment lines Log exception
Decrease requested quantity; if not sufficient for the change request, proceed to the next shipment line		 Log exception
Cancel delivery details
Line unassigned from a delivery or delivery is open No Yes Any other than canceled New delivery detail with full change, consider no more shipment lines Log exception
Decrease requested quantity; if not sufficient for the change request, proceed to the next shipment line		 Log exception
Cancel delivery details
Line unassigned from a delivery or delivery is open Yes Any Any other than canceled New delivery detail with full change, consider no more shipment lines Log exception
Decrease requested quantity; if not sufficient for the change request, proceed to the next shipment line		 Log exception
Cancel delivery details
Delivery is confirmed, in transit, or closed Any Any Status is closed; create a new sales order After Order Management Interface run, new delivery detail with full change, consider no more shipment lines Reject, return eligible quantity, and rollback Reject, return eligible quantity, and rollback
OM Changes vs. Shipping Actions
Action Booked or Scheduled Pick Released Reservations Allocated Pick Confirmed or Staged
Change organization Make change Delete move order line
Update delivery detail with new warehouse
- Delivery detail should be Ready to Release		 Set status on the move order line to Canceled
Make delivery detail Ready to Release and change
- Clear inventory control information
- OM deletes reservation and recreates a new reservation only if the created reservation existed prior to Pick Release		 Make change
Log exception
Unassign if needed
- Clear inventory information
- Make delivery detail Ready to Release
Change subinventory Make change Delete move order line
Update delivery detail with the new subinventory		 Set status on the move order line to Canceled
Make delivery detail Ready to Release and change
Clear inventory control information		 Make change
Log exception
Unassign if needed
Clear inventory information
Make delivery detail Ready to Release
Change inventory line item (only Customer Item can be changed) Change not allowed in Order Management with delivery in that status Change not allowed in Order Management with delivery in that status Change not allowed in Order Management with delivery in that status Change not allowed in Order Management with delivery in that status
Unschedule Set delivery detail released status to Ready to Release Delete move order line
Update delivery detail released status as Ready to Release and change		 Set Status on the move order line to canceled
Make delivery detail Ready to Release and change		 Make change
Log exception
Unassign if needed
Reset status to Ready to Release
Schedule date change: Date pulled in Update delivery detail with new scheduling information Update delivery detail with new scheduling information Update delivery detail with new scheduling information Update delivery detail with new scheduling information
Schedule date change: date pushed out Update delivery detail with new scheduling information
Log an exception		 Update delivery detail with new scheduling information
Log an exception		 Update delivery detail with new scheduling information
Log an exception		 Update delivery detail with new scheduling information
Log an exception
Increase quantity Increase delivery details quantity Create new delivery detail with status Ready for Release for the extra quantity
Create new assignments if needed		 <blank> <blank>
Decrease quantity or cancel line Decrease quantity
Set delivery details status to canceled if delivery detail is completely canceled		 Decrease quantity and update move order line
Unassign and unmark serial number if needed
Set delivery details status to Canceled if delivery detail is completely canceled
Delete move order line if completely canceled		 Decrease quantity and update move order line
Unassign and unmark serial number if needed
Set delivery details status to Canceled if delivery detail is completely canceled
Delete move order line if completely canceled		 Decrease quantity
Log exception
Unassign and unmark serial number if needed
Set delivery details status to Canceled if delivery detail is completely canceled
Ship set Make change Update delivery details
Update move order lines if enforce ship set		 Update delivery details Update the set
Split line Make change and split delivery details Make change, split delivery details and unrelease (set to Ready to Release) Make change, split delivery details and unrelease (set to Ready to Release) Make change and split delivery detail
Delivery grouping attributes Make change and split delivery details Make change, split delivery details and unrelease (set to Ready to Release) Make change, split delivery details and unrelease (set to Ready to Release) Make change and split delivery detail
Organization, implicit, mandatory If assigned to delivery or container, log an exception and unassign from delivery If assigned to delivery or container, log an exception and unassign from delivery If assigned to delivery or container, log an exception and unassign from delivery If assigned to delivery or container, log an exception and unassign from delivery
Ship from location, implicit, mandatory If assigned to delivery or container, log an exception and unassign from delivery If assigned to delivery or container, log an exception and unassign from delivery If assigned to delivery or container, log an exception and unassign from delivery If assigned to delivery or container, log an exception and unassign from delivery
Ship to location, implicit, mandatory If not assigned to delivery or container, make change.
If assigned to delivery or container, log an exception and unassign from delivery		 If not assigned to delivery or container, make change.
If assigned to delivery or container, log an exception and unassign from delivery		 If not assigned to delivery or container, make change.
If assigned to delivery or container, log an exception and unassign from delivery		 If not assigned to delivery or container, make change.
If assigned to delivery or container, log an exception and unassign from delivery
Intermediate ship to location, implicit, optional If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery
Customer, explicit, optional If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery
Freight terms, implicit, optional If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery
FOB code, explicit, optional If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery
Ship method, explicit, optional If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery
Carrier, explicit If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery
Delivery, implicit, mandatory when assigned to delivery If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery
Legend for delivery grouping attributes If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery If enforced, unassign from the delivery
Implicit: Automatically included, not part of shipping parameters Mandatory: Always Yes Optional: Can be Yes or No, usually set for each organization in the shipping parameters <blank> <blank>

Backorders

This section describes the functional flow of the backorder process in Shipping Execution.

The Backorder status:

Pick Release Statuses

The following list displays the various pick release statuses along with a description for the status and an event that will cause the status to display on the delivery line.

Delivery Detail Status Flow

the picture is described in the document text

Backorder at Pick Release

One way a delivery line detail can receive a picking status of Backordered is by auto-backorder. When the system determines insufficient inventory exists at the time of inventory allocation, it automatically splits the line if partial quantities are released and changes the status to Backordered for the unreleased quantity.

Picking Steps

  1. Pick release creates pick wave move order header.

  2. Pick release creates move order line.

  3. Move order line is allocated at pick release or at a subsequent step.

  4. Inventory updates Shipping Execution with the results of allocation. If a shortage exists (the quantity requested is greater than the quantity allocated on the move order line) Shipping performs the auto-backorder routine.

Backorder at Ship Confirmation

Backordering also happens at ship confirmation either by backordering the entire delivery, in which case all delivery lines that are associated with the delivery will receive a picking status of Backordered. Or you can enter a shipped quantity of less than the requested quantity to backorder a partial quantity of the items being shipped.

Picking Steps

  1. Pick release creates pick wave move order header and lines

  2. Move order line is detailed

  3. Move order line is pick confirmed

  4. Delivery is backordered at ship confirmation

  5. If the status is firmed, keep the LPN and delivery assignment. Otherwise, unpack if packed.

  6. Change line status to Backordered.

Backorder Flow

the picture is described in the document text

In the physical flow of the backorder process, material may or may not exist. In the case where the material does not exist, the backorder process is used to identify inventory discrepancies. For example, the system allocates the complete requested quantity at pick release based on availability. When the picker physically accesses the picking location, the quantity available to ship is less than the quantity the system determined as available. The shipper enters the actual quantity available in the shipped quantity field. The result of the ship confirm action is as follows:

This diagram illustrates the transaction flow for backorders.

Transaction Flow for Backorders

the picture is described in the document text

Scenario 1: Shortage at Detailing

A sales order line for 10 units of item A is booked and released. Only seven units exist in inventory. The order is allocated, pick confirmed and ship confirmed.

Post Detailing

During allocation, seven units are found. Inventory updated shipping with the results of the detail. Auto backorder split the delivery line and called OM to split the sales order line. Oracle Shipping then reduced the requested quantity on the move order line. These tables show post detailing data for sales order lines, delivery lines, move order lines, and move order line details.

Sales Order Lines
Line Quantity
1 10
Delivery Lines
Line SO Line Qty MO Line Staged Qty Status Subinventory
100 1 7 1000 0 Released to Warehouse  
101 1.1 3     Backordered  
Move Order Lines
MO Line Req Qty Detailed Qty Delivered Qty
1000 7 7 0
Move Order Line Details (MMTT)
Line MO Line Qty From Loc To Loc
100 1000 7 Stores Stage

Pick Confirm

You pick confirm the seven units. Because the move order line was changed at detailing, the move order line is closed at pick confirm even though all 10 units were not found. These tables show pick confirm data for sales order lines, delivery lines, move order lines, and move order line details.

Sales Order Lines
Line Quantity
1.1 10
Delivery Lines
Line SO Line Qty MO Line Staged Qty Status Subinventory
100 1.1 7 1000 7 Staged Stage
101 1.1 3   0 Backordered  
Move Order Lines
MO Line Req Qty Detailed Qty Delivered Qty
1000 7 7 7
Move Order Line Details
Line MO Line Qty From Loc To Loc
10000 1000 7 Stores Stage

Ship Confirm

You now ship confirm the seven units. These tables show ship confirm data for sales order lines, delivery lines, move order lines, and move order line details.

Sales Order Lines
Line Quantity
1.1 10
Delivery Lines
Line SO Line Qty MO Line Staged Qty Status Subinventory
100 1.1 7 1000 7 Shipped  
101 1.1 3   0 Backordered  
Move Order Lines
MO Line Req Qty Detailed Qty Delivered Qty
1000 7 7 7
Move Order Line Details
Line MO Line Qty From Loc To Loc
10000 1000 7 Stores Stage

Scenario 2: Shortage Reported at Pick Confirm

A sales order line for 10 units of item A is booked and released. Seven units are found during detailing but at pick confirmation you report a missing quantity of one and can only pick confirm six units for the order.

Post Detailing

Allocation completes successfully and all 10 units are found. These tables show post detailing data for sales order lines, delivery lines, move order lines, and move order line details.

Sales Order Lines
Line Quantity
1.1 10
Delivery Lines
Line SO Line Qty MO Line Staged Qty Status Subinventory
100 1.1 10 1000 0 Released to Warehouse  
Move Order Lines
MO Line Req Qty Detailed Qty Delivered Qty
1000 10 10 0
Move Order Line Details
Line MO Line Qty From Loc To Loc
10000 1000 10 Stores Stage

Pick Confirm

You were instructed to find 10 units but could only find seven. A missing quantity is reported. When you asked the system to redetail the balance, the system could not find more quantity of the item (the results would be the same if you had not prompted the system to find the balance.) These tables show pick confirm data for sales order lines, delivery lines, move order lines, and move order line details.

Sales Order Lines
Line Quantity
1.1 10
Delivery Lines
Line SO Line Qty MO Line Staged Qty Status Subinventory
100 1.1 7 1000 7 Staged Stage
101 1.1 3   0 Backordered  
Move Order Lines
MO Line Req Qty Detailed Qty Delivered Qty
1000 7 7 7
Move Order Line Details
Line MO Line Qty From Loc To Loc
100 1000 7 Stores Stage

Ship Confirm

You now ship confirm the seven units that were available to ship in the staging location. These tables show ship confirm data for sales order lines, delivery lines, move order lines, and move order line details.

Sales Order Lines
Line Quantity
1.1 10
Delivery Lines
Line SO Line Qty MO Line Staged Qty Status Subinventory
100 1.1 7 1000   Shipped  
101 1.1 3     Backordered  
Move Order Lines
MO Line Req Qty Detailed Qty Delivered Qty
1000 7 7 7
Move Order Line Details (MMTT)
Line MO Line Qty From Loc To Loc
100 1000 7 Stores Stage

Backorders and Over Picking

After pick-confirm step, the picked quantity should always be greater or equal to the requested quantity.

If not enough quantity was picked, the delivery line will be split at pick confirm. The delivery line will be updated to Staged with the picked quantity and a new backordered delivery line will be created.

If a delivery line is fulfilled by the picked quantity and there is a pending quantity, a new delivery line pending over pick is created.

When either one of the picked quantity or the pending quantity is null the following rule is used to handle delivery lines:

Consolidating Backorders

Consolidation of backordered delivery details can be performed systematically during pick release, cycle count, and ship confirm. The option to consolidate backordered lines is controlled using a Global Shipping Parameter named Consolidate Backordered Lines. If you enable the Consolidate Backordered Lines parameter, then any delivery line that was split and subsequently backordered will be automatically consolidated with other backordered lines that it was part of originally.

When this feature is enabled and a backorder occurs, Oracle Shipping Execution searches the database for existing delivery line backorders for the particular detail line. If an qualified existing backorder is found, then the current backordered delivery detail is consolidated with the existing backordered delivery detail. However, a backordered line that remains packed after backordering will not get consolidated.

See: Consolidating Backorders, Oracle Shipping Execution User's Guide

Backorders and Cycle Counting

The ability to identify and remedy inventory discrepancies as part of the picking and shipping process is available in Oracle Shipping Execution.

The process to send a reservation to cycle count and backorder lines that were released as a result of discrepant inventory is as follows.

Within the Shipping Transactions form:

  1. Select a line with a pick status of staged.

  2. Select Cycle Count from the action menu.

  3. Click Go.

    The Transfer to Cycle Count window opens. In this figure, the delivery has a delivery detail with a requested quantity of two.

    Transfer to Cycle Count Window

    the picture is described in the document text

    If you enter a quantity less than two, then the delivery detail will split as one staged, and one backordered.

    If you enter a quantity of 2, then the delivery will be completely backordered.

    In both cases the reservation for the quantity that you see backordered, is transferred to cycle count. This can be verified from the inventory Supply/Demand form.

    There are two other ways to transfer backordered quantities to cycle count:

    • There is a radio button titled Cycle Count All under the Ship Options in the Confirm Delivery dialog box. By selecting this at ship confirm, the reservations for all lines in the delivery will be transferred to cycle count and the entire delivery will be backordered.

    • In the unspecified quantities drop down box there is a Cycle Count selection. By choosing cycle count from here, any line that does not have a shipped quantity specified will be backordered and the reservation transferred to cycle count.

      Note: If a delivery line is Firm status (planned delivery line) and you transfer the line to cycle count, the delivery line will be un-assigned from the delivery.

Order Management and Shipping Execution Line Status

Oracle Order Management and Oracle Shipping Execution provide line statuses to best reflect the stage of the process for the order line and delivery line.

This section covers the flow and definitions of the order line and delivery line status from time of order entry to invoice.

Three tables are provided at the end of this chapter to serve as a quick reference for viewing actions and associated line status within the Order Organizer, Sales Orders window, and Shipping Transactions form.

Standard Line Status Flow (also includes PTO)

Oracle Order Management captures the order line status in the Sales Order Pad on the Line Items Main tab in the Status field and in the Order Organizer on the Summary and Line tabs. Oracle Shipping Execution displays the delivery line status in the Shipping Transactions form on the Lines/LPN Main tab in the Line Status field and in the Quick Ship window in the Line Status field within the Delivery Lines/LPNs region. For a standard flow the statuses are:

Begin by placing the order in Order Management (OM):

Navigating to Shipping Execution, the delivery line status flow is:

Navigate back to Order Management and query the order that results in Order Management pulling updated pick release information from Shipping Execution:

Shipping Execution passes the status information to Order Management when ship confirm is complete:

Scenario

The following scenario will emulate a standard customer order from the first customer call to the invoice. The line status will assist the customer service agent on the shipper's side to answer the questions of the customer.

Entered Status (OM)

A customer calls and begins placing an order with the customer service representative. The customer is unclear whether or not the order is complete and indicates that he or she will call back to finish placing the order. The customer service representative saves the order to capture the current information but will not book the order, because the customer has indicated that the order is not complete. Both the order header and the order lines associated with the customer call will have the status of Entered once the order is saved. The line on the order exists in the system and can be queried when the customer calls back to complete the order. The following window illustrates the Sales Orders window with a status of Entered.

Sales Orders Window - Status: Entered

the picture is described in the document text

Booked Status (OM)

The customer service representative receives a second call from the customer. The customer indicates that the order is complete, so the customer service representative books the order. The following window illustrates the Sales Orders window with a status of Awaiting Shipping.

Sales Orders Window - Status: Awaiting Shipping

the picture is described in the document text

In the Order Information tabbed region, the order status is Booked, as shown in the following graphic.

Sales Orders Window, Main Tab - Status: Booked

the picture is described in the document text

Ready to Release Status (SE)

Once the order has been booked, the information passes to Shipping Execution. Order lines appear as delivery lines. Initially, it is a one to one ratio of order line to delivery line.

The customer service agent calls the warehouse to ensure that the order that was just booked has appeared in Shipping Execution. The warehouse clerk queries the delivery lines by the order number provided by the customer service representative and indicates that the line status is Ready to Release indicating the delivery lines are eligible for pick release. The customer service representative has been assured that the booked order lines are visible in the Shipping Transactions form and are ready for the next step, pick release. The following graphic illustrates the Ready to Release status on the Lines/LPNs tab in the Shipping Transactions form.

Shipping Transactions Form - Status: Ready to release

the picture is described in the document text

Staged/Pick Confirmed and Released to Warehouse statuses (SE)

The warehouse clerk launches pick release. Upon querying the delivery lines by order number, the warehouse clerk will see that the pick release status is Staged/Pick Confirmed for those delivery lines that have received allocation and pick confirmed successfully and Released to Warehouse for delivery lines that require a manual pick confirm or have not been allocated. The following graphic illustrates the Staged/Pick Confirmed status on the Lines/LPNs tab in the Shipping Transactions form.

Shipping Transactions Window - Status: Staged/Pick Confirmed

the picture is described in the document text

Picked and Awaiting Shipping Statuses (OM)

The customer who placed the order calls up and wants to know the status. The customer service representative queries up the order in the Order Organizer and finds that the status of the sales order lines are Picked and Awaiting Shipping. The customer service representative is equipped to report that the order lines are processing smoothly as they have been picked from their source location and transferred to the staging location within the warehouse. The following window illustrates the Picked and Awaiting Shipping statuses on the Line Items Main tab in the Sales Orders window.

Sales Orders Window - Status: Picked

the picture is described in the document text

Closed Statuses (OM)

The warehouse clerk has just ship confirmed the delivery associated with the delivery lines corresponding to the customer's order. The warehouse clerk used the check boxes on the Ship Confirm window to automatically set the delivery In Transit and close the trip automatically. Order Management is updated through the Process Order API and the order lines that previously had the status of Picked will now show a status of Closed.

The customer calls back to check the status of the order, the customer service representative can tell the customer the date(s) that the order lines physically shipped from the warehouse. The following window illustrates the Closed and status on the Line Items' Main tab in the Sales Orders window.

Note: For a short time immediately following ship confirm, the order line status will show as Shipped while OM interfaces with Receivables so that the customer can be invoiced. When the interface to Receivables is completed the line status in Sales Orders window changes to Closed.

Sales Orders Window - Status: Shipped/Closed

the picture is described in the document text

ATO Line Status Flow

A customer calls up Computer ABC and orders a laptop computer with a 56k modem and 64 mb of memory. This order will be processed as an Assemble to Order (ATO) item. The line status flow will be:

Bill Only Line Status Flow

A customer calls up to place an order for Service that is a non-shippable item. The line status flow of this order will be:

Returns Line Status Flow

Drop Ship Line Status Flow

Order and Delivery Line Statuses

These tables show the status of order lines and delivery lines after you perform certain actions. They show information for the Order Organizer, Sales Orders window, Shipping Transactions form for deliveries and delivery lines, and Shipping Transactions form for stops and trips.

How to read the lines in the table:

Immediately after you autocreate a delivery, the status of all the entities will be as listed in the Create Trip column of the table.

Exception Handling

Export Compliance Screening Concurrent Program

This program can be used to progress any lines that are waiting at the Export Compliance Screening Eligible activity. The provided parameters such as Customer or Order Number can be used to refine the selection criteria for the lines. For example, if you have many orders for a customer that has come up with the same data errors, then you can fix the customer data and progress all lines for that customer.

Miscellaneous Shipments

Miscellaneous Shipments enable you to ship confirm deliveries that are not tied to (or did not originate from) a sales order, or have been sent via XML Shipment Request from a legacy order management system to Oracle Shipping Execution. XML support enables Oracle Shipping Execution to return an XML Shipment Advice message back to a legacy OM system to confirm the shipment.

XML Shipment Request is an XML message that is sent to Oracle Shipping Execution. It is the equivalent of the EDI transaction 940 Inbound. Oracle XML Gateway is used to generate the XML messages (both Shipment Request and Shipment Advice). Miscellaneous shipment deliveries can be combined in a trip with OM-originated deliveries.

The functionality of miscellaneous shipments is the same as Oracle Order Management-originated deliveries.

The following restrictions exist when using miscellaneous shipments with Oracle Shipping Execution:

Oracle XML Gateway, along with Advanced Queuing, must be installed. The WSH organization must be defined as a Trading Partner. (The supplier site Shipping organization must be defined as a Distributed organization).

Oracle Workflow is required for notifications.

XML Used with Miscellaneous Shipments

Shipment Request: Shipment Request transaction (the XML equivalent of the ASC X12 940 transaction) is a modified version of the Open Applications Group (OAG) document type definition (DTD) show_shipment_005. This DTD is used to send shipment information from Oracle Shipping Execution to a 3rd party order management system (or legacy system). These transactions contain all pertinent information for the delivery.

Shipment Advice: Shipment Advice transaction (the XML equivalent of the ASC X12 945 transaction) is a modified version of the OAG DTD show_shipment_005. This DTD is used to send shipment information from a 3rd party order management system (or legacy system) to Oracle Shipping Execution. The Shipment Advice transaction sends all pertinent information for the delivery.

Data Flow

The following graphic describes the data flow when Shipment Request is used to send information from a third-party order management system to Oracle Shipping Execution.

the picture is described in the document text

The following graphic describes the data flow when Shipment Advice is used to send information from Oracle Shipping Execution to a third-party order management system.

the picture is described in the document text

RFID-EPC Compliance

If you enable Oracle Warehouse Management, Radio Frequency Identification (RFID) can be used in the shipping process through the ship confirm process. RFID is a technology for tagging physical items with a unique ID that can be easily and non-invasively read, like a "wireless bar code". The Electronic Product Code (EPC) is a numbering standard for the unique identification used within RFID tags. RFID-EPC supported in the Shipping Execution enables you to select the LPN format and the printer associated to print a RFID tag, track the EPC associated with an LPN ID, and provide the EPC in the Departure Ship Notice Outbound (DSNO) file.

See: Oracle Warehouse Management User's Guide for more information on RFID-EPC.