Session ID:

Simplifying EDI for E- 10091

Business Suite
Prepared by:
Vic Roselli
Novara Solutions
How to simplify your EDI
configuration for optimum adoption
of EDI processes and services April 23, 2018

Remember to complete your evaluation for this session within the app!
Background

• Company wanted to implement EDI on existing EBS system in 8 weeks for new
division receiving and sending EDI transactions.

• No translator / transformer available

• No internal knowledge on EDI processes

• Basic functions expected but requirements grew over time

• Extended project to accommodate changing requirements

• New technology required more testing than expected

Team

• 1 – Part time client functional

• 1 – External EDI expert functional

• 1 – External EDI technical expert

• 1 – Affiliated company EDI expert

Novara Solutions, Inc

• EBS Implementations and Upgrades

• EBS Cloud Services and Interfaces
• EBS Support
• EBS Extensions
• EBS Integration of Native and Added SOX Controls
• EBS Training and Process Improvement
• 15+ years EBS implementation and support experience
• Vic Roselli, Functional / Accounting on EBS implementations
• Debbie Ciskie, Functional / Accounting on EBS implementations
Resources

• TEST and DEV reserved through go live

• Oracle Support

• EDI implementation guide

• EDI user guide

Time Line

Setups
Testing
Go Live
EBS EDI Options

• e-Commerce Gateway

• XML Gateway

• EDI as a service

• Oracle B2B

• Custom Development
File Types
ASC X12 XML

Flat File (native to EBS)

Opportunity

• Speed up Sale Order processing

• Greatly reduce manual order entry

• Leverage customer order processes

• Expedite ASNs, invoices and acknowledgments directly to customer systems

• Shorten the B to B order/fulfillment cycle with standard ERP delivered functions

EDI inbound /
outbound selection
and purpose
Phase 1 (DSNO)

• ASNs AKA DSNO & AKA Shipping Manifest

• Designed test transactions
• Transmitted
• Confirmed basic function
• Expanded to add DFF to expand delivered values
Phase 2 (POI)

• Inbound 850 POI Sales Orders

• Provided guidance on record layout

• Meet minimum requirements to pass “Stage”

• Meet minimum requirements to pass “Correction”

Sales Orders
Phase 3 (POAO)

• Outbound acknowledgments

• Accept delivered values

• Action - Book sales order

Phase 4 (INO)

• Outbound AR invoices

• Delivered has lots of detail

• Watch out for “upstream” dependencies

Invoice E-Commerce Gateway

Phase 5 (POO)

• Outbound purchase orders

• Watch that precision

• Sent on approval so do not approve until complete

• Watch those drop ship orders for address changes

• Purchasing forms do not = EDI POO

PO Approved E-Commerce Processing Purchase Order

Sources

Direct EDI
Customers Orders

Translator / Transformer
DSNO – ASNs

POI - SFTP POAO – PO Ack

E-Commerce
Gateway
INO – Invoices
B to B
Web Site
Customer Orders
POO - POs
Out of the Box Approach

• Used delivered EDI file layout

• Can be modified but risk later patching would cause additional maintenance so
you lose that “set it and forget it”

Just labels
Configuration
Expansion Options
• Used
– DFF
– EXT1 ---- EXT5
– Code Conversion
– Added needed values

• Not Used
– Outbound attachments
Code Conversions

• Limited to delivered columns / code

• Layers
• Simple means reliable
• Add new values or convert?
• EXT values
• Categories
• Assignments
• Values
• What is all that clutter
Trading Partner

• Just a related record, one to one, to control EDI types available for customer
accounts - POI – POAO- DSNO - INO
• Can be qualified by translator value
• Labels are labels
• Mapped to customer sites
Trading Partner EDI Setups

Just labels

Just labels
EDI Location Codes

• Purpose – Map external Bill to / Ship to valid Oracle AR accounts

• Best Practice
• Missed Opportunity
• Source values that can be used
• Cryptic values you may be required to use
• Control your source or you will have many to many setups for single customer
– Duplicate addresses
– Redundant EDI Location Codes
• Not needed if you allow “create customer” option in Order Management
Order Types

• Consider EDI specific order types

• Easier analysis
• Simpler data query
• Finer control on critical delivered defaults
Order Management Defaults

• Can simplify source values by setting defaults

• Lower overhead on your sources / translator

Going Live
Available Tools

• Interface File report

• Trading Partner Report

• Missing Tools
– EDI Location Code Report

• Staged Form

• Correction Form
Now for Some Maintenance

• Move the site move the EDI Location Code

• Typical failure mode for EDI Location Codes
• How many cooks in that kitchen
Staged

• Why staged
• How to train for staged
• How to avoid staged
• Where is the reporting ?
 Corrections
• Typical correction errors
– Terms
– UOM
– Addresses (lions and tigers and
bears,,,, oh my)
– Items
• How to avoid corrections
• Fix your sources
• Negotiate with your sources
• Best practice
• Best training
• Control it / maintain it
Concurrent Confusion
• Lots of inbound / outbound programs with unusual names

• User access to delivered processes not a good idea

• Lock it down with a menu mapped to control user

Scheduling (keep it simple)

• Inbounds every 24 hours

• Outbounds every 24 hours

• Respond to failed processes early

• You can run some processes again

Generating failed EDI transactions

• DSNO - Concurrent program if you know the trip

• POI - Run again and again

• POAO - Get out your keyboard

• INO - A support provided SQL script will reset as needed by invoice ID

• POO - A support provided SQL script will reset as needed by PO

Lessons Learned

• Plan your EDI location codes

• Control your sources or….. They will control you
• Use standard functions – Simplify
• Just say no ---- to special added functions
• Just say no to customization
• Cycle test (confirm) after go live before scheduling processes
• Do not automate broken processes
• Basic EBS processes need to be working well to take advantage of EDI
• Start with simple inbound, not outbound
• Do not give up, resist manual rework by fixing the root causes
• Start simple and keep it simple to improve reliability
 vroselli@novarasolutions.com
dciskie@novarasolutions.com
Session ID:
10091

Remember to complete your evaluation for this session within the app!