MR_Guide_8117_Rev_B

Siebel Maintenance Release Guide
Version 8.1.1.7, Rev. BApril 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 error-free. 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 RIGHTSPrograms, 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.

Release Notes for the Siebel 8.1.1.7 Fix Pack 7

What’s New in This Revision 8

Quick Fixes Included in the Siebel 8.1.1.7 Fix Pack 11

Enhancements and Updates in Version 8.1.1.7 14

Configuration Instructions for Enhancements and Updates 16Instructions for ACR 575 16Configuration Instructions for ACR 575 18Seed Data 18Lists of Values 18System Preferences 19New Repository Objects 19Changed Repository Objects 20Business Components 28Business Objects 42Enabling Diary Configurable Icons 42Copying Configurable Icons 48Configuring the Application 49Instructions for ACR 719B 49Instructions for ACR 731 55Instructions for ACR 750 58Instructions for ACR 762 62Instructions for ACR 802 69Instructions for ACR 839 71

Siebel Fix Pack Installation Instructions 80Siebel Fix Pack Installation Overview 81Installing the Siebel Fix Pack on Microsoft Windows 85Installing the Siebel Fix Pack on UNIX 90

Contents

Configuring Slipstream Patch Installation 95Postinstallation Tasks for the Siebel Server 96Postinstallation Tasks for the Web Server 97Postinstallation Tasks for High Interactivity Clients 97Postinstallation Tasks for Supporting Additional Languages 98Uninstalling Siebel Fix Packs 99

Resolved Change Requests 101

Resolved Bugs in the Siebel 8.1.1.7 Fix Pack 102Siebel Apps - Customer Order Management 102Siebel Apps - Data Quality 105Siebel Apps - Field Service 106Siebel Apps - Handheld Client 107Siebel Apps - Marketing 108Siebel Apps - Multichannel Technologies 108Siebel Apps - Oracle Customer Hub 109Siebel Apps - PRM 110Siebel Apps - Sales 110Siebel Apps - Search & Knowledge Management 111Siebel Apps - Self Svc: ADF 112Siebel Apps - Service 112Siebel Apps - Territory Management 112Siebel Apps - UCM 113Siebel Charts 113Siebel Communications & Energy 113Siebel Consumer Goods 114Siebel Core - EAI 115Siebel Core - EIM/Database 117Siebel Core - Handheld Sync 118Siebel Core - PIM Integration 119Siebel Core - Server BizLogic Rules 122Siebel Core - Server BizLogic Script 122Siebel Core - Server BizLogic WF 123Siebel Core - Server Infrastructure 124Siebel Core - Server OM Frwks 124Siebel Core - UIF Client 125Siebel Core - Unix/Windows 127Siebel Core - zSeries 128Siebel CRM Integration to Oracle Realtime Scheduler 128Siebel Data Model 128Siebel Documents 129Siebel Engineering - Release Engineering 129Siebel Life Sciences 129

Siebel Loyalty 133Siebel Reports 135Siebel Server Remote 141Siebel Travel & Transportation 142

Oracle Welcomes Your Comments 148

Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B

April 2012NOTE: 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

■ What’s 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 PackThe 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 IntegrationProduct: 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 7

Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B ■ What’s 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 Within Siebel Tools, navigate to the XMLP Integration project, and lock it.

2 Import the BIP_8117FP_Extension.sif file using the overwrite mode.

3 Compile the SRF.

Search Functionality Not Working with OSES 11.1.2 After German Language FixProduct: 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).

What’s New in This RevisionTable 1 describes the changes in this version of the documentation.

Table 1. What’s New in Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B

Topic Description

“Release Notes for the Siebel 8.1.1.7 Fix Pack” on page 7

Clarified the import mode in the procedure for applying 8.1.1.7 QF0703 and added the Bug ID for the QF.

“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

Corrected incorrect version number for ACR 699.

“Instructions for ACR 750” on page 58 Revised this topic.

Siebel Maintenance Release Guide Version 8.1.1.7, Rev. B8

Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B ■ What’s New in ThisRevision

“Instructions for ACR 839” on page 71 Added a new procedure for the Clinical Trip Report Business Component (Modified).

“Instructions for Bug 13003564” on page 145

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.

Table 1. What’s New in Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B

Topic Description


Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B ■ What’s New in This Revision

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 DocumentationOracle 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 Oracle’s Siebel Business Applications, Version 8.1 (http://www.oracle.com/technology/documentation/siebel.html) on Oracle Technology Network (OTN)


Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B ■ Quick Fixes Included inthe Siebel 8.1.1.7 Fix Pack

Quick Fixes Included in the Siebel 8.1.1.7 Fix PackNOTE: 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

Change Request ID/Base Bug ID

Fix Request ID/Bug ID Fix Pack Base

Quick Fix Version

Merged Into Fix Pack

10602136 10602141 8.1.1 WM5 [21112_14] 8.1.1 WM5 [21112_14

8.1.1.7

10587343 10587344 8.1.1.1 [21211] QF0156 8.1.1.7

12577313 12768536 8.1.1.1 [21211] QF01CP 8.1.1.7

12937764 13078962 8.1.1.1 [21211] QF01CQ 8.1.1.7

10598010 10598080 8.1.1.2 [21215] QF02BV 8.1.1.7

11869400 10600732 8.1.1.2 [21215] QF02CJ 8.1.1.7

10604196 10604265 8.1.1.2 [21215] QF02CQ 8.1.1.7

12570179 12811808 8.1.1.2 [21215] QF02CS 8.1.1.7

10558365 13260213 8.1.1.2 [21215] QF02CT 8.1.1.7

12772458 13407108 8.1.1.2 [21215] QF02CU 8.1.1.7

11818894 11831498 8.1.1.2 [21215] QF2203 8.1.1.7

12312702 12318058 8.1.1.2 [21215] QF2204 8.1.1.7

13419996 12608701 8.1.1.2 [21215] QF2207 8.1.1.7

12733277 12724391 8.1.1.2 [21215] QF2208 8.1.1.7

12807436 12732696 8.1.1.2 [21215] QF2209 8.1.1.7

13419996 12921815 8.1.1.2 [21215] QF2211 8.1.1.7


Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B ■ Quick Fixes Included in the Siebel 8.1.1.7 Fix Pack

12756997 12757030 8.1.1.2 [21215] QF2212 8.1.1.7

12857901 12856680 8.1.1.2 [21215] QF2212 8.1.1.7

12876544 12865401 8.1.1.2 [21215] QF2212 8.1.1.7

12876539 12869363 8.1.1.2 [21215] QF2212 8.1.1.7

12906967 12888652 8.1.1.2 [21215] QF2212 8.1.1.7

12962036 13242025 8.1.1.2 [21215] QF2213 8.1.1.7

13090315 13242164 8.1.1.2 [21215] QF2213 8.1.1.7

13419996 13420013 8.1.1.2 [21215] QF2213 8.1.1.7

13419996 13415880 8.1.1.2 [21215] QF2213 8.1.1.7

12577313 12577231 8.1.1.3 [21219] QF03AY 8.1.1.7

12566908 12566947 8.1.1.3 [21219] QF03BI 8.1.1.7

10598010 12944899 8.1.1.3 [21219] QF03BP 8.1.1.7

13384850 13384875 8.1.1.3 [21219] QF03BQ 8.1.1.7

13043868 13085632 8.1.1.3 [21219] QF03BS 8.1.1.7

12604183 13375871 8.1.1.3 [21219] QF03BV 8.1.1.7

12896102 12915223 8.1.1.3 [21219] QF1303 8.1.1.7

10606138 10606139 8.1.1.3 WM5 [21219_4] 8.1.1.3 WM5 [21219_4]

8.1.1.7

10606138 10606139 8.1.1.3 WM5 [21219_4] 8.1.1.3 WM5 [21219_4]

8.1.1.7

12318676 12313396 8.1.1.4 [21225] QF0421 8.1.1.7

10605987 12723709 8.1.1.4 [21225] QF0433 8.1.1.7

12736823 12737165 8.1.1.4 [21225] QF0438 8.1.1.7

12577313 12926026 8.1.1.4 [21225] QF0440 8.1.1.7

12795298 12795350 8.1.1.4 [21225] QF0443 8.1.1.7

12805219 12805266 8.1.1.4 [21225] QF0446 8.1.1.7

12802129 12866175 8.1.1.4 [21225] QF0448 8.1.1.7

12889047 12889120 8.1.1.4 [21225] QF0449 8.1.1.7

12826991 12827015 8.1.1.4 [21225] QF0450 8.1.1.7

10529645 12883388 8.1.1.4 [21225] QF0451 8.1.1.7




Quick Fix Version



Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B ■ Quick Fixes Included inthe Siebel 8.1.1.7 Fix Pack

10558365 12922188 8.1.1.4 [21225] QF0452 8.1.1.7

13384850 13384866 8.1.1.4 [21225] QF0454 8.1.1.7

12801963 13096035 8.1.1.4 [21225] QF0458 8.1.1.7

10583904 12720131 8.1.1.4 WM5 [21225_1] 8.1.1.4 WM5 21225_1

8.1.1.7

11830300 11858120 8.1.1.5 [21229] QF0502 8.1.1.7

11717572 12798488 8.1.1.5 [21229] QF0514 8.1.1.7

12937764 12945668 8.1.1.5 [21229] QF0515 8.1.1.7

12577313 12766445 8.1.1.5 [21229] QF0517 8.1.1.7

10537307 12643211 8.1.1.5 [21229] QF0520 8.1.1.7

12705438 12823043 8.1.1.5 [21229] QF0521 8.1.1.7

12833238 12838039 8.1.1.5 [21229] QF0522 8.1.1.7

12711326 12726874 8.1.1.5 [21229] QF0523 8.1.1.7

12865043 12865331 8.1.1.5 [21229] QF0526 8.1.1.7

10585340 12857923 8.1.1.5 [21229] QF0527 8.1.1.7

11767223 12934784 8.1.1.5 [21229] QF0530 8.1.1.7

12822135 12848581 8.1.1.5 [21229] QF0531 8.1.1.7

10534318 13008052 8.1.1.5 [21229] QF0532 8.1.1.7

10558365 12942915 8.1.1.5 [21229] QF0533 8.1.1.7

12750196 12790188 8.1.1.5 [21229] QF0536 8.1.1.7

12629343 12931623 8.1.1.5 [21229] QF0537 8.1.1.7

12800053 12829467 8.1.1.5 [21229] QF0538 8.1.1.7

12879239 13039780 8.1.1.5 [21229] QF0539 8.1.1.7

13384850 13384865 8.1.1.5 [21229] QF0547 8.1.1.7

12937371 12937408 8.1.1.5 [21229] QF0548 8.1.1.7

11682517 13105264 8.1.1.5 [21229] QF0549 8.1.1.7

12772458 12780386 8.1.1.5 [21229] QF0550 8.1.1.7

10605987 13324301 8.1.1.5 [21229] QF0551 8.1.1.7

12567732 13076148 8.1.1.5 [21229] QF0556 8.1.1.7

13019417 13026022 8.1.1.5 [21229] QF0557 8.1.1.7




Quick Fix Version



Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B ■ Enhancements and Updates in Version 8.1.1.7

Enhancements and Updates in Version 8.1.1.7Table 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.

10595170 12964888 8.1.1.5 [21229] QF0560 8.1.1.7

13391431 13436951 8.1.1.5 [21229] QF0563 8.1.1.7

10591152 13505777 8.1.1.5 [21229] QF0564 8.1.1.7

10598444 13114020 8.1.1.5 [21229] QF0565 8.1.1.7

12810197 12873861 8.1.1.5 [21229] QF0566 8.1.1.7

13085829 13106410 8.1.1.6 [21233] QF0601 8.1.1.7

13081720 13101755 8.1.1.6 [21233] QF0602 8.1.1.7

12772458 13422290 8.1.1.6 [21233] QF0604 8.1.1.7

12839398 13406439 8.1.1.6 [21233] QF0611 8.1.1.7

Table 3. Enhancements and Updates in Version 8.1.1.7

Feature Enhancement or Certification Number Feature Enhancement or Certification Description

ACR 575 Provides enhancements to Siebel Hospitality Diary functionality.

Instructions for ACR 575

ACR 698 Certifies AIX 7.1.

ACR 699 Certifies Oracle Enterprise Linux 6.1 64-bit.

ACR 701 Certifies IBM DB2 v10 for z/OS.




Quick Fix Version



Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B ■ Enhancements andUpdates in Version 8.1.1.7

ACR 719B 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

Instructions for ACR 719B

ACR 731 Supports Signature Capture using the CIC component on the Microsoft Windows 7 platform.


ACR 750 Provides SOAP and EJB fuctionality for Siebel Application Integration (SAI).


ACR 761 Provides a Data Quality sync switch.

ACR 762 Ports SonGo Web services to the iSales application.


ACR 802 Provides Bulk Administration enhancements and redemption concurrency functionality.


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.


Table 3. Enhancements and Updates in Version 8.1.1.7

Feature Enhancement or Certification Number Feature Enhancement or Certification Description


Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B ■ Configuration Instructions for Enhancements and Updates

Configuration Instructions for Enhancements and UpdatesThis 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 575Use 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 Log into Siebel Tools, query for the TNT SHM Function Space Diary and TNT SHM Compact Function Space Diary projects, and lock them.

2 In the Object Explorer, click on the Applet object.


Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B ■ Configuration Instructionsfor Enhancements and Updates

3 Click on any record on the right-hand side, and query for the TNT SHM Function Space Diary applet.

4 Right-click and lock the applet.

5 Click the + sign to expand the applet.

6 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


■ Value: Assign to Specific Space

7 Query for the TNT SHM Compact Function Space Diary applet.



10 Click on the Applet User Prop subobject, and create the following new user properties and values:


■ Value: N





11 Query for the TNT SHM Function Space Diary Total Availability Applet applet



14 Click on the Applet User Prop subobject, and create the following new user properties and values:


■ Value: N







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 575Use the instructions in the following section to configure ACR 575.

Seed Data1 Navigate to List of Values Explorer > List of Values - Types.

■ List Of Values Explorer > List Of Values - Types

Lists of Values

Type Replication Level Multilingual Translate

TNT_SHM_GNTAX_FS_TYPE_TOGGLE

All TRUE TRUE

TypeDisplay Value LIC

Language Name Order Active

Translate

TNT_SHM_GNTAX_FS_TYPE_TOGGLE All ALL English - American

1 TRUE TRUE

TNT_SHM_GNTAX_FS_TYPE_TOGGLE Specific Space

SPECIFIC_SPACE English - American

2 TRUE TRUE

TNT_SHM_GNTAX_FS_TYPE_TOGGLE Special Location

SPECIAL_LOCATION

English - American

3 TRUE TRUE

TNT_SHM_GNTAX_FSD_DSP_TOGGLE Inventory Status

17 English - American

10 TRUE TRUE



System Preferences

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 Uncompress the 8.1.1.2_Hospitality_Enhancements.zip file to create the 8.1.1.2_Diary_Porting folder.

2 Create a log folder in the \REPPATCH\8.1.1.2_Diary_Porting\REPOSITORY directory.

3 Rename the Picklist folder to Pick List.

4 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

System Preference Name System Preference Value Description

TNT CMT Special Location Pref Y

ACR495 Space Hold Y

ACR450 Change Diary Start Date N

TNT CMT Configurable Icons Y

GntAXCtrl:Color Display Toggle INVENTORY_STATUS

TNT CMT Func Spaces Cache Size 1000

TNT CMT Memory Utilization Y



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

AppletsThe following tables describe the applets associated with ACR 575.



TNT SHM Function Space Diary

Table 4. TNT SHM Function Space Diary Applet

TNT SHM Function Space Diary

Class CSSSWEFrameSHMAxDiary

Project TNT SHM Function Space Diary

BusComp TNT SHM Gantt AX Date Time Interval PopUp VBC

Title

Type Standard

HTML Number Of Rows

Table 5. Applet User Properties

New/Modified Name Value Existing Value

New Ignore Case Sensitivity Y

New Item Time Display Toggle Time Label 10

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

New Item Time Display Toggle Time Tooltip 17

Booking Set Up Tip;Booking Tip - Function Name;Booking Tear Down Tip;Booking Tear Down Tip

Modified Max X Pages 2 Existing Value: 3



Modified Max Y Rows Per Page 25 Existing Value: 15

New Number of Rows to Overlap 1

New Transient Suite Field Is Transient Suite

New Y-Axis Drill Down Enable Y

Modified Y-Axis Width Function Space Column Size

Existing Value: 150

New TNT Same Time Frame - Show Move Popup Applet

Y


New/Modified Name Value Existing Value



Applet Web Template ItemNOTE: Add the newly-added control to display in the UI.

Table 6. Controls

New/Modified Name/Field Caption

HTML Icon Map/HTML Type Runtime Existing Value

New Function Space Type Toggle

Function Space Type - Query

Function Space Type SBL_FUNCTION_SPACE_TYPE-1009100818-A2P

Text RunTime=True

New Go To

Go To

Go To

SBL_GO_TO-1004233041-4MM

Modified GanttChart HTML Height: 560

HTML Width: 960

HTML Height: 456

Existing HTML Width: 960

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 Command Menu Text Position Position

New TNT SHM InvokeAssignDayPopup

Assign

SBL_ASSIGN-1004224603-02B

6

New TNT SHM Add Function Popup Add Function

SBL_TNT_ADD_FUNCTION

8



TNT SHM Compact Function Space Diary

Table 8. TNT SHM Compact Function Space Diary

TNT SHM Compact Function Space Diary

Class CSSSWEFrameSHMAxCompactDiary

Project TNT SHM Compact Function Space Diary

Bus Comp TNT SHM Gantt AX Date Time Interval PopUp VBC

Title

Type Standard

HTML Number of Rows


New/Modified Name ValueExisting Value

New Ignore Case Sensitivity 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

Modified Max X Pages 2 3

Modified Max Y Rows Per Page 25 15

New Number of Rows to Overlap 1

New Transient Suite Field Is Transient Suite




New Y-Axis Drill Down Enable Y

Modified Y-Axis Width Function Space Column Size 150

New TNT Same Time Frame - Show Move Popup Applet

Y

Table 10. Controls


HTML Icon Map/HTML Type Runtime

Existing Value

New Function Space Type Toggle

Function Space Type - Query

Function Space Type SBL_FUNCTION_SPACE_TYPE-1009100818-A2P

Text RunTime = True

New

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

Color Display By


Booking Color Toggle

Table 11. Applet Method Menu Item

New/Modified Command Menu Text Position Position Comment

New TNT SHM InvokeAssignDayPopup

Assign

SBL_ASSIGN-1004224603-02B

6 New


New/Modified Name ValueExisting Value



TNT SHM Gantt AX Admin Form Applet


Table 12. TNT SHM Gantt AX Form Applet

Class CSSFrame

Project TNT SHM Function Space Diary

BusComp TNT SHM Gantt AX Admin Specialized Controls

Title FSD Administration

Type Standard

HTML Number Of Rows

Table 13. Controls


HTML Icon Map/HTML Type Runtime Comment

New Color Display By

Color Display Toggle

Color Display By


Text Set Runtime = TRUE

New HTML Form Section4

Default Diary Color Display Information

SBL_TNT_DEFAULT_DIARY_COLOR_DISPLAY_INFO

FormSection Runtime = TRUE



TNT SHM FSD User Preferences


Table 14. TNT SHM FSD User Preference

Class CSSFrameBase

Project User Preferences

BusComp User Preferences

Title Function Space Diary

Type Standard

HTML Number Of Rows

Table 15. Controls


HTML Icon Map/HTML Type Runtime Comment

New TNTCMTDiary/Function Space Column Size

TNT CMT Diary/Function Space Column Size

Function Space Column Size

SBL_TNT_FUNC_SPACE_COL_SIZE

Text New

New TNTCMTDiary/FunctionSpaceType

TNT CMT Diary/Function Space Type

Function Space Type

SBL_FUNCTION_SPACE_TYPE-1009100818-A2P

Text Runtime = TRUE

Modified Booking Color Schema

TNT CMT Diary/Booking Color Toggle Schema

Color Display By


Text Modified

It was mapped to the Diary/Booking Color Toggle Schema field.



TNT SHM Function Assoc Applet

TNT SHM Function Order Mvg Applet

Business ComponentsThe following tables describe some of the business components associated with ACR 575.

Table 16. TNT SHM Function Assoc Applet

Class CSSSWEFrameTNTSIAAssocList Existing Class: CSSSWEFrameList Assoc

Project TNT SHM Function

Bus Comp TNT SHM Function

Title Add Functions

Type Association List

HTML Number of Rows

Table 17. TNT SHM Function Order Mvg Applet

Class CSSSWEFrameOrderMvg

Project TNT SHM Function

BusComp Order Entry - Orders

Title Orders

Type MVG

HTML Number Of Rows

Table 18. Controls

Name/Field CaptionHTML Icon Map/HTML Type

Method Invoked

Existing Value

Add - Shuttle Add > AddOrder .AddRecords



Internal Product

Table 19. Business Component User Properties

New/ Modified Name Value Comments

New TNT Room Search Spec

([Type] = LookupValue('PRODUCT_TYPE', 'Indivisible') OR [Type] = LookupValue('PRODUCT_TYPE', 'Configured') OR [Type] = LookupValue('PRODUCT_TYPE', 'Category') OR [Type] = LookupValue('PRODUCT_TYPE', 'Suite'))

Diary Performance Issue



TNT SHM FSI Booking

Table 20. Fields

New/Modified Field Name Calculated

Calculated Value/Join Column DTYPE_xxx Miscellaneous

New Function End Time

True [Function Start Time] + [Function Duration] * 60

DTYPE_TEXT

New Function Space Event Check Status

Function Space Event Check

STATUS_CD

DTYPE_TEXT

New Quote Number S_DOC_QUOTE.

QUOTE_NUM

DTYPE_TEXT

New TNT Proposed Function Date

True DTYPE_TEXT

New TNT Proposed Function End Time

True DTYPE_TEXT

New TNT Proposed Function Space

True DTYPE_TEXT

New TNT Proposed Function Space Id

True DTYPE_TEXT

New TNT Proposed Function Start Time

True DTYPE_TEXT

New TNT Same Function Space

True DTYPE_BOOL

New Function Space Event Check Id

Order Item TNTX

EVT_CHECK_ID

Text Length = 15

D_TYPE_ID

New Function Space Order Item Id

Order Item

ROW_ID

Text Length = 15

D_TYPE_ID



Table 21. Function Space Event Check Join

New/Modified Table Alias Outer Join Flag

New S_INVOICE Function Space Event Check

True

Join Specification

Name Destination Column Source Column

Event Check Id ROW_ID Function Space Event Check ID

Table 22. Order Item TNTX Join


New S_ORDERITM_TNTX Order Item TNTX True

Join Specification


Par Row Id PAR_ROW_ID Function Space Order Item Id

Table 23. Order Item Join


New S_ORDER_ITEM Order Item True

Join Specification


Function Id FUNCTION_ID Function Id

Function Space Id PROD_ID Function Space Id



User Preferences

Table 24. Fields

New/Modified Field Name Calculated Required

Predefined Value Picklist Type

New TNT CMT Diary/Booking Color Toggle Schema

TRUE TNT FSD Color Schema PickList

DTYPE_TEXT

New TNT CMT Diary/Function Space Column Size

True 150 DTYPE_NUMBER

New TNT CMT Diary/Function Space Type

4TRUE TNT SHM FSD Function Space Type PickList

DTYPE_TEXT

Table 25. Pick Maps

Parent Field Sequence BC - ) FieldPicklist Field Constrain No Clear

TNT CMT Diary/Booking Color Toggle Schema

Value

TNT CMT Diary/Function Space Type

Value



TNT SHM Quote Template Pick BC

Table 26. Fields

New/Modified Field NameCalculated Value/Join Column

DTYPE_xxx Miscellaneous

New Account S_ORG_EXT.Name DTYPE_Text

Text Length = 100

New Account Id TARGET_OU_ID DTYPE_ID

New Arrival Date S_QUOTE_TNTX.

ARRIVAL_DT

DTYPE_DATE

New Departure Date S_QUOTE_TNTX.

DEPARTURE_DT

DTYPE_DATE

New Post As Name S_QUOTE_TNTX.

ALIAS_NAME

DTYPE_TEXT

Text Length = 100

New Property Property.NAME 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

Table 27. Property Join


New S_ORG_EXT Property True

Join Specification


Property Id PAR_ROW_ID Primary Organization Id



TNT SHM Gantt AX Date Time Interval PopUp VBC

Table 28. S_ORG_EXT Join


New S_ORG_EXT S_ORG_EXT True

Join Specification


Account Id PAR_ROW_ID Account Id

Table 29. Fields

New/ModifiedField Name

Calculated Value/Join.Column

Pick List

Post Default

Pre Default

Force Active Link Spec Required Immediate P.C.

DTYPE_xxx

Miscellaneous

New Function Space Type - Query

Calculated = TRUE TNT SHM FSD Function Space Type PickList

Immediate Post Change = TRUE

DTYPE_TEXT

New Go To Calculated = TRUE DTYPE_TEXT

Table 30. Pick Maps

Parent Field BC - ) Field Picklist Field

Function Space Type - Query Function Space Type - Query Value

Table 31. User Properties

New/Modified Name Modified Value

New Activation Field 1 Go To

New Activation Field 2 Function Space Type - Query

New Default Function Space Type Specific Space

Modified Scale Unit Major 1;1;2;1;4;.75;8;1;16;2;32;1;64;1;128;1;256;1

Modified Scale Unit Minor 1;1;2;1;4;.75;8;1;16;2;32;1;64;1;128;1;256;1



TNT SHM Gantt AX Admin Specialized Controls

Modified Segments Per Page Major 1;1;2;1;4;1;8;1;16;1;32;2;64;30;128;8;256;8

Modified Segments Per Page Minor 1;8;2;1;4;24;8;24;16;48;32;8;64;30;128;8;256;8

Modified Units Per Segment Major 1;7;2;1;4;1;8;0.5;16;0.25;32;28;64;1;128;1;256;7

Modified Units Per Segment Minor 1;1;2;1;4;0.0416666666666666;8;0.020833333333333334;16;0.010416666666666666;32;7;64;1;128;1;256;7

New X-Axis Drill Down Enable Y

Table 32. Fields

New/Modified Field Name

Pick List

Post Default

Pre Default

Force Active Link Spec Required Immediate P.C.

DTYPE_xxx

Miscellaneous

New Booking Color Toggle Schema

TNT FSD Color Schema PickList

Required = TRUE DTYPE_TEXT

New Color Display Toggle

TNT FSD Color Schema PickList

Required = TRUE DTYPE_TEXT

Table 33. Pick Maps

Parent Field BC > Field Picklist Field

Booking Color Toggle Schema Booking Color Toggle Schema Value

Color Display Toggle Color Display Toggle Value


New/Modified Name Modified Value



TNT SHM Function

Table 34. Fields

New/Modified Field Name Calculated Value

DTYPE_xxx

Miscellaneous

New TNT CMT Quote Status ReadOnly View Flag for Function Screen

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

DTYPE_TEXT


New / Modified Name Value

New Copy Function Field 11 "FN_TYPE_ID", "Function Type Id"

New Copy Function Field 12 "FN_TYPE", "Function Type"

New Copy Function Field 13 "SETUP_STYLE", "Setup Style"

New Copy Function Field 14 "EXP_NUM", "Expected Num"

New Copy Function Field 15 "GUARNT_NUM", "Guaranteed Num"

New Copy Function Field 16 "SET_NUM", "Set Num"

New Copy Function Field 17 "NEG_RM_RENTAL", "TNT CMT Negotiated Room Rental"

New Copy Function Field 18 "FLOW_FLAG", "Flow Flag"

New Copy Function Field 19 "DO_NOT_POST_FLAG", "TNT CMT Do Not Post Flag"

New Copy Function Field 20 "NOISE_FLAG", "Noise Flag"

New Copy Function Field 21 "FUNCTION_SPACE", "Active Function Space"



TNT SHM Compact Room Rel VBC

TNT SHM Compact Function Booking VBC

Table 36. Fields


Calculated Value/Join.Column Existing Value

DTYPE_xxx

Miscellaneous

Modified Hierarchy Bitmap Id

IIf([HasChildren] = '1', IIf([Expanded]='1', 206, 207), IIf([Parent Room Id] = 'ORPHANED', 0, 210))

IIF([HasChildren] = '1', IIF([Expanded]='1', 206, 207), IIF([Parent Room Id] = 'ORPHANED', 205, 210))

DTYPE_TEXT

Modified Room Backup Required Id

IIf([Room Backup Required]='Y', 221, 0)

if([Room Backup Required]='Y', 221, 205)

DTYPE_TEXT

Table 37. Fields



Force Active Link Spec Required Immed. P,C

DTYPE_xxx

Miscellaneous

New Active Function Space DTYPE_TEXT

New Addl Tip [Function Space Tip] + [Guaranteed Tip] + [Peak Rooms Tip] + [Total Catering Revenue Tip]

DTYPE_TEXT

New Backup Space DTYPE_TEXT

New Total Catering Revenue

DTYPE_TEXT

New Total Catering Revenue Field Name Tip

IIf([Total Catering Revenue] IS NOT NULL, LookupValue('TNT_SHM_TOOLTIP_OBJECTS', 'Total Catering Revenue') + ": " , "")

New Total Catering Revenue Tip

[Total Catering Revenue Field Name Tip] + [Total Catering Revenue] + IIF([Total Catering Revenue] IS NULL,"","\r\n")

DTYPE_TEXT

New Function Space Tip Field Value

IIF([Booking Type] = LookupValue('TNT_SHM_BOOKING_TYPE','Backup'), [Active Function Space], [Backup Space])

DTYPE_TEXT



New Function Space Tip [Function Space Field Name Tip] + [Function Space Tip Field Value] + IIF([Function Space Tip Field Value] IS NULL,"","\r\n")

DTYPE_TEXT

New Function Space Field Name Tip

IIF([Function Space Tip Field Value] IS NOT NULL, LookupValue('TNT_SHM_TOOLTIP_OBJECTS', 'Backup Space/Pri Space Link') + ": " , "")

DTYPE_TEXT

New Guaranteed Field Name Tip

IIF([Guaranteed] IS NOT NULL, LookupValue('TNT_SHM_TOOLTIP_OBJECTS', 'Guaranteed') + ": " , "")

DTYPE_TEXT

New Guaranteed Tip [Guaranteed Field Name Tip] + [Guaranteed] + IIF([Guaranteed] IS NULL,"","\r\n")

DTYPE_TEXT

New Peak Rooms DTYPE_INTEGER

Modified Peak Rooms Field Name Tip

IIF([Peak Rooms] IS NOT NULL, LookupValue('TNT_SHM_TOOLTIP_OBJECTS ', 'Peak Rooms') + ": " , "")

DTYPE_TEXT

Modified Peak Rooms Tip [Peak Rooms Field Name Tip] + [Peak Rooms] + IIF([Peak Rooms] IS NULL,"","\r\n")

DTYPE_TEXT

Modified Booking Tip - Business Type

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

Table 37. Fields




DTYPE_xxx

Miscellaneous



Modified Booking Tip - Event Manager

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

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

DTYPE_TEXT

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]

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

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]

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

DTYPE_TEXT

Table 37. Fields




DTYPE_xxx

Miscellaneous



Modified Booking Tip - Function Type

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

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

DTYPE_TEXT

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]

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

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]

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

DTYPE_TEXT

Table 37. Fields




DTYPE_xxx

Miscellaneous



Modified Booking Tip - Sales Manager

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

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

DTYPE_TEXT

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]

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

DTYPE_TEXT

Modified Inventory Status Set Force Active = TRUE

Note: Existing Field.

Modified Inventory Status Calculated

[Inventory Status] + ' ' + IIF([Function Revision Type] = LookupValue('TNT_SHM_REVISION_TYPE','REVISED'), ' -' + LookupValue('TNT_SHM_REVISION_TRANS_TYPE',[Function Revision Type]),'')

DTYPE_TEXT

Table 37. Fields




DTYPE_xxx

Miscellaneous



Order Entry - Orders

Business ObjectsThe following tables describe the SHM Site and Quote business object components associated with ACR 575.

SHM Site

Quote

Enabling Diary Configurable IconsThe following section describes how to enable the Diary configurable icons.

Seed Data 11 Launch the Siebel application.

Table 38. Fields

New/Modified Field Name Calculated Calculated Value

DTYPE_xxx

Miscellaneous

New Read Only Flag True IIf(([Status] = LookupValue("FS_ORDER_STATUS","Event Check") OR [Freeze Flag]),"Y","N")

DTYPE_TEXT

Table 39. Business Object Component

Name Link

TNT Configured Space

TNT Move Function VBC

TNT SHM Add Copy Function Parameter VBC

Table 40. Business Object Component

Name Link

TNT SHM Function Orders - DTU



2 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 1The 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_noiseType: 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_holdType: BMP

Width: 12 Pixel

Height: 11 Pixel

Function: Indicates that the current function space is on hold for 24 hours.


3. Name: ind_dont_moveType: BMP

Width:12 Pixel

Height:11 Pixel

Function: Indicates that the current booking should not be moved from the specified function space.




4. Name: hier_tee_ltr_dType: BMP

Width: 18 Pixel

Height: 18 Pixel

Function: Indicate to display the hierarchical function spaces.

5. Name: hier_spaceType: BMP

Width: 18 Pixel

Height: 18 Pixel


6. Name: hier_collapse_ltr_dType: BMP

Width: 18 Pixel

Height: 18 Pixel

Default Icon:


7. Name: hier_expand_ltr_dType: BMP

Width:18 Pixel

Height:18 Pixel


8. Name: hier_exp_tee_ltr_dType: BMP

Width:18 Pixel

Height:18 Pixel




9. Name: hier_exp_elbow_ltr_dType: BMP

Width: 18 Pixel

Height: 18 Pixel


10. Name: hier_elbow_ltr_dType: BMP

Width: 18 Pixel

Height: 18 Pixel


11. Name: hier_coll_tee_ltr_dType: BMP

Width: 18 Pixel

Height: 18 Pixel

Default Icon:


12. Name: hier_coll_elbow_ltr_dType: BMP

Width: 18 Pixel

Height: 18 Pixel


13. Name: Ind_detail_markerType: BMP

Width: 12 Pixel

Height: 11 Pixel

Function: Indicates that the current booking is a detailed function.


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.



14. Name: ind_sleepType: BMP

Width: 12 Pixel

Height: 11 Pixel

Function: To indicate the sleeping room.

15. Name: Ind_fnctn_schedule_markerType: BMP

Width: 12 Pixel

Height: 11 Pixel

Function: To Indicate the function Scheduled marker.

16. Name: ind_recurringType: 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_bookingType: 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_bookingType: BMP

Width: 12 Pixel

Height: 11 Pixel

Function: Indicates that the current booking is an affiliate booking.




19. Name: ind_backup_reqType: 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_EnabledType: BMP

Width: 16 Pixel

Height: 16 Pixel

Function: Indicates that Page Down is enabled.

21. Name: Diary_PageUp_EnabledType: BMP

Width: 16 Pixel

Height: 16 Pixel

Function: Indicates that the Scroll Page Up button is enabled.

22. Name: Diary_PageDown_DisabledType: BMP

Width: 16 Pixel

Height: 16 Pixel

Function: Indicates that the Scroll Page Down button is disabled.

23. Name: Diary_PageUp_DisabledType: BMP

Width: 16 Pixel

Height: 16 Pixel

Function: Indicates that the Scroll Page Up button is disabled.



24. Name: ind_holidayType: 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_IconType: BMP

Width:06 Pixel

Height:06 Pixel

Function: This icon marks special events in the Month/Day view.

26. Name: ind_sell_noteType: 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_eventsType: 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 Icons1 Navigate to \SWEAPP_ROOT\public\enu\.

2 Copy the icons into the images folder.



3 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 Application1 Navigate to Site Map > Function Space Administration > Function Space Diary Administration.

2 Update Start Time = “0700:00 AM”, End Time = “12:00:00 AM” and Time Scale = “Day/Hour” under “Time Interval Information”.

3 Delete the Siebel Hospitality Gantt Chart ActiveX DLLs from the Internet downloaded program files:

a Within Internet Explorer, navigate to Tools > Internet Options.

b Select the General tab, and click Settings.

c Click View Objects to open a window that contains all of the downloaded files.

d Select Diary ActiveX DLL and delete it.

Back to Configuration Instructions for Enhancements and Updates

Instructions for ACR 719BCAUTION: 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 719BTo implement ACR 719B, perform the following tasks:

1 “Applying Repository Changes for ACR 719B” on page 50

2 “Applying Schema Changes for ACR 719B” on page 52

3 “Applying Seed Data Changes for ACR 719B” on page 53



Applying Repository Changes for ACR 719BPerform 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.

1 Make sure that you have an existing Siebel CRM version 8.1.1 or later environment and have applied Siebel Fix Pack 8.1.1.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 Stop the Siebel Services.

3 Copy the existing .SRF file as a backup.

4 Edit the Siebel Tools configuration file by doing the following:

a 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 Save the tools.cfg file.

c Restart Siebel Tools, if currently active.

5 From the SIEBEL_TOOLS_ROOT\REPPATCH directory, extract the BIP_8117.zip file.

6 Import an archive file to apply the repository changes by doing the following:

a 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



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

b 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

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

7 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 Navigate to the View menu, then the Options menu item.

b Click the Language Settings tab.

c From the Language drop-down list, choose the desired language (FRA in this example), and then click OK.

d 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 Compile all locked projects.

8 Copy the browser scripts generated from the compiled SRF into the relevant Web folder by doing the following:

a Clear the existing folders in the language directory in the Siebel Tools installation directory (SIEBEL_TOOLS_ROOT\public\LANG).

b In Siebel Tools, compile the following object:

❏ XMLP Integration

c Navigate back to the Siebel Tools language directory and verify a new srfXXXXXXX_XXX folder was created, where X is an automatically generated number.



d Copy this folder to the SWSE\public\LANG directory.

e If you have a multi-language environment, repeat the above steps for each language in your deployment.

Applying Schema Changes for ACR 719BPerform the following procedure to apply schema changes for ACR 719B.

1 In Siebel Tools in the Object Explorer, select the Table object.

2 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 Click Apply/DDL, click Apply again, and then click OK.

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



Applying Seed Data Changes for ACR 719BApply 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.

1 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\SIABIP_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\SIABIP8113FP_SeedInps\database_type\SIABIP_8113FP_Seed_Locale_ENU.inp

■ To import 8.1.1.3 seed data for languages other than ENU for SIA:

Database Database User and Password ODBC Data Source

Oracle Query for dbtableowner in the temp.ini file and then apply that value as the database user and password

By default, this is set to either SSD Local Db default instance or Siebel_DSN.

MSSQL Query for databasename in the temp.ini file and then apply that value as the database user and password as MSSQL.


DB2 Provide db2 as the user and password for the Siebel application.


Database Database User and Password ODBC Data Source

Oracle Query for dbtableowner in the temp.ini file and then apply that value as the database user and password.


MSSQL Query for databasename in the temp.ini file and then apply that value as the database user and password as MSSQL.


DB2 Provide db2 as the user and password for the Siebel application.




❏ dataimp /u user_name /p password /f SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8113\SIA\SIABIP_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

2 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\HORBIP_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\HORBIP8113FP_SeedInps\database_type\HORBIP_8113FP_Seed_Locale_ENU.inp

3 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\HORBIP_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.

4 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\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\SIA\BIP_Seed.inp

❏ dataimp /u <user_name /p password /f <SIEBEL_TOOLS_ROOT\REPPATCH\BIP_8117FP\SEED_DATA\SEED_DATA_8116\SIA\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

5 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



6 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

7 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

8 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\ACR719B_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\SeedInp_Files\database_type\ACR719B_VACR719B_Seed.inp

9 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\ACR719B_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\SeedInp_Files\database_type\ACR719B_HACR719B_Seed.inp

10 Compile all locked projects.

11 Start the Siebel Services.


Instructions for ACR 731NOTE: 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.



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

1 Copy the iSign90.cab file to the following locations:

❏ \siebel\webmaster\siebel_build\applets

❏ \siebel\eapps\public\enu\21215\applets

2 Deploy iSign90.cab.

Installing ACR 7311 Log into Siebel Tools, navigate to Object Explorer and click on the Applet object.

2 Select any record on the right-hand side of the screen and query for "LS Pharma Call Signature Form Applet".

3 Navigate to Control and query for Name = Clear Signature.

4 Expand the User Properties control and modify the value of the AxMethod property from Reset to ClearSignature.

5 Navigate to Control and query for Name = Signature Capture.

6 Expand the User Properties control, and modify the value of the AxClassId property from {EFB7D763-97A3-11CF-AE19-00608CEADE00} to {93E5204A-4344-4381-8912-8A7091E0FAE5}.

7 Modify the value of the AxCodeBase property from iTools.cab to iSign90.cab.

8 Modify the value of the AxReturnProperties property from Ink to Signature.

9 Compile the applet.

10 Repeat Step 1 through Step 9 for the LS Pharma Txn Adjustment Signature Form Applet and LS Pharma Signature Capture Form Applet applets.

To edit the LS Pharma Master Signature Form Applet

1 Within Object Explorer, click on the Applet object.

2 Select any record on the right-hand side, and query for "LS Pharma Master Signature Form Applet".

3 Navigate to Control and query for Name = Signature.



4 Expand the User Properties control, and modify the value of the CLASSID property from {EFB7D763-97A3-11CF-AE19-00608CEADE00} to clsid:93E5204A-4344-4381-8912-8A7091E0FAE5.

5 Add a new property with the following values:

❏ Name: CodeBase

❏ Value: iSign90.cab#Version=4,5,0,319

6 Modify the value of the Enabled property from TRUE to 1.

7 Change the name of the Ink user property to Signature.


9 Repeat Step 1 through Step 8 for the Pharma Signature Display Form Applet.

To edit the LS Pharma Audit Signature Linear Form Applet

1 Within the Object Explorer, click on the Applet object.

2 Select any record on the right-hand side and query for "LS Pharma Audit Signature Linear Form Applet".

3 Navigate to Control and query for Name = Signature 1.

4 Expand the User Properties control, and modify the value of the property CLASSID from {EFB7D763-97A3-11CF-AE19-00608CEADE00} to clsid:93E5204A-4344-4381-8912-8A7091E0FAE5.


❏ Name: CodeBase


6 Modify the value of the Enabled property from TRUE to 1



9 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 Within Object Explorer, click on the Applet object.

2 Select any record on the right-hand side and query for "Pharma Signature Receipt Form Applet".

3 Navigate to Control and query for Name = Signature.

4 Expand the User Properties control, and modify the value of the property CLASSID from {EFB7D763-97A3-11CF-AE19-00608CEADE00} to clsid:93E5204A-4344-4381-8912-8A7091E0FAE5.




❏ Name: CodeBase


6 Modify the value of the Enabled property from FALSE to 0.



9 Repeat Step 1 through Step 8 for the Sign control.


Instructions for ACR 750Use 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 750ACR 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 750To apply ACR 750 to enable Web services using SAI for Oracle Fusion Middleware, perform the following:

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

2 Import the archive files.

For instructions, see “Importing Archive Files for ACR 750” on page 59.



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

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

5 (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 750This is a step in “Process of Applying ACR 750” on page 58.

To import archive files for ACR 750

1 Stop the Siebel Server (or servers).

2 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 Extract the archive files (.sif) from ACR750.zip. This ZIP file provides common archives for both Siebel Industry Applications and Siebel Cross-Industry Applications.

4 Edit the Siebel Tools configuration file (tools.cfg) to allow for import of symbolic strings.

a Navigate to the directory: SIEBEL_TOOLS_ROOT\bin\lang, where lang is the language directory specific to your deployment.

b Open the tools.cfg file in an editor, such as Notepad.

c Change the value of the SymStrPrefix parameter to SBL_, and then save the tools.cfg file.

5 Start Siebel Tools.

6 Lock the following projects:

■ EAI Business Services



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

7 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

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

9 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



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

2 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

3 Activate the new component definition that you created, using the following command:

activate compdef InfraEAIOutbound

4 Create the named subsystems EAIOutboundJVMSubsys and EAIOutboundsubsys.

a Use the following command for EAIOutboundSubsys:



create named subsystem EAIOutboundSubsys for subsystem OutboundEAISubsys with EAIOutboundContextFactory=weblogic.jndi.WLInitialContextFactory,EAIOutboundProviderURL="t3://weblogicserver:port,EAIOutboundSecurityCredentials=weblogic1,EAIOutboundSecurityPrincipal=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

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

5 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

6 Navigate to the SIEBSRVR_ROOT directory, and using the command prompt, create an XSD folder using the “mkdir xsd” command.


Instructions for ACR 7621 Navigate to <Tools Install Directory>\REPPATCH, and copy the ACR762.zip file.

2 Within the Tools.cfg file, edit the SymStrPrefix = X_ parameter to SymStrPrefix = SBL_.

3 Navigate to Tools\REPPATCH, and extract the ACR762.zip file.

Importing SIF Files for ACR 762Use the following procedure to import SIF files for ACR 762.



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.

2 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 Run the BatchImport batch file to import the new objects.

4 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 762The 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.

1 Add a new field to the Client - Mobile business component:

Name Column Pre-Def Value Pick List

Remote Node Type

REMOTE_NODE_TYPE_CD

Expr: "LookupValue(""REMOTE_NODE_TYPE"",""SIEBEL_REMOTE"")"

LS SGOP Remote Client Type Picklist

Pick Map

Parent Field Field Picklist Field

Remote Node Type

Remote Node Type

Value



2 Add a new field to the Pharma Address business component:

3 Add a new list column to the Mobile Client list applet with the following values, and map the new column to the Edit List:

4 Within the Siebel Life Sciences application, add a new screen menu item:

Applying Schema Changes for ACR 762Use the following procedure to apply the schema changes for ACR 762.

To apply schema changes for ACR 762

1 From within Siebel Tools, navigate to the Object Explorer and select Table.

2 Query for the new or modified tables (S_TXN_LOG_LS OR S_TBLOBJ_MAP_LS OR S_NODE).

3 Click the Apply/DDL button to apply the schema changes.

Importing Seed Data for ACR 762The seed data for ACR 762 has been provided in a .dat file.

Fields

Name Column Join Force Active

Row Id ROW_ID S_CON_ADDR TRUE

Business Component Class No Insert

Client - Mobile CSSSWEFrameListVisibilityPick TRUE

List Columns

Display Name Field

Display Name Display Name String Reference

Pick Applet

Remote Node Type

Remote Node Type

Remote Node Type

SBL_LS_SGOP_REMOTE_NODE_TYPE

Screen Menu Item

Screen Text Text String Reference

Screen Text Text String Reference

LS SGOP Modification Tracking Admin Screen

Administration - Modification Tracking

SBL_LS_SGOP_ADMINSTRATION_MODIFICATION_TRACKING



Use the following procedure to import seed data for ACR 762.

To import seed data for ACR 762NOTE: Before you import the seed data, you must have applied the schema changes for the new tables.

1 Create an ODBC entry for the database where you plan to import the seed data:

a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC), navigate to the System DSN tab, and click Add.

b Select the "Siebel Oracle90" driver (from Datadirect Technologies).

c Enter a data source name (such as Siebel_DSN.

d 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 Navigate to the directory where you installed Siebel Tools and change the directory to REPPATCH\ACR762.

3 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 Before executing the next step, make sure that the dataimp.exe file exists in the <Tools Install Directory>/bin directory.

5 Run the ImportSeed batch file to import the seed data.

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

7 Update the Object Table Mapping records:

a Log into the Siebel application as an administrator (sadmin/sadmin).

b Navigate to Modification Tracking Admin Screen > Object Table Mappings view, and update the following records:

Object Name Table Name

LS SGOP_RelatedContact S_PARTY_REL

LS SGOP_RelatedAccount S_PARTY_REL



Importing Web Services for ACR 762The 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 Navigate to <Tools Install Directory>\REPPATCH\ACR762.zip, and unzip the file.

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

3 Log into the Siebel application as an administrator (sadmin/sadmin).

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

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

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

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



&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 7621 Bounce the server and launch the Siebel Server URL.



2 Navigate to Site Map > Administration - Data > List Of Values, and create the following list of values:

Enabling Modification Tracking1 Bounce the server and launch the Siebel Server URL.

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

3 Navigate to Site Map >Administration - Server Configuration > Synchronize, and click the Synchronize button.

4 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

5 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

6 Wait until the new job completes, and repeat Step 5 for each remote client to complete remote client setup.


Type Display Value LIC

REMOTE_NODE_TYPE Offline Client OFFLINE CLIENT

REMOTE_NODE_TYPE Siebel Remote SIEBEL_REMOTE

REMOTE_NODE_TYPE Both BOTH

REMOTE_OPERATION_TYPE FullDownload FullDownload

REMOTE_OPERATION_TYPE Insert Insert

REMOTE_OPERATION_TYPE Update Update

REMOTE_OPERATION_TYPE Delete Delete



Instructions for ACR 802The following sections describe how to configure ACR 802.

Preinstallation Task for ACR 8021 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 parameter’s original value, as you need to change the prefix back to that after you have imported the SIF files.

Importing Repository Objects for ACR 8021 Navigate to <Tools Install Directory>\REPPATCH\ACR802.zip, and extract the file.

2 Open Siebel Tools connected to the relevant database, and using Object Explorer, navigate to Projects.

3 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. Repository Objects for ACR 802

S. No Repository Type SIF File Name

1 Applet Applet \ Applets.sif

2 Busienss Component Business Component \ BusinessComponents.sif

3 Business Object Business Object \ BusinessObjects.sif

4 Business Service Business Service \ BusinessServices.sif

5 Picklist Picklist \ PickLists.sif

6 View View \ Views.sif



To import repository objects

1 Open Siebel Tools connected to the relevant database, and from the main menu, select the Tools > Import from Archive option.

2 Import the files listed in Table 41 on page 69 one at a time, using the merge option, and click Next.

3 Review the changes within the Import Wizard - Review Conflicts and Actions window and click Next.

4 When the system displays the "Do you want to proceed?" confirmation message, click Yes to import the repository objects.

5 Click Finish to close the Import Wizard window.

Applying Schema Changes for ACR 802As 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 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.

2 Lock the Table Loyalty project. following project

7 Class Class \ Classes.sif

8 Workflow Workflow \ WorkFlows.sif

9 Symbolic String Symbolic String \ SymbolicStrings.sif

10 Integration Object Integration Object\IntegrationObjects.sif

11 Link Links\Links.sif

Table 41. Repository Objects for ACR 802

S. No Repository Type SIF File Name



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

2 Select the Apply/DDL option.

3 Within the confirmation dialog box, select Apply and then click OK.

Then Apply Schema dialog box displays.

4 Within the Apply Schema dialog box, provide details for the following fields.

a Within the Tables drop-down list, select Current Query.

b Within the Database user field, enter the database user name.

c Within the Database user password field, enter the database user password.

d Within the ODBC data source field, enter the ODBC name.

5 After filling out the fields in the Apply Schema dialog, click Apply.

6 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 Launch siebel tools connecting to the relevant database

2 From the main menu, select Tools > Compile Projects.

3 Press the CTRL key pressed, select the LOY Admin, LOY Engine Buscomps, SIA Server Object, LOY Gen Import, and Table Loyalty projects.

4 Select the relevant SRF file for your installation and then click Compile.


Instructions for ACR 839The following sections contain configuration instructions for ACR 839.

Preparing for the ACR 839 Installation1 Navigate to \REPPATCH\ACR839.zip and unzip the file to any location accessible by Siebel Tools.



2 In Siebel Tools, lock the following projects:

■ LS Clinical Protocol Site

■ Table Clinical

■ EIM Clinical

■ Symbolic Strings

Installing ACR 839 Using the Automated Process1 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 Create a folder called named Log in <Unziplocation>\REPOSITORY.

3 Run the import.bat file to import the .sif files, and check the log file to verify that all of the files imported successfully.

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

5 Import the workflow processes into Siebel repository. For more information, see “Importing Workflow Definitions for ACR 839” on page 78.

6 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 839NOTE: 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



■ 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 Within Siebel Tools, query for the list of tables that were imported into the repository.

2 Click the Apply/DDL button to apply the changes to the physical database.

3 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 839NOTE: 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



■ Column: ROW_ID

■ Text Length: 15

■ Type: DTYPE_ID

Clinical Trip Report Business Component (Modified)

1 Add the following Joins and Join Specifications fields described in Table 42 and Table 43:

2 Add a join with the following values:

Table 42. Joins and Join Specifications Fields for ACR 839 (Continued in Table 43)

Name Column JoinImmediate Post Changes No Copy

Email Format FORMAT_TYPE_CD S_EVT_MAIL

Emp Id EMP_ID S_ACT_EMP

Active Login Name

LOGIN S_USER

Table 43. Joins and Join Specifications for ACR 839 (Continued from Table 42)

Name (Continued) Picklist Type Required Calculated

Predefault Value

Email Format DTYPE_TEXT

Emp Id DTYPE_ID

Active Login Name

DTYPE_TEXT

Table Alias

S_ACT_EMP S_ACT_EMP

S_USER S_USER



3 Add a join specification with the values in the following table:

Configuring Links for ACR 839NOTE: 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.

1 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

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

Alias Name Destination Column Source Field

S_ACT_EMP Visit Employee ACTIVITY_ID Id

S_USER Emp Login ROW_ID Emp Id

Clinical Trip Report Business Component User Properties

New/Changed Name Value

Changed (Deep Delete changed to Deep Delete 1)

Deep Delete 1 Activity Plan

New Deep Delete 2 LS Clinical Site Visit Location



To update the changed business objects

1 Within Object Explorer, select the Business Object object type, and query for Clinical Trip Report.

2 Within Object Explorer, expand Business Object.

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

Configuring Symbolic Strings for ACR 839NOTE: 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 839NOTE: 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 839Import the following .sif files using the Import from Archives function within Siebel Tools:

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

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

Business Component Link Description

LS Clinical Site Visit Location Clinical Trip Report/LS Clinical Site Visit Location

Retrieves the data specific to the site visit

LS Clinical Site Visit Employee Clinical Trip Report/LS Clinical Site Visit Employee

Retrieves the employees specific to the site visit



Configuring Screens for ACR 839NOTE: 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 In OBLE, navigate to the Screen object.

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

3 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 839NOTE: 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 839NOTE: 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 Lock the LS Clinical Protocol Site project.

2 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

3 Compile the locked projects.

Screen Screen ViewsViewbar Text on Screen View

Clinical Site Management Clinical Trip Report Detail View with Geo Location

Geo Location Details

Clinical Site Management Clinical Trip Report Detail View with Geo Location Without CRF

Geo Location Details



Importing Workflow Definitions for ACR 839NOTE: 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 From Object Explorer, navigate to Workflow Process, and from the list applet, right-click and choose Import Workflow Process.

3 Navigate to <Unziplocation>\REPOSITORY\Workflows, and select SWI LS Clinical Query Protocol Site_Site Visits.xml.

4 Navigate to <Unziplocation>\REPOSITORY\Workflows, and select SWI LS Clinical Create Site Visit Geo Location.xml.

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

6 Repeat the preceding steps for the remaining new workflows.

Activating Workflow Definitions for ACR 839Use the following procedure to activate workflow definitions.

To activate workflow definitions

1 Log into Siebel eClinical, and navigate to the Administration - Business Process > Workflow Deployment view.

2 On the Repository Workflow Processes applet, query for the following workflows:

3 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

New/Modified Xml File to Import Workflow Name Project

New SWI LS Clinical Query Protocol Site_Site Visits.xml

SWI LS Clinical Query Protocol Site_Site Visits

LS Clinical Protocol Site

New SWI LS Clinical Create Site Visit Geo Location.xml

SWI LS Clinical Create Site Visit Geo Location

LS Clinical Protocol Site



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 839NOTE: 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 Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC), click the System DSN tab, and click Add.

b Select the "Siebel Oracle90" driver (from Datadirect Technologies).

c Enter a data source name (such as DevelopmentDB).

d Enter the server name to connect to.

❏ For Oracle enter the TNS service name that you created to connect your tools to the DB.

e Test your connection and click OK when tested successfully.

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

3 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

4 Run the Import_Seed_Data.bat file to import seed data.


Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B ■ Siebel Fix Pack Installation Instructions

5 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 839Note 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:


Siebel Fix Pack Installation InstructionsThis 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

Web Service Name Direction

SWILSClinicalQueryProtocolSite_SiteVisits Inbound

SWILSClinicalCreateSiteVisitGeoLocation Inbound


Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B ■ Siebel Fix PackInstallation Instructions

Siebel Fix Pack Installation OverviewThis 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



Installation Scenarios Described in This GuideThis 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 ReleasesThis 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.



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



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



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



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

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

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

■ Siebel_Image is the directory for your version-specific Siebel installation image, such as C:\Siebel_Install_Image\8.1.1.x.

4 Double-click setup.exe to start the Siebel Enterprise Server installer for version 8.1.1.x.

5 Select an instance of version 8.1.1 or 8.1.1.x to patch, from the list of detected Siebel installations.

6 Follow all prompts to complete installation of version 8.1.1.x.

7 Repeat these steps on each computer with a Siebel Enterprise Server component installation to be patched.



8 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 WindowsThis 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 Stop the Web server.

2 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 Double-click setup.exe to start the SWSE installer for version 8.1.1.x.



6 Repeat these steps on each computer with an SWSE installation to be patched.

7 Restart the Web server at the end of all Fix Pack or other patch release installation for server-based products.

For more information, see “Postinstallation Tasks for the Web Server” on page 97.

Installing the Fix Pack for Siebel Management Agent and Siebel Management Server on WindowsThis 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.



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 Stop the Siebel Management Agent service.

2 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 Double-click setup.exe to start the Siebel Management Agent installer for version 8.1.1.x.



6 Restart the Management Agent service.

7 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 Stop the Siebel Management Server service.

2 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 Double-click setup.exe to start the Siebel Management Server installer for version 8.1.1.x.



6 Restart the Management Server service.

7 Repeat these steps on each computer with a Siebel Management Server installation to be patched. (In most deployments, only one instance is installed.)



Installing the Fix Pack for Siebel Mobile Web Client, Siebel Tools, or Siebel Client Sync on WindowsThis 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.

2 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 Double-click oui.exe to start the Siebel client or Siebel Tools installer for version 8.1.1.x.

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


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



To install the Fix Pack for Siebel Client Sync

1 Exit any Siebel software on the client computer where you are installing the Fix Pack.

2 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 Double-click install.exe to start the Siebel Client Sync client installer for version 8.1.1.x.



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



Installing the Fix Pack for Siebel Enterprise Server on UNIXThis 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).

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

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

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

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

6 (AIX only) Execute slibclean, as follows:

/usr/sbin/slibclean

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

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

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



where:




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 UNIXThis 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 Log on to the server using the Web server owner account.




/usr/sbin/slibclean

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





6 (For GUI mode) Run setupUNIX_OS to start the SWSE installer in GUI mode for version 8.1.1.x, where:



7 (For console mode) Enter the following command to start the SWSE installer in console mode for version 8.1.1.x:


where:




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 server-based products.

For more information, see “Postinstallation Tasks for the Web Server” on page 97.

Installing the Fix Pack for Siebel Management Agent on UNIXThis 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.



To install the Fix Pack for Siebel Management Agent (where Management Agent was installed separately)

1 Stop the service for the Siebel Management Agent.




/usr/sbin/slibclean

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



5 (For GUI mode) Run setupUNIX_OS to start the Siebel Management Agent installer in GUI mode for version 8.1.1.x, where:



6 (For console mode) Enter the following command to start the Siebel Management Agent installer in console mode for version 8.1.1.x:


where:




9 Restart the Management Agent service.

10 Repeat these steps on each computer with a Siebel Management Agent installation to be patched (where Management Agent was installed separately).



Configuring Slipstream Patch InstallationThis 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_executableArg = argument



where:

■ full_path_to_Siebel_product_installer_executable is the full path to the installer executable program, located in the installation image for the release that will be installed using slipstream patch installation.

■ argument is the following value for the parameter Arg, for a server installation:

Arg = -args PatchInstance=$(SiebelRoot) Slipstream=yes

Examples for Specifying Execute ParameterTo 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 InstallationsIf, 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 ServerThis 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.



Postinstallation Tasks for the Web ServerThis 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 ClientsThis 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.



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



2 Select a source language and a target language.

The source language is the language of the locale-specific data in the LMU file you are importing. The target language is the Siebel language into which the strings will be imported.

3 Click the Import tab.

4 Enter the name of the LMU file from which you want to import locale-specific attributes.

You can also use the Browse button to find and select the file.

5 Specify whether you want to mark records in the repository with the Redo flag that have changed since the export occurred.

When the import occurs, the LMU compares the source language records in the repository with the source language records in the import file. If the records in the repository have changed since the export occurred, they are marked with the Redo flag. This flag helps you identify records that might need to be retranslated.

6 Click Import.

7 After finishing, recompile the SRF file and restart the Application Object Manager component on the Siebel Server to see the results.

Uninstalling Siebel Fix PacksThis 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



Scenarios for Uninstalling a Siebel Fix PackThis 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 PackThis 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).

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


Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B ■ Resolved ChangeRequests

■ optional_arguments is one or more valid arguments for the uninstaller. For example, specify -is:javaconsole -console to run in console mode.

2 At the prompt, select Maintenance Release Uninstall.

Guidelines and Limitations for Siebel Fix Pack UninstallationThis 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 RequestsThe 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 version-specific. 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.


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

Issue Addressed Bug IDBase Bug ID Subcomponent

Special Instructions

Siebel Apps - Customer Order ManagementCustomizable Prod/Configurator

Modifying a bulk request yields an error message that the deleted item field is not present

12801963 APIs

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

10589378 10587003 APIs

The Check Eligibilty Helper step invokes the wrong signal

12800345 Eligibility & Compatibility

When a child record is removed, the grandchild record is not removed as well

12826991 Rule Behavior

BatchValidateDetailedExpl crashes if a product has a minimum quantity violation and any rule is activated

10583881 Rule Behavior


Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B ■ Resolved Bugs in theSiebel 8.1.1.7 Fix Pack

ACR 502: The Quick Edit web template is not packaged with the installation files

12420803 Runtime

ACR 471: The UMF message is not reflected properly and promotions are not selected

12847176 12560619 Runtime

Child products that have been defaulted by min cardinality do not have NULL in the CFG_STATE_CD column

12399998 12397774 Runtime

The NoSave property does not work

12751510 10601639 Runtime

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

12398737 Saved Configurations

When users create product constraints in the Admin - Product view, the application crashes

12806588 11717572 User Interface

When pick applets are used to populate attributes, Dynamic Hide functionality does not work

12809668 User Interface

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


Order Administration

Agreement Approval functionality uses the wrong email template

12750196 Quote/Order Validation

Pricing Mgmt






The price is displayed incorrectly within the NRC field within line items

12723829 Price List

Product Administration

Action Code updates are not supported when editing simple products with attributes

10592171 10591152 Product Attributes

The RCOIS GetAttribute method returns attribute values that have not been translated into the display value for an enumerated attribute definition

10595715 10594080 Product Attributes

Product Promotions

Order line items are not created properly when they are created using Favorites functionality

10588017 10587582 Administration

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 non-root products

12852048 API

Allows users to disable a full table scan on the S_ASSET table

13043868 Runtime

IntegrityCheck does not pick up migrated assets

12996503 Runtime

Negative price overrides within the Edit Promotion applets are totalled incorrectly

12902863 Runtime

PSP Engine






In version 8.1.1.5, within Siebel Pricer, the Internal Integration functionality does not work properly

12857820 10585340 PSP Procedures

When users add a product to a quote, they receive the SBL-BPR-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

12705438 Asset Based Ordering

If Inclusive Eligibility is checked for a product, Configurator throws an error message

12794483 10605987 Eligibility & Compatibility

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)

12914620 12914658 Orders

If the PSP Engine/workflow is not used for pricing, the Extended Quantity field is not updated appropriately

10571055 10569588 Pricing

Siebel Apps - Data QualityData Quality






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

13065192 10603335 Batch Deduplication

The Data Quality real time deduplication functionality fails and displays an error

12324343 Data Quality

ACR 761: Provides a Data Quality sync switch

12618902 ODQ Connector

When an account, address, or contact record contain a special character, the SBL-DAT-60236 error message appears

13065076 10577129 Universal Connector

Previously-created records are not visible in the Duplicates view

11938030 Universal Connector

Siebel Apps - Field ServiceActivities

The FS Holiday Service API GetReponseTime method returns incorrect results

12596631 11823910 Activities

The Done field information for an activity is not synchronized to the server

12659425 11769292 Activities

Holiday API-GetElapsedBusinessTime does not work properly for different timezones

11788501 Activities

Field Service

Using the browser’s Back Button causes inefficient queries against S_EVT_ACT

10554464 10541485 Dispatch Board






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

10606526 10599378 Home Page

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

10585770 10582454 Shipping

Siebel Apps - Handheld ClientHandheld Client

The ScanAPI.dll file does not load error messages on the Motorola embedded barcode scanner

12810013 12720131 Barcode

When users drill down, context is lost

11795432 10602136 Client App

TAG:GetDirect does not retrieve multiple fields at once from the database

12411534 10592042 Printing

Handheld Sync

Duplicate transactions and data corruption occur

10592695 10591333 Direct Server Sync

Translation problems occur when strings contain words that are glued together (such as PatchAgent)

12857245 Patch Deployment






Makes sure that other Siebel .exe files are closed when PatchAgent needs to be started manually

10596115 10595588 Patch Deployment

Siebel Apps - MarketingMktg/Campaign Mgmt

Campaigns partially fail with the capacity warning

12703358 Campaign Processing

Different customer ids that exist in S_MKTEVTRG_HST are not loaded in S_CAMP_CON

12534286 Campaign Processing

Mktg/Email Marketing

When users save an offer template multiple times, the trackable URL stops working

12604183 Email Editor

Siebel Apps - Multichannel TechnologiesCommunications Server

HTML templates are truncated for Email Activities

10573591 Outbound Communication - Email

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

12887912 Templates

CTI






Siebel Agent web sessions time out when an agent is on a phone call or is chatting

12937764 Custom Drivers

There is no configuration option for logging out of orphaned sessions

10592992 10571641 Server Configuration

Email

When an email has extra characters in the "Content-Type: application/octet-stream; name=" section, inbound emails arrive over and over every five minutes

12530877 Email

With E-mail Response, unable to get proper substituion fields when using F9

10596275 10591050 Email

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

12828709 Send Email

eMail Response

Emails are rejected as Incomplete Header Line

10582649 10579692 Mail Server

Siebel Apps - Oracle Customer HubUniversal Customer Master

Errors occur while attempting to import PLK Symbolic Strings (ACR475_LMU_PLK.txt)

12556743 Other






Siebel Apps - PRMPRM Partner Manager

If there is an apostrophe in a prospective partner name, an error can occur when users click the Qualify button

10547826 10543941 Error Messages

Within Administration - Partner > Prospective Partners view, if the address of the prospective partner is a duplicate, partner qualification fails

10569529 10567133 Partner Admin

PRM Partner Portal

When the application is stopped and then resume, answers that have already been submitted are not retained

12573896 12432848 Other

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

10598235 10551381 Partner Programs Screen

Siebel Apps - SalesDun & 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






Siebel Apps - Search & Knowledge ManagementSearch - Oracle SES

Users can search with an attachment name but not with the contents of the attachment

10587092 10585429 Core Oracle SES

Long columns are indexed as content links rather than as attributes

10596898 10592900 Indexing

OSES searches do not return the number of records on the Records applet

13019417 Results UI

When users click on the Advanced Search link, data is lost

10582433 10582367 Saved Searches

Siebel Search

With the implementation of the German umlauts character content search, blank dates occur when Fetch Language-Specific Docs is selected in Search preferences

13252298 Results UI

When users click on search results, changes that they have made are not saved

12536584 11668672 Search Center

Search crashes when users navigate to the All Accounts Across Organization view

12795298 Search Center

Smart Answer

Provides Microsoft Windows 2008 R2 support for Smart Answer

13023227 11767223 Smart Answer






Siebel Apps - Self Svc: ADFE-Commerce

After ACR 502 has been applied, the Self-Service eCommerce application does not work properly

12322627 12429365 Other

Attachments of type URL are not displayed in eSupport SR Detail Page

10597748 13086583 Other

Siebel Apps - ServiceAssignment 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 ManagementTerritory Management - Sales






Users are unable to add multiple conditions in a Territory Alignment created by another user

10598582 10597734 Territory Management

Siebel Apps - UCMUniversal Customer Master

When a guided merge is performed, survivors do not remain in the Duplicates view

12802129 Merge Request

Improves the quality of error messages in the IAI category

10566294 10566293 Other

Errors occur when users click Merge within existing duplicates

12998690 12901373 Other

When an address is added to an account and a contact, the sdq dedup no memory error message occurs

12982010 12887716 Other

Siebel ChartsCharts

When users click twice on the Go button within the Chart applet, a blank chart displays

10588465 10585178 Chart Engine

Siebel Communications & EnergyIntegrations






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, ListOfSWIOrderItemPreviousValues" section is blank

13081720 AIA

Siebel Consumer GoodsADL

ACR 480: Copy should be disabled when selecting multiple target accounts

12916136

In CSSBCCopyADL::CopyADL method, the service is never released and set to NULL, which can cause a memory leak

12742166

Promotions

A couple of member variable business components are not initialized to NULL in the CSSAccntPlanSvc class, so destructor releases them

13068408

In Admin Data > Account Product > Price List, when users click the Update Price/Cost button, too many records appear, and performance suffers

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






If no active merchandising location is selected, the application crashes

13068452

Siebel Core - EAIIntegration - Transports

The user credentials in the jndi.properties file are stored in clear text format

13080056 JMS

JMS Receiver Auto Restart parameters do not allow users to specify when a component tries to reconnect

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

10589245 10581466 EAI Server Components

Yes, see “Instructions for ACR 750” on page 58.

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

12629343 Other






The EAI Siebel Adpater/EAI UI Data Adapter ignores PDQ Sort Spec

10603642 10591549 Other

Java Integration

Business service migration fails for the QueryBid method

12920858 Resource Adapter

Modified XSDS do not work with REST because Clear Cache is not called


There is no automation script for outbound configurationN

12691178 11733621 Resource Adapter

A deadlock occurs while deleting RA+MDB on WLS


There is no option to set the log level for outbound JMS logs


Not needed 11733621 Resource Adapter

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


Web Services






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

12727594 12673517 Inbound

When an invalid value is passed to pagesize, the application crashes instead of providing an error message

12953834 Inbound

Requests greater than 25 KB are not being returned from inbound HTTP requests

12736823 Inbound

In the fix for Bug 12763892, the business object is not released for the Leads service, which causes performance issues

13063284 Inbound

Outbound Web services do not work when calling a method that is hosted on WLS

10605839 10584990 Outbound

Siebel Core - EIM/DatabaseDatabase

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

10631899 Connector

Provides Siebel Connector fixes for IBM DB2 UDB and Oracle databases to address Bug 12985589 and Bug 12676475

13384863 13384850 Connector






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

10591636 10591201 Connector

An Oracle Connector CLOB + OCI descriptor leak occurs

13024449 10597810 Connector

In DB2/ZOS V10, the changed catalog table SYSIBM.SYSTRIGGERS catalog table was changed in a way that made it incompatible

13088789 IBM DB2/400

When resuming a task, fields that have the DATETIME type no longer hold their original values

12800053 MS SQL Server

In version 8.1.1.6, on Microsoft Windows 2008 R2, the Generate New Database job does not terminate and continues running

12995880 12355084 MS SQL Server

Siebel Core - Handheld SyncHandheld Sync

When the connection between the PDA and the server breaks, the Sync OM task continues running and does not terminate

12925053 12364796 Session Admin

Provides the server-side fix for Bug 12364796

12925628 12860325 Session Admin

With WM 6.5.3, the Customize tool bar screen is distorted

12734984 Session Admin

With WM 6.5.3, after the initial sync, when users lauch the application, the resolution is not correct

12734477 Session Admin

WebPhone






Records that contain a + sign in row_d cause the Wireless application to crash

12784519 11728298 HTML

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

In the Polish application, when there are sync conflicts, the client hangs with the "out of memory" error message

12810197 Lotus Notes

Corrects the translation.txt file installed for the Portuguese (Brazil) language

12922570 Lotus Notes

CRM Desktop

The copyright information is not displayed correctly

10587345 Admin

Provides a mechanism to upload an entire metadata package in a single file

12831330 12831319 Admin

Error message for invalid packages are not translated to Japanese

12597920 Data Sync

Recurring event exceptions are not reflected in attendee calendars

13341578 11729977 Data Sync

When users create a new meeting, invite attendees, send the invite, and then sync, a sync issue appears

13477759 Data Sync

Duplicate calendar items are created if an attendee is added after the first sync

13391431 Data Sync






On Microsoft Windows 7, the CRM Desktop shortcut does not launch the CRM Desktop

12997576 Installation

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

10590982 Outlook Client

Non-primary employees can delete activities


When users try to connect to the incorrect server, the resulting error message is not translated to Japanese







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







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

10606075 10585409 Performance

When the Siebel Server fetches 50 records, it takes more than 70 seconds

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

10598827 10598740 Calendar

Siebel Core - Server BizLogic RulesConfig - Rules

Errors occur when synchronizing from Haley to the Siebel application

12318676 Rules Engine

Siebel Core - Server BizLogic Script






Config - Scripting

Calling multiple methods in a single statement on smartscript objects produces a compile error

12865043 ST Engine

"Nested with" statement blocks do not resolve correct references

12833238 ST Engine

Calling a task from eScript crashes the Object Manager

10549592 T Engine

Integration - Scripting

Crashes occur two to three times a day on production servers

12570179 New eScript Engine

Deduce Types requires a return statement in the catch block to compile

10582714 10534318 New eScript Engine

Siebel Core - Server BizLogic WFBusiness 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

13117431 Workflow Process Execution

Activating a workflow process in one repository inactivates a workflow in another repository

12658950 Workflow Process Execution






Modulus operator MOD in the expression builder does not produce correct results

12591236 12405401 Workflow Process Execution

Unwanted SQL select statements occur when using a Siebel operation in a subworkflow

13033536 12879239 Workflow Process Execution

Siebel Core - Server InfrastructureSecurity

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






GetSearchSpec/SetSearchSpec unable to handle strings with apostrophes in SVB

10602278 10485907 Other

Siebel Core - UIF ClientAX/HI Web UI

Alarms do not reload consistent with the defined reload frequency

10586703 10584220 Calendar

The high-interactivity calendar allows users to reschedule signed calls

10566356 10566354 Calendar

SI Web UI

Allows calendar to work after installation of non-res:// calendar implementation

12741601 Calendar

Within Contacts, Calendar Tool Tips for appointments do not display meeting information

12838557 Calendar

Addresses various issues around dragging calendar appointments

12869678 10595170 Calendar

Allows suppression of the timestamp for events on the 7-Day calendar

11682527 11682517 Calendar

In the Hebrew version of the application, the cursor sticks when typing text

10536337 10529645 Calendar

Within the Portuguese and Spanish applications, the calendar displays in English

10605376 10605375 Calendar

If an employee's name contains a single quote, that employee's calendar cannot be accessed

12805219 Calendar






With the Casablanca timezone, the first weekend in April displays incorrectly

13082392 12730479 Calendar

When users create a contact record using copy-and-paste functionality, an error message appears

12831075 12578368 Controls

After version 8.1.1.5 has been applied, the Siebel application does not send parameters to Actuate

12822135 Controls

After version 8.0.0.10 has been applied, special characters appear in drop-down lists

13095646 11810469 Controls

When a session timeout occurs, the application crashes

10545453 10537307 Controls

An empty shuttle applet appears when users click within the application

12807613 12653248 Layout and Rendering

When there are two duplicate account names, importing contacts adds an entry to the first account in the contact list

12991744 10598313 Others

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

12984684 11711790 Popups

Tabs are not hidden in eService

10598444 10598429 Sitemap

Scripts execute twice 12608463 10605076 STD:Javascript

The application hangs if users click Enter instead of Alt + Enter to run a query

13080852 13071172 UI Behavior






SQL generated on the Clinical Trip Report business component does not honor search specifications

12768910 12407059 UI Behavior

On the Mobile Web Client, when EnableFQDN=FALSE, Amazon links are not visible

12882858 UI Behavior

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

12958059 10598010 UI Behavior

When users select multiple records by pressing Shift, not all of the records are selected

12997878 10600303 UI Behavior

Siebel Core - Unix/WindowsPlatform Support

ACR 698: Certifies AIX 7.1 13063733 AIX6L v6.1

ACR 699: Certifies Oracle Enterprise Linux 6.1 (64-bit)

13348117 Oracle Enterprise Linux 5

On Exalogic (Oracle Enterprise Linux 5.5 UEK) systems, the Siebel Server crashes during startup

12902189 Oracle Enterprise Linux 5






Provides a mechanism to set the default stack size for Posix threads on all UNIX platforms

12959307 12420463 Solaris 10/Sparc

After version 8.1.1.6 has been installed, SWSE configuration fails

13055566 Solaris 10/x86

The "./STARTAPA-SSL function does not work to enable SSL on the HP platform

12971646 11825060 Web Server

Siebel Core - zSeriesDatabase

ACR 701: Certifies IBM DB2 v10 for z/OS

13632576 IBM DB2/390

The strgxtrct utility is not written to cope with the new DB2 v9 PriQty and SecQty allocations of -1

10599350 IBM DB2/390

Siebel CRM Integration to Oracle Realtime SchedulerSiebel Components

When more than one skill is assigned, the Siebel session hangs

12896102 Address, Employees, Activities

Siebel Data ModelData 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






EIM_PRPDTL_TNT does not resolve foreign keys for custom mapping

10603651 10601933 Schema

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

13013178 EIM Table Mappings

While loading through EIM, an error occurs while setting the primary value

10560634 EIM Table Mappings

Siebel DocumentsDocuments

ACR 628: The Submit and Done buttons are enabled for failed correspondences

12434735 11895574 Correspondence

Siebel Engineering - Release EngineeringRel 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 SciencesActivities

The Detail button is disabled in the Call Details view

13430653






Within the Call Execution view, the Validate button does not behave consistently

13450349

The system allows enables capturing signature on paper and call submission without any samples

13431474 13430280

The Interactive Detailed button is disabled in the UI.

13500588

Within the Chinese application, the confirmation message that appears after users submit a contact call is translated incorrectly

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






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

13450252

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

13373693

No error message displays when users do not provide information in mandatory fields

13373799

The Comments field accepts more than 250 characters

13373712

The Done field accepts values other than Y and N

13373669

Within the Sales Assessment Template Web service, field validation is missing for a few fields

13386254

Not all of the values for the Follow Up picklist display

13373760

The Sales Assessment Template Web service shows all operations in the UI

13375345

Product Issues

ACR 712: The Device Available field information contains values other than Yes and No

12943304

ACR 712: The Send to Safety button sends incorrect data

13085829






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


Smart Calls

Products in smart calls are not applied

10604049 10578468

Web Services






ACR 762: Ports SonGo Web services to Siebel applications version 8.1.1.x for iSales


Siebel LoyaltyAccruals

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

12845264

Within version 8.1.1, points round if the points value is a decimal value

10570794 10570253

Decimal points are not rounded up

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

13039511

The Bulk Admin Membership process remains in the InProgress state even after a workflow is activated

12997281

There is no Go button in the Bulk Admin applet, so users have to press Enter to run a query

13039598






The error log shows duplicate invalid member numbers when at least one member is valid in a set defined by Bulk Unit Size

13033551

Incorrect validation error messages occur when users click the Process button

13039569

The Member Merge functionality does not merge or combine enrolled promotions

13027135

Merge actions do not work for member field attributes

10562859

On the Solaris platform, Bulk Admin functionality appends \A to the file name

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

"10547259

Slow SQL occurs for the LOY All Transactions view

12664236 10605463

Partner Administration

The end date is not considered for the Precalculated Accrual condition

12952157 12952144






Promotions

The Does Not Equal and Empty conditions do not perform as expected

12948668

Allows for an integer division operator in the promotion rule definition.txt file

10501048

Allows calculations not to round to two decimal places

10515441

Allows calculations not to round to two decimal places

10525601 10515441

Redemptions

Resolves a problem with concurrency in the redemption process

12663663

When 100 postings are initiated for the GetPriceOption scenario, each posting takes 25 to 38 seconds

12664159 12338939

Users cannot redeem decimal values while processing redemption transactions

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 ReportsReports BI Pubisher - App

The XMLP Purge Records workflow does not delete all of the reports

11828119 11824462 Call Center






After users run a report that contains no rows, the following reports also return no rows

12931618 12629343 Common Components

After users run a report that contains no rows, the following reports also return no rows

12931619 Common Components

Users cannot execute BI Publisher reports for languages that have not been shipped

11830300 Internationalization

Reports BI Publisher - Infra

On the Mobile Web Client, reports that are created in the Custom Templates view do not appear

11773795 10595951 Connector

Users are not able to configure or specify the maximum threshhold for the number of parameters

12627637 Connector

Allows users to rename Report menu labels

11886536 Connector

Within the Report business service, the AttachEntity method does not function properly

11733042 10577265 Connector

The Parameter applet does not display scroll bars

13442150 Connector

BIP Report Wait Time is not supported for Scheduler and on the Dedicated Client\

11723184 Connector

Multi Org Reports are not solely based on the Organization field within the Reports - Custom Template view

12907125 Connector






Adding responsibilities through Siebel security model should only query for XMLP* responsibilities, not all 700+ responsibilities

11733046 12374984 Connector

It is not possible to run multiple-language reports on a single object

12384180 Connector

When duplicate report names are entered, the incorrect error message displays

11733031 11731294 Connector

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-RPT-50584)

11773906 Connector

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

12627598 Connector

Includes a method on the Report business service to enable scheduled reports submitted using a business service

12627588 Connector






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

12627610 Connector

In version 8.1.1.6, within <Tools Install location>\REPPATCH\BIP_8115\SIA\REPOSITORY, the SIF files are incorrectly named

12971470 Connector

Provides enhancements to the My Reports view

12780408 Connector

When no search specification has been given, no error message displays for a non-primary integration object

11731294 Connector

The successful-upload error message does not appear when users upload a template for the first time

11773937 10596309 Connector

Parameter labels are not aligned correctly in the Parameters dialog box

11901290 Connector

Parameterized reports are not supported in Scheduler

11723728 Connector

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

13469718 Connector

The Report business service does not have the Custom Report Name Input property

12627606 Connector






Report parameter LOVs are restricted to the Report business object

12627683 Connector

Within the My Repors view, the status of In Progress is invalid

10562579 10551799 Connector

Within the Report Template Registration applet, when users click Upload, there is no confirmation message

10551927 Connector

Within the Report Template Registration applet, when users click Upload, there is no confirmation message

10551928 10551927 Connector

Query strings are not passed as part of XML

10594924 10559184 Connector

The BI Publisher Report business service does not launch on the Mobile Web Client

10562793 10562792 Connector

The BI Publisher Report business service does not launch on the Mobile Web Client

10562792 Connector

Users cannot set HTTPSleepTime for BI Publisher integration

10606449 10571200 Connector

When the BIP Report Wait Time threshold is exceeded, the popup window that displays is not in focus

10590983 10587343 Connector

Reports that are created in the Custom Templates view do not display on the Mobile Web Client

10595951 10595950 Connector

When users try to create a new report with the same name as an existing report, they do not receive an error message

10596309 10596288 Connector






Reports fail when the ''> Today () AND < Today () +365' fuctions are used within the Close Date field

10603328 10603312 Connector

It is not possible to disable BI Publisher Reports Scheduling option

12425291 10604432 Connector

When reports are scheduled with an MLOV-enabled XMLP_RPT_SCHEDULE_MODE, all reports run immediately

11684153 10605466 Connector

It is not possible to upload multiple .xlf translation files.

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

13105473 Error Messages

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







Report name validation messages are not translated


The Job Name validation message is not translated within the Report Scheduler window


Siebel Server RemoteFile 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

10596340 10594120 DB Init

In certain cases, DB Xtract does not create a required records in s_node_pref

10578939 10574894 DBxtract

Allows the client executable KIT for patch deployment to be created on the Siebel application when it is running on the UNIX platform

13003564 12757714 Other Yes, see “Instructions for Bug 13003564” on page 145.

Within DB Server Configuration screens, there are buttons with no strings

10568170 10555174 Other

Transaction Processor does not delete EIM DX files

12937222 10499137 Txn Processor

Database performance degradation occurs when queries use S_DOCK_TXN_SET

12553093 Txn Processor

On the MSSQL database, the TxnProc component fails with an error message

12369618 10578784 Txn Processor






Siebel Travel & TransportationAvailability 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

12906967 13090315

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

12955227 13090315

The Function Space Diary view does not display correctly with Time Scale as "Month/Day-of-Week Part" and "Week/Day/Day Part"

12876544 13090315

Users are not able to set up modified icons in Function Space Diary

12876539 13090315

The Diary functionality fails when users query for a specific date

12857901

Error Message

When users drag and drop over an existing booking, they receive an error message

13419996






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

13415909 13415880

When users attempt to cancel a function, they receive an error message

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

12312702

Within Event Order > Function, the Add button does not perform as expected

12756997

When users click the Split Check button, they receive an error message

12807436

Other

ACR 575: Provides enhancements to the Diary functionality







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

12970701 13090315

Within the Quote > Timeshift Summary view, when users select the Accept Shifted/Reject Shifted menu option, room blocks are not accepted or rejected

13367536

Inline changes to Arrival Date information for a quote do not change a meeting package's Start Date information

12913708 13090315

When users create a quote from an opportunity, a full table scan is performed on the S_OPTY table, which causes performance issues

12733277

Reapplying packages also recreates the functions

13028585 13090315

Reports - Hospitality

Within Account Profile reports, the Account Discount field only recognizes integers

10603524 10603523






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.

Instructions for Bug 13003564CAUTION: 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:

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

... ...

2 In Siebel Tools, lock the following projects:

❏ Symbolic Strings

❏ Software Upgrade

3 Within Object Explorer > Screen, search for Siebel Anywhere Administration Screen.

The $ symbol does not display for the Rate field

10604999 10604146

Room Block

When users drill down from Quotes, the New button is disabled on Room Block line items

11932544

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

10603618 10603617






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

5 Within Object Explorer > Symbolic Strings, add a symbolic string with the following values:

6 Within Object Explorer > Applet, search for the Find Upgrade Kit Wizard applet.

7 Within Control, add a control with the following values:

8 Navigate to Applet Web Template, and search for "UpgKitWiz Exe Files".

9 From the right-click menu, select Edit Web Layouts, and drag the StartProgram control to the applet.

10 Navigate to System Administration > List of Values, and add a regentry LOV with the following values:

11 Add a CheckResult LOV with the following values:

NameCurrent String Value Project Type Translate

SBL_PATH_OF_FILE_TO_EXECUTE The path of the startup program

Symbolic Strings

Conversion true

Name Caption Caption Reference FieldHTML Type

StartupProgram The path of the startup program

SBL_PATH_OF_FILE_TO_EXECUTE Execute File Name

Field

Type Display Value

Language-Independent Code Order

UPG_KIT_ITEM_TYPE RebootRegEntry RebootRegEntry 8

Type Display Value


UPG_KIT_ITEM_TYPE CheckResult CheckResult 9



12 Add Siebel Quick Fix LOV with the following value:

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:

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

Type Display Value


UPG_KIT_TYPE Siebel Quick Fix Siebel Quick Fix 13

Item Type NameDefault Value Required Sequence

FileCopy Unarchive Folder N Unchecked 9

CheckResult File Name Checked 1

CheckResult Acceptable Return Code List

Unchecked 2

RebootRegEntry File Name Checked 1

RebootRegEntry Command Line Unchecked 2

RebootRegEntry Check Return Code

Y Unchecked 3

RebootRegEntry Return Code Unchecked 4

RebootRegEntry Is Script N Unchecked 5

FileExecute Is Script N Unchecked 13


Siebel Maintenance Release Guide, Version 8.1.1.7, Rev. B ■ Oracle Welcomes Your Comments

❏ Description: Used to distribute the Quick Fix

Instructions for Bug 12572213Bug 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 CommentsTo 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:

OracleSiebel Technical Publications Department500 Oracle ParkwayRedwood Shores, CA 94065

[email protected]

We appreciate your feedback.


Date post:	27-Oct-2014
Category:	Documents
Upload:	daniel-dobre
View:	386 times
Download:	3 times