Beruflich Dokumente
Kultur Dokumente
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.
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.
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
________________________________________________________________________
The hierarchical Picklist is in which the LOV type for the Picklists we are going to
use is same for all.
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.
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.
________________________________________________________________________
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).
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
Dynamic Toggling
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)
________________________________________________________________________
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.
(To set the More /Less Mode Create a Toggle Layout Control and
add it using Web Layout Editor.)
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.
Link
Link
Multi-Value Link
________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________
Join
________________________________________________________________________
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.
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.
`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
________________________________________________________________________
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
________________________________________________________________________
________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________
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.
Error flags (0 or 1)
Default Value = 0
________________________________________________________________________
Release 1.0
Siebel 7.0.3 Seibel Configuration
________________________________________________________________________
________________________________________________________________________
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.
________________________________________________________________________
Release 1.0