MR Guide 8117 Rev B

Siebel Maintenance Release Guide
Version 8.1.1.7, Rev. B April 2012
Copyright 2005, 2012 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be errorfree. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Contents
Release Notes for the Siebel 8.1.1.7 Fix Pack Whats New in This Revision 8 11 16 14 7
Quick Fixes Included in the Siebel 8.1.1.7 Fix Pack Enhancements and Updates in Version 8.1.1.7
Instructions for ACR 575 16 Configuration Instructions for ACR 575 Seed Data 18 Lists of Values 18 System Preferences 19 New Repository Objects 19 Changed Repository Objects 20 Business Components 28 Business Objects 42 Enabling Diary Configurable Icons 42 Copying Configurable Icons 48 Configuring the Application 49 Instructions for ACR 719B 49 Instructions for ACR 731 55 Instructions for ACR 750 58 Instructions for ACR 762 62 Instructions for ACR 802 69 Instructions for ACR 839 71
Configuration Instructions for Enhancements and Updates

18
Siebel Fix Pack Installation Instructions
80
85
Siebel Fix Pack Installation Overview 81 Installing the Siebel Fix Pack on Microsoft Windows Installing the Siebel Fix Pack on UNIX 90
Configuring Slipstream Patch Installation 95 Postinstallation Tasks for the Siebel Server 96 Postinstallation Tasks for the Web Server 97 Postinstallation Tasks for High Interactivity Clients 97 Postinstallation Tasks for Supporting Additional Languages Uninstalling Siebel Fix Packs 99
98
Resolved Change Requests

Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel Siebel
101 102
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack
Apps - Customer Order Management 102 Apps - Data Quality 105 Apps - Field Service 106 Apps - Handheld Client 107 Apps - Marketing 108 Apps - Multichannel Technologies 108 Apps - Oracle Customer Hub 109 Apps - PRM 110 Apps - Sales 110 Apps - Search & Knowledge Management 111 Apps - Self Svc: ADF 112 Apps - Service 112 Apps - Territory Management 112 Apps - UCM 113 Charts 113 Communications & Energy 113 Consumer Goods 114 Core - EAI 115 Core - EIM/Database 117 Core - Handheld Sync 118 Core - PIM Integration 119 Core - Server BizLogic Rules 122 Core - Server BizLogic Script 122 Core - Server BizLogic WF 123 Core - Server Infrastructure 124 Core - Server OM Frwks 124 Core - UIF Client 125 Core - Unix/Windows 127 Core - zSeries 128 CRM Integration to Oracle Realtime Scheduler 128 Data Model 128 Documents 129 Engineering - Release Engineering 129 Life Sciences 129
Siebel Siebel Siebel Siebel
Loyalty 133 Reports 135 Server Remote 141 Travel & Transportation
142
Oracle Welcomes Your Comments
148
Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B
April 2012
NOTE: This guide documents the Quick Fixes, enhancements, instructions for enhancements, and bugs fixed in the Siebel 8.1.1.7 Fix Pack. For information about what was provided in the Siebel 8.1.1.1 through Siebel 8.1.1.4 Fix Packs, see Siebel Maintenance Release Guide, Version 8.1.1.x. For information about what was provided in the Siebel 8.1.1.5 and Siebel 8.1.1.6 Fix Packs, see Siebel Maintenance Release Guide, Version 8.1.1.5 and Siebel Maintenance Release Guide, Version 8.1.1.6. To access these guides, from within My Oracle Support, navigate to the Knowledge tab, and search for Article ID 880452.1. This guide includes the following topics: Release Notes for the Siebel 8.1.1.7 Fix Pack on page 7 Whats New in This Revision on page 8 Quick Fixes Included in the Siebel 8.1.1.7 Fix Pack on page 11 Enhancements and Updates in Version 8.1.1.7 on page 14 Configuration Instructions for Enhancements and Updates on page 16 Siebel Fix Pack Installation Instructions on page 80 Resolved Bugs in the Siebel 8.1.1.7 Fix Pack on page 102 Oracle Welcomes Your Comments on page 148
Release Notes for the Siebel 8.1.1.7 Fix Pack

The following section describes known issues with the Siebel 8.1.1.7 Fix Pack, as well as any applicable workaround information. NOTE: It is recommended that you apply Siebel 8.1.1.7 QF0703 (Bug ID 13695168) if you are using Oracle BI Publisher with the Siebel 8.1.1.7 Fix Pack.
Issues with Oracle Business Intelligence Publisher Integration

Product: Siebel Reports Component: Reports BI Publisher - Infra Subcomponent: Connector Product Version: Siebel 8.1.1.7 Bug 13528720: The Duration field is missing from the Report business component.
Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B
Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B Whats New in This Revision
Bug 13570979: Custom Name appears twice in the Report Output applet. Bug 13603930: The My BI Publisher Reports menu label was incorrectly changed. Bug 13528628: Unnecessary fields display in the Template applet. Bug 13604628: The Schedule Report menu item was incorrectly changed.
Workaround: Apply Siebel 8.1.1.7 QF0703 to resolve this issue, using the following procedure:
1 2 3
Within Siebel Tools, navigate to the XMLP Integration project, and lock it. Import the BIP_8117FP_Extension.sif file using the overwrite mode. Compile the SRF.
Search Functionality Not Working with OSES 11.1.2 After German Language Fix
Product: Siebel Apps - Search & Knowledge Management Component: Search - Oracle SES Subcomponent: Indexing Product Version: Siebel 8.1.1.7 Bug ID: 13559725 The fix for a German-language issue is not compatible with SES 11g and breaks basic search functionality. Workaround: Apply Siebel 8.1.1.7 QF0701 to resolve this issue. NOTE: For a comprehensive listing of all Siebel 8.1 Release Notes, see Siebel Release Notes on My Oracle Support (Article ID 557191.1).
Whats New in This Revision

Table 1 describes the changes in this version of the documentation. Table 1. Topic Release Notes for the Siebel 8.1.1.7 Fix Pack on page 7 Enhancements and Updates in Version 8.1.1.7 on page 14 Resolved Bugs in the Siebel 8.1.1.7 Fix Pack on page 102 Instructions for ACR 750 on page 58 Revised this topic. Whats New in Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B Description Clarified the import mode in the procedure for applying 8.1.1.7 QF0703 and added the Bug ID for the QF. Corrected incorrect version number for ACR 699.
Table 1. Topic
Whats New in Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B Description Added a new procedure for the Clinical Trip Report Business Component (Modified). Added required configuration instructions for this bug, and a caution that users should not perform the procedure if they have already installed the Siebel 8.1.1.6 Fix Pack and have performed the procedure for Bug 12757714.
Instructions for ACR 839 on page 71 Instructions for Bug 13003564 on page 145
How To Use This Guide

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

NOTE: The following table includes only the Quick Fixes included in the Siebel 8.1.1.7 Fix Pack. For information about Quick Fixes included in Siebel 8.1.1.1 through Siebel 8.1.1.4, see Siebel Maintenance Release Guide, Version 8.1.1.x on My Oracle Support. For information about Quick Fixes included in Siebel 8.1.1.5, see Siebel Maintenance Release Guide, Version 8.1.1.5 on My Oracle Support. For information about Quick Fixes included in the Siebel 8.1.1.6 Fix Pack, see Siebel Maintenance Release Guide, Version 8.1.1.6. To access these guides, from within My Oracle Support, navigate to the Knowledge tab, and search for Article ID 880452.1. Siebel Quick Fix releases are developed to address immediate critical issues for specific customers, and can be installed on top of Fix Packs. Quick Fixes address a small number of defects, and the fixes are typically rolled into the next available Fix Pack for wider distribution to the Siebel Business Applications customer base. Testing for Quick Fixes is focused and is usually limited to verifying that the fix works on the specific platforms that the affected customer is running.
Table 2.
Quick Fixes Included in Version 8.1.1.7 Fix Request ID/Bug ID 10602141 10587344 12768536 13078962 10598080 10600732 10604265 12811808 13260213 13407108 11831498 12318058 12608701 12724391 12732696 12921815 Quick Fix Version 8.1.1 WM5 [21112_14 QF0156 QF01CP QF01CQ QF02BV QF02CJ QF02CQ QF02CS QF02CT QF02CU QF2203 QF2204 QF2207 QF2208 QF2209 QF2211 Merged Into Fix Pack 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7
Change Request ID/ Base Bug ID 10602136 10587343 12577313 12937764 10598010 11869400 10604196 12570179 10558365 12772458 11818894 12312702 13419996 12733277 12807436 13419996
Fix Pack Base 8.1.1 WM5 [21112_14] 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] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215]
11
Table 2.
Quick Fixes Included in Version 8.1.1.7 Fix Request ID/Bug ID 12757030 12856680 12865401 12869363 12888652 13242025 13242164 13420013 13415880 12577231 12566947 12944899 13384875 13085632 13375871 12915223 10606139 10606139 12313396 12723709 12737165 12926026 12795350 12805266 12866175 12889120 12827015 12883388 Quick Fix Version QF2212 QF2212 QF2212 QF2212 QF2212 QF2213 QF2213 QF2213 QF2213 QF03AY QF03BI QF03BP QF03BQ QF03BS QF03BV QF1303 8.1.1.3 WM5 [21219_4] 8.1.1.3 WM5 [21219_4] QF0421 QF0433 QF0438 QF0440 QF0443 QF0446 QF0448 QF0449 QF0450 QF0451 Merged Into Fix Pack 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7
Change Request ID/ Base Bug ID 12756997 12857901 12876544 12876539 12906967 12962036 13090315 13419996 13419996 12577313 12566908 10598010 13384850 13043868 12604183 12896102 10606138 10606138 12318676 10605987 12736823 12577313 12795298 12805219 12802129 12889047 12826991 10529645
Fix Pack Base 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.2 [21215] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 [21219] 8.1.1.3 WM5 [21219_4] 8.1.1.3 WM5 [21219_4] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225]
12
Table 2.
Quick Fixes Included in Version 8.1.1.7 Fix Request ID/Bug ID 12922188 13384866 13096035 12720131 11858120 12798488 12945668 12766445 12643211 12823043 12838039 12726874 12865331 12857923 12934784 12848581 13008052 12942915 12790188 12931623 12829467 13039780 13384865 12937408 13105264 12780386 13324301 13076148 13026022 Quick Fix Version QF0452 QF0454 QF0458 8.1.1.4 WM5 21225_1 QF0502 QF0514 QF0515 QF0517 QF0520 QF0521 QF0522 QF0523 QF0526 QF0527 QF0530 QF0531 QF0532 QF0533 QF0536 QF0537 QF0538 QF0539 QF0547 QF0548 QF0549 QF0550 QF0551 QF0556 QF0557 Merged Into Fix Pack 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7
Change Request ID/ Base Bug ID 10558365 13384850 12801963 10583904 11830300 11717572 12937764 12577313 10537307 12705438 12833238 12711326 12865043 10585340 11767223 12822135 10534318 10558365 12750196 12629343 12800053 12879239 13384850 12937371 11682517 12772458 10605987 12567732 13019417
Fix Pack Base 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 [21225] 8.1.1.4 WM5 [21225_1] 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.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]
13
Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B Enhancements and Updates in Version 8.1.1.7
Table 2.
Quick Fixes Included in Version 8.1.1.7 Fix Request ID/Bug ID 12964888 13436951 13505777 13114020 12873861 13106410 13101755 13422290 13406439 Quick Fix Version QF0560 QF0563 QF0564 QF0565 QF0566 QF0601 QF0602 QF0604 QF0611 Merged Into Fix Pack 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7 8.1.1.7
Change Request ID/ Base Bug ID 10595170 13391431 10591152 10598444 12810197 13085829 13081720 12772458 12839398
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.6 [21233] 8.1.1.6 [21233] 8.1.1.6 [21233] 8.1.1.6 [21233]
Enhancements and Updates in Version 8.1.1.7

Table 3 lists the enhancements and updates provided in Fix Pack version 8.1.1.7. NOTE: For a list of enhancements provided in the Siebel 8.1.1.1 through 8.1.1.4 Fix Packs, see Siebel Maintenance Release Guide, Version 8.1.1.x on My Oracle Support. For a list of enhancements provided in the Siebel 8.1.1.5 Fix Pack, see Siebel Maintenance Release Guide, Version 8.1.1.5 on My Oracle Support. For a list of enhancements provided in the Siebel 8.1.1.6 Fix Pack, see Siebel Maintenance Release Guide, Version 8.1.1.6. To access these guides, from within My Oracle Support, navigate to the Knowledge tab, and search for Article ID 880452.1.
Table 3.
Enhancements and Updates in Version 8.1.1.7 Feature Enhancement or Certification Description Provides enhancements to Siebel Hospitality Diary functionality. Instructions for ACR 575
Feature Enhancement or Certification Number ACR 575
ACR 698 ACR 699 ACR 701
Certifies AIX 7.1. Certifies Oracle Enterprise Linux 6.1 64-bit. Certifies IBM DB2 v10 for z/OS.
14
Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B Enhancements and Updates in Version 8.1.1.7
Table 3.
Enhancements and Updates in Version 8.1.1.7 Feature Enhancement or Certification Description Provides the following enhancements: Improved upload functionality for multilingual reports Mobile client synchronization of report templates Ability to schedule parameterized reports Allows the UI applet sort order to be preserved in report output Report business service enhancements Parameterized reporting enhancements
Feature Enhancement or Certification Number ACR 719B
Instructions for ACR 719B ACR 731 Supports Signature Capture using the CIC component on the Microsoft Windows 7 platform. Instructions for ACR 731 ACR 750 Provides SOAP and EJB fuctionality for Siebel Application Integration (SAI). Instructions for ACR 750 ACR 761 ACR 762 Provides a Data Quality sync switch. Ports SonGo Web services to the iSales application. Instructions for ACR 762 ACR 802 Provides Bulk Administration enhancements and redemption concurrency functionality. Instructions for ACR 802 ACR 839 Provides the following enhancements: Allows the geographical details of a site to be captured. Web services to provide information about protocols, sites, and site visits when they are created in CTMS to other applications that are used in biotechnology and pharmaceutical companies.
Instructions for ACR 839
15
Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B Configuration Instructions for Enhancements and Updates
Configuration Instructions for Enhancements and Updates

This topic contains configuration instructions for some of the enhancements and updates provided in version 8.1.1.7. For configuration instructions for the enhancements and updates provided in the Siebel 8.1.1.1 through 8.1.1.4 Fix Packs, see Siebel Maintenance Release Guide, Version 8.1.1.x on My Oracle Support. For configuration instructions for the enhancements and updates provided in the Siebel 8.1.15 Fix Pack, see Siebel Maintenance Release Guide, Version 8.1.1.5. For configuration instructions for the enhancements and updates provided in the Siebel 8.1.1.6 Fix Pack, see Siebel Maintenance Release Guide, Version 8.1.1.6. To access these guides, from within My Oracle Support, navigate to the Knowledge tab and search for Article ID 880452.1. NOTE: It is only necessary to perform the configurations in the following section if you want to implement the ACRs that they are for. Perform the instructions described in the subtopics listed below after you install the current Siebel Fix Pack, as described in Siebel Fix Pack Installation Instructions on page 80. NOTE: For more information about activities performed in Siebel Tools, including importing archive (.sif) files, see Using Siebel Tools and Configuring Siebel Business Applications. For more information about activities performed in the Siebel application, see Siebel Applications Administration Guide and related books. These guides are available on the Siebel 8.1 Bookshelf on OTN at http:// www.oracle.com/technology/documentation/siebel.html. This topic contains the following subtopics: Instructions for ACR 575 on page 16 Instructions for ACR 719B on page 49 Instructions for ACR 731 on page 55 Instructions for ACR 750 on page 58 Instructions for ACR 762 on page 62 Instructions for ACR 802 on page 69 Instructions for ACR 839 on page 71

Use the following procedure to implement ACR 575. NOTE: Before you configure ACR 575, you must have configured ACR 450, ACR 488, ACR 494, and ACR 495.
1 2
Log into Siebel Tools, query for the TNT SHM Function Space Diary and TNT SHM Compact Function Space Diary projects, and lock them. In the Object Explorer, click on the Applet object.
16
3 4 5 6
Click on any record on the right-hand side, and query for the TNT SHM Function Space Diary applet. Right-click and lock the applet. Click the + sign to expand the applet. Click on the Applet User Prop subobject, and create the following new user properties and values.

Name: TNT Show Move Popup Applet Value: N
Name: Disable Right Click Menu Item 1 Value: Assign to Category
Name: Disable Right Click Menu Item 2 Value: Assign to Specific Space
7 8 9
Query for the TNT SHM Compact Function Space Diary applet. Right-click and lock the applet. Click the + sign to expand the applet.
10 Click on the Applet User Prop subobject, and create the following new user properties and values:

11 Query for the TNT SHM Function Space Diary Total Availability Applet applet 12 Right-click and lock the applet. 13 Click the + sign to expand the applet. 14 Click on the Applet User Prop subobject, and create the following new user properties and values:

17
15 Compile the TNT SHM Function Space Diary, TNT SHM Compact Function Space Diary, and TNT
SHM Function Space Diary Total Availability Applet objects to the SRF.
Configuration Instructions for ACR 575

Use the instructions in the following section to configure ACR 575.
Seed Data
1
Navigate to List of Values Explorer > List of Values - Types. List Of Values Explorer > List Of Values - Types Replication Level All Multilingual TRUE Translate TRUE
Type TNT_SHM_GNTAX_FS_TY PE_TOGGLE
Lists of Values
Type TNT_SHM_GNTAX_FS_TYPE_TOGGLE TNT_SHM_GNTAX_FS_TYPE_TOGGLE TNT_SHM_GNTAX_FS_TYPE_TOGGLE TNT_SHM_GNTAX_FSD_DSP_TOGGLE Display Value All Specific Space Special Location Inventory Status LIC ALL SPECIFIC_SPACE SPECIAL_LOCATI ON 17 Language Name English American English American English American English American Order 1 2 3 10 Active TRUE TRUE TRUE TRUE Translat e TRUE TRUE TRUE TRUE
18
System Preferences
System Preference Name TNT CMT Special Location Pref ACR495 Space Hold ACR450 Change Diary Start Date TNT CMT Configurable Icons GntAXCtrl:Color Display Toggle TNT CMT Func Spaces Cache Size TNT CMT Memory Utilization System Preference Value Y Y N Y INVENTORY_STATUS 1000 Y Description
New Repository Objects

All new repository objects created for the Diary enhancements have been compiled into SIF files. To import these SIF files, use the following procedure.
1 2 3 4
Uncompress the 8.1.1.2_Hospitality_Enhancements.zip file to create the 8.1.1.2_Diary_Porting folder. Create a log folder in the \REPPATCH\8.1.1.2_Diary_Porting\REPOSITORY directory. Rename the Picklist folder to Pick List. Run the import. bat file to import the following:From the 8.1.1.2_Hospitality_Diary_Enhancements.zip folder, import the following SIF files using the Merge option:
Applets:

TNT SHM Copy Function Option/Overbook Popup Applet TNT SHM Diary Add Function Parameter Popup Applet TNT SHM Diary Copy Function Parameter Popup Applet TNT Proposed Function Space Pick Applet TNT Move Function Popup Applet
Business components:

TNT SHM Add Copy Function Parameter VBC TNT Move Function VBC TNT Configured Space
Commands

TNT SHM Add Function Popup TNT SHM InvokeAssignDayPopup
19
Picklists:

TNT Quote PickList TNT SHM FSD Function Space Type PickList TNT Proposed Function Space Picklist
Symbolic strings:

SBL_TNT_ADD_FUNCTION SBL_TNT_COLOR_DISPLAY_BY SBL_TNT_COPY_SUB_FUNCTIONS SBL_TNT_DEFAULT_DIARY_COLOR_DISPLAY_INFO SBL_TNT_FUNC_SPACE_COL_SIZE SBL_TNT_NEG_RENTAL SBL_TNT_SEL_RESERV_TO_MOVE_SIA
Classes:

CSSBCVRecMoveFunction CSSSWEFrameTNTMoveFuncPopup CSSSWEFrameTNTSIAAssocList
Changed Repository Objects

All changes to existing repository objects for the Diary enhancements are listed below. Configure these changes manually.
Applets
The following tables describe the applets associated with ACR 575.
20
TNT SHM Function Space Diary Table 4. TNT SHM Function Space Diary Applet TNT SHM Function Space Diary Class Project BusComp Title Type HTML Number Of Rows Standard CSSSWEFrameSHMAxDiary TNT SHM Function Space Diary TNT SHM Gantt AX Date Time Interval PopUp VBC
Table 5. Applet User Properties New/ Modified New New New New New New New New New New Name Ignore Case Sensitivity Item Time Display Toggle Time Label 10 Item Time Display Toggle Time Label 11 Item Time Display Toggle Time Label 12 Item Time Display Toggle Time Label 13 Item Time Display Toggle Time Label 14 Item Time Display Toggle Time Label 15 Item Time Display Toggle Time Label 16 Item Time Display Toggle Time Label 17 Item Time Display Toggle Time Tooltip 17 Value Y Account Name Calculated Guaranteed Calculated Function Start Date Calculated Function Day Calculated Decision Date Calculated Total Catering Revenue Calculated Function Space Calculated Inventory Status Calculated Booking Set Up Tip;Booking Tip Function Name;Booking Tear Down Tip;Booking Tear Down Tip 2 Existing Value: 3 Existing Value
Modified
Max X Pages
21
Table 5. Applet User Properties New/ Modified Modified New New New Modified New Name Max Y Rows Per Page Number of Rows to Overlap Transient Suite Field Y-Axis Drill Down Enable Y-Axis Width TNT Same Time Frame - Show Move Popup Applet Value 25 1 Is Transient Suite Y Function Space Column Size Y Existing Value: 150 Existing Value Existing Value: 15
22
Table 6. Controls
HTML Icon Map/HTML Type Text
New/Modified New
Name/Field Function Space Type Toggle Function Space Type - Query
Caption Function Space Type SBL_FUNCTION_SPACE_TYPE1009100818-A2P
Runtime RunTime= True
Existing Value
New
Go To Go To
Go To SBL_GO_TO-1004233041-4MM HTML Height: 560 HTML Width: 960 HTML Height: 456 Existing HTML Width: 960
Modified
GanttChart
Modified
Booking Color Toggle Booking Color Toggle Schema
Color Display By SBL_TNT_COLOR_DISPLAY_BY
RunTime= True
Booking Color Toggle
Table 7. Applet Method Menu Item New/ Modified New Command TNT SHM InvokeAssignDayPopup Menu Text Position Assign SBL_ASSIGN-1004224603-02B Position 6
New
TNT SHM Add Function Popup
Add Function SBL_TNT_ADD_FUNCTION
Applet Web Template Item NOTE: Add the newly-added control to display in the UI.
23
TNT SHM Compact Function Space Diary Table 8. TNT SHM Compact Function Space Diary TNT SHM Compact Function Space Diary Class Project Bus Comp Title Type HTML Number of Rows Standard CSSSWEFrameSHMAxCompactDiary TNT SHM Compact Function Space Diary TNT SHM Gantt AX Date Time Interval PopUp VBC
Table 9. Applet User Properties New/Modified New New New New New New New New New Modified Modified New New Name Ignore Case Sensitivity Item Time Display Toggle Time Label 10 Item Time Display Toggle Time Label 11 Item Time Display Toggle Time Label 12 Item Time Display Toggle Time Label 13 Item Time Display Toggle Time Label 14 Item Time Display Toggle Time Label 15 Item Time Display Toggle Time Label 16 Item Time Display Toggle Time Label 17 Max X Pages Max Y Rows Per Page Number of Rows to Overlap Transient Suite Field Value Y Account Name Calculated Guaranteed Calculated Function Start Date Calculated Function Day Calculated Decision Date Calculated Total Catering Revenue Calculated Function Space Calculated Inventory Status Calculated 2 25 1 Is Transient Suite 3 15 Existing Value
24
Table 9. Applet User Properties New/Modified New Modified New Name Y-Axis Drill Down Enable Y-Axis Width TNT Same Time Frame Show Move Popup Applet Value Y Function Space Column Size Y 150 Existing Value
Table 10. Controls

New/ Modified New HTML Icon Map/HTML Type Text Existing Value New
Name/Field Function Space Type Toggle Function Space Type Query
Caption Function Space Type SBL_FUNCTION_SPACE_TYPE1009100818-A2P
Runtime RunTime = True
Modified
GanttChart
HTML Height: 560 HTML Width: 960
Existing HTML Height: 560 Existing HTML Width: 950
New
Go To Go To
Go To SBL_GO_TO-1004233041-4MM
RunTime= True
Modified
Booking Color Toggle Booking Color Toggle Schema
Booking Color Toggle
Table 11. Applet Method Menu Item New/ Modified New Command TNT SHM InvokeAssignDayPopup Menu Text Position Assign SBL_ASSIGN1004224603-02B Position 6 Comment New
25
TNT SHM Gantt AX Admin Form Applet Table 12. TNT SHM Gantt AX Form Applet
Class Project BusComp Title Type HTML Number Of Rows
CSSFrame TNT SHM Function Space Diary TNT SHM Gantt AX Admin Specialized Controls FSD Administration Standard
Table 13. Controls

New/ Modified New HTML Icon Map/HTML Type Text
Name/Field Color Display By Color Display Toggle
Caption Color Display By SBL_TNT_COLOR_DISPLAY_BY
Runtime Set Runtime = TRUE
Comment
New
HTML Form Section4
Default Diary Color Display Information SBL_TNT_DEFAULT_DIARY_COLOR_DISPLAY_ INFO
FormSection
Runtime = TRUE
26
TNT SHM FSD User Preferences Table 14. TNT SHM FSD User Preference
CSSFrameBase User Preferences User Preferences Function Space Diary Standard
Table 15. Controls

HTML Icon Map/ HTML Type Text
New/ Modified New
Name/Field TNTCMTDiary/ Function Space Column Size TNT CMT Diary/ Function Space Column Size
Caption Function Space Column Size SBL_TNT_FUNC_SPACE_COL_SIZE
Runtime
Comment New
New
TNTCMTDiary/ FunctionSpaceType TNT CMT Diary/ Function Space Type
Function Space Type SBL_FUNCTION_SPACE_TYPE1009100818-A2P
Text
Runtime = TRUE
Modified
Booking Color Schema TNT CMT Diary/ Booking Color Toggle Schema
Text
Modified It was mapped to the Diary/Booking Color Toggle Schema field.
27
TNT SHM Function Assoc Applet Table 16. TNT SHM Function Assoc Applet
Class Project Bus Comp Title Type HTML Number of Rows
CSSSWEFrameTNTSIAAssocList TNT SHM Function TNT SHM Function Add Functions Association List
Existing Class: CSSSWEFrameList Assoc
TNT SHM Function Order Mvg Applet Table 17. TNT SHM Function Order Mvg Applet
CSSSWEFrameOrderMvg TNT SHM Function Order Entry - Orders Orders MVG
Table 18. Controls Name/Field Add - Shuttle Caption Add > HTML Icon Map/ HTML Type Method Invoked AddOrder Existing Value .AddRecords
Business Components
The following tables describe some of the business components associated with ACR 575.
28
Internal Product
Table 19. Business Component User Properties New/ Modified New Name TNT Room Search Spec Value ([Type] = LookupValue('PRODUCT_TYPE', 'Indivisible') OR [Type] = LookupValue('PRODUCT_TYPE', 'Configured') OR [Type] = LookupValue('PRODUCT_TYPE', 'Category') OR [Type] = LookupValue('PRODUCT_TYPE', 'Suite')) Comments Diary Performance Issue
29
TNT SHM FSI Booking

Table 20. Fields New/ Modified New Calculated Value/Join Column [Function Start Time] + [Function Duration] * 60
Field Name Function End Time
Calculated True
DTYPE_xxx Miscellaneous DTYPE_TEXT
New
Function Space Event Check Status Quote Number
Function Space Event Check STATUS_CD S_DOC_QUOTE. QUOTE_NUM
DTYPE_TEXT
New
DTYPE_TEXT
New New
TNT Proposed Function Date TNT Proposed Function End Time TNT Proposed Function Space TNT Proposed Function Space Id TNT Proposed Function Start Time TNT Same Function Space Function Space Event Check Id Function Space Order Item Id
True True
DTYPE_TEXT DTYPE_TEXT
New
True
DTYPE_TEXT
New
True
DTYPE_TEXT
New
True
DTYPE_TEXT
New
True
DTYPE_BOOL
New
Order Item TNTX EVT_CHECK_ID Order Item ROW_ID
Text Length = 15 D_TYPE_ID Text Length = 15 D_TYPE_ID
New
30
Table 21. Function Space Event Check Join New/Modified New Join Specification Name Event Check Id Destination Column ROW_ID Source Column Function Space Event Check ID Table S_INVOICE Alias Function Space Event Check Outer Join Flag True
Table 22. Order Item TNTX Join New/Modified New Join Specification Name Par Row Id Destination Column PAR_ROW_ID Source Column Function Space Order Item Id Table S_ORDERITM_TNTX Alias Order Item TNTX Outer Join Flag True
Table 23. Order Item Join New/Modified New Join Specification Name Function Id Function Space Id Destination Column FUNCTION_ID PROD_ID Source Column Function Id Function Space Id Table S_ORDER_ITEM Alias Order Item Outer Join Flag True
31
User Preferences
Table 24. Fields
New/ Modified New Field Name TNT CMT Diary/ Booking Color Toggle Schema TNT CMT Diary/ Function Space Column Size TNT CMT Diary/ Function Space Type 4TRUE Calculated TRUE Required Predefined Value Picklist TNT FSD Color Schema PickList True 150 Type DTYPE_TEXT
New
DTYPE_NUMBER
New
TNT SHM FSD Function Space Type PickList
DTYPE_TEXT
Table 25. Pick Maps Parent Field TNT CMT Diary/ Booking Color Toggle Schema TNT CMT Diary/ Function Space Type Sequence BC - ) Field Picklist Field Value Constrain No Clear
Value
32
TNT SHM Quote Template Pick BC

Table 26. Fields New/Modified New Field Name Account Calculated Value/Join Column S_ORG_EXT.Name DTYPE_xxx Miscellaneous DTYPE_Text Text Length = 100 New New Account Id Arrival Date TARGET_OU_ID S_QUOTE_TNTX. ARRIVAL_DT New Departure Date S_QUOTE_TNTX. DEPARTURE_DT New Post As Name S_QUOTE_TNTX. ALIAS_NAME New Property Property.NAME DTYPE_TEXT Text Length = 100 DTYPE_TEXT Text Length = 100 New Quote Number QUOTE_NUM DTYPE_TEXT Text Length = 30 New Status STAT_CD DTYPE_TEXT Text Length = 30 New TNT CMT Status LIC LookUpName("QUOTE_STATUS" , [Status]) DTYPE_TEXT DTYPE_DATE DTYPE_ID DTYPE_DATE
Table 27. Property Join New/Modified New Join Specification Name Property Id Destination Column PAR_ROW_ID Source Column Primary Organization Id Table S_ORG_EXT Alias Property Outer Join Flag True
33
Table 28. S_ORG_EXT Join New/Modified New Join Specification Name Account Id Destination Column PAR_ROW_ID Source Column Account Id Table S_ORG_EXT Alias S_ORG_EXT Outer Join Flag True
TNT SHM Gantt AX Date Time Interval PopUp VBC

Table 29. Fields
Pick List Post Default New/Modified New Field Name Function Space Type Query Go To Calculated Value/ Join.Column Calculated = TRUE Pre Default TNT SHM FSD Function Space Type PickList Force Active Link Spec Required Immediate P.C. Immediate Post Change = TRUE DTYPE_xxx Miscellaneous DTYPE_TEXT
New
Calculated = TRUE
DTYPE_TEXT
Table 30. Pick Maps Parent Field Function Space Type - Query BC - ) Field Function Space Type - Query Picklist Field Value
Table 31. User Properties New/Modified New New New Modified Modified Name Activation Field 1 Activation Field 2 Default Function Space Type Scale Unit Major Scale Unit Minor Modified Value Go To Function Space Type - Query Specific Space 1;1;2;1;4;.75;8;1;16;2;32;1;64;1;128 ;1;256;1 1;1;2;1;4;.75;8;1;16;2;32;1;64;1;128 ;1;256;1
34
Table 31. User Properties New/Modified Modified Modified Modified Modified Name Segments Per Page Major Segments Per Page Minor Units Per Segment Major Units Per Segment Minor Modified Value 1;1;2;1;4;1;8;1;16;1;32;2;64;30;128;8;256;8 1;8;2;1;4;24;8;24;16;48;32;8;64;30;128;8;256 ;8 1;7;2;1;4;1;8;0.5;16;0.25;32;28;64;1 ;128;1;256;7 1;1;2;1;4;0.0416666666666666;8;0.02083333 3333333334;16;0.010416666666666666;32;7; 64;1;128;1;256;7 Y
New
X-Axis Drill Down Enable
TNT SHM Gantt AX Admin Specialized Controls

Table 32. Fields Pick List New/ Modified New New Post Default Field Name Booking Color Toggle Schema Color Display Toggle Pre Default TNT FSD Color Schema PickList TNT FSD Color Schema PickList Force Active Link Spec Required Immediate P.C. Required = TRUE Required = TRUE DTYPE_xxx Miscellaneous DTYPE_TEXT DTYPE_TEXT
Table 33. Pick Maps Parent Field Booking Color Toggle Schema Color Display Toggle BC > Field Booking Color Toggle Schema Color Display Toggle Picklist Field Value Value
35
TNT SHM Function

Table 34. Fields DTYPE_xxx New/Modified New Field Name TNT CMT Quote Status ReadOnly View Flag for Function Screen Calculated Value IIF([Quote Status]=LookupValue ('QUOTE_STATUS', 'Actual') OR [Quote Status]=LookupValue ('QUOTE_STATUS', 'Lost') OR [Quote Status]=LookupValue ('QUOTE_STATUS', 'Lost/Turndown') OR [Quote Status]=LookupValue ('QUOTE_STATUS', 'Cancel'), 'Y', 'N') Miscellaneous DTYPE_TEXT
Table 35. User Properties New / Modified New New New New New New New New New New New Name Copy Function Field 11 Copy Function Field 12 Copy Function Field 13 Copy Function Field 14 Copy Function Field 15 Copy Function Field 16 Copy Function Field 17 Copy Function Field 18 Copy Function Field 19 Copy Function Field 20 Copy Function Field 21 Value "FN_TYPE_ID", "Function Type Id" "FN_TYPE", "Function Type" "SETUP_STYLE", "Setup Style" "EXP_NUM", "Expected Num" "GUARNT_NUM", "Guaranteed Num" "SET_NUM", "Set Num" "NEG_RM_RENTAL", "TNT CMT Negotiated Room Rental" "FLOW_FLAG", "Flow Flag" "DO_NOT_POST_FLAG", "TNT CMT Do Not Post Flag" "NOISE_FLAG", "Noise Flag" "FUNCTION_SPACE", "Active Function Space"
36
TNT SHM Compact Room Rel VBC

Table 36. Fields New/ Modified Modified Calculated Value/ Join.Column IIf([HasChildren] = '1', IIf([Expanded]='1', 206, 207), IIf([Parent Room Id] = 'ORPHANED', 0, 210)) IIf([Room Backup Required]='Y', 221, 0) DTYPE_xxx Existing Value IIF([HasChildren] = '1', IIF([Expanded]='1', 206, 207), IIF([Parent Room Id] = 'ORPHANED', 205, 210)) if([Room Backup Required]='Y', 221, 205) Miscellaneous DTYPE_TEXT
Field Name Hierarchy Bitmap Id
Modified
Room Backup Required Id
DTYPE_TEXT
TNT SHM Compact Function Booking VBC

Table 37. Fields
Force Active Link Spec Required Immed. P,C DTYPE_xxx Miscellaneous DTYPE_TEXT [Function Space Tip] + [Guaranteed Tip] + [Peak Rooms Tip] + [Total Catering Revenue Tip] DTYPE_TEXT
New/ Modified New New
Field Name Active Function Space Addl Tip
Calculated Value/ Join.Column
Existing Value
New New New
Backup Space Total Catering Revenue Total Catering Revenue Field Name Tip IIf([Total Catering Revenue] IS NOT NULL, LookupValue('TNT_SHM _TOOLTIP_OBJECTS', 'Total Catering Revenue') + ": " , "") [Total Catering Revenue Field Name Tip] + [Total Catering Revenue] + IIF([Total Catering Revenue] IS NULL,"","\r\n") IIF([Booking Type] = LookupValue('TNT_SHM _BOOKING_TYPE','Back up'), [Active Function Space], [Backup Space])
DTYPE_TEXT DTYPE_TEXT
New
Total Catering Revenue Tip
DTYPE_TEXT
New
Function Space Tip Field Value
DTYPE_TEXT
37
Table 37. Fields

Force Active Link Spec Required Immed. P,C DTYPE_xxx Miscellaneous DTYPE_TEXT
New/ Modified New
Field Name Function Space Tip
Calculated Value/ Join.Column [Function Space Field Name Tip] + [Function Space Tip Field Value] + IIF([Function Space Tip Field Value] IS NULL,"","\r\n") IIF([Function Space Tip Field Value] IS NOT NULL, LookupValue('TNT_SHM _TOOLTIP_OBJECTS', 'Backup Space/Pri Space Link') + ": " , "") IIF([Guaranteed] IS NOT NULL, LookupValue('TNT_SHM _TOOLTIP_OBJECTS', 'Guaranteed') + ": " , "") [Guaranteed Field Name Tip] + [Guaranteed] + IIF([Guaranteed] IS NULL,"","\r\n")
Existing Value
New
Function Space Field Name Tip
DTYPE_TEXT
New
Guaranteed Field Name Tip
DTYPE_TEXT
New
Guaranteed Tip
DTYPE_TEXT
New Modified
Peak Rooms Peak Rooms Field Name Tip IIF([Peak Rooms] IS NOT NULL, LookupValue('TNT_SHM _TOOLTIP_OBJECTS ', 'Peak Rooms') + ": " , "") [Peak Rooms Field Name Tip] + [Peak Rooms] + IIF([Peak Rooms] IS NULL,"","\r\n") [Function Name Tip] + [Quote Name Tip] + [Function Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Meal Period Tip] + [Sales Manager Tip] + [Event Manager Tip] + [Expected Num Tip] + [Addl Tip] [Function Name Tip] + [Quote Name Tip] + [Function Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Meal Period Tip] + [Sales Manager Tip] + [Event Manager Tip] + [Expected Num Tip]
DTYPE_INTEGER DTYPE_TEXT
Modified
Peak Rooms Tip
DTYPE_TEXT
Modified
Booking Tip Business Type
DTYPE_TEXT
38
Table 37. Fields

New/ Modified Modified
Field Name Booking Tip - Event Manager
Calculated Value/ Join.Column [Function Name Tip] + [Quote Name Tip] + [Business Type Tip]+ [Function Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Meal Period Tip] + [Sales Manager Tip] + [Expected Num Tip] + [Addl Tip]
Existing Value [Function Name Tip] + [Quote Name Tip] + [Business Type Tip]+ [Function Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Meal Period Tip] + [Sales Manager Tip] + [Expected Num Tip] [Quote Name Tip] + [Business Type Tip]+ [Function Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Meal Period Tip] + [Sales Manager Tip] + [Event Manager Tip] + [Expected Num Tip] [Function Name Tip] + [Quote Name Tip] + [Business Type Tip] + [Function Type Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Meal Period Tip] + [Sales Manager Tip] + [Event Manager Tip] + [Expected Num Tip]
Modified
Booking Tip Function Name
[Quote Name Tip] + [Business Type Tip]+ [Function Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Meal Period Tip] + [Sales Manager Tip] + [Event Manager Tip] + [Expected Num Tip] + [Addl Tip]
DTYPE_TEXT
Modified
Booking Tip Function Status
[Function Name Tip] + [Quote Name Tip] + [Business Type Tip] + [Function Type Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Meal Period Tip] + [Sales Manager Tip] + [Event Manager Tip] + [Expected Num Tip] + [Addl Tip]
DTYPE_TEXT
39
Table 37. Fields

Field Name Booking Tip Function Type
Calculated Value/ Join.Column [Function Name Tip] + [Quote Name Tip] + [Business Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Meal Period Tip] + [Sales Manager Tip] + [Event Manager Tip] + [Expected Num Tip] + [Addl Tip]
Existing Value [Function Name Tip] + [Quote Name Tip] + [Business Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Meal Period Tip] + [Sales Manager Tip] + [Event Manager Tip] + [Expected Num Tip] [Function Name Tip] + [Quote Name Tip] + [Business Type Tip] + [Function Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Sales Manager Tip] + [Event Manager Tip] + [Expected Num Tip] [Function Name Tip] + [Business Type Tip] + [Function Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Meal Period Tip] + [Sales Manager Tip] + [Event Manager Tip] + [Expected Num Tip]
Modified
Booking Tip - Meal Period
[Function Name Tip] + [Quote Name Tip] + [Business Type Tip] + [Function Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Sales Manager Tip] + [Event Manager Tip] + [Expected Num Tip] + [Addl Tip]
DTYPE_TEXT
Modified
Booking Tip - Quote Name
[Function Name Tip] + [Business Type Tip] + [Function Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Meal Period Tip] + [Sales Manager Tip] + [Event Manager Tip] + [Expected Num Tip] + [Addl Tip]
DTYPE_TEXT
40
Table 37. Fields

Field Name Booking Tip - Sales Manager
Calculated Value/ Join.Column [Function Name Tip] + [Quote Name Tip] + [Business Type Tip]+ [Function Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Meal Period Tip] + [Event Manager Tip] + [Expected Num Tip] + [Addl Tip]
Existing Value [Function Name Tip] + [Quote Name Tip] + [Business Type Tip]+ [Function Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Setup Style Tip] + [Decision Date Tip] + [Meal Period Tip] + [Event Manager Tip] + [Expected Num Tip] [Function Name Tip] + [Quote Name Tip] + [Business Type Tip] + [Function Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Decision Date Tip] + [Meal Period Tip] + [Sales Manager Tip] + [Event Manager Tip] + [Expected Num Tip]
Modified
Booking Tip - Setup Style
[Function Name Tip] + [Quote Name Tip] + [Business Type Tip] + [Function Type Tip] + [Function Status Tip] + [Booking Start End Tip 2] + [Decision Date Tip] + [Meal Period Tip] + [Sales Manager Tip] + [Event Manager Tip] + [Expected Num Tip] + [Addl Tip]
DTYPE_TEXT
Modified Modified
Inventory Status Inventory Status Calculated [Inventory Status] + ' ' + IIF([Function Revision Type] = LookupValue('TNT_SHM _REVISION_TYPE','REVI SED'), ' -' + LookupValue('TNT_SHM _REVISION_TRANS_TY PE',[Function Revision Type]),'')
Set Force Active = TRUE
Note: Existing Field. DTYPE_TEXT
41
Order Entry - Orders

Table 38. Fields DTYPE_xxx New/Modified New Field Name Read Only Flag Calculated True Calculated Value IIf(([Status] = LookupValue("FS_ORDE R_STATUS","Event Check") OR [Freeze Flag]),"Y","N") Miscellaneous DTYPE_TEXT
Business Objects
The following tables describe the SHM Site and Quote business object components associated with ACR 575.
SHM Site
Table 39. Business Object Component Name TNT Configured Space TNT Move Function VBC TNT SHM Add Copy Function Parameter VBC Link
Quote
Table 40. Business Object Component Name TNT SHM Function Orders - DTU Link
Enabling Diary Configurable Icons

The following section describes how to enable the Diary configurable icons.
Seed Data 1
1
Launch the Siebel application.
42
From the Site Map, navigate to Administration - Application > System Preferences, and create a new system preference with the following values:

Sys Pref Name: TNT CMT Configurable Icons Sys Pref Value: Y
NOTE: If the System preference value is "Y", then only you can configure your own icons.
Instruction 1
The following section contains information about how to create your own icons. The icon name, type, height, and width should be the values detailed below.
1. Name: ind_noise Type: BMP Width: 12 Pixel Height: 12 Pixel Description: Indicates that the current booking is going to be noisy and may disturb other guests. Displayed on the booking indicator bar if space permits.
2. Name: ind_24hr_hold Type: BMP Width: 12 Pixel Height: 11 Pixel Function: Indicates that the current function space is on hold for 24 hours. Displayed on the booking indicator bar if space permits.
3. Name: ind_dont_move Type: BMP Width:12 Pixel Height:11 Pixel Function: Indicates that the current booking should not be moved from the specified function space. Displayed on the booking indicator bar if space permits.
43
4. Name: hier_tee_ltr_d Type: BMP Width: 18 Pixel Height: 18 Pixel Function: Indicate to display the hierarchical function spaces.
5. Name: hier_space Type: BMP Width: 18 Pixel Height: 18 Pixel Function: Indicate to display the hierarchical function spaces.
6. Name: hier_collapse_ltr_d Type: BMP Width: 18 Pixel Height: 18 Pixel Default Icon: Function: Indicate to display the hierarchical function spaces.
7. Name: hier_expand_ltr_d Type: BMP Width:18 Pixel Height:18 Pixel Function: Indicate to display the hierarchical function spaces.
8. Name: hier_exp_tee_ltr_d Type: BMP Width:18 Pixel Height:18 Pixel Function: Indicate to display the hierarchical function spaces.
44
9. Name: hier_exp_elbow_ltr_d Type: BMP Width: 18 Pixel Height: 18 Pixel Function: Indicate to display the hierarchical function spaces.
10. Name: hier_elbow_ltr_d Type: BMP Width: 18 Pixel Height: 18 Pixel Function: Indicate to display the hierarchical function spaces.
11. Name: hier_coll_tee_ltr_d Type: BMP Width: 18 Pixel Height: 18 Pixel Default Icon: Function: Indicate to display the hierarchical function spaces.
12. Name: hier_coll_elbow_ltr_d Type: BMP Width: 18 Pixel Height: 18 Pixel Function: Indicate to display the hierarchical function spaces.
13. Name: Ind_detail_marker Type: BMP Width: 12 Pixel Height: 11 Pixel Function: Indicates that the current booking is a detailed function. Displayed on the booking indicator bar if space permits. NOTE: If this icon is displayed next to a function space name on the y-axis, this indicates that it is a specific space that does not belong to any category.
45
14. Name: ind_sleep Type: BMP Width: 12 Pixel Height: 11 Pixel Function: To indicate the sleeping room.
15. Name: Ind_fnctn_schedule_marker Type: BMP Width: 12 Pixel Height: 11 Pixel Function: To Indicate the function Scheduled marker.
16. Name: ind_recurring Type: BMP Width: 12 Pixel Height: 11 Pixel Function: Indicates that the current booking is part of a series of recurring events.
17. Name: ind_host_booking Type: BMP Width: 12 Pixel Height: 11 Pixel Function: Indicates that the current booking is a host booking. Displayed on the booking indicator if space permits.
18. Name: ind_affiliates_booking Type: BMP Width: 12 Pixel Height: 11 Pixel Function: Indicates that the current booking is an affiliate booking. Displayed on the booking indicator bar if space permits.
46
19. Name: ind_backup_req Type: BMP Pixel Width: 12 Pixel Height: 11 Pixel Function: Indicates that current function space requires a backup function space. Displayed next to the function space name on the y-axis.
20. Name: Diary_PageDown_Enabled Type: BMP Width: 16 Pixel Height: 16 Pixel Function: Indicates that Page Down is enabled.
21. Name: Diary_PageUp_Enabled Type: BMP Width: 16 Pixel Height: 16 Pixel Function: Indicates that the Scroll Page Up button is enabled.
22. Name: Diary_PageDown_Disabled Type: BMP Width: 16 Pixel Height: 16 Pixel Function: Indicates that the Scroll Page Down button is disabled.
23. Name: Diary_PageUp_Disabled Type: BMP Width: 16 Pixel Height: 16 Pixel Function: Indicates that the Scroll Page Up button is disabled.
47
24. Name: ind_holiday Type: BMP Width: 12 Pixel Height: 11 Pixel Function: Indicates that the date is a holiday. This icon appears in all Function Space Diary views except the Month/Day view, where holidays are indicated only by the changed cell color specified in the Function Space Diary Administration screen.
25. Name: ind_Red_Icon Type: BMP Width:06 Pixel Height:06 Pixel Function: This icon marks special events in the Month/Day view.
26. Name: ind_sell_note Type: BMP Width: 12 Pixel Height: 11 Pixel Function: Indicates that sell note is associated with the date. This icon appears in all Function Space Diary views except the Month/Day view, where sell notes are indicated only by bold text.
27. Name: ind_special_events Type: BMP Width: 12 Pixel Height: 11 Pixel Function: Indicates that the date is a special event. This icon appears in all Function Space Diary views, except the Month/Day view, where special events are indicated only by small red triangle in the upper right corner of the cell.
Copying Configurable Icons

1 2
Navigate to \SWEAPP_ROOT\public\enu\. Copy the icons into the images folder.
48
Refresh the Web Server.
NOTE: The preceding instructions are specific to the English (ENU) language. If you are using another language, copy the icons into your specific language folder. For example, if you have deployed the icons in Spanish (SPA) language, copy the icons into the spa\images folder.
Configuring the Application

1 2 3
Navigate to Site Map > Function Space Administration > Function Space Diary Administration. Update Start Time = 0700:00 AM, End Time = 12:00:00 AM and Time Scale = Day/Hour under Time Interval Information. Delete the Siebel Hospitality Gantt Chart ActiveX DLLs from the Internet downloaded program files:
a b c d
Within Internet Explorer, navigate to Tools > Internet Options. Select the General tab, and click Settings. Click View Objects to open a window that contains all of the downloaded files. Select Diary ActiveX DLL and delete it.
Back to Configuration Instructions for Enhancements and Updates
Instructions for ACR 719B

CAUTION: For a known issue that affects ACR 719B and workaround information, see Release Notes for the Siebel 8.1.1.7 Fix Pack on page 7. Use the instructions in this topic to implement ACR 719B for Siebel Reports for Siebel CRM Fix Pack 8.1.1.7. For detailed information about Siebel Reports, see Siebel Reports Guide on Siebel Bookshelf. NOTE: To use the Parameters option with scheduled reports, you must have installed the appropriate Oracle BI Publisher patch level. For information about which patch to use, see Article ID 880452.1 on My Oracle Support.
Process of Implementing ACR 719B

To implement ACR 719B, perform the following tasks:
1 2 3
Applying Repository Changes for ACR 719B on page 50 Applying Schema Changes for ACR 719B on page 52 Applying Seed Data Changes for ACR 719B on page 53
49
Applying Repository Changes for ACR 719B

Perform the following procedure to apply repository changes for ACR 719B. The changes you apply depend on your Siebel application and whether you are upgrading from a previous release or deploying Siebel Reports for the first time.
Make sure that you have an existing Siebel CRM version 8.1.1 or later environment and have applied Siebel Fix Pack 8.1.1.7 For information about installing Siebel CRM, see Siebel Installation Guide for the operating system you are using. For information about installing the Fix Pack, see Siebel Fix Pack Installation Instructions on page 80.
2 3 4
Stop the Siebel Services. Copy the existing .SRF file as a backup. Edit the Siebel Tools configuration file by doing the following:
In the [Siebel] section of the tools.cfg file (in the SIEBEL_TOOLS_ROOT\BIN\LANG directory), set the SymStrPrefix parameter to SBL_. NOTE: You must change this parameter back to its original value of X_ at a later time. For more information about the SymStrPrefix parameter, see the topic on symbolic strings in Using Siebel Tools.
b c 5 6
Save the tools.cfg file. Restart Siebel Tools, if currently active.
From the SIEBEL_TOOLS_ROOT\REPPATCH directory, extract the BIP_8117.zip file. Import an archive file to apply the repository changes by doing the following:
Log in to Siebel Tools, and then lock the following projects:

XMLP Integration Table XMLP Symbolic Strings Reports UI User Preferences Activity Activity (CC) (Siebel Industry Applications) LS Pharma Calendar Siebel Universal Agent Siebel Sales Enterprise Locale Table Locale
50
Dock XMLP
NOTE: If the XMLP Integration project is inactive, activate it by unchecking the Inactive checkbox. Additionally, if projects and objects are not locked when you import SIF files, a message appears indicating which object or project is to be locked. In such a case, lock the project or object, and then import the SIF file again.
Navigate to SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\REPOSITORY, and edit the import.bat file to provide the following values:

SET TOOLSPATH = SIEBEL_TOOLS_ROOT SET DATASRC = data_source SET USERNAME = db_name SET PASSWORD = db_password
where:

SIEBEL_TOOLS_ROOT is the Siebel Tools installation path server_database is the DataSourceName from the tools.cfg file for the ServerDataSrc parameter
Run import.bat from the command prompt. NOTE: The BIP Calendar report project is available in Siebel Tools once you have imported the .sif file.
For multilingual implementations, change the language settings in Siebel Tools for each language used before compiling. For example, you would do the following to compile changes for French:
a b c d
Navigate to the View menu, then the Options menu item. Click the Language Settings tab. From the Language drop-down list, choose the desired language (FRA in this example), and then click OK. When you compile, choose the .srf file from the appropriate language folder. For this example, you would choose:
SIEBSRVR_ROOT\siebsrvr\OBJECTS\FRA\siebel_sia.srf
e 8
Compile all locked projects.
Copy the browser scripts generated from the compiled SRF into the relevant Web folder by doing the following:
a b c
Clear the existing folders in the language directory in the Siebel Tools installation directory (SIEBEL_TOOLS_ROOT\public\LANG). In Siebel Tools, compile the following object:
XMLP Integration
Navigate back to the Siebel Tools language directory and verify a new srfXXXXXXX_XXX folder was created, where X is an automatically generated number.
51
d e
Copy this folder to the SWSE\public\LANG directory. If you have a multi-language environment, repeat the above steps for each language in your deployment.
Applying Schema Changes for ACR 719B

Perform the following procedure to apply schema changes for ACR 719B.
1 2
In Siebel Tools in the Object Explorer, select the Table object. Query for all changed tables to make sure the following tables appear in the Tables list:

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

Apply the relevant seed data changes for your locales. The changes you apply depend on whether: Your deployment is Siebel Business Applications or Siebel Industry Applications. You are upgrading from a previous release or deploying Siebel Reports for the first time. To import 8.1.1.3 seed data for SIA, navigate to SIEBEL_TOOLS_ROOT\BIN, and execute the following commands: NOTE: You only need to import 8.1.1.3 seed data if you are deploying Siebel Reports for the first time. Ignore this step if you are upgrading to 8.1.1.7 from 8.1.1.3, 8.1.1.4, 8.1.1.5, or 8.1.1.6.
To import 8.1.1.3 seed data for ENU for SIA:
dataimp /u user_name /p password /f SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8113\SIA\SIAB IP_8113FP_Seed_Locale_ENU.dat /l SIEBEL_TOOLS_ROOT\TEMP\dataimp_seed.log /c data_source /d tableowner /e y /h log /w y /i SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8113\SIA\SIAB IP8113FP_SeedInps\database_type\SIABIP_8113FP_Seed_Locale_ENU.inp
To import 8.1.1.3 seed data for languages other than ENU for SIA:
53
dataimp /u user_name /p password /f SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8113\SIA\SIAB IP_8113FP_Seed_Locale_ADDITIONAL_LANG.dat /l SIEBEL_TOOLS_ROOT\TEMP\dataimp_seed.log /c data_source /d tableowner /q -1 /w n /e y /t n /x R /n 100 /h log
To import 8.1.1.3 seed data for SEA, navigate to SIEBEL_TOOLS_ROOT\BIN, and execute the following commands: NOTE: You need to import 8.1.1.3 seed data if you are deploying Siebel Reports for the first time. Ignore this step if you are upgrading from 8.1.1.4, 8.1.1.5, or 8.1.1.6 to 8.1.1.7.
To import 8.1.1.3 seed data for ENU:
dataimp /u user_name /p password /f SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8113\HOR\HO RBIP_8113FP_Seed_Locale_ENU.dat /l SIEBEL_TOOLS_ROOT\TEMP\dataimp_seed.log / c data_source /d tableowner /e y /h log /w y /i SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8113\HOR\HO RBIP8113FP_SeedInps\database_type\HORBIP_8113FP_Seed_Locale_ENU.inp
To import 8.1.1.3 seed data for languages other than ENU for SEA, run the following command:
dataimp /u user_name /p password /f SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8113\HOR\HO RBIP_8113FP_Seed_Locale_ADDITIONAL_LANG.dat /l SIEBEL_TOOLS_ROOT\TEMP\dataimp_seed.log /c data_source /d tableowner /q -1 /w n /e y /t n /x R /n 100 /h log
NOTE: You must repeat the preceding command for each language in your deployment.
To import 8.1.1.6 seed data for ENU for SIA, run the following command: NOTE: You need to import seed data if you are deploying Siebel Reports for the first time or if you are upgrading from 8.1.1.3, 8.1.1.4, or 8.1.1.5 to 8.1.1.7. If you are upgrading from 8.1.1.6 to 8.1.1.7, you do not need to import 8.1.1.6 seed data.
dataimp /u user_name /p password /f <SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8116\SIA\BI P_Seed.dat /l SIEBEL_TOOLS_ROOT\TEMP\dataimp_seed.log /c data_source /d tableowner /e y /h log /w y /i SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8116\SIA\BIP_ Seed.inp dataimp /u <user_name /p password /f <SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8116\SIA\BI P_Seed_Locale_ENU.dat /l SIEBEL_TOOLS_ROOT\TEMP\dataimp_seed.log /c data_source /d tableowner /q -1 /w n /e y /t n /x R /n 100 /h log
To import 8.1.1.6 for languages other than ENU for SIA, run the following command:
dataimp /u <user_name /p password /f SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8116\SIA\BIP_ Seed_Locale_LANG.dat /l SIEBEL_TOOLS_ROOT\TEMP\dataimp_seed.log /c data_source /d tableowner /q -1 /w n /e y /t n /x R /n 100 /h log
54
To import 8.1.1.6 seed data for ENU for SEA, navigate to SIEBEL_TOOLS_ROOT\BIN, and run the following command:
dataimp /u user_name /p password /f SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8116\HOR\BIP _Seed.dat /l SIEBEL_TOOLS_ROOT\TEMP\dataimp_seed.log /c data_source /d tableowner /e y /h log /w y /i SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8116\HOR\BIP _Seed.inp dataimp /u user_name /p password /f SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8116\HOR\BIP _Seed_Locale_ENU.dat /l SIEBEL_TOOLS_ROOT\TEMP\dataimp_seed.log /c data_source /d tableowner /q -1 /w n /e y /t n /x R /n 100 /h log
To import 8.1.1.6 seed data for languages other than ENU for SEA, run the following command:
dataimp /u user_name /p password /f SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8116\HOR\BIP _Seed_Locale_LANG.dat /l SIEBEL_TOOLS_ROOT\TEMP\dataimp_seed.log /c c data_source /d tableowner /q -1 /w n /e y /t n /x R /n 100 /h log
To import 8.1.1.7 seed data for ENU for SIA, run the following command: NOTE: The following command is required for all users, whether they are deploying Siebel Reports for the first time or whether they are upgrading from a previous 8.1.1.x Siebel Reports version.
dataimp /u user_name /p password /f SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8117\SIA\ACR 719B_VACR719B_Seed.dat /l SIEBEL_TOOLS_ROOT\TEMP\dataimp_seed.log /c data_source /d tableowner /e y /h log /w y /i <SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8117\SIA\Se edInp_Files\database_type\ACR719B_VACR719B_Seed.inp
To import 8.1.1.7 seed data for ENU for SEA, run the following command:
dataimp /u user_name /p password /f SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8117\HOR\ACR 719B_HACR719B_Seed.dat /l SIEBEL_TOOLS_ROOT\TEMP\dataimp_seed.log /c data_source /d tableowner /e y /h log /w y /i SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8117\HOR\See dInp_Files\database_type\ACR719B_HACR719B_Seed.inp
10 Compile all locked projects. 11 Start the Siebel Services.


NOTE: In order to install ACR 731, you must install an associated cab file. To access this file, from within My Oracle Support, navigate to the Patches & Updates tab, and search for Bug ID 11888716.
55
Use the instructions in the following sections to implement ACR 731. NOTE: In Siebel Tools, lock the respective object or project prior to making changes to it. Once the changes have been made, compile the respective object to the SRF file. After successful compilation, unlock the respective objects and projects.
Preinstallation Instructions
NOTE: The iSign90.cab file, which is used in this procedure, is available from Oracle Support. For more information about how to obtain this file, contact your Oracle representative or Product Manager.
Copy the iSign90.cab file to the following locations:

\siebel\webmaster\siebel_build\applets \siebel\eapps\public\enu\21215\applets
Deploy iSign90.cab.
Installing ACR 731

1 2 3 4 5 6
Log into Siebel Tools, navigate to Object Explorer and click on the Applet object. Select any record on the right-hand side of the screen and query for "LS Pharma Call Signature Form Applet". Navigate to Control and query for Name = Clear Signature. Expand the User Properties control and modify the value of the AxMethod property from Reset to ClearSignature. Navigate to Control and query for Name = Signature Capture. Expand the User Properties control, and modify the value of the AxClassId property from {EFB7D763-97A3-11CF-AE19-00608CEADE00} to {93E5204A-4344-4381-89128A7091E0FAE5}. Modify the value of the AxCodeBase property from iTools.cab to iSign90.cab. Modify the value of the AxReturnProperties property from Ink to Signature. Compile the applet. Pharma Signature Capture Form Applet applets.
7 8 9
10 Repeat Step 1 through Step 9 for the LS Pharma Txn Adjustment Signature Form Applet and LS
To edit the LS Pharma Master Signature Form Applet 1 2 3

Within Object Explorer, click on the Applet object. Select any record on the right-hand side, and query for "LS Pharma Master Signature Form Applet". Navigate to Control and query for Name = Signature.
56
Expand the User Properties control, and modify the value of the CLASSID property from {EFB7D763-97A3-11CF-AE19-00608CEADE00} to clsid:93E5204A-4344-4381-89128A7091E0FAE5. Add a new property with the following values:

Name: CodeBase Value: iSign90.cab#Version=4,5,0,319
6 7 8 9
Modify the value of the Enabled property from TRUE to 1. Change the name of the Ink user property to Signature. Compile the applet. Repeat Step 1 through Step 8 for the Pharma Signature Display Form Applet.
To edit the LS Pharma Audit Signature Linear Form Applet 1 2 3 4

Within the Object Explorer, click on the Applet object. Select any record on the right-hand side and query for "LS Pharma Audit Signature Linear Form Applet". Navigate to Control and query for Name = Signature 1. Expand the User Properties control, and modify the value of the property CLASSID from {EFB7D763-97A3-11CF-AE19-00608CEADE00} to clsid:93E5204A-4344-4381-89128A7091E0FAE5. Add a new property with the following values:

6 7 8 9
Modify the value of the Enabled property from TRUE to 1 Change the name of the Ink user property to Signature. Compile the applet. Repeat Step 1 through Step 8 for Control Signature 2, Control Signature 3, Control Signature 4, Control Signature 5, and Control Signature 6.
To edit the Pharma Signature Receipt Form Applet 1 2 3 4

Within Object Explorer, click on the Applet object. Select any record on the right-hand side and query for "Pharma Signature Receipt Form Applet". Navigate to Control and query for Name = Signature. Expand the User Properties control, and modify the value of the property CLASSID from {EFB7D763-97A3-11CF-AE19-00608CEADE00} to clsid:93E5204A-4344-4381-89128A7091E0FAE5. Add a new property with the following values:
57
6 7 8 9
Modify the value of the Enabled property from FALSE to 0. Change the name of the Ink user property to Signature. Compile the applet. Repeat Step 1 through Step 8 for the Sign control.

Use the instructions in this topic to implement ACR 750. It includes the following topics: About ACR 750 on page 58 Process of Applying ACR 750 on page 58 Importing Archive Files for ACR 750 on page 59 Creating Required Server Components for Using Outbound Web Services on page 61
About ACR 750

ACR 750 implements Siebel Application Integration for Oracle Fusion Middleware (SAI for Oracle Fusion Middleware). SAI for Oracle Fusion Middleware provides a new integration capability between Siebel Business Applications and Oracle WebLogic Server. For information about deploying and using SAI for Oracle Fusion Middleware and Siebel RESTful Services, see Siebel Application Integration for Oracle Fusion Middleware Guide on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html
Process of Applying ACR 750

To apply ACR 750 to enable Web services using SAI for Oracle Fusion Middleware, perform the following:
Review and implement the requirements for SAI for Oracle Fusion Middleware. For instructions, see Siebel Application Integration for Oracle Fusion Middleware Guide on Siebel Bookshelf.
Import the archive files. For instructions, see Importing Archive Files for ACR 750 on page 59.
58
Create the server components that you need to use outbound Web services. For instructions, see Creating Required Server Components for Using Outbound Web Services on page 61. For more information about outbound Web services specific to SAI for Oracle Fusion Middleware, see Siebel Application Integration for Oracle Fusion Middleware Guide on the Siebel Bookshelf.
Make sure the following Siebel Server components are enabled:

Siebel Application Object Manager, for example, Call Center Object Manager (ENU) EAI Object Manager (ENU) NOTE: ENU is only an example--ACR 750 is supported for all languages that are supported for the Siebel 8.1.1.7 Fix Pack.
CAUTION: Do not install SAI for Oracle Fusion Middleware until you have performed all of the steps in this section.
(First-time installation only) Install SAI for Oracle Fusion Middleware. For more information about installing and using SAI for Oracle Fusion Middleware, see Siebel Application Integration for Oracle Fusion Middleware Guide on the Siebel Bookshelf.
Importing Archive Files for ACR 750

This is a step in Process of Applying ACR 750 on page 58.
To import archive files for ACR 750 1 2

Stop the Siebel Server (or servers). On the computer where you installed Siebel Tools, locate the following ZIP files in the SIEBEL_TOOLS_ROOT\REPPATCH directory:

ACR750.zip ACR750_BaseIO_HOR.zip ACR750_BaseIO_SIA.zip
3 4
Extract the archive files (.sif) from ACR750.zip. This ZIP file provides common archives for both Siebel Industry Applications and Siebel Cross-Industry Applications. Edit the Siebel Tools configuration file (tools.cfg) to allow for import of symbolic strings.
a b c 5 6
Navigate to the directory: SIEBEL_TOOLS_ROOT\bin\lang, where lang is the language directory specific to your deployment. Open the tools.cfg file in an editor, such as Notepad. Change the value of the SymStrPrefix parameter to SBL_, and then save the tools.cfg file.
Start Siebel Tools. Lock the following projects:
EAI Business Services
59
Server Components - Infrastructure Server Components - EAI 00Phoenix
NOTE: Not all projects are available until you import the SIF files in the next step. In this case, lock the new projects, and then reimport the appropriate SIF files again.
Using the Import from Archive(s) menu item, import the following .sif archive files you previously extracted into Siebel Tools:

00Phoenix.sif (import this SIF only if you are using Siebel RESTful Services) CSSEAIJCAService.sif CSSIOCreationService.sif DynamicIOCreationService.sif EAI JCA Service.sif EAISubsys.sif InfraNameServer.sif SAI EAI Outbound Services.sif ServerMgr_ARN_ParameterRemoved.sif ServerMgrSubsys.sif
Extract the archive (.sif) files from the appropriate ZIP file to a folder.

ACR750_BaseIO_HOR.zip. This archive file provides base integration objects for Siebel Cross-Industry Applications. ACR750_BaseIO_SIA.zip. This archive file provides base integration objects for Siebel Industry Applications.
Run the following command from the SIEBEL_TOOLS_ROOT\tools\bin directory to import the preconfigured base integration objects: NOTE: This process can take some time; wait until the process completes. siebdev.exe /c tools.cfg /d data_source /u user_name /p password /batchimport "Siebel Repository" merge directory_name import.log where:

/c is the configuration file name and location /d is the data source to use /u is the username /p is the password Siebel Repository is the repository you want to use (the default is Siebel Repository)
directory_name is the directory to which you extracted the base integration objects in Step 8
import.log writes the data to a log file in the SIEBEL_TOOLS_ROOT\tools\bin directory
60
10 Lock the following additional projects:

SAI Outbound Services SAI Base Integration Objects
11 Compile the following projects into an updated repository file (SRF):

EAI Business Services EAI IO Deployment Server Components - Infrastructure Server Components - EAI SAI Outbound Services SAI Base Integration Objects
12 Copy the new SRF file to the Siebel Server installation directory, under SIEBSRVR_ROOT\objects\lang. 13 Restart the Siebel Server.
Creating Required Server Components for Using Outbound Web Services

To use the outbound Web services feature in SAI for Oracle Fusion Middleware, you must create new component definitions, activate the new components, and create named subystems. Use the following procedure to create a new EAI Outbound Server (InfraEAIOutbound) server component and the two subsystem instances that are detailed in the following procedure. This is a step in Process of Applying ACR 750 on page 58.
To create the component definitions 1

Connect to Server Manager using the following command: srvrmgr /g gatewayserver:port /e entrprserver /u username /p password
Create a component definition called InfraEAIOutbound for the EAI component group, using the following command: create compdef InfraEAIOutbound for comptype "EAI Outbound Service" compgrp "EAI" runmode batch full name "EAI Outbound Server" with param MaxTasks=20, UnicodeConvError=FALSE, CfgRepositoryFile="Siebel_sia.srf" fixparam Method=CallJava, ConfigFile=siebel.cfg, NamedDataSource="ServerDataSrc,GatewayDataSrc", DataSource=ServerDataSrc
Activate the new component definition that you created, using the following command: activate compdef InfraEAIOutbound
Create the named subsystems EAIOutboundJVMSubsys and EAIOutboundsubsys.
Use the following command for EAIOutboundSubsys:
61
create named subsystem EAIOutboundSubsys for subsystem OutboundEAISubsys with EAIOutboundContextFactory=weblogic.jndi.WLInitialContextFactory,EAIOutboundProv iderURL="t3:// weblogicserver:port,EAIOutboundSecurityCredentials=weblogic1,EAIOutboundSecurit yPrincipal=weblogic,EAIOutboundConnectionFactory="Connection Factory JNDI Name",EAIOutboundReceiveQueue="Receive Queue JNDI Name",EAIOutboundReceiveTimeout="30000",EAIOutboundSendQueue="Send Queue JNDI Name",EAIOutboundTransportType=RMI Where:

weblogicserver is a placeholder for your application server name port is the port on which the Oracle WebLogic Server resides
Use the following command for EAIOutboundJVMSubSys: create named subsystem EAIOutboundJVMsubsys for subsystem JVMSubSys with DLL="$(JAVA_HOME)/jre/bin/server/$jvm.dll", CLASSPATH="$(SiebelRoot)/classes/ original/Siebel.jar;$(SiebelRoot)/classes/original/ wlfullclient.jar;$(SiebelRoot)/classes/original/SiebelJI_$SiebelLang$.jar", VMOPTIONS="-Xrs -DEAIOutbound.log=EAIOutbound"
Restart the Siebel Server, and use the following commands to check the new component definition and named subsystems: list comp for compgrp EAI list param for named subsystem EAIOutboundJVMsubsys list param for named subsystem EAIOutboundSubsys
Navigate to the SIEBSRVR_ROOT directory, and using the command prompt, create an XSD folder using the mkdir xsd command.

1 2 3
Navigate to <Tools Install Directory>\REPPATCH, and copy the ACR762.zip file. Within the Tools.cfg file, edit the SymStrPrefix = X_ parameter to SymStrPrefix = SBL_. Navigate to Tools\REPPATCH, and extract the ACR762.zip file.
Importing SIF Files for ACR 762

Use the following procedure to import SIF files for ACR 762.
62
To import the ACR 762 sif files 1

Navigate to Tools\REPPATCH\ACR762\REPOSITORY\PROJECT_TO_LOCK.txt file, and lock the projects listed in the file. NOTE: Navigate to <Tools Install Directory>\REPPATCH\ACR762\REPOSITORY\Applet.list to find the list of objects to be imported.
Navigate to Tools\REPPATCH\ACR762\REPOSITORY\BatchImport.bat, and update the file with your environment information. SET IMPORTTOOLSROOT=<Tools Path E.g. D:\sea78\tools> SET IMPORT_DATASOURCE=<DataSrc from Tools.cfg> SET IMPORT_USER=<DB User Name> SET IMPORT_PASSWORD=<DB Password>
3 4
Run the BatchImport batch file to import the new objects. Navigate to Tools\REPPATCH\ACR762\REPOSITORY\ImportLog\ImportSummary.txt, and verify that the import completed successfully.
SBL_LS_SGOP_PRODUCT_DETAIL
Importing Repository Objects for ACR 762

The SIF files for ACR 762 are packaged in the ACR762.zip file, which is located in the <Tools Install Directory>\REPPATCH\ACR762\REPOSITORY\Modified Objects folder. You can configure the applets, the application, and the business components manually, or you can import the SIF filesor import the sif files one by one manually. If you choose to import the sif files, please lock those projects and use the "Merge" option for import from archive.
Add a new field to the Client - Mobile business component: Column REMOTE_NODE_TYPE_C D Pre-Def Value Expr: "LookupValue(""REMOTE _NODE_TYPE"",""SIEBEL _REMOTE"")" Pick List LS SGOP Remote Client Type Picklist
Name Remote Node Type
Pick Map Parent Field Remote Node Type Field Remote Node Type Picklist Field Value
63
Add a new field to the Pharma Address business component:
Fields Name Row Id Column ROW_ID Join S_CON_ADDR Force Active TRUE
Add a new list column to the Mobile Client list applet with the following values, and map the new column to the Edit List: Class CSSSWEFrameListVisibilityPick No Insert TRUE
Business Component Client - Mobile
List Columns Display Name Remote Node Type Field Remote Node Type Display Name Remote Node Type Display Name String Reference SBL_LS_SGOP_REMOTE_NODE_TYPE Pick Applet
Within the Siebel Life Sciences application, add a new screen menu item:
Screen Menu Item Screen Screen LS SGOP Modification Tracking Admin Screen Text Text Administration Modification Tracking Text String Reference Text String Reference SBL_LS_SGOP_ADMINSTRATION_MODIFICATION _TRACKING
Applying Schema Changes for ACR 762

Use the following procedure to apply the schema changes for ACR 762.
To apply schema changes for ACR 762 1 2 3

From within Siebel Tools, navigate to the Object Explorer and select Table. Query for the new or modified tables (S_TXN_LOG_LS OR S_TBLOBJ_MAP_LS OR S_NODE). Click the Apply/DDL button to apply the schema changes.
Importing Seed Data for ACR 762

The seed data for ACR 762 has been provided in a .dat file.
64
Use the following procedure to import seed data for ACR 762.
To import seed data for ACR 762

NOTE: Before you import the seed data, you must have applied the schema changes for the new tables.
Create an ODBC entry for the database where you plan to import the seed data:
a b c d
Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC), navigate to the System DSN tab, and click Add. Select the "Siebel Oracle90" driver (from Datadirect Technologies). Enter a data source name (such as Siebel_DSN. Enter the server name to connect to:

For Oracle, enter the TNS service name that you created to connect Siebel Tools to the database. Test your connection and click OK when tested successfully
2 3
Navigate to the directory where you installed Siebel Tools and change the directory to REPPATCH\ACR762. Navigate to <Tools Install Directory>Root\REPPATCH\ACR762\SEED_DATA\, and update the importSeed.bat file with your environment information.

SET SGOPTOOLSPATH=<Tools Path>, such as D:\sea78\tools SET SGOPDATASRC=<DataSrc from ODBC System DSN (such as Siebel_DSN> SET SGOPTBLOWNER=<Table Owner Name> SET SGOPUSERNAME=<DB User Name> SET SGOPPASSWORD=<DB Password>
4 5 6 7
Before executing the next step, make sure that the dataimp.exe file exists in the <Tools Install Directory>/bin directory. Run the ImportSeed batch file to import the seed data. Navigate to <Tools Install Directory>\REPPATCH\ACR762\SEED_DATA\log, and check the ACR762_SEEDImp.log file to see if there were any errors during the import. Update the Object Table Mapping records:
a b
Log into the Siebel application as an administrator (sadmin/sadmin). Navigate to Modification Tracking Admin Screen > Object Table Mappings view, and update the following records: Object Name LS SGOP_RelatedContact LS SGOP_RelatedAccount Table Name S_PARTY_REL S_PARTY_REL
65
Importing Web Services for ACR 762

The web service XML files are included in the ACR762.zip file. Use the following procedure to import the Web services for ACR 762.
To import the Web services for ACR 762 1 2 3 4 5

Navigate to <Tools Install Directory>\REPPATCH\ACR762.zip, and unzip the file. Navigate to <Tools Install Directory>\REPPATCH\ACR762\ WEB_SERVICE\ WS_XML_Listtoverify.txt, and use the instructions in the file to import the Web services. Log into the Siebel application as an administrator (sadmin/sadmin). Navigate to Web Services Admin Screen -> Inbound Web Services view, click the Import button, and browse to the Web service file that you want to import. Before importing LSSGOP_Contact.XML, run the update SQL command against the database that you are connecting to. This updates the existing OOTB Contact's Proxy Name to avoid a unique key violation error. Update S_WS_OPERATION set proxy_name = 'ContactIns' where name='ContactInsert' Update S_WS_OPERATION set proxy_name = 'ContactUpd' where name='ContactUpdate' Update S_WS_OPERATION set proxy_name = 'ContactDel' where name='ContactDelete' Update S_WS_OPERATION set proxy_name = 'ContactQP' where name='ContactQueryPage'
Before importing ModificationTrackingPurge.XML and ModificationTracking.XML, run the two SQL statements below Update S_WS_OPERATION set proxy_name = 'xx' where method_name='Delete' and proxy_name is null; Update S_WS_OPERATION set proxy_name = 'xx' where method_name='QueryPage' and proxy_name is null;
Move the DLLs from the ACR 762 > Library > Documents > Dlls to the \siebsrvr\BIN folder. NOTE: The .sscaspbc.dll and swcaspfr.dll files are specific to Siebel Life Sciences functionality, and the sssatrou.dll and sssrrec.dll files are specific to modification tracking.
Enabling Modification Tracking and Setting Up Mobile Clients

To enable modification tracking, update the SQL in the comdb44.sql and comdb45.sql files. In <siebsrvr_root>\SQLTEMPL\comdb44.sql,the new sql for modifcation tracking is not enabled by default. ;;; Find transactions to route TXN_ROUTER_SEL_NODES = select childn.ROW_ID NODE_ID, childn.NAME, dsr.LAST_TXN_NUM from &Table_Owner.S_DOCK_STATUS dsr,
66
&Table_Owner.S_NODE childn where childn.PAR_NODE_ID = ? and childn.APP_SERVER_NAME = ? and childn.NODE_TYPE_CD = 'REMOTE' and (childn.EFF_END_DT is null or childn.EFF_END_DT >= {fn now()}) and childn.ROW_ID = dsr.NODE_ID and dsr.TYPE = 'ROUTE' and dsr.LOCAL_FLG = 'Y' and childn.ROUTE_ACTIVE_FLG = 'Y' / The final sql should look like this: ;;; Find transactions to route TXN_ROUTER_SEL_NODES = select childn.ROW_ID NODE_ID, childn.NAME, dsr.LAST_TXN_NUM, childn.REMOTE_NODE_TYP_CD from &Table_Owner.S_DOCK_STATUS dsr, &Table_Owner.S_NODE childn where childn.PAR_NODE_ID = ? and childn.APP_SERVER_NAME = ? and childn.NODE_TYPE_CD = 'REMOTE' and (childn.EFF_END_DT is null or childn.EFF_END_DT >= {fn now()}) and childn.ROW_ID = dsr.NODE_ID and dsr.TYPE = 'ROUTE' and dsr.LOCAL_FLG = 'Y' and childn.ROUTE_ACTIVE_FLG = 'Y' /
Adding Lists of Values for ACR 762

1
Bounce the server and launch the Siebel Server URL.
67
Navigate to Site Map > Administration - Data > List Of Values, and create the following list of values: Type REMOTE_NODE_TYPE REMOTE_NODE_TYPE REMOTE_NODE_TYPE REMOTE_OPERATION_TYPE REMOTE_OPERATION_TYPE REMOTE_OPERATION_TYPE REMOTE_OPERATION_TYPE Display Value Offline Client Siebel Remote Both FullDownload Insert Update Delete LIC OFFLINE CLIENT SIEBEL_REMOTE BOTH FullDownload Insert Update Delete
Enabling Modification Tracking

1 2 3 4
Bounce the server and launch the Siebel Server URL. Navigate to Site Map> Administration - Application > System Preference view, add a new System Preference record called Enable Modification Tracking, and set the value to TRUE. Navigate to Site Map >Administration - Server Configuration > Synchronize, and click the Synchronize button. Navigate to Administration - Siebel Remote, and create a new mobile client entry with the following values: NOTE: If an entry already exists, delete it and recreate the record to set App Server Name as the current server.

Mobile Client - SPORTER Uid - SPORTER Routing Model - MOBILE CLIENT - STANDARD Language - ENU Remote Node Type - Offline Client
Navigate to Administration - Server Management > Jobs, and create a new job with the following parameters (one time per server) to create a new database template in the Siebel\dbtempl folder:
Component/Job - Generate New Database
Wait until the new job completes, and repeat Step 5 for each remote client to complete remote client setup.
68

The following sections describe how to configure ACR 802.
Preinstallation Task for ACR 802

1
Navigate to the Siebel Tools installation directory, and within the tools.cfg file, change the symbolic strings prefix to SBL_. NOTE: Make a note of the parameters original value, as you need to change the prefix back to that after you have imported the SIF files.
Importing Repository Objects for ACR 802

1 2 3
Navigate to <Tools Install Directory>\REPPATCH\ACR802.zip, and extract the file. Open Siebel Tools connected to the relevant database, and using Object Explorer, navigate to Projects. Using Object Explorer, navigate to Projects, and lock the following projects:

LOY Admin LOY Engine Buscomps SIA Server Objects LOY Gen Import
NOTE: All the repository objects are located within the ACR802\REPOSITORY folder inside the extracted ACR802.zip folder. The ACR802 Repository Objects.xls file lists all of the objects that were added or modified in ACR 802. These sif files are located in the corresponding folders, as shown in Table 41 on page 69.
Table 41. S. No 1 2 3 4 5 6
Repository Objects for ACR 802 Repository Type Applet Busienss Component Business Object Business Service Picklist View SIF File Name Applet \ Applets.sif Business Component \ BusinessComponents.sif Business Object \ BusinessObjects.sif Business Service \ BusinessServices.sif Picklist \ PickLists.sif View \ Views.sif
69
Table 41. S. No 7 8 9 10 11
Repository Objects for ACR 802 Repository Type Class Workflow Symbolic String Integration Object Link SIF File Name Class \ Classes.sif Workflow \ WorkFlows.sif Symbolic String \ SymbolicStrings.sif Integration Object\IntegrationObjects.sif Links\Links.sif
To import repository objects 1 2 3 4 5

Open Siebel Tools connected to the relevant database, and from the main menu, select the Tools > Import from Archive option. Import the files listed in Table 41 on page 69 one at a time, using the merge option, and click Next. Review the changes within the Import Wizard - Review Conflicts and Actions window and click Next. When the system displays the "Do you want to proceed?" confirmation message, click Yes to import the repository objects. Click Finish to close the Import Wizard window.
Applying Schema Changes for ACR 802

As part of the ACR802 release, schema changes have been done on the database. The REPPATCH\ACR802\Repository\Table\Base\ACR802_BaseTables.sif has all the changes for the following: The following table has been modified as part of the ACR802 release:

Sequence Number: 1 Table Name: S_LOY_MEM_BLKAD
Use the following procedure to import table repository objects.
To import table repository objects 1 2

Launch Siebel Tools connecting to the relevant database, and make sure that the database user has the DML privileges to apply schema changes in this database. Lock the Table Loyalty project. following project
70
Import the ACR802_BaseTables.sif file using the procedure described in To import repository objects on page 70. This file is located in the <Tools Install Directory>\REPPATCH\REPOSITORY\TableBase folder. NOTE: The ACR802_BaseTables.sif file also contains the schema changes for Bug 10606137, which was addresesd in the Siebel 8.1.1.5 Fix Pack. It contains changes for the following tables: S_LOY_TXN, S_LOY_ACRL_ITM, S_LOY_RDM_ITM).
To apply the table changes 1 2 3

Within Siebel Tools, navigate to the Tables object, and query for the S_LOY_TXN, S_LOY_ACRL_ITM, and S_LOY_RDM_ITM tables. Select the Apply/DDL option. Within the confirmation dialog box, select Apply and then click OK. Then Apply Schema dialog box displays.
Within the Apply Schema dialog box, provide details for the following fields.
a b c d 5 6
Within the Tables drop-down list, select Current Query. Within the Database user field, enter the database user name. Within the Database user password field, enter the database user password. Within the ODBC data source field, enter the ODBC name.
After filling out the fields in the Apply Schema dialog, click Apply. Within the confirmation dialog box, click OK. Use the following procedure to compile the repository objects into the SRF.
To compile the repository objects into the SRF 1 2 3 4

Launch siebel tools connecting to the relevant database From the main menu, select Tools > Compile Projects. Press the CTRL key pressed, select the LOY Admin, LOY Engine Buscomps, SIA Server Object, LOY Gen Import, and Table Loyalty projects. Select the relevant SRF file for your installation and then click Compile.

The following sections contain configuration instructions for ACR 839.
Preparing for the ACR 839 Installation

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

LS Clinical Protocol Site Table Clinical EIM Clinical Symbolic Strings
Installing ACR 839 Using the Automated Process

1
Rename <Unziplocation>\REPOSITORY\import.txt to import.bat, and edit the file to change the first four parameters related to database and Siebel Tools details with the Siebel Administrator username/password. For example: SET ACR839TOOLSPATH=D:\21219\Tools SET ACR839DATASRC=serverDatasrc SET ACR839USERNAME=<Siebel Admin Username> SET ACR839PASSWORD=<Siebel Admin Password>
2 3 4 5 6
Create a folder called named Log in <Unziplocation>\REPOSITORY. Run the import.bat file to import the .sif files, and check the log file to verify that all of the files imported successfully. Apply the schema changes for the S_SITE_VST_LOG and EIM_ST_VST_LOG tables. For more information, see Performing Schema Changes for ACR 839 on page 72. Import the workflow processes into Siebel repository. For more information, see Importing Workflow Definitions for ACR 839 on page 78. In Siebel Tools, compile all of the locked and updated projects. CAUTION: It is recommended that you delete the import.bat file after the installation is complete, because the file contains sensitive information.
NOTE: If you want to configure ACR 839 manually, use the instructions in Performing Schema Changes for ACR 839 on page 72 through Configuring Integration Objects for ACR 839 on page 77 . If you are using the automated functionality to configure ACR 839, you do not need to perform the procedures in these sections. Instead, perform the procedures described in Importing Workflow Definitions for ACR 839 on page 78 through Configuring Web Services for ACR 839 on page 80.
Performing Schema Changes for ACR 839

NOTE: The following step is not required if you have already imported the .sif files. This step is only required if you are performing the configuration changes manually. The following tables were modified for ACR 839: S_SITE_VST_LOG
72
EIM_ST_VST_LOG
Use the Tools - Import from Archive function within Siebel Tools to read this file and create the tables in the repository. Use the Merge option to import this file. NOTE: You only need to import the tables if you are configuring ACR 839 manually. If you have imported the sif files, you do not need to perform this procedure. Use the following procedure to create the S_SITE_VST_LOG and EIM_ST_VST_LOG tables on the physical database.
To create the S_SITE_VST LOG and EIM_ST_VST_LOG tables on the physical database 1 2 3
Within Siebel Tools, query for the list of tables that were imported into the repository. Click the Apply/DDL button to apply the changes to the physical database. Provide the Table Owner details in the username and password fields and the ODBC name in the ODBC data source field.
Configuring the Business Components for ACR 839

NOTE: The following procedures is not required if you have already imported the SIF files. This step is only required if you are performing the configuration changes manually. ACR 839 requires that you add new business components as well as modify existing business components. You must import the SIF files to use the new business components, you must import the SIF files. You must modify the existing business components to implement ACR 839. The following section describes how to configure the business components for ACR 839.
LS Clinical Site Visit Location Business Component (New) Navigate to <Unziplocation>\REPOSITORY\Business Component\LS Clinical Site Visit Location.sif, and import the file using the Import from Archive function within Siebel Tools.
LS Clinical Site Visit Employee Business Component (New) Navigate to <Unziplocation>\REPOSITORY\Business Component\LS Clinical Site Visit Employee.sif, and import the file using the Import from Archive function within Siebel Tools.
Clinical Protocol Site for Mobile Integration Business Component (New) Navigate to <Unziplocation>\REPOSITORY\Business Component\Clinical Protocol Site for Mobile Integration.sif, and import the file using the Import from Archive function within Siebel Tools.
Clinical Protocol Site Address Business Component (Modified) Add a new field to the Clinical Protocol Site Address business component with the following values:
Name: Address Row Id
73
Column: ROW_ID Text Length: 15 Type: DTYPE_ID
Clinical Trip Report Business Component (Modified)
Add the following Joins and Join Specifications fields described in Table 42 and Table 43:
Table 42. Name
Joins and Join Specifications Fields for ACR 839 (Continued in Table 43) Column FORMAT_TYPE_CD EMP_ID LOGIN Join S_EVT_MAIL S_ACT_EMP S_USER Immediate Post Changes No Copy
Email Format Emp Id Active Login Name
Table 43.
Joins and Join Specifications for ACR 839 (Continued from Table 42) Picklist Type DTYPE_TEXT DTYPE_ID DTYPE_TEXT Required Calculated Predefault Value
Name (Continued) Email Format Emp Id Active Login Name
Add a join with the following values: Alias S_ACT_EMP S_USER
Table S_ACT_EMP S_USER
74
Add a join specification with the values in the following table: Name Visit Employee Emp Login Destination Column ACTIVITY_ID ROW_ID Source Field Id Emp Id
Alias S_ACT_EMP S_USER
Clinical Trip Report Business Component User Properties New/Changed Changed (Deep Delete changed to Deep Delete 1) New Name Deep Delete 1 Deep Delete 2 Value Activity Plan LS Clinical Site Visit Location
Configuring Links for ACR 839

NOTE: The following step is not required if you have already imported the .sif files. This step is only required if you are performing the configuration changes manually.
Navigate to the <Unziplocation>\REPOSITORY\ Link\Clinical Trip Report folder, and import the following .sif files using the Import from Archive function within Siebel Tools:

LS Clinical Site Visit Location.sif LS Clinical Site Visit Employee.sif
Navigate to <Unziplocation>\REPOSITORY\Link\Clinical Protocol Site for Mobile Integration folder, and import the following files using the Import from Archive function within Siebel Tools:

Clinical Trip Report.sif Clinical Protocol Site Address BC.sif Clinical Account Investigator Role.sif
Configuring Business Objects

NOTE: The following step is not required if you have already imported the .sif files. This step is only required if you are performing the configuration changes manually. Navigate to the <Unziplocation>\REPOSITORY\Business Object folder, and import the following .sif files using the Import from Archive function within Siebel Tools:

Clinical Protocol Site for Mobile Integration.sif LS Clinical Site Visits Geo Location.sif
75
To update the changed business objects 1 2 3

Within Object Explorer, select the Business Object object type, and query for Clinical Trip Report. Within Object Explorer, expand Business Object. Within Object Explorer, select Business Component, and update the Business Object component information for the Clinical Trip Report business component as described in the following table: Link Clinical Trip Report/LS Clinical Site Visit Location Clinical Trip Report/LS Clinical Site Visit Employee Description Retrieves the data specific to the site visit Retrieves the employees specific to the site visit
Business Component LS Clinical Site Visit Location LS Clinical Site Visit Employee
Configuring Symbolic Strings for ACR 839

NOTE: The following step is not required if you have already imported the .sif files. This step is only required if you are performing the configuration changes manually. Navigate to <Unziplocation>\REPOSITORY\ Symbolic String, and import the following files using the Import from Archive function within Siebel Tools: SBL_LS_CLINICAL_SITE_VISIT_LOCATION.sif SBL_GEO_LOCATION_DETAILS.sif
Configuring Applets for ACR 839

NOTE: The following step is not required if you have already imported the .sif files. This step is only required if you are performing the configuration changes manually. Use the procedure in the following section to configure the applets for ACR 839.
Clinical Site Visit Location List Applet (New) Navigate to <Unziplocation>\REPOSITORY\Applet\ LS Clinical Site Visit Location List Applet.sif, and import the file using the Import from Archive function within Siebel Tools.
Configuring Views for ACR 839

Import the following .sif files using the Import from Archives function within Siebel Tools:
1 2
Navigate to <Unziplocation>\REPOSITORY\View\LS Clinical Trip Report Detail View with Geo Location.sif, and import the file using the Import from Archive function within Siebel Tools. Navigate to <Unziplocation>\REPOSITORY\View\LS Clinical Trip Report Detail View with Geo Location Without CRF.sif, and import the file using the Import from Archive function within Siebel Tools.
76
Configuring Screens for ACR 839

NOTE: The following procedure is not required if you have already imported the .sif files. This step is only required if you are performing the configuration changes manually. Use the following procedure to configure screens for ACR 839.
1 2
In OBLE, navigate to the Screen object. Query for the Clinical Site Management screen and add the LS Clinical Trip Report Detail View with Geo Location and LS Clinical Trip Report Detail View with Geo Location Without CRF views as shown in the following table: Viewbar Text on Screen View Geo Location Details Geo Location Details
Screen Clinical Site Management Clinical Site Management
Screen Views Clinical Trip Report Detail View with Geo Location Clinical Trip Report Detail View with Geo Location Without CRF
Right-click on Screen, select edit Screen View Sequence, and verify that the views are added after the last view under the "Clinical Trip Report Detail View" and "Clinical Trip Report Detail View without CRF" categories, respectively.
Configuring Picklists for ACR 839

NOTE: The following step is not required if you have already imported the .sif files. This step is only required if you are performing the configuration changes manually. Navigate to <Unziplocation>\REPOSITORY\Pick List\LS Clinical Site Visit Employee PickList.sif, and import the file using the Import from Archive function within Siebel Tools.
Configuring Integration Objects for ACR 839

NOTE: The following procedure is not required if you have already imported the .sif files. This step is only required if you are performing the configuration changes manually.
1 2
Lock the LS Clinical Protocol Site project. Navigate to <Unziplocation>\REPOSITORY\Integration Object folder, and import the following .sif files using the Import from Archive function within Siebel Tools:

LS Clinical Protocol Site_Site Visits Input IO.sif LS Clinical Protocol Site_Site Visits Intermediate IO.sif LS Clinical Protocol Site_Site Visits Output IO.sif LS Clinical Site Visits Geo Loc IO.sif LS Clinical Site Visits Geo Loc Intermediate IO.sif
Compile the locked projects.
77
Importing Workflow Definitions for ACR 839

NOTE: You must perform the following procedure regardless of whether you have imported the sif files using the automated function or if you have performed the ACR 839 configurations manually. Use the following procedure to import workflow definitions.
To import workflow definitions 1

Log in to Siebel Tools. NOTE: Siebel Tools must be connected to the same database as the Siebel application server.
2 3 4
From Object Explorer, navigate to Workflow Process, and from the list applet, right-click and choose Import Workflow Process. Navigate to <Unziplocation>\REPOSITORY\Workflows, and select SWI LS Clinical Query Protocol Site_Site Visits.xml. Navigate to <Unziplocation>\REPOSITORY\Workflows, and select SWI LS Clinical Create Site Visit Geo Location.xml. Xml File to Import SWI LS Clinical Query Protocol Site_Site Visits.xml SWI LS Clinical Create Site Visit Geo Location.xml Workflow Name SWI LS Clinical Query Protocol Site_Site Visits SWI LS Clinical Create Site Visit Geo Location Project LS Clinical Protocol Site LS Clinical Protocol Site
New/Modified New
New
5 6
After import, query for the workflows, and in Lock Projects view > Workflow process, focus on the records, and click the Publish button on top of the applet to deploy the workflows. Repeat the preceding steps for the remaining new workflows.
Activating Workflow Definitions for ACR 839

Use the following procedure to activate workflow definitions.
To activate workflow definitions 1 2 3

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

SWI LS Clinical Query Protocol Site_Site Visits SWI LS Clinical Create Site Visit Geo Location
78
Enabling Component Groups for ACR 839

Make sure that the EAI and Workflow Management component groups are enabled. If not, enable them and bounce the Siebel Server.
For information about how to enable component groups, see topic about enabling Siebel Server component groups for safety system integration in the Siebel Life Sciences Guide on the Siebel Bookshelf.
Importing Seed Data for ACR 839

NOTE: You must perform the following procedure regardless of whether you have imported the .sif files using the automated function or if you have performed the ACR 839 configurations manually.
To import seed data using the automated function 1

Create an ODBC entry for the database where you plan to import the seed data:
a b c d e 2
Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC), click the System DSN tab, and click Add. Select the "Siebel Oracle90" driver (from Datadirect Technologies). Enter a data source name (such as DevelopmentDB). Enter the server name to connect to.
For Oracle enter the TNS service name that you created to connect your tools to the DB.
Test your connection and click OK when tested successfully.
Navigate to the directory where you installed Siebel Tools. NOTE: Before executing the next step, make sure that the dataimp.exe file exists in the <Tools Install Directory>/bin directory.
Rename <Unziplocation>\SEED_DATA\Import_Seed_Data.txt to import_Seed_Data.bat, edit the file, and change the first six parameters related to the application database and Tools Path details. Create a temp directory under <Tools Install Directory> to save the log file. For example: SET ACR839TOOLSPATH=D:\Siebel_8113_Release\Tools_8115_21229 SET DBFOLDER=D:\Siebel_8113_Release\Tools_8115_21229\Seed\ORACLE SET ACR839DATASRC=emsqa1b SET ACR839TBLOWNER=EMSORA01225 SET ACR839USERNAME=SADMIN SET ACR839PASSWORD=SADMIN
Run the Import_Seed_Data.bat file to import seed data.
79
Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B Siebel Fix Pack Installation Instructions
Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import completed successfully CAUTION: It is recommended that you delete the import.bat file after the installation is complete, because the file contains sensitive information.
Configuring Web Services for ACR 839

Note the following information: You must have imported the seed data before you configure the Web services. You must import Web services regardless of whether you have used the automated .sif file import function or if you have configured ACR 839 manually. NOTE: You must have imported seed data before you configure the Web services. For information about how to configure web services, see the topic about configuring Web services Siebel Life Sciences Guide. The following Web services need to be imported for ACR 839: Web Service Name SWILSClinicalQueryProtocolSite_SiteVisits SWILSClinicalCreateSiteVisitGeoLocation Direction Inbound Inbound
Siebel Fix Pack Installation Instructions

This topic includes the following subtopics: Siebel Fix Pack Installation Overview on page 81 Installing the Siebel Fix Pack on Microsoft Windows on page 85 Installing the Siebel Fix Pack on UNIX on page 90 Configuring Slipstream Patch Installation on page 95 Postinstallation Tasks for the Siebel Server on page 96 Postinstallation Tasks for the Web Server on page 97 Postinstallation Tasks for High Interactivity Clients on page 97 Postinstallation Tasks for Supporting Additional Languages on page 98 Uninstalling Siebel Fix Packs on page 99
80
Siebel Fix Pack Installation Overview

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

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

This topic is part of Siebel Fix Pack Installation Overview on page 81. In general, each Siebel Fix Pack can be installed on top of an existing Siebel installation that is at a valid base version level for this Fix Pack.
82
Installing any Fix Pack requires an existing installation of a qualified base release to install into. Here, base release means the current version of the existing installation, including version 8.1.1 software and optionally including any installed Siebel Fix Pack 8.1.1.x or other patch releases. 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 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 81. You use the Siebel Image Creator utility to create an installation image (sometimes called a network image) for version 8.1.1 and for any Siebel Fix Pack 8.1.1.x release. The image can include any Siebel installable product and language provided as part of this product release. You can also add products or languages to an existing installation image of the same version, for products or languages that were not previously included. Installing any Siebel Business Applications release, including a new installation of version 8.1.1, an installation of a Siebel Fix Pack 8.1.1.x release, or the addition of one or more languages, must be done from an installation image created using Image Creator. NOTE: Always use the version of Siebel Image Creator provided with the Siebel release for which you are creating the installation image. Information about using Siebel Image Creator is provided in the Siebel Installation Guide for the operating system you are using, on the version 8.1 Siebel Bookshelf.
About Installing Siebel Fix Packs

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

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

This topic is part of Siebel Fix Pack Installation Overview on page 81. After installing version 8.1.1 and a Siebel Fix Pack 8.1.1.x release as described in this guide, you can also install any applicable Siebel Quick Fix releases on top of version 8.1.1.x. When you install a Quick Fix, installed languages might also be patched, depending on the content of the Quick Fix release. NOTE: Installing Quick Fixes 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.
Related Topics Quick Fixes Included in the Siebel 8.1.1.7 Fix Pack on page 11
Installing the Siebel Fix Pack on Microsoft Windows

This topic is part of Siebel Fix Pack Installation Instructions on page 80. Procedures for installing Siebel Fix Pack 8.1.1.x for products on Microsoft Windows are detailed in this topic. Follow these instructions to install each product over the existing base installation for the same product. Perform the steps that apply for the Fix Pack you are installing, in the general sequence presented here. Before you install the Fix Pack, review all applicable information in Siebel Fix Pack Installation Overview on page 81. The instructions generally assume that Fix Pack installers are started in GUI mode. Alternatively, the installers for server-based products can be started in console or unattended mode. In unattended mode, the Fix Pack installation runs silently. See also Configuring Slipstream Patch Installation on page 95.
85
NOTE: If you installed version 8.1.1 Siebel software using the Siebel FastTrack Wizard, use the Fix Pack installers for Siebel Enterprise Server and Siebel Web Server Extension to patch any installed instances of these modules. The FastTrack Wizard is provided for small to medium businesses (SMB). For more information, see Siebel Installation Guide for Microsoft Windows. This topic has the following subtopics: Installing the Fix Pack for Siebel Enterprise Server on Windows on page 86 Installing the Fix Pack for Siebel Web Server Extension on Windows on page 87 Installing the Fix Pack for Siebel Management Agent and Siebel Management Server on Windows on page 87 Installing the Fix Pack for Siebel Mobile Web Client, Siebel Tools, or Siebel Client Sync on Windows on page 89
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 85. Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any computer where a Siebel Enterprise Server component is installed, including Siebel Server, Siebel Gateway Name Server, and Database Configuration Utilities (formerly referred to as the Siebel Database Server). The Fix Pack installer for Siebel Enterprise Server also patches any instance of Siebel Management Agent that was automatically installed with a Siebel Server you are patching. See also Installing the Fix Pack for Siebel Management Agent and Siebel Management Server on Windows on page 87.
To install the Fix Pack for Siebel Enterprise Server components 1

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

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

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

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

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

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

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

Stop all running Siebel Servers by running the command stop_server on each applicable server computer. (See Siebel System Administration Guide for details on how to use this command.) Also shut down any running instances of the Siebel Server Manager (srvrmgr). If you are patching an instance of Siebel Management Agent that was previously installed with a Siebel Server, also stop the service for the Management Agent. Unload libraries from the system cache by running the command reset_server all on each applicable server computer. (See Siebel System Administration Guide for details on how to use this command.) Stop the Siebel Gateway Name Server by running the command stop_ns. (See Siebel System Administration Guide for details on how to use this command.) (AIX only) Verify that the login ID performing 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, then to the directory where the installer is located. For Siebel Enterprise Server, navigate to Siebel_Image/ UNIX_OS/Server/Siebel_Enterprise_Server, where:

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

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

ompmnctl stopall - for Oracle HTTP Server (on AIX or supported Linux platforms) stopapa for other Apache-based Web servers (on AIX, HP-UX, or supported Linux platforms) stop for Oracle iPlanet Web Server (on Oracle Solaris)
2 3
Log on to the server using the Web server owner account. (AIX only) Verify that the login ID performing the installation has permission to run slibclean by asking the administrator to change the permission as follows: chmod 6555 /usr/sbin/slibclean
Open a new shell and navigate to the Siebel image location for version 8.1.1.x, then to the directory where the installer is located. For SWSE, navigate to Siebel_Image/UNIX_OS/Server/ Siebel_Web_Server_Extension, where:

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

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

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

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

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

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

This topic is part of Siebel Fix Pack Installation Instructions on page 80. 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 you installed later included an updated security adapter library file, the checksum validation will fail and Siebel Web Clients might not start, unless the value of the CRC parameter is updated. For detailed information about this task, see the topic about configuring checksum validation in Siebel Security Guide.
96
Postinstallation Tasks for the Web Server

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

This topic is part of Siebel Fix Pack Installation Instructions on page 80. After you install a new version of a Siebel application, including a Siebel Fix Pack, new versions of applicable ActiveX controls for the high interactivity client will be downloaded onto your users client computers when they run the Siebel application within the Internet Explorer browser. Alternatively, updated versions of the ActiveX controls you require can be predeployed to the client computers. This behavior applies to Siebel Web Client (using high interactivity only), Mobile Web Client, and Developer Web Client. For more information, see the browser configuration chapter in Siebel System Administration Guide. After a new Siebel software version is installed, Java controls for the high interactivity client will also be downloaded. If caching is enabled, cached versions of these controls 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, then click Reset.
97
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 Siebel System Requirements and Supported Platforms on Oracle Technology Network. The JRE can be downloaded automatically to your computers. As described in 475457.1 (Article ID) on My Oracle Support, some configuration might be required in order to download the correct version.
Postinstallation Tasks for Supporting Additional Languages

This topic is part of Siebel Fix Pack Installation Instructions on page 80. If you are installing an additional language into an existing version 8.1.1.x installation, review the information in this topic, in case it applies to you. For more information about adding languages, see About Installing Additional Languages on page 84.
Importing Locale-Specific Data into the Repository

Sometimes it is necessary to update the text strings held in the repository for a particular language or for multiple languages. These text strings are held in the Symbolic String Model (SSM) table, and appear on-screen as labels for tabs, fields, and so on, across all Siebel Business Applications. 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 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 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.
98
Select a source language and a target language. The source language is the language of the locale-specific data in the LMU file you are importing. The target language is the Siebel language into which the strings will be imported.
3 4
Click the Import tab. Enter the name of the LMU file from which you want to import locale-specific attributes. You can also use the Browse button to find and select the file.
Specify whether you want to mark records in the repository with the Redo flag that have changed since the export occurred. When the import occurs, the LMU compares the source language records in the repository with the source language records in the import file. If the records in the repository have changed since the export occurred, they are marked with the Redo flag. This flag helps you identify records that 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 80. This topic describes how to uninstall Siebel Fix Pack 8.1.1.x releases for Microsoft Windows and for supported UNIX and Linux platforms. Generally, a Siebel Fix Pack 8.1.1.x release installed on top of version 8.1.1 (or a prior 8.1.1.x) can be uninstalled. When you uninstall a Fix Pack, you revert to the version 8.1.1 base installation. The uninstaller prompts you whether you want to uninstall just the Fix Pack (and revert to version 8.1.1) or perform a full uninstallation of the installed software. CAUTION: Separate uninstallation of a Fix Pack is not supported for Siebel Mobile Web Client or Siebel Tools. Only the full uninstallation option is possible for these modules. Fix Pack uninstallation for modules not mentioned here is generally similar to what is described here. To perform a full uninstallation of a Siebel module, follow the uninstallation instructions provided in the Siebel Installation Guide for the operating system you are using. This topic contains the following subtopics: Scenarios for Uninstalling a Siebel Fix Pack on page 100 Instructions for Uninstalling a Siebel Fix Pack on page 100 Guidelines and Limitations for Siebel Fix Pack Uninstallation on page 101
99
Scenarios for Uninstalling a Siebel Fix Pack

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

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

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

To uninstall a Siebel Fix Pack on UNIX or Linux, run the following command: $SIEBEL_ROOT/_uninst/product/uninstaller optional_arguments where:
product is one of the following values: ses (for Siebel Enterprise Server components) or eappweb (for SWSE)
100
Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B Resolved Change Requests
optional_arguments is one or more valid arguments for the uninstaller. For example, specify -is:javaconsole -console to run in console mode.
At the prompt, select Maintenance Release Uninstall.
Guidelines and Limitations for Siebel Fix Pack Uninstallation

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

The table in this topic provides a list of resolved bugs that are included in the Siebel 8.1.1.7 Fix Pack. Customers using version 8.1.1 or a prior Siebel Fix Pack 8.1.1.x (where applicable) should install the latest 8.1.1.x Fix Pack. NOTE: As of the Siebel 8.1.1.5 Fix Pack release, the Siebel Maintenance Release Guides are versionspecific. For a list of bugs that were resolved in the Siebel 8.1.1.1 through 8.1.1.4 Fix Packs, see Siebel Maintenance Release Guide, Version 8.1.1.x on My Oracle Support. For a list of bugs that were resolved in the Siebel 8.1.1.5 and Siebel 8.1.1.6 Fix Packs, see Siebel Maintenance Release Guide, Version 8.1.1.5 and Siebel Maintenance Release Guide, Version 8.1.1.6 on My Oracle Support. To access these guides, from within My Oracle Support, navigate to the Knowledge tab, and search for Article ID 880452.1. Unless specifically noted in the table, all known anomalies from the base version remain unresolved. For each release, the resolved changes tables include the following columns: Issues Addressed. The description of the issue. Bug ID/Fix Request ID. The tracking number for the fix request associated to the product defect. Base Bug ID/Change Request ID. The tracking number for the product defect associated with the fix request. 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.
10 1
Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B Resolved Bugs in the Siebel 8.1.1.7 Fix Pack
This section contains the following topics: Resolved Bugs in the Siebel 8.1.1.7 Fix Pack on page 102
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack

Table 44 lists the bugs that were resolved in the Siebel 8.1.1.7 Fix Pack. Table 44. Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID Base Bug ID Subcomponent Special Instructions
Issue Addressed
Siebel Apps Customer Order Management

Customizable Prod/ Configurator
Modifying a bulk request yields an error message that the deleted item field is not present When remote product configurator is enabled and is running a script with the BatchValidate method, the output property set contains an empty Original Instance when there is a constraint rule broken The Check Eligibilty Helper step invokes the wrong signal When a child record is removed, the grandchild record is not removed as well BatchValidateDetailedExpl crashes if a product has a minimum quantity violation and any rule is activated 12801963 APIs
10589378
10587003
APIs
12800345 12826991
Eligibility & Compatibility Rule Behavior
10583881
Rule Behavior
102
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 12420803 Base Bug ID Subcomponent Runtime Special Instructions
Issue Addressed ACR 502: The Quick Edit web template is not packaged with the installation files ACR 471: The UMF message is not reflected properly and promotions are not selected Child products that have been defaulted by min cardinality do not have NULL in the CFG_STATE_CD column The NoSave property does not work Within Product Configurator, when users enter an attribute value with the LineItemICField property and click Done, they receive the SBL-BPR-00162 and SBL-EAI-04381 error messages When users create product constraints in the Admin Product view, the application crashes When pick applets are used to populate attributes, Dynamic Hide functionality does not work When users exit eConfigurator within the Financial Services application, the focus is lost The cell height of the Required Attributes label is not the same as the cell height of the Optional Attributes label
12847176
12560619
Runtime
12399998
12397774
Runtime
12751510 12398737
10601639
Runtime Saved Configurations
12806588
11717572
User Interface
12809668
User Interface
12914220
User Interface
12415574
User Interface
Order Administration
Agreement Approval functionality uses the wrong email template 12750196 Quote/Order Validation
Pricing Mgmt
10 3
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 12723829 Base Bug ID Subcomponent Price List Special Instructions
Issue Addressed The price is displayed incorrectly within the NRC field within line items
Product Administration
Action Code updates are not supported when editing simple products with attributes The RCOIS GetAttribute method returns attribute values that have not been translated into the display value for an enumerated attribute definition 10592171 10591152 Product Attributes
10595715
10594080
Product Attributes
Product Promotions
Order line items are not created properly when they are created using Favorites functionality ACR 471: The Default Attribute Creation feature does not work for remote configurator When the Apply Promotion method is used within the Headless Configuration business service, an incorrect output product structure is created if the input product structure contains any nonroot products Allows users to disable a full table scan on the S_ASSET table IntegrityCheck does not pick up migrated assets Negative price overrides within the Edit Promotion applets are totalled incorrectly 10588017 10587582 Administration
10597624
10595493
Administration
12852048
API
13043868
Runtime
12996503 12902863
Runtime Runtime
PSP Engine
104 Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 12857820 Base Bug ID 10585340 Subcomponent PSP Procedures Special Instructions
Issue Addressed In version 8.1.1.5, within Siebel Pricer, the Internal Integration functionality does not work properly When users add a product to a quote, they receive the SBLBPR-00158, SBL-BPR-00162, or SBL-PSP-00831 error messages
12937371
12723829
PSP Transforms
Quotes & Orders

When assetizing an upgrade promotion. the SIS OM Apply Completed Service Order Line Item to Service Profile workflow calls the ISS Promotion Agreement Management Sub Process method, and it crashes during the CalculateDates step If Inclusive Eligibility is checked for a product, Configurator throws an error message When users remove all records from the Sales Order view, navigate to Site Map > Sales Order > Line Items view, and click the View New button in the child applet, they receive the following error message: Invalid operation when not executed (SBL-DAT-00471) If the PSP Engine/workflow is not used for pricing, the Extended Quantity field is not updated appropriately 12705438 Asset Based Ordering
12794483
10605987
Eligibility & Compatibility
12914620
12914658
Orders
10571055
10569588
Pricing
Siebel Apps Data Quality

Data Quality
10 5
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 13065192 Base Bug ID 10603335 Subcomponent Batch Deduplication Special Instructions
Issue Addressed When a record (such as an account, an address, or a contact) has an apostrophe or a special character, the application does not recognize the special character, and records error out when a batch is processed The Data Quality real time deduplication functionality fails and displays an error ACR 761: Provides a Data Quality sync switch When an account, address, or contact record contain a special character, the SBLDAT-60236 error message appears Previously-created records are not visible in the Duplicates view
12324343
Data Quality
12618902 13065076 10577129
ODQ Connector Universal Connector
11938030
Universal Connector
Siebel Apps Field Service

Activities
The FS Holiday Service API GetReponseTime method returns incorrect results The Done field information for an activity is not synchronized to the server Holiday APIGetElapsedBusinessTime does not work properly for different timezones 12596631 11823910 Activities
12659425
11769292
Activities
11788501
Activities
Field Service
Using the browsers Back Button causes inefficient queries against S_EVT_ACT 10554464 10541485 Dispatch Board
106
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 10571883 10601195 Base Bug ID 10571435 10600250 Subcomponent Dispatch Board Dispatch Board Special Instructions
Issue Addressed A memory leak occurs on the Dispatch Board When users access the Dispatch board, the application hangs Within the FS Holiday API Service business service, the GetElapsedBusinessTime method yields incorrect results When users input incorrect data in the shipped line for a product, and then delete the data, an error message occurs and the transaction is not committed to the database
10606526
10599378
Home Page
10585770
10582454
Shipping
Siebel Apps Handheld Client

Handheld Client
The ScanAPI.dll file does not load error messages on the Motorola embedded barcode scanner When users drill down, context is lost TAG:GetDirect does not retrieve multiple fields at once from the database 12810013 12720131 Barcode
11795432 12411534
10602136 10592042
Client App Printing
Handheld Sync
Duplicate transactions and data corruption occur Translation problems occur when strings contain words that are glued together (such as PatchAgent) 10592695 12857245 10591333 Direct Server Sync Patch Deployment
10 7
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 10596115 Base Bug ID 10595588 Subcomponent Patch Deployment Special Instructions
Issue Addressed Makes sure that other Siebel .exe files are closed when PatchAgent needs to be started manually
Siebel Apps Marketing

Mktg/Campaign Mgmt
Campaigns partially fail with the capacity warning Different customer ids that exist in S_MKTEVTRG_HST are not loaded in S_CAMP_CON 12703358 12534286 Campaign Processing Campaign Processing
Mktg/Email Marketing
When users save an offer template multiple times, the trackable URL stops working 12604183 Email Editor
Siebel Apps Multichannel Technologies

Communications Server
HTML templates are truncated for Email Activities Within the Send Communications applet, when users press F9 or click on the Body drop-down list, when there are around 1000 templates, it can take a while for the email client or body drop-down list to appear 10573591 Outbound Communication Email Templates
12887912
CTI
108
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 12937764 Base Bug ID Subcomponent Custom Drivers Special Instructions
Issue Addressed Siebel Agent web sessions time out when an agent is on a phone call or is chatting There is no configuration option for logging out of orphaned sessions
10592992
10571641
Server Configuration
Email
When an email has extra characters in the "ContentType: application/octetstream; name=" section, inbound emails arrive over and over every five minutes With E-mail Response, unable to get proper substituion fields when using F9 When users select a list of accounts in the Account applet and press F9, if one of the accounts does not have any contacts, only the first account that the users selected appears, and the rest of the accounts are not populated in the email form 12530877 Email
10596275
10591050
Email
12828709
Send Email
eMail Response
Emails are rejected as Incomplete Header Line 10582649 10579692 Mail Server
Siebel Apps Oracle Customer Hub

Universal Customer Master
Errors occur while attempting to import PLK Symbolic Strings (ACR475_LMU_PLK.txt) 12556743 Other
10 9
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID Base Bug ID Subcomponent Special Instructions
Issue Addressed
Siebel Apps PRM

PRM Partner Manager
If there is an apostrophe in a prospective partner name, an error can occur when users click the Qualify button Within Administration Partner > Prospective Partners view, if the address of the prospective partner is a duplicate, partner qualification fails 10547826 10543941 Error Messages
10569529
10567133
Partner Admin
PRM Partner Portal

When the application is stopped and then resume, answers that have already been submitted are not retained When users click the Recall button after having submitted partner program information, the application relaunches, but all of the values that were entered are lost 12573896 12432848 Other
10598235
10551381
Partner Programs Screen
Siebel Apps Sales

Dun & Bradsteet
D&B fails to promote accounts with duplicate addresses 13066937 10578577 Promote
Forecasts
Forecast Summary is not refreshed when Update Detail with Revenue Item is used 10592919 10588932 Forecasts
110
Table 44.
Issue Addressed
Siebel Apps Search & Knowledge Management

Search - Oracle SES
Users can search with an attachment name but not with the contents of the attachment Long columns are indexed as content links rather than as attributes OSES searches do not return the number of records on the Records applet When users click on the Advanced Search link, data is lost 10587092 10585429 Core Oracle SES
10596898
10592900
Indexing
13019417
Results UI
10582433
10582367
Saved Searches
Siebel Search
With the implementation of the German umlauts character content search, blank dates occur when Fetch LanguageSpecific Docs is selected in Search preferences When users click on search results, changes that they have made are not saved Search crashes when users navigate to the All Accounts Across Organization view 13252298 Results UI
12536584
11668672
Search Center
12795298
Search Center
Smart Answer
Provides Microsoft Windows 2008 R2 support for Smart Answer 13023227 11767223 Smart Answer
11 1
Table 44.
Issue Addressed
Siebel Apps Self Svc: ADF

E-Commerce
After ACR 502 has been applied, the Self-Service eCommerce application does not work properly Attachments of type URL are not displayed in eSupport SR Detail Page 12322627 12429365 Other
10597748
13086583
Other
Siebel Apps Service

Assignment Manager
Within Assignment Manager, comparing an object to Person/Organization does not work for Campaign Contact 10548372 10542838 Batch Assignment
Service Requests
When users drill down on a newly-created service request, the application crashes 13090158 10589090 Related SRs
SmartScript
SmartScript questions associated to an MVF field do not refresh correctly when users press the Enter key 10581920 10506510 SmartScript
Siebel Apps Territory Management

Territory Management - Sales
112
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 10598582 Base Bug ID 10597734 Subcomponent Territory Management Special Instructions
Issue Addressed Users are unable to add multiple conditions in a Territory Alignment created by another user
Siebel Apps UCM

Universal Customer Master
When a guided merge is performed, survivors do not remain in the Duplicates view Improves the quality of error messages in the IAI category Errors occur when users click Merge within existing duplicates When an address is added to an account and a contact, the sdq dedup no memory error message occurs 12802129 Merge Request
10566294 12998690
10566293 12901373
Other Other
12982010
12887716
Other
Siebel Charts
Charts
When users click twice on the Go button within the Chart applet, a blank chart displays 10588465 10585178 Chart Engine
Siebel Communications & Energy

Integrations
11 3
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 13081720 Base Bug ID Subcomponent AIA Special Instructions
Issue Addressed When users create an asset for an account with Billing Profile/ Service Id information, navigate to the Account screen, modify the Billing Profile/Service Id information, and submit the order, ListOfSWIOrderItemPreviousV alues" section is blank
Siebel Consumer Goods

ADL
ACR 480: Copy should be disabled when selecting multiple target accounts In CSSBCCopyADL::CopyADL method, the service is never released and set to NULL, which can cause a memory leak 12916136
12742166
Promotions
A couple of member variable business components are not initialized to NULL in the CSSAccntPlanSvc class, so destructor releases them In Admin Data > Account Product > Price List, when users click the Update Price/ Cost button, too many records appear, and performance suffers 13068408
13069081
Retail Execution
For targeted pharma accounts, within the Objectives view, when users click the Apply button, calls are not generated for the target account 13069220
114
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 13068452 Base Bug ID Subcomponent Special Instructions
Issue Addressed If no active merchandising location is selected, the application crashes
Siebel Core - EAI

Integration Transports
The user credentials in the jndi.properties file are stored in clear text format JMS Receiver Auto Restart parameters do not allow users to specify when a component tries to reconnect 13080056 JMS
12959596
11738656
JMS
MQ
Allows the Siebel application to receive an inbound message from MQ, process it, and provide a message response with a value for the MQMD_R_Out_CorrelId header, so that the value from MQMD_R_Out_CorrelId can be set as the next outbound message to MQ as the MQMD_S_In_CorrelId to match up the requests 12622626 MQ
Integration Business Services

ACR 750: Extends the Siebel Web services framework to provide an endpoint through Oracle WLS For certain predefined queries, once an empty PDQ is entered, when users execute a query after the empty one, their query does not return any records 10589245 10581466 EAI Server Components Yes, see Instructions for ACR 750 on page 58.
12629343
Other
11 5
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 10603642 Base Bug ID 10591549 Subcomponent Other Special Instructions
Issue Addressed The EAI Siebel Adpater/EAI UI Data Adapter ignores PDQ Sort Spec
Java Integration
Business service migration fails for the QueryBid method Modified XSDS do not work with REST because Clear Cache is not called There is no automation script for outbound configurationN A deadlock occurs while deleting RA+MDB on WLS There is no option to set the log level for outbound JMS logs Not needed Deployment fails for REST designed with XSD The log location mentioned in EJB-JAR.xml is misleading When the proxy method is the template like method (A arg1, B arg2, A arg3), the wrapper fails to compile ACR 543: Integration objects listed in the Base Integration Object field are not sorted alphabetically ACR 543: Provides a query option to retrieve required workflows in the Choose Workflow screen 12920858 13345955 Resource Adapter Resource Adapter
12691178 13247719 13085517 11733621 13085601 13337550 13247734
11733621
Resource Adapter Resource Adapter Resource Adapter Resource Adapter Resource Adapter Resource Adapter Resource Adapter
10591253
10591252
Resource Adapter
10591466
10591460
Resource Adapter
Web Services
116
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 12727594 Base Bug ID 12673517 Subcomponent Inbound Special Instructions
Issue Addressed When users generate WSDL for any inbound Web service from any non-Windows environment, import it in the SOAP UI and send a request for query method, a blank page displays and users receive an error message When an invalid value is passed to pagesize, the application crashes instead of providing an error message Requests greater than 25 KB are not being returned from inbound HTTP requests In the fix for Bug 12763892, the business object is not released for the Leads service, which causes performance issues Outbound Web services do not work when calling a method that is hosted on WLS
12953834
Inbound
12736823
Inbound
13063284
Inbound
10605839
10584990
Outbound
Siebel Core EIM/Database

Database
On Solaris 10, with 250 users, Call Center performs well for a few hours, but then users receive a connection limit exceeded error message from Siebel Web Server Provides Siebel Connector fixes for IBM DB2 UDB and Oracle databases to address Bug 12985589 and Bug 12676475 10631899 Connector
13384863
13384850
Connector
11 7
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 10591636 Base Bug ID 10591201 Subcomponent Connector Special Instructions
Issue Addressed The Object Manager allocates buffer memory for the CLOB data type based on the size of columns and not based on the size of the data An Oracle Connector CLOB + OCI descriptor leak occurs In DB2/ZOS V10, the changed catalog table SYSIBM.SYSTRIGGERS catalog table was changed in a way that made it incompatible When resuming a task, fields that have the DATETIME type no longer hold their original values In version 8.1.1.6, on Microsoft Windows 2008 R2, the Generate New Database job does not terminate and continues running
13024449 13088789
10597810
Connector IBM DB2/400
12800053
MS SQL Server
12995880
12355084
MS SQL Server
Siebel Core Handheld Sync

Handheld Sync
When the connection between the PDA and the server breaks, the Sync OM task continues running and does not terminate Provides the server-side fix for Bug 12364796 With WM 6.5.3, the Customize tool bar screen is distorted With WM 6.5.3, after the initial sync, when users lauch the application, the resolution is not correct 12925053 12364796 Session Admin
12925628 12734984 12734477
12860325
Session Admin Session Admin Session Admin
WebPhone
118
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 12784519 Base Bug ID 11728298 Subcomponent HTML Special Instructions
Issue Addressed Records that contain a + sign in row_d cause the Wireless application to crash Allows for read-only to be applicable to a TextArea control as well as a Text control
12572213
WML Thin Client
Yes, see Instructions for Bug 12572213 on page 148.
Siebel Core - PIM Integration

Client Sync
In the Polish application, when there are sync conflicts, the client hangs with the "out of memory" error message Corrects the translation.txt file installed for the Portuguese (Brazil) language 12810197 Lotus Notes
12922570
Lotus Notes
CRM Desktop
The copyright information is not displayed correctly Provides a mechanism to upload an entire metadata package in a single file Error message for invalid packages are not translated to Japanese Recurring event exceptions are not reflected in attendee calendars When users create a new meeting, invite attendees, send the invite, and then sync, a sync issue appears Duplicate calendar items are created if an attendee is added after the first sync 10587345 12831330 12831319 Admin Admin
12597920
Data Sync
13341578
11729977
Data Sync
13477759
Data Sync
13391431
Data Sync
11 9
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 12997576 Base Bug ID Subcomponent Installation Special Instructions
Issue Addressed On Microsoft Windows 7, the CRM Desktop shortcut does not launch the CRM Desktop Garbage characters display on the installation page Allows non-ENU users to launch the Siebel application from CRM Desktop using the URL that matches their chosen language by defaulting the eai_XXX URL to the chosen language There is an installation limitation when a user has multiple Exchange mailboxes in a single profile Adds the client version to the MSI Installation file's properties so that it is easy to determine. The New Email button is not the same as it was in previous versions Installation fails if the user's AppData folder is a UNC path In the Hebrew application, within the Account Entry applet, the Address Created date value is incorrectly formatted Non-primary employees can delete activities When users try to connect to the incorrect server, the resulting error message is not translated to Japanese
12423742 11742817
Installation Installation
13392118
Installation
13018849
Installation
13397152
Installation
10606202 10590982
Installation Outlook Client
10597053 12418939
Outlook Client Outlook Client
120
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 10590813 Base Bug ID Subcomponent Outlook Client Special Instructions
Issue Addressed In the Hebrew application, the content within the First Run Assistant > Settings wizard does not display from right to left In the Hebrew application, witin the First Run Assistant wizard, the check boxes appear on the wrong side In the Hebrew application, the Importing Package progress bar does not display from right to left In the Attachment filter, some of the values in the Field dropdown list are not translated into Japanese With "process_attachments" turned on, an invalid duplicate attachment is created. The CRM Desktop button launches the incorrect Siebel application If a toolbar has been customized, an invalid pointer error occurs during download When users click the Share bar to unshare a contact, after users click Yes in the confirmation dialog box, the contact is still shared Within the Control Panel > Confirm Synchronization tab, messages are not in Japanese After CRM Desktop 3.04.20.08 has been installed, the Next Item (CTRL + >) and Previous Item (CTRL + <) functions do not work once an email has been opened
10590807
Outlook Client
10590815
Outlook Client
12533099
Outlook Client
13393305
Outlook Client
10590926
Outlook Client
11807413
Outlook Client
12533287
Outlook Client
12429544
Outlook Client
12698073
Outlook Client
12 1
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 13025363 10590997 Base Bug ID Subcomponent Outlook Client Outlook Client Special Instructions
Issue Addressed Provides Right-to-Left language support Screen alignment is not correct for right-to-left languages When issues occur after synchronization, there is no notification message to inform the user Implements forward-only cursor mode to improve performance and remove the 10,000 record limitation When the Siebel Server fetches 50 records, it takes more than 70 seconds
12429594
Outlook Client
10606075
10585409
Performance
10604267
10604196
Performance
SSSE
Adds script file for granting permissions for SSSE Service User in an Exchange 2010 environment When the calendar is updated in the Siebel application, the organizer receives a notification 13091138 13091177 Administration
10598827
10598740
Calendar
Siebel Core Server BizLogic Rules

Config - Rules
Errors occur when synchronizing from Haley to the Siebel application 12318676 Rules Engine
Siebel Core Server BizLogic Script
122
Table 44.
Issue Addressed
Config - Scripting
Calling multiple methods in a single statement on smartscript objects produces a compile error "Nested with" statement blocks do not resolve correct references Calling a task from eScript crashes the Object Manager 12865043 ST Engine
12833238
ST Engine
10549592
T Engine
Integration Scripting
Crashes occur two to three times a day on production servers Deduce Types requires a return statement in the catch block to compile 12570179 New eScript Engine
10582714
10534318
New eScript Engine
Siebel Core Server BizLogic WF

Business Process Framework
After 8.0.0.10 QF0A23 has been applied, long-running workflows that consist of several Task Uis experience performance issues 12550370 12550373 Inbox
Config - Rules
The Workflow Utilities Echo Method output property takes values randomly from other input properties Activating a workflow process in one repository inactivates a workflow in another repository 13117431 Workflow Process Execution
12658950
Workflow Process Execution
12 3
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 12591236 Base Bug ID 12405401 Subcomponent Workflow Process Execution Workflow Process Execution Special Instructions
Issue Addressed Modulus operator MOD in the expression builder does not produce correct results Unwanted SQL select statements occur when using a Siebel operation in a subworkflow
13033536
12879239
Siebel Core Server Infrastructure

Security
An error is encountered when executing the encryptupg utility for RC2 encryption when there are more than 31 characters 12995718 12324377 Data Encryption
Server Infrastructure
A core file is created when the Siebel Gateway Server is stopped 12431050 10643339 Siebsrvr and Shells
Siebel Core Server OM Frwks

Business Process Framework
When a task is paused and then resumed, data is lost 12566908 Task Transaction: Commit
Object Manager
When DB connection pooling is used, an Object Manager crash occurs in the eComm OM in SqlCursor5CloseEv event 12577313 Business Components
124
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 10602278 Base Bug ID 10485907 Subcomponent Other Special Instructions
Issue Addressed GetSearchSpec/ SetSearchSpec unable to handle strings with apostrophes in SVB
Siebel Core - UIF Client

AX/HI Web UI
Alarms do not reload consistent with the defined reload frequency The high-interactivity calendar allows users to reschedule signed calls 10586703 10584220 Calendar
10566356
10566354
Calendar
SI Web UI
Allows calendar to work after installation of non-res:// calendar implementation Within Contacts, Calendar Tool Tips for appointments do not display meeting information Addresses various issues around dragging calendar appointments Allows suppression of the timestamp for events on the 7Day calendar In the Hebrew version of the application, the cursor sticks when typing text Within the Portuguese and Spanish applications, the calendar displays in English If an employee's name contains a single quote, that employee's calendar cannot be accessed 12741601 Calendar
12838557
Calendar
12869678
10595170
Calendar
11682527
11682517
Calendar
10536337
10529645
Calendar
10605376
10605375
Calendar
12805219
Calendar
12 5
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 13082392 Base Bug ID 12730479 Subcomponent Calendar Special Instructions
Issue Addressed With the Casablanca timezone, the first weekend in April displays incorrectly When users create a contact record using copy-and-paste functionality, an error message appears After version 8.1.1.5 has been applied, the Siebel application does not send parameters to Actuate After version 8.0.0.10 has been applied, special characters appear in dropdown lists When a session timeout occurs, the application crashes An empty shuttle applet appears when users click within the application When there are two duplicate account names, importing contacts adds an entry to the first account in the contact list Within ePublic Sector, within the Service Tab > Service Requests list view, when users click New in the form applet, enter the first three letters of the contact in the Owner field, and then try to select a user in the Pick Service Request Owner applet, an error message occurs Tabs are not hidden in eService Scripts execute twice The application hangs if users click Enter instead of Alt + Enter to run a query
12831075
12578368
Controls
12822135
Controls
13095646
11810469
Controls
10545453 12807613
10537307 12653248
Controls Layout and Rendering Others
12991744
10598313
12984684
11711790
Popups
10598444 12608463 13080852
10598429 10605076 13071172
Sitemap STD:Javascript UI Behavior
126
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 12768910 Base Bug ID 12407059 Subcomponent UI Behavior Special Instructions
Issue Addressed SQL generated on the Clinical Trip Report business component does not honor search specifications On the Mobile Web Client, when EnableFQDN=FALSE, Amazon links are not visible In version 8.1.1.5, within the Accounts screen, when users add a number to a site record and then press CTRL+an arrow key or CTRL+Save, they receive an error message When users press F9 and enter text in the subject line or body of the email, some characters do not display Within a service request, when users press F9 to send an email, choose a template in the Send Communciation applet, add the contents of the email, and then send it, the email content is missing from the received email When users select multiple records by pressing Shift, not all of the records are selected
12882858
UI Behavior
12711326
UI Behavior
12772458
UI Behavior
12958059
10598010
UI Behavior
12997878
10600303
UI Behavior
Siebel Core Unix/Windows

Platform Support
ACR 698: Certifies AIX 7.1 ACR 699: Certifies Oracle Enterprise Linux 6.1 (64-bit) On Exalogic (Oracle Enterprise Linux 5.5 UEK) systems, the Siebel Server crashes during startup 13063733 13348117 12902189 AIX6L v6.1 Oracle Enterprise Linux 5 Oracle Enterprise Linux 5
12 7
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 12959307 Base Bug ID 12420463 Subcomponent Solaris 10/Sparc Special Instructions
Issue Addressed Provides a mechanism to set the default stack size for Posix threads on all UNIX platforms After version 8.1.1.6 has been installed, SWSE configuration fails The "./STARTAPA-SSL function does not work to enable SSL on the HP platform
13055566
Solaris 10/x86
12971646
11825060
Web Server
Siebel Core zSeries

Database
ACR 701: Certifies IBM DB2 v10 for z/OS The strgxtrct utility is not written to cope with the new DB2 v9 PriQty and SecQty allocations of -1 13632576 10599350 IBM DB2/390 IBM DB2/390
Siebel CRM Integration to Oracle Realtime Scheduler

Siebel Components
When more than one skill is assigned, the Siebel session hangs 12896102 Address, Employees, Activities
Siebel Data Model

Data Model
Extends the length of the DISPLAY_NAME column on S_PROD_INT_TNTX from 50 to 100 to match the length of the NAME column on S_PROD_INT 12382137 Schema
128
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 10603651 Base Bug ID 10601933 Subcomponent Schema Special Instructions
Issue Addressed EIM_PRPDTL_TNT does not resolve foreign keys for custom mapping
EIM
The eim45.sql file for 8.1.1.x Fix Packs is not the same as it is for the 8.1.1 base release While loading through EIM, an error occurs while setting the primary value 13013178 EIM Table Mappings
10560634
EIM Table Mappings
Siebel Documents
Documents
ACR 628: The Submit and Done buttons are enabled for failed correspondences 12434735 11895574 Correspondence
Siebel Engineering Release Engineering

Rel Eng/Build System
The cabinet file is unsigned in version 8.1.1.5 and in Microsoft Windows 7 and Microsoft Windows 2008 12839398 12839231 Build System
Siebel Life Sciences

Activities
The Detail button is disabled in the Call Details view 13430653
12 9
Table 44.
Issue Addressed Within the Call Execution view, the Validate button does not behave consistently The system allows enables capturing signature on paper and call submission without any samples The Interactive Detailed button is disabled in the UI. Within the Chinese application, the confirmation message that appears after users submit a contact call is translated incorrectly
13431474
13430280
13500588 10579125 10572611
Clinical Programs/ Protocols

The Primary Investigator Site Contact information is not updated if the contact last name is the same as an existing contact 12725239
Clinical Project Mgt

When a user other than the admin user adds a team member within the Team MVG applet and then click Save 13248257
Handheld
Allows users to disable buttons within Pharma Handheld 11677627 10606138
License Key
Customers who have Call Activities option enabled should be able to view the call execution views 13078935
PCD - Interactive Detailer
130
Table 44.
Issue Addressed Within Contact > Contact Call, when users create a new call and click for Interactive Detailing, when they click the Close button in the ID dialog box, the ID dialog box does not close Within Interactive Detailing, clicking the Sign button does not call the Signature method
13450272
PCD - Message Planner

The Activity ID field accepts null values or any junk values provided No error message displays when users do not provide information in mandatory fields The Comments field accepts more than 250 characters The Done field accepts values other than Y and N Within the Sales Assessment Template Web service, field validation is missing for a few fields Not all of the values for the Follow Up picklist display The Sales Assessment Template Web service shows all operations in the UI 13373693
13373799
13373712 13373669 13386254
13373760 13375345
Product Issues
ACR 712: The Device Available field information contains values other than Yes and No ACR 712: The Send to Safety button sends incorrect data 12943304
13085829
13 1
Table 44.
Issue Addressed
Samples
Smart Calls with Promotional Items do not work as expected. 12757663 10601541
Samples - Disclaimer Mgmt

Product Allocation Identifier should not be a mandatory field 12371182
Samples - Handheld
When users adjust sample quantities on the PDA, they receive an "end of file" error message 12586387
Samples - Signature Capture

ACR 731: Supports signature capture using the CIC component on the Windows 7 platform 11869400 Yes, see Instructions for ACR 731 on page 55.
Site Management
ACR 839: Provides enhancements to capture the geographical details of a site ACR 839: Provides Web services to provide information about protocols, sites, and site visits when they are created in CTMS to other applications used in biotechnology and pharmaceutical companies 12998082 Yes, see Instructions for ACR 839 on page 71. Yes, see Instructions for ACR 839 on page 71.
12998073
Smart Calls
Products in smart calls are not applied 10604049 10578468
Web Services
132 Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 12976643 Base Bug ID Subcomponent Special Instructions Yes, see Instructions for ACR 762 on page 62.
Issue Addressed ACR 762: Ports SonGo Web services to Siebel applications version 8.1.1.x for iSales
Siebel Loyalty
Accruals
When the Process External Transaction method of LOY Accrual Services is invoked through Web services from SOAP UI with Request Mode as Simulate, the ACCRUED VALUE field in the output xml does not show decimals and only shows integers Within version 8.1.1, points round if the points value is a decimal value Decimal points are not rounded up 12845264
10570794
10570253
10600607
Member Administration
ACR 802: Provides Bulk Administration enhancements and redemption concurrency functionality Bulk Admin functionality only processes 11 records in a set when bulk unit size is greater than 11 The Bulk Admin Membership process remains in the InProgress state even after a workflow is activated There is no Go button in the Bulk Admin applet, so users have to press Enter to run a query 12558122 Yes, see Instructions for ACR 802 on page 69.
13039511
12997281
13039598
13 3
Table 44.
Issue Addressed The error log shows duplicate invalid member numbers when at least one member is valid in a set defined by Bulk Unit Size Incorrect validation error messages occur when users click the Process button The Member Merge functionality does not merge or combine enrolled promotions Merge actions do not work for member field attributes On the Solaris platform, Bulk Admin functionality appends \A to the file name
13039569
13027135
10562859 13034597
Member Services
Within the Loyalty Member screen, when users create contacts and do not provide enough information, the application does not navigate them back to the Loyalty Member screen to enter the missing information 12583802 10593362
Other
Within Administration > Product > Products List > More Info > Points, users cannot insert decimal values in the Point field Slow SQL occurs for the LOY All Transactions view "10547259
12664236
10605463
Partner Administration
The end date is not considered for the Precalculated Accrual condition 12952157 12952144
134
Table 44.
Issue Addressed
Promotions
The Does Not Equal and Empty conditions do not perform as expected Allows for an integer division operator in the promotion rule definition.txt file Allows calculations not to round to two decimal places Allows calculations not to round to two decimal places 12948668
10501048
10515441 10525601 10515441
Redemptions
Resolves a problem with concurrency in the redemption process When 100 postings are initiated for the GetPriceOption scenario, each posting takes 25 to 38 seconds Users cannot redeem decimal values while processing redemption transactions 12663663
12664159
12338939
10581810
Tiers
Allows users to set up Assign Points and Redeem Points actions within Tier Promotions 12663588 Yes, see Instructions for Bug 12663588 on page 145.
Siebel Reports
Reports BI Pubisher App
The XMLP Purge Records workflow does not delete all of the reports 11828119 11824462 Call Center
13 5
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 12931618 Base Bug ID 12629343 Subcomponent Common Components Common Components Internationalization Special Instructions
Issue Addressed After users run a report that contains no rows, the following reports also return no rows After users run a report that contains no rows, the following reports also return no rows Users cannot execute BI Publisher reports for languages that have not been shipped
12931619
11830300
Reports BI Publisher - Infra

On the Mobile Web Client, reports that are created in the Custom Templates view do not appear Users are not able to configure or specify the maximum threshhold for the number of parameters Allows users to rename Report menu labels Within the Report business service, the AttachEntity method does not function properly The Parameter applet does not display scroll bars BIP Report Wait Time is not supported for Scheduler and on the Dedicated Client\ Multi Org Reports are not solely based on the Organization field within the Reports - Custom Template view 11773795 10595951 Connector
12627637
Connector
11886536 11733042 10577265
Connector Connector
13442150 11723184
Connector Connector
12907125
Connector
136
Table 44.
Issue Addressed Adding responsibilities through Siebel security model should only query for XMLP* responsibilities, not all 700+ responsibilities It is not possible to run multiple-language reports on a single object When duplicate report names are entered, the incorrect error message displays Within the Administrator - BI Publisher Reports > Reports Custom Templates screen, when users create a custom template with a different naming convention for RTF and XLIFF files and click Upload, they receive the following error message: "Report XLIFF file must have filename in "<Report Template Filename>_<Locale Code>.xlf" format (SBL-RPT50584) Includes a method on the Report business service to enable reports that are submitted using a business service to be automatically sent to email recipients that have been defined on the BI Publisher server Includes a method on the Report business service to enable scheduled reports submitted using a business service
12384180
Connector
11733031
11731294
Connector
11773906
Connector
12627598
Connector
12627588
Connector
13 7
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 12627610 Base Bug ID Subcomponent Connector Special Instructions
Issue Addressed Includes a method on the Report business service to allow reports submitted through a business service to be sent to a delivery channel (such as ftp, webdav) that has been defined on the BI Publisher Server In version 8.1.1.6, within <Tools Install location>\REPPATCH\BIP_811 5\SIA\REPOSITORY, the SIF files are incorrectly named Provides enhancements to the My Reports view When no search specification has been given, no error message displays for a nonprimary integration object The successful-upload error message does not appear when users upload a template for the first time Parameter labels are not aligned correctly in the Parameters dialog box Parameterized reports are not supported in Scheduler When a user without the XMLP_Developer responsibility tries to generate a report using a template, the application window refreshes and becomes smaller instead of yielding an error message that the user does not have the XMLP_Developer responsibility The Report business service does not have the Custom Report Name Input property
12971470
Connector
12780408 11731294
Connector Connector
11773937
10596309
Connector
11901290
Connector
11723728 13469718
Connector Connector
12627606
Connector
138
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 12627683 Base Bug ID Subcomponent Connector Special Instructions
Issue Addressed Report parameter LOVs are restricted to the Report business object Within the My Repors view, the status of In Progress is invalid Within the Report Template Registration applet, when users click Upload, there is no confirmation message Within the Report Template Registration applet, when users click Upload, there is no confirmation message Query strings are not passed as part of XML The BI Publisher Report business service does not launch on the Mobile Web Client The BI Publisher Report business service does not launch on the Mobile Web Client Users cannot set HTTPSleepTime for BI Publisher integration When the BIP Report Wait Time threshold is exceeded, the popup window that displays is not in focus Reports that are created in the Custom Templates view do not display on the Mobile Web Client When users try to create a new report with the same name as an existing report, they do not receive an error message
10562579 10551927
10551799
Connector Connector
10551928
10551927
Connector
10594924 10562793
10559184 10562792
Connector Connector
10562792
Connector
10606449
10571200
Connector
10590983
10587343
Connector
10595951
10595950
Connector
10596309
10596288
Connector
13 9
Table 44.
Issue Addressed Reports fail when the ''> Today () AND < Today () +365' fuctions are used within the Close Date field It is not possible to disable BI Publisher Reports Scheduling option When reports are scheduled with an MLOV-enabled XMLP_RPT_SCHEDULE_MODE, all reports run immediately It is not possible to upload multiple .xlf translation files.
12425291
10604432
Connector
11684153
10605466
Connector
10605829
10605732
Connector
Error Messages
Allows users to be able to create new records in the Attachment business component based on the parent business component record Within My Reports View detail applet, the View Mode field is not populated Error messages in the Schedule applet should use Toggle Case to refer to labels Search specifications fail for custom templates with multiple integration objects Executing a BIP reporexpression on the secondary integration object fails with the following error message: SBL-DAT-00224: An error with an invalid syntax for a business object query has occurred BI Publisher does not execute in "Forward Only" mode 13105473 Error Messages
13105398
Error Messages
11653426
Error Messages
11854060
11731294
Error Messages
11802808
Error Messages
10594954
10585407
Error Messages
140
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 10596205 10596208 Base Bug ID Subcomponent Error Messages Error Messages Special Instructions
Issue Addressed Report name validation messages are not translated The Job Name validation message is not translated within the Report Scheduler window
Siebel Server Remote

File System
When users update an attachment, an error message appears 10596946 10591947 Attachments
Remote
Upgrade Wizard fails with the "Unable to uncompress file" error message In certain cases, DB Xtract does not create a required records in s_node_pref Allows the client executable KIT for patch deployment to be created on the Siebel application when it is running on the UNIX platform Within DB Server Configuration screens, there are buttons with no strings Transaction Processor does not delete EIM DX files Database performance degradation occurs when queries use S_DOCK_TXN_SET On the MSSQL database, the TxnProc component fails with an error message 10596340 10594120 DB Init
10578939
10574894
DBxtract
13003564
12757714
Other
Yes, see Instructions for Bug 13003564 on page 145.
10568170
10555174
Other
12937222 12553093
10499137
Txn Processor Txn Processor
12369618
10578784
Txn Processor
14 1
Table 44.
Issue Addressed
Siebel Travel & Transportation

Availability and Pricing
Within the TNT SHM FSI Out of Order view, users cannot create a new Out of Order record 12907010 13090315
Diary
Within User Preferences > Function Space Diary screen, the Color Display By field should not have the default value defined When users navigate to a diary for a property that has reserved bookings and more than one visible frame of Function Spaces, when they use the double-scroll-down button and drill down on the Function Space Reservation link, Internet Explorer crashes The Function Space Diary view does not display correctly with Time Scale as "Month/Day-ofWeek Part" and "Week/Day/ Day Part" Users are not able to set up modified icons in Function Space Diary The Diary functionality fails when users query for a specific date 12906967 13090315
12955227
13090315
12876544
13090315
12876539
13090315
12857901
Error Message
When users drag and drop over an existing booking, they receive an error message 13419996
142
Table 44.
Issue Addressed
FS Administration
Within the Function Space Diary screen, when users query on a property without changing the date, function spaces do not display 11818894
Functions
Allows the user to disable the Assign to Category option on the right-click menu When users attempt to cancel a function, they receive an error message 13415909 13415880
12654431
12608701
Inventory
Users are allowed to reserve a specific space multiple times 12926373 12921815
Orders
Non-core function line items do not display in BEO reports 13006790 13090315
Orders/Functions
Within Orders > Functions > Line Items, when a line item does not contain any records, the Add Item button is disabled Within Event Order > Function, the Add button does not perform as expected When users click the Split Check button, they receive an error message 12312702
12756997
12807436
Other
ACR 575: Provides enhancements to the Diary functionality 10561607 Yes, see Instructions for ACR 575 on page 16.
14 3
Table 44.
Issue Addressed
Properties
Within the TNT SHM Property Projected/Blocked list applet, when users click the Query Date button, execute a blank query, and then press CTRL+S, an error message appears 12899450 13090315
Property Admin
The Apply Package button is not disabled for NFLI whose applies-to information is CMP 13086795 13090315
Quote
If Package Non Function line items contain menu items, an error occurs when users try to apply the meeting package Within the Quote > Timeshift Summary view, when users select the Accept Shifted/ Reject Shifted menu option, room blocks are not accepted or rejected Inline changes to Arrival Date information for a quote do not change a meeting package's Start Date information When users create a quote from an opportunity, a full table scan is performed on the S_OPTY table, which causes performance issues Reapplying packages also recreates the functions 12970701 13090315
13367536
12913708
13090315
12733277
13028585
13090315
Reports - Hospitality
Within Account Profile reports, the Account Discount field only recognizes integers 10603524 10603523
144
Table 44.
Resolved Bugs in the Siebel 8.1.1.7 Fix Pack Bug ID 10604999 Base Bug ID 10604146 Subcomponent Special Instructions
Issue Addressed The $ symbol does not display for the Rate field
Room Block
When users drill down from Quotes, the New button is disabled on Room Block line items Within the Room Block applet, when users click New to add a new room block, the value in the Projected field does not default to 0 11932544
10603618
10603617
Instructions for Bug 12663588

Log into Siebel Tools, search for the LOY Tier Processor business object, and add the LOY Partner Account Debit business component to it.

CAUTION: If you have applied the Siebel 8.1.1.6 Fix Pack, and have followed the configuration instructions for Bug 12757714, you do not need to perform this procedure. Use the following workaround to address the issue:
Navigate to <Tools Install Directory>\BIN\ENU, open the tools.cfg file, and within the [Siebel] section, make sure that the SymStrPrefix entry has been set to SBL_.
[Siebel] ... ... ;SymStrPrefix parameter needs to be X_ for Siebel Customers. SymStrPrefix = SBL_ ... ...
In Siebel Tools, lock the following projects:

Symbolic Strings Software Upgrade
Within Object Explorer > Screen, search for Siebel Anywhere Administration Screen.
14 5
Within the Screen view, activate the Upgrade Kit Item Parameter Types view. NOTE: Because the Upgrade Kit Item Parameter Types view includes the Upgrade Kit Item Type Argument list applet, the applet is also activated.
Within Object Explorer > Symbolic Strings, add a symbolic string with the following values: Current String Value The path of the startup program
Name SBL_PATH_OF_FILE_TO_EXECUTE
Project Symbolic Strings
Type Conversion
Translate true
6 7
Within Object Explorer > Applet, search for the Find Upgrade Kit Wizard applet. Within Control, add a control with the following values: HTML Type Field
Name StartupProgram
Caption The path of the startup program
Caption Reference SBL_PATH_OF_FILE_TO_EXECUTE
Field Execute File Name
8 9
Navigate to Applet Web Template, and search for "UpgKitWiz Exe Files". From the right-click menu, select Edit Web Layouts, and drag the StartProgram control to the applet. values: LanguageIndependent Code RebootRegEntry
10 Navigate to System Administration > List of Values, and add a regentry LOV with the following
Type UPG_KIT_ITEM_TYPE
Display Value RebootRegEntry
Order 8
11 Add a CheckResult LOV with the following values:

LanguageIndependent Code CheckResult
Type UPG_KIT_ITEM_TYPE
Display Value CheckResult
Order 9
146
12 Add Siebel Quick Fix LOV with the following value:

LanguageIndependent Code Siebel Quick Fix
Type UPG_KIT_TYPE
Display Value Siebel Quick Fix
Order 13
13 Navigate to Tools > Compile Projects and select All Projects to compile the projects. 14 Save the srf file to <Siebel Server Install folder>\objects\ENU\siebel_sia.srf on the installed
Siebel server.
15 Log into the application, navigate to Site Map > Siebel Anywhere >Upgrade Kit Item Type
Argument List Applet, and add records with the following values: Default Value N
Item Type FileCopy CheckResult CheckResult RebootRegEntry RebootRegEntry RebootRegEntry RebootRegEntry RebootRegEntry FileExecute
Name Unarchive Folder File Name Acceptable Return Code List File Name Command Line Check Return Code Return Code Is Script Is Script
Required Unchecked Checked Unchecked Checked Unchecked
Sequence 9 1 2 1 2 3 4 5 13
Unchecked Unchecked
N N
Unchecked Unchecked
16 Navigate to Site Map > Siebel Anywhere > Upgrade Component list applet, and add a component
with the following values:

Name: Siebel Quick Fix Component Type: Siebel Quick Fix Minimum Version: N/A Maximum Version: N/A Locate Method: CFG Locate Information: Siebel,ClientRootDir,bin\quickfix.cfg Version Method: CFG Version Information: Siebel,Version
14 7
Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B Oracle Welcomes Your Comments
Description: Used to distribute the Quick Fix

Bug 12572213 contains changes to SWLSEdit_2c_html.xsl. Use the instructions below to override the existing file during patch installation. Rename or remove the original files (SWLSEdit_2c_html.xsl) in order to have the files delivered in the patch. If the customer file should not be modified by customers, this process may be automated by adding the filename explicitly to the siebel.ini file for the product in question. There is a clause in siebel.ini called deletefile that allows listing of the file. [DeleteFile] <filename> Example: Make the following changes in all of the siebel.ini files: OverwriteConfig = Yes [DeleteFiles.Windows] (Note: This varies depending upon your operating system.) File1 = $(SiebelRoot)\siebsrvr\WEBTEMPL \SWLSEdit_2c_html.xsl
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.
148

MR Guide 8117 Rev B

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MR Guide 8117 Rev B

Uploaded by

Copyright:

Available Formats

Siebel Maintenance Release Guide

Version 8.1.1.7, Rev. B April 2012

Configuration Instructions for Enhancements and Updates

Siebel Fix Pack Installation Instructions

Resolved Change Requests

Resolved Bugs in the Siebel 8.1.1.7 Fix Pack

Siebel Siebel Siebel Siebel

Oracle Welcomes Your Comments

Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B

Release Notes for the Siebel 8.1.1.7 Fix Pack

Issues with Oracle Business Intelligence Publisher Integration

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

Whats New in This Revision

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

How To Use This Guide

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

Quick Fixes Included in the Siebel 8.1.1.7 Fix Pack

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

Enhancements and Updates in Version 8.1.1.7

Feature Enhancement or Certification Number ACR 575

ACR 698 ACR 699 ACR 701

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

Feature Enhancement or Certification Number ACR 719B

Instructions for ACR 839

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

Configuration Instructions for Enhancements and Updates

Instructions for ACR 575

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

Name: TNT Show Move Popup Applet Value: N

Name: Disable Right Click Menu Item 1 Value: Assign to Category

Name: TNT Show Move Popup Applet Value: N

Name: Disable Right Click Menu Item 1 Value: Assign to Category

Name: TNT Show Move Popup Applet Value: N

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

Name: Disable Right Click Menu Item 1 Value: Assign to Category

Configuration Instructions for ACR 575

Type TNT_SHM_GNTAX_FS_TY PE_TOGGLE

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

New Repository Objects

TNT SHM Add Function Popup TNT SHM InvokeAssignDayPopup

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

SBL_TNT_ADD_FUNCTION SBL_TNT_COLOR_DISPLAY_BY SBL_TNT_COPY_SUB_FUNCTIONS SBL_TNT_DEFAULT_DIARY_COLOR_DISPLAY_INFO SBL_TNT_FUNC_SPACE_COL_SIZE SBL_TNT_NEG_RENTAL SBL_TNT_SEL_RESERV_TO_MOVE_SIA

CSSBCVRecMoveFunction CSSSWEFrameTNTMoveFuncPopup CSSSWEFrameTNTSIAAssocList

Changed Repository Objects

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

Name/Field Function Space Type Toggle Function Space Type - Query

Caption Function Space Type SBL_FUNCTION_SPACE_TYPE1009100818-A2P

Runtime RunTime= True

Booking Color Toggle Booking Color Toggle Schema

Color Display By SBL_TNT_COLOR_DISPLAY_BY

Booking Color Toggle

TNT SHM Add Function Popup

Add Function SBL_TNT_ADD_FUNCTION

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B

Table 10. Controls

Name/Field Function Space Type Toggle Function Space Type Query