Supplier Import R12

In R12 we have new concept of TCA(Trading Community Architecture),TCA is a centralized place where all the party details including Customer and Supplier details get saved.

TCA has some important tables like HZ_PARTIES and HZ_PARTY_SITES.
Steps to create Supplier in R12 payables:

  1. Insert data in the Supplier interface table AP_SUPPLIERS_INT table with mandatory columns like
    1. vendor_interface_id (AP_SUPPLIERS_INT_S.nextval)
    2. status as ‘NEW’
    3. Vendor_Name
    4. Segment1: This columns stores the value of supplier number and which you can get from NEXT_AUTO_SUPPLIER_NUM.AP_PRODUCT_SETUP
    5. term_id and other columns
  2. Insert data in supplier site interface table i.e AP_SUPPLIER_SITES_INT table with mandatory columns like :
    1. vendor_site_interface_id (AP_SUPPLIER_SITES_INT_S.nextval)
    2. vendor_interface_id (AP_SUPPLIERS_INT_S.currval)
    3. Vendor_id: Use the vendor_id created in Step 2 (Supplier Import Program).
    4. Status as ‘NEW’
    5. Org_id
    6. Vendor_Site_Code
    7. pay_site_flag as ‘Y’ else will throw error in the Import Program (The site is not a Pay Site error)
  3. Its not a mandatory step:Insert records in the supplier contact table i.e. AP_SUP_SITE_CONTACT_INT with mandatory columns like
    1. vendor_interface_id (AP_SUPPLIERS_INT_S.currval)
    2. vendor_site_interface_id (AP_SUPPLIER_SITES_INT_S.currval)
    3. vendor_contact_interface_id (AP_SUP_SITE_CONTACT_INT_S.nextval)
    4. LAST_NAME: Else will throw error in the import program.
    5. vendor_id
  4. Its not a mandatory step:Information for Supplier Bank table interface  IBY_TEMP_EXT_BANK_ACCTS with mandatory columns like
  1. TEMP_EXT_BANK_ACCT_ID
  2. BANK_ID
  3. BRANCH_ID
  4. BANK_ACCOUNT_NUM
  5. CALLING_APP_UNIQUE_REF1
  1. Run the standard Import program “Supplier Open Interface Import” to import data from AP_SUPPLIER_INT table to TCA and supplier standard tables.Using segment1 column we can check data in PO_VENDORS which is a view of AP_SUPPLIERS and HZ_PARTIES .This will create a unique vendor_id.In case of error,we can check import failure reason in either import program output file or in the AP_SUPPLIER_INT_REJECTIONS table.
  2. Run the Standard supplier site import program i.e. “Supplier Sites Open Interface Import”.This will create supplier site for above vendor_id.
  3. Then run supplier contact import program “Supplier Site Contacts Open Interface Import”.
Note: We can also use request set “Supplier Open Interface Request Set” in place of running each import program individually. 

**In case any of the import program fails,we can check import failure reason in either import program output file or in the AP_SUPPLIER_INT_REJECTIONS table.In case output file is not giving any error reason that means latest patch for the import program has not been applied.Please check with you DBA and ask him to apply the latest patch.

Vendor conversion program will load the Supplier Master, Sites and Contacts data from data files to the staging tables, validate the data and then load the data into Interface tables, finally Validated data will import into Oracle Supplier Standard Tables by using Oracle Standard Supplier Import Programs.
Pre-requisites setup’s are: Payment terms, Pay Groups, CCID, Supplier classifications, Bank Accounts , Employees (if employees have to set up as vendors).
The Interface Tables are:
  • AP_SUPPLIERS_INT
  • AP_SUPPLIER_SITES_INT
  • AP_SUP_SITE_CONTACT_INT
AP_SUPPLIERS_INT:
This is the open interface table for AP Suppliers. It holds Supplier information which is loaded by the user for import. The columns in the table map to corresponding columns in the PO_VENDORS table. The Oracle Payables application uses this information to create a new Supplier record when the Supplier Open Interface Import program is submitted. Each row in the table will be identified by a unique identifier, the VENDOR_INTERFACE_ID.
Mandatory Columns:
  • VENDOR_INTERFACE_ID (ap_suppliers_int_s.NEXTVAL)- Supplier interface record unique identifier
  • VENDOR_NAME – Supplier name
Other important columns:
  • SEGMENT1 – Supplier Number
  • VENDOR_TYPE_LOOKUP_CODE – Supplier type
  • SHIP_TO_LOCATION_CODE – Default ship-to-location name
  • BILL_TO_LOCATION_CODE – Default bill-to-location name
  • TERMS_NAME – Payment terms name
  • TAX_VERIFICATION_DATE – Tax verification date(1099)
  • VAT_REGISTRATION_NUM – Tax registration number
  • ATTRIBUTE1 -15 – Descriptive Flexfield Segments
  • PAY_GROUP_LOOKUP_CODE – Payment group type
  • INVOICE_CURRENCY_CODE – Default currency unique identifier
  • PAYMENT_CURRENCY_CODE – Default payment currency unique identifier
  • NUM_1099 – Tax identification number (1099)
  • VAT_CODE – Default invoice tax code
  • HOLD_FLAG – Indicates whether or not the supplier is on purchasing hold
  • SUMMARY_FLAG – Key flexfield summary flag
  • ENABLED_FLAG – Key flexfield enable flag
  • EMPLOYEE_ID – Employee unique identifier if supplier is an employee
AP_SUPPLIER_SITES_INT:
This is the open interface table for AP Supplier Sites. It holds Supplier Site information which is loaded by the user for import. The columns in the table map to corresponding columns in PO_VENDOR_SITES_ALL table. The Oracle Payables application uses this information to create a new Supplier Site record when the Supplier Sites Open Interface Import program is submitted. Each row in the table will be joined to the appropriate Supplier using the VENDOR_ID column.
Mandatory Columns:
  • VENDOR_SITE_INTERFACE_ID (ap_supplier_sites_int_s.NEXTVAL) – Supplier Site interface record unique identifier
  • VENDOR_SITE_CODE – Supplier Site name
Other important columns:
  • ADDRESS_LINE1 – First line of supplier address
  • ADDRESS_LINE2 – Second line of supplier address
  • ADDRESS_LINE3 – Third line of supplier address
  • CITY – City name
  • STATE – State name or abbreviation
  • ZIP – Postal code
  • COUNTRY – Country name
  • PHONE – Phone number
  • FAX – Supplier site facsimile number
  • SHIP_TO_LOCATION_CODE – Default ship-to-location name
  • BILL_TO_LOCATION_CODE – Default bill-to-location name
  • PAYMENT_METHOD_LOOKUP_CODE – Default payment method type
  • VAT_CODE – Invoice default tax code
  • PAY_GROUP_LOOKUP_CODE – Payment group type
  • TERMS_NAME – Payment terms name
  • INVOICE_CURRENCY_CODE – Default currency unique identifier
  • PAYMENT_CURRENCY_CODE – Default payment currency unique identifier
  • EMAIL_ADDRESS – E-mail address of the supplier contact
  • PURCHASING_SITE_FLAG – Indicates whether purchasing is allowed from this site
  • AUTO_TAX_CALC_FLAG – Level of automatic tax calculation for supplier
  • HOLD_ALL_PAYMENTS_FLAG – Indicates if Oracle Payables should place payments for this supplier on hold
AP_SUP_SITE_CONTACT_INT:
This is the open interface table for AP Supplier Site Contacts. It holds Supplier contact data. The columns in the table map to corresponding columns in PO_VENDOR_CONTACTS table. The Oracle Payables application uses this information to create a new Supplier Contact record when the Supplier Sites Open Interface Import program is submitted. Each row in the table will be joined to the appropriate Supplier Site using the VENDOR_SITE_CODE  and ORG_ID.
Mandatory Columns:
  • VENDOR_INTERFACE_ID – Supplier interface record unique identifier
  • VENDOR_CONTACT_INTERFACE_ID (AP_SUP_SITE_CONTACT_INT_S.NEXTVAL) – Vendor Contact Interface Identifier
  • VENDOR_SITE_CODE – Supplier Site name
Other important columns:
  • FIRST_NAME – Contact First name
  • LAST_NAME – Contact last name
  • AREA_CODE – Area code of contact phone number
  • PHONE – Contact phone number
  • FIRST_NAME_ALT – Alternate Supplier contact first name
  • LAST_NAME_ALT – Alternate Supplier contact last name
  • EMAIL_ADDRESS – Email address for the Supplier Site contact
  • FAX – Facsimile number for the Supplier Site contact
  • VENDOR_ID – Supplier unique identifier
Validations:
  • Vendor Number (Check for duplicate records in ap_suppliers table)
  • Vendor Name (Check for duplicate records in staging as well as in ap_suppliers table)
  • Terms Name (Check for proper record in ap_terms_tl table)
  • Pay Group (Check for proper record in fnd_lookup_values_vl table where lookup_type = ‘PAY GROUP’)
  • Employee Id (Check for proper employee record in per_all_people_f table)
  • Vendor Type (Check for proper record in po_lookup_codes table where lookup_type = ‘VENDOR TYPE’)
  • Vendor Site Code (Check for duplicate records in ap_supplier_sites_all table)
  • Country Code ( Check for proper country code in fnd_territories_vl table)
  • Payment Method (Check for proper payment method in iby_payment_methods_vl table)
Interface programs:
  1. Supplier Open Interface Import
  2. Supplier Sites Open Interface Import
  3. Supplier Site Contacts Open Interface Import
The data inserted via these interfaces are automatically populated into TCA tables.
Note: AP_SUPPLIER_INT_REJECTIONS table contains suppliers, sites, contacts rejections information.

4 thoughts on “Supplier Import R12

  1. Hi Buddy thanks for the detailed information, but my concern is can i use the Same Program for modification of Suppliers as well. like inserting the records in INTERFACE tables with status as “UPDATE”/”MODIFY” in-place of “NEW”.

  2. How to run :
    1. Supplier Open Interface Import
    2. Supplier Sites Open Interface Import
    3. Supplier Site Contacts Open Interface Import
    standard programs via procedure code.

Leave a comment