Shipping ExecutionYou can manage shipping information such as trips, trip stops, deliveries, delivery lines, containers, and freight costs in the Shipping Transactions form. In addition, you can complete the following shipping tasks:

Pick Release■ Release eligible delivery lines based on defined picking criteria.■ Select the Release Sequence Rule to control the order in which picking lines are allocated to inventory.■ Enter or validate shipped quantities, back ordered quantities, staged quantities, and inventory control information for delivery lines (after pick release).

Trip and Delivery Planning■ Create a trip or delivery.■ Assign delivery lines to a delivery or a container.■ Schedule pick-ups and drop-offs.

Ship Confirm■ Assign delivery lines to trips and deliveries.■ Auto-create a trip and close stops.■ Ship confirm or back order a delivery.

Pick ReleaseThe pick release process creates move orders which are pre-approved requests for sub inventory transfers to bring material from its source locations in the warehouse (stores/fg sub inventory) to a staging sub inventory.

1. If auto allocate and auto pick confirm both are set to NO then pick release does nothing except creating the move order.If the auto allocate is set to yes in release rule with the ware house and sub inventory name then pick process also does a reservation of the item in the pick from sub inventory. During the process of reservation in scheduling a demand line is created and can be seen in reservation form. At thaat point of time the system only does the reservation with type Inventory and w/o specifying the subinventory and locator. During pick release allocation/detailing the system populates the subinvenory and locator if applicable.If the auto pick confirm process is set to yes then pick release process also does the transact move order and at the end of pick release process the material moves automatically to the staging sub inventory. In this case the delivery line status in SE changes from ready to release to staged/pick confirmed but if either of the auto allocate/auto pick confirm is set to NO, then the status changes to released to ware house and the user needs to manually transact the move order created by the pick release process.

2. If there is no onhand then the order is back ordered and no move order is created. If there is not sufficient onhand then a move order is created for the available onahand and the delivery line splits in SE form.

3. Pick Slips can be created after the detailing process completes, and the quantity and source can be manually verified at pick confirm. Pick slip report contains the SO (line, item, quantity, ship set), Mover Order, Delivery and Trip numbers. A custmozied bill of lading & packing slip can be generated after this if required.

4. You can run one or more releases and customize release criteria to meet your requirements. You can define:■ Release Rules to specify your picking criteria and set the default Release Rule through Shipping Parameters Pick Release tab.

■ Release Sequence Rules to specify the order in which eligible delivery lines are allocated during pick release.■ Pick Slip Grouping Rules to determine how released move order lines are grouped onto pick slips.

Picking RulesMove orders will use the picking rules set up in Oracle Inventory to locate the material required to fulfill the move order line. Together with item-sub inventory defaults (required if the staging sub inventory is locator controlled), the pickingrules suggest the staging transfer transaction lines with appropriate source information that will be required to obtain enough material in the staging location for the delivery. The process where the Picking Engine generates these transactionline suggestions is called allocating.

When you define an item you choose a picking rule to determine the order in which revisions, lots, subinventories, and locators are picked for sales orders. Oracle Shipping Execution submits requests to Oracle Inventory, which uses the information you enter in the Picking Rules window to generate pick lists for sales orders. If you choose None for any of the criteria fields, Inventory ignores that criterion. For example, if you choose None for Revision, Inventory picks units of an item without regard to revision levels. Oracle Inventory looks at the picking criteria in the order in which they appear in the Picking Rules window. Then, Inventory looks at the options (except for None options) for each criterion in the order inwhich they appear beneath each criterion.

Note: If you utilize Oracle Transportation, compatibility constraints can be used in the shipping process up through shipconfirmation. Compatibility Constraints enable you to define a variety of transportation related restrictions related to items (goods for shipment), carriers, modes of transport, facilities, organizations, and customers. Then, these restrictions are used by the application to warn or prevent further order processing if the defined undesirable condition is encountered. For example, you can define an item-carrier compatibility constraint stating that designated carriers cannot transport specific inventory items. When a delivery is created violating the constraint, an error or warning message will be

generated. You determine the severity of the constraint violation; whether a warning or error should display.

Staging LocationsThe destination sub inventory for a pick wave move order is the staging location into which the picked material should be deposited. Each organization should designate at least one staging sub inventory. Staging sub inventories should bereservable. Each batch created at pick release will have the same destination staging sub inventory. The default staging sub inventory and locator to be used for all pick wave move orders are specified through Oracle Shipping Execution’s ShippingParameters window. This location can be changed at pick release. To model different staging lanes within the staging area, facilities may choose to either create different sub inventories or designate staging lane locators within one staging subinventory.

Pick Release from shippng transaction formAll the pick release setups can be done so that users can easily do pick release form shipping transaction form.once you do a pick cofirm system fires below requests

• Pick Selection List Generation • Pick Slip Report • Shipping Exceptions Report

When pick release is done from shipping transaction form, the system picks up the auto –allocate and create delivery set up from shipping parameter. If the Pick Confirmation Required box in the Organization Parameters window is not enabled then the system would also does the auto-transaction.Notes: Do not check the Pick Confirmation Required box in the Organization Parameters window. If you check this box, the Auto Pick Confirm parameter on the shipping tab of the Pick Release form will be set to No.To change this you would navigate to Setup -> Shipping -> Organization Parameters->'ATP, Pick, and Item-Sourcing tab

Defining Release RulesYou can create default pick release rules that are applied at pick release in the Release Sales Orders window. Each rule can be set up with its own set of unique pick release parameters depending on the pick release criteria required.When pick release is run, the pick release is performed based on the parameters set up in the selected pick release rule. For example, you can create a specific rule that pick releases only backordered lines.

Note: Although you can also enter the pick release criteria at pick release time without creating a rule, creating a rule is more efficient if you frequently run the same pick release. Also, note that it is required when releasing using SRS or when using the Auto Pick Pack and Ship features.

Release Sequence RulesYou can define release sequence rules to specify the order in which eligible picking lines are allocated to Inventory during pick release. Release sequence rules are given on "release sales order for picking" form and can be defaulted from release rule tab in shipping parameter or from the release rule it self.

Notes: While its not mandatory to provide the sales order number/delivery/trip while doing the pick release, its always advisible to do so to restrict the number of lines seleceted during pick release. The release sequence rule determines the priority given to selected lines while doing pick release.

You can release the picking lines by:■ Order number■ Outstanding Invoice Value■ Scheduled Date■ Departure Date■ Shipment Priority

You can assign a priority level to one or more attributes with 1 being the highest priority and 5 being the lowest. You can also define whether you want the picking lines released in ascending or descending order.

For example, if you select the Ascending button for Order, picking lines are released by ascending order number--Order 1 is released first, then Order 2, Order 3, and so on. If the Descending button is selected, the picking lines are released bydescending Order number from highest to lowest--Order 4 is released first, then Order 3, Order 2, and Order 1.

Pick Slip Grouping RulesYou can create grouping rules to organize how picking lines for released sales orders are grouped on to pick slips. For example, if you select Delivery as a grouping criteria, all picking lines for the same delivery are grouped together on a pick slip. If there are multiple deliveries, multiple pick slips are created. You can also define your grouping criteria further by selecting additional grouping attributes. For example, if you select Delivery and Carrier as grouping criteria, picking lines for the same delivery and carrier are grouped together on a pick slip.

Configuring Picking ProcessYou can determine the number of pick release steps the system will prompt to move material from pick release to ship confirmation. These steps are:

1. Pick Release2. Move Order Line Allocation (detailing)3. Move Order Line Pick Confirmation

Pick ReleaseOracle Shipping Execution’s Pick Release process creates move orders. One order is created per pick release batch per organization, so if you pick release across multiple organizations, one move order is generated in each facility. One moveorder line is generated for each order line included in the picking batch. That move order line includes the item, quantity, the staging location (the destination sub inventory and locator) and a source sub inventory and locator if one was specifiedon the sales order line or on the Release Sales Orders window.

For non-reservable items, allocation and pick release run, but suggestions are not created during pick release, and pick confirm will not run for the item. You can print pick slips, but they will not be detailed with subinventory and stock locator to pick from, however they will list the item and quantity to be picked. Auto-allocate should be Yes and Auto-pick-confirm can be set to any.

Detail Line Allocation (Detailing)To release the move order lines created at Pick Release to the warehouse and to print pick slips, the lines must be allocated. The allocation process for a pick wave move order line also creates a high level (organization level) reservation for the item(s) if no previous reservations exist for them. You can choose to do this immediately after the move order lines are created or to postpone this step until a later point in time. Once the lines are allocated, they have a status of Released toWarehouse.

The reservation is a soft reservation and from the transact move order form we can back order the move order line and the quantity would be available for reservation again.

Postponing the detailing process might be employed by organizations that pick release across multiple warehouses but prefer to enable each warehouse to determine when to release their order lines to the floor. Detailing the order lines immediately after they are created is called auto-detailing. Postponing the detailing process is referred to as manual-detail. You can set up a default detailing mode in the Shipping Parameters window. This default can be overridden at each Pick Release through the Release Sales Orders window.

Pick ConfirmationThe move order line details must be transacted (in Inventory) to confirm the material drop-off in staging. Pick confirmation executes the sub inventory transfer that systematically moves the material from its source location in the warehouse tothe staging location. Pick Confirmation automatically transfers the high level reservation to a allocated reservation (including lots, sub inventory and locators) in the staging location.Inventory updates Shipping Execution with the results of the pick confirm:■ Pick Confirmed quantity is assigned a status of Staged/Pick Confirmed.■ Unconfirmed quantity is assigned a status of Backordered.

Pick confirmation follows the allocation and reservation process automatically if both the Auto Allocate and Auto Pick Confirm options are selected in the Release Rules window. Pick Confirm always follows the detailing and reservation process.If Auto Allocate is not chosen, it is not possible to Auto Pick Confirm.

Create Delivery

A delivery consists of set delivery lines that are scheduled to be shipped to a customer's ship-to location on a specific date and time. In a delivery, you can include items from different sales orders as well as back orders. You can either manually or automatically group delivery lines to create a delivery. If a delivery is autocreated, the delivery lines are grouped together by the mandatory default criteria, ship-from location and ship-to location. However, additional grouping criteria can be included.

1.1 In operating unit level we can control the auto create delivery in shipping parameter.

1.2. Deliveries can be automatically created during the process of pick release by enabling autocreate delivery in pick release form.

1.3. we can manually create the delivery number in shipping transaction form.

2.1 Delivery parameters enable you to define how to group delivery lines for a delivery. The mandatory default attributes are Ship From Location and Ship To Location; however, you can select additional optional grouping parameters that include:

• Customer • Freight Terms • FOB Code • Intermediate Ship To location • Ship Method

The delivery attributes determine how delivery lines are grouped into deliveries when auto-creating deliveries. For example, if the grouping attribute Customer is selected, the delivery lines are grouped

into deliveries by customer: for example, deliveries for Customer A are grouped into Delivery A, deliveries for Customer B are grouped into Delivery B.

You can select more than one grouping attribute to refine your grouping criteria further: for example, if you select Customer and Ship Method as grouping criteria, delivery lines with the same customer and carrier criteria are grouped into deliveries.If each optional grouping attribute is checked, the delivery's corresponding field cannot be updated if delivery lines are assigned to the delivery. This ensures that the delivery lines' grouping criteria is not broken by a different attribute value: for example, if someone tries to select a different ship method.

If each optional grouping attribute is unchecked, its field in the delivery record can be updated until the ship confirm stage. For example, if you want to change the Ship Method in the delivery and do not need to enforce it as a grouping attribute, you can unselect Ship Method. Do not change these options if you have deliveries that are not ship confirmed.

Optionally, select a Autocreate Delivery Criteria if you enabled the Autocreate Delivery option on the Pick Release tab.

• Select Within An Order to autocreate deliveries whose lines all belong to the same sales order and match on the Delivery Grouping Attributes.

• Select Across Orders to autocreate deliveries across orders. All selected delivery lines that match on the Delivery Grouping Attributes are eligible to appear on one delivery.

Select an Appending Limit.The Appending Limit enables you to indicate the point at which you want to stop the system from adding lines to a delivery (the point that ends the ability to merge deliveries). You must set the Appending Limit to a value other than Do Not Append in order to use the Append Deliveries option within Release Rules and the Process Deliveries SRS.

The Appending Limits include:

• Do Not Append • Start of Staging • End of Staging

• Start of Packing (Oracle WMS enabled organizations only) • Start of Shipping (Oracle WMS enabled organizations only)

Managing Packing/Containers/LPNsIn the Shipping Transactions form, you can create and manage containers (LPNs) at any point in the shipping process. If you are using the Auto-packing feature, containers can be automatically packed using the container-item relationships setup in the Container-Item Relationships window. You can create containers without assigning them to a delivery. This is useful if you want to create multiple containers of the same type then pack them with unassigned delivery lines.

(Note: LPN is an acronym for License Plate Number. A packing container has a license plate number for unit identification and reporting capability, so containers are also called LPNs in Oracle Shipping Execution.)

Customer Items can be associated with containers within Oracle Inventory. This association is used when packing the Customer Item into a container in Oracle Shipping Execution. When the Customer Item is packed, the container associated with the Customer Item in Oracle Inventory is used as the default container.

You can pack multiple containers with multiple lines using one of the following packing methods:■ Auto-packing■ Manual packing■ Packing Workbench

• Equal packing: splits the delivery lines equally between the selected LPNs.You cannot use this method with delivery lines of serial controlled items.

• Sequential packing: fully packs one container at a time to its capacity (weight, volume, or quantity) before packing the next selected container.

1. Auto-packing Delivery Lines into ContainersAuto-packing provides a convenient and quick way of automatically packing delivery lines into containers (LPNs). The delivery lines are packed into LPNs based on the container-item relationship set up in Oracle Shipping Execution or in OracleInventory (defined as a customer item) and the setting of the Shipping parameter Percent Fill Basis must be set to Quantity. The container-item relationship defines the container that is used for packing the delivery lines. If Percent Fill Basis is set to Quantity, then auto-pack will look at Container-Load Relationships set up for the item and the Detail Container.If multiple container-item relationships exist for the same item, the Preferred setting in the Container-Item Relationships window indicates the default container-item relationship used for that item. Auto-packing can also be performed for those items in Oracle Inventory that are defined as Customer Items.

Using the Auto-pack Master Option■ If you select Auto-pack, then only the detail LPNs are created and packed. ■ If you select Auto-pack Master, the delivery lines are packed into the detail container, and the detail containers are packed into the parent/master container in one action:For example, a delivery line with a quantity of 12 of Item A has a container-load relationship set up so that 6 of Item A fits into Container A and 2 of Container A fits into Container B (the percent fill basis is set to quantity). If you run Auto-pack Master, the line is split into 2 lines of 6, the first line is packed

into the first container, the second line is packed into the second container, and the two detail LPNs (2 Container As) are packed into Container B.■ The Auto-pack Master option is available from the Actions menu in the Lines/LPNs tab in the Shipping Transactions form. It is also available at the delivery level1. Container type setups are done in inventory -> Setups ->Item ->Container

2. Crate a container Item in item master.

3. Shipping > Setup > Container Load Details > Organizations > [OK]

4. Auto pack it

2. Manual packing Delivery Lines into ContainersIt involves two steps i. Creating an LPN

ii. Assign LPN to lines/deliveries

3. Packing Work Bench Lines into Containers

Container setups and processSetups1. Create containers Items -> Master Items

Coose the Inventory Organization

Under Main tab, Primary UOM: Each, Item Status: active

Under Pysical AttributesWeight UOM: Pounds, UnitWeight: 1, Voulme UOM: Cubic Foot, UnitWeight: 1, Container Flag: Checked, Container Type: Choose a value from the LOV,Internal Volume: 2, Maximum Load Weight: 2, Minimum Fill Percent: 50

under Order Management tabShippable flag: Checked

Assign it to the inv organization.

2. Define a Ship-Container Load Relationship OM Responsibility: Shipping -> Setup -> Container Load Details

Container Item, Load Item, Maximum Quantiyt, Preferred Flag

Process Flow1. Creating LPNs On the shipping transaction formActions: Select Create LPNs and Click on Go buttonIn the LPN form enter Inventory Organization short name, Name Prefix, Base Number and Click on Ok.Check the LPNs names created and Close the form.

2.1 Manual Packing Delivery Select Order line 1Actions: Select Pack option and Click on Go buttonSelect the created container from the LOV.On the shipping transactions form, for the line 1, click on Details button

Check values for Line, Delivery, Parent LPN, Master LPN.

Parent LPN should be the one you selected above and Master LPN could be Null or the same value as above

Click on Done button

2.2 Auto-pack Delivery 2 Select Order line 2Actions: Select Auto-Pack option and Click on Go buttonClick on Details buttonCheck values for Line, Delivery, Parent LPN & Master LPN.Parent LPN should be the one genreated by the system and Master LPN could be Null or the same value as aboveClick on Done button

2.3 Full Manual Packing Delivery line 3Select Order line 3 Select (using CTRL-Click) couple of small LPNs not assigned yet Actions: Packing WorkbenchClick on Go button

Under LPNs tab check pack column for all selected lines Check Available Capacity

Change to Lines tabCheck Pack column only for line of delivery 3.

Packing mode : Choose Full optionCheck Item Total values at the left of the screenClick on Pack button

Actions: Select Packing workbench again and Click on Go Under LPNs tab Select each of the LPNs selected above

Check the Context section under same tab, for each one of the LPNs, it should be also one line under content. Check Item Name and Quantity

Overview of TripsA trip is an instance of a specific freight carrier departing from a particular location containing deliveries.

1. A trip is carrier specific and contains at least two stops such as a stop to pick up goods and another stop to drop off goods, and may include intermediate stops. Trip stops are displayed in sequence on the Stops tab within the Shipping Transactions form once you have queried your trip. The Stop sequence will not re-sequence if a stop is removed. For example, if you have two stops, each with an arrival and departure date and time, and you remove one, the remaining stops will stay in the same sequence as they were originally.

2. A trip can contain more than one delivery.

3. Trips can be created automatically or manually.

4. You can perform the following tasks with trips:■ Create a trip■ Plan a trip■ Unplan a trip■ Assign freight costs to a trip■ Print a document set for a trip■ Calculate weight and volume for a trip stop■ Ship confirm a trip

Creating a TripYou can create trips automatically or manually.

AutomaticTrips are required for all deliveries and can be created automatically as part of Ship Confirmation transparent to the user for those not interested. If your shipping process does not require advanced planning, you may prefer to automatically createtrips:■ Auto-creating a trip for a delivery: You can find the delivery you want to ship, and auto-create a trip

and related trip stops.■ Auto-creating a trip for containers and lines: You can find the lines and containers you want to ship and auto-create a trip which creates a trip, related deliveries, and trip stops.

ManualYou can manually create a trip and later assign delivery lines or find the delivery lines and create a trip. For example, for a regular trip scheduled to depart every Friday, you can manually set up a trip ahead of time and then assign delivery lines.When you manually create a trip, you can manually assign stops, deliveries, and delivery lines to that

To manually create trip, navigate to shipping transaction query manager form and enter the Trip Name, vechile org code and ship method.Once the trip is saved the stops tab in the form gets enabled and stops can be enter over there.

Firming a TripOnce deliveries and delivery lines have been assigned to a trip, you can set the status of the trip to one of the following:■ Firm Routing: Prevents trip stops from being added, or removed for the selected trip.■ Firm Routing and Contents: Prevents trip stops from being added, or removed for the selected trip and prevents contents from being added or removed. If the trip status is Firm Routing, you can still update trip details, delivery, anddelivery line information. For example, you can add delivery lines and make changes to the delivery. However, to add or remove trip stops, you first must set the status of the trip to Unfirmed before making the changes.

When you firm a trip, Shipping Execution performs the following:■ Validates that the sequence numbers between the deliveries of the trip are unique for containers within the deliveries■ Validates that the weight, volume, and fill percentage do not exceed their maximum number of containers in the delivery■ Validates that the minimum fill percentage is met■ Validates the planned arrival date and planned departure trip dates are not in the past■ Validates pick-up and drop-off dates and times with the Transportation Calendar for the shipper, carrier, and receiver

Unfirming a TripWhen a trip is in Firm Routing or Firm Routing and Contents status, you cannot add, remove, or re sequence trip stops unless you first Unfirm the trip. When the trip is in Not Firm status, you can remove or rescreen existing trip stops or add new stops.After the changes are done, the trip can be Firmed to prevent the trip stop settings from being changed. However, if you leave the trip Not Firm, the existing trip stops can be removed or new trip stops can be added.When you unfirm a trip, Shipping Execution:■ Sets the status of all deliveries in the trip to Open.■ Sets the status of the trip to Open

Assigning Freight Costs to a TripYou can assign freight costs to a specific trip, override the suggested freight costs, or update existing freight costs. For example, if you wanted to add additional costs to a particular vehicle that is used in the trip to deliver goods. A freight cost can also be assigned to a delivery, a stop, a delivery leg, a delivery detail, or a container.

Printing a Document Set for a TripYou can print a group of shipping documents and other reports in a set. These document sets can include pick release documents, all shipping documents, and pack slip information.

To print a document set for a trip:1. Navigate to the Query Manager window, and find the trip.2. From the Actions menu, select Print Document Set, or if you have added a Print Document Set

button, click it.

Ship ConfirmShip confirm is the process of confirming that items have shipped. When you ship confirm a delivery, Shipping Execution confirms that the delivery lines associated with the delivery have shipped.

You use the Confirm Delivery window to manually select or deselect ship confirm options. The options in the Confirm Delivery window provide flexibility for automating many tasks associated with processing deliveries with many delivery lines. For example, when the Ship Entered Quantities, Unspecified Quantities Ship option is selected at ship confirm, the shipped amounts are automatically processed so that each delivery line with a missing shipped quantity value is recorded as fully shipped. This saves you from manually entering each item as fully shipped.

Once you do SHIP CONFIRM. Then four concurrent program will run in the background .1. INTERFACE TRIP StopThe “Interface Trip Stop” process is executed either real time or later as a concurrent request. Typically, the process accomplishes three main objectives:i. Deducts on-hand quantity and debits Cost of Goods Sold.ii. Progresses the order line to “Shipped” status so that it can progress to the next workflow activity. iii. Progresses the shipment line to an “Interfaced” status and sets the trip to “In-Transit” or “Closed” depending on whether you elected to close the trip.2. Packing Slip Report3. Bill of Lading4. Commercial Invoice

If you dont defer interface (i.e. defer interface is not enabled in ship confirm form) then ITS runs after the ship confirm and it does the above 4 activites but if you enable defer interface then ITS wont be automatically fired after ship confirm and the sales order line remains in picked status. After ITS run the SO line status changes to shipped and after workflow back ground completes it goes to Fullfill and finally to AR interface

Ship Confirm A DeliveryShip Confirm is the process of recording that items have shipped. When you ship confirm a delivery, Shipping Execution confirms that the delivery lines associated with the delivery have shipped.

The prerequisites are

• Delivery lines must be released. • Delivery must be open.• At least one delivery line must be assigned to the delivery.

To ship confirm a deliveryNavigate to the Query Manager window, and find the delivery.The delivery displays in the Shipping Transactions window.From the Actions menu, select Ship Confirm to display the Confirm Delivery window.

1. In the Ship Options region, select one of the following ship confirm options:

-Ship Entered Quantities, Unspecified Quantities Ship: Ship confirms the quantity of items specified in the Shipped Quantity field and treats blank values as full quantity (shipped quantity = requested quantity). For example, if the Requested Quantity is 10 and the Shipped Quantity field is blank (no values entered), the full quantity (10) is shipped and displays in the Shipped Quantity field. -Ship Entered Quantities, Unspecified Quantities Backorder: Ship confirms the quantity of items specified in the Shipped Quantity field and treats blank quantities as full backorders (backorder quantity = requested quantity). For example, if the Requested Quantity is 10 and the Shipped Quantity field is blank (no values), the full quantity (10) is backordered and displays in the Backordered Quantity field. -Ship Entered Quantities, Unspecified Quantities Stage: Leaves the unspecified delivery line quantity as staged and removes it from the delivery. For example, if the Requested Quantity is 10 and the Shipped Quantity field is blank (no values), the full quantity (10) remains in the Stage Quantity field and the line is no longer associated with a delivery. Note: If a non-zero Stage Quantity exists on a line, it is split from the line and unassigned from the delivery. If the Create Delivery for Staged Quantities is enabled, all staged delivery lines are grouped together in a new delivery. -Ship Entered Quantities, Unspecified Quantities Cycle Count: Ship confirms the quantity of items specified in the Shipped Quantity field, treats blank quantities as full backorders (backorder quantity = requested quantity), and transfers the backorder reservation to cycle counting. For example, if the Requested Quantity is 10 and the Shipped Quantity field is blank (no values), the full quantity (10) is backordered and transferred to cycle

counting. You can also transfer delivery quantities to cycle count prior to ship confirm by using the Shipping Transactions form, Cycle Count action. -Ship All: Ship confirms the entire quantity regardless of what was entered in the Shipped Quantity field (shipped quantity = requested quantity). For example, if the Requested Quantity is 10 and the Shipped Quantity field is 5, the full requested quantity is shipped (10) and displays in the Shipped Quantity field. -Backorder All: Backorders the entire quantity irrespective of what was entered (shipped quantity = 0, backorder quantity = requested quantity). -Cycle Count All: Backorders the entire quantity irrespective of what was entered (shipped quantity = 0, backorder quantity = requested quantity)and transfers the backorder reservation to cycle counting. You can also transfer delivery quantities to cycle count prior to ship confirm by using the Shipping Transactions form, Cycle Count action.

2. Enable the Create Delivery for Staged Quantities box (default setting), if you want all staged delivery lines grouped together in a new delivery. If you do not want to create a trip for the delivery, choose the Go button to shipconfirm and save your work.

3. In the Auto-create Trip Options region, select or update the ship method and the actual departure date. This allows you to specify the stop departure date which also updates Inventory. The simplest way to ship confirm one or more deliveries is to enable the Set Delivery in-Transit and Close Trip fields in the Confirm Delivery window: Set Delivery In-transit: Creates a trip and stops for the delivery. Closes the first stop of the delivery, but leaves second stop open. Sets status of delivery to In-transit and initiates Order Management (OM) and Inventory interfaces.Close Trip: Creates a trip and stops for the delivery. Closes trip, all stops, and the delivery.You can enter a future Actual Departure Date. If Allow Future Ship Date in the Shipping Parameters form, Shipping Transactions tabbed region, is cleared, do not do so as you receive an error. If Allow Future Ship Date is selected, yourecieve a warning and the Inventory Interface concurrent process does not process the transaction until the actual departure date.Enable the Create Bill of Lading box if you want to create a Bill of Lading.This generates a Bill of Lading number and prints it if it is part of a document set.Choose one of the following -If you disable the Defer Interface box and run Ship Confirm, inventory gets decremented and the order line is updated with the shipped quantity. -If you enable the Defer Interface box and run Ship Confirm, you need to run the Interface Trip Stop-SRS concurrent request to update the Inventory and the Order Line status. When the Defer Interface box is enabled, a request is not automatically submitted to interface the trip stops.

4. Select the document set you want printed for the delivery and choose the OK button. A trip and related stops are created for the delivery. Save your work.

Fulfillment ActivityThe fulfillment activity acts as a synchronization point for all lines on the order that are in a fulfillment set. The lines in the fulfillment set will wait at the fulfillment activity until all the lines in the set have reached the activity. Lines that are not in a fulfillment set simply pass through the activity.

Once the Fulfillment activity completes, a Background Workflow Process processes the order line(s) to the Invoice Interface activity. The invoice interface activity places the information from the sales order line into the Receivables Interface tables. When the information is written to the tables, the invoice interface activity is complete, and the line proceeds to the close line activity. However, note that the invoice is not actually generated until the Autoinvoice program in Receivables has been run. The invoice will then be viewable in the Sales Order window.

OverviewTo fulfill an order line in Oracle Order Management means to satisfy the requirements for completion. Order Management provides the functionality required to recognize fulfillment of an order line, and to cause some order lines to wait until other related order lines have been fulfilled before processing can continue.Order Management's fulfillment functionality provides a simple way to synchronize line workflows for multiple order lines. It allows you to prevent invoicing of lines within a fulfillment set until all lines are ready for invoicing. Seeded workflowprocesses and activities can be used to provide baseline functionality for sales order, drop ship and return lines. The functionality is also designed to allow you the flexibility to define other activities as fulfillment methods so that you can model your unique business processes.

Order Management allows you to group lines into a fulfillment set and to establish a gate activity in your workflow process. Lines in a fulfillment set will wait until all lines in the set have been fulfilled to proceed through the gate. This gate is known as the fulfillment activity. The fulfillment feature is primarily designed to allow the grouping of related lines and to keep any lines in the group from being invoiced until all lines have been fulfilled. You may find additional uses for the fulfillment functionality in your business.

How It WorksThe fulfillment activity is a seeded workflow activity named FULFILL. This activity is the synchronization point between the lines of a fulfillment set. There are two activities which are considered fulfillment method activities (workflow attribute) in seeded Order Management workflows.• For a standard shippable line the fulfillment method activity is the shipping activity.• For a return line the fulfillment method activity is the receiving activity.

You may define any activity as the fulfillment method activity in a workflow process. The fulfillment activity must be between the fulfillment method activity and the invoice interface activity in the respective workflows. When a line workflow reaches the fulfillment activity, the activity checks to see if the fulfillment method activity (for example, shipping or receiving) completed successfully. If the line completed successfully, the fulfilled quantity for the order line will be updated with the shipped or received quantity, and the order line fulfilled Order Management Processes 5-5 flag is set to Yes. The fulfillment process then performs a check to verify if the line is part of a fulfillment set:• If the line is not part of a fulfillment set, then the order line completes the Fulfillment activity and continues with the next activity within its order line workflow process.• If the line is part of a fulfillment set, the fulfillment process performs an additional check to verify if remaining lines within the set have been fulfilled:

If any lines within the set are not fulfilled, the order line will wait at the fulfillment activity.If all lines within the set are fulfilled, the order line completes the fulfillment activity for all the lines within the fulfillment set.

SetupNo setup is required to use the fulfillment functionality with the seeded workflows. If you create your own workflows, include the fulfillment activity before invoicing in each process. This will provide two benefits: Update the fulfilled quantity for the lines and enable you to use fulfillment sets.

Change Orders in Oracle Shipping ExecutionIn 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.

Prior to the Order Management Change Management design, changes to pickable orders were allowed as long as the orders were not booked or interfaced with Oracle Shipping Execution. However, once the orders were interfaced into Shippingand Pick Released, changes to the sales orders were limited. 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 with 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.

The following table lists sales order line changes resulting from Order Management updates. The change category letters correspond to Shipping Execution change logic as follows:

• ■ A: Change in Quantity • ■ B: Change Organization, Inventory and Unschedule • ■ C: Change in Schedule Date • ■ D: Change in Ship Sets or Arrival Sets • ■ E: Change in Delivery Grouping Attributes

Change LogicBefore changes are considered, all line imports and line splits must be processed. The WSH_INTERFACE holds, in any order, the 3 types of entries from Order Management interface API call:■ Requests to Import lines and create matching deliveries (I - Import)■ Split existing delivery lines (S - Split)■ Order Management changes request to Update Shipping Attributes (U - Update)Shipping scans all entries through WSH_INTERFACE to process Order Management entries in the proper order. The Shipping change validation logic is initiated for interface lines where the action flag value is set to U for Update.When a change is requested, the attribute change category is evaluated to determine what type of validation and action is needed to successfully update the Shipping attributes.

Order and Delivery Status MappingThe following table shows the correlation between Sales Orders in Order Management and the related Shipping Deliveries status. Changes to sales order lines not interfaced from Order Management to Shipping are not restricted by Shipping. For sales order lines interfaced from Order Management to Shipping, changes are allowed based on attributes updates if the deliveries are not closed. No changes are allowed for Confirmed or Shipped deliveries if the interface between Shipping and Order Management has not run to update the sales orders.

OM-WSH Interface to Import Attribute ChangesOrder Management initiates a change by passing updated sales order data to Shipping and setting the Interface Action flag to the Update value. Shipping processes all interface data by:■ Importing order lines to create delivery line details for newly inserted records. (I)■ Processing Split request for existing delivery lines. (S)■ Shipping change validation determines what attributes have been changed. (U)Based on the attributes changed, distinct validations are applied to propagate the order changes to Shipping delivery lines.

Shipping Attribute Change Validation LogicThe change validation logic is initiated for WSH_INTERFACE.Update_Shipping_Attributes lines where the Action Flag is set to U. The distinct attribute changes that need validation are classified in the following categories:■ Change in Quantity■ Change Organization, Inventory, and Unschedule■ Change in Schedule Date■ Change in Ship Sets or Arrival Sets■ Change in Delivery Grouping AttributesChanges to other attributes are propagated if the delivery status is not Shipped or Staged/Pick Confirmed.Existing and new inventory reservations are managed by Shipping as detailed in the following section.

Inventory Reservations LogicThe Inventory reservation logic was redesigned so shipped quantities can always be matched with existing reservations during Inventory interface after Ship-confirmation. The reservations tables are part of the Oracle Inventory product.Inventory internal Applications Program Interfaces (APIs) are used to create, update, or cancel reservations stored in the Inventory tables. These APIs are called by Order Management and Shipping

code to manage reservations and reservationsplitting.Reservation management by Order Management and Shipping:■ When an order is booked, the Order Management code creates reservations by calling Inventory APIs.■ After the order lines are interfaced in Shipping, existing Inventory reservations are managed in Shipping by calling Inventory APIs.■ Order Management does not update reservations with changes after booking.Instead, Shipping updates, creates, or deletes reservations for changes originated in Order Management.■ Overpicked quantities do not have existing reservations when orders are interfaced. Shipping creates additional reservations so all picked inventory items can be tied to the reservation.

Delivery Line SplitWhen 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 not ship confirmed.■ Delivery lines Released to Warehouse are reset to Ready to Release and their move order lines are canceled■ Reservations are split ■ Both proportional and non-proportional splits retain and split original serial numbers

SetupsThere are no mandatory setups to enable the Change Management functionality. Order Management provides constraints that can be customized during implementation. These constraints are used to prevent sales order changes after theassociated 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 toalways make sure 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 ConstraintsOrder 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 step. Once the delivery lines have been pick confirmed/staged in Shipping Execution, Order Management users are not allowed to change, cancel or split orderlines.

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.

Changing DefaultsTo access the Order Management constraints window follow these steps:1. Navigate to the Processing Constraints window. N: Setup > Rules > Security > Processing Constraints.

2. In the Application field, query Oracle Order Management.3. In the Entity field, query Order Line.

List of OM Constraints at Pick ConfirmThe Order Management constraints control the following types of Order Line changes once deliveries are ship confirmed:■ Update order line■ Cancel order line■ Delete order line■ Split order lineIn turn, Order Line update is controlled for 22 different shipping attributes as shown in the following table:

Exception MessagesThe following messages have been created to provide feedback to Order Management users when an order line change is rejected.Update Not AllowedMessage: 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 QuantitiesMessage: 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 AllowedMessage: 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 beallowed all delivery lines, related to the source order line, must be eligible for the change.

Invalid Source CodeMessage: 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 isrestricted to 'OE'. Other products cannot request Shipping changes.

Invalid Packing Condition Caused by Shipment Attribute ChangeMessage: 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. The message provides the delivery line detail and the LPN ID to manually unassign the delivery line from it.