1.What is EIM?
Siebel Enterprise Integration Manager (EIM) manages the bi-directional exchange of data between the Siebel databases and other corporate databases. This exchange of information is accomplished through intermediary tables called EIM tables (in earlier releases, these tables were known as interface tables). The EIM tables act as a staging area between the Siebel application database and other databases. You should use EIM to perform bulk imports, exports, updates, and deletes.
2.what are the mandatory columns in EIM table?
ROW_ID. For an EIM table row to be eligible for processing, you must initialize its ROW_ID. The ROW_ID, in combination with the value of IF_ROW_BATCH_NUM, must yield a unique value. The ROW_ID values in the EIM tables are not the ROW_ID values that are assigned to the row when it is loaded into the base table. An EIM-generated ROW_ID has a ##-###-### format. A regular row ID that is assigned to the row has a #-## format.
IF_ROW_BATCH_NUM. You must set the values in this column to the same integer, greater than or equal to 0, as an identifying number for all rows to be processed as a batch. The maximum value is 2147483647. Use this column as the first key of any new indexes created on an EIM table.
IF_ROW_MERGE_ID. You can set this column to one of two values:
NULL. This value identifies the surviving or merged-into-row.
ROW_ID. This value identifies the ROW_ID number in the EIM table where the row will be merged.
IF_ROW_STAT. EIM updates this column after processing the row to indicate the status of the record. The IF_ROW_STAT column is not used by EIM when determining which rows to process. When populating the EIM tables, you can set this column to any value except NULL. You can initially set this value to FOR_IMPORT to indicate that the row has not been imported. After processing, if certain rows were not imported due to a data error, you should change:
IF_ROW_BATCH_NUM value for the rows that require reimporting
BATCH line in the configuration file
If EIM updates this column to NOT_ALLOWED after processing a row, EIM has attempted to insert a new row but the action is not allowed. In such cases, the INSERT ROWS parameter may have been set to FALSE.
3.what are the mandatory columns for file attachment?
Column
Description
Example
FILE_NAME
This column requires the root filename of the file attachment
FILE_NAME=”budget99”
FILE_EXT
This column requires the extension type of the file attachment (DOC, XLS or TXT)
FILE_EXT=”doc”
FILE_SRC_TYPE
This column requires the value “FILE” or the rows cannot be imported
FILE_SRC_TYPE=”FILE”
4.How did Choose Organization columns?
The EIM_ type interface tables use the xxx_BU/xxx_BI column pairs to map organizations. For example, the CON_BU/CON_BI column in the EIM_CONTACT interface table is mapped to the BU_ID column in the S_CONTACT base table. In order for organizations to be resolved properly, you need to populate the xxx_BU column with the organization name and leave the xxx_BI column empty. Do not populate the xxx_BU column with the organization ROW_ID. EIM looks up the ROW_ID for the organization in xxx_BU and puts it in the corresponding xxx_BI column.
5.How many type of Section in eim?
Two Types:
A. Header Section
B. Process Section
6.what are the header section parameters?
CONNECT à The ODBC source name for connecting to the database server.
LOG TRANSACTIONS TO FILE à This parameter must be in the header section and the default value is TRUE. Transactions can be logged in a file or a table. By default, EIM logs transactions into files. Log files are saved in the file system’s eim directory. If you do not want transactions to be logged in files, then setting this parameter to FALSE logs transactions to a table.
PASSWORD à The database password for the process to be run. This parameter is inherited for the EIM component from the Gateway Name Server, so it should already be set. However, you can specify this in the .IFB file if you are running EIM from the Siebel application (not the command line) and if you have not already set this value in the EIM Server Component parameters.
PROCESS à Identifies the specific process to run during this invocation of EIM. The named process must be defined in the process section of the .IFB file.
[Siebel Interface Manager] à Header section must use this reserved name.
TABLEOWNERà The database logon name that owns the tables to be operated on; used as the prefix for table names; defined during installation.
USERNAMEà The database/employee logon name for the process to be run. This parameter is inherited for the EIM component from the Gateway Name Server, so it should already be set. However, you can specify this in the .IFB file if you are running EIM from the Siebel application (not the command line) and if you have not already set this value in the EIM Server Component parameters.
7.What are the Process Section parameters?
BATCHà Required. Specifies a required batch number for the process to be run. Use this batch number to identify the set of rows to load from the EIM tables for this specific process. This batch number corresponds to the value in the interface column IF_ROW_BATCH_NUM and must be a positive integer between 0 and 2147483647 (no commas). To specify multiple batches, use a range or list of batch numbers. To specify a range of batches, use the first_batch-last_batch format as shown in this example:
BATCH=100-120
To list batches, use the comma-delimited format as shown in this
Example:
BATCH=100,103,104
COMMIT EACH PASSà Optional. Commit after each EIM pass; default is TRUE.
COMMIT EACH TABLEà Optional. Commit after each base table; default is TRUE.
IGNORE BASE TABLESà Optional. Do not process these tables.
USING SYNONYMSà Optional. Controls the queries of account synonyms during import processing. When set to FALSE, this parameter saves processing time because queries that look up synonyms are not used. The default value is TRUE.
USE INDEX HINTSà Optional. For Oracle databases only. Controls whether EIM issues optimizer hints to the underlying database to improve performance and throughput. The default value is FALSE
INCLUDEàThis parameter can be used only in shell processes. A shell process uses the INCLUDE statement to invoke a sequence of processes in a single run.
LOG TRANSACTIONSàUse this parameter to control the logging mode. If this parameter is set to TRUE, EIM logs changes when mobile clients synchronize. If this parameter is set to FALSE, changes are not logged. In general, when you load data into the HQ database for the first time, this parameter should be set to FALSE.
ONLY BASE TABLESàOptional. Process only base tables.
ROLLBACK ON ERRORàOptional. Error rollback behavior; default is FALSE.
TABLEà Required. Specifies the name of an EIM table used in this process. Multiple TABLE parameters may be used to define a process using more than one table.
TYPEàRequired. This parameter specifies the type of process being defined (possible values are IMPORT, EXPORT, DELETE, MERGE, SHELL). A shell process uses the INCLUDE statement to invoke a sequence of processes in a single run.
USING SYNONYMSàOptional. Controls the queries of account synonyms during import processing. When set to FALSE, this parameter saves processing time because queries that look up synonyms are not used. The default value is TRUE.
8. What is called an interface table and why we use interface table in EIM?
Interface table is a staging area for eim. Data from legacy is transferred to eim table first using non-siebel process. For this we need interface table.
9. How will you fine the particular interface table for a base table?
Go to Toolsà In Object Explorer select Flat Tab.
Select Eim Table Mapping à Query in OBLE in Destination Table (Base Table Name) and get the corresponding EIM Table Name in Parent EIM Interface Table.
10. What is .ifb? Mention its use?
. ifb is a configuration file, which is used when EIM Component is running. It contains information such as user name, password, process and many other parameters.
11. Write a sample ifb file for import process for Account or contact
.IFB FILE FOR ACCOUNT
[siebel Interface Manager]
User Name = “sadmin”
Password = “sadmin”
Process=ImportAccount
[ImportAccount]
Type = Import
Table = EIM_ACCOUNT
BATCH=55
ONLY BASE TABLES = S_PARTY, S_ACCNT_POSTN, S_ORG_EXT, S_ORG_BU
DEFAULT COLUMN = ACCNT_FLG, "Y"
DEFAULT COLUMN = ACTIVE_FLG, "Y"
DEFAULT COLUMN = BUYING_GROUP_FLG, "N"
DEFAULT COLUMN = CG_DEDN_AUTH_FLG, "Y"
DEFAULT COLUMN = CG_SVP_A_LOCK_FLG, "N"
DEFAULT COLUMN = CG_SVP_LOCK_FLG, "N"
DEFAULT COLUMN = CG_SVP_SKIP_FLG, "N"
DEFAULT COLUMN = CL_SITE_FLG, "N"
DEFAULT COLUMN = DISA_CLEANSE_FLG, "N"
DEFAULT COLUMN = EVT_LOC_FLG, "N"
DEFAULT COLUMN = FCST_ORG_FLG, "N"
DEFAULT COLUMN = FUND_ELIG_FLG, "N"
DEFAULT COLUMN = INCL_FLG, "N"
.IFB FILE FOR CONTACT
[Siebel Interface Manager]
USER NAME = "SADMIN"
PASSWORD = "SADMIN"
PROCESS = Import Contact
[Import Contact]
TYPE = SHELL
INCLUDE = "Import Contact Information"
INCLUDE = "Import POSTN_CON Information"
[Import Contact Information]
TYPE = IMPORT
TABLE= EIM_CONTACT
BATCH = 555
ONLY BASE TABLES = S_PARTY, S_CONTACT, S_CONTACT_BU
DEFAULT COLUMN = CON_ACTIVE_FLG, "Y"
DEFAULT COLUMN = CON_DISACLEANSEFLG, "N"
DEFAULT COLUMN = CON_DISPIMGAUTHFLG, "N"
DEFAULT COLUMN = CON_EMAILSRUPD_FLG, "N"
DEFAULT COLUMN = CON_EMP_FLG, "N"
DEFAULT COLUMN = CON_PRIV_FLG, "N"
DEFAULT COLUMN = CON_INVSTGTR_FLG, "N"
DEFAULT COLUMN = CON_PO_PAY_FLG, "N"
DEFAULT COLUMN = CON_PROSPECT_FLG, "N"
DEFAULT COLUMN = CON_PTSHPCONTACTFL, "N"
DEFAULT COLUMN = CON_PTSHPKEYCONFLG, "N"
DEFAULT COLUMN = CON_SENDSURVEY_FLG, "N"
DEFAULT COLUMN = CON_SPEAKER_FLG, "N"
DEFAULT COLUMN = CON_SUPPRESSEMAILF, "N"
DEFAULT COLUMN = CON_SUPPRESSFAXFLG, "N"
[Import POSTN_CON Information]
TYPE = IMPORT
TABLE= EIM_CONTACT1
BATCH = 555
ONLY BASE TABLES = S_PARTY, S_CONTACT, S_POSTN_CON
12. Why do you use Docking Transaction and UTC?
Docking Transaction:
Typically, a disabled Docking: Transaction Logging setting is only used during initial data loads. Disable Docking: Transaction Logging is set from the System Preferences settings within the Siebel application. This setting indicates whether or not the Siebel application will log transactions for the purpose of routing data to Siebel Mobile Web Clients. The default for this parameter is FALSE. If there are no Siebel Mobile Web Clients, then the default setting should remain. If you have Siebel Mobile Web Clients, then this parameter must be set to TRUE in order to route transactions to the mobile clients. However, during initial data loads, you can set this parameter to FALSE to reduce transaction activity to the Siebel docking tables. After the initial loads are complete, set the parameter back to TRUE.
UTC: If the Siebel administrator is importing into base tables that use the UTC (Universal Time Coordinated) time scale, the Siebel administrator or a database administrator must convert the local time in the data into UTC before loading data into the EIM tables.
13. List the difference between Default Column and Fixed column?
Default Column:
(Import only) Specifies a default value for an EIM table column. The
syntax is column name, value.
Example: DEFAULT COLUMN = CURCY_CD, "USD"
The given value will be used only if the column is null in the EIM table.
Fixed Column:
(Import only.) Specifies the value for an EIM table column. The syntax
is the same as for DEFAULT COLUMN.
Example: FIXED COLUMN=ORG_CD,. Commercial.
The given value will be loaded into the Siebel base table, overriding the value in the EIM table column.
14. How to identify an EIM table prior to Siebel 6 release?
Prior to Siebel 6 Eim Table starts with S_. After siebel 6 Eim Table starts with EIM_.
15. How to find the status of EIM process?
The status of EIM Process could be seen in IF_ROW_STAT IN EIM INTERFACE TABLE.
16. Write the steps for Import in EIM?
1 Identify and validate the data to be imported.
To perform this task, you must:
A. Determine the data to load and whether it already exists in another database. You should review existing data for completeness. For example, the Siebel database may require both an area code and a telephone number, while your existing database may not.
B. Determine the number of opportunities, contacts, and accounts you plan to import. This information assists you in estimating the time and resources required to import, process, and store your data.
2 Identify the column mappings and user key columns of the data to be imported.
To perform this task, you must:
A. Identify the mapping between the data and Siebel base columns.
B. Identify the EIM table columns that map to these base table columns.
C. Identify the user key columns and make sure they are populated uniquely.
3 Make sure that your hardware and software environments are ready. Before you use Siebel EIM tables to import data, the Siebel
application must be properly installed. Work with your Siebel representative and MIS personnel to verify that the required hardware and software resources are available.
4 Back up your existing database.
Before undertaking any significant change. Such as installing a new application, importing data, or upgrading an installed application. You should first perform a comprehensive backup of your database. This facilitates an easy recovery if problems occur.
5 Copy file attachments to the Siebel server subdirectory named. input.. If you want to import file attachments, you can:
A. Copy the files to the input subdirectory under the Siebel server root directory.
B. Store file attachments in the location specified in the ATTACHMENT DIRECTORY .IFB file header parameter.
Siebel EIM tables support all file attachment formats, including common file types such as Word documents (.doc), Excel spreadsheets (.xls), and text files (.txt).
6 Load and verify the EIM tables. Your database administrator can use a database tool provided with your RDBMS (such as SQL*Loader, Bulk Copy Utility, or dbload) to copy data from your existing database to the Siebel EIM tables.
A. After the EIM tables are loaded, check the number of loaded rows against your existing database to make sure that the appropriate rows were loaded.
B.Check the contents of several rows to make sure that the tables are ready for the import process.
7 Edit the EIM configuration file (default.ifb). This file customizes the behavior of EIM by defining the data you will import and identifying the batch number to use.
8 Test your import process. Run a small test batch (perhaps 100 records) to verify that the EIM tables load correctly, and that the correct parameters are set in the configuration file and on the srvrmgr command line.
9 Run the import process. Although your batch sizes depend on the volume of data you must import, consider using multiple smaller batches (1,000 to 5,000 rows) rather than one large batch. Smaller batches place fewer demands on resources. Also, when using smaller batches, the fixing of problems is simpler. If a batch is not imported correctly, it is easier to isolate the condition, correct it, and rerun the batch.
10 Verify results. EIM provides several diagnostic tools that let you verify the success of import processing. You must test and run the import process and verify the results for each batch you are importing.
17. What are the possible IF_ROW_STAT values after import?
AMBIGUOUS: There are two rows in the base table that have the same user key but different conflict IDs. EIM cannot distinguish these rows
DUP_RECORD_EXISTS: The row exactly matches rows that already exist in the destination tables.
DUP_RECORD_IN_EIM_TBL:
The row was eliminated because it is a duplicate (has the same user key) of another row in the EIM table with the same batch number. In this case, MIN(ROW_ID) is the record processed, and the other records with the same
user key are marked as UP_RECORD_IN_EIM_TBL.Do not confuse DUP_RECORD_IN_EIM_TBL with UP_RECORD_EXISTS. DUP_RECORD_EXISTS status indicates that the same record already exists in the base table, while DUP_RECORD_IN_EIM_TBL status indicates that there are two or more EIM table records having the same user key values.
FOREIGN_KEY:
A required foreign key column in the target table could not be resolved.
IMPORTED:
The row was successfully processed against all its destination base tables. This status is set after the import has been completed. You can check the import status by using database commands to query the appropriate EIM tables for rows whose IF_ROW_STAT value is not equal to IMPORTED. The result is a list of rows that were not successfully imported.
IMPORT_REJECTED:
A user-specified filter query failed for this row.
IN_PROGRESS:
If rows still have this status value after EIM exits, a failure occurred that aborted processing for this table.
PARTIALLY_IMPORTED:
The row did not fail for the target table (although it may have been a duplicate), but did fail during processing of a secondary base table. This status is set after the import has completed.
PICKLIST_VALUES:
A required picklist value in the target table could not be resolved.
REQUIRED_COLS:
One or more required columns for the target table were NULL.
ROLLBACK:
EIM encountered an error, such as an SQL database failure, and rolled back the transaction. This status is only used when ROLLBACK ON ERROR = TRUE.
SQL_ERROR:
An SQL error occurred during an attempt to import this row. This error occurs for rows processed when transaction logging is set to TRUE.
18.What is Export Process?
To export data, EIM reads the data in the Siebel database tables and places the information in the appropriate EIM tables. You can then copy data from the EIM tables into another database. The export process generally populates the applicable EIM table with a row for every Siebel base table row encountered. As a consequence, where EIM tables have mappings to multiple Siebel base tables, one export operation can generate multiple rows within the EIM table governing the rows encountered within the Siebel base tables.
19.what are the tasks eim perform in export process?
A. EIM initializes the EIM tables for export.
B. It applies filter logic to select rows for exporting.
C.EIM updates EIM table rows to indicate the export status.
20.write step for export?
1 EIM initializes EIM tables for export.
If CLEAR INTERFACE TABLE in the configuration file is TRUE, all rows with the specified batch number are deleted. Otherwise, a warning is issued if rows already exist with the specified batch number. The default configuration file is default.ifb.
2 It uses export parameter expressions in the configuration file to locate and export table rows:
A. If EXPORT ALL ROWS is TRUE, ignore any EXPORT MATCHES parameters and export all rows.
B.If EXPORT ALL ROWS is FALSE; use EXPORT MATCHES parameters to locate specific rows.
Set IF_ROW_STAT to EXPORTED for rows that are successfully exported.
3 For parent tables, EIM locates child table rows and exports them to their corresponding EIM tables.
21.what are the parameters for export process?
ATTACHMENT DIRECTORY:
(Default is SIEBEL_HOME\OUTPUT) Specifies the directory to be used for exporting attachments. Before specifying a directory, make sure the directory exists on a Siebel Server machine and you have read and write access to it. Example: ATTACHMENT DIRECTORY = SIEBEL_HOME\OUTPUT If the export of an attachment fails, the export process continues and EIM writes a message in the trace file.
CLEAR INTERFACE TABLE:
Specifies whether existing rows in the EIM table for the given batch number should be deleted. The default value is TRUE.
EXPORT ALL ROWS:
Specifies that all rows in the target base table and secondary tables are to be exported. The default value is FALSE. Existing values in the EIM table and export matches expressions are ignored. For all columns to export using an EIM table (both data from the base table and data from related child tables), you need to make sure this parameter is set to TRUE (you may need to add this line if it does not currently exist) in the .IFB file. Note: Rows from child tables of related child tables are not exported until they have been mapped.
EXPORT MATCHES WHERE clause fragment. Example: EXPORT MATCHES=(NAME LIKE .GEN%.)
22.IFB file for Export All Rows?
[Siebel Interface Manager]
USER NAME=”SADMIN”
PASSWORD=”SADMIN”
PROCESS=Export Accounts
[Export Accounts]
TYPE = EXPORT
BATCH = 2
TABLE = EIM_ACCOUNT
EXPORT ALL ROWS = TRUE
23. IFB file for Export Matches?
[Siebel Interface Manager]
USER NAME=”SADMIN”
PASSWORD=”SADMIN”
PROCESS=Export Accounts
[Export Accounts]
TYPE = EXPORT
BATCH = 2
TABLE = EIM_ACCOUNT
EXPORT ALL ROWS = FALSE
EXPORT MATCHES=(NAME LIKE .GEN%.)
24.How does Check Export Result?
A. Query the appropriate EIM tables for rows whose IF_ROW_BATCH_NUM equals the batch number for the export.
The value of IF_ROW_STAT should be EXPORTED.
25.what are task for delete process?
1.EIM initializes the EIM tables for deletion.
2. It applies filter logic to do one of the following:
a) Select rows for deleting
b) Insert EIM tables rows that correspond to matching base table rows
c) Select rows with matching user keys in the EIM tables
3. EIM updates other tables with rows containing foreign keys that point to newly deleted rows.
26.write step for delete process?
1. EIM initializes EIM tables for delete.
If CLEAR INTERFACE TABLE in the configuration file is TRUE, all rows with the specified batch number are deleted. CLEAR INTERFACE TABLE must be FALSE for a delete process that uses EIM table values to identify rows for deletion.
2. EIM deletes rows.
a If the DELETE EXACT parameter in the configuration file is set to TRUE, EIM deletes the rows
from the table that match the user key defined in the EIM table.
b If the DELETE MATCHES parameter in the configuration file is set to a base table, EIM deletes the rows from the target base table that match the predicate specified in the parameter.
c If the DELETE ALL ROWS parameter in the configuration file is set to TRUE, EIM deletes all rows from the target base table.
3 .EIM sets IF_ROW_STAT to DELETED for rows that are successfully processed.
a) When a foreign key column that references the deleted record is a required one, the record with the foreign key is deleted. Otherwise, the foreign key column is cleared.
27. What are the parameters for Delete process?
CASCADE DELETE ONLY (Default = FALSE). Set this parameter to TRUE to delete child records with nullable foreign keys when the parent record is deleted. If FALSE, then when EIM deletes a parent record, it sets the foreign keys of the child records to NULL.
CLEAR INTERFACE TABLE
This parameter specifies whether existing rows in the EIM table for the
given batch number should be deleted. Valid values are true (the default unless DELETE EXACT = TRUE) and false (the default if DELETE EXACT = FALSE).
DELETE ALL ROWS
Used for deleting all rows in table; default is FALSE.
DELETE EXACT
Delete using user key matching algorithm with rows in EIM table
DELETE SKIP PRIMARY
This parameter specifies whether EIM should perform a cascade update to the primary child column. The default value is TRUE.
DELETE MATCHES
SQL WHERE fragment deletion criteria. Example: DELETE MATCHES = EIM_ACCOUNT, (NAME LIKE .TST_ACCT%.).
DELETE ROWS
This parameter specifies whether rows from the target base table can be deleted. Valid values are TRUE (the default) and FALSE. This parameter can prevent deletions from one table while allowing them in others. For example, the following parameter setting prevents deletion
of rows from the S_ADDR_ORG table:
DELETE ROWS=S_ADDR_ORG, FALSE
IGNORE BASE COLUMNS
Specifies base table columns to be ignored by the import process. Use commas to separate column names, which can be qualified with base table names. Required and user key columns cannot be ignored. Use this parameter to improve performance when updating all but a few Columns. The default is to not ignore any base table columns.
UPDATE ROWS:
Specifies whether foreign key references can be updated. This parameter can be used to prevent the updating of foreign key references with a setting of FALSE. The default value is TRUE, which affects all tables. To affect only specific tables, you can specify a table name. For example:
UPDATE ROWS = S_CONTACT, TRUE
The UPDATE ROWS parameter also prevents updates in one table while allowing them in others. If this parameter is set to FALSE, EIM does not update rows in the specified base table. If you need to specify multiple tables, use one UPDATE ROWS statement for each table.
Inappropriate use can result in dangling foreign key pointers.
28. Write ifb file for delete all rows?
[Siebel Interface Manager]
USER NAME=”SADMIN”
PSSWORD=”SADMIN”
PROCESS=Delete Accounts
[Delete Accounts]
TYPE = DELETE
BATCH = 200
TABLE = EIM_ACCOUNT
DELETE ALL ROWS = TRUE
29.How do Check delete results in eim table?
Query the appropriate EIM table for rows whose IF_ROW_BATCH_NUM equals the batch number for the delete. The value of T_DELETED_ROW_ID identifies deleted rows.
30. Write step for delete process using delete exact parameter?
A. Populate the following columns in the EIM table (such as user keys for the S_ORG_PROD table and all the special interface columns):
ACCNT_NAME, ACCNT_LOC, INS_PROD_NAME, INS_PROD_VENDR, INS_PROD_VENDR_LOC, INS_DT, ROW_ID, IF_ROW_BATCH_NUM, IF_ROW_STAT, ROW_ID.
B.Add or modify the following process section in your .IFB file:
TYPE = DELETE
BATCH NUMBER =
TABLE = EIM_ACCOUNT
ONLY BASE TABLES = S_ORG_PROD
DELETE EXACT=TRUE
C.Run EIM.
This deletes all rows from the S_ORG_PROD table that have user keys that match the rows in your EIM table.
31. What are the tasks for merge process?
A. Initialize the EIM tables for merge.
B. Initialize the EIM tables for merge.
C. Merge child rows into the replacement rows. EIM then deletes rows from the target base table that are specified in the EIM table.
1. For deleted rows, EIM sets T_MERGED_ROW_ID to the ROW_ID of the row that was merged into (the surviving row).
2. EIM sets T_DELETED_ROW_ID to the ROW_ID of the deleted base table row.
D.Update child rows containing foreign keys that point to newly deleted rows. For base tables that have foreign keys in newly deleted rows, EIM updates the foreign keys to point to surviving rows (depending on the value for UPDATE ROWS in the configuration file).
32. Write ifb file for merge process?
[Siebel Interface Manager]
USER NAME=”SADMIN”
PSSWORD=”SADMIN”
PROCESS= Merge Accounts
[Merge Accounts]
TYPE = MERGE
BATCH = 1
TABLE = EIM_ACCOUNT
UPDATE ROWS = TRUE
33. List parameter for merge process?
SET BASED LOGGING
Specifies whether set-based logging is enabled. The default value is TRUE.
NOTE: EIM will ignore this parameter if Docking Transaction Logging is
set to FALSE in the System Preferences view
UPDATE ROWS
Specifies whether the foreign key (or keys) that reference the merged rows in the named table need to be adjusted. Valid values are TRUE (the default) and FALSE.
NOTE: Use the UPDATE ROWS = Table_Name, FALSE setting carefully. Inappropriate use can result in dangling foreign key pointers.
34. How do check merge results in eim table?
1 Query the appropriate EIM table for rows whose IF_ROW_BATCH_NUM equals the batch number for the merge process.
2 Inspect the values of T_DELETED_ROW_ID and T_MERGED_ROW_ID.
35. List required column for merge process in eim table?
ROW_ID, IF_ROW_BATCH_NUM,IF_ROW_STAT,IF_ROW_MERGE _ID
36. Why we give sql trace flag 8 i?
Setting the SQL Trace Flags parameter to 8 creates a log of all SQL statements that make up the EIM task.
37. What is purpose for give trace flag 1,2,4,8,32?
Trace Flag 1
Setting the Trace Flags parameter to 1 creates a step-oriented log of the task. This can be used to determine the amount of time EIM spends on each step of the EIM task, or for each EIM table processed.
Trace Flag 2
Setting the Trace Flags parameter to 2 creates a file log that traces all substitutions of user parameters.
Trace Flag 4
Setting the Trace Flags parameter to 4 creates a file log that traces all user-key overrides.
Trace Flag 8
Setting the Trace Flags parameter to 8 creates a file log that traces all Interface Mapping warnings.
Trace Flag 32
Setting the Trace Flags parameter to 32 creates a file log that traces all file attachment status.
38. What is purpose for give error flag 1?
Setting the Error Flags parameter to 1 produces a detailed explanation of rows that were not successfully processed.
39. Step for running for eim process using graphical user interface?
During this step data is imported from eim table to base table.
1.navigate to Administration - Server Management >jobs
2.add new record. In the Component/Job field, click the select button, and in the Component/Jobs window, select the Enterprise Integration Mgr component.
3. Job parameter list applet add a new record. Give value for name field and value field
4click Start button, now status Queued
5.click query and go button until status Success
40. Write the guidelines for improve performance in eim?
Verify that all indexes exist for the tables involved. Keep in mind, however, that for large loads you should drop most of the indexes from the target tables to increase the speed of the process, rebuilding those indexes afterward when the process is finished. Limit tables and columns to be processed using ONLY BASE ABLES/COLUMNS configuration parameters to minimize EIM processing. Consider switching off transaction logging during the EIM run. This improves performance. However, the performance benefit must be balanced with the need for mobile users to reextract afterward. Altering batch sizes to find the optimal batch size for a given business component typically helps resolve performance issues. The batch size is dependent upon the quantity of data and which type of EIM process you are running. For EIM delete processes that use the DELETE EXACT parameter, use a batch size of 20,000 rows or less. Try using batch ranges (BATCH = x.y). This allows you to run with smaller batch sizes and avoid the startup overhead on each batch. The maximum number of batches that you can run in an EIM process is 1,000.Perform regular table maintenance on EIM tables. Frequent insert or delete operations on EIM tables can cause fragmentation. Consult your database administrator to detect and correct fragmentation in the EIM tables. Delete batches from EIM tables on completion. Leaving old batches in the EIM table wastes space and could adversely affect performance. Run independent EIM jobs in parallel Set USING SYNONYMS parameter to FALSE in the .IFB file to indicate that account synonyms do not need to be checked.If no other strategy appears to be successful, use the SQLPROFILE parameter to identify slow-running steps and queries
Siebel Enterprise Integration Manager (EIM) manages the bi-directional exchange of data between the Siebel databases and other corporate databases. This exchange of information is accomplished through intermediary tables called EIM tables (in earlier releases, these tables were known as interface tables). The EIM tables act as a staging area between the Siebel application database and other databases. You should use EIM to perform bulk imports, exports, updates, and deletes.
2.what are the mandatory columns in EIM table?
ROW_ID. For an EIM table row to be eligible for processing, you must initialize its ROW_ID. The ROW_ID, in combination with the value of IF_ROW_BATCH_NUM, must yield a unique value. The ROW_ID values in the EIM tables are not the ROW_ID values that are assigned to the row when it is loaded into the base table. An EIM-generated ROW_ID has a ##-###-### format. A regular row ID that is assigned to the row has a #-## format.
IF_ROW_BATCH_NUM. You must set the values in this column to the same integer, greater than or equal to 0, as an identifying number for all rows to be processed as a batch. The maximum value is 2147483647. Use this column as the first key of any new indexes created on an EIM table.
IF_ROW_MERGE_ID. You can set this column to one of two values:
NULL. This value identifies the surviving or merged-into-row.
ROW_ID. This value identifies the ROW_ID number in the EIM table where the row will be merged.
IF_ROW_STAT. EIM updates this column after processing the row to indicate the status of the record. The IF_ROW_STAT column is not used by EIM when determining which rows to process. When populating the EIM tables, you can set this column to any value except NULL. You can initially set this value to FOR_IMPORT to indicate that the row has not been imported. After processing, if certain rows were not imported due to a data error, you should change:
IF_ROW_BATCH_NUM value for the rows that require reimporting
BATCH line in the configuration file
If EIM updates this column to NOT_ALLOWED after processing a row, EIM has attempted to insert a new row but the action is not allowed. In such cases, the INSERT ROWS parameter may have been set to FALSE.
3.what are the mandatory columns for file attachment?
Column
Description
Example
FILE_NAME
This column requires the root filename of the file attachment
FILE_NAME=”budget99”
FILE_EXT
This column requires the extension type of the file attachment (DOC, XLS or TXT)
FILE_EXT=”doc”
FILE_SRC_TYPE
This column requires the value “FILE” or the rows cannot be imported
FILE_SRC_TYPE=”FILE”
4.How did Choose Organization columns?
The EIM_ type interface tables use the xxx_BU/xxx_BI column pairs to map organizations. For example, the CON_BU/CON_BI column in the EIM_CONTACT interface table is mapped to the BU_ID column in the S_CONTACT base table. In order for organizations to be resolved properly, you need to populate the xxx_BU column with the organization name and leave the xxx_BI column empty. Do not populate the xxx_BU column with the organization ROW_ID. EIM looks up the ROW_ID for the organization in xxx_BU and puts it in the corresponding xxx_BI column.
5.How many type of Section in eim?
Two Types:
A. Header Section
B. Process Section
6.what are the header section parameters?
CONNECT à The ODBC source name for connecting to the database server.
LOG TRANSACTIONS TO FILE à This parameter must be in the header section and the default value is TRUE. Transactions can be logged in a file or a table. By default, EIM logs transactions into files. Log files are saved in the file system’s eim directory. If you do not want transactions to be logged in files, then setting this parameter to FALSE logs transactions to a table.
PASSWORD à The database password for the process to be run. This parameter is inherited for the EIM component from the Gateway Name Server, so it should already be set. However, you can specify this in the .IFB file if you are running EIM from the Siebel application (not the command line) and if you have not already set this value in the EIM Server Component parameters.
PROCESS à Identifies the specific process to run during this invocation of EIM. The named process must be defined in the process section of the .IFB file.
[Siebel Interface Manager] à Header section must use this reserved name.
TABLEOWNERà The database logon name that owns the tables to be operated on; used as the prefix for table names; defined during installation.
USERNAMEà The database/employee logon name for the process to be run. This parameter is inherited for the EIM component from the Gateway Name Server, so it should already be set. However, you can specify this in the .IFB file if you are running EIM from the Siebel application (not the command line) and if you have not already set this value in the EIM Server Component parameters.
7.What are the Process Section parameters?
BATCHà Required. Specifies a required batch number for the process to be run. Use this batch number to identify the set of rows to load from the EIM tables for this specific process. This batch number corresponds to the value in the interface column IF_ROW_BATCH_NUM and must be a positive integer between 0 and 2147483647 (no commas). To specify multiple batches, use a range or list of batch numbers. To specify a range of batches, use the first_batch-last_batch format as shown in this example:
BATCH=100-120
To list batches, use the comma-delimited format as shown in this
Example:
BATCH=100,103,104
COMMIT EACH PASSà Optional. Commit after each EIM pass; default is TRUE.
COMMIT EACH TABLEà Optional. Commit after each base table; default is TRUE.
IGNORE BASE TABLESà Optional. Do not process these tables.
USING SYNONYMSà Optional. Controls the queries of account synonyms during import processing. When set to FALSE, this parameter saves processing time because queries that look up synonyms are not used. The default value is TRUE.
USE INDEX HINTSà Optional. For Oracle databases only. Controls whether EIM issues optimizer hints to the underlying database to improve performance and throughput. The default value is FALSE
INCLUDEàThis parameter can be used only in shell processes. A shell process uses the INCLUDE statement to invoke a sequence of processes in a single run.
LOG TRANSACTIONSàUse this parameter to control the logging mode. If this parameter is set to TRUE, EIM logs changes when mobile clients synchronize. If this parameter is set to FALSE, changes are not logged. In general, when you load data into the HQ database for the first time, this parameter should be set to FALSE.
ONLY BASE TABLESàOptional. Process only base tables.
ROLLBACK ON ERRORàOptional. Error rollback behavior; default is FALSE.
TABLEà Required. Specifies the name of an EIM table used in this process. Multiple TABLE parameters may be used to define a process using more than one table.
TYPEàRequired. This parameter specifies the type of process being defined (possible values are IMPORT, EXPORT, DELETE, MERGE, SHELL). A shell process uses the INCLUDE statement to invoke a sequence of processes in a single run.
USING SYNONYMSàOptional. Controls the queries of account synonyms during import processing. When set to FALSE, this parameter saves processing time because queries that look up synonyms are not used. The default value is TRUE.
8. What is called an interface table and why we use interface table in EIM?
Interface table is a staging area for eim. Data from legacy is transferred to eim table first using non-siebel process. For this we need interface table.
9. How will you fine the particular interface table for a base table?
Go to Toolsà In Object Explorer select Flat Tab.
Select Eim Table Mapping à Query in OBLE in Destination Table (Base Table Name) and get the corresponding EIM Table Name in Parent EIM Interface Table.
10. What is .ifb? Mention its use?
. ifb is a configuration file, which is used when EIM Component is running. It contains information such as user name, password, process and many other parameters.
11. Write a sample ifb file for import process for Account or contact
.IFB FILE FOR ACCOUNT
[siebel Interface Manager]
User Name = “sadmin”
Password = “sadmin”
Process=ImportAccount
[ImportAccount]
Type = Import
Table = EIM_ACCOUNT
BATCH=55
ONLY BASE TABLES = S_PARTY, S_ACCNT_POSTN, S_ORG_EXT, S_ORG_BU
DEFAULT COLUMN = ACCNT_FLG, "Y"
DEFAULT COLUMN = ACTIVE_FLG, "Y"
DEFAULT COLUMN = BUYING_GROUP_FLG, "N"
DEFAULT COLUMN = CG_DEDN_AUTH_FLG, "Y"
DEFAULT COLUMN = CG_SVP_A_LOCK_FLG, "N"
DEFAULT COLUMN = CG_SVP_LOCK_FLG, "N"
DEFAULT COLUMN = CG_SVP_SKIP_FLG, "N"
DEFAULT COLUMN = CL_SITE_FLG, "N"
DEFAULT COLUMN = DISA_CLEANSE_FLG, "N"
DEFAULT COLUMN = EVT_LOC_FLG, "N"
DEFAULT COLUMN = FCST_ORG_FLG, "N"
DEFAULT COLUMN = FUND_ELIG_FLG, "N"
DEFAULT COLUMN = INCL_FLG, "N"
.IFB FILE FOR CONTACT
[Siebel Interface Manager]
USER NAME = "SADMIN"
PASSWORD = "SADMIN"
PROCESS = Import Contact
[Import Contact]
TYPE = SHELL
INCLUDE = "Import Contact Information"
INCLUDE = "Import POSTN_CON Information"
[Import Contact Information]
TYPE = IMPORT
TABLE= EIM_CONTACT
BATCH = 555
ONLY BASE TABLES = S_PARTY, S_CONTACT, S_CONTACT_BU
DEFAULT COLUMN = CON_ACTIVE_FLG, "Y"
DEFAULT COLUMN = CON_DISACLEANSEFLG, "N"
DEFAULT COLUMN = CON_DISPIMGAUTHFLG, "N"
DEFAULT COLUMN = CON_EMAILSRUPD_FLG, "N"
DEFAULT COLUMN = CON_EMP_FLG, "N"
DEFAULT COLUMN = CON_PRIV_FLG, "N"
DEFAULT COLUMN = CON_INVSTGTR_FLG, "N"
DEFAULT COLUMN = CON_PO_PAY_FLG, "N"
DEFAULT COLUMN = CON_PROSPECT_FLG, "N"
DEFAULT COLUMN = CON_PTSHPCONTACTFL, "N"
DEFAULT COLUMN = CON_PTSHPKEYCONFLG, "N"
DEFAULT COLUMN = CON_SENDSURVEY_FLG, "N"
DEFAULT COLUMN = CON_SPEAKER_FLG, "N"
DEFAULT COLUMN = CON_SUPPRESSEMAILF, "N"
DEFAULT COLUMN = CON_SUPPRESSFAXFLG, "N"
[Import POSTN_CON Information]
TYPE = IMPORT
TABLE= EIM_CONTACT1
BATCH = 555
ONLY BASE TABLES = S_PARTY, S_CONTACT, S_POSTN_CON
12. Why do you use Docking Transaction and UTC?
Docking Transaction:
Typically, a disabled Docking: Transaction Logging setting is only used during initial data loads. Disable Docking: Transaction Logging is set from the System Preferences settings within the Siebel application. This setting indicates whether or not the Siebel application will log transactions for the purpose of routing data to Siebel Mobile Web Clients. The default for this parameter is FALSE. If there are no Siebel Mobile Web Clients, then the default setting should remain. If you have Siebel Mobile Web Clients, then this parameter must be set to TRUE in order to route transactions to the mobile clients. However, during initial data loads, you can set this parameter to FALSE to reduce transaction activity to the Siebel docking tables. After the initial loads are complete, set the parameter back to TRUE.
UTC: If the Siebel administrator is importing into base tables that use the UTC (Universal Time Coordinated) time scale, the Siebel administrator or a database administrator must convert the local time in the data into UTC before loading data into the EIM tables.
13. List the difference between Default Column and Fixed column?
Default Column:
(Import only) Specifies a default value for an EIM table column. The
syntax is column name, value.
Example: DEFAULT COLUMN = CURCY_CD, "USD"
The given value will be used only if the column is null in the EIM table.
Fixed Column:
(Import only.) Specifies the value for an EIM table column. The syntax
is the same as for DEFAULT COLUMN.
Example: FIXED COLUMN=ORG_CD,. Commercial.
The given value will be loaded into the Siebel base table, overriding the value in the EIM table column.
14. How to identify an EIM table prior to Siebel 6 release?
Prior to Siebel 6 Eim Table starts with S_. After siebel 6 Eim Table starts with EIM_.
15. How to find the status of EIM process?
The status of EIM Process could be seen in IF_ROW_STAT IN EIM INTERFACE TABLE.
16. Write the steps for Import in EIM?
1 Identify and validate the data to be imported.
To perform this task, you must:
A. Determine the data to load and whether it already exists in another database. You should review existing data for completeness. For example, the Siebel database may require both an area code and a telephone number, while your existing database may not.
B. Determine the number of opportunities, contacts, and accounts you plan to import. This information assists you in estimating the time and resources required to import, process, and store your data.
2 Identify the column mappings and user key columns of the data to be imported.
To perform this task, you must:
A. Identify the mapping between the data and Siebel base columns.
B. Identify the EIM table columns that map to these base table columns.
C. Identify the user key columns and make sure they are populated uniquely.
3 Make sure that your hardware and software environments are ready. Before you use Siebel EIM tables to import data, the Siebel
application must be properly installed. Work with your Siebel representative and MIS personnel to verify that the required hardware and software resources are available.
4 Back up your existing database.
Before undertaking any significant change. Such as installing a new application, importing data, or upgrading an installed application. You should first perform a comprehensive backup of your database. This facilitates an easy recovery if problems occur.
5 Copy file attachments to the Siebel server subdirectory named. input.. If you want to import file attachments, you can:
A. Copy the files to the input subdirectory under the Siebel server root directory.
B. Store file attachments in the location specified in the ATTACHMENT DIRECTORY .IFB file header parameter.
Siebel EIM tables support all file attachment formats, including common file types such as Word documents (.doc), Excel spreadsheets (.xls), and text files (.txt).
6 Load and verify the EIM tables. Your database administrator can use a database tool provided with your RDBMS (such as SQL*Loader, Bulk Copy Utility, or dbload) to copy data from your existing database to the Siebel EIM tables.
A. After the EIM tables are loaded, check the number of loaded rows against your existing database to make sure that the appropriate rows were loaded.
B.Check the contents of several rows to make sure that the tables are ready for the import process.
7 Edit the EIM configuration file (default.ifb). This file customizes the behavior of EIM by defining the data you will import and identifying the batch number to use.
8 Test your import process. Run a small test batch (perhaps 100 records) to verify that the EIM tables load correctly, and that the correct parameters are set in the configuration file and on the srvrmgr command line.
9 Run the import process. Although your batch sizes depend on the volume of data you must import, consider using multiple smaller batches (1,000 to 5,000 rows) rather than one large batch. Smaller batches place fewer demands on resources. Also, when using smaller batches, the fixing of problems is simpler. If a batch is not imported correctly, it is easier to isolate the condition, correct it, and rerun the batch.
10 Verify results. EIM provides several diagnostic tools that let you verify the success of import processing. You must test and run the import process and verify the results for each batch you are importing.
17. What are the possible IF_ROW_STAT values after import?
AMBIGUOUS: There are two rows in the base table that have the same user key but different conflict IDs. EIM cannot distinguish these rows
DUP_RECORD_EXISTS: The row exactly matches rows that already exist in the destination tables.
DUP_RECORD_IN_EIM_TBL:
The row was eliminated because it is a duplicate (has the same user key) of another row in the EIM table with the same batch number. In this case, MIN(ROW_ID) is the record processed, and the other records with the same
user key are marked as UP_RECORD_IN_EIM_TBL.Do not confuse DUP_RECORD_IN_EIM_TBL with UP_RECORD_EXISTS. DUP_RECORD_EXISTS status indicates that the same record already exists in the base table, while DUP_RECORD_IN_EIM_TBL status indicates that there are two or more EIM table records having the same user key values.
FOREIGN_KEY:
A required foreign key column in the target table could not be resolved.
IMPORTED:
The row was successfully processed against all its destination base tables. This status is set after the import has been completed. You can check the import status by using database commands to query the appropriate EIM tables for rows whose IF_ROW_STAT value is not equal to IMPORTED. The result is a list of rows that were not successfully imported.
IMPORT_REJECTED:
A user-specified filter query failed for this row.
IN_PROGRESS:
If rows still have this status value after EIM exits, a failure occurred that aborted processing for this table.
PARTIALLY_IMPORTED:
The row did not fail for the target table (although it may have been a duplicate), but did fail during processing of a secondary base table. This status is set after the import has completed.
PICKLIST_VALUES:
A required picklist value in the target table could not be resolved.
REQUIRED_COLS:
One or more required columns for the target table were NULL.
ROLLBACK:
EIM encountered an error, such as an SQL database failure, and rolled back the transaction. This status is only used when ROLLBACK ON ERROR = TRUE.
SQL_ERROR:
An SQL error occurred during an attempt to import this row. This error occurs for rows processed when transaction logging is set to TRUE.
18.What is Export Process?
To export data, EIM reads the data in the Siebel database tables and places the information in the appropriate EIM tables. You can then copy data from the EIM tables into another database. The export process generally populates the applicable EIM table with a row for every Siebel base table row encountered. As a consequence, where EIM tables have mappings to multiple Siebel base tables, one export operation can generate multiple rows within the EIM table governing the rows encountered within the Siebel base tables.
19.what are the tasks eim perform in export process?
A. EIM initializes the EIM tables for export.
B. It applies filter logic to select rows for exporting.
C.EIM updates EIM table rows to indicate the export status.
20.write step for export?
1 EIM initializes EIM tables for export.
If CLEAR INTERFACE TABLE in the configuration file is TRUE, all rows with the specified batch number are deleted. Otherwise, a warning is issued if rows already exist with the specified batch number. The default configuration file is default.ifb.
2 It uses export parameter expressions in the configuration file to locate and export table rows:
A. If EXPORT ALL ROWS is TRUE, ignore any EXPORT MATCHES parameters and export all rows.
B.If EXPORT ALL ROWS is FALSE; use EXPORT MATCHES parameters to locate specific rows.
Set IF_ROW_STAT to EXPORTED for rows that are successfully exported.
3 For parent tables, EIM locates child table rows and exports them to their corresponding EIM tables.
21.what are the parameters for export process?
ATTACHMENT DIRECTORY:
(Default is SIEBEL_HOME\OUTPUT) Specifies the directory to be used for exporting attachments. Before specifying a directory, make sure the directory exists on a Siebel Server machine and you have read and write access to it. Example: ATTACHMENT DIRECTORY = SIEBEL_HOME\OUTPUT If the export of an attachment fails, the export process continues and EIM writes a message in the trace file.
CLEAR INTERFACE TABLE:
Specifies whether existing rows in the EIM table for the given batch number should be deleted. The default value is TRUE.
EXPORT ALL ROWS:
Specifies that all rows in the target base table and secondary tables are to be exported. The default value is FALSE. Existing values in the EIM table and export matches expressions are ignored. For all columns to export using an EIM table (both data from the base table and data from related child tables), you need to make sure this parameter is set to TRUE (you may need to add this line if it does not currently exist) in the .IFB file. Note: Rows from child tables of related child tables are not exported until they have been mapped.
EXPORT MATCHES WHERE clause fragment. Example: EXPORT MATCHES=(NAME LIKE .GEN%.)
22.IFB file for Export All Rows?
[Siebel Interface Manager]
USER NAME=”SADMIN”
PASSWORD=”SADMIN”
PROCESS=Export Accounts
[Export Accounts]
TYPE = EXPORT
BATCH = 2
TABLE = EIM_ACCOUNT
EXPORT ALL ROWS = TRUE
23. IFB file for Export Matches?
[Siebel Interface Manager]
USER NAME=”SADMIN”
PASSWORD=”SADMIN”
PROCESS=Export Accounts
[Export Accounts]
TYPE = EXPORT
BATCH = 2
TABLE = EIM_ACCOUNT
EXPORT ALL ROWS = FALSE
EXPORT MATCHES=(NAME LIKE .GEN%.)
24.How does Check Export Result?
A. Query the appropriate EIM tables for rows whose IF_ROW_BATCH_NUM equals the batch number for the export.
The value of IF_ROW_STAT should be EXPORTED.
25.what are task for delete process?
1.EIM initializes the EIM tables for deletion.
2. It applies filter logic to do one of the following:
a) Select rows for deleting
b) Insert EIM tables rows that correspond to matching base table rows
c) Select rows with matching user keys in the EIM tables
3. EIM updates other tables with rows containing foreign keys that point to newly deleted rows.
26.write step for delete process?
1. EIM initializes EIM tables for delete.
If CLEAR INTERFACE TABLE in the configuration file is TRUE, all rows with the specified batch number are deleted. CLEAR INTERFACE TABLE must be FALSE for a delete process that uses EIM table values to identify rows for deletion.
2. EIM deletes rows.
a If the DELETE EXACT parameter in the configuration file is set to TRUE, EIM deletes the rows
from the table that match the user key defined in the EIM table.
b If the DELETE MATCHES parameter in the configuration file is set to a base table, EIM deletes the rows from the target base table that match the predicate specified in the parameter.
c If the DELETE ALL ROWS parameter in the configuration file is set to TRUE, EIM deletes all rows from the target base table.
3 .EIM sets IF_ROW_STAT to DELETED for rows that are successfully processed.
a) When a foreign key column that references the deleted record is a required one, the record with the foreign key is deleted. Otherwise, the foreign key column is cleared.
27. What are the parameters for Delete process?
CASCADE DELETE ONLY (Default = FALSE). Set this parameter to TRUE to delete child records with nullable foreign keys when the parent record is deleted. If FALSE, then when EIM deletes a parent record, it sets the foreign keys of the child records to NULL.
CLEAR INTERFACE TABLE
This parameter specifies whether existing rows in the EIM table for the
given batch number should be deleted. Valid values are true (the default unless DELETE EXACT = TRUE) and false (the default if DELETE EXACT = FALSE).
DELETE ALL ROWS
Used for deleting all rows in table; default is FALSE.
DELETE EXACT
Delete using user key matching algorithm with rows in EIM table
DELETE SKIP PRIMARY
This parameter specifies whether EIM should perform a cascade update to the primary child column. The default value is TRUE.
DELETE MATCHES
SQL WHERE fragment deletion criteria. Example: DELETE MATCHES = EIM_ACCOUNT, (NAME LIKE .TST_ACCT%.).
DELETE ROWS
This parameter specifies whether rows from the target base table can be deleted. Valid values are TRUE (the default) and FALSE. This parameter can prevent deletions from one table while allowing them in others. For example, the following parameter setting prevents deletion
of rows from the S_ADDR_ORG table:
DELETE ROWS=S_ADDR_ORG, FALSE
IGNORE BASE COLUMNS
Specifies base table columns to be ignored by the import process. Use commas to separate column names, which can be qualified with base table names. Required and user key columns cannot be ignored. Use this parameter to improve performance when updating all but a few Columns. The default is to not ignore any base table columns.
UPDATE ROWS:
Specifies whether foreign key references can be updated. This parameter can be used to prevent the updating of foreign key references with a setting of FALSE. The default value is TRUE, which affects all tables. To affect only specific tables, you can specify a table name. For example:
UPDATE ROWS = S_CONTACT, TRUE
The UPDATE ROWS parameter also prevents updates in one table while allowing them in others. If this parameter is set to FALSE, EIM does not update rows in the specified base table. If you need to specify multiple tables, use one UPDATE ROWS statement for each table.
Inappropriate use can result in dangling foreign key pointers.
28. Write ifb file for delete all rows?
[Siebel Interface Manager]
USER NAME=”SADMIN”
PSSWORD=”SADMIN”
PROCESS=Delete Accounts
[Delete Accounts]
TYPE = DELETE
BATCH = 200
TABLE = EIM_ACCOUNT
DELETE ALL ROWS = TRUE
29.How do Check delete results in eim table?
Query the appropriate EIM table for rows whose IF_ROW_BATCH_NUM equals the batch number for the delete. The value of T_DELETED_ROW_ID identifies deleted rows.
30. Write step for delete process using delete exact parameter?
A. Populate the following columns in the EIM table (such as user keys for the S_ORG_PROD table and all the special interface columns):
ACCNT_NAME, ACCNT_LOC, INS_PROD_NAME, INS_PROD_VENDR, INS_PROD_VENDR_LOC, INS_DT, ROW_ID, IF_ROW_BATCH_NUM, IF_ROW_STAT, ROW_ID.
B.Add or modify the following process section in your .IFB file:
TYPE = DELETE
BATCH NUMBER =
TABLE = EIM_ACCOUNT
ONLY BASE TABLES = S_ORG_PROD
DELETE EXACT=TRUE
C.Run EIM.
This deletes all rows from the S_ORG_PROD table that have user keys that match the rows in your EIM table.
31. What are the tasks for merge process?
A. Initialize the EIM tables for merge.
B. Initialize the EIM tables for merge.
C. Merge child rows into the replacement rows. EIM then deletes rows from the target base table that are specified in the EIM table.
1. For deleted rows, EIM sets T_MERGED_ROW_ID to the ROW_ID of the row that was merged into (the surviving row).
2. EIM sets T_DELETED_ROW_ID to the ROW_ID of the deleted base table row.
D.Update child rows containing foreign keys that point to newly deleted rows. For base tables that have foreign keys in newly deleted rows, EIM updates the foreign keys to point to surviving rows (depending on the value for UPDATE ROWS in the configuration file).
32. Write ifb file for merge process?
[Siebel Interface Manager]
USER NAME=”SADMIN”
PSSWORD=”SADMIN”
PROCESS= Merge Accounts
[Merge Accounts]
TYPE = MERGE
BATCH = 1
TABLE = EIM_ACCOUNT
UPDATE ROWS = TRUE
33. List parameter for merge process?
SET BASED LOGGING
Specifies whether set-based logging is enabled. The default value is TRUE.
NOTE: EIM will ignore this parameter if Docking Transaction Logging is
set to FALSE in the System Preferences view
UPDATE ROWS
Specifies whether the foreign key (or keys) that reference the merged rows in the named table need to be adjusted. Valid values are TRUE (the default) and FALSE.
NOTE: Use the UPDATE ROWS = Table_Name, FALSE setting carefully. Inappropriate use can result in dangling foreign key pointers.
34. How do check merge results in eim table?
1 Query the appropriate EIM table for rows whose IF_ROW_BATCH_NUM equals the batch number for the merge process.
2 Inspect the values of T_DELETED_ROW_ID and T_MERGED_ROW_ID.
35. List required column for merge process in eim table?
ROW_ID, IF_ROW_BATCH_NUM,IF_ROW_STAT,IF_ROW_MERGE _ID
36. Why we give sql trace flag 8 i?
Setting the SQL Trace Flags parameter to 8 creates a log of all SQL statements that make up the EIM task.
37. What is purpose for give trace flag 1,2,4,8,32?
Trace Flag 1
Setting the Trace Flags parameter to 1 creates a step-oriented log of the task. This can be used to determine the amount of time EIM spends on each step of the EIM task, or for each EIM table processed.
Trace Flag 2
Setting the Trace Flags parameter to 2 creates a file log that traces all substitutions of user parameters.
Trace Flag 4
Setting the Trace Flags parameter to 4 creates a file log that traces all user-key overrides.
Trace Flag 8
Setting the Trace Flags parameter to 8 creates a file log that traces all Interface Mapping warnings.
Trace Flag 32
Setting the Trace Flags parameter to 32 creates a file log that traces all file attachment status.
38. What is purpose for give error flag 1?
Setting the Error Flags parameter to 1 produces a detailed explanation of rows that were not successfully processed.
39. Step for running for eim process using graphical user interface?
During this step data is imported from eim table to base table.
1.navigate to Administration - Server Management >jobs
2.add new record. In the Component/Job field, click the select button, and in the Component/Jobs window, select the Enterprise Integration Mgr component.
3. Job parameter list applet add a new record. Give value for name field and value field
4click Start button, now status Queued
5.click query and go button until status Success
40. Write the guidelines for improve performance in eim?
Verify that all indexes exist for the tables involved. Keep in mind, however, that for large loads you should drop most of the indexes from the target tables to increase the speed of the process, rebuilding those indexes afterward when the process is finished. Limit tables and columns to be processed using ONLY BASE ABLES/COLUMNS configuration parameters to minimize EIM processing. Consider switching off transaction logging during the EIM run. This improves performance. However, the performance benefit must be balanced with the need for mobile users to reextract afterward. Altering batch sizes to find the optimal batch size for a given business component typically helps resolve performance issues. The batch size is dependent upon the quantity of data and which type of EIM process you are running. For EIM delete processes that use the DELETE EXACT parameter, use a batch size of 20,000 rows or less. Try using batch ranges (BATCH = x.y). This allows you to run with smaller batch sizes and avoid the startup overhead on each batch. The maximum number of batches that you can run in an EIM process is 1,000.Perform regular table maintenance on EIM tables. Frequent insert or delete operations on EIM tables can cause fragmentation. Consult your database administrator to detect and correct fragmentation in the EIM tables. Delete batches from EIM tables on completion. Leaving old batches in the EIM table wastes space and could adversely affect performance. Run independent EIM jobs in parallel Set USING SYNONYMS parameter to FALSE in the .IFB file to indicate that account synonyms do not need to be checked.If no other strategy appears to be successful, use the SQLPROFILE parameter to identify slow-running steps and queries
No comments:
Post a Comment