Executing the EIM Job

Use the following procedure to execute the EIM job.

To execute the EIM job

Place the respective IFB file on the server computer using the Siebsrvr/Admin file path, as shown in the following example.

Component IFB File

Product

Product.ifb

Pricelist

Pricelist.ifb

Customer

Customer.ifb

Asset

Asset.ifb
Make sure that the SESSION SQL statement of the [UPDATE ACCOUNT NUMBER] section of the Customer Ifb file is modified to reflect the working instance:
```
UPDATE ORA19111.EIM_ACCOUNT SET OU_NUM = T_ORG_EXT__RID WHERE 
IF_ROW_BATCH_NUM=100
```
where ORA19111 is the working instance.

Also, consider the same for the [UPDATE INTEGRATION ID] section of the Pricelist.ifb file:
```
SESSION SQL = "UPDATE ORA19111.EIM_PRI_LST SET PL_INTEGRATION_ID = NULL WHERE 
PL_INTEGRATION_ID IS NOT NULL"
```
For Pricelist.ifb, comment the second process using a terminate symbol (so that it becomes inactive and only the first process is executed) as follows:
```
[IMPORT ALL PRICELISTS]
TYPE = SHELL
INCLUDE = "IMPORT PRICELIST"
;INCLUDE = "UPDATE INTEGRATION ID"
```
After EIM imports all of the pricelist data and the Integration Id is populated, the administrator needs to run another ODI API to populate the cross-reference database. Then, the administrator needs to run EIM again to nullify integ_id. The format of the IFB file for the second run follows:
```
[IMPORT ALL PRICELISTS]
TYPE = SHELL
;INCLUDE = "IMPORT PRICELIST"
INCLUDE = "UPDATE INTEGRATION ID"
```
All the job parameters must remain the same for both of the runs.
Log in to the application with administrator credentials to be able to access the Server Management screen.
Navigate to the Administration - Server Management screen, then the Jobs view.
Create a new record, and select Enterprise Integration Mgr in the Component/Job field.
In the Job Parameters applet, fill in the following parameters:
- Configuration file = .Ifb File name
- Error Flags = 1
- SQL Trace Flags = 8
- Trace Flags = 1
After passing parameters, click Submit Job.
In the Jobs view, for each job that you have executed, make sure that the Status column displays Success for the jobs that you have executed.
Check the status in the EIM table by executing the SQL statements that follow. In each case, make sure that the status is IMPORTED.

Component	IFB File
Product	Product.ifb
Pricelist	Pricelist.ifb
Customer	Customer.ifb
Asset	Asset.ifb

Products

Product Header:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_PROD_INT
WHERE IF_ROW_BATCH_NUM = '100'
GROUP BY IF_ROW_STAT

Product Details:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_PROD_INT1
WHERE IF_ROW_BATCH_NUM = '100'
GROUP BY IF_ROW_STAT

Product-Inventory Locations:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_PRODINVLOC
WHERE IF_ROW_BATCH_NUM = '100'
GROUP BY IF_ROW_STAT

Pricelists

In this case since the same set of records are processed twice by the two separate sections of the IFB file: one meant for importing the Pricelist Records and other meant for updating the Integration Id to NULL, you get the DUP_REC_EXISTS status in the EIM tables.

SELECT COUNT(*),IF_ROW_STAT FROM EIM_PRI_LST
WHERE IF_ROW_BATCH_NUM = '100'
GROUP BY IF_ROW_STAT

Customers

Address:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_ADDR_PER
WHERE IF_ROW_BATCH_NUM = '100'
GROUP BY IF_ROW_STAT

Account:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_ACCOUNT
WHERE IF_ROW_BATCH_NUM = '100'
GROUP BY IF_ROW_STAT

Account Details:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_FN_ACCNT1
WHERE IF_ROW_BATCH_NUM = '100'
GROUP BY IF_ROW_STAT

Customer:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_CONTACT
WHERE IF_ROW_BATCH_NUM = '100'
GROUP BY IF_ROW_STAT

Assets

There are two sections in the IFB file: For Importing Assets and For Updating the Parent Assets.

Hence the status shows DUP_REC_EXISTS

SELECT COUNT(*),IF_ROW_STAT,IF_ROW_BATCH_NUM FROM EIM_ASSET
WHERE IF_ROW_BATCH_NUM = '100'
GROUP BY IF_ROW_STAT,IF_ROW_BATCH_NUM

Checking the EIM Log File

Use the following procedure to check the EIM log file.

To check the EIM log file

From the Jobs view in the Administration - Server Management screen, navigate to the Tasks View in the same screen.
Get the task number from the Task field.
Navigate to the Siebsrvr\log directory, and query for the log file using the task number. The log file contains details about every level of processing and information about any errors.