Leveraging a Single OTM Instance Across Multiple Source ERP Systems

Leveraging a Single OTMInstance Across MultipleSource ERP SystemsHow to Enable a Transportation Shared Serviceusing OTM

Partnered with

Today’s SpeakersRavi BalakrishnanProject/Implementation ManagerThe Wonderful Company LLC

Chris BlackburnManager – Solution ArchitecturePropero Consulting LLC

Agenda• the Wonderful Company – who we are and

what we do• Transportation and IT Challenges• The Solution – OTM• Lessons Learned and Next Steps• Questions and Answers

4

5

Leveraging OTM Across Multiple ERP Systems

The Wonderful CompanyWho we are and what we do

7

The Wonderful Company• $4 billion privately held company• High quality and healthy brands• Grow, harvest, bottle, package and market a diverse range of healthy products

Applications Landscape

8

9


Transportation and IT Challenges

Pre - OTM• FIJI / POM – Manual transportation planning• Citrus – 3rd party TMS• Manual :

– Consolidation– Invoice creation and freight settlement

• No real time visibility

10

IT Challenges• FTI reports• Pallet count solution• Multiple SOA integration• Rate Loading• EDI

11

12

Leveraging OTM Across Multiple ERP SystemsThe Solution – Oracle Transportation

Management

Modules in Scope

13

TransportationManagement

TransportationOperational Planning

FreightPayment,Billing & Claims

TransportationIntelligence

Timeline

14

Solution Design

15

16

SOA 12cBPEL Domains:1. FIJI Water2. POM Wonderful

EBS INSTANCES1. FIJI Water (12.2.5)2. POM Wonderful (12.2.5)3. Wonderful CITRUS (12.1.3) SOA 11g

BPEL Domain:1. Wonderful CITRUS*Compatible with EBS 12.1.3

SINGLE OTM 6.4.1 INSTANCEPARENT DOMAIN (TWC):• CHILD DOMAIN 1 (TWC/FWC)• CHILD DOMAIN 2 (TWC/POM)• CHILD DOMAIN 3 (TWC/CIT)Domain Table Grants:* Parent has visibility to Child Domains.* Child has visibility to Parent Domain.* Child only has visibility to another Child Domain if granted.* VPD is used to limit visibility to data on tables granted.(i.e. Orders, Shipments, etc)

OTM PARENT DOMAIN (TWC)Shared Configs:• Agents• Saved Queries• Business Monitor• User Roles• Screens & Menus• Modes• Rate Service & Dist• Default Profiles• Other Shared Configs* No Transactional data (i.e. Orders, Rates,Shipments)

17

OTM CHILD DOMAINS1. FIJI Water (TWC/FWC)2. POM Wonderful (TWC/POM)3. Wonderful CITRUS (TWC/CIT)

TWC/FWC INTEGRATION• Carriers (from EBS)

• Locations (from EBS)

• Items (from EBS)

• Deliveries (from EBS)

• Shipments (to EBS)

• Invoices (from Carriers)

• AP Vouchers (to EBS)

TWC/POM INTEGRATION• Carriers (from EBS)







TWC/CIT INTEGRATION• Carriers (from EBS)







TWC/FWC CONFIG• Login Users• Carrier Rates• Bulk Plan Schedule• Other Domain

Specific Configs

TWC/POM CONFIG• Login Users• Carrier Rates• Bulk Plan Schedule• Other Domain

Specific Configs

TWC/CIT CONFIG• Login Users• Carrier Rates• Bulk Plan Schedule• Other Domain

Specific Configs

Two Workflow Types

IndependentIndependent CrossFunctional

CrossFunctional

18

1. Independent Domain Workflow

No Visibility AcrossChild Domains

Business UnitsOperate

Independently

19

20

Independent Domain Workflow

7. Trip is Created8. Pick, Pack & Ship Confirm9. Trans Sent to OTM



10. Actuals are Receivedfrom EBS - Shipment andOrder Rel are updated.



4. Order Rel (Del) is Plannedand Shipment Created

4. Order Rel (Del) is Plannedand Shipment Created

4. Order Rel (Del) is Plannedand Shipment Created5. Shipment is Tendered

6. Trans Sent to EBS5. Shipment is Tendered6. Trans Sent to EBS

5. Shipment is Tendered6. Trans Sent to EBS

1. Order is Booked2. Delivery Created:

5559943. Trans Sent to OTM





2. Cross Functional DomainWorkflow• The vision is to gradually move towards centralized planning, where an OTM child domain

can plan freight for multiple business units.• Today, some of POM Orders are planned by Citrus. Therefore, only orders flagged to be

planned by Citrus are visible to the Citrus domain (TWC/CIT).• Flagged POM orders are consolidated with Citrus orders for freight optimization.• Citrus Shipments containing POM orders have Trips created in POM EBS where it is

Picked, Packed & Ship Confirmed.• Actuals are sent from POM EBS to Citrus OTM domain (TWC/CIT) for Shipments planned

by Citrus.• POM tracks their orders planned by Citrus via Sell Shipments.• Citrus charges POM for freight management based on allocated costs.

21

22

Cross Functional Domain Workflow

10. Actuals are Receivedfrom EBS- POM Order Rel is updated.- CIT Shipment is Updated

3 OrdersConsolidatedinto a multi-

stop Shipment

Flagged Order Relfrom POM Domain

4. Order Releases are Plannedand Shipment Created


893821, 8954313. Trans Sent to OTM


763297Delivery is Flagged to beplanned by Citrus group3. Trans Sent to OTM

10. Actuals are Receivedfrom EBS- CIT Order Rel are updated.- CIT Shipment is Updated

5. Shipment is Tendered6. Trans Sent to CIT and POMEBS

7. Trip is Created with POMShipment Stops8. Pick, Pack & Ship Confirm9. Trans Sent to OTM:

- Update Release in TWC/POM- Update Shipment in TWC/CIT

7. Trip is Created with CITShipment Stops8. Pick, Pack & Ship Confirm9. Trans Sent to OTM- Update Release in TWC/CIT- Update Shipment in TWC/CIT

Cross Functional DomainKey Solutions1. Planning Domain (Citrus) should not have visibility to all Order Releases fromother domains:

– Domain Grants are used to turn on/off table visibility across child domains– VPD is applied to limit visibility to only ‘flagged’ data.– The ‘Flag’ is a DFF field labeled ‘Plan Domain’– Example of a POM order that is visible to the Citrus domain:

23

Cross Functional DomainKey Solutions2. Carrier ID from Planning domain (Citrus) does not exist in the Client EBSinstance (POM). Therefore, the Shipment transmission from CIT OTM to POM EBSfails the data validation and trip is not created:- A xref table is used to do a Carrier ID substitution when the data passes through

BPEL.- The xref data is stored as SERVPROV REFNUM in OTM:

24

Cross Functional DomainKey Solutions

3. BPEL assumes POM Trips are always planned by OTM POM domain. Therefore,POM Actuals Transmission for Shipments planned by Citrus fails:- BN Rule was defined to append a unique letter to the Shipment ID for each domain:

- BPEL was configured to map the Actuals Transmission data to the appropriatedomain based on the first letter of the Shipment ID.

25

26


Lessons Learned and Next Steps

Lessons Learned• EBS integration• Carrier portal

27

Next Steps• FTI reports• Rate loading• Sourcing

28

29


Questions and Answers

Leveraging a Single OTM Instance Across Multiple Source ERP Systems

Technology

Transcript of Leveraging a Single OTM Instance Across Multiple Source ERP Systems