EDI Invoice Inbound 810
Release 10.7 and 11.0
Qin Wu
Cheryl Ludwig
Oracle Support
Abstract
This paper provides an overview of the
steps to setup and use Oracle EDI
Invoice Inbound.
Scope
I. Overview of Oracle EDI Gateway
II. How to Setup and Use EDI Invoice
Inbound
III. Troubleshooting
I. Overview of Oracle EDI
Gateway
Oracle Applications provides users with
the ability to conduct business
electronically between trading partners
based on the Electronic Commerce
standards and methodology. One form of
Electronic Commerce is Electronic Data
Interchange (EDI).
EDI is an electronic exchange of
information between trading partners.
Data files are exchanged in a standard
format to minimize manual effort, speed
data processing, and ensure accuracy.
The EDI Gateway performs the
following functions:
• Define trading partner groups and
trading partner locations
• Enable transactions for trading
partners
• Provide location code conversion
between trading partner location
codes and codes used in Oracle
Applications
• Provide general code conversion
between trading partner codes or
standard codes
• Define interface data files so that
application data can interface with
EDI translators
• Extract application data, format, and
write to data files (outbound
transactions)
• Import data or converted codes into
application open interface tables so
that application program interfaces
(API) can validate and update Oracle
application tables (inbound
transactions).
A common EDI implementation is via
ASCII data files in a batch environment.
Data from the sending application is
extracted into an application data file.
The application data file is received by
the translation software which translates
it into the EDI standard both trading
partners agree upon. Then the EDI data
file is placed on a network for
transmission to the receiving application.
The receiving application's EDI
translator receives the EDI data file from
the network and begins the file
processing in reverse sequence. The
translator translates the EDI data file and
creates an application data file
meaningful to the receiving application.
The receiving application receives the
application data file for processing and
imports the data into the application.
Oracle EDI Gateway Product
Architecture
With an open architecture, Oracle
Applications allows you to choose the
best translation and electronic
transmission service for your business
requirements. You can use a
commercially available EDI translator
and transmission provider or use a
proprietary solution. The Oracle
Applications and the Oracle EDI
Gateway places no restriction on your
choices.
Oracle EDI Gateway is used for both
inbound and outbound transactions to
define trading partner locations within a
trading partner group. By defining a
trading partner, you do the following:
• Enable EDI translations
• Establish a link to the location or
business entity defined in the
Oracle Applications
• Establish a link to the trading partner
definition in the EDI translator.
II. How To Setup and Use
Oracle EDI Invoice Inbound
To use the Oracle EDI Payment
Inbound, perform the following tasks:
Step 1. Define Data File Directories
To use EDI Gateway, you must first
create directories where data files,
for both inbound and outbound
transactions, are stored. You must then
specify these in the INIT.ORA file and
in the EDI Gateway profile
options.
Prerequisite: You have to be on Rel
10.7.0.16.1G and 7.3.3.5 or Rel 11.
Apply:
• Latest EDI patchset
• Latest AP patchset
• Latest PO Patchset (If PO is
installed)
• Latest version of ECEPYO.sql
• Latest version of ecepyo.odf
1. init.ora Setup
============================
Add an environment variable
"utl_file_dir" in
$ORACLE_HOME/dbs/init.ora
For Example, you are using directory
"/sqlcom/inbound" as your EDI inbound
directory, you will need to set
utl_file_dir = /sqlcom/inbound in init.ora
for your database.
cd $ORACLE_HOME/dbs/
vi init.ora
add or set: utl_file_dir =
/sqlcom/inbound
2. Setup "ECE:Inbound Directory" in
Profile Options
=============================
In System Administrator Responsibility,
Navigate to Profile -> System -> Set:
Site = Yes,
Profile Option "ECE:Inbound Directory"
= /sqlcom/inbound
Save it.
Note: Setup step 1 and step 2 have to be
set to the same directory.
** Make sure that everyone has read,
write, and execute privilege on the
directory /sqlcom/inbound. This path
needs to be exactly the same as the path
you have defined in Profile Option.
3. View your flat file (ECEINI.dat) in WordPad or Notepad.
The following is an example of one invoice:
The first line is called Control record,
which contains:
Type of EDI Transaction Code,
Translator Code, EDI Location Code.
The second line is for Invoice Header,
which contains:
Invoice Type, Invoice Number, Invoice
Date, Invoice Amount.
The Third line is for Invoice
Distribution, which contains:
Line Type, Line Number, Amount, and
Expense CCID.
4. Copy the Flatfile
================
For Example: Flatfile Name =
ECEINI.dat
ftp ECEINI.dat from your PC into your
EDI Inbound Directory in UNIX:
ftp ECEINI.dat /sqlcom/inbound
5. Verify the Flatfile:
======================
For Example: Your Flatfile =
ECEINI.dat
It should return: PL/SQL procedure
successfully completed.
sqlplus apps/password
ECE_UTILITIES.verify_flatfile(810,'IN
I','/sqlcom/inbound','ECEINI.dat');
If it runs successfully, it means that so
far your setup is correct. If not, please go
through the above setup again.
6. Define Trading Partners:
===========================
In EDI Manager Responsibility,
Navigate to: Trading Partners -> Set:
For Example: Supplier = GE_Capital
Group = EDI Invoice Inbound Group,
Partner = GE_Capital
Document = Invoice Inbound,
Document Type = Standard Invoice,
Translator Code = TR_CODE
7. In AP Manager Responsibility, Navigate to:
Suppliers -> Entry
=================================
Query on Supplier = GE Capital, go to Site

a. Click on alternate region: Electronic Data Interchange,

Set: EDI Location = DANBURY

b. Click on alternate region: Site Uses and Telephone,

Set: Pay Site = Yes

At this point, you have set:

TRANSLATOR CODE = TR_CODE

EDI LOCATION CODE = DANBURY
8. Verify the control line in the flatfile:
===========================

select text from ECE_OUTPUT where text like '%0010%' order by text;

For Example:

Rec: 0010 Pos: 10 Width: 2 Col: COMMUNICATION_METHOD Val= ED

Rec: 0010 Pos: 20 Width: 1 Col: TP_TEST_FLAG Val= P
Rec: 0010 Pos: 30 Width: 6 Col: TP_DOCUMENT_ID Val= INI
Rec: 0010 Pos: 40 Width: 5 Col: DOCUMENT_TYPE Val= INVOI
Rec: 0010 Pos: 50 Width: 2 Col: TP_PURPOSE_CODE Val=
Rec: 0010 Pos: 60 Width: 35 Col: TP_DOCUMENT_CODE Val= EDI_INV01
Rec: 0010 Pos: 70 Width: 30 Col: TRANSLATOR_CODE Val= TR_CODE
Rec: 0010 Pos: 80 Width: 35 Col: TP_LOCATION_CODE_EXT Val= DANBURY
Rec: 0010 Pos: 90 Width: 74 Col: TP_DESCRIPTION Val=
Rec: 0010 Pos: 100 Width: 80 Col: TP_REFERENCE_EXT1 Val=
Rec: 0010 Pos: 110 Width: 80 Col: TP_REFERENCE_EXT2 Val=
Rec: 0010 Pos: 120 Width: 15 Col: TRANSACTION_DATE Val=
Rec: 0010 Pos: 130 Width: 15 Col: RUN_ID Val=
Rec: 0010 Pos: 140 Width: 10 Col: TRANSACTION_CONTROL1 Val=
Rec: 0010 Pos: 150 Width: 10 Col: TRANSACTION_CONTROL2 Val=
Rec: 0010 Pos: 160 Width: 10 Col: TRANSACTION_CONTROL3 Val=

Please make sure:

• All the records are left adjusted.

• The value of TRANSLATOR_CODE = TR_CODE
• The value of TP_LOCATION_CODE_TEXT = DANBURY

9. Verify the invoice header in the flatfile:

==============================

a) Edit ECEINI.dat in WordPad or NotePad.

b) EDI Manager Responsibility, Output Definition,

find Transaction = INI, Level = Invoice Header,

c) select text from ECE_OUTPUT where text like '%1000%' order by text;

Rec: 1000 Pos: 10 Width: 10 Col: INVOICE_TYPE_LOOKUP_CODE val=

STANDARD
Rec: 1000 Pos: 20 Width: 10 Col: INVOICE_NUM Val= EDI_INVO1
Rec: 1000 Pos: 30 Width: 20 Col: INVOICE_DATE Val= 20000815
Rec: 1000 Pos: 40 Width: 20 Col: INVOICE_AMOUNT Val= 123.45
Compare (a),(b),(c), make sure that positions are defined correctly.

10. Verify the invoice distribution in the flatfile:

==================================

a) Edit ECEINI.dat in WordPad or NotePad.

b) EDI Manager Responsibility, Output Definition,

find Transaction = INI, Level = Invoice Line,

c) select text from ECT_OUTPUT where text like '%3000%' order by text;

For Example:

Rec: 3000 Pos: 10 Width: 25 Col: ITEM_LINE_TYPE_CODE+L270 Val=ITEM

Rec: 3000 Pos: 20 Width: 15 Col: INVOICE_LINE_NUMBER_EXT Val=1
Rec: 3000 Pos: 30 Width: 20 Col: AMOUNT Val=123.45
Rec: 3000 Pos: 40 Width: 15 Col: DIST_CODE_COMBINATION_ID Val= 1032775

Compare (a),(b),(c), make sure that positions are defined correctly.

11. Run ECEINI EDI Invoice Inbound
===========================

In EDI Manager Responsibility, Navigate to: Import Programs.

Set Name = EDI Invoice Inbound, Submit the request.

III. Troubleshooting

entity defined in Oracle Applications

1. Note: 2081701.6 (TP Assignment Region).

Problem: INBOUND FLAT FILE NOT
IMPORTED INTO INTERFACE
TABLES
Solution: Check the following:
1. Make sure the utl_file_dir for
inbound file directory is defined in the
INIT.ORA file.
2. Make sure a Trading Partner is
defined and associated to an address
810, 832, 843, 856, 857 TP
associated to Supplier and Supplier Site
850 TP associated to Customer
and Customer Site
3. Make sure the Trading Partner is
enabled for the inbound EDI Document
(TP Details Region). Document Type
does not apply to inbound transactions as
the assumption is that EDI Gateway will
import the entire file.
4. Make sure the EDI Gateway program
parameter for file name contains the
correct file name. EDI Gateway will
provide a default file name. Do not
include the directory path as part of the
file name.
5. Make sure the Translator Code field
contains a valid value defined for the
Trading Partner (TP Details Region =
Record 10, Element 70 in the flat file).
6. Make sure the Location Code field
contains a valid value defined for the
Trading Partner (TP Header Region =
Record 10, Element 80 in the flat file).
2. Note: 120365.1
ECEINI Doesn't Copy INVOICE_NUM,
INVOICE_DATE From Flatfile
Problem: You are using Release
10.7.0.16.1. You have EDI Patchset
(898125, 898134) and
EDI Control Production Patch (898127)
applied. You log into your EDI
Responsibility, and run EDI Invoice
Inbound program 810 (ECEINI).
INVOICE_NUM,
INVOICE_AMOUNT,
INVOICE_DATE, and some other
columns are not populated in the table
ap_invoices_interface from the flatfile.
Solution: This is bug 1381826.
Please go to Metalink to get patch
1381826 applied to have the fix.
Prerequisite patches are: 898125,
898134, 898127.
3. Note: 106429.1
EDI Invoice Inbound Gets Exception
"No Supplier Found"
Problem: You are running EDI Invoice
Inbound (ECEINI 810), and are getting
the exception No Supplier Found.
The supplier and the site exists in the
tables po_vendors and
po_vendor_sites_all.
Solution: This can be a setup issue.
Please look into the following:
1) Using the EDI Manager
Responsibility, navigate to Trading
Partners.
Make sure the following has been set for
the supplier:
Group = <your group>
Partner = <your partner>
Document = Invoice Inbound
Document Type = Standard Invoice
Translator Code = <your translator
code>
2) Using the Payables Manager
Responsibility, navigate to Suppliers ->
Entry.
Query on Supplier, go to Site, then the
Electronic Data Interchange region.
Make sure the following has been set
for the supplier site:
Pay Site = Yes,
EDI Location = <your EDI location>*
*The value of EDI Location needs to
be exactly the same as
the value of
TP_LOCATION_CODE_EXT you have
put in the flat file.
4. Note: 1049417.6
How to Record Tax and Freight in the
EDI Open Interface Import Process
Problem: When importing Inbound 810
Invoices through the EDI Gateway, how
do you specify tax and freight? You
have reviewed the
AP_INVOICE_LINES_INTERFACE
table and the
AP_INVOICES_INTERFACE table and
you do not see a column containing
freight or tax.
Solution: There is a column in
AP_INOICE_LINES_INTERFACE
called LINE_TYPE_LOOKUP_CODE.
The four valid values for this column
are: ITEM, TAX, MISCELLANEOUS,
or FREIGHT.
If you want to record tax or freight, use a
LINE_TYPE_LOOKUP_CODE of TAX
or FREIGHT and then record the amount
of the tax or freight in the AMOUNT
column.
If you would like to specify a certain
type of tax, you may use the
TAX_CODE column.
5. Note: 1075470.6
MISSING ORG_ID IN PAYABLES
OPEN INTERFACE TABLES
Problem: You are trying to import
invoices using the Payables Open
Interface Import.
The field org_id does not exist in the
tables ap_invoices_interface and
ap_invoice_lines_interface. It is not
consistent with ap_invoices_all and
ap_invoice_distributions_all.
Solution: This feature was not available
at the base version of Payables on Rel
10.7 and Rel 11.
Please apply the latest AP patchset
for Rel 10.7 or Mini-Pack for Rel 11.
The org_id will then be available.
6. Where do I find out what the latest
patches are for EDI Gateway?
Log on to Metalink.
1. Navigate to Patches -> Patch
Download.
2. Click on ==> NEW! Click here for
ALL Applications Product Patches.
3. Choose your release version: 11 or
10.7
4. Choose your product: E-Commerce
Gateway
5. Choose your platform
6. Choose limit search to: Latest
Product Minipaks
7. Click on Submit.
About the Authors
Qin Wu is a Technical Specialist with
the Oracle Financials team. Qin has over
4 years of Oracle Payables experience.
Cheryl Ludwig is an Technical Analyst
with the Oracle Financials team. She has
been with Oracle Payables for 2 years.