Free Oracle Magazine Profit:The Executive's Guide to Oracle Applications

Enter your e-mail address to receive notifications when there are new posts

Profit Magazine: The Executive's Guide to Oracle Applications

EDI & E-Business Suite - Part II

Posted on February 15th, 2007 by anand |Print This Post Print This Post |Email This Post Email This Post

This is a continuation of last article for EDI, here are the add-on details for most of the EDI been offered within E-Business suite. More importantly, the two different widely acceptable standards are mostly used in different continent. For example the in North America and Canada ASC X12 is widely accepted across industry where as well as Europe and Asia has EDIFACT as preferred standards.

Now, here is the extensive list of EDI with categorization with E business suite module wise.

Oracle Purchasing

  • Outbound 850/ORDERS
  • Outbound 860/ORDCHG
  • Inbound 832/PRICAT
  • Inbound 843/QUOTES
  • Inbound 856/857/DESADV
  • Outbound 824/APERAK

Order Management

  • Inbound 850/ORDERS
  • Inbound 875/ORDERS
  • Outbound 855/ORDRSP
  • Inbound 860/ORDCHG
  • Outbound 865/ORDRSP

Shipping

  • Outbound 856/DESADV

Inventory

  • CUSDEC (No ASCX12 equivalent)

Payables

  • Inbound 810/INVOIC
  • Outbound 820/PAYORD-REMADV
  • Outbound 824/APERAK

Receivables

  • Outbound 810/INVOIC
  • Outbound 812/DEBADV-CREADV

Supplier Scheduling

  • Outbound 830/DELFOR
  • Outbound 862/DELJIT

Release Management

  • Inbound 830/DELFOR
  • Inbound 862/DELJIT
  • Inbound 866 (No EDIFACT equivalent)

Hope this helps a fair idea about the EDI messaging usage in EBS suite. Will write couple of more article under this head for setting up EDI message in EBS Suite with one business case.

Posted in 11i, EBS Suite, EDI | 1 Comment »

EDI & E-Business Suite

Posted on February 9th, 2007 by anand |Print This Post Print This Post |Email This Post Email This Post

This is an article is all about EDI, deal mostly with basics and some information with underline Oracle E business Product within the suite. This article start with a typical business case and describe how this is evolves and how important is in ERP, the article helps you understand the high-level overview of the EDI process.

Why EDI Evolved?

Let us consider a simple business scenario. A Customer from PO department who wants to purchase an item creates a purchase order and then faxes it to the suppliers. At the moment vendor receives the purchase order and manually keys in a sales order. The vendor's system generates a confirmation date that is sent back to the customer via fax or mail. The vendor then ships the goods via a carrier. The carrier delivers the products to the customer. When the goods are shipped, the vendor invoices the customer. The customer makes the payment by check, and the vendor deposits the check in the bank. Finally, funds are transferred from the customer's account to the vendor's account.

Drawing12

 

Figure: Typical business documents exchanged by business partners

Now It clears how much of information needs to be transferred and tracked to run the business, which in reality it is called trading partner. This simple scenario requires the exchange of various documents between several business partners at different times.

All this electronic data was exchanged using floppy disks and other secondary devices. So, ANSI committee was formed to define the standards. Hence the electronic exchange of business documents in a standard format gave birth to what is known as EDI, today the business world had accepted as one of most important entity.

What is EDI?

EDI (Electronic Data Interchange) is the electronic exchange of business documents between the computer systems of business partners, with a standard format over a communication network. It can also be called as paperless exchange.

EDI, electronic funds transfer (EFT), electronic mail and fax are increasingly being used to schedule operations, streamline order fulfilment, and optimise cash flow.

edi11

Standard Formats
The business documents that are been exchanged between business partners need to be in a standard format. ANSI X12 (American National Standards Institute) or EDIFACT (Electronic Data Interchange For administration, Commerce, and Transport) are two standards, which supply a common language for formatting the information content that is been exchanged.

Components
There are five major Components in the EDI Process:

o Sender
o Receiver
o Language
o Content
o Medium

In EDI, the senders and receiver are called trading partners (Customers and Vendors) and the ANSI X12 or EDIFACT standards supply a common language for formatting the information content of common messages.

Oracle's e-Commerce Gateway (EDI Gateway):

A standards-based integration product for Oracle Applications, which allows for companies to integrate Oracle Applications with applications residing inside or outside of the enterprise; communicating via Intranet, Extranet, or Internet.

Oracle's e-Commerce Gateway is independent of all EDI standards and can be integrated with any upstream or downstream process via an ASCII file. Thus, any EDI translator or third party application, that best suits a company's business requirements, can be selected.

Advantage

The major advantage of using Oracle e-Commerce Gateway are listed below:

1. Reduction in labor hours dedicated to data entry
2. Increased data accuracy
3. Quicker communication of key information to and from customers/suppliers resulting in reduced business cycle times and more efficient planning
4. Promotes commonality of business documents and processes

Know the Terminology used in EDI

  • Transaction Set - Business document transmitted between companies (e.g. Purchase Order).
  • Data Segment - Units of data used to communicate specific information within a message (e.g. the header).
  • Data Element - Specific unit of data within a data segment.
  • Trading Partner - Entity such as a customer, supplier, or sister organization with whom electronic commerce is executed.
  • EDI Standards - Agreed to formats for exchanging electronic data (typically developed by representatives of industry verticals).
  • Translator - Software application that translates data into or out of a specific format or standard for processing by an ERP system.

Oracle EDI Gateway - functionality

  • Define Trading Partner Relationships
  • Define Code Conversions
  • Customize Flat File Formats
  • Use Standard Report Submission
    • Initiate Extract Process
    • Initiate Import Process
    • View Extract/Import Process Status

A typical flow can be understood as:

edi

A note on File

  • ASC X12 is the EDI standard for North America and Canada.
  • EDIFACT is the EDI standard for Europe and Asia.

Transaction Supported in Oracle Apps

  • v10.6 - supports 4 transactions
  • v10.7 - supports 4 transactions
  • v11.0 - supports 14 transactions
  • v11i - supports 18 transactions
  • v11i10.2 - supports 23 transactions
  • R12 - data not available

Some Important EDI's Details with Orcle E business suite Modules

Some Important EDI's Details with Orcle E business suite Modules

EDI12

Posted in 11i, EBS Suite, EDI | 10 Comments »

Page 1 of 11