Siebel 7.0.

3 Seibel Configuration
________________________________________________________________________

SIEBEL TOOLS
CONFIGURATION GUIDE

e Business Applications
VERSION 7.0
10MK1-MS00-07000

January2004

________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

PickList

A static PickList is a selection list that is invoked from a particular text box or list
column in an applet. Dynamic Picklists draw values from other business components and
display those values in an applet that can contain multiple columns and buttons.
Static Picklists draw their values from the list of values table and display those values
in simple one-column lists. The values displayed in a static PickList are defined by an
administrator. Static Picklists can be bounded or unbounded.
Bounded Picklists force the user to select a value from the list. Unbounded Picklists
allow users to select a value from the PickList or type a value into the field.
Static Picklists draw their values from a table that is called the List of Values Table
(S_LST_OF_VAL). The values displayed in static Picklists are the values stored in the
Display Value column of the LOV table. When a user selects a value from a PickList, the
display value is the value that populates the field in the user interface and the column in the
base table. Pick lists are used to standardize data entry and minimize mistakes.

Steps for creating a Static Picklist

Step 1: First determine the field to which we are going to add PickList and in
what applet it belongs to and what field in BC it refers.
Step 2: Then create the LOV type for the PickList this is done by navigating
to Application Administration -> List of Values Explorer.
Step 3: Then add values for the PickList in the type by selecting Application
Administration -> List Of Values
Step 4: Create a new Picklist Object Definition
Specify Name, Project, BC=Picklist Generic, Static, Bounded, Type
Field, and Type Value = Name of the LOV type.
Step 5: Navigate to the BC -> SVF then select the corresponding field and
specify the Picklist Name

________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

Step 6: select the SVF PickMap create a new record and specify the Field =
the field for which we are adding a PickList and Picklist Field.
Step 7: Compile and Test.

What is a dynamic drilldown?

Enables hyperlink navigation to multiple views from the same hyperlink field,
depending on the value of a field in the applet’s current record. Siebel checks the value of
the field in the current record and navigates to the view based on the found value.

Steps for Creating a Static Constrained PickList

Create the First Picklist Using the Steps explained above. Then create the next one
using the following steps.
Step 1: Create the LOV type by navigating to the Application Administration
-> List of Values Explorer.
Step 2: Create Values for the Picklist by navigating to Application
Administration -> List of Values. Specify Type, Display Value, and
Description = the value of the another Picklist from which u are
going to constrain the current Picklist and Language Independent
Code.
Step 3: Create the Picklist Object Definition.
Step 4: Navigate to the BC -> SVF then select the corresponding field and
specify the Picklist Name
Step 5: select the SVF PickMap and create a new record and specify the Field
= the field for which we are adding a Picklist and Picklist Field =
Value.
Step 6: Create another record Specify Field = Name of the field from which
u are going to constrain the Picklist and Picklist Field = Description.

________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

Steps for Creating Hierarchical Picklist

The hierarchical Picklist is in which the LOV type for the Picklists we are going to
use is same for all.

Step 1: Create a LOV type by navigating to the Application Administration -

> LOV Explorer.
Step 2: Navigate to Application Administration -> List Of Values and first
create one more reference values which is used to display values in
our parent Picklist.
Step 3: Enter Values for all other Picklists and Specify in the Parent LIC for
that one.
Step 4: Then create the Picklist Object Definition for the parent Picklist.
Step 5: Then create the Picklist Object Definitions for the child Picklists.
Step 6: Navigate to BC -> SVF and Specify the Picklist for the Parent Field.
Step 7: Then navigate to SVF PickMap and create a new record Specify Field
and Picklist Field.
Step 8: Then create a dummy field in the BC and in its PreDefaultValue
Field Specify Expr: 'Lookup Value ("SR_AREA", "External")'
Step 9: Create a record in SVF PickMap Using this Field Name and Picklist
Field = Parent and constrain it. Then create the record with the field
in which child Picklist is going to be placed and specify the Picklist
Field = Dummy.
Step 8: Navigate to Child Picklist Field and Specify the Picklist and create a
Field in the BC Specify Name, Calculated = True and Calculate Value
= [Name of the Parent Picklist Field].
Step 7: Navigate to SVF PickMap and create three records. In first Specify
Field, Picklist Field = Value. In second Specify Field = Name of the
Calculated field Created by you and Picklist Field = Parent. In
third record Specify Field = Name of the field contain the parent
Picklist and Picklist Field = parent.
________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

Step 6: Compile and Test.

Steps for Creating Dynamic Picklist

Step 1: First Determine the Field, Applet and BC for which we are going to
add a dynamic Picklist.
Step 2: Create the Picklist Object Definition and Specify Name, BC, and
Project.
Step 3: Create the Pick Applet for the Picklist. (Account Picklist Applet)
Step 4: Select BC-> SVF and Specify the PickList for the Field.
Step 5: Create SVF PickMap and Specify Field and PickList Field = the field
form which we are going to assign the value for the field.
Step 6: Select the Applet on which the Field appears and specify the Pick
Applet and set Runtime = True.
Step 7: Compile and Test.

Steps for Creating Constrained Dynamic Picklist

Step 1: First Create the Picklist from which you are going to constrain the
PickList.
Step 2: Then create the second Dynamic Picklist Similarly.
Step 3: Then in the SVF PickMap add another record with Field=Field in
which the first Dynamic PickList stay and Picklist Field.

What is a dynamic drilldown?

Enables hyperlink navigation to multiple views from the same hyperlink field,
depending on the value of a field in the applet’s current record. Siebel checks the value of
the field in the current record and navigates to the view based on the found value.

________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

Static Drilldown

Enables hyperlink navigation to the same view which may be corresponds to the
same BC or another BC.

Step 1: First Determine the column to which you are going to produce
drilldown and it belongs to which applet and which BC.
Step 2: Select the Applet Object Definition from tools and desire to which
will the hyperlink takes to you.
Step 3: Then select the Drilldown Object and select the new record and then
specify Name, Hyperlink Field and View.
Step 4: Compile and Test. (This will always navigate to the same view in the
same BC)

Step 1: First Determine the column to which you are going to produce
drilldown and it belongs to which applet and which BC.
Step 2: Select the Applet Object Definition from tools and desire to which
will the hyperlink takes to you.
Step 3: Then select the Drilldown Object and select the new record and then
specify Name, Hyperlink Field, and Source Field = FK Field in the
record pointing to target BC Destination Field = PK field in the
target BC, BC and View.
Step 4: Compile and Test. (This will always navigate to the same view in
another BC).

Steps for creating Dynamic Drilldown

Step 1: Select the Applet Object Definition and select the corresponding
Applet.
Step 2: Create the Drilldown Object Object Definitions for the desired
Applet.
________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

Step 3: Create the Destination Drilldown Object Object Definition for each
type of values. Specify Name = Name of the Drilldown Object,
Field, Value = Type Value, and Destination Drilldown Object =
Name of the Drilldown Object.
Step 4: Compile and Test.

Toggling

Toggling allows to configure several applets to share the same place in a view. We
can add only one applet in the view web template. Users can switch this one with others by
an applet toggle that we define in the applet object definition.

Static Toggling

Step 1: Select the Applet Object Definition.

Step 2: Select Applet Toggle and Create a new record specify the name of
the applet. We can add as many as records the web template allows.

Dynamic Toggling

Step 1: Select the Applet Object Definition.

Step 2: Select Applet Toggle and create a new record specify the name of the
applet, Auto Toggle Field and Auto Toggle Value. (Child applets
must be based on the same BC as parent).

Create a view

Step 1: Create a new view object definition and specify name, project,
Business Object and View title.
________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

Step 2: Add a view web template object definition to the view as Name ,
Web Template.
Step 3: Bind Applets to the Web Template.
(a) Launch the web layout editor
(b) Drag the applets from the applet window to the placeholders in
the web view editor (the applets will appear in the view web
Template Item) Important Properties are Name, Item Identifier,
Applet Mode. Default Mode is Base .Set the appropriate mode.
Step 4: Configure the thread Bar. Edit the view Object definition and set the
display text for thread bar (thread title, thread field, thread applet).
Step 5: Assign the view to a screen. Select screen --> Screen View. Set the
Menu Text (Appears in the Sitemap) and View bar text (Appears in
the Show drop down list).
Step 6: Registering a view. To register navigate to Application
Administration --> Views
Step 7: To assign navigate to Application Administration-->Responsibilities.

(Views can be accessed through show drop down list or view tab)

Create a List Applet through wizard

Step 1: Navigate to File--> New Object and Select List Applet.

Step 2: Page 1: Assign (a) Project, (b) BC, (c) Name and (d) Title.
Step 3: Page 2: Select web templates for the web layout. It associates applet
and template.
Step 4: Page 3: Choose the BC fields that will Appear in the web Layout
(creates the Applet web template Items).
Step 5: Page 4: Choose the HTML controls appears in the applet (This
comes from Model HTML Controls Applet).

________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

Step 6: Review and Click Finish. This will create the required object
definitions for the (a) Applet, (b) Controls, (c) List, (d) List Columns
and Maps (a) Applet Web Template, (b) Applet Web Template Items
Set the Applet Class to CSSFrameList and invokes the web layout
editor.

(Show In List Property determines weather a field appears in the list

applet as first displayed

Create a Form Applet thru wizard

Step 1: File--> New Object.

Step 2: Page 1: Assign (a) Project, (b) BC, (c) Name, and (d) Title.
Step 3: Page 2: Select web templates for the web layout
Step 4: Page 3: Select fields from the BC to appear in the form applet.
Step 5: Page 4: Choose HTML controls to be added to the applet.

Step 6: Page 5: Finish the form applet wizard.

(To set the More /Less Mode Create a Toggle Layout Control and
add it using Web Layout Editor.)

Create Business Component

Step 1: Specify Name, C++ Class as C++BusComp and Table (Base).

Step 2: To map the columns in the base table (editable). (a) Create a SVF and
(b) Leave the join Property empty.
May include data from additional related tables (joined) (read only). Join table
provide out related row for each row in the base table. Have M: 1 or 1:1 relationships
with the joined tables. FK is in the base table.
________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

To Add Columns form Joined Tables

Step 1: Select the Business Component and select join and specify (a) Alias,
(b) Table, and (c) Outer Join Flag.
Step 2: Select Join Specification and specify (a) Name (b) Source Field (FK
to the joined table), (c) Destination Field (PK of the joined table).
Step 3: Create a SVF and specify (a) Name, (b) Join.

To add the column from the extension table

Step 1: Select BC and then Create SVF.

Step 2: Specify Name and Join= Name of the Extension table.

To bring the Party data into non-Party BC

Step 1: Create a Join definition specify Alias, and Table.

Step 2: Crate Join Specification definition and specify (a) Name, (b) Source
Field (FK to the joined table), (c) Destination Field
(PAR_ROW_ID).

To bring the Party data into Party BC

Step 1: Create a Join definition specify Alias, and Table. (Generally we

provide the Alias name as the name of the joined table. But here we
have to provide the different name for it. Because the implicit join
for that joined table already exists.)
Step 2: Crate Join Specification definition and specify (a) Name, (b) Source
Field (FK to the joined table), (c) Destination Field
(PAR_ROW_ID).
________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

Link

Specifies which records to retrieve from the child BC. Have 1: M or M: M

relationship between the parent and child business components. FK to the relationship is in
the child table.

Create Link for 1: M relationship

Step 1: Select the Link Object Definition in Tools.

Step 2: Specify Project, Child BC, Parent BC, Name, and Source Field =
Primary key of the parent BC and Destination Field = FK in the
Child BC.

Create Link for M: M relationship

Step 1: Select the Link Object Definition from Tools.

Step 2: Specify Project, Parent BC, Child BC, and Name, Inter Table, Inter
Parent Column and Inter Child column and Inter Child Delete. (FK
for the relationship are in the Inter table).

Link

. A link implements a one-to-many relationship between business components. The

Link object type makes master-detail views possible. A master detail view displays one
record of the master business component with many detail business component records
corresponding to the master. A pair of links also may be used to implement a many-to-many
relationship.

Multi-Value Link

________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

. A multi-value link is used in the implementation of a multi-value group. A multi-

value group is a user-maintainable list of detail records associated with a master record. The
user invokes the list of detail records from the master record when it is displayed in a list or
form applet. For example, in an applet displaying the Account business component, the user
can click an ellipsis icon to the right of the Address text box to see a popup window
displaying multiple Address records associated with the currently displayed account.

Join

A join object definition creates a relationship between a business component and a

table that is not the business component's base table. The join allows the business
component to build fields using columns from the non-base (joined) table. The join uses a
foreign key in the business component to obtain rows on a one-to-one basis from the joined
table, even though the two do not necessarily have a one-to-one relationship.

Steps for Creating a Multi Value Group

A multi value group is a set of detail records associated with a
parent record. Parent displays only one of the child records. On request
MVG Applet displays all child records.
Multi-value field
Is a field in the parent BC that references the field in the child BC.
The multi-value field provides access to a corresponding field value in the current
record of the detail business component. The control or list column that displays the multi-
value field normally will be able to invoke a multi-value group applet for display and
maintenance of the detail records.
Multi-value link

________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

The multi-value link provides access to the set of records in the detail business
component. One multi-value link is created for each multi-value group that is created using
the one-to-many extension table.
Step 1: Identity the Parent and Child BC and determine the relationship
between them.
Step 2: Check if there is an existing link between them if not create a new
link.
Step 3: Create a Multi Value Link for the BC. Specify Name, Destination BC
and Destination Link.
Step 4: Create a Multi Value Field Object Definition. Specify Name, Multi
Value Link and Field.
Step 5: Identify or create a Multi Value Group Applet.
Step 6: Enable primary for performance.
Step 6: Enable user to invoke the MVG Applet. Add the MVF in the applet
and specify the MVG Applet and set Runtime = True.
Step 7: Compile and Test.

Setting Up Primary for MVG

Primary refers to the designated child record. To improve performance use a FK in
the parent record that points to the primary child record. Creates an M: 1 relationship
between parent and primary child record. Allows a single query using a SQL join to retrieve
the parent and primary child record to display in the applet. When primary is used in MVF
one query is used to return date for all records in the list applet.

Step 1: Select the base table of the parent BC and query for PR_* in the
Column property.
Step 2: Select the column which has the Foreign Key Table value as the base
table of the child BC.
Step 3: Add this field in the parent BC and specify the Name as primary.
Step 4: Set the Primary Id Field and Use Primary Join flag in the MVL.

________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

Step 5: Set the Auto Primary property of MVL to Default. It sets the first
record as primary.
Step 6: Add the SSA Primary Field to MVG Applet to display a special field
to permit the user to see and change the primary child record.

EIM- (ENTEPRISE INTEGERATION MANAGER)

`Installation Populates seed data and repository data only .User data should be
populated and managed by ourselves. We can enter, Update, or delete small amounts of data
directly in the base tables using the client application. In order to enter large amounts data
EIM is used. EIM manages the exchange of data between Siebel database and other
corporate database. EIM Performs Bulk
(a) Imports, (b) Exports, (c) Merges, (d) Deletes.

Interface Tables
Siebel Interface tables are an intermediate table that acts as a staging area between
Siebel application DB and other DB Types: (a) S_type, (b) EIM_type

S_type
(a) Are used in release prior to 6.x.
(b) Identifies by S_ prefix and _IF suffix.
(c) Since it doesn't support organization, so it only be used to import data using
EIM.
(d) Can't be used for other operations
(e) Are provided for background compatibility only.

EIM_type
(a) Can add organizations to our implementation.
(b) Export, delete, or merge
(c) Set explicit primaries.
________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

Interface Table Columns

To process on a row-by-row basis, EIM uses several columns common to every interface
table. They are.
(i) ROW_ID.
(ii) IF_ROW_STAT.
(iii) IF_ROW_BATCH_NUM.
For merge populate IF_ROW_MERGE_ID also.

ROW_ID
For an interface table row to be eligible for processing, we must initialize the row_id
generated by the EIM has ##-##-#### format. The Regular row_id assigned to the row has #-##
format.
IF_ROW_BATCH_NUM
Set the values to >=0 used as a identifying number for all rows to be processed as a batch.
Max. Value 2147483647
IF_ROW_MERGE_ID
Used during the merge process
IF_ROW_STAT
EIM updates this column after processing a new row to indicate the status of the record.
Used by EIM to determine which row to process .set this column to any value except NULL .Initially
FOR_IMPORT to indicate the row have not been imported.
After processing certain rows were not imported due to data error ,we should change, (a)
IF_ROW_BATCH_NUM values for rows that require re importing and (b) 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.

IF_ROW_STAT_NUM
Contains (i) zero if a row wad successfully processed to completion.
(ii) Pass Number where the pass failed.
Temporary columns
An Interface table has T_ Columns used to hold temporary values and status used during
processing.

________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

File Attachment Column

The Interface table columns must be populated in order to import file attachment. The
column used in
(i) FILE_NAME.
(ii)FILE_EXT (DOL, XLS or TXT).
(iii)FILE_SRC_TYPE (Value "FILE").
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 will look up the ROW_ID for the
organization in xxx_BU and put it in the corresponding xxx_BI column.

Interface Table and Column Mapping

EIM uses interface table mappings to map column from interface tables to Siebel
base tables. Siebel predefined EIM mappings are predefined and cannot be remapped. Using
Siebel tools we can view
(a) Interface table mapping to Siebel base table
(b) Interface column mapping to Siebel base column
(c) Siebel base table mapping to interface table

Data Mapping determines

(1) Which Siebel table column will store external source data?
(2) Which EIM column will be used to import from source to destination
Step1: Analyze Source data
(a) Which attributes need to be stored?
(b) Which entity does the collection of attributes represents.
(c) What relationship does the entity have to other entities?
Step2: Analyze Siebel destination tables and columns
________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

Step3: Describe how the source maps to the destination.

(i) Which Siebel BC represents the External entity.
(ii) Which base table and column will store the source attributes.
Step4: After determining source to base mappings, determine EIM to base
mappings using bookshelf or tools (EIM Table Mapping is used to determine the
EIM tables for the base Table).
Select the EIM Table that best maps to the target base table and column. Query
attribute mapping in the tools to determine which EIM column populate the base
table. Determine required base table column that don’t have defaults.
Specify Source Entity, Source Attribute, EIM Table, EIM Column, Base Table, And Base
Column.
Considerations
The additional columns that must be populated for party BCs. (PARTYA-UID, PARTY-
TYPE-CD, ROOT_PARTY_FLG).
When importing, tables referenced via FK must be loaded first.
Importing data for BC's related to organizations
(i) For the single organization, must populate BU_ID.
(ii) For multiple, must populate the corresponding intersection table

EIM accepts parameter values from three sources

(i) The DOS command line Prompt (either entered by user or read from a .bat file)
(ii)The Siebel Server manager GUI.
(iii)The Config.file if specified or default.ifb, if not specified.
Command Line Parameter overrides component parameter and component
parameter overrides cfg.file parameters. Only Exception is if batch number component
parameter is set to 0, the batch number in the EIM cfg file will be used.

Running an EIM task

(I) creates an OS process that writes log entries
(ii) Reads the .ifb
(iii) Loads the dictionary.

________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

(iv) Executes EIM steps.

EIM Configuration file

EIM reads a special configuration file that specifies the EIM process to perform (import,
merge, delete, or export) and the appropriate parameters. The EIMconfiguration file (the
default file is default.ifb) is an ASCII text file of extension type .ifb that resides in the
admin subdirectory under the Siebel Server directory.

EIM Configuration File Parameters

The EIM cfg file begins with a header section used to specify global parameters that
apply to all process section defined later in the file. Following the header section there must
be at least one process section with its associated parameters.
(i) Some process section parameters are generic for all EIM process.
(ii) Some process section parameter are specified to a particular EIM processes
General process Parameter may be used in all EIM processes and Import process
parameter may be used only in import processes.
Header Section
This Section describes the parameter that appears in the header section of the EIM
cfg.file [SIEBEL INTERFACE MANAGER]
(a)PROCESS: Identifies the specific process to run during the invocation of EIM.
(b)CONNECT: The ODBC source name for the database server.
(c)USERNAME: The database login name for this process
(d)TABLE OWNER: Database table owner, defined during installation
(e)PASSWORD: The database password for this process
(f)LOG TRANSACTIONS TO FILE: If TRUE, transactions are logged in a file or
table. By default, EIM logs transaction into files, saved in EIM sub directory in the File
system directory. If set to FALSE, transaction will be logged into a table.

Process Section
This section describes only the general process parameter generic to all EIM process
that appears in the EIM process section of the EIM config file. The first non-line blank, not
________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

comment line of the each process section is a bracketed string that specifies the name of the
process .This is the name used in the PROCESS argument or RUN PROCESS parameter in
the header section.

TYPE: Specifies the type of the process being defined.

INCLUDE: Names a Process to be included as a part of this process
BATCH: Specifies the required batch number for this process. To specify multiple batches
use
(i) Range (100-120) or
(ii) Use a comma delimited format as 100,101,102.
TABLE: Specify the name of the interface table used in this process
LOG TRANSACTIONS: If it is set to TRUE, EIM will Log changes when mobile clients
synchronize otherwise changes will not be logged.
Extended parameters
We can dynamically name, and define extended parameters
(a) User defined extended parameter
(b) Predefined extended parameters
EP's are needed to create new parameter and defined values.

Running the EIM Process

To run (a) Navigate to server Admin-->Enterprise Operations
(b) Click the Component request view Tab
(c) Create new record
(d) In the component /job field select EIM
(e) Complete the rest of fields and clicks save
(f) In the component request parameter list, add or change the any
component parameter for the list.

Error flags (0 or 1)
Default Value = 0

________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

1 is used to produce a detailed explanation of rows that were not successfully

processed.

SQL Trace Flag (0, 1, 2, 4, 8)

May have values 1, 2, 4 and 8 defaults 0. 1, 2, 4 used for logging at ODBC level.
8--> Create a log of all SQL Statements that make up the EIM task.

Trace Flags (1, 2, 4, 8, 32)

1-create the steps oriented log of task
2-creates log that traces all substitution of user parameter
4-create the log that traces all user key overrides
8-creates the log that trace all interface mappings warning
32- Creates the log that traces all file attachment status.

Values for IF_ROW_STAT

IN_PROGRESS: In Step 1, Integration Manager sets IF_ROW_STAT to this initial value
for all rows in the batch. If rows still have this status value after Integration Manager exits, a
failure occurred that aborted processing for this table.
SQL_ERROR: A SQL error occurred during an attempt to import this row. This error
occurs for rows processed when transaction logging is TRUE.
IMPORT_REJECTED: A user-specified filter query failed for this row. This error occurs
in Step 3 if the user has specified FILTER QUERY expressions.
FOREIGN_KEY: A required foreign key column in the target table could not be resolved.
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.
DUP_RECORD_EXISTS: The row exactly matches rows that already exist in the
destination tables.
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.

________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________

IMPORTED: The row was successfully processed against all its destination base tables.
This status is set after the import has been completed.

View - Visibility Applet Type

All, Personal, Sales Rep, Manager, Organization, Sub-Organization, Group, Catalog
BusComp View Mode
Name: Personal, Sales Rep, Organization, Group, Catalog
Owner Type: Person, Position, Organization, Group, Catalog Category
Applet - List – List Column
HTML Type: ActiveXControl, Button, Caption, CfgCheckBox, CfgComboBox,
CfgLabel, CfgList, CfgLink, CfgRadio, CheckBox, ComboBox, DrilldownTile, Field,
FieldLabel, File, FromExpand, FromSection, Hidden, ImageButton, JavaApplet, Label, Link,
Mailto, MakeCall, MinButton, MinButtonEdit, MinButtonEditNew, MinButtonNew,
MinButtonQuery, Password, PostionOnRow, RTCEmbedded, RTCPopup, RadioButton,
RecNavNxt, RecNavPrv, SSNxt, SSPrv, Text, TextArea, URL
Business Component – Field
Type: DTYPE_BOOL, DTYPE_CURRENCY, DTYPE_DATE,
DTYPE_DATETIME, DTYPE_ID, DTYPE_INTEGER, DTYPE_NOTE,
DTYPE_NUMBRE, DTYPE_PHONE, DTYPE_TEXT, DTYPE_TIME,
DTYPE_DATETIME.
Link
Specifies which record to retrieve from the child business component. Supports the
master detail view. Specifies the FK to populate when creating new child records. Used
with both 1: M and M: M relationship between parent and child data.

________________________________________________________________________
Release 1.0