MR Guide 81110 Rev B PDF

Siebel Maintenance Release Guide
Version 8.1.1.10, Rev. B March 2013
Copyright 2005, 2013 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 END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are commercial computer software pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. 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 Siebel Fix Pack 8.1.1.10 Whats New in This Revision 10
9 10 19
Quick Fixes Included in Siebel Fix Pack 8.1.1.10
Enhancements and Updates in Siebel Fix Pack 8.1.1.10
Siebel Incremental Repository Merge 20 Updated Siebel Repository Files 21 Updated Siebel Sample Database 21 Siebel Open UI 22 Siebel Mobile Applications 22 ACR 505, ACR 506, and RF 1052: Oracle Secure Enterprise Search Enhancements ACR 643: Commerce Automation and Response Action Framework 23 ACR 652: Enhanced Product Promotions and Promotion Groups 24 ACR 669: Siebel Field Service to Oracle Real-Time Scheduler Integration 25 ACR 724: Siebel Social Media Integration 25 ACR 740: Siebel Process Failure Diagnostics 26 ACR 744 and ACR 900: Oracle Customer Hub (UCM) Enhancements 26 ACR 756: Utilities Billing System Integration 28 ACR 764: ATG - Siebel Integration 29 Siebel Loyalty Enhancements in Siebel Fix Pack 8.1.1.10 29 ACR 778: Siebel Social Marketing 31 ACR 855: Oracle Knowledge 31 RF 908: Siebel Chat Functionality Enhancements 32 RF 949: Complete Meeting Packages 33 RF 1053: Support for Customer Dashboard for Open UI 33 RF 1069: Support for Microsoft Internet Explorer 10 for Open UI 34 RF 1073: Support for Microsoft Windows 2012 34 ACR 457: Cross-Network Validation for Network Order Entry 34 ACR 471: Promotion AutoMatch 34 ACR 474: Order Management Enhancements for Product Integration Packs 35 ACR 499: Siebel Bulk Order Enhancements 38 ACR 500: CMU Advanced Bundling 39 ACR 502: Siebel Product Configurator Enhancements 39 ACR 508: Order to Cash Integration 40 ACR 620: Promotion Groups 40
23
Configuration Instructions for Enhancements and Updates

Instructions for ACR 457 42
41
Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B
Contents
Instructions Instructions Instructions Instructions Instructions Instructions Instructions
for for for for for for for
ACR 471 42 ACR 474 43 ACR 499 and ACR 643 60 ACR 508 65 ACR 652 83 ACR 756 84 Siebel Reports Enhancements
84
Siebel Fix Pack Installation Instructions
84
Siebel Fix Pack Installation Overview 84 Installing the Siebel Fix Pack on Microsoft Windows 91 Installing the Siebel Fix Pack on UNIX 96 Postinstallation Tasks for the Siebel Server 100 Postinstallation Tasks for the Siebel Web Server Extension Postinstallation Tasks for High Interactivity Clients 102 Postinstallation Tasks for Supporting Additional Languages Uninstalling Siebel Fix Packs 104
101 103
Resolved Bugs in Siebel Fix Pack 8.1.1.10

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
4
110
Application Integration 111 Apps - Customer Order Management 111 Apps -Data Quality 119 Apps - Handheld Client 121 Apps - Marketing 122 Apps - Multichannel Technologies 124 Apps - Multichannel Technologies 125 Apps - Oracle Customer Hub 129 Apps - PRM 130 Apps - Sales 130 Apps - Search & Knowledge Management 132 Apps - Service 133 Apps - Territory Management 134 Apps - UCM 135 Automotive 135 Calendar 136 Communications & Energy 139 Consumer Goods 141 Core - Automation 141 Core - Common Components 142 Core - DB Deployment and Configuration 142 Core - DB Deployment and Configuration 142 Core - EAI 143 Core - EIM/Database 145 Core - Handheld Sync 146
Contents
Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel
Core - PIM Integration 147 Core - Server BizLogic Rules 147 Core - Server BizLogic WF 148 Core - Server Infrastructure 148 Core - Server OM Frwks 149 Core - Server OM Svcs 150 Core - Social 151 Core - Tools 151 Core - UNIX/Windows 152 CRM Desktop 153 CRM Integration to Oracle Realtime Scheduler Data Model 154 Documents 159 Engineering - Installer 159 Engineering - Rel Eng 161 Financial Services 161 Life Sciences 162 Loyalty 166 Public Sector 168 Reports 168 Server Remote 171 Travel & Transportation 171 UI Framework 180
153
Oracle Welcomes Your Comments
195
Contents
Siebel Maintenance Release Guide, Version 8.1.1.10, Rev. B
March 2013
NOTE: Always check My Oracle Support for the latest revision of this guide. From within My Oracle Support, navigate to the Knowledge tab and search for Article ID 880452.1. See also Siebel Maintenance Release Guides for Siebel Fix Pack 8.1.1.x Releases on page 8.
How To Use This Guide

This document, Siebel Maintenance Release Guide, Version 8.1.1.10, applies to Siebel Fix Pack 8.1.1.10. This guide provides the Quick Fixes, enhancements, instructions for enhancements, bugs fixed, and installation instructions that are included in or that apply to the applicable Siebel Fix Pack 8.1.1.x release. You install the current Siebel Fix Pack 8.1.1.x into an existing installation of Siebel Business Applications version 8.1.1 or a prior Siebel Fix Pack 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. You might also need to refer to the Siebel Maintenance Release Guides for previous Siebel Fix Pack 8.1.1.x releases. NOTE: Verify the availability and applicability of all applicable Siebel Fix Pack or Quick Fix releases with Oracle Global Customer Support before you install. For more information about the available patch releases for Siebel CRM, see 975515.1 (Article ID) on My Oracle Support. For more information about finding and downloading patch releases for Siebel CRM, see 975535.1 (Article ID) on My Oracle Support. 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) My Oracle Support Certifications (https://support.oracle.com) The Certifications tab on My Oracle Support, also known as My Oracle Support Certifications, is a self-service certification application that is part of My Oracle Support (MOS) and that provides a structured display of certification data. You can search by platform, release version, product, and more. For version 8.1.1.9 and later, My Oracle Support Certifications replaces Siebel System Requirements and Supported Platforms on Oracle Technology Network. For more information, see 1492194.1 (Article ID) on My Oracle Support. NOTE: This document might include references to functionality, products, platforms, and language support 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.
Siebel Maintenance Release Guide, Version 8.1.1.10, Rev. B
Siebel Maintenance Release Guides for Siebel Fix Pack 8.1.1.x Releases
Separate Siebel Maintenance Release Guides are provided for each Siebel Fix Pack 8.1.1.x release, starting with version 8.1.1.5. This approach to publishing these guides is intended to make each version-specific guide more manageable to use. Siebel Fix Pack releases are cumulative and include all of the content of previous Fix Packs in the same series. For this reason, much of the information in previous guides is also relevant to your implementation of Siebel Business Applications. For information about previous Siebel Fix Packs 8.1.1.x, see the applicable Siebel Maintenance Release Guide on My Oracle Support. Each guide provides only the Quick Fixes, enhancements, instructions for enhancements, bugs fixed, and installation instructions that are included in or that apply to the applicable Siebel Fix Pack 8.1.1.x release. NOTE: For Siebel Fix Pack 8.1.1.10 and later (when it is installed as a patch release into an existing installation with an existing database), the Incremental Repository Merge feature replaces parts of the configuration instructions that were provided for ACRs and other enhancements in the Siebel Maintenance Release Guides for previous Siebel Fix Pack 8.1.1.x releases. You must use Incremental Repository Merge to implement any new enhancements. For more information about Incremental Repository Merge, see Enhancements and Updates in Siebel Fix Pack 8.1.1.10 on page 19. To access the latest revision of any of the Siebel Maintenance Release Guides for Siebel Fix Pack 8.1.1.x releases, from within My Oracle Support, navigate to the Knowledge tab, and search for Article ID 880452.1. Table 1 identifies the Siebel Maintenance Release Guide that applies to each Siebel Fix Pack 8.1.1.x release.
Table 1. Available Siebel Maintenance Release Guides for Siebel Fix Pack 8.1.1.x Releases Siebel Fix Pack 8.1.1.x Release Siebel Fix Pack 8.1.1.10 Siebel Fix Pack 8.1.1.9 Siebel Fix Pack 8.1.1.8 Siebel Fix Pack 8.1.1.7 Siebel Fix Pack 8.1.1.6 Siebel Fix Pack 8.1.1.5 Siebel Fix Pack 8.1.1.1 through Siebel Fix Pack 8.1.1.4 Applicable Siebel Maintenance Release Guide Siebel Maintenance Release Guide, Version 8.1.1.10 Siebel Maintenance Release Guide, Version 8.1.1.9 Siebel Maintenance Release Guide, Version 8.1.1.8 Siebel Maintenance Release Guide, Version 8.1.1.7 Siebel Maintenance Release Guide, Version 8.1.1.6 Siebel Maintenance Release Guide, Version 8.1.1.5 Siebel Maintenance Release Guide, Version 8.1.1.x
Additional Documentation
Oracle reserves the right to modify the documentation for Siebel Business Applications at any time. For related Siebel CRM documentation, see the following: My Oracle Support (https://support.oracle.com) (requires valid customer account)
Siebel Maintenance Release Guide, Version 8.1.1.10, Rev. B Release Notes for Siebel Fix Pack 8.1.1.10
My Oracle Support Certifications (https://support.oracle.com) The Certifications tab on My Oracle Support, also known as My Oracle Support Certifications, is a self-service certification application that is part of My Oracle Support (MOS) and that provides a structured display of certification data. You can search by platform, release version, product, and more. For version 8.1.1.9 and later, My Oracle Support Certifications replaces Siebel System Requirements and Supported Platforms on Oracle Technology Network. For more information, see 1492194.1 (Article ID) on My Oracle Support.
Siebel Bookshelf for Oracles Siebel Business Applications, Version 8.1 (http://www.oracle.com/ technology/documentation/siebel.html) on Oracle Technology Network (OTN)
Whats in This Guide

This guide includes the following information: Release Notes for Siebel Fix Pack 8.1.1.10 on page 9 Whats New in This Revision on page 10 Quick Fixes Included in Siebel Fix Pack 8.1.1.10 on page 10 Enhancements and Updates in Siebel Fix Pack 8.1.1.10 on page 19 Configuration Instructions for Enhancements and Updates on page 41 Siebel Fix Pack Installation Instructions on page 84 Resolved Bugs in Siebel Fix Pack 8.1.1.10 on page 110 Oracle Welcomes Your Comments on page 195
Release Notes for Siebel Fix Pack 8.1.1.10

The following section describes known issues with Siebel Fix Pack 8.1.1.10, as well as any applicable workaround information. NOTE: For a comprehensive list of all Siebel 8.1 Release Notes, see Siebel Release Notes on My Oracle Support (Article ID 557191.1).
Iexplore.exe Causes Siebel Web Client Installation to Hang

Product Area: Siebel Eng - Installer Component: Install - Client Subcomponent: Dedicated_ Client Bug ID: 16451844 When installing the Siebel Web Client, if Iexplore.exe is running in Task Manager, the installation may hang.
Siebel Maintenance Release Guide, Version 8.1.1.10, Rev. B Whats New in This Revision
Workaround: Make sure that Iexplore.exe is not running in Task Manager.
Whats New in This Revision

Table 2 describes the changes in this version of the documentation. Table 2. Whats New in Siebel Maintenance Release Guide, Version 8.1.1.10, Rev. B Topic Quick Fixes Included in Siebel Fix Pack 8.1.1.10 on page 10 Description Revised Quick Fixes list.
Quick Fixes Included in Siebel Fix Pack 8.1.1.10

NOTE: The table in this topic, Table 3 on page 10, includes only the Quick Fixes included in Siebel Fix Pack 8.1.1.10. For information about the Quick Fixes included in previous Siebel Fix Pack 8.1.1.x releases, see the applicable Siebel Maintenance Release Guide on My Oracle Support. For information about accessing Siebel Maintenance Release Guides for previous Siebel Fix Pack 8.1.1.x releases, see Siebel Maintenance Release Guides for Siebel Fix Pack 8.1.1.x Releases on page 8. Siebel Quick Fix releases are developed to address immediate critical issues for specific customers, and can be installed on top of Siebel 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 using. CAUTION: If you do not see your Quick Fix number in the table or in any similar table for prior Siebel Fix Pack 8.1.1.x releases, then do not install the latest Siebel Fix Pack 8.1.1.x. This list is updated for each new Siebel Fix Pack. Wait until your Quick Fix is listed before applying the latest Fix Pack. If you have questions, contact Global Customer Support or your Oracle representative.
Table 3.
Quick Fixes Included in Siebel Fix Pack 8.1.1.10 Bug ID 14786851 10588168 13888550 13242164 14596080 Fix Pack Base 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.1 [21211] 8.1.1.2 [21215] 8.1.1.2 [21215] Quick Fix Version QF01CV QF7102 QF7113 QF2213 QF2223 Merged Into Fix Pack 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10
Base Bug ID 14472864 10588167 13888514 13090315 14596020
10
Siebel Maintenance Release Guide, Version 8.1.1.10, Rev. B Quick Fixes Included in Siebel Fix Pack 8.1.1.10
Table 3.
Quick Fixes Included in Siebel Fix Pack 8.1.1.10 Bug ID 14740522 15838302 14632839 14578580 14730991 14682607 14749588 13589503 14765925 14779812 14376882 14760935 14696982 14802997 15908640 14786368 13054202 13892978 13693574 14214148 14386692 14203363 14588819 14339768 14590186 14611033 14491971 14160619 14781923 14697583 Fix Pack Base 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 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.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 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] Quick Fix Version QF2224 QF2225 QF2223 QF03DC QF03DH QF03DI QF03DJ QF03DL QF03DP QF03DQ QF04AC QF04AD QF04AE QF04AF QF04AG QF04AH QF0567 QF0598 QF05AB QF05AS QF05BU QF05BV QF05BW QF05BX QF05CC QF05CG QF05CI QF05CK QF05CN QF05CN Merged Into Fix Pack 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10
Base Bug ID 14740497 15838264 14632823 10597322 13820092 14220483 10477346 13082592 14337611 10528258 11936048 14750354 14678057 14740485 15911133 14707027 13514232 10597322 13703750 14214263 14305830 14183186 14306189 10588576 14605326 14472864 14469295 14156187 14313547 14612437
11
Table 3.
Quick Fixes Included in Siebel Fix Pack 8.1.1.10 Bug ID 14798714 14504612 14465295 Fix Pack Base 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.5 [21229] 8.1.1.6 [21233] 8.1.1.6 [21233] 8.1.1.6 [21233] 8.1.1.6 [21233] 8.1.1.6 [21233] 8.1.1.6 [21233] 8.1.1.6 [21233] 8.1.1.6 [21233] 8.1.1.6 [21233] 8.1.1.6 [21233] 8.1.1.6 [21233] 8.1.1.6 [21233] 8.1.1.6 [21233] 8.1.1.6 [21233_2] 8.1.1.7 [21238] Quick Fix Version QF05CP QF05CQ QF05CR QF05CU QF05CV QF05CW QF05CY QF05CZ QF05DA QF05DB QF05DE QF05DG QF05DH QF05DJ QF0629 QF0652 QF0653 QF0654 QF0658 QF0659 QF0660 QF0661 QF0663 QF0664 QF0666 QF0668 QF0674 8.1.1.6 [21233_2] QF0714 Merged Into Fix Pack 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10
Base Bug ID 14461301 14504343
14699984 10547611 14395165 14751742 14641009 14839547 15896394 14732447 14766080 13082592 14347191 12768910 10518337 13810633 14492206 10569855 14142983 14641837 14391368 14789552 16036064 16026562 16101862 14796029 13907291
14772411 14803052 14661152 14775689 14641288 15833917 15896452 15927928 14768271 12980430 14364073 13864892 14157717 13810751 14584483 14343996 14796092 14624960 14688851 14825363 16041569 16026572 16101934 14796125 13907319 13892491
12
Table 3.
Quick Fixes Included in Siebel Fix Pack 8.1.1.10 Bug ID 13823185 Fix Pack Base 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] Quick Fix Version QF0714 QF0735 QF0759 QF0767 QF0771 QF0775 QF0775 QF0775 QF0778 QF0778 QF0778 QF0779 QF0780 QF0783 QF0783 QF0784 QF0785 QF0786 QF0787 QF0790 QF0791 QF0794 QF0798 QF07AA QF07AB QF07AD QF07AE QF07AG QF07AI QF07AL Merged Into Fix Pack 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10
Base Bug ID
13514232 14142983 13252249 14247734 14537389 14560377 14537375 14569957 14569957
14126158 14337008 14181970 14318211 14527375 14552043 14527268 16070105 16010612 14569957
13834690 14372284 10554334 14539640 14361943 14211059 14365074 14353506 14782893 14549118 14350262 14337535 13965246 14660079 14782728 14578317 14670979 14404972 10525309
14047632 14372309 14141705 14539727 14527254 14211163 14518832 14353558 13345710 14554700 14532376 14341698 14489484 14660138 14782759 14578339 14724191 14495437 14732205
13
Table 3.
Quick Fixes Included in Siebel Fix Pack 8.1.1.10 Bug ID 14461652 15908688 15837795 15888952 14775570 14776592 14775537 15874112 14700822 14653219 14695523 16010262 16022150 14786140 16016317 15993776 14807455 16061153 16001827 16033912 15832120 13682694 15998821 16065823 15892862 16416578 14643684 14002935 Fix Pack Base 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.7 [21238] 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012] Quick Fix Version QF07AM QF07AN QF07AN QF07AP QF07AQ QF07AQ QF07AQ QF07AQ QF07AT QF07AW QF07AY QF07BA QF07BB QF07BD QF07BF QF07BG QF07BH QF07BI QF07BJ QF07BJ QF07BM QF07BQ QF07BR QF07BS QF07BV QF07CN QF1704 QF0000001 QF0000007 QF0000012 Merged Into Fix Pack 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10
Base Bug ID 14394947 15911133 14810181 14750354 14668043 15907184 15907067 15907257 14691343 14652801 14677467 16010088 16011105 10534512 16016275 15989475 14598294 14641009 14305830 16024058 15832063 13683744 16003200 14477717 13810633 14183186 14599122
14380714 14415526
14626259 16090494
14
Table 3.
Quick Fixes Included in Siebel Fix Pack 8.1.1.10 Bug ID 14746900 14705655 14501708 15972845 15972188 14704678 14654250 15979577 16291590 14164166 14136217 14729064 14701492 14699715 14699769 14569805 14638823 14740552 14785610 14653955 14782837 15863986 16457515 15977244 16003910 16201065 Fix Pack Base 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012_4] 8.1.1.8_8.2.2.1 [23012_4] 8.1.1.8_8.2.2.1 [23012_4] 8.1.1.8_8.2.2.1 [23012_4] 8.1.1.8_8.2.2.1 [23012_5] 8.1.1.8_8.2.2.1 [23012_5] 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012] 8.1.1.8_8.2.2.1 [23012] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] Quick Fix Version QF0000018 QF0000019 QF0000021 QF0000026 QF0000029 QF0000033 QF0000036 QF0000037 QF0000041 8.1.1.8_8.2.2.1 [23012_4] 8.1.1.8_8.2.2.1 [23012_4] 8.1.1.8_8.2.2.1 [23012_4] 8.1.1.8_8.2.2.1 [23012_4] 8.1.1.8_8.2.2.1 [23012_5] 8.1.1.8_8.2.2.1 [23012_5] QF0000009 QF0000014 QF0000014 QF0000014 QF0000014 QF0000020 QF0001006 QF0001006 QF0001008 QF0001010 QF0001012 Merged Into Fix Pack 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10
Base Bug ID 14703903 14705805 14460136 15975431 16002129 14697162 14331102 15974409 15862953 10561164 14127699 14729047 14700152 14560311 14658936 14569573 14632823 14740497 14784830 14596020 14744386 14705805 14705805 14670979 14305830 14682607
15
Table 3.
Quick Fixes Included in Siebel Fix Pack 8.1.1.10 Bug ID 16194870 16078373 16300445 16286478 16286474 16286458 16407372 16390588 Fix Pack Base 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] Quick Fix Version QF0001018 QF0001019 QF0001023 QF0001024 QF0001029 QF0001030 QF0001034 QF0001035 QF0001036 QF0001037 QF0101002 QF0101003 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 Merged Into Fix Pack 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10
Base Bug ID 10477346 16065271 14415526 15834186 14504343 14612437 14578317
14350262 14156187 16053676 16278359 14688411 14688411
16463536 16288826 16094279 16304760 14581341 14370058 14688411 14737937
14771527
14764754 14731031 14777402 14662629
14671753 14711456
14687736 14671753 14761391 14696652 14731980 14738111 14825865 14812706
14682058
14709379 14755382
16
Table 3.
Quick Fixes Included in Siebel Fix Pack 8.1.1.10 Bug ID 14682058 14731135 14723487 14754666 14561375 14735529 14797360 14732248 14755450 14703484 14683956 14806880 14604969 14672560 14724316 14778142 14823048 14741641 14805207 14769032 14750321 14802086 14738448 14797619 Fix Pack Base 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] Quick Fix Version QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 Merged Into Fix Pack 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10
Base Bug ID
14744813
14688204 14801507 14771548 14742707 14735928 14760638
17
Table 3.
Quick Fixes Included in Siebel Fix Pack 8.1.1.10 Bug ID 14585047 14742993 14760610 14709290 14822111 14754153 14792946 14782682 14849786 14771527 14735817 14705286 14137000 14724072 14744813 14804537 14852010 14837803 15849129 15898181 Fix Pack Base 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] 8.1.1.9_8.2.2.2 [23016] Quick Fix Version QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1001 QF1002 QF1002 QF1002 QF1002 QF0001031 Merged Into Fix Pack 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10 8.1.1.10
Base Bug ID
15908699
15965972
18
Siebel Maintenance Release Guide, Version 8.1.1.10, Rev. B Enhancements and Updates in Siebel Fix Pack 8.1.1.10
Enhancements and Updates in Siebel Fix Pack 8.1.1.10

Siebel Fix Pack 8.1.1.10 contains several product enhancements. This topic contains the following subtopics: Siebel Incremental Repository Merge on page 20 Updated Siebel Repository Files on page 21 Updated Siebel Sample Database on page 21 Siebel Open UI on page 22 Siebel Mobile Applications on page 22 ACR 505, ACR 506, and RF 1052: Oracle Secure Enterprise Search Enhancements on page 23 ACR 643: Commerce Automation and Response Action Framework on page 23 ACR 652: Enhanced Product Promotions and Promotion Groups on page 24 ACR 669: Siebel Field Service to Oracle Real-Time Scheduler Integration on page 25 ACR 724: Siebel Social Media Integration on page 25 ACR 740: Siebel Process Failure Diagnostics on page 26 ACR 744 and ACR 900: Oracle Customer Hub (UCM) Enhancements on page 26 ACR 756: Utilities Billing System Integration on page 28 ACR 764: ATG - Siebel Integration on page 29 Siebel Loyalty Enhancements in Siebel Fix Pack 8.1.1.10 on page 29 ACR 778: Siebel Social Marketing on page 31 ACR 855: Oracle Knowledge on page 31 RF 908: Siebel Chat Functionality Enhancements on page 32 RF 949: Complete Meeting Packages on page 33 RF 1053: Support for Customer Dashboard for Open UI on page 33 RF 1069: Support for Microsoft Internet Explorer 10 for Open UI on page 34 RF 1073: Support for Microsoft Windows 2012 on page 34 ACR 457: Cross-Network Validation for Network Order Entry on page 34 ACR 471: Promotion AutoMatch on page 34 ACR 474: Order Management Enhancements for Product Integration Packs on page 35 ACR 499: Siebel Bulk Order Enhancements on page 38 ACR 500: CMU Advanced Bundling on page 39 ACR 502: Siebel Product Configurator Enhancements on page 39
19
ACR 508: Order to Cash Integration on page 40 ACR 620: Promotion Groups on page 40
Siebel Incremental Repository Merge

This topic is part of Enhancements and Updates in Siebel Fix Pack 8.1.1.10 on page 19. For Siebel Fix Pack 8.1.1.10, when it is installed as a patch release into an existing installation with an existing database, you must use the Incremental Repository Merge feature (IRM) to implement any new enhancements. This feature implements any and all of the enhancements that have been provided since version 8.1.1. Incremental Repository Merge is available using the Siebel Tools software after you have installed Siebel Fix Pack 8.1.1.10. For information about setting up and using Incremental Repository Merge, see Siebel Database Upgrade Guide. NOTE: For information about the ACRs and other enhancements provided in previous Siebel Fix Pack 8.1.1.x releases, see the applicable Siebel Maintenance Release Guide on My Oracle Support. After installing the current Siebel Fix Pack, you must use Incremental Repository Merge to implement these enhancements instead of performing parts of the configuration instructions that were documented in prior guides for these enhancements, in particular the steps to import files from the REPPATCH directory. Some application-specific configuration steps still apply. For information about accessing the Siebel Maintenance Release Guides for previous Siebel Fix Pack 8.1.1.x releases, see Siebel Maintenance Release Guides for Siebel Fix Pack 8.1.1.x Releases on page 8. Other scenarios for getting the Siebel database to the version 8.1.1.10 level are as follows: If you have installed Siebel CRM version 8.1.1.10 as a new installation, then, when you install a new Siebel database using the Siebel Database Configuration Wizard, the new database that is created includes the database content that has been updated for version 8.1.1.10. Do not use Incremental Repository Merge in this new-installation case. For information about performing a new installation of Siebel CRM version 8.1.1.10, see Siebel Installation Guide for the operating system you are using. If you are upgrading to Siebel CRM version 8.1.1.10 from a release prior to Siebel CRM 8.1.1, then, for supported upgrade paths, you can upgrade the database to version 8.1.1.10. Do not use Incremental Repository Merge in this upgrade case. For information about upgrading the Siebel database, see Siebel Database Upgrade Guide.
Related Topics Updated Siebel Repository Files on page 21 Updated Siebel Sample Database on page 21
20
Updated Siebel Repository Files

This topic is part of Enhancements and Updates in Siebel Fix Pack 8.1.1.10 on page 19. Updated Siebel Repository Files (SRF files) are available for download from Oracle. These updated SRF files are available for all of the supported Siebel languages. The SRF files correspond to Siebel Repository updates for version 8.1.1.10. Use the updated SRF files in order to run the Siebel Business Applications after you install Siebel Fix Pack 8.1.1.10. NOTE: Before you can use an updated SRF file, the Siebel database must have been updated to include the Siebel Repository changes for version 8.1.1.10, such as those that you implement by using the Incremental Repository Merge feature. For more information, see Siebel Incremental Repository Merge on page 20. The updated SRF files are available as part of the Siebel Fix Pack 8.1.1.10 media pack on Oracle Software Delivery Cloud. You can download the srf.zip file, among all the other media ZIP files for the Fix Pack release. Unzip srf.zip to obtain all of the language-specific updated Siebel Repository Files (SRF files). The srf.zip file is included in the media for Microsoft Windows only. However, the SRF files themselves are applicable to all of the supported operating systems for the Siebel Server and the Siebel Mobile Web Client. For a Siebel Mobile Web Client, also obtain and use an updated Siebel Sample Database, if applicable.
Related Topics Siebel Incremental Repository Merge on page 20 Updated Siebel Sample Database on page 21
To use the updated SRF files on a Siebel Server or Siebel Mobile Web Client 1 2 3 4
Back up the existing SRF files for an installation. Stop the services for the Siebel Server or close the Siebel Mobile Web Client. Copy each new language-specific SRF file so that it overwrites the existing SRF file for that language. Restart the Siebel Server services or the client application.
Updated Siebel Sample Database

This topic is part of Enhancements and Updates in Siebel Fix Pack 8.1.1.10 on page 19. An updated Siebel Sample Database is available for download from Oracle. The updated Siebel Sample Database includes database schema and seed data changes for Siebel Fix Pack 8.1.1.10. The Sample Database is for Microsoft Windows only, for use with the Siebel Mobile Web Client and Siebel Tools. The updated Siebel Sample Database is for U.S. English (ENU) only.
21
The updated Siebel Sample Database is available as part of the Siebel Fix Pack 8.1.1.10 media pack on Oracle Software Delivery Cloud. You can download the sampledb.zip file, among all the other media ZIP files for the Fix Pack release. Unzip sampledb.zip to obtain the updated database file, sample.dbf. The sampledb.zip file is included in media for Microsoft Windows only. The existing Siebel Sample Database that was installed for version 8.1.1 does not work for Siebel Fix Pack 8.1.1.10, where the SRF file for the installation includes updates for version 8.1.1.10, such as those that you implement by using the Incremental Repository Merge feature. For information about installing the Siebel Sample Database for version 8.1.1 and about starting the Siebel Mobile Web Client, see the Siebel Installation Guide for the operating system you are using. For information about the demo users in the Sample Database, see Siebel Demo Users Reference. Also obtain and use the updated full SRF files that include the corresponding repository updates.
Related Topics Siebel Incremental Repository Merge on page 20 Updated Siebel Repository Files on page 21
To use the updated Siebel Sample Database on a Siebel Mobile Web Client 1 2 3 4
Back up the sample.dbf file for an existing installed Siebel Sample Database. Log out of the Siebel Mobile Web Client, as needed. Copy the new sample.dbf file so that it overwrites the existing file. Log in to the Siebel Mobile Web Client again as a demo user using the Sample Database.
Siebel Open UI
Siebel Fix Pack 8.1.1.10 delivers additional controls and support for Siebel Open UI. For more information about the new functionality available with this release, see the Siebel Open UI Best Practices - Deployment Guide article on My Oracle Support. To access this article, from within My Oracle Support, navigate to the Knowledge tab and search for Article ID 1499842.1. Information about Siebel Open UI has also been updated in many documents on the Siebel Bookshelf, including the Siebel Installation Guide for the operating system you are using.
Siebel Mobile Applications

Siebel Fix Pack 8.1.1.10 provides updated functionality for the Siebel Mobile applications, which were first provided in Siebel Fix Pack 8.1.1.9. For more information, see Siebel Mobile Guide: Connected on the Siebel Bookshelf.
22
ACR 505, ACR 506, and RF 1052: Oracle Secure Enterprise Search Enhancements
The following topic describes the Oracle Secure Enterprise Search enhancements provided in Siebel Fix Pack 8.1.1.10.
ACR 505
ACR 505 provides the following enhancements to Oracle Secure Enterprise Search: Auto suggestions Faceted navigation Support for external connectors
ACR 506
ACR 506 provides the following enhancements to Oracle Secure Enterprise Search: Actionable links Asynchronous indexing Automatic login Batch-error handling Drilldown in a new window Dynamic field mappings Filtering by business component type Multi-value group indexing One-click search
RF 1052
RF 1052 provides Oracle Secure Enterprise Search for Open UI.
ACR 643: Commerce Automation and Response Action Framework

NOTE: ACR 643 is provided in Siebel Fix Pack 8.1.1.10. ACR 643 allows users to create promotional product offers that customers can accept with one click, and that can be used on the Web or on channels where there is limited user interactivity, such as SMS and IVR. The new response-action framework supports offer-response capture and key order processes, including asset-based ordering. New Web services assist with personalized offer presentment and simplify the offer-to-order process for nonassisted interactions.
23
ACR 643 includes the following features: Product Offer Administration. ACR 643 provides a new administration view that allows product administrators to create and maintain the core elements of a product offer definition, such as offer responses, actions, eligibility and compatibility rules, and recommendations. Product Offer Presentment. ACR 643 allows users to recommend eligible product offers based on the customers installed assets. Product Offer Web Services. ACR 643 provides a new Web service to retrieve a product offer definition, get recommended offers for a customer, and apply an offer to create an order. Product Configurator Web Services for Orders. ACR 643 provides a new product configurator Web service to add and configure products within a sales order.
Postinstallation Instructions
You must perform some postinstallation configurations for ACR 643. For more information, see Instructions for ACR 499 and ACR 643 on page 60.
Additional Information and Documentation

For more information about the enhancements that ACR 643 provides, see Siebel Pricing Administration Guide on the Siebel Bookshelf. Siebel CRM Web Services Reference on the Siebel Bookshelf For more information about the Product Offer Web services and the Product Configurator Web service for orders, see Siebel CRM Web Services Reference on the Siebel Bookshelf.
ACR 652: Enhanced Product Promotions and Promotion Groups

NOTE: ACR 652 is provided in Siebel Fix Pack 8.1.1.10. ACR 652 allows communications service providers to provide advanced product and service bundling using Bundled Promotions and Promotion Groups. ACR 652 includes: Promotion Dynamic Transform. Provides the ability to merge and split bundled promotions without predefined transition paths. Promotion Manual Ambiguity Resolution. Provides the ability to manually resolve component transfer ambiguity during a promotion transition. Promotion Action User Prompt. Allows end-users to decide at runtime whether to keep or disconnect a debundled promotion component. Promotion Upgrade Within Orders. Provides the ability to initiate a promotion upgrade flow from the Quote or Order line items applets. Edit Promotion UI Improvements. Improves the usability of the Edit Promotion UI.
24
Promotion Group Creation Task-Based UI. Provides a seeded task-based UI for the creation of a new Promotion Group (including adding memberships and associating assets). Visual Indicators for Promotions and Promotion Groups. Provides better readability and usability in the Quote and Order line items applet for Promotion - Promotion Group-related lines.
ACR 652 provides the following benefits: Increases the ability to market new and innovative offers Improves customer visibility into offer transitions
ACR 652 provides the following operational efficiencies: Increases end-user productivity with guided flows for complex business processes Improves usability for faster agent adoption and reduces training needs Avoids the complex customization required to develop similar solutions

Siebel Order Management Guide Addendum for Communications
You must perform some postinstallation configurations for ACR 652. For more information, see Instructions for ACR 652 on page 83.
ACR 669: Siebel Field Service to Oracle Real-Time Scheduler Integration

NOTE: ACR 669 is provided in Siebel Fix Pack 8.1.1.10. ACR 669 integrates Siebel Field Service with Oracle Real-Time Scheduler v2.1. Oracle Real-Time Scheduler v2.1 provides a real-time dynamic scheduling solution for companies to schedule their mobile resources. Oracle Real-Time Scheduler v2.1 has a Web-based user interface that enhances usability, and the Siebel integration with Oracle Real-Time Scheduler v2.1 enhances the integration of data between Siebel Field Service and Oracle Real-Time Scheduler.
ACR 724: Siebel Social Media Integration

ACR 724 provides the following enhancements: A framework for Oracle Social Engagement & Monitoring and Oracle Social Marketing cloud services as well as custom and partner social media integrations. Using Oracle Social Engagement & Monitoring, you can create service requests from social media posts. Using Oracle Social Marketing, you can capture leads on Facebook and push the leads to Siebel CRM for lead creation, and you can link social media campaigns from Oracle Social Marketing cloud service to Siebel Campaigns.
25
With this enhancement, Siebel CRM now provides a framework for storing social media profiles for contacts. By having social profile and attribute information for contacts, you can obtain a complete, 360-degree view of your contacts. You can view and store many social media profiles that contain detailed profile and attribute data such as interests, likes, followers, friends, tweets, re-tweets, location, and so forth.
ACR 740: Siebel Process Failure Diagnostics

ACR 740 provides process failure diagnostics that help you to allocate system resources and maintain an efficient and reliable environment. Administrators can monitor KPIs (key performance indicators) of the various levels of the Siebel environment to do the following: Identify, isolate, and remedy adverse system and application conditions. Adjust the various settings and parameters of the Siebel environment to avert adverse conditions. Optimize available resources for improved performance.
When a Siebel process fails, the administrator can do the following: View all detectable failed processes for a given Siebel Enterprise by Siebel Server. Identify the probable cause and point of origin of the failure, including (but not limited to) user, process, thread, task, application, view, and activity immediately prior to the failure. Review content of the main process failure file (crash.txt) associated with a given failure including the call stack, the register contents, and the memory information. Review content of other failure information contained in the Siebel FDR (Flight Data Recorder), Siebel ARM (Application Response Management), and component log files. Determine other Siebel users directly affected by the failure.
ACR 744 and ACR 900: Oracle Customer Hub (UCM) Enhancements
NOTE: ACR 744 and ACR 900 are provided in Siebel Fix Pack 8.1.1.10. The following topics provide information about Customer Order Management and Oracle Customer Hub (UCM) enhancements and PIPS that were provided in previous Siebel Fix Packs. In some cases, the enhancements in version 8.1.1.10 build upon the functionality provided in these earlier enhancements. With Siebel Fix Pack 8.1.1.10, both business-to-business and business-to-customer industries can use Siebel Universal Customer Management to master customer records using enhanced child survivorship and child cross-referencing features. This enhancement also provides an integration with Enterprise Data Quality.
26
Key features delivered as part of this release include: Child Survivorship. The survivorship infrastructure has been enhanced to include the attributes at the child level to determine the golden record. Child Cross-Referencing. This functionality has been enhanced to provide a platform to store cross-referencing for any entity. Enterprise Data Quality Integration. This enhancement provides an integration between Oracle Customer Hub (UCM) and Oracle Enterprise Data Quality.
The following sections detail the enhancements provided in ACR 744 and ACR 900.
Child Survivorship (ACR 744)

Survivorship is the process of creating a surviving record when multiple systems attempt to contribute information about a customer. Survivorship rules govern how a best-version record, the surviving record, can be constructed for a specific data object. Data stewards often need sophisticated rules at a child level to create a golden record. Having a golden record facilitates appropriate behavior during merges, updates, and unmerge operations for child records. Data stewards define survivorship rules at the parent level. Oracle Customer Hub version 8.1.1.10 allows users to create a surviving record when drawing disjointed information for the same record from multiple systems. That is because the enhanced survivorship engine considers attributes not only at the parent level but also at the child level. This enhanced survivorship functionality provides the following benefits: Because Survivorship is the core engine for UCM, its enhanced functionality improves UCM functionality overall. Survivorship creates the golden record without requiring steward intervention. Survivorship helps to intelligently update records. Survivorship helps to master child entities in isolation.
Child Cross-Referencing (ACR 744)

This functionality has been extended to improve the cross-referencing infrastructure to provide a platform to store cross-referencing for any entity. Cross-referencing of customer identification data allows organizations to store the customer identification data from external systems within Oracle Customer Hub (UCM). This cross-referencing permits a one-to-many mapping of customer records across multiple systems throughout the organization. In other words, one record in Oracle Customer Hub (UCM) can map to one or more records in each registered application in Oracle Customer Hub (UCM). Oracle Customer Hub (UCM) has the infrastructure to store cross-referencing of parent entities. ACR 744 extends this crossreferencing infrastructure to provide a platform to store cross-referencing for any entity. Helps to master additional entities like Addresses, Households, and so on Makes it easy for operational systems to update child entities with child cross-references
27
Enterprise Data Quality Integration (ACR 900)

Data Quality provides a framework that facilitates a controlled path to higher data quality levels for an organization. The Oracle Enterprise Data Quality family of products helps organizations derive more value from their business-critical applications by delivering fit-for-purpose data. These products also allow individuals and collaborative teams to identify and resolve any problems in underlying data. This release of Siebel UCM (Oracle Customer Hub) integrates Oracle Enterprise Data Quality products that are preintegrated with Siebel UCM and this integration is functionally superior to the other preintegrated connectors provided by Siebel UCM in past releases. This integration provides the following benefits: An Oracle product for Data Quality. Matching on any child entity. Support and flexibility to match on multiple attributes. Stateless integration for better performance and scalability. Easy-to-configure match rules.
ACR 756: Utilities Billing System Integration

NOTE: ACR 756 is provided in Siebel Fix Pack 8.1.1.10. ACR 756 includes enhancements to Siebel Communications, Media, and Energy to better support its integration with billing systems for the Utilities industry and is a prerequisite to the deployment of the following Oracle Application Integration Architecture solutions: Customer Data Synchronization Integration Pack between Oracle Utilities Customer Care and Billing and Siebel CME (Energy). This Integration Pack enables the synchronization of customer information from Siebel CRM applications to Billing to support the Order-to-Bill process. Product Data Synchronization Integration Pack between Oracle Utilities Customer Care and Billing and Siebel CME (Energy). This Integration Pack allows the synchronization of product information from Utilities Billing System to Siebel CRM to support the Order-to-Bill process.
The Siebel Communications, Media, and Energy enhancements delivered with ACR 756 include: Enhancements to the Siebel user interface to support seasonal and temporary addresses, additional bill recipients, selection of valid bank information for automated debit, and product detail description. Enhanced outbound Web services for customer data synchronization to support seasonal addresses, additional bill recipients, and additional utility-specific data requirements. Enhanced inbound Web services for product data synchronization to support additional utilityspecific data requirements.
28

Siebel Energy Guide on the Siebel Bookshelf AIA Integration Packs:

Download the Oracle Application Integration Architecture Pre-built Integrations 11.2 Release on Oracle Software Delivery Cloud Implementation and Installation Guides: on My Oracle Support: (Knowledge > Oracle Applications > Integrations > Application Integration Architecture)
ACR 764: ATG - Siebel Integration

NOTE: ACR 764 is provided in Siebel Fix Pack 8.1.1.10. ACR 764 includes enhancements to Siebel Customer Order Management to support integration with ATG Web Commerce. The Siebel Customer Order Management enhancements delivered with ACR 764 include: A Siebel design-time user interface, provided in Administration views, that allows users to select Product Catalog records for synchronization with ATG. Enhanced inbound Web services for product catalog data synchronization that are invoked using the Siebel Commerce Object Aggregator.

Siebel Order Management Guide: Integrating Siebel Business Applications with Oracle ATG Web Commerce ATG Web Commerce and Siebel Reference Integration on My Oracle Support (Article ID 1358285.1)
Siebel Loyalty Enhancements in Siebel Fix Pack 8.1.1.10

This section describes the Siebel Loyalty enhancements provided in Siebel Fix Pack 8.1.1.10. With Siebel Fix Pack 8.1.1.10, business-to-customer industries can capture and track the social actions of their loyalty program members to be able reward profitable social behavior and recognize customers for their social influence. Member Acquisition Through Social Networks. Loyalty managers can promote their loyalty programs on their branded social pages (such as Fan Pages) and reward visitors or fans for joining loyalty programs.
29
Rewarding Social Actions. Loyalty managers can reward loyalty members for targeted social behaviors (such as liking or sharing the campaign on the latest Jaguar model or rating the new Samsung mobile phone) that helps spread the brand message or word-of-mouth virally or helps brands capture customer feedback for improvement. This also includes rewards for checking-in (location based rewards). Social Referrals. Loyalty managers can also reward existing members for referring other members to the loyalty program. The referral incentives can be one-time or recurring for subsequent actions of the members referred.
With the enhancements delivered in Social Loyalty, organizations can:

Maximize reach and lower the cost of customer acquisition Reward and recognize customers for their social behavior Build a community of social influencers
RF 1043: Siebel Loyalty Release 8.2.2 Functionality

Siebel Fix Pack 8.1.1.10 includes the features delivered in Siebel Loyalty version 8.2.2. This enhancement includes significant innovations targeted mainly to the retail and travel and transportation industries such as: Graphical Promotion Designer. Provides a graphical promotion designer to visually set up promotion flows and execution sequences. Theme Based Clubs. Provides the ability to set up Theme-Based Clubs, which are invitationonly microprograms that offer exclusive benefits, entitlements, and rewards to targeted customer segments (such as a baby club for expectant mothers). Event/Time-Based Promotions. Hierarchical Rules. These rules reduce the effort of setting up multi-tier loyalty promotions and improve loyalty engine throughput. Formula-Based, User-Defined Attributes. These attributes support complex promotions. Batch Redemption. Allows users to automatically redeem or monetize individual members' point balance and fulfill their points in the form of a check or a gift voucher. Transaction Simulation. Allows users to test promotions and also to enable call center agents and loyalty managers to review customer complaints with detailed information around each attribute and promotion and reasons for qualification or disqualification of the promotions.
This enhancement provides the following benefits: Loyalty 1:1. Allows brands to deliver personalized 1:1 loyalty programs that are relevant and tailored to the recipient. Business User Empowerment. Allows businesses to manage loyalty programs more easily and improve the user experience for the customers. Loyalty Management Best Practices. These best practices enhance brand affinity and help to improve competitive advantage.
30
ACR 778: Siebel Social Marketing

This section describes the Siebel Social Marketing enhancements provided in Siebel Fix Pack 8.1.1.10. The Siebel Social Marketing solution is based on the integration between Siebel Marketing and Oracle Social Relationship Management (SRM). It allows marketers to execute closed-loop, cross-channel marketing campaigns with integrated social media to maximize the reach, relevance, revenue, and overall marketing effectiveness of their campaigns. This release of Siebel Social Marketing includes the following features: Cross-Channel Campaigns. Allows marketers to link marketing campaigns that are defined in Siebel Marketing to corresponding social messages and tabs in Oracle Social Relationship Management. This allows marketers to capture leads from social media. Lead Capture from Social Media. Allows marketers to capture leads from social media based on the information provided by social users. This feature includes a form designed in Oracle Social Relationship Management that captures information about the social user on social networks. Social Sharing From Traditional Channels. This feature allows customers who have been targeted for specific marketing campaigns to share marketing or brand messages to their social networks directly from email. Dynamic URLs. This feature allows marketers to define dynamic URLs in email treatments that they can embed in email templates. When emails are generated, the Marketing Email Server will do an HTTP post to the URL and the retrieved content will be dynamically merged into an email.
ACR 855: Oracle Knowledge

The enhancements provided in ACR 855 allow agents to do the following while they are working on incidents: Search the knowledge base using the access credentials of the contact that submitted an incident View content that is returned from a search to allow interactions to be context-driven Filter results based on facets and languages Link and unlink content to a service request or incident Query for content that is linked to a service request or incident Provide links to contacts in their responses Respond to inline content in a response thread Draft new solutions from within a service request Post questions to a community Subscribe to content
ACR 855 also allows users to create reports to analyze the usage of content items in the knowledge base, and these reports can be provided down to the level of the individual agents.
31
RF 908: Siebel Chat Functionality Enhancements

RF 908 provides Siebel Chat enhancements for version 8.1.1.10 that were previously released in Siebel Quick Fixes:
ACR 610: Transfer Chat, Workgroup, and Customization Functionality

ACR 610 includes the following features: Transfer Chat to Agent functionality and data and presence management. Allows Siebel Chat to pass custom key/value pair data from the chat request page. Transfer Chat to Agent functionality and Workgroup with Bookmark data. Provides the ability to customize Chat Screen popup windows.
ACR 611: Chat Auto Accept Functionality

ACR 611 includes the following features: Provides Chat Auto Accept functionality.
ACR 745A: Chat UI Enhancements and Support for Customization

ACR 745A provides the following enhancements to the Siebel Chat functionality: Removes unused functionality from the Chat UI pane:

Removes the PushUrl AreaConfigure button sequence on the button bar Hides unused buttons and field controls Adjusts area functionality
Allows configuration of which elements are displayed in the Chat pane:

Allows users to add or remove fields from the dashboard Allows users to define the mapping of dashboard fields to interaction data or other business component fields Allows users to define columns, rows, and widths of fields
Customization of the Quick Actions list:
Users can use any business service method or workflow to accomplish a specific action
Spell Check enhancements:

Allows users to customize language mapping workflows to set the chat language Allows users to create hot-key buttons for spell check and for other buttons Allows users to provide language information in the Spell Checker popup window Allows users to change the Language popup window Allows users to restore the application back to the default language
32
Customizable chat display names:
Allows users to display custom chat display names
ACR 745B: Chat Status Functionality and Customizable Blinking Indicators

ACR 745B provides the following enhancements to the Siebel Chat functionality: Improved feedback between the customer and the agent by providing a "Typing" event for both the member and the agent:

Customers see the Agent is typing status Agents see the Customer is typing status
Chat browser-handling functionality to keep a chat session running when users press F5 to refresh. A customizable blinking indicator:

Yellow indicates that a new chat message is waiting Green indicates a new incoming chat Orange indicates a new incoming chat with a new message
NOTE: These are the default colors, but they can be customized.
RF 949: Complete Meeting Packages

NOTE: RF 949 is provided in Siebel Fix Pack 8.1.1.10. RF 949 provides enhancements to the Complete Meeting Packages functionality for Siebel Group Sales and Event Management. Complete Meeting Packages allows hospitality companies to increase revenue by selling prepackaged events. The packages can contain function spaces, sleeping rooms, audio-visual support for meetings, catering, and other event order items, and allow companies to better manage the budgets for events. This enhancement delivers the following key features: Meeting Package Price Adjustments. This allows users to make changes to a package price after the package has been added to a quote, which allows companies to have flexibility when negotiating with their customers. Meeting Package Subfunctions. This allows meeting packages to contain subfunctions.
RF 1053: Support for Customer Dashboard for Open UI

RF 1053 redesigns the Customer Dashboard feature to make it available for Open UI.
33
RF 1069: Support for Microsoft Internet Explorer 10 for Open UI

RF 1069 provides support for Microsoft Internet Explorer 10 for Open UI.
RF 1073: Support for Microsoft Windows 2012

RF 1073 provides support for Microsoft Windows Server 2012 for Siebel Fix Pack 8.1.1.10.
ACR 457: Cross-Network Validation for Network Order Entry

NOTE: ACR 457 was provided in Siebel Fix Pack 8.1.1.2. ACR 457 provides enhancements to the Network Order Entry module for communications customers. Networks in the communications industry can be large and customers may need multiple networks. This enhancement provides the ability to write validation rules across networks. It also provides enhancements for cascade delete.

ACR 471: Promotion AutoMatch

NOTE: ACR 471 was provided in Siebel Fix Pack 8.1.1.1. ACR 471 enables automatic configuration of customizable products based on the promotion definition. The promotion definition includes cardinality rules on various components of the products and include or exclude rules on attributes. Automatic configuration of customizable products is triggered by the following actions: When users change the promotion associated with an existing line item either by selecting the promotion from the promotion picker on an existing line item, or by adding a new promotion line item so that it is associated with an existing line item. When users accept a bottom-up recommendation for a product (this option is available when the user clicks Verify or adds products from the Catalog view). When users upgrade an existing promotion.
34

Siebel Order Management Guide
ACR 474: Order Management Enhancements for Product Integration Packs

NOTE: ACR 474 was provided in Siebel Fix Pack 8.1.1.3. ACR 474 includes enhancements to Siebel Communications, Media, and Energy to support prebuilt integration with various edge applications using Application Integration Architecture. The enhancements include four pre-built Product Integration Packs for various processes. The following sections describe these Product Integration Packs.
Oracle Communications Order to Cash Integration Pack for Siebel Customer Relationship Management
This PIP provides a prebuilt integration that includes Siebel Customer Relationship Management, Oracle Order Service Management (OSM), and Oracle Billing and Revenue Management (BRM) using Application Integration Architecture (AIA) to enable the following processes: Automated product synchronization between Siebel CRM and Oracle Order Service Management Automated order fulfillment from Siebel Customer Management through Central Order Management (OSM COM), Service Order Management (OSM SOM) and Oracle Billing and Revenue Management (BRM) Automated data synchronization to ensure accuracy and real-time availability of customer, product, and pricing data between Siebel CRM and Oracle Billing and Revenue Management
The Siebel Communications, Media, and Energy enhancements delivered for this PIP include: Offer Design Enhancements:

Automated product and pricing data synchronization from Oracle Billing and Revenue Management to Siebel CRM Synchronization of product definition metadata from Siebel CRM to Oracle Order Service Management
Order Delivery Enhancements:
Integrated order lifecycle management for orders (new, revised, follow-on and future-dated orders) captured in the Siebel application and fulfilled through OSM Central Order Management (COM) for service provisioning in OSM Service Order Management (SOM) and billing fulfillment in Oracle Billing and Revenue Management.
35
Integration with Oracle Billing and Revenue Management includes customer synchronization, billing initiation, and fulfillment. Integration between Oracle Service Management Central Order Management and Siebel CRM for Order Fall-out Management by using Siebel Trouble Ticketing for centralized visibility, notifications, and auto-assignment.
Agent Assisted Billing Care (AABC) PIP

This PIP provides a prebuilt integration between Siebel Communications, Energy, and Media and Oracle Billing to enable the following processes: An integration of the billing management process to provide an integrated, real-time, and actionable view of billing data from the CRM system Collection management
The Siebel Communications, Media, and Energy enhancements delivered for this PIP include: Billing Management enhancements that provide the following new views in the Siebel application:

Query Account Balance Query Balance Group, Query Balance Group Details, Query Balance Group Services Query Invoice List, Query Invoice, Query Invoice Charges, Query Invoice Event Details Query Service Usage, Query Service Usage Charges, Query Service Usage Event Details Query Payment, Query Invoice Payment, Create Payment, Create Invoice Payment Query Adjustment, Create Adjustment
Customer Management enhancement that provides a new Update Account view Collections Management Enhancements that provide the following functionality:

Syncs Collection Actions from Billing and Revenue Management to Siebel credit alerts using Enterprise Integration Management Updates the Collection Action status of credit alerts from Siebel CRM to BRM.
Product MDM Integration (PDH) PIP

This PIP provides a prebuilt integration between Siebel Customer Relationship Management, Oracle Billing and Revenue Management (BRM) and Oracle E-Business Suite to enable the following processes: Faster product launch by synchronizing product information from a central hub (Product Information Master Data Hub), to Siebel CRM, Oracle Communications Billing and Revenue Management, and E-Business Suite.
The following objects synchronize product classes and domain values from Oracle Product Hub to Siebel applications:

Synchronize Valuesets to Attribute Definitions Synchronize Item Catalog Categories (ICC) to Product Classes
36
Synchronize Transaction attributes to Product Class XA attributes Synchronize Relationships/Structure under Item Catalog Categories to structure under Product Classes
The following objects synchronize products, product structures, discounts, promotions, and associated pricing information from Oracle Product Hub to Siebel applications:

Synchronize Items to Products/Discounts and Promotions Synchronize Bill Of Materials to Customizable Products and Promotion components Synchronize Pricing Information to Price List entries Synchronize custom UDAs set in the context of items with product UDAs in the Siebel application Synchronize component item exclusions in the context of BOMs Synchronize component attribute value overrides in the context of BOMs
Oracle Customer Hub (CDH) PIP

This PIP provides a prebuilt integration between Siebel CRM, Oracle Billing and Revenue Management (BRM) and Oracle E-Business Suite to enable the following processes: Match Customer. Matches customers against Oracle Customer Hub to retrieve a set of matching customer records in order to identify the closely matching record. NOTE: This feature is not available when integrating with BRM. Fetch Customer. Retrieves the best version of customer records residing in Oracle Customer Hub from the participating application. NOTE: This feature is not available when integrating with BRM. Sync Customer. Synchronizes customer data (Organizations and Persons) between Oracle Customer Hub and participating applications (Siebel CRM and Oracle E-Business Suite). Merge Customer. Publishes the merge operation (of two or more duplicate records inside Oracle Customer Hub) to the participating applications for those applications to merge the same records. NOTE: This feature is not available when integrating with BRM. Enrich Customer. Enables the Oracle Customer Hub to get enriched person data from any thirdparty enrichment provider.
Customer Hub to Siebel CRM, Oracle BRM and Oracle E-Business Suite
This PIP enables a single source of customer truth in UCM and maintains consistent customer information in Siebel applications, Oracle E-Business Suite, and Oracle Billing Revenue and Management.
37

Siebel Order Management Guide Addendum for Communications Siebel Communications Guide
ACR 499: Siebel Bulk Order Enhancements

NOTE: ACR 499 was provided in Siebel Fix Pack 8.1.1.4. This ACR allows organizations to manage the lifecycle of customers' product and service instances through a bulk change process. These bulk changes are typically triggered because of product or service promotions rule changes or customer organization realignments. Siebel Bulk Orders streamlines the bulk creation process and provides the capability to generate a large number of orders by applying a common set of actions to a group of accounts and assets. This capability reduces order entry time and order fallout. ACR 499 provides the following enhancements to Siebel Bulk Orders: Extends the existing Bulk Order action types to allow existing assets that are based on a promotion to be upgraded to a new promotion and allows existing assets that are based on a promotion to be disconnected Provides the ability to apply consistent order validation rules during bulk order generation, and the enforcement of eligibility, compatibility, and complex product validation rules for all bulk order creation scenarios. Extends the action set child type to include agreement, network, and service accounts to allow users to generate bulk orders not only from asset records but also from a given set of agreements or networks that is attached to accounts. Provides the ability to create bulk quotes equivalent to bulk orders Support for performing account group specifications using lists, and analytics to specify multiple accounts or instances on which a common action should be applied Provides a new user interface button control and workflow to submit the orders created in bulk requests to fulfillment. This functionality uses Oracle's Application Integration Architecture (AIA).
You must perform some postinstallation configurations for ACR 499. For more information, see Instructions for ACR 499 and ACR 643 on page 60.

38
ACR 500: CMU Advanced Bundling

NOTE: ACR 500 was provided in Siebel Fix Pack 8.1.1.3. This ACR enhances product bundling (bundled promotions) capabilities commonly required in the Communication, Media and Utilities industries to reduce time-to-market of commercial offers. ACR 500 provides the following features: Merge & Split Promotions Promotion Component Commitment Check Eligibility in Promotion Upgrade Promotion Upgrade - Aggregate Promotion Disconnect Action Promotion components across service accounts Bundle Component into Promotion Promotion Upgrade - Charge Proration Component Level Commitment Recommendation based on Installed Assets Remove assets from bundle

ACR 502: Siebel Product Configurator Enhancements

ACR 502 provides the following usability and performance enhancements to Siebel Product Configurator: Prepick compatibility enablement. Proactively enforces business rules and policies during order capture. Dynamic product defaulting. Supports the ability to define conditional product bundles. Quick Edit Support. Allows rapid option selection and flexible rule enforcement. Dynamic configurator UI controls. Conditionally hides, shows, or inactivates user interface controls based on user selections and context values. Enhanced Product Configurator Script Engine. Enhances rule enforcement through Configurator scripts.

Siebel Product Administration Guide on the Siebel Bookshelf
39
ACR 508: Order to Cash Integration

NOTE: ACR 508 was provided in Siebel Fix Pack 8.1.1.3. Siebel CRM Integration Pack for Oracle Order Management provides a prebuilt solution that provides a streamlined, end-to-end order-to-cash business process that allows a faster time to market for new products and a faster time to revenue. ACR 508 includes the following features: Prebuilt business process maps to enable the complete Order Capture to Cash flow Embedded Oracle Configurator in Siebel CRM Order Capture Synchronized customer, product, pricing, and install base information Two-way synchronization of customers Synchronization of products, assets, and pricelists New Order Creation Order Revision/Cancellation RMA orders ATP Check Credit Check Payment Authorization Shipping Cost Calculation Shipping Details Tax and Freight Charges Order Status Update

ACR 620: Promotion Groups

NOTE: ACR 620 was provided in Siebel Fix Pack 8.1.1.5. Promotion Groups allow users to differentiate their product from their competition through advanced product and service bundling and the emergence of community offerings, which tie various customer assets in a loosely coupled network and provide shared benefits and provisioning functions.
40
Siebel Maintenance Release Guide, Version 8.1.1.10, Rev. B Configuration Instructions for Enhancements and Updates
Allows product administrators to create the structure of promotion groups and components, including membership, product domains, reward products and define rules for pricing, access control, validation and notification Run-time flows to create promotion groups in Quotes and Sales Orders and Top-down and bottom-up flows to create/modify/disconnect Promotion Groups and related Memberships Promotion Group Validation allows administrator to define and enforce validation rules for Promotion Groups, for eligibility and compatibility rules or rules validating the consistency across a Promotion Group. Promotion Group Pricing allows marketers to define and enforce all pricing-related aspects of a Promotion Group, like assigning charges to Promotion Group memberships or creating pricing adjustments to Promotion Group components. Promotion Group Access Control allows product administrator to define and enforce business rules governing who can manage the membership of a given Promotion Group. Promotion Group Notifications allows product administrator to define the different types of notifications to be sent to Promotion Group owners and members in response to business events like new or canceled membership. Promotion Group Commitment allows markers to define commitment rules for promotion groups (such as minimum/maximum runtime, penalty, and so on) as well as to enforce them.

Siebel Communications Guide Siebel Order Management Guide Addendum for Communications
Configuration Instructions for Enhancements and Updates

This topic contains configuration instructions for some of the enhancements and updates provided in version 8.1.1.10, which are listed in Enhancements and Updates in Siebel Fix Pack 8.1.1.10 on page 19. NOTE: In general, it is only necessary to perform the configuration tasks in this section if you want to implement the enhancements that they are for. In general, you 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 84. However, some of these instructions might include steps that you must perform before you install. For this reason, it is strongly recommended that you review all of the configuration instructions before you install the Siebel Fix Pack. 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 Oracle Technology Network (OTN) at http://www.oracle.com/technology/documentation/siebel.html.
41
This topic contains the following subtopics: Instructions for ACR 457 on page 42 Instructions for ACR 471 on page 42 Instructions for ACR 474 on page 43 Instructions for ACR 499 and ACR 643 on page 60 Instructions for ACR 508 on page 65 Instructions for ACR 652 on page 83 Instructions for ACR 756 on page 84 Instructions for Siebel Reports Enhancements on page 84
Instructions for ACR 457

Although using the Incremental Repository Merge (IRM) feature implements any and all enhancements that have been provided since version 8.1.1, in some cases, you must perform configurations.
1 2
From within Siebel Tools, query for the VORD CPVE Validation Service business service. Set the ValidateOtherNetwork user property to TRUE.
Apart from the repository objects, the following workflows have been modified and you need to deploy them if you are using compound product validation for cross-network validation: VORD Validate (Order) VORD Validate (Quote) SIS OM Disconnect Products and Services (modified)
Developers can change the field on which the other network is stored using the ValidateFieldName user property within the VORD CPVE Validation Service business service.

Although using the Incremental Repository Merge (IRM) feature implements any and all enhancements that have been provided since version 8.1.1, in some cases, you must perform configurations. To enable the functionality in ACR 471, navigate to Application Administration > System Preferences, and set the value of the Promotion Automatch system preference to Y.
42

Although using the Incremental Repository Merge (IRM) feature implements any and all enhancements that have been provided since version 8.1.1, in some cases, you must perform configurations. This topic contains the following subtopics: Instructions for Communications PIPs on page 43 Configuring Workflow Monitor Agent on page 46 Configuring Default Tasks for Workflow Monitor Agent on page 46 Generating the Trigger on page 47 Postinstallation Instructions for the MDM PIP on page 59
Instructions for Communications PIPs

The procedures in this section are applicable to the following PIPs: Oracle Communications Order to Cash Integration Pack for Siebel CRM Agent Assisted Billing Care (AABC) PIP Oracle Product Master Data Management (MDM) Integration (PDH) PIP In Siebel Tools, query for the following workflows:

CMU Credit Alert Status Sync CMU SIA Submit Adjustment Request to External SISOMBillingSubmitOrderWebService SWI Account Update Workflow SWI Billing Profile Update Workflow SWI Contact Update Workflow SWI Address Update Workflow SWI Cancel Sales Order_O2C SWI External Account Request Sync Process SWI External Contact Request Sync Process SWI Special Rating - Synchronize Process SWIAdjustmentStatusUpdate SWIOrderUpsert SWIOrderUpsert_O2C SWIOrderUpsertSubProcess SWIQuoteUpsert
43
SWISendATPCheck SWISendATPCheckLine SWISendCalculateShippingCharge SWISendCreditCheck SWISendOrder SWISendPaymentAuthorization SWISendQuote
2 3 4
For each of these workflows, change the default value of the UTCCanonical process property from N to Y. Publish the workflows, and then activate them. Check the status of the workflow processes. If any of them have a status of In-Progress, then publish and activate them.
Required Tasks for the Communications PIPs
Complete the following steps for defining the end point URL for ABS (Outbound Webservices)
a b c
Log into the Siebel application as an administrator and navigate to the Site Map. Select Administration - Web Service > Outbound Web Services. Query for "*JMS* OR *ABCS* OR *ESB* OR *ConfiguratorUserLangSiebelAdapter* OR SyncCustomerSiebelEventAggregator" on the Name field of the Web Services applet.

AdjustmentSiebelCommsReqABCS CalculateShippingChargeSalesOrderSiebelReqABCSImpl CheckATPSalesOrderSiebelReqABCSImpl ConfiguratorUserLangSiebelAdapter CreditCheckSalesOrderSiebelReqABCSImpl ESB_AccountBalanceSiebelCommsReqABCS_Service ESB_ConfiguratorCopyConfigEbizAdapter_Service ESB_InvoiceSiebelCommsReqABCS_Service ESB_UnbilledUsageSiebelCommsReqABCS_Service FetchAccountSiebelReqABCSImpl FetchContactSiebelReqABCSImpl MatchAccountSiebelReqABCSImpl MatchContactSiebelReqABCSImpl PaymentAuthorizationSalesOrderSiebelReqABCSImpl PaymentSiebelCommsReqABCS
44
ProcessSalesOrderSiebelCommsJMSProducer RequestProductStructureSiebelJMSProducer SyncCustomerSiebelEventAggregator SyncInstalledProductListSiebelCommsReqABCSImpl UpdateCreditAlertSiebelCommsReqABCSImpl
d e
Change the Address field for each outbound Web service to point to http:// <HostName>:<PortNumber> (such as http://ap6039fems.us.oracle.com:7797). For inbound Web services, navigate to Administration - Web Services > Inbound Web Services, and make sure that the corresponding Web Services are active. If they are not, change the status from Inactive to Active and click the Clear Cache button.
NOTE: Query for the following inbound web services: * ISS *; * Update Order *; * SWI Update *, SWI*.
Setting Up and Configuring Workflow Policies In order to enable the workflow policies, the following components should be configured and running on Siebel Server (in addition to the Application Object Manager component). Component Name Enterprise Integration Mgr EAI Object Manager (ENU) Workflow Process Manager Workflow Process Batch Manager Workflow Monitor Agent Generate Triggers Component Alias EIM EAIObjMgr_enu WfProcMgr WfProcBatchMgr WorkMon GenTrig Component Group EAI EAI Workflow Workflow Workflow Workflow
NOTE: Enabling the EAI and Workflow Component Groups in the Siebel Server will start all the required components stated above for transaction logging.
To set the Workflow Management component group

Check that the Workflow Management component group is enabled with its components by navigating to Administration > Server Management > Components, and then querying for Workflow*.
To generate a trigger with the Remove parameter set to TRUE 1 2

Navigate to Administration > Server management > Jobs to generate triggers. Create a job for the Generate Triggers component by clicking New and typing Generate Triggers under Component/Job.
45
Define the job parameters with the following values:

EXEC = TRUE Privileged User = <Table Owner> Privileged User Password = <Table Owner> Remove = TRUE Trigger File Name: trigger.sql
Start the job.
NOTE: If the job parameters do not appear when you query for them, then search for them in the Advanced or Hidden section.
Configuring Workflow Monitor Agent

1 2 3 4
Navigate to Administration - Server Configuration > Enterprises > Component Definitions, and query for WorkFlow*. Make a copy of the Workflow Monitor Agent in Administration - Server Configuration > Component Definition and change the name to Workflow Monitor Agent SWI. Change the Alias name to WorkMonSWI. Change the Group Name to "SWI Customer Update Policy Grp" in the component Parameter applet (down). (Under Component Parameters query for "Group Name" and type the SWI Customer Update Policy Grp under Value). Change the Action Interval to a value of 5. Change the Sleep Time to a value of 15. Change the Default Task to 1. Change the status of the new component to "Active" by clicking Activate. Synchronize the components.
5 6 7 8 9
Configuring Default Tasks for Workflow Monitor Agent

The Show Advanced Objects Server Manager parameter controls the display of all the objects that are marked for the advanced user. Workflow Monitor Agent has a parameter called Default Tasks that is hidden and should only be displayed or available to advanced users. Use the following procedure to reveal the hidden Default Tasks parameter, complete the following steps.
To reveal the hidden Default Tasks parameter 1

Navigate to Administration - Server Configuration > Servers.
46
2 3 4
In the top Siebel Servers applet, select the server on which you want to modify the parameter, and under the Component subtab, query for the Server Manager component. Under the Parameters subtab, query for Show Advanced Objects. Change the value to True. NOTE: You must log out from your current user session and log back into the application in order for the parameter to take effect.
Change the Default Task parameter to 1.
Starting the Tasks for Workflow Monitor Agent for Customer Synchronization This section describes the steps to start tasks for the component that is online/enabled.
1 2
Navigate to Administration - Server Management and select Tasks. Query for the WorkMonSWI and Start tasks. Alternatively, use Server Manager to start the tasks.
Start srvrmgr. srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u <userid> /p <password>
Start the task for the WorkMonSWI component.
To restart the server 1 2 3

Stop the Siebel Server. Rename the existing diccache.dat file in the path <Installed Directory> \ses\siebsrvr\bin. Restart the Siebel Server.
Generating the Trigger

Make sure that the system administrator has the necessary privileges for generating triggers before performing this procedure.
To generate the trigger 1 2 3

Navigate to Administration > Server management > Jobs. Create a job for the Generate Triggers component by clicking New and typing "Generate Triggers" under Component/Job. Define the job parameters with the following values:

EXEC = TRUE Privileged User = <Table Owner> Privileged User Password = <Table Owner>
47
Trigger File Name: trigger.sql
Start the job. NOTE: If the job parameters information does not appear when you query for it, then search for it in the Advanced or Hidden section.
5 6
After about five minutes, navigate to Administration > Server Management > Tasks, and check for log details for the task for the Workflow Monitor Agent SWI workflow monitor component. If errors occur, check whether all configurations have been done properly and then repeat To restart the server on page 47 and To generate the trigger on page 47.
Enabling Required System Preferences Use the following procedure to enable required system preferences.
To enable required system preferences 1

From within the application, navigate to Administration - Application > System Preferences, and query for the following list of PIPs, and set the value to TRUE:

Enable AIA Comms Enable AIA MDM Enable AIA OrderToCash Enable AIA Testing
CAUTION: Set the system preference to TRUE only for the required PIPs. The AIA Comms PIP and the AIA OrderToCash PIP cannot coexist.
Within the System Preference Name field, query for Validate Due Date and set the value in the System Preference Value field to 2. If querying for this preference does not yield any results, create this value. Query for Cancel Error Mode in the System Preference Name field and set the System Preference Value to 3 (the default value). Update the AIA Version system preference to 2.5.1. Restart the Siebel Server.
3 4 5
Setting Up the Integration User This section describes the integration user setup process. A new flag has been introduced to identify an integration user (needed while integration testing). This user credential needs to be configured (at AIA side) for the Siebel Inbound Web services call from the Application Integration Architecture side to avoid the boomerang effect. The following procedures describe the process of setting up the integration user:
1 2
48
Log into the application as an administrator, navigate to the Administration - User > Employee view, and verify that the list applet contains the Integration User flag. Set the Integration User flag to Y for the new integration user.
Setting Order Priority for AQ Use the following procedure to set order priority for AQ.
To set the order priority for AQ 1 2 3

Navigate to the Administration - Data > List Of Values view. Query for Type equals SWI_ORDER_JMS_PRIO_MAPPING. Change the values in the Language-Independent Code column to define the new mapping as per following table: Display Value Low Medium High Urgent Language-Independent Code 6 4 2 0
Click Clear Cache to clear the cache.
Advanced Queue Configuration NOTE: Advanced queue configuration is only required for the 10g client.
Extract oc4j-extended.zip from http://download.oracle.com/otn/java/oc4j/101330/ oc4j_extended_101330.zip to a folder on a machine where the Siebel Server is installed (such as the D:\JMS folder). Copy Siebel.jar and SiebelJI_enu to the D:\JMS folder. (These jar files are located in the <Siebel Server installation directory>\classes folder.) Copy the jndi.jar file from Fusion Middleware to the D:\JMS\j2ee\home\lib folder. Copy com/evermind/util/JCAProperties.class from the oc4j-internal.jar file to the D:\JMS folder. Create a file called jndi.properties with following details in the D:\JMS path: java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory java.naming.provider.url=opmn:ormi://<IP Address of the FMW server>:<OPMN Port No>:oc4j_soa java.naming.security.principal=anonymous For example: java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory java.naming.provider.url=opmn:ormi:// 152.68.240.154:6009:oc4j_soa java.naming.security.principal=anonymous Make sure that there are no extra spaces in the jndi.properties file.
2 3 4 5
49
Create a Named Subsystem in the Siebel application through the server manager:
Connect to the 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> Example: srvrmgr /g sdc78198svqe:4330 /e siebel /s sdc78198svqe /u sadmin /p sadmin
Run the following command to create the named subsystem and add the jar file into the class path. Create named subsystem JAVA for subsystem JVMSubSys with DLL=C:\Sun\SDK\jdk\jre\bin\server\jvm.dll, CLASSPATH = D:\JMS;D:\JMS\Siebel.jar;D:\JMS\rdbms\jlib\aqapi.jar;D:\JMS\jdbc\lib\ocrs12.jar;D:\JMS\ jdbc\lib\ojdbc14dms.jar;D:\JMS\jdbc\lib\orai18n.jar;D:\JMS\SiebelJI_enu.jar;D:\JMS\j2ee\ home\lib\adminclient.jar;D:\JMS\j2ee\home\lib\jndi.jar;D:\JMS\j2ee\home\lib\jta.jar;D:\J MS\j2ee\home\oc4jclient.jar;D:\JMS\j2ee\home\lib\bcel.jar;D:\JMS\j2ee\home\lib\jms.jar ;D:\JMS\j2ee\home\lib\javax77.jar;D:\JMS\lib\dms.jar;D:\JMS\opmn\lib\optic.jar;D:\JMS\ j2ee\home\lib\ejb.jar;., VMOPTIONS= D:\JMS\log\jms.log For Unix, the CLASSPATH should be separated by a colon (:) and for Windows it should be separated by a semicolon (;). The command for Unix should be the following: Create named subsystem JAVA for subsystem JVMSubSys with DLL= /usr/jdk1.5.0_06/jre/lib/sparc/client/libjvm.so, CLASSPATH = /export/home/qa1/ JMS:/export/home/qa1/JMS/Siebel.jar:/export/home/qa1/JMS/rdbms/jlib/aqapi.jar:/ export/home/qa1/JMS/jdbc/lib/ocrs12.jar:/export/home/qa1/JMS/jdbc/lib/ ojdbc14dms.jar:/export/home/qa1/JMS/jdbc/lib/orai18n.jar:/export/home/qa1/JMS/ SiebelJI_enu.jar:/export/home/qa1/JMS/j2ee/home/lib/adminclient.jar:/export/home/qa1/ JMS/j2ee/home/lib/jndi.jar:/export/home/qa1/JMS/j2ee/home/lib/jta.jar:/export/home/ qa1/JMS/j2ee/home/oc4jclient.jar:/export/home/qa1/JMS/j2ee/home/lib/bcel.jar:/export/ home/qa1/JMS/j2ee/home/lib/jms.jar:/export/home/qa1/JMS/j2ee/home/lib/javax77.jar:/ export/home/qa1/JMS/lib/dms.jar:/export/home/qa1/JMS/opmn/lib/optic.jar:/export/ home/qa1/JMS/j2ee/home/lib/ejb.jar:., VMOPTIONS= /export/home/qa2/JMS/log/jms.log
Make sure that the path is correct for all the files and that the CLASSPATH ends with a . (dot). Here qa2 should be replaced with the appropriate folder name.
Log into the Siebel application and navigate to Site Map > Administration Server Configuration > Profile Configuration.
a b c
Query for the JAVA profile in the profile list and make sure the parameters are correct. For the Windows environment, edit the value of VMOPTIONS to -Djms.log=D:\JMS\log\jms.log. For the Solaris environment, edit the value of VMOPTIONS to -Xusealtsigs -Xrs -Djms.log=/ export/home/qa2/JMS/log/jms.log.
Make sure that the JMS/log folder exists and has write permission.
50
Restart the Siebel Server. NOTE: For more information, see the Siebel Enterprise Application Integration (EAI) documentation on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/ siebel.html.
Configuring Corresponding Web Services for Advanced Queue (AQ) The following section contains information about how to configure corresponding Web services for AQ. For more detailed information about AQ configuration, refer to the topic about configuring JMS messaging between Siebel Business Application and Oracle SOA using Oracle Advanced Queuing in Transports and Interfaces: Siebel Enterprise Application Integration on the Siebel Bookshelf. Use the following procedure to configure corresponding Web services for AQ.
To configure corresponding Web services 1 2

Navigate to Site Map > Administration - Web Services > Outbound Web Services and query for SWI*. Change the transport to JMS and address as follows: jms://<queue name>@<connection factory> where: <queue name> is in the following format: java:comp/resource/ <Resource Provider Name as configured >/Queues/<queue name> where: <connection factory> is in the following format: java:comp/resource/<Resource Provider Name as configured>/QueueConnectionFactories/ QCF Queues were created as part of installing Application Integration Architecture. Refer to the same same queue name here.
To locate the Connection Factory Name, log into the Application Server control, and navigate to oc4j_soa ' Administration > Database Persistence. Here you can find the Resource Provider Name if it is configured. Example: jms://java:comp/resource/AIA_JMS_RP/Queues/ AIA_SALESORDERJMSQUEUE@java:comp/resource/AIA_JMS_RP/QueueConnectionFactories/ QCF
After changing the address, click Clear Cache.
Setting Session Pool Manager The Session Pool Manager (SPM) is a service in the SOA Web server that manages a pool of Web server session tokens that are reused among BPEL flows.
51
If SPM is enabled in AIA, use the following procedure to set Session Pool Manager values.
To set Session Pool Manager values 1 2 3

Navigate to <siebel installation folder>/eappweb/bin, and make a backup copy of the eapps.cfg file. Open eapps.cfg, and search for /eai_enu. Add the following parameters:

SessionTimeout = 300 SessionTokenTimeout = 15 SessionTokenMaxAge = 2880 SWSENoSessInPref = TRUE
Restart the Siebel Web Server.
Configuring Java Subsystem for Fusion Middleware 11g Integration In addition to performing the setup tasks for integrating Fusion Middleware in the Siebel installation guide, perform the following procedure. NOTE: The paths in this procedure assume you are running the Siebel server on the Windows operating system. They must be modified if the Siebel server is running on a UNIX operating system. Use the following procedure to configure Java subsystem for Fusion Middleware 11g Integration.
To configure Java subsystem for Fusion Middleware 11g Integration 1

Get the wlfullclient.jar file from the FMW/AIA team. If you cannot get this file, perform the following steps to create wlfullclient.jar in the FMW server:
a b c 2 3 4
WinScp to the SOA server. Change directories to the server/lib directory. (For example, go to WL_HOME/server/lib.) Execute the java -jar wljarbuilder.jar command. The wlfullclient.jar file is created.
Remotely log into the Siebel installed server. Get the Siebel.jar and SiebelJI_enu.jar files from the <siebelinstallation>\ses\siebsrvr\classes folder. Copy the wlfullclient.jar, Siebel.jar and SiebelJI_enu.jar files to the D:\JMS directory. If this directory does not exist, create it.
52
Prepare the jndi.properties file with the following values: java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory java.naming.provider.url=t3://<FMW_HOST>:<SOA_PORT> java.naming.security.principal=<UserName> java.naming.security.credentials=<Password> NOTE: If AIA is running on a clustered environment and a proxy host has been set up, then jndi.properties will have the following URL: java.naming.provider.url=http:// <FMW_HOST>:<PROXY_PORT>.
6 7
Create the JAVA Subsystem using the Siebel Web application. Connect to the server manager from the bin directory of the Siebel installed folder by entering the following command from the command prompt: Srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u <userid> /p <password> Example: srvrmgr /g sdc78198svqe:4330 /e siebel /s sdc78198svqe /u sadmin /p sadmin
Enter the following command to create the named subsystem: Create named subsystem JAVA for subsystem JVMSubSys
Add the following parameters with the CLASSPATH, DLL and VMOPTIONs aliases:
Data Type String
Name JVM Classpath
Alias CLASSPATH
Value D:\JMS;D:\JMS\Sie bel.jar;D:\JMS\Sieb elJI_enu.jar;D:\JMS \wlfullclient.jar;. C:\Sun\SDK\jdk\jre \bin\server\jvm.dll Name
Scope Subsystem
Type JVM Configuration Subsystem JVM Configuration Subsystem JVM Configuration Subsystem
Description JVM Classpath
Visibility Basic
JVM DLL Name JVM Options
DLL
String
Subsystem
JVM DLL Name JVM Options
Basic
VMOPTION S
String
Djms.log=D:\JMS\lo g\jms.log
Subsystem
Basic
10 Create the Simulator with the EAI JMS Transport as the service name and CheckAll as the method
name.
11 In the Input Argument section, create Test Case 1 with the following values:

Type: PropertySet Properties: PropertyName: ConnectionFactory PropertyValue: jms/TestQueueCF PropertyName: SendQueue
53
PropertyValue: jms/TestQueue
12 Click Run to verify the setup in the simulator and verify that the setup was successful. To activate the rule sets for Comms 1 2
Query for the Order Validation rule set. If two versions are displayed as active, select the earliest version. For example, if the active versions are 5 and 6, select version 5.
3 4
Select Deactivate Rule Set from the submenu. Navigate to Administration - Runtime Events > Events screen, and select Reload Runtime Events from the drop-down list.
NOTE: If two active versions are displayed for SWI Order Validation Rule Set, use the previous procedure.
Running EIM Data Migration for Comms This section defines the detailed steps to run the EIM jobs for Siebel applications as a part of the Creating and Updating Credit Alerts for Collection Flows functionality in AIA COM 2.5.1. Collections flow allows credit alerts to be created in the Siebel application based on scenarios defined in Oracle Billing and Revenue Management using Oracle Data Interchange and Siebel EIM. Before you begin your import, do the following: Make sure that the Siebel Server is up and running. Make sure that the Siebel EIM component is online and running properly. To check this, navigate to the Administration - Server Configuration and Administration - Server Management screens. To avoid data loss, do not restart the Siebel server while the EIM job is running. After you have completed loading data for one country, make a backup copy of the EIM logs for status verification. (These logs are located under siebsrvr/logs.)
Use the following procedure to execute the EIM job to create and update credit alerts.
To execute the EIM job to create and update credit alerts 1 2 3

Move the ProcessAlertsAndBillingProf.ifb file from <Tools Installation directory>/REPPATCH/ ACR474/EIM to <Siebel Installation Directory>/ses/siebsrvr/ADMIN. Run the EIM job with the ProcessAlertsAndBillingProf.ifb configuration file. Verify that the EIM job is successful.
Enabling Dynamic Pricing (Customer Order Management) The pricing module is available in multiple licensing modes.
54
Dynamic Pricing Mode This mode provides pricing capabilities such as attribute pricing, promotions, aggregate discounts, and so on. It leverages the variable maps that contain the XA child variable maps. It is available only to users who have the Dynamic Pricer license. Dynamic Pricing can also be enabled by navigating to Admin - Pricing > Price List, and selecting Enable Dynamic Pricing from the applet-level menu. This is a new implementation in Siebel version 8.1.1 applications. After you select Enable Dynamic Pricing, all the necessary changes will be performed.
Configuring the Email Notification for the Product Class and Attribute Query Feature Users to whom emails need to be sent need to be added to the user list.
To add/change the email addresses for the user list 1 2 3 4

Navigate to Administration - Users > Users. Add the user name and user ID. Add the email address in the contact information of the child applet. Navigate to Administration - Group > User Lists and query for the SCE Users user list. NOTE: If this list does not appear, create it.
Add the users created in the user list.
The user list created in the previous procedure is passed in the run time events. Use the following procedure to add the changed user list.
To change the BO/BC/Field name to extract the email addresses 1

Navigate to Administration - Run Time Events > Action Set, and query for the EmailNotify action set.
55
Query for the GetEmailAddr action in the child applet. The following is the business service context syntax: "Parent BC Record Name";"Field Name in Child BC ";"BO Name ";"Parent BC";"Child BC" For instance "SCE Users";"Email Address";"Account";"Account";"Contact" or "SCE Users";"EMail Addr";"User List";"User List";"User" The following runtime events use the action set described above. Action Set Name EmailNotify EmailNotify EmailNotify
Sequence 1 2 3
Object Type BusComp BusComp BusComp
Object Name Attribute VOD BusComp ISS Class VOD BusComp ISS Joint Workspace BusComp
Event PreInvokeMethod PreInvokeMethod PreInvokeMethod
Subevent SendEmail SendEmail SendEmail
Four communications templates are used to send email messages. The Attribute Defn and Product Class templates are already configured. Use the following procedure to configure or edit other templates.
To edit or configure email template text 1

Create a notepad file called Attribute_Template.txt and add the following values:

Attribute Name: [Name] Description: [Description] Type: [Type] Object Number: [Object Number] XRef Class Name: [XRef Class Name]
Create a notepad file called Class_Template.txt and add the following values:

Class Name: [Name] Description: [Description] Type: [Type] Object Number: [Object Number]
56
3 4 5 6 7 8 9
Navigate to Administration - Communication > All Templates > Template Items. Query for Workspace Attribute Defn Template and click on the Template Items view. Attach the Attribute_Template.txt file that you created in Step 1 on page 56 to the template item. Navigate to Administration - Communication > All Templates > Template Items. Query for Workspace Product Class Defn Template and click on the Template Items view. Attach the Class_Template.txt file that you created in Step 2 on page 56 to the template item. Make sure that ISS Joint Workspace VOD Pick BusComp is selected in the iteration child business component for the two template items. The communication template names are added in the user properties of the business components listed in the following table: Business Component ISS Joint Workspace BusComp ISS Joint Workspace BusComp Attribute VOD BusComp ISS Class VOD BusComp User Property PackageNameList|Attribute Definition PackageNameList|Product Class Definition PackageNameList PackageNameList Template Name Workspace Attribute Defn Template Workspace Product Class Defn Template Attribute Defn Template Product Class Template
The SMTP Server name, From Email Address, and POP server details are added in the Communication profile. Use the following procedure to add the SMTP server name, From Email Address, and POP server details.
To change the SMTP Server name, From Email Address, and POP server details 1 2
Navigate to Administration - Communications > Communications Drivers and Profiles. Query for the Internet SMTP/POP3 Server communication driver, and if it does not exist, create it using the following values:

Name: Internet SMTP/IMAP Server Channel Type: Email Channel String: POP3SMTP Library Name: sscmmail Outbound: Yes
3 4
Query for Default SMTP in the child applet, and if it does not exist, create it. Change the SMTP and POP Server details in the grandchild applet, using the following values:
From Address: siebel.product.admin@demohost.siebel.com
57
POP3 Account Name: support POP3 Account Password: support POP3 Server: demohost.siebel.com SMTP Server: rgmamersmtp.oraclecorp.com
The communication profile is added in the user properties of the business components listed in the following table: Business Component ISS Joint Workspace BusComp Attribute VOD BusComp ISS Class VOD BusComp User Property CommProfileOverride CommProfileOverride CommProfileOverride Template Name Default SMTP Profile Default SMTP Profile Default SMTP Profile
To set up the Time-Based Offering feature 1

Create Product Master Data.
Create three attributes:

Duration (Number/Enumerated, values 1, 2,3, 31) DurationUnitOfMeasure (Text/Enumerated values: Days, Months, Years) DurationValidityStart (Text/Enumerated Values: Original Start, Now, Original End)
b c
Create a class with the preceding three attributes.
NOTE: The class attribute names and the attribute definition names must be identical. For the TBO Discount products synced from BRM, change the structure type to Customizable, change the product type to Time Based Offer, and associate the preceding TBO class to this product.
Create a job to inactive assets.
Navigate to Server Management > Jobs, and create a new job.

Select Workflow Process Batch Manager as the component. Select Y as the value for repeating. Select the Siebel Server as the requested server. Select Days as the repeat unit. Select 1 as the repeat interval. Select Scheduled Start as the Repeat From value
b c d
Navigate to Job Parameters and create a new parameter. Select Workflow Process Name as the name and specify SWI Asset Status Update as the value. Select Search Specification as the name and specify the value if necessary.
58
Create revision data maps:
a b c d 4
Navigate to Administration Application, and then Data Map Administration. In Data Map Object, query for Revise Order or ReviseQuote. In Data Map Component, query for Line Item. In Data Map Field, add the fields that need to be copied during revision (such as Service End / Service Start Date/Due Date).
Configure the business service. The business service name must be specified as the value for the Business Service Query Access List server component parameter. For example, if the server component is eCommunications Object Manager (ENU), navigate to its parameters, query for Business Service Query Access List, add CMU External Integration Service as the value, and restart the server component so that the change to the component parameter value takes effect.
Release the data maps:
a b
Navigate to Site Map > Administration- Order Management > Variable Maps. In Variable Map, query for the following:

Default Pricing Eligibility Variable Map - Row Set Default Pricing Variable Map - Row Set Default Pricing Variable Map XA
Lock the preceding variable maps and release a new version.
Postinstallation Instructions for the MDM PIP

The following tasks are required if you are using the MDM PIP.
To activate the workflow policies 1 2

Navigate to Administration - Business Process Screen, and then Workflow Policies view. Query for the following workflow policies and remove the expiration date:

SWI Account Address Sync Policy SWI Account Contact Sync Policy SWI Account Sync Policy SWI Address Sync Policy SWI Contact Address Sync Policy SWI Contact Sync Policy
Remove the existing triggers, and then generate the triggers.
59
Restart Siebel Services. NOTE: By default, the Workspace Release Flag user preference is set to N. If you want to release products into the Siebel application automatically, you must change this preference.
To customize the Workspace Release flag 1 2

Navigate to Site Map > Administration - Application > System Preferences. Query for the Workspace Release flag, set the value to N, and restart the server.
Instructions for ACR 499 and ACR 643

Although running Siebel Incremental Repository Merge implements any and all enhancements that have been provided since version 8.1.1, in some cases, you must perform postinstallation configurations. This topic contains the following subtopics: Setting Up Customer Order Management Workflows on page 60 Modifying Pricing Signals on page 62 Updating Data Maps for Bulk Orders on page 62 Updating the ABO Bulk Request SIS OM Order Integration Object Map on page 62 Updating the ABO Bulk Request SIS OM Quote Integration Object Map on page 64
Setting Up Customer Order Management Workflows

Use the procedures in the following topic to set up Customer Order Management workflows.
To deactivate workflow processes 1

Navigate to Administration Business Process > Workflow Deployment, and within the Group field the Active Workflow Processes list, query for the following workflow groups:

Configurator Asset Based Ordering Eligibility & Compatibility Compound Product Validation Product Recommendation Product Promotions Pricer C/OM UI Processes User Registration
60
CUT Order Management SIS OM ABO Bulk Request
2 3
Multiselect the records, and from the applet menu, select Deactivate Process. NOTE: The status of the selected workflow groups should be Inactive. In the Active Workflow Processes list, within the Name field, query for the following workflows:

ABO* Verify* Transform* SIS OM* *Refresh* Submit* SWI*
Multiselect the records, and from the applet menu, select Deactivate Process.
To remove workflow processes from runtime events 1 2

In the Active Workflow Processes list of the Workflow Deployment view, select the workflows listed in Step 1 on page 60 and Step 3 on page 61. Multiselect the queried records, and from the applet menu, select Delete Process.
To activate workflow processes 1

Navigate to Administration Business Process > Workflow Deployment, and within the Group field in the Repository Workflow Processes list, query for the workflow groups listed in Step 1 on page 60. Multiselect the queried records and click the Activate button. Within the Name field in the Repository Workflow Processes list, query for the following workflows:

2 3
ABO* Verify* Transform* SIS OM* *Refresh* Submit* SWI* RAF*
61
Product*Offer*
Multiselect the queried records and click the Activate button.
Modifying Pricing Signals

The Dynamic Pricing feature is not enabled by default. If you want to use this feature and you have a license for the functionality, you must perform the following procedure to switch from Basic Pricing to Dynamic Pricing.
1 2
Navigate to Administration - Pricing > Price Lists view. Select Menu, and then select Enable Dynamic Pricing. The Dynamic Pricing dialog box appears to confirm that Dynamic Pricing has been enabled. Enabling Dynamic Pricing automatically changes all of the standard pricing signal definitions.
Click the Clear Cache button.
Updating Data Maps for Bulk Orders

Use the following procedure to update the data maps for Bulk Orders functionality.
To update the data maps for Bulk Orders 1

Navigate to Administration - Integration > Data Map Editor, and within the Name field in the Integration Object Map list, query for the integration object maps listed in the following table: Target Object Name ABO Bulk Request Order ABO Bulk Request Quote SIS OM Quote SIS OM Order
Name Bulk Request Order IO Map Bulk Request Quote IO Map ABO Bulk Request SIS OM Quote IO Map ABO Bulk Request SIS OM Order IO Map
Source Object Name SIS OM Order SIS OM Quote SIS OM Quote SIS OM Order
2 3
Navigate to the Integration Component Map list applet, and if integration component maps exist, delete the entries. After you delete the integration component maps, click the Auto Map button in the Integration Object Map applet to update the mapping between the source and destination objects.
Updating the ABO Bulk Request SIS OM Order Integration Object Map
Use the following procedure to update the ABO Bulk Requests SIS OM Order integration object map.
62
To update the ABO Bulk Requests SIS OM Order integration object map 1 2
Navigate to Administration - Integration > Data Map Editor, and within the Name field in the Integration Object Map List, query for ABO Bulk Request SIS OM Order IO Map. Verify that the entries in the following table exist in the corresponding Integration Component Map list applet: Source Component Name Header Line Item XA Deleted Item Target Component Name Header Line Item XA Deleted Item Header Line Item Line Item Parent Component Map Name
Name Header_to_Header Line Item_to_Line Item XA_to_XA Deleted Item_to_Deleted Item Deleted Item
3 4
Navigate to the Integration Component Map list and select Header_to_Header. In the Integration Field Map applet, within the Target Name Field, query for Order Type, and update the Source Expression Field with the following values:

Target Field Name: Source Expression Field Order Type: LookupValue("FS_ORDER_TYPE", "Bulk Request Template Order")
5 6
Navigate to the Integration Component Map list and select Header_to_Header. In the Integration Field Map applet, and within the Target Name field, query for the items listed in the following table and delete the entries: Source Expression [Order Number] [Revision Number] Target Field Name Order Number Revision Number
7 8 9
Navigate to the Integration Component Map list and select Line Item_to_Line Item. In the Integration Field Map applet, within the Target Name field, query for the items listed in the preceding table and delete all the entries. In the Integration Field Map applet for all four integration component maps, delete the field mappings for the items listed in the following table: Source Expression [Created] [Created By] [Id] [Mod Id] Target Field Name Created Created By Id Mod Id
63
Source Expression [Updated] [Updated By]
Target Field Name Updated Updated By
Updating the ABO Bulk Request SIS OM Quote Integration Object Map
Use the following procedure to update the ABO Bulk Request SIS OM Quote integration object map.
To update the ABO Bulk Request SIS OM Quote integration object map 1 2
Navigate to Administration - Integration > Data Map Editor, and within the Name field in the Integration Object Map list, query for ABO Bulk Request SIS OM Quote IO Map. Verify that the entries in the following table exist in the corresponding Integration Component Map List applet: Source Component Name Header Line Item XA Deleted Item Target Component Name Header Line Item XA Deleted Item Header Line Item Line Item Parent Component Map Name
Name Header_to_Header Line Item_to_Line Item XA_to_XA Deleted Item_to_Deleted Item Deleted Item
3 4
Navigate to the Integration Component Map list and select Header_to_Header. In the Integration Field Map applet, within Target Field Name, query for Quote Type, and update the Source Expression field with the following values:

Target Field Name: Source Expression Field Quote Type: LookupValue("QUOTE_TYPE", "Bulk Request Template Quote")
5 6
Navigate to the Integration Component Map list and select Header_to_Header. In the Integration Field Map applet, within Target Field Name, query for the entries listed in the following table and delete them: Source Expression [Quote Number] [Revision Number] Target Field Name Quote Number Revision Number
7 8
Navigate to the Integration Component Map list and select Line Item_to_Line Item. In the Integration Field Map applet, within Target Field Name, query for the items listed in the table in Step 6 on page 64, and delete the entries.
64
In the Integration Field Map applet for all four integration component maps, delete the field mappings for the items listed in the following table: Source Expression [Created] [Created By] [Id] [Mod Id] [Updated] [Updated By] Target Field Name Created Created By Id Mod Id Updated Updated By

Although using the Incremental Repository Merge (IRM) feature implements any and all enhancements that have been provided since version 8.1.1, in some cases, you must perform configurations. Use the procedures in the following topics to configure ACR 508.
To enable required system preferences for ACR 508

Within the application, navigate to Administration- Application > System Preferences, query for the following list of PIPs, and sent the value to TRUE:

Enable AIA Testing Enable AIA Order to Cash
Use the following procedure to disable Asset-Based Ordering.
To disable Asset-Based Ordering 1 2 3 4

Log into the Siebel application, and navigate to Site Map > Administration - Server Configuration > Servers > Parameters. Query for the corresponding object manager for the application (such as htimObjMgr_enu for application HTIM). Query for the Order Management - Enable Asset Based Ordering parameter in the parameter list for the component, and set the value to False. Restart the Siebel Server.
Running EIM Data Migration This section describes how to run the EIM jobs for loading initial data for the integration with EBusiness Suite.
65
Data Migration Sequence The below entities should be executed in sequence to maintain the data integrity. This includes the pre-and post-EIM activities, which need to be carried out manually. S.No 1 2 4 5 5 6 7 Main Entities Organization Inventory Location Products Post EIM Product Release Pricelist Customers Assets Task Type Manual Manual EIM Manual EIM EIM EIM
Before you begin the EIM import, note the following: Make sure that the Siebel Server is running. Make sure that the Siebel EIM component is online and is running properly. (To check this, navigate to the Administration - Server Configuration or Administration - Server Management screens.) To avoid data loss, do not restart the Siebel Server while the EIM job is running. After you have completed the data load for one country, make backup copies of the EIM logs, for status verification. These logs are located in the siebsrvr/logs directory.
Checking EIM Component Availability Use the following procedure to check EIM component availability.
To check EIM component availability 1

Navigate to the Administration - Server Management screen, then Servers, and then the Component Groups view. Make sure that the component group Enterprise Application Integration is active and online. Make sure that the Enterprise Integration Manager component within the Workflow Management component group is also active and online. Navigate to the Administration - Server Configuration screen, then Enterprise, then Component Groups, and then the Components Group Assignments view. Make sure that the Enterprise Application Integration Component Group is enabled.
2 3 4
Setting Up Organizations and Inventory Locations Use the following procedure to set up organizations and inventory locations.
66
To set up organizations 1 2
Navigate to the Administration - Group screen, and then the Organizations view. Create the required organizations. NOTE: Enter information into the Organization Name field but leave the Site field blank.
To set up inventory locations 1 2

Navigate to the Administration - Data screen, and then the Inventory Locations view. Create inventory locations. NOTE: Make sure that the inventory location is associated with the correct location.
Executing the EIM Job Use the following procedure to execute the EIM job.
To execute the EIM job 1

Place the respective IFB file on the server machine using the Siebsrvr/Admin file path, as shown in the following example: Component Product Pricelist Customer Asset IFB File Product.ifb Pricelist.ifb Customer.ifb Asset.ifb
Make sure that the SESSION SQL statement of the [UPDATE ACCOUNT NUMBER] section of the Customer Ifb file is modified in order to reflect the working instance: UPDATE ORA19111.EIM_ACCOUNT SET OU_NUM = T_ORG_EXT__RID WHERE IF_ROW_BATCH_NUM=100 where ORA19111 is the working instance. Also, the same should be considered for the [UPDATE INTEGRATION ID] section of the Pricelist.ifb file: SESSION SQL = "UPDATE ORA19111.EIM_PRI_LST SET PL_INTEGRATION_ID = NULL WHERE PL_INTEGRATION_ID IS NOT NULL" For Pricelist.ifb, comment the second process using a terminate symbol (so that it becomes inactive and only the first process is executed), like this: [IMPORT ALL PRICELISTS] TYPE = SHELL
67
INCLUDE = "IMPORT PRICELIST" ;INCLUDE = "UPDATE INTEGRATION ID" Once EIM imports all of the pricelist data and the Integration Id is populated, the administrator needs to run another ODI API to populate the cross-reference database. Then, the administrator needs to run EIM again to nullify integ_id. The format of the IFB file for the second run will look like: [IMPORT ALL PRICELISTS] TYPE = SHELL ;INCLUDE = "IMPORT PRICELIST" INCLUDE = "UPDATE INTEGRATION ID" All the job parameters should remain the same for both of the runs.
3 4 5 6
Log into the application with administrator credentials in order to be able to access the Server Management screen. Navigate to the Administration - Server Management screen, and then the Jobs view. Click New and select "Enterprise Integration Mgr" in the Component/Job tab. In the "Job Parameters" applet, fill in the following parameters:

Configuration file = .Ifb File name Error Flags = 1 SQL Trace Flags = 8 Trace Flags = 1
7 8 9
After passing parameters, click Submit Job. In the Jobs view, for each job that you have executed, make sure that the Status column displays Success for the jobs that you have executed. Check the status in the EIM table by executing the SQL statements in the following section. In each case, make sure that the status is IMPORTED.
Products Product Header: SELECT COUNT(*),IF_ROW_STAT FROM EIM_PROD_INT WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT Product Details: SELECT COUNT(*),IF_ROW_STAT FROM EIM_PROD_INT1 WHERE IF_ROW_BATCH_NUM = '100'
68
GROUP BY IF_ROW_STAT Product-Inventory Locations: SELECT COUNT(*),IF_ROW_STAT FROM EIM_PRODINVLOC WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT Pricelists In this case since the same set of records are processed twice by the two separate sections of the IFB file: one meant for importing the Pricelist Records and other meant for updating the Integration Id to NULL, you will get the DUP_REC_EXISTS status in the EIM tables. SELECT COUNT(*),IF_ROW_STAT FROM EIM_PRI_LST WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT Customers Address: SELECT COUNT(*),IF_ROW_STAT FROM EIM_ADDR_PER WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT Account: SELECT COUNT(*),IF_ROW_STAT FROM EIM_ACCOUNT WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT Account Details: SELECT COUNT(*),IF_ROW_STAT FROM EIM_FN_ACCNT1 WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT Customer: SELECT COUNT(*),IF_ROW_STAT FROM EIM_CONTACT WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT
69
Assets There are two sections in the IFB file: For Importing Assets and For Updating the Parent Assets. Hence the status will show DUP_REC_EXISTS SELECT COUNT(*),IF_ROW_STAT,IF_ROW_BATCH_NUM FROM EIM_ASSET WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT,IF_ROW_BATCH_NUM Use the following procedure to check the EIM log.
To check the EIM log 1 2 3

From the Jobs view in the Administration - Server Management screen, navigate to the Tasks View in the same screen. Get the Task Number from the Task field. Navigate to the Siebsrvr\log directory and query for the locate the log file using the Task #. The log file contains details about of every level of processing, as well as information about any errors.
To release the products 1 2

Navigate to the Administration - Business Service screen. In the top applet, create a new record with the following values:

Service Name: ISS Authoring Import Export Service Method Name: Post_EIM_Upgrade
In the bottom applet, create the Input Argument by creating pop up icons on the Property Name Field, using the following values:

Property Name: ReportOnly Value: FALSE Property Name: RootObjectType Value: ISS_JWS Property Name: RootObjectName Value: Staging Mode 1
NOTE: The RootObjectName should be any meaningful name for the Joint Workspace Project. This will be created automatically after the Business Service is executed from the simulator.
Click the Run button in the top applet and wait until the job ends.
To get the joint workspace Row ID 1

Navigate to the Administration - Product screen, and then the Workspace Projects view.
70
2 3 4
Query for the value provided for the RootObjectName input parameter given while running the ISS Authoring Import Export Service (as in Step 3 of To release the products on page 70). Go to the Menu option and click the About Record method or use the keyboard shortcut (CTRL + ALT + K) while on the active record. Make a note of the Row # value displayed in the pop-up applet, as you will need this value to provide the input argument to the workflow process.
To release the noncustomizable and orderable products 1 2 3 4

Navigate to the Administration - Business Process screen, then Workflow Deployment, and then the Repository Workflow Processes view. In the "Active Workflow Processes" view, search for the "SWI Initial Load Non CP Order Release" workflow to make sure that the active version of the workflow is present in the repository. If this record is not present, query for the SWI Initial Load Non CP Order Release workflow in the Repository Workflow Processes applet, and click Activate after you locate the record. If the workflow is not present in either of the previous applets, within the Active Workflow Processes applet, select Menu, select the Import Processes functionality, and choose the SWI Initial Load Non CP Order Release -WF.xml file from the Browse window. Navigate to the Administration - Server Management screen, and then the Jobs view. Click the New button on the top applet to create a new job, and enter "Workflow Process Batch Manager" as the value for Component/Job. Navigate to the "Job Parameters" applet and create the following two new values:

5 6 7
Name= Workflow Process Name Value = SWI Initial Load Non CP Order Release Name Search Specification Value = [Par JWS Id] = '6SIA-4HVMH' AND [Orderable Flag] = 'Y' AND [Product Def Type Code] <> LookupValue ("PROD_TYPE_CD", "Customizable")
NOTE: The Parent Joint Workspace Id value is the same as the one in Step 4 of To get the joint workspace Row ID on page 70.
Click the "Submit" button and wait until the job ends successfully.
Configuring Oracle Configurator

Use the procedures in the following topic to configure Oracle Configurator.
To compile the projects for generating scripts 1

Within Siebel Tools, navigate to Menu > View > Options > Scripting tab, and specify the following path for the Browser script compilation folder. \\<Server IP address>\<SWE server Installed Location>\eappweb\PUBLIC\enu
71
Compile all of the projects using the Compile Projects > All Locked Projects option and save the SRF file to the <Siebel Server Install folder>\objects\ENU\siebel_sia.srf folder on the installed Siebel server. Copy the Web Template file CZConfigurator.swt and CZView.swt from the Web template folder into Siebel Server <Siebel Server Install folder >\WEBTEMPL. Copy the CZReturn.html file from the HTML folder into the SWE Server <SWE Server Install folder >\eappweb\PUBLIC\enu. From the EIM folder, copy the files with extension "ifb" in Siebel Server <Siebel Server Install folder >\ADMIN.
3 4 5
Use the following procedure to apply the run changes for the configuration to the database.
To apply runtime Siebel configuration changes

You must perform the following runtime configuration changes before you launch Oracle configurator.
1 2
Log into the eCommunications/HTIM application from a browser. Navigate to Site Map > Administration Business process > Repository workflow process.
a b 3 a b c d e f g
In the top applet, query for the workflows that you imported previously and activate them. In the bottom applet, query for the workflows to make sure that they are in an active state.
Navigate to Site Map > Administration Order Management > Signals. Query for the Customize signal. Lock the signal record and click on Workspace. Change the service name to SWI Configurator Load. Navigate back to the Signals view and click the Release New Version button to release a new version of the signal. Query for the QuotesAndOrdersValidate signal. Lock the signal record and click on Workspace. Replace the Siebel Verification with Oracle Batch Validate'. Change all four records with sequence #2.

Mode = Quote, Instance Type = Line Item - Change Service Name column to "Oracle Verify Item (Quote)" Mode = Order, Instance Type = Line Item - Change Service Name column to "Oracle Verify Item (Order)" Mode = Quote, Instance Type = Header - Change Service Name column to "Oracle Verify Header (Quote)" Mode = Order, Instance Type = Header - Change Service Name column to "Oracle Verify Header (Quote)"
4 5
Navigate to Administration Runtime Events > Events and click Menu > Reload Runtime Events. Navigate to Administration - Application > Views.
72
Verify the following new views:

CZRuntimeInstanceView (JS) CZRuntimeInstanceView (JS) - Agreement CZRuntimeInstanceView (JS) - Order (Sales) CZRuntimeInstanceView (JS) - Favorites
For each view, assign the appropriate responsibility so that the user with that responsibility can navigate to this view. This is part of seed data. It should be done when exporting the seed data.
Navigate to Administration - Integration > WI Symbolic URL List.
a b
In the top applet, from the drop-down menu (bold highlighted menu), select Host Administration. Add a new host entry with the following values:

Host Name: <Oracle EBIZ host name:port number> for example qapache.us.oracle.com:3710 Virtual Name: OracleConfigurator
Select Symbolic URL Administration and add a new record in the top applet.

Name: OracleCfgURL (Note: This symbolic name is very important because the serverside business component code relies on this name.) URL: http://OracleConfigurator/OA_HTML/CfgSebl.jsp Choose the host name (such as qapache.us.oracle.com:3710) Fixup Name: Default SSO Disposition: IFRAME
In the bottom applet, add arguments to the URL by creating a new record with the following values:

Name: InitMessage Req Arg: checked Argument Type: Profile Attribute Argument Value: CZInitMessage Append as argument: checked
Add another new row:

Name: PostRequest Required Arg: Checked Argument Type: Command Argument Value: PostRequest Append as argument: Not-Checked
73
Complete the following two steps to set up the SSO login into Oracle applications: NOTE: The SSO login is the preferred method for accessing Oracle applications. If you do not set up the SSO login, the Siebel end user must enter Oracle login credentials at the login page.
For the next two arguments enter the values for Argument Value as specified. UserLoginId and UserLoginPassword are function names used by Siebel SSO. These functions look up the Oracle login credentials for the Siebel application user. If the user enters other values, they will be required to log into an Oracle Applications for Configurator session. Continue to add arguments to the same URL:

Name: username Required Arg: Checked Argument Type: Command Argument Value: UserLoginId Append as argument: Checked
Add the final argument:

Name: password Required Arg: Checked Argument Type: Command Argument Value: UserLoginPassword Append as argument: Checked
Select "SSO Systems Admin List" and add a record in the top applet.

System Name: OracleConfigSSO Symbolic URL Name: OracleCfgURL Description: Logs in to the Oracle Configurator
In the bottom applet "SSO System Users" add records for the Siebel users that will be invoking Oracle Configurator. The Siebel user names will be paired with Oracle login credentials. For example:

Siebel Login Name: sadmin Login Name: operations Password: welcome
Navigate to Administration - Server Configuration > Components, select the "eCommunications Object Manager (ENU)" component, select the "Order Management - Enable Asset Based Ordering" parameter and set this value to False to call Oracle Configurator instead of calling Siebel Configurator.
74
Navigate to the "HTIM Object Manager (ENU)" component, select the "Order Management Enable Asset Based Ordering" parameter, and set this value to False to call Oracle Configurator instead of calling Siebel Configurator. The following workflows need to be activated for Configurator to work. Note that these are not workflows that were introduced as part of the Oracle Configurator integration; they already existed.

Account - New Quote Account - New Order Goto* PSP* Product Compatibility* Product Eligibility* Product Reco* *Pric* Compatibility Multiple Popup Workflow Config* Check*
Adding Siebel Custom Applications to Oracle Applications Several custom Oracle applications need to be created to allow models to be accessed from the Siebel application. These custom applications are used during the publication phase of the Oracle Configurator Model development cycle.
To add Siebel Custom Applications to Oracle Applications 1 2 3

Log in to Oracle applications with system administrator credentials, and navigate to Application > Register. If the form page does not display, navigate to the form. Create three new entries with four values:

Siebel Quote Integration |SEBLQ | DUMMY_TOP |Provides integration between Siebel Quote and Oracle Configurator Siebel Order Entry Integration | SEBLO | DUMMY_TOP | Provides integration between Siebel Order Entry and Oracle Configurator Siebel Agreement Integration | SEBLA | DUMMY_TOP | Provides integration between Siebel Agreement and Oracle Configurator
The new applications now must be added to Oracle Configurator Publication Applicability list.
Change the responsibility to Configurator Administrator.
75
Choose Application to Publication Applicability List and add the applications. This step runs a concurrent program. Once the program runs, these new applications will be available during model publication.
Refer to Oracle documentation for Configurator for information about how to develop models for calling applications.
Copy Config Web Service Setup
1 2 3 4
Log in to the eCommunications/HTIM application from a browser. Navigate to Administration Web Services > Outbound Web Services. Click Import to import ESB_ConfiguratorCopyConfigEbizAdapter_Service.XML. Click Import to import ConfiguratorUserLangSiebelAdapter.XML. NOTE: Step 1 through 4 is part of seed data. It should be done when exporting the seed data.
After importing, change the IP Address on the Service Ports (middle applet) for each of the preceding web services.
Copy Config Data Map Setup
1 2
Log in to eCommunications/HTIM application from a browser and navigate to Administration Application > Data Map Administration. For the following data maps, add three columns named 'External Configurator Reference 1','External Configurator Reference 2', and 'External Configurator Reference 3' to both the Source and the Destination Column in the Data Map Field section for the data map component specified in the parentheses:

AutoAgreement (Data Map Component:Line Item) AutoAgreeFromOrder (Data Map Component Name:Line Items) CopyOrder (Data Map Component Name:Line Item) CopyQuote (Data Map Component Name:Line Item) OrderToTemplate (Data Map Component Name:Line Item) QuoteToSalesOrder (Data Map Component Name:Line Item) QuoteToServiceOrder (Data Map Component Name:Line Item) QuoteToTemplate (Data Map Component Name:Line Item) ReviseAgreement (Data Map Component Name:Line Item) ReviseOrder (Data Map Component Name:Line Item) ReviseQuote (Data Map Component Name:Line Item) TemplateToOrder (Data Map Component Name:Line Item) TemplateToQuote (Data Map Component Name:Line Item)
76
DoCompression Parameter Setup
1 2 3
Stop the Siebel Server. Back up the eapps.cfg file, which is located in the eappweb\bin folder within your installation directory. Edit eapps.cfg using Notepad. CAUTION: Do not use Wordpad, as this will cause incorrect characters to be added to the file.
4 5
Reset the DoCompression parameter in the [defaults] section. It should now be DoCompression=FALSE. Restart the machine. NOTE: You must restart the machine. Restarting only the Siebel Server will not make your changes take effect.
Fixing the State Model for Quote Status Use the following procedure to extend the state model. To make Quote Status work, you can extend the related State Model activation date.
1 2
Navigate to Administration - Application > State Model and search for "TNT SHM Quote Status". Extend its activation date until 2020 (leave day and month as sysdate).
Required Tasks for the COMM PIP NOTE: If you are implementing the Communications Order to Cash Integration Pack for Siebel CRM, you must perform the tasks in this topic.
To activate the rule sets for Comms 1 2

Query for the Order Validation rule set. If two versions are displayed as active, select the earliest version. For example, if the active versions are 5 and 6, select version 5.
3 4
Select Deactivate Rule Set from the submenu. Navigate to Administration - Runtime Events > Events screen, and select Reload Runtime Events from the drop-down list.
NOTE: If two active versions are displayed for SWI Order Validation Rule Set, use the previous procedure.
Running EIM Data Migration for Comms This section defines the detailed steps to run the EIM jobs for Siebel applications as a part of the Creating and Updating Credit Alerts for Collection Flows functionality in AIA COM 2.5. Collections flow allows credit alerts to be created in the Siebel application based on scenarios defined in Oracle Billing and Revenue Management using Oracle Data Interchange and Siebel EIM.
77
Before you begin your import, do the following: Make sure that the Siebel Server is up and running. Make sure that the Siebel EIM component is online and running properly. To check this, navigate to the Administration - Server Configuration and Administration - Server Management screens. To avoid data loss, do not restart the Siebel server while the EIM job is running. After you have completed loading data for one country, make a backup copy of the EIM logs for status verification. (These logs are located under siebsrvr/logs.)
Use the following procedure to execute the EIM job to create and update credit alerts.
To execute the EIM job to create and update credit alerts 1 2 3

Move the ProcessAlertsAndBillingProf.ifb file from <Tools Installation directory>/REPPATCH/ ACR474/EIM to <Siebel Installation Directory>/ses/siebsrvr/ADMIN. Run the EIM job with the ProcessAlertsAndBillingProf.ifb configuration file. Verify that the EIM job is successful.
NOTE: If the Order to Cash PIP is enabled, the Asset-Based Ordering parameter for the corresponding object manager for the application must be set to False. This section describes the integration user setup process. A new flag has been introduced to identify an integration user (needed while integration testing). This user credential must be configured (on the AIA side) for the Siebel Inbound Web services call from the AIA side to avoid the boomerang effect.
Enabling Dynamic Pricing (Customer Order Management) The pricing module is available in multiple licensing modes.
Dynamic Pricing Mode This mode provides pricing capabilities such as attribute pricing, promotions, aggregate discounts, and so on. It leverages the variable maps that contain the XA child variable maps. It is available only to users who have the Dynamic Pricer license. Dynamic Pricing can also be enabled by navigating to Admin - Pricing > Price List, and selecting Enable Dynamic Pricing from the applet-level menu. This is a new implementation in Siebel version 8.1.1 applications. After you select Enable Dynamic Pricing, all the necessary changes will be performed.
Configuring the Email Notification for the Product Class and Attribute Query Feature Users to whom emails need to be sent need to be added to the user list.
78
To add/change the email addresses for the user list 1 2 3 4

Navigate to Administration - Users > Users. Add user name and user ID. Add the email address in the contact information of the child applet. Navigate to Administration - Group > User Lists and query for the SCE Users user list. NOTE: If this list does not appear, create it.
Add the users created in the user list.
The user list created in the previous procedure is passed in the run time events. Use the following procedure to add the changed user list.
To change the BO/BC/Field name to extract the email addresses 1 2

Navigate to Administration - Run Time Events > Action Set, and query for the EmailNotify action set. Query for the 'GetEmailAddr' action in the child applet The following is the business service context syntax"Parent BC Record Name";"Field Name in Child BC ";"BO Name ";"Parent BC";"Child BC" For instance: "SCE Users";"Email Address";"Account";"Account";"Contact" or "SCE Users";"EMail Addr";"User List";"User List";"User" The following run-time events use the action set described above. Action Set Name EmailNotify EmailNotify EmailNotify
Sequence 1 2 3
Object Type BusComp BusComp BusComp
Object Name Attribute VOD BusComp ISS Class VOD BusComp ISS Joint Workspace BusComp
Event PreInvokeMethod PreInvokeMethod PreInvokeMethod
Subevent SendEmail SendEmail SendEmail
Four communications templates are used to send email messages. The Attribute Defn and Product Class templates are already configured. Use the following procedure to configure or edit other templates.
79
To edit or configure email template text 1

Create a notepad file called "Attribute_Template.txt" and add the following values:

Attribute Name: [Name] Description: [Description] Type: [Type] Object Number: [Object Number] XRef Class Name: [XRef Class Name]
Create a notepad file called "Class_Template.txt" and add the following values:

Class Name: [Name] Description: [Description] Type: [Type] Object Number: [Object Number]
3 4 5 6 7 8 9
Navigate to Administration - Communication > All Templates > Template Items. Query for Workspace Attribute Defn Template and click on Template Items View. Attach the "Attribute_Template.txt" file created in Step 1 in the template item. Navigate to Administration - Communication > All Templates > Template Items. Query for "Workspace Product Class Defn Template" and click on Template Items View. Attach the "Class_Template.txt" file created in Step 2 in the template item. Make sure that "ISS Joint Workspace VOD Pick BusComp" is selected in the iteration child business component for above two template items. The communication template names are added in the user properties of the business components listed in the following table. Business Component ISS Joint Workspace BusComp ISS Joint Workspace BusComp Attribute VOD BusComp ISS Class VOD BusComp User Property PackageNameList|Attribute Definition PackageNameList|Product Class Definition PackageNameList PackageNameList Template Name Workspace Attribute Defn Template Workspace Product Class Defn Template Attribute Defn Template Product Class Template
The SMTP Server name, From Email Address, and POP server details are added in the a Communication profile. Use the following procedure to add the SMTP server name, From Email Address, and POP server details.
80
To change the SMTP Server name, From Email Address, and POP server details 1 2
Navigate to Administration - Communications > Communications Drivers and Profiles. Query for the Internet SMTP/POP3 Server communication driver, and if it does not exist, create it using the following values:

Name: Internet SMTP/IMAP Server Channel Type: Email Channel String: POP3SMTP Library Name: sscmmail Outbound: Yes
3 4
Query for Default SMTP in the child applet, and if it does not exist, create it. Change the SMTP and POP Server details in the grandchild applet, using the following values:

From Address: siebel.product.admin@demohost.siebel.com POP3 Account Name: support POP3 Account Password: support POP3 Server: demohost.siebel.com SMTP Server: rgmamersmtp.oraclecorp.com
The communication profile is added the in the user properties of the business components listed in the following table: Business Component ISS Joint Workspace BusComp Attribute VOD BusComp ISS Class VOD BusComp User Property CommProfileOverride CommProfileOverride CommProfileOverride Template Name Default SMTP Profile Default SMTP Profile Default SMTP Profile
To set up the Time-Based Offering feature 1

Create Product Master Data.
Create three attributes:

Duration (Number/Enumerated, values 1, 2,3, 31) DurationUnitOfMeasure (Text/Enumerated values: Days, Months, Years) DurationValidityStart (Text/Enumerated Values: Original Start, Now, Original End)
Create a class with the preceding three attributes.
NOTE: The class attribute names and the attribute definition names must be identical.
81
For the TBO Discount products synced from BRM, change the structure type to Customizable, change the product type to Time Based Offer, and associate the preceding TBO class to this product.
Create Job to Inactive Assets.
Navigate to Server Management > Jobs, and create a new job.

Select Component as Workflow Process Batch Manager. Select Repeating as Y. Select Requested Server as the Siebel Server. Select Repeat Unit as Days. Select Repeat Interval as 1. Select Repeat From as Scheduled Start.
b c d 3 a b c d 4
Navigate to Job Parameters and create a new parameter. Select Workflow Process Name as the name and specify SWI Asset Status Update as the value. Select Search Specification as the name and specify the value if necessary.
Create Revision Data Maps. Navigate to Administration Application, and then Data Map Administration. In Data Map Object, query for Name = Revise Order or ReviseQuote. In Data Map Component, query for Name = Line Item. In Data Map Field, add the fields that needs to be copied during revision (such as Service End / Service Start Date/Due Date).
Configure the business service. The business service name must be specified as the value for the Business Service Query Access List server component parameter. For example, if the server component is eCommunications Object Manager (ENU), navigate to its parameters, query for Name = Business Service Query Access List, add Value = CMU External Integration Service, and restart the server component so that the change to the component parameter value takes effect.
Release the data maps:
a b
Navigate to Site Map > Administration- Order Management > Variable Maps. In Variable Map, query for the following:

Default Pricing Eligibility Variable Map - Row Set Default Pricing Variable Map - Row Set Default Pricing Variable Map XA
Lock the preceding variable maps and release a new version.
82
Tasks Required for the MDM PIP The following tasks are required if you are using the MDM PIP.
To activate the workflow policies 1 2

Navigate to Administration - Business Process Screen, and then Workflow Policies view. Query for the following workflow policies and remove the expiration date:

SWI Account Address Sync Policy SWI Account Contact Sync Policy SWI Account Sync Policy SWI Address Sync Policy SWI Contact Address Sync Policy SWI Contact Sync Policy
3 4
Remove the existing triggers, and then generate the triggers. Restart Siebel Services. NOTE: By default, the Workspace Release Flag user preference is set to N. If you want to release products into the Siebel application automatically, you must change this preference.
To customize the Workspace Release flag 1 2

Navigate to Site Map > Administration - Application > System Preferences. Query for 'Workspace Release Flag', set the value to N, and restart the server.

Although running Siebel Incremental Repository Merge implements any and all enhancements that have been provided since version 8.1.1, in some cases, you must perform postinstallation configurations. Use the following procedure to activate the ISS Promotion Group Create Order task.
To activate the ISS Promotion Group Create Order task 1 2

From the Site Map, navigate to Administration - Business Processes > Task Deployment, and query for the ISS Promotion Group Create Order task. Select the task and then click Activate.
83
Siebel Maintenance Release Guide, Version 8.1.1.10, Rev. B Siebel Fix Pack Installation Instructions

Although running Siebel Incremental Repository Merge implements any and all enhancements that have been provided since version 8.1.1, in some cases, you must perform postinstallation configurations. To enable the enhancements included in ACR 756, from within the application, navigate to Administration - Application and set the Enable AIA Utility system preference to True.
Instructions for Siebel Reports Enhancements

For information about how to implement the Siebel Reports enhancements in version 8.1.1.10, see 1501378.1 (Article ID) on My Oracle Support.
Siebel Fix Pack Installation Instructions

This topic includes the following information: Siebel Fix Pack Installation Overview on page 84 Installing the Siebel Fix Pack on Microsoft Windows on page 91 Installing the Siebel Fix Pack on UNIX on page 96 Postinstallation Tasks for the Siebel Server on page 100 Postinstallation Tasks for the Siebel Web Server Extension on page 101 Postinstallation Tasks for High Interactivity Clients on page 102 Postinstallation Tasks for Supporting Additional Languages on page 103 Uninstalling Siebel Fix Packs on page 104
Siebel Fix Pack Installation Overview

This topic is part of Siebel Fix Pack Installation Instructions on page 84. In order to receive the full benefit of all of the 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 Siebel Fix Pack for all of the applicable products in your existing deployment. NOTE: This Siebel Maintenance Release Guide includes information for the applicable Siebel Fix Pack 8.1.1.x release. Each Fix Pack is cumulative and includes all of the fixes included in previous Siebel Fix Pack 8.1.1.x releases. You can install the latest Siebel Fix Pack 8.1.1.x release onto Siebel CRM version 8.1.1 or any prior version 8.1.1.x release. Siebel Fix Packs 8.1.1.8 and later support some new installation and uninstallation capabilities. In particular, you can use the Fix Pack installer to perform new installations of Siebel Enterprise Server and Siebel Web Server Extension from a Siebel installation image that you have prepared for this purpose.
84
Before installing this Fix Pack, it is strongly recommended that you read all of the information in the topics in this section, Siebel Fix Pack Installation Instructions on page 84, and in other applicable sections of this guide. See also any relevant articles on My Oracle Support, such as 1484433.1 (Article ID), about installation troubleshooting for Siebel Fix Pack 8.1.1.8 and later. This guide describes Fix Pack installation and related tasks for several key products, but not for all of the Siebel Business Applications products that might apply to your deployment. Fix Pack installation tasks for products not covered here are generally similar to those described here. NOTE: After you install the Siebel Fix Pack 8.1.1.x release, you must perform additional configuration tasks in order to implement any enhancements and updates that you plan to use. For more information, see Enhancements and Updates in Siebel Fix Pack 8.1.1.10 on page 19 and Configuration Instructions for Enhancements and Updates on page 41. It is strongly recommended that you review the configuration instructions before installing. The instructions for some of the enhancements and updates might also include steps to be performed before you install the Siebel Fix Pack. For more information about the available patch releases for Siebel CRM, see 975515.1 (Article ID) on My Oracle Support. For more information about finding and downloading patch releases for Siebel CRM, see 975535.1 (Article ID) on My Oracle Support. This topic includes the following information: Installation Scenarios Described in This Guide on page 85 Applicable Base Releases on page 87 About Running Siebel Image Creator on page 87 About Installing Siebel Fix Packs on page 88 About Installing Languages on page 90 About Installing Siebel Quick Fix Releases on page 91
Installation Scenarios Described in This Guide

This topic is part of Siebel Fix Pack Installation Overview on page 84. The installation instructions in this guide are relevant to the following scenarios: Performing a new installation of Siebel CRM version 8.1.1 with Siebel Fix Pack 8.1.1.10. If you are installing Siebel CRM version 8.1.1 with version 8.1.1.10 (a new full installation), then follow the installation instructions in the Siebel Installation Guide for the operating system you are using. This installation option, which starts from the Siebel Fix Pack installer, was introduced in Siebel Fix Pack 8.1.1.8. When you run the Siebel Fix Pack 8.1.1.10 installer for Siebel Enterprise Server and Siebel Web Server Extension (SWSE), you can choose whether to perform a new installation of version 8.1.1.10, incorporating version 8.1.1, or to install version 8.1.1.10 as a patch onto an existing installation of version 8.1.1.x. The installers use the Oracle Universal Installer (OUI) framework.
85
The ability to perform a new installation depends on your having used the Siebel Image Creator utility to correctly set up the Siebel installation image for Siebel Enterprise Server and SWSE for version 8.1.1.10 to include the correct version 8.1.1 media. For a new installation, use the latest applicable version of the Siebel Installation Guide for the operating system you are using (such as version 8.1, Rev. D). This book is available on the version 8.1 Siebel Bookshelf (http://download.oracle.com/docs/cd/E14004_01/homepage.htm). You install Siebel modules other than Siebel Enterprise Server and SWSE in the traditional way. To install version 8.1.1, use the latest applicable version of the Siebel Installation Guide for the operating system you are using. After installing, follow the instructions in this Siebel Maintenance Release Guide for installing Siebel Fix Pack 8.1.1.x onto version 8.1.1. For more information about creating the Siebel installation image, including which version of Siebel Image Creator to use for each installation case, see About Running Siebel Image Creator on page 87. For more information about installing Siebel Fix Pack 8.1.1.x, see About Installing Siebel Fix Packs on page 88. Installing Siebel Fix Pack 8.1.1.10 (patching an existing Siebel CRM version 8.1.1 installation or a prior version 8.1.1.x installation). If you have already installed Siebel CRM version 8.1.1 as a new installation, and are now installing Siebel Fix Pack 8.1.1.10 onto version 8.1.1 or onto a previous version 8.1.1.x release (through version 8.1.1.9), then follow the instructions in this Siebel Maintenance Release Guide for doing this. Optionally, you can 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 104. When you installed Siebel CRM version 8.1.1 or 8.1.1.x as a new installation, you would have already referred to the Siebel Installation Guide for the operating system you are using. If you are installing the Siebel Fix Pack onto an existing installation of version 8.1.1 though version 8.1.1.7, then you would have used a guide like version 8.1, Rev. A, which can be found on My Oracle Support at Article ID 1461732.1. If you are installing the Siebel Fix Pack onto an existing installation of version 8.1.1.8 or later, then you would have used the same guide or version 8.1, Rev. B or later, depending on whether version 8.1.1.8 or later was installed as a patch installation or as a new installation. The latest version of the Siebel Installation Guide for the operating system you are using (such as version 8.1, Rev. D) is available on the version 8.1 Siebel Bookshelf (http://download.oracle.com/docs/cd/E14004_01/homepage.htm). After you install Siebel Fix Pack 8.1.1.10, use the latest version of the Siebel Installation Guide for the operating system you are using. Refer to this guide, for example, for information about running the updated Configuration Wizards that are provided in version 8.1.1.8 or later. This book is available on the version 8.1 Siebel Bookshelf (http://download.oracle.com/docs/cd/E14004_01/ homepage.htm). For more information about creating the Siebel installation image, see About Running Siebel Image Creator on page 87. For more information about installing Siebel Fix Pack 8.1.1.x, see About Installing Siebel Fix Packs on page 88. Adding languages. When you perform a new installation of Siebel CRM version 8.1.1.10, include any supported languages (language packs) that you require or expect to require. Restrictions apply to adding languages to an existing installation. For more information about adding languages and related tasks, see About Installing Languages on page 90.
86
Applicable Base Releases

This topic is part of Siebel Fix Pack Installation Overview on page 84. In general, each Siebel Fix Pack can be installed onto an existing Siebel CRM installation that is at a valid base version level for this Fix Pack. Installing any Siebel 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 Siebel CRM version 8.1.1 software and optionally including any installed Siebel Fix Pack 8.1.1.x of a lower version or other installed patch releases, where applicable. Valid base releases are Siebel Industry Applications, version 8.1.1 or version 8.1.1.x. NOTE: In order to run Siebel Business Applications software, all of the 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 84. You use the Siebel Image Creator utility to create a Siebel installation image (sometimes called a network image) for any Siebel Fix Pack 8.1.1.x release. The installation 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 in the installation image. Installing any Siebel Business Applications release, including a patch installation of version 8.1.1.10 or a new installation of version 8.1.1.10 with version 8.1.1, must be done from an installation image created using Siebel Image Creator. For patch installations, you obtain the Siebel Fix Pack 8.1.1.10 media from My Oracle Support. You obtain the version 8.1.1.10 media files and the version 8.1.1 OUI media files (for Siebel Enterprise Server and Siebel Web Server Extension) from Oracle Software Delivery Cloud. For more information, see 1461640.1 (Article ID) on My Oracle Support. Siebel Image Creator has changed for use with the Siebel Enterprise Server and SWSE installers, which use Oracle Universal Installer. Create a full image for Siebel Enterprise Server and SWSE. For patch installations, you can also create a patch-only image for these modules. You can perform patch installations for these modules by running the version 8.1.1.10 installers from either a full image or a patch-only image. For more information about using the version of Siebel Image Creator provided with version 8.1.1.10 and about performing new installations, see the latest version of the Siebel Installation Guide for the operating system you are using. This book is available on the version 8.1 Siebel Bookshelf. For information about using the version of Siebel Image Creator provided with version 8.1.1, see version 8.1, Rev. A of Siebel Installation Guide for the operating system you are using, which can be found on My Oracle Support, at Article ID 1461732. NOTE: The Image Creator executable file is called snic.bat for Windows or snic.sh for UNIX and Linux. Always use the version of Siebel Image Creator that is provided with the Siebel Business Applications release for which you are creating the installation image.
87
Table 4 identifies which version of Siebel Image Creator to use, and which JAR files you need, for creating the Siebel installation image for each installation case for version 8.1.1.10, for patch installation or new installation. Also include the JAR files for associated language packs, as needed.
Table 4. Applicable Versions for Siebel Image Creator and JAR Files Installation Case For all of the Siebel Business Applications modules, create a patch-only image of version 8.1.1.10. Perform a patch installation of version 8.1.1.10 onto an existing installation of version 8.1.1 or 8.1.1.x. For Siebel Enterprise Server and SWSE, create a full image of version 8.1.1.10. Perform either a new installation of version 8.1.1.10 or a patch installation onto an existing installation of version 8.1.1 or 8.1.1.x. For Siebel Mobile Web Client, Siebel Tools, and Siebel Management Server, create an installation image of version 8.1.1. Perform a new installation of version 8.1.1. (Then perform a patch installation of version 8.1.1.10 onto version 8.1.1.) For Siebel Enterprise Server and SWSE, create an installation image of version 8.1.1. Perform a new installation of version 8.1.1. (Then perform a patch installation of version 8.1.1.10 onto version 8.1.1.) NOTE: For new installations of Siebel Enterprise Server and SWSE, it is strongly recommended that you use the version 8.1.1.10 installers. Version 8.1.1. Version 8.1.1.0 (InstallShield installers). Version 8.1.1. Version 8.1.1.10. Version 8.1.1.10 and version 8.1.1.0 (Oracle Universal Installer installers). Siebel Image Creator Version Version 8.1.1.10. JAR Files Needed All version 8.1.1.10.
Version 8.1.1.0.
About Installing Siebel Fix Packs

This topic is part of Siebel Fix Pack Installation Overview on page 84. For each Siebel Business Applications product module, installing the latest Siebel Fix Pack 8.1.1.x release onto an existing base installation replaces existing executable files and provides new files in addition to the base installation. For supported base releases, see Applicable Base Releases on page 87.
88
NOTE: Installing a Siebel Fix Pack for Siebel Enterprise Server or Siebel Web Server Extension might replace (overwrite) customer-modified files. You can review which files were overwritten and restore an overwritten file if necessary. For more information, see Postinstallation Tasks for the Siebel Server on page 100 and Postinstallation Tasks for the Siebel Web Server Extension on page 101. If you plan to install any additional Siebel language packs, then review About Installing Languages on page 90 before you install any Siebel Fix Pack. Installing a Siebel Fix Pack might also patch any installed languages, depending on the content of the Fix Pack. When you run the Siebel Fix Pack 8.1.1.10 installer for Siebel Enterprise Server and Siebel Web Server Extension, you can choose to perform a new installation or to patch an existing installation of version 8.1.1.x. If you choose to perform a new installation, then the installer installs version 8.1.1.10, incorporating version 8.1.1. If you choose to patch an existing installation of version 8.1.1.x, then the installer displays a list of any existing valid version 8.1.1.x installations that it has detected. You can select a listed installation and install the Siebel Fix Pack onto it. The ability to perform a new installation depends on how the Siebel installation image was created. 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 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. For example, Siebel Fix Pack 8.1.1.8 and later introduce significant new installation scenarios. The Siebel Fix Pack must be installed from an installation image that 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. You must use the correct version of Image Creator based on what you are installing. For more information, see About Running Siebel Image Creator on page 87. 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. This guide is available on the version 8.1 Siebel Bookshelf. See also Postinstallation Tasks for the Siebel Web Server Extension on page 101. After you install version 8.1.1 and version 8.1.1.x, you can also install any applicable Quick Fix release onto version 8.1.1.x. For more information, see About Installing Siebel Quick Fix Releases on page 91.
Related Topics Installing the Siebel Fix Pack on Microsoft Windows on page 91 Installing the Siebel Fix Pack on UNIX on page 96 Uninstalling Siebel Fix Packs on page 104
89
About Installing Languages

This topic is part of Siebel Fix Pack Installation Overview on page 84. Include or add all of the languages that you will require in your Siebel CRM version 8.1.1 or version 8.1.1.10 installation image (network image), which you create by using the Siebel Image Creator utility. Include the same set of languages for all of the installation images for version 8.1.1 and version 8.1.1.x. Then install the software with the languages that you require. When you configure each installed Siebel Server and Siebel Web Server Extension (SWSE), you also specify which installed languages you are deploying. You can add languages to an existing installation of version 8.1.1. However, where a version 8.1.1.x Fix Pack has been installed, restrictions on adding languages apply in some cases. After adding the languages, install the current Fix Pack. Where restrictions prevent you from adding languages to an existing installation, it is always an option to perform a new installation that will include the languages that you require. If you are not adding languages, then you only need to install the latest Siebel Fix Pack 8.1.1.x release, as described in this guide. Restrictions apply to adding languages to an existing installation, as follows: Restrictions for Siebel Enterprise Server and SWSE. You cannot add languages to an existing installation of Siebel Enterprise Server or SWSE for version 8.1.1.8 or later. You can add languages to an existing installation of version 8.1.1.7 or lower by using the version 8.1.1 installer. You must do this before you install Siebel Fix Pack 8.1.1.8 or later. Uninstalling all of the Fix Packs first is recommended, although it is possible to add languages after a Fix Pack (through version 8.1.1.7) has been installed. Alternatively, if you installed version 8.1.1.8 or later as a patch installation, then you can uninstall it and revert to version 8.1.1 or version 8.1.1.x (through version 8.1.1.7 only), and then add languages. After adding languages, install the current Fix Pack (version 8.1.1.10). Typically, you would reinstall a previously installed Fix Pack before you install the current Fix Pack. Restrictions for Siebel Mobile Web Clients and Siebel Tools Clients. For Siebel Mobile Web Clients and Siebel Tools Clients, you cannot add languages to an existing installation where any version 8.1.1.x Fix Pack has been installed. You cannot uninstall any Fix Pack through version 8.1.1.7, and so you cannot add languages in this case. However, if you have installed version 8.1.1.8 or later onto version 8.1.1, then you can uninstall the Fix Pack and revert to version 8.1.1. Then you can add languages. After adding languages, install the current Fix Pack (version 8.1.1.10). Typically, you would reinstall a previously installed Fix Pack before you install the current Fix Pack. Some postinstallation tasks are required in order to deploy a language that you added after the initial product installation and configuration: If you add a language after you have configured an installed Siebel Server, then start the Siebel Server Configuration Wizard and run the configuration task Add Language Support for the Siebel Server. (It is not necessary to reconfigure the Siebel Server.) If you add a language after you have configured an installed SWSE, then start the SWSE Configuration Wizard and run the configuration task Add Language Support for the SWSE Configuration. (It is not necessary to reconfigure the SWSE.)
90
After you add 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 strongly recommended that you perform databaserelated tasks after installing applicable Fix Packs or other patch releases.
Related Topics About Running Siebel Image Creator on page 87 Postinstallation Tasks for Supporting Additional Languages on page 103 Uninstalling Siebel Fix Packs on page 104
Related Books Siebel Installation Guide for the operating system you are using Siebel Global Deployment Guide Configuring Siebel Business Applications My Oracle Support Certifications
About Installing Siebel Quick Fix Releases

This topic is part of Siebel Fix Pack Installation Overview on page 84. After installing a Siebel Fix Pack 8.1.1.x release as described in this guide, you can also install any applicable Siebel Quick Fix release onto version 8.1.1.x. When you install a Quick Fix, the installed languages might also be patched, depending on the content of the Quick Fix release. NOTE: Installing a Quick Fix might 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. The following related topic lists the Quick Fix releases that are included in the current Siebel Fix Pack 8.1.1.x release.
Related Topics Quick Fixes Included in Siebel Fix Pack 8.1.1.10 on page 10
Installing the Siebel Fix Pack on Microsoft Windows

This topic is part of Siebel Fix Pack Installation Instructions on page 84. Procedures for installing Siebel Fix Pack 8.1.1.x for products on Microsoft Windows are described in this topic. Follow these instructions to install the Fix Pack for each product over the existing base installation for the same product. Perform the steps that apply for the Fix Pack that you are installing, in the general sequence presented here.
91
Before you install the Fix Pack, review all of the applicable information in Siebel Fix Pack Installation Overview on page 84. The instructions generally assume that Fix Pack installers are started in GUI mode. Alternatively, you can start the installers for server-based products in unattended mode. In unattended mode, the Fix Pack installation runs silently. NOTE: If you installed Siebel CRM version 8.1.1 software using the Siebel FastTrack Wizard, then 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 was provided with the original version 8.1.1 media. It is no longer provided with the updated version 8.1.1 media, which uses Oracle Universal Installer and is required for new installations of version 8.1.1.8 or later. This topic has the following information: Installing the Fix Pack for Siebel Enterprise Server on Windows on page 92 Installing the Fix Pack for Siebel Web Server Extension on Windows on page 93 Installing the Fix Pack for Siebel Management Server on Windows on page 94 Installing the Fix Pack for Siebel Mobile Web Client or Siebel Tools on Windows on page 95
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 91. 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 Siebel Fix Pack installer for Siebel Enterprise Server also patches any instance of Siebel Management Agent that was automatically installed with a Siebel Server that you are patching. NOTE: This procedure is for installing the Siebel Fix Pack release (maintenance release) onto an existing installation of Siebel CRM version 8.1.1 or 8.1.1.x (through version 8.1.1.9). The installer might also allow you to perform a new installation, depending on how you created your Siebel installation image for Siebel Enterprise Server. For information about creating the Siebel installation image and about performing a new installation of version 8.1.1 with version 8.1.1.10, see the Siebel Installation Guide for the operating system you are using.
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 Gateway Name Server or Siebel 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, then also stop the service for the Management Agent.
92
In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, and then to the directory where the installer is located. For Siebel Enterprise Server, navigate to Siebel_Image\Windows\Server\Siebel_Enterprise_Server\Disk1\install. In this path, Siebel_Image is the directory for your version-specific Siebel installation image, such as C:\Siebel_Install_Image\8.1.1.x.
4 5 6 7 8 9
Double-click setup.bat to start the Siebel Enterprise Server installer for version 8.1.1.10. In the welcome screen, click Next. Confirm the instance of version 8.1.1 or 8.1.1.x to patch, and then click Next. In the Installation Details and Progress screen, click Install to complete the installation of version 8.1.1.10. When the installer indicates that the software was successfully installed, click Exit. Repeat these steps on each computer with a Siebel Enterprise Server component installation to be patched. Fix Pack or other patch release installation for server-based products.
10 Restart all of the applicable Siebel Business Applications product components at the end of all 11 Perform any postinstallation tasks.
For more information, see Postinstallation Tasks for the Siebel Server on page 100.
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 91. Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any computer where Siebel Web Server Extension (SWSE) is installed. Before you install any Fix Pack release for SWSE, see My Oracle Support Certifications and verify that the Web server version is correct for the Siebel Business Applications release. If you need to update the Web server, then do so before you install the Fix Pack for SWSE. NOTE: This procedure is for installing the Siebel Fix Pack release (maintenance release) onto an existing installation of Siebel CRM version 8.1.1 or 8.1.1.x (through version 8.1.1.9). The installer might also allow you to perform a new installation, depending on how you created the Siebel installation image for Siebel Web Server Extension. For information about creating the Siebel installation image and about performing a new installation of version 8.1.1 with version 8.1.1.10, see the Siebel Installation Guide for the operating system you are using.
To install the Fix Pack for Siebel Web Server Extension 1

Stop the Microsoft IIS services:

Stop the IIS Administration service. Stop the World Wide Web Publishing service.
93
In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, and then to the directory where the installer is located. For SWSE, navigate to Siebel_Image\Windows\Server\Siebel_Web_Server_Extension\Disk1\install. In this path, Siebel_Image is the directory for your version-specific Siebel installation image, such as C:\Siebel_Install_Image\8.1.1.x.
3 4 5 6 7 8 9
Double-click setup.bat to start the SWSE installer for version 8.1.1.10. In the welcome screen, click Next. Confirm the instance of version 8.1.1 or 8.1.1.x to patch, and then click Next. In the Installation Details and Progress screen, click Install to complete the installation of version 8.1.1.10. When the installer indicates that the software was successfully installed, click Exit. Repeat these steps on each computer with an SWSE installation to be patched. Restart the Microsoft IIS services:

Start the World Wide Web Publishing service. Start the IIS Administration service.
10 Perform any other postinstallation tasks.

For more information, see Postinstallation Tasks for the Siebel Web Server Extension on page 101.
Installing the Fix Pack for Siebel Management Server on Windows

This topic is part of Installing the Siebel Fix Pack on Microsoft Windows on page 91. Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any computer where Siebel Management Server is installed. After you install the Fix Pack for all instances of Siebel Server (which includes Siebel Management Agent), shut down the Siebel Management Server, and 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 are not operational until Management Server has also been patched. NOTE: This procedure is for installing the Siebel Fix Pack release (maintenance release) onto an existing installation of Siebel CRM version 8.1.1 or 8.1.1.x. For information about creating the Siebel installation image and about performing a new installation of version 8.1.1, see the Siebel Installation Guide for the operating system you are using.
To install the Fix Pack for Siebel Management Server 1

Stop the Siebel Management Server service.
94
In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, and then to the directory where the installer is located. For Siebel Management Server, navigate to Siebel_Image\Windows\Server\Siebel_Management_Server. In this path, Siebel_Image is the directory for your version-specific Siebel installation image, such as C:\Siebel_Install_Image\8.1.1.x.
3 4 5 6 7 8
Double-click setup.exe to start the Siebel Management Server installer for version 8.1.1.x. In the welcome screen, click Next. Select an instance of version 8.1.1 or 8.1.1.x to patch, from the list of detected Siebel installations, and then click Next. Follow all of the prompts to complete the installation of version 8.1.1.x. Restart the Siebel 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 or Siebel Tools on Windows
This topic is part of Installing the Siebel Fix Pack on Microsoft Windows on page 91. Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any computer where Siebel Mobile Web Client or Siebel Tools is installed. (Most of the information for Siebel Mobile Web Client also applies to Siebel Developer Web Client.) No patch installers are provided for the Siebel Sample Database for Siebel Fix Pack releases. However, for Siebel Fix Pack 8.1.1.10, you can download an updated Siebel Sample Database installer. For more information, see Updated Siebel Sample Database on page 21. NOTE: This procedure is for installing the Siebel Fix Pack release (maintenance release) onto an existing installation of Siebel CRM version 8.1.1 or 8.1.1.x. For information about creating the Siebel installation image and about performing a new installation of version 8.1.1, 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, and 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, and 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.
95
In these paths, Siebel_Image is the directory for your version-specific Siebel installation image, such as C:\Siebel_Install_Image\8.1.1.x.
3 4 5 6 7
Double-click setup.bat to start the Siebel client or Siebel Tools installer for version 8.1.1.x. In the Select Oracle Home and Oracle Location screen, select an instance of version 8.1.1 or 8.1.1.x to patch, from the list of detected Siebel installations, and then click Next. In the Installation Details and Progress screen, click Install to complete the installation of version 8.1.1.x. When the installer indicates that the software was successfully installed, click Exit. Repeat these steps on each computer with an applicable Siebel client or Siebel Tools installation to be patched. NOTE: The computer might require a restart at the end of the installation.
Perform any postinstallation tasks. For more information, see Postinstallation Tasks for High Interactivity Clients on page 102.
Installing the Siebel Fix Pack on UNIX

This topic is part of Siebel Fix Pack Installation Instructions on page 84. Procedures for installing Siebel Fix Pack 8.1.1.x for products on supported UNIX and Linux platforms are described in this topic. Follow these instructions to install the Fix Pack for each product over the existing base installation for the same product. Perform the steps that apply for the Fix Pack that you are installing, in the general sequence presented here. Before you install the Fix Pack, review all of the applicable information in Siebel Fix Pack Installation Overview on page 84. The instructions generally assume that Fix Pack installers are started in GUI mode. Alternatively, the installers for server-based products can be started in unattended mode. In 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, and Siebel Tools. For more information, see Installing the Siebel Fix Pack on Microsoft Windows on page 91. This topic has the following information: Installing the Fix Pack for Siebel Enterprise Server on UNIX on page 96 Installing the Fix Pack for Siebel Web Server Extension on UNIX on page 98
Installing the Fix Pack for Siebel Enterprise Server on UNIX

This topic is part of Installing the Siebel Fix Pack on UNIX on page 96. 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).
96
The Fix Pack installer for Siebel Enterprise Server also patches any instance of Siebel Management Agent that was automatically installed with a Siebel Server that you are patching. NOTE: Java Runtime Environment (JRE) must be installed on any computer running AIX where you will run the installer for Siebel Enterprise Server. Before you run the installer, set the ORACLE_HOME environment variable. When you run the installer, specify where JRE is installed by using the command-line option -jreLoc. For supported version information for JRE, see My Oracle Support Certifications. NOTE: This procedure is for installing the Siebel Fix Pack release (maintenance release) onto an existing installation of Siebel CRM version 8.1.1 or 8.1.1.x (through version 8.1.1.9). The installer might also allow you to perform a new installation, depending on how you created your Siebel installation image for Siebel Enterprise Server. For information about creating the Siebel installation image and about performing a new installation of version 8.1.1 with version 8.1.1.10, see the Siebel Installation Guide for the operating system you are using.
To install the Fix Pack for Siebel Enterprise Server components 1

Shut down the Siebel Business Applications product component to be updated. Stop all of the 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, then 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 the 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, and then to the directory where the installer is located. For Siebel Enterprise Server, navigate to Siebel_Image/ UNIX_OS/Server/Siebel_Enterprise_Server/Disk1/install, 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.
97
Enter a command like the following to start the Siebel Enterprise Server installer for version 8.1.1.10: ./runInstaller -oneclick -jreLoc JRE_directory -invPtrLoc inventory_location where:

jre_location is the full path of the installed Java Runtime Environment (JRE) software. On AIX, you must use the -jreLoc option. It is not required on other operating systems. inventory_location is the full path of the oraInst.loc file (for example, /export/home/
oraInst.loc), which points to the OUI inventory location. Use the -invPtrLoc option if you want to specify an inventory pointer file other than the default.
In the Installation Details and Progress screen, click Install to complete the installation of version 8.1.1.10.
10 When the installer indicates that the software was successfully installed, click Exit. 11 Repeat these steps on each computer with a Siebel Enterprise Server component installation to
be patched.
12 Restart all of the applicable Siebel Business Applications product components at the end of all
Fix Pack or other patch release installation for server-based products.
13 Perform any postinstallation tasks.

For more information, see Postinstallation Tasks for the Siebel Server on page 100.
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 96. Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any computer where Siebel Web Server Extension (SWSE) is installed. Before you install any Fix Pack for SWSE, see My Oracle Support Certifications and verify that the Web server version is correct for the Siebel Business Applications release. If you need to update the Web server, then do so before you install the Fix Pack for SWSE. NOTE: Java Runtime Environment (JRE) must be installed on any computer running AIX where you will run the installer for SWSE. Before you run the installer, set the ORACLE_HOME environment variable. When you run the installer, specify where JRE is installed by using the command-line option -jreLoc. For supported version information for JRE, see My Oracle Support Certifications. NOTE: This procedure is for installing the Siebel Fix Pack release (maintenance release) onto an existing installation of Siebel CRM version 8.1.1 or 8.1.1.x (through version 8.1.1.9). The installer might also allow you to perform a new installation, depending on how you created your Siebel installation image for Siebel Web Server Extension. For information about creating the Siebel installation image and about performing a new installation of version 8.1.1 with version 8.1.1.10, see the Siebel Installation Guide for the operating system you are using.
98
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 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 the installation has permission to run slibclean by asking the administrator to change the permission as follows: chmod 6555 /usr/sbin/slibclean
(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, and then to the directory where the installer is located. For SWSE, navigate to Siebel_Image/UNIX_OS/Server/ Siebel_Web_Server_Extension/Disk1/install, 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.
Enter a command like the following to start the SWSE installer for version 8.1.1.10: ./runInstaller -oneclick -jreLoc JRE_directory -invPtrLoc inventory_location where:

jre_location is the full path of the installed Java Runtime Environment (JRE) software. On AIX, you must use the -jreLoc option. It is not required on other operating systems. inventory_location is the full path of the oraInst.loc file (for example, /export/home/
7 8 9
In the welcome screen, click Next. Confirm the instance of version 8.1.1 or 8.1.1.x to patch, and then click Next. In the Installation Details and Progress screen, click Install to complete the installation of version 8.1.1.10.
10 When the installer indicates that the software was successfully installed, click Exit. 11 Repeat these steps on each computer with an SWSE installation to be patched. 12 Perform any postinstallation tasks. For example, restart the Web server at the end of all Fix Pack
or other patch release installation for server-based products. For more information, see Postinstallation Tasks for the Siebel Web Server Extension on page 101.
99
Postinstallation Tasks for the Siebel Server

This topic is part of Siebel Fix Pack Installation Instructions on page 84. This topic describes several postinstallation tasks that might be necessary for the Siebel Server. NOTE: Many other sections of this guide describe additional tasks that you might need to perform after installing the Siebel Fix Pack. In particular, see the release notes, configuration instructions, and bug fix sections. See also the Siebel Installation Guide for the operating system you are using.
Verifying the Version Number

After you install the Siebel Fix Pack 8.1.1.x release, verify the version number of the installed software. You do this by using the opatch lsinventory command. Using this command is described in the Siebel Installation Guide for the operating system you are using, in the chapter about verifying your installation. Verifying the version number is also recommended after you uninstall the Siebel Fix Pack, where the new version number is 8.1.1.8 or later.
Reviewing Whether Customized Files Were Overwritten

Installing a Fix Pack for Siebel Enterprise Server might replace (overwrite) customer-modified files (for example, application configuration files like siebel.cfg) that govern program execution. However, the existing files are backed up into a directory called fp_backup (which is used for Fix Pack uninstallation rollback) and you can restore an overwritten file if necessary. After you install Siebel Fix Pack 8.1.1.10, the installer runs a script to identify conflicts between your overwritten customized files (which were moved into fp_backup) and the files that were patched by the Fix Pack installer. These conflicts are identified in the file overwrittenfiles_timestamp.log, which is created in the ORACLE_HOME/cfgtoollogs/oui directory.
Using Incremental Repository Merge

For Siebel Fix Pack 8.1.1.10 and later, when it is installed as a patch release into an existing installation with an existing database, you must use the Incremental Repository Merge feature to implement new features. For Siebel Fix Pack 8.1.1.10 and later (when it is installed as a new installation with a new database), the Siebel Database Configuration Wizard task to install a new Siebel database installs the new database content to support the enhancements that were added after version 8.1.1. In this case, do not use the Incremental Repository Merge feature. For information about installing the Siebel database, see the Siebel Installation Guide for the operating system you are using. For information about setting up and using Incremental Repository Merge, see Siebel Database Upgrade Guide.
Related Topics Siebel Incremental Repository Merge on page 20
100
Obtaining an Updated Siebel Repository File

Updated Siebel Repository Files (SRF files) are available for download from Oracle Software Delivery Cloud. These updated SRF files are available for all of the supported Siebel languages. The SRF files correspond to Siebel Repository updates for version 8.1.1.10. Use the updated SRF files in order to run the Siebel Business Applications after you install Siebel Fix Pack 8.1.1.10 and update the Siebel database, such as by using the Incremental Repository Merge feature. For more information, see Updated Siebel Repository Files on page 21.
Updating the CRC Parameter

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 might 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 that you installed later included an updated security adapter library file, then checksum validation fails and Siebel Web Clients might not start, unless the value of the CRC parameter is updated. For more information about this task, see the topic about configuring checksum validation in Siebel Security Guide.
Postinstallation Tasks for the Siebel Web Server Extension

This topic is part of Siebel Fix Pack Installation Instructions on page 84. This topic describes postinstallation tasks that might be necessary for the Siebel Web Server Extension. NOTE: Many other sections of this guide describe additional tasks that you might need to perform after installing the Siebel Fix Pack. In particular, see the release notes, configuration instructions, and bug fix sections. See also the Siebel Installation Guide for the operating system you are using.
Verifying the Version Number

After you install the Siebel Fix Pack 8.1.1.x release, verify the version number of the installed software. You do this by using the opatch lsinventory command. Using this command is described in the Siebel Installation Guide for the operating system you are using, in the chapter about verifying your installation. Verifying the version number is also recommended after you uninstall the Siebel Fix Pack, where the new version number is 8.1.1.8 or later.
Review Whether Customized Files Were Overwritten

Installing a Fix Pack for Siebel Web Server Extension might replace (overwrite) customer-modified files that govern program execution. However, the existing files are backed up into a directory called fp_backup (which is used for Fix Pack uninstallation rollback) and you can restore an overwritten file if necessary.
10 1
After you install Siebel Fix Pack 8.1.1.10, the installer runs a script to identify conflicts between your overwritten customized files (which were moved into fp_backup) and the files that were patched by the Fix Pack installer. These conflicts are identified in the file overwrittenfiles_timestamp.log, which is created in the ORACLE_HOME/cfgtoollogs/oui directory.
Restart the Web Server

You must restart the Web server after you have finished installing Siebel Fix Pack 8.1.1.x on all of the 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 directory to contain static files required for the current version of the Siebel application (corresponding to the latest Fix Pack release). This directory 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 directory and other directories are created on the first SWSE request after you install any Siebel Business Applications release. This directory is populated with static files copied from the Siebel Server directory SIEBSRVR_ROOT/webmaster/siebel_build. The contents of these directories are updated each time that the Web server restarts, or when an administrator enters a Web update command in the browser. After a build-specific directory is created on the SWSE, directories 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, which are both on Siebel Bookshelf. Failure to restart the Web server after installing the Fix Pack for Siebel Enterprise Server components and for the SWSE means that the directories 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 84. Siebel applications running in high interactivity use both ActiveX controls and Java controls, which must be downloaded or predeployed to each client computer. This topic describes tasks that you might have to perform after installing a Siebel Fix Pack so that users of these applications can access the necessary controls. After you install a new version of a Siebel application, including a Siebel Fix Pack, the applicable ActiveX controls for high interactivity applications are downloaded onto your users client computers when they run the Siebel application in the Internet Explorer browser and access the features that use these controls. Updated versions of the ActiveX controls are provided in each Siebel Fix Pack. This behavior applies to high interactivity applications running in the Siebel Web Client, Mobile Web Client, and Developer Web Client.
102
Alternatively, for Mobile Web Clients and Developer Web Clients, administrators can predeploy the ActiveX controls to the client computers by loading the file predeploy.htm in the Internet Explorer browser. For more information about downloading or predeploying ActiveX controls for Siebel CRM version 8.1.1, see the browser configuration chapter in Siebel System Administration Guide. See also the Siebel client installation chapter in the Siebel Installation Guide for the operating system you are using. When you install Siebel Fix Pack 8.1.1.9 or later, an updated predeploy.htm file is placed in the directory SIEBEL_CLIENT_ROOT\public\lang. In this path, SIEBEL_CLIENT_ROOT is the Siebel Mobile Web Client installation directory and lang represents each installed Siebel language. In order to predeploy the updated ActiveX controls, the administrator must load each language-specific version of this file in the browser. After a new Siebel software version is installed, Java controls for high interactivity are also downloaded. If caching is enabled, then cached versions of these controls might 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, and then click Reset. After a new Siebel software version is installed, it 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 My Oracle Support Certifications. The JRE can be downloaded automatically to client computers, as described in Siebel System Administration Guide. NOTE: In version 8.1.1.9 and later, a new user interface framework, Siebel Open UI, is provided as an alternative to high interactivity. For more information, see 1499842.1 (Article ID) on My Oracle Support and see the Siebel Bookshelf.
Postinstallation Tasks for Supporting Additional Languages

This topic is part of Siebel Fix Pack Installation Instructions on page 84. If you are installing an additional language into an existing version 8.1.1.x installation, then review the information in this topic, in case it applies to you. For more information about adding languages, including important restrictions, see About Installing Languages on page 90.
Importing Locale-Specific Data into the Siebel 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 of the Siebel Business Applications.
10 3
Updates might be needed either because a string has been incorrectly translated for a particular language or because installing a patch release has caused a new string or message to appear for all of the 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. They might not apply for any particular version 8.1.1.x release or language. The following procedure uses the Locale Management Utility (LMU), which is part of Siebel Tools, to import an LMU file. An LMU file might 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 that you are actually using in your installation. In the procedure, 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.
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 that you are importing. The target language is the Siebel language into which the strings will be imported.
3 4
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, then they are marked with the Redo flag. This flag helps you identify records that might 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 84. This topic describes how to uninstall Siebel Fix Pack 8.1.1.x releases for Microsoft Windows and for UNIX and Linux.
104
In general, the uninstallation options for Siebel Fix Pack version 8.1.1.10 are as follows: Uninstall the full installation (Siebel CRM version 8.1.1 and version 8.1.1.10). If you installed version 8.1.1.10 as a new installation for Siebel Enterprise Server or Siebel Web Server Extension (SWSE), then you can use this option. NOTE: The uninstaller programs described in this document include an option to perform a complete uninstallation of version 8.1.1 and 8.1.1.10. Some requirements apply for a complete uninstallation, which are outside the scope of this document. For more information about performing a complete uninstallation, see the Siebel Installation Guide for the operating system you are using. Uninstall the Siebel Fix Pack version 8.1.1.10 and revert to the previous version of the installed Siebel software: version 8.1.1 or a prior version 8.1.1.x release, such as version 8.1.1.8 or 8.1.1.7. If you installed version 8.1.1.10 as a new installation for Siebel Enterprise Server or SWSE, then you cannot use this option.
NOTE: This topic describes how to uninstall the current Siebel Fix Pack version 8.1.1.x (for which installation is described in this guide, in Installing the Siebel Fix Pack on Microsoft Windows on page 91 or Installing the Siebel Fix Pack on UNIX on page 96). For uninstallation of a previous Siebel Fix Pack version 8.1.1.x (such as version 8.1.1.9), see the Siebel Maintenance Release Guide applicable to the version that you are uninstalling. For more information, see Siebel Maintenance Release Guides for Siebel Fix Pack 8.1.1.x Releases on page 8. Siebel Fix Pack uninstallation for modules that are not mentioned here is generally similar to what is described here. This topic contains the following information: Scenarios for Uninstalling the Siebel Fix Pack on page 105 Uninstalling the Siebel Fix Pack for Siebel Enterprise Server and Siebel Web Server Extension on page 106 Uninstalling the Siebel Fix Pack for Siebel Clients on page 109 Guidelines and Limitations for Siebel Fix Pack Uninstallation on page 109
Scenarios for Uninstalling the Siebel Fix Pack

This topic is part of Uninstalling Siebel Fix Packs on page 104. In some circumstances, you might need to, or might choose to, uninstall the current Siebel Fix Pack version 8.1.1.x release and revert to the version of the previously installed Siebel software: version 8.1.1 or a prior version 8.1.1.x release. For example: Where applicable, you might uninstall an existing installed Siebel Fix Pack 8.1.1.x release before installing the current Fix Pack or adding languages. For Siebel Enterprise Server and Siebel Web Server Extension, this option does not apply if you installed Fix Pack version 8.1.1.10 as a new full installation. However, if you installed version 8.1.1.8 as a new installation and then installed version 8.1.1.9, then you can uninstall version 8.1.1.9 and revert to version 8.1.1.8 before installing version 8.1.1.10.
10 5
If you have encountered issues in your deployment, then you might uninstall an existing installed Siebel Fix Pack 8.1.1.x release and revert to version 8.1.1 or a prior version 8.1.1.x release. Subsequently, you might decide to install a lower-level Fix Pack, where applicable. For Siebel Enterprise Server and Siebel Web Server Extension, this option does not apply if you installed Fix Pack version 8.1.1.10 as a new full installation. However, if you installed version 8.1.1.8 or version 8.1.1.9 as a new installation and then installed the current Fix Pack, then you can uninstall the current Fix Pack and revert to version 8.1.1.8 or version 8.1.1.9.
NOTE: For uninstallation of a previous Siebel Fix Pack version 8.1.1.x (such as version 8.1.1.9), see the Siebel Maintenance Release Guide applicable to that version. For more information, see Siebel Maintenance Release Guides for Siebel Fix Pack 8.1.1.x Releases on page 8. CAUTION: If you revert to the version 8.1.1 base installation or to a prior version 8.1.1.x, then change request fixes and new functionality that were added in any Siebel Fix Pack 8.1.1.x release that was uninstalled are no longer available. You also have to take steps described later in this topic, under guidelines and limitations.
Related Topics Enhancements and Updates in Siebel Fix Pack 8.1.1.10 on page 19 Siebel Fix Pack Installation Overview on page 84 Resolved Bugs in Siebel Fix Pack 8.1.1.10 on page 110
Uninstalling the Siebel Fix Pack for Siebel Enterprise Server and Siebel Web Server Extension
This topic is part of Uninstalling Siebel Fix Packs on page 104. Follow the instructions in this topic to uninstall the installed Siebel Fix Pack 8.1.1.x release for Siebel Enterprise Server and Siebel Web Server Extension (SWSE) and revert to version 8.1.1 or a prior version 8.1.1.x release. For more information about uninstalling Siebel base installations, see the Siebel Installation Guide for the operating system you are using. Where applicable, see also the Siebel Maintenance Release Guide for a prior version 8.1.1.x release. For more information, see Siebel Maintenance Release Guides for Siebel Fix Pack 8.1.1.x Releases on page 8. When you installed version 8.1.1.x as a new installation, you would have referred to the Siebel Installation Guide for the operating system you are using. After you uninstall version 8.1.1.10 and revert to version 8.1.1 or a prior version 8.1.1.x release (through version 8.1.1.7), the applicable version of the Siebel Installation Guide for the operating system you are using for your installed software is version 8.1, Rev. A, which is available on My Oracle Support at Article ID 1461732.1. After you uninstall version 8.1.1.10 or version 8.1.1.9 and revert to version 8.1.1.9 or version 8.1.1.8, the applicable version of the Siebel Installation Guide for the operating system you are using for your installed software is version 8.1, Rev. B or later. The latest version of this guide is available on the version 8.1 Siebel Bookshelf (http://download.oracle.com/docs/cd/E14004_01/ homepage.htm).
106
NOTE: The uninstaller programs described in this guide include an option to perform a complete uninstallation of version 8.1.1 and 8.1.1.10. Some requirements apply for a complete uninstallation, which are outside the scope of this document. For more information about performing a complete uninstallation, see the Siebel Installation Guide for the operating system you are using.
Uninstalling the Siebel Fix Pack for Siebel Enterprise Server or SWSE on Microsoft Windows Use these instructions for uninstalling the Siebel Fix Pack for Siebel Enterprise Server or Siebel Web Server Extension (SWSE) on Microsoft Windows. NOTE: In Siebel Fix Pack version 8.1.1.8, the uninstallation scripts for Siebel Enterprise Server and SWSE are uninstall_ses.bat and uninstall_swse.bat. In version 8.1.1.9 and later, the uninstallation scripts for Siebel Enterprise Server and SWSE are both named uninstall.bat. If you have installed version 8.1.1.9 or later onto version 8.1.1.8, then you will still see uninstall_ses.bat and uninstall_swse.bat, along with uninstall.bat. To uninstall version 8.1.1.9 or later, use either rollback.bat or uninstall.bat, as described in the procedure, instead of uninstall_ses.bat and uninstall_swse.bat. These scripts are provided in the directories noted in the following procedure. CAUTION: If you previously installed version 8.1.1.8 as a new installation, then, to uninstall version 8.1.1.9 or later and revert to version 8.1.1.8, you must use the rollback command, as shown in Step 2 on page 107. In all other cases, use the uninstall command, as shown in Step 3 on page 107. If you use the uninstall command instead of the rollback command where version 8.1.1.8 had been installed as a new installation, then the uninstall command performs a complete uninstallation. The rollback command is for installations that were installed using only Oracle Universal Installer software. The uninstall command is for installations that were originally installed using the version 8.1.1 installer, which is based on InstallShield.
To uninstall the Siebel Fix Pack for Siebel Enterprise Server or SWSE on Microsoft Windows 1 2
Stop the services, as you did when you installed the Siebel Fix Pack. (If you previously installed version 8.1.1.8 or version 8.1.1.9 as a new installation) To uninstall version 8.1.1.10 and revert to version 8.1.1.8 or version 8.1.1.9, do the following:
a b
From a DOS prompt, navigate to the ORACLE_HOME\oui\bin directory, such as C:\siebel\8.1.1.0.0\ses\oui\bin or C:\siebel\8.1.1.0.0\sweapp\oui\bin. Enter the following command: rollback -proceed
(In all other supported scenarios) To uninstall version 8.1.1.10 and revert to version 8.1.1 or a prior version 8.1.1.x release, do the following:
a b
From a DOS prompt, navigate to the ORACLE_HOME\uninstall directory, such as C:\siebel\8.1.1.0.0\ses\uninstall or C:\siebel\8.1.1.0.0\sweapp\uninstall. Enter the following command: uninstall
10 7
4 5
Choose the option to uninstall the Siebel Fix Pack. When the uninstallation and rollback process is complete, restart the services.
Uninstalling the Siebel Fix Pack for Siebel Enterprise Server or SWSE on UNIX or Linux Use these instructions for uninstalling the Siebel Fix Pack for Siebel Enterprise Server or Siebel Web Server Extension (SWSE) on UNIX or Linux. NOTE: In Siebel Fix Pack version 8.1.1.8, the uninstallation scripts for Siebel Enterprise Server and SWSE are uninstall_ses.sh and uninstall_swse.sh. In version 8.1.1.9 and later, the uninstallation scripts for Siebel Enterprise Server and SWSE are both named uninstall.sh. If you have installed version 8.1.1.9 or later onto version 8.1.1.8, then you will still see uninstall_ses.sh and uninstall_swse.sh, along with uninstall.sh. To uninstall version 8.1.1.9 or later, use either rollback.sh or uninstall.sh, as described in the procedure, instead of uninstall_ses.sh and uninstall_swse.sh. These scripts are provided in the directories noted in the following procedure. CAUTION: If you previously installed version 8.1.1.8 as a new installation, then, to uninstall version 8.1.1.9 or later and revert to version 8.1.1.8, you must use the rollback command, as shown in Step 2 on page 108. In all other cases, use the uninstall command, as shown in Step 3 on page 108. If you use the uninstall command instead of the rollback command where version 8.1.1.8 had been installed as a new installation, then the uninstall command performs a complete uninstallation. The rollback command is for installations that were installed using only Oracle Universal Installer software. The uninstall command is for installations that were originally installed using the version 8.1.1 installer, which is based on InstallShield.
To uninstall the Siebel Fix Pack for Siebel Enterprise Server or SWSE on UNIX or Linux 1 2
Stop the services, as you did when you installed the Siebel Fix Pack. (If you previously installed version 8.1.1.8 or version 8.1.1.9 as a new installation) To uninstall version 8.1.1.10 and revert to version 8.1.1.8 or version 8.1.1.9, do the following:
a b
Open a new shell and navigate to the $ORACLE_HOME/oui/bin directory, such as /siebel/ 8.1.1.0.0/ses/oui/bin or /siebel/8.1.1.0.0/sweapp/oui/bin. Enter the following command: rollback -proceed
(In all other supported scenarios) To uninstall version 8.1.1.10 and revert to version 8.1.1 or a prior version 8.1.1.x release, do the following:
a b
Open a new shell and navigate to the $ORACLE_HOME/uninstall directory, such as /siebel/ 8.1.1.0.0/ses/uninstall or /siebel/8.1.1.0.0/sweapp/uninstall. Enter a command like the following: ./uninstall -jreLoc jre_location -invPtrLoc inventory_location where:
jre_location is the full path of the installed Java Runtime Environment (JRE) software. On AIX, you must use the -jreLoc option. It is not required on other operating systems.
108
inventory_location is the full path of the oraInst.loc file (for example, /export/home/
4 5
Choose the option to uninstall the Siebel Fix Pack. When the uninstallation and rollback process is complete, restart the services.
Uninstalling the Siebel Fix Pack for Siebel Clients

This topic is part of Uninstalling Siebel Fix Packs on page 104. Follow the instructions in this topic to uninstall the installed Siebel Fix Pack 8.1.1.x release for Siebel Mobile Web Client and Siebel Tools Client and revert to version 8.1.1 or a prior version 8.1.1.x release. This option is available for Siebel Fix Pack 8.1.1.8 or later.
To uninstall the Siebel Fix Pack for Siebel clients 1 2

Exit the Siebel client if it is running. From a DOS prompt, navigate to the ORACLE_HOME\oui\bin directory, such as C:\siebel\8.1\Client_1\oui\bin (for Mobile Web Client) or C:\siebel\8.1\Tools_1\oui\bin (for Siebel Tools Client). To uninstall version 8.1.1.x and revert to version 8.1.1 or a prior version 8.1.1.x release, enter the following command: rollback -proceed
When the uninstallation and rollback process is complete, restart the Siebel client.
Guidelines and Limitations for Siebel Fix Pack Uninstallation

This topic is part of Uninstalling Siebel Fix Packs on page 104. Note the following guidelines and limitations related to Siebel Fix Pack uninstallation for installed Siebel CRM software: For Siebel Enterprise Server and Siebel Web Server Extension (SWSE): If you installed Siebel CRM version 8.1.1.9 or 8.1.1.8 as a new installation and then installed Siebel Fix Pack 8.1.1.10, then you can uninstall the current Fix Pack and revert to version 8.1.1.9 or 8.1.1.8. You can also perform a complete installation. However, you cannot revert to any version lower than the original version of the new installation (such as version 8.1.1.9 or 8.1.1.8). For Siebel Enterprise Server and SWSE: If you installed Siebel CRM version 8.1.1.8 as a new installation and then installed Siebel Fix Pack 8.1.1.10, then you must use the rollback command to uninstall the current Fix Pack and revert to version 8.1.1.8. If you use the uninstall command instead, then the command performs a complete uninstallation. For more information, see Uninstalling the Siebel Fix Pack for Siebel Enterprise Server and Siebel Web Server Extension on page 106.
10 9
Siebel Maintenance Release Guide, Version 8.1.1.10, Rev. B Resolved Bugs in Siebel Fix Pack 8.1.1.10
For Siebel Mobile Web Client or Siebel Tools, you can uninstall the current Siebel Fix Pack and revert to the previous version of the installed software. However, if you previously installed any Siebel Fix Pack below version 8.1.1.8, then you cannot uninstall this Fix Pack and revert to version 8.1.1. Limitations also apply to adding languages in this case, as noted in About Installing Languages on page 90. If a Fix Pack installation fails, then 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, then proceed with reinstalling the Fix Pack. If these steps are omitted, then future attempts to uninstall the Fix Pack might fail. If you made any repository or configuration changes related to a Fix Pack that you have installed, then, before you uninstall the Fix Pack, the repository or configuration must be restored to the state when the Fix Pack was first installed. It is recommended that you verify the version number of the installed Siebel CRM software after you uninstall a Siebel Fix Pack. For more information, see Postinstallation Tasks for the Siebel Server on page 100 and Postinstallation Tasks for the Siebel Server on page 100.
Resolved Bugs in Siebel Fix Pack 8.1.1.10

The table in this topic provides a list of resolved bugs that are included in Siebel Fix Pack 8.1.1.10. Customers using version 8.1.1 or a prior Siebel Fix Pack 8.1.1.x should install the latest 8.1.1.x Fix Pack. NOTE: For information about the bug fixes included in previous Siebel Fix Pack 8.1.1.x releases, see the applicable Siebel Maintenance Release Guide on My Oracle Support. For information about accessing Siebel Maintenance Release Guides for previous Siebel Fix Pack 8.1.1.x releases, see Siebel Maintenance Release Guides for Siebel Fix Pack 8.1.1.x Releases on page 8. Unless specifically noted in the table, all known anomalies from the base version remain unresolved. For each release, the resolved changes table includes 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. 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.
110
NOTE: If you have installed a Quick Fix, see Quick Fixes Included in Siebel Fix Pack 8.1.1.10 on page 10.
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID Base Bug ID Subarea Special Instructions
Issue Addressed
Siebel Application Integration

Inbound SOAP Services
When DistributeProductConsume.2009 1216.wsdl is deployed, deployment fails with errors 14671259 Inbound SOAP Services
Siebel Apps Customer Order Management

Bulk Requests
When users have set AutomaticTrailingWildcards to False, they do not receive the correct results when they query in the ABO Bulk Request Component Product pick applet When users create a new validation rule, the rule is not validated if a field has already been validated by another rule Attribute values in bulk requests are stored in Language Dependent Code (LDC) instead of in Language Independent Code (LIC) When the status of a bulk request is set to queued, processing, or complete, the Delete button is not disabled 14775727 Administration
13702285
Asset Based Ordering
13527856
10625529
14558895
11 1
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 13654907 Base Bug ID 13654521 Subarea Asset Based Ordering Special Instructions
Issue Addressed When two sets of actions are applied to an asset, Bulk Requests functionality does not work correctly ACR 499: Exceptions are not captured when a product that is not an asset is deleted through Bulk Requests ACR 499: When orders are created using Bulk Request, the Billing Profile field is not populated ACR 499: Orders that are created using Bulk Request have Medium as the default priority ACR 499: When a promotion is upgraded using Bulk Request, the OK button is disabled
10599898
10599242
10602216
10602215
10602889
10602888
Asset Based Ordering Asset Based Ordering
10606534
10606531
Catalog
Within Sales Order > Catalog, when users search for a product, click the Reset button, navigate to another view and then return to the Catalog > Search view, they receive an error message 12341562 Search
Customizable Prod/ Configurator

Joint workspace import does not process product descriptions that are too long The BatchValidate process returns an incomplete status for required products When AutoSync is set to Y, the BatchValidate process saves incomplete configurations 14571555 Administration
16169218
12901587
APIs
14578295
APIs
112
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14678057 Base Bug ID Subarea APIs Special Instructions
Issue Addressed The Configurator script GetAttribute() function does not work after ACR 502 has been installed When a conflict occurs during selection of a product on the Configurator page, when users click the Explanation button, the page refreshes but no explanation appears Validation does not succeed when the Configurator Validate Workflow workflow process is used When users select multiple assets when modifying an asset, the currency symbol ($) does not display The eCommunications Object Manager crashes during logoff Open UI: The buttons in the Configurator page are displayed vertically When the cardinality of a product is not met, a red asterisk does not display next to class and is only shown next to root product Runtime customization skips steps The SetAttribute event does not work for child products Smart part numbers are not calculated correctly for thirdlevel products User-defined errors from Product scripts have Siebel error messages appended
15942126
Error Messages
10571404
Rule Behavior
14590133
Runtime
14313547 14727183
Runtime Runtime
14574457
Runtime
14505984 14707027 16101862
Runtime Runtime Runtime
13538814
Runtime
11 3
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 12750350 Base Bug ID Subarea User Interface Special Instructions
Issue Addressed ACR 502: Dynamic Hide functionality does not work when users start Configurator Root product names are translated but subproducts in relationships are not translated
10518337
User Interface
Integrations
The SWIProductImport web service does not raise an error when an invalid Business Unit ID is provided When the SWIOrder Siebel inbound web service is used, AIA Order to Cash flows fail to sync orders in Siebel CRM Within the Contacts screen, the menu drop-down list does not display match or fetch options, and within the Accounts screen, these options are displayed in the drop-down list but the fetch option is unavailable The application crashes while accessing caching VBCs 13948380 AIA
14364868
AIA
14709355
Installation
14504343
UtilitiesCCMB
Order Administration
The Revise Commerce Content job does not work When users configure the AutoOrderServiceQuoter signal, query for the Reprice 5 quote, navigate to the Quotes - Orders view, and click the Service Order button, they receive an error message Errors occur in payments when the transaction amount is negative 14733441 13649127 Copy Service Order Types
14726389
10527493
Payment Terms
Product Administration
114 Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14341838 14160871 Base Bug ID Subarea Product Attributes Products Special Instructions
Issue Addressed ACR 502: Seed data includes locked attributes When users change the value in the Effective Date field and set a flag, after the users click Export, the values in the fields are reset to the default values The Error Message and Error Status columns are visible The Object Manager crashes when users log off The Submit and Revise buttons are disabled in the Export Contents header applet The Update Commerce application button is blank The Update Commerce App menu item is missing from all of the views within Administration Products
14733264 14732447 14415370
Products Products Products
14395899 14396023
Products Products
Product Offers
ACR 643: When the parameter value is Upgrade Product or Attribute Value, the Component Product field is editable when it should be read-only ACR 643: When users accept a product offer, they are not navigated to the Sales Order view ACR 643: Upgrading promotions through product offers does not work properly 13823239 Administration
16220210
Runtime
14101964
Runtime
Product Promotions
ACR 620: Adjustments are applied to all BP components instead of the BP header 11797917 11067703 Administration
11 5
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 15909474 Base Bug ID Subarea Administration Special Instructions
Issue Addressed Product Promotion Attributes does not work correctly if a product has constraints After users have installed version 8.1.1.7, have applied ACR 502, and have applied loose Library DLLS, upgrading promotions fails ACR 620: The Interpromotion Compatibility Require rule does not work as expected When agreements are created during the auto-asset process, the end date for promotion commitments is calculated incorrectly Edit Promotion functionality malfunctions and prevents users from selecting two distinct product lines inside one promotion When users update the component quantity to zero, an error message appears When a promotion is added to an order, the root product is added but the components are not The incorrect promotions display in the ISS Promotion Upgrade popup applet
14204917
14569957
Administration
11070214
11067703
Runtime
16036064
Runtime
14211059
Runtime
14193052
Runtime
13820092
Runtime
14337611
Runtime
Promotion Groups
Open UI: Promotion group flows do not work 14547738 Runtime
116
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14204833 Base Bug ID Subarea Runtime Special Instructions
Issue Addressed Within the Account - Summary view, when users enable the Task pane, run the Create Promotion Group task, run the workflow, and then click the Submit button, the newlycreated order has a status of Open, and the application navigates to the Account Summary view instead of the Sales Order > Line Items > Promotion Group Details view
PSP Engine
The Clear Cache method does not work on all Object Managers across an enterprise 15897514 14682607 PSP Procedures
Quotes & Orders

After an asset has been created, when users change the product class or change or delete the attribute, they receive an error message When ABO has been enabled, the EndConfiguration web services does not save changes to the database Assets can be modified after their attribute values have been changed The SIS OM Disconnect Products and Services Process workflow queries for all assets The Menu option is missing in the high interactivity application 14633703 Asset Based Ordering
12412226
14844432
Asset Based Ordering Asset Based Ordering COMMON
14796029
14506005
11 7
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14510727 Base Bug ID 15912137 Subarea ConfigRepository Special Instructions
Issue Addressed Within the Quotes > List view, when users create three quotes and then navigate to the Calendar view, the three quotes do not display, and when users navigate to the Calendar > Activity/Quote Calendar view, no quotes display When users revise a quote, the script generates the SBL-DAT00402 error message The Excludes compatibility rule does not work as expected Users cannot select the Ship To contact in the Line Item Fulfillment detail applet When users update opportunities from quotes, opportunity revenue is deleted from other quotes When users click the Verify button, incorrect validation messages display Within the Japanese application, the Weight column is inaccurately translated With the Quote screen, when users create a new quote, add an organization that the login user does not belong to within the Organization MVG applet, change the primary to the new organization record, close the MVG applet, and select Revise, the new quote record does not have the primary organization
12775019
Config-Scripting
13918250 14263237
Eligibility & Compatibility Fulfillment
12318993
Line Item Details
13385683
Line Item Details
13648936
Orders
10590121
Orders
118
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 13402592 Base Bug ID Subarea Special Instructions
Issue Addressed Within Administration - Product > Product Promotions, when users navigate to Menu > Export Version and select Objects Only or Full Structure in the Export Contents dialog box, they receive an error message
Siebel Apps -Data Quality

Data Quality
Within the PersonMatch operation, an error occurs processing the SWIPersonmatchOutputIO argument The Siebel UDQ API sdq_dedeup_realtime method expects an invalid XML element in the response parameter 14476074 Universal Connector
13828943
Universal Connector
Siebel Apps - Field Service Automation

Within the Activities > Recommended Parts view, when users click New, add a product from the Product Identifier MVG, and then click the Order Selected Parts button, they receive an error message 16002129
Home Page
The eService login applet does not have register, forget, and remember password controls 15946752
Inventory Management
11 9
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14649588 Base Bug ID Subarea Parts Inventory Special Instructions
Issue Addressed Automatically created inventory transactions use the wrong bias to calculate the UTC timestamp
Invoices
The GetLastDate method in the FS Service Schedule business service does not perform as expected 14744386 Invoices
Open UI - Mobile
The Contact Email Address field does not have an email icon next to it Within Activities, when users create an new activity, create line items for the activity, navigate to Invoice line items, click Auto Invoice, click Sign, and then click the Contact button to add a contact, the resolution for the signature is not correct and the Contact popup window does not work In the Activity Contacts view, the Contacts list applet does not show Name, Email, and Work Phone Within the Related Items list, the Instructions tab should display before the Steps tab Within the Invoice > Sign > Signature Capture applet, labels are missing for the Signature control Adds new symbolic strings for "Pl.Start", "Pl.End", "Par. Account", and "Par. Location" 14778671 14762814 Open UI - Mobile
14774935
14688411
Open UI - Mobile
14778751
14762814
Open UI - Mobile
14778725
14762814
Open UI - Mobile
14824146
14737937
14826491
14737937
ORS - Scheduling
The Get Geocode functionality does not work 14126154 Administration
120
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 12552354 Base Bug ID Subarea General Special Instructions
Issue Addressed There are invalid runtime events for Employee Shift Exception Hour actions
Service Requests
When users create service requests and select any area other than Human Resources in a service request, the Subarea field is not populated and they cannot create the service request 16056790 13339479 Service Requests
Siebel Apps Handheld Client

Handheld Client
After a call is submitted, the Sign and Submit buttons are still enabled After a successful initial sync and registration with the mQe server, the Handheld application fails to start with and a Storeand-Forward password decryption error message displays When the inbound message icon flashes, users cannot navigate to another view When Store-and-Forward Messaging is used and encryption is enabled for Storeand-Forward Messaging, the PDA reports that the database is invalid 8.1.1.7 PDA [21238_1] introduces a bug where the parent applet requires refreshing 14848801 Client App
14729047
SMQ Messaging
14360325
10561164
SMQ Messaging
14127699
Synchronization
14492498
User Interface
12 1
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14032014 14560311 14035563 Base Bug ID Subarea User Interface User Interface User Interface Special Instructions
Issue Addressed On WM 6.5.3 devices, there is no scroll bar for long form applets On WM 6.5.3 devices, View > Display Applet is too low The View drop-down lists are very small and the names of the items on the lists are truncated
Handheld Sync
In version 8.1.1.6, BatchSync processing fails because the UploadOnly option does not work With Store and Forward Messaging, when records are created on the handheld device, only the Id field value is preserved 13907291 Direct Server Sync
13840299
Direct Server Sync
Siebel Apps Marketing

Mktg/Campaign Mgmt
Campaign Wave Launch processes remain in the In Progress state When users log in from an organization other than the default organization, create a new offer and treatment with the Activity option checked, create a new campaign with the offer and treatment that they previously created, load the campaign, and launch it, follow-up activities are not created When activities are scheduled for a recurring campaign, the Load and Launch process does not complete the tasks according to the schedule 13626533 Campaign Processing Campaign Processing
14223649
13915134
Campaign Processing
122
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 13016886 Base Bug ID Subarea Campaign Processing Programs Special Instructions
Issue Addressed Within the Campaign > Design > Allocation view, the values in the Total Cost field are inconsistent The Remove and Remove All buttons on shuttle applets do not work with the "CSSBCMktgCommon" class
14080178
Mktg/Email Marketing
The incorrect campaign ID displays in email treatments that contain trackable URLs There is no option for merging dynamic content into emails 13490649 Server - Click Through Server (CTD) 15842866 Server Sending/Content Gen (ESD)
15882154
Mktg/Events
When users change the Event Planning status from In Planning to Launched, the status of subordinate events is also changed to Launched In event plans, team field values are not inherited by child events The value of the Format field that is defined in the session template is not carried over to Event Session records 14723352 Customer Views
14492206 12898788
Employee Views Employee Views
Mktg/Leads
The eCommunications application crashes when users log out 14306189 Lead Processing
Mktg/List Management
When a contact that is associated with a new account is imported, the import does not work if an account does not already exist for the contact 13391522 List Import
12 3
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14410199 16010880 14364073 Base Bug ID Subarea List Import List Import Special Instructions
Issue Addressed List import does not populate the Response > Account Id field When users create a response import mapping with mandatory fields, create import data that contains five records but two of the records contain the wrong date, and perform an import, three records should be imported and two records should appear in the Exceptions tab, but only one failed record appears If an import file contains the " character, the wrong mapping occurs
14578317
List Import
Mktg/Marketing
Within the Italian version of the Marketing application, within Administration - Marketing > Import, when users create new import jobs, attach text files within the Job Setup tab > File Name field, when the users drill down on the File Name field, they receive an error message Within Site Map > Landing Sites, side panels display an error message 13919535 Error Messages
14513910
Error Messages
Mktg/Responses
The eCommunications application crashes during logoff 14751742 Responses
Siebel Apps Multichannel Technologies

Assignment Manager
124
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14198101 Base Bug ID Subarea Administration Tools Special Instructions
Issue Addressed Join specifications only work when the assignment criteria from the policy component where the join specification is defined are used When the parent account is changed, dynamic rules for accounts do not work well
14100850
Server Processes
Siebel Apps Multichannel Technologies

CRM Chat
When a chat is active and agents refresh CTRL+R or F5 to refresh the screen, the chat disappears 14484513 14004904 UI: Agent Facing
CTI
Assistive technology reads the CTI messages displayed on the CTI toolbar twice Assistive technology reads Alert, Alert for CTI popup windows Open UI: The sound does not work for CTI inbound calls Resolves a performance issue with using hotkeys for outbound calls Hotelling fails after users uncheck the "Use automatic configuration script" option and clear the value in the "Do not use proxy server for addresses beginning with" field is cleared When parameter values are incorrect within a configuration, the CTI toolbar and Toggle CTI button cannot load, but no error message displays 14540124 Accessibility
14540162 14805540 10589436
Accessibility Accessibility Client
14631527
Client
Yes, see Instructions for Bug 14631527 on page 192.
14648455
Client
12 5
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14373938 14848944 14775938 Base Bug ID Subarea Client Client Client Yes, see Instructions for Bug 14775938 and Bug 14846565 on page 195. Yes, see Instructions for Bug 14775938 and Bug 14846565 on page 195. Special Instructions
Issue Addressed Open UI: Users cannot import CTI configurations The CTI client response time is not logged to a file Within the Siebel application, when agents log into the CTI toolbar, navigate to the Contact list view, and click a phone number hyperlink or press F2 to make a call, a Call button now appears within the dialog box Within the Siebel application, when agents log into the CTI toolbar, navigate to the Contact list view, and click a phone number hyperlink or press F2 to make a call, a Call button now appears within the dialog box The Dashboard does not contain a title, a frame, or a visible border for the display field, and the Go button is in text Users cannot change the language for the tooltip voice The CTI toolbar is not enabled for user names that contain more than 30 characters
14846565
Client
14228770
Client
12567335 14551453 10477346
Configuration Server
Email Issues
The CC, BCC, and Attachment fields do not work with wrapper templates When an email is sent to more than one recipient and one recipient's email address is not valid, there is no notification that the email failed to be delivered to the invalid email address 13108583 Comm Outbound Business Service Comm Outbound Business Service Yes, see Instructions for Bug 13717920 on page 192.
13717920
126
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 16011105 Base Bug ID Subarea Comm Server Components Special Instructions
Issue Addressed When a contact does not have an email address associated with it, CommOutboundMgr creates a new job to submit the outbound request again, which creates a loop When users add attachments with file names that contain the semicolon character (;), the email is resent every fifteen minutes Outbound requests yield the SBL-CMO-00165 error message Outbound requests yield the SBL-CMO-00165 error message When an email template contains a colon or a bracket, when users press F9 to generate an email, the email contains two blank lines Blank communications templates add carriage returns If substitution fields are present in the default closing template, text from body templates displays after the closing message When a template has colons and brackets, when users press F9 to send an email, the email contains two extra blank lines After users uncheck the HTML Template check box, HTML tags appear in email template text For generic email templates, the email body is not populated when users select the template from within a child applet
16024058
Comm Server Components
14305830 14780185 14514683 14305830 14514663
Comm Server Components Comm Server Components Communications Templates
14151179 14477717
Communications Templates Communications Templates
14514663
Communications Templates
14640581
Communications Templates Communications Templates
14626632
12 7
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14744010 Base Bug ID Subarea Email Response/ Workflows Email Response/ Workflows Special Instructions
Issue Addressed When users reply to an inbound email, they need to click twice on the Back button Email Response does not process emails from S_CM_INBND_EVT when the size of INBOUND_VAL columns is between 16351 and 16383 bytes When an outbound reply email is sent, it remains in Queued status instead of being set to Done A memory leak occurs in outbound emails When users click the Back button within the Communications Response detail view, they receive the SBL-DAT-00523 error message When users create two accounts with the same name but different locations, navigate to Communication > Communication List, select an email with the Account field not filled in, click the Reply button, navigate to the Outgoing Message applet and select one of the accounts that they created, they receive an error message When users press F9 to generate an email, the wrong sent date is written to the database Email addresses are validated incorrectly Users cannot restrict the visibility of categories and body templates using access groups
14839547
14267500
Email Response/ Workflows
14183186 14372284
Email Response/ Workflows Email Response/ Workflows
10534572
Email Response/ Workflows
10525309
Mail Client Integration (F9) Mail Client Integration (F9) User Interface (Comm Views)
16178940 13741577
128
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14604299 Base Bug ID Subarea User Interface (Comm Views) User Interface (Comm Views) Special Instructions
Issue Addressed Open UI: The Multiple Closing template is appended into the email body Within the Communications view, when users query using the query assistant using the OR operation, rows return that doe not meet the query criteria SSL and TLS can be enabled at the same time
14556786
14507521
User Interface (Comm Views)
Message Broadcasting
Accessibility: Within the Public Sector application, when users invoke the Landmark list using CTRL=INST+; focus on the Predefined Queries list, press Enter, and then press Tab, assistive technology reads Saved Queries, but when users press Tab again, assistive technology reads the application URL When users click the Notification icon, click on the Notification Summary list, and then press F5 to refresh, they receive a "server busy" error message 14706199 Message Bar
14743922
14731031
Message Bar
Siebel Apps Oracle Customer Hub

Universal Customer Master
When the RealTimePublishMethod method within the UCM Publish/ Subscribe business service is invoked, the application crashes 14740485 Publish/ Subscribe
12 9
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 15911133 Base Bug ID Subarea Publish/ Subscribe Special Instructions
Issue Addressed Updates on LAST_PUBLISH_DATE cause contention
Siebel Apps - PRM

PRM Partner Manager
Within Partner Programs > Application Inbox, when users query for an application, drill down on the Tracking Number link, drill down on the partner program, click the Entitlements Templates tab, click the Agreements tab and then click New in the Associated Agreements view, the application does not respond and users cannot create an agreement When a new user is created within the Partner Portal application, the Primary Id flag is not checked within the Accounts field When users log into the Partner Portal, create a service request, and then navigate to the Solution tab, the New button is unavailable Within the Partner Portal, when users navigate to Correspondence and click the New button, there is no field to input the data 13886192 Partner Programs Screen
10568066
Account/Contact Management
13912175
Other
13983783
Other
Siebel Apps Sales

Accounts
130
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14368727 Base Bug ID Subarea Accounts Special Instructions
Issue Addressed Invoices that are associated to an account do not display under the Account applet
Forecasts
When users create an account with more than 50 characters in the Account Name Field, create an opportunity record, associate products and revenue, associate the opportunity to the account, create a forecasting series with aggregation levels, and then generate a forecast, they receive an error message, but when the users remove the aggregation levels from the forecasting series and then regenerate the forecast, no error message appears When users create a forecast for a manager from the Forecasts screen, navigate to the Subordinates view, delete the forecasts in that view, and then query within the applet, the last record that the users deleted appears back in the applet When users opens a forecast that they did not create, the application performs slowly 14271585 Forecasts
14789552
Forecasts
14691343
Forecasts
Open UI - Mobile
When users navigate from Activities > Employees and select the second employee in the list, the first employee's information is still displayed The Duration field is not available within Accounts > Activities and Opportunities > Activities 14765216 Open UI Mobile
14777555
Open UI Mobile
13 1
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14741547 Base Bug ID Subarea Open UI Mobile Special Instructions
Issue Addressed Within Orders > Line Items, the percentage sign is missing from the Discount field Users cannot set the primary employee in the Activity Detail applet String values are inconsistent
16058520
Open UI Mobile
14609600
Opportunities
Within the Opportunity home page, the Collapse/Hide buttons in Rapid Search are not enabled Within the Sales Order home page, the Edit field is missing for the First Name field When the Opportunities list view, when users drill down on a record, navigate to the TAS tab, click the Prime Activities link, and create a new record, they receive an error message when they save the record 14839426 Opportunities
14631706
Opportunities
13540551
Opportunities
Siebel Apps Search & Knowledge Management

Search - Oracle SES
When users query in the Search Index Status applet and then click in the Search Index Settings view and then click it again, the previous query is retained When users select the Open in a New Window option, drilling down does not work ACR 603: Parameter values are not updated in eai.cfg 14224801 Administration
14813293
14777402
Administration
14122693
Administration
132
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14151419 Base Bug ID Subarea Administration Special Instructions
Issue Addressed The status is not updated to Indexed for all batches in FTP mode MVG popup windows display on top of the Preview Search view When users click the Save Preference button to save their language, the language preference is not saved Code is not independent of the repository for search preferences
13683744 15832063
Results UI Search Center
13523747
Search Preferences
Siebel Find
When users click the Binocular icon, the Search applet opens instead of the Find applet 14539640 Find
Siebel Search
With Advanced Search, the Modified Between Dates information is cached between users Open UI: Within Advanced Search, the Filter button is not translated into Spanish The focus is not in the Search for: text field 15974409 Advanced Search
16223920
Error Messages
14224164
Search
Siebel Apps Service

Assignment Manager
Account Organization Name criteria values display the row_id instead of the organization name The system assigns the wrong user to some accounts 10526357 10513356 Administration Client Server Processes
14391368
Customer Dashboard
13 3
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 16093420 Base Bug ID Subarea Customer Dashboard Special Instructions
Issue Addressed With Internet Explorer 8 and Chrome as the browser, in certain views, the Dashboard is hidden and users must scroll up to see it Adds a subsystem that is specific to Persistent Customer Dashboard
14727044
Customer Dashboard
SmartScript
Within the SmartScripts screen, when users drill down on the Acc_Test file name link, focus on the left side of the applet, and press Enter, the focus remains on the left side of the applet instead of moving to the applet on the right Within SmartScripts, when users enter a name in the first screen, click Next, select the Create New Record option in the next screen, click Next, and then select the Create Service Request option, when users click Next again, the Contact option is highlighted and cannot be deselected When users set the currency to a specific currency code in SmartScript questions, when users run the SmartScript, the currency defaults to US dollars 14560986 Open UI
14850718
14830645
Open UI
14616017
SmartScript
Siebel Apps Territory Management

Territory Management - Sales
134
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 10581529 Base Bug ID Subarea Territory Management Special Instructions
Issue Addressed Alignment Activation for opportunities fails with the ORA00936: missing expression error message
Siebel Apps - UCM

Universal Customer Master
ACR 744 and ACR 900 provide the following enhancements for the Siebel Customer Hub product: Child Survivorship Child Cross-Referencing Enterprise Data Quality Integration 14810181 Other
For more information, see ACR 744 and ACR 900: Oracle Customer Hub (UCM) Enhancements on page 26. ACR 744: Records are not enddated as expected ACR 744: After users click the Link and Update button in incoming duplicates, the second record does not display in the application A memory leak occurs in the InsertEntityAttributeData and InsertAttributeGroupData methods S_UCM_CONTACT address columns are not populated by the Transaction Manager business service 14696426 16013989 Other Other
16105640
Other
12942786
12648985
Source Data History
Yes, see Instructions for Bug 12942786 on page 193.
Siebel Automotive
Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B 13 5
Table 5.
Issue Addressed
Warranty Management
ACR 525: Errors occur during seed-data import 14140943
Siebel Calendar
Accessibility
Accessibility: There are three unlabeled buttons within the Daily Calendar home page 14704456 Accessibility
Alarms
When users set an value in the Alarm Lead field, the Alarm check box is not automatically selected 15857353 Alarms
Calendar UI
If users delete the primary contact for an appointment, they receive an "end of file" error message Users can edit the Primary check box within the Employee MVG when the Employee MVG is supposed to be read-only When users drag interface elements, the border does not follow the mouse When users query in the LS Pharma Activity HI Calendar Applet applet and then click on the left pane of the calendar, they receive an Internet Explorer script error Tooltips do not display meeting locations Within eCalendar, the Daily Applet home page tooltip is not translated correctly 12379156 Core ActiveX/HI
10598737
Core ActiveX/HI
13726040
Core ActiveX/HI
13463009
Core ActiveX/HI
14163448 13402699 14028483
Core ActiveX/HI Core ActiveX/HI
136
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14745895 Base Bug ID Subarea Core ActiveX/HI Special Instructions
Issue Addressed Within Activity > My Activity, when users create a new activity and set values in the Start Date and Duration fields, the End Date field defaults to blank When users navigate to the Activity screen, create an activity, enter values in the Start Date field, and then enter a value in the End Date field, when the users save the record, the duration is calculated incorrectly When appointment descriptions in the New Event dialog box, there is a limit on the number of characters The Month drop-down list displays full names of months and not abbreviations When users set an alarm for an appointment and the start time does not accommodate the minimum value for the alarm lead time, when users click OK on the error message dialog box, and then navigate to Help > Technical Support, the error message dialog box displays again Within the Calendar detail applet, the Owner field is readonly The Previous and Next arrow buttons are not reversed for right-to-left languages The time format for the Japanese application is set to the 12-hour clock Users can add invitees in readonly mode
14781687
Core ActiveX/HI
14734315
Core ActiveX/HI
10587720
14756693
Core ActiveX/HI
14723482
Core ActiveX/HI
14520818
Core ActiveX/HI
10534401
Core ActiveX/HI
14179669
Core ActiveX/HI
10598736
Core ActiveX/HI
13 7
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 10536662 Base Bug ID Subarea Core ActiveX/HI Special Instructions
Issue Addressed In the Portuguese - Brazilian application, the long-date format is not correctly displayed in calendar printouts Within the Calendar view, when users click the Advanced Calendar Options button, select All Employees from the Owner drop-down list, and then click OK, the settings window does not close Today is not highlighted in weekly and monthly calendar views The buttons for Day, Week, and Month are too small Within the Calendar home page, when users hover over the Daily, Weekly, and Monthly icons, the application displays Daily Calendar Applet for all three The Calendar tag renderer does not use component architecture There is no .css file to control the font sizes and attributes in jqfullcalrenderer.js When users create a call, add a contact, add a value to the Call Duration field, do not save the details, and then click the Attendees view tab, the screen is blank and the application hangs When users try to highlight multiple calendar slots to use the Quick Add functionality, the time slots are not highlighted The monthly mode does not appear in My Quotes calendar
14733772
Core Open UI
14725841
Core Open UI
15839717 14636492
Core Open UI Core Open UI
14395868 14707210
14597673
Core Open UI
14787941
Core Open UI
15983992
Core Open UI
138
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14667579 Base Bug ID Subarea Core Open UI Special Instructions
Issue Addressed Makes the 7-day and 30-day icons on the home page navigate to the full Calendar screen Open UI Calendar does not render appointments proportionally when the appointments overlap The 7 Day user preference does not work Within the Daily view, when users create a new appointment, drill down on that appointment to reach the Calendar detail view, add a meeting location to the appointment, and then click Save, the application navigates to the Weekly view instead of the Daily view Work hours are incorrectly calculated
14049695
Core Open UI
14787823 14798586
14768550
Core Open UI
Gantt Chart
Changes that users make in Calendar Gantt Chart AX applets are not retained when users navigate to other views The time format is incorrect in the Russian application 14502591 Gantt Chart
10552953
Gantt Chart
Siebel Communications & Energy

Assets/Admin
After users disconnect all of the products in a promotion, the disconnect fee is not added to the line items Contacts that are added in sales order do not appear in assets 13585357
10605181
13 9
Table 5.
Issue Addressed
Billing
Child applets are not refreshed when no child VBC records are returned 13965246
Integrations
Calls to the SWIProductImportUpsert web service cause an insert to the SIEBEL.S_PROD_INT_BU table that misses values for denormalized columns AIA: When users click within Billing Profile, the Siebel application displays an error message The default web services for asset-based operations behave inconsistently Within the Accounts screen, when users click on Billing Profile Name, and then navigate to the Payments tab, an error message displays 16030312 AIA
14789136
14723872
AIA
15977729
15856177
15853748
Order Management
If a product is set up incorrectly, the Application Object Manager crashes When users try to modify or disconnect orders on top of promotion assets, they receive an error message When users disconnect a promotion product that was not created by them, they receive an error message 14612437I
13034981
14247734
Orders
Users cannot create billing profiles for existing accounts 14116423
140
Table 5.
Issue Addressed
Workflow
When ACR 500 has been configured, when users try to perform the Add to Promotion function, they receive an error message 14050855 10513480
Siebel Consumer Goods

OPENUI_MOB
Within the Contacts > Best Times view, the Next button is truncated and the Previous button is not correct, and within Calls/Accounts > Retail Audit, the List Products button is truncated Within the Calls > Assessment view, when users add an assessment and an attribute, the Attribute applet can scroll completely behind the Assessment applet Users can edit account names that are in read-only mode 14848140 CGMobile
14832715
CGMobile
14762369
14662629
Promotions
The query that is used to search for promotions in order to update them is not efficient and returns too many records 13146612
User Admin
The default OnAssignProducttoSubAccount method is not working correctly in ADL 13602083 13515931
Siebel Core Automation

Table 5.
Issue Addressed
Test Automation
Siebel Core Common Components

Config - Rules
When users create a new quote record, create a quote child record, and save the record, the Delete button is disabled, but users can still edit the record 13027403 State Model
User Groups
Within the Position business component, when the postdefault value of the Relationship field is set, an error occurs when creating employees 14469295 Positions
Siebel Core - DB Deployment and Configuration

Repository Utilities
When users run DBCHK using the /9 Y switch, the DBCHK log show errors 14549118 Ddlsync
Upgrade
The Prepare for Table Creation step fails for the S_DOC_QUOTE and S_PER_ORG_UNIT tables 15884717 14852010 Repository
Siebel Core - DB Deployment and Configuration

Application Deployment Manager
142
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14286552 Base Bug ID Subarea Data Types Special Instructions
Issue Addressed When ADM is used to export SmartScripts, organizations that are associated with SmartScripts are not included When data is deployed using ADM, the schema version should not be checked
15862953
Framework
Siebel Core - EAI

Application Deployment Manager
When performing an activate step, ADM sends the GenTrig component to the wrong server 14061267 Data Transformation (EAI)
Integration Transports
The Siebel Dedicated Client cannot find the client certificate Workflow Process Manager does not connect to the failover JMS server in clusters A WebSphere MQe error occurs during the Publish/Subscribe process 14221148 14461301 HTTP JMS
14811813
MQ
Integration Business Services

Improves the quality of error messages Improves the quality of error messages Improves the quality of error messages Improves the quality of error messages DateTime fields are fetched as zeroes 13545850 13978067 14110100 10601544 14385681 13545850 Error Messages Error Messages Error Messages Error Messages Integration Objects
14 3
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 10604628 Base Bug ID 10599583 Subarea Other EAI Business Service Special Instructions
Issue Addressed The GetFieldValue business component method removes the leading zero (0) and returns a value of O
Java Integration
Corrects %1 to {0} in jca.xml to render error messages Improves the quality of error messages Improves the quality of error messages Improves the quality of error messages Improves the quality of error messages ACR 750: If the wrong certificate is declared on the Siebel Server side, a null point exception is thrown for outboundSSL Importing SAI Bundle with Jdev 11.1.1.5 does not throw an error message Corrects Siebel Application Integration log message formatting and presentation SOAP SAI services convert Boolean fields incorrectly Updates the error message for Bug 13509168 16065941 11679261 13548993 10601547 10604437 13509168 10601547 10601547 Error Messages Error Messages Error Messages Error Messages Error Messages Resource Adapter
14832232
Resource Adapter Resource Adapter Resource Adapter 13509168 Resource Adapter
14543116
15864406 16034743
Web Services
Anonymous Web services use the credentials of the previous Web service call 14269333 Inbound
144
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14380714 Base Bug ID 10556753 Subarea Inbound Special Instructions
Issue Addressed If two calls are made to business services with the CSSEAIDispatchService class within the same component, a crash occurs After Data Mapper is applied, field values are truncated When a WSDL file is generated for an inbound web service, the SBL-EAI-0133 error message appears for each web service method When an inbound web service is used along with session management, when users query for a record that is not in the database, no record is returned and a session token is returned, but when users query for a record that is in the database and the session token is used in this request, no record is retrieved String field lengths are not included in WSDLs that were generated in version 8.1.1.7 Web service calls fail with the "The connection with the server was reset" error message Improves the quality of error messages If an inbound web service is used with session management, an error occurs
14106547 14832139
14072155
Inbound Inbound
14699880
Inbound
14660079
Inbound
14472864
Inbound
11693260 10528258
10601547
Inbound Inbound
Siebel Core - EIM/ Database

Database
14 5
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 13632544 Base Bug ID Subarea Connector. Special Instructions
Issue Addressed Within Siebel Tools, when users click the Apply button to generate DDL SQL for a table that contains two or more CIAIenabled columns, the SQL contains errors When a table is in append mode, DDLIMP processing recreates indexes unnecessarily When custom extensions are deleted, Siebel Tools tries to rename the table
14415526
Utilities
13995107
Utilities
Platform Support
Users experience data transaction losses on the Mobile Web Client 13892979 10597322 OLE DB
Siebel Core Handheld Sync

Handheld Sync
Sync downloads a previouslyextracted database instead of reextracting When line items do not have parent items, Sync Object Manager does not skip follow-on queries for the item With Store-and-Forward Messaging, the Upload Now, Download Later option is enabled and it is not possible to inactivate it Warning messages that are displayed to stop an initial sync are not translated In version 8.1.1, wireless sync experiences many more network errors than in previous versions of the application 14334074 13060395 Session Admin
14026514
13391249
Session Admin
14026544
13595229
Session Admin
13416832
Session Admin
14700152
Settings Admin
146
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14658936 Base Bug ID Subarea Settings Admin Special Instructions
Issue Addressed On the WM 6.5.3 device, the Start/Stop button in the Sync window obscures the horizontal scroll bar
Siebel Core - PIM Integration

CRM Desktop
Some countries are missing from the Country field picklist 14266958 Admin
SSSE
The last occurrence of an unsupported appointment is not synchronized correctly When a recurring appointment is created in the Siebel application, it appears in the correct time slot within Outlook after synchronization, but future occurrences are shifted by one hour 14766759 Calendar
13810633
Calendar
Siebel Core Server BizLogic Rules

Config - Scripting
After version 8.1.1.8 has been installed, the Object Manager crashes Application Object Manager crashes frequently with heap corruption CG Heapsize is not behaving correctly 14705805 ST Engine
14220127
ST Engine
14605326
ST Engine
Integration - Scripting
14 7
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 13681224 Base Bug ID Subarea New eScript Engine Special Instructions
Issue Addressed The GetContactId method does not return the contact ID as a string
Siebel Core Server BizLogic WF

Business Process Framework
When a business service and a task view use different business components, an error occurs when a task is finished With non-transactional tasks, when users click the Previous button, they receive the following error message: "Can't write data without validation (SBL-DAT-60217)" 15977146 10561831 Task Controller
14641009
Task Execution
Config - Rules
Records processed from S_ESCL_STATE whose duration has passed are not processed first When the Condition column length is longer than 30 characters, Workflow Policy Triggers does not create a record in S_ESCL_REQ Within the Workflow Properties Instance Monitor business component, the Property Value field should be able to store 1999 characters 14395165 Workflow Policies
14365074
Workflow Policies
16026562
Workflow Process Execution
Siebel Core Server Infrastructure
148
Table 5.
Issue Addressed
Security
After version 8.1.1.8 has been installed, data is not encrypted correctly 15908699 Data Encryption
Server Infrastructure
Crash.txt does not display the time and date of process crashes The User Login label is inconsistently applied in the Failed Process Diagnostics view The 'CC_Alias' column for the events in the 'list evtloglvl' command does not contain values for all events When the EnableCDA parameter is set to False, it does not take effect Addresses several issues in the Server Infrastructure area After the end of Daylight Saving Time, the Repeating Start Date repeating instance is not correct When users run a command to change a nonexistent evtloglvl, no error message appears 14171186 14400743 Diagnostics & Monitoring Diagnostics & Monitoring 13484137 Logging Subsystem
14585315
14277915
Server ManagerGUI Server ManagerGUI Server Requests
13912219 14024212
14259418
Siebsrvr and Shells
Siebel Core Server OM Frwks

Task UI fails to create service requests on the remote client In the task-based UI, a performance issue occurs when the parent account pick applet is selected 10588576 Task Transaction: Commit Task Transaction: Other
14350262
14 9
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 16010088 Base Bug ID Subarea Task Transaction: Other Special Instructions
Issue Addressed When users create a new record and then query for it, the product displays with empty field names if the fields are based on the S_PROD_INT_LANG join When there are three-level join fields, when users query or pause a task and then resume it, the Parent Product Line field is empty In the Opportunity task-based UI, a conflict occurs with the Position business component
16016275
Task Transaction: Other
14361943
Temporary Storage
Integration Framework
When users sort on the Contact Last Name field, the application hangs 16003200 EBC
Object Manager
The CountRecords business component method produces incorrect SQL statements when connected to an Oracle database Setting the Defer Write Record property to True does not work for CUT Address When records in tables are updated, LAST_UPD, LAST_UPD_BY, and MODIFICATION_NUM are not updated In the task-based UI, users cannot change the values in form applets whose fields are based on the Intersection table 15837793 14593308 Business Components
13554570
Business Components Business Components
11869256
10601872
Business Components
Siebel Core Server OM Svcs

150 Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B
Table 5.
Issue Addressed
Audit Trail
Users cannot customize Audit Trail functionality Join fields within the Opportunity Product business component are not audited 14599122 14782728 10600685 Audit Trail Audit Trail
Object Manager
When business component fields contain the 'ParentFieldValue("<field>") expression, when users create an activity and an opportunity with the task-based UI, after they click Finish, they receive an error message The Query operation fails when bind variable length is greater than 128 Large search specifications that form deep parse trees cause crashes 13511027 Business Services
14755294
Other
13878606
Other
Siebel Core Social

Social
Duplicate contacts are created for new service requests 14468808 User Interface
Siebel Core Tools

Users experience performance issues with the Edit > Server Script and Check Syntax functions 10525104 Task UI Config
Config - Repository
15 1
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 15997159 Base Bug ID 15951861 Subarea Applet and View Configuration Special Instructions
Issue Addressed Within Contacts > Contact List > Contact form applet, when users create a new contact or use an existing contact, click on the MVG, and then click the MVG icon in the Street Address column, the shuttle applet disappears Integrates Siebel Tools online help into Siebel applications The CTRL+Shift+Space keyboard shortcuts are conflicting When users import a large number of SIF files using the Tools > Import from Archive option, the import fails with an error message In version 8.1.1.4, the CRMT Proactive SMS Number Pop Up dialog box freezes
16075658 14611723
14002935 14553247
Check In/Check Out Other
15876629
Tools Error Messages
14735616
14376882
Tools User Interface
Config - Scripting
The application crashes when the WriteRecord method is called If a new null value is passed to the date function, an exception error occurs There is not a way to handle null or invalid parameters in the Date.parse() and new Date() methods PreQuery takes a long time to execute when there is no script 14744364 14396466 13514232 Debugger Script Assist
13032649
Script Assist
15896394
Script Assist
Siebel Core UNIX/Windows

Platform Support
152
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 16078048 Base Bug ID 16028912 Subarea Oracle Enterprise Linux 5 Web Server Special Instructions
Issue Addressed On Linux and UNIX, a memory leak occurs in SSDLOPEN When installing Quick Fixes on AIX and HP-UX, libmod_swe.so is set to zero When "Transfer Encoding: Chunked" is enabled for HTTP version 1.1, the web server does not pass SOAP requests successfully
14580017
13830026
14641837
Web Server
Siebel CRM Desktop

CRM Desktop
Provides proper LOVs to support the fixes provided in Bug 12831330 13115497 Install
Siebel CRM Integration to Oracle Realtime Scheduler

Integration Components
ACR 669: A memory leak occurs after confirm an appointment that has been booked 16094188
Siebel Components
15 3
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 16017131 Base Bug ID Subarea Activity, Shifts, POU, Breaks Updates Special Instructions
Issue Addressed When ACR 484 and ACR 669 have been applied and the Siebel Wireless component group has been enabled, when users create a shift and breaks in the Siebel application and dispatch the activity from Oracle Real-Time Scheduler to the Siebel application, launch Siebel Wireless, navigate to Shifts, and try to edit the shift status to start, the shift changes are not saved and an error message displays ACR 669: The Schedule Date field is empty for POUs and breaks ACR 669: Provides the Siebel Field Service to Oracle Real-Time Scheduler version 2.1 integration
16010472
15984784
Address, Employees, Activities
15975431
Siebel Data Model

Data Model
ACR 758: Changes the data type for the Date fields to UTC date time AIA COM 11.1: Provides an index on S_ASSET (PROD_ID, INTEGRATION_ID, ASSET_NUM) to resolve an issue with high buffer gets AIA COM 3.1: Drilling down on an order in the Siebel application takes a long time AIA COM 3.1: Drilling down on an order in the Siebel application takes a long time 14117291 Global Time Zone Indexes
12974771
11773592
Indexes
11806473
Indexes
154
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14077492 Base Bug ID Subarea Indexes Special Instructions
Issue Addressed The S_ORG_EXT.COVERED_BY and S_ORG_EXT.FBI_FIELD_OFF_ID tables have no foreign key index During the Real-Time Loyalty Accrual process, the SQL executes slowly The S_LOY_TXN table is missing a column for Redemption Flowchart ID Adds new columns to support Mutually Exclusive functionality in campaign load Within service requests, the Description field can only contain 250 characters Within the Opportunities tab, when users navigate to the Opportunities view, click New, create a new record, and click Save, they receive an error message When the Description fields in the Internal Product and Asset Mgmt - Asset business components do not contain the same number of characters, when the SWOrderUpsert web service is invoked to create the asset, the transaction fails List import fails if the import file contains fields that are based on LOVs that are in a different language than the one set for Workflow Manager Provides a schema change to support Bug 13717920 Adds a new column to the S_DCP_URL table to store dynamic emails
14297346
10578907
Indexes
14323597
Schema
14184076
10605670
Schema
13886666
Schema
11704790
Schema
10649966
Schema
14225015
12430648
Schema
15879875 15842866
13717920
Schema Schema
15 5
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14184091 Base Bug ID 12316813 Subarea Schema Special Instructions
Issue Addressed Provides a new column called CAMP_LD_WAVE_ID to populate Load Wave ID in the S_CAMP_LSTDISTR table ACR 764: Adds an Integration ID field to Siebel ATG Profile Mapping When users create an account with more than 50 characters in the Account Name Field, create an opportunity record, associate products and revenue, associate the opportunity to the account, create a forecasting series with aggregation levels, and then generate a forecast, they receive an error message, but when the users remove the aggregation levels from the forecasting series and then regenerate the forecast, no error message appears URL detection fails if a URL contains more than 100 characters FIN Dumpfile creation fails and IBM DB2 and MSSQL imports exit with an error message IBM DB2 and MSSQL exit with an error during the seed_locale import step
14733696
Schema
15974513
14271585
Schema
14184106
10605059
Schema
14459061
Tech Configuration Tech Configuration
14408473
EIM
Importing the VACR744_EIM_Tables_1214201 1.sif file fails The EIM Table Mapping wizard does not work on the S_BNFPLNITM_PAY table 13526686 EIM Table Mappings EIM Table Mappings
15985965
IRM & Converged Repository
156
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14382309 Base Bug ID Subarea Object Tagging Special Instructions
Issue Addressed Duplicate applet web template items appear within the Clinical Subject Status MVG applet The Package Event Check flag is missing in the Package Event Check form applet Packaged functions are not visible in the Meeting Functions list applet After SDF merges, the Applet and View objects are missing list columns and web template items When users create an opportunity, add a function and a function line item to it, navigate to the Substitute column and press F2, the Substitute applet dialog box is missing several columns When users create a quote, create a function, create a subfunction, reserve a function space for the function, add Menu/Split Menu to the function and subfunction, create an order, and create an open check, when users click Post Check, they receive an error message When users create an opportunity, add a function, reserve function space, add a menu, select functions, create a function order, click the Open Day button to display the Which Day? applet, click the picklist in the Property field, select a property, and click OK, the property does not display in the Property field
14392903
Repository Merge for Converged Repository Repository Merge for Converged Repository Repository Merge for Converged Repository Repository Merge for Converged Repository
14392869
14385844
14471422
14408627
Repository Merge for Converged Repository
14397788
Repository Merge for Converged Repository
15 7
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14470938 Base Bug ID Subarea Repository Merge for Converged Repository Repository Merge for Converged Repository Repository Merge for Converged Repository Repository Merge for Converged Repository Repository Merge for Converged Repository Special Instructions
Issue Addressed The Post Day and Void Event Check buttons are missing from the Event Check list applet The Property column is missing from the TNT Generic Property list applet The Search applet is missing within the Orders > Functions view Columns are missing from the Pick Product pick applet within Event Order and Menu Item views Within Property Administration, when users drill down on the Property Name field, navigate to the Menu view, add a menu, and add menu items using the Add Item or New buttons, the Name field is not populated with the new data after users save the record or step off of it The seed data is missing some Web services ACR 525: Errors occur during seed-data import The Multichannel LOV is missing for the Portuguese application Several views are missing within the Product Promotions view ACR 525: The Warranty Claims, Supplier Recovery Claims, and Supplier Recovery Policy screens are not displayed within the Site Map Adds the Clinical tag for master database accounts
14387757
14392377
14386650
14388081
14353743 14281067 14369340 14323099 14301882
Seed Data Merge Seed Tagging Seed Tagging Seed Tagging Seed Tagging
15829770
Tag & Related Issues
158
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14340059 Base Bug ID Subarea Tag & Related Issues Special Instructions
Issue Addressed Within Siebel Financial Services, when users navigate to Admin Product > Product Definition, create a new product or select an existing product, click Validate to navigate to the Configurator view, click Done, and click Validate within the Versions view, the application hangs There are invalid tag records for FINS items Performance issues occur with checking in and checking out using TAGs Users cannot export records from the Product Promotions, Catalog, Category, and Price List applets
14377699 14200084
Tag & Related Issues Tag & Related Issues Tag & Related Issues
14378912
Remote
The default OnAssignProducttoSubAccount method is not working correctly in ADL 15850564 13602083 Routing Rules
Upgrade
Provides a one-step upgrade from Siebel Business Applications version 8.0 to Siebel Industry Applications, version 8.1 14164157 Database
Siebel Documents
Documents
Service request numbers are not populated in merged documents 12856454 Correspondence
Siebel Engineering Installer

Table 5.
Issue Addressed
Install - Configuration
The wrong gateway port is validated during enterprise configuration 13975622 Gateway_Server
Install - Patch Process

When users install version 8.1.1.8 on Windows, some files are not copied SES and SWEAPP installation is very slow 14351462 Patch
14558561
Patch
Install - Server
An error occurs when changes are applied to the S_LOCALE table on a local database The Strong Encryption Pack is missing from version 8.1.1.8 Installing version 8.1.1.8 fails with the OUI-10136 error message Users cannot install version 8.1.1.8 on a single Siebel Server installation Supports native IIS version 7 and above installations because Microsoft Windows Server 2003 is no longer available 14614803 Siebel_Server
14764209 14611533
Siebel_Server Siebel_Server
14761620
Siebel_Server
14753852
Siebel_Server
Install - Tools
On Windows 8, after users install the Oracle database client, configure it, make sure that it is connected to the database, install Siebel Tools, and enter Oracle as the database, when the users navigate to Windows > ODBC Editor, the SSD_default instance points to SQL Server Native Client 10.0, not the Oracle database 16051715 Tools
160
Table 5.
Issue Addressed
Siebel Engineering - Rel Eng

Rel Eng/Build System
In the Korean version of the Sales application, users receive an error message when they log in 14840267 Build System
Release Engineering/ PSX

The Message Type and Product Offer ID labels are missing in Product Offer header applets The Day/Date token is incorrect in the 5 Day Weekly screen and the Print Calendar screen 14381263
12574863
Siebel Financial Services

Claims
Associating an account to a claim updates the non-primary or primary address Users receive an error message when they navigate to Help > About Record 14526193 14098634
14372166
Group Policies
Buttons do not display within Configurator views 14534542
Industry XML Framework

When users upgrade from version 8.1.1.2 to version 8.1.1.7, VBCs that are based on the CSSFABCVREC class do not work 14191451
16 1
Table 5.
Issue Addressed
Integrations
Inactivates invalid repository objects 14844314
Siebel Life Sciences

Clinical Programs/ Protocols
Within Site Management, when users create a site with the No Subject Info Flag set to Y, drill down on the Site Number field, navigate to the More Info tab and enter date, navigate to the Subjects tab, create a new subject, apply an active version, select the subject record, and delete it, when users navigate back to the More Info tab, all of the data in the fields is deleted except for the information in the Initiated Date and Terminated Date fields 14710753
Clinical Trip Report

Within the CRF Tracking tab, the New button is enabled for approved trip reports 13995112
Handheld Cfg
The NewCall method should work in any applet or business component that is based upon a copy of the Contact business component 14085566
Message Broadcasting
162
Table 5.
Issue Addressed Addresses several issues with Notifications behavior: Colors should not be used in the Notifications list, there is no hyperlink from the list, the list should only show user-specific notifications, notifications should be removed once a report is opened, and failed reports do not display Report Generation notifications do not display at the top of the screen Open UI: Report generation notifications are not filtered
14513736
14513759
OPENUI_MOB
When users add a new contact in the Contacts screen, enter an address in the Contact Details applet, and then save the record, they receive the following error message: "City is a required field. Please enter a value for the field." Attendee calls are not shown within Contacts > Calls The mobile ePharma Object Manager and CGM are not in Open UI mode by default On the iPhone, when users change the orientation of the phone, a black tab displays on the navigation bar 15837162 PHMobile
14762370 14813294
14761391
PHMobile PHMobile
14772410
14696652
PHMobile
16 3
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14396420 Base Bug ID Subarea PHMobile Special Instructions
Issue Addressed When users navigate to the Administration Communication > Message Broadcast screen, create a new message, open the Message Summary pane and keep it open until the next polling, after polling is completed, the new message does not display in the open summary pane, but if the summary pane is reopened, the message does display Within Admin - Communications > Message Broadcast, when users create a new message with normal severity and then include the H tag to make part of the message high-severity, the message does not display in the text colors for high severity Pharma Mobile Object Manager parameters are not set to the correct values In the Spanish version of the application, the tooltip text on the Notification icon does not display in Spanish In the Spanish version of the application, the tooltip text on the Notification icon does not display in Spanish The Attendee Call Status field information does not change after an account call is submitted The About Record button is misaligned
15872623
14837803
PHMobile
15850138
PHMobile
14750090
14738111
PHMobile
14755796
PHMobile
14772441
14671753
PHMobile
14755783
14738204
164
Table 5.
Issue Addressed The EnableOpenUI, MobileApplication, and EnableSIFocusTracking parameters are not set properly for the ePharmaMObjMgr_ENU and CGMObjMgr_ENU Object Managers The OT, RN, and UN properties are missing within Message Broadcasting The OT, RN, and UN properties are missing within Message Broadcasting Signatures captured on the mobile application are not visible within Siebel Life Sciences
15900880
15927476
14619524
Site Management
When the Clinical Subject Web service is called for over 145 continuous messages, a Max_Open_Cursors error message occurs RF 970: The LS Clinical Protocol Get Sites web service does not return site details 15830115 14465295
16065271
Subjects
ACR 712: The Safety Study ID field is not displayed within Protocol List > More Info applet ACR 758: When users copy a record, click the Schedule button, enter the date and click OK, they receive an error message ACR 758: No error popup window appears when an active Sales Visit template is removed from a site 14769146
14382129
14343380
16 5
Table 5.
Issue Addressed ACR 758: When users enter a value in the Schedule Date field that is less than the value in the Date of Birth field, the error message refers to the Screen Date field instead of the Schedule Date field ACR 758: A memory leak occurs in Function Accruals A memory leak occurs within Siebel Clinical business service functions
15843910 15835191
14825865
Siebel Loyalty
Member Administration
During member merge, the last transaction of a deactivated member Merging fails when two members are enrolled in the same promotion Merging fails when two members are enrolled in the same themebased promotion 12427464
14639209
15927894
14639209
Member Services
When a member enrolls in a membership and uses a currency code other than USD, when the membership is cancelled, the Refund Amount currency code defaults to USD 12966616
Other
Import libraries display a single record multiple times and no scroll bar is displayed Bulk point updates do not work in non-ENU environments 14212938
14580770
166
Table 5.
Issue Addressed
Promotions
Provides a new view called Promotion List that displays the list of promotions associated with a flowchart 13793309
Redemptions
When a redemption to buy two products is initiated through the task-based UI, when users select a product and then select another product, within the Activities and Points Summary screen, the amount in the Total Amount field does not reflect the sum of the two products selected When users perform a redemption flow with points to pay conversion in the task-based UI, the Total Amount field reflects a zero value, but when users navigate to the last screen of the redemption flow, the fields reflect the correct value If the name in the Loyalty Member field contains more than 27 characters, the Loyalty Redemption Service get_spcQuote method fails with the SBL-DAT-00235 error message 13000928
14409808
10593474
Transaction Engine
End-dated promotions are not evaluated in the Simulated Calls - Accrual and Redemption Transactions screens When the Loyalty Engine creates new transactions, it uses the organization of the user who is running the Loyalty Engine 14699984
14807737
16 7
Table 5.
Issue Addressed When a promotion that contains attributes has been inactivated, an error message occurs during batch processing For order-based promotions, the attributes are not reset for each order The redemption and cancellation engine process does not work consistently
14697162
14786178
Siebel Public Sector

eService
When a new standard control has been added to the Applet Web Template item in the PUB GOV eService Account Quick Links applet, the applet does not navigate to a the PUB GOV Contact Case List View (eService) applet 14090993
Other
Open UI: MVGs appear blank The Disable UI Personalization system preference is not included 14664356 14569233
Siebel Reports
Reports Actuate Infra
In version 8.1.1.3, if users search for an employee whose last name contains an umlaut, Actuate reports retrieve all of the employees 13650028 Connected Client
168
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 15897525 Base Bug ID 13726869 Subarea Connected Client Special Instructions
Issue Addressed In version 8.1.1.3, if users search for an employee whose last name contains an umlaut, Actuate reports retrieve all of the employees
Reports BI Publisher Apps

Users cannot export BI Publisher report templates using Application Deployment Manager In Partner Relationship Management portal, the Selected Records flag is ignored When QF0744 has been applied, passwords display in clear text within encrypted environments Invoking GenerateBIPReport changes the locale With BIP reports, the default language is not set in the Generate Report pane Open UI: The applet title is missing in the Report pane Report execution does not consider the locale set in User Preferences > Report Parameters and defaults to the default object manager locale 14513606 Error Messages
14670979
Error Messages
14736110
Error Messages
14331102 14736291
Error Messages Localization
14757147 14652801
14639325
Localization Localization
Reports BI Publisher Infra

ACR 719B: Query strings are not passed in as part of XML When a user performs a dynamic query in an applet before they execute a report, the query string is not passed to the report as a value in the XML 13480115 16053578 16053578 Connector Connector
16 9
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 15897534 Base Bug ID 14812706 Subarea Connector Special Instructions
Issue Addressed When users generate a report with a parameterized template, they receive the following error message: "An error occurred while generating data. Make sure that the query for bookmark is valid." (SBL-RPT50515) Resizes and realigns labels and text boxes When users click the Report icon when BI Publisher has not been set up, the error message does not state that the BIP host is missing or that the application failed to connect to the BI Publisher Server When reports have custom names, the names are not passed during message broadcasting Implements parameterized reports for Open UI Support BI Publisher scheduled reports for Open UI Task ID is not populated in the My Reports view Users can add reports to any organization Visibility that is set in the primary integration object is not considered in the secondary integration object Visibility that is set in the primary integration object is not considered in the secondary integration object The Report Access field is not a MVG in list and form applets
11653381 11704034
11794693
Connector Connector
14487540
Connector
15938498 15896124 15891645 13345332 11731283 16050002
Connector Connector Connector Connector Connector
16050002
Connector
12996456
Error Messages
170
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14513237 Base Bug ID Subarea Error Messages Special Instructions
Issue Addressed When the active position has been changed, BIP report execution fails Default BIP calendar reports do not work when predefined queries or search specifications are used Error messages for nonparameterized reports are not translated
14286402
Error Messages
13440259
Error Messages
Siebel Server Remote

File System
The Field Read Only Filed business component user property does not work for the Attachments business component 13604520 10500527 File System Manager
Remote
Within Site Map > Administration - Siebel Remote > Remote System Preferences, the Lockout Period field displays days instead of minutes Sync fails with the "error putting ODBC into transaction mode" error message When Quickstart has been enabled, users cannot log in if they have attempted to log in with the incorrect password The audit trail is not in sync with the Mobile Client server 14296442 12604178 Other
14538054
Sync Client
14796224
Sync Client
10567120
Sync Server
Siebel Travel & Transportation

Accounts
17 1
Table 5.
Issue Addressed Within the Japanese application, the address and date formats are not correct
Event Checks
When users create a quote, create a function, assign an order to the function, refresh the quote, navigate to the order number and open a trial check, navigate back to the order and update the GTD number, the Actual Number field does not reflect the value that was set in the GTD Number field For Package Event Checks, the Display Name field does not display in the Line Item Guest and Accounting views Within Opportunity > Quote, when users add a function, associate a function space and reserve it, create an order, and then try to add a line item within the Event Check > Functions view, they receive an error message When users create a quote within the Opportunity screen, apply a meeting package that does not contain sleeping rooms, apply a meeting package that does contain sleeping rooms, create an order, and then create an open check, package event checks and normal event checks do not generate and an error message displays Event checks can be generated for properties that are outside of the user's visibility 15907236
14609401
14519026
14747535
14560377
172
Table 5.
Issue Addressed Within the Event Check screen, when users click the Adj. Check Report button and then click the Event Revenue Summary Report button, the Output and Locale fields do not default to the BIP settings When an event check is generated in open mode, the following error message displays: "The event check for this order is already open."
14501959
Event Templates
Duplicate child line items are created when using the Apply Quote template When users update the Package Each/Package Item Price fields with child line items with a quantity of more than one, create a property-specific event template, create a function, add the Package Each/Package Item value as function line items, and then verify the quantity in the Extended Quantity field, the quantity is not correct Within Event Templates > TNT SHM Specific Templates More Info My View, when users click the New button in the list applet to add a property to the new record, they receive an error message When users create an event from a quote, the quantity of menu line items is not correct in Event Templates 15915919 15838264
14370543
14555454
14554659
Functions
17 3
Table 5.
Issue Addressed Users are allowed to copy line items for products that have been created for dates in the future to quotes that have Arrival Date and Departure Date values that are before the Start Date value for the product Within Quotes, when users create functions, add line items to the functions, create a function order for the first function that they added, and click the Add button to add the rest of the functions, all of the functions are added to the event order, but the line items are not carried over The Copy Function button does not work for read-only quotes Core functions are not copied to different quotes When users delete hierarchical functions, the functions still remain in quotes Extended Net Price values for line items are not in sync between the Quote screen and the Function screen The error messages that display when the Start and End Date fields are validated do not consider the Start and End Date information of the parent function Users cannot copy functions from quotes that have been actualized
14740497
14632823 14785409 14784830
14784159
11929272
14537375
174
Table 5.
Issue Addressed The Menu or Package Quantity fields are not updated if the values for Projected, GTD, or Actual are changed from the Functions screen Users cannot calculate tax and service charge using the Reprice All button in Line Items applets The turntime conflict error message displays even when there is not a conflict When users attempt to change the value in the Backup Space field, an error occurs
14783481
15910315
14775570
15907184
Line Items
Within Quotes > Line Items view, subfunctions display after their associated function is deleted 14779023
Opportunities
Within Opportunity > Room Blocks > Room Blocks Line Item view, when users create room block line items, the date is not autopopulated Constraints on parent opportunities affect opportunities in other applications 14518429
14765113
Orders
When users add a child function and then a parent function and add the functions to an order, the subfunction line items are added twice 14806258
Orders/Line Items
17 5
Table 5.
Issue Addressed When an order is associated to a quote, line items are not carried over from the quote to the order
Other
ACR 575: Function Space Diary LOVs have untranslated values Within Quotes > Functions > Line Items view, critical items are not autobooked and users need to click Auto Book to book each asset 13397843 14518619
Pricing & Discounting

In Function Line Item view, incorrect revenue is generated for Package Per Person line items The Adjust Meeting Package Price menu option is missing within the Quote > Room Blocks > Negotiation Rate Manager view 14334035
14384872
Quote
Actualization workflow process does not actualize all of the eligible quotes When users override an action, the Apply Package functionality does not work as expected When the Day Number or Date fields are changed in parent functions, the changes are not reflected in the subfunctions 15907257
14001120
14386191
13090315
176
Table 5.
Issue Addressed When users create a quote for a property, navigate to the Quotes > Tracking Managers view, verify that the Event Manager 1 and ET Manager fields are blank, create a new record in the Quote Turnover view, and update the value in the Turnover To field to any user from the list, when user navigate to the Quotes > Tracking Managers view, the Event Manager 1 and ET Manager fields reflect the value set in the Turnover To field Users cannot book function spaces within scenarios when slots are available When users create a quote, add function details, child functions, and grandchild functions, add line items to all of the functions, click Reprice All, and then try to add Package Per Person information to the grandchild functions, they receive an error message Users can create a four-level hierarchy (great grandparent, grandparent, parent, and child) when the Detail flag is checked Subfunctions do not display when they are copied from another subfunction Hierarchical line items are not added as expected My Quotes calendar displays an empty view After users cancel functions, the Need Refresh flag is not checked
14615233
14402355
14555883
14465395
14518867 14580437 14732653
14402355
17 7
Table 5.
Issue Addressed When users create a quote, navigate to the Quote Meeting Package view, add a meeting package that has function line items (Menu), non-function line items (Menu), and room blocks, change the action to Override, and apply the meeting package with or without attendees, when users navigate to Quote > Functions, select any core function to verify the function line items, for Menu, only Menu header is applied and the child line items are missing The Quote form applet does not display correctly in the More Info and Line Items views Within Quotes > Functions > Line Items view, when users delete the Posting Rhythm, Applies To, and Package field information from a non-core line item, the package name of the line items is not deleted When a subfunction is cancelled, the Quote Revenue field still displays the line items price for the cancelled function Within the Quotes > Functions > Line Item view, users cannot add items with the Package Event type When users copy non-function line items, the Applies To and Posting Rhythm information is also copied
14626668
13990842
14710899
14058495
13737247
14621487
178
Table 5.
Issue Addressed When users create a quote, apply a meeting package that contains function line items and non-function line items, navigate to the Quote > Functions view, select a function, and copy it, the Applies To and Posting Rhythm information is also copied
Reports - Hospitality
BI Publisher does not support Cluster Visibility for the Siebel Hospitality application When users generate a report from within the Accounts view, they receive an error message stating that the field does not exist Within the Orders screen, when users select an event order, select an Events Order report, and generate a report, they receive the BIP Engine Failed error message 14782893
14597798
14639927
Service Charges
When the Billable flag is set to N, the Net Extended Price field does not consider taxes and service charges for line items 14596020
Taxes
Tax and service charges are not calculated correctly for packages 14785287
Time Shift
Within the Time Shift view, original and new applets are not in sync for non-function line items and room blocks 13839435
17 9
Table 5.
Issue Addressed
Siebel UI Framework
AX/HI Web UI
When users expand a parent position, child position records are missing The GotoView method does not write records to the database The Life Sciences Pharma calendar view crashes when users toggle within the application A memory leak occurs with eligibility benefits In Arabic and Hebrew applications, the text boxes do not read from right to left With Internet Explorer 8 running on Windows 7, the SmartScript options render incorrectly after the user refreshes the browser When users drill down on the Find Results applet, the application freezes and does not display results When the HTTP header length is greater than 10999 characters, when users drill down to a specific record from anywhere in the application, they receive the following error message: "We detected an error which may have occurred for one or more of the following reasons: The applet field with name "s_6_2_19_1" does not exist." (SBL-UIF-00289) 15989475 ActiveX Controls
16072572 13082592
14786140
ActiveX Controls ActiveX Controls
16188951 14404972
16028912
ActiveX Controls ActiveX Controls
14750354
ActiveX Controls
14766080
Task Based UI
14337535
Web Client Auto Server
Open_UI
180
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 15964283 Base Bug ID Subarea Framework Special Instructions
Issue Addressed Role=application is set on the main page div, and so assistive technology reads all of the content as an application When users click Next within a SmartScript screen, the screen stays busy for over 30 seconds Screen readers do not read third-level tabs within accounts Within the Call Center application, when users navigate to the Contact list applet and press CTRL+Insert+; within the Landmarks dialog box, the Contact applet form appears instead of the Contact list applet Screen readers do not read the Currency Code, Exchange Date, or Amount labels in the Revenue Field popup window Screen readers do not read labels in the Technical Support, About Record, or About View popup windows Within the Call Center application, when users navigate to the Contact home page, invoke the Pick Account popup window, tab to the Find dropdown list, open it, and then press the Down arrow to navigate between the values, the focus does not always move to the values Within the Call Center application, when users navigate to the Opportunity form applet, press CTRL+Alt+N, and tab to the Last Name field, assistive technology reads the field as read-only when it can be edited
15897532
14801507
Framework
14658241 14471773
Framework Framework
14492195
Framework
14576915
Framework
14628272
Framework
14627819
Framework
18 1
Table 5.
Issue Addressed Within Call Center, when users navigate to the Contact form applet, open the Address MVG and press Tab, assistive technology reads the Show Selected button incorrectly When users create a new contact within the Contact list applet and then press the Tab key until they reach the Student field, the screen reader does not read the Student or Veteran fields The focus order in form applets should be from column to column but is from row to row Assistive technology does not read the language of an application (WCAG 2.0 and W3C) When users navigate to the third-level views within an application, assistive technology reads all of the screens that the user navigated through before reading the third-level screen The Date picklist is not invoked when users click F2 within a popup window When users click the arrow key within Contacts, the focus does not move to the View tab After a file is attached, the focus moves to the page header Within Accounts > List, when users focus on the form applet and press the Tab key to navigate through the applet, the focus does not move forward from the State and Country fields
16010401
14584519
Framework
16025770
Framework
14690654
Framework
14708363
Framework
14690548
Framework
14603195
Framework
16027714 14590218
Framework Framework
182
Table 5.
Issue Addressed The Send Email, Send Page, Send Fax, and Send Wireless dialog boxes do not have their applet names appended, so users do not hear the applet names when they focus on the Send button Users cannot navigate pick applet grids using Aria key sequences In the Public Sector application, when users navigate to Service Provider > More Info, press Alt+Q to initiate a query, and tab through the fields, assistive technology only reads the column names and headers for the edit fields Within Partners > Partner list, when users focus on the form applet, focus on the Territory MVG, press F2, and then press the Down arrow key, assistive technology does not read values in the Territory drop-down list The focus gets trapped in the grid of list applets Accessibility: Within the Public Sector application, when users navigate to the Cases list applet within the Cases screen, create a new record, click on the Last Name MVG in the Case form applet, and then press Tab when the MVG opens, assistive technology does not read anything, and when users press Tab again, assistive technology reads the column header Accessibility: When users tab from the Address field, the focus lands on the Address bar
14613954
Framework
14723311
Framework
16066080
Framework
16082733 14791065
Framework Framework
14837643
Framework
18 3
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 16268061 Base Bug ID 14837643 Subarea Framework Special Instructions
Issue Addressed Accessibility: When users tab from the Address field, the focus lands on the Address bar Within the Pubic Sector application, when users navigate to Contacts > Photographs and focus on the Image applet, and press the Tab key, the assistive technology reads that the field is not labeled instead of reading New File Accessibility: Modifies the description text for check boxes in read-only mode Accessibility: There are no captions for option buttons in Sort Order dialog boxes Accessibility: Previous screen tabs are read along with a current screen's tabs Accessibility: There are unlabeled screens within SmartScripts Accessibility: Using the right arrow key does not move the focus to the next view tabs Accessibility: Within the Public Sector application, within Group Suspects > All Group Suspects, when users focus on the list applet, press CTRL+Alt+Q or Alt+Q to initiate a new query, press CTRL+Alt+S or Alt+S to execute the query, and then try to save the query with a different name, the dialog box does not contain a Query Name edit field or the Available Queries list
14681458
Framework
14584519
Framework
14627871
Framework
14706141
Framework
14560268
Framework
14559114
Framework
14493457
Framework
184
Table 5.
Issue Addressed When users refresh the screen, the assistive technology reads the labels on the first-level and second-level navigation tabs again Accessibility: Within the Public Sector application, when users focus on the first-level navigation view bar and then press the arrow keys to navigate through the application, assistive technology reads the names of the Calendar, Service, and Contacts tabs twice Accessibility: Within the Public Sector application, when users navigate to Cases > All Cases, focus on the form applet, and navigate through the applet using the arrow keys or the HTML quick keys, assistive technology does not read the names of the drop-down lists Accessibility: Within the Public Sector application, when users navigate to Medications > All Medications, focus on the form applet, focus on the Approximate Cost field, click the Down arrow key and press Enter on Graphic Calculator, the focus remains on the Approximate Cost field Accessibility: Keyboard shortcuts do not work
14363613
Framework
14513600
Framework
14494143
Framework
14502125
Framework
18 5
Table 5.
Issue Addressed Accessibility: Within the Public Sector application, when users navigate to Cases > All Cases, press CTRL+Alt+J to invoke technical support and then press Enter on the Close button or press Enter on the Resize button, no actions occur and the users must press F5 to refresh the page Accessibility: There are no Select Record links to select another record Accessibility: Sort icons are not visible and the shortcut keys for showing and hiding sort icons do not work Accessibility: Pressing the Tab key does not move the focus to the fields in the Query Assistant popup window Accessibility: When users press Tab to navigate to the New File button, the label disappears and a false tag is announced Accessibility: The Toolbar Landmark option is not available in the Landmark list When users create a quote, they cannot drill down on the Quote Name or Quote Number fields When the calculator is closed and then reopened, it does not display the first digit The Calendar screen does not load When users invoke the Calendar popup window from first-level or second-level popup windows
14508809
Framework
14392919
Framework
14559125
Framework
14245592
Framework
14385740
Framework
15962737
Framework
15897541
14735928
Framework
15995242 16016678
15990334
Framework Framework
186
Table 5.
Issue Addressed Within the Quote screen, when users drill down on quotes to the Quote - Browse Catalog view, not all of the applets associated with the view display Custom manifests do not work as expected Within the Opportunity list applet, when users drill down on a record, navigate to the Assignment Skill tab, and click on Query Mode in the Skill Item applet, they receive an error message Within the Accounts screen, when users navigate to the Contacts screen tab, the tab is not highlighted The line items applet does not display properly within the Quote - Assets Catalog view Within the Quote - Assets > Catalog view, line item applets do not display correctly With Firefox, when users navigate to the Opportunity home page, add an applet, click the Calculator icon in the Revenue field, click the Calculator icon in the Amount field, enter a value, click Use, and then close and reopen the calculator, users have to doubleclick to select the digits Provides general CSS and tangerine theme fixes Fixes some style problems in the toolbar, the task-based UI, the Report pane, and in SmartScript layout
15897515 15897539
15849129 14585047
Framework Framework
15897537
14742993
Framework
14758722
14709290
Framework
15897521
Framework
15897519
14754153
Framework
14824745 15897531
14792946 14782682
Framework Framework
18 7
Table 5.
Issue Addressed When users open a popup window, assistive technology reads the X button as Enter, not Close Provides support for a parameter that can indicate if the base functionality needs to be cancelled and override the return value accordingly Open UI: CTIGoToView takes 30 seconds to open Open UI: Phone numbers are prefixed with ? Open UI: Users cannot update amount values in second-level popup windows Within the Account list applet, when users navigate to Last Records, the last record is highlighted, "Last 10 records" displays, and the form applet shows "Last Record," but when users press F5 to refresh, the record information in the form applet changes to "9 from Last" Scrolling in the Site Map does not scroll the background When CSS is added to a theme, SiebelApp.ThemeManager.addR esource() replaces the theme instead of adding to it With Internet Explorer 9, the Search field does not work within the Site Map When users search in list applets, an "undefined console" error message appears Values added in the Description field in Public Notes are not visible
15922785
15898181
Framework
15897523 16053676 15897524
14771527
Framework Framework
14705286
Framework
15897512
14724072
Framework
14755782 15947605
14744813
Framework Framework
16278000
Framework
15897527
14804537
Framework
14465544
Framework
188
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 16067213 Base Bug ID 14755382 Subarea Client Special Instructions
Issue Addressed When users click the Sync button, they receive the "cache not found" error message Editing a child applet causes the application to hang The Cancel button does not work within Contact > Best Times > Address pick applet When users scroll to the last record in a list applet, the cursor goes into busy mode When the Sync button is clicked when there is no network connection, the incorrect error message displays
16067203 16067206
14682058 14735529
Client Client
16067214
14732248
Client
16067210
14755450
Client
OPENUI_MOB
Multi-select dialog boxes do not work properly Within Menu > Columns Displayed, the Selected Column dialog box behaves inconsistently Within the Sales application, when users navigate to the Accounts view and click the + icon to create a new account, the new account filed displays encoded data When the Field Read Only Field business component user property is defined for a field, the field does not become readonly Within the Order list applet, when users select an order, click the Edit button, and click Find within the Account pick applet, no query results display and the debug console shows a 'null' error 14839257 14758721 14672560 14724316 Framework Framework
14813286
14778142
Framework
16278359
Framework
14824735
14823048
Framework
18 9
Table 5.
Issue Addressed Within the Contacts screen, when users click on Query Assistant, enter data, and click Go, the results display in the form applet but the list applet is blank No busy cursor displays after users click the New, Edit, Save, or Cancel buttons IDS_SWE_MOBILE_TAP_TO_CR EATE is not translated to Traditional Chinese Opening a map on a form increases the open-window count In grid applets, when users create a record with Phone Number, Email, or URL fields, when the users save the record, the fields become blank, and the values display in the form applet but not in the grid Users are allowed to clear text from read-only pick lists Within the CG mobile application, when users navigate to Return Order, create a new return order, click the New button within Order line items, click on the Product picklist, and then click the Discount Percentage drop-down list, no busy cursor displays while the pick applet is loading On the iPhone, users cannot select call duration from dropdown lists JQMFormRenderer.prototype.Set ControlValue does not pay attention to the HTML Display Mode parameter in Siebel Tools
15832798
Framework
15876201
Framework
14813289
14802086
Framework
14838726
Framework
15854952 15843313
14826707
14824741
14805207
190
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 14813305 Base Bug ID 14769032 Subarea Special Instructions
Issue Addressed When users click on a drop-down list, LOV values with special characters are added to the Select menu There is no busy cursor to indicate that a picklist is loading When users enter invalid data in a pick field, the pick applet launches with only the header information (Pick Title, Find, Starting With) When two forms (parent and child) are open in editable mode and users click the Cancel button on one of the forms, the buttons on the other form disappear
14813308 14839256
14750321 14738448
14813291
14797619
Portal Framework
When a session is active for longer than four hours, performance degrades When users add an attachment to a service request that contains a toggle applet, an error occurs In version 8.1.1.7, the Back button does not work within Internet Explorer 14713267 Config Repository Other
10569855
14353506
SWSE Server Infrastructure
SI Web UI
In version 8.1.1.8, users cannot attach files that are already open in other programs In version 8.1.1.8, when the Auto Query mode has been set, when users navigate through account screens, some applets display in EditList mode The Applet_ChangeFieldValue event fires when there is not change in a field value 14460136 Attachments
14703903
Queries
14156187
STD:Javascript
19 1
Table 5.
Resolved Bugs in Siebel Fix Pack 8.1.1.10 Bug ID 16236627 Base Bug ID 16000960 Subarea UI Behavior Special Instructions
Issue Addressed When a parent window is closed, the Calendar and Calculator icons do not close The eCommunications Object Manager crashes when the ReconfigureCxProd method is invoked in the Quote Item List Applet applet In the Hebrew application, menu items appear from left to right When users personalize applets that are based on the main business component in a business object, the views associated with those applets do not appear When users query in a list that contains a form applet, navigate to another screen and then return to the list, garbage characters appear
14165389
UI Behavior
14598294 14677467 12768910
UI Behavior UI Behavior
14394947
UI Behavior
Instructions for Bug 13717920

Navigate to the Bug 13717920.zip file, unzip the file, and apply the .sif file using the instructions in the setup document.

1 2
Add a configuration parameter called AutoLoadDriver to the CTI configuration, and set the value to TRUE. Add a new button called Setup Hotelling in the CTI toolbar.
Note the following information: When you want to use hoteling with the agent's browser proxy enabled, you need to set AutoLoadDriver to FALSE. When agents log into the Siebel application, the driver will not load automatically. Only the Setup Hoteling button will be enabled, and agents need to input the hostname in the edit box, keep the focus in the edit box, and click the Setup Hoteling button. This will set up hoteling based on the hostname that the agent put in, and load the driver or drivers. This will enable the Login button.
192
Under Open UI, when AutoLoadDriver is set to FALSE, the @ClientIP may not work if the hostname is a non-LAN hostname.

Use the following procedures to implement this fix:
To edit the UCM Account Source Data and History business component 1 2 3
In Siebel Tools, select the UCM Account Source Data and History business component. Select the Business Address multivalue link, and unset the Inactive property. Select Multi Value Field, and unset the Inactive property for the following fields.

SDH City SDH Country SDH Postal Code SDH State SDH Street Address
Compile the business component to the SRF.
To edit the UCM Contact Source Data and History business component 1 2 3
In Siebel Tools, select the UCM Contact Source Data and History business component. Select the Business Address multivalue link, and unset the Inactive property. Select Multi Value Field, and unset the Inactive property for the following fields:

SDH City SDH Country SDH Postal Code SDH State SDH Street Address
Compile the business component to the SRF.
To edit the UCM Account DeDup Source Data List Applet applet 1
Within Siebel Tools, select the UCM Account DeDup Source Data List Applet applet.
19 3
Select the List list, select the following list columns, and update the corresponding values: Name City Country Postal Code State Street Address Field SDH City SDH Country SDH Postal Code SDH State SDH Street Address UCM Account Address Source Data and History Mvg Applet MVG Applet
Compile the applet to the SRF.
To edit the UCM Contact DeDup Source Data List Applet applet 1 2
Within Siebel Tools, select the UCM Contact DeDup Source Data List Applet applet. Select the List list, select the following list columns, and update the corresponding values: Name City Country Postal Code State Street Address Field SDH City SDH Country SDH Postal Code SDH State SDH Street Address UCM Contact Address Source Data and History Mvg Applet MVG Applet
Compile the applet to the SRF.
NOTE: After you have performed these procedures, you must restart the Siebel Server.
194
Siebel Maintenance Release Guide, Version 8.1.1.10, Rev. B Oracle Welcomes Your Comments
Instructions for Bug 14775938 and Bug 14846565

1
Add a new macro for Parameter Values with the following values: UIPhone. Represents the phone number that agent clicked. Example: [Command: MakeCallToUIPhone] DeviceCommand = "MakeCall" Hidden = "TRUE" CmdData = " MakeCallToUIPhone" . [CmdData: MakeCallToUIPhone] AttachContext = "TRUE" Param.CallNotifyText = "Call from {@UserName}..." Param.PhoneNumber = "{@UIPhone:Lookup} . .
Add the following parameter: CallFromUICommand = MakeCallToUIPhone
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.
19 5
Siebel Maintenance Release Guide, Version 8.1.1.10, Rev. B Oracle Welcomes Your Comments
196

MR Guide 81110 Rev B PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

MR Guide 81110 Rev B PDF

Enviado por

Direitos autorais:

Formatos disponíveis

Siebel Maintenance Release Guide

Version 8.1.1.10, Rev. B March 2013

Quick Fixes Included in Siebel Fix Pack 8.1.1.10

Enhancements and Updates in Siebel Fix Pack 8.1.1.10

Configuration Instructions for Enhancements and Updates

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Instructions Instructions Instructions Instructions Instructions Instructions Instructions

for for for for for for for

Siebel Fix Pack Installation Instructions

Resolved Bugs in Siebel Fix Pack 8.1.1.10

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Oracle Welcomes Your Comments

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Siebel Maintenance Release Guide, Version 8.1.1.10, Rev. B

How To Use This Guide

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Siebel Maintenance Release Guide, Version 8.1.1.10, Rev. B

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Whats in This Guide

Release Notes for Siebel Fix Pack 8.1.1.10

Iexplore.exe Causes Siebel Web Client Installation to Hang

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Workaround: Make sure that Iexplore.exe is not running in Task Manager.

Whats New in This Revision

Quick Fixes Included in Siebel Fix Pack 8.1.1.10

Base Bug ID 14472864 10588167 13888514 13090315 14596020

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Base Bug ID 14461301 14504343

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

13514232 14142983 13252249 14247734 14537389 14560377 14537375 14569957 14569957

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Base Bug ID 10477346 16065271 14415526 15834186 14504343 14612437 14578317

14350262 14156187 16053676 16278359 14688411 14688411

16463536 16288826 16094279 16304760 14581341 14370058 14688411 14737937

14764754 14731031 14777402 14662629

14687736 14671753 14761391 14696652 14731980 14738111 14825865 14812706

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

14688204 14801507 14771548 14742707 14735928 14760638

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Enhancements and Updates in Siebel Fix Pack 8.1.1.10

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Siebel Incremental Repository Merge

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Updated Siebel Repository Files

Updated Siebel Sample Database

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Siebel Mobile Applications

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

ACR 643: Commerce Automation and Response Action Framework

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Additional Information and Documentation

ACR 652: Enhanced Product Promotions and Promotion Groups

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

Additional Information and Documentation

ACR 669: Siebel Field Service to Oracle Real-Time Scheduler Integration

ACR 724: Siebel Social Media Integration

Siebel Maintenance Release Guide Version 8.1.1.10, Rev. B

ACR 740: Siebel Process Failure Diagnostics