Académique Documents
Professionnel Documents
Culture Documents
January 2011
This guide includes the following topics:
Subcategory: DB Init
Use the following workaround if you already have the Mobile Web Client installed.
2 Before you run dbxtract and dbinit, empty the mwc_8114> folder. For example, empty
C:\Siebel\<mwc_8114>\UPGRADE.
Subcategory: Framework
5 Execute the copyjar.ksh file as shown below (hence it can replace the respective jar files):
copyjar.ksh </siebel_root>
copyjar.ksh /export/home/qa1/21225/ses
Once it executes successfully, it will display the copied info on the console.
Table 1. What’s New in Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P
Topic Description
“Release Notes for the Siebel 8.1.1.4 Fix Added information about CR 12-1Y3OYFP.
Pack” on page 7
“Instructions for ACR 500” on page 318 Added information about two known issues with ACR 500,
and workaround information for these issues.
“Release Notes for the Siebel 8.1.1.4 Fix Added this section to describe known issues with the
Pack” on page 7 8.1.1.4 release. (Rev.O)
“Configuration Instructions for Updated these sections for the 8.1.1.4 GA release. (Rev.
Enhancements and Updates” O)
Table 1. What’s New in Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P
Topic Description
“Configuration Instructions for Added a note to indicate that customers only need to
Enhancements and Updates” perform the configuration changes if they are
implementing the ACRs. (Rev. N)
“Quick Fixes Included in 8.1.1.x Fix Updated these sections for the Siebel 8.1.1.4 Fix Pack
Packs” prerelease. (Rev. N)
“Instructions for ACR 474 and ACR 508” Added two workflows. (Rev. M)
“Instructions for ACR 474 and ACR 508” Added crucial “known issues” information and made a few
corrections in the procedures. (Rev. L)
“Enhancements and Updates in Version Added information about ACR 467 and how to configure
8.1.1.1” it. (Rev. K)
“Configuration Instructions for Revised configuration instructions for ACR 500 to include
Enhancements and Updates” procedures for importing seed data. (Rev. K)
“Enhancements and Updates in 8.1.1.x Updated these sections for the Siebel 8.1.1.3 Fix Pack
Fix Packs” release. (Rev. J)
“Quick Fixes Included in 8.1.1.x Fix Updated these sections for the Siebel 8.1.1.3 Fix Pack
Packs” prerelease. (Rev. I)
“Resolved Change Requests” Removed reference to FR 12-1VM75R7. This fix was not
provided in the 8.1.1.2 Fix Pack. (Rev. H)
“Resolved Change Requests” Removed reference to FR 12-1VE6WMU. This fix was not
provided in the 8.1.1.2 Fix Pack. (Rev. H)
“Instructions for ACR 480” Added instructions for importing seed data associated
with this enhancement. (Rev. H)
Table 1. What’s New in Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P
Topic Description
“Resolved Change Requests” Corrected Fix Request ID for providing support for
Internet Explorer 8 on Windows Vista. (Rev. H)
This guide also provides information, instructions, and guidelines for installing Siebel Business
Applications Siebel Fix Pack 8.1.1.x releases on top of version 8.1.1 or a prior 8.1.1.x release.
Use this Siebel Maintenance Release Guide in conjunction with Siebel Bookshelf documents,
particularly the Siebel Installation Guide for the operating system you are using.
NOTE: This Siebel Maintenance Release Guide is updated to include the latest Siebel Fix Pack 8.1.1.x
release. The latest Siebel Fix Pack 8.1.1.x release available at publication time is Siebel Fix Pack
8.1.1.3. Verify the availability and applicability of all Fix Pack or Quick Fix releases with Oracle Global
Customer Support before you install.
The information contained herein supersedes, for warranty and other purposes, the contents of all
other documentation that may accompany this product, including the following:
■ OracleMetaLink 3 (https://support.oracle.com)
This Siebel Maintenance Release Guide contains information about how to install the maintenance
release (Fix Pack release). It also contains the most current information on product configuration
issues and workarounds for your application. Note that there may be references to functionality,
products, platforms, and language support in this document that are not available as part of the
products that your organization has licensed. Consult Oracle Global Customer Support on
OracleMetaLink 3 with questions regarding the applicability of Siebel Maintenance Release Guide
items to your deployment.
Additional Documentation
Oracle reserves the right to modify the documentation for Siebel Business Applications at any time.
If you have installed a Quick Fix for any Siebel 8.1.1 or 8.1.1.x release prior to the latest 8.1.1.x
release covered by this document, review Table 2 on page 11 to make sure that your Quick Fix
number is listed.
CAUTION: If you do not see your Quick Fix number in the table, do not install the latest 8.1.1.x Fix
Pack. This list is updated as new Fix Packs are released. Wait until your Quick Fix appears in the table
before applying the latest Fix Pack. If you have questions, contact Global Customer Support or your
Oracle representative.
This topic is part of “Enhancements and Updates in 8.1.1.x Fix Packs” on page 32.
Feature Enhancement
or Certification Number Feature Enhancement or Certification Description
ACR 475B Enhances UCM to provide Data Governance, Data Quality, and
usability enhancements.
Feature Enhancement
or Certification Number Feature Enhancement or Certification Description
ACR 499 ACR 499 provides the following enhancements to the Bulk Orders
functionality:
ACR 502 ACR 502 provides the following Siebel Configurator enhancements:
ACR 543 Extends the Siebel web services framework to provide an endpoint
through Oracle WLS.
ACR 623 Intelligent-Offer Generation (IOG) and certification with RTD 3.0
This topic is part of “Enhancements and Updates in 8.1.1.x Fix Packs” on page 32.
Feature
Enhancement or
Certification
Number Feature Enhancement or Certification Description
ACR 426 Adds electronic medical device reporting to the AECM module.
Feature
Enhancement or
Certification
Number Feature Enhancement or Certification Description
ACR 474 Supports OSM Integration and he Order to Activate PIP, and forward-ports
MDM, PIM, and Order to Cash enhancements from Siebel 8.x to Siebel 8.1.1.x
applications.
ACR 508 Forward-ports the Order to Cash PIP to Siebel version 8.1.1 applications.
ACR 529 Provides a single-step upgrade from Siebel Enterprise Applications to Siebel
Industry Applications.
ACR 539 Modifies the Siebel Clinical product to support the Study, Subject, and Visit
Synchronization Process Integration Pack for Siebel Clinical and Oracle
Clinical. This enhancement also provides a way to accurately track and
respond to issues related to site performance and protocol adherence.
ACR 562 ACR 562 extends the functionality previously provided by ACR 422, which was
included in the Siebel 8.1.1.1 Fix Pack.
■ Added missing text for ALT strings and other text read by screen
readers.
This topic is part of “Enhancements and Updates in 8.1.1.x Fix Packs” on page 32.
Feature Enhancement
or Certification Number Feature Enhancement or Certification Description
ACR 468B Allows Siebel Client Sync to support Lotus Notes 8.0 and Microsoft
Outlook 2007 with Intellisync 7.x SDK.
ACR 492 Provides Web service access through the Mobile Web Client to other
local desktop applications.
ACR 494 Provides Event Check enhancements and BEO Report functionality for
the Siebel Travel & Transportation application.
ACR 544 Enhances the Siebel Remote utility and allows it to be integrated with
the Siebel HA Upgrade solution.
This topic is part of “Enhancements and Updates in 8.1.1.x Fix Packs” on page 32.
Feature Enhancement or
Certification Number Feature Enhancement or Certification Description
ACR 432 Prevents users from opening multiple sessions on the Mobile Web
Client.
ACR 435 ACR 435 resolves the following issues with the printed version of
the 5 Day Weekly HTML Calendar:
ACR 437 Provides the ability to expose CDI WebServices for all CRUD
operations on key entities such as Account, Contact, Household,
Financial Account, and so forth.
Feature Enhancement or
Certification Number Feature Enhancement or Certification Description
ACR 439 ACR 439 contains the following enhancements for Siebel Search
ACR 452 ACR 452 provides the following Oracle Secure Enterprise Search
enhancements:
■ Dynamic weights
Feature Enhancement or
Certification Number Feature Enhancement or Certification Description
ACR 471 Bundles the Promotion and Product class relationship so that
changing a promotion in a change order loads the default
product.
ACR 476 Rebases Siebel Email Response support for Smart Answer
support.
NOTE: It is only necessary to perform the configurations in the following section if you want to
implement the ACRs that they are for.
You perform the instructions described in the subtopics that follow after you install the current Siebel
Fix Pack 8.1.1.x, as described in “Siebel Fix Pack Installation Instructions” on page 441.
NOTE: For more information about activities performed in Siebel Tools, including importing archive
(.sif) files, see Using Siebel Tools and Configuring Siebel Business Applications. For more information
about activities performed in the Siebel application, see Siebel Applications Administration Guide and
related books. These guides are available on the Siebel 8.1 Bookshelf on OTN at http://
www.oracle.com/technology/documentation/siebel.html.
Preinstallation Instructions
Before you apply the Siebel 8.1.1.x Fix Pack, the local database needs to be extracted from the
Server machine and initialized on the machine where Siebel Mobile Client will be installed.
Use the following procedure to extract the local database from the server machine and initialize it on
the machine where the Siebel Mobile client will be installed.
a Query for HQ, and select APARKER as mobile client and MOBILE CLIENT - STANDARD as routing
model.
b Navigate to the Administration - Siebel Remote screen, and then the Remote System Preferences
view. Uncheck the following parameters:
3 From the Server Manager command line utility, connect to the Siebel Server and run the following
commands:
5 Using the Server Manager Command line utility, run the jobs-Generate New Database and db
extract as follows:
■ list task <tasked ID> (Keep listing the task until the status changes to "Completed")
■ list task <tasked ID> (Keep listing the task until the status changes to "Completed")
Installation Instructions
1 Apply 8.1.1.x on Siebel Tools and Siebel Enterprise Server. (The patch for Siebel Enterprise
Server automatically patches the "Siebel Server, Siebel Gateway Server, and Siebel Database
Server components.)
■ seed_disconn.dat
■ seed_disconn.inp
3 Verify that the following files are present under <Siebel Tools loc>\TOOLS\REPPATCH\:
■ discon_symbstring.sif
■ disconnected.sif
5 Log into Siebel Tools as APARKER and point to the local database.
6 Enter the password for APARKER (such as aparker1-2), click Continue, enter the Server password
for APARKER at the prompt, and click Next.
Siebel Tools starts initialization of all the tables and parameters for the local database. Once the
initialization is done, Siebel Tools will automatically open and will connect to the local database.
7 In the Tools ODBC entry, enter the UID/PWD for the local database. (For the local database, UID/
PWD should be DBA/SIEBEL12]
8 Enter the encryption Key for the database and check for the database connection. It should show
as successful once the UID/PWD and Encryption Key have been entered correctly.
TIP: To get the encryption key, navigate to the Administration - Siebel Remote screen, and then
the Mobile Clients view. Query for the HQ* and then query for the user APARKER. In the
Additional Info column, query for RemLocSec:PlainKey.
9 Log into Siebel Tools (pointing to the local database). Navigate to Tools, and then Check Out.
NOTE: If you receive the "Error connecting to Datasource" error message, then check the data
source information. The source should be SSD default instance (UID/Server pwd) and
Destination: SSD Local Db default instance.
11 Open Siebel Tools (connecting to the local database) and lock the following projects one by one
by selecting the project and setting the "Locked" flag to "true":
■ Fast Search
■ Service
■ ERM Admin
■ New Search
■ Siebel eChannel
Once import is successful, the number of objects imported and updated will display. Click OK.
14 Make a copy of your existing siebel.srf (or siebel_sia.srf for SIA) and compile the imported
changes mentioned in Step 12 to the siebel.srf (or siebel_sia.srf).
15 In MWC Application.cfg (such as uagent.cfg for Siebel Call Center Application) make the following
changes:
■ DockConnString = <machine name of the Siebel server machine from where the local
database is imported>::<Synch Mgr Port> (This is applicable only if this is a fresh
installation.) For example, DockConnString = sdcp1952i017::40400
16 Apply Siebel 8.1.1.x on the Mobile Web Client to create the dsm.zip file under <mobile client
install loc>\BIN>. Unzip the dsm.zip file to create the dsm folder under <mobile client install
loc>\BIN>.
a Copy the files seed_disconn.dat and seed_disconn.inp files from 4 to the Mobile Client machine
(for example, D:\FS\ Build4_Final.)
b Navigate to <mobile client install loc>\BIN> using the command prompt and run the following
command.
For example:
Once dataimp command is done, a message will be displayed in the following format showing
the details of the tables and rows that were affected:
TOTAL TABLES: 39
NOTE: The Mobile Search Administration screen has already been added for the Siebel Call Center
application.
3 Select the application in the Object Explorer, and note the project to which the application
belongs.
7 Choose Edit, and then New Record, and use the following information to define the object
properties:
Property Description
Sequence Use Screen View Sequence Editor to determine the sequence of views. Do not
edit the Sequence property of the Screen View Object manually. See
Configuring Siebel Business Applications for defining Sequence for Screen
View Objects.
For more information about installing and configuring the Disconnected Search Module to enable
Siebel Mobile Search, see Siebel Search Administration Guide on the Siebel Bookshelf at http://
www.oracle.com/technology/documentation/siebel.html.
For more information about accessibility enhancements, see Accessibility Guide for Siebel Business
Applications on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.
Use the following procedure to enable screen readers to read out the applet summary for an
application. This is a user property based on the respective XML for an application.
To allow screen readers to read out the applet summary for an application
1 Navigate to Object Explorer in Siebel Tools.
2 Navigate to View > Options, and click the Object Explorer tab.
3 Unselect Application Object, select it again to add all of the child objects to the Object Explorer,
and click OK.
4 Click Application, and query for the Application Names listed in the following table:
Enabling Screen Readers to Read MVGs and Pick Applets for Calendar, Calculator, and MVG
Use the following procedure to enable screen readers to read out the MVG and Pick Applet for
Calendar, Calculator, and MVG. After these changes have been made, screen readers will read out a
Calendar Pick Applet as shown in the following example: Start Date: 25/07/2007 Calendar Icon.
To enable screen readers to read out the MVG and Pick Applet for Calendar,
Calculator, and MVG (Symbolic Strings)
1 Navigate to Object Explorer in Siebel Tools.
2 Navigate to View > Options, and click the Object Explorer tab.
3 Select the Symbolic Strings Object and click OK to add the Symbolic Strings object to Object
Explorer.
4 Click on Symbolic Strings and query for 'Current String Value' as 'Input'.
5 Lock the object.
e For SBL_EDIT_ICON_ALT_TXT, change 'Current String Value' from Select to 'Pick Applet'.
To enable screen readers to read out the MVG and Pick Applet for Calendar,
Calculator, and MVG (Bitmaps)
1 Navigate to Object Explorer in Siebel Tools.
4 Navigate to Bitmap (child object) and query for 'CALENDAR_ ICON' and CALCULATOR_ICON.
5 Change the 'Alt Text' value to 'Calendar' and 'Calculator' respectively, as shown in the following
table:
New / Bitmap Alt Text SIA SIF File HOR SIF File
Changed Category Bitmap Value Description Name Name
2 Navigate to View > Options, and click the Object Explorer tab.
3 Select Symbolic Strings Object and click OK to add the Symbolic Strings object to Object
Explorer.
New/ Current
Changed Project Name String Value SIA SIF File Name HOR SIF File Name
Table 7 lists some of the keyboard shortcuts available with ACR 422, and the procedures in the
section that follows describe how to add these keyboard shortcuts.
NextApplet Next Applet Ctrl + Alt + ] Ctrl+Alt+221 Shifts focus to the CmdNextApplet_SIA.sif
first anchor of the
next applet
NextApplet Next Applet Ctrl + Alt + ] Ctrl+Alt+221 Shifts focus to the CmdNextApplet_SIA.sif
first anchor of the
next applet
2 Navigate to View > Options, and click the Object Explorer tab.
3 Select the 'Command' object and click OK to add the Command Strings object to Object Explorer.
4 Click the Command object on Object Explorer and query for the 'NextApplet' command.
7 In 'Display Name - String Reference', provide the newly created Symbolic String or in 'Display
Name' provide 'Ctrl + Alt + ]'.
4 In the Display Name - String Reference' field, enter the newly created Symbolic String or in the
Display Name field, enter 'Ctrl + Alt + ['.
4 Copy the Record Name '2'. Name the New Record '3'.
4 Copy the Record Name '2'. Name the New Record '3'.
4 Copy the Record Name '2'. Name the New Record '3'
4 Copy the Record Name '2'. Name the New Record '3'.
4 Copy the Record Name '2'. Name the New Record '3'.
2 Navigate to Applet.
5 Make sure that the proper Symbolic String has been selected.
New /
Changed Applet Name Title Description SIA SIF File Name HOR SIF File Name
2 Navigate to Applet.
NOTE: The DefaultFocus user property can be applied for any form applet where the user requires
a default focus.
Changed Search lookin DefaultFocus SearchFor Added the user AppletSearchlo AppletSearchlookin_H
property to set the okin_SIA.sif OR.sif
default focus
3 Create a New Command named "View Info" with project "Command" as the project, using the
values detailed in the following table:
■ NAME="ViewInfo"
■ METHOD="ViewInfo"
■ TARGET="SI Plus"
■ DISPLAY_NAME_-_STRING_REFERENCE="SBL_DOES_NOT_MATTER-1004225828-03I"
View Info Command ViewInfo Ctrl + Alt + Z Ctrl + Alt A new shortcut CmdViewInf CmdViewInf
+Z key that o_SIA.sif o_HOR.sif
generates a
dialog box that
contains
ViewName, View
Summary and
Applet Names
Sub-View Tab SWE N/A Ctrl + Alt + V Ctrl +Alt N/A CmdSubVie CmdSubVie
(SWE SI) +V wTab_SIA.si wTab_HOR.s
f if
4 Add a new Accelerator to the Command for the required Key Combination with the following
values:
■ NAME="1"
■ BROWSER_PLATFORM="All"
■ DISPLAY_NAME_-_STRING_REFERENCE="SBL_DOES_NOT_MATTER-1004225828-03I"
■ INACTIVE="N"
❏ KEY_SEQUENCE="Ctrl+Alt+Z"
NOTE: Although it is not mandatory, it is important that you enter “Does not matter” as the value
for the Display Name or Caption field.
7 Navigate to Menu, and create a new Menu Item (Hidden) under the menu used by your
application, using the following values:
❏ Name="Hidden-View Info
❏ Position=8.39
❏ Command = "ViewInfo"
For more information about shortcuts, refer to other shortcuts such as NextApplet within Siebel
Tools.
Enabling Screen Readers to Read Out the Check Box “HTML Flag” as HTML
The following procedure allows screen readers to read out the check box “HTML Flag” as HTML. By
default, it reads as Public. To make this change, you can also import the
Applet_CommPackageResponse_SIA.sif file. For information about how to import .sif files, see
“Importing SIF Files” on page 61.
To enable screen readers to read out the check box "HTML Flag" as HTML
1 Open Siebel Tools, and navigate to applet "Comm Package Response Form Applet".
Resolving an Error Generated When Creating New Records Within the Leads Screen
Use the following procedure to resolve an error message that occurs when users are creating new
records under the Leads screen, so that users are not able to see any case records in the Pick Cases
MVG. To make this change, you can also import the PUBLeadListCaseMvgApplet.sif, PUBLeadsList.sif,
PUBLeadsListApplet.sif, and CaseMvg.sif files. For information about how to import .sif files, see
“Importing SIF Files” on page 61.
5 Navigate to the "PUB Leads List Applet" applet and lock it.
6 Click Edit to create a web template and add the necessary controls, along with SAVE and CANCEL
buttons.
2 Add a web page item called AccessibilityButton in the Web Page: DotCom Page Container
eService (Framed), locking the project "eApp".
3 Add another web page item called AccessibilityButton in the Web Page: CC Login Page (Login
Only).
The default tag text should be set to the applet header name. Add TITLE or LABEL for each table
entry (all HTML form elements). Row and column headers must be identified as required by OGHAG
TABLE-1 and TABLE-2. Adding a row title for each row in data table (Suggestion: this could be the
first displayed data column in the applet display. Ideally the customer can select which column can
be used as the index for the row title through configuration).
NOTE: The list applet row ids are not available out of the box. Users can add them if they want. The
first data column will be used as the default rowid when there is no row id provided in the "RowId"
applet user property. There are two options available to users to select different rowid.
Option 1: Users need to contact the administrator to define the "RowId" user property.
To do this, a new applet user property called "RowId" has to be added for the list applet. The "RowId"
value should be equal to one of the displayed column name. For example, in the Contact list applet,
if 'Last Name' has been selected as the row header, the user property value has to be set to "RowId
= Last Name". Here "Last Name" is the list column name.
Option 2: Users can select the column displayed window and select some other column as the first
column for the list applet. The newly-selected column will become the rowid. Lock the particular
applet that needs to be changed.
Providing a New Key Combination for the Next and Previous Record Commands
2 Navigate to View > Options, and click the Object Explorer tab.
3 Select the 'Command' object and click OK to add the Command Strings object to Object Explorer.
4 Within Object Explorer, click the Command object and query for 'Previous Record(SWE)'
Command.
9 Within Object Explorer, click the Command object and query for 'Next Record(SWE)' Command.
Current
New/ String
Changed Project Name Value HOR SIF File Name SIA SIF File Name
Command Project Accelerator Key Sequence SIA SIF File Name HOR SIF File Name
New Symbolic Strings Confirmation Create a new string for the Control
Message
2 Navigate to Administration - Data > List Of Values Explorer, and add the new LOV types
mentioned in the following table:
Language
Display Independent
Type Value Translate Multilingual Code Order Language Name
3 After you have added these changes, navigate to Screen > System Administration > List Of
Values to view these changes in the repository.
New/ Business
Changed Name Project Component Static Type Field Type Value
The following changes have been made to the User Preferences Business Component.
The following table describes the new User Profile Confirmation Message Parameter Applet that has
been added to support ACR 422.
New/ Business
Changed Name Project Component Class Title
The following table describes the applet controls changes that have been implemented to support
ACR 422.
Name Caption Field HTML Type Method Invoked Runtime Field Type
The following table describes the view changes that have been added to support ACR 422.
Visibility Applet
New/Changed Name Project Business Object Type
The following table describes the User Profile screen changes that have been added to support ACR
422.
New User Profile User Profile Aggregate View User Profile Confirmation
Confirmation Message Confirmation Message Message Parameter Applet
Parameter View Parameter View
2 Make sure that the Execute Query, WriteRecord, UndoQuery, UndoRecord, and Query Assistant
controls are present on the applet template.
NOTE: Edit template uses 'Applet List Edit (Edit/New/Query)' as the web template.
Web
New/Changed Name Project Template SIF File
Resolving an Error Where Commands Are Executed Before Users Click Enter
Users are encountering an issue where before they click Enter on a menu item in the Show dialog
box, the command is executed.
To resolve an error in which commands are executed before users click Enter in the
Show dialog box
1 Navigate to Object Explorer in Siebel Tools.
2 Navigate to View > Options, and click the Object Explorer tab.
3 Select the Symbolic Strings Object and click OK to add the Symbolic Strings object to Object
Explorer.
2 Navigate to View > Options, and click the Object Explorer tab.
3 Select the 'Command' object and click OK to add the Command Strings object to Object Explorer.
4 Within Object Explorer, click the Command object and query for the 'NextPage' command.
6 Within Object Explorer, click the '+' sign and choose 'Accelerator'.
7 For 'Browser Platform' - Extended, in 'Display Name - String Reference', provide the newly
created Symbolic String or in 'Display Name' provide 'SBL_ALT+CTRL+DOWN'.
8 In the 'Key Sequence' field, change the value to 'Alt+Ctrl+Y', as shown in the following table:
9 Within Object Explorer, click the Command object and query for the 'PreviousPage' command.
Resolving an Error Encountered While Creating a New Record in the Identities Form Applet
The information in the following section resolves an issue where users encounter a problem within
the Immigration contacts screen > Identities view when they try to create a new record under the
Identities form applet. To make this change, you can follow the procedure below, or you can import
the PublicSector_Controls.sif file. For information about how to import .sif files, see “Importing SIF
Files” on page 61.
To resolve this error message, change the HTML Type property of the DeleteRecord control from
MiniButton to MiniButtonEdit for the PUB Immigration Identity Form Applet, the PUB Lead Form
Applet, the HLS Group Form Applet, the Disease Form Applet, the FINS Application Entry Applet —
ACAPS, and the HLS Medication Form Applet. Use the following bulleted list information group for
each applet as a reference point.
■ Template: Edit
■ Template: Edit
■ Additions: WriteRecord (save) control. UndoRecord (cancel) does not need to be added as the
'DeleteRecord' control is already present on the template.
■ Applet: "HLS Group Form Applet", "Disease Form Applet" and "FINS Application Entry Applet -
ACAPS"
■ Template: Edit
■ Template: Edit
NOTE: For the HLS Group Form Applet, Disease Form Applet, and FINS Application Entry Applet,
access these applets from under the Application screen and not from the BCM Applications screen.
The necessary changes need to be made under the configuration context of Siebel Public Sector for
these applets, because they are also used by the FINS application.
Resolving an Issue Where Users Are Unable to Query for Evidence Parent Information
The following procedure resolves a problem where under Evidence screen> Evidence parent, users
are unable to query for User Parent, and they receive an error message. To make this change, you
can also import the PublicEvidencePickApplet_SIA.sif file. For information about how to import .sif
files, see “Importing SIF Files” on page 61.
Add 'Popup Query' template to the 'PUB Evidence Pick Applet' with appropriate controls
[ExecuteQuery and CancelQuery] placed on it.
2 Navigate to Tools > Import from Archive and select the related .sif file
3 Click OK, and follow the instructions in the wizard to implement the changes.
4 Stop the servers, compile the objects or projects into respective .sif file and then restart the
servers.
3 Click Yes when the dialog box displays and asks “This operation should only be performed while
connected to your local database. Would you like to continue anyway?”
5 Select the first option "Overwrite the object definition in the repository" in the Conflict resolution
section of the import wizard view.
6 Review the conflicting objects to see if the new or modified columns appear. The import log is
stored at Siebel\tools\temp\importlog.txt
2 For a single table, select the current row option in Tables (Apply Schema Window).
3 For more than one table, select the Choose Current Query option.
4 For the Accessibility project, select the S_ACC_VIEW_APPL table and current row option.
5 Make the following changes depending upon which database you are using:
a For MSSQL, enter the database users, the database user password, and the correct ODBC data
source.
b For Oracle, enter the table space, the index space, the database user, the database user
password, and the correct ODBC data source.
c For IBM DB2, enter the table space, the 16K table space, the 32K table space, the index space,
the database users, the database user password, and the correct ODBC data source.
6 After entering in the database information, click the Apply button.
7 Verify that the required changes have been applied by selecting count(*) from
S_ACC_VIEW_APPL.
For example:
4 Check the log files for any errors, and check S_ACC_VIEW_APPL for the data imported.
2 Import AccProject.sif. For a list of files that this .sif contains, see “Changes to SIF Files in ACR
422” on page 65.
The AdminScreen.sif file contains the modified System Administration Screen. For the list of
changes to this screen, see “Changes to SIF Files in ACR 422” on page 65.
Type Value
ACC_ATTRIB_TYPE Summary
ACC_ATTRIB_TYPE Label
ACC_LOCALE ENU
a Open a command line window and navigate to the folder where the three scripts reside
(genAccessibilityXML.pl, app_tree.pl, sqlstmt.pl).
#Connect to DB
#################################################
#################################################
_________________________________________________________________________
____
c Once the script is run an xml file will be generated, copy this xml in the following location:
Siebel\ses\siebsrvr\bin\LANG_FOLDER\ folder.
The name of the XML File should be same as the value mentioned for the Application user
property 'AccessibilityXMLFileName' for that application.
NOTE: The preceding steps help the users provide the summary for a new or a customized
applet. A UI will be created in which the user has to enter the summary for a particular applet.
This in turn will be placed into the xml file that will be generated after the perl script is run. Users
can use this xml file to allow screen readers to read out the applet summary.
5 Edit the “Position on Row” control’s properties by entering “ROW_OFF” for HTML Bitmap and
“ROW_ON” for HTML Disabled Bitmap.
7 Drag and drop the GotoPreviousSet and GotoNextSet controls to their respective placeholders,
and edit the properties using the values in the following table:
10 Drag and drop the Save and Cancel buttons to their respective placeholders.
11 Save the applet.
AccProject.sif
The AccProject.sif file contains the following new objects:
Business Components:
Applets:
Business Objects:
Views:
Picklists:
Symbolic Strings:
■ Accessibility
■ Applet Attributes
■ Attribute Type
■ View Attributes
AdminScreen.sif
The AdminScreen.sif file contains the following changes:
Preinstallation Tasks
Before you begin your installation, change a parameter in tools.cfg file within Siebel Tools
Repository Configurations
1 Navigate to REPPATCH\ ACR426RepSeedFiles_v8113.zip and unzip to any location accessible by
Siebel Tools.
❏ Contact
❏ Audit Trail
❏ Table ProductComplaints
❏ LS Medical Report
❏ Product
❏ Symbolic Strings
❏ Bitmap
❏ EIM ProductComplaints
■ S_PRD_CMPLNT_LS
■ S_EMDR_BATCH
2 Use the Import from Archive function within Siebel Tools to read this file and create the tables in
the repository. Use the merge option while importing this file.
3 The tables have to be in the repository before creating this on the physical database.
4 Within Siebel Tools and query for the list of tables that were imported into the repository.
5 Click the Apply/DLL button to apply the changes to the physical database.
■ EIM_EMDR_BATCH
■ EIM_PRD_CMP_LS
Use the following procedure to import the EIMTables.sif file into the repository.
2 Use the Import from Archive function within Siebel Tools to read this file and create the tables in
the repository. Use the merge option while importing this file.
3 Within Siebel tools, query for the list of tables that were imported into the repository.
4 Click the Apply/DLL button to apply the changes to the physical database.
4 Check the logs to see if all of the files imported successfully, and reimport all of the objects that
did not import successfully.
NOTE: The following procedure is an alternative to importing the SIF files. Use the following
procedure if you want to perform manually configure the existing objects.
■ Import Unziplocation\ACR426\REPOSITORY\Business
Service\CRMIntegCreatePISEBL782ToAERSSync.sif
■ Import Unziplocation\ACR426\REPOSITORY\Integration
Objects\CRMIntegSEBLSIALSProductIssueInterface.sif
■ Import Unziplocation\ACR426\REPOSITORY\Integration
Object\CRMIntegSEBLSIALSClinicalFaultMessage.sif
■ Import Unziplocation\ACR426\REPOSITORY\Integration
Object\CRMIOSEBLSIALSProductIssueInternal.sif
Screen
View
3 Do manual configuration for the existing "LS Medical Product Issue RR" Business Component:
Single Value
Fields
Modify Follow- Y
Up
Number
Modify Parent Y
Product
Issue
Report
Num
Single Value
Fields
Modify Report Y
Number
Modify Sub Y
Report
Type
Modify Type of Y
Report -
Follow-
up Flag
New Batch Id Id
Join
Multi Value
Link
Destination Use
New/Needs Business Primary
Modification? Name Auto Primary Component Destination Link Join
Business
Component
User Properties
Business
Component
User Properties
4 Perform manual configuration for the "LS Medical Product Issue" Business Component:
Single
Value
Fields
New/
Needs Calcul
Modific ated Immediate Validati
ation? Name Join Column Value Type Post PickList on No Copy
Modify FDA Y
Reporta
ble
Single
Value
Fields
New/ Imm
Needs edia
Modificat Joi Colu Calculated te
ion? Name n mn Value Type Post PickList Validation No Copy
6 Perform manual configuration for the existing "LS Medical Product Issue RR" Business Object:
Business Object
Component
7 Perform manual configuration for the existing "Audit Trail Engine" Business Service:
Business Service
User Props
New/Needs
Modification? Name Value Comment
8 Perform manual configuration for the existing "Field Value Icons" Bitmap Category:
Bitmaps
9 Perform manual configuration for the existing "LS Medical Product Issue RR Form Applet" Applet:
Control
New/ HTML
Modified? Name Caption Caption String HTML Type Only
Applet Web
Template (Existing
and Modify) Name Type Web Template
Applet Web
Template Items
New/Needs
Modification? Name Control Comments
10 Perform manual configuration for the existing "LS Medical Product Issue RR Child List Applet"
Applet:
List Columns
Display Name -
New/Needs String
Modification Name Field Reference Read Only HTML Icon Map
Applet Web
Template (Existing
and Modify)
Applet Web
Template Items
Applet Web
Template Items
11 Perform manual configuration for the existing "LS Medical Product Issues RR Screen" Screen:
Screen
View
New/
Needs View Bar Text -
Modificat Category Parent String Menu Text String
ion? Name Name View Type Category Reference Reference
Screen
View
New/
Needs View Bar Text -
Modificat Category Parent String Menu Text String
ion? Name Name View Type Category Reference Reference
a Navigate to Start > Settings > Control Panel > Administrative Tools> Data Sources (ODBC),
navigate to the System DSN tab, and click Add.
e For Oracle, enter the TNS service name that you created to connect Siebel Tools to the database.
2 Before executing the next step, make sure that the dataimp.exe file exists in the <Tools Install
Directory>/bin directory.
<Tools Install Directory> - Replace with your Siebel Tools install directory
<Database Platform> - Replace with your database platform (ORACLE, DB2UDB or MSSQL)
4 Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
Seed data import includes mono-language seed data import and language seed-data import. Use
either Step 5 or Step 6 depending upon the language that you are installing.
<Tools Install Directory> - Replace with your Siebel Tools install directory
<Database Platform> - Replace with your database platform (ORACLE, DB2UDB or MSSQL)
b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure import completed
successfully
6 Use the following procedure to import languages other than ENU:
Run the following command after importing ACR426_Seed.dat file for importing the locale
specific ACR426_Seed_Locale_XXX.dat, where XXX is the language code.
<Tools Install Directory> - Replace with your Siebel Tools install directory
7 Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
2 Navigate to the Administration - Web Services > Outbound Web Services view.
5 On the Service Port applet, update the address to point to your BPEL server location. By default,
it looks like http://localhost:8888/orabpel/default/LSeMDRTransmitFDA/1.0, so change the
localhost to the SOA host name and change 8888 to the proper port number.
7 Navigate to the Administration - Web Services > Inbound Web Services view.
For more information about inbound Web services, refer to the sample acknowledgement
message: Unziplocation\ACR426\Sample\LSUpdateeMDRProductIssueStatus Sample Input.xml
NOTE: NOTE: Siebel Tools must be connected to the same database that the Siebel application
server is connected to.
3 From the list applet, right-click and choose Import Workflow Process.
LS LS LS eMDR
CRMIntegSEBLSIAProductIssueInsertOut CRMIntegSEBLSIAProductIssueIns
boundFlow.xml ertOutboundFlow
6 Withink Lock Projects view > Workflow process, focus on the record and then click the Deploy
button on top of the applet to deploy the workflows.
7 Repeat the preceding steps for the LS Siebel PI eMDR Batch workflow.
❏ Description: The value is the number of days before the regulatory report deadline, and
the system should highlight this value for the users. The urgency is indicated by having
the urgency flag in the eMDR list turn from yellow to red.
NOTE: Enhancements are required in the BPEL processes delivered to integrate with FDA.
For Outbound Web services, the Siebel message is transformed to an HL7 message using the
following transformation XSL:
Unziplocation\ACR426\BusinessProcesses\RegulatoryReport\LSeMDRTransmitFDA\bpel\
FDAAcceptanceFormat.xsl and written to a XML file.
The Web service supports the same schema for all the three acknowledgements. Customization is
required to transform the MDN message received from FDA for the first two acknowledgements to
The Siebel schema and call the Web service.
For information on installing Oracle SOA Suite, refer to the Oracle Application Server
Documentation Library. The library is available on Oracle Technology Network (OTN) at http:/
/www.oracle.com/technology/documentation/index.html. To access the documentation, click
the Oracle Application Server 10g Release 3 (10.1.3.1) link.
If desired, support for JDeveloper can be purchased separately. For information on installing
Oracle JDeveloper, refer to OTN at http://www.oracle.com/technology/documentation/
index.html.
2 Verify that the schema can be accessed by opening a browser and typing in the following URL:
The CoCommon schema should open correctly. If there is a problem in opening the file, restart
the SOA suite.
NOTE: Change the values in the lines that begin with "<property name="PARAMVALUE">.
Replace the values with the relevant values from your environment.
<LISTOFBUILDPARAMETERS xmlns="http://www.siebel.com/uan/SiebelBIAs/
SharedComponents/CRMIntegProcessProperties">
<BUILDPARAMETER>
<property name="PARAMNAME">http://sdc78212svod:8888/orabpel/default</property>
<property name="PARAMVALUE">http://127.0.0.1:8888/orabpel/default</property>
"http://127.0.0.1:8888" should be replaced with the HOST, PORT where the BPEL PM is
running. "orabpel" should stay same.
"default" is the name of domain where the bpel processes are to be deployed.</property>
</BUILDPARAMETER>
<BUILDPARAMETER>
<property name="PARAMNAME">http://sdc78212svod:8888/orabpel/xmllib</property>
<property name="PARAMVALUE">http://127.0.0.1:8888/orabpel/xmllib</property>
<property name="DESC">This Parameter is to capture the XMLLIB url. Please specify your
environment specific value for "PARAMVALUE" property.
Here "http://127.0.0.1:8888" should be replaced with the HOST, PORT where the BPEL PM is
running. "orabpel/xmllib" should stay same.</property>
</BUILDPARAMETER>
<BUILDPARAMETER>
<property name="PARAMNAME">"http://sdc78212svod/eai_enu/
start.swe?SWEExtSource=WebService;SWEExtCmd=Execute;UserName=harikuma;Passwor
d=harikuma"</property>
<property name="DESC">This Parameter is to capture the Siebel server url. Specify your
environment-specific value for "PARAMVALUE" property (such as http://
xyz.siebel.com:8888</property>
</BUILDPARAMETER>
<BUILDPARAMETER>
<property name="PARAMNAME">"c:\temp"</property>
<property name="PARAMVALUE">"c:\test"</property>
<property name="DESC">Ouput Directory where FDA eMDR XML files will be created </
property>
</BUILDPARAMETER>
</LISTOFBUILDPARAMETERS>
Use the following procedure to set the output directory for storing FDA Report XML files.
To set the output directory for storing the FDA report XML files
1 Navigate to Unziplocation\ACR426\BusinessProcesses\
RegulatoryReport\LSeMDRTransmitFDA\bpel, and edit WriteIntoFile.wsdl.
6 Specify a directory name where the BPEL processes are stored (for
example:Unziplocation\ACR426\BusinessProcesses).
8 Repeat the following steps for each of the following JPR files:
■ Unziplocation\ACR426\BusinessProcesses\RegulatoryReport\eMDRUpdateFDAAck\eMDRUpdat
eFDAAck.jpr
■ Unziplocation\ACR426\BusinessProcesses\RegulatoryReport
\LSeMDRTransmitFDA\LSeMDRTransmitFDA.jpr
NOTE: Before you begin, make sure that the SOA Suite has been installed, and make sure
JDeveloper has been installed and that the application server and integration server connection have
been configured.
3 Right-click on the project name and choose Deploy > IntegrationServerName > Deploy to default
domain.
6 Right-click on the project name and choose Deploy > IntegrationServerName > Deploy to default
domain.
This compiles the SRC code and then deploys the BPEL process to the SOA Instance.
❏ \DMGSchemaChanges (refer to the information about how to import .sif files in Siebel
CRM and UCM Integration Guide on My Oracle Support.
❏ \LMU
❏ \SeedData (refer to the information about how to import seed data in Siebel CRM and
UCM Integration Guide on My Oracle Support.
❏ \SIFFiles
❏ WFs
As part of the O2C release, schema changes have been made within the database. The
O2CMST80_S_USER.sif, VACR437_EIMFinal_81.sif and VACR437_TableFinal_81.sif files all
contain changes, and the S_USER table has been changed as well.
For information about how to import .sif files into the repository, how to create tables on the physical
database, how to import seed data, how to set up the workflow policy, how to create a job for the
Generate Triggers component, how to reveal the Default Tasks parameter, how to start tasks for
Workflow Monitor Agent, and how to set up the integration user, see Siebel CRM and UCM Integration
Guide. To access this guide, search for Doc ID 763962.1 on My Oracle Support.
After installing ACR 439, you must make sure that Find objects are visible in the application.
2 Select the application from Object Explorer, and search for the relevant Application Name.
3 Navigate to Application Find in the Object Explorer, and activate the Find names that you want
to display for the application.
4 Make sure that the relevant Business Components are part of the Search Execution Business
Object.
You may receive the following error message after you have installed ACR 439: “An error has
occurred creating business component ‘Consumer’ used by business object ‘Search Execution’.
Please ask your systems administrator to check your application configuration. (SBL-DAT-00222).
3 Query for “Search Execution,” right-click the access the submenu, and select “Unlock Object.”
5 Click New Record and add the required Business Component (such as “Consumer”).
For more information about ACR 439 and for information about how to implement this enhancement,
see Siebel Search Administration Guide on the Siebel Bookshelf, available on Oracle Technology
Network (OTN) at http://www.oracle.com/technology/documentation/siebel.html.
4 Import the .sif files you extracted from the .zip file.
■ Applet: Search lookin Results Body, Search lookin Results Header, Recent Saved Searches Applet
2 Within Applet Search lookin Results Header, add the user property GotoView= Search lookin
Results View.
To add the SamePage and GotoView user properties to the Search lookin applet
1 Connect to Siebel Tools.
3 Navigate to Applet User Prop and add the two user properties listed in the following table:
4 Navigate to Control, query for Name= "Search", and update the Search property as detailed in
the following table:
To add the GotoView user property to the Search Results Body applet
1 Connect to Siebel Tools.
3 Navigate to Applet User Prop and add the following user property:
4 Navigate to Control, query for Name = "PositionOnRow", and update the following property:
ROW_OFF ROW_ON
5 Navigate to Applet Web Template Items and add the item detailed below:
2 Click New and add "Search lookin Results View" with the following values:
3 To give the administrator responsibility to the view, navigate to the Administration - Application
screen, and then the Responsibilities view. Query for the administrator.
■ Search_ListBodySearchResults.swt
■ SearchResults.swt
■ SavedSearch.swt
Apply the changes listed below for each swt in order for ACR 439B to display the web templates
correctly.
To edit Search_ListBodySearchResults.swt
Place the text below between this line:
<tr class="swe:this.RowStyle">
To edit SearchResults.swt
Place the following text after the line </b> for id ="3000":
<b>
</swe:control>
</b>
<b>
</swe:control>
</b>
To edit SavedSearch.swt
Place the following text after the line </tr> for id="99":
<tr>
<td align="left">
<swe:control id="101">
</swe:control>
</td>
</tr>
<tr>
<td align="left"> </td>
</tr>
For more information about the Siebel Hospitality application, see Siebel Hospitality Guide on the
Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.
NOTE: Oracle Secure Enterprise Search patch 10.1.8.4 or higher is required for ACR 452.
❏ SET DATASRC= <Enter Source name used by Siebel Tools for ODBC DSN. The value is
the same as that used for ConnectString in the [ServerDataSrc] section of Tools.cfg>
❏ SET TBLOWNER=<Enter table owner name used by Siebel Tools for connecting to the
server database. The value is the same as that used for TableOwner in the
[ServerDataSrc] section of Tools.cfg>
❏ SET USERNAME=<Enter the username used to connect to the Siebel database, such as
SADMIN>
❏ SET PASSWORD=<Enter the password used to connect to the Siebel database, such as
SADMIN>
2 Run import.bat.
❏ Fast Search
❏ Search Execution
❏ Symbolic Strings
❏ SET PCDDATASRC= <Enter DataSrc name used by Tools.cfg. The value is the same as
[ServerDataSrc] in the Tools.cfg>
❏ SET PCDUSERNAME=<Enter the username used to connect to the Siebel database, such
as SADMIN>
❏ SET PCDPASSWORD==<Enter the password used to connect to the Siebel database, such
as SADMIN>
2 Run import.bat
a Navigate to Tools > Utilities > Locale Management to import LMU files for the specific language
from the Tools\REPPATCH_ACR452_phaseA\LMU folder into Siebel Tools.
b Select Source Language = English American
d Click the Import tab, click Browse to locate the LMU file you want to import, and then click
Import.
2 Stop the Siebel Server, if it is running.
3 To change the language to the specific language that you just imported, navigate to View >
Options > Language.
❏ Fast Search
❏ Search Execution
❏ Symbolic Strings
3 Navigate to Administration – Search > Search Engine Settings to confirm that the Connect and
Disconnect buttons have been added.
For information on installing Search_Engine_Config.xml, and configuring Search for ACR 452, see
the Siebel Search Administration Guide on the Siebel Bookshelf at http://www.oracle.com/technology/
documentation/siebel.html.
Use the instructions in this topic to implement ACR 456, which provides a user interface for exporting
and importing assignment-related data.
For more information about the enhancements provided by ACR 456 for version 8.1.1.1 and later,
see Siebel Assignment Manager Administration Guide. The latest version of this guide is available on
the Siebel 8.1 Bookshelf on OTN at http://www.oracle.com/technology/documentation/siebel.html.
1 On the machine where you installed Siebel Tools, locate the file ACR456.zip in the folder
SIEBEL_TOOLS_ROOT\REPPATCH.
2 Uncompress this .zip file and extract the archive files (.sif) it contains.
3 Navigate to SIEBEL_TOOLS_ROOT\bin\enu.
4 Open the file tools.cfg in an editor like Notepad.
5 Change the value of the SymStrPrefix parameter to SBL_. (After performing the steps described
in this topic, change this parameter back to its original value of X_.) Save the tools.cfg file.
■ Symbolic Strings
■ Assignment
■ Orgchart
■ Admin
8 Import the archive files (.sif) you previously extracted from ACR456.zip into Siebel Tools. Import
the files in the order shown below:
■ AM-ImportExport.sif
■ AM-ImportExport-SymbolicStrings.sif
■ AM-ImportExport-applet.sif
■ AM-ImportExport-buscomp.sif
■ AM-ImportExport-screen.sif
9 Compile the changes into an updated repository file (SRF file). Copy the new SRF file to the Siebel
Server installation, under SIEBSRVR_ROOT\objects\enu.
10 In the tools.cfg file, change the value of the SymStrPrefix parameter back to X_. Save the
tools.cfg file.
2 Navigate to the Administration - Application screen, and then the Views view.
5 Add List of Values (LOV) data for U.S. English (ENU), as described below.
NOTE: This example is for U.S. English (ENU) only. For other languages, see files in the
compressed file ACR456.zip. Set Display Value appropriately for each non-ENU language.
a Navigate to the Administration - Data screen, then the List of Values view.
❏ Display Value is Position and Activities, and Language-Independent Code is Position and
Activity.
3 Select the workflow process Export Assignment Data. (This workflow was added when you
imported the file AM-ImportExport.sif.)
For more information about Siebel Order Management, see Siebel Order Management Guide on the
Siebel Bookshelf http://www.oracle.com/technology/documentation/siebel.html.
1 Navigate to the Siebel Tools installation directory <Tools Install Directory>\REPPATCH, and unzip
the acr457.zip file.
3 Import the SIF files from the ObjectsSIFs folder into Siebel Tools using the Import From Archive
function. Make sure to choose Merge Option in the Siebel Tools import wizard.
NOTE: If you have not locked the required projects, you may receive a warning error message.
6 Compile all the projects using Compile Projects function, and select either the All Projects option
or the Locked Projects option. Save the srf file to the <Siebel Server Install
folder>\objects\ENU\siebel_sia.srf directory on the installed Siebel Server.
8 Lock the SIS OM Base Architecture project, and import the workflows listed in the following table
into the Siebel application.
SIS OM Disconnect Products & Services Process Modified SIS OM Base Architecture
b Right-click on the right-side pane called Workflow Processes and import the .xml file into Siebel
Tools from the workflows folder. Refer to the list of workflows in the table above to know which
projects these workflows need to be imported into.
c Check the status of each workflow process. If it is In-Progress, then deploy the workflow to
change its status to complete. Do not click the Deploy + Activate button, as doing so will yield
an error message. Only click the Deploy button.
NOTE: You may receive the "This is an invalid Workflow…" error message while deploying the
modified workflows from the list. Ignore the error and click Yes.
d Repeat Step b and Step c for of all the workflows in the folder.
e Log in to the Siebel application as an administrator, and navigate to the Site Map.
2 Query for each of the following component groups and if Enable State = Disabled, click
<Enable>:
SIA
NOTE: You can also activate the component groups by running the Enable compgrp <Alias>
command through the Srvrmgr command prompt.
3 After enabling the necessary components, navigate to Site Map > Administration - Server
Configuration > Enterprises > Synchronize, select all the records and click the Synchronize
button.
d Type <Build>ses\siebsrvr\bin.
f Run the command to verify that the components were successfully enabled.
h Verify that the command executed successfully, and then run the Exit command.
j After the machine is up, than connect to server manger by running command in Step e and verify
the enabled components groups by running the "list of compgrp" command.
6 Use the following procedure if you are a UNIX customer:
a From the local machine click on Stat - Run- type telnet <Machine name> (such as telnet
sdcpi43).
c Navigate to <Build>ses\siebsrvr\bin.
smgr <enter>
f Verify that the command executed successfully, and then run the Exit command.
NOTE: Before you run the scripts in the following procedure, make sure the Workflow component is
enabled and that the server has been restarted after the component groups have been enabled.
2 Click the Load from File button and load the "COM_Workflow Admin Service Delete.xml" file.
3 On the Input Arguments tab, click the Load from File button and load the "COM_Workflow Admin
Service Input.xml" file.
4 On the Simulator Applet, select the record that has the Method Name as "DeleteDeploy" and click
the Run button.
NOTE: Before you run the script, make sure the Workflow component is enabled and that the server
has been restarted after the component groups have been enabled.
2 Click the Load from File button and load the "COM_Workflow Admin Service Activate.xml" file.
3 On the Input Arguments tab, click the Load from File button and load the "COM_Workflow Admin
Service Input.xml" file.
4 On the Simulator Applet, select the record that has the Method Name as "Activate" and click the
Run button.
5 Log out of the eCommunications application and then log back in.
Use the following procedure to manually activate the Pricing and Eligibility Procedure - Default
workflow process.
3 Query for the Pricing and Eligibility Procedure - Default workflow process and activate it.
NOTE: If you have installed Siebel 8.1.1 QF1002 for ACR 463 or Siebel 8.1.1.1 QF5101 for ACR 463,
you do not need to perform the repository changes detailed in the following sections, as the changes
that you performed when you installed the Quick Fixes were not overwritten. However, if you are
installing ACR 463 for the first time, you do need to perform the repository changes detailed in the
following sections.
The ACR463.zip folder that you create will contain the following subfolders:
❏ \DMGSchemaChanges
❏ \EIM
❏ \LMU
❏ \SeedData
❏ \SIFFiles
❏ \WFs
Use the following procedure to import the schema into the database.
❏ EIM Asset
❏ EIM Invoice
❏ EIM Order
❏ EIM Product
❏ EIM Quote
❏ EIM BulkRequest
❏ EIM Organization
❏ Table Asset
❏ Table BulkRequest
❏ Table Invoice
❏ Table Order
❏ Table Organization
❏ Table Product
❏ Table Quote
❏ Table CIF
❏ Table Person
❏ Table FleetManagement
❏ CUT Newtable
❏ AIA24_schema_changes.sif
❏ AIA24_EIM_schema_changes.sif
3 Use the Siebel Tools Import from Archive function to read this file and create the tables in the
repository. The "merge" option should be used while importing this file.
2 Use privileged database user\pass word in the Database user \ Database user password column
in the Apply Schema dialog box.
NOTE: Make sure to create the ODBC data source for the database to which you want to apply
the schema changes.
4 Query for the tables that have changed using the following criteria:
5 Click on Apply/DDL.
8 Enter the appropriate information for ODBC Data Source/ Database User and Database User
Password.
a Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC).
c Click Add.
For Oracle, enter the TNS service name that you created to connect Siebel Tools to the
database.
g Test the connection and click OK after you have verified the connection.
2 Navigate to the directory where you installed Siebel Tools and change it to the REPATCH\ACR463
directory.
NOTE: Before you perform the following step, make sure that the dataimp.exe file exists in the
<Tools Install Directory>/bin directory.
3 Seed data import includes mono-language seed-data import and language seed-data import.
4 Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the
import completed successfully.
[Siebel]
……..
SymStrPrefix = SBL_
……..
NOTE: After changing the tools.cfg file, make sure to log out of Siebel Tools and log in again to
apply the changes.
❏ Account
❏ Account (SSE)
❏ Assignment (SSE)
❏ Asset Management
❏ Bitmap
❏ CMU Billing BC
❏ CMU Billing UI
❏ CUT Billing
❏ CUT Profile
❏ Contact
❏ Comm Manager
❏ Communication
❏ Eligibility Compatibility
❏ Fleet Management
❏ MACD Performance
❏ Order Entry
❏ Product
❏ Product (SSE)
❏ Product Integration
❏ Product Selection UI
❏ Quote (UI)
❏ Quote
❏ Service
❏ Symbolic Strings
❏ UCM Privacy Management
❏ VEAI CUT Billing Integration
❏ eService Billing
❏ eAuto Product
3 Import the rest of the SIF files from the SIFFiles folder into Siebel Tools using the Import From
Archive function.
NOTE: If you have not locked the required projects, you may receive a warning error message.
❏ Modified Applets.sif
❏ Modified BCs.sif
❏ Modified Bitmaps.sif
❏ Modified BOs.sif
❏ Modified BSs.sif
❏ Modified Classes.sif
❏ Modified Commands.sif
❏ Modified IOs.sif
❏ Modified Links.sif
❏ Modified Picklists.sif
❏ Modified Screens.sif
❏ Modified Views.sif
The following steps are only necessary for customers who are installing languages other than
ENU:
4 Import LMU Files for the specific language from the LMU folder into Siebel Tools. [Select menu
Tools ' Utilities ' Locale Management].
b Click the Import tab > Browse to locate the LMU file you want to import and click Import.
NOTE: If an error occurs while you are importing the LMU file, open the file, convert the language
value for Source into the corresponding language. For example, do the following for NLD:
6 Compile all the projects using Tools > Compile Projects and selecting the "All Projects" option.
Save the srf file to location <Siebel Server Install folder>\objects\ENU\siebel_sia.srf on the
installed Siebel server.
8 Import the workflows listed in the following table into the Siebel application.
NOTE: All of the existing workflows should be imported. In other words, the modified workflows
should be imported into the corresponding projects.
ABO Bulk Request Add Item Customize Process ABO Bulk Request
ABO Bulk Request - Clear Exception Process Workflow ABO Bulk Request
ABO Bulk Request - Parallel Sub Process Workflow ABO Bulk Request
ABO Bulk Request - Prepare Action Set Sub-Process Workflow ABO Bulk Request
SIS OM Suspend / Resume Products & Services Process SIS OM Base Architecture
b Right-click on the right-side pane 'Workflow Processes' and import the .xml file into Siebel Tools
from the WFs folder. Refer to the list of workflows in the table above to know which project these
workflows need to be imported into.
c Check the status of the Workflow process. If it is In-Progress, then make it complete by
deploying the Workflow process (For version 8.0 and above, the "Publish/Activate" button
changes the status to complete. To view this button, click the View menu > Tool Bar, and select
WF/Task Editor.)
NOTE: If this step throws an error message, note the workflows that failed and manually activate
them within the application.
d Repeat Step b and Step c for of all the workflows in the folder.
c In the first applet, called 'Action Sets', search for the Action Set 'Cache Refresh BC - ISS
Promotion Pricing Components List Applet'.
d For this Action Set, in the bottom Form Applet, there is a control with the 'Business Service
Context' label. For this control, the current value previously was only "ISS Promotion Pricing
Components", "ISS Promotion Pricing Rules Summary". Another new entry was added to this and
now the value for this control is "ISS Promotion Pricing Components", "ISS Promotion Pricing
Rules Summary", and "Promotion Config Item". (Note that there should be a space after the
comma.)
e Navigate to the child applet.
c Lock each Variable Map and release a new version of each of these maps.
After you activate the rulesets, you need to reload the runtime events.
3 Within the Events list applet, click the Menu button, and select Reload Runtime Events.
AQ has been implemented for the following outbound Web services in this release:
■ Submit Order
■ Adjustment
The following sections contain information about how to implement AQ in your Siebel application, as
well as more detailed information about the outbound Web services listed above.
4 Navigate to the Profiles view, and click on the Special Rating Profile subview.
5 Query for the target special rating list and click the Synchronize button.
The Synchronize button invokes the "SWI Special Rating List - Synchronize Process" workflow
using the Named Method Business Component user property.
The SWI Special Rating - Synchronize Process workflow is a new workflow created for the AIA Comm
2.4 release. It is invoked through the Synchronize button, which is available in the Special Rating list
applet (Account screen > Profiles view > Special Rating Profile). The workflow contains the steps to
query for and synchronize the updated Special Rating List with BRM by calling the Proxy Business
Service, as detailed below.
Start > (Connector 0) > Query Special Rating List > Synchronize > Update List Synch Date >
Upadate Items Synch Date > End 0
Note the following information about the SWISpecialRatingList outbound Web service:
This Web service is used to send the Updated/Modified Special Rating List details to BRM for
synchronizing when the user clicks the Synchronize button in the Special Rating list applet.
This AQ and connection factories are created in FMW and the same URI should be used in outbound
Web service target address.
❏ Transport: JMS
Use the following procedure to initiate the Submit Order outbound service.
Note the following information about the SWISubmitOrder outbound Web service:
Use this Web service to submit orders into the queue. This AQ and connection factories are created
in FMW and the same URI should be used in outbound Web service target address.
❏ Transport: JMS
2 If the adjustment request is not approved, it changes the status of the request to Pending, and
terminates.
3 If the adjustment request is approved, it reads the enterprise details, such as the enterprise
server name, language, and locale.
6 Updates the Siebel database for the Adjustment Record to reflect the status as Submitted.
Use this Web service to Submit Adjustment Request into the queue. This AQ and connection factories
are created in FMW and the same URL should be used in outbound Web service target address.
❏ Transport: JMS
5 Navigate to the Service Ports list applet and change the URI given by the ABS team.
NOTE: Query for these inbound web services: * ISS *; * Update Order *; * SWI Update *, SWI*
3 In the middle Inbound Service Ports list applet, change the address port.
NOTE: Replace the string <web server>, <lang>, <UserName>, <Password> with correct data
based on server information.
To enable compgrps
NOTE: Bounce the server after enabling the compgrp and synchronizing it.
For more information about enabling compgrps, see “Enabling Compgrps” on page 141.
To activate workflows
Use the following steps to activate all C/OM workflows.
1 Navigate to Site Map > Administration Business Process -> Workflow Deployment > Active
Workflow Processes.
■ Query for the following groups: Eligibility & Comp, Asset Based Ordering, Pricer, eSales,
Product Promotions, Configurator, C/OM UI processes, CUT eSales (for SIA, not for HOR),
Product Recommendation, and delete them manually after deactivating the processes. To
deactivate these groups, select them all and then select Deactivate Process. You can check
the Deployment Status as Inactive.
■ Query for the following groups: Eligibility & Comp, Asset Based Ordering, Pricer, eSales,
Product Promotions, Configurator, C/OM UI Processes, CUT eSales (for SIA, not for HOR),
Product Recommendations.
Enabling EAI and Workflow Component Groups in the Siebel Server will start all the required
Components stated above for transaction logging.
2 Click New and type "Generate Triggers" under Component/Job to create a job for the Generate
Triggers component.
❏ EXEC = TRUE
❏ Remove = TRUE
2 Click New and type "Generate Triggers" under Component/Job to create a job for the Gnereate
Triggers component.
❏ EXEC = TRUE
2 Make a copy of the Workflow Monitor Agent in Administration - Server Configuration >
Component Definition and change the name to "Workflow Monitor Agent SWI".
4 Under Component Parameters, query for "Group Name" and type the SWI Account Update Policy
Grp under Value to change the Group Name to “SWI Customer Update Policy Grp” in the
Component Parameter applet.
8 Click the Activate button to change the status of the new component to "Active".
Workflow Monitor Agent has a parameter called 'Default Tasks' which has been hidden and should
only be displayed or available to advanced users.
2 In the top Siebel Servers applet, select the server on which you want to modify the parameter.
3 Under the Component subtab, query for the Server Manager component.
4 Under the Component Parameter subtab, query for 'Show Advanced Objects'.
NOTE: You must log out from the current user session and log back into the application in order
for the parameter to take effect.
7 Rename the existing diccache.dat file in the path <Installed Directory> \ses\siebsrvr\bin.
2 Select "Tasks".
3 Query for the "WorkMonSWI" task and start it. You can also use Server Manager to start the task.
After about five minutes, check for log details for the task for the new workflow monitor component
"Workflow Monitor Agent SWI" by navigating to Administration > Server Management > Task.
If there are errors, check to see if all configurations have been properly performed. If not, repeat
the procedures detailed in “To generate the triggers” on page 118 after restarting the Siebel Server.
2 Navigate to Administration-User > Employee view. The list applet should contain the integration
user flag.
3 Configure a new integration user by setting the integration user flag to Y for a specific user.
3 Set "AIA Order Backup Path" to <the path where the xml files will be created on the Siebel Server
machine>/
4 Query for 'Validate Due Date' in the 'System Preference Name' field and set the 'System
Preference Value' to 3.
5 Query for 'Cancel Error Mode' in the 'System Preference Name' field and set the 'System
Preference Value' to 2.
In order to leverage the dynamic pricing procedure, customers have to perform following changes to
the existing repository.
The Siebel pricing module is available in multiple licensing modes and each mode is associated with
either the 'Basic Pricing Procedure' or the 'Dynamic Pricing Procedure'.
■ Basic Siebel Pricer functionality includes list price, volume discounts, and service pricing.
■ It leverages the variable maps that do not contain the XA child variable maps.
■ It leverages the variable maps that contain the XA child variable maps.
■ It is available only to those customers that have the 'Dynamic Pricer' license.
■ If you are running Siebel applications versions earlier than 8.1.1, you must modify the signals
mentioned in the following section manually.
Modifying Signals
Use the following procedure to modify signals.
To modify signals
1 Navigate to Administration - Order Management > Signals, query for each signal mentioned in
the following tables, and make the necessary modifications.
Signal: CalculatePriceAndCheckEligibility
Actions and Parameters:
Sequence: 1
Mode: N/A
Fields: N/A
Name Value
Variable Map - Row Set Default Pricing Eligibility Variable Map - Row Set
Signal: QuotesAndOrdersValidate
Actions and Parameters:
Sequence: 1
Mode: Order
Fields: N/A
Condition: N/A
Active: Y
Name Value
Variable Map - Row Set Default Pricing Eligibility Variable Map - Row
Set
Signal: VerifyItem
Actions and Parameters:
Sequence: 1
Mode: Agreement
Fields: N/A
Active: Y
Name Value
Sequence: 1
Mode: N/A
Fields: N/A
Active: Y
Name Value
Signal: CalculatePriceExternal
Actions and Parameters:
Sequence: 1
Mode: N/A
Fields: N/A
Condition: N/A
Active: N/A
Name Value
Sequence: 1
Mode: N/A
Fields: N/A
Condition: N/A
Active: Y
Name Value
Variable Map - Row Set Spread Discount Default Pricing Variable Map - Row Set
Signal: ApproveItem
Actions and Parameters:
Sequence: 1
Mode: Agreement
Fields: N/A
Active: Y
Name Value
Variable Map - Row Set Default Pricing Variable Map - Row Set
Signal: CalculatePrice
Actions and Parameters:
Sequence: 1
Mode: N/A
Fields: N/A
Active: Y
Name Value
Variable Map - Row Set Default Pricing Variable Map - Row Set
Signal: CalculatePriceAll
Actions and Parameters:
Sequence: 1
Mode: N/A
Fields: N/A
Active: Y
Name Value
Variable Map - Row Set Default Pricing Variable Map - Row Set
Signal: CalculatePrice_eSales
Actions and Parameters:
Sequence: 1
Mode: N/A
Fields: N/A
Name Value
Variable Map - Row Set Default Pricing Variable Map - Row Set
Signal: CalculatePriceAll_eSales
Actions and Parameters:
Sequence: 1
Mode: N/A
Fields: N/A
Action: Y
Name Value
Variable Map - Row Set Default Pricing Variable Map - Row Set
Signal: CalculatePrice_Configurator
Actions and Parameters:
Sequence: 1
Mode: N/A
Fields: N/A
Active: Y
Name Value
SubPSPWFName Dynamic Pricing Procedure
Variable Map - Row Set Default Pricing Variable Map - Row Set
Signal: CalculatePrice_Advisor
Actions and Parameters:
Sequence: 1
Mode: N/A
Fields: N/A
Active: Y
Name Value
Variable Map - Row Set Default Pricing Variable Map - Row Set
Signal: MergeIntoOnePackage
Actions and Parameters:
Sequence: 1
Mode: N/A
Fields: N/A
Active: Y
Name Value
Variable Map - Row Set Default Pricing Variable Map - Row Set
Signal: OrderTemplate
Actions and Parameters:
Sequence: 1
Mode: Order
Fields: N/A
Active: Y
Name Value
Variable Map - Row Set Default Pricing Variable Map - Row Set
Signal: OrderTemplateCopy
Actions and Parameters:
Sequence: 1
Mode: Order
Fields: N/A
Active: Y
Name Value
Variable Map - Row Set Default Pricing Variable Map - Row Set
Signal: OrderTemplateSelectItems
Actions and Parameters:
Sequence: 1
Mode: Order
Fields: N/A
Active: Y
Name Value
Variable Map - Row Set Default Pricing Variable Map - Row Set
Signal: QuoteTemplateCopy
Actions and Parameters:
Sequence: 1
Mode: Quote
Fields: N/A
Active: Y
Name Value
Variable Map - Row Set Default Pricing Variable Map - Row Set
Signal: QuoteTemplateSelectItems
Actions and Parameters:
Sequence: 1
Mode: Quote
Fields: N/A
Active: Y
Name Value
Variable Map - Row Set Default Pricing Variable Map - Row Set
Signal: SetFieldValue
Actions and Parameters:
Sequence: 1
Mode: N/A
Active: Y
Name Value
Variable Map - Row Set Default Pricing Variable Map - Row Set
Sequence: 1
Mode: Agreement
Fields: Product; Quantity Requested; Unit Price; Discount Amount; Discount Percent; Currency
Code; Item Price List; Covered Product Net Price
Active: Y
Name Value
Sequence: 1
Mode: Order
Fields: Product; Quantity Requested; Unit Price; Discount Amount; Discount Percent; Prod Prom
Name; Currency
Active: Y
Name Value
Variable Map - Row Set Default Pricing Variable Map - Row Set
Sequence: 1
Mode: Quote
Fields: Product; Quantity Requested; Unit Price; Discount Amount; Discount Percent; Prod Prom
Name; Currency Code; Item Price List; Covered Product Net Price
Active: Y
Name Value
Variable Map - Row Set Default Pricing Variable Map - Row Set
Mode: N/A
Fields: N/A
Condition: N/A
Active: Y
Name Value
Signal: GetProdPrice
Sequence: 1
Mode: N/A
Fields: N/A
Active: Y
Name Value
SubPSPWFName Dynamic Pricing Procedure
Variable Map - Context Default Pricing Variable Map - Context
Variable Map - Row Set Product Pricing Variable Map - Row Set
Signal: GetUserProdPrice
Sequence: 1
Mode: N/A
Fields: N/A
Active: Y
Name Value
Variable Map - Row Set Product Pricing Variable Map - Row Set
Mode: N/A
Fields: N/A
Condition: N/A
Active: Y
The ODI interface will be triggered to transport the required data for creating/updating Credit Alerts
from BRM into the Siebel EIM tables. EIM scripts will be then executed to load the data into the SFA
base tables.
2 Make sure that the Siebel EIM component is online and running properly. (Check this from the
Administration - Server Configuration and Administration - Server Management screens.)
3 To avoid data loss, do not restart the Siebel server while the EIM job is running.
4 After you have completed loading data for one country, make a backup copy of the EIM logs for
status verification. (These logs are located under siebsrvr/logs.)
User List
Use the following procedure to add users to the user list.
2 Add user name, User ID, and choose the "Siebel Administrator" responsibility.
5 Create a User List and add the users in the child applet.
The "SCE Users" user list is created for the product class/attribute sync feature. You can add the
users in the same user list. If the “SCE Users” list does not appear, create the list and add the
users in the same user list.
The following procedure describes how to add three runtime events to extract the email addresses
from user lists in the PreInvoke method of Business Components.
To add three runtime events to extract email addresses from users lists
1 Navigate to Administration - Run Time Events > Action Set.
Action 'GetEmailAddr' is added to get the email addresses from the user list.
"Parent BC Record Name";"Field Name in Child BC ";"BO Name ";"Parent BC";"Child BC"
For instance:
or
The following table describes the three run time events that are added.
Sequence Object Type Object Name Event SubEvent Action Set Name
Email Templates
Use the following procedure to view the email templates that have been added.
The following table describes the four templates that have been added:
Name Description
Attribute Defn Template To send email from the Attribute Definition view
Product Class Template To send email from the Product Class Definition
view
Workspace Attribute Defn Template To send attribute details from the Workspace view
in emails
Workspace Product Class Defn Template To send attributes from the Workspace view in
emails
2 To change the email body of the templates used to send emails from the workspace view,
navigate to Administration Communication > All Templates > Template Items.
The email templates detailed above are configured as user property values in the following Business
Components:
Communication Profile
Use the following procedure to add From Email Address, POP server name, and SMTP server name
in the communication profile.
To add From Email Address, POP server name, and SMTP server name
1 Navigate to Administration - Communications > Communications Drivers and Profiles.
■ Inbound: Yes
■ Outbound: Yes
4 Set the profile parameters in the grandchild Business Component using the following values as
an example:
The communication profile has to set in the user property in the Business Components listed in
the following table:
Recipient Group
The recipient group determines which Business Object is associated with the communication
template. Only primary Business Component fields and their child Business Component fields are
available to use in the template.
3 To set the recipient group, navigate to Administration - Communications > All Templates >
Advanced and select the recipient group from the drop-down list.
The LIC values of the recipient groups added in Step 2 are set in the user property of the Business
Components listed in the following table:
Recipient Group(LIC
Business Component User Property Value)
Enabling Compgrps
Use the following procedures to enable compgrps.
4 Type <Build>ses\siebsrvr\bin.
6 Run the command to verify how many components are enabled as "list compgrp".
9 After verifying that the command ran successfully, exit the application.
NOTE: The instance is located in the URL. For example, if the URL contains 16661 = qa1, 16662
= qa2 instance and so on.)
3 Navigate to <Build>ses\siebsrvr\bin.
smgr <enter>
7 After verifying that the command ran successfully, exit the application.
To prepare the Siebel Server for CRM Desktop, perform the following tasks:
1 Importing Changes to the Siebel Repository from a Batch File on page 142
2 Importing Changes to the Siebel Repository from SIF Files on page 143
2 Make a note of the value that is set for the SymStrPrefix parameter.
Keep this note. You will need it later to set the SymStrPrefix parameter back to the original value.
SymStrPrefix = SBL_
5 If Siebel Tools is open, then exit out of it, and then open it.
ACR464-SIA8112\repository\projects_to_lock.txt
8 In the Projects list, make sure the Locked property contains a check mark for each project that
is listed in the projects_to_lock.txt file.
It is recommended that you check these projects out to your local database, perform the
configuration, and then check them back into the server database after you complete the
configuration.
9 Edit the repository_import.bat file to reflect the database, username, folder names, Siebel Tools
installation directories, and other information that is specific to your environment.
■ Applet.log
■ Business Component.log
■ Business Object.log
■ Business Service.log
■ Class.log
■ DLL.log
■ Integration Object.log
■ Link.log
■ Pick List.log
■ Screen.log
■ Symbolic String.log
■ Table.log
■ View.log
If the log files indicate a problem, then create a service request (SR) on My Oracle Support.
Alternatively, you can phone Global Customer Support directly to create a service request or get
a status update on your current SR. Support phone numbers are listed on My Oracle Support.
You can also contact your Oracle sales representative for Oracle Advanced Customer Services to
request assistance from Oracle's Application Expert Services.
a Open Siebel Tools, choose the Tools menu, and then the Import From Archive menu item.
b In the Select Archive to Import dialog box, open the following file:
Application\Application-Update.sif
c In the Import Wizard-Preview dialog box, make sure the following option is chosen, and then
click Next:
Merge the object definition from the archive file with the definition in the repository
Siebel Tools displays the Import Wizard-Review Conflicts and Actions dialog box.
You can view the status bar at the bottom of the dialog box to monitor progress.
e If the Conflicting Objects window of the Import Wizard-Review Conflicts and Actions dialog box
contains an item, then see “Resolving Conflicts” on page 144. Otherwise, continue to Step f.
■ Business Object\BusinessObject-Update.sif
■ Table\base\Table-Update.sif
■ Business Component\BusinessComponent-Update.sif
3 Examine the following log file to make sure all imports executed successfully:
Siebel\tools\temp\importlog.txt
5 Set the SymStrPrefix parameter in the tools.cfg file to the original value you noted in Step 2 on
page 142.
7 If Siebel Tools is open, then exit out of it, and then open it.
Resolving Conflicts
1 In the Import Wizard-Review Conflicts and Actions dialog box, expand the tree and then click an
object so that the Object Differences window populates.
2 Compare the object that appears in the Object Differences window to the child objects that are
described in “Changes Made as a Result of Importing SIF Files” on page 147.
a If the object appears in “Changes Made as a Result of Importing SIF Files” on page 147, and if
there is no conflict, then do not adjust the default setting that Siebel Tools makes.
For more information, see “Example of Using the Value from the SIF File” on page 145.
b If the object does not appear in “Changes Made as a Result of Importing SIF Files” on page 147,
then right-click the object in the Object Differences window, and then choose Repository.
For more information, see “Example of Using the Value from the Repository” on page 145.
c If the object appears in “Changes Made as a Result of Importing SIF Files” on page 147, and if
there is a conflict, then create a service request (SR) on OracleMetaLink 3.
For more information, see “Example of a Conflict That Requires Additional Assistance” on
page 145.
4 If other objects appear in the Conflicting Objects window, then repeat Step 3 for each object until
all conflicts are addressed.
5 Click Next.
■ Some differences for the Screen Menu Item object, including different Text for the Account
Screen object and a different Sequence for the Activities Screen object.
These differences are not intended. The Page Tab, Account Screen, and Activities Screen objects do
not appear in “Changes Made as a Result of Importing SIF Files” on page 147. Therefore, you must set
Action to Repository for each of these objects in order to keep the current repository values.
In this situation, it is recommended that you create a service request (SR) on My Oracle Support.
Alternatively, you can phone Global Customer Support directly to create a service request or get a
status update on your current SR. Support phone numbers are listed on My Oracle Support. You can
also contact your Oracle sales representative for Oracle Advanced Customer Services to request
assistance from Oracle's Application Expert Services.
2 In the Tables list, issue the following query in the Name property:
3 Click Apply/DDL.
4 In the Choose option dialog box, make sure the Apply option is chosen, and then click OK.
5 In the Apply Schema dialog box, choose Current Query in the Tables drop-down list, and then
enter the following information according to the type of database into which you are applying
this schema change. These values might be different for your environment. Check with your
database administrator if you are not sure about the correct values to enter.
For more information, see Developing and Deploying Siebel Business Applications.
6 Click Apply.
ACR464-HOR8112\Seed_import.bat
2 Edit the Seed_import.bat file to reflect the database, username, folder names, Siebel Tools
installation directories, and other information that is specific to your environment. The required
parameters are documented in the file.
3 Open a DOS command line and then run the Seed_import.bat file.
4 Review the following files to make sure the import completed successfully:
The following applications are changed: The following applications are changed:
■ Account Territory
■ Assignment Group
■ Industry
■ Organization
■ Position
Employee The following business object components are added to Siebel Business
Applications and Siebel Industry Applications:
■ Employee Position
■ Employee Responsibility
Opportunity The following business object components are added to Siebel Business
Applications and Siebel Industry Applications:
■ Assignment Group
■ Opportunity AssignmentGroup
■ Opportunity Position
Position The following business object components are added to Siebel Business
Applications and Siebel Industry Applications:
■ Assignment Group
Adds the following columns to the S_EVT_ACT Makes the following changes to the S_EVT_ACT
table: table:
Changes the Text Length of the EMail Addr field from 50 to 100.
Contact Changes the Text Length of the Email Address field from 50 to 100.
Position Changes the Text Length of the Active Email field from 50 to 100.
Business Address Changes the Text Length of the Email Address field from 50 to 100.
NOTE: For more information about ACR 467 and about Siebel Financial Services Customer Order
Management for Banking functionality, see Siebel Order Management Guide Addendum for Financial
Services. To access this guide, from within My Oracle Support, navigate to the Knowledge tab and
search for Doc ID 1171542.1.
■ \LMU
■ \SeedData
■ \REPOSITORY
■ \WORKFLOWS
■ \Schema
❏ Table Asset
❏ Table FinAccounts
❏ Table Marketing
❏ Table Order
❏ Table Quote
3 Navigate to Tools > Import from Archive, and import the Table.sif file.
4 Navigate to the Siebel\tools\temp\importlog.txt file to verify that the objects imported correctly.
5 Select the table or tables that you want to apply to the physical database, click the Apply/DDL
button, and select Apply.
7 In the Apply Schema dialog box, enter the appropriate values for your database platform.
a For MSSQL, enter the appropriate values in the Database user, Database user password, and the
ODBC data source fields.
b For Oracle, enter the appropriate values in the Table space, Index space, Database user,
Database user password, and the ODBC data source fields.
c For DB2, enter the appropriate values in the Table space, 16K table space, 32K table space,
Index space, Database user, Database user password, and ODBC data source fields.
d For DB2/390, enter storage control file information, as well as information in the Database user,
Database user password, and ODBC data source fields.
NOTE: If you are implementing ACR 467 on DB2, you need to generate the storage control file.
For information aobut how to do this, see Implementing Siebel Business Applications on DB2 for
z/OS. This guide is available on the Siebel Bookshelf at http://www.oracle.com/technetwork/
documentation/siebel-087898.html.
CAUTION: You must import the Table.sif file before you import the EIM.sif file.
❏ EIM Activity
❏ EIM Quote
10 Importing the EIM.sif file using the Tools > Import from Archive function. Use the Merge option
within the Import Wizard.
11 Navigate to the Siebel\tools\temp\importlog.txt file to verify that the objects imported correctly.
12 Repeat Step 5 through Step 7 to apply the DDL for EIM.sif.
13 Open tools.cfg from <Tools Install Directory>\Bin\Enu and verify the [Siebel] section. Make sure
that the SymStrPrefix entry has been set to SBL_
[Siebel]
……..
SymStrPrefix = SBL_
……..
❏ Account (SSE)
❏ Asset Management
❏ Cfg JS
❏ Contact
❏ Contact (SSE)
❏ FINS Account Origination (Create this project if it does not already exist.)
❏ Household
❏ LS Pharma Call
❏ LS Pharma Signature
❏ MACD Performance
❏ Oppty (SSE)
❏ Order Entry
❏ Product Selection UI
❏ Quote
❏ Quote (UI)
❏ Symbolic Strings
❏ Corresp
❏ Account
❏ Mail Agent
❏ Accessibility
❏ FINS Captive Finance - Fin Acct
❏ LS Pharma Compliance
❏ PUB Case
❏ Schema
15 Import the rest of the SIF files from the REPPATCH\ACR467\REPOSITORY folder into Siebel Tools
using the Import from Archive function.
If you have not locked the required projects, you may receive a warning error message. Use the
Overwrite option.
16 Import the SIF files from the following subfolders under the REPPATCH\ACR467\REPOSITORY
folder:
❏ Applet
❏ Application
❏ Business Component
❏ Business Object
❏ Business Service
❏ Integration Object
❏ Project
❏ Screen
❏ Symbolic String
Use the following procedure to perform batch import of the SIF files.
SET PCDTOOLSPATH=..\..\..
SET PCDDATASRC=ServerDataSrc
SET PCDUSERNAME=<LOGIN>
SET PCDPASSWORD=<PWD>
Use the following procedure to import the seed data for ACR 467.
a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC),
navigate to the System DSN tab, and click Add.
b Select the "Siebel Oracle90" driver (from Datadirect Technologies).
❏ For Oracle, enter the TNS service name that you created to connect Siebel Tools to the
database.
2 Navigate to the directory where you installed Siebel Tools and change the directory to
REPPATCH\ACR467.
3 Before executing the next step, make sure that the dataimp.exe file exists in the <Tools Install
Directory>/bin directory.
4 Depending upon the language that you are installing, complete either Step 5 or Step 6.
<Tools Install Directory> - Replace with your Siebel Tools install directory
b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
6 For languages other than ENU, complete the following:
Customers who are installing languages other than ENU need to import two .dat files - the
base ENU seed.dat and the locale specific seed_locale_XXX.dat, where XXX is the language
code.
<Tools Install Directory> - Replace with your Siebel Tools install directory
<ODBC Source Name> - Replace with the ODBC name created in Step 1
c Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure import completed
successfully.
7 The following steps are only necessary for customers who are installing languages other than
ENU:
a Within Siebel Tools, navigate to Tools > Utilities > Locale Management to import LMU files for
the specific language from the LMU folder into Siebel Tools.
c Click the Import tab, browse to locate the LMU file you want to import, and click Import.
9 Within Siebel Tools, navigate to Menu > View > Options, select the Scripting tab, and specify the
following path for the browser script compilation folder.:
10 Navigate to Tools > Compile Projects > All Projects option, compile the projects, and save the
SRF file to <Siebel Server Install folder>\objects\ENU\siebel_sia.srf on the installed Siebel
Server.
New/
Process Name Modified? Project
FINS AcctOrig Apply For Product - Account New FINS Account Origination
FINS AcctOrig Apply For Product - Contact New FINS Account Origination
FINS AcctOrig Apply For Product - Household New FINS Account Origination
FINS AcctOrig New Products & Services Process New FINS Account Origination
FINS AcctOrig Set Applicant Group - Order Sub New FINS Account Origination
New/
Process Name Modified? Project
FINS AcctOrig Set Applicant Group - Order New FINS Account Origination
FINS AcctOrig Set Applicant Group - Quote Sub New FINS Account Origination
FINS AcctOrig Set Applicant Group - Quote New FINS Account Origination
SIS OM Disconnect Products & Services Process - Modify SIS OM Base Architecture
Contact
SIS OM Modify Products & Services Process - Modify SIS OM Base Architecture
Contact
SIS OM New Products & Services Process - Modify SIS OM Base Architecture
Contact
SIS OM Suspend / Resume Products & Services Modify SIS OM Base Architecture
Process - Contact
b Right-click on Workflow Processes (the right-side pane) and import the .xml file into Siebel Tools
from the Workflows folder. Refer to the list of workflows in the preceding table to know which
project these workflows need to be imported into.
c Check the status of the workflow process. If it is In-Progress, then make it complete by deploying
the Workflow process. Do not click the Deploy + Activate button, as doing so will yield an error
message. Click the Deploy button only.
NOTE: You may receive the "This is an invalid Workflow…" error message while deploying the
modified workflows from the list. Ignore the error and click Yes.
d Repeat Step b through Step c for of all the workflows in the folder.
For more information about Siebel Client Sync functionality, see Siebel Client Sync Guide on the
Siebel Bookshelf http://www.oracle.com/technology/documentation/siebel.html.
■ Before you install Client Sync SDK7.x, it is recommended that you unregister Intellisync
SDK5.5 dlls if they are installed.
❏ vcredist_x86.exe
❏ setup.exe
❏ SiebelClientSync.msi
Before you begin your installation, copy the translation.txt file from the <New Client Sync>\bin\enu
directory and replace the existing one under <Siebel Server Base>\siebsrvr\bin\enu with the copy.
The following examples show how to unregister each of the Intellisync connectors from the
command line. In the examples, replace "$(SiebelRoot)" with the appropriate path to the Siebel
Client Sync product directory.
■ Microsoft Outlook
❏ regsvr32.exe /u
"$(SiebelRoot)\bin\connectors\MS_Outlook_Connector\ilxolkCompanion.fil"
■ Lotus Notes
❏ regsvr32.exe /u "$(SiebelRoot)\bin\connectors\Lotus_Notes_Connector\ilxlnic.dll"
■ GroupWise
❏ regsvr32.exe /u
"$(SiebelRoot)\bin\connectors\Groupwise_6.5.x_Connector\GWEMAILCONN.dll"
❏ regsvr32.exe /u
"$(SiebelRoot)\bin\connectors\Groupwise_6.5.x_Connector\GWEMAILCONNApi.dll"
2 Unregister the Siebel Client Sync COM servers by issuing the following commands from the
command line:
regsvr32 /u cxlserver.dll
regsvr32 /u sscpumaconn.dll
regsvr32 /u stcpumaapi.dll
NOTE: If you are installing a language other than ENU, select your language from the
appropriate directory. For example, a customer who is installing the DEU application would use
DEU_Installer within bin\DEU.
3 Double-click on setup.exe to install the new Siebel Client Sync application. When you are
prompted to give the folder path for installing new Siebel Client Sync, accept the default path or
give a path other than the original Siebel Sync 8.1.1.1 installation path.
For example: If Siebel Sync 8.1.1.1 is installed in D:\SiebelSync, then install ACR 468 for Siebel
Sync in D:\ACR468B.
4 After the new Siebel Client Sync application is installed, double-click on the Siebel Client Sync
shortcut that was created during the installation and provide the User ID, Password, and Connect
String.
Subcategory: Deduplication
While merging two contacts, an error is thrown:Could not find 'Class' Named 'Merge Service ODOP'.
This object is inactive or non-existent. (SBL-DAT-00144)
The MergeAction runtime event refers to the the Merge Service ODOP business service, which is not
present in the repository.
1 Log into the Siebel application, and navigate to Administation - Runtime Events > Action Sets.
4 Navigate to the Events view, and from the applet menu, select the Reload Runtime Events menu
option.
1 Within Siebel Tools, navigate to Business Component and query for MACD Order Entry - Orders
or MACD Quote.
2 In MACD Order Entry - Orders add a field with the following values:
❏ Name: As Of Date
❏ Column: STATUS_DT
❏ Type: DTYPE_UTCDATETIME
❏ Name: As Of Date
❏ Column: STATUS_DT
❏ Type: DTYPE_UTCDATETIME
4 Navigate to Integration Object, and query for SIS OM Order or SIS OM Quote.
5 Add the Status As Of Date field to IC MACD Quote, and add the As Of Date field to IC MACD Order
Entry - Orders.
7 Navigate to Business Service User Properties, and add a new user property with the following
values:
1 Log into Siebel Tool, and query for the SWICancel Sales Order workflow.
2 Click Revise in the WF/Task Editor Toolbar to create a new version of the completed workflow and
increment the version number
3 Right-click SWICancel Sales Order (the one with status In Progress) and select Edit Workflow
Process.
4 In the Workflow Designer, select the Siebel Operation Step called "Update Fulfillment Mode and
Status for Header".
5 Under the Input Field Argument tab in the Multi-Value Property Window for the Update Fulfillment
Mode and Status for Header operation step, add the following two new records to configure the
input arguments:
6 Add a new Siebel Operation Step between "Update Fulfillment Mode and Status for Header"
(Siebel Operation Step) and "Submit" (Sub Process).
7 Right-click, select View Properties Window and modify the properties of the Siebel Operation Step
as follows:
Operation Update
Name Update Fulfillment Status and Status Context for Line Items
8 Under the Input Field Argument tab in the Multi-Value Property Window for the preceding step,
add the following new records to configure the input arguments:
9 Under the Search Spec Input Arguments tab in the Multi-Value Property Window for the preceing
step, add the following new records to configure the search specification:
E
Order Entry - Orders Order Entry - Line Expression "[Order Header Id] ='"
Items + [&Object Id] + "'"
The Effective Adjustment field stores only the Date field not the time value.
Before you begin, within My Oracle Support, navigate to the Knowledge tab and search for Doc ID
557191.1. Copy the FR_12-1ZV9SD1_AIA25_Invoice.sif file attached to the article.
Table Changes
Use the following procedure to edit the S_INV_ADJ table.
2 Import the "FR_12-1ZV9SD1_AIA25_Invoice.sif " file using merge as the Conflict Resolution
Option.
2 Change the following column for the Adjustment Effective Date field for the business component:
Name Value
Type DTYPE_UTCDATETIME
Name Value
Type DTYPE_UTCDATETIME
2 Change the following column for the Adjustment Effective Date field:
Name Value
Type DTYPE_UTCDATETIME
2 Change the following column for the Adjustment Effective Date field:
Name Value
Type DTYPE_UTCDATETIME
2 Change the following column for the Adjustment Effective Date field:
Name Value
Type DTYPE_UTCDATETIME
2 Change the following column for the Adjustment Effective Date field:
Name Value
Type DTYPE_UTCDATETIME
2 Change the following column for the Adjustment Effective Date field:
Name Value
Type DTYPE_UTCDATETIME
3 Change the type for the Adjustment Effective Date integration component field:
Name Value
4 Query for the SIA Invoice Adjustment External Items integration component.
5 Change the following Data Type for the Adjustment Effective Date integration component field:
Name Value
3 Change the type for the Adjustment Effective Date integration component field:
Name Value
4 Query for the SIA Invoice Adjustment External Items integration component.
5 Change the Data Type for the "Adjustment Effective Date integration component field:
Name Value
In Siebel 8.1.1.3, product synchronization between the Siebel application and BRM fails.
2 In the bottom applet, query for the Product integration component map from the bottom applet.
3 Within the Integration Field Map applet, click Query, and enter “Pricing Commit Type” in the
Target Field Name field.
6 Within the Integration Field Map applet, click Query, and enter "Dynamic Discount Method" in
Target Field Name.
To address CR 12-1YK6RG0
1 From within the Siebel application, navigate to Site Map > Administration - Order Management
> Variable Maps and query for the"Default Pricing Variable Map - Row Set" variable map.
2 Rename the variable map to "Default Pricing Variable Map - Row Set - original".
3 Copy the variable map from the applet-level menu, and rename it as "Default Pricing Variable
Map - Row Set".
5 Follow Step 1 through Step 4 for the "Default Pricing Eligibility Variable Map - Row Set" variable
map.
Siebel workflow process manager leaks memory and crashes in performance, scalability, and
reliability (PSR) testing after 20 hours of running with zero seconds of think time.
Workaround: Enable memory-based recycling on workflow process manager. For information about
configuring memory-based server component recycling, refer to Siebel System Administration Guide
on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.
No error occurs when a Follow On order is submitted after the Base Order is cancelled.
To address CR 12-1XTI4LP
1 Within the Siebel application, edit the Change the Submit Order workflow
(SISOMBillingSubmitOrderWebService) to add this logic:
a For each root line item, check if it has Base Order Line Item Id.
c Check if the status of the order is Pending. If it is Pending, the base order was not submitted.
Enter an error message saying, 'Submit base order %1 before follow-on order'.
NOTE: Implement this logic only if you are using follow-on orders, as this logic will affect the
time that it takes to submit an order.
To address CR 12-1XTI4NO
1 Within the Siebel application, edit the Change the Submit Order workflow
(SISOMBillingSubmitOrderWebService) to add this logic:
a For each root line item, check if it has Base Order Line Item Id.
c Check if the status of the order is Pending. If it is Pending, the base order was not submitted.
Enter an error message saying, 'Submit base order %1 before follow-on order'.
NOTE: Implement this logic only if you are using follow-on orders, as this logic will affect the
time that it takes to submit an order.
Sales Order Form Buttons Not Disabled After Cancel Order Starts
Category: Comm Media Energy
After clicking the Cancel Order button, all other buttons on the Sales Order form are not disabled,
so users can press buttons to interfere with cancel processing.
To address CR 12-1XTI4UE
1 Navigate to Siebel Tools > Applets and query for "Order Entry - Order Form Applet Dashboard
(Sales)".
3 Query for CanInvokeMethod*, and verify that all of the buttons that need to be disabled are
present. If they are not present, you need to create CanInvokeMethod:Method name value
To address CR 12-1XVFM9R
■ It is recommended that you use the Favorites menu option instead of the Copy Orders menu
option for Asset-Based Ordering (ABO) flows. This is because copying AssetIntegrationId does
not work for new orders, and Modify or Delete orders should not generate new
AssetIntegrationIds.
■ CR 12-1TU8OYZ
Description: The Discount Override fix is not working in MACD for Non-Residential Accounts
(asset-quote).
Workaround: Contact Technical Support for the workaround for this issue.
■ CR 12-1TK6WV1
Description: Suspend/Resume and move charges are applied to Simple Service Bundles in
Nested SBs after reprice.
Description: Error upon clicking the Revise button within Sales Order > Line Items tab.
3 Query for the Order Entry - Order Form Applet Dashboard (Sales) applet.
■ CR 12-1UVNZ65
Description: Net Price is carried forward for One-Time Products in MACD Operation.
To address CR 12-1UVNZ65
1 Within the Siebel application, navigate to the Sales Order screen.
2 Click the List link and navigate to the Sales Order Details screen.
3 Drill down on the Order # and navigate to the Line Items view.
4 Within the Line Items list applet, select Reprice All from the menu.
■ CR 12-1UK1DKW
Description: The Cancel Error Mode system preference default value should be '3'.
To address CR 12-1UK1DKW
1 Within the Siebel application, navigate to Administration - Application > System Preferences.
2 Within the System Preference Name field, query for “Cancel Error Mode” and set the value of the
System Preference field to 3.
■ CR 12-1T03IG9
Description: When the due date of a root product in a Customizable Product is nullified, order
validation does not occur.
To address CR 12-1T03IG9
1 Within the Siebel application, navigate to Site Map > Administration - Data Validation.
2 Click the Ruleset hyperlink, and query for ‘SWI Order Validation Rule Set’ in the Ruleset applet.
4 Click the ‘SWI Order Validation Rule Set’ hyperlink, and query for ‘SWI Validate Due Date’ in the
Rules applet.
The AIA251 folder that you create will contain the following subfolders and files:
■ \ACR474_Workaround. This file contains the Release Notes and workaround information.
■ \8113_Addendum.
The ACR474 folder that you create will contain the following subfolders:
■ \DMGSchemaChanges
■ \EIM
■ \HTML
■ \LMU
■ \SeedData
■ \SIFFiles
■ \WebTemplates
■ \WFs
Use the following procedure to apply the schema changes to the server database.
NOTE: The following instructions refer to the folders specified in Step 2 in the previous task.
The following two procedures describe how to import the ACR463_Tables.sif and
ACR463_EIMTables.sif files into the repository.
The ACR463_Tables.sif file has all the changes for the following:
■ S_ALERT_CUT
■ S_ADDR_PER
■ S_ADDR_PER_UCMX
■ S_ASSET
■ S_BULK_REQ
■ S_CONTACT
■ S_CON_ADDR
■ S_INV_PROF
■ S_INVOICE_ADJ
■ S_ORDER
■ S_ORDER_ITEM
■ S_ORG_EXT
■ S_PROD_INT
■ S_QUOTE_ITEM
■ S_SRV_ORD_FAIL
■ S_SRV_REQ
■ S_SPL_RATE_ITEM
■ S_SPL_RATE_LST
❏ CUT Newtable
❏ Table Asset
❏ Table BulkRequest
❏ Table Invoice
❏ Table Order
❏ Table Organization
❏ Table Product
❏ Table Quote
❏ Table FleetManagement
❏ Table Person
2 Use the Siebel Tools Import from Archive function to read this file and create the tables in the
repository. The "merge" option should be used while importing this file.
The ACR463_EIMTables.sif file has all the changes for the following:
■ EIM_ASSET
■ EIM_ASSET1
■ EIM_ALERT_CUT
■ EIM_INVOICE
■ EIM_ORDER
■ EIM_ORDER1
■ EIM_ORDER_ITEM1
■ EIM_PROD_INT1
■ EIM_QUOTE
■ EIM_QUOTE_IT1
❏ EIM Asset
❏ EIM Invoice
❏ EIM Order
❏ EIM Product
❏ EIM Quote
❏ EIM BulkRequest
❏ EIM CIF
❏ EIM FleetManagement
❏ EIM Organization
❏ EIM Person
2 Use the Siebel Tools Import from Archive function to read this file and create the tables in the
repository. The "merge" option should be used while importing this file.
■ S_ASSET
■ S_CONTACT
■ S_CONTACT_BU
■ S_DOC_QUOTE
■ S_OPTY
■ S_OPTY_BU
■ S_ORDER
■ S_ORDER_ITEM
■ S_ORDER_ITEM_OM
■ S_ORDER_STOP
■ S_ORDPART_MVMT
■ S_ORG_BU
■ S_ORG_EXT
■ S_ORG_GROUP
■ S_PRI_LST
■ S_PRI_LST_ITEM
■ S_PROD_INT
■ S_PROD_INT_BU
■ S_QUOTE_ITEM
■ S_REVN
■ S_UCM_ADDR_PER
■ S_UCM_ASSET
■ S_UCM_CONTACT
■ S_UCM_ORGGRP
■ S_UCM_ORG_EXT
■ S_UCM_PRIVACY
New Tables:
■ S_INTG_DEL_TXN
■ S_ORG_GRP_UCMX
■ S_PRD_USRDEFATR
❏ Table Asset
❏ Table CIF
❏ Table FieldService
❏ Table FleetManagement
❏ Table Forecast
❏ Table Household
❏ Table NetworkOrderManagement
❏ Table OnPremise-OnDemand
❏ Table Opty
❏ Table Order
❏ Table Organization
❏ Table Person
❏ Table PriceList
❏ Table Product
❏ Table Quote
2 Use the Siebel Tools Import from Archive function to read this file and create the tables in the
repository. The "merge" option should be used while importing this file.
■ EIM_ACCOUNT
■ EIM_ACCOUNT1
■ EIM_ASSET1
■ EIM_CONTACT
■ EIM_CONTACT2
■ EIM_GROUP
■ EIM_GROUP_DTL
■ EIM_OPTY
■ EIM_OPTY_DTL
■ EIM_ORDER1
■ EIM_ORDER_FM
■ EIM_ORDER_ITEM
■ EIM_ORDER_ITEM1
■ EIM_ORD_ITEM2
■ EIM_ORG_BU
■ EIM_ORG_INT
■ EIM_PART_MVMT
■ EIM_PRI_LST
■ EIM_PROD_INT
■ EIM_PROD_INT1
■ EIM_PROD_INT_BU
■ EIM_QUOTE1
■ EIM_QUOTE_IT2
■ EIM_REVN
■ EIM_UCM_ADRPER
■ EIM_UCM_ASSET
■ EIM_UCM_CON
■ EIM_UCM_ORG
■ EIM_UCM_ORGGRP
■ EIM_UCM_PRIVCY
❏ EIM Asset
❏ EIM CIF
❏ EIM FieldService
❏ EIM FleetManagement
❏ EIM Forecast
❏ EIM Household
❏ EIM Opty
❏ EIM Order
❏ EIM Organization
❏ EIM Person
❏ EIM PriceList
❏ EIM Product
❏ EIM Quote
2 Use Siebel Tools Import from Archive function to read this file and create the tables in the
repository. The "merge" option should be used while importing this file.
1 Create an ODBC entry for the database where you plan to import the seed data.
a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC),
navigate to the System DSN tab, and click Add.
b Select the "Siebel Oracle90" driver (from Datadirect Technologies).
❏ For Oracle, enter the TNS service name that you created to connect Siebel Tools to the
database.
2 Navigate to the directory where you installed Siebel Tools and change the directory to
REPPATCH\AIA251\ACR474\SeedData\ACR463_SEED.
3 Before executing the next step, make sure that the dataimp.exe file exists in the <Tools Install
Directory>/bin directory.
4 Seed data import includes mono-language seed-data import and language seed-data import. Use
either Step a or Step b depending upon the language that you are installing.
Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that
the import completed successfully.
<Tools Install Directory> - Replace with your Siebel Tools install directory.
<ODBC Source Name> - Replace with the ODBC name created in Step 1.
c Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the
import completed successfully.
a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC) >
System DSN tab, and click Add.
b Select the Siebel Oracle90 driver (from Datadirect Technologies).
e For Oracle, enter the TNS service name that you created to connect Siebel Tools to the database.
2 Navigate to the directory where you installed Siebel Tools and change the directory to
REPPATCH\ACR474.
3 Before executing the next step, make sure that the dataimp.exe file exists in the <Tools Install
Directory>/bin directory.
<Tools Install Directory> - Replace with your Siebel Tools install directory
<ODBC Source Name> - Replace with the ODBC name created in Step 1
<Database Platform> - Replace with the database platform (ORACLE, DB2UDB or MSSQL)
5 Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
Depending upon the language that you are installing, complete either Step XX or Step XX.
<Tools Install Directory> - Replace with your Siebel Tools install directory
<ODBC Source Name> - Replace with the ODBC name created in Step 1
<Database Platform> - Replace with your database platform (ORACLE, DB2UDB or MSSQL)
b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
7 For customers using languages other than ENU:
a Run the following commands after importing the ACR474_Seed.dat file for importing the locale
specific seed_locale_XXX.dat, where XXX is the language code.
<Tools Install Directory> - Replace with your Siebel Tools install directory
<ODBC Source Name> - Replace with the ODBC name created in Step 1
b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
c Run the following commands after importing seed_locale_XXX.dat file for importing the locale
specific AIA251_seed_locale_XXX.dat, where XXX is the language code.
<Tools Install Directory> - Replace with your Siebel Tools install directory
<ODBC Source Name> - Replace with the ODBC name created in Step 1
d Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
[Siebel]
……..
SymStrPrefix = SBL_
……..
NOTE: After changing the tools.cfg file, make sure to log out of Siebel Tools and log in again to
apply the changes.
■ ATP
■ Account
■ Account (SSE)
■ Assignment (SSE)
■ Asset Management
■ Bitmap
■ Cfg RTC
■ CMU Billing BC
■ CMU Billing Product
■ CMU Billing UI
■ CMU Billing Integration
■ COM Workflows
■ CUT Billing
■ CUT Profile
■ CUT Newtable
■ Contact
■ Contact (SSE)
■ Comm Manager
■ Communication
■ Division
■ Dock
■ Dock KDI
■ Docklog
■ Dockses
■ Eligibility Compatibility
■ EIM Asset
■ EIM CIF
■ EIM Household
■ EIM Organization
■ EIM Person
■ EIM Invoice
■ EIM Order
■ EIM Product
■ EIM Quote
■ EIM BulkRequest
■ EIM Organization
■ EIM Service Request
■ Employee
■ FS Agreement
■ Fleet Management
■ ISS Context
■ LS DB Action
■ MACD Performance
■ Order Entry
■ Opportunity Management
■ Oppty
■ Oppty (SSE)
■ PMP
■ Price List
■ Product
■ Product (SSE)
■ Product Integration
■ Product Selection UI
■ Quote (UI)
■ Quote
■ Service
■ Srvagree
■ Srvagree (SSV)
■ Symbolic Strings
■ Template (Order)
■ Table Asset
■ Table BulkRequest
■ Table Invoice
■ Table Order
■ Table Organization
■ Table Product
■ Table Promotions
■ Table Quote
■ Table CIF
■ Table Person
■ Table FleetManagement
■ Table FieldService
■ Table Forecast
■ Table Household
■ Table NetworkOrderManagement
■ Table Opty
■ Table PriceList
■ Table OnPremise-OnDemand
■ UMSUI
■ eService Billing
■ eAuto Product
NOTE: If you have implemented ACR 471, you must merge repository and workflow changes to
make sure that ACR 471 and ACR 474 are compatible:
3 Import the rest of the SIF files from the SIFFiles folder into Siebel Tools:
a Place the BatchImportAcr474.bat file in <Tools Install Directory>/bin, edit the file to replace
“REPPATCH\ACR474” with “REPPATCH\AIA251\ACR474,” save the file, and then execute it.
For further information on batch import, see the topic, “Importing Objects from an Archive File
Using the Command-Line Interface” in Using Siebel Tools on the Siebel Bookshelf library.
b Check the logs in <Tools Install Directory>/importLogsAcr474 directory.
c If you have not locked the required projects, you might receive a warning error message. Create
the projects and lock them the projects are not available by default.
d The Fleet Management and Table OnPremise-OnDemand projects are not available by default.
You must create them before you execute the BatchImportAcr474.bat file.
NOTE: The following steps apply only to customers who are installing languages other than ENU.
a Navigate to Select > Tools > Utilities > Locale Management to import LMU files for the specific
language from the LMU folder into Siebel Tools.
b Select Source Language = English American
d Click the Import tab and then Browse to locate the LMU file you want to import and click Import.
6 Within Siebel Tools, navigate to Menu > View > Options > Scripting tab, and specify the following
path for the Browser script compilation folder.
7 Compile all of the projects using the Compile Projects > All Locked Projects option and save the
SRF file to the <Siebel Server Install folder>\objects\ENU\siebel_sia.srf folder on the installed
Siebel server.
8 Copy the Web Template file CZConfigurator.swt and CZView.swt from the WebTemplate folder
into Siebel Server <Siebel Server Install folder >\WEBTEMPL.
9 Copy the CZReturn.html file from the HTML folder into the SWE Server <SWE Server Install folder
>\eappweb\PUBLIC\enu.
10 From the EIM folder, copy the files with extension "ifb" in Siebel Server <Siebel Server Install
folder >\ADMIN.
■ Import the "SWIOrderUpsert_O2C" workflow first and then import the "SWIOrderUpsert"
workflow.
■ Import the "SWISendOrder" workflow first and then import the "Submit Order ASI" workflow.
■ Import the "SWISendQuote" workflow first and then import the "Submit Quote ASI"
workflow.
■ Import the "Oracle Configurator Load" workflow first and then import the "SWI Configurator
Load" workflow.
■ Import the "SWISetTBOEndDate" workflow first and then import the "Dynamic Pricing
Procedure" workflow.
ABO Bulk Request - Clear Exception Process Workflow ABO Bulk Request
ABO Bulk Request - Parallel Sub Process Workflow ABO Bulk Request
ABO Bulk Request - Prepare Action Set Sub-Process Workflow ABO Bulk Request
ABO Bulk Request Add Item Customize Process ABO Bulk Request
SIS OM Suspend / Resume Products & Services Process SIS OM Base Architecture
NOTE: The asterisks denote workflows that were not modified for ACR 474.
b Right-click on the right side pane called Workflow Processes and import the .xml file into Siebel
Tools from the Workflows folder. Refer to the list of workflows in the table above to know which
project these workflows need to be imported into.
NOTE: The following step is required if you have installed AIA 2.5 IPS 1 or higher.
Revise the following workflows, change the Process Property ‘UTCCanonical’ default value
from ‘N’ to ‘Y’. Publish, and then activate.
❏ SISOMBillingSubmitOrderWebService
❏ SWIAdjustmentStatusUpdate
❏ SWIOrderUpsert
❏ SWIOrderUpsert_O2C
❏ SWIOrderUpsertSubProcess
❏ SWIQuoteUpsert
❏ SWISendATPCheck
❏ SWISendATPCheckLine
❏ SWISendCalculateShippingCharge
❏ SWISendCreditCheck
❏ SWISendOrder
❏ SWISendPaymentAuthorization
❏ SWISendQuote
c Check the status of the Workflow process. If it is In-Progress, then make it complete by
deploying the Workflow process.
For Siebel applications version 8.0 and above, the button to mark the workflow status
complete is Publish/Activate. To view this button, navigate to View menu > Tool Bar > WF/
Task Editor.
NOTE: If any of the workflows fail to import, manually activate them within the application.
d Repeat Step b and Step c for of all the workflows in the folder.
NOTE: It is recommended that you reload the runtime events after activating the workflows.
i Navigate to Administration - Runtime Events > Events screen, select all records and then select
Reload Runtime Events from the drop-down menu.
13 Import the rest of the SIF files from the SIFFiles folder AIA251\ACR474_Workaround into Siebel
Tools using the Import from Archive function.
If you have not locked the required projects, you may receive a warning error message.
Make sure to choose the Merge Option in Siebel Tools Import Wizard.
15 Compile all of the objects listed above using the Compile Selected Object option and save the
SRF file to the <Siebel Server Install folder>\objects\ENU\siebel_sia.srf folder on the installed
Siebel server.
16 Import and activate the workflows listed in the following table from
\AIA251\ACR474_Workaround\WFs into Siebel Tools:
New/
Process Name Modified Project
Pricing Procedure - Calculate Net Price Toolkit Modified Row Set Transformation
SIS OM Edit Service Order Line Item Modified SIS OM Base Architecture
b Right-click on the right side pane ‘Workflow Processes’ and import the .xml file into Siebel Tools
from the WFs folder. Refer to the list of workflows in the preceding table to know which project
these workflows need to be imported into.
c Activate the workflows by clicking on “Deploy+ Activate” button to activate the workflows.
d Repeat Step b and Step c c for of all the workflows in the folder.
17 Import the rest of the SIF files from the SIFFiles folder AIA251\8113_Addendum\ into Siebel
Tools using the Siebel Tools > Import from Archive function.
If you have not locked the required projects, you may receive a warning error message.
■ .\AIA251\8113_Addendum\DMGSchemaChanges\S_PRO_CFG_ITEM.sif
■ .\AIA251\8113_Addendum\Integration Object\SWIOrderIO.sif
18 Compile all of the preceding objects using the Compile Selected Object option and save the SRF
file to the <Siebel Server Install folder>\objects\ENU\siebel_sia.srf folder on the installed Siebel
server.
SWI External Contact Req Integration Process Modified Web Service Integration
SWI External Customer Req Integration Process Modified Web Service Integration
b Right-click on the right-side pane ‘Workflow Processes’ and import the .xml file into Siebel Tools
from the Workflows folder. Refer to the list of workflows in the preceding table to know which
project these workflows need to be imported into.
c Click the “Deploy+ Activate” button to activate the workflows.
d Repeat Step b and Step c for of all the workflows in the folder.
c In the first applet, Action Sets, search for the 'Cache Refresh BC - ISS Promotion Pricing
Components List Applet' Action Set.
d For this Action Set, in the bottom form applet, there is a control with the 'Business Service
Context' label. For this control, the previous value was only "ISS Promotion Pricing Components",
"ISS Promotion Pricing Rules Summary". Another new entry was added to this and now the value
for this control is "ISS Promotion Pricing Components", "ISS Promotion Pricing Rules Summary",
"Promotion Config Item".
b Release a new version of each of the above objects and then bounce the server.
a Navigate to Administration - Server Configuration > Enterprises > Component Groups and query
for each of the following Component Groups and, if Enable State = Disabled, click <Enable>:
❏ SIA
❏ HTIM
❏ EAI
b After enabling the necessary components, navigate to Administration - Server Configuration >
Enterprises > Synchronize. Select all the records and then click Synchronize.
27 Activate workflows.
a Navigate to Site Map > Administration Business Process > Workflow Deployment > Active
Workflow Processes and in the second applet, complete one of the following tasks:
❏ Query for SIS*,Pri*,PSP*,ISS*,Elig*,eSales*.
❏ Query for the following groups: Eligibility & Comp, Asset Based Ordering, Pricer, eSales,
Product Promotions, Configurator, C/OM UI processes, CUT eSales (only for SIA, not for
SEA), and Product Recommendation, and delete the groups manually after deactivating
the processes. To deactivate these groups, select them all and then select Deactivate
Process. You can check the Deployment Status as Inactive.
❏ Query for the following groups: Eligibility & Comp, Asset Based Ordering, Pricer, eSales,
Product Promotions, Configurator, C/OM UI Processes, CUT eSales (only for SIA, not for
SEA), and Product Recommendations, and then activate all the workflows.
❏ CalculateShippingChargeSalesOrderSiebelReqABCSImpl
❏ CheckATPSalesOrderSiebelReqABCSImpl
❏ ConfiguratorUserLangSiebelAdapter
❏ CreditCheckSalesOrderSiebelReqABCSImpl
❏ ESB_AccountBalanceSiebelCommsReqABCS_Service
❏ ESB_ConfiguratorCopyConfigEbizAdapter_Service
❏ ESB_InvoiceSiebelCommsReqABCS_Service
❏ ESB_UnbilledUsageSiebelCommsReqABCS_Service
❏ FetchAccountSiebelReqABCSImpl
❏ FetchContactSiebelReqABCSImpl
❏ MatchAccountSiebelReqABCSImpl
❏ MatchContactSiebelReqABCSImpl
❏ PaymentAuthorizationSalesOrderSiebelReqABCSImpl
❏ PaymentSiebelCommsReqABCS
❏ ProcessSalesOrderSiebelCommsJMSProducer
❏ RequestProductStructureSiebelJMSProducer
❏ SyncCustomerSiebelEventAggregator
❏ SyncInstalledProductListSiebelCommsReqABCSImpl
❏ UpdateCreditAlertSiebelCommsReqABCSImpl
d Change the Address field for each outbound Web service to point to http://
ap6039fems.us.oracle.com:7797.
e For Inbound Web Services, navigate to Administration - Web Services > Inbound Web Services,
and make sure that the corresponding Web Services are active. If they are not, change the status
from "Inactive" to "Active" and click the Clear Cache button.
NOTE: Query for these inbound web services --- * ISS *; * Update Order *; * SWI Update *,
SWI*.
NOTE: Enabling the EAI and Workflow Component Groups in the Siebel Server will start all the
required components stated above for transaction logging.
2 Create a Job for Component Generate Triggers by clicking New and typing Generate Triggers
under Component/Job.
■ EXEC = TRUE
■ Remove = TRUE
NOTE: If the job parameters do not appear when you query for them, then search for them in the
Advanced or Hidden section.
2 Make a copy of the Workflow Monitor Agent in Administration - Server Configuration ->
Component Definition and change the name to "Workflow Monitor Agent SWI".
4 Change the Group Name to "SWI Customer Update Policy Grp" in the component Parameter
applet (down). (Under Component Parameters query for "Group Name" and type the SWI
Customer Update Policy Grp under Value).
Workflow Monitor Agent has a parameter called 'Default Tasks' which has been hidden and should
only be displayed or available to advanced users. In order to reveal this hidden parameter, complete
the following steps.
NOTE: You must log out from your current user session and log back into the application in order
for the parameter to take effect.
3 Start srvrmgr.
2 Rename the existing diccache.dat file in the path <Installed Directory> \ses\siebsrvr\bin.
2 Create a job for the "Generate Triggers" component by clicking New and typing "Generate
Triggers" under Component/Job.
■ EXEC = TRUE
NOTE: If the job parameters information does not appear when you query for it, then search for
it in Advanced or Hidden section.
5 After about five minutes, check for log details for the task for the new workflow monitor
component "Workflow Monitor Agent SWI" by navigating to Administration > Server Management
> Tasks.
6 If errors occur, check whether all configurations have been done properly and then repeat “To
restart the server” on page 197 and “To generate the trigger” on page 197.
CAUTION: Set the system preference to TRUE only for the required PIPs. The AIA Comms PIP
and the AIA OrderToCash PIP cannot coexist.
2 Query for 'Validate Due Date' in the 'System Preference Name' field and set the 'System
Preference Value' to 2. If querying for this preference does not yield any results, create this
value.
3 Query for 'Cancel Error Mode' in the 'System Preference Name' field and set the 'System
Preference Value' to 3 (the default value).
4 Update the AIA Version system preference according to the AIA version that you are using. The
following versions are available:
■ 2.0.1
■ 2.4
■ 2.5
■ 2.5.1
NOTE: If you select any values other than the ones listed above, the application may not function
as expected.
The following procedures describe the process of setting up the integration user:
Login as SADMIN
Navigate to Administration-User ' Employee view The list applet should contain the
integration user flag
3 Change the values in the Language-Independent Code column to define the new mapping as per
following table:
Low 6
Medium 4
High 2
Urgent 0
2 Copy Siebel.jar and SiebelJI_enu to D:\JMS folder, these jar files can be found in <Siebel Server
installation directory>\classes folder
5 Create a file with name ‘jndi.properties’ with following details in the path D:\JMS:
java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory
java.naming.security.principal=anonymous
For example:
java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory
java.naming.provider.url=opmn:ormi:// 152.68.240.154:6009:oc4j_soa
java.naming.security.principal=anonymous
Make sure that there are no extra spaces in the jndi.properties file.
6 Create a Named Subsystem in the Siebel application through the server management.
a Connect to the server manager from the command prompt from the bin directory of the Siebel
installed folder with the following command.
b Run the following command to create the named subsystem and add the jar file into the class
path.
For Unix Environment the CLASSPATH should be separated by : (colon) while for windows it
should be ; (semicolon). So, the above command for Unix environment has to be the
following:
Make sure that the path is correct for all the files and that the CLASSPATH ends with a . (dot).
Here qa2 should be replaced with the appropriate folder name.
7 Log into the Siebel application and navigate to Site Map > Administration Server Configuration
> Profile Configuration.
a Query for the Profile with Alias Name ‘JAVA’ in the profile list and make sure the parameters are
correct.
b For the Windows environment, edit the value of VMOPTIONS to -Djms.log=D:\JMS\log\jms.log.
c For the Solaris environment, edit the value of VMOPTIONS to -Xusealtsigs -Xrs -Djms.log=/
export/home/qa2/JMS/log/jms.log.
Make sure that the JMS/log folder exists and has the write permission.
NOTE: For more information, see the Siebel Enterprise Application Integration (EAI)
documentation on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/
siebel.html.
Use the following procedure to configure corresponding Web services for AQ.
Queues must have been created as part of AIA installation. Please refer the same queue name
here.
3 To locate the Connection Factory Name, log into Application Server control, and navigate to
oc4j_soa ' Administration > Database Persistence.
Example: jms://java:comp/resource/AIA_JMS_RP/Queues/
AIA_SALESORDERJMSQUEUE@java:comp/resource/AIA_JMS_RP/QueueConnectionFactories/
QCF
2 Query for the corresponding object manager for the application (such as htimObjMgr_enu for
application HTIM).
3 Query for the ‘Order Management - Enable Asset Based Ordering’ parameter in the parameter
list for the component, and set the value to False.
1 Organization Manual
4 Products EIM
5 Pricelist EIM
6 Customers EIM
7 Assets EIM
■ Make sure that the Siebel EIM component is online and is running properly. (To check this,
navigate to the Administration - Server Configuration or Administration - Server Management
screens.)
■ To avoid data loss, do not restart the Siebel Server while the EIM job is running.
■ After you have completed the data load for one country, make backup copies of the EIM logs, for
status verification. These logs are located in the siebsrvr/logs directory.
2 Make sure that the Enterprise Integration Manager component within the Workflow Management
component group is also active and online.
3 Navigate to the Administration - Server Configuration screen, then Enterprise, then Component
Groups, and then the Components Group Assignments view.
4 Make sure that the Enterprise Application Integration Component Group is enabled.
To set up organizations
1 Navigate to the Administration - Group screen, and then the Organizations view.
NOTE: Enter information into the Organization Name field but leave the Site field blank.
NOTE: Make sure that the inventory location is associated with the correct location.
Product Product.ifb
Pricelist Pricelist.ifb
Customer Customer.ifb
Asset Asset.ifb
2 Make sure that the SESSION SQL statement of the [UPDATE ACCOUNT NUMBER] section of the
Customer Ifb file is modified in order to reflect the working instance:
Also, the same should be considered for the [UPDATE INTEGRATION ID] section of the Pricelist.ifb
file:
For Pricelist.ifb, comment the second process using a terminate symbol (so that it becomes
inactive and only the first process is executed), like this:
TYPE = SHELL
Once EIM imports all of the pricelist data and the Integration Id is populated, the administrator
needs to run another ODI API to populate the cross-reference database. Then, the administrator
needs to run EIM again to nullify integ_id. The format of the IFB file for the second run will look
like:
TYPE = SHELL
All the job parameters should remain the same for both of the runs.
3 Log into the application with administrator credentials in order to be able to access the Server
Management screen.
4 Navigate to the Administration - Server Management screen, and then the Jobs view.
5 Click New and select "Enterprise Integration Mgr" in the Component/Job tab.
■ Error Flags = 1
■ Trace Flags = 1
7 After passing parameters, click Submit Job.
8 In the Jobs view, for each job that you have executed, make sure that the Status column displays
“Success” for the jobs that you have executed.
9 Check the status in the EIM table by executing the SQL statements in the following section. In
each case, make sure that the status is IMPORTED.
Products
Product Header:
GROUP BY IF_ROW_STAT
Product Details:
GROUP BY IF_ROW_STAT
Product-Inventory Locations:
GROUP BY IF_ROW_STAT
Pricelists
In this case since the same set of records are processed twice by the two separate sections of the
IFB file: one meant for importing the Pricelist Records and other meant for updating the Integration
Id to NULL, you will get the DUP_REC_EXISTS status in the EIM tables.
GROUP BY IF_ROW_STAT
Customers
Address:
GROUP BY IF_ROW_STAT
Account:
GROUP BY IF_ROW_STAT
Account Details:
GROUP BY IF_ROW_STAT
Customer:
GROUP BY IF_ROW_STAT
Assets
There are two sections in the IFB file: For Importing Assets and For Updating the Parent Assets.
GROUP BY IF_ROW_STAT,IF_ROW_BATCH_NUM
Postinstallation Tasks
You must perform the tasks listed in this section.
NOTE: These postinstallation tasks only apply to the Order to Cash PIP.
2 In the top applet, create a new record with the following values:
3 In the bottom applet, create the Input Argument by creating pop up icons on the Property Name
Field, using the following values:
Value: FALSE
Value: ISS_JWS
NOTE: The RootObjectName should be any meaningful name for the Joint Workspace Project.
This will be created automatically after the Business Service is executed from the simulator.
4 Click the Run button in the top applet and wait until the job ends.
2 Query for the value provided for the RootObjectName input parameter given while running the
ISS Authoring Import Export Service (as in Step 4 of “To release the products” on page 207).
3 Go to the Menu option and click the About Record method or use the keyboard shortcut (CTRL +
ALT + K) while on the active record.
4 Make a note of the Row # value displayed in the pop-up applet, as you will need this value to
provide the input argument to the workflow process.
2 In the "Active Workflow Processes" view, search for the "SWI Initial Load Non CP Order Release"
workflow to make sure that the active version of the workflow is present in the repository.
3 If this record is not present, query for the “SWI Initial Load Non CP Order Release” workflow in
the “Repository Workflow Processes" applet, and click Activate after you locate the record.
4 If the workflow is not present in either of the previous applets, within the Active Workflow
Processes applet, select Menu, select the Import Processes functionality, and choose the SWI
Initial Load Non CP Order Release -WF.xml file from the Browse window.
5 Navigate to the Administration - Server Management screen, and then the Jobs view.
6 Click the New button on the top applet to create a new job, and enter "Workflow Process Batch
Manager" as the value for “Component/Job”.
7 Navigate to the "Job Parameters" applet and create the following two new values:
■ Value = [Par JWS Id] = '6SIA-4HVMH' AND [Orderable Flag] = 'Y' AND [Product Def Type
Code] <> LookupValue ("PROD_TYPE_CD", "Customizable")
NOTE: The Parent Joint Workspace Id value is the same as the one in Step 5 of “To get the joint
workspace Row ID” on page 208.
8 Click the "Submit" button and wait until the job ends successfully.
2 Navigate to Site Map > Administation Business process > Repository workflow process.
a In the top applet Query for the workflows imported above and activate them.
b Make sure they are in active state by querying in the bottom applet.
g Replace the Siebel Verification with Oracle Batch Validate'. Change all four records with sequence
#2.
❏ Mode = Quote, Instance Type = Line Item - Change Service Name column to "Oracle
Verify Item (Quote)"
❏ Mode = Order, Instance Type = Line Item - Change Service Name column to "Oracle
Verify Item (Order)"
❏ Mode = Quote, Instance Type = Header - Change Service Name column to "Oracle Verify
Header (Quote)"
❏ Mode = Order, Instance Type = Header - Change Service Name column to "Oracle Verify
Header (Quote)"
4 Navigate to Administration Runtime Events > Events and click Menu > Reload Runtime Events.
❏ CZRuntimeInstanceView (JS)
b For each view assign the appropriate responsibility so that user with that responsibility can
navigate to this view.
This is part of seed data. It should be done when exporting the seed data.
a From the top applet use the drop-down menu (bold highlighted menu) and select Host
Administration.
b Add a new host entry:
c Select "Symbolic URL Administration" and add new record in the top applet.
❏ Name: OracleCfgURL (Note: This symbolic name is very important because server side
business component code relies on this name)
❏ URL: http://OracleConfigurator/OA_HTML/CfgSebl.jsp
❏ Name: InitMessage
❏ Name: PostRequest
Complete the following two steps to set up the "SSO" login into Oracle Apps. The "SSO" login
is the preferred style to access Oracle. If "SSO" login is not set up, then the Siebel end user
will have to know and enter Oracle login credentials at the login page.
e For the next two arguments enter the values for Argument Value as specified. UserLoginId and
UserLoginPassword are function names used by Siebel SSO. These functions look up the Oracle
login credentials for the current Siebel User. Putting anything else in will require that you log into
an Oracle Applications for Configurator session.
f Continue to add arguments to the same URL.
❏ Name: username
❏ Name: password
h Select "SSO Systems Admin List" and add a record in the top applet.
❏ System Name: OracleConfigSSO
i In the bottom applet "SSO System Users" add records for the Siebel users that will be invoking
Oracle configurator. The Siebel usernames will be paired with Oracle login credentials. For
example:
❏ Siebel Login Name: sadmin
❏ Password: welcome
"HTIM Object Manager (ENU)" Component and select "Order Management - Enable Asset Based
Ordering" Parameter and set this value to False to call Oracle configurator instead of calling
Siebel Configurator.
The following workflows would need to be activated for Configurator to work. Note that these are
not workflows that were introduced as part of Oracle Configurator integration, but are existing
ones.
■ Goto*
■ PSP*
■ Product Compatibility*
■ Product Eligibility*
■ Product Reco*
■ *Pric*
■ Config*
■ Check*
3 The form page for Applications > Register should be displayed. If not, navigate to the form.
■ Siebel Quote Integration |SEBLQ | DUMMY_TOP |Provides integration between Siebel Quote
and Oracle Configurator
■ Siebel Order Entry Integration | SEBLO | DUMMY_TOP | Provides integration between Siebel
Order Entry and Oracle Configurator
The new applications now must be added to Oracle Configurator Publication Applicability list.
This step runs a concurrent program. Once the program runs these new applications will be
available during model publication.
Refer to Oracle documentation for Configurator for the entire process of developing models for calling
applications.
NOTE: Step 1 through 4 is part of seed data. It should be done when exporting the seed data.
5 After importing, change the IP Address on the Service Ports (middle applet) for each of the above
Web Services.
2 For the following Data Maps, add three columns: 'External Configurator Reference 1','External
Configurator Reference 2', 'External Configurator Reference 3' to both the Source and the
Destination Column in 'Data Map Field' section for the 'Data Map Component' specified in the
paranthesis below.
NOTE: The folder D:\19924 has been suggested here, but if you have installed the application
someplace else, please make sure that you refer to the eapps.cfg file in your installation.
CAUTION: Do not use Wordpad, as this will cause incorrect characters to be added to the file.
2 Change the following Signal sequences if required. By locking the signal and click the Workspace,
do the following Sequence changes and release the signal by clicking the Release button.
Service
Service Name Type Sequence Condition Active Mode
Service
Service Name Type Sequence Condition Active Mode
Service
Service Name Type Sequence Condition Active Mode
Service
Service Name Type Sequence Condition Active Mode
1 Navigate to Administration - Application > State Model and search for "TNT SHM Quote Status".
2 Extend its activation date until 2020 (leave day and month as sysdate).
a Navigate to Administration - Application > Data Map Administration and query for Data Map
Object 'ReviseOrder' and Data Map Component 'Header' and Data Map Field 'Back Office Process
Status'.
b Inactive this field map by selecting the Inactive Check box.
2 Change/Activate data validation rules.
a Navigate to Administrator > Data Validation > Rule Sets and query for the following rule sets:
3 Activate these five rule sets by clicking the Activate button on the top applet.
Rule Business
Name Expression Sequence Component Apply To Return Code
Business Return
Rule Name Expression Sequence Component Apply To Code
Business Return
Rule Name Expression Sequence Component Apply To Code
Business Return
Rule Name Expression Sequence Component Apply To Code
Business Return
Rule Name Expression Sequence Component Apply To Code
Business
Rule Name Expression Sequence Component Apply To Return Code
4 Navigate to Administration - Runtime Events > Events screen, and select Reload Runtime Events
from the drop-down list.
NOTE: If two active versions are displayed for “SWI Order Validation Rule Set”, use the procedure
detailed above.
■ Make sure that the Siebel EIM component is online and running properly. To check this, navigate
to the Administration - Server Configuration and Administration - Server Management screens.
■ To avoid data loss, do not restart the Siebel server while the EIM job is running.
■ After you have completed loading data for one country, make a backup copy of the EIM logs for
status verification. (These logs are located under siebsrvr/logs.)
Use the following procedure to execute the EIM job to create and update credit alerts.
NOTE: If the Order to Cash PIP is enabled, the Asset-Based Ordering parameter for the
corresponding object manager for the application has to be set to False.
This section describes the integration user setup process. We have introduced a new flag to identify
an integration user (needed while integration testing). This user credential needs to be configured
(at AIA side) for the Siebel Inbound Web services call from AIA side to avoid the boomerang effect.
Dynamic Pricing
■ This provides the complete pricing capabilities such as attribute pricing, promotions, aggregate
discounts, and so on.
■ It leverages the variable maps that contain the XA child variable maps.
■ It is available only to those customers that have the 'Dynamic Pricer' license.
■ Dynamic Pricing can also be enabled by selecting "Enable Dynamic Pricing" from Admin - Pricing
> Price List > In Applet Level Menu dropdown select "Enable Dynamic Pricing".
■ This is a new implementation in 8.1.1. On selecting "Enable Dynamic Pricing", all the necessary
changes will be done.
Configuring the Email Notification for the Product Class and Attribute
Query Feature
Users to whom emails need to be sent need to be added to the user list.
3 Add the email address in the contact information of the child applet.
5 Query for the "SCE Users" user list. If it does not appear, create it.
The user list created above is passed in the run time events. Use the following procedure to add the
changed user list.
"Parent BC Record Name";"Field Name in Child BC ";"BO Name ";"Parent BC";"Child BC"
For instance-
or
The following three run-time events use the action set described above.
Four communications templates are used to send email messages. The Attribute Defn and Product
Class templates are already configured. Use the following procedure to configure/edit other
templates.
❏ Type: [Type]
2 Create a notepad file called "Class_Template.txt" and add the following values:
❏ Description: [Description]
❏ Type: [Type]
4 Query for "Workspace Attribute Defn Template" and click on Template Items View.
7 Query for "Workspace Product Class Defn Template" and click on Template Items View.
9 Make sure that "ISS Joint Workspace VOD Pick BucComp" is selected in the iteration child
business component for above two template items.
The communication template names are added in the user properties of the BCs listed in the
following table.
The SMTP Server name, From Email Address, and POP server details are added in the a
Communication profile. Use the following procedure to add the SMTP server name, From Email
Address, and POP server details.
To change the SMTP Server name, From Email Address, and POP server details
1 Navigate to Administration - Communications > Communications Drivers and Profiles.
2 Query for the "Internet SMTP/POP3 Server" communication driver, and if it does not exist, then
create it, using the following values:
■ Outbound: Yes
3 Query for "Default SMTP" in child applet. If it does not exist, then create it.
4 Change the SMTP and POP Server details in the grandchild applet, using the following values:
The communication profile is added the in the user properties of the BCs listed in the following table:
NOTE: The Class attributes names and the attribute definition names must be identical.
c For the TBO Discount products synced from BRM. Change the Structure type to ‘Customizable’
and Product Type should be “Time Based Offer” and associate the above TBO class to this
product.
2 Create Job to Inactive Assets.
a Navigate to Server Management, and then Jobs, and create a new Job.
d In Data Map Field, add the fields that needs to be copied during revision (such as Service End /
Service Start Date/Due Date).
The business service name must be specified as the value for the “Business Service Query Access
List” server component parameter.
For example, if the server component is “eCommunications Object Manager (ENU)”, then go to
its parameters and query for Name = “Business Service Query Access List” and add Value = “CMU
External Integration Service”. Then, the server component should be restarted to take effect
after the change in the component parameter value.
a Navigate to Site Map > Administration- Order Management > Variable Maps.
2 Query for the following workflow policies and remove the "Expiration" date:
By default, the Workspace Release Flag user preference is set to N. If you want to release products
into the Siebel application automatically, you must change this preference.
2 Query for 'Workspace Release Flag', set the value to N, and restart the server.
■ Oracle 10g/11g
NOTE: Both Oracle and IIR servers are on the same operating system and both the Oracle database
and the IIR database are on the same database.
NOTE: Hyperion Data Relationship Management is only supported on the Windows platform.
When users query for a newly-created prospect, they receive an error message.
■ Within Siebel Tools, navigate to the List Mgmt Prospective Contact business component, add
a new field called RowId, and map it to Id.
The installer does not automatically overwrite the customer version of the CCHtmlType.swf file. The
UI-related fixes will not take effect unless the configuration files are delivered by the installer. To
receive the updated configuration files, users must set the Overwrite flag to “Y” in the Siebel.ini file.
❏ Siebel_Enterprise_Server/enu/siebel.ini
❏ Siebel_Enterprise_Server/siebel.ini
❏ Siebel_Web_Server_Extension/enu/siebel.ini
❏ Siebel_Web_Server_Extension/siebel.ini
The Back button navigates incorrectly when tabs are present in the DGM screen.
Workaround: None
The Initial Load process does not support cross-database (platform) data pull.
Workaround: Have the same database type for Siebel and IIR.
1 Install the Siebel Tools build and connect to the server database.
2 Navigate to the Siebel Tools installation directory <Tools Install Director>\REPPATCH folder.
3 Unzip the ACR437_UCM.zip file from <Tools Install Directory>\REPPATCH and configure ACR 437
using the instructions provided in the Siebel Maintenance Release Guide, Version 8.1.1.x. To
access this guide, from within My Oracle Support, navigate to the Knowledge tab and search for
Doc ID 880452.1.
4 Unzip the ACR475A_UCM.zip file from <Tools Install Directory>\REPPATCH and import the seed
data for ACR 475A. For instructions, see “Configuration Instructions for ACR 475A” on page 233.
5 Complete the ACR 437 and ACR 475A setup, including applying the Base Tables and EIM Table
schemas.
CAUTION: It is important that you complete the entire setup for ACR 437 and ACR 475A before
you make the repository changes for ACR 475B.
7 Unzip the ACR475B_UCM_2.zip file from <Tools Install Directory>\REPPATCH and perform the
required configuration changes.
8 Unzip the ACR475B_UCM_3.zip file from <Tools Install Directory>\REPPATCH and perform the
required configuration changes.
CAUTION: If you want to use DRM, do not unzip the UCM_3.zip file.
9 Unzip the ACR475B_UCM_4.zip file from <Tools Install Directory>\REPPATCH and perform the
required configuration changes.
CAUTION: In order to implement ACR 475B, you must already have installed ACR 437 and ACR
475A. ACR 437 was included in the Siebel 8.1.1.1 Fix Pack. For information about how to install and
configure ACR 437, see the Siebel 8.1.1.x Maintenance Release Guide on My Oracle Support. To
access this guide, navigate to the Knowledge tab, and search for Doc ID 880452.1. For information
about how to install ACR 475A, see “Configuration Instructions for ACR 475A” on page 233.
NOTE: For more information about what functionality ACR 475A provides, see Oracle Universal
Customer Master for Higher Education Constituent Hub Administration Guide on Oracle MetaLink 3.
To access the guide, navigate to the Knowledge tab and search for Doc ID 863982.1.
This section includes information on how to set up and configure Oracle Higher Education Constituent
Hub Web services. The following topic is included:
“Process for Configuring Oracle Higher Education Constituent Hub Web Services” on page 233
Both the Match and Fetch Web service are set up with the following tasks. If you need to manually
configure the Web services, see Doc ID 763962.1 on Oracle MetaLink 3.
Process for Configuring Oracle Higher Education Constituent Hub Web Services
You must set up and configure the Web Services.
To set up Oracle Higher Education Constituent Hub Web services for ACR 475A, perform the following
tasks:
■ “Compiling the SRF and Restarting the Siebel Server” on page 236
SIF files contain Siebel object definitions that can be imported into Siebel Tools to replace existing
definitions. Following successful application of ACR 475A, you will then locate and import the SIF files
that came with the Quick Fix into Siebel Tools. This SIF file contains object definitions that are
different from those contained in your present repository.
3 Open the Sifs folder, and verify that the following .sif files are present:
■ Tables.sif
■ Applets.sif
■ BusinessComponents.sif
■ BusinessObjects.sif
■ BusinessService.sif
■ EIMTables.sif
■ IntegrationObjects.sif
■ Links.sif
■ PickList.sif
■ Screen.sif
NOTE: Before importing the SymbolicStrings.sif file, make sure the following parameter value is
set in tools.cfg file: SymStrPrefix = SBL_.
■ SymbolicStrings.sif
■ Views.sif
4 After verifying that the .sif files are all present, log on to Siebel Tools.
■ Contact
■ Symbolic Strings
■ Table CIF
■ Table Person
■ UCM SDH
■ EIM CIF
■ EIM Person
■ LOY Profiles
TIP: Use the following query to get the list of projects to lock or unlock: {Contact or Symbolic
Strings OR Table CIF OR Table Person OR UCM CDM Child OR UCM Data Management OR UCM
Higher Education OR UCM SDH OR VEAI UCM CIF OR VEAI UCM CIF UI OR Web Service
Integration OR EIM CIF OR EIM Person OR LOY Profiles}.
9 In the Object Explorer, query for tables that have been modified, by using the Changed flag.
■ S_CONTACT_NAME
■ S_CONTACT_UCMX
■ S_CON_IDNTY_DOC
■ S_UCM_ADDR_PER
■ S_UCM_CONTACT
■ S_UCM_CON_CHILD
■ S_UCM_ORG_EXT
■ EIM_UCM_ADRPER
■ EIM_UCM_CON
■ EIM_UCM_CONCHLD
■ EIM_UCM_ORG
■ EIM_CONTACT3
13 Enter the required information for your database, including the exact ODBC name for your
database.
14 Click Apply.
The modification process may take a moment.
15 Once the process is finished, click OK to finish the table schema changes.
16 Repeat Step 11 through Step 15 until all required tables have been modified.
TIP: You can apply the schema changes to all the tables in one pass by selecting the Current
Query in the Tables drop-down in the Apply Schema window. To perform this you have to have
executed a query with changed flag set.
■ Contact
■ Symbolic Strings
■ Table CIF
■ Table Person
■ EIM CIF
■ EIM Person
■ LOY Profiles
4 Query for the Integration Objects that were imported from the .sif files.
❏ SwiPersonIO
❏ SwiPersonPublishIO
❏ CIFContact
❏ CIFContactInsert
❏ CIFContactInsertRs
❏ CIFContactUpdate
❏ CIFContactUpdateRs
❏ CIFContactUpsert
❏ CIFContactUpsertRs
❏ UCMContactSourceDataAndHistory
5 For each of the Integration Objects that were imported, choose Undeploy from the right-click
menu, then step off the record to retain changes.
4 Enter a data source name, and the name of the server you will be connecting to.
TIP: For an Oracle Database, enter the TNS service name that you created to connect your tools
to the Oracle Database.
6 Before executing the next step make sure dataimp.exe exists in the <Tools Install
directory>\bin directory.
NOTE: The /e n switch enforces the dataimp process to only look at tables in the imp file. To
track unique constraint violations, see the /h log file.
■ Replace Tools Install Directory with your Siebel Tools installation directory.
■ Replace ODBC Source Name with the ODBC you created in Step 3 of the “To import seed data”
procedure.
■ Replace Database Platform with your database platform, (for example: Oracle, MSSQL, and
so on).
■ Replace Tools Install Directory with your Siebel Tools installation directory.
■ Replace ODBC Source Name with the ODBC you created in Step 3 of the “To import seed data”
procedure.
■ Replace Database Platform with your database platform, (for example: Oracle, MSSQL, and
so on).
3 Review the Siebel Tools Install Directory>\temp\dataimp_seed.log file to make sure that
the import was completed successfully.
NOTE: The /e n file enforces the dataimp process to only look at tables in the imp file. To track
unique constraint violations, see the /h log file.
■ Replace Tools Install Directory with your Siebel Tools installation directory.
■ Replace ODBC Source Name with the ODBC you created in Step 3 of the “To import seed data”
procedure.
■ Replace Database Platform with your database platform, (for example: Oracle, MSSQL, and
so on).
■ Replace Tools Install Directory with your Siebel Tools installation directory.
■ Replace ODBC Source Name with the ODBC you created in Step 3 of the “To import seed data”
procedure.
■ Replace Database Platform with your database platform, (for example: Oracle, MSSQL, and
so on).
❏ Applets.sif
❏ Applications.sif
❏ BusinessComponents.sif
❏ BusinessObjects.sif
❏ BusinessServices.sif
❏ Classes.sif
❏ Command.sif
❏ Dlls.sif
❏ EBCTable.sif
❏ EIMTables.sif
❏ IntegrationObjects.sif
❏ Links.sif
❏ Menu.sif
❏ PickList.sif
❏ Screens.sif
❏ SymbolicStrings.sif
❏ Tasks.sif
❏ Tables.sif
❏ Views
❏ WebTemplates.sif
❏ Workflows.sif
NOTE: The Tables.sif file should be imported before you apply the EIM changes. Apply this table
in merge mode.
2 Verify that the SIFs folder within the ACR475B_UCM_1.zip file contains the following .sif files:
❏ BS_UCM_DataQualityManager.sif
❏ WF_UCMBatchProcess.sif
❏ Account
❏ Account (SSE)
❏ Account Hierarchy
❏ Comm Manager
❏ Common Components
❏ Contact
❏ DNB Data
❏ DQ ISS Integration
❏ DeDuplication
❏ Household
❏ LOY Profiles
❏ Menu
❏ Symbolic Strings
❏ Table CIF
❏ Table Organization
❏ Table Party
❏ Table Person
❏ UCM Merge
❏ UCM SDH
❏ UCM Survivorship
❏ UCM Task UI
❏ UCM Unmerge
i."Table Organization" OR "Table Party" OR "Table Person" OR "UCM CDM Child" OR "UCM Data
Management" OR "UCM Hierarchy Management" OR "UCM Higher Education"OR "UCM Merge" OR
"UCM Privacy Management" OR "UCM SDH" OR "UCM Survivorship" OR "UCM Task UI" OR "UCM
Unmerge" OR "VEAI UCM Account ASI" OR "VEAI UCM CIF" OR "VEAI UCM CIF UI" OR "VERT CUT
Address" OR "Web Service Integration"
4 Before importing the SymbolicStrings.sif file, make sure that the SymStrPrefix=SBL parameter
exists in the tools.cfg file.
5 Import all of the .sifs except EIMTables.sif to the server database using the merge mode. Import
the .sifs from ACR475B_UCM.zip before you import the .sifs from ACR475B_UCM_1.zip.
6 Within Object Explorer, navigate to Tables, and query for tables that have changed by selecting
the query with the Changed flag set.
❏ S_ADDR_PER
❏ S_CONTACT
❏ S_CONTACT_NAME
❏ S_CONTACT_UCMX
❏ S_CON_ADDR
❏ S_CON_IDNTY_DOC
❏ S_DYN_HRCHY
❏ S_DYN_HRCHY_REL
❏ S_PARTY_REL
❏ S_PARTY_UCMX
❏ S_UCMIMPORT_TSK
❏ S_UCMIMPTSK_ARG
❏ S_UCMIMPTSK_LOG
❏ S_UCMSRVTSK_MSG
❏ S_UCM_ADDR_PER
❏ S_UCM_ATGP_RULE
❏ S_UCM_CONTACT
❏ S_UCM_CON_CHILD
❏ S_UCM_CON_DECAY
❏ S_UCM_HRCHY
❏ S_UCM_HRCHY_REL
❏ S_UCM_IMPMP_ITM
❏ S_UCM_IMPRT_MAP
❏ S_UCM_MERGE_REQ
❏ S_UCM_MRG_ASSOC
❏ S_UCM_OGP_CHILD
❏ S_UCM_ORGRP_MRG
❏ S_UCM_ORG_CHILD
❏ S_UCM_ORG_DECAY
❏ S_UCM_ORG_EXT
❏ S_UCM_RULE_SET
❏ S_UCM_SRVR_TSK
7 With the query result, perform the following steps to extend the schema:
c In the window for login credentials and database information, enter the database administrator
password.
d From the Tables drop-down list, select Current Query.
e For ODBC data source, enter the exact ODBC name of the database, and click Apply.
f Wait until the process is finished and the tables are modified, and then click OK to finish the
schema changes for the tables.
9 On the right pane, query for the Integration Objects that changed during the sif file import.
10 Select all changed Integration Objects, right-click and select Undeploy, and then refresh.
11 Right-click and selct Deploy to deploy the changes to the runtime database.
The server repository- siebel_sia.srf located in
<ServerInstallLocation>\ses\siebsrvr\objects\enu\siebel_sia.srf should be compiled for the changes
in the above .sif files to take effect.
❏ DqSync
Use the following procedure to activate the workflows for ACR 475B.
2 In the Workflow Deployment screen, click the Active Workflow Process tab.
3 In the top Repository Workflow Processes applet, query for the workflows, select them, and click
the Activate button.
4 In the bottom Active Workflow Processes applet, query for the workflows that you just activated
and verify that the Activation Date/Time and Expiry Date/Time are valid.
NOTE: You can use the following query for query for all of the workflows: UCM*Batch Data
Management Workflow OR UCM*Data Decay Process OR UCM Batch Process* OR UCM*SOAP
Process OR UCM Import File Processing OR UCM Master List Import Process OR UCM Process
Merge Request OR UCM SOAP Customer Profile Integration Process. The ISS workflows: ISS
Delete Record Sync OR ISS Launch Pre*Sync OR ISS Launch Write Record Sync OR ISS Write
Record Sync OR ISSGetOldCountry should only be activated if you want to use the xml sync
server to sync records with the IIR Server.
1 Verify that the ACR475B_UCM_2.zip file contains the following SIF files:
■ Applets.sif
■ BusinessComponents.sif
■ Account
■ Contact
■ BusinessObjects.sif
■ Merged Account
■ Merged Contact
■ BusinessServices.sif
■ DQ Sync Services
■ IntegrationObjects.sif
■ CIFContact
■ SwiOrganizationMatchInputIO
■ SwiOrganizationMatchOutputIO
■ SwiPersonMatchInputIO
■ SwiPersonMatchOutputIO
■ SyncAccount
■ SyncContact
■ SyncProspect
■ UCMAccountSourceDataAndHistory
■ UCMAccountTaskUIMerge
■ UCMContactSourceDataAndHistory
■ UCMContactTaskUIMerge
■ Tables.sif
■ EIM_UCM_ADRPER
■ EIM_UCM_ASSET
■ EIM_UCM_CON
■ EIM_UCM_HRCHY
■ EIM_UCM_ORG
■ EIM_UCM_ORGGRP
■ S_UCM_ADDR_PER
■ S_UCM_ASSET
■ S_UCM_CONTACT
■ S_UCM_ORGGRP
■ S_UCM_HRCHY
■ S_UCM_HRCHY_REL
■ S_UCM_ORG_EXT
■ Views.sif
■ Workflows.sif
■ Account
■ Contact
■ DQ ISS Integration
■ EIM CIF
■ Employee
■ Table CIF
■ UCM SDH
■ UCM Unmerge
■ UCM SDH
■ UCM Merge
3 Import the SIF files to the server database using the Merge mode.
4 In the Object Explorer, navigate to Integration Objects, and in the right pane, query for the
Integration Objects that changed during the sif file import.
5 For each of the changed Integration Objects, right-click, select Undeploy, refresh, right-click
again, and select Deploy to Runtime Database.
■ Applets.sif
■ Screens.sif
■ Views.sif
CAUTION: The ACR475B_UCM_3.zip file inactivates DRM. If you want to use DRM functionality, do
not import the ACR475B_UCM_3 file.
❏ Account Hierarchy
2 Import all of the SIFs to the server database using the Merge option.
❏ Account Hierarchy
If you have imported the SIF files from UCM_3.zip, and you want to use DRM, use the following
procedure to revert the changes and to manually enable DRM.
2 In the Properties window, change the Inactive value for each view from TRUE to FALSE.
3 In the Object Explorer, click Applet, then query for Dynamic Hierarchy Admin List Applet, and
then change the following properties:
a In the Object Explorer click Control, query for Advanced Hierarchy, and then in the Properties
window, change the Inactive value from TRUE to FALSE.
b In the Object Explorer, click Applet Web Template, click Applet Web Template Item, and query
for Advanced Hierarchy.
c In the Properties window, change the Inactive value from TRUE to FALSE for both the Base and
Edit List Applet Web Templates.
4 In the Object Explorer, click Screen, and then query for CIF Administration Screen.
5 In the Object Explorer, click Screen View, query for UCM Hierarchy History Flat List View, and in
the Properties window, change the Inactive value from TRUE to FALSE.
6 Compile the objects into the SRF, and restart the Siebel Server.
Applets.sif
BusinessComponents.sif
■ Contact
BusinessServices.sif
■ DQ Sync Services
IntegrationObjects.sif
■ CIFContact
■ CIFContactInsert
■ CIFContactInsertRs
■ CIFContactUpdate
■ CIFContactUpdateRs
■ CIFContactUpsert
■ CIFContactUpsertRs
■ SwiPersonIO
■ SwiPersonPublishIO
■ UCMContactSourceDataAndHistory
Views.sif
WebTemplates.sif
■ View 50 50 50 Framed
Workflows.sif
❏ Comm Manager
❏ Contact
❏ DQ ISS Integration
❏ LOY Profiles
❏ Siebel Workflows - Seed
❏ UCM SDH
3 Import all the SIFs to the server database using Merge mode.
4 Within Object Explorer, navigate to Integration Objects, and query for the integration objects that
changed during the SIF file import.
5 For each of the changed integration objects, right-click, select Undeploy, select Refresh, right-
click, and select Deploy to Runtime Database.
❏ Comm Manager
❏ Contact
❏ DQ ISS Integration
❏ LOY Profiles
❏ UCM SDH
2 In the Siebel application, navigate to Site Map > Administration - Business Process > Workflow
Deployment, and query for the changed workflows in the Repository Workflow Processes applet.
3 Click the Activate button to activate workflows that have not already been activated.
4 Within the Active Workflow Processes applet, verify that the workflows are active.
2 With the query results, perform the following tasks to extend the schema:
e ODBC data source, enter the ODBC name, and click Apply.
f Wait until the process is finished and the tables are modified.
g When the process has finished, click OK to complete the schema changes for the tables.
NOTE: Import the Tables.sif file before you proceed with the EIM changes.
■ EIM_ADDR_PER
■ EIM_CONTACT1
■ EIM_ACCOUNT2
■ EIM_ACCOUNT3
■ EIM_CONTACT3
■ EIM_UCM_CON
■ EIM_UCM_ORG
■ EIM_UCM_CONCHLD
■ EIM_UCM_ORGCHLD
■ EIM_UCM_OGPCHD
■ EIM_PTYUCM_DTL
■ EIM_UCM_MRGREQ
■ EIM_UCM_ORGDCY
■ EIM_UCM_CONDCY
■ EIM_UCM_IMPTSK
■ EIM_UCM_SRVTSK
■ EIM_UCM_IMPMAP
■ EIM_UCM_HRCHY
Use the following procedure to import the EIMTables.sif file into the repository.
❏ EIM Organization
❏ EIM Person
❏ EIM CIF
2 Within Siebel Tools, use the Import from Archive function to read this file and create the tables
in the repository. The "merge" option should be used while importing this file.
2 Use the "Apply/DDL" button to apply the changes to the physical database.
NOTE: If you have previously installed ACR 475B QFs, note that the ACR475B_UCM file has been
replaced by the ACR475B_UCM_2.zip file.
❏ EIM_Files
❏ Knowledgebases
❏ Schemas
❏ SeedData
❏ Sifs
❏ WebServices_XML
NOTE: This folder exists in both the ACR475B_UCM.zip and ACR475B_UCM_4.zip files. These
folders also include a document with instructions for importing non-ENU symbolic strings.
■ For the "Knowledgebases" and "Sifs" categories and feature-specific setup instructions, use the
instructions in “Importing the SIFs and Workflows in the ACR 475B_UCM.zip File” on page 239 to
bring the categories into the testing target database.
1 Create an ODBC entry for the database where you plan to import the seed data.
a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC),
2 In the command prompt, navigate to the directory where you installed Siebel Tools\BIN.
NOTE: Make a note of the directory where the seed data is extracted to - [REPPATCH\ACR475B\
ACR475B_UCM_2\SeedData ].
3 Before you import ACR475B_Seed.dat, make sure that the dataimp.exe file exists in the <Tools
Install Directory>/bin directory.
<Tools Install Directory> - Replace with the Siebel Tools install directory
<Database Platform> - Replace with the database platform (ORACLE, DB2UDB, or MSSQL)
5 Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the
import completed successfully.
6 Seed data import includes mono-language seed data import and language seed-data import. If
you are an ENU (English Language) customer, do the following:
Directory>\REPPATCH\ACR475B\ACR475B_UCM\SeedData\ACR475B_Seed_Locale_ENU.dat
/l <Tools Install directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table
Owner> /i Owner>/i <Tools Install
Directory>\REPPATCH\ACR475B\ACR475B_UCM\SeedData\ACR475B_SeedInp_Files\<Data
base Platform>\ACR475B_seed_locale_ENU.inp /q -1 /w n /e y /t n /x R /n 100 /h log
<Tools Install Directory> - Replace with the Siebel Tools install directory
b To import seed_locale_XXX.dat for languages other than ENU, run the following command after
importing ACR475B_Seed.dat file for importing the locale specific seed_locale_XXX.dat, where
XXX is the language code.
<Tools Install Directory> - Replace with the Siebel Tools install directory
7 Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the
import completed successfully.
To unzip ISSdlls
1 Select the respective dll for the platform required. The dlls modified are ssadqsea.dll,
ssadqasm.dll and ssasec.dll.
2 Place these in the bin or lib folder under the Siebel Server installation directory, depending upon
the platform chosen. These files contain the session pooling fix to be used in ISS 2.8.7.
NOTE: You can also pick up these DLLs from the IIR Server (located in the bin folder if IIR is
running on the same OS.
Importing Knowledgebases
In the Knowledgebases folder provided in ACR475B_UCM.zip, you must bring the ucmdatadecay.xml
and ucmsurvivorshiprules.xml files into the target database to test Survivorship and Decay rules.
NOTE: The Activate button is no longer active after the import has completed.
■ Account
■ Contact
■ DQ ISS Integration
■ EIM CIF
■ Employee
■ Table CIF
■ UCM SDH
■ UCM Unmerge
■ UCM SDH
■ UCM Merge
NOTE: You must stop and restart both the Siebel Server and the Gateway Server for the changes in
the following procedure to take effect.
Execute the commands in the following procedure for the UCMBatchProcess component to run in
single-threaded mode. Make sure that there are no errors when you execute the following procedure.
2 Within the Siebel application, navigate to Site Map > Administration - Business Process >
Workflow Deployment.
3 In the Repository Workflow Processes applet, query for UCM Batch Process and UCM Process
Merge Request.
4 If the workflows are not already activated, click the Activate button.
5 In the Active Workflow Processes applet, verify that the workflows are active.
NOTE: These action sets are disabled by default, so you must enable them. Do not use quotes when
you query for the action sets.
1 Navigate to Site Map > Administration - Runtime Events > Events, and query for Action Set
Name=*Decay*.
2 For the events with Action Set Name=”UCM Account Decay New Record” OR “UCM Account Decay
Update Record”, change the Conditional Expression value to:
GetProfileAttr(‘UCMDecayFieldUpdated:Account’)=”Y”.
3 For the events with Action Set Name=”UCM Contact Decay Record” OR “UCM Contact Decay
Update Record”, change the Conditional Expression value to:
“GetProfileAttr(‘UCMDecayFieldUpdated:Contact’)=”Y”.
Use the following procedure to configure NetChart Server 4.6 Siebel Edition.
2 Copy over the Siebel.cdx file into the directory created in Step 1.
3 In ucm.cfg used by the Siebel thick client, under the specific datasource that you use to connect
to DB, add the following lines:.
ChartServer = localhost:8001
ChartImageFormat = png
Localhost is the name of the machine that is running chart server and 8001 is the port number
of chart server.
4 Navigate to Administration - Server Configuration > Profile Configuration, query for Alias as
ServerDataSrc, and change the DSChartServer and DSChartImageFormat parameters.
5 Start NetCharts Server 4.6 Siebel Edition from Control Panel > Services.
6 In Windows Explorer, navigate to your installation directory for Siebel Charts (such as
D:\Program Files\Visual Mining\NetCharts Server 4.6 Siebel Edition\Server\root\projects).
8 Within the new Siebel.chart subdirectory, create a new file, using Windows Notepad, and type
the following three characters in uppercase but without a carriage return:
CDL
10 Make sure that the DefaultChartFont parameter in your configuration file and the Application
Default Chart parameter for your Application Object Manager component are set to a font that
is available on your machine.
2 Configure the Comparison Rule to "External", select "Business Rule Service" for "Business
Service Name", "RunRules" for "Business Service Method", and then select the individual "Rule
Module Name" for each testing purpose.
3 Activate all four of the UCM Merge Tasks returned: UCM Merge Account Task; UCM Merge Contact
Task; UCM Merge Account Request Task; UCM Merge Contact Request Task.
1 Within Siebel Tools, navigate to Workflow Process, and query for the UCM Organization Customer
Profile Integration SOAP Process.
2 Select the workflow and then select Revise from the Workflow/Task Editor toolbar.
4 Navigate to the Workflow list view and select Publish/Activate from the Workflow/Task Editor
toolbar.
5 Repeat Step 1 through Step 4 for the UCM Person Customer Profile Integration SOAP Process.
2 Apply the hot fixes on top of the base installer. After the patch installation, check the IIR Version.
It should be on Patch level 141 or higher.
You can verify using the command "version" command for Windows. For other platforms, use
$SABIN/cevers.
Example: C:\InformaticaIR\bin>version
FixL141)
3 Place the configuration files required for both matching and cleansing in the SDQConnector
folders on Siebel Server.
ssadq_cfg.xml
ssadq_cfgasm.xml
4 Make sure that the country files and the key files exist in the location where ASM is installed.
If any one of the country files is missing, ASM will not perform cleansing for that country.
NOTE: If AD5 is used, the location of the country database files and key file would be
<drive>\InformaticaIR\ssaas\ad5\ad\db.
To configure ASM
1 Navigate to Administration - Server Configuration > Enterprise Explorer.
2 In the Explorer view, navigate to Component Definitions > Data Quality Manager > Parameters.
3 Within the Parameters list applet, query to verify the state of the following parameters.
5 In the Explorer view, navigate to Component Definitions > Application Object Manager > Call
Center Object Manager (ENU) > Parameters.
NOTE: You can replace the Call Center Object Manager with another Object Manager, depending
upon the application that you are running.
6 Within the Parameters list applet, query to verify the state of following parameters:
[DataCleansing]
Enable = TRUE
Type = ASM
3 Save the file and then launch the Call Center application
4 Navigate to Administration - Data Quality > Data Quality Settings, and verify that Enable
DataCleansing is set to Yes.
5 Navigate to User Preferences > Data Quality, and verify that Enable DataCleansing is set to Yes.
If the entries are blank, do not change anything.
6 Navigate to <Navigation> and verify if a vendor named ASM with the DLL name ssadqasm exists.
If this field does not exist, then create it, using the information in “Field Mappings for ASM.”
Name Account.Name
Vendor Parameter
Name Value
NOTE: The ASM High Deliverability Return Code parameter is optional and applies only if the value
for the DQ Cleanse High Deliverable Address parameter is set to Yes. Please set the values based on
the requirements.
The ssadq_cfgasm.xml file mentioned above in Vendor Parameter needs to be placed in the SDQ
Connector folder where the Siebel application is installed.
The <field> tag mentioned above represents Siebel Fields. <ssafield> represents fields used by ASM.
The fields used by ASM can only be the ones from the following table:
Data_Type Meaning
FName
MName
LName
Building
SubBuilding
HouseNumber
Street1
Street2
POBox
Std_Op Meaning
Camel Convert text to camel case (first letter is upper-cased, remainder are lower-cased)
The connector is not able to cleanse any other field types. Money, Date and other types of data will
remain unchanged if they are passed to the connector.
The Country database used for ASM can be obtained from Technical Support. See the Siebel Data
Quality Administration Guide for information about the sample XML file.
c In the LOV Explorer panel, click on the + sign to expand the node and navigate to the values for
COUNTRY.
The "DQ Cleanse High Delivery Address" vendor parameter is optional. If you want to revert back
to the old address and do not want to cleanse if deliverability is low, set the parameter to "Yes".
By default, the value is "No". This feature may only be required if the Country Database files
provided by Informatica are not the updated ones.
a Navigate to Site Map > Administration - Data Quality > Third Party Administration.
b In the Vendor applet, select ISS, and change the DLL Name value to ssadqsea.
2 If you are using UCM Batch Process and ISS as the third-party data quality vendor, you need to
change the BC field mappings for the Contact - DeDuplication business component:
a Navigate to Site Map > Administration - Data Quality > Third Party Administration
❏ Change the name of the Primary Street Address field to Primary Personal Street Address.
❏ Change the name of the Primary City field to Primary Personal City
❏ Change the name of the Primary State field to Primary Personal State.
❏ Change the name of the Primary Postal Code field to Primary Personal Postal Code.
❏ Change the name of the Primary Country field to Primary Personal Country.
2 Add a new entry called Enable DQ Sync, and set the value for this property to Yes.
a Navigate to Site Map > Administration - Runtime Events > Action Sets.
b Query for the DQ Sync action sets, and click on the Active field to activate them.
c Click the Menu button on the Action Sets applet, and select Reload Runtime Events to reload the
runtime events.
If you customize the SDF file, you must make sure that the value in the Record Length user property
matches the value for the Total Field Length user property in the new SDF file. For more information,
see Data Quality Guide for Oracle Customer Hub. To access this guide, within My Oracle Support,
navigate to the Knowledge tab and search for Doc ID 1282393.1.
3 Change the Profile and Alias properties to the Data Source name configured in Siebel Tools
(ISSDataSrc).
❏ For the Microsoft SQL Server or the IBM DB2 databases, create an ODBC or equivalent
connection and input the name of this in the parameter.
❏ For an Oracle RDBMS, this value should specify the TNS name associated with the
database and not an ODBC or other entry.
■ DSTableOwner = data source table owner (Click Advanced to see this parameter.)
Configuring Object Managers for ISS Data Source (for Data Sync)
Use the following procedure to configure Object Managers for ISS Data Source.
2 Query for the components used with UCM (such as UCM, DQ, EAI, and Workflow components).
3 Select a component, and then select Start Reconfiguration from the main menu.
4 In the lower applet, query for the OM - Named Data Source parameter.
5 Add a comma after the last data source, and add the ISS data source created in the “To configure
the data source definition” procedure. The default name is ISSDataSrc.
6 Save the record and select Commit Reconfiguration from the main menu.
8 Click Synchronize to save the changes into the Gateway configuration file.
2 Add a new entry called Enable DQ Multiple Addresses and set the value for this property to Yes.
3 Add a new entry called Account Match Against and set the value for this property to All Address.
4 Add a new entry called Contact Match Against and set the value for this property to All Address.
For more information about configuring multiple addresses, see the Configuring Deduplication
Against Multiple Addresses section in the Data Quality Guide for Oracle Customer Hub (UCM) To
access this guide, within My Oracle Support, navigate to the Knowledge tab and search for Doc ID
1282393.1.
2 Add a new entry called Enable DQ Multiple Languages and set the value for this property to Yes.
3 Navigate to Site Map > Administration - Data Quality > Third Party Administration, select ISS in
the Vendor applet, click on Vendor Parameter in the child applet, and do the following:
a Add a new entry called Append Account Record Type Field 1 and set the value for this property
to Primary Account Country.
b Add a new entry called Append Contact Record Type Field 1 and set the value for this property
to Primary Personal Country.
c Add a new entry called Batch Append Account Record Type Field 1 and set the value for this
property to Primary Account Country.
d Add a new entry called Batch Append Contact Record Type Field 1 and set the value for this
property to Primary Personal Country.
For more information about configuring support for multiple languages, see the Configuring Multiple
Language Support section in the Data Quality Guide for Oracle Customer Hub (UCM). To access this
guide, within My Oracle Support, navigate to the Knowledge tab and search for Doc ID 1282393.1.
Name Value
Enable Validation - [Optional step in the List Import Process] If this System Preference is turned on,
the validation process will automatically be run after records are imported into UCM (SDH tables).
The validation process will check if any required fields specify in the Import Mapping are missing in
the imported records. Any records that fail validation will have their 'UCM Type Code' changed from
'Batch' to 'Incomplete' and the validation status will be inserted in the 'Error Message' field.
Enable Launch BDM - [Optional step in the List Import Process] If this System Preference is turn on,
the UCM Batch Process will automatically be run after records are imported into staging tables (SDH
tables). This is an existing UCM process to move records in staging to base tables. Users can kick
off the UCM Batch Process as a server task outside of List Import.
Name Value
Map:[Object].[Field] [SDH buscomp Name].[Buscomp Field Name]
For example, in "UCM Account Source Data and History,” there are the following Business Component
user properties:
Name Value
1 In the child SDH Business Component, add a business component user prop: "Parent SDH Id Field
Name", the value is the field that contains its parent SDH ID.
2 In the parent SDH Business Component, add the additional field mapping for the child object (see
the example of field mapping configuration above).
3 In the "UCM Account Import" or "UCM Contact Import" Business Object, add the new child SDH
Business Component and the corresponding link to the parent SDH Business Component.
4 In the “UCM File Manager Service" Business Service, add a new Business Service user property
for the new child SDH buscomp. For example:
■ Account Import Staging Child Buscomp 1 => UCM Account Address Source Data and History
■ Account Import Staging Child Buscomp 2 => UCM Contact Source Data and History
■ OS System: DGM is a Java-based application; it can run on any mainstream Windows, Linux, or
Unix system.
■ Siebel UCM application: In this release of DGM, Siebel UCM is the only supported master hub.
For information about how to install and configure the Siebel application, refer to the Siebel UCM
DGM web service document.
■ DGM source code: The installer will extract DGM source code and install package to a directory.
Within this section, this directory will be referred to as <dgm_home>.
Deployment of DGM application is a process of customizing the DGM system and then transferring it
to the application server. You must preinstall and configure several software programs. Here is the
guideline for the whole installation process.
■ Application Server Installation and Configuration: The Java application will run inside Java
application server. In this section, Weblogic is the target application server.
■ ADF runtime Installation and Configuration: The DGM application uses functionality provided
by the Oracle ADF framework, so the target Weblogic domain should have the ADF runtime
extension installed.
Required Software
The following table describes the required software for DGM.
Installing JDeveloper
Use the following procedure to install JDeveloper.
To install JDeveloper
1 Click Next within the Welcome screen to begin the installation.
2 Accept the default value as the middleware home directory.
NOTE: Within this section, <mw_install_dir> will be used to represent the Middleware Home
directory.
The Complete Installation will install Oracle JDeveloper Studio, the ADF Runtime, and WebLogic
Server.
4 Confirm the product intstallation directories, and click Next to continue with the installation.
5 Select the Start Menu folder where you want to place your shortcuts. This step applies for the
Windows platform only.
7 Select Run Quickstart to open the Quickstart window once the installation process has ended.
Quickstart enables you to easily launch installed components and access online documentation.
3 Select Generate a domain configured automatically to support the following products, select
Oracle JRF - 11.1.1.0 [jdeveloper] and click Next.
The option Base WebLogic Server Domain - 10.3.1.0 [wlserver_10.3]* is already selected.
4 Enter the name and location for the domain if the default values are not correct, and then click
Next.
6 Select Production Mode in Weblogic Domain Startup Mode window, and click Next.
10 Select User Projects < (domainName) > Start > All Programs > Oracle Fusion Middleware
11.1.1.1.0 > User Projects > base_domain > Start Admin Server for Weblogic Server Domain.
11 When the DOS window prompts for the username and password, enter userName and passWord
if asked to do so.
When the window displays message like "Server started in RUNNING mode", the Weblogic server
has started up.
Installing DGM
Use the following procedure to install DGM.
To install DGM
1 Navigate to Disk1\install, and click setup.exe, and click Next.
2 Specify the home where DGM applications and source code will be installed, and click Next.
3 Choose Copy Application to copy the application and source code to home directory without
deployment— otherwise, the DGM application will be deployed after file copy. If you choose Copy
Application, go to Summary. Otherwise, go to the next step.
4 Browse to specify the JDK path. You can also use JDK installed with Oracle Middleware, which
can be found within the Oracle/Middleware/JDK_1.x.xx folder.
5 Browse to specify the ant path. In a default Oracle Middleware installation, the ant path is found
in the Oracle/Middleware/jdeveloper/ant folder.
6 Browse to specify the Weblogic 10gR3 installation path. You must select the root directory of
WLserver installation.
username
10 Specify the endpoint information of the DGM Web service according to your environment:
For example, specify http://sdc60005qe:16662/eai_enu
start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&UserName=SADMIN&a
mp;Password=MSSQL&
NOTE: The endpoint information will be kept in xml files, so escape '&' to '&'.
The install.cmd is the script for DGM installation. Edit the file, change the weblogic_home, jdk_home,
ant_home according to your environment.
cleanse_thresh_value=0.
33,0.66,1.0
cleanse_thresh_color=#d
62800,#ffcf21,#84ae31
After editing the install.cmd and deploy.properties according to your environment, open a dos
window and run install.cmd to deploy the application.
Accessing DGM
Open browser, and access the following URL to visit DGM:
http://<ServerAddress>:<ServerPort>/dgm/
NOTE: Java script and Active Control should be permitted to display the page.
Use the instructions in this topic to implement ACR 476, which provides the new product Siebel Smart
Answer Connector.
For more information about the enhancements provided by ACR 476 for version 8.1.1.1 and later,
see Siebel Smart Answer Connector Guide. This new guide is available on the Siebel 8.1 Bookshelf
on OTN at http://www.oracle.com/technology/documentation/siebel.html.
■ Smart Answer
■ Banter eService
■ Service (SSV)
■ Symbolic Strings
■ eCatalog Admin
■ eMail Response
NOTE: If projects and objects are not locked when you import SIF files, a message appears
indicating which object or project is to be locked. In such a case, lock the project or object, and
then import the SIF file again.
4 Import the SIF files you extracted in Step 1 in the order shown below:
■ 01_sma_project.sif
■ 02_sma_classes.sif
■ 03_sma_dll.sif
■ 04_sma_bussvc.sif
■ 05_sma_io.sif
■ 06_sma_ss.sif
■ 07_sma_applets.sif
■ 08_sma_sct.sif
■ 09_sma_view.sif
■ 10_emr_bussvc.sif
NOTE: SIF files are written in XML format. Their structure is a hierarchy of the objects archived,
listing all of their properties and including any associated scripts: Repository, then Project, then
Object, and then Child Objects.
5 Compile the changes into an updated repository file (SRF file). Copy the new SRF file to the Siebel
Server installation, under SIEBSRVR_ROOT\objects\enu.
6 Start the Siebel Server (or servers) using the newly compiled SRF.
For more information about starting Siebel Servers, see Siebel System Administration Guide.
a Navigate to the SIEBSRVR_ROOT\smartanswer directory, and then open the SAConfig.xml file
with a text editor.
b Replace the value for NLPAdapterDLLName with the correct location and filename.
c Verify the value for the FacadeName property. The value depends on the third-party product you
are using with Siebel Smart Answer.
8 Create a new smartanswer directory and subdirectories under the Siebel File System.
a Make sure the File System location is correct, accessible, and writable.
For example, if you map your File System to fs, then the resulting directory structure is
similar to that shown below.
fs
smartanswer
export
import
a Navigate to the Administration - Data screen, and then the List of Values view.
❏ Type = SEARCH_SMART_ANSWER
a Navigate to the Administration – Web Services screen, then the Inbound Web Services view.
❏ Namespace = http://siebel.com/asi/
❏ Name = SmartAnswerService
❏ Status = Active
a Navigate to the Administration – Web Services screen, then Inbound Web Services, and then the
Service Ports view.
b Click New, and then add the following values:
❏ Name = Default
❏ Transport = HTTP
❏ Address = http://130.35.27.238/eai_enu/
start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&UserName=
USERNAME&Password=PASSWORD
where:
❏ Binding = SOAP_RPC_LITERAL
a Navigate to the Administration – Web Services screen, Inbound Web Services, Service Ports, and
then the Operations view.
b Click New to create new operations using the values shown in the following table.
Setting Up Siebel Email Response for Use with Siebel Smart Answer
Connector
To make the Siebel Smart Answer Connector functionality available for use in Siebel Email Response,
you must set up the Siebel Email Response user interface.
To set up Siebel Email Response for use with Siebel Smart Answer Connector
1 Verify the following DLLs are available in the SIEBSRVR_ROOT\bin directory:
■ swcommfr.dll
■ sscommsv.dll
■ sscmclnt.dll
■ sscacabc.dll
■ swcacafr.dll
■ Mail Agent
■ eMail Response
5 Import the SIF files you extracted in Step 2 on page 279 in the order shown below:
■ EMR_UI_Applets.sif
■ EMR_UI_BC.sif
■ EMR_UI_BO.sif
■ EMR_UI_BS.sif
■ EMR_UI_Class.sif
■ EMR_UI_Screen.sif
■ EMR_UI_View.sif
■ EMR_UI_Webtemplate.sif
■ EMR_UI_WF.sif
NOTE: If projects and objects are not locked when you import SIF files, a message appears
indicating which object or project is to be locked. In such a case, lock the project or object, and
then import the SIF file again.
6 Compile the changes into an updated repository file (SRF file). Copy the new SRF file to the Siebel
Server installation, under SIEBSRVR_ROOT\objects\enu.
7 Start the Siebel Server (or servers) using the newly compiled SRF.
For more information about starting Siebel Servers, see Siebel System Administration Guide.
For information about working with workflows, see Siebel Business Process Framework: Workflow
Guide.
For more information about launching this client type, see the Siebel Installation Guide for
the operating system you are using.
c Click New to create a new view and add the following values:
To add views/responsibilities
1 Connect to the Siebel application with /editseeddata switch.
2 Navigate to Site Map > Administration Application > Views, and add the views and
responsibilities listed in the following table:
View Responsibility
CS CG My High Level Planning List View Siebel Administrator, CG Key Account Manager
CS CG My Team's High Level Planning List Siebel Administrator, CG Key Account Manager
View
CS CG All High Level Planning List View Siebel Administrator, CG Key Account Manager
CPG Plan High Level Planning View Siebel Administrator, CG Key Account Manager
CPG Account High Level Planning View Siebel Administrator, CG Key Account Manager
CPG Promotion Literature List View Siebel Administrator, CG Key Account Manager
CPG Promotion Product Performance View Siebel Administrator, CG Key Account Manager
SIS CS Corporate Promotions Target View Siebel Administrator, CG Key Account Manager
SIA CS ADL Authorized Category Product Siebel Administrator, CG Key Account Manager
View
SIA CS ADL Authorized Product View Siebel Administrator, CG Key Account Manager
CG Account Merchandising Location Product Siebel Administrator, CG Key Account Manager
View
View Responsibility
CS Plan Account Promotion Audit Trail View Siebel Administrator, CG Key Account Manager
CS Visit Parent Account Promotions View Siebel Administrator, CG Key Account Manager
CS Claim All Across Orgs Claims View Siebel Administrator, CG Key Account Manager
Lists of Values
The following section details how to add the LOVs provided in ACR 480.
To add LOVs
1 Connect to the Siebel application.
2 Navigate to Site Map > Administration Data > List of Values Explorer (for List of Values Type)
and List of Values (for LOV type values), and create or modify the following LOV Type/LOVs with
Translate = Y for all the values:
New or
Needs LOV Type Language-
Modification? Code Display Value Independent Code Comments
New SVP Source Baseline PY Baseline PY Currency Order = 7
Currency
New or
Needs LOV Type Language-
Modification? Code Display Value Independent Code Comments
Modify SVP Source Target Basis Target Basis Currency Change Order =
Currency 15
Modify SVP Source Target Basis Target Basis Cases Change Order =
Qty 16
Modify SVP Source Target Qty Target Baseline Cases Change Order =
20
New or
Needs LOV Type Language-
Modification? Code Display Value Independent Code Comments
New or
Needs LOV Type Language-
Modification? Code Display Value Independent Code Comments
New or
Needs LOV Type Language-
Modification? Code Display Value Independent Code Comments
State Model
Use the following procedure to add State Models.
3 Add the following new states for the CS Claim Status State Model: Closed, In Progress, Inactive,
Open (Default), Resolved.
4 Add the transactions described in the following tables for the CS Claim Status State Model:
5 Add new states for the State Models in the following table:
New or Needs
Modification? State Model Name Business Component Field
New or Needs
Modification? State Model Name Business Component Field
6 Add the new states for the State Models: Requested, Approved, and Rejected.
Pending Requested
Pending Cancelled
Requested Cancelled
Approved Cancelled
Approved Submitted
Rejected Pending
Rejected Requested
Rejected Cancelled
Submitted Paid
Submitted Cancelled
Paid Voided
9 Add the following new states for the State Models: Requested (Default), Approved, and Rejected.
10 Add the transactions listed in the following table for the State Models:
Requested Approved
Requested Rejected
11 Log out of the Siebel application and bounce the Siebel Server.
Audit Trail
Use the following procedure to create new Audit Trails.
2 Navigate to Site Map > Administration - Audit Trail > and create new Audit Trails with the
information in the following tables:
New? Audit Trail Buscomp Base Table Update Delete Insert Assoc
Workflows
The following procedure details how to add the workflows that are associated with ACR 480.
2 In Object Explorer, select Project, and lock the CPG Plan, CPG Corporate Promotion, and ADL
Enhancement projects.
3 Select Workflow Process in the Object Explorer, select Import Workflow Process from the right-
click menu in the list view pane, and import the following workflow xml files:
4 Navigate to View > Toolbars, and make sure that the WF/Task Editor toolbar is checked.
8 Navigate to Site Map > Administration - Business Process > Workflow Deployment , and verify
that all the workflows show up in the Active Workflow Processes List at the bottom.
Table 13 contains details about the SVPFilterYear profile variable, Table 14 contains information about
the SVP Current Year Filter rule set, and Table 15 contains information about the Current Filter rule.
Rule Set
SVP Current Year Filter Y Select today's date SVP Current Year Filter
Rules
Name Rule Type Seq Active Start Date End Date Description
Current Filter Expression 1 Y Select today's date Filter for current year
■ Make sure that the "SVPFilterYear" Profile Variable contains the proper values before you
associate these rules to the applet.
■ When setting rules and when associating the rules with the applets, remember to use the
"Reload Personalization Rules" menu option.
Changing Visibility
The following procedure details how to change visibility for the Plan Team and Promotion Team
Business Components.
To change visibility for the Plan Team and Promotion Team Business Components
1 In Object Explorer, navigate to Business Component.
2 For the Plan Team Business Component, query for Name = CPG Plan Account , and lock the
project using the right-click menu.
3 For the Promotion Team Business Component, query for Name = CPG Plan Account Promotion,
and lock the object using the right-click menu.
4 In Object Explorer, navigate to the Business Component View Modes for each Business
Component.
6 Change the value of the Visibility MVL from Account Position to Position.
7 Change the value of the Visibility MVF from Account Sales Rep to Sales
Changing the User Properties for the Plan Team and Promotion Team
Business Components
The following procedure details how to change the user properties for the Plan Team and Promotion
Team Business Components.
To change the user properties for the Plan Team and Promotion Team Business
Components
1 In Object Explorer, navigate to Business Component.
2 For the Plan Team Business Component, query for Name = CPG Plan Account, and lock the object
using the right-click menu.
3 For the Promotion Team Business Component, query for Name = CPG Plan Account Promotion,
and lock the object using the right-click menu.
4 In Object Explorer, navigate to Business Component User Properties for each Business
Component.
3 Navigate to Views, query for the “SIA CS ADL Authorized Category Product View” and “SIA CS
ADL Authorized Product View” views and activate them.
4 Query for the “SIA CS Source of Supply Accounts Products View” view and disable it.
For more information about Siebel Consumer Goods, see Siebel Consumer Goods Guide on the Siebel
Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.
For information about how to implement ACR 488, within My Oracle Support, navigate to the
Knowledge tab and search for Doc ID 880604.1.
For more information about the Siebel Hospitality application, see Siebel Hospitality Guide on the
Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.
OK Button Disabled
Category: Quotes and Orders
When promotions are upgraded through the Bulk Request function, the OK button is not enabled.
When users try to add an excluded product with scope all/exclude, Bulk Requests remains in the
Processing status.
[Siebel]
…..
SymStrPrefix = SBL_
……..
❏ Asset Management
❏ Contact
❏ Order Entry
❏ Product
❏ Product Selection UI
❏ Quote
❏ Quote (UI)
❏ Srvagree
❏ Symbolic Strings
❏ Table ListManagement
❏ Table BulkRequest
❏ EIM BulkRequest
❏ EIM ListManagement
5 Import the following SIF files in the order shown from the <Tools Installed
Directory>\REPPATCH\ BulkRequest_ACR499\REPOSITORY folder into Siebel Tools using the
Tools > Import from Archive option. Use the Merge option in Siebel Tools Import Wizard.
NOTE: For example, if Symbolic String is not exposed in View > Option > Object Explorer
>Siebel Object, navigate to View > Option, click the Object Explorer tab and check Symbolic
String.
❏ Tables
❏ Symbolic Strings
❏ Class
❏ Picklist
❏ Business Service
❏ Business Components
❏ Links
❏ Business Objects
❏ Integration Objects
❏ Applets
❏ Views
❏ Screens
NOTE: If you have not locked the required projects, you may receive a warning error message.
If you receive the warning error message, lock the project displayed in the message.
6 After the SIF files have been imported, within Object Explorer, navigate to Table.
b Use the "Apply/DDL" button to apply the changes to the physical database.
c Choose the "Current Query" option from the Table drop-down list.
■ ODBC data source= <DSN Name> (create the DSN if you get a “TNS not resolved” error
message)
2 Click on Integration Object in the Object Explorer, and query for SIS OM Order.
3 Right-click on the SIS OM Order integration object, and choose Copy Record.
5 Within the ABO Build Request Order integration object, select the MACD Order Entry - Line Items
integration component.
6 Click on Integration Component User Prop in OBLE and add a record with the following values:
❏ Name: SelectiveChildQuery
❏ Value: Y
7 Right-click on ABO Bulk Request Quote and choose Compile Selected Objects to compile the
integration object.
2 Click on Integration Object in the Object Explorer, and query for SIS OM Quote.
3 Right-click on the SIS OM Quote integration object and choose Copy Record.
5 Within the ABO Bulk Request Quote integration object, select the MACD Quote Item integration
component.
6 Click on Integration Component User Prop and add a record with the following values:
❏ Name: SelectiveChildQuery
❏ Value: Y
7 Right-click on ABO Bulk Request Quote and choose Compile Selected Objects to compile the
integration object.
2 Compile all the locked projects using Tools > Compile Projects.
3 Save the srf file to <Siebel Server Install folder>\objects\ENU\siebel_sia.srf on the installed
Siebel server.
a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC),
navigate to the System DNS tab, and click Add.
b Select the "Siebel Oracle90" driver (from Datadirect Technologies).
2 Navigate to the directory where you installed Siebel Tools and change the directory to
REPPATCH\BulkRequest_ACR499.
NOTE: Before executing the next step, make sure that the dataimp.exe file exists in the <Tools
Install Directory>/bin directory.
<Tools Install Directory> - Replace with your Siebel Tools install directory
<Database Platform> - Replace with your database platform (ORACLE, DB2UDB or MSSQL)
4 Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure import completed
successfully
5 Depending upon the language that you are installing, complete Step 6 or Step 7.
<Tools Install Directory> - Replace with your Siebel Tools install directory
<Database Platform> - Replace with your database platform (ORACLE, DB2UDB or MSSQL)
b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
7 If you are installing a language other than ENU, perform the following steps:
a Run the following command after importing ACR499_VACR499BLK_Seed.dat file to import the
locale specific seed_locale_XXX.dat, where XXX is the language code.
<Tools Install Directory> - Replace with your Siebel Tools install directory
2 In the Options tab, under Languages, select a source language and a target language.
3 Click the Import tab, and enter the directory path and name of the file you want to import. For
example, enter <Tools Install Directory>\REPPATCH\BulkRequest_ACR499\LMU\<target
language>\lmu_srm.xlf3.
Default
Local
View Name Description Access
ABO Bulk Request Action Set Quotes View ABO Bulk Request Action Set Quotes Y
View
ABO Quote Item Drill Down View ABO Quote Item Drill Down View Y
ABO BR List Mgmt Assets View - All ABO BR List Mgmt Assets View - All Y
ABO Bulk Request Template View ABO Bulk Request Template View Y
ABO Bulk Request Explode Exceptions View ABO Bulk Request Explode Y
Exceptions View
Type Translate
ABO_BR_ACTSET_TEMPLTE_TYPE Y
ABO_BR_TEMPLTE_INSTANCE_SCOPE Y
ABO_BR_TEMPLTE_INSTANCE_TYPE Y
2 Navigate to Administration - Data > List Of Values, and verify the following values:
NOTE: The values are for ENU only and the Display Value and the Language Independent Code
value is the same. The Language Name is English-American for all the LOV values.
Display Replication
Type Value LIC Language Name Order Active Translate Level
Display Replication
Type Value LIC Language Name Order Active Translate Level
3 After verifying the records in the preceding table, navigate to Menu > Clear Cache.
4 Log out of the Siebel application and then log back in.
Signals
2 In the Signals list view, confirm that the signal ABOBulkRequestCheckEligibility has been created.
3 In the Versions list view, click on the Work Space link to drill down to the Actions list view.
Name Value
CPScope Whole
Name Value
RowScope Selected
Variable Map - Row Set ABO Bulk Request Eligibility Variable Map - Row Set
Variable Maps
Use the procedures in the following section to verify the ACR 499 variable maps.
To verify the ABO Bulk Request Eligibility Variable Map - Row Set variable map
1 Navigate to Administration - Order Management > Variable Maps.
2 Verify that the ABO Bulk Request Eligibility Variable Map - Row Set variable map has been
created.
NOTE: The Path, Mode, and Source Type fields are shown in the Variable Sources view.
In/ On
Name Out Type Null Path Mode Source Type
$Current/Line Item/
Covered Asset Product Id
In/ On
Name Out Type Null Path Mode Source Type
In/ On
Name Out Type Null Path Mode Source Type
Mode Object
Data Maps
Use the following procedures to verify the ACR 499 data maps.
To verify the ABO Bulk Request Action Set Agreement Inbound Map
1 Navigate to Administration Integration > Data Map Editor.
2 In the Integration Component Map Applet, select the following records and verify the Source
Expression and Target Field Name as shown in the following table.
NOTE: The Source Expression and Target Field Name fields are shown in the Integration Field
Map Applet.
To verify the ABO Bulk Request Action Set Asset Inbound Map
1 Navigate to Administration Integration > Data Map Editor.
2 In the Integration Component Map Applet, select the following records and verify the Source
Expression and Target Field Name as shown in the following table.
NOTE: The Source Expression and Target Field Name fields are shown in the Integration Field
Map Applet.
Source
Name Component Target Component Source Expression Target Field Name
Action Set Header Action Set [Owner Account Id] Customer Account Id
To verify the ABO Bulk Request Action Set Contact Inbound Map
1 Navigate to Administration Integration > Data Map Editor.
2 In the Integration Component Map Applet, select the following records and verify the Source
Expression and Target Field Name as shown in the following table.
NOTE: The Source Expression and Target Field Name fields are shown in the Integration Field
Map Applet.
Target
Name Source Component Component Source Expression Target Field Name
To verify the ABO Bulk Request Action Set Network Inbound Map
1 Navigate to Administration Integration > Data Map Editor.
2 In the Integration Component Map Applet, select the following records and verify the Source
Expression and Target Field Name as shown in the following table.
NOTE: The Source Expression and Target Field Name fields are shown in the Integration Field
Map Applet.
Integration Target
Name Component Component Source Expression Target Field Name
Action Set Header Action Set [Owner Account Id] Customer Account Id
Number] Number
[Root Id] Root Asset Id
[Service Id] Service Id
2 In the Integration Component Map Applet, select the following records and verify the Source
Expression and Target Field Name as shown in the following table.
NOTE: The Source Expression and Target Field Name fields are shown in the Integration Field
Map Applet.
Source Target
Name Component Component Source Expression Target Field Name
Activating Workflows
Use the following procedure to activate the workflows for ACR 499.
2 Right-click Import Workflow Process and import the .xml workflow from the <Tools Installed
Directory>\REPPATCH\BulkRequest_ACR499\REPOSITORY\Workflow folder under the following
projects.
NOTE: You must import the workflows in the order listed in the following table.
3 ABO Bulk Request - Edit Iterate Process New ABO Bulk Request
10 ABO Bulk Request - Edit Complex Asset New ABO Bulk Request
Workflow
12 ABO Bulk Request - Disconnect Asset Sub- New ABO Bulk Request
process
13 ABO Bulk Request - Edit Promotion Related New ABO Bulk Request
Asset Workflow
15 ABO Bulk Request - Promotion - Add Missed New ABO Bulk Request
Items Sub Process
18 ABO Bulk Request - All Instances Sub Modified ABO Bulk Request
Process
24 ABO Bulk Request - Check Eligibility & New ABO Bulk Request
Compatibility
25 ABO Bulk Request - Process Action Sub- Modified ABO Bulk Request
Process Workflow
26 ABO Bulk Request - Disconnect Products & New ABO Bulk Request
Services Process
28 ABO Bulk Request - All Exclusive Process Modified ABO Bulk Request
Action Sub-Process Workflow
29 ABO Bulk Request - Prepare Action Set Sub- Modified ABO Bulk Request
Process Workflow
30 ABO Bulk Request - Sub Process Workflow Modified ABO Bulk Request
31 ABO Bulk Request - Parallel Sub Process Modified ABO Bulk Request
Workflow
33 ABO Bulk Request - Submit Driver Process Modified ABO Bulk Request
Workflow
34 ABO Bulk Request Add Item Customize Modified ABO Bulk Request
SubProcess Quotes
35 ABO Bulk Request Add Item Customize Modified ABO Bulk Request
Process
NOTE: Make sure that the new projects have been imported and that the new SRF has been
applied to the server before you import and activate the workflows.
b Navigate to Administration - Business Process > Workflow Deployment and activate the
workflows in the following order:
NOTE: The status of each workflow changes from In Progress to Complete after the workflow is
published.
Default
Local
View Name Description Access
ABO Bulk Request Action Set Quotes View ABO Bulk Request Action Set Y
Quotes View
ABO Quote Item Drill Down View ABO Quote Item Drill Down View Y
ABO BR List Mgmt Assets View - All ABO BR List Mgmt Assets View - Y
All
ABO Bulk Request Template View ABO Bulk Request Template View Y
ABO Bulk Request Explode Exceptions View ABO Bulk Request Explode Y
Exceptions View
3 Navigate to the Responsibilities applet and associate the Siebel Administrator responsibility to all
of these views.
4 Navigate to Administration User > Users, query for SADMIN in the User Id field, and add the
Siebel Administrator responsibility to the SADMIN user.
2 Query for the Product Eligibility Variable Map - Context variable map and lock the object.
4 In the Variable Definition view, query for the following records and create the Path, Mode, and
Source Type as shown in the following table.
NOTE: The Path, Mode, and Source Type fields are shown in the Variable Sources view.
6 Navigate back to the Variable Maps link and query for Product Eligibility Variable Map - Context
again.
7 Click Release New Version and select Menu > Clear Cache.
To modify the Product Eligibility Variable Map - Row Set variable map
1 Navigate to Administration - Order Management > Variable Maps.
2 Query for the Variable Product Eligibility Variable Map - Row Set and lock the object.
4 In the Variable Definition view, query for the following records and create the Path, Mode, and
Source Type as shown in the following table.
NOTE: The Path, Mode, and Source Type fields are shown in the Variable Sources view.
Source
Name In/Out Type On Null Path Mode Type
Source
Name In/Out Type On Null Path Mode Type
6 Navigate back to the Variable Maps link and query for Product Eligibility Variable Map - Row Set
again.
7 Click Release New Version and select Menu > Clear Cache.
2 Query for the Cfg Eligibility Variable Map - Context variable map and lock the object.
4 In the Variable Definition view, query for the following records and create the Path, Mode, and
Source Type as shown in the following table.
NOTE: The Path, Mode, and Source Type fields are shown in the Variable Sources view.
Source
Name In/Out Type On Null Path Mode Type
Any Header
6 Navigate back to the Variable Maps link and query for Cfg Eligibility Variable Map - Context again.
7 Click Release New Version and select Menu > Clear Cache.
2 Query for the Default Eligibility Variable Map - Context variable map and lock the object.
4 In the Variable Definition view, query for the following records and create the Path, Mode, and
Source Type as shown in the following table.
NOTE: The Path, Mode, and Source Type fields are shown in the Variable Sources view.
Source
Name In/Out Type On Null Path Mode Type
6 Navigate back to the Variable Maps link and query for Default Eligibility Variable Map - Context
again.
7 Click Release New Version and select Menu > Clear Cache.
To modify the Default Pricing Eligibility Variable Map - Row Set variable map
1 Navigate to Administration - Order Management > Variable Maps.
2 Query for the Default Pricing Eligibility Variable Map - Row Set variable map and lock the object.
4 In the Variable Definition view, query for the following records and create the Path, Mode, and
Source Type as shown in the following table.
NOTE: The Path, Mode, and Source Type fields are shown in the Variable Sources view.
Source
Name In/Out Type On Null Path Mode Type
6 Navigate back to the Variable Maps link and query for Default Pricing Eligibility Variable Map -
Row Set again.
7 Click Release New Version and select Menu > Clear Cache.
XA_to_XA XA XA
XA_to_XA XA XA
6 In the Integration Field Applet, change the Source Expression [Order Type] to LookupValue
("FS_ORDER_TYPE", "Bulk Request Template Order").
8 Delete the following values from the Integration Field Map Applet for all three Integration
Component Maps.
[Id] Id
[Updated] Updated
9 Delete the following fields from Integration Field Map Applet, corresponding to the
Header_to_Header mappings.
10 Delete the following fields from Integration Field Map Applet, corresponding to the XA_to_XA
mappings.
6 In the Integration Field Applet, change the Source Expression [Quote Type] to LookupValue
("QUOTE_TYPE", "Bulk Request Template Quote").
8 Delete the following values from the Integration Field Map Applet for all three Integration
Component Maps.
[Created] Created
[Id] Id
[Updated] Updated
9 Delete the following fields from Integration Field Map Applet, corresponding to the
Header_to_Header mappings.
[Revision] Revision
10 Delete the following fields from Integration Field Map Applet, corresponding to the Line
Item_to_Line Item mappings.
11 Delete the following fields from Integration Field Map Applet, corresponding to the XA_to_XA
mappings.
If you are using the Bulk Requests functionality for the first time, you must add a new List of Values.
Replic
Language ation
Type Display Value LIC Name Order Active Translate Level
2 Navigate to Inbox Administration > All Inbox Types and verify that the records listed in the
following table exist.
3 Select each record from Step 2 and navigate to the Translations Tab.
4 If the display name has not been added, then add it with the appropriate language. For example,
for "Bulk Request Exception" for ENU, add a record with the following values:
In the DEU application, the display mode in message type is ENU, not DEU.
1 Within the Siebel application, navigate to Administration - Order Management > Message Types,
and query for the following message types:
2 Change the display mode of the message type from ENU to the corresponding language. In this
case, change the display mode of the following message types from ENU to DEU:
3 For each of the message types mentioned above, select Menu > Clear Cache.
Subcategory: Administration
In the DEU application, users receive an error message when they try to debundle promotions.
NOTE: Before you begin the following procedures, within Siebel Tools, query for the ISS Promotion
Workflow project, and lock it.
2 Query for the ISS Promotion Upgrade Process workflow and revise the workflow.
3 In the revised workflow, select Edit Workflow Process from the menu, and add the following
Process Property.
4 Add the following output argument in the Get Account Details step:
Business Business
Property Name Type Component Name Component Field
5 Add the following input argument in the Disconnect Old Promotion step:
2 Query for the ISS Promotion Split Process workflow and revise the workflow.
3 In the revised workflow, select Edit Workflow Process from the menu, and add the following
process property:
4 Add the following output argument in the Get Account Details step:
Business Business
Property Name Type Component Name Component Field
5 Add the following input argument in the Disconnect Old Promotion step.
2 Query for the ISS Promotion Merge SubProcess workflow and revise the workflow.
3 In the revised workflow, select Edit Workflow Process from the menu, and add the following
process property.
4 Add the following output argument in the Get Account Details step:
5 Add the following input argument in the Disconnect Old Promotion step:
2 Query for the ISS Promotion Debundle Integration SubProcess workflow and revise the workflow.
3 In the revised workflow, select Edit Workflow Process from the menu, and add the following
process property.
Business
Name Display Name In/Out Object Data Type
2 Query for the ISS Promotion Debundle Process workflow and revise the workflow.
3 In the revised workflow, select Edit Workflow Process from the menu, and add the following
process property:
4 Add the following output argument in the Get Account Details step:
NOTE: After activating all the workflows, reload the run time events.
2 Make sure that the SymStrPrefix entry has been set to SBL_
[Siebel]
…..
SymStrPrefix = SBL_
……..
■ Account
■ Asset Management
■ Cfg RTC
■ FS Agreement
■ MACD Performance
■ Order Entry
■ Product Selection UI
■ Quote
■ Quote (UI)
■ Symbolic Strings
■ Table Order
■ Table Product
■ Table ProductPromotion
■ Table Quote
■ UMSUI
5 Import the following SIF files from the <Unzipped Folder>\ACR500\Objects folder into Siebel
Tools using the Tools Import from Archive option. Import these files in the order listed below. Use
the Merge option in Siebel Tools Import Wizard.
NOTE: If the symbolic strings are not exposed in View > Option > Object Explorer > Siebel
Object, navigate to View > Option, click the Object Explorer tab and check the Symbolic String.
■ Tables.sif
■ Symbolic Strings.sif
■ Web Templates.sif
■ Classes.sif
■ Commands.sif
■ Picklists.sif
■ Business Services.sif
■ Business Components.sif
■ Links.sif
■ Business Objects.sif
■ Integration Objects.sif
■ Applets.sif
■ Views.sif
■ Screens.sif
NOTE: If you have not locked the required projects, you may receive a warning error message.
If you receive the warning error message, then lock the project displayed in the message.
6 After you have imported the SIF files, within Object Explorer, navigate to Table, and do the
following:
b Click the Apply/DLL button, click Apply, and then click OK to apply the changes to the physical
database.
7 Within the Apply Schema dialog box, provide the following credentials to connect to the
database:
❏ ODBC data source= <DSN Name> (create the DSN if you get a TNS not resolved error
message).
9 Compile all the locked projects using Tools > Compile Projects.
10 Save the SRF to <Siebel Server Install folder>\objects\ENU\siebel_sia.srf on the installed Siebel
server.
13 Right-click on Import Workflow Process and import the .xml workflow from the <Unzipped
Folder>\ACR500\Workflows folder under the following projects:
29 SIS OM Edit Delta Quote Line Item Modified SIS OM Base Architecture
NOTE: Make sure that the new projects are imported and that the new SRF has been applied to
the server before you impor t and activate the workflows.
14 After you import the workflows, within Siebel Tools, publish the workflows in the same order in
which they were imported.
NOTE: After the workflows are published, the status of each workflow changes from In Progress
to Complete.
Sequence Workflow
Sequence Workflow
17 Navigate to Administration - Runtime Events, and choose to reload runtime events for each
event.
NOTE: Before you perform the following step, make sure that the dataimp.exe file exists in the
<Tools Install Directory>/bin directory.
<Tools Install Directory> - Replace with your Siebel Tools install directory
<Database Platform> - Replace with your database platform (ORACLE, DB2UDB or MSSQL)
3 Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
4 Depending upon the language that you are installing, perform Step 5 or Step 6.
<Tools Install Directory> - Replace with your Siebel Tools install directory
<Database Platform> - Replace with the database platform (ORACLE, DB2UDB or MSSQL)
b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
c After you have imported the seed data, you must verify that it imported correctly. For more
information about verifying seed data, see “Verifiying Seed Data for ACR 500” on page 332.
6 If you are installing a language other than ENU, perform the following steps:
a Run the following command after importing ACR500_Seed.dat file to import the locale-specific
seed_locale_XXX.dat, where XXX is the language code.
<Tools Install Directory> - Replace with your Siebel Tools install directory
b After you have imported the seed data, you must verify that it imported correctly. For more
information about verifying seed data, see “Verifiying Seed Data for ACR 500” on page 332.
NOTE: The following procedure applies to customers who are installing languages other than ENU.
It does not apply to customers who are installing only ENU.
2 In the Options tab, under Languages, select a source language and a target language.
4 Enter the directory path and name of the file you are going to import.
Default
Local
View Name Description Access
ISS Promotion Upgrade Aggregate View ISS Promotion Upgrade Aggregate View Y
3 Navigate to the Responsibilities applet and associate the Siebel Administrator responsibility to all
of these views.
4 Navigate to Administration User > Users, query for SADMIN in the User Id field, and add the
Siebel Administrator responsibility to the SADMIN user.
5 Stop the Siebel Server and then restart it to make your changes visible.
6 Log into the Siebel application and verify that the Split and Merge view appears on the
Administration - Product > Product Promotions.
NOTE: Only the order of the LOVs has changed in the preceding table.
2 Query for the Variable map Default Eligibility Variable Map - Context and lock the object.
4 In the Variable Definition view, query for the records listed in the following table and create the
Path, Mode and Source Type fields.
NOTE: Path, Mode and Source Type fields are shown in the Variable Sources view.
AccountHeader AccountHeader
6 Navigate back to the Variable Maps link and query for Promotion Upgrade Eligibility Variable Map
- Context again.
7 Click Release New Version and select Menu > Clear Cache
2 Query for the Variable map Default Eligibility Variable Map - Row Set ProdProm and lock the
object.
4 In the Variable Definition view, query for the following records and create the Path, Mode and
Source Type fields.
NOTE: Path, Mode and Source Type fields are shown in the Variable Sources view.
6 Navigate back to the Variable Maps link and query for Default Eligibility Variable Map - Row Set
ProdProm again.
7 Click Release New Version and select Menu > Clear Cache.
System
Preference
System Preference Name Value Description
NOTE: Setting the value for "All Assets" to N disables Asset Based Promotion Recommendation and
Apply - Scenario 2.
Default
Local
View Name Description Access
ISS Promotion Upgrade Aggregate View ISS Promotion Upgrade Aggregate View Y
Type Translate
PROMO_AGGREGATE_DURATION Y
PROMO_OPER_TYPE Y
2 Navigate to Administration - Data > List Of Values, and verify the following values:
NOTE: The values are for ENU only and the Display Value and the Language Independent Code
value are the same. The Language Name is English-American for all the LOV values.
Signals
Use the procedures in the following section to verify the signals for ACR 500.
2 In the Signals list view, confirm that the signal SplitPromotion has been created.
3 In the Versions list view, click on the Work Space link to drill down to the Actions list view.
Name Value
Name Value
2 In the Signals list view, confirm that the signal MergePromotion has been created.
3 In the Versions list view, click on the Work Space link to drill down to the Actions list view.
Name Value
2 In the Signals list view, confirm that the signal AddToPromotion has been created.
3 In the Versions list view, click on the Work Space link to drill down to the Actions list view.
Name Value
2 In the Signals list view, confirm that the signal AddToPromotionBilling has been created.
3 In the Versions list view, click on the Work Space link to drill down to the Actions list view.
4 In the Actions list view, verify the following:
Name Value
2 In the Signals list view, confirm that the signal GetPromoUpgradeEligibility has been created.
3 In the Versions list view, click on the Work Space link to drill down to the Actions list view.
Name Value
CPScope Whole
RowScope Selected
Variable Map - Row Set Promotion Upgrade Eligibility Variable Map - Row Set
2 In the Signals list view, confirm that the signal GetAgreementConditionalCharge has been
created.
3 In the Versions list view, click on the Work Space link to drill down to the Actions list view.
To verify the Promotion Upgrade Eligibility Variable Map - Context variable map
1 Navigate to Administration - Order Management > Variable Maps.
2 Verify that the variable map Promotion Upgrade Eligibility Variable Map - Context has been
created.
NOTE: The Path, Mode and Source Type fields are shown in the Variable Sources view.
Any AccountHeader
To verify the Promotion Upgrade Eligibility Variable Map - Row Set variable map
1 Navigate to Administration - Order Management > Variable Maps.
2 Verify that the variable map Promotion Upgrade Eligibility Variable Map - Row Set has been
created.
NOTE: The Path, Mode and Source Type fields are shown in the Variable Sources view.
Any Product
AssetLineItem AssetLineItem
Message Types
Use the procedures in the following section to verify the message types for ACR 500.
2 In the Message Type List view, verify that the Message Type Promotion - Multiple Commitment
Broken Message - Debundle has been created.
Display
Name Mode Group Title Short Text Full Text
Response Suppress
Sequence Name Type Log Repetition Business Service Method
Payload Field
Promotion Message
2 In the Message Type list view, verify that the Message Type Promotion - Broken Commitment
Error - Debundle has been created.
Display
Name Mode Group Title Short Text Full Text
Response Suppress
Sequence Name Type Log Repetition Business Service Method
Payload Field
Penalty
2 In the Message Type list view, verify that the Message Type Promotion - Component Commitment
Penalty has been created.
Display
Name Mode Group Title Short Text Full Text
Payload Field
Integration Id
Name
Penalty
2 In the Message Type list view, verify that the Message Type Promotion - Bottomup
Recommendation For Assets has been created.
Display
Name Mode Group Title Short Text Full Text
Suppress
Sequence Name Response Type Log Repetition Field Business Service Method
Account Id Account Id
2 In the Message Type list view, verify that the Message Type Promotion - No Promotion
Recommendations has been created.
Display
Name Mode Group Title Short Text Full Text
2 In the Message Type list view, verify that the Message Type Promotion - Multiple Commitment
Broken Message - Components has been created.
Display
Name Mode Group Title Short Text Full Text
Please
disconnect each
asset individually
to view the
specific terms.
Payload Field
Message
2 In the Message Type list view, verify that the Message Type Promotion - Broken Component
Commitment Error has been created.
Display
Name Mode Group Title Short Text Full Text
Suppress
Sequence Name Response Type Log Repetition Business Service Method
Payload Field
Commitment End
Date
Penalty
2 CreatePromotionItemAgreement
❏ EIM Asset
❏ EIM Order
❏ EIM Quote
❏ Table Asset
❏ Table Order
❏ Table Quote
❏ Cfg RTC
❏ Cfg JS
❏ Asset Management
❏ Order Entry
❏ Symbolic String
❏ MACD Performance
❏ Quote
2 Import the following SIF files in the order shown from the <Unzipped Folder>\ACR502 folder into
Siebel Tools using the Import From Archive option. Use the Merge option in Siebel Tools Import
Wizard.
NOTE: If Symbolic String is not exposed in View > Option > Object Explorer > Siebel Object,
navigate to View > Option, click the Object Explorer tab, and check Symbolic String.
❏ Applet.sif
❏ Business Component.sif
❏ Business Object.sif
❏ Business Service.sif
❏ Integration Object.sif
❏ Link.sif
❏ Symbolic String.sif
NOTE: If you have not locked the required projects, you may receive a warning error message.
If you receive the warning error message, then lock the project displayed in the message.
3 After you have imported the SIF files, navigate to Table in the Object Explorer.
a Query for all the changed objects and select them.
b Click the Apply/DDL button to apply the changes to the physical database.
❏ ODBC data source= <DSN Name> (create the DSN if you receive a "TNS not resolved
error message")
7 On the installed Siebel Server, save the SRF file to either <Siebel Server Install
folder>\objects\ENU\siebel_sia.srf (if you are an SIA customer) or to <Siebel Server Install
folder>\objects\ENU\siebel.srf (if you are an SEA customer).
Web Channel Product Eligibility & Modified Web Channel Order Management
Compatibility Driver Workflow
NOTE: Make sure that the new projects are imported and that the new SRF is applied to the
server prior to importing and activating the workflows.
13 Navigate to Administration - Business Process > Workflow Deployment and activate the
workflows listed in the following table in the order in which they are shown:
Sequence Workflow
NOTE: The status of each workflow changes from In Progress to Complete after the workflow is
published.
14 After activating the workflows, reload the runtime events by navigating to Administration -
Runtime Events, and selecting Reload Runtime Events from the applet-level menu.
1 Create an ODBC entry for the database where you plan to import the seed data:
a Navigate to Start > Setting > Control Panel > Administrative Tools > Data Sources (ODBC),
navigate to the System DSN tab, and click Add.
b Select the "Siebel Oracle90" driver (from Datadirect Technologies).
c Enter a data source name (such as DevelopmentDB).
❏ For Oracle, enter the TNS service name that you created to connect Siebel Tools to the
database.
2 Navigate to the directory where you installed Siebel Tools and change the directory to either
REPPATCH\VACR502 if you are an SIA customer or to REPPATCH\HACR502 if you are an SEA
customer.
NOTE: Before you perform the following step, make sure that the dataimp.exe file exists in the
<Tools Install Directory>/bin directory.
<ODBC Source Name> - Replace with the ODBC name created in Step 1.
<Database Platform> - Replace with the database platform (ORACLE, DB2UDB or MSSQL).
4 Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
5 Depending upon the language that you are installing, complete either Step 6 or Step 7.
<ODBC Source Name> - Replace with the ODBC name created in Step 1.
<Database Platform> - Replace with the database platform (ORACLE, DB2UDB or MSSQL).
a Run the following command after importing VACR502_Seed.dat file to import the locale-specific
VACR502_Seed_Locale_XXX.dat, where XXX is the language code.
<ODBC Source Name> - Replace with the ODBC name created in Step 1.
2 In the Options tab, under Languages, select a source language and a target language.
3 Click the Import tab, and enter the following directory path: ACR502\LMU\XXX\lmu\lmu_crm.slf,
where XXX is the language code.
5 Navigate to Symbolic Strings > Symbolic String Locale, and query for the SBL_CFG_ENGINE_ON
symbolic string to verify that the data was created correctly.
PrepareEnableEngine
1 Navigate to Administration - Order Management > Signals.
2 In the Signals list view, confirm that the PrepareEnableEngine signal was created.
3 In the Versions list view, click on the latest version of the signal to drill down to the Actions list
view.
ReEnableiLogForQuickEdit
1 Navigate to Administration - Order Management > Signals.
2 In the Signals list view, confirm that the ReEnableiLogForQuickEdit signal was created.
3 In the Versions list view, click on the latest version of the signal to drill down to the Actions list
view.
UpdateUIForQuickEdit
1 Navigate to Administration - Order Management > Signals.
2 In the Signals list view, confirm that the UpdateUIForQuick Edit signal was created.
3 In the Versions list view, click on the latest version of the signal to drill down to the Actions list
view.
PrepareDisableEngine
1 Navigate to Administration - Order Management > Signals.
2 In the Signals list view, confirm that the PrepareDisableEngine signal was created.
3 In the Versions list view, click on the latest version of the signal to drill down to the Actions list
view.
2 Query to find the "Product Eligibility Variable Map - Context" variable map.
NOTE: The Path, Mode and Source Type fields are shown in the Variable Sources view.
NOTE: The Path, Mode and Source Type fields are shown in the Variable Sources view.
2 Query to find the variable map "Product Eligibility Variable Map - Context".
NOTE: The Path, Mode and Source Type fields are shown in the Variable Sources view.
NOTE: The Path, Mode and Source Type fields are shown in the Variable Sources view.
List of Values
1 In the Siebel application, navigate to Administration - Data > LOV Explorer and verify that the
following LOV types have been created:
LOV_TYPE CFG_QUICKEDIT_BTN_TYPE Y
2 In the Siebel application, navigate to Administration - Data > List Of Values, and verify that the
following values have been created:
NOTE: The values are for ENU only and the Display Value and the Language Independent Code
value is the same. The Language Name is English-American for all the LOV values.
Server Parameter
1 Navigate to the Administration - Server Configuration screen > Servers and Parameters view.
NOTE: If you want to enable Pre Pick Compatibility, enter True in the Value field for this
parameter. The Value on Restart field also changes to True.
2 If the OrderManagement section already exists, add the following line to that section:
EnablePrePickCompatibility = TRUE
3 If the OrderManagement section does not already exist, add both the section header and the line
to the .cfg file, as follows:
[OrderManagement]
EnablePrePickCompatibility = TRUE
2 Locate the "eCfgTopLevelButtonsJS.swt" web template file for the UI control and open it using a
text editor (such as Notepad).
<td nowrap>
</td>
<tr>
<td nowrap>
</td>
<td nowrap>
InvokeMethod="CalculatePriceCX"/>
</td>
<td nowrap>
</td>
…..
</table>
4 Within Internet Explorer, navigate to Tools > Internet Options > General tab, delete all of the
temporary files and log into the Siebel application.
If you want to enable Pre Pick Compatibility inside Siebel Product Configurator, you must modify the
web template to include the parameter ForceRefresh = Y.
2 Locate the "eCfgControlComboAddPriceJS.swt" web template file for the UI control and open it
using a text editor (such as Notepad).
NOTE: The web templates for controls all begin with eCfgControl.
3 Within the file, search for the <swe: control> tag and edit it to ForceRefresh="Y".
<swe:include file="eCfgPort_HeaderJS.swt"/>
<tr>
<tr>
<td>
<script>
</script>
CfgJSShow="showSelectAndOptions" CfgJSUpdateExclusion="updateExcludedItemForPort"
CfgJSUpdateSelection="updatePortItemsForComboAdd"/>
</swe:for-each>
</td>
</tr>
<tr>
<td colspan="3">
<swe:include file="eCfgRelationContentsPriceQuantityJS.swt"/>
</td>
</tr>
</table>
</td>
</tr>
<swe:include file="eCfgPort_FooterJS.swt"/>
4 Within Internet Explorer, navigate to Tools > Internet Options > General tab, delete all of the
temporary files and log into the Siebel application.
NOTE: If you have installed ACR 474 and ACR 508 together, using the instructions provided in
“Instructions for ACR 474 and ACR 508” on page 159, do not perform the procedures in this section.
After you have unzipped the ACR508.zip file, the ACR508 folder will have the following
subfolders:
❏ \DMGSchemaChanges (For more information, see “Applying ACR 508 Schema Changes to
the Database” on page 356.)
❏ \SeedData (For more information, see “Importing Seed Data for ACR 508” on page 357.)
❏ \SIFFiles
❏ \WFs
❏ \LMU
■ S_ORDER
■ S_ORDER_ITEM
■ S_ORDER_ITEM_OM
■ S_ORDPART_MVMT
■ EIM_ORDER1
■ EIM_ORDER_ITEM
■ EIM_ORDER_ITEM1
■ EIM_PART_MVMT
■ Table FieldService
■ Table NetworkOrderManagement
■ Table Order
■ EIM Order
■ EIM FieldService
2 Use the Siebel Tools - Import from Archive function to read the ACR508_VACR508_BaseTables.sif
and ACR508_VACR508_EIMTables.sif files and create the tables in the repository. Use the merge
option while importing this file.
NOTE: You must import the files in the specified order. The ACR508_VACR508_BaseTables.sif file
must be imported before the ACR508_VACR508_EIMTables.sif file.
3 Within Siebel Tools, query for the list of tables that were imported into the repository, and click
the Apply/DDL button to apply the changes to the database.
a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC).
c Click Add.
2 Navigate to the directory where you installed Siebel Tools and change this directory to
REPPATCH\ACR508.
NOTE: Before executing the next step, make sure that the dataimp.exe file exists in the <Tools
Install Directory>/bin directory.
<Tools Install Directory> - Replace this with the location in which you installed Siebel Tools.
<ODBC Source Name> - Replace this with the ODBC name that you created in Step 1 of this
procedure.
<Database Platform> - Replace with this with your database platform (ORACLE, DB2UDB or
MSSQL).
4 Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the
import completed successfully.
5 Depending on the language that you are installing, use one of the following steps.
■ For ENU, run the following command after importing the ACR508_Seed.dat file.
<Tools Install Directory> - Replace this with the location in which you installed Siebel Tools.
<ODBC Source Name> - Replace this with the ODBC name that you created in Step 1 of this
procedure.
<Database Platform> - Replace this with your database platform (ORACLE, DB2UDB or
MSSQL).
■ For customers using languages other than ENU, run the following command after importing
ACR508_Seed.dat file to import the locale-specific ACR508_Seed_Locale_XXX.dat file, where
XXX is the language code.
<Tools Install Directory> - Replace this with the location in which you installed Siebel Tools.
<ODBC Source Name> - Replace this with the ODBC name that you created in Step 1 of this
procedure.
NOTE: Step 6 applies to both customers who are using ENU and customers who are using
languages other than ENU.
6 Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
NOTE: The default setting for the SymStrPrefix entry X_, but, as noted above, this value must
be changed to SBL.
[Siebel]
……..
SymStrPrefix = SBL_
……..
2 Import the Web Service Integration.sif file from the SIFFiles folder into Siebel Tools using the
Tools > Import from Archive option. Use the Merge option in Import Wizard.
3 Verify that the Project "Web Service Integration" project has been created.
4 In Siebel Tools, lock all the following projects:
❏ Order Entry
❏ Symbolic Strings
❏ Product Selection UI
5 Import the rest of the SIF files from the SIFFiles folder into Siebel Tools using the Tools > Import
from Archive function.
If you have not locked the required projects, you may receive a warning error message.
■ ModifiedApplets.sif
■ ModifiedBCs.sif
■ ModifiedBOs.sif
■ ModifiedBS.sif
■ ModifiedIO.sif
■ ModifiedLinks.sif
■ ModifiedPicklists.sif
■ ModifiedScreens.sif
■ ModifiedSymbStrings.sif
■ ModifiedView.sif
NOTE: The following step only applies for customers who are installing languages other than ENU.
a Select > Tools > Utilities > ' Locale Management to import LMU files for your specific language
into Siebel Tools.
b Select Source Language = English American
d Click on Import Tab > Browse to locate the LMU file you want to import and click Import.
9 Use the Compile Projects > All Projects option to compile the projects, and save the srf file to
the <Siebel Server Install folder>\objects\ENU\siebel_sia.srf folder on the installed Siebel
server.
b Right-click on the right-side pane called Workflow Processes and import the .xml file into Siebel
Tools from the workflows folder. Refer to the preceding table for information about which projects
these workflows need to be imported into.
c Check the status of the workflow process. If it is In-Progress, then deploy the workflow process
to change its status to complete. Do not click the Deploy + Activate button, as doing so will yield
an error message. Only click the Deploy button.
NOTE: You may receive the "This is an invalid Workflow…" error message while deploying the
modified workflows from the list. Just ignore the error and click Yes.
d Repeat Step b through Step c of this procedure for of all the workflows in the folder.
e Log in to the Siebel application as an administrator, and navigate to the Site Map.
12 Activate the O2C Cancel Order Validation and SWI Revise Order Validation rule sets:
a Navigate to Site Map > Administration - Data Validation > Rule Sets.
b Query for the Cancel Order Validation and SWI Revise Order Validation rule sets.
13 Navigate to Site Map > Administration - Application > Data Map Administration.
14 Query for the ReviseOrder data map object, the Header data map component, and the Back
Office Process Status data map field.
15 Check the Inactive check box to inactivate the Back Office Process Status data map field.
16 Restart the Siebel Server.
17 Launch the Siebel Communications application.
Preinstallation Tasks
■ Before you begin your installation, change a parameter in tools.cfg file within Siebel Tools
(Original: SymStrPrefix = X_) to SymStrPrefix = SBL_
Repository Configurations
1 Get $ReleaseRoot\release\redist\repatch\ACR539.zip and unzip to any location accessible by
Siebel Tools.
■ LS Clinical Protocol
■ LS Clinical Subject
■ LS Clinical Activity
■ Symbolic Strings
■ LS Clinical Investigators
■ Table Activity
■ Table Clinical
■ LS Clinical Enhancement
■ Table LifeScience
■ Table Sales
■ LS Clinical Workflow
■ LS Clinical Rollup
■ EIM Clinical
■ EIM Common
NOTE: The following steps can be followed to automate the process of importing all the sif files
at once into the Siebel repository else the section from Schema Changes steps can be followed
to perform manual configuration changes into the siebel repository.
8 Import the Workflow Processes into Siebel Repository. See "Importing Workflow Definitions" for
more information.
Schema Changes
Use the instructions below to apply the schema changes.
■ S_CL_PTCL_LS
■ S_EVT_ACT_LSX
■ S_PTCL_SITE_LS
■ S_TMPL_PLANITEM
■ EIM_TMPL_PLNITM
■ EIM_PTL_SITE_LS
■ EIM_CL_PTCL_LS
■ EIM_CL_ACT_LS
■ Table Clinical
■ Table LifeScience
■ Table Sales
■ EIM Clinical
■ EIM Common
2 Use the Import from Archive function within Siebel Tools to read the Tables.sif file and create the
tables in the repository. The "merge" option should be used while importing this file.
3 Use Siebel Tools to query for the list of tables that were imported into the repository.
4 Use the Apply/DDL button to apply the changes to the physical database.
1 Clinical Protocol
Update the existing Business Component "Clinical Protocol" Business Component by adding new
fields as shown below:
Table S_CL_PTCL_LS
Single
Value
Fields
Name Value
Field Read Only Field: Synchronize Active Sites Flag Is CDMS null
Table S_ PTCL_SITE_LS
JOINS
Join Specification
Name Value
Field Read Only Field: Activate Synchronization Flag Require Active Flag Check
New/
Modified Calculated Pre
? Name Join Column Type Value PickList Default
■ For the Address Line 1 field, add the following record in the Pickmap:
Table S_EVT_ACT
New/ Text
Modify Name Join Column Type Length
Project LS Clinical
Subject
Table S_EVT_ACT
New/ Text
Modified Name Join Column Type Length
Table S_TMPL_PLANITEM
6 Visit Plan
Update the existing Visit Plan Business Component by adding new fields as shown below:
Table S_EVT_ACT
New/ Text
Modify Name Join Column Type Length
Table S_EVT_ACT
New/ Text
Modified Name Join Column Type Length
Table S_PTL_ST_CON_LS
9 Clinical Subject
Update the existing Clinical Subject Business Component by adding new fields as shown below:
Table S_CL_SUBJ_LS
For the ProtocolSiteId field, add the following record in the pickmap:
NOTE: The "Integration Objects", "Workflow Policy Columns" and "Workflow Policy Objects"
contained in the SIF file are all new. These should be imported to apply the changes.
Applets
■ Clinical Protocol Admin Form Applet
Update the existing applet as shown below. Also need to add the new controls to the Applet Web
Template.
HTML
New/ Icon
Modified Name String Reference Caption Field Map HTML Type
■ In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout.
HTML
New/ String Icon
Modified Name Reference Caption Field Map HTML Type
HTML
New/ String Icon
Modified Name Reference Caption Field Map HTML Type
In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout.
New/ String
Modified Name Reference Caption Field PickList HTML Type
In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout.
List Columns
List Columns
Clinical Item Clinical Item List Item In Edit Web Layout, drag and drop this
List Column from Controls/Columns
onto the layout
Import the "Clinical Protocol Site Primary Addresses Pick Applet.sif" to apply the changes.
NOTE: These symbolic strings will be imported as part of the SIF file import. This list is provided for
reference only.
New/ Current
Existing Name StringValue Definition
NOTE: Siebel Tools has to connect to the same database as the Siebel application server.
3 From the list applet, right-click and choose choose Import Workflow Process.
New/
Modified Xml File to Import Workflow Name Project
5 After import, query for the workflow, and in Lock Projects view > Workflow process, focus on the
record and click the Publish/Activate button on top of the applet to deploy the workflows.
NOTE: If you receive the "The value entered in field Process Business Object of buscomp
Workflow Process Deployment does not match any value in the bounded picklist FOW SRF
Business Object" error message while you are deploying the workflow, ignore the error message.
3 Go to Edit mode.
6 Change the property name of the Input Argument VisitTemplateDate field as detailed below:
From:
VisitTemplateDateFieldName OriginalTemplateDateFieldName
To:
VisitTemplateDateFieldName VisitTemplateDateFieldName
5 On the Service Port applet, update the address to point to your Web server location. By default,
it looks like:
http://<webserver>/eai_<lang>/
start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&Username=<username>&Password=<p
assword>
3 On the Repository Workflow Processes applet, query for workflows listed in the following table,
focus on each record and click the Activate button to activate the workflow.
Workflow Name
LS ClinicalProtocolSite Outbound-UpdatedSite
NOTE: If you encounter the "The value entered in field Process Business Object of buscomp Workflow
Process Deployment does not match any value in the bounded picklist FOW SRF Business Object"
error message when you are deploying the workfklow, ignore this error message.
Seed Data
Use the following procedure to import the seed data for ACR 539.
a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC).
❏ For Oracle, enter the TNS service name that you created to connect Siebel Tools to the
database.
2 Navigate to the directory in which you installed Siebel Tools and change the directory to
REPATCH\ACR539.
NOTE: Before you execute the next step, make sure that the dataimp.exe file exists in the <Tools
Install Directory>/bin directory.
<Tools Install Directory> - Replace with your Siebel Tools install directory
<ODBC Source Name> - Replace with the ODBC name created in the previous procedure.
<Database Platform> - Replace with your database platform information (ORACLE, DB2UDB or
MSSQL)
4 Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the
import completed successfully.
5 Depending upon the language that you are installing, follow Step 6 or Step 7.
<Tools Install Directory> - Replace with your Siebel Tools install directory
<ODBC Source Name> - Replace with the ODBC name created in Step 1 of the previous
procedure.
<Database Platform> - Replace with your database platform (ORACLE, DB2UDB or MSSQL)
b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
7 If you are installing languages other than ENU, perform the following steps:
a Run the following command after importing ACR539_Seed.dat file for importing the locale
specific ACR539_Seed_Locale_XXX.dat, where XXX is the language code.
<Tools Install Directory> - Replace with your Siebel Tools install directory.
<ODBC Source Name> - Replace with the ODBC name created in Step 1 of the previous
procedure.
b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
■ Generating Triggers
3 In the Component Groups list, click Menu and choose Enable Component Group.
5 Click Synchronize.
NOTE: After enabling Workflow Policies you may need to restart the server.
3 Modify the policies in the "Conditions List Applet" for the ([Condition Field] = "LS Clinical Site No
Subject Flag" or "LS Clinical Site No Subject Flag") the [Value] to the ENU equivalent (either Y
or N).
Generating Triggers
You must generate triggers before using any one of the modules requiring Workflow Policies, and
again whenever new policies are created or deleted. You do not need to regenerate triggers in order
to use additional modules requiring Workflow Policies.
The Generate Trigger (GenTrig) component on the Siebel Server allows you to create database
triggers. Policy Manager uses these database triggers to identify which records may match policy
conditions. You must regenerate triggers whenever new policies are created or deleted.
This creates a new line entry but does not start the task.
4 In the Job Parameters list, click New and complete the fields in the following order:
■ Name: Click the name field select button to query for and select the EXEC record.
6 In the Job Parameter list, click the name field select button to query for and select the Privilege
User password record ), and click OK. Enter the Table Owner In the Value field.
8 In the Job Parameter list, click the name field select button to query for and select the Privilege
User record, and click OK. Enter the Table Owner in the Value field.
9 In the Job Detail form applet, click Menu and choose Start Job.
10 In the Batch Jobs List view, click Menu and choose Run Query.
NOTE: You must use a command prompt to start Workflow Monitor Agent. You cannot start it from
the application.
3 In Application, Navigate to the Administration - Server Management screen > Tasks >
Parameters view.
4 In Server Task List Applet, Query in Component Field for 'Workflow Monitor Agent'.
5 In Server Task-Parameter List Applet, query in Parameter field for 'Action interval' , it will have
default value as 3600, i.e, 3600 seconds, 1 hr. Set it to lower value, even 5 is fine.
2 Extract oc4j-extended.zip to a folder in a machine where the siebel server is installed say D:\JMS
folder.
3 Copy Siebel.jar and SiebelJI_enu to D:\JMS folder, these jar files can be found in Siebel installed
directory.
4 Copy jndi.jar file to D:\JMS\j2ee\home\lib folder. This file can be found on the SOA server under
<SOA_HOME>/datadirect/sun/lib
6 Create a file with name 'jndi.properties' with following details in the path D:\JMS
■ java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory
■ java.naming.security.principal=anonymous
For example:
■ java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory
■ java.naming.provider.url=opmn:ormi://adc60120fems.us.oracle.com:6009:oc4j_soa
■ java.naming.security.principal=sadmin
7 Create a Named Subsystem in the Siebel application through the server management. Connect
to the server manager from command prompt from the bin directory of the Siebel installed folder
with the command.
b Run the following command to create the named subsystem and add the jar file into the class
path.
8 Login into the Siebel application, and navigate to Site Map > Administration Server Configuration
> Profile Configuration.
a Query for the profile with Alias Name 'JAVA' in the profile list and make sure the parameters are
correct.
10 On the SOA server, log into Entreprise Manager and create a user called sadmin that is part of
the users role. For information about how to create the users, see the Enterprise Manager
documentation.
11 Login to the Siebel application and navigate to Site Map > Administration - Business Service >
Simulator.
13 Change the Method Name to CheckJNDIContext with the following input arguments in the
home\lib folder.
a SendUsername = sadmin
c ConnectionFactory = java:comp/resource/UpdateClinicalStudySEBLRP/
QueueConnectionFactories/QCF
d SendQueue = java:comp/resource/UpdateClinicalStudySEBLRP/Queues/AIA_CLINICALSTUDYQ
16 Query for the workflow process: LS ClinicalProtocolSite Outbound - NewSite workflow process,
and do the following:
a Click Revise.
f Change SendPassword to the password created for the sadmin user on the SOA Server in
Enterprise Manager.
17 Perform Step a through Step h for the LS ClinicalProtocolSite Outbound - UpdatedSite workflow
process.
18 Log into the Siebel application and navigate to Administration - Business Processes.
19 Click on Workflow Deployment.
20 Query for the LS ClinicalProtocolSite Outbound - NewSite workflow and click the Activate button.
21 Query for the LS ClinicalProtocolSite Outbound - UpdatedSite workflow and click the Activate
button.
f Change SendPassword to the password created for the sadmin user on the SOA Server in
Enterprise Manager.
g Save the workflow process.
24 Perform Step a through Step h for the LS ClinicalProtocolSite Outbound - UpdatedSite workflow
process.
25 Log into the Siebel application and navigate to Administration - Business Processes.
26 Click on Workflow Deployment.
27 Query for workflow LS ClinicalProtocolSite Outbound - NewSite and click the Activate button.
28 Query for workflow LS ClinicalProtocolSite Outbound - UpdatedSite and click the Activate button.
For information about deploying and using SAI for Oracle Fusion Middleware and Siebel RESTful
Services, see Siebel Application Integration for Oracle Fusion Middleware Guide on the Siebel
Bookshelf at
http://www.oracle.com/technology/documentation/siebel.html
■ Siebel Tools
For installation instructions, see Siebel Installation Guide for the operating system you are using.
http://www.oracle.com/
NOTE: When installing this server, a basic WebLogic Server Domain is sufficient. Additionally,
make sure to choose Sun JDK when prompted; this is a requirement for Siebel RESTful Services.
For more information on installing the Oracle WebLogic Server, see Oracle Fusion Middleware
Installation Guide for Oracle WebLogic Server on Oracle Technology Network.
http://www.oracle.com/
For information about installing Oracle JDeveloper, see Installation Guide for Oracle JDeveloper
in the Oracle Fusion Middleware Documentation Library 11g Release 1.
■ Siebel Application Object Manager, for example, Call Center Object Manager (ENU)
2 On the computer where you installed Siebel Tools, locate the following ZIP files in the
SIEBEL_TOOLS_ROOT\REPPATCH directory:
■ ACR543.zip
■ ACR543_BaseIO_HOR.zip
■ ACR543_BaseIO_SIA.zip
3 Extract the archive files (.sif) from ACR543.zip. This ZIP file provides common archives for both
Siebel Industry Applications and Siebel Cross-Industry Applications.
4 Edit the Siebel Tools configuration file (tools.cfg) to allow for import of symbolic strings.
c Change the value of the SymStrPrefix parameter to SBL_, and then save the tools.cfg file.
NOTE: If projects and objects are not locked when you import SIF files, a message appears
indicating which object or project you must lock. In such a case, lock the project or object, and
then import the SIF file again.
7 Using the Import from Archive(s) menu item, import the following .sif archive files you previously
extracted into Siebel Tools:
■ 00Phoenix.sif
■ CSSEAIJCAService.sif
■ CSSIOCreationService.sif
■ DynamicIOCreationService.sif
■ EAI_Outbound_Siebel_Side_Changes.sif
■ EAISubsys.sif
■ InfraNameServer.sif
■ ServerMgr_ARN _ParameterRemoved.sif
■ ServerMgrSubsys.sif
8 Log out of Siebel Tools.
9 Extract the archive (.sif) files from the appropriate ZIP file to a folder.
■ ACR543_BaseIO_HOR.zip. This archive file provides base integration objects for Siebel
Industry Applications.
■ ACR543_BaseIO_SIA.zip. This archive file provides base integration objects for Siebel
Cross-Industry Applications.
10 Run the following command from the SIEBEL_TOOLS_ROOT\tools\bin directory to import the
preconfigured base integration objects:
NOTE: This process can take some time; wait until the process completes.
where:
■ /u is the username
■ /p is the password
■ “repository name” is the repository you want to use (the default is “Siebel Repository”)
■ directory_name is the directory to which you extracted the base integration objects in Step 9
■ import.log writes the data to a log file in the SIEBEL_TOOLS_ROOT\tools\bin directory
11 Compile the changes into an updated repository file (SRF), and then copy the new SRF file to the
Siebel Server installation directory, under SIEBSRVR_ROOT\objects\enu.
❏ Siebel_Enterprise_Server/enu/siebel.ini
❏ Siebel_Enterprise_Server/siebel.ini
File2 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletActivityGanttChart.swt
File3 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletAdvancedSearch.swt
File4 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletBottomStd.swt
File5 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletCalendarDaily.swt
File6 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletCalendarDailyPortal.swt
File7 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletCalendarMonthly.swt
File8 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletCalendarService.swt
File9 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletCalendarWeekly.swt
File10 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletChart.swt
File11 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletChartTOC.swt
File12 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletDashboard.swt
File13 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFind.swt
File14 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm1Col_B_E_N.swt
File15 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm1ColLight_B_E_N.swt
File16 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4Col_B.swt
File17 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4Col_E_N.swt
File18 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormPlain.swt
File19 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormSearchTop.swt
File20 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletGanttChart.swt
File21 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletHead.swt
File22 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletItemsDisplayed.swt
File23 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletLayoutControls.swt
File24 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletList_B_EL.swt
File25 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletList_E_N_Q.swt
File26 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListBasicHeaderless.swt
File27 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListInverted.swt
File28 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListMessage.swt
File29 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListPortal.swt
File30 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListPortalGraphical.swt
File31 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListPortalHeaderless.swt
File32 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListSearchResults.swt
File33 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListTitleless.swt
File34 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListTotals_B_EL.swt
File35 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSalutation.swt
File36 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSalutationGraphical.swt
File37 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletScreenLinks.swt
File38 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSearchAdvanced.swt
File39 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSearchBasic.swt
File40 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSearchFind.swt
File41 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSendEmailPick.swt
File42 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSendMail.swt
File43 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSpellCheck.swt
File44 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletTail.swt
File45 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletTree.swt
File46 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletTree2.swt
File47 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletTreeMarketing.swt
File48 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCBottomApplet.swt
File49 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCCalendarAppletTitleGraphical.swt
File50 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCCalendarMonthly_weekday.swt
File51 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCCalendarMonthly_weekend.swt
File52 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCChartBasic.swt
File53 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCError.swt
File54 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCForm1ColBody.swt
File55 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCForm1ColBodyLight.swt
File56 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCForm4ColBody.swt
File57 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormBaseTitle.swt
File58 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormBody.swt
File59 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormButtonsBottom.swt
File60 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormButtonsTop.swt
File61 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormEditTitle.swt
File62 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormSearch.swt
File63 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFrameBanner.swt
File64 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFrameViewbar.swt
File65 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCGanttAppletTitle.swt
File66 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCLayoutButtons.swt
File67 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCList4ColBody.swt
File68 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListBody.swt
File69 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListBodyBullet.swt
File70 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListBodyInverted.swt
File71 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListBodyNoRowHilite.swt
File72 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListBodyTotals.swt
File73 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListBodyTotalsNoRowHilite.swt
File74 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListButtonsTop.swt
File75 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListButtonsTopNoRecNav.swt
File76 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListHeader.swt
File77 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListHeaderNoSort.swt
File78 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListHeaderTotals.swt
File79 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListTitle.swt
File80 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListTitlePortal.swt
File81 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListTitlePortalGraphical.swt
File82 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPageContainer_NoFrames.swt
File83 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupButtonsBottom.swt
File84 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupForm.swt
File85 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupList.swt
File86 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupQuery.swt
File87 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCRuleEditInsertionList.swt
File88 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCRuleEditStatement.swt
File89 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCScreenbar_Tabs.swt
File90 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCScreenLinks.swt
File91 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSendSMS.swt
File92 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSiteMap.swt
File93 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSmartScriptPlayerApplet.swt
File94 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSubViewbar_Drop.swt
File95 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSubViewbar_Tabs.swt
File96 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCThreadbar.swt
File97 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTogglebar_drop.swt
File98 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTogglebar_drop2.swt
File99 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTogglebar_Tabs.swt
File100 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_1Over2Over1.swt
File101 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_25_50_25.swt
File102 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_25_75.swt
File103 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_25_75_Framed.swt
File104 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_25_75_Framed2.swt
File105 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_33_66.swt
File106 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_50_50.swt
File107 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_66_33.swt
File108 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_Search.swt
File109 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewAdmin1.swt
File110 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewbar_Tabs.swt
File111 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewbarAll_Tabs.swt
File112 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewBasic.swt
File113 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewCatalog.swt
File114 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail.swt
File115 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail2.swt
File116 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail2_ParentPntr.swt
File117 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail3.swt
File118 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail3MultiChild.swt
File119 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail_GrndchldIndnt.swt
File120 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail_ParentPntr.swt
File121 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetailMultiChild.swt
File122 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewTree.swt
File123 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewTree2.swt
File124 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletForm1Col.swt
File125 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletForm2Col.swt
File126 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletForm4ColMerged_B_E_N.swt
File127 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletFormBase1Col.swt
File128 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletFormBase2Col.swt
File129 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletFormBasic.swt
File130 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletFormItemDetail.swt
File131 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletLicenseBase1Col.swt
File132 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletLinks.swt
File133 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletLinks2.swt
File134 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletLinksBorder.swt
File135 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletLinksNoTitle.swt
File136 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListBriefBullet.swt
File137 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListBriefBulletBorder.swt
File138 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListBriefBulletShaded.swt
File139 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListBriefImgBullet.swt
File140 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListBriefImgBullet2.swt
File141 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListBriefImgBulletBorder.swt
File142 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListBriefImgBulletShaded.swt
File143 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListCategorizedBullet.swt
File144 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListCategorizedBulletTab.swt
File145 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListCategorizedTab.swt
File146 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListCategorizedTOC.swt
File147 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListDetailedImgBullet.swt
File148 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListDetailedImgBulletRecNav2.swt
File149 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListDetailedImgBulletRecNav.swt
File150 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListHorizontal.swt
File151 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListLight.swt
File152 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListMerged_B_EL.swt
File153 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListMessage.swt
File154 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListSearchResults.swt
File155 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListSubCategory_1PerRow.swt
File156 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListSubCategory_4PerColumn.swt
File157 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListSubCategory_6PerColumn.swt
File158 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListSubCategoryIndented.swt
File159 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListTabbed.swt
File160 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletPSearchHead.swt
File161 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletPSearchTail.swt
File162 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletSearchAdvanced.swt
File163 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletSearchBasic.swt
File164 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletSearchFind.swt
File165 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletSearchTop.swt
File166 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCForm1Col.swt
File167 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCForm2Col.swt
File168 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCForm4ColBody.swt
File169 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormButtonsBottom.swt
File170 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormButtonsTopWithTitle.swt
File171 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormItemDetail.swt
File172 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormSearch.swt
File173 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormTotals.swt
File174 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFrameBanner.swt
File175 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFrameScreenbar.swt
File176 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFrameViewbar.swt
File177 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFrameViewbar_Hybrid.swt
File178 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyBullet.swt
File179 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyHorizontal.swt
File180 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyImgBullet.swt
File181 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyImgBulletDetailed.swt
File182 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyImgBulletDetailed2.swt
File183 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListButtonsTopWithTitle.swt
File184 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListCategorized.swt
File185 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListHeader.swt
File186 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListTitle.swt
File187 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListTitleNoRule.swt
File188 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCPageContainer.swt
File189 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCPageContainer_NoFrames.swt
File190 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCScreenbar_Tabs.swt
File191 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCSubViewbar_Drop.swt
File192 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCSubViewbar_Tabs.swt
File193 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCTogglebar_Tabs.swt
File194 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_100_66_33_100.swt
File195 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_25_50_25.swt
File196 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_25_75.swt
File197 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_25_75_Framed.swt
File198 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_50_50.swt
File199 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_66_33.swt
File200 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_75_25.swt
File201 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_Basic.swt
File202 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCViewAdmin1.swt
File203 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCViewbar_Tabs.swt
File204 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCViewDetail.swt
File205 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCViewDetail2.swt
File206 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCViewDetailMultiChild.swt
File207 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAttributeComboBox.swt
File208 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAttributeList.swt
File209 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgBasketBox.swt
File210 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgClassNode.swt
File211 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCompAttributeEdit.swt
File212 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNav.swt
File213 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNav_UiPicker.swt
File214 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavAttributes.swt
File215 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavClasses.swt
File216 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavConnectedProducts.swt
File217 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavLinks.swt
File218 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavRelationships.swt
File219 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavResources.swt
File220 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgLinkedItem.swt
File221 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_Status_Conflict.swt
File222 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_Status_Error_Info.swt
File223 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgPort_Header.swt
File224 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgResource.swt
File225 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgSaveFavoritesPopup.swt
File226 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgTabBasket.swt
File227 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgView_Decorations.swt
File228 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCollabAckApplet.swt
File229 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCollabHiddenApplet.swt
File230 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespAppletInboundMsg.swt
File231 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespAppletOutboundMsg.swt
File232 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespFormButtonsBottom.swt
File233 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespFormInBound.swt
File234 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespFormOutBound.swt
File235 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalAppletEdit.swt
File236 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalAppletFormBasic.swt
File237 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalAppletListTinyHeaderless.swt
File238 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalAppletTitle.swt
File239 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalBriefingHeaderApplet.swt
File240 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalCalendarAppletTitle.swt
File241 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalCalendarDaily.swt
File242 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalCompanySearchFormApplet.swt
File243 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalDeptSectionsApplet.swt
File244 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalDeptView.swt
File245 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalEmbeddedContainerPage.swt
File246 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalError.swt
File247 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalFullListApplet.swt
File248 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalHomeView.swt
File249 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalLinkListApplet.swt
File250 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalLitListApplet.swt
File251 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalNavBarApplet.swt
File252 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalPageContainer.swt
File253 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalQuickPicksApplet.swt
File254 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalSearchApplet.swt
File255 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalSimpleListApplet.swt
File256 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalSplashApplet.swt
File257 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalTickerSearchFormApplet.swt
File258 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalTOCApplet.swt
File259 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalTopUrlApplet.swt
File260 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalURLApplet.swt
File261 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalWeatherSearchFormApplet.swt
File262 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eSalesAppletFormItemDetail.swt
File263 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eSalesConfigApplet10.swt
File264 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eSalesView_100_25_75_100.swt
File265 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eServiceNewButtonApplet.swt
File266 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eWirelessPageTabLayoutEdit.swt
File267 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ICAppletList.swt
File268 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ICAppletListCategorizedBulletTab.swt
File269 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ICCurrentCategoryApplet.swt
File270 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ICListCategorized.swt
File271 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SIAppletTitle.swt
File272 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SIBriefingHeaderApplet.swt
File273 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SIBriefingListApplet.swt
File274 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SIBriefingView.swt
File275 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SILinkListApplet.swt
File276 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SIMyBriefingView.swt
File277 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SIPlainApplet.swt
File278 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SISalutationApplet.swt
File279 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SISwoopTitle.swt
File280 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SISynchronizeApplet.swt
File281 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SITOCApplet.swt
File282 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SITrackingProfileHeaderApplet.swt
File283 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SITrackingProfileReviewView.swt
File284 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SIUrlApplet.swt
File285 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SWELogin.swt
File286 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ToolsForm.swt
File287 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ToolsList.swt
File288 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ToolsUnmapped.swt
File289 = $(SiebelRoot)\siebsrvr\WEBTEMPL\TrainingTestApplet.swt
File290 = $(SiebelRoot)\siebsrvr\WEBTEMPL\TrainingTestResultApplet.swt
File291 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCCalendarAppletTitle.swt
File292 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewSegmentDetail.swt
File293 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDashboard.swt
File294 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_GlobalSignal.swt
File295 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletGanttChartPortal.swt
File296 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCLayoutTitlePortal.swt
File297 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgBaseAutoReprice.swt
File298 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgBaseManualReprice.swt
File299 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgClassNodeNoPick.swt
File300 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlCheck.swt
File301 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlCheckPrice.swt
File302 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlCombo.swt
File303 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboAdd.swt
File304 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboAddPrice.swt
File305 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlQuantity.swt
File306 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlQuantityPrice.swt
File307 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlRadio.swt
File308 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlRadioPrice.swt
File309 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgGroupStandard.swt
File310 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgGroupSummary.swt
File311 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductRawMode.swt
File312 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductSingle.swt
File313 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductTabs.swt
File314 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductWizard.swt
File315 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewAdmin1_GrndchldIndnt.swt
File316 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail2_GrndchldIndnt.swt
File317 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail3_GrndchldIndnt.swt
File318 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail3_ParentPntr.swt
File319 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletSearchAdvancedTabbed.swt
File320 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyImgBullet2.swt
File321 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eAuctionAppletPlaceBid.swt
File322 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlAttributeText.swt
File323 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboPrice.swt
File324 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboPriceQuantity.swt
File325 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboQuantity.swt
File326 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgRelationContentsPriceQuantity.swt
File327 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgRelationContentsQuantity.swt
File328 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgRelationRawCombo.swt
File329 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgViewBasic.swt
File330 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormButtonsTopNoRecNav.swt
File331 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eWirelessPageTabLayt4ColBody.swt
File332 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCApplet_NamedSpacer.swt
File333 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCApplet_Spacer.swt
File334 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_25_50_25_home.swt
File335 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4Col_NoRecNav.swt
File336 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormWizard.swt
File337 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTitle.swt
File338 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTitle_Mapped.swt
File339 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTitle_Portal.swt
File340 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTitle_PortalGraphical.swt
File341 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormButtonsTop.swt
File342 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListButtonsTop.swt
File343 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCTitle_Mapped.swt
File344 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCTitle_Portal.swt
File345 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_DetailExplanation.swt
File346 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_GlobalDetailExpl.swt
File347 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgPopupFrameContainer.swt
File348 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAttributeRadio.swt
File349 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListCategorizedNoTab.swt
File350 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyNoRowHilite.swt
File351 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyTotalsNoRowHilite.swt
File352 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListHeaderTotals.swt
File353 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCTitle_RecNav.swt
File354 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMViewBasic.swt
File355 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletForm4Col_B_TglBar.swt
File356 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletList_B_EL_TglBar.swt
File357 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletList_E_N_Q_TglBar.swt
File358 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMFormButtonsTop_TglBar.swt
File359 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMListButtonsTop_TglBar.swt
File360 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMViewBasic_TglBar.swt
File361 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMViewTree.swt
File362 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewTree_33_66.swt
File363 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletRealtimeCart.swt
File364 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletSalutationGraphical.swt
File365 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCLogout.swt
File366 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAtt_Header.swt
File367 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalAppletLinks2.swt
File368 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortaldCCAppletFormBasic.swt
File369 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortaldCCForm1ColBodyLight.swt
File370 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMReport_Form.swt
File371 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMReport_ListForm.swt
File372 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMReport_ListTotal.swt
File373 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgTopLevelButtons.swt
File374 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMObjectiveListApplet.swt
File375 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMTreeForm.swt
File376 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListMerged_B_EL.swt
File377 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListButtonsTopWithTitle.swt
File378 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormQuestionnaire.swt
File379 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCScreenbar_Tabs_Hybrid.swt
File380 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalNavBarAppletDeptPage.swt
File381 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalQuickPicksAppletDeptPage.swt
File382 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_50_50_Over_100_Framed.swt
File383 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewFilterDetail.swt
File384 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewVertical_Framed.swt
File385 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgError.swt
File386 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgErrorPicker.swt
File387 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCCalendarView.swt
File388 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCCalendarViewTabs.swt
File389 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ermFrameViewbar.swt
File390 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4Col_E_N_NoTitle.swt
File391 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_25_50_25_Framed.swt
File392 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupListButtonsTop.swt
File393 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eDocumentsTemplateLayout.swt
File394 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4ColMerged_B_E_N.swt
File395 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormButtonsTopWithTitle.swt
File396 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletHiGanttChart.swt
File397 = $(SiebelRoot)\siebsrvr\WEBTEMPL\HIcalendar.swt
File398 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFilterForm4Col_E_N.swt
File399 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EventHIcalendar.swt
File400 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletListTotals_B_EL_TglBar.swt
File401 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListCategorized3.swt
File402 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListCategorizedBulletTab3.swt
File403 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormWithSteps.swt
File404 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMImageDescr.swt
File405 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CBPopupForm.swt
File406 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CBListButtonsHierarchy.swt
File407 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CBPopupListHierarchy.swt
File408 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormButtonsTopNoRecNav.swt
File409 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletGotoURL.swt
File410 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletListPortalToggle.swt
File411 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupListAddItems.swt
File412 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortal4Up.swt
File413 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail_TglBar.swt
File414 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCPRMFrameViewbar.swt
File415 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMTopStory.swt
File416 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMTopStoryLgImg.swt
File417 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuBaseAutoReprice.swt
File418 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuControlCheckPrice.swt
File419 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuControlQuantityPrice.swt
File420 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuGroupSummary.swt
File421 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuLinkedItem.swt
File422 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuObj_GlobalSignal.swt
File423 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuProductTheme.swt
File424 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuTopLevelButtons.swt
File425 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_Status_Error_Undo.swt
File426 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewHIC.swt
File427 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4Col_B_Expanded.swt
File428 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4Col_E_N_Expanded.swt
File429 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4Col_NoRecNav_Expanded.swt
File430 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCForm4ColBody_Expanded.swt
File431 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalURLAppletForm.swt
File432 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalURLAppletInner.swt
File433 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSISOMAppletForm4Col_NoRecNavLinks.swt
File434 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSISOMForm4ColBodyLinks.swt
File435 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSISOMViewDetail2_ParentPntr.swt
File436 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CBAppletForm4Col_E_N_Simple.swt
File437 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuAttributeRadio.swt
File438 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalURLAppletGraphical.swt
File439 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCCRAFrameViewbar.swt
File440 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCScreenbar_NSTabs.swt
File441 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupListMvg.swt
File442 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupListAssoc.swt
File443 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletTaskAssistantPlayer.swt
File444 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletPopupFormGridLayout.swt
File445 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormGridLayout.swt
File446 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupListMvgShuttleButtonsTop.swt
File447 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupListAssocShuttleButtonsTop.swt
File448 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_CCAppletTree.swt
File449 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewbarAll_Tabs_DropList.swt
File450 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewbar_Tabs_DropList.swt
File451 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductTabsJS.swt
File452 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgBaseAutoRepriceJS.swt
File453 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboAddJS.swt
File454 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgHiddenFrame.swt
File455 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgRelationContentsQuantityJS.swt
File456 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCompAttributeEditJS.swt
File457 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAtt_HeaderJS.swt
File458 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgTopLevelButtonsJS.swt
File459 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgPort_HeaderJS.swt
File460 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgGroupStandardJS.swt
File461 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgViewBasicJS.swt
File462 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_Status_ConflictJS.swt
File463 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAttributeComboBoxJS.swt
File464 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMEmpLocatorSearchFormApplet.swt
File465 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMBusinessCardFormBasic.swt
File466 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMViewResultsDetail.swt
File467 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuProductThemeJS.swt
File468 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuAttributeRadioJS.swt
File469 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuBaseAutoRepriceJS.swt
File470 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuControlQuantityPriceJS.swt
File471 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuObj_GlobalSignalJS.swt
File472 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuTopLevelButtonsJS.swt
File473 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletGanttChartActX.swt
File474 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboJS.swt
File475 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewChartList.swt
File476 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewParentListWithTabs.swt
File477 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewParentMultiChildWithTabs.swt
File478 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ermPortalViewbar.swt
File479 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ermPortalPageContainer.swt
File480 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ermEmbeddedFrameViewbar.swt
File481 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMIntegrationURLApplet.swt
File482 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCError.swt
File483 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgBaseManualRepriceJS.swt
File484 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboPriceJS.swt
File485 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboQuantityJS.swt
File486 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductRawModeJS.swt
File487 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletTaskMap.swt
File488 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCTitle.swt
File489 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgRelationContentsPriceQuantityJS.swt
File490 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboAddPriceJS.swt
File491 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_ExplanationJS.swt
File492 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgLinkedItemJS.swt
File493 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgResourceJS.swt
File494 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_GlobalSignalJS.swt
File495 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgGroupSummaryJS.swt
File496 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMListBodyTotals.swt
File497 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletListTotals_TglBar.swt
File498 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuGroupSummaryJS.swt
File499 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductSingleJS.swt
File500 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductWizardJS.swt
File501 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormGridWizard.swt
File502 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboPriceQuantityJS.swt
File503 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListImgBulletScreenHomepage.swt
File504 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm1ColScreenHomepage.swt
File505 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMGenericViewTree.swt
File506 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCESSPlayerApplet.swt
File507 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ermAdminFrameBanner.swt
File508 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalNavBarAppletDeptPage_LeftNav.swt
File509 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_15_60_25_home.swt
File510 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMCPRDAListApplet.swt
File511 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMCPRDAListHeader.swt
File512 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAttributeRadioJS.swt
File513 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletCalendarGanttChartTop.swt
File514 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletCalendarGC.swt
File515 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletList_B_EL_NavControl.swt
File516 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletPortalLinks.swt
File517 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormPortalGraphical.swt
File518 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewbar_Tabs_DropList_Always.swt
File519 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespAttachmentListButtons.swt
File520 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespAppletInboundAttachments.swt
File521 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletScreenHomepageBanner.swt
File522 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyImgBulletScreenHomepage.swt
File523 =
$(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListImgBulletScreenHomepageWithDiv.swt
File524 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCForm1ColScreenHomepage.swt
File525 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyImgBulletScreenHomepage2.swt
File526 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletGanttChartActX_Mktg.swt
File527 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletAppHomepageBanner.swt
File528 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuControlCheckPriceJS.swt
File529 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuLinkedItemJS.swt
File530 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ermAppletListTabbedHighlight.swt
File531 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ermListBodyHighlight.swt
File532 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ICAppletForm.swt
File533 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletPortalList.swt
File534 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm1ColScreenHomepageAdd.swt
File535 =
$(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm1ColScreenHomepageSearch.swt
File536 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletListNoRowHilite_B_EL.swt
File537 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListCalToDo.swt
File538 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eEventsEventMicrositeView.swt
File539 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletDashboard_3Row.swt
File540 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_50_50_1.swt
File541 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletLinksNoTitle1.swt
File542 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListDetailedImgBulletRecNav3.swt
File543 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListItemDetail.swt
File544 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyImgBulletDetailed3.swt
File545 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListItemDetail.swt
File546 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormButtonsBottom_ext.swt
File547 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormGridLayout_Extend.swt
File548 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletFormBasic_ext.swt
File549 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMKPIListApplet.swt
File550 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMMMProductView.swt
File551 = $(SiebelRoot)\siebsrvr\WEBTEMPL\TNTSHMHICalendar.swt
File552 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgGroupMessagesJS.swt
File553 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListImgDetailHC.swt
File554 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListImgDetailHCBody.swt
File555 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail_ShoppingCart.swt
File556 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_MessagesJS.swt
File557 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletParametricSearch.swt
File558 = $(SiebelRoot)\siebsrvr\WEBTEMPL\COMActiveXAppletForm.swt
File559 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormGridLayoutNoRecNav.swt
File560 =
$(SiebelRoot)\siebsrvr\WEBTEMPL\eCFGViewBasicJS_ViewDetail_ShoppingCart.swt
File561 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCQuickPrintPopupForm.swt
File562 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletPlaybarButtons.swt
File563 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletTaskPane.swt
File564 = $(SiebelRoot)\siebsrvr\WEBTEMPL\TUPopupWatchWindow.swt
File565 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCInboxTransfer.swt
File566 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboAddDomainPriceJS.swt
File567 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboAddPriceAttribGridJS.swt
File568 =
$(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgRelationContentsPriceQuantityAttribGridJS.swt
File569 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlCheckPriceMultiLevelJS.swt
File570 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTaskViewTitle.swt
File571 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletPlaybarTop.swt
File572 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletPlaybarBottom.swt
File573 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormGridLayout_withJS.swt
File574 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlAttributeTextJS.swt
File575 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ccappletlist_b_el-shuttlemvg.swt
File576 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ccappletlist_b_el-shuttleassoc.swt
File577 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SavedSearch.swt
File578 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SearchLookin.swt
File579 = $(SiebelRoot)\siebsrvr\WEBTEMPL\AdvancedSearch.swt
File580 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SearchPreference.swt
File581 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SearchResults.swt
File582 = $(SiebelRoot)\siebsrvr\WEBTEMPL\Search_ListHeader.swt
File583 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SearchResultsFooter.swt
File584 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SearchHeaderResults.swt
File585 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SaveSearchApplet.swt
File586 = $(SiebelRoot)\siebsrvr\WEBTEMPL\RefineCategoryApplet.swt
File587 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail_ParentPntr_TAQ.swt
File588 = $(SiebelRoot)\siebsrvr\WEBTEMPL\Search_View.swt
File589 = $(SiebelRoot)\siebsrvr\WEBTEMPL\Search_RefineCategoryApplet.swt
File590 = $(SiebelRoot)\siebsrvr\WEBTEMPL\Search_Popup.swt
File591 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgBaseAutoRepriceMultiSelectJS.swt
File592 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgTopLevelButtonsJS_Configurator.swt
File593 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCActionBar.swt
File594 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCActionPane.swt
File595 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletReplaceQuery.swt
File596 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SearchFindResults.swt
File597 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SearchFindHeaderResults.swt
File598 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\dCCmain.css
File599 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCHtmlType.swf
File600 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCHtmlType.swf
File601 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\clock.gif
File602 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\voice.gif
File603 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_accept_work_item_enabled.
gif
File604 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_call_enabled.gif
File605 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_consultative_conference_en
abled.gif
File606 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_consultative_transfer_enabl
ed.gif
File607 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_email_enabled.gif
File608 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_fax_enabled.gif
File609 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_hold_work_item_enabled.gif
File610 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_initiate_work_item_enabled.
gif
File611 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_login_enabled.gif
File612 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_logout_enabled.gif
File613 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_mute_transfer_enabled.gif
File614 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_notready_enabled.gif
File615 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_page_enabled.gif
File616 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_release_work_item_enabled
.gif
File617 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_retrieve_enabled.gif
File618 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_webcall_enabled.gif
File619 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_fwd_wrk_itm_1_d.gif
File620 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_res_wrk_itm_1_d.gif
File621 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_wireless_enabled.gif
File622 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicscontrols.htm
File623 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicscontrolscal.htm
File624 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicscontrolscurr.htm
File625 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicsdata.htm
File626 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicsdatatoc.htm
File627 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicskbshortcuts.htm
File628 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicsnav.htm
File629 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicsselectiondbs.htm
File630 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcalendar.htm
File631 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcharts.htm
File632 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomfindinginfo.htm
File633 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomgeneric.htm
File634 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomgenericcontactustoc.htm
File635 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomgenericfindinginfotoc.htm
File636=
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomgenericlogintoc.htm
File637=
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomgenericregistrationtoc.ht
m
File638=
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomgenericuserinterfacetoc.h
tm
File639= $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomloggingin.htm
File640= $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomregistration.htm
File641= $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomsearch.htm
File642=
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomupdatinguserprofile.htm
File643=
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomuserinterface.htm
File644 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomwwattachments.htm
File645 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcorrespondence.htm
File646 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcorrespondencetoc.htm
File647 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebfindinginfotoc.htm
File648 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebhomepage.htm
File649 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebhomepagetoc.htm
File650 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebindex.htm
File651 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebliterature.htm
File652 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebliteraturetoc.htm
File653 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\sieboptions.htm
File654 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\sieboptionstoc.htm
File655 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebquery.htm
File656 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebquerytoc.htm
File657 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebreports.htm
File658 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebsearch.htm
File659 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebsearchtoc.htm
File660 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebstarthelp.htm
File661 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebuserinterfacetoc.htm
File662 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebusingcalendartoc.htm
File663 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebwelcome.htm
File664 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebusingtaskbasedui.htm
File665 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebusingtaskbaseduitoc.htm
File666 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebaccessibility.htm
❏ Siebel_Enterprise_Server/enu/siebel.ini
❏ Siebel_Enterprise_Server/siebel.ini
File2 = $(SiebelRoot)\siebsrvr\WEBTEMPL\FINSFrameViewbar.swt
File3 = $(SiebelRoot)\siebsrvr\WEBTEMPL\FINSPageContainer.swt
File4 = $(SiebelRoot)\siebsrvr\WEBTEMPL\FINSDBLogin.swt
File5 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletDashboard.swt
File6 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFrameMsgbar.swt
File7 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespFormInBoundNew.swt
File8 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespFormOutBoundNew.swt
1 Import all sif files related to the Siebel application located in the VARC562.zip and HACR562.zip
folders in the Siebel Tools/REPPATCH folder.
2 Set the following accessibility parameters for their respective application component:
❏ HighInteractivity = FALSE
❏ ExtendedKeyboard = True (In the cfg file under the InfraUI section)
❏ ApplicationStyle = EmployeeFacing
❏ AccessibleEnhanced = TRUE
❏ DisableSITabIndex = TRUE
❏ EnableSIFocusTracking = TRUE
Use the following procedure to enable screen readers to read out the applet summary for an
application. This is a user property based on the respective XML for an application.
To allow screen readers to read out the applet summary for an application
1 Navigate to Object Explorer in Siebel Tools.
2 Navigate to View > Options, and click the Object Explorer tab.
3 Unselect Application Object, select it again to add all of the child objects to the Object Explorer,
and click OK.
4 Click Application, and query for the Application Names listed in the following table:
Enabling Screen Readers to Read MVGs and Pick Applets for Calendar, Calculator, and MVG
Use the following procedure to enable screen readers to read out the MVG and Pick Applet for
Calendar, Calculator, and MVG. After these changes have been made, screen readers will read out a
Calendar Pick Applet as shown in the following example: Start Date: 25/07/2007 Calendar Icon.
To enable screen readers to read out the MVG and Pick Applet for Calendar,
Calculator, and MVG (Symbolic Strings)
1 Navigate to Object Explorer in Siebel Tools.
2 Navigate to View > Options, and click the Object Explorer tab.
3 Select the Symbolic Strings Object and click OK to add the Symbolic Strings object to Object
Explorer.
4 Click on Symbolic Strings and query for 'Current String Value' as 'Input'.
e For SBL_EDIT_ICON_ALT_TXT, change 'Current String Value' from Select to 'Pick Applet'.
To enable screen readers to read out the MVG and Pick Applet for Calendar,
Calculator, and MVG (Bitmaps)
1 Navigate to Object Explorer in Siebel Tools.
4 Navigate to Bitmap (child object) and query for 'CALENDAR_ ICON' and CALCULATOR_ICON.
5 Change the 'Alt Text' value to 'Calendar' and 'Calculator' respectively, as shown in the following
table:
New / Bitmap Alt Text SIA SIF File HOR SIF File
Changed Category Bitmap Value Description Name Name
7 In HTML Control Icons query for ' EDIT_ICON' and change the Alt Value to 'Pick Applet', as shown
in the preceding table.
3 Select Symbolic Strings Object and click OK to add the Symbolic Strings object to Object
Explorer.
New/ Current
Changed Project Name String Value SIA SIF File Name HOR SIF File Name
New/ Current
Changed Project Name String Value SIA SIF File Name HOR SIF File Name
The following table lists some of the keyboard shortcuts available with ACR 422, and the procedures
in the section that follows describe how to add these keyboard shortcuts.
Key
Command Action Accelerator Sequence Description SIA SIF File Name
2 Navigate to View > Options, and click the Object Explorer tab.
3 Select the 'Command' object and click OK to add the Command Strings object to Object Explorer.
4 Click the Command object on Object Explorer and query for the 'NextApplet' command.
7 In 'Display Name - String Reference', provide the newly created Symbolic String or in 'Display
Name' provide 'Ctrl + Alt + ]'.
4 In the Display Name - String Reference' field, enter the newly created Symbolic String or in the
Display Name field, enter 'Ctrl + Alt + ['.
4 Copy the Record Name '2'. Name the New Record '3'.
4 Copy the Record Name '2'. Name the New Record '3'.
4 Copy the Record Name '2'. Name the New Record '3'
4 Copy the Record Name '1'. Name the New Record '2'
4 Copy the Record Name '2'. Name the New Record '3'.
4 Copy the Record Name '2'. Name the New Record '3'.
2 Navigate to Applet.
5 Make sure that the proper Symbolic String has been selected.
New /
Changed Applet Name Title Description SIA SIF File Name HOR SIF File Name
NOTE: The DefaultFocus user property can be applied for any form applet where the user requires
a default focus.
Changed Search lookin DefaultFocus SearchFor Added the user AppletSearchlo AppletSearchlookin_HOR.sif
property to set the okin_SIA.sif
default focus
3 Create a New Command named "View Info" with project "Command" as the project, using the
values detailed in the following table:
■ NAME="ViewInfo"
■ METHOD="ViewInfo"
■ TARGET="SI Plus"
■ DISPLAY_NAME_-_STRING_REFERENCE="SBL_DOES_NOT_MATTER-1004225828-03I"
View Info Command ViewInfo Ctrl + Alt + Z Ctrl + Alt A new shortcut CmdViewInf CmdViewInf
+Z key that o_SIA.sif o_HOR.sif
generates a
dialog box that
contains
ViewName, View
Summary and
Applet Names
Sub-View Tab SWE N/A Ctrl + Alt + V Ctrl +Alt N/A CmdSubVie CmdSubVie
(SWE SI) +V wTab_SIA.si wTab_HOR.s
f if
4 Add a new Accelerator to the Command for the required Key Combination with the following
values:
■ NAME="1"
■ BROWSER_PLATFORM="All"
■ DISPLAY_NAME_-_STRING_REFERENCE="SBL_DOES_NOT_MATTER-1004225828-03I"
■ INACTIVE="N"
■ KEY_SEQUENCE="Ctrl+Alt+Z"
NOTE: Although it is not mandatory, it is important that you enter “Does not matter” as the value
for the Display Name or Caption field.
7 Navigate to Menu, and create a new Menu Item (Hidden) under the menu used by your
application, using the following values:
■ Name="Hidden-View Info
■ Position=8.39
■ Command = "ViewInfo"
For more information about shortcuts, refer to other shortcuts such as NextApplet within Siebel
Tools.
Enabling Screen Readers to Read Out the Check Box “HTML Flag” as HTML
The following procedure allows screen readers to read out the check box “HTML Flag” as HTML. By
default, it reads as Public. To make this change, you can also import the
Applet_CommPackageResponse_SIA.sif file. For information about how to import .sif files, see
“Importing SIF Files” on page 61.
To enable screen readers to read out the check box "HTML Flag" as HTML
1 Open Siebel Tools, and navigate to applet "Comm Package Response Form Applet".
Resolving an Error Generated When Creating New Records Within the Leads Screen
Use the following procedure to resolve an error message that occurs when users are creating new
records under the Leads screen, so that users are not able to see any case records in the Pick Cases
MVG. To make this change, you can also import the PUBLeadListCaseMvgApplet.sif, PUBLeadsList.sif,
PUBLeadsListApplet.sif, and CaseMvg.sif files. For information about how to import .sif files, see
“Importing SIF Files” on page 61.
5 Navigate to the "PUB Leads List Applet" applet and lock it.
6 Click Edit to create a web template and add the necessary controls, along with SAVE and CANCEL
buttons.
2 Lock the eApp project, and add a web page item called AccessibilityButton in the Web Page:
DotCom Page Container eService (Framed).
3 Add another web page item called AccessibilityButton in the Web Page: CC Login Page (Login
Only).
The default tag text should be set to the applet header name. Add TITLE or LABEL for each table
entry (all HTML form elements). Row and column headers must be identified as required by OGHAG
TABLE-1 and TABLE-2. Adding a row title for each row in data table (Suggestion: this could be the
first displayed data column in the applet display. Ideally the customer can select which column can
be used as the index for the row title through configuration).
NOTE: The list applet row ids are not available out of the box. Users can add them if they want. The
first data column will be used as the default rowid when there is no row id provided in the "RowId"
applet user property. There are two options available to users to select different rowid.
Option 1: Users need to contact the administrator to define the "RowId" user property.
To do this, a new applet user property called "RowId" has to be added for the list applet. The "RowId"
value should be equal to one of the displayed column name. For example, in the Contact list applet,
if 'Last Name' has been selected as the row header, the user property value has to be set to "RowId
= Last Name". Here "Last Name" is the list column name.
Option 2: Users can select the column displayed window and select some other column as the first
column for the list applet. The newly-selected column will become the rowid. Lock the particular
applet that needs to be changed.
Providing a New Key Combination for the Next and Previous Record Commands
Use the following procedure to provide a new key combination for the Next and Previous Record
commands.
2 Navigate to View > Options, and click the Object Explorer tab.
3 Select the 'Command' object and click OK to add the Command Strings object to Object Explorer.
4 Within Object Explorer, click the Command object and query for 'Previous Record(SWE)'
Command.
9 Within Object Explorer, click the Command object and query for 'Next Record(SWE)' Command.
Current
New/ String
Changed Project Name Value HOR SIF File Name SIA SIF File Name
Command Project Accelerator Key Sequence SIA SIF File Name HOR SIF File Name
New/
Changed Project Name Current String Value HOR SIF File Name SIA SIF File Name
New/
Changed Project Value Description
New Symbolic Strings Accessibility Create a new Symbolic String for Accessibility
Project for the "Confirmation Message" User
Preference
New Symbolic Strings Confirmation Create a new string for the Control
Message
2 Navigate to Administration - Data > List Of Values Explorer, and add the new LOV types
mentioned in the following table:
Language
Display Independent
Type Value Translate Multilingual Code Order Language Name
3 After you have added these changes, navigate to Screen > System Administration > List Of
Values to view these changes in the repository.
New/ Business
Changed Name Project Component Static Type Field Type Value
The following changes have been made to the User Preferences Business Component.
The following table describes the new User Profile Confirmation Message Parameter Applet that has
been added to support ACR 422.
New/ Business
Changed Name Project Component Class Title
The following table describes the applet controls changes that have been implemented to support
ACR 422.
Name Caption Field HTML Type Method Invoked Runtime Field Type
The following table describes the view changes that have been added to support ACR 422.
Visibility Applet
New/Changed Name Project Business Object Type
The following table describes the User Profile screen changes that have been added to support ACR
422.
Visibility Applet
New/Changed Name View Type Type
2 Make sure that the Execute Query, WriteRecord, UndoQuery, UndoRecord, and Query Assistant
controls are present on the applet template.
NOTE: Edit template uses 'Applet List Edit (Edit/New/Query)' as the web template.
New/ Web
Changed Name Project Template SIF File
New PUB Disease Case PUB HLS Bio Terrorism Edit Disease_Case_SIA.sif
List Applet
Resolving an Error Where Commands Are Executed Before Users Click Enter
Users are encountering an issue where before they click Enter on a menu item in the Show dialog
box, the command is executed.
To resolve an error in which commands are executed before users click Enter in the
Show dialog box
1 Navigate to Object Explorer in Siebel Tools.
2 Navigate to View > Options, and click the Object Explorer tab.
3 Select the Symbolic Strings Object and click OK to add the Symbolic Strings object to Object
Explorer.
2 Navigate to View > Options, and click the Object Explorer tab.
3 Select the 'Command' object and click OK to add the Command Strings object to Object Explorer.
4 Within Object Explorer, click the Command object and query for the 'NextPage' command.
6 Within Object Explorer, click the '+' sign and choose 'Accelerator'.
7 For 'Browser Platform' - Extended, in 'Display Name - String Reference', provide the newly
created Symbolic String or in 'Display Name' provide 'SBL_ALT+CTRL+DOWN'.
8 In the 'Key Sequence' field, change the value to 'Alt+Ctrl+Y', as shown in the following table:
9 Within Object Explorer, click the Command object and query for the 'PreviousPage' command.
Resolving an Error Encountered While Creating a New Record in the Identities Form Applet
The information in the following section resolves an issue where users encounter a problem within
the Immigration contacts screen > Identities view when they try to create a new record under the
Identities form applet. To make this change, you can follow the procedure below, or you can import
the PublicSector_Controls.sif file. For information about how to import .sif files, see “Importing SIF
Files” on page 61.
To resolve this error message, change the HTML Type property of the DeleteRecord control from
MiniButton to MiniButtonEdit for the PUB Immigration Identity Form Applet, the PUB Lead Form
Applet, the HLS Group Form Applet, the Disease Form Applet, the FINS Application Entry Applet —
ACAPS, and the HLS Medication Form Applet. Use the following bulleted list information group for
each applet as a reference point.
■ Template: Edit
■ Template: Edit
■ Additions: WriteRecord (save) control. UndoRecord (cancel) does not need to be added as the
'DeleteRecord' control is already present on the template.
■ Applet: "HLS Group Form Applet", "Disease Form Applet" and "FINS Application Entry Applet -
ACAPS"
■ Template: Edit
■ Template: Edit
NOTE: For the HLS Group Form Applet, Disease Form Applet, and FINS Application Entry Applet,
access these applets from under the Application screen and not from the BCM Applications screen.
The necessary changes need to be made under the configuration context of Siebel Public Sector for
these applets, because they are also used by the FINS application.
Resolving an Issue Where Users Are Unable to Query for Evidence Parent Information
The following procedure resolves a problem where under Evidence screen> Evidence parent, users
are unable to query for User Parent, and they receive an error message. To make this change, you
can also import the PublicEvidencePickApplet_SIA.sif file. For information about how to import .sif
files, see “Importing SIF Files” on page 61.
Add 'Popup Query' template to the 'PUB Evidence Pick Applet' with appropriate controls
[ExecuteQuery and CancelQuery] placed on it.
2 Navigate to Tools > Import from Archive and select the related .sif file
3 Click OK, and follow the instructions in the wizard to implement the changes.
4 Stop the servers, compile the objects or projects into respective .sif file and then restart the
servers.
3 Click Yes when the dialog box displays and asks “This operation should only be performed while
connected to your local database. Would you like to continue anyway?”
5 Select the first option "Overwrite the object definition in the repository" in the Conflict resolution
section of the import wizard view.
6 Review the conflicting objects to see if the new or modified columns appear. The import log is
stored at Siebel\tools\temp\importlog.txt
2 For a single table, select the current row option in Tables (Apply Schema Window).
3 For more than one table, select the Choose Current Query option.
4 For the Accessibility project, select the S_ACC_VIEW_APPL table and current row option.
5 Make the following changes depending upon which database you are using:
a For MSSQL, enter the database users, the database user password, and the correct ODBC data
source.
b For Oracle, enter the table space, the index space, the database user, the database user
password, and the correct ODBC data source.
c For IBM DB2, enter the table space, the 16K table space, the 32K table space, the index space,
the database users, the database user password, and the correct ODBC data source.
6 After entering in the database information, click the Apply button.
7 Verify that the required changes have been applied by selecting count(*) from
S_ACC_VIEW_APPL.
For example:
4 Check the log files for any errors, and check S_ACC_VIEW_APPL for the data imported.
2 Import AccProject.sif. For a list of files that this .sif contains, see “Changes to SIF Files in ACR
422” on page 65.
The AdminScreen.sif file contains the modified System Administration Screen. For the list of
changes to this screen, see “Changes to SIF Files in ACR 422” on page 65.
Type Value
ACC_ATTRIB_TYPE Summary
ACC_ATTRIB_TYPE Label
ACC_LOCALE ENU
6 Run the perl script using the procedures detailed in Step a through Step c.
a Open a command line window and navigate to the folder where the three scripts reside
(genAccessibilityXML.pl, app_tree.pl, sqlstmt.pl).
b Execute the script with the following command:
❏ For all databases, change Oracle in DBI->Connect(“ “) in app_tree.pl and
genAccessibilityXML.pl to ODBC.
#Connect to DB
#################################################
#################################################
_________________________________________________________________________
____
c Once the script is run an xml file will be generated, copy this xml in the following location:
Siebel\ses\siebsrvr\bin\LANG_FOLDER\ folder.
The name of the XML File should be same as the value mentioned for the Application user
property 'AccessibilityXMLFileName' for that application.
NOTE: The preceding steps help the users provide the summary for a new or a customized
applet. A UI will be created in which the user has to enter the summary for a particular applet.
This in turn will be placed into the XML file that will be generated after the perl script is run. Users
can use this XML file to allow screen readers to read out the applet summary.
5 Edit the “Position on Row” control’s properties by entering “ROW_OFF” for HTML Bitmap and
“ROW_ON” for HTML Disabled Bitmap.
7 Drag and drop the GotoPreviousSet and GotoNextSet controls to their respective placeholders,
and edit the properties using the values in the following table:
10 Drag and drop the Save and Cancel buttons to their respective placeholders.
11 Save the applet.
AccProject.sif
The AccProject.sif file contains the following new objects:
Business Components:
Applets:
Business Objects:
Views:
Picklists:
Symbolic Strings:
■ Accessibility
■ Applet Attributes
■ Attribute Type
■ View Attributes
AdminScreen.sif
The AdminScreen.sif file contains the following changes:
The following sections describe how to configure ACR 476 and the EMR UI.
2 Install Siebel Server and Siebel Tools provided within the 8.1.1.x Fix Pack.
3 Verify that the following DLL files exist in the siebsrvr\bin folder:
❏ sscasasv.dll
❏ swcasvfr.dll
❏ swcashfr.dl
❏ swcanshfr.dll
❏ sscashsv.dll
4 Verify that the ACR 476.zip file exists in the Siebel Tools/REPPATCH directory.
6 Navigate to Administration - Data > List Of Values, click New, and add a record with the following
values:
❏ Type = SEARCH_SMART_ANSWER
Customers using languages other than ENU can change the language.
2 Select the language from the drop-down list and click OK.
NOTE: When you are compiling and whne you are replacing the SRF, make sure that the SRFs are
from language folders.
2 Launch Siebel Tools, and import all of the extracted .sif files in the following order:
❏ 01_sma_project.sif
❏ 02_sma_classes.sif
❏ 03_sma_dll.sif
❏ 04_sma_bussvc.sif
❏ 05_sma_io.sif
❏ 06_sma_ss.sif
❏ 07_sma_applets.sif
❏ 08_sma_sct.sif
❏ 09_sma_view.sif
❏ 10_emr_bussvc.sif
3 Upon successful import, within Siebel Tools, make sure the following projects are locked:
❏ Smart Answer
❏ Banter eService
❏ Service (SSV)
❏ Symbolic Strings
❏ eCatalog Admin
❏ eMail Response
5 Use the newly compiled repository (.srf) for launching the Siebel Server.
a Update the value for NLPAdapterDLLName with the correct location and filename.
c Make sure that you have the correct, accessible, and writable FileSystem location.
d Under the above FileSystem, create a new folder called "smartanswer", and create two new
directories called "import" and "export" under the smartanswer directory.
7 Place the third-party DLL in the NLPAdapterDLLName directory specified in the SAConfig.xml file.
2 Install Siebel Server and Siebel Tools from the 8.1.1.x Fix Pack.
3 Verify that the following DLL files exist in the siebsrver\bin directory:
❏ swcommfr.dll
❏ sscommsv.dll
❏ sscmclnt.dll
❏ sscacabc.dll
❏ swcacafr.dll
4 Verify that the EMRUI_New.zip file exists in the Siebel Tools/REPPATCH directory.
5 Navigate to Administration - Application > View > Communication Detail view to add seed data.
❏ Siebel Administrator
❏ Call Center Administrator
2 Launch Siebel Tools, and import all of the extracted .sif files in the following order:
❏ EMR_UI_Applets.sif
❏ EMR_UI_BC.sif
❏ EMR_UI_BO.sif
❏ EMR_UI_BS.sif
❏ EMR_UI_Class.sif
❏ EMR_UI_Screen.sif
❏ EMR_UI_View.sif
❏ EMR_UI_Webtemplate.sif
❏ EMR_UI_WF.sif
3 Upon successful import, within Siebel Tools, make sure the following projects are locked:
❏ Mail Agent
❏ eMail Response
5 Use the newly-compiled repository (.srf) for launching the Siebel Server.
■ Smart Answer Server is currently only available for Microsoft Windows 2003.
■ It is recommended that Smart Answer Server be run on a single standalone server with 4GB RAM
and at least a 3.4 GHz processor.
Additional Software
The following software is required:
■ Java Runtime Environment 1.6+. Obtain and install Java from http://java.com/en/download/
manual.jsp.
NOTE: Smart Answer is not yet compatible with Python version 3.0 and above
■ PyWin32: http://sourceforge.net/projects/pywin32/files/.
NOTE: This is required for running Smart Answer Server as a Windows service. It is highly
recommended, but optional.
■ Be sure to download the automated installer that matches your version of Python.
3 Verify that the following DLL files exist in the siebsrvr\bin directory:
❏ swcommfr.dll
❏ sscanshsv.dll
❏ sscasasv.dll
❏ sscashsv.dll
❏ swcanshfr.dll
6 Verify that the SAConfig.xml file exists within the siebsrvr/smartanswer directory.
2 Open the Tools.cfg file, and change the SymStrPrefix value from ‘x_’ to ‘SBL_’.
8 Compile the changed objects to the Siebel repository and then unlock the locked projects.
NOTE: If there have been any changes made to the Symbolic String project, after you have
imported the .sif files, navigate to Tools\BIN\<lang>, open tools.cfg, and change the
SymStrPrefix value from ‘SBL_’ to ‘x_’.
You use the Locale Management Utility to import translated strings and other locale-specific
attributes back into the repository. Use the preview functionality to display the results of the import
process before you actually import them into the repository.
NOTE: When using the LMU to import files with the.xlf extension, make sure that you are connected
to the Internet.
.xlf files are provided along with the ACR content in the build and mirror the \ENU location.
2 In the Options tab, under Languages, select a source language and a target language.
4 Enter the directory path and name of the file you are going to import.
5 Enter the path and name of the file where you want to store the results for previewing.
6 Click Preview.
The Locale Management Utility writes the results of the import process to the log file rather than
to the repository.
NOTE: LMU does not mark changed records with a Redo flag when running in Preview mode.
to
8 Review the preview.log for errors. If this file is empty, there were no errors, so proceed with the
import.
BlackBerry® operating system versions: 4.2, 4.3, 4.5, 4.6, 4.7, 5.0
Apple iPhone™ or iPod touch mobile digital devices operating system version
3.0 or higher
Subcategory: Other
MSA Setting Preference for Calendar Updates available on the MSA client is not supported for the
MSA integration with Siebel On premise for this release. Changing the option between "Changes
Only" and "Download All" has no impact on data downloading behavior.
Subcategory: Other
Adding an opportunity from MSA client when integrated with Siebel On premise is not supported for
this release. Editing an available opportunity in MSA client is supported.
Subcategory: Other
The Leads entity is not supported for MSA integrated with Siebel On Premise. The Leads icon on MSA
is not functional.
NOTE: Import all of the .sif files except the ones in the Web Services directory, as those files will
be imported separately.To import the symbolic strings, edit the tools.cfg file (located within the
\bin\enu directory) to change the prefix from "X_" to "SBL_", and change the prefix back to "X_"
once you have imported the symbolic strings.
2 In Siebel Tools, using Object Explorer, navigate to Project, and lock the following projects:
❏ Account
❏ Account (SSE)
❏ Contact
❏ Lstofval
❏ Oppty
❏ Division
❏ Activity
❏ Employee
3 In Siebel Tools, select Import from Archive, and within the Import from Archive dialog box, the
"Merge the object definition from the archive file with the definition in the repository" option, and
click Next.
4 Click Yes to grant permission to modify the repository, and then click Finish.
5 Stop the Siebel Server or make sure that it has been stopped.
6 Within Siebel Tools, select Locked Projects, and select the file "SIEBEL_HOME/siebsrvr/OBJECTS/
ENU/siebel_sia.srf" file.
9 Navigate to Site Map > Web Service Administration > Inbound Web Services, and import the
following files:
❏ "SWIAccountNoteServices.XML"
❏ "SWIAccountServices.XML"
❏ "SWIActionServices.XML"
❏ "SWIActivityServices.xml"
❏ "SWIAddressServices.xml"
❏ "SWIContactNoteServices.XML"
❏ "SWIContactNoteServices.XML"
❏ "SWIContactServices.XML"
❏ "SWIContactUIServices.XML"
❏ "SWICurrentUserServices.XML"
❏ "SWICustomerParty.XML"
❏ "SWIEmployeeServices.XML"
❏ "SWINoteServices.XML"
❏ "SWIOpportunityServices.XML"
❏ "SWIOpptyServices.XML"
❏ "SWIPickListHierarchicalServices.XML "
❏ "SWISalesMethodServices.XML"
10 Click Clear Cache after you have imported the XML files.
The ACR487_MSA_to_Siebel_Integration_Package.zip file also contains the BPEL/java files required
for Mobile Sales Assistant.
Copy this file to the SOASuite machine and extract the zip to a directory of your choice, and then
follow the steps detailed in Oracle Mobile Sales Assistant Guide to deploy the composites.
In Oracle Mobile Sales Assistant Guide, where it refers to the "bpel" directory, this is the directory
extracted from ACR487_MSA_to_Siebel_Integration_Package.zip
In order to receive the full benefit of all product enhancements contained in the Siebel Business
Applications releases covered by this document, and to maintain a fully supported Siebel Business
Applications installation, install each product component shown on the Bill of Materials by following
the Siebel Fix Pack 8.1.1.x installation instructions in this section. Install the Fix Pack for all
applicable products in your existing deployment.
NOTE: This Siebel Maintenance Release Guide includes information for the latest Siebel Fix Pack
8.1.1.x release. Each Fix Pack is cumulative and includes all fixes included in previous Siebel Fix Pack
8.1.1.x releases (where applicable). You can install the latest Siebel Fix Pack 8.1.1.x release on top
of version 8.1.1 or any prior version 8.1.1.x release.
Before installing this Fix Pack, it is strongly recommended to read all the information in the topics in
this section (“Siebel Fix Pack Installation Instructions” on page 441). See also “How to Use This Guide”
on page 10.
This document describes Fix Pack installation and related tasks for several key products, but not for
all Siebel Business Applications products that may apply to your deployment. Fix Pack installation
tasks for products not covered here are generally similar to those described here.
■ Performing new full installation of version 8.1.1, with Siebel Fix Pack 8.1.1.x. If you are
installing version 8.1.1 (a new full installation), follow the installation instructions in the Siebel
Installation Guide for the operating system you are using. Also follow the instructions in this
Siebel Maintenance Release Guide for installing the latest Siebel Fix Pack 8.1.1.x release on top
of version 8.1.1.
Optionally, you can install 8.1 and 8.1.1.x together by configuring slipstream patch installation
for server-based Siebel modules. For details, see “Configuring Slipstream Patch Installation” on
page 456.
For the most recent version of the Siebel Installation Guide for the operating system you are
using, see the latest version 8.1 Siebel Bookshelf.
For more information about installing Siebel Fix Pack 8.1.1.x, see “About Installing Siebel Fix
Packs” on page 445.
■ Installing Siebel Fix Pack 8.1.1.x (patching existing version 8.1.1 or prior version
8.1.1.x installation). If you have already installed version 8.1.1 as a new full installation, and
are now installing the latest Siebel Fix Pack 8.1.1.x on top of version 8.1.1 or a previous version
8.1.1.x release, follow the instructions in this Siebel Maintenance Release Guide for doing this.
Where applicable, you can optionally uninstall an existing installed Siebel Fix Pack 8.1.1.x release
before you install the latest Fix Pack. For more information, see “Uninstalling Siebel Fix Packs” on
page 460.
When you installed version 8.1.1 as a full installation, you would have already referred to the
Siebel Installation Guide for the operating system you are using. For the most recent version of
this document, see the latest version 8.1 Siebel Bookshelf.
For more information about installing Siebel Fix Pack 8.1.1.x, see “About Installing Siebel Fix
Packs” on page 445.
■ Adding languages. When you perform a new version 8.1.1 installation of Siebel Business
Applications, it is recommended to include any supported languages (language packs) you
require or expect to require. You can also add languages to an existing installation; some
additional steps are required in this case.
For more information, see “About Installing Additional Languages” on page 444.
In general, each Siebel Fix Pack can be installed on top of an existing Siebel installation of the same
product suite that is at a valid base version level for this Fix Pack.
Installing any Fix Pack requires an existing installation of a qualified base release to install into. Here,
base release means the current version of the existing installation, including version 8.1.1 software
and optionally including any installed Siebel Fix Pack 8.1.1.x or other patch releases.
Here are the base releases and Siebel Business Applications product suites for installing the latest
Siebel Fix Pack 8.1.1.x release:
Do not install a Fix Pack for one product suite on top of a base installation for another product suite.
Such combinations are incompatible.
Siebel Industry Applications are composed of multiple industry product groups (vertical
applications). For a detailed listing of the industry products contained in each group, see Siebel
System Requirements and Supported Platforms on Oracle Technology Network.
NOTE: In order to run Siebel Business Applications software, all components of a Siebel Enterprise
must be at the same exact version 8.1.1.x release level.
The Siebel Image Creator utility is used to create an installation image (sometimes called a network
image) for version 8.1.1 or any Siebel Fix Pack 8.1.1.x release. The image can include any Siebel
installable product and language provided as part of this product release.
You can also add products or languages to an existing installation image of the same version, for
products or languages that were not previously included.
Installing any Siebel Business Applications release, including a new installation of version 8.1.1, an
installation of a Siebel Fix Pack 8.1.1.x release, or the addition of one or more languages, must be
done from an installation image created using Image Creator.
NOTE: Always use the version of Siebel Image Creator provided with the Siebel release for which
you are creating the installation image.
Information about using Siebel Image Creator is provided in the Siebel Installation Guide for the
operating system you are using, on the version 8.1 Siebel Bookshelf.
Include or add all languages you will require in your Siebel version 8.1.1 installation image (network
image), which you create using the Siebel Image Creator utility. Then install the software with the
languages you require. When you configure each installed Siebel Server and Siebel Web Server
Extension, you also specify which installed languages you are deploying.
Optionally, you can add languages to an existing installation. Some postinstallation tasks are
required in order to deploy a language you added after initial product installation and configuration:
■ If you add a language after you have configured an installed Siebel Server, launch the Siebel
Server Configuration Wizard and run the configuration task Add Language Support for the Siebel
Server. (It is not necessary to reconfigure the Siebel Server.)
■ If you add a language after you have configured an installed Siebel Web Server Extension
(SWSE), launch the SWSE Configuration Wizard and run the configuration task Add Language
Support for the SWSE Configuration. (It is not necessary to reconfigure the SWSE.)
After adding a language to your installed software, you must add the language to the Siebel
Database, import Siebel Repository data into the database for this language, and run the MLOV
(multilingual LOV) conversion utility. It is recommended to perform database-related tasks after
installing applicable Fix Packs or other patch releases.
NOTE: If you are adding languages to an existing installation, do so before you install the latest
Siebel Fix Pack 8.1.1.x release. It is possible to add a language after a Fix Pack has been installed.
However, for each component for which you add a language, you must reinstall the Fix Pack to bring
the language pack files up to the current release level. (Because Fix Packs are cumulative, you can
install just the latest Siebel Fix Pack 8.1.1.x release, even if you previously installed a prior Fix Pack
before adding the language.)
If you are not adding languages, you only need to install the latest Siebel Fix Pack 8.1.1.x release,
as described in this guide.
For detailed information about installing and deploying Siebel languages, see also:
■ Siebel Installation Guide for the operating system you are using
See also “Postinstallation Task for Supporting Additional Languages” on page 459.
After installing version 8.1.1 and a Siebel Fix Pack 8.1.1.x release as described in this guide, you can
also install any applicable Siebel Quick Fix releases on top of version 8.1.1.x. When you install a
Quick Fix, installed languages may also be patched, depending on the content of the Quick Fix
release.
NOTE: Installing Quick Fixes may entail restrictions about which subsequent Fix Packs can be
installed.
For detailed information about a particular Quick Fix, see the documentation that is provided
separately with the Quick Fix.
“Quick Fixes Included in 8.1.1.x Fix Packs” on page 11 identifies fixes from previous Quick Fix releases
that are included in specific Siebel Fix Pack 8.1.1.x releases.
For each Siebel Business Applications product module, installing the latest Siebel Fix Pack 8.1.1.x
release on top of an existing base installation replaces existing executable files and provides new
files in addition to the base installation.
For supported base releases, see “Siebel Fix Pack Installation Overview” on page 441.
Installing a Fix Pack does not replace any customer-modified files (for example, application
configuration files like siebel.cfg) that govern program execution. When you install a Fix Pack, any
installed languages may also be patched, depending on the content of the Fix Pack.
NOTE: References in this guide to Siebel Fix Pack 8.1.1.x releases apply to the current Fix Pack
release. However, you must verify the availability, characteristics, and requirements of any future Fix
Pack releases, including Siebel Fix Pack 8.1.1.x releases. Installation tasks and requirements for all
future releases are subject to change, and will be covered by updated documentation.
If you plan to install any additional Siebel language packs, review “Siebel Fix Pack Installation
Overview” on page 441 (in particular, “About Installing Additional Languages” on page 444) before you
install any Fix Pack.
The Siebel Fix Pack must be installed from an installation image you create using the Siebel Image
Creator utility. This utility is described in version 8.1 of the Siebel Installation Guide for the operating
system you are using. For more information, see “About Running Siebel Image Creator” on page 444.
For more information about stopping and restarting Siebel components, which is a required part of
the Fix Pack installation process, see Siebel System Administration Guide. See also Siebel
Installation Guide for the operating system you are using. For more information, see also
“Postinstallation Task for the Web Server” on page 458.
After you install version 8.1.1 and version 8.1.1.x, you can also install any applicable Quick Fix
release on top of version 8.1.1.x. For more information, see “About Installing Siebel Quick Fix
Releases” on page 445.
For information about uninstallation and Fix Packs, see “Uninstalling Siebel Fix Packs” on page 460.
For instructions for installing Siebel Fix Pack 8.1.1.x for your operating system platform, see:
Procedures for installing Siebel Fix Pack 8.1.1.x for products on Microsoft Windows are detailed
below. Follow these instructions to install each product over the existing base installation for the
same product. Perform the steps that apply for the Fix Pack you are installing, in the general
sequence presented here.
Before you install the Fix Pack, review all applicable information in “Siebel Fix Pack Installation
Overview” on page 441 and “About Installing Siebel Fix Packs” on page 445.
Instructions generally assume that Fix Pack installers are launched in GUI mode. Alternatively, the
installers for server-based products can be launched in console or unattended mode. The Fix Pack
installation runs silently.
NOTE: If you installed version 8.1.1 Siebel software using the Siebel FastTrack Wizard, use the Fix
Pack installers for Siebel Enterprise Server and Siebel Web Server Extension to patch any installed
instances of these modules. The FastTrack Wizard is provided for small to medium businesses (SMB).
For more information, see Siebel Installation Guide for Microsoft Windows.
■ “Installing the Fix Pack for Siebel Enterprise Server on Windows” on page 447
■ “Installing the Fix Pack for Siebel Web Server Extension on Windows” on page 447
■ “Installing the Fix Pack for Siebel Management Agent and Siebel Management Server on Windows”
on page 448
■ “Installing the Fix Pack for Siebel Mobile Web Client, Siebel Tools, Siebel Sample Database, or Siebel
Client Sync on Windows” on page 449
Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any machine where a Siebel
Enterprise Server component is installed, including Siebel Server, Siebel Gateway Name Server, and
Database Configuration Utilities (formerly known as Siebel Database Server).
The Fix Pack installer for Siebel Enterprise Server also patches any instance of Siebel Management
Agent that was installed with a Siebel Server you are patching. See also “Installing the Fix Pack for
Siebel Management Agent and Siebel Management Server on Windows” on page 448.
2 If you are patching an instance of Siebel Management Agent that was previously installed with a
Siebel Server, also stop the service for the Management Agent.
3 In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For Siebel Enterprise Server, navigate to
Siebel_Image\Windows\Server\Siebel_Enterprise_Server, where:
■ Siebel_Image is the directory for your version-specific Siebel installation image, such as
D:\Siebel_Install_Image\8.1.1.x.
4 Double-click setup.exe to launch the Siebel Enterprise Server installer for version 8.1.1.x.
5 Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel
installations.
7 Repeat these steps on each machine with a Siebel Enterprise Server component installation to
be patched.
8 Restart all applicable Siebel Business Applications product components at the end of all Fix Pack
or other patch release installation for server-based products.
Installing the Fix Pack for Siebel Web Server Extension on Windows
This topic is part of “Installing the Siebel Fix Pack on Microsoft Windows” on page 446.
Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any machine where a Siebel
Web Server Extension (SWSE) component is installed.
NOTE: Before you install any Fix Pack release for SWSE, refer to Siebel System Requirements and
Supported Platforms on Oracle Technology Network to verify that the Web server version is correct
for the Siebel Business Applications release. If you need to update the Web server, do so before you
install the Fix Pack for SWSE.
2 In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For SWSE, navigate to
Siebel_Image\Windows\Server\Siebel_Web_Server_Extension, where:
■ Siebel_Image is the directory for your version-specific Siebel installation image, such as
D:\Siebel_Install_Image\8.1.1.x.
4 Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel
installations.
7 Restart the Web server at the end of all Fix Pack or other patch release installation for server-
based products.
For more information, see “Postinstallation Task for the Web Server” on page 458.
Installing the Fix Pack for Siebel Management Agent and Siebel
Management Server on Windows
This topic is part of “Installing the Siebel Fix Pack on Microsoft Windows” on page 446.
Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on machines where Siebel
Management Agent or Siebel Management Server are installed.
NOTE: Instructions for installing Siebel Management Agent assume that Management Agent was
installed separately. If your instances of Management Agent were installed as part of Siebel Server
installation, follow the instructions in “Installing the Fix Pack for Siebel Enterprise Server on Windows”
on page 447. See also the Siebel Installation Guide for the operating system you are using.
When you install a Fix Pack for an instance of Siebel Management Agent, the Siebel Management
Server will be unable to connect to it. It is not necessary to shut down the Management Server while
you install the Fix Pack for the Management Agents. After you install the Fix Pack for all instances of
Management Agent, shut down the Siebel Management Server, then install the Fix Pack for
Management Server. After you restart Management Server, it automatically reconnects to each
instance of Management Agent. Newly patched instances of Management Agent will not be
operational until Management Server has also been patched.
To install the Fix Pack for Siebel Management Agent (where Management Agent was
installed separately)
1 Stop the Siebel Management Agent service.
2 In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For Siebel Management Agent, navigate to
Siebel_Image\Windows\Server\Siebel_Management_Agent, where:
■ Siebel_Image is the directory for your version-specific Siebel installation image, such as
D:\Siebel_Install_Image\8.1.1.x.
3 Double-click setup.exe to launch the Siebel Management Agent installer for version 8.1.1.x.
4 Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel
installations.
7 Repeat these steps on each machine with a Siebel Management Agent installation to be patched
(where Management Agent was installed separately).
2 In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For Siebel Management Server, navigate to
Siebel_Image\Windows\Server\Siebel_Management_Server, where:
■ Siebel_Image is the directory for your version-specific Siebel installation image, such as
D:\Siebel_Install_Image\8.1.1.x.
3 Double-click setup.exe to launch the Siebel Management Server installer for version 8.1.1.x.
4 Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel
installations.
7 Repeat these steps on each machine with a Siebel Management Server installation to be patched.
(In most deployments, only one instance is installed.)
Installing the Fix Pack for Siebel Mobile Web Client, Siebel Tools,
Siebel Sample Database, or Siebel Client Sync on Windows
This topic is part of “Installing the Siebel Fix Pack on Microsoft Windows” on page 446.
Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on machines where Siebel Mobile
Web Client, Siebel Tools, Siebel Sample Database, or Siebel Client Sync are installed. (Most of the
information for Siebel Mobile Web Client also applies to Siebel Developer Web Client.)
NOTE: As of version 8.1.1, the installer programs for Siebel Mobile Web Client and Siebel Tools are
based on the Oracle Universal Installer (OUI) framework, and have many differences from installers
for previous releases. For a detailed summary of installer changes, see the Siebel Installation Guide
for the operating system you are using.
To install the Fix Pack for Siebel Mobile Web Client or Siebel Tools
1 Exit any Siebel software on the client machine where you are installing the Fix Pack.
NOTE: For a Siebel Mobile Web Client using the Siebel QuickStart feature, you must also exit the
QuickStart agent, if it is running. To do this, right-click the QuickStart icon in the system tray,
then choose Exit. For more information about using Siebel QuickStart with the Mobile Web Client,
see the Siebel Installation Guide for the operating system you are using.
2 In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located.
where:
■ Siebel_Image is the directory for your version-specific Siebel installation image, such as
D:\Siebel_Install_Image\8.1.1.x.
3 Double-click oui.exe to launch the Siebel client or Siebel Tools installer for version 8.1.1.x.
4 In the dialog box labeled Specify Home Details, select an instance of version 8.1.1 or version
8.1.1.x to patch, from the list of detected Siebel installations.
6 Repeat these steps on each machine with an applicable Siebel client or Siebel Tools installation
to be patched.
NOTE: The machine may require a restart at the end of the installation.
CAUTION: If you do not perform these steps, an error will occur when you try to install the Fix
Pack for the Sample Database, and installation will not complete.
The version number should reflect the actual version of the Siebel Fix Pack 8.1.1.x release
you are installing.
e Make a copy of the file for each installed language, named upgrade_lang.txt, such as
upgrade_enu.txt for U.S. English (ENU).
f Place each language-specific copy of the file in the folder SIEBEL_CLIENT_ROOT or
SIEBEL_TOOLS_ROOT.
NOTE: If you install a future Siebel Fix Pack 8.1.1.x release for the Mobile Web Client or Siebel
Tools, update all applicable upgrade.txt and upgrade_lang.txt files again to reflect the new
version number. Do this before you install the new Fix Pack for the Sample Database.
3 In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For Siebel Sample Database, navigate to
Siebel_Image\Windows\Client\Siebel_Sample Database, where:
■ Siebel_Image is the directory for your version-specific Siebel installation image, such as
D:\Siebel_Install_Image\8.1.1.x.
4 Double-click install.exe to launch the Siebel Sample Database client installer for version 8.1.1.x.
5 Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel
installations.
7 Repeat these steps on each machine with an applicable Siebel Sample Database installation to
be patched.
NOTE: The machine may require a restart at the end of the installation.
2 In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For Siebel Client Sync, navigate to
Siebel_Image\Windows\Client\Siebel_Client_Sync, where:
■ Siebel_Image is the directory for your version-specific Siebel installation image, such as
D:\Siebel_Install_Image\8.1.1.x.
3 Double-click install.exe to launch the Siebel Client Sync client installer for version 8.1.1.x.
4 Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel
installations.
6 Repeat these steps on each machine with an applicable Siebel Client Sync installation to be
patched.
NOTE: The machine may require a restart at the end of the installation.
Procedures for installing Siebel Fix Pack 8.1.1.x for products on supported UNIX and Linux platforms
are detailed below. Follow these instructions to install each product over the existing base installation
for the same product. Perform the steps that apply for the Fix Pack you are installing, in the general
sequence presented here.
Before you install the Fix Pack, review all applicable information in “Siebel Fix Pack Installation
Overview” on page 441 and “About Installing Siebel Fix Packs” on page 445.
Instructions generally assume that Fix Pack installers are launched in GUI mode. Alternatively, the
installers for server-based products can be launched in console or unattended mode. The Fix Pack
installation runs silently.
NOTE: Some Siebel Business Applications products can only be installed on Windows, such as Siebel
Management Server, Siebel Mobile Web Client, Siebel Tools, or Siebel Client Sync. For more
information, see “Installing the Siebel Fix Pack on Microsoft Windows” on page 446.
■ “Installing the Fix Pack for Siebel Enterprise Server on UNIX” on page 452
■ “Installing the Fix Pack for Siebel Web Server Extension on UNIX” on page 453
■ “Installing the Fix Pack for Siebel Management Agent on UNIX” on page 455
Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any machine where a Siebel
Enterprise Server component is installed, including Siebel Server, Siebel Gateway Name Server, and
Database Configuration Utilities (formerly known as Siebel Database Server).
The Fix Pack installer for Siebel Enterprise Server also patches any instance of Siebel Management
Agent that was installed with a Siebel Server you are patching. See also “Installing the Fix Pack for
Siebel Management Agent on UNIX” on page 455.
2 If you are patching an instance of Siebel Management Agent that was previously installed with a
Siebel Server, also stop the service for the Management Agent.
3 Unload libraries from the system cache by running the command reset_server all on each
applicable server machine. (See Siebel System Administration Guide for details on how to use
this command.)
4 Stop the Siebel Gateway Name Server by running the command stop_ns. (See Siebel System
Administration Guide for details on how to use this command.)
5 (AIX only) Verify that the login ID performing installation has permission to run slibclean by
asking the administrator to change the permission as follows:
/usr/sbin/slibclean
7 Open a new shell and navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For Siebel Enterprise Server, navigate to Siebel_Image/
UNIX_OS/Server/Siebel_Enterprise_Server, where:
■ Siebel_Image is the directory for your version-specific Siebel installation image, such as
/Siebel_Install_Image/8.1.1.x.
■ UNIX_OS is your UNIX operating system, such as AIX, HPUX (HP-UX), Linux, or Solaris.
8 (For GUI mode) Run setupUNIX_OS to launch the Siebel Enterprise Server installer in GUI mode
for version 8.1.1.x, where:
■ UNIX_OS is your UNIX operating system, such as aix (AIX), hp (HP-UX), linux (Linux), or sol
(Solaris).
9 (For console mode) Enter the following command to launch the Siebel Enterprise Server installer
in console mode for version 8.1.1.x:
where:
■ UNIX_OS is your UNIX operating system, such as aix (AIX), hp (HP-UX), linux (Linux), or sol
(Solaris).
10 Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel
installations.
13 Restart all applicable Siebel Business Applications product components at the end of all Fix Pack
or other patch release installation for server-based products.
Installing the Fix Pack for Siebel Web Server Extension on UNIX
This topic is part of “Installing the Siebel Fix Pack on UNIX” on page 452.
Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any machine where a Siebel
Web Server Extension (SWSE) component is installed.
NOTE: Before you install any Fix Pack for SWSE, refer to Siebel System Requirements and Supported
Platforms on Oracle Technology Network to verify that the Web server version is correct for the Siebel
Business Applications release. If you need to update the Web server, do so before you install the Fix
Pack for SWSE.
■ ompmnctl stopall - for Oracle HTTP Server (on supported Linux platforms)
■ stopapa – for other Apache-based Web servers (on AIX, HP-UX, or supported Linux platforms)
■ stop – for Sun Java System Web Server (on Sun Solaris)
3 (AIX only) Verify that the login ID performing installation has permission to run slibclean by
asking the administrator to change the permission as follows:
/usr/sbin/slibclean
5 Open a new shell and navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For SWSE, navigate to Siebel_Image/UNIX_OS/Server/
Siebel_Web_Server_Extension, where:
■ Siebel_Image is the directory for your version-specific Siebel installation image, such as
/Siebel_Install_Image/8.1.1.x.
■ UNIX_OS is your UNIX operating system, such as AIX, HPUX (HP-UX), Linux, or Solaris.
6 (For GUI mode) Run setupUNIX_OS to launch the SWSE installer in GUI mode for version 8.1.1.x,
where:
■ UNIX_OS is your UNIX operating system, such as aix (AIX), hp (HP-UX), linux (Linux), or sol
(Solaris).
7 (For console mode) Enter the following command to launch the SWSE installer in console mode
for version 8.1.1.x:
where:
■ UNIX_OS is your UNIX operating system, such as aix (AIX), hp (HP-UX), linux (Linux), or sol
(Solaris).
8 Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel
installations.
Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on machines where Siebel
Management Agent is installed.
NOTE: Instructions for installing Siebel Management Agent assume that Management Agent was
installed separately. If your instances of Management Agent were installed as part of Siebel Server
installation, follow the instructions in “Installing the Fix Pack for Siebel Enterprise Server on UNIX” on
page 452 instead. See also the Siebel Installation Guide for the operating system you are using.
For information about installing the Fix Pack for Siebel Management Server (which runs on Windows
only), see “Installing the Fix Pack for Siebel Management Agent and Siebel Management Server on
Windows” on page 448.
When you install a Fix Pack for an instance of Siebel Management Agent, the Siebel Management
Server will be unable to connect to it. It is not necessary to shut down the Management Server while
you install the Fix Pack for the Management Agents. After you install the Fix Pack for all instances of
Management Agent, shut down the Siebel Management Server, then install the Fix Pack for
Management Server. After you restart Management Server, it automatically reconnects to each
instance of Management Agent. Newly patched instances of Management Agent will not be
operational until Management Server has also been patched.
To install the Fix Pack for Siebel Management Agent (where Management Agent was
installed separately)
1 Stop the service for the Siebel Management Agent.
2 (AIX only) Verify that the login ID performing installation has permission to run slibclean by
asking the administrator to change the permission as follows:
/usr/sbin/slibclean
4 Open a new shell and navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For Siebel Management Agent, navigate to Siebel_Image/
UNIX_OS/Server/Siebel_Management_Agent, where:
■ Siebel_Image is the directory for your version-specific Siebel installation image, such as
/Siebel_Install_Image/8.1.1.x.
■ UNIX_OS is your UNIX operating system, such as AIX, HPUX (HP-UX), Linux, or Solaris.
5 (For GUI mode) Run setupUNIX_OS to launch the Siebel Management Agent installer in GUI
mode for version 8.1.1.x, where:
■ UNIX_OS is your UNIX operating system, such as aix (AIX), hp (HP-UX), linux (Linux), or sol
(Solaris).
Go to Step 7 on page 456.
6 (For console mode) Enter the following command to launch the Siebel Management Agent
installer in console mode for version 8.1.1.x:
where:
■ UNIX_OS is your UNIX operating system, such as aix (AIX), hp (HP-UX), linux (Linux), or sol
(Solaris).
7 Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel
installations.
10 Repeat these steps on each machine with a Siebel Management Agent installation to be patched
(where Management Agent was installed separately).
Slipstream patch installation is the ability to configure installer behavior so that an installer process
(for full installation or Fix Pack installation) automatically invokes one or more patch installations for
the same product. The main installation can be performed in applicable installer modes (GUI,
console, or unattended mode). The Fix Pack or other patch installation runs silently.
NOTE: As noted in the Siebel Installation Guide for the operating system you are using, slipstream
patch installation applies only to installations of server-based Siebel modules. As of version 8.1.1,
installers for Siebel client modules are based on Oracle Universal Installer technology (and do not
use siebel.ini files) and do not support slipstream patch installation.
Where slipstream patch installation is invoked by a full installation rather than by another patch
installation, the patch installation executes after language packs are installed. After all installations
are complete, the Siebel Configuration Wizard launches, for applicable products.
As noted in “Siebel Fix Pack Installation Overview” on page 441, slipstream patch installation may
apply in multiple installation scenarios. Applicable scenarios for the current product releases include:
■ Full installation plus patch installation. Performing a version 8.1.1 full installation plus a
Siebel Fix Pack 8.1.1.x installation. This scenario may optionally also include a Quick Fix release
for version 8.1.1.x (where applicable).
■ Multiple patch installations. Performing a Siebel Fix Pack 8.1.1.x installation plus a Quick Fix
release for version 8.1.1.x (where applicable).
NOTE: If you are adding languages to an existing version 8.1.1 or 8.1.1.x installation, slipstream
installation does not apply for the installation session for installing the languages. However,
slipstream installation can be used when subsequently installing Siebel Fix Pack 8.1.1.x and Quick
Fix releases. For more information about installing languages, see “About Installing Additional
Languages” on page 444.
You configure slipstream patch installation by modifying the base siebel.ini files for each applicable
Siebel module in the version 8.1.1 or version 8.1.1.x installation image, according to your install
scenario.
The siebel.ini files are also modified in installation scenarios described in the chapter about
unattended and console mode installations, in the Siebel Installation Guide for the operating system
you are using.
To support slipstream patch installation, where a version 8.1.1 full installation automatically invokes
a Siebel Fix Pack 8.1.1.x installation, modify the siebel.ini file for each applicable product for version
8.1.1, as shown below. Examples for setting Execute for different modules follow.
[Slipstream]
Install1 = yes
[Install1]
Execute = full_path_to_Siebel_product_installer_executable
Arg = arg_argument
where:
Execute = /Siebel_Image/8.1.1.x/AIX/Server/Siebel_Enterprise_Server/setupaix
To configure slipstream patch installation for Siebel Web Server Extension 8.1.1.x on Windows, the
value for Execute might be as shown below:
Execute =
D:\Siebel_Image\8.1.1.x\Windows\Server\Siebel_Web_Server_Extension\setup.exe
To include the Quick Fix release in the slipstream patching sequence, add Install2 = yes under the
last entry in the [Slipstream] section, then configure an [Install2] section for the Quick Fix
release. Configure the [Install2] section so it resembles the [Install1] section you configured for
the Siebel Fix Pack 8.1.1.x, but points to the Quick Fix release instead.
If you are using a security adapter, then you might need to update the value of the CRC parameter
after installing Siebel Fix Pack 8.1.1.x. The value must reflect the checksum value applicable to the
security adapter library file, such as a DLL file on Windows.
This task may be necessary if you previously determined to use checksum validation for your security
adapter deployment, and set the value of the CRC parameter. If a Fix Pack you installed later included
an updated security adapter library file, the checksum validation will fail and Siebel Web Clients
might not launch, unless the value of the CRC parameter is updated.
For detailed information about this task, see the topic about configuring checksum validation in
Siebel Security Guide.
The Web server must be restarted after you have finished installing Siebel Fix Pack 8.1.1.x on all
server-based components: Siebel Server, Siebel Gateway Name Server, Siebel Web Server Extension
(SWSE), and so on.
The restart is required because the Web server must be able to create a folder to contain static files
required for the current version of the Siebel application (corresponding to the latest Fix Pack
release). This folder is created as SWSE_ROOT/public/lang_code/build_number, where:
■ build_number is the current build number of the installed Siebel software (the build number
comes from the content of the base.txt file on the SWSE installation)
The folder described above and other folders are created on the first SWSE request after installing
any Siebel Business Applications release. This folder is populated with static files copied from the
Siebel Server directory SIEBSRVR_ROOT/webmaster/siebel_build. The contents of these folders are
refreshed each time the Web server restarts, or when an administrator enters a Web update
command in the browser. After a build-specific folder is created on the SWSE, folders representing
earlier builds are no longer used.
For more information, see the Siebel Installation Guide for the operating system you are using and
Siebel Security Guide, both on Siebel Bookshelf.
Failure to restart the Web server after installing the Fix Pack for Siebel Enterprise Server components
and for the SWSE means the folders will not be created on the Web server, which causes the Siebel
login screens to stop responding.
After installing a new version of a Siebel application, including a Siebel Fix Pack, new versions of
applicable ActiveX controls for the high interactivity client will be downloaded onto your users’ client
computers when they run the Siebel application within the Internet Explorer browser. Alternatively,
updated versions of the ActiveX controls you require can be predeployed to the client machines.
This behavior applies to Siebel Web Client (using high interactivity only), Mobile Web Client, and
Developer Web Client.
For more information, see the browser configuration chapter in Siebel System Administration Guide.
After a new Siebel software version is installed, Java controls for the high interactivity client will also
be downloaded. If caching is enabled, cached versions of these controls may need to be cleared on
the client machine. To clear this data, choose Start, then Settings, then Control Panel, and then Java
Plug-In. Click the Cache tab, then click Reset.
After a new Siebel software version is installed, is also recommended that users clear their browser
cache. To do this in Internet Explorer, choose Tools, then Internet Options, and then choose Delete
Files from the General tab.
For the minimum supported version of the Sun Java Runtime Environment, see Siebel System
Requirements and Supported Platforms on Oracle Technology Network. The Sun JRE can be
downloaded automatically to your machines. As described in 475457.1 (Doc ID) on OracleMetaLink
3, some configuration may be required in order to download the correct version.
If you are installing an additional language into an existing version 8.1.1.x installation, review the
information in this topic in case it applies to you. For more information about adding languages, see
“About Installing Additional Languages” on page 444.
Updates may be needed either because a string has been incorrectly translated for a particular
language, or because installing a patch has caused a new string or message to appear for all
languages for which Oracle ships language packs for Siebel Business Applications.
NOTE: These instructions are provided for use with any releases to which they apply, and might not
apply for any particular version 8.1.1.x release or any particular language.
The procedure below uses the Locale Management Utility (LMU), which is part of Siebel Tools, to
import an LMU file. An LMU file may contain strings in just one language or in multiple languages.
When running the Locale Management Utility, you can choose to import only the strings for the
languages you are actually using in your installation.
In the procedure below, when you are prompted for the file to import, specify the name of the LMU
file provided for the applicable language.
NOTE: Install any applicable Siebel Fix Pack before you run the Locale Management Utility.
For more information about using the Locale Management Utility, see Using Siebel Tools and Siebel
Global Deployment Guide.
The source language is the language of the locale-specific data in the LMU file you are importing.
The target language is the Siebel language into which the strings will be imported.
4 Enter the name of the LMU file from which you want to import locale-specific attributes.
You can also use the Browse button to find and select the file.
5 Specify whether you want to mark records in the repository with the Redo flag that have changed
since the export occurred.
When the import occurs, the LMU compares the source language records in the repository with
the source language records in the import file. If the records in the repository have changed since
the export occurred, they are marked with the Redo flag. This flag helps you identify records that
may need to be retranslated.
6 Click Import.
7 After finishing, recompile the SRF file and restart the Application Object Manager component on
the Siebel Server to see the results.
This topic describes how to uninstall Siebel Fix Pack 8.1.1.x releases for Microsoft Windows and for
supported UNIX and Linux platforms.
Generally, a Siebel Fix Pack 8.1.1.x release installed on top of version 8.1.1 (or a prior 8.1.1.x) can
be uninstalled. When you uninstall a Fix Pack, you revert to the version 8.1.1 base installation. The
uninstaller prompts you whether you want to uninstall just the Fix Pack (and revert to version 8.1.1)
or perform a full uninstallation of the installed software.
CAUTION: Separate uninstallation of a Fix Pack is not supported for Siebel Mobile Web Client, Siebel
Tools, or Siebel Sample Database. Only the full uninstallation option is possible for these modules.
Fix Pack uninstallation for modules not mentioned here is generally similar to what is described here.
To perform a full uninstallation of a Siebel module, follow the uninstallation instructions provided in
the Siebel Installation Guide for the operating system you are using.
■ “Guidelines and Limitations for Siebel Fix Pack Uninstallation” on page 462
In some circumstances, you may need to, or choose to, uninstall a Siebel Fix Pack 8.1.1.x release
and revert to the base installation (version 8.1.1). For example:
■ You may decide to uninstall an existing installed Siebel Fix Pack 8.1.1.x release before installing
a later Fix Pack. (This is optional.)
■ If issues are encountered in your deployment, you may decide to uninstall an existing installed
Siebel Fix Pack 8.1.1.x release and revert to version 8.1.1. Subsequently (where multiple Fix
Packs have been released), you may decide to install a lower-level Fix Pack.
CAUTION: If you revert to the version 8.1.1 base installation, change request fixes and new
functionality added in any or all Siebel Fix Pack 8.1.1.x releases are no longer available, until an
applicable Fix Pack has been installed. You will also need to take steps described later in this topic,
under guidelines and limitations. See also “Enhancements and Updates in 8.1.1.x Fix Packs” on
page 32 and “Resolved Change Requests” on page 462.
Follow the instructions below to uninstall the installed Siebel Fix Pack 8.1.1.x release and revert to
the version 8.1.1 base installation.
For more information about running uninstaller programs and about uninstalling Siebel base
installations, see the Siebel Installation Guide for the operating system you are using.
See also “Enhancements and Updates in 8.1.1.x Fix Packs” on page 32.
NOTE: For applicable server-based modules, You can also invoke the uninstaller by running
SIEBEL_ROOT\_uninst\product\uninstaller.exe, where product is one of the following values: ses
(for Siebel Enterprise Server components) or eappweb (for SWSE).
$SIEBEL_ROOT/_uninst/product/uninstaller optional_arguments
where:
■ product is one of the following values: ses (for Siebel Enterprise Server components) or
eappweb (for SWSE)
■ optional_arguments is one or more valid arguments for the uninstaller. For example, specify
-is:javaconsole -console to run in console mode.
Note the following guidelines and limitations related to Siebel Fix Pack uninstallation for installed
Siebel software:
■ Separate uninstallation of a Fix Pack is not supported for Siebel Mobile Web Client, Siebel Tools,
and Siebel Sample Database. Only the full uninstallation option is possible for these modules.
(For Siebel Sample Database, this limitation is due to the module being dependent on either
Siebel Mobile Web Client or Siebel Tools.)
■ If a Fix Pack installation fails, it is recommended that the administrator attempt to uninstall and
then reinstall the Fix Pack. If the uninstaller for the Fix Pack is not available, proceed with
reinstalling the Fix Pack. If these steps are omitted, future attempts to uninstall the Fix Pack may
fail.
■ If you made any repository or configuration changes related to a Fix Pack you have installed,
then, before uninstalling the Fix Pack, the repository or configuration must be restored to the
state when the Fix Pack was first installed.
Unless specifically noted in these tables, all known anomalies from the base version remain
unresolved. A fix introduced in an earlier maintenance release for a given base version will
automatically be included in later maintenance releases for that same base version.
NOTE: As noted above, Fix Packs are cumulative. However, the Resolved CR information for each Fix
Pack release has been provided in its own table.
For each release, the resolved changes tables include the following columns:
■ Fix Request ID. The tracking number for the fix request associated to the product defect.
■ Change Request ID. The tracking number for the product defect associated with the fix request.
■ Fixed in Version. The version number of the release in which the fix was first introduced.
■ Config Changes. A “Yes” in this column means that in order to incorporate the fix into your
Siebel implementation, you must make some configuration changes to your Siebel repository file
using Siebel Tools. These configuration changes are described in detail in the linked document.
■ Quick Fix Information. If you have installed a Quick Fix, please review “Quick Fixes Included in
8.1.1.x Fix Packs” on page 11.
■ “Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack” on page 463
■ “Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack” on page 507
■ “Resolved Change Requests in the Siebel 8.1.1.2 Fix Pack” on page 552
■ “Resolved Change Requests in the Siebel 8.1.1.1 Fix Pack” on page 577
Table 16 lists the Change Request that were resolved in the 8.1.1.4 Fix Pack.
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Analytics
RTD
ACR 623: IOG Enhancements 12-1YM4H1Q 12-1YM4GZ9 8.1.1.4 Yes, see
and Certification with RTD 3.0 “Instructions for
ACR 623” on
page 438.
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Call Center
CTI
Within OSES > Advanced Search 12-1VMB8J9 12-1V418VF 8.1.1.4
view, pressing Enter to execute
searches does not work
Other
When users press Alt F9 (Send 12-1YKOA8M 12-1XVFQ3H 8.1.1.4
Mail Wireless with SMS
Template), an activity is created
and then deleted
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
The All option does not search 12-1Z0MD73 12-1XM986H 8.1.1.4 Yes, see
on Web datasources “Instructions for
FR 12-
1Z0MD73” on
page 701.
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Comm Media
Energy
Assets
Modifying two assets generates 12-1ZM2V2V 12-1ZFBCAH 8.1.1.4
a query with full table scan on
S_ASSET table.
Connectors/EAI
EAI Server
Components
Extends the Siebel web services 12-1XKSPJH 12-1VMAPI0 8.1.1.4
framework to provide an
endpoint through Oracle WLS
(ACR 543)
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Other
When EAI Siebel Adapter is used 12-1ZOZ5CJ 12-1XBND23 8.1.1.4
with Query or QueryPage
methods, the SBL-DAT-60180
error message appears
Consumer Sector
Handheld
Users are unable to print voided 12-1ZD5KI4 12-1Z3IMD9 8.1.1.4 Yes, see
invoices “Instructions for
FR 12-1ZD5KI4,
FR 12-
1YZMU0U, FR
12-1Z04AQ7,
and FR 12-
1Z04AS3” on
page 701.
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
When users void an invoice that 12-1Z04AS3 12-1YOMS7P 8.1.1.4 Yes, see
was paid using a credit memo, “Instructions for
the amount of the credit memo FR 12-1ZD5KI4,
is not adjusted properly FR 12-
1YZMU0U, FR
12-1Z04AQ7,
and FR 12-
1Z04AS3” on
page 701.
Other
Trade Promotions Management 12-1ZVR7XG 12-1ZVR7O5 8.1.1.4
Quickstart (ACR 526)
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Retail Objectives
With Internet Explorer, when 12-1XF0XUJ 12-1XF0FX9 8.1.1.4
users drill down on an objective
target account and then click the
Back button, context is lost
Route Management
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Sales Volume
Planning
Performing a Mass Change 12-1UFAJ7B 12-1U5SBU1 8.1.1.4
causes an infinite loop during
category aggregation
Trade Promotions
ACR 358: Accounts are visible in 12-1ZZ4S5N 12-1K2K8F5 8.1.1.4
the Funds screen even though
the Fund Eligible check box is
not selected
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Customer Order
Management
Configurator
After users apply 8.1.1 QF00BQ, 12-1ZQWHRQ 12-1ZPH4ZU 8.1.1.4
they receive an error message
when they attempt the
BeginConfiguration step
ACR 502 provides the following 12-205G4TZ 12-1LNHQJJ 8.1.1.4 Yes, see
Siebel Configurator “Instructions for
enhancements: ACR 502” on
page 344.
■ The ability to defer an
update within a scripting
event to allow multiple
attribute change even add/
set attribute calls.
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
eSales
When users select filtered 12-1Z6EUT7 12-1Z4YJPX 8.1.1.4
products and click OK, the
application crashes
Order Management
Product Promotion does not 12-1XJD2O9 12-1XIVLVL 8.1.1.4
maintain defaults for products
from parent classes
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Orders
ACR 499 provides the following 12-1ZUS8XP 12-1ZUS8W7 8.1.1.4 Yes, see
enhancements to the Bulk “Instructions for
Orders functionality: ACR 499” on
page 291.
■ Bulk Promotion Upgrade and
disconnect: Customers can
apply promotions to
products using bulk
requests.
■ Account Group
Specification: Customers
can use existing account,
contact, or assets lists to
create bulk requests.
Products
When users edit product 12-1YJ7WX1 12-1YDFAIF 8.1.1.4
component relationships, they
receive an error message
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Data Quality
Cleansing
Service requests, activities, and 12-1UHQ1L9 12-1U5RB3V 8.1.1.4 Yes, see
statements are not moved from “Instructions for
a merged member to a surviving FR 12-
member during member merge 1UHQ1L9” on
page 698.
Deduplication
ACR 475: Incorrect match 12-1VNJME1 12-1VNJC3T 8.1.1.4
results occur for accounts and
contacts when EAI is used
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Other
ACR 475, QF3101: IIR crashes 12-1VR228F 12-1VNJDR2 8.1.1.4
when posting contacts through
EAI
General
Activities
Employee MVG applet data is 12-1Y9ZLKQ 12-1XHFA1T 8.1.1.4
erased when changing the
primary employee
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Application
Deployment Manager
Field 'XliffFileAutoUpdflg' 12-1YOKK0R 12-1YOKGBZ 8.1.1.4
missing when migrating BIP
Report Template Registration
ADM Data Type
Assignment Manager
Multi-Tier Assignment 12-1NTJ04W 12-1M4UP57 8.1.1.4
functionality is missing in Siebel
version 7.8 applications
Audit Trail
The Audit Trail does not capture 12-1Y9Z1NN 12-1XSJG29 8.1.1.4
cascade deletes on the HLS Case
business component
Business Rules
When calling Haley Expert Rules 12-1Y9HL5B 12-1XZBSUD 8.1.1.4
knowledge bases, a runtime
error (top-level business
component not configured)
occurs
Calendar
Daylight Savings Time (DST) 12-1N1KSBQ 12-1MAMEI5 8.1.1.4
changes do not occur for
repeating appointments
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Correspondence
When generating a 12-1OK0VKH 12-1OD185U 8.1.1.4
correspondence document, the
SIEBEL.HTML document
contains non-standard spaces
that appear incorrect in the
generated correspondence
document
CRM Desktop
The LOV is missing for the Lotus 12-1WTKAOZ 12-1WTKAOF 8.1.1.4
meta data file the
"ln_package_res.xml" file
File System
Large attachments fail to open 12-1XJDI01 12-1WEU3RJ 8.1.1.4
on Linux with multiple
filesystems
Global/Multilingual
LOV
Strings for icons in Russian 12-1YOMKFA 12-1YOLRNV 8.1.1.4
(RUS) are missing in 8.1.1
Installation
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Other
Passing arguments by reference 12-1VEOXOD 12-1U4I7J7 8.1.1.4
from within a with block in
escript in the new ST engine
gives incorrect results
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
PIM Server
Integration
The PIMSI Engine crashes when 12-1XTI77K 12-1TK463D 8.1.1.4
trying to sync more than 100
users
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Remote
Database initialization still fails 12-1YR2YPR 12-1SM2JSV 8.1.1.4
after QF06AH has been installed
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Reports Server
Errors occur when running 12-1VNKJIP 12-1V418JR 8.1.1.4
reports in SI applications (such
as eService, eCustomer)
Search
Certifies Oracle Secure 12-20CQ1B0 12-20CQ19Q 8.1.1.4
Enterprise Search (SES) on the
Oracle 11g platform
Security
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Server Infrastructure
It is necessary to recompile the 12-1Y63UTG 12-1U5UGI1 8.1.1.4
SRF to execute scripts for
debugging environment
SmartScript
After 8.1.1.2 has been installed, 12-1XB5ZLZ 12-1X65YA7 8.1.1.4
SmartScript buttons do not
allow keyboard clicks
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Task UI
When a transient business 12-1X46YC9 12-1V9U49H 8.1.1.4
component is accessed across
two different TBUI views, the
application may not function
properly
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Tools/Configuration
Siebel Tools sometimes hangs 12-1SLL0QL 12-1PEQLIL 8.1.1.4
when applying schema changes
(such as a new extension
column)
Upgrade
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Workflow
Workflow policies triggered on 12-1R1VXOW 12-1QBCC09 8.1.1.4
extension tables do not fire
actions
Life Sciences
Clinical Account
Profiles
Within Administration - Clinical 12-1ZYN9IP 12-1TK3LHO 8.1.1.4 Yes, see
(Administração - Clínica) > “Instructions for
Protocol List (Lista de FR 12-1ZYN9IP”
protocolos), the title of Cargo is on page 696.
not correct.
Clinical Profiles
Within the Clinical Protocol 12-1ZUS8M9 12-1VM8M3T 8.1.1.4 Yes, see
Regions View, when users click “1Instructions
on subtabs (such as for FR 12-
Attachments or Contacts), the 1ZUS8M9” on
application refreshes and page 696.
displays a different Protocol
Number value than the one that
the users selected
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
List Management
Within Events > Resources > 12-1Y902JY 12-1WF6IYP 8.1.1.4
Staff, when users add two
records, delete one of the
records, and save the remaining
record using CTRL+S, an error
message displays and the
deleted record comes back
Other
Converts the Site Initiation By 12-1P4ORNG 12-1OQUM19 8.1.1.4 Yes, see
Site Actuate report (LS_INBSIT) “Instructions for
to BI Publisher FR 12-
1P4ORNG” on
page 695.
BIP report - Telephone and Fax 12-1YJ7X13 12-1QCS8LG 8.1.1.4 Yes, see
Numbers are not displayed in “Instructions for
the expected format FR 12-1YJ7X13”
on page 695.
Payments
The Payments Exception Query 12-1YFTGBH 12-1Y0B1UK 8.1.1.4 Yes, see
button does not work properly “Instructions for
FR 12-
1YFTGBH” on
page 694.
Protocol Builder
BIP: Pharma Site Enrollment 12-1P4ORM0 12-1OQUM7F 8.1.1.4 Yes, see
Status By Protocol - “Instructions for
LS_SITENRL FR 12-
1P4ORM0” on
page 694.
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Loyalty
Loyalty Customer
Portal
When transactions are moved 12-1Z3ZZO2 12-1TLCZVH 8.1.1.4 Yes, see
between members, accrual “Instructions for
records are not moved FR 12-
1Z3ZZO2” on
page 689.
Loyalty Engine
The LoyaltyEngineInteractive 12-1WB4GPH 12-1VI06M8 8.1.1.4
Object Manager has a memory
leak of around 88 KB
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Loyalty Manager
When users query within the 12-1XM93ST 12-1XHDRIJ 8.1.1.4 Yes, see
Points Balance view, rows “Instructions for
appear that should not be FR 12-
displayed 1XM93ST” on
page 689.
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
After two members are merged, 12-1YKOEQV 12-1TUEX22 8.1.1.4 Yes, see
the survivor member cannot “Instructions for
redeem points from the merged FR 12-
member points 1YKOEQV” on
page 688.
Marketing
Campaigns
Campaign repeating tasks may 12-1TKAALE 12-1THO6QN 8.1.1.4
repeat unexpectedly if record
contention occurs
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Events
An error occurs if two users try 12-1XQ4DQQ 12-1X1RY8J 8.1.1.4
to confirm an event attendee
concurrently
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Marketing Server
Campaign load will reject some 12-1UW60OB 12-1UH8JVF 8.1.1.4
rows as errors if the same
contact is targeted with more
than one treatment
Other
RTD 3.0: Within the Realtime 12-1YOMJX3 12-1YOMJWJ 8.1.1.4
Details view, the Sync button,
Last Sync Date field, and the
Need To Sync field should be
disabled
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Programs
Marketing Object Manager may 12-1VR268K 12-1VM5KMF 8.1.1.4
fail when two users delete a
campaign list at the same time
Mobile Solutions
Handheld for Windows
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Other
The Mobile Web Client crashes 12-1Y289R5 12-1K501OP 8.1.1.4
when script is added to the
Docking Service Business
Service
Wireless
Integration of Mobile Sales 12-1TXT8U0 12-1RCXQ1N 8.1.1.4 Yes, see
Assistant to the Siebel On- “Instructions for
Premise application (ACR 626) ACR 626” on
page 438.
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Partner
Relationship
Management
Other
If the PRM ANI Utility Service of 12-1X0BIRS 12-1QTP7PD 8.1.1.4
EAI Workflow is being called in
the EAI Object Manager many
times (hundreds of thousands of
times) repeatedly, the virtual
memory of EAI Object Manager
increases by about 5 MB for
every 10000 times that the
service is called
Public Sector
Other
Customers can not access 12-1ZW8OVR 12-1ZW8OV7 8.1.1.4
Incidents-related views because
of a license-key issue
Sales
Forecasting
Senior levels in forecasting 12-1XVG7QX 12-1XM98B7 8.1.1.4
hierarchy not able to generate
forecasts
Other
The Relationship Hierarchy view 12-1YOMKPD 12-1T2ILHX 8.1.1.4
allows access to all accounts
across all organizations
The Next arrow for the "Bill To" 12-1ZL9LEQ 12-1YNLB8N 8.1.1.4
Relationship Hierarchy Tree
Applet does not work
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Territory Management
Geo-Zone-based rules for 12-1U3BTSP 12-1U0C8HX 8.1.1.4 Yes
accounts do not give expected
results
Service
Other
If a manager has more than one 12-1PQPP5B 12-1PFQSZV 8.1.1.4
expense report to be approved,
when the manager clicks the
approve button for a expense
report gets approved and the
cursor is moved to the next
expense report, if the manager
selects On the Last Record Again
and clicks the approve button,
the manager receives the
following error message: "End of
file error has occured. Please
continue or ask your system
administrator to check your
application configuration if the
problem persists. (SBL-DAT'-
00393)".
Preventive
Maintenance
The Preventive Maintenance 12-1QR9B1Y 12-1Q0IVOB 8.1.1.4
Engine does not release the
database open cursors, which
creates a memory leak
Scheduling
GanttChart AX Applet does not 12-1RAJ8PX 12-1Q0IVS7 8.1.1.4
work in multilingual
environments
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Siebel E-
commerce for
Comms
Miscellaneous
Child products under a default 12-1YBWJSS 12-1VCQTQ1 8.1.1.4
CP in an upgraded promotion
are not shown in the Summary
of Changes page
Siebel Self
Service Common
Miscellaneous
Users are unable to launch the 12-1Z3HSYD 12-1YOJTGX 8.1.1.4
Self-Service URL
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Universal
Customer Master
Data Management
QF3104: When users unmerge 12-1ZQWVG8 12-1Z7DQZ9 8.1.1.4
contacts from accounts, the
association is not retrieved
EAI
ACR 437: With EAI, when 12-1VM871M 12-1VH3RYD 8.1.1.4
IsPrimaryMVG is set to Y,
records are not updated as
primary
Integration
The 'UCM Batch Manager' 12-1U0AQT7 12-1IBE8WR 8.1.1.4
Business Service
'ExecutePropSets' method
crashes when querying for an
account produces 0 rows
Other
ACR 475: When trying to select 12-205XKI9 12-205XKGR 8.1.1.4
a DnB Account to export to DRM
from UCM, an error message
occurs
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Publish/Subscribe
ACR 475, Higher Education: 12-1U5RIS6 12-1U0AEGZ 8.1.1.4
Publish fails for constituent data
Survivorship
ACR 475: Survivorship is not 12-1VR5FDN 12-1VNKG5Z 8.1.1.4
invoked in transaction manager
User Interface
Controls
Within the calculator function, 12-1XS1MGK 12-1XS1MG0 8.1.1.4
when users press the Enter
button, results do not display
History/Back/Refresh
After users click the Back 12-1VR2ZJV 12-OVT1LK 8.1.1.4
button, applets are displayed as
form applets instead of as list
applets
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Navigation
With Internet Explorer 7, when 12-1YMM6I5 12-1Y54CNH 8.1.1.4
users drill down on a link, the
application crashes
Other
Within Server Reporting, 12-1ZARFCK 12-1YO2RKX 8.1.1.4
predefined queries that contain
umlauts do not perform well
Popups/Pick Lists/
MVG/Shuttle
With Auto-hide on, closing an 12-1XTI9RZ 12-1XRKL8L 8.1.1.4
MVG results in a minimized
window
Toolbars/Menus/
Keyboard
Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Web Service
Other
The Siebel application expires 12-20M5KBU 12-20M5KB3 8.1.1.4
the session token when
SiebelSessionTimeOut value is
less than the
SessionTokenTimeout value
Table 17 lists the Change Requests that were resolved in the 8.1.1.3 Fix Pack
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Call Center
CTI
After 7.8.2.3 QFJ316 has been 12-1RRBR7O 12-1REPWYN 8.1.1.3
applied, CTI toolbar worker
threads loop infinitely
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Other
Searchable fields in the search 12-1PILI7W 12-1ONVDPT 8.1.1.3
results view are not being shown
Users are not able to change a 12-1TUEA6P 12-1SFP9CV 8.1.1.3 Yes, see
default date for Advanced “Instructions for
Search FR 12-1TUEA6P”
on page 717.
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
ACR 574: Provides Lymba as the 12-1WB70VJ 12-1UI8IN7 8.1.1.3 Yes, see
Smart Answer Engine “Instructions for
ACR 574” on
page 432.
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Comm Media
Energy
Order Management
Provides support for the OSM 12-1UJS4WK 12-1TK6U03 8.1.1.3 Yes, see
Integration and new Order to “Instructions for
Activate PIP, and forward-ports ACR 474 and ACR
MDM for customer and PIM, and 508” on
Order to Cash enhancements page 159.
from 8.x to 8.1.1. (ACR 474/
AIACOMS 2.5)
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Provides support for the OSM 12-1UZ5YMC 12-1UW5DFF 8.1.1.3 Yes, see
Integration and new Order to “Instructions for
Activate PIP, and forward-ports ACR 474 and ACR
MDM for customer and PIM, and 508” on
Order to Cash enhancements page 159.
from 8.x to 8.1.1.x (ACR 474/
AIACOMS 2.5)
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
When users create a new sales 12-1XTI4WC 12-1X0C24K 8.1.1.3 Yes, see
order, add a TBO product to the “Instructions for
order, click Customize, and then ACR 474 and ACR
click Done, within Sales Order 508” on
line items, the Service Start page 159.
Date field is blank
ACR 474: The bar on the line 12-1Y3OPDC 12-1XTI4RH 8.1.1.3 Yes, see
items view shows a cancelled “Instructions for
status ACR 474 and ACR
508” on
page 159.
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
ACR 474: Revised orders copy 12-1Y3OPDM 12-1XTI4OQ 8.1.1.3 Yes, see
fulfillment status and status “Instructions for
context from the base order ACR 474 and ACR
508” on
page 159.
Errors occur when updating the 12-1Y6LLL2 12-1Y6LLKD 8.1.1.3 Yes, see
Part# or inserting a record with “Instructions for
the Part # field populated in the ACR 474 and ACR
line 508” on
page 159.
Other
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Connectors/EAI
Application Svc
Interface/ASI
EAIHttpRespStatus code is set to 12-1RXY7ZA 12-1QNEH19 8.1.1.3
the incorrect value on Itanium
systems
EAI Server
Components
After 8.0.0.2 QF2207 has been 12-1UI8D5R 12-1U5R29R 8.1.1.3
applied, the 'signature' error still
occurs with a SWSE timeout
Other
Date-time data passed in 12-1YOLHXJ 12-1YOLHWR 8.1.1.3 Yes, see
payloads in UTC canonical “Instructions for
format (such as '2009-08- FR 12-1YOLHXJ”
14T03:09:01Z') throws the on page 717.
"cannot convert the value to
Date-Time" error message
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Consumer Sector
Handheld
The Cancel Invoice function does 12-1VMB721 12-1VM6HI1 8.1.1.3 Yes, see
not allow invoices to be marked “Instructions for
for deletion/voided FR 12-1VMB721
and FR 12-
1X0C0IZ” on
page 711.
Other
While processing accrual 12-1TPUQPM 12-1TGOA74 8.1.1.3
records, the addition is not
correct for the update to the
S_MDF_ACCRUAL.REVENUE_AM
T field
Customers are not able to void 12-1X0C0IZ 12-1VMBL0Z 8.1.1.3 Yes, see
faulty invoices and undo “Instructions for
payments and delivery for the FR 12-1VMB721
faulty invoices and FR 12-
1X0C0IZ” on
page 711
Objectives
Error messages that occur 12-1WHFTJD 12-1WF6PQV 8.1.1.3
during field validation do not
display correctly
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Trade Promotions
ACR 480: Within Corporate 12- 12-1VR4BZH 8.1.1.3 Yes, see
Promotions, the Apply Updates 1XCMB0W “Instructions for
function pushes products to the FR 12-1XCMB0W”
wrong category on page 710.
Customer Order
Management
Configurator
Applying FR 12-1N7B0OP causes 12-1VNJ53G 12-1VM83AX 8.1.1.3
action codes to be incorrect
Order Management
Enhances the AIA Order-to-Cash 12-1UZ5YP2 12-1UW5F8T 8.1.1.3 Yes, see
PIP to provide the ability to “Instructions for
change data on the Siebel Order ACR 508” on
screen and send the order to E- page 356.
Business Suite for processing
(ACR 508)
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Orders
If a CP has lot of rules with 12-1V7FE0H 12-1UWODHL 8.1.1.3
required attributes and the
attributes are not selected,
clicking Verify yields the
following error message: Value
too long for field 'Return
Message' (maximum size
1000).(SBL-DAT-00235)
Other
Users receive an error message 12-1X5NS4E 12-1X47HF9 8.1.1.3
when they upgrade promotions
from Service Account Installed
Assets
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Pricer
When users invoke the Pricing 12-1X5NXAL 12-1W6PXXB 8.1.1.3
Waterfall pick applet, the
application hangs
Sales Catalog
An error occurs when users 12-1YFTLDP 12-1XB55W9 8.1.1.3
disconnect a promotion after a
component of the promotion has
been disconnected
Data Quality
Deduplication
In the Polish (PLK) v8.1.1 12- 12-1UQ61Q1 8.1.1.3
version of the application, an 1VGM2UG
error occurs while running the
SSA Name3 library (n3sgsb)
Other
Using ISS with Siebel 8.0 results 12-1U0CY1S 12-1STC0TH 8.1.1.3
in the SBL-DAT-00381 error
message
Financial Services
Other
Within Claims > Loss Details, 12-1Y5LSOW 12-1Y5LSL2 8.1.1.3
the Create Reserves button is
disabled in the Coverages list
applet
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
General
Activities
When users attempt to update 12-1R1BTR7 12-1QJ1W43 8.1.1.3
the Planned Date and Due Date
fields using the Action Business
component through workflow
processes, the inserted values
are not saved to the database
Application
Administration
If users do not have the Siebel 12- 12-1XZMHAN 8.1.1.3
administrator privileges/ 1XZMHBG
responsibilities for their
Contacts and Responsibilities,
login fails
Assignment Manager
ACR 456: Formats of exported 12-1TWTYTF 12-1TWTYSQ 8.1.1.3
and imported files should be the
same
Audit Trail
The Audit Trail button behaves 12-1SPH0YN 12-1S5B2VD 8.1.1.3
inconsistently
The Audit Trail does not work for 12-1SWPT3X 12-1SD8XW1 8.1.1.3
the "FINS Claims Reserve Code
Admin" Business Component
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Calendar
The Send Email function is 12-1N1KL71 12-1K4ZTWH 8.1.1.3
unavailable
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Content Management
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Correspondence
Correspondence documents 12-1T2SVNQ 12-1SJNUGJ 8.1.1.3
contain additional space
characters
CRM Desktop
CRM Desktop: Improves the 12-1Y27VNT 12-1Y27VMJ 8.1.1.3
quality of the 'SBL-DOI-00006'
and 'SBL-DOI-00007' error
messages
File System
File System cleanup fails with 12-1UK14LM 12-1UI9S1Q 8.1.1.3
the "Failed to open the iterator"
error message
Installation
In 8.1.1.2, some files related to 12-1WR7UFE 12-1WR7UEP 8.1.1.3
siebel_sample_database are
missing
Other
Records obtained using the 12-1SCRGIB 12-1QV5W97 8.1.1.3
Access drop-down list display in
Base mode instead of in Edit
mode
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Personalization
It is not possible to use 12-1RV70SJ 12-1JJTA87 8.1.1.3
personalization rules to hide
views dynamically in Siebel 8.0
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
PIM Server
Integration
If an attendee is added to an 12- 12-1V9UFL1 8.1.1.3
Outlook/Exchange calendar item 1VM9ZON
after the initial sync, the data is
not pushed to the Siebel
database
Remote
File System cleanup deletes files 12-1UQ47CQ 12-1UJQWRB 8.1.1.3
that are referenced
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Reports Server
Users are not able to add a 12-1QCSJZ4 12-1QCSJXR 8.1.1.3
sequence number to the Reports
applet in View Association
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
When users set a default value 12-1XIE4NT 12-1X29VEW 8.1.1.3 Yes, see
for an LOV parameter in the RTF “Instructions for
template, the default value that FR 12-1XIE4NT”
they set does not appear as the on page 709.
default value in the popup list
applet
Search
Fields of type DTYPE_PHONE are 12-1SPY7BZ 12-1S9QMMD 8.1.1.3
not searchable
Security
eService permits users to log in 12-1TI62O9 12-1T2II25 8.1.1.3
with expired LDAP passwords
Send Email
When users cancel the F9 Send 12-1U93HR1 12-1TSQ0MP 8.1.1.3
Mail command, list applets
become unresponsive
Server Infrastructure
The default values of compiler 12-1O9NH16 12-SNUGZT 8.1.1.3
define FD_SETSIZE on Solaris
and HP-UX are set too low
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
The 'list stats' and 'list stats for 12-1RHA25T 12-1QXJF75 8.1.1.3
comp SCCObjMgr_enu' srvrmgr
commands produce an invalid
value-INF-for the CPUTime
statistic
Siebel Sync
After version 7.7.2.10 has been 12-1X980QT 12-1Q5L7W9 8.1.1.3
installed, the Lotus Notes Action
button disappears at the second
synchronization
SmartScript
ACR 574: Users are not able to 12-1WB70Y1 12-1VR347X 8.1.1.3
import different files using the
Smart Answer import button
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
State Models
State Models with "No Delete" 12-1SK4YF1 12-1S5B2PJ 8.1.1.3
set do not allow UndoRecord and
cause an error
Task UI
Validation of a Transient 12-1QFPEOP 12-1PPACL7 8.1.1.3
Business Component does not
function correctly
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Tools/Configuration
If script that raises an error 12-1QR9AYR 12-1PLG9OF 8.1.1.3
using RaiseErrorText is placed in
the WebApplet_Load event of
some applets, the error is not
displayed, but the entire script is
displayed
Upgrade
ACR 529: Provides a single-step 12-1T5W181 12-1SW8HKB 8.1.1.3
upgrade from Siebel Enterprise
Applications to Siebel Industry
Applications
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Web Framework
The ShowPopup method cannot 12- 12-1VH3RNJ 8.1.1.3
be invoked by a keyboard 1VM6NOB
accelerator
Workflow
Workflow Simulator crashes at 12-1RKM7V7 12-1ISLMDM 8.1.1.3
the LoadInstance (RCOIS BS)
step
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
iHelp
Other
In Siebel applications version 12-1N1KTE0 12-1L1J856 8.1.1.3 Yes, see
8.0, the New button is not “Instructions for
highlighted FR 12-1N1KTE0”
on page 708.
Life Sciences
Activity
Samples do not display when 12- 12-1VR4BT3 8.1.1.3 Yes, see
using the Inventory field, the Lot 1WWY5P4 “Instructions for
# Tracking field, and the FR 12-1WWY5P4”
Inventory by Lot field on page 706.
Clinical Account
Profiles
ACR 539: Modified Protocol site 12-1Y901CQ 12-1Y901B7 8.1.1.3 Yes, see
addresses in the Siebel “Instructions for
application are not getting ACR 539” on
updated in Oracle Clinical page 361.
Clinical Manager
Applying an Activity Template 12-1VR3QRB 12-1VM8H57 8.1.1.3
across multiple sites does not
work properly
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
ACR 539: Visit Sequence does 12-1X1S0P0 12-1OOD149 8.1.1.3 Yes, see
not get copied over from the “Instructions for
Subject visit template ACR 539” on
page 361.
Clinical Profiles
ACR 539: When the 12- 12-1VR73HT 8.1.1.3 Yes, see
ApplyTemplate workflow is 1WB70O1 “Instructions for
triggered through the UI, ACR 539” on
refresh does not occur page 361.
ACR 539: Search Center should 12-1X1S02N 12-1X0BGMO 8.1.1.3 Yes, see
accept incoming ICDs from “Instructions for
Order to Cash and default only ACR 539” on
when the date is unavailable page 361.
ACR 539: The Primary Site 12-1X4OYJB 12-1WF73ZD 8.1.1.3 Yes, see
Address pick applet field accepts “Instructions for
arbitrary values ACR 539” on
page 361.
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
ACR 539: Incoming NULL ICDs 12-1Y6LO7Y 12-1Y54O8F 8.1.1.3 Yes, see
from Oracle Clinical update valid “Instructions for
existing ICDs for subjects in ACR 539” on
Siebel Clinical page 361.
ACR 539: The status of subjects 12-1Y8IUF9 12-1Y8IUEI 8.1.1.3 Yes, see
still displays as Screened after “Instructions for
the enrollment date has been ACR 539” on
entered page 361.
eMedEd
Adds electronic medical device 12-1X0TENB 12-1OJC7XR 8.1.1.3 Yes, see
reporting to the AECM module “Instructions for
(ACR 426). ACR 426” on
page 66.
ACR 426: After ACR 426 has 12-1Y3OEAS 12-1Y36V4H 8.1.1.3 Yes, see
been installed and configured, “Instructions for
the Transmit button is disabled ACR 426” on
page 66.
Medical Education
ACR 426: B2 values are not 12-1XF0LI1 12-1R851IL 8.1.1.3 Yes, see
displayed in XML “Instructions for
ACR 426” on
page 66.
Other
ACR 426: The flag for 12-1S987UE 12-1R8LVJT 8.1.1.3 Yes, see
Transmitted-Rejected does not “Instructions for
display ACR 426” on
page 66.
ACR 426: The Reg Report view 12- 12-1S99GKY 8.1.1.3 Yes, see
displays eMDR status for an RR 1U5D3W7 “Instructions for
that is not in the eMDR queue ACR 426” on
yet page 66.
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
ACR 426: The FDA Status field is 12-1VNIQ18 12-1U5TKPH 8.1.1.3 Yes, see
not being updated correctly “Instructions for
ACR 426” on
page 66.
ACR 426: The eMDR LOV is 12-1XF0LCT 12-1R6NTLT 8.1.1.3 Yes, see
missing and there is a typo “Instructions for
within Accepted; LOV Type = ACR 426” on
LS_MED_RR_TRANS_SUB_STAT page 66.
US
ACR 426: The F10 values are not 12-1XF0LJ2 12-1R9TWH2 8.1.1.3 Yes, see
found in the path for patient “Instructions for
code in the XML, and the F11 ACR 426” on
values are not present in the page 66.
XML
ACR 426: Provides batch files for 12-1XF0LD4 12-1R6NTMI 8.1.1.3 Yes, see
importing .sif files and seed data “Instructions for
for ACR 426 and for ACR 372 as ACR 426” on
well page 66.
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
ACR 426: The F13 value is not 12-1XF0LG3 12-1R8LVMN 8.1.1.3 Yes, see
populated in the XML “Instructions for
ACR 426” on
page 66.
ACR426: The B1 Code for the AE 12-1XF0LH2 12-1R8LVO2 8.1.1.3 Yes, see
Drug event type is not displayed “Instructions for
in XML ACR 426” on
page 66.
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Protocol Builder
Users are unable to apply a new 12-1TQTU4C 12-1NWCZ7B 8.1.1.3 Yes, see
subject visit template in order to “Instructions for
create subject visits. FR 12-1TQTU4C”
on page 702.
Regulatory Reports
Adds electronic medical device 12-1U5D3P7 12-1U0ASU4 8.1.1.3 Yes, see
reporting to the AECM module “Instructions for
(ACR 426) ACR 426” on
page 66.
Trip Reports
In the Trip Report Details view, 12-1VR2857 12-1UIB7XV 8.1.1.3
after users select a trip report
template, do not update the
checklist items, and then try to
generate a BI Publisher report,
the application yields an error
message
Loyalty
Loyalty Customer
Portal
An error occurs while generating 12-1VR4PXA 12-1VMCEM9 8.1.1.3
statements for post-paid
partners
Loyalty Engine
When the LOY Batch Enrollment 12-1VM86N5 12-1VM72OT 8.1.1.3
Service is used, cursors are not
being released
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Loyalty Manager
The Voucher validity business 12-1VMBCJG 12-1VMAXQF 8.1.1.3
service does not return a failed
verification when a voucher is
used or expired
Marketing
Campaigns
Stage Execution fails with the 12-1SX7SLV 12-1STTN3F 8.1.1.3
error that the record has been
modified by another user
Wave Numbers are not assigned 12- 12-1VMC9ID 8.1.1.3 Yes, see
to Control Group records 1WUJ5W5 “Instructions for
FR 12-1WUJ5W5”
on page 702.
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Marketing Server
Campaign load rejects some 12- 12-1RVO17F 8.1.1.3
rows as errors if same contact is 1SSCMNU
targeted with more than one
treatment
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Other
A lead is still associated to a 12-1VM6EMK 12-1VM6ELV 8.1.1.3
prospect after the prospect is
promoted
Mobile Solutions
Handheld for Windows
Handheld PatchAgent fails when 12-1Q0MF5H 12-1PPAE9M 8.1.1.3
UserDefinedLang=Y and the
userstr.txt file exists on the PDA
device
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Other
Case Insensitivity and Accent 12-1Q06NYO 12-1JNWG6G 8.1.1.3
Insensitivity (CIAI) does not
work on the local database
Store-and-Forward
Messaging
Handheld, Store-and-Forward 12-1VMBFQI 12-1U5TD5N 8.1.1.3
messages on the PDA appear
only in ENU, regardless of the
Siebel language on the PDA
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Partner
Relationship
Management
Partner Manager
After users register a partner, no 12-1X668T1 12-1WF6FQC 8.1.1.3
records display in the Qualified
Partners view
Public Sector
Other
After an application has been 12-1Y5OQS8 12-1Y5MGFN 8.1.1.3
submitted, the Upload button is
still enabled
Section 508/
Accessibility
ACR 562: Provides Accessibility 12-1WU188L 12-1W6DOPP 8.1.1.3 Yes, see
enhancements for Siebel version “Instructions for
8.1.1.x applications. ACR 562” on
page 387.
For more detailed information
about what ACR 562 provides,
see “Enhancements and Updates
in Version 8.1.1.3” on page 33.
Sales
Forecasting
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Opportunities
Numeric and picklist fields 12-1XIVK5N 12-1JD9K31 8.1.1.3
temporarily blank out after
Siebel 7.7.2.8 has been applied
Service
Contracts
Auto entitlements does not 12-1SZMNL2 12-1RPRACV 8.1.1.3
apply the template information
to all line items
Other
Within eService > Advanced 12-1VR5LU1 12-1VMAF2Z 8.1.1.3
Search, searching with the All
option does not work
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
The hour unit does not work for 12-1X65BT0 12-1WXXADT 8.1.1.3
any start time for the
GetElapsed method
Preventive
Maintenance
The Preventive Maintenance 12-1VBATMM 12-1TAR4ZP 8.1.1.3
Engine crashes
Scheduling
The "Load ABS" function does 12-1U5RX6U 12-1REV4NL 8.1.1.3
not work correctly right after the
Siebel Server service has been
restarted
Siebel eMail
Response
General
Provides an addtional output 12-1S1XENY 12-1JGY6HC 8.1.1.3
argument from the
CreateRequest method from the
Outbound Communications
Manager BS to return the
activity id of the outbound email
activity generated automatically
by the CreateRequest method
Siebel Self
Service eCommon
Miscellaneous
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
User Interface
Controls
Form Redirect uses POST as the 12-1QKI632 12-1O2IS17 8.1.1.3
default and not GET
History/Back/Refresh
Thread bar navigation does not 12-1TJM5Y1 12-1NXS3RV 8.1.1.3
work when view names contain
special characters
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Other
The GetCalendarData method is 12-1QL06QH 12-1IHL5T5 8.1.1.3
missing a WHERE clause, so SQL
retrieves all of the activities in
the Activity HI Calendar applet
Popups/Pick Lists/
MVG/Shuttle
Using pick applets causes 12-1RXL8O6 12-1REVDKP 8.1.1.3
Internet Explorer 7 and Vista to
crash
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack
Web Service
Other
The EAI UI Data Adapter service 12-1SSCIPY 12-1RAJ0I1 8.1.1.3
search specifications <> and <
operators do not work and
generate an XML parsing error
Table 18 lists the Change Requests that were resolved in the 8.1.1.2 Fix Pack.
Call Center
CTI
In Siebel 8.1.1, when users query 12-1U5RK5A 12-1TK4CEL 8.1.1.2
in a case-insensitive column, BI
Publisher report data does not
appear
Other
Assignment Manager does not 12-1U0A7S1 12-1T12HUL 8.1.1.2
assign incidents
Comm Media
Energy
Order Management
Accepting product 12-1TK8BL1 12-1TB8YRV 8.1.1.2 Yes, see
recommendations add wrong “Instructions for
product to quote or order. FR 12-1TK8BL1”
on page 717.
Connectors/EAI
EAI Server
Components
Automatic relogin does not occur 12-1R3SFV9 12-1R1EH5L 8.1.1.2 Yes, see
for Stateless SessionType “Instructions for
FR 12-1R3SFV9”
on page 717.
Other
AnonUserPool requires SWSE 12-1TTL0L1 12-1TK6KJB 8.1.1.2
Server restart to recover from
Siebel EAI OM Component
outage.
VBC cache does not work for the 12-1TENTWD 12-1T6DMLW 8.1.1.2
CSSFABCVRec specialized class
Consumer Sector
Handheld
Sync locks the application if there 12-1U0CC0E 12-1TYBGYE 8.1.1.2
has been a sync exception
because of an incomplete
transaction
Customer Order
Management
Configurator
<ListofLinkedItems> tag is not 12-1UI92KZ 12-1TXC3RL 8.1.1.2
working correctly in web services
Order Management
A crash occurs in ABO cycles 12-1VM5GQ5 12-1VM5K43 8.1.1.2
when AutoMatch is called
Other
Promotions: The default 12-1U0DJZN 12-1TUVZQ9 8.1.1.2 Yes, see
cardinality of a relationship in a “Instructions for
CP is ignored when it is 0. Any FR 12-1U0DJZN”
relationship default cardinality in on page 718.
a promotion greater than 0
works. This FR addresses the 0
default scenario.
Pricer
Manual price overrides are lost 12-1TYSJWU 12-1T2J5H3 8.1.1.2
when quantities are changed
using rules
Data Quality
Deduplication
Functional anomalies are found 12-1UIB3HP 12-1TK6K87 8.1.1.2
within Data Quality Self-Service
Applications matching
Other
The batch data cleansing 12-1UHQ1IM 12-1R6NUCR 8.1.1.2
algorithm for UDQ is missing the
sdq_close_session call
General
Accounts
Application
Deployment Manager
Adds the ability to sequence 12-1VJIAVE 12-1QR8NKV 8.1.1.2
database deployment units in a
package
Audit Trail
After FRA users upgrade to 8.1.1, 12-1TYSS6S 12-1TD6X31 8.1.1.2
the Audit Trail language remains
ENU
Business Rules
Calendar
If users make changes to a 12-1US5U74 12-1SFP9PD 8.1.1.2
calendar item on the HI Calendar
views and click the browser's
Back button, the changes are not
saved
Correspondence
Installation
On the Linux platform, URLs do 12-1WF6D7D 12-1WF6D6N 8.1.1.2
not come up after 8.1.1.1 SIA has
been applied on 8.1.1 SIA
Other
"Maximum open cursors" error 12-1TXT8PN 12-1T12H8N 8.1.1.2
received when generating large
number of Proposal drafts
Performance
Double parsing without bind peek 12-1ORCIOH 12-1OQD0BB 8.1.1.2
in Oracle Connector causes
performance degradation
Personalization
If an association applet is 12-1TK8BFY 12-1THO6OP 8.1.1.2
assigned a rule set for
personalization that uses an
include expression to act as a
search specification, the include
expression is ignored
Remote
ACR 544: Enhances the Siebel 12-1UZ5TVC 12-1SW8HHD 8.1.1.2
Remote utility and allows it to be
intergrated with the Siebel HA
Upgrade solution
Search
ACR 439: Search Center does not 12-1P1OP6D 12-1NZODJL 8.1.1.2
remember terms and results after
it has been closed
Security
SWEU parameter should ignore 12-1N22J3V 12-1IYN1VD 8.1.1.2
hostnames to prevent phishing
Server Infrastructure
Addresses a problem with ACR 12-1QK1GVJ 12-1PLGZW1 8.1.1.2
405 where Dynamic MQ Reply
Queue does not work
Siebel Sync
ACR 468B: Allows Siebel Client 12-1UZNMA7 12-1S4ZI88 8.1.1.2 Yes, see
Sync to support Lotus Notes 8.0 “Instructions for
and Microsoft Outlook 2007 with ACR 468” on
Intellisync 7.x SDK. page 157.
SmartScripts
Smartscripts are causing Internet 12-1V0N8EM 12-1UQ62AL 8.1.1.2
Explorer to crash after installing
the 8.1.1.1 patch
Task UI
Invoking the binocular search 12-1V7F9GQ 12-1V3JQI3 8.1.1.2
icon from the Siebel application
toolbar while stepping through a
TBUI Task may cause the local
server to hang and the Siebel
application to crash
Tools/Configuration
An error occurs with the global 12-1N1RBJY 12-1M81JE0 8.1.1.2
variable of type property set
initialization in the global section
of Business Services
Upgrade
The Symbolic String Conversion 12-1STTIXO 12-1SI5H61 8.1.1.2
utility (consoleapp.exe) fails in
Siebel 8.1.1
Web Framework
Exporting from browsers that are 12-1QTPRGH 12-1J1X6NA 8.1.1.2
running Windows 2000 SP1 or
Windows XP SP2 causes session
timeouts from Siebel 7.7.2.6
onwards
Workflow
Business services that do not 12-1SSCMJ3 12-1SBRA31 8.1.1.2
initialize and return Output
Arguments to workflow steps tat
are expecting them cause a
runtime error
iHelp
Other
Related iHelp does not navigate 12-1SX7TI5 12-1SJ5MIZ 8.1.1.2
correctly
Life Sciences
Activity
Clinical Manager
Position Rollup does not always 12-1VAT6K9 12-1OK0UBP 8.1.1.2
function properly
Users are unable to copy Site 12-1V3K6BX 12-1K824E1 8.1.1.2 Yes, see
Vists records “Instructions for
FR 12-1V3K6BX”
on page 719.
Trip Reports
Users are unable to change the 12-1UVNYZX 12-1NVVH35 8.1.1.2 Yes, see
Trip Report Status field in the “Instructions for
Clinical Trip Report view FR 12-1UVNYZX”
on page 720.
Marketing
Campaigns
Prospect import does not check 12-1TK666M 12-1TK665T 8.1.1.2
for matches against existing
contacts
Events
When users navigate to Site Map 12-1S2F1F1 12-1RRBFQ9 8.1.1.2
> Events (create one or open
one) > Resources > Staff, add
two records, delete one of the
records, save the remaining
record, an error message
displays and the deleted record
comes back
Marketing Server
Integration to Marketing 12-1TK47RK 12-1KJP2WG 8.1.1.2
Outbound Web Services does not
support enterprise SSO
Other
Mobile Solutions
Handheld for Windows
During Handheld 12-1TXTR5T 12-1THO6UJ 8.1.1.2
synchronization, the logging of
URLs exposes username/
password combinations in web
server logs
Other
The DB_LAST_UPD and 12-1S1Y0MZ 12-1L0YDDK 8.1.1.2
DB_LAST_UPD_SRC columns are
listed twice in the update
statement
Store-and-Forward
Messaging
ACR 444 provides the following 12-1U087M8 12-1O2HQ4R 8.1.1.2
enhancements: Provides a utility
for administrators to act on
failing Store and Forward
transactions. Enhances logging
capabilities. (Server)
Sales
Other
Manually-created revenue items 12-1U0A7J0 12-1SW88FV 8.1.1.2
within accounts are not updated
when the account is changed by a
user who has not created the
revenue item
Service
Logistic Manager
Error invoking service 'Inventory 12-1V7FE6F 12-1UH87R1 8.1.1.2
Transaction', method
'SetTxnDetailsFromTxnSet’
Siebel eMail
Response
General
For draft emails, the status can 12-1U5TWJC 12-1U5TWIL 8.1.1.2
be changed to any value and
contacts can be removed or
added
With templates, the subject line 12-1QK0UEL 12-1FCL4BH 8.1.1.2 Yes, see
and body text are not replaced “Instructions for
according to the template FR 12-1QK0UEL”
selected on page 720.
Siebel Self-Service
Common
Miscellaneous
Travel &
Transportation
Events Execution
ACR 494: Provides Event Check 12-1S9QL59 12-1S9QL3Z 8.1.1.2 Yes, see
enhancements and BEO Report “Instructions for
functionality for the Siebel Travel ACR 494” on
& Transportation application page 291.
Other
For ACR 450 and ACR 488, the 12-1UI8ZAR 12-1UI8Z9H 8.1.1.2
sia_options.txt file is missing
several views for licensing
User Interface
Administration
Successful login does not reset 12-1UQU5DX 12-1U5V2WZ 8.1.1.2
IsStandaloneWebClient Profile
Attribute
Controls
After 8.1.1 QF0025 has been 12-1UW60LO 12-1UI8T7X 8.1.1.2
applied, the implicit save function
does not work on form applets
Navigation
If users enter a query of more 12-1SC96YJ 12-1OA585D 8.1.1.2
than two characters, when they
press the TAB key, the focus does
not move to the GO button
Other
Exporting results from queries 12-1V3VLLZ 12-1UU5KSH 8.1.1.2
that use calculated fields omits
valid records
Popups/Pick Lists/
MVG/Shuttle
Internet Explorer 7 crashes when 12-1UI7VQC 12-1UGQKML 8.1.1.2
users open a popup window on
top of an MVG
Web Service
Other
Provides Web service access 12- 12-1STBMTB 8.1.1.2
through the Mobile Web Client to 1STBMWW
other local desktop applications
(ACR 492)
Table 19 lists the Change Requests that were resolved in the 8.1.1.1 Fix Pack.
Call Center
CTI
The Chat transfer command 12-1S99AEF 12-1S99ADV 8.1.1.1
defined in multichannelC.def is
incorrect
Other
Redesigns the Email Response UI 12-1RB07UI 12-1RB07T9 8.1.1.1 Yes, see
so that replying to an incoming “Instructions for
email and forwarding a sent FR 12-1RB07UI”
email display in the same format on page 733.
Comm Media
Energy
Order Management
Other
Users are unable to add a 12-1O05GRF 12-1M6UUMK 8.1.1.1
promotion to the Shopping Cart
with default options selected
Connectors / EAI
Other
All messages sent to JMS go as 12-1SBSPDP 12-1RAJ07R 8.1.1.1
BytesMessage, regardless of
whether the data is String/
Binary
Consumer Sector
Deductions
ACR 480: Claim Resolution time 12-1SPXYJS 12-1SPXYHT 8.1.1.1 Yes, see
value changes after the record is “Instructions for
refreshed ACR 480” on
page 280.
Other
When users create a new plan, 12-1TXTRDT 12-1TXTR4J 8.1.1.1
the application crashes
ACR 480: Delist dates are not 12-1TSQ0BX 12-1TSQ0AH 8.1.1.1 Yes, see
being updated in the ADL applet “Instructions for
FR 12-1TSQ0BX”
on page 734.
ACR 480: The Seed.inp file is 12-1TAR916 12-1T9S0ZN 8.1.1.1 Yes, see
missing for seed data import on “Instructions for
JPN ACR 480” on
page 280.
ACR 480: Flags (A/O/P) should 12-1SOZJYK 12-1SOZJUX 8.1.1.1 Yes, see
retain their values if the Account “Instructions for
Distribution record exists (ADL) ACR 480” on
page 280.
ACR 480: Users are able to save 12-1S87KF6 12-1S87KDR 8.1.1.1 Yes, see
Delist date > Product end date “Instructions for
in Authorized Category Product ACR 480” on
(ADL), but they should receive page 280.
an error message and be
preventing from doing this
ACR 480: List Date and Delist 12-1S87KBC 12-1S87K9X 8.1.1.1 Yes, see
date do not get updated in the “Instructions for
Authorized Categories Product ACR 480” on
middle applet (ADL) page 280.
ACR 480: The List and Delist 12-1RYK5JX 12-1RYK5II 8.1.1.1 Yes, see
dates are not being populated in “Instructions for
the ADL applet ACR 480” on
page 280.
ACR 358: Provides support for 12-1RV6IE1 12-1JGEFDN 8.1.1.1 Yes, see
the new out-of-the-box “Instructions for
integration between Siebel and ACR 358” on
EBS OTM. Integration points page 41.
include account, products,
pricing, funding (accruals),
shipments, promotions,
deductions, and payments.
ACR 480: When users navigate 12-1RSAYQS 12-1RSAYPD 8.1.1.1 Yes, see
to Site Map > Adminstration - “Instructions for
Authorized Distribution List, click ACR 480” on
on the 2LNV detail list, navigate page 280.
to the Account Product applet,
click New, select a product, and
then click the Delete Selected
button, they receive an "end of
file occurred” error message
Retail Objectives
ACR 480: When users navigate 12-1SN1X8G 12-1SMKW6N 8.1.1.1
to Site Map > Account >
Merchandising Location, create a
location, navigate to the Product
applet (bottom applet), click the
Select category button, click the
Query button on the Add Product
dialog box, and then click the
Catalog picklist, the Catalog
picklist shows Categories and
not Catalogs
ACR 480: Within Accounts, when 12-1RUPL7F 12-1RUPL60 8.1.1.1 Yes, see
users select a account that has “Instructions for
distribution added, navigate to ACR 480” on
Merchandising Location > Create page 280.
a Location, add a product in the
Product bottom applet, navigate
to the Account Distribution
applet and delete that they
added earlier, when users
navigate back to Merchandising
Location > Product bottom
applet, the deleted product still
displays
Trade Promotions
ACR 480: Provides a system 12-1TXBBQB 12-1TXBBP1 8.1.1.1 Yes, see
reference called "Trade “Instructions for
Promotion Extended" to allow ACR 480” on
customers to implement the new page 280.
functionality in ACR 480 by
setting the value to TRUE or
keep the Trade Promotions
functionality that existed prior to
ACR 480 by setting the value to
FALSE
ACR 480: The Team field is blank 12-1S6A16E 12-1S6A14X 8.1.1.1 Yes, see
for a new plan “Instructions for
ACR 480” on
page 280.
ACR 480: Within Object Explorer, 12-1S2EV5J 12-1S2EV2Z 8.1.1.1 Yes, see
when users query for the CPG “Instructions for
Plan Account Plan Team, ACR 480” on
navigate to User Properties, page 280.
change the value of Add Account
Team from Y to N, query for the
CPG Plan Account Promotion
Promotion Team and also change
the value of Account Team from
Y to N, after the user compiles
the object, launches the
application, navigates to Plans,
creates a new plan with account
and period information, and then
checks the Plan Team field, it is
not populated with the login ID
ACR 480: When users create an 12-1S2EUXT 12-1S2EUVJ 8.1.1.1 Yes, see
account with team and “Instructions for
organization information, ACR 480” on
navigate to Plan and create a page 280.
plan with the account set as the
account that they just created,
add period information, set the
organization to default, and
check the Plan Team
information, it should be
populated with the login ID
information, but this field is
empty. This issue also occurs
with Promotions.
ACR 480: Within the Authorized 12-1RYK5LL 12-1RYK5K6 8.1.1.1 Yes, see
Category Product tab, the “Instructions for
product is not bounded ACR 480” on
page 280.
ACR 480: When users copy an 12-1RYK5G3 12-1RYK5EO 8.1.1.1 Yes, see
account in the Authorized “Instructions for
Account applet, the Primary flag ACR 480” on
is not checked for Account Team page 280.
ACR 480: Within the Promotion 12-1RXLGQL 12-1RXLGP5 8.1.1.1 Yes, see
screen > Category pick applet, “Instructions for
the Query button does not work ACR 480” on
page 280.
ACR 480: When users create an 12-1RV785V 12-1RV784G 8.1.1.1 Yes, see
account, log out of the “Instructions for
application, log back in, navigate ACR 480” on
to the Plan screen, click the New page 280.
button, enter a plan name,
navigate to Plan Team, verify
that the MVG does not display
any values, navigate to the
Account field, click the MVG,
search for the account that they
just created, click OK, and save
the record, the Plan Team field is
not populated with the account
that they just tried to add
ACR 480: When users create an 12-1RV782J 12-1RV7811 8.1.1.1 Yes, see
account with two members as “Instructions for
the Plan Team (for example, ACR 480” on
CTRIPP and RMARCKS, log out of page 280.
the application, log back in as
the RMARCKS user, create a plan
with account and period
information, and check the Plan
Team information, the user
RMARCKS is set as the primary
user, but the application allows
the user to change the Primary
flag
ACR 480: Within Plan List > High 12-1RUOZX8 12-1RUOZWH 8.1.1.1
Level Planning, when users
create a plan and click Simulate,
they receive an error message
ACR 480: Within Account screen 12-1RT9Z51 12-1RT9Z3C 8.1.1.1 Yes, see
> Distribution applet, the “Instructions for
Distribution Code, Sequence ACR 480” on
Code, and Retail Order fields are page 280.
missing
ACR 480: Delist date is updated 12-1RT9Z31 12-1RT9Z1M 8.1.1.1 TYes, see
with the effective end date of the “Instructions for
product ACR 480” on
page 280.
ACR 480: Within Account screen 12-1RT9Z16 12-1RT9YZW 8.1.1.1 Yes, see
> Distribution applet, the “Instructions for
Auditable and List Date fields are ACR 480” on
missing page 280.
ACR 480: The Auditable and List 12-1RT9YW4 12-1RT9YUP 8.1.1.1 Yes, see
Date fields are missing from the “Instructions for
ADL applet ACR 480” on
page 280.
ACR 480: The Update Delist Date 12-1RT9YU6 12-1RT9YSN 8.1.1.1 Yes, see
button should be read-only in “Instructions for
Query mode in Product ACR 480” on
Administration screen page 280.
ACR 480: Within the Target list 12-1RT9YSE 12-1RT9YQZ 8.1.1.1 Yes, see
applet, Copy ADL functionality “Instructions for
does not work properly ACR 480” on
page 280.
ACR 480 provides the following 12-1RHR1SG 12-1RKLYHL 8.1.1.1 Yes, see
enhancements: “Instructions for
ACR 480” on
■ Resolves key connection
page 280.
gaps between core
processes: marketing and
trade management, trade
management and retail
execution
■ Significantly enhances
usability across trade
management in Siebel
applications.
Customer Order
Management
Configurator
Order Management
Batch Validate does not give 12-1TK9032 12-1T7DFU1 8.1.1.1
expected output for incomplete
quotes or orders
Orders
The SIS OM PMT Service's 12-1QMFLED 12-1QL0ID7 8.1.1.1
Synchronize method leaves
rogue cursors open, which
consumes system resources
Pricer
When users accept an upsell 12-1SF7G9Z 12-1RZJE8H 8.1.1.1
recommendation product on an
order, the following error
message appears: Error invoking
service '<?>', method '<?>' at
step '<?>' (SBL-BPR-00162)
Products
Data Quality
Other
In Siebel 8.1.1, Data Quality 12-1STTNB0 12-1PCDF0P 8.1.1.1
does not work as expected if
both DeDup and DataCleansing
are enabled
Financial Services
Other
Screen:
Views:
Screen:
Views:
Other-Retail Finance
Provides Siebel Financial 12-1S987PV 12-1QT7XTB 8.1.1.1 Yes, see
Services Customer Order “Instructions for
Management for Banking ACR 467” on
functionality (ACR 467). page 150.
General
Access Control
Application
Deployment Manager
HTTP deployment of the Rules 12-1QODT6O 12-1PZOO3C 8.1.1.1
engine data type fails
ACR 456: Within the transaction 12-1TXC0BL 12-1TXC0A2 8.1.1.1 Yes, see
log, the time stamp is not correct “Instructions for
for imported and exported files ACR 456” on
(Linux-specific error) page 97.
ACR 456: When users attempt to 12-1TETVPG 12-1TETVNL 8.1.1.1 Yes, see
import an empty csv file, they do “Instructions for
not receive an error message ACR 456” on
page 97.
ACR 456: When users attempt to 12-1SUAR8D 12-1SREMIN 8.1.1.1 Yes, see
export an Assignment Rule that “Instructions for
does not contain data in the child ACR 456” on
applet, they should receive an page 97.
error message
ACR 456: Within the Admin- 12-1SSUPOB 12-1SSUPNP 8.1.1.1 Yes, see
Group > Skill view, the Import “Instructions for
Data Skill button is not required FR 12-1SSUPOB”
on page 733.
ACR 456: When users attempt to 12-1SSUPFB 12-1SSUPCK 8.1.1.1 Yes, see
import a csv file that does not “Instructions for
contain names or locatios in the ACR 456” on
Import dialob box, the incorrect page 97.
error message displays
ACR456: When users omit skill 12-1SSUPET 12-1SSUPE3 8.1.1.1 Yes, see
information from a csv file, they “Instructions for
do not receive an error message ACR 456” on
when they attempt to import the page 97.
csv file
ACR 456: The dialog box name 12-1SSCJTW 12-1SSCJQY 8.1.1.1 Yes, see
for Import displays as Position “Instructions for
Skill Export but it should be FR 12-1SSCJTW”
Position Skill Import on page 733.
ACR 456: When the Siebel 12-1SREMAH 12-1SREM9V 8.1.1.1 Yes, see
Server and the Call Center “Instructions for
application reside on different ACR 456” on
servers, users receive the page 97.
following error message when
they attempt to import a file: We
detected an Error which may
have occurred for one or more of
the following reasons:
ACR 456: When users export 12-1SPXSIK 12-1SPXSI3 8.1.1.1 Yes, see
rules that have had some criteria “Instructions for
and criteria values added to FR 12-1SPXSIK”
them, enter numeric values for on page 732.
Assignment Scores files with the
operation to be updated into the
csv file, and then import the
edited csv file into Call Center,
the score field is not updated,
and no error code or error
message is generated in the log
file
ACR 456: The status of imports 12-1SPXSHM 12-1SPXSGV 8.1.1.1 Yes, see
does not change, regardless of “Instructions for
whether the import succeeded or ACR 456” on
failed page 97.
Audit Trail
The audit trail is not in sync with 12-1TE6CIJ 12-1TE6CHR 8.1.1.1
server from mobile client
Business Rules
Only one 12-1TARV4S 12-1SW8CMD 8.1.1.1
knowledgebase:module
combination at a time is active
The Data Validation Engine is not 12-1OVTT1V 12-1NJKYC7 8.1.1.1 Yes, see
called correctly on the “Instructions for
PickRecord event, and rules are FR 12-1OVTT1V”
fired incorrectly on page 729.
Calendar
With Internet Explorer 8, a 12-1SJ56UP 12-1SJ56TU 8.1.1.1
double border appears around
calendar appointments
Correspondence
Custom Contact / Proposal 12-1QMG1J3 12-1P81NR1 8.1.1.1
objects do not generate properly
Global/Multilingual
LOV
Adds translations for features 12-1S5T3K5 12-1S5T3JL 8.1.1.1
and fixes in the Siebel 8.1.1.1
Fix Pack
Installation
Siebel Enterprise Server patch 12-1U0CAEA 12-1TARCGM 8.1.1.1
installation is blocked on the
Linux platform
Office
Provides support for Microsoft 12-1N1Q81D 12-1IDNOO9 8.1.1.1 Yes, see
Office 2007 with Document “Instructions for
Server and Siebel Search (ACR FR 12-1N1Q81D”
409) on page 721.
Other
After Siebel 8.0.0.2 QFA205 has 12-1TK99SO 12-1SM30JX 8.1.1.1
been apllied, the Dedicated
Client crashes when the
Business Service Invoke method
is called
oInputs.SetProperty("HTTPCertA
uthority",
"CN=DPTIPSEC,DC=dwpptp,DC
=londondc,DC=com");
oInputs.SetProperty("HTTPCertS
erialNo",
"1107BA79000000000002");
PIM Server
Integration
If a PIMSI share is unavailable at 12- 12-1MQCFNM 8.1.1.1
startup, the PIMSI Engine 1MQCM12
component dies
Platforms
Applications do not switch from 12-1TK84BZ 12-HFIYXK 8.1.1.1
http to https when
SecureBrowse = TRUE, HTTPS
Remote
ACR432: A blank Error message 12-1U087L1 12-1S7PRXF 8.1.1.1
displays when users try to
launch multiple Mobile Web
Client Sessions
Report Designer
The BI Publisher Report applet 12-1SQFISM 12-1SQFIRV 8.1.1.1
cannot be closed using the X icon
Reports Server
Within the Schedule a Report 12-1TCP6D1 12-1TCP6BM 8.1.1.1
dialog box, when users click the
Cancel button, the window does
not close
When users click the BIP icon > 12-1U5S3EF 12-1U5S3DL 8.1.1.1
Account List Report link, the
application crashes
Provides the following fixes and 12-1SW88PJ 12-1SW88O5 8.1.1.1 Yes, see
enhancements for BI Publisher: “Instructions for
BI Publisher
■ Corrects an issue where
Enhancements”
different users receive the
on page 441.
same report output after
scheduling
Search
ACR 403: Users cannot open the 12-1RBZCK1 12-1NCHNGC 8.1.1.1 Yes, see
search center from the All “Instructions for
Opportunities page ACR 403” on
page 41.
ACR 439: After Search Center is 12-1S7PQRR 12-1R49VTZ 8.1.1.1 Yes, see
closed, Last Find and its search “Instructions for
criteria are not retained FR 12-1S7PQRR”
on page 729.
ACR 452: After ACR 452 has 12-1TARBRC 12-1TARBQD 8.1.1.1 Yes, see
been set up, when users launch “Instructions for
Call Center, navigate to ACR 452” on
Administration - Search > page 95.
Search Index Settings and
attempt to index a Business
Component (such as the Contact
BC), the feed files are not
generated, and SCCObjMgr_enu
shows the following error
message: SBL-SRH-00186: An
unrecognized adapter class
'CSSOSESAdapter' was specified
for the search engine 'OSES'
ACR 452: Provides Siebel Search 12-1TARYMD 12-1T0KYST 8.1.1.1 Yes, see
support for languages other than “Instructions for
ENU ACR 452” on
page 95.
ACR 452: Adds the following text 12-1SX7AHU 12-1SX7AGD 8.1.1.1 Yes, see
boxes for Siebel Search: “Instructions for
ACR 439” on
■ All these words
page 90.
■ Any of these words
■ Exact Phrase
Security
Server Infrastructure
Within Admin - Server 12-1TB8XS8 12-1TB8XQI 8.1.1.1
Configuration, when users click
Server, query for Loyalty Object
Manager (ENU) on the
Components applet, select all of
the logs, and change the log
level to 5, save the change, and
navigate to the Enterprise, view,
they receive the following error
message: We detected an Error
which may have occurred for one
or more of the following reasons:
SBL-ADM-02049: There is no
connected server targeted for
that command.
Siebel Sync
SSSE Embedded Outlook 12-1QYIVKD 12-1NSKQ0N 8.1.1.1
Calendar fails on IE7
Task UI
Tools / Configuration
Using the Edit Web Layout menu 12-1U57ONN 12-1TYAW7D 8.1.1.1
command in Siebel Tools causes
Siebel Tools to exit
Upgrade
The datachk - Codepage tool 12-1RA1UL7 12-1RA1UJN 8.1.1.1
cannot handle multiple
repositories
Web Framework
Client-side logging does not 12-1Q3N50U 12-HPOMO0 8.1.1.1
perform correctly
Workflow
Upgrading or editing worflow 12-1TYBITJ 12-1PILZD3 8.1.1.1
processes resets properties for
other steps in the process
Life Sciences
Activity
When users try capture 12-1T9SI6C 12-1T9SI5L 8.1.1.1
signatures more than once in a
particular session, the
application crashes
Data Migration
Incorrect transaction status is 12-1R75OVY 12-1Q72AR6 8.1.1.1
displayed in the sender's "Sent
Samples" view for records
migrated from previous Siebel
Life Sciences application
releases
Other
Adds all of the 8.1.1 views to the 12-1TENX5R 12-1TENX4H 8.1.1.1
sia_options.txt file
Samples
Within the Pharma application 12-1TS6L62 12-1TS6L3P 8.1.1.1
Contacts > My Contacts view,
the Sample Dropped and
Requested applets should be
read-only and have their Add
buttons disabled when invalid
data is entered
Loyalty
Loyalty Customer
Portal
Updates Siebel Loyalty error 12-1QYIA05 12-1QDFKTJ 8.1.1.1
messages to provide more
detailed information about the
errors
Loyalty Engine
If accrual transactions with 12-1U5SIWR 12-1U5SIW7 8.1.1.1
expired points are canceled, the
point balance goes negative
Loyalty Manager
If accrued points have already 12-1RVNZS9 12-1RVNZQZ 8.1.1.1
been consumed, the transaction
cancellation should take the next
available accrual points
Auto creation of point blocks for 12-1QYI9WB 12-1Q3NIC7 8.1.1.1 Yes, see
prepaid partner is not working “Instructions for
FR 12-1QYI9WB”
on page 726.
Marketing
Campaigns
When upgrading from Siebel 12-1S2FFRD 12-1S2FFQT 8.1.1.1 Yes, see
application versions prior to “Instructions for
8.1.1 to Siebel 8.1.1 the FR 12-1S2FFRD”
segment trees that are more on page 730.
than one level deep with splits
are distorted
Events
Marketing Server
Waves are assigned a single 12-1QY0YIW 12-1P81NNZ 8.1.1.1
record if the first wave setting
has 0% allocation
When contact planning rules are 12-1QNF549 12-1OD2S8L 8.1.1.1 Yes, see
defined for treatment channels, “Instructions for
mutual exclusion cannot be FR 12-1QNF549”
guaranteed completely on page 735.
Other
When users create an import 12-1R84VR3 12-1R7N6Z2 8.1.1.1
job, activate it, and then click
the Deactivate button while
processing is occurring, they
receive the following error
message: The selected record
has been modified by another
user since it was retrieved.
Please continue.(SBL-DAT-
00523)
Programs
When users create a campaign 12-1S99AJC 12-1S99AIB 8.1.1.1
and associate segment, drag and
drop the Wait shape, attach a
constrained connector to the
campaign and then attempt to
attach the other end to the Wait
shape, they receive the following
error message: "Field 'Next
Stage Connector' does not exist
in definition for business
component 'Program Flowchart
Next Camp Connector'
Mobile Solutions
Handheld for Windows
Siebel application does not 12-1SW7Q25 12-1SREMMN 8.1.1.1
install on WM 6.1.4 devices, and
users receive an error message
stating that there are not
sufficient system permissions
Other
Wireless
When users create line items 12-1Q06NX7 12-1JJHDHH 8.1.1.1
within sales orders, duplicate
records are added
Partner
Relationship
Management
Other
Users receive error messags 12-1SJNT7T 12-1SEQDDV 8.1.1.1
when they try to qualify a
prospective partner in the
Administrator Partner screen
Partner Manager
'Expertise' values are removed 12-1RAJ7UZ 12-1QZYA3H 8.1.1.1
after qualifying the Prospective
Partner
Partner Portal
Within the PRM Manager 12-1S8QDC7 12-1S8QDAZ 8.1.1.1
application, when users click
Shopping Cart, they receive the
following error message: We
detected an Error which may
have occurred for one or more of
the following reasons:
Unterminated value for attribute
'' in XML tag ''.(SBL-UIF
Public Sector
Case Management
Under Verification Items list 12-1QRQ64V 12-1PLGBAO 8.1.1.1
applet, when users verify one
item and leave another one as
unverified, they are not allowed
to change Case Sub-Status
under the HLS Case Form applet
but they are allowed to change
Sub-Status from Edit Application
Menu-Change
Other
Creates a source code .jar file 12-1TXC3HB 12-1T30JOF 8.1.1.1
Sales
Forecasting
Opportunities
When users use the scroll bar to 12-1REV098 12-1QMFJR1 8.1.1.1
navigate to records within
Opportunity Record, data is not
saved in Revenue Line Items
Service
Other
The Action Business Component 12-1RBZC49 12-JX5I6Z 8.1.1.1 Yes, see
is hard coded to set the status of “Instructions for
an activity to Done when the FR 12-1RBZC49”
Done flag is checked or set to on page 737.
True
Scheduling
GetElapsedBusinessTime API 12- 12-1DR0EUR 8.1.1.1
returns an incorrect result when 1Q2NN4M
there are multiple time zone
entries
Siebel E-
Commerce
Assets
Shipping and tax amounts are 12-1SW8FCN 12-1SW8FBB 8.1.1.1
not included in the Open Order
Total field
Configurator
With a large number of users 12- 12-1RNY6ZZ 8.1.1.1
running the application 1ROWYK3
concurrently, users receive an
error message when they try to
configure the product
Miscellaneous
Self-Service Applications: Users 12-1T3ZEBN 12-1T3ZEAB 8.1.1.1
receive an error message when
they try to compile the
ErrorPageDirector.jsp file
Siebel E-
Commerce for
Comms
Assets
Within the Self-Service 12-1SSD2GO 12-1SSD2F8 8.1.1.1
application, Contact and Address
information is not refreshed
according to the account
selected in the Shipping Details
page
Configurator
A memory leak occurs 12-1SEPN3K 12-1SEPN2D 8.1.1.1
Miscellaneous
Provides a source code jar file to 12-1SXPC2R 12-1SXPC27 8.1.1.1
allow for overwrites
New Service
In new service activation (CP) 12-1QJ2KKN 12-1QJ2KJA 8.1.1.1
scenario, within the Products
page, the Gallery view should
display but the List view displays
instead
Order Status
When users upgrade from one 12-1REVTLR 12-1REVTL7 8.1.1.1
promotion to another, the data in
the order is incorrect
User Accounts
For a secondary B2B user, the 12-1QDRH42 12-1Q9ICDR 8.1.1.1
Add New button is disabled for
Account Address in the Shipping
Details page
Siebel eMail
Response
General
Siebel E-Support
Miscellaneous
A memory leak occurs during 12-1R1VRQO 12-1R1VRQ3 8.1.1.1
Order Management scenarios
Service Request
After solution types have been 12- 12-1U0DU1B 8.1.1.1
created in Call Center, indexed, 1U5UKMD
and then searched for, when
users invoke the Self-Service
application, navigate to Support
> KM pages, and click on FAQ
under the Popular Support
Information section, they
receive the following error
message: "No solution is found
based on your search criteria"
Deployment and
Packaging
The 811SelfService.ear data- 12-1RAJ02I 12-1RAJ01X 8.1.1.1
source.xml file has an entry for
Siebel Host that causes the
following error message: JBO-
30003: The application pool
(oracle.apps.ss.base.model.secu
rity.SessionAMLocal) failed to
checkout an application module
Miscellaneous
Users cannot navigate to the E- 12-1T30KEU 12-1T30KE9 8.1.1.1
Support tab in the Self-Service
Public Sector application
User Accounts
Within the My Account > 12-1T6EAI0 12-1T6EAGP 8.1.1.1
Company > Contacts page,
users cannot add new contacts
by clicking the Add button
User Management
When users log in as a B2B 12- 12-1PBY7ZX 8.1.1.1
primary user, login as b2b 1QDRWP8
primary user, navigate to
Products > Order Status page,
select an account within the
Search dialog box, click the
Contact Name LOV to display the
Contact dialog box, they receive
the following error message:
Mandatory view criteria field(s)
Account Id missing in ContactVO
Travel &
Transportation
Other
ACR 488: When users create 12-1T5W51N 12-1T5W513 8.1.1.1
multiple quotes for multiple
properties, they receive an error
message
ACR 488: Provides Histories and 12-1TK3LUK 12-1QPT2Q7 8.1.1.1 Yes, see
Futures functionality “Instructions for
ACR 488” on
page 291.
ACR 450 provides the following 12-1R8LRF4 12-1QJJCQN 8.1.1.1 Yes, see
enhancements: “Instructions for
ACR 456” on
■ Menus and Packages
page 97.
■ Function Space Displays
■ Inventory Display
Enhancements
ACR 488: Provides Histories and 12-1QPT2UA 12-1QPT2T1 8.1.1.1 Yes, see
Futures functionality for the “Instructions for
Siebel eHospitality application ACR 488” on
page 291.
Universal
Customer Master
Other
■ Restructures the
ACR437_UCM.zip directory
ACR 437: Provides the ability to 12-1SJO2V0 12-1M4CI03 8.1.1.1 Yes, see
expose CDI WebServices for all “Instructions for
CRUD operations on key entities ACR 437” on
such as Account, Contact, page 89.
Household, Financial Account,
and so forth
ACR 437 error message strings 12-1RSS7TV 12-1RPEN89 8.1.1.1 Yes, see
are not provided for languages “Instructions for
other than ENU ACR 437” on
page 89.
Publish/Subscribe
User Interface
Controls
Provides support for Internet 12-1RAJFVM 12-1RAJFUD 8.1.1.1.
Explorer 8 on Windows Vista.
ACR 422 provides the following 12-1PFQEKX 12-1N3ZXFY 8.1.1.1 Yes, see
enhancements: “Instructions for
ACR 422” on
■ Adds missing text for ALT
page 45.
strings and other text read
by screen readers
■ Provides an announcement
of row and column identifiers
in list applets and allows the
column used for the row
identifier to be configurable
Navigation
With Internet Explorer 8, the 12-1SD8N3Z 12-1RV6HKZ 8.1.1.1
browser's Back and Forward
buttons do not work
Other
Querying on the Account applet 12-1U4HH59 12-1TK7X5V 8.1.1.1
generates an extra query on the
Action Business Component
Popups/Pick Lists/
MVG/Shuttle
When users try to undo a query 12-1T6DTOD 12-1T6DTMX 8.1.1.1
after typing in a set of
characters, they receive the
folllowing error message:
"Method UndoRecord is not
allowed here. (SBL-UIF-00348)”
Web Service
Other
Within Siebel Tools, when users 12-1RH8IMZ 12-1PG7NLN 8.1.1.1
navigate to File > New Object >
EAI tab > Web Service, and
display the WSDL Import Wizard
dialog box, when users select a
locked project, select the Adobe
LiveCycle 8.1 WSDL file, and
click Next, they receive the
following error message: There
are no web service definitions to
be generated.(SBL-EAI-04340)
1 Within Siebel Tools, edit Signature Capture Applet ( in this case Order Signature Capture) to use
class as “CSSFrameFSSign” instead of “CSSFrame”.
2 Edit the corresponding BC to have “Signature” field. The name of the BC field introduced for
storing signature data must be “Signature” only.
The applet Browser script should refer to the Signature field to store/read the signatures from
the database table.
3 Run “genbscript command” to generate all java script for all browser script.
4 Within the Repository Objects panel, select Business Components, and add a new record with the
following details.
❏ Table: S_EVT_ACT
6 In the Repository Object panel, select Business Components, select Fields, and add a new field
with the following details:
❏ Join: S_EVT_ACT_LOYX
❏ Column:
8 Create a new link between the LOY Member business component and the LOY Merge Action
business component:
❏ Source Filed: Id
9 Add the LOY Merge Action business component to the LOY Member business object:
b Query for the LOY Member business object and lock it.
c Add a new record in Business Object Components with the following details
4 Query for the LOY Redemption Voucher Reissue Task UI and activate it.
2 Select "LOY Member" under Business Object, add "LOY Member Point Balances VBC" as Business
Object Component (link is not required) and compile the SRF.
3 Select "LOY Member Services" under Business Service, add "CalMemPointBalances" to Business
Service Method (no input/output arguments required) and compile the SRF.
4 Under View, select "LOY All Member View", "LOY All Members Across Organization View", "LOY
Member Detail View" and "LOY My Member View", add "LOY Member Point Balances Task Group"
under View Task Group list and compile the SRF.
9 In the Responsibilites applet, click New, and add the Siebel Administrator and Loyalty
Administrator responsibilities.
1 Within Siebel Tools, navigate to the LOY Members project, and lock it.
❏ Table: S_LOY_TXN
❏ Column: MEMBER_ID
❏ Column: VOUCHER_ID
4 Query for the LOY Member business object and lock it.
3 In the Field section of the LS Document Tracking business component, create a new record with
the following values:
6 Within the Siebel application, navigate to Site Map >Administration - BI Publisher Reports >
Reports - Standard Templates.
7 Create a new report wcalled Protocol Level Document Tracking and associate it with the template
(.rtf file) available for that report. Select Output type as "All".
8 In the XLIFF field, upload the xliff file corresponding to the report.
9 In Report Standard Template Registration Admin View > Translations tab, create a new record
and pick the desired language and report name for which the translation is required.
10 In the Integrations Objects tab, navigate to the Integration Object Name field and query for "BIP
LS Protocol Document Tracking"
11 Naviate to Administration-BIP Report > View Association, and associate view where you want to
see the report.
3 In the Field section of the LS Document Tracking business component, create new record with
the following values:
6 Within the Siebel application, navigate to Site Map > Administration - BI Publisher Reports >
Reports - Standard Templates.
7 Create a new report and associate it with the template (.rtf file) available for that report. Select
Output type as all.
8 In the XLIFF field, und upload the xliff file corresponding to the report.
9 In the Translations tab, query for "BIP LS Region Document Tracking" in the Integration Object
name field and select it.
10 Within Report Standard Template Registration Admin View > Translations tab, create a new
record and pick the desired language and report name for which the translation is required.
11 Navigate to Administration-BIP Report > View Association and associate the view where you want
to see the report.
3 If the field "Login User field does not already exist, within the Field section of the LS Document
Tracking business component, create a new record with the following values:
5 Unzip the zipped file, import "BIP LS Clinical Protocol Site.sif", and compile the SRF.
6 Within the Siebel application, navigat to Site Map >Administration - BI Publisher Reports->
Reports - Standard Templates.
7 Create a new report and associate it with the template (.rtf file) available for that report. Select
Output type as all.
8 In the XLIFF field, upload the xliff file corresponding to the report.
9 Navigate to Report Standard Template Registration Admin view > Translation tab create a new
record and pick the desired language and report name for which the translation is required.
10 In the Integrations Objects tab, navigate to the Integration Object Name field and query for "BIP
LS Clinical Protocol Site".
11 Navigate to Administration - BIP Report > View Association, and associate the view where you
want to see the report.
3 If the Login User field does not already exist, in the Field section of the LS Document Tracking
business component, create a new record with the following values:
❏ Alias: S_CL_PGM_APP_LS
b Navigate to Join Specification, and create a new record with the following values:
❏ Name: Application Id
d Within Object Browse, under Business Component, navigate to Field, and create a new record
with the following values:
❏ Name: Application Id
❏ Join: S_CL_PTCL_LS
❏ Column: PGM_APPLN_ID
f Within Object Browse, under Business Component, navigate to Field, and create a new record
with the following values:
❏ Join: S_CL_PGM_APP_LS
❏ Column: INDICATOR_CD
5 If you do not want to perform the manual steps detailed above, do the following:
7 Unzip the zipped file and import "BIP LS Clinical Protocol Site.sif".
8 Compile the SRF.
9 Within the Siebel application, navigate to Site Map >Administration - BI Publisher Reports->
Reports - Standard Templates.
10 Create a new report and associate it with the template (.rtf file) available for that report. Select
Output type as all.
11 In the XLIFF field, upload the xliff file corresponding to the report.
12 Within Report Standard Template Registration Admin View > Translations tab, create a new
record and pick the desired language and report name for which the translation is required.
13 In the Integrations Objects tab, within the Integration Object Name field, query for BIP LS
Clinical Protocol Site.
14 Navigate to Administration-BIP Report > View Association, and associate the view where you
want to see the report. Here we want to see the report in "Clinical Protocol Site List View",
"Clinical Protocol Site Manager's List View", and "Clinical Protocol Site All List View". So we
associate this view here.
3 If the Login User field does not already exist, in the Field section of the Clinical Protocol Site
business component, create a new record with the following values:
5 Unzip the zipped file, import the BIP_LS_Site_Enrollment_Status.sif, and compile the SRF.
6 Witin the Siebel application, navigate to Site Map > Administration - BI Publisher Reports >
Reports - Standard Templates.
7 Create a new report and associate it with the template hat with Template (.rtf file) available for
that report. Select Output type as all.
8 In the XLIFF field, click and upload the xliff file corresponding to the report.
9 Within Report Standard Template Registration Admin View > Translation tab, create a new record
and pick the desired language and report name for which the translation is required.
10 In the Integrations Objects tab, navigate to the Integration Object Name field, and query for BIP
LS Site Enrollment Status.
11 Navigate to Administration-BIP Report > View Association, and associate view where you want
to see the report.
3 Within the Object Explorer, navigate to the Applet tab, query for "Clinical Protocol Site Payment
Exceptions List Applet", and lock it.
4 In the Object browser, under Applet, click Control, and query for "NewRecord".
5 Change the value of the Method Invoked field from "ShowPopup" to "NewRecord".
4 Click the Upload button to upload the template to the BIP server.
5 Generate the MDV report, and view it in the LS Medical Product Issues RR view.
3 In the Field section of the LS Document Tracking business component, create a new record with
the following values:
❏ Calculated: LoginName()
6 If the Login User field does not already exist, create a new record with the following values in
the Field section of the Clinical Protocol Site business component:
❏ Calculated: LoginName()
8 Unzip the zipped file, import BIP Site Initiation By Site.sif, and compile the SRF.
9 Within the Siebel application, navigate to Site Map > Administration - BI Publisher Reports >
Reports - Standard Templates.
10 In the XLIFF field, click and upload the xliff file corresponding to the report.
11 Create a new report and associate that with the template (.rtf file) available for that report.
Select Output type as all.
12 In the Translations tab, query for "BIP Site Initiation By Site" in the Integration Object name field
and select it.
13 In the Translation tab, create a new record and pick the desired language and report name for
which the translation is required.
14 Navigate to Administration - BIP Report > View Association and associate the view where you
want to see the report.
2 Querying for the Clinical Protocol List Applet * applet, and lock it.
3 In the Object Explorer under Applet, select "Drilldown Object" and locate the Protocol object.
4 Update the "Source Field" with the value "Id" as shown in the first table below.
5 Repeat the Step 3 and Step 4 for the Protocol With Regions object (set Source Field = "Id" as
shown in the second table below.)
Name Protocol
Source Field Id
Source Field Id
■ LS Clinical Protocol
■ LS Pharma Common
■ LS Clinical Subject
■ LS Clinical Programs
■ LS Clinical Region
3 Within Object Explorer, navigate to Applet, and query for "Clinical Region List Applet".
4 In the Object Explorer under Applet, select List > List Column, and query for Field = Protocol
Title.
8 Under Applet, select Control, and query for "Field" = "Protocol Title".
2 Within Repository Objects panel, select Projects, query for the LOY Members project and lock it.
4 Within the Repository Objects Panel, select Business Components, and add a new record with the
following details:
❏ Table: S_EVT_ACT
6 Within the Repository Objects panel, within the Business Components section in the panel, select
field, and add a new field with the following details.
❏ Join: S_EVT_ACT_LOYX
❏ Column:
8 Create a new link between the LOY Member business component and the LOY Merge Action
business component:
a Select Link in the Repository Objects panel, and create a new record with the following details.
❏ Parent BC: LOY Member
❏ Source Filed: Id
9 Add the LOY Merge Action business component to the LOY Member business object:
b Query for the LOY Member Business object and lock it.
c Add a new record in Business Object Components with the following values
3 Add a new applet user property with the following name and value:
❏ Value: A number that should exceeds the maximum possible number of messages in the
product recommendation. For example, 100.
This example assumes that you are interested in filtering out ‘Products’ with Product Type: Technical.
The ‘Product Type’ field is mapped to the column ‘PROD_CD’ of the table ‘S_PROD_INT’ and it is a
LOV field with LOV type ‘PROD_CD’.
You need to add the following fields in the Cfg ISS Obj Details business component:
Field Name Calculated Calculated Value Join Column Type Text Length
Field Name Calculated Calculated Value Join Column Type Text Length
■ The calculated field above is required only if you are excluding an LOV field.
■ It is important to set the ‘Field User Property’ – ‘Cfg UI Field’ to TRUE for the field that you
want to exclude.
■ The S_PROD_INT’ join is already defined in the Cfg ISS Obj Details business component.
You need to add a User property to the ABO Bulk Request Action Component business component.
The format of the ‘BC User Property Name’ ‘Exclude:<Field Name>:LOV:<Field LOV Type>’.
The ‘User property value’ should specify the value that you would like to exclude. (In this case, it is
technical in this case. This is the value seen in the Siebel application.)
IMPORTANT: The <Field Name> specified here should match exactly with the filed name (new field)
specified in the BC - ‘Cfg ISS Obj Detailes’ (in our case it is Prod Type).
In case the field you are excluding is not an LOV, then the format of the ‘BC User Property Name’ is
‘Exclude:<Field Name’.
Compile the ABO Bulk Request Action Component and Cfg ISS Obj Details business components to
the .srf file.
After these changes the component pick applet should not show products of type ‘Technical’.
It assumes that you are interested in filtering out ‘Products’ with Dummy Field1: Dummy Value1.
Assume that the ‘Dummy Field1’ field is mapped to the column ‘DUMMY_COL’ of the table
‘S_PROD_INT’ .
You need to add the following fields in the Cfg ISS Obj Detailes business component:
Field Name Calculated Calculated Value Join Column Type Text Length
Add a field user property to this field with the following values:
Value: TRUE
You need to add a user property to the ABO Bulk Request Action Component business component:
2 Navigate Business Service User Properties and add a new property with the following values:
■ Type: SEARCH_FILEFORMATS
■ LIC: HTML
■ Translate: True
■ Active: True
2 Open the file and add the following two entries under the clsJLCMain section for Vertical Lines in
List Applet:
■ COLOR-VERTICAL-GRID-LINE: #EFEFEF;
■ JWIDTH-VERTICAL-GRID-LINE: 1px;
You can change the color and width for the preceding values; Hex Color code information is
available on the Internet.
3 Set the Calculated Value to 'Transaction Date' for the point expiry to be based on the transaction
date and not the transaction process date.
■ Column: CTRL_GRP_FLG
2 In the Campaign business component, add a new user property called Wave Id for Control Grp
and set the value as ‘Y’.
4 In the physical layer, under the S_CAMP_CON table, right-click, select Add New Object > Physical
Column.add a new column with the following values:
■ Type: varchar
■ Nullable: True
5 In the physical layer, navigate to Campaign Promotion, and drag the new column added to the
business model and mapping layer (to OLTP Campaign Promotion).
6 Drag the new field in the business layer to the presentation layer (under Marketing Contacts >
Campaign History (Transactional Database)). You can add this new field to any target level.
from:
VisitTemplateDateFieldName: OriginalTemplateDateFieldName
to:
Input Argument:PropertyName
VisitTemplateDateFieldName: VisitTemplateDateFieldName
2 Query for "Clinical Protocol Position to Region Position Map1" in Integration Object Map.
a Within Target Field Name, query for Region Position Assignment Type.
4 Query for "Clinical Protocol Position to Site Position Map1" in Integration Object Map.
b Within Target Field Name, query for Site Position Assignment Type.
c Delete the record.
5 Query for "Clinical Site Position to Protocol Position Map1" in Integration Object Map.
b Within Target Field Name, query for Protocol Position Assignment Type.
6 Query for "Clinical Site Position to Region Position Map1" in Integration Object Map.
b Within Target Field Name, query for Region Position Assignment Type.
7 Query for "Clinical Region Position to Protocol Position Map1" in Integration Object Map.
b Within Target Field Name, query for Protocol Position Assignment Type.
8 Query for "Clinical Region Position to Site Position Map1" in Integration Object Map.
b Within Target Field Name, query for Site Position Assignment Type.
10 Once you have performed the changes detailed in the preceding tables, publish and activate them
within Administration - Business Process > Repository Workflows.
New/
Modified Search Specification (Old) Search Specification (New)
Modified [Is Product Allocation Type] = 'Y' [Is Product Allocation Type] = 'Y' AND
AND [Is Stock Employee Id - [Owned By Id] = LoginId() AND [Stop
Owned by Id] = 'Y' AND [Is Stop Sampling Flag] =
Sampling Active Period Flag] = 'Y' LookupValue("BOOLEAN_VALUE","N") AND
AND [Is Lot Product Type] = 'Y' (([Active Flag] = LookupValue
AND [Is Lot Stock] = 'Y' AND ("BOOLEAN_VALUE","Y") and [Is Stock
[Inventory Audit Report Id] IS Employee Id - Owned by Id] = 'Y' AND [Is
NULL Lot Product Type] = 'Y' AND [Is Lot Stock] =
'Y' AND [Inventory Audit Report Id] IS NULL)
OR (([Inventory Flag] = 'N' OR [Inventory
Flag] IS NULL) AND ([Lot Flag] = 'N' OR [Lot
Flag] IS NULL)))
Fields
Join
Modified S_STK_PERD_EMP N Y
Modified S_STOCK_EMP N Y
New/
Modified? Search Specification (Old) Search Specification (New)
Modified [Is Product Allocation Type] = [Is Product Allocation Type] = 'Y' AND [Owned
'Y' AND [Is Stock Employee Id - By Id] = LoginId() AND [Stop Sampling Flag] =
Owned by Id] = 'Y' AND [Is LookupValue("BOOLEAN_VALUE","N") AND
Stop Sampling Active Period (([Active Flag] = LookupValue
Flag] = 'Y' AND ([Inventory ("BOOLEAN_VALUE","Y") and [Is Stock
Audit Report Id] IS NULL) Employee Id - Owned by Id] = 'Y' AND
[Inventory Audit Report Id] IS NULL) OR
(([Inventory Flag] = 'N' OR [Inventory Flag] IS
NULL)))
Fields
Join
Modified S_STK_PERD_EMP N Y
Modified S_STOCK_EMP N Y
2 Append the following files in the same siebel.ini file, but in the
..\<Build_Folder>\Release\Windows\Server\Siebel_Enterprise_Server folder only.
3 Under the [DeleteFiles.Windows] in the siebel.ini file, append the following entry:
File%Number% = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\main.css
4 Under the [DeleteFiles.Unix] in the siebel.ini file append the following entry:
File%Number% = $(SiebelRoot)/siebsrvr/WEBMASTER/files/%LANGUAGE%/main.css
5 Under the [DeleteFiles.Unix.HP-UX] in the siebel.ini file, append the following entry:
File%Number% = $(SiebelRoot)/siebsrvr/WEBMASTER/files/%LANGUAGE%/main.css
2 Add the APPLET_HIGHLIGHT_CONTROL_TYPE LOV type within the List of Values-Type screen.
3 Navigate to Site Map > Application - Data Administration > List of Values.
4 Add a translation for the List Columns control type with the following values:
■ Type: APPLET_HIGHLIGHT_CONTROL_TYPE
■ Display Value: List Columns
NOTE: This value must be List Column and not List Columns.
■ Order: 1
■ Active: Checked
2 Within Microsoft Outlook, navigate to Tools > Options, click Calendar Options, and click the Time
Zone tab.
3 Change the Time Zone information to make it the same as the Time Zone information in the
Siebel application.
4 Make a note of when the change from Standard Time to Daylight Savings Time (DST) occurs for
the current year.
5 Navigate to Administration - Data >Time Zone Administration view, and query for the time zone.
6 Modify the DST Start Ordinal, DST Start Day, DST Start Month, DST Start Time, DST End Ordinal,
DST End Day, DST End Month, and DST End Time fields in accordance with the current year’s
DST time change.
For example, using 2009 as the year, DST started on March 8 at 2 A.M. and ended on November
1 at 2 A.M. In this example, the values would be DST Start Ordinal=Second, DST Start
Day=Sunday, DST Start Month=March, DST Start Time=120, DST End Ordinal=First, DST End
Day=Sunday, DST End Month=November, DST End Time=120.
NOTE: This file is located within the REPPATCH folder within your Siebel Tools installation folder.
1 Within Siebel Tools, navigate to the Table Promotions project, and lock it.
2 Use the Import from Archive function to read the S_PRO_CFG_ITEM.sif file and create the tables
in the repository. Use the Merge option when creating this file.
3 Within Siebel Tools, query for the list of tables that were imported into the repository by entering
the following values into the Apply Schema dialog box:
e Click Apply.
Category Aggregation Field 1 "Promotion Incremental Qty", Add this property if it does not
"Incremental Cases” already exist
You can also create a custom column and can configure for aggregation of this custom column.
Use the following information to create a custom column for the CG SVP Product Baseline-Aux:
Category Aggregation Field n "Source Field", "Target Field" n is the next number of this
('Category Aggregation Field')
In this case, "CalcTest",
property.
"CalcTestStorage Cases"
Users need to add this value for
the new custom column.
■ The "Source Field" value listed in the preceding table is a custom field in the "CG SVP Product
Baseline - Aux" business component and represents the value that the user wants to roll up.
■ The "Target Field" value listed in the preceding table is a custom field in the "CG SVP Product
Baseline - Aux" business component and is the field into which the rolled up value will be stored.
This should be a physical column of the table.
Schema Changes
Table: S_INVC_PAYMENT (Modified)
Columns:
New? Name User Name Default Physical Type Nullable Length Required
New? Name User Name Default Physical Type Nullable Length Required
Columns:
Physic Nullabl
New? Name User Name Default al Type e Length Required
Business Components
Name: FS Invoice
Description:. Add a user property, which will be used to void the invoice and copy the fields.
No FS Invoice
BC User Property:
Name Details
Description:. Add a user property, which will be used to void the invoice and copy the fields.
BC User Property:
Name Details
Description: Add a user property, which will be used to void the invoice and copy the fields.
Field:
Field: Quantity
Inactive: T
BC User Property:
Name Details
Name Details
Field:
Pre Default : N
Required :Y
Type:DTYPE_BOOL
Name: CS HH FS Payments
Field:
Pre Default: N
Required: Y
Type: DTYPE_BOOL
Applets
Name: SIS HH FS Invoice Form Applet - CE
Column:
No VoidInvoice Enable: Y
Minibutton
List Columns:
Runtime = Y
Description: Make the Apply to Invoice and Payment Total fields read-only.
ReadOnly =T
Field: Amount
ReadOnly: T
Column:
ReadOnly:T
List Columns:
ReadOnly:T
No HH CG Undeposited Search Specification : ([Void Flag] <> 'Y') AND ([Deposited Flag]
Payment List Applet CE <> 'Y') AND ([Payment Method] <> LookupValue
("PAYMENT_METHOD_CODE", "Credit Memo") OR [Payment
Method] IS NULL)
NOTE: Please add the Void flag wherever necessary. It is present in all Invoice and Payment Business
Components, so it can be added to any applets based on these Business Components as required.
1 Log into Siebel Tools, and within Object Explorer, navigate to Applet.
3 Add "FromDate" and "ToDate" user properties for the applet and enter valid date as values. The
date format should be mm/dd/yyyy.
1 Within Siebel Tools, search for the "UMF Passive Message Virtual BusComp" Business Component.
2 Create a new field with the following values:
❏ Name = Sequence
❏ Text Length = 10
❏ Type = DTYPE_TEXT
■ Add the following parameter under the eai_enu section in eapps.cfg file to make the fix work:
SWSENoSessInPref= true
3 Navigate to Business component and query for the Order Item XA Business Component.
4 Navigate to Field and create a new field with the following values:
❏ Calculated: Yes
❏ Calculated Value: IIF([Attribute Id] IS NOT NULL, [Attribute Id], [Attribute Definition Id])
❏ Force Active: No
6 Navigate to List > List Column, and create a new list column with the following values:
7 Navigate to Applet Web Template, query for Edit List, right-click, and select Edit Web Layout.
8 Add Attribute Definition Id in the applet and change the field name to Attribute Id - Merged.
1 Launch Siebel Tools, and lock the Quote and Order entry projects.
3 Navigate to ‘Business Component User Props’, and add a new entry with the following values:
❏ Value: "Unit Price", "Cfg State Code", "IIf ([Cfg State Code] =
LookupValue('CFG_ITEM_STATE_CD', 'Engine Picked Item'),
LookupValue('CFG_ITEM_STATE_CD', 'User Requested Item'), [Cfg State Code])"
4 Query for the Order Entry - Line Items Business Component, and add an entry with the same
values as listed in Step 3.
■ You must recreate the Business Component source in SES and reindex all Search categories in
the Siebel application.
■ Make sure that the Category names are unique when they are pointing to the same Business
Component across different definitions (such as Call Center, Sales, and so forth).
■ Within Siebel Tools, make sure that the Category Name field exists for the Search Results Body
Business Component. If it does not, add the Category Name field named Search Results Body
Business Component.
■ When users click the Refresh button after category in Search Index Settings, all other categories
(across all definitions) that point to the same Business Component will also be refreshed.
■ Refresh and incremental indexing will be performed only on the already-indexed categories.
■ The <link> tag for every Business Component in the field mappings file has been modified.
■ FR 12-1U0D4B3 fixes multiple categories on the same Business Component as well as other
known issues with refreshing or incremental indexing.
■ Use the Solution Business Component for indexing, and not the Solution Admin Business
Component.
■ You must add a new Business Service user property with Name=Solution Admin and
Value=Solution under the Content Service Business Service. This property is not already
available within the application. This instruction also applies to other Business Component pairs
like Solution and Solution Admin. For example, records could be modified only in the Admin BC
but drill-downs search results could be set to a view that corresponds to a non-Admin Business
Componentn. Adding the new user property in the Business Service will make sure that:
■ If records are modified in Solution Admin Business Component, the index will be refreshed/
incremented with the changes.
■ If you want to index the Solution Admin Business Component and not the Solution Business
Component, it is not necessary to add the new user property mentioned above. The view name
for that index category should be set to the Solution Admin Business Component view.
■ If indexing is done on Solution Admin and the view name that is used is for the Solution Business
Component, the search results will not be correct.
■ In search results, the Data Source column displays the Category Name and not the Business
Component name.
2 Within Object Explorer, navigate to Project, query for LS Clinical Protocol Site, and lock the
project.
3 Within Object Explorer, navigate to Business Component, query for the Clinical Trip Report
Business Component, and lock the object.
4 Click Multi Value Link, and for the Clinical Attendee Static multi-value link, select True for the No
Copy option.
2 For the LS Clinical Site Visits Business Object, create a new Business Object Component with the
following values:
3 For the Clinical Protocol Site Business Object, create a new Business Object Component with the
following values:
2 Add the existing FINS Approval Stage Business Component as the primary Business Component.
4 Compile the new Business Object into the SRF and unlock the VEAI FINS Approval project.
5 Bounce the server.
❏ [ Description: Value=1, Append template to email body; Value=0, Replace email body
with template ]
NOTE: If the New button on the System Preference applet is disabled, navigate to the System
Preference object within Business Components in Siebel Tools and uncheck the 'No Insert' option.
b Right-click on the record , select 'Edit Web layout', and then change 'System Preference Name'
Read Only field to FALSE in Property Window.
3 Bounce the Siebel Server.
SWSENoSessInPref=True
To set up workflows
1 Within Siebel Tools, select Workflow Process Object in OBLE.
2 Right-click, select Import Workflow Process, and import SIS OM Get Future Asset
SubProcess.xml.
3 Click Deploy to change the workflow status from “In Progress” to “Complete.”
❏ If you are connected to the server data source, the completed workflow process is
available to be activated.
❏ If you are connected to the local data source, check in the workflow process in order to
be able to activate it at run time.
4 Verify that SIS OM Get Future Asset SubProcess appears in the child applet with Deployment
Status = ‘Active’.
4 Verify that the middle applet is the Action view tab, click New, and enter the following values:
a Sequence = 1
e Active = Checked
5 Navigate to the previous view by clicking Signals in the top view tab.
6 Select the record that you created in Step 2 and click the Release New Version button.
7 Select Menu > Clear Cache, and then log out of the application.
2 Click Clustering Configuration, and within the screen, check the Enable Clustering check box.
1 Navigate to the location in which you have installed the Mobile Web Client, navigate to
siebsrvr\XMLP\TEMPLATES, and open MOBUSRSUM.xsl.
TIP: Search for keyword= "Mobile User Name" to find the section.
</fo:block>
</fo:table-cell>
</fo:block>
</fo:table-cell>
</fo:block>
</fo:table-cell>
</fo:inline>
</fo:block>
</fo:table-cell>
1 Within the Siebel Loyalty application, navigate to Site Map > Administration - BIP Reports >
Report Template Registration.
The Loyalty Voucher Cancellation Statement and Loyalty Voucher Issue Statement rows will
appear.
a In the Template column, click and browse for the saved .rtf file (packaged with the build), select
the corresponding .rtf file and save the record.
2 Within the LOY Terms BC, change the Calculated Value of the IsNotPrePaid' field to: IIF([Billing
Type] = LookUpValue("LOY_PRT_BILL_CD","Pre Paid"), "N","Y")
3 Within the Billing Type field’s pickmap, change 'PickList Field' from 'Name' to 'Value'.
1 Within Siebel Tools, query for the SIS OM Base Architecture project, and lock it.
❏ Name: strSetCfgStateCodeOnExplode
❏ Value: Y
❏ Name: strCfgStateCodeOnExplodeValue
❏ Value: User Requested Item (This value has to be a LanguageIndependentCode from the
values of LOV “CFG_ITEM_STATE_CD”.)
3 In the Business Services list, query for the ISS Authoring Import Export Service BS.
5 Uncheck and recheck the Business Service object and click OK.
6 From Object Explorer, expand the Business Service object, and select Business Service User Prop
from the list.
7 Select “ISS Authoring Import Export Service” from the “Business Services” applet on the right-
hand side.
8 Within the “Business Service User Prop” applet, add a new record with the following values:
❏ Name = AutoProceed
❏ Value = Y
9 Navigate to Tools > Compile Projects, select “ISS Authoring Admin” from the Projects list, and
select the “Selected projects” option if it is not already selected.
2 Navigate to Administration Data Validation > Rule Set, and create a rule set with the following
values:
❏ Name: MS
❏ ReturnCode: 333
NOTE: The rule has Immediate Display set to TRUE which means that the message defined will
display if the expression evaluates to FALSE
3 Navigate to Administration Run Time Events > Action Sets, and create an action set with the
following values:
❏ Name: Quote
❏ Business Service Context: "Rule Set Name", "MS", "Enable Log", "Y"
❏ Event: PreWriteRecord
5 Log into to Siebel Web Server or launch the Siebel Web Client by connecting to the same
database to which the Siebel Server is connected.
6 From the Site Map, navigate to Administration > Run Time Events.
7 Click New on the top list applet to create a new action set with the following values:
❏ Active: ?
❏ Enable Export: ?
8 Click the New button on the middle list applet to create a new record with the following values:
❏ Sequence: 1
❏ Active: ?
❏ Value: [Id]
10 Within the Administration – Runtime Events tab, click the Events tab.
11 Click New on the list applet to create a new event with the following values:
❏ Sequence: 1
❏ Event: PreInvokeMethod
❏ Subevent: PSPExecute
NOTE: This is the name of the action set created in Step 7 on page 728.
3 Change the Business Service from Invoke Search to Search Client Service.
4 Query for the ToggleSearch command and change the Business Service from Invoke Search to
Search Client Service.
❏ Event: PreInvokeMethod
❏ SubEvent: PickRecord
4 Within Siebel Tools, navigate to the Account Business Component, and add a user property with
the following values:
NOTE: The first parameter of the [Value] should be same as the method given in 'Method Name'
of Action Set ('ValidateAccountStatus' in this case). The parameter after 'Rule Set Name' should
be the name of the Rule Set created ('Account Validation' in this case).
1 Within Siebel Tools, navigate to Object Explorer > Class, and add a record with the following
values:
❏ Name: CSSSegmentUpdateTreeService
❏ Project: Segmentation
❏ DLL: SSDBMSV
❏ Object Type: Service
❏ High Interactivity: 1
2 Navigate to Object Explorer > Business Service, and create a record with the following values:
❏ Project: Segmentation
❏ Class: CSSSegmentUpdateTreeService
3 Navigate to Object Explorer > Business Service > Business Service Method, and create a record
called UpdateSegmentTreeTable.
2 Query for the LOY Interactive Processing Engine Business Service, and add a new Business
Service User Property with the following details:
3 Query for the LOY Cancelled Transaction Business Component, and add two new fields with the
following details:
❏ Name: Amount
❏ Type: DTYPE_NUMBER
❏ Column: AMT_VAL
❏ Type: DTYPE_BOOL
❏ Text Length: 1
❏ Column: OVR_PRI_FLAG
4 Query for the 'LOY Corporate Transaction Business Component, and add two new fields with the
following details:
❏ Type: DTYPE_NUMBER
❏ Column: ORIG_AMOUNT
❏ Type: DTYPE_INTEGER
❏ Column: ORIG_POINTS
5 Compile the above changes to your .srf file and restart the application.
2 Drill down on the promotion number, add a new rule with an Appropriate name (such as: Invoke
Cancel Action Rule 1), ensure that this rule is the first rule under the promotion, and choose
Apply to = "Transactions".
3 Drill down on the rule name that you just created, and under Criteria Setup, enter the following
criteria:
❏ Object: Transaction
❏ Condition: Equals
❏ Value: Redemption
❏ Object: Transaction
❏ Condition: Equals
❏ Value: Y
4 Under the "Actions" tab, create an action with the following values:
5 Leave the other existing rule under the Promotion tab unchanged and activate the promotion.
1 Log into Siebel Tools and query for the Assignment Rule Business Component.
3 Open the Properties window, copy the value of the Post Default Value property, and then set the
value to empty for this property.
1 Within Siebel Tools, query for the Assignment Group-IO integration object.
3 Query for the Csv Import By EAI user property, and add this property if it does not exist.
1 Log into Siebel Tools, and query for the Skill Applet or Position-Skills-SkillItems applets.
3 Select Control in the applet, and query for the ImportSkillData control.
4 Delete the ImportSkillData control for both the Skill and the Position-Skills-SkillItems applets.
1 Log into Siebel Tools, query for the Synergy project, and lock it.
2 Query for a symbolic string with the following values: Name=SBL_ASG_*_POPUP and
Project=Synergy
❏ Name: SBL_ASG_IMPORT_POPUP
❏ Project: Synergy
❏ Type: Conversion
❏ Definition: Display as title for Import Popup Applet through which use initiates Import
Process
❏ Translate: Check on
❏ Comments: Display Popup to get Import file name and description for the Import Activity
4 Add a view called "Communication Detail View" with the following responsibilities:
■ Siebel Administrator
1 Within Siebel Tools, navigate to the SIA CS ADL Product Distribution List Applet > SIA CS Retail
Product - Authorized Distribution Business Component.
2 Change the fields used by these existing list columns of the applet:
1 In File > Page Setup, select Print Background Colors and Images.
2 In Tools > Internet Options > Advanced > Printing, select Print Background Colors and Images.
NOTE: It is very important that you make sure to override the object definition in the repository.
5 If the objects have been customized before, compare the relevant object with the corresponding
archive created in Step 2 and use the shuttle arrow to import the customizations.
1 Log into Siebel Tools, and lock the LS Pharma Samples project.
2 Add the LOY Merge Transaction Business Component to LOY Member Business Object.
2 Change the value of the 'LOY Queue Manager user property SearchSpec: Batch' to [Active] = 'Y'
AND ([Process Date] IS NULL OR ([Member Last Txn Date] > [Process Date] AND ([Next
Assessment Date] IS NULL OR [Next Assessment Date] <= Timestamp())) OR [Tier End Date] <
Timestamp() OR ([Qual Period End Date] IS NOT NULL AND [Qual Period End Date] <
Timestamp()))
2 In the Campaign BC, create a new field called Mutually Exclusive Segment based on this column.
The type should be DTYPE_BOOL and the 'Force Active' property must be set to 'true'.
3 In the Campaign Execution Options Form Applet-Manager applet, create new control (type:
checkbox) for the mutual exclusion flag based on the Mutually Exclusive Segment field of the BC.
2 Create a new LOV type for treatment channel, and create new values for the required treatment
channel types (Email, fax and web).
4 In the Mktg Campaign Segment Definition' BC, create the following user properties:
❏ Field CPR Count: Set the value to the number of CPR fields that need to be implemented
6 Create pick maps for these fields. If the field is based on LOV, then in the pickmap, 'Picklist Field'
should be 'value'.
7 In the Mktg Campaign Segment Definition List Applet, under list, create new list columns for
treatment channel, organization name and product name. For organization name and product
name, associate appropriate pick applets.
9 In the Segments/Lists BC, create the CPR fields based on the corresponding columns in
S_CALL_LST table (same as in the Mktg Campaign Segment Definition BC but here there is no
need to associate pickmaps and picklists).
❏ treatmentChannel
❏ primaryOrganizationName
❏ productName
10 In the Segments/Lists BC create the user properties for CPR fields (same as in the Mktg
Campaign Segment Definition business component).
❏ Field CPR Count: Set the value to the number of CPR fields that need to be implemented.
For example, to configure one more CPR field (such as organization) in addition to the ones
mentioned above, change the Field CPR Count user property to '4'. Create a new user property called
Field CPR Field: 4 and set the value as organization. Create a new business component field called
organization and associate a picklist or LOV as needed. Create a new column in S_CALL_LST for this
field with type as VARCHAR and length '30'. Create a list control in the Mktg Campaign Segment
Definition List Applet.
This filter is needed only in case of mutual exclusion. In case of campaign load without mutual
exclusion, the original load format as mentioned in bookshelf can be used.
Note the following information about lower and higher limits for allocation within BI Publisher: When
Update Count is done from Campaign > Design > Allocation, a job.xml file will be created on the BI
side as part of the fix. When loading the campaign, lower and higher limits for allocation will be
present in the xml file created on the BI side when mutual exclusion is selected.
2 Within Object Explorer, cliick on BC User Property and create new record with the following
values:
❏ Value: N
■ The name and version number of the Siebel application you are using
■ Your name, job title or functional area, company name, phone number, and email address
Oracle
Siebel Technical Publications Department
500 Oracle Parkway
Redwood Shores, CA 94065
Siebeldoc_ww@oracle.com