A merge process deletes one or more existing rows from the base table and ensures that intersecting table rows are adjusted to refer to the remaining rows. Some process parameters like TYPE, BATCH and TABLE are similar to that in case of the above mentioned processes. Upon completion of the merge process, the some row survives and the remaining rows are deleted.
Some process parameters like TYPE, BATCH, and TABLE are similar to an Import process.
DELETE ROWS: For Delete process the TYPE parameter should be defined as TYPE = DELETE. As a result the DELETE ROWS parameter will be automatically set to TRUE. This parameter can prevent deletions from one table while allowing them in others. For example, the following parameter prevents deletion of rows from the S_ADDR_PER table:
DELETE ROWS = S_ADDR_PER, FALSE
Some process parameters like TYPE, BATCH, and TABLE are similar to an Import process.
EXPORT ALL ROWS: It implies that all rows in the target base table and data from the related child tables in a specific batch section are to be exported. Valid values are TRUE and FALSE (the default). When it is set to TRUE, the EXPORT MATCHES parameter is ignored, as it is selective export process.
TYPE: This parameter specifies the type of process being defined (IMPORT, EXPORT, DELETE, MERGE, or SHELL). A shell process uses the INCLUDE statement to invoke a sequence of processes in a single run.
An IFB file consists of two main sections namely:
Header Section: The .ifb file begins with a header section to specify global parameters that apply to all process sections.
Process Section: Following the header section, there must be at least one process section with its associated parameters. Some process section parameters are generic for all EIM processes ‘Type’, ‘Process Name’, ‘Batch Number’, ‘EIM Table Selection’ etc.
An IFB file is nothing but a EIM configuration file which is an ASCII or Unicode (Binary) text file of extension type .ifb. IFB stands for Interface Batch. It resides in the Admin directory of Siebel Server and allows the database administrator to define the type of EIM process like Import, Export, Merge and Delete to be performed.
Why IFB is needed?
The 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. The EIM tables act as a staging area between the Siebel application database and other databases.
1. Create a new BC based on the Class CSSBCVExtern.
2. Do not associate any tables to this BC since VBC are not based on an underlying table but rather is based on a Business Service.
3. Create the fields associated with VBC.
4. The field names must exactly match the name of the columns of the table that this VBC will reference.
5. Do not specify column or type for the fields.
Total No. of Questions: 20
Time Duration : 30 Minutes
Answers are highlighted in Bold Green.
ABS Additional Billing Service Fee
Fee assessed when installment premium is billed.
ADC Add Coverage
Additional premium due for adding coverage(s) to a property.
