10/4/2017
i wish i knew this earlier
chunks of tech discoveries
Tag Archives: EBS R12
Importing Invoices into
OraclePayables
February 26, 2009 3:34 pm
Posted in Application
Tagged EBS R12, Oracle, Oracle Payables
Leave a Comment
https://iwikte.wordpress.com/tag/ebs-r12/
EBS R12 | i wish i knew this earlier...
About
If you are creating Purchase Orders outside of EBS, then you might need to import
Payables invoices into Oracle. The invoice data goes into two Open Interface tables,
namely: AP_INVOICES_INTERFACE and AP_INVOICE_LINES_ INTERFACE. Heres a
sample import run to demonstrate this facility.
Firstly, lets get a unique number to be used as INVOICE_ID to the invoice to be
imported. This method ensures that each invoice has a unique INVOICE_ID
assignment.
SQL> select ap_invoices_interface_s.nextval from dual;
NEXTVAL
----------
221389
Then, lets proceed to create records in the Invoice Open Interface tables via SQL.
insert into AP_INVOICES_INTERFACE (
invoice_id, invoice_num, vendor_id, vendor_site_code,
invoice_amount, invoice_date, terms_name, source,
org_id, group_id
) values (
221389, 'INV.105', '600', 'CORP HQ', 1200.00,
to_date('01-31-2009','mm-dd-yyyy'),
'COD', 'RETEK', 204, 'GRP.105'
);
insert into AP_INVOICE_LINES_INTERFACE (
invoice_id, line_number, line_type_lookup_code,
amount, dist_code_concatenated
) values (
221389, 1, 'ITEM', 1200.00, '01-110-6100-0000-000'
);
commit;
Then, submit a request for Invoice Import..
Check the output of your request..
Payables Open Interface
Source Name: Retek Matched Invoices
1/9
10/4/2017 EBS R12 | i wish i knew this earlier...

--------- ------------------------- ------------- ---------- ---------

5037 3M Health Care INV.105 31-JAN-09 USD

Total Invoices Imported:

Total Functional Currency Invoice Amount:

The imported invoice becomes available for review in Invoices Workbench..

The import run was performed using Payables responsibility on Release 12.0.6
Vision instance.

Advertisements

https://iwikte.wordpress.com/tag/ebs-r12/ 2/9
10/4/2017 EBS R12 | i wish i knew this earlier...

Journal Import to Journal Import allows you to load journal entries from other applications (payroll,
accounts receivable, etc.) into Oracle GL. Other options would be to create journal
OracleGL entries by hand or use only Oracle applications all throughout. Ill consider journal
upload using the ADI as a manual method still, albeit more convenient.
January 25, 2009 2:13 pm

Posted in Application The journal entries to be imported goes into the GL_INTERFACE table. There are
Tagged EBS R12, Oracle, Oracle GL nine mandatory fields, namely:

Comments (1)
STATUS VARCHAR2 (50)
LEDGER_ID NUMBER (15)
USER_JE_SOURCE_NAME VARCHAR2 (25)
USER_JE_CATEGORY_NAME VARCHAR2 (25)
ACCOUNTING_DATE DATE
CURRENCY_CODE VARCHAR2 (15)
DATE_CREATED DATE
CREATED_BY NUMBER (15)
ACTUAL_FLAG VARCHAR (1)

Lets highlight the important fields

STATUS Use the value NEW to indicate that you are importing new data into
the General Ledger.

LEDGER_ID this is the ID corresponding to your target

Ledger. The GL_LEDGERS table contain all valid values of LEDGER_ID. In the
Vision instance, the Vision Operations Ledger has an ID of 01. This shall be used in
the succeeding sample runs.

USER_JE_SOURCE_NAME should be one of the Journal Sources defined under

Setup : Journal / Sources. There are around 90 pre-defined sources in the Vision
isntance. We will use Payroll in the sample runs.

USER_JE_SOURCE_CATEGORY should be one of the Journal Categories defined

under Setup : Journal / Categories. We will use the Payroll category in the
sample runs.

SEGMENT1 .. SEGMENT5 refers to the five segments (company/department/

account/sub-account/product) of the Operations Accounting Flexfield. For Vison
Operations, account code 5300 and 1110 refer to Salaries and Cash accounts,
respectively.

GROUP_ID this can be used for.. well, grouping journals. During import runs,
you have the option to load journals selectively by GROUP_ID.

Now, were ready to do some actual journal import. Lets start by populating the
GL_INTERFACE table via SQL.

insert into GL_INTERFACE (

STATUS, LEDGER_ID, USER_JE_SOURCE_NAME, USER_JE_CATEGORY_NAME,
ACCOUNTING_DATE, CURRENCY_CODE, DATE_CREATED, CREATED_BY,
SEGMENT1, SEGMENT2, SEGMENT3, SEGMENT4, SEGMENT5,
ACTUAL_FLAG, ENTERED_DR, ENTERED_CR, GROUP_ID
)
values (
'NEW', 1, 'Payroll', 'Payroll',

https://iwikte.wordpress.com/tag/ebs-r12/ 3/9
10/4/2017 EBS R12 | i wish i knew this earlier...

to_date('DEC-22-2008','MON-DD-YYYY'), 'USD',
to_date('DEC-23-2008','MON-DD-YYYY'), 1092,
'01', '830', '5300', '0000', '000',
'A', 1000.00, 0.00, 12345
);
insert into GL_INTERFACE (
STATUS, LEDGER_ID, USER_JE_SOURCE_NAME, USER_JE_CATEGORY_NAME,
ACCOUNTING_DATE, CURRENCY_CODE, DATE_CREATED, CREATED_BY,
SEGMENT1, SEGMENT2, SEGMENT3, SEGMENT4, SEGMENT5,
ACTUAL_FLAG, ENTERED_DR, ENTERED_CR, GROUP_ID
)
values (
'NEW', 1, 'Payroll', 'Payroll',
to_date('DEC-22-2008','MON-DD-YYYY'), 'USD',
to_date('DEC-23-2008','MON-DD-YYYY'), 1092,
'01', '000', '1110', '0000', '000',
'A', 0.00, 1000.00, 12345
);
commit;

Then, submit a request for Journal Import..

Check the output of your request..

Vision Operations (USA) Journal Import Execut

Concurrent Request ID: 4405086

Total Total Tota

Journal Entry Source Name Group Id Status Lines Batches Header
---------------------------- ----------- ------- ------- ------- ------
Payroll 12345 Success 2 1
------- ------- ------
*** TOTALS *** 2 1

https://iwikte.wordpress.com/tag/ebs-r12/ 4/9
10/4/2017 EBS R12 | i wish i knew this earlier...

======================================================= Batches Creat

Warning Batch Name Period

------- -------------------------------------------------------- ------
Payroll A 12345 4405086 Dec-08

Lastly, review the imported Journal Entries..

Creating ELectronic The interrnediate goal would be to create a Payment Process Request Template
specifying the pre-built US Nacha Generic as the Payment Process Profile.
Payment Instruction
Files in Oracle
PayablesR12
January 8, 2009 4:06 pm

Posted in Application

Tagged EBS R12, Oracle, Oracle Payables

Comments (2)

There are a couple of settings to be made prior to this. Lets get on it right away..

Login to the EBS instance and select the Payables-Vision Operations Responsibility.
Select the option Setup : Payment Bank Account from the offered menu so we
can set up BofA-204 as the Disbursing Bank Account.

The US Nacha Generic format has some pre-defined document validations. One
such validation requires that the Bank Branch Number (or Transit Routing Number)
is exactly 9 digits. You may opt to remove the pre-defined validation (US NACHA

https://iwikte.wordpress.com/tag/ebs-r12/ 5/9
10/4/2017 EBS R12 | i wish i knew this earlier...

Internal Bank Validation) from the payment format, or disable this specific
validation, or edit the Bank Branch Number to conform.

Next task is to create an electronic payment document using the US Nacha

Generic Format with a Payment Document Category of EFT PAY.

You may disable sequential document numbering. Otherwise, define a Document

Sequence and assign it to this document category (use System Administrator
responsibility).

Now, we should be able to define a Payment Process Request Template with the
following parameters:

Payment Method Electronic

Disbursement Bank Account BofA-204
Payment Document Bofa204.eft.blank
Payment Process Profile US NACHA Generic
Payment Exchange Rate Type Corporate

Pay an invoice using this Request Template and you should get an electronic file
formatted like this..

101 00000000010000000000901080201A094101
5200VISION OPERATION42593 10SYS12125EFT 09
6227361982731214455555 00000123451529 3M HEALTH CARE
627736198273 0000012345BATCH_NAME 50387 10271-17621
8200000002007361982700000001234500000001234510SYS12125
9000001000001000000020073619827000000012345000000012345
99999999999999999999999999999999999999999999999999999999999999999999999
99999999999999999999999999999999999999999999999999999999999999999999999
99999999999999999999999999999999999999999999999999999999999999999999999
99999999999999999999999999999999999999999999999999999999999999999999999

https://iwikte.wordpress.com/tag/ebs-r12/ 6/9
10/4/2017 EBS R12 | i wish i knew this earlier...

Here is the associated Outbound Payment Instruction ..

Oracle EBS R12 First off, some documentation..

VendorImport Oracles E-Business Suite Online Documentation Library Release 12 has three
documents pertaining to Payables, namely:
January 5, 2009 4:34 pm

Posted in Application Oracle Payables Implementation Guide B25453-04

Oracle Payables Reference Guide B25455-04
Tagged EBS R12, Oracle, Oracle Payables
Oracle Payables Users Guide B25454-04
Leave a Comment

Section A of the Reference Guide is dedicated to Payables Interface Tables. Three

such tables are provided to hold vendor data to be imported into EBS. These
tables, with their corresponding import programs, are:

Open Interface Interface Table Import Program

Supplier AP_SUPPLIERS_INT APXSUIMP
Supplier Site AP_SUPPLIER_SITES_INT_ALL APXSSIMP
Supplier Contact AP_SUP_SITE_CONTACT_INT APXSCIMP

For detailed technical info on the interface tables and the import programs, visit the
Oracle Integration Repository and the eTRM websites (account required).

Lets try some hands-on..

Login to the VISION instance using OPERATIONS/WELCOME credentials and select

the Payables-Vision Operations Responsibility. At the bottom of the menu, choose
the Other:Requests/Run option.

https://iwikte.wordpress.com/tag/ebs-r12/ 7/9
10/4/2017 EBS R12 | i wish i knew this earlier...

Select Single-Request and pick Supplier Open Interface Import from the List Of
Values. Accept the default parameters and press the Submit button. Monitor the
progress of your requests and view its output in the Requests window.

Now, lets load some data..

Fire up sqlplus and execute the following sql statement:

insert into AP_SUPPLIERS_INT (VENDOR_INTERFACE_ID, VENDOR_NAME, SEGMENT1,

STATUS) values (10004,'XXX Financials','1092','NEW'); commit;

VENDOR_INTERFACE_ID and VENDOR_NAME are the only two mandatory fields

when importing vendor data. The VENDOR_INTERFACE_ID is the unique identifier
for records in this table and should be derived from the sql statement..

select AP_SUPPLIERS_INT_S.NEXTVAL from DUAL;

The STATUS field value is changed to PROCESSED after successful conversion,

otherwise it contains the value of REJECTED. Check the Request output for the
reason for rejection.

You can use either automatic Supplier Number assignment or include your own
values during import. Use the SEGMENT1 field to contain your desired Supplier
Number and change the Supplier Number Entry option to MANUAL in the Payables
System Setup screen.
https://iwikte.wordpress.com/tag/ebs-r12/ 8/9
10/4/2017 EBS R12 | i wish i knew this earlier...

Dont skip the commit statement. If the record you just added is neither Processed
nor Rejected, it might be because you havent committed your updates.

Submit the Supplier Open Interface Import request. Heres the imported vendor
record as seen in Supplier Entry..

Pages Search
About Find

Categories Blogroll
Categories WordPress.com
Application WordPress.org
Database
RSS Feeds
Uncategorized
All posts
Archives All comments
February 2009
Meta
January 2009
Register
November 2008
Log in
October 2008

Blog at WordPress.com.

https://iwikte.wordpress.com/tag/ebs-r12/ 9/9