MR Guide 80 Rev E

Siebel Maintenance
Release Guide
Version 8.0.0.x, Rev. E
October 2008
Copyright 2005, 2008, Oracle. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information;
they are provided under a license agreement containing restrictions on use and disclosure and are also
protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering,
disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability
with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems
in the documentation, please report them to us in writing. This document is not warranted to be errorfree. Except as may be expressly permitted in your license agreement for these Programs, no part of
these Programs may be reproduced or transmitted in any form or by any means, electronic or
mechanical, for any purpose.
PRODUCT MODULES AND OPTIONS. This guide contains descriptions of modules that are optional and
for which you may not have purchased a license. Siebels Sample Database also includes data related to
these optional modules. As a result, your software implementation may differ from descriptions in this
guide. To find out more about the modules your organization has purchased, see your corporate
purchasing agent or your Siebel sales representative.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs
on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical
data delivered to U.S. Government customers are "commercial computer software" or "commercial
technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific
supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
Programs, including documentation and technical data, shall be subject to the licensing restrictions set
forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set
forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA,
Inc., 500 Oracle Parkway, Redwood City, CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,
redundancy and other measures to ensure the safe use of such applications if the Programs are used for
such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third
parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites.
You bear all risks associated with the use of such content. If you choose to purchase any products or
services from a third party, the relationship is directly between you and the third party. Oracle is not
responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of
the agreement with the third party, including delivery of products or services and warranty obligations
related to purchased products or services. Oracle is not responsible for any loss or damage of any sort
that you may incur from dealing with any third party.
Contents
Whats New in This Revision
Quick Fixes Included in 8.0.0.x Fix Packs
Enhancements and Updates in 8.0.0.x Fix Packs

Enhancements
Enhancements
Enhancements
Enhancements
Enhancements
and
and
and
and
and
Updates
Updates
Updates
Updates
Updates
in
in
in
in
in
Version
Version
Version
Version
Version
8.0.0.5
8.0.0.4
8.0.0.3
8.0.0.2
8.0.0.1
14
15
18
19
20
20
Configuration Instructions for Enhancements and Updates

Configuration
Configuration
Configuration
Configuration
Configuration
Configuration
Configuration
Configuration
Configuration
Configuration
Configuration
Configuration
Instructions
Instructions
Instructions
Instructions
Instructions
Instructions
Instructions
Instructions
Instructions
Instructions
Instructions
Instructions
Installation Instructions
for
for
for
for
for
for
for
for
for
for
for
for
ACR 271 21
ACR 347 21
ACR 364 24
ACR 372 37
ACR 373C 48
ACR 374 50
ACR 378 53
ACR 385 55
ACR 415 56
ACR 428 63
ACR 439 74
FR 12-1JNDSVI
20
76
79
Installation Overview 79
About Installing Patch Releases for Siebel Products 83
Installing Patch Releases on Windows 83
Installing Patch Releases on UNIX 88
Configuring Slipstream Patch Installation 94
Postinstallation Task for the Siebel Server 96
Postinstallation Task for the Web Server 96
Postinstallation Tasks for High Interactivity Clients 97
Postinstallation Task for the Siebel Sample Database 98
Postinstallation Task for Supporting Additional Languages
Uninstalling Patch Releases 101
Resolved Change Requests
100
102
Resolved Change Requests in the Siebel 8.0.0.5 Fix Pack
103
Siebel Maintenance Release Guide Version 8.0.0.x, Rev. E
Contents
Call Center 103

Comm Media Energy 106
Connectors / EAI 106
Consumer Sector 107
Customer Order Management 107
Data Quality 109
General 110
Life Sciences 117
Loyalty 118
Marketing 118
Mobile Solutions 119
Partner Relationship Management 119
Public Sector 120
Sales 120
Service 120
Universal Customer Master 121
User Interface 121
Resolved Change Requests in the Siebel 8.0.0.1 Through 8.0.0.4 Fix Packs
Call Center 122
Web Service 122
Comm Media Energy 124
Connectors / EAI 125
Consumer Sector 126
Customer Order Management 127
Data Quality 131
Employee Relationship Management 132
Financial Services 132
General 133
iHelp 147
Life Sciences 148
Loyalty 150
Marketing 150
Mobile Solutions 152
Partner Relationship Management 153
Sales 153
Service 154
Siebel Email Response 155
Travel and Transportation 155
Universal Customer Master 155
User Interface 156
122
Siebel Maintenance Release

Guide, Version 8.0.0.x, Rev. E
October 2008
This guide includes the following topics:
Enhancements and Updates in 8.0.0.x Fix Packs
Configuration Instructions for Enhancements and Updates

Table 1 describes the changes in this version of the documentation.
IMPORTANT NOTE: If you are using the Siebel Sample Database with the Siebel Mobile Web
Client or Developer Web Client, then after the Fix Pack release is installed, a scripting error
will occur and the user will be unable to access this database. You can address this
problem in two ways: you can either follow the workaround procedure detailed in
Postinstallation Task for the Siebel Sample Database on page 98, or you can apply 8.0.0.5
QF0502. However, because there is a dependency between QF0502 and CR 12-1ONEBTJ,
applying 8.0.0.5 QF0502 will invalidate the fix provided by CR 12-1ONEBTJ.
Table 1.
Whats New in Siebel Maintenance Release Guide, Version 8.0.0.x, Rev. E
Topic
Description
Updated topics with Siebel 8.0.0.5 Fix Pack information.
Enhancements and Updates in 8.0.0.x Fix

Packs
Configuration Instructions for
Enhancements and Updates
Siebel Maintenance Release Guide, Version 8.0.0.x, Rev. E Whats New in This
Revision
Table 1.
Whats New in Siebel Maintenance Release Guide, Version 8.0.0.x, Rev. E
Topic
Description

Packs
Removed information about ACR 367 (included in the

8.0.0.2 Fix Pack), and updated information to direct
customers to implement ACR 439 instead.

Packs
Included Siebel 8.0.0.4 Fix Pack information.

NOTE: The Siebel 8.0.0.4 Fix Pack is for Siebel Industry
Applications customers only.
How to Use This Guide

This document, Siebel Maintenance Release Guide, Version 8.0.0.x, lists the enhancements and fixes
provided in version 8.0.0.x releases of Oracles Siebel Business Applications.
This guide also provides information, instructions, and guidelines for installing Siebel Business
Applications version 8.0.0.x Fix Pack releases on top of version 8.0 or a prior 8.0.0.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 version 8.0.0.x Fix
Pack release. The latest version 8.0.0.x Fix Pack release available at publication time is version
8.0.0.5. Verify the availability and applicability of all Fix Pack or Quick Fix releases with Siebel
Technical 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:
Siebel Release Notes on OracleMetaLink 3 (https://metalink3.oracle.com/)
Siebel System Requirements and Supported Platforms on Oracle Technology Network

(http://download.oracle.com/docs/cd/E11886_01/srsphomepage.html).
This Maintenance Release Guide contains information about how to install the maintenance 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 Technical Support on OracleMetaLink 3 with questions regarding
the applicability of Maintenance Release Guide items to your deployment.
Additional Documentation
Oracle reserves the right to modify the documentation for Siebel Business Applications at any time.
Siebel Maintenance Release Guide, Version 8.0.0.x, Rev. E Quick Fixes Included in
8.0.0.x Fix Packs
For related Siebel documentation, see OracleMetaLink 3 https://metalink3.oracle.com and Bookshelf

for Oracles Siebel Applications Version 8.0 (http://www.oracle.com/technology/documentation/
siebel.html) on Oracle Technology Network (OTN).

Quick Fixes are developed to address immediate critical issues for specific customers, and can be
installed on top of Fix Packs. Quick Fixes address a small number of defects, and the fixes are
typically rolled into the next available Fix Pack for wider distribution to the Siebel customer base.
Testing for Quick Fixes is focused and is usually limited to verifying that the fix works on the specific
platforms that the affected customer is running.If you have installed a Quick Fix for any Siebel
8.0.0.x release prior to the latest 8.0.0.x release covered by this document, review Table 2 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.0.0.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.
Table 2.
Quick Fixes Included in Version 8.0.0.x
Change
Request ID
Fix Request
ID
Fix Pack Base
Quick Fix
Version
Merged Into
Fix Pack
12-1NJKYFT
12-1NNUPWU
8.0 [20405]
QF0023
8.0.0.5
12-1NKJF4T
12-1OTULJ7
8.0 [20405]
QF0024
8.0.0.5
12-1JNESUD
12-1JNESXW
8.0 [20405]
QF1006
8.0.0.5
12-1LW16M5
12-1LW16MP
8.0 [20405]
QF1011
8.0.0.5
12-1NKJF4T
12-1OK0O5R
8.0 [20405]
QF3002
8.0.0.5
12-1HN5K1B
12-1KXE14H
8.0.0.1 [20408]
QF0131
8.0.0.5
12-1KGO2U6
12-1MPP1TN
8.0.0.1 [20408]
QF0135
8.0.0.5
12-1LW16M5
12-1N2KYHJ
8.0.0.1 [20408]
QF0140
8.0.0.5
12-1M0PGMJ
12-1M0PGOZ
8.0.0.1 [20408]
QF0140
8.0.0.5
12-1ME9N7W
12-1MET0NX
8.0.0.1 [20408]
QF0144
8.0.0.5
12-1M80EIN
12-1N7B2S9
8.0.0.1 [20408]
QF0145
8.0.0.5
12-1MZ3MSF
12-1N3JE51
8.0.0.1 [20408]
QF0146
8.0.0.5
12-1NCY63H
12-1NJKRQI
8.0.0.1 [20408]
QF0149
8.0.0.5
12-1NG9H19
12-1NJKRPV
8.0.0.1 [20408]
QF0149
8.0.0.5
12-1KBNC1G
12-1MW7XQP
8.0.0.1 [20408]
QF0150
8.0.0.5
12-1MYLII7
12-1MYLZGK
8.0.0.1 [20408]
QF0152
8.0.0.5
8.0.0.x Fix Packs
Table 2.
Change
Request ID
Fix Request
ID
Fix Pack Base
Quick Fix
Version
Merged Into
Fix Pack
12-1NKJF4T
12-1NLXKO9
8.0.0.1 [20408]
QF0152
8.0.0.5
12-1NJKYSL
12-1NJKYT5
8.0.0.1 [20408]
QF0153
8.0.0.5
12-1LKD1UF
12-1NNURWF
8.0.0.1 [20408]
QF0154
8.0.0.5
12-1MRTDA9
12-1NZQWE5
8.0.0.1 [20408]
QF0156
8.0.0.5
12-1NQ7LNP
12-1NQODA9
8.0.0.1 [20408]
QF0157
8.0.0.5
12-1M940GM
12-1MB5SBD
8.0.0.1 [20408]
QF0158
8.0.0.5
12-1O3GNTF
12-1O3GNU6
8.0.0.1 [20408]
QF0159
8.0.0.5
12-1MI9KUX
12-1OG2CWB
8.0.0.1 [20408]
QF0160
8.0.0.5
12-1N3J0TB
12-1N3J0TV
8.0.0.1 [20408]
QF0160
8.0.0.5
12-1MSAZCI
12-1OK121H
8.0.0.1 [20408]
QF0161
8.0.0.5
12-1JDTXGH
12-1JF9V3W
8.0.0.1 [20408]
QF0162
8.0.0.5
12-1MYLIO1
12-1MXLMCP
8.0.0.1 [20408]
QF0163
8.0.0.5
12-1OJJL8T
12-1OJJL9E
8.0.0.1 [20408]
QF0164
8.0.0.5
12-1L1J856
12-1M4AISN
8.0.0.1 [20408]
QF1106
8.0.0.5
12-1K501OP
12-1K50T03
8.0.0.1 [20408]
QF2102
8.0.0.5
12-1K80MJ9
12-1K80MKN
8.0.0.1 [20408]
QF2102
8.0.0.5
12-1KD7YOY
12-1KD7YPS
8.0.0.1 [20408]
QF2102
8.0.0.5
12-1JMEMFN
12-1MR57KJ
8.0.0.1 [20408]
QF3104
8.0.0.5
12-1NBZY6B
12-1P29Q67
8.0.0.1 [20408]
QF0165
8.0.0.5
12-1IEP866
12-1MV6RFJ
8.0.0.2 [20412]
QF0209
8.0.0.5
12-1LVID39
12-1N0KLLP
8.0.0.2 [20412]
QF0209
8.0.0.5
12-1MJDXY4
12-1MQB1QO
8.0.0.2 [20412]
QF0209
8.0.0.5
12-1MRTDA9
12-1MRTDBD
8.0.0.2 [20412]
QF0210
8.0.0.5
12-1ME9N7W
12-1NCHJZ9
8.0.0.2 [20412]
QF0214
8.0.0.5
12-1M1SEYF
12-1NCYABP
8.0.0.2 [20412]
QF0215
8.0.0.5
12-1NNU3JH
12-1NNU3K6
8.0.0.2 [20412]
QF0217
8.0.0.5
12-1MMQK8H
12-1MSCR7A
8.0.0.2 [20412]
QF0218
8.0.0.5
12-1N3J10T
12-1N5VRJ6
8.0.0.2 [20412]
QF0218
8.0.0.5
12-1JGWLNN
12-1NQOJRM
8.0.0.2 [20412]
QF0219
8.0.0.5
12-1JZ4C6J
12-1NQOJSR
8.0.0.2 [20412]
QF0219
8.0.0.5
8.0.0.x Fix Packs
Table 2.
Change
Request ID
Fix Request
ID
Fix Pack Base
Quick Fix
Version
Merged Into
Fix Pack
12-1L89W3Q
12-1NQOJS1
8.0.0.2 [20412]
QF0219
8.0.0.5
12-1NGYQCT
12-1NGYQDL
8.0.0.2 [20412]
QF0219
8.0.0.5
12-1NCHP9T
12-1NDFA3V
8.0.0.2 [20412]
QF0220
8.0.0.5
12-1NH83XB
12-1NJ3ML7
8.0.0.2 [20412]
QF0222
8.0.0.5
12-1N3J0VT
12-1NCH1G1
8.0.0.2 [20412]
QF0223
8.0.0.5
12-1NBZY6B
12-1NDFT1L
8.0.0.2 [20412]
QF0224
8.0.0.5
12-1N03ODH
12-1NWNR6D
8.0.0.2 [20412]
QF0225
8.0.0.5
12-1N3J0OL
12-1N31O9Z
8.0.0.2 [20412]
QF0226
8.0.0.5
12-1NNDC5J
12-1NMFALL
8.0.0.2 [20412]
QF0228
8.0.0.5
12-1LAUPGS
12-1NTIP61
8.0.0.2 [20412]
QF0229
8.0.0.5
12-1N8PI4R
12-1NA4Y3B
8.0.0.2 [20412]
QF0229
8.0.0.5
12-HV44S7
12-1NFBCCR
8.0.0.2 [20412]
QF0230
8.0.0.5
12-1NDFR61
12-1NMF5VT
8.0.0.2 [20412]
QF0232
8.0.0.5
12-1MI9KUX
12-1NTZKD3
8.0.0.2 [20412]
QF0233
8.0.0.5
12-1NKJF4T
12-1O05HOP
8.0.0.2 [20412]
QF0234
8.0.0.5
12-1IOMFYR
12-1O2IRMC
8.0.0.2 [20412]
QF0235
8.0.0.5
12-1NWD809
12-1NVVV4F
8.0.0.2 [20412]
QF0236
8.0.0.5
12-1NQOZM5
12-1NT1V9H
8.0.0.2 [20412]
QF0237
8.0.0.5
12-1NJKYSL
12-1O95F39
8.0.0.2 [20412]
QF0238
8.0.0.5
12-1O3GNTF
12-1O3QYUN
8.0.0.2 [20412]
QF0241
8.0.0.5
12-1LKD1UF
12-1OD2OUR
8.0.0.2 [20412]
QF0244
8.0.0.5
12-1N3J16X
12-1N5VNLR
8.0.0.2 [20412]
QF0246
8.0.0.5
12-1OQD0BB
12-1OQD0BV
8.0.0.2 [20412]
QF0248
8.0.0.5
12-1NZNRV3
12-1O76PAB
8.0.0.2 [20412]
QF0249
8.0.0.5
12-1O76UGH
12-1O9MN7A
8.0.0.2 [20412]
QF0250
8.0.0.5
12-1OJ22KN
12-1OJ22LD
8.0.0.2 [20412]
QF0252
8.0.0.5
12-1O2HRQ9
12-1O2HRSO
8.0.0.2 [20412]
QF0253
8.0.0.5
12-1O6OCKJ
12-1ORCRR3
8.0.0.2 [20412]
QF0259
8.0.0.5
12-1OFLU7D
12-1ORCRRD
8.0.0.2 [20412]
QF0259
8.0.0.5
12-1NMF0AW
12-1NMF0C7
8.0.0.2 [20412]
QF0262
8.0.0.5
8.0.0.x Fix Packs
Table 2.
Change
Request ID
Fix Request
ID
Fix Pack Base
Quick Fix
Version
Merged Into
Fix Pack
12-1JGWLNN
12-1NZNXQ0
8.0.0.2 [20412]
QF2203
8.0.0.5
12-1JZ4C6J
12-1NZNXSD
8.0.0.2 [20412]
QF2203
8.0.0.5
12-1L89W3Q
12-1NZNXR6
8.0.0.2 [20412]
QF2203
8.0.0.5
12-1NGYQCT
12-1NXS4D3
8.0.0.2 [20412]
QF2203
8.0.0.5
12-5PSXQ8
12-1NGFKEC
8.0.0.2 [20412]
QF2203
8.0.0.5
12-1MRTDA9
12-1NDFM2F
8.0.0.2 [20412]
QF6201
8.0.0.5
12-1NCHP85
12-1NDFMYD
8.0.0.2 [20412]
QF6201
8.0.0.5
12-1NNDC5J
12-1O2HWN6
8.0.0.2 [20412]
QF6201
8.0.0.5
12-1N03ODH
12-1P19HYB
8.0.0.2 [20412]
QF6202
8.0.0.5
12-1N3J0NR
12-1NDWYLH
8.0.0.2 [20412]
QF6202
8.0.0.5
12-1NABW5J
12-1P1APBT
8.0.0.2 [20412]
QF6202
8.0.0.5
12-1NCHP85
12-1OUD0YT
8.0.0.2 [20412]
QF6202
8.0.0.5
12-1NZODJL
12-1NZNUFJ
8.0.0.2 [20412]
QF6202
8.0.0.5
12-1O3GG5V
12-1O65L03
8.0.0.2 [20412]
QF6202
8.0.0.5
12-1O3GG6U
12-1P1APD5
8.0.0.2 [20412]
QF6202
8.0.0.5
12-1O3GOE9
12-1O664Z9
8.0.0.2 [20412]
QF6202
8.0.0.5
12-1O4OT5J
12-1O4OT63
8.0.0.2 [20412]
QF6202
8.0.0.5
12-1O4OT7M
12-1P1APAR
8.0.0.2 [20412]
QF6202
8.0.0.5
12-1OQU6GN
12-1P1APCU
8.0.0.2 [20412]
QF6202
8.0.0.5
12-1MW8RAT
12-1OEM37F
8.0.0.2 [20412]
QF7202
8.0.0.5
12-1MW8RAT
12-1OOE5FX
8.0.0.2 [20412]
QF7202
8.0.0.5
12-1NWUB8D
12-1OE3D0L
8.0.0.2 [20412]
QF8201
8.0.0.5
12-1NWUB8D
12-1ORD20V
8.0.0.2 [20412]
QF8202
8.0.0.5
12-1MI9KUX
12-1P0RSXT
8.0.0.2 [20412]
QFA201
8.0.0.5
12-1HCLZNP
12-1PBEK5F
8.0.0.2 [20412]
QFA202
8.0.0.5
12-1OK1T6F
12-1OK1T86
8.0.0.2 [20412]
QFA203
8.0.0.5
12-1J04D3B
12-1N6TSJP
8.0.0.2 [20416]
QF0301
8.0.0.5
12-1M80EIN
12-1NPQJ4D
8.0.0.2 [20416]
QF0301
8.0.0.5
12-1N5VRBX
12-1N5VRCO
8.0.0.2[20412]WM5[20412_1]
8.0.0.2
[20412] WM5
[20412_1]
8.0.0.5
8.0.0.x Fix Packs
Table 2.
Change
Request ID
Fix Request
ID
Fix Pack Base
Quick Fix
Version
Merged Into
Fix Pack
12-1HCLZNP
12-1O2ZX8A
8.0.0.3 [20416]
QF0303
8.0.0.5
12-1NBZY6B
12-1OK13AH
8.0.0.3 [20416]
QF0305
8.0.0.5
12-1EXGK4H
12-1OJ2H1E
8.0.0.3 [20416]
QF0306
8.0.0.5
12-1HN5K1B
12-1OHLI1N
8.0.0.3 [20416]
QF0306
8.0.0.5
12-1IJUZYP
12-1OJ2HBB
8.0.0.3 [20416]
QF0306
8.0.0.5
12-1JDTXGH
12-1ORD7PN
8.0.0.3 [20416]
QF0306
8.0.0.5
12-1K1YCWH
12-1OHLI7N
8.0.0.3 [20416]
QF0306
8.0.0.5
12-1LXLFA2
12-1OJ2H67
8.0.0.3 [20416]
QF0306
8.0.0.5
12-1LXLFJM
12-1OI3OL8
8.0.0.3 [20416]
QF0306
8.0.0.5
12-1M4BIKL
12-1OJ2HI2
8.0.0.3 [20416]
QF0306
8.0.0.5
12-1MIVDTR
12-1OI3OGC
8.0.0.3 [20416]
QF0306
8.0.0.5
12-1NKJF4T
12-1OE32O3
8.0.0.3 [20416]
QF0307
8.0.0.5
12-1JNESUD
12-1OXSMHA
8.0.0.3 [20416]
QF0310
8.0.0.5
12-1NZOD0Z
12-1NXSN5F
8.0.0.3 [20416]
QF0313
8.0.0.5
12-1LW16M5
12-1P4OEMC
8.0.0.3 [20416]
QF0314
8.0.0.5
12-1NJKYSL
12-1P1STWF
8.0.0.3 [20416]
QF0314
8.0.0.5
12-1MRTDA9
12-1MRSWFO
8.0.0.3 Fix Pack HOR

[20414]
8.0.0.3 Fix Pack
8.0.0.5
12-1I2UQ34
12-1I4FXFZ
8.0 [20405]
QF1004
8.0.0.3
12-1IE7L9M
12-1IE8EZO
8.0 [20405]
QF1004
8.0.0.3
12-1K8KLHT
12-1K8KLJ7
8.0 [20405]
QF1009
8.0.0.3
12-1HUG5Q1
12-1MCTUI4
8.0 [20405]
QF1010
8.0.0.3
12-12OZHTB
12-1LAWDNL
8.0 [20405]
QF2009
8.0.0.3
12-1LQVFFS
12-1LUJKJB
8.0.0.1 [20408]
QF2105
8.0.0.3
12-1J0HCWP
12-1J1GUQJ
8.0 [20405]
QF3001
8.0.0.3
12-1JXI05I
12-1JZ36OD
8.0 [20405]
QF0012
8.0.0.3
12-1JOETRU
12-1JPUZC6
8.0 [20405]
QF0014
8.0.0.3
12-1JPWFGY
12-1JTGG5I
8.0 [20405]
QF0015
8.0.0.3
12-1KKAOAV
12-1LBIKZO
8.0 [20405]
QF0016
8.0.0.3
12-1JUI73R
12-1L0HA1S
8.0 [20405]
QF0017
8.0.0.3
8.0.0.x Fix Packs
Table 2.
Change
Request ID
Fix Request
ID
Fix Pack Base
Quick Fix
Version
Merged Into
Fix Pack
12-1KXYIVT
12-1L0H9YY
8.0 [20405]
QF0017
8.0.0.3
12-1L75V7G
12-1LI4E7X
8.0 [20405]
QF0018
8.0.0.3
12-1KK81PK
12-1KL98TR
8.0 [20405]
QF0022
8.0.0.3
12-1KYHUVD
12-1L0HA0O
8.0 [20405]
QF0022
8.0.0.3
12-1FEU6CH
12-1FEU6DR
8.0 [20405]
QF1007
8.0.0.3
12-1KWUYUJ
12-1KWUYV3
8.0 [20405]
QF1008
8.0.0.3
12-1HPH4NF
12-1L88OZV
8.0.0.1 [20408]
QF1103
8.0.0.3
12-1JVI3Q3
12-1JYKBRQ
8.0.0.1 [20408]
QF1104
8.0.0.3
12-1M81JE0
12-1M90AUF
8.0.0.1 [20408]
QF1106
8.0.0.3
12-1MBQUCS
12-1MCAUV6
8.0.0.1 [20408]
QF1107
8.0.0.3
12-1K0UX7Z
12-1K0VOXT
8.0.0.1 [20408]
QF2101
8.0.0.3
12-1HPH4NF
12-1KST4V8
8.0.0.1 [20408]
QF2102
8.0.0.3
12-1KI538N
12-1KJOGJY
8.0.0.1 [20408]
QF2102
8.0.0.3
12-1KKAOAV
12-1KK87RI
8.0.0.1 [20408]
QF2102
8.0.0.3
12-1K2JRWJ
12-1K2JRYQ
8.0.0.1 [20408]
QF2104
8.0.0.3
12-1L0PBZM
12-1L0PC13
8.0.0.1 [20408]
QF2104
8.0.0.3
12-1L3HCY6
12-1L6R2FN
8.0.0.1 [20408]
QF2104
8.0.0.3
12-1LCLHO5
12-1LCLHOU
8.0.0.1 [20408]
QF2104
8.0.0.3
12-1JXJOIR
12-1M3AGT7
8.0.0.1 [20408]
QF3101
8.0.0.3
12-12OZHTB
12-12OZHYF
8.0.0.1 [20408]
QF0103
8.0.0.3
12-1HPH4NF
12-1HU038G
8.0.0.1 [20408]
QF0103
8.0.0.3
12-1J8INSJ
12-1J8INT5
8.0.0.1 [20408]
QF0107
8.0.0.3
12-1KKAOAV
12-1KUV095
8.0.0.1 [20408]
QF0110
8.0.0.3
12-1K70L2I
12-1K94L55
8.0.0.1 [20408]
QF0111
8.0.0.3
12-1ISHFB1
12-1ISLW4L
8.0.0.1 [20408]
QF0113
8.0.0.3
12-1KIMMXI
12-1KJQ6T9
8.0.0.1 [20408]
QF0114
8.0.0.3
12-1KHY6ZV
12-1KJ7UAF
8.0.0.1 [20408]
QF0115
8.0.0.3
12-1KWC0LQ
12-1KWC0T0
8.0.0.1 [20408]
QF0115
8.0.0.3
12-1EYH454
12-1KRFIVC
8.0.0.1 [20408]
QF0118
8.0.0.3
12-1KIMIIJ
12-1KIMIK2
8.0.0.1 [20408]
QF0119
8.0.0.3
10
8.0.0.x Fix Packs
Table 2.
Change
Request ID
Fix Request
ID
Fix Pack Base
Quick Fix
Version
Merged Into
Fix Pack
12-1K1EJU3
12-1L520XK
8.0.0.1 [20408]
QF0120
8.0.0.3
12-1L5O0ZF
12-1L5O100
8.0.0.1 [20408]
QF0121
8.0.0.3
12-1L5O108
12-1L5O11I
8.0.0.1 [20408]
QF0121
8.0.0.3
12-1LIIY6E
12-1LQ0BOY
8.0.0.1 [20408]
QF0121
8.0.0.3
12-1LX21TV
12-1LX486L
8.0.0.1 [20408]
QF0124
8.0.0.3
12-1L75V7G
12-1L9B6ZN
8.0.0.1 [20408]
QF0125
8.0.0.3
12-1K5DYEJ
12-1LWK3SY
8.0.0.1 [20408]
QF0126
8.0.0.3
12-1L8APQG
12-1LQ8KLW
8.0.0.1 [20408]
QF0127
8.0.0.3
12-1LO1HPM
12-1LQ3CNP
8.0.0.1 [20408]
QF0127
8.0.0.3
12-1GZQYJ8
12-1MAMP8M
8.0.0.1 [20408]
QF0128
8.0.0.3
12-1IE7L9M
12-1MB5E52
8.0.0.1 [20408]
QF0128
8.0.0.3
12-1LJ7B5G
12-1LLCWE7
8.0.0.1 [20408]
QF0128
8.0.0.3
12-1LMZ43F
12-1LMZ442
8.0.0.1 [20408]
QF0128
8.0.0.3
12-1LJ7BCH
12-1LNI5G1
8.0.0.1 [20408]
QF0129
8.0.0.3
12-1LXMIR2
12-1LXMIRR
8.0.0.1 [20408]
QF0129
8.0.0.3
12-1LJ8F8Q
12-1LJ8FA2
8.0.0.1 [20408]
QF0130
8.0.0.3
12-1HUG5Q1
12-1MITKS0
8.0.0.1 [20408]
QF0133
8.0.0.3
12-1M3SXGD
12-1MHRJJD
8.0.0.1 [20408]
QF0136
8.0.0.3
12-1MN97BN
12-1MTD36R
8.0.0.1 [20408]
QF0136
8.0.0.3
12-1MKRYN4
12-1MKRYWW
8.0.0.1 [20408]
QF0137
8.0.0.3
12-1KXYIVT
12-1NCY8CL
8.0.0.1 [20408]
QF0147
8.0.0.3
12-1MQ6T1B
12-1MQ7PBB
8.0.0.1 [20408]
QF3102
8.0.0.3
12-1L3YHWX
12-1L3YHXW
8.0.0.1 [20408] WM5

[20408_1]
8.0.0.1
[20408] WM5
[20408_1]
8.0.0.3
12-1H09LEB
12-1M17E0R
8.0.0.2 [20412]
QF0201
8.0.0.3
12-1HPH4NF
12-1M13CWT
8.0.0.2 [20412]
QF0201
8.0.0.3
12-1HWCC3D
12-1M13CVZ
8.0.0.2 [20412]
QF0201
8.0.0.3
12-1KMBU6V
12-1M17E11
8.0.0.2 [20412]
QF0201
8.0.0.3
12-1K5DYEJ
12-1LZL215
8.0.0.2 [20412]
QF0202
8.0.0.3
12-1LMD69K
12-1M179PV
8.0.0.2 [20412]
QF0202
8.0.0.3
11
8.0.0.x Fix Packs
Table 2.
Change
Request ID
Fix Request
ID
Fix Pack Base
Quick Fix
Version
Merged Into
Fix Pack
12-1JY2PND
12-1K1EG77
8.0.0.2 [20412]
QF0203
8.0.0.3
12-1KLS5VP
12-1LJ7NSH
8.0.0.2 [20412]
QF0203
8.0.0.3
12-1LD3J4V
12-1M7H1RB
8.0.0.2 [20412]
QF0204
8.0.0.3
12-1M8JSWV
12-1MB5Y6H
8.0.0.2 [20412]
QF0204
8.0.0.3
12-1KKAOAV
12-1MRSPZF
8.0.0.2 [20412]
QF0205
8.0.0.3
12-1LO1HPM
12-1MTWXYZ
8.0.0.2 [20412]
QF0207
8.0.0.3
12-1L8TYDN
12-1LZLWL5
8.0.0.2 [20412]
QF0208
8.0.0.3
12-1LXMIR2
12-1N3JE99
8.0.0.2 [20412]
QF0210
8.0.0.3
12-1MRTDA9
12-1MRTDBD
8.0.0.2 [20412]
QF0210
8.0.0.3
12-1L8APQG
12-1N033R9
8.0.0.2 [20412]
QF0212
8.0.0.3
12-1JOETRU
12-1N5Y89O
8.0.0.2 [20412]
QF0213
8.0.0.3
12-1KK81PK
12-1NC0EFR
8.0.0.2 [20412]
QF0216
8.0.0.3
12-1LJ8F8Q
12-1NSKUQ3
8.0.0.2 [20412]
QF0221
8.0.0.3
12-1I9TQ6T
12-1I9TQA2
8.0 [20405]
QF0002
8.0.0.2
12-1ILMQ95
12-1ILMQC8
8.0 [20405]
QF0003
8.0.0.2
12-1IKLOCF
12-1JDC2D1
8.0 [20405]
QF0005
8.0.0.2
12-1IB0KC3
12-1IB0KCW
8.0 [20405]
QF0007
8.0.0.2
12-1JN3RAX
12-1JN3RBO
8.0 [20405]
QF0009
8.0.0.2
12-1F7GO6A
12-1JL5IBO
8.0 [20405]
QF0010
8.0.0.2
12-1JL6KOR
12-1JL6KQD
8.0 [20405]
QF0011
8.0.0.2
12-1HD4F79
12-1I6D3R9
8.0 [20405]
QF1001
8.0.0.2
12-1HIVV67
12-1I3EW0N
8.0 [20405]
QF1001
8.0.0.2
12-1II5E73
12-1II6G5R
8.0 [20405]
QF1005
8.0.0.2
12-1II5E73
12-1K7J4HJ
8.0 [20405]
QF2005
8.0.0.2
12-1JRFLX1
12-1JTYAZN
8.0.0.1 [20408]
QF0101
8.0.0.2
12-1JA6PVQ
12-1K4JG6G
8.0.0.1 [20408]
QF0102
8.0.0.2
12-1JPUA0N
12-1JQDXKW
8.0.0.1 [20408]
QF0102
8.0.0.2
12-1DIFPC9
12-1K95AMZ
8.0.0.1 [20408]
QF0103
8.0.0.2
12-1HP0M1F
12-1HU039C
8.0.0.1 [20408]
QF0103
8.0.0.2
12-1HZUW8N
12-1HZUWAK
8.0.0.1 [20408]
QF0103
8.0.0.2
12
8.0.0.x Fix Packs
Table 2.
Change
Request ID
Fix Request
ID
Fix Pack Base
Quick Fix
Version
Merged Into
Fix Pack
12-1ILMQ95
12-1K62GOF
8.0.0.1 [20408]
QF0104
8.0.0.2
12-1JRZWCK
12-1JYKBRB
8.0.0.1 [20408]
QF0105
8.0.0.2
12-1JL6KOR
12-1KB4U4V
8.0.0.1 [20408]
QF0106
8.0.0.2
12-1IVNL8I
12-1KG5KP9
8.0.0.1 [20408]
QF0108
8.0.0.2
12-1KDK35I
12-1KI5GVU
8.0.0.1 [20408]
QF0109
8.0.0.2
12-1H1Y7HB
12-1KB5851
8.0.0.1 [20408]
QF0112
8.0.0.2
12-1I9TQ6T
12-1LMXFGF
8.0.0.1 [20408]
QF0119
8.0.0.2
12-1IB0KC3
12-1LIOR2Z
8.0.0.1 [20408]
QF0119
8.0.0.2
12-1F7GO6A
12-1LP8UHE
8.0.0.1 [20408]
QF0122
8.0.0.2
12-1H9M1SN
12-1KJPMA7
8.0.0.1 [20408]
QF1101
8.0.0.2
12-1ILMQ95
12-1KJONN9
8.0.0.1 [20408]
QF1101
8.0.0.2
12-1JRZWCK
12-1KK841Q
8.0.0.1 [20408]
QF1101
8.0.0.2
12-1K7HV14
12-1KMAYL0
8.0.0.1 [20408]
QF1101
8.0.0.2
12-1KF2B59
12-1KLSJPO
8.0.0.1 [20408]
QF1101
8.0.0.2
12-1KF2BA0
12-1KKANTS
8.0.0.1 [20408]
QF1101
8.0.0.2
12-1KGO375
12-1KKANU5
8.0.0.1 [20408]
QF1101
8.0.0.2
12-1JTXB2L
12-1JYKBQT
8.0.0.1 [20408]
QF1102
8.0.0.2
12-1DIFPC9
12-1L88P1R
8.0.0.1 [20408]
QF1103
8.0.0.2
12-1HP0M1F
12-1L87ZH9
8.0.0.1 [20408]
QF1103
8.0.0.2
12-1HZUW8N
12-1L87ZFX
8.0.0.1 [20408]
QF1103
8.0.0.2
12-1LH4DG3
12-1LJSWOF
8.0.0.1 [20408]
QF1104
8.0.0.2
12-1DIFPC9
12-1KST4WC
8.0.0.1 [20408]
QF2102
8.0.0.2
12-1HP0M1F
12-1KST4U4
8.0.0.1 [20408]
QF2102
8.0.0.2
12-1HZUW8N
12-1KST4T0
8.0.0.1 [20408]
QF2102
8.0.0.2
12-1ILMQ95
12-1KST4PI
8.0.0.1 [20408]
QF2102
8.0.0.2
12-1JA6PVQ
12-1KUCQZV
8.0.0.1 [20408]
QF2102
8.0.0.2
12-1JL6KOR
12-1KST4RV
8.0.0.1 [20408]
QF2102
8.0.0.2
12-1JPUA0N
12-1KUCQXP
8.0.0.1 [20408]
QF2102
8.0.0.2
12-1KDK35I
12-1KUCR1A
8.0.0.1 [20408]
QF2102
8.0.0.2
12-1HPYIJR
12-1HXY7X8
8.0 [20405]
QF1001
8.0.0.1
13
Siebel Maintenance Release Guide, Version 8.0.0.x, Rev. E Enhancements and

Updates in 8.0.0.x Fix Packs
Table 2.
Change
Request ID
Fix Request
ID
Fix Pack Base
Quick Fix
Version
Merged Into
Fix Pack
12-1HC16C2
12-1I3HKS6
8.0 [20405]
QF1002
8.0.0.1
12-1GEKI37
12-1HM3CTI
8.0 [20405]
QF0001
8.0.0.1
12-1HTFK99
12-1HTFKA3
8.0 [20405]
QF0001
8.0.0.1
12-1HWF27G
12-1HWWAW6
8.0 [20405]
QF0001
8.0.0.1
12-1IZ39WY
12-1IZLJCU
8.0 [20405]
QF0004
8.0.0.1
Enhancements and Updates in 8.0.0.x

Fix Packs
This topic identifies the enhancements and updates provided in version 8.0.0.x releases.
Enhancements in 8.0.0.x Fix Pack releases are cumulative. This topic contains the following
subtopics:
Enhancements and Updates in Version 8.0.0.5 on page 15
14

Enhancements and Updates in Version 8.0.0.5

Table 3 lists the enhancements and updates provided in version 8.0.0.5.
This topic is part of Enhancements and Updates in 8.0.0.x Fix Packs on page 14.
Table 3.
Feature Enhancement or
Certification #
Feature Enhancement or Certification Description
ACR 373
ACR 373 provides the following functionality:
ACR 378
Supports Microsoft Exchange 2003 SP2 so that customers

can use Exchange 2003 SP2 to synchronize Siebel
calendars using SSSE.
Allows the administrator to specify both a system-wide and

a server-wide parameter for 'UserMailBoxIDSource'.
ACR 378 provides the following functionality:
If an acquisition is performed by a third-party engine,

Siebel UDQ now allows the vendor engine to handle the
acquisition and matching by passing the source record to
the vendor engine to take advantage of vendor-specific
acquisition algorithm.
Allows Full Batch and Incremental Batch to both be treated

as Full Batch. In the case of a search specification, the
search specification is now consumed by the vendor engine
as well.
ACR 391
Resolves a problem where having the EXISTS operator in the

searchspec field of the UI Data Web Service causes an error.
ACR 408
Supports Call Center Anywhere version 8.1.1 on Siebel 7.7.x,

7.8.x, and 8.0.x.
15

Table 3.
Certification #
ACR 415
ACR 415 provides the following enhancements:
16
Provides one-way synchronization from Exchange to Siebel

Calendar.
Provides an archive utility for Siebel appointments. The

utility runs in the Siebel application and flags the records
to be archived so that SSSE deletes them from Exchange
and they are not considered in future synchronizations.
The Exchange archive removes records in Exchange that
were not synchronized.
Resolves a problem with recurring appointments that occur

in both Microsoft Outlook and in Siebel Calendar.
Allows the Extract Start Date to be specified at the user

level rather than globally.
Resolves an issue where when an employee who is not in

the Siebel application and a contact that is in the Siebel
application both have the same first and last name but
different email addresses, when the employee creates an
appointment in Outlook and adds a synchronizing user,
when the record synchronizes, the contact is incorrectly
added to the Contacts MVG, while the employee is not
added to the MVG.

Table 3.
Certification #
ACR 428
ACR 428 provides the following enhancements:
ACR 439
New billing management views
Multiple Account Billing Profiles
Multiple balance groups, balances, and details
Real-time display of unbilled usage and invoices.
New Web Services for products, accounts, contacts, and

billing profiles
Enhanced Customer Order Management to support onetime charges, promotions, customizable product pricing,
and asset-based ordering enhancements
Nested Service bundle
ACR 439 provides the following Search enhancements:
Prepopulates Search terms and sets defaults in the Search

task pane.
Implements Preview with Find, as in Siebel version 7.x

applications. With this enhancement, when users click the
Binoculars icon, perform a search using the Find object,
select a single result line item, and click on Preview, the
selected result is displayed as a popup window.
Allows Find and Attach functionality to have the parent

relationship be based on the parent applet.
Allows customers to toggle between views.
17


Table 4.
Certification #
ACR 347

NOTE: ACR 347 is for Siebel Industry Applications
customers only.
ACR 347 provides Personalized Content Delivery. It includes
the following enhancements:
18
Drag-and-drop presentation message assembly.
Interactive presentation delivery with CRM.
One-click customer response/assessment.
Automated interaction tracking (tracks the time

spent on a message).
Measures message effectiveness.
Extends the Siebel Pharma call reporting, campaign

management, and sampling processes.


Table 5.
Certification #
ACR 372

This enhancement provides the following new formatting and
fields for the MedWatch Report (LS_3500A):
New fields on the "LS Medical Product Issue" business

component:
Common Device Name
7-Day (Type of Report)
STN#
PMA/510(k)#
One new field on the "LS Medical PI Product" business

component:
Common Device Name
New fields on the "LS Medical Product Issue RR"

business component:
Common Device Name
STN#
PMA/510(k)#
ACR 374
Provides email response integration with IMAP4.
ACR 377
Corrects an issue where the FINS CAP Buscomp Data Loader

Service ClearCache method is only functional within the same
OS Process.
ACR 398
Ports FR 12-FRKG0N and 12-FUP5Z3 from the Siebel 7.5

product to Siebel 8.0 to address poor performance with the
Product Selection Engine.
ACR 403
Resolves a problem where the Save Search button does not

work.
ACR 405
Provides support for dynamic MQ queuing.
19
Siebel Maintenance Release Guide, Version 8.0.0.x, Rev. E Configuration Instructions

for Enhancements and Updates

Table 6.
Certification #
ACR 145N
Enhances discounts to allow overriding of the discounts at the

line-item or order level.
ACR 271
Certifies Microsoft Internet Explorer 7 on Windows XP SP2.

For descriptions of known issues with ACR 271 and suggested
workarounds, see the Siebel 8.0 Release Notes on
OracleMetaLink 3 (Doc ID 546969.1)
ACR 364
Allows alerts triggered in Oracle Enterprise Manager to call Siebel

Web Services to log an IT-related Service Request and provide
details about the issue.
ACR 382
Provides an option for MQ transport to disable report generation.
ACR 385
Exposes the SetContactContext and ResetContactContext

methods.
ACR 401
Certifies JPN for SSSE.

There were no enhancements and updates contained in version 8.0.0.1.

This topic contains configuration instructions for some of the enhancements and updates provided in
version 8.0.0.x releases. This topic contains the following subtopics:
Configuration Instructions for ACR 271 on page 21
Configuration Instructions for ACR 373C on page 48
20

Configuration Instructions for FR 12-1JNDSVI on page 76
Configuration Instructions for ACR 271

This topic is part of Configuration Instructions for Enhancements and Updates on page 20.
Use the following procedure to implement ACR 271.
Log in to the Siebel application.
Navigate to the Site Map, click the Web Browser Administration hyperlink, and then click the
Browsers hyperlink.
In the Browser list applet, create a new record with Name=IE 7.0.
Click on the Capabilities tab in the lower applet and create the same capabilities as those in IE
6.0.
Change the value of User-Agent to "Mozilla/4.0 (compatible; IE 7."
In the Browser list applet, create a new record with Name=MSIE 7.0.
Click on the Capabilities tab in the lower applet and create the same capabilities as those in MSIE
6.0.
Change the value of User-Agent to "Mozilla/4.0 (compatible; MSIE 7."
Change the value of Parent to "IE 7.0".
10 Restart the Siebel Server to make the new settings take effect.

NOTE: ACR 347 is for Siebel Industry Applications customers only.
Use the procedures in this topic to implement ACR 347 for Personalized Content Delivery. The process
includes the following procedures:
To install the Siebel Tools patch on page 22
To uncompress REPPATCH files on page 22
To update Tools.cfg on page 22
21

To update Import.bat on page 22
To lock Siebel Projects on page 23
To run the import on page 23
To perform a full compile on page 23
To import seed data on page 23
To set System Preferences on page 24
To create folders on page 24
To install the Siebel Tools patch

1
Once the install folders have been extracted from the CD image, copy the content to a local drive,
and, within the siebel.ini file, set OverwriteConfig=yes. (The siebel.ini file is located in the
Siebel_Enterprise_Server folder.)
If you have Stop Siebel Server and Gateway Server services running, navigate to Programs >
Administration Tools > Services and stop them.
To install the server patch, navigate to the ../siebsrvr/webtempl directory, find the files called
CCFrameViewbar.swt, and rename them or move them to a backup directory.
To install the mobile client patch, navigate to the {Client install folder}/webtempl directory, find
the files called CCFrameViewbar.swt,and rename them or move them to a backup directory.
The patch will then install updated versions of these files in the webtempl directory.
To uncompress REPPATCH files

1
Navigate to the REPPATCH folder and unzip the ACR347RepSeedFiles_v80.zip file.

This creates a new folder called ACR347 with the following subfolders:
Repository: Contains .sif files for repository changes.
SEED_DATA: Contains seed data used by Personalized Content Delivery.
LMU: Contains language translation files.
To update Tools.cfg
1
Open tools.cfg and change parameter SymStrPrefix from X_ to SBL_.
Save and Close the tools.cfg file.
To update Import.bat
1
Navigate to the tools\REPPATCH\ACR347\Repository folder.
Right-click on Import.bat and choose Edit.
Set PCDTOOLSPATH to point to the folder where Siebel Tools is installed.
22

Set PCDDATASRC to Local if you are importing .sif files to the local Siebel Tools database.
Set PCDUSERNAME and PCDPASSWORD to the user name and password used to log into Siebel
Tools.
Save and close the file.
To lock Siebel Projects

1
Open the PROJECTS_TO_LOCK file in Notepad.
Log into Siebel Tools and check out the projects listed in the file.
Add new projects as mentioned in the file and lock the projects.
Log out of Siebel Tools.
To run the import

1
Double-click Import.bat to import all of the .sif files and create log files in the
tools\REPPATCH\ACR347\Repository\Log Folder.
Verify that all imports were successful.
To perform a full compile

1
Log into Siebel Tools.
Using Object Explorer, navigate to Tables.
Apply the schema changes to the database and activate them. For more information about
applying and activating schema changes, see the Siebel Bookshelf for Oracle's Siebel Applications
(http://download.oracle.com/docs/cd/B31104_02/homepage.htm) on Oracle Technology Network
(OTN).
Run a full compile of the .srf.
To import seed data

1
Navigate to the tools\REPPATCH\ACR\SEED_DATA folder.
Right-click on import.bat and choose edit.
Set PCDTOOLSPATH to point to the folder in which Siebel Tools is installed.
Set PCDDATASRC to the data source name used to connect to the database.
Set PCDTBLOWNER to the database table owner.
Set PCDUSERNAME and PCDPASSWORD to the user name and password use to log into Siebel
Tools.
Set PCDADDITIONALLANG to the language alias or comment this parameter by prefixing it with
#REM if you are using only ENU.
Save and close the file.
23

Run the import.bat file.
To set System Preferences

1
Set the Server Uncompression Location in the application:
Navigate to Administration - Application > System Preferences.
Query for 'Server Uncompression Location' in the 'System Preference Name' column.
Set the System Preference Value to '$siebelroot\eappweb\PUBLIC\enu folder on the server.
Set the Decompression Path in the application:
Navigate to Administration - Application > System Preferences.
Query for 'Decompressed Files Path' in the 'System Preference Name' column.
Set the System Preference Value to 'filesystem\assets'.
For more information about setting System Preferences, see the Siebel Life Sciences Guide on
the Siebel Bookshelf for Oracle's Siebel Applications (http://download.oracle.com/docs/cd/
B31104_02/homepage.htm) on Oracle Technology Network (OTN).
To create folders
1
Create a folder called filesystem\assets' in the 'PUBLIC\enu' folder on the server.
Create a folder called 'filesystem\assets' in the 'PUBLIC\enu' folder on the Mobile Web Client.
NOTE: To make all of your settings changes take effect, you must restart the Siebel Server.

Siebel Connector integrates Siebel Helpdesk 8.0 with Enterprise Manager. Using this connector, you
can create a Siebel Helpdesk Service Request, update an existing Service Request, or close a Service
Request based on metric alerts in Enterprise Manager.
The information in the subtopics that follow describes how to set up and configure Siebel Connector.
Autoticketing
Siebel Connector integrates Enterprise Manager with Siebel Helpdesk through HTTP connection. You
can create, update, or close tickets (Service Requests) based on Metric Alerts in Enterprise Manager.
24

You can specify the set of alerts for which tickets must be opened and the alert severity for which
this should happen.This can be done in Notification Rules, the user-defined rules that define the
criteria by which notifications should be sent for alerts. After the ticket is opened, any subsequent
update of the alert (such as a change in alert severity) will cause an annotation to the ticket. Once
the alert is cleared (the severity is set to Clear), the ticket can optionally be closed. (For detailed
steps on how to configure Notification Rules, please refer to the Oracle Enterprise Manager Advanced
Configuration documentation.)
Manual Ticketing
From the Enterprise Manager console, you can choose to manually open a Siebel Helpdesk Service
Request based on an open alert in Enterprise Manager. The Siebel Connector will populate the service
request with details based on the alert and the ticket template selected.
Ticket Template
Ticket template is a transformation style sheet in XSLT format used to transform Enterprise Manager
alerts into ticket format before the requests are sent to Siebel Helpdesk.This template is used to
specify how Enterprise Manger alert attributes can be used to populate the fields of a Siebel Service
Request (Ticket). A ticket template helps in the mapping of Enterprise Manager Alert fields into Siebel
Service Request fields.
In autoticketing, a notification method is created for each registered ticket template. The selected
notification method determines which ticket template is used when a notification is sent out to the
Connector. In the case of manual ticketing, you have to select a ticket template before submitting a
request to create a ticket.
Grace Period
The Grace Period provides users with a configuration to prevent the creation of large number of
tickets for frequently reoccurring alerts. For alerts that occur frequently within a relatively short time
interval, it is often desirable to open and maintain one trouble ticket that tracks each occurrence of
the alert instead of opening separate tickets each time. For recurring alerts, the Grace Period is a
time period during which reoccurrences of the same alert will cause an existing ticket for the alert
to be updated (or reopened) instead of causing a new ticket to be opened. For example, an alert
triggers and a ticket is opened for it. If the Grace Period is one hour and the alert is cleared at 10:00
am, then if the same alert retriggers before 11:00 am (one hour grace period), the ticket that had
been originally created for the alert will be updated/reopened.
Prerequisites
Before using Siebel Connector, ensure that you meet the following prerequisites:
Siebel Helpdesk 8.x is installed and configured.
Siebel Helpdesk Web Services are up.
25

Installing Siebel Connector

To install Siebel Connector
1
Create a folder in ORACLE_HOME/sysman/connector with name "Siebel_Connector", where

ORACLE_HOME is the Oracle home directory of OMS.
Get the EMHelpdesk.jar file from $Object_Root\classes\original.
Unzip the EMHelpdesk.jar file in "Siebel_Connector" folder.
SiebelDeploy.xml - Connector Descriptor
SiebelHelpdeskTemplate.xsl - Ticket Template
CreateResponse.xsl - Ticket Response Template
EMModel.xml - Alert Schema
Registering Connector Descriptor

You can register a connector descriptor using the emctl command from ORACLE_HOME/bin directory,
where ORACLE_HOME is the Oracle home directory of OMS.
Run the following command as a user with the execute privilege on emctl and can read the connector
descriptor:
emctl register_connector connector $ORACLE_HOME/sysman/connector/Siebel_Connector/
SiebelDeploy.xml <host> <port> <db sid> <user> <password> $ORACLE_HOME
For details on the emctl command, please refer to the Oracle Enterprise Manager Advanced
Configuration documentation.
Registering a Ticket Template

You can register a ticket template using the emctl command from ORACLE_HOME/bin directory,
where ORACLE_HOME is the Oracle home directory of OMS.
Run the following command as a user with the execute privilege on emctl and can read the connector
descriptor:
emctl register_ticket_template connector $ORACLE_HOME/sysman/connector/Siebel_Connector/
siebelTemplates/SiebelHelpdeskTemplate.xsl <host> <port> <db sid> <user> <password>
<connectorTypeName> <connectorName> <templateName> <description>
For details on emctl command, please refer to the Oracle Enterprise Manager Advanced Configuration
documentation.
Configuring the Siebel Connector

Use the following instructions to configure the Siebel Connector.
26

To configure the Siebel Connector

1
As Super Administrator, from the Enterprise Manager console, click "Setup".
Click "Management Connectors" in the left pane.

The Manager Connector Setup page appears. For the Siebel Connector row, the Configured
column should be blank.
Click the "Configure" icon for the Siebel Connector.
Provide the required settings.

The Siebel Connector communicates with the Siebel Helpdesk through their Web services. You
need to provide the following mandatory fields:
Web Service Endpoints - Endpoints to createTicket, updateTicket, and getTicket Web services
exposed by Siebel Helpdesk. Please refer to the Siebel Helpdesk Web Services doc for
additional details.
Siebel UserName - The user with the privilege to create, update, and query tickets in Siebel
Helpdesk.
Siebel Password - Password associated with the supplied Siebel user.
Enable web console - Check this box to enable launching of the Siebel Service Request page
within context from Enterprise Manager.
Helpdesk Host - The Siebel Helpdesk host name.
Grace Period - You can enable and disable the grace period and configure its value. By
default, the grace period is disabled.
Click "OK".
Creating Siebel Service Requests (Tickets)

You can have Service Requests created automatically, or you can create them manually.
To create Service Requests automatically

1
From the Enterprise Manager console, click Preferences.
In the left pane, under Notification, click Rules, and then Create.
In the Create Notification Rule General page, specify the rule name, description, and the targets
for which this rule should apply.
In the Create Notification Rule Availability page, select the availability states for which you want
to create tickets.
In the Create Notification rule Metrics page, select the metrics and their associated alert
severities for which you want to create and update tickets. Ensure that you select all relevant
alert severities if you want the ticket to be updated when the alert severity changes.
27

In the Create Notification Rule Methods page, choose the ticket template from the Advanced
Notification Methods table. In the table, registered ticket templates appear as Java Callback type
notification methods under the same name as the ticket template's file name. This ticket
template will be used to open tickets for all availability and metric alerts specified in this
notification rule.
The following process occurs after you create the notification rule for your alerts:
A notification is sent to the Siebel Connector when a metric alert that matches your rule
triggers. The Siebel Connector creates/updates a service request according to the ticket
template as set in the notification rule.
The service request is created or updated on the Siebel Helpdesk.
In Enterprise Manager, the alert annotation is updated. A Comment is added to the Metric
Details page of the alert to indicate that a service request was created or updated, along with
the service request number and service request page URL.
Navigating Between Siebel Helpdesk and Enterprise Manager

This subtopic explains how to switch from one console to the other.
To navigate from Enterprise Manager to Siebel Helpdesk

1
In the Enterprise Manager console, click the alert message to go to the metric details page for
the alert.
In the Alert History table, locate the ticket ID link in the Last Comment column.
If the ticket ID link is not available, click the icon in the Details column to get more information
about the alert.
One the page that comes up, locate the ticket Id in the Alert Details table.
Click the ticket ID link. You are forwarded to the Siebel Helpdesk login page.
Provide a valid Siebel userid/password, the service request associated with that alert is
displayed.
To navigate from Siebel Helpdesk to Enterprise Manager

1
From the Service Request page, copy the EventPageURL from the Service Request description
field.
Open a browser and paste the EventPageURL on the location to navigate to the Enterprise
Manager console login page.
Provide a valid Enterprise Manager userid/password to be forwarded to the alert related to this
service request.
28

Siebel 8.0 Ticket Template

This subtopic provides details about the ticket template shipped along with the Siebel Connector. The
ticket template specifies the mappings between Enterprise Manager alert attributes and Siebel
Service Request attributes.
The following actions will occur when a Service Request is created for an alert:
An alert message will be written to the Service Request abstract.
Alert information will be written to the Service Request description.
The default Service Request status will be set to "Open". When the autoClose Web Service
fires, the Service Request status will be updated to "Closed".
The default Service Request type will be set to "Internal".
The default Service Request area will be set to "IT".
The Service Request severity will be set based on the alert's severity.
Reading Ticket Templates

When the Enterprise Manager connector creates an Incident service request record, there is a data
transformation that occurs that maps the attributes of the Alert in the Enterprise Manager, with the
attributes of a Service Request on the Helpdesk system. The trouble ticket template and response
files specify this mapping. The logical mapping is summarized in the following table below. This table
will help you to read the Siebel ticket template.
Table 7.
SR Field
SR Payload and Enterprise Manager Event Mapping
EM Event
Field
Data Type
Default
Value
for
Create
Default
Value
for
Update
Comment
Id
DTYPE_ID
N/A
Generated
SR
Number
DTYPE_TEXT
N/A
Generated.
Status
(SR_STAT
_ID)
DTYPE_TEXT
Open/
Closed
Create: Hard-coded
Open
Update: Open if EM's Severity

!= Clear
Closed if EM's Severity = Clear.
SR Type
(SR_CAT_
TYPE_CD)
DTYPE_TEXT
Internal
N/A
Hard-coded.
Service
Request
Type
DTYPE_TEXT
Incident
N/A
Hard-coded.
29

Table 7.
EM Event
Field
Data Type
Severity
(SR_SEV_
CD)
Severity
DTYPE_TEXT
Abstract
Message
SR Field
30
Default
Value
for
Create
Default
Value
for
Update
Comment
Helpdesk: 1-Critical, 2-High,
and 3-Medium.
EM: Critical, warning, and
down.
DTYPE_TEXT
N/A
E.g. CPU utilization increases

from 50 to 95%.

Table 7.
SR Field
Area
(SR_AREA
)
EM Event
Field
Data Type
Default
Value
for
Create
Default
Value
for
Update
DTYPE_TEXT
IT
N/A
Comment
31

Table 7.
EM Event
Field
SR Field
Descriptio
n
Target
type,
Target
name,
Target
Host,
Target
Agent,
Metric
Column,
Metric
Name,
Key
Values,
Collection
time, Rule
Name,
Event
Page URL
Data Type
DTYPE_TEXT
Default
Value
for
Create
Default
Value
for
Update
Comment
Target type: The type of the
target that this event is
associated with (such as host,
database, and so forth).
Target name: The name of the
target that this event is
associated with (such as DB1,
stadc40.us.oracle.com).
Target Host: This is the name
of the host of the target that
the event/alert was generated
by.
Target Agent: (low prioritymight not be included) This is
the name of the server hosting
the agent that is monitoring
the generated event.
Metric Column: The name of
the metric column as it
appears on the EM console.
Metric Name: The name of the
metric (such as cpu utilization,
mem usage...and so forth).
Key values: The key values
associated with a key value
base event.
Collection time: When the
event occurred.
Rule Name: This is the name of
the notification rule that
generated the notification
during auto ticketing.
EventPageURL: The URL to the
event details page of this
event.
32

Siebel Ticket Template: SiebelHelpdeskTicketTemplate.xsl

<?xml version='1.0' encoding='UTF-8'?>
<xsl:transform version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:ns0="http://xmlns.oracle.com/sysman/connector/tt"
targetNamespace="http://xmlns.oracle.com/sysman/connector/tt"
xmlns:ser="http://siebel.com/Service/ServiceReqEMHelpDesk"
xmlns:data="http://www.siebel.com/xml/ServiceReqIO/Data"
elementFormDefault="qualified">
<!-This template creates an incident type ticket with default categorization

(Category: Default, Type:Default, Item:Default), and high priority. On update,
the description and message fields are updated.
-->
<xsl:template match="ns0:EventModel">
<xsl:choose>
<xsl:when test="normalize-space(ns0:TicketId) = ''">

<ser:ServiceReqEMHelpDeskInsertAndQuery_Input xmlns:data="http://www.siebel.com/xml/
ServiceReqIO/Data">
<data:ListOfServicereqio>

<data:ServiceRequest operation="?">
<data:Abstract><xsl:value-of select="ns0:Message"/></data:Abstract>
<data:Status>Open</data:Status>
<data:ServiceRequestType>Internal</data:ServiceRequestType>
<xsl:choose>
<xsl:when test="normalize-space(ns0:Severity) = 'Critical'">
<data:Severity>1-Critical</data:Severity>
33

</xsl:when>
<xsl:when test="normalize-space(ns0:Severity) = 'Down'">
<data:Severity>2-High</data:Severity>
</xsl:when>
<xsl:when test="normalize-space(ns0:Severity) = 'Warning'">
<data:Severity>3-Medium</data:Severity>
</xsl:when>
<xsl:otherwise>
<data:Severity>5-Question</data:Severity>
</xsl:otherwise>
</xsl:choose>
<data:Area>IT</data:Area>
<data:Description>
Ticket created by EM Siebel Connector.
Event Information:
--------------------------------------Target Type: <xsl:value-of select="ns0:TargetType"/>
Target Name: <xsl:value-of select="ns0:TargetName"/>
Target Host: <xsl:value-of select="ns0:TargetHost"/>
Target Agent: <xsl:value-of select="ns0:TargetAgent"/>
Metric Column: <xsl:value-of select="ns0:MetricColumn"/>
Metric Name: <xsl:value-of select="ns0:MetricName"/>
<xsl:choose>
<xsl:when test="normalize-space(ns0:KeyColumn) != ''">
Key Column: <xsl:value-of select="ns0:KeyColumn"/>
Key Values: <xsl:value-of select="ns0:KeyValues"/>
</xsl:when>
</xsl:choose>
Collection Time: <xsl:value-of select="ns0:CollectionTime"/>
<xsl:choose>
<xsl:when test="normalize-space(ns0:NotificationRuleName) != ''">
34

Notification Rule: <xsl:value-of select="ns0:NotificationRuleName"/>

</xsl:when>
</xsl:choose>
Event Page URL: <xsl:value-of select="ns0:EventPageURL"/>
-------------------------------------</data:Description>
</data:ServiceRequest>
</data:ListOfServicereqio>
<ser:LOVLanguageMode>LIC</ser:LOVLanguageMode>

<ser:ViewMode>All</ser:ViewMode>
</ser:ServiceReqEMHelpDeskInsertAndQuery_Input>
</xsl:when>
<xsl:otherwise>

<ser:ServiceReqEMHelpDeskQueryAndUpdate_Input xmlns:data="http://www.siebel.com/xml/
ServiceReqIO/Data">
<data:ListOfServicereqio>

<data:ServiceRequest operation="?">
<data:SRNumber><xsl:value-of select="ns0:TicketId"/></data:SRNumber>
<xsl:choose>
<xsl:when test="normalize-space(ns0:Severity) = 'Critical'">
<data:Severity>1-Critical</data:Severity>
</xsl:when>
<xsl:when test="normalize-space(ns0:Severity) = 'Down'">
<data:Severity>2-High</data:Severity>
</xsl:when>
35

<xsl:when test="normalize-space(ns0:Severity) = 'Warning'">

<data:Severity>3-Medium</data:Severity>
</xsl:when>
<xsl:when test="normalize-space(ns0:Severity) = 'Clear'">
<data:Status>Closed</data:Status>
</xsl:when>
<xsl:otherwise>
<data:Severity>5-Question</data:Severity>
</xsl:otherwise>
</xsl:choose>
</data:ServiceRequest>
</data:ListOfServicereqio>
<ser:LOVLanguageMode>LIC</ser:LOVLanguageMode>

<ser:ViewMode>All</ser:ViewMode>
</ser:ServiceReqEMHelpDeskQueryAndUpdate_Input>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
</xsl:transform>
Customizing the Ticket Template

If the Siebel ticket template does not satisfy your requirements, you can modify it. To do this, Oracle
recommends that you use this template as the base template. Copy this ticket template to a new
file, and then modify and register the new ticket template. In most cases, when you modify the ticket
template, you might only be changing the mappings.
The template is highly customizable. Oracle recommends that only users with advanced knowledge
of XSLT make complex changes.
You can use notification rules as a filter to associate proper ticket templates with alerts. You can have
as many tickets templates as you want. One notification rule can have only one ticket template.
36

Reference Documents
Oracle Enterprise Manager Advanced Configuration 10g Release 3 (10.2.0.3)
Siebel CRM Web Services Reference, available on Siebel Bookshelf on OTN
Enterprise Manager Alert Schema
Siebel Service Request Schema

Use the following procedures to implement ACR 372.
Tools.cfg
1
In tools.cfg, change the SymStrPrefix = X_ parameter to SymStrPrefix = SBL_
Import and apply the schema changes from

$ReleaseRoot\release\redist\repatch\ACR372_schema_772.sif
Business Components
In order to implement ACR 372, you must update the following Business Components:
Internal Product
LS Medical PI Product
LS Medical Product Issue
LS Medical Product Issue PR
LS Medical Related Product Issue
Internal Product Business Component

Update the existing "Internal Product" Business Component by adding new fields as shown below:
Project
Product
Table
S_PROD_INT
Single Value Fields

New/Modify
Name
Join
Column
New Field
Common
Name
S_PROD_INT_LS
X
COM_DEV_
NAME
Text
Length
Type
50
DTYPE_TEXT
37

LS Medical PI Product Business Component

Update the existing "LS Medical PI Product" Business Component by adding new fields, as shown
below:
Project
LS Medical Product
Issue
Table
S_PC_PRDINT_LS
Single Value Fields

New/
Modify
New Field
Name
Join
Column
Text
Length
Type
Common
Name
S_PROD_INT_LSX
COM_DEV_NAME
50
DTYPE_TEXT
For the 'Product Name' field, add the following record in the pickmap:
Pick Maps
New/Modify
Field
Picklist Field
New
Common Name
Common Name
LS Medical Product Issue Business Component

Update the existing "LS Medical Product Issue" Business Component by adding new fields, as shown
below:
Project
LS Medical Product
Issue
Table
S_PRD_CMPLNT_LS
Single Value Fields
New/Modify
Name
Column
Text Length
Type
New Field
Combo Product
COMB_PROD_FL
G
DTYPE_BOOL
New Field
STN Number
PRD_SUB_TRAC
K_NUM
30
DTYPE_TEXT
New Field
PMA Number
PRE_MKT_APPL_
NUM
30
DTYPE_TEXT
38

Single Value Fields
New/Modify
Name
Column
Text Length
Type
New Field
Type of Report 7-day Flag
SEVEN_DAY_RPT
_FLG
DTYPE_BOOL
New Field
THIRTY_DAY_RP
T_FLG
DTYPE_BOOL
LS Medical Product Issue RR Business Component

Update the existing "LS Medical Product Issue RR" Business Component by adding new fields, as
shown below:
Project
LS Medical Product
Issue
Table
S_PRD_CMPLNT_LS
Single Value Fields
New/Modify
Name
Column
Text
Length
Type
New Field
Combo Product
COMB_PROD_FLG
DTYPE_BOOL
New Field
STN Number
PRD_SUB_TRACK_NUM
30
DTYPE_TEXT
New Field
PMA Number
PRE_MKT_APPL_NUM
30
DTYPE_TEXT
New Field
SEVEN_DAY_RPT_FLG
DTYPE_BOOL
New Field
THIRTY_DAY_RPT_FLG
DTYPE_BOOL
LS Medical Related Product Issue Business Component

Update the existing "LS Medical Related Product Issue" Business Component by adding new fields,
as shown below:
Project
LS Medical Product
Issue
Table
S_PRD_CMPLNT_LS
39

Single Value Fields
New/Modify
Name
Column
Text
Length
Type
New Field
Combo Product
COMB_PROD_FLG
DTYPE_BOOL
New Field
STN Number
PRD_SUB_TRACK_NUM
30
DTYPE_TEXT
New Field
PMA Number
PRE_MKT_APPL_NUM
30
DTYPE_TEXT
New Field
SEVEN_DAY_RPT_FLG
DTYPE_BOOL
New Field
THIRTY_DAY_RPT_FLG
DTYPE_BOOL
Symbolic Strings
New/Existing
Name
Current String
Value
Definition
New
SBL_LS_MPI_COMMON_NAME
Common Name
Common Name
New
SBL_LS_MPI_COMBO_PRODUCT
Combo Product
Combo Product
New
SBL_LS_MPI_STN_NUMBER
STN #
STN #
New
SBL_LS_MPI_PMA_NUMBER
PMA/510(k)#
PMA/510(k)#
New
SBL_LS_MPI_7-DAY
7-day
7-day
New
SBL_LS_MPI_30-DAY
30-day
30-day
New
SBL_LS_MPI_DISABILITY_OR_PER
MANENT_DAMAGE
Disability or
Permanent
Damage
Disability or
Permanent
Damage
New
SBL_LS_MPI_CONGENITAL_ANOM
ALY_BIRTH_DEFECT
Congenital
Anomaly or Birth
Defect
Congenital
Anomaly or Birth
Defect
New
SBL_LS_MPI_OTHER_SERIOUS
Other Serious
Other Serious
Applets
In order to implement ACR 372, you must update the following applets:
LS Medical Product Issue-Product List Applet
LS Product Form Applet More Info
LS Medical Product Issue-Adverse Event Info Applet
LS Medical Product Issue-Manufacturer Detail Applet
40

LS Medical Product Issue-Adverse Event Info Applet RR
LS Medical Product Issue-Manufacturer Detail Applet RR
LS Medical Product Issue-Product List Applet

Update the existing LS Medical Product Issue-Product List Applet as shown below. You also need to
add a new List Column to the Applet Web Template.
LS Medical Product Issue - Product List Applet (Modify)
Business Component
Project
LS Medical PI Product
LS Medical Product Issue (SSE)
List Columns
New/Modify
Name
Field
New
Common
Name
Common
Name
Read
Only
String Reference
TRUE
Applet Web Template

Name
Type
Web Template
Edit List
Edit List
Applet List (Base/Edit List)
Applet Web Template Item
New
Name
Control
Type
Comments
Common Name
Common
Name
List Item
In Edit Web Layout, drag and drop this List

Column from Controls/Columns onto the
layout.
LS Product Form Applet More Info

Update the existing LS Product Form Applet More Info as shown below. You also need to add the new
control to the Applet Web Template.
LS Product Form Applet More
Info
Business
Component
Project
Internal Product
Product (SSE)
41

Control (New)
Name
String Reference
Caption
Field
Common
Name
Common
Name
Common
Name
HTML
Icon Map
HTML
Type
Text
Applet Web Template

Name
Type
Web Template
Edit
Edit
Applet Form Grid

Layout
(New)
Name
Control
Expression
Type
Comments
Common Name
Common
Name
Siebel Life
Science
Control
In Edit Web Layout, drag and

drop this List Column from
Controls/Columns onto the
layout.
LS Medical Product Issue-Adverse Event Info Applet

Update the existing LS Medical Product Issue-Adverse Event Info Applet as shown below. You also
need to add the new Controls to the Applet Web Template.
LS Medical Product Issue - Adverse Event Info
Applet
Business Component
Project
LS Medical Product
Issue (SSE)
Control (Label Changes)

Name
Old Caption
String Reference
Caption
Name
Old Caption
String Reference
Caption
OE Disability Flag
Disability
SBL_LS_MPI_DISABILITY_OR_P
ERMANENT_DAMAGE
Disability or
Permanent Damage
OE Congenital
Anomaly Flag
Congenital
Anomaly
SBL_LS_MPI_CONGENITAL_ANO
MALY_BIRTH_DEFECT
Congenital Anomaly
or Birth Defect
OE Other
Other
Other Serious
42

LS Medical Product Issue-Manufacturer Detail Applet

Update the existing LS Medical Product Issue-Manufacturer Detail Applet as shown below. You also
LS Medical Product Issue - Manufacturer Detail
Applet
Business Component
Project
LS Medical Product
Issue (SSE)
Controls
(These are all new controls)

HTML
Icon
Map
Name
String Reference
Caption
Field
HTML Type
STN
Number
STN #
STN Number
Text
PMA
Number
PMA/
510(k)#
PMA Number
Text
Combo
Product
SBL_LS_MPI_COMBO_PRO
DUCT
Combo
Product
Combo
Product
CHECK
Checkbox
Type of
Report - 7day Flag
SBL_LS_MPI_7-DAY
7-day
Type of
Report - 7day Flag
CHECK
Checkbox
Type of
Report 30-day
Flag
SBL_LS_MPI_30-DAY
30-day
Type of
Report - 30day Flag
CHECK
Checkbox
Applet Web Template

Name
Type
Edit
Edit
Web
Template
Applet Form
Grid Layout
(New)1
Name
Control
Item Identifier
Type
Combo Product
Combo
Product
Control
STN Number
STN Number
Control
43

(New)1

Name
Control
Item Identifier
Type
PMA Number
PMA Number
Control
Type of Report - 7day Flag
Type of
Report - 7day Flag
Control
Type of
Report - 30day Flag
Control
1. In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout.
LS Medical Product Issue-Adverse Event Info Applet RR

Update the existing LS Medical Product Issue-Adverse Event Info Applet RR as shown below. You also
Alignment Condition Form Applet
Business Component
Project

RR
LS Medical Product
Issue (SSE)
Control (Label Changes)

Name
Old
Caption
OE Disability Flag
String Reference
Caption
Disability
SBL_LS_MPI_DISABILITY_OR_PERMA
NENT_DAMAGE
Disability or
Permanent
Damage
OE Congenital
Anomaly Flag
Congenita
l Anomaly
SBL_LS_MPI_CONGENITAL_ANOMALY
_BIRTH_DEFECT
Congenital
Anomaly or Birth
Defect
OE Other
Other
Other Serious
LS Medical Product Issue-Manufacturer Detail Applet RR

Update the existing LS Medical Product Issue-Manufacturer Detail Applet RR as shown below. You
also need to add the new Controls to the Applet Web Template.
Alignment Condition Form Applet
Business Component
Project

RR
LS Medical Product
Issue (SSE)
44

Controls
(These
are all are
new
controls)
HTML
Icon Map
HTML
Type
Name
String Reference
Caption
Field
STN
Number
STN #
STN
Number
Text
PMA
Number
PMA/
510(k)#
PMA
Number
Text
Combo
Product
SBL_LS_MPI_COMBO_PRODU
CT
Combo
Product
Combo
Product
CHECK
Checkbox
Type of
Report - 7day Flag
SBL_LS_MPI_7-DAY
7-day
Type of
Report 7-day
Flag
CHECK
Checkbox
Type of
Report 30-day
Flag
SBL_LS_MPI_30-DAY
30-day
Type of
Report 30-day
Flag
CHECK
Checkbox
Applet Web Template

Name
Type
Web Template
Edit
Edit
Applet Form Grid

Layout
(New)1
Name
Control
Item Identifier
Type
Combo Product
Combo
Product
Control
STN Number
STN Number
Control
PMA Number
PMA Number
Control
Type of
Report - 7day Flag
Control
45


Name
Control
Type of
Report - 30day Flag
(New)1
Item Identifier
Type
Control
1. In Edit Web Layout, Drag and Drop this List Column from Controls/Columns onto the layout.
Reports/Subreports
Update the existing "LS Medical Regulatory Report 3500A" report by adding new fields as shown
below:
Project
LS Medical Report
BusComp
LS Medical Product
Issue RR
Report Fields
New/Existing
Fields
New
Combo Product
New
STN Number
New
PMA Number
New
New
Update the existing LS Medical PI Product report by adding new fields as shown below:
Report Fields
New/Existing
Fields
New
Common Name
Data Map Administration

1
Log in to the Siebel Application as SADMIN.
From the site map, navigate to Application Administration screen > Data Map Administration.
Query for "LS Medical PI Create Related PI" and "LS Medical PI Populate Report - 3500A".
46

Add the new Data Map Fields as shown below:

Data Map Object
Name
Source Business Object
Destination Business Object
LS Medical PI Create Related PI
Data Map Component

Name
Source Business Component
Destination Business Component
Product Issue
Data Map Field
(These are all new field maps)
Source Type
Source
Destination Type
Destination
Field
Combo
Product
Field
Combo Product
Field
STN Number
Field
STN Number
Field
PMA Number
Field
PMA Number
Field
Type of
Report - 7day
Flag
Field
Type of Report - 7-day Flag
Field
Type of
Report - 30day Flag
Field
Data Map Object

Source
Business
Object
Name
LS Medical PI
Populate Report 3500A
LS Medical
Product Issue
Destination Business
Object
Data Map Component

Name
Source Business Component
Destination Business Component
Report
LS Medical Product Issue RR
47

Data Map Field
(All are new field maps)

Destination
Type
Destination
Combo
Product
Field
Combo Product
Field
STN Number
Field
STN Number
Field
PMA Number
Field
PMA Number
Field
Type of
Report - 7day
Flag
Field
Field
Type of
Report - 30day Flag
Field
Source Type
Source
Field
Configuration Instructions for ACR 373C

This topic contains detailed information about the functionality provided by ACR 373, as well as
instructions for implementing the ACR.
Fully-Qualified Domain Name (FQDN) Implementation

Starting with Microsoft Exchange Server 2003 SP1, the full SMTP address can be used to access a
user's mailbox.
In addition to being able to send the URI as:
http://SERVER/exchange/jpai/
Users can now also send the URI as:
http://SERVER/exchange/jpai@example.com/
Using this approach allows virtual directories on a front-end server to support multiple SMTP domains
and eliminates the need for matching virtual directories on the mailbox server.
Administrators can now change the configuration settings in the Siebel application for full SMTP
address (Fully Qualified Domain/Mail Name) support. User can opt to use the existing SMTP AddressLeft-Hand-Side (LHS) to access a users mailbox.
This configuration is at the Exchange level/System level and is applicable across all users and for the
Calendar domain.
There is now a new configuration parameter called 'UserMailBoxIDSource' for the connector. To
access this parameter, from the Siebel application menu, navigate to Site Map > Administration-PIM
Server Integration > Exchange 2000/2003 Profile.
48

The 'UserMailBoxIDSource' parameter can have values EMAILFULL or EMAILLEFT as the values. Not
having this parameter will be considered default and default behavior will be EMAILLEFT.
The Administrator adds the 'UserMailBoxIDSource' configuration parameter in the Calendar section,
as shown in the following table:
Section
Parameter
Value
System-Wide Parameter
Calendar
UserMailBoxIDSource
EMAILLEFT
Server-Wide Parameter
Calendar
Exchange Server Map
Exchange Server
ExchPIMSI01
UserMailBoxIDSource
EMAILFULL
This parameter can be configured in two ways:
System-wide. The System-wide parameter sets this value across all the Exchange Servers.
This setting is helpful when customers have a large number of Exchange Servers running and
the majority or all of them use Fully Qualified Domain Name to locate mailboxes.
Server wide (Referring to Exchange Servers). The Server-Wide parameter will set the value
for a particular Exchange Server.
For a particular Exchange Server, if the "Server wide parameter" is present, the Exchange Server will
use that. If not, then the Exchange Server will use the System-Wide parameter. If there is no value
for System-Wide parameter, then the default (EMAILLEFT) will be used.
This configuration parameter will be read while initializing the connector. During synchronizing the
calendar data, this configuration parameter's existence will be verified. If the parameter does exist,
then the URI (Uniform Resource Identifier) will be formed with corresponding value (FULL or LHS).
Otherwise, by default, the LHS of the email id will be used to form the URI.
Scripts Change for the "Send As" Permission

Previously, the "Send As" permission was implicitly included in the "Full Mailbox Access" permission.
This behavior has now been changed to allow granting "Full Mailbox Access" without having to also
allow "Send As."
Microsoft implemented this in the following versions of Exchange Server 2003:
Microsoft Exchange Server 2003 Service Pack 1 with a Store.exe file version of 7233.51 or
higher
Microsoft Exchange Server 2003 Service Pack 2 with a Store.exe file version of 7650.23 or
higher
Prior to this change, any user with the "Full Mailbox Access" permission for a mailbox also had the
ability to "Send As" the mailbox owner.
As part of SSSE installation, the ssse_exchange2k3_permissions.vbs script is run to provide
permissions to user/s. The modified VB script will also enable the "Send As" permission. Users who
have the "Full Mailbox Access" permission will also be updated with the "Send As" permission through
this script.
49

Use the following procedures to edit and run the script.
To edit and run the script

1
Open the script in edit mode in any text editor.
Grep ServiceUserName = "QA\qauser"
Update it to appropriate domain and admin user (domain\admin)
Save the file.
To run the script

1
Copy the script and map text file to another location and navigate to that location though the
command prompt.
Run the script with the appropriate parameter:

ssse_exchange2k3_permissions.vbs map.txt Y
or
ssse_exchange2k3_permissions.vbs sendas@qa.test.com Y
For full mail box access permission only: Only one parameter is required, which will be either the
user's mail id or the name of text file that has the list of users who will get full mail box
permission. (This is the current functionality.)
For the "Send As" permission with full mail box access permission: Two parameters need to be
passed. The first parameter will be the same as what was passed above, and the second
parameter will be any character (Just indication for Send As).

Use the following instructions to implement ACR 374.
Change the Internet SMTP/POP3 Server driver profile by navigating to Administration Communications > Communication Drivers and Profiles > Communications Drivers: Name =
Internet SMTP/POP3 Server and changing the 'Library Name' from 'sscmpop3' to 'sscmmail'.
Add a new Internet SMTP/IMAP Server driver profile by navigating to Administration Communications > Communication Drivers and Profiles > Communications Drivers, and adding
a new record with the following values:
Name: Internet SMTP/IMAP Server
Channel Type: Email
Inbound: checked
Outbound: checked
50

Channel String: IMAPSMTP
Library Name: sscmmail
For the new record created in Step 2, add the following records under the Administration Communications > Communication Drivers and Profiles > Communications Drivers > Driver
Parameters applet:
Default
Value
Sl No
Name
Charset
Convert Incoming To Plain Text
FALSE
Create Plain Text From HTML
FALSE
Delete Processed Messages
TRUE
Delivery Status Domain
Delivery Status Mailbox
Enable SSL for Backup SMTP
FALSE
Enable SSL for IMAP
FALSE
Enable SSL for SMTP
FALSE
10
Failed Email Directory
11
From Address
12
Incoming Email Directory
13
LogDebug
FALSE
14
Loopback Detection Interval
90
15
Loopback Email Directory
16
Max Line Length
17
Max Parsing Threads
18
Max Sends Per Session
19
Min Parsing Threads
20
IMAP Account Name
21
IMAP Account Password
22
IMAP Server
23
IMAP Server Port
143
24
IMAP Timeout
60
25
Parse Embedded Messages
TRUE
26
PollingInterval
30
27
Priority
Normal
Required
YES
51

Sl No
Name
Default
Value
28
Process If Loopback Detected
TRUE
29
Processed Email Directory
30
Reply-To Address
31
Return Attachments
32
SMTP Account Name
33
SMTP Account Password
34
SMTP Backup Account Name
35
SMTP Backup Account Password
36
SMTP Backup Server
37
SMTP Backup Server Port
38
SMTP Server
39
SMTP Server Port
25
40
SMTP Timeout
60
41
Save Sent Messages
FALSE
42
Sent Email Directory
43
Siebel Server
44
Use EHLO
TRUE
45
text/html encoding
Auto
46
text/plain encoding
Auto
Required
TRUE
25
YES
Add the java subsystem parameter for EMR by navigating to Administration - Server
Configuration > Enterprises > Profile Configuration applet and adding a new record with the
following values:
Profile: EMRJavaSubsys
Alias: EMRJavaSubsys
Subsystem Type: JVMSubSys
Description: EMR Java Subsystem Parameters
Under "Profile Parameters" for the applet created in Step 4, update the following records:
52
JVM Classpath: Absolute path of the following Siebel and JavaMail jar files:
Siebel JAR file: JMailClient.jar
Java JAR files: mail.jar (javamail), activation.jar (jaf) and rsajsse.jar (ssl)
JVM DLL Name: Absolute path of the jvm.dll in the machine

JVM Options: Any required options:
For increasing working memory for JVM: -DXmx512m (change the 512 number to specify
a different value)
For specifying the SSL certificate files: -Djavax.net.ssl.keyStore and Djavax.net.ssl.trustStore
Typical values for the developer debug servers are:
JVM DLL Name: M:\siebel\src\3rdparty\java50\w32\jre\bin\client\jvm.dll
JVM Classpath:
C:\debug_builds\siebel\classes\original\JMailClient.jar;M:\siebel\src\core\mgtserver\3rdpa
rty\javamail\mail.jar;M:\siebel\src\core\mgtserver\3rdparty\jaf\activation.jar;M:\siebel\sr
c\core\mgtserver\3rdparty\rsa-ssl-j-4.1.6\rsajsse.jar
JVM Options:
-DXmx512m Djavax.net.ssl.keyStore=M:\siebel\src\3rdparty\java50\w32\jre\lib\security\jssecacerts Djavax.net.ssl.trustStore=M:\siebel\src\3rdparty\java50\w32\jre\lib\security\jssecacerts
The rsajsse.jar and ssl jvm options are only needed if the SSL is being used for IMAP.

Use the instructions in the subtopics that follow to configure ACR 378. This topic contains procedures
for configuring Siebel Business Applications for Identity Search Server and for configuring Identity
Search Server. For more information, see Siebel Data Quality Administration Guide, which is available
on the Siebel Bookshelf on Oracle Technology Network (OTN) at http://www.oracle.com/technology/
documentation/siebel.
Configuring Siebel Business Applications for Identity Search Server

Use the following procedure to configure Siebel Business Applications for Identity Search Server.
To configure Siebel Business Applications for Identity Search Server

1
Import the Business Service, Integration Objects and Workflow .sifs from the 'Repository Files'
folder.
Compile the Business Service and Integration Objects into the .srf file, and publish and active
the workflows. For more information, refer to the procedure "To configure your Siebel Business
Application for Identity Search Server" within Appendix E of Siebel Data Quality Administration
Guide.
Copy the ssadq_cfg.xml file to the siebsrvr\SDQConnector folder.
Edit the file and modify the 'iss_host' and 'rulebase_name' parameters.
53

Copy the platform-specific ISS driver from the 'ISS Connector Dlls' folder to the siebserv\bin\enu
folder on the Windows platform or to the siebserv\lib on the Unix platform.
Configure the vendor parameter and field mapping in the Siebel application as detailed in the
"Configuring the Siebel Business Application for Identity Search Server" section within Appendix
E of Siebel Data Quality Administration Guide.
Follow the instructions detailed in the "Siebel Business Application Action Sets for Account,"
"Siebel Business Application Action Sets for Contact," "Siebel Business Application Action Sets
for List Mgmt Prospective Contact," and "Siebel Business Application Generic Action Sets"
sections within Appendix E of Siebel Data Quality Administration Guide.
Modify the 'URL' and 'File Path' in the Actions. For more information, refer to Siebel Data Quality
Administration Guide.
Configuring Identity Search Server

Use the following procedure to configure Identity Search Server.
To configure Identity Search Server

1
Modify the SQL in the 'Sample SQL for Oracle' folder to your specific database (such as MSSQL
or DB2).
Log in as the DBA and run the first and fifth SQL to create a user with special privileges (such as
ssa/SIEBEL).
Log in as this new user and run the remaining SQL to create the IDT/IDX and Update Sync tables.
Install ISS Server in the following sequence:
NAME3 (2.7.0.4)
ISS (2.7.0.4)
IDSFixcd081
IDSFixcd83
FixK066g
FixK104
Obtain the license key and copy it to the Installfolder\ids\nm32704\pr folder.
Edit the idsenvs.bat file in the Installfolder\ids\iss2704s\bin folder:
Uncomment the lines: Set SSA_XSHOST and set SSA_XSPORT.
Add a line to set rulebase name (e.g. Set SSA_RBNAME=odb:0:ssa/SIEBEL@Target).
Add an environment variable SSA_RB_RESTART_ID=0, to prevent the rule base from

occasionally locking.
Copy the odbc.ini file to Installfolder\ids\iss2704s\bin folder.
Modify the server parameter in odbc.ini file for your ODBC connectString.
10 Copy the SiebelDQ.sdf file to the Installfolder\ids\iss2704s\ids folder.

54

11 Start the IDS Server.

12 Start the IDS Console Client (Admin Mode).
13 Create a new system using the sdf file above.
14 Select this system as default system, if it is not already selected.
15 In the Siebel client application, modify a Data Quality Setting to trigger the ISSLoad process.
This process will export Account/Contact/Prospect records from the Siebel database to .xml files.
The filename and location is specified in the Action Sets ISSLoad in the Siebel application.
16 From the IDS Console Client/System, run LoadIDT using the xml data files generated above.
17 From the IDS Console Client/Tool, start the synchronizer process.

ACR 385 provides three new methods in the "SiebelUserProfileService"Business Services to allow
users to manipulate the current login user without having to logout/login:
SetContactContext: This method changes the current login user and provides one input
argument which is the Id (not Login) of the user to change to.
ResetContactContext: This method changes the current login user to what it was before the call
to SetContactContext. This method does not contain input or output arguments.
IsContactContextSwitched: This method determines whether the current login user has changed
as a result of a call to SetContactContext, and it contains one output argument, which is 'Y' or
'N' depending on whether the login user has changed.
To see logging of SetContactContext and ResetContactContext, please use ObjMgrSessionLog=3 or

higher. In Siebel Server enter the following command:
change evtloglvl ObjMgrSessionLog=3 for component <?>
The repository change for ACR 385 is optional, because when you invoke a business service method,
the Object Manager does not check if the method exists in the repository. Instead, the Object
Manager tries to invoke the method in the Business Service directly, and if the Business Service does
not handle the method, the Object Manager throws an error.
You can add the SetContactContext, ResetContactContext, and IsContactContextSwitched methods
to the Business Service. If you do not add these methods, then:
If the required argument to "SetContactContext" is missing, then you get an error that the usercontext could not be established. If you perform the repository change, then the error would be
that the required input argument to "SetContactContext" is missing.
If you design a workflow that calls a business service method, the method pick applet will not
show the method. However, you can still type in the method name, as the pick applet is
unbounded.
55

The following repository changes add the SetContactContext, ResetContactContext, and

IsContactContextSwitched methods.
To implement ACR 385

1
Within Siebel Tools, navigate to Business Service, and locate the "SiebelUserProfileService"
Business Service.
Navigate to Business Service Method, and create a new record with the following values:
Name="SetContactContext"
Display Name="SetContactContext"
Create a new Business Service Method Argument with the following values:
Name="Login Id"
Type="Input"
Storage Type="Property"
Data Type="String"
Optional=FALSE
Display Name - String Reference="SBL_LOGIN_ID-1004231308-3PG"
Create a new record with the following values:
Name="ResetContactContext"
Display Name="ResetContactContext"
Create a new record with the following values:
Name="IsContactContextSwitched"
Display Name="IsContactContextSwitched"
Create a new Business Service Method Argument with the following values:
Name="Value"
Type="Output"
Storage Type="Property"
Data Type="String"
Optional=FALSE
Display Name - String Reference="SBL_VALUE-1004224800-2W7"

The subtopics that follow contain procedures for implementing ACR 415.
56

Configuration Instructions for FR 12-1OI3OHA

1
Navigate to Administration > PIM Server Integration > Configuration.
Select the Siebel profile.
Set the values as follows:
Section: Siebel
Parameter: InboundCalendarOnly
Value: Y
Configuration Instructions for FR 12-1MQBYBK

1
Select the Exchange Calendar profile.
Create a record with the following values:
Section: Archive
Parameter: ArchiveGracePeriod
Value: 5 (in days)
Configuration Instructions for FR 12-1OJ2H2C

This feature enhances SSSE to allow ExtractStartDate to be specified on a per-user basis. This
subtopic contains instructions for enabling this feature.
Select the Siebel profile, as shown in the following table:

Section
Parameter
Value
System default
parameter
Siebel
ExtractStartDate
01/01/1980
User specific
parameter
UserLevelExtractStart
Dates
RBROWN
12/20/1996
UserLevelExtractStart
Dates
MSTERN
01/04/2008
NOTE: The system default will be used for all users who do not have a user-specific record
specified.
NOTE: The date format for the user-level extract start dates should use the formatting specified
in the following example:
Section: Siebel
Parameter: ExtractStartDateFormat
57

Value: MM/DD/YYYY
Configuration Instructions for FR 12-1OJ2H75

With this enhancement, the administrator can be notified by email whenever inbound synchronizing
fails due to certain EAI-specific errors.
The administrator is notified about the following errors:
Error List:
Duplicate Conflict: One or more records with the same key already exist.
Missing required field: One or more required fields of this record are empty.
Record does not exist: The record cannot be deleted because it does not exist.
Data Type Validation error: The value entered for one or more fields of this record is not
compatible with the fields declared data type.
Overflow: The number of characters entered for one or more fields of this record exceeds
their declared data length.
Unicode to code page conversion error: One or more fields of this record have characters that
are not compatible with this DB code page.
Alarm trigger time passed: The Alarm flag is checked for a past appointment.
Bounded picklist validation error: One or more picklist fields of this record have a value that
is not part of bounded picklist.
Configuration
System Alert Configuration:
You must perform the following configuration to enable this feature.
Go to Administration > Server Configuration > Enterprise > System Alerts.
Create an alert definition (such as Administrator Email Alerts) with the following alert
parameters:
Alert Definition
Name
Administrator Email
Alerts
Alias
Media
AdminEmailAlert
EmailNotification
Description
Create alert parameters as described in the following table:

Parameter Name
Value
SMTPServer
64.181.243.112
SMTPServerPort
25
58

Parameter Name
Value
AdminEmailAddress
sseadmin@sdcexch02.siebel.com
Fromaddress
sseadmin@sdcexch02.siebel.com
DLLName
ssemailntfy
Email Template Configuration:

The administrator can define the email body template in the application as necessary. This requires
the following changes in the administration view:
To define the email body template

1
Navigate to Administration PIMSI Server Integration > Configuration, and enter the following
values:
Profile: Exchange Calendar
NOTE: The Domain name should be the same as the Domain Identifier field in Administration > PIM
Server Integration > PIM Domains (such as IPM Task).
Section
Parameter
Value
Email Template:
Domain Name
MsgBody1
Body of the email

with place holders.
The supported place
holders are:
Description
1.%Domain% - Name
of the domain is
substituted
2. %login% - Name of
the login is
substituted
3. %ErrorMessage% Description of the
error
4. [Field Name]
Substitutes value of
the field name in the
parentheses
EmailTemplate:
Domain Name
MsgBody2
...Add email body as

specified above
For instance, if the email message needs to be configured for the Task domain, the following can be
configured.
59

Section
Parameter
Value
Email Template:
IPM.Task
MsgBody1
\n SSSE fails to
synchronize
%domain% record for
the sync enabled user
%login% \n
Description
The record has the

following
characteristics \n
Subject: [Subject]
Start Date: [Start
Date]
End Date: [Due Date]
\n The error
Email Template:
IPM.Task
MsgBody2
%ErrorMessage%
Assume the following substitution values:

Domain = IPM.Task
Login = GABBO
Subject = Meeting in the month of March
Start Date = 3/3/2008
Due Date= 3/5/2008
Error Message = One or more required fields are missing.
With the preceding data, the final email message looks like the following:
SSSE fails to synchronize IPM.Task record for the sync enabled user GABBO
The record has the following characteristics
Subject: meeting in the month of March
Start Date: 3/3/2008
End Date: 3/5/2008
The error Message was: One or more required fields are missing.
To increase the maximum notification size to allow large mails, use the following procedure:
Set Notify message size to 1024.
60

Srvrmgr> change param NOTIFYMSGSIZE=1024 for server <servername>.

NOTE: If the message size is not increased, the system sends a smaller message with fewer details.
Configuration Instructions for FR 12-1OI3OM6

Refanning of recurring appointments with no end date: In the previous design, whenever a
recurring appointment was created with the "No end date" option in Exchange, SSSE created limited
records in the Siebel database based on the configured parameters set in the Siebel database.
However, after that, SSSE did not create any more occurrences for that meeting. This feature
enhances the SSSE product to have the ability to refan new records at regular intervals to reflect the
same behavior as Exchange.
Use the following procedure to configure this fix:
To create the refanning job

1
Go to Administration Server Configuration.
Click on Job Templates.
Create a new Job Template with the following values:
Set Name = Refan
Short Name = Refan
Component = PIMSI Dispatcher
Component Type = BusSvcMgr
Business Service (TRUE)
Enabled? (TRUE)
Create the Job Parameter for the created template as follows:
Name = Encoded Input Arguments
Abbreviation = EncodedArgs
Value = Refan
To run the refanning job

1
Go to Administration Server Management.
Click on Jobs.
Click New.
Click on Component/Job and select Refan.
Click Go.
61

Repository Changes
Create a new column in the S_SD_PIM_ROW table using the following procedure.
To create a new column in the S_SD_PIM_ROW table

1
Open Siebel Tools.
Navigate to Tools Options and click on Lock Project.
Navigate to Table and search for S_SD_PIM_ROW.
Go to Column.
Create a new record (column) called "X_CAL_REPEAT_PATTERN" with the following values:
Field Name "Change" = True
User Name= "Cal Repeat Pattern Ext"
Type = "Extension"
Nullable = True
Physical Type = Varchar
Length = 500
Cascade Clear = Ignore.
Transaction log code: True
Status = Active.
Apply the changes for the table.
To configure the Business Component

1
Navigate to Business Component and search for the PIMSI PIM row
Navigate to the field.
Right-click on the field and click on New Record.
Set the name as "Cal Repeat Pattern".
Click on Column and select the "X_CAL_REPEAT_PATTERN" created previously.
Compile and deploy the SRF.
Changes in Siebel Application Configuration (Profile Change)

Profile name: Siebel Calendar
Section name: SupportedFan
Parameter: MultipleEntry
Values: 1 or 0, [1 for supported pattern behaves like unsupported (creates multiple entries). If the
value is set to 0, the application will behave in the old manner].
62

Section name: FanLimit

Parameter: DaysinNumber
Values: Number of days (The End Date value is calculated based on this number. For example, if Start
date is Mar 10, 2008 and the number of days value is 20, then the end date is Mar 30, 2008. So
based on this, end date record(s) are created. As time passes, additional records will be generated
to ensure that there will always be 20 days worth of appointments.)
To create a new entry

1
Click on Site Map.
Go to Administration Integration.
Go to Data Map Editor (Integration Object Map).
Select "PIMSI Calendar Outbound Map" in Data Map Editor.
Right-click on "PIMSI Calendar Outbound Map".
Click Copy Record (Ctrl + B).
Name the new record "PIMSI Calendar Outbound Refan Map".
Select this new entry.
Navigate to Integration Component Map (located below IntegrationObject Map).
10 Select "Action_CalendarAppointment", navigate to the Precondition column, and reset its value
(make it empty).
Important Notes:
This refanning feature will work only for new recurring appointments or updates that come
from Exchange.
While running the refan job, make sure that the dispatcher job is not running at the same
time. Having both jobs running at a same time causes a conflict and may introduce errors.

Siebel Communications Guide Addendum provides further information about integrations of Siebel
Communications with applications for managing billing and revenue. To access Siebel
Communications Guide Addendum, see the Siebel Bookshelf, log into OracleMetaLink 3 at https://
metalink3.oracle.com/ and search for Doc ID 604523.1.
Use the instructions in the following procedure to implement ACR 428.
Go to the Siebel Tools installation directory <Tools Install Directory>\REPPATCH.
63

Unzip the file ACR428.zip file.

This will create the following directory structure:
<Tools Install Directory>\REPPATCH\AIA2.0+2.0.1\
The AIA2.0+2.0.1 folder that you create will contain the following subfolders:
\DMGSchemaChanges.
\Seed Data.
\SifFiles
\WebTemplate
\WF
\LMU
\ACR428_8005fp_addendum
The following instructions refer to the folders specified above.
Apply the schema changes to the Server Database from the DMGSchemaChanges folder using
the instructions below:
The DMGSchemaChanges folder contains the Modified Tables.sif file. The Modified Tables.sif file
contains the following tables:
New table:
S_PRO_CFG_ITEM
Modified tables:
64
S_INV_PROF
S_ORG_EXT
S_DOC_QUOTE
S_QUOTE_ITEM
S_ORDER
S_ORDER_ITEM
S_ASSET
S_QUOTE_ITEM_OM
S_ORDER_ITEM_OM
S_PROD_REL
S_INVC_ADJ_ITEM
S_INVOICE_ADJ
S_INVOICE
S_INVOICE_ITEM

S_INVC_ITM_DTL
S_PROM_PMTRX
S_PROD_INT
In order to implement ACR 428, you must import the Modified Tables.sif file into the repository.
Before you import the Modified Tables.sif file, lock the following projects:
CUT Newtable
EIM AdjustmentGroup
EIM Asset
EIM Common SIA
EIM Invoice
EIM Order
EIM Product
EIM Quote
Table Asset
Table Invoice
Table NetworkOrderManagement
Table Order
Table Organization
Table Party
Table Product
Table ProductPromotion
Table Promotions
Table Quote
Use the Siebel Tools - Import from Archive function to read the Modified Tables.sif file and create
the tables in the repository. The "merge" option should be used while importing this file.
To create the Modified Tables.sif table on the physical database, use Siebel Tools to query for the
list of tables that were imported into the repository, and click the "Apply/DDL button to apply the
changes to the physical database.
You must have imported the tables into the repository before you apply the changes to the
physical database.
Import Seed Data from the SeedData folder using the following procedure:
Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC) to
create an ODBC entry for the database into which you plan to import the seed data.
Navigate to the System DSN tab, and click Add.
Select the "Siebel Oracle90" driver (from Datadirect Technologies).
65

Enter a data source name, such as DevelopmentDB.
Enter the server name to connect to. For Oracle, enter the TNS service name that you created
to connect Siebel Tools to the database.
Test your connection and click OK when tested successfully.
Navigate to the directory where you installed Siebel Tools and change it to the
REPATCH\AIA2.0+2.0.1 directory.
NOTE: Before executing the next step in this series of procedures, make sure that the
dataimp.exe file exists in the <Tools Install Directory>/bin directory.
Depending upon the language that you are installing, run the commands listed in Step 5 or
Step 6.
Run the following command if you are an ENU customer:

<Tools Install Directory>\bin\dataimp /u SADMIN /p sadmin /f <Tools Install
Directory>\REPATCH\AIA2.0+2.0.1\SeedData\seed_barcelona.dat /l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools
Install Directory>\REPATCH\AIA2.0+2.0.1\SeedData\seedupg_barcelona_imp.inp /q -1 /w y
/e n /t n /x R /n 100 /h log
<Tools Install Directory> - Replace with your Siebel Tools install directory.
<ODBC Source Name> - Replace with the ODBC name you created in the previous steps.
Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that
the import completed successfully.
Use the following procedure to import seed date if you are using a language other than ENU:
Import two .dat files - seed.dat and seed_locale_XXX.dat, where XXX is the language code.
There will also be two .inp files called seedupg_barcelona_imp.inp and
seedupg_barcelona_imp_locale.inp.
Run the following command for seed.dat:

Directory>\REPATCH\AIA2.0+2.0.1\SeedData\seed.dat /l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools
Install Directory>\REPATCH\AIA2.0+2.0.1\SeedData\seedupg_barcelona_imp.inp /q -1 /w y
/e n /t n /x R /n 100 /h log
<ODBC Source Name> - Replace with the ODBC name created in the previous steps.
66

Run the following command for seed_locale_XXX.dat:

Directory>\REPATCH\AIA2.0+2.0.1\SeedData\seed_locale_xxx.dat /l <Tools Install
Directory>\temp\dataimp_seed_lang.log /c <ODBC Source Name> /d <Table Owner> /i
<Tools Install
Directory>\REPATCH\AIA2.0+2.0.1\SeedData\seedupg_barcelona_imp_locale.inp /q -1 /w y
/e n /t n /x R /n 100 /h log
<ODBC Source Name> - Replace with ODBC name created in the previous steps.
Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that
the import completed successfully.
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 parameter needs to be X_ for Siebel Customers.
SymStrPrefix = SBL_
..
NOTE: After changing the tools.cfg file, log out of Siebel Tools and log in again to apply the
changes.
Within Siebel Tools, select the Tools > Import From Archive option to import the following SIF
files from the SIFFiles folder into Siebel Tools. Use the Merge option in Import Wizard.
CMU Billing BC.sif
CMU Billing Integration.sif
CMU Billing Product.sif
CMU Billing UI.sif
Product Integration.sif
In Siebel Tools, lock all the following projects:
CMU Billing BC
MACD Performance
Order Entry
Picklist
Price List
Pricer
Product
67

Product (SSE)
Product Data Services
Product Selection UI
Quote
Quote (UI)
Row Set Transformation Toolkit
SIS OM Base Architecture
Siebel Workflows - Seed
Symbolic Strings
VEAI CUT Billing Integration
VERT CUT Address
VERT CUT Common
VERT CUT Screens
eService Billing
Web Channel Order Management
10 Import the rest of the SIF files from the SIFFiles folder into Siebel Tools using the Tools 'Import
From Archive function.
Make sure to choose Merge Option in Siebel Tools Import Wizard.
Import the following SIF files:
ModifiedApplets.sif
ModifiedBC.sif
ModifiedBO.sif
ModifiedBS.sif
ModifiedIO.sif
ModifiedLink.sif
ModifiedPickList.sif
ModifiedScreen.sif
ModifiedViews.sif
ModifiedApplication.sif
ModifiedSymStrings.sif
11 The following steps are only necessary for customers who are installing languages other than
ENU:
68
Select Tools > Utilities > Locale Management to import LMU Files for the specific language from
the LMU folder into Siebel Tools.

Select Source Language = English American.
Target Language = <Specific Language>.
Click on Import Tab > Browse to locate the LMU file you want to import and click Import.
12 Stop Siebel Server if it is running.

13 Compile all the projects using Tools > Compile Projects and selecting the "All Projects" option,
and save the .srf file to <Siebel Server Install folder>\objects\ENU\siebel_sia.srf on the installed
Siebel server.
14 Copy the Web Template file ccview_parentdetails.swt from folder WebTemplate into Siebel Server
<Siebel Server Install folder >\WEBTEMPL.
15 Start the Siebel Server.

16 Import the workflows listed in the following table into the Siebel application.
NOTE: All new workflows should be imported into the CMU Billing Integration project. All of the
existing workflows should be imported. In other words, the modified workflows should be
imported into the corresponding projects. All of the SIS OM * workflows except SIS OM Add
Quote Service Charge Sub-Process and SIS OM Add Order Service Charge Sub-Process should
be imported into the SIS OM Base Architecture project. The workflow Pricing Procedure Calculate Net Price should be imported into the project Row Set Transformation ToolKit project.
Workflow Name
New/Modified
Project
CMU Account Sync Workflow
New
CMU Billing Integration
CMU Address Sync Workflow
New
CMU Adjustment View Sub Process
New
CMU Contact Sync Workflow
New
CMU Profile Sync Workflow
New
CMUBalanceDetailsEventAdjustmentWF
New
CMUEventDetailsAdjustmentWF
New
CMUEventDetailsQueryWF
New
CMUInvoiceAdjustmentWF
New
CMUInvoiceQueryWF
New
CMUItemChargeAdjustmentWF
New
CMUItemChargeQueryWF
New
Pricing Procedure - Calculate Net Price
Modified
Row Set Transformation

Toolkit
SIA External Integration Process
New
SIS OM Active Order Sub-Process
Modified
SIS OM Active Quote Sub-Process
Modified
69

Workflow Name
New/Modified
Project
SIS OM Add Order Service Charge SubProcess
New
SIS OM Add Quote Service Charge SubProcess
New
SIS OM Disconnect Asset Sub-Process

(Updated for nested service bundle
changes)
Modified
SIS OM Disconnect Products & Services

Process
Modified
SIS OM Modify Products & Services

Process
Modified
SIS OM Move Process (Updated for

nested service bundle changes)
Modified
SIS OM New Products & Services Process
Modified
SIS OM Suspend / Resume Asset SubProcess (Updated for nested service

bundle changes)
Modified
SIS OM Suspend / Resume Products &

Services Process
Modified
SIS OM UpdateOrderItem
New
SIS OM Submit Order Process
Modified
SIS OM Order Line Item Update

Main(New workflow for nested service
bundle changes)
New
SIS OM Add Service Charge Quote SubProcess (New workflow for nested
service bundle changes)
New
SIS OM Add Service Charge Order SubProcess (New workflow for nested
service bundle changes)
New
SIS OM Add Service Charge Sub-Process

(New workflow for nested service bundle
changes)
New
SISOMBillingSubmitOrderWebService
New
SIS OM NSB Update Order Line (New

workflow for nested service bundle
changes)
New
70

Workflow Name
New/Modified
Project
SIS OM Edit Complex Asset Workflow

(Updated workflows for nested service
bundle changes)
Modified
SIS OM Edit Delta Quote Line Item

bundle changes)
Modified
SIS OM Edit Service Order Line Item

bundle changes)
Modified
CMU SIA Submit Adjustment Request to

External
New
Select Workflow Process in Siebel Tools Object Explorer.
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 table above to know which project
these workflows need to be imported into.
Check the status of the Workflow process. If it is In-Progress, then make it complete by
deploying the Workflow process by clicking on the Deploy button.
CAUTION: Do not click the "Deploy+ Activate" Button, as doing so will yield an error
message.
For version 8.0 and above, the button to change the workflow status to complete is Publish/
Activate. To view this button, select View > Tool Bar > Workflow/Task Editor to make the WF
status as complete are "Publish/Activate" - To view this button click on View > Tool Bar> WF/
Task Editor. If you receive an error message, note the workflows that have failed and
manually activate these workflows in the application.
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.
Repeat Step b and Step c for of all the workflows in the folder.
Log in to the Siebel application as an administrator.
Navigate to the Site Map.
Click on Administration - Business Process.
Navigate to Workflow Deployment ' Repository Workflow Process.
Query for the workflow processes and activate.
17 Modify the run time events for promotions:

a
Navigate to the Administration - Runtime Events screen.
Click on the 'Action Sets' view. This shows three applets.
In the first applet, called 'Action Sets', search for the Action Set 'Cache Refresh BC - ISS
Promotion Pricing Components List Applet'.
71

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.)
18 Restart the Siebel Server.

19 Launch the Siebel Communications application.
Postinstallation Instructions for ACR 428

You must perform the procedures in this subtopic after you have configured ACR 428.
Defining the End-Point URL for ABS and Siebel Inbound Web Services
Use the following procedure to define the end-point URI for ABS (Outbound Web Services) and Siebel
Inbound Web Services:
To define Outbound Web Services

1
Log into the Siebel application as an administrator.
Navigate to the Site Map.
Click on Administration - Web Service >Outbound Web Services.
Query for the Name= *ABCS*.

Five records will appear.
Navigate to the Service Ports list applet and change the URI provided by the ABS team.
Query for *JMS* and change the URI.

Example: http://ap6039fems.us.oracle.com:7797
To define Inbound Web Services

1
In Administration - Web Services > Inbound Web Services, make sure that the corresponding
Web Services are Active. If not, change the Status from "Inactive" to "Active", and click the Clear
Cache button.
NOTE: Query for these inbound web services using QBE: *CMU* OR *ISS* OR *Update Order*
OR *SWI Update*
Query for Name = CMU Account Update.
72

In the middle Inbound Service Ports list applet, change the Address port.
Address: (example only) http://sdchs20n513.corp.siebel.com/eai_enu/
start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute&UserName=SADMIN&Pass
word=MSSQL
NOTE: Replace string <web server>, <lang>, <UserName>, <Password> with the correct data
based on the server information.
Repeat Step 3 for Name = CMU Account Query Service.
Setting Up Order Creation

Use the following procedure to enable component groups.
NOTE: Bounce the server after you have enabled the compgrp and synchronized it.
To enable component groups

1
Navigate to Site Map > Administration - Server Configuration > Enterprises > Component
Groups.
Query for each of the following Component Groups and if Enable State = Disabled, click
<Enable>:
SIA
Siebel CME [Alias- Communications]
Siebel ISS [Alias- ISS]
Communications Management [Alias- CommMgmt]
Workflow Management [Alias- Workflow]
EAI
After enabling the necessary components, navigate to Site Map > Administration - Server
Configuration > Enterprises > Synchronize.
Select all the records and click the Synchronize button.
Windows
Log in to the machine with the credentials.
From Start - Run, type cmd.
Find the drive that the build is installed on.
Type <Build>ses\siebsrvr\bin.
Execute the following command:

srvrmgr /e <Enterprise Server Name> /s <Siebel Server Name> /g <Gateway Server Name: Port
Number> /u <User Name> /p <Password> <enter>
Run the command to verify how many components are enabled for "list of compgrp".
73

Run the following command to enable the components group:

Enable compgrp <Alias>
After you run the Enable compgrp <Alias> command, verify that the command run was
successful, and then run the Exit command.
Restart the services.
10 After the machine is up, connect to Server Manger by running the command listed in Step 5 and
verify that enabled components groups exist by running the "list of compgrp" command.
UNIX
From the local machine click on Stat - Run- type telnet <Machine name> ex:telnet sdcpi43
Log in with the instance and pwd: resource. (Note: Look at the URL to determine the instance.
For example, the URL may contain 16661 = qa1, 16662 = qa2 instance and so on.)
Navigate to <Build>ses\siebsrvr\bin.
Run the following commands:

smgr <enter>
set server <machine name> <enter>
list compgroup <enter>
Run the following command to enable the components group:

Enable compgrp <Alias>
Verify that the command run displays correctly.
Run the Exit command.
Activating Workflows for Order Management

For information about how to activate workflows, refer to the Siebel Order Management Guide on the
Siebel Bookshelf, and search for the Roadmap for Setting Up Order Management section. The Siebel
Bookshelf is available on Oracle Technology Network (OTN) at http://download.oracle.com/docs/cd/
B40099_02/homepage.htm.
After you have activated the necessary workflows and restarted the server, you can create orders.

The Search functionality provided by ACR 439 replaces the Search functionary that was provided by
ACR 367.
If you have installed ACR 367, you must inactivate the views provided by ACR 367 before you
implement ACR 439.
74

To inactivate views provided by ACR 367

1
Connect to Siebel Tools, and lock the Fast Search project.
Select View in the Object Explorer, query for the Search Find Results View object, and inactivate
it.
Within Object Explorer, select Screen, and query for Search View Screen.
Navigate to Screen View, and inactivate Search Find Results View within the Screen Views
section.
Compile the Fast Search project and unlock it.
After installing ACR 439, you must make sure that Find objects are visible in the application.
To make sure that Find objects are visible in the application

1
Connect to Siebel Tools.
Select the application from Object Explorer, and search for the relevant Application Name.
Navigate to Application Find in the Object Explorer, and activate the Find names that you want
to display for the application.
Make sure that the relevant Business Components are part of the Search Execution Business
Object.
Compile your changes to the SRF.
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).
Use the following procedure to resolve this error.
To resolve the SBL-DAT-00222 error message

1
Connect to Siebel Tools.
Within the Object Explorer, select Business Object.
Query for Search Execution, right-click the access the submenu, and select Unlock Object.
Navigate to the Object Business Component.
Click New Record and add the required Business Component (such as Consumer).
Compile the changes to the SRF.
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.
75

Configuration Instructions for FR 12-1JNDSVI

Use the procedures in the subtopics that follow to implement FR 12-1JNDSVI.
Modifying the SIS OM Edit Complex Asset and SIS OM Edit Complex
Asset WorkflowContact
You must modify these workflows to avoid an error when modifying an Asset in non-interactive mode
or modifying a Simple Product, after the Product definition has changed as a result of adding or
removing components or attributes.
To modify the SIS OM Edit Complex Asset workflow

1
In Siebel Tools, navigate to the Workflow Process in the Object Explorer and update the workflow
as described.
Revise the SIS OM Edit Complex Asset Workflow as follows:
Move the "Auto Match Port Ids" step from between the "Interactive Mode?" and "Display
Warning?" steps to between the "Set Requested Product Instance" and "Is Product Instance
Customizable" steps.
Move the connector from "Set Requested Product Instance" to "Is Product Instance
Customizable" and connect it to "Auto Match Port Ids".
Move the connector from "Auto Match Port Ids" to "Display Warning?" and connect it to "Is
Product Instance Customizable".
Move the connector from "Interactive Mode?" to "Auto Match Port Ids" and connect it to "Display
Warning?"
Check that the Input Argument to the "Auto Match Port Ids" step contains the following values:
Input Argument: SiebelMessage
Type: Process Property
Property Name: Current Asset
Check that the Output Argument to the Auto Match Port Ids step contains the values in the
following table:
Property Name
Type
Output Argument
Current Asset
Output
Argument
SiebelMessage
Auto-Match Report
Output
Argument
AutomatchReport
NOTE: The input and output Property name should match the Input property passed to the
"Reconfigure Product Instance" step. In the default workflow, this property name is "Current
Asset".
76

Save the changes, test, and deploy.
To modify the SIS OM Edit Complex Asset Workflow-Contact workflow
Revise the SIS OM Edit Complex Asset WorkflowContact workflow using Step 2a through Step
5 detailed above.
Modifying the SIS OM Suspend/Resume Asset Sub-Process and the

SIS OM Suspend/Resume Asset Sub-Process Contact
You must modify these processes to avoid an error when suspending or resuming an Asset after the
Product definition has changed as a result of adding or removing components or attributes.
To modify the SIS OM Suspend/Resume Asset Sub-Process workflow

1
In Siebel Tools, navigate to the Workflow Process in the Object Explorer.
Revise the SIS OM Suspend/Resume Asset Sub-Process as follows:
Add a new process property with the following values:

Name
Display Name
In/Out
Default String
Data Type
Run AutoMatch
Run AutoMatch
In
String
NOTE: Set Default String to "Y" if AutoMatch steps are to be triggered.
Add a Decision Point step called "Run AutoMatch (Suspended)?" after the "Set Product Instance
(Active)" step by moving the connector between "Set Product Instance (Active)" and "Create
Delta (Suspended)" and connecting it to "Run AutoMatch (Suspended)?" with following
connectors:
Connector of Type Default and Name "No" connected to "Create Delta (Suspended)"
Connector of Type Condition and Name "Yes" connected to the new step "AutoMatch
(Suspended)".
Right-click the connector and select "Edit Conditions to add the following condition:
Compare To
Object
Operation
Values
Process Property
Run AutoMatch
This Must Match

(Ignore Case)
Add a new Business Service step "AutoMatch (Suspended)" with the following values:
Business Service Name
Business Service Method
Complex Product AutoMatch Service
AutoMatch
77

Add the following Input Argument:

Input Argument
Type
Property Name
SiebelMessage
Process Property
Suspended Asset
Add the following Output Argument:

Property Name
Type
Output Argument
Suspended Asset
Output Argument
SiebelMessage
NOTE: The input and output Property name should match the Input property passed to the
"Create Delta (Suspended)" step, in the Vanilla Workflow this property name is "Suspended
Asset".
Add a Decision Point step "Run AutoMatch (Active)?" after step "Set Product Instance
(Suspended)" by moving the connector between "Set Product Instance (Suspended)" and
"Create Delta (Active)" and connect it to "Run AutoMatch (Active)?" with following connectors:
Connector of Type Default and Name "No" connected to "Create Delta (Active)".
Connector of Type Condition and Name "Yes" connected to the new step "AutoMatch
(Active)". Right-click the connector and select "Edit Conditions to add the following
condition:
Compare To
Object
Operation
Values
Process Property
Run AutoMatch
This Must Match

(Ignore Case)
Add a new Business Service step "AutoMatch (Active)" with the following values:
78
Add a connector from this step to "Create Delta (Suspended)"
Business Service Name
Business Service Method
Complex Product AutoMatch Service
AutoMatch
Add the following Input Argument:

Input Argument
Type
Property Name
SiebelMessage
Process Property
Active Asset
Siebel Maintenance Release Guide, Version 8.0.0.x, Rev. E Installation Instructions
Add the following Output Argument:

Property Name
Type
Output Argument
Active Asset
Output Argument
SiebelMessage
NOTE: The Input and Output Property name should match the Input property passed to the
Create Delta (Active) step. In the default workflow, this property name is Active Asset.
Add a connector from this step to Create Delta (Active.
To revise the SIS OM Suspend/Resume Asset Sub-ProcessContact workflow
Revise the SIS OM Suspend/Resume Asset Sub-ProcessContact workflow using Step 2a

through Step 2e as detailed above.
This topic includes the following subtopics:
Installation Overview on page 79
About Installing Patch Releases for Siebel Products on page 83
Installing Patch Releases on Windows on page 83
Installing Patch Releases on UNIX on page 88
Configuring Slipstream Patch Installation on page 94
Postinstallation Task for the Siebel Server on page 96
Postinstallation Task for the Web Server on page 96
Postinstallation Tasks for High Interactivity Clients on page 97
Postinstallation Task for the Siebel Sample Database on page 98
Postinstallation Task for Supporting Additional Languages on page 100
Uninstalling Patch Releases on page 101
Installation Overview
This topic is part of Installation Instructions on page 79.
In order to receive the full benefit of all product enhancements contained in the releases covered by
this document, and to maintain a fully supported Siebel installation, install each product component
shown on the Bill of Materials by following the installation instructions in this chapter. Install the
patch release for all applicable products in your existing deployment.
79
This document describes patch installation and related tasks for several key products, but not for all
Siebel products that may apply to your deployment. Patch installation tasks are generally similar to
those described here.
NOTE: This Siebel Maintenance Release Guide is updated to include information for the latest version
8.0.0.x Fix Pack release. Each version 8.0.0.x Fix Pack release is cumulative and includes all fixes
included in previous 8.0.0.x Fix Packs. You can install the latest version 8.0.0.x release on top of
version 8.0 or any prior version 8.0.0.x release. See also How to Use This Guide on page 4.
This topic includes the following subtopics:
Installation Scenarios Described in This Guide on page 80
Applicable Base Releases on page 81
About Running Siebel Image Creator on page 81
About Installing Additional Languages on page 82
About Installing Siebel Quick Fix Releases on page 82
Installation Scenarios Described in This Guide

Installation instructions in this guide apply in the following scenarios:
Performing new full installation of version 8.0, with version 8.0.0.x. If you are installing
version 8.0 (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 version 8.0.0.x Fix Pack release on top of
version 8.0.
Optionally, you can install 8.0 and 8.0.0.x together by configuring slipstream patch installation.
For details, see Configuring Slipstream Patch Installation on page 94.
For the most recent version of the Siebel Installation Guide for the operating system you are
using, see the latest version 8.0 Siebel Bookshelf.
For more information about installing 8.0 or 8.0.0.x, see About Installing Patch Releases for Siebel
Products on page 83.
Installing version 8.0.0.x (patching existing 8.0 or prior 8.0.0.x installation). If you have
already installed version 8.0 as a new full installation, and are now installing the latest Fix Pack
version 8.0.0.x on top of 8.0 or a previous 8.0.0.x release, follow the instructions in this Siebel
Maintenance Release Guide for doing this.
When you installed version 8.0 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.0 Siebel Bookshelf.
For more information about installing 8.0.0.x, see About Installing Patch Releases for Siebel
Products on page 83.
80
Adding languages. When you perform a new version 8.0 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 82.
Applicable Base Releases

Each patch release 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 patch release.
Installing any patch release requires an existing installation of a qualified base release to install into.
Here, base release means the current version of the existing installation, including any installed
patches.
Here are the base versions and product suites for installing the latest version 8.0.0.x:
Siebel Business Applications, version 8.0 or lower-level 8.0.0.x
Siebel Industry Applications, version 8.0 or lower-level 8.0.0.x
Do not install a patch release 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 software, all components of a Siebel Enterprise must be at the same
exact version 8.0.0.x release level.
About Running Siebel Image Creator

The Siebel Image Creator utility is used to create an installation image (sometimes called a network
image) for version 8.0 or any 8.0.0.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 release, whether a new installation of version 8.0, the addition of one or more
languages, or a patch installation of a version 8.0.0.x Fix Pack, must be done from an installation
image created using Image Creator.
NOTE: Always use the most recent version of Siebel Image Creator: that is, the version 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.0 Siebel Bookshelf.
81
About Installing Additional Languages

Include or add all languages you will require in your Siebel version 8.0 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 configuring an installed Siebel Server, launch the Siebel Server
Configuration Wizard, remove the Siebel Server configuration, and reconfigure the Siebel Server.
If you add a language after configuring an installed Siebel Web Server Extension (SWSE), launch
the SWSE Configuration Wizard, and 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
(multivalue LOV) conversion utility. It is recommended to perform database-related tasks after
installing applicable patch releases.
NOTE: If you are adding languages to an existing installation, do so before you install the latest
version 8.0.0.x Fix Pack release. It is possible to add a language after a version 8.0.0.x patch release
has been installed. However, for each component for which you add a language, you must reinstall
the patch release to bring the language pack files up to the current patch level. (Because Fix Pack
releases are cumulative, you can install just the latest 8.0.0.x Fix Pack, even if you previously
installed a prior 8.0.0.x Fix Pack before adding the language.)
If you are not adding languages, you only need to install the latest version 8.0.0.x patch release, as
described in this guide.
For more information about installing and deploying Siebel languages, see also:
Siebel System Requirements and Supported Platforms on Oracle Technology Network
Siebel Installation Guide for the operating system you are using
Siebel Global Deployment Guide
Configuring Siebel Business Applications
See also Postinstallation Task for Supporting Additional Languages on page 100.
About Installing Siebel Quick Fix Releases

After installing version 8.0 and 8.0.0.x as described in this guide, you can also install any applicable
Quick Fix releases on top of version 8.0.0.x. When you install a Quick Fix release, installed languages
may also be patched, depending on the content of the Quick Fix release.
NOTE: Installing Quick Fix releases may entail restrictions about which subsequent Fix Pack releases
can be installed.
For detailed information about a particular Quick Fix release, see the documentation that is provided
separately with the Quick Fix.
Quick Fixes Included in 8.0.0.x Fix Packs identifies fixes from previous Quick Fix releases that are
included in version 8.0.0.x releases.
82
About Installing Patch Releases for Siebel Products

For each Siebel product, installing the latest version 8.0.0.x Fix Pack 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 Installation Overview on page 79.
A patch installation will not replace any customer-modified files (for example, application
configuration files like siebel.cfg) that govern program execution. When you install a patch release,
any installed languages may also be patched, depending on the content of the patch release.
NOTE: If you plan to install any additional Siebel language packs, review Installation Overview on
page 79 (and About Installing Additional Languages on page 82) before you install any patch
releases.
Patch releases for Siebel software must be installed from an installation image you create using the
Siebel Image Creator utility. This utility is described in the version 8.0 Siebel Installation Guide for
the operating system you are using. For more information, see About Running Siebel Image Creator
on page 81.
As an alternative to installing 8.0 and 8.0.0.x separately, you can combine 8.0 and 8.0.0.x
installation as described in Configuring Slipstream Patch Installation on page 94.
For more information about stopping and restarting Siebel components, which is a required part of
the patch installation process, see Siebel System Administration Guide. See also Siebel Installation
Guide for the operating system you are using.
After you install 8.0 and 8.0.0.x, you can also install any applicable Quick Fix release on top of
version 8.0.0.x. For more information, see About Installing Siebel Quick Fix Releases on page 82.
For information about uninstalling Siebel patch releases, see Uninstalling Patch Releases on
page 101.
For instructions for installing 8.0 and 8.0.0.x for your operating system platform, see:
Installing Patch Releases on Windows on page 83
Installing Patch Releases on UNIX on page 88
Installing Patch Releases on Windows

Procedures for installing a patch release for products on 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 patch release you are installing, in the general sequence presented here.
Before you install the patch release, review all applicable information in Installation Overview on
page 79 and About Installing Patch Releases for Siebel Products on page 83.
83
Instructions generally assume that patch installers are launched in GUI mode. Alternatively, the
installers for server-based products can be launched in console or unattended mode. The patch
installations run silently. See also Configuring Slipstream Patch Installation on page 94.
NOTE: If you installed version 8.0 Siebel software using the Siebel Fast Track Wizard (for SMB
customers), use the patch installers for Siebel Enterprise Server and Siebel Web Server Extension to
patch any installed instances of these modules. For more information about the Fast Track Wizard,
see the Siebel Installation Guide for the operating system you are using.
This topic has the following subtopics:
Installing Siebel Enterprise Server on Windows on page 84
Installing Siebel Web Server Extension on Windows on page 85
Installing Siebel Management Agent and Siebel Management Server on Windows on page 85
Installing Siebel Reports Server on Windows on page 87
Installing Siebel Mobile Web Client, Siebel Tools, or Siebel Client Sync on Windows on page 88
Installing Siebel Enterprise Server on Windows

This topic is part of Installing Patch Releases on Windows on page 83.
Use these instructions for installing the patch release 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 patch installer for Siebel Enterprise Server also patches an instance of Siebel Management Agent
that was installed with a Siebel Server you are patching. See also Installing Siebel Management Agent
and Siebel Management Server on Windows on page 85.
To install the patch release for Siebel Enterprise Server components

1
Shut down the Siebel product component to be updated. For example, stop the service for the
Siebel Server or Siebel Gateway Name Server. Also shut down any running instances of the Siebel
Server Manager (srvrmgr).
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.
In Windows Explorer, navigate to the Siebel image location for version 8.0.0.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 = The directory for your version-specific Siebel installation image, such as
D:\Siebel_Install_Image\8.0.0.x.
Double-click setup.exe to launch the Siebel Enterprise Server installer for 8.0.0.x.
Select an 8.0 or a previous 8.0.0.x instance to patch from the list of detected installations.
Follow all prompts to complete installation of 8.0.0.x.
84
Repeat these steps on each machine with a Siebel Enterprise Server component installation to
be patched.
Restart all applicable Siebel product components.
Installing Siebel Web Server Extension on Windows

Use these instructions for installing the patch release on any machine where a Siebel Web Server
Extension (SWSE) component is installed.
NOTE: Before you install any patch 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 release. If you need to update the Web server, do so before you install the SWSE patch
release.
To install the patch release for Siebel Web Server Extension

1
Stop the Web server.
directory where the installer is located. For SWSE, navigate to
Siebel_Image\Windows\Server\Siebel_Web_Server_Extension, where:
Double-click setup.exe to launch the SWSE installer for 8.0.0.x.
Repeat these steps on each machine with an SWSE installation to be patched.
Restart the Web server at the end of all patch installation for server-based products.
For more information, see Postinstallation Task for the Web Server on page 96.
Installing Siebel Management Agent and Siebel Management Server

on Windows
Use these instructions for installing the patch release 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, see also Installing Siebel Enterprise Server on Windows on page 84. (For background on
this point, see the Siebel Installation Guide for the operating system you are using.)
85
When you patch 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 patch the
Management Agents. It is recommended to patch all instances of Management Agent, and then patch
Management Server. After you restart Management Server, it will automatically reconnect 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 patch release for Siebel Management Agent (where Management
Agent was installed separately)
1
Stop the Siebel Management Agent service.
directory where the installer is located. For Siebel Management Agent, navigate to
Siebel_Image\Windows\Server\Siebel_Management_Agent, where:
Double-click setup.exe to launch the Siebel Management Agent installer for 8.0.0.x.
Restart the Management Agent service.
Repeat these steps on each machine with a Siebel Management Agent installation to be patched
(where Management Agent was installed separately).
To install the patch release for Siebel Management Server

1
Stop the Siebel Management Server service.
directory where the installer is located. For Siebel Management Server, navigate to
Siebel_Image\Windows\Server\Siebel_Management_Server, where:
Double-click setup.exe to launch the Siebel Management Server installer for 8.0.0.x.
Restart the Management Server service.
Repeat these steps on each machine with a Siebel Management Server installation to be patched.
(In most deployments, only one instance will be installed.)
86
Installing Siebel Reports Server on Windows

Use these instructions for installing the patch release on any machine where a Siebel Reports Server
component is installed, including Actuate iServer and Management Console for Siebel, and Actuate
Active Portal JSP and Reports View Adapter for Siebel.
For the Actuate versions delivered with each patch release and platform support details, see Siebel
TIP: Installation of an 8.0.0.x patch release for Siebel Reports Server products may take a
considerable amount of time to complete. If you are certain that the latest version of Actuate
products was already installed with 8.0 or a prior 8.0.0.x Fix Pack, then you can prevent the identical
Actuate products from being reinstalled for the current Fix Pack.
For example, if you previously installed 8.0, then you can determine from Siebel System
Requirements and Supported Platforms on Oracle Technology Network that the latest 8.0.0.x Fix Pack
would reinstall the same Actuate version. Before you install the latest 8.0.0.x Fix Pack, you can set
the parameter InstallActuate = no (default is yes) in the Reports Server siebel.ini file (located in
the installation image for the latest 8.0.0.x Fix Pack). Setting this parameter to no prevents the
Actuate software from being reinstalled when you install the Siebel Reports Server patch release.
To install the patch release for Siebel Reports Server

1
directory where the installer is located. For Siebel Reports Server, navigate to
Siebel_Image\Windows\Server\Siebel_Reports_Server, where:
Double-click setup.exe to launch the Siebel Reports Server installer for 8.0.0.x.
Specify the location of the license key file (XML file) for your Actuate products and click Next.
This license key file is available in the Siebel image directory from which you are installing Siebel
Reports Server. Specify the license key file provided with the Fix Pack release.
Depending on the Fix Pack release, this file may be an updated file, or it may be the same as the
one you used for your previous version 8.0.0.x release.
NOTE: You can find license key information for your Siebel Business Applications products at
Oracles license codes site. For details, see http://licensecodes.oracle.com/siebel.html.
Repeat these steps on each machine with a Siebel Reports Server installation to be patched.
87
Installing Siebel Mobile Web Client, Siebel Tools, or Siebel Client Sync
on Windows
Use these instructions for installing the patch release on machines where Siebel Mobile Web Client,
Siebel Tools, or Siebel Client Sync are installed.
To install the patch release for Siebel Mobile Web Clients, Siebel Tools, or Siebel
Client Sync
1
Exit the application for which you are installing the patch release.
NOTE: For a Siebel Mobile Web Client using the Siebel QuickStart feature, you must also exit the
QuickStart agent. 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.
directory where the installer is located. For example:
For Siebel Mobile Web Client, navigate to Siebel_Image\Windows\Client\Siebel_Web_Client
For Siebel Tools, navigate to Siebel_Image\Windows\Client\Siebel_Tools
For Siebel Client Sync, navigate to Siebel_Image\Windows\Client\Siebel_Client_Sync
where:
Double-click install.exe to launch the client installer for 8.0.0.x.
Repeat these steps on each machine with an applicable client installation to be patched.
NOTE: The machine may require a restart at the end of the installation.
Installing Patch Releases on UNIX

Procedures for installing a patch release for products on UNIX 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 patch release you are installing, in the general sequence presented here.
Before you install the patch release, review all applicable information in Installation Overview on
page 79 and About Installing Patch Releases for Siebel Products on page 83.
88
Instructions generally assume that patch installers are launched in GUI mode. Alternatively, the
installers for server-based products can be launched in console or unattended mode. The patch
installations run silently. See also Configuring Slipstream Patch Installation on page 94.
NOTE: Some Siebel products can only be installed on Windows, such as Siebel Management Server,
Siebel Mobile Web Client, Siebel Tools, and Siebel Client Sync. For more information, see Installing
Patch Releases on Windows on page 83.
This topic has the following subtopics:
Installing Siebel Enterprise Server on UNIX on page 89
Installing Siebel Web Server Extension on UNIX on page 90
Installing Siebel Management Agent on UNIX on page 92
Installing Siebel Reports Server on UNIX on page 93
Installing Siebel Enterprise Server on UNIX

This topic is part of Installing Patch Releases on UNIX on page 88.
Use these instructions for installing the patch release 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 patch installer for Siebel Enterprise Server also patches an instance of Siebel Management Agent
that was installed with a Siebel Server you are patching. See also Installing Siebel Management Agent
and Siebel Management Server on Windows on page 85.
To install the patch release for Siebel Enterprise Server components

1
Stop all running Siebel Servers by running the command stop_server on each applicable server
machine. (See Siebel System Administration Guide for details on how to use this command.) Also
shut down any running instances of the Siebel Server Manager (srvrmgr).
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.
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.)
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.)
Stop the Web server by running one of the following commands:
stopapa for Apache-based Web servers (on AIX, HP-UX, or Linux)
stop for Sun Java System Web Server (on Sun Solaris)
(AIX only) Verify that the login ID performing installation has permission to run slibclean by
asking the administrator to change the permission as follows:
chmod 6555 /usr/sbin/slibclean
89
(AIX only) Execute slibclean, as follows:

/usr/sbin/slibclean
Open a new shell and navigate to the Siebel image location for version 8.0.0.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_Install_Image/8.0.0.x.
UNIX_OS = Your UNIX operating system, such as AIX, HPUX (HP-UX), Linux, or Solaris.
(For GUI mode) Run setupUNIX_OS to launch the Siebel Enterprise Server installer in GUI mode
for version 8.0.0.x, where:
UNIX_OS = Your UNIX operating system, such as aix (AIX), hp (HP-UX), linux (Linux), or sol
(Solaris).
Go to Step 11 on page 90.
10 (For console mode) Enter the following command to launch the Siebel Enterprise Server installer
in console mode for 8.0.0.x:
setupUNIX_OS is:javaconsole -console
where:
(Solaris).
11 Select an 8.0 or a previous 8.0.0.x instance to patch from the list of detected installations.
12 Follow all prompts to complete installation of 8.0.0.x.
13 Repeat these steps on each machine with a Siebel Enterprise Server component installation to
be patched.
14 Restart all applicable Siebel product components.
Installing Siebel Web Server Extension on UNIX

Use these instructions for installing the patch release on any machine where a Siebel Web Server
Extension (SWSE) component is installed.
NOTE: Before you install any patch 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 release. If you need to update the Web server, do so before you install the SWSE patch
release.
To install the patch release for Siebel Web Server Extension

1
Stop the Web server by running one of the following commands:
90
stopapa for Apache-based Web servers (on AIX, HP-UX, or Linux)
stop for Sun Java System Web Server (on Sun Solaris)
Log on to the server using the Web server owner account.

/usr/sbin/slibclean
directory where the installer is located. For SWSE, navigate to Siebel_Image/UNIX_OS/Server/
Siebel_Web_Server_Extension, where:
(For GUI mode) Run setupUNIX_OS to launch the SWSE installer in GUI mode for 8.0.0.x, where:
(Solaris).
(For console mode) Enter the following command to launch the SWSE installer in console mode
for 8.0.0.x:
where:
(Solaris).
10 Repeat these steps on each machine with an SWSE installation to be patched.

11 Restart the Web server at the end of all patch installation for server-based products.
For more information, see Postinstallation Task for the Siebel Server on page 96.
91
Installing Siebel Management Agent on UNIX

Use these instructions for installing the patch release 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, see also Installing Siebel Enterprise Server on UNIX on page 89. (For background on this
point, see the Siebel Installation Guide for the operating system you are using.)
For information about installing the patch release for Siebel Management Server (which runs on
Windows only), see Installing Siebel Management Agent and Siebel Management Server on Windows
on page 85.
When you patch 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 patch the
Management Agents. It is recommended to patch all instances of Management Agent, and then patch
Management Server. After you restart Management Server, it will automatically reconnect 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 patch release for Siebel Management Agent (where Management
Agent was installed separately)
1
Stop the service for the Siebel Management Agent.

/usr/sbin/slibclean
directory where the installer is located. For Siebel Management Agent, navigate to Siebel_Image/
UNIX_OS/Server/Siebel_Management_Agent, where:
(For GUI mode) Run setupUNIX_OS to launch the Siebel Management Agent installer in GUI
mode for 8.0.0.x, where:
(Solaris).
92
(For console mode) Enter the following command to launch the Siebel Management Agent
installer in console mode for 8.0.0.x:
where:
(Solaris).
Restart the Management Agent service.
10 Repeat these steps on each machine with a Siebel Management Agent installation to be patched
(where Management Agent was installed separately).
Installing Siebel Reports Server on UNIX

Use these instructions for installing the patch release on any machine where a Siebel Reports Server
component is installed, including Actuate iServer and Management Console for Siebel, and Actuate
Active Portal JSP and Reports View Adapter for Siebel.
For the Actuate versions delivered with each patch release and platform support details, see Siebel
TIP: Installation of an 8.0.0.x patch release for Siebel Reports Server products may take a
considerable amount of time to complete. If you are certain that the latest version of Actuate
products was already installed with 8.0 or a prior 8.0.0.x Fix Pack, then you can prevent the identical
Actuate products from being reinstalled for the current Fix Pack.
For example, if you previously installed 8.0, then you can determine from Siebel System
Requirements and Supported Platforms on Oracle Technology Network that the latest 8.0.0.x Fix Pack
would reinstall the same Actuate version. Before you install the latest 8.0.0.x Fix Pack, you can set
the parameter InstallActuate = no (default is yes) in the Reports Server siebel.ini file (located in
the installation image for the latest 8.0.0.x Fix Pack). Setting this parameter to no prevents the
Actuate software from being reinstalled when you install the Siebel Reports Server patch release.
To install the patch release for Siebel Reports Server

1

/usr/sbin/slibclean
93
directory where the installer is located. For Siebel Reports Server, navigate to Siebel_Image/
UNIX_OS/Server/Siebel_Reports_Server, where:
(For GUI mode) Run setupUNIX_OS to launch the Siebel Reports Server installer in GUI mode for
version 8.0.0.x, where:
(Solaris).
(For console mode) Enter the following command to launch the Siebel Reports Server installer in
console mode for 8.0.0.x:
where:
(Solaris).
Specify the location of the license key file (XML file) for your Actuate products and click Next.
This license key file is available in the Siebel image directory from which you are installing Siebel
Reports Server. Specify the license key file provided with the Fix Pack release.
Depending on the Fix Pack release, this file may be an updated file, or it may be the same as the
one you used for your previous version 8.0.0.x release.
NOTE: You can find license key information for your Siebel Business Applications products at
Oracles license codes site. For details, see http://licensecodes.oracle.com/siebel.html.
Repeat these steps on each machine with a Siebel Reports Server installation to be patched.
Configuring Slipstream Patch Installation

Slipstream patch installation is the ability to configure installer behavior so that an installer process
(for full or patch installation) automatically invokes one or more patch installations for the same
product. The main installation can be performed in any applicable installer mode (GUI, console, or
unattended mode). The patch installations run silently.
NOTE: As noted in the Siebel Installation Guide for the operating system you are using, client
installations cannot be configured as silent or unattended installations. Patch release installations
invoked using slipstream installation do, however, run silently.
94
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 Installation Overview on page 79, slipstream patch installation may apply in multiple
installation scenarios. Applicable scenarios for the current product releases include:
Full installation plus patch installation. Performing an 8.0 full installation plus an 8.0.0.x
patch installation. This scenario may optionally also include a Quick Fix release for version
8.0.0.x (where applicable).
Multiple patch installations. Performing an 8.0.0.x patch installation plus a Quick Fix release
for version 8.0.0.x (where applicable).
NOTE: If you are adding languages to an existing 8.0 or 8.0.0.x installation, slipstream installation
does not apply for the installation session for installing the languages. However, slipstream
installation can be used when subsequently installing 8.0.0.x fix pack and Quick Fix releases. For
more information about installing languages, see About Installing Additional Languages on page 82.
You configure slipstream patch installation by modifying the base siebel.ini files for each applicable
Siebel product in the 8.0 or 8.0.0.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 an 8.0 full installation automatically invokes an
8.0.0.x patch installation, modify the siebel.ini file for each applicable product for 8.0, 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:
full_path_to_Siebel_product_installer_executable = The full path to the installer executable

program, located in the installation image for the release that will be installed using
slipstream patch installation.
arg_argument = One of the following values, depending on whether you are performing a
server installation or a client installation:
For server installations, the value should be:

Arg = -args PatchInstance=$(SiebelRoot) Slipstream=yes
For client installations, the value should be:

Arg = Defaults.RootDirectory=$(SiebelRoot) Slipstream=yes
95
Examples for Specifying Execute Parameter

To configure slipstream patch installation for Siebel Enterprise Server version 8.0.0.x on AIX, the
value for Execute might be as shown below. (The actual path would show the specific 8.0.0.x Fix
Pack version.)
Execute = /Siebel_Image/8.0.0.x/AIX/Server/Siebel_Enterprise_Server/setupaix
To configure slipstream patch installation for Siebel Web Server Extension 8.0.0.x on Windows, the
value for Execute might be as shown below:
Execute =
D:\Siebel_Image\8.0.0.x\Windows\Server\Siebel_Web_Server_Extension\setup.exe
To configure slipstream patch installation for Siebel Mobile Web Client 8.0.0.x on Windows, the value
for Execute might be as shown below:
Execute = D:\Siebel_Image\8.0.0.x\Windows\Client\Siebel_Web_Client\install.exe
Configuring Multiple Slipstream Installations

If, when installing version 8.0, you use slipstream installation to install both version 8.0.0.x and a
Quick Fix release for 8.0.0.x, you must configure multiple entries in the version 8.0 siebel.ini files.
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 8.0.0.x fix pack, but points to the Quick Fix release instead.
Postinstallation Task for the Siebel Server

If you are using a security adapter, then you might need to update the value of the CRC parameter
after installing a version 8.0.0.x patch release. The value must reflect the checksum value applicable
to the security adapter library file, such as a DLL file on Windows.
For detailed information about this task, see the topic about configuring checksum validation in
Siebel Security Guide.
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 patch release 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.
Postinstallation Task for the Web Server

The Web server must be restarted after you have finished installing the patch release on all serverbased components: Siebel Server, Siebel Gateway Name Server, Siebel Web Server Extension
(SWSE), and so on.
96
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 version 8.0.0.x
Fix Pack release). This folder is created as SWSE_ROOT/public/lang_code/build_number, where:
SWSE_ROOT = The location where the SWSE is installed
lang_code = Each installed language (such as ENU for U.S. English)
build_number = 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)
This folder and other folders are created on the first SWSE request after installing any Siebel 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 buildspecific folder is created, 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 patch release 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 hang.
Postinstallation Tasks for High Interactivity Clients

After installing a new version of a Siebel application, 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 do this, choose Start > Settings > Control Panel > 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 > Internet Options, 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.
97
Postinstallation Task for the Siebel Sample Database

If you are using the Siebel Sample Database with the Siebel Mobile Web Client or Developer Web
Client, then after the fix pack release is installed, a scripting error will occur and the user will be
unable to access this database. The scripting error occurs because new scripting variables have been
added which are not present in the version 8.0 Siebel Sample Database.
To use the Sample Database with either the Siebel Mobile Web Client or Developer Web Client,
perform the steps described here. These steps generate and extract a new local database that can
be used as a substitute for the version 8.0 Sample Database. (After the database has been initialized
for any user, no synchronization of this database is expected, unlike a typical local database.)
To generate and extract a new sample database

1
Navigate to Administration - Server Configuration and enable the Siebel Remote component
group, if it is not already enabled.
Navigate to Administration - Siebel Remote, then Mobile Clients. Query for HQ as the server
name in the top applet (the parent server).
Make sure the SADMIN user is present in the bottom applet (mobile clients) and has the routing
model MOBILE CLIENT - STANDARD. If the SADMIN user is not present then add it, or add any
other user you want.
If you add any other user here, it should be present in the Siebel Administrator responsibility. Go
to Administration - Application, then Responsibilities. Query for the Siebel Administrator
responsibility. In the bottom applet (users), make sure that the user is present. If not, add it.
Go to Administration- Siebel Remote, then Remote System Preferences. Uncheck the following
options:
Enable Mobile Password Expiration
Enable Mobile Password Syntax Check
Enable Mobile Web Client Lockout
To run the Generate New Database component (GenNewDb) using the GUI, go to Step 5. To run
GenNewDb using Server Manager at the command line, go to Step 6.
(GUI) Run the Generate New Database component (GenNewDb). Wait for GenNewDb to complete
before starting the next step.
Navigate to the Administration - Server Management screen, then the Jobs view.
Under Job Detail, click New and select Generate New Database (GenNewDb) in the Component/
Job field.
To submit the request, click Start Job from the applet menu.
To view the progress of your task, go to the Tasks view.
To run the Database Extract component (DbXtract) using the GUI, go to Step 7.
98
(Command line) Run the Generate New Database component (GenNewDb). Wait for GenNewDb
to complete before starting the next step.
At the command line instead of the GUI, go to SIEBSRVR_ROOT/bin and start Server Manager
using a command like this:
srvrmgr /e <enterprise> /g <gateway> /s <siebsrvr> /u SADMIN /p <password>
For example, you might enter:
D:\10643\siebsrvr\bin> srvrmgr /e Siebel /g siebgtwy /s sieb1 /u sadmin /p db2
Once you are in srvrmgr, start GenNewDb with this command:

srvrmgr:sieb1>start task for comp gennewdb
To run the Database Extract component (DbXtract) using Server Manager at the command line,
go to Step 7.
(GUI) Run the Database Extract component (DbXtract). Wait for DbXtract to complete before
starting the next step.
Navigate to the Administration - Server Management screen, then the Jobs view.
Under Job Detail, click New and select Database Extract (DbXtract) in the Component/Job field.
In the lower applet, Job Parameters, Click New.
From the Name picklist, select Client Name. Click OK.
Enter MMAY in the Value field.
To submit the request, click Start Job from the applet menu.
To view the progress of your task, go to the Tasks view.
(Command line) Run the Database Extract component (DbXtract). Wait for DbXtract to complete
before starting the next step.
Start Server Manager as described in Step 6.
Once you are in srvrmgr, start DbXtract with this command:

srvrmgr:sieb1>start task for comp dbxtract with client=MMAY
After both GenNewDb and DbXtract complete successfully, go to the machine where the Siebel
Mobile Web Client or Developer Web Client is installed. Open the application configuration file
(such as fins.cfg or uagent.cfg, depending on the application).
10 Locate the DockConnString parameter in the [Local] section of the configuration file. Specify a
value like <siebsrvr>::<synch_port>. For example: Sdcv780112::40400, where Sdcv780112 is
the Siebel Server machine and 40400 is the port number for the Synchronization Manager. The
default port number for Synchronization Manager is 40400 in a Windows environment.
11 Launch a Mobile Web Client connected to the local database, for the user for which DbXtract was
done, such as for user BCOOK, with password BCOOK.
12 Click Yes.
13 When prompted to change the password, enter a complex password. For example, specify
BCOOK@123 instead of BCOOK.
99
14 When prompted for the synchronization credentials, enter the credentials for the database you
are using, such as sadmin\sadmin or SADMIN\MSSQL.
15 The database initialization process starts.

16 After the initialization process ends, the Mobile Web Client launches.
Postinstallation Task for Supporting Additional

Languages
If you are installing an additional language into an existing version 8.0.0.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 82.
Importing Locale-Specific Data into the Repository

Sometimes it is necessary to update the text strings held in the repository for a particular language
or for multiple languages. These text strings are held in the Symbolic String Model (SSM) table, and
appear on-screen as labels for tabs, fields, and so on, across all Siebel products.
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 languages.
NOTE: These instructions are provided for use with any releases to which they apply, and may not
apply for any particular version 8.0.0.x release or 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 all applicable patch releases 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.
To import strings and other locale-specific attributes into the repository

1
In Siebel Tools, choose Tools > Utilities > Locale Management.

The Locale Management Utility appears.
Select a source language and a target language.

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.
100
Click the Import tab.
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.
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 helps you identify records that
may need to be retranslated.
Click Import.
After finishing, recompile the SRF file and restart the Application Object Manager component on
the Siebel Server to see the results.
Uninstalling Patch Releases

In some circumstances, a patch release must be uninstalled. This topic describes how to uninstall
patch releases for Windows and for UNIX platforms.
To uninstall a patch release on Windows, use the Add/Remove Programs utility to run the
uninstaller.
When uninstalling server products, the uninstaller can also be invoked by running
SIEBEL_ROOT\_uninst\product\uninstaller.exe. At the prompt, select Maintenance Release
Uninstall, where:
product = One of the following values: ses (for Siebel Enterprise Server components), eappweb
(for SWSE), or thirdparty (for Siebel Reports Server)
NOTE: For Siebel clients, no uninstaller.exe program is provided. However, the uninst.bat batch
file can be used instead. You can choose to uninstall a patch install or a full install.
To uninstall a patch release on UNIX, run the command $SIEBEL_ROOT/_uninst/uninstall.ksh

product, where:
product = One of the following values: ses (for Siebel Enterprise Server components), eappweb
(for SWSE), or thirdparty (for Siebel Reports Server)
For guidelines and limitations regarding patch release uninstallation, see below. For information
about uninstalling Siebel base installations, see the Siebel Installation Guide for the operating
system you are using.
10 1
Siebel Maintenance Release Guide, Version 8.0.0.x, Rev. E Resolved Change

Requests
Guidelines and Limitations

Note the following guidelines and limitations related to patch release uninstallation:
A release installed as a patch release, such as the latest 8.0.0.x Fix Pack installed on top of 8.0,
can be uninstalled as a patch. The uninstaller prompts you whether you want to uninstall just the
latest patch release, or perform a full uninstallation of 8.0.0.x.
A release installed as a patch release cannot be uninstalled if another later patch release has
been applied on top of it. For example, if you installed version 8.0.0.1 and then installed the
version 8.0.0.2, you would not be able to uninstall 8.0.0.1, even after uninstalling the 8.0.0.2
release. You could still perform a full uninstallation of 8.0.0.x.
If a patch release installation fails, it is recommended that the administrator uninstall and then
reinstall the patch release. If the uninstaller for the patch release is not available, proceed with
reinstalling the patch release. If this step is omitted, any future attempt at uninstalling the patch
release may fail.
If any repository or configuration changes necessary for a patch release are made after the patch
release is installed, before uninstalling the patch release, the repository or configuration must
be restored to the state when the patch release was first installed.

The tables in this topic provide lists of resolved change requests that are included in 8.0.0.x Fix
Packs. Customers using version 8.0 or a prior version 8.0.0.x Fix Pack should install the latest 8.0.0.x
Fix Pack.
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, Siebel Fix Packs are cumulative. However, the Resolved CR information for
the Siebel 8.0.0.5 Fix Pack has been provided in its own table. The Resolved CR information for the
Siebel 8.0.0.1 through Siebel 8.0.0.4 Fix Packs has been provided in a separate table.
The tables below include the following columns:
Issues Addressed: The description of the issue.
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.0.0.x Fix Packs.
102

Requests
Resolved Change Requests in the Siebel 8.0.0.5 Fix Pack

This topic is part of Resolved Change Requests on page 102.
Table 8 includes the Change Requests that were resolved in the 8.0.0.5 Fix Pack.
Table 8. Resolved Change Requests in the Siebel 8.0.0.5 Fix Pack
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
Prepopulates Search terms and

sets defaults in the search task
pane (ACR 439)
12-1P1OPFS
12-1NCHP85
8.0.0.5
For more
information about
ACR 439, see
Configuration
Instructions for ACR
439 on page 74
When users create two

simultaneous outbound
requests, the requests hang and
CommOutboundMgr logs show
errors:SBL-CMO-00169 and SBLSRM-053021
12-1NMF881
12-1NKJF4T
8.0.0.5
Supports Call Center Anywhere

version 8.1.1 on Siebel 7.7.x,
7.8.x, and 8.0.x (ACR 408)
12-1KYGTFY
12-1KSSD91
8.0.0.5
After an Email Response Group is

created, the inbound receiver
shows no running tasks
12-1PE9T4T
12-1M5DXF7
8.0.0.5
When users search, the Field

Name is used rather than the
Field Display name (ACR 439)
12-1P1OPK4
12-1OQU6GN
8.0.0.5
Issue Addressed
Call Center
CTI
Other
For more
information about
ACR 439, see
Configuration
439 on page 74
10 3

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
12-1P1OPGZ
12-1O4OT7M
8.0.0.5
For more
information about
ACR 439, see
Configuration
439 on page 74
After 8.0.0.2 QF 6201 has been

applied, when users perform the
Find <Specific Case> function,
the application logs them out
12-1P1OPDQ
12-1O3GOE9
8.0.0.5
For more
information about
ACR 439, see
Configuration
439 on page 74
After the Search applet is opened

during an Inbound Call, when
users drill down on an SR, the
application hangs (ACR 439)
12-1P1OPAO
12-1O3GG5V
8.0.0.5
For more
information about
ACR 439, see
Configuration
439 on page 74
Allows Find and Attach

functionality to have the parent
relationship be based on the
parent applet (ACR 439)
12-1P1OP8E
12-1O4OT5J
8.0.0.5
For more
information about
ACR 439, see
Configuration
439 on page 74
Search Center does not

remember terms and results
after it has been closed (ACR
439)
12-1P1OP5A
12-1NZODJL
8.0.0.5
For more
information about
ACR 439, see
Configuration
439 on page 74
Issue Addressed
Implements Preview with Find,
as in Siebel 7.x applications.
With this enhancement, when
users click the Binoculars icon,
perform a search using the Find
object, select a single result line
item and click on Preview, the
selected result is displayed as a
popup window.
Note: The preview is not
applicable when users are
viewing the results in the
Business Component view. (ACR
439)
104

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
Allows customers to toggle

between views (ACR 439)
12-1P1OP32
12-1N3J0NR
8.0.0.5
For more
information about
ACR 439, see
Configuration
439 on page 74
Prepopulate is not working with

variables (DLL issue with CTI
Search).
12-1P19HT2
12-1O3GG6U
8.0.0.5
For more
information about
ACR 439, see
Configuration
439 on page 74
Siebel Search Center (Simple

Search) does not work
12-1OA60HD
12-1NZOD0Z
8.0.0.5
When users attempt a Binocular

Search to query within the Date
field, they receive the following
error message: "The query could
not be run because there is an
invalid character in the field
'<?>'. Please ensure that the
value in the field is formatted
correctly with only valid
characters. Missing quotes
around the search criteria or
unnecessary punctuation will
often cause an error (SBL-DAT00403)".
12-1NZNTCR
12-1NMF0AW
8.0.0.5
The sequence in the Look In

drop-down list does not change
even after the sequence has
been changed in Siebel Tools
12-1NBZXEU
12-1NABW5J
8.0.0.5
Issue Addressed
In the Communication event

handler, when a parameter such
as FindDialog : Service Request
FindField First Name:
{@UserName} is given, the
Search applet opens up with First
name : {@UserName}
populated, and the agent's name
is populated. (ACR 439)
For more
information about
ACR 439, see
Configuration
439 on page 74
Territory Management
10 5

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
12-1OVTT0N
12-1OJJL8T
8.0.0.5
12-1OEJZ6H
12-1NWUB8D
8.0.0.5
Duplicate Transfer-Encoding
Chunked entries using Sun-ONEWeb-Server 6.1
12-1O3GXQ3
12-1NNDC5J
8.0.0.5
The Send method fails with the

Unknown character set" error
message when an XML document
is larger than 50 KB
12-1NUGTTC
12-1NBZY6B
8.0.0.5
Issue Addressed
Assignment Manager crashes
when Territory Management
does parallel alignment
Special
Instructions
Comm Media
Energy
Billing Management
ACR 428 provides the following
enhancements:
New billing management

views
Multiple Account Billing

Profiles
Multiple balance groups,

balances, and details
Real-time display of unbilled

usage and invoices.
New Web Services for

products, accounts,
contacts, and billing profiles
Enhanced Customer Order

Management to support onetime charges, promotions,
customizable product
pricing, and asset-based
ordering enhancements
Nested Service bundle
Connectors / EAI
Other
106
Yes, see
Configuration
428 on page 63.

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
For EAI JMS Transports, JVM

crashes when processing
messages of a certain size
12-1NT3UX7
12-1NH83XB
8.0.0.5
SetSearchExpr fails with "Type

Mismatch" when called through
COM Data Server
12-1MMPM3E
12-1LAUPGS
8.0.0.5
12-1KUV9CQ
12-1JFQEZ6
8.0.0.5
12-1NQ7VQO
12-1KGMH5V
8.0.0.5
12-1NVW4N1
12-1NWD809
8.0.0.5
12-1NTI7PU
12-1NTI7P5
8.0.0.5
Issue Addressed
Special
Instructions
Consumer Sector
Handheld
In the Consumer Sector
Handheld application, with
certain records in "FS InvLoc
Product", the InstantiateProduct
method hangs
Sales Volume Planning

Category Aggregation Fields are
not properly populated prior to
aggregation
Customer Order
Management
Configurator
After users have applied Siebel
8.0.0.2 QF0218, they receive the
following error message when
they attempt to configure a
product:
"We detected an Error which may
have occurred for one or more of
the following reasons: Error
invoking service 'Configurator
Service', method
'GetDomainRowSet' at step 'Pre
Pick Get Row Set'.(SBL-BPR00162)
When rules are fired against a
child Business Component, the
application crashes
10 7

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
Promotion default instances are

created incorrectly when
promotion constraints and rules
are used
12-1NNDIRO
12-1NNU3JH
8.0.0.5
Within a quote or order line item,

when users click the Add button
to add a product to the shopping
cart, change the quantity,
change the sort order two or
three times, and then click OK,
the application hangs
12-1NC2W6M
12-1LZM7AT
8.0.0.5
Within eConfigurator running on

a Standard Interactivity client,
when users click quickly on
attributes and then click the
Done button, the application
hangs
12-1N9NK1T
12-1N3J0OL
8.0.0.5
For some Customizable Products,

performing the Done operation
on Siebel 7.8.2.7 [19227]
crashes the application
12-1N5VOJ8
12-1N03ODH
8.0.0.5
Smartpart numbers based on

Attribute Matrix do not update
the smart part number correctly
for child components when
customized twice
12-1MDJISD
12-1M0PGMJ
8.0.0.5
Wrong validation results occur

with promotions and
Customizable Products
12-1M1ZNN1
12-1LY4CD9
8.0.0.5
12-1ONEBU7
12-1ONEBTJ
8.0.0.5
Issue Addressed
Order Management
Cursors are not closed as
expected when querying
specialized Business
Components like "Order Entry Orders and "Order Entry - Line
Items".
NOTE: 8.0.0.5 QF0502 reverts
this fix.
108
Special
Instructions

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
Users are unable to update

payment profiles it the profile
has been created using special
characters (such as
apostrophes)
12-1ONEBSB
12-1OJ22KN
8.0.0.5
When adding Customizable

Products or promotions using
Web Services, only Customizable
Products are added, not the
default components in a Sales
Order
12-1OD10YQ
12-1NZNRV3
8.0.0.5
The QuoteAddItemsWS Web

Service does not add promotion
default items
12-1NZNXVZ
12-1L89W3Q
8.0.0.5
The QuoteAddItemsWS Web

Service does not add promotion
default items
12-1NZNXUP
12-1JGWLNN
8.0.0.5
The Upgrade Promotion function

does not correctly apply
constraints
12-1NGQRE6
12-1N3J0VT
8.0.0.5
12-1NZNXTJ
12-1JZ4C6J
8.0.0.5
12-1NLXL4O
12-1NGYQCT
8.0.0.5
Issue Addressed
Special
Instructions
Products
Quotes
QuoteAddItemsWS Web Service
does not add promotion default
item customizable product
instances
Sales Catalog
QuoteAddItemsWS Web Service
does not add promotion default
item customizable product
instances
Data Quality
Deduplication
10 9

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
12-1NFSOGV
12-1MW8RAT
8.0.0.5
Users cannot import ISS Utility

Service because there is a
duplicate Business Service name
in the Siebel Repository
12-1PRN9B0
12-1POSOKJ
8.0.0.5
Duplicate records are not being

populated within the Duplicate
Accounts/Contacts/Prospect tab
on Admin - DQ
12-1PSMZM8
12-1PLGUT7
8.0.0.5
12-1PSMZLL
12-1PLXV8U
8.0.0.5
Issue Addressed
ACR 378 provides the following
functionality:
If an acquisition is performed
by a third-party engine,
Siebel UDQ now allows the
vendor engine to handle the
acquisition and matching by
passing the source record to
the vendor engine to take
advantage of vendor-specific
acquisition algorithm.
Allows Full Batch and

Incremental Batch to both be
treated as Full Batch. In the
case of a search
specification, the search
specification is now
consumed by the vendor
engine as well.
Other
Packages ISS-related DLLs.
NOTE: The 8.0.0.5 release
includes only the Windows DLLs.
Customers running AIX, HP-UX,
or Solaris should contact their
Oracle representative to obtain
the DLLs for their OS.
General
Advanced Search
110
Special
Instructions

Requests

Issue Addressed
Performance issues occur with
Business Components and
Business Objects that are not
released even if the variable is
set to null in the script
Fix Request
ID
Change
Request ID
Fixed in
Version
12-1ORC74V
12-1OK1T6F
8.0.0.5
12-1N22RZ9
12-1LW16M5
8.0.0.5
12-1MTX6BJ
12-1KGO2U6
8.0.0.5
12-1N32631
12-1MYLII7
8.0.0.5
12-1O6NJUB
12-1HPXCQP
8.0.0.5
12-1NUHCPH
12-1LQUP21
8.0.0.5
Special
Instructions
Application
Administration
When user tries to update the
manager position for a position
that itself has direct reports, the
operation will produce the
following error message:
"Cannot update Parent because
this will introduce recursive
reporting relationship, or such
relationship already exists for
given Parent SBL - DAT 00496".
Assignment Manager
When users drop a position, add
it back, and then run an
alignment, Assignment Manager
crashes
Audit Trail
Audit trail does not audit child
Business Component records
when the parent Business
Component records have been
merged
Calendar
Daily Calendar crashes with a
script error on line 5890
Installation
Users are unable to install
multiple languages using the
Unattended Configuration
function
11 1

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
Some customers' environment

does not allow the authorization
ID to be set to the table owner ID
12-1LVZZG0
12-1KXCD26
8.0.0.5
Users are unable to install

multiple languages using
unattended configuration
12-1LJ9U6C
12-1LDP7Y5
8.0.0.5
The Haley Rules Engine crashes

when trying to import Siebel
objects
12-1P84DZT
12-1P5NCJ1
8.0.0.5
With WebPhone, when users

enter a wrong User ID or
password while logging on to the
wireless URL, the error message
displays twice
12-1P1AQ77
12-1P1AQ6H
8.0.0.5
After Siebel 8.0.0.2 QF0203 has

been applied, users receive
compile errors
12-1OV1IR9
12-1O76UGH
8.0.0.5
During upgrade attempts, the

Dev database DDLIMP fails while
attempting to recreate existing
indexes
12-1OA603F
12-1NTZMQP
8.0.0.5
During reliability run testing and

with heavy and repeated login
and logouts, crashes occur
12-1O65MKP
12-1M96L5R
8.0.0.5
12-1ORCINL
12-1OQD0BB
8.0.0.5
Transaction Merger exits with an

error message when the Delete
function is performed in Cached
Update mode
12-1O13B8K
12-HV44S7
8.0.0.5
Merging contacts works on the

server, but not of the data comes
down to local
12-1NKJFAD
12-1NKJF9T
8.0.0.5
Issue Addressed
Other
Performance
The bind peek parse functionality
was not included in the Siebel
8.0 version of Oracle connector
Remote
112
Special
Instructions

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
12-1KPB593
12-KISC0Q
8.0.0.5
Reusing shortcuts with

SWECmd=GotoView after
clicking the X icon to exit the
page throws a session timeout
error
12-1O4OCFB
12-1HCLZNP
8.0.0.5
When Actuate Reports is

configured for SSL, and users
attempt to print reports, they
receive the following error
message: "Security Information.
This page contains both secure
and nonsecure items. Do you
want to display the nonsecure
items?
12-1JA90SV
12-1J04D3B
8.0.0.5
EIM jobs cannot be run because

siebsess.exe hangs in
OSDGetLatch
12-1OGL0HB
12-1O3GNTF
8.0.0.5
Pressing ENTER in a Pick Applet

field raises an error message and
an unexpected WriteRecord
event
12-1M0O2J3
12-1LVID39
8.0.0.5
Memory corruption occurs in

CSSOraSqlCursor::DoFetchNext
Record
12-1KWSN3X
12-1KT694D
8.0.0.5
Issue Addressed
Special
Instructions
Search
Users experience regular crashes
while using Fulcrum (the crash is
in the
CSSFulcrumSearchAdapter::Get
SourceName() function)
Security
Server Infrastructure
Siebel Sync
11 3

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
When an employee who is not in

the Siebel application and a
contact that is in the Siebel
application both have the same
first name and last name but
different email addresses, when
the employee creates an
appointment in Outlook and adds
a synchronizing user, when the
record syncs, the contact is
incorrectly added to the Contacts
MVG, while the employee is not
added to the MVG
12-1OJ2HC9
12-1IJUZYP
8.0.0.5
Validation errors cause

synchronization to fail
completely
12-1OJ2H75
12-1LXLFA2
8.0.0.5
Yes, see
Configuration
Instructions for FR
12-1OJ2H75 on
page 58
Allows the Extract Start Date to

be specified at the user level
rather than globally
12-1OJ2H2C
12-1EXGK4H
8.0.0.5
Yes, see
Configuration
Instructions for FR
12-1OJ2H2C on
page 57
ACR 415: Resolves a problem

with recurring appointments that
occur both in Microsoft Outlook
and in Siebel Calendar
12-1OI3OM6
12-1LXLFJM
8.0.0.5
Configuration
Instructions for FR
12-1OI3OM6 on
page 61
ACR 415: Provides one-way

synchronization from Exchange
to Siebel Calendar
12-1OI3OHA
12-1MIVDTR
8.0.0.5
Yes, see
Configuration
Instructions for FR
12-1OI3OHA on
page 57
Addresses issues with Client

Sync whereby the number of
recurrences synchronized into
the Siebel application is not
consistent with the number of
recurrences in the client PIM
application
12-1OE2BJ7
12-1M940GM
8.0.0.5
Issue Addressed
114
Special
Instructions

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
The configuration utility for

configuring SSSE fails because
the wrong password is used in
the siebns.dat file
12-1MQCBRI
12-1JDTXGH
8.0.0.5
Provides the ability to specify

alternate fields for lookup and
Exchange API calls
12-1MQBYQR
12-1M4BIKL
8.0.0.5
Yes, see
Configuration
373C on page 48
ACR 415: Provides an archive

utility for Siebel appointments.
The utility runs in the Siebel
application and flags the records
to be archived so that SSSE
deletes them from Exchange and
they are not considered in future
syncs. The Exchange archive
removes records in Exchange
that were not synched.
12-1MQBYBK
12-1K1YCWH
8.0.0.5
Yes, see
Configuration
Instructions for FR
12-1MQBYBK on
page 57
ACR 373C provides the following

functionality:
12-1ME9OGI
12-1HN5K1B
8.0.0.5
Yes, see
Configuration
373C on page 48
12-1NKJ3CN
12-1NCHP9T
8.0.0.5
Issue Addressed
Supports Microsoft Exchange

2003 SP2 so that customers
can use Exchange 2003 SP2
to synchronize Siebel
calendars using SSSE.
Allows the administrator to

specify both a system-wide
and a server-wide parameter
for 'UserMailBoxIDSource'.
Special
Instructions
Task UI
In the context of a task-based
UI, if an item is associated via an
MVG, then removed via the same
MVG, instead of the association
being removed, the record is
deleted from the base table
Tools / Configuration
11 5

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
Within the Contact Business

Component, the Clib.srand() line
in the
BusComp_PresetFieldValue
causes the application to display
a "requires parameters" error
message
12-1OYBXPH
12-1KD7YOY
8.0.0.5
Within the Contact Business

Component, the Clib.strspn()
line within the
BusComp_PreSetFieldValue
event causes the application to
hang
12-1OYBXOZ
12-1K80MJ9
8.0.0.5
Users cannot query for the +

character in any field
12-1O3GXSQ
12-1MRTDA9
8.0.0.5
When applying an Event

Template on the Opportunities
screen, Custom MVFs are not
copied from the template
12-1O0M29D
12-1N3J0TB
8.0.0.5
Navigation does not reset applet

mode
12-1NND5CT
12-1N3J16X
8.0.0.5
Performance issues occur with

Business Components that are
not released even if the variable
is set to null in the script
12-1N61MFU
12-1MI9KUX
8.0.0.5
The LAST_UPD_BY column on

S_PROJECT is being updated
with logins instead of ROW_IDs
on the Server database when
Single Object Locking Feature is
enabled
12-1N5EN4W
12-1IEP866
8.0.0.5
Within query mode, hierarchical

lists of values show nothing in
the drop-down lists
12-1M3S7VC
12-1LRCUKA
8.0.0.5
12-1P81Q2X
12-1OA5SRX
8.0.0.5
Issue Addressed
Upgrade
PROCEDURE ISSCACLS refers to
a temporary table that is not
used by the upg_iss scripts
(TMPTBL_CLSATTR)
116
Special
Instructions

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
The upg_iss.jcl script for DB2 for

z/OS does not migrate data the
same way as the corresponding
script for DB2 on LUW
12-1OI332K
12-1OI331L
8.0.0.5
Within the Database

Configuration Wizard, when
users choose 'Production
UpgRep', at the end, the wizard
fails and logs the following error
into sw_cfg_util.log: (icutil.cpp
(125) err=3604490 sys=0) SBLICF-00010: The value
"ENUinstalledFlag" was not
found.
12-1NALVYL
12-1NALVY1
8.0.0.5
Database username and

password validation is missing in
the dbsrvr.scm file for the
Migrate Repository option
12-1N6THZ5
12-1JMEMFN
8.0.0.5
Unload cards have a null

indicator 10 bytes longer than
the maximum length of the
record for the S_NOTE_CON
table
12-1N40GCI
12-1K8IWEC
8.0.0.5
12-1KWUR4G
12-Q47T8B
8.0.0.5
12-1O0M4BA
12-1NQ7LNP
8.0.0.5
Issue Addressed
Special
Instructions
Web Framework
In Siebel applications version 7.7
and higher, users can open
picklists in read-only fields
Life Sciences
Activity
Users are unable to multi-select
and add multiple attendees to a
meeting
Yes, see
Configuration
Instructions for FR
12-1O0M4BA on
page 161.
11 7

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
12-1JOZJ1L
12-1IFZNA5
8.0.0.5
Clicking the "Prepare for

interactive detailer" button
within a Solaris environment
causes the application to crash
12-1OB4V3X
12-1OB4V2N
8.0.0.5
Workflow Monitor Agent exits

with errors
12-1NIN1B3
12-1M1SEYF
8.0.0.5
12-1M5CF2R
12-1LKD1UF
8.0.0.5
12-1M05LYK
12-1M05LVL
8.0.0.5
12-1NVVXWF
12-1NJKYFT
8.0.0.5
"Token Number" is corrupted

when "Allow Repeated Contacts
Within Load" is checked
12-1ONE2SM
12-1O2HRQ9
8.0.0.5
Campaign load remains in

progress when generating
source codes during load
12-1NXS88S
12-1NJKYSL
8.0.0.5
Issue Addressed
Within the Pharma Professional
Call Detail view, when users add
sample dropped line items,
navigate to the Contact Call
applet, add text in click in the Ref
# control, and then click save,
the text in the Ref # control
disappears
Other
Protocol Builder
Incorrect activities are created
for subjects when applying a
protocol amendment
Signature Capture
Valid signatures can be
accidentally deleted from the
Signature Capture view
Loyalty
Loyalty Manager
Statement generation
sometimes fails due to invalid
SQL
Marketing
Campaigns
118
Special
Instructions

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
Campaign load tries to populate

campaign history for removed
treatments
12-1NUGS49
12-1NDFR61
8.0.0.5
Product line and account are not

autopopulated when an
opportunity is created
12-1N1RFK3
12-1MZ3MSF
8.0.0.5
Wave launch may fail when

launching multiple waves for a
campaign simultaneously
12-1J5GH7A
12-1IOMFYR
8.0.0.5
Memory that has been allocated

is not getting released after
processing leads
12-1OLHRAY
12-1NJKQ43
8.0.0.5
List Import does not perform

intelligent matching (Data
Quality) properly for multilingual
environments
12-1O9NHE3
12-1NQOZM5
8.0.0.5
Users are unable to process

10,000 leads using Haley Engine
12-1O5F105
12-1L3XV75
8.0.0.5
12-1NQP171
12-1N5VRBX
8.0.0.5
Mobile Web Client crashes when

script is added to the Docking
Service Business Service
12-1KC4LX0
12-1K501OP
8.0.0.5
Synchronization issues occur

when transactions files are being
applied
12-1NXSR13
12-1N8PI4R
8.0.0.5
Issue Addressed
Special
Instructions
Other
Mobile Solutions
Handheld for Windows
When the Outbound Message
icon flashes, users cannot
navigate to another view
Other
Yes, see
Configuration
Instructions for FR
12-1KC4LX0 on
page 160.
Partner
Relationship
Management
11 9

Requests

Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
12-1NJKT9W
12-1NCY63H
8.0.0.5
12-1NCYOL4
12-1M80EIN
8.0.0.5
12-1JVIQ92
12-1JVIQ83
8.0.0.5
12-1NLY7O2
12-1NG9H19
8.0.0.5
12-1IEBAAZ
12-1I4ZMCH
8.0.0.5
12-1N9NNZE
12-1KBNC1G
8.0.0.5
Partner Portal
The Partner Portal user
administrator of a partner
company can access
unauthorized Siebel
Responsibility records when the
New Responsibility field of the
Siebel User for this Partner Portal
user administrator contains a
value
Public Sector
Case Management
The Regenerate All function only
works if the record is visible
under the My Cases view
Other
ID Serialization does not work on
Business Components that are
not based on CSSBCHSCase
Sales
Forecasting
Aggregation by Product Line for
revenue-based forecasts is
incorrect.
Service
Other
Dispatch Board: Dispatch Board
activities disappear and
reappear on scrolling
Scheduling
Within the ePharma application,
denormalized columns do not
populate correctly
120
Special
Instructions

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
12-1LRPP0G
12-1HIVEAL
8.0.0.5
12-1POT5EZ
12-1JLPSEL
8.0.0.5
12-1PZODST
12-1JKODBX
8.0.0.5
The Display_Applet event causes

screen not to display correctly
12-1NNUUD2
12-1MMQK8H
8.0.0.5
Adding a script causes the

calendar control to display dates
without quotes
12-1NDWIAY
12-1N3J10T
8.0.0.5
If an external URL is defined, and

the IsRecordSensitive property is
used, choosing About Record or
Create Bookmark causes a crash
12-1N963HQ
12-1MSAZCI
8.0.0.5
Chart control does not display

text for horizontal lines
12-1N3IPMI
12-1MYLIO1
8.0.0.5
12-1MY3VD1
12-1MJDXY4
8.0.0.5
Issue Addressed
Even if there are
incompatibilities that prevent
Activities from being loaded into
the cache, the Optimizer should
not change the status of an
Activity to "Unscheduled
Special
Instructions
Universal
Customer Master
Data Management
Within the AdministrationUniversal Customer Master >
Unmerge Profiles > Merged
Contacts screen, when users
query for a merged contact, the
Unmerge button is inactive
Publish/Subscribe
Users are unable to publish
Account and Contact records
User Interface
Controls
Layout and Rendering

CCTogglebar_Tabs.swt does not
display static toggle applets as
buttons (tabs) in Siebel 8.0
applications
12 1

Requests

Fix Request
ID
Change
Request ID
Fixed in
Version
12-1LLTNZI
12-1JL69GJ
8.0.0.5
Second click required to navigate

when Immediate Post Change
has been set
12-1OCK4HD
12-1O6OCKJ
8.0.0.5
With Internet Explorer7,

navigating to the next applet
without completing the required
fields causes an endless loop
12-1MGRP5F
12-1ME9N7W
8.0.0.5
12-1JYK8T0
12-1JNESUD
8.0.0.5
Issue Addressed
Values entered in shuttle applet
fields do not appear until the
user steps off of the record
Special
Instructions
Navigation
Web Service
Other
ACR 391: EXISTS operator in the
searchspec field of the UI Data
Web Service causes an error
Resolved Change Requests in the Siebel 8.0.0.1 Through

8.0.0.4 Fix Packs
This topic is part of Resolved Change Requests on page 102.
Table 9 lists the Change Requests that are included in the 8.0.0.1 through 8.0.0.4 Fix Packs.
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Siebel Agent crashes when

accepting an inbound call
12-1K7HQ5F
12-1JYJ0ML
8.0.0.2
LookUp and PhoneTypeLookup

remove all non-numeric characters
from a string
12-1JBWVE4
12-1IP3F7J
8.0.0.2
Communication log files are not

generating at the default log folder
12-1II3PBY
12-1IHMFBH
8.0.0.2
Issue Addressed
Call Center
CTI
122
Configuration
Instructions

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Internet Explorer freezes when

users select a value from a toolbar
popup applet at the same time that
a CTI call occurs
12-1HG0VYV
12-JMHTR3
8.0.0.1
In the Calendar Detail view, when

users click on any field that has a
Date and Time Popup window and
then initiate an inbound call, the
popup window navigates to a
different view, but the Calendar
popup window remains on the
screen
12-1GXM4S9
12-1GE1D9O
8.0.0.1
Search on Account using City,

Country, City and Postal Code does
not work.
12-1KXY8CM
12-1KK81PK
8.0.0.3
When performing searches using

two words, Search defaults to
"AND" and not "OR
12-1L53HYS
12-1JUI73R
8.0.0.3
Provides email response integration

with IMAP4 (ACR 374)
12-1LJ9YRA
12-1FEU6CH
8.0.0.3
The IMAP driver fails with ten or

more mailboxes that contain 1MB
and larger emails
12-1LJ9YUL
12-1KWUYUJ
8.0.0.3
It is not possible search for multiple

words with FAST InStream search
12-1LQ3F5A
12-1KXYIVT
8.0.0.3
After an upgrade to the Siebel

8.0.0.1 Fix Pack, error messages
are displayed in the eCustomer
application
12-1MCS7GU
12-1M8JSWV
8.0.0.3
Refine Results is not retrieving the

search results associated only with
the DataSource selected.
12-1MMPMCA
12-1KYHUVD
8.0.0.3
Users are unable to search the

content of attachments (FAST
InStream)
12-1JOGRHR
12-1JN3RAX
8.0.0.2
Issue Addressed
Configuration
Instructions
Other
Yes, see
Configuration
Instructions for
ACR 374 on
page 50.
12 3

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Object Manager threads deadlock,

which leads to login failure
12-1IT4HJ3
12-1GVIZVC
8.0.0.2
In the Service Request form view, if

the Summary/Description field is
full and contains a misspelled word
with too few characters, the
application hangs when users click
on Check Spelling
12-1IK2FDU
12-1HSWAKX
8.0.0.2
SmartScript cannot execute the

PreLeave event at the last question
12-1I7YSNW
12-1HGLS1M
8.0.0.1
The User Property PageBaseURL

causes problems with WebSeal
12-1I7GCP5
12-1I6L378
8.0.0.1
ADM imports the body text of the

Comm Template incorrectly
12-1HXX9Q1
12-1HPYIJR
8.0.0.1
Users receive a FAST definition

error when they drill down on
eService result records
12-1HLZR0F
12-1HFZ2VX
8.0.0.1
Users cannot tab to the Next button

if their SmartScript page has only
one question of type information on
it
12-1GOP7QT
12-1GH2GUJ
8.0.0.1
Repeat Frequency field value

changes to Weekly with no message
displayed
12-1GN5D2C
12-190I2DK
8.0.0.1
Data Validation Manager does not

close all opened cursors on
S_VALDN_RL_SET
12-1I45PUL
12-1H1YB1M
8.0.0.2
Incorrect generation of Projected

Asset Cache
12-1I4YRSX
12-1I3Y2FN
8.0.0.1
Service Points are not populated

correctly during move operations
12-1I4Y3RH
12-1I4Y3QF
8.0.0.1
Issue Addressed
Configuration
Instructions
Comm Media
Energy
Order Management
124
Yes, see
Configuration
Instructions for
FR 12-1I4Y3RH
on page 162.

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
12-1HN49DJ
12-1HGM25X
8.0.0.1
12-1I0YRQB
12-RZ6BF5
8.0.0.1
The DeleteLeaves method of the

EAI UI Data Adapter throws an
error message when deleting an
association
12-1IEPC7J
12-1IAUTPJ
8.0.0.3
JCA/JDB code causes high CPU

usage
12-1IPOJHU
12-1H79NID
8.0.0.2
In a record, if one of the column

from an external table contains an
apostrophe in the string data, users
receive the following error
message: SBL-DAT-00494: The
selected record has been deleted by
another user since it was retrieved.
Please continue.
12-1LKE53B
12-1K8KLHT
8.0.0.3
The EAI HTTP response sets BOM

characters on outbound Web
Service calls if WS response is
greater than 51K
12-1M8WC0L
12-1L8APQG
8.0.0.3
Issue Addressed
Configuration
Instructions
Other
If a user runs multiple iterations of
the application, each iteration
causes the memory to grow by 2.8
MB
Partner Relationship
Management
Shopping Cart Quotes are not
properly loaded and users must add
items twice
Connectors / EAI
EAI Server Components
Other
12 5

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
The WSDL Import wizard fails with

the following error: "Insert
operation on integration component
'Repository Web Service' failed
because a matching record in
business component 'Repository
Web Service' with search
specification '[Inbound Flag] = "N"
AND
12-1N0406G
12-1L8TYDN
8.0.0.3
A memory leak occurs when adding

Accounts using SiebelDataControl
(COM)
12-1K1GVSB
12-1JGVIER
8.0.0.2
Provides an option for MQ transport

to disable report generation (ACR
382)
12-1JA49X2
12-IY12CI
8.0.0.2
Picklists based on External Business

Components do not work
12-1J61NIJ
12-1II5E73
8.0.0.2
Users are unable to run custom DTE

scripts in EAI Workflow steps
12-1ISKY5K
12-1HRHTLJ
8.0.0.2
Alerts triggered in Oracle Enterprise

Manager call Siebel Web Services to
log an IT-related Service Request
and provide details about the issue
(ACR 364)
12-1H1Y7JJ
12-1H1Y7HB
8.0.0.2
12-1I41UBD
12-L4H3V6
8.0.0.2
12-1KD8WEL
12-1K5IH9Q
8.0.0.3
Issue Addressed
Consumer Sector
Handheld
Enhances discounts to allow
overriding of the discounts at the
line item or order level (ACR 145N)
Route Management
In the Routes screen, when users
highlight all of the records in the
Target Accounts tab and click the
Commit button, they receive the
following error message: "The visit
you are creating overlaps with
another existing visit" (SBL-CNS00158)
126
Configuration
Instructions
Yes, see
Configuration
Instructions for
ACR 364 on
page 24.

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Provides the ability to extend SVP

Mass Change functionality to
custom fields. In previous releases,
users received an error "Field <?>
does not exist in definition for
Business Component '<?>'" after
adding a custom field to the Mass
Change Field LOV.
12-1I3R83Y
12-M7MJDG
8.0.0.3
The SVP Category hyperlink is not

available
12-1LRCE5Y
12-1LIIY6E
8.0.0.3
In the CG SVP Product Tree AppletBaseline applet, SVP totals are not
reflected correctly when users
move from Brand to MPG
12-1HPIIMD
12-1HN4AQ1
8.0.0.2
The Batch validate API does not

return all statuses correctly
12-1M19CDC
12-1LWJNFH
8.0.0.3
Configurator tracing/logging does

not allow the administrator to see/
troubleshoot iLog requests
12-1JUI1U2
12-1JUHIAC
8.0.0.3
Batch Validate does not provide

explanations about why a
configuration instance is
incomplete or invalid
12-1KCWFXE
12-1K8KWRR
8.0.0.3
When using dates on the PickMap,

eConfigurator expects the date to
be in the format mm/dd/yyyy and
not the current application date
format
12-1KR2DWQ
12-1G3SW7T
8.0.0.3
Issue Addressed
Configuration
Instructions
Sales Volume Planning
Yes, see
Configuration
Instructions for
FR 12-1LRCE5Y
on page 167
Customer Order
Management
Configurator
12 7

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Linked-item-based requirement
constraints do not remove enginepicked items when the linked item
is set to a different value
12-1L10H1P
12-1JYKJHX
8.0.0.3
Setattribute call is unable to use

the LIC code to set attribute values
12-1MDXDNP
12-1J35TSL
8.0.0.3
Global variables do not work in

eScript within Configurator
12-1MJCNS5
12-1MBQUCS
8.0.0.3
The configuration log does not

allow for a search time out/
constraint search request to be
identified at runtime
12-1K8KMPL
12-1JZ3XDD
8.0.0.2
Sequences of products, attributes,

and constraints are not maintained
between different versions/
database instances, so users may
experience different rule behavior
12-1K7JDZF
12-1K3YJ4M
8.0.0.2
Customer Order Management

applications do not contain a
parameterized goal strategy for
complex customizable products
with hundreds of rules and complex
attribute/quantity calculations so
that customers can choose the right
customizable product solution
12-1K216O3
12-1JUHICA
8.0.0.2
The Min/Max cardinality is not

exposed on numeric attributes
12-1JY20E0
12-1JUHIDR
8.0.0.2
Yes, see
Configuration
Instructions for
FR 12-1JY20E0
on page 165.
The Customize operation is

significantly slower when
configuring complex products with
large classes/attributes from the
catalog
12-1JWYV6V
12-1JTEUE1
8.0.0.2
Yes, see
Configuration
Instructions for
FR 12-1JWYV6V
on page 165.
BatchValidate does not recognize

invalid Customizable Product
configurations when the violation
comes from a rule with Linked
Items
12-1JBWV9E
12-1IVM41O
8.0.0.2
Issue Addressed
128
Configuration
Instructions

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Rule Effectivity Dates are not

integrated with Configurator Model
Caching
12-1IPDGZ6
12-1IP570Z
8.0.0.2
SQL performs poorly when users

click on an option while a UI refresh
request is in progress
12-1IAD76S
12-1I3D5YX
8.0.0.2
Within Configurator, when the

Internet Explorer setting "Check for
newer versions of Stored pages" is
set to "Every Visit to the Page," the
application hangs
12-1IF6M2K
12-1IF6M0J
8.0.0.1
Repeated "Cfg Object Broker" and

Method "GetProdStruct" calls from
Business Service > Simulator are
ignored
12-1IE4S44
12-1G24T0U
8.0.0.1
Improves ilog worker filtering logic

to avoid potential issues with
promotion conflicts
12-1I4Z4SW
12-1HQ7I52
8.0.0.1
Users are unable to move vendor

information from one database to
another through CP import
12-1I0ZP5B
12-1HTW1GF
8.0.0.1
Yes, see
Configuration
Instructions for
FR 12-1I0ZP5B
on page 162.
The PublishCatalog Web Service

with E&C display mode 2 does not
filter ineligible products
12-1HUG2SG
12-1HOZM1B
8.0.0.1
Yes, see
Configuration
Instructions for
FR 12-1HUG2SG
on page 162.
Some types of Customizable

Product script cause the Done
button to hang in the Standard
Interactivity application
12-1HJRUBO
12-1HFKAGX
8.0.0.1
Name-based Product Import does

not always roll back updates in case
of failure
12-1HFK806
12-1HFK7YR
8.0.0.1
Object Instances crash randomly in

eConfigurator
12-1HFIG33
12-1HF16R2
8.0.0.1
The Summary tab generates a UI

not found error and does not show
UI port items
12-1HCKI0O
12-L5R295
8.0.0.1
Issue Addressed
Configuration
Instructions
12 9

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Within the Product screen >

Product Definitions view, selecting
Translate Relationship from the
drop-down list causes Internet
Explorer to crash
12-1HCKHZ4
12-1GY6VBX
8.0.0.1
The "Revert to Selected Version"

button does not copy
responsibilities in the User
Interface
12-1H90B03
12-1GQBQCZ
8.0.0.1
The behavior of the 'Hide' property

in some UI controls for selected
items is not consistent
12-1GZ3YC3
12-1GAL3XE
8.0.0.1
12-1I0HK0X
12-1I0HK05
8.0.0.1
Inactivating product attributes

results in errors in the ABO
disconnect operation
12-1JNDSVI
12-1J1FLV0
8.0.0.2
If clear cache is performed on

Eligibility Criteria rules, it does not
take effect in runtime until the
application server is recycled
12-1JA9721
12-1IUL2T1
8.0.0.2
The default quantity of

subcomponents does not work as
expected within promotion rules
12-1I7FJSJ
12-1HFIFD7
8.0.0.1
Bundle Promotion does not

compute max cardinality
12-1I6XN62
12-1HXH2HP
8.0.0.1
121KQWMRS
121KQWMR3
8.0.0.2
Issue Addressed
Configuration
Instructions
eCustomer
With Internet Explorer 7, when
users click the Login link within the
eSales/eCustomer application, the
application crashes
Order Management
Orders
When users click Verify on the
header for Quotes/Sales Orders,
they receive a session warning
error message
Other
130
Yes, see
Configuration
Instructions for
FR 12-1JNDSVI
on page 76.

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
12-1HTXBMK
12-1HTXBL9
8.0.0.1
Yes, see
Configuration
Instructions for
FR 12-1HTXBMK
on page 163.
When users click Verify on the

Quote Header after adding a
Product that has constrains on it
and after associating a promotion,
the message shown does not
outline the promotion violations
12-1KK9FHJ
12-1K9OOI6
8.0.0.3
Users receive a special constraint

error when they click Validate in
EditPromotion
12-1KQYIH6
12-1KIMIUH
8.0.0.3
Product Promotion cache does not

refresh
12-1JFSTTP
12-1JC724U
8.0.0.2
Yes, see
Configuration
Instructions for
FR 12-1JFSTTP
on page 165.
The Promotion Constraint

Administration tree does not
contain an indicator to show which
node contains the promotion
constraint
12-1J2HQ9E
12-1HQ7I81
8.0.0.2
Yes, see
Configuration
Instructions for
FR 12-1J2HQ9E
on page 166.
Catalog categories are removed

from list applets upon repeated
demote/promote operations
12-1IT4HKF
12-1I8F79G
8.0.0.2
Users experience promotion

constraints and Customizable
Product constraint conflicts when a
Customizable Product is used in a
promotion
12-1I4Z4UQ
12-1HQ7I5S
8.0.0.1
12-1KM9UJX
12-1K405X2
8.0.0.3
Issue Addressed
Deep delete and deep copy may
result in cursor overflows if there is
a large data set to copy/delete
Products
Sales Catalog
Data Quality
Deduplication
When users click the Promote
button, the application crashes
13 1

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
When users select the Pick button

in real-time deduplication,
performance is slow
12-1L3H1W5
12-1KO0BIW
8.0.0.3
Deduplication Possible Matches are

not invoked when creating
duplicate contacts in the Account
Contacts View
12-1KJQEBH
12-PR8UL0
8.0.0.2
Real time deduplication is not

triggered while editing a record in
Account Entry Applet
12-1IF80AK
12-1IEPKU7
8.0.0.2
12-1IOKY5G
12-1AVSREW
8.0.0.2
12-1ID710T
12-1IBEJT9
8.0.0.1
Corrects an issue where the FINS

CAP Buscomp Data Loader Service
ClearCache method is only
functional within the same OS
Process (ACR 377)
12-1K0VP45
12-1K0UX7Z
8.0.0.3
If a component does not have

records, the Index All function
ends with an error
12-1KJQEGQ
12-1J8INSJ
8.0.0.3
Issue Addressed
Employee
Relationship
Management
Distance Learning
If the course contains a single
lesson, and the user fails the
lesson, the course remains in the
Confirmed state instead of being
changed to Completed-Failed
status
Financial Services
Financial Accounts
With Internet Explorer 7, within
shuttle applets, popup windows do
not display with Microsoft Internet
Explorer 7
Other
132
Configuration
Instructions

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Invoking the FINS CAP Processor

Service in the script causes the
system to crash
12-1LI4JWI
12-1L0PBZM
8.0.0.3
Global caching does not work
12-1LI68X1
12-1LCLHO5
8.0.0.3
After the 8.0.0.1 SIA [20408]

QF2104 patch has been applied,
when users click the Refresh Cache
button within Business Rule
Processor, they receive a session
warning error message
12-1M82UCL
12-1LQVFFS
8.0.0.3
The FINS dedicated client cannot be

launched when it is connected to a
customer database that is kept
locally
12-1JBP5O2
12-1J0HBZQ
8.0.0.2
12-1KMBZ1M
12-1KMBZ11
8.0.0.2
The details entered in the Activities

home page to add a new record do
not show up in the Activity Details
screen
12-1NCYP4H
12-1N5E9RR
8.0.0.3
After an activity has been created,

the activity has no OWNER_PER_ID
assigned to it
12-1NCYP54
12-1N6UDJ9
8.0.0.3
12-1K7J69Q
12-1JXI05I
8.0.0.3
Issue Addressed
Configuration
Instructions
General
Accounts
When users navigate to Accounts >
Global Accounts Hierarchy List,
click the New button to create a
new account, enter an account
name, and then try to save or move
to another record, they receive an
error message
Activities
Advanced Search
Drilling down into search results
does not navigate to the correct
record
Application Deployment
Manager
13 3

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
When users install a patch build of

the Management Server or the
Management Agent, the
configuration wizard is launched
again
12-1IZ5I4P
12-1IVV4NX
8.0.0.2
Application Deployment Manager

does not work for LOVs that have
the Parent LIC populated
12-1I8EZ84
12-1HC16C2
8.0.0.1
12-1LJ9Z0B
12-1IE7L9M
8.0.0.3
With some Java versions, a script

error occurs on the Calendar
12-1LDE1Q0
12-1K1EJU3
8.0.0.3
Appointments created by one user

on another user's shared calendar
also appear on the first user's
calendar
12-1M3TF07
12-1GJLPLM
8.0.0.3
The Employee field is not being

automatically populated with the
owner's name in Contacts,
Activities, and so forth
12-1NDWYUK
12-1MXLW85
8.0.0.3
Even when the Auto Calendar

Manager Access option is set to
False, subordinates' Calendar
Activities are visible to their
managers
12-1K4O1GQ
12-1ELW4U1
8.0.0.2
Changes made to Calendar dates

are not reflected in Attendee
Activities
12-1I3R8DS
12-1EA3KYL
8.0.0.2
When editing calendar activities,

the SQL spool shows a specific
statement being repeated dozens
or hundreds of times
12-1HG0VW2
12-1CKRT63
8.0.0.1
Issue Addressed
Configuration
Instructions
Audit Trail
Audit Trail does not work on joined
fields
Calendar
Communications Server
134
Yes, see
Configuration
Instructions for
FR 12-1K4O1GQ
on page 166.

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
12-1GRWI9D
12-1GLQ3F3
8.0.0.1
12-1IF80BH
12-1FX53WG
8.0.0.2
The sfscleanup utility deletes valid

.SAF files
12-1JGBIF1
12-1JDUHEL
8.0.0.3
Users are not able to specify the

location for the GetFile method on
CSSFileBusComp
12-1I6D3TI
12-1HD4F79
8.0.0.2
The Business Component user

property Field Read Only Field
does not work on the Attachments
Business Component
12-1HG0VS1
1213GWOMM
8.0.0.1
12-1M5DFWX
12-1K5DYEJ
8.0.0.3
Within the Call Center application,

Help > Technical Support displays
the wrong build number
12-1JRY78P
12-1JRY785
8.0.0.2
Image creation should not require

or prompt for any language-related
jar files
12-1JCFA23
12-1JCF9WN
8.0.0.1
A DLL error occurs after installation

of Danish or Swedish Handheld
applications
12-1HC13HC
121HC02WO
8.0.0.1
Issue Addressed
Files in the TEMP folder
\SEA77\Siebsrvr\TEMP are not
cleared after QF0643 has been
applied
Configuration
Instructions
Data Quality
The Potential Duplicates popup
window appears when records are
saved
File System
Yes, see
Configuration
Instructions for
FR 12-1HG0VS1
on page 163.
Global/Multilingual LOV
If the Language-Independent Code
contains an apostrophe, LOVs
cannot be activated in the Data
Administration screen
Installation
Other
13 5

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Certifies Microsoft Internet Explorer

7 on Windows XP SP2 (ACR 271)
12-1JVI79V
12-12OZHTB
8.0.0.3
Yes, see
Configuration
Instructions for
ACR 271 on
page 21
Using the Analytics ODBC driver to

connect from Siebel Customer
Relationship Management to Oracle
Business Intelligence, Enterprise
Edition, version 10.1.3.2 results in
truncated records
12-1KWAJBE
12-1KIMIIJ
8.0.0.3
After QF 3101 (ACR 405) has been

applied, ReceiveDispatchSend
yields an error message
12-1MSUS74
12-1MQ6T1B
8.0.0.3
Users experience performance

issues with the Edit > Server Script
and Check Syntax functions
12-1K2I7CV
12-1JTXB2L
8.0.0.2
Creating new Contacts through

Task UI generates an error message
12-1K7HRMR
12-1JPUA0N
8.0.0.2
Users experience performance

issues with the Edit > Server Script
and Check Syntax functions
12-1K2I7CV
12-1JTXB2L
8.0.0.2
Accessing the same view generates

different SQL, which causes growth
in the Oracle shared pool
12-1K0UWJ8
12-1JHFG2M
8.0.0.2
After QF0513 has been applied,

when the Execute method is called
to delete a particular child record,
the wrong child record is deleted
12-1J9MXX6
12-1J5GKMX
8.0.0.2
The script library is not enabled for

non-cached Business Services
12-1J4YTU3
12-1J4YTTF
8.0.0.2
Customers are not able to use RSA

providers for SSL
12-1IZO4CV
12-1I3KZQ5
8.0.0.2
When the Sales Order screen is

accessed, threads are left open in
DB2/390
12-1IS32FP
12-1II3R5W
8.0.0.2
An error message occurs if there

are parentheses in the search spec
field of the UI Data Web Service
12-1I3EW21
12-1HIVV67
8.0.0.2
Issue Addressed
136

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Bad SQL is generated when the

Contact Team shuttle applet is
added to the Task UI
12-1IGLPEB
12-1IGLYXZ
8.0.0.1
Siebel Tools crashes when users

select VB Script from Edit > Server
Scripts
12-1HZU308
12-1HWXA21
8.0.0.1
After Export > Save, the client

hangs and customers need to use
Task Manager to exit the application
12-1HJCXM2
12-UFYDEL
8.0.0.1
Users are unable to connect from

Siebel CRM applications to Oracle
Business Intelligence 10.1.3.2
using the Oracle Business
Intelligence ODBC driver
12-1HD4A01
12-1HD49YX
8.0.0.1
View data overlaps on applets when

Mozilla Firefox is the browser
12-1GXLYPX
12-1GD066N
8.0.0.1
Siebel Calendar Outbound

synchronization fails
12-1MV7RUC
12-1MKRYN4
8.0.0.3
Certifies JPN on SSSE (ACR 401)
12-1MMYW65
12-1KJCQXP
8.0.0.2
When both ENU and FRA have been

installed on the SSSE server, and an
ENU Siebel Outlook Add-in on an
Outlook client PC has been
installed, when users log into
Outlook and choose the Siebel
Options > Link Selected Item(s)
option, they see French values for
12-1HSWC4P
12-1HN3LE6
8.0.0.1
The Outlook Add-In Refresh

refreshes every one minute after
the initial cache build, rather than
refreshing at the interval specified
in Refresh Interval
12-1HMM74H
12-1H60LJD
8.0.0.1
The EIM 'Delete Exact' process does

not work on the Linux application
server
12-1MU7DOT
12-1MN97BN
8.0.0.3
Crashes occur on shutdown of Linux
12-1MZL354
12-1M3SXGD
8.0.0.3
Issue Addressed
Configuration
Instructions
PIM Server Integration
Platforms
13 7

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Siebel Tools Apply fails when

applying Case Insensitive and
Access Insensitive (CIAI) search
schema changes for tables with
long names on DB2 UDB LUW
12-1H8ITB0
12-1H6LRIB
8.0.0.1
The SQL0905N error is not handled

properly in the RecordCount
method
12-1GY0MET
121GUWDLD
8.0.0.1
Clients cannot be launched in readonly mode
12-1KFNO03
12-1JOETRU
8.0.0.3
The new local database cannot be

initialized when there are also
upgrade kits
12-1JS0K3P
12-1JL6KOR
8.0.0.2
Account Affiliation and other party

data is not routing properly
12-1JA6RSE
12-1HML1IV
8.0.0.2
Transaction Merger crashes when

merging product lines that have a
large number of products
12-1I4E4K2
121GQWGA1
8.0.0.1
The Reports Business Service

'Version' field is always blank
12-1LKCMBX
12-1FNN8PL
8.0.0.3
Cannot schedule reports after

installing 8.0.0.1
12-1MPOD79
12-1LUHRXH
8.0.0.3
The ENU folder is missing under the

Management Console URL (Siebel
Reports Folder)
12-1K1EQT6
12-1K1EQRS
8.0.0.2
When users attempt to install the

Reports Server, they receive the
following error message: "Invalid
License Key file. Please reenter
(SBL-STJ-50453)
"121IO335W
12-1INLZDP
8.0.0.2
Actuate Error 8103 -- The Siebel

Report Server license key has a
limitation of 4 CPUs
12-1IL3YOP
12-1IE8P4Z
8.0.0.1
Reports do not launch with the

Actuate Reports Server on Novell
SUSE Linux machines
12-1HMD3XS
12-1GORIQT
8.0.0.1
Issue Addressed
Remote
Reports Server
138
Configuration
Instructions

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Search results display incorrectly

when using context-sensitivity
functionality
12-1HFKDJM
12-1HCJ3K9
8.0.0.3
Incremental Index Processor gives

error SBL-OMS-00203 when there
are no records to process
12-1L756W4
12-1ISHFB1
8.0.0.3
With Service Requests, the

Associate button is disabled for Find
and Search results
12-1KPUHWL
12-1K7HVJ4
8.0.0.3
Context sensitivity does not work
12-1MS29YZ
12-1KOALQO
8.0.0.3
Resolves a problem where the Save

Search button does not work (ACR
403)
12-1NK1UP2
12-1NK1UOB
8.0.0.3
Search category names are not

consistent with Find names
12-1KUWQ5E
12-1KTA5VB
8.0.0.2
Users are unable to open file

attachments that have been
attached to Service Requests
using the Associate button
12-1KMC3OT
12-1K7HV14
8.0.0.2
Find object names are not

consistent
12-1KLSJU6
12-1KGO375
8.0.0.2
Within Search Center, users are not

able to see all of the values
available for the Account field
12-1KLSJSR
12-1KF2BA0
8.0.0.2
When users click Find on an

Opportunity, they receive the
following error message: "Sorting
on calculated field '<?>' is not
allowed.(SBL-DAT-00502)
12-1KLRDWP
12-1KF2B59
8.0.0.2
Searching on Literature is not

supported in the preconfigured
application
12-1HKBGE2
12-1H4FLAN
8.0.0.2
Indexing is not functional using

FAST on HP-UX/Oracle 10gR2
12-1G6PQQL
12-1G6PQQ1
8.0.0.2
Issue Addressed
Configuration
Instructions
Search
Yes, see
Configuration
Instructions for
FR 12-1KUWQ5E
on page 166.
13 9

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
When users click Save Search after

having searched across all records,
they receive an error message
12-1HXFRFM
12-1HTFK99
8.0.0.1
Indexing of Auction Details and

other categories is not working
12-1HXFRDL
12-1HWF27G
8.0.0.1
Allows the Advanced Search for

Oracle Secure Enterprise Search to
support using operators and dates
12-1HXFR9M
12-1GEKI37
8.0.0.1
Initiate Search Method returns only

Employee and Solution records for
all data sources
12-1HLZR2F
12-1GZ8AIH
8.0.0.1
There is no connector information

for a web crawler in Search
connector settings
12-1HKB3FM
12-1HGB2GN
8.0.0.1
Search preferences that users have

selected and saved are not
reflected in their search results
12-1GEKHQE
12-1GEKHP4
8.0.0.1
After responsibilities have been

removed, views associated with the
removed responsibilities are still
visible in the Site Map
12-1KPCDFF
12-1I2UQ34
8.0.0.3
Users are unable to access charts

when the SSL Accelerator is
enabled
12-1JA6RX8
12-1IVNL8I
8.0.0.2
There is a cross-site scripting

vulnerability in the Siebel
application
12-1ILKQA0
12-1I7X851
8.0.0.1
The Siebel Marketing Program Flow

applet does not load when the
Siebel application is integrated with
IBM WebSeal
12-1I7Q7FL
12-1H1FTOE
8.0.0.1
Siebel Tools incorrectly allows

saving <script> tags in View and
Applet names
12-1HN3IZA
12-1H1DCAH
8.0.0.1
The Siebel Marketing Program Flow

applet does not load when the
Siebel application is integrated with
IBM WebSeal
12-1H9MCHJ
12-1H1FTOE
8.0.0.1
Issue Addressed
Security
140
Configuration
Instructions

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
The Verify password field in User

Preferences does not reset
12-1GOS12O
12-1GFJFXH
8.0.0.1
A URL like the following allows for

an XSS type of response where a
script-triggered dialog box is
displayed: http://localhost/
sales_enu/
start.swe?\%22><script>alert('XS
S')</script>
12-1GO7GMS
12-1G2OJ1R
8.0.0.1
SecureLogin does not work for the

echannelcme_enu component on
Solaris Sun One
12-1JGWP23
12-1I3DE9V
8.0.0.3
Ports FR 12-FRKG0N and 12FUP5Z3 from the Siebel 7.5 product

to Siebel 8.0 to address poor
performance with the Product
Selection Engine (ACR 398)
12-1L9AO88
12-1K2JRWJ
8.0.0.3
EIM crashes on EIM_ACCOUNT

import with extension columns
mappings
12-1LQ79AL
12-1LQ48KB
8.0.0.3
Object Manager exits with a error

message after users click 'About
Record' in the Enterprise Server
Configuration screen
12-1M4B0WB
12-1LMD69K
8.0.0.3
Siebsess.exe crashes on Linux

when the list process command is
executed
12-1MM74TB
12-1HUG5Q1
8.0.0.3
The eCommunications Object

Manager crashes when the CTI
connection disappears
12-1KF4F67
12-1K207A0
8.0.0.2
Exposes the SetContactContext and

ResetContactContext methods
(ACR 385)
12-1JDC2E3
12-1IKLOCF
8.0.0.2
Siebel Server components

experience non-paged pool
memory leaks on Windows 2003
machines
12-1IZ3A0K
12-1IZ39WY
8.0.0.1
Issue Addressed
Configuration
Instructions
Server Infrastructure
Yes, see
Configuration
Instructions for
ACR 385 on
page 55.
14 1

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
When users attempt to create an

activity within the Contact Business
Object through the task-based UI,
they receive the following error
message: SBL-DAT-60241: An error
has occurred committing the record
of business component 'Action'. The
user key of the record is Activity
UID = ""S_EVT_COMM.Conflict
12-1KWC29R
12-1KUV3WB
8.0.0.3
Transient Business Components are

not instantiated after the commit
step
12-1LDERAR
12-1KWC0LQ
8.0.0.3
"'COUNTRY.TransValCalc' can not be

found in the Business Component
System Default BC - S_ADDR_PER
12-1LNI68S
12-1LJ8F8Q
8.0.0.3
Incorrect Task UI behavior with the

t "Account (No Link)" Business
Component
12-1LRNUKZ
12-1LJ7BCH
8.0.0.3
Users receive the SBL-DAT-00902

error message while trying to
update the MVG field in a task
12-1LX3SHI
12-1LJ7B5G
8.0.0.3
In the "GEC Opportunity Contacts

Task View", when users update a
contract attribute that is stored in
the intersection table
S_OTPY_CON, they receive an error
message
12-1MBRM0G
12-1LMZ43F
8.0.0.3
When the client is restarted after an

object compile, users receive the
following error message: "The User
ID or password that you have
entered is not correct. Please enter
your password again."
12-1MTD0X8
12-1LCJSLO
8.0.0.3
The Using ByRef argument to a

function fails if the function call is
within a With statement
12-1K94K4N
12-1JY2PND
8.0.0.3
Issue Addressed
Task UI
Tools/Configuration
142
Configuration
Instructions

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Calculated fields and the type used

give search specification errors
12-1K401HE
12-1JVI3Q3
8.0.0.3
Task UI Admin Views must be part

of base product license keys
12-1KPUZHV
12-1J6LWOX
8.0.0.3
The header of form applets that

contain the MORE button does not
show up in the Task UI
12-1KWSNC1
12-1KHY6ZV
8.0.0.3
WriteRecord gets invoked every

time a record focus moves in a list
applet after UndoRecord is run
12-1KXE3H3
12-1K70L2I
8.0.0.3
TheApplication().RaiseError() in
BusComp_PreDeleteRecord is not
showing the message text
12-1L1L8S4
12-1KIMMXI
8.0.0.3

12-1KXE3H3
12-1K70L2I
8.0.0.3
12-1L1L8S4
12-1KIMMXI
8.0.0.3
Users receive the following error

message when Siebel Dedicated
Web Client opens up after compiling
is done: "The User ID or password
that you have entered is not
correct. Please enter your password
again.
12-1LI68W0
12-1L3HCY6
8.0.0.3
Object Level Check-In fails for

Symbolic Strings that contain
ampersand characters
12-1LKE4ZZ
12-1EYH454
8.0.0.3
The New list column is not

displayed properly on the Columns
Displayed for Forecast applet
12-1LPH7XR
12-1LD3J4V
8.0.0.3
The GetService method returns the

"Can't convert 'Undefined' to
Object" error message
12-1M06O7J
12-1KI538N
8.0.0.3
Dynamic Applet Toggle crashes

Siebel applications when a
predefined query returns a record
that fires the toggle
12-1M1QFOP
12-1LXMIR2
8.0.0.3
Issue Addressed
Configuration
Instructions
14 3

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
An error occurs with the global

variable of type property set
initialization in the global section of
Business Services
12-1MF4J89
12-1M81JE0
8.0.0.3
In more complex scripts, the

debugger gets stuck on lines where
there are set breakpoints
12-1MGRG5K
12-1KLS5VP
8.0.0.3

121MRSWFO
12-1MRTDA9
8.0.0.3
Code in PreInvokeMethod and in

Declarations of Browser Script
cause pop-up applets not to open
12-1KM9UEZ
12-1KDK35I
8.0.0.2
Use of the '+' operator in a

SearchSpec causes error
12-1K1YKI7
12-1JRZWCK
8.0.0.2
The following error is encountered

after Tools compile and client is
automatically started back up: "The
User ID or password that you have
entered is not correct. Please enter
your password again.
12-1JGBSA8
12-1JA6PVQ
8.0.0.2
Incomplete exception returned in

ST eScript engine
12-1JBP5JG
12-1HOIZFB
8.0.0.2
All of the scripting options should

be On / checked by default
12-1J1XIWR
12-1J1GVJJ
8.0.0.2
When ADODB is used to retrieve

date fields, the date fields display a
value that is one month more than
the value stored in the database
12-1IY3ZRS
12-1IV5GYS
8.0.0.2
Global variables do not work in

eScript on a Business Service
12-1IRL941
12-1ILMQ95
8.0.0.2
Suspended workflow process

instances are saved in
S_WFA_INSTANCE even with AutoPersist= False
12-1I4Z68G
12-1HZAPD3
8.0.0.2
Issue Addressed
144
Configuration
Instructions

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Crashes may occur with the new

script engine and the following
script: var a =
TheApplication().GetBusObject("x"
).GetBusComp("y"); with a
temporary Business Object (not
assigned to any variables)
12-1IIOK2V
12-1I4ZI0J
8.0.0.1
The HTML Attribute Id handle is lost

when scripting is used on the
control
12-1II6AVC
12-1I2RN08
8.0.0.1
Incomplete exception returned in

ST eScript engine
12-1I9TFZ3
12-1HOIZFB
8.0.0.1
Text Field values are not available

in browser script in Query Mode if
the field is not stepped off of
12-1HJBHC3
12-1G49D48
8.0.0.1
Cannot preserve applets in Base

mode via browser scripting
12-1HGO3E4
12-1HBIS66
8.0.0.1
Fix-and-Go in new script engine

debugger fails on object unload
12-1H8K03J
12-1H80LMH
8.0.0.1
String.length crashes AIX server on

ST Engine
12-1H5KE95
12-1H2IDCM
8.0.0.1
Siebel VB Memory leak crash using

variant and arrays
12-1GO7GQZ
12-1GCFL3X
8.0.0.1

12-1KXE3H3
12-1K70L2I
8.0.0.3
12-1L1L8S4
12-1KIMMXI
8.0.0.3
Users receive the following error

message when Siebel Dedicated
Web Client opens up after compiling
is done: "The User ID or password
that you have entered is not
correct. Please enter your password
again.
12-1LI68W0
12-1L3HCY6
8.0.0.3
Issue Addressed
Configuration
Instructions
Upgrade
14 5

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Object Level Check-In fails for

Symbolic Strings that contain
ampersand characters
12-1LKE4ZZ
12-1EYH454
8.0.0.3
The New list column is not

displayed properly on the Columns
Displayed for Forecast applet
12-1LPH7XR
12-1LD3J4V
8.0.0.3
The GetService method returns the

"Can't convert 'Undefined' to
Object" error message
12-1M06O7J
12-1KI538N
8.0.0.3
Dynamic Applet Toggle crashes

Siebel applications when a
predefined query returns a record
that fires the toggle
12-1M1QFOP
12-1LXMIR2
8.0.0.3
An error occurs with the global

variable of type property set
initialization in the global section of
Business Services
12-1MF4J89
12-1M81JE0
8.0.0.3
In more complex scripts, the

debugger gets stuck on lines where
there are set breakpoints
12-1MGRG5K
12-1KLS5VP
8.0.0.3

121MRSWFO
12-1MRTDA9
8.0.0.3
The dbconf.xls spreadsheet is

unable to convert the cp partitioned
objects to Unicode as a part of the
migration
12-1KPUZA0
12-1KFNP6V
8.0.0.2
The load jobs failed for the

S_DMND_CRTN_PRG and S_NOTE
tables asking for CLOB updation
12-1KMTBFV
12-1JXK2BU
8.0.0.2
The upglocale.dan file has incorrect

values (affects all DAN paths for
HOR where DAN is the primary
language)
12-1KIMDM5
12-1HJBM0V
8.0.0.2
For Z series customers upgrading

from Siebel 7.8.2 to Siebel 8.0, the
driver_upgrep_dev_782_mf.ucf file
is corrupted
12-1JV0ZU0
12-1JV0ZT1
8.0.0.2
Issue Addressed
146
Configuration
Instructions

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
For multilingual deployments,

upgrade should use ENU picklist
values instead of the primary
language
12-1JQY891
12-1JNH7XK
8.0.0.2
During FTP of files to mainframes at

pause#1, hhmigpop.sql fails to
transfer because a blank line exists
12-1JHGN6J
12-1JHGN5P
8.0.0.2
The time periods in the

utc_insert_to_tmp_tab.sql are
incorrect for TIMEZONE_ID = 01OBMF ((GMT-03:00) Brasilia)
12-1J5KR29
12-1J2I69Q
8.0.0.2
Database upgrade process failure

error
12-1IIOGSL
12-1I6Y8Z9
8.0.0.1
The upglocale.dan file has incorrect

values (affects all DAN paths for
HOR where DAN is the primary
language)
12-1HJHDRZ
12-1HJBM0V
8.0.0.1
Popup applet dimension is small

with IFrame and Webcontrol as SSO
Disposition
12-1KGMZVN
12-1JPWFGY
8.0.0.3
When users select Print from the

File menu in Internet Explorer, a
blank page or just the tabs print
12-1HIUOMI
12-INEDTT
8.0.0.1
In the error step, only custom error

messages should be displayed
12-1LNZRSV
12-1L75V7G
8.0.0.3
Names with spaces get lost when

concurrent tasks are run on the
same MT Server
12-1IDOWLV
12-1IBWHCH
8.0.0.1
12-1IGMHWR
12-1I088D1
8.0.0.2
Issue Addressed
Configuration
Instructions
Web Framework
Workflow
iHelp
Tasks
Users are unable to select nonhyperlink steps after they click on
the "Additional Steps" hyperlink
14 7

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
12-1HJBHGC
12-1H52QJB
8.0.0.1
If a Contact Call is created with a

Start Date of the current date,
when the user attempts to sign, the
following message appears:
"Cannot capture a signature if the
call date is later than today. (SBLLFS-00223)
12-1HIVRPN
12-1H1DHHZ
8.0.0.1
ACR 347 provides Personalized

Content Delivery. For a description
of the enhancements provided by
ACR 347, see Table 4 on page 18.
12-1NQOWFI
12-1G38MT8
8.0.0.4
The same signature is displayed

differently in the Audit view when
the PDA has different modes
(portrait or landscape) during the
signature's capture
12-1M6VQJX
12-1L3YHWX
8.0.0.3
New calls created from the

Calendar using Smart Call lose the
Parent-Child relationship with
Details records after
synchronization
12-1HIUJO7
12-18TXPAI
8.0.0.1
12-1HWES7V
12-1HG2IH4
8.0.0.3
Issue Addressed
After QF0663 has been applied, an
error message displays if users
select Item 1, Item 2, Item 3, Item
4, and then select Item 1 again
Configuration
Instructions
Life Sciences
Activity
NOTE: ACR 347 is for Siebel

Industry Applications customers
only.
Yes, see
Configuration
Instructions for
ACR 347 on
page 21.
Pharma Handheld for

Windows
Regulatory Reports
Updates the MedWatch Report
(LS_3500A) to reflect new
formatting and fields (ACR 372)
148
Yes, see
Configuration
Instructions for
ACR 372 on
page 37.

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Local conditions on the Asset

Assignment object are not working
12-1I4WZ0L
12-1I0ZJ7A
8.0.0.1
Yes, see
Configuration
Instructions for
FR 12-1I4WZ0L
on page 163.
When a Single Div Alignment is

activated after Multi Single Division
Alignment, all records in
S_POSTN_CON are deleted, an
error occurs in the log, and
Alignment Status remains in Task
Started
12-1I4WYYS
12-1HVTV7Z
8.0.0.1
When a Single Div Alignment is

activated after Multi Single Division
Alignment, the rules in all of the
Territories that belong to the
Hierarchy are expired regardless of
the Division
12-1I4WYYE
12-1HZCA8X
8.0.0.1
The load balancer splits tasks

incorrectly
12-1I4WYUT
12-1FTLEZK
8.0.0.1
Single division alignment is not

overwritten
12-1I0Y621
12-1H8SB26
8.0.0.1
Alignment cannot be run or

activated by a user other than the
default user (SADMIN) for Siebel
Server components
12-1GY3X96
121GXMQWW
8.0.0.1
Within Territory Management >

Alignment Administration, when
users change the Rep Action to
"Exclude" for the Add rule and
change the Action to "Include" for
the Drop rule, and then select the
menu item 'Undo Accept Changes'
menu item from the form applet,
the Action is not restored
12-1GUI623
12-1GUI61J
8.0.0.1
Data is not being deleted in

S_ASGN_LB_DATA after alignment
is activated
12-1GOTS3P
12-1GOTS35
8.0.0.1
Issue Addressed
Territory Management
14 9

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Results from Alignment Run do not

include objects that do not meet
the Global Conditions
12-1GCZKV9
12-1GCYEY1
8.0.0.1
Yes, see
Configuration
Instructions for
FR 12-1GCZKV9
on page 164.
Some of the inbox item tasks

created by Publish Results
functionality are not removed when
Rollback Publish Results is invoked
12-1GAUEQL
12-1GAUEPB
8.0.0.1
Manually assigned contact/

accounts are not being dropped
after the action is set to drop
12-1G63W2R
12-1G632PD
8.0.0.1
Alignments are picking up only

those address where Alignment
Flag = Y.
12-1FRZJ63
12-1FRZJ5J
8.0.0.1
The Rep Action field can be edited

by people other than the Sales
Representative
12-1FK160I
12-1FJL1BW
8.0.0.1
12-1I8GIGI
12-1FK1D3Y
8.0.0.1
Cancel Transaction does not

remove the exact points that were
given as a result of the original
accrual
121KG3WXM
12-18C53LY
8.0.0.2
When the Loyalty Batch Engine

server component is enabled, it
causes the CPU to use 100% of its
capacity
12-1I7XLHJ
12-1GYQ0Q3
8.0.0.1
Issue Addressed
Loyalty
Loyalty Customer Portal
Transactions that fire a roundtrip
promotion do not process
successfully
Loyalty Engine
Marketing
Campaigns
150
Yes, see
Configuration
Instructions for
FR 12-1G63W2R
on page 164.

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
When importing a response and the

list import process identifies the
person in the input as an existing
contact, the "Contact Account
Name" field of the imported
response does not get populated,
even though the Contact has a
Account associated
12-1JGXOV3
12-1IB0KC3
8.0.0.2
List import does not associate

campaign when included in import
format
12-1IG43X6
12-1I9TQ6T
8.0.0.2
Email Confirm In and Confirm Out

treatments appear in Allocation
views
12-1GN5CY8
12-1GHLWQJ
8.0.0.1
12-1HZUP1L
12-SH3WX3
8.0.0.1
12-1HFKDFM
12-1H9J42H
8.0.0.1
12-1I7XJI1
12-1I6L320
8.0.0.1
12-1HZUOYF
12-1EOBXNT
8.0.0.1
12-1GZTALN
12-1GVM25R
8.0.0.1
Issue Addressed
Configuration
Instructions
Email and Web

Marketing
When a large email campaign is
sent, a portion of the recipients do
not have their call status updated
to Sent
Events
If an eEvents URL is embedded in a
Web offer treatment, the following
error appears: "Applet:
'EventRoute' does not have the
drilldown: '' defined or
enabled.(SBL-UIF-00286)
Marketing Base
The User Property PageBaseURL
causes problems with WebSeal
Marketing Server
Campaign load process may take
significant time to complete due to
Assignment query
Other
The application crashes when users
attempt to promote Prospects
15 1

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Companion Sync fails when the

Mobile Web Client is not connected
to the network
12-1IHLSS8
12-1GO748L
8.0.0.3
The letters "o" and "p" cannot be

entered in text fields within 7.7.x
Handheld applications
12-1I6XS1X
12-1AQS9YX
8.0.0.2
Daylight Savings Time is not

incorporated in Handheld
timestamps
12-1HMM76E
12-1GSGXNY
8.0.0.1
Radio button options do not refresh

correctly when users navigate
between records
12-1HG16HX
12-1HG0QER
8.0.0.1
Hidden attributes are not extracted

for List Columns
12-1H58CV7
12-1H58CSN
8.0.0.1
After DSS, after Upload Only,

Handheld Sync crashes if the
network cable is unplugged
12-1H4F3VR
12-1GUILQT
8.0.0.1
12-1KDACI6
12-1K1EYVP
8.0.0.2
TxnProc enters an infinite loop

when reading transactions on
S_CAMP_CALL_LST with OperType
= "X" (uses 100% CPU)
12-1M6BZ9B
12-1LO1HPM
8.0.0.3
When user create a new

opportunity on the local database,
undo the opportunity, and then
synchronize, the synchronization
fails with the "SBL-MRG-00102:
Error reading operation from file"
error message
121KUWWR9
12-1KKAOAV
8.0.0.3
Issue Addressed
Mobile Solutions
Handheld for Windows
Mobile Connector
Incomplete SQL is generated when
applying .dx files on client with
OperType = Cascade / Merge
Other
152
Configuration
Instructions

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
12-1K0DEBW
12-1JRFLX1
8.0.0.2
12-1H4YFKR
12-1H4YFJL
8.0.0.1
Negative MDF adjustment values

cause incorrect values for MDF
period snapshot fields
12-1JOGRLU
12-1JC7EHV
8.0.0.2
The MDF Paid field values are

rounded off, which makes the
ending balance of the current
period and the beginning balance of
the next period incorrect
12-1J6K6Y8
12-1J2FZN1
8.0.0.2
Recalculations of 90 days and 90+

days buckets of Market
Development Funds Period End
Snapshot records yield negative
balances
12-1IPOJJR
12-1IGM0QP
8.0.0.2
Drilldown on new Forecast goes to

a different record
12-1GZQYP2
12-1GZQYJ8
8.0.0.3
Managers cannot add manually add

revenue items for their
subordinates to forecasts
12-1I4FNJE
12-1GYRJYW
8.0.0.1
Issue Addressed
When a different location for
sse_data.dbf (data source) is used,
the Siebel application returns with
a "username or password is invalid"
error message
Configuration
Instructions
Store-and-Forward
Messaging
SRs and Activities associated with
an account are not downloaded on
the PDA Device through SMQ
Partner
Relationship
Management
Marketing Development
Funds
Sales
Forecasting
Opportunities
15 3

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
12-1KC4UJG
12-1JD9K31
8.0.0.3
The Global Accounts view does not

change its bottom applet after the
applet has been clicked on seven
times
12-1KNHDSR
12-1K8JX8R
8.0.0.3
If Primary Bill To and Primary Ship

To contact records that are
associated to an account in the
Account Address View are deleted
or unassociated in the Account
Address view, the PR_BL_PER_ID
and PR_SHIP_PER_ID columns in
the S_ORG_EXT table still contain
the Row_Id of the deleted/
unassociated records
12-1HG23PM
12-1HBHRBT
8.0.0.2
12-1J8K133
12-1H08UL2
8.0.0.2
12-1LJRMVN
12-1LGLA7W
8.0.0.3
Issue Addressed
Numeric and picklist fields
temporarily blank out after Siebel
7.7.2.8 has been applied
Other
Service
Contracts
Agreement Line Item Charges are
incorrect after switching to Daylight
Savings Time
Other
When users change the primary on
the Service Team, they receive the
following error messages: Wrong
field values or value types detected
in field Primary. Please reenter your
field values. If you need additional
assistance please refer to
documentation. (SBL-UIF-00299).
Could not find 'Business Object'
named 'CUT Address'. This object is
inactive or non-existent. (SBL-DAT00144)
154
Configuration
Instructions

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
12-1JX07VP
12-1JC6UJ9
8.0.0.2
12-1GVNRZF
12-1GREQAR
8.0.0.1
Users cannot configure the

application to allow multiple quotes
to be created for the same property
on multiple days within a single
quote
12-1LO0XYM
12-1L5O0ZF
8.0.0.3
Users cannot turn off automatic

status changes when a quote status
changes to "Definite
12-1LO0Y28
12-1L5O108
8.0.0.3
12-1M05HRJ
12-1JXJOIR
8.0.0.3
Issue Addressed
Within the Letters tab of a Service
Request, when users click the New
button, select a template for a
letter, and click the Generate Draft
button, they receive the following
error message: This operation is
not allowed when there are no
records displayed.
Configuration
Instructions
Siebel Email
Response
General
If users pressing F9 to invoke the
email template and input Korean
characters, when the users click the
Windows Start button and then
return back to the email template,
the Korean characters have
disappeared
Travel and
Transportation
Other
Universal Customer
Master
Other
Provides support for dynamic MQ
queuing (ACR 405)
15 5

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
12-1HN5QQ7
12-1HG1BO5
8.0.0.1
12-1L23X0Z
12-1GV13QB
8.0.0.3
Supports Internet Explorer 7 on

Microsoft Vista
12-1NTIPOB
12-1LX2O15
8.0.0.3
Users are experiencing the

following issues with focus in the
Sales Order screen:
12-1HWCQIH
121HWCC3D
8.0.0.3
12-1K95CG3
12-1HPH4NF
8.0.0.3
Issue Addressed
There is no search spec on
S_UCM_CONTACT during the
conflict resolution merge process,
which can result in severe
performance issues with large
volumes of data
Survivorship
A field value is protected during the
first update by SE but it is not
protected by subsequent updates
User Interface
Controls
When users click the New button on

the form applet, open the Account
picklist, and then close the picklist
by clicking X or pressing Alt+F4,
the cursor disappears from the
field.
When users click the New button on
the form applet, open the account
picklist, close the picklist by clicking
X or pressing Alt+F4, and then
press Shift+Tab in the Order Text
field, the focus does not jump to the
beginning of the Order
With Internet Explorer 7, pressing
CTRL+N for the first time brings up
a new record, but when users
maximize and minimize the window
and then press CTRL+N a second
time, another browser window
appears.
156
Configuration
Instructions

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
After QF0608 has been applied,

when users attempt to create a new
record, the UI 'Opportunity Name'
field displays the name of the
record that was previously
highlighted
12-1KUENYI
12-1KOBM82
8.0.0.3
The focus intermittently changes to

the Internet Explorer 7 browser
address bar
12-1LCK6LZ
12-1KMBU6V
8.0.0.3

users press CTRL+N to create a
new record, press CTRL+D, click
Cancel on the delete confirmation
dialog box, and then press CTRL+D
again, the Add a Favorite dialog box
appears instead of the delete
confirmation dialog box.
12-1K95CB4
12-1HP0M1F
8.0.0.2

Enable Health Check=TRUE, when
users launch the Call Center
application and click Exit on the
Browser Health Check Window, a
login dialog box appears and the
application hangs.
12-1K94GDT
121HZUW8N
8.0.0.2
The New File button on the

Attachments View does not work
after users click on the Internet
Explorer Back button
12-1JA6RUY
12-1IBV1AT
8.0.0.2
The application hangs when users

try to reopen a MVG after changing
the primary contact
12-1IAUMKT
12-1IAUMJV
8.0.0.1
Application and applet menus do

not work
12-1HZVOEX
12-1HXH4D6
8.0.0.1
Dynamic toggle causes records to

become read-only when stepping
onto form applets from list applets
12-1HG0VV1
12-18451UP
8.0.0.1
Issue Addressed
Configuration
Instructions
History / Back / Refresh
15 7

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
12-1HJBH78
12-1H1ZGMT
8.0.0.1
The layout becomes invalid when

switching to a new mode on applet
toggle from the base mode
12-1IPMN8J
12-1I6VHOH
8.0.0.2
The application crashes when users

log into the application again within
the same session, because the
application is still trying to clean up
objects from the first login
12-1IP55CL
12-1GA27ON
8.0.0.2
With views that contain a list applet

and a form applet, when users set
the focus on the last field of the list
and press the Tab button, JAWS
does not announce the next applet
name
12-1I4E4NO
12-1FCMY6H
8.0.0.2
In Proposal Documents that contain

tables, some words in the columns
spread over two lines
121GW4E9W
12-1GALIJ5
8.0.0.2
Users are unable to create for query

for records within Service Requests
> Letters
12-1H3GCFZ
12-1H1ZB2O
8.0.0.1
In the Siebel Employee Relationship

Management High Interactivity
application, when users attempt to
invoke the GotoView method, the
following error message appears:
121GQW07D
12-HFOTMD
8.0.0.1
Issue Addressed
If users perform an action in a base
mode applet that causes the mode
to change (such as edit or query),
and then click the Back button, they
are not brought back to the correct
view
Layout and Rendering
"We detected an Error which may

have occurred for one or more of
the following reasons: We are
unable to process your request.
This is most likely because you
used the browser BACK or REFRESH
button to get to this point."
Navigation
158
Configuration
Instructions

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
Order View Tab Layout does not

work in the Siebel 7.8.2.4 and
Siebel 7.8.2.5 applications
12-1KFNOLV
12-1K0WED0
8.0.0.3
Detail applets do not open when the

control is set to read-only
12-1HH39C7
12-1HDL8TA
8.0.0.1
The Y axis is incorrectly labeled on

charts
12-1IH2L8F
12-1E6WSOI
8.0.0.2
With Internet Explorer 7, users

should not be allowed to close Pick
Applets by Alt+Q
12-1IAD8LF
12-1IAD8KB
8.0.0.1
With Internet Explorer 7, within the

Contacts screen, when users
attempt to export in HTML format,
and then click Open on the File
Download popup window, the
Export Window closes
12-1I0XVKT
12-1I0XVCO
8.0.0.1

users export records to HTML, open
the HTML file, and then close it, the
application hangs and they must
refresh the browser
12-1HZUQL3
12-1HZUQAV
8.0.0.1
Actuate Reports files are missing

after UNIX install
12-1HN3IZL
12-1GYR7A1
8.0.0.1
When WebSeal is configured on the

server and users select New in the
Calendar, they receive the following
error message: "You do not have
the privileges required to view
detailed information for this record.
Please contact your systems
administrator if you would like to
access this record".
12-1HCLTH0
12-1H20BD7
8.0.0.1
When users set SSA Primary on a

list applet and step off to the top
applet, the application does not
focus on the top applet
12-1GZUZSP
12-1FS2FBF
8.0.0.1
Issue Addressed
Configuration
Instructions
Other
15 9

Requests
Table 9.
Fix Request
ID
Change
Request ID
Fixed in
Version
12-1HG0VU2
12-157Z9AN
8.0.0.1
Within the Calendar tab of the

Opportunities home page (FRA),
the accented characters for the
short months (February, August,
December) appear as boxes.
12-1IKKXOV
12-1H09LEB
8.0.0.3
Popup windows cannot be closed

(Vista-specific issue)
12-1DIFPEP
12-1DIFPC9
8.0.0.2
Issue Addressed
When a popup window does not
completely close, and it remains
visible in a minimized state in the
Windows Task bar, users cannot
launch other popup windows until
the minimized popup window is
closed
Configuration
Instructions
Popups/Pick Lists/
MVG/Shuttle
Configuration Instructions for FR 12-1KC4LX0

Use the following procedure to implement this fix.
Log into Siebel Tools as sadmin/sadmin/server, and create the PostSyncSVC Business Service
and the PostSyncNotify Business Service method.
Register the PostSyncSVC Business Service in the tools.cfg and fins.cfg files of the mobile
client.
A sample script follows:
function Service_PreInvokeMethod (MethodName, Inputs, Outputs)
{
if (MethodName=="PostSyncNotify")
{
var qf:String="AFG";
TheApplication().RaiseErrorText(qf);
}
return (ContinueOperation);
}
Compile the script in the Siebel_sia.srf file of the mobile client.
160

Requests
From the mobile client, synchronize the database.
Configuration Instructions for FR 12-1O0M4BA

Use the following procedures to implement this fix:
Within Siebel Tools, navigate to the Pharma Attendee Deleter Business Component.
Add a new field with the following values:
Name = "Contact Id"
Column = "TARGET_PER_ID"
Navigate to the Pharma Meeting Attendee List Applet.
Add a new applet user property with the following values:
Name = "Check Duplicate Meeting Attendee"
Value = "Y"
Navigate to the Pharma Meeting Speaker List Applet.
Add a new applet user property with the following values:
Name = "Check Duplicate Meeting Speaker"
Value = "Y"
Navigate to the Pharma Meeting Attendee List Applet.
Add a new SUPPRESSED applet method menu item with the following values:
Menu Text = "Apply List"
Menu Text - String Reference = "SBL_APPLY_LIST-1009085924-03D"
Command = "SLM Apply List Popup - Simple"
Suppress Menu Item = TRUE
Position = 1
Navigate to the Pharma Meeting Speaker List Applet.
10 Add a new SUPPRESSED applet method menu item with the following values:
Menu Text = "Apply List"
Menu Text - String Reference = "SBL_APPLY_LIST-1009085924-03D"
Command = "SLM Apply List Popup - Simple"
Suppress Menu Item = TRUE
Position = 1
16 1

Requests
Configuration Instructions for FR 12-1I4Y3RH

Use the following procedure to implement this fix:
Within Siebel Tools, navigate to Business Service, query for "SIS OM PMT Service", and lock the
project.
Navigate to Business Service User Properties, and add two new records as follows, where n is
the next available number for the map:
Name: SIS OM Asset.Line Item:SIS OM Quote.Line Item Map n
Value:[Service Type]:[Service Type]
Name: SIS OM Asset.Line Item:SIS OM Order.Line Item Map n
Value:[Service Type]:[Service Type]
NOTE: Except Name and Value, let all other fields be default.
Make a backup copy of your SRF and compile the changes made to the "SIS OM PMT Service"
Business Service to the SRF.
Configuration Instructions for FR 12-1I0ZP5B

NOTE: This procedure is only applicable for Siebel Industry Applications customers.
Within Siebel Tools, navigate to the 'ISS VOD Import Export' project.
Change the Business Component for the 'Product Vendor PickList' picklist to 'Com Organization' .
Configuration Instructions for FR 12-1HUG2SG

NOTE: This procedure is specific to when eligibility rules are set based on Account: Workaround for
Account Eligibility Rule.
Within Siebel Tools, open the "Web Channel Check Eligibility & Pricing Driver Workflow" workflow
(right-click and select "Edit Workflow Process").
Click "Set Pricing Date", and then right-click and select "Show Input Arguments".
In the "Input Arguments" window, add the following input arguments:
Name = "On True 1_2", Type = "Literal", Value = "{Row.Account Id} = IfNull({Row.Account Id},
{Context.Account Id})"
Name = "On Default 2", Type = "Literal", Value = "{Row.Account Id} = IfNull({Row.Account Id},
{Context.Account Id})"
Save the workflow and deploy it.
Connect to the Siebel Server and activate the "Web Channel Check Eligibility & Pricing Driver
Workflow".
162

Requests
Configuration Instructions for FR 12-1HTXBMK

To configure parameters for Siebel Web Clients

1
Run srvrmgr and set DSMaxCursorSize and DSPrefetchSize to a value of 16.

srvrmgr> change parameter DSMaxCursorSize=16 for named subsystem serverdatasrc
srvrmgr> change parameter DSPrefetchSize=16 for named subsystem serverdatasrc
Restart the Siebel Server.
Verify the parameters are set after restarting Siebel Server:

srvrmgr> list advanced parameter DSMaxCursorSize for named subsystem
serverdatasrc
srvrmgr> list advanced parameter DSPrefetchSize for named subsystem serverdatasrc
To configure parameters for Siebel Developer Web Clients
Set MaxCursorSize and PrefetchSize in the application configuration file as follows:

[ServerDataSrc]
MaxCursorSize = 16
PrefetchSize = 16
Configuration Instructions for FR 12-1HG0VS1

Within Siebel Tools, navigate to the Account Attachment Business Component and create a field
called SVCreatedBy with Column - CREATED_BY.
Create the following Join in the Account Attachment Business Component:
Table - S_USER
Join Specification (Dest. Column - ROW_ID and Source Field - SVCreatedBy)
Create a calculated field (SVAccess) in the Account Attachment Business Component with the
calculated value - IIF([SVCreatedBy]<>LoginId(), "Y", "N")
Add the BC User Property Field Read Only Field: AccntFileName with value - SVAccess.
Configuration Instructions for FR 12-1I4WZ0L

Connect Siebel Tools to the application database and lock the Territory Management project.
Within Object Explorer, select the Workflow Policy Object node, and query for the TM Asset
Workflow Policy object.
16 3

Requests
Select the Workflow Policy Component node under the Workflow Policy Object node and configure
the Workflow Policy Components as follows:
For Address (which already exists), set Source Table Name to S_ORG_EXT, Source Column Name
to ROW_ID, Target Component to Asset, and Target Component Column Name to
OWNER_ACCNT_ID.
For Account (a new component), set Source Table Name to S_ADDR_PER, Source Column Name
to ROW_ID, Target Component to Asset, and Target Component Column to PR_ADDR_ID.
Configuration Instructions for FR 12-1GCZKV9

Connect Siebel Tools to the Application DB and lock the Territory Management Project.
Query for the TOS Target Alignment-Territory-Contact Business Component, remove the Search
Specification, and compile the SRF.
Select the Workflow Process node in the Object Explorer view and query for Alignment - Run
Alignment Process. Select the Alignment - Run Alignment Process workflow process and click
the Revise button on the WF/Task Editor Toolbar.
Right-click on the Alignment - Run Alignment Process workflow process component and select
Edit Workflow option from the context menu.
Select the Post TOS Process step in the workflow process and go to the Multi Value Property
Window.
Select the Input Arguments tab and create a new record with the following attributes and
corresponding values:
Input Argument: Assignment Rulegrp Id
Property Name: Assignment Rule Group Id
Save the changes and click on the Publish/Activate button on the WF/Task Editor Toolbar.
Unlock the Territory Management Project.
Configuration Instructions for FR 12-1G63W2R

Connect Siebel Tools to the Application DB and lock the Territory Management Project.
Query for the TOS Target Alignment-Territory-Contact Business Component, remove the Search
Specification, and compile the SRF.
Select the Workflow Process node in the Object Explorer view and query for Alignment - Run
Alignment Process. Select the Alignment - Run Alignment Process workflow process and click
the Revise button on the WF/Task Editor Toolbar.
Right-click on the Alignment - Run Alignment Process workflow process component and select
Edit Workflow option from the context menu.
164

Requests
Select the Post TOS Process step in the workflow process and go to the Multi Value Property
Window.
Select the Input Arguments tab and create a new record with the following attributes and
corresponding values:
Input Argument: Assignment Rulegrp Id
Property Name: Assignment Rule Group Id
Save the changes and click on the Publish/Activate button on the WF/Task Editor Toolbar.
Unlock the Territory Management Project.
Configuration Instructions for FR 12-1JY20E0

Use the following procedures to implement this fix:
To enable Min/Max for Attribute Definition (domains)

1
In Siebel Tools, navigate to the in the "Attribute Details Form Applet" applet.
In the "Attribute Details Form Applet" applet, activate the "Maximum Value" and "Minimum
Value" items in the "Base" and "Edit" Web Templates. This will allow setting margins on nonenumerated domains of Integers and Numbers.
To enable Min/Max for Class/Product Attributes

1
In Siebel Tools, navigate to the "ISS Class Attributes VBC List Applet" applet.
In the "ISS Class Attributes VBC List Applet" applet, activate the "Maximum Value" and "Minimum
Value" items in the "Edit List" Web Template.
Check that the "Maximum Value" and "Minimum Value" List Columns are active and have their
properties "Show In List" set to False.
Configuration Instructions for FR 12-1JWYV6V

Set "ShowDeltaMessages" = "N" on the Configurator Service Business Service to stop sending delta
messages. The default value is Y.
Configuration Instructions for FR 12-1JFSTTP

Within Siebel Tools, query for the 'ISS Promotion Form Applet' applet.
Navigate to the 'Applet Method Menu Items' section using Object Explorer.
16 5

Requests
Change the Command used for menu text 'Clear Cache' from 'ISS Promotion ClearCache' to
'RefreshProductCache'.
Save the record.
Recompile the applet in your srf file.
Configuration Instructions for FR 12-1J2HQ9E

Within Siebel Tools, under Applet, query for the "ISS Promotion CP Structure Explorer" applet.
Lock the "ISS Promotion CP Structure Explorer" applet.
Click Control within the "ISS Promotion CP Structure Explorer applet, and change the Controls
Refresh (right bottom window) from inactive to active.
Click Applet Web Template under Applet, then click Applet Web Template Item, and change
Refresh (right bottom window) from inactive to active.
Compile the object to generate the new SRF file.
Configuration Instructions for FR 12-1K4O1GQ

Navigate to Application Administration > System Preferences, and set the "Auto Mgr Calendar
Access" value to 'False'.
Restart the servers.
Install Siebel Tools.
Navigate to the "Include Direct Reports In Owner Picklist" User Property, set this property to "N"
for the HI Activity Calendar view.
Configuration Instructions for FR 12-1KUWQ5E

The fix includes seed data changes. In seed_find.dat and seed_find.inp, there are some entries to
update the Search category table so that the search category names will be plural. Run dataimp to
upload this, as follows:
dataimp /u username /p password /c datasource /f seed_find.dat /i seed_find.inp /d tableowner /Z Y
For example, enter:
dataimp /u SADMIN /p MSSQL /c "SEAW siebel" /f seed_find.dat /i seed_find.inp /d dbo /Z Y
Note that this will also change the index status of those entries, so you need to reindex the updated
entries.
166

Requests
Configuration Instructions for FR 12-1LRCE5Y

In Siebel Tools, make a copy of the view "CS CG SVP Baseline View" and name it "CS CG SVP
Baseline View - All" with responsibility All.
Associate the "CS CG SVP Baseline View - All" view to the responsibility "CG XX Key Account
Manager".
Oracle Welcomes Your Comments

To help us improve our products, we want to know about any corrections or clarifications to this guide
that you would find useful. Please include in your message:
The title and version of the guide (very important)
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
Contact us through regular mail or email at:

Oracle
Siebel Technical Publications Department
500 Oracle Parkway
Redwood Shores, CA 94065
Siebeldoc_ww@oracle.com
We appreciate your feedback.
Zip Contents
16 7

Requests
168

MR Guide 80 Rev E

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

MR Guide 80 Rev E

Загружено:

Авторское право:

Доступные форматы

Siebel Maintenance

Copyright 2005, 2008, Oracle. All rights reserved.

Whats New in This Revision

Quick Fixes Included in 8.0.0.x Fix Packs

Enhancements and Updates in 8.0.0.x Fix Packs

Configuration Instructions for Enhancements and Updates

Resolved Change Requests

Resolved Change Requests in the Siebel 8.0.0.5 Fix Pack

Siebel Maintenance Release Guide Version 8.0.0.x, Rev. E

Call Center 103

Siebel Maintenance Release Guide Version 8.0.0.x, Rev. E

Siebel Maintenance Release

Whats New in This Revision

Quick Fixes Included in 8.0.0.x Fix Packs

Enhancements and Updates in 8.0.0.x Fix Packs

Configuration Instructions for Enhancements and Updates

Resolved Change Requests

Whats New in This Revision

Whats New in Siebel Maintenance Release Guide, Version 8.0.0.x, Rev. E

Quick Fixes Included in 8.0.0.x Fix Packs

Updated topics with Siebel 8.0.0.5 Fix Pack information.

Enhancements and Updates in 8.0.0.x Fix

Siebel Maintenance Release Guide Version 8.0.0.x, Rev. E

Whats New in Siebel Maintenance Release Guide, Version 8.0.0.x, Rev. E

Enhancements and Updates in 8.0.0.x Fix

Removed information about ACR 367 (included in the

Configuration Instructions for

Included Siebel 8.0.0.4 Fix Pack information.

Resolved Change Requests

How to Use This Guide

Siebel Release Notes on OracleMetaLink 3 (https://metalink3.oracle.com/)

Siebel System Requirements and Supported Platforms on Oracle Technology Network

Siebel Maintenance Release Guide Version 8.0.0.x, Rev. E

For related Siebel documentation, see OracleMetaLink 3 https://metalink3.oracle.com and Bookshelf

Quick Fixes Included in 8.0.0.x Fix Packs

Quick Fixes Included in Version 8.0.0.x

Fix Pack Base

Siebel Maintenance Release Guide Version 8.0.0.x, Rev. E

Quick Fixes Included in Version 8.0.0.x

Fix Pack Base

Siebel Maintenance Release Guide Version 8.0.0.x, Rev. E

Quick Fixes Included in Version 8.0.0.x

Fix Pack Base

Siebel Maintenance Release Guide Version 8.0.0.x, Rev. E

Quick Fixes Included in Version 8.0.0.x

Fix Pack Base

Siebel Maintenance Release Guide Version 8.0.0.x, Rev. E

Quick Fixes Included in Version 8.0.0.x

Fix Pack Base

8.0.0.3 Fix Pack HOR

8.0.0.3 Fix Pack

Siebel Maintenance Release Guide Version 8.0.0.x, Rev. E

Quick Fixes Included in Version 8.0.0.x

Fix Pack Base

Siebel Maintenance Release Guide Version 8.0.0.x, Rev. E

Quick Fixes Included in Version 8.0.0.x

Fix Pack Base

8.0.0.1 [20408] WM5

Siebel Maintenance Release Guide Version 8.0.0.x, Rev. E

Quick Fixes Included in Version 8.0.0.x

Fix Pack Base

Siebel Maintenance Release Guide Version 8.0.0.x, Rev. E

Quick Fixes Included in Version 8.0.0.x