Siebel Maintenance Release Guide Version 8.1.1.5, Rev. B

Siebel Maintenance Release Guide
Version 8.1.1.5, Rev. B June 2011
Copyright 2005, 2011 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be errorfree. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. 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, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Contents
Release Notes for the Siebel 8.1.1.5 Fix Pack Whats New in This Revision 7
5 8 21
Quick Fixes Included in the Siebel 8.1.1.5 Fix Pack Enhancements and Updates in Version 8.1.1.5
Instructions Instructions Instructions Instructions Instructions Instructions Instructions for for for for for for for ACR ACR ACR ACR ACR ACR ACR 484 495 525 600 604 633 713 21 21 22 27 51 52 56
17
Configuration Instructions for Enhancements and Updates
Siebel Fix Pack Installation Instructions
82
Siebel Fix Pack Installation Overview 83 About Installing Siebel Fix Packs 87 Installing the Siebel Fix Pack on Microsoft Windows 87 Installing the Siebel Fix Pack on UNIX 92 Configuring Slipstream Patch Installation 97 Postinstallation Tasks for the Siebel Server 98 Postinstallation Tasks for the Web Server 99 Postinstallation Tasks for High Interactivity Clients 99 Postinstallation Tasks for Supporting Additional Languages Uninstalling Siebel Fix Packs 101
100
Resolved Change Requests

Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel
103 104
Resolved Change Requests in the Siebel 8.1.1.5 Fix Pack

Apps - Customer Order Management 105 Apps - Data Quality 108 Apps - Field Service 108 Apps - Handheld Client 109 Apps - Marketing 110 Apps- Multichannel Technologies 112 Apps - Oracle Customer Hub 113 Apps - PRM 113 Apps - Sales 113 Apps - Search & Knowledge Management 114
Siebel Maintenance Release Guide Version 8.1.1.5, Rev. B
Contents n
Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel
Apps - Service 116 Apps - Territory Management 117 Apps - UCM 117 Automotive 117 Consumer Goods 118 Communications and Energy 118 Core - Accessibility 119 Core - Common Components 120 Core - DB Deployment and Configuration Core - DG Deployment 120 Core - EAI 121 Core - Globalization 121 Core - PIM Integration 122 Core - Server BizLogic Script 124 Core Server BizLogic WF 124 Core - Server Infrastructure 125 Core - Server OM Framework 125 Core - Server OM Svcs 126 Core - Tools 127 Core - UIF Client 127 Core - UIF Server 129 Core - UIF Task Based UI 131 Core - UIF Web Gateway 131 Core - UNIX 132 Core - Windows 132 Documents 132 Engineering 133 Financial Services 133 Life Sciences 133 Loyalty 136 Reports 137 Server Remote 140 Travel & Transportation 140
120
Oracle Welcomes Your Comments
150
1
June 2011
Siebel Maintenance Release Guide, Version 8.1.1.5, Rev. B
NOTE: As of the Siebel 8.1.1.5 Fix Pack, the Siebel Maintenance Release Guide is release-specific. This guide documents the Quick Fixes, enhancements, instructions for enhancements, and bugs provided in Siebel 8.1.1.5. For information about what was provided in Siebel 8.1.1.1 through Siebel 8.1.1.4, see Siebel Maintenance Release Guide, Version 8.1.1.x. To access this guide, from within My Oracle Support, navigate to the Knowledge tab, and search for Article ID 880452.1. This guide includes the following topics: Whats New in This Revision on page 7 Release Notes for the Siebel 8.1.1.5 Fix Pack on page 5 Quick Fixes Included in the Siebel 8.1.1.5 Fix Pack on page 8 Enhancements and Updates in Version 8.1.1.5 on page 17 Configuration Instructions for Enhancements and Updates on page 21 Siebel Fix Pack Installation Instructions on page 82 Resolved Change Requests in the Siebel 8.1.1.5 Fix Pack on page 104 Oracle Welcomes Your Comments on page 150
Release Notes for the Siebel 8.1.1.5 Fix Pack

The following section describes known issues with the Siebel 8.1.1.5 Fix Pack, as well as any applicable workaround information. CAUTION: The following section is not a comprehensive listing of all known issues for this Fix Pack. To access Siebel Release Notes version 8.1.1, from within My Oracle Support, navigate to the Knowledge tab and search for Article ID 557191.1.
Siebel 8.x Support for IBM HTTP Web Server 7 on AIX

NOTE: The following issue only applies to AIX customers. Category: General Subcategory: Web Server and SWSE Product Version: Siebel 8.1 Bug ID: 12316215
Siebel Maintenance Release Guide, Version 8.1.1.5, Rev. B Release Notes for the Siebel 8.1.1.5 Fix Pack
As of the Siebel 8.1.1.5 Fix Pack, IBM HTTP Server 7 is supported for the AIX platform. IBM HTTP Server 6.1 is supported for Siebel 8.1.1.1 through Siebel 8.1.1.4. IBM HTTP Server 6.1 is not supported for Siebel 8.1.1.5 and above.
Siebel Web Server Extension (SWSE) plug-in installation and configuration:
1 2 3
Install the base SWSE, but do not perform any configuration. Install the Siebel 8.1.1.5 Fix Pack. After 8.1.1.5 has been installed, configure SWSE.
ADM Deployment Fails on Siebel 8.1.1.4 on AIX 6.1 with Java 1.6
Product: Siebel Engineering - Release Engineering Component: Rel Eng/Build System Subcomponent: Build System ADM deployment fails in Siebel 8.1.1.4 on AIX 6.1 with Java 1.6. The copy command hangs. This issue only occurs on the AIX 6.1 environment. Use the following workaround to address this issue: CAUTION: Do not configure Management Agent until after you have applied Siebel 8.1.1.5.
1 2 3 4
Install Siebel Gateway Server, Siebel Server, and Siebel Management Agent. Apply the Siebel 8.1.1.5 Fix Pack. Configure the Siebel Gateway Server, Siebel Server, and Siebel Management Agent. Set the classpath and libpath explicitly as shown below for JAVA1.6 on AIX6.1: setenv LIBPATH /usr/java6/jre/lib/ppc:/usr/java6/jre/bin:/usr/java6/jre/bin/j9vm:${L IBPATH} setenv PATH /usr/java6/jre/lib/ppc:/usr/java6/jre/bin:/usr/java6/jre/bin/j9vm:${PAT H}
Do Not Deploy the AIA3.1.zip File

The following 8.1.1.5 bugs related to ACR 474 require configuration changes, but in order to configure these fixes, you must access the material in the AIA3.1.zip file. However, the AIA 3.1 (also known as AIA 11.1) release is not yet available. The following bugs are affected:

Bug 10605214 Bug 10604058
Siebel Maintenance Release Guide, Version 8.1.1.5, Rev. B Whats New in This Revision
Bug 10602944 Bug 10601341 Bug 10601366 Bug 10601365 Bug 10601368 Bug 11824787
Whats New in This Revision

Table 1 describes the changes in this version of the documentation. Table 1. Topic Enhancements and Updates in Version 8.1.1.5 on page 17 Instructions for ACR 620 on page 578 Resolved Change Requests in the Siebel 8.1.1.5 Fix Pack on page 104 Resolved Change Requests in the Siebel 8.1.1.5 Fix Pack on page 104 Added Bug ID for support for Microsoft Windows 2008 R2. Whats New in Siebel Maintenance Release Guide, Version 8.1.1.5, Rev. B Description Removed references to ACR 620.
How to Use This Guide

This document, Siebel Maintenance Release Guide, Version 8.1.1.5, lists the enhancements and fixes provided in the Siebel 8.1.1.5 Fix Pack. This guide also provides information, instructions, and guidelines for installing Siebel Business Applications Siebel Fix Pack 8.1.1.x releases on top of version 8.1.1 or a prior 8.1.1.x release. Use this Siebel Maintenance Release Guide in conjunction with Siebel Bookshelf documents, particularly the Siebel Installation Guide for the operating system you are using. NOTE: This Siebel Maintenance Release Guide is updated to include the latest Siebel Fix Pack 8.1.1.x release. The latest Siebel Fix Pack 8.1.1.x release available at publication time is Siebel Fix Pack 8.1.1.5. Verify the availability and applicability of all Fix Pack or Quick Fix releases with Oracle Global Customer Support before you install. The information contained herein supersedes, for warranty and other purposes, the contents of all other documentation that may accompany this product, including the following: My Oracle Support (https://support.oracle.com) Siebel System Requirements and Supported Platforms on Oracle Technology Network (http://download.oracle.com/docs/cd/E11886_01/srsphomepage.html)
Siebel Maintenance Release Guide, Version 8.1.1.5, Rev. B Quick Fixes Included in the Siebel 8.1.1.5 Fix Pack
This Siebel Maintenance Release Guide contains information about the following: How to install the maintenance (Fix Pack) release Product configuration issues and workarounds for your application
NOTE: There may be references to functionality, products, platforms, and language support in this document that are not available as part of the products that your organization has licensed. Consult Oracle Global Customer Support on My Oracle Support with questions regarding the applicability of Siebel Maintenance Release Guide items to your deployment.
Additional Documentation
Oracle reserves the right to modify the documentation for Siebel Business Applications at any time. For related Siebel documentation, see the following: My Oracle Support (https://support.oracle.com) (requires valid customer account) Siebel System Requirements and Supported Platforms on Oracle Technology Network (http:// download.oracle.com/docs/cd/E11886_01/srsphomepage.html) Siebel Bookshelf for Oracles Siebel Business Applications, Version 8.1 (http://www.oracle.com/ technology/documentation/siebel.html) on Oracle Technology Network (OTN)
Quick Fixes Included in the Siebel 8.1.1.5 Fix Pack

NOTE: The following table includes only the Quick Fixes included in the Siebel 8.1.1.5 Fix Pack. For information about Quick Fixes included in previous Fix Pack releases, see Siebel Maintenance Release Guide, Version 8.1.1.x on My Oracle Support. To access this guide, from within My Oracle Support, navigate to the Knowledge tab, and search for Article ID 880452.1.
Siebel Quick Fix releases are developed to address immediate critical issues for specific customers, and can be installed on top of Fix Packs. Quick Fixes address a small number of defects, and the fixes are typically rolled into the next available Fix Pack for wider distribution to the Siebel Business Applications customer base. Testing for Quick Fixes is focused and is usually limited to verifying that the fix works on the specific platforms that the affected customer is running. NOTE: If you have installed a Quick Fix for any Siebel 8.1.1 or 8.1.1.x release prior to Siebel 8.1.1.5, review the Quick Fixes Included in Siebel 8.1.1.x Fix Packs section within the Siebel Maintenance Release Guide, Version 8.1.1.x on My Oracle Support. To access this guide, from within My Oracle Support, navigate to the Knowledge tab and search for Article ID 880452.1.
Table 2.
Quick Fixes Included in Version 8.1.1.5 Fix Request ID/Bug ID 10595735 10597496 10597556 10594437 10600427 10603338 10602074 10601388 10603059 10605942 10572086 10604552 10603160 10605217 10589186 10595982 10587410 10586524 10592881 10599068 Quick Fix Version QF00BT QF00BU QF00BV QF00BW QF00BX QF00BZ QF00CB QF00CC QF00CC QF00CD QF00CE QF00CH 21112_12 21112_13 8.1.1 WM5 [21112_7] QF01CD QF0189 QF0195 QF01BK QF01BM Merged Into Fix Pack 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5
Change Request ID/ Base Bug ID 10595535 10597497 10597033 10594436 10600426 10582435 10601353 10601387 10603058 10587142 10572085 10604491 10601356 10605216 10585400 10593426 10550111 10584539 10592880 10598988
Fix Pack Base 8.1.1 [21112] 8.1.1 [21112] 8.1.1 [21112] 8.1.1 [21112] 8.1.1 [21112] 8.1.1 [21112] 8.1.1 [21112] 8.1.1 [21112] 8.1.1 [21112] 8.1.1 [21112] 8.1.1 [21112] 8.1.1 [21112] 8.1.1 WM5 [21112_12] 8.1.1 WM5 [21112_13] 8.1.1 WM5 [21112_7] 8.1.1.1 [21211[ 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211]
Table 2.
Quick Fixes Included in Version 8.1.1.5 Fix Request ID/Bug ID 10588365 10593616 10592086 10596139 10597390 10599895 10643886 10594276 10603543 10600699 10593419 10601716 10602091 10596446 10606027 10599794 10603247 10598514 11064672 10594564 10596435 11058917 11700093 10588992 10604927 10603605 10588663 10581745 10598874 Quick Fix Version QF01BP QF01BR QF01BR QF01BR QF01BS QF01BT QF01BV QF01BW QF01BW QF01BX QF01BZ QF01CA QF01CB QF01CC QF01CF QF01CH QF01CI QF01CJ QF01CL QF3104 QF5107 QF5108 QF5108 QF7102 QF01CK 02CA QF0234 QF0285 QF0293 Merged Into Fix Pack 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5
Change Request ID/ Base Bug ID 10588363 10570706 10592084 10594183 10597384 10589061 10643152 10594273 10603542 10600697 10577300 10601715 10599016 10558349 10606026 10599327 10603246 10593154 10643446 10594561 10594166 10589061 10599327 10588990 10603053 10603598 10588431 10550111 10598872
Fix Pack Base 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21219] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215]
10
Table 2.
Quick Fixes Included in Version 8.1.1.5 Fix Request ID/Bug ID 10590195 10599649 10590803 10597182 10596006 10601139 10601336 10599670 10598329 10598911 10597063 10597072 10598374 10600495 10596555 10599565 10592526 10592717 10600290 10599614 10599509 10598905 10599121 10599156 10601090 10589918 10602746 10601390 10594281 Quick Fix Version QF02AG QF02AH QF02AJ QF02AJ QF02AJ QF02AO QF02AP QF02AP QF02AQ QF02AS QF02AS QF02AS QF02AS QF02AT QF02AV QF02AV QF02AW QF02AW QF02AY QF02AY QF02AY QF02BA QF02BD QF02BE QF02BG QF02BH QF02BI QF02BM QF02BN Merged Into Fix Pack 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5
Fix Pack Base 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215]
11
Table 2.
Quick Fixes Included in Version 8.1.1.5 Fix Request ID/Bug ID 10603790 10603788 10600871 10602456 10603973 10603892 10602059 10601382 10599305 10603925 10598109 10604729 10604494 10596770 10599641 10603964 10604428 10606004 11061173 11065747 11819176 10594222 10603150 10604358 10600702 10604033 Quick Fix Version QF02BO QF02BP QF02BP QF02BP QF02BQ QF02BR QF02BT QF02BU QF02BW QF02BX QF02BY QF02CC QF02CE QF02CG QF02CG QF02CG QF02CG QF02CG QF02CG QF02CG QF02CI QF2202 8.1.1.2 21215_6B 8.1.1.2 WM5 [21215_10] 8.1.1.2 WM5 [21215_10] 8.1.1.2 WM5 [21215_10] Merged Into Fix Pack 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5
Change Request ID/ Base Bug ID 10598247 10582924 10599106 10602188 10598714 10603891 10602056 10601383 10598842 10603889 10598100 10603053 10604491 10596768 10599582 10603926 10604427 10606003 11702627 11702642 10606223 10594221 10529580 10513152 10600661 10604032
Fix Pack Base 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215_6B] 8.1.1.2 WM5 [21215_10] 8.1.1.2 WM5 [21215_10] 8.1.1.2 WM5 [21215_10]
12
Table 2.
Quick Fixes Included in Version 8.1.1.5 Fix Request ID/Bug ID 10600659 10600382 10601380 10592211 10592213 10590346 10599269 10598008 10597521 10598755 10599171 10599261 10598861 10599114 10600502 10599806 10602496 10598029 10590329 10600680 10602604 10598575 10601138 10603113 10644342 10599533 10598904 Quick Fix Version 8.1.1.2 WM5 [21215_8] 8.1.1.2 WM5 [21215_9] 8.1.1.2 WM5 [21215_9] QF0301 QF0301 QF0308 QF0322 QF0324 QF0325 QF0325 QF0329 QF0331 QF0332 QF0332 QF0335 QF0337 QF0338 QF0338 QF0340 QF0340 QF0340 QF0343 QF0344 QF0345 QF0346 QF0347 QF0349 Merged Into Fix Pack 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5
Change Request ID/ Base Bug ID 10600657 10585400 10592420 10588005 10589975 10589207 10597914 10570706 10597519 10598714 10599170 10599065 10582924 10599106 10600499 10589917 10594436 10597741 10543253 10577630 10602603 10598574 10592525 10597033 10643446 10565045 10598903
Fix Pack Base 8.1.1.2 WM5 [21215_8] 8.1.1.2 WM5 [21215_9] 8.1.1.2 WM5 [21215_9] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219]
13
Table 2.
Quick Fixes Included in Version 8.1.1.5 Fix Request ID/Bug ID 10603782 10603941 10600894 10600561 10599511 10596113 10535480 10600605 10601074 10604775 10605248 10602914 10605245 10605243 10605240 10605239 10605238 10603532 10605235 10605234 10605213 10604542 10598748 10604039 10603949 10603006 10605963 10605735 10602582 Quick Fix Version QF0350 QF0353 QF0355 QF0356 QF0357 QF0357 QF0358 QF0360 QF0361 QF0362 QF0363 QF0363 QF0363 QF0363 QF0363 QF0363 QF0363 QF0363 QF0363 QF0363 QF0363 QF0364 QF0365 QF0366 QF0368 QF0369 QF0370 QF0371 QF0374 Merged Into Fix Pack 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5
Fix Pack Base 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219]
14
Table 2.
Quick Fixes Included in Version 8.1.1.5 Fix Request ID/Bug ID 10605166 10604274 11786116 11786113 11786092 11786086 11785988 11786084 11786005 11785998 11785992 11786036 11786030 11786026 11786021 11786013 11786010 11821494 11712663 12312715 11933537 10602956 10603133 10593646 10592214 10592215 10592421 Quick Fix Version QF0378 QF0379 QF0384 QF0384 QF0384 QF0384 QF0384 QF0384 QF0384 QF0384 QF0384 QF0384 QF0384 QF0384 QF0384 QF0384 QF0384 QF0386 QF0390 QF0393 QF03AE QF2301 QF2301 8.1.1.3 WM5 [21219_1] 8.1.1.3 WM5 [21219_1] 8.1.1.3 WM5 [21219_1] 8.1.1.3 WM5 [21219_1] Merged Into Fix Pack 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5
Change Request ID/ Base Bug ID 10587142 10599370 10585231 10585602 10585662 10587790 10591800 10596768 10597058 10597068 10598201 10599582 10603926 10604427 10606003 11702627 11702642 10601353 10593154 11767251 10598842 10602955 10603132 10585400 10589652 10591406 10592420
Fix Pack Base 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 WM5 [21219_1] 8.1.1.3 WM5 [21219_1] 8.1.1.3 WM5 [21219_1] 8.1.1.3 WM5 [21219_1]
15
Table 2.
Quick Fixes Included in Version 8.1.1.5 Fix Request ID/Bug ID 10601476 10606232 10603778 10632594 11072815 11069872 10606421 11786192 11786182 11786180 11786170 11786119 11786168 11786133 11786130 11786123 11786162 11786158 11786151 11786145 11786142 11786136 10600524 11779599 10604566 10604172 11779457 11779661 Quick Fix Version 8.1.1.3 WM5 [21219_3] 8.1.1.3 WM5 [21219_6] QF0401 QF0402 QF0403 QF0403 QF0404 QF0407 QF0407 QF0407 QF0407 QF0407 QF0407 QF0407 QF0407 QF0407 QF0407 QF0407 QF0407 QF0407 QF0407 QF0407 QF0408 QF0408 QF0408 QF0408 QF0408 QF0408 Merged Into Fix Pack 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5
Change Request ID/ Base Bug ID 10601356 10606225 10596554 10597467 10597381 10604040 10597384 10585231 10585602 10585662 10587790 10591800 10596768 10597058 10597068 10598201 10599582 10603926 10604427 10606003 11702627 11702642 10599106 10601057 10602188 10602787 10605558 10605594
Fix Pack Base 8.1.1.3 WM5 [21219_3] 8.1.1.3 WM5 [21219_6] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225]
16
Siebel Maintenance Release Guide, Version 8.1.1.5, Rev. B Enhancements and Updates in Version 8.1.1.5
Table 2.
Quick Fixes Included in Version 8.1.1.5 Fix Request ID/Bug ID 11779503 11886540 11937495 11937475 11937580 11938696 12358803 11938155 10601585 Quick Fix Version QF0408 QF0411 QF0412 QF0413 QF0417 QF0419 QF0420 QF0420 8.1.1.5 Merged Into Fix Pack 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5 8.1.1.5
Change Request ID/ Base Bug ID 11059048 11850195 10593444 10593154 10601643 10594057 10603053 10606532 10576292
Fix Pack Base 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.5
Enhancements and Updates in Version 8.1.1.5

Table 3 lists the enhancements and updates provided in Fix Pack version 8.1.1.5.
17
Table 3.
Feature Enhancement or Certification Number ACR 464 ACR 484
Feature Enhancement or Certification Description Provides support for Siebel CRM Desktop for Outlook 2010. Provides an integration between Siebel Field Service and Oracle Real Time Scheduler. Instructions for ACR 484
ACR 495
ACR 495 provides the following enhancements to the Siebel Hospitality application: Run of House: Allows properties to set up a generic Run of House (ROH) room type or types to fulfill customer booking needs without enforcing availability to a specific room type. 24-Hour Hold: Allows the agent or customer to reserve function space and decide later how to divide the space and the time reserved to meet the requirements of their function. Five BIP reports: Account Profile Report, Accounting Event Check Report, Guest Event Check Report, Resume Report, Events Report Copy Function Line Items: Eliminates the need to reenter data by allowing users to copy line items from one function to another function. Function Space Diary Enhancements: Enhances the Function Space Diary functionality by providing users with the ability to see colorcoded bookings in the diary. The colors are based on the function status and the quote status. This enhancement also allows users to see function space information by using mouseovers. Arrival Date Modification: Provides the ability to sort on the Arrival Date field, and enhances the date-shifting functionality to allow users the flexibility to choose to change function dates, sleeping room dates, both, or neither. Sleeping Room Taxes and Service Charges: Adds support for managing and calculating sleeping-room taxes and service charges.
For more information about Siebel Hospitality functionality, see Siebel Hospitality Guide on the Siebel Bookshelf. Instructions for ACR 495
18
Table 3.
Feature Enhancement or Certification Number ACR 525
Feature Enhancement or Certification Description ACR 525: Provides the Warranty Management System. For more information about Siebel Automotive, see Siebel Automotive Guide and Siebel Dealer Administration Guide on the Siebel Bookshelf. Instructions for ACR 525
ACR 600
ACR 600 offers fixes for functionality that is required for accessibility support with screen readers. These features apply only to the Accessibility mode unless otherwise stated. ACR 600 provides the following enhancements: Show/Hide Sort icons in list applets The New, Query, and Save buttons have been recoded as HTML buttons instead of HTML links A personalization feature that allows user-specific settings for onscreen colors, fonts, and lines The ability to rename void(0) links New keyboard shortcuts:

Ctrl+Alt+O for Query Assistant Ctrl+Alt+X for Update Audit Cache Ctrl+Shift+9 for Cancel Query
For more information about accessibility enhancements, see Accessibility Guide for Siebel Business Applications on the Siebel Bookshelf. Instructions for ACR 600
19
Table 3.
Feature Enhancement or Certification Number ACR 604
Feature Enhancement or Certification Description ACR 604 adds three new features that are required for compliance with Section 508 and WCAG 1.0 accessibility standards: The ability to rename frame titles so that screen-reader users know what they are An indication of the active tab by a means other than by color only Addition of a warning message before session timeout occurs, with the option to extend the time available
For more information about this enhancement, see Siebel Fundamentals on the Siebel Bookshelf. Instructions for ACR 604
ACR 633
Provides Oracle Business Intelligence Publisher enhancements that include the following: Users can schedule BIP Reports for a time frame of a month or more Default Daily/Weekly/Monthly reports that are assigned to the Calendar view The Report Sharing feature has been extended to support multiorg A confirmation dialog box when Sample XML Data is successfully generated
For more information, see Siebel Reports Guide on the Siebel Bookshelf. Instructions for ACR 633
ACR 697 ACR 705 ACR 707 ACR 713
Certifies Microsoft Windows 2008 R2 Server. Certifies IBM HTTP Server 7 on AIX 6.1. Certifies Sun Java System Web Server 7 on Sun Solaris 10. ACR 713: Provides the modifications needed to support Oracle Clinical Trial Payments: Siebel Clinical Partial PIP. For more information about Siebel Life Sciences functionality, see Siebel Life Sciences Guide on the Siebel Bookshelf. Instructions for ACR 713
20
Siebel Maintenance Release Guide, Version 8.1.1.5, Rev. B Configuration Instructions for Enhancements and Updates
Configuration Instructions for Enhancements and Updates

This topic contains configuration instructions for some of the enhancements and updates provided in version 8.1.1.5. NOTE: It is only necessary to perform the configurations in the following section if you want to implement the ACRs that they are for. Perform the instructions described in the subtopics listed below after you install the current Siebel Fix Pack, as described in Siebel Fix Pack Installation Instructions on page 82. NOTE: For more information about activities performed in Siebel Tools, including importing archive (.sif) files, see Using Siebel Tools and Configuring Siebel Business Applications. For more information about activities performed in the Siebel application, see Siebel Applications Administration Guide and related books. These guides are available on the Siebel 8.1 Bookshelf on OTN at http:// www.oracle.com/technology/documentation/siebel.html. This topic contains the following subtopics: Instructions for ACR 484 on page 21 Instructions for ACR 495 on page 21 Instructions for ACR 525 on page 22 Instructions for ACR 600 on page 27 Instructions for ACR 604 on page 51 Instructions for ACR 633 on page 52 Instructions for ACR 713 on page 56
Instructions for ACR 484

For information about how to install and configure ACR 484, and for more detailed information about ACR 484s functionality, see Siebel Field Service Integration to Oracle Real-Time Scheduler Installation and Administration Guide and Siebel Field Service Integration to Oracle Real-Time Scheduler Implementation Guide on the Siebel Bookshelf.

For information about how to implement ACR 495, within My Oracle Support, navigate to the Knowledge tab and search for Article ID 1270141.1.
21

The following topic contains information about how to install and configure ACR 525.
Preinstallation Tasks for ACR 525

Before you install ACR 525, review the information in the Siebel Maintenance Release Guide, Version 8.1.1.5 (this document) and in the Siebel Maintenance Release Guide, Version 8.1.1.x (which includes information about the Siebel 8.1.1.1 through 8.1.1.4 releases). Siebel Fix Pack 8.1.1.x releases are cumulative and include all fixes included in previous Siebel Fix Pack 8.1.1.x releases (where applicable). You can install the latest Siebel Fix Pack 8.1.1.x release on top of version 8.1.1 or any prior version 8.1.1.x release. For more information about installing Siebel Fix Packs, see Siebel Fix Pack Installation Instructions on page 82. Verify the patch updates in the base.txt and upgrade.txt files and review the currently installed patchset. The currently installed Fix Pack or Quick Fix is listed in the file as <Version Number><quick fix release><date - time of installation>.
Installing ACR 525

1 2 3 4 5 6
Navigate to <Tools Install directory>\REPPATCH\ACR525.zip, and unzip the ACR525.zip folder. Navigate to <Tools Install directory>\REPPATCH\ACR525\Projects_Lock_forImport.txt, and lock the projects listed in the text file. Navigate to <Tools Install directory>\REPPATCH \ACR525\REPOSITORY\Import.bat, open the file, edit the file as required, and save it. In the tools.cfg file, change the symbolic string prefix to SBL_. Double-click on the Import.bat file to execute it. After you have imported the SIF files, log into Siebel Tools > Object Explorer > Table, and do the following:
a b c 7
Query for all the changed objects and select them. Click the Apply/DDL button to apply the changes to the physical database. Click Apply and then click OK.
Provide the following credentials when connecting to the database:

Database user= <Table Owner name> Database user password= <dependent on the DB> ODBC data source= <DSN Name> (create the DSN if you receive the "TNS not resolved error message")
8 9
If the Siebel Server is running, stop it. Navigate to <Tools Install directory>\REPPATCH\ACR525\Projects_Lock_forCompile.txt, and compile the projects listed in that file. Make sure that there are 49 projects to compile.
22
Updating EIM Files for ACR 525

As part of the ACR525 release, the eim45.sql and eim_export_lookup_bu_name.sql EIM files have undergone a change. The REPPATCH\VACR525\Repository\Table\EIM\eim45.sql and REPPATCH\VACR525\Repository\Table\EIM\eim_export_lookup_bu_name.sql files contain changes required for ACR 525 and have to be merged to the files in the following locations in the Siebel Server directory:

eim45.sql: <Installation Location>\SERVER\siebsrvr\SQLTEMPL eim_export_lookup_bu_name.sql : <Installation Location>\SERVER\siebsrvr\ADMIN
Importing Seed Data for ACR 525

Use the following procedure to import seed data.
Run the following command: <Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>\REPATCH\ACR525\SEED_DATA\ACR525_Seed.dat /l <Tools Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q -1 /w n /e y /t n /x R /n 100 /h log <Tools Install Directory> - Replace with your Siebel Tools install directory.
2 3 4
Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import completed successfully. Depending upon the language that you are installing, complete either Step a or Step b. If you are installing ENU, do the following:
Run the following command after importing the VACR502_Seed.dat file. <Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>\REPATCH\ACR525\SEED_DATA\ACR525_Seed_Locale_ENU.dat /l <Tools Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner /q -1 /w n / e y /t n /x R /n 100 /h log <Tools Install Directory> - Replace with your Tools install directory.
If you are installing a language other than ENU, do the following:
Run the following command after importing ACR525_Seed.dat to import the locale specific ACR525_Seed_Locale_XXX.dat, where XXX is the language code. <Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>\REPATCH\ACR525\SEED_DATA\XXX\ ACR525_Seed_Locale_XXX.dat /l <Tools Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q 1 /w n /e y /t n /x R /n 100 /h log <Tools Install Directory> - Replace with your Siebel Tools install directory.
Start the Siebel Server and log into the Siebel application.
23
Importing XML Files for ACR 525

1 2 3
Navigate to Administration - Application > Data Map Administration, and click the applet-level menu on the top list applet to access the XML import option. Navigate to <Tools Install Directory>\REPATCH\ACR525\DataMaps\WMS_DataMapObjects13.XML, and import the XML file. After import, query on the same list applet with Source Business Object = *WMS* and verify that thirteen records appear. Thirteen records should appear.
Creating View Links for ACR 525

1 2
Navigate to Administration - Application > View Links and query for 'Warranty Claims' in the top list applet. In the Warranty Claims link, create two new records in the middle View Links list applet with the following values: First record:

Sequence = 1 Active = Y Name = My Claims Description = My Claims View = eAuto WMS Warranty Claim - My Claims View
Second record:

Sequence = 2 Active = Y Name = All Claims Description = All Claims View = eAuto WMS Warranty Claim - All Claims View
Creating Signals for ACR 525

1 2 3 4
Navigate to Administration - Order Management > Signals and query for Signal Name = 'SetFieldValue'. Check Locked Flag to Y. Navigate to the bottom list applet and drill down on Work Space. In the Action tab, create a record with the following values:

Sequence: 1 Service Type: Workflow
24
Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name Mode: Warranty Claim Instance Type: Line Item Fields: Part Name Active: Y
In the Parameters applet, add the following:
Name CPScope RowScope SubPSPWFName Variable Map - Context Variable Map - Row Set
Value Whole Selected Basic Pricing Procedure Warranty Claim Part Pricing Variable Map Context Warranty Claim Part Pricing Variable Map Row Set
In the Action tab, create a record with the following values:

Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name Mode: Work Order Instance Type: Line Item Fields: Part Name Active: Y
In the Parameters applet, add the following:
Name CPScope RowScope SubPSPWFName
Value Whole Selected Basic Pricing Procedure
25
Name Variable Map - Context Variable Map - Row Set
Value Work Order Part Pricing Variable Map Context Work Order Part Pricing Variable Map - Row Set
8 9
After you have created the new records, click the Signals link to navigate to the Signals view, and click Release New Version on the top list applet. Navigate to the applet-level menu and clear the cache.
10 Create a new signal with the following values:

Signal Name: ReviseSupplierWarrantyPolicy Description: Supplier Warranty Policy Revise Copy
11 Set the Locked flag to Y. 12 Save the record. 13 Drill down on Work Space in the bottom list applet. 14 In the Action tab, create a record with the following values:

Sequence: 1 Service Type: Business Service Service Name: FINS Data Transfer Utilities Service Method: DataTransfer Application Name Mode: Supplier Policy Instance Type: Header Active: Y
15 In the Parameters applet, add the following:
Name SharedGlobalDestId Option Operation DataMapObj
Value Y /BatchMode Insert ReviseSupplierWarrantyPolicy
16 In the Action tab, create a record with the following values:

Sequence: 2 Service Type: Business Service
26
Service Name: ISS Copy Service Service Method: RefreshBCFromInstance Application Name Mode: Supplier Policy Instance Type: Header Active: Y
17 In the Parameters applet, add the following:
Name BusCompName InstanceName TargetRowIDSharedGlobal
Value eAuto WMS Supplier Warranty Policy ISS Instance DTUSharedGlobalDestId
CAUTION: It is important to set the sequence numbers as stated in Step 14 and Step 16.
18 After you have created the new records, click the Signals link to navigate to the Signals view,
and click Release New Version on the top list applet.
19 Navigate to the applet-level menu and clear the cache. 20 Restart the Siebel Server.

Use the instructions in the following sections to implement ACR 600.

Use the following procedure to import the seed data for ACR 600.
To import the seed data for ACR 600 1

Create an ODBC entry for the database where you plan to import the seed data:
a b c d
Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC), navigate to the System DSN tab, and click Add. Select the "SQL server" driver for the MSSQL database. Enter a data source name (such as DevelopmentDB). Enter the server name to connect to:
For Oracle enter the TNS service name that you created to connect Siebel Tools to the database.
Test your connection and click OK when tested successfully.
27
Navigate to the directory where you installed Siebel Tools and change the directory to REPPATCH\ACR600. NOTE: Before executing the next step, make sure that the dataimp.exe file exists in the <Tools Install Directory>/bin directory.
Run the following command: <Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install irectory>\REPATCH\ACR600\SeedData\SeedInp_Files\ACR600_Seed.dat /l <Tools Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools Install Directory>\REPATCH\ACR600\SeedData\SeedInp_Files \<Database Platform>\ACR600_Seed.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 Step 1. <Database Platform> - Replace with your database platform (Oracle, DB2UDB, or MSSQL). NOTE: For the MSSQL database, the default table owner is "dbo" (lower-case letters).
4 5 6
Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import completed successfully. Depending on the language you are installing, follow either For ENU, do the following:
Run the following command after importing the ACR600_Seed.dat file. <Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>\REPATCH\ACR600\SeedData\ACR600_SEED\ACR600_Seed_Locale_ENU.dat /l <Tools Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools Install Directory>\REPATCH\ACR600\SeedData\ACR600_SEED \<Database Platform>\ ACR600_Seed_Locale_ENU.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 Step 1. <Database Platform> - Replace with your database platform (Oracle, DB2UDB, or MSSQL).
b 7
Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import completed successfully.
For languages other than ENU, do the following:
Run the following command after importing ACR600_Seed.dat file for importing the locale specific ACR600_Seed_Locale_XXX.dat, where XXX is the language code. <Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>\REPATCH\ACR600\SeedData\ACR600_SEED\seed_locale_XXX.dat /l <Tools Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q 1 /w n /e y /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 Step 1.
28
Importing SIF Files for ACR 600

Use the following procedure to import the SIF files for ACR 600.
To import the SIF files for ACR 600 1 2 3

Extract the ACR600RepSeedFilesv811.zip file and copy the folder installed in <Tools_Installed_Loc>\REPPATCH. Create a log folder under the ACR600 folder. Update the import.bat file with the following information:

SET TOOLSPATH = <Tools_Path> SET DATASRC = <Data Src> SET USERNAME = <User Name> SET PASSWORD = <Password>
Run the .bat file.
Updating the Siebel.ini File for Solaris

1 2 3
Install the base build. Download the Siebel_Enterprise_Server folder. Set "OverwriteConfig = yes" in siebel.ini file under ..\<Build_Folder>\Release\Windows\Server\Siebel_Enterprise_Server folder and ..\<Build_Folder>\Release\Windows\Server\Siebel_Enterprise_Server\enu folder (in both the siebel.ini file) Append the below swt files information detailed below in the same siebel.ini file in the ..\<Build_Folder>\Release\Windows\Server\Siebel_Enterprise_Server folder only. NOTE: Add the new entries under [DeleteFiles.Unix.SunOS]. You must create this entry, as it does not exist. [DeleteFiles.Unix.SunOS] File1 = $(SiebelRoot)/siebsrvr/lib/libsscmgen.so
File2 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletActivityGanttChart.swt File3 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletAdvancedSearch.swt File4 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletBottomStd.swt File5 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletCalendarDaily.swt File6 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletCalendarDailyPortal.swt
29
File7 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletCalendarMonthly.swt File8 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletCalendarService.swt File9 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletCalendarWeekly.swt File10 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletChart.swt File11 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletChartTOC.swt File12 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletDashboard.swt File13 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletFind.swt File14 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletForm1Col_B_E_N.swt File15 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletForm1ColLight_B_E_N.swt File16 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletForm4Col_B.swt File17 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletForm4Col_E_N.swt File18 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletFormPlain.swt File19 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletFormSearchTop.swt File20 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletGanttChart.swt File21 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletHead.swt File22 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletItemsDisplayed.swt File23 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletLayoutControls.swt File24 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletList_B_EL.swt File25 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletList_E_N_Q.swt File26 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletListBasicHeaderless.swt File27 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletListInverted.swt File28 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletListMessage.swt File29 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletListPortal.swt File30 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletListPortalGraphical.swt File31 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletListPortalHeaderless.swt File32 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletListSearchResults.swt File33 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletListTitleless.swt File34 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletListTotals_B_EL.swt File35 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletSalutation.swt File36 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletSalutationGraphical.swt File37 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletScreenLinks.swt
30
File38 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletSearchAdvanced.swt File39 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletSearchBasic.swt File40 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletSearchFind.swt File41 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletSendEmailPick.swt File42 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletSendMail.swt File43 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletSpellCheck.swt File44 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletTail.swt File45 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletTree.swt File46 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletTree2.swt File47 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletTreeMarketing.swt File48 = $(SiebelRoot)/siebsrvr/webtempl/CCBottomApplet.swt File49 = $(SiebelRoot)/siebsrvr/webtempl/CCCalendarAppletTitleGraphical.swt File50 = $(SiebelRoot)/siebsrvr/webtempl/CCCalendarMonthly_weekday.swt File51 = $(SiebelRoot)/siebsrvr/webtempl/CCCalendarMonthly_weekend.swt File52 = $(SiebelRoot)/siebsrvr/webtempl/CCChartBasic.swt File53 = $(SiebelRoot)/siebsrvr/webtempl/CCError.swt File54 = $(SiebelRoot)/siebsrvr/webtempl/CCForm1ColBody.swt File55 = $(SiebelRoot)/siebsrvr/webtempl/CCForm1ColBodyLight.swt File56 = $(SiebelRoot)/siebsrvr/webtempl/CCForm4ColBody.swt File57 = $(SiebelRoot)/siebsrvr/webtempl/CCFormBaseTitle.swt File58 = $(SiebelRoot)/siebsrvr/webtempl/CCFormBody.swt File59 = $(SiebelRoot)/siebsrvr/webtempl/CCFormButtonsBottom.swt File60 = $(SiebelRoot)/siebsrvr/webtempl/CCFormButtonsTop.swt File61 = $(SiebelRoot)/siebsrvr/webtempl/CCFormEditTitle.swt File62 = $(SiebelRoot)/siebsrvr/webtempl/CCFormSearch.swt File63 = $(SiebelRoot)/siebsrvr/webtempl/CCFrameBanner.swt File64 = $(SiebelRoot)/siebsrvr/webtempl/CCFrameViewbar.swt File65 = $(SiebelRoot)/siebsrvr/webtempl/CCGanttAppletTitle.swt File66 = $(SiebelRoot)/siebsrvr/webtempl/CCLayoutButtons.swt File67 = $(SiebelRoot)/siebsrvr/webtempl/CCList4ColBody.swt File68 = $(SiebelRoot)/siebsrvr/webtempl/CCListBody.swt
31
File69 = $(SiebelRoot)/siebsrvr/webtempl/CCListBodyBullet.swt File70 = $(SiebelRoot)/siebsrvr/webtempl/CCListBodyInverted.swt File71 = $(SiebelRoot)/siebsrvr/webtempl/CCListBodyNoRowHilite.swt File72 = $(SiebelRoot)/siebsrvr/webtempl/CCListBodyTotals.swt File73 = $(SiebelRoot)/siebsrvr/webtempl/CCListBodyTotalsNoRowHilite.swt File74 = $(SiebelRoot)/siebsrvr/webtempl/CCListButtonsTop.swt File75 = $(SiebelRoot)/siebsrvr/webtempl/CCListButtonsTopNoRecNav.swt File76 = $(SiebelRoot)/siebsrvr/webtempl/CCListHeader.swt File77 = $(SiebelRoot)/siebsrvr/webtempl/CCListHeaderNoSort.swt File78 = $(SiebelRoot)/siebsrvr/webtempl/CCListHeaderTotals.swt File79 = $(SiebelRoot)/siebsrvr/webtempl/CCListTitle.swt File80 = $(SiebelRoot)/siebsrvr/webtempl/CCListTitlePortal.swt File81 = $(SiebelRoot)/siebsrvr/webtempl/CCListTitlePortalGraphical.swt File82 = $(SiebelRoot)/siebsrvr/webtempl/CCPageContainer_NoFrames.swt File83 = $(SiebelRoot)/siebsrvr/webtempl/CCPopupButtonsBottom.swt File84 = $(SiebelRoot)/siebsrvr/webtempl/CCPopupForm.swt File85 = $(SiebelRoot)/siebsrvr/webtempl/CCPopupList.swt File86 = $(SiebelRoot)/siebsrvr/webtempl/CCPopupQuery.swt File87 = $(SiebelRoot)/siebsrvr/webtempl/CCRuleEditInsertionList.swt File88 = $(SiebelRoot)/siebsrvr/webtempl/CCRuleEditStatement.swt File89 = $(SiebelRoot)/siebsrvr/webtempl/CCScreenbar_Tabs.swt File90 = $(SiebelRoot)/siebsrvr/webtempl/CCScreenLinks.swt File91 = $(SiebelRoot)/siebsrvr/webtempl/CCSendSMS.swt File92 = $(SiebelRoot)/siebsrvr/webtempl/CCSiteMap.swt File93 = $(SiebelRoot)/siebsrvr/webtempl/CCSmartScriptPlayerApplet.swt File94 = $(SiebelRoot)/siebsrvr/webtempl/CCSubViewbar_Drop.swt File95 = $(SiebelRoot)/siebsrvr/webtempl/CCSubViewbar_Tabs.swt File96 = $(SiebelRoot)/siebsrvr/webtempl/CCThreadbar.swt File97 = $(SiebelRoot)/siebsrvr/webtempl/CCTogglebar_drop.swt File98 = $(SiebelRoot)/siebsrvr/webtempl/CCTogglebar_drop2.swt File99 = $(SiebelRoot)/siebsrvr/webtempl/CCTogglebar_Tabs.swt
32
File100 = $(SiebelRoot)/siebsrvr/webtempl/CCView_1Over2Over1.swt File101 = $(SiebelRoot)/siebsrvr/webtempl/CCView_25_50_25.swt File102 = $(SiebelRoot)/siebsrvr/webtempl/CCView_25_75.swt File103 = $(SiebelRoot)/siebsrvr/webtempl/CCView_25_75_Framed.swt File104 = $(SiebelRoot)/siebsrvr/webtempl/CCView_25_75_Framed2.swt File105 = $(SiebelRoot)/siebsrvr/webtempl/CCView_33_66.swt File106 = $(SiebelRoot)/siebsrvr/webtempl/CCView_50_50.swt File107 = $(SiebelRoot)/siebsrvr/webtempl/CCView_66_33.swt File108 = $(SiebelRoot)/siebsrvr/webtempl/CCView_Search.swt File109 = $(SiebelRoot)/siebsrvr/webtempl/CCViewAdmin1.swt File110 = $(SiebelRoot)/siebsrvr/webtempl/CCViewbar_Tabs.swt File111 = $(SiebelRoot)/siebsrvr/webtempl/CCViewbarAll_Tabs.swt File112 = $(SiebelRoot)/siebsrvr/webtempl/CCViewBasic.swt File113 = $(SiebelRoot)/siebsrvr/webtempl/CCViewCatalog.swt File114 = $(SiebelRoot)/siebsrvr/webtempl/CCViewDetail.swt File115 = $(SiebelRoot)/siebsrvr/webtempl/CCViewDetail2.swt File116 = $(SiebelRoot)/siebsrvr/webtempl/CCViewDetail2_ParentPntr.swt File117 = $(SiebelRoot)/siebsrvr/webtempl/CCViewDetail3.swt File118 = $(SiebelRoot)/siebsrvr/webtempl/CCViewDetail3MultiChild.swt File119 = $(SiebelRoot)/siebsrvr/webtempl/CCViewDetail_GrndchldIndnt.swt File120 = $(SiebelRoot)/siebsrvr/webtempl/CCViewDetail_ParentPntr.swt File121 = $(SiebelRoot)/siebsrvr/webtempl/CCViewDetailMultiChild.swt File122 = $(SiebelRoot)/siebsrvr/webtempl/CCViewTree.swt File123 = $(SiebelRoot)/siebsrvr/webtempl/CCViewTree2.swt File124 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletForm1Col.swt File125 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletForm2Col.swt File126 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletForm4ColMerged_B_E_N.swt File127 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletFormBase1Col.swt File128 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletFormBase2Col.swt File129 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletFormBasic.swt File130 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletFormItemDetail.swt
33
File131 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletLicenseBase1Col.swt File132 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletLinks.swt File133 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletLinks2.swt File134 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletLinksBorder.swt File135 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletLinksNoTitle.swt File136 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListBriefBullet.swt File137 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListBriefBulletBorder.swt File138 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListBriefBulletShaded.swt File139 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListBriefImgBullet.swt File140 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListBriefImgBullet2.swt File141 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListBriefImgBulletBorder.swt File142 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListBriefImgBulletShaded.swt File143 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListCategorizedBullet.swt File144 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListCategorizedBulletTab.swt File145 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListCategorizedTab.swt File146 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListCategorizedTOC.swt File147 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListDetailedImgBullet.swt File148 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListDetailedImgBulletRecNav2.swt File149 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListDetailedImgBulletRecNav.swt File150 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListHorizontal.swt File151 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListLight.swt File152 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListMerged_B_EL.swt File153 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListMessage.swt File154 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListSearchResults.swt File155 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListSubCategory_1PerRow.swt File156 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListSubCategory_4PerColumn.swt File157 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListSubCategory_6PerColumn.swt File158 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListSubCategoryIndented.swt File159 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListTabbed.swt File160 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletPSearchHead.swt File161 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletPSearchTail.swt
34
File162 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletSearchAdvanced.swt File163 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletSearchBasic.swt File164 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletSearchFind.swt File165 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletSearchTop.swt File166 = $(SiebelRoot)/siebsrvr/webtempl/dCCForm1Col.swt File167 = $(SiebelRoot)/siebsrvr/webtempl/dCCForm2Col.swt File168 = $(SiebelRoot)/siebsrvr/webtempl/dCCForm4ColBody.swt File169 = $(SiebelRoot)/siebsrvr/webtempl/dCCFormButtonsBottom.swt File170 = $(SiebelRoot)/siebsrvr/webtempl/dCCFormButtonsTopWithTitle.swt File171 = $(SiebelRoot)/siebsrvr/webtempl/dCCFormItemDetail.swt File172 = $(SiebelRoot)/siebsrvr/webtempl/dCCFormSearch.swt File173 = $(SiebelRoot)/siebsrvr/webtempl/dCCFormTotals.swt File174 = $(SiebelRoot)/siebsrvr/webtempl/dCCFrameBanner.swt File175 = $(SiebelRoot)/siebsrvr/webtempl/dCCFrameScreenbar.swt File176 = $(SiebelRoot)/siebsrvr/webtempl/dCCFrameViewbar.swt File177 = $(SiebelRoot)/siebsrvr/webtempl/dCCFrameViewbar_Hybrid.swt File178 = $(SiebelRoot)/siebsrvr/webtempl/dCCListBodyBullet.swt File179 = $(SiebelRoot)/siebsrvr/webtempl/dCCListBodyHorizontal.swt File180 = $(SiebelRoot)/siebsrvr/webtempl/dCCListBodyImgBullet.swt File181 = $(SiebelRoot)/siebsrvr/webtempl/dCCListBodyImgBulletDetailed.swt File182 = $(SiebelRoot)/siebsrvr/webtempl/dCCListBodyImgBulletDetailed2.swt File183 = $(SiebelRoot)/siebsrvr/webtempl/dCCListButtonsTopWithTitle.swt File184 = $(SiebelRoot)/siebsrvr/webtempl/dCCListCategorized.swt File185 = $(SiebelRoot)/siebsrvr/webtempl/dCCListHeader.swt File186 = $(SiebelRoot)/siebsrvr/webtempl/dCCListTitle.swt File187 = $(SiebelRoot)/siebsrvr/webtempl/dCCListTitleNoRule.swt File188 = $(SiebelRoot)/siebsrvr/webtempl/dCCPageContainer.swt File189 = $(SiebelRoot)/siebsrvr/webtempl/dCCPageContainer_NoFrames.swt File190 = $(SiebelRoot)/siebsrvr/webtempl/dCCScreenbar_Tabs.swt File191 = $(SiebelRoot)/siebsrvr/webtempl/dCCSubViewbar_Drop.swt File192 = $(SiebelRoot)/siebsrvr/webtempl/dCCSubViewbar_Tabs.swt
35
File193 = $(SiebelRoot)/siebsrvr/webtempl/dCCTogglebar_Tabs.swt File194 = $(SiebelRoot)/siebsrvr/webtempl/dCCView_100_66_33_100.swt File195 = $(SiebelRoot)/siebsrvr/webtempl/dCCView_25_50_25.swt File196 = $(SiebelRoot)/siebsrvr/webtempl/dCCView_25_75.swt File197 = $(SiebelRoot)/siebsrvr/webtempl/dCCView_25_75_Framed.swt File198 = $(SiebelRoot)/siebsrvr/webtempl/dCCView_50_50.swt File199 = $(SiebelRoot)/siebsrvr/webtempl/dCCView_66_33.swt File200 = $(SiebelRoot)/siebsrvr/webtempl/dCCView_75_25.swt File201 = $(SiebelRoot)/siebsrvr/webtempl/dCCView_Basic.swt File202 = $(SiebelRoot)/siebsrvr/webtempl/dCCViewAdmin1.swt File203 = $(SiebelRoot)/siebsrvr/webtempl/dCCViewbar_Tabs.swt File204 = $(SiebelRoot)/siebsrvr/webtempl/dCCViewDetail.swt File205 = $(SiebelRoot)/siebsrvr/webtempl/dCCViewDetail2.swt File206 = $(SiebelRoot)/siebsrvr/webtempl/dCCViewDetailMultiChild.swt File207 = $(SiebelRoot)/siebsrvr/webtempl/eCfgAttributeComboBox.swt File208 = $(SiebelRoot)/siebsrvr/webtempl/eCfgAttributeList.swt File209 = $(SiebelRoot)/siebsrvr/webtempl/eCfgBasketBox.swt File210 = $(SiebelRoot)/siebsrvr/webtempl/eCfgClassNode.swt File211 = $(SiebelRoot)/siebsrvr/webtempl/eCfgCompAttributeEdit.swt File212 = $(SiebelRoot)/siebsrvr/webtempl/eCfgCxProdNav.swt File213 = $(SiebelRoot)/siebsrvr/webtempl/eCfgCxProdNav_UiPicker.swt File214 = $(SiebelRoot)/siebsrvr/webtempl/eCfgCxProdNavAttributes.swt File215 = $(SiebelRoot)/siebsrvr/webtempl/eCfgCxProdNavClasses.swt File216 = $(SiebelRoot)/siebsrvr/webtempl/eCfgCxProdNavConnectedProducts.swt File217 = $(SiebelRoot)/siebsrvr/webtempl/eCfgCxProdNavLinks.swt File218 = $(SiebelRoot)/siebsrvr/webtempl/eCfgCxProdNavRelationships.swt File219 = $(SiebelRoot)/siebsrvr/webtempl/eCfgCxProdNavResources.swt File220 = $(SiebelRoot)/siebsrvr/webtempl/eCfgLinkedItem.swt File221 = $(SiebelRoot)/siebsrvr/webtempl/eCfgObj_Status_Conflict.swt File222 = $(SiebelRoot)/siebsrvr/webtempl/eCfgObj_Status_Error_Info.swt File223 = $(SiebelRoot)/siebsrvr/webtempl/eCfgPort_Header.swt
36
File224 = $(SiebelRoot)/siebsrvr/webtempl/eCfgResource.swt File225 = $(SiebelRoot)/siebsrvr/webtempl/eCfgSaveFavoritesPopup.swt File226 = $(SiebelRoot)/siebsrvr/webtempl/eCfgTabBasket.swt File227 = $(SiebelRoot)/siebsrvr/webtempl/eCfgView_Decorations.swt File228 = $(SiebelRoot)/siebsrvr/webtempl/eCollabAckApplet.swt File229 = $(SiebelRoot)/siebsrvr/webtempl/eCollabHiddenApplet.swt File230 = $(SiebelRoot)/siebsrvr/webtempl/EmailRespAppletInboundMsg.swt File231 = $(SiebelRoot)/siebsrvr/webtempl/EmailRespAppletOutboundMsg.swt File232 = $(SiebelRoot)/siebsrvr/webtempl/EmailRespFormButtonsBottom.swt File233 = $(SiebelRoot)/siebsrvr/webtempl/EmailRespFormInBound.swt File234 = $(SiebelRoot)/siebsrvr/webtempl/EmailRespFormOutBound.swt File235 = $(SiebelRoot)/siebsrvr/webtempl/ePortalAppletEdit.swt File236 = $(SiebelRoot)/siebsrvr/webtempl/ePortalAppletFormBasic.swt File237 = $(SiebelRoot)/siebsrvr/webtempl/ePortalAppletListTinyHeaderless.swt File238 = $(SiebelRoot)/siebsrvr/webtempl/ePortalAppletTitle.swt File239 = $(SiebelRoot)/siebsrvr/webtempl/ePortalBriefingHeaderApplet.swt File240 = $(SiebelRoot)/siebsrvr/webtempl/ePortalCalendarAppletTitle.swt File241 = $(SiebelRoot)/siebsrvr/webtempl/ePortalCalendarDaily.swt File242 = $(SiebelRoot)/siebsrvr/webtempl/ePortalCompanySearchFormApplet.swt File243 = $(SiebelRoot)/siebsrvr/webtempl/ePortalDeptSectionsApplet.swt File244 = $(SiebelRoot)/siebsrvr/webtempl/ePortalDeptView.swt File245 = $(SiebelRoot)/siebsrvr/webtempl/ePortalEmbeddedContainerPage.swt File246 = $(SiebelRoot)/siebsrvr/webtempl/ePortalError.swt File247 = $(SiebelRoot)/siebsrvr/webtempl/ePortalFullListApplet.swt File248 = $(SiebelRoot)/siebsrvr/webtempl/ePortalHomeView.swt File249 = $(SiebelRoot)/siebsrvr/webtempl/ePortalLinkListApplet.swt File250 = $(SiebelRoot)/siebsrvr/webtempl/ePortalLitListApplet.swt File251 = $(SiebelRoot)/siebsrvr/webtempl/ePortalNavBarApplet.swt File252 = $(SiebelRoot)/siebsrvr/webtempl/ePortalPageContainer.swt File253 = $(SiebelRoot)/siebsrvr/webtempl/ePortalQuickPicksApplet.swt File254 = $(SiebelRoot)/siebsrvr/webtempl/ePortalSearchApplet.swt
37
File255 = $(SiebelRoot)/siebsrvr/webtempl/ePortalSimpleListApplet.swt File256 = $(SiebelRoot)/siebsrvr/webtempl/ePortalSplashApplet.swt File257 = $(SiebelRoot)/siebsrvr/webtempl/ePortalTickerSearchFormApplet.swt File258 = $(SiebelRoot)/siebsrvr/webtempl/ePortalTOCApplet.swt File259 = $(SiebelRoot)/siebsrvr/webtempl/ePortalTopUrlApplet.swt File260 = $(SiebelRoot)/siebsrvr/webtempl/ePortalURLApplet.swt File261 = $(SiebelRoot)/siebsrvr/webtempl/ePortalWeatherSearchFormApplet.swt File262 = $(SiebelRoot)/siebsrvr/webtempl/eSalesAppletFormItemDetail.swt File263 = $(SiebelRoot)/siebsrvr/webtempl/eSalesConfigApplet10.swt File264 = $(SiebelRoot)/siebsrvr/webtempl/eSalesView_100_25_75_100.swt File265 = $(SiebelRoot)/siebsrvr/webtempl/eServiceNewButtonApplet.swt File266 = $(SiebelRoot)/siebsrvr/webtempl/eWirelessPageTabLayoutEdit.swt File267 = $(SiebelRoot)/siebsrvr/webtempl/ICAppletList.swt File268 = $(SiebelRoot)/siebsrvr/webtempl/ICAppletListCategorizedBulletTab.swt File269 = $(SiebelRoot)/siebsrvr/webtempl/ICCurrentCategoryApplet.swt File270 = $(SiebelRoot)/siebsrvr/webtempl/ICListCategorized.swt File271 = $(SiebelRoot)/siebsrvr/webtempl/SIAppletTitle.swt File272 = $(SiebelRoot)/siebsrvr/webtempl/SIBriefingHeaderApplet.swt File273 = $(SiebelRoot)/siebsrvr/webtempl/SIBriefingListApplet.swt File274 = $(SiebelRoot)/siebsrvr/webtempl/SIBriefingView.swt File275 = $(SiebelRoot)/siebsrvr/webtempl/SILinkListApplet.swt File276 = $(SiebelRoot)/siebsrvr/webtempl/SIMyBriefingView.swt File277 = $(SiebelRoot)/siebsrvr/webtempl/SIPlainApplet.swt File278 = $(SiebelRoot)/siebsrvr/webtempl/SISalutationApplet.swt File279 = $(SiebelRoot)/siebsrvr/webtempl/SISwoopTitle.swt File280 = $(SiebelRoot)/siebsrvr/webtempl/SISynchronizeApplet.swt File281 = $(SiebelRoot)/siebsrvr/webtempl/SITOCApplet.swt File282 = $(SiebelRoot)/siebsrvr/webtempl/SITrackingProfileHeaderApplet.swt File283 = $(SiebelRoot)/siebsrvr/webtempl/SITrackingProfileReviewView.swt File284 = $(SiebelRoot)/siebsrvr/webtempl/SIUrlApplet.swt File285 = $(SiebelRoot)/siebsrvr/webtempl/SWELogin.swt
38
File286 = $(SiebelRoot)/siebsrvr/webtempl/ToolsForm.swt File287 = $(SiebelRoot)/siebsrvr/webtempl/ToolsList.swt File288 = $(SiebelRoot)/siebsrvr/webtempl/ToolsUnmapped.swt File289 = $(SiebelRoot)/siebsrvr/webtempl/TrainingTestApplet.swt File290 = $(SiebelRoot)/siebsrvr/webtempl/TrainingTestResultApplet.swt File291 = $(SiebelRoot)/siebsrvr/webtempl/CCCalendarAppletTitle.swt File292 = $(SiebelRoot)/siebsrvr/webtempl/CCViewSegmentDetail.swt File293 = $(SiebelRoot)/siebsrvr/webtempl/CCViewDashboard.swt File294 = $(SiebelRoot)/siebsrvr/webtempl/eCfgObj_GlobalSignal.swt File295 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletGanttChartPortal.swt File296 = $(SiebelRoot)/siebsrvr/webtempl/CCLayoutTitlePortal.swt File297 = $(SiebelRoot)/siebsrvr/webtempl/eCfgBaseAutoReprice.swt File298 = $(SiebelRoot)/siebsrvr/webtempl/eCfgBaseManualReprice.swt File299 = $(SiebelRoot)/siebsrvr/webtempl/eCfgClassNodeNoPick.swt File300 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlCheck.swt File301 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlCheckPrice.swt File302 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlCombo.swt File303 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlComboAdd.swt File304 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlComboAddPrice.swt File305 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlQuantity.swt File306 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlQuantityPrice.swt File307 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlRadio.swt File308 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlRadioPrice.swt File309 = $(SiebelRoot)/siebsrvr/webtempl/eCfgGroupStandard.swt File310 = $(SiebelRoot)/siebsrvr/webtempl/eCfgGroupSummary.swt File311 = $(SiebelRoot)/siebsrvr/webtempl/eCfgProductRawMode.swt File312 = $(SiebelRoot)/siebsrvr/webtempl/eCfgProductSingle.swt File313 = $(SiebelRoot)/siebsrvr/webtempl/eCfgProductTabs.swt File314 = $(SiebelRoot)/siebsrvr/webtempl/eCfgProductWizard.swt File315 = $(SiebelRoot)/siebsrvr/webtempl/CCViewAdmin1_GrndchldIndnt.swt File316 = $(SiebelRoot)/siebsrvr/webtempl/CCViewDetail2_GrndchldIndnt.swt
39
File317 = $(SiebelRoot)/siebsrvr/webtempl/CCViewDetail3_GrndchldIndnt.swt File318 = $(SiebelRoot)/siebsrvr/webtempl/CCViewDetail3_ParentPntr.swt File319 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletSearchAdvancedTabbed.swt File320 = $(SiebelRoot)/siebsrvr/webtempl/dCCListBodyImgBullet2.swt File321 = $(SiebelRoot)/siebsrvr/webtempl/eAuctionAppletPlaceBid.swt File322 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlAttributeText.swt File323 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlComboPrice.swt File324 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlComboPriceQuantity.swt File325 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlComboQuantity.swt File326 = $(SiebelRoot)/siebsrvr/webtempl/eCfgRelationContentsPriceQuantity.swt File327 = $(SiebelRoot)/siebsrvr/webtempl/eCfgRelationContentsQuantity.swt File328 = $(SiebelRoot)/siebsrvr/webtempl/eCfgRelationRawCombo.swt File329 = $(SiebelRoot)/siebsrvr/webtempl/eCfgViewBasic.swt File330 = $(SiebelRoot)/siebsrvr/webtempl/CCFormButtonsTopNoRecNav.swt File331 = $(SiebelRoot)/siebsrvr/webtempl/eWirelessPageTabLayt4ColBody.swt File332 = $(SiebelRoot)/siebsrvr/webtempl/CCApplet_NamedSpacer.swt File333 = $(SiebelRoot)/siebsrvr/webtempl/CCApplet_Spacer.swt File334 = $(SiebelRoot)/siebsrvr/webtempl/dCCView_25_50_25_home.swt File335 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletForm4Col_NoRecNav.swt File336 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletFormWizard.swt File337 = $(SiebelRoot)/siebsrvr/webtempl/CCTitle.swt File338 = $(SiebelRoot)/siebsrvr/webtempl/CCTitle_Mapped.swt File339 = $(SiebelRoot)/siebsrvr/webtempl/CCTitle_Portal.swt File340 = $(SiebelRoot)/siebsrvr/webtempl/CCTitle_PortalGraphical.swt File341 = $(SiebelRoot)/siebsrvr/webtempl/dCCFormButtonsTop.swt File342 = $(SiebelRoot)/siebsrvr/webtempl/dCCListButtonsTop.swt File343 = $(SiebelRoot)/siebsrvr/webtempl/dCCTitle_Mapped.swt File344 = $(SiebelRoot)/siebsrvr/webtempl/dCCTitle_Portal.swt File345 = $(SiebelRoot)/siebsrvr/webtempl/eCfgObj_DetailExplanation.swt File346 = $(SiebelRoot)/siebsrvr/webtempl/eCfgObj_GlobalDetailExpl.swt File347 = $(SiebelRoot)/siebsrvr/webtempl/eCfgPopupFrameContainer.swt
40
File348 = $(SiebelRoot)/siebsrvr/webtempl/eCfgAttributeRadio.swt File349 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListCategorizedNoTab.swt File350 = $(SiebelRoot)/siebsrvr/webtempl/dCCListBodyNoRowHilite.swt File351 = $(SiebelRoot)/siebsrvr/webtempl/dCCListBodyTotalsNoRowHilite.swt File352 = $(SiebelRoot)/siebsrvr/webtempl/dCCListHeaderTotals.swt File353 = $(SiebelRoot)/siebsrvr/webtempl/dCCTitle_RecNav.swt File354 = $(SiebelRoot)/siebsrvr/webtempl/ERMViewBasic.swt File355 = $(SiebelRoot)/siebsrvr/webtempl/ERMAppletForm4Col_B_TglBar.swt File356 = $(SiebelRoot)/siebsrvr/webtempl/ERMAppletList_B_EL_TglBar.swt File357 = $(SiebelRoot)/siebsrvr/webtempl/ERMAppletList_E_N_Q_TglBar.swt File358 = $(SiebelRoot)/siebsrvr/webtempl/ERMFormButtonsTop_TglBar.swt File359 = $(SiebelRoot)/siebsrvr/webtempl/ERMListButtonsTop_TglBar.swt File360 = $(SiebelRoot)/siebsrvr/webtempl/ERMViewBasic_TglBar.swt File361 = $(SiebelRoot)/siebsrvr/webtempl/ERMViewTree.swt File362 = $(SiebelRoot)/siebsrvr/webtempl/CCViewTree_33_66.swt File363 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletRealtimeCart.swt File364 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletSalutationGraphical.swt File365 = $(SiebelRoot)/siebsrvr/webtempl/dCCLogout.swt File366 = $(SiebelRoot)/siebsrvr/webtempl/eCfgAtt_Header.swt File367 = $(SiebelRoot)/siebsrvr/webtempl/ePortalAppletLinks2.swt File368 = $(SiebelRoot)/siebsrvr/webtempl/ePortaldCCAppletFormBasic.swt File369 = $(SiebelRoot)/siebsrvr/webtempl/ePortaldCCForm1ColBodyLight.swt File370 = $(SiebelRoot)/siebsrvr/webtempl/ERMReport_Form.swt File371 = $(SiebelRoot)/siebsrvr/webtempl/ERMReport_ListForm.swt File372 = $(SiebelRoot)/siebsrvr/webtempl/ERMReport_ListTotal.swt File373 = $(SiebelRoot)/siebsrvr/webtempl/eCfgTopLevelButtons.swt File374 = $(SiebelRoot)/siebsrvr/webtempl/ERMObjectiveListApplet.swt File375 = $(SiebelRoot)/siebsrvr/webtempl/ERMTreeForm.swt File376 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletListMerged_B_EL.swt File377 = $(SiebelRoot)/siebsrvr/webtempl/CCListButtonsTopWithTitle.swt File378 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletFormQuestionnaire.swt
41
File379 = $(SiebelRoot)/siebsrvr/webtempl/dCCScreenbar_Tabs_Hybrid.swt File380 = $(SiebelRoot)/siebsrvr/webtempl/ePortalNavBarAppletDeptPage.swt File381 = $(SiebelRoot)/siebsrvr/webtempl/ePortalQuickPicksAppletDeptPage.swt File382 = $(SiebelRoot)/siebsrvr/webtempl/CCView_50_50_Over_100_Framed.swt File383 = $(SiebelRoot)/siebsrvr/webtempl/CCViewFilterDetail.swt File384 = $(SiebelRoot)/siebsrvr/webtempl/CCViewVertical_Framed.swt File385 = $(SiebelRoot)/siebsrvr/webtempl/eCfgError.swt File386 = $(SiebelRoot)/siebsrvr/webtempl/eCfgErrorPicker.swt File387 = $(SiebelRoot)/siebsrvr/webtempl/CCCalendarView.swt File388 = $(SiebelRoot)/siebsrvr/webtempl/CCCalendarViewTabs.swt File389 = $(SiebelRoot)/siebsrvr/webtempl/ermFrameViewbar.swt File390 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletForm4Col_E_N_NoTitle.swt File391 = $(SiebelRoot)/siebsrvr/webtempl/dCCView_25_50_25_Framed.swt File392 = $(SiebelRoot)/siebsrvr/webtempl/CCPopupListButtonsTop.swt File393 = $(SiebelRoot)/siebsrvr/webtempl/eDocumentsTemplateLayout.swt File394 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletForm4ColMerged_B_E_N.swt File395 = $(SiebelRoot)/siebsrvr/webtempl/CCFormButtonsTopWithTitle.swt File396 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletHiGanttChart.swt File397 = $(SiebelRoot)/siebsrvr/webtempl/HIcalendar.swt File398 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletFilterForm4Col_E_N.swt File399 = $(SiebelRoot)/siebsrvr/webtempl/EventHIcalendar.swt File400 = $(SiebelRoot)/siebsrvr/webtempl/ERMAppletListTotals_B_EL_TglBar.swt File401 = $(SiebelRoot)/siebsrvr/webtempl/dCCListCategorized3.swt File402 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListCategorizedBulletTab3.swt File403 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletFormWithSteps.swt File404 = $(SiebelRoot)/siebsrvr/webtempl/ERMImageDescr.swt File405 = $(SiebelRoot)/siebsrvr/webtempl/CBPopupForm.swt File406 = $(SiebelRoot)/siebsrvr/webtempl/CBListButtonsHierarchy.swt File407 = $(SiebelRoot)/siebsrvr/webtempl/CBPopupListHierarchy.swt File408 = $(SiebelRoot)/siebsrvr/webtempl/dCCFormButtonsTopNoRecNav.swt File409 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletGotoURL.swt
42
File410 = $(SiebelRoot)/siebsrvr/webtempl/ERMAppletListPortalToggle.swt File411 = $(SiebelRoot)/siebsrvr/webtempl/CCPopupListAddItems.swt File412 = $(SiebelRoot)/siebsrvr/webtempl/ePortal4Up.swt File413 = $(SiebelRoot)/siebsrvr/webtempl/CCViewDetail_TglBar.swt File414 = $(SiebelRoot)/siebsrvr/webtempl/dCCPRMFrameViewbar.swt File415 = $(SiebelRoot)/siebsrvr/webtempl/ERMTopStory.swt File416 = $(SiebelRoot)/siebsrvr/webtempl/ERMTopStoryLgImg.swt File417 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuBaseAutoReprice.swt File418 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuControlCheckPrice.swt File419 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuControlQuantityPrice.swt File420 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuGroupSummary.swt File421 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuLinkedItem.swt File422 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuObj_GlobalSignal.swt File423 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuProductTheme.swt File424 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuTopLevelButtons.swt File425 = $(SiebelRoot)/siebsrvr/webtempl/eCfgObj_Status_Error_Undo.swt File426 = $(SiebelRoot)/siebsrvr/webtempl/CCViewHIC.swt File427 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletForm4Col_B_Expanded.swt File428 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletForm4Col_E_N_Expanded.swt File429 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletForm4Col_NoRecNav_Expanded.swt File430 = $(SiebelRoot)/siebsrvr/webtempl/CCForm4ColBody_Expanded.swt File431 = $(SiebelRoot)/siebsrvr/webtempl/ePortalURLAppletForm.swt File432 = $(SiebelRoot)/siebsrvr/webtempl/ePortalURLAppletInner.swt File433 = $(SiebelRoot)/siebsrvr/webtempl/CCSISOMAppletForm4Col_NoRecNavLinks.swt File434 = $(SiebelRoot)/siebsrvr/webtempl/CCSISOMForm4ColBodyLinks.swt File435 = $(SiebelRoot)/siebsrvr/webtempl/CCSISOMViewDetail2_ParentPntr.swt File436 = $(SiebelRoot)/siebsrvr/webtempl/CBAppletForm4Col_E_N_Simple.swt File437 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuAttributeRadio.swt File438 = $(SiebelRoot)/siebsrvr/webtempl/ePortalURLAppletGraphical.swt File439 = $(SiebelRoot)/siebsrvr/webtempl/CCCRAFrameViewbar.swt File440 = $(SiebelRoot)/siebsrvr/webtempl/dCCScreenbar_NSTabs.swt
43
File441 = $(SiebelRoot)/siebsrvr/webtempl/CCPopupListMvg.swt File442 = $(SiebelRoot)/siebsrvr/webtempl/CCPopupListAssoc.swt File443 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletTaskAssistantPlayer.swt File444 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletPopupFormGridLayout.swt File445 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletFormGridLayout.swt File446 = $(SiebelRoot)/siebsrvr/webtempl/CCPopupListMvgShuttleButtonsTop.swt File447 = $(SiebelRoot)/siebsrvr/webtempl/CCPopupListAssocShuttleButtonsTop.swt File448 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_CCAppletTree.swt File449 = $(SiebelRoot)/siebsrvr/webtempl/CCViewbarAll_Tabs_DropList.swt File450 = $(SiebelRoot)/siebsrvr/webtempl/CCViewbar_Tabs_DropList.swt File451 = $(SiebelRoot)/siebsrvr/webtempl/eCfgProductTabsJS.swt File452 = $(SiebelRoot)/siebsrvr/webtempl/eCfgBaseAutoRepriceJS.swt File453 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlComboAddJS.swt File454 = $(SiebelRoot)/siebsrvr/webtempl/eCfgHiddenFrame.swt File455 = $(SiebelRoot)/siebsrvr/webtempl/eCfgRelationContentsQuantityJS.swt File456 = $(SiebelRoot)/siebsrvr/webtempl/eCfgCompAttributeEditJS.swt File457 = $(SiebelRoot)/siebsrvr/webtempl/eCfgAtt_HeaderJS.swt File458 = $(SiebelRoot)/siebsrvr/webtempl/eCfgTopLevelButtonsJS.swt File459 = $(SiebelRoot)/siebsrvr/webtempl/eCfgPort_HeaderJS.swt File460 = $(SiebelRoot)/siebsrvr/webtempl/eCfgGroupStandardJS.swt File461 = $(SiebelRoot)/siebsrvr/webtempl/eCfgViewBasicJS.swt File462 = $(SiebelRoot)/siebsrvr/webtempl/eCfgObj_Status_ConflictJS.swt File463 = $(SiebelRoot)/siebsrvr/webtempl/eCfgAttributeComboBoxJS.swt File464 = $(SiebelRoot)/siebsrvr/webtempl/ERMEmpLocatorSearchFormApplet.swt File465 = $(SiebelRoot)/siebsrvr/webtempl/ERMBusinessCardFormBasic.swt File466 = $(SiebelRoot)/siebsrvr/webtempl/ERMViewResultsDetail.swt File467 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuProductThemeJS.swt File468 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuAttributeRadioJS.swt File469 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuBaseAutoRepriceJS.swt File470 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuControlQuantityPriceJS.swt File471 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuObj_GlobalSignalJS.swt
44
File472 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuTopLevelButtonsJS.swt File473 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletGanttChartActX.swt File474 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlComboJS.swt File475 = $(SiebelRoot)/siebsrvr/webtempl/CCViewChartList.swt File476 = $(SiebelRoot)/siebsrvr/webtempl/CCViewParentListWithTabs.swt File477 = $(SiebelRoot)/siebsrvr/webtempl/CCViewParentMultiChildWithTabs.swt File478 = $(SiebelRoot)/siebsrvr/webtempl/ermPortalViewbar.swt File479 = $(SiebelRoot)/siebsrvr/webtempl/ermPortalPageContainer.swt File480 = $(SiebelRoot)/siebsrvr/webtempl/ermEmbeddedFrameViewbar.swt File481 = $(SiebelRoot)/siebsrvr/webtempl/ERMIntegrationURLApplet.swt File482 = $(SiebelRoot)/siebsrvr/webtempl/dCCError.swt File483 = $(SiebelRoot)/siebsrvr/webtempl/eCfgBaseManualRepriceJS.swt File484 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlComboPriceJS.swt File485 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlComboQuantityJS.swt File486 = $(SiebelRoot)/siebsrvr/webtempl/eCfgProductRawModeJS.swt File487 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletTaskMap.swt File488 = $(SiebelRoot)/siebsrvr/webtempl/dCCTitle.swt File489 = $(SiebelRoot)/siebsrvr/webtempl/eCfgRelationContentsPriceQuantityJS.swt File490 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlComboAddPriceJS.swt File491 = $(SiebelRoot)/siebsrvr/webtempl/eCfgObj_ExplanationJS.swt File492 = $(SiebelRoot)/siebsrvr/webtempl/eCfgLinkedItemJS.swt File493 = $(SiebelRoot)/siebsrvr/webtempl/eCfgResourceJS.swt File494 = $(SiebelRoot)/siebsrvr/webtempl/eCfgObj_GlobalSignalJS.swt File495 = $(SiebelRoot)/siebsrvr/webtempl/eCfgGroupSummaryJS.swt File496 = $(SiebelRoot)/siebsrvr/webtempl/ERMListBodyTotals.swt File497 = $(SiebelRoot)/siebsrvr/webtempl/ERMAppletListTotals_TglBar.swt File498 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuGroupSummaryJS.swt File499 = $(SiebelRoot)/siebsrvr/webtempl/eCfgProductSingleJS.swt File500 = $(SiebelRoot)/siebsrvr/webtempl/eCfgProductWizardJS.swt File501 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletFormGridWizard.swt File502 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlComboPriceQuantityJS.swt
45
File503 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletListImgBulletScreenHomepage.swt File504 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletForm1ColScreenHomepage.swt File505 = $(SiebelRoot)/siebsrvr/webtempl/ERMGenericViewTree.swt File506 = $(SiebelRoot)/siebsrvr/webtempl/CCESSPlayerApplet.swt File507 = $(SiebelRoot)/siebsrvr/webtempl/ermAdminFrameBanner.swt File508 = $(SiebelRoot)/siebsrvr/webtempl/ePortalNavBarAppletDeptPage_LeftNav.swt File509 = $(SiebelRoot)/siebsrvr/webtempl/dCCView_15_60_25_home.swt File510 = $(SiebelRoot)/siebsrvr/webtempl/ERMCPRDAListApplet.swt File511 = $(SiebelRoot)/siebsrvr/webtempl/ERMCPRDAListHeader.swt File512 = $(SiebelRoot)/siebsrvr/webtempl/eCfgAttributeRadioJS.swt File513 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletCalendarGanttChartTop.swt File514 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletCalendarGC.swt File515 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletList_B_EL_NavControl.swt File516 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletPortalLinks.swt File517 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletFormPortalGraphical.swt File518 = $(SiebelRoot)/siebsrvr/webtempl/CCViewbar_Tabs_DropList_Always.swt File519 = $(SiebelRoot)/siebsrvr/webtempl/EmailRespAttachmentListButtons.swt File520 = $(SiebelRoot)/siebsrvr/webtempl/EmailRespAppletInboundAttachments.swt File521 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletScreenHomepageBanner.swt File522 = $(SiebelRoot)/siebsrvr/webtempl/dCCListBodyImgBulletScreenHomepage.swt File523 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletListImgBulletScreenHomepageWithDiv.swt File524 = $(SiebelRoot)/siebsrvr/webtempl/dCCForm1ColScreenHomepage.swt File525 = $(SiebelRoot)/siebsrvr/webtempl/dCCListBodyImgBulletScreenHomepage2.swt File526 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletGanttChartActX_Mktg.swt File527 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletAppHomepageBanner.swt File528 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuControlCheckPriceJS.swt File529 = $(SiebelRoot)/siebsrvr/webtempl/eCfg_MenuLinkedItemJS.swt File530 = $(SiebelRoot)/siebsrvr/webtempl/ermAppletListTabbedHighlight.swt File531 = $(SiebelRoot)/siebsrvr/webtempl/ermListBodyHighlight.swt File532 = $(SiebelRoot)/siebsrvr/webtempl/ICAppletForm.swt File533 = $(SiebelRoot)/siebsrvr/webtempl/ERMAppletPortalList.swt
46
File534 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletForm1ColScreenHomepageAdd.swt File535 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletForm1ColScreenHomepageSearch.swt File536 = $(SiebelRoot)/siebsrvr/webtempl/ERMAppletListNoRowHilite_B_EL.swt File537 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletListCalToDo.swt File538 = $(SiebelRoot)/siebsrvr/webtempl/eEventsEventMicrositeView.swt File539 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletDashboard_3Row.swt File540 = $(SiebelRoot)/siebsrvr/webtempl/dCCView_50_50_1.swt File541 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletLinksNoTitle1.swt File542 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListDetailedImgBulletRecNav3.swt File543 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListItemDetail.swt File544 = $(SiebelRoot)/siebsrvr/webtempl/dCCListBodyImgBulletDetailed3.swt File545 = $(SiebelRoot)/siebsrvr/webtempl/dCCListItemDetail.swt File546 = $(SiebelRoot)/siebsrvr/webtempl/dCCFormButtonsBottom_ext.swt File547 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletFormGridLayout_Extend.swt File548 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletFormBasic_ext.swt File549 = $(SiebelRoot)/siebsrvr/webtempl/ERMKPIListApplet.swt File550 = $(SiebelRoot)/siebsrvr/webtempl/ERMMMProductView.swt File551 = $(SiebelRoot)/siebsrvr/webtempl/TNTSHMHICalendar.swt File552 = $(SiebelRoot)/siebsrvr/webtempl/eCfgGroupMessagesJS.swt File553 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListImgDetailHC.swt File554 = $(SiebelRoot)/siebsrvr/webtempl/dCCAppletListImgDetailHCBody.swt File555 = $(SiebelRoot)/siebsrvr/webtempl/CCViewDetail_ShoppingCart.swt File556 = $(SiebelRoot)/siebsrvr/webtempl/eCfgObj_MessagesJS.swt File557 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletParametricSearch.swt File558 = $(SiebelRoot)/siebsrvr/webtempl/COMActiveXAppletForm.swt File559 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletFormGridLayoutNoRecNav.swt File560 = $(SiebelRoot)/siebsrvr/webtempl/eCFGViewBasicJS_ViewDetail_ShoppingCart.swt File561 = $(SiebelRoot)/siebsrvr/webtempl/CCQuickPrintPopupForm.swt File562 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletPlaybarButtons.swt File563 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletTaskPane.swt File564 = $(SiebelRoot)/siebsrvr/webtempl/TUPopupWatchWindow.swt
47
File565 = $(SiebelRoot)/siebsrvr/webtempl/CCInboxTransfer.swt File566 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlComboAddDomainPriceJS.swt File567 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlComboAddPriceAttribGridJS.swt File568 = $(SiebelRoot)/siebsrvr/webtempl/eCfgRelationContentsPriceQuantityAttribGridJS.swt File569 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlCheckPriceMultiLevelJS.swt File570 = $(SiebelRoot)/siebsrvr/webtempl/CCTaskViewTitle.swt File571 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletPlaybarTop.swt File572 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletPlaybarBottom.swt File573 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletFormGridLayout_withJS.swt File574 = $(SiebelRoot)/siebsrvr/webtempl/eCfgControlAttributeTextJS.swt File575 = $(SiebelRoot)/siebsrvr/webtempl/ccappletlist_b_el-shuttlemvg.swt File576 = $(SiebelRoot)/siebsrvr/webtempl/ccappletlist_b_el-shuttleassoc.swt File577 = $(SiebelRoot)/siebsrvr/webtempl/SavedSearch.swt File578 = $(SiebelRoot)/siebsrvr/webtempl/SearchLookin.swt File579 = $(SiebelRoot)/siebsrvr/webtempl/AdvancedSearch.swt File580 = $(SiebelRoot)/siebsrvr/webtempl/SearchPreference.swt File581 = $(SiebelRoot)/siebsrvr/webtempl/SearchResults.swt File582 = $(SiebelRoot)/siebsrvr/webtempl/Search_ListHeader.swt File583 = $(SiebelRoot)/siebsrvr/webtempl/SearchResultsFooter.swt File584 = $(SiebelRoot)/siebsrvr/webtempl/SearchHeaderResults.swt File585 = $(SiebelRoot)/siebsrvr/webtempl/SaveSearchApplet.swt File586 = $(SiebelRoot)/siebsrvr/webtempl/RefineCategoryApplet.swt File587 = $(SiebelRoot)/siebsrvr/webtempl/CCViewDetail_ParentPntr_TAQ.swt File588 = $(SiebelRoot)/siebsrvr/webtempl/Search_View.swt File589 = $(SiebelRoot)/siebsrvr/webtempl/Search_RefineCategoryApplet.swt File590 = $(SiebelRoot)/siebsrvr/webtempl/Search_Popup.swt File591 = $(SiebelRoot)/siebsrvr/webtempl/eCfgBaseAutoRepriceMultiSelectJS.swt File592 = $(SiebelRoot)/siebsrvr/webtempl/eCfgTopLevelButtonsJS_Configurator.swt File593 = $(SiebelRoot)/siebsrvr/webtempl/CCActionBar.swt File594 = $(SiebelRoot)/siebsrvr/webtempl/CCActionPane.swt File595 = $(SiebelRoot)/siebsrvr/webtempl/CCAppletReplaceQuery.swt
48
File596 = $(SiebelRoot)/siebsrvr/webtempl/SearchFindResults.swt File597 = $(SiebelRoot)/siebsrvr/webtempl/SearchFindHeaderResults.swt File598 = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/dCCmain.css File599 = $(SiebelRoot)/siebsrvr/webtempl/CCHtmlType.swf File600 = $(SiebelRoot)/siebsrvr/webtempl/dCCHtmlType.swf File601 File602 = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/clock.gif = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/voice.gif
File603 = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/ icon_accept_work_item_enabled.gif File604 = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/icon_call_enabled.gif
File605 = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/ icon_consultative_conference_enabled.gif File606 = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/ icon_consultative_transfer_enabled.gif File607 File608 = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/icon_email_enabled.gif = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/icon_fax_enabled.gif
File609 = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/ icon_hold_work_item_enabled.gif File610 = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/ icon_initiate_work_item_enabled.gif File611 File612 File613 File614 File615 = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/icon_login_enabled.gif = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/icon_logout_enabled.gif = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/icon_mute_transfer_enabled.gif = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/icon_notready_enabled.gif = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/icon_page_enabled.gif
File616 = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/ icon_release_work_item_enabled.gif File617 File618 File619 File620 File621 File622 File623 = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/icon_retrieve_enabled.gif = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/icon_webcall_enabled.gif = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/icon_fwd_wrk_itm_1_d.gif = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/icon_res_wrk_itm_1_d.gif = $(SiebelRoot)/siebsrvr/webmaster/files/%LANGUAGE%/icon_wireless_enabled.gif = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebbasicscontrols.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebbasicscontrolscal.htm
49
File624 File625 File626 File627 File628 File629 File630 File631 File632 File633
= $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebbasicscontrolscurr.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebbasicsdata.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebbasicsdatatoc.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebbasicskbshortcuts.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebbasicsnav.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebbasicsselectiondbs.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebcalendar.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebcharts.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebcomfindinginfo.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebcomgeneric.htm
File634 = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/ siebcomgenericcontactustoc.htm File635 = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/ siebcomgenericfindinginfotoc.htm File636 = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebcomgenericlogintoc.htm
File637 = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/ siebcomgenericregistrationtoc.htm File638 = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/ siebcomgenericuserinterfacetoc.htm File639 File640 File641 = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebcomloggingin.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebcomregistration.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebcomsearch.htm
File642 = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/ siebcomupdatinguserprofile.htm File643 File644 File645 File646 File647 File648 File649 File650 File651 = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebcomuserinterface.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebcomwwattachments.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebcorrespondence.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebcorrespondencetoc.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebfindinginfotoc.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebhomepage.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebhomepagetoc.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebindex.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebliterature.htm
50
File652 File653 File654 File655 File656 File657 File658 File659 File660 File661 File662 File663 File664 File665 File666 File667 File668 File669 File670 File671 File672 File673
= $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebliteraturetoc.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/sieboptions.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/sieboptionstoc.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebquery.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebquerytoc.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebreports.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebsearch.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebsearchtoc.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebstarthelp.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebuserinterfacetoc.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebusingcalendartoc.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebwelcome.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebusingtaskbasedui.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebusingtaskbaseduitoc.htm = $(SiebelRoot)/siebsrvr/webmaster/help/%LANGUAGE%/siebaccessibility.htm = $(SiebelRoot)/siebsrvr/webtempl/FINSFrameViewbar.swt = $(SiebelRoot)/siebsrvr/webtempl/FINSPageContainer.swt = $(SiebelRoot)/siebsrvr/webtempl/FINSDBLogin.swt = $(SiebelRoot)/siebsrvr/webtempl/CCAppletDashboard.swt = $(SiebelRoot)/siebsrvr/webtempl/CCFrameMsgbar.swt = $(SiebelRoot)/siebsrvr/webtempl/EmailRespFormInBoundNew.swt = $(SiebelRoot)/siebsrvr/webtempl/EmailRespFormOutBoundNew.swt

Use the instructions in this section to configure ACR 604.
Configuring the Frame Level Enhancement

Frame titles can be customized using Siebel Tools, by adding an application-level user property to the application. Multiple user properties may be specified, so that the maximum length of the user property value field is not exceeded. The user properties are in the form HTMLFramesTitle0 up to HTMLFramesTitle15. The user property values are given in the form 'FrameName1:User Title1, FrameName 2:UserTitle2'. The following table describes an example:
51
User Property Name HTMLFramesTitle0 HTMLFramesTitle1
Value _swe : My SWE ,_sweclient:MY SWE CLIENT _sweapp:My APPLICATION, _swecda:My SWE CDA, _swescrnbar:MY SCREENBAR
By default, frames are identified by a screen reader using the internal Siebel application names such as "_sweclient" unless one of the above properties has been set. This feature is applicable only in SI+ mode, with Accessibility mode turned on.
Configuring the Session Timeout Warning Enhancement

This feature offers two time parameters, both of which are specified in the eapps.cfg file. The values are specified in seconds. The following is an example: SessionTimeout = 900 (the existing parameter) SessionTimeoutWarning = 300 (the new parameter)
The Time Out Warning Period is defined as: TimeOutWarningPeriod = SessionTimeout value minus SessionTimeoutWarning value In the previous example, the timeout warning message will be displayed after 600 seconds (10 minutes) of inactivity, calculated as 900 -300 = 600 seconds.

Use the instructions in this topic to implement ACR 633 for Siebel Reports for Siebel CRM Fix Pack 8.1.1.5. For detailed information about Siebel Reports, see Siebel Reports Guide on Siebel Bookshelf.
Process of Implementing ACR 633

To implement ACR 633, perform the following tasks:
1 2 3
Applying Repository Changes for ACR 633 on page 53 Applying Schema Changes for ACR 633 on page 54 Applying Seed Data Changes for ACR 633 on page 55
52
Applying Repository Changes for ACR 633

1
Make sure that you have an existing Siebel CRM version 8.1.1 or later environment and have applied Siebel Fix Pack 8.1.1.5. For information about installing Siebel CRM, see Siebel Installation Guide for the operating system you are using. For information about installing the Fix Pack, see Siebel Fix Pack Installation Instructions on page 82.
2 3 4
Stop the Siebel Services. Copy the existing .SRF file as a backup. (First-time installation only) Edit the Siebel Tools configuration file by doing the following:
In the [Siebel] section of the tools.cfg file (in the SIEBEL_TOOLS_ROOT\BIN\ENU directory), set the SymStrPrefix parameter to SBL_. NOTE: You must change this parameter back to its original value of X_ at a later time. For more information about the SymStrPrefix parameter, see the topic on symbolic strings in Using Siebel Tools.
b 5 a
Save the tools.cfg file.
Import an archive file to apply the repository changes by doing the following: Log in to Siebel Tools, and then lock the following projects:

XMLP Integration Table XMLP Symbolic Strings Reports UI User Preferences Activity Activity (CC)
NOTE: If the XMLP Integration project is inactive, activate it by unchecking the Inactive checkbox. Additionally, if projects and objects are not locked when you import SIF files, a message appears indicating which object or project is to be locked. In such a case, lock the project or object, and then import the SIF file again.
b c
From the application-level menu, select Tools, and then the Import from Archive menu item. In the file browser dialog window, choose the appropriate BIP_8115FP.sif file from the REPPATCH directory where Siebel Tools is installed. For Siebel Business Applications, choose:
SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8115FP\HOR\REPOSITORY\BIP_8115FP.sif
For Siebel Industry Applications, choose:
SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8115FP\SIA\REPOSITORY\BIP_8115FP.sif
Follow the import wizard prompts to import the SIF file.
53
Lock the following new projects:

BIP Calendar Report (Siebel Industry Applications only) LS Pharma Calendar
NOTE: These projects were created as part of the SIF import.
For multilingual implementations, change the language settings in Siebel Tools for each language used before compiling. For example, you would do the following to compile changes for French:
a b c d
Navigate to the View menu, then the Options menu item. Click the Language Settings tab. From the Language drop-down list, choose the desired language (FRA in this example), and then click OK. When you compile, choose the .srf file from the appropriate language folder. For this example, you would choose:
SIEBSRVR_ROOT\siebsrvr\OBJECTS\FRA\siebel_sia.srf
e 7
Compile all locked projects.
Copy the browser scripts generated from the compiled SRF into the relevant Web folder by doing the following:
a b
Clear the existing folders in the language directory in the Siebel Tools installation directory (SIEBEL_TOOLS_ROOT\public\language). In Siebel Tools, compile one of the following objects:

XMLP Report Schedule Applet object XMLP Integration
c d e
Navigate back to the Siebel Tools language directory and verify a new srfXXXXXXX_XXX folder was created, where X is an automatically generated number. Copy this folder to the SWSE\public\language directory. If you have a multi-language environment, repeat the above steps for each language in your deployment.
Applying Schema Changes for ACR 633

1 2
In Siebel Tools in the Object Explorer, select the Table object. Query for all changed tables to make sure the following tables appear in the Tables list:

S_REPOUTPT_PSTN S_REP_TMPL_PSTN S_XMLP_REPOUTPT S_XMLP_REP_TMPL
54
S_XMLP_RPT_VIEW S_REP_PARM_DEF S_REP_TMPL_BU S_REPPRDEF_LANG
3 4
Click Apply/DDL, click Apply again, and then click OK. In the Apply Schema dialog box, select Current Query from the Tables drop-down list, enter the values for the database user, database user password, and the ODBC data source using the appropriate query and action for your database, and then click Apply. Database Oracle Database User and Password Query for dbtableowner in the temp.ini file and then apply that value as the database user and password. Query for databasename in the temp.ini file and then apply that value as the database user and password as MSSQL. Provide db2 as the user and password for the Siebel application. ODBC Data Source By default, this is set to either SSD Local Db default instance or Siebel_DSN. By default, this is set to either SSD Local Db default instance or Siebel_DSN. By default, this is set to either SSD Local Db default instance or Siebel_DSN.
MSSQL
DB2
Applying Seed Data Changes for ACR 633

Import the relevant seed data changes for your locale. The changes you apply depend on your Siebel application and whether you are upgrading from a previous release or deploying Siebel Reports for the first time.
Import the ACR633_Seed.dat.file (or files) applicable to your locale by running the appropriate command (or commands) as shown in the following table in the order presented. New Install Yes
Application Siebel Business Applications
Command SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8115FP\HOR\ SEED_DATA\SEED_DATA_8113\HORBIP_8113FP_Seed_ Locale_ENU SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8115FP\ HOR\SEED_DATA\SEED_DATA_8115\ACR633_Seed_ Locale_ENU
Upgrade No
Yes
Yes
Siebel Industry Applications
SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8115FP\SIA\ SEED_DATA\SEED_DATA_8113\SIABIP_8113FP_Seed_ Locale_ENU SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8115FP\ SIA\SEED_DATA\SEED_DATA_8115\ACR633_Seed_ Locale_ENU
Yes
No
Yes
Yes
55
Start the Siebel Services.

This section provides configuration information for ACR 713.
Preinstallation Tasks for ACR 713

Before you begin your installation, within the tools.cfg file, change the SymStrPrefix = X_ to SymStrPrefix = SBL_
Installing ACR 713

1 2
Navigate to REPPATCH\ACR713.zip and unzip the file to any location accessible by Siebel Tools. In Siebel Tools, lock the following projects:

LS Clinical Activity LS Clinical Payments Table Payment EIM Payment Symbolic String
NOTE: Importing SIF Files on page 56 describes the automated process that imports SIF files into the Siebel repository. Users who do not have a customized environment should follow this procedure. Users who do not have a customized environment should perform manual configuration changes using the instructions in Configuring ACR 713 Seed Data Manually on page 76.
Importing SIF Files

1
Rename <Unziplocation>\REPOSITORY\import.txt to import.bat, edit the file, and change the first four parameters related to database and Siebel Tools details with the Siebel administrator username and password. Create a log folder in <Unziplocation>\REPOSITORY. Run the import.bat file to import and use the log file to verify that the SIF files imported correctly. In Siebel Tools, compile all of the locked and updated projects. Apply the schema changes for S_SRC_PAYMENT and EIM_PAYMENT, using the instructions in Schema Changes for ACR 713 on page 57. Import the workflow processes, using the information in Importing Workflow Definitions for ACR 713 on page 69.
2 3 4 5 6
56
Schema Changes for ACR 713

The <Unziplocation>\REPOSITORY\Table\Base\Tables.sif has all the changes for Base Table and EIM\EIMTables.sif for EIM Tables. Changes to existing tables:

S_SRC_PAYMENT EIM_PAYMENT
Use the following procedure to import changes into the repository.
To import changes into the repository 1

Lock the following projects before import:

Table Payment EIM Payment
Within Siebel Tools, use the Import from Archive function to read this file and create the tables in the repository. Use the "merge" option while importing this file.
The tables have to be in the repository before creating this on the physical database.
To create the table on the physical database 1 2 3

Within Siebel Tools, query for the list of tables that were imported into the repository. Click the "Apply/DDL" button to apply the changes to the physical database. Provide the Table Owner details in the username and password and the ODBC name in the ODBC data source.
Updating EIM Files

As part of the ACR713 release, the eim45.sql and eim_export_lookup_bu_name.sql EIM files have undergone a change. The <UnzipLocation>\Repository\Table\EIM\eim45.sql and <Unziplocation>\Repository\Table\EIM\eim_export_lookup_bu_name.sql have all the changes required for the ACR. Copy the files to the following locations (overwrite the existing files) in the Siebel Server directory:

Eim45.sql: <Installation Location>\SERVER\siebsrvr\SQLTEMPL eim_export_lookup_bu_name.sql : <Installation Location>\SERVER\siebsrvr\ADMIN
Configuring the Classes for ACR 713

Two new classes have been added as part of this PIP: Navigate to <Unziplocation>\REPOSITORY\Class and import the following sif files:
CSSSWEFramePaymentListLS.sif
57
CSSSWEFramePaymentLS.sif
Configuring the Business Components for ACR 713

1 2
Within Object Explorer, select the Business Component object type. Query for Clinical Payments:
BC Name Clinical Payments
Table Name S_SRC_PAYMENT
Class CSSBCCLRollup
Project LS Clinical Payments
Within Object Explorer, select Field, and create a new field with the following details:
SVF Field # 1 2
Name Payment Feedback Payment WS Status
Column PAY_FEEDBAC K_TXT PAY_STAT_CD
No Copy
Force Active
Length 1500
Type DTYPE_TEXT DTYPE_TEXT
30
4 5
Within Object Explorer, under Business Component, select Business Component User Property. Create four new records with the following details:
Business Component User Property Name Named Method n
Value "SendPayment", "INVOKESVC", "Clinical Payments", "Workflow Process Manager", "RunProcess", ' "ProcessName" ', ' "LS Clinical Payments Outbound" ', " 'Object Id' ", " [Id] " "", "Clinical Payments", "SendPayment", "[Status] = LookupValue('FUNDRQ_STATUS','To Be Submitted') AND [Status] IS NOT NULL" "Status", "Waiting for Acknowledgement", "In Progress", "FUNDRQ_STATUS" OR "Status", "Waiting for Acknowledgement", "In Progress", "FUNDRQ_STATUS", "<<optional custom message>>" "Status", "Waiting for Acknowledgement", "Withdraw", "FUNDRQ_STATUS" OR "Status", "Waiting for Acknowledgement", "Withdraw", "FUNDRQ_STATUS", "<<optional custom message>>"
On Field Update Invoke n
Status Confirmation Popup 1
Status Confirmation Popup 2
58
Note the following about the user properties: For Status Confirmation Popup, an optional custom message is required only to customize the default warning message of the popup. For On Field Update Invoke, the status value in this user property is used to set the trigger status for the LS Clinical Payments Outbound workflow. Currently, the trigger point to invoke the workflow is configured to "To Be Submitted". If you want to have a different status to trigger the sending of the payment request, configure that status instead of "To Be Submitted"? in the value for On Field Update Invoke n. Query for the Payment Feedback field. Within Object Explorer, under Field, select Field User Prop, and create a new record with the following details:
6 7
Name Text Length Override
Value 1500
Use the following procedure to configure links.
To configure links for ACR 713 1 2

Within Object Explorer, select the Link object type. Right-click in OBLE and create a new record with the following details:
Name Clinical Payments/ Clinical Protocol Site Clinical Payments/LS Clinical Contract
Parent Business Component Clinical Payments Clinical Payments
Child Business Component Clinical Protocol Site LS Clinical Contract
Source Field Protocol Site Id Contract Id
Destination Field Id Id
Project LS Clinical Payments LS Clinical Payments
3 4 5 6
Within Object Explorer, select the Business Component object type. Right-click in OBLE and query for Clinical Payments. Within Object Explorer, expand Business Object, select Business Object Component, and pick up the link details in OBLE for "Clinical Protocol Site" as "Clinical Payments/Clinical Protocol Site". Select Business Object Component, enter "LS Clinical Contract in the Bus Comp field and enter Clinical Payments/LS Clinical Contract in the Link field.
Configuring Symbolic Strings for ACR 713

1
In Object Explorer, select Symbolic String.
59
Create a new record with the following details:
Name SBL_Feedback
Project Symbolic Strings
Current String Value Feedback
Type Conversion
Translate X
Configuring Applets for ACR 713

Use the procedures in the following section to configure the applets for ACR 713.
To configure the Clinical Protocol Site Payments List Applet 1

Within Object Explorer, select Object, and query for Clinical Protocol Site Payments List Applet.
Name Clinical Protocol Site Payments List Applet
Title Payments
Type Standard
No Delete X
2 3
Change the applet class type from 'CSSSWEFrameList' to 'CSSSWEFramePaymentListLS'. Within Object Explorer, select List > List Column, and create a new record with the following details:
Name Payment Feedback
Field Payment Feedback
Display Name Feedback
Display Name StringReference SBL_Feedback
HTML Type TextArea
4 5 6
Right-click on the Clinical Protocol Site Payments List Applet applet and select Edit Web Layout. Change the mode from Base to Edit List, and drag and drop the Feedback list column that you just created in the applet layout. Click Save.
To configure the Clinical Payment Form Applet 1

Within Object Explorer, select Applet, and query for Clinical Payments Form Applet.
60
Name Clinical Payments Form Applet
Title Payments
Type Standard
No Delete X
2 3
Change the applet class type from "CSSFrame" to "CSSSWEFramePaymentLS". Within Object Explorer, select Control, and create a new record with the following details:
Name Payment Feedback
Field Payment Feedback
Caption Feedback
Caption String Reference SBL_Feedback
HTML Type TextArea
4 5
Right-click on the Clinical Payments Form Applet applet and select Edit Web Layout. Select the Edit mode, drag and drop the Feedback control that you created in the applet layout, and click Save to save your changes.
Configuring Picklists for ACR 713

1
Within Object Explorer, select Picklist and query for "LS Clinical Payment Status PickList".
Name LS Clinical Payment Status PickList
Business Component PickList Generic
Bounded Y
Static Y
Type Field Type
Type Value FUNDRQ_STATUS
No Insert X
No Delete X
No Update X
No Merge X
In the Search Specification field, replace the existing search specification with [Order By] = 207 or [Order By] = 101 or [Order By] = 8 or [Order By] = 204 or [Order By] = 401 or ([Order By] > 500 and [Order By] < 508).
Configuring Integration Objects for ACR 713

Use the procedures in the following section to create the integration objects for ACR 713.
To configure the LS Clinical Payments integration object 1 2

Within Siebel Tools, navigate to File> New Object > EAI > Integration Object. Select the LS Clinical Payments project and the EAI Siebel Wizard business service.
61
3 4
Select Clinical Payments as the source root and source object, and LS Clinical Payments as the integration object name. Select only the integration components listed in the following table, click Next, verify the messages, and then click Finish.
Project LS Clinical Payments LS Clinical Payments LS Clinical Payments LS Clinical Payments
Source Object Clinical Payments Clinical Payments Clinical Payments Clinical Payments
Source Root Clinical Payments Clinical Payments Clinical Payments Clinical Payments
IO Name LS Clinical Payments LS Clinical Payments LS Clinical Payments LS Clinical Payments
Integration Component Clinical Payments Action (No Owner Lock) Clinical Protocol Site LS Clinical Contract
Within Object Explorer, under the LS Clinical Payments integration object, navigate to the Integration Components field of the Clinical Payments integration component, and inactivate the fields that are not listed in the following table:
Name Amount Currency Code Amount Exchange Date Comments Conflict Id Contract Id Created PaymentFeedback Id Mod Id Payment Number Protocol Number Requested Amount Status Type Updated
Data Type DTYPE_TEXT DTYPE_DATE DTYPE_TEXT DTYPE_ID DTYPE_ID DTYPE_DATETIME DTYPE_TEXT DTYPE_ID DTYPE_ID DTYPE_TEXT DTYPE_TEXT DTYPE_CURRENCY DTYPE_TEXT DTYPE_TEXT DTYPE_DATETIME
Length 20
Required
Type Data Data
XML Style Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element
XML Tag AmountCurrencyCode AmountExchangeDate Comments ConflictId ContractId Created PaymentFeedback Id ModId PaymentNumber ProtocolNumber RequestedAmount Status Type Updated
255 30
Data System Data
30 1500 30 30 30 30 X
System Data System System Data Data Data
30 30 30
Data Data System
62
Name Operation Searchspec Amount Paid To Date Check Date Check Number Payee Last Name Payee First Name
Data Type DTYPE_TEXT DTYPE_TEXT DTYPE_CURRENCY DTYPE_DATE DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT
Length 30 250 NA NA 30 50 50
Required
Type System System Data Data Data Data Data
XML Style Attribute Attribute Element Element Element Element Element
XML Tag Operation Searchspec AmountPaidToDate CheckDate CheckNumber PayeeLastName PayeeFirstName
The following IC key will be generated after creating the integration object:
Name V77 Wizard-Generated User Key:1
Key Sequence Number 1
Key Type User Key
Within Object Explorer, under the LS Clinical Payments integration object, navigate to the Integration Component field of the Action (No Owner Lock) integration component and inactivate the fields that are not mentioned in the following table:
Name Activity UID Comment Conflict Id Created Description Id Mod Id New Max Amount Subject Id Type Searchspec Operation Parent Template Name Subject Number Agreement Name Account Name
Data Type DTYPE_TEXT DTYPE_TEXT DTYPE_ID DTYPE_DATETIME DTYPE_TEXT DTYPE_ID DTYPE_ID DTYPE_CURRENCY DTYPE_ID DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT
Length 30 1,500 30 30 100 30 30
Type Data Data System System Data System System Data Data
External Name Activity UID Comment Conflict Id Created Description Id Mod Id New Max Amount Subject Id Type Searchspec Attribute Parent Template Name Subject Number Agreement Name Account Name
XML Tag ActivityUID Comment ConflictId Created Description Id ModId NewMaxAmount SubjectId Type Searchspec Operation ParentTemplateName SubjectNumber AgreementName AccountName
30 250 30 50 30 50 100
Data System System Data Data Data Data
63
The following integration component key will be generated after creating the integration object:
Key Type User Key
Within Object Explorer, under the LS Clinical Payments integration object, navigate to the Integration Components field of the Clinical Protocol Site integration component, and inactivate the fields that are not mentioned in the following table:
Name Conflict Id Created Id Mod Id Updated Operation Searchspec Site Name
Data Type DTYPE_ID DTYPE_DATETIME DTYPE_ID DTYPE_ID DTYPE_DATETIME DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT
Length 30 30 30 30 30 30 250 100
Type System System System System System System System Data
XML Style Element Element Element Element Element Attribute Attribute Element
XML Tag ConflictId Created Id ModId Updated Operation Searchspec SiteName
Name V77 WizardGenerated User Key:1
Key Type User Key
Within Object Explorer, under the LS Clinical Payments integration object, navigate to the Integration Component field of the LS Clinical Contract integration component, and inactivate the fields that are not mentioned in the following table:
Name Name Account Id
Data Type DTYPE_TEXT DTYPE_ID
Length 50
Type Data Data
XML Style Element Element
XML Tag Name AccountId
64
Name Agreement End Date Agreement Id Agreement Number Agreement Start Date Agreement Status Agreement Type Bill To Address Id Bill To Contact Id Contact Contact First Name Default Agreement Status Discount Discount Amount Discount Reason Default Agreement Type Effective Date End Date Exchange Date Primary Organization Primary Organization Id
Data Type DTYPE_UTCDATETIME DTYPE_ID DTYPE_TEXT DTYPE_UTCDATETIME DTYPE_TEXT DTYPE_TEXT DTYPE_ID DTYPE_ID DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT DTYPE_NUMBER DTYPE_CURRENCY DTYPE_TEXT DTYPE_TEXT DTYPE_UTCDATETIME DTYPE_DATE DTYPE_DATE DTYPE_TEXT DTYPE_ID
Length
Type Data Data
XML Style Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element
XML Tag AgreementEndDate AgreementId AgreementNumber AgreementStartDate AgreementStatus AgreementType BillToAddressId BillToContactId Contact ContactFirstName DefaultAgreementStatus Discount DiscountAmount DiscountReason DefaultAgreementType EffectiveDate EndDate ExchangeDate PrimaryOrganization PrimaryOrganizationId
30
Data Data
30 30 50 50 50 50 30
Data Data Data Data Data Data Data Data Data
250 30
Data Data Data Data Data
100
Data Data
To configure the LS Clinical Payments Internal integration object 1 2 3 4

Log into Siebel Tools, and navigate to File> New Object > EAI > Integration Object. Within Integration Object Builder, select the LS Clinical Payments project and and EAI Siebel Wizard business service. Select Clinical Payments as the source root and source object, and LS Clinical Payments Internal as the integration object name. Select only the integration components listed in the following table, click Next, verify the messages, and then click Finish.
65
Project LS Clinical Payments LS Clinical Payments LS Clinical Payments LS Clinical Payments
Source Object Clinical Payments
Source Root Clinical Payments
IO Name LS Clinical Payments Internal LS Clinical Payments Internal LS Clinical Payments Internal LS Clinical Payments Internal
Integration Component Clinical Payments
Clinical Payments
Clinical Payments
Action (No Owner Lock) Clinical Protocol Site LS Clinical Contract
Clinical Payments
Clinical Payments
Clinical Payments
Clinical Payments
Within Object Explorer, under the LS Clinical Payments Internal integration object, navigate to the Integration Component field of the Clinical Payment integration component, and inactivate the fields that are not listed in the following table:
Name Amount Currency Code Amount Exchange Date Comments Conflict Id Contract Id Created PaymentFeedback Id Mod Id Payment Number Protocol Number Requested Amount Status Payment WS Status Type
Data Type DTYPE_TEXT DTYPE_DATE DTYPE_TEXT DTYPE_ID DTYPE_ID DTYPE_DATETIME DTYPE_TEXT DTYPE_ID DTYPE_ID DTYPE_TEXT DTYPE_TEXT DTYPE_CURRENCY DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT
Length 20
Required
Type Data Data
XML Style Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element
XML Tag AmountCurrencyCode AmountExchangeDate Comments ConflictId ContractId Created PaymentFeedback Id ModId PaymentNumber ProtocolNumber RequestedAmount Status PaymentWSStatus Type
255 30
Data System Data
30 1500 30 30 30 30 X
System Data System System Data Data Data
30 30 30
Data Data Data
66
Name Updated Operation Searchspec Amount Paid To Date Check Date Check Number Payee Last Name Payee First Name
Data Type DTYPE_DATETIME DTYPE_TEXT DTYPE_TEXT DTYPE_CURRENCY DTYPE_DATE DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT
Length 30 30 250 NA NA 30 50 50
Required
Type System System System Data Data Data Data Data
XML Style Element Attribute Attribute Element Element Element Element Element
XML Tag Updated Operation Searchspec AmountPaidToDate CheckDate CheckNumber PayeeLastName PayeeFirstName
Key Type User Key
Within Object Explorer, under the LS Clinical Payments integration object, navigate to the Integration Component field of the Action (No Owner Lock) integration component, and inactivate the fields that are not listed in the following table:
Name Activity UID Comment Conflict Id Created Description Id Mod Id New Max Amount Subject Id Type Searchspec Operation Parent Template Name Subject Number
Data Type DTYPE_TEXT DTYPE_TEXT DTYPE_ID DTYPE_DATETIME DTYPE_TEXT DTYPE_ID DTYPE_ID DTYPE_CURRENCY DTYPE_ID DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT
Length 30 1,500 30 30 100 30 30
Type Data Data System System Data System System Data Data
External Name Activity UID Comment Conflict Id Created Description Id Mod Id New Max Amount Subject Id Type Searchspec Attribute Parent Template Name Subject Number
XML Tag ActivityUID Comment ConflictId Created Description Id ModId NewMaxAmount SubjectId Type Searchspec Operation ParentTemplateName SubjectNumber
30 250 30 50 30
Data System System Data Data
67
Name Agreement Name Account Name
Data Type DTYPE_TEXT DTYPE_TEXT
Length 50 100
Type Data Data
External Name Agreement Name Account Name
XML Tag AgreementName AccountName
Key Type User Key
Within Object Explorer, under the LS Clinical Payments integration object, navigate to the Integration Component field of the Clinical Protocol Site integration component, and inactivate the fields that are not listed in the following table:
Name Conflict Id Created Id Mod Id Updated Operation Searchspec Site Name
Data Type DTYPE_ID DTYPE_DATETIM E DTYPE_ID DTYPE_ID DTYPE_DATETIM E DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT
Length 30 30 30 30 30 30 250 100
Type System System System System System System System Data
XML Style Element Element Element Element Element Attribute Attribute Element
XML Tag ConflictId Created Id ModId Updated Operation Searchspec SiteName
Key Type User Key
Within Object Explorer, under the LS Clinical Payments integration object, navigate to the Integration Component field of the LS Clinical Contract integration component, and inactivate the fields that are not listed in the following table:
68
Name Name Account Id Agreement End Date Agreement Id Agreement Number Agreement Start Date Agreement Status Agreement Type Bill To Address Id Bill To Contact Id Contact Contact First Name Default Agreement Status Discount Discount Amount Discount Reason Default Agreement Type Effective Date End Date Exchange Date Primary Organization Primary Organization Id
Data Type DTYPE_TEXT DTYPE_ID DTYPE_UTCDATETIME DTYPE_ID DTYPE_TEXT DTYPE_UTCDATETIME DTYPE_TEXT DTYPE_TEXT DTYPE_ID DTYPE_ID DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT DTYPE_NUMBER DTYPE_CURRENCY DTYPE_TEXT DTYPE_TEXT DTYPE_UTCDATETIME DTYPE_DATE DTYPE_DATE DTYPE_TEXT DTYPE_ID
Length 50
Type Data Data Data Data
XML Style Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element Element
XML Tag Name AccountId AgreementEndDate AgreementId AgreementNumber AgreementStartDate AgreementStatus AgreementType BillToAddressId BillToContactId Contact ContactFirstName DefaultAgreementStatus Discount DiscountAmount DiscountReason DefaultAgreementType EffectiveDate EndDate ExchangeDate PrimaryOrganization PrimaryOrganizationId
30
Data Data
30 30 50 50 50 50 30
Data Data Data Data Data Data Data Data Data
250 30
Data Data Data Data Data
100
Data Data
Importing Workflow Definitions for ACR 713

Use the following procedure to import workflow definitions.
To import workflow definitions for ACR 713 1

Log in to Siebel Tools. NOTE: Siebel Tools must be connected to the same database as the Siebel application server.
2 3
From Object Explorer, navigate to Workflow Process. From the list applet, right-click and choose choose Import Workflow Process.
69
Browse to <Unziplocation>\REPOSITORY\Workflows, and choose LS Clinical Payments Outbound.xml.
New/Modified New New New
Xml File to Import LS Clinical Payments Outbound.xml LS Clinical State Validation.xml SWI LS Clinical Payments Inbound.xml
Workflow Name LS Clinical Payments Outbound LS Clinical State Validation SWI LS Clinical Payments Inbound
Project LS Clinical Activity LS Clinical Activity LS Clinical Activity
After import, query for the workflow, and in Lock Projects view > Workflow process, focus on the record and click the Publish/Activate button on top of the applet to deploy them. NOTE: While Validating/Publishing, if the workflow yields the Rule98 Validation (such as For Eg., "Validation failed for the workflow process 'SWI LS Clinical Payments Inbound' for the branch 'YES1' The 'WF Branch Criteria Value' - field such as LO_.. or HI_.. for the respective data type is null or empty) error message, ignore the error message and click the Publish button to publish the workflow and continue to publish the other workflows.
Repeat the preceding steps for the remaining new workflows. NOTE: Currently as part of the PIP, the exceptional statuses are "Submitted", "Rejected" and "Paid". If an exceptional status other than these needs to be configured, the configuration should be performed as part of the SWI LS Clinical Payments Inbound workflow in the "Is it an exceptional Status" decision step in the YES condition connection.
Fore more information about modifying list values and state models, see Configuring Siebel Business Applications and Siebel Applications Administration Guide. Use the following procedure to modify an exceptional status (a status value that updates the payment status in the Siebel application regardless of the state model definition).
To add or modify an exceptional status 1 2 3

Navigate to the SWI LS Clinical Payments Inbound workflow and open it in edit mode. Add or update a new incoming status value in the condition critieria set on the "Is it an Exceptional Status?" decision block. Publish and activate the SWI LS Clinical Payments Inbound workflow.
Use the following procedure to add or define the exceptional status as the final status (a status value that cannot be modified, such as Paid).
To define the exceptional status as the final status 1

Navigate to the SWI LS Clinical Payments Inbound workflow.
70
2 3
Add or update a new incoming status value in the condition critieria set on the "Is it an Exceptional Status?" decision block. Publish and activate the SWI LS Clinical Payments Inbound workflow.
For more information about modifying workflows, see Siebel Business Process Framework: Workflow Guide on the Siebel Bookshelf.
Activating Workflow Definitions for ACR 713

Use the following procedure to activate workflow definitions.
To activate worfklow definitions for ACR 713 1 2

Log into Siebel eClinical, and navigate to the Administration - Business Process > Workflow Deployment view. On the Repository Workflow Processes applet, query for workflows listed in the following table, focus on each record and click the Activate button to activate the workflow.

LS Clinical Payments Outbound SWI LS Clinical Payments Inbound LS Clinical State Validation
NOTE: Make sure that the EAI and Workflow Management component groups are not enabled. If they are not enabled, enable them and then restart the Siebel Server.
Importing Inbound Web Services for ACR 713

Use the following procedure to import Web services definitions.
To import Web Services definitions 1 2

Log into the Siebel application, and navigate to the Administration - Web Services > Inbound Web Services view. Navigate to the <Unziplocation>\ REPOSITORY\WebServices folder within the extracted folder, and import the SWI LS Clinical Payments Inbound.xml file.
XML File to Import SWI LS Clinical Payments Inbound.XML
Web Service Name SWI LS Clinical PaymentsInbound
Direction Inbound
Query for the "SWI LS Clinical Payments Inbound" Web service.
71
If you are using the Oracle Clinical Trial Payments Integration Pack for Siebel Clinical, update the default address as follows http://<webserver>/eai_<lang>/ start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute
Change <webserver> to the webserver hostname and change <lang> to "enu".
For more information about how to configure Web services, see the Web services section within Transports and Interfaces: Siebel Enterprise Application Integration on the Siebel Bookshelf.

The following section describes how to import seed data using the automated feature. For information about how to configure seed data manually, see Configuring ACR 713 Seed Data Manually on page 76.
To import ACR 713 seed data using automated seed-data import 1

Create an ODBC entry for the database where you plan to import the seed data:
a b c d
Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC), navigate to the System DSN tab, and click Add. Pick the "Siebel Oracle90" driver (from Datadirect Technologies). Enter a data source name (for example, DevelopmentDB). Enter the server name to connect to.
For Oracle, enter the TNS service name that you created to connect Siebel Tools to the database.
e 2 3
Test your connection and click OK when tested successfully.
Navigate to the directory in which you installed Siebel Tools. Rename <Unziplocation>\SEED_DATA\Import_Seed_Data.txt to import_Seed_Data.bat, edit the file, and change the first six parameters related to the application database and Siebel Tools path details. For example:

SET CTMSPATH=D:\21219\Tools SET DBFOLDER=Oracle SET CTMSDATASRC=loacal SET CTMSTBLOWNER=<Siebel Table Owner> SET CTMSUSERNAME=<Siebel Admin Username> SET CTMSPASSWORD=<Siebel Admin Password>
4 5 6
72
Run the Import_Seed_Data.bat file to import seed data. Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import completed successfully If you are implementing a language other than ENU, do the following:
Run the following command after importing ACR713_Seed.dat file for importing the locale specific ACR713_Seed_Locale_XXX.dat, where XXX is the language code. <Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Unziplocation>\SEED_DATA\XXX\ACR713_Seed_Locale_XXX.dat /l <Tools Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q -1 /w n /e y /t n /x R /n 100 /h log <Tools Install Directory> - Replace with your Tools install directory. <ODBC Source Name> - Replace with ODBC name created in Step 1.
Use the following procedure to perform a clear cache on the List of Values.
To perform a clear cache on the LOV 1

Navigate to Site Map > Data Administration > List Of Values, and query for the two records displayed in the following table:
Type FUNDRQ_STATUS
Display Value Waiting for Acknowledgement Withdraw
Language Independent Code Waiting for Acknowledgeme nt Withdraw
Language Name EnglishAmerican EnglishAmerican
Order 506
FUNDRQ_STATUS
507
Select these two records and click the Clear Cache button.
Configuring the State Model for ACR 713

Use the following procedure to configure the state model. NOTE: For more information about configuring state models, see Siebel Applications Administration Guide.
To configure the state model for ACR 713 1

Navigate to Site Map > Application Administration -> State Models, and query for the record with the following details:
73
State Model Name LS Clinical Payments Status
Business Component Clinical Payments
Field Status
Click the States button, and verify that the records listed in the following table exist in the States Tab. NOTE: The records marked as Imported are added as part of the seed data automation.
Existing/ Imported Existing Existing Existing Existing Existing Existing Existing Imported Imported
State To Be Processed Processed In Progress Paid Request Failed To Be Submitted Update Failed Withdraw Waiting for Acknowledgeme nt Rejected Submitted
Default Y
Restrict Transition Y Y Y Y Y Y Y Y Y
Description To Be Processed Processed In Progress Paid Request Failed To Be Submitted Update Failed Withdraw Waiting for Acknowledgement Rejected Submitted
Imported Imported
Y Y
Click the Transitions button, query for the records displayed in the following table, and delete them: NOTE: Query for the record with the "From State" value as "To Be Processed" and the "To State" value as "To Be Submitted" and delete the record. Follow the same process with the rest of the records.
Operation Performed Delete Delete
From State To Be Processed In Progress
To State To Be Submitted Processed
Public Y Y
74
Operation Performed Delete Delete
From State In Progress Request Failed
To State Request Failed Processed
Public Y Y
Query for the records listed in the following table, and verify that they appear. NOTE: Querying on "From State" with the "To Be Processed" value should retrieve only one record with the "To State" value as "In Progress" with the "Public" flag set to "Y". In addition, querying on the "From state" value as "In Progress" should retrieve only one record with the "To State" value as "To Be Submitted" with the Public Flag as "Y".
Existing/Imported/ Added Existing Imported Existing Existing Imported Imported Imported Imported Existing Imported Imported Imported Imported Imported Imported Imported Imported Imported Existing
From State To Be Processed In Progress Processed Processed Processed To Be Submitted To Be Submitted To Be Submitted To Be Submitted Waiting for Acknowledgement Waiting for Acknowledgement Waiting for Acknowledgement Submitted Submitted Submitted Withdraw Rejected Request Failed Update Failed
To State In Progress To Be Submitted Paid Update Failed In Progress Waiting for Acknowledgement Request Failed Processed In Progress Submitted Withdraw In Progress Paid Rejected Withdraw In Progress In Progress In Progress Paid
Public Y Y Y Y Y N N Y Y N Y Y N N Y Y Y Y Y
75
Verifying Data Maps for ACR 713

1 2 3
Navigate from Site Map > Administration - Integration > Data Map Editor. Query for the LS Clinical Send Payments integration object map, and verify that it appears. Query for the LS Clinical Payment Map integration object map and verify that it appears.
Configuring ACR 713 Seed Data Manually

The procedures in this section describe how to configure ACR 713 seed data manually.
To manually add new picklist values 1

Navigate to Site Map > Data Administration > List Of Values, and add two records with the following values:.
Type FUNDRQ_STATUS FUNDRQ_STATUS
Display Value Waiting for Acknowledgement Withdraw
Language Independent Code Waiting for Acknowledgement Withdraw
Language Name English-American English-American
Order 506 507
Select the two records that you just created and click the Clear Cache button.
To manually add the state model 1

Navigate to Site Map > Application Administration > State Models, and query for the record with the following details:
State Model Name LS Clinical Payments Status
Business Component Clinical Payments
Field Status
Click the States button, and make sure that the following records exist or were added to the States tab:
New/Existing Existing Existing Existing
State To Be Processed Processed In Progress
Default Y
Restrict Transition Y Y Y
Description To Be Processed Processed In Progress
76
New/Existing Existing New Existing Existing New New New
State Paid Rejected Request Failed To Be Submitted Submitted Withdraw Waiting for Acknowledgeme nt Update Failed
Default
Restrict Transition Y Y Y Y Y Y Y
Description Paid Rejected Request Failed To Be Submitted Submitted Withdraw Waiting for Acknowledgeme nt Update Failed
Existing
Click the Transitions button, and make sure that the records listed in the following table exist or were added to the Transitions tab, and delete the records marked as Delete.
New/Existing/ Delete Existing Delete New Delete Delete Existing Existing New New New New Existing New New
From State To Be Processed To Be Processed In Progress In Progress In Progress Processed Processed Processed To Be Submitted To Be Submitted To Be Submitted To Be Submitted Waiting for Acknowledgement Waiting for Acknowledgement
To State In Progress To Be Submitted To Be Submitted Processed Request Failed Paid Update Failed In Progress Waiting for Acknowledgement Request Failed Processed In Progress Submitted Withdraw
Public Y Y Y Y Y Y Y Y N N Y Y N Y
77
New/Existing/ Delete New New New New New New New Delete Existing
From State Waiting for Acknowledgement Submitted Submitted Submitted Withdraw Rejected Request Failed Request Failed Update Failed
To State In Progress Paid Rejected Withdraw In Progress In Progress In Progress Processed Paid
Public Y N N Y Y Y Y Y Y
To create new integration object maps 1

Navigate to Site Map > Administration - Integration > Data Map Editor, and create a new integration object map with the values in the following tables: NOTE: The LS Clinical Send Payments data map is used to map all the fields from the internal IO to the target IO. The target system requires the date to be sent in the ISO format. All of the required date fields have been mapped to the target integration component fields in the following format ToChar([fieldname],'YYYY-MM-DD').
Name LS Clinical Send Payments
Source Object Name LS Clinical Payments Internal
Target Object Name LS Clinical Payments
Name Clinical Payments_to_Clinical Payments Action_(No_Owner_Lock)_to_Action _(No_Owner_Lock)
Source Component Name Clinical Payments Action(No Owner Lock)
Target Component Name Clinical Payments Action (No Owner Lock)
Parent Component Map Name
Clinical Payments_to_Clinical Payments
78
Name Clinical_Protocol_Site_to_Clinical Protocol_Site LS_Clinical_Contract_to_LS_Clinical _Contract
Source Component Name Clinical Protcol Site LS Clinical Contract
Target Component Name Clinical Protocol Site LS Clinical Contract
Parent Component Map Name Clinical Payments_to_Clinical Payments Clinical Payments_to_Clinical Payments
2 3
Navigate to the Clinical Payments_to_Clinical Payments integration component map. Navigate to Integration Field map and query in the Source Expression field for the following values:
a b 4 5
Query for Primary Address Id and change it to IIF([Primary Address Id]="No Match Row Id" ,"",[Primary Address Id]) Query for Primary Payee Id and change it to IIF([Primary Payee Id]="No Match Row Id" ,"",[Primary Payee Id])
Navigate to the Action (No Owner Lock)_to_Action (No Owner Lock) integration component map. Navigate to Integration Field Map and query in the Source Expression field for the following values:
a b c d e 6 7
Query for Primary Product Detailed Id and change it to IIF([Primary Product Detailed Id]="No Match Row Id" ,"",[Primary Product Detailed Id]) Query for Primary Symptom Code and change it to IIF([Primary Symptom Code]="No Match Row Id" ,"",[Primary Symptom Code]) Query for Service Location Id and change it to IIF([Service Location Id]="No Match Row Id" ,"",[Service Location Id]) Query for Personal Location Id and change it to IIF([Personal Location Id]="No Match Row Id" ,"",[Personal Location Id]) Query for Primary Contact Id and change it to IIF([Primary Contact Id]="No Match Row Id" ,"",[Primary Contact Id])
Navigate to the Clinical Protocol Site_to_Clinical Protocol Site integration component map. Navigate to Integration Field Map and query in the Source Expression field for the following:
a 8 9
Primary Subject Template Id and change it to IIF([Primary Subject Template Id]="No Match Row Id" ,"",[Primary Subject Template Id])
Navigate to the LS_Clinical_Contract_to_LS_Clinical_Contract integration component map. Navigate to Integration Field Map and and query in the Source Expression field for the following values:
Bill To Address Id and change it to IIF([Bill To Address Id]="No Match Row Id" ,"",[Bill To Address Id])
79
b c
Bill To Contact Id and change it to IIF([Bill To Contact Id]="No Match Row Id" ,"",[Bill To Contact Id]) Primary Organization Id and change it to IIF([Primary Organization Id]="No Match Row Id" ,"",[Primary Organization Id])
10 Save the changes.

The LS Clinical Payment Map integration object map is used to update the status to the database, and contains the values listed in the following tables:
Name LS Clinical Payment Map
Source Object Name LS Clinical Payments
Target Object Name LS Clinical Payments Internal
Name Clinical Payments_to_Clinical Payments
Source Component Name Clinical Payments
Target Component Name Clinical Payments
Integration Component Map Clinical Payments_to_Clinical Payments Clinical Payments_to_Clinical Payments
Source Expression [Payment Number]
Target Field Name Payment Number
Auto-Mapped X
[Type]
Type
Configuring Siebel Applications to Write to the JMS Queue on the SOA Server
NOTE: The following instructions are for Weblogic configuration.
Deploying JAR Files on Siebel Server for Writing to JMS Queue on the SOA Server NOTE: The following instructions are an example. The queue name, user details, folder name and other configuration details depend upon the configuration on the SOA server and the Siebel application configuration.
Create a folder named D:\WLSJMS on the Siebel machine. NOTE: The Oracle Clinical Trial Payments Integration Pack for Siebel Clinical has been installed and configured on the SOA server.
Create a folder named log in the D:\WLSJMS directory.
80
Copy Siebel.jar and SiebelJI_enu to the WLSJMS folder. NOTE: These jar files are located in the Siebel installed directory.
4 5
Use the instructions in Installing wlfullclient.jar on page 82 to copy the jar files to the Siebel Server. Create a file called 'jndi.properties' in the WLSJMS directory and copy the following:

java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory java.naming.provider.url=t3://<host IP address>:<port>
NOTE: <hostIP address> is the IP address of the AIA FMW Server, and <port> is the Admin Server Port (the port at which the Webserver instance is listening for connections).
Configuring JMS Parameters/JVM Subsystem
1 2
Create a Named Subsystem in the Siebel application through the server management. Connect to the Siebel Server Manager from the command prompt from the bin directory of the Siebel installed folder with the following command: srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u <userid> /p <password> Eg. srvrmgr /g sdc78198svqe:4330 /e siebel /s sdc78198svqe /u sadmin /p sadmin
3 4
Run the named command to create the named subsystem and add the jar file into the class path. Create a named subsystem JAVA for subsystem JVMSubSys with DLL= D:\Siebel\8.1\Tools_1\jdk\jre\bin\server\jvm.dll, CLASSPATH = D:\WLSJMS;D:\WLSJMS\Siebel.jar;D:\WLSJMS\SiebelJI_enu.jar;D:\WLSJMS\wlfullclient.jar;, VMOPTIONS= D:\WLSJMS\log\jms.log Run a command to create the named subsystem for JMS. The following is an example of the command: create named subsystem JMSParameters for subsystem JMSSubsys with ConnectionFactory="jms/aia/AIA_SEBLCLINPayableInvoiceJMSQueueCF", SendQueue="jms/aia/AIA_SEBLCLINPayableInvoiceJMSQueue"
Log into the Siebel application, navigate to Site Map > Administration Server Configuration -> Profile Configuration, and do the following:
a b c d e
Query for the profile with Alias Name 'JAVA' in the profile list and make sure that the parameters are correct. Edit the value of VMOPTIONS to -Djms.log=D:\WLSJMS\log\jms.log. Query for the profile with Alias Name 'JMSParameters' in the profile list. Set the value of 'SendUsername' to the weblogic server user name. Set the value of 'SendPassword' to the weblogic server password
NOTE: The Weblogic server user needs to have minimum privileges to access the queue ("jms/ aia/AIA_SEBLCLINPayableInvoiceJMSQueue").
81
Siebel Maintenance Release Guide, Version 8.1.1.5, Rev. B Siebel Fix Pack Installation Instructions
7 8 9
Restart the Siebel Server. Log into the Siebel application, navigate to Site Map -> Administration-Business Service -> Simulator. Click New and provide the following parameters:

Service Name = EAI JMS Transport Method Name = CheckCLASSPATH
10 Click the Run button to verify. 11 Change the Method Name to CheckJNDIContext with the following input arguments:

SendUsername = <the user created in the weblogic console> SendPassword = <put password for the user created in Enterprise Manager> ConnectionFactory = jms/aia/AIA_SEBLCLINPayableInvoiceJMSQueueCF SendQueue = jms/aia/AIA_SEBLCLINPayableInvoiceJMSQueue
12 Click the Run button and verify. 13 Change the Method Name to Send, and let the input arguments remain the same. 14 Click the Run button and verify.
Installing wlfullclient.jar
1 2 3
Connect to SOA Server. Generate wlfullclient.jar. For more information, see http://download.oracle.com/docs/cd/ E12840_01/wls/docs103/client/jarbuilder.html. Copy wlfullclient.jar to the WLSJMS folder on the Siebel Server.
Siebel Fix Pack Installation Instructions

This topic includes the following subtopics: Siebel Fix Pack Installation Overview on page 83 About Installing Siebel Fix Packs on page 87 Installing the Siebel Fix Pack on Microsoft Windows on page 87 Installing the Siebel Fix Pack on UNIX on page 92 Configuring Slipstream Patch Installation on page 97 Postinstallation Tasks for the Siebel Server on page 98 Postinstallation Tasks for the Web Server on page 99 Postinstallation Tasks for High Interactivity Clients on page 99 Postinstallation Tasks for Supporting Additional Languages on page 100
82
Uninstalling Siebel Fix Packs on page 101
Siebel Fix Pack Installation Overview

This topic is part of Siebel Fix Pack Installation Instructions on page 82. In order to receive the full benefit of all product enhancements contained in the Siebel Business Applications releases covered by this document, and to maintain a fully supported Siebel Business Applications installation, install each product component shown on the Bill of Materials by following the Siebel Fix Pack 8.1.1.x installation instructions in this section. Install the Fix Pack for all applicable products in your existing deployment. NOTE: This Siebel Maintenance Release Guide includes information for the latest Siebel Fix Pack 8.1.1.x release. Each Fix Pack is cumulative and includes all fixes included in previous Siebel Fix Pack 8.1.1.x releases (where applicable). You can install the latest Siebel Fix Pack 8.1.1.x release on top of version 8.1.1 or any prior version 8.1.1.x release. Before installing this Fix Pack, it is strongly recommended to read all the information in the topics in this section and other applicable sections of this document. This document describes Fix Pack installation and related tasks for several key products, but not for all Siebel Business Applications products that may apply to your deployment. Fix Pack installation tasks for products not covered here are generally similar to those described here. This topic includes the following subtopics: Installation Scenarios Described in This Guide on page 84 Applicable Base Releases on page 84 About Running Siebel Image Creator on page 85 About Installing Additional Languages on page 85 About Installing Siebel Quick Fix Releases on page 86
83
Installation Scenarios Described in This Guide

This topic is part of Siebel Fix Pack Installation Overview on page 83. Installation instructions in this guide apply in the following scenarios: Performing new full installation of version 8.1.1, with Siebel Fix Pack 8.1.1.x. If you are installing version 8.1.1 (a new full installation), follow the installation instructions in the Siebel Installation Guide for the operating system you are using. Also follow the instructions in this Siebel Maintenance Release Guide for installing the latest Siebel Fix Pack 8.1.1.x release on top of version 8.1.1. Optionally, you can install 8.1 and 8.1.1.x together by configuring slipstream patch installation for server-based Siebel modules. For details, see Configuring Slipstream Patch Installation on page 97. For the most recent version of the Siebel Installation Guide for the operating system you are using, see the latest version 8.1 Siebel Bookshelf. For more information about installing Siebel Fix Pack 8.1.1.x, see About Installing Siebel Fix Packs on page 87. Installing Siebel Fix Pack 8.1.1.x (patching existing version 8.1.1 or prior version 8.1.1.x installation). If you have already installed version 8.1.1 as a new full installation, and are now installing the latest Siebel Fix Pack 8.1.1.x on top of version 8.1.1 or a previous version 8.1.1.x release, follow the instructions in this Siebel Maintenance Release Guide for doing this. Where applicable, you can optionally uninstall an existing installed Siebel Fix Pack 8.1.1.x release before you install the latest Fix Pack. For more information, see Uninstalling Siebel Fix Packs on page 101. When you installed version 8.1.1 as a full installation, you would have already referred to the Siebel Installation Guide for the operating system you are using. For the most recent version of this document, see the latest version 8.1 Siebel Bookshelf. For more information about installing Siebel Fix Pack 8.1.1.x, see About Installing Siebel Fix Packs on page 87. Adding languages. When you perform a new version 8.1.1 installation of Siebel Business Applications, include any supported languages (language packs) you require or expect to require. You can also add languages to an existing installation; additional steps are required in this case. For more information, see About Installing Additional Languages on page 85.
Applicable Base Releases

This topic is part of Siebel Fix Pack Installation Overview on page 83. In general, each Siebel Fix Pack can be installed on top of an existing Siebel installation of the same product suite that is at a valid base version level for this Fix Pack. Installing any Fix Pack requires an existing installation of a qualified base release to install into. Here, base release means the current version of the existing installation, including version 8.1.1 software and optionally including any installed Siebel Fix Pack 8.1.1.x or other patch releases.
84
Here are the base releases and Siebel Business Applications product suites for installing the latest Siebel Fix Pack 8.1.1.x release: Siebel Industry Applications, version 8.1.1 or version 8.1.1.x Siebel Cross-Industry Applications, version 8.1.1 or version 8.1.1.x
NOTE: Do not install a Fix Pack for one product suite on top of a base installation for another product suite. Such combinations are incompatible. Siebel Industry Applications are composed of multiple industry product groups (vertical applications). For a detailed listing of the industry products contained in each group, see Siebel System Requirements and Supported Platforms on Oracle Technology Network (http:// download.oracle.com/docs/cd/E11886_01/srsphomepage.html). NOTE: In order to run Siebel Business Applications software, all components of a Siebel Enterprise must be at the same exact version 8.1.1.x release level.
About Running Siebel Image Creator

This topic is part of Siebel Fix Pack Installation Overview on page 83. The Siebel Image Creator utility is used to create an installation image (sometimes called a network image) for version 8.1.1 or any Siebel Fix Pack 8.1.1.x release. The image can include any Siebel installable product and language provided as part of this product release. You can also add products or languages to an existing installation image of the same version, for products or languages that were not previously included. Installing any Siebel Business Applications release, including a new installation of version 8.1.1, an installation of a Siebel Fix Pack 8.1.1.x release, or the addition of one or more languages, must be done from an installation image created using Image Creator. NOTE: Always use the version of Siebel Image Creator provided with the Siebel release for which you are creating the installation image. Information about using Siebel Image Creator is provided in the Siebel Installation Guide for the operating system you are using, on the version 8.1 Siebel Bookshelf.
About Installing Additional Languages

This topic is part of Siebel Fix Pack Installation Overview on page 83. Include or add all languages you will require in your Siebel version 8.1.1 installation image (network image), which you create using the Siebel Image Creator utility. Then install the software with the languages you require. When you configure each installed Siebel Server and Siebel Web Server Extension, you also specify which installed languages you are deploying. Optionally, you can add languages to an existing installation. Some postinstallation tasks are required in order to deploy a language you added after initial product installation and configuration: If you add a language after you have configured an installed Siebel Server, launch the Siebel Server Configuration Wizard and run the configuration task Add Language Support for the Siebel Server. (It is not necessary to reconfigure the Siebel Server.)
85
If you add a language after you have configured an installed Siebel Web Server Extension (SWSE), launch the SWSE Configuration Wizard and run the configuration task Add Language Support for the SWSE Configuration. (It is not necessary to reconfigure the SWSE.)
After adding a language to your installed software, you must add the language to the Siebel Database, import Siebel Repository data into the database for this language, and run the MLOV (multilingual LOV) conversion utility. It is recommended to perform database-related tasks after installing applicable Fix Packs or other patch releases. NOTE: If you are adding languages to an existing installation, do so before you install the latest Siebel Fix Pack 8.1.1.x release. It is possible to add a language after a Fix Pack has been installed. However, for each component for which you add a language, you must reinstall the Fix Pack to bring the language pack files up to the current release level. (Because Fix Packs are cumulative, you can install just the latest Siebel Fix Pack 8.1.1.x release, even if you previously installed a prior Fix Pack before adding the language.) If you are not adding languages, you only need to install the latest Siebel Fix Pack 8.1.1.x release, as described in this guide. For detailed information about installing and deploying Siebel languages, see also: Siebel Installation Guide for the operating system you are using Siebel Global Deployment Guide Configuring Siebel Business Applications Siebel System Requirements and Supported Platforms on Oracle Technology Network (http:// download.oracle.com/docs/cd/E11886_01/srsphomepage.html)
See also Postinstallation Tasks for Supporting Additional Languages on page 100.
About Installing Siebel Quick Fix Releases

This topic is part of Siebel Fix Pack Installation Overview on page 83. After installing version 8.1.1 and a Siebel Fix Pack 8.1.1.x release as described in this guide, you can also install any applicable Siebel Quick Fix releases on top of version 8.1.1.x. When you install a Quick Fix, installed languages may also be patched, depending on the content of the Quick Fix release. NOTE: Installing Quick Fixes may entail restrictions about which subsequent Fix Packs can be installed. For detailed information about a particular Quick Fix, see the documentation that is provided separately with the Quick Fix. Quick Fixes Included in the Siebel 8.1.1.5 Fix Pack on page 8 identifies fixes from previous Quick Fix releases that are included in specific Siebel Fix Pack 8.1.1.x releases.
86
About Installing Siebel Fix Packs

This topic is part of Siebel Fix Pack Installation Instructions on page 82. For each Siebel Business Applications product module, installing the latest Siebel Fix Pack 8.1.1.x release on top of an existing base installation replaces existing executable files and provides new files in addition to the base installation. For supported base releases, see Siebel Fix Pack Installation Overview on page 83. Installing a Fix Pack does not replace any customer-modified files (for example, application configuration files like siebel.cfg) that govern program execution. When you install a Fix Pack, any installed languages may also be patched, depending on the content of the Fix Pack. NOTE: References in this guide to Siebel Fix Pack 8.1.1.x releases apply to the current Fix Pack release. However, you must verify the availability, characteristics, and requirements of any future Fix Pack releases, including Siebel Fix Pack 8.1.1.x releases. Installation tasks and requirements for all future releases are subject to change, and will be covered by updated documentation. If you plan to install any additional Siebel language packs, review Siebel Fix Pack Installation Overview on page 83 (in particular, About Installing Additional Languages on page 85) before you install any Fix Pack. The Siebel Fix Pack must be installed from an installation image you create using the Siebel Image Creator utility. This utility is described in version 8.1 of the Siebel Installation Guide for the operating system you are using. For more information, see About Running Siebel Image Creator on page 85. For more information about stopping and restarting Siebel components, which is a required part of the Fix Pack installation process, see Siebel System Administration Guide. See also Siebel Installation Guide for the operating system you are using. These guides are available on the Siebel Bookshelf 8.1 on Oracle Technology Network (http://www.oracle.com/technetwork/documentation/ siebel-087898.html). See also Postinstallation Tasks for the Web Server on page 99. After you install version 8.1.1 and version 8.1.1.x, you can also install any applicable Quick Fix release on top of version 8.1.1.x. For more information, see About Installing Siebel Quick Fix Releases on page 86.
Related Topics Uninstalling Siebel Fix Packs on page 101. Installing the Siebel Fix Pack on Microsoft Windows on page 87 Installing the Siebel Fix Pack on UNIX on page 92
Installing the Siebel Fix Pack on Microsoft Windows

This topic is part of Siebel Fix Pack Installation Instructions on page 82. Procedures for installing Siebel Fix Pack 8.1.1.x for products on Microsoft Windows are detailed below. Follow these instructions to install each product over the existing base installation for the same product. Perform the steps that apply for the Fix Pack you are installing, in the general sequence presented here.
87
Before you install the Fix Pack, review all applicable information in the following topics: Siebel Fix Pack Installation Overview on page 83 About Installing Siebel Fix Packs on page 87.
Instructions generally assume that Fix Pack installers are launched in GUI mode. Alternatively, the installers for server-based products can be launched in console or unattended mode. The Fix Pack installation runs silently. NOTE: If you installed version 8.1.1 Siebel software using the Siebel FastTrack Wizard, use the Fix Pack installers for Siebel Enterprise Server and Siebel Web Server Extension to patch any installed instances of these modules. The FastTrack Wizard is provided for small to medium businesses (SMB). For more information, see Siebel Installation Guide for Microsoft Windows. This topic has the following subtopics: Installing the Fix Pack for Siebel Enterprise Server on Windows on page 88 Installing the Fix Pack for Siebel Web Server Extension on Windows on page 89 Installing the Fix Pack for Siebel Management Agent and Siebel Management Server on Windows on page 90 Installing the Fix Pack for Siebel Mobile Web Client, Siebel Tools, or Siebel Client Sync on Windows on page 91
Installing the Fix Pack for Siebel Enterprise Server on Windows

This topic is part of Installing the Siebel Fix Pack on Microsoft Windows on page 87. Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any computer where a Siebel Enterprise Server component is installed, including Siebel Server, Siebel Gateway Name Server, and Database Configuration Utilities (formerly referred to as the Siebel Database Server). The Fix Pack installer for Siebel Enterprise Server also patches any instance of Siebel Management Agent that was automatically installed with a Siebel Server you are patching. See also Installing the Fix Pack for Siebel Management Agent and Siebel Management Server on Windows on page 90.
To install the Fix Pack for Siebel Enterprise Server components 1

Shut down the Siebel Business Applications product component to be updated. For example, stop the service for the Siebel Server or Siebel Gateway Name Server. Also shut down any running instances of the Siebel Server Manager (srvrmgr). If you are patching an instance of Siebel Management Agent that was previously installed with a Siebel Server, also stop the service for the Management Agent. In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the directory where the installer is located. For Siebel Enterprise Server, navigate to Siebel_Image\Windows\Server\Siebel_Enterprise_Server, where:
2 3
Siebel_Image is the directory for your version-specific Siebel installation image, such as D:\Siebel_Install_Image\8.1.1.x.
4
88
Double-click setup.exe to launch the Siebel Enterprise Server installer for version 8.1.1.x.
5 6 7 8
Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel installations. Follow all prompts to complete installation of version 8.1.1.x. Repeat these steps on each computer with a Siebel Enterprise Server component installation to be patched. Restart all applicable Siebel Business Applications product components at the end of all Fix Pack or other patch release installation for server-based products.
Installing the Fix Pack for Siebel Web Server Extension on Windows
This topic is part of Installing the Siebel Fix Pack on Microsoft Windows on page 87. Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any computer where a Siebel Web Server Extension (SWSE) component is installed. NOTE: Before you install any Fix Pack release for SWSE, refer to Siebel System Requirements and Supported Platforms on Oracle Technology Network (http://download.oracle.com/docs/cd/ E11886_01/srsphomepage.html) to verify that the Web server version is correct for the Siebel Business Applications release. If you need to update the Web server, do so before you install the Fix Pack for SWSE.
To install the Fix Pack for Siebel Web Server Extension 1 2

Stop the Web server. In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the directory where the installer is located. For SWSE, navigate to Siebel_Image\Windows\Server\Siebel_Web_Server_Extension, where:
3 4 5 6 7
Double-click setup.exe to launch the SWSE installer for version 8.1.1.x. Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel installations. Follow all prompts to complete installation of version 8.1.1.x. Repeat these steps on each computer with an SWSE installation to be patched. Restart the Web server at the end of all Fix Pack or other patch release installation for serverbased products. For more information, see Postinstallation Tasks for the Web Server on page 99.
89
Installing the Fix Pack for Siebel Management Agent and Siebel Management Server on Windows
This topic is part of Installing the Siebel Fix Pack on Microsoft Windows on page 87. Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on computers where Siebel Management Agent or Siebel Management Server are installed. NOTE: These instructions for installing Siebel Management Agent assume that Management Agent was installed separately. If your instances of Management Agent were installed as part of Siebel Server installation, follow the instructions in Installing the Fix Pack for Siebel Enterprise Server on Windows on page 88. See also the Siebel Installation Guide for the operating system you are using. When you install a Fix Pack for an instance of Siebel Management Agent, the Siebel Management Server will be unable to connect to it. It is not necessary to shut down the Management Server while you install the Fix Pack for the Management Agents. After you install the Fix Pack for all instances of Management Agent, shut down the Siebel Management Server, then install the Fix Pack for Management Server. After you restart Management Server, it automatically reconnects to each instance of Management Agent. Newly patched instances of Management Agent will not be operational until Management Server has also been patched.
To install the Fix Pack for Siebel Management Agent (where Management Agent was installed separately) 1 2
Stop the Siebel Management Agent service. In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the directory where the installer is located. For Siebel Management Agent, navigate to Siebel_Image\Windows\Server\Siebel_Management_Agent, where:
3 4 5 6 7
Double-click setup.exe to launch the Siebel Management Agent installer for version 8.1.1.x. Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel installations. Follow all prompts to complete installation of version 8.1.1.x. Restart the Management Agent service. Repeat these steps on each computer with a Siebel Management Agent installation to be patched (where Management Agent was installed separately).
To install the Fix Pack for Siebel Management Server 1 2

Stop the Siebel Management Server service. In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the directory where the installer is located. For Siebel Management Server, navigate to Siebel_Image\Windows\Server\Siebel_Management_Server, where:
90
3 4 5 6 7
Double-click setup.exe to launch the Siebel Management Server installer for version 8.1.1.x. Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel installations. Follow all prompts to complete installation of version 8.1.1.x. Restart the Management Server service. Repeat these steps on each computer with a Siebel Management Server installation to be patched. (In most deployments, only one instance is installed.)
Installing the Fix Pack for Siebel Mobile Web Client, Siebel Tools, or Siebel Client Sync on Windows
This topic is part of Installing the Siebel Fix Pack on Microsoft Windows on page 87. Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on computers where Siebel Mobile Web Client, Siebel Tools, or Siebel Client Sync are installed. (Most of the information for Siebel Mobile Web Client also applies to Siebel Developer Web Client.) NOTE: As of version 8.1.1, the installer programs for Siebel Mobile Web Client and Siebel Tools are based on the Oracle Universal Installer (OUI) framework, and have many differences from installers for previous releases. For a detailed summary of installer changes, see the Siebel Installation Guide for the operating system you are using.
To install the Fix Pack for Siebel Mobile Web Client or Siebel Tools 1
Exit any Siebel software on the client computer where you are installing the Fix Pack. NOTE: For a Siebel Mobile Web Client using the Siebel QuickStart feature, you must also exit the QuickStart agent, if it is running. To do this, right-click the QuickStart icon in the system tray, then choose Exit. For more information about using Siebel QuickStart with the Mobile Web Client, see the Siebel Installation Guide for the operating system you are using.
In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the directory where the installer is located.

For Siebel Mobile Web Client, navigate to Siebel_Image\Windows\Client\Siebel_Web_Client\Disk1\install For Siebel Tools, navigate to Siebel_Image\Windows\Client\Siebel_Tools\Disk1\install
where:
3 4 5
Double-click oui.exe to launch the Siebel client or Siebel Tools installer for version 8.1.1.x. In the dialog box labeled Specify Home Details, select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel installations. Follow all prompts to complete installation of version 8.1.1.x.
91
Repeat these steps on each computer with an applicable Siebel client or Siebel Tools installation to be patched. NOTE: The computer may require a restart at the end of the installation.
To install the Fix Pack for Siebel Client Sync 1 2

Exit any Siebel software on the client computer where you are installing the Fix Pack. In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the directory where the installer is located. For Siebel Client Sync, navigate to Siebel_Image\Windows\Client\Siebel_Client_Sync, where:
3 4 5 6
Double-click install.exe to launch the Siebel Client Sync client installer for version 8.1.1.x. Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel installations. Follow all prompts to complete installation of version 8.1.1.x. Repeat these steps on each computer with an applicable Siebel Client Sync installation to be patched. NOTE: The computer may require a restart at the end of the installation.
Installing the Siebel Fix Pack on UNIX

This topic is part of Siebel Fix Pack Installation Instructions on page 82. Procedures for installing Siebel Fix Pack 8.1.1.x for products on supported UNIX and Linux platforms are detailed below. Follow these instructions to install each product over the existing base installation for the same product. Perform the steps that apply for the Fix Pack you are installing, in the general sequence presented here. Before you install the Fix Pack, review all applicable information in the following topics: Siebel Fix Pack Installation Overview on page 83 About Installing Siebel Fix Packs on page 87
Instructions generally assume that Fix Pack installers are launched in GUI mode. Alternatively, the installers for server-based products can be launched in console or unattended mode. The Fix Pack installation runs silently. NOTE: Some Siebel Business Applications products can only be installed on Windows, such as Siebel Management Server, Siebel Mobile Web Client, Siebel Tools, or Siebel Client Sync. For more information, see Installing the Siebel Fix Pack on Microsoft Windows on page 87. This topic has the following subtopics: Installing the Fix Pack for Siebel Enterprise Server on UNIX on page 93 Installing the Fix Pack for Siebel Web Server Extension on UNIX on page 94
92
Installing the Fix Pack for Siebel Management Agent on UNIX on page 95
Installing the Fix Pack for Siebel Enterprise Server on UNIX

This topic is part of Installing the Siebel Fix Pack on UNIX on page 92. Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any computer where a Siebel Enterprise Server component is installed, including Siebel Server, Siebel Gateway Name Server, and Database Configuration Utilities (formerly referred to as the Siebel Database Server). The Fix Pack installer for Siebel Enterprise Server also patches any instance of Siebel Management Agent that was automatically installed with a Siebel Server you are patching. See also Installing the Fix Pack for Siebel Management Agent on UNIX on page 95.
To install the Fix Pack for Siebel Enterprise Server components 1

Stop all running Siebel Servers by running the command stop_server on each applicable server computer. (See Siebel System Administration Guide for details on how to use this command.) Also shut down any running instances of the Siebel Server Manager (srvrmgr). If you are patching an instance of Siebel Management Agent that was previously installed with a Siebel Server, also stop the service for the Management Agent. Unload libraries from the system cache by running the command reset_server all on each applicable server computer. (See Siebel System Administration Guide for details on how to use this command.) Stop the Siebel Gateway Name Server by running the command stop_ns. (See Siebel System Administration Guide for details on how to use this command.) (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 3
4 5
(AIX only) Execute slibclean, as follows: /usr/sbin/slibclean
Open a new shell and navigate to the Siebel image location for version 8.1.1.x, then to the directory where the installer is located. For Siebel Enterprise Server, navigate to Siebel_Image/ UNIX_OS/Server/Siebel_Enterprise_Server, where:

Siebel_Image is the directory for your version-specific Siebel installation image, such as /Siebel_Install_Image/8.1.1.x. UNIX_OS is your UNIX operating system, such as AIX, HPUX (HP-UX), Linux, or Solaris.
(For GUI mode) Run setupUNIX_OS to launch the Siebel Enterprise Server installer in GUI mode for version 8.1.1.x, where:
UNIX_OS is your UNIX operating system, such as aix (AIX), hp (HP-UX), linux (Linux), or sol (Solaris).
Go to Step 10 on page 94.
93
(For console mode) Enter the following command to launch the Siebel Enterprise Server installer in console mode for version 8.1.1.x: setupUNIX_OS is:javaconsole -console where:
10 Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel
installations.
11 Follow all prompts to complete installation of version 8.1.1.x. 12 Repeat these steps on each computer with a Siebel Enterprise Server component installation to
be patched.
13 Restart all applicable Siebel Business Applications product components at the end of all Fix Pack
or other patch release installation for server-based products.
Installing the Fix Pack for Siebel Web Server Extension on UNIX
This topic is part of Installing the Siebel Fix Pack on UNIX on page 92. Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any computer where a Siebel Web Server Extension (SWSE) component is installed. NOTE: Before you install any Fix Pack for SWSE, refer to Siebel System Requirements and Supported Platforms on Oracle Technology Network to verify that the Web server version is correct for the Siebel Business Applications release. If you need to update the Web server, do so before you install the Fix Pack for SWSE.
To install the Fix Pack for Siebel Web Server Extension 1

Stop the Web server by running one of the following commands:

ompmnctl stopall - for Oracle HTTP Server (on AIX or supported Linux platforms) stopapa for other Apache-based Web servers (on AIX, HP-UX, or supported Linux platforms) stop for Oracle iPlanet Web Server (on Oracle Solaris)
2 3
Log on to the server using the Web server owner account. (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
94
Open a new shell and navigate to the Siebel image location for version 8.1.1.x, then to the directory where the installer is located. For SWSE, navigate to Siebel_Image/UNIX_OS/Server/ Siebel_Web_Server_Extension, where:

(For GUI mode) Run setupUNIX_OS to launch the SWSE installer in GUI mode for version 8.1.1.x, where:
(For console mode) Enter the following command to launch the SWSE installer in console mode for version 8.1.1.x: setupUNIX_OS is:javaconsole -console where:
8 9
Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel installations. Follow all prompts to complete installation of version 8.1.1.x.
10 Repeat these steps on each computer with an SWSE installation to be patched. 11 Restart the Web server at the end of all Fix Pack or other patch release installation for serverbased products. For more information, see Postinstallation Tasks for the Web Server on page 99.
Installing the Fix Pack for Siebel Management Agent on UNIX

This topic is part of Installing the Siebel Fix Pack on UNIX on page 92. Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on computers where Siebel Management Agent is installed. NOTE: These instructions for installing Siebel Management Agent assume that Management Agent was installed separately. If your instances of Management Agent were installed automatically as part of Siebel Server installation, follow the instructions in Installing the Fix Pack for Siebel Enterprise Server on UNIX on page 93 instead. See also the Siebel Installation Guide for the operating system you are using. For information about installing the Fix Pack for Siebel Management Server (which runs on Windows only), see Installing the Fix Pack for Siebel Management Agent and Siebel Management Server on Windows on page 90.
95
When you install a Fix Pack for an instance of Siebel Management Agent, the Siebel Management Server will be unable to connect to it. It is not necessary to shut down the Management Server while you install the Fix Pack for the Management Agents. After you install the Fix Pack for all instances of Management Agent, shut down the Siebel Management Server, then install the Fix Pack for Management Server. After you restart Management Server, it automatically reconnects to each instance of Management Agent. Newly patched instances of Management Agent will not be operational until Management Server has also been patched.
To install the Fix Pack for Siebel Management Agent (where Management Agent was installed separately) 1 2
Stop the service for the Siebel Management Agent. (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
Open a new shell and navigate to the Siebel image location for version 8.1.1.x, then to the directory where the installer is located. For Siebel Management Agent, navigate to Siebel_Image/ UNIX_OS/Server/Siebel_Management_Agent, where:

(For GUI mode) Run setupUNIX_OS to launch the Siebel Management Agent installer in GUI mode for version 8.1.1.x, where:
(For console mode) Enter the following command to launch the Siebel Management Agent installer in console mode for version 8.1.1.x: setupUNIX_OS is:javaconsole -console where:
7 8 9
Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel installations. Follow all prompts to complete installation of version 8.1.1.x. Restart the Management Agent service.
96
10 Repeat these steps on each computer with a Siebel Management Agent installation to be patched
(where Management Agent was installed separately).
Configuring Slipstream Patch Installation

This topic is part of Siebel Fix Pack Installation Instructions on page 82. Slipstream patch installation is the ability to configure installer behavior so that an installer process (for full installation or Fix Pack installation) automatically invokes one or more patch installations for the same product. The main installation can be performed in applicable installer modes (GUI, console, or unattended mode). The Fix Pack or other patch installation runs silently. NOTE: As noted in the Siebel Installation Guide for the operating system you are using, slipstream patch installation applies only to installations of server-based Siebel modules. As of version 8.1.1, installers for Siebel client modules are based on Oracle Universal Installer technology (and do not use siebel.ini files) and do not support slipstream patch installation. Where slipstream patch installation is invoked by a full installation rather than by another patch installation, the patch installation executes after language packs are installed. After all installations are complete, the Siebel Configuration Wizard launches, for applicable products. As noted in Siebel Fix Pack Installation Overview on page 83, slipstream patch installation may apply in multiple installation scenarios. Applicable scenarios for the current product releases include: Full installation plus patch installation. Performing a version 8.1.1 full installation plus a Siebel Fix Pack 8.1.1.x installation. This scenario may optionally also include a Quick Fix release for version 8.1.1.x (where applicable). Multiple patch installations. Performing a Siebel Fix Pack 8.1.1.x installation plus a Quick Fix release for version 8.1.1.x (where applicable).
NOTE: If you are adding languages to an existing version 8.1.1 or 8.1.1.x installation, slipstream installation does not apply for the installation session for installing the languages. However, slipstream installation can be used when subsequently installing Siebel Fix Pack 8.1.1.x and Quick Fix releases. For more information about installing languages, see About Installing Additional Languages on page 85. You configure slipstream patch installation by modifying the base siebel.ini files for each applicable Siebel module in the version 8.1.1 or version 8.1.1.x installation image, according to your install scenario. The siebel.ini files are also modified in installation scenarios described in the chapter about unattended and console mode installations, in the Siebel Installation Guide for the operating system you are using. To support slipstream patch installation, where a version 8.1.1 full installation automatically invokes a Siebel Fix Pack 8.1.1.x installation, modify the siebel.ini file for each applicable product for version 8.1.1, as shown below. Examples for setting Execute for different modules follow. [Slipstream] Install1 = yes
97
[Install1] Execute = full_path_to_Siebel_product_installer_executable Arg = arg_argument where: full_path_to_Siebel_product_installer_executable is 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 is the value shown below for the parameter Arg, for a server installation: Arg = -args PatchInstance=$(SiebelRoot) Slipstream=yes
Examples for Specifying Execute Parameter

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

If, when installing version 8.1.1, you use slipstream installation to install both version 8.1.1.x and a Quick Fix release for version 8.1.1.x, you must configure multiple entries in the version 8.1.1 siebel.ini files. To include the Quick Fix release in the slipstream patching sequence, add Install2 = yes under the last entry in the [Slipstream] section, then configure an [Install2] section for the Quick Fix release. Configure the [Install2] section so it resembles the [Install1] section you configured for the Siebel Fix Pack 8.1.1.x, but points to the Quick Fix release instead.
Postinstallation Tasks for the Siebel Server

This topic is part of Siebel Fix Pack Installation Instructions on page 82. If you are using a security adapter, then you might need to update the value of the CRC parameter after installing Siebel Fix Pack 8.1.1.x. The value must reflect the checksum value applicable to the security adapter library file, such as a DLL file on Windows. This task may be necessary if you previously determined to use checksum validation for your security adapter deployment, and set the value of the CRC parameter. If a Fix Pack you installed later included an updated security adapter library file, the checksum validation will fail and Siebel Web Clients might not launch, unless the value of the CRC parameter is updated.
98
For detailed information about this task, see the topic about configuring checksum validation in Siebel Security Guide on the 8.1 Siebel Bookshelf.
Postinstallation Tasks for the Web Server

This topic is part of Siebel Fix Pack Installation Instructions on page 82. The Web server must be restarted after you have finished installing Siebel Fix Pack 8.1.1.x on all server-based components: Siebel Server, Siebel Gateway Name Server, Siebel Web Server Extension (SWSE), and so on. The restart is required because the Web server must be able to create a folder to contain static files required for the current version of the Siebel application (corresponding to the latest Fix Pack release). This folder is created as SWSE_ROOT/public/lang_code/build_number, where: SWSE_ROOT is the location where the SWSE is installed lang_code is each installed language (such as ENU for U.S. English) build_number is the current build number of the installed Siebel software (the build number comes from the content of the base.txt file on the SWSE installation)
The folder described above and other folders are created on the first SWSE request after installing any Siebel Business Applications release. This folder is populated with static files copied from the Siebel Server directory SIEBSRVR_ROOT/webmaster/siebel_build. The contents of these folders are refreshed each time the Web server restarts, or when an administrator enters a Web update command in the browser. After a build-specific folder is created on the SWSE, folders representing earlier builds are no longer used. For more information, see the Siebel Installation Guide for the operating system you are using and Siebel Security Guide, both on 8.1 Siebel Bookshelf. Failure to restart the Web server after installing the Fix Pack for Siebel Enterprise Server components and for the SWSE means the folders will not be created on the Web server, which causes the Siebel login screens to stop responding.
Postinstallation Tasks for High Interactivity Clients

This topic is part of Siebel Fix Pack Installation Instructions on page 82. After installing a new version of a Siebel application, including a Siebel Fix Pack, new versions of applicable ActiveX controls for the high interactivity client will be downloaded onto your users client computers when they run the Siebel application within the Internet Explorer browser. Alternatively, updated versions of the ActiveX controls you require can be predeployed to the client computers. This behavior applies to Siebel Web Client (using high interactivity only), Mobile Web Client, and Developer Web Client. For more information, see the browser configuration chapter in Siebel System Administration Guide.
99
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 computer. To clear this data, choose Start, then Settings, then Control Panel, and then Java Plug-In. Click the Cache tab, then click Reset. After a new Siebel software version is installed, is also recommended that users clear their browser cache. To do this in Internet Explorer, choose Tools, then Internet Options, and then choose Delete Files from the General tab. For the minimum supported version of the Java Runtime Environment (JRE), see Siebel System Requirements and Supported Platforms on Oracle Technology Network (http://download.oracle.com/ docs/cd/E11886_01/srsphomepage.html). The JRE can be downloaded automatically to your computers. As described in 475457.1 (Article ID) on My Oracle Support, some configuration may be required in order to download the correct version.
Postinstallation Tasks for Supporting Additional Languages

This topic is part of Siebel Fix Pack Installation Instructions on page 82. If you are installing an additional language into an existing version 8.1.1.x installation, review the information in this topic in case it applies to you. For more information about adding languages, see About Installing Additional Languages on page 85.
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 Business Applications 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 language packs for Siebel Business Applications. NOTE: These instructions are provided for use with any releases to which they apply, and might not apply for any particular version 8.1.1.x release or any particular language. The procedure below uses the Locale Management Utility (LMU), which is part of Siebel Tools, to import an LMU file. An LMU file may contain strings in just one language or in multiple languages. When running the Locale Management Utility, you can choose to import only the strings for the languages you are actually using in your installation. In the procedure below, when you are prompted for the file to import, specify the name of the LMU file provided for the applicable language. NOTE: Install any applicable Siebel Fix Pack before you run the Locale Management Utility. For more information about using the Locale Management Utility, see Using Siebel Tools and Siebel Global Deployment Guide on the 8.1 Siebel Bookshelf.
100
To import strings and other locale-specific attributes into the repository 1

In Siebel Tools, choose Tools, then Utilities, and then Locale Management. The Locale Management Utility appears.
Select a source language and a target language. The source language is the language of the locale-specific data in the LMU file you are importing. The target language is the Siebel language into which the strings will be imported.
3 4 5
Click the Import tab. Enter the name of the LMU file from which you want to import locale-specific attributes. You can also use the Browse button to find and select the file. Specify whether you want to mark records in the repository with the Redo flag that have changed since the export occurred. When the import occurs, the LMU compares the source language records in the repository with the source language records in the import file. If the records in the repository have changed since the export occurred, they are marked with the Redo flag. This flag helps you identify records that may need to be retranslated.
6 7
Click Import. After finishing, recompile the SRF file and restart the Application Object Manager component on the Siebel Server to see the results.
Uninstalling Siebel Fix Packs

This topic is part of Siebel Fix Pack Installation Instructions on page 82. This topic describes how to uninstall Siebel Fix Pack 8.1.1.x releases for Microsoft Windows and for supported UNIX and Linux platforms. Generally, a Siebel Fix Pack 8.1.1.x release installed on top of version 8.1.1 (or a prior 8.1.1.x) can be uninstalled. When you uninstall a Fix Pack, you revert to the version 8.1.1 base installation. The uninstaller prompts you whether you want to uninstall just the Fix Pack (and revert to version 8.1.1) or perform a full uninstallation of the installed software. CAUTION: Separate uninstallation of a Fix Pack is not supported for Siebel Mobile Web Client or Siebel Tools. Only the full uninstallation option is possible for these modules. Fix Pack uninstallation for modules not mentioned here is generally similar to what is described here. To perform a full uninstallation of a Siebel module, follow the uninstallation instructions provided in the Siebel Installation Guide for the operating system you are using. This topic contains the following subtopics: Scenarios for Uninstalling a Siebel Fix Pack on page 102 Instructions for Uninstalling a Siebel Fix Pack on page 102 Guidelines and Limitations for Siebel Fix Pack Uninstallation on page 103
10 1
Scenarios for Uninstalling a Siebel Fix Pack

This topic is part of Uninstalling Siebel Fix Packs on page 101. In some circumstances, you may need to, or choose to, uninstall a Siebel Fix Pack 8.1.1.x release and revert to the base installation (version 8.1.1). For example: You may decide to uninstall an existing installed Siebel Fix Pack 8.1.1.x release before installing a later Fix Pack. (This is optional.) If issues are encountered in your deployment, you may decide to uninstall an existing installed Siebel Fix Pack 8.1.1.x release and revert to version 8.1.1. Subsequently (where multiple Fix Packs have been released), you may decide to install a lower-level Fix Pack.
CAUTION: If you revert to the version 8.1.1 base installation, change request fixes and new functionality added in any or all Siebel Fix Pack 8.1.1.x releases are no longer available, until an applicable Fix Pack has been installed. You will also need to take steps described later in this topic, under guidelines and limitations.
Related Topics Enhancements and Updates in 8.1.1.x Fix Packs on page 46 Resolved Change Requests on page 103.
Instructions for Uninstalling a Siebel Fix Pack

This topic is part of Uninstalling Siebel Fix Packs on page 101. Follow the instructions below to uninstall the installed Siebel Fix Pack 8.1.1.x release and revert to the version 8.1.1 base installation. For more information about running uninstaller programs and about uninstalling Siebel base installations, see the Siebel Installation Guide for the operating system you are using. See also Enhancements and Updates in 8.1.1.x Fix Packs on page 46.
To uninstall the Siebel Fix Pack on Microsoft Windows 1

To uninstall a Fix Pack on Windows, use the Add/Remove Programs utility to run the uninstaller. NOTE: For applicable server-based modules, You can also invoke the uninstaller by running SIEBEL_ROOT\_uninst\product\uninstaller.exe, where product is one of the following values: ses (for Siebel Enterprise Server components) or eappweb (for SWSE).
At the prompt, select Maintenance Release Uninstall.
102
Siebel Maintenance Release Guide, Version 8.1.1.5, Rev. B Resolved Change Requests
To uninstall the Siebel Fix Pack on supported UNIX or Linux platforms 1

To uninstall a Fix Pack on UNIX or Linux, run the following command: $SIEBEL_ROOT/_uninst/product/uninstaller optional_arguments where:

product is one of the following values: ses (for Siebel Enterprise Server components) or eappweb (for SWSE) optional_arguments is one or more valid arguments for the uninstaller. For example, specify -is:javaconsole -console to run in console mode.
At the prompt, select Maintenance Release Uninstall.
Guidelines and Limitations for Siebel Fix Pack Uninstallation

This topic is part of Uninstalling Siebel Fix Packs on page 101. Note the following guidelines and limitations related to Siebel Fix Pack uninstallation for installed Siebel software: Separate uninstallation of a Fix Pack is not supported for Siebel Mobile Web Client or Siebel Tools. Only the full uninstallation option is possible for these modules. If a Fix Pack installation fails, it is recommended that the administrator attempt to uninstall and then reinstall the Fix Pack. If the uninstaller for the Fix Pack is not available, proceed with reinstalling the Fix Pack. If these steps are omitted, future attempts to uninstall the Fix Pack may fail. If you made any repository or configuration changes related to a Fix Pack you have installed, then, before uninstalling the Fix Pack, the repository or configuration must be restored to the state when the Fix Pack was first installed.
Resolved Change Requests

The table in this topic provides a list of resolved bugs that are included in the Siebel 8.1.1.5 Fix Pack. Customers using version 8.1.1 or a prior Siebel Fix Pack 8.1.1.x (where applicable) should install the latest 8.1.1.x Fix Pack. Unless specifically noted in the table, all known anomalies from the base version remain unresolved.
For each release, the resolved changes tables include the following columns: Issues Addressed. The description of the issue. Bug ID/Fix Request ID. The tracking number for the fix request associated to the product defect. Base Bug ID/Change Request ID. The tracking number for the product defect associated with the fix request. Subcomponent. The second-level categorization for the product defect.
10 3
Siebel Maintenance Release Guide, Version 8.1.1.5, Rev. B Resolved Change Requests in the Siebel 8.1.1.5 Fix Pack
Special Instructions. 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.
CAUTION: If you have installed a Quick Fix, please review Quick Fixes Included in the Siebel 8.1.1.5 Fix Pack on page 8. This section contains the following topic: Resolved Change Requests in the Siebel 8.1.1.5 Fix Pack on page 104
Resolved Change Requests in the Siebel 8.1.1.5 Fix Pack

This topic is part of Resolved Change Requests on page 103. Table 4 lists the bugs that were resolved in the 8.1.1.5 Fix Pack. NOTE: As of the Siebel 8.1.1.5 Fix Pack, the resolved bug information is classified by product name, component description, and subcomponent description (if applicable). These categories correspond to the CR Area and CR Subarea categories for previous Fix Pack releases, with the addition of a subcategory.
104
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID Base Bug ID Subcomponent Special Instructions
Issue Addressed
Siebel Apps Customer Order Management

Application Deployment Manager
ADM is not able to export/ import the Catalog/Category record due to Integration Object issues 10605169 10599327 Customer Order Mgmt
Comm/Energy
Clicking the Transfer Service button adds inactive assets to quotes 11069497 Workflow Yes, see Instructions for Bug 11069497 on page 141.
Customizable Prod/ Configurator

Configurator product instances are deleted if RaiseErrorText is used in the script Cardinality/constraint rules do not work Compatibility rule error messages are partially shown in ENU, not in the local language Eligibility and Compatibility rules inside Configurator web services An invalid error message occurs within the invocation of configurator/promotion validation step of the Verify(Order) workflow process. 11677160 Error Messages
10606183 10598936
10559334 10594166
User Interface Error Messages
10598213
10597497
Runtime
10599645
10597519
Runtime
10 5
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10601493 Base Bug ID 10599170 Subcomponent Runtime Special Instructions
Issue Addressed The Configurator UI does not display a red asterisk (required product) for a customizable product`s relationship where a min cardinality is defined and a promotion is associated to this CP Modifying multiple assets created by different users causes an error BeginConfiguration returns an empty tag <DomainItem/> for ineligible child products In Product Configurator, the Summary tab does not display products that break eligibility rules Remote Product Configurator cannot solve all conflicts at once When a script is validating an attribute and using SetAttribute to change its value, this can cause the constraint based over the attribute to fire and display the error message incorrectly
10602112
10600499
Runtime
10602999
10601387
Runtime
10601718
10601715
Runtime
10603752
10603058
Runtime
10606288
11071206
Error Messages
Order Administration
When network nodes or network connections are modified, the Due Date popup window does not show futuredated orders 10605214 10605212 Quote/Order Validation
Pricing Mgmt
Adds Version and Date fields within Pricing Designer for product and promotion administration 10604001 10599850 CP Pricing Designer
106
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10601799 Base Bug ID 10600032 Subcomponent Dynamic Matrices Special Instructions
Issue Addressed When an attribute adjustment has a DATA_TYPE of number and the value is greater than 999, the attribute adjustment is not applied properly
Product Administration
Within eConfigurator, ineligible products saved in a current configuration are not displayed in red Constraints using selection of products from class do not work The Upsert method of the Product Import business service should not cause the Synchronize method call of the EAI Siebel Adapter business service The ABO Bulk Request Component Product pick applet crashes with a large number of components Coupon promotion does not display correctly inside Configurator Product import errors or import warning reports are displayed in a popup window instead of prompting the user to download the report Users cannot import a child product that has a class relationship when a class has not been defined Default cardinality on products is not honored when a product is used in a promotion 10534651 10533693 Eligibility & Compatibility
10606479
10543644
Products
10568078
10561828
Products
Yes, see Instructions for Bug 10568078 on page 141.
10598396
10595706
Compound Product
10599164
10598714
Product Classes
10598786
10598785
Migration
10604058
10598903
Migration
10598992
10598872
Runtime
10 7
Table 4.
Issue Addressed
Quotes & Orders

The application hangs when adding customizable products to a quote 10602944 10597914 Line Item Details
Siebel Apps Data Quality

Data Quality
Crashes occur with the Deduplication business service when the Contact Key business component is released "In version 8.1.1.4 SIA with SSA Deduplication enabled, when users add a duplicate account and pick a duplicate account or contact to merge in the popup applet, they receive the following errors: SBL-DAT-00227: Unable to create the Business Service 'DQ Sync Services' SBL-DAT00144: Could not find 'Class' named 'DQ Sync Services'. This object is inactive or nonexistent. Deduplication does not work for some of the fields in the Contact and Account views 11738034 Real-Time Deduplication
11699398
11696864
Data Quality
10601612
10588363
Real-Time Deduplication
Siebel Apps Field Service

Field Service
The Preventive Maintenance engine queries fpr PM Plans other than the PM Plan against which it is being run, which causes problems for users with large datasets 10571656 10568862 Preventive Maintenance
108
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10591214 Base Bug ID 10585593 Subcomponent Dispatch Board Special Instructions Yes, see Instructions for Bug 10591214 on page 142.
Issue Addressed With Gantt Chart applets, when colors are overlaid, the colors do not display properly
The Holiday API Service GetResponseTime Method is giving incorrect results Within the Dispatch Board, the drag-and-drop functionality does not work properly
10591565
10586837
Error Messages
10596090
10590959
Dispatch Board
Scheduling
ACR 484: Provides an integration between Siebel Field Service and Oracle Real Time Scheduler 10596175 10582764 Optimizer Yes, see Instructions for ACR 484 on page 21.
Siebel Apps Handheld Client

Handheld Client
Characters are being corrupted during outbound transport When users click the Deliver button, the application hangs, and the log file displays an exception The Prepare Visit functionality consumes much more memory than in previous versions of the application Slow navigation occurs because totals in list applets are recalculated on every getfocus After 8.1.1.3 WM5 [21219_2] is applied, the UI behaves slowly 10605896 10584241 SMQ Messaging
10600071
10600052
CG App
10601463
10600657
CG App
10604840
10600661
User Interface
10603021
10601356
User Interface
10 9
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10604842 10605763 Base Bug ID 10604032 10605216 Subcomponent CG App CG App Special Instructions
Issue Addressed The List Products button does not perform properly Voiding a fully paid invoice does not change the available credit The Field Read Only user property does not work on multi-value fields
11802807
10606225
Client App
Handheld Sync
The BatchSync task fails after Bug BUG 10588005 (CR#121X7WAZN) is applied Handheld Sync cannot open and close the connection An infinite loop occurs when the network fails during DSS Provides enhanced DSS Handshaking and synchronization session tracking Handheld: Patch Agent fails after 8.0.0.2 [20412_9] has been applied Users must restart the application after an error occurs during synchronization 11905212 Direct Server Sync 10529580 10585400 10588005 Direct Server Sync Direct Server Sync Direct Server Sync
10605060 10589719 10589654
10591571
10591406
Patch Deployment
10593811
10592420
Direct Server Sync
Siebel Apps Marketing

Mktg/Campaign Mgmt
When users select one record and click the Generate Output Lists button, two lists are generated 10560735 10557298 Campaign Manager UI
110
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10572773 Base Bug ID 10570959 Subcomponent Campaign Processing Special Instructions
Issue Addressed The Stage Execution process fails with the following error: SBL-DAT-00523: The selected record has been modified by another user since it was retrieved. Please continue. Makes the Trackable URL functionality optional A trigger cannot be loaded more than twice for the same contact The list distribution record is removed after a campaign is launched In campaign allocation, assigning 0 to a certain segment should not export any contact in that segment Contacts in the deleted lists in the program designer should not be addressed in the campaign
10602182 10601450
10592525 10598328
Treatment Campaign Processing Campaign Manager UI Segments
10603117
10600264
10605179
10602056
10605063
10604117
Campaign Manager UI
Mktg/Email Marketing
Russian characters are not saved with the correct encoding in the HTML editor 10566327 10565408 Email Editor
Mktg/Events
When a user clicks Invite to invite a user to an event, an error message displays 10565850 10561856 Customer Views
Mktg/Leads
Sending an email from the My Leads view by selecting F9 populates the "To" field with "Lead Detail Form Applet (Detail)" 10606270 10603004 Lead UI
11 1
Table 4.
Issue Addressed
Mktg/List Management
List Import does not accept Job Input arguments Even after the fix provided by CR # 12-1XCM9RR, Marketing imports continue to fail When a contact is promoted, deduplication does not work as expected Error messages do not contain specific information during the list import process 10602184 10601824 10592716 10599065 List Import List Import
10601306
10601232
Promotion
10601721
10601668
List Import
Mktg/Marketing
Users receive an error message when saving a Web treatment 10604326 10604325 Error Messages
Mktg/Web Marketing
The location of the Save Content button is not consistent between screens 10536023 10527141 Surveys and Landing Sites
Siebel AppsMultichannel Technologies

Communications Server
F9 functionality: On the Mobile Web Client, when a language is set that is different than the language that was set for templates, the timestamp for the Mobile Client language is overwritten by the template language setting 10604412 10604360 Outbound Communication Email
CTI
112
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10600434 Base Bug ID 10589061 Subcomponent Client Special Instructions
Issue Addressed Business Services that contain GotoView() does not work when invoked from CTI EventLog With Internet Explorer 7, the ACD Transfer Group Call Applet appears behind the main Siebel application window
10597569
10593154
UI Configuration
eMail Response
Users must click the Send button twice when replying to email messages 10601855 10599067 Email Response View
Siebel Apps Oracle Customer Hub

Universal Customer Master
When UCM Merge is performed on the Oracle Database, the Unique Constraint error message appears 10602108 10597384 Data Management
Siebel Apps PRM

PRM Partner Portal
Within Activities > Activities List, only the upper part of the "Activities List" text appears 10599693 10599646 Other
Siebel Apps Sales

Forecasts
11 3
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10603019 Base Bug ID 10594273 Subcomponent Forecasts Special Instructions
Issue Addressed When the user is on a forecast view, such as All Forecasts Across Organizations view, with a PDQ is enforced (such as only forecasts for current week are displayed or a particular date), when the user navigates from this view to other forecast view, all subordinates' forecasts, including forecasts from previous weeks/years, are displayed on this view. Forecast adjustment is not updating when the product is adjusted in the Summary View tab
10605255
10600295
Forecasts
Opportunities
Within the Sales Pipeline Phases Analysis view, the wrong value displays for the % of Revenue Quota Data Restricted Function not working with `&` in Query Value on Revenue List Applet in 8.0 10581146 10572148 Opportunities
10601946
10597033
Revenues
Siebel Apps Search & Knowledge Management

Search - Oracle SES
Searchable fields in the search results view are not being shown 10601893 10543253 Results UI Yes, see Instructions for Bug 10601893 on page 142.
114
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10602264 Base Bug ID 10596554 Subcomponent Indexing Special Instructions
Issue Addressed Deleting all SES indexes from the eCustomer application causes it to use other indexes. After ACR 439 has been implemented, File System or Web sources are not retained after searches are performed In version 8.1.1.3, within the Advanced Search applet, the Clear All button is disabled After 8.1.1.2 QF02AP has been applied, the application hangs when users navigate between Search and Find categories
10602949
10598897
Search Center
10602094
10602093
Advanced Search
10605908
10603598
Connectors
Siebel Search
When two search categories are configured from one BC, and users perform a search after they select only one category, the search is performed on both categories even if only one was selected When the Siebel application has been configured for a language other than ENU, and the Siebel Search functionality is configured (Siebel Search integrated with OSES), when users search, the Search Results view displays words that have not been translated OSES: Once a Find category is selected, only Find categories are available in the Look In drop-down list 10602434 10577630 Advanced Search
10597045
10589207
Results UI
10600341
10589726
Search Center
11 5
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10604372 Base Bug ID 10594274 Subcomponent Results UI Special Instructions Yes, see Instructions for Bug 10604372 on page 143. Yes, see Instructions for Bug 10602262 on page 144.
Issue Addressed It is not possible to customize results teasers for search categories that are based on Attachment business components Within Search Center, the Clear button does not work
10602262
10599519
Search Center
Siebel Apps Service

Assignment Manager
Provides an All, Best Fit rule for Assignment Manager Assignment Manager does not assign employees correctly Within Assignment Manager, rule loading takes over two hours A performance issue occurs because of a conflict between the Employee Team Score column and the All Above Minimum condition 10554091 10563494 10571262 10543054 10558678 10561766 Batch Assignment Interactive Assignment Server Processes
10588378
10587333
Server Processes
SmartScript
If a SmartScript is running in Standard Interactivity mode and it has two questions on two separate pages, the focus is lost Search specifications are not invoked if tree explorer navigation is used When the same SmartScript is run simultaneously in the Web client, the wrong data is saved 10550708 10546684 eSmartScript Yes, see Instructions for Bug 10550708 on page 144.
10601258
10532326
Administration
10592482
10591844
Administration
116
Table 4.
Issue Addressed
Siebel Apps Territory Management

Territory Management - Sales
It is not possible to limit the amount of data on which the alignment process should operate on with the Alignment Periodic Runs workflow 10589744 10588325 Territory Management
Siebel Apps UCM

Universal Customer Master
Link/Update and CreateNew does not set the new address as the primary address for the Contact even when the S_UCM_ADDR_PER.PR_CHILD _FLG = 'Y When there are more than 150 records in matching results, the Siebel application crashes when running a batch request AIA MDM 3.1: Person/Org merge events are not published with Operation = Merge 11717148 Incoming Duplicates
10606222
10606223
Deduplication
11693101
Merge Request
Siebel Automotive
Warranty Management
ACR 525: Provides the Warranty Management System 11058413 10603423 Yes, see Instructions for ACR 525 on page 22.
11 7
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 11058448 Base Bug ID 11075793 Subcomponent Special Instructions
Issue Addressed ACR 525: Validation Messages are not populated in Warranty Claim
Siebel Consumer Goods

Calendar
Visit Planning drag-and-drop functionality does not work 10600655 10599120
Sales Volume Planning

Auto query applied on Products Baselines changes the values in Category Baseline Allocating 0 may result in a -1 in the product baseline record 10603845 10603842
10603419
10599016
Siebel Communications and Energy

Integrations
ACR 474: Optimizes the payload size for Submit Order functionality 11824787
Order Management
Changes the Effective Adjustment field from Date type to UTC Date-Time type The One-Time Payment check box is not checked by default when a payment form is submitted 10601341 10600311
10601366
10590790
118
Table 4.
Issue Addressed The Siebel application does not clear the Fulfillment Status and Status Context information for cancelled orders. Move Order Transfer results in an empty Status As of header field
10601368
10590774
Siebel Core Accessibility

Generic
The applet name is not appended to the applet buttons ACR 600 provides functionality that is required for screen readers. For more information about this enhancement, see Enhancements and Updates in Version 8.1.1.5 on page 17. ACR 604: Provides the ability to rename frame titles so that screen-reader users know what the frames are ACR 604: Provides an indication of the active tab other than by color only ACR 604: Adds a warning message before session timeout occurs, and provides an option to extend the time available Within timesheets, Submit To information is required, but the field has a picklist, and so it is not accessible Drop-down (SELECT) elements do not have HTML TITLE specified 11783087
10605972
10601068
Section 508 Compliance
11924114
Yes, see Instructions for ACR 604 on page 51.
11924337
11924380
Yes, see Instructions for ACR 604 on page 51. 10591099
10591100
10604193
10596761
11 9
Table 4.
Issue Addressed
Siebel Core Common Components

Security
Home page shows different data set after installing Quick Fix 7.8.2.14 QF[0E11] 10606073 10604234 Access Control
Siebel Core - DB Deployment and Configuration

Server Infrastructure
The Siebel Gateway Server cannot connect to the database On Microsoft Windows, it is not possible to deploy a new SRF with no downtime Crashes occur with Siebel applications running on Microsoft Windows 2008. A Siebel Gateway Server siebsvc process memory leak occurs 10644594 10642971 Name Server
10644061
10643152
Common Core Facilities Common Core Facilities Name Server
10643513
10643446
10644914
10644004
Siebel Core - DG Deployment

Application Deployment Manager
120
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10604871 Base Bug ID 10602732 Subcomponent Framework Special Instructions
Issue Addressed During the ADM package deployment process, if users execute 20-30 (or more) times the command status_all, they receive the 'Error executing SQL statement 'ADM_SQL_GET_LATEST_SES SIONS_BY_PACK_NAME'.(SBL -DMJ-00167)" error message
Siebel Core - EAI

Integration Business Services
In version 8.1.1.3, the error level for EAISiebAdptWrn is incorrect When a price list item is inserted using Siebel EAI Adapter, a new Select statement is run that is not part of the EAI Siebel Adapter call 10603116 10602997 EAI Siebel Adapter EAI Siebel Adapter
10604419
10603553
Web Services
Version 8.1.1.4 crashes when calling a Web service 11675131 Outbound
Siebel Core - EIM/ Database

Transaction Merger truncates long kanji strings 10594061 10594057 ODBC.
Siebel Core Globalization

Automotive
Possible Buffer Overflow issues Unauthorized access to the application is possible 10600525 10604139 10582924 10602188 Localization Localization
12 1
Table 4.
Issue Addressed
Siebel Core - PIM Integration

Client Sync
Addresses performance and stability issues During sync, the password dialog box does not appear In Lotus Notes Sync - Auto Sync mode, when users are not connected to the network, they receive an error message Incorrect logging occurs with UserMailBoxIDSource Conflict resolution behaves opposite to the settings Calendar entries that contain special characters cannot be synchronized Duplicate calendar items are created After users configure the siebelsettings.cfg file, click the Configure button, and receive confirmation that the sync options are allowed, when they click OK to navigate back to the main screen, they receive an error message When bi-directional sync is configured, and auto-sync is turned off, when users perform a manual sync, the sync window runs for an hour, and then the application crashes 10592665 10592669 10598449 10591227 10591919 10597457 Lotus Notes Lotus Notes Lotus Notes
10580213 10605068 10590036
10580210 10604687 10588431
Outlook Outlook Lotus Notes
10600945 10601936
10599949 10600664
Lotus Notes Other
10601820
10601310
Lotus Notes
122
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10605180 Base Bug ID 10601383 Subcomponent Other Special Instructions
Issue Addressed Within Siebel Sync 8.1.1.2 (PLK), when users click the Configure button (left most button), the configure screen does not appear and the log file contains the following error: "Error: Can't get language identifier. Provides support for Office 2010.
12319296
10595710
Outlook
CRM Desktop
ACR 464: Provides support for Siebel CRM Desktop for Outlook 2010 Checks in the CRM Desktop Client After users upgrade to version 8.1.1.4, the Predefined Queries field is missing User-defined opportunity statuses are ignored during upstream sync The Repository Import script attempts to import all languages Preserves the "Save Correspondence" flag during re-extract Adds non-ENU seed data Provides server-side seed data for Lotus Notes Corrects a problem with seed data for ACR 464. 10575809 10575810 Installation
11707103 11845639
10606003 11845636
Outlook Client Outlook Client
11707112
11702642
Data Sync
10592975
10587729
Installation
10596772
10596768
Data Sync
10597061 10597071 10599644
10597058 10597068 10599582
Admin Admin Installation
SSSE
The PIMSI Dispatcher Component behaves slowly 10603355 10598574 Performance
12 3
Table 4.
Issue Addressed
Siebel Core Server BizLogic Script

Config - Scripting
RaiseErrorText in BusComp_ChangeRecord event gives incomplete error information After an upgrade, eScripts with strings that contain "\n" are not being interpreted When using the data transformation engine on very large messages > 2000 records a runtime error occurs 10603596 10558349 T Engine
10603756
10567447
T Engine
10599978
10598988
T Engine
Integration Scripting
A core dump occurs 11060658 10601643 New eScript Engine
Siebel Core Server BizLogic WF

Business Process Framework
A task loop that creates a new child record in the loop yields the SBL-DAT-00393 or (SBLDAT-00468) error messages During TBUI Tasks, the server time-out error occurs The TBUI upsert operation causes an "end of file" error message 10594880 10594436 Task Controller
10600334 10599922
10595535 10597741
Task Controller Task Controller
124
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10598452 Base Bug ID 10598195 Subcomponent Task Controller Special Instructions
Issue Addressed When the Siebel Defer Write parameter = False and Task Transaction Property - False, the following error appears: "Can't write data without validation.(SBL-DAT-60217) When a task is initiated when the focus is on the standard error applet, the application crashes
10601631
10600697
Task Deployment
Siebel Core Server Infrastructure

Security
SSL with key bit lengths of 2048 or 4096 bits is not working 10602058 10515102 Transport Layer Encryption
The Flush FDR command does not generate FDR files When more than fifty processes are started within a few seconds, siebsvc crashes 10632036 11726368 10514239 10644912 Server ManagerGUI Siebsrvr and Shells
Siebel Core Server OM Framework

Subtask data does not appear after the parent task is paused EAI XML Converter throws an error because INTOBJNAME is required 10585140 11778219 10584161 Temporary Storage Task Transaction: Other Yes, see Instructions for ACR 713 on page 56.
12 5
Table 4.
Issue Addressed
Siebel Core Server OM Svcs

Audit Trail
There is no Audit Error event to monitor audit failures Audit Trail records are created when records are deleted in the Cloned BC even though the Audit Trail is not set up for that business component 11721518 10604535 10603889 Audit Trail Audit Trail
Config - Rules
When HTML and javascript are placed in the "include expressions" for a salutation applet, the actual markup language is shown, not the intended result. 10599650 10565045 Personalization
Integration Transport
JMS Receiver does not work for distributed queues 10590840 10590076 JMS Transports
Object Manager
Within Campaigns > Design > Offer, when users add ten offers simultaneously from Add Offer, and then move to another record, the Cannot locate record within view: Campaign Literature View Admin applet: Campaign Parent Offer List Applet (SBLUIF-00269) error message appears Siebsrvr components that do not use the DBConn layer for connections do not restart after a warning message from DB2 is received 10566498 10561779 Other
10601772
10584841
Other
126
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10600389 Base Bug ID 10599508 Subcomponent Business Services Special Instructions
Issue Addressed If an Encoded File size is larger than 24KB and if the string being passed contains special characters (such as >), the application hangs
Security
If a password is expired, the login process fails. 10595902 10592880 ADSI Security Adapter
Siebel Core Tools

Config - Repository
Popup Visibility Auto All BC property does not always work depending on how compilation is done The PHYSICAL_TYPE and TEXT_LENGTH attributes are missing in the consoleapp.sif file 10603114 10563034 Compiler
10601923
10599370
Tools Validator
Siebel Core - UIF Client

Calendar
With Internet Explorer 6 and Internet Explorer 7, users encounter the following error message when navigating to the calendar: An error has occured in the script on this page After 8.1.1.2 QF0244 has been applied, users receive the SBL-DAT-00471 error message when they drill down from the Home page to the calendar 10591191 10591190 User Interface
10605745
10598842
User Interface
12 7
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10603331 Base Bug ID 10600837 Subcomponent User Interface Special Instructions
Issue Addressed In the CSY version of the application, the days are translated incorrectly within the Calendar pick applet When users create a new calendar appointment and drill down into it, click the Add Contact button, select a contact from the list, and click OK, the "Invalid operation when not executed" error message appears An error occurs while executing the SQL statement 'ADM_SQL_GET_LATEST_SES SIONS_BY_PACK_NAME'.(SBL -DMJ-00167)
10601917
10601073
Logic
10604495
10602787
User Interface
User Interface
In versio 8.1.1.3, after QF0357 has been installed, auto focus is on fields. After users upgrade to version 8.1.1.4, the Predefined Queries field is missing Calendar applet buttons and layout are lost after applying Windows Update KB2360131 Internet Explorer crashes after users click F5 to refresh When a parent company is entered in the Account Hierarchy applet, an end-offile error message occurs In version 8.1.1.3, when S_ORDER.ACTIVE_FLG is set to N, the Standard Interactivity client hangs Within Accounts > Account List > List Applet, URLs do not launch 11071321 10532612 Behavior
11700390
Behavior
11693454
11059048
Behavior
10603938 10605999
10593426 10598100
Popups Popups
10603870
10603869
Behavior
11658630
10605558
Behavior
128
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 11695178 Base Bug ID 10606532 Subcomponent Behavior Special Instructions
Issue Addressed Allows users to disable personalization at the applet level
Siebel Core - UIF Server

Accessibility
The Retry, Cancel dialog box appears after users have made changes and saved them When users click CTRL+SHIFT+A to invoke the Site Map, wait for the session timeout warning message to appear, and click OK, the SBLUIF-00313 error message appears. Provides shortcut keys for OOTB Query Assistant and Update Audit Cache When you press Insert + F7 in Jaws, column headings are not labeled 10604817 10604816 User Interface
10604827
10604820
User Interface
10594856
10576292
User Interface
10585847
10583643
User Interface
Client Import/Export
When using Import object functionality in the client, the log file with highest log level setting = 5 does not say which record caused the error 10598784 10564937 Client Import
Config - Repository
When users log in and out of the Web Client, the memory consumed is not released, and a memory leak occurs as users continue to log in 11871308 11850195 UIF
Config - Scripting
12 9
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10600928 Base Bug ID 10577300 Subcomponent Browser Scripting Special Instructions
Issue Addressed The Clib.system() method has a runtime error if a command is greater than 255 characters
User Interface
When users click the Previous Record button, they receive the SBL-DAT-0036 error message When users select Menu options when the focus is in a List Management applet, popup windows do not display If users add a new checkbox to the UI using Siebel Tools, and then enter a data record where the field has been checked, the value does not show as checked after a Refine Query operation Drop-down boxes appear and disappear Provides "Undo Query" and "Undo Record" keyboard shortcuts for Siebel applications in SI+ mode DefaultFocus_New does not work on 8.1.1 releases When users use Change Records to set fields to null, it only works for the "1st Field to Change" in the Change Record applet Incorrect translations appear on the FRA calendar The Auto Toggle functionality does not behave as expected for the CTRL or SHIFT click shortcuts 10597212 10523165 Controls
10546419
10543288
Toolbars, Menus, Keyboard
10604684
10545952
Query
10580076 10594855
10578064 10583314
Controls Toolbars, Menus, Keyboard
10587144 10589053
10587142 10587089
Controls Controls
10603674 10597120
10589917 10594601
Controls Layout and Rendering
130
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10600885 Base Bug ID 10595660 Subcomponent Query Special Instructions
Issue Addressed When the Auto Query Mode, New Query applet property is enabled, causes navigating to causes nav to view w visibility dropdown to not work? Menus stop working after users preview a search result Applets with controls that have HTML Type as 'PlainText' do not show any title information
10601608 11689460
10599601 10605594
Toolbars, Menus, Keyboard Controls
Siebel Core - UIF Task Based UI

In the TBUI, child applets are not updated when the parent applet MVG is updated Splitting the entry of mandatory data across two task views may not properly notify the user of required data When users navigate between views in FS Asset To Contract Task, the following error may appear from the Agreement Detail task view: "Error: Attempting to show a task view in Agreement Detail Task View when no task is running. 10588004 10584539 Task View
10602789
10602788
Task View
"10604210
10603053
Task View
Siebel Core - UIF Web Gateway

13 1
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10602274 Base Bug ID 10602266 Subcomponent SWSE Special Instructions
Issue Addressed An anonymous session is created when the application is exited in cookieless mode
Siebel Core UNIX

Platform Support
ACR 705: Certifies IBM HTTP Server v7 on AIX 6.1. ACR 707: Certifies Sun Java System Web Server 7 on Solaris 10. If users increase MinMTServers=50 and set PreLoadSRF=True on an Application Object Manager OM and then start the Siebel Servers, the 'SBL-DAT-00142' error message appears in the AOM log files. 11071572 11071263 AIX 6L v6.1 Solaris 10/Sparc
10601215
10558665
AIX 5L v5.3
Siebel Core Windows

Platform Support
Certifies Microsoft Windows 2008 R2. 12622502
Siebel Documents
Documents
The eDocument Server is not able to generate correspondence With Microsoft Windows 2008, users receive errors when trying to use templates in the Correspondence screen 11774163 10596955 Correspondence
10639775
10605734
Correspondence
132
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10604766 Base Bug ID 10601353 Subcomponent Correspondence Special Instructions
Issue Addressed Clicking Ctrl + L does not generate correspondence if the focus is not applied to the Service Request list
Document Administration
Office 2007 supports documents that are not available in the Correspondence MVG 11881958 Correspondence Template
Siebel Engineering
Rel Eng/Build System
ADM deployment fails in version 8.1.1.4 10605916 10605914
Siebel Financial Services

Relationship Hierarchy
The Relationship Hierarchy view allows access to All Accounts Across Organizations 11816476 10566015
Siebel Life Sciences

Analysis
The system displays menu items that are not actionable 10592644 10511614
Calendar
In LS Pharma HI Activity Calendar View (Calendar > Calendar) drill-down functionality does not work properly in version 8.1.1.3 10600671 10599426
13 3
Table 4.
Issue Addressed
Clinical Payments
ACR 713: The payment request status changes to Request Failed When the SWI LS Clinical Payments Inbound Web service is imported, an error message displays 11722353 11778219 Yes, see Instructions for ACR 713 on page 56. Yes, see Instructions for ACR 713 on page 56.
10605937
10604774
Clinical Programs/ Protocols

ACR 713: Provides the modifications needed to support Oracle Clinical Trial Payments: Siebel Clinical Partial PIP. The Site Date Full Rollup and Region Date Full Rollup business component user properties do not work as expected Rollup occurs incorrectly for the last subject of a study date 10605936 10586654 Yes, see Instructions for ACR 713 on page 56. Yes, see Instructions for Bug 10603402 on page 144. Yes, see Instructions for Bug 10603259 on page 144. Yes, see Instructions for Bug 10587047 on page 144. Yes, see Instructions for ACR 713 on page 56.
10603402
10603388
10603259
10594500
After an account is associated with a protocol, merging an account causes data loss at the protocol level ACR 713: The payment request status changes to Request Failed Removal of a site under region A resets all values in another region where no site info=Y
10587047
10585751
11722353
11778219
10601424
10588071
134
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 11881167 Base Bug ID Subcomponent Special Instructions Yes, see Instructions for Bug 11881167 on page 145. 10594497 Yes, see Instructions for Bug 10601440 on page 145. Yes, see Instructions for Bug 12311668 on page 146.
Issue Addressed Deleting an activity template removes the record from the Activity Plan tab
The Last Subject of Study field displays as blank if the subject data is not available
10601440
Deleting the SVT removes site/subject activities
12311668
11881167
Other
Rewrites the WPTG_TBT:Q&A169253 & 169258 report headings 10601420 10596278 Yes, Instructions for Bug 10601420 on page 146.
Clinical Trip Report

When the status of the Trip Report Site Visit is changed, an error displays 11723179 Yes, see Instructions for Bug 11723179 on page 147.
Regulatory Reports
MDV device information section: Country information is not displayed in Address 11731803 Yes, see Instructions for Bug 11731803 on page 147. 11731750 Yes, see Instructions for Bug 11731750 on page 147.
The MDV Manufacturer Narrative Field value does not display a space before the text
13 5
Table 4.
Issue Addressed MDV (All Formats): The Associated Products tag is missing for all formats (PDF, RTF, HTML, EXCEL, PPT) MDV (All Formats): The alignment of the Report Date, Manufacturer Awareness Date, Reporting Firm Name, Authorized Representative, Device and Evaluation Result fields is not in sync with the other fields Within Site Management > Protocol Site List (My Sites), fields that should be read-only are not read-only, and fields that should not be read-only are read-only
10599874
10599714
10606117
10577421
Siebel Loyalty
Products
An extra single quote in code prevents members from redeeming points 10606297 10606026
Promotions
When a promotion is inactivated, the bucket attributes cause an error message 10605425 10603246
Redemption
The Loyalty Redemption Service GetQuoteTask method retrieves all quote items in the system rather than just the items associated with a quote 10606469 10605707
Tier Engine
136
Table 4.
Issue Addressed While processing transactions, LOY Processing Engine does not advise when there is a pending tier approval
Tiers
Qualifying points are cleared when a manual tier change is performed 10603087 10597381
Transaction Engine
Supports decimal and nondecimal points in Siebel Loyalty processes 10606137 10604040 Yes, see Instructions for Bug 10606137 on page 148.
Transactions of sub-type Missing Accrual and type Accrual do not calculate base points according to the distance table
10602771
10600426
Section 508/ Accessibility

Drop-Down lists in List Applets are not labeled Drop-Down lists in List Applets are not labeled Drop-Down lists in List Applets are not labeled 10596910 10596911 10596912 10596796 10596797 10596798
Siebel Reports
Reports BI Publisher - Infra
ACR 633: BI Publisher: Allows users to schedule BIP Reports for a time frame of one month or more 10603594 10594275 Call Center Yes, see Instructions for ACR 633 on page 52.
13 7
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10581407 Base Bug ID 10580239 Subcomponent Connector Special Instructions Yes, see Instructions for ACR 633 on page 52. Yes, see Instructions for ACR 633 on page 52. Yes, see Instructions for ACR 633 on page 52.
Issue Addressed ACR 633: BI Publisher: Provides default Daily/Weekly/ Monthly reports that are assigned to the Calendar views ACR 633: BI Publisher: Extends the Reports Sharing feature to support multi-org ACR 633: BI Publisher: Provides a confirmation dialog box when Sample XML Data is successfully generated Removes the BI Publisher Server header pages from the My Jobs view MLOV values are not translated for multi-lingual BI Publisher reports Changing an employee's active position in a different organization is not reflected in the report output Within the Case List view, when users attempt to run a report with no output type, the error message does not specify the user's error The "Run Once", "Run Daily/ Weekly", and "Run Immediately" scheduling options behave differently than how the jobs are scheduled to be executed. The Time value in the BIP Reports Server - My Jobs - Schedules view does not reflect the time set in the "Schedule a Report" applet.
10603595
10597768
Connector
10603566
10582912
Connector
10591196
10591195
Connector
10602913
10565912
Connector
10594983
10570706
Connector
10603564
10579473
Connector
10603068
10586194
Connector
138
Table 4.
Resolved Bugs in the Siebel 8.1.1.5 Fix Pack Bug ID 10592538 Base Bug ID 10588602 Subcomponent Connector Special Instructions
Issue Addressed Suppresses the Output Type dialog box, so that users who only have one report output type do not have to click Submit Parent selected records behavior does not include related child records when a view displays both parent records and child records in independent list applets BIP reports do not display time information using User Preferences Timezone BI Publisher reports cannot run with predefined queries that use the Today() function Case-insensitive search behaves inconsistently
10594546
10590314
Connector
10596676
10592084
Connector
10596283
10594183
Connector
10603593
10594063
Connector
BI Publisher reports display only selected records when the reports are run from a Detail View BI Publisher reports do not recognize language-specific predefined queries Schedule Reports functionality fails with a non-ENU object manager Automatic purging of BI Publisher reports does not recognise User ID input. When users execute a BI Publisher report on the Dedicated/Mobile Web Client, the line break appears twice
10594806
10594265
Connector
10596597
10595312
Connector
10597598
Error Messages
10602931
10598837
Connector
10601780
10600730
Connector
13 9
Table 4.
Issue Addressed
Siebel Server Remote

File System
When users attempt to open attachments, the system hangs Improves Siebel File System performance 10583657 10582435 Attachments
10598627
10593444
Utilities
Remote
SQL issued for merge operations takes over ten minutes to complete 10599599 10597467 Data Merge Yes, see Instructions for Bug 10599599 on page 149.
Database initializiation fails at the dmutl2.exe step with MRG-00104 Thai language data that is entered on the Mobile Web Client may be truncated by the Transaction Merger
10601014
10598247
DB Init
10592989
10466469
Data Merge
Siebel Travel & Transportation

Other
ACR 495 provides Siebel Hospitality enhancements. For detailed information about the enhancements, see Enhancements and Updates in Version 8.1.1.5 on page 17. When a function line item is split-menu and the parent is a package item price, the data is not grouped by displayed name 10602687 10594221 Yes, see Instructions for ACR 495 on page 21.
10604987
10600251
Yes, see Instructions for ACR 495 on page 21.
140
Instructions for Bug 11069497

1 2
Log into Siebel Tools, and query for the SIS OM Move Process workflow. Modify the Read Current Service Items step with the following modified property details:

Input Arguments: Sequence:0 InputArgument:SearchSpec Type:Expression Value: '[Header.Service Account Id] = ' + '"' + [&Object Id] + '"' + ' AND
[Header.Service Point Address Id] = ' + '"' + [&Move Out Address Id] + '"' + ' AND [Header.Status] = ' + '"' + LookupValue('IMPL_PHASE', 'Active') + '"' + ' AND [Line Item.Status] = ' + '"' + LookupValue ('IMPL_PHASE', 'Active') + '"'
Save your changes, and deploy the revised workflow.

1 2 3
Within Siebel Tools, navigate to the Product Integration project, and lock it. Query for Product Import Business Service, and select Upsert Business Service Method. Add the following Business Service Method Argument:

Name = SyncChild Data Type=String Type = Input Optional = Y Storage Type = Property Display Name/Display Name String Override = SyncChild
Add the following Business Service Method Arg Locale:

Language Code = ENU Display Name = SyncChild Translate = Y
Add the following Business Service User Property
Name = SyncChild
14 1
Value = N
6 7 8 9
Compile the Business Service Object on the srf file Stop the Siebel Server. Replace the compiled srf file. Start the Siebel Server.

In Siebel Tools, configure the Z-Background Color Map user property of the 'FS DB Planned GanttChart AX Applet' applet to use : #Green#Blue#Red#

Apply Oracle SES patch 8230654 on top of OSES 10.1.8.4 for teasers to be displayed in the search results.

Edit "SearchResults.swt" to place <swe:form> as the first statement in the swt file and </swe:form> as the last statement in the swt file.

1
Within Siebel Tools, navigate to Symbolic String, and create a new record with the following values:

Name: SBL_RESET_CATEGORIES Current String Value: Reset Categories Project: Symbolic Strings Type: Conversion Translate: True Glossary: True
Navigate to Applet > Edit - Find Applet, and add a control with the following values:

Name: GotoSearch Caption String Reference: SBL_RESET_CATEGORIES Html Display Mode: EncodeData Html Row Sensitive: True HTML Type: MiniButton Method Invoked: GotoLookInSearchView Sort: True
142
Text Alignment: Left Visible: True Text Alignment-Label: Right
Navigate to Applet WebTemplate > Edit, and add an Applet WebTemplate Item with the following values:

Name: GotoSearch Control: GotoSearch Item Identifier: 144 Type: Control Upgrade Behavior: Admin Method Invoked: GotoLookInSearchView Sort: True Text Alignment: Left Visible: True Text Alignment-Label: Right
Within CCAppletSearchFind.swt, add the following: <swe:control id="144">  <td valign="middle" nowrap> <swe:this property="FormattedHtml" hintMapType="Control"/> </td> </swe:control>
Before </tr></table>

Add a "Show Description" parameter in the Search Engine settings. This parameter takes a TRUE or FALSE value. When TRUE is set, the description from the query response is shown as the summary/teaser. When FALSE is set, a small amount of text from the query response is shown as the summary/teaser in the Search Results. This parameter is applicable for a normal BC and an attachment BC.
14 3

Edit "SearchLookin.swt to replace <swe:form htmlAttr="onsubmit='SubmitSearch(); return false;'"> with <swe:form htmlAttr="onsubmit='return false;'">.

1 2 3
Within Siebel Tools, create a new view user property called "FocusFirstEditableControl" for the Smart ScriptPlayer View (eApps) view. Set the value for the "FocusFirstEditableControl" view user property to True. Compile the SRF.

In the eapps.cfg file, append SessionTimeoutWarning below Session Timeout and provide a value for SessionTimeout warning.

1 2 3 4 5 6 7 8
Log into Siebel Tools, navigate to Object Explorer > Business Component, and query for Clinical Region business component. Navigate to to Business Component User Property and query for "Site Date Full Rollup". Update the name "Site Date Full Rollup" to "Region Date Full Rollup". Navigate to Object Explorer > Business Component and query for Clinical Protocol Site BC. Navigate to Business Component User Property and query for "Region Date Full Rollup". Update the name "Region Date Full Rollup" to "Site Date Full Rollup". To test the user property behavior, update BC User Property to "Site Date Full Rollup" = Y and "Region Date Full Rollup" = Y. Compile the SRF.

1 2 3 4
Log into Siebel Tools, and navigate to the Clinical Site Last Subject Off Study Date Upsert Rollup workflow. Select the Sorting process property and change the Default String from "(ASCENDING)" to "(DESCENDING)" Publish and activate the new version of the workflow. Restart the Siebel Server.

1
Within Siebel Tools, navigate to the LS Clinical Protocol project.
144
2 3
Within Object Explorer, select the Link object. Create a new record with the following values:

Parent Business Component: Account Child Business Component: Clinical Protocol Destinationfield:Central Lab Id Name : Account/Clinical Protocol (merge)
Compile the link.

1 2 3 4 5
Log into Siebel Tools, navigate to Projects, search for the "LS Clinical Subject" project, and lock the project. Navigate to Link and search for "Subject Visit Templates/Visit Template Activities". Select the Cascade Delete property and update its value to Clear. Navigate to Business Component and search for "Subject Visit Templates". Select Business Component User Property and add a property with the following values:

Name: Deep Delete Value: Visit Template Activities Comment: Delete Visit template Activities when Subject Vist Template is deleted.
6 7 8
Navigate to Tools and select Compile Project. Compile the Subject Visit Template project. Restart the services.

1
Edit the "LS Clinical Site Site Terminated Date Update Rollup" workflow policy to add following new condition

Condition Field: LS Clinical Site No Subject Info Operation : <> Value: Y
Add a new workflow policy called "LS Clinical Site Site Terminated Date Update Rollup (Without Subject Info)" with the following conditions:

Condition Field: LS Clinical Site No Subject Info Operation : = Value: Y
Add the following Action: LS Clinical Site Termination Date Upsert Rollup (Without Subject Info).
14 5
Add the following arguments:

Argument : Process Name Value : Clinical Site Termination Date Upsert Rollup (Without Subject Info)
5 6 7 8
Navigate to Site Map > Administration - Server Management > Jobs. In the job list, click New. From the Component/Job drop-down list, select Generate Triggers. This creates a new line entry but does not start the task. In the Job Parameters list, click New to modify parameter settings, and create the following parameters

EXEC = True Priviliged User: <table owner> Priviliged user password: <table_owner>

1 2 3 4 5
Log into Siebel Tools, navigate to Project, search for the "LS Clinical Subject" project, and lock it. Navigate to Link and search for "Subject Visit Templates/Visit Template Activities". Select the "Cascade Delete" property and update its value to "Clear". Navigate to Business Component and search for "Subject Visit Templates". Select Business Component user property and add the following property:

Name: Deep Delete Value: Visit Template Activities Comment: Delete Visit Template Activities when Subject Vist Template is deleted.
6 7 8
Navigate to Tools and select Compile Project. Compile the Subject Visit Template project. Restart the services.

NOTE: This bug has a dependency on Bug 10601440, which is provided in the Siebel 8.1.1.5 Fix Pack. In addition, before you perform the following procedure, you must have installed and configured ACR 426. For more information, see the Instructions for ACR 426 section in the Siebel Maintenance Release Guide, Version 8.1.1.x on My Oracle Support.
1 2 3
Navigate to Administration - Business Process > Workflow Policies. Query for "LS Clinical Site Site Terminated Date Update Rollup (Without Subject Info)", and change its name to "LS Clinical Site - Site Terminated Date Update Rollup - Without Subject Info". Save the record.
146
4 5 6
Navigate to Administration - Application > Views, and query for "LS Medical My Product Issues RR eMDR Batch Audit View" Change the description to "LS Medical - My Product Issues - Regulatory Report - eMDR Batch Audit". Save the record.

1 2 3
Within Siebel Tools, navigate to Business Object, search for the "Clinical Protocol Site" Business Object, and lock the project. Expand the Business Object, and click on Business Object Component. Add a new record in Business Object Component with the following values:

Business Component = Clinical Attendee Static Link = Clinical Trip Report/Clinical Attendee Static
4 5 6
Save the record. Right-click on the Clinical Protocol Site Business Object, and compile it. Restart the services.

1 2 3 4
Log into the Siebel application. Navigate to Administration BIP Reports - Report Standard Templates. Query for MDV and upload the new template. Run the MDV report.

1 2 3 4
Log into the Siebel application. Navigate to Administration BIP Reports - Report Standard Templates. Query for MDV and upload the new template. Run the MDV report.

1 2 3 4
Log into Siebel Tools. Navigate to Views, and query for "Clinical Protocol Site All List View". Locate the Admin Mode Flag column and uncheck the flag. Right-click on the view, compile the selected object, and restart the applications.
14 7

1
Make the following changes in the S_LOY_TXN table:
a b 2 3 4 5 6 7 a a a a a a 8
Change Scale to 7 and Precision to 22 for the ORIG_POINTS column. Change Scale to 7 and Precision to 22 for the LOAN_BALANCE column.
Make the following changes in the S_LOY_ACRL_ITM table: Change Scale to 7 and Precision to 22 for the PRTNR_PT_DEBT_QTY column.
Make the following changes in the S_LOY_RDM_ITM table: Change Scale to 7 and Precision to 22 for the PR_DEBT_PT column.
Make the following changes in the LOY Accrual Item Locator business component: Change Type to 'DTYPE_NUMBER' for the 'Partner Points Debited' field.
Make the following changes in the LOY Member Accrual Item business component: Change Type to 'DTYPE_NUMBER' for the 'Partner Points Debited' field.
Make the following changes in the LOY Transaction Accrual Item business component: Change Type to 'DTYPE_NUMBER' for the 'Partner Points Debited' field.
Make the following changes in the LOY Member Tier business component: Change Type to 'DTYPE_NUMBER' for the Point 1 Value, Point 2 Value, Point 3 Value, Point 4 Value, Point 5 Value, Point 6 Value, Point 7 Value, Point 8 Value fields.
Make the following changes in the LOY Member Tier Retroactive business component:
a 9
Change Type to 'DTYPE_NUMBER' for the Point 1 Value, Point 2 Value, Point 3 Value, Point 4 Value, Point 5 Value, Point 6 Value, Point 7 Value, Point 8 Value fields.
Make the following changes in the LOY Member Services business component:
a a a a a a
Change Type to 'DTYPE_NUMBER' for the 'Points' field
10 Make the following changes in the LOY Member Services business component:
Remove the value for 'Scale' for the 'Points' field.
11 Make the following changes in the LOY Redemption TBC business component:
Change Type to 'DTYPE_NUMBER' for the 'Points' field.
12 Make the following changes in the LOY Member Redemption Item business component:
Change Type to 'DTYPE_NUMBER' for the 'Partner Points' field.
13 Make the following changes in the LOY Transaction Redemption Item business component.
Change Type to 'DTYPE_NUMBER' for the 'Partner Points' field.
14 Make the following changes in the LOY Quote Point Types business component:
Change Type to 'DTYPE_NUMBER' for the Fields 'LOY Point 1 2 Total', 'LOY Point 3 4 Total', 'LOY Point 5 6 Total', 'LOY Point 7 8 Total', 'LOY Points' fields.
148
15 Make the following changes in the LOY ABB Transaction, LOY Corporate Transaction, LOY Engine
Transaction, LOY Member Services, LOY Reissue Transaction, LOY Transaction business components:
a a
Change Type to 'DTYPE_NUMBER' for the 'Original Points' field.
16 Make the following changes in the Quote Item business component:

Change Type to 'DTYPE_NUMBER' for the 'LOY Points', 'LOY Points Total', 'LOY Points Txn Total' fields.
17 Make the following changes for the Quote Item business component: a a a a
Change Calculated Value for the 'LOY Points Total' field to [LOY Points]*[Quantity Requested]
18 Make the following changes for the LOY Transaction business component:
Change Type to 'DTYPE_NUMBER' for the 'Current Loan Balance' field
19 Make the following changes in the LOY ABB Transaction business component:
Change type to 'DTYPE->NUMBER' for the 'Points' field.
20 Make the following changes for the Order Entry - Line Items business component:
Change Type to 'DTYPE_NUMBER' for Fields: LOY Amount Max Total, LOY Points, LOY Points Max Total, LOY Points Total, LOY Points Txn Total, LOY Points Used Total fields
21 Make the following changes in the LOY Customer Action Business Service business service: a b
For the Order Entry - Line Items|LOY ABB Transaction FieldMap 137 business service user property, change the value to: Extended Line Total - Display|Amount Add a new user property called Order Entry - Line Items|LOY ABB Transaction FieldMap 138 and change the value to End.

For information about how to correct this issue with case-insensitive search, see the information about running the Siebel Case-Insensitivity Wizard in the Siebel Database Upgrade Guide on the Siebel Bookshelf.

Use the following procedure to remove the empty string matching from the IN clause for the Merge/ Compensation operation:
1 2
Navigate to My Computer > Properties > Advanced > Environment Variables, and set SIEBEL_REMOVE_COMPENSATION_EMPTY_STRING_MATCHING=t as the environment variable. Restart Siebel Servers.
14 9
Siebel Maintenance Release Guide, Version 8.1.1.5, Rev. B Oracle Welcomes Your Comments

1
Set SIEBEL_DATA_MERGE_REPLACE_SURROGATE_PAIR=t. When enabled, this feature will replace the Surrogate Pair characters (that fall into 0xD800 ~ 0xDFFF range) to a pair of replacement characters (the default is "??").
2 3
To use different replacement characters, define the following additional environment variable: set SIEBEL_SURROGATE_PAIR_REPLACEMENT_CHAR=# After you set the environment variabale, bounce the servers, and open a new command prompt to connect to the Siebel Servers. Note the following:

When this is enabled, the replacement will always be performed no matter which database the remote component is connecting to. TxnMerge and RepAgent components are enabled for this feature.
Oracle Welcomes Your Comments

To help us improve our products, we want to know about any corrections or clarifications to this guide that you would find useful. Please include in your message: The title and version of the guide (very important) The name and version number of the Siebel application you are using Your name, job title or functional area, company name, phone number, and email address
Contact us through regular mail or email at: Oracle Siebel Technical Publications Department 500 Oracle Parkway Redwood Shores, CA 94065 Siebeldoc_ww@oracle.com We appreciate your feedback.
150

Siebel Maintenance Release Guide Version 8.1.1.5, Rev. B

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Siebel Maintenance Release Guide Version 8.1.1.5, Rev. B

Caricato da

Copyright:

Formati disponibili

Siebel Maintenance Release Guide

Version 8.1.1.5, Rev. B June 2011

Configuration Instructions for Enhancements and Updates

Siebel Fix Pack Installation Instructions

Resolved Change Requests

Resolved Change Requests in the Siebel 8.1.1.5 Fix Pack