Shipping Execution

Oracle
Shipping
Execution
Release:11i10
Oracle India Development Centre

- Venkat Sathiyamoorthi
- Nagraj Krishnamurty
- Abhijit Raut
New and Changed Features for

Shipping Execution
Delivery / Trip Consolidation

Master Bill of Lading Enhancements
Exception Enhancements
Pick Release Enhancements
Weight and Volume Enhancements
(continued . . . )
1-2
This presentation is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into
any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making a purchasing decision.
New and Changed Features for

Shipping Execution
Quick Ship User Interface

Shipping Transaction Form UI
Enhancements
Shipping Parameter Enhancements

Consolidate at Backorder
ITM Enhancements
1-3
Oracle Order Management Suite

Oracle Shipping
Prior to Release 11i10, pick releasing with Auto

Create Deliveries created new deliveries
New
functionality assigns lines to existing

deliveries before it auto creates new deliveries
Backordered delivery lines and new delivery
lines can be automatically assigned to existing

deliveries
Trip Consolidation systematically groups

deliveries into trips
1-5
Delivery Consolidation Flow

Pick release process
Auto Create
Appending
Delivery
Pick Release
Pick
Review exceptions:
Ship Confirm
1-6
Stage

Description
Process Deliveries SRS:
1-7
New concurrent program

Process unassigned delivery lines to deliveries:
Auto Create Deliveries
Append Deliveries
Process unassigned deliveries to trips:
Auto Create Trips
Consolidate deliveries into newly created trips

Benefits
1-8
Leverage opportunities of shipping/carrier

economies of scale
Fewer deliveries and trips in the system, less
shipment fragmentation
Consequently: A more simple transportation
organization
Improves application system performance
Improves warehouse efficiency
Delivery Consolidation
Shipping Parameter: Appending Limit Options
Do Not Append
- Delivery consolidation will not occur in that Org.
Start of Staging
- Delivery reaches consolidation limit when first delivery line
1-9
is Staged.
End of Staging
- Delivery reaches consolidation limit when last line in
delivery is Staged.
Start of Packing (WMS)
- Delivery will reach consolidation limit when packing
process begins.
Start of Shipping (WMS)
- Delivery reaches consolidation at start of Easy Ship, LPN
Ship, Direct Ship, or Dock Door Ship.
Business Need for Append Deliveries
Lower number of deliveries leads to

fewer transactions
less resource consumption
better performance
1-10
Larger deliveries may save shipping cost
Appending Limit Parameter:
1-11
Selecting Append Deliveries yes/no flag in the

Release Rules form or Release Sales Orders form:
1-12
Determines if consolidation will occur during pick

release. List of values includes:
Yes
No
Null
Selecting the Append Deliveries flag:
1-13
Criteria used to add lines to existing deliveries:
1-14
Status of the delivery must be Open

Delivery Firm Status must be Not Firm
Delivery appending limit other than Do Not Append
Appending only applies to outbound Deliveries
Delivery Line source, Order Management only
Deliveries that match the delivery grouping criteria
Verification of compatibility constraints
Delivery Firm Status:
1-15
Principles of the appending limit:
1-16
Delivery Firm Status is automatically set to Contents

Firm when appending limit is reached
Firmed deliveries are not eligible for consolidation
Exception logged for successful consolidation:
1-17
Code: WSH_DELIVERY_APPENDED
Type: Delivery exception
Message text: Delivery detail XXXX has been
automatically assigned to delivery YYYYY by
Append Deliveries function
Exception Behavior: Warning
Status: Open
Batch will
process
unassigned
deliveries lines
Only selection
criteria
applicable to
delivery lines is
available
Action
Parameters
1-18
Trip Consolidation
Batch will process
unassigned
deliveries to trips
Only selection
criteria
applicable to
delivery is
available
Grouping
parameters
1-19
Trip Consolidation
Process Deliveries SRS trip grouping criteria:
Organization Type (derived)
Delivery Status (derived)
Ship Method (optional)
Ship From (optional)
Maximum number of deliveries per trip
(mandatory)
1-20
Trip Consolidation
Trip Consolidation is invoked via Process Deliveries SRS
concurrent program. Entity = Deliveries Only.
Selection criteria applicable to Trip Consolidation
1-21
Delivery Status
Pickup & Drop off Dates on Delivery
Ship From Organization
Customer
Ship To Location
Ship Method
Group Deliveries By Ship Method
Group Deliveries By Ship From Organization
Maximum number of deliveries per trip (default = 50)
Trip Consolidation
Initial grouping criteria is
Organization Type (implicit)

Delivery Status (implicit)
Ship-From (User-controlled)
Ship Method (User-controlled)
After the initial grouping, the constraints API is used to

evaluate whether each set of deliveries can be assigned to a
single trip.
Within each constraint evaluated group, a set of deliveries
(controlled by Maximum number of deliveries per trip
parameter) is grouped into a single trip.
This program will only create new trips. Existing trips are
not used.
1-22
Trip Consolidation
If customer / ship-method will be used as parameters to the
Process Deliveries SRS, please make sure that when deliveries
are created, these two parameters are turned on as delivery
grouping attributes.
Deliveries from TPW and CMS organizations are not eligible for
trip consolidation.Only open and confirmed deliveries are eligible
for this process.
The concurrent program generates an output file providing a
summary of how many deliveries were selected vs. how many
trips were created.
1-23

Oracle Shipping
MBOL Enhancements
Master BOL report reformatted

Allows sequential numbering of Master BOL
Capability to include Master BOL in document set
New action Print Master BOL at the trip level
New enable check box Create Master Bill of Lading
at Trip Confirm
1-25
Master Bill of Lading
Master BOL provides a means of merging, onto a

single document, multiple deliveries
Master BOL is given to the transport carrier as a

summary of the various deliveries onboard
1-26

New Format
Attributes added
1-27

Master BOL Report Reformatted
HEADER: Trip Summary

BODY: Stop Details
Stop Sequence #1
Deliveries picked up
Delivery A
Delivery B
Delivery C
Deliveries dropped off
Stop Sequence #2
Deliveries picked up
Deliveries dropped off
Delivery A
1-28

Sequential Numbering of Master BOL
You can now have the

system sequentially
number the MBOL.
1-29

Master BOL in Document Set
You can now include the

MBOL in a document set.
1-30

Print Master BOL Action
At the trip level, a new action

has been added that enables
you to generate and print the
MBOL.
1-31

Create Master Bill of Lading Option
Within the Confirm Trip

window, a new option, Create
Master Bill of Lading, has
been added.
1-32

New attribute: Master Bill of Lading Number
The Master BOL

Number is a new
attribute displayed in
the Trip Details window.
1-33

New Parameter in MBOL Report
1-34

Oracle Shipping
1-36
Allows enabling or disabling of seeded exceptions
Changed status of exceptions to: Open, Closed, No

Action Required
Provides capability to automatically close

exceptions with warning
Enables user to raise a Business Event for an

exception
Enables user-defined exceptions
Replaces Severity with user-friendly Exception

Behavior
Benefits
Greater user control over seeded exceptions

Better definition of exceptions
Improved logging
Facilitates easier resolution
1-37
New checkbox enables

you to quickly enable or
disable exceptions.
1-38
Exception Behavior
replaces Default
Severity.
1-39
Workflow for Exceptions:
New check box to Raise Business Event for a

named exception.
Send notification to user requesting appropriate

action.
Resolution of the exception and processing of the
related Business Event are independent activities.
1-40
Creating user defined exceptions:
1-41
Enables you to define/create an exception

Manually applied in Shipping Transactions form (STF)
Tool to temporarily prevent ship confirm
Method of posting outstanding issues for an order
Applying user-defined exceptions:
In the STF, invoke the
new action Log
Exception.
This action is available
at all entity levels:
lines/LPN, delivery,
stop, and trip.
1-42
Manually Logged exception flag:
This view is as it appears if you

select the user-defined exception
within the Exception Name field.
1-43
Upgrade Consideration -- Mapping of Exception Status:
Mapping of status between
releases occurs as shown
in the table
Public APIs can no longer
specify the Status while
logging an exception
Status in PreRelease
11i10
Maps to Status
in Release
11i10
Closed
Closed
Error
Open
In Process
Open
Logged
Open
Manual
Open
No Action
Required
No Action
Required
No Action
Required
Not Handled
Open
1-44
Open
Warning:
Exception flag is yellow.

The exception will generate a
warning message at ship confirm and
allow ship confirm if user selects OK.
Error:
Exception flag is red. The

exception will generate an error
message at ship confirm and prevent
ship confirmation until resolved.
Information Only:
Exception flag
has a standard check mark with no
color. The exception will display in
the Exception Report but no action is
required prior to ship confirmation.
1-45

Oracle Shipping
Warning message in the release sales order form if

certain parameters are not entered.
Express Release Windows in number days plus or

minus instead of date range.
Picking criteria expanded in the Release Sales
1-47
Orders form and the Release Rules form

Enables you to define a rolling pick release
window in the Release Rules form
Release Sales Orders and

Release Rules Enhancements
Description
Pick release by Region and Zone

Ability to pick release by Item Category
Pick release using a designated subinventory
Parameter to autocreate delivery within an order or
across orders at request level
Consolidate deliveries using append deliveries

Ability to set up rolling release windows in Release
Rules form
New warning message in the release sales order

form if certain parameters are not entered
1-48

New pick release criteria
1-49
Region or Zone
Release all
qualified delivery
lines destined for
the area
Item Category
Release all
qualified delivery
lines that include
an item in the
selected item
category

New pick release criteria
1-50
Subinventory You can select a specific subinventory as a

criterion to pick release lines
Comparison of Criteria
Subinventory vs. Pick From Subinventory
1. Subinventory:
Determines which
lines are considered
for picking based
on the subinventory
name assigned to
the sales order line
2. Pick From
Subinventory:
Determines where
the line items are
picked/allocated
from
1-51
Release Rules Enhancement

How to Set Up these Features
Example: Release window based on Schedule Date
In this example, all orders with a

Scheduled Ship Date of the sysdate,
or within 3days of the sysdate will
be selected for pick release.
The time selected for start =
00:00:01 hours so that all 24 hours
of the Scheduled Date are included.
1-52
Release Rules Enhancement

How to Set Up these Features
Example: Pick release using static dates
Alternatively, you can create a

pick release rule using static
dates.
1-53
Release Sales Orders Enhancement

New warning message at Release Sales Orders form
A new warning message occurs to prevent

unintended release of an unusually large
number of delivery details
WARNING: The absence of more detailed criteria
defined for this Pick Release Batch could result in a
large number of lines being Pick Released. Do you
wish to continue?
1-54

Warning Message for Concurrent:
1-55

Message for Execute Now
1-56

Oracle Shipping
Automatically displays values at every entity level.

Re-calculates and displays values during change
management events.
Allows manual entry of values.

Automatically aggregates values at higher entity
level.
New action to reset Weight/Volume.
1-58
Weight & Volume Enhancements
System now assumes automatic calculation;
1-59
Calculate Weight/Volume parameter has been

removed
Automatically displays values at every entity
level

How to Use this Feature
Delivery Line
W/V values are automatically

displayed for all entities. No
need to invoke action. Also,
values are re-calculated and
displayed as change
management events occur.
LPN
Delivery
1-60
Adjusts values after change management
1-61
events
Aggregates values at higher entity level
Allows manual entry of values
Refreshes original values using the new action

Reset Weight/Volume
Added new field to the LPN window called Filled

Volume
1-62

Oracle Shipping
Entirely new UI for Quick Ship confirmation

Highly configurable UI
Target Customer: High shipping volume and noncomplex shipping process.
1-64

Goals of the new interface:
1-65
Minimize number of:

- Clicks
- Tabs
- Windows
Displays only required fields and entities
Targeted for simple Ship Confirm
Enter inventory controls and print documents

Major features:
Single window for Lines, Deliveries and Trips
1-66
User Configurability:
One click ship confirmation
Easily navigate to Shipping Transactions form
- Trip Confirm or Delivery Confirm view

- Hide Trip region
- Hide/show fields and additional tabs
- Includes printing shipping docs
- Entering inventory controls

User level Profile Option controls the type of Quick Ship UI View
Delivery or Trip View
User can also switch between views by navigating to

Tools-> Change View
1-67

Delivery Confirm View
1-68

Trip Confirm View
1-69

Delivery Only View
1-70

Save Folder
1-71

Oracle Shipping
Shipping Transaction Form UI Enhancements
Shipping Transactions Form UI

Enhancements
Before
Multi tab
Data entry required for processing was located on

different tabs resulting in excess navigation.
Only one look and feel was provided for all business
types and industries.
1-73
Shipping Transactions Form UI Before 11i10
1-74

Enhancements
After
User configurable
Larger canvas size with fewer tabs.

Ability to hide/unhide tabs.
Ability to determine what fields are shown in UI.
Ability to create buttons for common actions.
1-75
Shipping Transactions Form UI Enhancements

Right Click Actions & Buttons
1-76
Shipping Transactions Form UI Enhancements

Save Folder
11i10
1-77
11i9

Enhancements Ship Confirm Form
1-78

Enhancements Serial Entry
1-79

Enhancements
A New Field Next Step in STF
1-80
Line Status
Next Shipping Step
Not Applicable
Ship Confirm
Cancelled
Not Applicable
Not Ready for Release
Progress Order to Awaiting Shipping
Ready to Release
Back Ordered
Released to Warehouse
Staged/Pick Confirmed
Shipped
Interfaced
Run Pick Release

Run Pick Release
Transact Move Order
Ship Confirm
Run Interface Trip Stop
Not Applicable
Comments
Non-Transactable Item

Oracle Shipping
Re-organized to support new parameters in 11i10.

One tab for all delivery creation attributes.
Global Shipping Parameters form added.
1-82
11i10
11i9
1-83
11i10
11i9
1-84
11i10
11i10
Moved to Global
Shipping parameter
form.
1-85
11i9
11i10
11i9
1-86
1-87
Global Shipping Parameters
1-88

Oracle Shipping
Consolidates delivery lines initially from same sales

order line.
Occurs for lines backordered at :

- Pick Release
- Cycle Count
- Ship Confirm
Excludes backordered lines that remain packed.
1-90
Global Parameter
New Global Shipping
parameter enables
you to consolidate
backordered lines.
1-91
Example:
1.1 Delivery
detail line with
requested
quantity of 10
Split into 5
lines with Qty
2 each
If lines are
backordered
during pick
release, cycle
counting, or ship
confirm they will
be consolidated
Line is split
during
processing
1.1 DD = qty 2
1.1 DD = qty 2
1.1 DD = qty 2
1.1 DD = qty 2
1.1 DD = qty 2
Back
Ordered
1.1 Delivery
detail line with
qty of 10 *
* Lines that remain packed will NOT be consolidated

1-92

Oracle Shipping
ITM Enhancements
International Trade Management

Partner Integration: Enhancements
Supports asynchronous XML messaging by using
Oracle ITM Adapter and Oracle XML Gateway.
Option to provide synchronous acknowledgement.

Enhancements include:
-
Export compliance screening for sales orders.

Export compliance screening for deliveries.
Item and party synchronization with partner
application.
Parameter based flexible integration approach

including support for custom filtering criterion.
1-94

Integration Architecture
INTERNET / LAN / WAN
Export Screening
Oracle Shipping
Execution
Oracle Order
Management
Other Oracle
Applications
1-95
Export
Screening
Oracle ITM
Adapter /
Oracle
XML Gateway
Partner
ITM
Application
Export Screening

ITM Partner Form
1-96

Item Synchronization
Sends the item information to the vendor.
The Item information are picked up from Oracle

Bills of Materials by the ITM Adapter.
The item information is sent in XML format using a

Concurrent Program Item Synchronization in
ITM Adapter.
The Item Information like Long & Short
Description, Item ID, Hazard Class are sent to the

vendor.
1-97

Item Synchronization
1-98

Party Synchronization
Sends the party information both customer &
carrier to the vendor.
The party information is picked up from Oracle

Receivables by the ITM Adapter.
The party information is sent in XML format using

a Concurrent Program Party Synchronization in
ITM Adapter.
The Party Information like Name, ID, Site No,

Address etc are sent to the vendor.
1-99

Party Synchronization
1-100

Order Export Screening
Sends the order information for screening.
Assign the Workflow with screening activity to a

transaction type.
While screening, the order line status will be

Awaiting Export Screening.
Screening Pass, Line status will become Awaiting

Shipping
Screening Fail, Line status will become Awaiting

Shipping with Hold Applied.
1-101

1-102

Line Status- Screening Pass
1-103

Line Status-Screening Fail
1-104

Export Screening Workbench Find Screen
1-105

Export Screening Workbench
1-106

Export Screening Workbench
1-107

Delivery Export Screening
Delivery Screening can be done at 3 places
Pick Release
Ship Confirm
Pick Release & Ship Confirm
When delivery is sent for screening an exception
is logged against the delivery.
The delivery is sent for screening using a
concurrent program-Submit Deliveries for
Screening in ITM Adapter.
1-108

Following are the 5 exceptions available for Delivery

Export Screening
For Pick Release
WSH_PR_REQ_EXPORT_COMPL
WSH_PR_SUB_EXPORT_COMPL
For Ship Confirm
WSH_SC_REQ_EXPORT_COMPL
WSH_SC_SUB_EXPORT_COMPL
For Failed Screening
WSH_EXPORT_COMPL_FAILED
1-109

1-110

Delivery Export Screening Submit
Deliveries for Screening
1-111
Q&A
1-112

Shipping Execution

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Shipping Execution

Uploaded by

Copyright:

Available Formats

Oracle

Oracle India Development Centre

New and Changed Features for

Delivery / Trip Consolidation

New and Changed Features for

Quick Ship User Interface

Shipping Parameter Enhancements

Oracle Order Management Suite

Delivery / Trip Consolidation

Prior to Release 11i10, pick releasing with Auto

functionality assigns lines to existing

Backordered delivery lines and new delivery

lines can be automatically assigned to existing

Trip Consolidation systematically groups

Delivery Consolidation Flow

Delivery / Trip Consolidation

New concurrent program

Delivery / Trip Consolidation

Leverage opportunities of shipping/carrier

Business Need for Append Deliveries

Lower number of deliveries leads to

Larger deliveries may save shipping cost

Selecting Append Deliveries yes/no flag in the

Determines if consolidation will occur during pick

Status of the delivery must be Open

Principles of the appending limit:

Delivery Firm Status is automatically set to Contents

Organization Type (implicit)

After the initial grouping, the constraints API is used to

Oracle Order Management Suite

Master BOL report reformatted

Master Bill of Lading

Master BOL provides a means of merging, onto a

Master BOL is given to the transport carrier as a

Master Bill of Lading

Master Bill of Lading

HEADER: Trip Summary

Master Bill of Lading

You can now have the

Master Bill of Lading

You can now include the

Master Bill of Lading

At the trip level, a new action

Master Bill of Lading

Within the Confirm Trip

Master Bill of Lading

The Master BOL

Master Bill of Lading Enhancements

Oracle Order Management Suite

Allows enabling or disabling of seeded exceptions

Changed status of exceptions to: Open, Closed, No

Provides capability to automatically close

Enables user to raise a Business Event for an

Enables user-defined exceptions

Replaces Severity with user-friendly Exception

Greater user control over seeded exceptions

New checkbox enables

New check box to Raise Business Event for a

Send notification to user requesting appropriate

Resolution of the exception and processing of the

related Business Event are independent activities.

Enables you to define/create an exception

This view is as it appears if you

Exception flag is yellow.