Overview:

Oracle provides flexible and flexible tools in the form of Interface programs to import
the master and transactional data like Customers, Invoices, and Sales Orders etc from
external systems into Oracle Applications. This article briefs you about some of the
major interface programs.

Conversion/Interface Strategy:

1. Data Mapping

During the data mapping process, list of all the data sets and data elements that will
need to be moved into the Oracle tables as part of conversion are identified. Data
mapping tables are prepared as part of this activity that show what are the data elements
that are needed by the target system to meet the business requirements and from where
they will be extracted in the old system.

2. Download Programs

After the conversion data mapping is complete, download programs are developed that
are used to extract the identified conversion data elements from the current systems in
the form of an ASCII flat file. The structure of the flat file must match the structure of
the Oracle standard interface tables. These flat files generated may be in text form or a
comma or space delimited, variable or fixed format data file.

3. Upload Program

Once the data has been extracted to a flat file, it is then moved to the target file system
and the data from the file is loaded into user defined staging tables in the target
database using SQL Loader or UTL_FILE utilities. Then programs are written and run
which validate the data in the staging tables and insert the same into the Oracle
provided standard Interface tables.
 4. Interface Program

Once the interface tables are populated, the respective interface program (each
data element interface has a specific interface program to run) is submitted. The
interface programs validate the data, derive and assign the default values and ultimately
populate the production base tables.

Interface/Conversion examples with details:

The below list of interfaces/conversions are covered in this section. Details

like pre-requisites required, interface tables, interface program, base tables,

validations that need to be performed after inserting the details into the interface

tables and required columns that need to be populated in the interface table are

discussed for each interface.

• Order Import Interface (Sales Order Conversion)

• Item import (Item conversion)

• Inventory On-hand quantity Interface

• Customer conversion

• Auto Invoice Interface

• AR Receipts

• Lockbox Interface

• AP Invoices

• Vendor

• Purchase Orders
• Requisition

• Receiving

• Journal import

• Budget import

• Daily Conversion Rates

 Order Import Interface (Sales Order Conversion)

Order Import enables you to import Sales Orders into Oracle Applications instead of

manually entering them.

Pre-requisites:

Order Type
Line Type
Items
Customers
Ship Method/ Freight Carrier
Sales Person
Sales Territories
Customer Order Holds
Sub Inventory/ Locations
On hand Quantity

Interface tables:

OE_HEADERS_IFACE_ALL

OE_LINES_IFACE_ALL

OE_ACTIONS_IFACE_ALL
 OE_ORDER_CUST_IFACE_ALL

OE_PRICE_ADJS_IFACE_ALL

OE_PRICE_ATTS_IFACE_ALL

Base tables:

OE_ORDER_HEADERS_ALL

OE_ORDER_LINES_ALL

Pricing tables: QP_PRICING_ATTRIBUTES

Concurrent Program:

Order Import

Validations:

Check for sold_to_org_id. If does not exist, create new customer by

calling create_new_cust_info API.

Check for sales_rep_id. Should exist for a booked order.

Ordered_date should exist (header level)

Delivery_lead_time should exist (line level)

Earliest_acceptable_date should exist.

Freight_terms should exist

Notes:

During import of orders, shipping tables are not populated.

If importing customers together with the order, OE_ORDER_CUST_IFACE_ALL has to

be populated and the base tables are HZ_PARTIES, HZ_LOCATIONS.

Orders can be categorized based on their status:

1. Entered orders 2. Booked

orders 3. Closed orders

Order Import API OE_ORDER_PUB.GET_ORDER and PROCESS_ORDER can also

be used to import orders.

Some important columns that need to populated in the interface tables:

OE_HEADERS_IFACE_ALL:

ORIG_SYS_DOCUMENT_REF

ORDER_SOURCE

CONVERSION_RATE

ORG_ID

ORDER_TYPE_ID

PRICE_LIST

SOLD_FROM_ORG_ID

SOLD_TO_ORG_ID

SHIP_TO_ORG_ID

SHIP_FROM_ORG_ID
CUSTOMER_NAME

INVOICE_TO_ORG_ID

OPERATION_CODE

OE_LINES_IFACE_ALL

ORDER_SOURCE_ID

ORIG_SYS_DOCUMENT_REF

ORIG_SYS_LINE_REF

ORIG_SYS_SHIPMENT_REF

INVENTORY_ITEM_ID

LINK_TO_LINE_REF

REQUEST_DATE

DELIVERY_LEAD_TIME

DELIVERY_ID

ORDERED_QUANTITY

ORDER_QUANTITY_UOM

SHIPPING_QUANTITY

PRICING_QUANTITY

PRICING_QUANTITY_UOM
SOLD_FROM_ORG_ID

SOLD_TO_ORG_ID

INVOICE_TO_ ORG_ID

SHIP_TO_ORG_ID

PRICE_LIST_ID

PAYMENT_TERM_ID

 Item import (Item conversion)

The Item Interface lets you import items into Oracle Inventory.

Pre-requisites:

Creating an Organization

Code Combinations

Templates

Defining Item Status Codes

Defining Item Types

Interface tables:

MTL_SYSTEM_ITEMS_INTERFACE

MTL_ITEM_REVISIONS_INTERFACE (If importing revisions)

MTL_ITEM_CATEGORIES_INTERFACE (If importing categories)

 MTL_INTERFACE_ERRORS (View errors after import)

Concurrent Program:

Item import

In the item import parameters form, for the parameter 'set process id', specify the

'set process id' value given in the mtl_item_categories_interface table. The

parameter 'Create or Update' can have any value. Through the import process, we

can only create item category assignment(s). Updating or Deletion of item category

assignment is not supported.

Base Tables:

MTL_SYSTEM_ITEMS_B

MTL_ITEM_REVISIONS_B

MTL_CATEGORIES_B

MTL_CATEGORY_SETS_B

MTL_ITEM_STATUS

MTL_ITEM_TEMPLATES

Validations:

Check for valid item type.

Check for valid part_id/segment of the source table.

Validate part_id/segment1 for master org.

 Validate and translate template id of the source table.

Check for valid template id. (Attributes are already set for items, default

attributes for that template, i.e., purchasable, stockable, etc )

Check for valid item status.

Validate primary uom of the source table.

Validate attribute values.

Validate other UOMs of the source table.

Check for unique item type. Discard the item, if part has non-unique item

type.

Check for description, inv_um uniqueness

Validate organization id.

Load master records and category records only if all

Load child record if no error found.

Some important columns that need to populated in the interface tables:

MTL_SYSTEM_ITEMS_INTERFACE:

PROCESS_FLAG = 1 (1= Pending, 2= Assign Complete, 3= Assign/Validation Failed,

4= Validation succeeded; Import failed, 5 = Import in Process, 7 = Import

succeeded)

TRANSACTION_TYPE = ‘CREATE’, ‘UPDATE’

SET_PROCESS_ID = 1

ORGANIZATION_ID

DESCRIPTION

ITEM_NUMBER and/or SEGMENT (n)

MATERIAL_COST

REVISION

TEMPLATE_ID

SUMMARY_FLAG

ENABLED_FLAG

PURCHASING_ITEM_FLAG

SALES_ACCOUNT (defaulted from

MTL_PARAMETERS.SALES_ACCOUNT)

COST_OF_SALES_ACCOUNT (defaulted from

MTL_PARAMETERS.COST_OF_SALES_ACCOUNT)

MTL_ITEM_CATEGORIES_INTERFACE:

INVENTORY_ITEM_ID or ITEM_NUMBER.

ORGANIZATION_ID or ORGANIZATION_CODE or both.

TRANSACTION_TYPE = 'CREATE' ('UPDATE' or 'DELETE' is not possible through Item

Import).

CATEGORY_SET_ID or CATEGORY_SET_NAME or both.

CATEGORY_ID or CATEGORY_NAME or both.

PROCESS_FLAG = 1

SET_PROCESS_ID (The item and category interface records should have the same

set_process_id, if you are importing item and category assignment together)

MTL_ITEM_REVISIONS_INTERFACE:

INVENTORY_ITEM_ID or ITEM_NUMBER (Must match the

ORGANIZATION_ID or ORGANIZATION_CODE or both

REVISION

CHANGE_NOTICE

ECN_INITIATION_DATE

IMPLEMENTATION_DATE

IMPLEMENTED_SERIAL_NUMBER

EFFECTIVITY_DATE

ATTRIBUTE_CATEGORY

ATTRIBUTEn
REVISED_ITEM_SEQUENCE_ID

DESCRIPTION

PROCESS_FLAG = 1

TRANSACTION_TYPE = 'CREATE'

SET_PROCESS_ID = 1

Each row in the mtl_item_revisions_interface table must have the REVISION and

EFFECTIVITY_DATE in alphabetical (ASCII sort) and chronological order.

 Inventory On-hand quantity Interface

This interface lets you import the on hand inventory into Oracle.

Interface tables:

MTL_TRANSACTIONS_INTERFACE

MTL_MTL_TRANSACTION_LOTS_INTERFACE (If the item is Lot Controlled)

MTLL_SERIAL_NUMBERS_INTERFACE (If the item is Serial Controlled)

Concurrent Program:

Launch the Transaction Manager through Interface Manager or explicitly call the

API – INV_TXN_MANAGER_PUB.PROCESS_TRANSACTIONS () to launch a dedicated

transaction worker to process them.

The Transaction Manager picks up the rows to process based on the LOCK_FLAG,

TRANSACTION_MODE, and PROCESS_FLAG. Only records with TRANSACTION_MODE

of 3, LOCK_FLAG of '2', and PROCESS_FLAG of '1' will be picked up by the

Transaction Manager and assigned to a Transaction Worker. If a record fails to

process completely, then PROCESS_FLAG will be set to '3' and ERROR_CODE and

ERROR_EXPLANATION will be populated with the cause for the error.

Base Tables:

MTL_ON_HAND_QUANTITIES

MTL_LOT_NUMBERS

MTL_SERIAL_NUMBERS

Validations:

Validate organization_id

Check if item is assigned to organization

Validate disposition_id

Check if the item for the org is lot controlled before inserting into the Lots interface

table.

Check if the item for the org is serial controlled before inserting into Serial interface

table.

Check if inventory already exists for that item in that org and for a lot.

Validate organization_id, organization_code.

Validate inventory item id.

Transaction period must be open.

Some important columns that need to be populated in the interface tables:

MTL_TRANSACTIONS_INTERFACE:

TRANSACTION_SOURCE_NAME (ANY USER DEFINED VALUE),

TRANSACTION_HEADER_ID (MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL)

TRANSACTION_INTERFACE_ID (MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL – If

item is lot or serial controlled, use this field to link to mtl_transactions_interface

otherwise leave it as NULL),

TRANSACTION_DATE,

TRANSACTION_TYPE_ID,

PROCESS_FLAG (1 = Yet to be processed, 2 = Processed, 3= Error)

TRANSACTION_MODE (2 = Concurrent – to launch a dedicated transaction worker to

explicitly process a set of transactions, 3 = Background – will be picked up by

transaction manager polling process and assigned to transaction worker. These will

not be picked up until the transaction manager is running)

SOURCE_CODE,

SOURCE_HEADER_ID,

SOURCE_LINE_ID (Details about the source like Order Entry etc for tracking

purposes)

TRANSACTION_SOURCE_ID

Source Type Foreign Key Reference

Account GL_CODE_COMBINATIONS.CODE_COMBINATION_ID

Account Alias MTL_GENERIC_DISPOSITIONS.DISPOSITION_ID

Job or schedule WIP_ENTITIES.WIP_ENTITY_ID

Sales Order MTL_SALES_ORDERS.SALES_ORDER_ID

ITEM_SEGMENT1 TO 20,

TRANSACTION_QTY,

TRANSACTION_UOM,

SUBINVENTORY_CODE,

ORGANIZATION_ID,

LOC_SEGMENT1 TO 20.

MTL_TRANSACTION_LOTS_INTERFACE:

TRANSACTION_INTERFACE_ID,

LOT_NUMBER,

LOT_EXPIRATION_DATE,

TRANSACTION_QUANTITY,

SERIAL_TRANSACTION_TEMP_ID (This is required for items under both lot and

serial control to identify child records in mtl_serial_numbers_interface)

MTL_SERIAL_NUMBERS_INTERFACE :

TRANSACTION_INTERFACE_ID,

FM_SERIAL_NUMBER,

TO_SERIAL_NUMBER,

VENDOR_SERIAL_NUMBER

 Customer conversion

Customer Interface helps you create customers in Oracle Applications.

Interface tables:

RA_CUSTOMERS_INTERFACE_ALL

RA_CUSTOMER_PROFILES_INT_ALL

RA_CONTACT_PHONES_INT_ALL

RA_CUSTOMER_BANKS_INT_ALL

RA_CUST_PAY_METHOD_INT_ALL

Base tables:

RA_CUSTOMERS

RA_ADDRESSES_ALL

RA_CUSTOMER_RELATIONSHIPS_ALL

RA_SITE_USES_ALL
 Concurrent program:

Customer Interface

Validations:

Check if legacy values fetched are valid.

Check if customer address site is already created.

Check if customer site use is already created.

Check is customer header is already created.

Check whether the ship_to_site has associated bill_to_site

Check whether associated bill_to_site is created or not.

Profile amounts validation:

Validate cust_account_id, validate customer status.

Check if the location already exists in HZ_LOCATIONS. If does not exist, create

new location.

Some important columns that need to be populated in the interface tables:

RA_CUSTOMERS_INTERFACE_ALL:

ORIG_SYSTEM_CUSTOMER_REF

SITE_USE_CODE

ORIG_SYSTEM_ADDRESS_REF
INSERT_UPDATE_FLAG (I = Insert, U = Update)

CUSTOMER_NAME

CUSTOMER_NUMBER

CUSTOMER_STATUS

PRIMARY_SITE_USE_FLAG

LOCATION

ADDRESS1

ADDRESS2

ADDRESS3

ADDRESS4

CITY

STATE

PROVINCE

COUNTY

POSTAL_CODE

COUNTRY

CUSTOMER_ATTRIBUTE1

CUSTOMER_ATTRIBUTE2
CUSTOMER_ATTRIBUTE3

CUSTOMER_ATTRIBUTE4

CUSTOMER_ATTRIBUTE5

LAST_UPDATED_BY

LAST_UPDATE_DATE

CREATED_BY

CREATION_DATE

ORG_ID

CUSTOMER_NAME_PHONETIC

RA_CUSTOMER_PROFILES_INT_ALL:

INSERT_UPDATE_FLAG

ORIG_SYSTEM_CUSTOMER_REF

ORIG_SYSTEM_ADDRESS_REF

CUSTOMER_PROFILE_CLASS_NAME

CREDIT_HOLD

LAST_UPDATED_BY

LAST_UPDATE_DATE

CREATION_DATE
CREATED_BY

ORG_ID

RA_CONTACT_PHONES_INT_ALL:

ORIG_SYSTEM_CONTACT_REF

ORIG_SYSTEM_TELEPHONE_REF

ORIG_SYSTEM_CUSTOMER_REF

ORIG_SYSTEM_ADDRESS_REF

INSERT_UPDATE_FLAG

CONTACT_FIRST_NAME

CONTACT_LAST_NAME

CONTACT_TITLE

CONTACT_JOB_TITLE

TELEPHONE

TELEPHONE_EXTENSION

TELEPHONE_TYPE

TELEPHONE_AREA_CODE

LAST_UPDATE_DATE

LAST_UPDATED_BY
LAST_UPDATE_LOGIN

CREATION_DATE

CREATED_BY

EMAIL_ADDRESS

ORG_ID

 Customer API

Trading Community Architecture (TCA) is an architecture concept designed to

support complex trading communities. These APIs utilize the new TCA model,

inserting directly to the HZ tables.

API Details:

1. Set the organization id

Exec dbms_application_info.set_client_info(‘204’);

2. Create a party and an account

HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT()

HZ_CUST_ACCOUNT_V2PUB.CUST_ACCOUNT_REC_TYPE

HZ_PARTY_V2PUB.ORGANIZATION_REC_TYPE

HZ_CUSTOMER_PROFILE_V2PUB.CUSTOMER_PROFILE_REC_TYPE

3. Create a physical location

HZ_LOCATION_V2PUB.CREATE_LOCATION()
HZ_LOCATION_V2PUB.LOCATION_REC_TYPE

4. Create a party site using party_id you get from step 2 and location_id from

step 3.

HZ_PARTY_SITE_V2PUB.CREATE_PARTY_SITE()

HZ_PARTY_SITE_V2PUB.PARTY_SITE_REC_TYPE

5. Create an account site using account_id you get from step 2 and party_site_id

from step 4.

HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_ACCT_SITE()

HZ_CUST_ACCOUNT_SITE_V2PUB.CUST_ACCT_SITE_REC_TYPE

6. Create an account site use using cust_acct_site_id you get from step 5 ans

site_use_code = ‘BILL_TO’.

HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_SITE_USE()

HZ_CUST_ACCOUNT_SITE_V2PUB.CUST_SITE_USE_REC_TYPE

HZ_CUSTOMER_PROFILE_V2PUB.CUSTOMER_PROFILE_REC_TYPE

Base table:

HZ_PARTIES

HZ_PARTY_SITES

HZ_LOCATIONS

HZ_CUST_ACCOUNTS
HZ_CUST_SITE_USES_ALL

HZ_CUST_ACCT_SITES_ALL

HZ_PARTY_SITE_USES

Validations:

Check if legacy values fetched are valid.

Check if customer address site is already created.

Check if customer site use is already created.

Check is customer header is already created.

Check whether the ship_to_site has associated bill_to_site

Check whether associated bill_to_site is created or not.

Profile amounts validation:

Validate cust_account_id, validate customer status.

Check if the location already exists in HZ_LOCATIONS. If does not exist, create

new location.

For detailed explanation refer to the below article:

http://www.erpschools.com/Apps/oracle-

applications/articles/financials/Receivables/Customer-TCA-Architecture-and-

API/index.aspx

 Auto Invoice interface

This interface is used to import Customer invoices, Credit memos, Debit memos and

On Account credits.

Pre-requisites:

Set of Books

Code combinations

Items

Sales representatives

Customers

Sales Tax rate

Payment Terms

Transaction Types

Freight Carriers

FOB

Batch Sources

Accounting Rules

Interface tables:

RA_INTERFACE_LINES_ALL

RA_INTERFACE_SALESCREDITS
RA_INTERFACE_DISTRIBUTIONS

RA_INTERFACE_ERRORS (details about the failed records)

Base tables:

RA_BATCHES

RA_CUSTOMER_TRX_ALL

RA_CUSTOMER_TRX_LINES_ALL

AR_PAYMENT_SCHEDULES_ALL

RA_CUSTOMER_TRX_LINE_SALESREPS

RA_CUST_TRX_GL_DIST_ALL

RA_CUSTOMER_TRX_TYPES_ALL

Concurrent Program:

Auto invoice master program

Validations:

Check for amount, batch source name, conversion rate, conversion

type.

Validate orig_system_bill_customer_id, orig_system_bill_address_id,

Validate if the amount includes tax flag.

Some important columns that need to be populated in the interface tables:

 RA_INTERFACE_LINES_ALL:

AGREEMENT_ID

COMMENTS

CONVERSION_DATE

CONVERSION_RATE

CONVERSION_TYPE

CREDIT_METHOD_FOR_ACCT_RULE

CREDIT_METHOD_FOR_INSTALLMENTS

CURRENCY_CODE

CUSTOMER_BANK_ACCOUNT_ID

CUST_TRX_TYPE_ID

DOCUMENT_NUMBER

DOCUMENT_NUMBER_SEQUENCE_ID

GL_DATE

HEADER_ATTRIBUTE1–15

HEADER_ATTRIBUTE_CATEGORY

INITIAL_CUSTOMER_TRX_ID

INTERNAL_NOTES
INVOICING_RULE_ID

ORIG_SYSTEM_BILL_ADDRESS_ID

ORIG_SYSTEM_BILL_CONTACT_ID

ORIG_SYSTEM_BILL_CUSTOMER_ID

ORIG_SYSTEM_SHIP_ADDRESS_ID

ORIG_SYSTEM_SHIP_CONTACT_ID

ORIG_SYSTEM_SHIP_CUSTOMER_ID

ORIG_SYSTEM_SOLD_CUSTOMER_ID

ORIG_SYSTEM_BATCH_NAME

PAYMENT_SERVER_ORDER_ID

PREVIOUS_CUSTOMER_TRX_ID

PRIMARY_SALESREP_ID

PRINTING_OPTION

PURCHASE_ORDER

PURCHASE_ORDER_DATE

PURCHASE_ORDER_REVISION

REASON_CODE

RECEIPT_METHOD_ID
RELATED_CUSTOMER_TRX_ID

SET_OF_BOOKS_ID

TERM_ID

TERRITORY_ID

TRX_DATE

TRX_NUMBER

 Receipt API

To bring in Unapplied Receipts and Conversion Receipts for Open Debit items

to reduce the balance to the original amount due.

Pre-requisites:

Set of Books

Code combinations

Items

Quick Codes

Sales representatives

Customers

Sales Tax rate

API:
AR_RECEIPT_API_PUB.CREATE_CASH

AR_RECEIPT_API_PUB.CREATE_AND_APPLY

Base tables:

AR_CASH_RECEIPTS

Validations:

Check the currency and the exchange rate type to assign the exchange rate.

Validate bill to the customer.

Get bill to site use id.

Get the customer trx id for this particular transaction number.

Get payment schedule date for the customer trx id.

 Lockbox interface

AutoLockbox lets us automatically process receipts that are sent directly to

the bank instead of manually feeding them in Oracle Receivables.

AutoLockbox is a three step process:

1. Import: During this step, Lockbox reads and formats the data from your bank

file

into interface table AR_PAYMENTS_INTERFACE_ALL using a SQL *Loader

script.

2. Validation: The validation program checks data in this interface table for
compatibility with Receivables. Once validated, the data is transferred into

QuickCash tables (AR_INTERIM_CASH_RECEIPTS_ALL and

AR_INTERIM_CASH_RCPT_LINES_ALL).

3. Post QuickCash: This step applies the receipts and updates your customer’s

balances.

Pre-Requisites:

Banks

Receipt Class

Payment Method

Receipt Source

Lockbox

Transmission format

AutoCash Rule sets

Interface tables:

AR_PAYMENTS_INTERFACE_ALL (Import data from bank file)

AR_INTERIM_CASH_RECEIPTS_ALL

AR_INTERIM_CASH_RCPT_LINES_ALL (Validate data in interface table and place in

quick cash tables)

Base Tables:

AR_CASH_RECEIPTS

AR_RECEIVABLES_APPLICATIONS

AR_ADJUSTMENTS

AR_DISTRIBUTIONS_ALL

AR_PAYMENT_SCHEDULES_ALL

Concurrent program:

Lockbox

Validations:

Check for valid record type, transmission record id.

Validate sum of the payments within the transmission.

Identify the lockbox number (no given by a bank to identify a lockbox).

Some important columns that need to be populated in the interface tables:

AR_PAYMENTS_INTERFACE_ALL:

STATUS

RECORD_TYPE

LOCKBOX_NUMBER

BATCH_NAME
TRANSIT_ROUTING_NUMBER

ACCOUNT

CHECK_NUMBER

REMITTANCE_AMOUNT

DEPOSIT_DATE

ITEM_NUMBER

CURRENCY_CODE

DEPOSIT_TIME

 AP invoice interface

This interface helps us to import vendor invoices into Oracle applications from

external systems into Oracle Applications.

Pre-requisites:

Set of Books

Code combinations

Employees

Lookups

Interface tables:

AP_INVOICES_INTERFACE
AP_INVOICE_LINES_INTERFACE

Base tables:

AP_INVOICES_ALL – header information

AP_INVOICE_DISTRIBUTIONS_ALL – lines info

Concurrent program:

Payables Open Interface Import

Validations:

Check for valid vendor

Check for Source, Location, org_id, currency_code’s validity

Check for valid vendor site code.

Check if record already exists in payables interface table.

Some important columns that need to be populated in the interface tables:

AP_INVOICES_INTERFACE:

INVOICE_ID

INVOICE_NUM

INVOICE_DATE

VENDOR_NUM

VENDOR_SITE_ID
 INVOICE_AMOUNT

INVOICE_CURRENCY_CODE

EXCHANGE_RATE

EXCHANGE_RATE_TYPE

EXCHANGE_DATE

DESCRIPTION

SOURCE

PO_NUMBER

PAYMENT_METHOD_LOOKUP_CODE

PAY_GROUP_LOOKUP_CODE

ATTRIBUTE1 TO 15

ORG_ID

AP_INVOICE_LINES_INTERFACE:

INVOICE_ID

INVOICE_LINE_ID

LINE_TYPE_LOOKUP_CODE

AMOUNT

DESCRIPTION
 TAX_CODE

PO_NUMBER

PO_LINE_NUMBER

PO_SHIPMENT_NUM

PO_DISTRIBUTION_NUM

PO_UNIT_OF_MEASURE

QUANTITY_INVOICED

DIST_CODE_CONCATENATED

DIST_CODE_COMBINATION_ID

ATTRIBUTE1

ATTRIBUTE2

ATTRIBUTE3

ATTRIBUTE4

ATTRIBUTE5

ORG_ID

 Vendor conversion/interface

This interface is used to import suppliers, supplier sites and site contacts into

Oracle applications.
Pre-requisites setup’s required:

Payment terms

Pay Groups

CCID

Supplier classifications

Bank Accounts

Employees (if employees have to set up as vendors)

Interface tables:

AP_SUPPLIERS_INT

AP_SUPPLIER_SITES_INT

AP_SUP_SITE_CONTACT_INT

Base Tables:

PO_VENDORS

PO_VENDOR_SITES_ALL

PO_VENDOR_CONTACTS

Interface programs:

Supplier Open Interface Import

Supplier Sites Open Interface Import

Supplier Site Contacts Open Interface Import

Validations:

Check if vendor already exists

Check if vendor site already exists

Check if site contact already exists

Check if term is defined.

Some important columns that need to be populated in the interface tables:

AP_SUPPLIERS_INT :

VENDOR_NUMBER, VENDOR_NAME, VENDOR_TYPE, STATE_REPORTABLE,

FED_REPORTABLE, NUM_1099, TYPE_1099, PAY_GROUP_LOOKUP_CODE,

VENDOR_ID is auto generated.

AP_SUPPLIER_SITES_INT:

VENDOR_SITE_ID, ORG_ID, VENDOR_SITE_CODE, INACTIVE_DATE, PAY_SITE,

PURCHASING_SITE, SITE_PAYMENT_TERM, ADDRESS1, ADDRESS2.ADDRESS3,

CITY, STATE, COUNTRY, ZIP, PH_NUM, FAX_NUMBER, TAX_REPORTING_SITE_FLAG.

AP_SUP_SITE_CONTACTS_INT:

VENDOR_ID, VENDOR_SITE_ID, FIRST_NAME, LAST_NAME, AREA_CODE, PHONE,

EMAIL, ORG_ID

 Purchase Order conversion:

The Purchasing Document Open Interface concurrent program was replaced by two

new concurrent programs Import Price Catalogs and Import Standard Purchase

Orders. Import Price Catalogs concurrent program is used to import Catalog

Quotations, Standard Quotations, and Blanket Purchase Agreements. Import

Standard Purchase Orders concurrent program is used to import Unapproved or

Approved Standard Purchase Orders.

Import Standard Purchase Orders

Pre-requisites:

Suppliers, sites and contacts

Buyers

Line Types

Items

PO

Charge account setup

Interface Tables:

PO_HEADERS_INTERFACE

PO_LINES_INTERFACE

PO_DISTRIBUTIONS_INTERFACE

PO_INTERFACE_ERRORS (Fallouts)

Interface Program:
Import Standard Purchase Orders.

Base Tables:

PO_HEADERS_ALL

PO_LINES_ALL

PO_DISTRIBUTIONS_ALL

PO_LINE_LOCATIONS_ALL

Validations:

Header:

Check if OU name is valid

Check if Supplier is valid

Check if Supplier site is valid

Check if buyer is valid

Check if Payment term is valid

Check if Bill to and ship to are valid

Check if FOB, freight terms are valid

Lines :

Check if Line_type, ship_to_org, item, uom, ship_to_location_id, requestor,

charge_account, deliver_to_location are valid

General:

Check for duplicate records in interface tables

Check if the record already exists in base tables.

Some important columns that need to be populated in the interface tables:

PO_HEADERS_INTERFACE :

INTERFACE_HEADER_ID (PO_HEADERS_INTERFACE_S.NEXTVAL), BATCH_ID,

ORG_ID, INTERFACE_SOURCE_CODE, ACTION (‘ORIGINAL’,’UPDATE’,’REPLACE’),

GROUP_CODE, DOCUMENT_TYPE_CODE, PO_HEADER_ID (NULL), RELEASE_ID,

RELEASE_NUM, CURRENCY_CODE, RATE, AGENT_NAME, VENDOR_ID,

VENDOR_SITE_ID, SHIP_TO_LOCATION, BILL_TO_LOCATION, , PAYMENT_TERMS

PO_LINES_INTERFACE :

INTERFACE_LINE_ID, INTERFACE_HEADER_ID, LINE_NUM, SHIPMENT_NUM, ITEM,

REQUISITION_LINE_ID, UOM, UNIT_PRICE, FREIGHT_TERMS, FOB

PO_DISTRIBUTIONS_INTERFACE :

INTERFACE_LINE_ID, INTERFACE_HEADER_ID, INTERFACE_DISTRIBUTION_ID,

DISTRIBUTION_NUM, QUANTITY_ORDERED, QTY_DELIVERED, QTY_BILLED,

QTY_CANCELLED, DELIVER_TO_LOCATION_ID, DELIVER_TO_PERSON_ID,

SET_OF_BOOKS, CHARGE_ACCT, AMOUNT_BILLED.

Import Blanket Purchase Agreements:

Interface Tables:

PO_HEADERS_INTERFACE
PO_LINES_INTERFACE

Interface program:

Import Price Catalogs

Base tables:

PO_HEADERS_ALL

PO_LINES_ALL

PO_LINE_LOCATIONS_ALL

Example:

Suppose you want to create a blanket with one line and two price breaks and the

details for the price break are as below:

1) Quantity = 500, price = 10, effective date from '01-JAN-2006' to

'31-JUN-2006'

2) Quantity = 500, price = 11, effective date from '01-JUL-2006' to

'01-JAN-2007'

To create the above the BPA, you would create ONE record in

PO_HEADERS_INTERFACE and THREE records in PO_LINES_INTERFACE

LINE1: It will have only the line information. LINE NUM would be 1.

LINE2: For the first Price Break details, LINE NUM will be the same as above i.e. 1.

SHIPMENT_NUM would be 1 and SHIPMENT_TYPE would be ‘PRICE BREAK’

LINE3: For the second Price Break details, LINE NUM will be the same as above i.e.

1. SHIPMENT_NUM would be 2 and SHIPMENT_TYPE would be ‘PRICE BREAK’

All the line-level records above must have the same INTERFACE_HEADER_ID.

For detailed explanation refer to the below article:

http://www.erpschools.com/Apps/oracle-

applications/articles/financials/Purchasing/Import-Blanket-Purchase-

Agreements/index.aspx

 Requisition import

You can automatically import requisitions into Oracle Applications using the

Requisitions Open Interface

Pre-requisites:

Set of Books

Code combinations

Employees

Items

Define a Requisition Import Group-By method in the Options window.

Associate a customer with your deliver-to location using the Customer

Addresses window for internally sourced requisitions.

Interface tables:

PO_REQUISITIONS_INTERFACE_ALL
 PO_REQ_DIST_INTERFACE_ALL

Base tables:

PO_REQUISITIONS_HEADERS_ALL

PO_REQUISITION_LINES_ALL

PO_REQ_DISTRIBUTIONS_ALL

Concurrent program:

REQUISITION IMPORT

Validations:

Check for interface transaction source code, requisition destination

type.

Check for quantity ordered, authorization status type.

Some important columns that need to be populated in the interface tables:

PO_REQUISITIONS_INTERFACE_ALL :

INTERFACE_SOURCE_CODE (to identify the source of your Requisitions)

DESTINATION_TYPE_CODE

AUTHORIZATION_STATUS

PREPARER_ID or PREPARER_NAME

QUANTITY
CHARGE_ACCOUNT_ID or charge account segment values

DESTINATION_ORGANIZATION_ID or DESTINATION_ORGANIZATION_CODE

DELIVER_TO_LOCATION_ID or DELIVER_TO_LOCATION_CODE

DELIVER_TO_REQUESTOR_ID or DELIVER_TO_REQUESTOR_NAME

ORG_ID

ITEM_ID or item segment values (values if the SOURCE_TYPE_CODE or

DESTINATION_TYPE_CODE is 'INVENTORY')

PO_REQ_DIST_INTERFACE_ALL :

CHARGE_ACCOUNT_ID or charge account segment values

DISTRIBUTION_NUMBER

DESTINATION_ORGANIZATION_ID

DESTINATION_TYPE_CODE

INTERFACE_SOURCE_CODE

ORG_ID

DIST_SEQUENCE_ID (if MULTI_DISTRIBUTIONS is set to Y)

 PO Receipts Interface

The Receiving Open Interface is used for processing and validating receipt data that

comes from sources other than the Receipts window in Purchasing.

Pre-requisites:
 Set of Books

Code combinations

Employees

Items

Interface tables:

RCV_HEADERS_INTERFACE

RCV_TRANSACTIONS_INTERFACE

PO_INTERFACE_ERRORS

Concurrent program:

RECEIVING OPEN INTERFACE

Base tables:

RCV_SHIPMENT_HEADERS

RCV_SHIPMENT_LINES

RCV_TRANSACTIONS

Validations:

Check that SHIPPED_DATE should not be later than today.

Check if vendor is valid.

If Invoice number is passed, check for its validity

Check if Item is valid

Some important columns that need to be populated in the interface tables:

RCV_HEADERS_INTERFACE:

HEADER_INTERFACE_ID

GROUP_ID

PROCESSING_STATUS_

CODE

RECEIPT_SOURCE_CODE

TRANSACTION_TYPE

SHIPMENT_NUM

RECEIPT_NUM

VENDOR_NAME

SHIP_TO_

ORGANIZATION_CODE

SHIPPED_DATE

INVOICE_NUM

INVOICE_DATE

TOTAL_INVOICE_
AMOUNT

PAYMENT_TERMS_ID

EMPLOYEE_NAME

VALIDATION_FLAG (Indicates whether to validate a row or not, values ‘Y’, ‘N’)

RCV_TRANSACTIONS_INTERFACE:

INTERFACE_TRANSACTION_ID

GROUP_ID

TRANSACTION_TYPE (’SHIP’ for a standard shipment (an ASN or ASBN) or ’RECEIVE’

for a standard receipt)

TRANSACTION_DATE

PROCESSING_STATUS_CODE =’PENDING’

CATEGORY_ID

QUANTITY

UNIT_OF_MEASURE

ITEM_DESCRIPTION

ITEM_REVISION

EMPLOYEE_ID

AUTO_TRANSACT_CODE
SHIP_TO_LOCATION_ID

RECEIPT_SOURCE_CODE

TO_ORGANIZATION_CODE

SOURCE_DOCUMENT_CODE

PO_HEADER_ID

PO_RELEASE_ID

PO_LINE_ID

PO_LINE_LOCATION_ID

PO_DISTRIBUTION_ID

SUBINVENTORY

HEADER_INTERFACE_ID

DELIVER_TO_PERSON_NAME

DELIVER_TO_LOCATION_CODE

VALIDATION_FLAG

ITEM_NUM

VENDOR_ITEM_NUM

VENDOR_ID

VENDOR_SITE_ID
ITEM_ID

ITEM_DESCRIPTION

SHIP_TO_LOCATION_ID

 GL Journal interface

This interface lets you import journals from other applications like Receivables,

Payables etc to integrate the information with General Ledger.

Pre-requisites:

Set of Books

Flex field Value sets

Code Combinations

Currencies

Categories

Journal Sources

Interface tables:

GL_INTERFACE

Base tables:

GL_JE_HEADERS

GL_JE_LINES
GL_JE_BACTHES

Concurrent Program:

Journal Import

Journal Posting --- populates GL_BALANCES

Validations:

Validate SOB, journal source name, journal category name, actual flag

A – Actual amounts

B – Budget amounts

E – Encumbrance amount

If you enter E in the interface table, then enter appropriate encumbrance ID, if B

enter budget id.

Check if accounting date or GL date based period name is valid (i.e., not closed).

Check if accounting date falls in open or future open period status.

Check chart of accounts id based on Sob id.

Check if code combination is valid and enabled.

Check if record already exists in GL interface table.

Check if already journal exists in GL application.

Some important columns that need to be populated in the interface tables:

GL_INTERFACE:

STATUS

SET_OF_BOOKS_ID

ACCOUNTING_DATE

CURRENCY_CODE

DATE_CREATED

CREATED_BY

ACTUAL_FLAG

USER_JE_CATEGORY_NAME

USER_JE_SOURCE_NAME

CURRENCY_CONVERSION_DATE

ENCUMBRANCE_TYPE_ID

BUDGET_VERSION_ID

USER_CURRENCY_CONVERSION_TYPE

CURRENCY_CONVERSION_RATE

SEGMENT1 to

ENTERED_DR

ENTERED_CR
 ACCOUNTED_DR

ACCOUNTED_CR

TRANSACTION_DATE

PERIOD_NAME

JE_LINE_NUM

CHART_OF_ACCOUNTS_ID

FUNCTIONAL_CURRENCY_CODE

CODE_COMBINATION_ID

DATE_CREATED_IN_GL

GROUP_ID

 GL budget interface

Budget interface lets you load budget data from external sources into Oracle

Applications.

Pre-requisites:

Set of Books

Flex field Value sets

Code Combinations

Interface tables:
GL_BUDGET_INTERFACE

Base tables:

GL_BUDGETS

GL_BUDGET_ASSIGNMENTS

GL_BUDGET_TYPES

Concurrent program:

Budget Upload

Validations:

Check if CURRENCY_CODE is valid.

Check if SET_OF_BOOKS_ID is valid.

Check if BUDGET_ENTITY_NAME (budget organization) is valid.

Some important columns that need to be populated in the interface tables:

GL_BUDGET_INTERFACE:

BUDGET_NAME NOT

BUDGET_ENTITY_NAME

CURRENCY_CODE

FISCAL_YEAR

UPDATE_LOGIC_TYPE
BUDGET_ENTITY_ID

SET_OF_BOOKS_ID

CODE_COMBINATION_ID

BUDGET_VERSION_ID

PERIOD_TYPE

DR_FLAG

STATUS

ACCOUNT_TYPE

PERIOD1_AMOUNT through PERIOD60_AMOUNT

SEGMENT1 through SEGMENT30

 GL daily conversion rates

This interface lets you load the rates automatically into General Ledger.

Pre-requisites:

Currencies

Conversion rate Types

Interface tables:

GL_DAILY_RATES_INTERFACE

Base tables:
GL_DAILY_RATES

GL_DAILY_CONVERSION_TYPES

Concurrent Program:

You do not need to run any import programs. The insert, update, or deletion of

rates in GL_DAILY_RATES is done automatically by database triggers on the

GL_DAILY_RATES_INTERFACE. All that is required is to develop program to populate

the interface table with daily rates information.

Validations:

Check if FROM_CURRENCY and TO_CURRENCY are valid.

Check if USER_CONVERSION_TYPE is valid.

Some important columns that need to be populated in the interface tables:

GL_DAILY_RATES_INTERFACE :

FROM_CURRENCY

TO_CURRENCY

FROM_CONVERSION_DATE

TO_CONVERSION_DATE

USER_CONVERSION_TYPE

CONVERSION_RATE

MODE_FLAG (D= Delete, I = Insert, U = Update)

INVERSE_CONVERSION_RATE

Get On Hand Quantities Through API

This script can be used to get the below quantities.
1. On-hand Quantity
2. Available to Reserve
3. Quantity Reserved
4. Quantity Suggested
5. Available to Transact
6. Available to Reserve

You can also get the On-hand quantities from the table mtl_onhand_quantities

GET ON-HAND QUANTITIES API

DECLARE

x_return_status VARCHAR2 (50);

x_msg_count VARCHAR2 (50);

x_msg_data VARCHAR2 (50);

v_item_id NUMBER;

v_org_id NUMBER;

v_qoh NUMBER;

v_rqoh NUMBER;

v_atr NUMBER;

v_att NUMBER;

v_qr NUMBER;
 v_qs NUMBER;

v_lot_control_code BOOLEAN;

v_serial_control_code BOOLEAN;

BEGIN

-- Set the variable values

v_item_id := '6566';

v_org_id := 61;

v_qoh := NULL;

v_rqoh := NULL;

v_atr := NULL;

v_lot_control_code := FALSE;

v_serial_control_code := FALSE;

-- Set the org context

fnd_client_info.set_org_context (1);
-- Call API

inv_quantity_tree_pub.query_quantities

(p_api_version_number => 1.0,

p_init_msg_lst => 'F',

x_return_status => x_return_status,

x_msg_count => x_msg_count,

x_msg_data => x_msg_data,

p_organization_id => v_org_id,

p_inventory_item_id => v_item_id,

p_tree_mode => apps.inv_quantity_tree_pub.g_transaction_mode,

-- or 3

p_is_revision_control => FALSE,

p_is_lot_control => v_lot_control_code,

-- is_lot_control,

p_is_serial_control => v_serial_control_code,

p_revision => NULL, -- p_revision,

p_lot_number => NULL, -- p_lot_number,

p_lot_expiration_date => SYSDATE,

p_subinventory_code => NULL, -- p_subinventory_code,

p_locator_id => NULL, -- p_locator_id,

-- p_cost_group_id => NULL, -- cg_id,

p_onhand_source => 3,

x_qoh => v_qoh, -- Quantity on-hand

x_rqoh => v_rqoh, --reservable quantity on-hand

x_qr => v_qr,

x_qs => v_qs,

x_att => v_att, -- available to transact

x_atr => v_atr -- available to reserve

);

DBMS_OUTPUT.put_line ('On-Hand Quantity: ' || v_qoh);

DBMS_OUTPUT.put_line ('Available to reserve: ' || v_atr);

DBMS_OUTPUT.put_line ('Quantity Reserved: ' || v_qr);

DBMS_OUTPUT.put_line ('Quantity Suggested: ' || v_qs);

 DBMS_OUTPUT.put_line ('Available to Transact: ' || v_att);

DBMS_OUTPUT.put_line ('Available to Reserve: ' || v_atr);

Item Open Interface (INCOIN/IOI) Setup and How-To [ID 115557.1]

Modified 22-SEP-2010 Type BULLETIN Statu

s PUBLISHED

In this Document
Purpose
Scope and Application
Item Open Interface (INCOIN/IOI) Setup and How-To
1. Setup
2. How-To
2.1 Create Mode
2.2 Update Mode
2.3. Functionality
2.4 To populate material costs from IOI
3. Not Supported Issues
* Updating Item Attributes to NULL
4. Importing Master and Child Records
5. Importing Categories
6. Revisions
7. Error Checking
8. Template Use
References

Applies to:
Oracle Inventory Management

Purpose
Document the setup and usage of the Item Open Interface (IOI) process for the import of items.

Scope and Application

This document outlines various aspects of the item import to supplement existing documentation like
the Manufacturing APIs and Open Interfaces Guide.

Item Open Interface (INCOIN/IOI) Setup and How-To

This document will walk the user through the setup and execution of the Item
Open Interface (IOI) and provide examples for creating and updating items,
setting attributes to NULL, importing master and child records, importing
revisions and using templates.

1. Setup

Follow this checklist before attempting to load items via the Item Open
Interface:

a) If any IOI patches have been applied, verify that there are no invalid
packages. To find invalid objects, run the following:

b) Ensure that INCOIN has been relinked if any IOI patches were applied.
adrelink sample command lines to relink aiap:

c) Check that the standard indexes exist on the MTL_SYSTEM_ITEMS

(MTL_SYSTEM_ITEMS_B in Release 11.5) and MTL_SYSTEM_ITEMS_INTERFACE tables.

select TABLE_NAME, INDEX_NAME

from ALL_INDEXES
where TABLE_NAME in
('MTL_SYSTEM_ITEMS', 'MTL_SYSTEM_ITEMS_INTERFACE', 'MTL_SYSTEM_ITEMS_B')
order by TABLE_NAME, INDEX_NAME;

Example results from Release 11.0.3 would include the following indexes:

MTL_SYSTEM_ITEMS_INTERFACE_N1
MTL_SYSTEM_ITEMS_INTERFACE_N2
MTL_SYSTEM_ITEMS_INTERFACE_U1
MTL_SYSTEM_ITEMS_N1
MTL_SYSTEM_ITEMS_N2
MTL_SYSTEM_ITEMS_N3
MTL_SYSTEM_ITEMS_N4
MTL_SYSTEM_ITEMS_N5
MTL_SYSTEM_ITEMS_N6

Example results from Release 11i (11.5.x) would include the following indexes:

MTL_SYSTEM_ITEMS_INTERFACE_N1
MTL_SYSTEM_ITEMS_INTERFACE_N2
MTL_SYSTEM_ITEMS_INTERFACE_N3
MTL_SYSTEM_ITEMS_INTERFACE_U1
MTL_SYSTEM_ITEMS_B_N1
MTL_SYSTEM_ITEMS_B_N2
MTL_SYSTEM_ITEMS_B_N3
MTL_SYSTEM_ITEMS_B_N4
MTL_SYSTEM_ITEMS_B_N5
MTL_SYSTEM_ITEMS_B_N6
MTL_SYSTEM_ITEMS_B_N7
MTL_SYSTEM_ITEMS_B_U1

Example results on R12.0.x include:

MTL_SYSTEM_ITEMS_INTERFACE_N1
MTL_SYSTEM_ITEMS_INTERFACE_N2
MTL_SYSTEM_ITEMS_INTERFACE_N3
MTL_SYSTEM_ITEMS_INTERFACE_N4
MTL_SYSTEM_ITEMS_INTERFACE_N5
MTL_SYSTEM_ITEMS_INTERFACE_N6
MTL_SYSTEM_ITEMS_INTERFACE_U2
MTL_SYSTEM_ITEMS_B_N1
MTL_SYSTEM_ITEMS_B_N10
MTL_SYSTEM_ITEMS_B_N11
MTL_SYSTEM_ITEMS_B_N12
MTL_SYSTEM_ITEMS_B_N13
MTL_SYSTEM_ITEMS_B_N14
MTL_SYSTEM_ITEMS_B_N2
MTL_SYSTEM_ITEMS_B_N3
MTL_SYSTEM_ITEMS_B_N4
MTL_SYSTEM_ITEMS_B_N5
MTL_SYSTEM_ITEMS_B_N6
MTL_SYSTEM_ITEMS_B_N7
MTL_SYSTEM_ITEMS_B_N8
MTL_SYSTEM_ITEMS_B_N9
MTL_SYSTEM_ITEMS_B_U1
MTL_SYSTEM_ITEMS_N8

d) Check if the internal and standard concurrent managers are up and running before loading items
(system admin resp/concurrent/manager/administer) Check the actual and target processes, the numbers
should be the same for each.

e) Define an item through the Define Item form. If this does not work, then it is unlikely that items will load
through the interface. ex. inventory responsibility/items/master items Enter item name, description and
attributes needed and save the item.

f) Truncate all Item Import tables before loading MTL_SYSTEM_ITEMS_INTERFACE. For example:

TRUNCATE TABLE INV.MTL_SYSTEM_ITEMS_INTERFACE;

TRUNCATE TABLE INV.MTL_INTERFACE_ERRORS;
TRUNCATE TABLE INV.MTL_ITEM_REVISIONS_INTERFACE;
TRUNCATE TABLE INV.MTL_ITEM_CATEGORIES_INTERFACE;

Note: If Purchasing is fully installed but Inventory is only a shared product, users should be able to run the
IOI. You should, however, be aware that the IOI code is not shipped with standalone Purchasing. You will
have to obtain the code by downloading the latest IOI megapatches.
2. How-To

2.1 Create Mode

To run the item open interface in create mode, populate the MTL_SYSTEM_ITEMS_INTERFACE with the
following minimum required columns when creating new items:

PROCESS_FLAG = 1
TRANSACTION_TYPE = 'CREATE'
SET_PROCESS_ID = 1
ORGANIZATION_ID = Master Org id
DESCRIPTION = 'Description of the item'
ITEM_NUMBER [and/or SEGMENT(n)]

2.2 Update Mode

Running the Item Open Interface In Update Mode To update existing item(s), set TRANSACTION_TYPE
= 'UPDATE'.

Note: Creating and updating items in a single run of the Item Open Interface is not supported functionality.
For best performance, use inventory_item_id when updating items.

2.3. Functionality
Every attribute updateable from the Item form is updateable through the interface, and all required
validations are performed to enforce:

• Item Attribute Interdependencies

• Master - Child Attribute Dependencies
• Status Controlled Attributes

Templates can be applied to existing Items. For best results, use template_id and template_name. The
Item status can be changed for existing Items, and the proper attributes are Defaulted / Set accordingly.
The Status change is recorded in MTL_PENDING_ITEM_STATUS.

2.4 To populate material costs from IOI

Populate the LIST_PRICE_PER_UNIT column with a value while importing items and you will see your
material cost for your item in MTL_SYSTEM_ITEMS after running the Item Import process. (CREATE
transaction_type only)

Master level controlled attributes are correctly propagated to the Child records when the Master Item
record is updated. When launching items into the Master Item Org, the Child records are copied into
MTL_SYSTEM_ITEMS_INTERFACE for validation, and are identified with a transaction_type of
'AUTO_CHILD'. These records are deleted if the parameter 'Delete Processed Rows' has been passed as
'Yes', and remain for diagnostic purposes if the parameter is passed as 'No'.

When the defining attribute for a Functional area is enabled, the proper default category set and category
is assigned to the Item. For example: If an Inventory item is selected, and the default category set for
Inventory items is "inv.items", with a default category of "misc.misc", this is the category set and category
that will be assigned during the IOI process.

3. Not Supported Issues

• Item Costs cannot be UPDATED (using "UPDATE" transaction_type) through the interface.
• New Item revisions cannot be added to existing Items.
• Current functionality does not support updates to a PTO MODEL ITEM through the IOI update
feature. See note: Note 1076412.6.

* Updating Item Attributes to NULL

The method to update these columns to NULL is to use the following values:

• for Numeric fields: insert -999999

• for Character fields: insert '!'
• for Date fields: the above list does not include any updateable date fields.

4. Importing Master and Child Records

Previously, IOI processed items in an order that did not recognize that Master Items were loaded before
child records in MTL_SYSTEM_ITEMS. Therefore, users were advised to Import Master Records first in
one run and then separately Import Child records. The IOI code now automatically separates Master
records from Children, and processes Master records first. However, as one IOI process is not aware of
other IOI processes running in parallel, do not split a given item's separate Organization records into two
different SET_PROCESS_IDs that are being run in parallel. Doing so may cause the Child record to be
processed before the Master record.

Master level controlled attributes are correctly propagated to the Child records when the Master Item
record is updated. When launching items into the Master Item Org, the Child records are copied into
MTL_SYSTEM_ITEMS_INTERFACE for validation, and are identified with a transaction_type of
'AUTO_CHILD'.

5. Importing Categories
Apply Patch 1644995 for R11.0. This functionality is not available in R11i until 11.5.5.

With this enhancement, the user will have the flexiblity to import multiple item category
assignment as part of the item import process. The user procedures are as follows:

1. Populate the item interface tables (MTL_SYSTEM_ITEMS_INTERFACE). This step is necessary if you
are creating items and categories in the same run. For importing item category assignments for already
existing items, you do not need to populate item interface table. For details regarding populating the item
interface table, please refer to Open Interface Manual.

2. Poplate the item categories interface table (MTL_ITEM_CATEGORIES_INTERFACE). This table has
the following columns :

INVENTORY_ITEM_ID NUMBER
CATEGORY_SET_ID NUMBER
CATEGORY_ID NUMBER
LAST_UPDATE_DATE DATE
LAST_UPDATED_BY NUMBER
CREATION_DATE DATE
CREATED_BY NUMBER
LAST_UPDATE_LOGIN NUMBER
REQUEST_ID NUMBER
PROGRAM_APPLICATION_ID NUMBER
PROGRAM_ID NUMBER
PROGRAM_UPDATE_DATE DATE
ORGANIZATION_ID NUMBER
TRANSACTION_ID NUMBER
PROCESS_FLAG NUMBER
CATEGORY_SET_NAME VARCHAR2(30)
CATEGORY_NAME VARCHAR2(81)
ORGANIZATION_CODE VARCHAR2(3)
ITEM_NUMBER VARCHAR2(81)
TRANSACTION_TYPE VARCHAR2(10)
SET_PROCESS_ID NOT NULL NUMBER

The user needs to populate the following mandatory columns in item categories interface table:

A. Either inventory_item_id or item_number. When item and category are being imported together,then
user can only specify the item_number, since item id will be generated by
the import process.
B. Either organization_id or organization_code or both.
C. The transaction_type column should be 'CREATE'. We do not support 'UPDATE' or 'DELETE' for item
category assignment.
D. Either category_set_id or category_set_name or both.
E. Either category_id or category_name or both.
F. Process_flag column as 1.
G. Populate the set_process_id column. The item and category interface records should have the same
set_process_id, if you are importing item and category assignment together.

For better performance populate organization_id instead of organization_code, category_set_id instead of

category_set_name, category_id instead of category name. For already existing items, populate
inventory_item_id instead of item number.

3. After populating the item and category interface tables, launch the Item Import process from the
applications. In the item import parameters form, for the parameter 'set process id', specify the
'set process id' value given in the mtl_item_categories_interface table. The parameter 'Create or Update'
can have have any value. Through the import process, we can only create item category assignment(s).
Updation or Deletion of item category assignment is not supported.

4. Once the concurrent process completes, check the MTL_INTERFACE_ERRORS table for any error(s)
during the item and category import. Correct those error conditions in the interface tables and run the item
import again. If the process_flag is 7, that means the item category interface
records were successfully imported.
6. Revisions
Note: Using the ITEM_NUMBER column in the MTL_SYSTEM_ITEMS_INTERFACE table is required if
you are populating revision data into the MTL_ITEM_REVISIONS_INTERFACE table. The value of the
ITEM_NUMBER must equal the concatenated segments(n) of the item being imported, plus the segment
separator. If you are not importing revision history you can populate either ITEM_NUMBER or the
SEGMENT(n) column(s) or both.

For historical item revision data, do NOT populate the REVISION column in the
MTL_SYSTEM_ITEMS_INTERFACE table. This column is used only if the current revision of the item is
being imported. Populate these columns in the mtl_item_revisions_interface table:

PROCESS_FLAG = 1
TRANSACTION_TYPE = 'CREATE'
SET_PROCESS_ID = 1
ORGANIZATION_ID = Master Org ID.
REVISION
EFFECTIVITY_DATE
IMPLEMENTATION_DATE
ITEM_NUMBER = (Must match the item_number in MTL_SYSTEM_ITEMS_INTERFACE
table.)

Each row in the mtl_item_revisions_interface table must have the REVISION and EFFECTIVITY_DATE in
alphabetical (ASCII sort) and chronological order. The revision format must match the starting revision in
the Organization Parameters. For example, if the starting revision is '00A' then the REVISION column in
mtl_item_revisions_interface must match this format (00A,00B, etc.). The starting revision is sometimes
referred to as the default revision.
Under Inventory responsibility navigate to: Setup/Organizations/Parameters to verify the Starting Revision
in the "Revision, Lot, Serial" alternate region.

An Example of Revision History Import:

Org. Parameters Starting Revision = 00A
Organization_id = 204 (master org)
The current revision of the item being loaded is '00C' and there is historical data for revisions '00A' and
'00B'. Insert one record into the mtl_system_items_interface table for the new item:

insert into MTL_SYSTEM_ITEMS_INTERFACE

(process_flag,
transaction_type,
item_number,
description,
organization_id,
set_process_id)
VALUES (1,
'CREATE',
'Rev_hist_test', ----item_number
'IOI Revision Part', ----description
204,
1);
commit;
Insert 3 records into MTL_ITEM_REVISIONS_INTERFACE, one for each revision from
'00A' through '00C'. The REVISION and EFFECTIVITY_DATE columns must be in
alphabetical (ASCII sort) and chronological order:

insert into MTL_ITEM_REVISIONS_INTERFACE

(process_flag,
transaction_type,
set_process_id,
item_number,
organization_id,
revision,
effectivity_date,
implementation_date)
VALUES (1,
'CREATE',
1,
'Rev_hist_test',
204,
'00A', ---revision
sysdate-7, ---effectivity_date
sysdate-7
);
insert into MTL_ITEM_REVISIONS_INTERFACE
(process_flag,
transaction_type,
set_process_id,
item_number,
organization_id,
revision,
effectivity_date,
implementation_date)
VALUES (1,
'CREATE',
1,
'Rev_hist_test',
204,
'00B', ---revision
sysdate-6, ---effectivity_date
sysdate-6
);
insert into MTL_ITEM_REVISIONS_INTERFACE
(process_flag,
transaction_type,
set_process_id,
item_number,
organization_id,
revision,
effectivity_date,
implementation_date)
VALUES (1,
'CREATE',
1,
'Rev_hist_test',
204,
'00C', ---revision
sysdate-5, ---effectivity_date
sysdate-5
);
commit;

Run the IOI process. Navigate --> Inventory: Items: Import Items. There are 6 parameters to enter to
begin the process:
1. Specify one or all organizations.
2. Validate items, yes or no.
3. Process items, yes or no.
4. Delete processed rows, yes or no.
5. Process set (null for all)
6. Create or update items (1 for create, 2 for update)

Note: If you are importing Master and Child records, insert them into the
MTL_SYSTEM_ITEMS_INTERFACE and MTL_ITEM_REVISIONS_INTERFACE tables, and run them at
the same time by setting the 'All Organizations' parameter to 'Yes'. If you do not do this, then the Child
revision records will not be imported. What happens is, after the Master records are imported, the IOI
process sets the process_flag = 3 for the remaining records in the
mtl_item_revisions_interface table. There is a bug/patch for this issue: 1216978, available in the next
minipack.

7. Error Checking
When importing multiple revisions, if one record for an item fails validation, all revisions for that item fail.
Resolve failed rows by checking the mtl_interface_errors table.

select table_name, column_name, error_message, message_name

from MTL_INTERFACE_ERRORS;

Master/org## errors - These show in the column_name instead of the error_message. They indicate
master and child item attributes do not match.

The following PL/SQL packages define the columns in MTL_SYSTEM_ITEMS_INTERFACE for the
master/org# error. These packages are located in $INV_TOP/admin/sql.

INVPVM1B.pls: 'master/org1a'
INVPVM1B.pls: 'master/org2'
'master/org3'
INVPVM2B.pls: 'master/org4'
'master/org5'
'master/org6'
INVPVM3B.pls: 'master/org7a'
'master/org7b'
'master/org7c'
master/org1a: SUMMARY_FLAG thru ATTRIBUTE1
master/org2: ATTRIBUTE2 thru ITEM_CATALOG_GROUP_ID
master/org3: CATALOG_STATUS_FLAG thru AUTO_LOT_ALPHA_PREFIX
master/org4: START_AUTO_LOT_NUMBER thru ACCEPTABLE_RATE_DECREASE
master/org5: CUMULATIVE_TOTAL_LEAD_TIME thru CARRYING_COST
master/org6: POSTPROCESSING_LEAD_TIME thru ATO_FORECAST_CONTROL
master/org7a, 7b, & 7c: ENGINEERING_DATE thru VEHICLE_ITEM_FLAG
(overlaps with master/org6. Check PL/SQL package for exact attributes.)

8. Template Use
Item attributes populated in MTL_SYSTEM_ITEMS_INTERFACE take precedence (hold their value) even
if a template is also specified in MSII. However, a status controlled attribute, meaning one that can derive
its value from the 'item status' that is being assigned to the item, such as purchasing_enabled_flag, may
in turn override the value populated in MSII.

To use purchasing_enabled_flag as an example, if you specified purchasing_enabled_flag as 'N' in MSII,

and as 'Y' in the template, but if in the template you are applying there is an 'item status' such that it
makes purchasing_enabled_flag be 'Y', then that value, 'Y', prevails.

So, first check the value of 'Item status' attribute in the template applied. Then go to /setup/items/status
codes form, and query on this code, to see the value of purchasing_enabled_flag. If it is 'Y', then that is
the reason the value after import is 'Y'.

adrelink force=y ranlib=y "fnd aiap"

select OWNER, OBJECT_TYPE, OBJECT_NAME

from DBA_OBJECTS
where STATUS = 'INVALID';

References
NOTE:103869.1 - Item Attribute vs Template Attributes Using IOI
NOTE:106812.1 - Instructions for Running Item Open Import (IOI) Including Historical Revision Data
NOTE:109628.1 - FAQ for Item Import
NOTE:268968.1 - Understanding Item Import and Debugging Problems with Item Import
NOTE:458544.1 - Inventory Item Open Interface ITAR Template
NOTE:52746.1 - A Guideline to IOI Error Messages and Solutions

Item Attribute vs Template Attributes Using IOI [ID 103869.1]

Modified 21-APR-2009 Type PROBLEM Status PUBLISHED
Problem Description
-------------------

You are importing items into Inventory via the Item Open Interface(IOI).
 You manually enter various item attributes into the IOI and you also
specify
a template to be used to load attributes into the IOI.

Which attribute will an item inherit if the manually entered attribute

and the template attribute are different?

Solution Description
--------------------

Item attributes entered in the IOI table (MTL_SYSTEM_ITEMS_INTERFACE)

take precedence (hold their value) even if a template is specified in the
IOI table.

Explanation
-----------

Per Bug 1251197, user entered item attributes take precedence over template
values unless it can derive its value from the 'item status'(status
controlled attribute)
that is being assigned to the item.