Using the Open Interface Program

This chapter covers the following topics:

• Overview of the Open Interface Program
• Running the Open Interface Program
• Guidelines for Loading Open Interface Tables
• Considerations for Populating Open Interface Tables
• Example of Creating Instances in Oracle Install Base Using the Open Interface Tables

Overview of the Open Interface Program

Features

Oracle Install Base provides the following Open Interface features:

• Initial mass load

  This imports significant volumes of data into Oracle Install Base application tables. The data may be from multiple sources including external legacy systems.

  Key integration with Oracle E-Business Suite applications includes optional calls to Oracle Service Contracts for warranty creation and creation of counters during item instantiation using Open Interface functionality.

• Incremental load

  This synchronizes Oracle Install Base with subsystems by importing item instances from different feeder systems on a frequent, on-going basis. This application ensures accuracy, consistency, and up-to-date information between multiple systems.

• Change functionality

  This provides a mechanism to automate the process of adding as well as updating changes to item instance attributes including:

  • Add new party relationships to existing item instances

  • Add new physical attributes to the item instances

  • Add new contact information

  • Add new configuration elements

  • Change the party relationships of existing instances

  • Change contact information

  • Change configuration (relationships between item instances)

  • Remove and expire item instances

  • Remove and expire configuration, cascading

  • Remove and expire party relationships

  • Remove and expire contact information

• Data validation

  Imported data is validated to ensure data integrity with Oracle applications. You can set up and define rules to be applied for validation and manipulation of item instance data during the Open Interface Mass Load process.

Open Interface includes user interfaces to:

• Submit the Open Interface Import process

• View and update error transactions

  Note: Oracle Install Base Open Interface provides a user interface to view, update, and correct error transactions in the open interface tables. Using this user interface, you cannot view other transactions, such as initial load transactions and transactions without errors.

Oracle Install Base Open Interface functionality is restricted to customer items. It does not support internal items and instance assets.

Process

The process overview for a user of the Oracle Install Base Open Interface application is as follows:

1. Load data into a set of interface tables provided by Oracle Install Base.

2. Run a mass load concurrent program that reads, validates, and posts the data into Oracle Install Base tables. The program posts records that fail validation to Open Interface error tables.

3. Review and edit failed transactions.

4. Resubmit edited transactions for processing and loading into Oracle Install Base.

Running the Open Interface Program

Use this procedure to run the Open Interface programs:

Steps

1. Load the Open Interface tables, using SQL Loader or a custom program.

2. Using the Forms mode and the Oracle Install Base Admin responsibility, navigate to Others > Requests.

   The Install Base Requests window appears.

3. If you need general information about submitting requests, then click Help.

4. From the Name LOV, select either Install Base Open Interface or Install Base Open Interface-Parallel Concurrent Workers.

   

   Oracle Install Base has two programs available to process open interface records, Install Base Open Interface and Install Base Open Interface-Parallel Concurrent Workers.

   Install Base Open Interface submits the process to post records from the interface tables to the core Oracle Install Base tables.

   Install Base Open Interface-Parallel Concurrent Workers submits the interface program with the Parallel Workers option, which indicates the number of parallel processes to be run. Interface transactions are evenly divided by this number, and the original concurrent request is submitted the number of times indicated by the parameter. The process enhances speed and performance of the mass load process and is used for high volume loads. The parallel workers feature is used only for creating Oracle Install Base item instance, party, and account records. When loading the Open Interface tables, the Parallel Worker ID column must be populated with a value of -1. The transaction identifier column in table CSI_INSTANCE_INTERFACE must be null.

5. Click in the Parameters field.

   The Parameters window appears.

6. Enter the required parameters.

   Available Parameters:

   Source System Name: (Required). Selects from names loaded to Interface tables.

   Batch Name: (Optional). Provides ability to choose specific or all batches loaded to Open Interface tables.

   Resolve Oracle IDs: Yes = Derive IDs by matching item descriptions in interface transactions with Oracle Inventory tables.

   Purge Processed Records: Purges processed records. Status = P (Processed).

7. Click OK to return to the Install Base Requests window.

8. Complete the information, and click Submit.

9. After the program has run, navigate to Open Interface Error Details.

   The Find Interface Errors window appears.

   

10. Complete the desired entries, and click Find.

    The Open Interface Error Details window appears.

11. Review and edit error transaction details. Select the Process check box for transactions that you want to reprocess.

12. Save your changes.

13. Go to step 2 to resubmit the Install Base Open Interface program to load the records into Oracle Install Base tables.

Guidelines for Loading Open Interface Tables

Here are general guidelines for loading Open Interface tables:

1. Set up the source system details before using the Open Interface functionality.

2. Use the appropriate value for Transaction_Identifier. The value must be unique for the same source_system_name.

3. Set replace_flag to Y only if the complete structure, or image, of the item instance is being processed.

4. Any type of transaction requires at least one row in the CSI_INSTANCE_INTERFACE table.

5. Child entity updates, such as instance_party update and ip_account_update, must have a corresponding row with the same inst_interface_id in the csi_instance_interface table.

6. Get NEXTVAL from the respective instances for populating primary keys of the interface tables, as in the following examples:

   • INST_INTERFACE_ID from csi_instance_interface_s.nextval

   • IP_INTERFACE_ID from csi_i_party_interface_s.nextval

   • IEAV_INTERFACE_ID from csi_iea_value_interface_s.nextval

   • REL_INTERFACE_ID from csi_ii_relation_interface_s.nextval

   • IA_INTERFACE_ID from csi_asset_interface_s.nextval

7. Make sure that all the referenced entities are populated with their respective IDs before running the Open Interface program. For example, inventory_item exists in mtl_system_items, party exists in the respective party tables, and order line exists in the order entry tables.

8. When including pricing attributes on an instance, make sure that the Pricing Context Flexfield (QP_ATTR_DEFNS_PRICING) has the Context Field Code Value defined and the related segments specified.

9. The Open Interface program resolves the IDs from different tables from the descriptive values provided in the interface tables and also validates the existence of all the referenced IDs.

10. Transaction Identifier along with Source_System_Name is used to identify the set of instances and instance relationships. This set is committed as a single database transaction.

The following table shows the column names and table views used for validations.

Table Columns and Views Used for Validations

Reference Number	Column Name	Table and View Used for Validation
-	CSI_INSTANCE_INTERFACE	-
1	Inventory_item_id	Mtl_system_items_kfv
2	Inv_vld_organization_id	Hr_all_organization_units
3	Unit_of_measure_code	Mtl_all_primary_uoms_vv
4	Serial_number	Mtl_serial_numbers
5	Lot_number	Mtl_lot_numbers
6	Project_id	Pa_projects_all
7	Task_id	Pa_tasks
8	Inv_organization_id	Mtl_organizations
9	Wip_job_id	Wip_entities
10	Po_order_line_id	Po_headers_all, po_lines_all
11	Oe_order_line_id	Oe_order_headers_all, oe_order_lines_all
12	Intransit_order_line_id	Oe_order_headers_all, oe_order_lines_all
13	Oe_rma_line_id	Oe_order_headers_all, oe_order_lines_all
14	Operating_unit	Hr_operating_units
15	Instance_condition_id	Mtl_material_statuses
16	Instance_status_id	Csi_instance_statuses
-	CSI_I_PARTY_INTERFACE	-
17	Party_id	Based on the party_source_table: 'HZ_PARTIES' - hz_parties 'VENDORS' - po_vendors 'EMPLOYEE' - per_all_people_f 'TEAM' - jtf_rs_teams_vl 'GROUP' - jtf_rs_groups_vl
18	Party_account1_id	Hz_cust_accounts
19	Party_account2_id	Hz_cust_accounts
20	Party_account3_id	Hz_cust_accounts

The following table provides information about the setup of the source system.

Setup of the Source System

Reference Number	Parameter	Description
1	Source System ID	You can get the next value from the sequence CSI_INSTANCE_SOURCES_S.
2	Source System Name	Unique name of the source system from which the item instances are interfaced.
3	Source_lang	Source language of the descriptive data such as party name to be used to get IDs.

The following table describes the table columns that are specific to Open Interface.

Table Columns Specific to Open Interface

Reference Number	Column Name	Desciption
1	INST_INTERFACE_ID	This is the Primary key for the table. Interfaced rows are processed in the order of this key. You can get the next value from the sequence CSI_INSTANCE_INTERFACE_S.
2	IP_INTERFACE_ID	You can get the next value from the sequence CSI_I_PARTY_INTERFACE_S.
3	IEAV_INTERFACE_ID	You can get the next value from the sequence CSI_IEA_VALUE_INTERFACE_S.
4	REL_INTERFACE_ID	You can get the next value from the sequence CSI_INST_REL_INTERFACE_S.
5	IA_INTERFACE_ID	You can get the next value from the sequence CSI_ASSET_INTERFACE_S.
5	TRANSACTION_IDENTIFIER	There is a composite uniqueness on transaction_identifier and source_system_name. All the records corresponding to the same transaction_identifier are processed as a single database transaction. If you creating an top assembly, then you must stamp all the corresponding records in all the Oracle Install Base Open Interface tables with the same transaction_identifier.
6	PROCESS_STATUS	You must populate this column with 'R', used for READY. The processor picks only those records with 'R' value. The processor sets this values to 'P' if processed OK or 'E' if there is an ERROR while processing.
7	PARALLEL_WORKER_ID	For internal use only. When the parallel processing feature is used, this column gets populated by an internal program. When using the parallel worker feature, set this to (-1) for those records in the interface table that will use parallel workers.

Considerations for Populating Open Interface Tables

You must have a unique transaction identifier for every source system.

You must have a record in the CSI_INSTANCE_INTERFACE table for every instance that you process. You must reference the same inst_interface_id in the corresponding rows in the other child or relationship interface tables such as CSI_I_PARTY_INTERFACE, CSI_IEA_VALUE_INTERFACE, or CSI_II_RELATION_INTERFACE.

If you want to update a specific item instance, then you must provide the instance number in the interface table CSI_INSTANCE_INTERFACE.

When you want to create an instance-instance relationship for new instances, you must populate the CSI_INSTANCE_INTERFACE table with the instance details and reference the INST_INTERFACE_ID as SUBJECT_INTERFACE_ID or OBJECT_INTERFACE_ID in the CSI_II_RELATION_INTERFACE table.

When you want to create an instance-instance relationship for existing instances, you must populate corresponding rows in the CSI_INSTANCE_INTERFACE table with the instance number and then reference those INST_INTERFACE_IDs as SUBJECT_INTERFACE_ID or OBJECT_INTERFACE_ID in the CSI_II_RELATION_INTERFACE table appropriately.

Refer to the following table for descriptions of how to populate the interface tables under various scenarios.

Scenarios for Populating Interface Tables

Reference Number	Scenario	How to Populate
1	Create an item instance with one party	A row in the table CSI_INSTANCE_INTERFACE and a row in the table CSI_I_PARTY_INTERFACE referencing the INST_INTERFACE_ID of the parent table
2	Create an item instance with one party and an party account	A row in the table CSI_INSTANCE_INTERFACE and a row in the table CSI_I_PARTY_INTERFACE with Party details and Party Account details. Reference the INST_INTERFACE_ID of the parent table in the child table.
3	Create an item instance with one party and an extended attribute value	The extended attribute has to be set up prior to the interface process. You need to create a row in CSI_INSTANCE_INTERFACE. A row in the table CSI_I_PARTY_INTERFACE and a row in CS_IEA_VALUE_INTERFACE. All the child table rows to have referenced INST_INTERFACE_ID.
4	Change the owner	One row in CSI_INSTANCE_INTERFACE table with instance_number, new party details and INST_INTERFACE_ID in the table CSI_I_PARTY_INTERFACE.
5	Add Party Account	One row in CSI_INSTANCE_INTERFACE table with instance_number, details of to which party the account is added, new party account details in the table CSI_I_PARTY_INTERFACE.
6	Update party account details	One row in CSI_INSTANCE_INTERFACE table with instance_number, details of updated party account in the table CSI_I_PARTY_INTERFACE.
7	Remove a party account	One row in CSI_INSTANCE_INTERFACE table with instance_number, details of updated party account with an end date in the table CSI_I_PARTY_INTERFACE.
8	Add a pricing attribute	One row in the CSI_INSTANCE_INTERFACE with instance number and pricing attribute details in the same record.
9	Add an org assignment	One row in the CSI_INSTANCE_INTERFACE with instance number and organization assignment details in the same record.
10	Remove a pricing attribute	One row in the CSI_INSTANCE_INTERFACE with instance number and pricing attribute context and pricing attribute end date in the same record.
11	Update a pricing attribute	One row in the CSI_INSTANCE_INTERFACE with instance number and changed pricing attribute details in the same record.
12	Remove an organization assignment	One row in the CSI_INSTANCE_INTERFACE with instance number and organization assignment identifiers and org_assignment end date in the same record.
13	Add an extended attribute value	One row in the CSI_INSTANCE_INTERFACE with instance number and one row in CSI_IEA_VALUE_INTERFACE with details of new extended attribute value.
14	Remove an extended attribute value	One row in the CSI_INSTANCE_INTERFACE with instance number and one row in CSI_IEA_VALUE_INTERFACE identifier with an end date.
15	Create a UNIT consisting of two related instances with one instance party each.	Two rows in CSI_INSTANCE_INTERFACE. Two corresponding rows in CSI_I_PARTY_INTERFACE. One row in CSI_II_RELATION_INTERFACE, giving the corresponding INST_INTERFACE_IDs as SUBJECT_INTERFACE_ID and OBJECT_INTERFACE_ID.

Example of Creating Instances in Oracle Install Base Using the Open Interface Tables

The following is an example of creating two instances in Oracle Install Base using the Open Interface tables.

Each Customer Product instance will have its own owner party and owner account.

The steps also include the creation of an instance-to-instance relationship/configuration between the newly created Customer Products

The topics in this section are as follows:

• Initial Setup

• Load the Interface Tables

• Run the Install Base Open Interface Program

• Confirm Records Created Successfully

Initial Setup

Before using the open interface functionality, you must complete the mandatory source system details setup. This can be achieved by populating at least one record into the CSI_INTERFACE_SOURCES table.

The following is a sample script that can be used to populate a record into the CSI_INTERFACE_SOURCES table.

Declare
Begin
Insert into CSI_INTERFACE_SOURCES
(SOURCE_SYSTEM_ID
, SOURCE_SYSTEM_NAME
, SOURCE_DESCRIPTION
, SOURCE_LANG
, CREATED_BY, CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATE_DATE, LAST_UPDATE_LOGIN)
Values
(CSI_INTERFACE_SOURCES_S.nextval
, 'ENTERPRISE MANAGER'
, 'Enterprise Manager'
, 'US'
, FND_GLOBAL.USER_ID, Sysdate, FND_GLOBAL.USER_ID, Sysdate, FND_GLOBAL.USER_ID);
Commit;
Exception
When others then
Null;
End;
/

Note: Open interface functionality allows populating multiple records into CSI_INTERFACE_SOURCES table. However, each record must have a unique source system name.

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

Load the Interface Tables

The following is a sample script that can be used to populate the interface tables.

SET SERVEROUTPUT ON SIZE 1000000
DECLARE
Begin
Insert into CSI_INSTANCE_INTERFACE 
(INST_INTERFACE_ID 
,SOURCE_SYSTEM_NAME 
,PARALLEL_WORKER_ID 
,REPLACE_FLAG 
,TRANSACTION_IDENTIFIER 
,SOURCE_TRANSACTION_DATE 
,SOURCE_TRANSACTION_TYPE 
,INSTANCE_ID 
,INSTANCE_NUMBER 
,INSTANCE_DESCRIPTION 
,EXTERNAL_REFERENCE 
,PROCESS_STATUS 
,BATCH_NAME 
,ERROR_TEXT 
,INVENTORY_ITEM_ID 
,INV_CONCATENATED_SEGMENTS 
,INVENTORY_REVISION 
,INV_VLD_ORGANIZATION_ID 
,INV_VLD_ORGANIZATION_NAME 
,SERIAL_NUMBER 
,MFG_SERIAL_NUMBER_FLAG 
,LOT_NUMBER 
,QUANTITY 
,UNIT_OF_MEASURE_CODE 
,UNIT_OF_MEASURE 
,ACCOUNTING_CLASS_CODE 
,INSTANCE_CONDITION_ID 
,INSTANCE_CONDITION 
,INSTANCE_STATUS_ID 
,INSTANCE_STATUS 
,CUSTOMER_VIEW_FLAG 
,MERCHANT_VIEW_FLAG 
,SELLABLE_FLAG 
,SYSTEM_ID 
,SYSTEM_NUMBER 
,INSTANCE_START_DATE 
,INSTANCE_END_DATE 
,INSTANCE_TYPE_CODE 
,LOCATION_TYPE_CODE 
,LOCATION_ID 
,INV_ORGANIZATION_ID 
,INV_ORGANIZATION_CODE 
,INV_ORGANIZATION_NAME 
,INV_SUBINVENTORY_NAME 
,INV_LOCATOR_NUMBER 
,INV_LOCATOR_ID 
,PROJECT_ID 
,PROJECT_NUMBER 
,TASK_ID 
,TASK_NUMBER 
,IN_TRANSIT_ORDER_LINE_ID 
,IN_TRANSIT_ORDER_LINE_NUMBER 
,WIP_JOB_ID 
,WIP_JOB_NAME 
,PO_ORDER_LINE_ID 
,PO_ORDER_LINE_NUMBER 
,OE_ORDER_LINE_ID 
,OE_ORDER_LINE_NUMBER 
,OE_RMA_LINE_ID 
,OE_RMA_LINE_NUMBER 
,PO_PO_LINE_ID 
,PO_PO_LINE_NUMBER 
,OE_PO_NUMBER 
,OE_AGREEMENT_ID 
,INSTALL_LOCATION_TYPE_CODE 
,INSTALL_LOCATION_ID 
,INSTALL_DATE 
,RETURN_BY_DATE 
,ACTUAL_RETURN_DATE 
,CONFIG_INST_HDR_ID 
,CONFIG_INST_REV_NUM 
,CONFIG_INST_ITEM_ID 
,CONFIG_VALID_STATUS 
,INSTANCE_OU_ID 
,OPERATING_UNIT_NAME 
,OPERATING_UNIT 
,OU_RELATION_TYPE 
,OU_START_DATE 
,OU_END_DATE
,CREATED_BY ,CREATION_DATE ,LAST_UPDATED_BY ,LAST_UPDATE_DATE)
values
(CSI_INSTANCE_INTERFACE_S.NEXTVAL
,'ENTERPRISE MANAGER',null, null
,'100'
,sysdate,null,null,null
,'Instance creation',null
,'R',null,null,null 
, 'AS72111' 
,'A' ,null
,'Vision Operations' ,null
,'N',null
,1 ,null 
,'Each',null,null,null,null
,'CREATED'
,'Y'
,'Y' 
,'Y' ,null ,null ,null ,null ,null 
,'HZ_PARTY_SITES' 
,1020 ,null ,null ,null ,null ,null ,null ,null ,null ,null ,null ,null 
,null ,null ,null ,null, null ,null ,null ,null ,null ,null ,null ,null 
,null ,null ,null ,null ,null ,null ,null ,null ,null ,null ,null ,null 
,null ,null ,null, null
,FND_GLOBAL.USER_ID ,sysdate ,FND_GLOBAL.USER_ID ,sysdate); 

Insert into CSI_I_PARTY_INTERFACE
(IP_INTERFACE_ID 
,INST_INTERFACE_ID 
,PARALLEL_WORKER_ID 
,ERROR_TEXT 
,PARTY_ID 
,PARTY_NUMBER 
,INSTANCE_PARTY_ID 
,PARTY_NAME 
,PARTY_SOURCE_TABLE 
,PARTY_RELATIONSHIP_TYPE_CODE 
,PARTY_START_DATE 
,PARTY_END_DATE 
,CONTACT_FLAG 
,CONTACT_IP_ID 
,CONTACT_PARTY_NUMBER 
,CONTACT_PARTY_NAME 
,CONTACT_PARTY_ID 
,CONTACT_PARTY_REL_TYPE 
,IP_ACCOUNT1_ID 
,PARTY_ACCOUNT1_NUMBER 
,PARTY_ACCOUNT1_ID 
,ACCT1_RELATIONSHIP_TYPE_CODE 
,PARTY_ACCT1_START_DATE 
,PARTY_ACCT1_END_DATE 
,BILL_TO_ADDRESS1 
,SHIP_TO_ADDRESS1 
,IP_ACCOUNT2_ID 
,PARTY_ACCOUNT2_NUMBER 
,PARTY_ACCOUNT2_ID 
,ACCT2_RELATIONSHIP_TYPE_CODE 
,PARTY_ACCT2_START_DATE 
,PARTY_ACCT2_END_DATE 
,BILL_TO_ADDRESS2 
,SHIP_TO_ADDRESS2 
,IP_ACCOUNT3_ID 
,PARTY_ACCOUNT3_NUMBER 
,PARTY_ACCOUNT3_ID 
,ACCT3_RELATIONSHIP_TYPE_CODE 
,PARTY_ACCT3_START_DATE 
,PARTY_ACCT3_END_DATE 
,BILL_TO_ADDRESS3 
,SHIP_TO_ADDRESS3 
,CREATED_BY ,CREATION_DATE ,LAST_UPDATED_BY ,LAST_UPDATE_DATE)
values
(CSI_I_PARTY_INTERFACE_S.NEXTVAL
,CSI_INSTANCE_INTERFACE_S.currval,null,null,null ,null ,null 
,'Imaging Innovations, Inc.'
,'HZ_PARTIES'
,'OWNER',null ,null 
,'N' ,null,null ,null ,null ,null ,null 
,'1002' ,null 
,'OWNER' ,null ,null ,null ,null ,null ,null ,null ,null ,null ,null
,null ,null ,null ,null ,null ,null ,null ,null ,null ,null 
,FND_GLOBAL.USER_ID ,sysdate ,FND_GLOBAL.USER_ID ,sysdate);

Insert into CSI_INSTANCE_INTERFACE
(INST_INTERFACE_ID 
,SOURCE_SYSTEM_NAME 
,PARALLEL_WORKER_ID 
,REPLACE_FLAG 
,TRANSACTION_IDENTIFIER 
,SOURCE_TRANSACTION_DATE 
,SOURCE_TRANSACTION_TYPE 
,INSTANCE_ID 
,INSTANCE_NUMBER 
,INSTANCE_DESCRIPTION 
,EXTERNAL_REFERENCE 
,PROCESS_STATUS 
,BATCH_NAME 
,ERROR_TEXT 
,INVENTORY_ITEM_ID 
,INV_CONCATENATED_SEGMENTS 
,INVENTORY_REVISION 
,INV_VLD_ORGANIZATION_ID 
,INV_VLD_ORGANIZATION_NAME 
,SERIAL_NUMBER 
,MFG_SERIAL_NUMBER_FLAG 
,LOT_NUMBER 
,QUANTITY 
,UNIT_OF_MEASURE_CODE 
,UNIT_OF_MEASURE 
,ACCOUNTING_CLASS_CODE 
,INSTANCE_CONDITION_ID 
,INSTANCE_CONDITION 
,INSTANCE_STATUS_ID 
,INSTANCE_STATUS 
,CUSTOMER_VIEW_FLAG 
,MERCHANT_VIEW_FLAG 
,SELLABLE_FLAG 
,SYSTEM_ID 
,SYSTEM_NUMBER 
,INSTANCE_START_DATE 
,INSTANCE_END_DATE 
,INSTANCE_TYPE_CODE 
,LOCATION_TYPE_CODE 
,LOCATION_ID 
,INV_ORGANIZATION_ID 
,INV_ORGANIZATION_CODE 
,INV_ORGANIZATION_NAME 
,INV_SUBINVENTORY_NAME 
,INV_LOCATOR_NUMBER 
,INV_LOCATOR_ID 
,PROJECT_ID 
,PROJECT_NUMBER 
,TASK_ID 
,TASK_NUMBER 
,IN_TRANSIT_ORDER_LINE_ID 
,IN_TRANSIT_ORDER_LINE_NUMBER 
,WIP_JOB_ID 
,WIP_JOB_NAME 
,PO_ORDER_LINE_ID 
,PO_ORDER_LINE_NUMBER 
,OE_ORDER_LINE_ID 
,OE_ORDER_LINE_NUMBER 
,OE_RMA_LINE_ID 
,OE_RMA_LINE_NUMBER 
,PO_PO_LINE_ID 
,PO_PO_LINE_NUMBER 
,OE_PO_NUMBER 
,OE_AGREEMENT_ID 
,INSTALL_LOCATION_TYPE_CODE 
,INSTALL_LOCATION_ID 
,INSTALL_DATE 
,RETURN_BY_DATE 
,ACTUAL_RETURN_DATE 
,CONFIG_INST_HDR_ID 
,CONFIG_INST_REV_NUM 
,CONFIG_INST_ITEM_ID 
,CONFIG_VALID_STATUS 
,INSTANCE_OU_ID 
,OPERATING_UNIT_NAME 
,OPERATING_UNIT 
,OU_RELATION_TYPE 
,OU_START_DATE 
,OU_END_DATE
,CREATED_BY ,CREATION_DATE ,LAST_UPDATED_BY ,LAST_UPDATE_DATE)
values
(CSI_INSTANCE_INTERFACE_S.NEXTVAL
,'ENTERPRISE MANAGER',null,null
,'100'
,sysdate,null,null ,null
,'Instance creation',null
,'R',null,null,null 
,'AS72111' 
,'A' ,null
,'Vision Operations',null
,'N',null
,1 ,null 
,'Each',null,null,null ,null
,'CREATED'
,'Y'
,'Y' 
,'Y' ,null ,null ,null ,null ,null 
,'HZ_PARTY_SITES' 
,1020 ,null ,null ,null ,null ,null ,null ,null ,null ,null ,null ,null 
,null ,null ,null ,null ,null, null ,null ,null ,null ,null ,null ,null 
,null ,null ,null ,null ,null ,null ,null ,null ,null ,null ,null ,null 
,null ,null ,null ,null
,FND_GLOBAL.USER_ID ,sysdate ,FND_GLOBAL.USER_ID ,sysdate); 

Insert into CSI_I_PARTY_INTERFACE
(IP_INTERFACE_ID 
,INST_INTERFACE_ID 
,PARALLEL_WORKER_ID 
,ERROR_TEXT 
,PARTY_ID 
,PARTY_NUMBER 
,INSTANCE_PARTY_ID 
,PARTY_NAME 
,PARTY_SOURCE_TABLE 
,PARTY_RELATIONSHIP_TYPE_CODE 
,PARTY_START_DATE 
,PARTY_END_DATE 
,CONTACT_FLAG 
,CONTACT_IP_ID 
,CONTACT_PARTY_NUMBER 
,CONTACT_PARTY_NAME 
,CONTACT_PARTY_ID 
,CONTACT_PARTY_REL_TYPE 
,IP_ACCOUNT1_ID 
,PARTY_ACCOUNT1_NUMBER 
,PARTY_ACCOUNT1_ID 
,ACCT1_RELATIONSHIP_TYPE_CODE 
,PARTY_ACCT1_START_DATE 
,PARTY_ACCT1_END_DATE 
,BILL_TO_ADDRESS1 
,SHIP_TO_ADDRESS1 
,IP_ACCOUNT2_ID 
,PARTY_ACCOUNT2_NUMBER 
,PARTY_ACCOUNT2_ID 
,ACCT2_RELATIONSHIP_TYPE_CODE 
,PARTY_ACCT2_START_DATE 
,PARTY_ACCT2_END_DATE 
,BILL_TO_ADDRESS2 
,SHIP_TO_ADDRESS2 
,IP_ACCOUNT3_ID 
,PARTY_ACCOUNT3_NUMBER 
,PARTY_ACCOUNT3_ID 
,ACCT3_RELATIONSHIP_TYPE_CODE 
,PARTY_ACCT3_START_DATE 
,PARTY_ACCT3_END_DATE 
,BILL_TO_ADDRESS3 
,SHIP_TO_ADDRESS3 
,CREATED_BY ,CREATION_DATE ,LAST_UPDATED_BY ,LAST_UPDATE_DATE)
values
(CSI_I_PARTY_INTERFACE_S.NEXTVAL
,CSI_INSTANCE_INTERFACE_S.currval,null,null,null ,null ,null 
,'Imaging Innovations, Inc.'
,'HZ_PARTIES'
,'OWNER' ,null ,null 
,'N' ,null,null ,null ,null ,null ,null 
,'1002' ,null 
,'OWNER' ,null ,null ,null ,null ,null ,null ,null ,null ,null 
,null ,null ,null ,null ,null ,null ,null ,null ,null ,null ,null 
,FND_GLOBAL.USER_ID ,sysdate ,FND_GLOBAL.USER_ID ,sysdate 
);

Insert into CSI_II_RELATION_INTERFACE
(rel_interface_id 
,parallel_worker_id 
,subject_interface_id 
,object_interface_id 
,relationship_type_code 
,relationship_start_date 
,relationship_end_date 
,position_reference 
,display_order 
,mandatory_flag 
,relationship_direction 
,error_text 
,context 
,attribute1 ,attribute2 ,attribute3 ,attribute4 ,attribute5 
,attribute6 ,attribute7 ,attribute8 ,attribute9 ,attribute10 
,attribute11 ,attribute12 ,attribute13 ,attribute14 ,attribute15 
,created_by, creation_date,last_updated_by,last_update_date, last_update_login)
values
(CSI_II_RELATION_INTERFACE_S.nextval
,null
,CSI_INSTANCE_INTERFACE_S.currval 
,CSI_INSTANCE_INTERFACE_S.currval-1
,'COMPONENT-OF'
,SYSDATE
,null,null,null ,null ,null ,null ,null ,null ,null ,null ,null ,null 
,null ,null ,null ,null ,null ,null ,null ,null ,null ,null 
,FND_GLOBAL.USER_ID 
,sysdate 
,FND_GLOBAL.USER_ID 
,sysdate ,null);

Insert into CSI_IEA_VALUE_INTERFACE
(ieav_interface_id 
,inst_interface_id 
,parallel_worker_id 
,error_text 
,attribute_id 
,inv_concatenated_segments
,inventory_item_id 
,master_organization_id 
,master_organization_name 
,item_category_conc_seg 
,item_category_id 
,attribute_code 
,attribute_name 
,attribute_level 
,attribute_category 
,attribute_value 
,attribute_value_id 
,ieav_start_date 
,ieav_end_date 
,created_by ,creation_date,last_updated_by,last_update_date ,last_update_login)
Values
(CSI_IEA_VALUE_INTERFACE_S.nextval
,CSI_INSTANCE_INTERFACE_S.currval-1,null ,null ,null 
,'AS72111',null ,null 
,'Vision Operations' ,null ,null 
,'ADAPTER_NAME' ,null 
,'ITEM' ,null 
,'NETWORK_ADAPTER' ,null ,null ,null 
,FND_GLOBAL.USER_ID ,sysdate ,FND_GLOBAL.USER_ID ,sysdate ,null);

commit;
Exception
When others
Then
Null;
End;
/

After execution of the script, confirm the appropriate records have been inserted into the CSI_INSTANCE_INTERFACE, CSI_I_PARTY_INTERFACE, CSI_IEA_VALUE_INTERFACE and CSI_II_RELATION_INTERFACE tables.

Run Installed Base Open Interface Program

Run Installed Base Open Interface concurrent program by entering values in the mandatory parameters, Source System Name and Resolve Oracle IDs.

In this case Source System Name is Enterprise Manager and Resolve Oracle IDs should be set to 'Yes'.

Verify the concurrent program completed successfully by clicking on the View Log button from View Request screen. The Customer Product numbers should be listed in this Log file.

Confirm Records Created Successfully

As a result of the successful completion of the Install Base Open Interface concurrent program, the Install Base tables should now be populated. There should be no errors in the Open Interface Error Details form and your new Customer Products should exist in View Customer Products. You can view then by searching on the Customer Product number (Instance number) found in the Install Base Interface Log file. You can also view the relationship by clicking the Configuration link.