E-Commerce: Application
Integration with Oracle
Applications
Presented By:
Anne Blanchard
Director of Product Management SPS Commerce, Inc.
Application Integration with Oracle Applications
• Benefits of EDI and Integration • Integration Options
– Oracle’s EDI Gateway – Custom Coding
– Integration Engine
• What is required for each type of integration
– Customer requirements – Vendor requirements
• Customer case studies • Integration challenges
Why choose EDI???
Why integrate it with your
Oracle Apps?
– Increase communication time of key information with your trading
partners
– Reduction of business cycles – Increase accuracy of data
Integration Options: Oracle’s EDI Gateway
Supported Transactions for
Oracle 10.7
• 810 (invoice) outbound
• 850 (purchase order) inbound • 850 (purchase order) outbound
850 (purchase order) in 850 (purchase order) out
856 (advanced ship notice) out 856 (advanced ship notice) in 857 (shipment and billing
notice) in
860 (P.O. change request) out 862 (shipping schedule) out 810 (invoice) in
810 (invoice) out
820 (remittance advice) out 824 (application advice) out 830 (planning schedule with
release capability) out 832 (price/sales catalog) in 843 (response to request for
quotation) in
Integration Options: Oracle’s EDI Gateway
Supported Transactions for
Oracle 11.0
Supported Transactions for
Oracle 11i
Oracle 11i will support the traditional EDI Gateway and a new E-Commerce
Gateway. The E-Commerce gateway will output an XML file instead of a flat file.
Oracle 11i will support the same
transactions as 11.0.
Integration Options: Oracle’s EDI Gateway
• Vendor requirements
– The EDI vendor should provide tested map templates for each transaction
– Full featured translator
– Skilled consultants that can assist with the customization of the different map templates
Integration Options: Oracle’s EDI Gateway
Integration Options: Oracle’s EDI Gateway
• Customer requirements
– The customer is expected to provide a configured EDI gateway
– Knowledgeable resources
• Internal business processes
• Oracle configuration - most sites make changes to Oracle Apps!
• Customer Case Study
– Mid-market manufacturer of trucking equipment
• Oracle Apps 10.7 installed on Windows NT platform
• EDI translator installed on Windows NT server
• Using Oracle’s EDI Gateway
• Integrated 3 transactions for 5 trading partners - 810out, 850in, 856out
• 3 days of services per transaction
Integration Options: Oracle’s EDI Gateway
• Option for customers needing
transaction not supported by the
EDI Gateway
• Custom program written that will
either post or extract data from
the Oracle tables
• Vendor requirements
– The EDI vendor should offer a
flexible, easy-to-use mapping tool, that allows for the creation of
custom maps
– Full-featured translator
– Skilled consultants that can assist with the creation of custom maps
• Customer Requirements
– Custom interface to Oracle Apps
• Data validation
• Application of business rules
– Custom mapping information
• Flat file layout
• Trading partner specifications • Mapping matrix
• Customer Case Study
– Large manufacturer of computer supplies and accessories
• Oracle Apps 10.7 installed on an HP Unix system
• EDI translator installed on HP Unix system • Used the EDI Gateway for integrating
purchase orders, invoices, etc.
• Custom interfaces for 940out (warehouse
shipping order) and 945in (warehouse shipping advice)
• 3 weeks for custom interface to Oracle Apps • 2 days for first map for each transaction (940
and 945)
• Software package that supports
the integration of EDI
transactions to and from Oracle’s
Open Interface Tables
– Eliminate the need for custom coding
– Ideal for customers that require integration for transactions not supported by the EDI Gateway
• Vendor requirements
– Software package that sits between the EDI translator and Oracle Apps
• Provides cross reference capabilities • Application of business rules
• Data validation before posting or extracting data
– Same integration engine used for different transactions
• Customer requirements
– Knowledgeable resources
• Internal business processes • Trading partner requirements • Oracle configuration
• Customer Case Study
– Large manufacturer of print devices and print supplies for assembly lines
• Customers include US Postal Service, Phillip Morris, 3M, and GM
• Came from a “rip and read” EDI solution - they wanted to improve service to their larger
customers and reduce their operating costs • Did not want to support both the EDI Gateway
and an integration engine so they chose the integration engine because it supported more transactions
• Customer Case Study
• Oracle Apps 10.7 installed on DEC Alpha Unix system
• EDI translator and Integration Engine installed on Windows NT server
• Integrated purchase orders, invoices, etc. for 24 trading partners
• Approximately 3 days of gap analysis prior to implementation for each
transaction type
• 3 to 6 weeks implementation for each transaction type
Integration Options: Integration Engine
• Customer Case Study
• Final results
– Improved customer service
» 97% for invoicing within service standards
» 95% for shipping within service standards
» 0.85% error rate
– Significant decrease in order processing time
– Invoices sent when an order is closed out - no more delay!
Things to think about…
– Clear definition of project requirements - make sure
everyone is on board before
starting the project
– Cost and benefit analysis prior to selecting a solution
– What expertise is required?
• Oracle Applications
• Internal business processes • EDI requirements
Thank You!
Anne Blanchard