Data Export with EIM - An Overview
Exporting data with EIM involves a process where EIM accesses data stored in Siebel database tables and transfers it to the relevant EIM tables. Typically, this export operation creates entries in the appropriate EIM tables for each row encountered in the Siebel base tables. In cases where EIM tables are associated with multiple Siebel base tables, a single export can lead to various entries within the EIM table, reflecting the rows from the corresponding Siebel base tables. Throughout these processes, EIM performs several critical tasks, including initializing the EIM tables for export, applying filters to select specific rows for export, and updating EIM table rows to indicate their export status.
The EIM Export Process Unveiled
The process of exporting data to EIM tables through EIM involves a series of well-defined steps:
Initialization of EIM Tables for Export:
EIM starts the export operation by initializing the EIM tables designated for export. Depending on the configuration file settings, if the "CLEAR INTERFACE TABLE" parameter is set to TRUE, all rows associated with the specified batch number are removed. Alternatively, suppose this parameter is set to FALSE. In that case, a warning is issued if rows with the same batch number already exist.
Application of Export Parameter Expressions:
EIM utilizes export parameter expressions defined in the configuration file to identify and export rows from the target tables. When the "EXPORT ALL ROWS" parameter is set to TRUE, EIM disregards any "EXPORT MATCHES" parameters and exports all available rows. Conversely, when "EXPORT ALL ROWS" is set to FALSE, EIM relies on the "EXPORT MATCHES" parameters to pinpoint specific rows for export. Furthermore, EIM goes a step further for parent tables by locating and exporting child table rows to their corresponding EIM tables, ensuring comprehensive data transfer.
Preparing EIM Tables for Export
Effortless Table Preparation: Getting your EIM tables ready for export is a relatively straightforward task that doesn't require extensive preparation. EIM takes the lead here by carefully examining each EIM table involved. Suppose it detects a row with an IF_ROW_BATCH_NUM that matches the designated batch number for export. In that case, it proceeds based on the configuration settings:
Clearing or Warning: Depending on your EIM configuration, if "CLEAR INTERFACE TABLES" is set to TRUE, EIM will clear out the row. In contrast, EIM will warn about the existing rows if it's set to FALSE.
Verifying Batch Numbers
Check Existing Rows Before Export: Before initiating an export process, verifying whether any existing rows possess an IF_ROW_BATCH_NUM corresponding to the batch number you intend to use is crucial. If such rows exist, you have a couple of options. You can ensure they don't contain essential data or adjust the batch number to align it with your export process. Additionally, setting the IF_ROW_STAT column to FOR_EXPORT for the rows you plan to export is advisable.
Consistency in Column Values: In EIM tables, you'll notice a consistent pattern - the values in the LAST_UPD and CREATED columns always mirror those found in the corresponding base table's LAST_UPD and CREATED columns. For instance, if you're using the EIM_CONTACT interface table to export data from the S_CONTACT and S_ADDR_PER base tables, the values in EIM_CONTACT.LAST_UPD and EIM_CONTACT.CREATED will align precisely with the data in S_CONTACT.LAST_UPD and S_CONTACT.CREATED, respectively.
Unsupported EIM Tables for Export
Complexity Limitations: Certain EIM interface tables are not supported for export processes due to the complexity of their associated base tables. These interface tables include EIM_ACCSRCPIDTL, EIM_CRSE_TSTRUN, EIM_IC_CALC, EIM_IC_PERF_HST, and EIM_MDF.
Configuring for Export
Crucial Configuration: To embark on a successful data export journey, it's imperative to fine-tune the EIM configuration file. Specifically, you must define at least one process with the TYPE = EXPORT to initiate and manage your export process effectively. This configuration step lays the foundation for seamless data export with EIM.
Critical Parameters for Export Configuration
Attachment Directory: This parameter typically points to the default directory, SIEBEL_HOME\OUTPUT, which specifies the location for exporting attachments. For instance, you can set it as ATTACHMENT DIRECTORY = SIEBEL_HOME\OUTPUT (for Windows).
Clear Interface Table: Determined by the setting of this parameter, EIM decides whether to delete existing rows in the EIM table associated with the designated batch number. The default value is TRUE.
Export All Rows: When set to TRUE, this parameter indicates that all rows from the target base table and secondary tables should be included in the export. The default setting is FALSE. If EXPORT ALL ROWS is set to TRUE, any existing values in the EIM table and export match expressions are overridden. To ensure all columns are exported from an EIM table, encompassing data from both the base table and related child tables, consider adding this line to the.IFB file if it's not already present, as shown here: EXPORT ALL ROWS = TRUE.
Customizing Export Criteria with Export Matches
Export Matches: This parameter empowers you to define a WHERE clause expression for filtering base table rows during export. The value comprises the Siebel EIM table name and the filter expression applied to the target base table. The term functions as a self-contained WHERE clause (excluding the WHERE keyword). It should exclusively employ literal values or unqualified column names from the base table. It's crucial to maintain a space between the operator and the operand.
Syntax for EXPORT MATCHES with S_PARTY as the Target Base Table:
To extract all data rows from tables mapped within an EIM table, activate the EXPORT ALL ROWS parameter by setting it to TRUE, as exemplified below.IFB file:
[Export Accounts] TYPE = EXPORT BATCH = 2 TABLE = EIM_ACCOUNT EXPORT ALL ROWS = TRUE
Comments
Post a Comment