You are on page 1of 496

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.13 44
Enhancements and Updates in Version 7.8.2.12 45
Enhancements and Updates in Version 7.8.2.11 46
Enhancements and Updates in Version 7.8.2.10 48
Enhancements and Updates in Version 7.8.2.9 49
Enhancements and Updates in Version 7.8.2.8 50
Enhancements and Updates in Version 7.8.2.7 51
Enhancements and Updates in Version 7.8.2.6 51
Enhancements and Updates in Version 7.8.2.5 52
Enhancements and Updates in Version 7.8.2.4 53
Enhancements and Updates in Version 7.8.2.3 54
Enhancements and Updates in Version 7.8.2.2 55
Enhancements and Updates in Version 7.8.2.1 56
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
Instructions for ACR 272 117
Instructions for ACR 296 120
Instructions for ACR 308 124
Instructions for ACR 323 158
Instructions for ACR 327 165
Instructions for ACR 331 171

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 1


Contents

Instructions for ACR 346A 178


Instructions for ACR 347 182
Instructions for ACR 372 182
Instructions for ACR 373B 194
Instructions for ACR 382 197
Instructions for ACR 389 197
Instructions for ACR 391 198
Instructions for ACR 409 198
Instructions for ACR 415 198
Instructions for ACR 427 205
Instructions for ACR 428 208
Instructions for ACR 432 219
Instructions for ACR 460 219
Instructions for ACR 471 219
Instructions for ACR 481 220
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
Resolved Change Requests in the Siebel 7.8.2.13 Fix Pack 294
Call Center 294
Comm Media Energy 294
Connectors/EAI 295
Customer Order Management 296
General 297

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 3


Contents

Loyalty 302
Marketing 303
Mobile Solutions 303
Sales 303
Service 304
Siebel eMail Response 304
Universal Customer Master 305
User Interface 305
Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack 307
Call Center 307
Comm Media Energy 308
Connectors / EAI 308
Consumer Sector 309
Customer Order Management 309
Data Quality 311
Financial Services 311
General 311
iHelp 316
Life Sciences 316
Mobile Solutions 317
Public Sector 319
Sales 319
Service 324
Siebel eMail Response 324
User Interface 325
Resolved Change Requests in the Siebel 7.8.2.11 Fix Pack 326
Analytics 326
Call Center 326
Web Service 326
Comm Media Energy 327
Connectors / EAI 329
Consumer Sector 329
Customer Order Management 330
General 331
Life Sciences 335
Loyalty 336
Marketing 337
Mobile Solutions 337
Sales 338
Service 338
Siebel eMail Response 339
Universal Customer Master 339

4 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Contents

User Interface 339


Resolved Change Requests in the Siebel 7.8.2.10 Fix Pack 342
Call Center 342
Web Services 342
Comm Media Energy 343
Connectors / EAI 343
Consumer Sector 344
Customer Order Management 344
Financial Services 346
General 347
iHelp 351
Life Sciences 352
Loyalty 352
Marketing 352
Mobile Solutions 353
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
Comm Media Energy 363
Connectors/ EAI 365
Consumer Sector 366
Customer Order Management 369
Data Quality 392
Employee Relationship Management 392
Enterprise Integration Manager/EIM 393
Financial Services 394
General 395
iHelp 427
Life Sciences 427
Loyalty 434
Marketing 435
Mobile Solutions 437
Partner Relationship Management 441
Professional Services 442
Sales 443
Service 445
Siebel eMail Response 448

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 5


Contents

Travel & Transportation 449


UAN General Anomalies 449
Universal Customer Master 449
Universal Customer Master 450
User Interface 450
Web Service 460

6 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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 ■ 7


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.

8 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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 ■ 9


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

10 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 11


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

12 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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]

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 13


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

14 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 15


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

16 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 17


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

18 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 19


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

20 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 21


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

22 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 23


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

24 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 25


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

26 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 27


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

28 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 29


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

30 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 31


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

32 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 33


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

34 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 35


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

36 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 37


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

38 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 39


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

40 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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]

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 41


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ 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


Request ID ID Fix Pack Base Version Fix Pack

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

42 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Enhancements and Updates
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


Request ID ID Fix Pack Base Version Fix Pack
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.13

■ Enhancements and Updates in Version 7.8.2.12

■ Enhancements and Updates in Version 7.8.2.11

■ Enhancements and Updates in Version 7.8.2.10

■ Enhancements and Updates in Version 7.8.2.9

■ Enhancements and Updates in Version 7.8.2.8

■ Enhancements and Updates in Version 7.8.2.7

■ Enhancements and Updates in Version 7.8.2.6

■ Enhancements and Updates in Version 7.8.2.5

■ Enhancements and Updates in Version 7.8.2.4

■ Enhancements and Updates in Version 7.8.2.3

■ Enhancements and Updates in Version 7.8.2.2

■ Enhancements and Updates in Version 7.8.2.1

■ Enhancements and Updates in Version 7.8.2

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 43


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

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.

Enhancements and Updates in Version 7.8.2.13


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.

44 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Table 3. Enhancements and Updates in Version 7.8.2.13

Feature Enhancement
or Certification # Feature Enhancement or Certification Description

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.

Enhancements and Updates in Version 7.8.2.12


Table 4 contains the enhancements and updates contained in version 7.8.2.12.

Table 4. Enhancements and Updates in Version 7.8.2.12

Feature Enhancement
or Certification # Feature Enhancement or Certification Description

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 45


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

Table 4. Enhancements and Updates in Version 7.8.2.12

Feature Enhancement
or Certification # Feature Enhancement or Certification Description

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,


contacts, opportunities, and products between Oracle CRM On
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.

Enhancements and Updates in Version 7.8.2.11


Table 5 contains the enhancements and updates contained in version 7.8.2.11.

Table 5. Enhancements and Updates in Version 7.8.2.11

Feature Enhancement
or Certification # Feature Enhancement or Certification Description

ACR 389 NOTE: This enhancement applies for Siebel 7.8.2.x SEA only.

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).

ACR 391 Resolves a problem where having the EXISTS operator in the
searchspec field of the UI Data Web Service causes an error.

46 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Table 5. Enhancements and Updates in Version 7.8.2.11

Feature Enhancement
or Certification # Feature Enhancement or Certification Description

ACR 427 Allows the Turkish i-dot character to be handled correctly in data
queries.

ACR 428 ACR 428 provides the following enhancements:

■ New billing management views

■ Multiple Account Billing Profiles

■ Multiple balance groups, balances, and details

■ Real-time display of unbilled usage and invoices

■ New Web Services for products, accounts, contacts, and billing


profiles

■ Enhanced Customer Order Management to support one-time


charges, promotions, customizable product pricing, and asset-
based ordering enhancements

■ Nested Service bundle

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 47


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

Enhancements and Updates in Version 7.8.2.10


Table 6 contains the enhancements and updates contained in version 7.8.2.10.

Table 6. Enhancements and Updates in Version 7.8.2.10

Feature Enhancement
or Certification # Feature Enhancement or Certification Description

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.

ACR 415 ACR 415 provides the following enhancements:

■ 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.

48 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Enhancements and Updates in Version 7.8.2.9


Table 7 contains the enhancements and updates contained in version 7.8.2.9.

Table 7. Enhancements and Updates in Version 7.8.2.9

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 49


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

Enhancements and Updates in Version 7.8.2.8


Table 8 lists the enhancements and updates contained in version 7.8.2.8.

Table 8. Enhancements and Updates in Version 7.8.2.8

Feature Enhancement or
Certification # Feature Enhancement or Certification Description

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)

■ 30-Day (Type of Report)

■ STN#

■ PMA/510(k)

■ One new field on the “LS Medical PI Product” Business


Component:

■ Common Device Name

■ New fields on the “LS Medical Product Issue RR” Business


Component:

■ Common Device Name

■ 7-Day (Type of Report)


■ 30-Day (Type of Report)
■ 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.

50 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Enhancements and Updates in Version 7.8.2.7


Table 9 lists the enhancements and updates contained in version 7.8.2.7.

Table 9. Enhancements and Updates in Version 7.8.2.7

Feature Enhancement or Certification Description


Feature Enhancement or
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.

Enhancements and Updates in Version 7.8.2.6


Table 10 lists the enhancements and updates contained in version 7.8.2.6

Table 10. Enhancements and Updates in Version 7.8.2.6

Feature Enhancement or
Certification # Feature Enhancement or Certification Description

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 51


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

Enhancements and Updates in Version 7.8.2.5


Table 11 lists the enhancements and updates contained in version 7.8.2.5.

Table 11. Enhancements and Updates in Version 7.8.2.5

Feature Enhancement
or Certification # Feature Enhancement or Certification Description

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.

52 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Enhancements and Updates in Version 7.8.2.4


Table 12 lists the enhancements and updates contained in version 7.8.2.4.

Table 12. Enhancements and Updates in Version 7.8.2.4

Feature Enhancement or
Certification # Feature Enhancement or Certification Description

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 53


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

Enhancements and Updates in Version 7.8.2.3


Table 13 lists the enhancements and updates contained in version 7.8.2.3.

Table 13. Enhancements and Updates in Version 7.8.2.3

Feature Enhancement or
Certification # Feature Enhancement or Certification Description

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.

54 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Table 13. Enhancements and Updates in Version 7.8.2.3

Feature Enhancement or
Certification # Feature Enhancement or Certification Description
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

Enhancements and Updates in Version 7.8.2.2


Table 14 lists the enhancements and updates contained in version 7.8.2.2.

Table 14. Enhancements and Updates in Version 7.8.2.2

Feature Enhancement or
Certification # Feature Enhancement or Certification Description

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 55


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

Table 14. Enhancements and Updates in Version 7.8.2.2

Feature Enhancement or
Certification # Feature Enhancement or Certification Description
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()

Enhancements and Updates in Version 7.8.2.1


Table 15 lists the enhancements and updates contained in version 7.8.2.1.

Table 15. Enhancements and Updates in Version 7.8.2.1

Feature Enhancement or
Certification # Feature Enhancement or Certification Description

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.

56 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Table 15. Enhancements and Updates in Version 7.8.2.1

Feature Enhancement or
Certification # Feature Enhancement or Certification Description

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

ACR 245 ACR 245 provides the following enhancements:

■ 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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 57


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

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.

58 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Table 16. Enhancements and Updates in Version 7.8.2

Feature Description For More Information

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 59


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

Table 16. Enhancements and Updates in Version 7.8.2

Feature Description For More Information

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.

60 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Table 16. Enhancements and Updates in Version 7.8.2

Feature Description For More Information


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 272

■ Instructions for ACR 296

■ Instructions for ACR 308

■ Instructions for ACR 323

■ Instructions for ACR 327

■ Instructions for ACR 331

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 61


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

■ Instructions for ACR 346A

■ Instructions for ACR 347

■ Instructions for ACR 372

■ Instructions for ACR 373B

■ Instructions for ACR 382

■ Instructions for ACR 389

■ Instructions for ACR 391

■ Instructions for ACR 409

■ Instructions for ACR 415

■ Instructions for ACR 428

■ Instructions for ACR 460

■ Instructions for ACR 471

■ Instructions for ACR 481

■ 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.

62 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 63


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

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.

64 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

■ 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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 65


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

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.>

66 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

<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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 67


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

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".

68 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 69


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

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


1 In Siebel Tools, navigate to Object Explorer.

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.

70 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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
1 In Siebel Tools, navigate to Object Explorer.

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


1 In Siebel Tools, navigate to Object Explorer.

2 Click on Symbolic Strings, and add the new Symbolic Strings specified in the Symbolic Strings
worksheet within Repository Changes.xls.

Applet Setup
1 In Siebel Tools, navigate to Object Explorer.

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 71


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

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
Attributes listed in the Program Level Attributes worksheet within High Miles Changes.xls.

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.

72 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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


1 Within Siebel Loyalty, navigate to Loyalty Program Administration, and query for the High Miles
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.

6 Click the Activate button to activate the promotion.

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 73


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

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

74 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

■ 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
Name Field Applet String Reference

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

■ Class: CSSSWEFrameList

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 75


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

■ 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
Name Field Applet String Reference

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 Geo Zone Mapping List Applet

■ Class: CSSSWEFrameList

■ Business Component: Alignment Territory Geo Zone 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
Name Field Applet String Reference

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 Postal Code Mapping List Applet

■ Class: CSSSWEFrameList

76 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

■ Business Component: Alignment Territory Postal Code 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
Name Field Applet String Reference

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

■ 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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 77


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

■ Class: CSSBCAlignment

78 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

■ 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] =
LookupValue("ALIGNMENT_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")

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 79


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

Fields

Name Calculated Value Calculated? New?


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

Is Read Only 2 IIF([Status] = Y N


LookupValue("ALIGNMENT_STATUS",
"Alignment Run Failed") OR [Status] =
LookupValue("ALIGNMENT_STATUS", "Run
Tasks Not Started") OR [Status] =
LookupValue("ALIGNMENT_STATUS", "Run
Tasks Failed"), "N", "Y")

Is Read Only 3 IIF([Status] = Y Y


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

80 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 81


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

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

82 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

■ 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")

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 83


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

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

84 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

■ Table: S_TERRALGN_ACCT

Update the existing Business Component with the following changes:

Fields

Name Column Join Pick List Calculated Value

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
Name Field Field Constrain

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 85


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

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


■ Class: CSSBCAlgnComponent

86 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

■ Table: S_TERRALGN_CON

Fields

Name Column Join Pick List Calculated Value

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
Name Field Field Constrain

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


Territory Id

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 87


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

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

■ Class: CSSBCAlgnComponent

88 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

■ Table: S_TERRALGN_REGN

Fields

Name Column Join Pick List Calculated Value

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
Name Field Field Constrain

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


Territory Id

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 89


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

User Properties

New or
Changed? Name Value

New Field Read Only Field: From Disable From Territory Field
Territory Identifier

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


Identifier", ""

■ Alignment Territory Postal Code Mapping

■ Class: CSSBCAlgnComponent

■ 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
Name Field Field Constrain

Territory Identifier Territory Division


Division Id Id

From Territory From Territory Id


Identifier Id

From Territory Territory


Identifier Identifier

90 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Fields Pick Map

Picklist
Name Field Field Constrain
From Territory Display
Name Name
Territory Division Y
Division Id Id

Join Join Specification

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
Territory Identifier

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


Identifier", ""

■ Alignment Territory Position Mapping

■ Class: CSSBCAlgnComponent

■ 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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 91


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

■ Table: S_PARTY

Modify the Join Specification for the S_TERR_REGION join, as shown in the following table:

Join Join Specification

Destination Source
Alias Table Outer Name Column Field

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

Join Join Specification

Destination Source
Alias Table Outer Name Column Field

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

Table: S_TERRALGN_PSTN

92 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Alignment Activation Date ACTIVATION_DT S_TERRALGN

Rule Effective End Date EFF_END_DT S_TERR_ASSET

Rule Effective Start Date EFF_START_DT S_TERR_ASSET

Territory Alignment Id TERR_ALGN_ID

Territory Id TERR_ID

Join Join Specification

Destination Source
Alias Table Outer Name Column Field

S_TERRAL S_TERRALGN N S_TERRALGN ROW_ID Territory


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

Table: S_TERRALGN_PSTN

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

Alignment Activation Date ACTIVATION_DT S_TERRALGN

Rule Effective End Date EFF_END_DT S_TERR_CON

Rule Effective Start Date EFF_START_DT S_TERR_CON

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 93


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

Fields

Name Column Join


Territory Alignment Id TERR_ALGN_ID

Territory Id TERR_ID

Join Join Specification

Destination Source
Alias Table Outer Name Column Field

S_TERRAL S_TERRALGN N S_TERRALGN ROW_ID Territory


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

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

Account Flag ACTIVATION_DT S_TERR_REGION

Alignment Activation Date ACTIVATION_DT S_TERRALGN

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

Territory Alignment Id TERR_ALGN_ID

Territory Id TERR_ID

94 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Join Join Specification

Destination Source
Alias Table Outer Name Column Field

S_TERRAL S_TERRALGN N S_TERRALGN ROW_ID Territory


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

Table: S_TERRALGN_PSTN

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

Account Flag ACTIVATION_DT S_TERR_ZIP

Alignment Activation Date ACTIVATION_DT S_TERRALGN

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

Territory Alignment Id TERR_ALGN_ID

Territory Id TERR_ID

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 95


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

Join Join Specification

Destination Source
Alias Table Outer Name Column Field

S_TERRAL S_TERRALGN N S_TERRALGN ROW_ID Territory


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

96 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 97


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

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
N Alignment Join Path BC:TM IndirectPos:TOS
Account 6 Target Alignment-
Position-Territory-
Geo Zone-Account

N Alignment Join Path BC:TM DirectPos:TOS Target


Asset 3 Alignment-Position-
Territory-Asset

N Alignment Join Path BC:TM IndirectPos:TOS


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

N Alignment Join Path BC:TM DirectPos:TOS Target


Contact 4 Alignment-Position-
Territory-Contact

N Alignment Join Path BC:TM IndirectPos:TOS


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

N Alignment Join Path BC:TM IndirectPos:TOS


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


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

Y Minor Operational Join Path Indirect:TOS Target


BC:TM Account 3 Alignment-Territory-
Geo Zone-Account

98 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

User Properties

New? Name Value


Y Minor Operational Join Path Direct:TOS Target
BC:TM Asset 1 Alignment-Territory-
Asset

Y Minor Operational Join Path Indirect:TOS Target


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

Y Minor Operational Join Path Direct:TOS Target


BC:TM Contact 1 Alignment-Territory-
Contact

Y Minor Operational Join Path Indirect:TOS Target


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

Y Minor Operational Join Path Indirect:TOS Target


BC:TM Contact 3 Alignment-Territory-
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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 99


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

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

Physical Foreign Key


Name Type Length Nullable Table Required?

FROM_TERR_ID Varchar 15 Y S_TERRITORY N

Table: S_TERR_REGION

Columns
Physical Foreign Key
Name Type Length Nullable Table Required?

FROM_TERR_ID Varchar 15 Y S_TERRITORY N

Table: S_TERR_ZIP

Columns

Physical Foreign Key


Name Type Length Nullable Table Required?

FROM_TERR_ID Varchar 15 Y S_TERRITORY N

100 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Table: S_TERRALGN_ACCT

Columns

Physical Foreign Key


Name Type Length Nullable Table Required?

FROM_TERR_ID Varchar 15 Y S_TERRITORY N

Table: S_TERRALGN_CON

Columns

Physical Foreign Key


Name Type Length Nullable Table Required?

FROM_TERR_ID Varchar 15 Y S_TERRITORY N

Table: S_TERRALGN_REGN

Columns

Physical Foreign Key


Name Type Length Nullable Table Required?

FROM_TERR_ID Varchar 15 Y S_TERRITORY N

Table: S_TERRALGN_ZIP

Columns

Physical Foreign Key


Name Type Length Nullable Table Required?

FROM_TERR_ID Varchar 15 Y S_TERRITORY N

Workflows
Alignment - Activation Process

Step

Name New

Moving Mappings N

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 10 1


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

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

102 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Step
Number Name Type New

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 10 3


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

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")

6 Status Expressio LookupValue("ALIGNMENT_


n STATUS", "Run Completed")

7 Status Expressio LookupValue("ALIGNMENT_


n STATUS", "Run Tasks
Failed")

8 Status Expressio LookupValue("ALIGNMENT_


n STATUS", "Run Tasks Not
Started")

11 Status Expressio LookupValue("ALIGNMENT_


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

11 Locked Date Literal

11 Locked Flag Literal N

10 Locked By Literal

10 Locked Date Literal

10 Locked Flag Literal N

104 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Output
Arguments

Property
Step Number Name Type Output Argument

1 AMB Task Ids Process AMB Task Ids


Property

2 AMB Task Ids Process AMB Task Ids


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'))

4 DEFAULT:DEC Default
ISION1

4 Y:DECISION1 Condition (Has Tasks Started This Must Match (Ignore


Case)('N'))

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 10 5


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

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
Number Name Type New

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

6 Update Alignment Siebel Y


Status to Active Operation

7 Update Alignment Siebel Y


Status to Tasks Operation
Failed

8 Update Alignment Siebel Y


Status to Operation
Assignment Failed

9 Data Cleanup Business Y


Service

10 Unlock Alignment Siebel Y


Operation

106 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Step
Number Name Type New

11 Update Alignment Siebel Y


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
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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 10 7


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

Input Arguments

Step
Number Input Type Value Property Name

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")

6 Status Expressio LookupValue("ALIGNMENT_


n STATUS", "Active")

7 Status Expressio LookupValue("ALIGNMENT_


n STATUS", "Activation Tasks
Failed")

8 Status Expressio LookupValue("ALIGNMENT_


n STATUS", "Activation Tasks
Not Started")

11 Status Expressio LookupValue("ALIGNMENT_


n STATUS", "Activation Tasks
Unknown")

11 Locked By Literal

11 Locked Date Literal

11 Locked Flag Literal N

10 Locked By Literal
10 Locked Date Literal

10 Locked Flag Literal N

Output Arguments

Property
Step Number Name Type Output Argument

1 AMB Task Ids Process AMB Task Ids


Property

2 AMB Task Ids Process AMB Task Ids


Property

108 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Output Arguments

Property
Step Number Name Type Output Argument

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'))

4 DEFAULT:DEC Default
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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 10 9


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

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

New Copy Position Specific Data SQL 2 TM_COPY_POSTION_DATA_TERR_


ZIP_ACCNT

New Copy Position Specific Data SQL 3 TM_COPY_POSTION_DATA_TERR_


GEO_ZONE_ACCNT

New Territory Position Specific Columns ROLE_CD

110 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

New Copy Position Specific Data SQL 2 TM_COPY_POSTION_DATA_TERR


_ZIP_CON
New Copy Position Specific Data SQL 3 TM_COPY_POSTION_DATA_TERR
_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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 11 1


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

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

Operational # TM Account Geo Zone Hierarchy


Division Driven

Operational # TM Account Geo Zone Hierarchy


Driven

112 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Operational # TM Contact Geo Zone Hierarchy


Division Driven

Operational # TM Contact Geo Zone Hierarchy


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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 11 3


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

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

114 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

ALIGNMENT_STATUS Activation Activation Tasks Y


Tasks Failed Failed

ALIGNMENT_STATUS Run Tasks Run Tasks Y


Unknown Unknown
ALIGNMENT_STATUS Activation Activation Tasks Y
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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 11 5


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

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'

116 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Instructions for ACR 272


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


1 In Siebel Tools, navigate to Object Explorer.

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 11 7


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

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
1 In Siebel Tools, navigate to Object Explorer.

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


1 In Siebel Tools, navigate to Object Explorer.

2 Click on Symbolic Strings, and add the new Symbolic Strings specified in the Symbolic Strings
worksheet within Repository Changes.xls.

118 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Applet Setup
1 In Siebel Tools, navigate to Object Explorer.

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
Attributes listed in the Program Level Attributes worksheet within High Miles Changes.xls.

Tier Rule Setup


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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 11 9


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

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


1 Within Siebel Loyalty, navigate to Loyalty Program Administration, and query for the High Miles
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.

6 Click the Activate button to activate the promotion.

Instructions for ACR 296


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.

120 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Project Territory Management

Class CSSBusComp

Table S_ASSET_POSTN

Log Changes TRUE

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 12 1


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

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

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

Project Territory Management

Class CSSBusComp

Table S_POSTN_CON

Log Changes TRUE

Fields

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 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.

122 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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)

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 12 3


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

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

Instructions for ACR 308


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

124 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Label Destination Label Destination 2,203 Control


Availability Availability

Label Destination Label Destination 2,202 Control


Status Status

Label Selection Type Label Selection Type 1,201 Control

Label Transaction Type Label Transaction Type 1,202 Control

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 12 5


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

Applet Web Template Items

Name Control Item Identifier Type


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

126 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Destinati Y Y SBL_DESTINATION
Destination Availability

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 12 7


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

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
Label Y N SBL_DESTINATION
Destination Availability

Label

Right

Y
Destinati _AVAILABILITY-
on 1004231000-2LG
Availabilit
y

Label Y N SBL_DESTINATION
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

128 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 12 9


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

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

Applet Web Template Items


Name Control Item Identifier Type

bBulkTransfer bBulkTransfer 109 Control

130 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Destination Y FS PickList Y DTYPE_TEXT


Inventory Inventory
Location

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 13 1


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

Fields

Immediate
Post Predefault
Name Changes Picklist Value Required Type

Destination Y FS PickList Y DTYPE_TEXT


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

132 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 13 3


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

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

134 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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


FS Inventory Transaction
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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 13 5


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

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.

136 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 13 7


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

Business Service Method AddAssetsToTxn Arguments

Storage
Name Changed Data Type Type Comments Optional Type

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

Aggregate String Input Value of this i/p argument is the Y Property


Per Property name of the property on which
2 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

Aggregate String Input Value of this i/p argument is the Y Property


Per Property name of the property on which
3 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

138 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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


Per Property name of the property on which
4 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

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 13 9


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

Business Service Method 'BulkTransfer' Arguments

Storage
Name Changed Data Type Type Comments Optional Type

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.

140 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Business Service Method 'BulkTransfer' Arguments

Storage
Name Changed Data Type Type Comments Optional Type

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 14 1


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

Business Service Method CommitTxn Arguments

Data
Name Changed Type Type Comments Optional Storage Type

Error Code Y String Output N Property

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
Name Changed Data Type Type Comments Optional Type

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

Error Code Y String Output N Property

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

142 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Business Service Method Create CompleteInvTxn Arguments

Storage
Name Changed Data Type Type Comments Optional Type

Transaction Y String Output N Property


Number

Transaction Y String Input N Property


Type ID

Business Service Method GetDetails Arguments

Data
Name Changed Type Type Comments Optional Storage Type

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

Input: Y String Input Value of this i/p "Y Property


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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 14 3


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

Business Service Method GetDetails Arguments

Data
Name Changed Type Type Comments Optional Storage Type

Input: Y String Input Value of this i/p "Y Property


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

144 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Business Service Method GetDetails Arguments

Data
Name Changed Type Type Comments Optional Storage Type

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 14 5


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

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

Default: Source Y String Input "Default: xxx". Y Property


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

Default: Source Y String Input "Default: xxx". Y Property


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

146 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 14 7


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

Business Service Method SetTxnDetailsFromTxnSet Arguments

Data
Name Changed Type Type Comments Optional Storage Type

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

Default: Y String Input "Default: xxx". Y Property


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

Default: Y String Input "Default: xxx". Y Property


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

148 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Business Service Method SetTxnDetailsFromTxnSet Arguments

Data
Name Changed Type Type Comments Optional Storage Type

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 14 9


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

Business Service Method SetTxnDetailsFromTxnSet Arguments

Data
Name Changed Type Type Comments Optional Storage Type

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


Destination xxx". Here "xxx"
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.

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


Destination xxx". Here "xxx"
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.

150 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Business Service Method SetTxnDetailsFromTxnSet Arguments

Data
Name Changed Type Type Comments Optional Storage Type

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


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.

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


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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 15 1


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

Business Service Method SetTxnDetailsFromTxnSet Arguments

Data
Name Changed Type Type Comments Optional Storage Type

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


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.

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


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.

152 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Business Service Method SetTxnDetailsFromTxnSet Arguments

Data
Name Changed Type Type Comments Optional Storage Type

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


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.

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


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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 15 3


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

Business Service Method SetTxnDetailsFromTxnSet Arguments

Data
Name Changed Type Type Comments Optional Storage Type

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

154 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 15 5


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

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
FS Inventory Transaction

PickList Generic

N
Y

Type

BULK_INV_TXN_TYPE

Txn Type Picklist

156 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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
Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Configuration Instructions
for Enhancements and Updates

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

Instructions for ACR 323


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.

2 Create a new calculated field on the Business Component to hold the symbolic URL:

■ Name: MyReports

■ Calculated: True

■ Calculated Value: "MyReports"

158 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Business Component Modifications for the 'Personal Profile' View


1 Within Siebel Tools, navigate to the 'RS Personal Settings' Business Component.

2 Create a new calculated field on the Business Component to hold the symbolic URL:

■ Name: PersonalProfile

■ Calculated: True

■ 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

■ Class: CSSSWEFrameReportPortlet

2 Delete the existing control and create a new control. The control should have the following
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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 15 9


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

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

■ Class: CSSSWEFrameReportPortlet

2 Delete the existing control and create a new control. The control should have the following
properties:

■ Name: PersonalProfile

■ 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

160 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

■ Host Name: The location of your Report Server


■ Fixup Name: OutsideApplication

■ Multivalue Treatment : Comma Separated

■ SSO Disposition: Form Redirect

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 #

locale N Field Data Language Y N 1


Code

PreloadUrlPerSes Y Command TRUE Y N 1


sion

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 16 1


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

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

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 'PersonalProfile'


1 Create a new Symbolic URL called "PersonalProfile" with the following values:

■ Name: PersonalProfile

■ URL: http://rshost/acweb/options.do

■ Host Name: The location of your Report Server

■ Fixup Name: OutsideApplication

■ Multivalue Treatment : Comma Separated

■ SSO Disposition: Form Redirect

2 Create the following Symbolic URL Arguments for 'PersonalProfile':

Required Argument Argument Append as Substitute Seq


Name Argument Type Value Argument in 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

162 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Required Argument Argument Append as Substitute Seq


Name Argument Type Value Argument in Text #

rsPassword Y Field RS Password Y N 1

serverURL Y Field Server URL Y N 1

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 16 3


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

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.

164 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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.

Instructions for ACR 327


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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 16 5


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

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

166 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

LOV Name Value Order

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

LOV Name Value Order

ABO_BR_ACTSET_TYPE New 1

ABO_BR_ACTSET_TYPE Modify 2

ABO_BR_ACTSET_TYPE Upgrade 3

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 16 7


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

LOV Name Value Order

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.

168 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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-


Process Workflow.xml

4 ABO Bulk Request ABO Bulk Request - Delete Sub-


Process Workflow.xml

5 ABO Bulk Request ABO Bulk Request - Modify Sub-


Process Workflow.xml

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


Process Workflow.xml

12 ABO Bulk Request ABO Bulk Request - Submit


Driver Process Workflow.xml

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 16 9


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

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


Process Workflow.xml

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

170 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

■ ABO Order Item Drill Down View

Instructions for ACR 331


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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 17 1


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

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

172 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 17 3


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

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

174 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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"

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 17 5


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

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

ContextServiceWrapperServi New
ce-QuoteHeader-Verify

ContextServiceWrapperServi New
ce-OrderItem-Verify

ContextServiceWrapperServi New
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"

176 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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).

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 17 7


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

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:

178 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 17 9


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

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)

180 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

*******************************

* 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 *

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 18 1


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

************************************

1. View readme

2. Install SearchServer

3. Exit

Choose selection and press [ENTER]:3

Instructions for ACR 347


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.

Instructions for ACR 372


Use the following procedures to implement ACR 372.

182 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 18 3


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

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

184 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Table S_PRD_CMPLNT_LS

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

Table S_PRD_CMPLNT_LS

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 18 5


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

Single Value Fields

Text
New/Modify Name Column Length Type
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

186 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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)

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 18 7


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

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

Name Type 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

Business Component Project

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

188 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

LS Medical Product Issue-Manufacturer Detail Applet


Update the existing LS Medical Product Issue-Manufacturer Detail Applet as shown below. You also
need to add the new Controls to the Applet Web Template.

LS Medical Product Issue - Manufacturer Detail


Applet

Business Component Project

LS Medical Product Issue LS Medical Product


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

Type of SBL_LS_MPI_30-DAY 30-day Type of CHECK Checkbox


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

Name Control Item Identifier Type

Combo Product Combo Control


Product

STN Number STN Number Control

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 18 9


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

Applet Web Template Item (New)1

Name Control Item Identifier Type


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
need to add the new Controls to the Applet Web Template.

Alignment Condition Form Applet

Business Component Project

LS Medical Product Issue LS Medical Product


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

190 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

LS Medical Product Issue-Manufacturer Detail Applet RR


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

Alignment Condition Form Applet

Business Component Project

LS Medical Product Issue LS Medical Product


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

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


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

Type of SBL_LS_MPI_30-DAY 30-day Type of CHECK Checkbox


Report - Report -
30-day 30-day
Flag Flag

Applet Web Template

Name Type Web Template

Edit Edit Applet Form Grid


Layout

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 19 1


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

Applet Web Template Item (New)1

Name Control Item Identifier Type

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

192 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Field Type of Field Type of Report - 30-day Flag


Report - 30-
day Flag

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 19 3


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

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

Field Type of Field Type of Report - 7-day Flag


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

194 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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

Section Parameter Value

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 19 5


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

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:

196 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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).

Instructions for ACR 382


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.

Instructions for ACR 389


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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 19 7


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

Instructions for ACR 391


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.

Instructions for ACR 409


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.

Instructions for ACR 415

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


1 Navigate to Administration > PIM Server Integration > Configuration.

2 Select the Exchange Calendar profile.

3 Create a record with the following values:

❏ Section: Archive

❏ Parameter: ArchiveGracePeriod

❏ Value: 5 (in days)

198 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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.

1 Navigate to Administration > PIM Server Integration > Configuration.

2 Select the Siebel profile, as shown in the following table:

Section Parameter Value

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 19 9


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

■ 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).

200 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 20 1


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

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:

202 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 20 3


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

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].

204 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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.

Instructions for ACR 427


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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 20 5


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

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

206 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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 Maintenance Release Guide Version 7.8.2, Rev. X ■ 20 7


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

Instructions for ACR 428


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

208 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

❏ 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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 20 9


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

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

210 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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:

<Tools Install Directory>\bin\dataimp /u SADMIN /p sadmin /f <Tools Install


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

<Tools Install Directory> - Replace with your Siebel Tools install directory.

<ODBC Source Name> - Replace with the ODBC name created in the previous steps.

c Run the following command for seed_locale_XXX.dat:

<Tools Install Directory>\bin\dataimp /u SADMIN /p sadmin /f <Tools Install


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

<Tools Install Directory> - Replace with your Siebel Tools install directory.

<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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 21 1


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

❏ 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

212 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

❏ 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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 21 3


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

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

214 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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
(Updated workflows for nested service
bundle changes)

SIS OM Edit Service Order Line Item Modified SIS OM Base Architecture
(Updated workflows for nested service
bundle changes)

CMU SIA Submit Adjustment Request to New CMU Billing Integration


External

a Select Workflow Process in Siebel Tools Object Explorer.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 21 5


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

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.)
18 Restart the Siebel Server.
19 Launch the Siebel Communications application.

Postinstallation Instructions for ACR 428


You must perform the procedures in this subtopic after you have configured ACR 428.

216 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 21 7


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

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.

218 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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.

Instructions for ACR 432


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.

Instructions for ACR 460


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.

Instructions for ACR 471


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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 21 9


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

Instructions for ACR 481


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:

Section Parameter Value

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:

Section Parameter Value

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.

220 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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:

Section Parameter Value

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 ■ 22 1


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.

222 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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 ■ 22 3


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:

224 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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.

This task is a step in “Roadmap for Implementing Oracle BI Publisher Enhancements” on page 222.

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 ■ 22 5


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.

226 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Process of Implementing
Siebel Fix Pack 7.8.2.14

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.

This task is a step in “Process of Implementing Siebel Fix Pack 7.8.2.14” on page 226.

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 22 7


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Process of Implementing
Siebel Fix Pack 7.8.2.14

■ 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

9 Restart the Siebel Server.

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.

This task is a step in “Process of Implementing Siebel Fix Pack 7.8.2.14” on page 226.

To apply seed data changes


1 Verify the following tables are in the repository:

■ S_XMLP_REPOUTPT

■ S_XMLP_REP_IOBJ

228 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Process of Implementing
Siebel Fix Pack 7.8.2.14

■ 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.

This task is a step in “Process of Implementing Siebel Fix Pack 7.8.2.14” on page 226.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 22 9


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Process of Implementing
Siebel Fix Pack 7.8.2.14

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).

230 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Process of Implementing
Siebel Fix Pack 7.8.2.14

■ 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.

This task is a step in “Process of Implementing Siebel Fix Pack 7.8.2.14” on page 226.

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 23 1


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Process of Implementing
Siebel Fix Pack 7.8.2.14

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.

This task is a step in “Process of Implementing Siebel Fix Pack 7.8.2.14” on page 226.

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.

5 Restart the Siebel Server.

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.

232 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Process of Implementing
Siebel Fix Pack 7.8.2.14

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
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).

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.

This task is a step in “Process of Implementing Siebel Fix Pack 7.8.2.14” on page 226.

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 23 3


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Process of Implementing
Siebel Fix Pack 7.8.2.14

For more information about fonts in Siebel Business Applications, see Siebel Global Deployment
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).

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.

This task is an optional step in “Process of Implementing Siebel Fix Pack 7.8.2.14” on page 226.

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


This task is an optional step in “Process of Implementing Siebel Fix Pack 7.8.2.14” on page 226.

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
Oracle Technology Network (OTN).

234 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 23 5


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

Configuring JVM Settings


This topic describes how to configure the JVM settings.

This task is a step in “Process of Configuring Scheduling and Parameterization for Oracle BI Publisher
Reports” on page 235.

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
Oracle Technology Network (OTN).

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

236 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 23 7


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

Configuring User Management for Oracle BI Publisher


Reports
This topic provides instructions for configuring user management in the Siebel application for ACR
483.

This task is a step in “Process of Configuring Scheduling and Parameterization for Oracle BI Publisher
Reports” on page 235.

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.

5 Restart the Siebel Server.

238 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Configuring Report Scheduling for Oracle BI Publisher


Reports
This topic provides instructions for configuring report scheduling in the Siebel application.

This task is a step in “Process of Configuring Scheduling and Parameterization for Oracle BI Publisher
Reports” on page 235.

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 23 9


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

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

4 Restart the Siebel Server.

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.

This task is a step in “Process of Configuring Scheduling and Parameterization for Oracle BI Publisher
Reports” on page 235.

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

240 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

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 ■ 24 1


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Securing User Access to the
Oracle BI Publisher Server

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.

This task is a step in “Roadmap for Implementing Oracle BI Publisher Enhancements” on page 222.

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://
www.oracle.com/technology/documentation/siebel.html) on Oracle Technology Network (OTN).

242 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Securing User Access to the
Oracle BI Publisher Server

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 24 3


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Securing User Access to the
Oracle BI Publisher Server

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.

This task is a step in “Securing User Access to the Oracle BI Publisher Server” on page 242.

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.

244 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Securing User Access to the
Oracle BI Publisher Server

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 24 5


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Securing User Access to the
Oracle BI Publisher Server

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.

This task is a step in “Securing User Access to the Oracle BI Publisher Server” on page 242.

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.

246 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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.

This task is a step in “Roadmap for Implementing Oracle BI Publisher Enhancements” on page 222.

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 ■ 24 7


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.

248 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 24 9


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
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

250 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
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

Search specification:

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 25 1


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
Configurations

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: CG Retail Product

Search specification:

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)

252 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
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

Search specification:

Old Value New Value

N/A [Mark for Delete] not like 'Delete-*' OR [Mark


for Delete] IS NULL

PickList:

Name: Retail Profile Distribution Code PickList

Search specification:

Old Value New Value

N/A [Name] <> 'Delete'

Applet:

Name: CPG Product Distribution Applet (Toggle Read-Only)

Search specification:

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 25 3


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
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.

254 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 25 5


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
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

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 changes were removed.

5 Check the simulator report file.

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.

4 Download and save the warnings at the end of the import.

5 Make sure that the product changes were removed.

6 Check the simulator report file.

Case 4: Name not found, but ID in use


1 In the first database, update Product Definition from "Simp Adm1" to "Simp Adm1 Mod".

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 Check the simulator report file.

See the zip file folder on the main 7.8.2.x Maintenance Release page to access the
Cfg_Vod_Import_Simulator.xml file.

256 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 25 7


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
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:

258 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
Configurations

Field Picklist Field

Prod Cfg Model Id Configuration Model Id

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:

■ Name = Prod Cfg Model Id

■ 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:

■ Name = Prod Cfg Model Id

■ Join = Original Promotion

■ Column = CFG_MODEL_ID

■ Type = DTYPE_ID

■ Text Length = 15

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 25 9


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
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:

Field Picklist Field

Prod Cfg Model Id Configuration Model Id

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:

■ Name = Prod Cfg Model Id

■ 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

260 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
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".

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 26 1


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
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
■ Source 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.

262 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
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

■ Source 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).

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 26 3


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
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.

264 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Testing Your ACR 483
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 ■ 26 5


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

266 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 26 7


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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)

268 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 26 9


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

270 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 27 1


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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:

■ Siebel_Image = The directory for your version-specific Siebel installation image, such as
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.

272 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

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 SWSE, navigate to
Siebel_Image\Windows\Server\Siebel_Web_Server_Extension, 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 SWSE 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 SWSE, navigate to
Siebel_Image\Windows\Server\Siebel_Web_Server_Extension, where:

■ Siebel_Image = The directory for your version-specific Siebel installation image, such as
D:\Siebel_Install_Image\7.8.2.x.

7 Double-click setup.exe to launch the SWSE 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.

9 Follow all prompts to complete installation of 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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 27 3


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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


1 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 Reports Server, navigate to
Siebel_Image\Windows\Server\Siebel_Reports_Server, where:

■ Siebel_Image = The directory for your version-specific Siebel installation image, such as
D:\Siebel_Install_Image\7.8.2.0.

2 Double-click setup.exe to launch the Siebel Reports Server installer for 7.8.2.

3 Select a 7.8.0 or 7.8.1.x instance to patch from the list of detected installations.

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.

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 Reports Server, navigate to
Siebel_Image\Windows\Server\Siebel_Reports_Server, where:

■ Siebel_Image = The directory for your version-specific Siebel installation image, such as
D:\Siebel_Install_Image\7.8.2.x.

7 Double-click setup.exe to launch the Siebel Reports 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.

9 Enter your Actuate license key again. (Enter the same license key that you entered in Step 4.)

10 Follow all prompts to complete installation of 7.8.2.x.

274 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

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 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:

■ Siebel_Image = The directory for your version-specific Siebel installation image, such as
D:\Siebel_Install_Image\7.8.2.0.

3 Double-click install.exe to launch the client 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. The directory would match the directory from Step 2, except that:

■ Siebel_Image = The directory for your version-specific Siebel installation image, such as
D:\Siebel_Install_Image\7.8.2.x.

7 Double-click install.exe to launch the client 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.

9 Follow all prompts to complete installation of 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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 27 5


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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:

276 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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_Image = The directory for your version-specific Siebel installation image, such as
/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:

■ UNIX_OS = Your UNIX operating system, such as aix (AIX), hp (HP-UX), or sol (Solaris).

10 Select a 7.8.0 or 7.8.1.x instance to patch from the list of detected installations.
11 Follow all prompts to complete installation of 7.8.2.
12 Navigate to the Siebel image location for version 7.8.2.x, then to the directory where the installer
is located. The directory would match the directory from Step 7, except that:

■ Siebel_Image = The directory for your version-specific Siebel installation image, such as
/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.
14 Select a 7.8.2 or previous 7.8.2.x instance to patch from the list of detected installations.
15 Follow all prompts to complete installation of 7.8.2.x.
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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 27 7


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

3 (AIX only) Verify that the login ID performing installation has permission to run slibclean by
asking the administrator to change the permission as follows:

chmod 6555 /usr/sbin/slibclean

4 (AIX only) Execute slibclean, as follows:

/usr/sbin/slibclean

5 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 SWSE, navigate to Siebel_Image/UNIX_OS/Server/
Siebel_Web_Server_Extension, where:

■ Siebel_Image = The directory for your version-specific Siebel installation image, such as
/Siebel_Install_Image/7.8.2.0.

■ UNIX_OS = Your UNIX operating system, such as AIX, HPUX (HP-UX), or Solaris.

6 (For GUI mode) Run setupUNIX_OS to launch the SWSE installer in GUI mode for 7.8.2, where:

■ UNIX_OS = Your UNIX operating system, such as aix (AIX), hp (HP-UX), or sol (Solaris).

Go to Step 8.

7 (For console mode) Enter the following command to launch the SWSE installer in console mode
for 7.8.2:

setupUNIX_OS –is:javaconsole -console

where:

■ UNIX_OS = Your UNIX operating system, such as aix (AIX), hp (HP-UX), or sol (Solaris).

8 Select a 7.8.0 or 7.8.1.x instance to patch from the list of detected installations.
9 Follow all prompts to complete installation of 7.8.2.

10 Navigate to the Siebel image location for version 7.8.2.x, then to the directory where the installer
is located. The directory would match the directory from Step 5, except that:

■ Siebel_Image = The directory for your version-specific Siebel installation image, such as
/Siebel_Install_Image/7.8.2.x.

11 Launch the SWSE installer for 7.8.2.x, in GUI mode or console mode.
12 Select a 7.8.2 or previous 7.8.2.x instance to patch from the list of detected installations.
13 Follow all prompts to complete installation of 7.8.2.x.

278 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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


1 (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

2 (AIX only) Execute slibclean, as follows:

/usr/sbin/slibclean

3 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 Reports Server, navigate to Siebel_Image/
UNIX_OS/Server/Siebel_Reports_Server, where:

■ Siebel_Image = The directory for your version-specific Siebel installation image, such as
/Siebel_Install_Image/7.8.2.0.

■ UNIX_OS = Your UNIX operating system, such as AIX, HPUX (HP-UX), or Solaris.

4 (For GUI mode) Run setupUNIX_OS to launch the Siebel Reports 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 6.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 27 9


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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:

setupUNIX_OS –is:javaconsole -console

where:

■ UNIX_OS = Your UNIX operating system, such as aix (AIX), hp (HP-UX), or sol (Solaris).

6 Select a 7.8.0 or 7.8.1.x instance to patch from the list of detected installations.

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.

8 Follow all prompts to complete installation of 7.8.2.

9 Navigate to the Siebel image location for version 7.8.2.x, then to the directory where the installer
is located. The directory would match the directory from Step 3, except that:

■ Siebel_Image = The directory for your version-specific Siebel installation image, such as
/Siebel_Install_Image/7.8.2.x.

10 Launch the Siebel Reports Server installer for 7.8.2.x, in GUI mode or console mode.
11 Select a 7.8.2 or previous 7.8.2.x instance to patch from the list of detected installations.
12 Enter your Actuate license key again. (Enter the same license key that you entered in Step 7.)
13 Follow all prompts to complete installation of 7.8.2.x.
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

280 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 28 1


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

282 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 28 3


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

284 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 28 5


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

286 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 28 7


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

288 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 28 9


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

290 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 29 1


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Installation Instructions for
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.

292 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 29 3


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

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

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.

Resolved Change Requests in the Siebel 7.8.2.13 Fix


Pack
Table 19 lists the change requests that were resolved in the Siebel 7.8.2.13 Fix Pack.

Table 19. Resolved Change Requests in the Siebel 7.8.2.13 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

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

294 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 19. Resolved Change Requests in the Siebel 7.8.2.13 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 29 5


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 19. Resolved Change Requests in the Siebel 7.8.2.13 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

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

296 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 19. Resolved Change Requests in the Siebel 7.8.2.13 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 29 7


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 19. Resolved Change Requests in the Siebel 7.8.2.13 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

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

298 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 19. Resolved Change Requests in the Siebel 7.8.2.13 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

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)

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 29 9


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 19. Resolved Change Requests in the Siebel 7.8.2.13 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

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.”

300 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 19. Resolved Change Requests in the Siebel 7.8.2.13 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 30 1


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 19. Resolved Change Requests in the Siebel 7.8.2.13 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

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

302 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 19. Resolved Change Requests in the Siebel 7.8.2.13 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 30 3


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 19. Resolved Change Requests in the Siebel 7.8.2.13 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

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

304 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 19. Resolved Change Requests in the Siebel 7.8.2.13 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 30 5


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 19. Resolved Change Requests in the Siebel 7.8.2.13 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

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

306 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 19. Resolved Change Requests in the Siebel 7.8.2.13 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

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

Resolved Change Requests in the Siebel 7.8.2.12 Fix


Pack
Table 20 lists the change requests that were resolved in the Siebel 7.8.2.12 Fix Pack.

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 30 7


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

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

308 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 30 9


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

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

310 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

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
receive the following error
message: "No association list is
available in this applet.(SBL-DAT-
00276)".

General
Activities

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 31 1


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

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

312 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 31 3


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

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

PIM Server Integration


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.

314 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

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

Server Infrastructure
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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 31 5


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

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

316 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

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 for Windows
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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 31 7


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

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)

318 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

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)

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 31 9


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

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


and Siebel CRM On Premise
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


and Siebel CRM On Premise
integration: contact information
does not synchronize from the
Japanese-language version of On
Premise to On Demand

320 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

ACR 460: Oracle CRM On Demand 12-1S5SKHU 12-1S5SKGK 7.8.2.12


and Siebel CRM On Premise
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


and Siebel CRM On Premise
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


and Siebel CRM On Premise
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


and Siebel CRM On Premise
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
and Siebel CRM On Premise
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


and Siebel CRM On Premise
integration: the Integration User
column is missing

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 32 1


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

ACR 460: Oracle CRM On Demand 12-1S5SKRV 12-1S5SKQL 7.8.2.12


and Siebel CRM On Premise
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


and Siebel CRM On Premise
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


and Siebel CRM On Premise
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


and Siebel CRM On Premise
integration: when users update
an existing product's net price
within On Premise, the update
does not display within On
Demand

322 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

ACR 460: Oracle CRM On Demand 12-1S5SMHP 12-1S5SMGF 7.8.2.12


and Siebel CRM On Premise
integration: when users log into
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
and Siebel CRM On Premise
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


and Siebel CRM On Premise
integration: when users log into
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


and Siebel CRM On Premise
integration: when users log into
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


and Siebel CRM On Premise
integration: delete triggers are
not being generated on Solaris

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 32 3


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

ACR 460: Oracle CRM On Demand 12-1SN6XRI 12-1SN6XQ9 7.8.2.12


and Siebel CRM On Premise
integration: when users log into
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

324 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

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

Layout and Rendering


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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 32 5


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 20. Resolved Change Requests in the Siebel 7.8.2.12 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed # Request # Version Changes

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

Resolved Change Requests in the Siebel 7.8.2.11 Fix


Pack
Table 21 lists the Change Requests that are included in the Siebel 7.8.2.11 Fix Pack.

Table 21. Resolved Change Requests 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

326 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 21. Resolved Change Requests in the Siebel 7.8.2.11 Fix Pack

Change Fixed in Configuration


Issue Addressed Fix Request # Request # Version Changes

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 32 7


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 21. Resolved Change Requests in the Siebel 7.8.2.11 Fix Pack

Change Fixed in Configuration


Issue Addressed Fix Request # Request # Version Changes

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

328 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 21. Resolved Change Requests in the Siebel 7.8.2.11 Fix Pack

Change Fixed in Configuration


Issue Addressed Fix Request # Request # Version Changes

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 32 9


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 21. Resolved Change Requests in the Siebel 7.8.2.11 Fix Pack

Change Fixed in Configuration


Issue Addressed Fix Request # Request # Version Changes

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.

330 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 21. Resolved Change Requests in the Siebel 7.8.2.11 Fix Pack

Change Fixed in Configuration


Issue Addressed Fix Request # Request # Version Changes

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.

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 33 1


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 21. Resolved Change Requests in the Siebel 7.8.2.11 Fix Pack

Change Fixed in Configuration


Issue Addressed Fix Request # Request # Version Changes

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

332 ■ Siebel Maintenance Release Guide Version 7.8.2, Rev. X


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 21. Resolved Change Requests in the Siebel 7.8.2.11 Fix Pack

Change Fixed in Configuration


Issue Addressed Fix Request # Request # Version Changes

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
receive an error message

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

Siebel Maintenance Release Guide Version 7.8.2, Rev. X ■ 33 3


Siebel Maintenance Release Guide, Version 7.8.2, Rev. X ■ Resolved Change Requests

Table 21. Resolved Change Requests in the Siebel 7.8.2.11 Fix Pack

Change Fixed in Configuration


Issue Addressed Fix Request # Request # Ve