R12.1R12.1

Oracle Online Training Materials – Usage Agreement

Use of this Site (“Site”) or Materials constitutes agreement with the following terms and conditions:

1. Oracle Corporation (“Oracle”) is pleased to allow its business partner (“Partner”) to download and copy the information, documents, and the online training courses (collectively, “Materials") found on this Site. The use of the Materials is restricted to the non-commercial, internal training of the Partner’s employees only. The Materials may not be used for training, promotion, or sales to customers or other partners or third parties.

2. All the Materials are trademarks of Oracle and are proprietary information of Oracle. Partner or other third party at no time has any right to resell, redistribute or create derivative works from the Materials.

3. Oracle disclaims any warranties or representations as to the accuracy or completeness of any Materials.  Materials are provided "as is" without warranty of any kind, either express or implied, including without limitation warranties of merchantability, fitness for a particular purpose, and non-infringement.

4. Under no circumstances shall Oracle be liable for any loss, damage, liability or expense incurred or suffered which is claimed to have resulted from use of this Site of Materials. As a condition of use of the Materials, Partner agrees to indemnify Oracle from and against any and all actions, claims, losses, damages, liabilities and expenses (including reasonable attorneys' fees) arising out of Partner’s use of the Materials.

R12.1R12.1

Purpose:This document provides an overview of features and enhancements included in Release xx. It is intended solely to help you assess the business benefits of upgrading to Release xx. 

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle. Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code. 

Disclaimer:

Transfer of InformationOracle Logistics

Oracle Transportation Management IntegrationFunctional Overview

Sales Order/Shipping Integration with OTM

R12.1R12.1Sales Order/Shipping Integration with OTMAgenda

Introduction– Description– Release Details– Benefits

Setup Process

– Reference Data Synchronization– Delivery Outbound flow– Planned Shipment Inbound Flow– Actual Shipment Outbound Flow

Dependencies and Interactions

R12.1R12.1

Support same business process flows in Oracle’s 11i.10 TMS solution

Deliver pre-Fusion– E-Business Suite 11i.10– Oracle Transportation Management 5.5

Leverage Oracle Fusion Middleware– BPEL process manager

Sales Order/Shipping Integration with OTM Description

R12.1R12.1

Standardized, Packaged Integrationsvia Web Services Orchestrated by BPEL

BPEL

XML XML

BPEL

WebServices

OrdersShipments

Events

WebServices

InvoicesAllocationsAccruals

*Oracle Transportation Management

OTM*

Leverage Fusion Middleware

EBSOM / WMS /

Inv Mgmt

EBS Purchasing

OracleRetail

OtherERP / SCM

EBS Financials

OtherFinancials

Sales Order/Shipping Integration with OTMDescription

R12.1R12.1 Sales Order/ Shipping FlowDescription

Create Shipments (Deliveries)

CustomerYOU

Plan

Rate

Execute

Route

OTM

EBS

Shipper

Logistics Planner

(1) Create Sales Orders

(7)Ship Notice

(3)Plan, Execute

and Track

(4)Deliveries

(5) Planned

Shipments

(6)Actual

Shipments

(2)Rate inquiry

R12.1R12.1

Sales Orders created in Order Management, Deliveries created in Shipping

Get Ship Method and/or Freight Rate Quotes in Order Management

Deliveries passed from Shipping to OTM for transportation planning & execution

Transportation Planning & Execution– Optimize shipments & select carriers– Carrier tender & booking process

Actual Shipments– Shipping sends OTM the results of the Actual Shipment after Ship Confirm

Sales Order/Shipping Integration Description

R12.1R12.1

Solution Footprint– Oracle EBS 11.5.10 CU2

– Oracle Applications Server with BPEL 10.1.2.0.2

– Oracle Transportation Management 5.5

Delivery Mechanism–The solution will be provided via patch application.

–Configuration options will be outlined as part of the delivery documentation.

– BPEL configuration files, XML translation maps, and readme instructions for all the solution components on Metalink

Sales Order/Shipping Integration Release Details

R12.1R12.1

Equivalent business process solution for existing Oracle Transportation Execution and Transportation Planning users

Centralized transportation management– Manage transportation for orders/shipments outside of EBS or

across multiple EBS instances

Additional TMS functionality including:– Visibility & Exception Management– Additional modes & regions (air, ocean, EMEA, APAC)– Partner Collaboration (suppliers, customers, carriers)– Freight Payment (more modes, auto-pay)

Sales Order/Shipping Integration Benefits

Setup

R12.1R12.1

Global Parameters

Shipping Parameters

Sales Order/Shipping Integration

Profile Options

SETUP

Carriers

All the existing Shipping setup continues to apply

BPEL Setup– Process Manager should be running

on the same server

UOMs5

1

2

3

4

R12.1R12.1 Sales Order/Shipping Integration Setup - Profile Options

OTM: Integration Enabled – Site level, determines enabled components of integration

Profile Value Description

Neither OTM integration disabled

Order Management Only the sales orders outbound flow enabled

Purchasing Only the purchase orders inbound flow enabled

Both Both sales order management and purchase order flows enabled

1

R12.1R12.1 Sales Order/Shipping Integration Setup – Profile Options

OTM: Domain Name– Site Level, Required profile, Uppercase only– Used by Order Management and Purchasing Integration

on the outbound messages– Identifies an instance of e-Business Suite in OTM

1

R12.1R12.1 Sales Order/Shipping Integration Setup – Profile Options

OTM: Domain User – OTM domain user name used by Oracle Shipping and

Oracle Purchasing to integrate with OTM – Site Level, Required profile, Uppercase only– Used by Order Management and Purchasing Integration

OTM: Domain Password– Password for OTM Domain User– Site Level, Required profile, Case sensitive– Used by Order Management and

Purchasing Integration

1

R12.1R12.1 Sales Order/Shipping Integration Setup – Profile Options

OTM: Proxy Server– HTTP proxy server on Oracle e-Business Suite instance

used by Oracle Shipping – Site level, Required profile– Used by Order Management and Purchasing Integration

OTM: Proxy Port– Port number for Proxy Server– Site Level, Required profile– Used by Order Management and

Purchasing Integration

1

R12.1R12.1 Sales Order/Shipping Integration Setup – Profile Options

OTM: Servlet URI– Site level profile provides the OTM Servlet URI for

eBusiness Suite instance to connect to OTM – Used by freight estimation at sales order integration

WSH: BPEL Web Service URI for OTM – Site level profile stores the HTTP location of the BPEL

Process Manager – Used by freight estimation at sales order, outbound orders, and reference data

integration

1

R12.1R12.1 Sales Order/Shipping Integration Setup – Profile Options

WSH: Default Shipping User for OTM– Site level profile provides the application user for inbound

BPEL process– Used by inbound PlannedShipment XML integration

WSH: Default Shipping Responsibility for OTM– Site level profile provides the application responsibility for

inbound BPEL process– Used by inbound PlannedShipment XML integration

1

R12.1R12.1 Sales Order/Shipping Integration Setup – Profile Options

OTM: Corporation Country Code– Used by OTM to identify the country for the customer

account and carriers in EBS – Stored as the ISO code for the country and

communicated on the reference data messages to OTM– Default Value: United States– Site Level, Required profile– Used by Shipping for Reference Data integration only

1

R12.1R12.1 Sales Order/Shipping Integration Setup - Global Parameters

Verify Delivery Date Calculation Method

Set Weight Class and UOM

Transportation Tab disabled

2

Shipping > Setup > Global Parameters

R12.1R12.1 Sales Order/Shipping Integration Setup – Shipping Parameters

Set Weights Limits – Delivery details

maximum net weight– Delivery Maximum

Gross weight – Weight UOM is

defaulted from Global Parameters

Transportation tab disabled

3

Shipping > Setup > Shipping Parameters

R12.1R12.1 Sales Order/Shipping IntegrationSetup - Carrier

Rating, Payment tab – Verify supplier &

default supplier site– All other fields

disabled– Applicable to

Accounts Payable integration

Mode Limits and Vehicle Types tab disabled

4

Shipping > Setup > Freight Carriers, Cost Types > Freight Carriers

R12.1R12.1 Sales Order/Shipping IntegrationSetup - Carrier

Carrier Site Details transportation tab – Verify Supplier &

default Supplier site– All other fields

disabled

4

R12.1R12.1 Sales Order/Shipping IntegrationSetup – Unit of Measure

Required when the UOM code in EBS and OTM are different for the same UOM– OTM can have a 4 letter code for a UOM

Enable the descriptive flexfield on Unit of Measure Setup form– Must use column for Attribute 15

Used for converting to OTM specified UOMs on all outbound transactions – If a value is not found in Attribute 15, the UOM Code

from EBS is sent

5

R12.1R12.1 Sales Order/Shipping IntegrationSetup – Unit of Measure

Enable Descriptive Flexfield – Use Attribute 15 for setting up corresponding OTM UOM

Inventory > Setup > Unit Of Measure > Unit Of Measure

5

This ends Part 1. Please proceed to Part 2.

R12.1R12.1Sales Order/Shipping Integration with OTMAgenda

Introduction– Description– Release Details– Benefits

Setup Process

– Reference Data Synchronization– Delivery Outbound flow– Planned Shipment Inbound Flow– Actual Shipment Outbound Flow

Dependencies and Interactions

R12.1R12.1

Carrier (XML Location)

OTM Shipping

Reference Data SynchronizationDescription

Organization, Customer, Item (XML Release)

TIP Interface (Manual)

R12.1R12.1 TIP (Type In Place) Interface Description

Data maintain by user in both products via the UI (TIP interface)– Enter exactly the same data used in both Oracle

Shipping Execution (WSH) and Oracle Transportation Management (OTM)

– The ID entered in OTM and code entered in Shipping must match

– Manually entered

R12.1R12.1 TIP (Type In Place) Interface Description

Data affected by TIP Interface:– Freight Terms– FOB Codes– UOMs

Weight UOM, Dimensions UOM, Distance UOM, Volume UOM, Quantity UOM

– Currency Codes– Service Levels– Transport Modes– Vehicle Items– LPN Types (example: Box, Pallet)

R12.1R12.1 Carrier InterfaceDescription

Carriers creation and updating:– from Oracle Shipping Execution (WSH) to Oracle

Transportation Management (OTM) via a stand-alone interface.

– Launched on demand and/or Scheduled

WSH OTM Carrier Service Provider

Carrier Site Location

R12.1R12.1 Organization, Customer, Item synchDescription

Organization, Customer, Item creation and updating:– from Oracle Shipping Execution (WSH) to Oracle

Transportation Management (OTM) via Release Transaction.

– Automatically launched through Outbound Interface

WSH OTM Organization Corporation

Location LocationCustomer Corporation

Customer Site LocationItem Item

R12.1R12.1 Reference Data SynchronizationProcess

PROCESS

ORGANIZATION SETUPOracle Shipping Execution Oracle Transportation Management

CarriersCarrier Sites

Service ProvidersLocations

CarrierInterface

Freight Terms, UOMs,Currency Code,

Transport Modes…

Freight Terms, UOMs,Currency Code,

Transport Modes…

TIPInterface

Shipments PlannedDeliveries Created

OrganizationsLocations

CustomersCustomer Sites

Items

CorporationsLocations

CorporationsLocations

Items

XML Release

R12.1R12.1 TIP InterfaceWSH Setup – Navigation

Select Responsibility– Oracle Shipping

Execution– Or Manufacturing and

Distribution Manager Enter navigation path as

– Shipping– Setup– Lookups

R12.1R12.1 TIP InterfaceWSH Setup – Transport Modes

1. Enter all Modes of Transport used (pay attention to Code entered)

2. Click on “Save” icon

R12.1R12.1 TIP InterfaceOTM Setup – Navigation

Enter navigation path as– Transportation

Planning and Execution

– Power Data– General– Transport Modes

R12.1R12.1 TIP InterfaceOTM Setup – Transport Modes

Enter the exact same Modes of Transport used (ID must

match the code entered in Oracle Shipping)

R12.1R12.1 Carrier InterfaceProcess – Navigation

Select Responsibility– Oracle Shipping

Execution– Or Manufacturing and

Distribution Manager Enter navigation path as

– Shipping– Interfaces– Run

R12.1R12.1 Carrier InterfaceProcess – Carrier synch Request

Select “Shipping-Transportation Carriers Synchronization”

concurrent program

R12.1R12.1 Carrier InterfaceProcess – Carrier synch Parameters

1. Enter Parameters selection

2. Click on “Ok” button

R12.1R12.1 Carrier InterfaceProcess – Schedule Carrier synch

1. Click on “Schedule” button2. Select “Periodically” radio

button3. Enter Run Parameters4. Click on “Ok” button5. Click on “Submit” button

R12.1R12.1 Reference Data SynchronizationSummary

Sales Order/Shipping Integration with OTM allows: Ability to synchronize key set up data

– Organizations / Locations– Customers / Customer Sites– Items– Carriers / Carrier Sites

Visibility to consistent reference data

This ends Part 2. Please proceed to Part 3.

R12.1R12.1Sales Order/Shipping Integration with OTMAgenda

Introduction– Description– Release Details– Benefits

Setup Process

– Reference Data Synchronization– Delivery Outbound flow– Planned Shipment Inbound Flow– Actual Shipment Outbound Flow

Dependencies and Interactions

R12.1R12.1 Deliveries Outbound flowAgenda

Overview Source of deliveries Expedite shipments: Setting deliveries and trips as ignore for planning Scheduling the interface concurrent request Delivery actions/updates that trigger the interface Visibility on Interface actions through exceptions Splitting and visibility on splitting through exceptions Interface errors handling Changes to actions on deliveries and delivery details Automated Shipping Scenarios Carrier Manifesting/Third Party Warehousing Warehouse Management System

R12.1R12.1 Delivery Outbound flow Description: flow

Shipment Creation

(1) DeliveriesOrder Entry

Delivery Creation

ACTIVITY OM WSH OTM

Trips Created in

Shipping

(2) Planned Shipments

Ship Confirm Close Stops

Order Entry

Picking

Ready to Ship

TruckDeparture

(3) Actual Shipment

Shipment Updated

Order Release

R12.1R12.1

Delivery Create/update/Delete (XML Release)

Planned Shipments (XML PlannedShipment)

Actual shipment (XML ActualShipment)

OTM Shipping

Delivery Outbound flow Description : messaging

R12.1R12.1 Delivery Outbound flow Process - Delivery sources

– Deliveries sources considered for transportation planning Order Management Project Contracts Shipping Execution (Third party Warehousing, Third

party instance)

R12.1R12.1 Delivery Outbound flow Process – Ignore for planning

– Ignore for planning deliveries and trips are not planned by OTM. This to allow expedite shipments

Whenever a delivery is “ignore for planning” a delete* transaction is sent to OTM removing it from planning (*if the delivery was previously transmitted)

Trips created within shipping execution are set to “ignore for planning” It is possible to freely assign/unassign ignore for planning deliveries

from ignore for planning trip and proceed to ship confirmation – stop close

Actual ship confirmation information is then transmitted to OTM through the actual shipment interface Concurrent Request

Interface action Run every

R12.1R12.1 Delivery Outbound flow Interface Concurrent Request

– Schedule Outbound Interface Request

Interface Action Auto Split Deliveries Restriction

Parameters Batch Size

­ Navigation: Shipping > Interfaces > Run > Shipping-Transportation Outbound Concurrent Request

R12.1R12.1 Delivery Outbound flow How to use - Interface actions

Action Entity Description Create Deliveries Pick all deliveries to be created in OTM*

Update Deliveries Pick all deliveries to be updated in OTM*

Delete Deliveries Pick all deliveries to be deleted in OTM*

Create, Update Deliveries Update, Create combined*

All except Actual Shipment Deliveries Update, Create, Delete combined*

Actual Shipment Trips Pick trips with all pick up stop closed and send actual shipment transactions to OTM*

* Within restriction parameters Interface action Run every

R12.1R12.1 Delivery Outbound flow How to use – Scheduling interface examples

Concurrent Request Interface action Run every Interface Conc. request 1 All Except Actual Shipment 20 min

Interface Conc. request 2 Actual Shipment 60 min

– Example1: Combine interface actions

– Example 2: Single interface action per request

Concurrent Request Interface action Run every Interface Conc. request 1 Actual Shipment 60 minInterface Conc. request 2 Create 60 minInterface Conc. request 3 Update 30 minInterface Conc. request 4 Delete 10 min

R12.1R12.1 Delivery Outbound flow How to use – interface conditions

– Include for planning Deliveries are sent to the interface under the following conditions:Concurrent Request Interface action Run every

Delivery event Interface action Delivery is created or empty delivery is getting item content Creation

Delivery is ignored for planning or all items delivery details unassigned from it Delete

Delivery details assign / unassign Packing/Unpacking (except in WMS orgs)Quantity changes in Order Management Delivery details weight changes

Update

Changes in Delivery attributes: Delivery Name Pick Up / Drop-off locations Earliest/latest Pick Up / Drop-off dates Freight terms and FOB code

Update

R12.1R12.1 Delivery Outbound flow How to use – Interface exceptions

– Visibility on interface process is given by shipping exceptions logged against the deliveries:

­ When the delivery is created, updated or set as “ignore for

planning” a transaction is requested to be processed in OTM

­ When the above transaction has been transmitted to OTM

­ When the delivery has been assigned to a trip through the planned shipment interface

­ Ship confirmation is allowed only if delivery is assigned to an up to date OTM issued trip or deleted in OTM

­ Interface Shipping Exceptions are information only

R12.1R12.1 Delivery Outbound flow How to use –Interface exceptions

Shipping Exception Meaning

WSH_OTM_DEL_TRANS_REQ Delivery Creation , Update or Deletion is required to be passed to OTM Ship confirmation not allowed

WSH_OTM_DEL_AWAIT_TRIP

Above required transaction (Create, Update) has been transmitted to OTM, delivery is now awaiting for a planned shipment from OTM (trip in shipping) Ship confirmation not allowed

WSH_OTM_DEL_DELETED

Above required transaction (Delete) has been transmitted to OTM, delivery is now deleted in OTMShip confirmation allowed

WSH_OTM_SHIPMENT_REC A planned shipment has been received from OTM, delivery is now assigned to a trip Ship confirmation allowed

R12.1R12.1 Delivery Outbound flow How to use – Interface Exception - example

– WSH_OTM_DEL_TRANS_REQ Delivery has been created,

transaction have been required to be passed to OTM

– WSH_OTM_DEL_AWAIT_TRIP Shipment was went back by OTM,

delivery has been successfully assigned to it

– WSH_OTM_SHIPMENT_REC Shipment was went back by OTM,

delivery has been successfully assigned to it

R12.1R12.1 Delivery Outbound flow How to use – Splitting

– Reason & affected processes

­ The delivery weight limits are defined to avoid creation in OTM of multi-equipment and parallel shipments not supported in shipping execution

­ Gross weight limit should correspond to the weight capacity of the biggest equipment used, net weight limit should be gross weight limit minus estimated average tare weight

­ Delivery details exceeding the net weight limit will be split at delivery detail import

­ Deliveries exceeding the Gross weight limit will be split by the Shipping-Transportation outbound interface (interface action creation and update) or will fail the interface

R12.1R12.1 Delivery Outbound flow How to use – Delivery Splitting Rules &

Exceptions

­ Deliveries sent to the interface for creation or update, exceeding the gross weight limit will be automatically split if Auto split parameter is set to yes

­ Auto Split might fail for various reasons (delivery is pick released etc …). In this case the delivery will fail the interface

­ A shipping exception is logged against the split delivery

­ A shipping exception is logged to indicate that a delivery is the result of a split

­ If interface parameter “Auto Split Deliveries” is “No”, oversized deliveries are set in error by the interface, and a shipping exception is logged

R12.1R12.1 Delivery Outbound flow How to use –Splitting exceptions

Shipping Exception Meaning

WSH_OTM_DET_OVERSIZED Delivery import failed to split delivery detail exceeding the net weight limit because of indivisible quantity

WSH_OTM_DEL_SPLIT Interface successfully split delivery exceeding gross weight limit Interface success – if no other errors

WSH_OTM_DEL_SPLIT_CHILD New delivery created by split Interface success – if no other errors

WSH_OTM_DEL_SPLIT_FAIL Interface was unable to split delivery exceeding the gross weight limit Interface failure

WSH_OTM_DEL_OVERSIZED Auto split parameter is set to “No” oversized delivery is rejected by the interface Interface failure

R12.1R12.1 Delivery Outbound flow How to use – Interface errors handling

1. Monitor interface concurrent requests for abnormal termination (error - warning)

2. Output files list deliveries or trips with errors or root cause of failure (missing setup)

3. Log files contain detailed causes of errors for deliveries and trips

4. In case of error the deliveries or trips remain at a “to be processed” status. Whenever the problem is fixed next interface run will pick them up for re-process

5. Only errors due to inability to split deliveries are shown in exceptions

R12.1R12.1 Delivery Outbound flow How to use – Delivery actions

– Allowed actions on deliveries Shipping is the “master application” for Deliveries Therefore, all actions & updates are allowed on deliveries as of

before integration However: Certain actions are not available when OTM is installed (Oracle

Transportation Execution related actions) Some actions have new conditions or effects

R12.1R12.1 Delivery Outbound flow How to use – Delivery

Action Action Assign Freight Costs Un firmClose View message historyFirm content View Shipping StatusGenerate loading sequence Generate BOLLaunch Pick Release Generate Packing SlipResolve / log exceptions Print BOLPrint Document SetPrint Packing slipRe-open

– Allowed actions on Deliveries – no new conditions or effects

R12.1R12.1 Delivery Outbound flow How to use – Delivery

Action Condition / effectAuto Pack /Auto Pack Master

Triggers an update to OTM in non-WMS orgs

Delete Delivery must be ignore for planning first and deleted in OTM

Ignore for planning Enable on unassigned deliveries only Pick and Ship Delivery must be assigned to an up to date OTM trip Reset Weight and volume Triggers an update to OTM

Ship Confirm Delivery must be assignedTo an up to date OTM trip

Unassign from trip Set the delivery as “ignore for planning”

– Allowed actions on include for planning Deliveries – with new conditions or effect

R12.1R12.1 Delivery Outbound flow How to use – Delivery

Action Cancel Ship method Get Freight Costs Select CarrierUPS related actions

– Actions disabled on include for planning deliveries - allowed on ignore for planning

Action Assign to trip Auto Create Trip Pick Pack and ship

– Actions Disabled on Deliveries – removed from role definition

R12.1R12.1 Delivery Outbound flow How to use – Delivery Detail

Action Condition / effectAssign to delivery Unassign from delivery

Triggers an update to OTM for the affected delivery

Auto PackAuto Pack Master Pack / Unpack

Triggers an update to OTM in non-WMS orgs if assigned to a delivery

Cycle count Triggers an update to OTM if assigned to a delivery Reset Weight and volume Triggers an update to OTM if assigned to a delivery

Pick Pack and ShipPick and Ship

Will automatically turn the delivery details to “ignore for planning”

– Allowed actions on include for planning Deliveries Details – with new conditions or effect

R12.1R12.1 Delivery Outbound flow How to use – Delivery Detail

Action UPS related actions

– Actions disabled on include for planning deliveries details allowed on ignore for planning

Action Auto Create Trip

– Actions Disabled on deliveries details – removed from role definition

R12.1R12.1 Delivery Outbound flow How to Use – Automated Shipping

Pick and Ship, Pick pack and Ship fully allowed on ignore for planning deliveries details, delivery

and trips Pick and ship enabled for include for planning deliveries

assigned to an up to date OTM trip

Auto ship confirm SRS Fully allowed on ignore for planning deliveries Allowed to process include for planning deliveries with an up to

date OTM trip – would fail if ship confirm rule enforces a ship method different from the OTM trip

R12.1R12.1 Delivery Outbound flow How to Use – Automated Shipping

Pick release with auto create deliveries and auto ship confirm

All entities are created as ignore for planning

Process delivery SRS When processing deliveries : picks only ignore for planning deliveries

and consolidates them into ignore for planning trips

R12.1R12.1 Delivery Outbound flow How to Use – Carrier Manifesting

– OTM is not installed: Carrier manifesting is now a standard Shipping Execution feature

– OTM is installed: Carrier Manifesting setup is disabled in shipping execution

– Dialog with carrier manifesting system assumed to be handled through OTM

– Ship confirmation to be done in Shipping execution based on the received planned shipment

R12.1R12.1 Delivery Outbound flow How to Use – Third Party Warehousing

– Transportation arrangements assumed to be made by the third party:

Deliveries created on the “supplier instance” are not transmitted to OTM for planning

Delivery transmitted to the third party warehouse (Shipping Execution TPW instance) are transmitted to OTM for planning

They then receive their planned shipment and can ship confirm in this instance

Ship confirmation is transmitted back to the “supplier instance” as usual

R12.1R12.1 Delivery Outbound flow How to Use – Warehouse Management System

– Packing and unpacking operations for an include for planning delivery will not be sent as delivery updates to be re-planned by OTM

– This includes the following transactions: Pick Load and Pick Drop LPN pack/Unpack/Consolidate LPN/Dock ship- Load/Unload Direct ship- Load

R12.1R12.1 Delivery Outbound flow How to Use – Warehouse Management System

– Unloading a part of an already loaded delivery, using Direct ship, requires replanning of the delivery.

– Overpick and underpick in a pick-pack-ship flow will require an updated plan from OTM, before these deliveries can be ship confirmed.

– Overpick and underpick in Direct ship do not require replanning of the delivery and the user is allowed to ship confirm.

R12.1R12.1 Delivery Outbound flow How to use – Warehouse Management System

– Shipping scenarios and mobile inventory using RF devices Quick Ship LPN Ship Dock Door Ship Direct Ship

– If Deliveries and Trips are not pre-existing to theses flows Deliveries and Trips are created as “ignore for planning” to allow the ship confirmation process

– If Deliveries are pre-existing they must be assigned to an up to date OTM trip to allow ship confirmation

R12.1R12.1 Delivery Outbound flow Summary

– Source of deliveries – Expedite shipments: Setting deliveries and trips as ignore for planning – Scheduling the interface concurrent request – Delivery actions/updates that trigger the interface – Visibility on Interface actions through exceptions – Splitting and visibility on splitting through exceptions – Interface errors handling – Changes to actions on deliveries and delivery details – Automated Shipping Scenarios – Carrier Manifesting/ Third Party Warehousing– Warehouse Management System

This ends Part 4. Please proceed to Part 5.

R12.1R12.1Sales Order/Shipping Integration with OTMAgenda

Introduction– Description– Release Details– Benefits

Setup Process

– Reference Data Synchronization– Delivery Outbound flow– Planned Shipment Inbound Flow– Actual Shipment Outbound Flow

Dependencies and Interactions

R12.1R12.1 Planned Shipments Inbound FlowDescription

Standardized packaged integrations using Web Services, orchestrated by BPEL

Ability to process inbound shipment interface automatically

– Does not require any user intervention– Creates Trips, Stops, Delivery Legs, Freight costs in Oracle e-

Business Suite

Planned shipment data validation and error handling

– Correct data validation errors using interface message corrections form

R12.1R12.1

Delivery Create/Update (XML Release)

Planned Shipments (XML PlannedShipment)

Actual shipment(XML ActualShipment)

OTM Shipping

OracleShipping Execution

OracleTransportation Management

Planned Shipments Inbound Flow Description - Messaging

R12.1R12.1 Planned Shipments Inbound Flow Description

Support for change management– Ability to handle changes to deliveries/delivery lines

after receiving planned shipment from OTM– EBS can accept multiple responses for the same

version of the delivery Any updates which increments the version marks the delivery to

be sent again

– If the response from OTM corresponds to a lower version of delivery in EBS, the message is rejected

R12.1R12.1 Planned Shipments Inbound Flow Description

Visibility and interface status tracking via the shipping exceptions

Enhanced UI for supporting the integration– Interface Message corrections form– Shipping Transactions form and Quick Ship UI

Visibility to OTM applied freight costs in Shipping Architected for high volume environments

R12.1R12.1

Planned Shipment XML With Trip Information

Order Release XML With Delivery Information

Planned Shipments Inbound Flow Process - How to Use

ORGANIZATION SETUP

Shipments Planned

Oracle Transportation Management

Deliveries Created/Updated

Oracle Shipping Execution

Data Validation/Correction

Ship Confirm Actual Shipment XML Shipment Update

Trips/Stops/Del Legs/Freight cost

creation

R12.1R12.1 Planned Shipments Inbound Flow Process - How to Use

Planned Shipment XML With Trip Information

Order Release XML With Delivery Information

ORGANIZATION SETUP

Shipments Planned

Oracle Transportation Management

Deliveries Created/Updated

Oracle Shipping Execution

Data Validation/Correction

Ship Confirm Actual Shipment XML Shipment Update

Trips/Stops/Del Legs/Freight cost

creation

Shipments Changed(Trip or Appt.)

Appointment creation

R12.1R12.1 Planned Shipments Inbound Flow Process - How to Use

Planned Shipment XML With Trip Information

Order Release XML With Delivery Information

ORGANIZATION SETUP

Shipments Planned

Oracle Transportation Management

Deliveries Created/Updated

Oracle Shipping Execution

Data Validation/Correction

Trip/AppointmentChanges Change Shipment XML Shipment Planning

Trips/Stops/Del Legs/Freight cost

creation

Shipments Changed(Trip or Appt.)

Trip/AppointmentCreation

Non synchronous process

R12.1R12.1 Planned Shipments Inbound Flow Process - How to Use

Monitor Planned Shipment Interface concurrent requests for termination with error or warning– Log file contains detailed causes of errors for deliveries

and trips In case of error, the deliveries remain at “Awaiting

Response” status – Use Interface Message Correction form to update and

resubmit– Or fix the issue in OTM and next interface run will pick

it up for re-process

R12.1R12.1 Planned Shipments Inbound Flow How to Use – Interface Message Corrections

Use the form to validate and correct the planned shipments from OTM

Shipping > Interfaces > Interface Message Corrections

R12.1R12.1 Planned Shipments Inbound Flow How to Use – Shipping Exceptions

R12.1R12.1 Planned Shipments Inbound Flow How to Use – OTM Applied Freight Costs

R12.1R12.1

Planned Shipments integration with OTM enables to: Integrate OTM shipment planning with EBS shipment

execution and order fulfillment– Create Trips, Stops, Delivery Legs and Freight Costs in

Shipping, allowing ship confirmation

Process inbound shipment interface automatically Enhanced feature rich transportation solution for

existing Oracle Transportation Execution customers Consistent reference data visibility

Planned Shipments Inbound Flow Summary

R12.1R12.1Sales Order/Shipping Integration with OTMAgenda

Introduction– Description– Release Details– Benefits

Setup Process

– Reference Data Synchronization– Delivery Outbound flow– Planned Shipment Inbound Flow– Actual Shipment Outbound Flow

Dependencies and Interactions

R12.1R12.1

Delivery Create/Update (XML Release)

Planned Shipments (XML PlannedShipment)

Actual shipment(XML ActualShipment)

OTM Shipping

OracleShipping Execution

OracleTransportation Management

Actual Shipment Outbound Flow Description - Messaging

R12.1R12.1 Actual Shipment Outbound FlowTransportation Outbound Interface

– Schedule Outbound Interface Request

Interface Action ­ Actual Shipment

Shipping > Interfaces > Run > Shipping-Transportation Outbound Concurrent Request

R12.1R12.1 Actual Shipment Outbound Flow Process – Interface conditions

Trips are sent to OTM via Actual Shipment when last pick up stop is closed

Actions allowed for ignore for planning trips– Disabled for include for planning trips

Action Action Delete UnfirmFirm Routing Ignore for Planning Firm Routing and Content

R12.1R12.1 Actual Shipment Outbound Flow Process – Trip

Attributes Attributes Trip Name Operator Seal Code Vehicle Information Routing Instructions Flexfields

Trip attributes allowed for maintenance

Dependencies and Interactions

R12.1R12.1 Sales Order/Shipping IntegrationDependencies and Interactions

Oracle Transportation Management (OTM) Release 5.5

Oracle Fusion Middleware Oracle Order Management Oracle Project Contracts Oracle Warehouse Management

R12.1R12.1 Sales Order/Shipping Integration Dependencies and Interactions

Oracle Transportation Management (new)– Receive Deliveries though the interface process– Plan shipments and send them back to Shipping Execution– Receive actual ship confirmation from Shipping Execution

Project contract (existing) – Transmits delivery lines to Shipping

Warehouse management System (modified)– Handle Pick, Pack and ship transactions for OTM-planned

deliveries and trips.– Handle Pick, Pack and ship for non-OTM planned deliveries

and trips Order Management (existing) - Source of deliveries

R12.1R12.1 Sales Order/Shipping Integration Dependencies and Interactions

Shipping Execution

Oracle Transportation Management

Project Contracts Order Management

Warehouse Management System

Delivery creation and updates

Deliveries lines import

Planned Shipments

11i10Integration

CARRIERS

Actual Shipments

Actual Shipments

Delivery Delivery

details

R12.1R12.1 Sales Order/Shipping Integration Dependencies and Interactions

Shipping Execution

Oracle Transportation Management

Project Contracts Order Management

Warehouse Management System

Delivery Creation and Updates

Deliveries lines import

Planned Shipments

12.1Integration

CARRIERS

Actual Shipments

Delivery Delivery

details

Update Shipments

Actual Shipments

Additional Resourcesfor Customers and Partners

R12.1R12.1Additional Resources

For Customers and Partners

For More Information about our Products– http://www.oracle.com/products/

For More Information about Education– http://www.oracle/com/education/

For More Information about Support– http://www.oracle.com/support/

For Metalink Information:– http://metalink.oracle.com/

Oracle Product Documentation:– http://www.oracle.com/technology/documentation/applications.html– About Document (provide MetaLink ID)