Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

eCommerce Gateway

Posted on September 21st, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

There are are the two out-of-box integration capabilities for E2E available in Oracle Applications:

  • Oracle E-Commerce Gateway (formerly EDI Gateway)
  • Oracle XML Gateway

if you are new about EDI , refer to this post

dgreybarrow Oracle E-Commerce Gateway

eCommerce Gateway enables to expose internal business objects in a standardized format thus the trading partners integrate with the external business objects to send/receive information to/from Oracle E-Business Suite”

  • Support EDI Transactions
  • Executes Batch Processing
  • ASCII file format
  • Interface Files are EDI Standards Independent
  • EDI Translator is required
  • eCommerce Gateway interface is a Concurrent Program Packaged ‘Out of the Box’ key business transactions

A typical Transactional Flow can be best understood as in context of Ecommerce Gateway is as below:

ecoomernce

 

Oracle e-Business Suite in conjunction with Oracle e-Commerce Gateway supports 23 EDI transactions. Oracle e-Business Suite generates and consumes ASCII flat files.

The ASCII flat files are sent to/received from a third party EDI translator who transforms the flat file content into the ASC X12 or EDIFACT equivalent. ASC X12 is the EDI standard for North America and Canada. EDIFACT is the EDI standard for Europe and Asia.

  • 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)

Next we will have a look on XML gateway.

Posted in EDI, Integration | No Comments »

Oracle Apps and ASN

Posted on April 14th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

The ASN aka Advanced Shipment Notice is a document that is sent to a buyer in advance of the buyer receiving the product. It is typically used within the context of an EDI environment. It can be used to list the contents of an expected shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking carrier information, and configuration of goods within the transportation equipment. In the implementation of the transaction the latest the ship notice may be sent is the time of shipment. In practice the ship notices just arrive before the shipment.

dgreybarrow Basic Business Needs

  • To receive a Shipping notice in Advance:
  • Provide user the ability to electronically receive supplier ship notice into Purchasing by loading an ASN electronically into Oracle Apps using the Receiving Open Interface.

dgreybarrow Business Flow

Typical Process with company using Oracle EBS would be similar to this:

  1. Supplier sends ASN.
  2. EDI validates the data for EDI standards and inserts data into Receiving Interface tables.
  3. Receiving Open Interface validates ASN data. If accepted shipment lines are populated.
  4. Supply details are maintained.
  5. Application Advice is generated. The supplier can check if there is a rejection of ASN through the advice.

dgreybarrowInbound Shipment Notice Transaction (856)

If you are using EDI Gateway , make sure you have done setup for Trading partner correctly. These are relevant Oracle Purchasing Profiles and Set-ups

The following is a list of the Purchasing set-ups related to the Receiving Open Interface.

  1. RCV: Fail All ASN Lines if One Line Fails:
    If the profile option is set to 'Yes' and any line failed validation, no further validation is performed for the ship notice.
    If the profile option is set to 'No' and any line failed validation, the process continues with the next line.
  2. ASN Control:
    In the Receiving Options window in Purchasing, select Warning, Reject, or
    None in the ASN Control field to determine how Purchasing handles the receipt against a purchase order shipment for which a ship notice exists.
  3. PO: Enable SQL Trace for Receiving Processor :
    If the profile option is set to 'Yes', more detailed error data is provided in the View Log screen of the Submit Request window when you run the Receiving Transaction Processor.

dgreybarrow Data Flow Diagram

Here is data flow looks typically when you are using with EDI gateway.


ASN DATAfLOW

Receiving Open Interface tables which got involved in this is:
RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE

You can use Import Programs to submit ECEASNI.sql (856) to the Concurrent Manager to populate the Receiving Open Interface tables with data from the inbound interface file.This is applicable if you are using EDI Gateway , else you can directly use Receiving Open Interface (RCVTP) program.

Use Import Programs to submit the Receiving Open Interface (RCVTP) program to the Concurrent Manager to validate the data in the Receiving Open Interface tables.

Hope with this, you can easily implement ASN in EBS. Question, comments are most welcome.

Posted in EDI, Oracle Purchasing | No Comments »

ASN – An Inside View

Posted on April 12th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

dgreybarrow What exactly is an ASN and its types

ASN stands for “Advanced Shipment Notice”.

  • An ASN is a document used to transmit critical shipping information to the receiver.
  • It contains information on the carrier, the items and quantities shipped by Order, packaging information, and (potentially) labeling data from the item, package .
  • An ASN is composed of TWO parts:
    • Serial Shipping Container Code (SSCC) barcode labels on the shipping containers
    • An “856” Electronic Data Interchange (EDI) document
  • There are two types of ASNs:
    • Standard Pack ASNs
    • Pick & Pack ASNs.
  • A Standard Pack ASN is used when the same item is packaged together in one container.
  • A Pick & Pack ASN allows for different items within the same package.

dgreybarrow Levels of ASN

  • ASN can contain many levels of information.
  • These levels, sometimes referred to as hierarchical levels, or simply "HLs" define the different levels of detail within the ASN. These levels are different from different Trading Partner.
    • Shipment Level: This is the most broad level of detail. There is one Shipment HL allowed in an ASN. It contains data such as the Pro Number, the Bill of Lading Number, etc.
    • Order Level: There may be one or more orders per ASN. Information necessary to reconcile the shipment with the customer's orders is placed here.
    • Tare Level: This HL represents a unique pallet identification. This level is used in some, but not all ASNs, depending on your Trading Partner and the manner in which you ship your goods. It normally contains a number corresponding to a bar-coded label as well as some physical characteristics of the pallet, such as weight and size.
    • Pack Level: This level identifies each carton in the shipment (or on the pallet, if the Tare Level is used). The Pack Level HL also contains a number corresponding to a bar-coded label. Usually, but not always, the pack level is used on an ASN.
    • Item Level: The item level represents an item that is shipped. Quantity and item identification data is stored at this level

dgreybarrowA typical Business senario for Inbound ASN

  1. ABC sends a Purchase Order to the Supplier A.
  2. The supplier picks the order. As the order is picked, the supplier’s warehousing/distribution system (aka “supplier’s system”) keeps track of what items are being picked into particular shipping cartons .
  3. When the carton is closed, the supplier’s system assigns an SSCC to that carton/pallet. Instead of when the carton is closed, this is sometimes done by the supplier’s system during the allocation/cubing process.
  4. The SSCC is encoded into a barcode on a shipping label and placed on the carton/pallet.
  5. Upon shipping the shipment of cartons/pallet to ABC, the supplier’s system generates the 856 EDI and transmits it to ABC so that ABC receives the EDI prior to the shipment arriving. The 856 EDI hierarchy must match the physical shipment (carton SSCC, carton detail, pallet, PO# information, etc.).
  6. ABC receives and processes the 856 EDI and stores it in their system. ABC acts on the ASN by scheduling the receipt, scheduling labor, doing prep work, etc.
  7. The shipment arrives at ABC. The ABC receiver scans the SSCC barcode and the ABC distribution system knows what is in that carton because of the 856 EDI. The distribution software system “guides” the receiver through what is supposed to be received since it knows everything about that carton because of the SSCC and 856 EDI, including what PO it is on, what items and quantities are in it, the lots and expiration dates, pedigree information, etc.

In case if you any more scenario do share .:)

Posted in EDI | No Comments »

EDI and there prevalent EDI standards

Posted on March 11th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Electronic Data Interchange (EDI) is the electronic exchange of routine business transactions. These transactions include documents such as purchase orders, invoices, inquiries, payments acknowledgements etc.

EDI is the cross-industry electronic business interchange standard that enables individuals, companies and organizations to participate in global e-commerce.

EDI enables a commonly understood and standardized format of the relevant data to be transmitted from one computer system to another with minimal human intervention.

edi

EDI extracts information from a business process (e.g. purchase order, invoice etc). The data is usually transmitted over a Value Added Network (VAN – which acts as a electronic post offices) and delivered to a trading partner. Once the trading partner receives the information, the EDI systems will automatically translate the standardized EDI data into application data and moved to the appropriate business application.

dgreybarrow EDI Standards

  • United States
    • X12
    • EDIFACT (Multi- Industry)
  • UK
    • TRADACOMS (Retail)
    • ODETTE (Automotive)
    • EDIFACT (Multi- Industry)
  • Germany
    • VDA (Automotive)
    • ODETTE (Automotive)
    • EDIFACT (Multi-industry)
  • France
    • ODETTE (Automotive)
    • GENCODE (Retail)
    • EDIFACT (Multi- Industry)
  • Brazil
    • RND (Automotive)
    • NTC (Transportation)
    • CNAB (Banking)
    • X12 (Multi-industry)
    • EDIFACT (Multi- Industry)
  • Mexico
    • X12
    • EDIFACT (Multi- Industry)
  • Japan
    • CII (Multi-industry)
    • EDIFACT (Multi- Industry)
  • Australia
    • X12 (Multi-industry)
    • EDIFACT (Multi- Industry)

Posted in EDI | No Comments »

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 | 2 Comments »

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 | 11 Comments »

Page 1 of 11