MR Guide 782 Rev X

Siebel Maintenance
Release Guide
Version 7.8.2, Rev. X
December 2009
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 error-
free. 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. Siebel’s 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 Oracle 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 is a registered trademark 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
Siebel Maintenance Release Guide 1
Chapter 1: Siebel Maintenance Release Guide, Version

7.8.2, Rev. X
Release Notes for the Siebel 7.8.2.14 Fix Pack 7
What’s New in This Revision 8
Quick Fixes Included in 7.8.2.x Fix Packs 10
Enhancements and Updates in 7.8.2.x Fix Packs 43
Enhancements and Updates in Version 7.8.2.14 44
Enhancements and Updates in Version 7.8.2 57
Configuration Instructions for Enhancements and Updates 61
Instructions for ACR 228B 62
Configuration and Program Setup Instructions for ACR 252 69
Program Setup 72
Instructions for ACR 263 73
Workflows 101
Client Database Configuration 109
Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 1

Contents
Instructions for ACR 346A 178

Instructions for ACR 373B 194
Instructions for Oracle BI Publisher Enhancements 221
What Does ACR 483 Provide? 221
Requirements for ACR 483 222
Roadmap for Implementing Oracle BI Publisher Enhancements 222
Installing Oracle BI Publisher for Siebel Business Applications 223
Copying JAR Files to the Oracle BI Publisher Server 225
Process of Implementing Siebel Fix Pack 7.8.2.14 226
Extracting Siebel Fix Pack 7.8.2.14 227
Applying Repository and Schema Changes 227
Applying Seed Data Changes 228
Activating the XMLP Components 229
Enabling the XMLP Components on the Siebel Server 231
Configuring the Outbound Web Service to the Oracle BI Publisher Server 232
Associating Oracle BI Publisher Reports with Siebel Views 233
Copying Fonts for Report Generation 233
Working with Oracle BI Publisher and Actuate Reports Concurrently 234
Enabling Logging for the Oracle BI Publisher Server 234
Process of Configuring Scheduling and Parameterization for Oracle BI Publisher
Reports 235
Importing Scheduling and Parameterization Features for Oracle BI Publisher Reports 235
Configuring JVM Settings 236
Configuring User Management for Oracle BI Publisher Reports 238
Configuring Report Scheduling for Oracle BI Publisher Reports 239
Configuring Report Parameterization for Oracle BI Publisher Reports 240
2 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X

Contents
Securing User Access to the Oracle BI Publisher Server 242

Configuring Security and Authentication Using the BI Publisher Security Model 243
Configuring Security and Authentication Using the LDAP Security Model 244
Configuring Security and Authentication Using the Siebel Security Model 246
Configuring the Siebel Mobile Client to Generate Oracle BI Publisher Reports 247
Testing Your ACR 483 Configurations 248
Instructions for FR 12-1K0VS0T 249
Instructions for FR 12-1BJO1E5 254
Instructions for FR 12-1CY8FKI 257
Instructions for FR 12-1ERTG8V 260
Instructions for FR 12-1FWLGC6 and FR 12-1DS2LPX 262
Instructions for FR 12-1IAE2QU 263
Instructions for FR 12-1J5IVKH 265
Installation Instructions for 7.8.2.x Fix Packs 266
Installation Overview 267
Installation Scenarios Described in This Section 267
Applicable Base Releases 269
About Running Siebel Image Creator 270
About Installing Additional Languages 270
About Installing Siebel Quick Fix Releases 270
Upgrade Requirements 271
About Installing Patch Releases for Siebel Products 271
Installing Patch Releases on Windows 272
Installing Patch Releases on UNIX 276
Configuring Slipstream Patch Installation 280
Installing New Languages 282
Postinstallation Task for the Siebel Server 285
Postinstallation Task for the Web Server 285
Postinstallation Tasks for High Interactivity Clients 286
Postinstallation Tasks for Supporting New Languages 286
Installing Siebel Universal Customer Master 289
Uninstalling Patch Releases 292
Resolved Change Requests 293
Resolved Change Requests in the Siebel 7.8.2.14 Fix Pack 293
General 293
Call Center 294
Comm Media Energy 294
Connectors/EAI 295
Customer Order Management 296
General 297

Contents
Loyalty 302
Marketing 303
Mobile Solutions 303
Sales 303
Service 304
Siebel eMail Response 304
Universal Customer Master 305
User Interface 305
Call Center 307
Connectors / EAI 308
Consumer Sector 309
Data Quality 311
Financial Services 311
General 311
iHelp 316
Life Sciences 316
Public Sector 319
Sales 319
Service 324
User Interface 325
Analytics 326
Call Center 326
Web Service 326
Consumer Sector 329
General 331
Life Sciences 335
Loyalty 336
Marketing 337
Sales 338
Service 338

Contents
User Interface 339

Call Center 342
Web Services 342
Consumer Sector 344
General 347
iHelp 351
Life Sciences 352
Loyalty 352
Marketing 352
Partner Relationship Management 354
Sales 354
Service 354
User Interface 355
Resolved Change Requests in the Siebel 7.8.2.1 Through 7.8.2.9 Fix Packs 357
Analytics 357
Automotive 357
Call Center 357
Connectors/ EAI 365
Consumer Sector 366
Data Quality 392
Employee Relationship Management 392
Enterprise Integration Manager/EIM 393
General 395
iHelp 427
Life Sciences 427
Loyalty 434
Marketing 435
Partner Relationship Management 441
Professional Services 442
Sales 443
Service 445

Contents
Travel & Transportation 449

UAN General Anomalies 449
User Interface 450
Web Service 460

1 Siebel Maintenance Release
Guide, Version 7.8.2, Rev. X
December 2009
Version 7.8.2, Rev. X
This guide includes the following topics:
■ What’s New in This Revision
■ Quick Fixes Included in 7.8.2.x Fix Packs
■ Enhancements and Updates in 7.8.2.x Fix Packs
■ Configuration Instructions for Enhancements and Updates
■ Installation Instructions for 7.8.2.x Fix Packs
■ Resolved Change Requests
Release Notes for the Siebel 7.8.2.14 Fix

Pack
The following section contains information about known issues related to the Siebel 7.8.2.14 Fix
Pack, as well as any applicable workaround information.
Siebel CTI Connect Is No Longer Supported

Siebel CTI Connect is no longer supported as of this release.
7.8.2.14 Quick Fixes for Actuate and BI Publisher Functionality

Customers who are implementing the Siebel 7.8.2.14 Fix Pack should also download 7.8.2.14
QF0E01 and 7.8.2.14 QF0E02. 7.8.2.14 QF0E01 provides Actuate 8 support for all platforms except
HP, and 7.8.2.14 QF0E02 resolves several issues related to BI Publisher functionality.
NOTE: The Siebel 7.8.2.15 Fix Pack will provide support for Actuate 8 on the HP platform. However,
both this Fix Pack and 7.8.2.14 QF0E01 will only be available through the end of 2009.
LMU Files and Seed Data Missing

Area: General
Subarea: Reports Server
Product Version: Siebel 7.8.2.14
Change Request: 12-1VR1SM1

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ What’s New in This Revision
Only ENU seed data files were provided in the Oracle Business Intelligence Publisher enhancement.
LMU files and seed data were not provided.
Use the following workaround to address this issue:
1 Create language specific list of values by copying the ENU records for the following LOV values
and then modifying the display value:
❏ XMLP_RPT_OUTPUT_TYPE
❏ XMLP_RPT_SCHEDULE_MODE
2 In Siebel Tools, query for symbolic strings added from the patch with prefix SBL_*.
3 Add foreign language translations for the new symbolic string objects.
4 Compile and deploy the language SRF.
What’s New in This Revision

Table 1 describes the changes in this version of the documentation.
Table 1. What’s New in Siebel Maintenance Release Guide, Version 7.8.2, Rev. X
Topic Description
Instructions for Oracle BI Publisher Updated this section.

Enhancements
Enhancements and Updates in 7.8.2.x Updated sections with Siebel 7.8.2.14 Fix Pack
Fix Packs information for the 7.8.2.14 prerelease.
Configuration Instructions for

Enhancements and Updates
Resolved Change Requests
How to Use This Book

This document, Maintenance Release Guide, Version 7.8.2, lists the enhancements and fixes
provided in version 7.8.2 and version 7.8.2.x releases.
This guide also provides information, instructions, and guidelines for installing Oracle’s Siebel
Business Applications version 7.8.2 as a maintenance release (patch) on top of an existing 7.8.x
installation, installing version 7.8.2.x Fix Pack releases on top of version 7.8.2, and installing
languages packs provided with version 7.8.2.

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ What’s New in This Revision
Use this Maintenance Release Guide in conjunction with Siebel Bookshelf documents such as the
Siebel Installation Guide for the operating system you are using.
NOTE: This Maintenance Release Guide is updated to include the latest version 7.8.2.x Fix Pack
release. The latest version 7.8.2.x Fix Pack release available at publication time is version 7.8.2.14.
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.
Terminology Used in This Guide

In this guide, any Siebel product release that you can install on top of an existing release may be
referred to as a patch release, maintenance release, or simply release. As outlined above, version
7.8.2 is a full release that can also be installed as a maintenance release on top of an existing
installation of a prior 7.8.x release.
A Fix Pack release is a four-digit release that can be installed as a patch release on top of any prior
release in the same series, such as on top of 7.8.2 or 7.8.2.1. In this guide, Fix PackFix Packs in the
series 7.8.2.1, 7.8.2.2, and so on, are collectively referred to as 7.8.2.x. Most references to version
7.8.2.x refer to the latest Fix Pack release.
In general, the terms version and release are used interchangeably in this guide.
The Siebel Image Creator utility creates or updates an installation image on your network, from
which you install Siebel applications. This is also called a network image or a Siebel image.
Installation Scenarios
Instructions in this guide apply in the following scenarios:
■ Performing new full installation of version 7.8.2, with version 7.8.2.x
■ Installing version 7.8.2 and version 7.8.2.x (patching existing 7.8.0 (Developer Release) or
7.8.1.x (Limited Release) installation)
■ Installing version 7.8.2.x (patching existing 7.8.2 or prior 7.8.2.x installation)
■ Installing languages (language packs) provided with version 7.8.2

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Quick Fixes Included in
7.8.2.x Fix Packs
Version 7.8.2.x Fix Pack releases are cumulative and do not need to be installed sequentially. For
example, you can install version 7.8.2, then install the latest version 7.8.2.x Fix Pack. You do not
have to install any prior 7.8.2.x Fix Pack before installing the latest 7.8.2.x Fix Pack. You can install
any later version 7.8.2.x Fix Pack on top of a prior 7.8.2.x Fix Pack.
For detailed information about these scenarios, see Installation Overview. Full installation of version
7.8.2 is covered in Installation Instructions for 7.8.2.x Fix Packs. This section provides information
about installing version 7.8.2 (as a patch release) and version 7.8.2.x releases, installing additional
languages provided with version 7.8.2, and postinstallation tasks you may need to perform.
Additional Documentation
Oracle reserves the right to modify the documentation for Siebel Business Applications at any time.
For related Siebel documentation, see OracleMetaLink 3 (https://metalink3.oracle.com and Bookshelf

for Oracle’s Siebel Applications for v7.8: http://download.oracle.com/docs/cd/B31104_02/
homepage.htm on Oracle Technology Network (OTN).
Product Documentation
Oracle reserves the right to modify the documentation for Siebel Business Applications at any time.
For Siebel documentation, see Oracle MetaLink 3 (https://metalink3.oracle.com and the Siebel
Bookshelf for Oracle's Siebel Applications Version 7.8 (http://download.oracle.com/docs/cd/
B31104_02/homepage.htm) on Oracle Technology Network (OTN).
Quick Fixes Included in 7.8.2.x Fix Packs

If you have installed a quick fix for any Siebel 7.8.x release prior to the latest 7.8.2.x covered by
this document, review Table 2 to make sure that your quick fix number is listed.
NOTE: There were no Quick Fixes merged into the Siebel 7.8.2.14 Fix Pack.
CAUTION: If you do not see your Quick Fix number in the table, do not install the latest 7.8.2.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 7.8.2.x
Change Fix Request Quick Fix Merged Into

Request ID ID Fix Pack Base Version Fix Pack
12-108H728 12-1LKB0FH 7.8.2.3 [19221] QF03D4 7.8.2.13
12-16DUIYU 12-1NVVYTH 7.8.2.3 [19221] QF03D9 7.8.2.13
12-1QMWX5R 12-1QNWL5X 7.8.2.3 [19221] QF03F5 7.8.2.13
12-1PCDHDP 12-1PZ4T2P 7.8.2.3 [19221] QF03F6 7.8.2.13

7.8.2.x Fix Packs

12-1MKB7V9 12-1N6TYJD 7.8.2.3 [19221] QFJ322 7.8.2.13
12-1PILEIJ 12-1RRTL54 7.8.2.3 [19221] QFJ322 7.8.2.13
12-1S85TE5 12-1S85TFG 7.8.2.3 [19221] QFJ323 7.8.2.13
12-1NNU3JH 12-1SUAJS5 7.8.2.3 [19221] QFJ324 7.8.2.13
12-1THNL1J 12-1THNL33 7.8.2.3 [19221] QFJ325 7.8.2.13
12-1TG5VA9 12-1TGO8BK 7.8.2.3 [19221] QFJ326 7.8.2.13
12-1KWV58T 12-1P2RHT5 7.8.2.4 [19224] QF0461 7.8.2.13
12-1Q3L025 12-1SOZ68J 7.8.2.4 [19224] QF0469 7.8.2.13
12-1RSS5YD 12-1RVO2VP 7.8.2.5 [19227] QF05A7 7.8.2.13
12-1R4A1RB 12-1RIPFUD 7.8.2.5 [19227] QF05A9 7.8.2.13
12-1K51E4X 12-1KFZ6YZ 7.8.2.6 [19230] QF0619 7.8.2.13
12-1T21JMR 12-1T21JP6 7.8.2.6 [19230] QF0688 7.8.2.13
12-1SC9C45 12-1SC9C4Z 7.8.2.6 PDA [19230_6] 7.8.2.6 PDA 7.8.2.13

[19230_6]
12-1RSS41H 12-1SDQHFO 7.8.2.8 [19237] QF0827 7.8.2.13
12-1JGY6HC 12-1RAJ5MR 7.8.2.10 [19241] QF0A02 7.8.2.13
12-1QUOKCX 12-1QX23RT 7.8.2.10 [19241] QF0A24 7.8.2.13
12-1R4A1RB 12-1RIPFTX 7.8.2.10 [19241] QF0A31 7.8.2.13
12-1S5B2PJ 12-1S99GF2 7.8.2.10 [19241] QF0A33 7.8.2.13
12-1FWL602 12-1QZY4K4 7.8.2.10 [19241] QF0A37 7.8.2.13
12-1LTGS5B 12-1QDA5D9 7.8.2.10 [19241] QF0A37 7.8.2.13
12-1MIVDVK 12-1QDA588 7.8.2.10 [19241] QF0A37 7.8.2.13
12-1RPHO7U 12-1RPHOCN 7.8.2.10 [19241] QF0A37 7.8.2.13
12-1S7PQF1 12-1S7PQJ4 7.8.2.10 [19241] QF0A37 7.8.2.13
12-XLYU4T 12-1QTPBF9 7.8.2.10 [19241] QF0A37 7.8.2.13
12-1S7POKB 12-1S7SIW7 7.8.2.10 [19241] QF0A38 7.8.2.13
12-PUDQB1 12-1SREMN1 7.8.2.10 [19241] QF0A40 7.8.2.13
12-1MBR3N7 12-1QDA53A 7.8.2.10 [19241] QF0A41 7.8.2.13
12-1OXSN8J 12-1OXSN9A 7.8.2.10 [19241] QF0A41 7.8.2.13
12-1SB91UB 12-1SLLFHX 7.8.2.10 [19241] QF0A42 7.8.2.13

7.8.2.x Fix Packs

12-1SFPA4D 12-1SFPA5I 7.8.2.10 [19241] QF0A42 7.8.2.13
12-1SG6A0Z 12-1SG6A1O 7.8.2.10 [19241] QF0A45 7.8.2.13
12-1Q0IVS7 12-1QBC7RH 7.8.2.10 [19241] QF0A46 7.8.2.13
12-1Q5L7UL 12-1T7GQA9 7.8.2.10 [19241] QF0A47 7.8.2.13
12-1PCDHDP 12-1TY3M7D 7.8.2.10 [19241] QF0A50 7.8.2.13
12-1LTGS5B 12-1LTYZBE 7.8.2.10 [19241] QF2A0 7.8.2.13
12-1LY4V61 12-1QDA0LG 7.8.2.10 [19241] QF2A0 7.8.2.13
12-1MBR3N7 12-1QDA52D 7.8.2.10 [19241] QF2A0 7.8.2.13
12-1MIVDVK 12-1QDA596 7.8.2.10 [19241] QF2A0 7.8.2.13
12-1OXSN8J 12-1QDA5HP 7.8.2.10 [19241] QF2A01 7.8.2.13
12-1RPHO7U 12-1RPHODL 7.8.2.10 [19241] QF2A01 7.8.2.13
12-XLYU4T 12-1QTPBG7 7.8.2.10 [19241] QF2A01 7.8.2.13
12-1OQD0BB 12-1TK8O7J 7.8.2.10 [19241] QF0A05 7.8.2.13
12-1S8Q8LJ 12-1S98CN6 7.8.2.11 [19244] QF0B04 7.8.2.13
12-VD0XNH 12-1S8KS79 7.8.2.11 [19244] QF0B05 7.8.2.13
12-1SBRA8B 12-1SBRA8W 7.8.2.11 [19244] QF0B07 7.8.2.13
12-1SZMHGR 12-1SZMHHL 7.8.2.11 [19244] QF0B07 7.8.2.13
12-TRBP9F 12-1SW7Q57 7.8.2.11 [19244] QF0B08 7.8.2.13
12-1OQD0BB 12-1THNJJ3 7.8.2.11 [19244] QF0B09 7.8.2.13
12-1THO6QN 12-1TK3P4Z 7.8.2.11 [19244] QF0B12 7.8.2.13
12-1SJNUGJ 12-1TDNZW5 7.8.2.11 [19244] QF0B13 7.8.2.13
12-1R4A1RB 12-1U08T8Z 7.8.2.11 [19244] QF0B17 7.8.2.13
12-1SB91UB 12-1SC28ZF 7.8.2.11 [19244] QF0B03 7.8.2.13
12-1SJNUGJ 12-1SZ537H 7.8.2.12 [19247] QF0C01 7.8.2.13
12-1R4A1RB 12-1U08T9N 7.8.2.12 [19247] QF0C02 7.8.2.13
12-1QUOKCX 12-1U17STF 7.8.2.12 [19247] QF0C04 7.8.2.13
12-1S8Q8LJ 12-1U5RRAP 7.8.2.12 [19247] QF0C06 7.8.2.13
12-1DRKC6T 12-1FV290N 7.8.2.3 [19221] QF0354 7.8.2.12
12-1JTG6V1 12-1JTG6W2 7.8.2.3 [19221] QF03BS 7.8.2.12
12-FOURWR 12-1PJK9MZ 7.8.2.3 [19221] QF03E8 7.8.2.12

7.8.2.x Fix Packs

12-1Q0IVOB 12-1Q1OFEI 7.8.2.3 [19221] QF03F3 7.8.2.12
12-1R1VGAZ 12-1R1VGBX 7.8.2.3 [19221] QF03F4 7.8.2.12
12-1RXY8FA 12-1RZ1GL9 7.8.2.3 [19221] QFJ321 7.8.2.12
12-1QZXUMT 12-1REDHGX 7.8.2.3 [19221] QFJ319 7.8.2.12
12-1RPEWYN 12-1RQU9DH 7.8.2.3 [19221] QFJ320 7.8.2.12
12-1QR99W7 12-1QR99WR 7.8.2.4 [19224] QF0465 7.8.2.12
12-1R75AA5 12-1R75AAX 7.8.2.4 [19224] QF0467 7.8.2.12
12-1J1ZOUE 12-1J1ZOVK 7.8.2.5 [19227] QF0564 7.8.2.12
12-1LMD4PF 12-1LMGI6T 7.8.2.5 [19227] QF0570 7.8.2.12
12-1GO70DP 12-1LX1X8J 7.8.2.5 [19227] QF0593 7.8.2.12
12-U7Q5X7 12-1PLGPPD 7.8.2.5 [19227] QF0598 7.8.2.12
12-1PWMKNX 12-1PWMKOI 7.8.2.5 [19227] QF0599 7.8.2.12
12-1GUIBBW 12-1QFSCMH 7.8.2.5 [19227] QF05A1 7.8.2.12
12-1F5JWPT 12-1P5695P 7.8.2.5 [19227] QF05A2 7.8.2.12
12-1QEA1TZ 12-1QEA1VD 7.8.2.5 [19227] QF05A3 7.8.2.12
12-1PWMP5B 12-1QNW4QB 7.8.2.5 [19227] QF05A4 7.8.2.12
12-1D2D48G 12-1QBCUBP 7.8.2.6 [19230] QF0679 7.8.2.12
12-1JTG2I5 12-1MIVJ7X 7.8.2.6 [19230] QF1801 7.8.2.12
12-1JTG2I5 12-1N327KX 7.8.2.6 [19230] QF1801 7.8.2.12
12-1MSUM5D 12-1MSUM6E 7.8.2.6 [19230] QF0648 7.8.2.12
12-1ME997V 12-1ME99D8 7.8.2.6 [19230] QF0675 7.8.2.12
12-1PG85QP 12-1PLGAOE 7.8.2.6 [19230] QF0677 7.8.2.12
12-1PILZ4H 12-1PILZ52 7.8.2.6 [19230] QF0680 7.8.2.12
12-1Q626EV 12-1QK16TN 7.8.2.6 [19230] QF0681 7.8.2.12
12-1O2HQ4R 12-1QR8QJA 7.8.2.6 [19230] QF0682 7.8.2.12
12-1Q35O1B 12-1Q625MJ 7.8.2.6 [19230] QF0683 7.8.2.12
12-1QR98KH 12-1QR98LH 7.8.2.6 [19230] QF0684 7.8.2.12
12-1JTG2I5 12-1NGR3P1 7.8.2.6 [192303] QF1801 7.8.2.12
12-1QFPJ7Z 12-1QFOT2G 7.8.2.6 WM5 [19230_4] 7.8.2.6 WM5 7.8.2.12

[19230_4]

7.8.2.x Fix Packs

12-1O2HQ4R 12-1O2HQ5C 7.8.2.6 WM5 [19230_5] 7.8.2.6 7.8.2.12

[19230_5]
12-1O2HQ4R 12-1R84VXU 7.8.2.6 WM5 [19230_5] 7.8.2.6 WM5 7.8.2.12

[19230_4]
12-1DRKC6T 12-1M3DW9Q 7.8.2.7 [19234] QF0710 7.8.2.12
12-1PLG9R7 12-1PLGB1H 7.8.2.7 [19234] QF0762 7.8.2.12
12-1Q92LOD 12-1QDA2ZB 7.8.2.7 [19234] QF0764 7.8.2.12
12-1PT60R3 12-1PX42MJ 7.8.2.7 [19234] QF0764 7.8.2.12
12-1QTP7FD 12-1RDWOIL 7.8.2.7 [19234] QF0765 7.8.2.12
12-WHE0WB 12-1QWL4JD 7.8.2.8 [19237] QF0822 7.8.2.12
12-1JTG2I5 12-1OOV74D 7.8.2.8 [19237] QF1801 7.8.2.12
12-1N22X1J 12-1N7RVTR 7.8.2.8 [19237] QF0806 7.8.2.12
12-1PQ8RSX 12-1Q1OF9Z 7.8.2.8 [19237] QF0820 7.8.2.12
12-1PT60OB 12-1Q6JWVB 7.8.2.8 [19237] QF0821 7.8.2.12
12-1Q71PT7 12-1Q909AM 7.8.2.8 [19237] QF0823 7.8.2.12
12-1QT8EZN 12-1ROXHM7 7.8.2.8 [19237] QF0825 7.8.2.12
12-1KIMIIJ 12-1R6NSVF 7.8.2.9 [19238] QF0905 7.8.2.12
12-1PLY5DH 12-1PZOL11 7.8.2.9 [19238] QF0907 7.8.2.12
12-1QWNHQL 12-1R75B3R 7.8.2.9 [19238] Q QF0906 7.8.2.12
12-1OI2RO5 12-1P9HALD 7.8.2.10 [19241] QF0A08 7.8.2.12
12-1QJ1W43 12-1QJJY1V 7.8.2.10 [19241] QF0A11 7.8.2.12
12-1QJ1W43 12-1QX2347 7.8.2.10 [19241] QF0A11 7.8.2.12
12-1Q71PVP 12-1QFY4SO 7.8.2.10 [19241] QF0A12 7.8.2.12
12-1QYIMX6 12-1R3AYKS 7.8.2.10 [19241] QF0A13 7.8.2.12
12-1PT60R3 12-1QFY5F8 7.8.2.10 [19241] QF0A14 7.8.2.12
12-1GUIBBW 12-1QMFKR5 7.8.2.10 [19241] QF0A16 7.8.2.12
12-1O2IS17 12-1REX8BJ 7.8.2.10 [19241] QF0A18 7.8.2.12
12-1RAJ07R 12-1RFCWQ3 7.8.2.10 [19241] QF0A19 7.8.2.12
12-1QR99W7 12-1RF944X 7.8.2.10 [19241] QF0A20 7.8.2.12
12-1OI2RO5 12-1P9HALD 7.8.2.10 [19241] QF0A08 7.8.2.12
12-1QJ1W43 12-1QJJY1V 7.8.2.10 [19241] QF0A11 7.8.2.12

7.8.2.x Fix Packs

12-1QJ1W43 12-1QX2347 7.8.2.10 [19241] QF0A11 7.8.2.12
12-1Q71PVP 12-1QFY4SO 7.8.2.10 [19241] QF0A12 7.8.2.12
12-1QYIMX6 12-1R3AYKS 7.8.2.10 [19241] QF0A13 7.8.2.12
12-1PT60R3 12-1QFY5F8 7.8.2.10 [19241] QF0A14 7.8.2.12
12-1GUIBBW 12-1QMFKR5 7.8.2.10 [19241] QF0A16 7.8.2.12
12-1O2IS17 12-1REX8BJ 7.8.2.10 [19241] QF0A18 7.8.2.12
12-1RAJ07R 12-1RFCWQ3 7.8.2.10 [19241] QF0A19 7.8.2.12
12-1QR99W7 12-1RF944X 7.8.2.10 [19241] QF0A20 7.8.2.12
12-1MM6X76 12-1MQCKML 7.8.2.10 [19241] QF0A21 7.8.2.12
12-1PQ8RSX 12-1RU7Z7T 7.8.2.10 [19241] QF0A23 7.8.2.12
12-1PT60OB 12-1RRC62L 7.8.2.10 [19241] QF0A24 7.8.2.12
12-1MTD3AQ 12-1RUP1ZH 7.8.2.10 [19241] QF0A26 7.8.2.12
12-1R75AA5 12-1S4CABZ 7.8.2.10 [19241] QF0A28 7.8.2.12
12-1RXY8FA 12-1SN2H12 7.8.2.10 [19241] QF0A35 7.8.2.12
12-1QZXUMT 12-1SN2H2I 7.8.2.10 [19241] QF0A36 7.8.2.12
12-1QT8EZN 12-1QT8F3P 7.8.2.10 [19241] QF2A01 7.8.2.12
12-1QBCIEN 12-1QBCIKE 7.8.2.10 [19241] QF2A01 7.8.2.12
12-1RPEWYN 12-1SN2H1P 7.8.2.10 [19241] QF0A35 7.8.2.12
12-1PE9R41 12-1RV740L 7.8.2.11 [19244] QF0B02 7.8.2.12
12-1JTG2I5 12-1OH2MLV 7.8.2.11 [19244] QF1801 7.8.2.12
12-1JV0W1H 12-1PS5Z93 7.8.2.10 [19241] QF0A01 7.8.2.11
12-1KRH24C 12-1Q06VHP 7.8.2.10 [19241] QF0A02 7.8.2.11
12-1PE98Y5 12-1PCUP1W 7.8.2.10 [19241] QF0A03 7.8.2.11
12-1PE98W7 12-1PE992P 7.8.2.10 [19241] QF0A03 7.8.2.11
12-1MYLIWN 12-1Q725LW 7.8.2.10 [19241] QF0A04 7.8.2.11
12-1OUTTE9 12-1QAHEET 7.8.2.10 [19241] QF0A05 7.8.2.11
12-1POSM7C 12-1QAHEHX 7.8.2.10 [19241] QF0A05 7.8.2.11
12-1PG85AB 12-1QDRG35 7.8.2.10 [19241] QF0A06 7.8.2.11
12-1QJ1WE3 12-1QK1H4H 7.8.2.10 [19241] QF0A09 7.8.2.11

12-1HPXCQP 12-1HPXCY8 7.8.2.3 [19221] QF03AP 7.8.2.11

7.8.2.x Fix Packs

12-1JV0W1H 12-1L51T82 7.8.2.3 [19221] QF03C2 7.8.2.11
12-1NWD6IX 12-1NWD6K0 7.8.2.3 [19221] QF03E3 7.8.2.11
12-1NBZX4T 12-1PAX5OZ 7.8.2.3 [19221] QF03E4 7.8.2.11
12-1NMF7K3 12-1NMF7KN 7.8.2.3 [19221] QF03E5 7.8.2.11
12-1MM7CTD 12-1PKZ0K5 7.8.2.3 [19221] QF03E6 7.8.2.11
12-1OA571N 12-1OA5727 7.8.2.3 [19221] QF03E6 7.8.2.11
12-1PJKJJF 12-1PJKJKS 7.8.2.3 [19221] QF03E6 7.8.2.11
12-1PV3ANX 12-1PX42TO 7.8.2.3 [19221] QF03E9 7.8.2.11
12-1P19TLP 12-1P0SA0V 7.8.2.3 [19221] QF03F1 7.8.2.11
12-1OVC1X9 12-1QJJQ9L 7.8.2.3 [19221] QF03F2 7.8.2.11
12-1G4O98M 12-1G6J3WL 7.8.2.3 [19221] QFE302 7.8.2.11
12-1HPXCQP 12-1O13BPZ 7.8.2.3 [19221] QFN301 7.8.2.11
12-1MCA5KV 12-1MDSKQB 7.8.2.3 WM5 [19221_10] 7.8.2.3 WM5 7.8.2.11

[19221_10]
12-1FBGZVR 12-1I7DZAV 7.8.2.4 [19224] QF0424 7.8.2.11
12-1NSKPJP 12-1NSKPK9 7.8.2.4 [19224] QF0457 7.8.2.11
12-1MCAAK1 12-1MCAAL3 7.8.2.4 [19224] QF0460 7.8.2.11
12-1NWENJ9 12-1NVVGIL 7.8.2.4 [19224] QF0463 7.8.2.11
12-1O5H1CL 12-1OBLMHZ 7.8.2.5 [19227] QF0591 7.8.2.11
12-1OVC1X9 12-1P1RNXC 7.8.2.5 [19227] QF0595 7.8.2.11
12-1HTDK6P 12-1HTDK8T 7.8.2.5 [19227] QF0531 7.8.2.11

12-1P81NGH 12-1P8IH5K 7.8.2.5 [19227] QF0598 7.8.2.11
12-1NJLF3J 12-1NLXFVH 7.8.2.6 [19230] QF0668 7.8.2.11
12-1MM7CTD 12-1N0KPL7 7.8.2.6 [19230] QF0670 7.8.2.11
12-1JC6UJ9 12-1P8ZR4A 7.8.2.6 [19230] QF0671 7.8.2.11
12-1N6CGIZ 12-1PC6BIN 7.8.2.6 [19230] QF0672 7.8.2.11
12-1KBLS9L 12-1OCJLGM 7.8.2.6 [19230] QF0674 7.8.2.11
12-1PG85AB 12-1PG3OJH 7.8.2.6 [19230] QF3602 7.8.2.11
12-1HPXCQP 12-1J1YVG4 7.8.2.6 [19230] QF0601 7.8.2.11
12-1LMZ94M 12-1LNZ4LV 7.8.2.6 [19230] QF0645 7.8.2.11

7.8.2.x Fix Packs

12-1NCHH5Z 12-1NDFOVL 7.8.2.6 [19230] QF0664 7.8.2.11
12-1NBZX4T 12-1NBZX5R 7.8.2.6 [19230] QF0668 7.8.2.11
12-1P0S6GP 12-1PSJ9MR 7.8.2.6 [19230] QF0676 7.8.2.11
12-1L2GKY7 12-1L2GKYZ 7.8.2.6 PDA [19230_1] 7.8.2.6 PDA 7.8.2.11

[19230_1]
12-1KRH24C 12-1KTW63P 7.8.2.7 [19234] QF0738 7.8.2.11
12-1GVJ1I5 12-1L7OV7D 7.8.2.7 [19234] QF0707 7.8.2.11
12-1MYLIWN 12-1N032DJ 7.8.2.7 [19234] QF0732 7.8.2.11
12-1NNUWZ5 12-1NT1YA3 7.8.2.7 [19234] QF0733 7.8.2.11
12-1LEZF5Z 12-1LEZF7N 7.8.2.7 [19234] QF0745 7.8.2.11
12-1JOFBKB 12-1NZ79HT 7.8.2.7 [19234] QF0747 7.8.2.11
12-1NJKYC7 12-1O0M3MV 7.8.2.7 [19234] QF0751 7.8.2.11
12-1NDJFWP 12-1NDJFXS 7.8.2.7 [19234] QF0757 7.8.2.11
12-1N6CGIZ 12-1O64OJ5 7.8.2.7 [19234] QF0758 7.8.2.11
12-1OVTSLR 12-1OVTSMM 7.8.2.7 [19234] QF0760 7.8.2.11
12-1PBVEDV 12-1PE9XLD 7.8.2.7 [19234] QF1702 7.8.2.11
12-1NKJK2V 12-1NKJK3F 7.8.2.7 [19234] QF0752 7.8.2.11
12-1NZODFZ 12-1OYUG3D 7.8.2.7 [19234] QF0753 7.8.2.11
12-1OVC1X9 12-1OVC1Y1 7.8.2.7 [19234] QF0755 7.8.2.11
12-1I1GBT5 12-1O9N09P 7.8.2.7 [19234] QF0756 7.8.2.11
12-1O36R9V 12-1O2ZSJ7 7.8.2.7 [19234] QF0759 7.8.2.11
12-1PILZ2T 12-1PJ2TLJ 7.8.2.7 [19234] QF0761 7.8.2.11
12-1NJKNF5 12-1NIN173 7.8.2.7 [19234] QF1702 7.8.2.11
12-1NALW8B 12-1NALW8V 7.8.2.8 [19237] QF0812 7.8.2.11
12-1LMFG3A 12-1P72ZLP 7.8.2.8 [19237] QF0816 7.8.2.11
12-1N3J10T 12-1PSN4F5 7.8.2.8 [19237] QF0818 7.8.2.11
12-1P18LL9 12-1P7KAAX 7.8.2.8 [19237] QF0819 7.8.2.11
12-1JTG2I5 12-1OOV74D 7.8.2.8 [19237] QF1801 7.8.2.11
12-1MYLIWN 12-1O3XRMN 7.8.2.8 [19237] QF0801 7.8.2.11
12-1JV0W1H 12-1P5N601 7.8.2.8 [19237] QF0813 7.8.2.11

7.8.2.x Fix Packs

12-1NMVTUP 12-1NMVTVF 7.8.2.8 [19237] QF0815 7.8.2.11
12-1GVJ1I5 12-1PTMX9M 7.8.2.9 [19238] QF0903 7.8.2.11
12-1OMWGIX 12-1OXAW53 7.8.2.9 [19238] QF1901 7.8.2.11
12-E0F3BX 12-1Q90A0Z 7.8.2.9 [19238] QF0904 7.8.2.11
12-11LSN3S 12-1JA8NM3 7.8.2.6 [19230] QF0614 7.8.2.10
12-12TA492 12-1MBP6PL 7.8.2.7 [19234] QF0722 7.8.2.10
12-18C53LY 12-1ORCNDL 7.8.2.8 [19237] QF0808 7.8.2.10
12-19869N5 12-1NWD9WB 7.8.2.7 [19234] QF0740 7.8.2.10
12-1BCQWWV 12-1F9I0G7 7.8.2.3 [19221] QF0348 7.8.2.10
12-1DOVFWZ 12-1LKB0B7 7.8.2.3 [19221] QF03D4 7.8.2.10
12-1DSNDFY 12-1DSNDHT 7.8.2.2 [19219] QF1204 7.8.2.10
12-1DSNDFY 12-1E4E0CB 7.8.2.2 [19219] QF0214 7.8.2.10
12-1DSNDFY 12-1E9FYOV 7.8.2.3 [19221] QF0312 7.8.2.10
12-1DSNDFY 12-1HGLRL8 7.8.2.4 [19224] QF0418 7.8.2.10
12-1DSNDFY 12-1OKIYER 7.8.2.6 [19230] QF0667 7.8.2.10
12-1DT6IB7 12-1NH8JQR 7.8.2.3 [19221] QF03E1 7.8.2.10
12-1EXGK4H 12-1OJ2H0D 7.8.2.8 [19237] QF0805 7.8.2.10
12-1FW5GDJ 12-1NDF8DD 7.8.2.6 [19230] QF0655 7.8.2.10
12-1G07N9F 12-1LCKF61 7.8.2.5 [19227] QF0568 7.8.2.10
12-1G07N9F 12-1N04279 7.8.2.7 [19234] QF0720 7.8.2.10
12-1GRZD9P 12-1GY700N 7.8.2.7 [19234] QF0703 7.8.2.10
12-1I4ZMCH 12-1I7EW2X 7.8.2.2 [19219] QF0219 7.8.2.10
12-1I4ZMCH 12-1L75AZH 7.8.2.4 [19224] QF0444 7.8.2.10
12-1IJUZYP 12-1LAWANG 7.8.2.6 [19230] QF0629 7.8.2.10
12-1IJUZYP 12-1OJ2H9E 7.8.2.8 [19237] QF0805 7.8.2.10
12-1JL69GJ 12-1MQBF8N 7.8.2.7 [19234] QF0723 7.8.2.10
12-1K1YCWH 12-1OHLI5S 7.8.2.8 [19237] QF0805 7.8.2.10
12-1KBNC1G 12-1O13A5L 7.8.2.6 [19230] QF0661 7.8.2.10
12-1KGMH5V 12-1KGMH78 7.8.2.4 [19224] QF0456 7.8.2.10
12-1KGO7K3 12-1MZ2SRV 7.8.2.6 [19230] QF0651 7.8.2.10

7.8.2.x Fix Packs

12-1KI5D2O 12-1KJ5L7U 7.8.2.5 [19227] QF0562 7.8.2.10
12-1L3Z5X1 12-1L3YXES 7.8.2.5 [19227] QF0571 7.8.2.10
12-1L89B79 12-1O2HQVQ 7.8.2.3 [19221] QFN301 7.8.2.10
12-1L9C3FT 12-1OA57LN 7.8.2.4 [19224] QF0458 7.8.2.10
12-1LBF1QO 12-1LEEZ5N 7.8.2.6 [19230] QF3601 7.8.2.10
12-1LC1A2Z 12-1OLI8DO 7.8.2.8 [19237] QF0807 7.8.2.10
12-1LDEQ3N 12-1PE97YB 7.8.2.4 [19224] QF0462 7.8.2.10
12-1LDEQ3N 12-1MJEBVN 7.8.2.7 [19234] QF0717 7.8.2.10
12-1LDEQ3N 12-1OH2B7Q 7.8.2.8 [19237] QF0803 7.8.2.10
12-1LH4DGT 12-1LH4DHJ 7.8.2.3 [19221] QF03D2 7.8.2.10
12-1LH4DGT 12-1MGGJA7 7.8.2.6 [19230] QF0666 7.8.2.10
12-1LI6FFI 12-1PE97YS 7.8.2.4 [19224] QF0462 7.8.2.10
12-1LI6FFI 12-1LMYEZ0 7.8.2.7 [19234] QF0708 7.8.2.10
12-1LI6FFI 12-1OH2B5X 7.8.2.8 [19237] QF0803 7.8.2.10
12-1LXLFA2 12-1OJ2H56 7.8.2.8 [19237] QF0805 7.8.2.10
12-1LXLFJM 12-1OI3OK7 7.8.2.8 [19237] QF0805 7.8.2.10
12-1LXMIR2 12-1NJ44RX 7.8.2.7 [19234] QF0728 7.8.2.10
12-1LXMIR2 12-1O3XOVN 7.8.2.8 [19237] QF0808 7.8.2.10
12-1M04HMN 12-1M17CMV 7.8.2.7 [19234] QF0749 7.8.2.10
12-1M0NF6T 12-1M1S002 7.8.2.6 [19230] QF0637 7.8.2.10
12-1M3T6MS 12-1M7DUUN 7.8.2.6 [19230] QF0642 7.8.2.10
12-1M4BIKL 12-1M4BIPW 7.8.2.7 [19234] QF0712 7.8.2.10
12-1M4BIKL 12-1OJ2HE9 7.8.2.8 [19237] QF0805 7.8.2.10
12-1M4BK6R 12-1M6OMZW 7.8.2.4 [19224] QF0453 7.8.2.10
12-1M4CTAH 12-1MHR6R3 7.8.2.5 [19227] QF0583 7.8.2.10
12-1M4UMZ7 12-1MTVX3J 7.8.2.7 [19234] QF0734 7.8.2.10
12-1M4UP57 12-1M56VER 7.8.2.3 [19221] QF03D8 7.8.2.10
12-1M4UP57 12-1NLY6LZ 7.8.2.7 [19234] QF0731 7.8.2.10
12-1M6VAR9 12-1N6CGU5 7.8.2.6 [19230] QF0656 7.8.2.10

12-1M7ES7R 12-1M7ES8E 7.8.2.6 [19230] QF3601 7.8.2.10

7.8.2.x Fix Packs

12-1M7GX6L 12-1OK0Q5Z 7.8.2.5 [19227] QF0588 7.8.2.10
12-1M8K2OX 12-1M8K2TT 7.8.2.6 [19230] QF0647 7.8.2.10
12-1MATDY7 12-1MATDZL 7.8.2.6 PDA [19230_3] 7.8.2.6 PDA 7.8.2.10

[19230_3]
12-1MCTJBR 12-1MCTJFN 7.8.2.4 [19224] QF3401 7.8.2.10
12-1ME9N7W 12-1NVVXF4 7.8.2.7 [19234] QF0733 7.8.2.10
12-1MI9KUX 12-1P565EP 7.8.2.3 [19221] QF03E6 7.8.2.10
12-1MI9KUX 12-1NXSQV9 7.8.2.7 [19234] QF0734 7.8.2.10
12-1MI9KUX 12-1O3XOTG 7.8.2.8 [19237] QF0802 7.8.2.10
12-1MI9KUX 12-1OLHKAX 7.8.2.9 [19238] QF0901 7.8.2.10
12-1MIVDTR 12-1MQCFKV 7.8.2.8 [19237] QF0805 7.8.2.10
12-1MPOVAP 12-1MRRNGP 7.8.2.6 [19230] QF0650 7.8.2.10
12-1MSATS6 12-1NFB9FH 7.8.2.5 [19227] QF0587 7.8.2.10
12-1MSAZCI 12-1NZNS7J 7.8.2.6 [19230] QF0660 7.8.2.10
12-1MSC1BJ 12-1MVQK79 7.8.2.4 [19224] QF0454 7.8.2.10
12-1MSV4EV 12-1MY4IZ7 7.8.2.6 [19230] QF0657 7.8.2.10
12-1MVEOSB 12-1MVEOT9 7.8.2.7 [19234] QF0742 7.8.2.10
12-1MW8D61 12-1MY3R4Z 7.8.2.7 [19234] QF0725 7.8.2.10
12-1MYLIS7 12-1NNDIF3 7.8.2.7 [19234] QF0729 7.8.2.10
12-1N03ODH 12-1N03OEF 7.8.2.5 [19227] QF0582 7.8.2.10
12-1N03OFF 12-1N03OG6 7.8.2.5 [19227] QF0586 7.8.2.10

12-1N0LQFP 12-1N0LQH8 7.8.2.6 [19230] QF0654 7.8.2.10
12-1N40J6C 12-1N5VOLB 7.8.2.6 [19230] QF0653 7.8.2.10
12-1N5V9BL 12-1N5V9CO 7.8.2.7 [19234] QF0725 7.8.2.10
12-1N6CEUR 12-1N8P0N0 7.8.2.6 [19230] QF0659 7.8.2.10
12-1N6TXTP 12-1N9NJS3 7.8.2.7 [19234] QF0727 7.8.2.10
12-1NALH1D 12-1NDWEIZ 7.8.2.7 [19234] QF0743 7.8.2.10
12-1NALW2H 12-1NDWE1S 7.8.2.7 [19234] QF0742 7.8.2.10
12-1NALW2H 12-1OHLHLF 7.8.2.8 [19237] QF0803 7.8.2.10
12-1NJLF4A 12-1NMVOWS 7.8.2.6 [19230] QF0662 7.8.2.10

7.8.2.x Fix Packs

12-1NKJKRL 12-1NKJKSJ 7.8.2.7 [19234] QF0730 7.8.2.10
12-1NNUJCN 12-1NPQOD9 7.8.2.7 [19234] QF0750 7.8.2.10
12-1NXBFQR 12-1O2ZDZ1 7.8.2.7 [19234] QF0754 7.8.2.10
12-1O139AX 12-1O139BO 7.8.2.5 [19227] QF0589 7.8.2.10
12-1OEL3NZ 12-1OE3JDW 7.8.2.7 [19234] QF0748 7.8.2.10
12-1OEL3NZ 12-1OVCLMP 7.8.2.8 [19237] QF0809 7.8.2.10
12-1OLHN69 12-1OLHKEB 7.8.2.7 [19234] QF0750 7.8.2.10
12-ZALGVD 12-1LTF7DF 7.8.2.5 [19227] QF0575 7.8.2.10
12-ZALGVD 12-1KMTIAN 7.8.2.6 [19230] QF0620 7.8.2.10
12-13HEJBV 12-1IGLZ4O 7.8.2.5 [19227] QF3501 7.8.2.8
12-15LZ0PJ 12-1KRG5EX 7.8.2.5 [19227] QF0563 7.8.2.8
12-18BVPZG 12-1MJVDHH 7.8.2.6 [19230] QF0646 7.8.2.8
12-18TWSSC 12-1JKOOOD 7.8.2.4 [19224] QF0433 7.8.2.8
12-1COJO4F 12-1K40AXY 7.8.2.4 [19224] QF0437 7.8.2.8
12-1COJO4F 12-1LU0G2L 7.8.2.6 [19230] QF0635 7.8.2.8
12-1COJO4F 12-1MZLGU5 7.8.2.7 [19234] QF0720 7.8.2.8
12-1DCUH2U 12-1DCXM8T 7.8.2.3 [19221] QF0301 7.8.2.8
12-1E7GLGL 12-1KMY2NL 7.8.2.3 [19221] QF03BU 7.8.2.8
12-1E7GLGL 12-1METCZD 7.8.2.7 [19234] QF0713 7.8.2.8
12-1E8PE3B 12-1J05K0V 7.8.2.5 [19227] QF0520 7.8.2.8
12-1ELW4U1 12-1JKMZLJ 7.8.2.4 [19224] QF0435 7.8.2.8
12-1ELW4U1 12-1ELW4WL 7.8.2.5 [19227] QF0548 7.8.2.8
12-1ELW4U1 12-1L220D8 7.8.2.6 [19230] QF0623 7.8.2.8
12-1FEV7DF 12-1KD93E1 7.8.2.4 [19224] QF0442 7.8.2.8
12-1FNN8PL 12-1KE3J9U 7.8.2.6 [19230] QF0633 7.8.2.8
12-1FT2GCY 12-1JXJEXL 7.8.2.5 [19227] QF0545 7.8.2.8
12-1G3SW7T 12-1KPBMGB 7.8.2.5 [19227] QF0559 7.8.2.8
12-1G656T6 12-1G64GQR 7.8.2.3 [19221] QF0367 7.8.2.8
12-1G6MQ04 12-1KKA6W3 7.8.2.6 [19230] QF0615 7.8.2.8

12-1GD066N 12-1GD069G 7.8.2.3 [19221] QF0391 7.8.2.8

7.8.2.x Fix Packs

12-1GD066N 12-1M3TEW5 7.8.2.7 [19234] QF0710 7.8.2.8
12-1GDIRHB 12-1JQD56V 7.8.2.4 [19224] QF0436 7.8.2.8
12-1GDIRHB 12-1KWBL4H 7.8.2.7 [19234] QF0706 7.8.2.8
12-1GE3EGA 12-1K62ESW 7.8.2.7 [19234] QF0704 7.8.2.8
12-1GJLPLM 12-1M18QXP 7.8.2.6 [19230] QF0640 7.8.2.8
12-1GK2GR8 12-1GOOM4V 7.8.2.5 [19227] QF0540 7.8.2.8
12-1GK2GR8 12-1J2YMH1 7.8.2.6 [19230] QF0603 7.8.2.8
12-1GV13QB 12-1JY2M11 7.8.2.3 [19221] QF5304 7.8.2.8
12-1H09LEB 12-1LWKNW7 7.7.2.9 [18382] QF0901 7.8.2.8
12-1H1YB1M 12-1LX7H6C 7.8.2.5 [19227] QF0576 7.8.2.8
12-1H8J1VY 12-1K8LHW7 7.8.2.6 [19230] QF0628 7.8.2.8
12-1HIVEAL 12-1LMH116 7.8.2.3 [19221] QF03D3 7.8.2.8
12-1HN5K1B 12-1KXCC78 7.8.2.6 [19230] QF0618 7.8.2.8
12-1HTFNUN 12-1K8LHWM 7.8.2.6 [19230] QF0628 7.8.2.8
12-1HWCC3D 12-1LWKNYI 7.8.2.7 [19234] QF0701 7.8.2.8
12-1I2UQ34 12-1KRR7O2 7.8.2.5 [19227] QF5501 7.8.2.8
12-1I2UQ34 12-1M93O6O 7.8.2.6 [19230] QF4601 7.8.2.8
12-1IBVB5T 12-1IERLKF 7.8.2.3 [19221] QF03BL 7.8.2.8
12-1IBVB5T 12-1M8I8M5 7.8.2.6 [19230] QF0639 7.8.2.8
12-1IBVB5T 12-1MT5XSA 7.8.2.7 [19234] QF0718 7.8.2.8
12-1IBVDFG 12-1LKD443 7.8.2.6 [19230] QF0620 7.8.2.8
12-1IF8YBJ 12-1IV3KGK 7.8.2.3 [19221] QF03BT 7.8.2.8
12-1IF8YBJ 12-1KUV3YM 7.8.2.7 [19234] QF0702 7.8.2.8
12-1IGLRHV 12-1JHFO1L 7.8.2.4 [19224] QF0436 7.8.2.8
12-1IGLRHV 12-1KWBL5J 7.8.2.7 [19234] QF0706 7.8.2.8
12-1IGM0QP 12-1J3HWTH 7.8.2.5 [19227] QF4501 7.8.2.8
12-1IOMFYR 12-1IRC828 7.8.2.3 [19221] QF03BB 7.8.2.8
12-1IOMFYR 12-1MFEGU5 7.8.2.6 [19230] QF0644 7.8.2.8
12-1IP3MI0 12-1IRK17C 7.8.2.3 [19221] QF03C7 7.8.2.8
12-1IP3MI0 12-1L1IPW3 7.8.2.6 [19230] QF0630 7.8.2.8

7.8.2.x Fix Packs

12-1IP3MI0 12-1MIS8ZN 7.8.2.7 [19234] QF0714 7.8.2.8
12-1IR1ALS 12-1IRKDKR 7.8.2.7 [19234] QF0706 7.8.2.8
12-1IV2L0N 12-1IVV4TP 7.8.2.3 [19221] QF03BO 7.8.2.8
12-1IV2L0N 12-1N02XU7 7.8.2.7 [19234] QF0721 7.8.2.8
12-1J2FZN1 12-1J5I9VB 7.8.2.5 [19227] QF4501 7.8.2.8
12-1J5J1AH 12-1LMQZDO 7.8.2.6 [19230] QF2601 7.8.2.8
12-1J5J1AH 12-1JGBIOS 7.8.2.6 [19230] QF0607 7.8.2.8
12-1J6KROP 12-1J6KRUZ 7.8.2.4 [19224] QF2403 7.8.2.8
12-1J6KROP 12-1KXXX1X 7.8.2.6 [19230] QF0622 7.8.2.8
12-1JBP01G 12-1JBP03L 7.8.2.4 [19224] QF0443 7.8.2.8
12-1JC7EHV 12-1JCRMCR 7.8.2.5 [19227] QF4501 7.8.2.8
12-1JD9K31 12-1KCPTLN 7.8.2.6 [19230] QF0616 7.8.2.8
12-1JD9K31 12-1M4DA4S 7.8.2.7 [19234] QF0710 7.8.2.8
12-1JFT7ZP 12-1JXIMRV 7.8.2.5 [19227] QF0546 7.8.2.8
12-1JNXYKV 12-1JRF4CV 7.8.2.5 [19227] QF0551 7.8.2.8
12-1JRGCSB 12-1KG5NXS 7.8.2.5 [19227] QF0579 7.8.2.8
12-1JUHIAC 12-1KAXCZ7 7.8.2.6 [19230] QF0617 7.8.2.8
12-1JUHICA 12-1K93GH9 7.8.2.6 [19230] QF0609 7.8.2.8
12-1JVHT5J 12-1LWJ19N 7.8.2.7 [19234] QF0706 7.8.2.8
12-1JWOVYQ 12-1JY26VG 7.8.2.5 [19227] QF0553 7.8.2.8
12-1JWXPJE 12-1JWZ492 7.8.2.5 [19227] QF0552 7.8.2.8
12-1JWZ08Z 12-1JY2QF9 7.8.2.5 [19227] QF0556 7.8.2.8
12-1JWZ08Z 12-1KXEY77 7.8.2.7 [19234] QF0703 7.8.2.8
12-1JYKJHX 12-1JYKJKX 7.8.2.3 [19221] QF03BZ 7.8.2.8
12-1JYKJHX 12-1M4USTE 7.8.2.7 [19234] QF0711 7.8.2.8
12-1JZ3XDD 12-1JZ3XHH 7.8.2.6 [19230] QF0609 7.8.2.8
12-1K0CG45 12-1K5KAGI 7.8.2.6 [19230] QF0611 7.8.2.8
12-1K0UO0B 12-1LNINAZ 7.8.2.7 [19234] QF0707 7.8.2.8
12-1K0WED0 12-1K4IY1F 7.8.2.4 [19224] QF0443 7.8.2.8

12-1K0WED0 12-1M0P38B 7.8.2.6 [19230] QF0634 7.8.2.8

7.8.2.x Fix Packs

12-1K3Y8W2 12-1K5IGPB 7.8.2.5 [19227] QF0533 7.8.2.8
12-1K3YJ4M 12-1K3YJ5X 7.8.2.6 [19230] QF0609 7.8.2.8
12-1K3Z5YW 12-1K4I3FQ 7.8.2.6 [19230] QF0620 7.8.2.8
12-1K405X2 12-1K4H4T2 7.8.2.3 [19221] QF03BS 7.8.2.8
12-1K405X2 12-1METD1G 7.8.2.7 [19234] QF0713 7.8.2.8
12-1K405ZO 12-1K5WCRE 7.8.2.3 [19221] QF03BW 7.8.2.8
12-1K5K9MP 12-1KF41VT 7.8.2.7 [19234] QF0714 7.8.2.8
12-1K60Q35 12-1KAXCYM 7.8.2.6 [19230] QF0609 7.8.2.8
12-1K62V6P 12-1K62SSV 7.8.2.5 [19227] QF0556 7.8.2.8
12-1K62V6P 12-1KXEY7T 7.8.2.7 [19234] QF0703 7.8.2.8
12-1K801GD 12-1K9OYT8 7.8.2.4 [19224] QF0440 7.8.2.8
12-1K8KWRR 12-1K8KXDL 7.8.2.3 [19221] QF03BT 7.8.2.8
12-1K8KWRR 12-1M4UM6X 7.8.2.7 [19234] QF0716 7.8.2.8
12-1K8LJO2 12-1K9P26P 7.8.2.5 [19227] QF0549 7.8.2.8
12-1K9OFVL 12-1KB5D97 7.8.2.3 [19221] QF03C5 7.8.2.8
12-1K9OFVL 12-1MIS8VD 7.8.2.7 [19234] QF0713 7.8.2.8
12-1K9OOI6 12-1KBM1YB 7.8.2.5 [19227] QF0560 7.8.2.8
12-1KCM430 12-1KCR4VB 7.8.2.6 [19230] QF0608 7.8.2.8
12-1KIMIUH 12-1LAUPE6 7.8.2.5 [19227] QF0566 7.8.2.8
12-1KIMIUH 12-1LNINE5 7.8.2.7 [19234] QF0707 7.8.2.8
12-1KL8VYM 12-1KUVOV2 7.8.2.6 PDA [19230_3] 7.8.2.6 PDA 7.8.2.8

[19230_3]
12-1KMBU6V 12-1LBIKXL 7.8.2.5 [19227] QF5502 7.8.2.8
12-1KMBU6V 12-1MU7LQJ 7.8.2.5 [19227] QF0581 7.8.2.8
12-1KMBU6V 12-1LWKNVX 7.8.2.7 [19234] QF0701 7.8.2.8
12-1KNZ65Y 12-1KQFC2G 7.8.2.5 [19227] QF0565 7.8.2.8
12-1KO0BIW 12-1KOACYA 7.8.2.3 [19221] QF03BX 7.8.2.8
12-1KOBM82 12-1KQF0C1 7.8.2.6 [19230] QF0616 7.8.2.8
12-1KPTOMP 12-1KQDB55 7.8.2.6 [19230] QF0623 7.8.2.8
12-1KQWSAI 12-1KUV45G 7.8.2.7 [19234] QF0702 7.8.2.8

7.8.2.x Fix Packs

12-1KT694D 12-1LNINDD 7.8.2.7 [19234] QF0707 7.8.2.8
12-1KUV9OR 12-1M0OQFJ 7.8.2.5 [19227] QF6504 7.8.2.8
12-1KUV9OR 12-1KUVTJM 7.8.2.6 [19230] QF0627 7.8.2.8
12-1L3FCL3 12-1L3GZ69 7.8.2.4 [19224] QF0445 7.8.2.8
12-1L4K0LS 12-1L5LPS0 7.8.2.6 [19230] QF0631 7.8.2.8
12-1L4K0LS 12-1MIBHZ7 7.8.2.7 [19234] QF0724 7.8.2.8
12-1L51LOI 12-1L51LU5 7.8.2.3 [19221] QF03C4 7.8.2.8
12-1L51LOI 12-1M4USU3 7.8.2.7 [19234] QF0716 7.8.2.8
12-1L75EGF 12-1L7Q0TY 7.8.2.6 [19230] QF0632 7.8.2.8
12-1L9B74C 12-1L9B756 7.8.2.5 [19227] QF0572 7.8.2.8
12-1L9B74C 12-1M1RTCD 7.8.2.6 [19230] QF0636 7.8.2.8
12-1LAUPGS 12-1MFY2WI 7.8.2.7 [19234] QF0713 7.8.2.8
12-1LEVEHU 12-1LEXHSJ 7.8.2.4 [19224] QF0448 7.8.2.8
12-1LIIY6E 12-1LIIY7I 7.8.2.4 [19224] QF0446 7.8.2.8
12-1LSO6N2 12-1LSXXMK 7.8.2.5 [19227] QF0577 7.8.2.8
12-1LVID39 12-1LWL15B 7.8.2.6 [19230] QF0638 7.8.2.8
12-1LVX3H3 12-1LWJ14X 7.8.2.7 [19234] QF0713 7.8.2.8
12-1LWJNFH 12-1LWJNGB 7.8.2.3 [19221] QF03C8 7.8.2.8
12-1LWJNFH 12-1M4USUI 7.8.2.7 [19234] QF0716 7.8.2.8
12-1LY4CD9 12-1LZKJ7M 7.8.2.5 [19227] QF0580 7.8.2.8
12-1M37WNS 12-1M37WPH 7.8.2.5 [19227] QF0578 7.8.2.8
12-1M37WNS 12-1MCANYY 7.8.2.7 [19234] QF0715 7.8.2.8
12-1M8MM8N 12-1M94ZS0 7.8.2.3 [19221] QF03D1 7.8.2.8
12-1M94CXF 12-1M94ZRD 7.8.2.3 [19221] QF03D5 7.8.2.8
12-1M94CXF 12-1MCSJ21 7.8.2.7 [19234] QF0716 7.8.2.8
12-BQ9JRE 12-1KPRCNQ 7.8.2.5 [19227] QF0567 7.8.2.8
12-GFPPTB 12-1KPTJU1 7.8.2.7 [19234] QF0706 7.8.2.8
12-IY12CI 12-1HWEOLW 7.8.2.5 [19227] QF0528 7.8.2.8
12-KISC0Q 12-1L1JLM3 7.8.2.5 [19227] QF6502 7.8.2.8

12-KISC0Q 12-1KOBC9D 7.8.2.5 [19227] QF0558 7.8.2.8

7.8.2.x Fix Packs

12-KISC0Q 12-1LJSJMW 7.8.2.7 [19234] QF0703 7.8.2.8
12-PR8UL0 12-1JZ2Q8S 7.8.2.3 [19221] QF03BR 7.8.2.8
12-Q47T8B 12-1KC71NR 7.8.2.4 [19224] QF0441 7.8.2.8
12-Q47T8B 12-1M0P3C8 7.8.2.6 [19230] QF0638 7.8.2.8
12-QUXJJ5 12-1LCKP1B 7.8.2.4 [19224] QF0447 7.8.2.8
12-QUXJJ5 12-1LY5N8E 7.8.2.7 [19234] QF0709 7.8.2.8
12-VWE00J 12-1K0DAVH 7.8.2.5 [19227] QF0557 7.8.2.8
12-12OZHTB 12-12OZI4P 7.8.2.5 [19227] QF0547 7.8.2.7
12-182BQGQ 12-1IIMRWW 7.8.2.1 [19216] QF0124 7.8.2.7
12-185GFP8 12-1DZ22WR 7.8.2.5 [19227] QF3501 7.8.2.7
12-1AVSREW 12-1JNVGMT 7.8.2.3 [19221] QF03BV 7.8.2.7
12-1BI8P0H 12-1HCKRZJ 7.8.2.3 [19221] QF030C 7.8.2.7
12-1CRT154 12-1JNXZW8 7.8.2.4 [19224] QF0434 7.8.2.7
12-1D5T7YR 12-1J63F94 7.8.2.5 [19227] QF0532 7.8.2.7
12-1DCNRBA 12-1JBPCGZ 7.8.2.4 [19224] QF0532 7.8.2.7
12-1DZ9VIJ 12-1HP0K03 7.8.2.3 [19221] QF03AT 7.8.2.7
12-1E6WSOI 12-1HY9J2W 7.8.2.3 [19221] QF03AY 7.8.2.7
12-1EE7E8T 12-1GE38TP 7.8.2.3 [19221] QF0395 7.8.2.7
12-1EIIJ8O 12-1IGKD55 7.8.2.3 [19221] QF03B3 7.8.2.7
12-1EIIJ8O 12-1JFQH9Z 7.8.2.5 [19227] QF0535 7.8.2.7
12-1EIIJ8O 12-1JOOM0B 7.8.2.6 [19230] QF0606 7.8.2.7
12-1F4YWQ4 12-1IRLCND 7.8.2.5 [19227] QF0523 7.8.2.7
12-1F4YWQ4 12-1JGX6M7 7.8.2.3 [19221] QF03BN 7.8.2.7
12-1FBZFGQ 12-1IRMJUJ 7.8.2.4 [19224] QF0426 7.8.2.7
12-1FFDG3C 12-1IY45FM 7.8.2.4 [19224] QF0428 7.8.2.7
12-1FIZJNP 12-1I0ZW37 7.8.2.5 [19227] QF0505 7.8.2.7
12-1FIZJNP 12-1GI4ATD 7.8.2.3 [19221] QF0381 7.8.2.7
12-1G24T0U 12-1G54DW1 7.8.2.3 [19221] QF03AW 7.8.2.7
12-1G9HYP7 12-1IV2I8X 7.8.2.5 [19227] QF0524 7.8.2.7
12-1GF25RP 12-1II3TQB 7.8.2.3 [19221] QFL302 7.8.2.7

7.8.2.x Fix Packs

12-1GF25RP 12-1IRC81C 7.8.2.3 [19221] QF03B7 7.8.2.7
12-1GF25RP 12-1IZ37MF 7.8.2.4 [19224] QF0429 7.8.2.7
12-1GF25RP 12-1KDJEH3 7.8.2.5 [19227] QF0550 7.8.2.7
12-1GF25RP 12-1KLPGZ4 7.8.2.6 [19230] QF0621 7.8.2.7
12-1GUIONJ 12-1IBW9M1 7.8.2.3 [19221] QF03BK 7.8.2.7
12-1GUZY3H 12-1H1ZUBW 7.8.2.3 [19221] QF03BF 7.8.2.7
12-1GZ7TLM 12-1H25E9X 7.8.2.3 [19221] QF0392 7.8.2.7
12-1H08UL2 12-1H63KVY 7.8.2.4 [19224] QF0430 7.8.2.7
12-1H08UL2 12-1J92UPZ 7.8.2.5 [19227] QF0541 7.8.2.7
12-1H1DHHZ 12-1H1DHIP 7.8.2.3 [19221] QF0393 7.8.2.7
12-1H3WJP9 12-1H4EDHF 7.8.2.3 [19221] QF03AZ 7.8.2.7
12-1H79NID 12-1H79NKU 7.8.2.5 [19227] QF0555 7.8.2.7
12-1H80XWH 12-1I6X675 7.8.2.5 [19227] QF0507 7.8.2.7
12-1HG1QKF 12-1HMJXWW 7.8.2.3 [19221] QF03AQ 7.8.2.7
12-1HGLS1M 12-1HJRTVR 7.8.2.5 [19227] QF0508 7.8.2.7
12-1HKB17M 12-1HR0UPP 7.8.2.3 [19221] QF03AX 7.8.2.7
12-1HML1IV 12-1HML7UI 7.8.2.3 [19221] QF03BD 7.8.2.7
12-1HML1IV 12-1JZ2E81 7.8.2.6 [19230] QF0605 7.8.2.7
12-1HN3LE6 12-1HVVO89 7.8.2.3 [19221] QF03AU 7.8.2.7
12-1HN3LE6 12-1IAVMGS 7.8.2.5 [19227] QF0511 7.8.2.7
12-1HPGZGV 12-1ID76OR 7.8.2.5 [19227] QF0513 7.8.2.7
12-1HPGZGV 12-1HQO8AO 7.8.2.4 [19224] QF0422 7.8.2.7
12-1HPGZGV 12-1KLSDBR 7.8.2.6 [19230] QF0612 7.8.2.7
12-1HPXCQP 12-1J1YVG4 7.8.2.6 [19230] QF0601 7.8.2.7
12-1HPXCQP 12-1HPXCY8 7.8.2.3 [19221] QF03AP 7.8.2.7
12-1HQ7I52 12-1I6DCE3 7.8.2.5 [19227] QF0513 7.8.2.7
12-1HQ7I5S 12-1I6DCDN 7.8.2.5 [19227] QF0513 7.8.2.7
12-1HSWAKX 12-1J93GQ8 7.8.2.4 [19224] QF0432 7.8.2.7
12-1HTDF2J 12-1HTE1J0 7.8.2.5 [19227] QF0522 7.8.2.7

12-1HVJDLF 12-1HVJDTH 7.8.2.3 [19221] QF03BD 7.8.2.7

7.8.2.x Fix Packs

12-1HWCBX0 12-1HWCC0H 7.8.2.5 [19227] QF0531 7.8.2.7
12-1HZUQAV 12-1HZUQJM 7.8.2.5 [19227] QF0531 7.8.2.7
12-1I0HK05 12-1IEQ974 7.8.2.5 [19227] QF0522 7.8.2.7
12-1I0XVCO 12-1I0XVKG 7.8.2.5 [19227] QF0522 7.8.2.7
12-1I1IH18 12-1I3Y2M6 7.8.2.3 [19221] QF03AS 7.8.2.7
12-1I3D5YX 12-1I3D688 7.8.2.4 [19224] QF0424 7.8.2.7
12-1I3DE9V 12-1I3DEB0 7.8.2.4 [19224] QF2401 7.8.2.7
12-1I3R7YL 12-1IYL6NN 7.8.2.3 [19221] QF03BH 7.8.2.7
12-1I3R7YL 12-1JWZ43T 7.8.2.5 [19227] QF0542 7.8.2.7
12-1I3R7YL 12-1K3HWXJ 7.8.2.3 [19221] QFJ308 7.8.2.7
12-1I3R7YL 12-1L1JLN7 7.8.2.5 [19227] QF6503 7.8.2.7
12-1I6E093 12-1I6E0BJ 7.8.2.3 [19221] QF03AR 7.8.2.7
12-1I6VHOH 12-1I7E7GF 7.8.2.4 [19224] QF0425 7.8.2.7
12-1I6WJ6M 12-1IH4D3F 7.8.2.3 [19221] QFB303 7.8.2.7
12-1I6WJ6M 12-1I6XPR2 7.8.2.5 [19227] QF0514 7.8.2.7
12-1I7X851 12-1I7X85Y 7.8.2.3 [19221] QF03B1 7.8.2.7
12-1IAC6SB 12-1ILM3L1 7.8.2.3 [19221] QF03B8 7.8.2.7
12-1IAD8KB 12-1IKJTR0 7.8.2.5 [19227] QF0522 7.8.2.7
12-1IAUTPJ 12-1ID6CVC 7.8.2.4 [19224] QF0427 7.8.2.7
12-1IBCP2J 12-1IBCP61 7.8.2.5 [19227] QF0522 7.8.2.7
12-1IBEJT9 12-1IC8PM1 7.8.2.5 [19227] QF0522 7.8.2.7
12-1IBV1AT 12-1IKJIR6 7.8.2.6 [19230] QF0602 7.8.2.7
12-1IBWHCH 12-1IC8P6W 7.8.2.4 [19224] QF0423 7.8.2.7
12-1IBWHCH 12-1ILL7Y2 7.8.2.3 [19221] QFL302 7.8.2.7
12-1IFNSNX 12-1IFNSP8 7.8.2.3 [19221] QF03AS 7.8.2.7
12-1IHL5T5 12-1IO2731 7.8.2.3 [19221] QF03B9 7.8.2.7
12-1II3R5W 12-1II63DR 7.8.2.5 [19227] QF0532 7.8.2.7
12-1IINAVP 12-1IJ4IHJ 7.8.2.3 [19221] QF03B6 7.8.2.7
12-1ILNI7X 12-1INJKF0 7.8.2.5 [19227] QF0517 7.8.2.7
12-1IOMFYR 12-1IRC828 7.8.2.3 [19221] QF03BB 7.8.2.7

7.8.2.x Fix Packs

12-1IP3F7J 12-1IRK15J 7.8.2.3 [19221] QF03BE 7.8.2.7
12-1IPGQRX 12-1J63J37 7.8.2.5 [19227] QF0533 7.8.2.7
12-1IS3EZC 12-1IS3XZ8 7.8.2.3 [19221] QF03B5 7.8.2.7
12-1IUL2T1 12-1IUL2UD 7.8.2.5 [19227] QF0530 7.8.2.7
12-1IVM41O 12-1IVMN9H 7.8.2.3 [19221] QF03BG 7.8.2.7
12-1IVNL8I 12-1IY3OWX 7.8.2.4 [19224] QF0431 7.8.2.7
12-1IVNL8I 12-1J9MOSD 7.8.2.5 [19227] QF0529 7.8.2.7
12-1J1FLV0 12-1J1FM8H 7.8.2.3 [19221] QFJ305 7.8.2.7
12-1J1FLV0 12-1JPU3WL 7.8.2.3 [19221] QF03BJ 7.8.2.7
12-1J30VA7 12-1J30VCA 7.8.2.5 [19227] QF0525 7.8.2.7
12-1J5GKMX 12-1J5IJSL 7.8.2.5 [19227] QF0534 7.8.2.7
12-1J5HG35 12-1J63S8V 7.8.2.3 [19221] QFJ306 7.8.2.7
12-1J92WS2 12-1J92WYD 7.8.2.5 [19227] QF0539 7.8.2.7
12-1JC724U 12-1JC72AE 7.8.2.3 [19221] QFJ304 7.8.2.7
12-1JGB3L0 12-1JGBCBJ 7.8.2.3 [19221] QF03BV 7.8.2.7
12-1JHFG2M 12-1JL6I8L 7.8.2.5 [19227] QF0544 7.8.2.7
12-1JK3LTD 12-1JQDHL6 7.8.2.3 [19221] QF03BM 7.8.2.7
12-1JTEUE1 12-1JTEUEM 7.8.2.6 [19230] QF0604 7.8.2.7
12-1JTEUE1 12-1JXHY9U 7.8.2.3 [19221] QF03BP 7.8.2.7
12-1JUHIDR 12-1K93GJR 7.8.2.6 [19230] QF0609 7.8.2.7
12-1K20DOB 12-1K20DP1 7.8.2.3 [19221] QF03BQ 7.8.2.7
12-CQQG3Q 12-1H9103P 7.8.2.3 [19221] QFJ307 7.8.2.7
12-GIQQ1B 12-1GUZDPV 7.8.2.3 [19221] QF0392 7.8.2.7
12-KAG3PM 12-1I0ZW3M 7.8.2.5 [19227] QF0505 7.8.2.7
12-KAG3PM 12-1GHMWC6 7.8.2.3 [19221] QF0381 7.8.2.7
12-KUL7HX 12-1GAIDAK 7.8.2.3 [19221] QF0366 7.8.2.7
12-KUL7HX 12-1JQEXAK 7.8.2.5 [19227] QF0537 7.8.2.7
12-VZ5W1R 12-1JCS2PJ 7.8.2.5 [19227] QF0543 7.8.2.7
12-1DIFPC9 12-1K95AL6 7.8.2.5 [19227] QF0547 7.8.2.7

12-1HP0M1F 12-1HPH48E 7.8.2.5 [19227] QF0547 7.8.2.7

7.8.2.x Fix Packs

12-1HPH4NF 12-1HPH4OO 7.8.2.5 [19227] QF0547 7.8.2.7
12-1HTDK6P 12-1HTDK8T 7.8.2.5 [19227] QF0531 7.8.2.7
12-1HZUW8N 12-1HZUWA6 7.8.2.5 [19227] QF0547 7.8.2.7
12-1JYJKQJ 12-1JZDLO8 7.8.2.4 [19224] QF0439 7.8.2.7
12-1CFOFQ3 12-1CFXANS 7.8.1.1 [19044] QF0104 7.8.2.6
12-1GL4XZX 12-1GMWIWI 7.8.2 [19161_UCM] QF5003 7.8.2.6
12-1HG1BO5 12-1HKRGX7 7.8.2 [19161_UCM] QF5004 7.8.2.6
12-1GVIZVC 12-1H1XB2C 7.8.2.2 [19219] QF0216 7.8.2.6
12-1CEXDCS 12-1G76YCF 7.8.2.2 [19219] QF0217 7.8.2.6
12-1E6DRJL 12-1E6DRKB 7.8.2.3 [19221] QF0309 7.8.2.6
12-1G66Y2M 12-1HBK5EB 7.8.2.3 [19221] QF030A 7.8.2.6
12-1HBTXCU 12-1HBTXDD 7.8.2.3 [19221] QF030B 7.8.2.6
12-1FCLG2J 12-1FFD8BD 7.8.2.3 [19221] QF0347 7.8.2.6
12-HFOTMD 12-1FV1YES 7.8.2.3 [19221] QF0376 7.8.2.6
12-14GZEHR 12-1GQCODL 7.8.2.3 [19221] QF0379 7.8.2.6
12-1FJLGBP 12-1GRWJ1F 7.8.2.3 [19221] QF0380 7.8.2.6
12-1GALIJ5 12-1GW4E8V 7.8.2.3 [19221] QF0382 7.8.2.6
12-182HB93 12-1GW4B3P 7.8.2.3 [19221] QF0384 7.8.2.6
12-1GUWDLD 12-1GUZDY1 7.8.2.3 [19221] QF0386 7.8.2.6
12-1GQWQN9 12-1GRVZMV 7.8.2.3 [19221] QF0387 7.8.2.6
12-L5R295 12-1GAJEQX 7.8.2.3 [19221] QF0390 7.8.2.6
12-1GZ7TLM 12-1H25E9X 7.8.2.3 [19221] QF0392 7.8.2.6
12-1GZSUYC 12-1H185OJ 7.8.2.3 [19221] QF0394 7.8.2.6
12-1GO748L 12-1GO749D 7.8.2.3 [19221] QF0396 7.8.2.6
12-1GY6VBX 12-1HCJ3XB 7.8.2.3 [19221] QF0397 7.8.2.6
12-1H1ZGMT 12-1H1ZYIF 7.8.2.3 [19221] QF0398 7.8.2.6
12-1HF16R2 12-1HF16S4 7.8.2.3 [19221] QF0399 7.8.2.6
12-1GREQAR 12-1GS63VV 7.8.2.3 [19221] QF03AA 7.8.2.6
12-UFYDEL 12-1HC00A4 7.8.2.3 [19221] QF03AA 7.8.2.6
12-1GG1HJ4 12-1GG1HOZ 7.8.2.3 [19221] QF03AB 7.8.2.6

7.8.2.x Fix Packs

12-1H60LJD 12-1H69ZYZ 7.8.2.3 [19221] QF03AC 7.8.2.6
12-1CG5OHL 12-1EMG9QN 7.8.2.3 [19221] QF03AD 7.8.2.6
12-1GLKAML 12-1GLKAOO 7.8.2.3 [19221] QF03AE 7.8.2.6
12-1H4W95G 12-1HD2G7O 7.8.2.3 [19221] QF03AG 7.8.2.6
12-1GQBQCZ 12-1HQKOZI 7.8.2.3 [19221] QF03AH 7.8.2.6
12-1GK2IBR 12-1GQCQXX 7.8.2.3 [19221] QF03AI 7.8.2.6
12-MRPP13 12-1HUEZ95 7.8.2.3 [19221] QF03AJ 7.8.2.6
12-1HTW1GF 12-1HTYFM2 7.8.2.3 [19221] QF03AK 7.8.2.6
12-1FWNQCH 12-1FX4F5G 7.8.2.3 [19221] QF03AL 7.8.2.6
12-1HZAPD3 12-1I0FT5P 7.8.2.3 [19221] QF03AM 7.8.2.6
12-17EE2FG 12-1I1IDAY 7.8.2.3 [19221] QF03AN 7.8.2.6
12-1DI7Y17 12-1GSFLBT 7.8.2.3 [19221] QF03AO 7.8.2.6
12-1H2IDCM 12-1H2Z2I1 7.8.2.3 [19221] QF03AO 7.8.2.6
12-138VFMS 12-1I7XRKY 7.8.2.3 [19221] QF03B2 7.8.2.6
12-Y3FYS2 12-1F4AF5T 7.8.2.3 [19221] QF2303 7.8.2.6
12-1D8VKB2 12-1H1ZUAH 7.8.2.3 [19221] QF2304 7.8.2.6
12-1DPDH8J 12-1GDZHSV 7.8.2.3 [19221] QF6303 7.8.2.6
12-1E6DRJL 12-1F0DLRC 7.8.2.3 [19221] QF8301 7.8.2.6
12-1BSM70H 12-1CF2D34 7.8.2.3 [19221] QFA302 7.8.2.6
12-1E6DRJL 12-1GY6VH7 7.8.2.3 [19221] QFJ301 7.8.2.6
12-1HF16R2 12-1HF16VS 7.8.2.3 [19221] QFJ302 7.8.2.6
12-1FX53WG 12-1G247QH 7.8.2.3 [19221] QFK301 7.8.2.6
12-1FN3JA8 12-1FNM5NR 7.8.2.3 [19221_8] 7.8.2.3 7.8.2.6

[19221_8]
12-1G63R0D 12-1G5MA1Y 7.8.2.3 [19221_8] 7.8.2.3 7.8.2.6

[19221_8]
12-1GSGXNY 12-1GTY30N 7.8.2.3 [19221_9] 7.8.2.3 7.8.2.6

[19221_9]
12-1G6OP3D 12-1G77RC3 7.8.2.4 [19224] QF0407 7.8.2.6
12-1GAL3XE 12-1H1AHRY 7.8.2.4 [19224] QF0409 7.8.2.6
12-1GE3I3V 12-1GK2SB5 7.8.2.4 [19224] QF0410 7.8.2.6

7.8.2.x Fix Packs

12-1DI7Y17 12-1HEZV72 7.8.2.4 [19224] QF0412 7.8.2.6
12-1H1ZGMT 12-1H581GR 7.8.2.4 [19224] QF0413 7.8.2.6
12-1D8VKB2 12-1H8IODZ 7.8.2.4 [19224] QF0414 7.8.2.6
12-UFYDEL 12-1HE3F1K 7.8.2.4 [19224] QF0415 7.8.2.6
12-1HFKAGX 12-1HG21JE 7.8.2.4 [19224] QF0416 7.8.2.6
12-1GY6VBX 12-1HJTR49 7.8.2.4 [19224] QF0417 7.8.2.6
12-1HP0N3Q 12-1HUG5EY 7.8.2.4 [19224] QF0419 7.8.2.6
12-1HQ0RZP 12-1HQ0S2Y 7.8.2.4 [19224] QF0419 7.8.2.6
12-1HSENAN 12-1HSV3X3 7.8.2.4 [19224] QF0419 7.8.2.6
12-1HSENBO 12-1HSV41J 7.8.2.4 [19224] QF0419 7.8.2.6
12-1HSENIN 12-1HSV400 7.8.2.4 [19224] QF0419 7.8.2.6
12-1HXH2HP 12-1HZCCNN 7.8.2.4 [19224] QF0420 7.8.2.6
12-1HF16R2 12-1I6WG9G 7.8.2.4 [19224] QF0421 7.8.2.6
12-1FJLGBP 12-1H1WXTZ 7.8.2.5 [19227] QF0501 7.8.2.6
12-1GZSUYC 12-1HBI4WX 7.8.2.5 [19227] QF0501 7.8.2.6
12-1HOZM1B 12-1HPHJT3 7.8.2.5 [19227] QF0502 7.8.2.6
12-1GY6VBX 12-1HWVBNL 7.8.2.5 [19227] QF0503 7.8.2.6
12-1G66Y2M 12-1HVUN16 7.8.2.5 [19227] QF0504 7.8.2.6
12-1H60LJD 12-1I3EE6F 7.8.2.5 [19227] QF0506 7.8.2.6
12-1HFIFD7 12-1HTGB0Y 7.8.2.5 [19227] QF0509 7.8.2.6
12-1HZAPD3 12-1IADICC 7.8.2.5 [19227] QF0510 7.8.2.6
12-1GUWDLD 12-1I4FP3Z 7.8.2.5 [19227] QF0512 7.8.2.6
12-1FCLG2J 12-1IAV0AL 7.8.2.5 [19227] QF0513 7.8.2.6
12-1DI7Y17 12-1IH566X 7.8.2.5 [19227] QF0515 7.8.2.6
12-1H2IDCM 12-1IHL6IF 7.8.2.5 [19227] QF0515 7.8.2.6
12-1GVIZVC 12-1IR175V 7.8.2.5 [19227] QF0519 7.8.2.6
12-1IOLYSM 12-1ION34E 7.8.2.5 [19227] QF0521 7.8.2.6
12-1EPYAX0 12-1HXY1Z8 7.8.2.5 [19227] QF1501 7.8.2.6
12-1FRYTFM 12-1FRYTK8 7.8.1.1 [19044] QF0105 7.8.2.5
12-1BMY8KF 12-1CMKMI1 7.8.2 [19213] QF1011 7.8.2.5

7.8.2.x Fix Packs

12-1EEVL37 12-1EIH6UA 7.8.2 [19213] QF1016 7.8.2.5
12-1GL4XZX 12-1GMWIWI 7.8.2 [19161_UCM] QF5003 7.8.2.5
12-1DEP6NA 12-1H1XB8I 7.8.2.2 [19219] QF0216 7.8.2.5
12-15J386J 12-1FT3H9P 7.8.2.3 [19221] QF3303 7.8.2.5
12-1CE669P 12-1FEAUOH 7.8.2.3 [19221] QF1302 7.8.2.5
12-1CX92OK 12-1FDVCVK 7.8.2.3 [19221] QF1302 7.8.2.5
12-1EAIV1R 12-1ECU55G 7.8.2.3 [19221] QF0309 7.8.2.5
12-1DEP6NA 12-1DEP6VE 7.8.2.3 [19221] QF0315 7.8.2.5
12-1EAITV3 12-1EAMKH9 7.8.2.3 [19221] QF0324 7.8.2.5
12-173WUM1 12-1E4X0JU 7.8.2.3 [19221] QF0326 7.8.2.5
12-1EUGMZN 12-1EZ02TI 7.8.2.3 [19221] QF0327 7.8.2.5
12-1B6PHFV 12-1F0CB9R 7.8.2.3 [19221] QF0329 7.8.2.5
12-1EL7LWL 12-1EVHDX0 7.8.2.3 [19221] QF0331 7.8.2.5
12-1EOBXNT 12-1EUYFKR 7.8.2.3 [19221] QF0332 7.8.2.5
12-1EJHIWS 12-1EMWEGT 7.8.2.3 [19221] QF0335 7.8.2.5
12-1EUG350 12-1EXF5KS 7.8.2.3 [19221] QF0337 7.8.2.5
12-1F8IO91 12-1F8HPQ2 7.8.2.3 [19221] QF0338 7.8.2.5
12-1E6WEZ6 12-1EXMB7F 7.8.2.3 [19221] QF0339 7.8.2.5
12-1EB7C1F 12-1EBBHT3 7.8.2.3 [19221] QF0340 7.8.2.5
12-1EXYLTC 12-1EXYLV0 7.8.2.3 [19221] QF0341 7.8.2.5
12-1EAIWZX 12-1F8HEML 7.8.2.3 [19221] QF0342 7.8.2.5
12-1F4BUQP 12-1F60W86 7.8.2.3 [19221] QF0343 7.8.2.5
12-11WHZ7D 12-1FFW4UA 7.8.2.3 [19221] QF0344 7.8.2.5
12-1EUHW9D 12-1EUI17F 7.8.2.3 [19221] QF0346 7.8.2.5
12-19DUIPI 12-19E1DYM 7.8.2.3 [19221] QF0347 7.8.2.5
12-1E6VZH7 12-1E6WE3B 7.8.2.3 [19221] QF0347 7.8.2.5
12-1FVIPQA 12-1FVKI6P 7.8.2.3 [19221] QF0349 7.8.2.5
12-G42V53 12-1FK3YIZ 7.8.2.3 [19221] QF0351 7.8.2.5
12-1EMYMKH 12-1FVICNG 7.8.2.3 [19221] QF0352 7.8.2.5

12-1FLGF8L 12-1FW1G29 7.8.2.3 [19221] QF0353 7.8.2.5

7.8.2.x Fix Packs

12-1EBUW9T 12-1FV1YDR 7.8.2.3 [19221] QF0354 7.8.2.5
12-1F9HXOT 12-1FC0WIN 7.8.2.3 [19221] QF0355 7.8.2.5
12-1FVLCE9 12-1FZ2ZN5 7.8.2.3 [19221] QF0357 7.8.2.5
12-1FN4NGJ 12-1FNN923 7.8.2.3 [19221] QF0358 7.8.2.5
12-1G2M3GL 12-1G2NUUT 7.8.2.3 [19221] QF0358 7.8.2.5
12-1G08XJV 12-1G08XLT 7.8.2.3 [19221] QF0359 7.8.2.5
12-1FBH4M1 12-1FBIETY 7.8.2.3 [19221] QF0360 7.8.2.5
12-1F7GO6A 12-1FB0LBT 7.8.2.3 [19221] QF0361 7.8.2.5
12-1D0N3BF 12-1FWM9W9 7.8.2.3 [19221] QF0363 7.8.2.5
12-1G5LE4K 12-1G76U1A 7.8.2.3 [19221] QF0363 7.8.2.5
12-1G75OUN 12-1G76ZV3 7.8.2.3 [19221] QF0364 7.8.2.5
12-1FW11DV 12-1FWON5V 7.8.2.3 [19221] QF0365 7.8.2.5
12-1FBZHZX 12-1FC174C 7.8.2.3 [19221] QF0368 7.8.2.5
12-1E0IX6G 12-1FZONWZ 7.8.2.3 [19221] QF0369 7.8.2.5
12-1E6FMHH 12-1FZONW3 7.8.2.3 [19221] QF0369 7.8.2.5
12-1EMFVML 12-1G5LVRZ 7.8.2.3 [19221] QF0369 7.8.2.5
12-1GD0GIH 12-1GCZXBY 7.8.2.3 [19221] QF0370 7.8.2.5
12-1EJ0C1P 12-1FZ5DCF 7.8.2.3 [19221] QF0373 7.8.2.5
12-1FW19I7 12-1FW1LZD 7.8.2.3 [19221] QF0373 7.8.2.5
12-1GA27ON 12-1GA27PD 7.8.2.3 [19221] QF0373 7.8.2.5
12-1G7QHMK 12-1GL4IV6 7.8.2.3 [19221] QF0374 7.8.2.5
12-1GFJFXH 12-1GKL8C1 7.8.2.3 [19221] QF0374 7.8.2.5
12-1GE0B0B 12-1GEMK35 7.8.2.3 [19221] QF0375 7.8.2.5
12-1G6MTDQ 12-1GCY4GN 7.8.2.3 [19221] QF0377 7.8.2.5
12-1CT6PEG 12-1GHKT21 7.8.2.3 [19221] QF0380 7.8.2.5
12-1B405OT 12-1GYOWJO 7.8.2.3 [19221] QF0389 7.8.2.5
12-5PSXQ8 12-1BJRUF3 7.8.2.3 [19221] QF6301 7.8.2.5
12-1EAIV1R 12-1F0DLTC 7.8.2.3 [19221] QF8301 7.8.2.5
12-1BSM70H 12-1CF2D34 7.8.2.3 [19221] QFA302 7.8.2.5
12-I3M1H6 12-1EEBQ4N 7.8.2.3 [19221] QFB302 7.8.2.5

7.8.2.x Fix Packs

12-Z86R4G 12-1F7GADA 7.8.2.3 [19221] QFC301 7.8.2.5
12-1FVK7VQ 12-1FVKLWD 7.8.2.3 [19221] QFC303 7.8.2.5
12-1B6PHFV 12-1FZMGGD 7.8.2.3 [19221] QFD301 7.8.2.5
12-1EXYLTC 12-1FZMGEQ 7.8.2.3 [19221] QFD301 7.8.2.5
12-RQTT47 12-1FTNVAK 7.8.2.3 [19221] QFD301 7.8.2.5
12-1FT54TH 12-1FT54V6 7.8.2.3 [19221] QFD302 7.8.2.5
12-1GMMW5D 12-1GMMW64 7.8.2.3 [19221] QFE303 7.8.2.5
12-1F3R04L 12-1F3R05L 7.8.2.3 [19221] QFE303 7.8.2.5
12-1F0DL3D 12-1G800D3 7.8.2.3 [19221] QFG301 7.8.2.5
12-173WUM1 12-1GF38IS 7.8.2.3 [19221] QFG302 7.8.2.5
12-1E6WEZ6 12-1GEK5Q0 7.8.2.3 [19221] QFG302 7.8.2.5
12-1EAITV3 12-1GF2GUJ 7.8.2.3 [19221] QFG302 7.8.2.5
12-1F0DL3D 12-1G800E2 7.8.2.3 [19221] QFG302 7.8.2.5
12-1DKDRRD 12-1FMLPP3 7.8.2.3 [19221] QFH301 7.8.2.5
12-1EJHIWS 12-1GCHF8C 7.8.2.3 [19221] QFH301 7.8.2.5
12-1E6VZH7 12-1GY6VJW 7.8.2.3 [19221] QFJ301 7.8.2.5
12-1EAIV1R 12-1GY6VIN 7.8.2.3 [19221] QFJ301 7.8.2.5
12-1G6P9GP 12-1G75VOO 7.8.2.3 [19221_7] 7.8.2.3 7.8.2.5

[19221_7]
12-1FBZFNC 12-1FD51UJ 7.8.2.3 WM5 [19221_4] 7.8.2.3 WM5 7.8.2.5

[19221_4]
12-1FW11DV 12-1GNNB0K 7.8.2.3SIA [19221] QF6302 7.8.2.5
12-1CSSQO7 12-1FW54OE 7.8.2.4 [19224] QF0401 7.8.2.5
12-19CTFX5 12-1GNLWU3 7.8.2.4 [19224] QF0402 7.8.2.5
12-1DU7ZCZ 12-1GOVT93 7.8.2.4 [19224] QF0403 7.8.2.5
12-1C0ARUL 12-1GQWWXQ 7.8.2.4 [19224] QF0404 7.8.2.5
12-1EUG350 12-1GUH6OT 7.8.2.4 [19224] QF0405 7.8.2.5
12-1FC2209 12-1H18EO2 7.8.2.4 [19224] QF0406 7.8.2.5
12-12D28US 12-1H6O73L 7.8.2.4 [19224] QF0408 7.8.2.5
12-1EB7C1F 12-1GZF5AT 7.8.2.4 [19224] QF0411 7.8.2.5
12-170GA6B 12-1EX6CG9 7.8.2 [19213] Branch QF6001 7.8.2.4

7.8.2.x Fix Packs

12-106O61K 12-1EG019Z 7.8.2.3 [19221] QF3301 7.8.2.4
12-OAS23C 12-1G04RZ2 7.8.2.3 [19221] QF0356 7.8.2.4
12-1DHXBGZ 12-1FSJDN7 7.8.2.3 [19221] QF2302 7.8.2.4
12-1B0PCBI 12-1EKVUJG 7.8.2.3 [19221] QF5301 7.8.2.4
12-1CLPMMD 12-1EKVULE 7.8.2.3 [19221] QF5301 7.8.2.4
12-1CT6EMH 12-1EKVUNC 7.8.2.3 [19221] QF5301 7.8.2.4
12-170GA6B 12-1FFY7EL 7.8.2.3 [19221] QF9301 7.8.2.4
12-1EUHZ81 12-1EVIHRL 7.8.2.3 WM5 [19221_1] 7.8.2.3 WM5 7.8.2.4

[19221_1]
12-TCQCOS 12-15P1WOD 7.8.2 [19213] QF0015 7.8.2.4
12-1CB4VBG 12-1CEIDUV 7.8.2 [19213] QF0033 7.8.2.4
12-R997QN 12-1CTY86B 7.8.2 [19213] QF0037 7.8.2.4
12-E49VJE 12-1CSZLT3 7.8.2 [19213] QF0038 7.8.2.4
12-1DS2LOR 12-1DS2LQT 7.8.2 [19213] QF0039 7.8.2.4
12-1APIYB7 12-1DQWT3O 7.8.2 [19213] QF0041 7.8.2.4
12-1BOCGNX 12-1BVSZ33 7.8.2 PDA [19213_5] 7.8.2 PDA 7.8.2.4

[19213_5]
12-1APIYB7 12-1BKH9M2 7.8.2.1 [19216] QF0113 7.8.2.4
12-19ZGK7N 12-1B9V685 7.8.2.1 [19216] QF0115 7.8.2.4
12-EACRKZ 12-1CP1VUB 7.8.2.1 [19216] QF0116 7.8.2.4
12-1DK2UO8 12-1DK6WV7 7.8.2.1 [19216] QF0118 7.8.2.4
12-1D3Z2PJ 12-1D5N696 7.8.2.1 [19216] QF0119 7.8.2.4
12-19XUD6T 12-19XUUYC 7.8.2.1 [19216] QF0120 7.8.2.4
12-1CY7NGD 12-1DSLU0F 7.8.2.1 [19216] QF0121 7.8.2.4
12-1ECCUZL 12-1EDUZA8 7.8.2.1 [19216] QF0122 7.8.2.4
12-17BDXWM 12-1ELXO53 7.8.2.1 [19216] QF0123 7.8.2.4
12-M38RXJ 12-19FDO4P 7.8.2.1 [19216] QF5102 7.8.2.4
12-1CGPFGV 12-1CGTOG2 7.8.2.2 [19219] QF0206 7.8.2.4
12-19ZGK7N 12-1D2J21A 7.8.2.2 [19219] QF0207 7.8.2.4
12-1BPMVNA 12-1BPMVZ8 7.8.2.2 [19219] QF0208 7.8.2.4
12-1DL58T7 12-1DLBXMG 7.8.2.2 [19219] QF0210 7.8.2.4

7.8.2.x Fix Packs

12-1DJ0LNN 12-1DL2ZJP 7.8.2.2 [19219] QF0212 7.8.2.4
12-1DS2M4Y 12-1DS2M6E 7.8.2.2 [19219] QF0213 7.8.2.4
12-R997QN 12-1FW3HC7 7.8.2.2 [19219] QF0215 7.8.2.4
12-1B9IZXJ 12-1B9KB0X 7.8.2.2 [19219] QF1202 7.8.2.4
12-1DGZH3B 12-1DL37OH 7.8.2.2 [19219] QF1203 7.8.2.4
12-106O61K 12-1F4V5WD 7.8.2.3 [19221] QF3302 7.8.2.4
12-1ERU766 12-1ETX2BY 7.8.2.3 [19221] QF3302 7.8.2.4
12-1F8YZRL 12-1F8YZSX 7.8.2.3 [19221] QF5302 7.8.2.4
12-12SECG8 12-1D5NY54 7.8.2.3 [19221] QF1301 7.8.2.4
12-16VBCE1 12-1D8THAB 7.8.2.3 [19221] QF1301 7.8.2.4
12-1BGP5KB 12-1D8N8PX 7.8.2.3 [19221] QF1301 7.8.2.4
12-1BWIR7X 12-1BWL4ON 7.8.2.3 [19221] QF1301 7.8.2.4
12-1DJ0LNN 12-1DNLSTB 7.8.2.3 [19221] QF1301 7.8.2.4
12-12KF1LR 12-1DS5D0Y 7.8.2.3 [19221] QF0302 7.8.2.4
12-1DWKLGQ 12-1DZ90YL 7.8.2.3 [19221] QF0305 7.8.2.4
12-EACRKZ 12-1E3OJHT 7.8.2.3 [19221] QF0305 7.8.2.4
12-1748YVY 12-1DE1HJV 7.8.2.3 [19221] QF0306 7.8.2.4
12-Q63CSV 12-1E9Y4A2 7.8.2.3 [19221] QF0307 7.8.2.4
12-18O4EAZ 12-1ECEDA4 7.8.2.3 [19221] QF0308 7.8.2.4
12-1A9JLPL 12-1ECB94I 7.8.2.3 [19221] QF0308 7.8.2.4
12-1AM14I5 12-1ECEDB5 7.8.2.3 [19221] QF0308 7.8.2.4
12-1AD8P9Z 12-1E44JFJ 7.8.2.3 [19221] QF0310 7.8.2.4
12-1E3B1GP 12-1E3SQTZ 7.8.2.3 [19221] QF0310 7.8.2.4
12-1E2AUOD 12-1E2AUVV 7.8.2.3 [19221] QF0311 7.8.2.4
12-1B9IZXJ 12-1E9FYNY 7.8.2.3 [19221] QF0312 7.8.2.4
12-R997QN 12-1DCVK95 7.8.2.3 [19221] QF0313 7.8.2.4
12-1D52692 12-1DVIG8X 7.8.2.3 [19221] QF0314 7.8.2.4
12-E49VJE 12-1ELX1VZ 7.8.2.3 [19221] QF0316 7.8.2.4
12-155LVQC 12-1EBPPQF 7.8.2.3 [19221] QF0317 7.8.2.4

12-1APIYB7 12-1ETZ9KG 7.8.2.3 [19221] QF0317 7.8.2.4

7.8.2.x Fix Packs

12-1D7JHH7 12-1EUGZDH 7.8.2.3 [19221] QF0318 7.8.2.4
12-TCQCOS 12-1EUYRRX 7.8.2.3 [19221] QF0319 7.8.2.4
12-1EJ16IC 12-1ELESJ7 7.8.2.3 [19221] QF0320 7.8.2.4
12-1DTRBFH 12-1EOU127 7.8.2.3 [19221] QF0321 7.8.2.4
12-1DK2UO8 12-1ETZ5DT 7.8.2.3 [19221] QF0322 7.8.2.4
12-1ECCUZL 12-1ETZKLV 7.8.2.3 [19221] QF0322 7.8.2.4
12-1D0SLHJ 12-1EWYMK4 7.8.2.3 [19221] QF0323 7.8.2.4
12-19XUD6T 12-1EV7ZTB 7.8.2.3 [19221] QF0325 7.8.2.4
12-19ZGK7N 12-1EXG7M4 7.8.2.3 [19221] QF0328 7.8.2.4
12-1DS2M4Y 12-1EXEGE9 7.8.2.3 [19221] QF0328 7.8.2.4
12-1E6CL2P 12-1F2CT79 7.8.2.3 [19221] QF0330 7.8.2.4
12-XNPOEH 12-1EPFE4X 7.8.2.3 [19221] QF0333 7.8.2.4
12-1EPZIYJ 12-1EQEP5A 7.8.2.3 [19221] QF0334 7.8.2.4
12-1ELX0H1 12-1F90SEJ 7.8.2.3 [19221] QF0336 7.8.2.4
12-1BYVPC7 12-1EXWLFP 7.8.2.3 [19221] QF0345 7.8.2.4
12-1EFI931 12-1F8YY4P 7.8.2.3 [19221] QF0347 7.8.2.4
12-11QVOFA 12-1E4WY6R 7.8.2.3 [19221] QF2301 7.8.2.4
12-1EA0ZXV 12-1EKVUIN 7.8.2.3 [19221] QF5301 7.8.2.4
12-XOU8DX 12-1DVECEV 7.8.2.3 [19221] QF5301 7.8.2.4
12-XOU8DX 12-1EKVUPF 7.8.2.3 [19221] QF5301 7.8.2.4
12-1EFH8EX 12-1EFH9DT 7.8.2.3 [19221] QF7301 7.8.2.4
12-QLXOIB 12-1EEFLOG 7.8.2.3 [19221] QF7301 7.8.2.4
12-1EUI5H2 12-1EUI5I0 7.8.2.3 [19221_2] 7.8.2.3 7.8.2.4

[19221_2]
12-1F5JMQD 12-1F5JMQX 7.8.2.3 WM5 [19221_3] 7.8.2.3 WM5 7.8.2.4

[19221_3]
12-1F9I5TD 12-1FBJ0X7 7.8.2.3 WM5 [19221_3] 7.8.2.3 WM5 7.8.2.4

[19221_3]
12-1CS189R 12-1FEB4KH 7.8.2.3 WM5 [19221_4] 7.8.2.3 WM5 7.8.2.4

[19221_4]
12-11AA4CY 12-11AJI4F 7.8.2 [19213] QF1002 7.8.2.3

7.8.2.x Fix Packs

12-11H2U2X 12-11H2U3U 7.8.2 [19213] QF1002 7.8.2.3
12-12TI4D4 12-1CS4Z0D 7.8.2 [19213] QF1011 7.8.2.3
12-131AXY2 12-17OZWK3 7.8.2 [19213] QF0027 7.8.2.3
12-131AXY2 12-18MYG9V 7.8.2.1 [19216] QF0107 7.8.2.3
12-131AXY2 12-1AYL3NT 7.8.2.2 [19219] QF0211 7.8.2.3
12-13VBZFB 12-1BX0932 7.8.2.2 [19219] QF1201 7.8.2.3
12-14SRU9B 12-15F1UQD 7.8.2 [19213] QF0018 7.8.2.3
12-15ZD78A 12-190ZZ59 7.8.2 [19213] QF0029 7.8.2.3
12-15ZD78A 12-1BOFC73 7.8.2.2 [19219] QF0201 7.8.2.3
12-160V8TB 12-1CU1Z57 7.8.2.1 [19216] QF6101 7.8.2.3
12-16HRCQ3 12-16IBX25 7.8.2 [19213] QF0022 7.8.2.3
12-16HRCQ3 12-18XP5UJ 7.8.2.1 [19216] QF0110 7.8.2.3
12-174OZ9B 12-174OZG4 7.8.2 [19213] QF1003 7.8.2.3
12-1769YNL 12-184OLK4 7.8.2 [19213] QF1003 7.8.2.3
12-1769YNL 12-17AG7XA 7.8.2 [19213] QF0020 7.8.2.3
12-177WVJJ 12-17B78E9 7.8.2 [19213] QF0024 7.8.2.3
12-17IAP5R 12-184OLI6 7.8.2 [19213] QF1003 7.8.2.3
12-17IAP5R 12-17IAPMR 7.8.2 [19213] QF0020 7.8.2.3
12-17QTH02 12-19KWZXJ 7.8.2 [19213] QF0027 7.8.2.3
12-184LGSY 12-184D2NE 7.8.2 [19213] QF0021 7.8.2.3
12-186C78G 12-186DCJH 7.8.2 [19213] QF0021 7.8.2.3
12-187O830 12-18BWXAN 7.8.2.1 [19216] QF0106 7.8.2.3
12-187O830 12-1BLWSRA 7.8.2.2 [19219] QF1201 7.8.2.3
12-18BWX0V 12-18BV2IF 7.8.2.1 [19216] QF0105 7.8.2.3
12-18BWX0V 12-1BX090X 7.8.2.2 [19219] QF1201 7.8.2.3
12-18CJ2Q1 12-18CIJR3 7.8.2 [19213] QF0021 7.8.2.3
12-18FCZ1J 12-18FCZ3Y 7.8.2 [19213] QF1003 7.8.2.3
12-18FZBHW 12-1B5PE1T 7.8.2 [19213] QF0031 7.8.2.3
12-18P56BP 12-1AYN6KR 7.8.2.2 [19219] QF0202 7.8.2.3

12-18P8ATF 12-19MEG2R 7.8.2.1 [19216] QF0111 7.8.2.3

7.8.2.x Fix Packs

12-18Q8EZ1 12-18Q8F07 7.8.2.1 [19216] QF4101 7.8.2.3
12-18TUFRD 12-19BTLC8 7.8.2.1 [19216] QF0109 7.8.2.3
12-18TXPAI 12-1920N5J 7.8.2 PDA [19213_3] 7.8.2 PDA 7.8.2.3

[19213_3]
12-18X6SZZ 12-18X78YL 7.8.2 PDA [19213_3] 7.8.2 PDA 7.8.2.3
[19213_3]
12-192QTBD 12-19EZJFE 7.8.2 [19213] QF2001 7.8.2.3
12-199Z7LK 12-199Z7OO 7.8.2 [19213] QF1004 7.8.2.3
12-199Z7LK 12-19F1WLE 7.8.2 [19213] QF1004 7.8.2.3
12-19WTMYV 12-19WTN27 7.8.2 [19213] QF1004 7.8.2.3
12-19YVICO 12-1BCRQE5 7.8.2 [19213] QF0032 7.8.2.3
12-1A9JPZL 12-1A9JQ27 7.8.2 [19213] QF1005 7.8.2.3
12-1AIZS4K 12-1ALR09S 7.8.2 [19213] QF1006 7.8.2.3
12-1B5HBGO 12-1B5QKI8 7.8.2.2 [19219] QF1201 7.8.2.3
12-1B6S62J 12-1BGQYFN 7.8.2 PDA [19213_4] 7.8.2 PDA 7.8.2.3

[19213_4]
12-1B9ZTQZ 12-1B9ZTTJ 7.8.2 [19213] QF1007 7.8.2.3
12-1BDW135 12-1BDWJK7 7.8.2.1 [19216] QF2102 QF2102 Branch 7.8.2.3

Branch Quickfix Quickfix
12-1BDW795 12-1BI58XB 7.8.2.2 [19219] QF0201 7.8.2.3
12-1BJSGHW 12-1BJTP4J 7.8.2 [19213] QF1008 7.8.2.3
12-1BSDL7F 12-1BV8LI1 7.8.2.1 [19216] QF3101 7.8.2.3
12-1BWLGK9 12-1CG28QV 7.8.2.1 [19216] QF2102 Branch 7.8.2.3

Quickfix
12-1BXXYXD 12-1BY1ETB 7.8.2 [19213] QF1009 7.8.2.3
12-1CHK6H8 12-1CHK6V7 7.8.2 [19213] QF0035 7.8.2.3
12-1CMUHMR 12-1CMUHSY 7.8.2 [19213] QF1010 7.8.2.3
12-1CQYDZ5 12-1CU765P 7.8.2.2 [19219] QF0205 7.8.2.3
12-1CY9IV1 12-1CY9JA4 7.8.2 [19213] QF1010 7.8.2.3
12-DEEPHB 12-18M06CS 7.8.2.1 [19216] QF2102 Branch 7.8.2.3

Quickfix
12-HX7923 12-17EJAW1 7.8.2.1 [19216] QF0104 7.8.2.3

7.8.2.x Fix Packs

12-HX7923 12-1BLWT90 7.8.2.2 [19219] QF1201 7.8.2.3
12-OWLV0O 12-18NBV6H 7.8.2.1 [19216] QF1101 7.8.2.3
12-T2FO1P 12-18DZJFB 7.8.2 [19213] QF0025 7.8.2.3
12-T2FO1P 12-1B6Q51A 7.8.2.2 [19219] QF0204 7.8.2.3
12-TMKKIA 12-1AZYV5K 7.8.2.1 [19216] QF0112 7.8.2.3
12-TSZJJN 12-1AYL3C9 7.8.2.2 [19219] QF1201 7.8.2.3
12-U0SAEP 12-1CZ39UW 7.8.2.1 [19216] QF6101 7.8.2.3
12-U0SAEP 12-1B9V5RI 7.8.2.1 [19216] QF0114 7.8.2.3
12-ZJ1AG5 12-ZJ1AH2 7.8.2 [19213] QF1002 7.8.2.3
12-ZOXVZD 12-1CZ39E6 7.8.2.1 [19216] QF6101 7.8.2.3
12-ZOXVZD 12-1B9V5UW 7.8.2.1 [19216] QF0114 7.8.2.3
12-11ZRC2T 12-1206ROV 7.8.1 [19042] QF1001 7.8.2.2
12-11ZRC2T 12-15V99F0 7.8.1.1[19044] QF1101 7.8.2.2
12-1203DJ5 12-17VYVBY 7.8.2.1 [19216_1] 7.8.2.1 7.8.2.2

[19216_1]
12-121Q35N 12-16ZTPK7 7.8.2 [19213] QF0016 7.8.2.2
12-12UKJ8B 12-12ZNXRO 7.8.2 [19213] QF0005 7.8.2.2
12-12ZQJVR 12-19CNMY5 7.8.2.1 [19216] QF2101 7.8.2.2
12-131CEK8 12-17SBFZ7 7.8.2 [19213] QF0023 7.8.2.2
12-133EXGL 12-133EXIV 7.8.2 [19213] QF0007 7.8.2.2
12-139DIGB 12-13O848X 7.8.2 [19213] QF0017 7.8.2.2
12-14ZV2IQ 12-19WXDBS 7.8.2.1 [19216] QF0108 7.8.2.2
12-157878Z 12-15787BP 7.8.2 [19213] QF0008 7.8.2.2
12-15AAHO2 12-15AAHSU 7.8.1.1 [19044_1] 7.8.1.1 7.8.2.2

[19044_1]
12-15AAHO2 12-1B3U5VQ 7.8.2.1 [19216_2] 7.8.2.1 7.8.2.2

[19216_2]
12-15ONRTT 12-17HZFZM 7.8.1.1 [19044_1] 7.8.1.1 7.8.2.2

[19044_1]
12-15ONRTT 12-19PSTMR 7.8.2 PDA [19213_5] 7.8.2 PDA 7.8.2.2

[19213_5]

7.8.2.x Fix Packs

12-15ONRTT 12-186CPRO 7.8.2.1 [19216_1] 7.8.2.1 7.8.2.2

[19216_1]
12-15UEFOI 12-17EV0YW 7.8.2 [19213] QF1002 7.8.2.2
12-15UEFOI 12-15UEFQS 7.8.2 [19213] QF0011 7.8.2.2

12-15X7O2Q 12-15Z9F5K 7.8.2 [19213] QF0010 7.8.2.2
12-15ZD5XM 12-18RBO3D 7.8.2.1 [19216] QF2101 7.8.2.2
12-15ZJKKB 12-15ZK4MW 7.8.2 [19213] QF0014 7.8.2.2
12-160QR4S 12-171O2XX 7.8.2 [19213] QF0017 7.8.2.2
12-161J4B2 12-166SO4R 7.8.2 [19213] QF0009 7.8.2.2
12-16EHBLB 12-1BBVULL 7.8.2 [19213] QF0030 7.8.2.2
12-16EHBLB 12-16EKQCE 7.8.2.1 [19216] QF0101 7.8.2.2
12-16F0D7T 12-16OS065 7.8.2 [19213] QF0013 7.8.2.2
12-16F3J3T 12-16LHWPA 7.8.2 [19213] QF0014 7.8.2.2
12-16N1XUK 12-16OL5HU 7.8.2 [19213] QF0017 7.8.2.2
12-16VR3K3 12-16VR3MY 7.8.2 [19213] QF0017 7.8.2.2
12-16XIENV 12-16ZQGJL 7.8.2 [19213] QF1002 7.8.2.2
12-16XLA97 12-1704GHL 7.8.2.1 [19216] QF0102 7.8.2.2
12-175M220 12-175NB20 7.8.2 [19213] QF0018 7.8.2.2
12-178SHRD 12-17F45YE 7.8.2 [19213] QF0017 7.8.2.2
12-17EEEO9 12-17EHKP9 7.8.2 [19213] QF0019 7.8.2.2
12-17GLJV4 12-18RFDDJ 7.8.2 [19213] QF0023 7.8.2.2

12-186NX2D 12-1AIFCLH 7.8.2 [19213] QF0028 7.8.2.2
12-197UX0E 12-19PMR3V 7.8.2 [19213] QF3001 7.8.2.2
12-JQ66YF 12-1ADJNAZ 7.8.2 [19213] QF2001 7.8.2.2
12-R5WXCB 12-14HD5QZ 7.8.2 [19213] QF0012 7.8.2.2
12-UA5DSZ 12-175DJB7 7.8.2.1 [19216] QF2101 7.8.2.2
12-Z8VLZL 12-187DIP9 7.8.2.1 [19216] QF2101 7.8.2.2
12-105UB8Y 12-10SKQHD 7.8.1 [19042] QF0006 7.8.2.1
12-105UB8Y 12-10STCPU 7.8.2 [19213] QF0004 7.8.2.1
12-105VG5N 12-1487ZDZ 7.8.2 [19213] QF0006 7.8.2.1

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Enhancements and Updates
in 7.8.2.x Fix Packs

12-108AZM7 12-10GJ7B0 7.8.2 [19213] QF0001 7.8.2.1
12-10P6QCA 12-10PL5OC 7.8.1 [19042] QF0006 7.8.2.1
12-10P6QCA 12-12R37DT 7.8.2 [19213] QF0004 7.8.2.1
12-11AGPN6 12-11AF5EF 7.8.1 [19042] QF0006 7.8.2.1
12-11AGPN6 12-11NORQU 7.8.2 [19213] QF0004 7.8.2.1
12-145Z3QB 12-145Z3T6 7.8.2 [19213] QF0006 7.8.2.1
12-RIVLWC 12-12IPDPZ 7.8.2 [19213] QF0003 7.8.2.1
Enhancements and Updates in 7.8.2.x

Fix Packs
This section identifies the enhancements and updates provided in version 7.8.2 and 7.8.2.x releases.
Enhancements in 7.8.2.x Fix Pack releases are cumulative. This section contains the following topics:
■ Enhancements and Updates in Version 7.8.2.14
■ Enhancements and Updates in Version 7.8.2

Enhancements and Updates in Version 7.8.2.14

The Siebel 7.8.2.14 Fix Pack provided the following enhancements to the BI Publisher functionality:
■ Enables reports with parameters.
■ Enables scheduling.
■ Provides a new Web service to support the new BI Publisher security model.

Table 4 contains the enhancements and updates contained in version 7.8.2.13.
Table 3. Enhancements and Updates in Version 7.8.2.13
Feature Enhancement
or Certification # Feature Enhancement or Certification Description
ACR 266/ACR 277 Supports starting the ChartWorks engine with QuickStart.
ACR 369 Provides support for Outlook Embedded Calendar on Outlook 2007.
ACR 471 ACR 471 provides the following enhancements:
■ Resolves a problem with Product Promotions where users add

a Customizable Product and add an invalid promotion. When
the Undo operation is performed and the promotion is
removed, and the user then adds a new Customizable Product
within the same view, the Customizable Product does not get
saved.
■ Automatically sets attribute values at promotion upgrade.
■ When applying or upgrading a promotion associated with a

Complex Product, product class port defaults/constraints are
not applied and the user needs to launch the configurator to
make the appropriate selection.
■ Changing promotions on order line items does not update

products correctly.

Feature Enhancement
ACR 481 ACR 481 provides the following SSSE enhancements:
■ Ability to use Exchange as system of record.
■ PIMSI Dispatcher User Filtering
■ Preserves Outlook categories when synchronizing contacts
ACR 481 resolves the following issues with SSSE:
■ Account lockout issue with Outlook Add-in
■ Missing connector causes engine crash
■ If the “Category Field” for the contact domain is changed from

the default “Category,” contact matching fails during
synchronization
■ SSSE skips record-level failures of any kind during

synchronization
ACR 504 Provides an integration to allow users to synchronize accounts,

contacts, opportunities, and products between Oracle CRM On
Demand and Siebel CRM (Siebel CRM On Premise) for both Siebel
Enterprise Applications (SEA) and Siebel Industry Applications (SIA)
and for all available platforms.
NOTE: This functionality was previously provided by two separate

ACRs: ACR 389 for SEA, provided in the Siebel 7.8.2.11 Fix Pack, and
and ACR 460 for SIA, provided in the Siebel 7.8.2.12 Fix Pack.

Feature Enhancement
ACR 302 Enhances the “Generate Hierarchy” button performance so that it can
process a large number of records.
ACR 409 Provides support for Microsoft Office 2007 with Document Server and
Siebel Search.

Feature Enhancement
ACR 444 Provides the following enhancements:
■ A utility for administrators to act on failing Store and Forward

transactions.
■ Enhanced logging capabilities (Server).
ACR 460 NOTE: This enhancement extends the functionality provided by ACR
389 to provide support for SIA.
Provides an integration to allow users to synchronize accounts,

Demand and Siebel CRM (Siebel CRM On Premise).
Please note that there is a known issue associated with ACR 460. For
more information, see “Instructions for FR 12-1CY8FKI” on page 257.

Feature Enhancement
ACR 389 NOTE: This enhancement applies for Siebel 7.8.2.x SEA only.
Provides an integration to allow users to synchronize accounts,

Demand and Siebel CRM (Siebel CRM on Premise).
ACR 391 Resolves a problem where having the EXISTS operator in the
searchspec field of the UI Data Web Service causes an error.

Feature Enhancement
ACR 427 Allows the Turkish i-dot character to be handled correctly in data
queries.
■ 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 one-time

charges, promotions, customizable product pricing, and asset-
based ordering enhancements
■ Nested Service bundle


Feature Enhancement
ACR 379 Corrects an issue where when the splash screen is activated, and any
windows with the WS_POPUP style are also activated regardless of
whether or not the windows are created by the Siebel application.
■ 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 syncs. The Exchange archive removes records
in Exchange that were not synched.
■ 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 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.
ACR 432 Prevents users from opening multiple sessions on the Mobile Web
Client.


Feature Enhancement or
Certification # Feature Enhancement or Certification Description
ACR 347 ACR 347 provides Personalized Content Delivery. It includes the
following enhancements:
■ 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 8 lists the enhancements and updates contained in version 7.8.2.8.
ACR 296 Corrects a problem where Territory Rules are incorrectly

translated in Assignment Manager.
ACR 372 Updates the MedWatch Report (LS_3500A) to reflect new

formatting and fields:
■ 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:
■ New fields on the “LS Medical Product Issue RR” Business

Component:

■ STN#
■ PMA/510(k)
ACR 373B This ACR provides the following functionality:
■ 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 systemo-wide

and a server-wide parameter for ‘UserMailBoxIDSource’.
ACR 382 Provides an option for MQ transport to disable report

generation.


Feature Enhancement or Certification Description

Certification #
ACR 271 Certifies Microsoft Internet Explorer 7 on Windows XP SP2.
ACR 365 Allows Campaign loads between Siebel 7.7 or 7.8 and Oracle
Business Intelligence Enterprise Edition 10.1.3.2.
ACR 401 Certifies JPN for SSSE.

Table 10 lists the enhancements and updates contained in version 7.8.2.6
ACR 190B Provides a parameter to allow the driver to selective turn on/off
the proxy connection, as well as a parameter to determine
whether proxy information should be cached and be used later
or not.
ACR 264 When users click the Find button to search for records, the
application returns incorrect records and then crashes.
ACR 275 Allows Siebel High Interactivity applications to be downloaded

when the user logs in when the application is configured for SSO
through Webseal/TAM version 5.1.
ACR 275A/B Allows the Siebel High Interactivity client to smoothly process
HTML responses.
ACR 302 Allows Enterprise Integration Manager to populate the CREATED

and LAST_UPD columns with UTC instead of with the server
timestamp.
ACR 346A/B Certifies Hummingbird SearchServer 6.0 on Siebel 7.8.2 for

Oracle 10g.


Feature Enhancement
ACR 190 Provides hosted CRM functionality with Enterprise applications running
on Windows.
ACR 269B Provides support for Lotus Notes 7 for Siebel Client Sync.
ACR 272 Provides the following Cancel Transaction Attributes functionality:
■ It allows the application to update the current numeric total to

reflect the current total lless the addition (or subtraction) of the
cancelled numeric attribute.
■ It allows the application to reject redemptions that go above the

member's available balance even if the member has canceled
accrual transactions in the past.
ACR 288 Supports multiple NQHOST parameters for Mobile and Enterprise
Analytics.
ACR 308 Allows bulk transfer of assets/inventory.
ACR 310 Resolves a problem where users are able to access data that should
not be visible to someone in their position.
ACR 323 Allows users to be able to access the Report Server screen using
Mozilla FireFox 1.5.0.1.
ACR 327 ACR 327: New module for Communications, Media, and Energy. The
module provides the ability to mass-generate orders for a group of
assets that are based on a set of common actions. Please note that this
is an optional module that requires additional licensing and installation
files. Please contact your client manager for details.
ACR 329 Allows EAI HTTP transport to support client authentication via a SSL
client certificate.
ACR 331 Backports Siebel Customer Order Management version 8.0 Catalog,
Asset, Pricer, and CFG broker Web Services to Siebel 7.8.2.5, and also
backports the core framework (Hierarchy and EAI IO to XML
Converter) to support the ability to subscribe to catalogs, customer
assets, and prices from an external application as a service.
ACR 335 Provides SNAC support for Microsoft SQL Server 2005.
ACR 365A Certifies RTD 2.2 with Siebel 7.8.2.5 for HP-UX.
ACR 365B Certifies RTD 2.2 with Siebel 7.8.2.5 for Windows.


ACR 252 Provides Retroactive Tier functionality so that points are

allocated based on the actual date of the transaction.
ACR 255 Provides the ability to create separate association records in the
intersection table for the same child table record, based on the
user key in the intersection table.
ACR 305 Ports Siebel Handheld 7.8.2, 7.7, and 7.5 to Windows Mobile 5
and certifies HP hx2790 and Dell X51.
ACR 320 Provides SSL Accelerator support for high-interactivity mode and
standard-interactivity mode clients.


ACR 186 Displays the search results in the corresponding Business

Component List Applet, and automatically closes the Search
Center if records are returned after a search is performed.
ACR 228B Provides SSL Support for JMS Transport (WebLogic).

ACR 262 Provides the ability to expose Product Promotions and associated
processes on the Web.
ACR 263 ACR 263 resolves the following issues with Territory
Management:
■ Allows users of Territory Management to create local

conditions by division.
■ Enables Territory Management to use Siebel’s standard

Oracle ODBC connection.
■ When activating multiple alignments for different territory

hierarchies, Assignment Manager writes the rule group ID
from the first hierarchy (for example, "H1") to records in
S_POSTN_CON, S_ACCNT_POSTN, or S_ASSET_POSTN that
correspond to active territory rules from all territory
hierarchies, not just H1. As a result, the next time the user
activates a new alignment for territories in H1, objects from
other hierarchies will also be affected by Assignment
Manager.
■ Provides users of Territory Management with the ability to
specify which territories should exchange position-specific
data.
■ Cursors are not closed on Oracle 9i when running and

activating alignments in Territory Management.
■ Data from load-balancing tables is not deleted after

alignments are run or activated.
■ Execution of Assignment Manager rule groups created by

Territory Management does not pass rule group ID as a
parameter, which leads to incorrect assignments.
■ From Territory # and From Territory Name are also displayed

on territory rules.

ACR 279 Supports the Hebrew (HEB ) code page for the Siebel Client Sync
product.
ACR 290 Allows the BAPI Wizard to use the UCLEN=01 argument for the
'DDIF_FIELDINFO_GET' call in SAP R/3 version 4.70 and higher.
ACR 307 Allows Visit Planning to use Role/Category to assign activities to

the proper merchandiser.
ACR 317 This feature corrects problems in high interactivity applications

that may have been observed where customers had installed a
recent Microsoft update that changed the way that ActiveX
controls are handled. For more information about this issue, see
Alert 1222 (Doc ID 473913.1) on OracleMetaLink 3

ACR 249 Improves the Data Quality Universal Connector to provide better
integration to third-party data quality solutions. The enhanced
Universal Connector is certified with FirstLogic IQ8 data
cleansing and matching technologies.

ACR 261 Adds a new Applet User Property called TriggerFindRecord.
ACR 273A Backports the Siebel Test Express Repository API feature.
This Test Automation enhancement also resolves the following

issues:
■ The contents in Query Assistant window (for PDQ) are not

recognized
■ The call to getContainerobject() method with SiebText as the

object should return a empty string
■ The Add Agent applet is missing under Admin-

Communications--Applets
■ Picklist Fields like "Select Field" and "Perfom Query Using"

are not recognized
■ Within Test Automation, Logging throws an exception in

setDataSource()

ACR 121 Certifies Microsoft Windows XP Tablet PC Edition 2005 for the
Siebel 7.8.2 High Interactivity client and Mobile Web Client.
Signature Capture using Tablet PC in the Siebel ePharma
application is only supported with the 7.8.2.1 Fix Pack or higher.
ACR 147 Given that SSL is configured for the Web server and Siebel Web
Server Extension, when the Web server attempts to find the
appropriate component to respond to a user request, the initial
message is now encrypted using SSL.
ACR 152 Allows a log file to be opened or copied if the client is running or
hung, and makes the format of the log entries similar to server
logs.
ACR 218 Provides the ability to exclude skipped categories/products from

aggregation.

ACR 239 Resolves an invalid hierarchical accounts problem created by the

Merge Record operation.
ACR 242 Enables Siebel Store-and-Forward Messaging to better support

high interactivity when it interacts with Siebel Handheld Sync
servers by using the Handheld Sync Server’s Load Balancing
functionality within Store-and-Forward Messaging calls to it.
ACR 243/244 ACR 243/244 provides the following enhancements:
■ Better support for using variables as parameters and the SQL

WHERE clause as a Search Specification to various TAGS
■ Fifteen new TAGS and six enhanced TAGS for formatting

flexibility
■ A printer dialog box for choosing printer options that allow

users to print multiple quantities of forms
■ Applet and List tags can now print data tables even when
there is no record
■ Enables users to invoke the Customer Authentication

Manager from the All Contacts Across Organizations view
when the users is not in the Contact team.
■ Enables the “Confirm Flag” value to passed as a process

property to the Customer Authentication Manager success
workflow.
ACR 246 Improves Siebel Store-and-Forward Messaging scalability and

allows Siebel Store-and-Forward Messaging to support multiple
IBM MQe queue managers.
Enhancements and Updates in Version 7.8.2

Release 7.8.2 contains several important features for Siebel Customer Order Management.

Table 16 lists the enhancements and updates added between version 7.8.1 and version 7.8.2.
Table 16. Enhancements and Updates in Version 7.8.2
Feature Description For More Information
Product Administration
Usability Enhancements ■ Provides a single place for See Siebel Product

creating and releasing new Administration Guide on the
products. Siebel Bookshelf.
■ Simplifies and reorganizes views

and navigation paths to reduce
the number of times that users
have to click.
Scenario Tester ■ Allows product administrators to See the section about
simulate product and pricing Scenario Tester in Siebel
information in development in Product Administration Guide
order to validate the information on the Siebel Bookshelf.
before it is introduced to
Production.
Attribute Eligibility
Support for Attaching Custom ■ Allows customers to attach See the section about
Eligibility Procedures to eligibility procedures attributes and the section
Attributes (workflows) to attributes. about eligibility in Siebel
Product Administration Guide
Each attribute can have its own
on the Siebel Bookshelf.
eligibility procedure or several
attributes can use the same
eligibility procedure.
Attribute value eligibility runs in

the context of the product
configuration process and
informs users which attribute
values are ineligible.

Ability to Write Aggregate ■ Allows administrators to write See the section about
Eligibility and Compatibility eligibility and compatibility rules eligibility in Siebel Product
Rules at the Product, Product Line, Administration Guide on the
and Product Class level, as well Siebel Bookshelf.
as to mix Product Line, Product,
and Product Class inside
compatibility rules.
For example, a compatibility

rule could say that Product Class
A excludes Product B or a rule
could say that Product Line C
requires Product Line E.
Improved Messaging in ■ Messages now point users to See the section about
Eligibility specific rules that are being eligibility in Siebel Product
violated and indicate the Administration Guide on the
product that is in violation, even Siebel Bookshelf.
if the violated rule is written
against product class or product
line.
Improved Eligibility and ■ Applet titles have been adjusted See the section about
Compatibility Administration to be specific to the rules for eligibility in Siebel Product
that applet, rather than being Administration Guide on the
generic across Eligibility and Siebel Bookshelf.
Compatibility applets.
■ All Eligibility and Compatibility

administration has been placed
under the Product
Administration screen.

Pricing Management
Enhanced Runtime UI ■ New pricing views for Quotes, See the section about the
Orders, and Agreements provide Discount Negotiation view in
a Discount Negotiation Siebel Order Management
framework for sales users. Guide on the Siebel
These views provide insight into Bookshelf.
price calculations, and expose
the logical progression from a
starting price to the final net
price, per corporate pricing
policies. Visibility into these
calculations allows sales users
to negotiate within corporate
guidelines and provide any
additional discounts necessary
to make sure that a deal is
closed.
Quote and Order Management
Quote and Order Verify ■ The Verify, Validate, and Verify See the section about
Enhancements Promotion buttons have been verifying quotes in Siebel
combined into one button called Order Management Guide on
“Verify” for the Quote, Order, the Siebel Bookshelf.
and Agreement headers.
■ The Verify Eligibility Status and

Validate buttons have been
combined into one button called
“Verify” for the Quote, Order,
and Agreement line item levels.
Siebel eSales
Enabled Dynamic Pricing and ■ The Catalog applies Dynamic See Siebel eSales
Eligibility and Compatibility Pricing and specialized filtering Administration Guide on the
Processes dependent on the value of the Siebel Bookshelf.
Eligibility and Compatibility
mode.
■ The Favorites and Shopping Cart

views apply Dynamic Pricing.

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Configuration Instructions
for Enhancements and Updates

Enhanced Catalog Product ■ “Start Price” and “Unit of See Siebel eSales
Detail, Favorite, and Shopping Measure” fields have been Administration Guide on the
Cart Views added to views. Siebel Bookshelf.
■ “Eligibility and Compatibility

Result” and “Eligibility and
Compatibility Explanation” fields
have been added to views.
Enhanced Saved Quote and ■ “Start Price” and “Unit of See the section about
Order Views Measure” fields have been creating quotes and orders in
added to views. Siebel Order Management
Guide on the Siebel
■ “Eligibility and Compatibility
Bookshelf.
Result” and “Eligibility and
Compatibility Explanation” fields
have been added to views.
Product Promotions for ■ The Catalog adds the contents See the section about
Catalog Product Detail and of the Product Promotion and its Promotions in Siebel Pricing
Shopping Cart Views associated commitments to the Administration Guide on the
Enhancements Shopping Cart. Siebel Bookshelf.
■ The Shopping Cart view

removes the Product Promotion
and its associated commitments
from the Shopping Cart.
Configuration Instructions for

Enhancements and Updates
This section contains instructions for some of the enhancements and updates provided in version
7.8.2 and 7.8.2.x releases and contains the following topics:
■ Instructions for ACR 228B
■ Configuration and Program Setup Instructions for ACR 252
■ Instructions for ACR 263

■ Instructions for ACR 346A
■ Instructions for ACR 373B
■ Instructions for Oracle BI Publisher Enhancements
■ Instructions for FR 12-1K0VS0T
■ Instructions for FR 12-1BJO1E5
■ Instructions for FR 12-1CY8FKI
■ Instructions for FR 12-1ERTG8V
■ Instructions for FR 12-1FWLGC6 and FR 12-1DS2LPX
■ Instructions for FR 12-1IAE2QU
■ Instructions for FR 12-1J5IVKH
Instructions for ACR 228B

The procedures in this section detail how to install and configure ACR 228B.
Installing Weblogic Application Server 8.1 SP6+

The following procedure explains how to install Weblogic Application Server 8.1.
To install BEA WebLogic Application Server 8.1 SP6+

1 Install BEA WebLogic 8.1 SP6+ binaries from http://bea.com.
2 Accept all default values for the installation except for JVM version. Only Sun Java JRE 1.4.x has
been certified.

3 Be certain to pair the WebLogic JVM and Siebel JVM minor versions the same. For example: 1.4.2-
04.
4 Set up the new server configuration for your BEA WebLogic Application Server.
While setting up, you will be prompted for a username and password.
Enter these values as system and resource, respectively.
5 Once this has been done, you should have new directories in your
<bea_install_dir>\user_projects\domains directory. You need to verify thatmydomain directory
is created. (Under this myserver, applications and other scripts should be present.)
6 Assuming that weblogic is installed under C:\bea, for starting web logic, open a command
window, go to C:\bea\user_projects\domains\mydomain, and execute StartWebLogic. Once web
logic server is up, it shows "RUNNING MODE".
7 Once web logic is in RUNNING MODE, you can open the Admin console. To do that, open the
Internet explore window, use the following URL: http://localhost:7001/console. To log in, use
system/resource as the username/password.
8 If you are able to perform all the above tasks, your WebLogic set up is complete.
NOTE: You have to execute stopWeblogic.cmd for stopping the WebLogic server. This batch file
is located under C:\bea\user_projects\domains\mydomain.
Generating the Self-Signed Certificate and Uploading It in the Java-

Provided Custom Store
The following procedure explains how to generate the Self-Signed Certificate and upload it.
To generate the Self-Signed Certificate

1 Generate a Server Key and Certificate:
keytool -genkey -alias RitKey -dname "CN=<hostname/machine_name>

OU=ComputerEngineering, O=RitCorp, L=Dublin, S=Dublin, C=IE" -keyalg RSA -keypass
changeit -storepass changeit -keystore Rit.jks
2 Export the Server Certificate:
keytool -export -alias servercert -storepass changeit -file Rit_server.cer -keystore Rit.jks
3 Import the Certificate to the Java-provided custom store:
keytool -import -keystore C:\j2sdk1.4.2_08\jre\lib\security\cacerts -alias servercert -file

D:\bea\user_projects\domains\mydomain\Rit_server.cer
WebLogic SSL Configuration

The identity keystore contains the certificates and keys related to the server's identity. This is
generally the certificate information that your server will share with clients.

The trust keystore is used whenever the server will accept or make two-way SSL calls-that is, when
both the server and client present certificates. In most cases, Web applications use one-way SSL;
the server presents a certificate, and the browser chooses to accept or reject the certificate. In two-
way SSL, the server presents its certificate and asks the client to present a certificate as well. When
the server receives the client's certificate, it uses the trust keystore to determine whether to trust
the issuer of the client certificate.
Configuring WebLogic
Use the following procedure to configure WebLogic.
To configure WebLogic
1 Start by going to the WebLogic console. If you accept the default settings when you install your
domain (the place where you'll run servers and deploy code), the admin port is 7001. For
example, my admin server is found here: http://localhost:7001/console
2 In the left pane, click the plus (+) next to the Servers link to display a list of all the servers
available in the domain. This example uses the admin server, usually named myserver in a
default configuration.
3 Click your admin server to display its configuration in the right pane. On the Configuration tab,
click the Keystores & SSL tab.
CAUTION: Warning: By default, WebLogic ships with demo certificates for testing purposes.
However, you should not use these certificates should not be used for a production site. One
reason is because every WebLogic installation has a set of these certificates. Although each set
is different, which minimizes the risk of someone getting a copy of your private key, the
certificates are not issued by a commercial certificate authority. This can present two problems:
Almost no browsers will trust your certificates, and these certificates come with no assurances.
Therefore, it is recommended that you use a commercial certificate authority rather than demo
certificates.
4 Click on the Change hyperlink to configure for the new certificate.
This example specifies a custom-made keystore for the configuration. Click the Change link in
the upper-right portion of the configuration items. Figure 4 shows the resulting drop-down list of
options for configuration:
■ Demo Identity and Demo Trust. These are the certificates that were mentioned previously.
The Demo Trust contains the root certificate for the demo certificate authority. By default, if
you are using Node Manager, the demo certificates are used.
■ Custom Identity and Java Standard Trust. The custom identity is a keystore that you create.
The Java Standard Trust refers to the trusted keystore included in most JDKs. In the Sun JDK
and BEA's JRockit JVM, you can find a file called cacerts in jre/lib/security directory. The
password to this keystore is changeit.

■ Custom Identity and Custom Trust. This is the same identity configuration as above, but with
this option you also provide a custom trust. If your server is engaging in two-way SSL calls
as a client or a server, the custom trust is how your server will determine whether it should
trust the certificate that the peer presents. If you are accepting client certificates, it is a good
idea to build your own trust. This limits the certificates that can be presented to ones that
are issued by the certificate authorities of your choice. The cacerts file has approximately 30
root certificates. If you are only trying to establish one-way SSL, you needn't worry about
this option or the next.
■ Custom Identity and Command Line Trust. This is the same identity as was previously
discussed, but this time the trust will be supplied on the command line. This option can be
useful if you will switch trusts often and do not want to continually use the console or edit
the config.xml file.
5 Choose Custom Identity and Java Standard Trust from the list.
6 Specify your identity keystore information.
Within this document, Custom Identity and Java Standard Trust will be used.
The Keystore Type entry refers to the provider of the keystore structure. If you did not create
the keystore yourself, ask the provider what the type is. In most cases, it will be JKS, which is
Sun's implementation. Then, enter the password for the keystore. (Do not confuse this with your
private key password, which will be entered later.)
7 Enter the Java Standard Trust password. Unless you or your system administrator changed it,
the password will be changeit. Click Continue.
8 On the following screen, enter the private key alias. This is the unique identifier in the keystore
for your private key.
Remember that the password for the private key may differ from the one for the keystore. One
keystore can contain more than one key, so keystore may not be your alias.
Enabling the SSL Port

The following procedure describes how to enable the SSL port.
To enable the SSL port

1 Expand the Server node.
2 Select the General tab.
3 Check the SSL Port Enabled option.
4 Click Apply to save your changes.
5 Reboot WebLogic Server.
Testing Configuration
The following procedure describes how to test the configuration.

To test configuration
1 Stop your server and edit your startWeblogic.cmd or startWebLogic.sh file. You need to change
the logging level of the server, enable debugging to the standard output, and set the logging level
to Info. These actions can be performed through the console, but there is a specific SSL
debugging flag that can only be set through the script, so it may be best to modify the start script
for the other settings through the console as well.
2 Open your script and make the following changes:
Set JAVA_OPTIONS=-Dweblogic.StdoutSeverityLevel=64 -Dweblogic.StdoutDebugEnabled=true

-Dssl.debug=true
3 After you have made these changes, restart the server. If the flags have been added correctly,
the server begins producing a lot of output. To confirm that the flags have been accepted, check
the text at the beginning of the output at startup for the following:
***************************************************
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\[hostname]:[port]\console *
***************************************************
<Mar 6, 2005 12:45:41 PM MST> <Info> <WebLogicServer> <BEA-000377> <Starting

WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04
from Sun Microsystems Inc.>
<Mar 6, 2005 12:45:41 PM MST> <Debug> <TLS> <000000> <Enabled muxing IO for SSL in
server>
<Mar 6, 2005 12:45:41 PM MST> <Info> <Configuration
How can you tell if your keystore is loaded? Look for the following in the debugging
output:
<Mar 6, 2005 1:23:02 PM MST> <Debug> <TLS> <000000> <SSLManager: getting server
private key>
<Mar 6, 2005 1:23:02 PM MST> <Notice> <Security> <BEA-090170> <Loading the private
key stored under the alias servercert from the jks keystore fi
le D:\MyData\solutions\my_keystores\verisign-example\verisign-keystore.jks.>
<Mar 6, 2005 1:23:02 PM MST> <Debug> <TLS> <000000>

<SSLManager.getServerCertificate()>
<Mar 6, 2005 1:23:02 PM MST> <Notice> <Security> <BEA-090171> <Loading the identity
certificate stored under the alias servercert from the jks keystore file
D:\MyData\solutions\my_keystores\verisign-example\verisign-keystore.jks.>

<Mar 6, 2005 1:23:02 PM MST> <Notice> <WebLogicServer> <BEA-000298> <Certificate

expires in 14 days: [
Additionally, the end of the output will contain more information about whether the configuration
changes were successful:
<Mar 6, 2005 1:23:08 PM MST> <Info> <WebLogicServer> <BEA-000300> <Certificate

contents: 2 certificate(s):
fingerprint = c597c372b1ebe10124382d5f32a40239, not before = Sat Mar 05 17:00:00

MST 2005, not after = Sun Mar 20 16:59:59 MST 2005, holder = C
=US SP=Colorado L=Denver O=BEA Systems Inc OU=Support CN=jsvede , issuer =

O=VeriSign, Inc OU=For VeriSign authorized testing only. No assurances
(C)VS1997 , key = modulus length=129, exponent length=3
fingerprint = 40065311fdb33e880a6f7dd14e229187, not before = Sat Jun 06 18:00:00

MDT 1998, not after = Tue Jun 06 17:59:59 MDT 2006, holder = O
=VeriSign, Inc OU=For VeriSign authorized testing only. No assurances (C)VS1997 ,

issuer = O=VeriSign, Inc OU=For VeriSign authorized testing onl
y. No assurances (C)VS1997 , key = modulus length=65, exponent length=3
>
...
<Mar 6, 2005 1:23:08 PM MST> <Notice> <WebLogicServer> <BEA-000360> <Server started

in RUNNING mode>
<Mar 6, 2005 1:23:08 PM MST> <Notice> <WebLogicServer> <BEA-000355> <Thread

"SSLListenThread.Default" listening on port 7002, ip address *.*>
4 Try to access your server over the SSL port. The easiest way to test this is to access the console
over the secure port: http://localhost:7002/console.
Configuring Siebel Server

The following procedure describes how to configure Siebel Server.
To configure Siebel Server

1 Start NameServer.
2 Start server manager (without starting Siebel server) srvrmgr /g localhost /e siebel /s
<hostname> (sdchs20N172) /u <username> /p <password> /s <hostname>
3 Start EAI Compgrp.

4 Enable compgroup EAI.
SSL Class Path Dependencies:
{BEA.HOME}weblogic.jar
webserviceclient+ssl.jar
jsafeFIPS.jar
license.bea
Siebel Class Path Dependencies:
Siebel.jar
SiebelJI_xxx.jar
jndi.properties
5 Create JVM Name Subsystem, using the following command examples:
Create named subsystem JAVA for subsystem JVMSubSys with

DLL=C:\bea\JDK142_04\jre\bin\server\jvm.dll,CLASSPATH=".;D:\JMS;C:\bea;C:\bea\weblogic
81\server\lib\weblogic.jar;c:\JMS\Siebel.jar;c:\JMS\SiebeJI_xxx.jar;
c:\JMS\webserviceclient+ssl.jar;c:\JMS\jsafeFIPS.jar", VMOPTIONS='-Xusealtsigs -
Dweblogic.security.TrustKeyStore=CustomTrust -
Dweblogic.security.CustomTrustKeyStoreFileName=c:\JMS\Cert.jks -
Dweblogic.security.CustomTrustKeyStorePassPhrase=changeit -Djms.log=C:\JMS\jms.log'
Java SubSystem Notes
■ DLL: Points to the location in which JVM is installed.
■ D:\JMS: This directory should contain jndi.properties and JavaKeyStore files.
■ C:\BEA: Should contain the license.bea file.

6 Restart the Siebel Server.
Testing WebLogic JMS Server with SSL Encryption

Use the following procedure to test WebLogic JMS Server.
To test WebLogic JMS Server

1 Open an Internet Explorer session on the same window, and go to "http://localhost:7001/
console. This launches the WebLogic Administrator Login page. Log in using the username and
password that you created earlier.
2 Go to mydomain -> Services -> JMS -> Connection Factories, and click on the "Configure a new
JMS Connection Factory" link on the right panel. You can also directly click the JMS connection
factory link in the Service Configurations section in the right panel.
3 Type "<Connection_Factory_name>" in the "JNDI Name" field, and keep the default values in all
other fields. Click "Create".

4 In "Target and Deploy" tab, check "myserver" and click the "Apply" button.
5 Go to mydomain -> Services -> JMS -> Stores, and click on "Configure a new JMS File Store" link.
6 Type "D:\JMSFile" in the directory field. Create this directory if it is not there yet, and then click
"Create" button, and then click the "Apply" button.
7 Repeat Step 5 and Step 6 to create another File Store, and give D:\JMSPage as the directory.
8 Go to mydomain -> Services -> JMS -> Servers, and click on "Configure a new JMS Server".
9 In the "Persistent Store", pick "MyJMS File Store", in the "Paging Store", pick "MyJMS File Store-
1", and then click the "Create" button.
10 In the "Target and Deploy" tab, click "Apply".

11 Go to mydomain -> Services -> JMS -> Servers -> MyJMS Server -> Destinations, and click on
"Configure a new JMS Queue".
12 Type "<Send_Queue_Name>" in the "JNDI Name" field, click the "Create" button, and then click
the "Apply" button.
13 Create a file using Notepad, put the following two lines in the file, and save it as "jndi.properties"
file under a testing directory (e.g. D:\JMS ):
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3s://<server_name>:7002
14 Start a Siebel application such as Call Center) and go to the business service simulator.
15 Click the New button, and specify the name of business service as "EAI JMS Transport", and the
Method name as "CheckAll".
16 Go to the child form and click New Record. Specify the parameter as
ConnectionFactoryName,ConnectionPassword, ConnectionUsername,SendQueue and so forth.
The Java Browse Queue, a JNDI browser, can be very helpful in debugging JMS Connectivity
issues.
Configuration and Program Setup Instructions for ACR

252
Use the instructions in the following section to set up and configure ACR 252.
Configuration Setup
The following files are necessary for implementing ACR 252:
■ ACR_252_High_Miles_Changes.xls
■ ACR_252_Repository_Changes.xls
■ ACR_252_schema.xls
To access these documents, contact Oracle Customer Care.

Schema Setup
1 In Siebel Tools, navigate to Object Explorer.
2 Click Table, and lock the "Table Loyalty" project.
3 Import schema.sif, or save it to disk.
LOV Setup
1 In Siebel Tools, navigate to Screen > System Administration > List of Values.
2 Enter the LOVs listed for Member Tier Status, Member Tier Level Attributes, Transaction
Attributes and Criteria as specified in the LOVs worksheet in Repository Changes.xls.
NOTE: Not all of the LOVs have the same language-independent value as the language-
dependent value. These values should be entered as-is according to the spreadsheet. You do not
need to enter the LOVs if they are already present.
Business Component Setup

2 Click on Business Component, and query for each Business Component specified in the BC Fields
worksheet within Repository Changes.xls.
3 For each Business Component, check to see if the Business Component already exists. If it does
not, you will need to create it.
4 Click on the Join item of the Business Component. If the Join and Join Specification already exist,
modify them. If they do not already exist, add new Join and Join Specifications for the Business
Component.
5 Click on the Field item of the Business Component, and modify the existing fields. If the fields
do not exist, add new fields. Add a Pick Map for the field, if one is required.
6 Click on the Business Component User Property item of the Business Component. If the item
already exists, modify it. If it does not already exist, add a new Business Component User
Property using the information listed in the BC User Props worksheet within Repository
Changes.xls.
Business Service Setup

1 In Siebel Tools, navigate to Object Explorer, and click on Business Service.
2 Query for each Business Service specified in the Business Service worksheet within Repository
Changes.xls.
3 Click on the Business Service Method item of the Business Service. If the item already exists,
modify it. If it does not already exist, add new Business Service Method and Business Service
Method Arguments listed in the Business Service worksheet within Repository Changes.xls.

4 Click on the Business Service User Prop item of the Business Component. If it already exists,
modify it. If it does not already exist, add the new Business Service Method and Business Service
Method Arguments listed in the Service User Props worksheet within Repository Changes.xls.
Link Setup
2 Click Link, and query for the Link specified in the Links worksheet within Repository Changes.xls.
If the Link already exists, modify it. If it does not already exist, add the new Links listed in the
Links worksheet within Repository Changes.xls.
Business Object Setup

1 In Siebel Tools, navigate to Object Explorer, and click Business Object.
2 Query for the Business Object specified in the BO Changes worksheet within Repository
Changes.xls.
3 Click on the Business Object Component item of Business Object. If the item already exists,
modify it. If it does not already exist, add a new Business Object Component for the Business
Object listed in the BO Changes worksheet within Repository Changes.xls.
4 Click on the Business Service User Prop item of the Business Component. If the item already
exists, modify it. If it does not already exist, add the new Business Service Method and Business
Service Method Arguments listed in the Service User Props worksheet within Repository
Changes.xls.
Symbolic String Setup

2 Click on Symbolic Strings, and add the new Symbolic Strings specified in the Symbolic Strings
Applet Setup
2 Click on Applet, and query for the Applets specified in the Applet Changes worksheet within
Repository Changes.xls.
3 Click on the List Column item of the Applet, and modify the item if it exists. If it does not already
exist, add a new List Column for the Applet listed in the Applet Changes worksheet within
Repository Changes.xls and add it to any available column in the Web template.
4 Click on Applet toggle item of the Applet, and modify the item if it exists. If it does not already
exist, add the new Applet toggle listed in the Applet Changes worksheet within Repository
Changes.xls.

Program Setup
Refer to the High Miles Changes.xls document for instructions about setting up Program
configuration. These are the suggested program changes to illustrate how this feature should be set
up. However, the actual implementation may vary.
LOV Setup
1 Within Siebel Loyalty, navigate to Site Map > Administration Data > List of Values.
2 Verify that all the LOVs are listed for Member Tier Status, Member Tier Level Attributes,
Transaction Attributes, and Criteria.
Program Level Attributes Setup

1 Within Siebel Loyalty, navigate to Loyalty Program Administration, and query for High Miles
Program.
2 Drill down on Program Id.
3 Navigate to the Go To Program Level Attributes view, and then to the LOY Program Member
Attributes view.
4 Click the New button to add the Member Attributes listed in the Program Level Attributes work
sheet within High Miles Changes.xls.
5 Navigate to Member Tier Attributes 3LN, and click the New button to add the Member Tier
Attributes listed in the Program Level Attributes worksheet within High Miles Changes.xls.
6 Navigate to Transaction Attributes 3LN, and click the New button to add the Transaction
Tier Rule Setup

1 Within Siebel Loyalty, navigate to Loyalty Program Administration and query for the High Miles
program.
2 Drill down on Program Id, click on the Tier Class tab, and navigate to the LOY Program Tier Admin
view.
3 Select HM Tier Class 2 and navigate to the LOY Tier List Applet - Admin bottom applet.
4 Drill down on each Tier Id, which will take you to the LOY Promotion Rules View - Admin view.
5 Click the Modify button and add the related Rules, Action and Criteria specified in the Tier Rule
worksheet within High Miles Changes.xls.
6 Click the Activate button to activate the modified promotion.

7 Repeat the same steps for HM Tier Class 1 and related tiers.

Admin - Retro Accruals Setup

1 Within Siebel Loyalty, navigate to Loyalty Program Administration, and query for the High Miles
program.
2 Drill down on Program Id, click on the Promotion tab and navigate to the LOY Program Tier Admin
view.
3 Select Admin - Accruals Promotion and copy the record.
4 Rename Promotion Name to Admin - Retro Accruals.
5 Add related Rules, Action and Criteria specified in the Admin - Retro Accruals worksheet within
High Miles Changes.xls.
6 Click the Activate button to activate the promotion.
Admin - Cancellation Setup

program.
2 Drill down on Program Id, click the Promotion tab, and navigate to the LOY Program Tier Admin
view.
3 Drill down on Promotion# of Admin - Cancellation Promotion.
4 Rename Promotion Name to Admin - Retro Accruals
5 Click the Modify button and add the related Rules, Action and Criteria specified in the Admin -
Cancellation worksheet within High Miles Changes.xls.
Instructions for ACR 263

The configurations for ACR 263 include both mandatory and optional steps. You can use this
document to implement the changes manually, or you can use the zip file package included on the
build DVD. The build DVD contains the following files:
■ Client DB.sif: SIF for Workflow Policy changes. Importing this file is optional.
■ Repository.sif: SIF that includes all repository changes. Importing this file is optional, but note
that if you use the configuration instructions document to implement the repository changes, and
then import Repository.sif, importing the file will overwrite any configurations that you have
made to the repository changes.
■ Workflows.zip: This file contains an export of the workflows associated with ACR 263. Importing
this file is optional.
■ Tables.sif: Although importing the preceding files is optional, you must import this SIF. Itis
necessary to keep the schema in sync with future Siebel releases.

Tools.cfg
Change a parameter in tools.cfg (Original: SymStrPrefix = X_) to SymStrPrefix = SBL_
Master Database Configuration
Applets
To implement ACR 263, you must make changes to the applets listed in the following section.
■ Alignment List Applet
■ Alignment Form Applet
Business Component: Alignment
User Properties for

the Alignment
Business
Component
New or Changed
Name Value Name Value
New Validate Alignment Type Y
New Error String: This aligment has position rules.

Please remove these rules from the
IDS_TM_MINOR_WITH_POSITION_
alignment before changing the
RULES
alignment type to Minor.
New Error String: This alignment has position rules.

Minor alignments are run against
IDS_TM_RUN_MINOR_WITH_PSTN
active position rules. If you
_RULES
continue, the position rules in the
alignment will be deleted.
New Error String: This alignment has position rules.

Minor alignments are run against
IDS_TM_ACTIVATE_MINOR_WITH_
active position rules. If you
PSTN_RULES
continue, the position rules in the
alignment will be deleted.
■ Alignment Condition List Applet
■ Class: CSSFrameList
■ Business Component: Alignment Condition

■ Update the existing applet by adding a new List Column. You also need to add this new List
Column item to the Applet Web Template, as shown in the following table.
List Column
Pick
Name Field Applet String Reference
Division Name Condition Internal SBL_DIVISION-1004225615-010

Division Name Division
Pick
Applet
■ Alignment Account Mapping List Applet
■ Class: CSSSWEFrameList
■ Business Component: Alignment Territory Account Mapping
Update the existing applet by adding the new List Columns as shown in the following table. You
must also add these new List Column items to the Applet Web Template and set the "Runtime"
property for List Column "From Territory Identifier" to TRUE.
List Column
Pick
From Territory From Territory Territory SBL_TM_FROM_TERRITORY_#_HOR

Identifier Identifier Pick
Applet
From Territory From Territory SBL_TM_FROM_TERRITORY_HOR

Name Name
■ Alignment Contact Mapping List Applet

■ Business Component: Alignment Territory Contact Mapping
Update the existing applet by adding new List Columns as shown below. Also need to add these
new List Column items to the Applet Web Template and set the "Runtime" property for List
Column "From Territory Identifier" to TRUE.
List Column
Pick

Applet

Name Name
■ Alignment Geo Zone Mapping List Applet
■ Business Component: Alignment Territory Geo Zone Mapping
List Column
Pick

Applet

Name Name
■ Alignment Postal Code Mapping List Applet

■ Business Component: Alignment Territory Postal Code Mapping
List Column
Pick

Applet

Name Name
■ Assignment Attribute
Assignment
Attribute
Use
Name Data Type Range
Division Varchar N
List Column
■ Assignment Criteria
Assignment
Criteria
Display
Name Name Team
Division Division Y
Assignment
Criteria Attribute
Assignment Display Display

Name Attribute Name Store Column Sequence
Division Division Division 1 1
Business Component
■ Alignment

■ Class: CSSBCAlignment

■ Table: S_TERRALGN
Add four new fields and update the Link Specification for the 'Division Id' field, as shown in the
following table:
Fields
Link
Name Join Column Type Specification
Locked By LOCKED_BY_ DTYPE_ID

USER_ID
Locked By User Locked By LOGIN DTYPE_TEXT
Locked Date LOCKED_DT DTYPE_UTCDATETIME

Locked Flag LOCKED_FLG DTYPE_BOOL
Division Id DIVISION_ID Y
Add two new calculated fields, Read Only Assignment Position and Is Read Only 3, and modify
existing calculated fields, as shown in the following tables:
Fields
Name Calculated Value Calculated? New?
Read Only IIF([Read Only Alignment] = "Y" OR [Type] = Y Y

Alignment LookupValue("ALIGNMENT_Type", "Minor"), "Y",
Position "N")
Enable Flag for NOT [Is Read Only 3] Y N

Activate
Enable Flag for NOT [Is Read Only] AND [Status] <> Y N
Run Alignment LookupValue("ALIGNMENT_STATUS",
"Alignment Activation Failed")
Enable Flag for IIF([Status] = Y N
Undo Activation LookupValue("ALIGNMENT_STATUS",
"Scheduled") OR [Status] =
LookupValue("ALIGNMENT_STATUS",
"Activation Tasks Not Started") OR [Status] =
"Alignment Activation Failed"), "Y", "N")
Is Read Only IIF([Is Read Only 1] = "N" OR [Is Read Only 2] Y N

= "N" OR [Is Read Only 3] = "N", "N", "Y")

Fields
Name Calculated Value Calculated? New?

Is Read Only 1 IIF([Status] = Y N
LookupValue("ALIGNMENT_STATUS", "In
Progress") OR [Status] =
"Imported") , "N", "Y")
Is Read Only 2 IIF([Status] = Y N

"Alignment Run Failed") OR [Status] =
LookupValue("ALIGNMENT_STATUS", "Run
Tasks Not Started") OR [Status] =
Tasks Failed"), "N", "Y")
Is Read Only 3 IIF([Status] = Y Y

Completed") OR [Status] =
Tasks Unknown") OR [Status] =
"Alignment Activation Failed"), "N", "Y")

Join
Outer
Table3 Alias Join
S_USER Locked By Y
Join
Specification
Destination Source
Name Column Field
LOGIN PAR_ROW_ID Locked By
Change the Named Method 3 User Property and add eight new User Properties, as shown in the
following table:
User Properties
New Name Value
N Named "Undo Activation", "INVOKESVC",

Method 3 "Alignment", "Alignment Management
Service", "Undo Activation", "'Alignment
Id'", "[Id]", "'Request Id'", "[Activation
Server Request Id]", "'Roll Back Status'",
"LookupValue('ALIGNMENT_STATUS', 'Run
Completed')"
Y Direct "TM Account", "Alignment Territory Position

Territory Account Mapping"
Rules 4
Y Direct "TM Contact", "Alignment Territory Position
Territory Contact Mapping"
Rules 5
Y Direct "TM Asset", "Alignment Territory Position
Territory Asset Mapping"
Rules 6
Y Indirect "TM Account", "Alignment Territory Position

Territory Postal Code Mapping", "Account Flag,Zip"
Rules 6

User Properties
New Name Value
Y Indirect "TM Contact", "Alignment Territory Position

Territory Postal Code Mapping", "Contact Flag,Zip"
Rules 7
Y Indirect "TM Asset", "Alignment Territory Position
Territory Postal Code Mapping", "Asset Flag,Zip"
Rules 8
Y Indirect "TM Account", "Alignment Territory Position
Territory Geo Zone Mapping", "Account Flag,Geo
Rules 9 Zone"
Y Indirect "TM Contact", "Alignment Territory Position

Territory Geo Zone Mapping", "Contact Flag,Geo
Rules 10 Zone"
■ Alignment Condition
■ Class: CSSLSBCAlignCondition

■ Table: S_TERRALGN_COND
Update the existing Business Component by adding new joins, new Fields and Business
Component User Properties, as shown in the following tables:
Join
Alias Table Outer
S_ORG_EXT S_ORG_EXT Y
Join
Specification
Destination Source
Name Column Field
Condition Division ROW_ID Condition

Id Division
Id
Fields
Name Column Join Pick List Calculated Value
Alignment Division ParentFieldValue("D

Id ivision Id")
Condition Division DIVISION_ID

Id
Condition Division NAME S_ORG_E PickList Internal

Name XT Division
Is Read Only IIF(([Condition

Others Division Id] IS NOT
NULL), "Y", "N")
Is Read Only IIF(([Territory Id]

Division IS NOT NULL) OR
([Region Id] IS NOT
NULL) OR ([Zip] IS
NOT NULL) OR
([Alignment
Division Id] IS NOT
NULL), "Y", "N")

Fields Pick Map
Picklist
Name Field Field Constrain
Condition Division Condition Id

Name Division Id
Condition Name
Division Name
Alignment Territory Y
Hierarchy Id Hierarchy
Id
User Properties
New or
Changed? Name Value
New Field Read Only Field: Is Read Only Division

Condition Division Name
New Field Read Only Field: Is Read Only Others

Territory Identifier
New Field Read Only Field: Zip Is Read Only Others
New Field Read Only Field: Region Is Read Only Others
Changed Conditions Sort Spec 6 "Condition Division Id","Sequence",""
New Conditions Sort Spec 7 "Sequence", "", ""
Changed Convert Conditions "[Condition Division Id] Is NOT NULL"

SearchSpec6
New Convert Conditions "[Territory Id] Is NULL and [Zip] Is NULL

SearcSpec7 and [Region Id] Is NULL and [Condition
Division Id] Is NULL"
New Person Candidate Source "Zip", "Geo Zone"

Names 7
■ Alignment Territory Account Mapping

■ Class: CSSBCAlgnComponent

■ Table: S_TERRALGN_ACCT
Update the existing Business Component with the following changes:
Fields
From FROM_TERR_ID
Territory Id
From NAME From Territory Picklist TM

Territory Territory
Identifier
From DISPLAY_NAME From Territory
Territory
Name
Territory DIVISION_ID S_TERRITORY

Division Id
Disable From IIF ([Territory Id] IS NULL,

Territory Field "Y", "N")
Fields Pick Map
Picklist
Territory Identifier Territory Division

Division Id Id
From Territory From Territory Id

Identifier Id
From Territory Territory

Identifier Identifier
From Territory Display

Name Name
Territory Division Y
Division Id Id
Join Join Specification
Destination
Alias Table Outer Name Column Source Field
From S_TERRITORY Y From Territory ROW_ID From Territory Id

Territory

User Properties
New or
Changed? Name Value
New Field Read Only Field: Disable From Territory Field

From Territory
Identifier
New On Field Update Set "Territory Identifier", "From Territory

Identifier", ""
■ Alignment Territory Contact Mapping


■ Table: S_TERRALGN_CON
Fields
From FROM_TERR_ID
Territory Id
From NAME From Territory Picklist TM

Territory Territory
Identifier
From DISPLAY_NAME From Territory
Territory
Name
Territory DIVISION_ID S_TERRITORY

Division Id
Disable From IIF ([Territory Id] IS NULL,

Territory Field "Y", "N")
Fields Pick Map
Picklist

Division Id Id

Identifier Id


Name Name
Division Id Id
Destination
From S_TERRITORY Y From Territory ROW_ID From Territory

Territory Id

User Properties
New or
Changed? Name Value
New Field Read Disable From Territory

Only Field:
From Territory
Identifier
New On Field "Territory Identifier", "From Territory

Update Set Identifier", ""
■ Alignment Territory GeoZone Mapping

■ Table: S_TERRALGN_REGN
Fields
From Territory Id FROM_TERR_ID
From Territory NAME From Territory Picklist

Identifier TM
Territory
From Territory DISPLAY_NAME From Territory

Name
Territory Division DIVISION_ID S_TERRITORY

Id
Disable From IIF ([Territory Id] IS

Territory Field NULL, "Y", "N")
Field Pick Map
Picklist

Division Id Id

Identifier Id


Name Name
Division Id Id
Destination
From S_TERRITORY Y From Territory ROW_ID From Territory

Territory Id

User Properties
New or
Changed? Name Value
New Field Read Only Field: From Disable From Territory Field

Identifier", ""
■ Alignment Territory Postal Code Mapping
■ Table: S_TERRALGN_ZIP
Fields
Pick
Name Column Join List Calculated Value
From FROM_TERR_ID
Territory Id
From NAME From Picklist

Territory Territory TM
Identifier Territory
From DISPLAY_NAME From

Territory Territory
Name
Territory DIVISION_ID S_TERRIT
Division Id ORY
Disable From IIF ([Territory Id] IS NULL, "Y",

Territory Field "N")
Fields Pick Map
Picklist

Division Id Id

Identifier Id


Fields Pick Map
Picklist
Name Name
Division Id Id
Destination Source
Alias Table Outer Name Column Field
From S_TERRITORY Y From Territory ROW_ID From

Territory Territory Id
User Properties
New or
Changed? Name Value
New Field Read Only Field: From Disable From Territory Field

Identifier", ""
■ Alignment Territory Position Mapping
■ Table: S_TERRALGN_PSTN
Change an existing Business Component User Property.
User Properties
New or
Changed? Name Value
Changed Parent Read Only Field Alignment Read Only Alignment Position
■ TOS Target Territory Geo Zone Account

■ Class: CSSBCBase

■ Table: S_PARTY
Modify the Join Specification for the S_TERR_REGION join, as shown in the following table:
Destination Source
S_TERR_R S_TERR_REGI N Region Id REGION_ID Region Id

EGION ON
Alignment Territory Position Account Mapping (New)
Class: CSSBCBase
Table: S_TERRALGN_PSTN
Search Specification: [Rule Effective Start Date] <= [Alignment Activation Date] AND ([Rule
Effective End Date] > [Alignment Activation Date] OR [Rule Effective End Date] IS NULL)
Fields
Name Column Join
Alignment Activation Date ACTIVATION_DT S_TERRALGN
Rule Effective End Date EFF_END_DT S_TERR_ACCNT
Rule Effective Start Date EFF_START_DT S_TERR_ACCNT
Territory Alignment Id TERR_ALGN_ID
Territory Id TERR_ID
Destination Source
S_TERRAL S_TERRALGN N S_TERRALGN ROW_ID Territory

GN Alignment
Id
S_TERR_A S_TERR_ACC N S_TERR_ACCNT TERR_ID Territory Id

CCNT NT
Alignment Territory Position Asset Mapping (New)
Class: CSSBCBase

Search Specification: Search Specification: [Rule Effective Start Date] <= [Alignment Activation
Date] AND ([Rule Effective End Date] > [Alignment Activation Date] OR [Rule Effective End Date] IS
NULL)
Fields
Name Column Join
Rule Effective End Date EFF_END_DT S_TERR_ASSET
Rule Effective Start Date EFF_START_DT S_TERR_ASSET
Destination Source

GN Alignment
Id
S_TERR_A S_TERR_ASS N S_TERR_ASSET TERR_ID Territory Id

SSET ET
Alignment Territory Position Contact Mapping (New)
Class: CSSBCBase
NULL)
Fields
Name Column Join
Rule Effective End Date EFF_END_DT S_TERR_CON
Rule Effective Start Date EFF_START_DT S_TERR_CON

Fields
Name Column Join

Destination Source

GN Alignment
Id
S_TERR_C S_TERR_CON N S_TERR_CON TERR_ID Territory Id

ON
Alignment Territory Position Geo Zone Mapping (New)
Class: CSSBCBase
Table: STERRALGN_PSTN
NULL)
Fields
Name Column Join
Account Flag ACTIVATION_DT S_TERR_REGION
Asset Flag ACTIVATION_DT S_TERR_REGION
Contact Flag ACTIVATION_DT S_TERR_REGION
Rule Effective End Date EFF_END_DT S_TERR_REGION
Rule Effective Start Date EFF_START_DT S_TERR_REGION

Destination Source

GN Alignment
Id
S_TERR_R S_TERR_REGI N S_TERR_REGION TERR_ID Territory Id

EGION ON
Alignment Territory Position Postal Code Mapping (New)
Class: CSSBCBase
Search Specification:Search Specification: [Rule Effective Start Date] <= [Alignment Activation
NULL)
Fields
Name Column Join
Account Flag ACTIVATION_DT S_TERR_ZIP
Asset Flag ACTIVATION_DT S_TERR_ZIP
Contact Flag ACTIVATION_DT S_TERR_ZIP
Rule Effective End Date EFF_END_DT S_TERR_ZIP

Rule Effective Start Date EFF_START_DT S_TERR_ZIP

Destination Source

GN Alignment
Id
S_TERR_ZI S_TERR_ZIP N S_TERR_ZIP TERR_ID Territory Id

P
Business Objects
Alignment
Add the following new Business Components to the Business Object:
■ Alignment Territory Position Account Mapping
■ Alignment Territory Position Asset Mapping
■ Alignment Territory Position Contact Mapping
■ Alignment Territory Position Geo Zone Mapping
■ Alignment Territory Position Postal Code Mapping
Business Service
Alignment Management Service
Class: CSSAlignmentMgmtSvc

Add the new User Properties listed in the following table:
User Properties
Name Value
Data Cleanup SQL TM_DELETE_LOAD_SPLITTER
Activation Data Cleanup SQL 1 TM_ACTIVATION_UPDATE_TERR_ACCNT
Activation Data Cleanup SQL 2 TM_ACTIVATION_UPDATE_TERR_CON
Activation Data Cleanup SQL 3 TM_ACTIVATION_UPDATE_TERR_ZIP
Activation Data Cleanup SQL 4 TM_ACTIVATION_UPDATE_TERR_REGION
TMP Data Cleanup SQL 1 TM_RUN_MINOR_DELETE_TEMP_POSITION
TMP Data Cleanup SQL 2 TM_RUN_MINOR_DELETE_TEMP_ACCNT
TMP Data Cleanup SQL 3 TM_RUN_MINOR_DELETE_TEMP_CON
TMP Data Cleanup SQL 4 TM_RUN_MINOR_DELETE_TEMP_ASSET
TMP Data Cleanup SQL 5 TM_RUN_MINOR_DELETE_TEMP_REGION
TMP Data Cleanup SQL 6 TM_RUN_MINOR_DELETE_TEMP_ZIP
Enable Multiuser Environment Y
Error String - Alignment '%1' is being run or activated by '%2'.

IDS_TM_ERR_ALIGNMENT_IN_USE Please try again later
Error String - Another alignment belonging to hierarchy '%1' is

IDS_TM_ERR_UNIQUE_HIERARCHY being run or activated. Please try again later
Error String - This function is not enabled in disconnected mode.

IDS_TM_NOT_IN_SERVER_MODE Please connect to the server and try again
Additional SQL statements can be configured using the user property Data Cleanup SQL. These
These SQL statements must have one input parameter, Alignment Id. Refer to comdb42.sql
(TM_DELETE_LOAD_SPLITTER) for an example.
"Enable Multiuser Environment" value must be 'Y' for the multi-user functionality to work. If the
value is 'N' or NULL, alignments will work.

Target Object Selector Service

Class: CSSTargetObjectSelectorSvc
User Properties
New? Name Value
N Alignment Join Path BC:TM DirectPos:TOS Target

Account 4 Alignment-Position-
Territory-Account
N Alignment Join Path BC:TM IndirectPos:TOS

Account 5 Target Alignment-
Position-Territory-
Postal Code-Account
Account 6 Target Alignment-
Position-Territory-
Geo Zone-Account

Asset 3 Alignment-Position-
Territory-Asset

Asset 4 Target Alignment-
Position-Territory-
Postal Code-Asset

Contact 4 Alignment-Position-
Territory-Contact

Contact 5 Target Alignment-
Position-Territory-
Postal Code-Contact

Contact 6 Target Alignment-
Position-Territory-
Geo Zone-Contact
Y Minor Operational Join Path Direct:TOS Target

BC:TM Account 1 Alignment-Territory-
Account
Y Minor Operational Join Path Indirect:TOS Target

Postal Code-Account

Geo Zone-Account

User Properties
New? Name Value

BC:TM Asset 1 Alignment-Territory-
Asset

BC:TM Asset 2 Alignment-Territory-
Postal Code-Asset

BC:TM Contact 1 Alignment-Territory-
Contact

Postal Code-Contact

Geo Zone-Contact
Symbolic Strings
Symbolic Strings
Name String Value Project Type
Name String Value Project Type
SBL_TM_FROM_TE From Territory Symbolic Conversion

RRITORY_#_HOR # Strings
SBL_TM_FROM_TE From Territory Symbolic Conversion

RRITORY_HOR Strings
Tables
Table: S_TERRALGN
Add three new columns to the S_TERRALGN table:
Columns
Name User Name Nullable Required Type Length Default
LOCKED_BY_USER_I Locked By Y N Varchar 15

D

Columns
Name User Name Nullable Required Type Length Default

LOCKED_DT Locked Date Y N UTC Date
Time
LOCKED_FLG Locked Flag N Y Character 1 N
Table: S_TERR_ACCNT
Columns
Physical Foreign Key

Name Type Length Nullable Table Required?
FROM_TERR_ID Varchar 15 Y S_TERRITORY N
Table: S_TERR_CON
Columns

Table: S_TERR_REGION
Columns
Table: S_TERR_ZIP
Columns


Table: S_TERRALGN_ACCT
Columns

Table: S_TERRALGN_CON
Columns

Table: S_TERRALGN_REGN
Columns

Table: S_TERRALGN_ZIP
Columns

Workflows
Alignment - Activation Process
Step
Name New
Moving Mappings N
Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 10 1

Input Arguments
Property
Input Argument Type Name
Alignment Id Process Alignment

Property Id
Alignment - Run Alignment Process
Workflow
Process
Properties
Name In/Out Default
AMB Task Ids In/Out
Has Tasks Started In/Out N
Job Status Out
Step
Number Name Type New
1 Load Business N
Balancer/AM Service
2 Get AMB Business Y

Tasks Status Service
3 AMB Tasks Decision Y

Completed? Point
4 Update Decision Y
Alignment Point
Status?
5 Update Siebel Y
Alignment Operation
Status to
Tasks Started
6 Update Siebel Y
Alignment Operation
Status to Run
Completed
7 Update Siebel Y
Alignment Operation
Status to
Tasks Failed

Step
8 Update Siebel Y
Alignment Operation
Status to
Assignment
Failed
9 Data Cleanup Business Y

Service
10 Unlock Siebel Y
Alignment Operation
11 Update Siebel Y
Alignment Operation
Status to
Assignment
Unknown
12 Stop:Process Stop Y
Failed1
Step Number Error Code
12 TM_WF_ERR_
PROCESS_FAI
LED
Step Business Service Business Service Business

Number Name Method Component Operation
2 Alignment Update Tasks Status

Management Service
9 Alignment Data Cleanup

Management Service
5 Alignment Update
6 Alignment Update
7 Alignment Update
8 Alignment Update
10 Alignment Update
11 Alignment Update

Input Arguments
Step
Number Input Type Value Property Name
2 AMB Task Ids Process AMB Task Ids

Property
2 Sleep Time Literal 1
2 Validate Literal Y
Queued Tasks
9 Alignment Id Process Alignment Id

Property
9 Alignment Process Alignment Type

Type Property
9 TMP Tables Literal Y
5 Status Expressio LookupValue("ALIGNMENT_

n STATUS", "Tasks Started")

n STATUS", "Run Completed")

n STATUS", "Run Tasks
Failed")

n STATUS", "Run Tasks Not
Started")

n STATUS", "Run Tasks
Unknown")
11 Locked By Literal
11 Locked Date Literal
11 Locked Flag Literal N

Output
Arguments
Property
Step Number Name Type Output Argument

Property

Property
2 Jobs Status Process Jobs Status

Property
5 Has Tasks Literal Y

Started
Workflow Step
Branch
Step Number Name Type Expression
3 ACTIVE:DECI Condition (Jobs Status One Must Match (Ignore

SION Case)('ACTIVE' AND 'ERR-ACTIVE' AND
'QUEUED'))
3 ASSFAILED:D Condition (Jobs Status This Must Match (Ignore

ECISION Case)('FAILED'))
3 DEFAULT:DEC Default
ISION
3 SUCCESS:DE Condition (Jobs Status This Must Match (Ignore

CISION Case)('SUCCESS'))
ISION1
4 Y:DECISION1 Condition (Has Tasks Started This Must Match (Ignore

Case)('N'))

Alignment - Scheduled Run Assignment

Workflow
Process
Properties
Name In/Out Default
AMB Task Ids In/Out
Has Tasks Started In/Out N
Job Status Out
Step
1 Load Balancer/AM Business N

Service
2 Get AMB Tasks Business Y

Status Service
3 AMB Tasks Decision Y

Completed? Point
4 Update Alignment Decision Y

Status? Point
5 Update Alignment Siebel Y

Status to Tasks Operation
Started

Status to Active Operation

Status to Tasks Operation
Failed

Status to Operation
Assignment Failed
9 Data Cleanup Business Y

Service
10 Unlock Alignment Siebel Y

Operation

Step

Status to Operation
Assignment
Unknown
12 Stop:Process Stop Y
Failed1
Step
Number Error Code
12 TM_WF_ERR_PROCESS_FAILED
Business Business
Operation
Step Service Service Business
Number Name Method Component
2 Alignment Update
Management Tasks
Service Status
9 Alignment Data
Management Cleanup
Service
5 Alignment Update
6 Alignment Update
7 Alignment Update
8 Alignment Update
10 Alignment Update
11 Alignment Update
Input Arguments
Step

Property
2 Sleep Time Literal 1
2 Validate Literal Y
Queued Tasks

Input Arguments
Step
9 Alignment Id Process Alignment Id

Property
9 Alignment Process Alignment Type

Type Property
9 TMP Tables Literal Y

n STATUS", "Tasks Started")

n STATUS", "Active")

n STATUS", "Activation Tasks
Failed")

Not Started")

Unknown")
Output Arguments
Property

Property

Property

Output Arguments
Property
2 Jobs Status Process Jobs Status

Property
5 Has Tasks Literal Y

Started
Workflow Step Branch
Step Number Name Type Expression
3 ACTIVE:DECI Condition (Jobs Status One Must Match (Ignore

SION Case)('ACTIVE' AND 'ERR-ACTIVE' AND
'QUEUED'))
3 ASSFAILED:D Condition (Jobs Status This Must Match (Ignore

ECISION Case)('FAILED'))
ISION
3 SUCCESS:DE Condition (Jobs Status This Must Match (Ignore

CISION Case)('SUCCESS'))
ISION1
4 Y:DECISION1 Condition (Has Tasks Started This Must Match (Ignore

Case)('N'))
Client Database Configuration

Configure tools.cfg to connect to client database and perform the following configuration on the client
database.
Assignment Attribute
Assignment
Attribute
Use
Name Data Type Range
Division Varchar N
Assignment Criteria

Assignment Criteria
Assignment
Criteria
Display
Name Name Team
Division Division Y
Assignment
Criteria Attribute
Assignment Display Display

Name Attribute Name Store Column Sequence
Division Division Division 1 1
Workflow Policy Objects
TM Account
Assignment Object: TM Account
Assignment User
Properties
User Properties
New or
Changed? Name Value
New Copy Position Specific Data SQL 1 TM_COPY_POSTION_DATA_TERR_

ACCNT

ZIP_ACCNT

GEO_ZONE_ACCNT
New Territory Position Specific Columns ROLE_CD

TM Contact
Assignment Object: TM Contact
Assignment User
Properties
User Properties
New or
Changed? Name
New Copy Position Specific Data SQL 1 TM_COPY_POSTION_DATA_TERR

_CON

_ZIP_CON
_GEO_ZONE_CON
New Territory Position Specific Columns LAST_CALL_DT,SPECIALTY,PR_AD

DR_ID
Object Explorer > Workflow Policy Object > Dynamic Candidate > Dynamic Candidate Component >
Dynamic Candidate Component Column
'TM Account' -> 'TM Account' -> 'Staging Minor # TM Account Zip Hierarchy Driven'
Add a new record of Dynamic Candidate Component Column for Dynamic Candidate Component
'Territory'.
Dynamic
Candidate
Component
Columns
Attribute Assignment Assignment

Column Criteria Attribute Criteria Parent
Name Name Name Name Dynamic
Name Attribute Assignment Criteria Assignment Parent Dynamic
Column Name Attribute Name Criteria Name Candidate
Component
Division DIVISION_ID Division Division Territory
Repeat this for all the following dynamic candidates.
Name
Hierarchy Driven Minor Alignment
Staging Minor # TM Account Zip Hierarchy Driven

Name
Staging Minor # TM Account Geo Zone Hierarchy

Driven
Staging Minor # TM Contact Zip Hierarchy Driven
Staging Minor # TM Contact Geo Zone Hierarchy

Driven
Staging Minor # TM Asset Zip Hierarchy Driven
Hierarchy Driven Major Alignment
Staging Major # TM Account Zip Hierarchy Driven
Staging Major # TM Account Geo Zone Hierarchy

Driven
Staging Major # TM Contact Zip Hierarchy Driven
Staging Major # TM Contact Geo Zone Hierarchy

Driven
Staging Major # TM Asset Zip Hierarchy Driven
Hierarchy Driven Operational
Operational # TM Account Zip Hierarchy Driven
Operational # TM Account Geo Zone Hierarchy

Driven
Operational # TM Contact Zip Hierarchy Driven
Operational # TM Contact Geo Zone Hierarchy

Driven
Operational # TM Asset Zip Hierarchy Driven
Object Explorer > Workflow Policy Object > Dynamic Candidate > Dynamic Candidate Component
'TM Account' > 'TM Account' > 'Operational # TM Account Geo Zone Hierarchy Division Driven' ->
'Informational Table'
Update Additional Join Spec by including "AND [Informational Table].ASGN_RULE_GRP_ID =

#RuleGrpId#"
Repeat this for all the following dynamic candidates.
Name
Dynamic Candidate: TM Account

Division Driven

Driven

Name
Operational # TM Account Hierarchy Division

Driven
Operational # TM Account Hierarchy Driven
Operational # TM Account Zip Hierarchy

Division Driven
Operational # TM Account Zip Hierarchy Driven
Dynamic Candidate: TM Contact

Division Driven

Driven
Operational # TM Contact Hierarchy Division

Driven
Operational # TM Contact Hierarchy Driven
Operational # TM Contact Zip Hierarchy

Division Driven
Operational # TM Contact Zip Hierarchy Driven
Dynamic Candidate: TM Asset
Operational # TM Asset Hierarchy Division

Driven
Operational # TM Asset Hierarchy Driven
Operational # TM Asset Zip Hierarchy Division

Driven
Operational # TM Asset Zip Hierarchy Driven

Lists of Values
Lists of Value
Display
Type Value LIC New?
ALIGNMENT_STATUS Imported Imported N
ALIGNMENT_STATUS Validated Validated N
ALIGNMENT_STATUS Assigned Assigned N
ALIGNMENT_STATUS Active Active N
ALIGNMENT_STATUS Moving Moving Territory N

Territory Rules
Rules
ALIGNMENT_STATUS Creating Creating N

Assignment Assignment
Rules Rules
ALIGNMENT_STATUS Scheduling Scheduling N

Assignment Assignment Run
Run
ALIGNMENT_STATUS Scheduled Scheduled N
ALIGNMENT_STATUS Identifying Identifying N

Affected Affected Objects
Objects
ALIGNMENT_STATUS Splitting Splitting N

Assignment Assignment
Tasks Tasks
ALIGNMENT_STATUS In Progress In Progress N
ALIGNMENT_STATUS Process Failed Process Failed N
ALIGNMENT_STATUS Update Rules Update Rules for N

for Production Production
ALIGNMENT_STATUS Alignment Alignment Run N

Run Failed Failed
ALIGNMENT_STATUS Alignment Alignment N

Activation Activation Failed
Failed
ALIGNMENT_STATUS Run Run Completed Y

Completed
ALIGNMENT_STATUS Tasks Started Tasks Started Y
ALIGNMENT_STATUS Run Tasks Not Run Tasks Not Y

Started Started

Lists of Value
Display
Type Value LIC New?
ALIGNMENT_STATUS Activation Activation Tasks Y

Tasks Not Not Started
Started
ALIGNMENT_STATUS Run Tasks Run Tasks Failed Y

Failed

Tasks Failed Failed
ALIGNMENT_STATUS Run Tasks Run Tasks Y

Unknown Unknown
Tasks Unknown
Unknown
ALIGNMENT_TYPE Major Major N
ALIGNMENT_TYPE Minor Minor N
ALIGNMENT_TYPE Intermediate Intermediate Y
Further Information About ACR 263

The state of the 'Run Alignment', 'Activate' and 'Rollback' buttons that are based on the Alignment
Status field can be determined using the updated Alignment BC user properties.
Run
Alignment Alignment Activate
Status Read-Only Enabled? Enabled? Rollback Enabled?
Imported X
Validated X
Assigned X
Active X
Moving Territory X
Rules
Creating X
Assignment Rules
Scheduling X
Assignment Run
Scheduled X X

Run
Alignment Alignment Activate
Status Read-Only Enabled? Enabled? Rollback Enabled?
Identifying X "
Affected Objects
Splitting X
Assignment Tasks
In Progress X
Process Failed X
Update Rules for X

Production
Alignment Run X
Failed
Alignment X X
Activation Failed
Run Completed X X
Tasks Started X
Run Tasks Not X

Started
Activation Tasks X X
Not Started
Run Tasks Failed X
Activation Tasks X
Failed
Run Tasks X X
Unknown
Activation Tasks X
Unknown
The following SQL statements can be used by an administrator to unlock a hierarchy or all hierarchies
in the case of exceptions that result in alignments being locked out forever:
■ SQL to unlock a single hierarchy:
UPDATE [tblo].S_TERRALGN SET LOCKED_FLG = 'N', LOCKED_BY_USER_ID = NULL, LOCKED_DT

= NULL WHERE LOCKED_FLG = 'Y' AND TERR_HIER_ID = (SELECT ROW_ID FROM
[tblo].S_TERR_HIER WHERE NAME = '[Hierarchy Name]')
■ SQL to unlock all hierarchies
UPDATE [tblo].S_TERRALGN SET LOCKED_FLG = 'N', LOCKED_BY_USER_ID = NULL, LOCKED_DT

= NULL WHERE LOCKED_FLG = 'Y'


Use the instructions in this section to set up and configure ACR 272.
The following files are necessary for implementing ACR 272:
■ ACR_272_High_Miles_Changes.xls
■ ACR_272_Repository_Changes.xls
■ ACR_272_schema.xls
Configuration Setup
NOTE: Refer to the ACR_272_Repository_Changes.xls document for information about necessary
Siebel Tools configurations.
Schema Setup
1 Open ACR 272 Schema Changes.xls.
2 Within Siebel Tools, navigate to the S_LOY_MEM_TIER table, lock the table, and add the columns
detailed in the spreadsheet.
3 Apply the schema changes by clicking the Apply/DLL button within Siebel Tools.
LOV Setup
1 In Siebel Tools, navigate to Screen > System Administration > List of Values.
2 Enter the LOVs listed for Member Tier Status, Member Tier Level Attributes, Transaction
Attributes and Criteria as specified in the LOVs worksheet in Repository Changes.xls.
NOTE: Not all of the LOVs have the same language-independent value as the language-
dependent value. These values should be entered as-is according to the spreadsheet. You do not
need to enter the LOVs if they are already present.
Business Component Setup

2 Click on Business Component, and query for each Business Component specified in the BC Fields
3 For each Business Component, check to see if the Business Component already exists. If it does
not, you will need to create it.
4 Click on the Join item of the Business Component. If the Join and Join Specification already exist,
modify them. If they do not already exist, add new Join and Join Specifications for the Business
Component.
5 Click on the Field item of the Business Component, and modify the existing fields. If the fields
do not exist, add new fields. Add a Pick Map for the field, if one is required.

6 Click on the Business Component User Property item of the Business Component. If the item
already exists, modify it. If it does not already exist, add a new Business Component User
Property using the information listed in the BC User Props worksheet within Repository
Changes.xls.
Business Service Setup

1 In Siebel Tools, navigate to Object Explorer, and click on Business Service.
2 Query for each Business Service specified in the Business Service worksheet within Repository
Changes.xls.
3 Click on the Business Service Method item of the Business Service. If the item already exists,
modify it. If it does not already exist, add new Business Service Method and Business Service
Method Arguments listed in the Business Service worksheet within Repository Changes.xls.
4 Click on the Business Service User Prop item of the Business Component. If it already exists,
modify it. If it does not already exist, add the new Business Service Method and Business Service
Method Arguments listed in the Service User Props worksheet within Repository Changes.xls.
Link Setup
2 Click Link, and query for the Link specified in the Links worksheet within Repository Changes.xls.
If the Link already exists, modify it. If it does not already exist, add the new Links listed in the
Links worksheet within Repository Changes.xls.
Business Object Setup

1 In Siebel Tools, navigate to Object Explorer, and click Business Object.
2 Query for the Business Object specified in the BO Changes worksheet within Repository
Changes.xls.
3 Click on the Business Object Component item of Business Object. If the item already exists,
modify it. If it does not already exist, add a new Business Object Component for the Business
Object listed in the BO Changes worksheet within Repository Changes.xls.
4 Click on the Business Service User Prop item of the Business Component. If the item already
exists, modify it. If it does not already exist, add the new Business Service Method and Business
Service Method Arguments listed in the Service User Props worksheet within Repository
Changes.xls.
Symbolic String Setup

2 Click on Symbolic Strings, and add the new Symbolic Strings specified in the Symbolic Strings

Applet Setup
2 Click on Applet, and query for the Applets specified in the Applet Changes worksheet within
Repository Changes.xls.
3 Click on the List Column item of the Applet, and modify the item if it exists. If it does not already
exist, add a new List Column for the Applet listed in the Applet Changes worksheet within
Repository Changes.xls and add it to any available column in the Web template.
4 Click on Applet toggle item of the Applet, and modify the item if it exists. If it does not already
exist, add the new Applet toggle listed in the Applet Changes worksheet within Repository
Changes.xls.
Program Setup
Refer to the High Miles Changes.xls document for instructions about setting up Program
configuration. These are the suggested program changes to illustrate how this feature should be set
up. However, the actual implementation may vary.
LOV Setup
1 Within Siebel Loyalty, navigate to Site Map > Administration Data > List of Values.
2 Verify that all the LOVs are listed for Member Tier Status, Member Tier Level Attributes,
Transaction Attributes, and Criteria.
Program Level Attributes Setup

1 Within Siebel Loyalty, navigate to Loyalty Program Administration, and query for High Miles
Program.
2 Drill down on Program Id.

3 Navigate to the Go To Program Level Attributes view, and then to the LOY Program Member
Attributes view.
4 Click the New button to add the Member Attributes listed in the Program Level Attributes work
sheet within High Miles Changes.xls.
5 Navigate to Member Tier Attributes 3LN, and click the New button to add the Member Tier
6 Navigate to Transaction Attributes 3LN, and click the New button to add the Transaction
Tier Rule Setup

1 Within Siebel Loyalty, navigate to Loyalty Program Administration and query for the High Miles
program.

2 Drill down on Program Id, click on the Tier Class tab, and navigate to the LOY Program Tier Admin
view.
3 Select HM Tier Class 2 and navigate to the LOY Tier List Applet - Admin bottom applet.
4 Drill down on each Tier Id, which will take you to the LOY Promotion Rules View - Admin view.
5 Click the Modify button and add the related Rules, Action and Criteria specified in the Tier Rule
worksheet within High Miles Changes.xls.
6 Click the Activate button to activate the modified promotion.
7 Repeat the same steps for HM Tier Class 1 and related tiers.
Admin - Retro Accruals Setup

program.
2 Drill down on Program Id, click on the Promotion tab and navigate to the LOY Program Tier Admin
view.
3 Select Admin - Accruals Promotion and copy the record.
4 Rename Promotion Name to Admin - Retro Accruals.
5 Add related Rules, Action and Criteria specified in the Admin - Retro Accruals worksheet within
High Miles Changes.xls.
Admin - Cancellation Setup

program.
2 Drill down on Program Id, click the Promotion tab, and navigate to the LOY Program Tier Admin
view.
3 Drill down on Promotion# of Admin - Cancellation Promotion.

4 Rename Promotion Name to Admin - Retro Accruals
5 Click the Modify button and add the related Rules, Action and Criteria specified in the Admin -
Cancellation worksheet within High Miles Changes.xls.

Use the following procedure to configure ACR 296.
You must have applied all of the configuration changes for ACR 263 in the application database before
you begin configuring ACR 296. If you have not applied the configuration changes for ACR 263, see
“Instructions for ACR 263” on page 73.

Use the following procedure to configure ACR 296:
1 Connect Siebel Tools to the application database, and lock the Territory Management project.
2 Import \REPPATCH\ACR296_Repository.sif (available under the REPPATCH folder from the Siebel
Tools install location after applying the QF) by navigating to Siebel Tools > Import from Archive
> Browse .sif file and then click OK.
3 Create a new Business Component called "TM Account Position" with the following values:
TM Account Position
Name TM Account Position
Project Territory Management
Class CSSBusComp
Table S_ACCNT_POSTN
Log Changes TRUE
Fields
Text
Name Column Length Type
Name Column Text Type

Length
Assign Rule Group ASGN_RULE_ 15 DTYPE_ID

Id GRP_ID
Assign Territory Id ASGN_TERR_ 15 DTYPE_ID

ID
Position Id POSITION_ID 15 DTYPE_ID
Account Id OU_EXT_ID 15 DTYPE_ID
4 Create a new Business Component called "TM Asset Position" with the following values:
TM Asset Position
Name TM Asset Position
Class CSSBusComp
Table S_ASSET_POSTN
Log Changes TRUE

Fields
Text
Name Column Length Type

Length

Id GRP_ID

ID
Position Id POSITION_ID 15 DTYPE_ID
Asset Id ASSET_ID 15 DTYPE_ID
5 Create a new Business Component called "TM Contact Position" with the following values:
TM Contact Position
Name TM Contact Position
Class CSSBusComp
Table S_POSTN_CON
Log Changes TRUE
Fields

Length

Id GRP_ID

ID
Position Id POSTN_ID 15 DTYPE_ID
Contact Id CON_ID 15 DTYPE_ID
6 Add the TM Account Position, TM Asset Position, and TM Contact Position Business Components
that you created to the Alignment Business Object.

7 Update the "Alignment" Business Component by removing the following user properties:
User Properties
Name Value
Direct Territory Rules 4 "TM Account", "Alignment Territory

Position Account Mapping"
Direct Territory Rules 5 "TM Contact", "Alignment Territory

Position Contact Mapping"
Direct Territory Rules 6 "TM Asset", "Alignment Territory

Position Asset Mapping"
Indirect Territory Rules 6 "TM Account", "Alignment Territory

Position Postal Code Mapping", "Account
Flag,Zip"
Indirect Territory Rules 7 "TM Contact", "Alignment Territory

Position Postal Code Mapping", "Contact
Flag,Zip"
Indirect Territory Rules 8 "TM Asset", "Alignment Territory

Position Postal Code Mapping", "Asset
Flag,Zip"
Indirect Territory Rules 9 "TM Account", "Alignment Territory

Position Geo Zone Mapping", "Account
Flag,Geo Zone"
Indirect Territory Rules 10 "TM Contact", "Alignment Territory

Position Geo Zone Mapping", "Contact
Flag,Geo Zone"
8 Import the following workflows into the application database:

■ \reppatch\ACR296\ACR296_Alignment - Run Alignment Process.xml
■ \reppatch\ACR296\ACR296_Alignment - Scheduled Run Assignment.xml

■ \reppatch\ACR296\ACR296_Alignment - Periodic Runs.xml
9 In Object Explorer, select the Select Workflow Policy Object node and query for the "TM Contact"
Workflow Policy Object.
10 Select Workflow Policy Component node under the Workflow Policy Object node and configure the
Workflow Policy Components as follows:
Source Target
Source Table Column Target Component
Name Name Name Component Column Name
Geo Zone S_REGION_CON CONTACT Contact ROW_ID

Relationship _ID
(Existing)

11 Select Workflow Policy Object node in the Object Explorer view and query for the "TM Asset"
Workflow Policy Object.
12 Select Workflow Policy Component node under the Workflow Policy Object node and configure the
Workflow Policy Components as follows:
Source
Source Table Column Target Target Component
Name Name Name Component Column Name
Account (New S_ORG_EXT ROW_ID Asset OWNER_ACCNT_ID

Component)
Address (Existing) S_ADDR_PER ROW_ID Account PR_ADDR_ID
13 Compile the changed Territory Management project and the following Business Components and
Business Objects:
■ Alignment Business Component
■ TM Account Position Business Component
■ TM Contact Position Business Component
■ TM Asset Position Business Component
■ Alignment Business Object

The following sections contain procedures for configuring ACR 308.
Applet
1 Create a new applet called Asset Bulk Inventory Txn Popup Applet with the values contained in
the following tables:
Applets
Title -
Business String
Name Project Component Class Title Reference Type
Asset Bulk FS Inventory Bulk CSSSWEF Inventory SBL_INVEN Standar

Inventory Txn Transaction Inventory Txn ramePopu Transaction TORY_TRAN d
Popup Applet Popup VBC pInvTxn s SACTIONS-
100423085
5-0AR

Applet User Properties
Name Value
Inv Txn Workflow Bulk Inventory Transaction - Asset List - Default
Read Field 1 Destination Inv ID
Read Field 2 Destination Status
Read Field 3 Destination Availability
Read Field 4 Transaction Type ID
Read Field 5 Comments
Row Property Asset Id
Row Property Set Value Asset
Row Set Property Set Value Asset List
Applet Web Templates
Upgra ICL
Web de Upgra Contain
Nam Change Se Typ Templat Behavi de Inacti Commen er
W e d q e e or Path ve ts Module
Y Edit Y 0 Edit Popup Preserv N

Form e
Applet Web Template Items
Name Control Item Identifier Type
CloseApplet CloseApplet 153 Control

Comments Comments 1,303 Control
Destination Destination 2,301 Control
Destination Availability Destination Availability 2,303 Control
Destination Status Destination Status 2,302 Control
Label Comments Label Comments 1,203 Control
Label Destination Label Destination 2,201 Control

Availability Availability

Status Status
Label Selection Type Label Selection Type 1,201 Control
Label Transaction Type Label Transaction Type 1,202 Control


Selection Type Selection Type 1,301 Control
Transaction Type Transaction Type 1,302 Control
Transfer Transfer 152 Control
Controls
Field
Caption
Field Type
HTML Type
HTML Row Sensitive
Method Invoked
Text Alignment Label
Visible
Pick Sor Runti Caption - String

Name Applet t me Reference
CloseAppl Y N SBL_CANCEL-
Cancel
MiniButton
CloseApplet
et 1004230137-1J7
Comment Y Y SBL_COMMENTS-
Comments
Comments
BC Field
Text Area
Right
s 1004225654-00N
Destinati FS Y Y SBL_DESTINATION
Destination Inventory
Destination
BC Field
Field
Right
on Inventor -1004225143-0AA
y
Location
Pick
Applet

Controls
Field
Caption
Field Type
HTML Type
HTML Row Sensitive
Method Invoked
Visible
Destinati Y Y SBL_DESTINATION
Destination Availability
BC Field
Field
Right
Y
on _AVAILABILITY-
Availabilit 1004231000-2LG
y
Destinati Y Y SBL_DESTINATION
Destination Status
Destination Status
BC Field
Field
Right
on Status _STATUS-
1004231001-2LO
Label Y N SBL_COMMENTS-
Comments
Label
Right
Comment 1004225654-00N
s
Label Y N SBL_DESTINATION
Destination
Label
Right
Destinati -1004225143-0AA
on

Controls
Field
Caption
Field Type
HTML Type
HTML Row Sensitive
Method Invoked
Visible
Label
Right
Y
Destinati _AVAILABILITY-
on 1004231000-2LG
Availabilit
y
Destination Status
Label
Right
Destinati _STATUS-
on Status 1004231001-2LO
Label Y N SBL_SELECTION_T
Selection Type
Label
Selection YPE-1005112954-
Type 2V3
Label Y N SBL_TRANSACTION
Transaction Type
Label
Right
Transacti _TYPE-
on Type 1004233441-77Q

Controls
Field
Caption
Field Type
HTML Type
HTML Row Sensitive
Method Invoked
Visible
QueryAss Y N SBL_QUERY_ASSIS
Query Assistant
MiniButtonQuery
ShowQueryAssistant
Y
istant TANT-1004224746-
2EA
Selection Y Y SBL_SELECTION_T
Selection Type
Selection Type
BC Field
Field
Type YPE-1005112954-
2V3
Transacti FS Y Y SBL_TRANSACTION
Transaction Type
Transaction Type
BC Field
Field
Right
on Type Inventor _TYPE-

y Txn 1004233441-77Q
Type Pick
Applet
Transfer Y N SBL_TRANSFER-
Transfer
MiniButton
BulkTransfer
1004224757-2UN

2 Add a “Transfer” butto to the Asset Mgmt - Asset List Applet, with the values shown in the
following tables:
Controls
Field
Caption
Method Invoked
Field Type
Changed
HTML Type
HTML Row Sensitive
HTML Display Mode
Visible
Pick Applet
Sort
Runtime
Name Caption - String Reference
bBulkTra SBL_TRANSFER-1004224757-
Transfer
ShowPopup
Y
MiniButtonEdit
Y
EncodeData
N
nsfer 2UN
Control User
Properties
Name Value Inactive Comments
Mode Edit N
Popup Asset Bulk Inventory N

Txn Popup Applet

bBulkTransfer bBulkTransfer 109 Control

Business Component
1 Create a new Business Component called Bulk Inventory Txn Popup VBC with the values shown
in the following tables:
Business Component
Name
Project
Cache Data
Class
Dirty Read
Distinct
Force Active
GenReassignAct
Hierarchy Parent Field
Type
Inactive
InsertUpdate All Columns
Log Changes
Multirecipient Select
No Delete
No Insert
No Update
No Merge
Owner Delete
Popup Visibility Auto All

Popup Visibility Type
Scripted
Search Specification
Sort Specification
Status Field
Table
Bulk Inventory Txn Popup VBC
FS Inventory Transaction
N
CSSBCVSpreadDiscount
Y
N
N
Non-Transient
Fields
Immediate
Post Predefault
Name Changes Picklist Value Required Type
Comments N N DTYPE_TEXT
Destination Y FS PickList Y DTYPE_TEXT

Availability ProdInvCat
Availability
Destination Y Y DTYPE_ID
Inv ID

Inventory Inventory
Location

Fields
Immediate
Post Predefault
Name Changes Picklist Value Required Type

Status ProdInvCcat
Status
Selection Y Bulk Inventory Expr: Y DTYPE_TEXT

Type Txn Type 'LookupValue
Picklist ("BULK_INV_TXN
_TYPE",
"Selected
Items")'
Transaction Y FS PickList Y DTYPE_TEXT

Type Inventory Txn
Type
Transaction Y Y DTYPE_ID
Type ID
Field - Destination Availability
Pick
Maps
Pickli
Chang Constra No st Seque
Field ed in Clear Field nce Inactive Comment Module
Destinatio Y N Value N
n
Availabilit
y

Field - Destination Inventory
Pick Maps
No
Chang Constr Clea Picklis Sequenc Inacti Commen Modu
W Field ed ain r t Field e ve ts le
Y Destinatio Y N Id N
n Inv ID
Y Destinatio Y N Invent N
n ory
Inventory Name
Field - Destination Status
Pick Maps
Chang Constr No Picklis Sequen Inactiv Commen Modul

W Field ed ain Clear t Field ce e ts e
Y Destinati Y N Value N
on
Status
Field - Selection Type
Pick Maps
Change Constr No Picklis Sequen Inactiv Comme Modul
W Field d ain Clear t Field ce e nts e
Y Selecti Y N Value N
on
Type

Field - Transaction Type
Pick Maps
Change Constr No Picklist Sequenc Inacti Comme Modu

W Field d ain Clear Field e ve nts le
Y Transacti Y N Transacti N
on Type on Type
Y Transacti Y N Id N
on Type
ID
Business Object
1 Add a new Business Component to the Asset Management Business Object, with the values in
the following table:
Business Object Components
Business
W Component Changed Inactive Link Comments Module
Y Bulk Inventory Y N
Txn Popup VBC

Business Service
1 Create a new Business Service called Inventory Transaction, with the values shown in the
following tables:
Business Services
Project
Cache
Class
Display Name
External Use
Hidden
Server Enabled
State Management Type

Web Service Enabled
Display Name -
String
Name Reference Coments
Inventory SBL_INVENTORY This Business

N
CSSInvTxnBusServ
Inventory Transaction
Stateful
N
Transaction _TRANSACTION- Service is used
1004233346- for Inventory
4ZT Transaction. It
has APIs for Bulk
transfer as well
as single
Inventory
Transaction
Business Service Methods

Name Display Name Hidden Inactive Comments
AddAssetsToTxn N N This method adds Assets to

the Inventory transaction
record.
AggrAssetsPerProdPer N N Used to aggregate Assets

Source based on Properties
specified by "Aggregate per
Property 1...n". Each such
aggregation will form one
transaction. This is used so
that Assets of same
Product with the same
Source details are part of
the same transaction

Business Service Methods
Name Display Name Hidden Inactive Comments

BulkTransfer N N This method loops around
and calls the next step to
create each Inventory
transaction. During each
iteration, a child is
removed and passed to the
next step to create the
transaction. When the child
count reaches 0, the loop
should stop.
CommitTxn N N This method commits the

transaction.
CreateCompleteInvTxn N N
GetDetails N N This method is used to

Query the specified
Business Component and
get the fields that start
with "Input: xxx". These
are added into the Property
Set as Properties. It goes in
a loop for each Line Item
and queries for the fields.
SetTxnDetails N N This method creates the

inventory transaction
record. It can only take
input arguments that are
fields on Inventory
Transaction Business
Component or they start
with "Default:". It outputs
the Id of the created
transaction.
SetTxnDetailsFromTxn N N This method reads the

Set transaction details from
"Inventory Transaction
Set" and creates a
transaction record. All the
fields specified by "Inv Txn
Field: " are populated on
the transaction. This
method calls
"SetTxnDetails" method
internally.

Business Service Method AddAssetsToTxn Arguments
Storage
Name Changed Data Type Type Comments Optional Type
Asset ID Y String Input Name of the N Property

Property Name Property on the
Line Item which
has the Asset
ROW_ID.
Asset Row Set Y Hierarchy Input This input N Hierarchy

Property Set has
Line Item
Children
property Sets.
Each Line Item
represents one
Asset.
Assets Not Y Hierarchy Output This Property Set Y Hierarchy

Added Row Set contains the
Assets that were
not added to the
inventory
transaction
record. The
reasons could be
because the
product of the
Asset does not
match the
product on the
transaction or
the Source
bucket does not
match.
Auto Update Y String Input If it is "Y" it will Y Property

Quantity update the
Quantity on the
inventory
transaction
record with the
exact number of
Assets that could
be added to the
transaction.
Error Code Y String Output N Property

Business Service Method AddAssetsToTxn Arguments
Storage
Inventory Y String Input This is the N Property

Transaction ID ROW_ID of the
Inventory
transaction to
which the assets
are added.
Valid Asset Y Number Output The actual Y Property

Quantity number of assets
that is added to
the inventory
transaction.
Business Service Method AggrAssetsPerProdPerSource Arguments
Data
Name Type Type Comments Optional Storage Type
Aggregate String Input Value of this i/p argument is the Y Property

Per Property name of the property on which
1 aggregation takes place. There
should at least be 4 such
properties. The values should be
Properties for Product Id, Source
Inventory Id, Source Status and
Source Availability

Source Availability

Source Availability

Business Service Method AggrAssetsPerProdPerSource Arguments
Data
Name Type Type Comments Optional Storage Type
Aggregate String Input Value of this i/p argument is N Property

Source Availability
Bulk Hierarc Output This is the output Property Set N Hierarchy

Transfer List hy which has the aggregated
Assets. Each aggregation is a
child property set and has
distinct values for the properties
on which the aggregation took
place. Each child will be of a
unique Product and Source
combination
Row Set Hierarc Input Input Property Set. It has several N Hierarchy
hy Line Item children Property Sets.
Each Line Item represents an
Asset and has the properties on
which the aggregation takes
place.

Business Service Method 'BulkTransfer' Arguments
Storage
Name Changed Data Type Type Comments Optional Storage

Type
Bulk Transfer Y Hierarchy Input / Each child of N Hierarchy

List Output this property
set represents
one Inventory
Transaction.
During each
iteration, the
last child is
removed and
passed on to
the next step.
This Property
Set with one
less child is
also outputted
for the next
loop.
Child Count Y String Output It gives the N Property

remaining
number of
children
present in
"Bulk Transfer
List". When
this count goes
to 0 there are
no more
children and
the loop should
stop.

Business Service Method 'BulkTransfer' Arguments
Storage
Context Y Hierarchy Input This Property N Hierarchy

Set has context
information for
all the
Inventory
transactions.
Generally the
destination
information.
The Context is
combined with
each child of
"Bulk Transfer
List" to create
"Inventory
Transaction
Set".
Inventory Y Hierarchy Output This is a N Hierarchy

Transaction combined
Set Property Set of
a "Bulk
Transfer List"
child and the
"Context". This
has all the
information
needed for a
single
transaction.
This is passed
on to the next
step to create
the Inventory
Transaction

Business Service Method CommitTxn Arguments
Data
Name Changed Type Type Comments Optional Storage Type
Inventory Y String Input This is the N Property

Transaction ROW_ID of the
ID inventory
transaction
record that
needs to be
committed.
Business Service Method Create CompleteInvTxn Arguments
Storage
Asset ID Y String Input N Property

Property Name
Asset Row Set Y Hierarchy Input N Hierarchy
Comments Y String Input Y Property
Destination Y String Input N Property

Availability
Destination Inv Y String Input N Property

ID
Destination Y String Input N Property

Status
Inventory Y String Output N Property

Transaction ID
Product ID Y String Input N Property
Quantity Y Number Input N Property
Source Y String Input N Property

Availability
Source Inv ID Y String Input N Property
Source Status Y String Input N Property
Transaction Y Date Output N Property

Date

Business Service Method Create CompleteInvTxn Arguments
Storage
Transaction Y String Output N Property

Number
Transaction Y String Input N Property

Type ID
Business Service Method GetDetails Arguments
Data
Business Y String Input Name of the N Property

Component Business
Component to
Query
Business Y String Input Name of the N Property

Object Business Object
to Query
Input: Y String Input Value of this i/p "Y Property

Product ID argument is the
name of the Field
for which to
query. The data
that is got in
inserted as a
property in the
Line Item. Name
of this property
is 'xxx' where the
I/p argument is
"Input: xxx

Source argument is
Bucket ID name of the Field
for which to
query. The data
that is got in
inserted as a
property in the
Line Item. Name
of this property
is 'xxx' where the
I/p argument is
"Input: xxx

Data

Source Inv argument is
ID name of the Field
for which to
query. The data
that is got in
inserted as a
property in the
Line Item. Name
of this property
is 'xxx' where the
I/p argument is
"Input: xxx
Row Y String Input Value of this i/p 'N Property

Property argument is
Name name of the
property which
has the value for
the query. If the
value is "Asset
Id" and the
property in the
line item is
[Asset Id] =
'123', the query
on the Business
Component will
be [xxx] = '123

Data
Row Set Y Hierarch Input / Input Property N Hierarchy

y Output Set. This has
Line Item
children Property
Sets. Each Line
Item
corresponds to
one of the multi-
selected rows.
Line Item has a
property with the
corresponding
ROW_ID. Fields
that are queried
are inserted as
properties in the
line item.
SearchSpec Y String Input Value of this i/p N Property

Field argument is the
field on which
the query is
done. If the
value is "Id", the
query on the
Business
component will
be [Id] = 'xxxx'.
This xxxx is the
value of the
property in the
Line Item
specified by
"Row Property
Name" i/p
argument.

Business Service Method SetTxnDetails Arguments
Data Storage
Name Changed Type Type Comments Optional Type
Comments Y String Input Inventory Y Property

Transaction
Business
Component field
Default: Source Y String Input "Default: xxx". Y Property

Availability Value of this i/p
argument is the
default value for
"xxx" field on
Inventory
Transaction
Business
Component

Inv ID Value of this i/p
argument is the
default value for
"xxx" field on
Inventory
Transaction
Business
Component

Status Value of this i/p
argument is the
default value for
"xxx" field on
Inventory
Transaction
Business
Component
Destination Y String Input Inventory N Property

Availability Transaction
Business
Component field
Destination Inv Y String Input Inventory N Property

ID Transaction
Business
Component field

Business Service Method SetTxnDetails Arguments
Data Storage
Name Changed Type Type Comments Optional Type
Destination Y String Input Inventory N Property

Status Transaction
Business
Component field
Inventory Y String Output Inventory N Property

Transaction ID Transaction
Business
Component field
Product ID Y String Input Inventory N Property

Transaction
Business
Component field
Quantity Y String Input Inventory N Property

Transaction
Business
Component field
Source Y String Input Inventory N Property

Availability Transaction
Business
Component field
Source Inv ID Y String Input Inventory N Property

Transaction
Business
Component field
Source Status Y String Input Inventory N Property

Transaction
Business
Component field
Transaction Date Y Date Output Inventory N Property

Transaction
Business
Component field
Transaction Y String Output Inventory N Property

Number Transaction
Business
Component field
Transaction Type Y String Input Inventory N Property

ID Transaction
Business
Component field

Business Service Method SetTxnDetailsFromTxnSet Arguments
Data
Auto Calculate Y String Input If it is "Y" and Y Property

Quantity Quantity
property is
empty it
calculates the
Quantity by
counting the
number of Line
Item Children
present in the
Row Set of
"Inventory
Transaction Set”
Default: Y String Input "Default: xxx". Y Property

Source Value of this i/p
Availability argument is the
default value for
"xxx" field on
Inventory
Transaction
Business
Component

Source Inv ID Value of this i/p
argument is the
default value for
"xxx" field on
Inventory
Transaction
Business
Component

Source Status Value of this i/p
argument is the
default value for
"xxx" field on
Inventory
Transaction
Business
Component

Data
Inv Txn Field: Y String Input "Inv Txn Field: Y Property

Comments xxx". Here "xxx"
is the field on
Inventory
Transaction
Business
Component that
is going to be
populated. It is
populated with a
property from
"Inventory
Transaction set"
specified by the
value of this i/p
argument.
Inv Txn Field: Y String Input "Inv Txn Field: N Property

Destination xxx". Here "xxx"
Availability is the field on
Inventory
Transaction
Business
Component that
is going to be
populated. It is
populated with a
property from
"Inventory
Transaction set"
specified by the
value of this i/p
argument.

Data

Inv ID is the field on
Inventory
Transaction
Business
Component that
is going to be
populated. It is
populated with a
property from
"Inventory
Transaction set"
specified by the
value of this i/p
argument.

Status is the field on
Inventory
Transaction
Business
Component that
is going to be
populated. It is
populated with a
property from
"Inventory
Transaction set"
specified by the
value of this i/p
argument.

Data

Product ID xxx". Here "xxx"
is the field on
Inventory
Transaction
Business
Component that
is going to be
populated. It is
populated with a
property from
"Inventory
Transaction set"
specified by the
value of this i/p
argument.

Quantity xxx". Here "xxx"
is the field on
Inventory
Transaction
Business
Component that
is going to be
populated. It is
populated with a
property from
"Inventory
Transaction set"
specified by the
value of this i/p
argument.

Data

Source xxx". Here "xxx"
Availability is the field on
Inventory
Transaction
Business
Component that
is going to be
populated. It is
populated with a
property from
"Inventory
Transaction set"
specified by the
value of this i/p
argument.

Source Inv ID xxx". Here "xxx"
is the field on
Inventory
Transaction
Business
Component that
is going to be
populated. It is
populated with a
property from
"Inventory
Transaction set"
specified by the
value of this i/p
argument.

Data

Source Status xxx". Here "xxx"
is the field on
Inventory
Transaction
Business
Component that
is going to be
populated. It is
populated with a
property from
"Inventory
Transaction set"
specified by the
value of this i/p
argument.

Transaction xxx". Here "xxx"
Type ID is the field on
Inventory
Transaction
Business
Component that
is going to be
populated. It is
populated with a
property from
"Inventory
Transaction set"
specified by the
value of this i/p
argument.
Inventory Y String Output ROW_ID of the N Property

Transaction ID Inventory
Transaction
record that is
created

Data
Inventory Y Hierarch Input It is the Input N Hierarchy

Transaction y Property Set
Set which has Row
Set and Context
as its children.
These children
have all the
information for
the Inventory
Transaction.
Row Set Y Hierarch Output Row Set of the Y Hierarchy

y "Inventory
Transaction Set".
It generally has
the list of Asset
Line Items.
Transaction Y Date Output Transaction Date N Property

Date of the Inventory
Transaction
record that is
created
Transaction Y String Output Transaction N Property

Number Number of the
Inventory
Transaction
record that is
created

Class
1 Create new classes called CSSSWEFramePopupInvTxn and CSSInvTxnBusServ, using the values
shown in the following table:
Classes
DLL
Object Type
Super Class
Handheld Client
High Interactivity Enabled

Name Project Comments
CSSSWEFramePopupInvTxn FS Inventory Inventory

SSCAFSFR
Applet
CSSSWEFramePopup
5
Transaction Transaction
Popup Applet
CSSInvTxnBusServ FS Inventory Class for

ClientAppFSOMSVInvTxnDll
Service
CSSService
1
Transaction Inventory
Transaction
Business
Service

DLL
1 Create a new DLL called ClientAppFSOMSVInvTxnDll, with the values shown in the following
table:
DLLs
Changed
Attributes
Code or Class ID
Java Package
Name Project File Name Comments
ClientAppFSOMS FS Inventory sscafsinvtxn.dll Dll for Inventory

Y
VInvTxnDll Transaction Transaction

Business Service
Picklist
1 Create a new picklist called Bulk Inventory Txt Type Picklist, with the values shown in the
following table:
Picklists
Project
Changed
Bounded
Business Component
Inactive
Long List
No Delete
No Insert
No Merge
No Update
Search Specification
Sort Specification
Static
Type Field
Type Value
Visibility Auto All
Visibility Type
Name
Bulk Inventory
PickList Generic
N
Y
Type
BULK_INV_TXN_TYPE
Txn Type Picklist

■ 15 7
BULK_INV_TXN_TYPE
Description
Create the LOV_TYPE and BULK_INV_TXN_TYPE LOVS with the values shown in the following
Bitmap
Siebel Maintenance Release Guide Version 7.8.2, Rev. X

Weighing Factor
Target High
Target Low
Replication Level All All All
Language Name English-American English-American English-American
Active Y Y Y
Order 1 1
Low
High
Parent LIC
Language-Independent Code BULK_INV_TXN_TYPE Entire Document Selected Items
Multilingual N N N
Y Y Y
Translate
BULK_INV_TXN_TYPE Entire Document Selected Items
Display Value
BULK_INV_TXN_TYPE
BULK_INV_TXN_TYPE
Lists of Values
List of Values
LOV_TYPE
table:
Type
1
Workflows
1 Create a new workflow called Bulk Inventory Transaction - Asset List -Default with the following
steps: Start > Get Asset Details > Get Source Details > Aggregate Per Product Per Source > Bulk
Transfer > Create Inv Txn > Has More Children (Decision Step) > End.
2 Create a new workflow called Inventory Transaction > Asset List > Default with the following
steps: Start > Add Txn > Add Assets > Commit Txn > End.
Error Strings
Resource Identifier: IDS_INVALID_SELECTION_TYPE
Text: Selection type field is empty. Please choose appropriate selection type
Resource Identifier: IDS_INVALID_INPUT_ARG
Text: The required Input Argument '%1' is missing in '%2' method of '%3' Business Service

To implement ACR 323, you must modify Business Components and Applets within Siebel Tools. You
must also perform modifications within the Symbolic URL Administrator screen, and you must also
edit the application configuration and Actuate Report Server files. The necessary changes are
detailed in the following sections.
Business Component Modifications for the My Jobs View

1 Within Siebel Tools, navigate to the RS Jobs Business Component.
2 Create a new calculated field on the Business Component to hold the symbolic URL:
■ Name: MyJobs
■ Calculated: True
■ Calculated Value: “MyJobs"
Business Component Modifications for the 'My Reports' View

1 Within Siebel Tools, navigate to the ‘RS Files Folders' Business Component.
■ Name: MyReports
■ Calculated Value: "MyReports"

Business Component Modifications for the 'Personal Profile' View

1 Within Siebel Tools, navigate to the 'RS Personal Settings' Business Component.
■ Name: PersonalProfile
■ Calculated Value: “PersonalProfile"
Applet Modifications for the 'My Jobs' Applet

1 Create a copy of the 'RS Jobs Applet' applet and change the following properties:
■ Name: My Jobs Applet
■ Class: CSSSWEFrameReportPortlet
2 Delete the existing control and create a new control. The control should have the following
properties:
■ Name: MyJobs
■ Field: MyJobs
■ Field Retrieval Type: Symbolic URL
Accept the default values for the rest of the properties.
3 Right-click on the 'My Jobs Applet' and navigate to the 'Edit web layout' page.
4 Remove 'ReportsServerJobsPage' from the page and drag and drop the 'MyJobs' field.
5 Save the changes.
Applet Modifications for the 'My Reports' Applet

1 Create a copy of the 'RS Files Folders Applet' applet and change the following properties:
■ Name: My Reports Applet
properties:
■ Name: MyReports
■ Field: MyReports
■ Field Retrieval Type: Symbolic URL
Accept the default values for rest of the properties.
3 Right-click on 'My Reports Applet' and go to 'Edit web layout' page. Remove
'ReportsServerFilesPage' from the page and drag and drop the 'MyReports' field.
4 Save the changes.

Applet Modifications for the 'Personal Profile' Applet

1 Create a copy of the 'RS Personal Settings Applet' and change the following properties:
■ Name: Personal Profile Report Applet
properties:
■ Field: PersonalProfile
■ Field Retrievel Type: Symbolic URL
Accept the default values for rest of the properties
3 Right-click on 'Personal Profile Report Applet' and navigate to the 'Edit web layout' page. Remove
'ReportsServerPersonalPage' from the page and drag and drop the 'PersonalProfile' field.
4 Save the changes.
Compiling Changes
1 Navigate to Tools > Compile Projects.
2 Compile all objects that were modified during the course of this configuration. In this example,
all changes were made to objects belonging to the 'Report Server' project.
Siebel Application Administration Changes

1.Navigate to Site Map > Administration - Integration > WI Symbolic URL List > Symbolic URL
Administrator.
Symbolic URL for 'My Jobs'
1 Create a new Symbolic URL called "MyJobs" with the following values:
■ Name: MyJobs
■ URL: http://rshost/acweb/selectjobs.do
■ Host Name: The location of your Report Server
■ Fixup Name: OutsideApplication
■ Multivalue Treatment : Comma Separated
■ SSO Disposition: Form Redirect

2 Create Symbolic URL Arguments for ‘MyJobs’, as detailed in the following table:
Append Substitu
Required Argument Argument as te in Seq
Name Argument Type Value Argument Text #
locale N Field Data Language Y N 1

Code
PreloadUrlPerSes Y Command TRUE Y N 1

sion
PreloadUrl Y Command http://rshost/ Y N 1

sswebapp/
logout.jsp
rsUserID Y Field RS Username Y N 1
anyName Y Command PostRequest Y N 1
volume Y Field Volume Name Y N 1
timeZone N Field Timezone Y N 1
rsPassword Y Field RS Password Y N 1
serverURL Y Field Server URL Y N 1
To create a Symbolic URL for 'My Reports

1 Create a new Symbolic URL called “My Reports” with the following values:
■ Name: MyReports
■ URL: http://rshost/acweb/getfolderitems.do

2 Create the following Symbolic URL Arguments for 'MyReports:
Required
Argumen Argumen Argument Append as Substitute Seq
Name t t Type Value Argument in Text #

Code

sion

Required
Argumen Argumen Argument Append as Substitute Seq
Name t t Type Value Argument in Text #

sswebapp/
logout.jsp

To create a Symbolic URL for 'PersonalProfile'

1 Create a new Symbolic URL called "PersonalProfile" with the following values:
■ URL: http://rshost/acweb/options.do
2 Create the following Symbolic URL Arguments for 'PersonalProfile':
Required Argument Argument Append as Substitute Seq

Name Argument Type Value Argument in Text #

Code

sion

sswebapp/
logout.jsp

Required Argument Argument Append as Substitute Seq

Name Argument Type Value Argument in Text #
Siebel Configuration File Changes

Actuate support for FireFox can be configurable from the [SWE] section in the application
configuration files.
To enable Admin menus, set the parameter EnableReportforFireFox = TRUE in the application
configuration file.
Report Server Changes

You must make some changes to the Actuate Report Server files to support FireFox.
1 Extract Reports.zip into $\..\Actuate7\ActivePortalJSP.
2 Restart the Reports Server.
Test Changes and Verify Results

1 Log into the Siebel application.
2 Select admin reports from the Reports drop-down list.
3 Select 'My Jobs' or 'My Reports' or 'Personal Profile'.
The Admin view opens in a pop-up window.
About the Administration Views
My Jobs View
Actuate Server maintains status information about background run requests (also called background
jobs). To view this information, click the "My Jobs" button and browse for the jobs.
My Jobs has four options:
■ Choose Schedules to see the jobs that will run at a later date and time.
■ Choose Pending to see the jobs that are in the process queue.
■ Choose Running to see the jobs that are running.
■ Choose Completed to see jobs that have been processed.
Users will only see the jobs that they have scheduled in this view. Jobs scheduled by other users are
not visible.

Job Process Flow

As a job progresses from one state to another, it moves to the corresponding page. A submitted job
appears first in Scheduled. When a job enters the queue, it moves to Pending. When a job executes,
it moves to Running. When the Actuate Server System finishes processing a job, the job moves to
Completed. A job remains in the Completed queue until it is deleted.
Getting Detailed Information About a Job

Users can see the job detail of a particular job by clicking the "Details" icon in the right corner of
each job entry in each page. Clicking this icon displays "Name of the report", "Owner", Report
Executable information and Output information.
Canceling a Scheduled Job

Use the following procedure to cancel or delete jobs before the Actuate Server processes them.
1 Choose My Jobs.
2 Choose Schedules.
3 Click the "Details" icon for the report you want to delete.
4 Click the "Delete Schedule" button.
5 Click the "HERE" link to navigate to the default page for "My Jobs".
Deleting a Job from the Completed Queue

Use the following procedure to delete a job from the completed queue.
1 Click on "My Jobs".
2 Click on Completed.
3 Click the "Details" icon for the job you want to delete.
4 Click the "Delete Job" button.

5 Click the "HERE" link to navigate to the default page for "My Jobs".
My Reports
My Reports provides links to the folders and files that users can access in the Report Server. It
displays the contents of the current folder, as shown in the following screen shot. On this page, users
can open previously-generated reports and can access their version numbers by clicking the version
link.
Getting Detailed Information About a Report

Users can see the details of a particular Report by clicking the "Details" icon in the right corner of
each report entry in each page.
Deleting a Report
Use the following procedure to delete a report.

1 Choose My Reports.
2 Click the "Details" icon for the report that you want to delete.
3 Click on the combo box in the new page and select "Delete".
4 Click the "OK" button.
Personal Profile View

This view manages personal information, such as the mail id and the home folder and it is also used
for sending an email notification that a job has succeeded or failed. This view contains two tabs,
General and Notification.
General: Under this tab, users can set the personal mail id for a user.
Notification: Under this tab, users can set an email notification about the success or failure of a job.

Use the procedures in this section to install and configure ACR 327.
Symbolic Strings
Within Siebel Tools, lock the "Symbolic Strings" project, and create new records in the Symbolic
String Locale based on the data included in the file in the Symbolic Strings folder. This file is included
in the Bulk Orders Installation Toolkit.
SIF Files
The following .sif files are required to create the Bulk Orders objects. These files are included in the
Bulk Orders Installation Toolkit.
■ Table_BulkRequest.sif
■ SIS_OM_Base_Architecture.sif
■ Order_Entry.sif
■ CUT_Siebel_Communications.sif
■ ABO_Bulk_Request.sif
■ ABO_Bulk_Request_UI.sif
■ Product Selection UI.sif
Within Siebel Tools, import the .sif files, in the order listed above, into their respective projects.

For Table Bulk Request.sif, after you have imported the file, click the Apply button on the table
objects.
Project Name Table Name
Table BulkRequest S_BR_ACTION
Table BulkRequest S_BR_ACTN_SET
Table BulkRequest S_BR_EXCPTN
Table BulkRequest S_BR_INST
Table BulkRequest S_BULK_REQ
Table BulkRequest S_ORDER_ACTNSET
Seed Data Details - List of Values

List of values are required as part of the Bulk Orders installation. You can create the LOVs by using
the import utility, dataimp, based on the files provided in the LOV\LOV_Dat folder of the Bulk Orders
Installation Toolkit. Import "BulkRequestLOV_base_78.dat" and "BulkRequestLOV_ENU_78.dat"
before importing the other language specific files.
Optionally, you can create the LOV entry based on the following instruction. The language specific
values are included in the LOV folder of the Bulk Orders Installation Toolkit.
In Administration - Data > List of Values, create the following LOV entry:
Language-
Independent
Type Display Value Code Language Name Order
FS_ORDER_TYPE Bulk Request Bulk Request English-American 20

Template Order Template Order
The following tables list the order types that need to be added. In the client application, navigate to
Site Map > Administration - Data > Orders > Order Types, and add the following values:
■ Order Type: Bulk Request Template Order
■ Type Code: Sales
Create LOV-Type first in Administration - Data > List of Values Explorer > List of Values -Type applet,
create the following types:
■ ABO_BR_ACTSET_TYPE
■ ABO_BR_EXCEPTION_TYPE
■ ABO_BR_HEADER_STATUS
■ ABO_BR_SUBMIT_STATUS
■ ABO_BR_ACTION_CODE

The following table contains a list of LOV's and their values. In the client application, navigate to Site
Map > Administration - Data > List of Values, and add the following values. The Display Value and
the Language Independent Code value will be same and the Language Name will be English-American
for all the LOV values.
LOV Name Value OrderValue
ABO_BR_SUBMIT_STATUS Processed 1
ABO_BR_SUBMIT_STATUS Error 2
ABO_BR_SUBMIT_STATUS To Process 3
ABO_BR_SUBMIT_STATUS Partially 4
Processed
LOV Name Value Order
ABO_BR_HEADER_STATUS New 1
ABO_BR_HEADER_STATUS Pending 2
ABO_BR_HEADER_STATUS Queued 3
ABO_BR_HEADER_STATUS Processing 4
ABO_BR_HEADER_STATUS Partially 5
Complete
ABO_BR_HEADER_STATUS Complete 6
ABO_BR_HEADER_STATUS Cancel Pending 7
ABO_BR_HEADER_STATUS Cancelled 8
ABO_BR_EXCEPTION_TYPE Action Set 1
ABO_BR_EXCEPTION_TYPE Action 2
ABO_BR_EXCEPTION_TYPE Instance 3
ABO_BR_EXCEPTION_TYPE Instance Action 4
ABO_BR_ACTSET_TYPE New 1
ABO_BR_ACTSET_TYPE Modify 2
ABO_BR_ACTSET_TYPE Upgrade 3

ABO_BR_ACTION_CODE Add 1
ABO_BR_ACTION_CODE Update 2
ABO_BR_ACTION_CODE Delete 3
ABO_BR_ACTION_CODE Suspend 4
ABO_BR_ACTION_CODE Resume 5
ABO_BR_ACTION_CODE Upgrade 6
LOV Name Value
UINBOX_INBOX_TYPE BULK REQUEST
Seed Data Details - Universal Inbox

1 Navigate to Site Map > Inbox Administration > All Inbox Types.
2 Add a new record with the following values:
■ Name: Bulk Request Exception
■ Business Object Name: ABO Bulk Request
■ Category: BULK REQUEST
■ Action Type: UINBOX_STATUS_TYPE
3 Navigate to the Views tab and add a new record with the following values:
View: ABO Bulk Request Exceptions List View
4 Add a new record with the following values:
Name: Bulk Request Status
■ Business Object Name: ABO BulkRequest
■ Category: BULK REQUEST
■ Action Type: UINBOX_STATUS_TYPE
5 Go to the Views tab and add a new record with the following values:
View: ABO Bulk Request Users Actions View
6 Navigate to Administration > Server Configuration > Enterprises > Synchronize, and click the
Synchronize button.
7 Navigate to Administration > Server Configuration >Servers-> Components-> Parameters,

query for "Order Management - Enable Asset Based Ordering" and set Value, Value on Restart
and Default Value to True.

New Workflows
The workflows that you need to import in order to configure Bulk Orders are included in the Bulk
Orders Installation Toolkit.
NOTE: Ensure that the new projects are imported and that the new .srf has been applied to the
server before you import and activate the workflows.
In order to deploy the workflows, either:
■ Import all workflows into Siebel Tools and deploy them. Then, in the client, navigate to Site
Map > Administration - Business Process > Workflow Deployment, and then activate these
workflows.
■ In the client application, from the site map, navigate to Administration - Business Process >
Workflow Deployment >Active Workflow Process > Menu >Import Processes. In the pop up
applet, select the relevant workflows in the following order mentioned:
1 ABO Bulk Request ABO Bulk Request -Validate

Process.xml
2 ABO Bulk Request ABO Bulk Request - Cancel

Process Workflow.xml
3 ABO Bulk Request ABO Bulk Request - Add Sub-

4 ABO Bulk Request ABO Bulk Request - Delete Sub-

5 ABO Bulk Request ABO Bulk Request - Modify Sub-

6 ABO Bulk Request ABO Bulk Request - Suspend/

Resume Sub-Process
Workflow.xml
7 ABO Bulk Request ABO Bulk Request - Upgrade

Sub-Process Workflow.xml
8 ABO Bulk Request ABO Bulk Request - Process

Action Sub-Process
Workflow.xml
9 ABO Bulk Request ABO Bulk Request - Prepare

Action Set Sub-Process
Workflow.xml
10 ABO Bulk Request ABO Bulk Request - Notify User

Sub-Process Workflow.xml
11 ABO Bulk Request ABO Bulk Request - Submit

12 ABO Bulk Request ABO Bulk Request - Submit

Driver Process Workflow.xml

13 ABO Bulk Request ABO Bulk Request - Clear

Exception Sub-Process
Workflow.xml
14 ABO Bulk Request ABO Bulk Request - Clear

Exception Process Workflow.xml
15 ABO Bulk Request ABO Bulk Request - Reset
Process Sub-Process
Workflow.xmll
16 ABO Bulk Request ABO Bulk Request - Reset

17 ABO Bulk Request ABO Bulk Request Add Item

Customize SubProcess.xml
18 ABO Bulk Request ABO Bulk Request Add Item

Customize Process.xml
19 ABO Bulk Request ABO Bulk Request Import

Workflow.xml
20 ABO Bulk Request ABO Bulk Request - Edit Order

Line Item.xml
After activating the workflows the runtime events should be reloaded. Navigate to Site Map >
Administration - Application > Runtime Events > Events, query for SubEvent "*ABO*" from the menu
drop-down list, and choose to reload runtime event for each of the runtime events.
System Preferences
Navigate to Site Map > Application Administration > System Preferences, and edit the following:
Name: Bulk Request Template Version
Value: 0
After you have edited this system preference, bounce the server.
New Views
The following lists the new views created for the ABO Bulk Request. In the client application, navigate
to Site Map > Administration - Application > Views, and add the views listed below to the appropriate
responsibilities. Then, assign responsibility to the appropriate users. You must log out and then log
back in to see the Bulk Request screen.
■ ABO Bulk Request Action Set Orders View
■ ABO Bulk Request Exceptions List View
■ ABO Bulk Request List View
■ ABO Bulk Request Users Actions View

■ ABO Order Item Drill Down View

ACR331 includes backporting of the Siebel applications version 8.0 Web Service features. Besides
the binary patches, the following repository/seed data changes are required before using the Web
Services.
The Sample Code.zip file contains sample code for you to code Web Services.
If you are not using the Web services, then the following procedure is not required.
There are two zip files, ACR331ImportFilesApps.v1205.zip and ACR331ImportFilesCore.zip. Thse

files are located under the Tools\REPPATCH directory.
Applying Repository Changes to the EAI Infrastructure

Under "sif files" folder in the zip file, there are two folders, hor (horizontal) and sia. You will import
files based on your environment. The following is the list of sif files to be imported:
Symbolic Strings
1 In the Tools.cfg file, change the SymStrPrefix parameter from "X_" to "SBL_".
2 Within Siebel Tools, import the "Symbolic_Strings_New_1.sif" and

"Symbolic_Strings_New_2.sif" files.
3 In the Tools.cfg file, change SymStrPrefix back to "X_".
DLLs
1 Within Siebel Tools, import the "BS_State_WS_Wiz_Dlls.sif" and "IO_Wiz_DLL_New.sif" files.
Classes
■ Within Siebel Tools, import the "BS_State_WS_Wiz_Classes.sif", and "IO_Wiz_Class_New.sif"
files.
Business Services
1 Within Siebel Tools, import the "EAI BusComp State Service.sif", "IO_Wiz_Svc_New.sif", "Web
Service Deployment Service.sif", and "IO_XML_Conv_Svc_Changed.sif" files.
2 After you have imported all of the .sif files, compile the following projects:
■ EAI Business Services
■ EAI Design
■ Web Service
■ EAI Converter Services

The following table contains the files delivered with this ACR:
Module Name Web Service Name Operations
Configurator ProductConfigurator GetCfgObjectStructure
GetCfgObjectGroupItems
GetCfgObjectDefaultGroupItems
Catalog CatalogWebService GetCatalogs
GetCatalogCategories
GetCategoryProducts
GetSearchParameters
GetSearchOptions
PublishCatalog
ExecuteSearch
GetRelatedPromotion
GetProductDetails
GetProductAttributeDomain
GetProductChildren
Quote and Order ContextServiceWrapper ValidateQuotes

Service
ValidateQuoteItems
EligibilityCompatibility CheckQuoteEligibilityCompatibility
ProductRecommendatio GetRecommendedProductsForQuote
n
QuoteAddItemsWS AddQuoteItems

Module Name Web Service Name Operations
ABO (Asset-Based Ordering) CalculatePriceWS CalculatePrice

AutoOrder
ABOWebService SubmitOrder
AutoAsset
ModifyAssetToQuote
ModifyAssetToOrder
SuspendAssetToQuote
ResumeAssetToQuote
SuspendAssetToOrder
ResumeAssetToOrder
DisconnectAssetToQuote
DisconnectAssetToOrder
Sif Files and Seed Data Instructions

After unzipping the file, you should see this file together with the following directories:
■ Sif files: Sif files with the UI_FREEZE tag in the project level.
■ Sif files without UI_FREEZE tag: Sif files without the UI_FREEZE tag in the project level.
■ Seed data: Workflows, variable maps, and Web Services.
The "sif files" and "sif files without UI_FREEZE tag" directories are basically the same; the only
difference is the UI_FREEZE tag. Some repositories do require having the UI_FREEZE tag. Please try
the "sif files without UI_FREEZE tag" directory first, and if you encounter a UI_FREEZE issue, then
switch to the "sif files" directory. You should only install from one of the directories. Under each
directory, there are two subdirectories, hor (horizontal) and sia. You will import files based on your
environment, and should import and merge all files. These files are detailed in the following table:
Name HOR/SIA Comments
Product_Data_Services_Project_HOR.sif HOR Existing project. Product Data Service

Project - include the whole project
Product_Data_Services_Project_SIA.sif SIA Existing project. Sia differs from HOR

on the address link in the Buscomp.
SIA uses CUT Address.
Catalog Category (Content HOR/SIA New

Management).sif
782_Web_Channel_Order_Management_ HOR New

HOR.sif

Name HOR/SIA Comments
782_Web_Channel_Order_Management_ SIA New. Sia differs from HOR on the

SIA.sif address link in the Buscomp. SIA uses
CUT Address.
ContextServiceWrapper (directory) HOR/SIA New. Sif files for

ContextServiceWrapper
ProductConfigurator (directory) HOR/SIA New. Sif files for Product Configurator
BO_PDS Asset.sif HOR/SIA Existing. Fix for PDS Asset (ABO

related)
After you have imported all of the .sif files, compile the following projects:
■ Product Data Services
■ Content Management
■ Web Channel Order Management
■ SIS OM Base Architecture
■ Cfg WebChannel
■ Cfg RTC
■ ISS Context
■ ISS Order Management
Seed Data
There are three directories under the seed data folder. There are no sia/hor differences.
Variable Maps: Import the variable maps into the Administration - Order Management Screen >
Variable Maps. Refer to the Siebel Bookshelf for more information about the import process. Variable
maps are sorted under the Web Service names, as shown in the following table:
WS Name (Directory) Variable Map Name Comments
ProductRecommendation Default_Product_Recommen Existing(Default Product

dation_Variable_Map- Recommendation Variable Map-
Context.xml Context)
Default_Product_Recommen New
dation_Variable_Map-
Row_Set.xml
CatalogWebService Product Eligibility and New. Used to check Product Eligibility

Pricing Variable Map - Row and Pricing
Set - Basic.xml

WS Name (Directory) Variable Map Name Comments
CalculatePriceWS Default Pricing Variable Map Existing(Default Pricing Variable Map

- Context.xml - Context)
Default Pricing Variable Map Existing(Default Pricing Variable Map

- Row Set.xml - Row Set)
EligibilityCompatibility Default Eligibility Variable Existing (Default Eligibility Variable

Map - Context.xml Map - Context)
Default Eligibility Variable Existing (Default Eligibility Variable

Map - Row Set.xml Map - Row Set)
Signals
The following signal needs to be modified:
Name: Product Recommendation Signal
Import the variable maps into the Administration - Order Management Screen > Signals. First, lock
the Signal by click on the "Locked Flag" on the top applet. Nothing changes in the root level. In the
parameter (child) view, add the last line in the following table (in bold font):
Name Value
CPScope Component
RowScope Current
SubPSPPricingWFName Basic Pricing Procedure
VariableMap 1 Default Product Recommendation Variable Map - Context
VariableMap 2 Default Product Recommendation Variable Map - Row Set
Workflows
Workflows have been put into subdirectories based on the related Web Services Names, as shown in
the following table:
Workflow Names (add

Web Service Name (Directory) .xml as file) Comments
CatalogWebService Check Product Eligibility & New

Pricing
Web Channel Check New, please import after

Eligibility & Pricing Driver "Check Product Eligibility &
Workflow Pricing"

Workflow Names (add

Web Service Name (Directory) .xml as file) Comments
ContextServiceWrapperService Verify Header (Quote) Existing
Verify Header (Order) Existing
Verify Item (Order) Existing
Verify Item (Quote) Existing
ContextServiceWrapperServi New
ce-QuoteItem-Verify
ce-QuoteHeader-Verify
ce-OrderItem-Verify
ce-OrderHeader-Verify
EligibilityCompatibility Web Channel Product New

Eligibility & Compatibility
Driver Workflow
ProductRecommendation Product Recommendation Existing

Get Recommended Products
Product Recommendation Existing

Driver Workflow
Web Channel Product New

Recommendation Driver
Workflow
CalculatePriceWS Web Channel Pricing Driver New

Workflow
QuoteAddItemsWS Web Channel Quote Add New, please import after "Web
Default Items Channel Pricing Driver
Workflow"

ABOWebService SIS OM Apply Completed Modified1

Service Order Line Item to
Service Profile
SIS OM Edit Complex Asset New1

Workflow - Contact - WS
SIS OM Edit Complex Asset New1

Workflow - WS
SISOMAutoAssetWebService New1
SISOMAutoOrderWebService New1
SISOMDisconnectWebService- New1
Order
SISOMDisconnectWebService- New1
Quote
SISOMModifyWebService- New1
Order
SISOMModifyWebService- New1
Quote
SISOMResumeWebService- New1
Order
SISOMResumeWebService- New1
Quote
SISOMSubmitWebService New1
SISOMSuspendWebService- New1
Order
SISOMSuspendWebService- New1
Quote
1. See the note in the following paragraph about warning error messages that you may receive while
importing the ABO workflows.
Web Services
Each file matches one of the Web Services in the delivery list. QuoteWebService.xml corrects a
problem with QuoteWebService. Import the files them into Administration - Web Services Screen >
Inbound Web Services.
NOTE: For all the ABO workflows, during import, you may see this following warning: Sub-Process
Step 'Submit Sub Process' uses a workflow that is not a service flow. It is not allowed to invoke a
non-service flow from a service flow (the parent workflow of this step). When you validate
"SISOMModifyWebService-Order", you will see the following warning/error message text: Sub-
Process Step 'Get Active Doc for Contact' uses a workflow that is not a service flow. It is not allowed
to invoke a non-service flow from a service flow (the parent workflow of this step).

Please ignore these warnings. If you perform validation on the SISOM workflows, you will receive
similar error messages, which you can also ignore.
When you deploy the workflow, you will see the following error message: “This is an invalid workflow.
You are advised to run the validator before you deploy. Do you still want to deploy anyway?” Click
Yes to proceed with the deployment.
Unzip the ACR331ImportFilesApps_v1205 file (it should unzip to the “Import Files” directory). Under
the directory, locate the document named “ACR331_Backporting_COM_Import_Document.doc.”
Follow the instructions in the document and import all of the repository and seed data changes.
1 Unzip the ACR331ImportFilesCore.zip file, and follow the instructions document contained in the
file.
2 Unzip the ACR331ImportFilesv7Apps.zip file, and follow the instructions document contained in
the file. Note that you must import the ACR331ImportFilesCore.zip file before you import the
ACR331ImportFilesv7Apps.zip file.
Instructions for ACR 346A

The following section contains information about how to install ACR 346A on Windows and on UNIX.
Installing Hummingbird SearchServer 6.0 on Windows

You can install Hummingbird SearchServer 6.0 from the third-party directory of the Siebel network
image. For more information about creating Siebel network images, see the Siebel Installation
Guides for the operating system you are using. For information about which versions of the Windows
operating system are supported by Hummingbird SearchServer, see Siebel System Requirements
and Supported Platforms on Oracle Technology Network.
To install Hummingbird SearchServer 6.0 on Windows

1 In Windows Explorer, navigate to the Siebel image location for the current software version such
as D:\Siebel_Install_Image\7.7.2.0, and then navigate to the third party directory where the
Hummingbird SearchServer installer is located.
2 Double-click setup.exe.
The Hummingbird installation screen appears with list of options. Click the Install Search Server
option. Setup then prepares the InstallShield Wizard used to install the software.
3 Accept the license agreement, and then in the SearchServer 6.0 Setup dialog box, enter the
serial number information listed in the table below:

ectory location, or click Browse to select your own location. When you have chosen your
Hummingbird SearchServer Serial Number
Operating
System License Key
Microsoft Windows KPJJKS-BKDKB-T4KQ-MZBHG2-MBCBJ-RF

2000/2003
default directory, click Next.
NOTE: You are not required to change the default location to your Siebel server installation
directory. Please accept the default directory location, unless you do not have disk space.
4 In the Select Components dialog box, accept the defaults, and then click Next.
5 In the Hummingbird SS Servlet Runner Setup Options dialog box, accept the default port number,
and then click Next.
6 In the JDBC Driver Port Selection dialog box, accept default, and then click Next.
7 Upon completion of SearchServer 6.0 setup, click Finish.
NOTE: For an environment where you have all operations running from one machine, or do not
have a client connector set up, you do not need to have any of the Services running.
To determine what Hummingbird SearchServer version is currently installed, from the

Hummingbird SearchServer installation directory, open the command prompt and run the
following command:
>D:\Hummingbird\SearchServer60\bin>ftcin -9
Installing Hummingbird SearchServer 6.0 on UNIX

NOTE: This is not currently supported on AIX because of a known third-party issue.
The Hummingbird SearchServer 6.0 server can run on a HP-UX or Solaris computer. You can install
Hummingbird SearchServer 6.0 from the installation directory on your Siebel network image. For
more information about creating Siebel network images, see the Siebel Installation Guides for the
operating system you are using.
In order to use Siebel Search, you must edit the library path variable in the Siebel script used for
setting the environment variables (siebenv.csh or siebenv.sh) so that the library variable includes
the Hummingbird library path. For example, you would edit the library path in the script as follows:
■ For Solaris: setenv LD_LIBRARY_PATH /export/home/fulcrum/lib:$LD_LIBRARY_PATH
■ For HP-UX: setenv SHLIB_PATH /export/home/fulcrum/lib:$SHLIB_PATH
If you do not edit the library path as shown above, and source the new Siebel script before you start
the Siebel servers, you may not be able to access the Search Indices View or any valid Search
Categories in Search Center.

The following instructions pertain to installing Hummingbird on UNIX.
The license key listed in the table below will be required during the SearchServer installation. Make
sure you have it available when you perform installation.
NOTE: To perform any of the tasks in this chapter, you must log in to the system using the same
administrator login ID that you used when performing the Siebel Server installations
Hummingbird SearchServer License Key
Operating System License Key
Solaris/HP-UX KPJJKS-BKDKB-T4KQ-MZBHG2-
MBCBJ-RF
To install Hummingbird SearchServe 6.0 on UNIX

1 Create a directory to install Hummingbird, then navigate to the Siebel image location for the
current software version such as D:/Siebel_Install_Image/7.8.1.0, and then navigate to the
directory where the Hummingbird installer is located.
For more information about creating Siebel network images, see the Siebel Installation Guide for
the operating system you are using.
2 Run install executable:
./install.sh
The Hummingbird installer script will run.
3 Type in the values displayed in bold as follows:
************************************
* Search Server 6.0 UNIX Installer *
************************************
1. View readme
2. Install SearchServer
3. Exit
**
Choose selection and press [ENTER]: 2
************************************
* Enter valid product license key: *
************************************
KPJJKS-BKDKB-T4KQ-MZBHG2-MBCBJ-RF (this is the SearchServer +

DatabaseBaseTextReader license key)

*******************************
* Choose destination location *
*******************************
Enter the path or press [d]+[ENTER] to use the default one
Default path:
/home/Hummingbird/SearchServer60
**
==>Enter your desired hummingbird installation locale here, for example:/export/

home/SearchServer60
*********************
* Select components *
*********************
Do you want to install SearchServer? [y/n]+[ENTER]
**
==>: y
*********************
* Select components *
*********************
Do you want to install Database Text Reader? [y/n]+[ENTER]
**
==>: y
**
Copying files...
**
**
Files have been copied successfully. Press any key+[ENTER] to continue.
**
[Enter]
************************************
* Search Server 6.0 UNIX Installer *

************************************
1. View readme
2. Install SearchServer
3. Exit
Choose selection and press [ENTER]:3

Use the following procedure to implement ACR 347 for Personalized Content Delivery.
1 Navigate to the REPPATCH folder, and unzip the ACR347RepSeedFiles_v782.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.
2 Open the tools.cfg file and change the SymStrPrefix parameter from X_ to SBL_.
3 Save and close the tools.cfg file.
4 Navigate to the tools\REPPATCH\ACR\Repository folder.
5 Right-click on Import.bat and choose edit.
6 Change PCDTOOLSPATH to point to the folder in which Siebel Tools is installed.
7 Change PCDDATASRC to Local if you are importing .sif files to the local Siebel Tools database.
8 Change PCDUSERNAME and PCDPASSWORD to the user name and password used to log into
Siebel Tools.
9 Save and close the file.
10 Open the PROJECTS_TO_LOCK file in Notepad.

11 Log into Siebel Tools and check out the projects listed in the file.
12 Add new projects as detailed in the file and lock these projects.
13 Log out of Siebel Tools.
Import.bat will import the .sif files to merge these object changes.

Use the following procedures to implement ACR 372.

Tools.cfg
1 In tools.cfg, change the SymStrPrefix = X_ parameter to SymStrPrefix = SBL_
2 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
Text
New/Modify Name Join Column Length Type
New Field Common S_PROD_INT_LS COM_DEV_ 50 DTYPE_TEXT

Name X NAME
LS Medical PI Product Business Component

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

Single Value Fields
New/ Text
Modify Name Join Column Length Type
New Field Common S_PROD_INT_LSX COM_DEV_NAME 50 DTYPE_TEXT

Name
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:
LS Medical Product
Project Issue
Table S_PRD_CMPLNT_LS
Single Value Fields
New/Modify Name Column Text Length Type
New Field Combo Product COMB_PROD_FL 1 DTYPE_BOOL

G
New Field STN Number PRD_SUB_TRAC 30 DTYPE_TEXT

K_NUM
New Field PMA Number PRE_MKT_APPL_ 30 DTYPE_TEXT

NUM
New Field Type of Report - SEVEN_DAY_RPT 1 DTYPE_BOOL

7-day Flag _FLG
New Field Type of Report - THIRTY_DAY_RP 1 DTYPE_BOOL

30-day Flag T_FLG

LS Medical Product Issue RR Business Component

Update the existing "LS Medical Product Issue RR" Business Component by adding new fields, as
shown below:
LS Medical Product
Project Issue
Single Value Fields
Text
New/Modify Name Column Length Type
New Field Combo Product COMB_PROD_FLG 1 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 Type of Report - SEVEN_DAY_RPT_FLG 1 DTYPE_BOOL

7-day Flag
New Field Type of Report - THIRTY_DAY_RPT_FLG 1 DTYPE_BOOL

30-day Flag
LS Medical Related Product Issue Business Component

Update the existing "LS Medical Related Product Issue" Business Component by adding new fields,
as shown below:
LS Medical Product
Project Issue
Single Value Fields
Text
New Field Combo Product COMB_PROD_FLG 1 DTYPE_BOOL
New Field STN Number PRD_SUB_TRACK_NUM 30 DTYPE_TEXT
New Field PMA Number PRE_MKT_APPL_NUM 30 DTYPE_TEXT

Single Value Fields
Text
New Field Type of Report - SEVEN_DAY_RPT_FLG 1 DTYPE_BOOL
7-day Flag
New Field Type of Report - THIRTY_DAY_RPT_FLG 1 DTYPE_BOOL

30-day Flag
Symbolic Strings
Current String
New/Existing Name 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 Disability or Disability or

MANENT_DAMAGE Permanent Permanent
Damage Damage
New SBL_LS_MPI_CONGENITAL_ANOM Congenital Congenital

ALY_BIRTH_DEFECT Anomaly or Birth Anomaly or Birth
Defect 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

■ 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
Read
New/Modify Name Field Only String Reference
New Common Common TRUE SBL_LS_MPI_COMMON_NAME

Name Name
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 List Item In Edit Web Layout, drag and drop this List
Name 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)

Control (New)
HTML HTML
Name String Reference Caption Field Icon Map Type
Common SBL_LS_MPI_COMMON_NAME Common Common Text

Name Name Name
Applet Web Template
Edit Edit Applet Form Grid

Layout
Applet Web Template Item (New)
Name Control Expression Type Comments
Common Name Common Siebel Life Control In Edit Web Layout, drag and
Name Science 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
LS Medical Product Issue 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 Disability or

ERMANENT_DAMAGE Permanent Damage
OE Congenital Congenital SBL_LS_MPI_CONGENITAL_ANO Congenital Anomaly

Anomaly Flag Anomaly MALY_BIRTH_DEFECT or Birth Defect
OE Other Other SBL_LS_MPI_OTHER_SERIOUS Other Serious

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

Issue (SSE)
Controls (These are all new controls)
HTML
Icon
Name String Reference Caption Field Map HTML Type
STN SBL_LS_MPI_STN_NUMBER STN # STN Number Text

Number
PMA SBL_LS_MPI_PMA_NUMBER PMA/ PMA Number Text

Number 510(k)#
Combo SBL_LS_MPI_COMBO_PRO Combo Combo CHECK Checkbox

Product DUCT Product Product
Type of SBL_LS_MPI_7-DAY 7-day Type of CHECK Checkbox

Report - 7- Report - 7-
day Flag day Flag

Report - Report - 30-
30-day day Flag
Flag
Applet Web Template
Web
Name Type Template
Edit Edit Applet Form

Grid Layout
Applet Web Template Item (New)1
Combo Product Combo Control

Product
STN Number STN Number Control


PMA Number PMA Number Control
Type of Report - 7- Type of Control

day Flag Report - 7-
day Flag
Type of Report - Type of Control

30-day Flag Report - 30-
day Flag
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

RR Issue (SSE)
Control (Label Changes)
Old
Name Caption String Reference Caption
OE Disability Flag Disability SBL_LS_MPI_DISABILITY_OR_PERMA Disability or

NENT_DAMAGE Permanent
Damage
OE Congenital Congenita SBL_LS_MPI_CONGENITAL_ANOMALY Congenital

Anomaly Flag l Anomaly _BIRTH_DEFECT Anomaly or Birth
Defect
OE Other Other SBL_LS_MPI_OTHER_SERIOUS 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

RR Issue (SSE)
Controls
(These
are all are
new
controls)
HTML HTML
Name String Reference Caption Field Icon Map Type
STN SBL_LS_MPI_STN_NUMBER STN # STN Text

Number Number
PMA SBL_LS_MPI_PMA_NUMBER PMA/ PMA Text

Number 510(k)# Number
Combo SBL_LS_MPI_COMBO_PRODU Combo Combo CHECK Checkbox

Product CT Product Product

Report - 7- Report -
day Flag 7-day
Flag

Report - Report -
30-day 30-day
Flag Flag
Applet Web Template
Edit Edit Applet Form Grid

Layout

Combo Product Combo Control

Product
STN Number STN Number Control
PMA Number PMA Number Control
Type of Report - 7- Type of Control

day Flag Report - 7-
day Flag
Type of Report - Type of Control

30-day Flag Report - 30-
day Flag
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 Type of Report - 7-

day Flag
New Type of Report - 30-

day Flag
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.
2 From the site map, navigate to Application Administration screen > Data Map Administration.
3 Query for "LS Medical PI Create Related PI" and "LS Medical PI Populate Report - 3500A".
4 Add the new Data Map Fields as shown below:
Data Map Object
Destination
Source Business
Name Business Object Object
LS Medical PI Create LS Medical LS Medical

Related PI Product Issue Related
Product
Issue
Data Map Component
Source Destination
Business Business
Name Component Component
Product Issue LS Medical LS Medical Related

Product Issue Product Issue
Data Map Field (These are all new field maps)
Source Type Source Destination Type Destination
Field Combo Field Combo Product

Product
Field STN Number Field STN Number
Field PMA Number Field PMA Number
Field Type of Field Type of Report - 7-day Flag

Report - 7day
Flag

Report - 30-
day Flag

Data Map Object
Source
Business Destination Business
Name Object Object
LS Medical PI LS Medical LS Medical Product Issue

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

Issue Product Issue
RR
Data Map Field (All are new field maps)
Destination
Source Type Source Type Destination
Field Combo Field Combo Product

Product
Field STN Number Field STN Number
Field PMA Number Field PMA Number

Report - 7day
Flag
Report - 30-
day Flag
Instructions for ACR 373B

The following section 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 Address-
Left-Hand-Side (LHS) to access a user's 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.
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:
System-Wide
Parameter
Section Parameter Value
Calendar UserMailBoxIDSource EMAILLEFT
System-Wide
Parameter
Calendar Exchange Server Map S
S Exchange Server ExchPIMSI01
S UserMailBoxIDSource EMAILFULL
Server-wide Calendar Exchange Server

parameter Map
S Exchange Server
S UserMailBoxIDSour
ce

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.
Use the following steps to edit and run the script:
1 Open the script in edit mode in any text editor.
2 Grep ServiceUserName = "QA\qauser".
3 Update it to appropriate domain and admin user (domain\admin).
4 Save the file.
To run the script:
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).

The following section contains information about how to implement ACR 382.
Disabling MQ Reports in Siebel MQ Transport

The MQ series server generates several reports based on different conditions such as errors,
exceptions, or acknowledgements. In Siebel implementations, these reports are sent to the same
queue on which the original message was put. In certain cases, it is desirable to suppress the report
generation, and hence EAl MQ Transport now allows a configuration for no report generation. EAI MQ
Transport currently enables the following report options by default:
■ MQRO_EXCEPTION_WITH_DATA
■ MQRO_EXPIRATION_WITH_DATA
■ MQRO_PAN
■ MQRO_NAN
Use the following procedure to implement the report disabling option for Siebel MQ Transport:
1 Set the EAI MQSeries Server transport parameter FullMQMDControl to TRUE.
2 Add the header MQMD_S_In_Report with value "MQRO_NONE" to the SendReceive() method of
EAI MQSeries Server Transport.
For more information about how to pass parameters and headers to EAI MQSeries Server Transport,
refer to the Siebel Bookshelf documentation, and search for Transports and Interfaces: Siebel
Enterprise Application Integration.

For information about how to configure ACR 389, see Oracle MetaLink 3 at https://
metalink3.oracle.com and search for Doc ID 758061.1.


For information about how to configure ACR 391, see Integration Platform Technologies: Siebel
Enterprise Application Integration on the Siebel Bookshelf for version 7.8 on OTN at http://
download.oracle.com/docs/cd/B31104_02/homepage.htm.

Use the following procedure to implement this fix.
1 Query for "Correspondence Template Pick Applet" in the Applet Objects.
2 Edit the Search Specification property for this applet as [SalesFileExt]='doc' OR

[SalesFileExt]='lwp' OR [SalesFileExt]='LWP' OR [SalesFileExt]='DOC' OR
[SalesFileExt]='DOCX' OR [SalesFileExt]='docx'
3 Compile the .srf.
Configuration Instructions for FR 12-1OH3BN4

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

2 Select the Exchange Calendar profile.
3 Create a record with the following values:
❏ Section: Archive
❏ Parameter: ArchiveGracePeriod
❏ Value: 5 (in days)

Configuration Instructions for FR 12-1OH3BM7

This feature enhances SSSE to allow ExtractStartDate to be specified on a per-user basis. The
following section contains instructions for enabling this feature.
2 Select the Siebel profile, as shown in the following table:
System default Siebel ExtractStartDate 01/01/1980

parameter
User specific UserLevelExtractStart RBROWN 12/20/1996

parameter Dates
UserLevelExtractStart MSTERN 01/04/2008
Dates
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
❏ Value: MM/DD/YYYY
Configuration Instructions for FR 12-1OH3BOC

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.
1 Go to Administration > Server Configuration > Enterprise > System Alerts.
2 Create an alert definition (such as Administrator Email Alerts) with the following alert
parameters:
Alert Definition
Name Alias Media Description
Administrator Email AdminEmailAlert EmailNotification

Alerts
3 Create alert parameters as described in the following table:
Parameter Name Value
SMTPServer 64.181.243.112
SMTPServerPort 25
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 Description
Email Template: MsgBody1 Body of the email

Domain Name with place holders.
The supported place
holders are:
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: MsgBody2 ...Add email body as

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

Section Parameter Value Description
Email Template: MsgBody1 \n SSSE fails to

IPM.Task synchronize
%domain% record for
the sync enabled user
%login% \n
The record has the

following
characteristics \n
Subject: [Subject]
Start Date: [Start

Date]
End Date: [Due Date]
\n The error
Email Template: MsgBody2 %ErrorMessage%

IPM.Task
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.
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-1OH3BL9

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.
2 Click on Job Templates.
3 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)
4 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.
2 Click on Jobs.
3 Click New.
4 Click on Component/Job and select Refan.
5 Click Go.

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.
2 Navigate to Tools Options and click on Lock Project.
3 Navigate to Table and search for S_SD_PIM_ROW.
4 Go to Column.
5 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.
6 Apply the changes for the table.
To configure the Business Component

1 Navigate to Business Component and search for the PIMSI PIM row
2 Navigate to the field.

3 Right-click on the field and click on New Record.
4 Set the name as "Cal Repeat Pattern".
5 Click on Column and select the "X_CAL_REPEAT_PATTERN" created previously.
6 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].

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.
2 Go to Administration – Integration.
3 Go to Data Map Editor (Integration Object Map).
4 Select "PIMSI Calendar Outbound Map" in Data Map Editor.
5 Right-click on "PIMSI Calendar Outbound Map".
6 Click Copy Record (Ctrl + B).
7 Name the new record "PIMSI Calendar Outbound Refan Map".
8 Select this new entry.
9 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.

This section provides an understanding of how to use collations to get the expected results while
running a query for strings that contain the Turkish i/I (i-dot) character with the Microsoft SQL Server
and Oracle databases.
The following table details the functionality provided by ACR 427. A “Yes” in the cell means that the
corresponding record will display.

Same Database
Turkish Org Non-Turkish Org
Data First Letter Query: i* Query: I* Query: i* Query: i* Query:i* Query: I*

Description
istanbul Upper, Dotted Yes Yes
India Upper, Non- Yes Yes Yes Yes

Dotted
india2 Lower, Dotted Yes Yes Yes Yes
iabcde Lower, Non- Yes Yes

Dotted
Oracle Database
For the Oracle database:
Mention
ORACLE_NLS_UPPER=XTURKISH
or
ORACLE_NLS_UPPER=XTURKISH_CI under the [Siebel] section.
MSSQL Database
For the MSSQL database:
For Turkish OMs, mention
MSSQL_COLLATION=TURKISH_CI
or
MSSQL_COLLATION=TURKISH_CI_AI under the [Siebel] section.
For non-Turkish OMs:
Mention MSSQL_COLLATION=SQL_Latin1_General_CP1_CI_AS under the [Siebel] section.
Configuration File Details

For the Oracle DB, the [Siebel] section in the configuration file will look like:
[Siebel]
ORACLE_NLS_UPPER= XTURKISH

OR
[Siebel]
ORACLE_NLS_UPPER= XTURKISH_CI
For Turkish OM and MSSQL server, the [Siebel] section in the configuration file will look like:
[Siebel]
MSSQL_COLLATION = TURKISH_CI_AI
OR
[Siebel]
MSSQL_COLLATION = TURKISH_CI
For non Turkish OM and MSSQL server, the [Siebel] section in the configuration file will look like:
[Siebel]
MSSQL_COLLATION = SQL_Latin1_General_CP1_CI_AS
The Siebel server component has to be restarted for the settings to take effect.


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 for version 7.8 on OTN at http://
download.oracle.com/docs/cd/B31104_02/homepage.htm.
Use the instructions in the following procedure to implement ACR 428.
1 Go to the Siebel Tools installation directory \REPPATCH\ACR428.
2 Unzip the ACR428.zip file.
This will create the following directory structure:
\REPPATCH\ACR428\
The folder that you create will contain the following subfolders:
❏ \DMGSchemaChanges
❏ \Seed Data
❏ \SifFiles
❏ \WebTemplate
❏ \WF
❏ \LMU
❏ \ACR428_78211fp_addendum
The following instructions refer to the folders specified above.
3 Apply the schema changes to the Server Database from the DMGSchemaChanges folder using
the instructions below:
The DMGSchemaChanges folder contains the Barcelona_schema_changes.sif file. This file

contains the following tables:
New table:
❏ S_PRO_CFG_ITEM
Modified tables:
❏ 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 Barcelona_schema_changes.sif file into the
repository.
a Before you import the Barcelona_schema_changes.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
b Use the Siebel Tools - Import from Archive function to read the Barcelona_schema_changes.sif
file and create the tables in the repository. The "merge" option should be used while importing
this file.

c To create the Barcelona_schema_changes.siftable 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.
4 Import Seed Data from the SeedData folder using the following procedure:
a 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.
b Navigate to the System DSN tab, and click Add.
c Select the "Siebel Oracle90" driver (from Datadirect Technologies).
d Enter a data source name, such as DevelopmentDB.
e Enter the server name to connect to. For Oracle, enter the TNS service name that you created
to connect Siebel Tools to the database.
f Test your connection and click OK when tested successfully.
g 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.
5 Run the following command if you are an ENU customer:
a <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.
b Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the
import completed successfully.
c After importing, the seed data from \REPATCH\ ACR428\SeedData folder, import seed data from
\REPATCH\ ACR428\ACR428_78211FP_addendum\SeedData folder provided in the file

seed_barcelona.dat using the input file seedupg_barcelona_imp.inp provided in the same
folder using the command
<Tools Install Directory>\bin\dataimp /u SADMIN /p sadmin /f <Tools Install
Directory>\REPATCH\ ACR428\ACR428_78211FP_addendum\SeedData\seed_barcelona.dat
/l <Tools InstallDirectory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table
Owner> /I <ToolsInstal lDirectory>\REPATCH\
ACR428\ACR428_78211FP_addendum\SeedData\seedupg_barcelona_imp.inp /q -1 /w y /e
n /t n /x R /n 100 /h log

6 Use the following procedure to import seed date if you are using a language other than ENU:
a 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.
b 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.
c 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.
7 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.
8 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
9 In Siebel Tools, lock all the following projects:
❏ CMU Billing BC
❏ MACD Performance
❏ Order Entry
❏ Picklist
❏ Price List
❏ Pricer
❏ Product
❏ 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.
a 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
b From the \REPATCH\ ACR428 \ACR428_78211FP_addendum\SIFFiles folder, import the rest of

the SIF files into Siebel Tools using the Tools àImport From Archive function.
If you have not locked the required projects, you may receive a warning error message.
Make sure to choose Merge Option in Siebel Tools Import Wizard.
Import the following SIF files:
❏ ModifiedApplets.sif
❏ ModifiedBC.sif
❏ ModifiedBS.sif
11 The following steps are only necessary for customers who are installing languages other than
ENU:
a Select Tools > Utilities > Locale Management to import LMU Files for the specific language from
the LMU folder into Siebel Tools.
b Select Source Language = English American.
c Target Language = <Specific Language>.
d 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 Billing Integration
CMU Adjustment View Sub Process New CMU Billing Integration
CMU Contact Sync Workflow New CMU Billing Integration
CMU Profile Sync Workflow New CMU Billing Integration
CMUBalanceDetailsEventAdjustmentWF New CMU Billing Integration
CMUEventDetailsAdjustmentWF New CMU Billing Integration
CMUEventDetailsQueryWF New CMU Billing Integration
CMUInvoiceAdjustmentWF New CMU Billing Integration
CMUInvoiceQueryWF New CMU Billing Integration
CMUItemChargeAdjustmentWF New CMU Billing Integration
CMUItemChargeQueryWF New CMU Billing Integration
Pricing Procedure - Calculate Net Price Modified Row Set Transformation

Toolkit
SIA External Integration Process New CMU Billing Integration
SIS OM Active Order Sub-Process Modified SIS OM Base Architecture
SIS OM Active Quote Sub-Process Modified SIS OM Base Architecture
SIS OM Add Order Service Charge Sub- New CMU Billing Integration
Process
SIS OM Add Quote Service Charge Sub- New CMU Billing Integration
Process
SIS OM Disconnect Asset Sub-Process Modified SIS OM Base Architecture

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

Process
SIS OM Modify Products & Services Modified SIS OM Base Architecture

Process

Workflow Name New/Modified Project
SIS OM Move Process (Updated for Modified SIS OM Base Architecture

nested service bundle changes)
SIS OM New Products & Services Process Modified SIS OM Base Architecture
SIS OM Suspend / Resume Asset Sub- Modified SIS OM Base Architecture

Process (Updated for nested service
bundle changes)
SIS OM Suspend / Resume Products & Modified SIS OM Base Architecture

Services Process
SIS OM UpdateOrderItem New CMU Billing Integration

SIS OM Submit Order Process Modified SIS OM Base Architecture
SIS OM Order Line Item Update New CMU Billing Integration

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

(New workflow for nested service bundle
changes)
SISOMBillingSubmitOrderWebService New CMU Billing Integration
SIS OM NSB Update Order Line (New New CMU Billing Integration
workflow for nested service bundle
changes)
SIS OM Edit Complex Asset Workflow Modified SIS OM Base Architecture

(Updated workflows for nested service
bundle changes)
SIS OM Edit Delta Quote Line Item Modified SIS OM Base Architecture
bundle changes)
SIS OM Edit Service Order Line Item Modified SIS OM Base Architecture
bundle changes)
CMU SIA Submit Adjustment Request to New CMU Billing Integration

External
a Select Workflow Process in Siebel Tools Object Explorer.

b Right-click on the right-side pane 'Workflow Processes' and import the .xml file into Siebel Tools
from the workflows folder. Refer to the list of workflows in the table above to know which project
these workflows need to be imported into.
c Check the status of the Workflow process. If it is In-Progress, then make it complete by
deploying the Workflow process 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.
d Repeat Step b and Step c for of all the workflows in the folder.
e Log in to the Siebel application as an administrator.
f Navigate to the Site Map.
g Click on Administration - Business Process.
h Navigate to Workflow Deployment ' Repository Workflow Process.
i Query for the workflow processes and activate.
17 Modify the run time events for promotions:

a Navigate to the Administration - Runtime Events screen.
b Click on the 'Action Sets' view. This shows three applets.
c In the first applet, called 'Action Sets', search for the Action Set 'Cache Refresh BC - ISS
Promotion Pricing Components List Applet'.
d For this Action Set, in the bottom form applet, there is a control with the 'Business Service
Context' label. For this control, the current value previously was only "ISS Promotion Pricing
Components", "ISS Promotion Pricing Rules Summary". Another new entry was added to this and
now the value for this control is "ISS Promotion Pricing Components", "ISS Promotion Pricing
Rules Summary", and "Promotion Config Item". (Note that there should be a space after the
comma.)
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.
2 Navigate to the Site Map.
3 Click on Administration - Web Service >Outbound Web Services.
4 Query for the Name= *ABCS*.
Five records will appear.
5 Navigate to the Service Ports list applet and change the URI provided by the ABS team.
6 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*
2 Query for Name = CMU Account Update.
3 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.
4 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.

2 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
3 After enabling the necessary components, navigate to Site Map > Administration - Server
Configuration > Enterprises > Synchronize.
4 Select all the records and click the Synchronize button.
Windows
1 Log in to the machine with the credentials.
2 From Start - Run, type cmd.
3 Find the drive that the build is installed on.
4 Type <Build>ses\siebsrvr\bin.
5 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>
6 Run the command to verify how many components are enabled for "list of compgrp".
7 Run the following command to enable the components group:
Enable compgrp <Alias>
8 After you run the Enable compgrp <Alias> command, verify that the command run was
successful, and then run the Exit command.
9 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
1 From the local machine click on Stat - Run- type telnet <Machine name> ex:telnet sdcpi43
2 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.)
3 Navigate to <Build>ses\siebsrvr\bin.

4 Run the following commands:
smgr <enter>
set server <machine name> <enter>
list compgroup <enter>
5 Run the following command to enable the components group:
Enable compgrp <Alias>
6 Verify that the command run displays correctly.
7 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.

To implement ACR 432, set the environment variable "SEBLCL_TRACESINGLEINST" to 1 on the
Mobile Web Client.
Expected Result: Launch an instance of Mobile Web Client. When you try to open another instance,
instead of opening a new instance, the system should display the "One Siebel Instance is already
running" error message.

To access the configuration instructions and BPEL files for ACR 460, the Oracle On Demand and Siebel
CRM On Premise integration enhancement, see Doc ID 815193.1 on Oracle MetaLink 3 at
https:metalink3.oracle.com.
Please note the following known issue related to ACR 460.
Bug ID 763268: When users toggle between synchronization statuses and then update the record,
their updates are not synchronized.

To access the configuration instructions for ACR 471, see the Siebel Order Management Guide
Version 7.8, Rev. B. This guide is available on the Siebel Bookshelf at http://www.oracle.com/
technology/documentation/siebel.html.


Use the following instructions to configure ACR 481.
NOTE: For more information about SSSE, see the Siebel Server Sync Guide, Version 7.8, Rev. B. This
guide is available on the Siebel Bookshelf at http://www.oracle.com/ technology/documentation/
siebel.html.
Configuration Changes for the Validation and Record Skipping Feature

Use the following procedure to enable/disable the Record Skipping feature.
To enable/disable the Record Skipping feature

1 Navigate to Administration-PIMSI Integration >Configuration.
2 Navigate to Profile > Siebel.
3 Create the following section:
SyncState Always Save Syncstate Y
Configuring the Attendee Tracking Feature

Use the following procedure to configure the Attendee Tracking feature.
To configure the Attendee Tracking feature

1 Navigate to Administration - PIMSI Integration > Configuration > PIM Server Integration
Configuration > Configuration.
2 In the Siebel profile, create the following section parameters:
Siebel AddAttendee Y (or N)
NOTE: The default value is Y, so with no user configuration, the system will perform Attendee
Tracking.
Configuring the Contact Matching Feature

Use the following procedure to configure the Contact Matching feature.

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ What Does ACR 483
Provide?
To configure the Contact Matching feature

1 Naviagate to Administration - PIMSI Integration > Configuration > PIM Server Integration
Configuration > Configuration.
2 In the Siebel profile, create the following section parameters:
Siebel IgnoreContactMatching TRUE (or FALSE)
NOTE: The default value is False, so with no user configuration, the system will perform contact
matching.
Instructions for Oracle BI Publisher Enhancements

Use the instructions in this topic to implement ACR 483, which integrates Oracle Business
Intelligence Publisher (Oracle BI Publisher) report functionality with Siebel Business Applications.
The topics include:
■ What Does ACR 483 Provide? on page 221
■ Requirements for ACR 483 on page 222
■ Roadmap for Implementing Oracle BI Publisher Enhancements on page 222
■ Installing Oracle BI Publisher for Siebel Business Applications on page 223
■ Copying JAR Files to the Oracle BI Publisher Server on page 225
■ Process of Implementing Siebel Fix Pack 7.8.2.14 on page 226
■ Process of Configuring Scheduling and Parameterization for Oracle BI Publisher Reports on page 235
■ Copying JAR Files to the Oracle BI Publisher Server on page 225
■ Configuring the Siebel Mobile Client to Generate Oracle BI Publisher Reports on page 247
■ Testing Your ACR 483 Configurations on page 248
NOTE: It is recommended that after fulfilling the requirements for this ACR, you execute the
instructions in the order presented.
What Does ACR 483 Provide?

ACR 483 integrates Oracle Business Intelligence Publisher (Oracle BI Publisher) report functionality
with Siebel Business Applications. After fulfilling the requirements and tasks described in these
instructions, you can execute Oracle BI Publisher reports from the Siebel application.
You work with Oracle BI Publisher reports in the following locations:

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Requirements for ACR 483
■ In the Siebel application views to generate, schedule, and view reports. The views are also used
for Siebel application administration tasks and report administration, such as modifying existing
reports, creating new reports, purging reports, and so on.
For more information about using and administering reports, see Siebel Reports Administration
Guide on Siebel Bookshelf for Oracle’s Siebel Business Applications Version 8.1 (http://
www.oracle.com/technology/documentation/siebel.html) on Oracle Technology Network (OTN).
■ In Microsoft Word by using Oracle Business Intelligence Publisher Add-in for Microsoft Word (also
known as Oracle BI Publisher Desktop) to create and customize layout templates.
For information about using Oracle BI Publisher Desktop, see Oracle Business Intelligence
Publisher Report Designer's Guide in the Oracle Business Intelligence Publisher Documentation
Library 10.1.3.4 available on Oracle Technology Network (OTN). However, be aware that not all
features mentioned in this documentation are currently supported in Siebel Business
Applications.
■ In Oracle BI Publisher to manage report scheduling, report users, and other Oracle BI Publisher
administration tasks.
Requirements for ACR 483

Note the following requirements for implementing ACR 483:
■ You must have a qualified Siebel CRM version 7.8.2 base release installed and configured on your
machine (Siebel Server, Gateway Server, Siebel Web Server, Siebel Tools, and Siebel Mobile Web
Client).
■ Make sure the following component groups are enabled on the Siebel Server:
■ Enterprise Application Integration (EAI)
■ Siebel Remote
■ The applicable Siebel AOM (Application Object Manager), for example, SCCObjMgr_enu for
Siebel Call Center
■ Make sure the Siebel Server is running and the Siebel Mobile Web Client and Siebel Tools can
connect to the server data source.
Roadmap for Implementing Oracle BI

Publisher Enhancements
To use Oracle BI Publisher reports in Siebel CRM version 7.8.2, you must install and configure Oracle
BI Publisher in addition to configuring your Siebel application.
To implement the Oracle BI Publisher enhancements for ACR 483, perform the following processes
and tasks:
1 “Installing Oracle BI Publisher for Siebel Business Applications” on page 223
Perform this task to install Oracle BI Publisher for the first time.

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installing Oracle BI
Publisher for Siebel Business Applications
2 “Copying JAR Files to the Oracle BI Publisher Server” on page 225
Perform this task to copy custom Java classes (Java ARchive [JAR] files) associated with
individual reports. By default, these Java functions are not available on the Oracle BI Publisher
Server.
3 “Process of Implementing Siebel Fix Pack 7.8.2.14” on page 226
Perform the tasks in this process to integrate Oracle BI Publisher report functionality with your
Siebel application.
If you plan to implement report scheduling and parameterization, continue on to the next step.
If not, proceed to Step 5.
4 (Optional) “Process of Configuring Scheduling and Parameterization for Oracle BI Publisher Reports”
on page 235
Perform the tasks in this process if you want to use report scheduling and parameterized reports.
NOTE: This is an optional step for using Oracle BI Publisher reports. However, it is recommended
that you perform this step to utilize the full suite of Oracle BI Publisher report features and
functionality available for Siebel Business Applications.
5 “Securing User Access to the Oracle BI Publisher Server” on page 242
Perform the appropriate configuration task to secure access to the Oracle BI Publisher Server.
The security models available for your use are based on whether or not you implement report
scheduling and parameterization in your deployment.
6 “Configuring the Siebel Mobile Client to Generate Oracle BI Publisher Reports” on page 247
Perform this task if you want to generate reports from the Siebel Mobile Web Client.
Installing Oracle BI Publisher for Siebel

Business Applications
To use Oracle BI Publisher report functionality with Siebel Business Applications, you must install the
following:
■ Oracle Business Intelligence Publisher version 10.1.3.4.1
OC4J (Oracle Application Server Containers for Java Platform, Enterprise Edition) is installed as part
of this installation. For more information about OC4J, see Oracle Business Intelligence Publisher
Installation Guide, Release 10.1.3 available at Oracle Technology Network (OTN).
The Oracle BI Publisher Server is also installed as part of this installation. During report
generation, which is triggered from the Siebel application, data is pushed from the Siebel
Database to the Oracle BI Publisher Server to generate reports. When handling a report request,
the Oracle BI Publisher Server merges the data with the report template from the Oracle BI
Publisher repository, and then sends the report to the Siebel application.

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installing Oracle BI
Publisher for Siebel Business Applications
■ Oracle BI Publisher Add-In for Microsoft Word (also known as Oracle BI Publisher Desktop)
version 10.1.4.3.1
Oracle BI Publisher Desktop is a report authoring tool, which allows you to author and preview
layout templates using Microsoft Word.
This task is a step in “Roadmap for Implementing Oracle BI Publisher Enhancements” on page 222.
NOTE: You can install the Oracle BI Publisher software any time before or after the Siebel Server
installation.
To install Oracle BI Publisher for Siebel Business Applications

1 Log in to Oracle E-Delivery available at:
http://edelivery.oracle.com
2 Choose a language, or click Continue to download with English (US) as the default language.
3 Enter the export validation information, accept the license terms and export restrictions, and
then click Continue.
4 Select Oracle Business Intelligence as the product pack and an operating system (for example,
Microsoft Windows (32-bit)). Then click Go.
NOTE: You must select an operating system compatible with the computer on which the Oracle
BI Publisher Server is installed. For information about which platforms are supported for Siebel
Reports, see Siebel System Requirements and Supported Platforms on Oracle Technology
Network.
5 Select the Oracle Business Intelligence 10.1.3 Media Pack for your operating system, and then
click Continue.
For example, you might select Oracle Business Intelligence (10.1.3) Media Pack for Microsoft
Windows (32-bit).
6 Download the Oracle BI Publisher 10.1.3.4.1 installers. For example, if you chose Oracle Business
Intelligence (10.1.3) Media Pack for Microsoft Windows (32-bit) in Step 5, you download the
following:
■ Oracle Business Intelligence Publisher Enterprise 10.1.3.4.1 for Microsoft Windows.
■ Oracle Business Intelligence Publisher Desktop 10.1.3.4.1 for Microsoft Windows.
NOTE: Typically administrators download and install Oracle BI Publisher Desktop (also
known as Oracle Business Intelligence Publisher Add-in for Microsoft Word) during the Oracle
BI Publisher Enterprise installation, however, you can install it any time.
NOTE: The titles and part numbers for the installers differ depending on the operating system
you selected in Step 4.
7 Install Oracle BI Publisher by doing the following:

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Copying JAR Files to the
Oracle BI Publisher Server
a Decompress the installer into a directory of your choice.
If you chose Oracle Business Intelligence (10.1.3) Media Pack for Microsoft Windows (32-bit)
in Step 4, you decompress the V16384-01.zip file.
CAUTION: You must extract the .zip file to a directory whose name does not contain any
spaces. If the directory name contains spaces, the installation fails.
b Follow the instructions provided in Installing BI Publisher into Oracle Application Server for OC4J
10.1.3.1 in Oracle Business Intelligence Publisher Installation Guide, Release 10.1.3 available at
Oracle Technology Network (OTN).
NOTE: OC4J is installed and the Oracle BI Publisher Server starts automatically as part of
this installation.
8 Install Oracle Business Intelligence Publisher Add-in for Microsoft Word (also known as Oracle BI
Publisher Desktop) by doing the following:
a Decompress the appropriate .zip file according to the Media Pack you chose in Step 4.
For example, if you chose Oracle Business Intelligence (10.1.3) Media Pack for Microsoft
Windows (32-bit) in Step 5, you decompress the V16380-01.zip file.
CAUTION: You must extract the .zip file to a directory whose name does not contain any
spaces. If the directory name contains spaces, the installation fails.
b Run the installer.
9 Make sure applicable users install Oracle BI Publisher Desktop on a machine where Microsoft
Word is installed.
Copying JAR Files to the Oracle BI

Publisher Server
After installing Oracle BI Publisher, you must copy custom Java classes (Java ARchive [JAR] files)
associated with individual reports to the Oracle Application Server installation directory. By default,
these Java functions are not available on the Oracle BI Publisher Server.
To copy JAR files to the Oracle BI Publisher Server

1 Copy the following files from the SIEBSRVR_ROOT\CLASSES directory to the
<OracleAS_HOME>\j2ee\home\applications\xmlpserver\xmlpserver\WEB-INF\lib directory,
where OracleAS_HOME is the Oracle Application Server:
■ XSLFunctions.JAR
■ SiebelCustomXMLP.JAR
■ SiebelCustomXMLP_SIA.JAR
NOTE: JAR files are the standard functions used in reports. If there are additional custom Java
extensions, you must perform this step for those JAR files as well.

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Process of Implementing
Siebel Fix Pack 7.8.2.14
2 Enable the external file references:
a Log in to the Oracle BI Publisher Server with administrator privileges.
b Click the Admin tab, and then select Runtime Configuration and Properties.
c Change the default value for the Disable External Reference attribute to FALSE, click Apply, and
then verify the changes were made.
3 Restart OC4J by doing the following:
a Select Start, Programs, and then Oracle - BIPHomeX (where X is a system-assigned number
when you install Oracle BI Publisher).
b Choose Start BI Publisher.
Process of Implementing Siebel Fix Pack

7.8.2.14
This topic provides instructions for integrating Oracle BI Publisher report functionality with your
Siebel application. In this process, you apply Siebel Fix Pack 7.8.2.14 and then perform several
configuration tasks.
This process is a step in “Roadmap for Implementing Oracle BI Publisher Enhancements” on page 222.
To implement Siebel Fix Pack 7.8.2.14, perform the following tasks:
1 “Extracting Siebel Fix Pack 7.8.2.14” on page 227
2 “Applying Repository and Schema Changes” on page 227
3 “Applying Seed Data Changes” on page 228
4 “Activating the XMLP Components” on page 229
5 “Enabling the XMLP Components on the Siebel Server” on page 231

6 “Configuring the Outbound Web Service to the Oracle BI Publisher Server” on page 232
7 (Optional) “Associating Oracle BI Publisher Reports with Siebel Views” on page 233
8 “Copying Fonts for Report Generation” on page 233
9 (Optional) “Working with Oracle BI Publisher and Actuate Reports Concurrently” on page 234
10 (Optional) “Enabling Logging for the Oracle BI Publisher Server” on page 234
NOTE: If you want to use report scheduling and parameterized reports, you must perform additional
configuration. For configuration tasks specific to report scheduling and parameterization, see
“Process of Configuring Scheduling and Parameterization for Oracle BI Publisher Reports” on page 235.

Extracting Siebel Fix Pack 7.8.2.14

This topic describes how to extract Siebel Fix Pack 7.8.2.14. This extraction provides the required
directories and files for integrating Siebel Business Applications with Oracle BI Publisher.
This task is a step in “Process of Implementing Siebel Fix Pack 7.8.2.14” on page 226.
To extract Siebel Fix Pack 7.8.2.14

1 From the SIEBEL_TOOLS_ROOT\REPPATCH directory on the machine where you installed Siebel
Tools, decompress and extract one of the following files to the same directory:
■ SEA_ACR483RepSeedFiles_v78.zip for Siebel Cross-Industry Applications
■ SIA_ACR483RepSeedFiles_v78.zip for Siebel Industry Applications
An ACR483 folder is created in the REPPATCH directory with the following subfolders:
■ REPORTS
■ REPOSITORY
■ SEED_DATA
2 Change the SymStrPrefix parameter by doing the following:
a Navigate to the SIEBEL_TOOLS_ROOT\BIN\ENU directory, and then open the tools.cfg file in a
text editor.
b In the [Siebel] section, change the value of the SymStrPrefix parameter to SBL_, and then save
the tools.cfg file.
Applying Repository and Schema Changes

This topic describes how to apply repository and schema changes using Siebel Tools.
To apply repository and schema changes

1 Launch Siebel Tools, connecting to the server data source.
2 Lock all the projects listed in the ACR483\REPOSITORY\PROJECTS_TO_LOCK file.
NOTE: If the Table XMLP project is inactive, activate this project by unchecking the Inactive
checkbox.
3 Edit the import.bat file located in the SIEBEL_TOOLS_ROOT\REPPATCH\ACR483\REPOSITORY

directory to provide the following parameters:
■ TOOLSPATH is the Siebel Tools installation directory (SIEBEL_TOOLS_ROOT).
■ UNZIPROOT is the REPPATCH folder in the Siebel Tools installation directory.
■ DATASRC is the database connect string value used by Siebel Tools.

■ USERNAME is the database user name.
■ PASSWORD is the database password.
4 Run import.bat to import the SIF files from all the subfolders in the
REPPATCH\ACR483\REPOSITORY directory, and then save the file. The import might take some
time.
NOTE: Make sure the applicable projects are locked before running the batch file.
5 Import the XMLP Purge Records workflow.
a Launch Siebel Tools, connecting to the server database.
b In the Object Explorer, select Workflow Process.
c In the Workflow Process list, right-click to select Import Workflow Process.
d Browse to select the ACR483\REPOSITORY\Workflow Process\XMLP Purge Records.xml file.
e In the Select Project dialog box, select the XMLP Integration project from the drop-down list, and
then click OK.
6 Examine the log files in the SIEBEL_TOOLS_ROOT\LOG directory to verify the import successfully
completed.
7 Stop the Siebel Server, if it is running.
8 Using Siebel Tools, compile the changes for all projects into an updated SRF by doing the
following:
a From the Tools menu, choose Tools, and then the Compile Projects menu item.
b Select the All projects option.
c Save the SRF in the SIEBSRVR_ROOT\objects\ENU directory as:
❏ siebel.srf for Siebel Cross-Industry Applications
❏ siebel_sia.srf for Siebel Industry Applications
Applying Seed Data Changes

This topic describes how to verify that the necessary tables are in the repository and how to create
these tables in the physical database.
To apply seed data changes

1 Verify the following tables are in the repository:
■ S_XMLP_REPOUTPT
■ S_XMLP_REP_IOBJ

■ S_XMLP_REP_TMPL
■ S_XMLP_RPT_LANG
■ S_XMLP_RPT_VIEW
NOTE: You imported these tables from the ACR483\REPOSITORY\Table directory in Step 4 on
page 228 in “Applying Repository and Schema Changes.”
2 Using Siebel Tools, create these tables in the physical database by doing the following:
a Perform a query to select the five tables listed above, and then click Apply.
b In the Apply Schema dialog box, provide the following information:
❏ From the Tables drop-down list, choose Current Query.
❏ Enter the database user, database user password, and OBDC data source, making sure
the database user has privileges to change the database schema.
c Click Apply to create the tables in the physical database by doing the following:
3 Populate the seed data by doing the following:
a Make sure the dataimp.exe file exists in the SIEBEL_TOOLS_ROOT\BIN directory.
b Navigate to the SIEBEL_TOOLS_ROOT\REPPATCH\ACR483 directory.
c Edit the ACR483\SEED_DATA\import.bat file to set the following parameters to the proper
values:
❏ TOOLSPATH is the Siebel Tools installation path (SIEBEL_TOOLS_ROOT).
❏ DATASRC is the database connect string value used by Siebel Tools.
❏ USERNAME is the database user name.
❏ PASSWORD is the database password.
❏ TBLOWNER is the database table owner.
❏ ADDITIONALLANG is the language locale.

d Run import.bat.
e Review the following log files to make sure the import successfully completed:
❏ SIEBEL_TOOLS_ROOT\LOG\dataimp_seed.log
❏ SIEBEL_TOOLS_ROOT\LOG\dataimp_seed_ENU.log (for English environments)
Activating the XMLP Components

This topic describes how to activate the XMLP components.

To activate the XMLP components

1 In the SIEBSRVR_ROOT\BIN directory, create a new srvrdefs_xmlp.txt file with the following
parameters.
[Component Groups]
XMLPReport = XMLP Report
[Components]
XMLPReportServer = XMLP Report Server
[XMLPReport]
FullName = XMLP Report
Description = XMLP Report Components
CreateDisabled = TRUE
[XMLPReportServer]
FullName = XMLP Report Server
Description = Generates Reports
SvcName = XMLP Driver Service
CompGrp = XMLPReport
FixedParam: Method = GenerateReport
Param: MaxTasks = 20
FixedParam: ConfigFile = siebel.cfg
FixedParam: DataSource = ServerDataSrc
FixedParam: NamedDataSource = ServerDataSrc,GatewayDataSrc
Param: CfgRepositoryFile = siebel$(Vertical_Extension).srf
Param: UnicodeConvError = FALSE
[Named Subsystems]
XMLPJvmSubsys = XMLP Java Business Service Subsystem Parameters
[XMLPJvmSubsys]
FullName = XMLPJvmSubsys
Description = XMLP Java Business Service Subsystem Parameters
SubsysType = JVMSubSys
CLASSPATH = %SiebelRoot%/classes/SiebelXMLP.jar;%SiebelRoot%/classes/
xdoparser.jar;%SiebelRoot%/classes/fix6312772.jar;%SiebelRoot%/classes/
xdocore.jar;%SiebelRoot%/classes/xmlparserv2-904.jar;%SiebelRoot%/classes/
versioninfo.jar;%SiebelRoot%/classes/share.jar;%SiebelRoot%/classes/
jewt4.jar;%SiebelRoot%/classes/jdbc12.jar;%SiebelRoot%/classes/
i18nAPI_v3.jar;%SiebelRoot%/classes/collections.jar;%SiebelRoot%/classes/
bipres.jar;%SiebelRoot%/classes/bicmn.jar;%SiebelRoot%/classes/
siebel.jar;%SiebelRoot%/classes/XSLFunctions.jar;%SiebelRoot%/classes/
SiebelCustomXMLP.jar
where:
■ CfgRepositoryFile is siebel.srf (or siebel_sia.srf for Siebel Industry Applications).

■ CLASSPATH is the XMLP JAR files path.
NOTE: Typically, this path is in the SIEBSRVR_ROOT\CLASSES directory. Make sure the end
of line character for the Classpath is appropriate for your operating system. For example, for
UNIX, replace the semicolon (;) with a colon (:).
CAUTION: An error might occur if the value of the CLASSPATH parameter is too long. To
avoid this, copy the CLASSPATH folder to the root directory, and then point CLASSPATH to
this path.
■ %SiebelRoot% is the Siebel Server root directory.
2 Make sure the Gateway Name Server is running, but the Siebel application server is not.
3 Execute one of the following commands in the SIEBSRVR\BIN directory with the proper values.
■ For Windows:
srvrcfg.exe /g <gateway server:port> /e <entrpr server>

/u <username> /p <password> /r <Siebel Root Dir> /c XMLPReport
/a compgrps,components,NamedSubsystem /i srvrdefs_xmlp.txt
■ For non-Windows:
srvrcfg /g <gateway server:port> /e <entrpr server>

/u <username> /p <password> /r <Siebel Root Dir> /c XMLPReport
/a compgrps,components,NamedSubsystem /i srvrdefs_xmlp.txt
NOTE: If the port number for the Siebel Gateway Name Server is not 2320 (the default), you
must specify the port number. Otherwise, no port number is needed.
4 To verify results, make sure the named subsystem definitions were added to the appropriate .dat
file.
■ For Windows: gtwysrver/ADMIN/siebns.dat
■ For non-Windows: ./sys/siebns.dat
If not, create them using the Siebel Web Client (or Developer Web Client).
Enabling the XMLP Components on the Siebel Server

Use the following procedure to enable the XMLP components on the Siebel Server.
To enable the XMLP components on the Siebel Server

1 Navigate to the Administration - Server Configuration screen, and then the Enterprises view.
2 In the Component Group field, query for XMLP*.
3 Select the XMLP Report component group, and then click Enable.
4 In the Component Group Assignments subview, choose the target Siebel Server, and then click
Assign to assign the component group to this server.

Configuring the Outbound Web Service to the Oracle BI

Publisher Server
Use the following procedure to configure the outbound Web service to the Oracle BI Publisher Server.
To configure the outbound Web service to the Oracle BI Publisher Server

1 Navigate to the Administration - Web Services screen, then the Outbound Web Services view.
2 In the Name field, query and select PublicReportService.
3 Set the address of the service ports of this Web service to the actual address of the Oracle BI
Publisher Server web service, for example:
http://<host.domain>:<port>/xmlpserver/services/PublicReportService
where:
■ host.domain is the full path for your Oracle BI Publisher Server
■ port is the port that the Oracle BI Publisher Server uses
4 In the Operations view, make sure there are some operations, for example, reportLogin and
createReport.
Known Issue
If you have removed the PublicReportService Web service and its related integration objects and then
attempt to create the EAI outbound Web service with the WSDL again, the data type of some of the
integration component fields might be incorrectly set to DTYPE_TEXT. If this occurs, change the data
type for these fields back to DTYPE_ATTACHMENT by doing the following:
1 Log in to Siebel Tools.
2 In the Object Explorer, select the Flat tab, and then click Integration Component Field.
3 In the Name field, perform the following query:
'XLIFFData' or 'documentData' or 'documentOutput' or

'downloadReportInSessionReturn' or 'downloadReportReturn' or 'reportBytes' or
'reportData' or 'reportDataChunk' or 'reportZippedData' or 'templateData'
4 Change the Data Type field of the records to DTYPE_ATTACHMENT (from DTYPE_TEXT).
5 Compile the SRF file and restart the Siebel Server.

Associating Oracle BI Publisher Reports with Siebel

Views
This topic describes how to associate Oracle BI Publisher reports with Siebel views.
NOTE: Some preconfigured reports are available for your use. For a comprehensive list of the
preconfigured reports that ship with Siebel Business Applications, see 876284.1 (Doc ID) on My
Oracle Support.
This task is an optional step in “Process of Implementing Siebel Fix Pack 7.8.2.14” on page 226.
To associate Oracle BI Publisher reports with Siebel views

1 Navigate to the Administration - BIP Reports screen, then the View Association view.
2 In the Views list, select a view with which you want to associate a report.
3 In the Reports List subview, click Add.
4 In the Views dialog box, choose a report name, and then click OK.
The report is now available in the Reports menu when you are in a view with which the report is
associated.
For more information about associating reports with Siebel views, see Siebel Reports Administration
Copying Fonts for Report Generation

Fonts used in reports are obtained from the computer on which the report is generated. If a report
is generated from a computer where the fonts in the report are not available, the output might not
be as expected when trying to generate, view, preview, or schedule reports.
NOTE: It is the responsibility of the report designer to make sure that fonts are selected that match
the data that is likely to be included in a report.
To copy fonts for report generation

■ On the Siebel Server machine where the XMLP Report Server server component is enabled, do
one of the following:
■ For Windows, copy the fonts in C:\WINDOWS\Fonts directory to the $JRE_HOME\fonts

directory
■ For UNIX, copy the fonts in the C:/Fonts directory to the $JRE_HOME/fonts directory
NOTE: This task is typically performed as part of the Siebel Reports installation. However,
administrators can perform this task at any time.

For more information about fonts in Siebel Business Applications, see Siebel Global Deployment
Working with Oracle BI Publisher and Actuate Reports

Concurrently
If you want to work with Oracle BI Publisher reports and Actuate reports concurrently, you must
make sure the ReportEngineType system preference is set to BOTH.
To work with Oracle BI Publisher and Actuate reports concurrently

1 Navigate to the Administration - Application screen, then the System Preferences view.
2 In the System Preference Name field, select ReportEngineType.
3 In the System Preference Value field, type one of the following:
■ BIP if you want only Oracle BI Publisher reports to appear.
■ ACTUATE if you want only Actuate reports to appear.
■ BOTH if you want both Oracle BI Publisher and Actuate reports to appear. This is the default
setting.
Your selection indicates what appears in the Reports menu drop-down list in the Siebel
application.
4 Perform the following:
■ If you plan to use Oracle BI Publisher reports (with or without Actuate reports), there are no
further steps because the reporting engine is active by default.
■ If you plan to use only Actuate reports, disable the XMLP Report Server Component.
Enabling Logging for the Oracle BI Publisher Server

For instructions, see Siebel Reports Administration Guide on Siebel Bookshelf for Oracle’s Siebel
Business Applications Version 8.1 (http://www.oracle.com/technology/documentation/siebel.html) on

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Process of Configuring
Scheduling and Parameterization for Oracle BI Publisher Reports
Process of Configuring Scheduling and

Parameterization for Oracle BI Publisher
Reports
If you plan to use report scheduling and parameterized reports, you must import a special SIF file
(in addition to extracting Siebel Fix Pack 7.8.2.14), and then perform several configuration tasks.
This process is one step in “Roadmap for Implementing Oracle BI Publisher Enhancements” on
page 222.
NOTE: Before performing the tasks in the process, you must have completed the procedures in
“Process of Implementing Siebel Fix Pack 7.8.2.14” on page 226.
To configure scheduling and parameterization features for Oracle BI Publisher reports, perform the
following tasks:
1 “Importing Scheduling and Parameterization Features for Oracle BI Publisher Reports” on page 235
2 “Configuring JVM Settings” on page 236
3 “Configuring User Management for Oracle BI Publisher Reports” on page 238
4 “Configuring Report Scheduling for Oracle BI Publisher Reports” on page 239
5 “Configuring Report Parameterization for Oracle BI Publisher Reports” on page 240
For information about using report scheduling and parameterization, see Siebel Reports
Administration Guide on Siebel Bookshelf for Oracle’s Siebel Business Applications Version 8.1 (http:/
/www.oracle.com/technology/documentation/siebel.html) on Oracle Technology Network (OTN).
Importing Scheduling and Parameterization Features

for Oracle BI Publisher Reports
If you plan to use report scheduling and parameterized reports, you must import a special SIF file
specifically for these features.
This task is a step in “Process of Configuring Scheduling and Parameterization for Oracle BI Publisher
Reports” on page 235.
To import scheduling and parameterization features for Oracle BI Publisher reports

1 Using Siebel Tools, import the 8111FP_new_feature.sif file from the
SIEBEL_TOOLS_ROOT\REPPATCH\ACR483 directory on the machine where you installed Siebel
Tools.
2 Compile the changes to the appropriate SRF file.

Configuring JVM Settings

This topic describes how to configure the JVM settings.
To configure JVM settings

1 Make sure you have JDK version 1.5 or higher installed on the Siebel Server.
2 Review the topic on prerequisites for implementing a Java Business Service (http://
download.oracle.com/docs/cd/E14004_01/books/EAI3/EAI3_EAIJBS3.html) in Siebel Reports
Administration Guide on Siebel Bookshelf for Oracle’s Siebel Business Applications Version 8.1 on
3 In the Siebel Web Client, create an XMLPJVmSubsys profile by doing the following:
a Navigate to the Administration - Server Configuration screen, Enterprises, and then the Profile
Configuration view.
b In the Profile field, query for XMLPJvmSubsys.
Notice the query returns no records.
c Create a new profile with the following values:
❏ Profile is XMLPJvmSubsys
❏ Alias is XMLPJvmSubsys
❏ Subsytem Type is JVMSubSys
❏ Description is XMLP Java Business Service Subsystem Parameters

d Create three profile parameters for this profile and make sure the paths correctly locate the
required files.
For more information on setting the values of the JVM DLL Name and JVM Options
parameters, see the EAI documentation at:
http://download.oracle.com/docs/cd/E14004_01/books/EAI3/EAI3_EAIJBS3.html
Data
Parameter Alias Type Value Description
JVM Classpath CLASSPATH String <SIEBSRVR_ROOT>/ses/ JVM Classpath

siebsrvr/Classes/Siebel.jar;
<SIEBSRVR_ROOT>/ses/
siebsrvr/Classes/SiebelXMLP.jar
CAUTION: An error might occur

if the value of the CLASSPATH
parameter is too long. To avoid
this, copy the CLASSPATH folder
to the root directory, and then
point CLASSPATH to this path.
JVM DLL Name DLL String For Windows: JVM DLL Name
<path to jvm.dll_file>
For AIX, Linux, and Solaris:

<path to libjvm.so_file>
For HP-UX:
<path to libjvm.sl_file>
JVM Options VMOPTIONS String JVM Options
e For UNIX, set environment variables as follows:
❏ JAVA_HOME is /usr/java
❏ LIBPATH ${LIBPATH} is /usr/jdk1.5.0_06/jre/bin/usr/jdk1.5.0_06/jre/bin/j9vm
4 Synchronize the component definitions with the Siebel Gateway Name Server.
a Select the Synchronize view tab, and then click Synchronize.
b Stop the Siebel Server service.
c Stop and restart the Gateway Name Server service.
d Start the Siebel Server service.

Configuring User Management for Oracle BI Publisher

Reports
This topic provides instructions for configuring user management in the Siebel application for ACR
483.
To configure user management for Oracle BI Publisher reports

1 Create an inbound Web service to extract data from the Oracle BI Publisher Server.
a Navigate to the Administration - Web Services screen, then the Inbound Web Services view.
b Import the BIPSiebelSecurityWS.xml file.
c Change the host and port number of the server port’s address to match that of the Siebel
Server.
2 Create new responsibilities and assign users to the responsibilities by doing the following:
a Navigate to the Administration - Application screen, then the Responsibilities view.
b Create the following new responsibilities:
❏ XMLP_ADMIN
❏ XMLP_SCHEDULER
❏ XMLP_DEVELOPER
❏ XMLP_SIEBEL_GUEST
c Assign these responsibilities to users.
3 Navigate to the Administration - Application screen, then the Views view to create a new Report
Job List View view.
4 Associate the XMLP_SCHEDULER responsibility with the Report Job List View view.

Configuring Report Scheduling for Oracle BI Publisher

Reports
This topic provides instructions for configuring report scheduling in the Siebel application.
To configure report scheduling for Oracle BI Publisher reports

1 Create new List of Values (LOVs).
a Navigate to the Administration - Data screen, then the LOV Explorer view.
b Add a new XMLP_RPT_SCHEDULE_MODE type.
NOTE: The Replication Level field is automatically populated to All. Keep the default values
for the other fields.
c Navigate to the List of Values view.
d Create three new LOV records with the following values:
Type Display Value Translate Order
XMLP_RPT_SCHEDULE_MODE Run Immediately Y 1
XMLP_RPT_SCHEDULE_MODE Run Once Y 2
XMLP_RPT_SCHEDULE_MODE Run Daily/Weekly Y 3
NOTE: The display values are now available as choices for the Time field in the Schedule a Report
dialog box. For more information about this field, see topics on scheduling reports in Siebel
Reports Administration Guide on Siebel Bookshelf for Oracle’s Siebel Business Applications
Version 8.1 (http://www.oracle.com/technology/documentation/siebel.html) on Oracle Technology
Network (OTN).
2 Create an inbound Web service to extract data from the Oracle BI Publisher Server.
a Navigate to the Administration - Web Services screen, then the Inbound Web Services view.
b Import the BIPDataService.xml file.
c Query for BIPDataService, and verify there is a BIPDataPort service port with a GetReportData
operation.
d Change the host and port number of the server port’s address to match that of the Siebel
Server.
e Change the Siebel administrator user name and password accordingly.

f Click Generate WSDL and save it as dataservice.wsdl in the Oracle BI Publisher Server bin
directory.
3 Configure the Oracle BI Publisher embedded user interface by doing the following:
a Navigate to the Administration - Integration screen, then the Host Administration view.

b Add a new record with the following values:
❏ Name is host:port (this is the Oracle BI Publisher host and port)
❏ Virtual Name is biphost
c Navigate to the Administration - Integration screen, then the Symbolic URL Administration view
to create a new record with the following values:
❏ Name is BIPReportJobListPage
❏ URL is http://biphost/xmlpserver/servlet/myhistory
❏ Host Name is host:port (the Oracle BI Publisher host address that you choose from a
picklist)
❏ Fixup Name is Default
❏ SSO Disposition is IFrame
d Scroll down to Symbolic URL Arguments to add new records with the following values:
Argument
Name Required Type Argument Value
PreloadURL Yes Command http://biphost/xmlpserver/signout.jsp
PreloadUrlPerSession Yes Command True
anyname Yes Command PostRequest
id Yes Field BIPUser
passwd Yes Field BIPPassword
Configuring Report Parameterization for Oracle BI

Publisher Reports
This topic provides instructions for creating and configuring a new outbound Web service that allows
you to parameterize reports.
To configure report parameterization for Oracle BI Publisher reports

1 Get the latest Oracle BI Publisher WSDL by doing the following:
a Start the Oracle BI Publisher Server.
b Type the following in browser address bar:
http://<host>:<port>/xmlpserver/services/PublicReportService_v11?wsdl

c Save the output as PublicReportService_v11.WSDL to a temporary location on your machine.
2 Remove the existing outbound Web service and related integration objects by doing the
following:
a Log in to Siebel Tools.
b In the Object Explorer, select Business Service.
c In the Business Services list, query for PublicReportService, and then delete it.
d In the Object Explorer, select Integration Object.
e In the Integration Objects list, query for XMLP Integration project, and then select and delete
all the objects.
NOTE: There are approximately 100 (or more) objects.
3 Import the WSDL you saved in Step 1 by doing the following:
a From the Tools menu, choose File, New Object, EAI, and then the Web Service icon, and click OK.
b In the WSDL Import Wizard dialog box:
❏ Select XMLP Integration project.
❏ Browse to the select PublicReportService_v11.WSDL, and then click Next.
c Check the Deploy Integration Object(s) and Proxy Business Service(s) option, and then click
Finish.
NOTE: A PublicReportService_v11.xml file is created in the same folder where the

PublicReportService_v11.WSDL resides. This xml file is what you will select in Step 5 of this
procedure to create a new outbound Web service.
4 Verify the results by doing the following.
a In the Object Explorer, select Business Service.
b In the Business Services list, perform a query where:
❏ Project is XMLP Integration project

❏ Name is PublicReportService
c Check the Business Service user properties to confirm the following:
❏ siebel_port_name is PublicReportService_v11
❏ siebel_web_service_name is PublicReportServiceService
❏ siebel_web_service_namespace is http://xmlns.oracle.com/oxp/service/v11/
PublicReportService
d In the Object Explorer, select Integration Object, and query for the XMLP Integration project.
Approximately 125 (or more) objects appear.
e Compile the SRF.
f Restart the Siebel Server.

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Securing User Access to the
5 In the Siebel Web Client, create and configure a new outbound Web service.
a Navigate to the Administration - Web Service screen, then the Outbound Web Services view.
b In the name field, query for PublicReportServiceService, and then delete this service.
c Click Import, browse to select the PublicReportService_v11.xml file (that you imported in
Step 3), and then click Import.
A new PublicReportServiceService outbound Web service is created.
d With this new PublicReportServiceService web service selected, scroll down to the Operations
subview, and then select all operations records.
e From the application-level menu, choose the Edit menu, the Change Records menu item, and
then perform the following, and then click OK:
❏ In the 1st Field to Change field, select Authentication Type.
❏ In the Value field, type None.
f Verify that the Authentication Type value for all operations are changed to None (from
Username/Password - clear text).
Securing User Access to the Oracle BI

Publisher Server
This topic describes the various security models for authenticating users to the Oracle BI Publisher
Server.
The following models are available for authenticating user access to the Oracle BI Publisher Server
in a Siebel Reports connected environment.
■ BI Publisher Security
■ Siebel Security
■ LDAP
For more information about the Siebel Reports environments, see Siebel Reports Administration
Guide on the Siebel Bookshelf for Oracle’s Siebel Business Applications Version 8.1 (http://

Which model you can use depends on whether or not you plan to implement scheduling and
parameterization for Oracle BI Publisher reports as shown in Table 17.
Table 17. Security Model Options for Authenticating User Access to the Oracle BI Publisher Server
Supports Report
Scheduling and
Security Model Parameterization? For Configuration Instructions, See...
BI Publisher Security1 No “Configuring Security and Authentication Using the

BI Publisher Security Model” on page 243
LDAP Yes2 “Configuring Security and Authentication Using the

LDAP Security Model” on page 244
Siebel Security Yes “Configuring Security and Authentication Using the

Siebel Security Model” on page 246
1. The BI Publisher Security model is the default setting after installing Oracle BI Publisher.
2. LDAP authentication is available whether or not you are implementing report scheduling and parameterization.
To secure user access to the Oracle BI Publisher Server, perform one of the following tasks:
■ “Configuring Security and Authentication Using the BI Publisher Security Model” on page 243
■ “Configuring Security and Authentication Using the LDAP Security Model” on page 244
■ “Configuring Security and Authentication Using the Siebel Security Model” on page 246
Configuring Security and Authentication Using the BI

Publisher Security Model
This topic describes how to implement the BI Publisher Security model to manage user access to the
Oracle BI Publisher Server in a Siebel Reports connected environment.
This task is a step in “Securing User Access to the Oracle BI Publisher Server” on page 242.
By default, when you install Oracle BI Publisher, the security model for the Oracle BI Publisher Server
is set to BI Publisher Security. No additional configuration for the Oracle BI Publisher Server is
necessary.

To implement BI Publisher Security authentication, you specify the user ID and password used to
access the Oracle BI Publisher Server as a parameter for the XMLP Report Server Component. When
the XMLP Report Server Component issues an outbound Web service call to run a report, the Oracle
BI Publisher user ID and password specified for the XMLP Report Server Component are passed as a
parameter (which can be encrypted or in plain text) to be authenticated by the Oracle BI Publisher
Server as the request is processed.
CAUTION: You cannot use the BI Publisher Security model if your deployment supports report
scheduling or parameterized reports. Instead, you must use either the Siebel Security or LDAP
model. For information about configuring the Siebel Security model, see “Configuring Security and
Authentication Using the Siebel Security Model” on page 246. For information about configuring the
LDAP model, see “Configuring Security and Authentication Using the LDAP Security Model” on page 244.
To configure security and authentication using the BI Publisher Security model

1 Log in to your Siebel application.
2 Navigate to Administration - Server Configuration, Servers, and then Components.
3 Query for XMLP Report Server, and then select it.
4 Click the Parameters tab and query for BIP*.
5 Enter the user ID and password used to access the Oracle BI Publisher Server in the Default Value
fields of the BIP Server Login and BIP Server Password parameters.
6 Log out of your Siebel application.
Configuring Security and Authentication Using the LDAP

Security Model
This topic describes how to implement LDAP security adapter authentication to manage user access
to the Oracle BI Publisher Server in a Siebel Reports connected environment.
To implement LDAP authentication for Siebel user access to the Oracle BI Publisher Server, you
implement LDAP authentication for your Siebel application, and you must use the same LDAP
directory for the Oracle BI Publisher Server.
In an implementation using LDAP authentication, an LDAP security adapter provided with Siebel
Business Applications authenticates users against an LDAP-compliant directory. The directory stores
information that is required to allow users to connect to the database and the Oracle BI Publisher
Server and this information is retrieved by the security adapter when users try to run a report. When
users log into a Siebel application that uses LDAP authentication, they are already authenticated for
the current session.
NOTE: Using the LDAP security adapter to connect to a Microsoft Active Directory Server (ADS)
directory has not been certified for use with Oracle BI Publisher.

To implement LDAP authentication for the Oracle BI Publisher Server

1 Configure the LDAP Server by doing the following:
a Make sure there is an XMLP_ADMIN group for the LDAP Server.
b Log in to the LDAP Server.
c Create a new LDAP user with which to authenticate the Oracle BI Publisher Server. For example,
uid=appsuser,ou=people,o=siebel.com, where appsuser is any name of your choice.
d Add this new user to the XMLP_ADMIN group.
e Add users who schedule reports to the XMLP_ADMIN group.
For more information on this step, see the topic on configuring LDAP or ADSI security adapters
using the Siebel Configuration Wizard in Siebel Security Guide.
2 Set the user credentials for the Oracle BI Publisher Server by doing the following:
a Log in to the Oracle BI Publisher Server with administrator privileges, and specify LDAP as the
security model you want to implement for Oracle BI Publisher. Then specify the user credentials
for your directory.
For example, you might set the credentials for a SunOne LDAP Server as follows:
❏ Security Model is LDAP.
❏ URL is ldap://<ldap_host_name>:<ldap_port>.
❏ Administrator Username is uid=appuser,ou=people,o=siebel.com

where appuser is the authentication user created in the LDAP Server Directory. This is a
fully qualified username with LDAP connect string.
❏ Administrator Password is the password for the user you created for authentication (in
this example, that is uid=appsuser,ou=people,o=siebel.com).
❏ Distinguished Name for Users is based on the LDAP Server value.

❏ Distinguished Name for Groups is based on the LDAP Server value.
❏ Group Search Filter is a value of your choice. The default value is

(&(objectclass=groupofuniquenames)(cn=*)).
❏ Group Attribute Name is a value of your choice. The default value is cn.
❏ Group Member Attribute Name is a value of your choice. The default value is
uniquemember.
❏ Group Description Attribute Name is a value of your choice. The default value is
description.
❏ attribute used for RDN is based on the LDAP Server value (in this example, uid).
❏ Ldap Cache Interval is based on your specific deployment.

❏ Ldap Cache Interval Unit is based on your specific deployment.
b Stop and restart the OC4J environment.
c Log in to the Oracle BI Publisher Server using the LDAP directory user name and password.

For more information on implementing LDAP for Oracle BI Publisher, refer to the Oracle BI Publisher
documentation. For information on setting up an LDAP directory, see the topic on setting up the LDAP
or ADS Directory in Siebel Security Guide.
Configuring Security and Authentication Using the

Siebel Security Model
This topic describes how to implement the Siebel Security model to manage user access to the Oracle
BI Publisher Server in a Siebel Reports connected environment.
CAUTION: If you plan to use report scheduling and parameterized reports, you must set the security
model for the Oracle BI Publisher Server to either Siebel Security or LDAP. You cannot use the Oracle
BI Publisher Security model. For information about configuring the LDAP model, see “Configuring
Security and Authentication Using the LDAP Security Model” on page 244.
The Siebel Security model authenticates logins for reports users against the Siebel Database one
time only, then a session token is provided for the Oracle BI Publisher Server authentication. Because
every user executing reports has their own credentials and roles, users have private visibility on the
Oracle BI Publisher Server when scheduling reports.
To configure security and authentication using the Siebel Security Model

1 Make sure you have imported the 8111FP_new_feature.sif using Siebel Tools.
For import instructions, see “Importing Scheduling and Parameterization Features for Oracle BI
Publisher Reports” on page 235.
2 Launch Oracle BI Publisher (for example, http://<BIPServerHost>:9704/xmlpserver), and then

log in to the Oracle BI Publisher Server as administrator/Administrator.
NOTE: The URL for launching Oracle BI Publisher resides in the BI_Publisher_readme.txt file
located in the Oracle BI Publisher installation folder.
3 Click the Admin tab, and then select Security Configuration.
4 (Optional) In the Local Superuser section, enable local superuser by checking the Enable Local
Superuser checkbox, and typing a Superuser name and password of your choice.
NOTE: Superusers can log into the Oracle BI Publisher Server when the Siebel application is not
running.
5 In the Security Model section, perform the following, and then click Apply.
■ Set the model to Siebel Security
■ Enter the host name and port as the Web Service Endpoint
■ Enter the Siebel administrator credentials
NOTE: Settings are specific to your specific Siebel deployment.
6 Restart the BI Publisher Server.

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Configuring the Siebel
Mobile Client to Generate Oracle BI Publisher Reports
7 Launch Oracle BI Publisher again using the same URL, username, and password in Step 2 above.
8 Click the Admin tab, select Roles and Permissions, and then add the SiebelCRMReports folder to
the following roles:
❏ XMLP_ADMIN
❏ XMLP_SCHEDULER
❏ XMLP_DEVELOPER
❏ XMLP_SIEBEL_GUEST
9 Log out of the Oracle BI Publisher Server.
Configuring the Siebel Mobile Client to

Generate Oracle BI Publisher Reports
If you want to generate Oracle BI Publisher reports from the Siebel Mobile Web Client, you must add
two XMLP sections in the Siebel application and client configuration files.
To configure the Siebel Mobile Web Client to generate Oracle BI Publisher reports
■ Add the following XMLP sections in the siebel.cfg and client application (such as uagent.cfg for
Siebel Call Center) configuration files.
[XMLPReports]
XdoDir = /xmlp/templates/
ReportOutputDir = /xmlp/reports/
ReportDataDir = /xmlp/data/
[XMLPJvmSubsys]
FullName = XMLPJvmSubsys
Description = XMLP Java Business Service Subsystem Parameters
SubsysType = JVMSubSys
CLASSPATH = %SiebelRoot%/classes/SiebelXMLP.jar;%SiebelRoot%/classes/
xdoparser.jar;%SiebelRoot%/classes/fix6312772.jar;%SiebelRoot%/classes/
xdocore.jar;%SiebelRoot%/classes/xmlparserv2-904.jar;%SiebelRoot%/classes/
versioninfo.jar;%SiebelRoot%/classes/share.jar;%SiebelRoot%/classes/
jewt4.jar;%SiebelRoot%/classes/jdbc12.jar;%SiebelRoot%/classes/
i18nAPI_v3.jar;%SiebelRoot%/classes/collections.jar;%SiebelRoot%/classes/
bipres.jar;%SiebelRoot%/classes/bicmn.jar;%SiebelRoot%/classes/siebel.jar;%SiebelRoot%/
classes/XSLFunctions.jar;%SiebelRoot%/classes/SiebelCustomXMLP.jar
where:
■ CfgRepositoryFile is siebel.srf (or siebel_sia.srf for Siebel Industry Applications).

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
Configurations
■ CLASSPATH is the XMLP JAR files path.
NOTE: Typically, this path is in the SIEBSRVR_ROOT\CLASSES directory. Make sure the end
of line character for the Classpath is appropriate for your operating system. For example, for
UNIX, replace the semicolon (;) with a colon (:).
CAUTION: An error might occur if the value of the CLASSPATH parameter is too long. To
avoid this, copy the CLASSPATH folder to the root directory, and then point CLASSPATH to
this path.
■ %SiebelRoot% is the Siebel Server root directory.
Testing Your ACR 483 Configurations

It is recommended that you test your configurations by registering a preconfigured Oracle BI
Publisher report layout template in the Siebel application, then generating a report for that template.
NOTE: You must complete all configuration tasks for ACR 483 as described in “Roadmap for
Implementing Oracle BI Publisher Enhancements” on page 222 before performing the following
procedure.
To test your ACR 483 configurations

1 Register a preconfigured Oracle BI Publisher report template.
a Navigate to the Administration - BIP Reports screen, then the Report Template Registration view.
b Select the Account List report template, and then click Upload Files to upload this template to
the Oracle BI Publisher Server.
c Navigate to the View Association view to associate the Account List report to the Account List
view.
The Account List report template is now available to the Siebel application for use in generating
reports.
2 Generate an Oracle BI Publisher report (or reports) by doing the following:
a Navigate to the Accounts screen, then the Accounts List view.
b Query 30 or so records, and then click Reports.
c In the BI Publisher section, choose Account List.
d Select the report output type, and then click Submit.
The report generates after you choose to open the report.
e Click Close to close the output type dialog box or generate the report in a different format.
To generate a report other than the Account List report, you must first register the report template
to the Oracle BI Publisher Server, and then associate the report with the appropriate view or views
in the Siebel application.

Configurations
For more information about generating reports, see Siebel Reports Administration Guide on the
Siebel Bookshelf for Oracle’s Siebel Business Applications Version 8.1 (http://www.oracle.com/
technology/documentation/siebel.html) on Oracle Technology Network (OTN).
Instructions for FR 12-1K0VS0T

Use the following instructions to implement this fix.
1 Modify the existing data model, using the information in the following tables:
Table:
Name: S_ORG_DIST_LST
Project: Table ADL
Column: (New)
User Key
Name Type Sequence Nullable Required Physical Type Length
Name Type User Key Nullable Required Physical Type Length

Sequence
DELETE_CD Data (Public) 6 Y N Varchar 30
Index: S_ORG_DIST_LST_U1
Index Column: (New)
Column Name Sequence Sort Order
DELETE_CD 6 Asc
User Key: S_ORG_DIST_LST_U1,
User Key Attribute: (New)
Name Attribute Sequence EIM IT Column Name Basis
DELETE_CD 0 DELETE_CD
User Key Column: (New)
Name Column Sequence Column Name
DELETE_CD 0 DELETE_CD

Configurations
2 Create new Siebel Repository Objects, using the information in the following tables:
Business Component:
Name: SIA CS Retail Product - Authorized Distribution for Delete
Project: AF Assortment Group
Table: S_ORG_DIST_LST
Class: CSSBusComp
Search Spec: [Mark for Delete] like 'Delete-*'
Fields:
Name Column Join Text Length Type
Account Id OU_ID 15 DTYPE_ID
Account Product Id ORG_PROD_ID 15 DTYPE_ID
Category Id CTLG_CAT_ID 15 DTYPE_ID
Distribution Code PROD_DIST_CD 30 DTYPE_TEXT
Dist Code Order By DIST_ORDER_BY DTYPE_INTEGER
Skip Flag APPLY_SKIP_FLG 1 DTYPE_BOOL
Supplier Id SUPPLIER_ID 15 DTYPE_ID
Mark for Delete DELETE_CD 30 DTYPE_TEXT
Business Component:
Name: CG Retail Product - Distribution for Delete
Project: CG Supplier
Table: S_ORG_PROD
Class: CSSBusComp
Search Spec: [Distribution Code] = LookupValue("RTL_PRFL_DIST_CODE","Delete")
Fields:
Name Column Join Text Length Type
Account Id OU_ID 15 DTYPE_ID
Product Id PROD_ID 15 DTYPE_ID
Distribution Code PROD_DIST_CD 30 DTYPE_TEXT
Active DSTRBN_ACTV_FLG 1 DTYPE_BOOL

Configurations
3 Modify existing Siebel Repository Objects using the information in the following tables:
Business Component:
Name: SIA CS Retail Product - Authorized Distribution
Search specification:
Old Value New Value
N/A [Mark for Delete] not like 'Delete-*' OR [Mark

for Delete] IS NULL
Fields:
New? Name Column Join Text Length Type
New Mark for Delete DELETE_CD 30 DTYPE_TEXT
Business Component:
Name: SIA CS Retail Product - Authorized List

Configurations
Old Value New Value

for Delete] IS NULL
Fields:
New? Name Column Join Text Length Type
New Mark for Delete DELETE_CD 30 DTYPE_TEXT
Business Component:
Name: CG Retail Product
Old Value New Value
N/A [Distribution Code] <>

LookupValue("RTL_PRFL_DIST_CODE","Delet
e") OR [Distribution Code] IS NULL
Business Component User Property: (New)
Name Value
CG Mark Dist Code for Deletion Y
Business Object:
Name: SIA CS Supplier Account
Business Object Component: (New)

Configurations
Bus Comp Link
SIA CS Retail Product - Authorized Distribution N/A

for Delete
CG Retail Product - Distribution for Delete N/A
Link:
Name: CG Retail Product - Distribution/SIA CS Retail Product - Authorized List
Old Value New Value

for Delete] IS NULL
PickList:
Name: Retail Profile Distribution Code PickList
Old Value New Value
N/A [Name] <> 'Delete'
Applet:
Name: CPG Product Distribution Applet (Toggle Read-Only)
Old Value New Value
N/A [Distribution Code] <>

LookupValue("RTL_PRFL_DIST_CODE","Delet
e") OR [Distribution Code] IS NULL
4 Add the following new LOV value:
❏ LOV Type: RTL_PRFL_DIST_CODE
❏ Language-Independent Code: Delete

Configurations
❏ Display Value: Delete (or properly translated display value corresponding to the
language)
NOTE: As a result of ADLApply run, 'Mark for Delete' value as 'Delete-'+[RowId] could be set for
some S_ORG_DIST_LST records and 'Distribution Code' value as 'Delete' could be set for some
S_ORG_PROD records which are marked for deletion. Those records will eventually get deleted
by DeleteExtra method. Except for the previously listed BCs that are used by ADL, any BCs that
are based on S_ORG_PROD should add a BC search spec "[Distribution Code] <>
LookupValue("RTL_PRFL_DIST_CODE","Delete") OR [Distribution Code] IS NULL". Any BCs that
are based on S_ORG_DIST_LST should add a BC search spec "[Mark for Delete] not like 'Delete-
*' OR [Mark for Delete] IS NULL" to avoid this kind of record being displayed or used.
Instructions for FR 12-1BJO1E5

Use the following steps to connect to two databases.
To connect to two databases

1 Copy the database file (to C:\7.8.2[19213]FP\Seaw\SAMPLE\UTF8\ and name it
sse_sample1.dbf.
2 Copy the same file in the same directory and name it sse_sample2.dbf
3 In the uagent.cfg file, rename the existing [Sample] section to [Sample1] and rename
sse_samp.dbf to sse_samp1.dbf in the connect string. This is for the first database.
4 Copy the [Sample1] section in the file, rename it to [Sample2], and change its name to
sse_samp2.dbf in the connect string. This is for the second database.
5 Add Sample1 and Sample2 under [Datasources] in uagent.cfg.
Use the following procedure to test name-based import.
To test name-based import

1 Within Siebel Tools, query for the 'ISS Authoring Import Export Service' Business Service and
add the following user property in the Business Service User Prop section (this is independent of
the change made in case1):
■ Name = VOD_RESOLVE BY_NAMES
■ Value = TRUE
2 In the ISS VOD Import Popup Applet, add the following applet user property:
■ Name = AutoProceed
■ Value = Y
3 Recompile your siebel.srf file.

Configurations
To implement FR 12-1BJO1E5 (Scenario 1)

1 Launch twsiebel with sample db1 (source machine). http://sdcdl585i040.corp.siebel.com:8080/
start.swe (sadmin/ sadmin).
2 Create Attributes "attr1" and "attr2" and release them.
3 Create product classes "prodclass1" and "prodclass2", associate attributes to them, and release
them.
4 Create CPs, prod1 and associate the product class and attributes created in Step 2.
5 Repeat Step 4 for prod2, and release both products.
6 Go to the Product Promotions screen and create a promotion called my promo1.
7 Go to Administration - Product -> Workspace projects, create a record, and associate the data
created.
8 Take an export of the data and save the XML file.
9 Launch twsiebel with sample db2 (target machine). http://sdcdl585i040.corp.siebel.com:8082/

start.swe (sadmin/ sadmin).
10 Create data with the same names as in sample db1, and perform all of the operations that you
performed with sample db1. With Name Based imports, you should create objects with the same
name on two databases and ensure that the row ids of these objects are different.
11 Go to Administration > Product > Workspace projects and create a record called my promo1.
12 From the same screen, go to the applet menu and select Import Contents.
13 Import the XML file. This will generate a warning report.
14 The data is imported with the IDs of products present in source machine. In the pop-up dialog
box, click on the 'DownloadReport' button, and review the log file to ensure that there are no
errors and the import is successful.
Verify that the data in the target database is successfully updated with the data in the source
database.
The following four outcomes are possible for Name-Based Import:
■ Case 1: Name not found, ID not found, go through without error
■ Case 2: Name found, with same ID, OK, go through
■ Case 3: Name found, ID not the same, replace source ID in the property set with target ID,
no conflict
■ Case 4: Name not found, but ID in use, conflict, cannot resolve
Procedures for working with the four preceding possible outcomes are detailed below.
Setup Instructions
Desynchronize ROW_ID generation in the first database and the second database (big gap) (keep
the created record in one database to bounce up the row) or if you are able to run SQL, run the
following the SQL command on one database using dbisql: Update S_SSA_ID set
CORPORATE_PREFIX = a different value.

Configurations
Case 1: Name not found, ID not found

1 In the first database, create the Product Definition "Simp Adm1", and export it in a file called
"Simp Adm1 - DB1 Orig"
2 In the second database, using simulator with "UseNamesAsKeys" = Y, "LogFullReport" =Y, import
the "Simp Adm1 - DB1 Orig" file.
3 Download and save the warnings at the end of the import.
4 Make sure that the product was created correctly.
5 Check the simulator report file.
Case 2: Name found, with same ID

1 In the first database, Update Product Definition "Simp Adm1" e.g add a resource
4 Make sure that the product changes were removed.
Case 3: Name found, ID not the same

1 In the first database, create a Product Definition called "Simp Man1", and export it in a file called
"Simp Man1 - DB1 Orig".
2 In the second database, create a Product Definition "Simp Man1" with one resource, and export
it in a file called "Simp Man1 - DB2 Orig" using simulator with "UseNamesAsKeys" = Y,
"LogFullReport" =Y.
3 Import the "Simp Man1 - DB1 Orig" file.
5 Make sure that the product changes were removed.
Case 4: Name not found, but ID in use

1 In the first database, update Product Definition from "Simp Adm1" to "Simp Adm1 Mod".

See the zip file folder on the main 7.8.2.x Maintenance Release page to access the
Cfg_Vod_Import_Simulator.xml file.

Configurations
Import it in Administration - Business Services > Details.
Import the test simulator entry in Administration - Business Services > Simulator. Contact Oracle
Customer Care to access the SimulatorForImport.xml file.
Parameters can be imported in Administration - Business Services > Input Arguments. Contact
Oracle Customer Care to access the SimulatorForImportParams.xml file.
To modify the parameters

1 Click on the "Property Name" field and open the pop-up window.
2 For "LogFile", enter the full file path.
3 For "FileName", enter the full path to the XML file that you want to import.
4 For "FileType", enter the extension of the file that you want to import.
5 For "RootObjectName", enter the name of the JWS project that you want to import content from.
The name should point to a fresh JWS project so that you will not confuse new objects with
existing ones.
6 For "ReportOnly", enter Y if you do not want to perform an actual import and only analyze for
possible conflicts, and enter N/leave the field empty if you want to perform the actual import.
7 For UseNamesAsKeys", enter Y if you do not want to use name mapping - input XML should
contain all referenced objects - or enter N/leave the field empty if you want to use standard
behavior - ID based mapping.
8 For "NoSrcNameChange", enter Y if you do not want to enforce VOD Names from source or enter
N/leave the field empty.
9 For "NoTargNameChange", enter Y if you do not want to prevent VOD Names change on target
or enter N/leave the field empty.
10 For "AutoProceed", enter Y to enable automatic conflict resolution or enter N/leave the field
empty.
11 For "LogFullReport", enter Y if you do not want to dump the resulting property set in the log file,
or enter N/leave the field empty to log the shortened report.
12 After completing the modifications, run the simulator.
Instructions for FR 12-1CY8FKI

To implement this fix, you must make changes to the following ISS Integration Components:
■ ISS Promotion
■ ISS Promotion Items for Import
■ ISS Promotion Pricing Rules Summary
■ ISS Promotion Upgrade
■ ISS Promotion Terms

Configurations
Integration Component - ISS Promotion

1 In the Integration Component 'ISS Promotion', for component field 'Name', add the following
Integration Component User Properties:
■ NoInsert = 'Y"
■ NoUpdate = 'Y'
NOTE: Configuration Model Id already exists in 'ISS Promotion'
Integration Component - ISS Promotion Items for Import

1 Promotion Id already has NoInsert and NoUpdate = 'Y'.
2 Added NoInsert and NoUpdate = 'Y' for Product Name and deactivated PickList = 'Y'.
3 Prod Cfg Model Id already exists. Add integration component field user prop PICKLIST = 'Y'
4 Prod Id already has NoInsert and NoUpdate = 'Y'
5 In the Business Component 'ISS Promotion Items for Import', for field 'Prod Cfg Model Id', set
picklist = PickList Internal Product All and the following pickmap fields:
Field Picklist Field
Prod Cfg Model Id Configuration Model Id
Prod Id Id
Product Name Name
Product Type Product Def Type Code
Integration Component - ISS Promotion Pricing Rules Summary

1 Promotion Id already has NoInsert and NoUpdate = 'Y'.
2 Add a new field in the 'ISS Promotion Pricing Rules Summary' Business Component using the
following values:
■ Name = Prod Cfg Model Id
■ Join = S_PROD_INT
■ Column = CFG_MODEL_ID
■ Type = DTYPE_ID
■ Text Length = 15
3 Set picklist = PickList Internal Product All for the 'Prod Cfg Model Id' field in the 'ISS Promotion
Pricing Rules Summary' Business Component and set pickmaps using the following values:

Configurations
Prod Id Id
Product Name Name
4 Add a new integration component field for the 'ISS Promotion Pricing Rules Summary' integration
component using the following values:
■ Data Type = DTYPE_ID
■ User Visible = Y
■ Type = Data
■ External Name = Prod Cfg Model Id
■ External Data Type = DTYPE_ID
■ External Sequence = 22
■ XML Sequence = 22
■ XML Style = Element
■ XML Tag = ProdCfgModelId
5 Add integration component field User Property user prop for 'Prod Cfg Model Id' using the
following values:
■ Name = PICKLIST
■ Value = Y
6 Add NoInsert and NoUpdate = 'Y' for Product Name and deactivate PickList = 'Y'.
Integration Component - ISS Promotion Upgrade

1 Target Promotion Id is already inactive.
2 Target Promotion Name already has NoInsert and NoUpdate = 'Y'
3 Add a new field in the 'ISS Promotion Upgrade' Business Component with the following values:
■ Join = Original Promotion
■ Column = CFG_MODEL_ID
■ Type = DTYPE_ID
■ Text Length = 15

Configurations
4 Set picklist = ISS Promotion PickList for the 'Prod Cfg Model Id' field in the 'ISS Promotion
Upgrade' Business Component and set pickmaps using the following values:
Original Promotion Id Id
Original Promotion Name Name
5 Add a new integration component field for the 'ISS Promotion Upgrade' Integration Component
using the following values:
■ Data Type = DTYPE_ID
■ User Visible = Y
■ Type = Data
■ External Name = Prod Cfg Model Id
■ External Data Type = DTYPE_ID
■ External Sequence = 28
■ XML Sequence = 28
■ XML Style = Element
■ XML Tag = ProdCfgModelId
6 Add an integration component field for the 'Prom Cfg Model Id' User Property using the following
values:
■ Name = PICKLIST
■ Value = Y
7 Add NoInsert and NoUpdate = 'Y' for 'Original Promotion Name' and deactivate PickList = 'Y'.
Integration Component - ISS Promotion Terms

1 Make Inactive = 'Y' for Component Field 'Term Template Id', to deactivate it.
Instructions for FR 12-1ERTG8V

1 Within Siebel Tools, query for the "Quote" Business Component and add the following user
property:
■ Name: Instance Uniform Name EAI Object:Account
■ Value: ISS Quote

Configurations
2 Query for the "Order Entry - Orders" Business Component and add the following user property:
■ Name: Instance Uniform Name EAI Object:Account
■ Value: ISS Order
3 Query for the "Account" Business Object and add the following Business Components:
a Business Component: Quote Item (Simple)
Link: Quote/Quote Item (Simple)
b Business Component: Quote Item XA (Deep)
Link: Quote/Quote Item XA (Deep)
c Business Component: Order Entry - Line Items (Simple)
Link: Order Entry - Orders/Order Entry - Line Items (Simple)
d Business Component: Order Item XA (Deep)
Link: Order Entry - Orders/Order Item XA (Deep)
e Business Component: Order Entry - Line Items (Simple).Line Number (Sequence)
Link: Order Entry - Orders/Order Entry - Line Items (Simple).Line Number (Sequence)
NOTE: The Business Components added should be the same as the ones configured in the
Application Data Map for "CopyOrder" or "CopyQuote".
4 Query for the "Quote", "Order Entry - Orders" Business Components and add the following user
property:
■ Name: Instance Uniform Name EAI Object:Contact
■ Value: ISS Order
5 Query for the "Contact" Business Object and add the following Business Components:
a Business Component: Quote Item (Simple)

Link: Quote/Quote Item (Simple)
b Business Component: Quote Item XA (Deep)
Link: Quote/Quote Item XA (Deep)
c Business Component: Order Entry - Line Items (Simple)
Link: Order Entry - Orders/Order Entry - Line Items (Simple)
d Business Component: Order Item XA (Deep)
Link: Order Entry - Orders/Order Item XA (Deep)
e Business Component: Order Entry - Line Items (Simple).Line Number (Sequence)
Link: Order Entry - Orders/Order Entry - Line Items (Simple).Line Number (Sequence)
NOTE: The Business Components added should be the same as the ones configured in the
Application Data Map for "CopyOrder" or "CopyQuote".

Configurations
6 Compile the preceding changes to the srf, and test it.
Instructions for FR 12-1FWLGC6 and FR 12-1DS2LPX

1 Within the Object Explorer view in Siebel Tools, navigate to "Link" and lock the CS CG Sales
Volume Planning2 project.
2 Create a new "Link" record with the following values:
■ Name: CG SVP Product Baseline/CS CG SVP Flat Category Prod
■ Parent Business Component: CG SVP Product Baseline
■ Child Business Component: CS CG SVP Flat Category Prod
■ Source Field: Product Id
■ Destination Field: Product Id
3 In Object Explorer, navigate to "Business Object" and check out the "CG Sales Volume Planning"
Business Object.
4 Expand "Business Object" into "Business Object Component" and create a new "Business Object
Component" record with the following values:
■ Business Component: CS CG SVP Flat Category Prod
5 In Object Explorer, navigate to "Business Component" and check out the "CG SVP Product
Baseline" Business Component.
6 Expand "Business Component," navigate to "Multi Value Link", and create a new "Multi Value
Link" Record with the following values:
■ Name: Parent Categories
■ Destination Business Component: CS CG SVP Flat Category Prod
■ Destination Link: CG SVP Product Baseline/CS CG SVP Flat Category Prod

■ Primary ID Field: Product Id
■ Use Primary Join: Checked
7 Navigate to "Field", and create a new "Field" record with the following values:
■ Name: Par Categories
■ Destination Field: Category Id
■ Multivalue Link: Parent Categories
■ Multivalued: Checked
■ Text Length: This field should be blank
■ Type: This field should be blank
8 Check out the "CG SVP Product Target" Business Component.

Configurations
9 Expand "Business Component", navigate to "Multi Value Link", and create a new "Multi Value
Link" record with the following values:
■ Name: Parent Categories
■ Destination Business Component: CS CG SVP Flat Category Prod
■ Destination Link: CG SVP Product Target/CS CG SVP Flat Category Prod
■ Primary ID Field: Product Id
■ Use Primary Join: Checked
10 Navigate to "Field", and create a new "Field" record with the following values:
■ Name: Par Categories
■ Destination Field: Category Id
■ Multivalue Link: Parent Categories
■ Multivalued: Checked
■ Text Length: This field should be blank
■ Type: This field should be blanked out
11 Compile all of the changes.
Instructions for FR 12-1IAE2QU

Use the information in the following section to implement FR 12-1IAE2QU.
NOTE: The Custom Business Component in this example was created by copying the Account
Business Component and Custom Business Object was created by copying the Account Business
Object. For Business Components and Business Objects that are not similar to any existing entities,
be careful for making addition changes.
CAUTION: Remember to compile when necessary.
1 Create the Custom Business Component (My_Account Business Component was created by
copying Account BC, so "Custom BC Name" = My_Account )and compile.
2 Create the Custom Business Object (My_Account Business Object was created by copying
Account BO), make Custom Business Component (My_Account) part of the Business Components
under this Business Object and make it (My_Account) the primary Business Component for this
Business Object (My_Account).
3 Add the Custom Business Component under the appropriate Account/Contact Business Object
(whatever the Custom Business Object is similar to).
4 Create the "Custom BC Name"/DeDuplication Results (Account) link (e.g. My_Account/

DeDuplication Results (Account) because if the My_Account BC was created by copying the
Contact Business Component, the link would be "My_Account/DeDuplication Results (Contact)"
and so forth).

Configurations
5 Check if DeDuplication Results (Account) is part of the Business Components under this Custom
Business Object with the "Custom BC Name"/DeDuplication Results (Account) link (if necessary,
edit the existing link name).
6 Edit the appropriate applets (in this example "Account List Applet" and "Account Entry Applet")
to be based on "Custom BC Name" (such as My_Account ), and include the following user
property in each of the Applets:
■ Name: DeDuplication Results Applet
■ Value: DeDuplication Results (Account) List Applet
NOTE: Be careful about the values corresponding to your Business Component.
7 Add the "Custom Business Component" under the "DeDuplication" Business Object.
8 Compile the affected projects.
9 Create the applets and views (create Custom Account List Applet copied from the Account List
Applet and so forth), and base the "Custom Account List View" on "Custom Business Object" .
10 Add the applets to the custom view that you just created ("Custom Account List View" in this
case).
11 Navigate to View > View Web Template Item, navigate to the bottom applet, and add the two
applets under this view. (You may keep the same name.)
12 Add the view to the appropriate screen (such as the Accounts Screen).
13 On the left pane of View > Screen View, add the New view to the screen at the bottom applet,
using the following values:
■ Name: Custom Account List View
■ Select the appropriate value from the Viewbar Text String Reference
■ Select the appropriate value from the Menu Text String Reference
14 Create a view similar to the "Account Duplicates Detail View" (such as the "Custom Contact
Duplicates Detail View" or similar depending upon your Custom Business Object/Business
Component) and base it upon the Custom Business Object.
15 Compile all the changes to the SRF.

16 Launch the Siebel application.
17 Register the view in the application by navigating to Admin Application > Views> New, and copy
and paste the view name in Name and Description.
18 Navigate to Application - Responsibilitie, and add the new view under administration
responsibility.
19 Add the responsibility to the user SADMIN.

20 Log out of the application and log back in.
21 Start the application, and navigate to Site Map > Admin - Data > List of Values.

Configurations
22 Create a new record for the type DQ_SETTING_NAME with Appropriate Display Name (such as
Force User DeDup-"Custom BC Name or some short form of it" within some prescribed length)
and Language Independent Code
CAUTION: The BC Name must be exact.
23 Navigate to the List of Values Explorer (under Admin-Data) and add values Y and N of type
DQ_SETTING_VALUES .
24 Log out of the application and log back in.

25 Go to Admin-Data Quality >Data Quality Setting, add a new record with Value Force User DeDup
- "Custom BC" and set the value to Yes.
26 Check whether Forced DeDuplication works or not.
Instructions for FR 12-1J5IVKH

Use the procedures in the following section to implement FR 12-1J5IVKH.
Modifying the SIS OM Edit Complex Asset and SIS OM Edit Complex
Asset Workflow—Contact
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.
2 Revise the SIS OM Edit Complex Asset Workflow as follows:
a 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.
b Move the connector from "Set Requested Product Instance" to "Is Product Instance
Customizable" and connect it to "Auto Match Port Ids".
c Move the connector from "Auto Match Port Ids" to "Display Warning?" and connect it to "Is
Product Instance Customizable".
d Move the connector from "Interactive Mode?" to "Auto Match Port Ids" and connect it to "Display
Warning?"
3 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

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
7.8.2.x Fix Packs
4 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 SiebelMessage

Argument
Auto-Match Report Output AutomatchReport

Argument
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".
5 Save the changes, test, and deploy.
To modify the SIS OM Edit Complex Asset Workflow-Contact workflow

■ Revise the SIS OM Edit Complex Asset Workflow—Contact workflow using Step 2a through Step
5 detailed above.
Installation Instructions for 7.8.2.x Fix

Packs
This section includes the following topics:
■ Installation Overview
■ Installation Scenarios Described in This Section
■ Applicable Base Releases
■ About Running Siebel Image Creator
■ About Installing Additional Languages
■ About Installing Siebel Quick Fix Releases
■ Upgrade Requirements
■ About Installing Patch Releases for Siebel Products
■ Installing Patch Releases on Windows
■ Installing Patch Releases on UNIX
■ Configuring Slipstream Patch Installation
■ Installing New Languages
■ Postinstallation Task for the Siebel Server
■ Postinstallation Task for the Web Server
■ Postinstallation Tasks for High Interactivity Clients

7.8.2.x Fix Packs
■ Postinstallation Tasks for Supporting New Languages
■ Installing Siebel Universal Customer Master
■ Uninstalling Patch Releases
Installation Overview
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
applicable releases for all products that apply to your localized version.
NOTE: This Maintenance Release Guide is updated to include the latest version 7.8.2.x Fix Pack
release. Version 7.8.2.x Fix Pack releases are cumulative and do not need to be installed sequentially.
You can install version 7.8.2, then the latest version 7.8.2.x release.
This section includes the following subtopics:
■ Installation Scenarios Described in This Section
■ Applicable Base Releases
■ About Running Siebel Image Creator
■ About Installing Additional Languages
■ About Installing Siebel Quick Fix Releases
■ Upgrade Requirements
Installation Scenarios Described in This Section

Instructions in this section apply in the following scenarios:
■ Performing new full installation of version 7.8.2, with version 7.8.2.x. If you are installing
version 7.8.2 as a new full installation, follow the instructions in the Siebel Installation Guide for
the operating system you are using to install the products.
Where applicable, also follow the instructions in this Maintenance Release Guide for installing the
latest version 7.8.2.x Fix Pack release on top of version 7.8.2. You can install 7.8.2 and 7.8.2.x
together by configuring slipstream patch installation. For details, see Configuring Slipstream Patch
Installation.
For the most recent version of the Siebel Installation Guide for the operating system you are
using, see the latest version 7.8 Siebel Bookshelf.
For more information about installing 7.8.2 or 7.8.2.x, see About Installing Patch Releases for
Siebel Products.

7.8.2.x Fix Packs
■ Installing version 7.8.2 and version 7.8.2.x (patching existing 7.8.0 (Developer
Release) or 7.8.1.x (Limited Release) installation). If you are installing version 7.8.2 as a
maintenance release (patch release) on top of an existing base installation of version 7.8.0
(Developer Release) or version 7.8.1 or 7.8.1.1 (Limited Release), follow the instructions in this
Maintenance Release Guide for doing this.
Also follow the instructions in this guide for installing the latest version 7.8.2.x Fix Pack release
on top of version 7.8.2. You can install 7.8.2 and 7.8.2.x together by configuring slipstream patch
installation. For details, see Configuring Slipstream Patch Installation.
When you installed version 7.8.0 or 7.8.1, 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 7.8 Siebel Bookshelf.
CAUTION: Upgrade requirements apply for this scenario. For more information, see Upgrade
Requirements.
For more information about installing 7.8.2 or 7.8.2.x, see About Installing Patch Releases for
Siebel Products.
■ Installing version 7.8.2.x (patching existing 7.8.2 or prior 7.8.2.x installation). If you
have already installed version 7.8.2 as a new full installation, and optionally installed a 7.8.2.x
Fix Pack release, and are now installing the latest Fix Pack version 7.8.2.x on top of 7.8.2 or
7.8.2.x, follow the instructions in this Maintenance Release Guide for doing this.
When you installed version 7.8.2 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 7.8 Siebel Bookshelf.
For more information about installing 7.8.2.x, see About Installing Patch Releases for Siebel
Products.
■ Installing new languages provided with version 7.8.2. You can include languages
(language packs) in a new 7.8.2 installation. Or, you can add them to an existing installation after
you have installed version 7.8.2 as a new installation or as a maintenance release. Languages
provided with release 7.8.2 are:
■ Arabic (ARA)
■ Chinese Traditional (CHT)
■ Hebrew (HEB)

7.8.2.x Fix Packs
■ Swedish (SVE)
Include or add any languages that you will require in your Siebel version 7.8.2 installation image
(network image), which you create using the Siebel Image Creator utility. Then install the
software, or add languages to existing installed software, from the installation image.
You can add languages to an existing installation. If you are installing 7.8.2 as a maintenance
release on top of an existing 7.8.0 or 7.8.1.x release, you must add the languages after you
install 7.8.2 (this is a change compared to version 7.7.x).
Install any applicable 7.8.2.x Fix Packs after you have installed languages in a new or existing
installation.
For more information about installing new languages provided with version 7.8.2, see Installing
New Languages.
For information about installing other supported Siebel languages, see the Siebel Installation
Guide for the operating system you are using. See also Siebel System Requirements and
Supported Platforms on Oracle Technology Network and the Siebel Global Deployment Guide.
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.
As noted earlier, version 7.8.2 can be installed either as a full installation or as a patch installation.
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 version 7.8.2 as a patch release:
■ Siebel Business Applications, version 7.8.0 (Developer Release), 7.8.1 or 7.8.1.1 (Limited
Release)
■ Siebel Industry Applications, version 7.8.0 (Developer Release), 7.8.1 or 7.8.1.1 (Limited
Release)
Here are the base versions and product suites for installing the latest version 7.8.2.x:
■ Siebel Business Applications, version 7.8.2 or lower-level 7.8.2.x
■ Siebel Industry Applications, version 7.8.2 or lower-level 7.8.2.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 7.8.2.x release level.

7.8.2.x Fix Packs
About Running Siebel Image Creator

The Siebel Image Creator utility is used to create an installation image (sometimes called a network
image) for any version 7.8.2 or 7.8.2.x release. The image can include any Siebel installable product
provided as part of this product release. You can also add languages to an existing installation image
of the same version, for languages that were not previously included.
Siebel Image Creator is described in the Siebel Installation Guide for the operating system you are
using, on the 7.8 Siebel Bookshelf.
See also What Are JAR files and How Do You Use Them? (Doc ID 473799.1) on OracleMetaLink 3.
NOTE: Installing any Siebel 7.8.2.x release, for a new installation or a patch installation, must be
done from an installation image. Always use the most recent version of Siebel Image Creator.
About Installing Additional Languages

With version 7.8.x, you can install additional languages for an existing installation. It is possible to
do so after a version 7.8.2.x patch release has been installed. However, for each component for which
you install a language, you must then install (or reinstall) all applicable 7.8.2.x releases. (Because
Fix Pack releases are cumulative, you can install just the latest 7.8.2.x Fix Pack, even if you
previously installed a prior 7.8.2.x Fix Pack.)
Where possible, install any languages you require before you install any version 7.8.2.x Fix Pack
releases, so you will not need to reinstall the same Fix Pack releases.
For more information, see Installing New Languages.
NOTE: You must perform additional steps to implement any new language you have installed,
including importing repository data and related steps. For more information about implementing a
language, see relevant Siebel Bookshelf documentation, including the Siebel Installation Guide for
the operating system you are using, Configuring Siebel Business Applications, and the Siebel Global
Deployment Guide. See also Postinstallation Tasks for Supporting New Languages.
About Installing Siebel Quick Fix Releases

After installing version 7.8.2 and 7.8.2.x as described in this guide, you can also install any
applicable quick fix releases on top of version 7.8.2.x. When you install a quick fix release, installed
languages may also be patched. Installing quick fix releases may entail restrictions about which
subsequent Fix Pack releases can be installed.
For detailed information about a particular quick fix, see the documentation that comes with the
quick fix.
Quick Fixes Included in 7.8.2.x Fix Packs identifies fixes from previous quick fix releases that are
included in version 7.8.2.x releases.

7.8.2.x Fix Packs
Upgrade Requirements
In order to move from version 7.8.0 (Developer Release) or 7.8.1.x (Limited Release) to version
7.8.2, you install 7.8.2 as a patch release (maintenance release) on top of your prior 7.8.x release,
as described in this document. If a 7.8.2.x Fix Pack release is available, you then install this release
on top of 7.8.2.
NOTE: After you install, a database schema and repository upgrade is required to move
from your prior 7.8.x release to 7.8.2 or 7.8.2.x.
Moving to release 7.8.2 or 7.8.2.x from any release prior to 7.8.x (such as 7.7.x) also requires
upgrading.
For detailed information about upgrade tasks, see the Siebel Database Upgrade Guide. See also
Siebel System Requirements and Supported Platforms on Oracle Technology Network.
About Installing Patch Releases for Siebel Products

For each Siebel product, installing version 7.8.2 or 7.8.2.x 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.
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.
NOTE: If you require one of the new languages that were provided with version 7.8.2 (ARA, CHT,
HEB, or SVE), review all applicable information in Installation Overview and Installing New Languages
before you install the patch releases. Where possible, install any languages you require before you
install any version 7.8.2.x Fix Pack releases, so you will not need to reinstall the same Fix Pack
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 7.8 Siebel Installation Guide for
the operating system you are using. For more information, see About Running Siebel Image Creator.
After you install 7.8.2 and 7.8.2.x, any applicable quick fix releases can also be installed, on top of
version 7.8.2.x. For more information, see About Installing Siebel Quick Fix Releases.
NOTE: As noted in Upgrade Requirements, moving from version 7.8.0 or 7.8.1.x to version 7.8.2 or
7.8.2.x requires that you also perform steps described in the Siebel Database Upgrade Guide.
For instructions for installing 7.8.2 and 7.8.2.x for your operating system platform, see:
■ Installing Patch Releases on Windows
■ Installing Patch Releases on UNIX

7.8.2.x Fix Packs
Installing Patch Releases on Windows

Procedures for installing the Windows products provided with these patch releases 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 releases you are installing, in the general
sequence presented here.
Before you install patch releases, review all applicable information in About Installing Patch Releases
for Siebel Products.
If you will be installing CHT, ARA, HEB, or SVE languages, also review Installing New Languages.
NOTE: Before you can install any patch releases, you must create the installation images you require
for versions 7.8.2 and 7.8.2.x. For more information, see About Running Siebel Image Creatorand see
the Siebel Installation Guide for the operating system you are using.
TIP: As an alternative to installing 7.8.2 and 7.8.2.x separately as described in the procedures in
this section, you can configure 7.8.2.x installation as described in Configuring Slipstream Patch
Installation.
Installing Siebel Enterprise Server on Windows

Use these instructions for installing these patch releases on any machine where a Siebel Enterprise
Server component is installed, including Siebel Server, Siebel Gateway Name Server, and Siebel
Database Server.
To install the patch releases 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).
2 In Windows Explorer, navigate to the Siebel image location for version 7.8.2, 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\7.8.2.0.
3 Double-click setup.exe to launch the Siebel Enterprise Server installer for 7.8.2.
4 Select a 7.8.0 or 7.8.1.x instance to patch from the list of detected installations.
5 Follow all prompts to complete installation of 7.8.2.
6 Navigate to the Siebel image location for version 7.8.2.x, then to the directory where the installer
is located. For Siebel Enterprise Server, navigate to
Siebel_Image\Windows\Server\Siebel_Enterprise_Server, where:
D:\Siebel_Install_Image\7.8.2.x.
7 Double-click setup.exe to launch the Siebel Enterprise Server installer for 7.8.2.x.
8 Select a 7.8.2 or previous 7.8.2.x instance to patch from the list of detected installations.

7.8.2.x Fix Packs
9 Follow all prompts to complete installation of 7.8.2.x.
10 Repeat these steps on each machine with a Siebel Enterprise Server component installation to
be patched.
Installing Siebel Web Server Extension on Windows

Use these instructions for installing these patch releases 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
releases.
To install the patch releases for Siebel Web Server Extension

1 Shut down the Web server.
directory where the installer is located. For SWSE, navigate to
Siebel_Image\Windows\Server\Siebel_Web_Server_Extension, where:
3 Double-click setup.exe to launch the SWSE installer for 7.8.2.
is located. For SWSE, navigate to
Siebel_Image\Windows\Server\Siebel_Web_Server_Extension, where:
7 Double-click setup.exe to launch the SWSE installer for 7.8.2.x.
10 Repeat these steps on each machine with a SWSE installation to be patched.

NOTE: The Web server must be restarted at the end of all patch installation. For more
information, see Postinstallation Task for the Web Server.

7.8.2.x Fix Packs
Installing Siebel Reports Server on Windows

Use these instructions for installing these patch releases 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.
NOTE: Installation of a 7.8.2 or 7.8.2.x patch release for Siebel Reports Server products may take
a considerable amount of time to complete, if the patch release delivers a new version of Actuate
software. For the version of Actuate delivered with each patch release, see Siebel System
Requirements and Supported Platforms on Oracle Technology Network.
TIP: If you are certain that the latest version of Actuate products was already installed with 7.8.2
or a prior 7.8.2.x Fix Pack, then you can prevent the Actuate products from being reinstalled for the
current Fix Pack. For example, if you previously installed 7.8.2, then you can determine from Siebel
System Requirements and Supported Platforms on Oracle Technology Network that the latest 7.8.2.x
Fix Pack would reinstall the same Actuate version. Before you install the latest 7.8.2.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 7.8.2.x Fix Pack). Setting this parameter to no
prevents the same version of Actuate from being reinstalled when you install the Siebel Reports
Server patch release.
To install the patch releases for Siebel Reports Server

directory where the installer is located. For Siebel Reports Server, navigate to
Siebel_Image\Windows\Server\Siebel_Reports_Server, where:
2 Double-click setup.exe to launch the Siebel Reports Server installer for 7.8.2.
4 Enter your Actuate license key. (Enter the same license key for all version 7.8.x.x releases.)
NOTE: The license key is provided by Siebel Systems in an Actuate letter. If you have the Siebel
Reports Server license and have not received the Actuate license key letter, contact Siebel
Technical Support to request the Actuate license key.
is located. For Siebel Reports Server, navigate to
Siebel_Image\Windows\Server\Siebel_Reports_Server, where:
7 Double-click setup.exe to launch the Siebel Reports Server installer for 7.8.2.x.
9 Enter your Actuate license key again. (Enter the same license key that you entered in Step 4.)

7.8.2.x Fix Packs
11 Repeat these steps on each machine with a Siebel Reports Server installation to be patched.
Installing Siebel Mobile Web Client, Siebel Tools, or Siebel Client Sync
on Windows
Use these instructions for installing these patch releases on machines where Siebel Mobile Web
Client, Siebel Tools, or Siebel Client Sync are installed.
To install the patch releases for Siebel Mobile Web Clients, Siebel Tools, or Siebel
Client Sync
1 Exit the application for which you are installing the patch releases.
NOTE: For a Siebel Mobile Web Client using the Siebel QuickStart feature, you must also exit the
QuickStart agent. To do this, right-click on 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:
3 Double-click install.exe to launch the client installer for 7.8.2.
is located. The directory would match the directory from Step 2, except that:
7 Double-click install.exe to launch the client installer for 7.8.2.x.
10 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.

7.8.2.x Fix Packs
Installing Patch Releases on UNIX

Procedures for installing the UNIX products provided with these patch releases 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 releases you are installing, in the general
sequence presented here.
Before you install patch releases, review all applicable information in About Installing Patch Releases
for Siebel Products.
If you will be installing CHT, ARA, HEB, or SVE languages, also review Installing New Languages.
Some Siebel products can only be installed on Windows, such as Siebel Mobile Web Clients, Siebel
Tools, and Siebel Client Sync. For more information, see Installing Patch Releases on Windows.
NOTE: Before you can install any patch releases, you must create the installation images you require
for versions 7.8.2 and 7.8.2.x. For more information, see About Running Siebel Image Creator and
see the Siebel Installation Guide for the operating system you are using.
TIP: As an alternative to installing 7.8.2 and 7.8.2.x separately as described in the procedures in
this section, you can configure 7.8.2.x installation as described in Configuring Slipstream Patch
Installation.
Installing Siebel Enterprise Server on UNIX

Use these instructions for installing these patch releases on any machine where a Siebel Enterprise
Server component is installed, including Siebel Server, Siebel Gateway Name Server, and Siebel
Database Server. These instructions are for both GUI mode and console mode.
To install the patch releases for Siebel Enterprise Server components

1 Stop all running Siebel Servers by running the command stop_server on each applicable server
machine. (See the Siebel System Administration Guide for details on how to use this command.)
Also shut down any running instances of the Siebel Server Manager (srvrmgr).
2 Unload libraries from the system cache by running the command reset_server all on each
applicable server machine. (See the Siebel System Administration Guide for details on how to
use this command.)
3 Stop the Siebel Gateway Name Server by running the command stop_ns. (See the Siebel System
Administration Guide for details on how to use this command.)
4 Stop the Web server by running one of the following commands:
■ stopapa – for IBM HTTP Server (on AIX) and HP Apache Web Server (on HP-UX)
■ stop – for Sun Java System Web Server (on Sun Solaris)
5 (AIX only) Verify that the login ID performing installation has permission to run slibclean by
asking the administrator to change the permission as follows:
chmod 6555 /usr/sbin/slibclean
6 (AIX only) Execute slibclean, as follows:

7.8.2.x Fix Packs
/usr/sbin/slibclean
7 Open a new shell and navigate to the Siebel image location for version 7.8.2, 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/7.8.2.0.
■ UNIX_OS = Your UNIX operating system, such as AIX, HPUX (HP-UX), or Solaris.
8 (For GUI mode) Run setupUNIX_OS to launch the Siebel Enterprise Server installer in GUI mode
for version 7.8.2, where:
■ UNIX_OS = Your UNIX operating system, such as aix (AIX), hp (HP-UX), or sol (Solaris).
Go to Step 10.
9 (For console mode) Enter the following command to launch the Siebel Enterprise Server installer
in console mode for 7.8.2:
setupUNIX_OS –is:javaconsole -console
where:
/Siebel_Install_Image/7.8.2.x.
13 Launch the Siebel Enterprise Server installer for 7.8.2.x, in GUI mode or console mode.
16 Repeat these steps on each machine with a Siebel Enterprise Server component installation to
be patched.
Installing Siebel Web Server Extension on UNIX

Use these instructions for installing these patch releases on any machine where a Siebel Web Server
Extension (SWSE) component is installed. These instructions are for both GUI mode and console
mode.
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
releases.

7.8.2.x Fix Packs
To install the patch releases for Siebel Web Server Extension

1 Stop the Web server by running one of the following commands:
■ stopapa – for IBM HTTP Server (on AIX) and HP Apache Web Server (on HP-UX)
■ stop – for Sun Java System Web Server (on Sun Solaris)
2 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:
6 (For GUI mode) Run setupUNIX_OS to launch the SWSE installer in GUI mode for 7.8.2, where:
Go to Step 8.
7 (For console mode) Enter the following command to launch the SWSE installer in console mode
for 7.8.2:
where:
11 Launch the SWSE installer for 7.8.2.x, in GUI mode or console mode.

7.8.2.x Fix Packs
14 Repeat these steps on each machine with a SWSE installation to be patched.

NOTE: The Web server must be restarted at the end of all patch installation. For more
information, see Postinstallation Task for the Web Server.
Installing Siebel Reports Server on UNIX

Use these instructions for installing these patch releases 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. These instructions are for both GUI
mode and console mode.
NOTE: Installation of a 7.8.2 or 7.8.2.x patch release for Siebel Reports Server products may take
a considerable amount of time to complete, if the patch release delivers a new version of Actuate
software. For the Actuate versions delivered with each patch release, see Siebel System
Requirements and Supported Platforms on Oracle Technology Network.
TIP: If you are certain that the latest version of Actuate products was already installed with 7.8.2
or a prior 7.8.2.x Fix Pack, then you can prevent the Actuate products from being reinstalled for the
current Fix Pack. For example, if you previously installed 7.8.2, then you can determine from Siebel
System Requirements and Supported Platforms on Oracle Technology Network that the latest 7.8.2.x
Fix Pack would reinstall the same Actuate version. Before you install the latest 7.8.2.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 7.8.2.x Fix Pack). Setting this parameter to no
prevents the same version of Actuate from being reinstalled when you install the Siebel Reports
Server patch release.
To install the patch releases for Siebel Reports Server

/usr/sbin/slibclean
directory where the installer is located. For Siebel Reports Server, navigate to Siebel_Image/
UNIX_OS/Server/Siebel_Reports_Server, where:
4 (For GUI mode) Run setupUNIX_OS to launch the Siebel Reports Server installer in GUI mode for
version 7.8.2, where:
Go to Step 6.

7.8.2.x Fix Packs
5 (For console mode) Enter the following command to launch the Siebel Reports Server installer in
console mode for 7.8.2:
where:
7 Enter your Actuate license key. (Enter the same license key for all version 7.8.x.x releases.)
NOTE: The license key is provided by Siebel Systems in an Actuate letter. If you have the Siebel
Reports Server license and have not received the Actuate license key letter, contact Siebel
Technical Support to request the Actuate license key.
10 Launch the Siebel Reports Server installer for 7.8.2.x, in GUI mode or console mode.
12 Enter your Actuate license key again. (Enter the same license key that you entered in Step 7.)
14 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.
Where slipstream patch installation is invoked by a full installation rather than by another patch
installation, the patch installation is executed after language packs are installed, and before the
Siebel Software Configuration Wizard is launched.
As noted in Installation Overview, slipstream patch installation may apply in multiple installation
scenarios. Applicable scenarios for the current product releases include:
■ Performing a 7.8.2 full installation plus a 7.8.2.x patch installation

7.8.2.x Fix Packs
■ Performing a 7.8.2 patch installation (on top of existing 7.8.0 or 7.8.1.x) plus a 7.8.2.x patch
installation
NOTE: Slipstream patch installation does not apply if you are also adding new languages for version
7.8.2, as described in Installing New Languages. Such language packs must be installed after the
version 7.8.2 installation, and before version 7.8.2.x Fix Pack or other patch installation. You can add
any language after installing post-7.8.2 patches, but you must then reinstall these patches in order
to patch the language.
You configure slipstream patch installation by modifying the base siebel.ini files for each applicable
Siebel product in the 7.8.2 installation image. These siebel.ini files are also modified in installation
scenarios described in the chapter about unattended and console mode installations, in the Siebel
Installation Guide for the operating system you are using.
To support slipstream patch installation, where a 7.8.2 full/patch installation automatically invokes
a 7.8.2.x patch installation, modify the siebel.ini file for each applicable product for 7.8.2, 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
Examples for Specifying Execute Parameter

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

7.8.2.x Fix Packs
To configure slipstream patch installation for Siebel Mobile Web Client 7.8.2.x on Windows, the value
for Execute might be as shown below:
Execute = D:\Siebel_Image\7.8.2.x\Windows\Client\Siebel_Web_Client\install.exe
Configuring Multiple Slipstream Installations

Where another applicable patch release, such as a quick fix release for 7.8.2.x, is available at the
time you are configuring slipstream patch installation, you can include it in the slipstream patching
sequence. To do so, add Install2 = yes under the last entry in the [Slipstream] section, then
configure an [Install2] section, similar to how you created an [Install1] section.
Installing New Languages

This section provides information about installing new languages that were provided with version
7.8.2. Installing and deploying any of the new languages requires additional installation and
postinstallation tasks.
The additional languages provided with version 7.8.2 are:
■ Arabic (ARA)
■ Chinese Traditional (CHT)
■ Hebrew (HEB)
■ Swedish (SVE)
If you require any of these languages for a new version 7.8.2 installation, follow instructions in the
Siebel Installation Guide for the operating system you are using. Also review the remainder of this
topic.
NOTE: Customers who do not require any of the new languages do not need to install them, and
only need to install the current patch releases, as described in About Installing Patch Releases for
Siebel Products and subsequent topics.
For general information about language and patch installation, see Installation Overview.
After installing applicable patch releases and any new language, perform applicable tasks in
Postinstallation Tasks for Supporting New Languages.
Requirements for Installing and Deploying with Arabic and Hebrew

Languages
Deploying Siebel Business Applications with Arabic or Hebrew languages requires that you perform
various steps noted in Postinstallation Tasks for Supporting New Languages. The required tasks stem
from the right-to-left display characteristics of these languages.

7.8.2.x Fix Packs
■ Each Siebel Server on which Application Object Managers will run must support either languages
using a left-to-right display or languages using a right-to-left display.
In other words, you must dedicate particular Siebel Servers that will host Arabic or Hebrew
deployments of Siebel applications. Postinstallation steps you must perform for Arabic or Hebrew
deployments affect resources such as Siebel Web template files and cascading style sheet files,
which are shared by all applications on each Siebel Server.
■ A single Web server and Siebel Web Server Extension installation can support applications using
both left-to-right and right-to-left displays.
■ In order to install Siebel software, the system clock on the computer you are installing on must
be set to a Western calendar. After installation and the first login, the system can optionally be
set to another calendar setting, such as the Hijri calendar for Arabic.
Procedure for Installing New Languages

This section provides instructions for installing new languages (CHT, ARA, HEB, or SVE) for your
Siebel applications. To install any of these languages, perform the steps in this section for each
installable Siebel product.
These are high-level instructions. More details about many of the steps are provided in Installing
Patch Releases on Windows and Installing Patch Releases on UNIX and in the Siebel Installation Guide
for the operating system you are using.
See also Installation Overview and About Installing Patch Releases for Siebel Products.
Procedure steps differ according to which languages you require, whether you have an existing
version 7.8.2 installation image, and whether you are installing new languages as part of a new
installation or adding them to an existing installation.
NOTE: In general, it is assumed that you have already included any languages you will require in
your 7.8.2 installation images and product installations. If you did not, you can add languages to an
existing 7.8.2 installation image and add languages to an existing product installation.
Creating or Updating Installation Images to Include New Languages

Follow the procedure below to create or update installation images to include new languages.
To create or update installation images to include new languages

1 Run the Siebel Image Creator utility, with which you will create or modify your installation image
for version 7.8.2. Follow the prompts to create or modify your 7.8.2 installation image.
For details, see the Siebel Installation Guide for the operating system you are using. See also
About Running Siebel Image Creator.
■ If you do not already have a 7.8.2 installation image for your Siebel installable products, you
create it using this utility, and include any available languages you require (for example, ARA,
CHT, HEB, or SVE). You can also add products to an existing installation image; if you do so,
be sure to include all languages already included in the installation image.

7.8.2.x Fix Packs
■ Or, for an existing 7.8.2 installation image, you add any additional available languages you
require.
CAUTION: When you specify a directory in which to create a installation image, do not specify
a directory name that contains a space. For additional naming requirements, see the Siebel
Installation Guide for the operating system you are using.
2 Run Siebel Image Creator again to create an installation image for any applicable 7.8.2.x Fix Pack
release. Include any available languages you require.
3 (Where applicable) Run Siebel Image Creator again to create an installation image for any
applicable 7.8.2.x quick fix (QF) for the current Fix Pack release.
For more information, see About Installing Siebel Quick Fix Releases.
Installing New Languages in a New or Existing Installation

In the previous procedure, you prepared your Siebel installation images to include all the languages
you require.
Follow the procedure below to install new languages by including them in a new installation or adding
them to an existing installation. Performing this procedure requires that all languages you require
have already been added to the installation images.
To install new languages and install necessary patch releases

1 For a new 7.8.2 installation, run the Siebel installer for each product from the 7.8.2 installation
image you created or updated in Step 2 in the previous procedure. Install the product and include
any available languages you require (for example, ARA, CHT, HEB, or SVE). Then go to Step 4 in
this procedure.
For details about running Siebel installers and performing full installations of Siebel software, see
the Siebel Installation Guide for the operating system you are using.
2 For an existing 7.8.2 installation, run the Siebel installer for each product from the 7.8.2 installation
image you created or updated in Step 1 in the previous procedure. When prompted, specify the
existing installed instance of the product to which you are adding languages, and specify which
languages to install (for example, ARA, CHT, HEB, or SVE). Then go to Step 4 in this procedure.
For details about running Siebel installers and adding languages, see the Siebel Installation
Guide for the operating system you are using.
3 For an existing prior 7.8.0 or 7.8.1.x installation, perform both of the following steps for each
product:
a Install version 7.8.2 as a patch (maintenance release) from the 7.8.2 installation image you
created or updated in Step 1 in the previous procedure. When prompted, specify the existing
installed instance of the product on top of which you are installing 7.8.2. Any installed languages
are also patched.
For details, see About Installing Patch Releases for Siebel Products and subsequent topics for
Windows and UNIX.

7.8.2.x Fix Packs
b Run the 7.8.2 installer again. When prompted, specify the existing installed 7.8.2 instance of
the product to which you are adding languages, and specify which languages to install.
NOTE: As noted in Installation Overview, moving from version 7.8.0 or 7.8.1.x to version 7.8.2.x
requires that you also perform steps described in the Siebel Database Upgrade Guide.
4 for each product, install the latest version 7.8.2.x Fix Pack release on top of version 7.8.2. You
install from the 7.8.2.x installation image you created in Step 2 in the previous procedure. When
prompted, specify the existing installed 7.8.2 instance of the product on top of which you are
installing 7.8.2.x. Any installed languages are also patched.
For details, see About Installing Patch Releases for Siebel Products and subsequent topics for
Windows and UNIX.
5 (Where applicable) For each product, install an applicable 7.8.2.x quick fix (QF) release on top
of version 7.8.2.x. You install from the 7.8.2.x QF installation image (if you created one in Step 3
in the previous procedure). When prompted, specify the existing installed 7.8.2.x instance of the
product on top of which you are installing the 7.8.2.x QF. Any installed languages may also be
patched.
For more information, see About Installing Siebel Quick Fix Releases.
6 Perform additional steps to implement any new language, as noted in Postinstallation Tasks for
Supporting New Languages.
Postinstallation Task for the Siebel Server

If you are using a security adapter, then, after you have installed version 7.8.2 and 7.8.2.x patch
releases, you may need to update the value of the CRC parameter. 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 the
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 later installed
delivered an updated security adapter library file, the checksum validation will fail and Siebel Web
Clients may 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 these patch releases on all
server-based components: Siebel Server, Siebel Gateway Name Server, Siebel Web Server Extension
(SWSE), and so on.
The restart is required because the Web server must be able to create a folder to contain static files
required for the current version of the Siebel application (corresponding to the latest version 7.8.2.x
Fix Pack release). This folder is created as SWSE_ROOT/public/lang/build_number, where:
■ SWSE_ROOT = The location where the SWSE is installed

7.8.2.x Fix Packs
■ lang = 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 build-
specific 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
the 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 can be predeployed to the client machines.
This behavior applies to Siebel Web Client (using high interactivity only), Mobile Web Client, or
Developer Web Client.
For more information, see the browser configuration chapter in the Siebel System Administration
Guide and see Technical Note 418 (Doc ID 476952.1) on OracleMetaLink 3.
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.
Postinstallation Tasks for Supporting New Languages

If you are installing one of the new 7.8.2 languages (ARA, CHT, HEB, or SVE) into a version 7.8.2
installation that had been installed as a maintenance release (patch) on top of version 7.8.0 or
7.8.1.x, you must perform all applicable tasks described in this section.
Some tasks apply to scenarios in which you add any language to an existing installation, not just one
of the new languages. Some tasks do not apply for languages included in new installations.

7.8.2.x Fix Packs
For more information about some of these issues, see the Siebel Global Deployment Guide,
Configuring Siebel Business Applications, and applicable documents in Siebel Bookshelf on Oracle
Technology Network (OTN).
Running Srvrcfg Command to Create Language-Specific Object

Manager Components
After installing one of the new 7.8.2 languages (ARA, CHT, HEB, or SVE) in an add language scenario
(adding languages to an existing installation), you must run the srvrcfg command in order to
configure the language on the Siebel Server and create language-specific Application Object Manager
components.
NOTE: This task applies after you add any language to an existing installation. This task does not
apply for languages included in new 7.8.2 installations.
The srvrcfg command syntax is shown below:
srvrcfg -g gateway_name_server -e enterprise -a components -i

SIEBSRVR_ROOT\bin\lang\omdefs.dat -c ALL
■ Specify omdefs.dat for Siebel Business Applications (horizontal applications).
■ Specify omdefs_sia.dat for Siebel Industry Applications (vertical applications).
For example, enter a command similar to the following on UNIX, for Hebrew:
./srvrcfg -g gatewaymachine -e siebel -a components -i /export/home/sea78/siebsrvr/

bin/heb/omdefs.dat -c ALL
CAUTION: Before you run the srvrcfg command, you must stop the Siebel Server. However, the
Siebel Gateway Name Server must be running.
For more information, see the Siebel Global Deployment Guide.
Creating Language-Specific eapps.cfg File Entries

After you have installed one of the new 7.8.2 languages (ARA, CHT, HEB, or SVE) in an add language
scenario (adding languages to an existing installation where you installed 7.8.2 as a patch release),
you must manually create language-specific eapps.cfg file entries on the Siebel Web Server
Extension (SWSE) to support applications for those languages.
NOTE: This task does not apply when you add any language that had originally been provided with
version 7.8.0 or 7.8.1. This task does not apply for languages included in new 7.8.2 installations.
After you installed Siebel Web Server Extension (SWSE) version 7.8.0 or 7.8.1, virtual directories
were created and corresponding entries and associated parameters were created in eapps.cfg (or
similar files) on the SWSE. Entries were created for all languages that were supported for version
7.8.0 or 7.8.1.
After you have installed 7.8.2 as a patch release on top of 7.8.0 or 7.8.1.x, added all languages you
require, and installed the latest 7.8.2.x Fix Pack release, you must modify eapps.cfg to support
applications for new languages, as shown below.

7.8.2.x Fix Packs
Create language-specific entries for all applications you require. For example, for Siebel eSales on
UNIX, copy an existing eapps.cfg entry, such as [/esales_enu] for U.S. English (ENU), and modify
it to represent an equivalent Arabic (ARA) entry, such as [/esales_ara], similar to the following:
[/esales_ara]
AnonUserName = anonuser
AnonPassword = OsofSfgGq0u6BD8l+2YohAHLCnGx
ConnectString = siebel.TCPIP.None.None://Siebsrvr:2321/Enterprise/eSalesObjMgr_ara
StartCommand = SWECmd=GotoView&SWEView=Home+Page+View+(eSales)
WebPublicRootDir = /sea78/SWEApp/public/ara
WebUpdatePassword = fvfe39mKKKoBBACmSA==
Configuring Bidirectionality for the Siebel Server, for Arabic or Hebrew

Deployments
By default, Siebel applications display user interface elements from left-to-right. To use Siebel
Business Applications with Arabic (ARA) or Hebrew (HEB), you must perform various steps to change
the user interface directionality to a right-to-left display.
NOTE: This task applies for any deployment using ARA or HEB, whether for new 7.8.2 installations
or for add language scenarios.
For more information about some of these issues, see the Siebel Global Deployment Guide,
Configuring Siebel Business Applications, and applicable documents in Siebel Bookshelf on Oracle
Technology Network (OTN).
See also Requirements for Installing and Deploying with Arabic and Hebrew Languages.
After you have completed installation tasks in this chapter, you can run the BidiConf utility on any
Siebel Servers that are designated to host Application Object Managers for ARA or HEB. This utility
modifies Siebel Web template files and cascading style sheet files to support bidirectional capability
(to change from left-to-right to right-to-left display).
For detailed instructions on obtaining and running the BidiConf utility, see Technical Note 599 (Doc
ID 478224.1) on OracleMetaLink 3.
Technical Note 599 also notes that configuration files for the Siebel Mobile or Developer Web Client
(formerly known as Dedicated Web Client), if you are using those client types, must be configured
to specify user interface directionality.
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.

7.8.2.x Fix Packs
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 by Oracle 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
Configuring Siebel Business Applications. See also the 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.
2 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.
3 Click the Import tab.
4 Enter the name of the LMU file from which you want to import locale-specific attributes.
You can also use the Browse button to find and select the file.
5 Specify whether you want to mark records in the repository with the Redo flag that have changed
since the export occurred.
When the import occurs, the LMU compares the source language records in the repository with
the source language records in the import file. If the records in the repository have changed since
the export occurred, they are marked with the Redo flag. This helps you identify records that
may need to be retranslated.
6 Click Import.
7 After finishing, recompile the SRF file and restart the Application Object Manager component on
the Siebel Server to be able to see the results.
Installing Siebel Universal Customer Master

Siebel Universal Customer Master(UCM) is enabled in the Siebel application via a license key. You
should have received your Universal Customer Master license key in a letter. A supplementary CD
contains objects and data for you to import into your Siebel environment.
For more information about how to use the objects once you have imported them, see the Siebel
Master Data Applications Reference. The document is available under Product Documentation on
Oracle MetaLink 3 at https://metalink3.oracle.com, and updates are posted periodically.

7.8.2.x Fix Packs
The prerequisite for this installation is Siebel 7.8.2 SIA [19213]. The installation includes the
following two UCM zip files in the UCM directory under the $ROOT\Tools\REPPATCH folder:
UCMArchives.zip (Siebel Import Files) contains the UCM metadata:
■ Account BC.sif
■ Account BO.sif
■ Contact BC.sif
■ Contact BO.sif
■ UCM CDM Child Project.sif
■ UCM Data Management Project.sif
■ UCM Hierarchy Management Project.sif
■ UCM Merge Project.sif
■ UCM SDH Project.sif
■ UCM Survivorship Project.sif
■ UCM Unmerge Project.sif
■ VEAI UCM Account ASI Project.sif
■ VEAI UCM CIF Project.sif
■ VEAI UCM CIF UI Project.sif
UCMWorkflows.zip (Siebel Workflows) contains the business process flows for UCM messages:
■ UCM Account Batch Data Management Workflow.xml
■ UCM Async Realtime Publish Workflow.xml
■ UCM Batch Process - Single step.xml
■ UCM Batch Process.xml

■ UCM Contact Batch Data Management Workflow.xml
■ UCM Daily Publish.xml

■ UCM Server Party Package Workflow (File Transport).xml
■ UCM Server Party Package Workflow (MQSeries Server Transport Error Handling).xml
■ UCM Server Party Package Workflow (MQSeries Server Transport).xml
Use the procedures in the following section to install Siebel Connector for UCM into your Siebel
environment.
NOTE: If you are importing into your existing development repository that has modified objects that
belong to the impacted projects, you must export any changes made into SIF files, import the
changes using the procedure below, make sure to check the "Overwrite the object definition in the
repository" radio button in the Preview screen, compile all the changes, test to make sure that the
out-of-the-box UCM functions are working properly, and then import all the exported development
changes from SIF file to continue development.

7.8.2.x Fix Packs
To import Siebel Import files into your development repository

1 Unzip the UCMArchives.zip file and save the .sif files to your computer.
2 Make a backup copy of your existing Tools repository using the repimexp utility as described in
the Siebel Tools Online Help.
3 Launch Siebel Tools and connect to your development server.
4 Navigate to Project in the Object Explorer window, query for the following projects and lock
them: Account, Contact, UCM CDM Child, UCM Data Management, UCM Merge, UCM SDH, UCM
Survivorship, UCM Unmerge, UCM Hierarchy Management, VEAI UCM Account ASI, VEAI UCM
CIF, and VEAI UCM CIF UI.
5 Select Tools > Import From Archive.
6 In the Select Archive to Import box, navigate to the location of the *.sif file and click Open.
7 In the Import Wizard - Preview box, click the "Overwrite the object definition in the repository"
radio button and click Next.
8 After Tools has read the file, click Next.
9 When you see a dialog box stating the number of objects that will be modified in your repository,
click Yes.
10 In the Import Wizard - Summary box, click Finish.

11 Repeat Step 5 through Step 10 for each .sif file.
12 Compile the all affected projects into a new Siebel Repository File (.srf). The steps in the
following procedure assume that you are running your Siebel Web Client against an installation
that includes this new .srf file.
To import Siebel Workflow (.xml files) into your database

1 Unzip the UCMWorkflows.zip file and save the nine .xml files to your computer.
2 Launch Siebel Tools and connect to your Siebel database.
3 Navigate to Project in the Object Explorer window, query for the Siebel Workflows - Seed project,
and lock it.
4 Navigate to Workflow Process in the Object Explorer window.
5 Right-click on the Workflow Process applet and select Import Workflow Process from the applet
menu.
6 In the Workflow Process Import box, navigate to the location of the *.xml file and click Open.
The workflow file will be selected.
7 In the Select Project box, select the project name and click OK.
8 Repeat Step 5 through Step 7 for each Workflow *.xml file.

7.8.2.x Fix Packs
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.
Guidelines and Limitations

Note the following guidelines and limitations related to patch release uninstallation:
■ A release installed as a patch release, such as 7.8.2 installed on top of 7.8.0 or 7.8.1.x, or the
latest 7.8.2.x Fix Pack installed on top of 7.8.2, 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 7.8.x.
■ A release installed as a full release, such as 7.8.2 installed as a full release (as described in the
Siebel Installation Guide for the operating system you are using), can be uninstalled as a full
release. It cannot be uninstalled as a patch (effectively downgrading, such as from 7.8.2 to
7.8.1).
■ 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 7.8.2 as a patch release, and then
installed the latest 7.8.2.x Fix Pack, you would not be able to uninstall 7.8.2 (as a patch release),
even after uninstalling the 7.8.2.x release. You could still perform a full uninstallation of 7.8.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.

Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests
Resolved Change Requests

The tables in this section provide a complete list of resolved change requests that are included in
7.8.2 and 7.8.2.x Fix Packs. Customers using 7.8.1 should install 7.8.2 with the latest 7.8.2.x Fix
Pack. Customers using 7.8.2 or a prior 7.8.2.x Fix Pack should install the latest 7.8.2.x Fix Pack.
Unless specifically noted in this table, 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, as of the Siebel 7.8.2.10 Fix Pack,
the Resolved CR information for the current Fix Pack has been provided in its own table.
The Resolved Change Requests tables include the following columns:
■ Issue 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.
■ Customers upgrading from Siebel 7.5.x or 7.7.x to Siebel 7.8.2 should refer to Alert 1179: Siebel
7.8 Upgrade – Important Steps to a Successful 7.8 Upgrade (Doc ID 478177.1) on
OracleMetaLink 3 for important information about performing the upgrade.
■ Quick Fix Information: If you have installed a quick fix, review Quick Fixes Included in 7.8.2.x Fix
Packs.
Resolved Change Requests in the Siebel 7.8.2.14 Fix

Pack
Table 18 lists the change requests that were resolved in the Siebel 7.8.2.14 Fix Pack.
Table 18. Resolved Change Requests in the Siebel 7.8.2.14 Fix Pack
Fix Request Change Fixed in Configuration

Issue Addressed ID Request ID Version Instructions
General


Reports Server
Provides the following BI Publisher 12-1UJR2O5 12-1REE3K7 7.8.2.14 Yes, see
enhancements: “Instructions for
Oracle BI
■ Enables reports with
Publisher
parameters.
Enhancements”
■ Enables scheduling. on page 221.
■ Provides a new Web service to

support the new BI Publisher
security model.

Pack

Call Center
Other
If a SmartScript is running in SI 12-1Q356CA 12-1PCDHDP 7.8.2.13
mode, and it has two questions on
two separate pages, the focus is
not placed on the first question,
and when users click the Next
button, the focus is not placed on
the first question on the second
page
Comm Media
Energy
Order Management


ACR 471: If headless configuration 12-1SZ4WNB 12-1SXN45J 7.8.2.13 Yes, see

is used to adjust the CP definition “Instructions for
automatically based on CP ACR 471” on
definition, if page 219
PRESERVE_ENGINE_AND_USER_P
ICKS have been set to Y, and if
linked items have been used in in
the configurator model, during
Upgrade promotion, the CP
structure is not adjusted
ACR 471 provides several 12-1S624WD 12-1S85TE5 7.8.2.13 Yes, see
enhancements for promotions. For “Instructions for
a detailed list of what ACR 471 ACR 471” on
provides, see “Enhancements and page 219.
Updates in Version 7.8.2.13” on
page 44.
ACR 471: Users cannot disable the 12-1TK3LO6 12-1THNL1J 7.8.2.13 Yes, see
Promotion Automatch feature “Instructions for
ACR 471” on
page 219
ACR 471: Automatically sets 12-1S8QOCX 12-1MKB7V9 7.8.2.13 Yes, see

attribute values during a “Instructions for
promotion upgrade ACR 471” on
page 219
ACR 471: The system crashes 12-1TK3Z2H 12-1TK3Z1X 7.8.2.13 Yes, see
while executing iLog Rule Test case “Instructions for
ACR 471” on
page 219
Connectors/EAI
Other
The EAI Data Transformation 12-1NAM1JD 12-1MNQ3BZ 7.8.2.13
Engine outputs the target instance
when the source search
specification is not met
The EAI Data Mapper does not 12-1S5SIOK 12-1M6BZN3 7.8.2.13

correctly map external Integration
Objects to internal Integration
Objects


The UndoRecord throws the 12-1OXTBGY 12-1NJKY8V 7.8.2.13

"Argument not optional" error
message in Data Server
Customer Order
Management
Configurator
Changing a promotion or an 12-1S8QOBK 12-1PILEIJ 7.8.2.13
upgrade promotion on an order
line item does not update products
correctly
BatchValidate returns the wrong 12-1SJ5CDP 12-1SFPA4D 7.8.2.13

status on modified quotes
On the AIX platform, when users 12-1RKMAUN 12-1QUOKCX 7.8.2.13

configure a product and encounter
an error message, clicking the
Explanation button on the error
page causes the application to
crash
When the "Skip Loading Default 12-1SINGAX 12-VD0XNH 7.8.2.13

Cfg Instance" user property is set
to Y, a constraint violation occurs
for products that have required
attributes
Promotion default instances are 12-1SZ4WM9 12-1NNU3JH 7.8.2.13

created incorrectly when
promotion constraints and rules
are used
On the AIX platform, the Ilog 12-1TG6E8N 12-1SG6A0Z 7.8.2.13

engine crashes for more than 500
child products and a single
constraint
Order Management
Changing a promotion in a change 12-1S1XQR6 12-1P81O39 7.8.2.13
order does not load the default
product
The logging mechanism does not 12-1LEYQYD 12-1KWV58T 7.8.2.13

capture enough data about what
causes the application to crash


All event logs are incorrectly 12-1LD54HZ 12-1LD541G 7.8.2.13

redirected to Cfgscript.log
When users create a bulk order of 12-1SFP6VD 12-1S7POKB 7.8.2.13

type Modify and try to update
Start Date in the action set, the
start date on the order is not
updated
The Prod Prom Instance Id is not 12-1TK6J7M 12-1TG5VA9 7.8.2.13

populated during an 'Upgrade
Promotion' use case
Orders
Bulk order add scenario behaves in 12-1SW8RKH 12-1SB91UB 7.8.2.13
a different way between 7.8.2.6
and 7.8.2.11
The Add Items button does not 12-1FECB71 12-1F9JWBW 7.8.2.13

add products from the Product
popup applet to order line items
Products
The Promotion Constraint 12-1J2HZOZ 12-1HQ7I81 7.8.2.13
Administration tree does not
contain an indicator to show which
node contains the promotion
constraint
Revising a quote errors out if line 12-1GHNZ4K 12-1GCH7S5 7.8.2.13

items are copied in the local
database and synchronized to the
server
Quotes
General
Assignment Manager
Dynamic Assignment fails when 12-1NQ7VKS 12-1FFXV5U 7.8.2.13
multiple scoring occurs on non-
passing rules
Calendar


Clicking the Back button on the 12-1R3T5AM 12-1R3T5A1 7.8.2.13

calendar does not refresh the
calendar
Activity and Contact List missing in 12-1RYK34I 12-1RYK33X 7.8.2.13 Yes, see
the Weekly/Daily Calendar View “Instructions for
FR 12-1RYK34I”
on page 462.
Paritally visible calendar items 12-1SI5KKI 12-1SI5KJF 7.8.2.13

cannot be selected
When users work with a smaller 12-1RRBNQC 12-1REVSHX 7.8.2.13 Yes, see
window, not all appointments “Instructions for
display on the calendar, but even FR 12-
after users resize, the 1RRBNQC” on
appointments still do not display page 462.
Correspondence
Correspondence documents 12-1T2SVLS 12-1SJNUGJ 7.8.2.13
contain additional space
characters
Global/Multilingual LOV
MLOV field in child records is not 12-1T9SBLW 12-1Q3L025 7.8.2.13
correctly copied when copying a
parent record where the child
contains the MLOV inserts display
value
Message Broadcasting
Broadcast messages are not 12-1H1Y99P 12-1GUIPP1 7.8.2.13
displayed when the word "Same"
is used
Other
ACR 266/ACR 277: Supports 12-1NVW46A 12-16DUIYU 7.8.2.13
starting the ChartWorks engine
with QuickStart
The wrong SQL is generated when 12-1GVLEWI 12-1GGJVDF 7.8.2.13

EXISTS is used with two bind
variables and a joined field


When attach certifications using 12-1PSN4S7 12-1OQU1KJ 7.8.2.13

mwcontrol are installed, EAI HTTP
Transport is used to connect to an
MA-enabled server, when the
following is specified for
certifications:oInputs.SetProperty
("HTTPCertAuthority",
"CN=DPTIPSEC,DC=dwpptp,DC=l
ondondc,DC=com");// Set the
Serial Number of the
ClientCertificate
oInputs.SetProperty("HTTPCertSe
rialNo",
"1107BA79000000000002");
the certifications are not found
Performance
Double parsing without bind peek 12-1TK3QAM 12-1OQD0BB 7.8.2.13
in Oracle connector causes
performance degradation
PIM Server Integration

Provides the ability to use 12-1LTYZCO 12-1LTGS5B 7.8.2.13
Exchange as system of record for
calendar attendees
PIMSI Dispatcher does not filter by 12-1MQCB6P 12-1MIVDVK 7.8.2.13

user group
When an email address contains 12-1NH7ZBY 12-1FWL602 7.8.2.13

non-alphanumeric characters
(such as apostrophes),
synchronization does not occur
ACR 369: Updates the permissions 12-1O1KGEE 12-1O1KGDB 7.8.2.13

script to grant permissions using
Exchange Shell
ACR 481: Provides the ability to 12-1MQBY8I 12-1LY4V61 7.8.2.13 Yes, see
ignore Outlook appointments/ “Instructions for
tasks based on "Private" flag ACR 481” on
page 220.
Provides support for Outlook 2007 12-1P1AWHW 12-1OXSN8J 7.8.2.13

Embedded Outlook Calendar (ACR
369)


There is no email notification when 12-1RPHOBP 12-1RPHO7U 7.8.2.13

a record is not processed by
Exchange Connector
ACR 481: Addresses an issue 12-1MQCFE9 12-1MBR3N7 7.8.2.13 Yes, see

where the Outlook Add-in can lock “Instructions for
a user out of his/her account after ACR 481” on
they have changed the password page 220
on the authenticating agent (e.g.,
Active Directory), but have not
updated their Outlook Add-in
password
Contact categories other than 12-1QTPBH6 12-XLYU4T 7.8.2.13
"Siebel Contact" are not preserved
during outbound contact sync
Platforms
Internet Explorer crashes 12-1COXTWI 12-1CNSZDJ 7.8.2.13
frequently
DeepDelete functionality does not 12-1BIBOX6 12-18E1CY6 7.8.2.13

act defensively to avoid accidental
deletions, and a large amount of
data is lost
Remote
The Siebel local database becomes 12-1RZ10Y3 12-1RSS5YD 7.8.2.13
corrupted and displays insertion
errors
Reports Server
Removes Actuate from base media 12-1S6A0TD 12-1S4U9QQ 7.8.2.13
and Fix Packs
Security
When using SSL with High 12-1EOVJFK 12-DTWC3Y 7.8.2.13
Interactivity applications, users
receive the following error
message: "This page contains
both secure and nonsecure items.”


When ADSI security adapter is 12-1OG3CJ4 12-108H728 7.8.2.13

used with password syntax
enabled, entering a password that
does not conform with the
password policy yields the generic
error message SBL-SEC-10001
Server Infrastructure
The Object Manager Restart 12-1KF1UGS 12-1K2JB2N 7.8.2.13
feature restarts too many Object
Managers when an Object
Manager crashes
When shared objects are loaded 12-1KF4F8A 12-1KCQ5CJ 7.8.2.13

into Object Manager, an error
occurs during startup
When using the Siebel Server 12-1SQXF4J 12-1SOSTHT 7.8.2.13

Manager srvrmgr command line
mode to create a named
subsystem (create named
subsystem XYZ...), certain
command string combinations
may result in the following error:
SBL-CSO-09100: The Server
object (null) was not found.
A cursor leak occurs in Document 12-1RNYL7X 12-1QK0SEH 7.8.2.13

Server when nested
correspondence templates are
used
When users attempt to print, the 12-1SWPM7G 12-1K51E4X 7.8.2.13

application fails and displays an
error message
Clicking "X" on the browser 12-1T3HLFK 12-PUDQB1 7.8.2.13

window should terminate the
Siebel session on the server
State Models
State Models with "No Delete" set 12-1SCQFFB 12-1S5B2PJ 7.8.2.13
will not allow UndoRecord and will
cause an error
Tools/Configuration


When SetFieldValue is used on a 12-1IUKMDM 12-1IDQ8ML 7.8.2.13

bounded picklist, the Object
Manager crashes
Adding new indexes in Siebel Tools 12-1SWPM2B 12-1STC0LZ 7.8.2.13

using "Apply" fails
Workflow
The Workflow Process Mananger 12-1PJ38QA 12-1OLHNBT 7.8.2.13
crashes
Importing workflows may cause 12-1R3SIPZ 12-1OA5EFH 7.8.2.13

version mismatches and
deployment errors
When a trigger is created in a 12-1SGSZOE 12-1S8Q8LJ 7.8.2.13

version prior to Siebel 7.8.2.11
and the application is then
upgraded to Siebel 7.8.2.11, the
trigger may be incompletely or
incorrectly created
Life Sciences
Pharma Handheld for
Windows
All functionality that is based on 12-1NC2W1B 12-1MXLV6R 7.8.2.13 Yes, see
the Customer Id field does not “Instructions for
work FR 12-
1NC2W1B” on
page 461.
Service Requests
The Signature Capture view 12-1SOZHFL 12-1SBRA8B 7.8.2.13 Yes, see
becomes unavailable when users “Instructions for
accidentally press the Esc key FR 12-1SOZHFL”
on page 461.
Loyalty
Loyalty Engine
When a member has a negative 12-1TG588V 12-1Q5L7UL 7.8.2.13 Yes, see
balance, when a member “Instructions for
redemption transaction is FR 12-1TG588V”
cancelled, the point balance is not on page 461.
updated correctly


Loyalty Manager
The member creation process 12-1T4GFKV 12-1SW8N8V 7.8.2.13
creates multiple records
Marketing
Campaigns
Stage Execution fails with the 12-1SX7SKW 12-1STTN3F 7.8.2.13
error that the record has been
modified by another user
Campaign repeating tasks may 12-1TKAAG8 12-1THO6QN 7.8.2.13

repeat unexpectedly if record
contention occurs
Mobile Solutions
Handheld for Windows
CompanionSync PDA is able to 12-1QODYH2 12-1QJJ9PR 7.8.2.13
synchronize with another laptop
that has the same IP address
The "Drilldown View from HH 12-1RV767B 12-1R7NDX7 7.8.2.13

Calendar" user property is ignored
on WM5
When users attempt to 12-1S9RUVZ 12-1RVORD3 7.8.2.13

synchronize a PDA device with a
machine running Vista, the
synchronization fails
With WM5 and WM6 devices, when 12-1SZ4U1G 12-1SC9C45 7.8.2.13

certain characters are extracted
into dbfile.txt, the dbimport
synchronization step fails
Other
The router does not route 12-1K0VS0T 12-1J63EYJ 7.8.2.13 Yes, see
S_ORG_PROD although the visutl “Instructions for
reports that it is visible FR 12-1K0VS0T”
on page 249.
Sales
Forecasting


Internet Explorer 7 crashes if the 12-1S1Y0UI 12- 7.8.2.13

CTRL-S or Save Record functions 1QMWX5R
are invoked when the focus on is a
new field/column created in the
Forecast list applet after the field
value has been populated using a
picklist
ACR 504: Provides an integration 12-1U5SJVI 12-1U5SJUZ 7.8.2.13

to allow users to synchronize
accounts, contacts, opportunities,
and products between Oracle CRM
On Demand and Siebel CRM
(Siebel CRM On Premise) for both
Siebel Enterprise Applications
(SEA) and Siebel Industry
Applications (SIA) and for all
available platforms.
When the relationship between 12-1T7V96H 12-1T21JMR 7.8.2.13

two accounts is modified, the
entire account hierarchy is rebuilt,
which causes poor performance
Service
Other
The ResolveDuplicates function for 12-1PAX5TM 12-1OA5AGP 7.8.2.13
inventory transactions produces
incorrect results for serialized
products
Performing queries in the Assets 12-1SJNUGA 12-1SJNUFP 7.8.2.13

view causes performance issues
Scheduling
The Dispatch Board does not allow 12-1F1W7G4 12-1EPYD4P 7.8.2.13
small appointment overlaps
GanttChart AX Applet does not 12-1R3SR0U 12-1Q0IVS7 7.8.2.13

work in multilingual environments
Siebel eMail
Response
General


The Siebel Native Client mail 12-1QXK394 12-16EFGPH 7.8.2.13

transmission retry strategy does
not function
Provides an addtional output 12-1S1XELX 12-1JGY6HC 7.8.2.13

argument from the CreateRequest
method from the Outbound
Communications Manager BS to
return the activity id of the
outbound email activity generated
automatically by the
CreateRequest method
Universal
Customer Master
Data Management
The UCM Transaction Manager 12-1SUB19K 12-1S5B2FT 7.8.2.13
Business Service issues a query
even though the crmml message
has IXMLOperation_QUERYPAGE
User Interface
Layout and Rendering
Parameterized reports do not work 12-1DTOBP5 12-TRBP9F 7.8.2.13
in the read-only view
When users delete the contents of 12-1R0WJQB 12-1PBVEEP 7.8.2.13

a required field and then click
Save, an error message appears,
but when users dismiss the error
message, and reenter the data
that they deleted, the data is not
saved
Navigation
With Internet Explorer 7, when 12-1RZ1O5X 12-1R4A1RB 7.8.2.13
users select a record on the
Employee Type picklist and press
the Enter key, the cursor returns
to the previous field


Closing a window with the X 12-1TD3XR1 12-1SZMHGR 7.8.2.13

causes a new anonymous session
to start
Other
The Refine Query function does 12-1L8TKFA 12-1KUDS47 7.8.2.13
not work in a predefined query
that contains an EXISTS clause
Crash in 12-1B9YQYA 12-NNSJOJ 7.8.2.13

CSSHtmlRenderer::ShowSWETagA
ppletAssocMvgE CRASH_EBIZ 8/2/
04
When users perform a query in a 12-1TK63G0 12-1TGO4KR 7.8.2.13

list applet and the current record
in focus is not the first row, the
first row of data is overwritten with
the query parameters
Popups/Pick Lists/
MVG/Shuttle
When users attempt to select a file 12-19F4LT1 12-18T7GRN 7.8.2.13
name from the Microsoft file
browser dialog from an
attachment applet while in query
mode, existing data in the file
name field may be overwritten
upon return from the dialog
After 7.7.2.6 SIA QF0165 has been 12-1QMXR7O 12-1FW28NC 7.8.2.13

applied, shuttle applets land in the
wrong place
If no value is supplied for a 12-1T139GK 12-1RSS41H 7.8.2.13

required field, users receive an
error message, but even after they
have entered the required
information, the error message
continues to appear


Toolbars/Menus/
Keyboard
After users use the keyboard 12-1HTY9WA 12-1HCLBH7 7.8.2.13
shortcut to jump to the next applet
(Ctrl+Shift+[), and press the Tab
key, the focus jumps to the next
applet, not the next field

Pack

Issue Addressed # Request # Version Changes
Call Center
CTI
The output arguments "Status" 12-18I6PDP 12-WHE0WB 7.8.2.12
and "ComRequestId" for the
Create and Submit Request
method (which is part of the
Outbound Communications
Manager business service) do not
return values
After 7.8.2.3 QFJ316 has been 12-1RRBR5N 12-1RPEWYN 7.8.2.12

applied, CTI toolbar worker
threads loop infinitely
The Communications toolbar 12-1S0YV8G 12-1RXY8FA 7.8.2.12

freezes if it receives an HTTP
message that contains no content
after a push connection request
Other


In Standard Interactivity Plus 12-1IM67NE 12-1GUIBBW 7.8.2.12 Yes,

mode, when users press the TAB “Instructions for
key to navigate through the FR 12-
application, they receive an error 1IM67NE” on
message page 463
Even when the No Activities 12-1J7ZOLV 12-FOURWR 7.8.2.12

option has been set, when users
navigate to the Contact view,
select a record, press F9,
compose an email, and send it
out, an activity record is still
created
When Contact Denormalization is 12-1QCBI1F 12-1PG85QP 7.8.2.12

run, PR_ADDR_ID is not being
populated
After 7.8.2.6 QF0640 has been 12-1MVQFCR 12-1MSUM5D 7.8.2.12

applied, newly-created activities
lose visibility
Comm Media
Energy
Order Management
Within the Sales Order screen, 12-1RZJ9LH 12-1R75AA5 7.8.2.12
when users select the order
number, navigate to the order,
select line items, select an item,
click Customize, select an item,
and then navigate out of the field,
they receive an error message
that the item was not found, and
when they navigate to the
Accounts screen, the Object
Manager crashes
Connectors / EAI
EAI Server
Components
XML messages with namespaces 12-1S2WDU5 12-1PE9R41 7.8.2.12
starting with _ cannot be
processed


Other
All messages sent to JMS go as 12-1RZ1OC1 12-1RAJ07R 7.8.2.12
BytesMessage, regardless of
whether the data is String/Binary
The message names included in a 12-1QQAA3P 12-1Q626EV 7.8.2.12

WSDL generated by Siebel for an
inbound web service changed
between Siebel 7.8.2.3 and
Siebel 7.8.2.6 from
<ServiceName>_<OperationNam
e>_<Direction>
(for example:
Siebel_spcAccount_SiebelAccoun
tInsert_Input) to
<OperationName>_<Direction>
(for example:
SiebelAccountInsert_Input), so
external applications cannot
consume the version 7.8.2.6
WSDL
Object Manager tasks are not 12-1QUOIJN 12-1OI2RO5 7.8.2.12

reused when a Siebel exception
occurs using JCA/Siebel Resource
Adapter
Consumer Sector
Handheld
With PocketPC, when users click 12-1PLH2YS 12-1OQU1AX 7.8.2.12
the Deliver button, they receive
an error message, and the
hourglass hangs
Customer Order
Management
Configurator
Within Siebel 7.8.2 SIA, the 12-1DVEAHP 12-1D2D48G 7.8.2.12
NUMBER/INTEGER attribute value
does not display correctly in the
SI User Interface


Error messages always display 12-19ENK76 12-19ENK5T 7.8.2.12

the first invalid linked item
When users click the Customize 12-1CAOZ37 12-1BDXE8B 7.8.2.12

button to correct a conflict for
Upsell Recommendation, the
application crashes
In SI mode, even though the UI 12-1RNGTE1 12-1BAI1CD 7.8.2.12

control Combo Box with Add
Button is set, the Quantity box is
missing
The RemoveItem detailed logging 12-1MZ3WPH 12-1MBQBIO 7.8.2.12

function is not available
Users receive an "Invalid 12-1QHMYZA 12-1PWMKNX 7.8.2.12

operation - error" error message
when selecting a record in a pick
applet
Configurator Rules and the 12-1Q35692 12-1PLY5DH 7.8.2.12

Structure Default behavior that
worked in previous versions of
Siebel applications does not work
on version 7.8
Batch Validate should set the 12-1R75ARV 12-1R1VGAZ 7.8.2.12

status to invalid and populate the
error message when validating a
missing required attribute
Order Management
Cursors remain open after a 12-1QZXUOJ 12-1QZXUMT 7.8.2.12
promotion creates an agreement
After QF0560 has been installed, 12-1LMZ3JO 12-1LMD4PF 7.8.2.12

validations do not recognize
invalid promotions
A validation problem occurs with 12-1Q7IPVZ 12-1PQ8RSX 7.8.2.12

inserting and associating a record
from an MVG applet
Other


A defect in the ADMImport 12-1QRS824 12-1Q92LOD 7.8.2.12

method of the ISS Authoring
Import Export Service prevents
the ADMImport method from
being able to successfully support
name changes to the destination
environment
The application crashes when 12-1R0X0DT 12-1QR99W7 7.8.2.12

upsell/cross sell messages are
still queued
ADM Workspace file import fails 12-1RAJ8M6 12-1PT60R3 7.8.2.12 Yes, see
“Instructions for
FR 12-
1RAJ8M6” on
page 463.
Data Quality
Deduplication
Accounts cannot be created when 12-1SX79NJ 12-1SWPNBV 7.8.2.12
real-time deduplication is turned
off
Financial Services
Other
Users cannot select multiple 12-1PVLXUH 12-1ETZHUF 7.8.2.12
records when dynamic toggle is
used
Within Siebel Financial Services, 12-1G2PJWA 12-1F2F46O 7.8.2.12 Yes, see

when users navigate to the "List “Instructions for
Management" screen, click on the 12-1G2PJWA”
Create Activity button in List on page 462
Management, and then select a
template and execute it, they
message: "No association list is
available in this applet.(SBL-DAT-
00276)".
General
Activities


The Activity alarm still pops up 12-19NEZQQ 12-10KGDOU 7.8.2.12

after the user has clicked Snooze
and then has set the Activity to
"Done" status
Within Siebel 7.8.2.10, when 12-1QRT6ZF 12-1QJ1W43 7.8.2.12

users attempt to update the
Planned Date and Due Date fields
using the Action Business
component through workflow
processes, the inserted values are
not saved to the database
Application
Deployment Manager
Whe implementing ADM for Smart 12-1QX24X5 12-1Q71PVP 7.8.2.12
Scripts, the import process simply
ignores the end of line
Assignment Manager
Interactive Assignment Manager 12-1MSUSAH 12-1M81BSP 7.8.2.12 Yes, see
does not work with Rule Groups “Instructions for
set FR 12-
1MSUSAH” on
page 462.
Business Rules
Data Validation Manager opens 12-1Q06YW7 12-1PLG9R7 7.8.2.12
database cursors and forgets to
close them
Calendar
Unable to translate day and 12-1Q06QPH 12-1PLH0JN 7.8.2.12
month names
When users create a repeating 12-1QG6MCY 12-1QEA3I9 7.8.2.12

appointment with a daily
frequency, save the appointment,
drill down on the same
appointment for a date other than
the start date, and then change
the duration of the appointment,
they receive the "Invalid
operation while not in update
mode" error message


When users attempt to delete a 12-1QG6MEJ 12-1QG6MDD 7.8.2.12

Repeating Appointment, they
receive the 'The selected record
has been deleted by another user
since it was retrieved. Please
continue (SBL-DAT-00494)' error
message
Events that cross a day boundary 12-1QK1BM5 12-1OTU3FT 7.8.2.12

are not shown on the second day
When a meeting is dragged and 12-1QR97EQ 12-1QER4QN 7.8.2.12

dropped, the duration is reset to
the default duration
File System
Modified dates of attachments are 12-1E3SL4S 12-1DRKC6T 7.8.2.12
updated even if the applet
runtime property is equal to True
in WinXP FAT
Installation
The option to install Siebel 12-1S6A0RJ 12-1S4U9OZ 7.8.2.12
Reports Server should not display
The 12-1S8Q83S 12-1S8Q837 7.8.2.12

ACR347RepSeedFiles_v782.zip
file is not present within Siebel
7.8.2.11 SIA
Office
Provides support for Microsoft 12-1L1B1VT 12-1IDNOO9 7.8.2.12 Yes, see
Office 2007 with Document “Instructions for
Server and Siebel Search (ACR ACR 409” on
409) page 198.
Other
The link property "Inter Child 12-1EFFC2H 12-1BYUKN7 7.8.2.12
Delete" does not work when there
is a value in “Source Field”
Using the Date Object in eScript 12-1QWKP5L 12-1QJJ9X9 7.8.2.12

may give incorrect results


After users change the default 12-1FYLM0Y 12-1EWWS2H 7.8.2.12

class for the Responsibility
Business Component from
CSSBCBase to CSSBCRole, the
Object Manager crashes
Incorrect behavior occurs when 12-1BRN1UM 12-19M9UDE 7.8.2.12

users click the Cancel button on a
Multi-Value Group applet when
Inter Child Delete is TRUE
An Object Manager crash occurs 12-1Q9IBIN 12-1PILZ4H 7.8.2.12

several times a day in version
7.8.2.4
Tables such as S_LOCALE and 12-1PF9K47 12-TUKTPU 7.8.2.12

S_CURCY have records that are
invalid in EBCDIC CP. This issue is
specific to DB2-390
Using the Analytics ODBC driver 12-1RBI8W5 12-1KIMIIJ 7.8.2.12

to connect from Siebel Customer
Relationship Management to
Oracle Business Intelligence,
Enterprise Edition, version
10.1.3.2 results in truncated
records
Performance
The Oracle database is not able to 12-1R0WUXF 12-1QYIMX6 7.8.2.12
perform bind variable peeking
and uses index full scan on
s1.ASSET_NUM, which causes
major performance degradation

If the "Category Field" for the 12-1QDR9A1 12-1QBCIEN 7.8.2.12
contact domain is changed from
the default "Category," contact
matching fails during
synchronization
SSSE skips record-level failures 12-1QT8F4O 12-1QT8EZN 7.8.2.12 Yes, see

of any kind during integration “Instructions for
FR 12-
1QT8F4O” on
page 464.


Remote
Orphaned records caused by 12-1B5F2V1 12-188ALUO 7.8.2.12
merging contacts are not rectified
properly by Siebel Remote
Product and part number fields 12-14WF2EQ 12-14WF2CF 7.8.2.12

cannot be amended on the Mobile
Web Client
The database schema kit drops 12-1K1EMAH 12-X29RUP 7.8.2.12

and recreates 177 indexes,
regardless of whether or not
there are changes
Transaction Merger fails because 12-1PKZCZU 12-1NWLI7J 7.8.2.12

single byte ROW_ID is duplicated
Lock on S_DOCK_SESSION with 12-1REVPM9 12-1QXJVFB 7.8.2.12

MS SQL Server 2005
Siebel Remote transactions 12-1RV6TJ8 12-1RV6TB8 7.8.2.12

generated by Copy Event Plan do
not route correctly (with
DeepCopy)
Reports Server
Error messages were 12-1N68H9C 12-1ME997V 7.8.2.12
incompletely localized into the
Czech language
Security
LDAP Security adapter crashes 12-1S4C8E9 12-1PE9R2X 7.8.2.12
when used with Global Catalog
parameters
Active X controls overflow issues 12-1S6A27R 12-1OA5EPH 7.8.2.12
can cause a security vulnerability
Using AES 256 encryption on 12-1JTFZRB 12-1J1ZOUE 7.8.2.12

7.8.2.5 SIA causes the Object
Manager to crash
Clicking the Back button 12-1JY2DY3 12-1JTG6V1 7.8.2.12 Yes, see
repeatedly within Internet “Instructions for
Explorer deletes records from FR 12-1JY2DY3”
Calendar on page 462.


The eCommunications Object 12-1KF1UJW 12-1K207A0 7.8.2.12

Manager crashes when the CTI
connection disappears
After 7.7.2.6 QF06AJ has been 12-1REE3XO 12-1RBZ5QV 7.8.2.12

applied, the Object Manager
crashes when users attempt to
use Query Assistant
A SRProc crash/timeout occurs on 12-1REW47B 12-1QTP7FD 7.8.2.12

server startup, and jobs remain in
the "Queued" state
Tools / Configuration
If script that raises an error using 12-1QQ9WZM 12-1PLG9OF 7.8.2.12
RaiseErrorText is placed in the
WebApplet_Load event of some
applets, the error is not
displayed, but the entire script is
displayed
Workflow
Workflow policies triggered on 12-1QUO60R 12-1QBCC09 7.8.2.12
extension tables do not fire
actions
iHelp
Administration
OM crash when importing iHelp 12-1P2RY7M 12-1P2RY57 7.8.2.12
topics in Czech
Life Sciences
Other


Within the Life Sciences Pharma 12-1J2I89J 12-11WYHRI 7.8.2.12

HI Activity Calendar view, when
users create a contact call by
dragging and dropping from
contact (Pharma Calendar
Professional List Applet) to the LS
Pharma Activity HI Calendar
Applet, and then drag and drop
the record to another time, the
start date displays as updated in
the activities list applet but the
Pharma Professional Call Form
Applet still displays the previous
time
Pharma Handheld for

Windows
The select button on the Columns 12-1O0507T 12-1EJHTCR 7.8.2.12
Displayed view is not available on
the non-ENU Pharma Handheld
application
Mobile Solutions
Handheld error message do not 12-1NLY7WT 12-1NB2IGZ 7.8.2.12
appear on screen for CZ installed
PDA
The Handheld 'Edit' and 'View' 12-1NMWEHG 12-1KRRD8P 7.8.2.12
menu text are empty in 7.7.2.8
ePharma Czech-language
application on WM5 devices
240x240 display not recognized 12-1NMVUJ6 12-1KQW9WG 7.8.2.12

with CSY language
Dbimport hangs occasionally 12-1P8IZ2S 12-1OLL617 7.8.2.12

during companion
synchronization
Within the Service Handheld 7.7.x 12-1PWM4VO 12-1N20QGN 7.8.2.12

application, most invoice
signatures do not display on the
Web Client


Handheld PatchAgent fails when 12-1Q0MF3L 12-1PPAE9M 7.8.2.12

UserDefinedLang=Y and the
userstr.txt file exists on the PDA
device
Within the Handheld dbimport 12-1QL04P7 12-1QFPJ7Z 7.8.2.12

logging file, information about
non-database-related steps such
as file creation or file deletion is
missing
After users perform a Full Sync on 12-1RAJ8J0 12-1NG9XVD 7.8.2.12

the device side, create some
transactions, sync, and then
select Upload Now, Auto
Download Later option, the Siebel
Handheld Sync screen signs off
with no transaction errors.
However, when the device starts
to poll the server for the
extracted database file, the first
polling attempt is fine, but the
second polling attempt fails.
The No Delete property is ignored 12-1NR67M5 12-1562WAI 7.8.2.12

in Siebel Handheld daily and
weekly calendar applets
Store-and- Forward
Messaging
The "SMQ Process User Queue" 12-1RRTKEU 12-1QR98KH 7.8.2.12
workflow can create duplicate
records in case of MQe problems
Database import sporadically fails 12-1QL0553 12-1QFOUWX 7.8.2.12
silently in the last steps and
prevents any further use of the
application
ACR 444 provides the following 12-1QR8QK8 12-1O2HQ4R 7.8.2.12

enhancements:
■ A utility for administrators to

act on failing Store and
Forward transactions.
■ Enhanced logging
capabilities(Server)


Public Sector
Other
After QF0593 has been applied, 12-1R4AJP5 12-1QEA1TZ 7.8.2.12
within Siebel Public Sector, when
users open an associate or pick
applet from any screen, and then
click the double-arrow button to
move to the next record set, the
application does not respond and
the users see either an "Error
connecting to the server" error
message or the "Method
GotoNextSet is not allowed here
(SBL-UIF-00348)" error message
Accessibility
Section 508: Spell Checker does 12-1GTW55B 12-1F5JWPT 7.8.2.12
not display misspelled words
properly in the Contacts screen
Sales
Other
If Primary Bill To and Primary Ship 12-1HG23OP 12-1HBHRBT 7.8.2.12
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
Enhances the "Generate 12-19FL9KE 12-IKU3V0 7.8.2.12

Hierarchy" button performance so
that it can process a large number
of records (ACR 302)
By default, the Update Hierarchy 12-1E8NZLH 12-1E7IDSF 7.8.2.12

process is limited to 10,000
records (ACR 302A)


The Primary ID of the Bill to and 12-1JJHN0A 12-1JDTN8Z 7.8.2.12 Yes, see
Ship to Contact is not updated “Instructions for
when the contact is deleted from FR 12-1JJHN0A”
the Accounts > Contacts view on page 462.
Provides an integration to allow 12-1ROFMHZ 12-1JTG2I5 7.8.2.12 Yes, see

users to synchronize accounts, “Instructions for
contacts, opportunities, and ACR 460” on
products between Oracle CRM On page 219
Demand and Siebel CRM (Siebel
CRM On Premise) for Siebel
Industry Applications (ACR 460)
For information about a known

issue associated with ACR 460,
see “Instructions for ACR 460” on
page 219.
ACR 460: Oracle CRM On Demand 12-1SJ53FD 12-1SGODNM 7.8.2.12
and Siebel CRM On Premise
integration: When users change
the primary contact from the
account parent level, the
transaction is not synchronized to
On Premise
ACR 460: Oracle CRM On Demand 12-1S4YW40 12-1S4YW3J 7.8.2.12

integration: when users attempt
to merge contact and account
records between On Premise and
On Demand, they receive the
following error message: Method
OPMergeToOD is not allowed
here. (SBL-UIF-00348)
ACR 460: Oracle CRM On Demand 12-1S5SKG9 12-1S5SKEZ 7.8.2.12

integration: contact information
does not synchronize from the
Japanese-language version of On
Premise to On Demand


ACR 460: Oracle CRM On Demand 12-1S5SKHU 12-1S5SKGK 7.8.2.12

integration: within On Premise,
when users create an account
record, drill down on the account,
and then navigate to the More
Info tab, the Organization field
does not appear
ACR 460: Oracle CRM On Demand 12-1S5SKJ9 12-1S5SKHZ 7.8.2.12

integration: the External Host
view is not present within the
Products screen
ACR 460: Oracle CRM On Demand 12-1S5SKKS 12-1S5SKJI 7.8.2.12

integration: users receive an
error message when they try to
create a product
ACR 460: Oracle CRM On Demand 12-1S5SKM7 12-1S5SKKX 7.8.2.12

integration: after users create an
account, the Organization
column is missing
ACR 460: Oracle CRM On Demand 12-1S5SKNM 12-1S5SKMC 7.8.2.12
integration: Sync Status values
does not appear after a contact
has been created
ACR 460: Oracle CRM On Demand 12-1S5SKP1 12-1S5SKNR 7.8.2.12

integration: the Integration User
column is missing


ACR 460: Oracle CRM On Demand 12-1S5SKRV 12-1S5SKQL 7.8.2.12

integration: within On Premise,
when users create an account,
synchronize it to On Demand,
associate an address to the
account within On Premise, verify
that the address information
synchronized to On Demand, and
then delete the address from On
Premise, the address is not
deleted from On Demand
ACR 460: Oracle CRM On Demand 12-1S5SMCW 12-1S5SKS2 7.8.2.12

integration: when users log into
On Premise, navigate to Account
> Account List, create an account
with values in the custom field,
and then synchronize the record
to On Demand, the updates do
not appear within On Demand
ACR 460: Oracle CRM On Demand 12-1S5SMEV 12-1S5SMD1 7.8.2.12

integration: when users create an
opportunity that contains a Lead
Source value and sync it to On
Premise, the information is not
synchronized to On Premise
ACR 460: Oracle CRM On Demand 12-1S5SMGA 12-1S5SMF0 7.8.2.12

integration: when users update
an existing product's net price
within On Premise, the update
does not display within On
Demand


ACR 460: Oracle CRM On Demand 12-1S5SMHP 12-1S5SMGF 7.8.2.12

On Premise, navigate to
Opportunity > Opportunity List,
click the New button to create a
new opportunity, sync the
opportunity to On Demand, and
then navigate to the Opportunity
External Host list applet, the
Synchronization Status and
Synchronization Description
values display as read-only
ACR 460: Oracle CRM On Demand 12-1S5SMJG 12-1S5SMHW 7.8.2.12
integration: after users have
associated a new account to a
contact, the change is not
synchronized from On Premise to
On Demand
ACR 460: Oracle CRM On Demand 12-1SC8EWH 12-1SC8EV7 7.8.2.12

On Premise and navigate to Site
Map > Admin - User > Employee
List Applet, the Siebel CRM
Integration User Flag is not there
ACR 460: Oracle CRM On Demand 12-1SGODMX 12-1SGODLN 7.8.2.12

On Premise, navigate to Account,
create two accounts and
associate the On Demand host to
them, query for the two newly-
created accounts, and then use
the application-level menu Merge
Record option, the accounts are
not merged in the On Demand
application
ACR 460: Oracle CRM On Demand 12-1SK5KYW 12-1SJ53G2 7.8.2.12

integration: delete triggers are
not being generated on Solaris


ACR 460: Oracle CRM On Demand 12-1SN6XRI 12-1SN6XQ9 7.8.2.12

the application, navigate to Site
Map > Admin - Data > List of
Values, and query for the
SYNC_STATUS value in the
TYPE_VALUE column, they do not
see any values for SYNC_ON for
the Japanese language
The Accounts Summary view does 12-1J1G8VP 12-1GO70DP 7.8.2.12

not display correctly after Siebel
7.8.2.3 has been applied
Service
Logistics Manager
When the Field Service Fulfillment 12-1R7NKMJ 12-1PWMP5B 7.8.2.12
Service GenPickTickets method is
used, the session is terminated
Other
Entitlement adjustments are 12-1H808LF 12-1H2GOJH 7.8.2.12 Yes, see
calculated incorrectly “Instructions for
FR 12-1H808LF”
on page 462.
Preventive
Maintenance
PM Engine is not releasing the 12-1QR9AZX 12-1Q0IVOB 7.8.2.12
database open cursors, which
creates a memory leak
Scheduling
Using the browser's Back Button 12-1P19QD8 12-1OB4K97 7.8.2.12
causes inefficient queries against
S_EVT_ACT
Siebel eMail
Response
General


When F9 is integrated to the 12-1RBHO94 12-1Q35O1B 7.8.2.12

Outlook application and the user
select two contacts as the
recipients in the Outlook email
message, the Outbound activity is
only associated to the second
contact
Siebel Smart Answer

The Smart Answer Import 12-1QKIA73 12-1PT60OB 7.8.2.12
functionality does not import new
categories
User Interface
Controls
Query assistant causes the 12-1QBCUDD 12-1MTD3AQ 7.8.2.12
application to crash when no
fields are selected
List applets show in collapsed 12-1NP9G4R 12-1N22X1J 7.8.2.12

mode even when records are
present
Form Redirect uses POST, not GET 12-1RFCLU5 12-1O2IS17 7.8.2.12

as documented

The vertical page scroll bar does 12-1PBDZCW 12-1PBDZC1 7.8.2.12
not work correctly
When users attempt to use the 12-1PCCOGY 12-1PCCOFR 7.8.2.12

vertical scroll bar, the application
crashes
Navigation
Within Server Management > 12-1R75V4P 12-1Q71PT7 7.8.2.12
Components, when users scroll
down using the second arrow,
within a couple of seconds, the
application session quits
Toolbars/Menus/
Keyboard


After QF0277 has been applied, 12-1RBHPX2 12-1QWNHQL 7.8.2.12

Edit menu options are unavailable
Web Service
Other
When a Siebel Inbound Web 12-1QDAA5N 12-U7Q5X7 7.8.2.12
Service that is based on a Siebel
account returns a large-sized
SOAP response, the EAI OM log
and SWSE log record errors and
the Web service client receives a
HTTP 500 error

Pack
Table 21 lists the Change Requests that are included in the Siebel 7.8.2.11 Fix Pack.
Change Fixed in Configuration

Issue Addressed Fix Request # Request # Version Changes
Analytics
Pharma Analytics
When the Analytics Create Target 12-1PILAB9 12-1PBVEDV 7.8.2.11
List is used on HP Unix Row Ids,
Contact or Account records over
six characters are truncated
when they are saved into the
Siebel database
Call Center
CTI
Different CCA driver instances 12-1PPRJ5C 12-1POB92U 7.8.2.11
use the same customId


If the focus is in the Siebel CTI 12-1PMWMYI 12-1PILZ2T 7.8.2.11

toolbar, applet menu hot keys do
not work
The CTI toolbar hangs 12-1OYAWWN 12-1OUTTE9 7.8.2.11
Other
Within SmartScripts, there is no 12-1QBCEZ4 12-1PG85AB 7.8.2.11
text wrapping within text box
controls
Search operations using Search 12-1P7KCMT 12-1MCAAK1 7.8.2.11
Center intermittently hang
When users invoke a 12-1P64W4H 12-1OVTSLR 7.8.2.11

SmartScript, answer the
questions, and click Finish, both
Opportunity and Quote records
are created, but only an
Opportunity record should be
created
Comm Media
Energy
Billing Management


ACR 428 provides the following 12-1PEQMTD 12-1NWUB8D 7.8.2.11 Yes, see
enhancements: “Instructions
for ACR 428” on
■ New billing management
page 208.
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 one-
time charges, promotions,
customizable product pricing,
and asset-based ordering
enhancements
■ Nested Service bundle

Payment confirmations are not 12-1R0F3IO 12-1R0F3HX 7.8.2.11
displayed
Within the CMU Billing Profile 12-1QPT4JM 12-1QR979C 7.8.2.11

Portal Screen, CMU Balance
Group view, the View Detail
button is missing
eSales
After users click the Check Out 12-1QY0Y1B 12-1QY0Y0L 7.8.2.11 Yes, see
button in the shopping cart, “Instructions
select shipping and billing for FR 12-
details, click the Confirm Order 1QY0Y1B” on
button on the Order Summary page 468
page, and click the Submit
button, they receive the following
error message: Error running
sub-process '<?>' at step
'<?>'.(SBL-BPR-00183)
Order Management


Within the Account Summary 12-1QPT2HG 12-1QR976A 7.8.2.11

view > Installed Assets list
applet, when users click the
Modify button, they receive an
error message
Within the Sales Order screen, 12-1QPT2H4 12-1QR975B 7.8.2.11

after users enter an order, submit
the order, and click the Auto
Asset button within the Sales
Order Line Items screen, they
receive an error message
Within the Sales Order screen, 12-1QPT2GS 12-1QR977T 7.8.2.11

users receive an error message
when they select the Suspend,
Resume, or Disconnect options
Other
Product synchronization does not 12-1R0F3JN 12-1R0F3IY 7.8.2.11
work because BPEL instances are
not initiated
Connectors / EAI
Other
Poor performance occurs when 12-1OB50JG 12-1NZODFZ 7.8.2.11
XML Hierarchy Converter
processes escaped characters
Users encounter synchronization 12-1NZNY93 12-1NWENJ9 7.8.2.11
problems with the M:N
relationship
Consumer Sector
Other
The following views are missing 12-1P0S6H9 12-1P0S6GP 7.8.2.11
from Consumer Goods Base
options:
■ Catalog Admin Detail View –

Products
■ FINS Approval Administration

View


Customer Order
Management
Configurator
The Customize icon should not 12-1Q2NH08 12-1GVJ1I5 7.8.2.11
appear within a Configurator
session for child items that have
product type marked as 'non
structure’
The Standard Interactivity User 12-1PJK2BF 12-1LMFG3A 7.8.2.11

Interface does not pick the local
date formats
The sequence of the components 12-1PCD7ON 12-1O36R9V 7.8.2.11

in the Configurator UI is not in
the correct order
Custom rules cause the Object 12-1OTUXE7 12-1MFCJ25 7.8.2.11

Manager to crash
The state of the Configurator 12-1OQUB45 12-1OQDGLF 7.8.2.11

Service UI is not properly reset
when users select a pick and the
pick map causes a conflict with
the constraint rules
The BatchValidate method does 12-1OA5S1R 12-1NWD6IX 7.8.2.11

not release cached product
instances
BatchValidate does not create 12-1O2HW9S 12-1NCHH5Z 7.8.2.11
child items
When users click the Cancel 12-1GYNNCV 12-1GUZDQK 7.8.2.11

button on the incomplete
configuration dialog box,
Configurator hangs
Order Management
Changes the synchronization of 12-1PLXVS2 12-1NMVTUP 7.8.2.11 Yes, see
the waterfall funtion from “Instructions
asynchronous to synchronous, for FR 12-
which prevents the code from 1PLXVS2” on
intermittently failing to write the page 468.
waterfall property set to the
database.


Orders
Product with constraints cannot 12-1OH29EL 12-1JOFBKB 7.8.2.11
be customized from the Bulk
Order Actions applet
General
Business Rules
The Data Validation Engine is not 12-1O3QL9S 12-1NJKYC7 7.8.2.11
called correctly on the PickRecord
event, and rules are fired
incorrectly
Calendar
Daily Calendar crashes with a 12-1Q7218W 12-1HPXCQP 7.8.2.11
script error on line 5890
With Internet Explorer 7, users 12-1Q6JY3R 12-1J4XXPF 7.8.2.11 Yes, see

encounter script errors within “Instructions
Siebel Calendar for the
Microsoft
Internet
Explorer 7
Calendar Issue”
on page 467.
An appointment created by User 12-1O2IRC7 12-1NJLF3J 7.8.2.11

A on User B's shared calendar
also appears on User A's calendar
Events (eEvents) appear in 12-1NUHDOU 12-1NKJK2V 7.8.2.11

backwards chronological order on
the monthly event calendar when
events cross multiple days
With Internet Explorer 7, users 12-1LWIHTF 12-1LJ845F 7.8.2.11 Yes, see

occasionally encounter script “Instructions
errors for the
Microsoft
Internet
Explorer 7
Calendar Issue”
on page 467.


In the German version of Siebel 12-1CGOFY7 12-IH2AXE 7.8.2.11

Industry Applications, when a
Calendar is printed, the month is
not translated and the month,
day, and year have no numbers
With Internet Explorer 7, when 12-1IW6MAL 12-1GW3DL9 7.8.2.11 Yes, see

users launch the application, “Instructions
navigate to Site Map > Calendar, for the
and click the Calendar hyperlink Microsoft
multiple times, the application Internet
fails Explorer 7
Calendar Issue”
on page 467.
When users open the Calendar 12-1Q6JY1X 12-1N8PHWZ 7.8.2.11 Yes, see
popup window within the Activity “Instructions
HI Calendar applet, and then for the
navigate to another screen, the Microsoft
Calendar popup window remains Internet
visible Explorer 7
Calendar Issue”
on page 467.
When users navigate to the HI 12-1Q6JY2U 12-1NNDCKJ 7.8.2.11 Yes, see

Activity Outlook Calendar view or “Instructions
the HI Activity Calendar view, for the
they receive the following error Microsoft
message: "Internet Explorer has Internet
stopped working. Windows is Explorer 7
checking for a solution to the Calendar Issue”
problem." After this message on page 467.
display
Communciations
Server
The Recipient Group drop-down 12-1POSQIW 12-U5LAZN 7.8.2.11
list displays ENU values along
with the language pack used
Content Management


When users navigate to 12-1QK0ZSC 12-1QK0ZRR 7.8.2.11

Administration - Microsite > Page
Administration, and drill down on
any page to display the Page
Administration view, the contents
of the ePortal MM Page Item
Properties form applet do not
display
When users click the Back button 12-1OHKDWB 12-1I1GBT5 7.8.2.11

from within a microsite within the
eCustomer application, they
Installation
The 7.8.2.10 Fix Pack is missing 12-1QNW45X 12-1QNW1PN 7.8.2.11
the Handheld application jar files
Error message installing QF patch 12-1MYLZPI 12-1G4O98M 7.8.2.11

on Reports Server
Other
RaiseErrorText in SI mode adds 12-1O9NHB5 12-HFWA47 7.8.2.11
"Error(0)" to the front of the
error message
The connection from Siebel CRM 12-1NQ7LQM 12-1NJKNF5 7.8.2.11

applications to Siebel Analytics
using the Analytics ODBC driver
fails
If a user makes changes to a 12-1319EBT 12-E0F3BX 7.8.2.11
record and selects the Export
option from the Applet Menu
without stepping off the record,
new changes are not reflected in
the exported data
Platforms
There is a failover defect in 12-1PV3MO8 12-1POSM7C 7.8.2.11
oracon.cpp, so the failover retry
setup does not work properly
Remote


On the Tablet PC device, when 12-1PCUMVP 12-1NALW8B 7.8.2.11

Quick Start is enabled, when
users connect to the local
database, the application
launches, but the sync reminder
is launched in the background
and users have to use Alt + Tab
to bring the reminder to the
forefront
Reports Server
Parameterized reports do not 12-1QMWZE3 12-1QJ1WE3 7.8.2.11
work within 7.8.2.10
Users are unable to schedule 12-1NIN2SR 12-1NIN2S1 7.8.2.11

reports after the Siebel 7.8.2.7
Fix Pack has been applied
Garbage collector crash during 12-1P1SSSZ 12-1OVC1X9 7.8.2.11
logoff when CTI is enabled
SRBroker crashes when a 12-1NU09BP 12-1NMF7K3 7.8.2.11

persistent connection is broken
User session timeout causes 12-1JTYQA8 12-1EFIDCN 7.8.2.11

intermittent Object Manager
crashes when trying to unregister
the Communications Client
Business Service
The S_SRM_REQUEST table 12-1GLAU3J 12-1FBGZVR 7.8.2.11

status is not updated with the
correct status of deployment
Siebel Sync
When a recurring meeting is 12-1PCCTF2 12-1OYUA2Z 7.8.2.11
moved, the records are not
moved correctly during
synchronization, and data
corruption occurs
When an invalid email address is 12-1NQOFYX 12-1N6CGJT 7.8.2.11

associated with a calendar item,
it prevents SSSE from
synchronizing the item


The Opportunity Form URL 12-1PVLXPQ 12-1KBLS9L 7.8.2.11
Display Applet displays correctly
when it is placed in a view, but
when it exists as a toggle applet,
the system crashes
ST eScript engine does not work 12-1P1SV5F 12-1KRH24C 7.8.2.11

in an HP-UX environment
With the ST Engine turned on, 12-1OQCZWK 12-1OJJKWB 7.8.2.11
the "with" statement does not
behave as expected
Web Framework
Closing the High Interactivity 12-1BEH6OS 12-1B4DABL 7.8.2.11
client with the "X" crashes
Internet Explorer
Workflow
Workflow Process Manager 12-1PLGMSZ 12-1PJKJJF 7.8.2.11
crashes while loading Marketing
campaigns due to a memory leak
in the Upsert method
When multiple, independent, 12-1P1AHRZ 12-1N6CGIZ 7.8.2.11

long-running workflows run in
parallel, if one workflow
experiences an error, an error
can occur in one of the other
workflows
Life Sciences
Activity
Users are unable to multi-select 12-1O0M4C7 12-1NQ7LNP 7.8.2.11 Yes, see
and add multiple attendees to a “Instructions
meeting for FR 12-
1O0M4C7” on
page 467.
Calendar


Users are unable to drag and 12-1O0MOKX 12-1KGMKIF 7.8.2.11 Yes, see
drop accounts onto the calendar “Instructions
for FR 12-
1O0MOKX” on
page 467.
Clinical Manager
Users cannot undo records after 12-1PLGIXW 12-1P2RV9L 7.8.2.11 Yes, see
selecting a template in the Trip “Instructions
Report Details view for FR 12-
1PLGIXW” on
page 466.
Other
Within the Life Sciences Pharma 12-1J2I89J 12-11WYHRI 7.8.2.11
HI Activity Calendar view, when
users create a contact call by
dragging and dropping from
contact (Pharma Calendar
Professional List Applet) to the LS
Pharma Activity HI Calendar
Applet, and then drag and drop
the record to another time, the
start date displays as updated in
the activities list applet but the
Pharma Professional Call Form
Applet still displays the previous
time
Loyalty
Loyalty Engine
There is a discrepancy between 12-1Q44F2K 12-1P18LL9 7.8.2.11 Yes, see
the point expiration date and “Instructions
accrual cancellation process for FR 12-
1Q44F2K” on
page 466.
Loyalty Manager


MergeRecords method causes an 12-1PCCWM3 12-1JV0W1H 7.8.2.11

End of File error message for the
Loyalty Member Business
Component, and while the target
record is deleted, the data is not
merged properly with the
survivor record
Marketing
Campaigns
Siebel Marketing users do not get 12-1Q3MY8B 12-1PV3ANX 7.8.2.11
real counts when segments are
updated
Email and Web

Marketing
Database cursors left open after 12-1N9IG3A 12-1MM7CTD 7.8.2.11
launching email campaigns can
result in "ORA-1000" errors
Marketing Server
Workflow Process Manager 12-1PLGMOR 12-1OA571N 7.8.2.11
crashes when Siebel Server
memory is exhausted
Mobile Solutions
The Expense Item 'End Date' field 12-1QODHR8 12-1MCA5KV 7.8.2.11
behaves incorrectly
The SMQ Process User Queue 12-1QODI7L 12-1LMZ94M 7.8.2.11

workflow loops forever when
synchronization Object Manager
returns with an error
When users navigate to Screens 12-1QODI6N 12-1L2GKY7 7.8.2.11

> Customers, drill down on a
Customer column, drill down on
New Issue Type, scroll down on
the applet, and then close the
keyboard, the application closes


Signatures captured within the 12-1QK0UA9 12-1P19TLP 7.8.2.11

Handheld application are not
displayed in the Web Client
Sales
Forecasting
Managers cannot add manually 12-1H4DWEG 12-1GYRJYW 7.8.2.11
add revenue items for their
subordinates to forecasts
Opportunities
Field Values disappear on 12-1HSUWX5 12-1HJCC1T 7.8.2.11
attachment views
Other
Within the Accounts > 12-1PS51SP 12-1PILBIH 7.8.2.11
Relationship Hierarchy screen,
the application crashes when
users navigate down several
levels in the hierarchy and then
navigate back up
Provides an integration to allow 12-1OOVPMW 12-1JTG2I5 7.8.2.11 Yes, see

users to synchronize accounts, “Instructions
contacts, opportunities, and for ACR 389” on
products between Oracle CRM On page 197.
Demand and Siebel CRM (Siebel
CRM On Premise) (ACR 389)
When users shift between 12-1IW72VD 12-1HTDK6P 7.8.2.11
calendar views within the Sales
Home Page, Microsoft Internet
Explorer 7 crashes
Service
Other
Object Manager crashes when 12-1P0RVY6 12-1OXAP5N 7.8.2.11
saving asset records


Within the Letters tab of a 12-1JOB02X 12-1JC6UJ9 7.8.2.11

Service Request, when users
click the New button, select a
template for a letter, and click the
Generate Draft button, they
message: “This operation is not
allowed when there are no
records displayed.”
Scheduling
Dispatch Board does not 12-13VBZI6 12-138N9SR 7.8.2.11
maintain query context after
drilldown
Siebel eMail
Response
General
The F9 Send Email function 12-1O94XHM 12-1O76UET 7.8.2.11
within a Microsoft Outlook
integration using CDO returns
the distinguished [X.400 style]
address format rather than the
SMTP [Internet Mail format]
address format
Universal
Customer Master
Survivorship
Survivorship does not work 12-1OH3SW1 12-1NSKPJP 7.8.2.11
User Interface
Controls
Within the Opportunity list 12-1R4AGFG 12-1R4RE7V 7.8.2.11
applet, when users click the
Query button, and then click
Menu, the query launches before
the menu displays


With Internet Explorer 7, the 12-1Q6JY0Z 12-1KXXY85 7.8.2.11 Yes, see

Calendar control only shows up “Instructions
intermittently for the
Microsoft
Internet
Explorer 7
Calendar Issue”
on page 467.
Adding a script causes the 12-1Q255B2 12-1N3J10T 7.8.2.11

calendar control to display dates
without quotes
With Internet Explorer 7, the 12-1PMFCAO 12-1PE98W7 7.8.2.11 “Instructions

Siebel Calendar control does not for the
work Microsoft
Internet
Explorer 7
Calendar Issue”
on page 467.
With Internet Explorer 7, Siebel 12-1PMFC8A 12-1PE98Y5 7.8.2.11 “Instructions

Calendar crashes, hangs, does for the
not load, or fails with a script Microsoft
error Internet
Explorer 7
Calendar Issue”
on page 467.
Allows the Turkish i-dot character 12-1OHLT5B 12-1LEZF5Z 7.8.2.11 Yes, see
to be handled correctly in data “Instructions
queries (ACR 427) for ACR 415” on
page 198.
WriteRecord is triggered 12-1O958FD 12-1NNUWZ5 7.8.2.11

prematurely when an applet
menu is invoked
After Siebel 7.8.2.7 QF0701 has 12-1N5JOT9 12-1MYLIWN 7.8.2.11

been applied, users are unable to
use the right-click menu to undo
the record


When users click the My Calendar 12-1Q6KRQF 12-1P29LVH 7.8.2.11 “Instructions

link, Internet Explorer closes for the
Microsoft
Internet
Explorer 7
Calendar Issue”
on page 467.

When users click the New button 12-1POBN3X 12-1NNUJ7N 7.8.2.11
within an MVG, EditList template
mode is invoked instead of Edit
template mode
If users add a new checkbox to 12-1PLYBTQ 12-1P81NGH 7.8.2.11

the UI using Siebel Tools, and
then enter a data record where
the field has been checked, the
value does not show as checked
after a Refine Query operation
When the AccessibleEnhanced 12-1OQUQUJ 12-1O5H1CL 7.8.2.11

parameter for SI+ mode is
enabled, LOV values do not
appear, and JAWS cannot read
any values
Navigation
After 7.8.2.7 QF0701 for Internet 12-1NPQIR1 12-1NDJFWP 7.8.2.11
Explorer 7 has been applied, the
tab sequence in the application
changes
Other
When users select Menu > New 12-1QV5Z1T 12-1QU6ZFX 7.8.2.11
Query, enter text into a field, and
select Menu > Run Query, the
application returns all records,
not just the ones that were
queried for
If a user closes a tabbed 12-1NSK9Z7 12-1NCHOM7 7.8.2.11

browsing window in Internet
Explorer 7 by clicking on the X,
then the window closes but the
Siebel session is not logged out


When a session timeout occurs, 12-1NPPXMH 12-1NBZX4T 7.8.2.11

the application crashes
Popups/Pick Lists/
MVG/Shuttle
After users have upgraded to the 12-1QBC40L 12-1PILB5Z 7.8.2.11
Siebel 7.8.2.9 Fix Pack, pick
applets do not appear when fields
are read-only
Web Services
Resolves a problem where having 12-1O757WS 12-1JNESUD 7.8.2.11 Yes, see
the EXISTS operator in the “Instructions
searchspec field of the UI Data for ACR 391” on
Web Service causes an error page 198.
(ACR 391)

Pack
Table 22 lists the Change Requests that are included in the 7.8.2.10 Fix Pack.

Issue Addressed ID Request ID Version Changes
Call Center
CTI
Smartscript datetimes are taken 12-1M6BZ8A 12-HEKTWH 7.8.2.10
from the server (GMT) and not
from the end user's TZ setting
Supports Call Center Anywhere 12-1KYGTF1 12-1KSSD91 7.8.2.10

version 8.1.1 on Siebel 7.7.x,
7.8.x, and 8.0.x (ACR 408)
Retrieving a consultation call 12-1NLXH5I 12-1M7GX6L 7.8.2.10

(conference or transfer) and
hanging up does not clean work
items


After Siebel 7.8.2.7 [19234] 12-1ODKQXH 12-1MVEOSB 7.8.2.10

QF0714 has been applied, the CTI
toolbar is not visible
When agents try to use the 12-1OVTSXP 12-1OKJGSN 7.8.2.10

ConferenceComplete function,
they receive an error message
Other
Users are not able to control or 12-1MVQLTB 12-1LBF1QO 7.8.2.10
modify the font of SmartScript
question answers
There are no values in the 12-1D9PLC4 12-1BCQWWV 7.8.2.10

'Categories' field in
Communication Detail - Response
View
Comm Media 7.8.2.10
Energy
Order Management
Automatch does not work for 12-1NALGAC 12-1N5V9BL 7.8.2.10
attributes
Port Id cannot be retrieved during 12-1NDWXZR 12-1N40J6C 7.8.2.10

Bulk Order processing and
custom Action Set Type and
Action Code cannot be added
Connectors / EAI
Other
BOM is not present in the 12-1MWPU9X 12-1MSC1BJ 7.8.2.10
message when UTF-16 data is
sent to MQ using EAI JMS
Transport
COM Data Control crashes occur 12-1KYG3XD 12-1KXD5F8 7.8.2.10

when large records are inserted
Users encounter synchronization 12-1MAMT89 12-1M4BK6R 7.8.2.10

problems with the M:N
relationship


When users attempt to receive 12-1MQC51J 12-1E3CBSB 7.8.2.10

attachments using Web Services
on Siebel 7.7.2.2 SEA, they
message: "Error while processing
argument SiebelMessage for
operation
TIBCOTrnAdmCrseQueryById
(SBL-EAI-04316)".
Consumer Sector
Sales Volume Planning
Category Aggregation Fields are 12-1NQ7VPK 12-1KGMH5V 7.8.2.10
nt properly populated prior to
aggregation
Trade Promotions
The Baseline Data button does 12-1MSUS46 12-1M7ES7R 7.8.2.10 Yes, see
not perform properly “Instructions
for FR 12-
1MSUS46” on
page 469
Customer Order
Management
Configurator
Attributes' user properties cannot 12-1LGKDL7 12-1L3Z5X1 7.8.2.10
be accessed after Display Name
has been created
Within eConfigurator, ineligible 12-1N3J08K 12-1MJBBK6 7.8.2.10
products saved in a current
configuration are not displayed in
red
For some Customizable Products, 12-1N3IUFN 12-1N03ODH 7.8.2.10

performing the Done operation on
Siebel 7.8.2.7 [19227] crashes
the application


On Siebel 7.8.2.5 [19227], a 12-1NFSUFR 12-1N03OFF 7.8.2.10

memory leak occurs when users
select radio button options and
then perform the Done operation.
When users upgrade to Siebel 12-1NXBCEC 12-1NKJKRL 7.8.2.10

7.8.2.6 or Siebel 7.8.2.7, some
product constraint rules cause
attribute values to display in red
Invalid workers are not 12-1OA5YZB 12-1L9C3FT 7.8.2.10

immediately inactivated or
dropped to avoid them from being
used by other Configurator
sessions
Component-based routing can fail 12-1OMWL3N 12-1O139AX 7.8.2.10

if the components are not enabled
in all of the servers after Siebel
Server has attempted routing five
times
Attribute Eligibility does not work 12-1O0MLO1 12-1MSATS6 7.8.2.10

with attributes that have Data
Type = Date
Within a quote or order line item, 12-1NC2W5L 12-1LZM7AT 7.8.2.10

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
eCustomer
Users are unable to edit credit 12-1NG9IFJ 12-1N6TXTP 7.8.2.10
card numbers in the eCustomer
application
eSales


After Siebel 7.8.2.7 has been 12-1NPQM73 12-1NALH1D 7.8.2.10

applied and when a custom SRF is
being used, when users log into
eSales, click on Shop by part,
search for a part, and then click
Add Item, they receive the
following error message: ORA-
00001: unique constraint
(SIEBEL.S_QUOT
Order Management
When an Attribute with a real 12-1CTUZFN 12-1BLU3OL 7.8.2.10
number is updated, the action
code in the Quote is set to
Updated
Orders
Data validation rules for required 12-1O9NI4S 12-1G07N9F 7.8.2.10
attributes are fired incorrectly
Products
Promotion Customizable Product 12-1N9NJQ7 12-1MW8D61 7.8.2.10
cardinality constraints are not
enforced consistently
Sales Catalog
Removing the account association 12-1MZ2UN4 12-1M4UMZ7 7.8.2.10
with an agreement does not
change the Eligibility Status when
the product was initially ineligible
because of account association
When the Thread Bar is used to 12-1M4VIOD 12-1M04HMN 7.8.2.10

navigate to category eligibility
check, display mode 2 does not
work
Financial Services
Other
Query execution on the eEvents 12-19OJZK3 12-19869N5 7.8.2.10
Register Event applet returns
improper results


General
Access Control
Prevents users from opening 12-1MMPMS3 12-1L89B79 7.8.2.10 Yes, see
multiple sessions on the Mobile “Instructions
Web Client (ACR 432) for ACR 432” on
page 219.
Accounts
Users are unable to add new 12-1ONEAXE 12-1ONEAWH 7.8.2.10
records for any child applet that
does not have previous records
Advanced Search
Performance issues occur with 12-1OWBSEP 12-1OK1T6F 7.8.2.10
Business Components and
Business Objects that are not
released even if the variable is set
to null in the script
Assignment Manager
Multi-Tier Assignment 12-1MQB41B 12-1M4UP57 7.8.2.10
functionality is missing in Siebel
version 7.8 applications
Calendar
When users click the New button 12-1NUHA0F 12-1NJLF4A 7.8.2.10
in the Calendar applet in the
Home Page view, an 'End of File'
error is generated
File System
Even after 7.5.3.15 QF0F28 has "12-1M1RZVE 12-1KGO7K3 7.8.2.10
been applied, when users run the
sfscleanup utility, they receive
the following error message:
"Failed to open the iterator. See
log for details.
Installation


In Siebel version 7.8.2.8, the IAA 12-1NQODR7 12-1NQODPO 7.8.2.10

XML connector component is
created for UNIX, which is not
correct
With Siebel 7.8.2.8, during image 12-1NQODPE 12-1NQODOP 7.8.2.10

creation, if users select AIX or
any version of UNIX as the OS,
during component selection all of
the windows components are also
displayed
Other
View Tabs ignore dynamic rules 12-1H091EF 12-1GRZD9P 7.8.2.10
When users configure products, 12-1KI5D5I 12-1KI5D2O 7.8.2.10

threads are left open and
performance becomes slow
On Microsoft Windows XP SP2, a 12-10P3K0D 12-ZALGVD 7.8.2.10

blank page remains after 1000 or
more records are exported
Values that follow an ampersand 12-1K8L62L 12-1BDKMON 7.8.2.10

(&) in a URL argument value are
truncated

Attendees are not being added 12-1MANV77 12-1M0NF6T 7.8.2.10
into the Siebel Appointment
Contact MVG when
ResoveContactByEmail = False
Reports Server
Reports do not display when they 12-1LLTKSW 12-1LH4DGT 7.8.2.10 Yes, see
are embedded within Proposals “Instructions
within Service Agreements for FR 12-
1LLTKSW” on
page 493.
Scheduled reports return 12-1MD7UDL 12-1M8K2OX 7.8.2.10

inconsistent results when queries
with special characters are used


When a report is generated on the 12-1NDF8PK 12-1M6VAR9 7.8.2.10

Mobile Web Client (DHTML
format), the report does not open
up in a full-size window
Search
Repeated use of Search causes a 12-1OI3L63 12-1OEL3NZ 7.8.2.10
memory leak for Object Manager
processes
Security
The audit trail uses a header 12-1CZRQ86 12-1CZRQ2O 7.8.2.10
record that includes the User Id.
This can cause problems with
components that keep switching
the user context and can cause
the wrong User Id to be written to
the audit trail.
The "SBL-SEC-10017" error 12-1GI5WV5 12-1FW5GDJ 7.8.2.10

message is not displayed in Siebel
7.7.2.6 if the account has been
locked out
When the 12-1OOVPF3 12-1DOVFWZ 7.8.2.10

PasswordExpireWarnDays value is
set to greater than nine days, the
Password Expiration Warning
Feature does not work
The Siebel application 12-1NCYOWD 12-1N3J0WN 7.8.2.10
experiences non-reproducible
random crashes
Siebel Sync


ACR 415: When an employee who 12-1LW0Z7F 12-1IJUZYP 7.8.2.10

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.
ACR 415: Provides an archive 12-1MQBYAN 12-1K1YCWH 7.8.2.10 Yes, see

utility for Siebel appointments. “Instructions
The utility runs in the Siebel for ACR 415” on
application and flags the records page 198
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.
A contact created in one 12-1NLY81D 12-1N02ZUZ 7.8.2.10
application is not matched to an
existing record created in the
other, even though first name,
last name, and email address
match and the user has visibility
to the record
ACR 415: Validation errors cause 12-1OH3BOC 12-1LXLFA2 7.8.2.10 Yes, see
synchronization to fail completely “Instructions
for ACR 415” on
page 198
ACR 415: Resolves a problem 12-1OH3BL9 12-1LXLFJM 7.8.2.10 Yes, see

with recurring appointments that “Instructions
occur both in Microsoft Outlook for ACR 415” on
and in Siebel Calendar page 198
ACR 415: Allows the Extract Start 12-1OH3BM7 12-1EXGK4H 7.8.2.10 Yes, see
Date to be specified at the user “Instructions
level rather than globally for ACR 415” on
page 198


ACR 415: Provides one-way 12-1OH3BN4 12-1MIVDTR 7.8.2.10 Yes, see

synchronization from Exchange to “Instructions
Siebel Calendar for ACR 415” on
page 198
Functions require an extra 12-1N889D9 12-1MSV4EV 7.8.2.10
leading { in front of the function
body to behave properly
Dynamic Applet Toggle crashes 12-1NTJ02K 12-1LXMIR2 7.8.2.10
Siebel applications when a
predefined query returns a record
that fires the toggle
If a Workflow step has a field that 12-1ES8GWL 12-JGBOTO 7.8.2.10

is based on an LOV which has
more than one LOVs containing
the same Display Value and Type,
then the workflow fails with the
following error: Method
'WriteRecord' of business
component 'Workflow Branch
Criteria Value' (
RefreshRecord and 12-1LUJ5YV 12-1LI6FFI 7.8.2.10

RefreshBusComp does not work
with single quote value
Performance issues occur with 12-1N61MET 12-1MI9KUX 7.8.2.10

Business Components that are
not released even if the variable
is set to null in the script
After displaying a message with 12-1NQP2C1 12-1MYLIS7 7.8.2.10

RaiseErrorText, future invocations
of RaiseErrorText will display that
same, original message, even
though a new string is specified in
the subsequent calls
iHelp
Tasks
Users are unable to select non- 12-1IIODHY 12-1I088D1 7.8.2.10
hyperlink steps after they click on
the "Additional Steps" hyperlink


Life Sciences
Other
LS Pharma HI Activity Calendar 12-1J2I89J 12-11WYHRI 7.8.2.10
drag and drop
Pharma Handheld for

Windows
When users scroll through list 12-1MMPMEQ 12-1M06R37 7.8.2.10
applets using the vertical scroll
bar, duplicate records are visible
Samples
Users experience poor 12-1GNONIM 12-1G32VVU 7.8.2.10
performance when they drag and
drop an account onto the
Calendar and then drill down on
the Account Call into the Contact/
Attendee picklist
Signature Capture
Valid signatures can be 12-1M05LWO 12-1M05LVL 7.8.2.10
accidentally deleted from the
Signature Capture view
Loyalty
Loyalty Engine
Cancel Transaction does not 12-1OTUJXZ 12-18C53LY 7.8.2.10
remove the exact points that
were given as a result of the
original accrual
Loyalty Manager
When users navigate to the 12-1PF9N0N 12-1PF9MZS 7.8.2.10 Yes, see
Loyalty Member screen, drill “Instructions
down on a member, create an for FR 12-
Accrual transaction, and the 1PF9N0N” on
process the transaction, the page 468
Expiration Date is not set
Marketing


Campaigns
Marketing Object Manager 12-1O1KG7H 12-1NNUJCN 7.8.2.10
crashes occur after users approve
an offer and navigate to another
screen
Events
Query specification does not filter 12-1N68H8C 12-1N0LQFP 7.8.2.10
results on Event Sessions data
Queries on Business Components 12-1MQ844O 12-1M3T6MS 7.8.2.10

that are based on the
CSSBCEventAdminRegistration
class return all rows
Concurrent modification of an 12-1NDFSSY 12-12TA492 7.8.2.10

event's attendee list is not
supported
Mobile Solutions
Signature Control in Service Apps 12-1DT6ICO 12-1DT6IB7 7.8.2.10
does not show signature data
correctly.
When users attempt to use the 12-1MTX67O 12-1MATDY7 7.8.2.10

barcode scanner, but the
"spinning beachball" (equivalent
to an hourglass) displays
The application closes when the 12-1MWRLOG 12-1MWRLNP 7.8.2.10

Order Line Items view is scanned
using the barcode on the
Intermec device
Corrects an issue where when the 12-1LBEUBT 12-1LBEU7C 7.8.2.10

splash screen is activated, any
windows with the WS_POPUP
style are also activated regardless
of whether or not the windows are
created by the Siebel application
(ACR 379)


Partner
Relationship
Management
Partner Portal
The date format of a date value 12-1MPOJ4N 12-1LDEQ3N 7.8.2.10
changes after the date value has
failed the date data validation
Sales
Opportunities
If the user tries to change 12-11QP43L 12-VDOTDZ 7.8.2.10
primary position from the Sales
Team tab after setting the
Opportunity Business Component
user property MVG Set Primary
Restricted: Position=FALSE, the
user receives an error message
Other
The Address field is not updated 12-1LW0Z4Y 12-XMG50B 7.8.2.10
when the primary account related
to a contact is changed
Service
Contracts
The Time Discount % field does 12-1KTTP7V 12-11LSN3S
not work as expected
Other
Dispatch Board: Dispatch Board 12-1IEBA6X 12-1I4ZMCH 7.8.2.10
activities disappear and reappear
on scrolling
Scheduling
Errors are displayed when the 12-1DZX15D 12-1DSNDFY 7.8.2.10
Dispatch Board cache is exceeded


Within the ePharma application, 12-1O4OALH 12-1KBNC1G 7.8.2.10 Yes, see

denormalized columns do not “Instructions
populate correctly for FR 12-
1O4OALH” on
page 468
User Interface
Controls
If an external URL is defined, and 12-1MSBHST 12-1MSAZCI 7.8.2.10
the IsRecordSensitive property is
used, choosing About Record or
Create Bookmark causes a crash
Applets do not display in base 12-1MSW27L 12-1M4CTAH 7.8.2.10

mode
Tree applets doe not open to the 12-1MU7BOL 12-1MCTJBR 7.8.2.10

current selected record
Siebel 7.8.2.6 [19237] QF0638 12-1NNU62Z 12-1N6CEUR 7.8.2.10

introduces a regression of an
issue that was fixed by QF0616
(CR 12-1JD9K31--numeric values
are temporarily blanked out)
When audit trail is enabled and 12-1OCO3CU 12-1NXBFQR 7.8.2.10

the "Audit Trail Item 2" Business
Component is contained in the
Business Object involved, a
cursor leak occurs. This happens
even if there is no insert into
audit table.
After Siebel 7.8.2.7 QF0736 has 12-1OQCAFF 12-1OLHN69 7.8.2.10
been applied, users are unable to
add more records, as using the
Show More feature should allow

Dynamic toggles cause the UI not 12-1FII2Q9 12-1FEVYNN 7.8.2.10
to paint in Windows 2000 clients


After 7.7.2.8 QF0820 (FRA) has 12-1MA4TC7 12-1M7BOQY 7.8.2.10

been applied, when users log in
and navigate to Accounts >
Account list view, the focus is on
the first record field instead of the
record line
The Japanese tilde sign appears 12-1DERI83 12-1D2A4DX 7.8.2.10

as a question mark (?)
When users click F9 and open an 12-1LTGUB2 12-1LC1A2Z 7.8.2.10

email, the text that is copied and
pasted into the email window gets
truncated
Values entered in shuttle applet 12-1NCYOMH 12-1JL69GJ 7.8.2.10

fields do not appear until the user
steps off of the record
The vertical page scroll bar does 12-1PBDZCW 12-1PBDZC1 7.8.2.10

not work correctly
When users attempt to use the 12-1PCCOGY 12-1PCCOFR 7.8.2.10

vertical scroll bar, the application
crashes
With Internet Explorer 7, 12-1N3JDRC 12-1ME9N7W 7.8.2.10

navigating to the next applet
without completing the required
fields causes an endless loop
Other
When users navigate to the 12-1N0LJ0C 12-1MPOVAP 7.8.2.10
Administration - Business Service
> Simulator view, click the the
'Load from File' button, paste in
an incorrect file path, and then
click Submit, the client crashes
instead of displaying a "File not
found" or "Wrong file path"
TODAY() returns no results with 12-1MJVJ60 12-I9SIHA 7.8.2.10

Query Assistant
Personalization administration 12-1ODKQWF 12-1NALW2H 7.8.2.10

screen fields (Include Expression)
show empty pop-up windows
after Siebel 7.8.2.7 [19234]
QF0710 has been applied

Resolved Change Requests in the Siebel 7.8.2.1 Through

7.8.2.9 Fix Packs
Table 23 lists the Resolved Change Requests for the Siebel 7.8.2.1 through 7.8.2.9 Fix Packs.
Table 23. Resolved Change Requests in Siebel 7.8.2.1 Through Siebel 7.8.2.9 Fix Packs

Analytics
Pharma Analytics
The New Call button and drills are 12-17QYMM2 12-174OZ9B 7.8.2.3
disabled when using the
IsRecordSensitive portal agent
command to enable Contextual
Navigation on a child applet
Automotive
eDealer
Reassign functionality is not 12-1F0CJEX 12-1F0CJDD 7.8.2.4
available within Auto eDealer
Portal
Other
When the order status is changed 12-1GN5LUZ 12-1FIZJNP 7.8.2.7 Yes, see
to "Booked," the line item “Instructions
quantity field becomes read-only for FR 12-
1GN5LUZ” on
page 485.
Errors occur when users select 12-194OVBL 12-18CAKW0 7.8.2.5 Yes, see
Contact and Address from the “Instructions
Opportunity view for FR 12-
194OVBL” on
page 470.
Call Center
CTI
Queries called by the 12-1L8TUWN 12-1GO6RLK 7.8.2.8
CleanAllWorkItem method use
PROF_ID in the criteria instead of
USER_ID


In Contact Center Anywhere, 12-1LD362A 12-1LD361L 7.8.2.8

agents cannot be changed to the
'Ready' state and the agents go
out of sync
The Make Call CTI HotKey (F7) 12-1LTHRSQ 12-1IP3MI0 7.8.2.8

does not work if it is placed in the
Toolbar input text box
LookUp and PhoneTypeLookup 12-1JBWVBC 12-1IP3F7J 7.8.2.7

remove all non-numeric
characters from a string
Provides a parameter to allow the 12-1GSFV2Z 12-1EPYAX0 7.8.2.6

driver to selectively turn on/off
the proxy connection, as well as a
parameter to determine whether
proxy information should be
cached and be used later or not
(ACR 190B)
Hoteling on JRE using BigIP fails 12-13WVI6B 12-138VFMS 7.8.2.6 Yes, see
“Instructions
for FR 12-
13WVI6B” on
page 471
Newer versions of Envox products 12-1F4BWFV 12-1F4B8C1 7.8.2.5

need to be supported
On the XP SP2 client, the 12-19F6YP3 12-16KJKNR 7.8.2.5

dashboard is not updated
correctly when an inbound call
comes in
After the communication 12-1F9JROW 12-1EUFQ6P 7.8.2.5

response has been sent, the Send
button and the email body field do
not gray out
Provides hosted CRM functionality 12-1BRPGSN 12-Z86R4G 7.8.2.5

with Enterprise applications
running on Windows (ACR 190)
Inbound emails are truncated in 12-1FK2E2L 12-1FAY9YD 7.8.2.5

the Communications view


An Object Manager memory leak 12-14ZY5ML 12-11WHZ7D 7.8.2.5

occurs when suspending Work
Items (such as when placing calls
directly on hold or during
consultative transfers)
The CleanDashBoard_UI method 12-17R5UYF 12-170P6ZR 7.8.2.5

used in a CTI EventHandler does
not clear the dashboard when a
new inbound call is received
Choosing Predefied Queries can 12-18CGDMF 12-16AKRLL 7.8.2.4

launch the CTI toolbar command
unexpectedly
The CTI toolbar does not appear 12-1F8YK6H 12-1F7YCZ7 7.8.2.4

in Siebel Call Center version
7.8.2.3 (FRA)
Internet Explorer freezes when 12-19ZLKOK 12-JMHTR3 7.8.2.4

users select a value from a
toolbar popup applet at the same
time that a CTI call occurs
Screenpops do not work when 12-133KKMJ 12-118GAM9 7.8.2.2

popup applets are open
Other
When an exception occurs after 12-1JK2ZDU 12-1IZNZBX 7.8.2.8
the Create Activity step,
duplicates may be created
When users reply to a 12-1K3ZWI7 12-1FT2GCY 7.8.2.8
communication, the body
template associated to a Business
Object is not inserted
Line Item records are not added 12-1L0Z303 12-1K5K9MP 7.8.2.8

properly to Quotes when they are
created via SmartScripts
Siebel eMail Response cannot 12-1LWIXS9 12-QUXJJ5 7.8.2.8

process files with filenames that
only contain extensions


In the Service Request form view, 12-1IK2FCX 12-1HSWAKX 7.8.2.7

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
SmartScript cannot execute the 12-1I7YSJ0 12-1HGLS1M 7.8.2.7

PreLeave event at the last
question
The SR Attachments search index 12-1FGEYZC 12-1FBZFGQ 7.8.2.7

refresh process takes much
longer than it should
Object Manager threads 12-1H4ZSZH 12-1GVIZVC 7.8.2.6

deadlock, which leads to login
failure
Users cannot tab to the Next 12-1H1SO80 12-1GH2GUJ 7.8.2.6

button if their SmartScript page
has only one question of type
information on it
Custom drilldown in the Inbox 12-1GTY08N 12-14GZEHR 7.8.2.6

applet does not work
Forwarded emails have one less 12-1GCY46F 12-182HB93 7.8.2.6

attachments than the number of
attachments in the original email
that was sent
Within eTraining, after users 12-1G0NX8P 12-1FWNQCH 7.8.2.6 Yes, see

attempt to add a contact with the “Instructions
Add User button and then click for FR 12-
Save, they receive the following 1G0NX8P” on
error message: 'Contact Id' is a page 471
required field. Please enter a
value for the field. (SBL-DAT-
00498)”
Certifies SearchServer 6.0 for 12-1FBJ89D 12-1D4XH0D 7.8.2.6 Yes, see
Siebel 7.8.2 for Oracle 10g “Instructions
customers (ACR 346A/B) for ACR 346A”
on page 178


Email recipients' display names 12-1FZ4ONL 12-1FN23ZJ 7.8.2.5

are not handled correctly when
users click “Reply to All” from the
Communications screen
The priority of the Smart Answer 12-1CS255Y 12-1B5VEN9 7.8.2.5

search results is not changed
even after users select the
positive feedback button
Provides SNAC support for 12-1EA1AGK 12-1EA2Y6T 7.8.2.5

Microsoft SQL Server 2005 (ACR
335)
The screen goes blank on the 12-1GN3HZQ 12-1EJ0C1P 7.8.2.5 Yes, see
Service Request toggle applet “Instructions
after running a predefined query for FR 12-
1GN3HZQ” on
page 472
After the 7.7.2.3 Fix Pack has 12-12FR3JC 12-12D28US 7.8.2.5

been applied, the application does
not recognize the 31st of the
month as a valid date
When a second Recipient is added 12-12RRPFV 12-12IN37R 7.8.2.5

to a record in the Correspondence
screen, data in the associated
Service Request is lost
dbchck cannot find the column 12-19BUVYJ 12-18O4EAZ 7.8.2.4

default values on Microsoft SQL
Server 2005
If you create a very long report as 12-1BZ3V2H 12-1BWIR7X 7.8.2.4

a section of a proposal, the Doc
Server appears to stop the
srviewer before all data has been
writen into the resulting HTML file
In Siebel 7.8.2, too many 12-1DUROBT 12-1D3Z2PJ 7.8.2.4

employees are visible in the ACD
Transfer popup applet
The single-select checkbox 12-1BBFO8L 12-1B9IZXJ 7.8.2.4

associated to a String/Integer
answer type does not work as
expected


Default answers are not saved to 12-1E2B3ZZ 12-1DGZH3B 7.8.2.4

the Business Component
After Siebel 7.7.2.6 has been 12-1EGYCK8 12-1EFI931 7.8.2.4

applied, pages that contain a
large number of objects do not
work properly
GotoView in Script_Finish is not 12-1DI9WUB 12-1CQWBFT 7.8.2.4

executed if Script().Finish() is
called
In Standard Interactivity mode, 12-1CEANXS 12-1BY11XO 7.8.2.4

the Show drop-down list is not
available for the ERMADMIN
application login page
The F9 [File > Send > Email] 12-1CFDOGI 12-1BAMYS8 7.8.2.4

Email - Outbound Activity Status
is incorrectly marked as Done
A table column width limitation 12-1CG8Y1U 12-1BYVPC7 7.8.2.4

causes long descriptions to be
truncated
The Employee Relationship 12-1CGMP3W 12-12D8EHD 7.8.2.4

Management Object Manager
crashes when executing
CSSSWEWebCSPlayerQuest*CSS
SWEWebCSPlayerPage::GetQuest
ionByFieldName
The On Finish Go To View does not 12-13NJIGW 12-12G3193 7.8.2.4

work when SmartScript is finished
programmatically
SmartScript is not designed to 12-15KGOBN 12-FYNW01 7.8.2.4

resume a saved session when the
SmartScript definition is changed
The background color and width 12-1BXYDL6 12-1B5HBGO 7.8.2.3

of radio button questions cannot
be modified
A default Answer for a 12-18I502R 12-187O830 7.8.2.3

SmartScript acts as a post default
value
Resumed SmartScripts have 12-16I6IV9 12-TSZJJN 7.8.2.3

questions in the incorrect order


With the Customer Dashboard 12-17GMY3G 12-13VBZFB 7.8.2.3 Yes, see

enabled, when users log in, “Instructions
navigate to the Contact record for for FR 12-
the logged-in user, click the 17GMY3G” on
Update button to capture the user page 472
in the Customer Dashboard, and
then navigate to the Home Page
view, the layout of the view is not
co
An error occurs if the Answer 12-17LP3OF 12-HX7923 7.8.2.3
Translation is longer than the
Business Component field
The index hint syntax "(INDEX 12-14MHRZO 12-14JVU0R 7.8.2.2

(index_name))" has been
deprecated in SQL Server 2005
Blanks in Siebel fields are not 12-15LOO1F 12-V0XVAD 7.8.2.2

correctly merged
Configurations cause 12-15LX50K 12-15A7AZC 7.8.2.2

GetProfileAttrAsList ("User
Responsibilities") to not work in
the thin client
SQL statements in escl.sql need 12-17BFJVX 12-179ACLL 7.8.2.2

to be modified to adhere to SQL-
92 syntax
Navigation via the threadbar 12-WY1IQ1 12-O4ML8R 7.8.2.1

should always retrigger the
SmartScript
Second Entitlement does not have 12-Y83K6X 12-Y61GJZ 7.8.2.1

Product associated with it
Comm Media
Energy
Field Service
The ABS LoadEmployees method 12-1GG9U1N 12-1D02Z9L 7.8.2.8
does not apply the Parameter Set
"ABS - Activity Status" to exclude
activities
License Key


The Home Page view is not 12-1E3C3FV 12-1E3C3F6 7.8.2.4

included in CME eCustomer
Order Management
Data Validation Manager does not 12-1HA4D4G 12-1H1YB1M 7.8.2.8
close all opened cursors on
S_VALDN_RL_SET
Promotion validation reports are 12-1JDSS7P 12-1J5HG35 7.8.2.7

missing components when the
promotion and components are
brought into a document through
Modify Order
When a network node is 12-18CL52W 12-173WUM1 7.8.2.5

disconnected, the ABO workflow
misses Cascade Delete on Open
Orders
ACR 327: New module for 12-1FMLPQA 12-1DKDRRD 7.8.2.5 Yes, see
Communications, Media, and “Instructions
Energy. The module provides the for ACR 327” on
ability to mass-generate orders page 165
for a group of assets that are
based on a set of common
actions. Please note that this is an
optional module that requires
additional licens
When using a compound product 12-1FNN8O7 12-19DUIPI 7.8.2.5
with more than one validation
service, the error messages
displayed are repeated based on
the number of validation services
associated to the compound
product
When users add two products in 12-1EFY8LD 12-1CY7NGD 7.8.2.4

eCommunications, compatibility
reasons are not being set
Other
If a user runs multiple iterations 12-1HN4I11 12-1HGM25X 7.8.2.6
of the application, each iteration
causes the memory to grow by
2.8 MB


Price Comparison
The Competitor Attribute Matrix 12-XAQI6G 12-SEB2SI 7.8.2.1
needs entries for each
combination of attributes
Connectors/ EAI
Connector for SAP
Under certain circumstances, 12-1805W4G 12-ON0MQZ 7.8.2.3
when a BAPI integration object is
created for a SAP R/3 4.7 BAPI,
not all fields are created in the
BAPI integration component (ACR
289)
EAI Server
Components
When sending SOAP message 12-1KI5IY2 12-1JWXPJE 7.8.2.8
requests to the EAI Object
Manager to perform pricing logic,
the pricing workflow process
becomes corrupted and throws an
error due to a truncation of the
input/output arguments and the
server CPU maxes out to 100%
The DeleteLeaves method of the 12-1IE8D0R 12-1IAUTPJ 7.8.2.7

EAI UI Data Adapter throws an
error message when deleting an
association
JCA/JDB code causes high CPU 12-1IPOJFT 12-1H79NID 7.8.2.7

usage
Provides SSL Support for JMS 12-1GO4RLL 12-116M8FN 7.8.2.3 Yes, see
Transport (WebLogic) (ACR 228B) “Instructions
for ACR 228B”
on page 62
Enterprise Integration
Manager (EIM)


Allows Enterprise Integration 12-1CB1UGB 12-Z330FP 7.8.2.6

Manager to populate the
CREATED and LAST_UPD columns
with UTC instead of with the
server timestamp (ACR 302)
Users receive the error message 12-13OVAJ5 12-12OXZYB 7.8.2.2 Yes, see
ORA-00001: unique constraint “Instructions
(SIEBEL.S_ADDR_ORG_U1) for FR 12-
violated when Multilingual Lists of 19KT1JR” on
Values are enabled page 473
Other
Provides an option for MQ 12-1JA49PT 12-IY12CI 7.8.2.8 Yes, see
transport to disable report “Instructions
generation (ACR 382) for FR 12-
1JA49PT” on
page 489
A memory leak occurs when 12-1K1GVID 12-1JGVIER 7.8.2.8

adding Accounts using
SiebelDataControl (COM)
With MSMQ Connector, users are 12-1LEYYA6 12-BQ9JRE 7.8.2.8

not able to read/write to private
queues without using the Primary
Domain Controller
SetSearchExpr fails with "Type 12-1MMPLZA 12-1LAUPGS 7.8.2.8
Mismatch" when called through
COM Data Server
7.8.2.3 x 7.8.2.4 EAI Siebel 12-1HY9N8N 12-1HPGZGV 7.8.2.7
Adapter EXECUTE, the delete
operation on child Integration
Components fails on newer Fix
Packs
External Business Components 12-1H1CH7L 12-1GOU9L1 7.8.2.6

columns brought into the Siebel
Schema may cause the server to
crash
Consumer Sector
Handheld


In the Consumer Sector Handheld 12-1KUV9BR 12-1JFQEZ6 7.8.2.8

application, with certain records
in "FS InvLoc Product", the
InstantiateProduct method hangs
Handheld printing does not work 12-1EU0JGJ 12-1EUI5H2 7.8.2.4

properly when a child applet is
empty
Creation of Order Line Items can 12-1CXB4RU 12-1CS189R 7.8.2.4

be slow
Updates resulting from PickMaps 12-1F915RC 12-1EU0JQZ 7.8.2.4

are not being logged in the
CeTxnTable
Printing does not work correctly 12-1670TQT 12-15YY2Q6 7.8.2.4

with the Norand dot matrix
printer when using serial ports
The content of the Credit Check is 12-1CR35ED 12-1B6S62J 7.8.2.3

no longer controllable through the
'Available Credit Dialog Warning
Type' User Property on Order
Entry - Orders
The applet user property "Confirm 12-19KT1JR 12-18X6SZZ 7.8.2.3 Yes, see
Payment Dialog" does not work in “Instructions
7.8.2 for FR 12-
19KT1JR” on
page 473
Repeated 'Prepare Visits' leads to 12-11A009B 12-Y6CT2R 7.8.2.1

memory leak and eventual crash
of the application
The Handheld backup feature fails 12-11AD20R 12-YWZOE0 7.8.2.1

when SiebelDB.sdf is too large
Orders
Clicking the Apply button on 12-1EMG0DO 12-1EMG0A3 7.8.2.4
Authorized Products does not
update the Distribution Code in
the ADL list with Distributed Code
from the Product's Category
Other


Distribution Codes in final ADL 12-1KXZEQC 12-1FEV7DF 7.8.2.8

lists are not updated properly
The Last Updated/Updated by 12-1GLQI2O 12-KAG3PM 7.8.2.7 Yes, see

fields are not updated for “Instructions
inventory transactions that are for FR 12-
the stock transfer type 1GLQI2O” on
page 486
Clicking the Apply button in 12-1DYRRAG 12-1DVBSEM 7.8.2.4

Authorized Category Products
does not remove products from
ADL
An Account Distribution List is 12-14ZUGA9 12-14WL0LD 7.8.2.2

created although the distribution
code set for account does not
match any product
Retail Objectives
Once an objective has been 12-182BVT9 12-JQ909B 7.8.2.4
created and accounts have been
applied against it, it can no longer
be used
Visit Planning does not support 12-1CGJ8R0 12-18Q8EZ1 7.8.2.3

using Role/Category in order to
assign activities to the proper
merchandiser (ACR 307)
A memory leak occurs when 12-15NKKBB 12-V3E525 7.8.2.2

committing target accounts to
objectives
Account Position not associated to 12-17VXWJL 12-17VXWH5 7.8.2.2

any Employee
Sales Volume Planning

The SVP Category hyperlink is not 12-1LQRU81 12-1LIIY6E 7.8.2.8 Yes, see
available “Instructions
for FR 12-
1LQRU81” on
page 489
Performing Mass Change takes a 12-1GOR49F 12-1GELAOH 7.8.2.6

long time because Category/
Product Baselines does not have
the correct search specifications


Performing Mass Change takes a 12-1DS2LPX 12-1DS2LOR 7.8.2.4 Yes, see

long time because Category/ “Instructions
Product Baselines does not have for FR 12-
the correct search specifications 1FWLGC6 and
FR 12-
1DS2LPX” on
page 262
The Sales Volume Planning 12-1F8ZASQ 12-1EQGLOJ 7.8.2.4

Aggregate Action crashes
When applying percentage 12-ZUW8RL 12-Y269KA 7.8.2.1

change using mass change
continuously within a category-
product hierarchy, an error may
occur
Sales Volume Planning Baseline 12-ZYFCXL 12-REJ4Y3 7.8.2.1

Aggregation deletes Baseline
(ACR 218)
Trade Promotions
The Products, Base Volume, and 12-1HJBN4V 12-1GG1HJ4 7.8.2.6
Spread buttons should be in the
background
In the Consumer Goods 12-1GNNHF6 12-1FUK966 7.8.2.6 Yes, see

Promotion form applet, clicking “Instructions
the Products button retrieves for FR 12-
inactive products 1GNNHF6” on
page 473
Totals in parent applets do not 12-134ZCDG 12-12A0LQP 7.8.2.6

reflect all changes in the child
applet
Rollup does not happen from 12-1CR35GV 12-18TUFRD 7.8.2.3

Promotion to Plan with the
Consumer Sector Rollup Business
Component user property
configured
Customer Order
Management
Configurator


When using dates on the PickMap, 12-1G3SW8J 12-1G3SW7T 7.8.2.8

eConfigurator expects the date to
be in the format mm/dd/yyyy and
not the current application date
format
Cfg_InstPosSynchronize does not 12-1JBPLNZ 12-1J9LV0H 7.8.2.8

fire when calling eConfigurator
from the catalog
Customer Order Management 12-1K216OC 12-1JUHICA 7.8.2.8

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 g
In the Standard Interactivity 12-1K4H739 12-1J5J1AH 7.8.2.8

version of Configurator, the
Quantity input box is not
rendered
Sequences of products, 12-1K7JDYH 12-1K3YJ4M 7.8.2.8

attributes, and constraints are
not maintained between different
versions/database instances, so
users may experience different
rule behavior
The configuration log does not 12-1K8LKOQ 12-1JZ3XDD 7.8.2.8

allow for a search time out/
constraint search request to be
identified at runtime
The default attribute value does 12-1K8LKTC 12-1K60Q35 7.8.2.8 Yes, see
not validate Max/Min range “Instructions
values for attributes for FR 12-
1K8LKTC” on
page 490
Batch Validate does not provide 12-1KAV0OV 12-1K8KWRR 7.8.2.8

explanations about why a
configuration instance is
incomplete or invalid


Configurator tracing/logging does 12-1KTTM61 12-1JUHIAC 7.8.2.8

not allow the administrator to
see/troubleshoot iLog requests
In a list of attributes, when users 12-1KUW3TJ 12-15LZ0PJ 7.8.2.8

press the down arrow key to see
the next attribute value, they
have to click the Tab key in order
to put the focus back on the
attribute and to be able to click
the up or down arrow again to
navigate to the next or previous
value
Linked-item-based requirement 12-1L10H2M 12-1JYKJHX 7.8.2.8

constraints do not remove
engine-picked items when the
linked item is set to a diffeent
value
Batch validate is not generating 12-1LBHGRU 12-1L51LOI 7.8.2.8

deatile error messages upon
invalid data
The values ' < and >' in attribute '12-1LGC801 12-1L75EGF 7.8.2.8
values will result in 'empty line
value
Wrong validation results occur 12-1M1ZNE1 12-1LY4CD9 7.8.2.8

with promotions and
Customizable Products
The Batch validate API does not 12-1LXMXCJ 12-1LWJNFH 7.8.2.8

return all statuses correctly
Promotion policy enforcement 12-1M04FO5 12-1LVX3H3 7.8.2.8

results in incorrect behavior upon
the first promotion policy
violation 'undo' operation
When a class with constraints is 12-1MB5LV6 12-1LSO6N2 7.8.2.8 Yes, see

copied, the rule nodes are not Instructions for
copied (S_ISS_CFRL_NODE FR 12-1MB5LV6
records are missing)
When a product rule uses an 12-1MTX4R1 12-1M94CXF 7.8.2.8
optional attribute, the optional
attribute is defaulted


Within Configurator, when the 12-1IF6M1J 12-1IF6M0J 7.8.2.7

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

Method "GetProdStruct" calls
from Business Service >
Simulator are ignored
Improves ilog worker filtering 12-1I4Z4R9 12-1HQ7I52 7.8.2.7

logic to avoid potential issues
with promotion conflicts
Rule Effectivity Dates are not 12-1IPDH0G 12-1IP570Z 7.8.2.7

integrated with Configurator
Model Caching
The Exclude User property on 12-1IPMBTN 12-1F2E9FA 7.8.2.7

relationships is not behaving
properly with some High
Interactivity UI controls
Add Item from Catalog results in 12-1D5WYTB 12-1D5T7YR 7.8.2.7

bad performance if Product has a
default instance
The Min/Max cardinality is not 12-1JY20FX 12-1JUHIDR 7.8.2.7 Yes, see

exposed on numeric attributes “Instructions
for FR 12-
1JY20FX” on
page 486
SQL performs poorly when users 12-1IAD75L 12-1I3D5YX 7.8.2.7

click on an option while a UI
refresh request is in progress
Rules with future dates do not get 12-1IRLY37 12-1F7X2PA 7.8.2.7

triggered in Workspace Project
BatchValidate does not recognize 12-1J4XHBH 12-1IVM41O 7.8.2.7 Yes, see

invalid Customizable Product “Instructions
configurations when the violation for FR 12-
comes from a rule with Linked 1J4XHBH” on
Items page 486.


The PublishCatalog Web Service 12-1J5GH2B 12-1J30VA7 7.8.2.7 Yes, see

with E&C display mode 2 is not “Instructions
filtering out all ineligible products for FR 12-
1J5GH2B” on
page 487
Linked items inherited from class- 12-1IULR6D 12-1G9HYP7 7.8.2.7

based constraints result in an
"item cannot be found" error
message
When MAX_SESSION_ID_SIZE 12-1JQQWVT 12-1J1GVQ1 7.8.2.7

contains more than thirty
characters, Configurator crashes
Auto match is not populating the 12-1JVHFUN 12-CQQG3Q 7.8.2.7

ids for component products that
are grandchildren of the parent
and it is only pouplating ids for
immediate child-level component
products when Asset Based
Ordering is enabled
The Customize operation is 12-1JWYV5T 12-1JTEUE1 7.8.2.7 Yes, see

significantly slower when “Instructions
configuring complex products for FR 12-
with large classes/attributes from 1JWYV5T” on
the catalog page 487
Users are unable to move vendor 12-1I0ZP44 12-1HTW1GF 7.8.2.6 Yes, see
information from one database to “Instructions
another through CP import for FR 12-
1I0ZP44” on
page 473
The PublishCatalog Web Service 12-1HUG2R6 12-1HOZM1B 7.8.2.6 Yes, see

with E&C display mode 2 does not “Instructions
filter ineligible products for ACR 331” on
page 171
Some types of Customizable 12-1HJRUAS 12-1HFKAGX 7.8.2.6

Product script cause the Done
button to hang in the Standard
Interactivity application
Name-based Product Import does 12-1HFK80I 12-1HFK7YR 7.8.2.6

not always roll back updates in
case of failure


Object Instances crash randomly 12-1HFIG27 12-1HF16R2 7.8.2.6

in eConfigurator
Within the Product screen > 12-1HCKHY7 12-1GY6VBX 7.8.2.6

Product Definitions view,
selecting Translate Relationship
from the drop-down list causes
Internet Explorer to crash
The Summary tab generates a UI 12-1H9L97K 12-L5R295 7.8.2.6

not found error and does not
show UI port items
The behavior of the 'Hide' 12-1H6OQAB 12-1GAL3XE 7.8.2.6

property in some UI controls for
selected items is not consistent
The "Revert to Selected Version" 12-1H5IP3R 12-1GQBQCZ 7.8.2.6

button does not copy
responsibilities in the User
Interface
The Pre Cache capability does not 12-1GZUWFA 12-1GZSUYC 7.8.2.6

work properly in Siebel 7.8.2.4
and above
When the remote parameter is 12-1GA28DX 12-1FJLGBP 7.8.2.6

enabled, the AddItem API in
JavaScripting hangs the URL
Rules do not fire after users click 12-1G9ZP8S 12-1G63TZQ 7.8.2.6

the Finish It button
The Product Object Broker Cache 12-1G5BXTF 12-1G4NB5B 7.8.2.6
is not released properly on some
re-cache requests
When users add products and 12-1DQWRNK 12-1CT6PEG 7.8.2.5

rules, and then delete products
without deleting the associated
rules, they receive an error
message with only <?> and no
description of the error and they
are not directed to Configuration
Rules
Random failures occur when 12-1ADHYC0 12-1A80H6H 7.8.2.5

accessing remote eConfigurator
with DeltaQuote on the Solaris OS


Within Configurator, when users 12-1FX4U3F 12-1FVIPQA 7.8.2.5

receive an error message about a
compatibility violation and then
click the Undo button to remove
the conflicting product, the
Configurator session exits
Using the Validate or Customize 12-1CSENWL 12-1C086X5 7.8.2.5

function within Configurator
generates an internal error
Modifying assets that are being 12-1FI0VN3 12-1E6WEZ6 7.8.2.5

imported through Enterprise
Integration manager corrupts
existing assets
UI properties defined on class are 12-1FIIG7F 12-1FHI3NX 7.8.2.5 Yes, see

not released after JWS import “Instructions
for FR 12-
1FIIG7F” on
page 473
Dynamic part number generation 12-1GEKDJ3 12-1FBZHZX 7.8.2.5

terminates inappropriately
When Configurator calculates 12-1EOVV3U 12-1EJHIWS 7.8.2.5

large numbers, the following
error message occurs: “While
updating the model, the Internal
Configuration Engine
encountered the following error:
<?>.(SBL-CFG-00148)”.
Configurator High Interactivity UI 12-1FNN8PA 12-1E6VZH7 7.8.2.5

grandchild display attributes
sequencing is not correct
After users modify a Product 12-18EFM37 12-18CC1SL 7.8.2.4

Asset under a Promotion, they
receive an error message that
states that the Promotion is
invalid
After a large number of product 12-1CB51GO 12-1CACFLY 7.8.2.4

releases, the product version
table accumulates a large number
of unnecessary records


Old version data is not deleted 12-1CB51JI 12-1CB51CV 7.8.2.4

from the Product Details table
With Configurator running in 12-18X4T3U 12-18X5APT 7.8.2.4

Standard Interactivity mode,
clicking the Done button throws a
javascript error
The Excluded property is not 12-1DUQIIH 12-1DTRBFH 7.8.2.4

working as expected for attribute
values
Installing QF0207 on top of 12-1DUSZCW 12-1DS2M4Y 7.8.2.4

7.8.2.2 [19219] SIA deactivates
the buttons in Product Admin >
Workspace
When the record pointer is on the 12-1DVA6QX 12-1AAV9CX 7.8.2.4

child component of the
Customizable Product line item,
the New button is disabled in the
Quote Line Item applet, so
Promotion Recommendation does
not work
The Configurator UI red star does 12-192T8SD 12-192N5XK 7.8.2.4

not show up correctly
The code in 12-1E3ALCC 12-1E12XSR 7.8.2.4

CSSConfiguratorService::LoadIns
tanceFromContext causes a
memory leak
The code in 12-1E3RRNV 12-1E3AZMD 7.8.2.4

CSSCxObj::ClearGenerics causes
a memory leak
Customizable order items cannot 12-1CXH729 12-EACRKZ 7.8.2.4

have a decimal quantity of x,
where 0 > x > 1
The information in the Summary 12-19FEDXC 12-Y3M6K3 7.8.2.4

view is not correct when a
product that has already been
selected is selected again


In an asset modification scenario, 12-1CYDBZQ 12-1CGPFGV 7.8.2.4 Yes, see

if the asset is removed, the user “Instructions
must click the Cancel button and for FR 12-
then restart the Product 1CYDBZQ” on
Configurator session page 474
Within the Configurator (High 12-1E8LCZR 12-1E50NOC 7.8.2.4

Interactivity) UI, the Javascript
UI control for the the Add button
within the Combo Box formats the
fields incorrectly
When a product is selected from 12-1E8PJLS 12-1DWKLGQ 7.8.2.4

the Order Line, the read-only
attribute is not passed to the Line
Item attribute
When the Customizable Product 12-1D0SB0Y 12-1D0SLHJ 7.8.2.4

UI Done operation has a large
number of attributes for selected
child items, excessive cache
queries are generated, and
performance is adversely affected
Products associated with Classes 12-1BJO1IT 12-1A6ZJRD 7.8.2.4

that have Attributes doe not show
the Attributes consistently
The application hangs when users 12-18RHKGY 12-18CHHU6 7.8.2.4 Yes, see
disconnect multiple promotions in “Instructions
the customer portal for FR 12-
18RHKGY” on
page 474
The UI becomes corrupted when 12-18UQTXJ 12-16YQA1G 7.8.2.4

an inline attribute's attribute
translation name contains an
apostrophe
When the domain of a class has 12-1BPKKIM 12-151OUJU 7.8.2.4

only one product, the minimum
and default cardinality is set to 1,
and Configurator is run in Remote
mode, the application crashes
Asset Based Ordering does not 12-1D7JHKJ 12-1D7JHH7 7.8.2.4

work properly if the Remote
parameter is enabled


Reconfiguring a customizable 12-1EIGOYC 12-1EFH8EX 7.8.2.4

product in Asset-Based Ordering
generates a warning message
When users upgrade a promotion, 12-1DHBJI5 12-1DET9SH 7.8.2.4 Yes, see

the start date is set to the current “Instructions
date, and the agreement does not for FR 12-
appear to consider the duration 1DHBJI5” on
and commitment start attributes page 475
that have been set within the
Upgrade view within the Product
Administration screen
Users receive an error message 12-1CE5XL2 12-1BRD10F 7.8.2.4
when they click the Edit
Promotion button within the
Quote > Catalog view
Clicking the Verify button to 12-1FS1S93 12-1EHX0GF 7.8.2.4

perform Product Validation
causes the screen to freeze
The Start Over API is not 12-1DN3USD 12-1DL58T7 7.8.2.4

supported in the Standard
Interactivity UI
Crashes occur in 12-UMGAT7 12-UMCM7P 7.8.2.4

CSSCfgObjFlCon::RefreshProdSrv
rMap
For LDAP users, the "Customize" 12-12QRYWZ 12-XOZGSC 7.8.2.4

operation is slow due to a slow
database login when Configurator
is used remotely
When users attempt to validate "12-174EU2S 12-1748YVY 7.8.2.4

the product, they recieve the
following error message: "Error
getting new worker. Failed
loading configuration model (SBL-
CFG-00124)
Unable to show translated 12-1CR1RCV 12-18FZBHW 7.8.2.3 Yes, see

product names in Configurator “Instructions
High-Interactivity runtime and for FR 12-
error messages 1CR1RCV” on
page 476


The verification message only 12-18MUMOB 12-184LGSY 7.8.2.3

returns one entry when two
products have the same missing
required attribute
Enables Name-Based Product 12-1BJO1E5 12-1AUSMMY 7.8.2.3

Import so that duplicate product
names are not created when the
product name that is imported
exists in the target database with
a different Row ID
After upgrading to 7.8 customers 12-1BVJT8V 12-1BDW795 7.8.2.3 Yes, see

are unable to make tools changes “Instructions
and show Attribute description in for FR 12-
line item applets(quote/order) 1BVJT8V” on
page 476
Bundle product selectioion errors 12-17AZ4LX 12-L50Q1C 7.8.2.3

out if some of the bundle products
do not have unique names
The Required Attribute warning 12-18XH5BA 12-18OX4TR 7.8.2.2

message does not behave
consistently
The application hangs after an 12-18NF8KJ 12-17TG9I5 7.8.2.2

Incomplete Configuration dialog
is displayed
Configurator does not report 12-1300RR9 12-12ZMVD0 7.8.2.2

attribute violations driven by
Promotion Product Special
Configuration
After the upgrade from 7.5 to 7.8, 12-1300RT8 12-12VZ2HZ 7.8.2.2

several attributes have a prefix of
an exclamation mark within the
Class-Attributes explorer view
Unable to get the S_PROD_INT 12-13II1NF 12-131CEK8 7.8.2.2

auxilary fields in the Configurator
summary page and thread bar
Users are unable to enter "double 12-14K3KEG 12-139DIGB 7.8.2.2

Quotes" in Attribute values
strings
Error messages need to be clearer 12-14V71L6 12-14V71J6 7.8.2.2

for Configurator script errors


When a user clicks the Done 12-15CP41X 12-157878Z 7.8.2.2

button, an incomplete list of
attributes displays
Users receive a “Complex object 12-15ETD8M 12-10S1Y3J 7.8.2.2

instance is not loaded” error
message when using Asset-Based
Ordering on a Customizable
product
When a Customizable Product 12-160NEVW 12-14V71LV 7.8.2.2

with a script is copied, the
product of the script does not
change
The Show inline attribute does 12-16F6T78 12-160QR4S 7.8.2.2 Yes, see
not work when the port has two “Instructions
products with different set for FR 12-
attributes 16F6T78” on
page 477
Configurator Linked Items that 12-16JEFQ0 12-16JBZ9I 7.8.2.2

are Date Fields are always
expressed as MM/DD/YY and not
changed based on locale
Non-ilog Integer or date type 12-16JEULP 12-161J4B2 7.8.2.2

attributes are initialized with
incorrect values
The Product in-line Attributes 12-16NCJ73 12-15ZJKKB 7.8.2.2

control does not show the
required attribute red star in the
configurator runtime screen
Cfg_ChildItemChanged script not 12-16VOBFD 12-16N1XUK 7.8.2.2

getting triggered for child
components products
Replacing items inside 12-16VYUNJ 12-16VXLN7 7.8.2.2

Configurator that have rules
defined throws an error message.
In Standard Interactivity mode, 12-16XM2A9 12-16XER9K 7.8.2.2

clicking the Undo button returns
the user to the line item view
The Red Asterisks remain in the 12-176N0TV 12-175M220 7.8.2.2

tab although all required fields
are filled out


When eligibilty mode is set to 2, 12-178FNXT 12-16XLA97 7.8.2.2

ineligibile products are still
displayed in Configurator when
they should have been removed
from the UI
Attribute Exclude rules behave 12-17FLG6X 12-178SHRD 7.8.2.2

differently with non-ENU
languages
The customize icon string is not 12-17GBH6W 12-16VR3K3 7.8.2.2 Yes, see
translated to the local language “Instructions
for FR 12-
17GBH6W” on
page 477
PRESERVE_ENGINE_AND_USER_ 12-17GBHCY 12-16F3J3T 7.8.2.2 Yes, see

PICKS = Y and remote cfg with “Instructions
some rules gives a re/customize for FR 12-
error 17GBHCY” on
page 477
The "Finish It' operation does not 12-17HSR3X 12-17AK3W1 7.8.2.2

clear the required attribute
warning for eConfigurator running
in High Interactivity mode
The red star for a required 12-17I793V 12-17GLJV4 7.8.2.2

attribute on the parent product
does not disappear when the
attribute is changed to a valid
value
Configurator component-based 12-17K2IWJ 12-17K2I9L 7.8.2.2

routing does not support
multilingual requirements
The empty attriubute value fix 12-17LNJIK 12-17LNJHD 7.8.2.2

needs to be consistently
implemented across different
code lines
Missing Required Attributes are 12-17R5VUH 12-17R5VQT 7.8.2.2

not populated after users click the
Verify button


Configurator does not fire the 12-17VO7IX 12-16I4ZF3 7.8.2.2

required attributes for the
Business Component Attribute
Domain
Clicking coupons inside 12-10GDEUI 12-107TKQ6 7.8.2.1

Configurator causes the browser
to hang
Creating multiple Customizable 12-122DOM9 12-121BCSR 7.8.2.1

Product factories simultaneously
causes the Object Manager to
crash
The system throws an error when 12-10G1Z8R 12-105VG5N 7.8.2.1

the user clicks the Customize
button
When users click the Undo 12-115US98 12-107BBSM 7.8.2.1

button, an error is thrown
The Configurator summary page 12-12SXKLG 12-11AGPN6 7.8.2.1

shows extra product names
Customized field values do not 12-12X5YN0 12-12KJWRY 7.8.2.1

show up in the eSales CME or
eSales applications
Customizing fails with the 12-148RSSA 12-145Z3QB 7.8.2.1

Remote+Asset-Based Ordering
setup on 7.8.2
The Pick Applet value is not 12-15USBXV 12-15TYQ16 7.8.2.1

populated until the Configurator
is invoked a second time
No explanation message is 12-15YUE32 12-15TYPXH 7.8.2.1

provided when users click the
Explanation button
The Menu Summary page does 12-15YUE3P 12-15TYPTP 7.8.2.1

not display the data correctly
eCustomer
When users navigate from the 12-1GG1C7W 12-1EE7E8T 7.8.2.7
Home Page to the Offers and Info
tab, and then click the Back
button, the Home Page displays,
but the active tab still indicates
Offers and Info


With Internet Explorer 7, when 12-1IW6MD5 12-1I0HK05 7.8.2.7

users click the Login link within
the eSales/eCustomer
application, the application
crashes
When users log out of the 12-1FBIBL5 12-1F8IO91 7.8.2.5

eCustomer application and then
log back in, they receive the
following error message: "Unable
to load message 0xffff
eSales
Users are able to see information 12-1LNHUY4 12-1LEVEHU 7.8.2.8 Yes, see
from other users' sessions “Instructions
for FR 12-
1LNHUY4” on
page 490
The Quote/Cart "Create Date" 12-1M3SXW1 12-1M37WNS 7.8.2.8

value is not updated when a
quote is updated
In the Shopping Cart applet, 12-1FII2LN 12-1EB7C1F 7.8.2.5

when users click the Check Out
button, they receive the following
error message: "An end of file
error has occurred. Please
continue or ask your system
administrator to check your
application configuration if the
problem persi
Order Management
After 7.8.2.3 QF03C8 has been 12-1MAUDDH 12-1M8MM8N 7.8.2.8
applied, when customers
navigate to an order with a
customizable product, click
Configure, make some changes,
and click Done, they receive the
following error message: Error
invoking service 'SIS OM PMT
Service', method 'Delta' at step
'Create Delta'.(SBL-BPR-00162)


Pick Applets do not work properly 12-1KG3V7X 12-1JWOVYQ 7.8.2.8

in the grandchild applet of the
Administration - Pricing >
Attribute Adjustment >
Conditions view
After an asset item has been 12-1KJ7XDV 12-1K3Y8W2 7.8.2.8

disconnected, when users click
the Verify button, they receive an
error message that says that the
old promotion being disconnected
has active associated assets that
need to be updated
When run in batch mode, during 12-1LO0I5I 12-1K0UO0B 7.8.2.8

Auto-Asset, the Apply method of
the SIS OM PMT Service
intermittently returns an empty
asset
Using attributes in in network 12-1IUKMFM 12-1IS3EZC 7.8.2.7

order validation expression
results in large queries with no
constraints on ASSET_XA, which
causes the product cache to
overflow
If clear cache is performed on 12-1J60FNO 12-1IUL2T1 7.8.2.7

Eligibility Criteria rules, it does
not take effect in runtime unitl
the application server is recycled
A Siebel 7.7 workflow that 12-1HGLB8Q 12-1H2GXTE 7.8.2.7

updates the order line when the
order header is updated does not
work when it is migrated to Siebel
7.8
Inactivating product attributes 12-1J5IVKH 12-1J1FLV0 7.8.2.7

results in errors in the ABO
disconnect operation
Bundle Promotion does not 12-1I3Y3XL 12-1HXH2HP 7.8.2.6

compute max cardinality
The default quantity of 12-1HX753Z 12-1HFIFD7 7.8.2.6

subcomponents does not work as
expected within promotion rules


Users cannot open attachments in 12-1HR0GXH 12-1CTBBRP 7.8.2.6

revised copies of quotes or orders
In the Edit Promotion applet, 12-1GW54K3 12-1GTZHK9 7.8.2.6

when users add a non-default
product with a class, they receive
an error message
Users receive a Session Warning 12-1GLKATX 12-1GHO4S9 7.8.2.6

while adding Products with
classes in the Edit Promotion
applet
The 'FS Inventory Location Org 12-1CHVNOH 12-1CGHRTJ 7.8.2.5

List View' and the 'FINS Data Map
Admin View' were not included in
Option 228
Users can select ineligible 12-1EWWTUD 12-1EL7LWL 7.8.2.5

products by typing in the Product
field
With Asset-Based Ordering, the 12-1FS1LJF 12-1FN4NGJ 7.8.2.5

eligibility and compatibility check
does not work
The Quotes/Sales Order and 12-1EA0Q19 12-1E6CL2P 7.8.2.4

Service Order views lose record
focus after users drill down from
the respective home pages
Setting the "SkipToEnd" Profile 12-1BOLCA3 12-1APIYB7 7.8.2.4

Attribute to "Y" does not halt the
execution of PSP workflows
Approved items do not move to 12-17PNCT9 12-17EEEO9 7.8.2.2

Completed Items list upon
approval
Errors occur when users 12-Z3H82T 12-Y8W15N 7.8.2.1

customize a Customizable
Product that has an attribute
adjustment associated to it
Orders
The Add Items button on Order 12-1GZUZTU 12-1E6DRJL 7.8.2.6
Entry Line Items does not allow
decimal values to be entered


Revising Quotes/Orders or 12-1G0OPG5 12-1FVK7VQ 7.8.2.5 Yes, see

converting Quotes to Orders fails “Instructions
if bounded picklists used by the for FR 12-
Quote or Order are inactive 1G0OPG5” on
page 478
The Credit Card Transaction 12-1GCG0V0 12-1G5LE4K 7.8.2.5

Service business service causes
the application to crash
Follow-up Orders with a status of 12-1GFZ5O4 12-1G6MTDQ 7.8.2.5

'Pending' are not visible in the
Orders screen
If users upgrade from 7.5.x to 12-1EEYWUA 12-1E3B1GP 7.8.2.4

7.8.2, and are using Payments BC
as a child of any other Business
Component other than Quotes
and Order, they may encounter
the following error message:
"Primary Payment Id" does not
exist in the definition for business
comp
The currency code on the form 12-Z9XD1Q 12-Z4B1OK 7.8.2.1 Yes, see
applet is not editable “Instructions
for FR 12-
Z9XD1Q” on
page 478
Other
Deep delete and deep copy may 12-1HVVJWY 12-1HTXBL9 7.8.2.7
result in cursor overflows if there
is a large data set to copy/delete
When users open the Product 12-1BQ8TBK 12-1BPMVNA 7.8.2.4
Promotion pick applet, the Order
Management Signal is not
triggered as expected
The Bundle product "Add Item" 12-158QCR6 12-155J05S 7.8.2.1

operation without Configurator
License Keys fails in 7.8
Pricer
In eCustomer, the List Price does 12-1GKL4SK 12-1G6OP3D 7.8.2.6
not appear within the Catalog


The "Round" function returns 12-1F1W7K1 12-1EUGMZN 7.8.2.5

incorrect results
When Price Lists are transformed, 12-1EUDFRB 12-1EUHN1E 7.8.2.5 Yes, see
the regular price list items “Instructions
transform correctly, but the for FR 12-
values in the Adjustment Value 1EUDFRB” on
field do not transform correctly page 478
Spread Discount can cause the 12-18E1VPC 12-18E3OD3 7.8.2.4

application to hang when the
currency code precision
associated with a line item is
empty
Using the Spread Discount 12-1DS3U0U 12-1DJ0LNN 7.8.2.4

functionality on quotes, orders, or
agreements causes the
application to hang
When an attribute adjustment is 12-1ETXRE1 12-1EJ16IC 7.8.2.4 Yes, see

associated with a child “Instructions
component product of a for FR 12-
customizable product, the 1ETXRE1” on
attribute adjustment is not page 479
applied when the component
product is first selected
Attribute Adjustments with 12-18EDM5Q 12-18CJ2Q1 7.8.2.3
Dimensions that contain ',' in
their domains cause errors in
multi-lingual environments
Calling the SaveWaterfall-Quote 12-1CY9EE9 12-1CQYDZ5 7.8.2.3

signal via script does not save the
waterfall information.
Attribute adjustment pricing is 12-1883C9K 12-186C78G 7.8.2.3

not working for some multilingual
attribute data
Error encountered during upgrade 12-133XRP4 12-133EXGL 7.8.2.2

to 7.8.x Attribute Adjustments
If a dimension is based on a date 12-XWWKWN 12-X1FALH 7.8.2.1

or number in an Attribute
Adjustment table, errors will be
encountered in a multi-lingual
deployments


Service Pricing adjustments not 12-103V6S3 12-ZX54E9 7.8.2.1

fired for certain scenarios on OS/
390
Products
Within Pricing Administration - 12-1GB1U69 12-1G656T6 7.8.2.8
Attribute Adjustments, when
users choose a Customizable
Product with attributes that have
pricing rules, increase the
quantity to two, and click Add
Item, they receive an error
message
When users create products and 12-1K4JIDL 12-1COJO4F 7.8.2.8

then create a Customizable
Product, drill down, create
relationships without associating
any class with this relationship,
add all three products previously
created, create a Bundled
Promotion, and add the
Customizable Produ
Users receive a special constraint 12-1KQYIG4 12-1KIMIUH 7.8.2.8

error when they click Validate in
EditPromotion
When users click Verify on the 12-1KTBD6L 12-1K9OOI6 7.8.2.8

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
BatchValidate hangs with 12-1L0G58O 12-1KNZ65Y 7.8.2.8

incorrect promotion/
Customizable Product definition
Name based import does not 12-1IS4ZQO 12-1IS4KPV 7.8.2.7

resolve S_VOD.VOD_NAME user
key conflicts


Product Promotion cache does not 12-1JFSTSL 12-1JC724U 7.8.2.7 Yes, see
refresh “Instructions
for FR 12-
1JFSTSL” on
page 487
Smart Part Number does not 12-1H4ECLO 12-1FCLG2J 7.8.2.6

generate correctly for translated
attributes
Inline attribute labels are not 12-1DIASDN 12-1DCH0TE 7.8.2.4

aligned properly
Using the Business Service "ISS 12-1B9TU7T 12-1B768FX 7.8.2.3

Authoring Import Export Service"
to release products causes a hang
Provides the ability to expose 12-19F1FNZ 12-12IR0CL 7.8.2.3

Product Promotions and
associated processes on the Web
(ACR 262)
Product Promotions displays 12-18Q315F 12-18P56BP 7.8.2.3

products that were not specified
during setup
Users cannot customize to show 12-186VQQR 12-17VSVU3 7.8.2.2

the UI property on the thread bar
After users select the Attribute 12-YXDG7A 12-Y4T6DZ 7.8.2.1

tab, click the New button, add the
created FreeForm attribute, and
try to enter a default value, the
system accepts any text
The page refreshes whenever a 12-15P938L 12-15MSZB8 7.8.2.1

user performs an activity in the
Configurator
Quotes
The Network Product or Network 12-1ID7J6R 12-1DZ9VIJ 7.8.2.7
Node Product applets do not
refresh
All approval items are updated 12-1HGJM6D 12-1G66Y2M 7.8.2.6

with the status of the latest
approval action
The Quote Activities view is 12-1E3A8VJ 12-1E2AUOD 7.8.2.4

missing in the Quotes product


Change Records functionality is 12-1BVQJ2K 12-1BSDL7F 7.8.2.3

not working consistently under
Quote > Line Items or Sales
Order -> Line Items
Child Line Items created through 12-137D934 12-12ZWARK 7.8.2.2

Catalog View do not have the
exchange date predefaulted
For parallel approvals, return 12-17SB2EP 12-16F0D7T 7.8.2.2

message of the rule set does not
show up in Owner's Comments in
approver's inbox.
Reprice does not get triggered 12-105MJJJ 12-105B6G8 7.8.2.1

automatically after users click on
the Auto Order button in the
Asset-Based Ordering Enabled
Environment
Object Manager Session stops 12-10G1HAV 12-107QQN6 7.8.2.1

responding when user clicks on
Verify option under Quote-Line
Item level in AIX.
Incorrect Line Items are added to 12-11S3XXF 12-105UB8Y 7.8.2.1

quotes when using the Copy
Record and Undo Record buttons
Sales Catalog
Internet Explorer crashes when 12-1KFNBSN 12-1K9OFVL 7.8.2.8
users drill down repeatedly in
catalog navigator categories if
there is no product
Users experience promotion 12-1I4Z4Q3 12-1HQ7I5S 7.8.2.7

constraints and Customizable
Product constraint conflicts when
a Customizable Product is used in
a promotion
Duplicate records are returned by 12-1I7YSD8 12-1H80XWH 7.8.2.7

ExecuteSearch when no context
information is provided
An error occurs on the "Edit 12-1JFSNU5 12-1J92WS2 7.8.2.7

Related Items" substep within the
"ISS Promotion Disconnect
Process" workflow process


Catalog categories are removed 12-1IL3F5G 12-1I8F79G 7.8.2.7

from list applets upon repeated
demote/promote operations
The AddItem Web Service 12-1HCJLEH 12-1H4FZSL 7.8.2.6

generates an error when adding a
promotion item from the catalog
in 7.8.x
When users search for a product 12-1GO7CLW 12-1GE3I3V 7.8.2.6 Yes, see
with the "Attribute Search" “Instructions
feature ("Quote-Search Catalog for FR 12-
View"), access control does not 1GO7CLW” on
apply page 479
Backports Siebel Customer Order 12-1GHNS9O 12-1F0DL3D 7.8.2.5 Yes, see

Management version 8.0 Catalog, “Instructions
Asset, Pricer, and CFG broker Web for ACR 331” on
Services to Siebel 7.8.2.5, and page 171
also backports the core
framework (Hierarchy and EAI IO
to XML Converter) to support the
ability to subscribe to catalogs, cu
When the Catalog Navigator 12-1CF2W4F 12-1C0DFAD 7.8.2.5
control property
"DefaultExpanded" is set to 'Y',
users experience problems with
drilling down
The Catalog Navigator submenu 12-1EFYMPP 12-QLXOIB 7.8.2.4

does not display when users first
attempt to navigate to it, but
when they move up in the catalog
and then navigate back to the
Catalog Navigator submenu, it is
displayed
The Quote Entry applet Quick 12-1CR35J9 12-14SRU9B 7.8.2.3

Print function does not work
Upgrading a Promotion (Asset) 12-1300ROI 12-12ZQJVR 7.8.2.2

with a new promotion results in
false asset violation
Accessing Configurator through a 12-113MSI6 12-10P6QCA 7.8.2.1

URL from Outlook fails to initialize
the .cfg Active-X control, so users
requests are ignored


Data Quality
Deduplication
Deduplication Possible Matches 12-1K1FL2Y 12-PR8UL0 7.8.2.8
are not invoked when creating
duplicate contacts in the Account
Contacts view
When users click the Promote 12-1KM9UIV 12-1K405X2 7.8.2.8

button, the application crashes
When users select the Pick button 12-1L3H1UH 12-1KO0BIW 7.8.2.8

in real-time deduplication,
performance is slow
SSA does not provide clear error 12-1IRLZ32 12-SBNMME 7.8.2.7

messages
Saving a new Contact or Account 12-1IW687P 12-1HR123Z 7.8.2.7

record with the New button or
CTRL-N does not trigger a Data
Quality dialog box
Other
It takes fifteen times longer to 12-1KPTEVS 12-1K405ZO 7.8.2.8
merge four duplicate contacts
than it takes to merge two
duplicate contacts
Merging accounts in the 12-1JGAI7F 12-1IPGQRX 7.8.2.7

Administration-Data Quality
>Duplicate Accounts screen
causes an error message
Employee
Relationship
Management
Distance Learning
If the course contains a single 12-1IP68S7 12-1AVSREW 7.8.2.7
lesson, and the user fails the
lesson, the course remains in the
Confirmed state instead of being
changed to Completed-Failed
status


Users have to click the Finish 12-1JNVKOD 12-1JGB3L0 7.8.2.7 Yes, see
button twice to enroll multiple “Instructions
newly created users for eTraining for FR 12-
1JNVKOD” on
page 488
eTraining
Partial Grade functionality for 12-1GXEZ5F 12-GIQQ1B 7.8.2.7
multiple-choice questions does
not calculate scores correctly
The eTraining application 12-1I3D3NU 12-1H3WJP9 7.8.2.7

computes a score or grade for the
end user even when the user
takes a test with Scoring Method
= No Score
When users complete a course 12-1BWFW7Z 12-1BGP5KB 7.8.2.4

that is assigned to a curriculum,
the status of the course in the
curriculum view stays in
"Confirmed" status
When a course taken under a 12-155MHHB 12-12SECG8 7.8.2.4

curriculum has been completed
and has the status of Completed-
Passed, the Curriculum
Completed, Status, Depth, and
Progress fields are not updated
The status for a training course is 12-185KLRC 12-16VBCE1 7.8.2.4

not changed to Completed-Failed
if the course has been failed
HelpDesk Agent
Applying QF0730 only fixes FR 12-143AFJO 12-13ZB4L2 7.8.2.2 Yes, see
12-T2XZLL in High Interactivity “Instructions
mode by exposing the "Query for FR 12-
Save" menu item at the 143AFJO” on
application level page 479
Enterprise
Integration
Manager/EIM


The EIM process fails to import 12-1HC2F7V 12-1FNCX6B 7.8.2.7

tables that have VARCHAR
columns with lengths of more
than 255 characters
Financial Services
Financial Accounts
With Internet Explorer 7, within 12-1IW72UE 12-1IBEJT9 7.8.2.7
shuttle applets, popup windows
do not display with Microsoft
Internet Explorer 7
Corporate &
Commercial Banking
When invoking Customer 12-1049J3P 12-X74TLV 7.8.2.1
Authentication Manager from the
All Contacts View, the following
error is returned when the user is
not on the contact team:
"Authentication Manager cannot
be invoked in this context.(SBL-
SBL-00000)".
Other
The FINS dedicated client cannot 12-1JBP5MX 12-1J0HBZQ 7.8.2.7
be launched when it is connected
to a customer database that is
kept locally
When SIEBEL_LOG_EVENTS=5 is 12-1FT8M6U 12-1FT54TH 7.8.2.5

set, the application crashes
The application crashes when 12-1F3R0VN 12-1EXYLTC 7.8.2.5

users work with Contacts in the
Relationship Hierarchy view
Call Center scenarios hang with a 12-1FX6IGR 12-1FW5F71 7.8.2.4

memory reference error
The 'EditField' method requires a 12-14JF5HT 12-W0007D 7.8.2.4

value for the SWEField argument
in Standard Interactivity
applications


Error messages occur when users 12-1BJG079 12-1BDW135 7.8.2.3

drill down on any node on
Relationship Hierarchy Tree
Allows the "Confirm Flag" value to 12-1049J4P 12-X9D56F 7.8.2.1

be captured and passed to the
Success workflow (ACR 245)
Personal Lines Policies

Within the "FINS Life Policy List 12-Z2ZK21 12-X2334B 7.8.2.1
Applet" applet, the "SBL state"
Multi-Value Field does not show
any data, and when you query on
this field, a SQL error appears
General
Access Control
Allows Siebel High Interactivity 12-1G5N68B 12-1CX0X8X 7.8.2.6
applications to be downloaded
when the user logs in when the
application is configured for SSO
through Webseal/TAM version 5.1
(ACR 275)
Adds license key Option 173, 12-15IN0TZ 12-15IJPMJ 7.8.2.2

"Data Mapping Administration,"
to Customer Order Management
version 7.8.2.x
SIA base apps should include 12-11NBFCT 12-MRA31A 7.8.2.1
Option #206 - 'Data Validation'
which contains: View: 'FINS
Validation Administration View'
View: 'FINS Validation Rules View'
View: 'FINS Validation More Info
View' View: 'FINS Validation
Rule Actions
Activities
The details entered in the 12-1N88NBP 12-1N5E9RR 7.8.2.8
Activities home page to add a new
record do not show up in the
Activity Details screen


The application crashes when 12-11RJLGX 12-XANYW3 7.8.2.1

trying to update the Status field
in the Action Business Component
Application
Administration
Users have access to 12-WZ49NP 12-W3XK85 7.8.2.1
unauthorized views
Application
Deployment Manager
Reusing an Application 12-156V4S6 12-156V4P0 7.8.2.2
Deployment Manager session
multiple times for file export
causes the 200-character limit to
be exceeded and the data can be
imported multiple times, which
causes slow performance
Assignment Manager
Assignment Batch Manager logs 12-1HWESEG 12-1GK2IBR 7.8.2.6
transactions even when the
component parameter "log txn on
change only" is set to True
When running Batch Assigment, 12-1FEVKHT 12-1EUG350 7.8.2.5

Assignment Manager exits with
an "'Invalid Cursor State" error
message
Within Territory Management, the 12-1E37TEX 12-1DO9POY 7.8.2.4

"From Territory" field does not
always copy the position-specific
data from the previous position
A memory leak occurs during 12-1CFB2NT 12-1CB4VBG 7.8.2.4

Batch Assignment
The Keep Creator flag does not 12-15UEZPA 12-12QB1ER 7.8.2.2

work as expected
Audit Trail
Audit trail works for recording the 12-1KNI4Q5 12-1JWZ08Z 7.8.2.8
disassociation of parent-child
relationships, but not for the
initial association itself


Logged date values in audit trail 12-1KMUO1F 12-VWE00J 7.8.2.8 Yes, see
records are not displayed “Instructions
according to local settings for FR 12-
1KMUO1F” on
page 491
Calendar
Even when the Auto Calendar 12-1FTLT9K 12-1ELW4U1 7.8.2.8 Yes, see
Manager Access option is set to “Instructions
False, subordinates' Calendar for FR 12-
Activities are visible to their 1FTLT9K” on
managers page 491
Appointments created by one 12-1IT4L3B 12-1GJLPLM 7.8.2.8
user on another user's shared
calendar also appear on the first
user's calendar
The Alarm Manager can be 12-1JTYQ6S 12-1GK2GR8 7.8.2.8

disabled by editing a text field
Internet Explorer crashes when 12-1MQ6STT 12-18BVPZG 7.8.2.8

users click the My Calendar link
When users click the My Calendar 12-1MQAV0Z 12-1MQAUQ0 7.8.2.8

hyperlink, they receive a script
error message
A user is able to delete an 12-1N31M0J 12-1N31LWO 7.8.2.8

appointment in another user's
calendar even with read-only
access
The Employee field is not being 12-1N3INLI 12-1MXLW85 7.8.2.8

automatically populated with the
owner's name in Contacts,
Activities, and so forth
Daily Calendar crashes with a 12-1I7YSA3 12-1HPXCQP 7.8.2.7

script error on line 5890
Within the Calendar Screen HI 12-1J2Z487 12-1FEVIQ5 7.8.2.7

Activity Calendar View, when
users click the Print button and
select the default printing format,
the date displayed in the printed
report is “dddd, August dd, yyyy”


In a multilingual environment, 12-1IY3SCN 12-1IL1WXK 7.8.2.7

the SSSE calendar synchronizes
inappropriately
Toggling applets on the LS 12-1HCKO3G 12-1CANJO7 7.8.2.6

Pharma HI Activity Calendar View
causes a view refresh
The Daily Calendar crashes after 12-1H2GPDM 12- 7.8.2.6

users drag and drop contacts onto 1GQWQN9
it
The Applet "First Day of Week" 12-1FDDE9H 12-1F9HXOT 7.8.2.5

User Property only works in the
Weekly display and does not work
in the Monthly display
Visibility rules are ignored in the 12-1FRI5N0 12-1EV7ZCW 7.8.2.5

eEvents High Interactivity
Calendar view
A memory leak occurs while 12-1E8PHTO 12-1E3V061 7.8.2.4

adding Contacts in a Calendar
Appointment after QF0531 has
been applied on top of Siebel
7.7.2.5
A memory leak occurs when users 12-1DN4LN6 12-1D5QSHX 7.8.2.4

create calendar appointments
with 7.7.2.5 Siebel Industry
Applications
Outlook crashes when using 12-123JHX4 12-123JHN4 7.8.2.4

Outlook Add-In with Avaya
Unified Messenger Add-In
Reminder messages pop up for a 12-16BJ1S4 12-H2OFUJ 7.8.2.4

meeting that has been deleted
When the "Symptom" Multi-Value 12-17SSMLQ 12-14UM8OR 7.8.2.4 Yes, see

Link is exposed, when a user “Instructions
creates a Calendar Activity, the for FR 12-
Symptom Code is picked up and a 17SSMLQ” on
recurring activity is created. page 480
Later, when users click the Save
This One button on a recurring
activity, activities with new
ROW_I


Supports a Hebrew codepage for 12-18NBV8U 12-OWLV0O 7.8.2.3

the Siebel Client Sync product
(ACR 279)
The Weekly calendar crashes with 12-12WIP9U 12-12D5MFD 7.8.2.2

a script error
Comments in the eCalendar Daily 12-YT82QO 12-W166JS 7.8.2.1

View should be right-aligned, and
AM/PM symbols should be left-
aligned
The Edit Repeating Activities Pop- 12-11AOLPR 12-VEFS4T 7.8.2.1

up is blocked
Communications
Server
The Recipient Group drop-down 12-1GE0I28 12-U5LAZN 7.8.2.5
list displays ENU values along
with the language pack used
The Email Communication Profile 12-1EVJ9IT 12-TCQCOS 7.8.2.4

is associated with either
Responsibility or Organization,
but the organization field pre-
defaults to "Default Organization"
even when Organization is
removed from the Email Profile
Having 1500 or more double-byte 12-15ZKMYV 12-Q5KE51 7.8.2.2

characters (Japanese) in an email
causes errors
Correspondence
Proposal Generator output text is 12-1JTFZP4 12-1IBVB5T 7.8.2.8
not aligned correctly, which
leaves large spaces between
words
Data Quality
An incorrect SSA DLL causes 12-1GVL6V5 12-1GL4XZX 7.8.2.6
performance issues
The Potential Duplicates popup 12-1G63BEB 12-1FX53WG 7.8.2.6

window appears when records are
saved


The Cleansing method is being 12-1EYGSCD 12-1CLPMMD 7.8.2.4

called twice when the request
comes through on the EAI layer
DQ functions are being called 12-1EYGSDB 12-1B0PCBI 7.8.2.4

twice when running list import,
and this causes performance
issues
Addresses are not reflected in 12-1EYGSEJ 12-XOU8DX 7.8.2.4

dedup keys for account records
when records are inserted
through connector workflow
An extra join on the 12-1EYGS5U 12-1CT6EMH 7.8.2.4

S_PER_DEDUP_KEY table causes
records to pile up in the dedup
key table
Entering '*' sign in Account name 12-19FPWTU 12-19FPWQ3 7.8.2.2

as the first character gives an
error
Improves the Data Quality 12-17EY65M 12-17EY60P 7.8.2.2

Universal Connector to provide
better integration to third-party
data quality solutions (ACR 249)
On startup, the DQMgr 12-186NX4X 12-186NX2D 7.8.2.2

component crashes with SIGABRT
Dun & Bradstreet

Integration
Within Dun & Bradstreet, when 12-1GO7G5R 12-1FW19I7 7.8.2.5 Yes,
users search for a business name “Instructions
and enter Germany as the for FR 12-
country, when they select one of 1GO7G5R” on
the companies that the query page 481
returns, they receive the
following error message: "SBL-
DAT-00498: '<?>' is a required
field. Please en
File System


The 'New File' attachment button 12-1IBES6T 12-1IBVDFG 7.8.2.8

no longer works once three or
more attachments have been
uploaded to an applet
The sfscleanup utility deletes 12-1JGBIE4 12-1JDUHEL 7.8.2.8

valid .SAF files
After users overwrite 12-1I0ZBA5 12-1HPGHP3 7.8.2.7

attachments and click the OK
button, the view hangs in the edit
mode instead of toggling back to
the list applet that shows all
attachments for a defect
The timestamp of the Modified 12-1FZKY84 12-1D0N3BF 7.8.2.5

field on Opportunity Attachments
is incorrect
File attachments larger than 12-12ZLZH4 12-121Q35N 7.8.2.2

600KB cannot be retrieved using
the Sun One 6.1 Web Server
Global/ Multilingual
LOV
Homonym strings are translated 12-1CY430L 12-1CXXLYR 7.8.2.4
incorrectly in Siebel applications,
version 7.8.2
Fields are out of place, 12-15O6MAJ 12-145FWVU 7.8.2.2

overlapping, or missing in a
multilingual environment
Global Time Zone

Repeating Component Request 12-1EEBBBF 12-1D52692 7.8.2.4 Yes, see
tasks queue up due to timezone “Instructions
differences for FR 12-
1EEBBBF” on
page 481
Installation
After users uninstall Siebel 12-1HPHC4F 12-1HNN2WR 7.8.2.8
7.8.2.4 SIA, Siebel Server
crashes
The certificates used to sign 12-1JUI86L 12-1CMTTO9 7.8.2.8

ActiveX controls have expired


During Fix Pack installation, users 12-1EYN43T 12-1D9O8R1 7.8.2.6

are prompted for language pack
jar files, even though these files
do not exist
The public/enu/predeploy.htm file 12-1CU52GA 12-1CU4JJY 7.8.2.4

was not updated in 7.8.2.1 or
7.8.2.2, and customers must edit
the predeploy file and manually
discover all the class IDs
The 7.8.2 installer does not install 12-1BY7DMU 12-1BXXYXD 7.8.2.3

the SQL file comdb42.sql
Unable to select the Database 12-1BOCADF 12-1BO1QJJ 7.8.2.2

Server operation system: Linux
Environment Verification Testing 12-15L4J2M 12-15L4J15 7.8.2.1

(EVT) is not being executed on
HP, AIX, or Windows
Other
View data overlaps on applets 12-1GXLYP0 12-1GD066N 7.8.2.8
when Mozilla Firefox is the
browser
Query Assistant does not work for 12-1IK52X3 12-1IEQBEQ 7.8.2.8

fields based on a join to an
external table
Using Spell Check causes the 12-1EA1ZEO 12-1E7GLGL 7.8.2.8

Object Manager to crash
COM Data Control throws an 12-1K1FQ4J 12-1JC9CFM 7.8.2.8
exception at logoff
The UndoRecord throws an 12-1JNY7VK 12-1JNXYKV 7.8.2.8

exception in the OCX interface
In Standard Interactivity mode, 12-1KLR8GU 12-1JRGCSB 7.8.2.8

when users navigate through the
list applet using the
"GotoNextSet" and
"GotoPreviousSet" buttons, they
receive the "Charts Error.gif"
error message
Delay in process initilization 12-1M1RZRN 12-1DCUH2U 7.8.2.8


Within Siebel Employee 12-1FT2JDY 12-1FFDG3C 7.8.2.7

Relationship Management
Administration, when users click
on the Create Position Link, and
then navigate back to it, the
hyperlink turns into a button with
a gray background color
SSL client mutual authentication 12-1II6AWB 12-1I6WJ6M 7.8.2.7

with EAI HTTP Transport/
Outbound Web Service raises the
12157
(ERROR_INTERNET_SECURITY_C
HANNEL_ERROR) error message
When the Sales Order screen is 12-1IL1TS6 12-1II3R5W 7.8.2.7

accessed, threads are left open in
DB2/390
Users are unable to connect from 12-1HD4A0T 12-1HD49YX 7.8.2.7

Siebel CRM applications to Oracle
Business Intelligence 10.1.3.2
using the Oracle Business
Intelligence ODBC driver
Concurrent accesses to static 12-1J1EU2J 12-1GF25RP 7.8.2.7

picklists yield the SBL-DAT-00225
error message in Workflow
Process Manager
After the 7.5.3.15 Fix Pack has 12-1I6XF1D 12-1I3R7YL 7.8.2.7

been applied, Business Services
crash the Object Manager when a
child record is saved without all of
the required fields having been
filled out
CSSAxCatalogNavigator does not 12-1IP3MO9 12-1ILNI7X 7.8.2.7

work work in Siebel 7.8.2.5
running on IBM DB2
Cicking the Process Receipt 12-1JQYCK2 12-KUL7HX 7.8.2.7

button leads to errors in the case
of products with duplicate names
When eScript and ADODB are 12-1IP63AV 12-1IKJ7JH 7.8.2.7

used to retrieve date fields, the
date shows an hour less than the
value stored in the database


Accessing the same view 12-1JUFQEQ 12-1JHFG2M 7.8.2.7

generates different SQL, which
causes growth in the Oracle
shared pool
BizTalk server based HTTP-based 12-1IZNY0G 12-1HUGQLD 7.8.2.7

AIC returns cannot send
messages to the Siebel EAI
Object Manager in 7.7.2.7
[18376]
After QF0513 has been applied, 12-1J8JG5R 12-1J5GKMX 7.8.2.7

when the Execute method is
called to delete a particular child
record, the wrong child record is
deleted
Certifies Microsoft Internet 12-1JQW3KS 12-12OZHTB 7.8.2.7 Yes, see

Explorer 7 on Windows XP SP2 “Instructions
(ACR 271) for FR 12-
1JQW3KS” on
page 489
After Export > Save, the client 12-1HH3YC3 12-UFYDEL 7.8.2.6

hangs and customers need to use
Task Manager to exit the
application
After 7.8.1.1 [19044] QF0103 has 12-1DNNZS2 12-1CFOFQ3 7.8.2.6

been applied, the application
hangs, and a call stack is
registered in the log file
If JMS message has any property 12-1A80976 12-1A8095X 7.8.2.6

with NULL value, JMS transport
BS errors out
EAI HTTP Transport returns an 12-1EWVWY3 12-1DWDZ69 7.8.2.5

error when chunked data is
returned
SQL performance is slow in 12-1AL5D8J 12-18U0I16 7.8.2.5

version 7.5.3.13
When users toggle between 12-1F1D4DL 12-1EAITV3 7.8.2.5

screens, the screens do not
display properly


The EAI Adapter causes errors 12-1FYK5I9 12-1FWNSOH 7.8.2.5

when invoking component
requests on DirectDb mode with
the ‘Server Requests’ Business
Service
A Global Account Hierarchy must 12-1G6M9YK 12-1FX6J5L 7.8.2.5

be defined in order to allow
accounts to be merged
This enhancement resolves a 12-1GGLHHZ 12-1CAY77 7.8.2.5

problem where users are able to
access data that should not be
visible to someone in their
position (ACR 310)
When a new mode is defined, it 12-1EMY6DB 12-1EBUW9T 7.8.2.5

causes the SetLabelProperty
script command to fail when
executed for the second time
The Korean translation for the 12-1EMYUOX 12-1DU7ZCZ 7.8.2.5

'Campaign' object is incorrect
Object Manager threads 12-1DLFBR7 12-1DEP6NA 7.8.2.5
deadlock, which leads to login
failure once the threads build up
When users click just outside of 12-1EUYVVA 12-1ETX21V 7.8.2.5

the calculator popup applet, the
application crashes
Siebel WSDL generates the 12-WDY4R4 12-WDY4NG 7.8.2.5

following XMLSpy error: "Cannot
resolve declaration or definition x
in namespace y".
Supports multiple NQHOST 12-12CUZBQ 12-OVE4U3 7.8.2.5

parameters for Mobile and
Enterprise Analytics (ACR 288)
Internet Explorer hangs when 12-1CNXQFU 12-S2OPMU 7.8.2.4

users modify a contact record
The Object Manager crashes 12-1DOT9Y0 12-1DK2UO8 7.8.2.4

when users generate reports
using Actuate


Enterprise Integration Manager 12-1DOTM6R 12-10GLCY3 7.8.2.4

fails with the "SBL-EIM-00101:
Invalid arguments to function"
error message when using
DELETE SKIP PRIMARY = FALSE
In Siebel Industry Applications 12-1CMNOPT 12-11WHI28 7.8.2.4

version 7.7.2, the Automatic
Trailing Wildcard is not added for
MVG fields
Syntax of ddlview.sql is not 12-1AQ2KN6 12-1AM14I5 7.8.2.4

compatible with MSSQL2005
(compatibility level90)
Business Services called from a 12-19DSWHJ 12-17HHWX8 7.8.2.4

COM Application are not invoked
and no error messages are
generated
EBC cannot call external views 12-1E70OG8 12-1E6YDVU 7.8.2.4

that have been built to access
another table or view in another
instance using Linked Server
If an intersection table that is 12-19KYB32 12-192VDPP 7.8.2.4

used in an MVG has denormalized
columns, these denormalized
columns can be out of sync when
Undo is run
When using Charts, there is the 12-1EB74ZJ 12-XNPOEH 7.8.2.4

possibility of a potential impact
on performance for DB2 on
OS390
Daily crashes occur when users 12-1ECV7YN 12-1EA0ZXV 7.8.2.4

perform Contact Merging in the
CSSBCBase::PreMerge function
In 7.7.2 Communications/Media/ 12-1EEV48L 12-1EEV78L 7.8.2.4

Energy [18325], a memory leak
occurs with the Availability
service


Provides the ability to create 12-1DNNM63 12-114FFQN 7.8.2.4

separate association records in
the intersection table for the
same child table record, based on
the user key in the intersection
table (ACR 255)
Changes on MVG using 12-1CDB004 12-1BWLGK9 7.8.2.3

intersection table does not update
calculated field on Parent When
changes are made to Multi-Value
Groups using intersection tables,
calculated fields on the Parent
record are not updated
The SBL-UIF-00335 error occurs 12-19PSTPS 12-T2FO1P 7.8.2.3

when users log into Siebel 7.7.2
using the Web Client
Primary is lost when MVG applet 12-18R33FU 12-16X3B4Q 7.8.2.2

is closed and record is past
MaxCursorSize
Display error when same data is 12-133YX0K 12-12UKJ8B 7.8.2.2

being updated by multiple users
concurrently
Currency conversion does not 12-14V33TS 12-143JH3W 7.8.2.2

work for Virtual Business
Components
The Pass By reference does not 12-15F38Q6 12-15F38P9 7.8.2.2

work for member variables and
arguments of functions
If the only record in a Multi-Value 12-15XTVBG 12-14IMYTX 7.8.2.2

Group is deleted and closed, and
then Undo Record is executed,
the UI still shows the primary
record even though there is no
record in the MVG applet
The Excel object 12-15IST6L 12-15C0Q1Q 7.8.2.2

"COMCreateObject" generates an
error on the SaveAs method


In Siebel 7.7.2.3, the compiler/ 12-15NN1ZN 12-14TKRNA 7.8.2.2

run time parser does not detect
typo errors or incorrect
alphanumeric values
Allow UCM to publish messages to 12-15XY4ND 12-11ZRC2T 7.8.2.2

multiple destination queues
Editing Server script crashes 12-169YM50 12-15UBHOW 7.8.2.2

Siebel Tools
The GetProperty method does not 12-16B5VT3 12-15YW80X 7.8.2.2

retrieve a business service user
property
For a MVF field on the parent 12-17U2W28 12-17P5CT7 7.8.2.2

applet, the owner org id field
comes from the parent Business
Component
Runtime escript does not work 12-17U50NQ 12-179FHMB 7.8.2.2
When users search on more than 12-XQRAJG 12-XPIZO6 7.8.2.1

one external field, only the first
searched field is taken into
account
When an Inbound message is 12-10GJ78E 12-108AZM7 7.8.2.1

invoked from the J2EE server, the
following exception is thrown:
Siebel-Error-Message-1: Unable
to create the Business Service
'Web Service Inbound
Dispatcher'(SBL-Siebel-Error-
Message-2: The DLL
'sscaeiwd.dll' could not be load
When a Java application that is 12-10H2WUW 12-KDXVB5 7.8.2.1

using the Siebel Data Bean tries
connecting to Siebel server that
has all its tasks occupied, the
Java application hangs up to 10
minutes
GetProfileAttr does not work 12-10JIB0H 12-Z742QI 7.8.2.1

properly with External Business
Components


Allows log files to be opened/ 12-116FPAI 12-SEPY65 7.8.2.1

copied if the client is running or
hung and makes the format of the
log entries similiar to server logs
(including timestamps) (ACR
152)
The Object Manager crashes on 12-11RO6XW 12-TX9CAX 7.8.2.1

the Salutation applet when the
home page loads
After the general declaration 12-12FUBND 12-11P9ATE 7.8.2.1

#include "eaisiebel.js" is added to
the SIS Account Entry Applet and
the application is compiled and
then run, the application crashes
in the Account List view within the
Account screen
Err.errCode and Err.errText 12-1461FC6 12-11WSFIJ 7.8.2.1

incorrectly return unmapped
error code
The Arguments object does not 12-146COL3 12-119MX6E 7.8.2.1

work at the top-most event
invocation
The compilation time script is not 12-146CON0 12-12EAQ1R 7.8.2.1

working in the thin client (Solaris)
Peformance
Performance slows after setting 12-1HWEE23 12-1HSENAN 7.8.2.6
the "EnforceSSL=True"
parameter
Oracle connector code causes 12-17HZFWA 12-17EE2FG 7.8.2.6
double parsing when a view is
accessed for the first time
For Oracle 10g, the 12-14HD5TV 12-R5WXCB 7.8.2.2

_hash_join_enabled parameter is
set to false
Personalization
Personalization rules do not work 12-139BCKP 12-12KF1LR 7.8.2.4
when using the dynamic profile
attribute to control view visibility


Personalization Rules are not 12-160S82Z 12-G8BJO1 7.8.2.4

applied to the results in reports
on the Reports Server

Certifies JPN for SSSE (ACR 401) 12-1MK9TEJ 12-1KJCQXP 7.8.2.7
When both ENU and FRA have 12-1IE0NMD 12-1HN3LE6 7.8.2.7

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
the Link Type and Search
Columns even though the ENU
Outlook Add-in was installed
The Outlook Add-In Refresh 12-1H6A031 12-1H60LJD 7.8.2.6

refreshes every one minute after
the initial cache build, rather than
refreshing at the interval
specified in Refresh Interval
If the SWSE is on iPlanet, then it 12-1H4ZSIN 12-1G07KDG 7.8.2.6

is not possible to initialize and use
the SSSE Outlook Addin, and
Status Error 204 is reported
With the Outlook Add In, the user 12-1FN5OF6 12-1EUHW9D 7.8.2.5
receives the following error
message: "The Siebel data cache
is currently getting updated.
Please wait five minutes before
attempting to access the link to
Siebel popup that appears in
Outlook.”
Sync fails when the subject field 12-1CGSBDW 12-1B6PHFV 7.8.2.5

in Outlook Calendar contains
special characters (such as
carriage return, tabs, and so on)


Outlook Add In does not read 12-1CU8EXD 12-1CKOCTX 7.8.2.4

regional setting values When
users have the Regional List
Separator set to a character other
than "," Outlook Add In cannot
sync data
Both Recurring and Nonrecurring 12-1FD2WZZ 12-1FD2WY9 7.8.2.4

Inbound Calendar records are not
synchronizing
Inbound Business Contact 12-1FD2X0C 12-1FD2WZ0 7.8.2.4

Records not are not synchronizing
Inbound Delete does not work for 12-1FD2X1O 12-1FD2X0R 7.8.2.4

Personal Contacts
A small percentage of users may 12-YCROVC 12-VPFGNA 7.8.2.4

not see the correct time for
recurring appointments that span
Daylight Savings Time
If Contact Notes are removed 12-18RQIQO 12-18R15QX 7.8.2.2

from Field Mappings, they are
synched in both directions
incorrectly
PIM phone numbers import 12-15MC85M 12-15M3X93 7.8.2.2

incorrectly if the Engine runs
under the English (United
Kingdom) locale
Users cannot change the default 12-16N200T 12-16L4RU0 7.8.2.2 Yes, see
virtual directory name - WebDEV “Instructions
Calls to Exchange from SSSE for FR 12-
16N200T” on
page 481
The "Show Time As" field in 12-16N4SJW 12-161J7BM 7.8.2.2

Exchange is overwritten with
fixed values during updates
A record can be committed, even 12-17BJ6NO 12-17BEUBL 7.8.2.2

though a failure is detected and
the Sync State is not saved
Platforms
Mainwin fails to verify a valid 12-1H727TD 12-1D8VKB2 7.8.2.6
intermediate CA certificate


The SQL0905N error is not 12-1GY0M3L 12- 7.8.2.6

handled properly in the 1GUWDLD
RecordCount method
IBM DB2/390 drops threads that 12-1EXYEZO 12-1C0ARUL 7.8.2.5

are idle and returns a 1224N error
when the application tries to use
a thread that was dropped
Address records are updated even 12-15KOTNM 12-13YN700 7.8.2.4

when no updates are made and
blanks ' ' are changed to nulls
Enterprise Integration Manager 12-1CRV6NZ 12-1CHK6H8 7.8.2.3

crashes when attempting to
populate
S_EXP_ITEM.PAR_EXP_ITEM_ID
When the RLF limit is exceeded 12-ZB05HB 12-Z8VLZL 7.8.2.2

while the SQL statement is being
prepared, the user receives a
SQL0905N error message
The DB2 Stored Procedure for 64- 12-19Q0S4M 12-197UX0E 7.8.2.2

bit Linux siebproc64 is missing
from the Linux directory
The OCI connection fails with the 12-17GIYY1 12-15ZD5XM 7.8.2.2

65535 error
Remote
Account Affiliation and other 12-1I4X9TH 12-1HML1IV 7.8.2.7
party data is not routing properly
S_PARTY_RPT_REL is not routed 12-1I4YZPP 12-1HVJDLF 7.8.2.7
to the mobile client when a
position is added to an Access
Group
Two synchronizations are 12-1BSM154 12-1BI8P0H 7.8.2.7

required for .SAF Syndicated Data
files
Remote Sync fails when user 12-1HGJM7I 12-1HBTXCU 7.8.2.6

passwords are in lowercase and
Siebel Analytics has accessed the
local database first


Clicking the Hide button while 12-1FFCCYK 12-1D2FHRI 7.8.2.6

initializing a new local database
causes the synchronization to
close
In certain scenarios, a deadlock 12-1D5ZNP0 12-R997QN 7.8.2.4

may occur on the
S_DOCK_SESSION table
In certain scenarios, a character 12-13F4X2S 12-JEUOIV 7.8.2.4

string is appended to a column
when the field is replicated to the
Mobile Client
The Mobile Web Client may 12-15AONVH 12-14UZ9WZ 7.8.2.2

experience a slight memory leak
when synchronizing changes on
the S_SRC table
In certain scenarios, the 12-15J105Q 12-W4EK2C 7.8.2.2

DOBJINST file of a Mobile Client
may be corrupted by the
Transaction Router
In certain circumstances, the 12-17IBNE6 12-16MP7EE 7.8.2.2

ending transaction is skipped for
complex transactions, which
causes the complex transactions
to be queued up
TrickleSync fails to detect when a 12-12KT1T3 12-Y38H9P 7.8.2.1

VPN connection is reestablished
on a wireless network
DBInit restarts from the 12-X7RMG1 12-WX7KV4 7.8.2.1

beginning if it is interrupted (ACR
251)
Transaction Router exits 12-11RO6OS 12-10TIZVI 7.8.2.1

abnormally under certain
conditions
Replication Manager
URLs are incorrectly replicated to 12-16HQB6P 12-15CMUKY 7.8.2.2
regional nodes
Report Designer


After My Reports and/or Schedule 12-1DB4CUP 12-171FOV3 7.8.2.6 Yes, see

Reports options have been “Instructions
removed from the Reports drop- for FR 12-
down menu, there are blank spots 1DB4CUP” on
on the menu, and if users click on page 482
the blank spots, the application
takes them to the schedule report
window or displays an error
Reports Server
The Reports Business Service 12-1M0PDNZ 12-1FNN8PL 7.8.2.8
'Version' field is always blank
The Report Viewer crashes when 12-1JS02UP 12-1GUIONJ 7.8.2.7

users attempt to print reports
multiple times
If the Password field contains 12-1JYL7LD 12-VZ5W1R 7.8.2.7

special characters (such as
ampersands and apostrophes),
reports fail
In reports that allow users to 12-1HZTGIU 12-MRPP13 7.8.2.6 Yes, see

enter report parameters, all text “Instructions
after a special character (such as for FR 12-
an apostrophe or an ampersand) 1HZTGIU” on
is truncated page 482
Users are unable to schedule 12-1DTOBPR 12-TX8TGT 7.8.2.5

Reports from the Read Only views
Provides support for Actuate 7 12-1F3R077 12-1F3R04L 7.8.2.5

SP2 Fix 19 (ACR 316)
Predefined Queries that contain 12-18H3GLV 12-MJU64L 7.8.2.2

special characters do not work
well
Running a report, then closing the 12-X9MAR2 12-EESLSK 7.8.2.2

application causes memory error.
Search
Users experience regular crashes 12-1KPB581 12-KISC0Q 7.8.2.8
while using Fulcrum (the crash is
in the
CSSFulcrumSearchAdapter::GetS
ourceName() function)


After a contact has been added, 12-1EMX5JK 12-1EIIJ8O 7.8.2.7

and users access ‘All Contacts
across Organization' and click
Find, they receive the following
error message: We detected an
Error which may have occurred
for one or more of the following
reasons: The selected search
result cannot be found.(SBL-SRH-
00167)
When users click on the Search 12-1DHC8EL 12-1D35TD5 7.8.2.4

button in Search Center, Internet
Explorer refreshes and logs in
again
After users apply QF2105, the 12-1EUFLXH 12-1EPZIYJ 7.8.2.4

customized error messages in the
Find applet no longer work, and
<?> ( SBL-EXL-00151 ) is
displayed instead
When Hummingbird 12-16LF4C7 12-119VB6K 7.8.2.4

uncompresses attachments, it
loops through all files and causes
performance problems
Users receive the error message 12-17V6XLR 12-17A4Z1J 7.8.2.4
"The selected search result
cannot be found" when they drill
down on Find results
Refresh of file attachment indexes 12-143VX2T 12-1409A3N 7.8.2.2

is slow with Siebel 7.5.3.12
Security
Memory corruption occurs while 12-1MPR529 12-1IWNIU9 7.8.2.8
using EAI HTTP Transport over
SSL
mwcontrol does not import 12-1I3DHOS 12-1I3DHCK 7.8.2.8

extensions that are marked as
critical


NULL encryption does not work 12-1IL26GJ 12-1IFMN3R 7.8.2.8 Yes, see
properly, so users cannot “Instructions
implement ACR 329 for FR 12-
1IL26GJ” on
page 491
Users receive an incorrect 12-ZYAANB 12-ZYAAK3 7.8.2.8

confirmation message when
cancelling the import of the
certificate into the mainwin
registry
After responsibilities have been 12-1KWTLMB 12-1I2UQ34 7.8.2.8

removed, views associated with
the removed responsibilities are
still visible in the Site Map
Certificates are imported 12-1MRTOBD 12-1ILP01K 7.8.2.8

incorrectly with mwcontrol
When a valid certificate is 12-1MU820N 12-1LKBU9G 7.8.2.8

imported into the mainwin
registry, the certificate is shown
as untrusted
There is a cross-site scripting 12-1ILKQ7X 12-1I7X851 7.8.2.7

vulnerability in the Siebel
application
Corrects a performance issue with 12-1JTXN1Z 12-I3M1H6 7.8.2.7

ACR 329, which allows EAI HTTP
Transport to support client
authentication via an SSL client
certificate
Certificates are imported 12-1IT4MTT 12-1ILP01K 7.8.2.7

incorrectly with mwcontrol
Users are unable to access charts 12-1J4ZVNX 12-1IVNL8I 7.8.2.7

when the SSL Accelerator is
enabled


When Actuate Reports is "12-1J5H1NE 12-1J04D3B 7.8.2.7

configured for SSL, and users
attempt to print reports, they
message: "Security Information.
This page contains both secure
and nonsecure items. Do you
want to display the nonsecure
items?
The Duplicate Users functionality 12-1GNMIN3 12-1DPDH8J 7.8.2.6

does not work as expected when
using adapter-defined user name
such as email address for
registering users
Siebel Calendar crashes when 12-1G5LBSI 12-1E6EIWY 7.8.2.6

used in SSO with IBM WebSeal
The Verify password field in User 12-1GOS11Q 12-1GFJFXH 7.8.2.5

Preferences does not reset
If the "User must change 12-1F0V98P 12-1EYFZPX 7.8.2.5

password after reset" function is
enabled on the SunOne LDAP
server, and if the administrator
resets the user's password, when
the user next logs in, the user will
recieve a message prompting
them to change their password.
However
LDAP to ADSI Authentication 12-1G6Q4TZ 12-1G3RFWQ 7.8.2.5

allows users to log in without a
password
A Cross Site Scripting (XSS) 12-1FBGDWW 12-1F4BUQP 7.8.2.5

vulnerability exists with the Last
Name field
Active Directory Users are being 12-1G8YP2B 12-1FW11DV 7.8.2.5

deleted when they register with a
previously used email address
Allows EAI HTTP Transport to 12-18U6OH5 12-I3M1H6 7.8.2.5

support client authentication via a
SSL client certificate (ACR 329)


Provides SSL Accelerator support 12-1F1BR4E 12-170GA6B 7.8.2.4 Yes, see

for the High Interactivity and “Instructions
Standard Interactivity mode for FR 12-
clients (ACR 320) 1F1BR4E” on
page 483
The Protected Virtual Directory 12-1BH8AWD 12-19ZGK7N 7.8.2.4

does not work for SSO scenarios
It is not possible to configure a 12-1CGSBFS 12-M38RXJ 7.8.2.4

Terms and Conditions Page that
users must read and agree to
before they are granted access to
the Siebel application
Object Manager crashes due to an 12-17SC5UO 12-UJ1B7M 7.8.2.4

expired user in LDAP (IBM
SecureWay)
User Registration workflow 12-1869XN3 12-15Y7VXS 7.8.2.4

resumes from the wait step and
picks up sensitive data from the
incorrect instance
Looping occurs during Single Sign 12-170SW5P 12-16HRCQ3 7.8.2.3

On for a user who does not exist
in Siebel, but does exist in LDAP
Cross-site scripting is possible 12-16XLAMH 12-16JIIYO 7.8.2.2

when issuing a script in a URL
Incorrect login on Dedicated 12-174LCW4 12-16XIENV 7.8.2.2

client generates Security Adapter
cleanup callstack if the
SIEBEL_LOG_EVENTS
environment variable is set to 5
Adding a hash column to the to 12-182R3XQ 12-17IXL0D 7.8.2.2

S_SRC_PAYMENT table fails with
a TBLO error even when the
correct TBLO has been provided
during login
Custom buttons should be 12-XE8ED5 12-RIVLWC 7.8.2.1

disabled in read only views
Send Email


The "To" field is not populated 12-19BRPUF 12-Y7HD9L 7.8.2.4

into the Microsoft Outlook mail
client when a custom field is used
as the source
Core dump in 12-1JYL7MI 12-18TWSSC 7.8.2.8
CSSSqlObj::InvalMvfCalcs
Within the Product Promotions > 12-1K5099O 12-1JFT7ZP 7.8.2.8

Terms view, when users perform
a query and then perform a
second query, the results from
the first query display
When users follow the 12-1KCRKQ5 12-1K8LJO2 7.8.2.8

instructions in Technical Note 520
(Doc ID 477671.1) on
OracleMetaLink 3, in DB2/390,
the Visual Basic classes
CSSFABCVRec and
CSSFAExternalService leave
threads open
Memory corruption occurs in 12-1KWSN2Z 12-1KT694D 7.8.2.8

CSSOraSqlCursor::DoFetchNextR
ecord
Pressing ENTER in a Pick Applet 12-1LZKAED 12-1LVID39 7.8.2.8

field raises an error message and
an unexpected WriteRecord event
SecureLogin does not work for the 12-1JGWP10 12-1I3DE9V 7.8.2.7

echannelcme_enu component on
Solaris Sun One
Allows the Siebel High 12-1HXFPMP 12-J6KGE1 7.8.2.6

Interactivity client to smoothly
process HTML responses (ACR
275A/B)
Siebel Native load balancing does 12-16F8M13 12-Y3FYS2 7.8.2.6

not detect down Siebel Servers
Siebel Native Load Balancing 12-1EDSU0X 12-1EAIV1R 7.8.2.5
generates uneven load balancing
when a server is shut down out of
a load-balanced pool


Slow response time is 12-18QBCKB 12-18481AC 7.8.2.4

encountered after upgrading to
7.5.3.13 Quick Fix 1D02
Enterprise Integration Manager 12-1D4WAYG 12-1D3GF47 7.8.2.4

fails while importing bounded
picklists with empty string values
(BLANKS)
A crash occurs when users click 12-1EFH4ZZ 12-1ECCUZL 7.8.2.4

the New button after nullifying an
address in the Account Address
MVG Shuttle applet
Repeating Comp Jobs get fired 12-Z38J85 12-YSQR8K 7.8.2.2

quickly when the Database Server
transitions from Daylight Savings
to Standard time
The Listener thread hangs during 12-15Z6X5X 12-14ZV2IQ 7.8.2.2

shutdown when SBL-SMI-00006
is received
Crashes occur on 12-TZ2Q7V 12-T6H7KD 7.8.2.1

CCFMapStats::~CCFMapStats()
when EAI DataMap is missing
Restarting the Gateway Server 12-103Z8UO 12-103B7QE 7.8.2.1

when a session is using Server
Administration screens may crash
the Object Manager
After a user has applied the "12-123VSKD 12-112LAXV 7.8.2.1

7.7.2.3 SIA patch and attempts to
log out of the client using File >
Logout, they receive a "DDE
Server Window: Siebel.exe -
Application Error
Service Requests
The Sort icon does not display 12-1JV0CL4 12-1GDIRHB 7.8.2.8
correctly in the All Service
Request List view
Siebel Anywhere


Users are unable to run the 12-1JY05NH 12-1IV2L0N 7.8.2.8

Upgrade Wizard with a delta srf
upgrade kit that has a full path to
the srf in the configuration file
Mobile Web Client fails to exit 12-1G080SX 12-1F7GO6A 7.8.2.5

when applying upgrade kits on
certain Tablet PCs
The Upgrade Wizard of Siebel 12-18G6GX3 12-17SJ17Y 7.8.2.2

Anywhere may appear to not be
responding when applying a Delta
SRF Upgrade Kit
The ODBC Data Source for the 12-19MKO80 12-161J3S4 7.8.2.2

Mobile Web Client is not created
by the Siebel Anywhere Upgrade
Kit
Siebel Sync
ACR 373B provides the following 12-1HN5K2B 12-1HN5K1B 7.8.2.8 Yes, see
functionality: “Instructions
for ACR 373B”
■ Supports Microsoft Exchange
on page 194
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'.
Double-quote characters in the 12-1KNI4O1 12-1K62V6P 7.8.2.8
Last Name field (as in Hebrew
names) prevent SSSE
synchronization
Users are unable to sync 12-1LQV647 12-1L9B74C 7.8.2.8

recurring appointments that are
created in a handheld device
Provides support for Lotus Notes 12-17F6GFE 12-17F6GCT 7.8.2.5

7 for Siebel Client Sync (ACR
269B)
SmartScript


The application crashes when 12-1D3LDDE 12-1D35M64 7.8.2.3

users click on any SmartScripts
from the Smart Script Path
Language List applet
Test Automation
Picklist fields like "Select Field" 12-1AD2GCP 12-1ACYC2B 7.8.2.2
and "Perform Query Using" are
not recognized (ACR 273A)
The Add Agent applet is missing 12-1AD5YE1 12-1AD5Y70 7.8.2.2
under Admin-Communications--
Applets (ACR 273A)
The contents in the Query 12-18YWJMP 12-18YSN3P 7.8.2.2

Assistant window (for PDQ) are
not recognized (ACR 273A)
Logging throws an exception in 12-1AN29PM 12-1AN29LA 7.8.2.2

setDataSource() (ACR 273A)
The call to getContainerobject() 12-18T91DH 12-18T917L 7.8.2.2

method with SiebText as the
object should return an empty
string (ACR 273A)
Backports the Siebel Test Express 12-15PJ7ET 12-15NVLDF 7.8.2.2

Repository API feature (ACR 273)
Tools/Configuration
An incorrect delete statement on 12-1IPMFM7 12-1IE6G8G 7.8.2.8
the S_ESCL_REQ table causes
performance issues
An error message occurs when 12-1KYYHY1 12-1G49KFR 7.8.2.8

the query criteria DOES NOT
CONTAIN is used
The Date function in the ST 12-1LEYRAU 12-1KUV9OR 7.8.2.8

scripting engine returns the
incorrect time in the AIX
enviroment
The setUTC and getUTC methods 12-1IEREBB 12-1HKB17M 7.8.2.7

are not working properly after
applying the 2007 rules for


The HTML Attribute Id handle is 12-1II6AUD 12-1I2RN08 7.8.2.7

lost when scripting is used on the
control
Crashes may occur with the new 12-1IINQQB 12-1I4ZI0J 7.8.2.7

script engine and the following
script: var a =
TheApplication().GetBusObject("
x").GetBusComp("y"); with a
temporary Business Object (not
assigned to any variables)
Incomplete exception returned in 12-1IP5OSF 12-1HOIZFB 7.8.2.7

ST eScript engine
After applying the 7.7.2.6 Fix 12-1FIIYBA 12-1FGFJZ1 7.8.2.7

Pack, users receive the SBL-DAT-
00398 error message
When ADODB is used to retrieve 12-1IY3ZRJ 12-1IV5GYS 7.8.2.7

date fields, the date fields display
a value that is one month more
than the value stored in the
database
Suspended workflow process 12-1I4Z67F 12-1HZAPD3 7.8.2.6

instances are saved in
S_WFA_INSTANCE even with
Auto-Persist= False
Text Field values are not available 12-1HJBHAW 12-1G49D48 7.8.2.6

in browser script in Query Mode if
the field is not stepped off of
A memory leak occurs when script 12-1H61H31 12-1H61H1N 7.8.2.6

assist is invoked
String.length crashes AIX server 12-1H5KDUM 12-1H2IDCM 7.8.2.6

on ST Engine
With the new engine, compiling 12-1GHNQTL 12-1GH4DEN 7.8.2.6

scripts to SRF ignores user
preferences for type deduction
Siebel VB Memory leak crash 12-1GE1LMF 12-1GCFL3X 7.8.2.6

using variant and arrays
The Date object's toString() 12-1DICO31 12-1DI7Y17 7.8.2.6

function does not work with AIX
with the new scripting engine


Comparison between Date 12-1CB5DX6 12-17Q978R 7.8.2.6

objects returns wrong result
The Date object returns an 12-1EZ0ELV 12-1EBAAE1 7.8.2.5

unexpected format for seconds
with the new script engine
It is not possible to get the 12-1FVKZQ3 12-6E7OR7 7.8.2.5

current sort specification property
of a business component using
Siebel VB/eScript
Internet Explorer freezes when 12-1AQGFAV 12-1AJ5133 7.8.2.5

users drill down on views that
have AutoToggleApplet
With the new eScript engine, 12-1FETWO2 12-1EAIWZX 7.8.2.5

RaiseErrorText uses cached
messages
Adding tables in Word documents 12-1FHYM2Q 12-1B405OT 7.8.2.5

using COM objects fails in the
eScript Engine
The Date object in the Siebel 12-1FN5FL1 12-1FC2209 7.8.2.5

Tools Scripting engine does not
accept documented formats
With DELETESKIPPRIMARY = 12-1DOTM6B 12-10PHXKF 7.8.2.4

FALSE set in the .ifb file, the
application fails to update the
Primary Position ID value for
Accounts
Browser Scripts are not being 12-1CKP3J8 12-OAS23C 7.8.2.4

executed in 7.7.1 SIA when
customers use Internet Explorer
5.5
The Javascript Date function does 12-1EA1ALT 12-Q63CSV 7.8.2.4

not return daylight saving time
values (Solaris problem only)
The Workflow Monitor process 12-1A9RRS1 12-1A9JLPL 7.8.2.4

crashes when running MS SQL
Server 2005 in '90' compatibility
mode


RaiseErrorText in 12-18E7UPF 12-18BWX0V 7.8.2.3

BusComp_PreQuery crashes the
Object Manager
Querying on custom Multi-Value 12-1CXF67Z 12-ZOXVZD 7.8.2.3

Fields in the Contact Business
Component causes a database
error
Runtime script is not working in 12-19XOA7J 12-131AXY2 7.8.2.3

the thin client (AIX)
SiebelAX_Desktop_Integration 12-19BPHBK 12-166MVYV 7.8.2.2

"referenced memory" error
Users are not able to add or view 12-14YL4RE 12-JQ66YF 7.8.2.2

workflow criteria for a "User
Defined Exception" exception
Workflow step branch
Certain configuration gestures in 12-Z2WL0W 12-XJ7NPE 7.8.2.1

Tools cause a unique key violation
Internet Explorer crashes when 12-10GJ7D2 12-XBY5XU 7.8.2.1

dynamic toggle applet is
configured
The Business Service Pick Applet "12-145297B 12-13I057B 7.8.2.1

is empty in Siebel Workflow when
the repository name is changed
from "Siebel Repository
Upgrade
The SQL file vod_diff_rpt.sql 12-12IR07K 12-12IR02G 7.8.2.3
contains a defect
The “Migrate ICL Objects to 12-1694CBR 12-15X1FEJ 7.8.2.2

Standard” utility crashes Siebel
Tools with the SBL-DAT-00382
error
The “Migrate ICL Objects to 12-16KIYHZ 12-15X7O2Q 7.8.2.2

Standard” utility does not
correctly identify “Within Lag
Time” objects
The DB Install for V7.8 is failing 12-123LPE2 12-11IUUDN 7.8.2.1

on Unix for S_CTXT_SGNL_SVC
table.


Users are unable to run the 12-ZD3FTR 12-ZCUC6P 7.8.2.1

mainframe-centric development
upgrade on DEU
Web Framework
In Siebel applications version 7.7 12-1KWUQXA 12-Q47T8B 7.8.2.8
and higher, users can open
picklists in read-only fields
Exporting from browsers that are 12-1JNABCM 12-1J1X6NA 7.8.2.8

running Windows 2000 SP1 or
Windows XP SP2 causes session
timeouts from Siebel 7.7.2.6
onwards
After Siebel 7.8.2.6 has been 12-1KJQLDF 12-1K3Z5YW 7.8.2.8

installed, clicking the brower's
Back button causes the last
selected record's history to be
lost
When a new record in the Client 12-1KPTEZT 12-1KCM430 7.8.2.8

Private Note screen is created,
and text is entered in the
description field, the text does
not appear
UseANSIControlsForCP = CP932 12-1KUES2O 12-1KPTOMP 7.8.2.8

does not work in the Siebel
7.8.2.6 .cfg file
When users select Print from the 12-1HIUOL8 12-INEDTT 7.8.2.6

File menu in Internet Explorer, a
blank page or just the tabs print
Makes Siebel ActiveX controls 12-1BJOS21 12-1BJHOCC 7.8.2.3

interactive when they are loaded
to support the Microsoft Internet
Explorer 6 patch (ACR 317)
Using Real Time Data 12-17QNQPM 12-177WVJJ 7.8.2.3

Deduplication with Contacts
results in an Object Manager
crash
Workflow


Using the browser Back or 12-1J1X7UG 12-1IR1ALS 7.8.2.8

Forward buttons with interactive
workflows causes an error
message to appear
Having user events in start and 12-1JQY2FX 12-1IF8YBJ 7.8.2.8

wait steps of Long Running
workflow process causes infinite
looping
The Custom STOP Step in the 12-1KM9N4I 12-1K0CG45 7.8.2.8

Spread Discount workflow does
not show WF_ERR_CUSTOM_1
mess.text and displays a <?> in a
popup message instead
A user event resumes a long 12-1M3RZ17 12-1KQWSAI 7.8.2.8

running workflow even if there is
no pending instance
Names with spaces get lost when 12-1IDOWKX 12-1IBWHCH 7.8.2.7

concurrent tasks are run on the
same MT Server
Second import of a Workflow 12-12VXX5D 12-12K11K7 7.8.2.2

process sets the criteria value
incorrectly for the decision step
iHelp
Tasks
After QF0663 has been applied, 12-1HJBHF7 12-1H52QJB 7.8.2.6
an error message displays if users
select Item 1, Item 2, Item 3,
Item 4, and then select Item 1
again
Life Sciences
Activity
Appointment duration in the User 12-1J5HADX 12-1J5GM4X 7.8.2.9
Preferences Calendar is ignored in
the Life Sciences Pharma High-
Interactivity Activity Calendar
view


Within the Pharma Professional 12-1JGFDIZ 12-1IFZNA5 7.8.2.8

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
If a Contact Call is created with a 12-1H4DD18 12-1H1DHHZ 7.8.2.7

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. (SBL-
LFS-00223)”
Smart Calls are lost after users 12-1GCG0U1 12-1FS5J53 7.8.2.5

execute a query on the Account
Call Detail view
High memory usage when adding 12-1BD3END 12-1B9ZTQZ 7.8.2.3

Attendee Calls
High memory usage when using 12-1B53828 12-1AIZS4K 7.8.2.3

“Pharma Attendee Call” and
“Signature Capture” fields
Clinical Manager
Trip reports are not locked when 12-121G1R5 12-10YXMXD 7.8.2.2
the status becomes approved
Medical Handheld
Resolves the following Handheld 12-184JL1Y 12-17S2W9Z 7.8.2.4
printing issues: The option
PrinterUser=2 does not work
When Bluetooth is used, it takes
several minutes for the
application to begin printing
When Bluetooth is used,
templates do not print correctly
Other


ACR 347 provides Personalized 12-1G38MUQ 12-1G38MT8 7.8.2.9 Yes, see

Content Delivery. For a “Instructions
description of the enhancements for ACR 347” on
provided by ACR 347, see Table 8 page 182.
on page 50.
When users click the Back button, 12-1FX4U7R 12-RQTT47 7.8.2.5
the account hierarchy displays all
accounts instead of the focused
account hierarchy
After QF1011 has been applied, 12-1E4G80L 12-1DN3PUX 7.8.2.4

memory leaks occur when adding
attendees to account calls
Applying QF1006, QF1007, or 12-1CYDBXP 12-1CY9IV1 7.8.2.3

QF1008 on 7.8.2 SIA ENU
[19213] causes a memory leak,
and then the application crashes
The fix for CR# 12-1B9ZTQZ 12-1BMC36V 12-1BJSGHW 7.8.2.3

causes the application to crash
Adds 2 List Management views to 12-175TSC6 12-175PGQ8 7.8.2.2

Pharma Base application
Pharma Handheld for

Windows
When Regional Settings are 12-1CXAGNT 12-1BXP5ZY 7.8.2.8
changed to Germany, the date
control throws an error message
(ACR 264)
The CalMedEd Method and 12-1CXB4N7 12-1BXYD88 7.8.2.8

UserProp in Calendar & Create
Activity UserProp for 'CSSBCBase'
Business Components fail (ACR
264)
The Enhanced Search Function 12-1CXB4EP 12-1BXRKHI 7.8.2.8

treats each Multi-Value Link field
in a search separately, which
causes more data than expected
to return (ACR 264)
When users perform specific 12-1JFU2NB 12-1JF9KN9 7.8.2.8

steps in CS Sync mode,
S_ACT_PRDINT records are
deleted


When users click the Find button 12-1H5WQ8P 12-1GRXZSP 7.8.2.6

to search for records, the
application returns incorrect
records and then crashes (ACR
264)
The Edit and Help menus do not 12-1GQULV8 12-1FN3JA8 7.8.2.6

open in 7.8.2.3 [19221_3] FRA
When the 'Disburse on Signature 12-1GQTQZ4 12-1FZ4G8Z 7.8.2.6

Capture' system preference is set
to TRUE and the necessary
configuration changes are
incorporated, the Add & Adjust
Qty buttons are disabled for the
transactions of new samples
added
Drilling down into the Contact Call 12-1CMQD3P 12-1BXYDAX 7.8.2.4

from the Activities view and
pressing the Back button in a
contact call throws an error
message when the Regional
Setting for the device is set to
Germany (ACR 264)
The PDA Daily Calendar should 12-1BWU1MH 12-1BOCGNX 7.8.2.4

not display two entries when
Start, End, and Duration are
inconsistent
New calls created from the 12-1BH7V9P 12-18TXPAI 7.8.2.3
Calendar using Smart Call lose
the Parent-Child relationship with
Details records after
synchronization
Setting Validate Professional 12-XQRAPI 12-XL17K0 7.8.2.1 Yes, see

Profile User Property to N results “Instructions
in an error when users tap the for FR 12-
Sign button XQRAPI” on
page 483
The Back button always navigates 12-XQVZ7Z 12-NIEYG1 7.8.2.1

back to today's Daily view
Product Issues


The LS Medical Generic Lot 12-1746TC6 12-171IN9R 7.8.2.3

Admin View and LS Medical
Service Request - Assessment
View are missing from the
Adverse Events module
Protocol Builder
Incorrect activities are created for 12-1M5CF1P 12-1LKD1UF 7.8.2.9
subjects when applying a protocol
amendment
Regulatory Reports
Updates the MedWatch Report 12-1HWES6Y 12-1HG2IH4 7.8.2.8 Yes, see
(LS_3500A) to reflect new “Instructions
formatting and fields (ACR 372) for ACR 372” on
page 182
Samples
On the Mobile Web Client, the 12-1IM5DXH 12-1IINAVP 7.8.2.7
Signature Capture view freezes
when users press the Tab key
Calls are marked as signed but a 12-1JK4O41 12-1JK3LTD 7.8.2.7 Yes, see
signature record does not exist “Instructions
for FR 12-
1JK4O41” on
page 489
Signature Capture
Signature Capture Pen strokes 12-1GG19N2 12-1E6FMHH 7.8.2.5
intermittently do not get
refreshed in the Signature Control
in UI if the pen strokes are
performed in quick succession
(Tablet PC)
If the Signature Capture view has 12-1GG1E4N 12-1EMFVML 7.8.2.5

been in standby mode, users
receive a "Drawing Failure
message" error message when
they log in again


The signature string is truncated 12-1GG1E3K 12-1E0IX6G 7.8.2.5 Yes, see

when users draw a considerable “Instructions
amount in the signature window for FR 12-
1GG1E3K” on
page 483
Territory Management
Territory rules are translated into 12-1I7EEHR 12-13HEJBV 7.8.2.8
Assignment Manager rules
incorrectly (ACR 296)
The Territory Management 12-1ICZRG7 12-1I1IH18 7.8.2.7

Alignment Conditions view does
not work after users apply ACR
263
Internet Explorer crashes after 12-1IKK1DF 12-1IFNSNX 7.8.2.7

users create condition records
using the Tab key
The From/To function wipes out 12-1IULVJO 12-1IOLYSM 7.8.2.6

data
Assignment tasks fail if any of the 12-1EOUP61 12-1EEVL37 7.8.2.5

objects processed by Territory
Management no longer exist in
the database
Alignment activation generates 12-1F1V37W 12-1EDTC7J 7.8.2.4 Yes, see

duplicate columns in “Instructions
S_POSTN_CON for ACR 263” on
page 73
Local conditions that include 12-1D5ZWYG 12-1COEPTQ 7.8.2.4

division and territory values do
not work properly
Batch assignment exits with an 12-1EKD42H 12-1DXDURP 7.8.2.4

error when all positions from the
same rule group are removed


When Territory Management 12-1ELF7SP 12-1EJHHQR 7.8.2.4

attempts to insert records in
S_POSTN_CON that already exist
and have the columns
ASGN_MANL_FLG and
ASGN_SYS_FLG set to 'Y' and 'N'
respectively, the position-specific
data for these records (e.g. Last
Call Date) is erased
From Territory # and From 12-1CR7O69 12-1A9JPZL 7.8.2.3 Yes, see

Territory Name should not be “Instructions
displayed on territory rules (ACR for ACR 263” on
263) page 73
Conditions sequence order is not 12-1D0UC11 12-12TI4D4 7.8.2.3

followed on TOS search
specification
Creates a new local condition 12-14O2RGV 12-11H2U2X 7.8.2.3 Yes, see

called "Division" that allows users “Instructions
to specify conditions by division in for ACR 263” on
cases where they group multiple page 73
divisions under the same territory
hierarchy (ACR 263)
Cursors are not closed on Oracle 12-17F41LP 12-ZJ1AG5 7.8.2.3 Yes, see
9i when running and activating “Instructions
alignments in Territory for ACR 263” on
Management (ACR 263) page 73
Provides users of Territory 12-17F5PP9 12-11AA4CY 7.8.2.3 Yes, see

Management with the ability to “Instructions
specify which territories should for ACR 263” on
exchange position-specific data page 73
(ACR 263)
Boolean attributes are not 12-17RHDKG 12-1769YNL 7.8.2.3
supported by Territory
Management conditions
Execution of Assignment Manager 12-17UGUMJ 12-17IAP5R 7.8.2.3 Yes, see

rule groups created by Territory “Instructions
Management does not pass rule for FR 12-
group id as a parameter, which 17UGUMJ” on
leads to incorrect assignments page 484
(ACR 263)


Loyalty
Loyalty Engine
Loyalty engine may process some 12-1DT6JSR 12-182BQGQ 7.8.2.7
transactions twice
Provides the following Cancel 12-1FTNFD6 12-15J386J 7.8.2.5 Yes, see

Transaction Attributes “Instructions
functionality (ACR 272): for ACR 272” on
page 117
■ It allows the application to
update the current numeric
total to reflect the current
total lless the addition (or
subtraction) of the cancelled
numeric attribute.
■ It allows the application to

reject redemptions that go
above the member's available
balance even if the member
has canceled accrual
transactions in the past.
New transactions are not rejected 12-18P6Z1C 12-151D7AB 7.8.2.4
if member has a negative point
balance
Frequency promotion does not 12-18POOUN 12-178LRJ9 7.8.2.4

give points when the first rule
updates a promotion-specific
attribute and the second rule
gives points
Redemption transactions do not 12-18Q0F81 12-14XETXW 7.8.2.4

process using a non-integer
number of points
Provides Retroactive Tier 12-1EJW47N 12-106O61K 7.8.2.4 Yes, see

functionality so that points are “Configuration
allocated based on the actual date and Program
of the transaction (ACR 252) Setup
Instructions for
ACR 252” on
page 69


Actions for a Loyalty Promotion do 12-18PJU29 12-18P8ATF 7.8.2.3

not allow an attribute to be
updated
Marketing
Campaigns
Promotion of a prospect does not 12-1KIOBZN 12-1K801GD 7.8.2.8
populate the Industry SIC code
onto the account
Wave launch may fail when 12-1MSUS83 12-1IOMFYR 7.8.2.8

launching multiple waves for a
campaign simultaneously
Wave launch may fail when 12-1J1XLZS 12-1IOMFYR 7.8.2.7

launching multiple waves for a
campaign simultaneously
The Source Code and Offer Code 12-1IV2DOY 12-OBOTLR 7.8.2.7

fields are not populated for
imported responses
If users import a list with 12-1GYQIN1 12-123G6DL 7.8.2.6

additional attributes columns
where some attributes have the
same value across prospects,
some prospects may not be
associated to the list due to
concurrency on the prospect
attributes component
List import does not complete on 12-1AKJRCP 12-19CTFX5 7.8.2.5
the DB2 390 database when a
SADMIN user does not create the
list record
When the Auto Response 12-1FHXST8 12-1CE669P 7.8.2.5

Business Service is enabled,
when users navigate from the
contact list to the Contact Detail -
Opportunities View, they lose
context of the correct contact
after they select a source in the
opportunity list applet


When a prospect is promoted, the 12-1GO7GS2 12-1G7QHMK 7.8.2.5

associated address is not marked
as the primary personal address
field on the Contact List Applet
When using 'Promote Many' to 12-198C0K4 12-18Z6YT6 7.8.2.4

promote a large number of
prospects (more than 1000),
memory usage grows and the
Object Manager can fail
Views do not automatically 12-1F4X5PB 12-1F3VZ1N 7.8.2.4

requery when users navigate
between views on the Offers
screen
List Import Service Manager fails 12-1A0YRK3 12-19P4AQY 7.8.2.4

when Maximum Cursor Size and
PreFetch Size reach their limit for
mappable columns
The List Management screen does 12-WY1J8M 12-UZZTFA 7.8.2.4

not display Recipients when F9 is
pressed
Create Opportunity does not 12-12IN2NP 12-YXVZ85 7.8.2.2

associate the Response to the
Opportunity
Email and Web

Marketing
Email campaigns do not create 12-1FZ3O16 12-1EMYMKH 7.8.2.5
activities when the 'Create
Activity' box is checked
Email offer sent date is incorrect 12-12UVOUN 12-Y7MMWP 7.8.2.2
on French version
Events
When a user attempts to alter a 12-1FVKCAC 12-1EWW813 7.8.2.8
large number of records (100+)
using the Change Records
functionality, they receive an "end
of file" error message


Users receive the 'URLRouter5' 12-1G37N3Q 12-1G37N2I 7.8.2.8

view error when using Email
Campaigns and eEvents without a
Web Marketing license
Marketing Server
Allows Campaign loads between 12-1IZO01S 12-1F4YWQ4 7.8.2.7
Siebel 7.7 or 7.8 and Oracle
Business Intelligence Enterprise
Edition 10.1.3.2 (ACR 365).
Campaign load process may take 12-1F60B9M 12-1EOBXNT 7.8.2.5

significant time to complete due
to Assignment query
Mobile Solutions
The letters "o" and "p" cannot be 12-1LMZ3S1 12-1LC0MR7 7.8.2.8
entered in text fields within Siebel
Handheld applications
When users navigate through the 12-1M0NSUR 12-1KL8VYM 7.8.2.8

application using File > Exit , they
receive an error message in the
gwes.exe file
After DSS, after Upload Only, 12-1GUILSZ 12-1GUILQT 7.8.2.7

Handheld Sync crashes if the
network cable is unplugged
The letters "o" and "p" cannot be 12-1I6XS0N 12-1AQS9YX 7.8.2.7

entered in text fields within 7.7.x
Daylight Savings Time is not 12-1HMM75H 12-1GSGXNY 7.8.2.6

incorporated in Handheld
timestamps
Companion Sync fails when the 12-1HE1UD5 12-1GO748L 7.8.2.6

Mobile Web Client is not
connected to the network
The Default Time in the Date/ 12-1GQULWX 12-1G63R0D 7.8.2.6

Time popup window does not
reflect the User Timezone/current
time (WM5)


Promotional Items records are 12-1GP72KO 12-1E9ZZ7I 7.8.2.5

not created after users sign
Contact Calls
Records are lost when timeout 12-1FV2QM6 12-1FLGF8L 7.8.2.5

occurs at a certain point in time
during UploadOnly for BatchSync
capability
There are layout and translation 12-1FX4TWT 12-1FBZFNC 7.8.2.5

issues with the PTB and ESN
languages in 7.8.2.3 [19221] -
WM5 [19221_1]
The Handheld application does 12-1GAJNC3 12-1G6P9GP 7.8.2.5

not start automatically after
synchronization when it is
running in BatchSync mode
The Help menu [Guida] does not 12-1GCY4Q2 12-1G0Q5BY 7.8.2.5

open in 7.8.2.3 ITA
Multiple Sample Adjustment to a 12-1FN4CAJ 12-17K2KR5 7.8.2.5

disbursement can cause
Inventory to updated twice
Ports Siebel Handheld 7.8.2, 7.7, 12-1F7YDR5 12-1EUHZ81 7.8.2.4

and 7.5 to Windows Mobile 5, and
certifies HP hx2790 and Dell X51
(ACR 305)
In WM5, the string returned from 12-1FAZLF4 12-1F5JMQD 7.8.2.4

the version DLL cannot be
typecasted to a CString, and
therefore it leads to a loss of data
Handheld Sync conflict resolution 12-1B53EPO 12-19CWR0Y 7.8.2.4

displays the incorrect date and
time
The letters "o" and "p" cannot be 12-1BWSYWQ 12-1AQS9YX 7.8.2.4

entered in text fields within 7.7.x
PDA synchronization times out if 12-1EQGLY1 12-1ELX0H1 7.8.2.4

remote synchronization takes
more than 10 minutes


The Inventory Reconciliation in 12-1302EXD 12-11R8EBT 7.8.2.4

RMA function does not work
properly in some scenarios
The first record of the Find Result 12-19MQWUH 12-15YD10N 7.8.2.3

List from the Find Feature in the
Account and Contact Detail View
is overwritten
An error is generated when 12-190MOHR 12-17AVPKH 7.8.2.2

running "\batchsync.exe -f
D:\siebel\ses\siebsrvr\hhsync\Ba
tchRepository.ini -e
Find/Query functionality is not 12-1208NSU 12-1203DJ5 7.8.2.2 Refer to

supported in Handheld (ACR 261) Technical Note
644 (Doc ID
473933.1 on
OracleMetaLin
k 3) for
information
about how to
apply this fix.
Users are unable to update 12-13MD2PH 12-1345YIL 7.8.2.2

siebel.ssf and print templates
using patchagent
Handheld Sync process does not 12-13MD31V 12-131506T 7.8.2.2

terminate after an "Upload Only"
synchronization session when
Patch Agent is running
Patch Agent is invoked twice if 12-14Y0FIZ 12-145WXY2 7.8.2.2

batchsync is enabled or if two
patch files on the server are in
non-batch sync
Within Conflict Administration, 12-16DS026 12-15YZYAT 7.8.2.2

clicking 'Reapply' modifies the
Last Tran Id, which may lead to
duplicate records
Changing the Primary Address 12-16VSNHP 12-15UEFOI 7.8.2.2

Designation of an account is not
replicated up to the server


Users receive the following error "12-17HZG3W 12-15ONRTT 7.8.2.2

message: "Application manager
cannot install this application on
your mobile device due to invalid
setup file.
Siebel Handheld does not install 12-17I787Q 12-15AAHO2 7.8.2.2

msdadc.dll, msdaer.dll, and
msdaeren.dll in the Windows
directory
Processing SAF transactions for a 12-XOMIDK 12-XC08KN 7.8.2.1

specific user while trying to sync
with the same user results in a
sync error
Find/Query functionality is not 12-XQRAMW 12-XL2DM9 7.8.2.1

supported
If a backup is performed after 12-1302F25 12-12HO0F6 7.8.2.1

transactions have been created
on the Handheld client, the
backup is incomplete
Resolves a problem where 12-13MD2VD 12-13JNPIH 7.8.2.1

columns and grids are shifted to
the left when the row contains
empty field(s) (ACR 243/244)
Resolves an issue where the 12-13MD2XP 12-13J04RN 7.8.2.1

PrintUserSelect parameter does
not work if it is specified in the
setup.ini file (ACR 243/244)
Applet and List tags can print data 12-13OPWXU 12-13OORO3 7.8.2.1
tables even when there is no
record (ACR 243/244)
Other
Transaction Router crashes when 12-1K404ES 12-1K20DOB 7.8.2.7
new events are created


Provides better support for using 12-148TNZ6 12-VYZRWI 7.8.2.1

variables as parameters and the
SQL WHERE clause as a Search
Specification to various TAGS,
provides 15 new TAGS and 6
enhanced TAGS for formatting
flexibility, and provides a printer
dialogue box for choosing printer
opt
Store-and-Forward
Messaging
Form applets become read-only 12-11WDCCD 12-11NFBMX 7.8.2.2
after a Store and Forward
message is received
UTC conversion does not work 12-10GJ72J 12-108G0EC 7.8.2.1

when activities are sent through
Store and Forward
Blank date values do not come 12-11JKRF6 12-10IZ9E8 7.8.2.1

down when an activity is sent
through Store and Forward
Messaging
Store and Forward Messaging 12-12KF1VQ 12-VS49YS 7.8.2.1

calls to Handheld Sync should
honor load balancing (ACR 242)
Wireless
Users are not able to add a new 12-1N3J9S3 12-1N3Q0NZ 7.8.2.8
calendar record in the wireless
application
When the user enters an expired 12-138MYBG 12-131HN9G 7.8.2.1
password, the Wireless
application fails and shows the
user XML
Partner
Relationship
Management
Marketing
Development Funds


Recalculations of 90 days and 12-1IGM0SI 12-1IGM0QP 7.8.2.8 Yes, see

90+ days buckets of Market “Instructions
Development Funds Period End for FR 12-
Snapshot records yield negative 1IGM0SI” on
balances page 491
The MDF Paid field values are 12-1J6K6W7 12-1J2FZN1 7.8.2.8 Yes, see
rounded off, which makes the “Instructions
ending balance of the current for FR 12-
period and the beginning balance 1J6K6W7” on
of the next period incorrect page 492
Negative MDF adjustment values 12-1JOGRKT 12-1JC7EHV 7.8.2.8 Yes, see

cause incorrect values for MDF “Instructions
period snapshot fields for FR 12-
1JOGRKT” on
page 492
The HTIM MDF Period Ending 12-1EMGCMM 12-1EMGCLP 7.8.2.5 Yes, see
Process workflow does not “Instructions
produce correct snapshot records for FR 12-
and information 1EMGCMM” on
page 484
Partner Portal
When attempting to add 12-1AQDGZO 12-19YVICO 7.8.2.3
attachments through a toggle
applet, the user may receive an
unexpected error message
indicating a problem with an
unsaved attachment
Professional
Services
Professional Services
Automation
Microsoft Project Export issues 12-1HQH1J5 12-1HG1QKF 7.8.2.7
related to predecessor field
The Baseline Start/Finish fields 12-1H91USE 12-1GLKAML 7.8.2.6 Yes, see

are overwritten when exporting “Instructions
from the Siebel application to for FR 12-
Microsoft Project 1H91USE” on
page 484


Sales
Forecasting
When users create a Forecast 12-1G8YUH5 12-1G75OUN 7.8.2.5
record, define a forecast series,
and then save the record, they
message: SBL-DAT-00235: Value
too long for field 'Win Probability'
(maximum size 16)
The Forecast applet scrollbar 12-18FUSM2 12-18CF6WR 7.8.2.4

record counter shows incorrect
numbers
The scrollbar freezes in the 12-1BBSD86 12-1BAJ9TU 7.8.2.4

Forecast 2000 -- Forecast Item
Detail Flat view
The Forecast applet scroll-bar 12-1BBPDLU 12-1BAJ9OH 7.8.2.4

record counter shows incorrect
numbers
The "Add Revenue Items" pick 12-13K71WZ 12-13JKAJ9 7.8.2.4

applet shows additional records
that could result in an incorrect
forecast
Ability to suppress the option of 12-160M4OD 12-1459GUH 7.8.2.4

creating subordinates' forecasts
The Forecast Date is incorrectly 12-190KW6Z 12-18Z0TXP 7.8.2.3

set in the summary detail view
The Change Record operation is 12-152H7VI 12-14UGUEK 7.8.2.2

not allowed on SQL objects in
forward-only mode
Opportunities
Numeric and picklist fields 12-1K2K9T6 12-1JD9K31 7.8.2.8
temporarily blank out after Siebel
7.7.2.8 has been applied
In Siebel Industry Applications 12-18YMRAC 12-16EVUR7 7.8.2.5

FINS version 7.5.3.x, Proposals
stay in "Queued" status


The Quota Report does not show 12-17ZZ47N 12-160RURQ 7.8.2.5

the complete list of opportunities
The Opportunity - product picker 12-12L1DQZ 12-12J5YTD 7.8.2.4

applet should not enforce
catalog-based visibility
The "Replace Revenue" Button in 12-145KR01 12-12UHCTF 7.8.2.4

the Revenue Schedule
SmartScript does not change the
new values defined in the UI
Other
Cancel Query Function in the 12-1KXW6NX 12-1GE3EGA 7.8.2.8
associate applet is not working
properly
When users navigate to Contacts 12-1LDERE6 12-1L4HE3E 7.8.2.8

> Contacts List, and toggle
between the List and Form applet
fields of a record, the fields in the
upper list applet appear to
become read only and cannot be
edited
The 'Dynamic Hierarchy' and 12-1BVPJ8N 12-19LNZC7 7.8.2.5

'Dynamic Hierarchy Parent
Account' Business Components
leave cursors open in the
database
Adding attendees in the Account 12-1CURG8R 12-1CMUHMR 7.8.2.4

Call Detail view takes a long time
to process
Removing an Account from a 12-1E7JJLC 12-1E1TYHP 7.8.2.4

contact using a MVG field causes
Dynamic Hierarchy deletion
Account merge fails if there is no 12-1D08U5H 12- 7.8.2.4

account hierarchy defined 17BDXWM
Pick List Values are based on the 12-1AD57WG 12-192QTBD 7.8.2.3

user position context and not the
record context
Invalid Hierarchy Accounts are 12-YRYRXK 12-W5Z2VV 7.8.2.1

created by merging records


After Merging Accounts, some 12-YSJSDC 12-WC72DZ 7.8.2.1

Dynamic Hierarchy Relationship
records remain
Creating contacts and undoing 12-ZCT50I 12-WFAB6C 7.8.2.1

them without saving creates
orphaned intersection records in
tables
Territory Management
After ACR 263 has been applied, 12-1J3KLN2 12-1J3KLM8 7.8.2.7
alignment activation fails on DB2
Service
Contracts
Agreement Line Item Charges are 12-1IPNY4N 12-1H08UL2 7.8.2.7
incorrect after switching to
The 'FINS Data Map Admin View' 12-1E0CMZN 12-1E0CMX1 7.8.2.4

is missing from HOR agreements
functionality
The Entitle button throws an error 12-15J38H8 12-1502YMK 7.8.2.4

when duplicate product names
exist
The "Use Plan View" and the "Use 12-1A15M7L 12-150H3VT 7.8.2.3
Plan Line Item View" are missing
from Option 74
Logistics Manager
Allows bulk transfer of assets and 12-1G0QIGI 12-1ADKL0H 7.8.2.5 Yes, see
inventory (ACR 308) “Instructions
for ACR 308” on
page 124
Subsequent pick tickets are not 12-19PIUWV 12-17QTH02 7.8.2.3

being generated for existing
orders that have been partially
shipped
The Ship All button leads to 12-16OKGCW 12-16EHBLB 7.8.2.2

shipped items that lack inventory
updates


Other
Within the Letters tab of a Service 12-1HPHX1Q 12-1HM2FEF 7.8.2.8
Request, when users select a
letter template and click the
Generate Draft button, they
When there is a database with a 12-1KTTP9H 12-1G6MQ04 7.8.2.8 Yes, see

high volume of Asset records “Instructions
(>10,000), when the standard for FR 12-
Asset view is displayed, users 1KTTP9H” on
receive the following error page 493
message: “There are more rows
than could be returned. Please
refine your query to bring back
fewer rows (SBL-DAT-00500)”
The XA List Applet Columns 12-1GO6TNW 12-13ZDWGB 7.8.2.6
Displayed function does not work
When users query on the date 12-1FTLSIT 12-1FBH4M1 7.8.2.5

field within eService, the
application does not recognize
the quotes, and no records are
returned
Smart Answer is not able to filter 12-194MXVW 12-18GYOIH 7.8.2.5

the low-score categories
The Field Service application 12-1348323 12-12F1LO5 7.8.2.4

stores Order by Clause from
Predefined Queries, which causes
performance problems
The srvrinit utility fails on HQ as 12-17BFK19 12-15LVRJM 7.8.2.2

HP/Oracle 10g and on Regional
as Win2003/MSSQL
Within the Dispatch Board within 12-15AQK1L 12-14ZP8YY 7.8.2.1

Siebel Field Service, thePlanned
GanttChart AX Applet (top applet)
does not display correctly
Preventive
Maintenance


With a large number of assets 12-19O65U1 12-17L31IT 7.8.2.4

(100,000), Preventive
Maintenance performance
degrades significantly
The Preventive Maintenance 12-12X6OKI 12-12IIOVF 7.8.2.2

Engine crashes when the value
set for Oracle Max Cursors is
reached
Scheduling
ABS LoadActivities crashes on 12-1I1FYK8 12-1HTFNUN 7.8.2.8
activities with planned start dates
within glued periods or outside of
the horizon
ApptBook fails during 12-1I1FYGM 12-1H8J1VY 7.8.2.8

ReloadServiceRegion when
inserting an activity with Planned
Start < ABS Load Time
After 7.7.2.5 SIA QF0533 has 12-1FLI24K 12-1E8PE3B 7.8.2.8

been applied, the ABS
LoadActivity method goes into an
infinite loop
Even if there are incompatibilities "12-1LRPP07 12-1HIVEAL 7.8.2.8

that prevent Activities from being
loaded into the cache, the
Optimizer should not change the
status of an Activity to
"Unscheduled
The Calculate Distance button in 12-1ICP9BF 12-1I6E093 7.8.2.7

the Dispatch Board does not
consider the right starting
addresses for certain scenarios of
Field Engineers
ABS does not return slots if the 12-1FCN39P 12-1FA0R12 7.8.2.7

timeslot result's Slot Start time
matches the activity Latest Start
Running the optimizer with the 12-1CALWFP 12-1BID53P 7.8.2.5

value of "ABS Days to Start = 1"
does not yield the the right
results


Loading Appointment Based 12-1BSO1UI 12-1BOKCMV 7.8.2.5

Scheduling blanks out the Owner
ID field of an Activity when an
employee has exception hours
during the Activity timeslot
The "Load Activities" method 12-1FLI23G 12-1DYTORN 7.8.2.5

loads all activities, even including
those that should be excluded
based on the "Abs Activity Status"
parameter
iLog consumes lot of memory to 12-1A0XC26 12-18OC5L6 7.8.2.5

cache the costs for each visit, and
exceeds the system limit
Dispatch Board loses query 12-12X6O29 12-11ZD1BJ 7.8.2.1

context after drilling down
Siebel eMail
Response
General
Scheduling
ABS LoadActivities crashes on 12-1I1FYK8 12-1HTFNUN 7.8.2.8
activities with planned start dates
within glued periods or outside of
the horizon
ApptBook fails during 12-1I1FYGM 12-1H8J1VY 7.8.2.8

ReloadServiceRegion when
inserting an activity with Planned
Start < ABS Load Time
After 7.7.2.5 SIA QF0533 has 12-1FLI24K 12-1E8PE3B 7.8.2.8

been applied, the ABS
LoadActivity method goes into an
infinite loop
Even if there are incompatibilities "12-1LRPP07 12-1HIVEAL 7.8.2.8

that prevent Activities from being
loaded into the cache, the
Optimizer should not change the
status of an Activity to
"Unscheduled


If users pressing F9 to invoke the 12-1GVNRYI 12-1GREQAR 7.8.2.6

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
The Internet SMTP/POP3 server 12-15Y9RRI 12-15E1C76 7.8.2.6

communcations driver is unable
to complete the parsing of an
inbound message that has a
message body of circa 1 MB
(Solaris only)
InboundMgr crashes on assert 12-138ZEER 12-136BGV4 7.8.2.2

when plain-text emails are
detected
Travel &
Transportation
Other
On HP-UX, the Object Manager 12-YR830J 12-Y4ZA3B 7.8.2.1
crashes whenever the user
navigates to the Function Space
Diary screen
UAN General
Anomalies
Other
When Data Quality is enabled for 12-1IAE2QU 12-1IAC6SB 7.8.2.7
customized Business Objects/
Business Components, users
receive a "BO not found" error
message
Universal
Customer Master
Other


Country is a required field for 12-1H610RP 12-1GZ7TLM 7.8.2.7

searching Dun&Bradstreet by a
DUNS number
There is no search spec on 12-1HIUYVZ 12-1HG1BO5 7.8.2.6

S_UCM_CONTACT during the
conflict resolution merge process,
which can result in severe
performance issues with large
volumes of data
Within the Administration- 12-1FRYM89 12-1F8YZRL 7.8.2.4

Universal Customer Master
screen, Publish/Subscribe view,
the time and date values reflected
in the Last Published field can be
more recent than the time and
date values reflected in the End
Date field
Universal
Customer Master
Survivorship
A field value is protected during 12-1L23WZR 12-1GV13QB 7.8.2.8
the first update by SE but it is not
protected by subsequent updates
User Interface
Administration
If a user updates the Default View 12-119RXI3 12-Y1C4KF 7.8.2.1
for any screen (where there was
no view set as default), the next
time when user logs in, he cannot
see any other view than the
Default View that he previously
selected for that screen
Controls


Users are experiencing the 12-1IW730Q 12-1HWCC3D 7.8.2.8

following issues with focus in the
Sales Order screen:
■ 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
After QF0608 has been applied, 12-1KTWG2B 12-1KOBM82 7.8.2.8

when users attempt to create a
new record, the UI 'Opportunity
Name' field displays the name of
the record that was previously
highlighted
The focus changes to the Internet 12-1LWJZSZ 12-1KMBU6V 7.8.2.8

Explorer 7 browser address bar
intermittently
With Internet Explorer 7, when 12-1K95C90 12-1HZUW8N 7.8.2.7

Enable Health Check=TRUE,
when users launch the application
and click Exit on the Browser
Health Check Window, a login
dialog box appears and the
application hangs.


With Internet Explorer 7, when 12-1K95CCB 12-1HP0M1F 7.8.2.7

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.
With Internet Explorer 7, pressing 12-1K95CF4 12-1HPH4NF 7.8.2.7

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.
With Internet Explorer 7, when 12-1IW72ZR 12-1IBCP2J 7.8.2.7

users try to open Multi Value
Groups, the application hangs
The New File button on the 12-1JA6RTL 12-1IBV1AT 7.8.2.7

Attachments View does not work
after users click on the Internet
Explorer Back button
On the home page of the Public 12-1CQPRG9 12-1CG5OHL 7.8.2.6

Sector application, the
application hangs when users
select Alt+K, Alt+J, or Alt+N
When users work with Answers 12-1F4B38F 12-1ERSEST 7.8.2.5
and view Dashboards, the
application hangs and they
message: "Error: 'length' is null
or not an object”
The application errors out while 12-1G0QY07 12-1FVLCE9 7.8.2.5

navigating through the Employee
Skill view after a Skill Item that is
based on a calculated field with
IIF function is added


Suppression/display of leading 12-1DJZ3WN 12-5PSXQ8 7.8.2.5 Yes, see

zero on telephone numbers “Instructions
for FR 12-
1DJZ3WN” on
page 485
Dynamic toggle causes records to 12-1A9ZFVX 12-18451UP 7.8.2.4

become read-only when stepping
onto form applets from list
applets
An error message should be 12-1CXF65J 12-U0SAEP 7.8.2.3

provided whenever users try to
refine a query that includes the
"OR" Boolean
When a user changes position, 12-1CXF69R 12-160V8TB 7.8.2.3

the application does not refresh
to reflect screens that should be
visible to the user after their
position has been changed
Using the right-click context 12-16VG7H0 12-15ZD78A 7.8.2.3

menu on a different row than the
one that is selected causes
unexpected behavior
Some date formats are not 12-WY1IUL 12-OZ0F9T 7.8.2.1

automatically converted
History/Back/Refresh
After Siebel 7.8.2.4 has been 12-1JLEK1T 12-1IGLRHV 7.8.2.8
installed, when customers run a
query and then run a second
query, the results from the first
query still display
When users drill down on a query 12-1LZLGST 12-1JVHT5J 7.8.2.8

and then click the browser Back
button, they are returned to an
older query, not the query that
they had just been looking at
Using a Query Mode Standard 12-1IACZSW 12-1IADASB 7.8.2.7

Interactivity template in High
Interactivity applications causes a
problem with the browser's Back
button


If users perform an action in a 12-1H5KDTY 12-1H1ZGMT 7.8.2.6

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
When users perform queries in 12-1D36SZ9 12-E49VJE 7.8.2.4

applets that have the "Auto Query
Mode" property set to "New
Query," navigate to another
view, use the Back button, drill
down into another view and then
click the Back button, a new
query is executed on the applet,
the cont

Performing a SRF full compile on 12-1E3VAOI 12-1DT9615 7.8.2.8
Siebel 7.7.2.4 causes Internet
Explorer to crash
On Siebel 7.8 applications 12-1JAAYNR 12-1J6KROP 7.8.2.8

running Oracle 10g, Turkish
characters do not display
Within Siebel 7.8.2.6, not all 12-1LI4GDI 12-1L4K0LS 7.8.2.8

views are displayed in the Show
drop-down list
The cursor sticks when typing 12-1LJ7LI3 12-1L3FCL3 7.8.2.8

text in the Hebrew version of
Siebel applications
Using Spell Check on a read-only 12-1EYYP9M 12-1DCNRBA 7.8.2.7

field crashes the Object Manager
(on Solaris)
The layout becomes invalid when 12-1IP5OTE 12-1I6VHOH 7.8.2.7

switching to a new mode on
applet toggle from the base mode
In Proposal Documents that 12-1GEMLLR 12-1GALIJ5 7.8.2.6

contain tables, some words in the
columns spread over two lines


In the Siebel Employee 12-1F1CW7D 12-HFOTMD 7.8.2.6 Yes, see

Relationship Management High “Instructions
Interactivity application, when for FR 12-
users attempt to invoke the 1F1CW7D” on
GotoView method, the following page 485
error message appears: "We
detected an Error which may have
occurred for one or more of the
following reasons: W
The application-level menu does 12-1H734ZZ 12-1H734R3 7.8.2.5 Yes, see
not display properly and does not “Instructions
behave as expected for FR 12-
1H734ZZ” on
page 485
Users are unable to change the 12-1EYH1GD 12-1CSSQO7 7.8.2.5

font size in Cascading Style
Sheets
In version 7.7.2.6, when users 12-1F0CIV0 12-1EME00F 7.8.2.5

click the Next Record and
Previous Record buttons on form
applets, the buttons become
large and bold
Within the Opportunities 12-1G0OP85 12-1CX92OK 7.8.2.5

Attachments screen, when users
change the column layout or
column width, and then log out,
their changes are not saved
Allows users to be able to access 12-1FFMTX4 12-1BSM70H 7.8.2.5 Yes, see

the Report Server screen using “Instructions
Mozilla FireFox 1.5.0.1 (ACR 323) for ACR 323” on
page 158
The application crashes when 12-1GGP7VV 12-1GA27ON 7.8.2.5

users log into the application
again within the same session,
because the application is still
trying to clean up objects from
the first login
Weekday names are translated 12-1GK3P0B 12-1GE0B0B 7.8.2.5

incorrectly in the Calendar Popup
Applet (CHT)


The "New from Template" and 12-1EEYWT7 12-1AD8P9Z 7.8.2.4

"New from last template" buttons
are still enabled in read-only
views
The Show drop-down list does not 12-15XTV9C 12-13Y8RWZ 7.8.2.4

display all selections (Japanese)
The ampersand character '&' is 12-184TGMJ 12-17ZMIP6 7.8.2.4

displayed as '&' in error
messages
Home Page Applets are not 12-17ER1UB 12-UA5DSZ 7.8.2.2

minimized when there are no
records to display
All of the Visibility drop-down list 12-WH5F05 12-QKWE5T 7.8.2.1

options do not display if Windows
fonts are set too large
Navigation
Order View Tab Layout does not 12-1KFNOKX 12-1K0WED0 7.8.2.8
work in the Siebel 7.8.2.4 and
Siebel 7.8.2.5 applications
In the Korean version of Siebel 12-1KUF8GF 12-1JBP01G 7.8.2.8

applications, the Show drop-down
list does not show all available
values
Clicking on the "Quick Print" icon 12-1JKN7B5 12-1JGAPVH 7.8.2.7

does not commit the record
Drilling down in Standard 12-1JQYCYM 12-1CRT154 7.8.2.7

Interactivity mode does not
change the focus of the Screen
Tab
The Site Map does not function 12-1HWXFNB 12-1HP0N3Q 7.8.2.6

after "EnforceSSL" is set to TRUE
for enabling SSL Accelerators
Detail applets do not open when 12-1HH39BA 12-1HDL8TA 7.8.2.6

the control is set to read-only
Other
Symbolic URLs that use iFrames 12-1K8JZBR 12-1I0GSVR 7.8.2.8
cause Server Sessions to fail to
time out


Within the Calendar tab of the 12-1HBJRWZ 12-1H09LEB 7.8.2.8

Opportunities home page (FRA),
the accented characters for the
short months (February, August,
December) appear as boxes.
When users put the cursor in a 12-1M4ULQH 12-GFPPTB 7.8.2.8

form applet field control and
right-click within that control the
Siebel Applet menu appears,
whereas if users put the cursor in
a list column and right-click
within that list column, the
Internet Explorer menu appears
With Internet Explorer 7, the 12-1IW734W 12-1HXDQY7 7.8.2.7

cursor does not appear in the
Phone number field after an
incorrect phone number has been
entered
The Y axis is incorrectly labeled 12-1IH2L5Q 12-1E6WSOI 7.8.2.7

on charts
sXML interface returns either 12-1IE0NOV 12-1GUZY3H 7.8.2.7

ERROR tag from AOM with
different message
The GetCalendarData method is 12-1IRMNYB 12-1IHL5T5 7.8.2.7

missing a WHERE clause, so SQL
retrieves all of the activities in the
Activity HI Calendar applet
With Internet Explorer 7, users 12-1IW6MEZ 12-1IAD8KB 7.8.2.7

should not be allowed to close
Pick Applets by Alt+Q
With Internet Explorer 7, when 12-1IW72WF 12-1HZUQAV 7.8.2.7

users export records to HTML,
open the HTML file, and then
close it, the application hangs and
they must refresh the browser
With Internet Explorer 7, within 12-1IW72YS 12-1I0XVCO 7.8.2.7

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


With Internet Explorer 7, when 12-1IW731P 12-1HTDF2J 7.8.2.7

the picklist dialog box appears,
the first record is not highlighted
Check boxes on the Tab Layout 12-1HWEE17 12-1HSENIN 7.8.2.6

screen are not displayed after
adding "EnforceSSL=True"
setting
Status Images on Server 12-1HUG91Y 12-1HSENBO 7.8.2.6

Administration Screen are not
displayed after adding the
"EnforceSSL=True" setting
Users are unable to refine "12-1HNDBHB 12-1H4W95G 7.8.2.6

Opportunity queries that contain
"OR
Applet Menu > Print Preview pops 12-1HGJM8N 12-1CEXDCS 7.8.2.6

up a blank Internet Explorer page
for applets that have dynamic
toggle configured
If users make changes to the 12-12QUV9O 12-XAP0LH 7.8.2.6

standard Product Defect List
Applet and Personal Defects List
view by changing the visibility to
"Al"l for the Personal Defects List
view, they will receive the
following error when they drill
down on a Related CR: "Can not lo
Entering ALT+ENTER multiple 12-184QPCK 12-RD05MP 7.8.2.5

times causes queries to hang
The Object Manager crashes 12-150E8WL 12-KTTO3N 7.8.2.4

when ViewBookmark is deleted
If users create a new parent 12-17VDK5B 12-17SFWUO 7.8.2.4

record and then immediately click
on the grandchild's toggle, (in
effect stepping off the parent
applet record), the record is not
saved
Base mode list applets and chart 12-1BPM9AT 12-TMKKIA 7.8.2.3

applets do not work correctly in
Query mode


The "*=" and "=*" left and right 12-14MHRUY 12-14M4B22 7.8.2.2
outer join syntax has been
deprecated in SQL Server 2005
Suppresses the warning message 12-WY1J2O 12-SI34S5 7.8.2.1

when users delete an
uncommited attachment with
unsaved changes
Performing a Record Count on the 12-XF0XWT 12-VB5PJT 7.8.2.1

My Service Requests view makes
the underlying applets go blank
Query Assistant does not work on 12-10IW43J 12-WHV8BH 7.8.2.1

ALIAS'd fields
Popups/Pick Lists/
MVG/Shuttle
Popup windows cannot be closed 12-1K95CJB 12-1DIFPC9 7.8.2.7
(Vista-specific issue)
Selected records are lost when 12-1IT4L13 12-1IERLCC 7.8.2.7

moving to the first or last record
in an associate applet
When users close a picklst by 12-1IW733X 12-1HWCBX0 7.8.2.7

choosing ALT+F4 or clicking the X
icon, they cannot open another
picklist
Some Popup windows do not 12-1HUG90R 12-1HQ0RZP 7.8.2.6

display correctly after adding
"EnforceSSL=True" setting for
SSL Acceleration
The Contact MVG applet hangs or 12-1HE2YWV 12-1HD1PRY 7.8.2.6

crashes the application in Siebel
7.8.2.4
After QF0526 has been applied in 12-1EWVXT6 12-1EHXT7T 7.8.2.4

7.7.2.5, when users click the New
button in the MVG Applet, the
button invokes a List Applet
instead of a Form Applet


The Accounts screen within the 12-1F1TTN0 12-1EYXYM2 7.8.2.4

Siebel Industry Applications
application, version 7.7.2.6,
renders a list applet instead of a
form applet when users click New
to create a new account
After QF0615 has been applied, 12-1FHZLSS 12-1F9K95T 7.8.2.4

when users open a MVG Applet, a
new pop-up window appears, and
after the user has entered data in
the applet, the data is saved but
the user must explicitly click the
"X" icon to close the applet
A crash occurs when users click 12-1A9AID3 12-19XUD6T 7.8.2.4

the 'New' button after nullifying
an address in the Account
Address MVG Shuttle applet
Closing Pick Applet or MVG with 12-123YVUK 12-10IGUCJ 7.8.2.4

the cursor in the "Starting with"
field loses the cursor on the
particular screen
The Query drop-down list (PDQ 12-18853WI 12-184YOGC 7.8.2.2 Yes, see
picklist) is not available in the “Instructions
ERM application running in for FR 12-
Standard Interactivity mode 18853WI” on
page 485
Tools/Menus/
Keyboard
Accelerator child objects with Key 12-14I9UL0 12-12EM3RC 7.8.2.4
Sequence = ENTER do not work
consistently
Ctrl+Enter key does not work in 12-12BB016 12-10T1R6R 7.8.2.1

pick applet pop-up window in
7.7.x.
Web Service
Other


When a Web Service calls a 12-1E4WYF3 12-11QVOFA 7.8.2.4

workflow process with the output
argument of type "Integration
Object," SBL-EAI-04007 error
message occurs: “Integration
Object Message error -- object
list property set has wrong type:
'%1' (expecting '%2')”
When an Outbound Web Service 12-1EG0TH0 12-155LVQC 7.8.2.4

that has binding
SOAP_RPC_ENCODED, users
message: SBL-EAI-04019:
Required message header
property 'IntObjectName' is
missing or invalid
Instructions for FR 12-1TG588V

■ Add the following user property to the 'LOY Engine Transaction' Business Component:
■ Name: Point Expiration Start Date Field
■ Value: Point Expiration Start Date
Instructions for FR 12-1SOZHFL

1 Within Siebel Tools > Applets, query for "LS Pharma Call Signature Form Applet".
2 In the 'Search Specification Property' enter [Signature Status]<>LookupValue

("SIGNATURE_STATUS", "Cancelled by User")
3 Compile the applet on to the SRF used by the application server.
4 Restart the siebel server.
Instructions for FR 12-1NC2W1B

1 Log into Siebel Tools.
2 Add the "Pharma Professional Best Times To Call View - CE" responsibility to user SPORTER
3 Add "Contact Id" to "SIS HH LS Contact Best Times List Applet", and then compile the SRF.
4 Synchronize the PDA, using the default BO filters for the PDA.

Instructions for FR 12-1RYK34I

■ Within Siebel Tools, empty the value of the applet user property "Suppress Side Applets Calendar
Types" for LS Pharma Activity HI Calendar Applet and compile the changes.
Instructions for FR 12-1RRBNQC

■ Within Siebel Tools, add an Applet user property called "Refresh On Resize" with value = TRUE
for Activity HI Outlook Calendar Applet, and compile the srf.
Instructions for FR 12-1H808LF

■ In Siebel Tools, navigate to the Service Details applet and set the Time Billable flag.
Instructions for FR 12-1JJHN0A

1 Navigate to the parent applet in the Account Contacts view.
2 Add Bill To Last Name and Ship To Last Name fields.
Instructions for FR 12-1JY2DY3

Use the following procedure to implement this fix:
■ Navigate to Admin Server Configuration > Servers > Components > Parameters, and set the
NumberOfBookmarks parameter to a higher value. However, note that there may be a
performance impact if too many bookmarks are stored.
Instructions for FR 12-1MSUSAH

Use the following instructions to implement this fix:
1 Within SrvrMgr, run the following commands:
change param ShowAdvancedObjects=True for server <server name> comp ServerMgr
change param ShowHiddenObjects=True for server <server name> comp ServerMgr
2 Bounce the server to check for these parameters
Instructions for 12-1G2PJWA

1 Within Siebel Tools, navigate to Business Components > FS Activity Symptom.
2 Within User Properties, add a field with the following values:
■ Name: "ForeignKeyField"

■ Value: True
3 Query for the List Mgmt Lists Business Component, and within the Subtype Code field, set 'Force
Active' to TRUE.
4 Compile the SRF.
Instructions for FR 12-1RAJ8M6

1 Launch Siebel Tools connected to the server data source.
2 Lock the “ISS Authoring Admin” repository project.
3 In Object Explorer, select the “Business Service” object.
4 In the Business Services list, query for the “ISS Authoring Import Export Service” Business
Service.
5 Go to View > Options > Object Explorer.
6 Uncheck and recheck the Business Service object on the list and click OK.
7 Expand the Business Service object and select “Business Service User Prop” from the list.
8 Make sure that you have selected “ISS Authoring Import Export Service” in the “Business
Services” applet on the right side of the screen. (Note that there are two applets called “Business
Service User Prop”.)
9 Add a new record in “ISS Authoring Import Export Service” from the “Business Service User Prop”
applet.
10 Enter the values as is without double quotes. Name = “AutoProceed” and Value = “Y”;
11 Navigate to Tools > Compile Projects.
12 Select “ISS Authoring Admin” from projects list, and select the “Selected projects” option if it is
not already selected.
13 Make a backup copy of your existing siebel.srf (or siebel_sia.srf) file.

14 Locate the original copy of siebel.srf (or siebel_sia.srf) file. This file is located within the
“siebel\objects\enu\” relative path. Make sure that this file is not being used by any application
(Siebel application or Siebel Tools), because the compilation will fail if this file is being used.
15 Press the Compile button to incorporate the changes into the new .srf.
Instructions for FR 12-1IM67NE

■ Convert the application to SI+ mode by setting High Interactivity=FALSE and Application
Style=EmployeeFacing.

Instructions for FR 12-1QT8F4O

Use the following procedure to configure the System Alert for PIMSI Engine errors.
To configure the System Alert for PIMSI Engine errors

1 Navigate to to Administration > Server Configuration > Enterprise > System Alerts.
2 Create an alert definition (such as Administrator Email Alerts) with the following alert
parameters:
Alert Definition
Name Alias Media Description
Administrator AdminEmailAlert EmailNotification

Email Alerts
3 Create Alert Parameters as follows:
❏ SMTPServer: The name of a server with an SMTP mail service enabled. IP Address or
Server Name are appropriate.
❏ SMTPServerPort: The port on which the SMTP mail service or daemon is listening.
❏ AdminEmailAddress: The destination email address for any alerts.
❏ FromAddress: The email address from which the email alert should be sent.
❏ DLLName: Must be ssemailntfy.

4 To configure the Email Template for PIMSI Engine Errors, navigate to Administration PIMSI Server
Integration > Configuration Profile : Exchange Calendar
NOTE: The Domain name should be the same as the Domain Identifier field in Administration->
PIM Server Integration >PIM Domains.
For example:
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 above data, the final email message looks like below :
SSSE fails to synchronize IPM.Task record for the sync enabled user GABBO
The record has following characteristics
Subject: meeting in the month of march
Start Date: 3/3/2008
End Date: 3/5/2008
The error message is: One or more required fields are missing.
Email Template: MsgBody1 Body of the email with place holders. The supported
Domain Name place holders are:
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 the value of the field name

in the parentheses
Note: The Field Name is the Field Identifier column in

Administration > PIM Server Integration
Email Template: MsgBody2 ...Add email body as specified above

Domain Name

Email Template: MsgBody1 \n SSSE fails to synchronize %domain record for the
IPM.Task sync enabled user %login% \n
The record has the following characteristics \n
Subject: [Subject]
Start Date: [Start Date]
End Date: [Due Date]
\n The error
Email MsgBody2 Message was:

Template:IPM.Task %ErrorMessage%
5 Increase the maximum notification size to allow large mails:
a Set Notify message size to 1024.
b Srvrmgr>change param NOTIFYMSGSIZE=1024 for server <servername>
NOTE: If message size is not increased, the system sends the smaller message with less details.
Instructions for FR 12-1Q44F2K

1 Within Siebel Tools, navigate to the ‘LOY Engine Transaction’ Business Component.
2 Add a new user property to the 'LOY Engine Transaction' Business Component with the following
values:
Instructions for FR 12-1PLGIXW

1 Within Siebel Tools, navigate to the LS Activity Plan Business Component.
2 Within the LS Activity Plan Business Component, add a new field with the following values:
■ Name: Template Type Code
■ Join: Parent Template

■ Column: TYPE_CD
■ Force Active: TRUE
■ Type: DTYPE_TEXT

■ Text Length: 30
■ Use Default Sensitivity: TRUE
Instructions for FR 12-1O0MOKX

1 Within Siebel Tools, navigate to the A. Applet: Pharma Calendar Account List Applet applet, and
change the applet user property as follows:
■ Name: "Calendar Drag Field1"
■ Value: "Id, Account Id"
2 Within the CUT Address for Account/Contact Business Component, add a new calculated field
with the following values:
■ Field Name: Full Address
■ Calculated Value: [Street Address] + IIf([Street Address] IS NULL,"", ", ") + [City] +
IIf([City] IS NULL,"", ", ") + [State] + IIf([State] IS NULL,"", " ") + [Postal Code] +
IIf([Postal Code] IS NULL,"", " ") + [Country]
Instructions for FR 12-1O0M4C7

1 Within Siebel Tools, navigate to the "Pharma Attendee Deleter" Business Component, and add a
new field with the following values:
■ Name = "Contact Id"
■ Column = "TARGET_PER_ID"
2 Navigate to the "Pharma Meeting Attendee List Applet" applet, and add a new applet user
property with the following values:
■ Name = "Check Duplicate Meeting Attendee"
■ Value = "Y"
3 Navigate to the "Pharma Meeting Speaker List Applet" applet, and add a new applet user property
with the following values:
■ Name = "Check Duplicate Meeting Speaker"
■ Value = "Y"
Instructions for the Microsoft Internet Explorer 7 Calendar Issue

NOTE: These instructions apply to the following FRs: 12-1Q6JY3R, 12-1LWIHTF, 12-1IW6MAL, 12-
1Q6JYIX, 12-1Q6JY2U, 12-1Q6JY0Z, 12-1PMFCAO, 12-1PMFC8A, and 12-1Q6KRQ.
1 Add the Siebel application URL to Trusted Sites.

2 Add res:// to Trusted Sites.
3 Set the Trusted Sites security level to the Default level (Medium), disable Popup Blocker, and
select Enable Download Signed ActiveX controls within the Custom Security setting.
Instructions for FR 12-1PLXVS2

To implement this fix, import the PSP Driver workflow, which is packaged with the Siebel 7.8.2.11
Fix Pack build.
Instructions for FR 12-1QY0Y1B

1 Within Siebel Tools, navigate to the Order Item XA (No Link) Business Component.
2 Add the following set of fields to the
■ Previous Value (is a Calculated Field)
■ Previous Date Value (Column: PREV_DATE_VAL)
■ Previous Numeric Value (Column: PREV_NUM_VAL)
■ Previous Text Value (Column: PREV_CHAR_VAL)
All four fields have 'Force Active' as TRUE. Field 'Previous Value' has a PickList value of 'PickList XA
Dynamic LOV'.
Instructions for FR 12-1PF9N0N

1 Log into Siebel Tools, and navigate to the LOY Engine Transaction Business Component.
2 Add the following user property:
Instructions for FR 12-1O4OALH

The following procedure explains how to populate data from the Pharma Attendee Call Business
Component to the Action Employee Business Component. Because of special configuration in the
applet, Object Manager denormalization cannot be set up on the Pharma Attendee Call Business
Component.
Make the following changes within Siebel Tools:
1 In the Action Employee Business Component (Table: S_ACT_EMP), add the following three
denormalized column/fields and set Force Active = True:
■ ACT_CAL_TYPE_CD (Column: ACT_CAL_TYPE_CD)
■ ACT_EVT_STAT_CD (Column: ACT_EVT_STAT_CD)

■ ACT_TODO_PLNEND_DT (Column: ACT_TODO_PLNEND_DT)
2 In the Pharma Attendee Call Business Component, locate the following three source columns/
fields and set Force Active = True:
■ Call Status (Column: S_EVT_ACT.EVT_STAT_CD)
■ Display (Column: S_EVT_ACT.CAL_TYPE_CD)
■ Planned Completion (Column: S_EVT_ACT.TODO_PLAN_END_DT)
3 Add the Business Component user properties detailed in the following table:
Name Value
Denorm Fields 1 “Call Status”, “ACT_EVT_STAT_CD”
Denorm Fields 2 “Display”, “ACT_CAL_TYPE_CD”
Denorm Fields 3 “Planned Completion”,

“ACT_TODO_PLNEND_DT”
NOTE: There should be a blank space after the comma in the user property value.
The following field values will be populated from the Pharma Attendee Call Business Componnent
to the Action Employee Business Component:
❏ Pharma Attendee Call.Call Status > Action Employee.ACT_EVT_STAT_CD
❏ Pharma Attendee Call.Display > Action Employee.ACT_CAL_TYPE_CD
❏ Pharma Attendee Call.Planned Completion > Action Employee.ACT_TODO_PLNEND_DT
4 For the Pharma Account Call Business Component, set Table as S_EVT_ACT.
5 Create the following Business Component View Modes:
❏ Name: Personal
❏ Owner Type: Person

❏ Visibilility MVField: Owned By
❏ Visibility Multivalue Link: Employee (only if it does not already exist)
6 For the Pharma Account Call Business Component, set the Employee Destination Link Multivalue
Link to Pharma Account Call/Employee.
7 For the Pharma Account Call/Employee link, set Inter Table as S_ACT_EMP.
8 In the S_ACT_EMP table, make the following changes:
a Set the Activity_ID column’s Foreign Key Table value to S_EVT_ACT.
b Set the ACT_ALARM_FLG column’s Denormalization Path value to

[ACTIVITY_ID].[ALARM_FLAG].
Instructions for FR 12-1MSUS46

Make the following changes in Siebel Tools to implement this fix:

1 Within the S_SRC_PRD_BASLN table, create a new column called DELETE_FLG with the following
values:
Name User Name Physical Type Nullable Required Length Status
DELETE_FLG Delete Flag Character Y N 1 Active
2 Within the S_SRC_PRD_BASLN table, create a new index called S_SRC_PRD_BASLN_D1 with the
following values:
Name User Name Physical Type Length Status
S_SRC_PRD_BA Delete Flag Character 1 Active

SLN_D1
3 Within the CS CG Promoted Product Baseline Business Component, create the following new
field:
Name Column Type Length
Delete Flag DELETE_FLG DTYPE_TEXT 1
4 Create a new Business Component called CS CG Promoted Product Baseline - Atom with the
following values:
Name Table Class Project Search Spec
CS CG Promoted S_SRC_PRD_BA CSSBusComp CPG Promotion [Delete Flag] =

Product Baseline SLN Product 'Y'
- Atom
5 Within the CS CG Promoted Product Baseline - Atom Business Component, create a new field with
the following values:
Name Join Column Type Length
Delete Flag DELETE_FLG DTYPE_TEXT 1
6 Within the CPG Plan Business Object, add the CS GG Promoted Product Baseline - Atom Business
Component.
Instructions for FR 12-194OVBL

1 In Siebel Tools, under Siebel Objects/Applet, query for the Opportunity List applet.
2 Drill down on the Business Component field. (The value for the field will be Opportunity.)
3 Click the Multi Value Link object under Business Component.

4 Navigate to the Contact Address Multi Value Link.
5 Change the value of the Primary ID Field to Primary Contact Address Id.
6 Lock the project and compile.
7 Bounce the server.
Instructions for FR 12-13WVI6B

Add the parameter TrustClientHostName=True under Parameters Tab in Administration
Communications--> All Configurations
Instructions for FR 12-1G0NX8P

1 In Siebel Tools, query for the "Training Register Course Enroll Others Applet" applet
2 Change the "Read Only" property of the List Column "Contact First Name" to FALSE.
3 From Business Components, query for the "Training Admin Contact" Business Component.
4 Change the following fields as detailed below:
Field Name:-Contact Id
Join:-S_CONTACT
Column:-ROW_ID
Pre Default Value:-Field: 'Id'
Required:-FALSE
Field Name:-Employee Flag
Join:-S_CONTACT
Column:-EMP_FLG
Pre Default Value:-N
Required:-FALSE

5 Create new fields with the following values:
Field Name:-Party Type Code
Join:-
Column:-PARTY_TYPE_CD
Pre Default Value:-Person
Required:-TRUE
Field Name:-Party Uid
Join:-
Column:-PARTY_UID
Required:-TRUE
Field Name:-Person Uid
Join:-S_CONTACT
Column:-PERSON_UID
Required:-TRUE
Instructions for FR 12-1GN3HZQ

1 In Siebel Tools, query for "Service Request List Applet".
2 Select Applet Toggle from the Object Explorer and insert a new record into "Service Request List
Applet" with the sequence value set to 2 in the Properties window of Applet Toggle.
Instructions for FR 12-17GMY3G

■ Add a record in User Property of Persistent Customer Dashboard Business Service (BS) with the
following data:
■ Name: Support Dual Personalization
■ Value: TRUE
TRUE is the default value. If you do not want Dual Personalization, set the Value to FALSE.

Instructions for FR 12-13OVAJ5

The IFB parameter "USE MLOV LIC = TRUE" must be used when processing Hierarchical Multilingual
LOVs. The EIM table needs to be populated with the LIC for Multilingual LOVs when using this
parameter. The EIM table should still be populated with the Display Value for standard (non-MLOV)
LOVs.
Instructions for FR 12-19KT1JR

■ Add the applet user property "Confirm Payment Dialog" to the HH CG Payment Entry Applet CE,
and set the value to "Y"
Instructions for FR 12-1GNNHF6

1 Launch Siebel Tools, and select "Business Component" in Object Explorer.
2 Query for "CPG Plan Account Promotion", lock the project, and select "Business Component User
Prop".
3 Create a new Business Component User Property with the following values:
Name: CG Category Product Search Spec
Value: [Version Status] <> LookupValue("IMPL_PHASE", "Inactive")
Note: If this BC User Property is defined, its value is read by "Products" button code and the
search specification is applied on the "Internal Product" Business Component when the category
products are retrieved for creating Promoted Products.
4 Compile the SRF.
Instructions for FR 12-1I0ZP44

Use the following procedure to implement this fix (SIA customers only):
1 Log into Siebel Tools, and navigate to the "ISS VOD Import Export" project.
2 Change the Business Component for the picklist 'Product Vendor PickList' to 'Com Organization'.
Instructions for FR 12-1FIIG7F

1 Create three user properties for the "ISS Class VOD BusComp (JWS)" Business Component as
follows:
SubscriberBrokerName1 = CfgObjBroker
VODReleaseBuscomp12 = ISS Release UI Option Responsibility BusComp
VODReleaseBuscomp13 = ISS Release Decor Prop Admin BusComp

2 After you have created these three user properties, compile the SRF.
Instructions for FR 12-1CYDBZQ

1 From \\siebel\ses\siebsrvr\WEBTEMPL, modify eCfgTopLevelButtonsJS.swt to add the following

two buttons after FinishIt:
<td nowrap>
<swe:control id="swe:Restart" CfgUIControl="Restart" CfgHtmlType="MiniButton"

InvokeMethod="RestartInstance"/>
</td>
<td nowrap>
<swe:control id="swe:SaveCXProd" CfgUIControl="SaveCXProd" CfgHtmlType="MiniButton"

InvokeMethod="SaveCXProd"/>
</td>
2 Within Siebel Tools, locate the From Tools "Cfg Cx Runtime Instance Frame (JS HI)" applet, and
"Restart" and "SaveCXProd" buttons with method 'SubmitRequest' and fill out the display name.
3 Within Siebel Tools, navigate to Business Service and query for Cfg Web UI Service (JS).
4 From Business Service User Properties, create a new record called “Test Restart” and set the
value to Y.
5 Compile and bounce the server.
6 From the UI, navigate to Administration – Order Management and add 'RestartInstance" signal
in Context Service
The new 'Restart' button will triger 'RestartInstance' signal.
7 Release the RestartInstance Signal.
8 Navigate to Order Management Admin > Signals. Use LoadInstance as reference. All of the values
are the same as in LoadInstance except that the method name is "RestartInstance". If you want
to pass a CxObj, you can can use workflow.
For example, for workflow, you can get CxObj from the file system in the first step and you can
pass this property set and call 'Remote Complex Object Instance Service' Business Service and
method 'RestartInstance'.
NOTE: The 'RestartInstance" button is displayed in all eConfigurator views except Product
Validation Mode. Clicking theRestart button will go back to the root product and default tab
(group).
Instructions for FR 12-18RHKGY

1 Navigate to Site Map > Administration - Order Management > Message Types.

2 Click on the New button to create a new message type.
3 Enter the following values into the fields:
■ Name: Promotion - Asset Description Message
■ Display Mode: Passive
■ Group: Promotion
■ Title: Promotion - Asset Description Message
■ Short Text: <[Product Name] installed on [Install Date]>
■ Full Text: <[Product Name] installed on [Install Date]>
4 Click the New button to create another new message type.
5 Enter the following values into the fields::
■ Name: Promotion - Multiple Commitment Broken Message
■ Display Mode: Active
■ Group: Promotion
■ Title: Promotion - Multiple Commitment Broken Message
■ Short Text: Commitment has been broken for the following promotions: [Message] Please
disconnect promotions individually to view the specific terms.
■ Full Text: Commitment has been broken for the following promotions: [Message] Please
disconnect promotions individually to view the specific terms.
6 Navigate to the Response third-level tab to define responses for this message.
7 Click the New button on the Response child list applet.
8 Enter the following values into the fields:
■ Sequence#: 1
■ Name: OK
■ Response Type: Respondent Interested
■ Log: N
■ Suppress Repetition: N
■ Business Service: ISS Promotion Management Service
■ Method: MsgResumeWorkflow
Instructions for FR 12-1DHBJI5

Use the following procedures to implement this fix:

To implement repository changes for FR 12-1DHBJI5

1 In Siebel Tools, query for the 'ISS Promotion Management Service' Business Service, and add the
following input arguments for the 'ApplyPromotion' Business Service method:
■ Name = Prod Prom Source Id
■ Data Type = String
■ Type = Input
■ Optional = TRUE
■ Storage Type = Property
2 Recompile the 'ISS Promotion Management Service' Business Service.
To implement workflow changes for FR 12-1DHBJI5

1 In Siebel Tools, navigate to the 'ISS Promotion Upgrade Process' Workflow Process, and add the
following input argument in the 'Apply New Promotion' Workflow Step:
■ Input Argument = Prod Prom Source Id
■ Sequence = 0
■ Type = Process Property
■ Property Name = Old Prod Promotion Instance Id
2 Activate the 'ISS Promotion Upgrade Process' Workflow Process.
3 Launch the Siebel application, navigate to Sitemap > Administration - Business Process >
Workflow Deployment, query for the 'ISS Promotion Upgrade Process' Workflow and click
'Activate'.
Instructions for FR 12-1CR1RCV

1 Launch Siebel Tools, and navigate to Business Service.

2 Query for Name = "Configurator Session Service".
3 Navigate to Business Service User Properties, and add a new user property with the following
values:
■ Name = "Product Alias For Required Attribute Message"
■ Value = "NewProductName"
NOTE: The value should be the UI property name that you use to save Product Name
translations.
Instructions for FR 12-1BVJT8V

To implement this fix, make the following repository changes:

1 In the Business Component 'ISS Objects Attributes Lang BusComp', add a field called
'Description' that is mapped to the column 'DESC_TEXT' and set Force active = TRUE.
2 In the Business Component 'ISS Objects Attributes Lang Clone BusComp', add a field called
'Description' that is mapped to the column DESC_TEXT and set Force active = TRUE.
3 In the applet 'ISS Objects Attributes Name Lang Popup List Applet', add a field called 'Description'
to List Column, and map the string reference 'SBL_DESCRIPTION-1004230718-21G' to Base and
Edit template.
4 In the Business Components 'Quote Item XA', Order Item XA and Asset Mgmt - Asset XA, make
the following changes:
a Add a calculated field called 'Attribute Description' and set Force Active = TRUE.
b Add a calculated field called 'Attribute Unit of Measure' and set Force Active = TRUE.
5 In applets 'Quote Item XA List Applet', 'Order Item XA List Applet' and 'Asset Mgmt - Asset XA
List Applet', make the following changes:
a Add a field called 'Attribute Description' and map string reference 'SBL_DESCRIPTION-
1004230718-21G' to it. Set the Read-Only property to True.
b Add a field called 'Attribute Unit of Measure' and map string reference 'SBL_UoM-1004233551-
7A7' to it. Set the Read-Only peroperty to True.
c Map the above fields to the Base and EditList template
d Remove the old existing fields/list columns 'Description' and 'Unit of Measure' from the Base and
Edit List Template
6 Recompile the preceding Business Components and applets.
Instructions for FR 12-16F6T78

Please set the Overwrite flag to “Y” in Siebel.ini file to ensure the new fixed .swt file is delivered by
the installer.
Instructions for FR 12-17GBH6W

■ In the Applet "Cfg Cx Runtime Instance Frame (JS HI)", create a new control:
■ Name = lblEditField
■ Caption - String Reference = SBL_EDIT-1004231338-2SY
■ HTML Type = Label
Instructions for FR 12-17GBHCY

The Cfg State Code field is missing for the following three integration components and needs to be
added.
Integration object/components to modify:

■ 7.7 Order Entry Integration Object -> MACD Order Item XA
■ 7.7 Quote Integration Object -> MACD Quote Item XA
■ 7.7 Service Agreement Integration Object -> MACD Agreement Item XA
Integration component fields to add:
■ Name=Cfg State Code
■ Data Type=DTYPE_TEXT
■ Length=30
■ Type=Data
■ External Name=Cfg State Code
■ External Data Type=DTYPE_TEXT
■ External Length=30
■ XML Style=Element
■ XML Tag=CfgStateCode
Instructions for FR 12-1G0OPG5

1 Launch Siebel Tools, and query for Order Entry – Orders Buscomp.
2 Click on the Multi Value link.
3 Select “Ship to Address”.
4 Change the Primary Id Field to “Ship To Address Id”.
5 Recompile the SRF.
Instructions for FR 12-Z9XD1Q

1 In Siebel Tools, select Siebel Objects->Applet to navigate to the Applet view.
2 Query for the applet with NAME equal to 'Order Entry - Line Item Form Applet (Sales)(Pricing)'.
3 Select Siebel Objects->Applet->Control to navigate to the Applets/Control view.
4 Query for the Control with NAME equal to 'Currency Code' in the applet 'Control'.
5 Uncheck the field 'Read Only'.
Instructions for FR 12-1EUDFRB


1 In Siebel Tools, create a Business Component called 'Price Config Item - Tranformation' based on
the :S_PRI_CFG_ITEM table. You can also copy the existing 'Price Config Item (No Link)'
Business Component and rename it to 'Price Config Item - Tranformation'.
2 Query in the 'Admin Price List' Business Object, and add the new Business Component to the
Business Object.
3 Click the link information to navigate to the link information screen.
4 Enter Link Name as 'Price List/PriceConfig Item - Tranformation', the Parent Business Component
as 'Price List', the Child Business Component as 'Price Config Item - Tranformation', and the
destination Field as 'Price List'.
5 Save your changes.
6 Go to the 'Price Config Item - Tranformation' Business Component, and add the following
Business Component User Properties:
List Price Field 1-Minimum Price
List Price Field 2-Maximum Price
7 Compile the new 'Price Config Item - Tranformation' Business Component, the 'Admin Price List'
Business Object and the 'Price List/PriceConfig Item - Tranformation' link to the repository.
Instructions for FR 12-1ETXRE1

1 Search for all templates that contain the "CfgFieldName:List Price" or "CfgFieldName="List
Price"" strings.
2 Replace "List Price" with "Original List Price".
3 Restart the server.
Instructions for FR 12-1GO7CLW

1 Navigate to Siebel Tools and lock the Product Selection UI project.
2 Navigate to Applet, query for "Attribute Search Applet" and click on Applet User Prop.
3 Add a new record in "Applet User Prop" Enable Search Result Applet Access Control and set the
value to Y.
4 Go to View and query for the Quote-Search Catalog view, select the Quote Catalog Attribute
Search Product List Applet from Visibility applet, and select Catalog from Visibility Applet Type.
5 Compile the SRF and replace on the environment on which QF is applied.
Instructions for FR 12-143AFJO

1 Expose the Applet “Query–Save” using Siebel Tools by adding the following record.

■ Applet: Contact List Applet
2 Create a new Applet Method Menu Item with the following values:
■ Command: Save Query (SWE)
■ Menu Text: Jer Save Query SWE
■ Position: 32
3 Expose a SWE menu item on the Contact List Applet menu by adding the following record:
■ Applet: Contact List Applet
■ Create a new Applet Method Menu Item with the following values:
■ Command: Refine Query (SWE)
■ Menu Text: Jer Refine Query
■ Position: 31
4 Test the “Save Query” Functionality after doing the above mentioned configuration with the
following repro steps.
5 Execute a query (i.e. Last Name = A*)
6 Save this query using "Query Save As"
7 Clear the current query by executing an empty query to return all records
8 Execute the saved query to make sure it works
9 Refine the query using "Refine Query" (i.e. First Name = A*)
10 Save the query using Query - Save (the newly exposed menu item)
11 Clear the current query by executing an empty query to return all records
12 Execute the saved query and it should now return the refined query results (i.e. Last Name = A*
and First Name = A*)
NOTE: 'Save Query' applet level menu item will show up only if the current PDQ you are in has
been created by you. Remember 'Save Query' will let you overwrite the existing PDQ created.
Instructions for FR 12-17SSMLQ

1 Log into Siebel Tools, and navigate to the Action Business Component.
2 In the Action Business Component, create a User Property called "Calendar One to Many Child
BC Names" with the value "FS Activity Symptom", as shown below:
■ Name: Calendar One to Many Child BC Names
■ Value: FS Activity Symptom
3 Create a User Property called "FS Activity Symptom.ActivityIdFieldName" with the value "Activity
Id", as shown below:
■ Name: FS Activity Symptom.ActivityIdFieldName

■ Value: Activity Id
4 Compile the .srf.
Instructions for FR 12-1GO7G5R

1 In Siebel Tools, query for the 'DNB Global Access' Business Component.
2 Under the Business Component, navigate to the Field option, add a field called "Reason Code"
and set Data Type= DTYPE_TEXT.
Data Objects Changes
■ New or Changed: Changed
■ Name: DNB Global Access
■ Type: Business Component
■ Class: CSSBCVGlobalAccess
■ Description : Field Reason Code needs to be added
3 Navigate to the applet option and query for the "DNB Global Access List Applet"
UI Objects Changes
■ New or Changed: Changed
■ Name: DNB Global Access List Applet
■ Type: Applet
■ Class: CSSSWEFrameDNBGlobalAccess
■ Description: Mapped Reason Code field to show up in the UI
4 Under Applet, go to the "Applet Web Templet" and select the name "Query".
5 In "Applet Web Templet Item", add a field "Reason Code" and also set the value for Control field
as "Reason Code".
6 In "Applet Web Templet", right-click on "Query" and select "Edit Web Layout".
7 Add a Label and TextBox for the reason code.
8 Compile the SRF.
Instructions for FR 12-1EEBBBF

For this FR both Siebserver and DB server timezones must be in sync.
Instructions for FR 12-16N200T

1 Navigate to Administration – PIM Server Integration --> PIM Server Integration configuration.

2 Select the Profile “Engine 2000 Connector”.
3 Enter the following parameters:
■ Section: Calendar
■ Parameter: Exchange Virtual Directory Map 1
■ Value: S1
■ Parameter: Exchange Server
■ Value: SMTDL380EXCH2 (the above value should be in CAPITAL letters)
■ Parameter: Virtual Directory 1
■ Value: SSSETEST<created virtual directory name>
Instructions for FR 12-1DB4CUP

Use the following procedure to enable the Report menu:
1 Make a backup copy of the dccframeviewbar.swt (located in the

SIEBEL_HOME\SIEBEL_SERVER\WEBTEMPL’ folder), add dccframeviewbar_nosearch.swt to the
WEBTEMPL folder, and rename it dccframeviewbar.swt.
2 Go to the Actuate7\rptviewadp\filesfolders, make a backup copy of the itempopupmenu.jsp and

mitemdropdownmenu.jsp files and copy them to the same folder with the files attached
(itempopupmenu.jsp, mitemdropdownmenu.jsp ).
3 Clear the Cache and restart the Web Server, Siebel Server and Actuate.
4 Open the eService application and verify that the Reports drop-down menu is visible.
Instructions for FR 12-1HZTGIU

After applying the fix, please modify the ROD to replace the escape sequence with the ampersand
(or Single Quote) before using the parameter.
The Start method of the top level report object in the ROD would be a good place for this, since it
needs to be done before the parameter is used.
For example, assume the parameter is "AccountName".
For Ampersand:
Do While StrComp (AccountName, StrSubst (AccountName, "ESPAMPERSANDESP", "&")) <> 0
AccountName = StrSubst (AccountName, "ESPAMPERSANDESP", "&")
Loop

For Single Quote:
Do While StrComp (AccountName, StrSubst (AccountName, "ESPSINGLEQUOTEESP", "'")) <> 0
AccountName = StrSubst (AccountName, "ESPSINGLEQUOTEESP", "'")
Loop
Instructions for FR 12-1F1BR4E

1 Under the [SWE] section of the apps configuration file (such as uagent.cfg for Call Center and
eservice.cfg for eService), set EnforceSSL=True.
2 Bounce the Siebel server.
3 Bring up the URL as either http://<VIP>/callcenter_enu/start.swe?SWECmd=Start or http://

<VIP>/callcenter_enu/ default.htm
4 Log in to the application.
Instructions for FR 12-XQRAPI

1 In Siebel Tools, navigate to the Pharma Professional Call - CE Business Component.
2 Query for BusComp user properties and set the values as follows:
■ "Validate Professional Profile"=N
■ "Validate License Number”=N
■ “Validate License Number Expiration”=N
■ “Validate License Number Status”=N

3 Log in to the Pharma application on the Handheld device as SPORTER \ MSSQL
4 Create a call for Mary Alexander and set the address field to blank.
5 Create a sample dropped.
6 Click the Sign button.
Instructions for FR 12-1GG1E3K

■ Add the following control user property to control "Signature Capture" in the "LS Pharma Call
Signature Form Applet" applet:
■ Name: AxProperty: PointsLimit
■ Value: 7000

Instructions for FR 12-17UGUMJ

Append the following additional join specification to "Operational # TM Account Geo Zone Hierarchy
Division Driven" > dynamic candidate > Informational Table dynamic candidate component as
follows:
"AND [Informational Table].ASGN_RULE_GRP_ID=#RuleGrpId#"
Instructions for FR 12-1EMGCMM

Set the Business Component User Properties as follows:
■ BC: HTIM MDF Program Checkbook - Period Ending

■ BC User Property: Period Ending Search Spec
Value : (([Forfeit Amount]) = 0) AND ([Expiration Date] <= Today()) AND ([Type] <>
LookupValue("MDF_TXN_TYPE_CD","Paid") AND [Type] <>
LookupValue("MDF_TXN_TYPE_CD","Forfeiture"))
■ BC: HTIM MDF Fund Snapshot
■ BC User Property: Period Ending Search Spec
Value : ([MDF Process Status]<>LookupValue("HTIM_MDF_SNAPSHOT_STATUS_CD",

"Processed") OR ([MDF Process Status] IS NULL))
Set the Business Component Calculated Values as follows:
■ BC : HTIM MDF Fund Snapshot
■ BC Calculated Field : MDF Ending Balance
Value : [MDF Beginning Balance] + [MDF Accrued] + [MDF Adjusted] + [MDF Reinstated] - [MDF
Forfeited] - [MDF Total Paid]
■ BC: HTIM MDF Fund Snapshot Admin

■ BC Calculated Field : MDF Ending Balance
Value : [MDF Beginning Balance] + [MDF Accrued] + [MDF Adjusted] + [MDF Reinstated] - [MDF
Forfeited] - [MDF Total Paid]
Instructions for FR 12-1H91USE

■ Within Siebel Tools, navigate to the PS Project Plan Integration List Applet, and edit the following
values:
■ Applet UserProp: BaseLineSave

■ Value: N

Instructions for FR 12-1DJZ3WN

■ Under the ODBC prompt, run the following script to set the Parameter value to 33:
INSERT INTO ORA21001.S_SYS_PREF (ROW_ID, CREATED_BY, LAST_UPD_BY, SYS_PREF_CD, VAL)

values ('Test','0-1','0-1','AllowPhoneNumberLeadingZero','33');
Instructions for FR 12-1F1CW7D

■ Within the 'Siebel ERM' application, add the following lines in Application_PreNavigate:
if(DestViewName == "Portal Page Home View")
TheApplication().GotoView("All Account List View");
Instructions for FR 12-1H734ZZ

1 Take the patch installer into the local machine.
2 Change the value of OverWriteConfig=Yes in:
■ Siebel_Enterprise_Server/enu/siebel.ini
■ Siebel_Enterprise_Server/siebel.ini
■ Siebel_Web_Server_Extension/enu/siebel.ini
■ Siebel_Web_Server_Extension/siebel.ini
3 Install the base and the patch.
4 Launch the application, and verify the Application Menu Items and the Applet Menu items.
Instructions for FR 12-18853WI

1 Uninstall the 7.8.2.2 Fix Pack, if you have applied it.
2 Navigate to the Siebel Installer executable directory.
3 Update <PRODUCT>\siebel.ini and <PRODUCT>\<language>\siebel.ini
From: OverwriteConfig=no
To: OverwriteConfig=yes
4 Run the Installer.
Instructions for FR 12-1GN5LUZ


1 Log into Siebel Tools, and navigate to the Order Entry - Line Items Business Component.
2 Add a Business Component User Property with the following values:
■ Name: Is Qty ReadOnly After Booked
■ Value: N
Instructions for FR 12-1GLQI2O

1 In Siebel Tools, navigate to the FS InvTxn Ledger Entry Business Component.
2 In the FS InvTxn Ledger Entry Business Component, add the following new fields:
■ Name : Last Updated By
■ Column : LAST_UPD_BY
■ Text Length : 15
■ Type : DTYPE_ID
3 Add the following new User Property:
■ Name : HasLastUpdbyfield
■ Value : Y
Instructions for FR 12-1JY20FX

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.
2 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 non-
enumerated domains of Integers and Numbers.
To enable Min/Max for Class/Product Attributes

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


1 Set ""ExternalScript"" to Y in the BatchValidate parameters list in the script.
2 Check the ""Need Execution"" check box in linked item configuration. (This will generally be
checked by default.)
Instructions for FR 12-1J5GH2B

NOTE: This is only for specific cases where the Eligibility Rule is based on Account.
1 Log into Siebel Tools.
2 Select Workflow, and query for the "Web Channel Check Eligibility & Pricing Driver Workflow"
workflow.
3 Right-click and select "Edit Workflow Process"
4 Click on the "Set Pricing Date" step, right-click and pick "Show Input Arguments”.
5 In the "Input Arguments" window, add the following two input arguments:
a Name = "On True 1_2", Type = "Literal" ,
Value = "{Row.Account Id} = IfNull({Row.Account Id}, {Context.Account Id})"
b Name = "On Default 2", Type = "Literal" ,
Value = "{Row.Account Id} = IfNull({Row.Account Id}, {Context.Account Id})"
6 Save the workflow and deploy it.
7 Log into the Siebel application.
8 Navigate to Administration – Business ProcessesàWorkflow Deployment. In the top applet, query

for "Web Channel Check Eligibility & Pricing Driver Workflow" and activate it.
Instructions for FR 12-1JWYV5T

To switch off delta messages (produced on initial load and on proceed action after conflict) set User
Property "ShowDeltaMessages"=N on "Configurator Service" in the SRF.
Instructions for FR 12-1JFSTSL

1 Log into Siebel Tools and query for the ISS Promotion Form Applet.
2 Using Object Explorer, navigate to the Applet Method Menu Items section.
3 Change the command used for the 'Clear Cache' menu text from 'ISS Promotion ClearCache' to
'RefreshProductCache'.
4 Save the record, and recompile the applet in your SRF file.

Instructions for FR 12-1JNVKOD

1 In Siebel Tools, query for the "Training Register Course Enroll Others Applet" applet.
2 Change the "Read Only" property of the List Column "Contact First Name" to FALSE.
3 From Business Components, query for "Training Admin Contact" Business Component, and
change the following fields as mentioned below:
■ Field Name:-Contact Id
■ Join:-S_CONTACT
■ Column:-ROW_ID
■ Pre Default Value:-Field: 'Id'
■ Required:-FALSE
■ Field Name:-Employee Flag
■ Join:-S_CONTACT
■ Column:-EMP_FLG
■ Pre Default Value:-N
■ Required:-FALSE
4 Create new fields as follows:
■ Field Name:-Party Type Code
■ Join:-
■ Column:-PARTY_TYPE_CD
■ Pre Default Value:-Person
■ Required:-TRUE
■ Field Name:-Party Uid
■ Join:-
■ Column:-PARTY_UID
■ Required:-TRUE
■ Field Name:-Person Uid
■ Join:-S_CONTACT
■ Column:-PERSON_UID

■ Required:-TRUE
Instructions for FR 12-1JQW3KS

1 Log in to the Siebel application.
2 Navigate to the Site Map, click the Web Browser Administration hyperlink, and then click the
Browsers hyperlink.
3 In the Browser list applet, create a new record with Name=IE 7.0.
4 Click on the Capabilities tab in the lower applet and create the same capabilities as those in IE
6.0.
5 Change the value of User-Agent to “Mozilla/4.0 (compatible; MSIE 7.”
6 In the Browser list applet, create a new record with Name=MSIE 7.0.
7 Click on the Capabilities tab in the lower applet and create the same capabilities as those in MSIE
6.0.
8 Change the value of User-Agent to “Mozilla/4.0 (compatible; MSIE 7.”
9 Change the value of Parent to “IE 7.0”.
10 Restart the Siebel Server to make the new settings take effect.
Instructions for FR 12-1JK4O41

To check the value of sign_capture_flg from the S_EVT_ACT table, access the Querty tool.
Instructions for FR 12-1JA49PT

The following parameters need to be set to disable generation of reports:
MQMD_S_In_Report = MQRO_NONE
MQMD_S_In_Expiry = 1000
FullMQMDControl = TRUE
Instructions for FR 12-1LQRU81

1 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.
2 Associate the "CS CG SVP Baseline View - All" view to the responsibility "CG XX Key Account
Manager".

Instructions for FR 12-1K8LKTC

1 Log into Siebel Tools, and navigate to the "Attribute Details Form Applet" applet
for Web Templates "Base" and "Edit".
2 Activate the "Maximum Value" and "Minimum Value" items.
3 Compile the srf so that the changes take effect.
Instructions for FR 12-1MB5LV6

1 Log into Siebel Tools, and navigate to the ISS Product Group Styles Business Component/Cfg
Responsiblilty, and check the No Delete and No Delete properties (example in File "Link ISS
Product Group Styles BusComp Vs Cfg Responsibility.sif").
2 In the ISS Product Group Styles BusComp/Responsibility, check the No Delete and No Inter
Delete properties (example in File "Link ISS Product Group Styles BusComp Vs
Responsibility.sif").
3 Modify the ISS Product Group Styles Business Component Multi Value Links to be No Copy
(example in File "ISS Product Group Styles BusComp.sif").
4 Disable the "Lang Extension Business Components" User Property in the ISS Release UI Option
Responsibility Business Component (example in File "ISS Release UI Option Responsibility
BusComp.sif").
5 Set the new "Orig Id Fields" User Property to "UI Option Id" and make all fields ForceActive in
the ISS Delete UI Option Responsiblity (example in File "ISS Delete UI Option Responsibity
BusComp.sif").
6 In the ISS Release Group Styles Business Component, create a new field called "Primary
Responsibility Id" based on PR_RESP_ID, make it copyable and make it force active (example in
File "ISS Release Group Styles BusComp.sif")
7 In the ISS Delete Group Styles Business Component, create a new field called "Primary
Responsibility Id" based on PR_RESP_ID, make it copyable, and make it force active (example
in File "ISS Delete Group Styles BusComp.sif").
Instructions for FR 12-1LNHUY4

1 In Siebel Tools, click on the View tab in Object explorer and querry for the view name in which
you want to disable the IE back button.
2 Click on the View User Prop tab in the Object explorer for the same view.
3 Create a new record with Name = DisableIEBackButton and Value = TRUE.
4 Compile your changes.

Instructions for FR 12-1KMUO1F

1 In Siebel Tools, navigate to the 'Audit Trail' project, and lock it.
2 Add a new class with the following values:
■ Name: CSSBCAuditTrail
■ Project: Audit Trail
■ Dll: SSCABCBC
■ Object Type: Business Component
■ Super Class: CSSBCBase
■ High Interactivity Enabled: 4
3 Copy the 'Audit Trail Item 2' Business Component to the 'Audit Trail Item 2 RO' and set NoDelete,
NoInsert, NoUpdate, and NoMerge to TRUE.
4 Change the class to be CSSBCAuditTrail.
5 Add 'Audit Trail Item 2 RO' Business Component to BusObj 'Audit Trail, and and leave the link
empty.
6 In the 'Audit Trail Item List Applet 2' applet, change the Business Component from 'Audit Trail
Item 2' to 'Audit Trail Item 2 RO', and change the class to 'CSSSWEFrameList' or 'CSSFrameList'
if it is not one of these two values.
Instructions for FR 12-1FTLT9K

1 Set the value "Auto Mgr Calendar Access” to ‘False’ in the Application- Administration > System
Preference screen.
2 Restart the servers and install Siebel Tools.
3 Set the ”Include Direct Reports In Owner Picklist” User Property to ‘N’ for the HI Activity Calendar
View.
Instructions for FR 12-1IL26GJ

1 If the target webserver to which EAI SSL data is being sent from Siebel application has a self
signed certificate installed, you must import this self signed server certificate into the mainwin
registry in Siebel Server.
2 For enabling NULL Cipher, in the mainwin registry, disable all other ciphers except the NULL
cipher.
Instructions for FR 12-1IGM0SI


1 Log into Siebel Tools, and expand the Business Component section.
2 Query for the 'HTIM MDF Fund Snapshot Business Component, and lock it.
3 Right-click and create a new multi-value field named 'New Used Amount 60-90 MVL'. The value
for the Multi-Value Link should be 'All Credit Txn' and the value for the field should be 'Used
Amount'.
4 Create another multi-value field named 'New Forfeiture Amount 60-90 MVL'. The value for the
Multi-Value Link should be 'All Credit Txn' and the value for the field should be 'Forfeit Amount'.
5 Save the modification and expand the Field section.
6 Query for the 'Calc New Available Balance 60-90' field.
7 Change the Calculated Value to IfNull (Sum ([New Available Balance 60-90 MVL]), 0.0) - IfNull
(Sum ([New Used Amount 60-90 MVL]), 0.0) - IfNull (Sum ([New Forfeiture Amount 60-90
MVL]), 0.0)'.
Instructions for FR 12-1J6K6W7

1 Log into Siebel Tools and expand the Business Component section.
2 Query for the 'HTIM MDF Fund Snapshot' Business Component, and lock it.
3 Right-click and create a new multi value field with the name ‘New Used Amount 60-90 MVL’. The
value for the Multi Value Link should be ‘All Credit Txn’ and the value for the field should be ‘Used
Amount’.
4 Create another multi value field called ‘New Forfeiture Amount 60-90 MVL’ with Value Link as ‘All
Credit Txn’ and Field as ‘Forfeit Amount’.
5 Save the modifications and expand the Field section.
6 Query for the ‘Calc New Available Balance 60-90 field.’

7 Change the Calculated Value to ‘IfNull (Sum ([New Available Balance 60-90 MVL]), 0.0) - IfNull
(Sum ([New Used Amount 60-90 MVL]), 0.0) - IfNull (Sum ([New Forfeiture Amount 60-90
MVL]), 0.0)’ from ‘IfNull (Sum ([New Available Balance 60-90 MVL]), 0.0)’
8 Save the modifications and unlock the Business Component.
Instructions for FR 12-1JOGRKT

1 Expose a new field on UI: Adjusted Balance
■ Applet: HTIM MDF Checkbook Credits List Applet

■ New:
■ List Column: Adjusted Balance
■ Field: Available Balance

2 HTIM MDF Program Account Items
User Properties (new):
■ Name: Credit Items Search Spec
■ Value: [Type]=LookupValue(""MDF_TXN_TYPE_CD"",""Accrual"") AND ([Amount] - [Used

Amount] > 0)
■ Name: Credit Items Sort Spec
■ Value: Created
■ BC Field (modified):
■ Name: Period
■ Properties:
■ Required: TRUE"
Instructions for FR 12-1KTTP9H

1 In Signal change - SetFieldValue, activate call to ISS Save CX Prod Service for mode Asset, and
change Fields to "Product Name".
2 In Asset Mgmt - Asset, disable the Business Component User Property On Field Update Invoke 2
| "Product Name", "Asset Mgmt - Asset", "SaveCxProd"
3 Change Applet User Property to Disable Buscomp Hierarchy and the value to TRUE for the Asset
Mgmt - Asset List Applet, Internal Asset Mgmt - Asset List Applet, and Asset Mgmt - Asset
Detail.Applet applets.
Instructions for FR 12-1LLTKSW

Note that Actuate Reports server should be installed and running before you begin.
1 Navigate to Agreements > Documents, make a note of the View name from "About View", and
copy the view name.
2 Navigate to Siebel Tools - Object Explorer > Views > PS Agreement Document View.
3 Within Siebel Tools, query for PS Agreement Document View and navigate to "View Report" (a
child of Views).
4 Add a new record called "Agreement Summary".
5 Compile the srf.
6 Create a blank document and save it on the desktop.
7 Navigate to Admin Document > Proposal Field Mappings and create a new Field Mapping named
"Agreement" with Service Agreement as the Business Object.

8 Add corresponding Business Components and Business Component fields as Account and
Agreement Number.
9 Navigate to Proposal Template and create a new record with the created Field Mapping and
Template.
10 Navigate to Sections and create a new section with the Section Type as Report, the Business
Object as Service Agreement, and the Report as Agreement Summary.
11 Give the Link Spec - Service Agreement,Id/Proposal,Agreement Id.

12 Navigate to Agreements > Documents, and create a new record by selecting the one you created
in Proposal Template and generate the Proposal.
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.
Platforms:
AIX, HPUX, Solaris, Windows

MR Guide 782 Rev X

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MR Guide 782 Rev X

Uploaded by

Copyright:

Available Formats

Siebel Maintenance

Siebel Maintenance Release Guide 1

Chapter 1: Siebel Maintenance Release Guide, Version

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 1

Instructions for ACR 346A 178

2 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X

Securing User Access to the Oracle BI Publisher Server 242

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 3

4 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X

User Interface 339

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 5

Travel & Transportation 449

6 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X

This guide includes the following topics:

■ What’s New in This Revision

■ Quick Fixes Included in 7.8.2.x Fix Packs

■ Enhancements and Updates in 7.8.2.x Fix Packs

■ Configuration Instructions for Enhancements and Updates

■ Installation Instructions for 7.8.2.x Fix Packs

■ Resolved Change Requests

Release Notes for the Siebel 7.8.2.14 Fix

Siebel CTI Connect Is No Longer Supported

7.8.2.14 Quick Fixes for Actuate and BI Publisher Functionality

LMU Files and Seed Data Missing

Subarea: Reports Server

Product Version: Siebel 7.8.2.14

Change Request: 12-1VR1SM1

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 7

Use the following workaround to address this issue:

4 Compile and deploy the language SRF.

What’s New in This Revision

Instructions for Oracle BI Publisher Updated this section.

Configuration Instructions for

Resolved Change Requests

How to Use This Book

8 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X

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

Terminology Used in This Guide

■ Performing new full installation of version 7.8.2, with version 7.8.2.x

■ Installing version 7.8.2.x (patching existing 7.8.2 or prior 7.8.2.x installation)

■ Installing languages (language packs) provided with version 7.8.2

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 9

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

Quick Fixes Included in 7.8.2.x Fix Packs

Table 2. Quick Fixes Included in Version 7.8.2.x

Change Fix Request Quick Fix Merged Into

12-108H728 12-1LKB0FH 7.8.2.3 [19221] QF03D4 7.8.2.13

12-16DUIYU 12-1NVVYTH 7.8.2.3 [19221] QF03D9 7.8.2.13

12-1QMWX5R 12-1QNWL5X 7.8.2.3 [19221] QF03F5 7.8.2.13

12-1PCDHDP 12-1PZ4T2P 7.8.2.3 [19221] QF03F6 7.8.2.13

10 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X

Table 2. Quick Fixes Included in Version 7.8.2.x

Change Fix Request Quick Fix Merged Into

12-1MKB7V9 12-1N6TYJD 7.8.2.3 [19221] QFJ322 7.8.2.13

12-1PILEIJ 12-1RRTL54 7.8.2.3 [19221] QFJ322 7.8.2.13

12-1S85TE5 12-1S85TFG 7.8.2.3 [19221] QFJ323 7.8.2.13

12-1NNU3JH 12-1SUAJS5 7.8.2.3 [19221] QFJ324 7.8.2.13

12-1THNL1J 12-1THNL33 7.8.2.3 [19221] QFJ325 7.8.2.13

12-1TG5VA9 12-1TGO8BK 7.8.2.3 [19221] QFJ326 7.8.2.13

12-1KWV58T 12-1P2RHT5 7.8.2.4 [19224] QF0461 7.8.2.13

12-1Q3L025 12-1SOZ68J 7.8.2.4 [19224] QF0469 7.8.2.13

12-1RSS5YD 12-1RVO2VP 7.8.2.5 [19227] QF05A7 7.8.2.13