MR Guide 811x Rev AA

Siebel Maintenance
Release Guide
Version 8.1.1.x, Rev.
AA
November 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 RIGHTS
Programs, software, databases, and related documentation and technical data delivered to U.S.
Government customers are "commercial computer software" or "commercial technical data" pursuant to
the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the
use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license
terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the
Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software
License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications, including
applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and
other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any
damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks
are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,
Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced
Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content,
products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third-party content, products, and services.
Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due
to your access to or use of third-party content, products, or services.
Release Notes for the Siebel 8.1.1.x Fix Pack 7
Whats New in This Revision 9
Quick Fixes Included in Siebel 8.1.1.x Fix Packs 10
Enhancements and Updates in 8.1.1.x Fix Packs 32
Enhancements and Updates in Version 8.1.1.4 33
Configuration Instructions for Enhancements and Updates 44
Instructions for ACR 358 45
Instructions for ACR 439B 96
Instructions for ACR 474 and ACR 508 169
Contents

Instructions for BI Publisher Enhancements 466
Siebel Fix Pack Installation Instructions 467
Siebel Fix Pack Installation Overview 467
Installing the Siebel Fix Pack on Microsoft Windows 471
Installing the Siebel Fix Pack on UNIX 476
Configuring Slipstream Patch Installation 480
Postinstallation Tasks for the Siebel Server 482
Postinstallation Tasks for the Web Server 482
Postinstallation Tasks for High Interactivity Clients 483
Postinstallation Tasks for Supporting Additional Languages 483
Uninstalling Siebel Fix Packs 485
Resolved Change Requests 487
. . . . . . . . . . . . . . Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack 488
Analytics 488
Call Center 488
Comm Media Energy 490
Connectors/EAI 490
Consumer Sector 492
Customer Order Management 495
Data Quality 500
General 502
Life Sciences 512
Loyalty 514
Marketing 516
Mobile Solutions 520
Partner Relationship Management 521
Public Sector 521
Sales 522
Service 522
Siebel E-Commerce for Comms 524
Siebel Self Service Common 524
Universal Customer Master 524
User Interface 529
Web Service 531
Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack 532
Call Center 532
Connectors/EAI 539
Consumer Sector 541
Data Quality 545
Financial Services 545
General 545
iHelp 560
Life Sciences 561
Loyalty 566
Marketing 567
Public Sector 571
Sales 571
Service 572
Siebel Email Response 573
Siebel Self Service eCommon 573
User Interface 573
Web Service 576
Call Center 577
Connectors/EAI 579
Consumer Sector 580
Data Quality 582
General 582
iHelp 593
Life Sciences 593
Marketing 594
Sales 597

Service 597
Siebel Self-Service Common 598
Travel & Transportation 598
User Interface 599
Web Service 601
Call Center 602
Connectors / EAI 605
Consumer Sector 606
Data Quality 624
Financial Services 625
General 626
Life Sciences 652
Loyalty 654
Marketing 658
Public Sector 664
Sales 664
Service 665
Siebel E-Commerce 666
Siebel E-Commerce for Comms 669
Siebel E-Support 683
Siebel Self Service Common 684
Travel & Transportation 686
Universal Customer Master 692
User Interface 695
Web Service 711
Oracle Welcomes Your Comments 777
Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 7
Siebel Maintenance Release
Guide, Version 8.1.1.x, Rev. AA
November 2012
NOTE: This guide documents the Quick Fixes, enhancements, instructions for enhancements, and
bugs fixed in the Siebel 8.1.1.1 through Siebel 8.1.1.4 Fix Packs. As of the Siebel 8.1.1.5 Fix Pack,
Fix Pack documentation is provided in a release-specific Siebel Maintenance Release Guide. 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.x Fix Pack on page 7
Whats New in This Revision on page 9
Quick Fixes Included in Siebel 8.1.1.x Fix Packs on page 10
Enhancements and Updates in 8.1.1.x Fix Packs on page 32
Configuration Instructions for Enhancements and Updates on page 44
Siebel Fix Pack Installation Instructions on page 467
Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack on page 488
Oracle Welcomes Your Comments on page 777
NOTE: If you are installing ACR 474, please note that there are known issues, which are documented
in this section. Also, for instructions about how to implement and configure ACR 474, see Siebel
Maintenance Release Guide, Version 8.1.1.x on My Oracle Support. To access this guide, from within
My Oracle Support, navigate to the Knowledge tab and search for Article ID 880452.1.
Release Notes for the Siebel 8.1.1.x Fix
Pack
The following sections describes known issues with the Siebel 8.1.1.x Fix Packs, as well as any
applicable workaround information.
Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA
Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA Release Notes for the
Siebel 8.1.1.x Fix Pack
8
No Records Display in Sample Compliance > Employee Based Tracking
> My Team's Employee View
Category: Siebel Life Sciences
Subcategory: Samples - Compliance
Product Version: Siebel 8.1.1.3
Bug ID: 12371899
All reporting employees should be displayed within Sample Compliance > Employee Based Tracking
> My Team's Employee view, but no records are displayed.
Use the following workaround to address this issue:
1 Log into Siebel Tools, and query for the LS Pharma Compliance Employee business component.
2 Select the Sales Rep business component view mode.
3 Change the Visibility MVLink property from Sales Team to Position
4 Change the Visibility MVField property from Sales Team to Position.
5 Compile the object into the SRF and restart the server.
LS Pharma Data Migration Service Returns Error
Category: Siebel Life Sciences
Subcategory: Samples
Product Version: Siebel 8.1.1.x
Bug ID: 10556780
When users create a server job using the Worfklow Process Manager component to run the LS
Pharma Data Migration for Life Sciences Pharma version 8.1.1, the process terminates with an error.
This issue applies to customers who are upgrading from Siebel Life Sciences customers who are
upgrading to Siebel 8.1.1.x from Siebel 8.0 or prior versions.
For workaround information, from within My Oracle Support, navigate to the Knowledge tab and
search for Article ID 1310515.1.
Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA Whats New in This
Revision
Whats New in This Revision
Table 1 describes the changes in this version of the documentation.
How To Use This Guide
This document, Siebel Maintenance Release Guide, Version 8.1.1.x, lists the enhancements and fixes
provided in the Siebel 8.1.1.1 through Siebel 8.1.1.4 Fix Packs.
This guide also provides information, instructions, and guidelines for installing Siebel Business
Applications Siebel Fix Pack 8.1.1.x releases on top of version 8.1.1 or a prior 8.1.1.x release.
Use this Siebel Maintenance Release Guide in conjunction with Siebel Bookshelf documents,
particularly the Siebel Installation Guide for the operating system you are using.
NOTE: Verify the availability and applicability of all Fix Pack or Quick Fix releases with Oracle Global
Customer Support before you install.
The information contained herein supersedes, for warranty and other purposes, the contents of all
other documentation that may accompany this product, including the following:
My Oracle Support (https://support.oracle.com)
Siebel System Requirements and Supported Platforms on Oracle Technology Network
(http://download.oracle.com/docs/cd/E11886_01/srsphomepage.html)
This Siebel Maintenance Release Guide contains information about the following:
How to install the maintenance (Fix Pack) release
Product configuration issues and workarounds for your application
NOTE: There may be references to functionality, products, platforms, and language support in this
document that are not available as part of the products that your organization has licensed. Consult
Oracle Global Customer Support on My Oracle Support with questions regarding the applicability of
Siebel Maintenance Release Guide items to your deployment.
Additional Documentation
Oracle reserves the right to modify the documentation for Siebel Business Applications at any time.
Table 1. Whats New in Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA
Topic Description
Instructions for ACR 474 and ACR 508 on
page 169
Revised this section.
Resolved Change Requests in the Siebel
8.1.1.4 Fix Pack on page 488
Added FR 12-1ZM2V2V and configuration
instructions for it.
Instructions for ACR 574 on page 457 Added tips under the Installing ACR 574 heading.
Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA Quick Fixes Included in
Siebel 8.1.1.x Fix Packs
10
For related Siebel documentation, see the following:
My Oracle Support (https://support.oracle.com) (requires valid customer account)
Siebel System Requirements and Supported Platforms on Oracle Technology Network (http://
download.oracle.com/docs/cd/E11886_01/srsphomepage.html)
Siebel Bookshelf for Oracles Siebel Business Applications, Version 8.1 (http://www.oracle.com/
technology/documentation/siebel.html) on Oracle Technology Network (OTN)
Quick Fixes Included in Siebel 8.1.1.x
Fix Packs
Siebel Quick Fix releases are developed to address immediate critical issues for specific customers,
and can be installed on top of Fix Packs. Quick Fixes address a small number of defects, and the fixes
are typically rolled into the next available Fix Pack for wider distribution to the Siebel Business
Applications customer base. Testing for Quick Fixes is focused and is usually limited to verifying that
the fix works on the specific platforms that the affected customer is running.
NOTE: If you have installed a Quick Fix for any Siebel 8.1.1 or 8.1.1.x release prior to the latest
8.1.1.x release covered by this document, review Table 2 on page 11 to make sure that your Quick
Fix number is listed.
CAUTION: If you do not see your Quick Fix number in the table, do not install the latest 8.1.1.x Fix
Pack. This list is updated as new Fix Packs are released. Wait until your Quick Fix appears in the table
before applying the latest Fix Pack. If you have questions, contact Global Customer Support or your
Oracle representative.
Table 2. Quick Fixes Included in Version 8.1.1.x
Change
Request ID/
Base Bug ID
Fix Request
ID/Bug ID Fix Pack Base
Quick Fix
Version
Merged Into
Fix Pack
12-1Q35A8A 12-1Q450JI [21107] 21107 8.1.1.4
12-1QVMO57 12-1QVMO5T [21112] 21112 8.1.1.4
12-1TK3VGV 12-1TK3VI7 8.1.1 [21112] QF0028 8.1.1.4
12-1TK4OZF 12-1TK4P0Q 8.1.1 [21112] QF0028 8.1.1.4
12-1TK9B70 12-1TK92RX 8.1.1 [21112] QF0028 8.1.1.4
12-1TKA4KE 12-1TKA4MZ 8.1.1 [21112] QF0028 8.1.1.4
12-1TPS15R 12-1TPS17B 8.1.1 [21112] QF0028 8.1.1.4
12-1TPS1BB 12-1TPS1CY 8.1.1 [21112] QF0028 8.1.1.4
12-1TPS1E1 12-1TPS1FI 8.1.1 [21112] QF0028 8.1.1.4
12-1TWTQPT 12-1TWTQR5 8.1.1 [21112] QF0028 8.1.1.4
12-1VH3RYD 12-1VI2I3J 8.1.1 [21112] QF0072 8.1.1.4
12-1VM6N5D 12-1VR58XF 8.1.1 [21112] QF0082 8.1.1.4
12-1WXWUIF 12-1WXWUIX 8.1.1 [21112] QF00AN 8.1.1.4
12-1QVMO57 12-1VHKVBD 8.1.1 [21112] QF00AO 8.1.1.4
12-1XZBSUD 12-1Y8IY97 8.1.1 [21112] QF00AV 8.1.1.4
12-1XO6UN9 12-1XOO9FM 8.1.1 [21112] QF00AW 8.1.1.4
12-1XUY3ZF 12-1XVFKIP 8.1.1 [21112] QF00AW 8.1.1.4
12-1VI06I9 12-1YFC5GX 8.1.1 [21112] QF00AY 8.1.1.4
12-1IBE8WR 12-1YM4XDT 8.1.1 [21112] QF00BD 8.1.1.4
12-1WLTVBV 12-1YMLXLT 8.1.1 [21112] QF00BG 8.1.1.4
12-1XF0G9H 12-1XMQKEZ 8.1.1 [21112] QF00BK 8.1.1.4
12-1YOMS98 12-1YOMSBW 8.1.1 [21112] QF00BO 8.1.1.4
12-1PZ4R7R 12-1XTIC0H 8.1.1 [21112] QF00BP 8.1.1.4
12-1YCG2PL 12-1Z6WBPB 8.1.1 [21112] QF00BU 8.1.1.4
12-1TGO7DJ 12-1U0BPJM 8.1.1 [21112] QF0028 8.1.1.4
12
12-1TJMH71 12-1TJMH8L 8.1.1 [21112] QF0028 8.1.1.4
12-1TK3VIM 12-1TK3VJY 8.1.1 [21112] QF0028 8.1.1.4
12-1TK3VKD 12-1TK4OX9 8.1.1 [21112] QF0028 8.1.1.4
12-1TK4OXO 12-1TK4OZ0 8.1.1 [21112] QF0028 8.1.1.4
12-1TK962G 12-1TK964K 8.1.1 [21112] QF0028 8.1.1.4
12-1TK9B1B 12-1TK92TB 8.1.1 [21112] QF0028 8.1.1.4
12-1TK9ENW 12-1TK9EP6 8.1.1 [21112] QF0028 8.1.1.4
12-1TK9ZE3 12-1TK9ZFM 8.1.1 [21112] QF0028 8.1.1.4
12-1TKA445 12-1TKA45M 8.1.1 [21112] QF0028 8.1.1.4
12-1TKA4GE 12-1TKA4J7 8.1.1 [21112] QF0028 8.1.1.4
12-1TKA4NA 12-1TK9ZGP 8.1.1 [21112] QF0028 8.1.1.4
12-1TKA9BK 12-1TKA9D4 8.1.1 [21112] QF0028 8.1.1.4
12-1TPS192 12-1TPS1B0 8.1.1 [21112] QF0028 8.1.1.4
12-1TPS1HM 12-1TKA9AH 8.1.1 [21112] QF0028 8.1.1.4
12-1TUW8FW 12-1TUW8HC 8.1.1 [21112] QF0028 8.1.1.4
12-1TUW8IF 12-1TUW8JX 8.1.1 [21112] QF0028 8.1.1.4
12-1TUWQ23 12-1TUW8ET 8.1.1 [21112] QF0028 8.1.1.4
12-1TWTQRK 12-1TWTQSU 8.1.1 [21112] QF0028 8.1.1.4
12-1U0AEGZ 12-1U0AEIY 8.1.1 [21112] QF0028 8.1.1.4
12-1U0AR67 12-1U0AR7L 8.1.1 [21112] QF0028 8.1.1.4
12-1U5RB3V 12-1U5RB5J 8.1.1 [21112] QF0041 8.1.1.4
12-1VH3RP7 12-1VH3X9H 8.1.1 [21112] QF0072 8.1.1.4
12-1VM7S6L 12-1VM7S7C 8.1.1 [21112] QF0075 8.1.1.4
12-1VM6MO5 12-1VM6040 8.1.1 [21112] QF00AH 8.1.1.4
12-1XHDRIJ 12-1XHX6IZ 8.1.1 [21112] QF00AI 8.1.1.4
12-1XIVKJJ 12-1XIVKK8 8.1.1 [21112] QF00AJ 8.1.1.4
12-1XLAL2N 12-1XP58OF 8.1.1 [21112] QF00AJ 8.1.1.4
12-1XHF9F1 12-1XKSPM0 8.1.1 [21112] QF00AM 8.1.1.4
12-1XP5AVL 12-1XQM2DJ 8.1.1 [21112] QF00AQ 8.1.1.4
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
12-1XCM26P 12-1XCM27D 8.1.1 [21112] QF00AR 8.1.1.4
12-1WF6ZG1 12-1WR5BMI 8.1.1 [21112] QF00AS 8.1.1.4
12-1Y6LBZN 12-1Y6LC0G 8.1.1 [21112] QF00AT 8.1.1.4
12-1VMCEBF 12-1VNJREX 8.1.1 [21112] QF00AW 8.1.1.4
12-1XT16PO 12-1XT16QR 8.1.1 [21112] QF00AW 8.1.1.4
12-1YIQQID 12-1YIQKSC 8.1.1 [21112] QF00AZ 8.1.1.4
12-1XWIYRL 12-1YCXRIV 8.1.1 [21112] QF00BA 8.1.1.4
12-1VDPBPF 12-1Y54A1B 8.1.1 [21112] QF00BF 8.1.1.4
12-1Z4YJPX 12-1Z4YJQJ 8.1.1 [21112] QF00BI 8.1.1.4
12-1XWEWDL 12-1XYCRU9 8.1.1 [21112] QF00BK 8.1.1.4
12-1YKOYUX 12-1YM4UWN 8.1.1 [21112] QF00BK 8.1.1.4
12-1XF0GC9 12-1XL4MPA 8.1.1 [21112] QF00BL 8.1.1.4
12-1WUJE2X 12-1WUJE3Y 8.1.1 [21112] QF00BR 8.1.1.4
12-1ZPH4ZU 12-1ZRVWP8 8.1.1 [21112] QF00BU 8.1.1.4
12-1YOKK4N 12-1Z7V33V 8.1.1 PDA [21112_10] 8.1.1 PDA
[21112_10]
8.1.1.4
12-1YOKGG5 12-1Z04TF7 8.1.1 PDA [21112_11] 8.1.1 PDA
[21112_11]
8.1.1.4
12-1YOK96H 12-1YOK97J 8.1.1 PDA [21112_8] 8.1.1 PDA
[21112_8]
8.1.1.4
12-1YOKK66 12-1YOKK9R 8.1.1 PDA [21112_8] 8.1.1 PDA
[21112_8]
8.1.1.4
12-1YOMS7P 12-1YOMS8H 8.1.1 PDA [21112_9] 8.1.1 PDA
[21112_9]
8.1.1.4
12-1JFQEZ6 12-1Z9RYA5 8.1.1 PDA [21112_9] 8.1.1 PDA
[21112_9]
8.1.1.4
12-1YGT6Q9 12-1YOMSAP 8.1.1 PDA [21112_9] 8.1.1 PDA
[21112_9]
8.1.1.4
12-1Z3IMD9 12-1Z3I799 8.1.1 PDA [21112_9] 8.1.1 PDA
[21112_9]
8.1.1.4
12-1TK4UBL 12-1XS216R 8.1.1.1 [21211] QF0191 8.1.1.4
12-1S1Y205 12-1X6RYEB 8.1.1.1 [21211] QF0192 8.1.1.4
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
14
12-1VH3RP7 12-1Y5LUYL 8.1.1.1 [21211] QF01AD 8.1.1.4
12-1XC7KQR 12-1YJP6YH 8.1.1.1 [21211] QF01AH 8.1.1.4
12-1PFQSZV 12-1YJPUAJ 8.1.1.1 [21211] QF01AN 8.1.1.4
12-1Y9HK6T 12-1YIQPLL 8.1.1.1 [21211] QF01AS 8.1.1.4
12-1YIQP2P 12-1YIQP3X 8.1.1.1 [21211] QF01AY 8.1.1.4
12-1Z1KQM1 12-1ZFBVG7 8.1.1.1 [21211] QF01BF 8.1.1.4
12-1YNLB8N 12-1YO2D6J 8.1.1.1 [21211] QF01BH 8.1.1.4
12-OVT1LK 12-1XJDH9J 8.1.1.1 [21211] QF01BK 8.1.1.4
12-1BDKMON 12-1YOLF2T 8.1.1.1 [21211] QF1109 8.1.1.4
12-1VNJDR2 12-1VNJDUK 8.1.1.1 [21211] QF3102 8.1.1.4
12-1VR4QM7 12-1VR4QMW 8.1.1.1 [21211] QF3103 8.1.1.4
12-1Z6VRAB 12-1Z4YK31 8.1.1.1 [21211] QF7106 8.1.1.4
12-1VM6N5D 12-1VM90VR 8.1.1.1 [21211] QF0131 8.1.1.4
12-1VM7S6L 12-1VR2KHF 8.1.1.1 [21211] QF0132 8.1.1.4
12-1WEU3RJ 12-1WFJXIH 8.1.1.1 [21211] QF0179 8.1.1.4
12-1X5627A 12-1X5628Q 8.1.1.1 [21211] QF0180 8.1.1.4
12-1U5RB3V 12-1U5RB56 8.1.1.1 [21211] QF0185 8.1.1.4
12-1U0C8HX 12-1XQLOAP 8.1.1.1 [21211] QF0187 8.1.1.4
12-1WF6IYP 12-1WF6SRH 8.1.1.1 [21211] QF0194 8.1.1.4
12-1Y0AHAJ 12-1Y0B0CN 8.1.1.1 [21211] QF0196 8.1.1.4
12-1XCM26P 12-1Y8ID43 8.1.1.1 [21211] QF0197 8.1.1.4
12-1WXWV2P 12-1XZBJGV 8.1.1.1 [21211] QF0198 8.1.1.4
12-1Y63UOX 12-1Y63KCJ 8.1.1.1 [21211] QF0199 8.1.1.4
12-1XF0FUR 12-1Y37HAT 8.1.1.1 [21211] QF01AA 8.1.1.4
12-1KBLS9L 12-1XHF8MP 8.1.1.1 [21211] QF01AC 8.1.1.4
12-1V418JR 12-1XSKD01 8.1.1.1 [21211] QF01AD 8.1.1.4
12-1UH8JVF 12-1YFCJ1B 8.1.1.1 [21211] QF01AE 8.1.1.4
12-1XLALJV 12-1XPMVCR 8.1.1.1 [21211] QF01AG 8.1.1.4
12-1VE77T9 12-1YCX4WP 8.1.1.1 [21211] QF01AI 8.1.1.4
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
12-1Y3OYE1 12-1Y5MADB 8.1.1.1 [21211] QF01AM 8.1.1.4
12-1BV2Y2P 12-1Y6LKPJ 8.1.1.1 [21211] QF01AO 8.1.1.4
12-1WLUTXP 12-1XHF5O1 8.1.1.1 [21211] QF01AP 8.1.1.4
12-1J1ZOUE 12-1YDESND 8.1.1.1 [21211] QF01AQ 8.1.1.4
12-1TLCZVH 12-1Z04WCR 8.1.1.1 [21211] QF01AV 8.1.1.4
12-1YQ37AZ 12-1YOMUG9 8.1.1.1 [21211] QF01AX 8.1.1.4
12-1W6DOUA 12-1WXF8N2 8.1.1.1 [21211] QF01BA 8.1.1.4
12-1XQ4S1X 12-1Z3IAW7 8.1.1.1 [21211] QF01BB 8.1.1.4
12-1XC7L43 12-1XC7L4O 8.1.1.1 [21211] QF01BC 8.1.1.4
12-1YOKFU7 12-1YOKNFT 8.1.1.1 [21211] QF01BC 8.1.1.4
12-1XTIR2L 12-1Z04WDL 8.1.1.1 [21211] QF01BF 8.1.1.4
12-1Y28AMJ 12-1Z04UJ7 8.1.1.1 [21211] QF01BF 8.1.1.4
12-1YOLRSL 12-1YOM3YD 8.1.1.1 [21211] QF01BG 8.1.1.4
12-1YOLS7V 12-1YOMC6N 8.1.1.1 [21211] QF01BI 8.1.1.4
12-1WXWUIF 12-1Y90L0B 8.1.1.1 [21211] QF01BO 8.1.1.4
12-1XIVYP9 12-1ZSUWJJ 8.1.1.1 [21211] QF01BU 8.1.1.4
12-1WF6ZG1 12-206EOPP 8.1.1.1 [21211] QF01CE 8.1.1.4
12-1XM98B7 12-1XQ4PLV 8.1.1.1 [21211] QF1107 8.1.1.4
12-1XTBN8V 12-1XTBN9M 8.1.1.1 [21211] QF1108 8.1.1.4
12-1TK672L 12-1VM54KD 8.1.1.1 [21211] QF3101 8.1.1.4
12-1VH3RP7 12-1VM7VPD 8.1.1.1 [21211] QF3101 8.1.1.4
12-1VH3RYD 12-1VM7VQC 8.1.1.1 [21211] QF3101 8.1.1.4
12-1VNJ8G2 12-1VNJ8HJ 8.1.1.1 [21211] QF3101 8.1.1.4
12-1VNJ8DR 12-1VNJ8F6 8.1.1.1 [21211] QF3102 8.1.1.4
12-1VNJC3T 12-1VNJC4I 8.1.1.1 [21211] QF3102 8.1.1.4
12-1VNJKCG 12-1VNIZ0Z 8.1.1.1 [21211] QF3103 8.1.1.4
12-1VNKG5Z 12-1VNKG7I 8.1.1.1 [21211] QF3103 8.1.1.4
12-1VR1NO3 12-1VR1NPM 8.1.1.1 [21211] QF3103 8.1.1.4
12-1VR2BBP 12-1VR38XI 8.1.1.1 [21211] QF3103 8.1.1.4
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
16
12-1VR3RJX 12-1VR3RLH 8.1.1.1 [21211] QF3103 8.1.1.4
12-1VR3SGC 12-1VR3SIF 8.1.1.1 [21211] QF3103 8.1.1.4
12-1VR4QK5 12-1VR4QL4 8.1.1.1 [21211] QF3103 8.1.1.4
12-1VR4VCC 12-1VR4VE1 8.1.1.1 [21211] QF3103 8.1.1.4
12-1VR4VUQ 12-1VR4VW7 8.1.1.1 [21211] QF3103 8.1.1.4
12-1X56AT7 12-1X660OB 8.1.1.1 [21211] QF3104 8.1.1.4
12-1Z6ER6J 12-1Z7UTG8 8.1.1.1 [21211] QF3106 8.1.1.4
12-1XWEYTD 12-1XWEYU7 8.1.1.1 [21211] QF4103 8.1.1.4
12-1WUJGPN 12-1YCFW5J 8.1.1.1 [21211] QF5105 8.1.1.4
12-1Q7NVMV 12-1XJD1PB 8.1.1.1 [21211] QF7104 8.1.1.4
12-1V4JH1X 12-1YL5W2L 8.1.1.1 [21211] QF7105 8.1.1.4
12-1XTIRJJ 12-1XWEU4W 8.1.1.1 [21211] QF7106 8.1.1.4
12-1S1Y205 12-1YFTTGZ 8.1.1.2 [ 21215] QF0264 8.1.1.4
12-1VR32TN 12-1VR32VC 8.1.1.2 [21215] QF0201 8.1.1.4
12-1IKIU3B 12-1XLRN7L 8.1.1.2 [21215] QF0229 8.1.1.4
12-1XIVLVL 12-1XJD2N6 8.1.1.2 [21215] QF0236 8.1.1.4
12-1WXWV2P 12-1X3PWGR 8.1.1.2 [21215] QF0237 8.1.1.4
12-1V418VF 12-1XF0ZKU 8.1.1.2 [21215] QF0242 8.1.1.4
12-1X65YA7 12-1XF0ZCF 8.1.1.2 [21215] QF0243 8.1.1.4
12-1XIVYP9 12-1XKTAIF 8.1.1.2 [21215] QF0244 8.1.1.4
12-1W7XG6V 12-1WA3IG1 8.1.1.2 [21215] QF0245 8.1.1.4
12-1XC4GYV 12-1XC4UGA 8.1.1.2 [21215] QF0247 8.1.1.4
12-1R4A19T 12-1XVG8MP 8.1.1.2 [21215] QF0248 8.1.1.4
12-1VNK8MB 12-1XF0ZM4 8.1.1.2 [21215] QF0249 8.1.1.4
12-1XZBSUD 12-1XZXNT7 8.1.1.2 [21215] QF0250 8.1.1.4
12-1XC7KQR 12-1XFILLH 8.1.1.2 [21215] QF0252 8.1.1.4
12-1Y3OXVF 12-1Y54EHL 8.1.1.2 [21215] QF0252 8.1.1.4
12-1WQ5PD9 12-1Y9R4SN 8.1.1.2 [21215] QF0256 8.1.1.4
12-1HE1XTL 12-1XIW0S1 8.1.1.2 [21215] QF0258 8.1.1.4
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
12-1VR26EP 12-1YK6TPN 8.1.1.2 [21215] QF0259 8.1.1.4
12-1XM987B 12-1XQ4AG0 8.1.1.2 [21215] QF0261 8.1.1.4
12-1Y3OY73 12-1Y5M9YK 8.1.1.2 [21215] QF0263 8.1.1.4
12-1QPSYL1 12-1XVG5E1 8.1.1.2 [21215] QF0266 8.1.1.4
12-1X3PQB1 12-1X3P5C7 8.1.1.2 [21215] QF0268 8.1.1.4
12-1XSJG29 12-1XSYA2D 8.1.1.2 [21215] QF0269 8.1.1.4
12-1YCXQYB 12-1YDWOIW 8.1.1.2 [21215] QF0270 8.1.1.4
12-1YNKWFD 12-1YO29DX 8.1.1.2 [21215] QF0272 8.1.1.4
12-1VM7S6L 12-1YNL9FN 8.1.1.2 [21215] QF0274 8.1.1.4
12-1YOLRNV 12-1YOLGB9 8.1.1.2 [21215] QF0275 8.1.1.4
12-1XF0GC9 12-1YN3T0B 8.1.1.2 [21215] QF0276 8.1.1.4
12-1YOMS98 12-1YSM0JM 8.1.1.2 [21215] QF0277 8.1.1.4
12-1XIVLOD 12-1XJDJVF 8.1.1.2 [21215] QF0279 8.1.1.4
12-1XM986H 12-1XQ4AF7 8.1.1.2 [21215] QF0280 8.1.1.4
12-1YM4GZ9 12-1YM4H07 8.1.1.2 [21215] QF0281 8.1.1.4
12-1YOMJWJ 12-1YSN3X1 8.1.1.2 [21215] QF0281 8.1.1.4
12-1YOMN57 12-1YSN3WN 8.1.1.2 [21215] QF0281 8.1.1.4
12-1YOMN72 12-1YSN3W9 8.1.1.2 [21215] QF0281 8.1.1.4
12-1YQGG4M 12-1YSN3VH 8.1.1.2 [21215] QF0281 8.1.1.4
12-1YQGG7U 12-1YOMPJT 8.1.1.2 [21215] QF0281 8.1.1.4
12-1YQGG9F 12-1YOMPJF 8.1.1.2 [21215] QF0281 8.1.1.4
12-1YQGGD5 12-1YOMPIN 8.1.1.2 [21215] QF0281 8.1.1.4
12-1YQGGEQ 12-1YOMPI9 8.1.1.2 [21215] QF0281 8.1.1.4
12-1YQZ267 12-1YQZ29Q 8.1.1.2 [21215] QF0281 8.1.1.4
12-1SW8L6P 12-1Y2PUMT 8.1.1.2 [21215] QF0282 8.1.1.4
12-1Y6LBZN 12-1YR2YWB 8.1.1.2 [21215] QF0282 8.1.1.4
12-1Y28AMJ 12-1Y28AN4 8.1.1.2 [21215] QF0283 8.1.1.4
12-1YAH50J 12-1YBWTK1 8.1.1.2 [21215] QF0283 8.1.1.4
12-1YAH4TL 12-1YBWHO9 8.1.1.2 [21215] QF0284 8.1.1.4
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
18
12-1VNJ7BV 12-1VNJBI3 8.1.1.2 [21215] QF0285 8.1.1.4
12-1XF0FX9 12-1YUNVWZ 8.1.1.2 [21215] QF0286 8.1.1.4
12-1YO2RKX 12-1YO2RLM 8.1.1.2 [21215] QF0287 8.1.1.4
12-1Z1KQY9 12-1Z3IALD 8.1.1.2 [21215] QF0288 8.1.1.4
12-1NWCZMB 12-1Y54DN1 8.1.1.2 [21215] QF0289 8.1.1.4
12-1YAH55T 12-1YCFIBF 8.1.1.2 [21215] QF0290 8.1.1.4
12-1VJZTJ7 12-1YOKQLH 8.1.1.2 [21215] QF0294 8.1.1.4
12-1QBCC09 12-1Z312WH 8.1.1.2 [21215] QF0296 8.1.1.4
12-1YOLS71 12-1YOMPKH 8.1.1.2 [21215] QF0298 8.1.1.4
12-1YZND55 12-1Z04EEK 8.1.1.2 [21215] QF0299 8.1.1.4
12-1Y3OXW9 12-1Y90EUX 8.1.1.2 [21215] QF02AB 8.1.1.4
12-1V9U49H 12-1Z0MDNB 8.1.1.2 [21215] QF02AC 8.1.1.4
12-1XRKKWD 12-1YAH25H 8.1.1.2 [21215] QF02AI 8.1.1.4
12-1YNLBB5 12-1Z7DTPM 8.1.1.2 [21215] QF02AI 8.1.1.4
12-1Z1KQM1 12-1ZF3CXL 8.1.1.2 [21215] QF02AI 8.1.1.4
12-1Z3IMBL 12-1ZOJCQH 8.1.1.2 [21215] QF02AI 8.1.1.4
12-1V418JR 12-1VOFQ3P 8.1.1.2 [21215] QF02AJ 8.1.1.4
12-1U0C8HX 12-1XM9N8Z 8.1.1.2 [21215] QF02AM 8.1.1.4
12-1TLCZVH 12-1Z9S46Z 8.1.1.2 [21215] QF02AN 8.1.1.4
12-1U5RB3V 12-203152F 8.1.1.2 [21215] QF02AN 8.1.1.4
12-1XIVMBZ 12-1XQ4T5X 8.1.1.2 [21215] QF02AQ 8.1.1.4
12-1Y9HK6T 12-1Y9HK8A 8.1.1.2 [21215] QF02AQ 8.1.1.4
12-1XBND23 12-1ZRW32R 8.1.1.2 [21215] QF02AR 8.1.1.4
12-1VMCEBF 12-1ZUS4MB 8.1.1.2 [21215] QF02AU 8.1.1.4
12-1SEPT2B 12-20F4VE5 8.1.1.2 [21215] QF02BK 8.1.1.4
12-1ZZMR15 12-202252X 8.1.1.2 [21215] QF02BL 8.1.1.4
12-1YGT6Q9 12-1YGT6R2 8.1.1.2 WM5 [21215_5] 8.1.1.2 WM 5
[21215_5]
8.1.1.4
12-1YOMS7P 12-1YV5IMZ 8.1.1.2 WM5 [21215_5] 8.1.1.2 WM 5
[21215_5]
8.1.1.4
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
12-1Z6VW9H 12-1Z6VWA6 8.1.1.2 WM5 [21215_6] 8.1.1.2 WM 5
[21215_6]
8.1.1.4
12-1JFQEZ6 12-1Y28CXL 8.1.1.2 WM5 [21215_5] 8.1.1.2 WM 5
[21215_5]
8.1.1.4
12-1Y2PC95 12-1YCFJSR 8.1.1.3 [21219] QF0302 8.1.1.4
12-1VMCEBF 12-1XYUAXZ 8.1.1.3 [21219] QF0303 8.1.1.4
12-1WTJXWZ 12-1X97V94 8.1.1.3 [21219] QF0303 8.1.1.4
12-1XF0G9H 12-1XMQKEJ 8.1.1.3 [21219] QF0303 8.1.1.4
12-1XOOC39 12-1XQ4AWP 8.1.1.3 [21219] QF0303 8.1.1.4
12-1HCLBH7 12-1XYTSLP 8.1.1.3 [21219] QF0304 8.1.1.4
12-1U0C8HX 12-1Z0MB07 8.1.1.3 [21219] QF0305 8.1.1.4
12-1QTP7PD 12-1Y2PBV7 8.1.1.3 [21219] QF0306 8.1.1.4
12-1Y0AZPB 12-1Y0AZPY 8.1.1.3 [21219] QF0307 8.1.1.4
12-1YOKG0B 12-1YOKNO0 8.1.1.3 [21219] QF0310 8.1.1.4
12-1VM7S6L 12-1Z4YJJT 8.1.1.3 [21219] QF0311 8.1.1.4
12-1Z1KQM1 12-1Z04V45 8.1.1.3 [21219] QF0312 8.1.1.4
12-1YFU2BX 12-1YHAEXR 8.1.1.3 [21219] QF0313 8.1.1.4
12-1YQ37K5 12-1YVB42D 8.1.1.3 [21219] QF0313 8.1.1.4
12-1Z6VRLF 12-1Z6WCOG 8.1.1.3 [21219] QF0314 8.1.1.4
12-1Z3IMBL 12-1Z6PEQ9 8.1.1.3 [21219] QF0315 8.1.1.4
12-1XTIRJJ 12-1ZF3T8Z 8.1.1.3 [21219] QF0316 8.1.1.4
12-1Q7NVMV 12-1ZFBE8H 8.1.1.3 [21219] QF0317 8.1.1.4
12-1IKIU3B 12-1ZH9OLB 8.1.1.3 [21219] QF0318 8.1.1.4
12-1X65YA7 12-1ZFCYUM 8.1.1.3 [21219] QF0319 8.1.1.4
12-1ZFBCAH 12-1ZFBJ5Z 8.1.1.3 [21219] QF0320 8.1.1.4
12-1V4JH1X 12-1ZF3AMP 8.1.1.3 [21219] QF0321 8.1.1.4
12-1W6DOUA 12-1ZD5YHL 8.1.1.3 [21219] QF0323 8.1.1.4
12-1Y8J0H7 12-1ZF38WH 8.1.1.3 [21219] QF0326 8.1.1.4
12-1YCFMMF 12-1YFCA4P 8.1.1.3 [21219] QF0328 8.1.1.4
12-1PZ4R7R 12-1ZURZZ3 8.1.1.3 [21219] QF0334 8.1.1.4
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
20
12-1XBND23 12-1ZY61E5 8.1.1.3 [21219] QF0336 8.1.1.4
12-OVT1LK 12-201KB2F 8.1.1.3 [21219] QF0337 8.1.1.4
12-1YOLS7V 12-1ZXOMPB 8.1.1.3 [21219] QF0341 8.1.1.4
12-1XTBN8V 12-1ZPH5PX 8.1.1.3 [21219] QF0342 8.1.1.4
12-1XIVMBZ 12-20MEJOF 8.1.1.3 [21219] QF0351 8.1.1.4
12-1VM6MO5 12-20IJAD1 8.1.1.3 [21219] QF0352 8.1.1.4
12-206F3XH 12-209BHN9 8.1.1.3 [21219] QF0355 8.1.1.4
12-1V418JR 12-1ZNIQFX 8.1.1.3 [21219] QF0357 8.1.1.4
12-1YCG2PL 12-20GLG4R 8.1.1.3 [21219] QF0357 8.1.1.4
12-1YOKK4N 12-1Z520FN 8.1.1.3 WM5 [21219_2] 8.1.1.3 WM5
[21219_2]
8.1.1.4
12-1VGM2U4 12-1Y641L8 Unspecified - 8.1.1.4
12-1VM72OT 12-1WLUTF3 7.7.2.2 [18356] QF7201 8.1.1.3
12-1U5SY53 12-1U5ULV5 8.1.1 [21112] QF0043 8.1.1.3
12-1UQ61Q1 12-1UQWPP0 8.1.1 [21112] QF0061 8.1.1.3
12-1V7WVM7 12-1V7WVNO 8.1.1 [21112] QF0062 8.1.1.3
12-1V0593H 12-1V3K66J 8.1.1 [21112] QF0068 8.1.1.3
12-1UH87LR 12-1UOUW8L 8.1.1 [21112] QF0080 8.1.1.3
12-1UJQNRZ 12-1UJQNTU 8.1.1 [21112] QF0080 8.1.1.3
12-1VH3RCZ 12-1VH3HYN 8.1.1 [21112] QF0080 8.1.1.3
12-1VKHEG7 12-1VKHEGV 8.1.1 [21112] QF0080 8.1.1.3
12-1UIB7XV 12-1UPTJSJ 8.1.1 [21112] QF0081 8.1.1.3
12-1V418GZ 12-1V418HK 8.1.1 [21112] QF0081 8.1.1.3
12-QND3G8 12-1VM7MNP 8.1.1 [21112] QF0083 8.1.1.3
12-1U5VI79 12-1VMAZDJ 8.1.1 [21112] QF0084 8.1.1.3
12-1VM8H57 12-1VM8H5Y 8.1.1 [21112] QF0085 8.1.1.3
12-1VR73HT 12-1VR73IR 8.1.1 [21112] QF0088 8.1.1.3
12-1VROIM3 12-1WE2T3K 8.1.1 [21112] QF0089 8.1.1.3
12-1U4NF3F 12-1WAL0Z9 8.1.1 [21112] QF0093 8.1.1.3
12-1VM6N4J 12-1WLTUS5 8.1.1 [21112] QF0095 8.1.1.3
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
12-1VMBL0Z 12-1WXXCZJ 8.1.1 [21112] QF0096 8.1.1.3
12-1WVI3Q5 12-1WV14UH 8.1.1 [21112] QF00AA 8.1.1.3
12-1VR5SGX 12-1VR7CDZ 8.1.1 [21112] QF00AB 8.1.1.3
12-1WF6FQC 12-1WLTV3T 8.1.1 [21112] QF00AC 8.1.1.3
12-1WF6P3J 12-1X56312 8.1.1 [21112] QF00AF 8.1.1.3
12-1VR4BZH 12-1XFIKC2 8.1.1 [21112] QF00AG 8.1.1.3
12-1X65TKV 12-1XS24V7 8.1.1 [21112] QF00AK 8.1.1.3
12-1VNIMYR 12-1XM9M42 8.1.1 [21112] QF00AO 8.1.1.3
12-1WXFOAB 12-1Y54TB7 8.1.1 [21112] QF00AU 8.1.1.3
12-1R3SHD7 12-1R3SHEV 8.1.1 [21112] QF1001 8.1.1.3
12-1UWODHL 12-1UWODIV 8.1.1 [21112] QF0059 8.1.1.3
12-1VHLD1H 12-1VJIBZ1 8.1.1 [21112] QF0078 8.1.1.3
12-1V41905 12-1V4190P 8.1.1 [21112] QF0079 8.1.1.3
12-1VCQAE7 12-1VABY2J 8.1.1 [21112] QF0080 8.1.1.3
12-1VMCEM9 12-1VNJB15 8.1.1 [21112] QF0082 8.1.1.3
12-1VM5K6V 12-1VM5OFZ 8.1.1 [21112] QF0086 8.1.1.3
12-1TK4DJP 12-1VR7XBB 8.1.1 [21112] QF0088 8.1.1.3
12-1NXS3RV 12-1VMB443 8.1.1 [21112] QF0090 8.1.1.3
12-1VCQVAZ 12-1VVFZX5 8.1.1 [21112] QF0091 8.1.1.3
12-1VMC9ID 12-1VMC9JC 8.1.1 [21112] QF0094 8.1.1.3
12-1VR43FP 12-1VR613R 8.1.1 [21112] QF0097 8.1.1.3
12-1WV0HS3 12-1WVIDDX 8.1.1 [21112] QF0098 8.1.1.3
12-1WXX8FJ 12-1WYEWC1 8.1.1 [21112] QF00AA 8.1.1.3
12-1SD8XW1 12-1XEBKOX 8.1.1 [21112] QF00AE 8.1.1.3
12-1T2IN2L 12-1U5RPCP 8.1.1 [21112] QF00AO 8.1.1.3
12-1U0AX75 12-1XM9M2R 8.1.1 [21112] QF00AO 8.1.1.3
12-1R3SHD7 12-1SCQC43 8.1.1 [21112] QF1001 8.1.1.3
12-1R3SHD7 12-1SSU185 8.1.1 [21112] QF1002 8.1.1.3
12-1VM6B55 12-1VM8H0R 8.1.1 [21112] QF1003 8.1.1.3
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
22
12-1LC1A2Z 12-1WF6BOH 8.1.1 [21112] QF0099 QF0099 8.1.1.3
12-1U5VI4H 12-1UH8O67 8.1.1 PDA [21112_1] 8.1.1 PDA
[21112_1]
8.1.1.3
12-1VR6T39 12-1VR6T42 8.1.1 PDA [21112_4] 8.1.1 PDA
_21112_4]
8.1.1.3
12-1VMBHFJ 12-1VMBHGE 8.1.1 PDA [21112_5] 8.1.1 PDA
[21112_5]
8.1.1.3
12-1VM6HI1 12-1WS4HGD 8.1.1 PDA [21112_6] 8.1.1 PDA
[21112_6]
8.1.1.3
12-1V418N3 12-1V7FOQ9 8.1.1.1 [21211] QF0114 8.1.1.3
12-1VH3RGB 12-1VKYYB5 8.1.1.1 [21211] QF0114 8.1.1.3
12-1UI8TH3 12-1UI8THP 8.1.1.1 [21211] QF0115 8.1.1.3
12-1RAJ0I1 12-1VGLLEK 8.1.1.1 [21211] QF0121 8.1.1.3
12-1VE7EH7 12-1VE6TJ6 8.1.1.1 [21211] QF0124 8.1.1.3
12-1U5V32T 12-1U7CGKP 8.1.1.1 [21211] QF0125 8.1.1.3
12-1VEOU89 12-1VI2IE9 8.1.1.1 [21211] QF0130 8.1.1.3
12-1UWODHL 12-1VR3IU1 8.1.1.1 [21211] QF0133 8.1.1.3
12-1VR2PWN 12-1VR3NJZ 8.1.1.1 [21211] QF0134 8.1.1.3
12-1HWWAY4 12-1VM5IIV 8.1.1.1 [21211] QF0139 8.1.1.3
12-1VR2PUZ 12-1VR3L6U 8.1.1.1 [21211] QF0141 8.1.1.3
12-1TXBDIV 12-1VTSQMV 8.1.1.1 [21211] QF0146 8.1.1.3
12-1WF6P3J 12-1WF6HIG 8.1.1.1 [21211] QF0153 8.1.1.3
12-1VR5ZGB 12-1VR4O99 8.1.1.1 [21211] QF0154 8.1.1.3
12-1PVZS4R 12-1VR5PTN 8.1.1.1 [21211] QF0155 8.1.1.3
12-1X3RF25 12-1X3RF2X 8.1.1.1 [21211] QF0156 8.1.1.3
12-1VNJ8NI 12-1VR29OR 8.1.1.1 [21211] QF0157 8.1.1.3
12-1WF5ZQH 12-1WF5ZRW 8.1.1.1 [21211] QF0157 8.1.1.3
12-1WA5CGZ 12-1WEE4FN 8.1.1.1 [21211] QF0158 8.1.1.3
12-1WF6G1R 12-1WF6G2Q 8.1.1.1 [21211] QF0158 8.1.1.3
12-1WLTLED 12-1WLTLEY 8.1.1.1 [21211] QF0159 8.1.1.3
12-1UGQKS5 12-1VR5ORB 8.1.1.1 [21211] QF0160 8.1.1.3
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
12-1WF6PMP 12-1WK5MQ5 8.1.1.1 [21211] QF0161 8.1.1.3
12-1W4M5R5 12-1WERWGT 8.1.1.1 [21211] QF0162 8.1.1.3
12-1VMCEHT 12-1VNJ4VP 8.1.1.1 [21211] QF0165 8.1.1.3
12-1QG70K8 12-1X1AK5N 8.1.1.1 [21211] QF0167 8.1.1.3
12-1WVIKB5 12-1WWYDEF 8.1.1.1 [21211] QF0169 8.1.1.3
12-1O2IS17 12-1X65R0B 8.1.1.1 [21211] QF0171 8.1.1.3
12-1WTJXYN 12-1WTJXZ8 8.1.1.1 [21211] QF0176 8.1.1.3
12-1VHLD1H 12-1YCG7H4 8.1.1.1 [21211] QF01AB 8.1.1.3
12-1VKHEG7 12-1YFTGHB 8.1.1.1 [21211] QF01AG 8.1.1.3
12-1TK6U03 12-1UIBBJV 8.1.1.1 [21211] QF1101 8.1.1.3
12-1UW5F8T 12-1UW5FA5 8.1.1.1 [21211] QF1102 8.1.1.3
12-1VM7OFB 12-1VM8AUM 8.1.1.1 [21211] QF1103 8.1.1.3
12-1VR2YCD 12-1VR2YD7 8.1.1.1 [21211] QF1104 8.1.1.3
12-1WA5CGZ 12-1WRAAA5 8.1.1.1 [21211] QF1105 8.1.1.3
12-1WF6G1R 12-1WRAAD1 8.1.1.1 [21211] QF1105 8.1.1.3
12-1X56KI9 12-1X56R61 8.1.1.1 [21211] QF1106 8.1.1.3
12-1VE7EQ3 12-1VG4DL9 8.1.1.1 [21211] QF2103 8.1.1.3
12-1UI8IN7 12-1VR7JA7 8.1.1.1 [21211] QF4101 8.1.1.3
12-1VNJJZ2 12-1VNKHLQ 8.1.1.1 [21211] QF4101 8.1.1.3
12-1VNJZ8L 12-1VNJUIQ 8.1.1.1 [21211] QF4101 8.1.1.3
12-1VR347X 12-1VR348W 8.1.1.1 [21211] QF4101 8.1.1.3
12-1VR398K 12-1VR399Z 8.1.1.1 [21211] QF4101 8.1.1.3
12-1VR4A7V 12-1VR4A8M 8.1.1.1 [21211] QF4101 8.1.1.3
12-1VR4FMB 12-1VR4FN2 8.1.1.1 [21211] QF4101 8.1.1.3
12-1VR6FWO 12-1VR60PC 8.1.1.1 [21211] QF4101 8.1.1.3
12-1UI8IN7 12-1WLTWCD 8.1.1.1 [21211] QF4102 8.1.1.3
12-1VR3957 12-1VR397S 8.1.1.1 [21211] QF4102 8.1.1.3
12-1WCP9WP 12-1WCP9XZ 8.1.1.1 [21211] QF4102 8.1.1.3
12-1WF73FF 12-1WF73IY 8.1.1.1 [21211] QF4102 8.1.1.3
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
24
12-1WFFM67 12-1WFFM6W 8.1.1.1 [21211] QF4102 8.1.1.3
12-1R3SHD7 12-1VR77JP 8.1.1.1 [21211] QF5101 8.1.1.3
12-1W6DOPP 12-1W6DOQT 8.1.1.1 [21211] QF6101 8.1.1.3
12-1TXBDIV 12-1WV0RNH 8.1.1.1 [21211] QF7101 8.1.1.3
12-1W6PXXB 12-1WV0ROK 8.1.1.1 [21211] QF7101 8.1.1.3
12-1WA5CGZ 12-1XWWVON 8.1.1.1 [21211] QF7103 8.1.1.3
12-1WF6G1R 12-1XWWVPV 8.1.1.1 [21211] QF7103 8.1.1.3
12-1X56KGX 12-1XWWVQT 8.1.1.1 [21211] QF7103 8.1.1.3
12-1X56KI9 12-1XWWVRR 8.1.1.1 [21211] QF7103 8.1.1.3
12-1VR46RP 12-1VR46SJ 8.1.1.1 [21211] QF0100 8.1.1.3
12-1REV4NL 12-1VDPAUL 8.1.1.1 [21211] QF0118 8.1.1.3
12-1SJ54EF 12-1VGLLFE 8.1.1.1 [21211] QF0121 8.1.1.3
12-1U5SY53 12-1VMAX0J 8.1.1.1 [21211] QF0126 8.1.1.3
12-1VNJ20P 12-1VR2KIF 8.1.1.1 [21211] QF0132 8.1.1.3
12-1VNJZD9 12-1VR3YPZ 8.1.1.1 [21211] QF0136 8.1.1.3
12-1VM81EJ 12-1VR3OK5 8.1.1.1 [21211] QF0137 8.1.1.3
12-1V418SN 12-1V418T8 8.1.1.1 [21211] QF0138 8.1.1.3
12-1VNKRB3 12-1VNKRC7 8.1.1.1 [21211] QF0140 8.1.1.3
12-1UJQNRZ 12-1VMCBXB 8.1.1.1 [21211] QF0143 8.1.1.3
12-1VROIM3 12-1VROIMY 8.1.1.1 [21211] QF0148 8.1.1.3
12-1V41905 12-1VR46VZ 8.1.1.1 [21211] QF0149 8.1.1.3
12-1VM6N0D 12-1VM6N0Y 8.1.1.1 [21211] QF0150 8.1.1.3
12-1T2II25 12-1WF6XDZ 8.1.1.1 [21211] QF0154 8.1.1.3
12-1QHN64C 12-1VM5JMC 8.1.1.1 [21211] QF0156 8.1.1.3
12-1VMAF2Z 12-1VMC0PF 8.1.1.1 [21211] QF0160 8.1.1.3
12-1W4M5S2 12-1WAWS42 8.1.1.1 [21211] QF0162 8.1.1.3
12-1RVO17F 12-1VR5GB0 8.1.1.1 [21211] QF0164 8.1.1.3
12-1VM83AX 12-1X5630E 8.1.1.1 [21211] QF0170 8.1.1.3
12-1VR66BT 12-1VR6WMR 8.1.1.1 [21211] QF0170 8.1.1.3
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
12-1VR4BZH 12-1WF6HRX 8.1.1.1 [21211] QF0172 8.1.1.3
12-1X3PRS9 12-1X3PRSZ 8.1.1.1 [21211] QF0173 8.1.1.3
12-1WXFOAB 12-1X1RZWH 8.1.1.1 [21211] QF0174 8.1.1.3
12-1UH87BR 12-1WF6V8X 8.1.1.1 [21211] QF0176 8.1.1.3
12-1XFIDB5 12-1XHFCTH 8.1.1.1 [21211] QF0176 8.1.1.3
12-1X65TKV 12-1XKSUW0 8.1.1.1 [21211] QF0181 8.1.1.3
12-1S9QMWN 12-1XPN62V 8.1.1.1 [21211] QF0186 8.1.1.3
12-1VM6N8P 12-1VM7TE6 8.1.1.1 [21211] QF0186 8.1.1.3
12-1LC1A2Z 12-1XVG87F 8.1.1.1 [21211] QF0188 8.1.1.3
12-1Q16OWB 12-1X4CYI9 8.1.1.1 [21211] QF0189 8.1.1.3
12-1VM72OT 12-1XP58ZT 8.1.1.1 [21211] QF0190 8.1.1.3
12-1VMAEXZ 12-1VMBEH5 8.1.1.1 [21211] QF0190 8.1.1.3
12-1UH87LR 12-1Y72ZUH 8.1.1.1 [21211] QF01AF 8.1.1.3
12-1VR2NH1 12-1VR2NII 8.1.1.1 [21211] QF1104 8.1.1.3
12-1TXBDIV 12-1WLTK5Q 8.1.1.1 [21211] QF1105 8.1.1.3
12-1UW5DFF 12-1UW5DGH 8.1.1.1 [21211] QF1105 8.1.1.3
12-1W6PXXB 12-1W6PXY5 8.1.1.1 [21211] QF1105 8.1.1.3
12-1X56155 12-1X56KGK 8.1.1.1 [21211] QF1106 8.1.1.3
12-1X56KGX 12-1X56KHX 8.1.1.1 [21211] QF1106 8.1.1.3
12-1X65TKV 12-1XVG99R 8.1.1.1 [21211] QF1107 8.1.1.3
12-1UH87BR 12-1VPNBHD 8.1.1.1 [21211] QF2103 8.1.1.3
12-1VMJW4R 12-1VNJUJS 8.1.1.1 [21211] QF4101 8.1.1.3
12-1VNJJXN 12-1VNKHMB 8.1.1.1 [21211] QF4101 8.1.1.3
12-1VNJZ9H 12-1VNJUHZ 8.1.1.1 [21211] QF4101 8.1.1.3
12-1VR3GUN 12-1VR4LB3 8.1.1.1 [21211] QF4101 8.1.1.3
12-1VR4V1B 12-1VR4V22 8.1.1.1 [21211] QF4101 8.1.1.3
12-1VR6QRN 12-1VR6QT2 8.1.1.1 [21211] QF4101 8.1.1.3
12-1WF77PG 12-1WF77Q5 8.1.1.1 [21211] QF4102 8.1.1.3
12-1VM6N4J 12-1XQ49XF 8.1.1.1 [21211] QF5105 8.1.1.3
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
26
12-1VR2NH1 12-1WIXZ3T 8.1.1.1 [21211] QF7101 8.1.1.3
12-1X0C24K 12-1X0C26K 8.1.1.1 [21211] QF7102 8.1.1.3
12-1X56155 12-1XYCA25 8.1.1.1 [21211] QF7103 8.1.1.3
12-1X65TKV 12-1XWWVSZ 8.1.1.1 [21211] QF7103 8.1.1.3
12-1XVXEFP 12-1XWET8K 8.1.1.1 [21211] QF7103 8.1.1.3
12-1KXYCJ7 12-1VGLLDP 8.1.1.1 [21211] QF0121 QF0121 8.1.1.3
12-1U089B9 12-1U089CS 8.1.1.1[21210]
QFACR474_DEV3 ENU
Don't think that
this s/b
8.1.1.3
12-1U0ATEW 12-1U0ATGA 8.1.1.1[21210]
QFACR474_DEV3 ENU
Don't think that
this s/b
8.1.1.3
12-1VM81EJ 12-1VMATZX 8.1.1.2 [21215] QF0201 8.1.1.3
12-1VR4BF7 12-1VR3P8V 8.1.1.2 [21215] QF0201 8.1.1.3
12-1UI7QYZ 12-1V14JRA 8.1.1.2 [21215] QF0202 8.1.1.3
12-1W7XG07 12-1WF75UB 8.1.1.2 [21215] QF0205 8.1.1.3
12-1U4NF3F 12-1VKHKCF 8.1.1.2 [21215] QF0206 8.1.1.3
12-1VR4BT3 12-1VR50U7 8.1.1.2 [21215] QF0207 8.1.1.3
12-1WF6PLV 12-1WHFPCJ 8.1.1.2 [21215] QF0207 8.1.1.3
12-1QG70K8 12-1VMBCSV 8.1.1.2 [21215] QF0208 8.1.1.3
12-1SJNUGJ 12-1WQ5VI3 8.1.1.2 [21215] QF0209 8.1.1.3
12-1VMAEXZ 12-1WLUFT3 8.1.1.2 [21215] QF0210 8.1.1.3
12-1DK2UO8 12-1WU19LH 8.1.1.2 [21215] QF0211 8.1.1.3
12-1U5V32T 12-1VR5ESF 8.1.1.2 [21215] QF0212 8.1.1.3
12-1QHN64C 12-1WYEYBP 8.1.1.2 [21215] QF0213 8.1.1.3
12-1JGY6HC 12-1WYWA9N 8.1.1.2 [21215] QF0216 8.1.1.3
12-1X6681L 12-1XCMB93 8.1.1.2 [21215] QF0216 8.1.1.3
12-1VR78HP 12-1VR7VHR 8.1.1.2 [21215] QF0217 8.1.1.3
12-1X1AZAL 12-1X65NWV 8.1.1.2 [21215] QF0218 8.1.1.3
12-1X3PH1V 12-1X4OYWX 8.1.1.2 [21215] QF0220 8.1.1.3
12-1VNKRB3 12-1X98CML 8.1.1.2 [21215] QF0221 8.1.1.3
12-1V418GZ 12-1WYEKN7 8.1.1.2 [21215] QF0222 8.1.1.3
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
12-1PPACL7 12-1VMB80D 8.1.1.2 [21215] QF0223 8.1.1.3
12-1VEOU89 12-1WF6MH3 8.1.1.2 [21215] QF0223 8.1.1.3
12-1WA5CGZ 12-1WEE4GH 8.1.1.2 [21215] QF0223 8.1.1.3
12-1WF6G1R 12-1WF7AUB 8.1.1.2 [21215] QF0223 8.1.1.3
12-1X65TKV 12-1X65TML 8.1.1.2 [21215] QF0223 8.1.1.3
12-1V418N3 12-1X1AS17 8.1.1.2 [21215] QF0225 8.1.1.3
12-1NSKPIL 12-1X8R0OX 8.1.1.2 [21215] QF0226 8.1.1.3
12-1S9QMWN 12-1VM55TX 8.1.1.2 [21215] QF0227 8.1.1.3
12-1STC0L5 12-1XHX1P1 8.1.1.2 [21215] QF0230 8.1.1.3
12-1UH87BR 12-1WXFIOE 8.1.1.2 [21215] QF0231 8.1.1.3
12-1XFIDB5 12-1XHFCUG 8.1.1.2 [21215] QF0231 8.1.1.3
12-1UJQNRZ 12-1X0SZC7 8.1.1.2 [21215] QF0232 8.1.1.3
12-1W4M5R5 12-1XC4U97 8.1.1.2 [21215] QF0232 8.1.1.3
12-1W4M5S2 12-1XC4UA1 8.1.1.2 [21215] QF0232 8.1.1.3
12-1XCM9RR 12-1XEJ0CQ 8.1.1.2 [21215] QF0233 8.1.1.3
12-1T2IN2L 12-1TK4R41 8.1.1.2 [21215] QF0238 8.1.1.3
12-1U0AX75 12-1VGLSEY 8.1.1.2 [21215] QF0238 8.1.1.3
12-1VNIMYR 12-1X663V7 8.1.1.2 [21215] QF0238 8.1.1.3
12-1X0BIZX 12-1X0BJ10 8.1.1.2 [21215] QF0239 8.1.1.3
12-1UH87LR 12-1WYVUF3 8.1.1.2 [21215] QF0240 8.1.1.3
12-1XC7L1L 12-1XC7L26 8.1.1.2 [21215] QF0241 8.1.1.3
12-1VMC9ID 12-1XT0PSF 8.1.1.2 [21215] QF0246 8.1.1.3
12-1VM7HW1 12-1XS1LZH 8.1.1.2 [21215] QF0251 8.1.1.3
12-1Q16OWB 12-1VMBP4R 8.1.1.2 [21215] QF0253 8.1.1.3
12-1VHLD1H 12-1Y2P00T 8.1.1.2 [21215] QF0254 8.1.1.3
12-1VMAF2Z 12-1YDEQQT 8.1.1.2 [21215] QF0256 8.1.1.3
12-1LC1A2Z 12-1Y54T99 8.1.1.2 [21215] QF0257 8.1.1.3
12-1VR43FP 12-1YK6TOR 8.1.1.2 [21215] QF0259 8.1.1.3
12-1V41SPV 12-1XEJIBF 8.1.1.2 [21215] QF1201 8.1.1.3
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
28
12-1VR4BVB 12-1VR5ATP 8.1.1.2 WM5 [21215_1] 8.1.1.2
[21215_1]
8.1.1.3
12-1V6XL7R 12-1V7WKHX 8.1.1.2 WM5 [21215_1] 8.1.1.2 WM5
[21215_1]
8.1.1.3
12-1VNJH0Z 12-1VNJH1R 8.1.1.2 WM5 [21215_1] 8.1.1.2 WM5
[21215_1]
8.1.1.3
12-1WCP7ZT 12-1WCP80M 8.1.1.2 WM5 [21215_1] 8.1.1.2 WM5
[21215_1]
8.1.1.3
12-1X1S03V 12-1X1GML7 8.1.1.2 WM5 [21215_2] 8.1.1.2 WM5
_21215_2]
8.1.1.3
12-1VNJY1R 12-1VR6P9H 8.1.1.2 WM5 [21215_3] 8.1.1.2 WM5
[21215_3]
8.1.1.3
12-1OOD149 12-1WQNMNT Unspecified ??? 8.1.1.3
12-1PBVORR 12-1SM2F17 8.1.1 [21112] QF0008 8.1.1.2
12-1SI5H61 12-1SI5H6M 8.1.1 [21112] QF0008 8.1.1.2
12-1TBLYYA 12-1TBLZ15 8.1.1 [21112] QF0015 8.1.1.2
12-1THO6OP 12-1TK476J 8.1.1 [21112] QF0016 8.1.1.2
12-1T7V4R7 12-1TBLYXR 8.1.1 [21112] QF0017 8.1.1.2
12-1TH5NV5 12-1THO2I5 8.1.1 [21112] QF0017 8.1.1.2
12-1SFPEAN 12-1TK3VLL 8.1.1 [21112] QF0019 8.1.1.2
12-1TGO4RF 12-1TI66LP 8.1.1 [21112] QF0021 8.1.1.2
12-1OQD0BB 12-1TK8U26 8.1.1 [21112] QF0023 8.1.1.2
12-1STC0UB 12-1TK5L5F 8.1.1 [21112] QF0023 8.1.1.2
12-1TK6LZT 12-1TK85H4 8.1.1 [21112] QF0023 8.1.1.2
12-1TD6X31 12-1TDOVOJ 8.1.1 [21112] QF0024 8.1.1.2
12-1L3YVPO 12-1T5WKPM 8.1.1 [21112] QF0025 8.1.1.2
12-1QBCC2R 12-1TA9KB1 8.1.1 [21112] QF0026 8.1.1.2
12-1SJ5MIZ 12-1TS8XK5 8.1.1 [21112] QF0026 8.1.1.2
12-1T2J5H3 12-1TARVI6 8.1.1 [21112] QF0026 8.1.1.2
12-1SBRAKT 12-1TTI5LX 8.1.1 [21112] QF0031 8.1.1.2
12-1TK4CEL 12-1TK9IXL 8.1.1 [21112] QF0031 8.1.1.2
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
12-1QMX8LP 12-1U0DDZT 8.1.1 [21112] QF0033 8.1.1.2
12-1U0BPQZ 12-1U0BPSO 8.1.1 [21112] QF0034 8.1.1.2
12-1T7DG8H 12-1T7DG98 8.1.1 [21112] QF0035 8.1.1.2
12-1RHR0N1 12-1TARVQH 8.1.1 [21112] QF0037 8.1.1.2
12-1R6NUCR 12-1TDO7P7 8.1.1 [21112] QF0040 8.1.1.2
12-1TUVZQ9 12-1TXBVH1 8.1.1 [21112] QF0041 8.1.1.2
12-1U5RB3V 12-1U5RB5J 8.1.1 [21112] QF0041 8.1.1.2
12-1UHPV6B 12-1UHPV78 8.1.1 [21112] QF0042 8.1.1.2
12-1TXC3RL 12-1TXT92X 8.1.1 [21112] QF0044 8.1.1.2
12-1U4I7KV 12-1U5RZSJ 8.1.1 [21112] QF0044 8.1.1.2
12-1TK9JCV 12-1U0AHDE 8.1.1 [21112] QF0045 8.1.1.2
12-1UI81Z5 12-1UI820R 8.1.1 [21112] QF0046 8.1.1.2
12-1ME9N7W 12-1U8SE0P 8.1.1 [21112] QF0048 8.1.1.2
12-1U0866H 12-1U09KKL 8.1.1 [21112] QF0048 8.1.1.2
12-1UI8T7X 12-1UFS6HJ 8.1.1 [21112] QF0048 8.1.1.2
12-IVNITD 12-1U5RJ4P 8.1.1 [21112] QF0048 8.1.1.2
12-OM5V6D 12-1TDOR8T 8.1.1 [21112] QF0048 8.1.1.2
12-1UIB7Z9 12-1UMPRTK 8.1.1 [21112] QF0049 8.1.1.2
12-1SSTZQV 12-1UJQL8W 8.1.1 [21112] QF0050 8.1.1.2
12-1UH87BR 12-1UH8JTX 8.1.1 [21112] QF0051 8.1.1.2
12-1KJP2WG 12-1UIA3SN 8.1.1 [21112] QF0053 8.1.1.2
12-1RRBFQ9 12-1UOWLB9 8.1.1 [21112] QF0054 8.1.1.2
12-1QPSY8J 12-1UIADXT 8.1.1 [21112] QF0055 8.1.1.2
12-1V0598R 12-1UZMXSH 8.1.1 [21112] QF0056 8.1.1.2
12-1SBRA31 12-1STC1G9 8.1.1 [21112] QF0058 8.1.1.2
12-1TGOA5B 12-1V41YTV 8.1.1 [21112] QF0060 8.1.1.2
12-1VH3J0H 12-1VH3J1D 8.1.1 [21112] QF0064 8.1.1.2
12-1UGQK67 12-1UG91VX 8.1.1 [21112] QF0065 8.1.1.2
12-1U8XCTD 12-1U8XCU7 8.1.1 [21112] QF0066 8.1.1.2
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
30
12-1T6DMLW 12-1VI33A5 8.1.1 [21112] QF0067 8.1.1.2
12-1UI8QNP 12-1VKHLAV 8.1.1 [21112] QF0068 8.1.1.2
12-1UU5KSH 12-1UX5VWV 8.1.1 [21112] QF0074 8.1.1.2
12-1RPD2ML 12-1VM83TH 8.1.1 [21112] QF0076 8.1.1.2
12-1OK0UBP 12-1VEOVOV 8.1.1 [21112] QF0081 8.1.1.2
12-1VM6N5D 12-1VR58XF 8.1.1 [21112] QF0082 8.1.1.2
12-1V6FY27 12-1V6FY31 8.1.1 PDA [21112_2] 8.1.1 PDA
[21112_2]
8.1.1.2
12-1SBRAKT 12-1UH8553 8.1.1.1 [21211] QF0101 8.1.1.2
12-1TGO4RF 12-1UI8E4P 8.1.1.1 [21211] QF0101 8.1.1.2
12-1OVCU5D 12-1UI8Y05 8.1.1.1 [21211] QF0103 8.1.1.2
12-1UQ62AL 12-1UX6LM3 8.1.1.1 [21211] QF0104 8.1.1.2
12-1TK9JCV 12-1UZ5U7X 8.1.1.1 [21211] QF0105 8.1.1.2
12-1THO6OP 12-1UX5DMT 8.1.1.1 [21211] QF0106 8.1.1.2
12-1UGQKML 12-1UI7VPC 8.1.1.1 [21211] QF0106 8.1.1.2
12-IVNITD 12-1UIBF3Z 8.1.1.1 [21211] QF0106 8.1.1.2
12-1TK4UOX 12-1U0F4EH 8.1.1.1 [21211] QF0107 8.1.1.2
12-1U0A9KV 12-1UIA7EN 8.1.1.1 [21211] QF0107 8.1.1.2
12-1QMX8LP 12-1UXMXVV 8.1.1.1 [21211] QF0108 8.1.1.2
12-1V3JQI3 12-1V3JQIN 8.1.1.1 [21211] QF0109 8.1.1.2
12-1SBRA31 12-1UW6491 8.1.1.1 [21211] QF0110 8.1.1.2
12-1UX6FHT 12-1UZD71U 8.1.1.1 [21211] QF0112 8.1.1.2
12-1R0X6NL 12-1V4108B 8.1.1.1 [21211] QF0113 8.1.1.2
12-1L3YVPO 12-1V9TQUZ 8.1.1.1 [21211] QF0116 8.1.1.2
12-1S1FXNF 12-1VBAHH9 8.1.1.1 [21211] QF0117 8.1.1.2
12-1VK09JB 12-1VK09K4 8.1.1.1 [21211] QF0119 8.1.1.2
12-1R6NUCR 12-1VM565P 8.1.1.1 [21211] QF0120 8.1.1.2
12-1TENCIJ 12-1VGLLFW 8.1.1.1 [21211] QF0121 8.1.1.2
12-1VM5K43 12-1VM585D 8.1.1.1 [21211] QF0122 8.1.1.2
12-OM5V6D 12-1VM8YSH 8.1.1.1 [21211] QF0123 8.1.1.2
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
12-1PBVORR 12-1VM6VS9 8.1.1.1 [21211] QF0127 8.1.1.2
12-1RRBFQ9 12-1VM9CT7 8.1.1.1 [21211] QF0128 8.1.1.2
12-1U5R7UV 12-1VNJ8VX 8.1.1.1 [21211] QF0129 8.1.1.2
12-1VM6N5D 12-1VM90VR 8.1.1.1 [21211] QF0131 8.1.1.2
12-1V0598R 12-1VR2KEB 8.1.1.1 [21211] QF0136 8.1.1.2
12-1VH3J0H 12-1VR2KGF 8.1.1.1 [21211] QF0136 8.1.1.2
12-1NSKL0N 12-1VABKYK 8.1.1.1 [21211] QF0142 8.1.1.2
12-1TUED13 12-1VR3YEY 8.1.1.1 [21211] QF0142 8.1.1.2
12-1TBLYYA 12-1WCVGL3 8.1.1.1 [21211] QF0147 8.1.1.2
12-1SF7E1F 12-1VR36YB 8.1.1.1 [21211] QF1104 8.1.1.2
12-1OVCU5D 12-1VCQE1C 8.1.1.1 [21211] QF2101 8.1.1.2
12-1UQ62AL 12-1VCQE0E 8.1.1.1 [21211] QF2101 8.1.1.2
12-1UX5Q36 12-1UX5Q4K 8.1.1.1 [21211] QF2101 8.1.1.2
12-1UX6LOB 12-1UX6LQ5 8.1.1.1 [21211] QF2101 8.1.1.2
12-1UX5RJV 12-1VR5MSB 8.1.1.1 [21211] QF4101 8.1.1.2
12-1QK1GG2 12-1QK1GGU 8.1.1 [21111] QF0001 8.1.1.1
12-1RBHO55 12-1RBHO6F 8.1.1 [21111] QF0001 8.1.1.1
12-1RPF1Z9 12-1RPF20H 8.1.1 [21111] QF0001 8.1.1.1
12-1RR1O5N 12-1RRCAHA 8.1.1 [21111] QF0001 8.1.1.1
12-1RRCAHM 12-1RRCAIV 8.1.1 [21111] QF0001 8.1.1.1
12-1RNH7ER 12-1RNH7G4 8.1.1 [21111] QF0001 8.1.1.1
12-1NLY66Z 12-1R7MK4U 8.1.1 [21111] QF0002 8.1.1.1
12-1KDK35I 12-1RBZBRA 8.1.1 [21111] QF0003 8.1.1.1
12-1S8QNHX 12-1S8QNIW 8.1.1 [21112] QF0004 8.1.1.1
12-1QT7XTB 12-1S20GWP 8.1.1 [21112] QF0005 8.1.1.1
12-1ONVDYP 12-1SGOF1D 8.1.1 [21112] QF0006 8.1.1.1
12-1RKLYHL 12-1RKLYIW 8.1.1 [21112] QF0006 8.1.1.1
12-1S8I5DB 12-1SGOF07 8.1.1 [21112] QF0006 8.1.1.1
12-1RAJ07R 12-1SD932B 8.1.1 [21112] QF0007 8.1.1.1
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA Enhancements and
Updates in 8.1.1.x Fix Packs
32
Enhancements and Updates in 8.1.1.x
Fix Packs
This topic identifies the enhancements and updates provided in version 8.1.1.x releases.
Enhancements are cumulative, inclusive of the previous 8.1.1.x Fix Pack releases. This topic contains
the following subtopics:
Enhancements and Updates in Version 8.1.1.4 on page 33
12-1KPTT57 12-1S4C6VJ 8.1.1 [21112] QF0009 8.1.1.1
12-1M4CI03 12-1M4CI1D 8.1.1 [21112] QF0009 8.1.1.1
12-1PCDF0P 12-1SB8AZ3 8.1.1 [21112] QF0009 8.1.1.1
12-1RPEN89 12-1ROX0RL 8.1.1 [21112] QF0009 8.1.1.1
12-1RVNYWA 12-1RXLAYA 8.1.1 [21112] QF0009 8.1.1.1
12-1SD8MX5 12-1SD8MYF 8.1.1 [21112] QF0009 8.1.1.1
12-1SSU76Z 12-1SSU77O 8.1.1 [21112] QF0009 8.1.1.1
12-1RVNYUP 12-1RVNYW3 8.1.1 [21112] QF0009 8.1.1.1
12-1RZPUA5 12-1S98C5N 8.1.1 [21112] QF0009 8.1.1.1
12-1RZPUB1 12-1S8R2S7 8.1.1 [21112] QF0009 8.1.1.1
12-1SSU75R 12-1SSU76Q 8.1.1 [21112] QF0009 8.1.1.1
12-1P5N6JM 12-1SLLJBD 8.1.1 [21112] QF0011 8.1.1.1
12-1OUTTD2 12-1T30LUT 8.1.1 [21112] QF0012 8.1.1.1
12-1SW8CMD 12-1T12EQ1 8.1.1 [21112] QF0013 8.1.1.1
12-1SK50OF 12-1SZMHS5 8.1.1 [21112] QF0014 8.1.1.1
12-1Q25Q6M 12-1TB9J4X 8.1.1 [21112] QF0018 8.1.1.1
12-1TK7X5V 12-1TKA88F 8.1.1 [21112] QF0030 8.1.1.1
12-1N3J10T 12-1TXT2GX 8.1.1 [21112] QF0032 8.1.1.1
12-1RAJ07R 12-1SINFF1 8.1.1 [21112] QF1001 8.1.1.1
Change
Request ID/
Base Bug ID
Fix Request
Quick Fix
Version
Merged Into
Fix Pack
Enhancements and Updates in Version 8.1.1.4
Table 3 lists the enhancements and updates provided in Fix Pack version 8.1.1.4.
This topic is part of Enhancements and Updates in 8.1.1.x Fix Packs on page 32.
Table 3. Enhancements and Updates in Version 8.1.1.4
Feature Enhancement
or Certification Number Feature Enhancement or Certification Description
ACR 475A Enhances UCM to support the Higher Education application.
Instructions for ACR 475
ACR 475B Enhances UCM to provide Data Governance, Data Quality, and
usability enhancements.
ACR 499 ACR 499 provides the following enhancements to the Bulk Orders
functionality:
Bulk Promotion Upgrade and Disconnect: Customers can apply
promotions to products using bulk requests.
Bulk Quotes: Customers can create bulk quotes.
Agreement and Network Child Types in Action Sets: Customers
can add Network or Agreement products in orders or quotes using
bulk requests.
Account Group Specification: Customers can use existing account,
contact, or assets lists to create bulk requests.
Submit Bulk Orders: Bulk orders can be submitted to the back
office in a single click from the Bulk Request screen.
ACR 502 ACR 502 provides the following Siebel Configurator enhancements:
The ability to defer an update within a scripting event to allow
multiple attribute change even add/set attribute calls.
A new scripting event to get product attribute values.
The ability to show/hide UI controls based on user properties and
the instance variable values.api method.
34
Table 5 lists the enhancements and updates provided in Fix Pack version 8.1.1.3.
ACR 526 Trade Promotions Management Quickstart
ACR 543 Extends the Siebel web services framework to provide an endpoint
through Oracle WLS.
ACR 623 Intelligent-Offer Generation (IOG) and certification with RTD 3.0
ACR 626 Integration of Mobile Sales Assistant to the Siebel On-Premise
application.
Feature Enhancement
or Certification Number Feature Enhancement or Certification Description
36
Feature
Enhancement or
Certification
Number Feature Enhancement or Certification Description
ACR 426 Adds electronic medical device reporting to the AECM module.
ACR 463 ACR 463 provides the following enhancements:
Order to Activate Enhancements:
Cancel Order header button
Cancellation affecting future dated orders:
Changes to support order revisions
Computing previous values on Submit
Dependency on follow-on orders
Due Date changes for Disconnect
Extending Sales Order EBO
Invalidate stale orders
Keep customer intent of submitted orders
Line item history
Non-paying accounts
Trouble Ticketing extensions
Order Update Business Web Service
Product Class/Attribute Sync Web Service
Product Import Web Service
Product Extensions for O2A:
Verify future-dated orders (warning message on header)
Warning messages on assets for future-dated orders
Order to Bill PIP Enhancements:
Support Friends and Family
Collections Flow
Map CRM discount to billing objects
Order validations
Billing Management UI enhancements:
Adjust unbilled events and child account events
Display child account balance in Siebel Billing Management screen.
View promotion name on invoice.
Feature
Enhancement or
Certification
38
ACR 474 Supports OSM Integration and the Order to Activate PIP, and forward-ports
MDM, PIM, and Order to Cash enhancements from Siebel 8.x to Siebel 8.1.1.x
applications.
Instructions for ACR 474 and ACR 508
ACR 500 Enables effective bundling of products necessary in the communications,
finance, media, and utilities industries, and enhances promotion capabilities
for component-level commitment, eligibility in promotion upgrade, asset-
based recommendations, and split/merge capabilities of promotions.
ACR 508 Forward-ports the Order to Cash PIP to Siebel version 8.1.1 applications.
ACR 529 Provides a single-step upgrade from Siebel Business Applications to Siebel
Cross-Industry Applications.
ACR 539 Modifies the Siebel Clinical product to support the Study, Subject, and Visit
Synchronization Process Integration Pack for Siebel Clinical and Oracle
Clinical. This enhancement also provides a way to accurately track and
respond to issues related to site performance and protocol adherence.
Feature
Enhancement or
Certification
Table 5 lists the enhancements and updates provided in version 8.1.1.2.
ACR 562 ACR 562 extends the functionality previously provided by ACR 422, which was
included in the Siebel 8.1.1.1 Fix Pack.
ACR 422 provided the following functionality:
Added missing text for ALT strings and other text read by screen readers.
Added titles for views and applets.
Provided announcements of row and column identifiers in list applets and
allowed the column used for the row identifier to be configurable.
Fixed various loss-of-focus defects.
Fixed various tab-order defects that are most often encountered when
users are navigating between applets.
Fixed various keyboard-shortcut defects and extended the set of available
shortcuts.
Added help topics for accessibility and updated the keyboard shortcuts
help topics.
ACR 574 Enhances the Smart Answer Server.
Feature
Enhancement or
Certification
40
Table 6 lists the enhancements and updates provided in version 8.1.1.1.
Feature
Enhancement or
Certification
Provides a utility for administrators to act on failing Store-and-Forward
transactions.
Enhances logging capabilities (server).
ACR 457 Provides cross-network validation and cascade delete enhancements for
network ordering for Siebel Customer Order Management for SIA.
ACR 464 Provides support for CRM Desktop for Outlook.
ACR 492 Provides Web service access through the Mobile Web Client to other local
desktop applications.
ACR 494 Provides Event Check enhancements and BEO Report functionality for the
Siebel Travel & Transportation application.
ACR 544 Enhances the Siebel Remote utility and allows it to be integrated with the
Siebel HA Upgrade solution.
Feature Enhancement or
Certification Number Feature Enhancement or Certification Description
ACR 432 Prevents users from opening multiple sessions on the Mobile Web
Client.
ACR 435 ACR 435 resolves the following issues with the printed version of the
5 Day Weekly HTML Calendar:
The calendar only shows appointments that are scheduled within
the 8 a.m. to 5 p.m. workday.
The default page orientation for most printers is set to Portrait.
Changing the display intervals on the Calendar results in sporadic
results.
Contact Name, Primary Phone, and Description should be
displayed on the 5 Day Weekly Calendar for each appointment.
ACR 437 Provides the ability to expose CDI WebServices for all CRUD
operations on key entities such as Account, Contact, Household,
Financial Account, and so forth.
42
ACR 439 ACR 439 contains the following enhancements for Siebel Search
Activates the Advanced Search button only when a search engine
has been configured.
Converts Saved Searches from an HTML list to a drop-down list.
Makes Recent Saved Searches only display when a search engine
has been configured.
Implements Preview with Search functionality to match the
functionality available with Siebel version 7 applications. ACR 439
provides a preview button in the Search results pane (left-pane
search). When users click the preview button, the record details
appear in a pop-up window.
Provides Attach functionality that is based on the parent applet.
ACR 439 provides an Attach button in the Search results pane
(left-pane search). When users click the Attach button, the record
selected in the search pane is attached to the record on the right.
For example, users can attach a contact to the opportunity record
displayed on the right side of the screen.
Corrects a Search Definition dependency for the FIND function.
FIND categories can now be defined irrespective of the search
engine definition.
Instructions for ACR 439B
Menus and Packages
Function Space Displays
Inventory Display Enhancements
Sleeping Room Mapping
ACR 452 ACR 452 provides the following Oracle Secure Enterprise Search
enhancements:
Remote Administration configuration
Auto keyword generation
Mixed operator search
Searching by file format
Dynamic weights
ACR 456 Allows users to perform Assignment Manager bulk-data maintenance
(CRUD on Rules, Positions, candidates and so forth) through client
views and screens.
ACR 467 Provides Siebel Financial Services Customer Order Management for
Banking functionality.
ACR 471 Bundles the Promotion and Product class relationship so that
changing a promotion in a change order loads the default product.
ACR 476 Rebases Siebel Email Response support for Smart Answer support.
Resolves key connection gaps between core processes:
marketing and trade management, trade management, and retail
execution.
Provides key functional enhancements needed to fulfill Oracle
Trade Management processes.
Significantly enhances usability across trade management in
Siebel applications.
Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA Configuration
Instructions for Enhancements and Updates
44
Configuration Instructions for
Enhancements and Updates
This topic contains configuration instructions for some of the enhancements and updates provided in
version 8.1.1.x releases.
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 467.
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 358 on page 45
ACR 481 Provides the ability to ignore Outlook appointments/tasks based
on the Private flag.
Addresses an issue where the Outlook Add-in can lock users out
of their accounts after the password has been changed on the
authenticating agent (such as Active Directory), but the users
have not updated their Outlook Add-in passwords.
ACR 488 Provides Histories and Futures functionality.
Instructions for ACR 474 and ACR 508 on page 169
Instructions for BI Publisher Enhancements on page 466
For information about how to implement ACR 358, within My Oracle Support, navigate to the
Knowledge tab, and search for Article ID 781368.1
Back to Configuration Instructions for Enhancements and Updates
Use the instructions in the following section to configure ACR 403.
46
Preinstallation Instructions for ACR 403
Before you apply the Siebel 8.1.1.x Fix Pack, the local database needs to be extracted from the
Server machine and initialized on the machine where Siebel Mobile Client will be installed.
Use the following procedure to extract the local database from the server machine and initialize it on
the machine where the Siebel Mobile client will be installed.
To extract the local database and initialize it
1 Navigate to the Administration - Siebel Remote screen.
a Query for HQ, and select a sample user in your system as mobile client and MOBILE CLIENT -
STANDARD as routing model.
b Navigate to the Administration - Siebel Remote screen, and then the Remote System Preferences
view. Uncheck the following parameters:
Enable Mobile Password Expiration
Enable Mobile Password Syntax Check
Optimized Visibility Check
Check Enable Transaction Logging
2 Enable Siebel Remote Component Group.
3 From the Server Manager command line utility, connect to the Siebel Server and run thefollowing
commands:
change param authentication=none for comp synchmgr
list advanced param authentication for comp synchmgr
4 Verify that the authentication parameter has been configured correctly.
5 Using the Server Manager Command line utility, run the jobs-Generate New Database and db
extract as follows:
start task for comp gennewdb with sleeptime = 10
list task <tasked ID> (Keep listing the task until the status changes to "Completed")
start task for comp dbxtract with client=a sample user in your system
list task <tasked ID> (Keep listing the task until the status changes to "Completed")
list advanced param portnumber for comp synchmgr
Installation Instructions
1 Apply 8.1.1.x on Siebel Tools and Siebel Enterprise Server. (The patch for Siebel Enterprise
Server automatically patches the "Siebel Server, Siebel Gateway Server, and Siebel Database
Server components.)
2 Verify that the following files are present under DBSRVR\ENU
seed_disconn.dat
seed_disconn.inp
3 Verify that the following files are present under <Siebel Tools loc>\TOOLS\REPPATCH\:
discon_symbstring.sif
disconnected.sif
4 In tools.cfg, make the following changes:
SymStrPrefix = SBL_ (instead of X_)
DockConnString = <Siebel Server Name>::<Synchmgr port>
(For example, sdchs21n467::40400)
5 Log into Siebel Tools as a sample user in your system and point to the local database.
6 Enter the password for the sample user, click Continue, enter the Server password for the sample
user at the prompt, and click Next.
Siebel Tools starts initialization of all the tables and parameters for the local database. Once the
initialization is done, Siebel Tools will automatically open and will connect to the local database.
7 In the Tools ODBC entry, enter the UID/PWD for the local database. (For the local database, UID/
PWD should be DBA/SIEBEL12]
8 Enter the encryption Key for the database and check for the database connection. It should show
as successful once the UID/PWD and Encryption Key have been entered correctly.
TIP: To get the encryption key, navigate to the Administration - Siebel Remote screen, and then
the Mobile Clients view. Query for the HQ* and then query for the sample user. In the Additional
Info column, query for RemLocSec:PlainKey.
9 Log into Siebel Tools (pointing to the local database). Navigate to Tools, and then Check Out.
NOTE: If you receive the "Error connecting to Datasource" error message, then check the data
source information. The source should be SSD default instance (UID/Server pwd) and
Destination: SSD Local Db default instance.
10 Click the Get button to get all the projects.
Siebel Tools will get all the projects one by one. This will take two to five hours to complete.
11 Open Siebel Tools (connecting to the local database) and lock the following projects one by one
by selecting the project and setting the "Locked" flag to "true":
Fast Search
Service
Siebel Universal Agent
ERM Admin
New Search
Siebel Field Service Enterprise
Siebel Marketing Enterprise
Siebel Sales Enterprise
48
Siebel eChannel
Siebel Field Service Enterprise
12 Import the discon_symbstring.sif and Disconnected.sif files (mentioned in Step 3) by clicking on
Tools> Import from Archive and selecting the .sif files one by one. Complete the following steps:
a Click the Next button in "Import Wizard - Preview".
Once import is successful, the number of objects imported and updated will display. Click OK.
b Click Finish in "Import Wizard - Summary" to finish the import.
13 Install Mobile Client (MWC) on a Microsoft Windows XP machine (An XP machine is needed to
start the DSM listener and .net 2.0 should be installed on that machine.
14 Make a copy of your existing siebel.srf (or siebel_sia.srf for SIA) and compile the imported
changes mentioned in Step 12 to the siebel.srf (or siebel_sia.srf).
15 In MWC Application.cfg (such as uagent.cfg for Siebel Call Center Application) make the following
changes:
DockConnString = <machine name of the Siebel server machine from where the local
database is imported>::<Synch Mgr Port> (This is applicable only if this is a fresh
installation.) For example, DockConnString = sdcp1952i017::40400
SearchDefName = Mobile Client Search Definition
16 Apply Siebel 8.1.1.x on the Mobile Web Client to create the dsm.zip file under <mobile client
install loc>\BIN>. Unzip the dsm.zip file to create the dsm folder under <mobile client install
loc>\BIN>.
17 Run the dataimp command as follows:
a Copy the files seed_disconn.dat and seed_disconn.inp files from 4 to the Mobile Client machine
(for example, D:\FS\ Build4_Final.)
b Navigate to <mobile client install loc>\BIN> using the command prompt and run the following
command.
dataimp /u $USERNAME /p $PASSWORD /c "$Local ODBCDatasource" /f "seed_disconn.dat"
/i "seed_disconn.inp" /d $Tableowner /Z Y /l implog.log
For example:
dataimp /u DBA /p SIEBEL12 /c "SEAW Local Db default instance" /f "D:\FS\ Build4_Final
\seed_disconn.dat" /i "D:\FS\Build4_Final\seed_disconn.inp" /d siebel /Z Y /l implog.log
Once dataimp command is done, a message will be displayed in the following format showing
the details of the tables and rows that were affected:
TOTAL TABLES: 39
TOTAL ROWS PROCESSED: 167
TOTAL ROWS FAILED: 0
TOTAL ROWS SUCCEEDED: 167
ELAPSED TIME: 2.219s
Disconnecting from the database
Adding the Mobile Search Administration Screen
You must add the Mobile Search Administration screen for each application project in Siebel Tools.
NOTE: The Mobile Search Administration screen has already been added for the Siebel Call Center
application.
To add the Mobile Search Administration screen
1 Connect to Siebel Tools.
2 From the Object Explorer, expand the Application object type.
3 Select the application in the Object Explorer, and note the project to which the application
belongs.
4 Lock the application project.
5 From the Object Explorer, expand the Application object type.
6 Select Screen Menu Item.
50
7 Choose Edit, and then New Record, and use the following information to define the object
properties:
For more information about installing and configuring the Disconnected Search Module to enable
Siebel Mobile Search, see Siebel Search Administration Guide on the Siebel Bookshelf at http://
The following sections contain procedures for making the configuration changes needed in order to
implement ACR 422.
For more information about accessibility enhancements, see Accessibility Guide for Siebel Business
Applications on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.
Use the following procedure to enable screen readers to read out the applet summary for an
application. This is a user property based on the respective XML for an application.
To allow screen readers to read out the applet summary for an application
1 Navigate to Object Explorer in Siebel Tools.
2 Navigate to View > Options, and click the Object Explorer tab.
3 Unselect Application Object, select it again to add all of the child objects to the Object Explorer,
and click OK.
4 Click Application, and query for the Application Names listed in the following table:
Property Description
Screen This should be set to Search Mobile Admin View Screen.
Sequence Use Screen View Sequence Editor to determine the sequence of views. Do not
edit the Sequence property of the Screen View Object manually. See
Configuring Siebel Business Applications for defining Sequence for Screen
View Objects.
Text - String
Reference
This should be set to SBL_ADMINISTRATION_-_MOBILE_SEARCH.
New/
Changed Name
Application
User Property Value
SIA SIF File
Name
HOR SIF File
Name
Changed Siebel Universal
Agent
AccessibilityXMLF
ileName
Accessibility_Callce
nter.xml
nter_SIA.sif
Accessibility_Callc
enter_HOR.sif
Changed Siebel
eMarketing
AccessibilityXMLF
ileName
Accessibility_eMark
eting.xml
Accessibility_eMark
eting_SIA.sif
Accessibility_eMa
rketing_HOR.sif
Changed Siebel eSales AccessibilityXMLF
ileName
Accessibility_eSales
.xml
Accessibility_eSale
s_SIA.sif
Accessibility_eSal
es_HOR.sif
5 Click the '+' sign and select 'Application User Property'.
6 Lock the object, right-click and select New Record.
7 Add the User Properties listed in the preceding table.
8 Save the changes.
Enabling Screen Readers to Read MVGs and Pick Applets for Calendar, Calculator, and MVG
Use the following procedure to enable screen readers to read out the MVG and Pick Applet for
Calendar, Calculator, and MVG. After these changes have been made, screen readers will read out a
Calendar Pick Applet as shown in the following example: Start Date: 25/07/2007 Calendar Icon.
To enable screen readers to read out the MVG and Pick Applet for Calendar,
Calculator, and MVG ( Symbolic Strings)
3 Select the Symbolic Strings Object and click OK to add the Symbolic Strings object to Object
Explorer.
4 Click on Symbolic Strings and query for 'Current String Value' as 'Input'.
5 Lock the object.
6 Make the following changes, as detailed in the following table:
a For SBL_CALCULATOR_ICON_ALT_TXT, change 'Current String Value' to 'Calculator'.
Changed Siebel eService AccessibilityXMLF
ileName
Accessibility_eServi
ce.xml
Accessibility_eServ
ice_SIA.sif
Accessibility_eSer
vice_HOR.sif
Changed Siebel Public
Sector
AccessibilityXMLF
ileName
Accessibility_Public
Sector.xml
Sector_SIA.sif
Accessibility_Publi
cSector_HOR.sif
Changed Siebel Sales AccessibilityXMLF
ileName
Accessibility_Sales.
xml
Accessibility_Sales
_SIA.sif
Accessibility_Sale
s_HOR.sif
Changed Siebel Service AccessibilityXMLF
ileName
Accessibility_Servic
e.xml
e_SIA.sif
Accessibility_Serv
ice_HOR.sif
New/
Changed Project Name Value SIA SIF File Name
HOR SIF File
Name
Changed Symbolic
Strings
SBL_CALCULATOR_IC
ON_ALT_TXT
Calculator SymbolicStrings_SI
A.sif
SymbolicStrings_H
OR.sif
Changed Symbolic
Strings
SBL_CALENDAR_ICON
_ALT_TXT
Calendar SymbolicStrings_SI
A.sif
SymbolicStrings_H
OR.sif
Changed Symbolic
Strings
SBL_EDIT_ICON_ALT_
TXT
Pick Applet SymbolicStrings_SI
A.sif
SymbolicStrings_H
OR.sif
New/
Changed Name
Application
User Property Value
SIA SIF File
Name
HOR SIF File
Name
52
b For SBL_CALENDAR_ICON_ALT_TXT, change 'Current String Value' to 'Calendar'.
c Save the changes.
d In Symbolic Strings, query for 'Current String Value' as 'Select'.
e For SBL_EDIT_ICON_ALT_TXT, change 'Current String Value' from Select to 'Pick Applet'.
f Save the changes.
Calculator, and MVG ( Bitmaps)
2 Click on Bitmap Category and query for 'HTML Control Icons'.
3 Lock the HTML Control Icons object.
4 Navigate to Bitmap (child object) and query for 'CALENDAR_ ICON' and CALCULATOR_ICON.
5 Change the 'Alt Text' value to 'Calendar' and 'Calculator' respectively, as shown in the following
table:
6 Save the changes.
7 In HTML Control Icons query for ' EDIT_ICON' and change the Alt Value to 'Pick Applet', as shown
in the preceding table.
8 Save the changes.
Creating Keyboard Shortcuts for Navigation
Use the following procedures to provide shortcut keys for navigation.
To provide shortcut keys for navigation ( symbolic strings)
New /
Changed
Bitmap
Category Bitmap
Alt Text
Value Description
SIA SIF File
Name
HOR SIF File
Name
Changed HTML
Control
Icons
CALENDAR_ ICON Calendar Change the
Alt text from
"Input" to
Calendar.
HTMLControlIcon
s_SIA.sif
HTMLControlIcon
s_HOR.sif
Changed HTML
Control
Icons
CALCULATOR_ICON Calculator Change the
Alt text from
"Input" to
Calculator.
HTMLControlIcon
s_SIA.sif
HTMLControlIcon
s_HOR.sif
Changed HTML
Control
Icons
ICON_SELECT Pick
Applet
Change the
Alt text from
"Select" to
Pick Applet.
HTMLControlIcon
s_SIA.sif
HTMLControlIcon
s_HOR.sif
3 Select Symbolic Strings Object and click OK to add the Symbolic Strings object to Object
Explorer.
4 Lock the 'Symbolic Strings' project.
5 Right-click and click New Record.
6 Add the new records listed in the following table:
Table 7 lists some of the keyboard shortcuts available with ACR 422, and the procedures in the
section that follows describe how to add these keyboard shortcuts.
New/
Changed Project Name
Current
String Value SIA SIF File Name HOR SIF File Name
New Symbolic
Strings
SBL_CTRL_+_ALT_+_] Ctrl + Alt + ] SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif
New Symbolic
Strings
SBL_CTRL_+_ALT_+_[ Ctrl + Alt + [ SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif
New Symbolic
Strings
SBL_CTRL+SHIFT+B Ctrl+Shift+B symstr_columnsdisplay
ed_SIA.sif
symstr_columnsdisplaye
d_HOR.sif
New Symbolic
Strings
SBL_CTRL+, Ctrl+, SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif
New Symbolic
Strings
SBL_CTRL+. Ctrl+. SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif
New Symbolic
Strings
SBL_ALT_G ALT+G SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif
New Symbolic
Strings
SBL_ALT_U ALT+U SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif
New Symbolic
Strings
SBL_ALT_W ALT+W SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif
Table 7. Keyboard Shortcuts
Command Action Accelerator Key Sequence Description SIA SIF File Name
NextApplet Next Applet Ctrl + Alt + ] Ctrl+Alt+221 Shifts focus to the
first anchor of the
next applet
CmdNextApplet_SIA.sif
PrevApplet Previous
Applet
Ctrl + Alt + [ Ctrl+Alt+219 Shifts focus to the
first anchor of the
previous applet
CmdPreviousApplet_SIA.sif
Refine Query
(SWE)
N/A Alt+G Alt+G N/A CmdRefineQuery_SIA.sif
First Page (SWE) N/A Alt+U Alt+U N/A CmdFirstPageSWE_SIA.sif
Last Page (SWE) N/A Alt+W Alt+W N/A CmdLastPageSWE_SIA.sif
54
Creating Keyboard Shortcuts for Commands
Use the following procedures to provide keyboard shortcuts for commands.
To provide a keyboard shortcut for the NextApplet command
3 Select the 'Command' object and click OK to add the Command Strings object to Object Explorer.
4 Click the Command object on Object Explorer and query for the 'NextApplet' command.
5 Lock the object.
6 Click the '+' sign in Object Explorer and choose 'Accelerator'.
7 In 'Display Name - String Reference', provide the newly created Symbolic String or in 'Display
Name' provide 'Ctrl + Alt + ]'.
8 In the 'Key Sequence' field, change the value to 'Ctrl+Alt+221'.
To provide a keyboard shortcut for the PrevApplet command
1 Click the Command object on Object Explorer and query for the PrevApplet command.
2 Lock the object.
4 In the Display Name - String Reference' field, enter the newly created Symbolic String or in the
Display Name field, enter 'Ctrl + Alt + ['.
To provide a keyboard shortcut for the RefineQuery[ SWE] command
1 Click the Command object in Object Explorer and query for the Refine Query[SWE] command.
2 Lock the object.
4 Copy the Record Name '2'. Name the New Record '3'.
5 In the Display Name field, enter 'Alt+G'.
Columns Displayed
(SWE)
N/A Ctrl+Shift+B Ctrl+Shift+B N/A CmdColumnsDisplayed_SIA.sif
NextApplet Next Applet Ctrl + Alt + ] Ctrl+Alt+221 Shifts focus to the
first anchor of the
next applet
Table 7. Keyboard Shortcuts
Command Action Accelerator Key Sequence Description SIA SIF File Name
6 In the Key Sequence field, change the value to 'Alt+G'.
To provide a keyboard shortcut for the FirstPage command
1 Click on Command object in Object Explorer and query for the First Page (SWE) command.
2 Lock the object.
5 In the Display Name field, enter 'Alt+U'.
6 In the Key Sequence field, change the value to 'Alt+U'.
To provide a keyboard shortcut for the LastPage ( SWE) command
1 Click on Command object in Object Explorer and query for 'Last Page (SWE)' Command.
2 Lock the object.
3 Click on '+' sign in Object Explorer and choose 'Accelerator'.
4 Copy the Record Name '2'. Name the New Record '3'
5 In the Display Name field, enter 'Alt+W'.
6 In the Key Sequence field, change the value to 'Alt+W'.
To provide a keyboard shortcut for the Columns Displayed ( SWE) command
1 Click on Command object on Object Explorer and query for 'Columns Displayed (SWE)'
Command.
2 Lock the object.
5 In the Display Name field, enter 'Ctrl+Shift+B'.
6 In the Key Sequence field, change the value to 'Ctrl+Shift+B'.
To provide a keyboard shortcut for the Previous Record ( SWE) command
1 Click on Command object on Object Explorer and query for 'Previous Record (SWE)' Command.
2 Lock the object.
5 In Display Name field, enter 'Ctrl+,'.
6 In the Key Sequence field, change the value to 'Ctrl+,'.
56
To provide a keyboard shortcut for the Next Record ( SWE) command
1 Click on Command object on Object Explorer and query for 'Next Record (SWE)' Command.
2 Lock the object.
5 In the Display Name field, enter 'Ctrl+.'
6 In the Key Sequence field, change the value to 'Ctrl+.'
Providing Default Focus for Search Center
The following section details the changes that are required for the search applet in order to provide
a default focus for the "Search" option provided in the Siebel application.
Use the following procedure to provide a default focus for Search.
To provide a default focus for Search
2 Navigate to Applet.
3 Query for "Search lookin" and lock it.
4 Enter "Search" in the Title field.
5 Make sure that the proper Symbolic String has been selected.
To add the DefaultFocus User Property
3 Query for "Search lookin".
4 Navigate to Applet User Property.
New /
Changed Applet Name Title Description SIA SIF File Name HOR SIF File Name
Changed Search lookin Search Provides a title
to the applet
for screen
readers to
read out.
AppletSearchlookin_SIA.sif AppletSearchlookin_HOR.sif
5 Add the DefaultFocus user property, as described in the following table.
NOTE: The DefaultFocus user property can be applied for any form applet where the user requires
a default focus.
Creating the View Info Command
The following procedure explains how to create the View Info command.
To create the View I nfo command
2 Navigate to Command and lock the "Command" project.
3 Create a New Command named "View Info" with project "Command" as the project, using the
values detailed in the following table:
NAME="ViewInfo"
METHOD="ViewInfo"
TARGET="SI Plus"
DISPLAY_NAME_-_STRING_REFERENCE="SBL_DOES_NOT_MATTER-1004225828-03I"
4 Add a new Accelerator to the Command for the required Key Combination with the following
values:
NAME="1"
BROWSER_PLATFORM="All"
INACTIVE="N"
New /
Changed Applet Name
Applet User
Property Value Description
SIA SIF File
Name HOR SIF File Name
Changed Search lookin DefaultFocus SearchFor Added the user
property to set the
default focus
AppletSearchlo
okin_SIA.sif
AppletSearchlookin_H
OR.sif
Command Project Action Accelerator
Key
Sequence Description
SIA SIF
File Name
HOR SIF
File Name
View Info Command ViewInfo Ctrl + Alt + Z Ctrl + Alt
+Z
A new shortcut
key that
generates a
dialog box that
contains
ViewName, View
Summary and
Applet Names
CmdViewInf
o_SIA.sif
CmdViewInf
o_HOR.sif
Sub-View Tab
(SWE SI)
SWE N/A Ctrl + Alt + V Ctrl +Alt
+V
N/A CmdSubVie
wTab_SIA.si
f
CmdSubVie
wTab_HOR.s
if
58
KEY_SEQUENCE="Ctrl+Alt+Z"
NOTE: Although it is not mandatory, it is important that you enter Does not matter as the value
for the Display Name or Caption field.
5 Add a new Symbolic String if required.
6 Add the required Key Combination.
7 Navigate to Menu, and create a new Menu Item (Hidden) under the menu used by your
application, using the following values:
(For example, Siebel Universal Agent uses Generic Web Menu.)
Name="Hidden-View Info
Position=8.39
Command = "ViewInfo"
Caption="Does not matter"
8 Associate this menu item to the newly created command object.
For more information about shortcuts, refer to other shortcuts such as NextApplet within Siebel
Tools.
Enabling Screen Readers to Read Out the Check Box HTML Flag as HTML
The following procedure allows screen readers to read out the check box HTML Flag as HTML. By
default, it reads as Public. To make this change, you can also import the
Applet_CommPackageResponse_SIA.sif file. For information about how to import .sif files, see
Importing SIF Files on page 65.
To enable screen readers to read out the check box "HTML Flag" as HTML
1 Open Siebel Tools, and navigate to applet "Comm Package Response Form Applet".
2 Right-click, and select the "Edit web layout" menu item.
3 Focus on the HTML template check box
4 Change the control name from "Public" to "HTML Flag".
Resolving an Error Generated When Creating New Records Within the Leads Screen
Use the following procedure to resolve an error message that occurs when users are creating new
records under the Leads screen, so that users are not able to see any case records in the Pick Cases
MVG. To make this change, you can also import the PUBLeadListCaseMvgApplet.sif, PUBLeadsList.sif,
PUBLeadsListApplet.sif, and CaseMvg.sif files. For information about how to import .sif files, see
To resolve an error message generated in the Leads screen
1 Open Siebel Tools, and navigate to the "PUB Lead List Case Mvg Applet" applet.
2 Lock the object.
3 Navigate to Applet Web Template.
4 Add one more Web Template Item for Base.
5 Navigate to the "PUB Leads List Applet" applet and lock it.
6 Click Edit to create a web template and add the necessary controls, along with SAVE and CANCEL
buttons.
Making the Help System Accessible for Screen-Reader Users
The following procedure makes the help system accessible for screen-reader users. It adds a topic
to the Siebel iHelp system that describes accessibility features and how to use them, and it also
ensures that the iHelp system is available on each home page of the Siebel application. To make
these changes, you can also import the Accessibility_symbolicString.sif, CCLoginPage_HOR.sif,
CCLoginPage_SIA.sif, DotComPage_HOR.sif, and DotComPage_SIA.sif files. For information about
how to import .sif files, see Importing SIF Files on page 65.
1 Add a symbolic string called SBL_ACCESSIBILITY.
2 Add a web page item called AccessibilityButton in the Web Page: DotCom Page Container
eService (Framed), locking the project "eApp".
3 Add another web page item called AccessibilityButton in the Web Page: CC Login Page (Login
Only).
Generating HTML Summary Attributes for All List Applets
The following changes need to be made for Generating HTML SUMMARY attributes for all list applets.
The default tag text should be set to the applet header name. Add TITLE or LABEL for each table
entry (all HTML form elements). Row and column headers must be identified as required by OGHAG
TABLE-1 and TABLE-2. Adding a row title for each row in data table (Suggestion: this could be the
first displayed data column in the applet display. Ideally the customer can select which column can
be used as the index for the row title through configuration).
NOTE: The list applet row ids are not available out of the box. Users can add them if they want. The
first data column will be used as the default rowid when there is no row id provided in the "RowId"
applet user property. There are two options available to users to select different rowid.
Option 1: Users need to contact the administrator to define the "RowId" user property.
To do this, a new applet user property called "RowId" has to be added for the list applet. The "RowId"
value should be equal to one of the displayed column name. For example, in the Contact list applet,
if 'Last Name' has been selected as the row header, the user property value has to be set to "RowId
= Last Name". Here "Last Name" is the list column name.
Option 2: Users can select the column displayed window and select some other column as the first
column for the list applet. The newly-selected column will become the rowid. Lock the particular
applet that needs to be changed.
60
Providing a New Key Combination for the Next and Previous Record Commands
NOTE: The tables that follow this procedure provide more information about the fields that you are
changing.
To provide key combinations for Next Record and Previous Record
4 Within Object Explorer, click the Command object and query for 'Previous Record(SWE)'
Command.
5 Lock the object.
7 Change the 'Display Name' from 'Ctrl+,' to 'Alt+,'
8 In the 'Key Sequence' field, change the value to Alt+0xBC.
9 Within Object Explorer, click the Command object and query for 'Next Record(SWE)' Command.
10 Lock the object.
12 Change 'Display Name' from 'Ctrl+.' to 'Alt +.'
13 In the 'Key Sequence' field, change the value to Alt+0xBE.
New/
Current
String
Value HOR SIF File Name SIA SIF File Name
New Symbolic Strings SBL_ALT+, Alt+, symbolistring_Next_Prev_H
OR.sif
symbolistring_Next_Prev_S
IA.sif
New Symbolic Strings SBL_ALTL+. Alt+. symbolistring_Next_Prev_H
OR.sif
IA.sif
Command Project Accelerator Key Sequence SIA SIF File Name HOR SIF File Name
Next Record(SWE) Command Alt +. Alt+0xBE Next_Prev_SIA.sif Next_Prev_HOR.sif
Previous
Record(SWE)
Command Alt +, Alt+0xBC Next_Prev_HOR.sif Next_Prev_HOR.sif
Providing Alt Text for Bullets
In Recent Records, the bullets need to have alt text provided. To make this change, import the
orangebullet_HOR or orangebullet_SIA.sif files as detailed in the following table. For information
about how to import .sif files, see Importing SIF Files on page 65.
Enabling or Disabling the Confirmation Message on Page Refresh
The procedure in the following section describes how to enable or disable the confirmation message
upon page refresh. To make this change, you can also import .sif files. To do so, import
ConfirmationMessage_SIA.sif and ConfirmationMessage_HOR.sif. For symbolic strings, import
symstr_confirmationmessage_SIA.sif and symstr_confirmationmessage_HOR.sif. For information
To enable or disable the confirmation message upon page refresh
1 Log into the application using /editseeddata (for Siebel Developer Web Client) for the local
database or dedicated database (for the master database, the Add button is enabled by default).
2 Navigate to Administration - Data > List Of Values Explorer, and add the new LOV types
mentioned in the following table:
New/
Current String
Changed Symbolic
Strings
SBL__IMG_SRC__IMAGES/
CHEVRON_SM.GIF__ALIGN
__RIGHT__BORDER__0
<IMG
SRC="images/
orange_bullet.gif"
align="right"
border="0" alt="" >
orangebullet_HOR.sif orangebullet_SIA.sif
New/Changed Project Value Description
New Symbolic Strings Accessibility Create a new Symbolic String for
Accessibility Project for the
"Confirmation Message" User
Preference
New Symbolic Strings Confirmation
Message
Create a new string for the Control
Type
Display
Value Translate Multilingual
Language
Independent
Code Order Language Name
SWE_CONFIRMATION
_MESSAGE
TRUE Yes Yes TRUE 1 English-American
SWE_CONFIRMATION
_MESSAGE
FALSE Yes Yes FALSE 2 N/A
62
3 After you have added these changes, navigate to Screen > System Administration > List Of
Values to view these changes in the repository.
The following changes have been made to the User Preferences Business Component.
The following table describes the new User Profile Confirmation Message Parameter Applet that has
been added to support ACR 422.
The following table describes the applet controls changes that have been implemented to support
ACR 422.
New/
Changed Name Project
Business
Component Static Type Field Type Value
New Confirmation
Message
Picklist
User Preference PickList Generic Yes Type SWE_CONFIRM_MESSAGE
Name PickList Predefault Value Type
SWE/Confirmation Message Confirmation Message
Picklist
TRUE DTYPE_TEXT
New/
Business
Component Class Title
New User Profile
Confirmation Message
Parameter Applet
User
Preferences
User Preferences CSSFrameBase Accessibility
Name Caption Field HTML Type Method Invoked Runtime Field Type
Applet Title Accessibility N/A Text N/A N/A N/A
ConfirmMssg Confirmation
Message
SWE/
Confirmation
Message
Text N/A Yes BC Field
ExecuteQuery Go N/A MiniButtonQuery ExecuteQuery N/A N/A
NewQuery Query N/A MiniButtonEdit NewQuery N/A N/A
QueryAssistan
t
Query
Assistant
N/A MiniButtonQuery ShowQueryAssistant N/A N/A
ResetRecord Reset N/A MiniButton ResetRecord N/A N/A
SaveEditRecor
d
Save N/A MiniButtonEditNe
w
ExplicitWriteRecord N/A N/A
UndoQuery Cancel N/A MiniButtonQuery UndoQuery N/A N/A
WebEditTitle Accessibility N/A Label N/A N/A N/A
The following table describes the view changes that have been added to support ACR 422.
The following table describes the User Profile screen changes that have been added to support ACR
422.
Resolving an Error Message Within Under Diseases > Cases 3LNV
Users are receiving error messages while creating new records under Diseases > Cases 3LNV. This
is specific to SIA.
Use the following procedure to resolve this issue.
To resolve an error message within Cases 3NLNV
1 Add the 'Edit' template to 'PUB Disease Case List Applet'.
2 Make sure that the Execute Query, WriteRecord, UndoQuery, UndoRecord, and Query Assistant
controls are present on the applet template.
NOTE: Edit template uses 'Applet List Edit (Edit/New/Query)' as the web template.
Resolving an Error Where Commands Are Executed Before Users Click Enter
Users are encountering an issue where before they click Enter on a menu item in the Show dialog
box, the command is executed.
To resolve an error in which commands are executed before users click Enter in the
Show dialog box
New/Changed Name Project Business Object
Visibility Applet
Type
New User Profile
Parameter View
User Preferences User Preferences User Profile
Parameter Applet
New/Changed Name View Type Visibility Applet Type
New User Profile
Parameter View
User Profile
Parameter View
Aggregate View User Profile Confirmation
Message Parameter Applet
New/Changed Name Project
Web
Template SIF File
New PUB Disease
Case List Applet
PUB HLS Bio
Terrorism
Edit Disease_Case_SIA.sif
64
Explorer.
5 Right-click and select 'New Record'.
6 Add the new records mentioned in the following table.
To implement the NextPage and PreviousPage commands
4 Within Object Explorer, click the Command object and query for the 'NextPage' command.
5 Lock the object.
6 Within Object Explorer, click the '+' sign and choose 'Accelerator'.
7 For 'Browser Platform' - Extended, in 'Display Name - String Reference', provide the newly
created Symbolic String or in 'Display Name' provide 'SBL_ALT+CTRL+DOWN'.
8 In the 'Key Sequence' field, change the value to 'Alt+Ctrl+Y', as shown in the following table:
9 Within Object Explorer, click the Command object and query for the 'PreviousPage' command.
10 Lock the object.
11 Within Object Explorer, click the '+' sign in and choose 'Accelerator'.
created Symbolic String or in 'Display Name' provide 'SBL_ALT+CTRL+UP'.
13 In the 'Key Sequence' field, change the value to 'Alt+Ctrl+L'.
New/Changed Project Name Value
New Symbolic Strings SBL_ALT+CTRL+Y Alt+Ctrl+Y
New Symbolic Strings SBL_ALT+CTRL+L Alt+Ctrl+L
Command Action Accelerator Key Sequence Description
NextPage Next Page Alt + Ctrl + Y Alt+Ctrl+Y Navigate to the Next
Page
PreviousPage Previous Page Alt + Ctrl + L Alt+Ctrl+L Navigate to the
Previous Page
Resolving an Error Encountered While Creating a New Record in the Identities Form Applet
The information in the following section resolves an issue where users encounter a problem within
the Immigration contacts screen > Identities view when they try to create a new record under the
Identities form applet. To make this change, you can follow the procedure below, or you can import
the PublicSector_Controls.sif file. For information about how to import .sif files, see Importing SIF
Files on page 65.
To resolve this error message, change the HTML Type property of the DeleteRecord control from
MiniButton to MiniButtonEdit for the PUB Immigration Identity Form Applet, the PUB Lead Form
Applet, the HLS Group Form Applet, the Disease Form Applet, the FINS Application Entry Applet
ACAPS, and the HLS Medication Form Applet. Use the following bulleted list information group for
each applet as a reference point.
Applet: 'PUB Immigration Identity Form Applet'
Template: Edit
Additions: UndoRecord and WriteRecord controls
Applet: PUB Lead Form Applet
Template: Edit
Additions: WriteRecord (save) control. UndoRecord (cancel) does not need to be added as the
'DeleteRecord' control is already present on the template.
Applet: "HLS Group Form Applet", "Disease Form Applet" and "FINS Application Entry Applet -
ACAPS"
Template: Edit
Additions: 'WriteRecord' control.
Applet: HLS Medication Form Applet
Template: Edit
NOTE: For the HLS Group Form Applet, Disease Form Applet, and FINS Application Entry Applet,
access these applets from under the Application screen and not from the BCM Applications screen.
The necessary changes need to be made under the configuration context of Siebel Public Sector for
these applets, because they are also used by the FINS application.
Resolving an Issue Where Users Are Unable to Query for Evidence Parent Information
The following procedure resolves a problem where under Evidence screen> Evidence parent, users
are unable to query for User Parent, and they receive an error message. To make this change, you
can also import the PublicEvidencePickApplet_SIA.sif file. For information about how to import .sif
files, see Importing SIF Files on page 65.
Add 'Popup Query' template to the 'PUB Evidence Pick Applet' with appropriate controls
[ExecuteQuery and CancelQuery] placed on it.
Importing SIF Files
The following procedure describes how to import .sif files.
66
To import SI F files
1 Lock the particular object /project that needs to be changed.
2 Navigate to Tools > Import from Archive and select the related .sif file
3 Click OK, and follow the instructions in the wizard to implement the changes.
4 Stop the servers, compile the objects or projects into respective .sif file and then restart the
servers.
Configuration Changes for Adding the Applet Summary for New or
Customized Applets
The following sections contain configuration changes that you must make to add the applet summary
for new or customized applets. You must import .sif files for table changes, apply the DLL, import
seed data, and import the Accessibility Project .sif files. The necessary changes are detailed in the
following sections:
Importing SIF Files for Table Changes
Applying the DDL
Importing Seed Data
Importing the Accessibility Project SIF Files
The procedure in the following section describes how to add the applet summary for customized or
new applets.
To import the SI F file for table changes
1 Lock the (Table Common) project by navigating to the Project Tab and checking the "Locked"
check box.
2 Import the Table archive file "Accessibility_Table.sif" table archive file.
3 Click Yes when the dialog box displays and asks This operation should only be performed while
connected to your local database. Would you like to continue anyway?
4 Select the "Accessibility_Table.sif" file.
5 Select the first option "Overwrite the object definition in the repository" in the Conflict resolution
section of the import wizard view.
6 Review the conflicting objects to see if the new or modified columns appear. The import log is
stored at Siebel\tools\temp\importlog.txt
Applying the DDL
The procedure in the following section describes how to apply the DDL.
To apply the DDL
1 Select the table or tables you want to apply to the physical database and press Apply/DDL button
(option > Apply).
2 For a single table, select the current row option in Tables (Apply Schema Window).
3 For more than one table, select the Choose Current Query option.
4 For the Accessibility project, select the S_ACC_VIEW_APPL table and current row option.
5 Make the following changes depending upon which database you are using:
a For MSSQL, enter the database users, the database user password, and the correct ODBC data
source.
b For Oracle, enter the table space, the index space, the database user, the database user
password, and the correct ODBC data source.
c For IBM DB2, enter the table space, the 16K table space, the 32K table space, the index space,
the database users, the database user password, and the correct ODBC data source.
6 After entering in the database information, click the Apply button.
7 Verify that the required changes have been applied by selecting count(*) from
S_ACC_VIEW_APPL.
The query should result in 0 records.
Importing Seed Data
The procedure in the following section describes how to import seed data.
To import seed data
1 Copy dat files into a work-area folder.
2 Run the following command for importing seed data:
(For HOR applications, use the HOR .dat file.)
siebsrvrroot\BIN\dataimp /u <UID> /p <PWD> /f <HOR DAT file> /l dataimp_HORseed.log /c
<ODBC > /d <TABLEOWNER > /q -1 /e n /t n /x R /n 100 /h log
(For SIA applications, use the SIA .dat file.)
siebsrvrroot\BIN\dataimp /u <UID > /p <PWD> /f <SIA DAT file> /l dataimp_SIAseed.log /c
<ODBC > /d <TABLEOWNER > /q -1 /e n /t n /x R /n 100 /h log
For example:
C:\21011\siebsrvr\BIN\dataimp /u MMRAO /p ****** /f HACR422.dat /l dataimp_ORA21013.log
/c ORA21013 /d ORA21013 /q -1 /e n /t n /x R /n 100 /h log
3 When prompted for the table name, enter S_ACC_VIEW_APPL.
4 Check the log files for any errors, and check S_ACC_VIEW_APPL for the data imported.
68
The following section describes how to import the Accessibility Project .sif files.
To import the .sif files provided for ACR 422
1 Create the Accessibility project and import the .sif.
2 Import AccProject.sif. For a list of files that this .sif contains, see Changes to SIF Files in ACR
422 on page 70.
3 Import AdminScreen.sif and merge the file.
The AdminScreen.sif file contains the modified System Administration Screen. For the list of
changes to this screen, see Changes to SIF Files in ACR 422 on page 70.
4 Add the following new LOV types and values:
5 Add the following views to the application and associate responsibility:
Accessibility Applet Attributes View
Accessibility View Attributes View
6 Run the perl script using the procedures detailed in Step a through Step c.
Note the following prerequisites for running the perl script:
Perl 5.8 or higher (http://www.activestate.com/Products/activeperl/index.mhtml)
Perl module: DBI (http://dbi.perl.org/)
Perl module: XML: Generator (http://search.cpan.org/~bholzman/XML-Generator-1.01/
Generator.pm). Install Perl modules: DBI (DBD::ODBC) and XML::Generator from PPM (Perl
Package Manager).
a Open a command line window and navigate to the folder where the three scripts reside
(genAccessibilityXML.pl, app_tree.pl, sqlstmt.pl).
b Execute the script with the following command:
For all databases, change Oracle in DBI->Connect( ) in app_tree.pl and
genAccessibilityXML.pl to ODBC.
Type Value
ACC_ATTRIB_TYPE Summary
ACC_ATTRIB_TYPE Label
ACC_LOCALE ENU
The following step applies only to the MSSQL database:
After the following lines in app_tree.pl script:
#Connect to DB
#################################################
$dbh = DBI->connect("dbi:ODBC:$ODBCConnection", $userid, $passwd) || die
$DBI::errstr;
#################################################
Add the line $dbh->{odbc_SQL_ROWSET_SIZE} = 2;
Execute the script with the following command:
SYNTAX: perl genAccessibilityXML.pl "<Application Name>" <LOCALE_CODE>
<CONNECTSTRING/TABLEOWNER> <USERID> <PASSWD>
c Once the script is run an xml file will be generated, copy this xml in the following location:
Siebel\ses\siebsrvr\bin\LANG_FOLDER\ folder.
The LANG_FOLDER should be substituted by ENU for English, and so forth.
The name of the XML File should be same as the value mentioned for the Application user
property 'AccessibilityXMLFileName' for that application.
NOTE: The preceding steps help the users provide the summary for a new or a customized
applet. A UI will be created in which the user has to enter the summary for a particular
applet. This in turn will be placed into the xml file that will be generated after the perl script
is run. Users can use this xml file to allow screen readers to read out the applet summary.
Workaround for Accessibility Applets
You must perform the following workaround procedure in order to be able to implement ACR 422.
These changes must be made to the Accessibility Applet Attributes List Applet and the Accessibility
Applet Attributes Form Applet. This workaround has been added to address CR 12-1Q8YZDL, CR 12-
1Q6XXPY, and CR 12-1Q6XXOX.
For both of these applets, use the following procedure:
1 Right-click, and select Applet > Edit Web Layout.
2 In the Controls/Column Pane, select EditList.
3 Uncheck the Show mapped controls only check box.
4 Drag and drop the Position on Row control.
5 Edit the Position on Row controls properties by entering ROW_OFF for HTML Bitmap and
ROW_ON for HTML Disabled Bitmap.
6 Save the applet.
70
7 Drag and drop the GotoPreviousSet and GotoNextSet controls to their respective placeholders,
and edit the properties using the values in the following table:
8 Save the applet.
9 From the drop-down list, select Edit.
10 Drag and drop the Save and Cancel buttons to their respective placeholders.
11 Save the applet.
Changes to SIF Files in ACR 422
This section contains the list of changes to the .sif files provided for ACR 422.
AccProject.sif
The AccProject.sif file contains the following new objects:
Business Components:
Accessibility Applet Attributes
Accessibility View Attributes
Applets:
Accessibility Applet Attributes List Applet
Accessibility Applet Attributes Form Applet
Business Objects:
Views:
Picklists:
Accessibility Applet Attribute PickList
Accessibility View Attribute PickList
Control Property Value
GotoPreviousSet HTMLBitmap RECNAV_PREVSET_ON
GotoPreviousSet HTML Disabled Bitmap RECNAV_PREVSET_OFF
GotoNextSet HTML Bitmap RECNAV_PREVSET_ON
GotoNextSet HTML Disabled Bitmap RECNAV_PREVSET_OFF
Accessibility Locale PickList
Symbolic Strings:
Accessibility
Applet Attributes
Attribute Type
View Attributes
AdminScreen.sif
The AdminScreen.sif file contains the following changes:
Accessibility Attributes (new category)
Accessibility Applet Attributes View (new view)
Accessibility View Attributes View (new view)
This topic contains information about how to configure and install ACR 426.
Before you begin your installation, change a parameter in tools.cfg file within Siebel Tools
(Original: SymStrPrefix = X_) to SymStrPrefix = SBL_
Repository Configurations
1 Navigate to REPPATCH\ ACR426RepSeedFiles_v8113.zip and unzip to any location accessible by
Siebel Tools.
2 In Siebel Tools, lock the following projects:
LS Medical Product Issue
LS Medical Product Issue (SSE)
Contact
Audit Trail
Table ProductComplaints
LS Medical Report
Product
Symbolic Strings
72
Bitmap
EIM ProductComplaints
Applying Schema Changes
As part of the ACR426 release, schema changes have been done on the database. The
Unziplocation\ACR426\Repository\Table\Base\Tables.sif file has all the changes for the following:
ACR 426 contains changes to the following existing table:
S_PRD_CMPLNT_LS
ACR 426 contains the following new table:
S_EMDR_BATCH
Use the following procedure to import tables.
To import the Tables.sif file into the repository
1 Lock the Table ProductComplaints table.
2 Use the Import from Archive function within Siebel Tools to read this file and create the tables in
the repository. Use the merge option while importing this file.
3 The tables have to be in the repository before creating this on the physical database.
4 Within Siebel Tools and query for the list of tables that were imported into the repository.
5 Click the Apply/DLL button to apply the changes to the physical database.
Applying EIM Changes
As part of the ACR426 release, EIM changes have been performed on the database. The
Unziplocation\ACR426\Repository\Table\EIM\EIMTables.sif has all the changes for the following:
EIMTables.sif contains the following new EIM table:
EIM_EMDR_BATCH
EIMTables.sif contains changes to the following existing table:
EIM_PRD_CMP_LS
Use the following procedure to import the EIMTables.sif file into the repository.
To import the EI MTables.sif file into the repository
1 Lock the EIM ProductComplaints project.
2 Use the Import from Archive function within Siebel Tools to read this file and create the tables in
the repository. Use the merge option while importing this file.
3 Within Siebel tools, query for the list of tables that were imported into the repository.
4 Click the Apply/DLL button to apply the changes to the physical database.
Use the following procedure to import all of the SIF files.
NOTE: Use the following option if you want Siebel Tools to merge the changes for all the existing
components as well. However, if you have performed customizations, some user properties may
clash.
To import all of the SI F files
1 Rename Unziplocation\ACR426\REPOSITORY\import.txt to import.bat, edit the file, and change
the first four parameters related to database and Siebel Tools details.
2 Create a log folder in Unziplocation\ACR426\REPOSITORY.
3 Run the import.bat file to import.
4 Check the logs to see if all of the files i mported successfully, and reimport all of the objects that
did not import successfully.
5 In Siebel Tools, compile all of the locked and updated projects.
NOTE: The following procedure is an alternative to importing the SIF files. Use the following
procedure if you want to perform manually configure the existing objects.
To import the SI F files manually
1 Import the following new objects:
Import Unziplocation\ACR426\REPOSITORY\Pick List\LS Medical Picklist Product Issue eMDR
Acknowledgement RR.sif
Batch RR.sif
Status RR.sif
SubStatus RR.sif
Import Unziplocation\ACR426\REPOSITORY\Business Component\LS Medical Product Issue
RR eMDR Batch.sif
Import Unziplocation\ACR426\REPOSITORY\Business Component\LS Medical Product Issue
RR eMDR.sif
Import Unziplocation\ACR426\REPOSITORY\Link\LS Medical Product Issue RR eMDR
Batch_Audit Trail Item 2.sif
Import Unziplocation\ACR426\REPOSITORY\Link\LS Medical Product Issue RR eMDR
Batch_LS Medical Product Issue RR.sif
Import Unziplocation\ACR426\REPOSITORY\Link\LS Medical Product Issue RR_Contact.sif
Import Unziplocation\ACR426\REPOSITORY\Link\LS Medical Product Issue RR_LS Medical
Product Issue RR eMDR Batch.sif
74
Import Unziplocation\ACR426\REPOSITORY\Link \LS Medical Product Issue RR eMDR_LS
Medical Product Issue RR eMDR Batch.sif
Import Unziplocation\ACR426\REPOSITORY\Link \LS Medical Product Issue RR eMDR_Audit
Trail Item 2.sif
Medical PI Product.sif
Medical Product Issue Attachment.sif
Import Unziplocation\ACR426\REPOSITORY\Business Object\LS Medical Product Issue RR
eMDR.sif
Import Unziplocation\ACR426\REPOSITORY\Business Object\LS Medical Product Issue RR
eMDR Batch.sif
Import Unziplocation\ACR426\REPOSITORY\Business
Service\CRMIntegCreatePISEBL782ToAERSSync.sif
Import Unziplocation\ACR426\REPOSITORY\Business Service\Genesis Error Handler.sif
Import Unziplocation\ACR426\REPOSITORY\Business Service\LS Siebel Product Issue.sif
Import Unziplocation\ACR426\REPOSITORY\ Bitmap Category \Urgency Flag Values.sif
Import Unziplocation\ACR426\REPOSITORY \Icon Map\LS_ATTACHMENT.sif
Import Unziplocation\ACR426\REPOSITORY \Icon Map\ LS_CHECK.sif
Import Unziplocation\ACR426\REPOSITORY \Icon Map\ LS_URGENCY_FLAG.sif
Import Unziplocation\ACR426\REPOSITORY\Integration
Objects\CRMIntegSEBLSIALSProductIssueInterface.sif
Object\CRMIntegSEBLSIALSClinicalFaultMessage.sif
Object\CRMIOSEBLSIALSProductIssueInternal.sif
Import Unziplocation\ACR426\REPOSITORY\Applet\LS Medical Product Issue RR eMDR Batch
Details List Applet.sif
List Applet.sif
Pick Applet.sif
Import Unziplocation\ACR426\REPOSITORY\Applet\LS Medical Product Issue RR eMDR
Report List Applet.sif
Import Unziplocation\ACR426\REPOSITORY\View\LS Medical My Product Issues RR eMDR
Batch Audit View.sif
Batch Details View.sif
Report Attachment View.sif
Report Audit View.sif
2 Manually add the following symbolic strings:
Screen
View
New/
Modified? Name
Current String
Value Definition
New SBL_LS_BATCH_# Batch # Batch #
New SBL_LS_BATCH_AUDIT Batch Audit Batch Audit
New SBL_LS_BATCH_DETAILS Batch Details Batch Details
New SBL_LS_EMDR eMDR EMDR
New SBL_LS_EMDR_BATCH eMDR Batch eMDR Batch
New SBL_LS_EMDR_QUEUE eMDR Queue eMDR Queue
New SBL_LS_EMDR_STATUS Transmission Status Transmission Status
New SBL_LS_EMDR_SUB_STATUS eMDR Status eMDR Status
New SBL_LS_FDA_STATUS FDA Status FDA Status
New SBL_LS_INDIVIDUAL_TRANSMIT Individual Transmit Individual Transmit
New SBL_LS_NOT_SELECTED Not Selected Not Selected
New SBL_LS_REPORT_ATTACHMENTS Report Attachments Report Attachments
New SBL_LS_REPORT_AUDIT Report Audit Report Audit
New SBL_LS_TRANSMIT Transmit Transmit
76
3 Do manual configuration for the existing "LS Medical Product Issue RR" Business Component:
Single Value
Fields
New/Needs
Modification? Name Join Column
Calculate
d Value Type
Immediate
Post PickList Validation
No
Copy
New Area LIC LookupNa
me("SR_A
REA",
[Area])
DTYPE_TEXT
New Attach IIf
(Count(At
tachment)
> 0, 1, 0)
DTYPE_BOOL
New Batch Id BATCH_I
D
DTYPE_ID
New Batch
Number
eMDR
Batch
BATCH_
NUMBER
DTYPE_TEXT Y LS Medical
Picklist
Product
Issue
eMDR
Batch RR

New FDA
Acknowl
edgeme
nt
FDA_AC
KNOWLE
DGE_CD
Picklist
Product
Issue
eMDR
Acknowled
gement RR

Modify Device
Age
>0
Modify Follow-
Up
Number
Y
New Follow-
Up
Number
Read
Only
IIF ([Sub
Report
Type] =
LookupVal
ue("LS_M
ED_CMPL
NT_SUB_
REPORT_T
YPE","Foll
ow-up"),
"N", "Y")
DTYPE_BOOL Y
New Individu
al
Transmit
IIf ([Batch
Number]
IS NULL,
1, 0)
DTYPE_BOOL
Modify Parent
Product
Issue
Report
Num
Y
New Patient
Sex LIC
LookupNa
me("FIN_
GENDER",
[Patient
Sex])
DTYPE_TEXT
New Reopen
Flag
[Status]=
LookupVal
ue("LS_M
ED_PI_ST
ATUS_TYP
E","Closed
") OR
[Status]=
LookupVal
ue("LS_M
ED_PI_ST
ATUS_TYP
E","Revie
w
Complete"
)
DTYPE_TEXT
Modify Report
Number
Y
Modify Sub
Report
Type
Y
Modify Type of
Report -
Follow-
up Flag
Y
New Urgency
Flag
IIF (
[eMDR
Status] =
'Transmitt
ed' AND
[eMDR
SubStatus
] <>
'Rejected'
, Green,
IIF(
(Today()
+
SystemPr
eference("
eMDR
Deadline
Threshold
Value")) <
[Report
Deadline
Date],
Yellow,
Red))
DTYPE_TEXT
New eMDR
Status
EMDR_S
TATUS_C
D
Picklist
Product
Issue
eMDR
Status RR

New eMDR
SubStat
us
EMDR_S
UB_STAT
US_CD
Picklist
Product
Issue
eMDR
SubStatus
RR

Single Value
Fields
New/Needs
Modification? Name Join Column
Calculate
d Value Type
Immediate
Post PickList Validation
No
Copy
78
Pick Maps for the Batch Number Field
New/Modified? Field Picklist Field
New Batch Id Id
New Batch Number Batch Number
Pick Maps for the FDA Acknowledgement
Field
New FDA Acknowledgement Value
Pick Maps for the eMDR Status Field
New eMDR Status Value
Pick Maps for the eMDR Substatus Field
New eMDR SubStatus Value
Join
New/Needs Modification? Table Alias Outer Join Flag
New S_EMDR_BATCH eMDR Batch Yes
Join Specification for 'eMDR Batch'
New/Needs Modification? Name Source Field Destination Column
New Join Batch Id ROW_ID
Multi Value
Link
New/Needs
Modification? Name Auto Primary
Destination
Business
Component Destination Link
Use
Primary
Join
New Attachment Default LS Medical
Product Issue
Attachment
LS Medical Product Issue RR/
LS Medical Product Issue
Attachment
Y
Business
Component
User
Properties
New/
Modified? Name Value Inactive
New Field Read Only Field:
Follow-Up Number
Follow-Up Number Read Only N
New Named Method 8 "EscalatePIToeMDRQueue", "SET", "RR
Sub-Status",
"LookupValue('LS_MED_RR_STATUS_CD',
'eMDR')
"N
New Named Method 9 "Transmit", "INVOKESVC", "LS Medical
Product Issue RR", "Workflow Process
Manager", "RunProcess", "'ProcessName'",
"LS
CRMIntegSEBLSIAProductIssueInsertOutbo
undFlow", "'RowId'", "[Id]
"N
New Named Method 10 "Transmit", "SET", "eMDR Status",
"LookupValue('LS_MED_RR_TRANS_STATU
S', 'TRANSMITTED')
"N
New Named Method 11 "Transmit", "SET", "eMDR SubStatus",
"LookupValue('LS_MED_RR_TRANS_SUB_S
TATUS', 'NO RESPONSE')
"N
New Named Method 12 "UpdateeMDRStatus", "SET", "eMDR
Status",
"LookupValue('LS_MED_RR_TRANS_STATU
S', 'TRANSMITTED')
"N
New Named Method 13 "UpdateeMDRStatus", "SET", "eMDR
SubStatus",
"LookupValue('LS_MED_RR_TRANS_SUB_S
TATUS', 'NO RESPONSE')
"N
New Named Method 14 "EscalatePIToeMDRQueue", "SET", "eMDR
Status", "IIf ([eMDR Status] IS NULL,
LookupValue('LS_MED_RR_TRANS_STATUS
', 'NOT TRANSMITTED'), [eMDR Status])
"N
New Named Method 15 "EscalatePIToeMDRQueue", "SET", "eMDR
SubStatus", "IIf ([eMDR SubStatus] IS
NULL,
LookupValue('LS_MED_RR_TRANS_SUB_S
TATUS', 'WORK IN PROGRESS'), [eMDR
SubStatus])
"N
80
New Named Method 16 "Transmit", "SET", "FDA
Acknowledgement",
""""N
New Named Method 17 "UpdateeMDRStatus", "SET", "FDA
Acknowledgement",
""""N
New On Field Update Set 3 "Sub Report Type", "Follow-Up Number
Read Only", "IIF ([Sub Report Type] =
LookupValue(""LS_MED_CMPLNT_SUB_REP
ORT_TYPE"",""Follow-up""), ""N"", ""Y"")
"N
New On Field Update Set 4 "Sub Report Type", "Follow-Up Number",
"IIF ([Sub Report Type] =
LookupValue(""LS_MED_CMPLNT_SUB_REP
ORT_TYPE"",""Initial""), """", [Follow-Up
Number])
"N
New On Field Update Set 5 "Type of Report - Follow-up Flag", "Sub
Report Type", "IIF ([Type of Report - Follow-
up Flag]='Y',
LookupValue('LS_MED_CMPLNT_SUB_REP
ORT_TYPE','Follow-up'),
LookupValue('LS_MED_CMPLNT_SUB_REP
ORT_TYPE','Initial'))
"N
New Status Locked Field 6 "eMDR Status", ""N
New Status Locked Field 7 "eMDR SubStatus", ""N
New Status Locked Field 8 "FDA Acknowledgement", ""N
Modify Status Locked Field 2 "RR Status", "Submitted "N
Business
Component
User
Properties
New/
Modified? Name Value Inactive
4 Perform manual configuration for the "LS Medical Product Issue" Business Component:
5 Perform manual configuration for the existing "Contact" Business Component.
Single
Value
Fields
New/
Needs
Modific
ation? Name Join Column
Calcul
ated
Value Type
Immediate
Post PickList
Validati
on No Copy
New Area
LIC
Lookup
Name("
SR_ARE
A",
[Area])
DTYPE_TEXT
Modify FDA
Reporta
ble
Y
New Patient
Sex LIC
Lookup
Name("
FIN_GE
NDER",
[Patient
Sex])
DTYPE_TEXT
New Sub-
Area
LIC
Lookup
Name("
SR_ARE
A",
[Sub-
Area])
DTYPE_TEXT
Single
Value
Fields
New/
Needs
Modificat
ion? Name
Joi
n
Colu
mn
Calculated
Value Type
Imm
edia
te
Post PickList Validation No Copy
New Country
LIC
LookupName(
"COUNTRY",[
Country])
DTYPE_
TEXT

82
6 Perform manual configuration for the existing "LS Medical Product Issue RR" Business Object:
7 Perform manual configuration for the existing "Audit Trail Engine" Business Service:
8 Perform manual configuration for the existing "Field Value Icons" Bitmap Category:
Business Object
Component
New/Modified? Business Component Link
New Contact LS Medical Product Issue RR/
Contact
New LS Medical Product Issue RR
eMDR Batch
LS Medical Product Issue RR/
LS Medical Product Issue RR
eMDR Batch
Business Service
User Props
New/Needs
Modification? Name Value Comment
Modify Enable TRUE 12-CBU9V3: turned
OFF on default for
performance reasons
Bitmaps
New/Modified? Name FileName
Alt Text String
Reference Alt Text
New uncheck.gif uncheck.gif SBL_LS_NOT_SE
LECTED
Not Selected
9 Perform manual configuration for the existing "LS Medical Product Issue RR Form Applet" Applet:
Control
New/
Modified? Name Caption Caption String HTML Type
HTML
Only
New/Modify Name Caption Caption String HTML Type HTML
Only
Method
Invoked
New eMDRQueue eMDR Queue SBL_LS_EMDR_
QUEUE
MiniButtonEditN
ew
Y EscalatePIToeM
DRQueue
Applet Web
Template (Existing
and Modify) Name Type Web Template
Modify Edit Edit Applet Form Grid
Layout
Applet Web
Template Items
New/Needs
Modification? Name Control Comments
New eMDRQueue eMDRQueue In Edit Web Layout,
drag and drop this
control from Controls/
Columns onto the
layout
Applet User Properties
New/Needs Modification Name Value
New CanInvokeMethod:
EscalatePIToeMDRQueue
([RR Sub-Status] <> 'eMDR'
OR [RR Sub-Status] IS NULL)
AND [RR Status] =
'Submitted'
84
10 Perform manual configuration for the existing "LS Medical Product Issue RR Child List Applet"
Applet:
List Columns
New/Needs
Modification Name Field
Display Name -
String
Reference Read Only HTML Icon Map
New FDA Status FDA
Acknowledgeme
nt
SBL_LS_FDA_ST
ATUS
Y
New Flag Urgency Flag SBL_FLAG-
1004224902-
05I
LS_URGENCY_FLAG
New eMDR Status eMDR Status SBL_LS_EMDR_
STATUS
Y
New eMDR SubStatus eMDR SubStatus SBL_LS_EMDR_
SUB_STATUS
Y
Applet Web
Template (Existing
and Modify)
New/Modify Name Type Web Template
Modify Edit List Edit List Applet List (Base/
EditList)
Applet Web
Template Items
New/Modify Name Fields Comments
New FDA Status FDA Status In Edit Web Layout,
drag and drop this
List Column from
Controls/Columns
onto the layout
New Flag Flag In Edit Web Layout,
drag and drop this
List Column from
Controls/Columns
onto the layout
11 Perform manual configuration for the existing "LS Medical Product Issues RR Screen" Screen:
New eMDR Status eMDR Status In Edit Web Layout,
drag and drop this
List Column from
Controls/Columns
onto the layout
New eMDR SubStatus eMDR SubStatus In Edit Web Layout,
drag and drop this
List Column from
Controls/Columns
onto the layout
Screen
View
New/
Needs
Modificat
ion? Name
Category
Name View Type
Parent
Category
View Bar Text -
String
Reference
Menu Text String
Reference
New LS
Medical
My
Product
Issues RR
eMDR
Batch
Audit
View
LS
Medical
My
Produc
t
Issues
RR
eMDR
Batch
Audit
View
Detail
View
eMDR
Batch
SBL_LS_BATCH_
AUDIT
SBL_LS_BATCH_AUDIT
New LS
Medical
My
Product
Issues RR
eMDR
Batch
Details
View
LS
Medical
My
Produc
t
Issues
RR
eMDR
Batch
Details
View
Detail
View
eMDR
Batch
SBL_LS_BATCH_
DETAILS
SBL_LS_BATCH_DETAIL
S
Applet Web
Template Items
New/Modify Name Fields Comments
86
Importing Seed Data
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 DevelopmentDB)
d Enter the server name to connect to:
e For Oracle, enter the TNS service name that you created to connect Siebel Tools to the database.
f Test your connection and click OK when tested successfully.
2 Before executing the next step, make sure that the dataimp.exe file exists in the <Tools Install
Directory>/bin directory.
New LS
Medical
My
Product
Issues RR
eMDR
Report
Attachme
nt View
LS
Medical
My
Produc
t
Issues
RR
eMDR
Report
Attach
ment
View
Detail
View
eMDR SBL_LS_REPORT
_ATTACHMENTS
SBL_LS_REPORT_ATTAC
HMENTS
New eMDR eMDR Aggregate
Category
SBL_LS_EMDR SBL_LS_EMDR
New eMDR
Batch
eMDR
Batch
Aggregate
Category
SBL_LS_EMDR_B
ATCH
SBL_LS_EMDR_BATCH
Screen
View
New/
Needs
Modificat
ion? Name
Category
Name View Type
Parent
Category
View Bar Text -
String
Reference
Menu Text String
Reference
3 Run the following command:
<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f
Unziplocation\ACR426\SEED_DATA\ACR426_Seed.dat /l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i
Unziplocation\ACR426\SEED_DATA\ ACR426_SeedInp\<Database Platform>\ACR426_seed.inp
/q -1 /w y /e n /t n /x R /n 100 /h log
<Tools Install Directory> - Replace with your Siebel Tools install directory
<ODBC Source Name> - Replace with the relevant ODBC name
<Database Platform> - Replace with your database platform (ORACLE, DB2UDB or MSSQL)
4 Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
Seed data import includes mono-language seed data import and language seed-data import. Use
either Step 5 or Step 6 depending upon the language that you are installing.
5 Use the following procedure to import ENU language seed data:
a Run the following command after importing the ACR426_Seed.dat file.
Unziplocation\ACR426\SEED_DATA\ACR426_Seed_Locale_ENU.dat /l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i
Unziplocation\ACR426\SEED_DATA\ ACR426_SeedInp\<Database
Platform>\ACR426_Seed_Locale_ENU.inp /q -1 /w y /e n /t n /x R /n 100 /h log
<ODBC Source Name> - Replace with the relevant ODBC name
b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure import completed
successfully
6 Use the following procedure to import languages other than ENU:
a Run the following command after importing ACR426_Seed.dat file for importing the locale
specific ACR426_Seed_Locale_XXX.dat, where XXX is the language code.
Unziplocation\ACR426\SEED_DATA\LMU\XXX\ACR426_Seed_Locale_XXX.dat /l <Tools
Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q -
1 /w n /e y /t n /x R /n 100 /h log
b <Tools Install Directory> - Replace with your Siebel Tools install directory
c <ODBC Source Name> - Replace with the relevant ODBC name
88
Importing Web Services Definitions
Use the following procedure to import Web services definitions.
To import Web services definitions
1 Log into the Siebel application.
2 Navigate to the Administration - Web Services > Outbound Web Services view.
3 Import the LSeMDRTransmitFDA.XML file. (This file is located in
\ApplicationChanges\WebServices folder within the extracted zip file.)
4 Query for the LSeMDRTransmitFDA Web service.
5 On the Service Port applet, update the address to point to your BPEL server location. By default,
it looks like http://localhost:8888/orabpel/default/LSeMDRTransmitFDA/1.0, so change the
localhost to the SOA host name and change 8888 to the proper port number.
7 Navigate to the Administration - Web Services > Inbound Web Services view.
8 Import the LSUpdateeMDRProductIssueStatus.XML file. (The file is located in the
\ApplicationChanges\WebServices folder within the extracted zip file.)
9 Query for the LSUpdateeMDRProductIssueStatus Web service.
10 On the Service Ports applet, update the address to point to your Siebel server location. By
default, it will look like http://sdc78212/eai_enu/
start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&UserName=harikuma&Password
=harikuma by default, so change the host name, user name, and password values.
For more information about inbound Web services, refer to the sample acknowledgement
message: Unziplocation\ACR426\Sample\LSUpdateeMDRProductIssueStatus Sample Input.xml
Importing Workflow Definitions
Use the following procedure to import workflow definitions.
XML File to Import Web Service Name Direction
LSeMDRTransmitFDS.xml LSeMDRTransmitFDA Outbound
LSUpdateeMDRProductIssueStatus.XML LSUpdateeMDRProductIssueStatus Inbound
To import workflow definitions
1 Log into Siebel Tools.
NOTE: NOTE: Siebel Tools must be connected to the same database that the Siebel application
server is connected to.
2 From Object Explorer, navigate to Workflow Process.
3 From the list applet, right-click and choose Import Workflow Process.
4 Browse to Unziplocation\ACR426\REPOSITORY\Workflows, and choose LS
CRMIntegSEBLSIAProductIssueInsertOutboundFlow.xml.
5 After import, query for the LS CRMIntegSEBLSIAProductIssueInsertOutboundFlow workflow
process.
6 Withink Lock Projects view > Workflow process, focus on the record and then click the Deploy
button on top of the applet to deploy the workflows.
7 Repeat the preceding steps for the LS Siebel PI eMDR Batch workflow.
Activating Workflow Definitions
Use the following procedure to activate workflow definitions.
To activate workflow definitions
2 Navigate to the Administration - Business Process > Workflow Deployment view.
3 On the Repository Workflow Processes applet, query for the LS
CRMIntegSEBLSIAProductIssueInsertOutboundFlow and LS Siebel PI eMDR Batch workflows,
focus on each record and click the Activate button to activate the workflow.
Adding System Preferences
Use the following procedure to add system preferences.
To add system preferences
1 In the Site Map, navigate to Application Administration > System Preferences.
2 Create a new record with the following details:
XML File to Import Workflow Name Project
LS
CRMIntegSEBLSIAProductIssueInsertOut
boundFlow.xml
LS
CRMIntegSEBLSIAProductIssueInsertO
utboundFlow
LS eMDR
LS Siebel PI eMDR Batch.xml LS Siebel PI eMDR Batch LS eMDR
90
System Preference Name: eMDR Deadline Threshold Value
System Preference Value: 7
Description: The value is the number of days before the regulatory report deadline, and the
system should highlight this value for the users. The urgency is indicated by having the
urgency flag in the eMDR list turn from yellow to red.
To enable Component Groups
Make sure that EAI Component Group is enabled. If it is not, enable it and bounce the Siebel
Server.
BPEL (Middle Tier) Setup
The procedures in the following topic describe how to install Fusion Middleware software and how to
set up Canonical Objects.
NOTE: Enhancements are required in the BPEL processes delivered to integrate with FDA.
For Outbound Web services, the Siebel message is transformed to an HL7 message using the
following transformation XSL:
Unziplocation\ACR426\BusinessProcesses\RegulatoryReport\LSeMDRTransmitFDA\bpel\
FDAAcceptanceFormat.xsl and written to a XML file.
Enhancements are required to send this xml file to FDA.
For Inbound Web services, a sample schema
(Unziplocation\ACR426\BusinessProcesses\RegulatoryReport\ eMDRUpdateFDAAck\bpel\
sample1.xsd) is used to capture data from BPEL console and the same is transformed to siebel
schema using following XSL Unziplocation\ACR426\BusinessProcesses\RegulatoryReport\
eMDRUpdateFDAAck\bpel\Transformation_1.xsl.
The Web service supports the same schema for all the three acknowledgements. Customization is
required to transform the MDN message received from FDA for the first two acknowledgements to
The Siebel schema and call the Web service.
Installing Fusion Middleware Software
Use the following procedure to install Fusion Middleware software.
To install Fusion Middlware components
Install the following Fusion Middleware components:
SOA Suite 10g 10.1.3.1
For information on installing Oracle SOA Suite, refer to the Oracle Application Server
Documentation Library. The library is available on Oracle Technology Network (OTN) at http:/
/www.oracle.com/technology/documentation/index.html. To access the documentation, click
the Oracle Application Server 10g Release 3 (10.1.3.1) link.
Oracle JDeveloper 10.1.3.1 (Studio Version)
If desired, support for JDeveloper can be purchased separately. For information on installing
Oracle JDeveloper, refer to OTN at http://www.oracle.com/technology/documentation/
index.html.
Setting Up Canonical Objects
Canonical Objects are useful in error handling for both business logic and runtime errors.
Use the following procedure to set up Canonical Objects.
To set up canonical obj ects
1 Copy the following folder: Unziplocation\ACR426\BusinessProcesses\xmllib\ SEBLLSeMDRFDA
and place it into the xmllib folder for your SOA installation (such as:
<SOA_HOME>\bpel\system\xmllib).
2 Verify that the schema can be accessed by opening a browser and typing in the following URL:
http://<SOA Host Name:BPEL Console port number>/orabpel/xmllib/ SEBLLSeMDRFDA /
CanonicalObjects/coCommon.xsd
For example: http://127.0.0.1:8888/orabpel/xmllib/SEBLLSeMDRFDA/CanonicalObjects/
coCommon.xsd
The CoCommon schema should open correctly. If there is a problem in opening the file, restart
the SOA suite.
Configuring Business Processes Execution Language Processes
Use the following procedure to configure BPEL processes.
To configure BPEL processes
1 Open the following file for editing:
Unziplocation\ACR426\SetUp\CRMIntegProcessParameters.xml.
92
2 Modify its content until it matches the following:
NOTE: Change the values in the lines that begin with "<property name="PARAMVALUE">.
Replace the values with the relevant values from your environment.
<?xml version="1.0" encoding="UTF-8" ?>
<LISTOFBUILDPARAMETERS xmlns="http://www.siebel.com/uan/SiebelBIAs/
SharedComponents/CRMIntegProcessProperties">
<BUILDPARAMETER>
<property name="PARAMNAME">http://sdc78212svod:8888/orabpel/default</property>
<property name="PARAMVALUE">http://127.0.0.1:8888/orabpel/default</property>
<property name="DESC">This Parameter is to capture BPEL domain URL information.Please
specify your environment specific value for "PARAMVALUE" property. Here
"http://127.0.0.1:8888" should be replaced with the HOST, PORT where the BPEL PM is running.
"orabpel" should stay same.
"default" is the name of domain where the bpel processes are to be deployed.</property>
</BUILDPARAMETER>
<BUILDPARAMETER>
<property name="PARAMNAME">http://sdc78212svod:8888/orabpel/xmllib</property>
<property name="PARAMVALUE">http://127.0.0.1:8888/orabpel/xmllib</property>
<property name="DESC">This Parameter is to capture the XMLLIB url. Please specify your
environment specific value for "PARAMVALUE" property.
Here "http://127.0.0.1:8888" should be replaced with the HOST, PORT where the BPEL PM is
running. "orabpel/xmllib" should stay same.</property>
</BUILDPARAMETER>
<BUILDPARAMETER>
<property name="PARAMNAME">"http://sdc78212svod/eai_enu/
start.swe?SWEExtSource=WebService;SWEExtCmd=Execute;UserName=harikuma;Password=
harikuma"</property>
<property name="PARAMVALUE">[SIEBEL SERVER LOCATION]</property>
<property name="DESC">This Parameter is to capture the Siebel server url. Specify your
environment-specific value for "PARAMVALUE" property (such as http://xyz.siebel.com:8888</
property>
</BUILDPARAMETER>
<BUILDPARAMETER>
<property name="PARAMNAME">"c:\temp"</property>
<property name="PARAMVALUE">"c:\test"</property>
<property name="DESC">Ouput Directory where FDA eMDR XML files will be created </
property>
</BUILDPARAMETER>
</LISTOFBUILDPARAMETERS>
3 After you have changed the parameter values, navigate to Unziplocation\ACR426\SetUp\scripts
and run the following command for the BPEL projects in the Compound project:
j ava - j ar Edi t Par am. j ar - i Unzi pl ocat i on\ ACR426\ Busi nessPr ocesses - f
Unzi pl ocat i on\ ACR426\ Set up\ CRMI nt egPr ocessPar amet er s. xml - ver bose - t D: \ t emp
Use the following procedure to set the output directory for storing FDA Report XML files.
To set the output directory for storing the FDA report XML files
1 Navigate to Unziplocation\ACR426\BusinessProcesses\
RegulatoryReport\LSeMDRTransmitFDA\bpel, and edit WriteIntoFile.wsdl.
2 Locate "PhysicalDirectory="c:\temp"", and replace the value to the relevant value
3 Locate "FileNamingConvention="FDAReport.xml"" and replace the value to relevant value, such
as 'FDA_%yyMMddHHmmss%.xml'.
Setting Up an Application Workspace
Use the following procedure to set up an application workspace.
To set up an application workspace
1 Start Oracle JDeveloper.
2 Click the Applications Navigator tab.
3 Right-click the Applications icon.
4 Choose New and specify the type as Application.
5 Specify eMDR as the name for the application.
6 Specify a directory name where the BPEL processes are stored (for
example:Unziplocation\ACR426\BusinessProcesses).
7 In the Create Project popup, click Cancel.
8 Repeat the following steps for each of the following JPR files:
Unziplocation\ACR426\BusinessProcesses\RegulatoryReport\eMDRUpdateFDAAck\eMDRUpdat
eFDAAck.jpr
Unziplocation\ACR426\BusinessProcesses\RegulatoryReport
\LSeMDRTransmitFDA\LSeMDRTransmitFDA.jpr
a Select the eMDR application.
b Right-click and choose Add to eMDR.jws.
94
c Select a JPR file and click Open.
This imports the process code into the application.
Deploying Business Process Execution Language
Use the following procedure to deploy BPEL processes.
NOTE: Before you begin, make sure that the SOA Suite has been installed, and make sure
JDeveloper has been installed and that the application server and integration server connection have
been configured.
To deploy BPEL processes
1 Make sure that the SOA Suite has been started.
2 From Oracle JDeveloper, select the LSeMDRTransmitFDA project.
3 Right-click on the project name and choose Deploy > IntegrationServerName > Deploy to default
domain.
4 Ignore the warnings listed on the build output window.
5 Select the eMDRUpdateFDAAck project.
6 Right-click on the project name and choose Deploy > IntegrationServerName > Deploy to default
domain.
7 Ignore the warnings listed on the build output window.
This compiles the SRC code and then deploys the BPEL process to the SOA Instance.
1 Go to the Siebel Tools installation directory <Tools Install Directory>\REPPATCH.
2 Unzip the file ACR437.zip file.
This will create the following directory structure:
<Path of the Unzipped Folder>\REPPATCH\
The above ACR437 folder will have the following subfolders:
\DMGSchemaChanges (refer to the information about how to import .sif files in Siebel CRM
and UCM Integration Guide on My Oracle Support.
\LMU
\SeedData (refer to the information about how to import seed data in Siebel CRM and UCM
Integration Guide on My Oracle Support.
\SIFFiles
WFs
As part of the O2C release, schema changes have been made within the database. The
O2CMST80_S_USER.sif, VACR437_EIMFinal_81.sif and VACR437_TableFinal_81.sif files all
contain changes, and the S_USER table has been changed as well.
More Information
See Siebel CRM and UCM Integration Guide on My Oracle Support (Article ID 763962.1) for
information about the following topics:
How to import .sif files into the repository
How to create tables on the physical database
How to import seed data
How to set up the workflow policy
How to create a job for the Generate Triggers component
How to reveal the Default Tasks parameter
How to start tasks for Workflow Monitor Agent
How to set up the integration user.
This topic is part of Configuration Instructions for Enhancements and Updates on page 44.
After installing ACR 439, you must make sure that Find objects are visible in the application.
To make sure that Find obj ects are visible in the application
2 Select the application from Object Explorer, and search for the relevant Application Name.
3 Navigate to Application Find in the Object Explorer, and activate the Find names that you want
to display for the application.
4 Make sure that the relevant Business Components are part of the Search Execution Business
Object.
5 Compile your changes to the SRF.
You may receive the following error message after you have installed ACR 439: An error has
occurred creating business component Consumer used by business object Search Execution.
Please ask your systems administrator to check your application configuration. (SBL-DAT-00222).
Use the following procedure to resolve this error.
96
To resolve the SBL- DAT- 00222 error message
2 Within the Object Explorer, select Business Object.
3 Query for Search Execution, right-click the access the submenu, and select Unlock Object.
4 Navigate to the Object Business Component.
5 Click New Record and add the required Business Component (such as Consumer).
6 Compile the changes to the SRF.
For more information about ACR 439 and for information about how to implement this enhancement,
see Siebel Search Administration Guide on the Siebel Bookshelf, available on Oracle Technology
Network (OTN) at http://www.oracle.com/technology/documentation/siebel.html.
Instructions for ACR 439B
The following sections contain information about how to configure and install ACR 439B.
Importing SIF Files for ACR 439B
Use the following procedure to import the .sif files for ACR 439B.
To import the .sif files for ACR 439B
2 Navigate to the Fast Search project and lock it.
3 Uncompress the file ACR439_sif.zip file, which is located under Tools\REPPATCH.
4 Import the .sif files you extracted from the .zip file.
5 Compile the project.
Importing the sif files creates the following objects:
Applet: Search lookin Results Body, Search lookin Results Header, Recent Saved Searches Applet
View: Search lookin Results View
Web Template: Lookin Results View
Screen: Search View Dummy Screen
Siebel Tools Changes for ACR 439B
NOTE: Lock the Fast Search project before performing the changes detailed in this section.
To add the GotoView=Search lookin Results view
2 Within Applet Search lookin Results Header, add the user property GotoView= Search lookin
Results View.
3 Compile the project.
To add the SamePage and GotoView user properties to the Search lookin applet
2 Query for the Search lookin applet.
3 Navigate to Applet User Prop and add the two user properties listed in the following table:
4 Navigate to Control, query for Name= "Search", and update the Search property as detailed in
the following table:
To add the GotoView user property to the Search Results Body applet
2 Query for the Search Results Body applet.
3 Navigate to Applet User Prop and add the following user property:
4 Navigate to Control, query for Name = "PositionOnRow", and update the following property:
Name Value Description
SamePage TRUE/ FALSE Having this value set to TRUE displays the
Search Results on the left hand side of the
screen.
GotoResultsView Search lookin Results View Search lookin Results View
Name Target View Frame Description
Search empty The old value is "_sweview". The property needs to be set to
empty.
Name Value Description
GotoResultsView Search lookin Results View
HTML Bitmap HTML Disabled Bitmap
ROW_OFF ROW_ON
98
5 Navigate to Applet Web Template Items and add the item detailed below:
Seed Data Changes for ACR 439B
Use the following procedure to add the Search lookin Results view.
To add the Search lookin Results View
1 Navigate to the Administration - Application screen, and then the Views view.
2 Click New and add "Search lookin Results View" with the following values:
View Name = "Search lookin Results View"
Description = "Search lookin Results View"
Default Local Access = "true"
3 To give the administrator responsibility to the view, navigate to the Administration - Application
screen, and then the Responsibilities view. Query for the administrator.
4 In the view applet, add "Search lookin Results View".
SWT Changes for ACR 439B
Siebel Web Templates (SWT) are a set of HTML files with embedded Siebel tags that determine how
the UI is rendered in a browser. The following SWT files need to be edited for ACR 439B:
Search_ListBodySearchResults.swt
SearchResults.swt
SavedSearch.swt
Apply the changes listed below for each swt in order for ACR 439B to display the web templates
correctly.
To edit Search_ ListBodySearchResults.swt
1 Place the text below between this line:
<! - - - - - - - - - - - - Begi n Row - - - - - - - - - - - - - >
and this line:
<! - - - - - - - - - - - - Di spl ay al l Sear ch Resul t Fi el d - - - - - - - - - - - - - >
2 Insert the following text:
<t r cl ass=" swe: t hi s. RowSt yl e" >
Item Identifier Name Control Parent Name Type
501 PositionOnRow PositionOnRow Base Control
<swe: cont r ol i d=" 501" ><! - - Sel ect 501 - - ><t d al i gn=" swe: t hi s. Text Al i gnment "
wi dt h=" 42" cl ass=" Row" ><swe: t hi s pr oper t y=" For mat t edHt ml " hi nt Text =" Sel ect ed Row"
hi nt MapType=" Cont r ol " / ></ t d></ swe: cont r ol >
<swe: sel ect - r ow><t d al i gn=" swe: t hi s. Text Al i gnment " wi dt h=" 42" cl ass=" Row" ><swe: t hi s
pr oper t y=" For mat t edHt ml " / ></ t d></ swe: sel ect - r ow>
To edit SearchResults.swt
Place the following text after the line </b> for id ="3000":

<b>
<swe: cont r ol i d=" 3001" > <! - - CR 12- 1O4OT68 - - >
<swe: t hi s pr oper t y=" For mat t edHt ml " hi nt MapType=" Cont r ol " hi nt Text =" At t ach" / >
</ swe: cont r ol >
</ b>
<b>
<swe: cont r ol i d=" 3002" > <! - - CR 12- 1O4OT91 - - >
<swe: t hi s pr oper t y=" For mat t edHt ml " hi nt MapType=" Cont r ol " hi nt Text =" Pr evi ew" / >
</ swe: cont r ol >
</ b>
To edit SavedSearch.swt
Place the following text after the line </tr> for id="99":
<! - - Begi n of CR 12- 1O4OTAF - - >
<t r >
<t d al i gn=" l ef t " >
<swe: cont r ol i d=" 101" >
<b><swe: t hi s pr oper t y=" For mat t edHt ml " hi nt MapType=" Cont r ol " hi nt Text =" Fi el d" / ></ b>
</ swe: cont r ol >
</ t d>
</ t r >
<t r >
<t d al i gn=" l ef t " >&nbsp</ t d>
100
</ t r >
<! - - End of CR 12- 1O4OTAF - - >
Knowledge tab and search for Article ID 880612.1.
For more information about the Siebel Hospitality application, see Siebel Hospitality Guide on the
Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.
Use the following procedure to install ACR 452 for the Siebel 8.1.1.1 Fix Pack.
NOTE: Oracle Secure Enterprise Search patch 10.1.8.4 or higher is required for ACR 452.
To install ACR 452
Extract the Tools\REPPATCH\ ACR452_phaseA.zip file to Tools\REPPATCH.
This creates the following directory structure: Tools\REPPATCH\ACR452_phaseA\.
To import ACR 452 seed data
1 Open Tools\REPPATCH\ACR452_phaseA\SEED_DATA\ import.bat and edit the required
import.bat parameters, using the following as an example:
SET TOOLSPATH= <Enter Tools path here>
SET DATASRC= <Enter Source name used by Siebel Tools for ODBC DSN. The value is the
same as that used for ConnectString in the [ServerDataSrc] section of Tools.cfg>
SET TBLOWNER=<Enter table owner name used by Siebel Tools for connecting to the server
database. The value is the same as that used for TableOwner in the [ServerDataSrc] section
of Tools.cfg>
SET USERNAME=<Enter the username used to connect to the Siebel database, such as
SADMIN>
SET PASSWORD=<Enter the password used to connect to the Siebel database, such as
SADMIN>
2 Run import.bat.
To edit Tools.cfg to import symbolic strings
1 Open Tools.cfg, search for the SymStrPrefix parameter, and change the value of the SymStrPrefix
parameter from X_ to SBL_.
2 Within Siebel Tools, lock the following Search projects:
Fast Search
Search Execution
Symbolic Strings
To import ACR 452.sif
1 Open Tools\REPPATCH\ACR452_phaseA\repository\import.bat, and edit the required import.bat
parameters, using the following as an example:
SET PCDTOOLSPATH= <Enter Tools path here>
SET PCDDATASRC= <Enter DataSrc name used by Tools.cfg. The value is the same as
[ServerDataSrc] in the Tools.cfg>
SET PCDUSERNAME=<Enter the username used to connect to the Siebel database, such as
SADMIN>
SET PCDPASSWORD==<Enter the password used to connect to the Siebel database, such as
SADMIN>
SET LANG==<Enter language code, such as ENU>
2 Run import.bat
3 In Siebel Tools, import the Tools\REPPATCH\ACR452_phaseA\Business Component.sif file.
To install localization files
1 (Optional) The following step only applies only to customers who are installing languages other
than ENU. If you are installing languages other than ENU:
a Navigate to Tools > Utilities > Locale Management to import LMU files for the specific language
from the Tools\REPPATCH_ACR452_phaseA\LMU folder into Siebel Tools.
b Select Source Language = English American
c Target Language = <Select Language>
d Click the Import tab, click Browse to locate the LMU file you want to import, and then click
Import.
2 Stop the Siebel Server, if it is running.
3 To change the language to the specific language that you just imported, navigate to View >
Options > Language.
To compile and save the Siebel Tools changes
1 Within Siebel Tools, navigate to Compile Projects, select all projects, and then click Compile.
102
2 Save the srf file
3 Within Siebel Tools, unlock the following Search projects:
Fast Search
Search Execution
Symbolic Strings
To edit Tools.cfg for customer changes
Open Tools.cfg, search for the SymStrPrefix parameter, and change the value of the SymStrPrefix
parameter from SBL_ to X_.
To install the AdvancedSearch SWT file
1 On the Siebel Sever, replace the \ses\siebsrvr\WEBTEMPL\AdvancedSearch.swt file with the
Tools\REPPATCH\ACR452_phaseA\repository\Web Template\ AdvancedSearch.swt file .
2 Start the Siebel Server.
3 Navigate to Administration Search > Search Engine Settings to confirm that the Connect and
Disconnect buttons have been added.
For information on installing Search_Engine_Config.xml, and configuring Search for ACR 452, see
the Siebel Search Administration Guide on the Siebel Bookshelf at http://www.oracle.com/technology/
documentation/siebel.html.
Use the instructions in this topic to implement ACR 456, which provides a user interface for exporting
and importing assignment-related data.
For more information about the enhancements provided by ACR 456 for version 8.1.1.1 and later,
see Siebel Assignment Manager Administration Guide. The latest version of this gui de is available on
the Siebel 8.1 Bookshelf on OTN at http://www.oracle.com/technology/documentation/siebel.html.
Importing Archive Files for ACR 456
To implement this ACR, you must import archive files (.sif) in Siebel Tools.
1 On the machine where you installed Siebel Tools, locate the file ACR456.zip in the folder
SIEBEL_TOOLS_ROOT\REPPATCH.
2 Uncompress this .zip file and extract the archive files (.sif) it contains.
3 Navigate to SIEBEL_TOOLS_ROOT\bin\enu.
4 Open the file tools.cfg in an editor like Notepad.
5 Change the value of the SymStrPrefix parameter to SBL_. (After performing the steps described
in this topic, change this parameter back to its original value of X_.) Save the tools.cfg file.
6 Launch Siebel Tools.
7 Lock the following projects:
Symbolic Strings
Assignment
Orgchart
Admin
8 Import the archive files (.sif) you previously extracted from ACR456.zip into Siebel Tools. Import
the files in the order shown below:
AM-ImportExport.sif
AM-ImportExport-SymbolicStrings.sif
AM-ImportExport-applet.sif
AM-ImportExport-buscomp.sif
AM-ImportExport-screen.sif
9 Compile the changes into an updated repository file (SRF file). Copy the new SRF file to the Siebel
Server installation, under SIEBSRVR_ROOT\objects\enu.
10 In the tools.cfg file, change the value of the SymStrPrefix parameter back to X_. Save the
tools.cfg file.
Adding Seed Data for ACR 456
To implement this ACR, you must add views and other seed data to the Siebel application.
1 Launch the Siebel application, such as Siebel Call Center.
2 Navigate to the Administration - Application screen, and then the Views view.
3 Add the following views:
Transaction Log View
Transaction Log View - All
Transaction Log View - Manager
Position Export View by Skill
4 Associate suitable responsibilities to the new views.
5 Add List of Values (LOV) data for U.S. English (ENU), as described below.
NOTE: This example is for U.S. English (ENU) only. For other languages, see files in the
compressed file ACR456.zip. Set Display Value appropriately for each non-ENU language.
a Navigate to the Administration - Data screen, then the List of Values view.
104
b For Type TODO_TYPE, add new records, where:
Display Value is Import, and Language-Independent Code is Import.
Display Value is Export, and Language-Independent Code is Export.
c For Type EVENT_STATUS, add new records, where:
Display Value is Success, and Language-Independent Code is Success.
Display Value is Failed, and Language-Independent Code is Failed.
d For Type ACTIVITY_DISPLAY_CODE, add new records, where:
Display Value is Position and Activities, and Language-Independent Code is Position and
Activity.
Display Value is Assignment and Activities, and Language-Independent Code is
Assignment and Activity.
Activating Workflow Process for ACR 456
To implement this ACR, you must activate a new workflow process in Siebel Tools.
1 Launch Siebel Tools.
2 In the Object Explorer, click Workflow Process.
3 Select the workflow process Export Assignment Data. (This workflow was added when you
imported the file AM-ImportExport.sif.)
4 Publish and activate the selected workflow process.
Validating Configuration Steps for ACR 456
After performing all the steps described earlier in this topic, restart the Siebel Server and log in to
the Siebel Server. Refer to the information about importing and exporting assignment-related data
in the Siebel Assignment Manager Administration Guide. Validate that the user interface changes are
visible in the Administration - Assignment screen, and validate that the relevant functionality
described in that book works as expected.
The following sections contain information about how to implement ACR 457.
For more information about Siebel Order Management, see Siebel Order Management Guide on the
Siebel Bookshelf http://www.oracle.com/technology/documentation/siebel.html.
1 Navigate to the Siebel Tools installation directory <Tools Install Directory>\REPPATCH, and unzip
the acr457.zip file.
<Tools Install Directory>\REPPATCH\acr457\
VORD Compound Product Validation Engine
VORD Network Order Entry
3 Import the SIF files from the ObjectsSIFs folder into Siebel Tools using the Import From Archive
function. Make sure to choose Merge Option in the Siebel Tools import wizard.
NOTE: If you have not locked the required projects, you may receive a warning error message.
4 Import the following SIF files:
VORD CPVE Validation Service.sif
VORD Network Node.sif
5 Stop Siebel Server, if it is running.
6 Compile all the projects using Compile Projects function, and select either the All Projects option
or the Locked Projects option. Save the srf file to the <Siebel Server Install
folder>\objects\ENU\siebel_sia.srf directory on the installed Siebel Server.
8 Lock the SIS OM Base Architecture project, and import the workflows listed in the following table
into the Siebel application.
a Select Workflow Process in Siebel Tools Object Explorer.
b Right-click on the right-side pane called Workflow Processes and import the .xml file into Siebel
Tools from the workflows folder. Refer to the list of workflows in the table above to know which
projects these workflows need to be imported into.
c Check the status of each workflow process. If it is In-Progress, then deploy the workflow to
change its status to complete. Do not click the Deploy + Activate button, as doing so will yield
an error message. Only click the Deploy button.
NOTE: You may receive the "This is an invalid Workflow" error message while deploying the
modified workflows from the list. Ignore the error and click Yes.
d Repeat Step b and Step c for of all the workflows in the folder.
e Log in to the Siebel application as an administrator, and navigate to the Site Map.
Workflow Name New/Modified Project
VORD Validate (Order) Modified SIS OM Base Architecture
VORD Validate (Quote) Modified SIS OM Base Architecture
SIS OM Disconnect Products & Services Process Modified SIS OM Base Architecture
106
f Click on Administration - Business Process.
g Navigate to Workflow Deployment > Repository Workflow Process.
h Query for the workflow processes and activate them.
9 Restart the Siebel Server.
10 Launch the Siebel Communications application.
Enabling Component Groups
Use the following procedure to enable component groups.
To enable component groups
1 Navigate to Site Map > Administration - Server Configuration > Enterprises > Component
Groups.
2 Query for each of the following component groups and if Enable State = Disabled, click
<Enable>:
SIA
Siebel CME [Alias- Communications]
Siebel ISS [Alias- ISS]
Communications Management [Alias- CommMgmt]
Workflow Management [Alias- Workflow]
NOTE: You can also activate the component groups by running the Enable compgrp <Alias>
command through the Srvrmgr command prompt.
3 After enabling the necessary components, navigate to Site Map > Administration - Server
Configuration > Enterprises > Synchronize, select all the records and click the Synchronize
button.
4 Bounce the server.
5 Use the following procedure if you are a Windows customer:
a Log in with system administrator credentials.
b From Start > Run, type cmd.
c Find the drive that the build is installed on.
d Type <Build>ses\siebsrvr\bin.
e Execute the following command:
srvrmgr /e SIEBEL /s server name:portnum /u SADMIN /p MSSQL <enter>
f Run the command to verify that the components were successfully enabled.
g Run the following command to enable the component group:
Enable compgrp <Alias>
h Verify that the command executed successfully, and then run the Exit command.
i Restart the services.
j After the machine is up, than connect to server manger by running command in Step e and verify
the enabled components groups by running the "list of compgrp" command.
6 Use the following procedure if you are a UNIX customer:
a From the local machine click on Stat - Run- type telnet <Machine name> (such as telnet
sdcpi43).
b Log in with administrator credentials.
c Navigate to <Build>ses\siebsrvr\bin.
d Run the following commands:
smgr <enter>
set server <machine name> <enter>
list compgroup <enter>
e Run the following command to enable components group:
f Verify that the command executed successfully, and then run the Exit command.
g Restart the services.
Use the following procedure to delete Customer Order Management workflows.
NOTE: Before you run the scripts in the following procedure, make sure the Workflow component is
enabled and that the server has been restarted after the component groups have been enabled.
To delete Customer Order Management workflows
1 Navigate to Site Map > Administration Business Service > Simulator.
2 Click the Load from File button and load the "COM_Workflow Admin Service Delete.xml" file.
3 On the Input Arguments tab, click the Load from File button and load the "COM_Workflow Admin
Service Input.xml" file.
4 On the Simulator Applet, select the record that has the Method Name as "DeleteDeploy" and click
the Run button.
Activating the Workflows Through Scripts
Use the following procedure to activate Customer Order Management workflows.
NOTE: Before you run the script, make sure the Workflow component is enabled and that the server
has been restarted after the component groups have been enabled.
108
To activate Customer Order Management workflows
1 Navigate to Site Map > Administration Business Service > Simulator.
2 Click the Load from File button and load the "COM_Workflow Admin Service Activate.xml" file.
3 On the Input Arguments tab, click the Load from File button and load the "COM_Workflow Admin
Service Input.xml" file.
4 On the Simulator Applet, select the record that has the Method Name as "Activate" and click the
Run button.
A record displaying the number of workflows activated will display.
5 Log out of the eCommunications application and then log back in.
This will allow you to begin creating orders.
Use the following procedure to manually activate the Pricing and Eligibility Procedure - Default
workflow process.
To manually enable the Pricing and Eligibility workflow process
1 Click on Administration - Business Process.
2 Navigate to Workflow Deployment > Repository Workflow Process.
3 Query for the Pricing and Eligibility Procedure - Default workflow process and activate it.
4 Log out and relogin in to Siebel eCommunications application.
You can now create orders.
The following sections contain information about how to install and configure ACR 463.
CAUTION: ACR 463 does not include all of the Web services for MDM/PIM.
NOTE: This ACR is for Siebel Industry Applications only.
NOTE: If you have installed Siebel 8.1.1 QF1002 for ACR 463 or Siebel 8.1.1.1 QF5101 for ACR 463,
you do not need to perform the repository changes detailed in the following sections, as the changes
that you performed when you installed the Quick Fixes were not overwritten. However, if you are
installing ACR 463 for the first time, you do need to perform the repository changes detailed in the
following sections.
1 Navigate to the Siebel Tools installation directory <Tools Install Directory>\REPPATCH.
2 Unzip the file ACR463.zip file.
<Tools Install Directory>\REPPATCH\ACR463.zip
The ACR463.zip folder that you create will contain the following subfolders:
\DMGSchemaChanges
\EIM
\LMU
\SeedData
\SIFFiles
\WFs
The following instructions refer to the folders specified above.
Applying Schema Changes to the Database
The information in the following section describes how to apply schema changes to the database,
and also provides information about which tables were changed.
Use the following procedure to import the schema into the database.
To import the schema into the database
1 Lock the following projects before importing:
EIM Asset
EIM Common SIA
EIM Invoice
EIM Order
EIM Product
EIM Quote
EIM BulkRequest
EIM Organization
EIM Service Request
Table Asset
Table BulkRequest
Table Invoice
Table Order
Table Organization
110
Table Product
Table Quote
Table Service Request
Table Special Rate List
Table CIF
Table Person
Table FleetManagement
CUT Newtable
2 Import the .sif files in the following sequence
AIA24_schema_changes.sif
AIA24_EIM_schema_changes.sif
3 Use the Siebel Tools Import from Archive function to read this file and create the tables in the
repository. The "merge" option should be used while importing this file.
Creating Tables on the Physical Database
Use the following procedure to create tables on the physical database.
To create tables on the physical database
1 Use Siebel Tools to query for the list of tables that were imported into the repository, and then
use the "Apply/DDL" button to apply the changes to the physical database.
2 Use privileged database user\pass word in the Database user \ Database user password column
in the Apply Schema dialog box.
NOTE: Make sure to create the ODBC data source for the database to which you want to apply
the schema changes.
3 From Object Explorer, select Table Object Definition.
4 Query for the tables that have changed using the following criteria:
Query Criteria: Changed = Yes
5 Click on Apply/DDL.
6 Select Apply DDL.
7 Select Current Query from the Tables drop-down list.
8 Enter the appropriate information for ODBC Data Source/ Database User and Database User
Password.
9 Click the Apply button.
The "Changes Successfully Applied" message displays.
Importing Seed Data
Use the following procedure to import seed data.
To import seed data
a Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC).
b Navigate to the System DSN tab.
c Click Add.
d Select "Siebel Oracle90" driver (from Datadirect Technologies).
e Enter a data source name (such as DevelopmentDB).
f Enter the server name to connect to:
For Oracle, enter the TNS service name that you created to connect Siebel Tools to the
database.
g Test the connection and click OK after you have verified the connection.
2 Navigate to the directory where you installed Siebel Tools and change it to the REPATCH\ACR463
directory.
NOTE: Before you perform the following step, make sure that the dataimp.exe file exists in the
<Tools Install Directory>/bin directory.
3 Seed data import includes mono-language seed-data import and language seed-data import.
NOTE: Use the /Z option flag to ignore duplicates during import.
a Use the following command to import mono-language seed data:
<Tools Install Directory>\bin\dataimp /u sadmin /p sadmin /f <Tools
InstallDirectory>\REPATCH\ ACR463\SeedData\Seed_aiacom24.dat /l <Tools
InstallDirectory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q -
1 /w n /e y /t n /x R /n 100 /h log
b Use the following command to import the language seed data:
<Tools Install Directory>\bin\dataimp /u sadmin /p sadmin /f <Tools
InstallDirectory>\REPATCH\ ACR463\SeedData\seed_locale_<language>.dat /l <Tools
InstallDirectory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q -
1 /w n /e y /t n /x R /n 100 /h log
<Tools Install Directory> - Replace with your Tools install directory.
<ODBC Source Name> - Replace with ODBC name created in Step 1.
4 Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the
import completed successfully.
112
Siebel Tools Changes for ACR 463
1 Open tools.cfg from <Tools Install Directory>\Bin\Enu and verify the [Siebel] section. Make sure
that the SymStrPrefix entry has been set to SBL_
[Siebel]
..
SymStrPrefix parameter needs to be X_ for Siebel Customers.
SymStrPrefix = SBL_
..
NOTE: After changing the tools.cfg file, make sure to log out of Siebel Tools and log in again to
apply the changes.
2 In Siebel Tools, lock all the following projects:
ABO Bulk Request
Account
Account (SSE)
Assignment (SSE)
Asset Management
Bitmap
CMU Billing BC
CMU Billing Product
CMU Billing UI
CMU Billing Integration
CUT Admin - External Data
CUT Billing
CUT Credit Alert
CUT Profile
CUT Trouble Ticket
Contact
Comm Manager
Communication
Eligibility Compatibility
Fleet Management
ISS Authoring Admin
ISS Class Admin
ISS Product Admin
ISS Promotion Admin
MACD Performance
Order Entry
Prepaid Service 8.1
Product
Product (SSE)
Product Integration
Product Selection UI
Quote (UI)
Quote
SIS OM Base Architecture
Service
Symbolic Strings
UCM Privacy Management
VEAI CUT Billing Integration
VERT CUT Address
VERT CUT Screens
Web Channel Order Management
Web Service Integration
eService Billing
eAuto Product
3 Import the rest of the SIF files from the SIFFiles folder into Siebel Tools using the Import From
Archive function.
Make sure to choose Merge Option in Siebel Tools Import Wizard.
Import the following SIF files:
Modified Applets.sif
Modified BCs.sif
Modified Bitmaps.sif
Modified BOs.sif
Modified BSs.sif
Modified Classes.sif
114
Modified Commands.sif
Modified IOs.sif
Modified Links.sif
Modified Picklists.sif
Modified Screens.sif
Modified Symbolic Strings.sif
Modified Views.sif
Modified Workflow Policy Columns.sif
Modified Workflow Policy Objects.sif
The following steps are only necessary for customers who are installing languages other than
ENU:
4 Import LMU Files for the specific language from the LMU folder into Siebel Tools. [Select menu
Tools ' Utilities ' Locale Management].
a Select Source Language = English American
Target Language = <Specific Language>
b Click the Import tab > Browse to locate the LMU file you want to import and click Import.
NOTE: If an error occurs while you are importing the LMU file, open the file, convert the
language value for Source into the corresponding language. For example, do the following
for NLD:
Source (Language,Application) : (Engels-Amerikaans,STD - Standard)
Target (Language,Application) : (Dutch,STD - Standard)
6 Compile all the projects using Tools > Compile Projects and selecting the "All Projects" option.
Save the srf file to location <Siebel Server Install folder>\objects\ENU\siebel_sia.srf on the
installed Siebel server.
8 Import the workflows listed in the following table into the Siebel application.
NOTE: All of the existing workflows should be imported. In other words, the modified workflows
should be imported into the corresponding projects.
Workflow Name Project
ABO Bulk Request - Validate Process ABO Bulk Request
ABO Bulk Request Add Item Customize Process ABO Bulk Request
ABO Bulk Request - Clear Exception Process Workflow ABO Bulk Request
ABO Bulk Request - Parallel Sub Process Workflow ABO Bulk Request
ABO Bulk Request - Prepare Action Set Sub-Process Workflow ABO Bulk Request
ABO Bulk Request - Submit Process Workflow ABO Bulk Request
Basic Pricing Procedure Cfg RTC
CMU Credit Alert Status Sync Web Service Integration
CMU SIA Submit Adjustment Request to External CMU Billing Integration
CMUBalanceDetailsEventAdjustmentWF CMU Billing Integration
CMUEventDetailsAdjustmentWF CMU Billing Integration
CMUInvoiceAdjustmentWF CMU Billing Integration
CMUItemChargeAdjustmentWF CMU Billing Integration
CMUUnbilledEventAdjustmentWF Web Service Integration
CMUUnbilledNonCurrencyEventAdjustmentWF Web Service Integration
Dynamic Pricing Procedure Row Set Transformation Toolkit
ISS Promotion Upgrade Process ISS Promotion Workflow
Pricing Procedure - Calculate Net Price Row Set Transformation Toolkit
SIS OM Disconnect Products & Services Process SIS OM Base Architecture
SIS OM Edit Complex Asset Workflow SIS OM Base Architecture
SIS OM Edit Service Order Line Item SIS OM Base Architecture
SIS OM Modify Products & Services Process SIS OM Base Architecture
SIS OM Order Line Item Update Main SIS OM Base Architecture
SIS OM Suspend / Resume Asset Sub-Process SIS OM Base Architecture
SIS OM Suspend / Resume Products & Services Process SIS OM Base Architecture
SISOMBillingSubmitOrderWebService CMU Billing Integration
SWI Account Update Workflow Web Service Integration
SWI Address Update Workflow Web Service Integration
SWI Billing Profile Update Workflow Web Service Integration
SWI Cancel Sales Order Line Item Web Service Integration
SWI Contact Update Workflow Web Service Integration
SWICancel Sales Order Web Service Integration
SWI Special Rating - Synchronize Process Web Service Integration
SWIAdjustmentStatusUpdate Web Service Integration
SWICopyOrder Web Service Integration
SWIOrderUpsert Web Service Integration
116
b Right-click on the right-side pane 'Workflow Processes' and import the .xml file into Siebel Tools
from the WFs folder. Refer to the list of workflows in the table above to know which project these
workflows need to be imported into.
c Check the status of the Workflow process. If it is In-Progress, then make it complete by
deploying the Workflow process (For version 8.0 and above, the "Publish/Activate" button
changes the status to complete. To view this button, click the View menu > Tool Bar, and select
WF/Task Editor.)
NOTE: If this step throws an error message, note the workflows that failed and manually
activate them within the application.
e Log in to the Siebel application as an administrator.
f Navigate to the Site Map.
g Click on Administration - Business Process.
h Go to Workflow Deployment > Repository Workflow Process.
i Query for the workflow processes and activate them.
9 Modify the run time events for promotions:
a Navigate to the Administration - Runtime Events screen.
b Click on the 'Action Sets' view.
This shows three applets.
c In the first applet, called 'Action Sets', search for the Action Set 'Cache Refresh BC - ISS
Promotion Pricing Components List Applet'.
d For this Action Set, in the bottom Form Applet, there is a control with the 'Business Service
Context' label. For this control, the current value previously was only "ISS Promotion Pricing
Components", "ISS Promotion Pricing Rules Summary". Another new entry was added to this and
now the value for this control is "ISS Promotion Pricing Components", "ISS Promotion Pricing
Rules Summary", and "Promotion Config Item". (Note that there should be a space after the
comma.)
e Navigate to the child applet.
f Uncheck the Active flag for the Validate record.
10 Release Variable Maps and Signals manually:
a Navigate to Site Map > Admin - Order Management > Variable Maps.
b Query for the following:
SWIValidateDependentOrders Web Service Integration
Verify Header (Order) COM Workflows
Verify Item (Order) COM Workflows
Default Pricing Variable Map - Row Set - Basic
Default Pricing Variable Map - Row Set
Default Pricing Eligibility Variable Map - Row Set
c Lock each Variable Map and release a new version of each of these maps.
d Navigate to the Signals view, and query for ReviseCopyOrder.
e Lock this signal and release a new version.
Activating Validation Rulesets and Reloading Runtime Events
Use the following procedure to activate data validation ruleset.
To activate the data validation ruleset
1 Navigate to the Site Map, and query for Administration - Data Validation.
2 Click the Ruleset View hyperlink.
Query for the following rulesets in the Validation Ruleset applet:
SWI Order Validation Rule Set
SWI SRL Delete
SWI SRL Item
SWI SRL Modify
3 Click the Activate button to activate the rulesets.
After you activate the rulesets, you need to reload the runtime events.
Use the following procedure to reload the runtime events.
To reload the runtime events
1 Within the Site Map, navigate to the Administration - Runtime Events screen.
2 Click the Events view hyperlink.
3 Within the Events list applet, click the Menu button, and select Reload Runtime Events.
Oracle Advanced Queuing (AQ)
Oracle Streams Advanced Queuing (AQ) is a database-integrated messaging infrastructure in Oracle
database. AQ uses the functionality of the Oracle database to store messages in persistent queues.
All operational benefits of the Oracle database such as high availability, scalability, and reliability are
applicable to the messages and queues in AQ. Standard database features such as backup and
recovery, security, and manageability are available to AQ.
AQ has been implemented for the following outbound Web services in this release:
Special Rating List
118
Submit Order
Adjustment
The following sections contain information about how to implement AQ in your Siebel application, as
well as more detailed information about the outbound Web services listed above.
Special Rating List
This service is used to synchronize the modified friends and family list with the external BRM system.
It is invoked through the Synchronize button in the Special Rating list applet.
Use the following procedure to sync the modified list.
1 Navigate to Accounts > Account List view.
2 Query for the Target Account from the list.
3 Drill down on the account name.
4 Navigate to the Profiles view, and click on the Special Rating Profile subview.
5 Query for the target special rating list and click the Synchronize button.
The Synchronize button invokes the "SWI Special Rating List - Synchronize Process" workflow
using the Named Method Business Component user property.
The SWI Special Rating - Synchronize Process workflow is a new workflow created for the AIA Comm
2.4 release. It is invoked through the Synchronize button, which is available in the Special Rating list
applet (Account screen > Profiles view > Special Rating Profile). The workflow contains the steps to
query for and synchronize the updated Special Rating List with BRM by calling the Proxy Business
Service, as detailed below.
Start > (Connector 0) > Query Special Rating List > Synchronize > Update List Synch Date >
Upadate Items Synch Date > End 0
Note the following information about the SWISpecialRatingList outbound Web service:
It is a new Web service.
It is an asynchronous outbound Web service
Its namespace is http://siebel.com/asi
This Web service is used to send the Updated/Modified Special Rating List details to BRM for
synchronizing when the user clicks the Synchronize button in the Special Rating list applet.
This AQ and connection factories are created in FMW and the same URI should be used in outbound
Web service target address.
Use the following procedure to update the target address.
To update the target address
1 Naviate to the Site Map > Administration - Web Services screen.
2 Navigate to the Outbound Web Services aggregate view.
3 Query for the "SWISpecialRatingList" service name.
4 Change the following field values in the Service Port applet:
Transport: JMS
Address: <Give the AQ URL in FMW> (for example, jms://java:comp/resource/
CommsJmsRP1/Queues/AIA_SPECIALRATINGJMSQ@java:comp/resource/CommsJmsRP1/
QueueConnectionFactories/QCF)
5 Save the record and click the Clear Cache button.
Submit Order Outbound Web Service
This outbound service is used to send the order details to AIA. The user initiates the service by
clicking the Submit button on the order header form in the Order Entry view.
Use the following procedure to initiate the Submit Order outbound service.
To initiate the Submit Order outbound service
1 Navigate to the Sales Order screen > Order List view.
2 Query for the Target Sales Order.
3 Drill down on the Order #.
4 Click the Submit button.
SISOMBillingSubmitOrder Web Service Workflow
This is an existing workflow that submits an order from the Siebel CRM application to the billing
application and creates a new account, if needed, in the billing application. Users initiate this
workflow by clicking the Submit button on the order header form in the Order Entry view.
Note the following information about the SWISubmitOrder outbound Web service:
It is a new Web service
It is an outbound Web service
Use this Web service to submit orders into the queue. This AQ and connection factories are created
in FMW and the same URI should be used in outbound Web service target address.
Use the following procedure to update the address:
To update the address
1 Navigate to Site Map > Administration - Web Services screen.
3 Query for the "SWISubmitOrder" service name.
4 Change the following field values in the Service Port applet:
120
Transport: JMS
CommsJmsRP1/Queues/AIA_SALESORDERJMSQUEUE@java:comp/resource/
CommsJmsRP1/QueueConnectionFactories/QCF)
SWICreateAdjustment Outbound Web Service
This outbound service is used to Submit an Adjustment request to BRM. Users initiate the service by
clicking the Submit button on the SIA CUT Adjustment External Line Items view.
To initiate the SWI CreateAdj ustment outbound Web service
1 Navigate to the Billing Adjustments screen > SIA CUT Adjustment External Line Items view.
2 Query for the particular adjustment.
3 Click the Submit button.
CMU SIA Submit Adjustment Request to External Workflow
This workflow has been modified as part of the "Adjustment Revenue Leakage Enhancement"
feature. This workflow submits the Adjustment Request to the external system by invoking an
outbound Web service and changing the status of Adjustment Header to Submitted. Users initiates
this workflow by clicking the Submit button in the Billing Adjustments screen.
This workflow does the following:
1 Queries the adjustment request.
2 If the adjustment request is not approved, it changes the status of the request to Pending, and
terminates.
3 If the adjustment request is approved, it reads the enterprise details, such as the enterprise
server name, language, and locale.
4 Sets the enterprise details as part of the request message.
5 Makes an outbound call to the AQ.
6 Updates the Siebel database for the Adjustment Record to reflect the status as Submitted.
SWICreateAdjustment Outbound Web Service
Note the following information about the SWICreateAdjustment outbound Web service:
It is a new Web service
It is an outbound Web service
Use this Web service to Submit Adjustment Request into the queue. This AQ and connection factories
are created in FMW and the same URL should be used in outbound Web service target address.
Use the following procedure to update the address.
To update the address
1 Navigate to Site Map > Administration - Web Services screen.
3 Query for the "SWICreateAdjustment" service name.
4 Change the following field values in the Service Port applet.
Transport: JMS
CommsJmsRP1/Queues/AIA_CMUREQADJIOJMSQUEUE@java:comp/resource/
CommsJmsRP1/QueueConnectionFactories/QCF)
Configuring FMW URLs for Web Services
Use the following procedures to configure FMW URLs for Web services.
To configure FMW URLs for the outbound Web services
1 Log into the Siebel application as an administrator.
2 Navigate to the Site Map.
3 Click on Administration - Web Service > Outbound Web Services.
4 Query for the Name= *ABCS*.
5 Navigate to the Service Ports list applet and change the URI given by the ABS team.
6 Query for *JMS* and *Sync* and change the URI.
(For example, http://ap6039fems.us.oracle.com:7797)
To configure FMW URLs for inbound Web services
1 In Administration - Web Services > Inbound Web Services, make sure the corresponding Web
services are active. If they are not, change the status from "Inactive" to "Active", and click the
Clear Cache button.
NOTE: Query for these inbound web services: * ISS *; * Update Order *; * SWI Update *, SWI*
2 Query for Name = SWI Account Update.
122
3 In the middle Inbound Service Ports list applet, change the address port.
Address: (example only) http://sdchs20n513.corp.siebel.com/eai_enu/
start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute&UserName=SADMIN&Pass
word=MSSQL
NOTE: Replace the string <web server>, <lang>, <UserName>, <Password> with correct data
based on server information.
4 Repeat the preceding steps for all inbound Web services.
Setting Up Order Creation
Use the following procedures to enable component groups.
To enable compgrps
1 Bounce the server after enabling the compgrp and synchronizing it.
2 Enable the following compgrps:
Communications Management [Alias CommMgmt]
For more information about enabling compgrps, see Enabling Compgrps on page 146.
Activating and Configuring ACR 463 Workflows
The procedures in the following sections describe how to activate and configure the ACR 463
workflows.
To activate workflows
Use the following steps to activate all C/OM workflows.
1 Navigate to Site Map > Administration Business Process -> Workflow Deployment > Active
Workflow Processes.
2 In the second applet, perform one of the two following actions:
Query for SIS*,Pri*,PSP*,ISS*,Elig*,eSales*
Query for the following groups: Eligibility & Comp, Asset Based Ordering, Pricer, eSales,
Product Promotions, Configurator, C/OM UI processes, CUT eSales (for SIA, not for HOR),
Product Recommendation, and delete them manually after deactivating the processes. To
deactivate these groups, select them all and then select Deactivate Process. You can check
the Deployment Status as Inactive.
3 Delete all the records.
4 In the first applet, perform one of the following two actions:
Query for SIS*,Pri*,PSP*,ISS*,Elig*,eSales*
Product Promotions, Configurator, C/OM UI Processes, CUT eSales (for SIA, not for HOR),
Product Recommendations.
5 Activate all of the workflows.
Workflow Policy Setup and Configuration
The following sections describe how to set up and configure workflow policies.
Siebel Components Groups
In order to enable the workflow policies, the following components should be configured and running
on Siebel Server (in addition to the Application Object Manager component).
Enabling EAI and Workflow Component Groups in the Siebel Server will start all the required
Components stated above for transaction logging.
To set the workflow component group
Navigate to Site Map > Administration > Server Management > Components, and query for
Workflow* to check that the Workflow Management component and its components are enabled.
To remove the existing triggers ( if any)
1 Navigate to Administration > Server Management > Jobs.
2 Click New and type "Generate Triggers" under Component/Job to create a job for the Generate
Triggers component.
3 Define the job parameters with the following values:
EXEC = TRUE
Privileged User = SADMIN
Privileged User Password = ******[Password for SADMIN]
Component Name Component Alias Component Group
Enterprise Integration Mgr EIM EAI
EAI Object Manager (ENU) EAIObjMgr_enu EAI
Workflow Process Manager WfProcMgr Workflow
Workflow Process Batch Manager WfProcBatchMgr Workflow
Workflow Monitor Agent WorkMon Workflow
Generate Triggers GenTrig Workflow
124
Remove = TRUE
Trigger File Name: trigger.sql
4 Start the job.
5 Verify that the job was successful once it has completed.
NOTE: Make sure that the SADMIN user has the necessary privileges for generating triggers before
performing the following procedure.
To generate the triggers
1 Navigate to Administration > Server Management > Jobs.
2 Click New and type "Generate Triggers" under Component/Job to create a job for the Gnereate
Triggers component.
3 Define the job parameters with the following values:
EXEC = TRUE
Privileged User = SADMIN
Privileged User Password = ******[Password for SADMIN]
4 Start the job.
5 Verify that the job was successful once the job has completed.
Configuring Workflow Monitor Agent
Use the following procedure to configure Workflow Monitor Agent.
To configure Workflow Monitor Agent
1 Navigate to Site Map > Administration - Server Configuration > Enterprises > Component
Definitions, and query for Workflow*.
2 Make a copy of the Workflow Monitor Agent in Administration - Server Configuration >
Component Definition and change the name to "Workflow Monitor Agent SWI".
3 Change the Alias name to 'WorkMonSWI'.
4 Under Component Parameters, query for "Group Name" and type the SWI Account Update Policy
Grp under Value to change the Group Name to SWI Customer Update Policy Grp in the
Component Parameter applet.
5 Change the Action Interval to 5.
6 Change the Sleep Time to 15. (Select the Advanced button.)
7 Change the Default Task to 1. (Select the Advanced button.)
8 Click the Activate button to change the status of the new component to "Active".
9 Synchronize the components.
Configuring Default Tasks for Workflow Monitor Agent
Server Manager contains a parameter called 'Show Advanced Objects' that controls the display of all
the objects that are marked for the advanced user.
Workflow Monitor Agent has a parameter called 'Default Tasks' which has been hidden and should
only be displayed or available to advanced users.
Use the following procedure to reveal this hidden parameter.
To display the Default Tasks parameter
1 Navigate to Site Map > Administration - Server Configuration > Servers.
2 In the top Siebel Servers applet, select the server on which you want to modify the parameter.
3 Under the Component subtab, query for the Server Manager component.
4 Under the Component Parameter subtab, query for 'Show Advanced Objects'.
5 Change the value to 'True'.
6 Change the Default Task parameter to 1 (Select the Advanced button.)
NOTE: You must log out from the current user session and log back into the application in order
for the parameter to take effect.
7 Rename the existing diccache.dat file in the path <Installed Directory> \ses\siebsrvr\bin.
Starting Tasks for Workflow Monitor Agent for Customer
Synchronization
Use the following procedure to start tasks for the component that is online/enabled.
To start tasks for Workflow Monitor Agent
1 Navigate to Site Map > Administration - Server Management.
2 Select "Tasks".
3 Query for the "WorkMonSWI" task and start it. You can also use Server Manager to start the task.
4 Start srvrmgr: srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u
<userid> /p <password>.
5 Start the task for the WorkMonSWI component.
After about five minutes, check for log details for the task for the new workflow monitor component
"Workflow Monitor Agent SWI" by navigating to Administration > Server Management > Task.
126
If there are errors, check to see if all configurations have been properly performed. If not, repeat
the procedures detailed in To generate the triggers on page 124 after restarting the Siebel Server.
Integration User Setup
This section describes the integration user setup process. User credentials need to be configured (on
the AIA side) for the Siebel Inbound Web Services call from the AIA side to avoid the boomerang
effect.
To set up the integration user
1 Log in as SADMIN.
2 Navigate to Administration-User > Employee view. The list applet should contain the integration
user flag.
3 Configure a new integration user by setting the integration user flag to Y for a specific user.
NOTE: The flag name is Integration User Flag.
To set up and configure system preferences
1 Navigate to Administration - Application > System Preferences in the application, query for
'Enable AIA Comms' in the 'System Preference Name' field, and set the 'System Preference Value'
to 'TRUE'.
2 Set "Enable AIA Testing" to "TRUE".
3 Set "AIA Order Backup Path" to <the path where the xml files will be created on the Siebel Server
machine>/
For example, for Windows, this would be D:/.
For Unix, this would be /export/home/qa1/orderbackup/
4 Query for 'Validate Due Date' in the 'System Preference Name' field and set the 'System
Preference Value' to 3.
5 Query for 'Cancel Error Mode' in the 'System Preference Name' field and set the 'System
Preference Value' to 2.
Enabling Dynamic Pricing
Customers with the 'Dynamic Pricer' license will need to undertake the steps mentioned in the
document to enable the execution of 'Dynamic Pricing Procedure'.
In order to leverage the dynamic pricing procedure, customers have to perform following changes to
the existing repository.
The Siebel pricing module is available in multiple licensing modes and each mode is associated with
either the 'Basic Pricing Procedure' or the 'Dynamic Pricing Procedure'.
Basic Pricing Procedure
This procedure mimics the basic Siebel Pricer functionality that was available in Siebel version
7.7 applications.
Basic Siebel Pricer functionality includes list price, volume discounts, and service pricing.
It leverages the variable maps that do not contain the XA child variable maps.
Dynamic Pricing Procedure
This provides the complete pricing capabilities such as attribute pricing, promotions, aggregate
discounts, and so forth.
It leverages the variable maps that contain the XA child variable maps.
It is available only to those customers that have the 'Dynamic Pricer' license.
To enable dynamic pricing
If you are running Siebel applications version 8.1.1 or above, navigate to Administration - Pricing
> Price Lists, and select Enable Dynamic Pricing from the applet-level menu in the Price List
applet.
If you are running Siebel applications versions earlier than 8.1.1, you must modify the signals
mentioned in the following section manually.
Modifying Signals
Use the following procedure to modify signals.
To modify signals
Navigate to Administration - Order Management > Signals, query for each signal mentioned in
the following tables, and make the necessary modifications.
Signal: CalculatePriceAndCheckEligibility
Actions and Parameters:
Sequence: 1
Service Type: Workflow
Service Name: PSP Driver Workflow Process
Service Method: RunProcess
Application Name: N/A
Mode: N/A
Instance Type: N/A
Fields: N/A
128
Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL
Action: Y
Signal: QuotesAndOrdersValidate
Sequence: 1
Mode: Order
Instance Type: Header
Fields: N/A
Condition: N/A
Active: Y
Make similar changes to actions in this signal where:
Mode: Order, Instance Type: Line Item
Mode: Quote, Instance Type: Header
Mode: Quote, Instance Type: Line Item
Name Value
SubPSPPricingWFName Dynamic Pricing Procedure
SubPSPWFName Pricing and Eligibility Procedure - Default
Variable Map - Context Default Pricing Variable Map - Context
Variable Map - Row Set Default Pricing Eligibility Variable Map - Row Set
Name Value
Variable Map - Row Set Default Pricing Eligibility Variable Map - Row
Set
Signal: VerifyItem
Sequence: 1
Mode: Agreement
Fields: N/A
Active: Y
Mode: Order, Instance Type: Header
Signal: Product Recommendation Signal
Sequence: 1
Service Name: Product Recommendation Driver Workflow
Mode: N/A
Instance Type: Line Item
Fields: N/A
Name Value
Variable Map - Row Set Default Pricing Eligibility Variable Map - Row
Set
130
Condition: GetProfileAttr('Block Variable Map Operations')='N' OR GetProfileAttr('Block Variable Map
Operations') IS NULL
Active: Y
Signal: CalculatePriceExternal
Sequence: 1
Service Type: Business Service
Service Name: Pricing Manager
Service Method: RunPricerWorkflow
Mode: N/A
Instance Type: N/A
Fields: N/A
Condition: N/A
Active: N/A
Signal: SpreadDiscount, SpreadDiscount - All
Sequence: 1
Service Name: Spread Discount Driver Workflow Process
Mode: N/A
Instance Type: N/A
Name Value
VariableMap 1 Default Product Recommendation Variable
Map - Context
Name Value
Fields: N/A
Condition: N/A
Active: Y
Signal: ApproveItem
Sequence: 1
Service Name: PSP Workflow Driver Process
Mode: Agreement
Fields: N/A
Active: Y
Mode: Order, Instance Type: Header
Signal: CalculatePrice
Sequence: 1
Name Value
Variable Map - Row Set Spread Discount Default Pricing Variable Map - Row Set
Name Value
SubPSPWFName Dynamic Pricing Procedure
Variable Map - Row Set Default Pricing Variable Map - Row Set
132
Mode: N/A
Instance Type: N/A
Fields: N/A
Active: Y
Signal: CalculatePriceAll
Sequence: 1
Mode: N/A
Fields: N/A
Active: Y
Name Value
Name Value
Signal: CalculatePrice_eSales
Sequence: 1
Mode: N/A
Instance Type: N/A
Fields: N/A
Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULLY
Signal: CalculatePriceAll_eSales
Sequence: 1
Mode: N/A
Instance Type: Line
Fields: N/A
Action: Y
Name Value
Name Value
134
Signal: CalculatePrice_Configurator
Sequence: 1
Mode: N/A
Instance Type: N/A
Fields: N/A
Active: Y
Signal: CalculatePrice_Advisor
Sequence: 1
Mode: N/A
Instance Type: N/A
Fields: N/A
Name Value
Name Value
Active: Y
Signal: MergeIntoOnePackage
Sequence: 1
Mode: N/A
Fields: N/A
Active: Y
Signal: OrderTemplate
Sequence: 1
Mode: Order
Name Value
Name Value
136
Fields: N/A
Active: Y
Signal: OrderTemplateCopy
Sequence: 1
Mode: Order
Fields: N/A
Active: Y
Signal: OrderTemplateSelectItems
Sequence: 1
Name Value
Name Value
Mode: Order
Fields: N/A
Active: Y
Signal: QuoteTemplateCopy
Sequence: 1
Mode: Quote
Fields: N/A
Active: Y
Signal: QuoteTemplateSelectItems
Name Value
Name Value
138
Sequence: 1
Mode: Quote
Fields: N/A
Active: Y
Signal: SetFieldValue
Sequence: 1
Mode: N/A
Fields: Discount; Price List; Currency Code
Active: Y
Name Value
Name Value
Sequence: 1
Mode: Agreement
Fields: Product; Quantity Requested; Unit Price; Discount Amount; Discount Percent; Currency
Code; Item Price List; Covered Product Net Price
Active: Y
Sequence: 1
Mode: Order
Fields: Product; Quantity Requested; Unit Price; Discount Amount; Discount Percent; Prod Prom
Name; Currency
Active: Y
Name Value
Name Value
140
Sequence: 1
Mode: Quote
Fields: Product; Quantity Requested; Unit Price; Discount Amount; Discount Percent; Prod Prom
Name; Currency Code; Item Price List; Covered Product Net Price
Active: Y
Signal: Get Config Item Price
Sequence: 1
Service Name: Get Config Item Price - Driver Workflow
Mode: N/A
Instance Type: N/A
Fields: N/A
Condition: N/A
Active: Y
Name Value
Name Value
SubPSPWFName Get Config Item Price - Dynamic
Signal: GetProdPrice
Sequence: 1
Mode: N/A
Instance Type: N/A
Fields: N/A
Active: Y
Signal: GetUserProdPrice
Sequence: 1
Mode: N/A
Instance Type: N/A
Fields: N/A
Active: Y
Name Value
Variable Map - Row Set Product Pricing Variable Map - Row Set
Name Value
Variable Map - Context User Product Pricing Variable Map - Context
Variable Map - Row Set Product Pricing Variable Map - Row Set
142
Signal: PDS GetPricing
Sequence: 1
Service Name: Dynamic Pricing Procedure
Mode: N/A
Instance Type: N/A
Fields: N/A
Condition: N/A
Active: Y
Running EIM Data Migration
This section defines the detailed steps to run the EIM jobs for Siebel applications as a part of the
Creating and Updating Credit Alerts for Collection Flows in AIA -Com 2.4.
The ODI interface will be triggered to transport the required data for creating/updating Credit Alerts
from BRM into the Siebel EIM tables. EIM scripts will be then executed to load the data into the SFA
base tables.
Before you begin your import, do the following:
1 Make sure that the Siebel Server is up and running.
2 Make sure that the Siebel EIM component is online and running properly. (Check this from the
Administration - Server Configuration and Administration - Server Management screens.)
3 To avoid data loss, do not restart the Siebel server while the EIM job is running.
4 After you have completed loading data for one country, make a backup copy of the EIM logs for
status verification. (These logs are located under siebsrvr/logs.)
Use the following procedure to execute the EIM job.
To execute the EI M j ob
1 Move the ProcessAlertsAndBillingProf.ifb file from <Tools Installation directory>/REPPATCH/
ACR463/EIM to <Siebel Installation Directory>/ses/siebsrvr/ADMIN.
2 Run the EIM job with the ProcessAlertsAndBillingProf.ifb configuration file.
3 Verify that the EIM job is successful.
Runtime Configuration for Product Class and Attribute Definition Sync
Use the procedures in the following sections to perform runtime configuration for Product Class and
Attribute Definition Sync.
User List
Use the following procedure to add users to the user list.
To add users to the user list
1 Navigate to Administration - Users > Users.
2 Add user name, User ID, and choose the "Siebel Administrator" responsibility.
3 Add email address in the contact information in the child applet.
4 Navigate to Administration -Group > User Lists.
5 Create a User List and add the users in the child applet.
The "SCE Users" user list is created for the product class/attribute sync feature. You can add the
users in the same user list. If the SCE Users list does not appear, create the list and add the
users in the same user list.
Run Time Events
An email notification can be sent from product class definition, attribute definition and workspace
definition.
The following procedure describes how to add three runtime events to extract the email addresses
from user lists in the PreInvoke method of Business Components.
To add three runtime events to extract email addresses from users lists
1 Navigate to Administration - Run Time Events > Action Set.
2 Query for EmailNotify.
Action 'GetEmailAddr' is added to get the email addresses from the user list.
The Business Service context syntax is as follows
"Parent BC Record Name";"Field Name in Child BC ";"BO Name ";"Parent BC";"Child BC"
For instance:
"SCE Users";"Email Address";"Account";"Account";"Contact"
or
144
"SCE Users";"EMail Addr";"User List";"User List";"User"
The following table describes the three run time events that are added.
Email Templates
Use the following procedure to view the email templates that have been added.
To view the added email templates
1 Navigate to Administration- Communications > All Templates.
The following table describes the four templates that have been added:
2 To change the email body of the templates used to send emails from the workspace view,
navigate to Administration Communication > All Templates > Template Items.
The email templates detailed above are configured as user property values in the following Business
Components:
Sequence Object Type Object Name Event SubEvent Action Set Name
1 BusComp Attribute VOD
BusComp
PreInvokeMethod SendEmail EmailNotify
2 BusComp ISS Class VOD
BusComp
3 BusComp ISS Joint
Workspace
BusComp
Name Description
Attribute Defn Template To send email from the Attribute Definition view
Product Class Template To send email from the Product Class Definition
view
Workspace Attribute Defn Template To send attribute details from the Workspace view
in emails
Workspace Product Class Defn Template To send attributes from the Workspace view in
emails
Business Component User Property Template Name
ISS Joint Workspace
BusComp
PackageNameList|Attribute
Definition
Workspace Attribute Defn
Template
ISS Joint Workspace
BusComp
PackageNameList|Product
Class Definition
Workspace Product Class
Defn Template
Communication Profile
Use the following procedure to add From Email Address, POP server name, and SMTP server name
in the communication profile.
To add From Email Address, POP server name, and SMTP server name
1 Navigate to Administration - Communications > Communications Drivers and Profiles.
2 Create a new driver using the following values as an example:
Name: Internet SMTP/POP3 Server
Channel Type: Email
Inbound: Yes
Outbound: Yes
Channel String: POP3SMTP
Library Name: sscmmail
3 Set the profile in the child applet as Default SMTP profile.
For Example - Default SMTP profile
4 Set the profile parameters in the grandchild Business Component using the following values as
an example:
From Address: siebel.product.admin@demohost.siebel.com
POP3 Account Name: support
POP3 Account Password: support
POP3 Server: demohost.siebel.com
SMTP Server: rgmamersmtp.oraclecorp.com
The communication profile has to set in the user property in the Business Components listed in
Attribute VOD BusComp PackageNameList Attribute Defn Template
ISS Class VOD BusComp PackageNameList Product Class Template
ISS Joint Workspace
BusComp
CommProfileOverride Default SMTP Profile
Attribute VOD BusComp CommProfileOverride Default SMTP Profile
ISS Class VOD BusComp CommProfileOverride Default SMTP Profile
146
Recipient Group
The recipient group determines which Business Object is associated with the communication
template. Only primary Business Component fields and their child Business Component fields are
available to use in the template.
Use the following procedure to add the recipient group.
To add the recipient group
1 Navigate to Administration - Data > List of Values.
2 Query for "COMM_RECIP_GROUP" and add the recipient group.
3 To set the recipient group, navigate to Administration - Communications > All Templates >
Advanced and select the recipient group from the drop-down list.
The LIC values of the recipient groups added in Step 2 are set in the user property of the Business
Components listed in the following table:
Enabling Compgrps
Use the following procedures to enable compgrps.
To enable compgrps for the Windows machine
1 Log in with system administrator credentials.
2 From Start > Run, type cmd.
3 Find the build-installed drive.
4 Type <Build>ses\siebsrvr\bin.
5 Execute the following command:
Name Recipient Group
Attribute Defn Template AttributeDefnBC
Product Class Template ProductClassDefnBC
Workspace Attribute Defn Template WorkSpaceBC
Workspace Product Class Defn Template WorkSpaceBC
Business Component User Property
Recipient Group(LIC
Value)
ISS Joint Workspace
BusComp
RecipientGroup ISS Joint Workspace
BusComp
Attribute VOD BusComp RecipientGroup Attribute VOD BusComp
ISS Class VOD BusComp RecipientGroup ISS Class VOD BusComp
sr vr mgr / e SI EBEL / s sdchs21n110 / g sdchs21n110: 4330 / u SADMI N / p MSSQL <ent er >
6 Run the command to verify how many components are enabled as "list compgrp".
7 Run the following command to enable the components group:
8 Verify that the command ran successfully.
9 After verifying that the command ran successfully, exit the application.
10 Restart the server.
11 After the machine is up, connect to server manger by running the command in Step 5 and verify
enabled components groups by running the command " list compgrp ".
To enable compgrps for UNI X
1 From the local machine, click Start > Run, and type telnet <Machine name> ex:telnet sdcpi43.
2 Log in with the instance and pwd: resource.
NOTE: The instance is located in the URL. For example, if the URL contains 16661 = qa1, 16662
= qa2 instance and so on.)
3 Navigate to <Build>ses\siebsrvr\bin.
4 Run the following commands:
smgr <enter>
set server <machine name> <enter>
list compgroup <enter>
5 Type the following command to enable the components group:
6 Verify that the command ran successfully.
7 After verifying that the command ran successfully, exit the application.
This section describes how to prepare the Siebel Server for CRM Desktop for ACR 464.
To prepare the Siebel Server for CRM Desktop, perform the following tasks:
1 Importing Changes to the Siebel Repository from a Batch File on page 148
2 Importing Changes to the Siebel Repository from SIF Files on page 149
3 Applying Changes to the Siebel Database on page 151
4 Importing Seed Data on page 152
148
Importing Changes to the Siebel Repository from a Batch File
This section describes how to import schema changes into the Siebel Repository from a batch file.
To import changes to the Siebel Repository from a batch file
1 On the computer where Siebel Tools is installed, open the tools.cfg file in a text editor.
For more information, see Using Siebel Tools.
2 Make a note of the value that is set for the SymStrPrefix parameter.
Keep this note. You will need it later to set the SymStrPrefix parameter back to the original value.
3 Set the SymStrPrefix parameter to the following value:
SymSt r Pr ef i x = SBL_
4 Save the tools.cfg file.
5 If Siebel Tools is open, then exit out of it, and then open it.
6 In Windows Explorer, open one of the following files in a text editor:
For a Siebel Business Application, open the following file:
ACR464- HOR8112\ r eposi t or y\ pr oj ect s_t o_l ock. t xt
For a Siebel Industry Application, open the following file:
ACR464- SI A8112\ r eposi t or y\ pr oj ect s_t o_l ock. t xt
7 In Siebel Tools, click Project in the Object Explorer.
8 In the Projects list, make sure the Locked property contains a check mark for each project that
is listed in the projects_to_lock.txt file.
It is recommended that you check these projects out to your local database, perform the
configuration, and then check them back into the server database after you complete the
configuration.
9 Edit the repository_import.bat file to reflect the database, username, folder names, Siebel Tools
installation directories, and other information that is specific to your environment.
The required parameters are documented in the file.
10 Close Siebel Tools.
11 Open a DOS command line, and then run the Repository_import.bat file.
12 Check the following log files in the <Si ebel Tool s i nst al l at i on>\ l og directory to make sure
that only insert operations were performed.
Applet.log
Business Component.log
Business Object.log
Business Service.log
Class.log
DLL.log
Integration Object.log
Link.log
Pick List.log
Screen.log
Symbolic String.log
Table.log
View.log
If the log files indicate a problem, then create a service request (SR) on My Oracle Support.
Alternatively, you can phone Global Customer Support directly to create a service request or get
a status update on your current SR. Support phone numbers are listed on My Oracle Support.
You can also contact your Oracle sales representative for Oracle Advanced Customer Services to
request assistance from Oracle's Application Expert Services.
Importing Changes to the Siebel Repository from SIF Files
This section describes how to import schema changes into the Siebel Repository from sif files. You
must import these files separately because each import might affect an object in a subsequent
import. The objects must be merged. The batch import feature does not merge objects.
To import changes to the Siebel Repository from sif files
1 Import the changes:
a Open Siebel Tools, choose the Tools menu, and then the Import From Archive menu item.
b In the Select Archive to Import dialog box, open the following file:
Appl i cat i on\ Appl i cat i on- Updat e. si f
c In the Import Wizard-Preview dialog box, make sure the following option is chosen, and then
click Next:
Merge the object definition from the archive file with the definition in the repository
Siebel Tools displays the Import Wizard-Review Conflicts and Actions dialog box.
d Wait until Siebel Tools finishes loading the sif file.
You can view the status bar at the bottom of the dialog box to monitor progress.
e If the Conflicting Objects window of the Import Wizard-Review Conflicts and Actions dialog box
contains an item, then see Resolving Conflicts on page 150. Otherwise, continue to Step f.
f In the confirmation dialog box, click Yes.
g In the Import Wizard-Summary dialog box, click Finish.
2 Repeat Step 1 for each of the following files:
150
Busi ness Obj ect \ Busi nessObj ect - Updat e. si f
Tabl e\ base\ Tabl e- Updat e. si f
Busi ness Component \ Busi nessComponent - Updat e. si f
3 Examine the following log file to make sure all imports executed successfully:
Si ebel \ t ool s\ t emp\ i mpor t l og. t xt
4 Compile all locked projects.
5 Set the SymStrPrefix parameter in the tools.cfg file to the original value you noted in Step 2 on
page 148.
6 Save the t ool s. cf g file.
7 If Siebel Tools is open, then exit out of it, and then open it.
Resolving Conflicts
1 In the Import Wizard-Review Conflicts and Actions dialog box, expand the tree and then click an
object so that the Object Differences window populates.
2 Compare the object that appears in the Object Differences window to the child objects that are
described in Changes Made as a Result of Importing SIF Files on page 152.
3 Do one of the following:
a If the object appears in Changes Made as a Result of Importing SIF Files on page 152, and if
there is no conflict, then do not adjust the default setting that Siebel Tools makes.
For more information, see Example of Using the Value from the SIF File on page 150.
b If the object does not appear in Changes Made as a Result of Importing SIF Files on page 152,
then right-click the object in the Object Differences window, and then choose Repository.
For more information, see Example of Using the Value from the Repository on page 151.
c If the object appears in Changes Made as a Result of Importing SIF Files on page 152, and if
there is a conflict, then create a service request (SR) on My Oracle Support.
For more information, see Example of a Conflict That Requires Additional Assistance on
page 151.
4 If other objects appear in the Conflicting Objects window, then repeat Step 3 for each object until
all conflicts are addressed.
5 Click Next.
Example of Using the Value from the SIF File
In this situation, the object does not exist in the repository and Siebel Tools sets the Action to File
by default. For example, the Siebel Universal Agent application includes a difference for the PIM
Client Package screen in the Screen Menu Item object. There is no conflict because this is an intended
change and the PIM Client Package screen does not exist in the repository.
Example of Using the Value from the Repository
When you import the Application.sif file, Siebel Tools displays 15 objects in the Conflicting Objects
window. If you expand an object, then the Object Differences window displays the following
differences for the Siebel Universal Agent application:
Some differences for the Page Tab object
Some differences for the Screen Menu Item object, including different Text for the Account
Screen object and a different Sequence for the Activities Screen object.
These differences are not intended. The Page Tab, Account Screen, and Activities Screen objects do
not appear in Changes Made as a Result of Importing SIF Files on page 152. Therefore, you must set
Action to Repository for each of these objects in order to keep the current repository values.
Example of a Conflict That Requires Additional Assistance
Assume you import the BusinessComponent-Update.sif and the ContactDBLastUpd field of the
Employee business component includes a conflict because the field already exists in the repository.
In this situation, it is likely that the field was created earlier for a customization. This field is an
intended change and it appears in Changes Made as a Result of Importing SIF Files on page 152.
In this situation, it is recommended that you create a service request (SR) on My Oracle Support.
Alternatively, you can phone Global Customer Support directly to create a service request or get a
status update on your current SR. Support phone numbers are listed on My Oracle Support. You can
also contact your Oracle sales representative for Oracle Advanced Customer Services to request
assistance from Oracle's Application Expert Services.
Applying Changes to the Siebel Database
1 In the Object Explorer, click Table.
2 In the Tables list, issue the following query in the Name property:
S_EVT_ACT OR S_PI M_I NT_PKG OR S_PI M_I NT_FI LE OR S_PI M_I NT_PKGFL OR S_PI M_I NTFL_DEF
3 Click Apply/DDL.
4 In the Choose option dialog box, make sure the Apply option is chosen, and then click OK.
If the Warning dialog box appears, then click OK.
5 In the Apply Schema dialog box, choose Current Query in the Tables drop-down list, and then
enter the following information according to the type of database into which you are applying
this schema change. These values might be different for your environment. Check with your
database administrator if you are not sure about the correct values to enter.
For more information, see Developing and Deploying Siebel Business Applicationson the Siebel
Bookshelf 8.1 on Oracle Technology Network (OTN).
Field MSSQL Oracle DB2
Tables Current Query Current Query Current Query
Table space (Leave empty) DATA TBS_4K
152
6 Click Apply.
7 Compile and deploy the SRF.
Importing Seed Data
The following procedure describes how to import seed data.
To import seed data
1 Open the following file in a text editor:
ACR464- HOR8112\ Seed_i mpor t . bat
2 Edit the Seed_import.bat file to reflect the database, username, folder names, Siebel Tools
installation directories, and other information that is specific to your environment. The required
parameters are documented in the file.
3 Open a DOS command line and then run the Seed_import.bat file.
Changes Made as a Result of Importing SIF Files
This section describes changes that are made to the Siebel Repository as a result of importing SIF
files.
16K table space (Leave empty) (Leave empty) TBS_4K
32K table space (Leave empty) (Leave empty) TBS_32K
Index space (Leave empty) DATA TBS_4K
Storage control file (Leave empty) (Leave empty) (Leave empty)
Database user (User name) (User name) (User name)
Database user password (User password) (User password) (User password)
ODBC data source (Data source) (Data source) (Data source)
DDL file (Leave empty) (Leave empty) (Leave empty)
Field MSSQL Oracle DB2
Changes Made as a Result of Importing the Application-Update.sif File
Table 8 describes changes made to applications as a result of importing the Application-Update.sif
file.This sif file includes the new PIM Client Package screen of the screen menu item for these
applications.
Table 8. Changes Made as a Result of Importing the Application-Update.sif File
Siebel Business Applications and Siebel Industry
Applications Siebel Industry Applications
The following applications are changed:
Siebel ERM Administration
Siebel Field Service
Siebel Marketing Enterprise
Siebel Partner Manager
The following applications are changed:
Siebel Automotive
Siebel Consumer Sector
Siebel Financial Services
Siebel HTIM
Siebel Hospitality
Siebel Life Sciences
Siebel Loyalty
Siebel Power Communications
Siebel Public Sector
154
Changes Made as a Result of Importing the BusinessObject-Update.sif File
Table 9 lists the new business object components that are added into business objects as a result of
importing the BusinessObject-Update.sif file.
Table 9. Changes Made as a Result of Importing the BusinessObject-Update.sif File
Business Object Siebel Business Applications Siebel Industry Applications
Account The following business object
components are added:
Account Contact
Account Industry
Account Organization
Account Position
Account Territory
Assignment Group
Industry
The following business object
Account Address
Account Industry
Account Organization
Account Territory
Contact The following business object
Account Contact
Business Address
Contact Organization
Opportunity Contact
Organization
Position
The following business object
Account Contact
Contact Address
Contact Organization
Opportunity Contact
Employee The following business object components are added to Siebel Business
Applications and Siebel Industry Applications:
Employee Position
Employee Responsibility
Changes Made as a Result of Importing the Table-Update.sif File
Table 10 describes changes made to the S_EVT_ACT table as a result of importing the Table-
Update.sif file.
Changes Made as a Result of Importing the BusinessComponent-Update.sif File
Table 11 describes changes made to business components as a result of importing the
BusinessComponent-Update.sif file. Note that these changes apply to Siebel Business Applications
and Siebel Industry Applications except for the change to the Business Address business component.
The change to the Business Address business component described in Table 11 does not apply for
Siebel Industry Applications.
Opportunity The following business object components are added to Siebel Business
Assignment Group
Opportunity AssignmentGroup
Opportunity Position
Position The following business object components are added to Siebel Business
Assignment Group
Assignment Group Position Intersection
Table 10. Changes Made as a Result of Importing the Table-Update.sif File
Siebel Business Applications Siebel Industry Applications
Adds the following columns to the S_EVT_ACT
table:
INTEGRATION_ID
INFO_SOURCE_CD
Makes the following changes to the S_EVT_ACT
table:
Changes the length of the INTEGRATION_ID
column from 30 to 450
Adds the INFO_SOURCE_CD column
Table 11. Changes Made as a Result of Importing the BusinessComponent-Update.sif File
Business Component Change to Business Component Field
Action Adds the new CRMD Integration Id field.
Employee Adds the new ContactDBLastUpd field.
Changes the Text Length of the EMail Addr field from 50 to 100.
Table 9. Changes Made as a Result of Importing the BusinessObject-Update.sif File
Business Object Siebel Business Applications Siebel Industry Applications
156
Use the procedures in the following section to configure ACR 467.
NOTE: For more information about ACR 467 and about Siebel Financial Services Customer Order
Management for Banking functionality, see Siebel Order Management Guide Addendum for Financial
Services. To access this guide, from within My Oracle Support, navigate to the Knowledge tab and
1 Navigate to <Tools installation folder>\REPPATCH\ACR467.zip.
The ACR 467 folder contains the following subfolders:
\LMU
\SeedData
\REPOSITORY
\WORKFLOWS
\Schema
Table Asset
Table Closing Requirement Manager
Table FinancialServices
Table FinAccounts
Table Marketing
Table Order
Table Quote
3 Navigate to Tools > Import from Archive, and import the Table.sif file.
NOTE: Use the Merge option within the Import Wizard.
4 Navigate to the Siebel\tools\temp\importlog.txt file to verify that the objects imported correctly.
5 Select the table or tables that you want to apply to the physical database, click the Apply/DDL
button, and select Apply.
Contact Changes the Text Length of the Email Address field from 50 to 100.
Position Changes the Text Length of the Active Email field from 50 to 100.
Business Address Changes the Text Length of the Email Address field from 50 to 100.
Table 11. Changes Made as a Result of Importing the BusinessComponent-Update.sif File
Business Component Change to Business Component Field
6 Choose the Current Query option.
7 In the Apply Schema dialog box, enter the appropriate values for your database platform.
a For MSSQL, enter the appropriate values in the Database user, Database user password, and the
ODBC data source fields.
b For Oracle, enter the appropriate values in the Table space, Index space, Database user,
Database user password, and the ODBC data source fields.
c For DB2, enter the appropriate values in the Table space, 16K table space, 32K table space,
Index space, Database user, Database user password, and ODBC data source fields.
d For DB2/390, enter storage control file information, as well as information in the Database user,
Database user password, and ODBC data source fields.
NOTE: If you are implementing ACR 467 on DB2, you need to generate the storage control file.
For information aobut how to do this, see Implementing Siebel Business Applications on DB2 for
z/OS. This guide is available on the Siebel Bookshelf 8.1at http://www.oracle.com/technetwork/
documentation/siebel-087898.html.
8 Verify that the changes have been applied to the database.
CAUTION: You must import the Table.sif file before you import the EIM.sif file.
EIM Activity
EIM Common SIA
EIM Quote
10 Importing the EIM.sif file using the Tools > Import from Archive function. Use the Merge option
within the Import Wizard.
11 Navigate to the Siebel\tools\temp\importlog.txt file to verify that the objects imported correctly.
12 Repeat Step 5 through Step 7 to apply the DDL for EIM.sif.
that the SymStrPrefix entry has been set to SBL_
[Siebel]
..
.; SymStrPrefix parameter needs to be X_ for Siebel customers.
SymStrPrefix = SBL_
..
Account
Account (SSE)
Asset Management
Cfg JS
158
Contact
Contact (SSE)
FINS Account Origination (Create this project if it does not already exist.)
FINS Financial Services
FINS Mortgage Application
FINS Needs Analysis
FINS Requirement Template
FINS Retirement Planning
Household
LS Pharma Call
LS Pharma Signature
MACD Performance
Oppty (SSE)
Order Entry
Quote
Quote (UI)
Symbolic Strings
Corresp
Account
Mail Agent
Accessibility
FINS Captive Finance - Fin Acct
LS Pharma Compliance
PUB Case
Schema
Product Data Services
15 Import the rest of the SIF files from the REPPATCH\ACR467\REPOSITORY folder into Siebel Tools
using the Import from Archive function.
If you have not locked the required projects, you may receive a warning error message. Use the
Overwrite option.
16 Import the SIF files from the following subfolders under the REPPATCH\ACR467\REPOSITORY
folder:
Applet
Application
Business Component
Business Object
Business Service
Integration Object
Project
Screen
Symbolic String
.
Use the following procedure to perform batch import of the SIF files.
To perform batch import for ACR 467
Run the following command:
SET PCDTOOLSPATH=. . \ . . \ . .
SET PCDDATASRC=Ser ver Dat aSr c
SET PCDUSERNAME=<LOGI N>
SET PCDPASSWORD=<PWD>
%PCDTOOLSPATH%\ bi n\ si ebdev. exe / c t ool s. cf g / d %PCDDATASRC%/ u %PCDUSERNAME%/ p
%PCDPASSWORD%/ bat chi mpor t " Si ebel Reposi t or y" mer ge " . \ Appl et "
" . \ Log\ Appl et I mp. l og"
%PCDPASSWORD%/ bat chi mpor t " Si ebel Reposi t or y" mer ge " . \ Appl i cat i on"
" . \ Log\ Appl i cat i onI mp. l og"
%PCDPASSWORD%/ bat chi mpor t " Si ebel Reposi t or y" mer ge " . \ Busi ness Component "
" . \ Log\ BusCompI mp. l og"
%PCDPASSWORD%/ bat chi mpor t " Si ebel Reposi t or y" mer ge " . \ Busi ness Obj ect "
" . \ Log\ BusObj I mp. l og"
%PCDPASSWORD%/ bat chi mpor t " Si ebel Reposi t or y" mer ge " . \ Busi ness Ser vi ce"
" . \ Log\ BusSvcI mp. l og"
%PCDPASSWORD%/ bat chi mpor t " Si ebel Reposi t or y" mer ge " . \ I nt egr at i on Obj ect "
" . \ Log\ I nt Obj I mp. l og"
160
%PCDPASSWORD%/ bat chi mpor t " Si ebel Reposi t or y" mer ge " . \ Li nk" " . \ Log\ Li nk. l og"
%PCDPASSWORD%/ bat chi mpor t " Si ebel Reposi t or y" mer ge " . \ Pi ck Li st "
" . \ Log\ Pi ckLi st I mp. l og"
%PCDPASSWORD%/ bat chi mpor t " Si ebel Reposi t or y" mer ge " . \ Scr een"
" . \ Log\ Scr eenI mp. l og"
%PCDPASSWORD%/ bat chi mpor t " Si ebel Reposi t or y" mer ge " . \ Symbol i c St r i ng" " . \ Log\
SymSt r I mp. l og"
%PCDPASSWORD%/ bat chi mpor t " Si ebel Reposi t or y" mer ge " . \ Vi ew" " . \ Log\ Vi ewI mp. l og"
%PCDPASSWORD%/ bat chi mpor t " Si ebel Reposi t or y" mer ge " . \ EI M" " . \ Log\ EI MI mp. l og"
Use the following procedure to import the seed data for ACR 467.
To import ACR 467 seed data
a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC),
c Enter a data source name (such as DevelopmentDB).
database.
e 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\ACR467.
4 Depending upon the language that you are installing, complete either Step 5 or Step 6.
5 For ENU customers:
a Run the following command:
<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install
Directory>\REPATCH\ACR467\SeedData\ENU\Seed_ACR467.dat/l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools
Install Directory>\REPATCH\ACR467\SeedData\ENU\ACR467_seedimp.inp /q -1 /w n /e n /t
n /x R /n 100 /h log
b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
6 For languages other than ENU, complete the following:
Customers who are installing languages other than ENU need to import two .dat files - the
base ENU seed.dat and the locale specific seed_locale_XXX.dat, where XXX is the language
code.
a Run the following command for seed.dat:
Directory>\REPATCH\ACR467\SeedData\Seed_ACR467.dat/l <Tools Install
Install Directory>\REPATCH\ACR451\SeedData\ ACR467_seedimp.inp /q -1 /w n /e n /t n /
x R /n 100 /h log
<ODBC Source Name> - Replace with the ODBC name created in Step 1
b Run the following command for seed_locale_XXX.dat:
<Tools Install Directory>\bin\dataimp /u SADMIN /p sadmin /f <Tools Install
Directory>\REPATCH\ACR467\SeedData\Local\<LANG>\seed_locale_xxx.dat /l <Tools
Install Directory>\temp\dataimp_seed_lang.log /c <ODBC Source Name> /d <Table Owner>
/i <Tools Install Directory>\REPATCH\ACR467\SeedData\ENU\kzhou.inp /q -1 /w y /e n /t n
/x R /n 100 /h log
<Tools Install Directory> - Replace with your Tools install directory
<ODBC Source Name> - Replace with ODBC name created in Step 1
c Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure import completed
successfully.
7 The following steps are only necessary for customers who are installing languages other than
ENU:
a Within Siebel Tools, navigate to Tools > Utilities > Locale Management to import LMU files for
the specific language from the LMU folder into Siebel Tools.
Target Language = <Specific Language>
c Click the Import tab, browse to locate the LMU file you want to import, and click Import.
162
9 Within Siebel Tools, navigate to Menu > View > Options, select the Scripting tab, and specify the
following path for the browser script compilation folder.:
\\<Server IP address>\<SWE server Installed Location>\eappweb\PUBLIC\enu
10 Navigate to Tools > Compile Projects > All Projects option, compile the projects, and save the
SRF file to <Siebel Server Install folder>\objects\ENU\siebel_sia.srf on the installed Siebel
Server.
12 Import the workflows listed in the following table into the Siebel application:

b Right-click on Workflow Processes (the right-side pane) and import the .xml file into Siebel Tools
from the Workflows folder. Refer to the list of workflows in the preceding table to know which
project these workflows need to be imported into.
Process Name
New/
Modified? Project
FINS AcctOrig Apply For Product - Account New FINS Account Origination
FINS AcctOrig Apply For Product - Contact New FINS Account Origination
FINS AcctOrig Apply For Product - Household New FINS Account Origination
FINS AcctOrig AutoQuote New FINS Account Origination
FINS AcctOrig Identity Check Process New FINS Account Origination
FINS AcctOrig New Products & Services Process New FINS Account Origination
FINS AcctOrig Profile Process - Order New FINS Account Origination
FINS AcctOrig Set Applicant Group - Order Sub New FINS Account Origination
FINS AcctOrig Set Applicant Group - Order New FINS Account Origination
FINS AcctOrig Set Applicant Group - Quote Sub New FINS Account Origination
FINS AcctOrig Set Applicant Group - Quote New FINS Account Origination
SIS OM Active Order Sub-Process - Contact Modify SIS OM Base Architecture
SIS OM Disconnect Products & Services Process -
Contact
Modify SIS OM Base Architecture
SIS OM Modify Products & Services Process -
Contact
SIS OM New Products & Services Process -
Contact
SIS OM Suspend / Resume Products & Services
Process - Contact
c Check the status of the workflow process. If it is In-Progress, then make it complete by deploying
the Workflow process. Do not click the Deploy + Activate button, as doing so will yield an error
message. Click the Deploy button only.
modified workflows from the list. Ignore the error and click Yes.
d Repeat Step b through Step c for of all the workflows in the folder.
e Log into the Siebel application as an administrator.
f Navigate to Site Map > Administration - Business Process > Workflow Deployment > Repository
Workflow Process.
g Query for the workflow processes and activate them.
Use the instructions in the following sections to install and configure ACR 471.
Installing ACR 471
1 Launch Siebel Tools connected to the server data source.
2 Navigate to Projects in the Object Explorer, and lock the following projects:
ISS Promotion Integration
Symbolic Strings
ISS Promotion Admin
UMSUI
ISS Promotion Workflow
3 Create a repository project called Headless Configuration.
4 In the tools.cfg file, change the SymStrPrefix = X_ parameter to SymStrPrefix = SBL_.
5 In Object Explorer, navigate to Symbolic String and create new records with the following values:
Name = SBL_PROM_AUTOMATCH
Current String Value = Promotion Automatch
Translate Flag = TRUE
Type = Conversion
NOTE: You may need to expose this object type. To do so, navigate to View > Options. In the
Object Explorer tab, check the checkbox for Symbolic Strings.
Name = SBL_APPLY_PROM_DEF
164
Current String Value = Apply Promotion Defaults
Type = Conversion
Project = Symbolic Strings
Name = SBL_LOG_HDLS_ERR
Current String Value = Log Error
Type = Conversion
Project = Symbolic Strings
6 Use the following steps to import the CSSHeadlessCfgService class:
a Navigate to Tools > Import From Archive, and import the Class - CSSHeadlessCfgService.sif file.
NOTE: If the "This operation should only be performed while connected to your local
database" message appears, click Yes.
b Choose the Merge option in the Conflict Resolution dialog box, and follow the steps to complete
the import.
7 Import the Business Service - Headless Configuration Service.sif file using the steps in Step 6.
8 Import the Business Service - ISS Promotion Management Service.sif file using the steps in
Step 6.
9 Import the Applet - UMF Message List SI.sif file using the steps in Step 6.
10 In Object Explorer, navigate to Workflow Process and import the workflow files in the order given
by the table below:
a Right-click on the workspace and select Import Workflow Process.
b Choose the <workflow_name>.xml file you want to import, and add it to its corresponding
project.
c Click Publish/Activate to change each workflows status from In Progress to Complete.
11 Within Object Explorer, navigate to Business Component, and search for the ISS Promotion Item
Attribute Value business component.
SI Workflow File Project
1) SIS OM Get Future Asset SubProcess.xml SIS OM Base Architecture
2) SIS OM Sync Delta SubProcess.xml SIS OM Base Architecture
3) ISS Promotion Upgrade Process.xml ISS Promotion Workflow
4) Headless Configuration Web Service.xml Headless Configuration
12 Set the Sort Specification value to Created.
13 Compile the following locked projects into an SRF file:
Headless Configuration
Symbolic Strings
ISS Promotion Admin
UMSUI
14 Unlock all projects, and log out of Siebel Tools.
Setting Up the Application
1 Launch the application connected to the server data source and refer to the SRF that you
compiled in Step 13 as a Siebel administrator.
2 Navigate to Administration - Business Processes > Workflow Deployment.
3 In the Repository Workflow Processes applet, query for the following workflows and activate
them:
SIS OM Get Future Asset SubProcess
SIS OM Sync Delta SubProcess
ISS Promotion Upgrade Process
Seed Data
Signals
Signal Name Action
Sequence Type Service Name Service Method
HdlsCfgSvcLoad 1 Business Service ISS Copy Service LoadEAI
HdlsCfgSvcLoad
ABO
1 Workflow SIS OM Get
Future Asset
SubProcess
RunProcess
166
Adding System Preferences
Navigate to Administration - Application > System Preferences and add a new system preference
called Promotion Automatch with System Preference Value = "Y"
Setting Up UMF
Use the following procedure to set up UMF.
To set up UMF
1 Navigate to view Administration - Order Management > Message Types, navigate to the All
Message Types applet, and in the All Messages type applet, add new records with the values in
HdlsCfgSvcSync 1 Business Service Remote Complex
Object Instance
Service
SyncInstance
HdlsCfgSvcSync
ABO
1 Workflow SIS OM Sync
Delta SubProcess
7.8 [SIS OM
Sync Delta
SubProcess]
8.1 [SIS OM
Sync Delta
SubProcess]
Run Process
Signal Name Action
2 For the Headless Configuration Message record, in the Payload view tab, add four new records,
with the following values for 'Payload Field'
Error Text
Id
Product Name
Promotion Instance Id
3 For the Headless Configuration Message record, in the Responses view tab, add two new records
with the values in the following table:
Adding Web Services
Use the following procedure to add web services.
To add web services
1 Navigate to Administration - Web Services > Inbound Web Services, and add a web service with
the following details:
Name Display Mode Group Title Full Text
Headless
Configuration
Message
Passive Promotion Product Structure
Changed
Product [Product
Name] ([Id])
associated to
promotion
[Promotion
Instance Id] has
changed: [Error
Text]
Headless
Configuration
Error Message
Passive Promotion Undo Apply
Promotion
A non-
proceedable error
was detected
during processing
of your last
request. Your last
request was
rolled back.
Sequence Name
1 Accept
2 Reject
168
2 Click Clear Cache.
For information about the process of enabling the automatic configuration of customizable products,
see Siebel Order Management Guide.
Inbound Web Service
Namespace Name Status
http://siebel.com/OrderManagement/
HeadlessConfiguration
HeadlessConfigurationWS Active
Service Ports
Name Type
Business
Service/
Business
Process
Name Transport Address Binding
HeadlessConfigurationPort Workflow
Process
Headless
Configuration
Web Service
HTTP http://<webserver>/
eai_<lang>/
start.swe?SWEExtSou
rce=SecureWebServic
e&SWEExtCmd=Exec
ute&UserName=<Use
rName>&Password=
<Password>
For example, http://
sdc78187svod/
eai_enu/
start.swe?SWEExtSou
rce=SecureWebServic
e&SWEExtCmd=Exec
ute&UserName=SAD
MIN&Password=SAD
MIN
SOAP_DOC_LITERAL
SOAP_DOC_LITERAL
Operations
Name Method Display Name Authentication Type
HeadlessConfiguration RunProcess None
Instructions for ACR 474 and ACR 508
This section provides information, instructions, and guidelines for installing ACR 474 and ACR 508.
CAUTION: Before you apply ACR 474, you must apply schema changes and import seed data from
ACR 463. Repository changes for ACR 474 include repository changes that were made in ACR 463.
For information about how to configure ACR 463, see Instructions for ACR 463 on page 108.
Release Notes for ACR 474 and ACR 508
The following topic documents known issues with ACR 474 and ACR 508.
NOTE: For known issues that affect the installation of AIA 11.1, see Siebel Maintenance Release
Guide, Version 8.1.1.6 on My Oracle Support. To access this guide, from within the Knowledge tab,
USERS CAN ASSOCIATE PRODUCTS THAT ARE NOT RELEASED WITH
NEW PRODUCTS WITH ACTIVEWORKSPACE
Category: Web Service
Subcategory: Other
Product Version: AIA 11.1
Bug ID: 12396630
When users import the generated WSDL file into SOAP UI, create a product using
SWIProductImportUpsert, and then create a product by associating it with products that are not yet
released but that are under the same workspace and specify the ActiveWorkspaceFlag as 'N', the
script does not throw an error stating that the products have not been released yet.
1 From within the Siebel application, navigate to Site Map > Administration Integration > Data Map
Editor, and query for the SWI Product Structure object map.
2 In the bottom applet, query for the SWI ISS Product Structure Admin BusComp component map.
3 Within the Integration Field Map applet, click New, and enter "Product Name" in the Target Field
Name field.
4 In the Source Expression Field Name, enter value [Component Product Name] and save the
record.
Editor, and query for the SWI Admin ISS Product Class Structure object map.
6 In the bottom applet, query for the SWI Structure Admin component map.
7 Within the Integration Field Map applet, click New, and enter Product Name in the Target Field
Name field.
8 In Source Expression Field Name, enter value [Component Product Name].
9 Save the record and log out of the Siebel application.
170
ERROR IN IMPORTING AN XML FILE WITH EXPRESSION IN THE
SOURCE FIELD
Category: Application Deployment Manager
Subcategory: Data Transformation (EAI)
Bug ID: 12952312
1 Navigate to Site Map > Administration-Integration > Data Map Editor.
2 Import the XML file from <Tools>/REPPATCH/AIA11.1/Xml folder.
3 Within the Integration Object Map applet, query for .SWI Asset Integration.
4 Within the Integration Component Map applet, query for Line_Item_to_Line_Item.
5 Click New, and add a record in the Integration Field Map applet with the following values:
Source Expression: "insert"
Target Field Name: operation
6 Query for the Status field and change the source expression:
Source Expression: IIF([Status] IS NULL, LookupValue ("IMPL_PHASE", "Active"),[Status])
Target Field Name : Status
Source Expression: "insert" Target Field Name: operation
PROMOTION SYNC: PERIOD, GRACE PERIOD AND THEIR UOM ARE NOT
SYNCHED TO SIEBEL
Subcategory: Other
Bug ID: 12651202
Sync BillofMaterial changes the values of Period, Period UOM and Grace UOM to the default values.
Use the following workaround to address this issue
Editor, and query for the SWI Promotion integration object map.
2 In the bottom applet, query for the SWI Promotion Header component map.
3 Within the Integration Field Map applet, click Query, and enter Grace Period UOM in the Target
Field Name field.
4 In Source Expression Field Name, change the value from IIF([Grace Period UOM] IS
NULL,LookupValue("PROMO_PERIOD_CD", "Days"),[Grace Period UOM]) to [Grace Period UOM],
and save the record.
5 Within the Integration Field Map applet, click Query, and enter "NRC Qty" in Target Field Name.
6 In Source Expression Field Name, change the value from IIF([NRC Qty] IS NULL,"1",[NRC Qty])
to [NRC Qty], save the record, and log out of the Siebel application.
7 Within the Integration Field Map applet, click Query, and enter Period in Target Field Name.
8 In Source Expression Field Name, change the value from IIF([Period] IS NULL,"1",[Period])to
[Period], save the record, and log out of the Siebel application.
9 Within the Integration Field Map applet, click Query, and enter Period UoM in Target Field Name.
10 In Source Expression Field Name, change the value from IIF([Period UOM] IS
NULL,LookupValue("PROMO_PERIOD_CD", "Years"),[Period UOM])to [Period UoM], save the
record, and log out of the Siebel application.
251D ST2: NOTIFICATION TO SCE FROM SIEBEL MUST INCLUDE THE EFFECTIVE DATES
Category: Oracle Order to Activate Integration
Bug ID: 9471608
Whenever a product class is created in the Siebel application, a notification is sent to the SCE
"product to service mapping specialist". The notification must consist of effective dates of the product
class. The notification sent by the Siebel application does not have the effective dates.
Use the procedures in the following section to address this issue.
Product Class Email Notification
Use the following procedure to change the business object name.
To change the LOV values for Product Class Definition
1 Navigate to the Administration - Data > List Of Values view.
2 Query for Type equals COMM_RECIP_SRC and Display Value equals Product Class Defn BC.
3 Change the values in the Language-Independent Code column to SWI ISS Class VOD BusComp
(Notify).
4 Click Clear Cache to clear the cache.
6 Query for Type equals COMM_RECIP_SRC and Display Value equals Product Class Defn BO.
7 Change the values in the Language-Independent Code column to SWI Admin ISS Class Definition
Use the following procedure to edit/configure email template text.
172
To edit/ configure email template text
1 Create a notepad file called "Attribute_Version_Template.txt" and add the following values:
Attribute Version Details
========================
________________________________________
| Effective Start Date: [Required Start Date]
|
| Effective End Date: [Required End Date]
|
| VOD Version Number: [Version]
________________________________________
2 Navigate to Administration - Communication > All Templates > Template Items.
3 Query for "Attribute Defn Template" and click on the Template Items View.
4 Attach the "Attribute_Version_Template.txt" file created in Step 1 in the template item.
5 Change the Iteration Child Business Component to "SWI Attribute Versions BusComp (Notify)"
and check Substitute Values and Message Body.
To change the LOV values
2 Query for Type equals COMM_RECIP_SRC and Display Value equals Attribute Defn BC.
3 Change the values in the Language-Independent Code column to SWI Attribute VOD BusComp
(Notify).
6 Query for Type equals COMM_RECIP_SRC and Display Value equals Attribute Defn BO.
7 Change the values in the Language-Independent Code column to SWI Admin Attribute VOD
Definition.
Use the following procedure to change the LOV values for Product Class Email Notification.
Attribute Details Email Notification
Use the following procedure to change the business object.
To change the BO name to communication template
1 Navigate to Administration - Communication > All Templates > Templates.
2 Query for "Product Class Template" and click on Simple View.
3 In Pick Available Substitutions change the object to "SWI Admin ISS Class Definition".
Use the following procedure to edit/configure email template text.
To edit/ configure email template text
1 Create a notepad file called "Class_Version_Template.txt" and add the following values:
Product Class Version Details
=============================
_____________________________________________________
| Effective Start Date: [Required Start Date]
|
| Effective End Date: [Required End Date]
|
| VOD Version Number: [Version]
______________________________________________________
3 Query for "Product Class Template" and click on Template Items View.
4 Attach the "Class_Version_Template.txt" file created in Step 1 in the template item.
5 Change the Iteration Child Business Component to"SWI ISS Product Versions BusComp (Notify)"
and check Substitue Values and Message Body.
Use the following procedure to change the LOV values for Attribute Email Notification.
To change the LOV values
2 Query for Type equals COMM_RECIP_SRC and Display Value equals Product Class Defn BC.
3 Change the values in the Language-Independent Code column to SWI ISS Class VOD BusComp
(Notify).
6 Query for Type equals COMM_RECIP_SRC and Display Value equals Product Class Defn BO.
7 Change the values in the Language-Independent Code column to SWI Admin ISS Class Definition
174
SET PRICING COMMIT TYPE AND DYNAMIC DISCOUNT METHOD
Subcategory: Other
Bug ID: 11724422
This bug enhances the Product/Promotion Web Service to support more attributes.
Use the following workaround to address this issue.
To address Bug 11724422
1 Within the Siebel application, navigate to Site Map > Administration Integration > Data Map
Editor.
2 Query for the "SWI Promotion" integration object map.
3 Query for "SWI Promotion Header" integration component map in the bottom applet.
4 Click New in the Integration Field Map Applet, and enter the following values:
a Enter "Pricing Commit Type" in Target Field Name.
b In the Source Expression field name enter "IIF([Pricing Commit Type] IS
NULL,LookupValue("PRICE_OVERRIDE_TYPE", "Dynamic"),[Pricing Commit Type])"
5 Save the record.
6 Click New in the Integration Field Map Applet, and enter the following values:
a Enter "Dynamic Discount Method" in Target Field Name
b In the Source Expression field name enter "IIF([Dynamic Discount Method] IS NULL ,
LookupValue("DISCOUNT_OVERRIDE_TYPE", "Amount") ,[Dynamic Discount Method])"
7 Save the record and close the Siebel application.
ERROR UPDATING A PROMOTION IN SIEBEL WITH SYNCCHILD FLAG SET AS 'Y'
Subcategory: Other
Bug ID: 11842102
To address Bug 11842102
1 Within the Siebel application, navigate to Site Map > Administration Integration > Data Map
Editor.
2 Query for the "SWI Promotion Override Internal to External" integration object map.
3 Query for "Product Components" integration component map in the bottom applet.
4 Change the Source Componenet Map to SWI ISS Promotion Product Component Override from
SWI ISS Promotion Product Components
5 Save the record and close the Siebel application.
Unable to Merge Contacts after Applying Siebel OnDemand/OnPremise
Category: Data Quality
Subcategory: Deduplication
Product Version: 8.1.1.4
Change Request: 12-204Y58X
While merging two contacts, an error is thrown:Could not find 'Class' Named 'Merge Service ODOP'.
This object is inactive or non-existent. (SBL-DAT-00144)
The MergeAction runtime event refers to the the Merge Service ODOP business service, which is not
present in the repository.
To avoid this error, inactivate the MergeAction runtime event:
1 Log into the Siebel application, and navigate to Administation - Runtime Events > Action Sets.
2 Query for the MergeAction action set.
3 Uncheck the Active check box to inactivate this action set.
4 Navigate to the Events view, and from the applet menu, select the Reload Runtime Events menu
option.
MOVE ORDER TRANSFER RESULTS IN EMPTY STATUS AS OF HEADER FIELD
Category: Comm Media Energy
Subcategory: Order Management
Change Request: 12-1XTI4Q6
MOVE ORDER TRANSFER RESULTS IN EMPTY STATUS AS OF HEADER FIELD.
1 Within Siebel Tools, navigate to Business Component and query for MACD Order Entry - Orders
or MACD Quote.
2 In MACD Order Entry - Orders add a field with the following values:
Name: As Of Date
Column: STATUS_DT
Type: DTYPE_UTCDATETIME
3 In MACD Quote, add a field with the following values:
Name: As Of Date
176
Column: STATUS_DT
Type: DTYPE_UTCDATETIME
4 Navigate to Integration Object, and query for SIS OM Order or SIS OM Quote.
5 Add the Status As Of Date field to IC MACD Quote, and add the As Of Date field to IC MACD Order
Entry - Orders.
6 Navigate to Business Service, and query for "SIS OM PMT Service".
7 Navigate to Business Service User Properties, and add a new user property with the following
values:
Name "SIS OM Quote.Header:SIS OM Order.Header Map 302"
Value: "[Status As Of Date]:[As Of Date]"
8 Compile the changes to the SRF.
CLEAR FULFILLMENT STATUS AND STATUS CONTEXT FOR CANCEL ORDER
Subcategory: Billing Management
Change Request: 12-1ZVR997
CLEAR FULFILLMENT STATUS AND STATUS CONTEXT FOR CANCEL ORDER
1 Log into Siebel Tool, and query for the SWICancel Sales Order workflow.
2 Click Revise in the WF/Task Editor Toolbar to create a new version of the completed workflow and
increment the version number
3 Right-click SWICancel Sales Order (the one with status In Progress) and select Edit Workflow
Process.
4 In the Workflow Designer, select the Siebel Operation Step called "Update Fulfillment Mode and
Status for Header".
5 Under the Input Field Argument tab in the Multi-Value Property Window for the Update Fulfillment
Mode and Status for Header operation step, add the following two new records to configure the
input arguments:
6 Add a new Siebel Operation Step between "Update Fulfillment Mode and Status for Header"
(Siebel Operation Step) and "Submit" (Sub Process).
Field Name Type Value
Fulfillment Status Code Literal
Back Office Error Text Literal
7 Right-click, select View Properties Window and modify the properties of the Siebel Operation Step
as follows:
8 Under the Input Field Argument tab in the Multi-Value Property Window for the preceding step,
add the following new records to configure the input arguments:
9 Under the Search Spec Input Arguments tab in the Multi-Value Property Window for the preceing
step, add the following new records to configure the search specification:
10 Save all of your changes and publish/activate the workflow.
PROBLEM WITH ADJUSTMENT EFFECTIVE DATE
Subcategory: Billing Management
Change Request: 12-1ZOI2LP
The Effective Adjustment field stores only the Date field not the time value.
Before you begin, within My Oracle Support, navigate to the Knowledge tab and search for Article ID
557191.1. Copy the FR_12-1ZV9SD1_AIA25_Invoice.sif file attached to the article.
Table Changes
Use the following procedure to edit the S_INV_ADJ table.
Business Component Order Entry - Line Items
Business Component Order Entry - Line Items
Operation Update
Name Update Fulfillment Status and Status Context for Line Items
Field Name Type Value
Fulfillment Status Code Literal
Status Context Literal
xpression Business
Component
Filter Business
Component Type Search Specification
Order Entry - Orders Order Entry - Line
Items
Expression "[Order Header Id] ='"
+ [&Object Id] + "'"
178
To edit the S_ I NVOI CE_ ADJ table
1 Log into Siebel Tools, and from the menu bar, select Import from Archive.
2 Import the "FR_12-1ZV9SD1_AIA25_Invoice.sif " file using merge as the Conflict Resolution
Option.
3 Query for the 'S_INVOICE_ADJ' OR 'S_INVC_ADJ_ITEM' tables.
4 Select the rows and click the Apply/DDL button.
5 Compile the changes to the srf.
Business Component Changes
To edit the CMU Billing I nvoice Adj ustment BC
1 Log into Siebel Tools, and query for the CMU Billing Invoice Adjustment business component.
2 Change the following column for the Adjustment Effective Date field for the business component:
3 Save the changes, and then compile them to the SRF.
To edit the CMU I nvoice Adj ustment BC
1 Log into Siebel Tools, and query for the CMU Invoice Adjustment business component.
2 Change the following column for Adjustment Effective Date field:
To edit the FS I nvoice Adj ustment BC
1 Log into Siebel Tools, and query for the FS Invoice Adjustment business component.
2 Change the following column for the Adjustment Effective Date field:
Name Value
Type DTYPE_UTCDATETIME
Name Value
Name Value
To edit the SI A I nvoice Adj ustment External I tems BC
1 Log into Siebel Tools, and query for the SIA Invoice Adjustment External Items business
component.
3 Save the changes, and them compile them to the SRF.
To edit the CMU Billing I nvoice Adj ustment External I tems BC
1 Log into Siebel Tools, and query for the CMU Billing Invoice Adjustment External Items business
component.
3 Save your changes, and then compile them to the SRF.
To edit the CMU SI A I nvoice Adj ustment External I tems BC
1 Log into Siebel Tools, and query for the CMU SIA Invoice Adjustment External Items business
component.
To edit the CMU I nvoice Adj ustment External I tems BC
1 Log into Siebel Tools, and query for the CMU Invoice Adjustment External Items business
component.
Name Value
Name Value
Name Value
Name Value
180
Integration Object Changes
To edit the CMU Request Adj ustment I O
1 Log into Siebel Tools, and query for the CMU Request Adjustment integration object.
2 Query for FS Invoice Adjustment integration component.
3 Change the type for the Adjustment Effective Date integration component field:
4 Query for the SIA Invoice Adjustment External Items integration component.
5 Change the following Data Type for the Adjustment Effective Date integration component field:
To edit the CmuRequestAdj ustmentI o I O
1 Log into Siebel Tools, and query for the CmuRequestAdjustmentIo integration object.
2 Query for the FS Invoice Adjustment integration component.
3 Change the type for the Adjustment Effective Date integration component field:
4 Query for the SIA Invoice Adjustment External Items integration component.
Name Value
Data Type DTYPE_UTCDATETIME
External Data Type DTYPE_UTCDATETIME
Name Value
Name Value
5 Change the Data Type for the "Adjustment Effective Date integration component field:
PRODUCT SYNC FAILS FROM SIEBEL TO BRM
Area: Comm/Energy
Subarea: Order Management
Product Version: Siebel 8.1.1.3 Fix Pack
Change Request: 12-1YOWCOT/Bug # 9851535
In Siebel 8.1.1.3, product synchronization between the Siebel application and BRM fails.
To address Bug 9851535/ CR 12- 1YOWCOT
Editor, and query for the Product Integration integration object map.
2 In the bottom applet, query for the Product integration component map from the bottom applet.
3 Within the Integration Field Map applet, click Query, and enter Pricing Commit Type in the
Target Field Name field.
4 In Source Expression Field Name, enter "IIF([Pricing Commit Type] IS
NULL,LookupValue("PRICE_OVERRIDE_TYPE", "Dynamic"),[Pricing Commit Type])".
5 Save the record.
6 Within the Integration Field Map applet, click Query, and enter "Dynamic Discount Method" in
Target Field Name.
7 In Source Expression Field Name, enter "IIF([Dynamic Discount Method] IS NULL ,
LookupValue("DISCOUNT_OVERRIDE_TYPE", "Amount") ,[Dynamic Discount Method])".
8 Save the record and log out of the Siebel application.
Error Message Occurs When Variable Maps Released
Area: Comm/Energy
Subarea: Order Management
Change Request: 12-1YK6RG0
Name Value
182
To address CR 12- 1YK6RG0
1 From within the Siebel application, navigate to Site Map > Administration - Order Management
> Variable Maps and query for the"Default Pricing Variable Map - Row Set" variable map.
2 Rename the variable map to "Default Pricing Variable Map - Row Set - original".
3 Copy the variable map from the applet-level menu, and rename it as "Default Pricing Variable
Map - Row Set".
4 Lock the variable map and then release it.
5 Follow Step 1 through Step 4 for the "Default Pricing Eligibility Variable Map - Row Set" variable
map.
Siebel Workflow Process Manager Leaks Memory
Product Version: Siebel 8.1.1.1 QF7103
Change Request: 12-1Y0AZBZ
Siebel workflow process manager leaks memory and crashes in performance, scalability, and
reliability (PSR) testing after 20 hours of running with zero seconds of think time.
Workaround: Enable memory-based recycling on workflow process manager. For information about
configuring memory-based server component recycling, refer to Siebel System Administration Guide
on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.
Error Messages Translated Incorrectly
Change Request: 12-1VBS4SZ, 12-1VBS4UF, 12-1VBS4VL
To address CR 12- 1VBS4SZ, CR 12- 1VBS4VL, and CR 12- 1VBS4VL
1 Navigate to Administration - Data Validation > Validation Messages screen and query for the
following Message Code:
SWI_PROD_VAL_ASSET or SWI_PROD_VAL_ORDER or SWI_PROD_VAL_QUOTE
2 Add the missing translations in the Translations applet.
Follow-On Orders Can Be Submitted Before Base Orders
Change Request: 12-1XTI4LP
No error occurs when a Follow On order is submitted after the Base Order is cancelled.
To address CR 12- 1XTI 4LP
1 Within the Siebel application, edit the Change the Submit Order workflow
(SISOMBillingSubmitOrderWebService) to add this logic:
a For each root line item, check if it has Base Order Line Item Id.
b Get the Order Id of the Base Order Line Item Id.
c Check if the status of the order is Pending. If it is Pending, the base order was not submitted.
Enter an error message saying, 'Submit base order %1 before follow-on order'.
NOTE: Implement this logic only if you are using follow-on orders, as this logic will affect the
time that it takes to submit an order.
Follow-On Orders Can Be Submitted Before Base Orders
Change Request: 12-1XTI4NO
Follow-On orders can be submitted for Cancelled Base Order.
To address CR 12- 1XTI 4NO
1 Within the Siebel application, edit the Change the Submit Order workflow
(SISOMBillingSubmitOrderWebService) to add this logic:
a For each root line item, check if it has Base Order Line Item Id.
b Get the Order Id of the Base Order Line Item Id.
c Check if the status of the order is Pending. If it is Pending, the base order was not submitted.
Enter an error message saying, 'Submit base order %1 before follow-on order'.
NOTE: Implement this logic only if you are using follow-on orders, as this logic will affect the
time that it takes to submit an order.
Sales Order Form Buttons Not Disabled After Cancel Order Starts
184
Product: Siebel 8.1.1.1 QF7103
Change Request: 12-1XTI4UE
After clicking the Cancel Order button, all other buttons on the Sales Order form are not disabled,
so users can press buttons to interfere with cancel processing.
To address CR 12- 1XTI 4UE
1 Navigate to Siebel Tools > Applets and query for "Order Entry - Order Form Applet Dashboard
(Sales)".
2 Navigate to Applet User Properties.
3 Query for CanInvokeMethod*, and verify that all of the buttons that need to be disabled are
present. If they are not present, you need to create CanInvokeMethod:Method name value
IIf([Active],IIf(([Status] = LookupValue('FS_ORDER_STATUS','Cancel pending')) OR ([Status] =
LookupValue('FS_ORDER_STATUS','Cancelled')) OR ([Status] =
LookupValue('FS_ORDER_STATUS','Pending Cancel')), 'FALSE','TRUE'),'FALSE')
4 For existing CanInvokeMethod*, append the value "IIf(([Status] =
LookupValue('FS_ORDER_STATUS','Cancel pending')) OR ([Status] =
LookupValue('FS_ORDER_STATUS','Cancelled')) OR ([Status] =
LookupValue('FS_ORDER_STATUS','Pending Cancel')), 'FALSE','TRUE'),'FALSE')" with logical OR
operator
5 Compile the changes.
COPY ORDER DOES NOT ASSIGN NEW ASSET INTEGRATION ID FOR COPIED ORDERS
Change Request: 12-1XVFM9R
To address CR 12- 1XVFM9R
It is recommended that you use the Favorites menu option instead of the Copy Orders menu
option for Asset-Based Ordering (ABO) flows. This is because copying AssetIntegrationId does
not work for new orders, and Modify or Delete orders should not generate new
AssetIntegrationIds.
CR 12-1TU8OYZ
Description: The Discount Override fix is not working in MACD for Non-Residential Accounts
(asset-quote).
Workaround: Contact Technical Support for the workaround for this issue.
CR 12-1TK6WV1
Description: Suspend/Resume and move charges are applied to Simple Service Bundles in
Nested SBs after reprice.
Workaround: Use Reprice to see all charges.
Bug # 8979872/CR 12-1UPWTKJ
Description: Error upon clicking the Revise button within Sales Order > Line Items tab.
Workaround: Use the following procedure to address this issue.
To address Bug #8979872/ CR 12- 1UPWTKJ
2 Within the Object Explorer, select Applet.
3 Query for the Order Entry - Order Form Applet Dashboard (Sales) applet.
4 Modify the applet user property sequence to:
Name: Named Method 1: Revise Order
Value: INVOKE, ReviseCopyOrder
Name: Named Method: ReviseOrder
Value: 'INVOKESVC', 'Workflow Process Manager', 'RunProcess', '"ProcessName"',
'"SWIReviseOrderValidation"', '"RowId"', '[Id]'
5 Save the changes and compile the applet to the SRF.
CR 12-1UVNZ65
Description: Net Price is carried forward for One-Time Products in MACD Operation.
Workaround: Use the following workaround to address this issue.
To address CR 12- 1UVNZ65
1 Within the Siebel application, navigate to the Sales Order screen.
2 Click the List link and navigate to the Sales Order Details screen.
3 Drill down on the Order # and navigate to the Line Items view.
4 Within the Line Items list applet, select Reprice All from the menu.
CR 12-1UK1DKW
Description: The Cancel Error Mode system preference default value should be '3'.
To address CR 12- 1UK1DKW
1 Within the Siebel application, navigate to Administration - Application > System Preferences.
186
2 Within the System Preference Name field, query for Cancel Error Mode and set the value of the
System Preference field to 3.
CR 12-1T03IG9
Description: When the due date of a root product in a Customizable Product is nullified, order
validation does not occur.
To address CR 12- 1T03I G9
1 Within the Siebel application, navigate to Site Map > Administration - Data Validation.
2 Click the Ruleset hyperlink, and query for SWI Order Validation Rule Set in the Ruleset applet.
3 Click Revise to revise the ruleset.
4 Click the SWI Order Validation Rule Set hyperlink, and query for SWI Validate Due Date in the
Rules applet.
5 Modify the rules property as follows:
Apply To: All Records
6 Activate the ruleset.
Unpacking the AIA251.zip File
1 Navigate to the Siebel Tools installation directory <Tools Install Directory>\REPPATCH.
2 Unzip the AIA251.zip file.
<Tools Install Directory>\REPPATCH\AIA251
The AIA251 folder that you create will contain the following subfolders and files:
\ACR474.zip. This file contains the repository changes.
\ACR474_SEED. This file contains the seed data changes.
\ACR474_Workaround. This file contains the Release Notes and workaround information.
\8113_Addendum.
3 Unzip the ACR474.zip file.
<Tools Install Directory>\REPPATCH\AIA251\ACR474
The ACR474 folder that you create will contain the following subfolders:
\DMGSchemaChanges
\EIM
\HTML
\LMU
\SeedData
\SIFFiles
\WebTemplates
\WFs
Use the following procedure to apply the schema changes to the server database.
NOTE: The following instructions refer to the folders specified in Step 2 in the previous task.
As part of the AIA 2.5 release, schema changes have been done on the database.
The following two procedures describe how to import the ACR463_Tables.sif and
ACR463_EIMTables.sif files into the repository.
The ACR463_Tables.sif file has all the changes for the following changes to existing tables:
S_ALERT_CUT
S_ADDR_PER
S_ADDR_PER_UCMX
S_ASSET
S_BULK_REQ
S_CONTACT
S_CON_ADDR
S_INV_PROF
S_INVOICE_ADJ
S_ORDER
S_ORDER_ITEM
S_ORG_EXT
S_PROD_INT
S_QUOTE_ITEM
S_SRV_ORD_FAIL
S_SRV_REQ
S_SPL_RATE_ITEM
S_SPL_RATE_LST
188
To import the ACR463_ Tables.sif file into the repository
1 Lock the following projects before import:
CUT Newtable
Table Asset
Table BulkRequest
Table Invoice
Table Order
Table Organization
Table Product
Table Quote
Table CIF
Table Person
To create this table on the physical database
The tables have to be in the repository before creating this on the physical database. Use Siebel
tools and query for the list of tables that were imported into the repository. Use the "Apply/DDL"
button to apply the changes to the physical database, and provide the correct database user
(table owner name, password, and ODBC data source).
The ACR463_EIMTables.sif file has all the changes for the following:
Changes to existing tables:
EIM_ASSET
EIM_ASSET1
EIM_ALERT_CUT
EIM_INVOICE
EIM_ORDER
EIM_ORDER1
EIM_ORDER_ITEM1
EIM_PROD_INT1
EIM_QUOTE
EIM_QUOTE_IT1
To import the ACR463_ EI MTables.sif file into the repository
EIM Asset
EIM Common SIA
EIM Invoice
EIM Order
EIM Product
EIM Quote
EIM BulkRequest
EIM CIF
EIM FleetManagement
EIM Organization
EIM Person
EIM Service Request
Applying ACR 474 Schema Changes
REPPATCH\AIA251\ACR474\DMGSchemaChanges\ACR474_Tables.sif has all the changes for the
following:
S_ASSET
S_CONTACT
S_CONTACT_BU
S_DOC_QUOTE
S_OPTY
S_OPTY_BU
S_ORDER
S_ORDER_ITEM
S_ORDER_ITEM_OM
S_ORDER_STOP
S_ORDPART_MVMT
S_ORG_BU
190
S_ORG_EXT
S_ORG_GROUP
S_PRI_LST
S_PRI_LST_ITEM
S_PROD_INT
S_PROD_INT_BU
S_QUOTE_ITEM
S_REVN
S_UCM_ADDR_PER
S_UCM_ASSET
S_UCM_CONTACT
S_UCM_ORGGRP
S_UCM_ORG_EXT
S_UCM_PRIVACY
New Tables:
S_INTG_DEL_TXN
S_ORG_GRP_UCMX
S_PRD_USRDEFATR
To import the ACR_ 474_ Tables.sif file into the repository
Table Asset
Table CIF
Table FieldService
Table Forecast
Table Household
Table NetworkOrderManagement
Table OnPremise-OnDemand
Table Opty
Table Order
Table Organization
Table Person
Table PriceList
Table Product
Table Quote
The tables have to be in the repository before creating this on the physical database. Use Siebel
tools and query for the list of tables that were imported into the repository. Use the "Apply/DDL"
button to apply the changes to the physical database.
Applying EIM Changes
As part of the ACR474 release, EIM changes have been done on the database. The
REPPATCH\ AI A251\ ACR474\ DMGSchemaChanges\ ACR474_EI MTabl es. si f file contains all the changes
for the following existing tables:
EIM_ACCOUNT
EIM_ACCOUNT1
EIM_ASSET1
EIM_CONTACT
EIM_CONTACT2
EIM_GROUP
EIM_GROUP_DTL
EIM_OPTY
EIM_OPTY_DTL
EIM_ORDER1
EIM_ORDER_FM
EIM_ORDER_ITEM
EIM_ORDER_ITEM1
EIM_ORD_ITEM2
EIM_ORG_BU
EIM_ORG_INT
EIM_PART_MVMT
EIM_PRI_LST
EIM_PROD_INT
EIM_PROD_INT1
192
EIM_PROD_INT_BU
EIM_QUOTE1
EIM_QUOTE_IT2
EIM_REVN
EIM_UCM_ADRPER
EIM_UCM_ASSET
EIM_UCM_CON
EIM_UCM_ORG
EIM_UCM_ORGGRP
EIM_UCM_PRIVCY
To import the ACR_ 474_ EI MTables.sif file into the repository
EIM Asset
EIM CIF
EIM Common SIA
EIM FieldService
EIM FleetManagement
EIM Forecast
EIM Household
EIM Opty
EIM Order
EIM Organization
EIM Person
EIM PriceList
EIM Product
EIM Quote
2 Use Siebel Tools Import from Archive function to read this file and create the tables in the
The tables have to be in the repository before creating this on the physical database. Use Siebel tools
and query for the list of tables that were imported into the repository. Use the "Apply/DDL" button
to apply the changes to the physical database.
Importing Seed Data for ACR 463
NOTE: As stated earlier, ACR 463 provided the AIA COM 2.4 release.
1 Create an ODBC entry for the database where you plan to import the seed data.
database.
REPPATCH\AIA251\ACR474\SeedData\ACR463_SEED.
4 Seed data import includes mono-language seed-data import and language seed-data import. Use
Step a or Step b or both steps depending upon the language that you are installing.
a Use the following command to import mono-language seed data:
<ToolsInstall Directory>\bin\dataimp /u sadmin /p sadmin /f
<ToolsInstallDirectory>\REPPATCH\AIA251\ACR474\SeedData\ACR463_SEED\Seed_aiacom
24.dat /l <ToolsInstallDirectory>\temp\dataimp_seed.log /c <ODBC Source Name> /d
<Table Owner> /q -1 /w n /e y /t n /x R /n 100 /h log
Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that
the import completed successfully.
b Use the following command to import the language seed data:
<Tools Install Directory>\bin\dataimp /u sadmin /p sadmin /f
<ToolsInstallDirectory>\REPPATCH\AIA251\ACR474\SeedData\ACR463_SEED\seed_locale_
<language>.dat /l <ToolsInstallDirectory>\temp\dataimp_seed.log /c <ODBC Source
Name> /d <Table Owner> /q -1 /w n /e y /t n /x R /n 100 /h log
<Tools Install Directory> - Replace with your Siebel Tools install directory.
<ODBC Source Name> - Replace with the ODBC name created in Step 1.
c Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the
a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC) >
System DSN tab, and click Add.
194
b Select the Siebel Oracle90 driver (from Datadirect Technologies).
e For Oracle, enter the TNS service name that you created to connect Siebel Tools to the database.
f Test your connection and click OK when tested successfully
REPPATCH\ACR474.
Directory>\REPATCH\AIA251\ACR474_SEED\ACR474_8113FP_Seed.dat /l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools Install
Directory>>\REPATCH\AIA251\ACR474_SEED\<Database Platform>\
ACR474_8113FP_Seed.inp /q -1 /w y /e n /t n /x R /n 100 /h log
<Database Platform> - Replace with the database platform (ORACLE, DB2UDB or MSSQL)
Depending upon the language that you are installing, complete either Step 6or Step 7.
6 For ENU (English Language) customers:
a Run the following command after importing the ACR474_Seed.dat file.
Directory>\REPATCH\AIA251\ACR474_SEED\ACR474_8113FP_Seed_Locale_ENU.dat /l
<Tools Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table
Owner> /i <Tools Install Directory>\REPATCH\AIA251\ACR474_SEED \<Database
Platform>\ACR474_8113FP_Seed_Locale_ENU.inp /q -1 /w y /e n /t n /x R /n 100 /h log
7 For customers using languages other than ENU:
a Run the following commands after importing the ACR474_Seed.dat file for importing the locale
specific seed_locale_XXX.dat, where XXX is the language code.
Directory>\REPATCH\AIA251\ACR474_SEED\seed_locale_XXX.dat /l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q -1 /w n
/e y /t n /x R /n 100 /h log
c Run the following commands after importing seed_locale_XXX.dat file for importing the locale
specific AIA251_seed_locale_XXX.dat, where XXX is the language code.
Directory>\REPATCH\AIA251\ACR474_SEED\AIA251_seed_locale_XXX.dat /l <Tools Install
/e y /t n /x R /n 100 /h log
d Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
Updating ACR 474 EIM Files
As part of the ACR474 release, the EIM files - ei m45. sql and ei m_expor t _l ookup_bu_name. sql have
been changed. The REPPATCH\ AI A251\ ACR474\ EI M\ ei m45. sql and
REPPATCH\ AI A251\ f ACR474\ EI M\ ei m_expor t _l ookup_bu_name. sql have all the changes required.
You must merge these files with the existing files in the Siebel Server directory:
ei m45. sql : <I nst al l at i on Locat i on>\ SERVER\ si ebsr vr \ SQLTEMPL
ei m_expor t _l ookup_bu_name. sql : <I nst al l at i on Locat i on>\ SERVER\ si ebsr vr \ ADMI N
196
that the SymStrPrefix entry has been set to SBL_.
[Siebel]
..
SymStrPrefix parameter needs to be X_ for Siebel customers.
SymStrPrefix = SBL_
..
NOTE: After changing the tools.cfg file, make sure to log out of Siebel Tools and log in again to
apply the changes.
2 In Siebel Tools, lock all of the following projects:
ABO Bulk Request
ATP
Account
Account (SSE)
Assignment (SSE)
Asset Management
Bitmap
Cfg RTC
CMU Billing BC
CMU Billing Product
CMU Billing UI
CMU Billing Integration
COM Workflows
CUT Admin - External Data
CUT Billing
CUT Credit Alert
CUT Profile
CUT Newtable
CUT Siebel Communications
CUT Trouble Ticket
Contact
Contact (SSE)
Comm Manager
Communication
Division
Dock
Dock KDI
Docklog
Dockses
Eligibility Compatibility
EIM Asset
EIM CIF
EIM Household
EIM Organization
EIM Person
EIM Common SIA
EIM Invoice
EIM Order
EIM Product
EIM Quote
EIM BulkRequest
EIM Organization
EIM Service Request
Employee
FS Agreement
Fleet Management
ISS Authoring Admin
ISS Class Admin
ISS Context
ISS Order Management
ISS Product Admin
ISS Promotion Admin
ISS VOD Import Export
198
ISS VOD Loader
LS DB Action
MACD Performance
Order Entry
Opportunity Management
Oppty
Oppty (SSE)
PMP
Prepaid Service 8.1
Price List
Product
Product (SSE)
Product Integration
Quote (UI)
Quote
Row Set Transformation Toolkit
Service
Siebel High Tech
Srvagree
Srvagree (SSV)
Symbolic Strings
Template (Order)
Table Asset
Table BulkRequest
Table Invoice
Table Order
Table Organization
Table Product
Table Promotions
Table Quote
Table CIF
Table Person
Table FieldService
Table Forecast
Table Household
Table Opty
Table PriceList
Table OnPremise-OnDemand
UMSUI
VEAI CUT Billing Integration
VERT CUT Address
VERT CUT Common
VERT CUT Screens
Workflow Policy
eService Billing
eAuto Product
NOTE: If you have implemented ACR 471, you must merge repository and workflow changes to
make sure that ACR 471 and ACR 474 are compatible:
Business Service - ISS Promotion Management Service.sif
Workflow - ISS Promotion Upgrade Process.xml
3 Import the rest of the SIF files from the SIFFiles folder into Siebel Tools:
a Place the BatchImportAcr474.bat file in <Tools Install Directory>/bin, edit the file to replace
REPPATCH\ACR474 with REPPATCH\AIA251\ACR474, save the file, and then execute it.
For further information on batch import, see the topic, Importing Objects from an Archive File
Using the Command-Line Interface in Using Siebel Tools on the Siebel Bookshelf library.
200
b Check the logs in <Tools Install Directory>/importLogsAcr474 directory.
c If you have not locked the required projects, you might receive a warning error message. Create
the projects and lock them the projects are not available by default.
d The Fleet Management and Table OnPremise-OnDemand projects are not available by default.
You must create them before you execute the BatchImportAcr474.bat file.
NOTE: The following steps apply only to customers who are installing languages other than ENU.
4 (Optional) If you are installing languages other than ENU:
a Navigate to Select > Tools > Utilities > Locale Management to import LMU files for the specific
language from the LMU folder into Siebel Tools.
c Target Language = <Specific Language>
d Click the Import tab and then Browse to locate the LMU file you want to import and click Import.
6 Within Siebel Tools, navigate to Menu > View > Options > Scripting tab, and specify the following
path for the Browser script compilation folder.
\ \ <Ser ver I P addr ess>\ <SWE ser ver I nst al l ed Locat i on>\ eappweb\ PUBLI C\ enu
7 Compile all of the projects using the Compile Projects > All Locked Projects option and save the
SRF file to the <Si ebel Ser ver I nst al l f ol der >\ obj ect s\ ENU\ si ebel _si a. sr f folder on the
installed Siebel server.
8 Copy the Web Template file CZConf i gur at or . swt and CZVi ew. swt from the WebTemplate folder
into Siebel Server <Siebel Server Install folder >\WEBTEMPL.
9 Copy the CZRet ur n. ht ml file from the HTML folder into the SWE Server <SWE Server Install
folder >\eappweb\PUBLIC\enu.
10 From the EIM folder, copy the files with extension "ifb" in Siebel Server <Siebel Server Install
folder >\ADMIN.
NOTE: All of the existing workflows should be imported. In other words, the modified workflows
should be imported into the corresponding projects. Note the following dependencies before you
begin importing the files:
Import the "SWIOrderUpsert_O2C" workflow first and then import the "SWIOrderUpsert"
workflow.
Import the "SWISendOrder" workflow first and then import the "Submit Order ASI" workflow.
Import the "SWISendQuote" workflow first and then import the "Submit Quote ASI"
workflow.
Import the "Oracle Configurator Load" workflow first and then import the "SWI Configurator
Load" workflow.
Import the "SWIOrderUpsertSubProcess" workflow first and then import "SWIOrderUpsert"
workflow
202
Import the "SWISetTBOEndDate" workflow first and then import the "Dynamic Pricing
Procedure" workflow.
*SIS OM Disconnect Asset Sub-process SIS OM Base Architecture
*SIS OM Move Process SIS OM Base Architecture
ABO Bulk Request -Validate Process ABO Bulk Request
ABO Bulk Request - Clear Exception Process Workflow ABO Bulk Request
ABO Bulk Request - Parallel Sub Process Workflow ABO Bulk Request
ABO Bulk Request - Prepare Action Set Sub-Process Workflow ABO Bulk Request
ABO Bulk Request - Submit Process Workflow ABO Bulk Request
ABO Bulk Request Add Item Customize Process ABO Bulk Request
Account - New Order COM Workflows
Basic Pricing Procedure Cfg RTC
CMU Credit Alert Status Sync Web Service Integration
CMU SIA Submit Adjustment Request to External CMU Billing Integration
CMUBalanceDetailsEventAdjustmentWF CMU Billing Integration
CMUEventDetailsAdjustmentWF CMU Billing Integration
CMUInvoiceAdjustmentWF CMU Billing Integration
CMUItemChargeAdjustmentWF CMU Billing Integration
CMUUnbilledEventAdjustmentWF Web Service Integration
CMUUnbilledNonCurrencyEventAdjustmentWF Web Service Integration
CZ PSP Interface Web Service Integration
CZ Return Web Service Integration
Dynamic Pricing Procedure Row Set Transformation Toolkit
ISS Promotion Disconnect Process ISS Promotion Workflow
ISS Promotion Upgrade Process ISS Promotion Workflow
Oracle Configurator Load Web Service Integration
Oracle Verify Complex Product All (Order) Web Service Integration
Oracle Verify Complex Product All (Quote) Web Service Integration
Pricing Procedure - Calculate Net Price Row Set Transformation Toolkit
SIA External Integration Process Prepaid Service 8.1
SIS OM Add Service Charge Order Sub-Process SIS OM Base Architecture
SIS OM Add Service Charge Quote Sub-Process SIS OM Base Architecture
SIS OM Add Service Charge Sub-Process SIS OM Base Architecture
SIS OM Disconnect Products & Services Process SIS OM Base Architecture
SIS OM Edit Complex Asset Workflow SIS OM Base Architecture
SIS OM Edit Delta Quote Line Item SIS OM Base Architecture
SIS OM Edit Service Order Line Item SIS OM Base Architecture
SIS OM Modify Products & Services Process SIS OM Base Architecture
SIS OM Order Line Item Update Main SIS OM Base Architecture
SIS OM Submit Order Process SIS OM Base Architecture
SIS OM Suspend / Resume Asset Sub-Process SIS OM Base Architecture
SIS OM Suspend / Resume Products & Services Process SIS OM Base Architecture
SISOMBillingSubmitOrderWebService CMU Billing Integration
Submit Order ASI COM Workflows
Submit Quote ASI COM Workflows
SWI Account Update Workflow Web Service Integration
SWI Address Update Workflow Web Service Integration
SWI Asset Status Update CMU Billing Integration
SWI Billing Profile Update Workflow Web Service Integration
SWI Cancel Sales Order Line Item Web Service Integration
SWI Cancel Sales Order_O2C Web Service Integration
SWI Configurator Load Web Service Integration
SWI Contact Update Workflow Web Service Integration
SWI External Account Integration Process Web Service Integration
SWI External Account Request Sync Process Web Service Integration
SWI External Contact Integration Process Web Service Integration
SWI External Contact Req Integration Process Web Service Integration
SWI External Contact Request Sync Process Web Service Integration
SWI External Customer Req Integration Process Web Service Integration
SWI External Product Sync Workflow Web Service Integration
SWI Initial Load Non CP Order Release Web Service Integration
SWI Parent Order Web Service Integration
SWI Special Rating - Synchronize Process Web Service Integration
SWI TSQ Order Web Service Integration
204
NOTE: The asterisks denote workflows that were not modified for ACR 474.
b Right-click on the right side pane called Workflow Processes and import the .xml file into Siebel
Tools from the Workflows folder. Refer to the list of workflows in the table above to know which
project these workflows need to be imported into.
NOTE: The following step is required if you have installed AIA 2.5 IPS 1 or higher.
13 Revise the following workflows, change the Process Property UTCCanonical default value from
N to Y. Publish, and then activate.
CMU Credit Alert Status Sync
CMU SIA Submit Adjustment Request to External
SISOMBillingSubmitOrderWebService
SWI Account Update Workflow
SWI Billing Profile Update Workflow
SWIAdjustmentStatusUpdate Web Service Integration
SWICancel Sales Order Web Service Integration
SWICopyOrder Web Service Integration
SWIOrderUpsert Web Service Integration
SWIOrderUpsert_O2C Web Service Integration
SWIOrderUpsertSubProcess Web Service Integration
SWIQuoteUpsert Web Service Integration
SWIReviseOrderValidation Web Service Integration
SWISendATPCheck Web Service Integration
SWISendATPCheckLine Web Service Integration
SWISendCalculateShippingCharge Web Service Integration
SWISendCreditCheck Web Service Integration
SWISendOrder Web Service Integration
SWISendPaymentAuthorization Web Service Integration
SWISendQuote Web Service Integration
SWISetTBOEndDate CMU Billing Integration
SWIValidateDependentOrders Web Service Integration
Verify Header (Order) COM Workflows
Verify Item (Order) COM Workflows
SWI Contact Update Workflow
SWI Address Update Workflow
SWI Cancel Sales Order_O2C
SWI External Account Request Sync Process
SWI External Contact Request Sync Process
SWI Special Rating - Synchronize Process
SWIAdjustmentStatusUpdate
SWIOrderUpsert
SWIOrderUpsert_O2C
SWIOrderUpsertSubProcess
SWIQuoteUpsert
SWISendATPCheck
SWISendATPCheckLine
SWISendCalculateShippingCharge
SWISendCreditCheck
SWISendOrder
SWISendPaymentAuthorization
SWISendQuote
Check the status of the Workflow process. If it is In-Progress, then make it complete by deploying
the Workflow process.
For Siebel applications version 8.0 and above, the button to mark the workflow status complete
is Publish/Activate. To view this button, navigate to View menu > Tool Bar > WF/Task Editor.
NOTE: If any of the workflows fail to import, manually activate them within the application.
a Repeat Step b and Step c of Siebel Tools Changes for ACR 474 on page 196 for of all the
workflows in the folder.
b Log in to the Siebel application as an administrator.
c Navigate to the Site Map, and click Administration - Business Process.
d Navigate to Workflow Deployment > Repository Workflow Process.
e Query for the workflow processes and activate them.
NOTE: It is recommended that you reload the runtime events after activating the workflows.
f Navigate to Administration - Runtime Events > Events screen, select all records and then select
Reload Runtime Events from the drop-down menu.
206
14 Import the rest of the SIF files from the SIFFiles folder AIA251\ACR474_Workaround into Siebel
Tools using the Import from Archive function.
If you have not locked the required projects, you may receive a warning error message.
Make sure to choose the Merge Option in Siebel Tools Import Wizard.
15 Import the following SIF files:
.\AIA251\ACR474_Workaround\Applet\Order Entry - Line Item List Applet (Sales).sif
.\AIA251\ACR474_Workaround\Bitmap Category\Order Status.sif
.\AIA251\ACR474_Workaround\Business Component\Order Entry - Line Items.sif
.\AIA251\ACR474_Workaround\Business Service\SIS OM PMT Service.sif
.\AIA251\ACR474_Workaround\Icon Map\Graphical indicator - Order Status.sif
.\AIA251\ACR474_Workaround\Integration Object\ISS Order.sif
16 Compile all of the objects listed above using the Compile Selected Object option and save the
SRF file to the <Siebel Server Install folder>\objects\ENU\siebel_sia.srf folder on the installed
Siebel server.
17 Import and activate the workflows listed in the following table from
\AIA251\ACR474_Workaround\WFs into Siebel Tools:

a Within Siebel Tools > Object Explorer, select Workflow Process.
b Right-click on the right side pane Workflow Processes and import the .xml file into Siebel Tools
from the WFs folder. Refer to the list of workflows in the preceding table to know which project
these workflows need to be imported into.
c Activate the workflows by clicking on Deploy+ Activate button to activate the workflows.
18 Import the rest of the SIF files from the SIFFiles folder AIA251\8113_Addendum\ into Siebel
Tools using the Siebel Tools > Import from Archive function.
.\ AIA251\8113_Addendum\Business Component\SWI Internal Product VOD.sif
.\AIA251\8113_Addendum\Business Component\SWI Match Account VBC.sif
.\ AIA251\8113_Addendum\Business Component\SWI Match Contact VBC.sif
Process Name
New/
Modified Project
Pricing Procedure - Calculate Net Price Toolkit Modified Row Set Transformation
SIS OM Edit Service Order Line Item Modified SIS OM Base Architecture
.\ AIA251\8113_Addendum\Business Component\UMF Passive Message Virtual BusComp.sif
.\AIA251\8113_Addendum\Business Service \MatchAccountSiebelReqABCSImplService.sif
.\AIA251\8113_Addendum\Business Service \MatchContactSiebelReqABCSImplService.sif
.\AIA251\8113_Addendum\DMGSchemaChanges\S_PRO_CFG_ITEM.sif
.\AIA251\8113_Addendum\Integration Object\SWIOrderIO.sif
19 Compile all of the preceding objects using the Compile Selected Object option and save the SRF
file to the <Siebel Server Install folder>\objects\ENU\siebel_sia.srf folder on the installed Siebel
server.
20 If the Table Promotions project is not already locked, lock it.
21 Within Siebel Tools, query for the S_PRO_CFG_ITEM table.
22 Click the Apply/DDL button to apply the changes to the physical database.
23 Import the workflows listed in the following table into Siebel Tools and then activate the
workflows.
a Within Siebel Tools > Object Explorer, select Workflow Process.
Tools from the Workflows folder. Refer to the list of workflows in the preceding table to know
which project these workflows need to be imported into.
c Click the Deploy+ Activate button to activate the workflows.
Applying Incremental Fixes for AIA 11.1
1 Unzip the AIA11.1.zip file to create the following directory structure: <Tools Install
Directory>\REPPATCH\AIA11.1
The AIA11.1 folder will contain the following subfolders:
\DMGSchemaChanges
\SIFFiles
\WFs
\Xml
Process Name New/Modified Project
SWI External Account Integration Process Modified Web Service Integration
SWI External Contact Integration Process Modified Web Service Integration
SWI External Contact Req Integration Process Modified Web Service Integration
SWI External Customer Req Integration Process Modified Web Service Integration
208
2 Import the SIF files from DMGSchemaChanges using the Merge option within Siebel Tools Import
Wizard.
3 Within Siebel Tools, query for the tables S_INVC_ADJ_ITEM or S_INVOICE_ADJ tables, and click
Apply/DLL to apply the changes to the physical database.
4 Import the SIF files from SIFFiles using the Merge option in Siebel Tools Import Wizard.
5 Compile all of the preceding objects using the Compile Selected Object option and save the SRF
file to the <Siebel Server Install folder>\objects\ENU\siebel_sia.srf folder on the installed Siebel
server.
6 Import the workflows listed in the following table into Siebel Tools and then activate them:
7 Within Siebel Tools > Object Explorer, select Workflow Process.
8 Right-click on the right-side pane (Workflow Processes) and import the .xml file into Siebel Tools
from the Workflows folder.
NOTE: Refer to the list of workflows in the preceding table to know which project these workflows
need to be imported into.
9 Click Deploy+ Activate button to activate the workflows.
10 Repeat Step 8 and Step 9 for of all the workflows in the folder.
11 Launch the Siebel communications application, and navigate to Site Map > Administration-
Integration > Data Map Editor.
ABO Bulk Request - Prepare
Action Set Sub-Process
Workflow
Modified ABO Bulk Request
ABO Bulk Request - Submit
Process Workflow
CMUBalanceDetailsEventAdjust
mentWF
Modified CMU Billing Integration
CMUInvoiceAdjustmentWF Modified CMU Billing Integration
CMUItemChargeAdjustmentWF Modified CMU Billing Integration
SIS OM Apply Completed
Service Order Line Item to
Service Profile
Modified SIS OM Base Architecture
SISOMBillingSubmitOrderWeb
Service
Modified CMU Billing Integration
SWI Configurator Load Modified Web Service Integration
SWICancel Sales Order Modified Web Service Integration
SWIOrderUpsert Modified Web Service Integration
12 Import the "SWI_Asset_Integration.XML" file from <Tools folder>\REPPATCH\AIA11.1\Xml.
13 In the Integration Object Map applet, query for SWI Asset Integration.
14 In the Integration Component Map applet, query for Line_Item_to_Line_Item.
15 In the Integration Field Map applet, click New and add a new record with the following values:
16 Query for the Status field and change the source expression as follows:
17 Modify the run time events for promotions:
a Navigate to the Administration - Runtime Events screen.
b Click the Action Sets view.
Three applets appear.
c In the first applet, Action Sets, search for the 'Cache Refresh BC - ISS Promotion Pricing
Components List Applet' Action Set.
d For this Action Set, in the bottom form applet, there is a control with the 'Business Service
Context' label. For this control, the previous value was only "ISS Promotion Pricing Components",
"ISS Promotion Pricing Rules Summary". Another new entry was added to this and now the value
for this control is "ISS Promotion Pricing Components", "ISS Promotion Pricing Rules Summary",
"Promotion Config Item".
Note that there should be a space after the comma.
[This step needs to be performed only if it is required.]
18 Release the variable maps:
a Navigate to Site Map > Admin - Order Management > Variable Maps, and query for the following:
Default Pricing Variable Map - Row Set - Basic
b Release a new version of each of the above objects and then bounce the server.
19 Release the signal:
Source Expression Target Field Name
insert operation
IIF([Status] IS NULL, LookupValue
("IMPL_PHASE", "Active"),[Status])
Status
210
a Navigate to Site Map > Admin - Order Management > Signal and query for the ReviseCopyOrder
signal.
b Release a new version of the above object and then bounce the server.
20 Enable component groups for order creation:
NOTE: Bounce the server after enabling the compgrp and synchronizing it.
a Navigate to Administration - Server Configuration > Enterprises > Component Groups and query
for each of the following Component Groups and, if Enable State = Disabled, click <Enable>:
HTIM
EAI
*Note through Srvrmgr Command Prompt - Enable compgrp <Alias>
b After enabling the necessary components, navigate to Administration - Server Configuration >
Enterprises > Synchronize. Select all the records and then click Synchronize.
21 Activate workflows.
a Navigate to Site Map > Administration Business Process > Workflow Deployment > Active
Workflow Processes and in the second applet, complete one of the following tasks:
Query for SIS*,Pri*,PSP*,ISS*,Elig*,eSales*.
Product Promotions, Configurator, C/OM UI processes, CUT eSales (only for SIA, not for
SEA), and Product Recommendation, and delete the groups manually after deactivating
the processes. To deactivate these groups, select them all and then select Deactivate
Process. You can check the Deployment Status as Inactive.
b Delete all the records.
c In the first applet, complete one of the following tasks:
Query for SIS*,Pri*,PSP*,ISS*,Elig*,eSales*.
Product Promotions, Configurator, C/OM UI Processes, CUT eSales (only for SIA, not for
SEA), and Product Recommendations, and then activate all the workflows.
24 Complete the following steps for defining the end point URL for ABS (Outbound Webservices)
a Log into the Siebel application as an administrator and navigate to the Site Map.
b Select Administration - Web Service > Outbound Web Services.
c Query for "*JMS* OR *ABCS* OR *ESB* OR *ConfiguratorUserLangSiebelAdapter* OR
SyncCustomerSiebelEventAggregator" on the Name field of the Web Services applet.
AdjustmentSiebelCommsReqABCS
CalculateShippingChargeSalesOrderSiebelReqABCSImpl
CheckATPSalesOrderSiebelReqABCSImpl
ConfiguratorUserLangSiebelAdapter
CreditCheckSalesOrderSiebelReqABCSImpl
ESB_AccountBalanceSiebelCommsReqABCS_Service
ESB_ConfiguratorCopyConfigEbizAdapter_Service
ESB_InvoiceSiebelCommsReqABCS_Service
ESB_UnbilledUsageSiebelCommsReqABCS_Service
FetchAccountSiebelReqABCSImpl
FetchContactSiebelReqABCSImpl
MatchAccountSiebelReqABCSImpl
MatchContactSiebelReqABCSImpl
PaymentAuthorizationSalesOrderSiebelReqABCSImpl
PaymentSiebelCommsReqABCS
ProcessSalesOrderSiebelCommsJMSProducer
RequestProductStructureSiebelJMSProducer
SyncCustomerSiebelEventAggregator
SyncInstalledProductListSiebelCommsReqABCSImpl
UpdateCreditAlertSiebelCommsReqABCSImpl
d Change the Address field for each outbound Web service to point to http://
<HostName>:<PortNumber> (such as http://ap6039fems.us.oracle.com:7797).
e For Inbound Web Services, navigate to Administration - Web Services > Inbound Web Services,
and make sure that the corresponding Web Services are active. If they are not, change the status
from "Inactive" to "Active" and click the Clear Cache button.
NOTE: Query for these inbound web services --- * ISS *; * Update Order *; * SWI Update *,
SWI*.
212
Setting Up and Configuring Workflow Policies
In order to enable the workflow policies, the following components should be configured and running
on Siebel Server (in addition to the Application Object Manager component).
NOTE: Enabling the EAI and Workflow Component Groups in the Siebel Server will start all the
required components stated above for transaction logging.
To set the Workflow Management component group
Check that the Workflow Management component group is enabled with its components by
navigating to Administration > Server Management > Components, and then querying for
Workflow*.
To generate trigger with parameter Remove = TRUE
1 Navigate to Administration -> Server management -> Jobs) to generate trigger.
2 Create a Job for Component Generate Triggers by clicking New and typing Generate Triggers
under Component/Job.
3 Define the Job Parameters with the following values:
EXEC = TRUE
Privileged User = <Table Owner>
Privileged User Password = <Table Owner>
Remove = TRUE
4 Start the job.
NOTE: If the job parameters do not appear when you query for them, then search for them in the
Advanced or Hidden section.
Configuring Workflow Monitor Agent
1 Navigate to Administration - Server Configuration > Enterprises > Component Definitions, and
query for WorkFlow*.
Component Name Component Alias Component Group
Enterprise Integration Mgr EIM EAI
EAI Object Manager (ENU) EAIObjMgr_enu EAI
Workflow Process Manager WfProcMgr Workflow
Workflow Process Batch Manager WfProcBatchMgr Workflow
Workflow Monitor Agent WorkMon Workflow
Generate Triggers GenTrig Workflow
2 Make a copy of the Workflow Monitor Agent in Administration - Server Configuration ->
Component Definition and change the name to "Workflow Monitor Agent SWI".
3 Change the Alias name to 'WorkMonSWI'.
4 Change the Group Name to "SWI Customer Update Policy Grp" in the component Parameter
applet (down). (Under Component Parameters query for "Group Name" and type the SWI
Customer Update Policy Grp under Value).
5 Change the Action Interval to a value 5.
6 Change the Sleep Time to a value 15.
7 Change the Default Task to 1.
8 Change the status of the new component to "Active" by clicking Activate.
9 Synchronize the components.
Configuring Default Task for Workflow Monitor Agent
The Show Advanced Objects Server Manager parameter controls the display of all the objects that
are marked for the advanced user.
Workflow Monitor Agent has a parameter called 'Default Tasks' that is hidden and should only be
displayed or available to advanced users.
Use the following procedure to reveal the hidden Default Tasks parameter, complete the following
steps.
To reveal the hidden Default Tasks parameter
1 Navigate to Administration - Server Configuration > Servers.
2 In the top Siebel Servers applet, select the server on which you want to modify the parameter,
and under the Component subtab, query for the Server Manager component.
3 Under the Parameters subtab, query for Show Advanced Objects.
4 Change the value to 'True'.
NOTE: You must log out from your current user session and log back into the application in order
for the parameter to take effect.
5 Change the Default Task parameter to 1.
Starting the Tasks for Workflow Monitor Agent for Customer
Synchronization
This section describes the steps to start tasks for the component that is online/enabled.
1 Navigate to Administration - Server Management and select Tasks.
2 Query for the Task "WorkMonSWI" and Start Task.
Alternatively, use Server Manager to start task.
214
3 Start srvrmgr.
srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u <userid> /p
<password>
4 Start task for component WorkMonSWI.
To restart the server
1 Stop the Siebel Server.
2 Rename the existing diccache.dat file in the path <Installed Directory> \ses\siebsrvr\bin.
Generating the Trigger
Make sure that the User SADMIN has the necessary privileges for generating triggers before running
this procedure.
To generate the trigger
1 Navigate to Administration > Server management > Jobs.
2 Create a job for the "Generate Triggers" component by clicking New and typing "Generate
Triggers" under Component/Job.
3 Define the Job Parameters with the following values:
EXEC = TRUE
Privileged User = <Table Owner>
Privileged User Password = <Table Owner>
4 Start the job.
NOTE: If the job parameters information does not appear when you query for it, then search for
it in Advanced or Hidden section.
5 After about five minutes, check for log details for the task for the new workflow monitor
component "Workflow Monitor Agent SWI" by navigating to Administration > Server Management
> Tasks.
6 If errors occur, check whether all configurations have been done properly and then repeat To
restart the server on page 214 and To generate the trigger on page 214.
Enabling Required System Preferences
Use the following procedure to enable required system preferences.
To enable required system preferences
1 Navigate to Administration - Application > System Preferences in the application, query for the
following list of PIPs, and set the value to TRUE:
Enable AIA Comms
Enable AIA MDM
Enable AIA OrderToCash
Enable AIA Testing
CAUTION: Set the system preference to TRUE only for the required PIPs. The AIA Comms PIP
and the AIA OrderToCash PIP cannot coexist.
2 Query for 'Validate Due Date' in the 'System Preference Name' field and set the 'System
Preference Value' to 2. If querying for this preference does not yield any results, create this
value.
3 Query for 'Cancel Error Mode' in the 'System Preference Name' field and set the 'System
Preference Value' to 3 (the default value).
4 Update the AIA Version system preference according to the AIA version that you are using. The
following versions are available:
2.0.1
2.4
2.5
2.5.1
NOTE: If you select any values other than the ones listed above, the application may not function
as expected. Also, you must select 2.5.1 for 11g.
Setting Up the Integration User
This section describes the integration user setup process. We have introduced a new flag to identify
an integration user (needed while integration testing). This user credential needs to be configured
(at AIA side) for the Siebel Inbound Web services call from AIA side to avoid the boomerang effect.
The following procedures describe the process of setting up the integration user:
Steps Expected Result
Login as SADMIN
Navigate to Administration-User ' Employee view The list applet should contain the
integration user flag
Configure a new integration user by setting the
integration user flag to Y for a specific user.
216
Setting Order Priority for AQ
Use the following procedure to set order priority for AQ.
2 Query for Type equals SWI_ORDER_JMS_PRIO_MAPPING.
3 Change the values in the Language-Independent Code column to define the new mapping as per
following table:
Advanced Queue Configuration
NOTE: Advanced queue configuration is only required for the 10g client.
1 Extract oc4j-extended.zip from http://download.oracle.com/otn/java/oc4j/101330/
oc4j_extended_101330.zip to a folder in a machine where the Siebel server is installed, such as
D:\JMS folder.
2 Copy Siebel.jar and SiebelJI_enu to D:\JMS folder, these jar files can be found in <Siebel Server
installation directory>\classes folder
3 Copy jndi.jar file from FMW to D:\JMS\j2ee\home\lib folder.
4 Copy "com/evermind/util/JCAProperties.class" from the oc4j-internal.jar file to the D:\JMS
folder.
5 Create a file with name jndi.properties with following details in the path D:\JMS:
java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory
java.naming.provider.url=opmn:ormi://<IP Address of the FMW server>:<OPMN Port
No>:oc4j_soa
java.naming.security.principal=anonymous
For example:
java.naming.provider.url=opmn:ormi:// 152.68.240.154:6009:oc4j_soa
Make sure that there are no extra spaces in the jndi.properties file.
6 Create a Named Subsystem in the Siebel application through the server management.
Display Value Language-Independent Code
Low 6
Medium 4
High 2
Urgent 0
a Connect to the server manager from the command prompt from the bin directory of the Siebel
installed folder with the following command.
Srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u <userid> /p
<password>
Example: srvrmgr /g sdc78198svqe:4330 /e siebel /s sdc78198svqe /u sadmin /p sadmin
b Run the following command to create the named subsystem and add the jar file into the class
path.
Create named subsystem JAVA for subsystem JVMSubSys with
DLL=C:\Sun\SDK\jdk\jre\bin\server\jvm.dll, CLASSPATH =
D:\JMS;D:\JMS\Siebel.jar;D:\JMS\rdbms\jlib\aqapi.jar;D:\JMS\jdbc\lib\ocrs12.jar;D:\JMS\
jdbc\lib\ojdbc14dms.jar;D:\JMS\jdbc\lib\orai18n.jar;D:\JMS\SiebelJI_enu.jar;D:\JMS\j2ee\
home\lib\adminclient.jar;D:\JMS\j2ee\home\lib\jndi.jar;D:\JMS\j2ee\home\lib\jta.jar;D:\J
MS\j2ee\home\oc4jclient.jar;D:\JMS\j2ee\home\lib\bcel.jar;D:\JMS\j2ee\home\lib\jms.jar
;D:\JMS\j2ee\home\lib\javax77.jar;D:\JMS\lib\dms.jar;D:\JMS\opmn\lib\optic.jar;D:\JMS\
j2ee\home\lib\ejb.jar;., VMOPTIONS= D:\JMS\log\jms.log
For Unix Environment the CLASSPATH should be separated by : (colon) while for windows it
should be ; (semicolon). So, the above command for Unix environment has to be the
following:
DLL= /usr/jdk1.5.0_06/jre/lib/sparc/client/libjvm.so, CLASSPATH = /export/home/qa1/
JMS:/export/home/qa1/JMS/Siebel.jar:/export/home/qa1/JMS/rdbms/jlib/aqapi.jar:/
export/home/qa1/JMS/jdbc/lib/ocrs12.jar:/export/home/qa1/JMS/jdbc/lib/
ojdbc14dms.jar:/export/home/qa1/JMS/jdbc/lib/orai18n.jar:/export/home/qa1/JMS/
SiebelJI_enu.jar:/export/home/qa1/JMS/j2ee/home/lib/adminclient.jar:/export/home/qa1/
JMS/j2ee/home/lib/jndi.jar:/export/home/qa1/JMS/j2ee/home/lib/jta.jar:/export/home/
qa1/JMS/j2ee/home/oc4jclient.jar:/export/home/qa1/JMS/j2ee/home/lib/bcel.jar:/export/
home/qa1/JMS/j2ee/home/lib/jms.jar:/export/home/qa1/JMS/j2ee/home/lib/javax77.jar:/
export/home/qa1/JMS/lib/dms.jar:/export/home/qa1/JMS/opmn/lib/optic.jar:/export/
home/qa1/JMS/j2ee/home/lib/ejb.jar:., VMOPTIONS= /export/home/qa2/JMS/log/jms.log
Make sure that the path is correct for all the files and that the CLASSPATH ends with a . (dot).
Here qa2 should be replaced with the appropriate folder name.
7 Log into the Siebel application and navigate to Site Map > Administration Server Configuration
> Profile Configuration.
a Query for the Profile with Alias Name JAVA in the profile list and make sure the parameters are
correct.
b For the Windows environment, edit the value of VMOPTIONS to -Djms.log=D:\JMS\log\jms.log.
c For the Solaris environment, edit the value of VMOPTIONS to -Xusealtsigs -Xrs -Djms.log=/
export/home/qa2/JMS/log/jms.log.
Make sure that the JMS/log folder exists and has the write permission.
218
NOTE: For more information, see the Siebel Enterprise Application Integration (EAI)
documentation on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/
siebel.html.
Configuring Corresponding Web Services for Advanced Queue (AQ)
The following section contains information about how to configure corresponding Web services for
AQ. For more detailed information about AQ configuration, refer to the topic, Process of Configuring
JMS Messaging Between Siebel Business Applications and Oracle SOA Suite Using Oracle Advanced
Queuing section Transports and Interfaces: Siebel Enterprise Application Integration on the Siebel
Bookshelf.
Use the following procedure to configure corresponding Web services for AQ.
To configure corresponding Web services
1 Navigate to Site Map > Administration - Web Services > Outbound Web Services and query for
SWI*.
2 Change the transport to JMS and address as:
jms://<queue name>@<connection factory>
<queue name> will be in the below format:
java:comp/resource/ <Resource Provider Name as configured >/Queues/<queue name>
<connection factory> will be in the below format:
java:comp/resource/<Resource Provider Name as configured>/QueueConnectionFactories/
QCF
Queues must have been created as part of AIA installation. Please refer the same queue name
here.
3 To locate the Connection Factory Name, log into Application Server control, and navigate to
oc4j_soa ' Administration > Database Persistence.
Here you can find the Resource Provider Name if it is configured.
Example: jms://java:comp/resource/AIA_JMS_RP/Queues/
AIA_SALESORDERJMSQUEUE@java:comp/resource/AIA_JMS_RP/QueueConnectionFactories/
QCF
4 After changing the address, click Clear Cache.
Setting Session Pool Manager
The Session Pool Manager (SPM) is a service in the SOA Web server that manages a pool of Web
server session tokens that are reused among BPEL flows.
If SPM is enabled in AIA, use the following procedure to set Session Pool Manager values.
To set Session Pool Manager values
1 Navigate to <siebel installation folder>/eappweb/bin, and make a backup copy of the eapps.cfg
file.
2 Open eapps.cfg, and search for /eai_enu
3 Add the following parameters:
SessionTimeout = 300
SessionTokenTimeout = 15
SessionTokenMaxAge = 2880
SWSENoSessInPref = TRUE
4 Restart the Siebel Web Server.
Configuring Java Subsystem for Fusion Middleware 11g Integration
In addition to performing the setup tasks for integrating Fusion Middleware in the Siebel installation
guide, perform the following procedure.
NOTE: The paths in this procedure assume you are running the Siebel server on the Windows
operating system. They must be modified if the Siebel server is running on a UNIX operating system.
Use the following procedure to confiugre Java subsystem for Fusion Middleware 11g Integration.
To configure J ava subsystem for Fusion Middleware 11g I ntegration
1 Get the wlfullclient.jar file from the FMW/AIA team. If you cannot get this file, perform the
following steps to create wlfullclient.jar in the FMW server:
a WinScp to the SOA server .
b Change directories to the server/lib directory. (For example, go to WL_HOME/server/lib.)
c Execute the java -jar wljarbuilder.jar command.
The wlfullclient.jar file is created.
2 Remotely log into the Siebel installed server.
3 3. Get the files Siebel.jar and SiebelJI_enu.jar files from the
<siebelinstallation>\ses\siebsrvr\classes folder.
4 Copy the wlfullclient.jar, Siebel.jar and SiebelJI_enu.jar files to the D:\JMS directory. If this
directory does not exist, create it.
220
5 Prepare the jndi.properties file with the following values:
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://<FMW_HOST>:<SOA_PORT>
java.naming.security.principal=<UserName>
java.naming.security.credentials=<Password>
NOTE: If AIA is running on a clustered environment and a proxy host has been set up, then
jndi.properties will have following URL: java.naming.provider.url=http://
<FMW_HOST>:<PROXY_PORT>.
6 Create the JAVA Subsystem using the Siebel Web application:
7 Connect to the server manager from the bin directory of the Siebel installed folder by entering
the following command from the command prompt:
Srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u
<userid> /p <password>
Example: srvrmgr /g sdc78198svqe:4330 /e siebel /s sdc78198svqe /u sadmin /p
sadmin
8 Enter the following command to create the named subsystem:
Create named subsystem JAVA for subsystem JVMSubSys
9 Add the following parameters with the aliases CLASSPATH, DLL and VMOPTIONs:
10 Create the Simulator (with the service name:EAI JMS Transport and Method name: CheckAll).
Name Alias
Data
Type Value Scope Type Description Visibility
JVM
Classpath
CLASSPATH String D:\JMS;D:\JMS\Sie
bel.jar;D:\JMS\Sieb
elJI_enu.jar;D:\JMS
\wlfullclient.jar;.
Subsystem JVM
Configuration
Subsystem
JVM
Classpath
Basic
JVM DLL
Name
DLL String C:\Sun\SDK\jdk\jre
\bin\server\jvm.dll
Name
Subsystem JVM
Configuration
Subsystem
JVM DLL
Name
Basic
JVM
Options
VMOPTION
S
String
-
Djms.log=D:\JMS\lo
g\jms.log
Subsystem JVM
Configuration
Subsystem
JVM Options Basic
11 In the Input Argument Section create Test Case 1 with following values:
Type: PropertySet
Properties :
PropertyName: ConnectionFactory
PropertyValue: jms/TestQueueCF
PropertyName: SendQueue
PropertyValue: jms/TestQueue
12 Click Run to verify the setup in the simulator. It should not display any error messages after the
run.
Required Tasks for the Order to Cash PIP
NOTE: The following tasks are required if you are using the Order to Cash PIP.
Use the following procedure to disable Asset-Based Ordering.
To disable Asset- Based Ordering
1 Log into the Siebel application, and navigate to Site Map > Administration - Server Configuration
> Servers > Parameters.
2 Query for the corresponding object manager for the application (such as htimObjMgr_enu for
application HTIM).
3 Query for the Order Management - Enable Asset Based Ordering parameter in the parameter
list for the component, and set the value to False.
Running EIM Data Migration
This section describes how to run the EIM jobs for implementing the O2C PIP.
Data Migration Sequence
The below entities should be executed in sequence to maintain the data integrity. This includes the
pre-and post EIM activities, which need to be carried out manually.
S.No Main Entities Task Type
1 Organization Manual
2 Inventory Location Manual
4 Products EIM
5 Post EIM Product Release Manual
222
Before you begin the EIM import, note the following:
Make sure that the Siebel Server is running.
Make sure that the Siebel EIM component is online and is running properly. (To check this,
navigate to the Administration - Server Configuration or Administration - Server Management
screens.)
To avoid data loss, do not restart the Siebel Server while the EIM job is running.
After you have completed the data load for one country, make backup copies of the EIM logs, for
status verification. These logs are located in the siebsrvr/logs directory.
Checking EIM Component Availability
Use the following procedure to check EIM component availability.
To check EI M component availability
1 Navigate to the Administration - Server Management screen, then Servers, and then the
Component Groups view. Make sure that the component group Enterprise Application Integration
is active and online.
2 Make sure that the Enterprise Integration Manager component within the Workflow Management
component group is also active and online.
3 Navigate to the Administration - Server Configuration screen, then Enterprise, then Component
Groups, and then the Components Group Assignments view.
4 Make sure that the Enterprise Application Integration Component Group is enabled.
Setting Up Organizations and Inventory Locations
Use the following procedure to set up organizations and inventory locations.
To set up organizations
1 Navigate to the Administration - Group screen, and then the Organizations view.
2 Create the required organizations.
NOTE: Enter information into the Organization Name field but leave the Site field blank.
5 Pricelist EIM
6 Customers EIM
7 Assets EIM
S.No Main Entities Task Type
To set up inventory locations
1 Navigate to the Administration - Data screen, and then the Inventory Locations view.
2 Create inventory locations.
NOTE: Make sure that the inventory location is associated with the correct location.
Executing the EIM Job
Use the following procedure to execute the EIM job.
To execute the EI M j ob
1 Place the respective IFB file on the server machine using the Siebsrvr/Admin file path, as shown
in the following example:
2 Make sure that the SESSION SQL statement of the [UPDATE ACCOUNT NUMBER] section of the
Customer Ifb file is modified in order to reflect the working instance:
UPDATE ORA19111. EI M_ACCOUNT SET OU_NUM = T_ORG_EXT__RI D WHERE
I F_ROW_BATCH_NUM=100
where ORA19111 is the working instance.
Also, the same should be considered for the [UPDATE INTEGRATION ID] section of the Pricelist.ifb
file:
SESSI ON SQL = " UPDATE ORA19111. EI M_PRI _LST SET PL_I NTEGRATI ON_I D = NULL WHERE
PL_I NTEGRATI ON_I D I S NOT NULL"
For Pricelist.ifb, comment the second process using a terminate symbol (so that it becomes
inactive and only the first process is executed), like this:
[ I MPORT ALL PRI CELI STS]
TYPE = SHELL
I NCLUDE = " I MPORT PRI CELI ST"
Component IFB File
Product Product.ifb
Pricelist Pricelist.ifb
Customer Customer.ifb
Asset Asset.ifb
224
; I NCLUDE = " UPDATE I NTEGRATI ON I D"
Once EIM imports all of the pricelist data and the Integration Id is populated, the administrator
needs to run another ODI API to populate the cross-reference database. Then, the administrator
needs to run EIM again to nullify integ_id. The format of the IFB file for the second run will look
like:
[ I MPORT ALL PRI CELI STS]
TYPE = SHELL
; I NCLUDE = " I MPORT PRI CELI ST"
I NCLUDE = " UPDATE I NTEGRATI ON I D"
All the job parameters should remain the same for both of the runs.
3 Log into the application with administrator credentials in order to be able to access the Server
Management screen.
4 Navigate to the Administration - Server Management screen, and then the Jobs view.
5 Click New and select "Enterprise Integration Mgr" in the Component/Job tab.
6 In the "Job Parameters" applet, fill in the following parameters:
Configuration file = .Ifb File name
Error Flags = 1
SQL Trace Flags = 8
Trace Flags = 1
7 After passing parameters, click Submit Job.
8 In the Jobs view, for each job that you have executed, make sure that the Status columndisplays
Success for the jobs that you have executed.
9 Check the status in the EIM table by executing the SQL statements in the following section. In
each case, make sure that the status is IMPORTED.
Products
Product Header:
SELECT COUNT( *) , I F_ROW_STAT FROM EI M_PROD_I NT
WHERE I F_ROW_BATCH_NUM = ' 100'
GROUP BY I F_ROW_STAT
Product Details:
SELECT COUNT( *) , I F_ROW_STAT FROM EI M_PROD_I NT1
Product-Inventory Locations:
SELECT COUNT( *) , I F_ROW_STAT FROM EI M_PRODI NVLOC
Pricelists
In this case since the same set of records are processed twice by the two separate sections of the
IFB file: one meant for importing the Pricelist Records and other meant for updating the Integration
Id to NULL, you will get the DUP_REC_EXISTS status in the EIM tables.
SELECT COUNT( *) , I F_ROW_STAT FROM EI M_PRI _LST
Customers
Address:
SELECT COUNT( *) , I F_ROW_STAT FROM EI M_ADDR_PER
Account:
SELECT COUNT( *) , I F_ROW_STAT FROM EI M_ACCOUNT
Account Details:
SELECT COUNT( *) , I F_ROW_STAT FROM EI M_FN_ACCNT1
Customer:
SELECT COUNT( *) , I F_ROW_STAT FROM EI M_CONTACT
Assets
There are two sections in the IFB file: For Importing Assets and For Updating the Parent Assets.
226
Hence the status will show DUP_REC_EXISTS
SELECT COUNT( *) , I F_ROW_STAT, I F_ROW_BATCH_NUM FROM EI M_ASSET
GROUP BY I F_ROW_STAT, I F_ROW_BATCH_NUM
Use the following procedure to check the EIM log.
To check the EI M log
1 From the Jobs view in the Administration - Server Management screen, navigate to the Tasks
View in the same screen.
2 Get the Task Number from the Task field.
3 Navigate to the Siebsrvr\log directory and query for the locate the log file using the Task #. The
log file contains details about of every level of processing, as well as information about any
errors.
Postinstallation Tasks
You must perform the tasks listed in this section.
NOTE: These postinstallation tasks only apply to the Order to Cash PIP.
To release the products
1 Navigate to the Administration - Business Service screen.
2 In the top applet, create a new record with the following values:
Service Name: ISS Authoring Import Export Service
Method Name: Post_EIM_Upgrade
3 In the bottom applet, create the Input Argument by creating pop up icons on the Property Name
Field, using the following values:
Property Name: ReportOnly
Value: FALSE
Property Name: RootObjectType
Value: ISS_JWS
Property Name: RootObjectName
Value: Staging Mode 1
NOTE: The RootObjectName should be any meaningful name for the Joint Workspace Project.
This will be created automatically after the Business Service is executed from the simulator.
4 Click the Run button in the top applet and wait until the job ends.
To get the j oint workspace Row I D
1 Navigate to the Administration - Product screen, and then the Workspace Projects view.
2 Query for the value provided for the RootObjectName input parameter given while running the
ISS Authoring Import Export Service (as in Step 4 of To release the products on page 226).
3 Go to the Menu option and click the About Record method or use the keyboard shortcut (CTRL +
ALT + K) while on the active record.
4 Make a note of the Row # value displayed in the pop-up applet, as you will need this value to
provide the input argument to the workflow process.
To release the noncustomizable and orderable products
1 Navigate to the Administration - Business Process screen, then Workflow Deployment, and then
the Repository Workflow Processes view.
2 In the "Active Workflow Processes" view, search for the "SWI Initial Load Non CP Order Release"
workflow to make sure that the active version of the workflow is present in the repository.
3 If this record is not present, query for the SWI Initial Load Non CP Order Release workflow in
the Repository Workflow Processes" applet, and click Activate after you locate the record.
4 If the workflow is not present in either of the previous applets, within the Active Workflow
Processes applet, select Menu, select the Import Processes functionality, and choose the SWI
Initial Load Non CP Order Release -WF.xml file from the Browse window.
5 Navigate to the Administration - Server Management screen, and then the Jobs view.
6 Click the New button on the top applet to create a new job, and enter "Workflow Process Batch
Manager" as the value for Component/Job.
7 Navigate to the "Job Parameters" applet and create the following two new values:
Name= Workflow Process Name
Value = SWI Initial Load Non CP Order Release
Name Search Specification
Value = [Par JWS Id] = '6SIA-4HVMH' AND [Orderable Flag] = 'Y' AND [Product Def Type
Code] <> LookupValue ("PROD_TYPE_CD", "Customizable")
NOTE: The Parent Joint Workspace Id value is the same as the one in Step 5 of To get the joint
workspace Row ID on page 227.
8 Click the "Submit" button and wait until the job ends successfully.
Configuring Oracle Configurator
Use the following instructions to apply the run changes for the configuration to the database.
To apply runtime Siebel configuration changes
You must perform the following runtime configuration changes before you launch Oracle configurator.
228
1 Log into the eCommunications/HTIM application from a browser.
2 Navigate to Site Map > Administation Business process > Repository workflow process.
a In the top applet, query for the workflows that you imported previously and activate them.
b In the bottom applet, query for the workflows to make sure that they are in an active state.
3 Navigate to Site Map > Administation Order Management > Signals.
a Query for the Customize signal.
b Lock the signal record and click on Workspace.
c Change the service name to SWI Configurator Load.
d Navigate back to the Signals view and click the Release New Version button to release a new
version of the signal.
e Query for the QuotesAndOrdersValidate signal.
f Lock the signal record and click on Workspace.
g Replace the Siebel Verification with Oracle Batch Validate'. Change all four records with sequence
#2.
Mode = Quote, Instance Type = Line Item - Change Service Name column to "Oracle
Verify Item (Quote)"
Mode = Order, Instance Type = Line Item - Change Service Name column to "Oracle
Verify Item (Order)"
Mode = Quote, Instance Type = Header - Change Service Name column to "Oracle Verify
Header (Quote)"
Mode = Order, Instance Type = Header - Change Service Name column to "Oracle Verify
Header (Quote)"
4 Navigate to Administration Runtime Events > Events and click Menu > Reload Runtime Events.
5 Navigate to Administration - Application > Views.
a Verify the following new views:
CZRuntimeInstanceView (JS)
CZRuntimeInstanceView (JS) - Agreement
CZRuntimeInstanceView (JS) - Order (Sales)
CZRuntimeInstanceView (JS) - Favorites
b For each view, assign the appropriate responsibility so that the user with that responsibility can
navigate to this view.
This is part of seed data. It should be done when exporting the seed data.
6 Navigate to Administration - Integration > WI Symbolic URL List.
a In the top applet, from the drop-down menu (bold highlighted menu), select Host
Administration.
b Add a new host entry with the following values:
Host Name: <Oracle EBIZ host name:port number> for example
qapache.us.oracle.com:3710
Virtual Name: OracleConfigurator
c Select Symbolic URL Administration and add a new record in the top applet.
Name: OracleCfgURL (Note: This symbolic name is very important because the server-
side business component code relies on this name.)
URL: http://OracleConfigurator/OA_HTML/CfgSebl.jsp
Choose the host name (such as qapache.us.oracle.com:3710)
Fixup Name: Default
SSO Disposition: IFRAME
d In the bottom applet, add arguments to the URL by creating a new record with the following
values:
Name: InitMessage
Req Arg: checked
Argument Type: Profile Attribute
Argument Value: CZInitMessage
Append as argument: checked
e Add another new row:
Name: PostRequest
Required Arg: Checked
Argument Type: Command
Argument Value: PostRequest
Append as argument: Not-Checked
f Complete the following two steps to set up the SSO login into Oracle applications:
NOTE: The SSO login is the preferred method for accessing Oracle applications. If you do not
set up the SSO login, the Siebel end user must enter Oracle login credentials at the login
page.
g For the next two arguments enter the values for Argument Value as specified. UserLoginId and
UserLoginPassword are function names used by Siebel SSO. These functions look up the Oracle
login credentials for the Siebel application user. If the user enters other values, they will be
required to log into an Oracle Applications for Configurator session.
h Continue to add arguments to the same URL:
Name: username
Argument Value : UserLoginId
230
Append as argument: Checked
i Add the final argument:
Name: password
Argument Value: UserLoginPassword
Append as argument: Checked
j Select "SSO Systems Admin List" and add a record in the top applet.
System Name: OracleConfigSSO
Symbolic URL Name: OracleCfgURL
Description: Logs in to the Oracle Configurator
k In the bottom applet "SSO System Users" add records for the Siebel users that will be invoking
Oracle Configurator. The Siebel user names will be paired with Oracle login credentials. For
example:
Siebel Login Name: sadmin
Login Name: operations
Password: welcome
7 Navigate to Administration - Server Configuration > Components, select the "eCommunications
Object Manager (ENU)" component, select the "Order Management - Enable Asset Based
Ordering" parameter and set this value to False to call Oracle Configurator instead of calling
Siebel Configurator.
8 Navigate to the "HTIM Object Manager (ENU)" component, select the "Order Management -
Enable Asset Based Ordering" parameter, and set this value to False to call Oracle Configurator
instead of calling Siebel Configurator.
The following workflows need to be activated for Configurator to work. Note that these are not
workflows that were introduced as part of the Oracle Configurator integration; they already
existed.
Account - New Quote
Account - New Order
Goto*
PSP*
Product Compatibility*
Product Eligibility*
Product Reco*
*Pric*
Compatibility Multiple Popup Workflow
Config*
Check*
Adding Siebel Custom Applications to Oracle Applications
Several custom Oracle applications need to be created to allow models to be accessed from the Siebel
application. These custom applications are used during the publication phase of the Oracle
Configurator Model development cycle.
To add Siebel Custom Applications to Oracle Applications
1 Log in to Oracle Applications with system administrator credentials, and navigate to Application
> Register.
2 If the form page does not display, navigate to the form.
3 Create three new entries with four values:
Siebel Quote Integration |SEBLQ | DUMMY_TOP |Provides integration between Siebel Quote
and Oracle Configurator
Siebel Order Entry Integration | SEBLO | DUMMY_TOP | Provides integration between Siebel
Order Entry and Oracle Configurator
Siebel Agreement Integration | SEBLA | DUMMY_TOP | Provides integration between Siebel
Agreement and Oracle Configurator
The new applications now must be added to Oracle Configurator Publication Applicability list.
4 Change the responsibility to Configurator Administrator.
5 Choose Application to Publication Applicability List and add the applications.
This step runs a concurrent program. Once the program runs, these new applications will be
available during model publication.
Refer to Oracle documentation for Configurator for information about how to develop models for
calling applications.
Copy Config Web Service Setup
1 Log in to the eCommunications/HTIM application from a browser.
2 Navigate to Administation Web Services > Outbound Web Services.
3 Click Import to import 'ESB_ConfiguratorCopyConfigEbizAdapter_Service.XML'.
4 Click Import to import 'ConfiguratorUserLangSiebelAdapter.XML'.
NOTE: Step 1 through 4 is part of seed data. It should be done when exporting the seed data.
5 After importing, change the IP Address on the Service Ports (middle applet) for each of the
preceding web services.
232
Copy Config Data Map Setup
1 Log in to eCommunications/HTIM application from a browser and navigate to Administration -
Application > Data Map Administration.
2 For the following data maps, add three columns named 'External Configurator Reference
1','External Configurator Reference 2', and 'External Configurator Reference 3' to both the Source
and the Destination Column in the Data Map Field section for the data map component specified
in the parentheses:
AutoAgreement (Data Map Component:Line Item)
AutoAgreeFromOrder (Data Map Component Name:Line Items)
CopyOrder (Data Map Component Name:Line Item)
CopyQuote (Data Map Component Name:Line Item)
OrderToTemplate (Data Map Component Name:Line Item)
QuoteToSalesOrder (Data Map Component Name:Line Item)
QuoteToServiceOrder (Data Map Component Name:Line Item)
QuoteToTemplate (Data Map Component Name:Line Item)
ReviseAgreement (Data Map Component Name:Line Item)
ReviseOrder (Data Map Component Name:Line Item)
ReviseQuote (Data Map Component Name:Line Item)
TemplateToOrder (Data Map Component Name:Line Item)
TemplateToQuote (Data Map Component Name:Line Item)
DoCompression Parameter Setup
2 Back up the eapps.cfg file, which is located in the eappweb\bin folder within your installation
directory.
3 Edit eapps.cfg using Notepad.
CAUTION: Do not use Wordpad, as this will cause incorrect characters to be added to the file.
4 Reset the DoCompression parameter in the [defaults] section. It should now be
DoCompression=FALSE.
5 Restart the machine.
NOTE: You must restart the machine. Restarting only the Siebel Server will not make your
changes take effect.
Applying Changes for the Signal
1 Navigate to Administration - Order Management > Signal.
2 To change the signal sequence (if required), lock the signal, click the workspace, make the
sequence changes described in the following tables, and click the Release button to release the
signal.
Table 12. CalculateShippingAndTax Signal
Service Name Service Type Sequence Condition Active Mode
SWISendCalculateShippingCha
rge
Workflow 1 SystemPreference("Enable
AIA OrderToCash")="TRUE
Yes Order
ISS Tax Calculation Service Business Service 2 Yes Order
ISS Shipping Calculation
Service
Business Service 3 No Order
ISS Tax Calculation Service Business Service 2 Yes Quote
ISS Shipping Calculation
Service
Business Service 3 Yes Quote
Table 13. CreditCardAuthentication Signal
Service Name
Service
Type Sequence Condition Active Mode
SWISendPaymentAuthorization Workflow 1 SystemPreference("Enable AIA
OrderToCash")="TRUE
Yes Payment
ISS Credit Card Transaction
Service
Business
Service
2 Yes Payment
ISS Credit Card Transaction
Service
Business
Service
2 Yes Quote
Table 14. RunCreditCheck Signal
Service Name
Service
SWISendCreditCheck Workflow 1 SystemPreference("E
nable AIA
OrderToCash")="TRU
E
Yes Payment
ISS Credit Check Service Business
Service
2 Yes
Table 15. ATPInquire Signal
SWISendATPCheckLine Workflow 1 SystemPreference("Enable
Yes Order
ISS ATP Service BusinessService 2 Yes
234
Fixing State Model for Quote Status
Use the following procedure to extend the state model
To make Quote Status work, you can extend the related State Model activation date.
1 Navigate to Administration - Application > State Model and search for "TNT SHM Quote Status".
2 Extend its activation date until 2020 (leave day and month as sysdate).
Table 16. ATPInquireAll Signal
SWISendATPCheck Workflow 1 SystemPreference("E
nable AIA
OrderToCash")="TRU
E
Yes Order
ISS ATP Service Business Service 2 Yes
Table 17. Customize Signal
Service Name
Service
SWI Configurator
Load
Yes
Table 18. QuotesAndOrdersValidate Signal
Service Name
Service
PSP Driver
Workflow Process
Workflow 1 Yes Order
PSP Driver
Workflow Process
Workflow 1 Yes Order
Oracle Verify
Header (Order)
Yes Order
Oracle Verify Item
(Order)
Yes Order
PSP Driver
Workflow Process
Workflow 1 Yes Quote
PSP Driver
Workflow Process
Workflow 1 Yes Quote
Oracle Verify Item
(Quote)
Yes Quote
Oracle Verify
Header (Quote)
Yes Quote
Other Order to Cash Configuration Steps
1 Navigate to Administration - Application > Data Map Administration and query for the
ReviseOrder data map object, the Header data map component, and the Back Office Process
Status data map field.
2 Select the Inactive check box to inactivate the Back Office Process Status data map field.
3 Navigate to Administrator > Data Validation > Rule Sets and query for the following rule sets:
O2C Order Validation
O2C Payment Authorization
O2C Quote Validation
O2C Cancel Order Validation
SWI Revise Order Validation
4 Activate these five rule sets by clicking the Activate button on the top applet.
Rule Name Expression Sequence
Business
Component
Apply
To
Return
Code
Account (SystemPreference("E
nable AIA
OrderToCash")="FALS
E") OR (([Account Id]
IS NOT NULL AND
[Bill To Account Id] IS
NOT NULL AND [Bill To
Address Id] IS NOT
NULL AND [Ship To
Account Id] IS NOT
NULL AND [Ship To
Address Id] IS NOT
NULL))
1 PDS Simplified
Order Entry -
Orders
Current
Record
O2C-Order-
002
Status (SystemPreference("E
nable AIA
OrderToCash")="FALS
E") OR ([Status] =
LookupValue("FS_OR
DER_STATUS","Booke
d"))
2 PDS Simplified
Order Entry -
Orders
Current
Record
O2C-Order-
002
236
Resubmit (SystemPreference("E
nable AIA
OrderToCash")="FALS
E") OR (([Back Office
Process Status] IS
NULL) OR ([Back
Office Process Status]
=
LookupValue("EAI_OR
DER_SYNC_STATUS",
"Error on Creating")))
3 PDS Simplified
Order Entry -
Orders
Current
Record
O2C-Order-
003
Payment ((SystemPreference("
Enable AIA
OrderToCash")="FALS
E") OR ((([Payment
Method]
=LookupValue("PAYM
ENT_METHOD_CODE"
,"Credit Card") OR
[Payment Method] =
LookupValue("PAYME
NT_METHOD_CODE","
Purchase Order"))
AND [Payment Status]
=
LookupValue("FUNDR
Q_STATUS","Approve
d")) OR ([Payment
Method] NOT LIKE
LookupValue("PAYME
NT_METHOD_CODE","
Credit Card") AND
[Payment Method]
NOT LIKE
LookupValue("PAYME
NT_METHOD_CODE","
Purchase Order")) OR
([Payment Method] IS
NULL)))
4 Payments All
Records
O2C-Order-
004
Business
Component
Apply
To
Return
Code
Credit Hold (SystemPreference("E
nable AIA
OrderToCash")="FALS
E") OR ([Hold Flag]
="N" )
5 PDS Simplified
Order Entry -
Orders
Current
Record
O2C-Order-
005
Cancel
Reason not
empty
NOT(SystemPreferenc
e("Enable AIA
OrderToCash")="TRU
E" AND ([Request To
Cancel] = "Y" AND
[Cancel Reason] IS
NULL))
6 PDS Simplified
Order Entry -
Line Items
All
Records
SWI_CANCE
L_ORDER_0
02
Rule
Name Expression Sequence
Business
Component Apply To Return Code
Card
Filled
(SystemPreference(
"Enable AIA
OrderToCash")="FA
LSE") OR
(([Payment Method]
=LookupValue("PAY
MENT_METHOD_CO
DE","Credit Card")
AND [Credit Card
Number - Display]
IS NOT NULL) OR
[Payment Method]
<> "Credit Card")
1 Payments Current
Record
O2C-Order-006
Business
Component
Apply
To
Return
Code
238
Business
Component Apply To
Return
Code
O2C Account (SystemPreferen
ce("Enable AIA
OrderToCash")="
FALSE")OR
([Account Id] IS
NOT NULL )
1 PDS
Simplified
Quote
Current
Record
O2C-Quote-
002
O2C Ship
Address
(SystemPreferen
ce("Enable AIA
OrderToCash")="
FALSE") OR
([Ship To
Address] IS NOT
NULL)
2 PDS
Simplified
Quote
Current
Record
O2C-Quote-
004
O2C Bill
Address
((SystemPrefere
nce("Enable AIA
OrderToCash")="
FALSE") OR ([Bill
To Address] IS
NOT NULL ))
3 PDS
Simplified
Quote
Current
Record
O2C-Quote-
003
O2C Already
Processed
(SystemPreferen
ce("Enable AIA
OrderToCash")="
FALSE") OR ([EAI
Status] IS NULL
OR [EAI Status]
=
LookupValue("EA
I_ORDER_SYNC_
STATUS","Error
on Creating") or
[EAI Status] =
LookupValue("EA
I_ORDER_SYNC_
STATUS","Creati
ng in Back
Office"))
4 PDS
Simplified
Quote
Current
Record
O2C-Quote-
005
O2C Quote
Status
(SystemPreferen
ce("Enable AIA
OrderToCash")="
FALSE") OR
([Status] =
LookupValue("Q
UOTE_STATUS","
Approved"))
5 PDS
Simplified
Quote
Current
Record
O2C-Quote-
001
Business
Component Apply To
Return
Code
SWI Active
Check
(SystemPreferenc
e("Enable AIA
OrderToCash")="F
ALSE")OR
([Account Id] IS
NOT NULL )
1 PDS Simplified
Order Entry -
Orders
Current
Record
SWI Order
Revise 001
SWI Revise
Order
(SystemPreferenc
e("Enable AIA
OrderToCash")="F
ALSE") OR
(([Back Office
Process Status] =
LookupValue("EAI
_ORDER_SYNC_S
TATUS","Created
in Back Office"))
OR (([Status] =
LookupValue("FS_
ORDER_STATUS",
"Booked"))) AND
(([Status] <>
LookupValue("FS_
ORDER_STATUS",
"Shipped")) AND
([Status] <>
LookupValue("FS_
ORDER_STATUS",
"Closed"))))
2 PDS Simplified
Order Entry -
Orders
Current
Record
SWI Order
Revise 002
240
SWI Revise
Order Line
(SystemPreferenc
e("Enable AIA
OrderToCash")="F
ALSE")
OR((([Status] =
LookupValue("FS_
ORDER_STATUS",
"Booked")) OR
([Status] =
LookupValue("FS_
ORDER_STATUS",
"Picked")) OR
([Status] =
LookupValue("FS_
ORDER_STATUS",
"Cancelled")) OR
([Status] =
LookupValue("FS_
ORDER_STATUS",
"Pending")) OR
([Status] =
LookupValue("FS_
ORDER_STATUS",
"Shipped")) OR
([Status] =
LookupValue("FS_
ORDER_STATUS",
"Closed")) OR
([Status] =
LookupValue("FS_
ORDER_STATUS",
"Configured Item
created"))))
3 PDS Simplified
Order Entry -
Orders
All
Records
SWI Order
Revise 003
SWI Back
Office Check
(SystemPreferenc
e("Enable AIA
OrderToCash")="F
ALSE") OR ([Back
Office Process
Status] =
"Created in Back
Office")
4 PDS Simplified
Order Entry -
Orders
Current
Record
SWI Order
Revise 002
Business
Component Apply To
Return
Code
Required Tasks for the COMM PIP
NOTE: If you are implementing the Communications Order to Cash Integration Pack for Siebel CRM,
you must perform the tasks in this topic.
To activate the rule sets for Comms
1 Query for the Order Validation rule set.
Business
Component Apply To Return Code
PONR Not
Reached
NOT(SystemPref
erence("Enable
AIA
OrderToCash")="
TRUE" AND
([Status] =
LookupValue
('FS_ORDER_ST
ATUS',
'Shipped')) or
([Status] =
LookupValue
('FS_ORDER_ST
ATUS', 'Closed'))
or ([Status] =
LookupValue
('FS_ORDER_ST
ATUS',
'Fulfilled')) or
([Status] =
LookupValue
('FS_ORDER_ST
ATUS', 'Supply
Eligible')))
1 PDS Simplified
Order Entry -
Line Items
All Records SWI_CANCEL
_ORDER_001
Cancel
Reason not
empty
NOT(SystemPref
erence("Enable
AIA
OrderToCash")="
TRUE" AND
([Cancel Reason]
IS NULL))
2 PDS Simplified
Order Entry -
Line Items
Current
Record
SWI_CANCEL
_ORDER_002
242
2 If two versions are displayed as active, select the earliest version.
For example, if the active versions are 5 and 6, select version 5.
3 Select Deactivate Rule Set from the submenu.
4 Navigate to Administration - Runtime Events > Events screen, and select Reload Runtime Events
from the drop-down list.
NOTE: If two active versions are displayed for SWI Order Validation Rule Set, use the previous
procedure.
Running EIM Data Migration for Comms
This section defines the detailed steps to run the EIM jobs for Siebel applications as a part of the
Creating and Updating Credit Alerts for Collection Flows functionality in AIA COM 2.5. The ODI
interface will be triggered to transport the required data for creating/updating Credit Alerts from BRM
into the Siebel EIM tables. EIM scripts will be then executed to load the data into the SFA base tables.
Before you begin your import, do the following:
Make sure that the Siebel Server is up and running.
Make sure that the Siebel EIM component is online and running properly. To check this, navigate
to the Administration - Server Configuration and Administration - Server Management screens.
To avoid data loss, do not restart the Siebel server while the EIM job is running.
After you have completed loading data for one country, make a backup copy of the EIM logs for
status verification. (These logs are located under siebsrvr/logs.)
Use the following procedure to execute the EIM job to create and update credit alerts.
To execute the EI M j ob to create and update credit alerts
1 Move the ProcessAlertsAndBillingProf.ifb file from <Tools Installation directory>/REPPATCH/
ACR474/EIM to <Siebel Installation Directory>/ses/siebsrvr/ADMIN.
2 Run the EIM job with the ProcessAlertsAndBillingProf.ifb configuration file.
3 Verify that the EIM job is successful.
NOTE: If the Order to Cash PIP is enabled, the Asset-Based Ordering parameter for the
corresponding object manager for the application must be set to False.
This section describes the integration user setup process. A new flag has been introduced to identify
an integration user (needed while integration testing). This user credential must be configured (on
the AIA side) for the Siebel Inbound Web services call from the AIA side to avoid the boomerang
effect.
Enabling Dynamic Pricing (Customer Order Management)
The pricing module is available in multiple licensing modes.
Dynamic Pricing Mode
This mode provides pricing capabilities such as attribute pricing, promotions, aggregate
discounts, and so on.
It leverages the variable maps that contain the XA child variable maps.
It is available only to users who have the Dynamic Pricer license.
Dynamic Pricing can also be enabled by navigating to Admin - Pricing > Price List, and selecting
Enable Dynamic Pricing from the applet-level menu.
This is a new implementation in Siebel version 8.1.1 applications. After you select Enable
Dynamic Pricing, all the necessary changes will be performed.
Configuring the Email Notification for the Product Class and Attribute
Query Feature
Users to whom emails need to be sent need to be added to the user list.
To add/ change the email addresses for the user list
1 Navigate to Administration - Users > Users.
2 Add user name and user ID.
3 Add the email address in the contact information of the child applet.
4 Navigate to Administration - Group > User Lists and query for the SCE Users user list.
NOTE: If this list does not appear, create it.
5 Add the users created in the user list.
The user list created in the previous procedure is passed in the run time events.
Use the following procedure to add the changed user list.
To change the BO/ BC/ Field name to extract the email addresses
1 Navigate to Administration - Run Time Events > Action Set, and query for the EmailNotify action
set.
244
2 Query for the 'GetEmailAddr' action in the child applet
The following is the business service context syntax-
"Parent BC Record Name";"Field Name in Child BC ";"BO Name ";"Parent BC";"Child BC"
For instance-
"SCE Users";"Email Address";"Account";"Account";"Contact"
or
"SCE Users";"EMail Addr";"User List";"User List";"User"
The following run-time events use the action set described above.
Four communications templates are used to send email messages. The Attribute Defn and Product
Class templates are already configured.
Use the following procedure to configure or edit other templates.
To edit or configure email template text
1 Create a notepad file called "Attribute_Template.txt" and add the following values:
Attribute Name: [Name]
Description: [Description]
Type: [Type]
Object Number: [Object Number]
XRef Class Name: [XRef Class Name]
2 Create a notepad file called "Class_Template.txt" and add the following values:
Class Name: [Name]
Description: [Description]
Type: [Type]
Object Number: [Object Number]
Sequence Object Type Object Name Event Subevent Action Set
Name
1 BusComp Attribute VOD
BusComp
2 BusComp ISS Class VOD
BusComp
3 BusComp ISS Joint
Workspace
BusComp
4 Query for Workspace Attribute Defn Template and click on Template Items View.
5 Attach the "Attribute_Template.txt" file created in Step 1 in the template item.
7 Query for "Workspace Product Class Defn Template" and click on Template Items View.
8 Attach the "Class_Template.txt" file created in Step 2 in the template item.
9 Make sure that "ISS Joint Workspace VOD Pick BucComp" is selected in the iteration child
business component for above two template items.
The communication template names are added in the user properties of the business components
listed in the following table.
The SMTP Server name, From Email Address, and POP server details are added in the a
Communication profile.
Use the following procedure to add the SMTP server name, From Email Address, and POP server
details.
To change the SMTP Server name, From Email Address, and POP server details
1 Navigate to Administration - Communications > Communications Drivers and Profiles.
2 Query for the Internet SMTP/POP3 Server communication driver, and if it does not exist, create
it using the following values:
Name: Internet SMTP/IMAP Server
Channel Type: Email
Channel String: POP3SMTP
Library Name: sscmmail
Outbound: Yes
3 Query for Default SMTP in the child applet, and if it does not exist, create it.
4 Change the SMTP and POP Server details in the grandchild applet, using the following values:
From Address: siebel.product.admin@demohost.siebel.com
ISS Joint Workspace
BusComp
PackageNameList|Attribute
Definition
Workspace Attribute Defn
Template
ISS Joint Workspace
BusComp
PackageNameList|Product
Class Definition
Workspace Product Class Defn
Template
Attribute VOD BusComp PackageNameList Attribute Defn Template
ISS Class VOD BusComp PackageNameList Product Class Template
246
POP3 Account Name: support
POP3 Account Password: support
POP3 Server: demohost.siebel.com
SMTP Server: rgmamersmtp.oraclecorp.com
The communication profile is added the in the user properties of the business components listed in
To set up the Time- Based Offering feature
1 Create Product Master Data.
a Create three attributes:
Duration (Number/Enumerated, values 1, 2,3, 31)
DurationUnitOfMeasure (Text/Enumerated values: Days, Months, Years)
DurationValidityStart (Text/Enumerated Values: Original Start, Now, Original End)
b Create a class with the preceding three attributes.
NOTE: The class attribute names and the attribute definition names must be identical.
c For the TBO Discount products synced from BRM, change the structure type to Customizable,
change the product type to Time Based Offer, and associate the preceding TBO class to this
product.
2 Create Job to Inactive Assets.
a Navigate to Server Management > Jobs, and create a new job.
Select Component as Workflow Process Batch Manager.
Select Repeating as Y.
Select Requested Server as the Siebel Server.
Select Repeat Unit as Days.
Select Repeat Interval as 1.
Select Repeat From as Scheduled Start.
b Navigate to Job Parameters and create a new parameter.
c Select Workflow Process Name as the name and specify SWI Asset Status Update as the value.
d Select Search Specification as the name and specify the value if necessary.
ISS Joint Workspace
BusComp
CommProfileOverride Default SMTP Profile
Attribute VOD BusComp CommProfileOverride Default SMTP Profile
ISS Class VOD BusComp CommProfileOverride Default SMTP Profile
3 Create Revision Data Maps.
a Navigate to Administration Application, and then Data Map Administration.
b In Data Map Object, query for Name = Revise Order or ReviseQuote.
c In Data Map Component, query for Name = Line Item.
d In Data Map Field, add the fields that needs to be copied during revision (such as Service End /
Service Start Date/Due Date).
4 Configure the business service.
The business service name must be specified as the value for the Business Service Query Access
List server component parameter.
For example, if the server component is eCommunications Object Manager (ENU), navigate to
its parameters, query for Name = Business Service Query Access List, add Value = CMU
External Integration Service, and restart the server component so that the change to the
component parameter value takes effect.
5 Release the data maps:
a Navigate to Site Map > Administration- Order Management > Variable Maps.
b In Variable Map, query for the following:
Default Pricing Variable Map XA
c Lock the preceding variable maps and release a new version.
Tasks Required for the MDM PIP
The following tasks are required if you are using the MDM PIP.
To activate the workflow policies
1 Navigate to Administration - Business Process Screen, and then Workflow Policies view.
2 Query for the following workflow policies and remove the expiration date:
SWI Account Address Sync Policy
SWI Account Contact Sync Policy
SWI Account Sync Policy
SWI Address Sync Policy
SWI Contact Address Sync Policy
SWI Contact Sync Policy
3 Remove the existing triggers, and then generate the triggers.
248
4 Restart Siebel Services.
NOTE: By default, the Workspace Release Flag user preference is set to N. If you want to release
products into the Siebel application automatically, you must change this preference.
To customize the Workspace Release flag
1 Navigate to Site Map > Administration - Application > System Preferences.
2 Query for 'Workspace Release Flag', set the value to N, and restart the server.
Use the procedures in the following section to configure ACR 475.
System Requirements for ACR 475
The following section contains information about the supported databases and operating systems for
ACR 475.
System Requirements for DRM
DRM version 11.1.2.0.3 is certified with Siebel 8.1.1.4.
The following operating systems are supported:
Microsoft Windows 2003 and 2008
The following database is supported:
Oracle 10g/11g
The following homogenous operating system/database combinations are certified:
NOTE: Both Oracle and IIR servers are on the same operating system and both the Oracle database
and the IIR database are on the same database.
Microsoft Windows 2003/Oracle 11g
NOTE: Hyperion Data Relationship Management is only supported on the Windows platform.
Software Version Description
ADF 11.1.1.54.7 Oracle framework for the Java application
ANT 1.6 A Java-based build tool
JDK 1.6 Provides runtime for the Java application
Weblogic 10gR3 Java application server
Release Notes for ACR 475
The following section contains information about known issues with ACR 475.
Querying for New Prospects Causes Error
Category: Data Quality
Subcategory: ODQ Connector
Change Request: 12-215L8J5
When users query for a newly-created prospect, they receive an error message.
Within Prospect Mapping, do the following:
Change the Vendor Mapping Id to Row Id.
Within Siebel Tools, navigate to the List Mgmt Prospective Contact business component, add
a new field called RowId, and map it to Id.
Installer Does Not Overwrite Customer Version of CCHtmlType.swf
Change Request: 12-1TK672L
The installer does not automatically overwrite the customer version of the CCHtmlType.swf file. The
UI-related fixes will not take effect unless the configuration files are delivered by the installer. To
receive the updated configuration files, users must set the Overwrite flag to Y in the Siebel.ini file.
1 Copy the patch installer onto the local machine.
2 Change the value of OverWriteConfig=Yes in the following files:
Siebel_Enterprise_Server/enu/siebel.ini
Siebel_Enterprise_Server/siebel.ini
Siebel_Web_Server_Extension/enu/siebel.ini
Siebel_Web_Server_Extension/siebel.ini
3 Install the base release and the patch.
Back Button Navigates Incorrectly When Tabs Present
Change Request: 12-1UTNLYY
The Back button navigates incorrectly when tabs are present in the DGM screen.
Workaround: None
250
Initial Load Process Does Not Support Cross-Database Pull
Change Request: 12-1VJIM79
The Initial Load process does not support cross-database (platform) data pull.
Workaround: Have the same database type for Siebel and IIR.
Installation Overview for ACR 475
The following section contains an overview of the different builds that you must install to be able to
implement ACR 475.
Installation Sequence for ACR 475
The installation sequence for ACR 475 for UCM 8.2 is as follows: Siebel 8.1.1. SIA + Siebel 8.1.1.4
Fix Pack.
Zip Files for ACR 475
The ACR437_UCM.zip file. This file is packaged with the Siebel 8.1.1.1 Fix Pack.
The ACR475A_UCM.zip, ACR475B_UCM.zip, ACR475B_UCM_1.zip, ACR475B_UCM_2.zip,
ACR475B_UCM_3.zip, ACR475B_UCM_4.zip and ACR475B_UCM_5.zip files.
The following is an overview of the installation process.
1 Install the Siebel Tools build and connect to the server database.
2 Navigate to the Siebel Tools installation directory <Tools Install Director>\REPPATCH folder.
3 Unzip the ACR437_UCM.zip file from <Tools Install Directory>\REPPATCH and configure ACR 437
using the instructions provided in the Siebel Maintenance Release Guide, Version 8.1.1.x. To
access this guide, from within My Oracle Support, navigate to the Knowledge tab and search for
Article ID 880452.1.
4 Unzip the ACR475A_UCM.zip file from <Tools Install Directory>\REPPATCH and import the seed
data for ACR 475A. For instructions, see Configuration Instructions for ACR 475A on page 251.
5 Complete the ACR 437 and ACR 475A setup, including applying the Base Tables and EIM Table
schemas.
CAUTION: It is important that you complete the entire setup for ACR 437 and ACR 475A before
you make the repository changes for ACR 475B.
6 Unzip the ACR475B_UCM.zip and ACR475_UCM_1.zip files from <Tools Install
Directory>\REPPATCH and perform the required configuration changes.
7 Unzip the ACR475B_UCM_2.zip file from <Tools Install Directory>\REPPATCH and perform the
required configuration changes.
CAUTION: If you want to use DRM, do not unzip the UCM_3.zip file.
Configuration Instructions for ACR 475A
Use the procedures in the following sections to install and configure ACR 475A.
CAUTION: In order to implement ACR 475B, you must already have installed ACR 437 and ACR
475A. ACR 437 was included in the Siebel 8.1.1.1 Fix Pack. For information about how to install and
configure ACR 437, see the Siebel 8.1.1.x Maintenance Release Guide on My Oracle Support. To
access this guide, navigate to the Knowledge tab, and search for Article ID 880452.1. For information
about how to install ACR 475A, see Configuration Instructions for ACR 475A on page 251.
Configuration Instructions for ACR 475A
The following section contains information about how to install and configure ACR 475A.
NOTE: For more information about what functionality ACR 475A provides, see Oracle Universal
Customer Master for Higher Education Constituent Hub Administration Guide on My Oracle Support.
To access the guide, navigate to the Knowledge tab and search for Article ID 863982.1.
This section includes information on how to set up and configure Oracle Higher Education Constituent
Hub Web services. The following topic is included:
Process for Configuring Oracle Higher Education Constituent Hub Web Services on page 251
Both the Match and Fetch Web service are set up with the following tasks. If you need to manually
configure the Web services, see Article ID 763962.1 on My Oracle Support.
Process for Configuring Oracle Higher Education Constituent Hub Web Services
You must set up and configure the Web Services.
To set up Oracle Higher Education Constituent Hub Web services for ACR 475A, perform the following
tasks:
Importing the SIF Files on page 251
Compiling the SRF and Restarting the Siebel Server on page 254
Importing Seed Data on page 255
Importing the SIF Files
This task is a step in Process for Configuring Oracle Higher Education Constituent Hub Web Services
on page 251.
SIF files contain Siebel object definitions that can be imported into Siebel Tools to replace existing
definitions. Following successful application of ACR 475A, you will then locateand import the SIF files
that came with the Quick Fix into Siebel Tools. This SIF file contains object definitions that are
different from those contained in your present repository.
252
To import the .sif files
1 Navigate to the Siebel Tools installation directory <Siebel Tools Install Directory>\REPPATCH.
2 Unzip the .sif files from the Tools\ACR475A_UCM.zip file.
3 Open the Sifs folder, and verify that the following .sif files are present:
Tables.sif
NOTE: Be sure to import Tables.sif before EIMtables.sif.
Applets.sif
BusinessComponents.sif
BusinessObjects.sif
BusinessService.sif
EIMTables.sif
IntegrationObjects.sif
Links.sif
PickList.sif
Screen.sif
NOTE: Before importing the SymbolicStrings.sif file, make sure the following parameter value is
set in tools.cfg file: SymSt r Pr ef i x = SBL_.
SymbolicStrings.sif
Views.sif
4 After verifying that the .sif files are all present, log on to Siebel Tools.
Contact
Symbolic Strings
Table CIF
Table Person
UCM CDM Child
UCM Data Management
UCM Higher Education
UCM SDH
VEAI UCM CIF
VEAI UCM CIF UI
EIM CIF
EIM Person
LOY Profiles
TIP: Use the following query to get the list of projects to lock or unlock: {Contact or Symbolic
Strings OR Table CIF OR Table Person OR UCM CDM Child OR UCM Data Management OR UCM
Higher Education OR UCM SDH OR VEAI UCM CIF OR VEAI UCM CIF UI OR Web Service
Integration OR EIM CIF OR EIM Person OR LOY Profiles}.
6 From the Tools menu, choose Import from Archive.
7 Import the first SIF file, using the Merge option.
8 Repeat Step 6 and Step 7 for the remaining SIF files.
9 In the Object Explorer, query for tables that have been modified, by using the Changed flag.
10 Make sure that the query returns the following values:
S_CONTACT
S_CONTACT_NAME
S_CONTACT_UCMX
S_CON_IDNTY_DOC
S_UCM_ADDR_PER
S_UCM_CONTACT
S_UCM_CON_CHILD
S_UCM_ORG_EXT
EIM_UCM_ADRPER
EIM_UCM_CON
EIM_UCM_CONCHLD
EIM_UCM_ORG
EIM_CONTACT3
11 Select a modified table, then click the Apply/DLL button.
The Choose Option window appears.
12 Choose Apply, then click OK.
A prompt appears requiring login credentials.
13 Enter the required information for your database, including the exact ODBC name for your
database.
14 Click Apply.
The modification process may take a moment.
15 Once the process is finished, click OK to finish the table schema changes.
254
16 Repeat Step 11 through Step 15 until all required tables have been modified.
TIP: You can apply the schema changes to all the tables in one pass by selecting the Current
Query in the Tables drop-down in the Apply Schema window. To perform this you have to have
executed a query with changed flag set.
Compiling the SRF and Restarting the Siebel Server
on page 251.
The Siebel repository:
si ebel _si a. sr f
is located at:
<Ser ver I nst al l Locat i on>\ ses\ si ebsr vr \ obj ect s\ enu\ si ebel _si a. sr f .
Compile the business object changes you made in the preceding steps for the changes to take effect.
To compile and restart the Siebel Server
2 In Siebel Tools, compile the following projects:
Contact
Symbolic Strings
Table CIF
Table Person
UCM CDM Child
UCM Data Management
UCM SDH
VEAI UCM CIF
VEAI UCM CIF UI
EIM CIF
EIM Person
LOY Profiles
3 In the Object Explorer, navigate to integration objects.
4 Query for the Integration Objects that were imported from the .sif files.
The following Integration Objects were modified for ACR 475A:
SwiPersonIO
SwiPersonPublishIO
CIFContact
CIFContactInsert
CIFContactInsertRs
CIFContactUpdate
CIFContactUpdateRs
CIFContactUpsert
CIFContactUpsertRs
UCMContactSourceDataAndHistory
5 For each of the Integration Objects that were imported, choose Undeploy from the right-click
menu, then step off the record to retain changes.
6 From the right-click menu, choose Deploy to Runtime database.
7 Start the Siebel Server using the newly compiled SRF.
Importing Seed Data
on page 251.
To import seed data
1 From the Windows Start menu, select Control Panel, Administrative Tools, then Data Sources
ODBC.
2 Click the System DSN tab.
3 Click Add, then choose the Siebel Oracle90 driver.
4 Enter a data source name, and the name of the server you will be connecting to.
TIP: For an Oracle database, enter the TNS service name that you created to connect Siebel
Tools to the Oracle database.
5 Navigate to <Tools Install Directory>\REPPATCH\ ACR475A.
6 Before executing the next step, make sure that the dataimp.exe file exists in the <Tool s I nst al l
di r ect or y>\ bi n directory.
Importing Seed Data For ENU Implementations
ENU implementations require you to import two .dat files which contain seed data.
To import required .dat files
1 Run the following command to import the seed.dat file:
256
<Tool s I nst al l Di r ect or y>\ bi n\ dat ai mp / u <USERNAME> / p <PASSWORD> / f <Tool s I nst al l
Di r ect or y>\ REPPATCH\ ACR475A_UCM\ SeedDat a\ ACR475A_Seed. dat / l <Tool s I nst al l
Di r ect or y>\ t emp\ dat ai mp_seed. l og / c <ODBC Sour ce Name> / d <Tabl e Owner > / i <Tool s
I nst al l Di r ect or y>\ REPPATCH\ ACR475A_UCM\ SeedDat a\ <Dat abase
Pl at f or m>\ ACR475A_Seed. i np / e n / h l og
NOTE: The /e n switch enforces the dataimp process to only look at tables in the imp file. To
track unique constraint violations, see the /h log file.
Replace Tools Install Directory with your Siebel Tools installation directory.
Replace ODBC Source Name with the ODBC you created in Step 3 of the To import seed data
procedure.
Replace Database Platform with your database platform, (for example: Oracle, MSSQL, and
so on).
Replace username with your database user Id.
Replace password with your database password.
2 Run the following command to import the ENU seed.dat file:
Di r ect or y>\ REPPATCH\ ACR475A_UCM\ SeedDat a\ ENU\ ACR475A_Seed_Local e_ENU. dat / l <Tool s
I nst al l Di r ect or y>\ t emp\ dat ai mp_seed. l og / c <ODBC Sour ce Name> / d <Tabl e Owner > / i
<Tool s I nst al l Di r ect or y>\ REPPATCH\ ACR475A_UCM\ SeedDat a\ <Dat abase
Pl at f or m>\ ACR475A_seed_l ocal e_ENU. i np / e n / h l og.
procedure.
so on).
Replace username with your database user ID.
3 Review the Si ebel Tool s I nst al l Di r ect or y>\ t emp\ dat ai mp_seed. l og file to make sure that
the import completed successfully.
Importing Seed Data For Non-ENU Implementations
Non-ENU implementations require you to import two .dat files: the base ENU seed.dat and the locale
specific, seed_locale_XXX.dat, where XXX is the language code.
To import required .dat files
1 Run the following command to import the seed.dat file:
Di r ect or y>\ REPPPATCH\ ACR475A_UCM\ SeedDat a\ ENU\ ACR475A_Seed_Local e_ENU. dat / l
<Tool s I nst al l Di r ect or y>\ t emp\ dat ai mp_Seed. l og / c <ODBC Sour ce Name> / d <Tabl e
Owner > / i <Tool s I nst al l Di r ect or y>\ REPPATCH\ ACR475A_UCM\ SeedDat a\ <Dat abase
Pl at f or m>\ ACR475A_seed_LOCALE_ENU. i np / e n / h l og
NOTE: The /e n file enforces the dataimp process to only look at tables in the imp file. To track
unique constraint violations, see the /h log file.
procedure.
so on).
2 Run the following command to import the seed_locale_XXX.dat file:
<Tool s I nst al l Di r ect or y>\ bi n\ dat ai mp / u SADMI N / p sadmi n / f <Tool s I nst al l
Di r ect or y>\ REPATCH\ ACR475A_UCM\ SeedDat a\ <LANG>\ ACR475A_seed_l ocal e_xxx. dat / l
<Tool s I nst al l Di r ect or y>\ t emp\ dat ai mp_seed_l ang. l og / c <ODBC Sour ce Name>/ d <Tabl e
Owner > / e n / h l og.
procedure.
so on).
3 Review the Si ebel Tool s I nst al l Di r ect or y>\ t emp\ Seed. l og file to make sure that the import
Configuration Instructions for ACR 475B
NOTE: You must have installed the Siebel 8.1.1.1 Fix Pack, ACR 437, and ACR 475A before you can
install ACR 475B. For information about how to install ACR 437, see Siebel Maintenance Release
Guide Version 8.1.1.x on My Oracle Support. To access this guide, navigate to the Knowledge tab,
and search for Article ID 880452.1.
For information about how to install ACR 475A, see Configuration Instructions for ACR 475A on
page 251.
Importing the SIFs and Workflows in the ACR 475B_UCM.zip File
Use the following procedure to import the SIFs and workflows packaged in the ACR 475B_UCM.zip
file.
258
To import the SI Fs and workflows for ACR 475B
1 Verify that the Sifs folder within the ACR475B_UCM.zip file contains the following .sif files:
Applets.sif
Applications.sif
BusinessObjects.sif
BusinessServices.sif
Classes.sif
Command.sif
Dlls.sif
EBCTable.sif
EIMTables.sif
Links.sif
Menu.sif
PickList.sif
Screens.sif
SymbolicStrings.sif
Tasks.sif
Tables.sif
Views
WebTemplates.sif
Workflows.sif
NOTE: The Tables.sif file should be imported before you apply the EIM changes. Apply this table
in merge mode.
2 Verify that the SIFs folder within the ACR475B_UCM_1.zip file contains the following .sif files:
BS_UCM_DataQualityManager.sif
WF_UCMBatchProcess.sif
3 Log into Siebel Tools, and lock the following projects:
Account
Account (SSE)
Account Hierarchy
Comm Manager
Common Components
Contact
DNB Data
DQ ISS Integration
DeDuplication
Household
LOY Profiles
Menu
Server Components - Object Manager
Siebel Workflows - Seed
Symbolic Strings
Table CIF
Table Organization
Table Party
Table Person
UCM CDM Child
UCM Data Management
UCM Hierarchy Management
UCM Merge
UCM SDH
UCM Survivorship
UCM Task UI
UCM Unmerge
VEAI UCM Account ASI
VEAI UCM CIF
VEAI UCM CIF UI
VERT CUT Address
260
Use the following query to get the list of projects to lock/unlock:
{
i . " Tabl e Or gani zat i on" OR " Tabl e Par t y" OR " Tabl e Per son" OR " UCMCDMChi l d" OR " UCM
Dat a Management " OR " UCM Hi er ar chy Management " OR " UCM Hi gher Educat i on" OR " UCM
Mer ge" OR " UCM Pr i vacy Management " OR " UCM SDH" OR " UCM Sur vi vor shi p" OR " UCM Task
UI " OR " UCMUnmer ge" OR " VEAI UCMAccount ASI " OR " VEAI UCMCI F" OR " VEAI UCMCI F UI "
OR " VERT CUT Addr ess" OR " Web Ser vi ce I nt egr at i on"
i i . " Account " OR " Account ( SSE) " OR " Account Hi er ar chy" OR " CommManager " OR " Common
Component s" OR " Cont act " OR " DNB Dat a" OR " DQ I SS I nt egr at i on" OR " DeDupl i cat i on"
OR " Househol d" OR " LOY Pr of i l es" OR " Menu" OR " Ser ver Component s - Obj ect Manager "
OR " Si ebel Wor kf l ows - Seed" OR " Symbol i c St r i ngs" OR " Tabl e CI F" }
4 Before importing the SymbolicStrings.sif file, make sure that the SymStrPrefix=SBL parameter
exists in the tools.cfg file.
5 Import all of the .sifs except EIMTables.sif to the server database using the merge mode. Import
the .sifs from ACR475B_UCM.zip before you import the .sifs from ACR475B_UCM_1.zip.
6 Within Object Explorer, navigate to Tables, and query for tables that have changed by selecting
the query with the Changed flag set.
The query will give you the following list of tables:
S_ADDR_PER
S_CONTACT
S_CONTACT_NAME
S_CONTACT_UCMX
S_CON_ADDR
S_CON_IDNTY_DOC
S_DYN_HRCHY
S_DYN_HRCHY_REL
S_PARTY_REL
S_PARTY_UCMX
S_UCMIMPORT_TSK
S_UCMIMPTSK_ARG
S_UCMIMPTSK_LOG
S_UCMSRVTSK_MSG
S_UCM_ADDR_PER
S_UCM_ATGP_RULE
S_UCM_CONTACT
S_UCM_CON_CHILD
S_UCM_CON_DECAY
S_UCM_HRCHY
S_UCM_HRCHY_REL
S_UCM_IMPMP_ITM
S_UCM_IMPRT_MAP
S_UCM_MERGE_REQ
S_UCM_MRG_ASSOC
S_UCM_OGP_CHILD
S_UCM_ORGRP_MRG
S_UCM_ORG_CHILD
S_UCM_ORG_DECAY
S_UCM_ORG_EXT
S_UCM_RULE_SET
S_UCM_SRVR_TSK
7 With the query result, perform the following steps to extend the schema:
a Click the Apply/DLL button.
The Choose Option window displays.
b Choose Apply and click OK.
c In the window for login credentials and database information, enter the database administrator
password.
d From the Tables drop-down list, select Current Query.
e For ODBC data source, enter the exact ODBC name of the database, and click Apply.
f Wait until the process is finished and the tables are modified, and then click OK to finish the
schema changes for the tables.
8 Within Object Explorer, navigate to Integration Objects.
9 On the right pane, query for the Integration Objects that changed during the sif file import.
10 Select all changed Integration Objects, right-click and select Undeploy, and then refresh.
11 Right-click and selct Deploy to deploy the changes to the runtime database.
The server repository- siebel_sia.srf located in
<ServerInstallLocation>\ses\siebsrvr\objects\enu\siebel_sia.srf should be compiled for the changes
in the above .sif files to take effect.
262
Applying the EIM Changes in the ACR475B_UCM.zip File
As part of the ACR475B release, EIM changes have been done on the database. The
REPPATCH\ACR475B_UCM\Sifs\EIMTables.sif file contains these changes.
NOTE: Import the Tables.sif file before you proceed with the EIM changes.
The EIMTables.sif file contains changes to the following existing tables:
EIM_ADDR_PER
EIM_CONTACT1
EIM_ACCOUNT2
EIM_ACCOUNT3
EIM_CONTACT3
EIM_UCM_CON
EIM_UCM_ORG
EIM_UCM_CONCHLD
EIM_UCM_ORGCHLD
EIM_UCM_OGPCHD
EIM_PTYUCM_DTL
The EIMTables.sif file contains the following new EIM tables:
EIM_UCM_MRGREQ
EIM_UCM_ORGDCY
EIM_UCM_CONDCY
EIM_UCM_IMPTSK
EIM_UCM_SRVTSK
EIM_UCM_IMPMAP
EIM_UCM_HRCHY
Use the following procedure to import the EIMTables.sif file into the repository.
To import EI MTables.sif into the repository:
EIM Organization
EIM Person
EIM CIF
2 Within Siebel Tools, use the Import from Archive function to read this file and create the tables
in the repository. The "merge" option should be used while importing this file.
To apply the EI MTables.sif file
1 Within Siebel Tools, query for the list of tables that were imported into the repository.
2 Use the "Apply/DDL" button to apply the changes to the physical database.
3 Unzip the ACR475B_UCM.zip file from <Tools Install Directory>\REPPATCH.
NOTE: If you have previously installed ACR 475B QFs, note that the ACR475B_UCM file has been
replaced by the ACR475B_UCM_2.zip file.
The unzipped ACR475B_UCM folder contains the following structure:
EIM_Files
Knowledgebases
Non-ENU Symbolic Strings
Schemas
SeedData
Sifs
WebServices_XML
Updating the EIM Files
As part of the ACR475B release, the EIM files - eim45.sql and eim_export_lookup_bu_name.sql have
undergone a change. The REPPATCH\ACR475B\Repository\Table\EIM\eim45.sql and
REPPATCH\ACR475B\Repository\Table\EIM\eim_export_lookup_bu_name.sql files have all of the
changes required for the ACR and should replace the files in the following locations in the Siebel
server directory:
Ei m45. sql : <I nst al l at i on Locat i on>\ SERVER\ si ebsr vr \ SQLTEMPL
ei m_expor t _l ookup_bu_name. sql : <I nst al l at i on Locat i on>\ SERVER\ si ebsr vr \ ADMI N
To compile the SRF and restart the server
Use the following procedure to compile the SRF and restart the server.
1 Stop the relevant server
2 Lock the projects that were newly added in this release.
UCM Merge Task UI
UCM List Import
UCM Data Decay Management
Table UCM DRM Integration
Table UCM Import
DqSync
NOTE: If you have customized projects, lock these projects as well.
264
3 Compile all of the locked projects.
4 Start the server using this newly-compiled srf.
Use the following procedure to activate the workflows for ACR 475B.
To activate the workflows for ACR 475B
1 Navigate to Site Map > Administration Business Process > Workflow Deployment.
2 In the Workflow Deployment screen, click the Active Workflow Process tab.
3 In the top Repository Workflow Processes applet, query for the workflows, select them, and click
the Activate button.
4 In the bottom Active Workflow Processes applet, query for the workflows that you just activated
and verify that the Activation Date/Time and Expiry Date/Time are valid.
5 Repeat Step 1 through Step 4 for the workflows listed below.
NOTE: You can use the following query for query for all of the workflows: UCM*Batch Data
Management Workflow OR UCM*Data Decay Process OR UCM Batch Process* OR UCM*SOAP
Process OR UCM Import File Processing OR UCM Master List Import Process OR UCM Process
Merge Request OR UCM SOAP Customer Profile Integration Process. The ISS workflows: ISS
Delete Record Sync OR ISS Launch Pre*Sync OR ISS Launch Write Record Sync OR ISS Write
Record Sync OR ISSGetOldCountry should only be activated if you want to use the xml sync
server to sync records with the IIR Server.
UCM Account Batch Data Management Workflow
UCM Account Data Decay Process
UCM Batch Process - Single Step
UCM Batch Process
UCM Contact Batch Data Management Workflow
UCM Contact Data Decay Process
UCM Financial Asset Customer Profile Integration SOAP Process
UCM Group Customer Profile Integration SOAP Process
UCM Import File Processing
UCM Master List Import Process
UCM Organization Customer Profile Integration SOAP Process
UCM Organization Hierarchy Management Integration SOAP Process
UCM Person Customer Profile Integration SOAP Process
UCM Process Merge Request
UCM SOAP Customer Profile Integration Process
Importing the SIF Files in the ACR475B_UCM_2.zip File
Use the following procedure to import the ACR475B_UCM_2.zip file. (This file is packaged with the
build.)
CAUTION: You must import the Tables.sif file before you import the EIMTables.sif file.
1 Verify that the ACR475B_UCM_2.zip file contains the following SIF files:
Applets.sif
Contact Personal Address Mvg Applet
UCM Account Source Data and History List Applet
UCM Contact Source Data and History List Applet
UCM HE Constituent Address Source Data and History List Applet
Account
Contact
UCM Account Source Data and History
UCM Contact Source Data and History
BusinessObjects.sif
Merged Account
Merged Contact
DQ Sync Services
ISS System Services
UCM Data Quality Manager
UCM Merge Service
UCM Source Data and History Service
EIMTables.sif
EIM_UCM_ADRPER
EIM_UCM_ASSET
EIM_UCM_CON
EIM_UCM_HRCHY
EIM_UCM_ORG
EIM_UCM_ORGGRP
CIFContact
SwiOrganizationMatchInputIO
266
SwiOrganizationMatchOutputIO
SwiPersonMatchInputIO
SwiPersonMatchOutputIO
SyncAccount
SyncContact
SyncProspect
UCMAccountSourceDataAndHistory
UCMAccountTaskUIMerge
UCMContactTaskUIMerge
Tables.sif
S_UCM_ADDR_PER
S_UCM_ASSET
S_UCM_CONTACT
S_UCM_ORGGRP
S_UCM_HRCHY
S_UCM_HRCHY_REL
S_UCM_ORG_EXT
Views.sif
UCM Account UnMerge View
UCM Contact UnMerge View
Workflows.sif
UCM Account Batch Data Management
UCM Batch Process
UCM Batch Process - Single Step
UCM Contact Batch Data Management
Account
Contact
DQ ISS Integration
EIM CIF
Employee
Table CIF
UCM Data Management
UCM Merge Task UI
UCM SDH
UCM Unmerge
VEAI UCM CIF
VEAI UCM CIF UI
UCM SDH
UCM Merge
3 Import the SIF files to the server database using the Merge mode.
4 In the Object Explorer, navigate to Integration Objects, and in the right pane, query for the
Integration Objects that changed during the sif file import.
5 For each of the changed Integration Objects, right-click, select Undeploy, refresh, right-click
again, and select Deploy to Runtime Database.
The file ACR475B_UCM_3.zip file contains the following SIF files in the SIFs folder:
Applets.sif
Dynamic Hierarchy Admin List Applet
Screens.sif
CIF Administration Screen
Views.sif
DRM Web Client View
Hierarchy Selection View
UCM Hierarchy History Flat List View
Use the following procedure to import the ACR475B_UCM_3.zip file.
CAUTION: The ACR475B_UCM_3.zip file inactivates DRM. If you want to use DRM functionality, do
not import the ACR475B_UCM_3 file.
268
To import the ACR475B_ UCM_ 3.zip file
Account Hierarchy
VEAI UCM CIF UI
2 Import all of the SIFs to the server database using the Merge option.
3 Stop the relevant server.
Account Hierarchy
VEAI UCM CIF UI
6 Start the server using the newly-compiled SRF.
If you have imported the SIF files from UCM_3.zip, and you want to use DRM, use the following
procedure to revert the changes and to manually enable DRM.
To manually enable Oracle Hyperion Data Relationship Management for Oracle
Customer Hub
1 In the Siebel Tools Object Explorer, click View, and then query for the following views:
UCM Hierarchy History Flat List View
DRM Web Client View
2 In the Properties window, change the Inactive value for each view from TRUE to FALSE.
3 In the Object Explorer, click Applet, then query for Dynamic Hierarchy Admin List Applet, and
then change the following properties:
a In the Object Explorer click Control, query for Advanced Hierarchy, and then in the Properties
window, change the Inactive value from TRUE to FALSE.
b In the Object Explorer, click Applet Web Template, click Applet Web Template Item, and query
for Advanced Hierarchy.
c In the Properties window, change the Inactive value from TRUE to FALSE for both the Base and
Edit List Applet Web Templates.
4 In the Object Explorer, click Screen, and then query for CIF Administration Screen.
5 In the Object Explorer, click Screen View, query for UCM Hierarchy History Flat List View, and in
the Properties window, change the Inactive value from TRUE to FALSE.
6 Compile the objects into the SRF, and restart the Siebel Server.
1 Verify that the following .sif files exist:
Applets.sif
Alternate Phone MVG Applet
Communication Address MVG Applet
LOY Communication Email List Applet
LOY Communication Phone List Applet
UCM HE Communication Email Source Data and History List Applet
UCM HE Communication Phone Source Data and History List Applet
UCM HE Constituent Affiliation Source Data and History List Applet
UCM HE Constituent Name MVG Applet
UCM HE Constituent Source Data and History List Applet
UCM HE Personal Address Pick Applet
Contact
UCM HE Constituent Affiliation Source Data and History
DQ Sync Services
UCM Utility Service
CIFContact
CIFContactInsert
CIFContactInsertRs
CIFContactUpdate
CIFContactUpdateRs
CIFContactUpsert
CIFContactUpsertRs
SwiPersonIO
SwiPersonPublishIO
270
Views.sif
WebTemplates.sif
View 50 50 50 Framed
Workflows.sif
UCM Account Batch Data Management Workflow
UCM Contact Batch Data Management Workflow
UCM Financial Asset Customer Profile Integration SOAP Process
UCM Group Customer Profile Integration SOAP Process
UCM Organization Customer Profile Integration SOAP Process
UCM Organization Hierarchy Management Integration SOAP Process
UCM Person Customer Profile Integration SOAP Process
2 Within Siebel Tools, lock the following projects:
Comm Manager
Contact
DQ ISS Integration
LOY Profiles
UCM SDH
VEAI UCM CIF
3 Import all the SIFs to the server database using Merge mode.
4 Within Object Explorer, navigate to Integration Objects, and query for the integration objects that
changed during the SIF file import.
5 For each of the changed integration objects, right-click, select Undeploy, select Refresh, right-
click, and select Deploy to Runtime Database.
<ServerInstallLocation>\ses\siebsrvr\objects\enu\siebel_sia.srf needs to be compiled for the
changes in the preceding .sif files to take effect.
Use the following procedure to compile the server repository.
To compile the server repository
2 Lock the projects that were modified in this release:
Comm Manager
Contact
DQ ISS Integration
LOY Profiles
UCM SDH
VEAI UCM CIF
Use the following procedure to deploy the UCM workflows.
To deploy the UCM workflows
1 In Siebel Tools, select the changed workflows, set appropriate workflow process properties, and
then click the Publish/Activate button.
2 In the Siebel application, navigate to Site Map > Administration - Business Process > Workflow
Deployment, and query for the changed workflows in the Repository Workflow Processes applet.
3 Click the Activate button to activate workflows that have not already been activated.
4 Within the Active Workflow Processes applet, verify that the workflows are active.
1 Verify that the following .sif files exist:
Applets.sif
UCM Account Address Source Data and History List Applet
272
UCM Contact Address Source Data and History List Applet
CIF Systems List Applet
DataEnrichment
UCM Data Quality Manager
2 Within Siebel Tools, lock the following projects:
DeDuplication
UCM Data Management
UCM SDH
VEAI UCM CIF UI
3 Import all the SIFs to the server database using Merge mode.
<ServerInstallLocation>\ses\siebsrvr\objects\enu\siebel_sia.srf needs to be compiled for the
changes in the preceding .sif files to take effect.
2 Lock the following projects that were modified in this release:
DeDuplication
UCM Data Management
UCM SDH
VEAI UCM CIF UI
Applying the Table Definition
Use the following procedure to apply the table definition for the tables that were changed during the
ACR475B_UCM_2.zip file import.
To apply the table definition
1 In Object Explorer, navigate to Tables, and query for the tables that were changed. (Select the
queries that have the Changed flag.)
2 With the query results, perform the following tasks to extend the schema:
a Click the Apply/DLL button.
The Choose Option dialog displays.
b Choose Apply and click OK.
The login credentials and database information dialog box appears.
c Enter the dba password for login credentials.
d In the Tables drop-down list, select Current Query.
e ODBC data source, enter the ODBC name, and click Apply.
f Wait until the process is finished and the tables are modified.
g When the process has finished, click OK to complete the schema changes for the tables.
Importing Non-ENU Symbolic Strings
For languages other than ENU, open the Non-ENUSymbolicStrings folder and import the non-enu
symbolic strings to the database.
NOTE: This folder exists in both the ACR475B_UCM.zip, ACR475B_UCM_4.zip, and
ACR475B_UCM_5.zip files. These folders also include a document with instructions for importing
non-ENU symbolic strings.
For the "Knowledgebases" and "Sifs" categories and feature-specific setup instructions, use the
instructions in Importing the SIFs and Workflows in the ACR 475B_UCM.zip File on page 257 to
bring the categories into the testing target database.
Importing the Seed Data in the ACR475B_UCM_2.zip and
ACR475B_UCM_5.zip Files
NOTE: If you are an existing customer who has already installed QF3101, QF3102, or QF3103, you
do still need to import the ACR475B_UCM_2.zip file, as this file contains necessary fixes.
For Oracle enter the TNS service name that you created to connect Siebel Tools to the
database.
2 In the command prompt, navigate to the directory where you installed Siebel Tools\BIN.
NOTE: Make a note of the directory where the seed data is extracted to - [REPPATCH\ACR475B\
ACR475B_UCM_2\SeedData ].
3 Before you import ACR475B_Seed.dat, make sure that the dataimp.exe file exists in the <Tools
Install Directory>/bin directory.
274
<Tool s I nst al l Di r ect or y\ bi n>dat ai mp / u <USERNAME> / p <PASSWORD> / f <Tool s I nst al l
Di r ect or y>\ REPPATCH\ ACR475B\ ACR475B_UCM_2\ SeedDat a\ ACR475B_Seed. dat / l <Tool s
I nst al l Di r ect or y>\ t emp\ dat ai mp_seed. l og / c <ODBC Sour ce Name> / d <Tabl e Owner >/ i
<Tool s I nst al l Di r ect or y>\ REPPATCH\ ACR475B
\ ACR475B_UCM_2\ SeedDat a\ ACR475B_SeedI np_Fi l es\ <Dat abase Pl at f or m>\ ACR475B_Seed. i np
/ q - 1 / w y / e n / t n / x R / n 100 / h l og
<Tools Install Directory> - Replace with the Siebel Tools install directory
<Database Platform> - Replace with the database platform (ORACLE, DB2UDB, or MSSQL)
6 Seed data import includes mono-language seed data import and language seed-data import. If
you are an ENU (English Language) customer, do the following:
a To import ACR475B_Seed_Locale_ENU.dat, run the following command after importing the
ACR475B_Seed.dat file:
Directory>\REPPATCH\ACR475B\ACR475B_UCM_2\SeedData\ACR475B_Seed_Locale_ENU.
dat /l <Tools Install directory>\temp\dataimp_seed_locale_ENU.log /c <ODBC Source
Name> /d <Table Owner> /i Owner>/i <Tools Install
Directory>\REPPATCH\ACR475B\ACR475B_UCM_2\SeedData\ACR475B_SeedInp_Files\<Da
tabase Platform>\ACR475B_seed_locale_ENU.inp /q -1 /w n /e y /t n /x R /n 100 /h log
<Database Platform> - Replace with Database Platform (ORACLE, DB2UDB, or MSSQL)
b To import seed_locale_XXX.dat for languages other than ENU, run the following command after
importing ACR475B_Seed.dat file for importing the locale specific seed_locale_XXX.dat, where
XXX is the language code.
Directory>\REPPATCH\ACR475B\ACR475B_UCM_2\SeedData\ACR475B_NON_ENU_Seed_Lo
cale\seed_locale_XXX.dat /l <Tools Install directory>\temp\dataimp_seed_locale_XXX1.log
/c <ODBC Source Name> /d <Table Owner> /q -1 /w n /e y /t n /x R /n 100 /h log
c Run the following command for additional seed_locale_XXX.dat in the ACR475B_UCM_5.zip,
extracted to REPPATCH\ACR475B\ACR475B_UCM_5\SeedData, where XXX is the language code:
Directory>\REPPATCH\ACR475B\ACR475B_UCM_5\SeedData\ACR475B_NON_ENU_Seed_Lo
cale\seed_locale_XXX.dat /l <Tools Install directory>\temp\dataimp_seed_locale_XXX2.log
/c <ODBC Source Name> /d <Table Owner> /q -1 /w n /e y /t n /x R /n 100 /h log
7 Review the log file in <Tools Install Directory>\temp to make sure that the import completed
successfully.
Schemas and WebServices_XML
The ACR475B_UCM.zip, ACR475B_UCM_1.zip, and ACR475B_UCM_4.zip files contain schemas. Use
the later version in case of conflicts.
Copying ISS DLLs
Use the following procedure to unzip ISSdlls, which contains the ISS DLLs for all platforms. The ISS
connector DLLs are available within the bin folder within the IIR Installation folder.
To unzip I SSdlls
1 Select the respective dll for the platform required. The dlls modified are ssadqsea.dll,
ssadqasm.dll and ssasec.dll.
2 Place these in the bin or lib folder under the Siebel Server installation directory, depending upon
the platform chosen. These files contain the session pooling fix to be used in ISS 2.8.7.
NOTE: You can also pick up these DLLs from the IIR Server (located in the bin folder if IIR is
running on the same OS.
Installing Siebel Haley
You must install Siebel Haley before you install and activate knowledgebases and any rule-related
tasks.
Importing Knowledgebases
In the Knowledgebases folder provided in ACR475B_UCM.zip, you must bring the ucmdatadecay.xml
and ucmsurvivorshiprules.xml files into the target database to test Survivorship and Decay rules.
Use the following procedure to import knowledgebases for ACR 475B.
To import knowledgebases for ACR 475B
1 Navigate to Administration - Business Rules > Business Rule Knowledge Base.
2 Select Import Knowledge Base from the menu and and navigate to
REPPATCH\ACR475B_UCM\Knowledgebases to access the ucmdatadecay.xml and
ucmsurvivorshiprules.xml files, and import them.
3 Once the import is done, click the Activate button.
NOTE: The Activate button is no longer active after the import has completed.
276
Compiling the SRF File
The server repository- siebel_sia.srf file located in
<ServerInstallLocation>\ses\siebsrvr\objects\enu\siebel_sia.srf should be compiled for the changes
in the preceding SIF files to take effect.
2 Lock the projects that were modified in this release:
Account
Contact
DQ ISS Integration
EIM CIF
Employee
Table CIF
UCM Data Management
UCM Merge Task UI
UCM SDH
UCM Unmerge
VEAI UCM CIF
VEAI UCM CIF UI
UCM SDH
UCM Merge
Configuring the UCM Batch Process Server Component for Single
Threading
Use the following procedure to compile the server components and start the server.
NOTE: You must stop and restart both the Siebel Server and the Gateway Server for the changes in
the following procedure to take effect.
Execute the commands in the following procedure for the UCMBatchProcess component to run in
single-threaded mode. Make sure that there are no errors when you execute the following procedure.
To configure the server component and start the server
1 While the server is stopped, execute the following srvrmgr utility and connect to the gateway but
not to the server. Run srvrmgr as: srvrmgr /g <Gateway> /e <Enterprisename> /u <UserName>
/p <Password>
2 Execute the following commands for UCMBatchProcess component to run in single-threaded
mode. Make sure that there are no errors when executing the following sequence of steps.
srvrmgr> reconfig compdef UCMBatchProcess
srvrmgr> change param Threaded=true for compdef UCMBatchProcess
srvrmgr> commit reconfig compdef UCMBatchProcess
3 Start the server using the newly-compiled SRF.
Deploying the UCM Batch Process Workflow
Use the following procedure to deploy the UCM Batch Process workflow.
To deploy the UCM Batch Process workflow
1 In Siebel Tools, select the changed workflows, and click the Publish/Activate button.
2 Within the Siebel application, navigate to Site Map > Administration - Business Process >
Workflow Deployment.
3 In the Repository Workflow Processes applet, query for UCM Batch Process and UCM Process
Merge Request.
4 If the workflows are not already activated, click the Activate button.
5 In the Active Workflow Processes applet, verify that the workflows are active.
Configuring Data Decay Runtime Events
You must manually configure the seed data to enable the Data Decay runtime events.
NOTE: These action sets are disabled by default, so you must enable them. Do not use quotes when
you query for the action sets.
1 Navigate to Site Map > Administration - Runtime Events > Events, and query for Action Set
Name=*Decay*.
2 For the events with Action Set Name=UCM Account Decay New Record OR UCM Account Decay
Update Record, change the Conditional Expression value to:
GetProfileAttr(UCMDecayFieldUpdated:Account)=Y.
3 For the events with Action Set Name=UCM Contact Decay Record OR UCM Contact Decay
Update Record, change the Conditional Expression value to:
GetProfileAttr(UCMDecayFieldUpdated:Contact)=Y.
278
Configuring NetChart Server
Chart server needs to be installed from any release location with default settingsit is usually in
Server_Ancillary\Visual_Mining_Netcharts_Server.
Use the following procedure to configure NetChart Server 4.6 Siebel Edition.
Use the following procedure to configure NetChart Server.
To configure NetChart Server 4.6 Siebel Edition
1 Create a folder called "Siebel.chart" under the C:\Program Files\Visual Mining\NetCharts Server
4.6 Siebel Edition\Server\root\projects directory. Note that there needs to be a dot between
Siebel and chart.
2 Copy over the Siebel.cdx file into the directory created in Step 1.
3 In ucm.cfg used by the Siebel Developer Web Client, under the specific datasource that you use
to connect to DB, add the following lines:.
ChartServer = localhost:8001
ChartImageFormat = png
Localhost is the name of the machine that is running chart server and 8001 is the port number
of chart server.
4 Navigate to Administration - Server Configuration > Profile Configuration, query for Alias as
ServerDataSrc, and change the DSChartServer and DSChartImageFormat parameters.
5 Start NetCharts Server 4.6 Siebel Edition from Control Panel > Services.
6 In Windows Explorer, navigate to your installation directory for Siebel Charts (such as
D:\Program Files\Visual Mining\NetCharts Server 4.6 Siebel Edition\Server\root\projects).
7 Create a new subdirectory called Siebel.chart.
8 Within the new Siebel.chart subdirectory, create a new file, using Windows Notepad, and type
the following three characters in uppercase but without a paragraph return:
CDL
9 Save the file as Siebel.cdx.
10 Make sure that the DefaultChartFont parameter in your configuration file and the Application
Default Chart parameter for your Application Object Manager component are set to a font that
is available on your machine.
Configuring Survivorship to Use Haley Knowledgebase
Use the following procedure to configure survivorship to use Haley for rules evaluation.
To configure survivorship engine to use Haley for rules evaluation
1 Navigate to Administration - Universal Customer Master > Survivorship Rules.
2 Configure the Comparison Rule to "External", select "Business Rule Service" for "Business
Service Name", "RunRules" for "Business Service Method", and then select the individual "Rule
Module Name" for each testing purpose.
Use the following procedure to test task-based UI for merge.
Activating Tasks for the Task-Based UI
Use the following procedure to activate tasks to test the task-based UI for merge.
To activate tasks to test the task- based UI for merge
1 Navigate to Administration- Business Process > Task Deployment >Active Tasks.
2 In the Published Tasks applet, query for 'UCM*'.
3 Activate all four of the UCM Merge Tasks returned: UCM Merge Account Task; UCM Merge Contact
Task; UCM Merge Account Request Task; UCM Merge Contact Request Task.
Enabling Data Quality in SOAP Workflows
Use the following procedure to enable Data Quality in SOAP workflows.
1 Within Siebel Tools, navigate to Workflow Process, and query for the UCM Organization Customer
Profile Integration SOAP Process.
2 Select the workflow and then select Revise from the Workflow/Task Editor toolbar.
3 Set the workflow properties as follows:
Turn On CDM Cleans = true
Turn On CDM Exact Match = true
Turn On CDM Match = true
Turn On Survivorship = true
4 Navigate to the Workflow list view and select Publish/Activate from the Workflow/Task Editor
toolbar.
5 Repeat Step 1 through Step 4 for the UCM Person Customer Profile Integration SOAP Process.
Configuring Data Quality
1 Install IIR 2.8.07. using the instructions provided in the IIR Installation guide (
IS_2807_IIR_02_Installation.pdf) provided with the installer for completing this activity. There
is a single installer for both ISS and ASM, so make sure that you have the license for both.
280
2 Apply the hot fixes on top of the base installer. After the patch installation, check the IIR Version.
It should be on Patch level 141 or higher.
You can verify using the command "version" command for Windows. For other platforms, use
$SABIN/cevers.
Example: C:\InformaticaIR\bin>version
SSA-NAME3 v2.8.07 (FixL106)
SSA-NAME3 Extensions v2.8.07 (FixL106)
Data Clustering Engine v2.8.07 (FixL106)
Informatica Identity Resolution v2.8.07 (FixL106 + FixL113 + FixL114 + FixL120 +
FixL123 + FixL124 + FixL125 + FixL126 + FixL127 + FixL134 + FixL136 + FixL140 +
FixL141)
3 Place the configuration files required for both matching and cleansing in the SDQConnector
folders on Siebel Server.
ssadq_cfg.xml
ssadq_cfgasm.xml
4 Make sure that the country files and the key files exist in the location where ASM is installed.
If any one of the country files is missing, ASM will not perform cleansing for that country.
The location of these files will be: <drive>\InformaticaIR\ssaas\ad\ad\db.
NOTE: If AD5 is used, the location of the country database files and key file would be
<drive>\InformaticaIR\ssaas\ad5\ad\db.
Configuring ASM for Data Cleansing
Use the following procedure to configure ASM for data cleansing.
To configure ASM
1 Navigate to Administration - Server Configuration > Enterprise Explorer.
2 In the Explorer view, navigate to Component Definitions > Data Quality Manager > Parameters.
3 Within the Parameters list applet, query to verify the state of the following parameters.
Data Cleansing Enable Flag: True
Data Cleansing Type: ASM
4 Navigate to Administration - Server Configuration > Enterprise Explorer.
5 In the Explorer view, navigate to Component Definitions > Application Object Manager > Call
Center Object Manager (ENU) > Parameters.
NOTE: You can replace the Call Center Object Manager with another Object Manager, depending
upon the application that you are running.
6 Within the Parameters list applet, query to verify the state of following parameters:
Data Cleansing Enable Flag: True
Data Cleansing Type: ASM
Use the following procedure to set client-level settings.
To set client- level settings
1 Use any text editor to open uagent.cfg for the Siebel Call Center application, and ucm.cfg for
UCM located in the siebsrver/BIN/<LANG> directory.
2 Within the cfg file, change the Enable parameter to TRUE
[DataCleansing]
Enable = TRUE
Type = ASM
3 Save the file and then launch the Call Center application
4 Navigate to Administration - Data Quality > Data Quality Settings, and verify that Enable
DataCleansing is set to Yes.
5 Navigate to User Preferences > Data Quality, and verify that Enable DataCleansing is set to Yes.
If the entries are blank, do not change anything.
6 Navigate to <Navigation> and verify if a vendor named ASM with the DLL name ssadqasm exists.
If this field does not exist, then create it, using the information in Field Mappings for ASM.
Field Mappings for ASM
Make sure that the following vendor mappings are set for ASM.
NOTE: The mappings are imported as part of seed data import.
Account Business Component
Contact Business Component
Business Component Field Mapped Field
Name Account.Name
First Name Contact.First Name
Last Name Contact.Last Name
Middle Name Contact.Middle Name
282
List Mgmt Prospective Contact Business Component
CUT Address Business Component
Personal Address Business Component
First Name List Mgmt Prospective Contact.First Name
Job Title List Mgmt Prospective Contact.Job Title
Last Name List Mgmt Prospective Contact.Last Name
Middle Name List Mgmt Prospective Contact.Middle Name
City Business Address.City
Country Business Address.Country
Postal Code Business Address.Postal Code
State Business Address.State
Street Address Business Address.Street Address
Street Address 2 Business Address.Street Address 2
City Business Address.City
Country Business Address.Country
Postal Code Business Address.Postal Code
State Business Address.State
Street Address Business Address.Street Address
Street Address 2 Business Address.Street Address 2
Vendor Parameter
NOTE: The ASM High Deliverability Return Code parameter is optional and applies only if the value
for the DQ Cleanse High Deliverable Address parameter is set to Yes. Please set the values based on
the requirements.
The ssadq_cfgasm.xml file mentioned above in Vendor Parameter needs to be placed in the SDQ
Connector folder where the Siebel application is installed.
<?xml ver si on=" 1. 0" encodi ng=" UTF- 8" ?>
<Dat a>
<Par amet er >
<i ss_host >Host Name</ i ss_host >
</ Par amet er >
<Par amet er >
<i ss_por t >1666</ i ss_por t >
</ Par amet er >
<Par amet er >
<dat acl eanse_mappi ng>
<mappi ng>
<f i el d>BC Fi el d</ f i el d>
<ssaf i el d>ASM Fi el d</ ssaf i el d>
<st d_oper at i on>Oper at i on</ st d_oper at i on>
Name Value
Account DataCleanse Record Type Account
Contact DataCleanse Record Type Contact
List Mgmt Prospective Contact DataCleanse Record Type Prospect
Personal Address DataCleanse Record Type Business Address
CUT Address DataCleanse Record Type Business Address
DQ Send Empty Field To Third Party Vendor Yes
DQ Cleanse High Deliverable Address No
Parameter 1 "global", "iss-config-file",
"ssadq_cfgasm.xml"
ASM Country Database Return Code 16,17,18,32,33
ASM High Deliverability Return Code 0,1,2
284
</ mappi ng>
</ dat acl eanse_mappi ng>
</ par amet er >
</ dat a>
The <field> tag mentioned above represents Siebel Fields. <ssafield> represents fields used by ASM.
The fields used by ASM can only be the ones from the following table:
Data_Types and Standardization_Operations supported by the connector are:
Data_Type Meaning
Organization Organization Name
Department Department Name
Nobility (e.g. Lord)
Title (e.g. Mr, Dr)
FName
MName
LName
Function (e.g. Manager)
Building
SubBuilding
HouseNumber
Street1
Street2
POBox
DepLocality (e.g. URB, Colonia)
Locality (e.g. County)
Province (e.g. State)
Zip Zip / Postal Code
Country
Std_Op Meaning
Upper Convert text to upper case
Lower Convert text to lower case
Camel Convert text to camel case (first letter is upper-cased, remainder are lower-cased)
The connector is not able to cleanse any other field types. Money, Date and other types of data will
remain unchanged if they are passed to the connector.
The Country database used for ASM can be obtained from Technical Support. See the Siebel Data
Quality Administration Guide for information about the sample XML file.
Additional Seed Data Changes for ASM
1 If you are using ASM as the third-party vendor for data cleansing, then add UNITED STATES in
the COUNTRY List of Values using the following steps:
a Navigate to Site Map > Administration - Data > LOV Explorer.
b Query for List of Values - Type: "COUNTRY".
c In the LOV Explorer panel, click on the + sign to expand the node and navigate to the values for
COUNTRY.
d Add a new entry for 'UNITED STATES'.
2 Add 'DQ Cleanse High Delivery Address' in ASM - Vendor Parameter.
The "DQ Cleanse High Delivery Address" vendor parameter is optional. If you want to revert back
to the old address and do not want to cleanse if deliverability is low, set the parameter to "Yes".
By default, the value is "No". This feature may only be required if the Country Database files
provided by Informatica are not the updated ones.
Additional Seed Data Changes for ISS
1 Change DLL Name for ISS as follows:
a Navigate to Site Map > Administration - Data Quality > Third Party Administration.
b In the Vendor applet, select ISS, and change the DLL Name value to ssadqsea.
2 If you are using UCM Batch Process and ISS as the third-party data quality vendor, you need to
change the BC field mappings for the Contact - DeDuplication business component:
a Navigate to Site Map > Administration - Data Quality > Third Party Administration
b In the Vendor applet, select ISS.
c In BC Vendor Field Mapping, select Contact - Deduplication.
d In the Field Mappings applet, make the following changes:
Change the name of the Primary Street Address field to Primary Personal Street Address.
Change the name of the Primary City field to Primary Personal City
Change the name of the Primary State field to Primary Personal State.
Change the name of the Primary Postal Code field to Primary Personal Postal Code.
Change the name of the Primary Country field to Primary Personal Country.
286
Configuring ISS for Deduplication
The following sections contain information about how to configure ISS for deduplication.
Configuring the Siebel Application for the ISS Synchronizer Process
You must perform the following procedure if you want to use the DQ-ISS synchronizer process to
bypass XML Sync Server to insert records directly into the NSA table.
To configure the DQ- I SS Synchronizer Process
1 Navigate to Site Map > Administration - Data Quality > Data Quality Settings.
2 Add a new entry called Enable DQ Sync, and set the value for this property to Yes.
3 Use the following steps to activate the DQ Sync action sets:
a Navigate to Site Map > Administration - Runtime Events > Action Sets.
b Query for the DQ Sync action sets, and click on the Active field to activate them.
c Click the Menu button on the Action Sets applet, and select Reload Runtime Events to reload the
runtime events.
If you customize the SDF file, you must make sure that the value in the Record Length user property
matches the value for the Total Field Length user property in the new SDF file. For more information,
see Data Quality Guide for Oracle Customer Hub. To access this guide, within My Oracle Support,
navigate to the Knowledge tab and search for Article ID 1282393.1.
Configuring the EBC Table (for Data Sync)
Use the following procedure to configure the data source definition required to synchronize data
between the Siebel application and IIR.
To configure the data source definition
1 Navigate to Administration - Server Configuration > Enterprises > Profile Configuration.
2 Copy an existing InfraDatasources named subsystem type.
3 Change the Profile and Alias properties to the Data Source name configured in Siebel Tools
(ISSDataSrc).
4 Update the profile parameters to correspond to the external RDBMS:
DSConnectString = data source connect string
For the Microsoft SQL Server or the IBM DB2 databases, create an ODBC or equivalent
connection and input the name of this in the parameter.
For an Oracle RDBMS, this value should specify the TNS name associated with the
database and not an ODBC or other entry.
DSSQLStyle = database SQL type (Click Advanced to see this parameter.)
DSDLLName = DLL Name corresponding to the SQL type
DSTableOwner = data source table owner (Click Advanced to see this parameter.)
DSUsername = default user name used for connections
DSPassword = default password used for connections
Configuring Object Managers for ISS Data Source (for Data Sync)
Use the following procedure to configure Object Managers for ISS Data Source.
To configure Obj ect Managers for I SS Data Source
1 Navigate to Administration - Server Configuration > Enterprises > Component Definitions.
2 Query for the components used with UCM (such as UCM, DQ, EAI, and Workflow components).
3 Select a component, and then select Start Reconfiguration from the main menu.
4 In the lower applet, query for the OM - Named Data Source parameter.
NOTE: The value for this parameter is similiar to ServerDataSrc,GatewayDataSrc.
5 Add a comma after the last data source, and add the ISS data source created in the To configure
the data source definition procedure. The default name is ISSDataSrc.
6 Save the record and select Commit Reconfiguration from the main menu.
7 Repeat Step 3 through Step 7 for all required Object Managers.
8 Click Synchronize to save the changes into the Gateway configuration file.
9 Bounce the Gateway Server and the Siebel Server.\
Configuring Deduplication for Multiple Addresses
Use the following procedure if you want to use matching with multiple addresses instead of with the
primary address.
To configure deduplication for multiple addresses
2 Add a new entry called Enable DQ Multiple Addresses and set the value for this property to Yes.
3 Add a new entry called Account Match Against and set the value for this property to All Address.
4 Add a new entry called Contact Match Against and set the value for this property to All Address.
For more information about configuring multiple addresses, see the Configuring Deduplication
Against Multiple Addresses section in the Data Quality Guide for Oracle Customer Hub (UCM) To
access this guide, within My Oracle Support, navigate to the Knowledge tab and search for Article ID
1282393.1.
288
Configuring Support for Multiple Languages
Use the following procedure if you want to use matching with multiple languages using different
population files.
To configure multiple- language support
2 Add a new entry called Enable DQ Multiple Languages and set the value for this property to Yes.
3 Navigate to Site Map > Administration - Data Quality > Third Party Administration, select ISS in
the Vendor applet, click on Vendor Parameter in the child applet, and do the following:
a Add a new entry called Append Account Record Type Field 1 and set the value for this property
to Primary Account Country.
b Add a new entry called Append Contact Record Type Field 1 and set the value for this property
to Primary Personal Country.
c Add a new entry called Batch Append Account Record Type Field 1 and set the value for this
property to Primary Account Country.
d Add a new entry called Batch Append Contact Record Type Field 1 and set the value for this
property to Primary Personal Country.
For more information about configuring support for multiple languages, see the Configuring Multiple
Language Support section in the Data Quality Guide for Oracle Customer Hub (UCM). To access this
guide, within My Oracle Support, navigate to the Knowledge tab and search for Article ID 1282393.1.
Configuring List Import
These are the new system preferences used in List Import:
Enable Validation - [Optional step in the List Import Process] If this System Preference is turned on,
the validation process will automatically be run after records are imported into UCM (SDH tables).
The validation process will check if any required fields specify in the Import Mapping are missing in
the imported records. Any records that fail validation will have their 'UCM Type Code' changed from
'Batch' to 'Incomplete' and the validation status will be inserted in the 'Error Message' field.
Enable Launch BDM - [Optional step in the List Import Process] If this System Preference is turn on,
the UCM Batch Process will automatically be run after records are imported into staging tables (SDH
tables). This is an existing UCM process to move records in staging to base tables. Users can kick
off the UCM Batch Process as a server task outside of List Import.
Name Value
UCM Import: Enable Validation True/False
UCM Import: Enable Launch BDM True/False
Configuring Import Field Mapping
When creating the Import Mapping, the list of fields displayed in the popup dialog for user selection
is configured in the Business Component User Prop for Accout/Contact SDH Business Component.
sers can include additional fields that they want to support in these Business Component User
Properties.
The format for these Business Component User Properties is as follows:
For example, in "UCM Account Source Data and History, there are the following Business Component
user properties:
Configuring Additional Child Objects for Import
Assume that users already configure additional SDH child objects, and they want to import these
child objects along with the account/contact SDH parent record. These are the additional
configuration steps for List Import:
1 In the child SDH Business Component, add a business component user prop: "Parent SDH Id Field
Name", the value is the field that contains its parent SDH ID.
2 In the parent SDH Business Component, add the additional field mapping for the child object (see
the example of field mapping configuration above).
3 In the "UCM Account Import" or "UCM Contact Import" Business Object, add the new child SDH
Business Component and the corresponding link to the parent SDH Business Component.
4 In the UCM File Manager Service" Business Service, add a new Business Service user property
for the new child SDH buscomp. For example:
Account Import Staging Child Buscomp 1 => UCM Account Address Source Data and History
Account Import Staging Child Buscomp 2 => UCM Contact Source Data and History
Installing Data Governance Management
The following section contains information about how to install Data Governance Management
(DGM).
Name Value
Map:[Object].[Field] [SDH buscomp Name].[Buscomp Field Name]
Name Value
Map:Account.Name UCM Account Source Data and History.Name
Map:Address.City UCM Account Address Source Data and History.City
Map:Contact.Job Title UCM Contact Source Data and History.Job Title
290
Overview of DGM and Prerequisites
Data Governance Management (DGM) tool is software built on Java technology, and Oracle ADF
framework are introduced. This section describes how to install DGM.
OS System: DGM can only be run on the Windows platform.
DGM is a Java-based application.
Siebel UCM application: In this release of DGM, Siebel UCM is the only supported master hub.
For information about how to install and configurethe Siebel application, refer to the Siebel UCM
DGM web service document.
DGM source code: The installer will extract DGM source code and install package to a directory.
Within this section, this directory will be referred to as <dgm_home>.
Deployment of DGM application is a process of customizing the DGM system and then transferring it
to the application server. You must preinstall and configure several software programs. Here is the
guideline for the whole installation process.
Application Server Installation and Configuration: The Java application will run inside Java
application server. In this section, Weblogic is the target application server.
ADF runtime Installation and Configuration: The DGM application uses functionality provided by
the Oracle ADF framework, so the target Weblogic domain should have the ADF runtime
extension installed.
DGM Configuration and Deployment: External environments parameters should be set correctly
before DGM is deployed. After that, DGM can be deployed to Weblogic server.
Required Software
The following table describes the required software for DGM.
Installing JDeveloper
Use the following procedure to install JDeveloper.
To install J Developer
1 Click Next within the Welcome screen to begin the installation.
2 Accept the default value as the middleware home directory.
NOTE: Within this section, <mw_install_dir> will be used to represent the Middleware Home
directory.
Software Name Version Description
JDK 1.6 Providing runtime for java application.
Weblogic 10gR3 Java application server.
ADF 11.1.1.54.7 Oracle framework for java application.
ANT 1.6 A Java-based build tool.
3 Select Complete Install.
The Complete Installation will install Oracle JDeveloper Studio, the ADF Runtime, and WebLogic
Server.
4 Confirm the product intstallation directories, and click Next to continue with the installation.
5 Select the Start Menu folder where you want to place your shortcuts. This step applies for the
Windows platform only.
6 Display the installation summary info, and start the installation.
7 Select Run Quickstart to open the Quickstart window once the installation process has ended.
Quickstart enables you to easily launch installed components and access online documentation.
8 Click Done to complete the installation.
Creating the Weblogic Domain
A weblogic domain should be created to accept the ADF-based DGM application.
Use the following procedure to create the Weblogic domain.
To create the Weblogic domain
1 Choose Configure Domains for Oracle ADF from the Quickstart window to display the Oracle
Weblogic Configuration Wizard.
2 Select Create a New WebLogic Domain and click Next.
3 Select Generate a domain configured automatically to support the following products, select
Oracle JRF - 11.1.1.0 [jdeveloper] and click Next.
The option Base WebLogic Server Domain - 10.3.1.0 [wlserver_10.3]* is already selected.
4 Enter the name and location for the domain if the default values are not correct, and then click
Next.
5 Enter the user name and password and click Next.
6 Select Production Mode in Weblogic Domain Startup Mode window, and click Next.
7 Click Next to ignore optional configuration.
8 Review the domain configuration, and click Create.
9 Click Done when the domain has been created.
10 Select User Projects < (domainName) > Start > All Programs > Oracle Fusion Middleware
11.1.1.1.0 > User Projects > base_domain > Start Admin Server for Weblogic Server Domain.
11 When the DOS window prompts for the username and password, enter userName and passWord
if asked to do so.
When the window displays message like "Server started in RUNNING mode", the Weblogic server
has started up.
292
Installing DGM
Use the following procedure to install DGM.
To install DGM
1 Navigate to Disk1\install, and click setup.exe, and click Next.
2 Specify the home where DGM applications and source code will be installed, and click Next.
3 Choose Copy Application to copy the application and source code to home directory without
deployment otherwise, the DGM application will be deployed after file copy. If you choose Copy
Application, go to Summary. Otherwise, go to the next step.
4 Browse to specify the JDK path. You can also use JDK installed with Oracle Middleware, which
can be found within the Oracle/Middleware/JDK_1.x.xx folder.
5 Browse to specify the ant path. In a default Oracle Middleware installation, the ant path is found
in the Oracle/Middleware/jdeveloper/ant folder.
6 Browse to specify the Weblogic 10gR3 installation path. You must select the root directory of
WLserver installation.
7 Specify the Weblogic configurations according to your environment.
8 Specify the URL for Siebel server login, such as http://serverName:webPort/eai_enu/
start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute.
9 Specify the URL for Hierarchy Management, such as http://serverName:webPort/eai_enu/
start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute.
10 Specify the endpoint information of the DGM Web service according to your environment:
For example, specify http://sdc60005qe:16662/eai_enu
start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&UserName=SADMIN&a
mp;Password=MSSQL&
NOTE: The endpoint information will be kept in xml files, so escape '&' to '&'.
11 Click Install to start the install process.
12 Click Exit to finish the installation.
Entry Name Description
host Weblogic server address
port weblogic server listening port
username
password weblogic server credential
target.server The default value is AdminServer
Manually Installing or Redeploying DGM
The src directory contains the source code for DGM application, and the build directory contains the
script and configuration files you can use to manually deploy the DGM application.
The install.cmd is the script for DGM installation. Edit the file, change the weblogic_home, jdk_home,
ant_home according to your environment.
DGM configurations are kept in <dgm_home>/build/deploy.properties. The configuration entries in
this file are list in the following table.
Entry Name Default Value Description
dgm_web_service_end_point N/A This configuration MUST
be changed to the
endpoints of DGM web
service
siebel_login_url N/A This configuration MUST
be changed to the url
used for login into Siebel.
govern_hier_url N/A The url of hierarchy
explorer
batch_preview_page_size 23 Specify how many records
in a page when
previewing imported
batch.
paginate_page_size
paginate_cache_size
23 This configuration will
specify how many records
will be displayed in a
page.
#Note: For now, please
keep the
paginate_page_size and
paginate_cache_size
having same setting.
batch_job_size 1000 When importing batch
file, this configuration will
specify how many records
will be sent in a single
request.
294
After editing the install.cmd and deploy.properties according to your environment, open a dos
window and run install.cmd to deploy the application.
Accessing DGM
Open browser, and access the following URL to visit DGM:
cleanse_thresh_value
cleanse_thresh_color
0.33,0.66,1.0
#d62800,#ffcf21,#84ae31
This configuration will
specify the color for the
healthy status of hub and
source systems.
cleanse_thresh_value are
the threshhold values,
and cleanse_thresh_color
are colors used for
representing different
status. For example:
cleanse_thresh_value=0.
33,0.66,1.0
cleanse_thresh_color=#d
62800,#ffcf21,#84ae31
When the healthy is below
33%(0.33), the node of
corresponding system will
be marked with color of
#d62800; if healthy is
between 33% and 66%,
color of #ffcf21 is used;
when above 66%,
#84ae31 will be used.
HubAccount
SrcAccount
HubContact
SrcContact
[name, location, mainPhoneNumber]
[name, loc, mainPhoneNumber]
[firstName, lastName]
[firstName, lastName]
The default fields
combination used to
query completeness info.
min_date_format
min_date_value
MM/dd/yyyy HH:mm:ss
09/13/1990 00:00:00
When choosing the query
criteria of "From"
calendar selector, the
oldest time users can
specify.
collectionsClassPath
loggingClassPath
com/oracle/mdm/view/collections.xml
logging.properties
These are the internally-
used configurations. Do
not modify them.
Entry Name Default Value Description
http://<ServerAddress>:<ServerPort>/dgm/
For example, navigate to http://130.35.79.111:7001/dgm/
NOTE: Java script and Active Control should be permitted to display the page.
Use the instructions in this topic to implement ACR 476, which provides the new product Siebel Smart
Answer Connector.
For more information about the enhancements provided by ACR 476 for version 8.1.1.1 and later,
see Siebel Smart Answer Connector Guide. This new guide is available on the Siebel 8.1 Bookshelf
on OTN at http://www.oracle.com/technology/documentation/siebel.html.
Updating Repository Objects for Siebel Smart Answer Connector
To deploy Siebel Smart Answer Connector, you must update repository objects in Siebel Tools.
To update repository obj ect for Siebel Smart Answer Connector
1 Extract all archive files (*.sif) from SIEBEL_TOOLS_ROOT/REPPATCH/ACR476.zip into a
temporary location.
2 Log in to Siebel Tools with administrator privileges.
Smart Answer 8.x
Smart Answer
Banter eService
Service (SSV)
Symbolic Strings
eCatalog Admin
Email Response
NOTE: 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.
4 Import the SIF files you extracted in Step 1 in the order shown below:
01_sma_project.sif
02_sma_classes.sif
296
03_sma_dll.sif
04_sma_bussvc.sif
05_sma_io.sif
06_sma_ss.sif
07_sma_applets.sif
08_sma_sct.sif
09_sma_view.sif
10_emr_bussvc.sif
NOTE: SIF files are written in XML format. Their structure is a hierarchy of the objects archived,
listing all of their properties and including any associated scripts: Repository, then Project, then
Object, and then Child Objects.
6 Start the Siebel Server (or servers) using the newly compiled SRF.
For more information about starting Siebel Servers, see Siebel System Administration Guide.
7 Update the file SAConfig.xml by performing the following:
a Navigate to the SIEBSRVR_ROOT\smartanswer directory, and then open the SAConfig.xml file
with a text editor.
b Replace the value for NLPAdapterDLLName with the correct location and filename.
c Verify the value for the FacadeName property. The value depends on the third-party product you
are using with Siebel Smart Answer.
8 Create a new smartanswer directory and subdirectories under the Siebel File System.
a Make sure the File System location is correct, accessible, and writable.
b In the smartanswer directory, create two subdirectories: import and export.
For example, if you map your File System to f s, then the resulting directory structure is
similar to that shown below.
f s
smar t answer
expor t
i mpor t
Adding Seed Data for Siebel Smart Answer Connector
To deploy Siebel Smart Answer Connector, you must add seed data for Siebel Smart Answer
Connector. Seed data is required for product operation.
To add seed data for Siebel Smart Answer Connector
1 Add a new LOV (List of Values) by doing the following:
a Navigate to the Administration - Data screen, and then the List of Values view.
b Click New, and then add the following values:
Type = SEARCH_SMART_ANSWER
Display Value = Smart Answer
Language = English American
2 Add a new inbound Web service by doing the following:
a Navigate to the Administration Web Services screen, then the Inbound Web Services view.
Namespace = http://siebel.com/asi/
Name = SmartAnswerService
Status = Active
Comment = Smart Answer Service
3 Add a service port to the newly created Inbound Web Service.
a Navigate to the Administration Web Services screen, then Inbound Web Services, and then the
Service Ports view.
Name = Default
Type = Business Service
Business Service/Business Process name = Smart Answer External Business Service
Transport = HTTP
Address = http://130.35.27.238/eai_enu/
start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&UserName=
USERNAME&Password=PASSWORD
where:
USERNAME is a valid Siebel user name
PASSWORD is the corresponding password.
Binding = SOAP_RPC_LITERAL
4 Add operations for the newly created service port.
a Navigate to the Administration Web Services screen, Inbound Web Services, Service Ports, and
then the Operations view.
298
b Click New to create new operations using the values shown in the following table.
Setting Up Siebel Email Response for Use with Siebel Smart Answer
Connector
To make the Siebel Smart Answer Connector functionality available for use in Siebel EmailResponse,
you must set up the Siebel Email Response user interface.
To set up Siebel Email Response for use with Siebel Smart Answer Connector
1 Verify the following DLLs are available in the SIEBSRVR_ROOT\bin directory:
swcommfr.dll
sscommsv.dll
sscmclnt.dll
sscacabc.dll
swcacafr.dll
2 Extract all archive files (*.sif) from SIEBEL_TOOLS_ROOT\REPPATCH\EMRUI_New.zip into a
temporary location.
3 Log in to Siebel Tools with administrator privileges.
Mail Agent
Email Response
5 Import the SIF files you extracted in Step 2 on page 298 in the order shown below:
EMR_UI_Applets.sif
EMR_UI_BC.sif
EMR_UI_BO.sif
EMR_UI_BS.sif
EMR_UI_Class.sif
EMR_UI_Screen.sif
EMR_UI_View.sif
Name Method Display Name Authentication Type
Import Import None
Export Export None
Feedback Feedback None
Lookup Lookup None
RefreshKB Refresh None
EMR_UI_Webtemplate.sif
indicating which object or project is to be locked. In such a case, lock the project or object, and
7 Start the Siebel Server (or servers) using the newly compiled SRF.
For more information about starting Siebel Servers, see Siebel System Administration Guide.
8 Import the following workflows:
Email Response - Analyze Message.xml
Email Response - Client Send Email.xml
Email Response - Create Activity.xml
Email Response - Process Message.xml
Email Response - Response Workflow.xml
Email Response - Send Auto Response.xml
Email Response - Set Parent Activity Status.xml
For information about working with workflows, see Siebel Business Process Framework: Workflow
Guide.
9 Activate the workflows you imported in Step 8 on page 299.
10 Add seed data by doing the following:
a Launch the Siebel Developer Web Client with the /editseeddata command-line option.
For more information about launching this client type, see the Siebel Installation Guide for
the operating system you are using.
b Navigate to the Administration - Application screen, and then Views.
c Click New to create a new view and add the following values:
View Name = Communication Detail View
Description = Drill down View
Default Local Access = Yes
Responsibilities = Siebel Administrator, Call Center Administrator, Email Response Agent,
Email Response Manager, and Call Center Manager
The following sections contain information about how to work with the seed data provided with ACR
480.
300
Views and Responsibilities
The following procedure details how to add the views and responsiblities for ACR 480.
To add views/ responsibilities
1 Connect to the Siebel application with /editseeddata switch.
2 Navigate to Site Map > Administration Application > Views, and add the views and
responsibilities listed in the following table:
View Responsibility
CS CG My High Level Planning List View Siebel Administrator, CG Key Account Manager
CS CG My Team's High Level Planning List
View
Siebel Administrator, CG Key Account Manager
CS CG All High Level Planning List View Siebel Administrator, CG Key Account Manager
CS CG All Across Organizations High Level
Planning List View
Siebel Administrator
CPG Plan High Level Planning View Siebel Administrator, CG Key Account Manager
CPG Account High Level Planning View Siebel Administrator, CG Key Account Manager
CPG Promotion List View Siebel Administrator, CG Key Account Manager
CPG Promotion Literature List View Siebel Administrator, CG Key Account Manager
CPG Promotion Product Performance View Siebel Administrator, CG Key Account Manager
CS CG All Promotion List View Siebel Administrator, CG Key Account Manager
CS CG Corporate Promotion Category List
Admin View - SIS
CS CG Promotion Literature List View Siebel Administrator, CG Key Account Manager
CS CG Corporate Promotion Attachments
View
SIA CS Target Account View Siebel Administrator, CG Key Account Manager
SIS CS Corporate Promotions Target View Siebel Administrator, CG Key Account Manager
CS CG Deal Payment Approval View Siebel Administrator, CG Key Account Manager,
Super User - SIS 7.7, Super User - SIS
SIA CS ADL Authorized Category Product
View
SIA CS ADL Authorized Product View Siebel Administrator, CG Key Account Manager
CG Account Merchandising Location Product
View
CS Fund Transfer Admin View Siebel Administrator, CG Key Account Manager
Lists of Values
The following section details how to add the LOVs provided in ACR 480.
To add LOVs
1 Connect to the Siebel application.
2 Navigate to Site Map > Administration Data > List of Values Explorer (for List of Values Type)
and List of Values (for LOV type values), and create or modify the following LOV Type/LOVs with
Translate = Y for all the values:
CS Plan Account Promotion Audit Trail View Siebel Administrator, CG Key Account Manager
CS Plan Audit Trail View Siebel Administrator, CG Key Account Manager
CS Visit Parent Account Promotions View Siebel Administrator, CG Key Account Manager
CS Claim My Claims View Siebel Administrator, CG Key Account Manager
CS Claim My Team's Claims View Siebel Administrator, CG Key Account Manager
CS Claim All Claims View Siebel Administrator, CG Key Account Manager
CS Claim All Across Orgs Claims View Siebel Administrator, CG Key Account Manager
CS Claim Attachments View Siebel Administrator, CG Key Account Manager
CS Claim Resolution View Siebel Administrator, CG Key Account Manager
New or
Needs
Modification?
LOV Type
Code Display Value
Language-
Independent Code Comments
New SVP Source Baseline PY
Currency
Baseline PY Currency Order = 7
New SVP Source Baseline PY
Qty
Baseline PY Cases Order = 8
New SVP Source Baseline
Target
Currency
Baseline Target
Currency
Order = 9
New SVP Source Baseline
Target Qty
Baseline Target Cases Order = 10
Modify SVP Source Incremental
Qty
Baseline Incremental
Cases
Change Order =
11
Modify SVP Source Incremental
Currency
Baseline Incremental
Currency
Change Order =
12
View Responsibility
302
Modify SVP Source Consumed Qty Consumption
Consumed Cases
Change Order =
13
Modify SVP Source Shipped Qty Shipments Shipped
Cases
Change Order =
14
Modify SVP Source Target Basis
Currency
Target Basis Currency Change Order =
15
Modify SVP Source Target Basis
Qty
Target Basis Cases Change Order =
16
Modify SVP Source Target
Planning
Currency
Target Planning
Currency
Change Order =
17
Planning Qty
Target Planning Cases Change Order =
18
Currency
Target Baseline
Currency
Change Order =
19
Modify SVP Source Target Qty Target Baseline Cases Change Order =
20
New CAMP_EXEC_S
TATUS
In Progress In Progress Translate = Y
New DISPLAY_LOC Shelf Shelf Order = 1
New DISPLAY_LOC Off-Shelf Off-Shelf Order = 2
New DISPLAY_LOC Secondary Secondary Order = 3
New DISPLAY_LOC End-of-Isle End-of-Isle Order = 4
New DISPLAY_LOC Checkout Checkout Order = 5
New DISPLAY_LOC Multiple Multiple Order = 6
New DISPLAY_SIZE Small Small Order = 1
New DISPLAY_SIZE Medium Medium Order = 2
New DISPLAY_SIZE Large Large Order = 3
New DISPLAY_TYPE Literature Literature Order = 1
New DISPLAY_TYPE Merchandise Merchandise Order = 2
New DISPLAY_TYPE Sweepstakes Sweepstakes Order = 3
New DISPLAY_TYPE Audio Audio Order = 4
New DISPLAY_TYPE Multi-Media Multi-Media Order = 5
New DISPLAY_TYPE Promoter Promoter Order = 6
New or
Needs
Modification?
LOV Type
Code Display Value
Language-
New ADV_LOC Premium Premium Order = 1
New ADV_LOC Secondary Secondary Order = 2
New ADV_LOC Tertiary Tertiary Order = 3
New ADV_SIZE Postage Stamp Postage Stamp Order = 1
New ADV_SIZE Quarter Page Quarter Page Order = 2
New ADV_SIZE Half Page Half Page Order = 3
New ADV_SIZE Full Page Full Page Order = 4
New ADV_SIZE Not Applicable Not Applicable Order = 5
New ADV_TYPE Flyer Flyer Order = 1
New ADV_TYPE Newspaper Newspaper Order = 2
New ADV_TYPE TV TV Order = 3
New ADV_TYPE Radio Radio Order = 4
New ADV_TYPE Direct Mail Direct Mail Order = 5
New ADV_TYPE Internet Internet Order = 6
New PRICE_REDUCT
ION_SIZE
Reduction
Amount
Reduction Amount Order = 1
New PRICE_REDUCT
ION_SIZE
Reduction % Reduction % Order = 2
New PRICE_REDUCT
ION_SIZE
Reduced Price Reduced Price Order = 3
New PRICE_
REDUCTION_T
YPE
TPR TPR Order = 1
New PRICE_
REDUCTION_T
YPE
Special Pack Special Pack Order = 2
New PRICE_
REDUCTION_T
YPE
BOGO BOGO Order = 3
New PRICE_
REDUCTION_T
YPE
EDLP/EDLC EDLP/EDLC Order = 4
New PRICE_
REDUCTION_T
YPE
Coupon Coupon Order = 5
New or
Needs
Modification?
LOV Type
Code Display Value
Language-
304
New FD_SLOTFEE_P
AY_MTH
Bill Back Bill Back Order = 1
New FD_SLOTFEE_P
AY_MTH
Deduction Deduction Order = 2
New FD_SLOTFEE_P
AY_MTH
Check Check Order = 3
New OTHER_FD_SP
ND_PAY_MTH
New OTHER_FD_SP
ND_PAY_MTH
New OTHER_FD_SP
ND_PAY_MTH
Check Check Order = 3
New SH_VAR_SPEN
D_MTH
New SH_VAR_SPEN
D_MTH
New SH_VAR_SPEN
D_MTH
Off-Invoice Off-Invoice Order = 3
New TACTICS_TYPE Display & TPR
10%
Display & TPR 10%
15%
Display & TPR 15%
5%
Display & TPR 5%
New TACTICS_TYPE F&D F&D
New TACTICS_TYPE F&D 10% F&D 10%
New TACTICS_TYPE Feature & TPR
10%
Feature & TPR 10%
15%
Feature & TPR 15%
5%
Feature & TPR 5%
New or
Needs
Modification?
LOV Type
Code Display Value
Language-
3 Click the Clear Cache button.
State Model
Use the following procedure to add State Models.
To add State Models
2 Navigate to Site Map > Administration - Application > State Models.
3 Add the following new states for the CS Claim Status State Model: Closed, In Progress, Inactive,
Open (Default), Resolved.
4 Add the transactions described in the following tables for the CS Claim Status State Model:
5 Add new states for the State Models in the following table:
Modify PAYMENT_MET
HOD_CODE
Claim Claim Order = 23
Modify PAYMENT_TYPE
_CODE
Claim Claim
New? State Model Name Business Component Field
New CS Claim Status CS Claims Payment Status
Transition From Transition To
Resolved Closed
New or Needs
Modification? State Model Name Business Component Field
Modified CS CG Promo
Category Payment
Status
CS CG Promotion Category Deal
Payment
Payment Status
Modified CS Check Payment
Status
CPG Check Payment Payment Status
Modified CS Deduction
Payment Status
CPG Deduction Resolution -
Payment
Payment Status
New or
Needs
Modification?
LOV Type
Code Display Value
Language-
306
6 Add the new states for the State Models: Requested, Approved, and Rejected.
7 Add or modify the transactions for the State Models:
8 Add new states for the following State Model:
9 Add the following new states for the State Models: Requested (Default), Approved, and Rejected.
10 Add the transactions listed in the following table for the State Models:
Modified CS Promo Payment
Status
CPG Promo Deal Payment Payment Status
Modified CS Promoted Product
Payment Status
CG Promo Product Fund Payment Payment Status
New CS Claim Payment
Status
CS Claim Payments Payment Status
Pending Requested
Pending Cancelled
Requested Cancelled
Approved Cancelled
Approved Submitted
Rejected Pending
Rejected Requested
Rejected Cancelled
Submitted Paid
Submitted Cancelled
Paid Voided
New? State Model Name Business Component Field
New CS CG Deal Payment Status CS CG Deal Payment Approval Payment Status
Requested Approved
Requested Rejected
New or Needs
Modification? State Model Name Business Component Field
11 Log out of the Siebel application and bounce the Siebel Server.
Audit Trail
Use the following procedure to create new Audit Trails.
To create new Audit Trails
2 Navigate to Site Map > Administration - Audit Trail > and create new Audit Trails with the
information in the following tables:
3 Click the Update Audit Cache button.
Workflows
The following procedure details how to add the workflows that are associated with ACR 480.
To add the ACR 480 workflows
1 Connect to Siebel Tools and navigate to Object Explorer.
2 In Object Explorer, select Project, and lock the CPG Plan, CPG Corporate Promotion, and ADL
Enhancement projects.
3 Select Workflow Process in the Object Explorer, select Import Workflow Process from the right-
click menu in the list view pane, and import the following workflow xml files:
CG Apply Corporate Promotion Process (Project = CPG Corporate Promotion)
New?
Audit Trail Business
Component Base Table Update Delete Insert Assoc
New CPG Plan Account S_SRC Y Y Y Y
New? Field Table Name Column Name
New Account Promotion Status S_SRC STATUS_CD
New? Audit Trail Buscomp Base Table Update Delete Insert Assoc
New CPG Plan Account Promotion S_SRC Y Y Y Y
New? Field Table Name Column Name
New Account Promotion Status S_SRC STATUS_CD
308
CS CG Account Plan Update Process (Project = CPG Plan)
SIA CS ADL Service Workflow (Project = ADL Enhancement)
SIA CS Update Product Status (Project = ADL Enhancement)
4 Navigate to View > Toolbars, and make sure that the WF/Task Editor toolbar is checked.
5 Click the Publish/Activate button to deploy all of the workflows.
6 Log out of Siebel Tools.
8 Navigate to Site Map > Administration - Business Process > Workflow Deployment , and verify
that all the workflows show up in the Active Workflow Processes List at the bottom.
About Rules in the Personalization Screen
The following section contains information about Rules in the Administration > Personalization
screen.
Table 19 contains details about the SVPFilterYear profile variable, Table 20 contains information about
the SVP Current Year Filter rule set, and Table 21 contains information about the Current Filter rule.
Table 19. Values of SVPFilterYear
Value of SVPFilterYear Description
CurrentSVPYear Profile Variable value for Current Year
NextSVPYear Profile Variable value for Next Year
PriorSVPYear Profile Variable value for Prior Year
AllSVPYears Profile Variable value for All Years
Table 20. SVP Current Year Filter Rule Set
Rule Set
Name Active Start Date End Date Description
SVP Current Year Filter Y Select today's date SVP Current Year Filter
Table 21. Current Filter Rule
Rules
Name Rule Type Seq Active Start Date End Date Description
Current Filter Expression 1 Y Select today's date Filter for current year
Note the following information about working with rule sets:
You need to set different rule sets for different filters.
Make sure that the "SVPFilterYear" Profile Variable contains the proper values before you
associate these rules to the applet.
When setting rules and when associating t he rules with the applets, remember to use the "Reload
Personalization Rules" menu option.
Changing Visibility
The following procedure details how to change visibility for the Plan Team and Promotion Team
Business Components.
To change visibility for the Plan Team and Promotion Team Business Components
1 In Object Explorer, navigate to Business Component.
2 For the Plan Team Business Component, query for Name = CPG Plan Account , and lock the
project using the right-click menu.
3 For the Promotion Team Business Component, query for Name = CPG Plan Account Promotion,
and lock the object using the right-click menu.
4 In Object Explorer, navigate to the Business Component View Modes for each Business
Component.
5 Query for for Sales Rep in Business Component View Modes.
6 Change the value of the Visibility MVL from Account Position to Position.
7 Change the value of the Visibility MVF from Account Sales Rep to Sales
8 Compile the Business Components.
Changing the User Properties for the Plan Team and Promotion Team
Business Components
The following procedure details how to change the user properties for the Plan Team and Promotion
Team Business Components.
To change the user properties for the Plan Team and Promotion Team Business
Components
1 In Object Explorer, navigate to Business Component.
2 For the Plan Team Business Component, query for Name = CPG Plan Account, and lock the object
using the right-click menu.
3 For the Promotion Team Business Component, query for Name = CPG Plan Account Promotion,
and lock the object using the right-click menu.
4 In Object Explorer, navigate to Business Component User Properties for each Business
Component.
310
5 Change the value of Add Account Team from Y to N.
6 Compile both Business Components.
Activating and Disabling Views in the SIA CS ADL Screen
The following procedure details how to add activate two views and disable one view in the SIA CS
ADL screen.
To activate and disable views in the SI A CS ADL screen
1 In Object Explorer, navigate to Screen in the Object Explorer.
2 Query for SIA CS ADL Screen.
3 Navigate to Views, query for the SIA CS ADL Authorized Category Product View and SIA CS
ADL Authorized Product View views and activate them.
4 Query for the SIA CS Source of Supply Accounts Products View view and disable it.
5 Compile the screen.
For more information about Siebel Consumer Goods, see Siebel Consumer Goods Guide on the Siebel
Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.
CAUTION: You must have installed ACR 450 before you install ACR 488. For more information about
installing ACR 450, see Instructions for ACR 456 on page 102.
For more information about the Siebel Hospitality application, see Siebel Hospitality Guide on the
Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.
For instructions about how to implement ACR 494, within My Oracle Support, navigate to the
The following sections contain detailed information about the functionality provided by ACR 499, as
well as instructions for implementing the ACR.
NOTE: This ACR is for Siebel Industry Applications only.
CAUTION: You must have installed ACR 502 before you install ACR 499. For information about how
to install ACR 502, see Instructions for ACR 502 on page 364. For information about why installing
ACR 499 after you have installed ACR 502 is problematic, from within My Oracle Support, navigate
to the Knowledge tab, and search for Article ID 1295924.1.
The following section contains information about known issues with ACR 499, as well as any
OK Button Disabled
Category: Quotes and Orders
Subcategory: Asset-Based Ordering
Change Request: 12-2169YMX
When promotions are upgraded through the Bulk Request function, the OK button is not enabled.
Bulk Requests Remain in Processing Status
Category: Quotes and Orders
Subcategory: Asset-Based Ordering
Change Request: 12-216ABLP
When users try to add an excluded product with scope all/exclude, Bulk Requests remains in the
Processing status.
Installing ACR 499
1 Open tools.cfg from <Tools Install Directory>\Bin\Enu and verify the [Siebel] section.
312
2 Ensure that the SymStrPrefix entry has been set to SBL_
[Siebel]
..
.; SymStrPrefix parameter needs to be X_ for Siebel Customers.
SymStrPrefix = SBL_
..
3 Navigate to <Tools Installed Directory>\REPPATCH, and unzip the BulkRequest_ACR499.zip file.
ABO Bulk Request
ABO Bulk Request UI
Asset Management
Contact
ISS Product Loader
ISS Promotion Admin
List Mgmt (UI)
Order Entry
Product
Quote
Quote (UI)
Srvagree
Symbolic Strings
eAuto Simplified List Mgmt
Table ListManagement
Table BulkRequest
EIM BulkRequest
EIM ListManagement
5 Import the following SIF files in the order shown from the <Tools Installed
Directory>\REPPATCH\ BulkRequest_ACR499\REPOSITORY folder into Siebel Tools using the
Tools > Import from Archive option. Use the Merge option in Siebel Tools Import Wizard.
For example, if Symbolic String is not exposed in View > Option > Object Explorer >Siebel
Object, navigate to View > Option, click the Object Explorer tab and check Symbolic String.
Tables
Symbolic Strings
Class
Picklist
Business Service
Business Components
Links
Business Objects
Integration Objects
Applets
Views
Screens
If you receive the warning error message, lock the project displayed in the message.
6 After the SIF files have been imported, within Object Explorer, navigate to Table.
a Query for all of the changed objects and select them.
b Use the "Apply/DDL" button to apply the changes to the physical database.
c Choose the "Current Query" option from the Table drop-down list.
d Click Apply and then click OK.
7 Provide the following credentials when connecting to the database:
Database user= <Table Owner name>
Database user password= <Table Owner name>
ODBC data source= <DSN Name> (create the DSN if you get a TNS not resolved error
message)
Creating Integration Objects
The following section describes how to create the integration objects for ACR 499.
ABO Bulk Request Order
314
2 Click on Integration Object in the Object Explorer, and query for SIS OM Order.
3 Right-click on the SIS OM Order integration object, and choose Copy Record.
4 Name the new record ABO Bulk Request Order.
5 Within the ABO Build Request Order integration object, select the MACD Order Entry - Line Items
integration component.
6 Click on Integration Component User Prop in OBLE and add a record with the following values:
Name: SelectiveChildQuery
Value: Y
7 Right-click on ABO Bulk Request Quote and choose Compile Selected Objects to compile the
integration object.
ABO Bulk Request Quote
1 Log in to Siebel Tools.
2 Click on Integration Object in the Object Explorer, and query for SIS OM Quote.
3 Right-click on the SIS OM Quote integration object and choose Copy Record.
4 Name the new record ABO Bulk Request Quote.
5 Within the ABO Bulk Request Quote integration object, select the MACD Quote Item integration
component.
6 Click on Integration Component User Prop and add a record with the following values:
Name: SelectiveChildQuery
Value: Y
7 Right-click on ABO Bulk Request Quote and choose Compile Selected Objects to compile the
integration object.
Compiling the Projects
Use the following procedure to compile the projects.
To compile the proj ects
2 Compile all the locked projects using Tools > Compile Projects.
3 Save the srf file to <Siebel Server Install folder>\objects\ENU\siebel_sia.srf on the installed
Siebel server.
To import the seed data for ACR 499
navigate to the System DNS tab, and click Add.
d Enter the server name to connect to.
REPPATCH\BulkRequest_ACR499.
NOTE: Before executing the next step, make sure that the dataimp.exe file exists in the <Tools
Directory>\REPPATCH\BulkRequest_ACR499\SEED_DATA\ACR499_VACR499BLK_Seed.dat /l
<Tools Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner>
/i <Tools Install
Directory>\REPPATCH\BulkRequest_ACR499\SEED_DATA\SeedInp_Files\<Database Platform>\
ACR499_SIAMSTDNV_Seed.inp /q -1 /w y /e n /t n /x R /n 100 /h log
<ODBC Source Name> - Replace with the ODBC name
4 Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure import completed
successfully
5 Depending upon the language that you are installing, complete Step 6 or Step 7.
6 If you are installing ENU, perform the following steps:
a Run the following command after importing the ACR499_VACR499BLK_Seed.dat file:
Directory>\REPPATCH\BulkRequest_ACR499\SEED_DATA\ACR499_VACR499BLK_Seed_Loca
le_ENU.dat /l <Tools Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /
d <Table Owner> /i <Tools Install Directory>\REPPATCH\
BulkRequest_ACR499\SEED_DATA\SeedInp_Files\<Database Platform>\
ACR499_SIAMSTDNV_Seed_Locale_ENU.inp q -1 /w y /e n /t n /x R /n 100 /h log
316
7 If you are installing a language other than ENU, perform the following steps:
Run the following command after importing ACR499_VACR499BLK_Seed.dat file to import
the locale specific seed_locale_XXX.dat, where XXX is the language code.
Directory>\REPPATCH\BulkRequest_ACR499\SEED_DATA\XXX\seed_locale_XXX.dat/l
<Tools Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table
Owner> /q -1 /w n /e y /t n /x R /n 100 /h log
xxx - Replace with your language name
To import locale- specific symbolic strings
1 From within Siebel Tools, navigate to Tools > Utilities > Locale Management.
The Locale Management dialog box appears.
2 In the Options tab, under Languages, select a source language and a target language.
3 Click the Import tab, and enter the directory path and name of the file you want to import. For
example, enter <Tools Install Directory>\REPPATCH\BulkRequest_ACR499\LMU\<target
language>\lmu_srm.xlf3.
4 Click the Import button to import the data.
Verifying Seed Data for ACR 499
Use the procedures in the following sections to verify the seed data for ACR 499.
To verify the views
2 Verify the following views.
View Name Description
Default
Local
Access
ABO Bulk Request Action Set Quotes View ABO Bulk Request Action Set Quotes
View
Y
ABO Quote Item Drill Down View ABO Quote Item Drill Down View Y
ABO BR List Mgmt Assets View - All ABO BR List Mgmt Assets View - All Y
ABO Bulk Request Template View ABO Bulk Request Template View Y
To verify the List of Values
1 Navigate to Administration - Data > LOV Explorer and verify the following values:
2 Navigate to Administration - Data > List Of Values, and verify the following values:
NOTE: The values are for ENU only and the Display Value and the Language Independent Code
value is the same. The Language Name is English-American for all the LOV values.
Asset Target Query View Asset Target Query View Y
ABO Bulk Request Explode Exceptions View ABO Bulk Request Explode
Exceptions View
Y
Type Translate
ABO_BR_ACTSET_TEMPLTE_TYPE Y
ABO_BR_TEMPLTE_INSTANCE_SCOPE Y
ABO_BR_TEMPLTE_INSTANCE_TYPE Y
Type
Display
Value LIC Language Name Order Active Translate
Replication
Level
QUOTE_TYPE Bulk Request
Template
Quote
Bulk
Request
Template
Quote
English-American 52 Y Y All
QUOTE_TYPE Bulk Request
Explode
Quote
Bulk
Request
Explode
Quote
ABO_BR_INSTAN
CE_TYPE
Network Id Network
Id
ABO_BR_INSTAN
CE_TYPE
Agreement
Id
Agreeme
nt Id
LISTMGMT_LIST_
TYPE
Assets Assets English-American 3 Y Y All
SLM_FIELD_DISP
LAY
Assets Assets English-American - Y Y All
SLM_LST_CATEG
ORY
Assets SLM List
Member -
Asset
English-American - Y N All
ABO_BR_SUBMIT
_STATUS
Processing Processin
g
ABO_BR_SUBMIT
_STATUS
Queued Queued English-American 6 Y Y All
Default
Local
Access
318
3 After verifying the records in the preceding table, navigate to Menu > Clear Cache.
4 Log out of the Siebel application and then log back in.
Signals
Use the procedures in the following section to verify the ACR 499 signals.
WF_GROUP_CD ABO Bulk
Request
ABO Bulk
Request
ABO_BR_ACTSET
_TEMPLTE_TYPE
New New English-American 1 Y Y All
ABO_BR_ACTSET
_TEMPLTE_TYPE
Modify Modify English-American 2 Y Y All
ABO_BR_ACTSET
_TEMPLTE_TYPE
Upgrade Upgrade English-American 3 Y Y All
ABO_BR_TEMPLT
E_INSTANCE_SCO
PE
All All English-American 1 Y Y All
ABO_BR_TEMPLT
E_INSTANCE_SCO
PE
Include Include English-American 2 Y Y All
ABO_BR_TEMPLT
E_INSTANCE_SCO
PE
Exclude Exclude English-American 3 Y Y All
ABO_BR_HEADER
_STATUS
Explode Fault Explode
Fault
ABO_BR_HEADER
_STATUS
Exploded Exploded English-American 10 Y Y All
ABO_BR_HEADER
_STATUS
Exploding Explodin
g
FS_ORDER_TYPE Bulk Request
Explode
Order
Bulk
Request
Explode
Order
ABO_BR_ACTION
_CODE
Replace Replace English-American 7 Y Y All
ABO_BR_TEMPLT
E_INSTANCE_TYP
E
Contact Id Contact
Id
ABO_BR_TEMPLT
E_INSTANCE_TYP
E
Service Id Service
Id
ABO_BR_EXCEPTI
ON_TYPE
E&C E&C English-American 1 Y Y All
ABO_BR_EXCEPTI
ON_TYPE
Explode
Error
Explode
Error
Type
Display
Value LIC Language Name Order Active Translate
Replication
Level
To verify the ABOBulkRequestCheckEligibility signal
1 Navigate to Administration - Order Management -> Signals.
2 In the Signals list view, confirm that the signalABOBulkRequestCheckEligibility has been created.
3 In the Versions list view, click on the Work Space link to drill down to the Actions list view.
4 In the Actions list view, verify the following.
5 In the Parameters list view, verify the following.
Variable Maps
Use the procedures in the following section to verify the ACR 499 variable maps.
To verify the ABO Bulk Request Eligibility Variable Map - Row Set variable map
1 Navigate to Administration - Order Management > Variable Maps.
2 Verify that the ABO Bulk Request Eligibility Variable Map - Row Set variable map has been
created.
3 Click on the Work Space link.
4 In the Variable Definition view, verify the following.
NOTE: The Path, Mode, and Source Type fields are shown in the Variable Sources view.
Sequence Service Type Service Name Service Method
1 Workflow PSP Driver Workflow Process RunProcess
Name Value
CPScope Whole
Pick Mode Post-Pick
Project Asset Key Delay
RowScope Selected
SubPSPWFName ABO Bulk Request - Check Eligibility & Compatibility
Variable Map - Context Cfg Eligibility Variable Map - Context
Variable Map - Row Set ABO Bulk Request Eligibility Variable Map - Row Set
Name
In/
Out Type
On
Null Path Mode Source Type
Account Id In ID Ignore $Current/Header/Account
Id
Any Instance
Action Code In Text Ignore $Current/Line Item/Action
Code
Any Instance
320
City In Text Ignore $Current/Header/City Any Instance
Class Id In ID Ignore $Current/Line Item/Class
Id
Any Instance
Country In Text Ignore $Current/Header/Country Any Instance
Covered
Asset
Product Id
In ID Ignore $Current/Line Item/
Covered Asset Product Id
$Current/Line Item/
$Current/Line Item/
Agreement Instance
Order
Quote
Covered Line
Item Id
Covered Line Item Id
Agreement Instance
$Current/Line Item/
Order
$Current/Line Item/
Quote
Covered
Product Id
Covered Product Id
Any Instance
Eligibility
Reason
In/Out Text Ignore $Current/Line Item/
Eligibility Reason
Any Instance
Eligibility
Status
In/Out Text Ignore $Current/Line Item/
Eligibility Status
Any Instance
Exclude
Pricing Flag
In/Out Boole
an
Ignore $Current/Line Item/
Exclude Pricing Flag
Any Instance
Id In ID Ignore $Current/Line Item/Id Any Instance
Inclusive
Eligibility
Flag
In Boole
an
Inclusive Eligibility Flag
Any Instance
Name In Text Ignore $Current/Line Item/Name Any Instance
Parent Item
Id
In ID Ignore $Current/Line Item/Parent
Id
Any Instance
Post Pick In Text Ignore $Current/Line Item/Post
Pick CD
Any Instance
Postal Code In Text Ignore $Current/Header/Postal
Code
Any Instance
Pre Pick In Boole
an
Ignore $Current/Line Item/Pre
Pick CD
Any Instance
Pricelist Id In ID Ignore $Current/Line Item/Item
Price List Id
Agreement Instance
$Current/Line Item/Item
Price List Id
Config
Price List Id
Order
Price List Id
Quote
Name
In/
Out Type
On
5 In the Modes view, verify the following.
Data Maps
Use the following procedures to verify the ACR 499 data maps.
To verify the ABO Bulk Request Action Set Agreement I nbound Map
1 Navigate to Administration Integration > Data Map Editor.
Prod Prom Id In ID Ignore $Current/Line Item/Prod
Prom Id
Any Instance
Product Id In ID Ignore $Current/Line Item/
Product Id
Any Instance
Product Line
Id
Product Line Id
Any Instance
Product Port
Id
In ID Ignore $Current/Line Item/Port
Item Id
Any Instance
Promotion
Item Flag
In Boole
an
Promotion Item Flag
Quote Instance
Quantity In Integ
er
Quantity
Any Instance
Root Bundle
Flag
In Boole
an
Ignore $Current/Line Item/Root
Bundle Flag
Agreement Instance
$Current/Line Item/Root
Bundle Flag
Order
$Current/Line Item/Root
Bundle Flag
Quote
Sales
Service Flag
In Boole
an
Ignore $Current/Line Item/Sales
Service Flag
Agreement Instance
$Current/Line Item/Sales
Service Flag
Order
$Current/Line Item/Sales
Service Flag
Quote
State In Text Ignore $Current/Header/State Any Instance
Usage Asset
Product Id
In ID Ignore $Current/Line Item/Usage
Asset Product Id
Any Instance
$Current/Line Item/
Covered Asset Id
Order
$Current/Line Item/Usage
Asset Product Id
Quote
Mode Object
Any Line Item
Name
In/
Out Type
On
322
2 In the Integration Component Map Applet, select the following records and verify the Source
Expression and Target Field Name as shown in the following table.
NOTE: The Source Expression and Target Field Name fields are shown in the Integration Field
Map Applet.
To verify the ABO Bulk Request Action Set Asset I nbound Map
Map Applet.
To verify the ABO Bulk Request Action Set Contact I nbound Map
Name
Source
Component
Target
Component
Source
Expression Target Field Name
Action Set Header Action Set [Account] Customer Account
[Account Id] Customer Account Id
Instance Line Item Instance [Agreement Id] Agreement Id
Name
Source
Component Target Component Source Expression Target Field Name
Action Set Header Action Set [Owner Account Id] Customer Account Id
Instance Line Item Instance [Id] Asset Id
[Product Id] Product Id
[Name] Product Name
[Root Id] Root Asset Id
[Service Id] Service Id
Map Applet.
To verify the ABO Bulk Request Action Set Network I nbound Map
Map Applet.
To verify the ABO Bulk Request All Contact I nbound Map
Name Source Component
Target
Component Source Expression Target Field Name
Action Set Account Action Set [Name]
[Account Id]
Customer Account
Customer Account Id
Instance Related Contact Instance [Email Address] Email Address
[Contact Id] Unique Id
Name
Integration
Component
Target
Action Set Header Action Set [Owner Account Id] Customer Account Id
Instance Line Item Instance [Id] Asset Id
[Compound Product Compound Product
Number] Number
[Root Id] Root Asset Id
[Service Id] Service Id
324
Map Applet.
Activating Workflows
Use the following procedure to activate the workflows for ACR 499.
To activate the workflows for ACR 499
1 Select Workflow Process Object in OBLE.
Name
Source
Component
Target
Action Set Account Header [Name]
[Account Id]
Customer Account
Customer Account Id
Instance Related Contact Line Item [Email Address] Email Address
[Contact Id] Unique Id
2 Right-click Import Workflow Process and import the .xml workflow from the <Tools Installed
Directory>\REPPATCH\BulkRequest_ACR499\REPOSITORY\Workflow folder under the following
projects.
NOTE: You must import the workflows in the order listed in the following table.
Sequence Workflow Name New/Modified Project
1 ABO Bulk Request - Promotion Disconnect
Process
New ABO Bulk Request
2 ABO Bulk Request - Modify Promotion
Products & Services Process
3 ABO Bulk Request - Edit Iterate Process New ABO Bulk Request
4 ABO Bulk Request - Disconnect Iterate
Process
5 ABO Bulk Request - Cancel Process
Workflow
6 ABO Bulk Request -Validate Process Modified ABO Bulk Request
7 ABO Bulk Request - Explode Workflow New ABO Bulk Request
8 ABO Bulk Request - Explode Driver
Workflow
Sub Process
10 ABO Bulk Request - Edit Complex Asset
Workflow
Integration SubProcess
12 ABO Bulk Request - Disconnect Asset Sub-
process
13 ABO Bulk Request - Edit Promotion Related
Asset Workflow
14 ABO Bulk Request - Promotion - Update
Matched Items Sub Process
15 ABO Bulk Request - Promotion - AddMissed
Items Sub Process
16 ABO Bulk Request - Add Sub-Process
Workflow
17 ABO Bulk Request - ApplyProductPromotion New ABO Bulk Request
18 ABO Bulk Request - All Instances Sub
Process
326
NOTE: Make sure that the new projects have been imported and that the new SRF has been
applied to the server before you import and activate the workflows.
3 Use the following steps to publish the workflows:
a Log into the Siebel application as an administrator.
19 ABO Bulk Request - Modify Sub-Process
Workflow
20 ABO Bulk Request - Delete Sub-Process
Workflow
21 ABO Bulk Request - Upgrade Sub-Process
Workflow
22 ABO Bulk Request - Suspend_Resume Sub-
Process Workflow.xml
23 ABO Bulk Request - ModifyWebService-
Order
24 ABO Bulk Request - Check Eligibility &
Compatibility
25 ABO Bulk Request - Process Action Sub-
Process Workflow
26 ABO Bulk Request - Disconnect Products &
Services Process
27 ABO Bulk Request - Inclusive Process
Action Sub-Process Workflow
28 ABO Bulk Request - All Exclusive Process
Action Sub-Process Workflow
29 ABO Bulk Request - Prepare Action Set Sub-
Process Workflow
30 ABO Bulk Request - Sub Process Workflow Modified ABO Bulk Request
31 ABO Bulk Request - Parallel Sub Process
Workflow
32 ABO Bulk Request - Submit Process
Workflow
33 ABO Bulk Request - Submit Driver Process
Workflow
34 ABO Bulk Request Add Item Customize
SubProcess Quotes
35 ABO Bulk Request Add Item Customize
Process
Sequence Workflow Name New/Modified Project
b Navigate to Administration - Business Process > Workflow Deployment and activate the
workflows in the following order:
Sequence Workflow Name
1 ABO Bulk Request - Promotion Disconnect Process
2 ABO Bulk Request - Modify Promotion Products & Services Process
3 ABO Bulk Request - Edit Iterate Process
4 ABO Bulk Request - Disconnect Iterate Process
5 ABO Bulk Request - Cancel Process Workflow
6 ABO Bulk Request -Validate Process
7 ABO Bulk Request - Explode Workflow
8 ABO Bulk Request - Explode Driver Workflow
9 ABO Bulk Request - Promotion Disconnect Sub Process
10 ABO Bulk Request - Edit Complex Asset Workflow
11 ABO Bulk Request - Promotion Disconnect Integration SubProcess
12 ABO Bulk Request - Disconnect Asset Sub-process
13 ABO Bulk Request - Edit Promotion Related Asset Workflow
14 ABO Bulk Request - Promotion - Update Matched Items Sub Process
15 ABO Bulk Request - Promotion - Add Missed Items Sub Process
16 ABO Bulk Request - Add Sub-Process Workflow
17 ABO Bulk Request - ApplyProductPromotion
18 ABO Bulk Request - All Instances Sub Process
19 ABO Bulk Request - Modify Sub-Process Workflow
20 ABO Bulk Request - Delete Sub-Process Workflow
21 ABO Bulk Request - Upgrade Sub-Process Workflow
22 ABO Bulk Request - Suspend/Resume Sub-Process Workflow
23 ABO Bulk Request - ModifyWebService-Order
24 ABO Bulk Request - Check Eligibility & Compatibility
25 ABO Bulk Request - Process Action Sub-Process Workflow
26 ABO Bulk Request - Disconnect Products & Services Process
27 ABO Bulk Request - Inclusive Process Action Sub-Process Workflow
28 ABO Bulk Request - All Exclusive Process Action Sub-Process Workflow
29 ABO Bulk Request - Prepare Action Set Sub-Process Workflow
30 ABO Bulk Request - Sub Process Workflow
328
NOTE: The status of each workflow changes from In Progress to Complete after the workflow is
published.
4 After activating the workflows, reload the runtime events as follows:
a Navigate to Administration - Runtime Events.
b Choose reload runtime events once.
Adding Responsibilities for New Views
1 From the Siebel application, navigate to Administration - Application > Views.
2 Query for the views listed in the following table.
NOTE: If the views do not exist, add them.
3 Navigate to the Responsibilities applet and associate the Siebel Administrator responsibility to all
of these views.
4 Navigate to Administration User > Users, query for SADMIN in the User Id field, and add the
Siebel Administrator responsibility to the SADMIN user.
5 Log out of the Siebel application and log back in.
31 ABO Bulk Request - Parallel Sub Process Workflow
32 ABO Bulk Request - Submit Process Workflow
33 ABO Bulk Request - Submit Driver Process Workflow
34 ABO Bulk Request Add Item Customize SubProcess Quotes
35 ABO Bulk Request Add Item Customize Process
Default
Local
Access
ABO Bulk Request Action Set Quotes View ABO Bulk Request Action Set
Quotes View
Y
ABO Quote Item Drill Down View ABO Quote Item Drill Down View Y
ABO BR List Mgmt Assets View - All ABO BR List Mgmt Assets View -
All
Y
ABO Bulk Request Template View ABO Bulk Request Template View Y
Asset Target Query View Asset Target Query View Y
ABO Bulk Request Explode Exceptions View ABO Bulk Request Explode
Exceptions View
Y
Sequence Workflow Name
Adding New Order Types
1 From the Siebel application, navigate to Administration - Data > Orders > Order Types.
2 Create a record with the following values:
Order Type: Bulk Request Explode Order
Type Code: Sales
Adding New System Preferences
1 Navigate to Administration - Application > System Preferences.
2 Create a new record with the following values:
System Preference Name: Enable ACR499 BulkRequest
System Preference Value: Y
Modifying Variable Maps
You must modify variable maps to implement ACR 499. The following section contains procedures for
modifying these variable maps.
To modify the Product Eligibility Variable Map - Context variable map
2 Query for the Product Eligibility Variable Map - Context variable map and lock the object.
3 Click the Work Space link.
4 In the Variable Definition view, query for the following records and create the Path, Mode, and
Source Type as shown in the following table.
5 In the Modes view, create records as shown in the following table.
Name In/Out Type On Null Path Mode Source Type
Account Id In ID Ignore $Current/Header/
Customer Account Id
Bulk Request Instance
$Current/ActionSet/
Customer Account Id
External Bulk
Request
Mode Object Name
Bulk Request Header
External Bulk Request ActionSet
330
6 Navigate back to the Variable Maps link and query for Product Eligibility Variable Map - Context
again.
7 Click Release New Version and select Menu > Clear Cache.
To modify the Product Eligibility Variable Map - Row Set variable map
2 Query for the Variable Product Eligibility Variable Map - Row Set and lock the object.
Name In/Out Type On Null Path Mode
Source
Type
Account Id In ID Ignore $Current/Line Item/
Account Id
External
Bulk
Request
Instance
Agreement Id In ID Ignore $Current/Instance/
Agreement Id
External
Bulk
Request
Instance
Asset Id In ID Ignore $Current/Instance/Asset
Id
External
Bulk
Request
Instance
Compound
Product
Number
In Text Ignore $Current/Instance/
Compound Product
Number
External
Bulk
Request
Instance
Email Address In Text Ignore $Current/Instance/Email
Address
External
Bulk
Request
Instance
Product Name In Text Ignore $Current/Instance/
Product Name
External
Bulk
Request
Instance
Root Asset Id In ID Ignore $Current/Instance/Root
Asset Id
External
Bulk
Request
Instance
5 In the Modes view, create a record with the following values:
Mode: External Bulk Request
Object Name: Instance
6 Navigate back to the Variable Maps link and query for Product Eligibility Variable Map - Row Set
again.
To modify the Cfg Eligibility Variable Map - Context variable map
2 Query for the Cfg Eligibility Variable Map - Context variable map and lock the object.
5 In the Modes view, create records as shown in the following table:
6 Navigate back to the Variable Maps link and query for Cfg Eligibility Variable Map - Context again.
Service Id In ID Ignore $Current/Instance/
Service Id
External
Bulk
Request
Instance
Unique Id In ID Ignore $Current/Instance/
Unique Id
External
Bulk
Request
Instance
Source
Type
Customer Account Id
External Bulk
Request
Mode Object Name
Bulk Request Header
Any Header
Source
Type
332
To modify the Default Eligibility Variable Map - Context variable map
2 Query for the Default Eligibility Variable Map - Context variable map and lock the object.
5 In the Modes view, create records as shown in the following table:
6 Navigate back to the Variable Maps link and query for Default Eligibility Variable Map - Context
again.
To modify the Default Pricing Eligibility Variable Map - Row Set variable map
2 Query for the Default Pricing Eligibility Variable Map - Row Set variable map and lock the object.
Source
Type
Customer Account Id
$Current/ActionSet/
Customer Account Id
External Bulk
Request
Mode Object Name
Bulk Request Header
External Bulk Request ActionSet
Mode: External Bulk Request
Object Name: Line Item
6 Navigate back to the Variable Maps link and query for Default Pricing Eligibility Variable Map -
Row Set again.
Modifying Integration Data Maps
Use the procedures in the following section to modify the data maps for ACR 499.
To modify the Bulk Request Order I O Map
2 Query for Bulk Request Order IO Map.
3 Delete all of the records from Integration Component Map applet.
4 In the Integration Object Map Applet, click on Auto-Map.
Source
Type
Action
Code
In/Out Text Ignore $Current/Line Item/Action
Code
External
Bulk
Request
Instanc
e
Prod
Prom Id
In/Out ID Ignore $Current/Line Item/Prod
Prom Id
External
Bulk
Request
Instanc
e
Prod
Prom
Instance
Id
Prom Instance Id
External
Bulk
Request
Instanc
e
Prod
Prom Rule
Id
Prom Rule Id
External
Bulk
Request
Instanc
e
334
5 Verify the following records in the Integration Component Map Applet.
To modify the Bulk Request Quote I O Map
2 Query for Bulk Request Quote IO Map.
3 Delete all the records from Integration Component Map Applet.
5 Verify the following records in the Integration Component Map Applet.
To modify the ABO Bulk Request SI S OM Order I O Map
2 Query for ABO Bulk Request SIS OM Order IO Map.
5 Select Header_to_Header in the Integration Component Map Applet.
6 In the Integration Field Applet, change the Source Expression [Order Type] to LookupValue
("FS_ORDER_TYPE", "Bulk Request Template Order").
7 Select Line Item_to_Line Item in IC Map Applet and repeat Step 6.
8 Delete the following values from the Integration Field Map Applet for all four Integration
Component Maps.
Name Source Component Target Component
Header_to_Header Header Header
Line Item_to_Line Item Line Item Line Item
XA_to_XA XA XA
Name Source Component Target Component
Header_to_Header Header Header
Line Item_to_Line Item Line Item Line Item
XA_to_XA XA XA
[Created] Created
[Created By] Created By
[Id] Id
9 Delete the following fields from Integration Field Map Applet, corresponding to the
Header_to_Header mappings.
10 Delete the following fields from Integration Field Map Applet, corresponding to the XA_to_XA
mappings.
To modify the ABO Bulk Request SI S OM Quote I O Map
2 Query for the ABO Bulk Request SIS OM Quote IO Map.
5 Select Header_to_Header in the Integration Component Map Applet.
6 In the Integration Field Applet, change the Source Expression [Quote Type] to LookupValue
("QUOTE_TYPE", "Bulk Request Template Quote").
7 Select Line Item_to_Line Item in IC Map Applet and repeat Step 6.
8 Delete the following values from the Integration Field Map Applet for all four Integration
Component Maps.
[Mod Id] Mod Id
[Updated] Updated
[Updated By] Updated By
[Conflict Id] Conflict Id
[Revision Number] Revision Number
[Order Number] Order Number
[Quote Number] Quote Number
[Parent Id] Parent Id
[Created] Created
[Created By] Created By
[Id] Id
336
9 Delete the following fields from Integration Field Map Applet, corresponding to the
Header_to_Header mappings.
10 Delete the following fields from Integration Field Map Applet, corresponding to the Line
Item_to_Line Item mappings.
11 Delete the following fields from Integration Field Map Applet, corresponding to the XA_to_XA
mappings.
If you are using the Bulk Requests functionality for the first time, you must add a new List of Values.
To add the LOV_ TYPE List of Values
1 Navigate to Administration - Data > List Of Values, search for the LOV_TYPE List of Values, and
if it does not exist, add it using the values in the following table:
[Mod Id] Mod Id
[Updated] Updated
[Updated By] Updated By
[Conflict Id] Conflict Id
[Parent Quote Id] Parent Quote Id
[Revision] Revision
[Quote Number] Quote Number
Type Display Value LIC
Language
Name Order Active Translate
Replic
ation
Level
LOV_TYPE UINBOX_INBOX
_TYPE
UINBOX_IN
BOX_TYPE
English-
American
- Y Y All
2 Navigate to Inbox Administration > All Inbox Types and verify that the records listed in the
following table exist.
3 Select each record from Step 2 and navigate to the Translations Tab.
4 If the display name has not been added, then add it with the appropriate language. For example,
for "Bulk Request Exception" for ENU, add a record with the following values:
The following sections contain information about how to apply and configure ACR 500.
CAUTION: You must install ACR 471 before you install ACR 500.
applicable workarounds.
Wrong Display Mode in Message Type
Category: Order Administration
Subcategory: Unified Messaging
Change Request: 12-1YMMELB
In the DEU application, the display mode in message type is ENU, not DEU.
1 Within the Siebel application, navigate to Administration - Order Management > Message Types,
and query for the following message types:
Promotion - Multiple Commitment Broken Message - Debundle
Name Business Object Name Category Action Type
Bulk Request Exception ABO Bulk Request BULK REQUEST UINBOX_INBOX_TYPE
Bulk Request Status ABO Bulk Request BULK REQUEST UINBOX_INBOX_TYPE
Bulk Request Cancelled ABO Bulk Request BULK REQUEST UINBOX_INBOX_TYPE
Language Display Name
English-American Bulk Request Exception
338
Promotion - Broken Commitment Error - Debundle
Promotion - Component Commitment Penalty
Promotion - Bottomup Recommendation For Assets
Promotion - No Promotion Recommendations
Promotion - Multiple Commitment Broken Message - Components
Promotion - Broken Component Commitment Error
2 Change the display mode of the message type from ENU to the corresponding language. In this
case, change the display mode of the following message types from ENU to DEU:
3 For each of the message types mentioned above, select Menu > Clear Cache.
Error Messages Occur When Debundling Promotions
Category: Product Promotions
Subcategory: Administration
Change Request: 12-20JI6NQ
In the DEU application, users receive an error message when they try to debundle promotions.
NOTE: Before you begin the following procedures, within Siebel Tools, query for the ISS Promotion
Workflow project, and lock it.
Message Type Display Mode (ENU) Display Mode (DEU)
Promotion - Multiple Commitment Broken
Message - Debundle
Active Aktiv
Promotion - Broken Commitment Error -
Debundle
Active Aktiv
Promotion - Component Commitment Penalty Passive Passiv
Promotion - Bottomup Recommendation For
Assets
Active List Aktive Liste
Promotion - No Promotion Recommendations Active Aktiv
Promotion - Multiple Commitment Broken
Message - Components
Active Aktiv
Promotion - Broken Component Commitment
Error
Active Aktiv
To edit the I SS Promotion Upgrade Process workflow
1 Within Siebel Tools, navigate to Object Explorer, and select Workflow Processes.
2 Query for the ISS Promotion Upgrade Process workflow and revise the workflow.
3 In the revised workflow, select Edit Workflow Process from the menu, and add the following
process property:
4 Add the following output argument in the Get Account Details step:
5 Add the following input argument in the Disconnect Old Promotion step:
6 Publish and activate the workflow.
To edit the I SS Promotion Split Process workflow
2 Query for the ISS Promotion Split Process workflow and revise the workflow.
process property:
Name Display Name In/Out Business Object Data Type
Root Account Id Root Account Id In/Out Account String
Property Name Type
Business
Component Name
Business
Component Field
Root Account Id Business Component Account Master Account Id
Subprocess Input Type Property Name
Root Account Id Process Property Root Account Id
Property Name Type
Business
Component Name
Business
Component Field
340
5 Add the following input argument in the Disconnect Old Promotion step.
To edit the I SS Promotion Merge SubProcess workflow
1 Within Siebel Tools, navigate to Object Explorer and select Workflow Processes.
2 Query for the ISS Promotion Merge SubProcess workflow and revise the workflow.
3 In the revised workflow, select Edit Workflow Process from the menu, and Add the following
process property:
To edit the I SS Promotion Debundle I ntegration SubProcess workflow
2 Query for the ISS Promotion Debundle Integration SubProcess workflow and revise the workflow.
3 In the revised workflow, select Edit Workflow Process from the menu, and Add the following
process property:
Property Name Type
Business
Component Name
Business Component
Field
Name Display Name In/Out
Business
Object Data Type
4 Add the following input argument in the Disconnect SubProcess step:
To edit the I SS Promotion Debundle Process workflow
2 Query for the ISS Promotion Debundle Process workflow and revise the workflow.
process property:
5 Add the following input argument in the Debundle Sub-process step:
NOTE: After activating all the workflows, reload the run time events.
Applying ACR 500
1 Open tools.cfg from <Tools Install Directory>\Bin\Enu and verify the [Siebel] section.
Property Name Type
Business
Component Name
Business Component
Field
342
2 Make sure that the SymStrPrefix entry has been set to SBL_
[Siebel]
..
.; SymStrPrefix parameter needs to be X_ for Siebel customers.
SymStrPrefix = SBL_
..
3 In Siebel Tools, create a project called ISS Promotion Split Merge.
Account
Asset Management
Cfg RTC
FS Agreement
ISS Authoring Admin
ISS Promotion Admin
ISS Promotion Split Merge
MACD Performance
Order Entry
Quote
Quote (UI)
Symbolic Strings
Table Order
Table Product
Table ProductPromotion
Table Quote
UMSUI
5 Import the following SIF files from the <Unzipped Folder>\ACR500\Objects folder into Siebel
Tools using the Tools Import from Archive option. Import these files in the order listed below. Use
the Merge option in Siebel Tools Import Wizard.
NOTE: If the symbolic strings are not exposed in View > Option > Object Explorer > Siebel
Object, navigate to View > Option, click the Object Explorer tab and check the Symbolic String.
Tables.sif
Symbolic Strings.sif
Web Templates.sif
Classes.sif
Commands.sif
Picklists.sif
Business Services.sif
Business Components.sif
Links.sif
Business Objects.sif
Integration Objects.sif
Applets.sif
Views.sif
Screens.sif
If you receive the warning error message, then lock the project displayed in the message.
6 After you have imported the SIF files, within Object Explorer, navigate to Table, and do the
following:
a Query for all the changed objects and select them.
b Click the Apply/DLL button, click Apply, and then click OK to apply the changes to the physical
database.
7 Within the Apply Schema dialog box, provide the following credentials to connect to the
database:
ODBC data source= <DSN Name> (create the DSN if you get a TNS not resolved error
message).
8 If the Siebel Server is running, stop it.
9 Compile all the locked projects using Tools > Compile Projects.
10 Save the SRF to <Siebel Server Install folder>\objects\ENU\siebel_sia.srf on the installed Siebel
server.
344
13 Right-click on Import Workflow Process and import the .xml workflow from the <Unzipped
Folder>\ACR500\Workflows folder under the following projects:
Sequence Workflow Name New/Modified? Project
1 ISS Promotion Calculate
Component Penalty Charges
SubProcess
New ISS Promotion Workflow
2 ISS Promotion Calculate Related
Objects Penalty Charges
SubProcess
3 ISS Promotion Disconnect
Component SubProcess
4 ISS Promotion Disconnect Process Modified ISS Promotion Workflow
5 ISS Promotion Disconnect
Modified ISS Promotion Workflow
6 ISS Promotion Upgrade Charge
Proration SubProcess
7 ISS Promotion Create Agreement
Details
8 ISS Promotion Agreement
Management Sub Process
9 ISS Promotion Upgrade Check
Agreement SubProcess
10 SIS OM Edit Service Order Line
Item
11 ISS Promotion Debundle
12 ISS Promotion Debundle Process New ISS Promotion Workflow
13 ISS Promotion Recommendation
For Assets
14 ISS Add To Promotion Sub Process New ISS Promotion Workflow
15 ISS Promotion Check Order Item
Sub Process
16 ISS Promotion Check Quote Item
Sub Process
17 ISS Promotion Add To Promotion
Process
18 ISS Promotion Commitment
Compliance Check SubProcess
346
NOTE: Make sure that the new projects are imported and that the new SRF has been applied to
the server before you impor t and activate the workflows.
14 After you import the workflows, within Siebel Tools, publish the workflows in the same order in
which they were imported.
NOTE: After the workflows are published, the status of each workflow changes from In Progress
to Complete.
15 Log in to the Siebel application as an administrator.
16 Navigate to Administration - Business Process > Workflow Deployment and activate the
workflows in the following order:
19 ISS Promotion Disconnect Process
- for Verify
20 ISS Promotion Edit Integration
SubProcess
21 ISS Promotion Merge SubProcess New ISS Promotion Workflow
22 ISS Promotion Merge Process New ISS Promotion Workflow
23 ISS Promotion Split Process New ISS Promotion Workflow
24 ISS Promotion Upgrade Process Modified ISS Promotion Workflow
25 ISS Promotion Verify SubProcess Modified ISS Promotion Workflow
26 SIS OM Modify Products &
Services Process
27 SIS OM Disconnect Asset Sub-
process
28 SIS OM Edit Complex Asset
Workflow
29 SIS OM Edit Delta Quote Line Item Modified SIS OM Base Architecture
Sequence Workflow
1 ISS Promotion Calculate Component Penalty Charges SubProcess
2 ISS Promotion Calculate Related Objects Penalty Charges SubProcess
3 ISS Promotion Disconnect Component SubProcess
4 ISS Promotion Disconnect Process
5 ISS Promotion Disconnect Integration SubProcess
6 ISS Promotion Upgrade Charge Proration SubProcess
7 ISS Promotion Create Agreement Details
Sequence Workflow Name New/Modified? Project
17 Navigate to Administration - Runtime Events, and choose to reload runtime events for each
event.
1 Navigate to the directory in which you installed Siebel Tools and change the directory to
REPATCH\ACR500.
8 ISS Promotion Agreement Management Sub Process
9 ISS Promotion Upgrade Check Agreement SubProcess
10 SIS OM Edit Service Order Line Item
11 ISS Promotion Debundle Integration SubProcess
12 ISS Promotion Debundle Process
13 ISS Promotion Recommendation For Assets
14 ISS Promotion Check Order Item Sub Process
15 ISS Promotion Check Quote Item Sub Process
16 ISS Add To Promotion Sub Process
17 ISS Promotion Add To Promotion Process
18 ISS Promotion Commitment Compliance Check SubProcess
19 ISS Promotion Disconnect Process - for Verify
20 ISS Promotion Edit Integration SubProcess
21 ISS Promotion Merge SubProcess
22 ISS Promotion Merge Process
23 ISS Promotion Split Process
24 ISS Promotion Upgrade Process
25 ISS Promotion Verify SubProcess
26 SIS OM Modify Products & Services Process
27 SIS OM Disconnect Asset Sub-process
28 SIS OM Edit Complex Asset Workflow
29 SIS OM Edit Delta Quote Line Item
Sequence Workflow
348
Directory>\REPATCH\ACR500\SeedData\ACR500_Seed.dat /l <Tools Install
Directory>\REPATCH\ACR500\SeedData\SeedInpFiles\<Database Platform>\ ACR500_Seed.inp
/q -1 /w y /e n /t n /x R /n 100 /h log
<ODBC Source Name> - Replace with your ODBC name
4 Depending upon the language that you are installing, perform Step 5 or Step 6.
5 If you are installing ENU (English Language), do the following:
a Run the following command after importing ACR500_Seed.dat file.
Directory>\REPATCH\ ACR500\SeedData\ENU\seed_locale_ENU.dat /l <Tools Install
Install Directory>\REPATCH\ACR500\SeedData\SeedInpFiles\<Database
Platform>\ACR500_Seed_Locale_ENU.inp /q -1 /w y /e n /t n /x R /n 100 /h log
<Database Platform> - Replace with the database platform (ORACLE, DB2UDB or MSSQL)
c After you have imported the seed data, you must verify that it imported correctly. For more
information about verifying seed data, see Verifiying Seed Data for ACR 500 on page 352.
6 If you are installing a language other than ENU, perform the following steps:
a Run the following command after importing ACR500_Seed.dat file to import the locale-specific
seed_locale_XXX.dat, where XXX is the language code.
Directory>\REPATCH\ ACR500\SeedData\XXX\seed_locale_XXX.dat /l <Tools Install
/e y /t n /x R /n 100 /h log
b After you have imported the seed data, you must verify that it imported correctly. For more
information about verifying seed data, see Verifiying Seed Data for ACR 500 on page 352.
Use the following instructions to import locale-specific symbolic string values.
NOTE: The following procedure applies to customers who are installing languages other than ENU.
It does not apply to customers who are installing only ENU.
To import locale- specific symbolic string values
1 Within Siebel Tools, navigate to Tools > Utilities > Locale Management.
3 Click the Import tab.
4 Enter the directory path and name of the file you are going to import.
Adding Responsibilities for New Views
1 From the Siebel application, navigate to Administration - Application > Views.
2 Query for the views listed in the following table:
3 Navigate to the Responsibilities applet and associate the Siebel Administrator responsibility to all
of these views.
4 Navigate to Administration User > Users, query for SADMIN in the User Id field, and add the
Siebel Administrator responsibility to the SADMIN user.
5 Stop the Siebel Server and then restart it to make your changes visible.
6 Log into the Siebel application and verify that the Split and Merge view appears on the
Administration - Product > Product Promotions.
Modifying Lists of Values
1 In the Siebel application, navigate to Administration - Data > List Of Values.
Default
Local
Access
ISS Promotion Merge View ISS Promotion Merge View Y
ISS Promotion Split View ISS Promotion Split View Y
ISS Promotion Upgrade Aggregate View ISS Promotion Upgrade Aggregate View Y
350
2 Modify the values listed in the following table:
NOTE: Only the order of the LOVs has changed in the preceding table.
Modifying Variable Maps
Use the procedures in the following section to modify the variable maps associated with ACR 500.
Default Eligibility Variable Map - Context
2 Query for the Variable map Default Eligibility Variable Map - Context and lock the object.
4 In the Variable Definition view, query for the records listed in the following table and create the
Path, Mode and Source Type fields.
NOTE: Path, Mode and Source Type fields are shown in the Variable Sources applet.
Type
Display
Value LIC
Language
Replicati
on Level
PROMO_UPGRADE_
START_CD
Original
Start
Original
Start
English-
American
1 Y Y All
PROMO_UPGRADE_
START_CD
Original
End
Original
End
English-
American
2 Y Y All
PROMO_UPGRADE_
START_CD
Now Now English-
American
3 Y Y All
Account
Contracted
Products Only
Flag
In Boolean Ignore $Current/
AccountHeader/Use
Contracted Products
Only Flag
AccountHeader Instance
Account Id In ID Ignore $Current/
AccountHeader/Id
Account Type In Text Ignore $Current/
AccountHeader/Type
City In Text Ignore $Current/
AccountHeader/
Primary Account City
Country In Text Ignore $Current/
AccountHeader/
Primary Account
Country
6 Navigate back to the Variable Maps link and query for Promotion Upgrade Eligibility Variable Map
- Context again.
7 Click Release New Version and select Menu > Clear Cache
Default Eligibility Variable Map - Row Set ProdProm
2 Query for the Variable map Default Eligibility Variable Map - Row Set ProdProm and lock the
object.
4 In the Variable Definition view, query for the following records and create the Path, Mode and
Source Type fields.
NOTE: Path, Mode and Source Type fields are shown in the Variable Sources applet.
Postal Code In Text Ignore $Current/
AccountHeader/
Primary Account
Postal Code
State In Text Ignore $Current/
AccountHeader/
Primary Account State
Mode Object Name
AccountHeader AccountHeader
City In Text Ignore $Current/
AccountHeader/
Primary Account
City
Country In Text Ignore $Current/
AccountHeader/
Primary Account
Country
Postal Code In Text Ignore $Current/
AccountHeader/
Primary Account
Postal Code
352
6 Navigate back to the Variable Maps link and query for Default Eligibility Variable Map - Row Set
ProdProm again.
Verifiying Seed Data for ACR 500
Use the procedures in the following section to verify the seed data for ACR 500.
To verify the system preferences for ACR 500
Use the following procedure to verify system preferences.
1 Navigate to Administration - Application > System Preferences.
2 Verify the following system preferences:
NOTE: Setting the value for "All Assets" to N disables Asset Based Promotion Recommendation and
Apply - Scenario 2.
To verify the views for ACR 500
State In Text Ignore $Current/
AccountHeader/
Primary Account
State
Price List Id In ID Ignore $Current/
AccountHeader/
Price List Id
Mode Object Name
AccountHeader ProdProm Line Item
System Preference Name
System
Preference
Value Description
All Assets Y ACR500: Asset Based Promotions
Recommendation and Apply
Promotion Component Commitment Y ACR 500
2 Verify the following views.
To verify the Lists of Values for ACR 500
1 Navigate to Administration - Data > LOV Explorer and verify the following values:
2 Navigate to Administration - Data > List Of Values, and verify the following values:
value are the same. The Language Name is English-American for all the LOV values.
Default
Local
Access
ISS Promotion Merge View ISS Promotion Merge View Y
ISS Promotion Split View ISS Promotion Split View Y
ISS Promotion Upgrade Aggregate View ISS Promotion Upgrade Aggregate View Y
Type Translate
PROMO_AGGREGATE_DURATION Y
PROMO_OPER_TYPE Y
Type
Display
Value LIC
Language
Replication
Level
PROMO_OPER_TYPE Merge MERGE English-
American
1 Y Y All
PROMO_OPER_TYPE Split SPLIT English-
American
2 Y Y All
PROMO_OPER_TYPE Upgrade UPGRADE English-
American
3 Y Y All
PROMO_AGGREGATE_D
URATION
New
Duration
New
Duration
English-
American
1 Y Y All
PROMO_AGGREGATE_D
URATION
Original -
Maximum
Original -
Maximum
English-
American
2 Y Y All
PROMO_AGGREGATE_D
URATION
Original -
Minimum
Original -
Minimum
English-
American
3 Y Y All
PROMO_UPGRADE_STA
RT_CD
Earliest
Start
Earliest
Start
English-
American
4 Y Y All
PROMO_UPGRADE_STA
RT_CD
Earliest End Earliest End English-
American
5 Y Y All
PROMO_UPGRADE_STA
RT_CD
Latest Start Latest Start English-
American
6 Y Y All
354
Signals
Use the procedures in the following section to verify the signals for ACR 500.
To verify the SplitPromotion signal
1 Navigate to Administration - Order Management > Signals.
2 In the Signals list view, confirm that the signal SplitPromotion has been created.
4 In the Actions list view, verify the following:
5 In the Parameters list view, verify the following:
6 In the Properties list view, verify the following:
To verify the MergePromotion signal
2 In the Signals list view, confirm that the signal MergePromotion has been created.
PROMO_UPGRADE_STA
RT_CD
Latest End Latest End English-
American
7 Y Y All
UMS_DISPLAY_MODE Active List Active List English-
American
3 Y Y All
1 Business Service ISS Promotion Edit UI Service ShowPopup
Name Value
Applet ISS Promotion Split Popup Applet
Name Value
CanInvoke:Any [Product Type]=LookupValue('PROD_CD','Promotion')
1 Business Service ISS Promotion Management Service GetMergePromotion
Type
Display
Value LIC
Language
Replication
Level
5 In the Properties list view, verify the following:
To verify the AddToPromotion signal
2 In the Signals list view, confirm that the signal AddToPromotion has been created.
To verify the AddToPromotionBilling signal
2 In the Signals list view, confirm that the signal AddToPromotionBilling has been created.
To verify the GetPromoUpgradeEligibility signal
2 In the Signals list view, confirm that the signal GetPromoUpgradeEligibility has been created.
Name Value
CanInvoke:Any [Product Type]=LookupValue('PROD_CD','Promotion')
Name Value
Applet ISS Promotion Add To Promotion Popup Applet
Name Value
Applet ISS Promotion Add to Promotion Popup Applet (Billing)
356
To verify the GetAgreementConditionalCharge signal
2 In the Signals list view, confirm that the GetAgreementConditionalCharge signal has been
created.
Verifying Variable Maps
Use the procedures in the following section to verify the variable maps for ACR 500.
To verify the Promotion Upgrade Eligibility Variable Map - Context variable map
2 Verify that the variable map Promotion Upgrade Eligibility Variable Map - Context has been
created.
Sequenc
e
Service
Type
Service
Name
Service
Method Condition
1 Workflow PSP Driver
Workflow
Process
RunProcess GetProfileAttr('SkipToEnd') = 'N' OR
GetProfileAttr('SkipToEnd') IS NULL
Name Value
CPScope Whole
RowScope Selected
SubPSPWFName Check Eligibility & Compatibility - Default
Variable Map - Context Promotion Upgrade Eligibility Variable Map - Context
Variable Map - Row Set Promotion Upgrade Eligibility Variable Map - Row Set
1 Business Service ISS Promotion
Management Service
GetAgreementConditionalCharge
4 In the Variable Definition view, verify the following:
NOTE: The Path, Mode and Source Type fields are shown in the Variable Sources applet.
5 In the Modes view, verify the following:
To verify the Promotion Upgrade Eligibility Variable Map - Row Set variable map
2 Verify that the variable map Promotion Upgrade Eligibility Variable Map - Row Set has been
created.
4 In the Variable Definition view, verify the following:
NOTE: The Path, Mode and Source Type fields are shown in the Variable Sources applet.
Account
Contracted
Products Only
Flag
In Boolean Ignore $Current/AccountHeader/Use
Contracted Products Only Flag
Any Instance
Account Id In ID Ignore $Current/AccountHeader/Id Any Instance
Account Type In Text Ignore $Current/AccountHeader/Type Any Instance
City In Text Ignore $Current/AccountHeader/City Any Instance
Country In Text Ignore $Current/AccountHeader/Country Any Instance
Eligibility Display
Mode
In Integer Ignore PARAM_PSP_ELIGIBILITY_DISPL_MO
DE
Any Server Parameter
Mode In Text Ignore Context Service/GetCurrentMode Any Business Service
Postal Code In Text Ignore $Current/AccountHeader/Postal Code Any Instance
Price List Id In ID Ignore $Current/AccountHeader/Price List Id Any Instance
State In Text Ignore $Current/AccountHeader/State Any Instance
Mode Object Name
Any AccountHeader
Account Id In ID Ignore $Current/AssetLineItem/
Root Asset Service Account
Id
AssetLineItem Instance
Class Id In ID Ignore $Current/Product/Class Id Any Instance
Effective From In Date Ignore $Current/Product/Effective
From
Any Instance
Effective To In Date Ignore $Current/Product/Effective
To
Any Instance
358
5 In the Modes view, verify the following:
Message Types
Use the procedures in the following section to verify the message types for ACR 500.
To verify the Promotion - Multiple Commitment Broken Message - Debundle
message type
1 Navigate to Administration - Order Management > Message Types.
Eligibility Reason Out Text Ignore $Current/Product/Eligibility
Reason
Any Instance
Eligibility Status Out Text Ignore $Current/Product/Eligibility
Status
Any Instance
Inclusive Eligibility Flag In Boolean Ignore $Current/Product/Inclusive
Eligibility Flag
Any Instance
Pre Pick In Boolean Ignore $Current/Product/Pre Pick
CD
Any Instance
Product Id In ID Ignore $Current/Product/Id Any Instance
Product Line Id In ID Ignore $Current/Product/Product
Line Id
Any Instance
Mode Object Name
Any Product
AssetLineItem AssetLineItem
2 In the Message Type List view, verify that the Message Type Promotion - Multiple Commitment
Broken Message - Debundle has been created.
3 In the Responses list view, verify the following:
4 In the Payload list view, verify the following:
To verify the Promotion - Broken Commitment Error - Debundle message type
1 Navigate to Administration - Order Management > Message Types.
Name
Display
Mode Group Title Short Text Full Text
Promotion -
Multiple
Commitment
Broken
Message -
Debundle
Active Promotion Promotion -
Multiple
Commitment
Broken
Message
Commitment has
been broken for the
following
promotions:
[Promotion
Message] and
promotion
components:
[Promotion
Component
Message] Please
debundle each
promotion
component
individually to view
the specific terms.
Commitment has
been broken for the
following
promotions:
[Promotion
Message] and
promotion
components:
[Promotion
Component
Message] Please
debundle each
promotion
component
individually to view
the specific terms.
Sequence Name
Response
Type Log
Suppress
Repetition Business Service Method
1 Skip Respondent
Interested
N N ISS Promotion
Management
Service
MsgResponse
2 Cancel Respondent
Interested
N N ISS Promotion
Management
Service
MsgResponse
Payload Field
Promotion Message
Promotion Component Message
360
2 In the Message Type list view, verify that the Message Type Promotion - Broken Commitment
Error - Debundle has been created.
Name
Display
Promotion -
Broken
Commitment
Error - Debundle
Active Promotion Broken
Commitment
Commitment
broken for
promotion
component
'[Prod Prom
Name]'.
Commitment has
been broken for
promotion
component
'[Prod Prom
Name]'.
Customer must
keep this product
until
[Commitment
End Date] or pay
a penalty of
[Penalty]. Click
Accept to accept
the penalty and
de-bundle. Click
Skip to exclude
this component
from de-bundle.
Click Cancel to
cancel the
operation.
Sequence Name
Response
Type Log
Suppress
1 Accept Respondent
Interested
N N ISS Promotion
Management
Service
MsgResponse
2 Skip Respondent
Interested
N N ISS Promotion
Management
Service
MsgResponse
3 Cancel Respondent
Interested
N N ISS Promotion
Management
Service
MsgResponse
To verify the Promotion - Component Commitment Penalty message type
1 Navigate to Administration - Order Management -> Message Types.
2 In the Message Type list view, verify that the Message Type Promotion - Component Commitment
Penalty has been created.
To verify the Promotion - Bottomup Recommendation For Assets message type
Payload Field
Prod Prom Name
Commitment End Date
Penalty
Name
Display
Promotion -
Component
Commitment
Penalty
Passive Promotion Component
Commitment
Penalty
A penalty of
[Penalty] for
removing [Name]
with Integration
Id = [Integration
Id] is triggered.
Please click
Cancel to avoid
the penalty.
A penalty of
[Penalty] for
removing [Name]
with Integration
Id = [Integration
Id] is triggered.
Please click
Cancel to avoid
the penalty.
Payload Field
Integration Id
Name
Penalty
362
2 In the Message Type list view, verify that the Message Type Promotion - Bottomup
Recommendation For Assets has been created.
To verify the Promotion - No Promotion Recommendations message type
2 In the Message Type list view, verify that the Message Type Promotion - No Promotion
Recommendations has been created.
To verify the Promotion - Multiple Commitment Broken Message - Components
message type
Name
Display
Promotion -
Bottomup
Recommendation
For Assets
Active List Promotion Promotion
Recommendation
Recommend
[Prod Prom
Name]
Recommend
promotion
'[Prod Prom
Name]':
[Promotion
Description].
Sequence Name Response Type Log
Suppress
Repetition Field Business Service Method
1 Accept Respondent
Interested
Y N ISS Promotion
Management Service
MsgResponse
2 Reject No Interest Y Y Account Id ISS Promotion
Management Service
MsgResponse
Payload Field Response Field
Account Id Account Id
Name
Display
Promotion - No
Promotion
Recommendations
Active Promotion Recommendations There are no
Promotion
Recommendations for
this account.
There are no
Promotion
Recommendations for
this account.
2 In the Message Type list view, verify that the Message Type Promotion - Multiple Commitment
Broken Message - Components has been created.
To verify the Promotion - Broken Component Commitment Error message type
2 In the Message Type list view, verify that the Message Type Promotion - Broken Component
Commitment Error has been created.
Name
Display
Promotion -
Multiple
Commitment
Broken Message
- Components
Active Promotion Promotion -
Multiple
Commitment
Broken Message
Commitment has
been broken for
the following
assets:
[Message]
Commitment has
been broken for
the following
assets:
[Message]
Please
disconnect each
asset individually
to view the
specific terms.
Payload Field
Message
Name
Display
Promotion -
Broken
Component
Commitment
Error
Active Promotion Broken
Commitment
Commitment
broken for
promotion
component
'[Prod Prom
Name]
'A commitment
has been broken
for promotion
component '[Prod
Prom Name]'.
Customer must
keep this product
until
[Commitment
End Date] or pay
a penalty of
[Penalty].
364
Verifying Data Maps
Use the following procedure to verify the data maps for ACR 500.
To verify the data maps
1 Navigate to Administration - Application > Data Map Administration.
2 Verify the following data maps:
The following section contains information about how to install and configure ACR 502.
CAUTION: You must have installed ACR 502 before you install ACR 499. For information about how
to install ACR 499, see Instructions for ACR 499 on page 311. For information about why installing
ACR 499 after you have installed ACR 502 is problematic, from within My Oracle Support, navigate
to the Knowledge tab, and search for Article ID 1295924.1.
Sequence Name Response Type Log
Suppress
1 Accept Respondent
Interested
N N ISS Promotion
Management Service
MsgResponse
2 Reject Respondent
Interested
N N ISS Promotion
Management Service
MsgResponse
Payload Field
Prod Prom Name
Commitment End
Date
Penalty
Sequence XML File
1 CreatePromotionAgreementCoveredAssets
2 CreatePromotionItemAgreement
Installing ACR 502
EIM Asset
EIM Order
EIM Quote
Table Asset
Table Order
Table Quote
Row Set Transformation Toolkit
Cfg RTC
ISS Order Management
Cfg JS
Asset Management
Order Entry
Symbolic String
MACD Performance
Quote
2 Import the following SIF files in the order shown from the <Unzipped Folder>\ACR502 folder into
Siebel Tools using the Import From Archive option. Use the Merge option in Siebel Tools Import
Wizard.
NOTE: If Symbolic String is not exposed in View > Option > Object Explorer > Siebel Object,
navigate to View > Option, click the Object Explorer tab, and check Symbolic String.
VACR502_Tables.sif (HACR502_Tables.sif if you are an SEA customer)
VACR502_EIMTables.sif (HACR502_EIMTables.sif if you are an SEA customer)
Applet.sif
Business Component.sif
Business Object.sif
Business Service.sif
Integration Object.sif
Link.sif
Server Component Type.sif
366
Symbolic String.sif
If you receive the warning error message, then lock the project displayed in the message.
3 After you have imported the SIF files, navigate to Table in the Object Explorer.
a Query for all the changed objects and select them.
b Click the Apply/DDL button to apply the changes to the physical database.
c Click Apply and then click OK.
4 Provide the following credentials when connecting to the database:
ODBC data source= <DSN Name> (create the DSN if you receive a "TNS not resolved error
message")
5 Stop the Siebel Server if it is running.
6 Select Tools > Compile Projects to compile the locked projects.
7 On the installed Siebel Server, save the SRF file to either <Siebel Server Install
folder>\objects\ENU\siebel_sia.srf (if you are an SIA customer) or to <Siebel Server Install
folder>\objects\ENU\siebel.srf (if you are an SEA customer).
9 Update EIM mappings to reflect the new data model changes:
a Copy REPPATCH\VACR502\Repository\Table\EIM\eim45.sql and paste it into the <Installation
Location>\SERVER\siebsrvr\SQLTEMPL folder.
b Copy REPPATCH\VACR502\Repository\Table\EIM\ eim_export_lookup_bu_name.sql and paste it
into the <Installation Location>\SERVER\siebsrvr\ADMIN folder.
11 Right-click on Import Workflow Process and import the .xml workflow from the <Unzipped
Folder>\ACR502 folder under the projects listed in the following table:
NOTE: Make sure that the new projects are imported and that the new SRF is applied to the
server prior to importing and activating the workflows.
12 Log into the Siebel application as an administrator.
13 Navigate to Administration - Business Process > Workflow Deployment and activate the
workflows listed in the following table in the order in which they are shown:
NOTE: The status of each workflow changes from In Progress to Complete after the workflow is
published.
14 After activating the workflows, reload the runtime events by navigating to Administration -
Runtime Events, and selecting Reload Runtime Events from the applet-level menu.
Workflow Name New/Modified Project
Check Eligibility & Compatibility -
Default
Modified ISS Order Management
Product Eligibility & Compatibility -
Default
Modified Row Set Transformation Toolkit
Product Compatibility - Default Modified Row Set Transformation Toolkit
Configurator Eligibility Compatibility
Workflow
Modified Cfg RTC
Web Channel Product Eligibility &
Compatibility Driver Workflow
Modified Web Channel Order Management
SIS OM Apply Completed Service
Order Line Item to Service Profile
SIS OM Move Process Modified SIS OM Base Architecture
Sequence Workflow
1 Check Eligibility & Compatibility - Default
2 Product Eligibility & Compatibility - Default
3 Product Compatibility - Default
4 Configurator Eligibility Compatibility Workflow
5 Web Channel Product Eligibility & Compatibility Driver Workflow
6 SIS OM Apply Completed Service Order Line Item to Service Profile
7 SIS OM Move Process
368
a Navigate to Start > Setting > Control Panel > Administrative Tools > Data Sources (ODBC),
database.
2 Navigate to the directory where you installed Siebel Tools and change the directory to either
REPPATCH\VACR502 if you are an SIA customer or to REPPATCH\HACR502 if you are an SEA
customer.
Directory>\REPATCH\VACR502\SeedData\ENU\VACR502_Seed.dat/l <Tools Install
Directory>\REPATCH\VACR502\SeedData\<Database Platform>\VACR502_Seed.inp /q -1 /w y /
e n /t n /x R /n 100 /h log
<Database Platform> - Replace with the database platform (ORACLE, DB2UDB or MSSQL).
5 Depending upon the language that you are installing, complete either Step 6 or Step 7.
6 For ENU only, do the following:
Run the following command after importing the VACR502_Seed.dat file.
Directory>\REPATCH\VACR502\SeedData\ENU\VACR502_Seed_Locale_ENU.dat /l <Tools
Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i
<Tools Install Directory>\REPATCH\VACR502\SeedData\<Database Platform>\
VACR502_Seed_Locale_ENU.inp /q -1 /w y /e n /t n /x R /n 100 /h log
<Database Platform> - Replace with the database platform (ORACLE, DB2UDB or MSSQL).
7 For languages other than ENU, do the following:
Run the following command after importing VACR502_Seed.dat file to import the locale-
specific VACR502_Seed_Locale_XXX.dat, where XXX is the language code.
Directory>\REPATCH\VACR502\SeedData\XXX\VACR502_Seed_Locale_XXX.dat /l <Tools
Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q -
1 /w n /e y /t n /x R /n 100 /h log
Use the following procedure to import locale-specific symbolic strings.
To import locale- specific symbolic strings
1 Within Siebel Tools, navigate to Tools > Utilities > Locale Management.
3 Click the Import tab, and enter the following directory path: ACR502\LMU\XXX\lmu\lmu_crm.slf,
where XXX is the language code.
5 Navigate to Symbolic Strings > Symbolic String Locale, and query for the SBL_CFG_ENGINE_ON
symbolic string to verify that the data was created correctly.
Verifying Seed Data for ACR 502
The following section contains procedures for verifying signals, variable maps, lists of values,
andsystem preferences for ACR 502.
PrepareEnableEngine
2 In the Signals list view, confirm that the PrepareEnableEngine signal was created.
370
3 In the Versions list view, click on the latest version of the signal to drill down to the Actions list
view.
ReEnableiLogForQuickEdit
2 In the Signals list view, confirm that the ReEnableiLogForQuickEdit signal was created.
view.
UpdateUIForQuickEdit
2 In the Signals list view, confirm that the UpdateUIForQuick Edit signal was created.
view.
PrepareDisableEngine
2 In the Signals list view, confirm that the PrepareDisableEngine signal was created.
view.
1 Business Service Remote Complex Object Instance Service PrepareEnableEngine
1 Business Service Remote Complex Object Instance Service ReEnableiLogForQuickEdit
1 Business Service Remote Complex Object Instance Service UpdateUIForQuickEdit
1 Business Service Remote Complex Object
Instance Service
PrepareDisableEngine
Product Eligibility Variable Map - Context
2 Query to find the "Product Eligibility Variable Map - Context" variable map.
3 Click on the latest version of the variable map.
4 In the Variable Definition view, verify the following records:
5 In the Variable Sources applet, create a record as shown in the following table:
8 Release the variable map and clear the cache.
9 If you notice multiple workspaces for the variable map, use the following steps to correct the
workspace:
a Rename the Cfg Eligibility Variable Map - Context variable map to Old Cfg Eligibility Variable
Map - Context.
b Navigate to Menu and select Copy Variable Map.
c Rename the copied variable map to Cfg Eligibility Variable Map - Context, release the new
version, and clear the cache.
Cfg Eligibility Variable Map - Context
2 Query to find the Cfg Eligibility Variable Map - Context" variable map.
3 Click on the latest version of the variable map.
Name In/Out Type On Null Default Value
Pre Pick Compatibility In Boolean Ignore
Mode Path Source Type
Any PARAM_OM_PRODCFG_PREPICKCOMP Server Parameter
Pre Pick Mode In Text Ignore
Any $Current/Header/Pre Pick Mode Instance
372
8 Release the variable map and clear the cache.
9 If you notice multiple workspaces for the variable map, use the following steps to correct the
workspace:
a Rename the Cfg Eligibility Variable Map - Context variable map to Old Cfg Eligibility Variable
Map - Context.
b Navigate to Menu and select Copy Variable Map.
c Rename the copied variable map to Cfg Eligibility Variable Map - Context, release the new
version, and clear the cache.
List of Values
1 In the Siebel application, navigate to Administration - Data > LOV Explorer and verify that the
following LOV types have been created:
Pre Pick Compatibility In Boolean Ignore
Any PARAM_OM_PRODCFG_PREPICKCOMP Server Parameter
Pre Pick Mode In Text Ignore
Any $Current/Header/Pre Pick Mode Instance
Type Display Value Translate
LOV_TYPE CFG_QUICKEDIT_BTN_TYPE Y
2 In the Siebel application, navigate to Administration - Data > List Of Values, and verify that the
following values have been created:
value is the same. The Language Name is English-American for all the LOV values.
Server Parameter
1 Navigate to the Administration - Server Configuration screen > Servers and Parameters view.
2 Verify that the following server parameter has been created:
NOTE: If you want to enable Pre Pick Compatibility, enter True in the Value field for this
parameter. The Value on Restart field also changes to True.
Configuring Siebel Developer Web Client for ACR 502
Use the following procedure to configure the Siebel Developer Web Client for ACR 502.
To configure the Siebel Developer Web Client for ACR 502
1 Use any text editor to open the .cfg file of the Siebel Developer Web Client.
2 If the OrderManagement section already exists, add the following line to that section:
EnablePrePickCompatibility = TRUE
3 If the OrderManagement section does not already exist, add both the section header and the line
to the .cfg file, as follows:
[OrderManagement]
EnablePrePickCompatibility = TRUE
Configuring Siebel Product Configurator Web Templates
If you want to enable the Quick Edit UI theme, you must modify the web template to include the
Quick Edit button.
Type
Display
Value LIC
Language
Replication
Level
CFG_QUICKEDIT_BTN_TYPE Turn On
Quick-Edit
CFG OFF English -
American
1 Y Y All
CFG_QUICKEDIT_BTN_TYPE Turn Off
Quick-Edit
CFG ON English -
American
1 Y Y All
Name Value Value on Restart
Enable Pre Pick
Compatibility
False False
374
To modify the web template to include the Quick Edit button
1 Navigate to the <siebel install directory>\webtempl\ directory.
2 Locate the "eCfgTopLevelButtonsJS.swt" web template file for the UI control and open it using a
text editor (such as Notepad).
3 Edit the file:
Add the following lines:
<td nowrap>
<swe:control id="swe:EnableEngine" CfgUIControl="EnableEngine"
CfgHtmlType="MiniButton" InvokeMethod="EnableEngine"/>
</td>
NOTE: Use the REPPATCH\VACR502\TEMPLATES\eCfgTopLevelButtonsJS.swt file as a
reference.
<table datatable="0" summary="" border="0" bgcolor="white" width="100%">
<tr>
<td nowrap>
<swe:control id="swe:EnableEngine" CfgUIControl="EnableEngine"
CfgHtmlType="MiniButton" InvokeMethod="EnableEngine"/>
</td>
<td nowrap>
<swe:control id="swe:CheckPrice" CfgUIControl="Check the price"
CfgHtmlType="MiniButton"
InvokeMethod="CalculatePriceCX"/>
</td>
<td nowrap>
<swe:control id="swe:Save" CfgUIControl="Save" CfgHtmlType="MiniButton"
InvokeMethod="SyncInstance"/>
</td>
..
</table>
4 Within Internet Explorer, navigate to Tools > Internet Options > General tab, delete all of the
temporary files and log into the Siebel application.
If you want to enable Pre Pick Compatibility inside Siebel Product Configurator, you must modify the
web template to include the parameter ForceRefresh = Y.
To enable Pre Pick Compatibilty with Siebel Product Configurator
1 Navigate to the <siebel install directory>\webtempl\ directory.
2 Locate the "eCfgControlComboAddPriceJS.swt" web template file for the UI control and open it
using a text editor (such as Notepad).
NOTE: The web templates for controls all begin with eCfgControl.
376
3 Within the file, search for the <swe: control> tag and edit it to ForceRefresh="Y".

<swe:include file="eCfgPort_HeaderJS.swt"/>
<tr>
<td width=100% colspan=2>
<table cellpadding=0 cellspacing=0 border=0 width=100%>
<tr>
<td>
<script>
var sAddItemLabel = '<swe:control id="AddItem" CfgUIControl="AddItem"
CfgHtmlType="CfgLabel"/>';
var sComboAddNameLabel = '<swe:control id="Name" CfgUIControl="lblName"
var sComboAddQtyLabel = '<swe:control id="Quantity" CfgUIControl="lblQuantity"
</script>
<swe:for-each id="1100" CfgLoopType="Domain" Automation="N" startValue="1000"
count="Dynamic" iteratorName="1100Id" >
<swe:control id="ComboAdd" CfgHtmlType="CfgComboAdd" ForceRefresh="Y"
CfgJSShow="showSelectAndOptions" CfgJSUpdateExclusion="updateExcludedItemForPort"
CfgJSUpdateSelection="updatePortItemsForComboAdd"/>
</swe:for-each>
</td>
</tr>
<tr>
<td colspan="3">
<swe:include file="eCfgRelationContentsPriceQuantityJS.swt"/>
</td>
</tr>
</table>
</td>
</tr>
<swe:include file="eCfgPort_FooterJS.swt"/>

4 Within Internet Explorer, navigate to Tools > Internet Options > General tab, delete all of the
temporary files and log into the Siebel application.
The following section contains information about how to install and configure ACR 508.
NOTE: If you have installed ACR 474 and ACR 508 together, using the instructions provided in
Instructions for ACR 474 and ACR 508 on page 169, do not perform the procedures in this section.
Unpacking the ACR508.zip File
Use the following procedure to unpack the ACR508.zip file.
To unzip the ACR508.zip file
1 Navigate to <Tools Install Directory>\REPPATCH.
2 Unzip the ACR508.zip file.
This will create the following directory structure.
<Path of the Unzipped Folder>\REPPATCH\ACR508\
After you have unzipped the ACR508.zip file, the ACR508 folder will have the following
subfolders:
\DMGSchemaChanges (For more information, see Applying ACR 508 Schema Changes to the
Database on page 377.)
\SeedData (For more information, see Importing Seed Data for ACR 508 on page 378.)
\SIFFiles
\WFs
\LMU
Applying ACR 508 Schema Changes to the Database
Siebel 8.0.0.8 QF3801 includes changes to the following existing tables:
S_ORDER
S_ORDER_ITEM
S_ORDER_ITEM_OM
S_ORDPART_MVMT
EIM_ORDER1
378
EIM_ORDER_ITEM
EIM_ORDER_ITEM1
EIM_PART_MVMT
The ACR508_VACR508_BaseTables.sif and ACR508_VACR508_EIMTables.sif files within the
REPPATCH\ACR508\DMGChanges directory contain these changes.
Use the following procedure to apply schema changes to the database.
To import the ACR508_ VACR508_ BaseTables.sif and
ACR508_ VACR508_ EI MTables.sif files into the repository
Table FieldService
Table Order
EIM Order
EIM FieldService
2 Use the Siebel Tools - Import from Archive function to read the ACR508_VACR508_BaseTables.sif
and ACR508_VACR508_EIMTables.sif files and create the tables in the repository. Use the merge
option while importing this file.
NOTE: You must import the files in the specified order. The ACR508_VACR508_BaseTables.sif file
must be imported before the ACR508_VACR508_EIMTables.sif file.
3 Within Siebel Tools, query for the list of tables that were imported into the repository, and click
the Apply/DDL button to apply the changes to the database.
Use the following procedure to import seed data.
To import seed data for ACR 508
a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC).
b Navigate to the System DSN tab.
c Click Add.
d Select the "Siebel Oracle90" driver (from Datadirect Technologies).
e Enter a data source name (such as DevelopmentDB).
f Enter the server name to connect to. For Oracle, enter the TNS service name that you created
to connect Siebel Tools to the database.
g Test your connection and click OK when you have verified that the connection was successful.
2 Navigate to the directory where you installed Siebel Tools and change this directory to
REPPATCH\ACR508.
NOTE: Before executing the next step, make sure that the dataimp.exe file exists in the <Tools
Directory>\REPPATCH\ACR508\SeedData\ACR508_Seed.dat /l <Tools Install
Directory>\REPPATCH\ACR508\SeedData\<Database Platform>\ACR508_Seed.inp /q -1 /w y /e
n /t n /x R /n 100 /h log
<Tools Install Directory> - Replace this with the location in which you installed Siebel Tools.
<ODBC Source Name> - Replace this with the ODBC name that you created in Step 1 of this
procedure.
<Database Platform> - Replace with this with your database platform (ORACLE, DB2UDB or
MSSQL).
5 Depending on the language that you are installing, use one of the following steps.
For ENU, run the following command after importing the ACR508_Seed.dat file.
Directory>\REPPATCH\ACR508\SeedData\ACR508_Seed_Locale_ENU.dat /l <Tools Install
Install Directory>\REPPATCH\ACR508\SeedData\<Database Platform>\
ACR508_Seed_Locale_ENU.inp /q -1 /w y /e n /t n /x R /n 100 /h log
procedure.
<Database Platform> - Replace this with your database platform (ORACLE, DB2UDB or
MSSQL).
380
For customers using languages other than ENU, run the following command after importing
ACR508_Seed.dat file to import the locale-specific ACR508_Seed_Locale_XXX.dat file, where
XXX is the language code.
Directory>\REPPATCH\ACR508\SeedData\ACR508_Seed_Locale_XXX.dat /l <Tools Install
/e y /t n /x R /n 100 /h log
procedure.
NOTE: Step 6 applies to both customers who are using ENU and customers who are using
languages other than ENU.
that the SymStrPrefix entry has been set to SBL_.
NOTE: The default setting for the SymStrPrefix entry X_, but, as noted above, this value must
be changed to SBL.
[Siebel]
..
SymStrPrefix = SBL_
..
2 Import the Web Service Integration.sif file from the SIFFiles folder into Siebel Tools using the
Tools > Import from Archive option. Use the Merge option in Import Wizard.
3 Verify that the Project "Web Service Integration" project has been created.
Order Entry
Symbolic Strings
5 Import the rest of the SIF files from the SIFFiles folder into Siebel Tools using the Tools > Import
from Archive function.
ModifiedApplets.sif
ModifiedBCs.sif
ModifiedBOs.sif
ModifiedBS.sif
ModifiedIO.sif
ModifiedLinks.sif
ModifiedPicklists.sif
ModifiedScreens.sif
ModifiedSymbStrings.sif
ModifiedView.sif
NOTE: The following step only applies for customers who are installing languages other than
ENU.
6 If you are installing languages other than ENU:
a Select > Tools > Utilities > ' Locale Management to import LMU files for your specific language
into Siebel Tools.
c Target Language = <Specific Language>
d Click on Import Tab > Browse to locate the LMU file you want to import and click Import.
7 Stop Siebel Server if it is running.
8 Within Siebel Tools, navigate to Menu > View >Options > Scripting tab and specify the following
path for the browser script compilation folder:
\\<Server IP address>\<SWE server Installed Location>\eappweb\PUBLIC\enu
9 Use the Compile Projects > All Projects option to compile the projects, and save the srf file to
the <Siebel Server Install folder>\objects\ENU\siebel_sia.srf folder on the installed Siebel
server.
382

Tools from the workflows folder. Refer to the preceding table for information about which projects
these workflows need to be imported into.
c Check the status of the workflow process. If it is In-Progress, then deploy the workflow process
to change its status to complete. Do not click the Deploy + Activate button, as doing so will yield
an error message. Only click the Deploy button.
modified workflows from the list. Just ignore the error and click Yes.
d Repeat Step b through Step c of this procedure for of all the workflows in the folder.
e Log in to the Siebel application as an administrator, and navigate to the Site Map.
f Click on Administration - Business Process.
g Navigate to Workflow Deployment > Repository Workflow Process.
h Query for the workflow processes and activate them.
12 Activate the O2C Cancel Order Validation and SWI Revise Order Validation rule sets:
a Navigate to Site Map > Administration - Data Validation > Rule Sets.
b Query for the Cancel Order Validation and SWI Revise Order Validation rule sets.
c Click Activate to activate the rule sets.
13 Navigate to Site Map > Administration - Application > Data Map Administration.
14 Query for the ReviseOrder data map object, the Header data map component, and the Back
Office Process Status data map field.
15 Check the Inactive check box to inactivate the Back Office Process Status data map field.
For more information about ACR 526 and how to implement it, from within My Oracle Support,
navigate to the Knowledge tab and search for Article ID 1296984.1.
SWISendOrder Modified Web Service Integration
SWIReviseOrderValidation New Web Service Integration
SWI Cancel Sales Order New Web Service Integration
The following section contains information about how to configure and install ACR 539.
Database Connection Lost When Updating Orders Using Web Services
CR Category: Web Services
CR Subcategory: Inbound
Product Version: Siebel 8.1.1.x Fix Pack
Change Request ID: 12-20M5K9X
Set the following parameters in the [eai_lang] section of the eapps.cfg file, which is located in the
SWEAPP_ROOT\bin directory, where SWEAPP_ROOT is the directory in which you installed the SWSE:
SessionTimeout = 300
SessionTokeTimeout = 15
SessionTokenMaxAge = 2880
SWSENoSessInPref = TRUE
Invalid Session Token Error in UpdateSalesOrderSiebelCommsProvABCSImpl Process
CR Category: EAI
CR Subcategory: Runtime
Change Request: 12-20IJC1J
The following error occurs when running the UpdateSalesOrderSiebelCommsProvABCSImpl process:
Error: Inbound SOAP Message - Session Token is missing or invalid or has expired.
Apply Siebel 8.1.1.3 QF0363.
384
Before you begin your installation, change a parameter in tools.cfg file within Siebel Tools (Original:
SymStrPrefix = X_) to SymStrPrefix = SBL_.
Repository Configurations for ACR 539
1 Navigate to REPPATCH\ACR539.zip and unzip the file to any location accessible by Siebel Tools.
LS Clinical Protocol
LS Clinical Protocol Site
LS Clinical Subject
LS Clinical Activity
Symbolic Strings
LS Clinical Investigators
Table Activity
Table Clinical
LS Clinical Enhancement
Table LifeScience
Table Sales
LS Clinical Workflow
LS Clinical Rollup
EIM Clinical
EIM Common
EIM Common SIA
NOTE: The following steps can be followed to automate the process of importing all the sif files
at once into the Siebel repository else the section from Schema Changes steps can be followed
to perform manual configuration changes into the Siebel repository.
3 Rename Unziplocation\ACR539 \REPOSITORY\import.txt to import.bat, edit the file, and change
the first four parameters related to database and Siebel Tools details with the username "Siebel
Administrator Username".
4 Create a log folder in Unziplocation\ACR539\REPOSITORY.
5 Run the import.bat file to import.
7 Apply the schema changes for the 'S_CL_PTCL_LS', 'S_EVT_ACT_LSX', 'S_PTCL_SITE_LS'
'S_TMPL_PLANITEM', 'EIM_CL_ACT_LS', 'EIM_CL_PTCL_LS', 'EIM_PTL_SITE_LS' and
'EIM_TMPL_PLNITM' tables (Refer to Schema Changes for information about how to apply the
changes.)
8 Import the Workflow Processes into Siebel Repository. See "Importing Workflow Definitions" for
more information.
Schema Changes
Use the instructions below to apply the schema changes.
REPPATCH\ ACR539\ REPOSI TORY\ Tabl es\ Tabl es. si f has all the changes for the following:
S_CL_PTCL_LS
S_EVT_ACT_LSX
S_PTCL_SITE_LS
S_TMPL_PLANITEM
EIM_TMPL_PLNITM
EIM_PTL_SITE_LS
EIM_CL_PTCL_LS
EIM_CL_ACT_LS
To import changes into the repository
1 Lockthe following projects before import:
Table Clinical
Table LifeScience
Table Sales
EIM Clinical
EIM Common
EIM Common SIA
2 Use the Import from Archive function within Siebel Tools to read the Tables.sif file and create the
tables in the repository. Use the merge option to import this file.
3 Use Siebel Tools to query for the list of tables that were imported into the repository.
4 Click Apply/DDL button to apply the changes to the physical database.
Applying Links Changes
Import Clinical Protocol Site_Clinical Protocol.sif to apply the changes.
386
Applying PickList Changes
Import PickList Clinical Protocol Site Primary Addresses.sif to apply the changes.
Applying Business Service Changes
Import LS SubjectVisits Service.sif to apply the changes.
Applying Business Components Changes
NOTE: The procedures in this section are an alternative to importing SIF files. Use the following
procedure if you want to perform manual configuration because this is an existing Business
Component and the Business Component user properties may clash with your existing Business
Component user properties.
1 Clinical Protocol
2 Clinical Protocol Site
3 Visit Template Activities
4 Action (No Owner Lock)
5 Subject Visit Templates
6 Visit Plan
7 Visit Plan Action
8 Clinical Account Investigator Role
9 Clinical Subject
1 Clinical Protocol
Update the existing Clinical Protocol business component by adding new fields as shown in the
following tables:
Project LS Clinical Protocol
Table S_CL_PTCL_LS
Single
Value
Fields
New/
Modified?
Name Column Type Calculated
Value
Text
Length
Pre
Default
New Synchronize
Active Sites
Flag
SYNC_SITES_FLG DTYPE_BOO
L
1 N
Field User Properties
Business Component User Properties
2 Clinical Protocol Site
Update the existing Clinical Protocol Site business component by adding new fields as shown in the
following tables:
Project LS Medical Product Issue
JOINS
New CDMS Study
ID
CDMS_STUDY_CODE DTYPE_TEXT 50
New Is CDMS null IIF(([CDMS
Study ID] IS
NULL), "Y",
"N")
Parent Field User Property Name Value
CDMS Study ID Text Length Override 15
Name Value
Field Read Only Field: Synchronize Active Sites Flag Is CDMS null
On Field Update Set 2 "CDMS Study ID", "Synchronize Active Sites
Flag", "N"
Project LS Clinical Protocol Site
Table S_ PTCL_SITE_LS
Table Alias Outer Join
S_USER Last Updated By
S_ADDR_PER Primary Address TRUE
S_CL_PTCL_LS S_CL_PTCL_LS TRUE
S_CL_ST_ADDR_LS S_CL_ST_ADDR_LS TRUE
Single
Value
Fields
388
Join Specification
BUSINESS COMPONENT USER PROPERTY
Parent Table Name Name Source Field Destination Column
S_USER Last Updated By Login Last Updated By ROW_ID
S_ADDR_PER Primary Addr1 Primary Address ROW_ID
S_CL_PTCL_LS Protocol Info Protocol Id Id
S_CL_ST_ADDR_LS Primary Address Row Primary Address Id ROW_ID
S_CL_ST_ADDR_LS SiteID Protocol Site Id PTCL_SITE_ID
Name Value
Field Read Only Field: Activate Synchronization Flag Require Active Flag Check
New/
Modified
? Name Join Column Type
Calculated
Value PickList
Pre
Default
New Field Activate
Synchronizat
ion Flag
ACTIVATE_
SYNC_FLG
DTYPE_BOOL N
New Field Address Line
1
Primary Address ADDR DTYPE_TEXT PickList
Clinical
Protocol
Site
Primary
Addresses
New Field Address
RowId
S_CL_ST_ADDR_LS ADDR_ORG
_ID
DTYPE_ID
New Field Address Type S_CL_ST_ADDR_LS SITE_ADDR
_TYPE
DTYPE_TEXT
New Field CDMS Site DTYPE_TEXT [Account
Id]+":"+[Ad
dress RowId]
New Field CDMS Study
Site
DTYPE_TEXT [Account
Id]+":"+[Ad
dress RowId]
New Field Description S_CL_ST_ADDR_LS DESC_TEXT DTYPE_TEXT
New Field Primary
Address Id
PR_ADDR_I
D
DTYPE_TEXT
New Field Prev CDMS
Site
AIA_INTEG
_ID
DTYPE_TEXT
New Field Primary
Address
S_CL_ST_ADDR_LS ADDR_ORG
_ID
DTYPE_ID
For the Address Line 1 field, add the following record in the Pickmap:
3 Visit Template Activities
Update the existing Visit Template Activities business component by adding new fields as shown in
the following tables:
Single Value Fields
New Field Protocol
Active Sync
Flag
S_CL_PTCL_LS SYNC_SITE
S_FLG
DTYPE_BOOL
New Field Require
Active Flag
Check
IIF(([Protoco
l Active Sync
Flag] = 'Y'
AND [Street
Address] IS
NOT NULL ),
"N", "Y")
New Field Site Last
Updated
LAST_UPD DTYPE_UTCDATETIME
New/Modified? Field Constraint Picklist Field
New Address Line 1 Address Line 1
New Address RowId Address Id
New Address Type Address Type
New Description Description
New Id Y Protocol Site Id
New Primary Address Id Id
Project LS Clinical Subject
Table S_EVT_ACT
New/
Modify Name Join Column Type
Text
Length
New
Field
Clinical Item S_EVT_ACT_LSX CLINICAL_ITEM_
VAL
DTYPE_TEXT 255
New
Field
Parent Activity
Template RowId
TEMPLATE_ID DTYPE_ID 15
New/
Modified
? Name Join Column Type
Calculated
Value PickList
Pre
Default
390
4 Action (No Owner Lock)
Update the existing Action (No Owner Lock) business component by adding new fields as shown in
5 Subject Visit Templates
Update the existing Subject Visit Templates business component by adding new fields as shown in
Single Value Fields
Project LS Clinical
Subject
Table S_EVT_ACT
New/
Modified Name Join Column Type
Text
Length
New Field Activity
Clinical Item
S_EVT_ACT_LSX CLINICAL_ITEM_VAL DTYPE_TEXT 255
New Field Visit Clinical
Item
Parent Template CLINICAL_ITEM_VAL DTYPE_TEXT 255
Table S_TMPL_PLANITEM
New/Modify Name Column Type Text Length
New Field Clinical Item CLINICAL_ITEM_VAL DTYPE_TEXT 255
6 Visit Plan
Update the existing Visit Plan business component by adding new fields as shown in the following
tables:
7 Visit Plan Action
Update the existing Visit Plan Action business component by adding new fields as shown in the
following tables:
Table S_EVT_ACT
New/
Modify Name Join Column Type
Text
Length
New Field Clinical Item Parent
Template
CLINICAL_ITEM_VAL DTYPE_TEXT 255
Modified
Field
Priority EVT_PRIORITY_CD DTYPE_TEXT 30
Table S_EVT_ACT
Table Alias Outer Join
S_EVT_ACT_LSX Clinical Item Activity TRUE
Parent Table
Name Name Source Field
Destinatio
n Column
S_EVT_ACT_LSX ClinicalItemActivity Parent Activity Template
RowId
ROW_ID
New/
Modified Name Join Column Type
Text
Length
New Field Clinical Item Clinical Item
Activity
CLINICAL_ITEM_VAL DTYPE_TEXT 255
New Field Parent Activity
Template
RowId
TEMPLATE_ID DTYPE_ID 15
392
8 Clinical Account Investigator Role
Update the existing Clinical Account Investigator Role business component by adding new fields as
shown in the following tables:
9 Clinical Subject
Update the existing Clinical Subject business component by adding new fields as shown in the
following tables:
For the ProtocolSiteId field, add the following record in the pickmap:
Project LS Clinical Investigators
Table S_PTL_ST_CON_LS
New/Modify Name Link Specification
Modified Field Site Id TRUE
Table S_CL_SUBJ_LS
New/Modified Name PickList
Modified Field Protocol Site Id LS Clinical Protocol Site Picklist
New/Modified? Field Constraint Picklist Field
New Amount Currency Code Amount Currency Code
New Amount Exchange Date Amount Exchange Date
New Investigator First Name Investigator First Name
New Investigator Id Primary Investigator Id
New Investigator Last Name Investigator Last Name
New Protocol Id Protocol Id
New Protocol Number Protocol Number
New Protocol Site Id Id
New Regions Required Flag Regions Required Flag
New Site Id Site Id
New Site Name Site Name
New Site Number Site Number
Applying Business Object Changes
Import Clinical Protocol Site New.sif to apply the changes.
NOTE: The "Integration Objects", "Workflow Policy Columns" and "Workflow Policy Objects"
contained in the SIF file are all new. These should be imported to apply the changes.
Applets
Clinical Protocol Admin Form Applet
Update the existing applet as shown below. You also must add the new controls to the Applet
Web Template.
In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout.
Clinical Protocol Form Applet
Clinical Protocol Admin Form Applet (Modify)
BusComp Clinical Protocol
New/
Modified Name String Reference Caption Field
HTML
Icon
Map HTML Type
New CDMS Study
ID
SBL_CDMS_STUDY_ID CDMS Study
ID
CDMS Study
ID
Text
New Synchronize
Active Sites
SBL_SYNC_STUDY_SITES Synchronize
Active Study
Sites
Synchronize
Active Sites
Flag
Checkbox
New Label
Integration
SBL_INTEGRATION-
1004224521-0XI
Integration FormSection
Clinical Protocol Form Applet (Modify)
BusComp Clinical Protocol
New/
Modified Name
String
Reference Caption Field
HTML
Icon
Map HTML Type
New CDMS
Study ID
SBL_CDMS
_STUDY_ID
CDMS
Study ID
CDMS
Study ID
Text
394
Clinical Protocol Site Entry Applet
New Synchronize
Active Sites
SBL_SYNC_
STUDY_SIT
ES
Synchronize
Active
Study Sites
Synchronize
Active Sites
Flag
Checkbox
New Label
Integration
SBL_INTEG
RATION-
100422452
1-0XI
Integration FormSection
Clinical Protocol Site Entry Applet (Modify)
BusComp Clinical Protocol Site
Project LS Clinical Protocol Site
New/
Modified Name
String
Reference Caption Field PickList HTML Type
New Primary Site
Address
SBL_PRIMA
Y_SITE_AD
DRESS
Primary Site
Address
Address
Line 1
PickList
Clinical
Protocol
Site Primary
Addresses
Text
New Activate for
Synchroniza
tion
SBL_ACTIV
ATE_FOR_S
YNC
Activate for
Synchroniza
tion
Activate for
Synchroniza
tion
Checkbox
New Label
Integration
SBL_INTEG
RATION-
100422452
1-0XI
Integration FormSectio
n
New/
Modified Name
String
Reference Caption Field
HTML
Icon
Map HTML Type
Clinical Visit Template Activities
Clinical Subjects Visit Templates List Applet
Clinical Visit Template Activities (Modify)
BusComp Visit Template Activities
List Columns
New /Modify Name Field String Reference
New Clinical Item Clinical Item SBL_CLINICAL_ITEM
Applet Web Template (Existing and Modify)
Name Type Web Template
Edit List Edit List Applet List (Base/Edit List)
Applet Web Template Item New
Name Control Type Comments
Clinical Item Clinical Item List Item In Edit Web Layout,
Drag and Drop this List
Column from Controls/
Columns onto the
layout
Clinical Subjects Visit Templates List Applet (Modify)
BusComp Subject Visit Templates
List Columns
New /Modify Name Field String Reference
New Clinical Item Clinical Item SBL_CLINICAL_ITEM
Applet Web Template (Existing and Modify)
Name Type Web Template
Edit List Edit List Applet List (Base/Edit List)
396
Clinical Protocol Site Primary Addresses Pick Applet (New)
Import the "Clinical Protocol Site Primary Addresses Pick Applet.sif" to apply the changes.
Symbolic Strings Changes
The following table contains details about the symbolic strings added for ACR 539.
NOTE: These symbolic strings will be imported as part ofthe SIF file import. This list is provided for
reference only.
Importing Workflow Definitions
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.
Applet Web Template
Item New
Name Control Type Comments
Clinical Item Clinical Item List Item In Edit Web Layout, drag and drop this
List Column from Controls/Columns
onto the layout
New/
Existing Name
Current
StringValue Definition
New SBL_ACTIVATE_FOR_SYNC Activate for
Synchronization
An indicator that determines
when a protocol site is ready
to be sent outbound
New SBL_CDMS_STUDY_ID CDMS Study ID The CDMS unique system
identifier for a study
New SBL_CLINICAL_ITEM Clinical Item The code used to represent
an abstract clinical entity
independent of any system
New SBL_SYNC_STUDY_SITES Synchronize Active
Study Sites
An indicator that determines
if the protocol site interface
will be used for a protocol
New SBL_PRIMAY_SITE_ADDRESS Primary Site Address Indicatges the Primary Site
Address on the Site
3 From the list applet, right-click and choose choose Import Workflow Process.
4 Browse to Unziplocation\ACR539\REPOSITORY\Workflows, choose LS ClinicalProtocolSite
Outbound - NewSite.xml .
5 After import, query for the workflow, and in Lock Projects view > Workflow process, focus on the
record and click the Publish/Activate button on top of the applet to deploy the workflows.
6 Repeat the preceding steps for the remaining new workflows.
7 For the LS Clinical - DeleteNonAppVisits Process workflow, follow the preceding steps if the you
want to directly import the Workflow or use the following procedure if you want to perform the
configurations manually.
NOTE: If you receive the "The value entered in field Process Business Object of buscomp
Workflow Process Deployment does not match any value in the bounded picklist FOW SRF
Business Object" error message while youare deploying the workflow, ignore the error message.
NOTE: The following procedures are an alternative to importing XML files. Use the following
procedure if you want to perform manual configuration because this is an existing workflow.
To update the LS Clinical - DeleteNonAppVisits Process workflow
2 Create a new version of the LS Clinical - DeleteNonAppVisits Process workflow.
3 Go to Edit mode.
4 Select the Delete Non App Visits business service.
New/
Modified XML File to Import Workflow Name Project
New LS ClinicalProtocolSite
Outbound - NewSite.xml
LS ClinicalProtocolSite
Outbound - NewSite
New LS ClinicalProtocolSite
Outbound-UpdatedSite.xml
LS ClinicalProtocolSite
Outbound-UpdatedSite
New SWI LS Clinical Subject
Inbound.xml
SWI LS Clinical Subject
Inbound
LS Clinical Subject
Inbound - Subject.xml
Inbound - Subject
LS Clinical Subject
Inbound - Activity.xml
Inbound - Activity
LS Clinical Subject
New SWI Protocol Number
Lookup.xml
SWI Protocol Number
Lookup
LS Clinical Subject
Modified LS Clinical -
DeleteNonAppVisits
Process.xml
LS Clinical -
DeleteNonAppVisits
Process
LS Clinical
Enhancement
398
5 Select Tab Input arguments in the Multivalue Property window
6 Change the property name of the Input Argument VisitTemplateDate field as detailed below:
From:
Input Argument PropertyName
VisitTemplateDateFieldName OriginalTemplateDateFieldName
To:
Input Argument PropertyName
VisitTemplateDateFieldName VisitTemplateDateFieldName
7 Add a business service BS by name "FINS Teller UI Navigation", BS Method Name
"RefreshCurrentApplet". Name the BS as "Refresh Applet".
8 Add the following property in the Multi Value Property Window:

9 Save the workflow, and then publish and activate it.
Siebel Application Changes
Use the following procedure to import Web Services definitions.
To import Web Services definitions
2 Navigate to the Administration - Web Services > Inbound Web Services view.
3 Import the ClinicalSubject.xml file. The file is located in the
Unzi pl ocat i on\ ACR539\ REPOSI TORY\ WebSer vi ces folder that you extracted from the zip file.
4 Query for the ClinicalSubject Web Service.
Input Argument Type Value
Refresh All Literal Y
ClinicalSubject.XML ClinicalSubject Inbound
5 On the Service Port applet, update the address to point to your Web server location. By default,
it looks like:
http://<webserver>/eai_<lang>/
start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&Username=<username>&Passw
ord=<password>
If you are using the Study, Subject, and Visit Synchronization Integration Pack, update the
default address as follows:
http://<webserver>/eai_<lang>/
start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute
NOTE: It is recommended that HTTPS be used as per security guidelines and the preceding
example is only an illustration. For more information on enabling HTTPS/SSL, see the Siebel
Security Guide on the Siebel Bookshelf.
6 Change the webserver to the webserver host name.
NOTE: For more information about how to configure Web Services, see Integration Platform
Technologies: Siebel Enterprise Application Integration on the Siebel Bookshelf.
Activating Workflow Definitions
Use the following procedure to activate workflow definitions.
To activate workflow definitions
1 Log into Siebel eClinical.
2 Navigate to the Administration - Business Process > Workflow Deployment view.
3 On the Repository Workflow Processes applet, query for workflows listed in the following table,
focus on each record and click the Activate button to activate the workflow.
NOTE: If you encounter the "The value entered in field Process Business Object of buscomp Workflow
Process Deployment does not match any value in the bounded picklist FOW SRF Business Object"
error message when you are deploying the workfklow, ignore this error message.
Workflow Name
LS ClinicalProtocolSite Outbound - NewSite
LS ClinicalProtocolSite Outbound-UpdatedSite
SWI LS Clinical Subject Inbound
SWI LS Clinical Subject Inbound - Subject
SWI LS Clinical Subject Inbound - Activity
SWI - Protocol Number Lookup
LS Clinical - DeleteNonAppVisits Process
400
Seed Data
To import seed data
a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC).
b Navigate to the System DSN tab and click Add.
c Pick the "Siebel Oracle90" driver (from Datadirect Technologies).
d Enter a data source name (such as DevelopmentDB).
e Enter the server name to connect to.
database.
f Test your connection and click OK when tested successfully.
2 Navigate to the directory in which you installed Siebel Tools and change the directory to
REPATCH\ACR539.
NOTE: Before you execute the next step, make sure that the dataimp.exe file exists in the <Tools
Use the following procedure to edit and import seed data.
To edit and import seed data
1 Rename Unziplocation\ACR539\SEED_DATA\Import_Seed_Data.txt to import_Seed_Data.bat,
edit the file, and change the first six parameters related to the application database and Siebel
Tools path details.
For example:
SET SCOCPATH=D:\Siebel\8.1\Tools_2
SET DBFOLDER=D:\Siebel\8.1\Tools_2\REPPATCH\ACR539\SEED_DATA\ORACLE
SET SCOCDATASRC=<DB data source name>
SET SCOCTBLOWNER=<DB table owner name>
SET SCOCUSERNAME=<Siebel Admin user name>
SET SCOCPASSWORD=<Siebel Admin password>
2 Run the Import_Seed_Data.bat file to import seed data.
NOTE: It is recommended that you remove the Import_Seed_Data.bat file after installation, as
this file contains sensitive information.
4 If you are installing languages other than ENU, perform the following steps:
a Run the following command after importing ACR539_Seed.dat file for importing the locale
specific ACR539_Seed_Locale_XXX.dat, where XXX is the language code.
<Tool s I nst al l Di r ect or y>\ bi n\ dat ai mp / u <USERNAME> / p <PASSWORD> / f <Tool s
I nst al l Di r ect or y>\ REPATCH\ ACR539\ SeedDat a\ XXX\ ACR539_Seed_Local e_XXX. dat / l
<Tool s I nst al l Di r ect or y>\ t emp\ dat ai mp_seed. l og / c <ODBC Sour ce Name> / d <Tabl e
Owner > / q - 1 / w n / e y / t n / x R / n 100 / h l og
<Tools Install Directory> - Replace with your Siebel Tools install directory.
<ODBC Source Name> - Replace with the ODBC name created in Step 1 of the previous
procedure.
Process for the Workflow Policies and Regenerating the Triggers on
the Database
Enabling Siebel Workflow Policies
Updating Clinical Related Workflow Policies for Non-ENU Builds
Generating Triggers
Starting the Workflow Monitor Agent
Enabling Siebel Workflow Policies
You must enable Siebel Workflow Policies before using any one of the modules that require them.
However, if you are using more than one of these modules, you only need to enable Workflow Policies
once.
To enable Siebel Workflow Policies
1 Navigate to the Administration - Server Configuration screen > Enterprises view.
2 In the Component Groups list, query for the record that contains Workflow Management, and
select it.
3 In the Component Groups list, click Menu and choose Enable Component Group.
4 Click the Synchronize view tab.
5 Click Synchronize.
The components populate the Batch Components list.
NOTE: After enabling workflow policies, you may need to restart the server.
Updating Clinical Related Workflow Policies for Non-ENU Builds
NOTE: You do not need to perform this procedure if you are deploying ENU.
402
To update workflow policies for languages other than ENU
1 Navigate to Site Map > Administration - Business Process > Workflow Policies.
2 In Policies List, query in the Policy Group field.
3 Modify the policies in the "Conditions List Applet" for the ([Condition Field] = "LS Clinical Site No
Subject Flag" or "LS Clinical Site No Subject Flag") the [Value] to the ENU equivalent (either Y
or N).
Generating Triggers
You must generate triggers before using any one of the modules requiring Workflow Policies, and
again whenever new policies are created or deleted. You do not need to regenerate triggers in order
to use additional modules that require workflow policies.
The Generate Trigger (GenTrig) component on the Siebel Server allows you to create database
triggers. Policy Manager uses these database triggers to identify which records may match policy
conditions. You must regenerate triggers whenever new policies are created or deleted.
To generate triggers in Siebel Workflow Policies
1 Navigate to the Administration - Server Management screen > Jobs view.
2 In the Batch Jobs List view, click New.
3 In the Component/Job field, select Generate Triggers.
This creates a new line entry but does not start the task.
4 In the Job Parameters list, click New and complete the fields in the following order:
Name: Click the name field select button to query for and select the EXEC record.
Value: Type True.
5 In the Job Parameter list, click New.
6 In the Job Parameter list, click the name field select button to query for and select the Privilege
User password record ), and click OK.
7 Enter the Table Owner In the Value field.
8 In the Job Parameter list, click New.
9 In the Job Parameter list, click the name field select button to query for and select the Privilege
User record, and click OK.
10 Enter the Table Owner in the Value field.
11 In the Job Detail form applet, click Menu and choose Start Job.
12 In the Batch Jobs List view, click Menu and choose Run Query.
Starting the Workflow Monitor Agent
You need to start Workflow Monitor Agent to execute your policies. Workflow Monitor Agent checks
to see when the conditions of policies are met.
NOTE: You must use a command prompt to start Workflow Monitor Agent. You cannot start it from
the application.
To start Workflow Monitor Agent
1 Open a DOS command prompt, navigate to siebsrvr\bin folder where the server is installed, and
execute the following command:
Sr vr mgr / e <Ent er pr i se name> / s <si ebel ser ver name> / g <gat eway name
ser ver > / u <sadmi n> / p <passwor d>
2 Start the task for the Workflow Monitor Agent component, using the following command:
srvrmgr> start task for comp workmon with tableownpass='<the table owner's name
>',Actionagent='false',Groupname='LS Clinical Rollup'
3 Within the application, navigate to the Administration - Server Management screen > Tasks >
Parameters view.
4 In the Server Task list applet, within the Component field, query for Workflow Monitor Agent.
5 In the Server Task-Parameter list applet, within the Parameter field, query for Action interval ,and
change the value from the default value (3600, which means 3600 seconds) to a lower value.
Enabling Component Groups
Make sure that the EAI and Workflow component groups are enabled. If they are not, enable them
and bounce the Siebel Server.
Configuring the Siebel Application to Write to the JMS Queue on the
SOA Server 10g
1 Download oc4j_extended_101330.zip from download.oracle.com
2 Extract oc4j-extended.zip to a folder in a machine where the siebel server is installed (such as
D:\JMS folder).
3 Copy Siebel.jar and SiebelJI_enu to D:\JMS folder (these jar files can be found in the Siebel
install directory).
4 Copy jndi.jar to D:\JMS\j2ee\home\lib folder. This file is located on the SOA server under
<SOA_HOME>/datadirect/sun/lib.
5 Copy "com/evermind/util/JCAProperties.class" from the oc4j-internal.jar file to the D:\JMS
folder. When you extract the file, check the folders to make sure that JCAProperties.class is
created under D:\JMS\com\evermind\util\ and not under D:\JMS.
6 Create a file called 'jndi.properties' with the following details in the D:\JMS path:
404
java.naming.provider.url=opmn:ormi://<IP Address of the FMW server>:<Posrt
No>:oc4j_soa
For example:
java.naming.provider.url=opmn:ormi://adc60120fems.us.oracle.com:6009:oc4j_soa
java.naming.security.principal=sadmin
NOTE: Make sure that there are no trailing spaces at the end of any of the lines in the
jndi.properties file.
7 Create a Named Subsystem in the Siebel application through the server management, and
connect to the server manager from the command prompt from the bin directory of the Siebel
installed folder with the following command:
Srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u <userid> /p
<password>
8 Run the following command to create the named subsystem and add the jar file into the class
path:
DLL=C: \ Sun\ SDK\ j dk\ j r e\ bi n\ ser ver \ j vm. dl l , CLASSPATH =
D: \ J MS; D: \ J MS\ Si ebel . j ar ; D: \ J MS\ Si ebel J I _enu. j ar ; D: \ J MS\ j 2ee\ home\ l i b\ admi ncl i e
nt . j ar ; D: \ J MS\ j 2ee\ home\ l i b\ j ndi . j ar ; D: \ J MS\ j 2ee\ home\ l i b\ j t a. j ar ; D: \ J MS\ j 2ee\ h
ome\ oc4j cl i ent . j ar ; D: \ J MS\ j 2ee\ home\ l i b\ bcel . j ar ; D: \ J MS\ j 2ee\ home\ l i b\ j ms. j ar ; D
: \ J MS\ j 2ee\ home\ l i b\ j avax77. j ar ; D: \ J MS\ j dbc\ l i b\ oj dbc14dms. j ar ; D: \ J MS\ l i b\ dms. j
ar ; D: \ J MS\ opmn\ l i b\ opt i c. j ar ; D: \ J MS\ j 2ee\ home\ l i b\ ej b. j ar ; . , VMOPTI ONS=
D: \ J MS\ l og\ j ms. l og
9 Log into the Siebel application, and navigate to Site Map > Administration Server Configuration
> Profile Configuration.
a Query for the profile with Alias Name 'JAVA' in the profile list and make sure that the parameters
are correct.
b Edit the value of VMOPTIONS to -Djms.log=D:\JMS\log\jms.log.
11 On the SOA server, log into Enterprise Manager and create a user called sadmin that is part of
the user role. For information about how to create the users, see the Enterprise Manager
documentation.
12 Log into the Siebel application and navigate to Site Map > Administration - Business Service >
Simulator.
13 Click New and provide the following parameters:
Service Name = EAI JMS Transport
Method Name = CheckClasspath
14 Change the Method Name to CheckJNDIContext with the following input arguments in the
home\lib folder.
SendUsername = sadmin
SendPassword = <put password for sadmin user created in Enterprise Manager>
ConnectionFactory = java:comp/resource/UpdateClinicalStudySEBLRP/
QueueConnectionFactories/QCF
SendQueue = java:comp/resource/UpdateClinicalStudySEBLRP/Queues/
AIA_CLINICALSTUDYQ
15 Change the method nme to Send.
16 Log into Siebel Tools and click on Workflow Processes.
17 Query for the workflow process: LS ClinicalProtocolSite Outbound - NewSite workflow process,
and do the following:
a Click Revise.
b Choose Edit Workflow Process.
c Choose Send to Queue.
d Click on Input Arguments.
e Change SendUserName to sadmin.
f Change SendPassword to the password created for the sadmin user on the SOA Server in
Enterprise Manager.
g Save the workflow process.
h Activate and publish the workflow.
18 Perform Step a through Step h for the LS ClinicalProtocolSite Outbound-UpdatedSite workflow
process.
19 Log into the Siebel application and navigate to Administration - Business Processes.
20 Click on Workflow Deployment.
21 Query for the LS ClinicalProtocolSite Outbound - NewSite workflow and click the Activate button.
22 Query for the LS ClinicalProtocolSite Outbound-UpdatedSite workflow and click the Activate
button.
24 Query for the LS ClinicalProtocolSite Outbound - NewSite workflow process, and do the following:
a Click on Revise.
c Choose Send to Queue.
d Click on Input Arguments.
e Change SendUserName to sadmin.
406
f Change SendPassword to the password created for the sadmin user on the SOA Server in
Enterprise Manager.
h Activate and publish the workflow.
25 Perform Step a through Step h for the LS ClinicalProtocolSite Outbound-UpdatedSite workflow
process.
27 Click on Workflow Deployment.
28 Query for the LS ClinicalProtocolSite Outbound - NewSite workflow and click the Activate button.
29 Query for the LS ClinicalProtocolSite Outbound-UpdatedSite workflow and click the Activate
button.
Configuring Siebel to Write to the JMS Queue on the Weblogic
Application Server 11g
NOTE: The following instructions provide an example that is based on the Oracle Study, Subject, and
Visit Synchronization Integration Pack. The Queue Name, user details and other configuration details
are dependent on the JMS Queue Configuration on the Weblogic server. Also, this procedure assumes
that you have already installed and configured the Weblogic Server 11g.
1 Create a folder called D:\WLSJMS on the Siebel machine.
2 Create a folder called log in the D:\WLSJMS directory.
3 Copy Siebel.jar and SiebelJI_enu.jar to the D:\WLSJMS folder (these jar files can be found inthe
Siebel install directory).
4 Generate the wlfullclient.jar file:
a Connect to Weblogic Application Server, and generate wlfullclient.jar. For more information about
how to do this, see http://download.oracle.com/docs/cd/E12840_01/wls/docs103/client/
jarbuilder.html.
b Copy the jar to D:\WLSJMS on Siebel Server.
5 Create a file called 'jndi.properties' in the D:\WLSJMS directory and copy the following contents:
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://<host IP address>:<port>
NOTE: <hostIP address>: This should be the IP address of Weblogic Application Server.
<port>:is the port at which the Web server instance is listening/configured for connections. Also,
make sure that there are no trailing spaces at the end of any of the lines in the jndi.properties
file.
6 Create a Named Subsystem in the Siebel application through the Server Manager, and connect
to the server manager from the command prompt from the bin directory of the Siebel installed
folder.
a Enter the following command:
Srvrmgr /g <gatewayserver> /e <enterprise server> /s <Siebel server> /u <userid> /p
<password> Eg. srvrmgr /g sdc78198svqe:4330 /e siebel /s sdc78198svqe /u sadmin /p
sadmin
b Run the following command to create the named subsystem and add the jar file into the class
path:
create named subsystem JAVA for subsystem JVMSubSys with DLL=
D:\Siebel\8.1\Tools_1\jdk\jre\bin\server\jvm.dll,CLASSPATH=D:\WLSJMS;D:\WLSJMS\Sieb
el.jar;D:\WLSJMS\SiebelJI_enu.jar;D:\WLSJMS\wlfullclient.jar;.,VMOPTIONS=D:\WLSJMS\l
og\jms.log
c Run the following command to create the named JMS subsystem:
create named subsystem JMSParameters_study for subsystem JMSSubsys with
ConnectionFactory=" jms/aia/AIA_SiebelClinical_ClinicalStudyJMSQueueCF", SendQueue="
jms/aia/AIA_SiebelClinical_ClinicalStudyJMSQueue"
7 Log into the Siebel application, navigate to Site Map > Administration Server Configuration >
Profile Configuration, and perform the following steps:
a Query for the pofile with Alias Name 'JAVA' in the profile list and make sure that the parameters
are correct.
b Edit the value of VMOPTIONS to -Djms.log=D:\WLSJMS\log\jms.log.
c Query for the profile with Alias Name 'JMSParameters_study' in the profile list.
d Set the value of 'SendUsername' to the weblogic server user name.
e Set the value of 'SendPassword' to the weblogic server password.
NOTE: The Weblogic server user needs to have minimum privilege to access the queue ("jms/
aia/AIA_SiebelClinical_ClinicalStudyJMSQueue").
The password is stored as encrypted in the database and is displayed with asterisks in the UI
once the record is saved and refreshed.
9 Log into the Siebel application, and navigate to Site Map > Administration - Business Service >
Simulator.
10 Click New and provide the following parameters:
Service Name = EAI JMS Transport
Method Name = CheckClasspath
11 Click Run to verify.
12 Change the Method Name to CheckJNDIContext with the following input arguments:
SendUsername = <Weblogic user name>
SendPassword = <weblogic password >
ConnectionFactory = jms/aia/AIA_SiebelClinical_ClinicalStudyJMSQueueCF
408
SendQueue = jms/aia/AIA_SiebelClinical_ClinicalStudyJMSQueue
13 Click Run to verify.
14 Change the Method Name to Send, use the same input arguments as in Step 11, and click Run
to verify.
16 Query for the LS ClinicalProtocolSite Outbound - NewSite workflow process, and do the following:
a Click Revise.
c Select the Send to Queue workflow step.
d Click Input Arguments.
e Create a new argument called "ConnectionSubsystem" with value "JMSParameters_study"
f Delete the SendUserName, SendPassword, ConnectionFactory, and SendQueue parameters.
h Activate and publish it.
17 Follow Step 16a through Step 16h for the LS ClinicalProtocolSite Outbound-UpdatedSite workflow
process.
19 Click Workflow Deployment.
20 Query for the LS ClinicalProtocolSite Outbound - NewSite workflow and click Activate.
21 Query for the LS ClinicalProtocolSite Outbound-UpdatedSite workflow and click Activate.
Use the instructions in this topic to implement ACR 543. It includes the following topics:
About ACR 543 on page 409
Requirements for ACR 543 on page 409
Applying ACR 543 on page 410
Importing Archive Files for ACR 543 on page 410
About ACR 543
ACR 543 implements Siebel Application Integration for Oracle Fusion Middleware. SAI for Oracle
Fusion Middleware provides a new integration capability between Siebel Business Applications and
the Oracle WebLogic Server. Within the Oracle WebLogic Server, either independently or as part of
Oracle Fusion Middleware, SAI for Oracle Fusion Middleware provides a distinct container for hosting
Web services and building Java applications. This initial release of SAI for Oracle Fusion Middleware
supports the deployment of Siebel RESTful Services to the Oracle WebLogic Server. Siebel RESTful
Services (Representational State Transfer) are a set of Java EE (Java Enterprise Edition) services that
make available an instance of a Siebel Repository or a Siebel Enterprise instance to a connected
application or data management system.
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
Requirements for ACR 543
Before deploying SAI for Oracle Fusion Middleware, make sure the following products are installed
and properly configured:
Siebel CRM version 8.1.1.x or later
Some of the requirements include:
Siebel Gateway Server
Siebel Server (or servers)
Siebel Tools
For installation instructions, see Siebel Installation Guide for the operating system you are using.
Oracle WebLogic Server 11g Release 1 (10.3.3) or later
Download it from Oracle Technology Network at:
http://www.oracle.com
NOTE: When installing this server, a basic WebLogic Server Domain is sufficient. Additionally,
make sure to choose Sun JDK when prompted; this is a requirement for Siebel RESTful Services.
For more information on installing the Oracle WebLogic Server, see Oracle Fusion Middleware
Installation Guide for Oracle WebLogic Server on Oracle Technology Network.
Oracle JDeveloper 11g (11.1.1.2.0 or later)
Download it from Oracle Technology Network:
http://www.oracle.com/
For information about installing Oracle JDeveloper, see Installation Guide for Oracle JDeveloper
in the Oracle Fusion Middleware Documentation Library 11g Release 1.
410
Applying ACR 543
1 Install the latest Siebel CRM Fix Pack 8.1.1.4.
2 Make sure the following Siebel Server components are enabled:
Siebel Application Object Manager, for example, Call Center Object Manager (ENU)
EAI Object Manager (ENU)
Importing Archive Files for ACR 543
1 Stop the Siebel Server (or servers).
2 On the computer where you installed Siebel Tools, locate the following ZIP files in the
SI EBEL_TOOLS_ROOT\ REPPATCH directory:
ACR543.zip
ACR543_BaseIO_HOR.zip
ACR543_BaseIO_SIA.zip
3 Extract the archive files (.sif) from ACR543.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: SI EBEL_TOOLS_ROOT\ bi n\ enu.
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.
EAI Business Services
Server Components - Infrastructure
Server Components - EAI
SAI EAI Outbound Services
SAI Base Integration Objects
indicating which object or project you must lock. In such a case, lock the project or object, and
7 Using the Import from Archive(s) menu item, import the following .sif archive files you previously
extracted into Siebel Tools:
00Phoenix.sif
CSSEAIJCAService.sif
CSSIOCreationService.sif
DynamicIOCreationService.sif
EAI JCA Service.sif
EAI_Outbound_Siebel_Side_Changes.sif
EAISubsys.sif
InfraNameServer.sif
SAI EAI Outbound Services.sif
ServerMgr_ARN _ParameterRemoved.sif
ServerMgrSubsys.sif
8 Log out of Siebel Tools.
9 Extract the archive (.sif) files from the appropriate ZIP file to a folder.
ACR543_BaseIO_HOR.zip. This archive file provides base integration objects for Siebel
Industry Applications.
ACR543_BaseIO_SIA.zip. This archive file provides base integration objects for Siebel
Cross-Industry Applications.
10 Run the following command from the SI EBEL_TOOLS_ROOT\ t ool s\ bi n directory to import the
preconfigured base integration objects:
NOTE: This process can take some time; wait until the process completes.
si ebdev. exe / c t ool s. cf g / d sampl e / u sadmi n / p sadmi n / bat chi mpor t " r eposi t or y
name" mer ge di r ect or y_name i mpor t . l og
where:
/c is the configuration file name and location
/d is the data source to use
/u is the username
/p is the password
repository name is the repository you want to use (the default is Siebel Repository)
di r ect or y_name is the directory to which you extracted the base integration objects in Step 9
import.log writes the data to a log file in the SI EBEL_TOOLS_ROOT\ t ool s\ bi n directory
11 Compile the changes into an updated repository file (SRF), and then copy the new SRF file to the
Siebel Server installation directory, under SI EBSRVR_ROOT\ obj ect s\ enu.
You are now ready to deploy SAI for Oracle Fusion Middleware. For more information, see Siebel
Application Integration for Oracle Fusion Middleware Guide.
412
The following sections contain information about how to configure ACR 562, as well as repository
changes that you need to make to implement this ACR. The section also contains information about
how to resolve some known issues or problems that have been encountered, as well as a workaround
procedure that you must perform within the Accessibility Applet Attributes List Applet and the
Accessibility Applet Attributes Form Applet.
1 After you have installed the Siebel 8.1.1.x Fix Pack, perform the following steps:
a Copy the Siebel_Enterprise_Server folder into the local machine.
(This is the Siebel image folder created using the Siebel Image Creator utility.)
b Change the value of OverWriteConfig=Yes in the following files:
c Append the following accessibility files information in the Siebel_Enterprise_Server/siebel.ini
file, under [DeleteFiles.Windows]:
File2 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletActivityGanttChart.swt
File3 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletAdvancedSearch.swt
File4 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletBottomStd.swt
File5 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletCalendarDaily.swt
File6 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletCalendarDailyPortal.swt
File7 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletCalendarMonthly.swt
File8 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletCalendarService.swt
File9 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletCalendarWeekly.swt
File10 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletChart.swt
File11 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletChartTOC.swt
File12 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletDashboard.swt
File13 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFind.swt
File14 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm1Col_B_E_N.swt
File15 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm1ColLight_B_E_N.swt
File16 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4Col_B.swt
File17 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4Col_E_N.swt
File18 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormPlain.swt
File19 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormSearchTop.swt
File20 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletGanttChart.swt
File21 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletHead.swt
File22 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletItemsDisplayed.swt
File23 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletLayoutControls.swt
File24 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletList_B_EL.swt
File25 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletList_E_N_Q.swt
File26 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListBasicHeaderless.swt
File27 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListInverted.swt
File28 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListMessage.swt
File29 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListPortal.swt
File30 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListPortalGraphical.swt
File31 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListPortalHeaderless.swt
414
File32 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListSearchResults.swt
File33 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListTitleless.swt
File34 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListTotals_B_EL.swt
File35 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSalutation.swt
File36 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSalutationGraphical.swt
File37 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletScreenLinks.swt
File38 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSearchAdvanced.swt
File39 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSearchBasic.swt
File40 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSearchFind.swt
File41 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSendEmailPick.swt
File42 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSendMail.swt
File43 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletSpellCheck.swt
File44 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletTail.swt
File45 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletTree.swt
File46 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletTree2.swt
File47 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletTreeMarketing.swt
File48 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCBottomApplet.swt
File49 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCCalendarAppletTitleGraphical.swt
File50 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCCalendarMonthly_weekday.swt
File51 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCCalendarMonthly_weekend.swt
File52 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCChartBasic.swt
File53 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCError.swt
File54 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCForm1ColBody.swt
File55 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCForm1ColBodyLight.swt
File56 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCForm4ColBody.swt
File57 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormBaseTitle.swt
File58 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormBody.swt
File59 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormButtonsBottom.swt
File60 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormButtonsTop.swt
File61 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormEditTitle.swt
File62 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormSearch.swt
File63 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFrameBanner.swt
File64 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFrameViewbar.swt
File65 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCGanttAppletTitle.swt
File66 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCLayoutButtons.swt
File67 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCList4ColBody.swt
File68 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListBody.swt
File69 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListBodyBullet.swt
File70 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListBodyInverted.swt
File71 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListBodyNoRowHilite.swt
File72 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListBodyTotals.swt
File73 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListBodyTotalsNoRowHilite.swt
File74 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListButtonsTop.swt
File75 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListButtonsTopNoRecNav.swt
File76 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListHeader.swt
File77 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListHeaderNoSort.swt
File78 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListHeaderTotals.swt
File79 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListTitle.swt
File80 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListTitlePortal.swt
File81 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListTitlePortalGraphical.swt
File82 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPageContainer_NoFrames.swt
File83 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupButtonsBottom.swt
File84 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupForm.swt
File85 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupList.swt
File86 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupQuery.swt
File87 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCRuleEditInsertionList.swt
File88 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCRuleEditStatement.swt
File89 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCScreenbar_Tabs.swt
File90 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCScreenLinks.swt
File91 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSendSMS.swt
File92 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSiteMap.swt
File93 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSmartScriptPlayerApplet.swt
416
File94 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSubViewbar_Drop.swt
File95 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSubViewbar_Tabs.swt
File96 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCThreadbar.swt
File97 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTogglebar_drop.swt
File98 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTogglebar_drop2.swt
File99 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTogglebar_Tabs.swt
File100 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_1Over2Over1.swt
File101 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_25_50_25.swt
File102 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_25_75.swt
File103 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_25_75_Framed.swt
File104 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_25_75_Framed2.swt
File108 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_Search.swt
File109 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewAdmin1.swt
File110 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewbar_Tabs.swt
File111 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewbarAll_Tabs.swt
File112 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewBasic.swt
File113 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewCatalog.swt
File114 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail.swt
File115 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail2.swt
File116 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail2_ParentPntr.swt
File117 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail3.swt
File118 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail3MultiChild.swt
File119 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail_GrndchldIndnt.swt
File120 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail_ParentPntr.swt
File121 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetailMultiChild.swt
File122 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewTree.swt
File123 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewTree2.swt
File124 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletForm1Col.swt
File125 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletForm2Col.swt
File126 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletForm4ColMerged_B_E_N.swt
File127 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletFormBase1Col.swt
File128 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletFormBase2Col.swt
File129 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletFormBasic.swt
File130 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletFormItemDetail.swt
File131 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletLicenseBase1Col.swt
File132 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletLinks.swt
File133 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletLinks2.swt
File134 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletLinksBorder.swt
File135 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletLinksNoTitle.swt
File136 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListBriefBullet.swt
File137 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListBriefBulletBorder.swt
File138 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListBriefBulletShaded.swt
File139 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListBriefImgBullet.swt
File140 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListBriefImgBullet2.swt
File141 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListBriefImgBulletBorder.swt
File142 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListBriefImgBulletShaded.swt
File143 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListCategorizedBullet.swt
File144 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListCategorizedBulletTab.swt
File145 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListCategorizedTab.swt
File146 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListCategorizedTOC.swt
File147 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListDetailedImgBullet.swt
File148 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListDetailedImgBulletRecNav2.swt
File149 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListDetailedImgBulletRecNav.swt
File150 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListHorizontal.swt
File151 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListLight.swt
File152 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListMerged_B_EL.swt
File153 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListMessage.swt
File154 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListSearchResults.swt
File155 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListSubCategory_1PerRow.swt
418
File156 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListSubCategory_4PerColumn.swt
File157 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListSubCategory_6PerColumn.swt
File158 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListSubCategoryIndented.swt
File159 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListTabbed.swt
File160 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletPSearchHead.swt
File161 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletPSearchTail.swt
File162 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletSearchAdvanced.swt
File163 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletSearchBasic.swt
File164 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletSearchFind.swt
File165 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletSearchTop.swt
File166 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCForm1Col.swt
File167 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCForm2Col.swt
File168 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCForm4ColBody.swt
File169 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormButtonsBottom.swt
File170 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormButtonsTopWithTitle.swt
File171 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormItemDetail.swt
File172 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormSearch.swt
File173 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormTotals.swt
File174 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFrameBanner.swt
File175 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFrameScreenbar.swt
File176 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFrameViewbar.swt
File177 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFrameViewbar_Hybrid.swt
File178 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyBullet.swt
File179 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyHorizontal.swt
File180 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyImgBullet.swt
File181 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyImgBulletDetailed.swt
File182 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyImgBulletDetailed2.swt
File183 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListButtonsTopWithTitle.swt
File184 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListCategorized.swt
File185 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListHeader.swt
File186 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListTitle.swt
File187 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListTitleNoRule.swt
File188 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCPageContainer.swt
File189 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCPageContainer_NoFrames.swt
File190 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCScreenbar_Tabs.swt
File191 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCSubViewbar_Drop.swt
File192 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCSubViewbar_Tabs.swt
File193 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCTogglebar_Tabs.swt
File194 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_100_66_33_100.swt
File195 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_25_50_25.swt
File196 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_25_75.swt
File197 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_25_75_Framed.swt
File201 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_Basic.swt
File202 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCViewAdmin1.swt
File203 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCViewbar_Tabs.swt
File204 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCViewDetail.swt
File205 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCViewDetail2.swt
File206 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCViewDetailMultiChild.swt
File207 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAttributeComboBox.swt
File208 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAttributeList.swt
File209 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgBasketBox.swt
File210 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgClassNode.swt
File211 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCompAttributeEdit.swt
File212 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNav.swt
File213 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNav_UiPicker.swt
File214 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavAttributes.swt
File215 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavClasses.swt
File216 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavConnectedProducts.swt
File217 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavLinks.swt
420
File218 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavRelationships.swt
File219 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavResources.swt
File220 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgLinkedItem.swt
File221 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_Status_Conflict.swt
File222 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_Status_Error_Info.swt
File223 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgPort_Header.swt
File224 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgResource.swt
File225 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgSaveFavoritesPopup.swt
File226 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgTabBasket.swt
File227 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgView_Decorations.swt
File228 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCollabAckApplet.swt
File229 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCollabHiddenApplet.swt
File230 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespAppletInboundMsg.swt
File231 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespAppletOutboundMsg.swt
File232 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespFormButtonsBottom.swt
File233 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespFormInBound.swt
File234 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespFormOutBound.swt
File235 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalAppletEdit.swt
File236 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalAppletFormBasic.swt
File237 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalAppletListTinyHeaderless.swt
File238 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalAppletTitle.swt
File239 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalBriefingHeaderApplet.swt
File240 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalCalendarAppletTitle.swt
File241 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalCalendarDaily.swt
File242 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalCompanySearchFormApplet.swt
File243 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalDeptSectionsApplet.swt
File244 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalDeptView.swt
File245 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalEmbeddedContainerPage.swt
File246 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalError.swt
File247 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalFullListApplet.swt
File248 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalHomeView.swt
File249 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalLinkListApplet.swt
File250 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalLitListApplet.swt
File251 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalNavBarApplet.swt
File252 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalPageContainer.swt
File253 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalQuickPicksApplet.swt
File254 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalSearchApplet.swt
File255 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalSimpleListApplet.swt
File256 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalSplashApplet.swt
File257 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalTickerSearchFormApplet.swt
File258 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalTOCApplet.swt
File259 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalTopUrlApplet.swt
File260 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalURLApplet.swt
File261 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalWeatherSearchFormApplet.swt
File262 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eSalesAppletFormItemDetail.swt
File263 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eSalesConfigApplet10.swt
File264 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eSalesView_100_25_75_100.swt
File265 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eServiceNewButtonApplet.swt
File266 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eWirelessPageTabLayoutEdit.swt
File267 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ICAppletList.swt
File268 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ICAppletListCategorizedBulletTab.swt
File269 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ICCurrentCategoryApplet.swt
File270 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ICListCategorized.swt
File271 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SIAppletTitle.swt
File272 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SIBriefingHeaderApplet.swt
File273 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SIBriefingListApplet.swt
File274 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SIBriefingView.swt
File275 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SILinkListApplet.swt
File276 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SIMyBriefingView.swt
File277 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SIPlainApplet.swt
File278 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SISalutationApplet.swt
File279 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SISwoopTitle.swt
422
File280 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SISynchronizeApplet.swt
File281 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SITOCApplet.swt
File282 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SITrackingProfileHeaderApplet.swt
File283 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SITrackingProfileReviewView.swt
File284 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SIUrlApplet.swt
File285 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SWELogin.swt
File286 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ToolsForm.swt
File287 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ToolsList.swt
File288 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ToolsUnmapped.swt
File289 = $(SiebelRoot)\siebsrvr\WEBTEMPL\TrainingTestApplet.swt
File290 = $(SiebelRoot)\siebsrvr\WEBTEMPL\TrainingTestResultApplet.swt
File291 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCCalendarAppletTitle.swt
File292 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewSegmentDetail.swt
File293 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDashboard.swt
File294 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_GlobalSignal.swt
File295 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletGanttChartPortal.swt
File296 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCLayoutTitlePortal.swt
File297 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgBaseAutoReprice.swt
File298 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgBaseManualReprice.swt
File299 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgClassNodeNoPick.swt
File300 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlCheck.swt
File301 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlCheckPrice.swt
File302 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlCombo.swt
File303 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboAdd.swt
File304 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboAddPrice.swt
File305 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlQuantity.swt
File306 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlQuantityPrice.swt
File307 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlRadio.swt
File308 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlRadioPrice.swt
File309 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgGroupStandard.swt
File310 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgGroupSummary.swt
File311 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductRawMode.swt
File312 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductSingle.swt
File313 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductTabs.swt
File314 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductWizard.swt
File315 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewAdmin1_GrndchldIndnt.swt
File316 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail2_GrndchldIndnt.swt
File317 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail3_GrndchldIndnt.swt
File318 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail3_ParentPntr.swt
File319 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletSearchAdvancedTabbed.swt
File320 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyImgBullet2.swt
File321 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eAuctionAppletPlaceBid.swt
File322 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlAttributeText.swt
File323 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboPrice.swt
File324 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboPriceQuantity.swt
File325 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboQuantity.swt
File326 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgRelationContentsPriceQuantity.swt
File327 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgRelationContentsQuantity.swt
File328 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgRelationRawCombo.swt
File329 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgViewBasic.swt
File330 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormButtonsTopNoRecNav.swt
File331 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eWirelessPageTabLayt4ColBody.swt
File332 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCApplet_NamedSpacer.swt
File333 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCApplet_Spacer.swt
File334 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_25_50_25_home.swt
File335 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4Col_NoRecNav.swt
File336 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormWizard.swt
File337 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTitle.swt
File338 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTitle_Mapped.swt
File339 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTitle_Portal.swt
File340 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTitle_PortalGraphical.swt
File341 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormButtonsTop.swt
424
File342 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListButtonsTop.swt
File343 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCTitle_Mapped.swt
File344 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCTitle_Portal.swt
File345 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_DetailExplanation.swt
File346 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_GlobalDetailExpl.swt
File347 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgPopupFrameContainer.swt
File348 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAttributeRadio.swt
File349 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListCategorizedNoTab.swt
File350 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyNoRowHilite.swt
File351 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyTotalsNoRowHilite.swt
File352 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListHeaderTotals.swt
File353 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCTitle_RecNav.swt
File354 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMViewBasic.swt
File355 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletForm4Col_B_TglBar.swt
File356 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletList_B_EL_TglBar.swt
File357 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletList_E_N_Q_TglBar.swt
File358 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMFormButtonsTop_TglBar.swt
File359 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMListButtonsTop_TglBar.swt
File360 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMViewBasic_TglBar.swt
File361 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMViewTree.swt
File362 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewTree_33_66.swt
File363 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletRealtimeCart.swt
File364 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletSalutationGraphical.swt
File365 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCLogout.swt
File366 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAtt_Header.swt
File367 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalAppletLinks2.swt
File368 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortaldCCAppletFormBasic.swt
File369 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortaldCCForm1ColBodyLight.swt
File370 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMReport_Form.swt
File371 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMReport_ListForm.swt
File372 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMReport_ListTotal.swt
File373 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgTopLevelButtons.swt
File374 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMObjectiveListApplet.swt
File375 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMTreeForm.swt
File376 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListMerged_B_EL.swt
File377 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCListButtonsTopWithTitle.swt
File378 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormQuestionnaire.swt
File379 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCScreenbar_Tabs_Hybrid.swt
File380 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalNavBarAppletDeptPage.swt
File381 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalQuickPicksAppletDeptPage.swt
File382 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_50_50_Over_100_Framed.swt
File383 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewFilterDetail.swt
File384 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewVertical_Framed.swt
File385 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgError.swt
File386 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgErrorPicker.swt
File387 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCCalendarView.swt
File388 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCCalendarViewTabs.swt
File389 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ermFrameViewbar.swt
File390 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4Col_E_N_NoTitle.swt
File391 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_25_50_25_Framed.swt
File392 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupListButtonsTop.swt
File393 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eDocumentsTemplateLayout.swt
File394 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4ColMerged_B_E_N.swt
File395 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFormButtonsTopWithTitle.swt
File396 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletHiGanttChart.swt
File397 = $(SiebelRoot)\siebsrvr\WEBTEMPL\HIcalendar.swt
File398 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFilterForm4Col_E_N.swt
File399 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EventHIcalendar.swt
File400 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletListTotals_B_EL_TglBar.swt
File401 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListCategorized3.swt
File402 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListCategorizedBulletTab3.swt
File403 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormWithSteps.swt
426
File404 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMImageDescr.swt
File405 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CBPopupForm.swt
File406 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CBListButtonsHierarchy.swt
File407 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CBPopupListHierarchy.swt
File408 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormButtonsTopNoRecNav.swt
File409 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletGotoURL.swt
File410 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletListPortalToggle.swt
File411 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupListAddItems.swt
File412 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortal4Up.swt
File413 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail_TglBar.swt
File414 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCPRMFrameViewbar.swt
File415 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMTopStory.swt
File416 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMTopStoryLgImg.swt
File417 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuBaseAutoReprice.swt
File418 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuControlCheckPrice.swt
File419 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuControlQuantityPrice.swt
File420 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuGroupSummary.swt
File421 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuLinkedItem.swt
File422 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuObj_GlobalSignal.swt
File423 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuProductTheme.swt
File424 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuTopLevelButtons.swt
File425 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_Status_Error_Undo.swt
File426 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewHIC.swt
File427 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4Col_B_Expanded.swt
File428 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4Col_E_N_Expanded.swt
File429 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm4Col_NoRecNav_Expanded.swt
File430 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCForm4ColBody_Expanded.swt
File431 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalURLAppletForm.swt
File432 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalURLAppletInner.swt
File433 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSISOMAppletForm4Col_NoRecNavLinks.swt
File434 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSISOMForm4ColBodyLinks.swt
File435 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCSISOMViewDetail2_ParentPntr.swt
File436 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CBAppletForm4Col_E_N_Simple.swt
File437 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuAttributeRadio.swt
File438 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalURLAppletGraphical.swt
File439 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCCRAFrameViewbar.swt
File440 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCScreenbar_NSTabs.swt
File441 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupListMvg.swt
File442 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupListAssoc.swt
File443 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletTaskAssistantPlayer.swt
File444 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletPopupFormGridLayout.swt
File445 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormGridLayout.swt
File446 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupListMvgShuttleButtonsTop.swt
File447 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCPopupListAssocShuttleButtonsTop.swt
File448 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_CCAppletTree.swt
File449 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewbarAll_Tabs_DropList.swt
File450 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewbar_Tabs_DropList.swt
File451 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductTabsJS.swt
File452 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgBaseAutoRepriceJS.swt
File453 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboAddJS.swt
File454 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgHiddenFrame.swt
File455 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgRelationContentsQuantityJS.swt
File456 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCompAttributeEditJS.swt
File457 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAtt_HeaderJS.swt
File458 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgTopLevelButtonsJS.swt
File459 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgPort_HeaderJS.swt
File460 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgGroupStandardJS.swt
File461 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgViewBasicJS.swt
File462 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_Status_ConflictJS.swt
File463 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAttributeComboBoxJS.swt
File464 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMEmpLocatorSearchFormApplet.swt
File465 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMBusinessCardFormBasic.swt
428
File466 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMViewResultsDetail.swt
File467 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuProductThemeJS.swt
File468 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuAttributeRadioJS.swt
File469 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuBaseAutoRepriceJS.swt
File470 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuControlQuantityPriceJS.swt
File471 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuObj_GlobalSignalJS.swt
File472 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuTopLevelButtonsJS.swt
File473 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletGanttChartActX.swt
File474 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboJS.swt
File475 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewChartList.swt
File476 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewParentListWithTabs.swt
File477 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewParentMultiChildWithTabs.swt
File478 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ermPortalViewbar.swt
File479 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ermPortalPageContainer.swt
File480 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ermEmbeddedFrameViewbar.swt
File481 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMIntegrationURLApplet.swt
File482 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCError.swt
File483 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgBaseManualRepriceJS.swt
File484 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboPriceJS.swt
File485 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboQuantityJS.swt
File486 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductRawModeJS.swt
File487 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletTaskMap.swt
File488 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCTitle.swt
File489 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgRelationContentsPriceQuantityJS.swt
File490 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboAddPriceJS.swt
File491 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_ExplanationJS.swt
File492 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgLinkedItemJS.swt
File493 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgResourceJS.swt
File494 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_GlobalSignalJS.swt
File495 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgGroupSummaryJS.swt
File496 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMListBodyTotals.swt
File497 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletListTotals_TglBar.swt
File498 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuGroupSummaryJS.swt
File499 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductSingleJS.swt
File500 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgProductWizardJS.swt
File501 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormGridWizard.swt
File502 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboPriceQuantityJS.swt
File503 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListImgBulletScreenHomepage.swt
File504 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm1ColScreenHomepage.swt
File505 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMGenericViewTree.swt
File506 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCESSPlayerApplet.swt
File507 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ermAdminFrameBanner.swt
File508 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ePortalNavBarAppletDeptPage_LeftNav.swt
File509 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_15_60_25_home.swt
File510 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMCPRDAListApplet.swt
File511 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMCPRDAListHeader.swt
File512 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAttributeRadioJS.swt
File513 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletCalendarGanttChartTop.swt
File514 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletCalendarGC.swt
File515 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletList_B_EL_NavControl.swt
File516 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletPortalLinks.swt
File517 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormPortalGraphical.swt
File518 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewbar_Tabs_DropList_Always.swt
File519 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespAttachmentListButtons.swt
File520 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespAppletInboundAttachments.swt
File521 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletScreenHomepageBanner.swt
File522 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyImgBulletScreenHomepage.swt
File523 =
$(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListImgBulletScreenHomepageWithDiv.swt
File524 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCForm1ColScreenHomepage.swt
File525 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyImgBulletScreenHomepage2.swt
File526 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletGanttChartActX_Mktg.swt
File527 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletAppHomepageBanner.swt
430
File528 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuControlCheckPriceJS.swt
File529 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfg_MenuLinkedItemJS.swt
File530 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ermAppletListTabbedHighlight.swt
File531 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ermListBodyHighlight.swt
File532 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ICAppletForm.swt
File533 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletPortalList.swt
File534 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm1ColScreenHomepageAdd.swt
File535 =
$(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletForm1ColScreenHomepageSearch.swt
File536 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMAppletListNoRowHilite_B_EL.swt
File537 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletListCalToDo.swt
File538 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eEventsEventMicrositeView.swt
File539 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletDashboard_3Row.swt
File540 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_50_50_1.swt
File541 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletLinksNoTitle1.swt
File542 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListDetailedImgBulletRecNav3.swt
File543 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListItemDetail.swt
File544 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListBodyImgBulletDetailed3.swt
File545 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCListItemDetail.swt
File546 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCFormButtonsBottom_ext.swt
File547 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormGridLayout_Extend.swt
File548 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletFormBasic_ext.swt
File549 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMKPIListApplet.swt
File550 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ERMMMProductView.swt
File551 = $(SiebelRoot)\siebsrvr\WEBTEMPL\TNTSHMHICalendar.swt
File552 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgGroupMessagesJS.swt
File553 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListImgDetailHC.swt
File554 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletListImgDetailHCBody.swt
File555 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail_ShoppingCart.swt
File556 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgObj_MessagesJS.swt
File557 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletParametricSearch.swt
File558 = $(SiebelRoot)\siebsrvr\WEBTEMPL\COMActiveXAppletForm.swt
File559 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormGridLayoutNoRecNav.swt
File560 =
$(SiebelRoot)\siebsrvr\WEBTEMPL\eCFGViewBasicJS_ViewDetail_ShoppingCart.swt
File561 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCQuickPrintPopupForm.swt
File562 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletPlaybarButtons.swt
File563 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletTaskPane.swt
File564 = $(SiebelRoot)\siebsrvr\WEBTEMPL\TUPopupWatchWindow.swt
File565 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCInboxTransfer.swt
File566 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboAddDomainPriceJS.swt
File567 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlComboAddPriceAttribGridJS.swt
File568 =
$(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgRelationContentsPriceQuantityAttribGridJS.swt
File569 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlCheckPriceMultiLevelJS.swt
File570 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCTaskViewTitle.swt
File571 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletPlaybarTop.swt
File572 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletPlaybarBottom.swt
File573 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletFormGridLayout_withJS.swt
File574 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgControlAttributeTextJS.swt
File575 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ccappletlist_b_el-shuttlemvg.swt
File576 = $(SiebelRoot)\siebsrvr\WEBTEMPL\ccappletlist_b_el-shuttleassoc.swt
File577 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SavedSearch.swt
File578 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SearchLookin.swt
File579 = $(SiebelRoot)\siebsrvr\WEBTEMPL\AdvancedSearch.swt
File580 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SearchPreference.swt
File581 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SearchResults.swt
File582 = $(SiebelRoot)\siebsrvr\WEBTEMPL\Search_ListHeader.swt
File583 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SearchResultsFooter.swt
File584 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SearchHeaderResults.swt
File585 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SaveSearchApplet.swt
File586 = $(SiebelRoot)\siebsrvr\WEBTEMPL\RefineCategoryApplet.swt
File587 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail_ParentPntr_TAQ.swt
File588 = $(SiebelRoot)\siebsrvr\WEBTEMPL\Search_View.swt
432
File589 = $(SiebelRoot)\siebsrvr\WEBTEMPL\Search_RefineCategoryApplet.swt
File590 = $(SiebelRoot)\siebsrvr\WEBTEMPL\Search_Popup.swt
File591 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgBaseAutoRepriceMultiSelectJS.swt
File592 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgTopLevelButtonsJS_Configurator.swt
File593 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCActionBar.swt
File594 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCActionPane.swt
File595 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletReplaceQuery.swt
File596 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SearchFindResults.swt
File597 = $(SiebelRoot)\siebsrvr\WEBTEMPL\SearchFindHeaderResults.swt
File598 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\dCCmain.css
File599 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCHtmlType.swf
File600 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCHtmlType.swf
File601 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\clock.gif
File602 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\voice.gif
File603 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_accept_work_item_enabled.
gif
File604 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_call_enabled.gif
File605 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_consultative_conference_en
abled.gif
File606 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_consultative_transfer_enabl
ed.gif
File607 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_email_enabled.gif
File608 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_fax_enabled.gif
File609 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_hold_work_item_enabled.gif
File610 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_initiate_work_item_enabled.
gif
File611 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_login_enabled.gif
File612 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_logout_enabled.gif
File613 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_mute_transfer_enabled.gif
File614 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_notready_enabled.gif
File615 = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_page_enabled.gif
File616 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_release_work_item_enabled
.gif
File617 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_retrieve_enabled.gif
File618 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_webcall_enabled.gif
File619 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_fwd_wrk_itm_1_d.gif
File620 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_res_wrk_itm_1_d.gif
File621 =
$(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\icon_wireless_enabled.gif
File622 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicscontrols.htm
File623 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicscontrolscal.htm
File624 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicscontrolscurr.htm
File625 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicsdata.htm
File626 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicsdatatoc.htm
File627 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicskbshortcuts.htm
File628 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicsnav.htm
File629 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebbasicsselectiondbs.htm
File630 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcalendar.htm
File631 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcharts.htm
File632 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomfindinginfo.htm
File633 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomgeneric.htm
File634 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomgenericcontactustoc.htm
File635 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomgenericfindinginfotoc.htm
434
File636=
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomgenericlogintoc.htm
File637=
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomgenericregistrationtoc.ht
m
File638=
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomgenericuserinterfacetoc.h
tm
File639= $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomloggingin.htm
File640= $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomregistration.htm
File641= $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomsearch.htm
File642=
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomupdatinguserprofile.htm
File643=
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomuserinterface.htm
File644 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcomwwattachments.htm
File645 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcorrespondence.htm
File646 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebcorrespondencetoc.htm
File647 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebfindinginfotoc.htm
File648 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebhomepage.htm
File649 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebhomepagetoc.htm
File650 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebindex.htm
File651 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebliterature.htm
File652 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebliteraturetoc.htm
File653 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\sieboptions.htm
File654 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\sieboptionstoc.htm
File655 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebquery.htm
File656 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebquerytoc.htm
File657 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebreports.htm
File658 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebsearch.htm
File659 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebsearchtoc.htm
File660 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebstarthelp.htm
File661 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebuserinterfacetoc.htm
File662 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebusingcalendartoc.htm
File663 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebwelcome.htm
File664 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebusingtaskbasedui.htm
File665 =
$(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebusingtaskbaseduitoc.htm
File666 = $(SiebelRoot)\siebsrvr\WEBMASTER\help\%LANGUAGE%\siebaccessibility.htm
2 Install the 8.1.1.x Siebel Fix Pack.
3 Copy the Siebel_Enterprise_Server folder into the local machine.
4 Change the value of OverWriteConfig=Yes in the following files:
5 Append the following accessibility files information in the Siebel_Enterprise_Server/siebel.ini
file, under [DeleteFiles.Windows]:
Fi l e2 = $( Si ebel Root ) \ si ebsr vr \ WEBTEMPL\ FI NSFr ameVi ewbar . swt
Fi l e3 = $( Si ebel Root ) \ si ebsr vr \ WEBTEMPL\ FI NSPageCont ai ner . swt
Fi l e4 = $( Si ebel Root ) \ si ebsr vr \ WEBTEMPL\ FI NSDBLogi n. swt
Fi l e5 = $( Si ebel Root ) \ si ebsr vr \ WEBTEMPL\ CCAppl et Dashboar d. swt
Fi l e6 = $( Si ebel Root ) \ si ebsr vr \ WEBTEMPL\ CCFr ameMsgbar . swt
Fi l e7 = $( Si ebel Root ) \ si ebsr vr \ WEBTEMPL\ Emai l RespFor mI nBoundNew. swt
Fi l e8 = $( Si ebel Root ) \ si ebsr vr \ WEBTEMPL\ Emai l RespFor mOut BoundNew. swt
Installing ACR 562
implement ACR 562.
1 Import all sif files related to the Siebel application located in the VARC562.zip and HACR562.zip
folders in the Siebel Tools/REPPATCH folder.
2 Set the following accessibility parameters for their respective application component:
HighInteractivity = FALSE
ExtendedKeyboard = True (In the cfg file under the InfraUI section)
ApplicationStyle = EmployeeFacing
AccessibleEnhanced = TRUE
436
DisableSITabIndex = TRUE
EnableSIFocusTracking = TRUE
Configuration Changes for ACR 422
implement ACR 422. As stated previously, ACR 422 was provided in the Siebel 8.1.1.1 Fix Pack.
NOTE: Siebel Fix Packs are cumulative.
Use the following procedure to enable screen readers to read out the applet summary for an
application. This is a user property based on the respective XML for an application.
To allow screen readers to read out the applet summary for an application
3 Unselect Application Object, select it again to add all of the child objects to the Object Explorer,
and click OK.
4 Click Application, and query for the Application Names listed in the following table:
5 Click the '+' sign and select 'Application User Property'.
6 Lock the object, right-click and select New Record.
7 Add the User Properties listed in the preceding table.
8 Save the changes.
New/
Changed Name
Application
User Property Value
SIA SIF File
Name
HOR SIF File
Name
Changed Siebel Universal
Agent
AccessibilityXMLF
ileName
nter.xml
nter_SIA.sif
nter_HOR.sif
Changed Siebel
eMarketing
AccessibilityXMLF
ileName
Accessibility_eMark
eting.xml
Accessibility_eMark
eting_SIA.sif
Accessibility_eMark
eting_HOR.sif
Changed Siebel eSales AccessibilityXMLF
ileName
.xml
Accessibility_eSale
s_SIA.sif
_HOR.sif
Changed Siebel eService AccessibilityXMLF
ileName
ce.xml
Accessibility_eServ
ice_SIA.sif
ce_HOR.sif
Changed Siebel Public
Sector
AccessibilityXMLF
ileName
Sector.xml
Sector_SIA.sif
Sector_HOR.sif
Changed Siebel Sales AccessibilityXMLF
ileName
Accessibility_Sales.
xml
Accessibility_Sales
_SIA.sif
Accessibility_Sales_
HOR.sif
Changed Siebel Service AccessibilityXMLF
ileName
e.xml
e_SIA.sif
e_HOR.sif
Enabling Screen Readers to Read MVGs and Pick Applets for Calendar, Calculator, and MVG
Use the following procedure to enable screen readers to read out the MVG and Pick Applet for
Calendar, Calculator, and MVG. After these changes have been made, screen readers will read out a
Calendar Pick Applet as shown in the following example: Start Date: 25/07/2007 Calendar Icon.
Calculator, and MVG ( Symbolic Strings)
Explorer.
4 Click on Symbolic Strings and query for 'Current String Value' as 'Input'.
5 Lock the object.
6 Make the following changes, as detailed in the following table:
a For SBL_CALCULATOR_ICON_ALT_TXT, change 'Current String Value' to 'Calculator'.
b For SBL_CALENDAR_ICON_ALT_TXT, change 'Current String Value' to 'Calendar'.
c Save the changes.
d In Symbolic Strings, query for 'Current String Value' as 'Select'.
e For SBL_EDIT_ICON_ALT_TXT, change 'Current String Value' from Select to 'Pick Applet'.
f Save the changes.
Calculator, and MVG ( Bitmaps)
2 Click on Bitmap Category and query for 'HTML Control Icons'.
3 Lock the HTML Control Icons object.
4 Navigate to Bitmap (child object) and query for 'CALENDAR_ ICON' and CALCULATOR_ICON.
New/
Changed Project Name Value SIA SIF File Name
HOR SIF File
Name
Changed Symbolic
Strings
SBL_CALCULATOR_IC
ON_ALT_TXT
Calculator SymbolicStrings_SI
A.sif
SymbolicStrings_H
OR.sif
Changed Symbolic
Strings
SBL_CALENDAR_ICON
_ALT_TXT
Calendar SymbolicStrings_SI
A.sif
SymbolicStrings_H
OR.sif
Changed Symbolic
Strings
SBL_EDIT_ICON_ALT_
TXT
Pick Applet SymbolicStrings_SI
A.sif
SymbolicStrings_H
OR.sif
438
5 Change the 'Alt Text' value to 'Calendar' and 'Calculator' respectively, as shown in the following
table:
6 Save the changes.
7 In HTML Control Icons query for ' EDIT_ICON' and change the Alt Value to 'Pick Applet', as shown
in the preceding table.
8 Save the changes.
Creating Keyboard Shortcuts for Navigation
Use the following procedures to provide shortcut keys for navigation.
To provide shortcut keys for navigation ( symbolic strings)
3 Select Symbolic Strings Object and click OK to add the Symbolic Strings object to Object
Explorer.
5 Right-click and click New Record.
6 Add the new records listed in the following table:
New /
Changed
Bitmap
Category Bitmap
Alt Text
Value Description
SIA SIF File
Name
HOR SIF File
Name
Changed HTML
Control
Icons
CALENDAR_ ICON Calendar Change the
Alt text from
"Input" to
Calendar.
HTMLControlIcon
s_SIA.sif
HTMLControlIcon
s_HOR.sif
Changed HTML
Control
Icons
CALCULATOR_ICON Calculator Change the
Alt text from
"Input" to
Calculator.
HTMLControlIcon
s_SIA.sif
HTMLControlIcon
s_HOR.sif
Changed HTML
Control
Icons
ICON_SELECT Pick
Applet
Change the
Alt text from
"Select" to
Pick Applet.
HTMLControlIcon
s_SIA.sif
HTMLControlIcon
s_HOR.sif
New/
Current
New Symbolic
Strings
SBL_CTRL_+_ALT_+_] Ctrl + Alt + ] SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif
New Symbolic
Strings
SBL_CTRL_+_ALT_+_[ Ctrl + Alt + [ SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif
New Symbolic
Strings
SBL_CTRL+SHIFT+B Ctrl+Shift+B symstr_columnsdisplay
ed_SIA.sif
symstr_columnsdisplaye
d_HOR.sif
The following table lists some of the keyboard shortcuts available with ACR 422, and the procedures
in the section that follows describe how to add these keyboard shortcuts.
New Symbolic
Strings
SBL_CTRL+, Ctrl+, SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif
New Symbolic
Strings
SBL_CTRL+. Ctrl+. SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif
New Symbolic
Strings
SBL_ALT_G ALT+G SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif
New Symbolic
Strings
SBL_ALT_U ALT+U SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif
New Symbolic
Strings
SBL_ALT_W ALT+W SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif
Command Action Accelerator
Key
Sequence Description SIA SIF File Name
NextApplet Next
Applet
Ctrl + Alt + ] Ctrl+Alt+221 Shifts focus
to the first
anchor of
the next
applet
PrevApplet Previous
Applet
Ctrl + Alt + [ Ctrl+Alt+219 Shifts focus
to the first
anchor of
the previous
applet
CmdPreviousApplet_SIA.
sif
Refine Query
(SWE)
N/A Alt+G Alt+G N/A CmdRefineQuery_SIA.sif
First Page
(SWE)
N/A Alt+U Alt+U N/A CmdFirstPageSWE_SIA.si
f
Last Page
(SWE)
N/A Alt+W Alt+W N/A CmdLastPageSWE_SIA.si
f
Columns
Displayed
(SWE)
N/A Ctrl+Shift+B Ctrl+Shift+B N/A CmdColumnsDisplayed_S
IA.sif
NextApplet Next
Applet
Ctrl + Alt + ] Ctrl+Alt+221 Shifts focus
to the first
anchor of
the next
applet
New/
Current
440
Creating Keyboard Shortcuts for Commands
Use the following procedures to provide keyboard shortcuts for commands.
To provide a keyboard shortcut for the NextApplet command
4 Click the Command object on Object Explorer and query for the 'NextApplet' command.
5 Lock the object.
7 In 'Display Name - String Reference', provide the newly created Symbolic String or in 'Display
Name' provide 'Ctrl + Alt + ]'.
To provide a keyboard shortcut for the PrevApplet command
1 Click the Command object on Object Explorer and query for the PrevApplet command.
2 Lock the object.
4 In the Display Name - String Reference' field, enter the newly created Symbolic String or in the
Display Name field, enter 'Ctrl + Alt + ['.
To provide a keyboard shortcut for the RefineQuery[ SWE] command
1 Click the Command object in Object Explorer and query for the Refine Query[SWE] command.
2 Lock the object.
5 In the Display Name field, enter 'Alt+G'.
6 In the Key Sequence field, change the value to 'Alt+G'.
To provide a keyboard shortcut for the FirstPage command
1 Click on Command object in Object Explorer and query for the First Page (SWE) command.
2 Lock the object.
5 In the Display Name field, enter 'Alt+U'.
6 In the Key Sequence field, change the value to 'Alt+U'.
To provide a keyboard shortcut for the LastPage ( SWE) command
1 Click on Command object in Object Explorer and query for 'Last Page (SWE)' Command.
2 Lock the object.
5 In the Display Name field, enter 'Alt+W'.
6 In the Key Sequence field, change the value to 'Alt+W'.
To provide a keyboard shortcut for the Columns Displayed ( SWE) command
1 Click on Command object on Object Explorer and query for 'Columns Displayed (SWE)'
Command.
2 Lock the object.
5 In the Display Name field, enter 'Ctrl+Shift+B'.
6 In the Key Sequence field, change the value to 'Ctrl+Shift+B'.
To provide a keyboard shortcut for the Previous Record ( SWE) command
1 Click on Command object on Object Explorer and query for 'Previous Record (SWE)' Command.
2 Lock the object.
5 In Display Name field, enter 'Ctrl+,'.
6 In the Key Sequence field, change the value to 'Ctrl+,'.
To provide a keyboard shortcut for the Next Record ( SWE) command
1 Click on Command object on Object Explorer and query for 'Next Record (SWE)' Command.
2 Lock the object.
442
5 In the Display Name field, enter 'Ctrl+.'
6 In the Key Sequence field, change the value to 'Ctrl+.'
Providing Default Focus for Search Center
The following section details the changes that are required for the search applet in order to provide
a default focus for the "Search" option provided in the Siebel application.
Use the following procedure to provide a default focus for Search.
To provide a default focus for Search
3 Query for "Search lookin" and lock it.
4 Enter "Search" in the Title field.
5 Make sure that the proper Symbolic String has been selected.
To add the DefaultFocus User Property
3 Query for "Search lookin".
4 Navigate to Applet User Property.
5 Add the DefaultFocus user property, as described in the following table.
NOTE: The DefaultFocus user property can be applied for any form applet where the user requires
a default focus.
Creating the View Info Command
The following procedure explains how to create the View Info command.
New /
Changed Applet Name Title Description SIA SIF File Name HOR SIF File Name
Changed Search lookin Search Provides a title
to the applet
for screen
readers to
read out.
AppletSearchlookin_SIA.sif AppletSearchlookin_HOR.sif
New /
Changed Applet Name
Applet User
Property Value Description
SIA SIF File
Name HOR SIF File Name
Changed Search lookin DefaultFocus SearchFor Added the user
property to set the
default focus
AppletSearchlo
okin_SIA.sif
AppletSearchlookin_HOR.sif
To create the View I nfo command
2 Navigate to Command and lock the "Command" project.
3 Create a New Command named "View Info" with project "Command" as the project, using the
values detailed in the following table:
NAME="ViewInfo"
METHOD="ViewInfo"
TARGET="SI Plus"
4 Add a new Accelerator to the Command for the required Key Combination with the following
values:
NAME="1"
BROWSER_PLATFORM="All"
INACTIVE="N"
KEY_SEQUENCE="Ctrl+Alt+Z"
NOTE: Although it is not mandatory, it is important that you enter Does not matter as the value
for the Display Name or Caption field.
5 Add a new Symbolic String if required.
6 Add the required Key Combination.
7 Navigate to Menu, and create a new Menu Item (Hidden) under the menu used by your
application, using the following values:
(For example, Siebel Universal Agent, the name of a project in Siebel Tools, uses Generic Web
Menu.)
Name="Hidden-View Info
Position=8.39
Command Project Action Accelerator
Key
Sequence Description
SIA SIF
File Name
HOR SIF
File Name
View Info Command ViewInfo Ctrl + Alt + Z Ctrl + Alt
+Z
A new shortcut
key that
generates a
dialog box that
contains
ViewName, View
Summary and
Applet Names
CmdViewInf
o_SIA.sif
CmdViewInf
o_HOR.sif
Sub-View Tab
(SWE SI)
SWE N/A Ctrl + Alt + V Ctrl +Alt
+V
N/A CmdSubVie
wTab_SIA.si
f
CmdSubVie
wTab_HOR.s
if
444
Command = "ViewInfo"
Caption="Does not matter"
8 Associate this menu item to the newly created command object.
For more information about shortcuts, refer to other shortcuts such as NextApplet within Siebel
Tools.
Enabling Screen Readers to Read Out the Check Box HTML Flag as HTML
The following procedure allows screen readers to read out the check box HTML Flag as HTML. By
default, it reads as Public. To make this change, you can also import the
Applet_CommPackageResponse_SIA.sif file. For information about how to import .sif files, see
To enable screen readers to read out the check box "HTML Flag" as HTML
1 Open Siebel Tools, and navigate to applet "Comm Package Response Form Applet".
2 Right-click, and select the "Edit web layout" menu item.
3 Focus on the HTML template check box
4 Change the control name from "Public" to "HTML Flag".
Resolving an Error Generated When Creating New Records Within the Leads Screen
Use the following procedure to resolve an error message that occurs when users are creating new
records under the Leads screen, so that users are not able to see any case records in the Pick Cases
MVG. To make this change, you can also import the PUBLeadListCaseMvgApplet.sif, PUBLeadsList.sif,
PUBLeadsListApplet.sif, and CaseMvg.sif files. For information about how to import .sif files, see
To resolve an error message generated in the Leads screen
1 Open Siebel Tools, and navigate to the "PUB Lead List Case Mvg Applet" applet.
2 Lock the object.
3 Navigate to Applet Web Template.
4 Add one more Web Template Item for Base.
5 Navigate to the "PUB Leads List Applet" applet and lock it.
6 Click Edit to create a web template and add the necessary controls, along with SAVE and CANCEL
buttons.
Making the Help System Accessible for Screen-Reader Users
The following procedure makes the help system accessible for screen-reader users. It adds a topic
to the Siebel iHelp system that describes accessibility features and how to use them, and it also
ensures that the iHelp system is available on each home page of the Siebel application. To make
these changes, you can also import the Accessibility_symbolicString.sif, CCLoginPage_HOR.sif,
CCLoginPage_SIA.sif, DotComPage_HOR.sif, and DotComPage_SIA.sif files. For information about
how to import .sif files, see Importing SIF Files on page 65.
To make the help system accessible for screen- reader users
1 Add a symbolic string called SBL_ACCESSIBILITY.
2 Lock the eApp project, and add a web page item called AccessibilityButton in the Web Page:
DotCom Page Container eService (Framed).
3 Add another web page item called AccessibilityButton in the Web Page: CC Login Page (Login
Only).
Generating HTML Summary Attributes for All List Applets
The following changes need to be made for Generating HTML SUMMARY attributes for all list applets.
The default tag text should be set to the applet header name. Add TITLE or LABEL for each table
entry (all HTML form elements). Row and column headers must be identified as required by OGHAG
TABLE-1 and TABLE-2. Adding a row title for each row in data table (Suggestion: this could be the
first displayed data column in the applet display. Ideally the customer can select which column can
be used as the index for the row title through configuration).
NOTE: The list applet row ids are not available out of the box. Users can add them if they want. The
first data column will be used as the default rowid when there is no row id provided in the "RowId"
applet user property. There are two options available to users to select different rowid.
Option 1: Users need to contact the administrator to define the "RowId" user property.
To do this, a new applet user property called "RowId" has to be added for the list applet. The "RowId"
value should be equal to one of the displayed column name. For example, in the Contact list applet,
if 'Last Name' has been selected as the row header, the user property value has to be set to "RowId
= Last Name". Here "Last Name" is the list column name.
Option 2: Users can select the column displayed window and select some other column as the first
column for the list applet. The newly-selected column will become the rowid. Lock the particular
applet that needs to be changed.
Providing a New Key Combination for the Next and Previous Record Commands
Use the following procedure to provide a new key combination for the Next and Previous Record
commands.
446
To provide key combinations for Next Record and Previous Record
NOTE: The tables that follow this procedure provide more information about the fields that you
will be changing.
4 Within Object Explorer, click the Command object and query for 'Previous Record(SWE)'
Command.
5 Lock the object.
7 Change the 'Display Name' from 'Ctrl+,' to 'Alt+,'
8 In the 'Key Sequence' field, change the value to Alt+0xBC.
9 Within Object Explorer, click the Command object and query for 'Next Record(SWE)' Command.
10 Lock the object.
12 Change 'Display Name' from 'Ctrl+.' to 'Alt +.'
13 In the 'Key Sequence' field, change the value to Alt+0xBE.
New/
Current
String
New Symbolic Strings SBL_ALT+, Alt+, symbolistring_Next_Prev_H
OR.sif
IA.sif
New Symbolic Strings SBL_ALTL+. Alt+. symbolistring_Next_Prev_H
OR.sif
IA.sif
Command Project Accelerator Key Sequence SIA SIF File Name HOR SIF File Name
Next Record(SWE) Command Alt +. Alt+0xBE Next_Prev_SIA.sif Next_Prev_HOR.sif
Previous
Record(SWE)
Command Alt +, Alt+0xBC Next_Prev_HOR.sif Next_Prev_HOR.sif
Providing Alt Text for Bullets
In Recent Records, the bullets need to have alt text provided. To make this change, import the
orangebullet_HOR or orangebullet_SIA.sif files as detailed in the following table. For information
Enabling or Disabling the Confirmation Message on Page Refresh
The procedure in the following section describes how to enable or disable the confirmation message
upon page refresh. To make this change, you can also import .sif files. To do so, import
ConfirmationMessage_SIA.sif and ConfirmationMessage_HOR.sif. For symbolic strings, import
symstr_confirmationmessage_SIA.sif and symstr_confirmationmessage_HOR.sif. For information
To enable or disable the confirmation message upon page refresh
1 Log into the application using /editseeddata (for Siebel Developer Web Client) for the local
database or dedicated database (for the master database, the Add button is enabled by default).
2 Navigate to Administration - Data > List Of Values Explorer, and add the new LOV types
mentioned in the following table:
New/
Changed Project Name Current String Value HOR SIF File Name SIA SIF File Name
Changed Symbolic
Strings
SBL__IMG_SRC__IMA
GES/
CHEVRON_SM.GIF__
ALIGN__RIGHT__BOR
DER__0
<IMG SRC="images/
orange_bullet.gif"
align="right" border="0"
alt="" >
orangebullet_HOR.sif orangebullet_SIA.sif
New/
Changed Project Value Description
New Symbolic Strings Accessibility Create a new Symbolic String for Accessibility
Project for the "Confirmation Message" User
Preference
New Symbolic Strings Confirmation
Message
Create a new string for the Control
Type
Display
Value Translate Multilingual
Language
Independent
Code Order Language Name
SWE_CONFIRMATION
_MESSAGE
TRUE Yes Yes TRUE 1 English-American
SWE_CONFIRMATION
_MESSAGE
FALSE Yes Yes FALSE 2 N/A
448
3 After you have added these changes, navigate to Screen > System Administration > List Of
Values to view these changes in the repository.
The following changes have been made to the User Preferences Business Component.
The following table describes the new User Profile Confirmation Message Parameter Applet that has
been added to support ACR 422.
The following table describes the applet controls changes that have been implemented to support
ACR 422.
New/
Business
Component Static Type Field Type Value
New Confirmation
Message
Picklist
User Preference PickList Generic Yes Type SWE_CONFIRM_MESSAGE
Name PickList Predefault Value Type
SWE/Confirmation Message Confirmation Message
Picklist
TRUE DTYPE_TEXT
New/
Business
Component Class Title
New User Profile
Parameter Applet
User
Preferences
User Preferences CSSFrameBase Accessibility
Name Caption Field HTML Type Method Invoked Runtime Field Type
Applet Title Accessibility N/A Text N/A N/A N/A
ConfirmMssg Confirmation
Message
SWE/
Confirmation
Message
Text N/A Yes BC Field
ExecuteQuery Go N/A MiniButtonQuery ExecuteQuery N/A N/A
NewQuery Query N/A MiniButtonEdit NewQuery N/A N/A
QueryAssistant Query Assistant N/A MiniButtonQuery ShowQueryAssistant N/A N/A
ResetRecord Reset N/A MiniButton ResetRecord N/A N/A
SaveEditRecord Save N/A MiniButtonEditNew ExplicitWriteRecord N/A N/A
UndoQuery Cancel N/A MiniButtonQuery UndoQuery N/A N/A
WebEditTitle Accessibility N/A Label N/A N/A N/A
The following table describes the view changes that have been added to support ACR 422.
The following table describes the User Profile screen changes that have been added to support ACR
422.
Resolving an Error Message Within Under Diseases > Cases 3LNV
Users are receiving error messages while creating new records under Diseases > Cases 3LNV. This
is specific to SIA.
Use the following procedure to resolve this issue.
To resolve an error message within Cases 3NLNV
1 Add the 'Edit' template to 'PUB Disease Case List Applet'.
2 Make sure that the Execute Query, WriteRecord, UndoQuery, UndoRecord, and Query Assistant
controls are present on the applet template.
NOTE: Edit template uses 'Applet List Edit (Edit/New/Query)' as the web template.
Resolving an Error Where Commands Are Executed Before Users Click Enter
Users are encountering an issue where before they click Enter on a menu item in the Show dialog
box, the command is executed.
To resolve an error in which commands are executed before users click Enter in the
Show dialog box
New/Changed Name Project Business Object
Visibility Applet
Type
New User Profile
Parameter View
User Preferences User Preferences User Profile
Parameter Applet
New/Changed Name View Type
Visibility Applet
Type
New User Profile
Parameter View
User Profile
Parameter View
Aggregate View User Profile
Parameter Applet
New/
Web
Template SIF File
New PUB Disease Case
List Applet
PUB HLS Bio Terrorism Edit Disease_Case_SIA.sif
450
Explorer.
5 Right-click and select 'New Record'.
6 Add the new records mentioned in the following table.
To implement the NextPage and PreviousPage commands
4 Within Object Explorer, click the Command object and query for the 'NextPage' command.
5 Lock the object.
6 Within Object Explorer, click the '+' sign and choose 'Accelerator'.
created Symbolic String or in 'Display Name' provide 'SBL_ALT+CTRL+DOWN'.
8 In the 'Key Sequence' field, change the value to 'Alt+Ctrl+Y', as shown in the following table:
9 Within Object Explorer, click the Command object and query for the 'PreviousPage' command.
10 Lock the object.
11 Within Object Explorer, click the '+' sign in and choose 'Accelerator'.
created Symbolic String or in 'Display Name' provide 'SBL_ALT+CTRL+UP'.
13 In the 'Key Sequence' field, change the value to 'Alt+Ctrl+L'.
New/Changed Project Name Value
New Symbolic Strings SBL_ALT+CTRL+Y Alt+Ctrl+Y
New Symbolic Strings SBL_ALT+CTRL+L Alt+Ctrl+L
Command Action Accelerator Key Sequence Description
NextPage Next Page Alt + Ctrl + Y Alt+Ctrl+Y Navigate to the
Next Page
PreviousPage Previous Page Alt + Ctrl + L Alt+Ctrl+L Navigate to the
Previous Page
Resolving an Error Encountered While Creating a New Record in the Identities Form Applet
The information in the following section resolves an issue where users encounter a problem within
the Immigration contacts screen > Identities view when they try to create a new record under the
Identities form applet. To make this change, you can follow the procedure below, or you can import
the PublicSector_Controls.sif file. For information about how to import .sif files, see Importing SIF
Files on page 65.
To resolve this error message, change the HTML Type property of the DeleteRecord control from
MiniButton to MiniButtonEdit for the PUB Immigration Identity Form Applet, the PUB Lead Form
Applet, the HLS Group Form Applet, the Disease Form Applet, the FINS Application Entry Applet
ACAPS, and the HLS Medication Form Applet. Use the following bulleted list information group for
each applet as a reference point.
Applet: 'PUB Immigration Identity Form Applet'
Template: Edit
Additions: UndoRecord and WriteRecord controls
Applet: PUB Lead Form Applet
Template: Edit
Additions: WriteRecord (save) control. UndoRecord (cancel) does not need to be added as
the 'DeleteRecord' control is already present on the template.
Applet: "HLS Group Form Applet", "Disease Form Applet" and "FINS Application Entry Applet -
ACAPS"
Template: Edit
Additions: 'WriteRecord' control.
Applet: HLS Medication Form Applet
Template: Edit
NOTE: For the HLS Group Form Applet, Disease Form Applet, and FINS Application Entry Applet,
access these applets from under the Application screen and not from the BCM Applications screen.
The necessary changes need to be made under the configuration context of Siebel Public Sector for
these applets, because they are also used by the FINS application.
Resolving an Issue Where Users Are Unable to Query for Evidence Parent Information
The following procedure resolves a problem where under Evidence screen> Evidence parent, users
are unable to query for User Parent, and they receive an error message. To make this change, you
can also import the PublicEvidencePickApplet_SIA.sif file. For information about how to import .sif
files, see Importing SIF Files on page 65.
Add 'Popup Query' template to the 'PUB Evidence Pick Applet' with appropriate controls
[ExecuteQuery and CancelQuery] placed on it.
Importing SIF Files
The following procedure describes how to import .sif files.
452
To import SI F files
1 Lock the particular object /project that needs to be changed.
2 Navigate to Tools > Import from Archive and select the related .sif file
3 Click OK, and follow the instructions in the wizard to implement the changes.
4 Stop the servers, compile the objects or projects into respective .sif file and then restart the
servers.
Configuration Changes for Adding the Applet Summary for New or
Customized Applets
The following sections contain configuration changes that you must make to add the applet summary
for new or customized applets. You must import .sif files for table changes, apply the DLL, import
seed data, and import the Accessibility Project .sif files. The necessary changes are detailed in the
following topics:
Applying the DDL
Importing Seed Data
The procedure in the following section describes how to add the applet summary for customized or
new applets.
To import the SI F file for table changes
1 Lock the (Table Common) project by navigating to the Project Tab and checking the "Locked"
check box.
2 Import the Table archive file "Accessibility_Table.sif" table archive file.
3 Click Yes when the dialog box displays and asks This operation should only be performed while
connected to your local database. Would you like to continue anyway?
4 Select the "Accessibility_Table.sif" file.
5 Select the first option "Overwrite the object definition in the repository" in the Conflict resolution
section of the import wizard view.
6 Review the conflicting objects to see if the new or modified columns appear. The import log is
stored at Siebel\tools\temp\importlog.txt
Applying the DDL
The procedure in the following section describes how to apply the DDL.
To apply the DDL
1 Select the table or tables you want to apply to the physical database and press Apply/DDL button
(option > Apply).
2 For a single table, select the current row option in Tables (Apply Schema Window).
3 For more than one table, select the Choose Current Query option.
4 For the Accessibility project, select the S_ACC_VIEW_APPL table and current row option.
5 Make the following changes depending upon which database you are using:
a For MSSQL, enter the database users, the database user password, and the correct ODBC data
source.
b For Oracle, enter the table space, the index space, the database user, the database user
password, and the correct ODBC data source.
c For IBM DB2, enter the table space, the 16K table space, the 32K table space, the index space,
the database users, the database user password, and the correct ODBC data source.
6 After entering in the database information, click the Apply button.
7 Verify that the required changes have been applied by selecting count(*) from
S_ACC_VIEW_APPL.
The query should result in 0 records.
Importing Seed Data
The procedure in the following section describes how to import seed data.
To import seed data
1 Copy dat files into a work-area folder.
2 Run the following command for importing seed data:
NOTE: For HOR applications, use the HOR .dat file.
si ebsr vr r oot \ BI N\ dat ai mp / u <UI D>/ p <PWD>/ f <HOR DAT f i l e>/ l dat ai mp_HORseed. l og
/ c <ODBC > / d <TABLEOWNER > / q - 1 / e n / t n / x R / n 100 / h l og
(For SIA applications, use the SIA .dat file.)
si ebsr vr r oot \ BI N\ dat ai mp / u <UI D >/ p <PWD>/ f <SI A DAT f i l e>/ l dat ai mp_SI Aseed. l og
/ c <ODBC > / d <TABLEOWNER > / q - 1 / e n / t n / x R / n 100 / h l og
For example:
C: \ 21011\ si ebsr vr \ BI N\ dat ai mp / u MMRAO / p ****** / f HACR422. dat / l
dat ai mp_ORA21013. l og / c ORA21013 / d ORA21013 / q - 1 / e n / t n / x R / n 100 / h l og
3 When prompted for the table name, enter S_ACC_VIEW_APPL.
4 Check the log files for any errors, and check S_ACC_VIEW_APPL for the data imported.
454
The following section describes how to import the Accessibility Project .sif files.
To import the .sif files provided for ACR 422
1 Create the Accessibility project and import the .sif.
2 Import AccProject.sif. For a list of files that this .sif contains, see Changes to SIF Files in ACR
422 on page 70.
3 Import AdminScreen.sif and merge the file.
The AdminScreen.sif file contains the modified System Administration Screen. For the list of
changes to this screen, see Changes to SIF Files in ACR 422 on page 70.
4 Add the following new LOV types and values:
5 Add the following views to the application and associate responsibility:
6 Run the perl script using the procedures detailed in Step a through Step c.
Note the following prerequisites for running the perl script:
Perl 5.8 or higher (http://www.activestate.com/Products/activeperl/index.mhtml)
Perl module: DBI (http://dbi.perl.org/)
Perl module: XML: Generator (http://search.cpan.org/~bholzman/XML-Generator-1.01/
Generator.pm). Install Perl modules: DBI (DBD::ODBC) and XML::Generator from PPM (Perl
Package Manager).
a Open a command line window and navigate to the folder where the three scripts reside
(genAccessibilityXML.pl, app_tree.pl, sqlstmt.pl).
b Execute the script with the following command:
For all databases, change Oracle in DBI->Connect( ) in app_tree.pl and
genAccessibilityXML.pl to ODBC.
Type Value
ACC_ATTRIB_TYPE Summary
ACC_ATTRIB_TYPE Label
ACC_LOCALE ENU
The following step applies only to the MSSQL database:
After the following lines in app_tree.pl script:
#Connect to DB
#################################################
$dbh = DBI->connect("dbi:ODBC:$ODBCConnection", $userid, $passwd) || die
$DBI::errstr;
#################################################
Add the line $dbh->{odbc_SQL_ROWSET_SIZE} = 2;
Execute the script with the following command:
SYNTAX: perl genAccessibilityXML.pl "<Application Name>" <LOCALE_CODE>
<CONNECTSTRING/TABLEOWNER> <USERID> <PASSWD>
_________________________________________________________________________
____
**Deleted SYNTAX: perl genAccessibilityXML.pl "<Application Name>" <LOCALE_CODE>
<CONNECTSTRING/TABLEOWNER> <USERID> <PASSWD> that used to be here, because
Punit pointed out that it was already covered above.**
c Once the script is run an xml file will be generated, copy this xml in the following location:
Siebel\ses\siebsrvr\bin\LANG_FOLDER\ folder.
The LANG_FOLDER should be substituted by ENU for English, and so forth.
The name of the XML File should be same as the value mentioned for the Application user
property 'AccessibilityXMLFileName' for that application.
NOTE: The preceding steps help the users provide the summary for a new or a customized
applet. A UI will be created in which the user has to enter the summary for a particular applet.
This in turn will be placed into the XML file that will be generated after the perl script is run. Users
can use this XML file to allow screen readers to read out the applet summary.
Workaround for Accessibility Applets
You must perform the following workaround procedure in order to be able to implement ACR 422.
These changes must be made to the Accessibility Applet Attributes List Applet and the Accessibility
Applet Attributes Form Applet. This workaround has been added to address CR 12-1Q8YZDL, CR 12-
1Q6XXPY, and CR 12-1Q6XXOX.
For both of these applets, use the following procedure:
1 Right-click, and select Applet > Edit Web Layout.
2 In the Controls/Column Pane, select EditList.
3 Uncheck the Show mapped controls only check box.
4 Drag and drop the Position on Row control.
456
5 Edit the Position on Row controls properties by entering ROW_OFF for HTML Bitmap and
ROW_ON for HTML Disabled Bitmap.
6 Save the applet.
7 Drag and drop the GotoPreviousSet and GotoNextSet controls to their respective placeholders,
and edit the properties using the values in the following table:
8 Save the applet.
9 From the drop-down list, select Edit.
10 Drag and drop the Save and Cancel buttons to their respective placeholders.
11 Save the applet.
About the SIF Files Provided for ACR 422
This section contains the list of changes to the .sif files provided for ACR 422.
AccProject.sif
The AccProject.sif file contains the following new objects:
Business Components:
Applets:
Accessibility Applet Attributes List Applet
Accessibility Applet Attributes Form Applet
Business Objects:
Views:
Picklists:
Control Property Value
GotoPreviousSet HTMLBitmap RECNAV_PREVSET_ON
GotoPreviousSet HTML Disabled Bitmap RECNAV_PREVSET_OFF
GotoNextSet HTML Bitmap RECNAV_PREVSET_ON
GotoNextSet HTML Disabled Bitmap RECNAV_PREVSET_OFF
Accessibility Applet Attribute PickList
Accessibility View Attribute PickList
Accessibility Locale PickList
Symbolic Strings:
Accessibility
Applet Attributes
Attribute Type
View Attributes
AdminScreen.sif
The AdminScreen.sif file contains the following changes:
Accessibility Attributes (new category)
Accessibility Applet Attributes View (new view)
Accessibility View Attributes View (new view)
The following section contains procedures for installing and configuring ACR 574.
Prerequisites for ACR 574
ACR 476 and the new Email Response UI were provided in the Siebel 8.1.1.1 Fix Pack, but you must
perform configuration changes for ACR 476 and the new Email Response UI to be able to install and
configure ACR 574.
The following sections describe how to configure ACR 476 and the EMR UI.
Installing ACR 476
1 Install Siebel Server and Siebel Tools version 8.1.1, if you have not already.
2 Install Siebel Server and Siebel Tools provided within the 8.1.1.x Fix Pack.
3 Verify that the following DLL files exist in the siebsrvr\bin folder:
sscasasv.dll
swcasvfr.dll
swcashfr.dl
swcanshfr.dll
458
sscashsv.dll
4 Verify that the ACR 476.zip file exists in the Siebel Tools/REPPATCH directory.
5 Verify that the SAConfig.xml file exists in the siebsrvr/smartanswer directory.
6 Navigate to Administration - Data > List Of Values, click New, and add a record with the following
values:
Type = SEARCH_SMART_ANSWER
Display Value = Smart Answer
Language = English American
Customers using languages other than ENU can change the language.
To change the language
1 Launch Siebel Tools, and navigate to View > Options > Language setting.
2 Select the language from the drop-down list and click OK.
NOTE: When you are compiling and whne you are replacing the SRF, make sure that the SRFs are
from language folders.
Configuring ACR 476
1 Extract *.sif files from siebsrvr/objects/ACR476.zip into a temporary location.
2 Launch Siebel Tools, and import all of the extracted .sif files in the following order:
01_sma_project.sif
02_sma_classes.sif
03_sma_dll.sif
04_sma_bussvc.sif
05_sma_io.sif
06_sma_ss.sif
07_sma_applets.sif
08_sma_sct.sif
09_sma_view.sif
10_emr_bussvc.sif
3 Upon successful import, within Siebel Tools, make sure the following projects are locked:
Smart Answer 8.x
Smart Answer
Banter eService
Service (SSV)
Symbolic Strings
eCatalog Admin
Email Response
5 Use the newly compiled repository (.srf) for launching the Siebel Server.
6 Within the siebsrvr/smartanswer directory, update SAConfig.xml:
a Update the value for NLPAdapterDLLName with the correct location and filename.
b Make sure that the value for FacadeName is correct.
c Make sure that you have the correct, accessible, and writable FileSystem location.
d Under the above FileSystem, create a new folder called "smartanswer", and create two new
directories called "import" and "export" under the smartanswer directory.
7 Place the third-party DLL in the NLPAdapterDLLName directory specified in the SAConfig.xml file.
Installing the Email Response User Interface
1 Install Siebel Server and Siebel Tools version 8.1.1, if you have not already.
2 Install Siebel Server and Siebel Tools from the 8.1.1.x Fix Pack.
3 Verify that the following DLL files exist in the siebsrver\bin directory:
swcommfr.dll
sscommsv.dll
sscmclnt.dll
sscacabc.dll
swcacafr.dll
4 Verify that the EMRUI_New.zip file exists in the Siebel Tools/REPPATCH directory.
5 Navigate to Administration - Application > View > Communication Detail view to add seed data.
a Launch the dedicated client with the /editseeddata parameter set.
b Click New and add the following values:
View Name = Communication Detail View
Description = Drill down View
Default Access = Yes
c Add the following responsibilities to this view:
Call Center Administrator
Email Response Agent
460
Email Response Manager
Configuring the Email Response User Interface
1 Extract the *.sif files from Tools\REPPATCH\EMRUI_New.zip into a temporary location.
2 Launch Siebel Tools, and import all of the extracted .sif files in the following order:
EMR_UI_Applets.sif
EMR_UI_BC.sif
EMR_UI_BO.sif
EMR_UI_BS.sif
EMR_UI_Class.sif
EMR_UI_Screen.sif
EMR_UI_View.sif
EMR_UI_Webtemplate.sif
3 Upon successful import, within Siebel Tools, make sure the following projects are locked:
Mail Agent
Email Response
5 Use the newly-compiled repository (.srf) for launching the Siebel Server.
6 Import and activate the following workflows:
Email Response - Analyze Message.xml
Email Response - Client Send Email.xml
Email Response - Create Activity.xml
Email Response - Process Message.xml
Email Response - Response Workflow.xml
Email Response - Send Auto Response.xml
Email Response - Set Parent Activity Status.xml
Prerequisites for Smart Answer Server and Admin Tool
The following prerequisites apply for Smart Answer Server and Installer:
Smart Answer Server is currently only available for Microsoft Windows 2003.
It is recommended that Smart Answer Server be run on a single standalone server with 4GB RAM
and at least a 3.4 GHz processor.
Additional Software
The following software is required:
PostgreSQL 8.3+. Obtain and install PostgreSQL from http://www.postgresql.org/download/
windows.
Java Runtime Environment 1.6+. Obtain and install Java from http://java.com/en/download/
manual.jsp.
Python Interpreter 2.4+: http://www.python.org/download/.
NOTE: Smart Answer is not yet compatible with Python version 3.0 and above
PyWin32: http://sourceforge.net/projects/pywin32/files/.
NOTE: This is required for running Smart Answer Server as a Windows service. It is highly
recommended, but optional.
Be sure to download the automated installer that matches your version of Python.
Installing ACR 574
Note the following before you install ACR 574:
Avoid using Siebel subservices and use Port 1099. It has been coded for use with Smart
Answer.
Start the Smart Answer first and then start the Siebel application to avoid a potential port
conflict.
1 Install Siebel Server version 8.1.1, if you have not already.
2 Install the Siebel 8.1.1.x Fix Pack.
3 Verify that the following DLL files exist in the siebsrvr\bin directory:
swcommfr.dll
sscanshsv.dll
sscasasv.dll
sscashsv.dll
swcanshfr.dll
4 Verify that the SmartAnswerInstall.zip file exists in the Smart Answer
InstalleRelease\Windows\Server_Ancillary\Smart_Answer\enu directory.
5 Verify that the ACR574.zip file exists within Siebel Tools/REPPATCH.
6 Verify that the SAConfig.xml file exists within the siebsrvr/smartanswer directory.
Configuring ACR 574
1 Navigate to Tools\BIN\<lang> (where <lang> is ENU, DEU, and so on).
2 Open the Tools.cfg file, and change the SymStrPrefix value from x_ to SBL_.
462
3 Extract the contents of ACR574.zip (<Extract_Dir>).
4 Connect to Siebel Tools, and lock the eCatalog Admin project.
5 Select Tools > Import from Archive, and then select
<Extract_Dir>\ACR574\Repository\Applet\Applet.sif.
6 Lock the Symbolic Strings project.
7 Select Tools > Import from Archive, and then select
<Extract_Dir>\ACR574\Repository\SymbolicString\SymbolicString.sif.
8 Compile the changed objects to the Siebel repository and then unlock the locked projects.
9 Navigate to <Extract_Dir>\ACR574\Workflow, and import and activate the Email Response -
Create Activity.xml workflow.
NOTE: If there have been any changes made to the Symbolic String project, after you have
imported the .sif files, navigate to Tools\BIN\<lang>, open tools.cfg, and change the
SymStrPrefix value from SBL_ to x_.
Importing LMU Files for ACR 574
The LMU files for non-ENU languages are also available in the ACR574.zip file. This file is located in
the Extract_Dir>\ACR574\LMU\<lang>\ directory. The LMU files hold the translation for the
Synchronize Button added in the Administration - Catalog Screen.
You use the Locale Management Utility to import translated strings and other locale-specific
attributes back into the repository. Use the preview functionality to display the results of the import
process before you actually import them into the repository.
NOTE: When using the LMU to import files with the.xlf extension, make sure that you are connected
to the Internet.
.xlf files are provided along with the ACR content in the build and mirror the \ENU location.
To preview the results of the import process
1 Choose Tools > Utilities > Locale Management.
4 Enter the directory path and name of the file you are going to import.
5 Enter the path and name of the file where you want to store the results for previewing.
The default file name is "preview.log."
6 Click Preview.
The Locale Management Utility writes the results of the import process to the log file rather than
to the repository.
NOTE: LMU does not mark changed records with a Redo flag when running in Preview mode.
7 If you receive an error message, use the following workaround:
NOTE: CR 12-1VR263N has been logged for this issue.
a Save a copy of the xliff.dtd file locally (http://www.oasis-open.org/committees/xliff/documents/
xliff.dtd).
NOTE: Save from the parent directory http://www.oasis-open.org/committees/xliff/documents
and not from the file itself as doing so will yield the "Invalid structure error message.)
b Change the following line in each language .xlf file:
<!DOCTYPE xliff PUBLIC "-//XLIFF//DTD XLIFF//EN" "http://www.oasis-open.org/
committees/xliff/documents/xliff.dtd">
to
<!DOCTYPE xliff PUBLIC "-//XLIFF//DTD XLIFF//EN" "D:\xliff.dtd">
where D:\xliff.dtd represents the local location.
8 Review the preview.log for errors. If this file is empty, there were no errors, so proceed with the
import.
9 Repeat these steps for each language you are testing.
For information about how to configure the IOG integration, see Real-Time Decisions (RTD) for Siebel
Intelligent Offer Generation (IOG) Installation and Reference Guide. This guide is available on Oracle
Technology Network (OTN) at http://download.oracle.com/docs/cd/E20657_01/homepage.htm.
The following topic contains information about how to install and configure ACR 626.
464
Supported Devices for Oracle Mobile Sales Assistant
The following are the supported versions for different components for ACR 626:
The following section contains information about known issues with ACR 626.
Calendar Updates Feature Unavailable
Category: Mobile Solutions
Subcategory: Other
Change Request: 12-20SPIQ5
MSA Setting Preference for Calendar Updates available on the MSA client is not supported for the
MSA integration with Siebel On premise for this release. Changing the option between "Changes
Only" and "Download All" has no impact on data downloading behavior.
Users Cannot Add Opportunities from MSA Client
Subcategory: Other
Change Request: 12-20SPIPD
Adding an opportunity from MSA client when integrated with Siebel On premise is not supported for
this release. Editing an available opportunity in MSA client is supported.
Leads Entity Not Supported
Subcategory: Other
Change Request: 12-20W3J8R
Component Supported Version
Client Devices Blackberry smartphone models: 8100, 8110, 8120, 8130, 8220, 8300, 8310,
8320, 8330, 8350, 8520, 8530, 8700, 8703, 8705, 8707, 8800, 8820, 8830,
8900, 9000, 9500, 9530, 9550, 9630
BlackBerry operating system versions: 4.2, 4.3, 4.5, 4.6, 4.7, 5.0
Apple iPhone or iPod touch mobile digital devices operating system version
3.0 or higher
MSA Client Version 2.2.085 for BlackBerry
Version 2.2.100 for iPhone
Oracle SOA Suite 11gR1 PS1
The Leads entity is not supported for MSA integrated with Siebel On Premise. The Leads icon on MSA
is not functional.
Installing ACR 626
NOTE: Make sure that the EAI Component Group is enabled.
1 Navigate to REPPATCH\ACR487_MSA_to_Siebel_Integration_Package.zip, unzip the file, and
import the .sif files into their respective directories.
NOTE: Import all of the .sif files except theones in the Web Services directory, as those files will
be imported separately.To import the symbolic strings, edit the tools.cfg file (located within the
\bin\enu directory) to change the prefix from "X_" to "SBL_", and change the prefix back to "X_"
once you have imported the symbolic strings.
2 In Siebel Tools, using Object Explorer, navigate to Project, and lock the following projects:
Account
Account (SSE)
Contact
Lstofval
Oppty
Division
Activity
Employee
VERT CUT Address
3 In Siebel Tools, select Import from Archive, and within the Import from Archive dialog box, the
"Merge the object definition from the archive file with the definition in the repository" option, and
click Next.
4 Click Yes to grant permission to modify the repository, and then click Finish.
5 Stop the Siebel Server or make sure that it has been stopped.
6 Within Siebel Tools, select Locked Projects, and select the file "SIEBEL_HOME/siebsrvr/OBJECTS/
ENU/siebel_sia.srf" file.
NOTE: "SIEBEL_HOME" is the Siebel installation directory.
7 Click the Compile button
9 Navigate to Site Map > Web Service Administration > Inbound Web Services, and import the
following files:
"SWIAccountNoteServices.XML"
"SWIAccountServices.XML"
466
"SWIActionServices.XML"
"SWIActivityServices.xml"
"SWIAddressServices.xml"
"SWIContactNoteServices.XML"
"SWIContactNoteServices.XML"
"SWIContactServices.XML"
"SWIContactUIServices.XML"
"SWICurrentUserServices.XML"
"SWICustomerParty.XML"
"SWIEmployeeServices.XML"
"SWINoteServices.XML"
"SWIOpportunityServices.XML"
"SWIOpptyServices.XML"
"SWIPickListHierarchicalServices.XML "
"SWISalesMethodServices.XML"
10 Click Clear Cache after you have imported the XML files.
The ACR487_MSA_to_Siebel_Integration_Package.zip file also contains the BPEL/java files required
for Mobile Sales Assistant.
Copy this file to the SOASuite machine and extract the zip to a directory of your choice, and then
follow the steps detailed in Oracle Mobile Sales Assistant Guide to deploy the composites.
In Oracle Mobile Sales Assistant Guide, where it refers to the "bpel" directory, this is the directory
extracted from ACR487_MSA_to_Siebel_Integration_Package.zip
Instructions for BI Publisher Enhancements
For information about how to implement the BI Publisher enhancements, see the Siebel Reports
Guide on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.
Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA Siebel Fix Pack
Siebel Fix Pack Installation Instructions
This topic includes the following subtopics:
Siebel Fix Pack Installation Overview on page 467
Installing the Siebel Fix Pack on Microsoft Windows on page 471
Installing the Siebel Fix Pack on UNIX on page 476
Configuring Slipstream Patch Installation on page 480
Postinstallation Tasks for the Siebel Server on page 482
Postinstallation Tasks for the Web Server on page 482
Postinstallation Tasks for High Interactivity Clients on page 483
Postinstallation Tasks for Supporting Additional Languages on page 483
Uninstalling Siebel Fix Packs on page 485
Siebel Fix Pack Installation Overview
This topic is part of Siebel Fix Pack Installation Instructions on page 467.
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 468
Applicable Base Releases on page 468
About Running Siebel Image Creator on page 469
About Installing Siebel Fix Packs on page 469
About Installing Additional Languages on page 470
About Installing Siebel Quick Fix Releases on page 471
468
Installation Scenarios Described in This Guide
This topic is part of Siebel Fix Pack Installation Overview on page 467.
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 480.
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 469.
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 485.
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 469.
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 470.
Applicable Base Releases
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 Creator
You use the Siebel Image Creator utility to create an installation image (sometimes called a network
image) for version 8.1.1 and for any Siebel Fix Pack 8.1.1.x release. The image can include any
Siebel installable product and language provided as part of this product release.
You can also add products or languages to an existing installation image of the same version, for
products or languages that were not previously included.
Installing any Siebel Business Applications release, including a new installation of version 8.1.1, an
installation of a Siebel Fix Pack 8.1.1.x release, or the addition of one or more languages, must be
done from an installation image created using Image Creator.
NOTE: Always use the version of Siebel Image Creator provided with the Siebel release for which
you are creating the installation image.
Information about using Siebel Image Creator is provided in the Siebel Installation Guide for the
operating system you are using, on the version 8.1 Siebel Bookshelf.
About Installing Siebel Fix Packs
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 468.
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 470 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 469.
470
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 480.
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 482.
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 471.
Related Topics
Installing the Siebel Fix Pack on Microsoft Windows on page 471
Installing the Siebel Fix Pack on UNIX on page 476
Uninstalling Siebel Fix Packs on page 485
About Installing Additional Languages
Include or add all languages you will requirein 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 483.
About Installing Siebel Quick Fix Releases
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 Siebel 8.1.1.x Fix Packs on page 10
Installing the Siebel Fix Pack on Microsoft Windows
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 467.
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 480.
472
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 472
Installing the Fix Pack for Siebel Web Server Extension on Windows on page 473
Installing the Fix Pack for Siebel Management Agent and Siebel Management Server on Windows
on page 473
Installing the Fix Pack for Siebel Mobile Web Client and Siebel Tools on Windows on page 475
Installing the Fix Pack for Siebel Enterprise Server on Windows
This topic is part of Installing the Siebel Fix Pack on Microsoft Windows on page 471.
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 473.
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
Si ebel _I mage\ Wi ndows\ Ser ver \ Si ebel _Ent er pr i se_Ser ver, where:
Siebel_Image is the directory for your version-specific Siebel installation image, such as
C: \ Si ebel _I nst al l _I mage\ 8. 1. 1. x.
4 Double-click set up. 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 Windows
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.
directory where the installer is located. For SWSE, navigate to
Si ebel _I mage\ Wi ndows\ Ser ver \ Si ebel _Web_Ser ver _Ext ensi on, where:
3 Double-click set up. exe to start the SWSE installer for version 8.1.1.x.
installations.
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 482.
Installing the Fix Pack for Siebel Management Agent and Siebel
Management Server on Windows
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 472 instead. See also the Siebel Installation Guide for the operating
system you are using.
474
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 shu t 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.
directory where the installer is located. For Siebel Management Agent, navigate to
Si ebel _I mage\ Wi ndows\ Ser ver \ Si ebel _Management _Agent , where:
3 Double-click set up. exe to start the Siebel Management Agent installer for version 8.1.1.x.
installations.
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.
directory where the installer is located. For Siebel Management Server, navigate to
Si ebel _I mage\ Wi ndows\ Ser ver \ Si ebel _Management _Ser ver, where:
3 Double-click set up. exe to start the Siebel Management Server installer for version 8.1.1.x.
installations.
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 and Siebel Tools
on Windows
Mobile Web Client or Siebel Tools 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.
directory where the installer is located. For example:
For Siebel Mobile Web Client, navigate to
Si ebel _I mage\ Wi ndows\ Cl i ent \ Si ebel _Web_Cl i ent \ Di sk1\ i nst al l
For Siebel Tools, navigate to Si ebel _I mage\ Wi ndows\ Cl i ent \ Si ebel _Tool s\ Di sk1\ i nst al l
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.
476
Installing the Siebel Fix Pack on UNIX
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 467.
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 480.
NOTE: Some Siebel Business Applications products can only be installed on Windows, such as Siebel
Management Server, Siebel Mobile Web Client, or Siebel Tools. For more information, see Installing
the Siebel Fix Pack on Microsoft Windows on page 471.
This topic has the following subtopics:
Installing the Fix Pack for Siebel Enterprise Server on UNIX on page 476
Installing the Fix Pack for Siebel Web Server Extension on UNIX on page 478
Installing the Fix Pack for Siebel Management Agent on UNIX on page 479
Installing the Fix Pack for Siebel Enterprise Server on UNIX
This topic is part of Installing the Siebel Fix Pack on UNIX on page 476.
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 479.
To install the Fix Pack for Siebel Enterprise Server components
1 Stop all running Siebel Servers by running the command st op_ser ver 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 r eset _ser ver al l 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 st op_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 sl i bcl ean
by asking the administrator to change the permission as follows:
chmod 6555 / usr / sbi n/ sl i bcl ean
6 (AIX only) Execute sl i bcl ean, as follows:
/ usr / sbi n/ sl i bcl ean
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 Si ebel _I mage/
UNI X_OS/ Ser ver / Si ebel _Ent er pr i se_Ser ver, where:
/ Si ebel _I nst al l _I mage/ 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 set upUNI X_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 477.
9 (For console mode) Enter the following command to start the Siebel Enterprise Server installer
in console mode for version 8.1.1.x:
set upUNI X_OS i s: j avaconsol e - consol e
where:
(Solaris).
installations.
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.
478
Installing the Fix Pack for Siebel Web Server Extension on UNIX
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:
ompmnct l st opal l - for Oracle HTTP Server (on AIX or supported Linux platforms)
st opapa for other Apache-based Web servers (on AIX, HP-UX, or supported Linux platforms)
st op for Oracle iPlanet Web Server (on Oracle Solaris)
2 Log on to the server using the Web server owner account.
directory where the installer is located. For SWSE, navigate to Si ebel _I mage/ UNI X_OS/ Ser ver /
Si ebel _Web_Ser ver _Ext ensi on, where:
6 (For GUI mode) Run set upUNI X_OS to start the SWSE installer in GUI mode for version 8.1.1.x,
where:
(Solaris).
7 (For console mode) Enter the following command to start the SWSE installer in console mode for
version 8.1.1.x:
where:
(Solaris).
installations.
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 482.
Installing the Fix Pack for Siebel Management Agent on UNIX
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 476 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 473.
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 shu t 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.
480
directory where the installer is located. For Siebel Management Agent, navigate to
Si ebel _I mage/ UNI X_OS/ Ser ver / Si ebel _Management _Agent , where:
5 (For GUI mode) Run set upUNI X_OS to start the Siebel Management Agent installer in GUI mode
for version 8.1.1.x, where:
(Solaris).
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:
(Solaris).
installations.
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 Installation
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 467, 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 470.
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.
[ Sl i pst r eam]
I nst al l 1 = yes
[ I nst al l 1]
Execut e = f ul l _pat h_t o_Si ebel _pr oduct _i nst al l er _execut abl e
Ar g = ar gument
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:
Ar g = - ar gs Pat chI nst ance=$( Si ebel Root ) Sl i pst r eam=yes
Examples for Specifying Execute Parameter
To configure slipstream patch installation for Siebel Enterprise Server version 8.1.1.x on AIX, the
value for Execute might be as follows. (The actual path would show the specific Siebel Fix Pack
8.1.1.x version.)
Execut e = / Si ebel _I mage/ 8. 1. 1. x/ AI X/ Ser ver / Si ebel _Ent er pr i se_Ser ver / set upai x
482
To configure slipstream patch installation for Siebel Web Server Extension 8.1.1.x on Windows, the
value for Execute might be as follows:
Execut e =
C: \ Si ebel _I mage\ 8. 1. 1. x\ Wi ndows\ Ser ver \ Si ebel _Web_Ser ver _Ext ensi on\ set up. exe
Configuring Multiple Slipstream Installations
If, when installing version 8.1.1, you use slipstream installation to install both version 8.1.1.x and a
Quick Fix release for version 8.1.1.x, then you must configure multiple entries in the version 8.1.1
siebel.ini files.
To include the Quick Fix release in the slipstream patching sequence, add I nst al l 2 = yes under the
last entry in the [ Sl i pst r eam] section, then configure an [ I nst al l 2] section for the Quick Fix
release. Configure the [ I nst al l 2] section so it resembles the [ I nst al l 1] section you configured for
the Siebel Fix Pack 8.1.1.x but points to the Quick Fix release instead.
Postinstallation Tasks for the Siebel Server
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 Server
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/ publ i c/ l ang_code/ bui l d_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 SI EBSRVR_ROOT/ webmast er / si ebel _bui l d. The contents of these folders arerefreshed each
time the Web server restarts, or when an administrator enters a Web update command in the
browser. After a build-specific folder is created on the SWSE, folders representing earlier builds are
no longer used.
For more information, see the Siebel Installation Guide for the operating system you are using and
Siebel Security Guide, both on Siebel Bookshelf.
Failure to restart the Web server after installing the Fix Pack for Siebel Enterprise Server components
and for the SWSE means the folders will not be created on the Web server, which causes the Siebel
login screens to stop responding.
Postinstallation Tasks for High Interactivity Clients
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
Languages
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 470.
484
Importing Locale-Specific Data into the Repository
Sometimes it is necessary to update the text strings held in the repository for a particular language
or for multiple languages. These text strings are held in the Symbolic String Model (SSM) table, and
appear on-screen as labels for tabs, fields, and so on, across all Siebel Business Applications.
Updates might be needed either because a string has been incorrectly translated for a particular
language or because installing a patch release has caused a new string or message to appear for all
languages for which Oracle ships language packs for Siebel Business Applications.
NOTE: These instructions are provided for use with any releases to which they apply; they might not
apply for any particular version 8.1.1.x release or language.
The following procedure uses the Locale Management Utility (LMU), which is part of Siebel Tools, to
import an LMU file. An LMU file might contain strings in just one language or in multiple languages.
When running the Locale Management Utility, you can choose to import only the strings for the
languages you are actually using in your installation.
In the procedure, when you are prompted for the file to import, specify the name of the LMU file
provided for the applicable language.
NOTE: Install any applicable Siebel Fix Pack before you run the Locale Management Utility.
For more information about using the Locale Management Utility, see Using Siebel Tools and Siebel
Global Deployment Guide.
To import strings and other locale- specific attributes into the repository
1 In Siebel Tools, choose Tools, then Utilities, and then Locale Management.
The Locale Management Utility appears.
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.
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 Packs
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 485
Instructions for Uninstalling a Siebel Fix Pack on page 486
Guidelines and Limitations for Siebel Fix Pack Uninstallation on page 486
Scenarios for Uninstalling a Siebel Fix Pack
This topic is part of Uninstalling Siebel Fix Packs on page 485.
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
Enhancements and Updates in 8.1.1.x Fix Packs on page 32
Resolved Change Requests on page 487
486
Instructions for Uninstalling a Siebel Fix Pack
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
SI EBEL_ROOT\ _uni nst \ pr oduct \ uni nst al l er . 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 UNI X or Linux platforms
1 To uninstall a Siebel Fix Pack on UNIX or Linux, run the following command:
$SI EBEL_ROOT/ _uni nst / pr oduct / uni nst al l er opt i onal _ar gument s
where:
product is one of the following values: ses (for Siebel Enterprise Server components) or
eappweb (for SWSE)
optional_arguments is one or more valid arguments for the uninstaller. For example, specify
- i s: j avaconsol e - consol e to run in console mode.
2 At the prompt, select Maintenance Release Uninstall.
Guidelines and Limitations for Siebel Fix Pack Uninstallation
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.
Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA Resolved Change
Requests
Resolved Change Requests
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
Unless specifically noted in the table, all known anomalies from the base version remain unresolved.
The tables in this topic provide lists of resolved change requests that are included in 8.1.1.x Fix
Packs. Customers using version 8.1.1 or a prior Siebel Fix Pack 8.1.1.x (where applicable) should
install the latest 8.1.1.x Fix Pack.
Unless specifically noted in these tables, all known anomalies from the base version remain
unresolved. A fix introduced in an earlier maintenance release for a given base version will
automatically be included in later maintenance releases for that same base version.
NOTE: As noted above, Fix Packs are cumulative. However, the Resolved CR information for each Fix
Pack release has been provided in its own table.
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.
Fixed in Version. The version number of the release in which the fix was first introduced.
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.
NOTE: If you have installed a Quick Fix, please review Quick Fixes Included in Siebel 8.1.1.x Fix
Packs on page 10.
This section contains the following:
Requests in the Siebel 8.1.1.4 Fix Pack
488
8.1.1.4 Fix Pack
This topic is part of Resolved Change Requests on page 487.
Table 22 lists the Change Requests that were resolved in the 8.1.1.4 Fix Pack.
Table 22. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
Analytics
RTD
ACR 623: IOG Enhancements
and Certification with RTD 3.0
12-1YM4H1Q 12-1YM4GZ9 8.1.1.4 Yes, see
Instructions for
ACR 623 on
page 463.
Call Center
CTI
Within OSES > Advanced Search
view, pressing Enter to execute
searches does not work
12-1VMB8J9 12-1V418VF 8.1.1.4
Other
When users press Alt F9 (Send
Mail Wireless with SMS
Template), an activity is created
and then deleted
12-1YKOA8M 12-1XVFQ3H 8.1.1.4
Oracle SES
CreateIncrementalIndex
overwrites feed files
12-1WUJ5UX 12-1WQ5PD9 8.1.1.4
Updates the Smart Answer
Admin Tool
12-1Y72XTM 12-1XWEYTD 8.1.1.4
With Siebel Chat, when a chat
contains a percentage sign (%),
the information after the
percentage sign is not sent
12-1Z6EQIH 12-1YOLS71 8.1.1.4
Functionality is not available to
set the owner for Created Email
Outbound Record to the user
who clicked the button
12-1T4H0BC 12-1HE1XTL 8.1.1.4
When users attempt to wrap up
a chat using Shift+Alt+W, the
chat information is not saved,
an error message appears, no
picklist information displays for
the recipient, and no transcript
is attached in an email
12-1VK04GN 12-1VGM2U4 8.1.1.4
When users close a window
using the Close (x) icon, the
application hangs
12-1VM6ZRB 12-1VE77T9 8.1.1.4
Within OSES, when users click
the Search Results link in the
Search view, they receive an
error message
12-1VR72Q7 12-1VNK8MB 8.1.1.4
With OSES, Search Result
Teasers display garbled
characters with the non-enu
content of the UI name
parameter
12-1XANOHD 12-1X65Y3T 8.1.1.4 Yes, see
Instructions for
FR 12-
1XANOHD on
page 738.
For outbound requests, when
users press F9 to send an email
and then navigate to Send
HTML emails > Activity
Comments, the contents are
displaysed without any HTML
tags
12-1XYU5LR 12-1XCM26P 8.1.1.4
Users can select separators in
Search drop-down lists
12-1Y9ZMQB 12-1XM980D 8.1.1.4
For activities, the Owned By
field does not get updated
correctly
12-1TH3VYL 12-1SW8N2H 8.1.1.4
The Lookin drop-down list loses
selections after consecutive
searches on parent categories
12-1Y5LXIO 12-1W7XG6V 8.1.1.4
With OSES, searching does not
work with partial values
12-1YJ7WRD 12-1XM987B 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
490
The All option does not search
on Web datasources
12-1Z0MD73 12-1XM986H 8.1.1.4 Yes, see
Instructions for
FR 12-
1Z0MD73 on
page 725.
With Advanced Search, the
Modified Between Dates option
appears to be caching values
between users
12-1Z7DR3K 12-1YAH4TL 8.1.1.4
It is not possible to search using
exact phrases
12-1ZAR9M8 12-1Z1KQY9 8.1.1.4
Even after QA0150 has been
applied, when users press F9
within the Members List screen,
Internet Explorer hangs
12-1ZB8WZG 12-1YOKFU7 8.1.1.4
When users accept incoming
chats, Siebel Chat displays the
incorrect SR number
12-1ZBPWC2 12-1YAH55T 8.1.1.4
Comm Media
Energy
Assets
Modifying two assets generates
a query with full table scan on
S_ASSET table.
12-1ZM2V2V 12-1ZFBCAH 8.1.1.4 Yes, see
Instructions for
FR 12-
1ZM2V2V on
page 725.
Connectors/EAI
EAI Server
Components
Extends the Siebel web services
framework to provide an
endpoint through Oracle WLS
(ACR 543)
12-1XKSPJH 12-1VMAPI0 8.1.1.4
EAI HTTP Transport hangs when
SOAP response includes special
characters
12-1YR2YDT 12-1YKOJJJ 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
When the EAI Siebel Adapter
cache is released, a crash occurs
12-1Y642Q1 12-1Y28AMJ 8.1.1.4
Siebel EAI queries for all
existing child records when a
new child record is added
12-1XP5RAA 12-1XLAL87 8.1.1.4
EAI Adapter is unable to process
child integration components
that use the same user key
12-1Y285PL 12-1VMAEWV 8.1.1.4
Users experience performance
degradation when using the XML
Hierarchy Converter/ DocToHier
method to convert XML
messages with escaped
characters
12-1YDWEYX 12-1Y8J059 8.1.1.4
Inbound requests to the EAI
Object Manager crash during
EAI task logout/cleanup
12-1YFC9TW 12-1XRKKTV 8.1.1.4
Crashes occur when processing
large attachments (~115) using
EAI
12-1YN3U39 12-1YIQP2P 8.1.1.4
The "UseFormattedValues" user
property for Integration Objects
with DTE causes unexpected
results
12-1YOKV2S 12-1QPSYL1 8.1.1.4
When any Inbound Web Service
is used, when the response is
greater than 51k, the charset-
type is removed from the
content-type HTTP header
parameter
12-1XQ4SDJ 12-1WXWV2P 8.1.1.4
Other
When EAI Siebel Adapter is used
with Query or QueryPage
methods, the SBL-DAT-60180
error message appears
12-1ZOZ5CJ 12-1XBND23 8.1.1.4
There is no support for
homogeneous hierarchies in the
code generator
12-1UI9FGG 12-1GCFOY0 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
492
After 8.1.1 QF00AA has been
applied, problems occur with the
cardinality of child products
12-1XOOB5F 12-1XIVKJJ 8.1.1.4
ACR 480: Deduction Totals are
not updated when payments are
changed under a promotion
12-1ZZ4S3U 12-1V0596T 8.1.1.4
Consumer Sector
Handheld
Users are unable to print voided
invoices
12-1ZD5KI4 12-1Z3IMD9 8.1.1.4 Yes, see
Instructions for
FR 12-1ZD5KI4,
FR 12-
1YZMU0U, FR
12-1Z04AQ7,
and FR 12-
1Z04AS3 on
page 724.
In the Consumer Sector
Handheld application, with
certain records in "FS InvLoc
Product", the InstantiateProduct
method hangs
12-1N1QA5V 12-1JFQEZ6 8.1.1.4
Provides the Void button
functionality for version 8.x that
was available in version 7.7 of
the application (server)
12-1YZMU0U 12-1YOMS98 8.1.1.4 Yes, see
Instructions for
FR 12-1ZD5KI4,
FR 12-
1YZMU0U, FR
12-1Z04AQ7,
and FR 12-
1Z04AS3 on
page 724.
Provides the Void button
functionality for version 8.x that
was available in version 7.7 of
the application
12-1Z04AQ7 12-1YGT6Q9 8.1.1.4 Yes, see
Instructions for
FR 12-1ZD5KI4,
FR 12-
1YZMU0U, FR
12-1Z04AQ7,
and FR 12-
1Z04AS3 on
page 724.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
When users void an invoice that
was paid using a credit memo,
the amount of the credit memo
is not adjusted properly
12-1Z04AS3 12-1YOMS7P 8.1.1.4 Yes, see
Instructions for
FR 12-1ZD5KI4,
FR 12-
1YZMU0U, FR
12-1Z04AQ7,
and FR 12-
1Z04AS3 on
page 724.
Other
Trade Promotions Management
Quickstart (ACR 526)
12-1ZVR7XG 12-1ZVR7O5 8.1.1.4 Yes, see
Instructions for
ACR 526 on
page 382.
Within the Target list applet, the
Copy ADL function sometimes
does not work properly
12-1T9SFNB 12-1TA9LJD 8.1.1.4
The following views are missing
from Consumer Goods Base
options: Catalog Admin Detail
View Products FINS Approval
Administration View
12-1Q7K1G9 12-1P0S6GP 8.1.1.4
ACR480 : Improper error
messages display when users
try to submit funds to
themselves for approval
12-1ZZ4SCG 12-1RVOKYD 8.1.1.4
Improves the quality of the error
messages for the CHS version of
the application
12-1ZZ4SDS 12-1UH86P4 8.1.1.4
12-1ZZ4SF4 12-1UWOE37 8.1.1.4
The Volume Planning Type
default value is not set for
promotions that do not have
plans associated to them.
12-20BQPV1 12-20BQPTP 8.1.1.4
The Warehouse WIthdrawal
Units and Forward Buy Units
values do not autospread from
the promotion level
12-205S6GS 12-204H02Q 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
494
UOM conversion does not
happen for Forward Buy Cases/
Units and Warehouse withdrawal
cases/units
12-205S6GJ 12-204H021 8.1.1.4
Retail Objectives
With Internet Explorer, when
users drill down on an objective
target account and then click the
Back button, context is lost
12-1XF0XUJ 12-1XF0FX9 8.1.1.4
Route Management
In the Routes screen, when
users highlight all of the records
in the Target Accounts tab and
click the Commit button, they
receive the following error
message: "The visit you are
creating overlaps with another
existing visit" (SBL-CNS-00158)
12-1YDWAOE 12-1K5IH9Q 8.1.1.4
Sales Volume
Planning
Performing a Mass Change
causes an infinite loop during
category aggregation
12-1UFAJ7B 12-1U5SBU1 8.1.1.4
Executing the Mass Change
function on Category Baseline
records for a subcategory
causes the application to hang
12-1YCFLBK 12-1XC7KQR 8.1.1.4
Intra-allocation does not work
as expected and drops the
remainder value during
allocation
12-1YJPBKN 12-1YGUPJV 8.1.1.4
Query Assistant returns all
records, regardless of the query
conditions
12-1YOMDX9 12-1BV2Y2P 8.1.1.4
Trade Promotions
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
ACR 358: Accounts are visible in
the Funds screen even though
the Fund Eligible check box is
not selected
12-1ZZ4S5N 12-1K2K8F5 8.1.1.4
ACR 358: When users change
the chargeback resolution status
to void, they receive an error
message that contains no
details
12-1ZZ4S6Z 12-1KC4OQB 8.1.1.4
ACR 358: When users copy a
deduction that has a resolution
record associated with it, they
receive an error message
12-1ZZ4S8E 12-1KEJDM8 8.1.1.4
ACR480: The From and Amount
fields are still editible even after
a Funds Transfer has been
approved
12-1ZZ4S9T 12-1RVOL2V 8.1.1.4
When users attempt to create
child and grandchild accounts to
fund, they receive the following
error message : You have
attempted to insert the value for
column 'FIXED_MDF_AMT' in
table 'S_MDF' twice in the same
statement.(SBL-DAT-00418)
12-1ZZ4SB8 12-1JUZ3ZD 8.1.1.4
Customer Order
Management
Configurator
After users apply 8.1.1 QF00BQ,
they receive an error message
when they attempt the
BeginConfiguration step
12-1ZQWHRQ 12-1ZPH4ZU 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
496
ACR 502 provides the following
Siebel Configurator
enhancements:
The ability to defer an
update within a scripting
event to allow multiple
attribute change even add/
set attribute calls.
A new scripting event to get
product attribute values.
The ability to show/hide UI
controls based on user
properties and the instance
variable values.api method.
12-205G4TZ 12-1LNHQJJ 8.1.1.4 Yes, see
Instructions for
ACR 502 on
page 364.
An incorrect refresh occurs for
user-added business component
fields within eCfg-UI in SI mode
12-1X65SFB 12-1VM9GO3 8.1.1.4 Yes, see
Instructions for
FR 12-1X65SFB
on page 724.
If RaiseErrorText is called within
an eCfg script like on
Cfg_InstInitialize, an error
message should appear in the
response of the calling
webservice
12-1XS1NKP 12-1XO6UN9 8.1.1.4
The ProductConfigurator
BeginConfig Load web service
gets no response with two or
more grandchild products
12-1XYUA5E 12-1XUY3ZF 8.1.1.4
The BeginConfiguration Web
Service should return
<Excluded>true</Excluded>
for component products that
violate product constraints and
eligibility rules
12-1Y2PFJH 12-1Q7NVMV 8.1.1.4
Within Product Configurator, the
Summary tab does not display
products that break eligibility
rules
12-1Y72XPE 12-1XQ4S1X 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
It is not possible to display an
attribute value's language
independent code (LIC value) in
the product configurator web
service response message.
12-1Y902IR 12-1XT16PO 8.1.1.4 Yes, see
Instructions for
FR 12-1Y902IR
on page 724.
When a constraint that uses
"Constrain conditionally"
template fails, the explanation
does not contain the proper
information
12-1YK7CKM 12-1VR7NH8 8.1.1.4
CfgEval expressions that use
"$Cur" in PickSpec UI Properties
do not work correctly for three-
level product hierarchies
12-1YOJV1Z 12-1XWEWDL 8.1.1.4
The Product Configurator Load
operation web service response
has an empty <Item/> tag for
grandchild records
12-1Z04TNB 12-1Y2PC95 8.1.1.4
Attributes cannot be set using
the VBC applet
12-1Z3ZZMT 12-1YZNDJB 8.1.1.4
When users translate
relationships and then step off
of the record, the "Specified
relationship name already
exists, please make sure
relationship names are unique
(SBL-CFG-00102)" error
message occurs
12-1ZM3DNU 12-1Z6VRLF 8.1.1.4
Remote configurator is not
working after patch upgrade
12-1ZZMA8H 12-1WYW4B2 8.1.1.4
ACR 502 :Summary theme is not
coming with products with Quick
edit theme with Tabproduct
theme
12-1ZZMA9H 12-1VNIMC9 8.1.1.4
ACR 502:Explain button is not
throwing any error for
cardinality violation
12-1ZZMAAJ 12-1VNJNK9 8.1.1.4
eSales
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
498
When users select filtered
products and click OK, the
application crashes
12-1Z6EUT7 12-1Z4YJPX 8.1.1.4
Order Management
Product Promotion does not
maintain defaults for products
from parent classes
12-1XJD2O9 12-1XIVLVL 8.1.1.4
After QF0E16 has been installed,
users receive an error message
when validating products
12-1ZA4LHW 12-1YM4QX1 8.1.1.4
Querying in the Promotion
popup applet does not work
12-20OTD3P 12-206F3XH 8.1.1.4
There is no filtering capability in
the Bulk Order Action
component pick applet
12-1TK90K2 12-1SEPT2B 8.1.1.4 Yes, see
Instructions for
FR 12-1TK90K2
on page 723.
Inefficient SQL select
statements are created during
ApplyPromotion
12-1U3KD9O 12-1T2IWYD 8.1.1.4
When users modify assets, they
recieve the SBL-BPR-00183,
SBL-BPR-00162, and SBL-ISS-
00121 error messages
12-1VM8C3T 12-1VM7S6L 8.1.1.4
Bulk Requests that include the
Replace action cause orders to
be generated with incorrect
action codes
12-1VR61KE 12-1VR26EP 8.1.1.4
UMS UI applet does not refresh/
display all buttons
12-1X1B3C6 12-1WUJE2X 8.1.1.4
The Suspend and Resume
workflows add unwanted line
items
12-1XJDJYH 12-1X5627A 8.1.1.4 Yes, see
Instructions for
FR 12-1XJDJYH
on page 722.
Promotion Upgrade does not
work as expected with ACR 471
12-1Y4N1FU 12-1XTBN8V 8.1.1.4
Users receive an error message
when migrating promotions
12-1YCFL9K 12-1Y0AHAJ 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
With Bulk Orders, selected
records are not copied or
displayed on the Instances
applet
12-1YCXTST 12-1Y3OY73 8.1.1.4
The AutoMatch function
incorrectly adds products to
orders
12-1YDWCXG 12-1Y63UOX 8.1.1.4
QF00AW on 8.1.1 has changed
response for web service
AssetManagementComplex
QF00BK Un Installation on WIN
is not reverting back the dll Time
Stamp.
12-1YQ4NCA 12-1YKOYUX 8.1.1.4
When promotions are imported
twice, the same price
adjustment is created twice for
subcomponents with the same
data
12-1Z3152J 12-1YFU2BX 8.1.1.4
The SQL Delete of an Attribute
from a Class is not removing all
support records from the entity
relationships diagram.
12-1Z7DBBN 12-1YOKG0B 8.1.1.4
Promotions Export/Import does
not work for Pricing Adjustments
at the Component Level
12-1ZD654T 12-1YQ37K5 8.1.1.4
Remote configurator is not
working after patch upgrade
12-1ZY61K5 12-1XBNFD5 8.1.1.4
Orders
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
500
enhancements to the Bulk
Orders functionality:
Bulk Promotion Upgrade and
disconnect: Customers can
apply promotions to
products using bulk
requests.
Bulk Quotes: Customers can
create Bulk Quotes.
Agreement and Network
Child Types in Action Set:
Customers can add Network
or Agreement Products in
orders or quotes using Bulk
Requests.
Account Group
Specification: Customers
can use existing account,
contact, or assets lists to
create bulk requests.
Submit Bulk Orders: Bulk
orders can be submitted to
the back office in a single
click from the Bulk Request
screen.
12-1ZUS8XP 12-1ZUS8W7 8.1.1.4 Yes, see
Instructions for
ACR 499 on
page 311.
Products
When users edit product
component relationships, they
12-1YJ7WX1 12-1YDFAIF 8.1.1.4
When products are released for
two concurrently logged-in
users, the SBL-ISS-00121 error
message occurs
12-1X3PGV5 12-1X1SG5R 8.1.1.4
Data Quality
Cleansing
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
Service requests, activities, and
statements are not moved from
a merged member to a surviving
member during member merge
12-1UHQ1L9 12-1U5RB3V 8.1.1.4 Yes, see
Instructions for
FR 12-
1UHQ1L9 on
page 721.
Address cleansing returns
addresses in single parameters
rather than in multiple
parameters
12-1ZFCRF7 12-1YOLRSL 8.1.1.4
Deduplication
ACR 475: Incorrect match
results occur for accounts and
contacts when EAI is used
12-1VNJME1 12-1VNJC3T 8.1.1.4
ACR 475: The batch task does
not end when accounts with
multiple addresses are inserted
using the BDM workflow
12-1VR6B4G 12-1VR2BBP 8.1.1.4
ACR 475: Incorrect matches
occur when an address is
removed from one country and
another country is added
12-1VR6B74 12-1VR3SGC 8.1.1.4
ACR 475: Changing the primary
address to a different country
does not create the record in the
new population
12-1VR6B9Q 12-1VR4QK5 8.1.1.4
ACR475: Changing the primary
contact for an account causes an
error message to appear
12-1VR6BB1 12-1VR4QM7 8.1.1.4
When users run the Batch Data
Matching workflow to match
contact records according to the
contact's [last name] field using
SAP DQ Server, the first run
completes successfully, but the
second batch job immediately
fails
12-20GLHEH 12-1ZZMR15 8.1.1.4
Other
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
502
ACR 475, QF3101: IIR crashes
when posting contacts through
EAI
12-1VR228F 12-1VNJDR2 8.1.1.4
Provides a parameter to turn off
the UCM Data Quality workflows
for ACR 437
12-1VM7P1D 12-1VH3RP7 8.1.1.4
QF3103: The synchronizer
architecture does not support
the MSSQL and DB2 UDB
databases
12-1ZE4T14 12-1ZE4SZN 8.1.1.4
QF3104: When Data Decay
runtime events are on,
associating contacts with
accounts causes an error
message
12-1ZD61KI 12-1Z6ER6J 8.1.1.4
General
Activities
Employee MVG applet data is
erased when changing the
primary employee
12-1Y9ZLKQ 12-1XHFA1T 8.1.1.4
When an Activity is deleted,
under Activity Templates, the
Action business component does
not refresh
12-1YAYCT1 12-1YAH4YV 8.1.1.4
Cost and Price are not converted
on tracker level when the
activity comes from an activity
plan
12-1XLROYV 12-1IKIU3B 8.1.1.4
Application
Deployment Manager
Field 'XliffFileAutoUpdflg'
missing when migrating BIP
Report Template Registration
ADM Data Type
12-1YOKK0R 12-1YOKGBZ 8.1.1.4
Assignment Manager
Multi-Tier Assignment
functionality is missing in Siebel
version 7.8 applications
12-1NTJ04W 12-1M4UP57 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
Audit Trail
The Audit Trail does not capture
cascade deletes on the HLS Case
business component
12-1Y9Z1NN 12-1XSJG29 8.1.1.4
Within the Detail view, the
associate information for the
object being audited is missing
12-1YOK7PR 12-1YKOK4N 8.1.1.4
Business Rules
When calling Haley Expert Rules
knowledge bases, a runtime
error (top-level business
component not configured)
occurs
12-1Y9HL5B 12-1XZBSUD 8.1.1.4
Calendar
Daylight Savings Time (DST)
changes do not occur for
repeating appointments
12-1N1KSBQ 12-1MAMEI5 8.1.1.4
Double-border appears around
meetings on 5-day calendar
screen
12-1ZM2UY9 12-1YTS6AX 8.1.1.4
Events (eEvents) appear in
backwards chronological order
on the monthly event calendar
when events cross multiple days
12-1NUHDPR 12-1NKJK2V 8.1.1.4
Within the Participant
Availability form applet, the Go
button is not translated
12-1PSNEO1 12-1MFY3XO 8.1.1.4
When creating or editing a
calendar item, clearing the
"Type" field and then stepping
off the record throws an error
message, and then the user
cannot clear the error message
12-1YKOARK 12-1Y3OYE1 8.1.1.4
The Monthly calendar does not
respect the First Day of the
Week user property
12-1Z4YXGN 12-1YQ37AZ 8.1.1.4
Correspondence
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
504
When generating a
correspondence document, the
SIEBEL.HTML document
contains non-standard spaces
that appear incorrect in the
generated correspondence
document
12-1OK0VKH 12-1OD185U 8.1.1.4
CRM Desktop
The LOV is missing for the Lotus
meta data file the
"ln_package_res.xml" file
12-1WTKAOZ 12-1WTKAOF 8.1.1.4
Improves the quality of error
messages
12-1Y28CO5 12-1WLULD1 8.1.1.4
File System
Large attachments fail to open
on Linux with multiple
filesystems
12-1XJDI01 12-1WEU3RJ 8.1.1.4
Modified dates of attachments
are updated even if the applet
runtime property is equal to
True in WinXP FAT
12-1YAGYUB 12-1DRKC6T 8.1.1.4
Global/Multilingual
LOV
Strings for icons in Russian
(RUS) are missing in 8.1.1
12-1YOMKFA 12-1YOLRNV 8.1.1.4
Installation
The dmutl2.exe file cannot be
accessed
12-1YUTSZZ 12-1YUTSZ6 8.1.1.4
Siebel Tools Online Help files
were not updated for Siebel
8.1.1
12-1ZV9SEZ 12-1Q35A8A 8.1.1.4
Other
Passing arguments by reference
from within a with block in
escript in the new ST engine
gives incorrect results
12-1VEOXOD 12-1U4I7J7 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
In version 8.0.0.9, there was a
conflict between CR 12-
1U5V2W5 and CR#12-1RSS5TX
that meant that the fix for
CR#12-1RSS5TX could not be
included in the Fix Pack
12-1XUY70M 12-1XP5AGR 8.1.1.4
When instantiating an excel
applicaiton using
COMCreateObject in escript with
the ST engine turned on, the
process does not quit even
though the method
Application.Quit is called
12-1YFTLB8 12-1XWIYRL 8.1.1.4
The escript method
Date.fromSystem() returns the
incorrect time in Linux
12-1YN3WIP 12-1XRKKWD 8.1.1.4
Business service escript is
allowing the custom method to
fall through to C++ code
producing an error.
12-1YOOQQR 12-1YAH50J 8.1.1.4
The Thin Client cannot retrieve
the entire string contained in a
profile attribute
12-1YUWFO2 12-1YOLLSB 8.1.1.4
Calling server script from
browser script in a single
business service causes an error
12-1Z30P3H 12-1Z1KQM1 8.1.1.4
Creating a new buffer where the
input is > 90K causes the
application to hang
12-1ZFBL3U 12-1YNLBB5 8.1.1.4
Business service invocation in
the Application_Start event
using the old escript engine (the
T engine) causes an error
12-1ZJG9IJ 12-1Z3IMBL 8.1.1.4
View Tabs ignore dynamic rules 12-1N1Q7FN 12-1GRZD9P 8.1.1.4
Error messages are not thrown
in eaisiebel.js in the
EAIExecuteMap()
12-1QJ1VFB 12-1QJ1VZN 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
506
Script in the
WebApplet_PreCanInvokeMetho
d event can cause memory use
to increase
12-1VR236Y 12-1V059J1 8.1.1.4
When an error message is
thrown from script in the
Application_PreNavigate event,
the error text is not shown when
navigation to another view is
accomplished using the
browser's back button or the
thread bar
12-1XOOB8H 12-1XIVYP9 8.1.1.4
WebApplet_Load event causes
WriteRecord to occur after it
completes
12-1ZO0KN8 12-1Y3OXW9 8.1.1.4
Values that follow an ampersand
(&) in a URL argument value are
truncated
12-1YOOQSY 12-1BDKMON 8.1.1.4
PIM Server
Integration
The PIMSI Engine crashes when
trying to sync more than 100
users
12-1XTI77K 12-1TK463D 8.1.1.4
The "MultipleEntry" feature does
not work as expected
12-1V7F7Y9 12-1TGNL4T 8.1.1.4
Users are unable to sync
appointments that were created
by non-Exchange users
12-1X8ID6D 12-1VMABYH 8.1.1.4
The user extract start date
feature does not work properly
12-1XPNABN 12-1VNJMW6 8.1.1.4
Outbound appointments are not
retried after a failure
12-1XOOA50 12-1VR2GS3 8.1.1.4
The Outlook Add-in does not
respect the PIMSI Domain
"Category" setting
12-1TYSGWK 12-1TYAXPJ 8.1.1.4
Warnings are incorrectly called
errors in the PIMSI Engine log
12-1VM60MM 12-1VM60LR 8.1.1.4
Remote
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
Database initialization still fails
after QF06AH has been installed
12-1YR2YPR 12-1SM2JSV 8.1.1.4
Internet Explorer cannot display
web page errors on Vista
12-1Q2N41G 12-1PWMKKV 8.1.1.4
Quick start does not work for
non-administrator users on XP
and Vista
12-1VKZHLM 12-1VKZHKI 8.1.1.4
Frequent dbxtract, dbinit and
synchronization leads to
TxnMerger failing on HOR
12-1VM6ZSU 12-1QVMO57 8.1.1.4
ACR 402: Users are unable to
log into the Mobile Web Client
they have rebooted with Quick
Start enabled
12-1VMAK2L 12-1QFPANA 8.1.1.4
Ports QuickStart applications 12-1YOK7QV 12-1X5R8TQ 8.1.1.4 Yes, see
Instructions for
FR 12-
1YOK7QV on
page 721.
On Vista, with Quick Start
enabled, users are unable to log
into the Mobile Web Client after
they restart a machine
12-1YOK7S3 12-1NZ7889 8.1.1.4
With Quick Start enabled, when
the File > Sync DB option is used
after rebooting, the Sync Dialog
box is not visible
12-1YOK7TT 12-1VKYX0H 8.1.1.4
The Quick Start function does
not work on Microsoft Vista
12-1YOK7UR 12-1JNDF6J 8.1.1.4
During Mobile Web Client
synchronization, the SBL-DAT-
00369: Error with the connector
DLL '<?>' has occurred
_SSACreateSqlObj@12 error
message occurs
12-1WF6Q84 12-1VDPBPF 8.1.1.4
Reports Server
Errors occur when running
reports in SI applications (such
as eService, eCustomer)
12-1VNKJIP 12-1V418JR 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
508
BI Publisher reports show
incorrect output when executing
a PDQ and refining the query
12-1YK7EER 12-1XIVLOD 8.1.1.4
BI Publisher report Output type
not visible due to Read Only
View settings
12-1V4JIO9 12-1S1Y205 8.1.1.4
Executing a BI Publisher report
in Split Calendar View does not
display any data.
12-1VR3YGT 12-1VNJ7BV 8.1.1.4
Reports do not work correctly in
disconnected mode
12-1YCG5VU 12-1YCG2PL 8.1.1.4
Siebel Reports Scheduling does
not work when the locale date is
changed
12-1YFC2CA 12-1XLALJV 8.1.1.4
BI Publisher reports with
signature display (LS_RECIPT &
LS_SIGNAD) do not display
signatures correctly on the
mobile client.
12-1YZN89Z 12-1XF0GC9 8.1.1.4 Yes, see
Instructions for
FR 12-
1YZN89Z on
page 721.
Error when executing BI
Publisher report with Oracle
database
NLS_CHARACTERSET=JA16SJIS
12-1XLRL99 12-1VM6MO5 8.1.1.4
Search
Certifies Oracle Secure
Enterprise Search (SES) on the
Oracle 11g platform
12-20CQ1B0 12-20CQ19Q 8.1.1.4
Security
Using AES 256 encryption on
7.8.2.5 SIA causes the Object
Manager to crash
12-1N22I4I 12-1J1ZOUE 8.1.1.4
Using email addresses to
register new ADSI users will
sometimes fail
12-1U0CXTI 12-1TK4UBL 8.1.1.4
Name fields allow scripts to be
executed, which permits
possible XSS attacks
12-1YAGOEH 12-1WUJGPN 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
The Active Directory "Force
password change at next login"
feature yields an error message
12-1YOMH3G 12-1YNKWFD 8.1.1.4
Server Infrastructure
It is necessary to recompile the
SRF to execute scripts for
debugging environment
12-1Y63UTG 12-1U5UGI1 8.1.1.4
SmartScript
After 8.1.1.2 has been installed,
SmartScript buttons do not
allow keyboard clicks
12-1XB5ZLZ 12-1X65YA7 8.1.1.4
Importing SmartScripts in
update mode adds records
instead of updating existing
records
12-1YDEPAU 12-1Y8J0H7 8.1.1.4
System Operation &
Diagnostics
When a cached business service
is called by another business
service through script, the
instance is not correctly
reclaimed and upon logout, a
runtime error may occur
12-1VASVI5 12-1UX6FPL 8.1.1.4
With the standard SRF, the
ePharma ENU application
crashes when Siebel 8.1.1.2 is
installed
12-1XRKLEH 12-1XRKLDV 8.1.1.4
The Object Manager crashes in
version 8.1.1
12-1XUYPKV 12-1XOOC8J 8.1.1.4
After the AES 256 Encryptor has
been enabled, the Siebel Object
Manager crashes
12-1XVXX9N 12-1XP5AVL 8.1.1.4
Custom joins to s_audit_item
cause the SBL-DBC-00105 error
message to appear
12-1U5VBII 12-1U0C8KF 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
510
"Last Updated Source" and "Last
Updated On" are not populated
in the UI in the About Record
window
12-1VUZHOZ 12-1VUZHM8 8.1.1.4
New servers can not be added to
the enterprise.
12-1Y36YRO 12-1Y0AZPB 8.1.1.4
When users log into an Object
Manager as SADMIN, navigate
to Administration - Server
Management > Jobs, run any
job, and review SRProc logs, the
logs show repeated 'SBL-SVR-
01031: Invalid Parameter' error
messages whenever a SQL
statement has parameters
bound to it
12-1YIQJZD 12-1NWCZMB 8.1.1.4
SCBroker crash in 8.1.1.1 on
RHL 5.2
12-1YOLTT3 12-1XTIRJJ 8.1.1.4
Task UI
When a transient business
component is accessed across
two different TBUI views, the
application may not function
properly
12-1X46YC9 12-1V9U49H 8.1.1.4
When multiple languages are
used in TBUI Tasks, even though
the language of Task Name can
be overriden, this does not work
with symbolic strings
12-1X3PH49 12-1X3PPT4 8.1.1.4
Chapter names are not
displaying in the user interface
for a task
12-1X3PH4Y 12-1X3PQB1 8.1.1.4
When users step through
multiple views in a TBUI Task
and then pause the task, the
context field in the Inbox may
still show the output argument
value from a previous task step
12-1ZFBL2R 12-1VJZTJ7 8.1.1.4
Tools/Configuration
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
Siebel Tools sometimes hangs
when applying schema changes
(such as a new extension
column)
12-1SLL0QL 12-1PEQLIL 8.1.1.4
Functions require an extra
leading { in front of the function
body to behave properly
12-1XS1M33 12-1MSV4EV 8.1.1.4
After 8.0.0.2 QF0220 has been
applied, the Web_Applet_Load
events are fired twice each time
the user navigates to a view
12-1XUY6Y9 12-1RSS5TX 8.1.1.4
Checkboxes in the first column
of list applets do not work
correctly
12-1Y63IC7 12-1Y3OY5F 8.1.1.4
applied, the Web_Applet_Load
events are fired twice each time
the user navigates to a view
12-1ZIM652 12-1UIA11Z 8.1.1.4
The Opportunity Form URL
Display Applet displays correctly
when it is placed in a view, but
when it exists as a toggle applet,
the system crashes
12-1N1KLVX 12-1KBLS9L 8.1.1.4
Dynamic Applet Toggle moves
focus to the bottom applet
instead of the parent applet
after toggle
12-1WVI20Z 12-1VR32TN 8.1.1.4
Upgrade
The repository is not in sync
with physical implementation
after an upgrade to a new
database version with LONG
support
12-1YVVM4G 12-1W6DOUA 8.1.1.4
There is no Database
Configuration Wizard support for
the z/OS database in version
8.1.1.3
12-1Y3EOKX 12-1Y37CQ3 8.1.1.4
After users upgrade, revenue
history data is missing
12-1YCFLEM 12-1Y3OXVF 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
512
Workflow
Workflow policies triggered on
extension tables do not fire
actions
12-1R1VXOW 12-1QBCC09 8.1.1.4
Calling asynchronous workflow
processes from scripts causes
runtime errors when logging out
of the application
12-1Y54SUX 12-1XTIR2L 8.1.1.4
Life Sciences
Clinical Account
Profiles
Within Administration - Clinical
(Administrao - Clnica) >
Protocol List (Lista de
protocolos), the title of Cargo is
not correct.
12-1ZYN9IP 12-1TK3LHO 8.1.1.4 Yes, see
Instructions for
FR 12-1ZYN9IP
on page 720.
Clinical Profiles
Within the Clinical Protocol
Regions View, when users click
on subtabs (such as
Attachments or Contacts), the
application refreshes and
displays a different Protocol
Number value than the one that
the users selected
12-1ZUS8M9 12-1VM8M3T 8.1.1.4 Yes, see
Instructions for
FR 12-
1ZUS8M9 on
page 719.
Subject Visit Templates does not
keep the Required flag set for
activities
12-1VM6ZU4 12-1T2ILPP 8.1.1.4
PTCL Region & Site become
invisible if the position that is
removed from the protocol is the
primary at the region or site of
that protocol
12-1YFU2M8 12-1YFU2LN 8.1.1.4
List Management
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
Within Events > Resources >
Staff, when users add two
records, delete one of the
records, and save the remaining
record using CTRL+S, an error
message displays and the
deleted record comes back
12-1Y902JY 12-1WF6IYP 8.1.1.4
Other
Converts the Site Initiation By
Site Actuate report (LS_INBSIT)
to BI Publisher
12-1P4ORNG 12-1OQUM19 8.1.1.4 Yes, see
Instructions for
FR 12-
1P4ORNG on
page 719.
BIP report - Telephone and Fax
Numbers are not displayed in
the expected format
12-1YJ7X13 12-1QCS8LG 8.1.1.4 Yes, see
Instructions for
FR 12-1YJ7X13
on page 718.
Payments
The Payments Exception Query
button does not work properly
12-1YFTGBH 12-1Y0B1UK 8.1.1.4 Yes, see
Instructions for
FR 12-
1YFTGBH on
page 718.
Protocol Builder
BIP: Pharma Site Enrollment
Status By Protocol -
LS_SITENRL
12-1P4ORM0 12-1OQUM7F 8.1.1.4 Yes, see
Instructions for
FR 12-
1P4ORM0 on
page 717.
Converts the Site Initiation By
Protocol Actuate report
(LS_INBPRO) to BI Publisher
12-1P4ORMD 12-1OQUM5W 8.1.1.4 Yes, see
Instructions for
FR 12-
1P4ORMD on
page 716.
Converts the LS Site Initiation
By Region Actuate report
(LS_INBREG) to BI Publisher
12-1P4ORMQ 12-1OQUM4D 8.1.1.4 Yes, see
Instructions for
FR 12-
1P4ORMQ on
page 715.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
514
Converts the LS Region
Document Tracking Actuate
report (LS_TRBREG) to BI
Publisher
12-1P4ORN3 12-1OQUM2S 8.1.1.4 Yes, see
Instructions for
FR 12-
1P4ORN3 on
page 715.
BI Publisher reports are
unavailable for the LS Protocol
Document Tracking Actuate
report (LS_TRBPRO) to BI
Publisher.
12-1P4ORNT 12-1OQULZQ 8.1.1.4 Yes, see
Instructions for
FR 12-
1P4ORNT on
page 714.
Non-applicable visits do not get
deleted when the SVT version is
changed
12-1UI92I9 12-1TK4CFP 8.1.1.4
Position Rolldown shows the
error message: Error SBL-BPR-
00162 fo 'EAI Siebel Adapter'.
12-1Z5203P 12-1R7MY7D 8.1.1.4
Loyalty
Loyalty Customer
Portal
When transactions are moved
between members, accrual
records are not moved
12-1Z3ZZO2 12-1TLCZVH 8.1.1.4 Yes, see
Instructions for
FR 12-
1Z3ZZO2 on
page 713.
Loyalty Engine
The LoyaltyEngineInteractive
Object Manager has a memory
leak of around 88 KB
12-1WB4GPH 12-1VI06M8 8.1.1.4
The LoyaltyEngineRealtime
Object Manager has a memory
leak of around 240KB
12-1WB4GPV 12-1VI06I9 8.1.1.4
The Loyalty Interactive Engine
crashes while processing
redemption transactions
12-1XKTALR 12-1XLAL2N 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
During transaction processing,
the number of open SQL cursors
starts increasing rapidly and
reaches the maximum number
possible
12-1YFC6E8 12-1SW8L6P 8.1.1.4
When point block optimization is
used, the Batch Engine fails
while being shut down
12-1YKOEPX 12-1SK5J9J 8.1.1.4
Slow SQL occurs during the
Real-Time Loyalty Accrual
scenario
12-1VGM3O1 12-1VGM3N7 8.1.1.4
Redemption Cancellation task-
based UI performance is slow
12-1Y90J9T 12-1Y6LBZN 8.1.1.4
Enhancement to accrual
webservice
12-1YDWAPR 12-1XF0FUR 8.1.1.4
Loyalty Manager
When users query within the
Points Balance view, rows
appear that should not be
displayed
12-1XM93ST 12-1XHDRIJ 8.1.1.4 Yes, see
Instructions for
FR 12-
1XM93ST on
page 713.
The LOY Member Service Issue
> Override pay flag does not
allow the Business Service to
continue without the credit card
details being in the service
12-1VM75R7 12-1VM6N5D 8.1.1.4
The Reissue Voucher task-based
UI takes too long to process
transactions
12-1XS21JF 12-1XHF9F1 8.1.1.4 Yes, see
Instructions for
FR 12-1XS21JF
on page 713.
The LOY Batch Enrollment
Service's MemberUpdate
method causes an open query
against all of the business
components that are used in the
service, which results in the
queries taking a long time
12-1YJPCOB 12-1YIQQID 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
516
After two members are merged,
the survivor member cannot
redeem points from the merged
member points
12-1YKOEQV 12-1TUEX22 8.1.1.4 Yes, see
Instructions for
FR 12-
1YKOEQV on
page 712.
Marketing
Campaigns
Campaign repeating tasks may
repeat unexpectedly if record
contention occurs
12-1TKAALE 12-1THO6QN 8.1.1.4
The system allows users to
associate a promoted prospect
to a new list
12-1U5U3TC 12-1TDX5HX 8.1.1.4
Campaign launch fails when
using an internal list with no
prospects
12-1VKZCM4 12-1V4JH1X 8.1.1.4
Queries on My Leads and My
Team's Leads views return all
leads
12-1W7RMKA 12-1VMCEBF 8.1.1.4
In the Campaign Members view,
when users select a prospect
and click the Create Opportunity
button, they receive an error
message
12-1XEJEWF 12-G9NBE5 8.1.1.4
When users chose segments,
the user folder offered is always
the administrator's rather than
the user's
12-1XVXFA2 12-1XIVMBZ 8.1.1.4
User cannot see segments or
lists that were created by other
users in the same group
12-1YSNB9N 12-1Y9HK6T 8.1.1.4
On UNIX-based platforms, one
contact gets missed during 1st
campaign wave assignment
12-1QNF4T7 12-1PZ4R7R 8.1.1.4
Offer Treatments are not copied
with Campaign Template is
applied
12-1S0YVDC 12-1KTY061 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
When contacts are manually
added, Campaign Launch
functionality defaults to a null
wave number
12-1T03JW2 12-1S5BL5P 8.1.1.4
Email and Web
Marketing
Certifies Ektron version 5.2 12-1ZB8X4V 12-1YKOJKX 8.1.1.4
When multiple lists are used, the
wrong emails are sent to
contacts
12-1XHX8U6 12-1WF6ZG1 8.1.1.4
Trackable URLs are not created
correctly if the links include <br.
(Solaris-specific issue)
12-1YR9X61 12-1WLUTXP 8.1.1.4
Many temporary files are
created in the siebsrvr/TEMP
directory when editing mail
templates
12-1YNLA4P 12-1O75I6F 8.1.1.4
Events
An error occurs if two users try
to confirm an event attendee
concurrently
12-1XQ4DQQ 12-1X1RY8J 8.1.1.4
Waitlist count is incremented
when the Allow Waitlist flag is
set to N
12-1YIQBXE 12-1XZBYDT 8.1.1.4
when they click quickly on the
Invite on Event Registration list
12-1US5UG8 12-1S8Q8RN 8.1.1.4
Add to List button on Contact
Category view adds empty
record to list
12-1UZ5SCZ 12-1UI8TSH 8.1.1.4
Waitlist count does not decrease
when the participants who are
waitlisted are cancelled
12-1VR235E 12-1VH3S01 8.1.1.4
Within eEvents version 8.1.1.1,
creating a session takes longer
than in previous versions of the
application
12-1Y36UO3 12-1XC4GYV 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
518
Changes to the Event Plan
Status field automatically
update the event status field
12-1URKHKE 12-1UGQKG7 8.1.1.4
Marketing Server
Campaign load will reject some
rows as errors if the same
contact is targeted with more
than one treatment
12-1UW60OB 12-1UH8JVF 8.1.1.4
The Campaign Load/Campaign
Launch process exits if
Segmentation Engine does not
respond
12-1X5R8D6 12-1VMC65K 8.1.1.4
Other
RTD 3.0: Within the Realtime
Details view, the Sync button,
Last Sync Date field, and the
Need To Sync field should be
disabled
12-1YOMJX3 12-1YOMJWJ 8.1.1.4
RTD 3.0: The Campaign field
should be required for all RTD
offers
12-1YOMN8C 12-1YOMN72 8.1.1.4
RTD 3.0: Stage information
should only include enabled
offers in the eligible offers group
12-1YOMN6R 12-1YOMN57 8.1.1.4
RTD 3.0: Within the Retention
Action view, the Offer Response
buttons should not be enabled
12-1YQGG5W 12-1YQGG4M 8.1.1.4
RTD 3.0: Within Call Center, the
Offer Details view is not
consistent with the display of
attributes
12-1YQGG94 12-1YQGG7U 8.1.1.4
RTD 3.0: The Reason field is not
displayed in the Responses
screen
12-1YQGGAZ 12-1YQGG9F 8.1.1.4
RTD 3.0: For intelligent offers,
the Reason field should not
record responses with "tell me
more
"12-1YQGGEF 12-1YQGGD5 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
Positions added to the Lead
Sales Team MVG are also added
to the last saved Lead record
12-1YOWCFE 12-1XF0G9H 8.1.1.4
In Siebel 8.1.1, the My Leads
view returns an EOF error
message when the owner of a
record is changed
12-1ZB8X0J 12-1XC7L43 8.1.1.4
With RTD 3.0, after users import
SIF files and compile them, the
Contact screen does not display
12-1ZG57E3 12-1ZHAMQF 8.1.1.4
Within the Response screen,
when users click the Campaign
hyperlink, they receive an error
message
12-1ZOZ4CB 12-1ZOZ4A7 8.1.1.4
Within the Retention Action
view, when users click the No
Thank You button, the
application displays a Reason
dialog box .
12-1YQZ29F 12-1YQZ267 8.1.1.4
RTD 3.0: Within Decision Center,
Offers should be listed as Offers
Name
12-1YQGGG0 12-1YQGGEQ 8.1.1.4
Within the List Import tab,
importing a large file creates
garbage characters
12-1Z04TPQ 12-1Y54UZR 8.1.1.4
When users click the Reject Lead
button, they receive the
following error message: The
following error occurs : "An end
of file error has occurred.
Please continue or ask your
systems administrator to check
your application configuration if
the problem persists.(SBL-DAT-
00393). The same error
message occurs when users
click the Retire Lead button.
12-1Z30OQR 12-1WTJXWZ 8.1.1.4
Modifying a lead record
overwrites the Lead Rejected
Time value
12-1Z30OS2 12-1XOOC39 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
520
Within List Management > Lists,
when users select a row where
List Type = "Targeted List", and
click Query, the Content field is
read-only, but when users
cancel the query, select a row
that does not have List Type =
"Targeted List", and click Query,
the Content field is no longer
read only and can be edited.
12-1ZYN2ZW 12-1YCFMMF 8.1.1.4
Response forms that are added
to the treatment template in
default task-based UI tasks are
not converted to HTMLwhen
they are sent
12-1XHWSY8 12-1XHWSXH 8.1.1.4
Programs
Marketing Object Manager may
fail when two users delete a
campaign list at the same time
12-1VR268K 12-1VM5KMF 8.1.1.4
Mobile Solutions
Handheld for Windows
When the Order Signature
Capture applet class is
CSSFrameFSSign, when users
create a new signature and click
either the Store or Clear
signature button, the following
error message occurs: The
specialized method
StoreSignature' is not
supported on Business
Component Order Entry -
Orders' used by Business Object
'Order Entry (Sales)'.
12-1ZFE3KR 12-1YZND55 8.1.1.4 Yes, see
Instructions for
FR 12-1ZFE3KR
on page 711.
Handheld: GetCount TAG from
print tagging language delivers
wrong value
12-1Z6W895 12-1YOK96H 8.1.1.4
Handheld: GetTotal TAG from
print tagging language delivers
wrong value
12-1Z6W8AC 12-1YOKK66 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
When users navigate in the
Billings screen and use the
Signature function, the device
freezes
12-1ZFBR93 12-1YOKK4N 8.1.1.4
The Screen drop-down list does
not appear on the Samsung
Saga device
12-1ZFBLOZ 12-1Z6VW9H 8.1.1.4
Handheld synchronization loops
if the compressed siebel.rml.z
file on the server is bigger than
250000 bytes (244KB)
12-1ZL9LBT 12-1YOKGG5 8.1.1.4
Other
The Mobile Web Client crashes
when script is added to the
Docking Service Business
Service
12-1Y289R5 12-1K501OP 8.1.1.4
Wireless
Integration of Mobile Sales
Assistant to the Siebel On-
Premise application (ACR 626)
12-1TXT8U0 12-1RCXQ1N 8.1.1.4 Yes, see
Instructions for
ACR 626 on
page 463.
Partner
Relationship
Management
Other
If the PRM ANI Utility Service of
EAI Workflow is being called in
the EAI Object Manager many
times (hundreds of thousands of
times) repeatedly, the virtual
memory of EAI Object Manager
increases by about 5 MB for
every 10000 times that the
service is called
12-1X0BIRS 12-1QTP7PD 8.1.1.4
Public Sector
Other
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
522
Customers can not access
Incidents-related views because
of a license-key issue
12-1ZW8OVR 12-1ZW8OV7 8.1.1.4
Sales
Forecasting
Senior levels in the Forecasting
hierarchy are not able to
generate forecasts
12-1XVG7QX 12-1XM98B7 8.1.1.4
After users delete a forecast and
then drill down on another
forecast, they receive the SBL-
DAT-00393 "end of file" error
message
12-1YN3TX3 12-1YCXQYB 8.1.1.4
Other
The Relationship Hierarchy view
allows access to all accounts
across all organizations
12-1YOMKPD 12-1T2ILHX 8.1.1.4
The Next arrow for the "Bill To"
Relationship Hierarchy Tree
Applet does not work
12-1ZL9LEQ 12-1YNLB8N 8.1.1.4
Territory Management
Geo-Zone-based rules for
accounts do not give expected
results
12-1U3BTSP 12-1U0C8HX 8.1.1.4
Service
Other
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
If a manager has more than one
expense report to be approved,
when the manager clicks the
approve button for a expense
report and the cursor is moved
to the next expense report, if
the manager selects On the Last
Record Again and clicks the
approve button,
the manager receives the
following error message:
"End of file error has occured.
system administrator to check
the problem persists.
(SBL-DAT'-00393)".
12-1PQPP5B 12-1PFQSZV 8.1.1.4
The Activity Plan Copy
functionality does not work
properly after case insensitivity
has been implemented
12-1Y37FF1 12-1XZYBNJ 8.1.1.4
Preventive
Maintenance
The Preventive Maintenance
Engine does not release the
database open cursors, which
creates a memory leak
12-1QR9B1Y 12-1Q0IVOB 8.1.1.4
Scheduling
GanttChart AX Applet does not
work in multilingual
environments
12-1RAJ8PX 12-1Q0IVS7 8.1.1.4
Holiday API Service -
IsHoliday() is not working
properly when Exceptions are
used in the Schedule
12-1V6GM1C 12-1UIBDO9 8.1.1.4
SR broker tasks increase when
invoking booking appointments
that integrate with Asgnsrvr
12-1Z7DAAJ 12-1YOLS7V 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
524
Updating an activity does not
generate an update in the FS
Activity Cache Sync business
component
12-1ZFB9X9 12-1YOKGHT 8.1.1.4
Within the Dispatch Board, the
Refresh command switches off
the cache
12-1ZFBA2F 12-1YJP6FL 8.1.1.4
Siebel E-
Commerce for
Comms
Miscellaneous
Child products under a default
CP in an upgraded promotion
are not shown in the Summary
of Changes page
12-1YBWJSS 12-1VCQTQ1 8.1.1.4
Within sales order, the request
dates for line items are being
saved as the request date minus
one
12-1ZOI4IM 12-1ZOI4H7 8.1.1.4
Siebel Self
Service Common
Miscellaneous
Users are unable to launch the
Self-Service URL
12-1Z3HSYD 12-1YOJTGX 8.1.1.4
With different ship-to
information for line items, the
MultipleShipto column shows
"No' in the Review and Submit
page
12-1YBWKB5 12-1V3JPQB 8.1.1.4
Universal
Customer Master
Data Management
QF3104: When users unmerge
contacts from accounts, the
association is not retrieved
12-1ZQWVG8 12-1Z7DQZ9 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
QF3103: The Initial Load
process is not available for
MSSQL DB Type
12-1YNL8YQ 12-1Y9HZTV 8.1.1.4
ACR 475: When multi-lang is
enabled, when users associate a
contact to an account through
the UI, an error message occurs
12-1ZYNASE 12-1ZNIRZH 8.1.1.4
QF3103: The Initial Load
process is not available for IBM
DB2 UDB Type
12-1YNL8XJ 12-1Y9HZWG 8.1.1.4
EAI
ACR 437: With EAI, when
IsPrimaryMVG is set to Y,
records are not updated as
primary
12-1VM871M 12-1VH3RYD 8.1.1.4
Integration
The 'UCM Batch Manager'
Business Service
'ExecutePropSets' method
crashes when querying for an
account produces 0 rows
12-1U0AQT7 12-1IBE8WR 8.1.1.4
AIA responses back to the Si ebel
application return the entire
XML to the Siebel UI
12-1Z7UTPT 12-1Z6VRAB 8.1.1.4
Other
ACR 475: When trying to select
a DnB Account to export to DRM
from UCM, an error message
occurs
12-205XKI9 12-205XKGR 8.1.1.4
ACR 475, Higher Education: The
EIM tables are missing some
data
12-1U5RGGN 12-1TJMH71 8.1.1.4
ACR 475, Higher Education:
There is no text box for the Date
of Birth field
12-1U5RGIV 12-1TK3VIM 8.1.1.4
Data cannot be posted in the
SOAP UI
12-1U5RGM3 12-1TK4OZF 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
526
Phone and Email tabs do not
contain a Delete Record button
12-1U5RGQC 12-1TK962G 8.1.1.4
Country field is missing from the
Constituent main view
12-1U5RH22 12-1TPS1E1 8.1.1.4
Email changes are not reflected
in Email History for constituents
12-1U5RH34 12-1TUWQ23 8.1.1.4
Phone Number changes are not
reflected within Phone History
for constituents
12-1U5RH46 12-1TUW8FW 8.1.1.4
system accepts any phone num
type that is sent in from a web
service call
12-1U5RH58 12-1TUW8IF 8.1.1.4
Users are unable to enter data in
the Personal Address field
12-1U5RIPU 12-1TWTQPT 8.1.1.4
Users are unable to create a
record for affiliation
12-1U5RIR3 12-1TWTQRK 8.1.1.4
During BDM, the institution is
not populated for the Affiliation
integration component
12-1U5RITI 12-1U0A72A 8.1.1.4
ACR 475, DQ: Synchronizer
stops after a few addresses are
selected within Accounts and
Contacts
12-1VR2CAU 12-1VNJ8DR 8.1.1.4
ACR 475: Data matching does
not work for account and
contact records posted through
EAI
12-1VR5FB1 12-1VNJKCG 8.1.1.4
ipmort WSDLs from the build
location
12-1VR5FCC 12-1VNJ8G2 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
ACR 475, QF3101: Sessions are
restarted/the Object Manager
crashes consistently
12-1VR6B35 12-1VR1NO3 8.1.1.4
ACR 475: Users receive an error
message when creating records
through the UI
12-1VR6B5T 12-1VR3RJX 8.1.1.4
ACR 475, DQ: Using EAI, the
Update and Upsert of address
information for contacts does
not occur
12-1VR6B8F 12-1VR4VCC 8.1.1.4
post household data through
EAI
12-1VR6BCC 12-1VR4VUQ 8.1.1.4
Enhances UCM to provide Data
Governance, Data Quality and
Usability enhancements (ACR
475)
12-1X1S0L7 12-1TK672L 8.1.1.4 Yes, see
Instructions for
ACR 475 on
page 248.
QF3105: Within the UCM
Account List Applet, when users
click the Unmerge button to
unmerge a record, the applet
does not display any records
until the user refreshes the
application
12-1ZQWVF9 12-1ZA9UNJ 8.1.1.4
ACR 475: UCM session log off
when trying to save changes
made in DRM (such as adding a
new hierarchy to an existing
version)
12-1ZW8S4J 12-1ZW8S1B 8.1.1.4
ACR 475: The Communication
Address User Key is not
enforced for data inserted in
realtime (UI/WSI)
12-1ZYNARN 12-1Z6WB8N 8.1.1.4
ACR475B: The login for DRM is
hard-coded
12-205G5OJ 12-205G5MC 8.1.1.4
ACR 475: Data loss occurs
during multi-session scenarios
12-207UHWR 12-207UHVB 8.1.1.4
ACR 475, Higher Education: ID
Type Label is missing
12-1U5RGHR 12-1TK3VGV 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
528
Street Address field does not
contain a MVG
12-1U5RGJZ 12-1TK3VKD 8.1.1.4
Streeet Address3 and Street
Addres4 fields cannot be located
12-1U5RGL1 12-1TK4OXO 8.1.1.4
Constituent list applet can only
display four records at a time
12-1U5RGN5 12-1TK9ENW 8.1.1.4
columns meant to be flag
columns for selecting primary
entities are incorrectly named
12-1U5RGO7 12-1TK9B70 8.1.1.4
Affiliate Institute ID is displayed
instead of Institution Name
12-1U5RGP9 12-1TK9B1B 8.1.1.4
External Constituent ID view is
not designed correctly
12-1U5RGRE 12-1TKA445 8.1.1.4
Street Address field and several
other filds are not editable
12-1U5RGSI 12-1TKA4GE 8.1.1.4
Importing data to the LOY
Profiles and Comm Manager
projects fails
12-1U5RGTK 12-1TKA4KE 8.1.1.4
Start/End Date columns should
be named Effective Start/End
Date
12-1U5RGUM 12-1TPS1HM 8.1.1.4
Class Year field does not have
UI-level validations
12-1U5RGVO 12-1TKA9BK 8.1.1.4
Effective Start Date is populated
to the current date for ID,
Affiliations, Name, and Address
12-1U5RGWQ 12-1TK9ZE3 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
ACR 475: The Constituent Main
view design is not in accordance
with the design of the rest of the
application
12-1U5RGYU 12-1TPS15R 8.1.1.4
ACR 475, Higher Education: Not
all fields are editable in the
Personal Address Selection
applet
12-1U5RGZY 12-1TPS192 8.1.1.4
textbox sizes are not standard
within the Constituent view
12-1U5RH10 12-1TPS1BB 8.1.1.4
UCM Batch task errors out
12-1U5RIUN 12-1U0AR67 8.1.1.4
ACR475B: When the Hierarchy
Name information for an orphan
account is changed, the change
is not reflected in the UI
12-205G433 12-204Y7UB 8.1.1.4
ACR475B: If the hierarchy
contains special characters, an
error occurs while trying to
launch DRM
12-205G43L 12-205FPWT 8.1.1.4
Enhances UCM to support the
Higher Education application
(ACR 475A)
12-1U0DSWL 12-1TGO7DJ 8.1.1.4 Yes, see
Instructions for
ACR 475 on
page 248.
The Relationship Hierarchy View
crashes when the number of
records is greater than or equal
to the MaxCursorSize and
PrefetchSize values
12-1XYCTT8 12-1WXWUIF 8.1.1.4
Publish/Subscribe
Publish fails for constituent data
12-1U5RIS6 12-1U0AEGZ 8.1.1.4
Survivorship
ACR 475: Survivorship is not
invoked in transaction manager
12-1VR5FDN 12-1VNKG5Z 8.1.1.4
User Interface
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
530
Controls
Within the calculator function,
when users press the Enter
button, results do not display
12-1XS1MGK 12-1XS1MG0 8.1.1.4
Extra queries are executed when
users click the Back and Forward
browser buttons
12-1Y731MN 12-1V4JFKL 8.1.1.4
The Display_Applet event
causes screens not to display
correctly
12-1NMWHFR 12-1MMQK8H 8.1.1.4
Queries with invalid day
numbers are accepted
12-1VR3S08 12-1VR3RZJ 8.1.1.4
When an HTML form is attached
to a field, an initial save in the
field will work, but subsequent
attempts to modify the field
contents do not work
12-1XBN94Z 12-1WLTVBV 8.1.1.4
History/Back/Refresh
After users click the Back
button, applets are displayed as
form applets instead of as list
applets
12-1VR2ZJV 12-OVT1LK 8.1.1.4
Layout and Rendering
When personalization is used,
form applet field labels do not
appear the first time
12-1VHLJA2 12-1UK0QN1 8.1.1.4
When using run-time events and
personalization rules to drive
toggle applet selection, the first
time that the toggle applet
displays results in an incomplete
display
12-1ZM340L 12-1NVVH71 8.1.1.4
List applets show "hidden" list
columns when users create a
new record
12-1XPMTE7 12-1XC7L61 8.1.1.4
Resizing the screen causes one
applet to be painted on top of
another
12-1RB0A83 12-1R4A19T 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
Toggle applets become
corrupted when a
personalization rule is specified
12-1V9U9X3 12-1U5V2W5 8.1.1.4
Navigation
With Internet Explorer 7, when
users drill down on a link, the
application crashes
12-1YMM6I5 12-1Y54CNH 8.1.1.4
Other
Within Server Reporting,
predefined queries that contain
umlauts do not perform well
12-1ZARFCK 12-1YO2RKX 8.1.1.4
ACR 600: Three shortcut keys
were removed, so the SIF file
does not import properly
12-20QA1DI 12-20QA1AR 8.1.1.4
Popups/Pick Lists/
MVG/Shuttle
With Auto-hide on, closing an
MVG results in a minimized
window
12-1XTI9RZ 12-1XRKL8L 8.1.1.4
Toolbars/Menus/
Keyboard
Pressing the TAB key causes the
focus to jump to the next applet,
not the next field
12-1SC970H 12-1HCLBH7 8.1.1.4
Screen menus stop working
after MVG operations are
cancelled
12-1YOKUKR 12-1YOKG15 8.1.1.4
Web Service
Other
The Siebel application expires
the session token when
SiebelSessionTimeOut value is
less than the
SessionTokenTimeout value
12-20M5KBU 12-20M5KB3 8.1.1.4
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Special
Instructions
532
8.1.1.3 Fix Pack
Table 23 lists the Change Requests that were resolved in the 8.1.1.3 Fix Pack
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Call Center
CTI
After 7.8.2.3 QFJ316 has been
applied, CTI toolbar worker
threads loop infinitely
12-1RRBR7O 12-1REPWYN 8.1.1.3
The Communications toolbar
freezes if it receives an HTTP
message that contains no
content after a push connection
request
12-1S0YVAJ 12-1RXY8FA 8.1.1.3
A crash occurs with
SCCObjMgr_enu on use of
invoking method for invoking a
command on Communication
Session Manager (CSM)
12-1VR7RHL 12-1VNKRB3 8.1.1.3
ACR 574: If the application is
idle for a few hours, users
cannot connect to Smart Answer
Server for KB
12-
1WMU5BW
12-1WFFM67 8.1.1.3
When users send email using the
F9 command, the "To" field is
not being populated
12-1XZTJ3V 12-1XSTNYN 8.1.1.3
Other
Searchable fields in the search
results view are not being shown
12-1PILI7W 12-1ONVDPT 8.1.1.3
RaiseErrorText in PreLeave
prevents SaveUserParameter
from working
12-
1QGOBD8
12-1PSNSBZ 8.1.1.3
When users query in the All
Communications view, the HTML
toolbar is displayed
12-1SSCGFN 12-1SPY0IE 8.1.1.3
Users are not able to change a
default date for Advanced
Search
12-1TUEA6P 12-1SFP9CV 8.1.1.3 Yes, see
Instructions for
FR 12-1TUEA6P
on page 756.
Error SBL-SVR-00006 occurs in
workflows that call Outbound
Communications Manager
12-1U0BJHL 12-1TD6WP5 8.1.1.3
When Search/Find is closed
using the "X" button, the
application navigates to the
login page
12-
1U5QXWD
12-1OFLUA5 8.1.1.3
After indexing certain business
components for mobile search,
the datasource is shown as
"buscomp".
12-1UIAGQE 12-1RKLPVN 8.1.1.3
Field values are erased out after
users cancel the F9 send mail
command
12-1US5UAP 12-1FJKS6A 8.1.1.3
Within the eChannel application,
the Find function is not working
12-1UX632W 12-1UGQKS5 8.1.1.3
When users navigate to the All
Contacts link > All Contacts view
> Contacts view, select a record,
and then press Alt+F9 or
Ctrl+F9 to send a fax or wireless
message, Internet Explorer
hangs
12-1VM90QP 12-1T7D4XN 8.1.1.3
When users select and use a
Simple Email Template that
belongs to a different language,
the Web Client caches that
language
12-1VMB73K 12-1VHLD1H 8.1.1.3
With service requests that have
more than one attachment,
when users select a different
attachment than the one that is
defaulted to and press F9, the
application hangs
12-1VNJLI3 12-1VM81EJ 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
534
ACR 574: Enhances the Smart
Answer Server
12-1WB70VJ 12-1UI8IN7 8.1.1.3 Yes, see
Instructions for
ACR 574 on
page 457.
ACR 574: When an inbound
email is sent that does not
contain a matching string, the
customer does not receive an
acknowledgement email
12-
1WB70WQ
12-1VR6FWO 8.1.1.3
ACR 574: Provides a Refresh
button on the Administration
Catalog screen to allow users to
synchronize the catalog
12-1WB70Z8 12-1VMJW4R 8.1.1.3
ACR 574: Enables error-
handling and logging in Siebel
Smart Answer Connector
12-1WB710H 12-1VNJJXN 8.1.1.3
ACR 574: Users cannot send the
Catalog Name to the Lymba
Adapter with an API call
12-1WEE3SH 12-1VNJJZ2 8.1.1.3
ACR 574: Search Center closes
when users click the Smart
Answer button
12-1WEE3TP 12-1VNJZ8L 8.1.1.3
ACR 574: Smart Answer: Users
are unable to close Search
Center using the X icon in
certain scenarios
12-
1WEE3UU
12-1VNJZ9H 8.1.1.3
ACR 574: Smart Answer: Users
are unable to import language
XML files into the
Knowledgebase catalog within
the Siebel application
12-1WEE3VZ 12-1VR398K 8.1.1.3
ACR 574: AutoResponse exits
with an error and no
autoresponse is sent to the
client
12-1WEE3XE 12-1VR4FMB 8.1.1.3
ACR 574: For some instances of
the Smart Answer process, file
reading fails because of
concurrent access
12-1WEE3YJ 12-1VR4V1B 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
ACR 574: The Smart Answer
Synchronize button is not
translated
12-1WEE3ZV 12-1VR4A7V 8.1.1.3
ACR 574: Auto Response
behavior is inconsistent
12-1WEE410 12-1VR3GUN 8.1.1.3
ACR 574: Lymba Smart Answer:
The Siebel application does not
call the SM component when
agents choose Yes or No for
feedback
12-1WEE425 12-1VR6QRN 8.1.1.3
With ACR 439 installed and with
Internet Explorer as the
browser, when users click the
Back button within Search
Center, and select another
search category and execute the
search, the results of the
previous search still display and
users cannot close out
12-1WLTQ3L 12-1VE7EQ3 8.1.1.3
Object Manager crashes when
indexing 1,000,000 employee
records
12-
1WLUWSV
12-1UH87BR 8.1.1.3
ACR 574: If users perform blank
summary queries on Service
Requests or from Search Center,
they receive the "Smart Answer
component unavailable" error
message
12-
1WMU59O
12-1WCP9WP 8.1.1.3
ACR 574: When Port 1099 is
used, Lymba Smart Answer
server immediately shuts down
with an "unable to connect"
exception
12-
1WMU5A0
12-1WF73FF 8.1.1.3
ACR 574: When multiple emails
are sent or requests are madeto
Smart Answer with a short time
interval,
a mutex error occurs in the
Smart Answer log, and the
Siebel Smart Answer component
is not available
12-
1WMU5AY
12-1WF77PG 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
536
Within the eChannel application,
Binocular Search does not work
12-1X6DJB3 12-1WTJXYN 8.1.1.3
Within CRM Chat, the Spell
Check button does not work
12-1Y36UV1 12-1Y2PWNA 8.1.1.3
Comm Media
Energy
Order Management
Provides support for the OSM
Integration and the Order to
Activate PIP, and forward-ports
MDM for customer and PIM and
Order to Cash enhancements
from 8.x to 8.1.1.
(ACR 474/AIACOMS 2.5)
12-1UJS4WK 12-1TK6U03 8.1.1.3 Yes, see
Instructions for
ACR 474 and ACR
508 on
page 169.
Provides support for the OSM
Integration and new Order to
Activate PIP, and forward-ports
MDM for customer and PIM, and
Order to Cash enhancements
from 8.x to 8.1.1.x
12-1UZ5YMC 12-1UW5DFF 8.1.1.3 Yes, see
Instructions for
ACR 474 and ACR
508 on
page 169.
Provides Order to Activate and
Order to Bill PIP enhancements
12-
1RDW596
12-1R3SHD7 8.1.1.3 Yes, see
Instructions for
ACR 463 on
page 108.
Provides an OSM Integration and
the new Order to Activate PIP
and forward- ports MDM, PIM,
and Order to Cash
enhancements from version 8.x
to version 8.1.1.x
(ACR 474/AIACOMS 2.5.1)
12-1VM9314 12-1VM7OFB 8.1.1.3 Yes, see
Instructions for
ACR 474 and ACR
508 on
page 169.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Supports OSM Integration and
the Order to Activate PIP, and
forward-ports MDM for customer
and PIM, O2C Enhancements
from 8.x to 8.1.1.x
(ACR 474/AIACOMS 2.5.1)
12-1VR3ZSJ 12-1VR2NH1 8.1.1.3 Yes, see
Instructions for
ACR 474 and ACR
508 on
page 169.
Provides Order to Activate and
Order to Bill PIP enhancements
12-1W6062R 12-1R3SHD7 8.1.1.3 Yes, see
Instructions for
ACR 463 on
page 108.
ACR 474: When users create a
Follow On order, an error
message displays
12-1X5NNA5 12-1X56KI9 8.1.1.3
ACR 474: Within the Sales Order
screen, when users create a
sales order and then associate a
price list to it, they receive the
following error messages:
[1] Error invoking service 'Row
Set Transformation Toolkit',
method 'Conditional Action
Transform' at
12-1X5NXC8 12-1X56155 8.1.1.3
ACR 474: Within the Sales Order
screen, when users create a new
sales order, add a product line
item, submit the order, change
the status of the line item and
order header to Complete, and
then click Auto-Asset, they
receive error messages.
12-1X5NXEM 12-1X56KGX 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
538
Enables effective bundling of
products necessary in
communications, finance,
media, and utiltities industries
to enhance promotion
capabilities for component-level
commitment, eligibility in
promotion upgrade, asset-based
recommendations, and split/
merge capabilities of promotions
(ACR 500).
12-1XHX8VP 12-1V41SPV 8.1.1.3 Yes, see
Instructions for
ACR 508 on
page 377.
When users create a new sales
order, add a TBO product to the
order, click Customize, and then
click Done, within Sales Order
line items, the Service Start
Date field is blank
12-1XTI4WC 12-1X0C24K 8.1.1.3 Yes, see
Instructions for
ACR 474 and ACR
508 on
page 169.
Promotional discounts for items
are not being applied to BRM
12-1Y3OPD3 12-1XSJPP1 8.1.1.3 Yes, see
Instructions for
ACR 474 and ACR
508 on
page 169.
Customer service
representatives can delete root
customizable products that have
components that have reached
the "point of no return" in
revised orders
12-1Y36V3X 12-1Y0B1ZJ 8.1.1.3 Yes, see
Instructions for
ACR 474 and ACR
508 on
page 169.
ACR 474: The bar on the line
items view shows a cancelled
status
12-1Y3OPDC 12-1XTI4RH 8.1.1.3 Yes, see
Instructions for
ACR 474 and ACR
508 on
page 169.
ACR 474: Revised orders copy
fulfillment status and status
context from the base order
12-1Y3OPDM 12-1XTI4OQ 8.1.1.3 Yes, see
Instructions for
ACR 474 and ACR
508 on
page 169.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
When Manual Price Override is
updated on a modified order , the
action code is not changed to
'Update
'12-1Y6LFEF 12-1XVFMBA 8.1.1.3 Yes, see
Instructions for
ACR 474 and ACR
508 on
page 169.
Users cannot modify orders to
customize a Service Bundle
12-1Y6LFEP 12-1XSJPMM 8.1.1.3 Yes, see
Instructions for
ACR 474 and ACR
508 on
page 169.
Errors occur when updating the
Part# or inserting a record with
the Part # field populated in the
line
12-1Y6LLL2 12-1Y6LLKD 8.1.1.3 Yes, see
Instructions for
ACR 474 and ACR
508 on
page 169.
When users modify orders, the
Siebel Server crashes
12-1Y6LLLG 12-1XVXEFP 8.1.1.3
ACR 474: Users do not get an
error message in the SOAP
response when they enter the
class release date as DD/MM/YY
format
12-1YIQMGO 12-1U0ATEW 8.1.1.3
ACR 474: The EAI Data
Transformation Engine creates
an empty container in the output
12-1YIQMHB 12-1U0BPB9 8.1.1.3
ACR 474: The application
crashes when users drill down on
a copied order that was created
using the CTRL+B shortcut
12-1YK6THT 12-1U089B9 8.1.1.3 Yes, see
Instructions for
ACR 474 and ACR
508 on
page 169.
Other
ACR 474: Date-time data that is
passed in the payload in UTC
canonical format (such as '2009-
08-14T03:09:01Z')
throws the "cannot convert the
value to Date-Time" error
message
12-1YIQMEE 12-1VR2YCD 8.1.1.3
Connectors/EAI
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
540
Application Svc
Interface/ASI
EAIHttpRespStatus code is set to
the incorrect value on Itanium
systems
12-1RXY7ZA 12-1QNEH19 8.1.1.3
EAI Server
Components
applied, the 'signature' error still
occurs with a SWSE timeout
12-1UI8D5R 12-1U5R29R 8.1.1.3
An error occurs during base64
attachment conversion
(IntObjPS to XMLDoc)
12-1VNJD5G 12-1UX6FV5 8.1.1.3
MQ Receiver Logs contain
unnecessary entries
12-1VR5P25 12-1RAJ0L3 8.1.1.3
Other
Date-time data passed in
payloads in UTC canonical
format (such as '2009-08-
14T03:09:01Z') throws the
"cannot convert the value to
Date-Time" error message
12-1YOLHXJ 12-1YOLHWR 8.1.1.3 Yes, see
Instructions for
FR 12-1YOLHXJ
on page 756.
If a Web service SOAP response
contains a character length
greater than 100 K, then the
Web service errors out
12-1SBR7MX 12-1KXYCJ7 8.1.1.3
EAI HTTP requests should not
send BOM in UTF-16 XML with
byte endian information in the
encoding
12-1U0BRC3 12-1TD6XBN 8.1.1.3
XML Convertor does not
correctly convert property
names that start with a number
12-1VR4PJL 12-1VNJ4JJ 8.1.1.3
VBC-based CSSFABCVRec class
only works for alternate calls
12-1VR4ZV9 12-1VR2PWN 8.1.1.3
EAI Siebel Adapter ignores IC
Field Precision and Scale
settings
12-1WIYSJ4 12-1VR2PRN 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
EAI UI Date Adapter does not
return error messages without
error codes
12-1WV14V4 12-1WVI3Q5 8.1.1.3
Consumer Sector
Handheld
The Cancel Invoice function does
not allow invoices to be marked
for deletion/voided
12-1VMB721 12-1VM6HI1 8.1.1.3 Yes, see
Instructions for
FR 12-1VMB721
and FR 12-
1X0C0IZ on
page 750.
The Book, Cancel, Deliver,
Invoice, and List Product buttons
are disabled
12-1Y4N2FP 12-1Y4N2E7 8.1.1.3
Other
While processing accrual
records, the addition is not
correct for the update to the
S_MDF_ACCRUAL.REVENUE_AM
T field
12-1TPUQPM 12-1TGOA74 8.1.1.3
Customers are not able to void
faulty invoices and undo
payments and delivery for the
faulty invoices
12-1X0C0IZ 12-1VMBL0Z 8.1.1.3 Yes, see
Instructions for
FR 12-1VMB721
and FR 12-
1X0C0IZ on
page 750
Objectives
Error messages that occur
during field validation do not
display correctly
12-1WHFTJD 12-1WF6PQV 8.1.1.3
Sales Volume Planning
Category Aggregation Fields are
not properly populated prior to
aggregation
12-
1NQ7VRQ
12-1KGMH5V 8.1.1.3 Yes, see
Instructions for
FR 12-1NQ7VRO
on page 749.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
542
Export functionality on CG SVP
Catalog Category Product
results in error-SBL-UIF-00146
12-1VK07NT 12-1U09RY5 8.1.1.3
Trade Promotions
ACR 480: Within Corporate
Promotions, the Apply Updates
function pushes products to the
wrong category
12-
1XCMB0W
12-1VR4BZH 8.1.1.3 Yes, see
Instructions for
FR 12-1XCMB0W
on page 747.
Customer Order
Management
Configurator
Applying FR 12-1N7B0OP causes
action codes to be incorrect
12-1VNJ53G 12-1VM83AX 8.1.1.3
With Asset-Based Ordering
enabled, the BeginConfiguration
Web service throws an error
message when loading quotes
from modified assets
12-1WYEK8I 12-1VM6N4J 8.1.1.3 Yes, see
Instructions for
FR 12-1WYEK8I
on page 747.
The LineItemICField user
property does not work for
nested products
12-1XC4G9C 12-1VR66BT 8.1.1.3
Order Management
Enhances the AIA Order-to-Cash
PIP to provide the ability to
change data on the Siebel Order
screen and send the order to E-
Business Suite for processing
(ACR 508).
12-1UZ5YP2 12-1UW5F8T 8.1.1.3 Yes, see
Instructions for
ACR 508 on
page 377.
Enhances the AIA Order-to-Cash
PIP to provide the ability to
change data on the Siebel Order
screen and send the order to E-
Business Suite for processing
(ACR 508).
12-1V2K3L1 12-1V0MXXD 8.1.1.3 Yes, see
Instructions for
ACR 508 on
page 377.
The default cardinalities of
promotion components are not
properly enforced for grandchild
products
12-1VG4IQP 12-1STC0L5 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Signal conditions do not function
appropriately
12-1VLO03W 12-1VDPX7V 8.1.1.3
Promotion Product Defect:
Conditional Constraint does not
resolve properly with Promotion
Attribute Domain Filter
12-1VR1Q8I 12-1VNJ20P 8.1.1.3
With Promotions, a default
attribute values cause an
unresolvable error
12-1VR5DVQ 12-1VNJZD9 8.1.1.3
When a promotion has a
modified relationship domain,
when users click Verify within a
quote, they receive the following
error message:
"Promotion 'Promo' does not
meet the following rules: Promo
has special constrain for product
'Prod1'.
12-
1VR4WHT
12-1VM6B55 8.1.1.3
Batch Validate evalutes
Attributes with Action Code =
Delete, which results in a Batch
Validate error message
12-1VR7NMF 12-1VNJ8NI 8.1.1.3
With promotions, there is an
issue where the constraint and
promotion defintions have
contrasting constraints, and
12-1WF6JAZ 12-1WF5ZQH 8.1.1.3
Bulk Orders: Addresses an issue
where BatchValidate is not
implementing a requires rule.
12-1X0SXWT 12-1VR43FP 8.1.1.3
The SBL-DAT-00500 error
message occurs when the VORD
CPVE Validation business service
is invoked
12-1X5NSWF 12-1WXFOAB 8.1.1.3
Verification of Product
Promotions fails the max
cardinality rules due to
disconnected assets
12-1XT0Z2X 12-1XT180B 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
544
Upgrade Promotion does not
update Action Codes
appropriately, and it does not
upsert components
appropriately
12-1YAH2Q9 12-1RYJL7R 8.1.1.3
Within Promotions, Precision/
Scale deficiencies occur in
Component-Based Pricing
12-1YCX6CX 12-1XRKKYV 8.1.1.3 Yes, see
Instructions for
FR 12-1YCX6CX
on page 746.
Orders
If a CP has lot of rules with
required attributes and the
attributes are not selected,
clicking Verify yields the
Value too long for field 'Return
Message' (maximum size 1000).
(SBL-DAT-00235)
12-1V7FE0H 12-1UWODHL 8.1.1.3
when they add a customizable
product to an order, customize
the order, and then click the
Done button
12-1XTBMZ0 12-1XTBMYB 8.1.1.3
Other
when they upgrade promotions
from Service Account Installed
Assets
12-1X5NS4E 12-1X47HF9 8.1.1.3
Within Bundled Promotions,
defaults via a promotion's
cardinality are not enforced for
Class Product definitions
12-1X65MC7 12-1X3PH1V 8.1.1.3
Pricer
When users invoke the Pricing
Waterfall pick applet, the
application hangs
12-1X5NXAL 12-1W6PXXB 8.1.1.3
Sales Catalog
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
An error occurs when users
disconnect a promotion after a
component of the promotion has
been disconnected
12-1YFTLDP 12-1XB55W9 8.1.1.3
Data Quality
Deduplication
In the Polish (PLK) v8.1.1
version of the application, an
error occurs while running the
SSA Name3 library (n3sgsb)
12-
1VGM2UG
12-1UQ61Q1 8.1.1.3
If the Deduplication popup
applet is the first popup window
for the current session, the
browser hangs
12-1VR7B29 12-1TXBDIV 8.1.1.3
Other
Using ISS with Siebel 8.0 results
in the SBL-DAT-00381 error
message
12-1U0CY1S 12-1STC0TH 8.1.1.3
Financial Services
Other
Within Claims > Loss Details,
the Create Reserves button is
disabled in the Coverages list
applet
12-1Y5LSOW 12-1Y5LSL2 8.1.1.3
Within Claims> Financials, the
New button is disabled in the
Payments list applet
12-
1Y5W0HO
12-1Y5W0GX 8.1.1.3
General
Activities
When users attempt to update
the Planned Date and Due Date
fields using the Action Business
component through workflow
processes, the inserted values
are not saved to the database
12-1R1BTR7 12-1QJ1W43 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
546
Application
Administration
If users do not have the Siebel
administrator privileges/
responsibilities for their
Contacts and Responsibilities,
login fails
12-
1XZMHBG
12-1XZMHAN 8.1.1.3
Assignment Manager
ACR 456: Formats of exported
and imported files should be the
same
12-1TWTYTF 12-1TWTYSQ 8.1.1.3
Audit Trail
The Audit Trail button behaves
inconsistently
12-1SPH0YN 12-1S5B2VD 8.1.1.3
The Audit Trail does not work for
the FINS Claims Reserve Code
Admin business component
12-1SWPT3X 12-1SD8XW1 8.1.1.3
Audit Trail About Record shows
wrong or null data
12-1TK7QD5 12-1T6EFZV 8.1.1.3
When Audit Trail is enabled for a
Long or CLOB column in an
extension table, the delete
operation fails
12-
1V7X3WH
12-1V41905 8.1.1.3
Within the Position business
component, the audit logs
display correct data when the
New or Modify functions are
invoked for Division, Position,
Parent Position, and Position
Type, but the logs do not display
correct data when Delete is
invoked
12-1VBRSC2 12-1VBRSBI 8.1.1.3
Calendar
The Send Email function is
unavailable
12-1N1KL71 12-1K4ZTWH 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Within 7.7x, 7.8.x, 8.0.x, and
8.1.x applications, when users
click the Next button (on the
right-hand side of the Month
picklist) to navigate to the next
month, they are directed to the
incorrect month.
12-
1UMN7BM
12-1UMN79T 8.1.1.3
Toggling applets on the LS
Pharma HI Activity Calendar
View causes a view refresh
12-
1N0KW3X
12-1CANJO7 8.1.1.3
Incorrect background colors on
Currency/Calendar popup
12-1N1KBEQ 12-1IU58IV 8.1.1.3
Changes made to Calendar
dates are not reflected in
Attendee Activities
12-1N1KBVR 12-1EA3KYL 8.1.1.3
The Alarm Manager can be
disabled by editing a text field
12-
1N1KHWC
12-1GK2GR8 8.1.1.3
For repeating appointments,
when users click the Delete This
Appointment button, all of the
appointments are deleted
12-1N1KLLH 12-1K8JU30 8.1.1.3
When users click the New button
in the Calendar applet in the
Home Page view, an 'End of File'
error is generated
12-1O9NHG3 12-1NJLF4A 8.1.1.3
An appointment created by User
A on User B's shared calendar
also appears on User A's
calendar
12-
1P5O1MW
12-1NJLF3J 8.1.1.3
Events that cross a day
boundary are not shown on the
second day
12-1Q3MZVP 12-1OTU3FT 8.1.1.3
When users change the start/
end time for an appointment on
a Calendar Detail applet, the
selected time is not saved
correctly
12-1QU6RIC 12-1QNF2NB 8.1.1.3
Adding employees on Calendar
GanttChart AX Applet is ignored
by screen navigation
12-1TG5AM6 12-1LPLAB7 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
548
Users are allowed to set
Type=NULL on existing
appointments
12-1TK63CO 12-1SF7VWH 8.1.1.3
When users navigate to Site Map
> Calendar view and click the
New Contact Call or the New
Account Call button, the
application hangs
12-1U5U0M0 12-1U5U0KT 8.1.1.3
After users create a new call in
ePharma version 8.1.1, the call
detail fields are greyed out and
uneditable
12-1VJZVMV 12-1V418GZ 8.1.1.3
Duplicate records are displayed
on calendars in the Brasilia time
zone
12-1VM67Y1 12-1THO6TP 8.1.1.3
Within the JPN application, the
weekly calendar view is partially
cut off
12-
1VR7CWB
12-1VR5EY9 8.1.1.3
Within the Portuguese-Brazilian
version of the application, the
week abbreviations display
incorrectly in the calendar popup
12-1VR77QR 12-1VM5K6V 8.1.1.3
Incorrect abbreviation for
Saturday in ESN calendar
12-1VR77RQ 12-1VR2PUZ 8.1.1.3
When users add new contacts or
employees to the calendar, the
application crashes
12-1YM4R1Q 12-1YM4R0X 8.1.1.3
Content Management
When users click the Back
button from within a microsite
within the eCustomer
application, they receive an
error message
12-1P5O1KL 12-1I1GBT5 8.1.1.3
Correspondence
Correspondence documents
contain additional space
characters
12-1T2SVNQ 12-1SJNUGJ 8.1.1.3
CRM Desktop
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
CRM Desktop: Improves the
quality of the 'SBL-DOI-00006'
and 'SBL-DOI-00007' error
messages
12-1Y27VNT 12-1Y27VMJ 8.1.1.3
CRM Desktop: The text in the
"SBL-DOI-00007" error message
is not clear
12-1Y28BQJ 12-1XHWPV2 8.1.1.3
The Import button does not
work on CRM Desktop Admin
Views
12-
1VNKOWM
12-1VNKOUR 8.1.1.3
File System
File System cleanup fails with
the "Failed to open the iterator"
error message
12-1UK14LM 12-1UI9S1Q 8.1.1.3
Installation
In 8.1.1.2, some files related to
siebel_sample_database are
missing
12-1WR7UFE 12-1WR7UEP 8.1.1.3
Siebel Web Client Patchset
8.1.1.1 PTG language is not
applied correctly over 8.1.1 SIA
12-1X663ED 12-1VR46RP 8.1.1.3
Other
Records obtained using the
Access drop-down list display in
Base mode instead of in Edit
mode
12-1SCRGIB 12-1QV5W97 8.1.1.3
COMCreateObject causes error
when object instance set to null
in eScript with Deduce Types set
to True
12-1TJM70N 12-1T12HLZ 8.1.1.3
After 8.0.0.5 QF05AB has been
applied, a scripting error occurs
when calling a method on a
business component
12-1U5UH1R 12-1U5RO9P 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
550
Comparing disparate data types
such as a string to an integer in
eScript using the >, <, >=, <=,
== logical operators causes the
script to exit.
12-1UGZRFB 12-1U0CP53 8.1.1.3
Scripts in the WriteRecord event
of attachment business
components show inconsistent
error message behavior
12-
1UW5AWW
12-1U5VHQV 8.1.1.3
When using the business service
simulator, if a runtime error
occurs when the first method is
invoked and then a second
business service is invoked,
the second business service
displays the error invoked by the
previous business service
12-1V0ND11 12-1UZMXMX 8.1.1.3
RaiseErrorText in SVB when
populated with the Error$
function does not recognize the
return from the Error$ function
and the error message is not
displayed correctly
12-1VCQU0V 12-1V418N3 8.1.1.3
DisableSearch functionality
allows searching on fields
12-1VEOXTT 12-1UI8TH3 8.1.1.3
With 8.1.1.1, calling methods in
objects scripted in Siebel Visual
Basic fails with a runtime error
12-
1VH3RGW
12-1VH3RGB 8.1.1.3
Dynamic drilldowns do not work
when the value of the drilldown
field is changed
12-1VMCEOI 12-1VMCENX 8.1.1.3
The Object Manager crashes
when users generate reports
using Actuate
12-1VR2MU3 12-1DK2UO8 8.1.1.3
Business services are not found
if they are first called in server
script, and then called in
browser script
12-1VR3RGV 12-1VM7TM9 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
The eScript GetMonth method
displays the wrong value on
months with 30 days or more
12-1VR6F3U 12-1VR5H23 8.1.1.3
The ToggleTo SWE method
causes applet runtime error
12-
1WQVBBB
12-1WLTLED 8.1.1.3
The traditional eScript engine
has a runtime error when calling
business service methods
from application object events
such as Application_Start
12-
1WRMDVP
12-1WF6PMP 8.1.1.3
Scripts that placed in the
general declaration sections of
business services only fire once
instead of running once for each
iteration
12-
1WU1SDA
12-FH9TL9 8.1.1.3
RaiseErrorText does not pass
back Error Code or Error
Message to workflow processes
or log files
12-1X1AZTH 12-1WV0HS3 8.1.1.3
The script in the
Application_Start event is not
firing
12-1Y27TNJ 12-1XC7L1L 8.1.1.3
The Data Transformation Engine
does not handle error messages
for invalid dates
12-1YOLHYY 12-1YOLHXV 8.1.1.3
Personalization
It is not possible to use
personalization rules to hide
views dynamically in Siebel 8.0
12-1RV70SJ 12-1JJTA87 8.1.1.3
Hiding an applet with
Personalization causes a corrupt
user interface
12-1VMAFZA 12-1VMAFY3 8.1.1.3
PIM Server
Integration
If an attendee is added to an
Outlook/Exchange calendar item
after the initial sync, the data is
not pushed to the Siebel
database
12-
1VM9ZON
12-1V9UFL1 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
552
When a non-sync enabled user
organizes a meeting and invites
a sync-enabled user, and then
later moves the meeting time,
the meeting time change is not
reflected in the Siebel
application
12-1SPYM2L 12-1S8Q8A5 8.1.1.3
Allows resizing of the Outlook
Add-in window
12-1UI8PUU 12-1S0YE6N 8.1.1.3
Removes the
"ForceAttendeeLowerCase"
parameter from the SSSE
product
12-1VM60QY 12-1VM60PT 8.1.1.3
installed, user-level extract start
date functionality does not work
12-1VM8LG0 12-1VH3ELT 8.1.1.3
Only the first contact invited to a
meeting is synchronized
12-1VR7GA3 12-1VR6AAV 8.1.1.3
Appointments that start before
and end after a Daylight Savings
Time transition are not
synchronized appropriately
12-1WLU29Y 12-1SG6WNZ 8.1.1.3 Yes, see
Instructions for
FR 12-1WLU29Y
on page 746.
If an external organizer invites
two users to a meeting, and one
accepts, then declines before
the second user accepts, a
duplicate meeting is created
12-1X8ID8R 12-1VNK3XP 8.1.1.3
Remote
File System cleanup deletes files
that are referenced
12-1UQ47CQ 12-1UJQWRB 8.1.1.3
After QF05AB has been applied,
when the application is
restarted, TxnProc starts
reprocessing previously routed
transactions
12-
1URKHHM
12-1U0AX75 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
The solution to CR# 12-
1U0AX75 caused the following
issue: when txnproc is restarted
it can display the txnproc status
as Rescan: Operations: <num-
of-opers>" instead of "Copy:
Operations: <num-of-
opers>(the txnproc status
value before fix), in certain
cases
12-
1VNK25W
12-1VNIMYR 8.1.1.3
The ScanAPI.dll fails to load
error messages on the Motorola
SYMBOL scanner
12-1WFVVYB 12-1VR6T39 8.1.1.3
After Siebel 8 Web Client has
been installed on an XP
machine, the machine hangs for
five minutes
12-1WLUUYX 12-1U5R7RT 8.1.1.3
Transaction Processor becomes
slow when it processes large
set-based transactions logged
by EIM
12-
1WYEWYD
12-1T2IN2L 8.1.1.3
Reports Server
Users are not able to add a
sequence number to the Reports
applet in View Association
12-1QCSJZ4 12-1QCSJXR 8.1.1.3
Adds default output type to User
Preferences > Report
Parameters
12-1QG70TR 12-1QG70RX 8.1.1.3
When users run a report, the
Applet Search specification is
not applied
12-
1RDWNBK
12-1Q16OWB 8.1.1.3
Not possible to run multiple
language reports on a single
object manager
12-1SD8MFS 12-1IERLJL 8.1.1.3
The Search Specification field is
read-only for the Primary IO in
the Report Template Integration
Objects view
12-1SG6W3F 12-1PVLXKZ 8.1.1.3 Yes, see
Instructions for
FR 12-1SG6W3F
on page 746.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
554
It is not possible to run a BI
Publisher report for a current
highlighted record or records
12-1SJN8HF 12-1QG70K8 8.1.1.3
Reports are not visible by
position in "My Reports" and
Reports cannot be shared
12-1SZ541H 12-1PBVOVN 8.1.1.3
Users are unable to upload a
updated report template if the
template already exists on the
BIP Server
12-1TK644R 12-1TCP66H 8.1.1.3
With parameterized reports,
when users do not select a
report output type in the
Parameter applet, they receive
an error message
12-1UG999N 12-1UAZJSL 8.1.1.3
Users cannot schedule both
Actuate and BI Publisher reports
12-1UIBFZN 12-1UIBFXT 8.1.1.3
When users schedule a report to
run once, it fails if the month is
set to 10, 11, or 12
12-1VE7GVE 12-1VE7DPF 8.1.1.3
Integration Object Name does
not validate with LOV values
12-1VLO3PN 12-1V7X8ZB 8.1.1.3
When users execute Parent/
Child reports from a My...view,
the reports display only
position-based visibility
rather than displaying all child
records associated to the parent
record (EAI component)
12-1VMA29T 12-1UH87LR 8.1.1.3
When users execute Parent/
Child reports from a My...view,
the reports display only
position-based visibility rather
than displaying all child records
associated to the parent record
(Report component)
12-
1VMA2BM
12-1VKHEG7 8.1.1.3
The BIP Report Wait Time
parameter has no effect
12-
1VMAKQX
12-1QHN64C 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Modifies the Report Output
applet to allow users to query on
output type
12-1VNIO88 12-1VNIO6N 8.1.1.3
Allows uers to run multiple
language reports on a single
Object Manager for XMLP
reports
12-
1VWTRVD
12-1VWTRU1 8.1.1.3
When more than one report is
executed in the same session,
only the first report is displayed
12-
1WCP9GB
12-1VR5SGX 8.1.1.3
Enables query and delete on
additional fields in the Purge
Reports view
12-
1WHOAH7
12-1QD9UWH 8.1.1.3
BI Publisher views are not
displayed based on the Siebel
user language defaults or Object
Manager language/location
12-1WUJ0OL 12-1WQ5P93 8.1.1.3
It is not possible to perform date
calculations in BIP templates
unless the date fields are in
canonical format
12-
1WV0HA1
12-1WV0H8I 8.1.1.3
It is not possible to schedule
reports after the Siebel Reports
Adapter has been applied
12-1X0BJ1E 12-1X0BIZX 8.1.1.3
Corrects instances of BIP to BI
Publisher throughout the
interface
12-1X1AJME 12-1P90KAL 8.1.1.3
The XMLP Report Schedule
Applet is missing German string
values
12-1X1AJS9 12-1VNJS6Z 8.1.1.3
Actuate Report scheduling fails 12-1X1ADBJ 12-1WTJXQV 8.1.1.3
When the BIP Report Wait Time
threshold is exceeded, the
popup window that displays is
not in focus
12-1XANNSX 12-1X3RF25 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
556
When users set a default value
for an LOV parameter in the RTF
template, the default value that
they set does not appear as the
default value in the popup list
applet
12-1XIE4NT 12-1X29VEW 8.1.1.3 Yes, see
Instructions for
FR 12-1XIE4NT
on page 746.
For non-reporting deployments,
sets the system preference
ReportEngineType system
preference to ACTUATE
12-1XOOCIT 12-1XM9LA9 8.1.1.3
Report Administration screen
names display incorrectly
12-1XWFG3I 12-1XWFG1Z 8.1.1.3
Within Administration - BI
Publisher, when users click the
Generate Sample XML button,
an error message appears
12-1YN3MMI 12-1YN3MLR 8.1.1.3
Search
Fields of type DTYPE_PHONE are
not searchable
12-1SPY7BZ 12-1S9QMMD 8.1.1.3
Incremental Index jobs crash
while creating feed files
12-1XFIDCF 12-1XFIDB5 8.1.1.3
The Administration - Search
screen is not accessible
12-1Y90LL6 12-1Y90LJM 8.1.1.3 Yes, see
Instructions for
FR 12-1Y90LL6
on page 746.
Security
eService permits users to log in
with expired LDAP passwords
12-1TI62O9 12-1T2II25 8.1.1.3
Send Email
When users cancel the F9 Send
Mail command, list applets
become unresponsive
12-1U93HR1 12-1TSQ0MP 8.1.1.3
The default values of compiler
define FD_SETSIZE on Solaris
and HP-UX are set too low
12-1O9NH16 12-SNUGZT 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
The 'list stats' and 'list stats for
comp SCCObjMgr_enu' srvrmgr
commands produce an invalid
value-INF-for the CPUTime
statistic
12-1RHA25T 12-1QXJF75 8.1.1.3
Business service instances may
not be deleted from memory
whether the cache flag is set to
True (checked) or False
(unchecked)
12-1RZIYCN 12-1QZYA5Z 8.1.1.3
Object Mananger exits with an
error message when users
cancel the send email or fax
functions
12-1TH3VV7 12-1MANTCD 8.1.1.3
The SiebelAdmin RoleName
parameter cannot be changed
using the Server Manager
command line command
12-1U08CUZ 12-1U08DIB 8.1.1.3
Siebel Object Managers fail
when querying on sessions using
the Server Manager UI
12-1VNJ4VA 12-1VMCEHT 8.1.1.3
Server Manager List Tasks
command performs slowly
12-1XIQSKH 12-1S9QMWN 8.1.1.3
SmartScript
ACR 574: Users are not able to
import different files using the
Smart Answer import button
12-1WB70Y1 12-1VR347X 8.1.1.3
ACR 574: The 'SBL-SMA-00153'
error message is not translated
into German
12-
1WMU59B
12-1VR3957 8.1.1.3
Within Admin - Catalog, when
users select the KB category and
click the Smart Answer
Synchronize button, they
12-1XFZXT4 12-1XFZXSB 8.1.1.3
After users click the Next button
on the last page of a script, and
then click the Finish/Finish Later
button, the application crashes
12-1Y72XA6 12-1Y72X9F 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
558
State Models
State Models with "No Delete"
set do not allow UndoRecord and
cause an error
12-1SK4YF1 12-1S5B2PJ 8.1.1.3
System Operation &
Diagnostics
A Siebel Gateway memory leak
occurs with the DataDirect
ODBC driver on the AIX platform
12-1UI8B4J 12-1U5V32T 8.1.1.3
Stress-testing Web services on
Unix causes communications
failures
12-1UK0UG9 12-1TVDWRD 8.1.1.3
The delete confirmation dialog
box prompt displays incorrectly
12-1VM9XBG 12-1VM9XAP 8.1.1.3
When the system tries to write
log files or FDRs larger than 2GB
to the Linux filesystem, a crash
occurs
12-1VR55QL 12-1VM6N8P 8.1.1.3
Within the LS Pharma
Promotional Items Dropped list
applet, when users click Add, no
data appears on the popup
applet, and the Object Manager
crashes
12-
1WWY5NH
12-1WF6PLV 8.1.1.3
Task UI
Validation of a Transient
Business Component does not
function correctly
12-1QFPEOP 12-1PPACL7 8.1.1.3
When users attempt to activate
a TBUI task within Siebel Tools
when the language is set to JPN,
an error may occur to indicate
that the value is too long for the
current field
12-
1VR5WGT
12-1U5VI79 8.1.1.3
After QF4703 has been applied,
the Siebel client may hang
indefinitely when an invalid
account type is entered in a
TBUI task
12-1X3PA99 12-1WTJXVV 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Tools/Configuration
If script that raises an error
using RaiseErrorText is placed in
the WebApplet_Load event of
some applets, the error is not
displayed, but the entire script is
displayed
12-1QR9AYR 12-1PLG9OF 8.1.1.3
Querying against the Client -
Mobile business component fails
12-
1OEM3OM
12-1NSKPIL 8.1.1.3
The BACKSPACE key does not
work in the Association applet
12-1R1VXR7 12-1Q71PG5 8.1.1.3
Attempting to pick a database
column for a business
component field in 8.0.0.7
causes an SQL error
12-1TK6TMD 12-1TK5I7B 8.1.1.3 Yes, see
Instructions for
FR 12-1TK6TMD
on page 745.
External business component
joins cause Object Manager
errors
12-1U5TVBL 12-1GXKO5H 8.1.1.3
trying to run the
ValidateBuscompCalcExprs
method
12-1YJP5VU 12-1OQDGRJ 8.1.1.3
Upgrade
ACR 529: Provides a single-step
upgrade from Siebel Enterprise
Applications to Siebel Industry
Applications
12-1T5W181 12-1SW8HKB 8.1.1.3
Web Framework
The ShowPopup method cannot
be invoked by a keyboard
accelerator
12-
1VM6NOB
12-1VH3RNJ 8.1.1.3
Workflow
Workflow Simulator crashes at
the LoadInstance (RCOIS BS)
step
12-1RKM7V7 12-1ISLMDM 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
560
Names with spaces get lost
when concurrent tasks are run
on the same MT Server
12-1SFPEXO 12-1IBWHCH 8.1.1.3
When an exception branch leads
to another business service step
that handles the error execution
does not continue to the End
step after the successful
completion of the business
service step
12-1VM96AX 12-1VCQVAZ 8.1.1.3
Workflow process on the
SetFieldValue event are not
working correctly
12-1VMA5PJ 12-1VEOU89 8.1.1.3
Submitting orders through
workflow processes causes
runtime errors, and the orders
have to be reset to Pending
status in order to be able to be
resubmitted
12-
1VR3C6W
12-1UI7QYZ 8.1.1.3
some steps in workflow
processes display errors about
steps without providing detailed
information about what the error
is
12-
1WHMZ4P
12-1WA5CGZ 8.1.1.3
After QF0119 has been installed,
custom error messages do not
display for Stop steps in
workflow processes
12-
1WHMZ5N
12-1WF6G1R 8.1.1.3
When a workflow is revised and
then deployed and activated
using the Publish/Activate
button, Workflow Process
Manager does not recognize the
revised version.
12-1WVIPO5 12-1VR789D 8.1.1.3
Runtime error messages contain
insufficient information
12-1X8QYGX 12-1X65TKV 8.1.1.3
iHelp
Other
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
In Siebel applications version
8.0, the New button is not
highlighted
12-1N1KTE0 12-1L1J856 8.1.1.3 Yes, see
Instructions for
FR 12-1N1KTE0
on page 745.
Life Sciences
Activity
Samples do not display when
using the Inventory field, the Lot
# Tracking field, and the
Inventory by Lot field
12-
1WWY5P4
12-1VR4BT3 8.1.1.3 Yes, see
Instructions for
FR 12-1WWY5P4
on page 742.
Created activities do not appear
in the calendar
12-
1WXFSD8
12-1VR4BVB 8.1.1.3
Clinical Account
Profiles
ACR 539: Modified Protocol site
addresses in the Siebel
application are not getting
updated in Oracle Clinical
12-1Y901CQ 12-1Y901B7 8.1.1.3 Yes, see
Instructions for
ACR 539 on
page 383.
Clinical Manager
Applying an Activity Template
across multiple sites does not
work properly
12-1VR3QRB 12-1VM8H57 8.1.1.3
ACR 539: When the LS Clinical -
ApplyTemplates Process
workflow is run through
Workflow Process Manager, an
exception occurs
12-1VUZHHE 12-1VR6AOT 8.1.1.3
ACR 539: Visit Sequence does
not get copied over from the
Subject visit template
12-1X1S0P0 12-1OOD149 8.1.1.3 Yes, see
Instructions for
FR 12-1X1S0P0
on page 744.
Clinical Profiles
ACR 539: When the
ApplyTemplate workflow is
triggered through the UI,
refresh does not occur
12-
1WB70O1
12-1VR73HT 8.1.1.3 Yes, see
Instructions for
ACR 539 on
page 383.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
562
ACR 539: Search Center should
accept incoming ICDs from
Order to Cash and default only
when the date is unavailable
12-1X1S02N 12-1X0BGMO 8.1.1.3 Yes, see
Instructions for
ACR 539 on
page 383.
ACR 539: The Primary Site
Address pick applet field accepts
arbitrary values
12-1X4OYJB 12-1WF73ZD 8.1.1.3 Yes, see
Instructions for
ACR 539 on
page 383.
Modifies the Siebel Clinical
product to support the Study,
Subject, and Visit
Synchronization Process
Integration Pack for Siebel
Clinical and Oracle Clinical. This
enhancement also provides a
way to accurately track and
respond to issues related to site
performance and protocol
adherence. (ACR 539)
12-
1WB70MX
12-1TK4DJP 8.1.1.3 Yes, see
Instructions for
ACR 539 on
page 383.
The SWI LS Clinical Subject
Inbound - Subject" workflow
does not work when the
<clin:InformedConsentSignedD
ate></
clin:InformedConsentSignedDat
e> tag does not exist in the
WSDL
12-1Y6LNZN 12-1Y54O9K 8.1.1.3 Yes, see
Instructions for
ACR 539 on
page 383.
ACR 539: Incoming NULL ICDs
from Oracle Clinical update valid
existing ICDs for subjects in
Siebel Clinical
12-1Y6LO7Y 12-1Y54O8F 8.1.1.3 Yes, see
Instructions for
ACR 539 on
page 383.
ACR 539: The status of subjects
still displays as Screened after
the enrollment date has been
entered
12-1Y8IUF9 12-1Y8IUEI 8.1.1.3 Yes, see
Instructions for
ACR 539 on
page 383.
eMedEd
Adds electronic medical device
reporting to the AECM module
(ACR 426).
12-1X0TENB 12-1OJC7XR 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
ACR 426: After ACR 426 has
been installed and configured,
the Transmit button is disabled
12-1Y3OEAS 12-1Y36V4H 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
Medical Education
ACR 426: B2 values are not
displayed in XML
12-1XF0LI1 12-1R851IL 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
Other
ACR 426: The flag for
Transmitted-Rejected does not
display
12-1S987UE 12-1R8LVJT 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
ACR 426: The Reg Report view
displays eMDR status for an RR
that is not in the eMDR queue
yet
12-
1U5D3W7
12-1S99GKY 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
ACR 426: When existing
Regulatory Reports are
escalated to the eMDR queue
after eMDR has been installed,
the Transmission Status & eMDR
Status fields for those records is
blank
12-1U5D3ZB 12-1SFOTGX 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
ACR 426: Phone numbers of
manufacturers or distributors do
not display in accordance with
the XML path given
12-1U5D45C 12-1TBJW6J 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
ACR 426: Manufacturer
telephone numbers are not
displayed in the (xxx) xxx-xxxx
format
12-1VNIPV7 12-1VKYUHX 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
ACR 426: The FDA Status field is
not being updated correctly
12-1VNIQ18 12-1U5TKPH 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
564
ACR 426: Manufacturer
telephone numbers entered into
the screen are not displayed in
the XML
12-1VNIQ4C 12-1U5U51Y 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
ACR 426: It is not possible to
trace the path for the fields in
XML
12-1VNJ2JW 12-1R8M1X4 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
Within Site Management >
Protocol Site List, when users
create a new site record and
make it active, and then create a
subject, the Screen, Rescreen,
and Enroll functions do not work
properly
12-1XOOAJ7 12-1XOO8RJ 8.1.1.3
ACR 426: The eMDR LOV is
missing and there is a typo
within Accepted; LOV Type =
LS_MED_RR_TRANS_SUB_STAT
US
12-1XF0LCT 12-1R6NTLT 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
ACR 426: The F10 values are not
found in the path for patient
code in the XML, and the F11
values are not present in the
XML
12-1XF0LJ2 12-1R9TWH2 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
ACR 426: Provides batch files for
importing .sif files and seed data
for ACR 426 and for ACR 372 as
well
12-1XF0LD4 12-1R6NTMI 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
ACR 426: When a record is
selected in the Siebel application
and the FDA sends an
acknowledgement, the
Transmission status is not
updated
12-1XF0LE3 12-1R6NTPL 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
ACR 426: The F13 value is not
populated in the XML
12-1XF0LG3 12-1R8LVMN 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
ACR426: The B1 Code for the AE
Drug event type is not displayed
in XML
12-1XF0LH2 12-1R8LVO2 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
ACR 426: If the Regulatory
Report View already contains
records of type 3500A, when
eMDR patch is applied, the same
records cannot be transmitted
because the Transmit button is
disabled
12-1XF0LL7 12-1S0YLCP 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
ACR426: If multiple
Concomitant Product codes are
selected, the corresponding
values are not displayed
12-1XF0LN5 12-1S0YLFX 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
Site Management: Users receive
an error message when
selecting an account to create a
new site
12-1XONPTL 12-1XIE5IH 8.1.1.3
Assigning/Autodelete
functionality for Team members
does not work as expected
12-1YDETC0 12-1XYC96B 8.1.1.3 Yes, see
Instructions for
FR 12-1YDETC0
on page 740.
Within Call Activity, when users
create a new call, and then click
the Add button in the Sample
Drop applet, they receive an
error message
12-1YJ865O 12-1YIQ3XG 8.1.1.3
Pharma Handheld for
Windows
The Busy icon is sometimes not
cleared even though the
application is ready for the next
steps
12-
1WXFSAM
12-1V6XL7R 8.1.1.3
Protocol Builder
Users are unable to apply a new
subject visit template in order to
create subject visits.
12-1TQTU4C 12-1NWCZ7B 8.1.1.3 Yes, see
Instructions for
FR 12-1TQTU4C
on page 739.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
566
Regulatory Reports
Adds electronic medical device
reporting to the AECM module
(ACR 426)
12-1U5D3P7 12-1U0ASU4 8.1.1.3 Yes, see
Instructions for
ACR 426 on
page 71.
Trip Reports
In the Trip Report Details view,
after users select a trip report
template, do not update the
checklist items, and then try to
generate a BI Publisher report,
the application yields an error
message
12-1VR2857 12-1UIB7XV 8.1.1.3
Loyalty
Loyalty Customer
Portal
An error occurs while generating
statements for post-paid
partners
12-1VR4PXA 12-1VMCEM9 8.1.1.3
Loyalty Engine
When the LOY Batch Enrollment
Service is used, cursors are not
being released
12-1VM86N5 12-1VM72OT 8.1.1.3
Enrollment Web services fail
when the number of concurrent
users is above 30
12-1VMA8YH 12-1VE7EH7 8.1.1.3
Accrual Template Validation on
using Workflow/EAI Adapter
12-1WAYNKL 12-1VMAEXZ 8.1.1.3
The Loyalty Batch Engine task
exits with Error ORA-01000:
maximum open cursors
exceeded
12-1WF753R 12-1VROIM3 8.1.1.3
Custom Attributes are not
recalculated correctly
12-
1WLU9WG
12-1WF6P3J 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
There is no user property to
control point expiry based on
transaction date instead of the
processing date
12-1WVIKCQ 12-1WVIKB5 8.1.1.3 Yes, see
Instructions for
FR 12-1WVIKCQ
on page 738.
The Redemption Services Get
Quote method crashes
12-1X65TII 12-1WXX8FJ 8.1.1.3
Loyalty Manager
The Voucher validity business
service does not return a failed
verification when a voucher is
used or expired
12-1VMBCJG 12-1VMAXQF 8.1.1.3
Marketing
Campaigns
Stage Execution fails with the
error that the record has been
modified by another user
12-1SX7SLV 12-1STTN3F 8.1.1.3
List Import of the Prospect
object on Siebel 8.1.1 exhibits a
memory leak on the Workflow
Process Manager component
12-1VM5JXR 12-1VCQAE7 8.1.1.3
Deleted segments and segment
trees are still being used in
allocations
12-1VM7HXI 12-1VM7HW1 8.1.1.3
Wave Numbers are not assigned
to Control Group records
12-
1WUJ5W5
12-1VMC9ID 8.1.1.3 Yes, see
Instructions for
FR 12-1WUJ5W5
on page 739.
Campaign launch fails 12-1XSJLCF 12-1XSJLAV 8.1.1.3
Email and Web
Marketing
Database cursors left open after
launching email campaigns can
result in "ORA-1000" errors
12-1OK5WI5 12-1MM7CTD 8.1.1.3
The Test Email feature does not
use the delivery profile of the
email treatment
12-1VOEV3S 12-1VNJHQ0 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
568
Saving the HTML template for an
email treatment incorrectly
modifies links that include the
<style> attribute
12-1WF61M1 12-1W4M5S2 8.1.1.3
Saving the HTML template for an
email treatment incorrectly
modifies links that include target
information
12-1WVI96L 12-1W4M5R5 8.1.1.3
Marketing Server
Campaign load rejects some
rows as errors if same contact is
targeted with more than one
treatment
12-
1SSCMNU
12-1RVO17F 8.1.1.3
Repeating list import jobs try to
repeat with the same start date
as previous job
12-1UZ5H5D 12-1UU5KV9 8.1.1.3
List Import Exception Files do
not provide business-user-
friendly error messages
12-1V6XLVX 12-1UJQNRZ 8.1.1.3
Allocation of internal lists across
multiple treatments in a single
row yields the wrong results
12-1VHLD6X 12-1V7WVM7 8.1.1.3
Users are unable to create a lead
with a prospect using the default
Siebel 8.1 LeadService
:CreateLead Web
12-1VR2F30 12-1VH3RCZ 8.1.1.3
Token numbers are not
generated correctly when Allow
Repeated Contacts Within Load
is checked
12-1VR3DQV 12-1VMBTV1 8.1.1.3
List Import does not allow users
to select an existing mapping
12-1XPMR57 12-1XCM9RR 8.1.1.3
Other
A lead is still associated to a
prospect after the prospect is
promoted
12-1VM6EMK 12-1VM6ELV 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
The Lead Import process hangs
when there are exceptions in the
import file
12-1WYVV8E 12-1WYVV7P 8.1.1.3
Mobile Solutions
Handheld PatchAgent fails when
UserDefinedLang=Y and the
userstr.txt file exists on the PDA
device
12-1Q0MF5H 12-1PPAE9M 8.1.1.3
After users perform a Full Sync
on the device side, create some
transactions, sync, and then
select Upload Now, Auto
Download Later option, the
Siebel Handheld Sync screen
signs off with no transaction
errors. However, when the
device starts to poll the server
for the extracted database file,
the first polling attempt is
successful, but the second
polling attempt fails.
12-1RAJ8KY 12-1NG9XVD 8.1.1.3
Handheld, Store-and-Forward
messages on the PDA appear
only in ENU, regardless of the
the Siebel language on the PDA
12-1VM5JWF 12-1VBATI1 8.1.1.3
Handheld: When an activity is
created using the calendar, the
PreDefault value for the Type
field is ignored
12-1VNJY2K 12-1VNJY1R 8.1.1.3
Within Handheld tree applets,
occasionally the context gets
lost
12-1VR5Q6M 12-1VMBHFJ 8.1.1.3
After the 7.8.2.13 Fix Pack has
been applied, there is a problem
with calendar display, and the
issue applies to version 8.0.x
and 8.1.1.x applications as well
12-1WVI1ZR 12-1WQNSKV 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
570
Handheld with VGA-style
resolutions: Users cannot select
the time in the Calendar popup
window
12-1WXFSBX 12-1VNJH0Z 8.1.1.3
Handheld daily calendar: when
users change the month or the
year in Date popup window, an
exception occurs
12-1WXFSEJ 12-1WCP7ZT 8.1.1.3
With Windows Mobile 6.1.4, the
Setting Filters drop-down list
does not open during
synchronization
12-1X46WK5 12-1X1S03V 8.1.1.3
Tree Applet Recursive
12-1XC6WS4 12-1U5VI4H 8.1.1.3
Parent applets are not being
refreshed
12-1XRK5TV 12-1XRK5SR 8.1.1.3
When users perform the SMQ set
up for Siebel Service, install the
Service application for
Handheld, perform the initial
sync, navigate to the Activity
screen, and create a new
activity, the new activity screen
opens with old record entries
12-1XS220M 12-1XS21ZV 8.1.1.3
Other
Case Insensitivity and Accent
Insensitivity (CIAI) does not
work on the local database
12-1Q06NYO 12-1JNWG6G 8.1.1.3
Store-and-Forward
Messaging
Handheld, Store-and-Forward
messages on the PDA appear
only in ENU, regardless of the
Siebel language on the PDA
12-1VMBFQI 12-1U5TD5N 8.1.1.3
When QF0682 has been applied,
when the Handheld Object
Manager is unavailable, SMQ
messages are lost
12-1VR24OB 12-1TK9JRL 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Partner
Relationship
Management
Partner Manager
After users register a partner , no
records display in the Qualified
Partners view
12-1X668T1 12-1WF6FQC 8.1.1.3
Public Sector
Other
After an application has been
submitted, the Upload button is
still enabled
12-1Y5OQS8 12-1Y5MGFN 8.1.1.3
Section 508/
Accessibility
ACR 562: Provides Accessibility
enhancements for Siebel version
8.1.1.x applications.
For more detailed information
about what ACR 562 provides,
see Enhancements and Updates
in Version 8.1.1.3 on page 34.
12-1WU188L 12-1W6DOPP 8.1.1.3 Yes, see
Instructions for
ACR 562 on
page 412.
Sales
Forecasting
When users apply ACR 448,
perform the required
configuration changes, log in as
SADMIN, create a forecast
series, generate it, and then
navigate to Site Map > Forecast
> Spread Sheet (Summary), it
contains only one forecast
without a forecast date
12-1S0YV7A 12-1RXL8ET 8.1.1.3
Supports the Spreadsheet view
under the Summary tab
12-1S6AJ9P 12-1M5CV1E 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
572
In the Forecast Series
Organization view, if
participants are not added, the
12-1XCLVSZ 12-1X3PRS9 8.1.1.3
After QF0215 or QF0173 has
been applied, forecast
generation takes longer than
expected
12-1XRKN34 12-1XRKN1L 8.1.1.3
Opportunities
Numeric and picklist fields
temporarily blank out after
Siebel 7.7.2.8 has been applied
12-1XIVK5N 12-1JD9K31 8.1.1.3
Service
Contracts
Auto entitlements does not
apply the template information
to all line items
12-1SZMNL2 12-1RPRACV 8.1.1.3
Other
Within eService > Advanced
Search, searching with the All
option does not work
12-1VR5LU1 12-1VMAF2Z 8.1.1.3
Within the eSales application >
OSES > the Results per Page
preference does not work when
it is set as 15, 20, or 25
12-1VR7KJC 12-1HWWAY4 8.1.1.3
The hour unit does not work for
any start time for the
GetElapsed method
12-1X65BT0 12-1WXXADT 8.1.1.3
Preventive
Maintenance
The Preventive Maintenance
Engine crashes
12-1VBATMM 12-1TAR4ZP 8.1.1.3
Scheduling
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
The Load ABS function does not
work correctly right after the
Siebel Server service has been
restarted
12-1U5RX6U 12-1REV4NL 8.1.1.3
The Book Appointment Process
is terminated
12-1VR7Q81 12-1V418SN 8.1.1.3
Siebel Email
Response
General
Provides an addtional output
argument from the
CreateRequest method from the
Outbound Communications
Manager business service to
return the activity id of the
outbound email activity
generated automatically by the
CreateRequest method
12-1S1XENY 12-1JGY6HC 8.1.1.3
users press F9 to send an email,
the application loses focus, and
the text that users have entered
into the mail is not saved
12-1UIB3AO 12-1U0COUJ 8.1.1.3
The Communication Detail -
Response view is read-only
12-1XF0MTB 12-1X6681L 8.1.1.3
Siebel Self
Service eCommon
Miscellaneous
Users cannot configure a CP in a
promotion
12-1Y55X9A 12-1Y55X7M 8.1.1.3
User Interface
Controls
Form Redirect uses POST as the
default and not GET
12-1QKI632 12-1O2IS17 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
574
When using script to set the
properties of a control's label
using the SetLabelProperty
method and when navigating to
the Show More view, the
"Cannot bind to source" error
message appears
12-
1QMFHYW
12-1DNMXIW 8.1.1.3
The Siebel PRINT function
executes Javascript or other
code that is part of the data
being printed
12-1VABVRY 12-1UZO2A9 8.1.1.3
Provides an option to either
suppress or display the leading
zero on telephone numbers
12-1WYEFRX 12-5PSXQ8 8.1.1.3
With Internet Explorer 8, the
application hangs if a popup
window or MVG is invoked
multiple times
12-1XANXNP 12-1X1AZAL 8.1.1.3
The Site Map and controls in the
toolbars are not visible
12-
1XQLNOO
12-1XQLNN9 8.1.1.3
Spell Check does not work 12-1YAH2YE 12-1XZBT2P 8.1.1.3
History/Back/Refresh
Thread bar navigation does not
work when view names contain
special characters
12-1TJM5Y1 12-1NXS3RV 8.1.1.3
When users click F9 and open an
email, the text that is copied and
pasted into the email window
gets truncated
12-1N1L2OD 12-1LC1A2Z 8.1.1.3
Declaring a regional phone
number format does not work in
Siebel 8.0.0.5
12-
1S7PQSW
12-1RAJ08L 8.1.1.3
Error messages in SI mode are
written into the Siebel toolbar
12-1UAGKY7 12-1U5SY53 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
When users press CTRL+N, a
new record is added, but the
focus remains on the last field
selected in the previous record
12-1VR2MJO 12-1VM6N0D 8.1.1.3
Vertical separator lines in list
applets that appeared in Siebel
version 7.x applications do not
display in version 8.0.x or
8.1.1.x applications
12-
1VR5WEW
12-QND3G8 8.1.1.3 Yes, see
Instructions for
FR 12-
1VR5WEW on
page 738.
In version 8.1, users have to
click the Query button twice to
enter query mode
12-
1WEE4BO
12-1VR5ZGB 8.1.1.3
Other
The GetCalendarData method is
missing a WHERE clause, so SQL
retrieves all of the activities in
the Activity HI Calendar applet
12-1QL06QH 12-1IHL5T5 8.1.1.3
Random hangs and crashes
occur when new sessions are
started
12-
1WLUYOC
12-1PVZS4R 8.1.1.3
Popups/Pick Lists/
MVG/Shuttle
Using pick applets causes
Internet Explorer 7 and Vista to
crash
12-1RXL8O6 12-1REVDKP 8.1.1.3
When selecting two entries in a
shuttle applet, nothing shows up
in the detail applet until the
record is saved
12-1SCRGLU 12-1P81NOT 8.1.1.3
If no value is supplied for a
required field, users receive an
error message, but even after
they have entered the required
information, the error message
continues to appear
12-1SGSZN3 12-1RSS41H 8.1.1.3
Removing a required entry in an
MVG query applet causes crash
12-1U5VCA3 12-1U4NF3F 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
576
performing validations within
eScript, if an error message
occurs and users click anywhere
but on the error message, the
browser crashes
12-1US5U9H 12-1SPYNHD 8.1.1.3
The Back button inside an error
message popup in SI mode is
disabled
12-1VUZHE0 12-1PT60C3 8.1.1.3
When SecureLogin=True and
SecureBrowser=False, if users
close the application by clicking
the X on the browser window, a
minimized browser remains on
the start bar at the bottom of the
screen
12-
1WAJZZW
12-1V0593H 8.1.1.3
Custom drilldowns do not work
in the Universal Inbox Item list
applet
12-
1WLUVWX
12-1W7XG07 8.1.1.3
With Internet Explorer 7 and
Internet Explorer 8, querying in
list applets on picklist fields
causes queries to fail
12-
1WRMXID
12-1WQ5PN9 8.1.1.3
CTRL+SHIFT+3 (Record Count)
hangs upon display
12-1WVI24O 12-1VR4BF7 8.1.1.3
When users click the Calculator
icon, they receive the following
error message: "Error: Object
doesn't support this property or
method."
12-1X13K22 12-1VR78HP 8.1.1.3
Keyboard accelerator does not
work in standard interactivity
mode
12-1VM6N6S 12-1VM6N67 8.1.1.3
Web Service
Other
The EAI UI Data Adapter service
search specifications <> and <
operators do not work and
generate an XML parsing error
12-1SSCIPY 12-1RAJ0I1 8.1.1.3
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
8.1.1.2 Fix Pack
If a call to WS
WC_Opportunity_BS fails,
subsequent calls to other ports
at the same session fail
12-1SX7TJO 12-1SJ54EF 8.1.1.3
The SoapOperation %1 does not
have either an input or output
SoapBody child.WSDL with input
header
12-1U5SP9R 12-1TYAWKZ 8.1.1.3
The Type field is not mapped
correctly in in the Product
Integration data map
12-1XS25LG 12-1XHF6N5 8.1.1.3
Rule Ids that are unique
identifiers for compatibilty
records are not mapped in the
SWI Promotion data map
12-1XS25UX 12-1V32N5L 8.1.1.3
The List Price field is not being
updated in the Siebel UI because
it is not mapped in the Product
data map
12-1XS25VI 12-1UGQO8Z 8.1.1.3
The IO SWI Promotion Internal
to External data map is incorrect
12-1XS25VT 12-1VM8W85 8.1.1.3
The Pricing Commit Type and
Dynamic Discount Method data
maps are not correct
12-1YM4QNJ 12-1XWWFPF 8.1.1.3
Table 24. Resolved Change Requests in the 8.1.1.2 Fix Pack
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Call Center
CTI
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
578
In Siebel 8.1.1, when users query
in a case-insensitive column, BI
Publisher report data does not
appear
12-1U5RK5A 12-1TK4CEL 8.1.1.2
The CCA Driver Transfer
command is disabled
12-1U5V6K0 12-1U0B3EH 8.1.1.2
The CTI toolbar hangs 12-1P90BO1 12-1OUTTE9 8.1.1.2
When the CTI Toolbar is enabled,
sending SWE commands to
Internet Explorer causes Internet
Explorer to hang
12-1RC0739 12-1QQ9XCT 8.1.1.2
When users update the Text Input
field by pasting in text with
CTRL+V but leave the mouse on
the Make Call button, the wrong
number is dialed
12-1TUEN5V 12-1ADDD6B 8.1.1.2
Other
Assignment Manager does not
assign incidents
12-1U0A7S1 12-1T12HUL 8.1.1.2
Assignment Manager sets the
Service Request Assigned Date
(ASGN_DT) incorrectly
12-1UXNSIN 12-1THO6BX 8.1.1.2
Drilling down on a Service
Request within search results
generates an error message
12-1RXY84H 12-1P56A4F 8.1.1.2
F9 Send Email with MS Outlook
Integration Siebel activity
created but instantly deleted
12-1TDOU48 12-1SUB033 8.1.1.2
indexing 1,000,000 employee
records
12-1UX5JI7 12-1UH87BR 8.1.1.2
Comm Media
Energy
Order Management
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Accepting product
recommendations adds the
wrong product to quotes or
orders.
12-1TK8BL1 12-1TB8YRV 8.1.1.2 Yes, see
Instructions for
FR 12-1TK8BL1
on page 756.
ACR 471: Users cannot disable
the Promotion Automatch feature
12-1TK3LQM 12-1THNL1J 8.1.1.2
Connectors/EAI
EAI Server
Components
Automatic relogin does not occur
for Stateless SessionType
12-1R3SFV9 12-1R1EH5L 8.1.1.2 Yes, see
Instructions for
FR 12-1R3SFV9
on page 756.
When a customer creates an
account hierachy by calling the
Upsert method on the EAI Siebel
Adapter and then passes the
account hierarchy to the EAI
Siebel Adapter again in order to
add a new child account to the
hierarchy, the following error
occurs: (oracon.cpp (3165))
SBL-DBC-00111: An error has
occurred writing to a record.
systems administrator to check
the problem persists.
12-1SN1XBS 12-1S7SIFT 8.1.1.2
EAI Object Manager returns a
"server busy" error message
12-1TD5M65 12-1T2IL37 8.1.1.2
Other
AnonUserPool requires a SWSE
Server restart to recover from a
Siebel EAI OM component
outage.
12-1TTL0L1 12-1TK6KJB 8.1.1.2
Empty XML elements are not
stripped from outbound
messages
12-1SW8EBY 12-1SW8EB7 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
580
Intermittent login issues occur
while connecting to EAI object
manager
12-1VP4GAQ 12-1QJJ9VL 8.1.1.2
Poor performance occurs when
XML Hierarchy Converter
processes escaped characters
12-1OOD0QL 12-1NZODFZ 8.1.1.2
The UTC Date Time Format for a
date field in the UI Data Web
Service does not match the
industry standard
12-1V0NBIX 12-1OUCG3F 8.1.1.2
VBC cache does not work for the
CSSFABCVRec specialized class
12-1TENTWD 12-1T6DMLW 8.1.1.2
Web Services sessions with
SessionType=None are not closed
in Siebel Server
12-1U09JKK 12-1TENCIJ 8.1.1.2
Consumer Sector
Handheld
Sync locks the application if there
has been a sync exception
because of an incomplete
transaction
12-1U0CC0E 12-1TYBGYE 8.1.1.2
Customer Order
Management
Configurator
<ListofLinkedItems> tag is not
working correctly in web services
12-1UI92KZ 12-1TXC3RL 8.1.1.2
GetCPInstance does not return
anything
12-1TWTOV8 12-1SFPEAN 8.1.1.2
If an attribute LOV domain is
updated, with values removed,
an error is encountered when
modifying the asset
12-1V3VLX3 12-1V0598R 8.1.1.2
On the AIX platform, the Ilog
engine crashes for more than 500
child products and a single
constraint
12-1TG6EAP 12-1SG6A0Z 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Remote Configurator Object
Manager hangs when customizing
complex products
12-1TK530Y 12-1S1FVNR 8.1.1.2
There is no way to join the
Attribute ID stored at Quote Item
XA.ATTR_ID to S_VOD
12-1U5UH3L 12-1T7DG8H 8.1.1.2 Yes, see
Instructions for
FR 12-1U5UH3L
on page 757.
When users modify a price, the
currency symbol is lost
12-1UIA0LH 12-1UI8TEV 8.1.1.2
When users navigate outside of
Configurator without clicking
Done/Cancel, the application
crashes
12-1VM568P 12-1U8XCTD 8.1.1.2
Within the Web client, when child
and grandchild attributes are
configured through a product
hierarchy using a constraint
popup applet, the attributes are
rendered incorrectly
12-1TK6P9Z 12-1T12HW9 8.1.1.2
Order Management
A crash occurs in ABO cycles
when AutoMatch is called
12-1VM5GQ5 12-1VM5K43 8.1.1.2
ACR 457: Provides cross-network
validation and cascade delete
enhancements for network
ordering for Siebel Customer
Order Management for SIA
12-1N22K2E 12-1MAMCSM 8.1.1.2 Yes, see
Instructions for
ACR 457 on
page 104.
Cursors are not closed as
expected when querying for
specialized Business Components
like Order Entry - Orders and
Order Entry - Line Items
12-1OOE5F3 12-1ONEBTJ 8.1.1.2
If an LOV value is removed from
the Attribute domain and the
component product containing
this attribute is unselected as
part of the ABO process, an error
occurs
12-1VH410I 12-1VH3J0H 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
582
The constraint definition UI for
customizable products does not
work correctly
12-1UIA3G7 12-1TGOA5B 8.1.1.2
Other
Promotions: The default
cardinality of a relationship in a
CP is ignored when it is 0. Any
relationship default cardinality in
a promotion greater than 0
works.
12-1U0DJZN 12-1TUVZQ9 8.1.1.2 Yes, see
Instructions for
FR 12-1U0DJZN
on page 757.
The application crashes when
upsell/cross sell messages are
still queued
12-1R6O99P 12-1QR99W7 8.1.1.2
Pricer
Manual price overrides are lost
when quantities are changed
using rules
12-1TYSJWU 12-1T2J5H3 8.1.1.2
Data Quality
Deduplication
Functional anomalies are found
within Data Quality Self-Service
Applications matching
12-1UIB3HP 12-1TK6K87 8.1.1.2
Other
The batch data cleansing
algorithm for UDQ is missing the
sdq_close_session call
12-1UHQ1IM 12-1R6NUCR 8.1.1.2
General
Accounts
Displaying a record in Print
Preview mode prints the record
three times
12-1TK47ZP 12-1TK4BU1 8.1.1.2
Application
Deployment Manager
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Adds the ability to sequence
database deployment units in a
package
12-1VJIAVE 12-1QR8NKV 8.1.1.2
Users are unable to specify
double path (samba;unix path)
as Destination Root, and this is
required while working with the
ADM framework where
Management Server and Siebel
Server are on different
environments
12-1UI7XPK 12-1TK6KG9 8.1.1.2
When ADM is used for attribute
adjustment import, the values of
the fields are populated
incorrectly
12-1U3KDHG 12-1SBRAKT 8.1.1.2
Audit Trail
After FRA users upgrade to 8.1.1,
the Audit Trail language remains
ENU
12-1TYSS6S 12-1TD6X31 8.1.1.2
Users are unable to track DELETE
operations using Audit Trail on
the Account Business Component
12-1SC3OC1 12-1R0X1G3 8.1.1.2
When trying to merge two
accounts, the Merge Record
process fails and yields an error
message
12-1US5UEV 12-1UI7QQX 8.1.1.2
Within the Audit Trail screen,
when users query for the Id field,
they receive the "Invalid
operation when not executed"
error message
12-1RBHPQ3 12-1PBVORR 8.1.1.2
Business Rules
Applet_ChangeFieldValue does
not trigger for fields that only
display in Show More mode for
Internet Explorer 7
12-1UI9URN 12-1MSUXR3 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
584
Exporting rule modules from the
Siebel user interfaces generates
a file that is not able to be
imported into another Siebel
instance
12-1U5RUZN 12-1QMX8LP 8.1.1.2
Calendar
If users make changes to a
calendar item on the HI Calendar
views and click the browser's
Back button, the changes are not
saved
12-1US5U74 12-1SFP9PD 8.1.1.2
On the LS Pharma HI Activity
Calendar View, when the user
switches from the contact list to
the activity list, the date is reset
to the current date rather than
the date previously selected by
the user
12-1UK0V2R 12-1UGQKAX 8.1.1.2
The Siebel 8.1.1 SIA FRA popup
version of the calendar displays
Saturday (Samedi) incorrectly
12-1U0DVDN 12-1U0BYHX 8.1.1.2
When users create or edit a
calendar item and then close the
brower with the "X" close button,
the record is not saved and an
12-1US5UC0 12-1T6T4CF 8.1.1.2
When users drag a contact record
to the calendar, the first contact
in the list is associated to the
calendar record and not the
contact record that the user was
dragging
12-1UIA8WC 12-1UGQK67 8.1.1.2
Correspondence
During proposal generation,
when multiple proposals are
generated during a single user
session, cursors are exceeded
12-1Q2558J 12-1PLH0GL 8.1.1.2
Installation
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
On the Linux platform, URLs do
not come up after 8.1.1.1 SIA has
been applied on 8.1.1 SIA
12-1WF6D7D 12-1WF6D6N 8.1.1.2
Siebel Tools Online Help files
were not updated for Siebel 8.1.1
12-1SW89YF 12-1Q35A8A 8.1.1.2
Other
When users generate a large
number of proposal drafts, they
receive the "Maximum open
cursors" error message
12-1TXT8PN 12-1T12H8N 8.1.1.2
Provides support for CRM
Desktop for Outlook (ACR 464).
12-
1UWOAQL
12-1UWOAPI 8.1.1.2 Yes, see
Instructions for
ACR 464 on
page 147.
Calling a business service method
written in Siebel Visual Basic
causes the error: SBL-DAT-00323
after the first invocation.
12-1V9U8A5 12-1UX6FHT 8.1.1.2
Deleting a position for an
employee using Java Data bean
causes a runtime error
12-1U0CC80 12-1SNJLOF 8.1.1.2
Repository objects are incorrectly
named
12-
1UWOARN
12-1TTI51Q 8.1.1.2
It is not possible to sync a contact
whose email address contains
more than fifty characters
12-1VLGHMD 12-1UT7XJH 8.1.1.2
Large temporary files created
during EAI processing are not
always deleted
12-1VM6K61 12-1OUD1RP 8.1.1.2
MakeFile.dep does not get
created when the flag
NoDepent=t is removed from the
makefile.dcl file
12-1UJQLUG 12-1UIAVXD 8.1.1.2
Opening a pick applet fires the
WriteRecord method on the
underlying business component
12-1TK89IV 12-1T9B2VI 8.1.1.2
Querying for records in the
Inbound Calls applet causes a
memory leak
12-1TK9WIQ 12-1TDX57D 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
586
RaiseErrorText in the JPN
language appends a character to
the message box
12-1VABKXZ 12-1TUED13 8.1.1.2
Users are not able to apply
different view modes to parent or
child integration components of
an integration object
12-1TK92JL 12-1T135UF 8.1.1.2
Users cannot deassociate
multiple association records in an
MVG at the same time
12-
1VCQUHG
12-1V6FUML 8.1.1.2
When users query within the top
applet of the Contact Detail View
(within Contacts Screen
>Activities), the application
crashes
12-1UI92G1 12-1U5TMPJ 8.1.1.2
Runtime errors occur because of
the ST eScript engine
12-1SSUR6E 12-1SM2KAX 8.1.1.2
Performance
Double parsing without bind peek
in Oracle Connector causes
performance degradation
12-1ORCIOH 12-1OQD0BB 8.1.1.2
Personalization
If an association applet is
assigned a rule set for
personalization that uses an
include expression to act as a
search specification, the include
expression is ignored
12-1TK8BFY 12-1THO6OP 8.1.1.2
PIM Server Integration
PIMSI Dispatcher does not filter
by user group
12-1MQCB8J 12-1MIVDVK 8.1.1.2
Add-in does not respect the
"PIMSI Category" setting
12-1U5RVL3 12-1U5RIY5 8.1.1.2
After users apply the Outlook
Add-in Quick Fix to support SSO,
their passwords are overwritten
12-1TQNB3M 12-1TK9Z8J 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Attendees are not properly
synched when there is a
combination of sync-enabled and
non-sync invitees
12-1UI7XSW 12-1UGR5SJ 8.1.1.2
Outlook Add-in fails on non-
Windows servers
12-1TK4K9Y 12-1TBJVXL 8.1.1.2
Outlook Add-in illustrates
incorrect behavior with SSO
enabled
12-1R84XM5 12-1QXJF7Z 8.1.1.2
Outlook Add-in Toolbar
disappears
12-1UI8TXL 12-1U0B955 8.1.1.2
The SSSE engine crashes when
QF8501 is installed on top of
QF0581
12-1UAFDX6 12-1T6T4DJ 8.1.1.2
The SSSE Outlook Add-in sorts
incorrectly when searching in the
Link dialog box
12-1VI15ZT 12-1UH87KX 8.1.1.2
Valid Category value overwritten
by default
12-1TH5KDI 12-1RW60U6 8.1.1.2
Remote
ACR 544: Enhances the Siebel
Remote utility and allows it to be
intergrated with the Siebel HA
Upgrade solution
12-1UZ5TVC 12-1SW8HHD 8.1.1.2
After a failed database
initialization, users can cancel,
and then log in again and add
data, but the synchronization to
the server fails, and the data is
lost
12-1UJQTMH 12-1U5RF2V 8.1.1.2
Lock on S_DOCK_SESSION with
MS SQL Server 2005
12-1RV74GM 12-1QXJVFB 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
588
On the Tablet PC device, when
Quick Start is enabled, when
users connect to the local
database, the application
launches, but the sync reminder
is launched in the background
and users have to use Alt + Tab to
bring the reminder to the
forefront
12-
1PCUMWS
12-1NALW8B 8.1.1.2
Quick Start does not work with an
non-admin user on Microsoft
Windows XP and Microsoft Vista
12-1THNI2Z 12-1QKIPCK 8.1.1.2
SynchMgr does not close file
handles for dropped sessions, so
when a user whose session has
been dropped attempts a new
session, another file handle is
used
12-1U5SIB2 12-1U08IXL 8.1.1.2
The apply_thrd function fails with
the Index 'S_EVT_ACT_X_U1' for
table 'S_EVT_ACT_X' would not
be unique" error
12-1T7DDJT 12-1SZLZ9R 8.1.1.2
The Help button on the
Synchronization window does not
work
12-1TK3QXJ 12-1JAR0YF 8.1.1.2
The Siebel application crashes
when it is opened twice using
Quick Start
12-1V3JRDF 12-1U4I7Q5 8.1.1.2
Transaction Merger fails because
single byte ROW_ID is duplicated
12-1PKZD0S 12-1NWLI7J 8.1.1.2
Under heavy routing conditions
(such as with EIM) and large
remote environments (over 400
users), after some time of
working normally, multiple
Txnrouter tasks fail with errors
12-1SING9C 12-1RPD2ML 8.1.1.2
Within the txnmerge log file,
pTableName is NULL or empty
12-1UK0UHZ 12-1TUWRGV 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
After users create a report and
associate it to a view, the report
does not show up in the BIP
Reports drop-down menu
12-1WLUFQ1 12-1WLUFOF 8.1.1.2
Search
ACR 439: Search Center does not
remember terms and results after
it has been closed
12-1P1OP6D 12-1NZODJL 8.1.1.2
ACR 439: When users search, the
Field Name is used rather than
the Field Display name
12-1P1OPJ6 12-1OQU6GN 8.1.1.2
After indexing certain business
components for mobile search,
the datasource is shown as
"buscomp".
12-1UIAGQE 12-1RKLPVN 8.1.1.2
Binocular Search does not work
with special characters
12-1U09BK1 12-1NZO98B 8.1.1.2
Binocular search yields the
previous search's data when
users do not enter the search
criteria a second time
12-1U0CXZG 12-1S7PQXV 8.1.1.2
Drilling down on a Service
Request within search results
12-1RXY84H 12-1P56A4F 8.1.1.2
For Search, the Context
Sensitivity preference does not
work when invoked from the
Opportunity, Solutions, or
Literature screens
12-1SXP5U8 12-1S8Q8CN 8.1.1.2
Incremental indexing with OSES
does not work for SR, Contact, or
Account
12-1U0D4B3 12-1T6T4GB 8.1.1.2 Yes, see
Instructions for
FR 12-1U0D4B3
on page 758.
OSES- Search: Simultaneous
incremental indexing results in
leaving some newly created
records
12-
1RXL8MW
12-1HTFNR3 8.1.1.2
OSES: Records Visibility in OSES
for an eService user
12-1SC8YE5 12-1QV5WFV 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
590
OSES: Schedule ID parameter in
Engine Settings
12-1TAA6HJ 12-1SJ5C83 8.1.1.2
Search: When users try to index
a category for a Business
Component that has a begin
parenthesis in the name, they
message: SBL-DAT-00222: An
error has occurred creating
business component '<?>' used
by business object '<?>'.
12-1RYK4D8 12-1QR8N6F 8.1.1.2
The "Look In" drop-down list still
contains values even after those
values have been removed from
the user's responsibilities
12-
1NZQW39
12-1NVVH4J 8.1.1.2
When a Search Category is
indexed, the old indexes are not
removed
12-1QH55SS 12-1OVCU5D 8.1.1.2
When advanced search is
performed, search results from
multiple search categories based
on the same BC are displayed
even if only one category was
selected.
12-1V7WJSN 12-1V7F8AT 8.1.1.2
When Search Center is opened
from within CTI, users cannot use
Enter for submitting FIND criteria
12-1S7SIQX 12-1S0YDZ5 8.1.1.2
When users enter special
characters, the FIND feature does
not fetch results with the correct
criteria
12-1TK6OSU 12-1RV73Z9 8.1.1.2
ACR 452: When users run a blank
search or enter search criteria in
the "Search For" dialog box and
click Go, in the Search Results
window, the datasource displays
"buscomp" instead of the Search
Category name
12-1U5V2FD 12-1U5V2EN 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
After users have set Context-
Sensitive as a preference, when
they navigate to the Contacts
screen > All Contact view and
click on the Binocular icon, the
Search Center opens with "All"
specified in the Lookin instead of
opening with "Contacts" specified
12-1TDNZTL 12-1QXJYZI 8.1.1.2
Drilling down on keywords does
not refine the results
12-1VGM8F2 12-1VD87WA 8.1.1.2
Queries show + instead of AND
when users drill down on
keywords
12-1VGM8I5 12-1VGM8AG 8.1.1.2
Users are unable to set the
default flag for search definitions
12-1UJQSQT 12-1UJQSQ1 8.1.1.2
Security
SWEU parameter should ignore
hostnames to prevent phishing
12-1N22J3V 12-1IYN1VD 8.1.1.2
User can change their privileges
to that of another user (such as
an administrator) by entering a
Javascript command
12-1UGR0BD 12-1U0CPDF 8.1.1.2
Addresses a problem with ACR
405 where Dynamic MQ Reply
Queue does not work
12-1QK1GVJ 12-1PLGZW1 8.1.1.2
Cannot add MLOV entry with
same display value, even when
LIC code is different
12-1V417JN 12-1R0X6NL 8.1.1.2 Yes, see
Instructions for
FR 12-1V417JN
on page 758.
The Siebel application
experiences non-reproducible
random crashes
12-1NTIUTF 12-1N3J0WN 8.1.1.2
When users attempt to print, the
application fails and displays an
error message
12-1N22LHT 12-1K51E4X 8.1.1.2
SmartScripts
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
592
Smartscripts are causing Internet
Explorer to crash after installing
the 8.1.1.1 patch
12-1V0N8EM 12-1UQ62AL 8.1.1.2
System Operation &
Diagnostics
The Siebel 8.1.1 Gateway Server
crashes on Microsoft Cluster 2008
12-1U5VCBL 12-1U5R7UV 8.1.1.2
Task UI
Invoking the binocular search
icon from the Siebel application
toolbar while stepping through a
TBUI Task may cause the local
server to hang and the Siebel
application to crash
12-1V7F9GQ 12-1V3JQI3 8.1.1.2
TBUI task statuses do not reflect
the correct values
12-1TK7ABX 12-1TGO4RF 8.1.1.2
The license key is missing for the
Task Pane view in Siebel
Professional Edition (SPE) is not
available
12-1TYSIXQ 12-1TK6LZT 8.1.1.2
Tools/Configuration
An error occurs with the global
variable of type property set
initialization in the global section
of Business Services
12-1N1RBJY 12-1M81JE0 8.1.1.2
NoRefreshOnDynamicTogg in
8.0.0.6 corrupts applets in Query
mode
12-1TUEN4I 12-1TA9WD7 8.1.1.2
Siebel Tools sessions end without
a warning or error message when
processing WSDL
12-1U5SZNL 12-1TK9JCV 8.1.1.2
Upgrade
The Symbolic String Conversion
utility (consoleapp.exe) fails in
Siebel 8.1.1
12-1STTIXO 12-1SI5H61 8.1.1.2
Web Framework
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Exporting from browsers that are
running Windows 2000 SP1 or
Windows XP SP2 causes session
timeouts from Siebel 7.7.2.6
onwards
12-1QTPRGH 12-1J1X6NA 8.1.1.2
Workflow
Business services that do not
initialize and return Output
Arguments to workflow steps tat
are expecting them cause a
runtime error
12-1SSCMJ3 12-1SBRA31 8.1.1.2
Workflow processes edited in
Siebel Tools fail to validate in
8.1.1.1
12-1VM6SF3 12-1VK09JB 8.1.1.2
iHelp
Other
Related iHelp does not navigate
correctly
12-1SX7TI5 12-1SJ5MIZ 8.1.1.2
The title "Additional iHelp Topics"
in the iHelp pane is not in the
local language
12-1U0DSQ7 12-1TK4UOX 8.1.1.2
Life Sciences
Activity
A memory and cursor leak error
message occurs when Smart Call
functionality is used
12-1UUNN76 12-1UGQKF3 8.1.1.2
Users are unable to submit calls
created on the current day from
Handheld
12-1VKHIB7 12-1V6FY27 8.1.1.2
Clinical Manager
Position Rollup does not always
function properly
12-1VAT6K9 12-1OK0UBP 8.1.1.2
Trip report status does not
automatically change to In
Progress
12-1UX5E8Z 12-1PCUB4Z 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
594
Undo record in Clinical Trial
Report Detail View
12-1UG9MN3 12-1U5RQB1 8.1.1.2
Users cannot undo records after
selecting a template in the Trip
Report Details view
12-1UU4KQ7 12-1P2RV9L 8.1.1.2
Users are unable to copy Site
Vists records
12-1V3K6BX 12-1K824E1 8.1.1.2 Yes, see
Instructions for
FR 12-1V3K6BX
on page 759.
Trip Reports
Users are unable to change the
Trip Report Status field in the
Clinical Trip Report view
12-1UVNYZX 12-1NVVH35 8.1.1.2 Yes, see
Instructions for
FR 12-1UVNYZX
on page 759.
Marketing
Campaigns
Prospect import does not check
for matches against existing
contacts
12-1TK666M 12-1TK665T 8.1.1.2
Prospect promotion on Leads
screen gives error when matches
are ignored
12-1UI92JW 12-1U4I7KV 8.1.1.2
Response import does not use all
selected Exact Match fields to
check for matches
12-
1UXNWE8
12-1UIB7Z9 8.1.1.2
When uers create a treatment
template, create an offer, add a
new treatment that users the
treatment template that they
created, add URLs, and navigate
to the Edit Email tab, they receive
the Transform Error C00CE505 (-
1072896763) error message
12-1TK96TH 12-1T7V4R7 8.1.1.2
While running the 'Response to
Lead' conversion, users receive a
maximum cursors error message
12-1UI8DMO 12-1UHPV6B 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Within the Campaign Segment
Allocation view, users are unable
to see lists created by other users
12-1TK9WGJ 12-1TBLYYA 8.1.1.2
Email and Web
Marketing
After Siebel 8.1.1 QF0034 has
been applied, when users edit
text email templates, the
changes they make disappear
12-1UIB3EZ 12-1UI81Z5 8.1.1.2
Error messages appear when
users add URLs to an email HTML
body
12-1U0D8SV 12-1U0BPQZ 8.1.1.2
Events
> Events (create one or open
one) > Resources > Staff, add
two records, delete one of the
records, save the remaining
record, an error message
displays and the deleted record
comes back
12-1S2F1F1 12-1RRBFQ9 8.1.1.2
Marketing Server
Integration to Marketing
Outbound Web Services does not
support enterprise SSO
12-1TK47RK 12-1KJP2WG 8.1.1.2
Other
When users create a Landing
Site, add a footer within the Site
Details tab, navigate to the
Preview and Deploy tab, and click
Preview, the footer does not
display
12-1TPUQJB 12-1TH5NV5 8.1.1.2
Mobile Solutions
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
596
During Handheld
synchronization, the logging of
URLs exposes username/
password combinations in web
server logs
12-1TXTR5T 12-1THO6UJ 8.1.1.2
For Handheld batch sync, the Exit
and Next buttons that were
available with Siebel version
7.5.x are not available in later
releases
12-1VGMVZT 12-1U0CP6R 8.1.1.2
In Handheld daily calendar, the
calendar popup window for the
Date field corrupts the display
when resolution = VGA
12-1VHL8BW 12-1UOF62N 8.1.1.2
PDA DSS Batchsync loses data if
you select Download without
uploading first
12-1UZO7F7 12-1UH87ET 8.1.1.2
The application hangs when the
barcode for the second item
listed in a picklist is scanned
12-1UG9MQI 12-1ROXJHT 8.1.1.2
When users attempt to run
Companion Sync, they receive
the following error message:
"Error detected while
communicating with the device
"12-
1SWPT87
12-1RSS5V1 8.1.1.2
When users attempt to
synchronize a PDA device with a
machine running Vista, the
synchronization fails
12-1S9RUXX 12-1RVORD3 8.1.1.2
With WM5 and WM6 devices,
when certain characters are
extracted into dbfile.txt, the
dbimport synchronization step
fails
12-1SIO0R1 12-1SC9C45 8.1.1.2
Within the Handheld dbimport
logging file, information about
non-database-related steps such
as file creation or file deletion is
missing
12-1QL04RJ 12-1QFPJ7Z 8.1.1.2
Other
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
The DB_LAST_UPD and
DB_LAST_UPD_SRC columns are
listed twice in the update
statement
12-1S1Y0MZ 12-1L0YDDK 8.1.1.2
Store-and-Forward
Messaging
enhancements:
Provides a utility for
administrators to act on
failing Store and Forward
transactions.
Enhances logging
capabilities. (Server)
12-1U087M8 12-1O2HQ4R 8.1.1.2
SMQReceiver component look at
all server requests and not just
those for which it is responsible.
12-1TKABND 12-1SI5H9N 8.1.1.2
The "SMQ Process User Queue"
workflow can create duplicate
records in case of MQe problems
12-1RRTKGX 12-1QR98KH 8.1.1.2
Users are unable to remove
reassigned messages
12-1TGOAM3 12-1SFP9NP 8.1.1.2
Sales
Other
Manually-created revenue items
within accounts are not updated
when the account is changed by a
user who has not created the
revenue item
12-1U0A7J0 12-1SW88FV 8.1.1.2
Service
Logistic Manager
Error invoking service 'Inventory
Transaction', method
'SetTxnDetailsFromTxnSet
12-1V7FE6F 12-1UH87R1 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
598
Siebel Email
Response
General
For draft emails, the status can
be changed to any value and
contacts can be removed or
added
12-1U5TWJC 12-1U5TWIL 8.1.1.2
Siebel Automated Quote Approval
Emails are not being sent
12-1T2SVQ5 12-1SSTZQV 8.1.1.2 Yes, see
Instructions for
FR 12-1T2SVQ5
on page 759.
When users are sending an
outbound email, resolution
documents cannot be seen in the
Attachment field
12-1TK99NV 12-1TK99KZ 8.1.1.2
When users send an outbound
email to duplicate email
accounts, duplicate emails are
received in the mail client
12-1TYT3N8 12-1TZR995 8.1.1.2
With templates, the subject line
and body text are not replaced
according to the template
selected
12-1QK0UEL 12-1FCL4BH 8.1.1.2 Yes, see
Instructions for
FR 12-1QK0UEL
on page 759.
Siebel Self-Service
Common
Miscellaneous
The following error message
occurs when trying to invoke Web
services: "Error Code: 10944642
Error Message: Error: Inbound
SOAP Message - Session Token is
missing or invalid or has expired
12-1TK4BEP 12-1R7V0XR 8.1.1.2 Yes, see
Instructions for
FR 12-1TK4BEP
on page 760.
Travel &
Transportation
Events Execution
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
ACR 494: Provides Event Check
enhancements and BEO Report
functionality for the Siebel Travel
& Transportation application
12-1S9QL59 12-1S9QL3Z 8.1.1.2 Yes, see
Instructions for
ACR 494 on
page 310.
Other
For ACR 450 and ACR 488, the
sia_options.txt file is missing
several views for licensing
12-1UI8ZAR 12-1UI8Z9H 8.1.1.2
Provides more technical content
for the Travel and Transportation
application error messages
12-1T6VXUH 12-1T6VXSP 8.1.1.2
Selecting the output type as ALL
for Report Name in
Administration > BIP Report
does not work as expected
12-1WIXYWB 12-1WIXYVR 8.1.1.2
When users click on the
Functional Space Diary, they
12-1V41X13 12-1V41X0M 8.1.1.2
User Interface
Administration
Successful login does not reset
IsStandaloneWebClient Profile
Attribute
12-1UQU5DX 12-1U5V2WZ 8.1.1.2
Controls
After 8.1.1 QF0025 has been
applied, the implicit save function
does not work on form applets
12-1UW60LO 12-1UI8T7X 8.1.1.2
Browser script causes error
messages on picklist auto-
selection
12-1V421BE 12-1QPSY8J 8.1.1.2
IE crash when triggering
Smartscript from client-side
script
12-1UGR21U 12-1U0866H 8.1.1.2
Provides the ability to
programmatically suppress error
messages
12-1UGQZS5 12-IVNITD 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
600
Translated error messages have
extra Japanese characters in
them
12-1VHLBL9 12-1NSKL0N 8.1.1.2
The UI shows only 32K of data
onscreen from the CLOB field
12-1UFAJ40 12-1RHR0N1 8.1.1.2
Users should be able to query on
fields in a view even if the Read
Only View flag is set to TRUE
12-1O7OFOV 12-OM5V6D 8.1.1.2
With Internet Explorer 7, Siebel
Calendar crashes, hangs, does
not load, or fails with a script
error
12-1QKI678 12-1PE98Y5 8.1.1.2
Siebel Calendar control does not
work
12-
1QNW677
12-1PE98W7 8.1.1.2
When using run-time events and
personalization rules to drive
toggle applet selection, the first
time that the toggle applet
displays, the display is
incomplete
12-1QQACIH 12-1NVVH71 8.1.1.2
Navigation
If users enter a query of more
than two characters, when they
press the TAB key, the focus does
not move to the GO button
12-1SC96YJ 12-1OA585D 8.1.1.2
When users perform a new query
in a child form applet, the
application does not switch from
edit to query mode
12-1U0A7PV 12-1TGO4VB 8.1.1.2
When the Immediate Post
Change property has been set, a
second click is required to
navigate
12-1VM6K6Y 12-1O6OCKJ 8.1.1.2
With Internet Explorer 7,
navigating to the next applet
without completing the required
fields causes an endless loop
12-1SC96ZD 12-1ME9N7W 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Other
Exporting results from queries
that use calculated fields omits
valid records
12-1V3VLLZ 12-1UU5KSH 8.1.1.2
Launching a TBUI Task while it is
running and then opening Search
Center (using the binoculars
icon) may cause the application
to hang and an error message to
appear
12-1RZ1P11 12-1RQUGN3 8.1.1.2
Quickprint of a toggle applet
prints the record twice
12-1SCQKBZ 12-1L3YVPO 8.1.1.2
Refining a query on account team
12-1TG65R2 12-1TG65Q3 8.1.1.2
The 'Select Field' string for Query
Assistant is not translated
12-1U0BDIC 12-1U0A9KV 8.1.1.2
When Query Assistant is used for
LOV entries, the "The value
entered in Field does not match
any value in the bounded picklist
12-
1VKHWBE
12-1UI8QNP 8.1.1.2
Popups/Pick Lists/
MVG/Shuttle
Internet Explorer 7 crashes when
users open a popup window on
top of an MVG
12-1UI7VQC 12-1UGQKML 8.1.1.2
Minimizing and then restoring a
window when changes have not
been saved causes Internet
Explorer to crash
12-1TYSS1V 12-1QBCC2R 8.1.1.2
When a toggle applet is
configured, running a query by
hitting the Enter key causes the
12-
1VM6K4W
12-1S8Q8EL 8.1.1.2
users close a popup window using
the X, the application hangs
12-1S9RBEG 12-1S1FXNF 8.1.1.2
Web Service
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
602
8.1.1.1 Fix Pack
Other
Provides Web service access
through the Mobile Web Client to
other local desktop applications
(ACR 492)
12-
1STBMWW
12-1STBMTB 8.1.1.2
The "all" XSD element is treated
as sequence
12-1TK86GJ 12-1STC0UB 8.1.1.2
The EAI UI Data Adapter does not
work for paging child integration
components
12-1TK5S8P 12-1TK4C5P 8.1.1.2
The Impersonate feature does
not consider time zones
12-1U09CUR 12-1TYAWK5 8.1.1.2
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Call Center
CTI
The Chat transfer command
defined in multichannelC.def is
incorrect
12-1S99AEF 12-1S99ADV 8.1.1.1
Accessiblity: CTI does not take
any input from the toolbar
editbox after the application has
been converted for Section 508
compliance
12-1RV6IUZ 12-1ME9KRG 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Changes
Accessibility: After CTI has been
configured for Section 508
compliance, the screen reader
reads every underlying
command for CTI controls from
the CTI toolbar
12-1RV6IUP 12-1MEBPT5 8.1.1.1
Within CCA, when an invalid
Visited KB item number is
submitted, the chat is
submitted, the agent answers
and clicks Open KB Visted list,
and chooses the invalid KB item
number, no error message
displays
12-1R8MHX2 12-1PJ2S1Z 8.1.1.1
When two driver profiles have
been configured, including all
the commands and events in
both drivers, and Envox is used
for Voice and Virtual CTI driver is
used for Chat, when users make
an inbound voice call to Envox
and then an inbound chat to
virutal CTI driver separately,
accept both inbound calls, check
the toolbar status, and release
one of the active calls, the
Release button becomes
disabled
12-1R6NUYJ 12-1R58N93 8.1.1.1
Provides Hoteling-Hotdesking
support for Call Center
Anywhere
12-1QXO3LS 12-1QK0QNF 8.1.1.1
When there are multiple CCA
driver instances running, users
receive the "Could not find the
matched SVC for session..."
error message
12-
1QTPMTW
12-1QDA9FX 8.1.1.1
CCA: If the "MaxAgentNumber"
parameter does not exist, a new
login creates a new driver
instance
12-1QTPMTH 12-1QBCUYH 8.1.1.1
Updates CRM Chat to use the
latest Java file content
12-1QR9BRG 12-1Q2MZRN 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
604
When users create two
simultaneous outbound
requests, the requests hang and
CommOutboundMgr logs show
errors SBL-CMO-00169 and SBL-
SRM-053021
12-1NQ7VT4 12-1NKJF4T 8.1.1.1
Other
Redesigns the Email Response UI
so that replying to an incoming
email and forwarding a sent
email display in the same format
12-1RB07UI 12-1RB07T9 8.1.1.1 Yes, see
Instructions for
FR 12-1RB07UI
on page 772.
With the Find feature, when
values have special characters,
records are not returned in the
Destination Results view
12-1RA1T6W 12-1QNWAIL 8.1.1.1
The CCA Driver does not retrieve
all of the records in the CCA
library
12-1QQ9XSR 12-1QUOFMN 8.1.1.1
After 8.0 [20405] QF1009 has
been applied, spell check does
not work on Linux servers
12-1QR8PCO 12-1LSX5J6 8.1.1.1
Users receive the SBL-DAT-
00457 error message when
searching on a Multi Value Field
that is mapped to another Multi
Value Field
12-1QL05SF 12-1Q9I2QJ 8.1.1.1
Comm Media
Energy
Order Management
ACR 471: If headless
configuration is used to adjust
the CP definition automatically
based on CP definition, if
PRESERVE_ENGINE_AND_USER
_PICKS have been set to Y, and
if linked items have been used in
in the configurator model, during
Upgrade promotion, the CP
structure is not adjusted
12-1SZ4WPA 12-1SXN45J 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Within the Sales Order screen,
when users select the order
number, navigate to the order,
select line items, select an item,
click Customize, select an item,
and then navigate out of the
field, they receive an error
message that the item was not
found, and when they navigate
to the Accounts screen, the
Object Manager crashes
12-1S1Y0R1 12-1R75AA5 8.1.1.1
Other
Users are unable to add a
promotion to the Shopping Cart
with default options selected
12-1O05GRF 12-1M6UUMK 8.1.1.1
Connectors / EAI
Other
All messages sent to JMS go as
BytesMessage, regardless of
whether the data is String/
Binary
12-1SBSPDP 12-1RAJ07R 8.1.1.1
installed, ReplyToQ and
ReplyToQMgr are cached by the
MQ Listener component after
replying to the first message in
the queue rather than
dynamically applying for each
message
12-1RGSQ98 12-1R0X6P9 8.1.1.1
Object Manager tasks are not
reused when a Siebel exception
occurs using JCA/Siebel
Resource Adapter
12-1QUOILO 12-1OI2RO5 8.1.1.1
When setting
HDR.connection=close on some
W eb servers, response is
delayed
12-1Q3NJU1 12-1JZ28HA 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
606
The EAI Data Transformation
Engine outputs the target
instance when the source search
specification is not met
12-1N1QM7X 12-1MNQ3BZ 8.1.1.1
Consumer Sector
Deductions
ACR 480: Claim Resolution time
value changes after the record is
refreshed
12-1SPXYJS 12-1SPXYHT 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
Other
When users create a new plan,
the application crashes
12-1TXTRDT 12-1TXTR4J 8.1.1.1
ACR 480: Delist dates are not
updated in the ADL applet
12-1TSQ0BX 12-1TSQ0AH 8.1.1.1 Yes, see
Instructions for
FR 12-1TSQ0BX
on page 773.
Improves the quality of the
Consumer Sector application
error messages
12-1TGNFMK 12-1TGNFL1 8.1.1.1
ACR 480: Provides translations
for error messages related to
ACR 480
12-1TG5FLS 12-1TG5FKD 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: The Seed.inp file is
missing for seed data import on
JPN
12-1TAR916 12-1T9S0ZN 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
Improves the quality of
Consumer Sector application
error messages
12-1T6VXL6 12-1T6VXJQ 8.1.1.1
ACR 480: Flags (A/O/P) should
retain their values if the Account
Distribution record exists (ADL)
12-1SOZJYK 12-1SOZJUX 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
import seed_locale_JPN.dat for
LOV seed data
12-1SN1W5R 12-1SN1W4H 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Consumer Sector error message
content is not useful
12-1SJ5WTI 12-1SJ5WS3 8.1.1.1
Improves the quality of
Consumer Sector error
messages
12-1SF7RMM 12-1SF7RL9 8.1.1.1
ACR 480: Users are able to save
Delist date > Product end date
in Authorized Category Product
(ADL), but they should receive
an error message and be
preventing from doing this
12-1S87KF6 12-1S87KDR 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: List Date and Delist
date are not updated in the
Authorized Categories Product
middle applet (ADL)
12-1S87KBC 12-1S87K9X 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: The List and Delist
dates are not populated in the
ADL applet
12-1RYK5JX 12-1RYK5II 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR480: The Auditable,
Orderable, and Promotable flags
are always checked as True in
the ADL applet
12-1RYK5I2 12-1RYK5GS 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 358: Provides support for
the new out-of-the-box
integration between Siebel and
EBS OTM. Integration points
include account, products,
pricing, funding (accruals),
shipments, promotions,
deductions, and payments.
12-1RV6IE1 12-1JGEFDN 8.1.1.1 Yes, see
Instructions for
ACR 358 on
page 45.
ACR 480: Within Administration
- Authorized Distribution List
(ADL), when users click on the
2LNV detail list to navigate to
the Target Account applet, the
accounts on which ADL have
been applied should display, but
blank records display instead
12-1RSAYUA 12-1RSAYSV 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
608
ACR 480: When users navigate
to Site Map > Adminstration -
Authorized Distribution List, click
on the 2LNV detail list, navigate
to the Account Product applet,
click New, select a product, and
then click the Delete Selected
button, they receive an "end of
file occurred error message
12-1RSAYQS 12-1RSAYPD 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
Retail Objectives
to Site Map > Account >
Merchandising Location, create a
location, navigate to the Product
applet (bottom applet), click the
Select category button, click the
Query button on the Add Product
dialog box, and then click the
Catalog picklist, the Catalog
picklist shows Categories and
not Catalogs
12-1SN1X8G 12-1SMKW6N 8.1.1.1
ACR 480: Within Accounts, when
users select a account that has
distribution added, navigate to
Merchandising Location > Create
a Location, add a product in the
Product bottom applet, navigate
to the Account Distribution
applet and delete that they
added earlier, when users
navigate back to Merchandising
Location > Product bottom
applet, the deleted product still
displays
12-1RUPL7F 12-1RUPL60 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
Sales Volume Planning
ACR 480: For leaf-level
accounts, Aggregated Quantity
should not equal Promotion
Incremental Quantity
12-1SEPR7S 12-1SEPR65 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
ACR 480: Within the SVP >
Baseline - Flat view, the All Years
button is missing
12-1S2WET4 12-1S1GHXS 8.1.1.1
The cursors are left open during
the Aggregation and Allocation
processes
12-1RSB0UE 12-1ONVDYP 8.1.1.1
Trade Promotions
ACR 480: Provides a system
reference called "Trade
Promotion Extended" to allow
customers to implement the new
functionality in ACR 480 by
setting the value to TRUE or
keep the Trade Promotions
functionality that existed prior to
ACR 480 by setting the value to
FALSE
12-1TXBBQB 12-1TXBBP1 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: Provides the following
EIM import files: eim45.sql and
eim_export_bu_look_up_name.
sql
12-1SG67VF 12-1SEPND9 8.1.1.1
ACR 480: Includes translated
error message files
12-1SD8PE4 12-1SD8PCN 8.1.1.1
ACR 480: Some fields are not
copied from the Corporate
Promotion header to the Account
Promotion header
12-1SCRGQE 12-1SCRGO9 8.1.1.1
ACR 480: Within Corporate
Promotions, the Target Child
Account applet is not refreshed
properly
12-1SCRGO0 12-1SCRGNB 8.1.1.1
ACR 480: When users click the
Products button within Corporate
Promotions, they receive an
error message
12-1SC7RS9 12-1SC7RRJ 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
610
new Account Promotion,
associate categories and add,
products, enter spend variables
at the Promotion Product level,
and verify that the Promoted
Price and Est. Baseline Revenue
fields are calculated, the Est.
Baseline Rev value is not rolled
up to the Promoted Category and
Promotion level
12-1SB91B5 12-1SB919Q 8.1.1.1
ACR480: Category Pick applet is
not refreshed in CPG Plan
Account Promotion List Applet
12-1S9R960 12-1S9R95B 8.1.1.1
ACR480: Within Account
Promotions > Pick Plan applet,
the Go button is unavailable
12-1S9R952 12-1S9R94D 8.1.1.1
ACR 480: Clicking the Products
button on CG Promotion Form
Applet Non-Corporate retrieves
inactive products
12-1S9AHQ9 12-1S8I5DB 8.1.1.1
ACR 480: Within the Corporate
Promotion screen, when users
create a new promotion, drill
down on the Corporate
Promotion Name field, and
associate a Promoted Category,
when they click the New button,
a pick applet appears and the
user can pick the desired
category, but when users select
Ctrl + N or Menu > New Record,
a new record is created without
Category = NULL. The two
options should behave
identically.
12-1S87Q2L 12-1S87Q0F 8.1.1.1
ACR 480: Includes the translated
error message files
12-1S8I5CG 12-1S8I5B5 8.1.1.1
ACR 480: Spend Values are not
being rolled up
12-1S7SICW 12-1S7SIBE 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
ACR 480: An error message
appears when users create a
promotion
12-1S6A181 12-1S6A16Q 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: The Team field is blank
for a new plan
12-1S6A16E 12-1S6A14X 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: In the Promotion
screen, clicking the Shipment
button yields an error message
12-1S35CMR 12-1S35CLB 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: Adds the the following
new fields that were created for
the SVP -Baseline view to the
SVP - Flat view as well: PY
Baseline Volume, PY Baseline
Currency, Target Baseline
Volume, and Target Baseline
Currency
12-1S1GHXJ 12-1S1GHUK 8.1.1.1
ACR 480: Within Plan Promotion,
Category pick applet data is
incorrect when a plan has a
category
12-1S29NQA 12-1S29NOZ 8.1.1.1
ACR 480: Within Object Explorer,
when users query for the CPG
Plan Account Plan Team,
navigate to User Properties,
change the value of Add Account
Team from Y to N, query for the
CPG Plan Account Promotion
Promotion Team and also change
the value of Account Team from
Y to N, after the user compiles
the object, launches the
application, navigates to Plans,
creates a new plan with account
and period information, and then
checks the Plan Team field, it is
not populated with the login ID
12-1S2EV5J 12-1S2EV2Z 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
612
ACR 480: Changing an account
does not update the Plan Team
information accordingly
12-1S2EV2Q 12-1S2EV11 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: When users create an
account with team and
organization information,
navigate to Plan and create a
plan with the account set as the
account that they just created,
add period information, set the
organization to default, and
check the Plan Team
information, it should be
populated with the login ID
information, but this field is
empty. This issue also occurs
with Promotions.
12-1S2EUXT 12-1S2EUVJ 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: Makes the Deal Id field
mandatory for claim resolution
records
12-1RVOP62 12-1RVOP5D 8.1.1.1
ACR 480: When a claim
resolution is canceled, the
amount at the claim leve is not
updated accordingly
12-1S0YT2N 12-1S0YT1Y 8.1.1.1
ACR 480: Users are allowed to
create a claim resolution with a
zero or negative rate
12-1S0YT0Q 12-1S0YSZZ 8.1.1.1
ACR 480: Users are allowed to
create a claim resolution with a
zero or negative rate
12-1S0YSZQ 12-1S0YSZ1 8.1.1.1
ACR 480: When users create
claims, the application ignores
the decimal value of the rate
during calculation
12-1S0YSW4 12-1S0YSV5 8.1.1.1
ACR 480: Within the Target
Accounts tab, the New button is
enabled in the Committed Target
account applet
12-1RY2D5T 12-1RY2D54 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
ACR 480: Within Promotion >
Corporate Promotions, when
users attempt to create account
promotions from the Target
Account tab, they receive an
error message
12-1RY2D4S 12-1RY2D2P 8.1.1.1
ACR 480: Within the Authorized
Category Product tab, the
product is not bounded
12-1RYK5LL 12-1RYK5K6 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: When users copy an
account in the Authorized
Account applet, the Primary flag
is not checked for Account Team
12-1RYK5G3 12-1RYK5EO 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: After a payment is
approved or rejected, the
Approve and Reject buttons are
not disabled
12-1RYK3YO 12-1RYK3WU 8.1.1.1
new plan, drill down on the plan
name, create a new promotion,
associate a category to the
promotion, click the Products
button, click the Baseline button,
click the Aggregate button,
navigate back to the plan, and
click the Update button, the
calculation for Est Incremental
Revenue = Est Incremental
Volume x Promoted Price, but
the calculation should be Est.
Incremental Revenue = (total
volume x promoted price) -
(baseline volume x list price)
12-1RXY8AU 12-1RXY89D 8.1.1.1
ACR 480: Within the Payment
Approval view, the Amount field
in Credit Memo Payment applet
displays more than two decimal
places
12-1RYJINX 12-1RXLDGI 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
614
Promotion List, when users drill
down on an existing promotion,
click on any of the Promoted
Products in the grand child
applet, create a new deal, create
a new payment for this deal
without entering a value in the
PayTo field and step off the
record, the value of the Pay To
field does not default to the
account for which the promotion
is being run
12-1RVOL6Y 12-1RVOL5H 8.1.1.1
ACR 480: Within the Promotion
screen > Category pick applet,
the Query button does not work
12-1RXLGQL 12-1RXLGP5 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
account, log out of the
application, log back in, navigate
to the Plan screen, click the New
button, enter a plan name,
navigate to Plan Team, verify
that the MVG does not display
any values, navigate to the
Account field, click the MVG,
search for the account that they
just created, click OK, and save
the record, the Plan Team field is
not populated with the account
that they just tried to add
12-1RV785V 12-1RV784G 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
account with two members as
the Plan Team (for example,
CTRIPP and RMARCKS, log out of
the application, log back in as
the RMARCKS user, create a plan
with account and period
information, and check the Plan
Team information, the user
RMARCKS is set as the primary
user, but the application allows
the user to change the Primary
flag
12-1RV782J 12-1RV7811 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: Changing the plan
information within the
Promotions screen does not
update Plan fields accordingly
12-1RVO4UE 12-1RVO4TP 8.1.1.1
ACR 480: Deleting a plan from a
promotion does not update the
Plan fields accordingly
12-1RVO4TB 12-1RVO4SL 8.1.1.1
Plan pick list, the OK button is
not available
12-1RVO4S2 12-1RVO4QT 8.1.1.1
ACR 480: When a plan has a
category with Private Flag set to
Y, baseline values are not
updated
12-1RVO4QI 12-1RVO4PT 8.1.1.1
ACR 480: Within Promotions >
Promotion List screen, when
users create a new promotion,
associate a category to the
promotion, and enter a field in
the Off Invoice Rate field, the
field does not become read-only
12-1RUPMUC 12-1RUPMSM 8.1.1.1
Promotion List screen, the Off
Invoice Rate should become
read-only when a value is
entered for the Off Invoice Pct
field and vice versa, but this
does not occur
12-1RUPMSB 12-1RUPMQC 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
616
Promoted Category applet, the
Tactics field is not available
12-1RU7ZTM 12-1RU7ZSX 8.1.1.1
ACR 480: The values in the PY
Baseline Revenue and Target
Baseline Revenue fields are
calculated incorrectly
12-1RV0XWF 12-1RV0XRV 8.1.1.1
ACR 480: Within Promotions,
users are not able to add
products to the Promoted
Product applet
12-1RV6FVL 12-1RV6FUV 8.1.1.1
ACR 480: Provides a button on
the SVP Flat view to navigate to
Previous, Next, and Current SVP
periods
12-1RSSAP2 12-1RSSANR 8.1.1.1
ACR 480: Within Plan List > High
Level Planning, when users
create a plan and click Simulate,
12-1RUOZX8 12-1RUOZWH 8.1.1.1
ACR 480: Moves the High Leve
Planning view under Plan List
within the Plans screen
12-1RSB0SK 12-1RSB0R9 8.1.1.1
ACR 480: The PY Revenue and
Target Revenue fields should be
copied from Product Baseline
12-1RU81XF 12-1RU81VZ 8.1.1.1
ACR 480: Provides Claim
Management functionality within
Settlements > Claim List
12-1RUPJ1P 12-1RQU8CD 8.1.1.1
ACR 480: Within Admin - Data >
Account Product > Baseline
view, the PY Baseline Qty and
Target Qty fields are read-only
12-1RSB6PK 12-1RSB6OV 8.1.1.1
ACR 480: Within Account screen
> Distribution applet, the
Distribution Code, Sequence
Code, and Retail Order fields are
missing
12-1RT9Z51 12-1RT9Z3C 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
ACR 480: Delist date is updated
with the effective end date of the
product
12-1RT9Z31 12-1RT9Z1M 8.1.1.1 TYes, see
Instructions for
ACR 480 on
page 299.
ACR 480: Within Account screen
> Distribution applet, the
Auditable and List Date fields are
missing
12-1RT9Z16 12-1RT9YZW 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: Within Adminstration -
Product > Product applet, when
users select a product, update
the Effective End Date field, and
click the Update Delist Date
button, they receive an error
message
12-1RT9YZI 12-1RT9YWF 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: The Auditable and List
Date fields are missing from the
ADL applet
12-1RT9YW4 12-1RT9YUP 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: The Update Delist Date
button should be read-only in
Query mode in Product
Administration screen
12-1RT9YU6 12-1RT9YSN 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: Within the Target list
applet, Copy ADL functionality
does not work properly
12-1RT9YSE 12-1RT9YQZ 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
to Site Map > Promotion >
Corporate Promotion List, click
New, enter Promotion, Period,
and Parent Account information,
and save the record, they
message: "Promotion id
required, please enter the value"
12-1RSS2IC 12-1RSS2HN 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
618
ACR 480: Within Administration
- Data > Funds, when users
select any fund in the top applet,
navigate to the Funds Transfer
tab in the third-level level
navigation, create a new record
in the Transfer In applet, and
either press Esc or select Undo
Record from the meny, they
12-1RRTIA6 12-1RRTI9H 8.1.1.1
Authorized Distribution List >
2LNV detail list > Account
product applet, the following
fields are missing: SKU/UPC,
Allocated Units, Seq. Code, Date
Added, Date Changed, Effective
Start, and Effective End, and
within the Authorized Category
product applet, the following
fields are missing: Allocated
Units, Effective Start, and
Effective End
12-1RSAYSM 12-1RSAYR6 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
ACR 480: Within >
Adminstration - Authorized
Distribution List, when users
click on the 2LNV detail list,
navigate to the Account Product
applet, click the New button, and
select a product, the date is
defaulted to the current date,
but the time is defaulted to
12:00:00 AM
12-1RSAYP2 12-1RSAYNN 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
Authorized Distribution List,
when users click on the 2LNV
detail list, navigate to the
Account Product applet, click the
New button, and select the
Product pick applet, the applet
opens in query mode
12-1RQU5AA 12-1RQU57X 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
ACR 480: Some fields within
High Level Category are not
copied to Promoted Category
12-1RRI4MW 12-1RRI4LT 8.1.1.1
ACR 480: Within Accounts >
High Level Planning, the Account
field is not defaulted to the
parent account
12-1RRI4LI 12-1RRI4KT 8.1.1.1
enhancements:
Resolves key connection
gaps between core
processes: marketing and
trade management, trade
management and retail
execution
Provides key functional
enhancements needed to
fulfill Oracle Trade
Management process.
Significantly enhances
usability across trade
management in Siebel
applications.
12-1RHR1SG 12-1RKLYHL 8.1.1.1 Yes, see
Instructions for
ACR 480 on
page 299.
Customer Order
Management
Configurator
On the AIX platform, when users
configure a product and
encounter an error message,
clicking the Explanation button
on the error page causes the
12-1TYASEC 12-1QUOKCX 8.1.1.1
RaiseErrorText does not work
properly within Customizable
Products script
12-1T03JT6 12-1SWPR8F 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
620
When users modify an installed
asset that has had changes
made to the class relationships
in the workspace version, they
receive an error message stating
that the component product is
being removed
12-1T03XIC 12-1SFOTK9 8.1.1.1
The Begin Configuration Web
service does not add the default
product to the instance
12-1SQFLCT 12-1S1GFK5 8.1.1.1
AutoMatch Promotion
functionality does not work in
Remote Configurator
12-1SM2Y98 12-1SB8JB4 8.1.1.1
After Siebel 8.0.0.5 QF6501 has
been applied, child product
scripts in eConfigurator are not
run, and the scripts on the root
are run instead
12-1SMKVHR 12-1SINAW9 8.1.1.1
BatchValidate returns the wrong
status on modified quotes
12-1SJ5CJI 12-1SFPA4D 8.1.1.1
Configurator crashes when
invoking the 'CopyXA' method
12-1RZ1HIB 12-1LG27LD 8.1.1.1
Product Configurator :Scripting
the Attribute_Changed event
impacts performance on UNIX
12-1RY2OPU 12-1RNYSBH 8.1.1.1
Constraints on product quantity
do not calculate correctly when
products are exploded
12-1RAJ7W8 12-1PI44DB 8.1.1.1 Yes, see
Instructions for
FR 12-1RAJ7W8
on page 765.
Batch Validate should set the
status to invalid and populate
the error message when
validating a missing required
attribute
12-1R8LSHO 12-1R1VGAZ 8.1.1.1
Within the Configurator UI,
existing but ineligible items are
not visible
12-1QH5LLS 12-1Q25XGN 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
The Customize icon should not
appear within a Configurator
session for child items that have
product type marked as 'non
structure
12-1Q2NGYC 12-1GVJ1I5 8.1.1.1
Changing a promotion or an
upgrade promotion on an order
line item does not update
products correctly
12-1PLH1UO 12-1PILEIJ 8.1.1.1
After users upgrade, all UI
values that are attached to
attribute display values are
missing
12-1PLGJCL 12-1P55Q2H 8.1.1.1
In Configurator, an attribute pick
list cannot be filtered by a value
of a hidden attribute
12-1PILI4L 12-1J9GEWZ 8.1.1.1
Custom rules cause the Object
Manager to crash
12-1OTUXFZ 12-1MFCJ25 8.1.1.1
BatchValidate does not create
child items
12-
1OOWDM5
12-1NCHH5Z 8.1.1.1
Component-based routing can
fail if the components are not
enabled in all of the servers after
Siebel Server has attempted
routing five times
12-
1OMWL5M
12-1O139AX 8.1.1.1
After users have applied Siebel
8.0.0.2 QF0218, they receive the
following error message when
they attempt to configure a
product:
"We detected an Error which
may have occurred for one or
more of the following reasons:
Error invoking service
'Configurator Service', method
'GetDomainRowSet' at step 'Pre
Pick Get Row Set'.(SBL-BPR-
00162)
12-
1O7OYPW
12-1NWD809 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
622
When users upgrade, some
product constraint rules cause
attribute values to display in red
12-1NXSFEU 12-1NKJKRL 8.1.1.1
Within eConfigurator running on
a Standard Interactivity client,
when users click quickly on
attributes and then click the
Done button, the application
hangs
12-1NTIUSH 12-1N3J0OL 8.1.1.1
A Object Manager memory leak
occurs when users perform the
Done operation within
Configurator
12-
1NNUXWO
12-1N03OFF 8.1.1.1
Promotion policy enforcement
results in incorrect behavior
upon the first promotion policy
violation 'undo' operation
12-1N22KA2 12-1LVX3H3 8.1.1.1
Eligibility Display mode 2 is not
hiding in eligible products
12-1N22K77 12-1MGHHF6 8.1.1.1
Global variables do not work in
eScript within Configurator
12-1N22K4B 12-1MBQUCS 8.1.1.1
Wrong validation results occur
with Promotions and
Customizable Products
12-1N1RDOP 12-1LY4CD9 8.1.1.1 Yes, see
Instructions for
FR 12-1N1RDOP
on page 760.
Invalid workers are not
immediately inactivated or
dropped to avoid their being
used by other Configurator
sessions
12-1MJW3F9 12-1L9C3FT 8.1.1.1
Smartpart numbers based on
Attribute Matrix do not update
the smart part number correctly
for child components when
customized twice
12-
1M0PGOQ
12-1M0PGMJ 8.1.1.1
Order Management
Batch Validate does not give
expected output for incomplete
quotes or orders
12-1TK9032 12-1T7DFU1 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
When an auto contract is
inserted from an order, an error
message appears that states
that the value for the
CCNUM_ENCRPKEY_REF column
the S_AGREE_TERMS' table
occurs twice in the same
statement'.
12-1SM2HO1 12-1SI5HGB 8.1.1.1
When users create a bulk order
of the Modify type and try to
update Start Date in the action
set, the start date on the order is
not updated
12-1SJO2TA 12-1S7POKB 8.1.1.1
Bundles the Promotion and
Product class relationship so that
changing a promotion in a
change order loads the default
product (ACR 471)
12-1S8QOEL 12-1P81O39 8.1.1.1 Yes, see
Instructions for
ACR 471 on
page 163.
Enforces Max and Min cardinality
for Bulk Orders functionality
12-1RVOKIA 12-1QL0MPH 8.1.1.1 Yes,
seeInstructions
for FR 12-
1RVOKIA on
page 773.
Cursors remain open after a
promotion creates an agreement
12-1RNYLCO 12-1QZXUMT 8.1.1.1
When users click on Product
Category in the Quotes screen
after DVM, they receive Siebel
error message SBL-DAT_00309
12-1RIPN17 12-1ORVK5E 8.1.1.1 Yes, see
Instructions for
FR 12-1RIPN17
on page 766.
Date calculation in Row Set
Transformation Toolkit does not
work consistently
12-1RHA20H 12-1P9YKJD 8.1.1.1
A validation problem occurs with
inserting and associating a
record from an MVG applet
12-
1QQ9WQW
12-1PQ8RSX 8.1.1.1
Users are unable to update
payment profiles it the profile
has been created using special
characters (such as
apostrophes)
12-1OUUFYF 12-1OJ22KN 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
624
Orders
The SIS OM PMT Service's
Synchronize method leaves
rogue cursors open, which
consumes system resources
12-1QMFLED 12-1QL0ID7 8.1.1.1
When adding Customizable
Products or promotions using
web services, only Customizable
Products are added, not the
default components in a sales
order
12-
1OK5WH7
12-1NZNRV3 8.1.1.1
Application Deployment Manager
Workspace file import fails
12-1RAJ8OH 12-1PT60R3 8.1.1.1 Yes, see
Instructions for
FR 12-1RAJ8OH
on page 766.
Pricer
When users accept an upsell
recommendation product on an
order, the following error
message appears: Error invoking
service '<?>', method '<?>' at
step '<?>' (SBL-BPR-00162)
12-1SF7G9Z 12-1RZJE8H 8.1.1.1
Products
ACR 471: The system crashes
while executingthe iLog Rule test
case
12-1TYASDV 12-1TK3Z1X 8.1.1.1
The Upgrade Promotion function
does not correctly apply
constraints
12-1NT21HP 12-1N3J0VT 8.1.1.1
Data Quality
Other
In Siebel 8.1.1, Data Quality
does not work as expected if
both DeDup and DataCleansing
are enabled
12-1STTNB0 12-1PCDF0P 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Data Validation Manager: Non-
active fields are activated by the
DVM engine
12-1RSRZYQ 12-1QV5W5B 8.1.1.1
Financial Services
Other
Adds the following views in FINS
(1208 and 1209):
Screen:
Catalog Admin Screen
Views:
Catalog Admin Detail View -
Catalog Detail
Catalog Admin Detail View -
Products
Screen:
ISS Unified Administration
Screen
Views:
Category Master Data View -
Products
Product Catalog Admin
Detail View - Catalog Detail
Product Catalog Admin
Detail View - Products
ISS Product Versions View
ISS Product Attributes VBC
12-1R3SH2T 12-1QCSQ49 8.1.1.1
Within the FINS CEM Calculation
business service, the Calculate
method does not work after
users drill down
12-1QDA84B 12-1ORDCF9 8.1.1.1
Other-Retail Finance
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
626
Provides Siebel Financial
Services Customer Order
Management for Banking
functionality (ACR 467).
12-1S987PV 12-1QT7XTB 8.1.1.1 Yes, see
Instructions for
ACR 467 on
page 156.
General
Access Control
Prevents users from opening
multiple sessions on the Mobile
Web Client (ACR 432)
12-
1O4OGQ1
12-1L89B79 8.1.1.1
Application
Deployment Manager
HTTP deployment of the Rules
Engine data type fails
12-1QODT6O 12-1PZOO3C 8.1.1.1
ACR456: Allows users to perform
Assignment Manager bulk-data
maintenance (CRUD on Rules,
Positions, candidates and so
forth) through client views and
screens
12-1Q2NT7U 12-1ORUZ7R 8.1.1.1 Yes, see
Instructions for
ACR 456 on
page 102.
ACR 456: Within the transaction
log, the time stamp is not correct
for imported and exported files
(Linux-specific error)
12-1TXC0BL 12-1TXC0A2 8.1.1.1 Yes, see
Instructions for
ACR 456 on
page 102.
ACR 456:When users navigate to
Admin Group > Positions, drill
down on a position, and click
Export, the following session
warning error message appears:
The server you are trying to
access is either busy or
experiencing difficulties. Please
close the Web
12-1TKAELA 12-1TKAEJI 8.1.1.1 Yes, see
Instructions for
ACR 456 on
page 102.
ACR 456: The default value for
export operations should be
Upsert
12-1TETVRS 12-1TE65KB 8.1.1.1
ACR 456: When users attempt to
import an empty csv file, they do
not receive an error message
12-1TETVPG 12-1TETVNL 8.1.1.1 Yes, see
Instructions for
ACR 456 on
page 102.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
ACR 456: If exported data
contains a percentage sign, the
import fails
12-1TETVMR 12-1TETVL9 8.1.1.1
ACR 456: Improves the quality
of Assignment Manager error
messages related to ACR 456
12-1SZ4I4Z 12-1SZ4I3F 8.1.1.1
export an Assignment Rule that
does not contain data in the child
applet, they should receive an
error message
12-1SUAR8D 12-1SREMIN 8.1.1.1 Yes, see
Instructions for
ACR 456 on
page 102.
ACR 456: Within the Admin-
Group > Skill view, the Import
Data Skill button is not required
12-1SSUPOB 12-1SSUPNP 8.1.1.1 Yes, see
Instructions for
FR 12-1SSUPOB
on page 772.
import a csv file that does not
contain names or locatios in the
Import dialob box, the incorrect
error message displays
12-1SSUPFB 12-1SSUPCK 8.1.1.1 Yes, see
Instructions for
ACR 456 on
page 102.
ACR456: Deleting a missing
portion of an input record does
not yield an error message
12-1SSUPF2 12-1SSUPD9 8.1.1.1 Yes, see
Instructions for
FR 12-1SSUPF2
on page 771.
ACR456: When users omit skill
information from a csv file, they
do not receive an error message
when they attempt to import the
csv file
12-1SSUPET 12-1SSUPE3 8.1.1.1 Yes, see
Instructions for
ACR 456 on
page 102.
ACR 456: The dialog box name
for Import displays as Position
Skill Export but it should be
Position Skill Import
12-1SSCJTW 12-1SSCJQY 8.1.1.1 Yes, see
Instructions for
FR 12-1SSCJTW
on page 772.
ACR456: When the server is
bounced, the ServerDataSrc
folder in the log directory is
deleted
12-1SREMH3 12-1SREMB7 8.1.1.1 Yes, see
Instructions for
ACR 456 on
page 102.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
628
ACR 456: When the Siebel
Server and the Call Center
application reside on different
servers, users receive the
following error message when
they attempt to import a file: We
detected an Error which may
have occurred for one or more of
the following reasons:
An error happened during
restoring the context for
requested location.(SBL-UIF-
00313)
12-1SREMAH 12-1SREM9V 8.1.1.1 Yes, see
Instructions for
ACR 456 on
page 102.
ACR 456: When users export
rules that have had some criteria
and criteria values added to
them, enter numeric values for
Assignment Scores files with the
operation to be updated into the
csv file, and then import the
edited csv file into Call Center,
the score field is not updated,
and no error code or error
message is generated in the log
file
12-1SPXSIK 12-1SPXSI3 8.1.1.1 Yes, see
Instructions for
FR 12-1SPXSIK
on page 771.
ACR 456: The status of imports
does not change, regardless of
whether the import succeeded or
failed
12-1SPXSHM 12-1SPXSGV 8.1.1.1 Yes, see
Instructions for
ACR 456 on
page 102.
Audit Trail
The audit trail is not in sync with
server from mobile client
12-1TE6CIJ 12-1TE6CHR 8.1.1.1
Running EIM with
EnableEimAuditing set to TRUE
leads to an error message
12-1RQUQEX 12-1M0WC9R 8.1.1.1
Business Rules
Only one
knowledgebase:module
combination at a time is active
12-1TARV4S 12-1SW8CMD 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
The application may stop
functioning when calling Haley
Rules from runtime events
12-
1QODHWT
12-1QL06E5 8.1.1.1
Data Validation Manager opens
database cursors and forgets to
close them
12-1QAH5TF 12-1PLG9R7 8.1.1.1
The Data Validation Engine is not
called correctly on the
PickRecord event, and rules are
fired incorrectly
12-1OVTT1V 12-1NJKYC7 8.1.1.1 Yes, see
Instructions for
FR 12-1OVTT1V
on page 768.
Calendar
With Internet Explorer 8, a
double border appears around
calendar appointments
12-1SJ56UP 12-1SJ56TU 8.1.1.1
With Internet Explorer 8, within
Call Center, when users navigate
to Calendar, click the Daily tab
after verifying that there are
existing appointments, click
Print, select Todays Activities
(Calendar Format), and click
Run, they either receive an error
message stating that the server
threw an exception or they are
notified that Internet Explorer
has stopped working
12-1SJ56TJ 12-1SJ56SC 8.1.1.1 Yes, see
Instructions for
FR 12-1SJ56TJ
on page 773.
ACR 435 resolves the following
issues with the printed version of
the 5 Day Weekly HTML
Calendar: The calendar only
shows appointments that are
scheduled within the 8 a.m. to 5
p.m. workday, the default page
orientation for most printers is
set to Portrait, changing the
display intervals on the Calendar
results in sporadic results, and
Contact Name, Primary Phone,
and Description should be
displayed on the 5 Day Weekly
Calendar for each appointment.
12-1QFPE7F 12-WXG93N 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
630
The Contact icon is not available
when drilldown has been
configured
12-1PZO53U 12-1OFLU7D 8.1.1.1
Within the ePharma application,
when users navigate to the
eCalendar screen > LS Pharma
HI Activity Calendar view, and
drag and drop an contact on the
daily calendar onto the last
available time slot, a script error
occurs when users resize, move,
or drag the record off of the
calendar area
12-1PZO52G 12-1OB4JHF 8.1.1.1
A user is able to delete an
appointment in another user's
calendar even with read-only
access
12-1PZ4Q5K 12-1N31LWO 8.1.1.1
When users click the Query
button in Calendar My To Do's
List Applet, the applet size
increases and the controls stop
working, and when users click
the Go button, the button does
not work the first time, but it
does work when users click it
again
12-1PSNEQB 12-1JN9R0J 8.1.1.1
Correspondence
Custom Contact / Proposal
objects do not generate properly
12-1QMG1J3 12-1P81NR1 8.1.1.1
Global/Multilingual
LOV
Adds translations for features
and fixes in the Siebel 8.1.1.1
Fix Pack
12-1S5T3K5 12-1S5T3JL 8.1.1.1
Installation
Siebel Enterprise Server patch
installation is blocked on the
Linux platform
12-1U0CAEA 12-1TARCGM 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Network Image Creator does not
expose both the SEA and the SIA
options
12-
1SDQHGZ
12-1SDQHGF 8.1.1.1
For the Siebel Web Client,
incorrect text appears in the
base.txt file
12-1SCQCYI 12-1SCQCXT 8.1.1.1
After a new Gateway Name
Server has been created, the
installer crashes when
navigating back to the main
menu
12-1RZ1JB1 12-1RNH59T 8.1.1.1
Provides an OPatch to allow
customers to install or uninstall
8.1.1 Quick Fixes for Siebel Tools
or Siebel Mobile Web Client
12-1R7SLGL 12-1R7SLG1 8.1.1.1
The Publish product information
to Siebel Update Server option
in Network Image Creator is
obsolete and should not display
12-1QH5ECK 12-1QDRA0T 8.1.1.1
Users are unable to install
multiple languages using the
Unattended Configuration
function
12-1N22JTR 12-1LQUP21 8.1.1.1
Office
Provides support for Microsoft
Office 2007 with Document
Server and Siebel Search (ACR
409)
12-1N1Q81D 12-1IDNOO9 8.1.1.1 Yes, see
Instructions for
FR 12-1N1Q81D
on page 760.
Other
After Siebel 8.0.0.2 QFA205 has
been apllied, the Dedicated
Client crashes when the
Business Service Invoke method
is called
12-1TK99SO 12-1SM30JX 8.1.1.1
Changes the default value for
"allow reverse scans" for DB2 v9
12-1TS5GM7 12-1S5BJ8W 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
632
When string variables containing
the empty string are used in
boolean expressions they fail to
evaluate correctly and the script
will abort bypassing catch and
finally clauses
12-1TK99Q5 12-1TAR58L 8.1.1.1
Improves the quality of error
messages related to integrations
12-1SXOQ2S 12-1SXP5CT 8.1.1.1
The DBinit function fails on the
mobile client
12-1SUB0QJ 12-1SUAZVN 8.1.1.1
When calling object scripts
written in Siebel Visual Basic
from scripts written in Siebel
eScript the following error
occurs: The method
'SomeMethodName' is not
supported on Business Service
'SomeBusinessServiceName'.(S
BL-DAT-00323)
12-1SSUEYF 12-1SSCEWB 8.1.1.1
If a script references an object
using "with" so that methods do
not have to repeatedly use the
object reference, the script fails
12-
1SBQM0M
12-1RVOMWT 8.1.1.1
using Find functionality causes a
runtime error
12-1S7SIUA 12-1S1FXDF 8.1.1.1
Replacement of OCIStmtFetch
with OCIStmtFetch2 for Oracle
10g support
12-1S2JFXL 12-1S2JFWV 8.1.1.1
Calling GetService in
eConfigurator scripts queries all
available services, not just the
one specified in the function's
argument, which can cause
performance degradation
12-1RGSQ74 12-1R1VZN3 8.1.1.1
Provides the Next Step capability
for TASK UI
12-1REDG33 12-1REDG1H 8.1.1.1
The Gateway Server cannot
connect to the database
12-1RAJFNC 12-1PBDVO1 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Invoking methods in .NET COM
dlls sometimes fails in eScript
12-1RDFC53 12-1QER4G3 8.1.1.1
Tags Object-Manager-generated
SQL with user session
information to allow the
administrator to trace any slow
or bad SQL back to its
originating Object-Manager-
based task
12-1R84Y40 12-1R4AL4P 8.1.1.1
Having only a single line of script
in ST engine causes a runtime
error
12-1QXJDNV 12-1Q7IUCR 8.1.1.1
Within eScript, when variables
used in "with" blocks are
declared outside of the "with"
block, they are not recognized
12-1QXJDMR 12-1Q9Z7W1 8.1.1.1
When certain scripts are used in
the new scripting engine, cursor
leaks occur
12-1QODT7F 12-1PMW6OI 8.1.1.1
When attach certs using
mwcontrol are installed, EAI
HTTP Transport is used to
connect to an MA-enabled
server, when the following is
specified for certs:
oInputs.SetProperty("HTTPCertA
uthority",
"CN=DPTIPSEC,DC=dwpptp,DC
=londondc,DC=com");
// Set the Serial Number of the
Client Certificate
oInputs.SetProperty("HTTPCertS
erialNo",
"1107BA79000000000002");
the certifications are not found
12-
1QODWZU
12-1OQU1KJ 8.1.1.1
During upgrade attempts, the
Development database DDLIMP
fails while attempting to recreate
existing indexes
12-1NU063L 12-1NTZMQP 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
634
PIM Server
Integration
SSSE Embedded Outlook
Calendar fails on IE7
12-1QYIVKD 12-1NSKQ0N 8.1.1.1
When a Siebel contact is enabled
for synchronization, and the
matching contact (first name,
last name, email address) exists
in Outlook, the existing contact
is not matched
12-1Q06AUV 12-1OFLUNH 8.1.1.1
ACR 369: Updates the
permissions script to grant
permissions using Exchange
Shell
12-1O3Y6VC 12-1O1KGDB 8.1.1.1
Provides the ability to use
Exchange as system of record for
calendar attendees
12-1N1QJYA 12-1LTGS5B 8.1.1.1
If a PIMSI share is unavailable at
startup, the PIMSI Engine
component dies
12-
1MQCM12
12-1MQCFNM 8.1.1.1
When an Exchange calendar
item includes
"mailto:address@domain.com"
(as opposed to
"address@domain.com"), the
item is not parsed properly
during inbound synchronization
12-1S2WDXF 12-1RW60TB 8.1.1.1
There is no email notification
when a record is not processed
by Exchange Connector
12-1RPHOHG 12-1RPHO7U 8.1.1.1
System-wide configurations
performed for UserMailBoxID are
not reflected in the logs
12-1R7MVJZ 12-1L51WBF 8.1.1.1
SSSE skips record-level failures
of any kind during integration
12-1QUOI8I 12-1QT8EZN 8.1.1.1
Contact categories other than
"Siebel Contact" are not
preserved during outbound
contact sync
12-1QTPBL0 12-XLYU4T 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
When synching, an error
indicating a duplicate attendee is
shown in the attendee cache
12-1QL0MAF 12-1QJJA4H 8.1.1.1
If the "Category Field" for the
contact domain is changed from
the default "Category," contact
matching fails during
synchronization
12-1QDR9DV 12-1QBCIEN 8.1.1.1
Provides support for Outlook
2007 Embedded Outlook
Calendar (ACR 369)
12-1P1AWIT 12-1OXSN8J 8.1.1.1
ACR 481: Provides the ability to
ignore Outlook appointments/
tasks based on the Private flag
12-1MX8ZG9 12-1LY4V61 8.1.1.1
ACR 481: Addresses an issue
where the Outlook Add-in can
lock a user out of his/her
account after changing the
password on the authenticating
agent (e.g., Active Directory),
but have not updated their
Outlook Add-in password
12-1MQCFG3 12-1MBR3N7 8.1.1.1
Platforms
Applications do not switch from
http to https when
SecureBrowse = TRUE, HTTPS
12-1TK84BZ 12-HFIYXK 8.1.1.1
The Mainwin version command
("mwversion") does not display
the version and patch level
12-1T8C7B4 12-1T8C79H 8.1.1.1
On Solaris, after Siebel 8.1.1.1
has been installed, the Call
Center application is unavailable
12-1T6VFL8 12-1T6VFKJ 8.1.1.1
Remote
ACR432: A blank error message
displays when users try to
launch multiple Mobile Web
Client Sessions
12-1U087L1 12-1S7PRXF 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
636
Transaction Processor becomes
slow when it processes large set-
based transactions logged by
EIM
12-1TK4ZPR 12-1T2IN2L 8.1.1.1
On the local database, manager
visibility is not changed after
subordinates have been
removed
12-1SPGXZK 12-1S4C8GR 8.1.1.1
If you have more than one case-
insensitive indexed column on a
table, GennewDb fails
12-1SC3OLN 12-1S8QNHX 8.1.1.1
Repagent fails with the following
error message: ORA-01400:
cannot insert NULL into
("ORA05299"."S_AUDIT_ITEM".
"BUSCOMP_NAME
12-1R1VGZM 12-1R1VGYV 8.1.1.1
MLOV-enabled fields display
incorrect values after applying
CIAI table changes to database
12-1QU74G4 12-1NWCZ8F 8.1.1.1
Applying database schema kits
fails if CIAI is enabled on
S_USER
12-1QODYE6 12-1Q71PB5 8.1.1.1
When the initialization process i s
attempted on the Siebel Mobile
Web Client, users receive the
following error message: "An
Unsupported Operation was
attempted.
12-1Q25ZLO 12-1EFZ3Q9 8.1.1.1
Login lockout time is expressed
in days instead of minutes and
the value can only be an integer
12-
1HMLBHM
12-1H2HO3L 8.1.1.1
Report Designer
The BI Publisher Report applet
cannot be closed using the X icon
12-1SQFISM 12-1SQFIRV 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Provides the following
enhancements for BI Publisher:
Enables reports with
parameters.
Enables scheduling.
Provides a new Web service
to support the new BI
Publisher security model.
12-1SFP3WR 12-1SFP3UM 8.1.1.1 Yes, see
Instructions for
BI Publisher
Enhancements
on page 466.
Users are unable to update the
rtf template in the Report
Template Registration view for
existing records
12-1RAJ9OJ 12-1Q353O9 8.1.1.1
Reports Server
Within the Schedule a Report
dialog box, when users click the
Cancel button, the window does
not close
12-1TCP6D1 12-1TCP6BM 8.1.1.1
When users click the BIP icon >
Account List Report link, the
application crashes
12-1U5S3EF 12-1U5S3DL 8.1.1.1
BI Publisher: Users are unable to
choose a different report format
once they have run a report
using the default method
12-1TH5MF4 12-1TH5MDM 8.1.1.1
BI Publisher: Clicking the Close
button does not close the Report
window
12-1TH5MDA 12-1TH5MBQ 8.1.1.1
The BIPDataService.xml and
BIPSiebelSecurityWS.xml files
are missing from the patch
installer
12-1TG6D0Q 12-1TG6D01 8.1.1.1
BI Publisher: The SiebelXMLP.jar
file is outdated
12-1TG5CZR 12-1TG5CZ2 8.1.1.1
The path of dataservice.wsdl is
hardcoded to a absolute path
12-1TG5CYT 12-1TG5CY4 8.1.1.1
BI Publisher: The XMLP Driver
Service Business Service is
missing the GetAllRoles method
12-1TG5EFC 12-1TG5EED 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
638
Error messages display behind
the active window and users
must minimize the application
window to be able to see the
error messages
12-1TE6GDE 12-1TE6FZ1 8.1.1.1
Within the application, when
users navigate to Account >
Account List > BIP icon, and click
Account List Report, the picklist
spelling is incorrect in the
Reports Run dialog box
12-1TE6GD3 12-1TE6G7O 8.1.1.1
Users who do not have the
appropriate responsibility can
see the Schedule Reports menu
12-1TDOSFC 12-1TDOSDX 8.1.1.1
When users download a
template from Administration-
BIP Reports, make changes to
the template and save them, and
then upload the updated .rtf
template, the changes that the
user made are not saved
12-1TCP6DA 12-1TCP6A6 8.1.1.1
When users click the BIP icon
and navigate to Schedule >
Schedule Report, the Schedule
dialog box displays the values
from the last report that was
run, and users cannot enter new
data in any fields other than in
the Job Name field
12-1TCP6A1 12-1TCP68R 8.1.1.1
When users run a report, close
the parameterized report
window, and then navigate to
BIP Report Menu > Account List,
the Schedule Report and
Parameterized Report dialog
boxes open together
12-1TB8SBT 12-1TAREQG 8.1.1.1
When users schedule reports
using the Run Immediately
option in PDF format, and then
click the Schedule button, the
Schedule Report window resizes
12-1TB8S9I 12-1TAREOW 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
When users schedule reports
with the Run Immediately option
in PDF format, navigate to BIP
Menu > My BI Publisher Reports
> My Jobs, and click the
Document icon, the report
output contains no data
12-1TB8S8G 12-1TARENH 8.1.1.1
Provides the following fixes and
enhancements for BI Publisher:
Corrects an issue where
different users receive the
same report output after
scheduling
Adds default values to the
report schedule applet
Adds field input validation
for the report schedule
applet
Adds symbolic strings for the
parameterization applet
Fixes a display problem with
parameterization
Optimizes the BI Publisher
code
12-1SW88PJ 12-1SW88O5 8.1.1.1 Yes, see
Instructions for
BI Publisher
Enhancements
on page 466.
Provides XMLP Integration -
Schedule Reports functionality
12-1SFP3X0 12-1SFP3TR 8.1.1.1 Yes, see
Instructions for
BI Publisher
Enhancements
on page 466.
Provides XMLP Integration - User
Management, and new Web
services for BI Publisher's new
Security Model
12-1SFP3W8 12-1SFP3VD 8.1.1.1
When generating a report from a
view where the primary applet
has a search specification, this
expression is not passed as part
of the report query
12-1QJJWDF 12-1Q37ZF9 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
640
Within Siebel Tools > Object
Explorer, the Reports option
should not display
12-1QDRPN2 12-1PS529D 8.1.1.1
Method input arguments are
missing in the XMLP Driver
Service business service
12-
1QDRNNC
12-1PW3PQ9 8.1.1.1
Corrects instances of BIP to BI
Publisher throughout the
interface
12-1QCSJWS 12-1P90KAL 8.1.1.1
BI Publisher: The Routing Model
field is not populated in the
Mobile User Summary Report
12-1Q35LZW 12-1Q06K23 8.1.1.1 Yes, see
Instructions for
FR 12-1Q35LZW
on page 761.
Search
ACR 403: Users cannot open the
search center from the All
Opportunities page
12-1RBZCK1 12-1NCHNGC 8.1.1.1 Yes, see
Instructions for
ACR 403 on
page 45.
ACR403: Drilldown on Search
results does not work
12-1S1XV7D 12-1NGQQVD 8.1.1.1 Yes, see
Instructions for
ACR 403 on
page 45.
Provides Disconnected Search
for Siebel Mobile Client (ACR
403)
12-1L9AXI2 12-1L8TZWR 8.1.1.1 Yes, see
Instructions for
ACR 403 on
page 45.
ACR439: Provides the ability to
show Search results in the left
pane.
12-1M7YTQL 12-1M7YTKT 8.1.1.1 Yes, see
Instructions for
ACR 439 on
page 95.
ACR 439: After Search Center is
closed, Last Find and its search
criteria are not retained
12-1S7PQRR 12-1R49VTZ 8.1.1.1 Yes, see
Instructions for
FR 12-1S7PQRR
on page 768.
Prepopulates Search terms and
sets defaults in the search task
pane (ACR 439)
12-1RBZCM1 12-1NCHP85 8.1.1.1 Yes, see
Instructions for
ACR 439 on
page 95.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
been set up, when users launch
Call Center, navigate to
Administration - Search >
Search Index Settings and
attempt to index a Business
Component (such as the Contact
BC), the feed files are not
generated, and SCCObjMgr_enu
shows the following error
message: SBL-SRH-00186: An
unrecognized adapter class
'CSSOSESAdapter' was specified
for the search engine 'OSES'
12-1TARBRC 12-1TARBQD 8.1.1.1 Yes, see
Instructions for
ACR 452 on
page 100.
ACR 452: Provides Siebel Search
support for languages other than
ENU
12-1TARYMD 12-1T0KYST 8.1.1.1 Yes, see
Instructions for
ACR 452 on
page 100.
ACR452: OSES Integration
uptake: Auto keyword
generation
12-1P5O4RM 12-1OQD10Y 8.1.1.1 Yes, see
Instructions for
FR 12-1P5O4RM
on page 761.
ACR452: OSES integration
uptake: Search by file format
12-1P5O4MN 12-1OQD13S 8.1.1.1 Yes, see
Instructions for
ACR 452 on
page 100.
uptake: Mixed Operator Search
12-1P56B8M 12-1ORBTGJ 8.1.1.1 Yes, see
Instructions for
ACR 452 on
page 100.
uptake: Dynamic Weights
12-1ORBTNH 12-1ORBTM7 8.1.1.1 Yes, see
Instructions for
ACR 452 on
page 100.
The Administration - Mobile
Search > Search Index Settings
> SCC FTP Location field label is
incorrect
12-1S1XV5H 12-1OXSZ78 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
642
When configuring the Find
Applet to display the result in the
main pane, the error message
thrown by RaiseErrorText does
not appear on the UI when it is
invoked by the Find object
12-1RPEVGE 12-1QJ1W1B 8.1.1.1
With Siebel 8.0.0.5, using Siebel
Find to drill down into records
and then clicking the Back
button results in the SBL-UIF-
00335 error message
12-1RH9JAH 12-1R4A1BH 8.1.1.1
With Oracle SES, when searches
contain quotation marks, the
queries fail
12-1RGSQ4A 12-1PBVDYL 8.1.1.1
Allows customers to toggle
between views (ACR 439)
12-1RBZCO1 12-1N3J0NR 8.1.1.1 Yes, see
Instructions for
ACR 439 on
page 95.
The sequence in the Look In
drop-down list does not change
even after the sequence has
been changed in Siebel Tools
(ACR 439)
12-1RBZCN1 12-1NABW5J 8.1.1.1
ACR 403: Does not contain/
Exact Phase/with exact phase is
not working properly
12-1RBZCJ1 12-1NFSUUI 8.1.1.1
Allows Find and Attach
functionality to have the parent
relationship be based on the
parent applet (ACR 439)
12-1RBZCI0 12-1O4OT5J 8.1.1.1 Yes, see
Instructions for
ACR 439 on
page 95.
ACR 439: Associates button
availability based on the parent
applet, as with Siebel
applications version 7.8
12-1RBZCH0 12-1O4OT68 8.1.1.1 Yes, see
Instructions for
ACR 439 on
page 95.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Implements Preview with Find,
as in Siebel 7.x applications.
With this enhancement, when
users click the Binoculars icon,
perform a search using the Find
object, select a single result line
item and click on Preview, the
selected result is displayed as a
popup window.
Note: The preview is not
applicable when users are
viewing the results in the
Business Component view. (ACR
439)
12-1RBZCFZ 12-1O4OT7M 8.1.1.1 Yes, see
Instructions for
ACR 439 on
page 95.
ACR439: Implements Preview
with Search functionality to
match the behavior that was
available with Siebel applications
version 7.x
12-1RBZCEZ 12-1O4OT91 8.1.1.1 Yes, see
Instructions for
ACR 439 on
page 95.
ACR439: Converts "Saved
Searches" from an HTML list to a
drop-down pick list
12-1RBZCDZ 12-1O4OTAF 8.1.1.1 Yes, see
Instructions for
ACR 439 on
page 95.
ACR439: The Advanced Search
button should only be activated
when a search engine has been
configured
12-1RBZCCX 12-1O4OTBW 8.1.1.1
ACR 439: Blank records are
yielded when users perform the
Find operation
12-
1RBZCBW
12-1P55M4B 8.1.1.1
After ACR 439 has been applied,
Previous Search criteria are lost
12-1RBZCAU 12-1P55M5L 8.1.1.1
There should not be a Search
Definition dependency for the
FIND function
12-1RBZC9U 12-1PG7SQT 8.1.1.1
Makes "Recent Saved Searches"
only appear when a search
engine has been configured
12-1RBZC8U 12-1PLXUCJ 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
644
When Windows Desktop Search
is not installed, Basic Search
unexpectedly closes the Mobile
Client.
12-1RBI95M 12-1PZ42DC 8.1.1.1
ACR 452: Exact Search with
quotes replaces delimiters with
&quote:
12-1TAA6DH 12-1SZEIXA 8.1.1.1
ACR 403: Indexing is not
working on the Mobile Web Client
12-1STT0AE 12-1STT095 8.1.1.1
ACR 452: Data import using
import.bat fails
12-1STTMYT 12-1STTMY4 8.1.1.1
ACR 452: Auto Keyword
Generation is not refining the
Search
12-1TYARO5 12-1TYARMF 8.1.1.1
ACR 452: Searching for strings
with double quotes or "None of
These Words" yields an error
message
12-1TUW2TZ 12-1TUW2RV 8.1.1.1
ACR 452: Searching using a
wildcard or a single letter
followed by a wildcard should
yield an error message but it
does not
12-1TUW2PA 12-1TUW2IJ 8.1.1.1
ACR 452: Within the
Administration Search - Search
Connector Setting page,
changes the labels of the Deploy
and Undeploy buttons to Create
Source and Delete Source,
respectively
12-1THOE42 12-1THOE3D 8.1.1.1 Yes, see
Instructions for
ACR 452 on
page 100.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
ACR 452: Within the Call Center
application, when users index
the Opportunities Business
Component, add new
Opportunity record, navigate to
Search Admin > Search Index
Settings, and refresh the
Opportunity BC, they receive the
following error message even if
new Opportunity records were
successfully added: "No records
found for indexing
purpose.(SBL-SRH-00225)"
12-1TD6T75 12-1TD6T55 8.1.1.1
been set up, when users log into
the application as SADMIN/
MSSQL, click on the Search
Binocular icon, click the
Advanced Search hyperlink,
enter text in the 'None of these
words' text box, they receive an
inappropriate error message
instead of of one that states that
searching on "None of these
words" alone is not supported.
12-1TAA6DT 12-1SZEIZE 8.1.1.1
ACR 452: Adds the following text
boxes for Siebel Search:
All these words
Any of these words
Exact Phrase
None of these words
12-1SX7AHU 12-1SX7AGD 8.1.1.1 Yes, see
Instructions for
ACR 439 on
page 95.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
646
When users log in to Call Center,
index the Solutions Business
Component, click the Binocular
(Search) icon, select Solutions in
the Lookin, click Go, and drill
down on any of the Solutions
records, they receive the
following error message: "We
the following reasons: The
selected search result cannot be
found.(SBL-SRH-00167)"
12-1SX7AF4 12-1SW7MFH 8.1.1.1
ACR 452: Exact Phrase search
does not work
12-
1SW7MBM
12-1SW7MAD 8.1.1.1
ACR 403: After a Business
Component has been indexed,
users are unable to drill down on
search results, and the Mobile
Web Client must be restarted
12-1SVPBQO 12-1SVPBOZ 8.1.1.1
ACR 452: Packages the
Search_Engine_Config.xml and
ACR452_Seed_Import.dat files
for the 8.1.1.1 Fix Pack
12-1STTMVR 12-1STTMUS 8.1.1.1
ACR 452: Searching on
filesystem records (Filesystem
connector configured through
Remote Administration) yields
no results
12-1SN2A27 12-1SINAGI 8.1.1.1
ACR452: SES Integration
uptake: Remote Administration
configuration
12-
1SMKDVD
12-1S0YCKL 8.1.1.1 Yes, see
Instructions for
ACR 452 on
page 100.
The application hangs when
users click the Advanced Search
link in the Search pane
12-1SJ62UA 12-1OUTTD2 8.1.1.1
After ACR 403 has been
installed, users are unable to
find the 'Admin-Mobile Search'
screen after running the dataimp
utility
12-1SJ62U0 12-1R4A0N4 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Within Call Center, when users
click the Binocular icon, enter
Search For = *credit OR A* and
click the Search/Go button, they
should receive either the "Left
truncated wild card query is not
supported by the search
engine.(SBL-SRH-00235)" or the
"Single letter followed by
Wildcard not supported" error
messages, but instead the
Search applet appears
12-1SLL019 12-1SLL00K 8.1.1.1
Improves the usability of the
'SBL-SRH-50049' error message
12-1SF7RL4 12-1SF7RJR 8.1.1.1
ACR 403: The
discon_symbstring.sif and
Disconnected.sif files are
missing from TOOLS\REPPATCH
12-1S78VAI 12-1QR8QLH 8.1.1.1
ACR 439: The ACR439.sif folder
is missing from Tools\REPPATCH
12-1S5T74H 12-1S5T73Q 8.1.1.1
Within the Server_Manager
prompt, Component Search
displays as unavailable
12-1S5B5AV 12-1S5B5AB 8.1.1.1
Resolves a problem where the
Save Search button does not
work (ACR 403)
12-1S1XV6F 12-1NK1UOB 8.1.1.1
Incremental Index Processor
gives error SBL-OMS-00203
when there are no records to
process
12-1RFD4GC 12-1ISHFB1 8.1.1.1
ACR 403: Users are not able to
search for date ranges from the
Advance Search page
12-1RBZCL1 12-1NCHNBI 8.1.1.1
Within the application (on the
Dedicated Client), when users
navigate to Administration -
Mobile Search > Search Index
Settings, select Solution (Call
Center) and click on Index, the
client crashes
12-1RBZC7U 12-1PZ4263 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
648
when users log into to the
application (Dedicated Client),
navigate to Administration -
Mobile Search > Search Index
Settings, and select Product and
then Index, they receive the
following error message: "An
error has occurred creating
business component '<?>' used
by business object '<?>'. Please
ask your systems administrator
to check your application
configuration.(SBL-DAT-00222)
.
12-1RBI96O 12-1PZ42BP 8.1.1.1
when users click Advanced
Search, search on invalid criteria
in Advanced Search and receive
No Results Found, search on the
same invalid criteria again, and
then click Search and click Select
All in basic search mode with
blank criteria, they receive the
No Results Found message
instead of the results from the
blank search
12-1RBI94M 12-1PZ42F9 8.1.1.1
using the Index All function
throws the "Unable to load
message 0x1(SBL-GEN-00001)
error message
12-1RBI93M 12-1PZ42NW 8.1.1.1
Searching on SR Attachments
does not work correctly
12-1RBI92C 12-1PX52N2 8.1.1.1
The seed_disconn files are not
created after the ACR 403 patch
for JPN has been applied
12-1RBI919 12-1Q06HNN 8.1.1.1
Refreshing Indexing Search
Objects for Oracle SES crashes
the Object Manager.
12-1QH55SI 12-1Q0IVZ5 8.1.1.1
Security
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Include Mainwin 5.0.4 patch to
enable certificates to work on
Unix
12-1T03XZ8 12-1SK50OF 8.1.1.1
Port ACR329 Support of Security
Certificates in Mainwin
12-1ROFZHA 12-1RDWN1J 8.1.1.1
The AUTOCOMPLETE attribute is
not disabled in the HTML FORM/
INPUT element that contains
password-type input like the
password field in the login page,
so passwords can be store in
browsers and retrieved
12-1R1VGML 12-1PX49PY 8.1.1.1
Corrects a cross-site scripting
(XSS) vulnerability found with
default drilldown fields in the
high-interactivity application
12-1R1VGM2 12-1LEFWYP 8.1.1.1
LDAP Security adapter crashes
when used with Global Catalog
parameters
12-1QYIC79 12-1PE9R2X 8.1.1.1
Security Certificates with key
size larger than 4096 bits fail on
Unix
12-1Q35S5Q 12-1P56BSF 8.1.1.1
Mainwin fails to verify valid
intermediate certificates
12-1PI44YE 12-1PCDHM6 8.1.1.1
Within Admin - Server
Configuration, when users click
Server, query for Loyalty Object
Manager (ENU) on the
Components applet, select all of
the logs, and change the log
level to 5, save the change, and
navigate to the Enterprise, view,
they receive the following error
message: We detected an Error
which may have occurred for one
or more of the following reasons:
SBL-ADM-02049: There is no
connected server targeted for
that command.
12-1TB8XS8 12-1TB8XQI 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
650
Connection requests disappear
between SCBroker and the
Object Manager
12-1SN6XG9 12-1QXJEX5 8.1.1.1
A SRProc crash/timeout occurs
on server startup, and jobs
remain in the Queued state
12-1RAJ7XO 12-1QTP7FD 8.1.1.1
Addresses a memory leak
related to Siebel Self-Service
Applications
12-1R759QW 12-1R759QB 8.1.1.1
Customappobjmgr tasks are
timing out and sessions are not
closed
12-1R4AO4X 12-1R4AO4B 8.1.1.1
The garbage collector crashes
during logoff when CTI is
enabled
12-1P4OFB1 12-1OVC1X9 8.1.1.1
Task UI
Pausing a task-based UI task
may result in the following error
messages: [1] An error has
occurred while restoring task
instance '<task instance
id>'.(SBL-BPR-00536) [2] The
workflow/task engine
encountered an internal
error.(SBL-BPR-00232)
12-1R3BC6V 12-1Q5L8AP 8.1.1.1
Manually populating certain
columns in the Siebel S_PARTY
table may prevent some paused
Task UI items from appearing in
the Inbox
12-1QODIO5 12-1OH2I5T 8.1.1.1
Tools / Configuration
Using the Edit Web Layout menu
command in Siebel Tools causes
Siebel Tools to exit
12-1U57ONN 12-1TYAW7D 8.1.1.1
Siebel Tools crashes while
compiling Siebel 8.0.0.5 QF0593
12-1TK99PA 12-1THNFAT 8.1.1.1
With the ST Engine turned on,
the "with" statement does not
behave as expected
12-1QY0ZK6 12-1OJJKWB 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
When script in an applet uses the
this.InvokeMethod("WriteRecord
") syntax and an error occurs,
the event name displays instead
of an error message
12-1QQAF3Y 12-1QBCBPP 8.1.1.1
The SetProperty control method
with the Visible property can
only hide a control, regardless of
whether or not the value is True
or False
12-1QDRNTS 12-1PT56EL 8.1.1.1
During LMU import, Siebel Tools
stops and displays an error
message, and the user has to
click OK to terminate the
instance that is running
12-1Q4577F 12-1PPRMZF 8.1.1.1
Users experience problems when
running multiple sessions of
Siebel Tools on the same
machine while running LMU
imports
12-1Q4576Z 12-1PPRMYV 8.1.1.1
Code in PreInvokeMethod and in
Declarations of Browser Script
causes popup applets not to
open
12-1N1KM7F 12-1KDK35I 8.1.1.1
Upgrade
The datachk - Codepage tool
cannot handle multiple
repositories
12-1RA1UL7 12-1RA1UJN 8.1.1.1
When users run an upgrade
using the job0.txt and
siebin01.jcl files, during additive
changes application to the
target, the existing rows in the
log table are deleted and only
rebuild log entries are there
12-1RAKHWJ 12-1Q355KL 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
652
Upgrading from Siebel 8.1.1 SEA
to Siebel 8.1.1 SIA fails with the
[DataDirect][ODBC Oracle
driver][Oracle]ORA-02296:
cannot enable (ORA17120.) -
null values found
12-1QRRBVH 12-1QT8DS1 8.1.1.1
Web Framework
Client-side logging does not
perform correctly
12-1Q3N50U 12-HPOMO0 8.1.1.1
Workflow
Upgrading or editing worflow
processes resets properties for
other steps in the process
12-1TYBITJ 12-1PILZD3 8.1.1.1
When workflow calls a sub-
process workflow which includes
an Siebel operation to set field
values, an error is encountered
12-1S9RQQJ 12-1P56A6N 8.1.1.1
When a subtask is called from a
main task, the application
crashes
12-1S3DS71 12-1NQOD87 8.1.1.1
Workflow processes based on
runtime events may not pick up
lists of values
12-1RF7CDZ 12-1PE9QNX 8.1.1.1
Life Sciences
Activity
When users try capture
signatures more than once in a
particular session, the
application crashes
12-1T9SI6C 12-1T9SI5L 8.1.1.1
Users are unable to multi-select
and add multiple attendees to a
meeting
12-1OBLK4C 12-1NQ7LNP 8.1.1.1
Data Migration
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Incorrect transaction status is
displayed in the sender's "Sent
Samples" view for records that
were migrated from previous
Siebel Life Sciences application
releases
12-1R75OVY 12-1Q72AR6 8.1.1.1
Duplicate records display in the
Sample pick applet when users
try to add line items for in-
progress transactions from
Siebel Life Science application
versions prior to version 8.1.1
12-
1R75OUW
12-1Q72APO 8.1.1.1
The system displays an error
message when users try to
adjust processed transactions
from previous Siebel Life Science
application releases
12-1R75OTU 12-1Q72AO5 8.1.1.1
An error message displays when
users try to acknowledge "In
Transit" transactions in Samples
> Received Samples
12-1R75OSS 12-1Q72AMN 8.1.1.1
Shipped Quantity information for
the "Processed with
Discrepancies" records in the
Received Samples does not show
up correctly
12-1R75ORL 12-1Q72AL7 8.1.1.1
Transactions for "Processed with
Discrepancies" records do not
update to Processed status
12-1R75OQK 12-1Q72AJR 8.1.1.1
When transactions are adjusted
within Siebel Life Sciences
applications prior to version
8.1.1, post-migration, the
adjusted transaction records do
not show up in the Original Line
Items applet
12-1R75OPJ 12-1Q72AJ1 8.1.1.1
Other
Adds all of the 8.1.1 views to the
sia_options.txt file
12-1TENX5R 12-1TENX4H 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
654
Users are unable to save
campaign responses in the
Contact Call Detail view
12-1SJO29Z 12-1I3ER4T 8.1.1.1 Yes, see
Instructions for
FR 12-1SJO29Z
on page 773.
The Data Migration service
returns an error when executed
from a workflow
12-1R75OOH 12-1Q25Q6M 8.1.1.1 Yes, see
Instructions for
FR 12-1R75OOH
on page 774.
Samples
Within the Pharma application
Contacts > My Contacts view,
the Sample Dropped and
Requested applets should be
read-only and have their Add
buttons disabled when invalid
data is entered
12-1TS6L62 12-1TS6L3P 8.1.1.1
No records display for Samples,
Promotion Items, or Product
Details within the Sample
Management > Allocations and
Call Activities > Product Focus
screens
12-1R75OZ4 12-1Q8JEWD 8.1.1.1
Users are able to drop controlled
substances to an SRE exception
contact type for a state
12-1R75OY2 12-1Q7IP1X 8.1.1.1
Samples for Handheld
Inbox items are not created for
sample transactions that have
Disbursement Adjustment as the
type
12-1R75P18 12-1QAH3KW 8.1.1.1
Loyalty
Loyalty Customer
Portal
Updates Siebel Loyalty error
messages to provide more
detailed information about the
errors
12-1QYIA05 12-1QDFKTJ 8.1.1.1
Loyalty Engine
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
If accrual transactions with
expired points are canceled, the
point balance goes negative
12-1U5SIWR 12-1U5SIW7 8.1.1.1
When a member has a negative
balance, when a member
redemption transaction is
cancelled, the point balance is
not updated correctly
12-1TUEX0T 12-1Q5L7UL 8.1.1.1
Within the Loyalty Member
screen, when users query for a
member under Member Name,
drill down on the name to the
Statement view, select a
statement, and click the
Generate Document tab, they
receive error messages stating
that they are not connected to a
valid file server
12-
1TDOGWU
12-1TDOGV5 8.1.1.1
Accrual cancellation leads to
used points having values
greater than their accrued value
12-1T9RYZS 12-1T9RYZ1 8.1.1.1
When users attempt to merge
two members in a Redemption/
Accrual Cancellation Transaction,
12-1T7D8JJ 12-1T7D8HQ 8.1.1.1 Yes, see
Instructions for
FR 12-1T7D8JJ
on page 774.
Redemption Cancelation
Transactions with vouchers are
rejected in both the Transaction
UI and the Task UI
12-1T7D8HE 12-1T7D8F3 8.1.1.1
Improves the quality of Loyalty
application error messages
12-1T6VXJE 12-1T6VXHT 8.1.1.1
When users create a member,
navigate to Tier, and click
Process Tier Change, the
member is not promoted to a
new tier
12-1T6DMP5 12-1T6DMOL 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
656
Within the Loyalty application,
when users navigate to Loyalty
Members, select a member with
points, click the Task bar to
select Member Services, click
Gift Points, enter Points =
Regular, Gift To = (Customer
Name), award points, and click
Next, they receive the following
error message: Error invoking
service 'LOY Member Services',
method
'SimulateServicesPromotions' at
step
'SimulateServicesPromotions'.(S
BL-BPR-00162)
12-1SJ5HRQ 12-1SJ5HQ6 8.1.1.1
Redemption cancellation overide
points functionality should not
redeem extra points
12-1S5BJ6K 12-1S5BJ59 8.1.1.1 Yes, see
Instructions for
FR 12-1S5BJ6K
on page 769.
The Loyalty Batch Engine
processes objects twice
12-1R84WIL 12-1R8LQY9 8.1.1.1
Improves the overall
performance of Batch Tier
processing
12-1R7NHCI 12-1QUO2ZN 8.1.1.1 Yes, see
Instructions for
FR 12-1R7NHCI
on page 774,
Duplicate tier processing occurs
on the Linux platform
12-
1R0WC2Q
12-1QK0TP5 8.1.1.1
When users configure a simple
frequency promotion and click
the Process button, they receive
Error invoking service 'LOY
Processing Engine', method
'SubmitObjectForProcessing' at
step
'InvokeSubmitObject':(SBL-
BPR-00162)
12-
1R0WC2D
12-1QU76SD 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
When a user has not performed
Gift Points Limit setup tasks,
when the user selects a member
and updates the Gift Points
information, when they click
Next, they receive an error
message related to invoking the
LOY Member Services method
instead of an error message
related to Gift Points setup not
having been performed
12-1QYI9WX 12-1Q3NKNZ 8.1.1.1
Loyalty Batch Engine processes
records twice
12-1QXAZCF 12-1P2S23P 8.1.1.1
There is a discrepancy between
the point expiration date and
accrual cancellation process
12-1QK1D4H 12-1P18LL9 8.1.1.1
Loyalty Manager
If accrued points have already
been consumed, the transaction
cancellation should take the next
available accrual points
12-1RVNZS9 12-1RVNZQZ 8.1.1.1
Provides a Web service to serve
as a wrapper for Accrual
simulation calls
12-
1R0WV7D
12-1PV3QSH 8.1.1.1
Auto creation of point blocks for
prepaid partners is not working
12-1QYI9WB 12-1Q3NIC7 8.1.1.1 Yes, see
Instructions for
FR 12-1QYI9WB
on page 765.
Provides RTF template changes
to fix an issue where Voucher
Statements (VoucherIssue,
Cancellation) are not displaying
Issue Date and Expiration Date
fields correctly
12-1QYI9VW 12-1Q5L30R 8.1.1.1 Yes, see
Instructions for
FR 12-1QYI9VW
on page 765.
An error message displays
whenever the Raise Dispute
functionality is invoked for a
transaction
12-1QYI9U5 12-1Q71LSD 8.1.1.1
Language transalation issue and
requires code fix
12-1QYI9TU 12-1Q7IR96 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
658
Marketing
Campaigns
When upgrading from Siebel
application versions prior to
8.1.1 to Siebel 8.1.1 the
segment trees that are more
than one level deep with splits
are distorted
12-1S2FFRD 12-1S2FFQT 8.1.1.1 Yes, see
Instructions for
FR 12-1S2FFRD
on page 769.
Changing a node on a segment
tree clears all of the allocation
information
12-1QNF55C 12-1OD2S71 8.1.1.1 Yes, see
Instructions for
FR 12-1QNF55C
on page 765.
Campaign Allocation applet does
not show correct counts when
segments are changed and
Refresh Tree is used
12-1QAH5RH 12-1PV3ANX 8.1.1.1
"Token Number" is corrupted
when "Allow Repeated Contacts
Within Load" is checked
12-1ORVNY9 12-1O2HRQ9 8.1.1.1
Email and Web
Marketing
Batch triggers do not pass the
correct set of customer IDs as
segmentation prompts
12-1TYBKSS 12-1TYBKRT 8.1.1.1
Responses are not being
generated for automatic
trackable URLs
12-1TXC0I6 12-1TXC0GS 8.1.1.1
URL detector replaces image
source paths for all of the
graphics in the body of an email,
so the graphics are broken when
users save
12-1TVEKTK 12-1TVEKS3 8.1.1.1
HTML Editor incorrectly appends
HTTP prefix to links
12-1T30JMR 12-1NP9FJ9 8.1.1.1
Response loading uses only the
first name to determine if the
contact exists
12-1RNH75K 12-1NWCQ7S 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
When users create a campaign
and associate a segment tree to
the campaign that has multiple
nodes (second-level), when the
tree is expanded, it has a
remainder that is split and does
not display properly in the tree
12-1RBI8H4 12-1R75VHI 8.1.1.1
When users create an offer and
an email treatment, create a
campaign, attach the offer and
email treatment to the
campaign, and click Test
Treatment, they receive an error
message
12-
1QVMOSS
12-1QNF5R9 8.1.1.1
Provides a mechanism to
autogenerate Form HTML that
can be embedded in custom
pages
12-
1QODWTG
12-1M6V1A0 8.1.1.1
Not all URLs appear in the Verify
and Preview window
12-1QNF521 12-1P0SCHD 8.1.1.1
URLs are not automatically
trackable
12-
1NQOGCK
12-1NQ7TYV 8.1.1.1
Survey responses are not linked
to campaigns
12-1NQP3ON 12-1NLY66Z 8.1.1.1
Events
Confirm Registration fails when
contacts were added to events
through campaign load
12-
1NGQSNW
12-1NC0KKJ 8.1.1.1
Marketing Server
Waves are assigned a single
record if the first wave setting
has 0% allocation
12-1QY0YIW 12-1P81NNZ 8.1.1.1
When contact planning rules are
defined for treatment channels,
mutual exclusion cannot be
guaranteed completely
12-1QNF549 12-1OD2S8L 8.1.1.1 Yes, see
Instructions for
FR 12-1QNF549
on page 774.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
660
SOAP arguments must be
configured when using
Campaign Load to external
tables
12-
1QMX8WH
12-1K3ZEIQ 8.1.1.1
Campaign Launch does not
attempt to generate a list file
when there are zero contacts in
a Wave
12-1QMXRDI 12-1K3ZEFN 8.1.1.1
Campaign Load does not update
Load Count when loading
external tables
12-1QMXR8X 12-1K1EYLP 8.1.1.1
The Date Scheduled field for
Campaign Wave does not
populate when a future date is
selected
12-
1QNEGM0
12-1H8HPIW 8.1.1.1
Other
When users create an import
job, activate it, and then click
the Deactivate button while
processing is occurring, they
message: The selected record
has been modified by another
user since it was retrieved.
Please continue.(SBL-DAT-
00523)
12-1R84VR3 12-1R7N6Z2 8.1.1.1
When no Prospect ID is passed in
the input field, Lead Update fails
with the following error
message: 'No user key can be
used for the Integration
Component instance 'List Mgmt
Prospective Contact
12-1R7N6XZ 12-1R7N6O0 8.1.1.1
During lead import, while trying
to add the Lead Partner field, the
following error message is
thrown: "No definition found for
the field 'Lead Partner' in the
business component 'Lead
12-1QZXLZJ 12-1QZXLY0 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Data mapping is not performed
properly, and imports with xml
input error out with the following
EAI error message: 'First Name'
is a required field. Please enter a
value for the field.
12-1QZXLWZ 12-1QZXLVJ 8.1.1.1
When list import is performed
with a prospect ID that does not
exist, a new prospect is created
12-1QY0ZJ0 12-1NMF0K5 8.1.1.1
Event Trigger Execution results
in huge memory consumption for
Workflow Process Manager
12-
1QWLCO2
12-1QWLCMH 8.1.1.1
Programs
When users create a campaign
and associate segment, drag and
drop the Wait shape, attach a
constrained connector to the
campaign and then attempt to
attach the other end to the Wait
shape, they receive the following
error message: "Field 'Next
Stage Connector' does not exist
in definition for business
component 'Program Flowchart
Next Camp Connector'
12-1S99AJC 12-1S99AIB 8.1.1.1
Within the Marketing application,
when users create a program,
add shapes, navigate to the
Program list, drill down on a
program name, log out, log back
in again, navigate to the
Programs screen, and drill down
on a program name again, the
system logs the user out
12-1RA4BEH 12-1OA5PY7 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
662
When users create a program
flow, drag a stage, drag a wait
step, drag a connector to
connect a stage to the wait step,
select the connector arrow,
select Edit > Add Point from the
right-click menu, leave the
screen and then return, the edit
point is gone
12-1QNF56F 12-1OA5UMP 8.1.1.1
Mobile Solutions
Siebel application does not
install on WM 6.1.4 devices, and
stating that there are not
sufficient system permissions
12-1SW7Q25 12-1SREMMN 8.1.1.1
Applying the Siebel Anywhere
SRF upgrade kit causes
Handheld three-way sync to
hang
12-1P2RFO0 12-1P2RFND 8.1.1.1
When a database is extracted
with the BCP file type, scripts
containing "\n" are wrongly
imported on the local database
12-1QYI7IR 12-1IZLKDL 8.1.1.1
Other
Wireless
When users create line items
within sales orders, duplicate
records are added
12-1Q06NX7 12-1JJHDHH 8.1.1.1
Partner
Relationship
Management
Other
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Users receive error messags
when they try to qualify a
prospective partner in the
Administrator Partner screen
12-1SJNT7T 12-1SEQDDV 8.1.1.1
Partner Manager
Expertise values are removed
after a prospective partner is
qualified
12-1RAJ7UZ 12-1QZYA3H 8.1.1.1
Partner Portal
Within the PRM Manager
application, when users click
Shopping Cart, they receive the
following error message: We
the following reasons:
Unterminated value for attribute
''in XML tag''(SBL-UIF)
12-1S8QDC7 12-1S8QDAZ 8.1.1.1
When users click the Shopping
Cart icon, empty the shopping
cart, drill down on a
recommended item, click the
Add Item button to reach the
New Cart applet, click the My
Customer button to reach the
Customer Selection applet,
select a customer, change the
price list, and click Next, the
user is not navigated to the
Transfer Cart view
12-1RIPG3X 12-1RIPG2H 8.1.1.1
When a cart is transferred, the
value of the price list remains as
the master price list rather than
changing to the price list of the
account to which the cart was
transferred
12-1RIPG1L 12-1RIPG01 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
664
When users attempt to transfer
the Shopping Cart (through the
Partner Portal), the following
error message appears: "Error
running sub-process 'Transfer
Cart Outbound Request Process'
at step 'Transfer Shopping
12-1R8LV71 12-1L0FANB 8.1.1.1
Public Sector
Case Management
Under the Verification Items list
applet, when users verify one
item and leave another one as
unverified, they are not allowed
to change Case Sub-Status
under the HLS Case Form applet
but they are allowed to change
Sub-Status from Edit Application
Menu-Change
12-1QRQ64V 12-1PLGBAO 8.1.1.1
Session warning error messages
occur when users try to submit a
benefit case for approval
12-1QCBH4O 12-1QCBH37 8.1.1.1
Other
Creates a source code .jar file 12-1TXC3HB 12-1T30JOF 8.1.1.1
Within the Public Sector Self-
Service application Support >
Knowledge Base view, Search
12-1RNDGN5 12-1RGOB9N 8.1.1.1
Sales
Forecasting
On the Forecast Details tab, the
AutoAdjust functionality is
greyed out on for the eleventh
record onwards while using the
single arrow on the vertical scroll
bar
12-1SCRNIJ 12-1S87JC1 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Internet Explorer 7 crashes if the
CTRL-S or Save Record functions
are invoked when the focus on is
a new field/column created in
the Forecast list applet after the
field value has been populated
using a picklist
12-1S1Y0WJ 12-1QMWX5R 8.1.1.1
On viewing subordinates'
submitted forecasts from the My
Teams forecast view, managers
cannot see data aggregated by
defined aggregation levels
12-1REV2P1 12-1PLH0DT 8.1.1.1
Adjustment of subordinate
forecasts (summary) with
percentages is not possible when
aggregation has been added
12-1Q626J5 12-1PE9QN3 8.1.1.1
Opportunities
When users use the scroll bar to
navigate to records within
Opportunity Record, data is not
saved in Revenue Line Items
12-1REV098 12-1QMFJR1 8.1.1.1
Service
Other
The Action business component
is hard coded to set the status of
an activity to Done when the
Done flag is checked or set to
True
12-1RBZC49 12-JX5I6Z 8.1.1.1 Yes, see
Instructions for
FR 12-1RBZC49
on page 776.
Within the FRA Call Center
application, when users navigate
to the My Service Request view,
select a record in the Service
Request List Applet, select Edit
menu > Change Record, select
field Owner on the popup
applet, and enter an invalid
value in the value, they receive
Unable to load message
12-1QV5YIV 12-1PLGZZ3 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
666
Dates in Activity Plans are not
being updated when the date is
edited
12-1QTPTZT 12-1H6LL9V 8.1.1.1
Within Field Service, the
isHoliday Business Service does
not return the correct outputs
12-
1QQ9WWM
12-19VLZT3 8.1.1.1
When users create an address
with a recipient and mark the
address as primary, log out, log
back in, add an item to the
shopping cart, check out, and
then change the contact address
on the shipping details page, the
address containing the recipient
is displayed without the recipient
name
12-1QDRS0L 12-1POB949 8.1.1.1
Scheduling
GetElapsedBusinessTime API
returns an incorrect result when
there are multiple time zone
entries
12-
1Q2NN4M
12-1DR0EUR 8.1.1.1
Siebel E-
Commerce
Assets
Shipping and tax amounts are
not included in the Open Order
Total field
12-1SW8FCN 12-1SW8FBB 8.1.1.1
On the Asset Details page for
Individual Accounts, the Bill To
Address field is not populated
correctly
12-1QDSJ0J 12-1NVVGDB 8.1.1.1
Browse and Select
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Within the Catalog page, when
users navigate to Computer &
Office > Computers & Add-Ons >
Computer Software, provide a
price range in the Narrow By bin,
and click Go, they receive the
following error message: "No
items found. To expand your
search, please remove filters in
the Expand By panel."
12-1T03IPL 12-1SXP6NF 8.1.1.1 Yes, see
Instructions for
FR 12-1T03IPL
on page 777.
Configurator
With a large number of users
running the application
concurrently, users receive an
error message when they try to
configure the product
12-
1ROWYK3
12-1RNY6ZZ 8.1.1.1
concurrently, when users add
products to a car, configure
products, return to promotions,
or try to submit orders, they
message:
#{ConfigHandler.performAction
}:javax.el.Eval
12-1R3AUZS 12-1R1EKMX 8.1.1.1
When users log in as B2B users,
navigate to the Order Status
page, browser for an order that
has two CP products, select Copy
to Cart, and select the
Reconfigure link for the product,
on the Configure page, the
previous options should be
selected, but instead a a warning
message displays that says that
subobjects of CP were removed
12-1QKI5Z0 12-1QH5LF3 8.1.1.1
Provides a more useful error
message for minimum
cardinality violation errors
12-1QGO85X 12-1QGO85B 8.1.1.1
Miscellaneous
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
668
Self-Service Applications: Users
receive an error message when
they try to compile the
ErrorPageDirector.jsp file
12-1T3ZEBN 12-1T3ZEAB 8.1.1.1
Within the E-Commerce
application, the session times
out
12-1QDRWVI 12-1PBEJY2 8.1.1.1
Shopping Cart and
Checkout
The line-level Ship To account is
not updated when user selects
the Bill To and Sold To account
12-1TD34QN 12-1TD34PB 8.1.1.1
At checkout, on the Shipping and
Billing page, the session may
hang and then time out
12-
1QDSO0O
12-1L3YXAQ 8.1.1.1
When users navigate to My
Account > Modify Service, drill
down on Asset #, click Next,
click Next in the Modify Due Date
page, choose the Upgrade/
Downgrade Promotion option,
select a different promotion from
Available Promotions, click Next,
configure the promotion, add it
to the Shopping Cart, click Next
in the Summary of Changes
page, click Next in the Shipping
page, and then click Logout on
the Billing pabe, the "page
cannot be found" error message
occurs
12-
1QDSKCD
12-1MQC54B 8.1.1.1
When a user creates a Shopping
Cart, saves it, and then later
deletes the chosen Address or
Payment Profile from the
Address Book or Payment Wallet,
when the user reopens the
original Shopping Cart and tries
to place the order, the order may
fail
12-1QDRVIG 12-1PEQUVR 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
The application can fail if the
Cart line amount exceeds
9,999,999.99 in the local
currency
12-1QDRIUP 12-1Q62WPC 8.1.1.1
Siebel E-
Commerce for
Comms
Assets
Within the Self-Service
application, Contact and Address
information is not refreshed
according to the account
selected in the Shipping Details
page
12-1SSD2GO 12-1SSD2F8 8.1.1.1
Users cannot add promotions to
ABO-Shopping cart with default
selected products
12-1S87JBI 12-1S87JA7 8.1.1.1
The Address Line 2 field for the
Bill To address of a secondary
user is incorrectly displayed as
the Address Line 2 field of the
parent record's Primary address
12-1QFOVBV 12-1QFOVAJ 8.1.1.1
When users navigate to My
Products > Assets > Asset
Details, verify that the products
are displayed in the respective
bins, select a product from one
of the bins and click the Add to
Compare button, the page
refreshes and there is no
message stating that the
products have been added to the
Compare Bin, and the Compare
Bin page does not display
12-1QDS1DK 12-1P2RG2P 8.1.1.1
Browse and Select
Users cannot add a promotion to
the shopping cart if they select a
Customizable Product without
having configured it first
12-1SMKT33 12-1SMKT1I 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
670
Expand By Price does not display
the correct results
12-1QDSJKB 12-1NSG9IG 8.1.1.1
Configurator
A memory leak occurs 12-1SEPN3K 12-1SEPN2D 8.1.1.1
Miscellaneous
Provides a source code jar file to
allow for overwrites
12-1SXPC2R 12-1SXPC27 8.1.1.1
A memory leak occurs when
calling the "PSTOIntObjHier"
method of EAI Integration
Object to XML Hierarchy
Converter
"12-
1TXBUGN
12-1TXBUEZ 8.1.1.1
The build XML does not include
the "createsourcearchive" target
12-1T5Q38F 12-1T5Q375 8.1.1.1
With a large number of users and
both Product Promotion and
Customizable Product scenarios,
the application crashes
12-1STSZ9X 12-1STSZ9B 8.1.1.1
Within My Accounts > Modify
Service, when users drill down
on an asset with a promotion,
click Next in the Asset Details
page, select Modify My Existing
Promotion, click Next, click Next
in the Modify Due Date page,
make changes to the
information, click Next in the
Summary of Changes page,
select the default values, click
the Next button in Modify
Shipping, Billing and Subscribers
page, and navigate to the
Review and Submit page, the
Submit button is disabled and an
error message displays
12-1QJ20GR 12-1QJ20FH 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Within Packages > Configurable
Promotions, when users drill
down on the Millenium Max 500
Packages field, the "Make Your
Selection" option does not
appear
12-1QDSK6D 12-1MV7OIM 8.1.1.1
When users navigate to the My
Accounts screen, click on the
Update Payment Method on a
Service link to navigate to the
Asset List screen, drill down on
an asset number to navigate to
the Asset Detail screen, click
Next to navigate to the Modify
Asset screen, the default billing
profile is selected in the LOV, but
when users click the Show Less/
Show More button, the default
billing profile is no longer
selected
12-1NA4XY1 12-1MGRVT8 8.1.1.1
New Service
In new service activation (CP)
scenario, within the Products
page, the Gallery view should
display but the List view displays
instead
12-1QJ2KKN 12-1QJ2KJA 8.1.1.1
if they add a large number of
products to the shopping cart
(over ten products) and then
perform a new service activation
12-1QDRT9N 12-1PLH7MB 8.1.1.1
Order Status
When users upgrade from one
promotion to another, the data in
the order is incorrect
12-1REVTLR 12-1REVTL7 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
672
When users navigate to Order
Status, select an order, navigate
to the Shipment Details tab,
select the individual account in
the Accounts drop-down list,
click on Search to navigate to
the Orders page wtih the
matching records, select a status
for which there are no orders
from the Order Status drop-
down list, and click Search, a
null pointer exception occurs
12-1QKIA6G 12-1QKIA53 8.1.1.1
Within the Review and Submit
page, the Submit button is
disabled for aggregate
promotions that have
commitments when the user has
made changes that affect the
original terms or commitment
12-1QJ2EH3 12-1QJ2EG6 8.1.1.1
Shopping Cart and
Checkout
When users navigate to Products
> Browse, add a few products to
the shopping car, click the Check
Out button, click Add New Profile
on the Shipping and Billing
Details page and set this profile
to Primary, and query for the
new profile in the
eCommunications application,
when they navigate to Profiles >
Billing Profiles, the new billing
profile does not have the Primary
check box selected
12-1TGNL80 12-1TGNL6P 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
When users log in, add a few
products to the Shopping Cart,
click the Check Out button, keep
the defaults in the Shipping
Details page, click the Next
button, change the account
name in the Billing Details page,
click the Back button, click the
Cancel button in the Shipping
Details page, and then click the
Check Out button in Shopping
Cart, the changes that were
made to the Shipping Details and
Billing Details pages are retained
even though they were not
saved
12-1T7V47Y 12-1T7V46N 8.1.1.1
Provides the web.xml file to
synchronize the SIA application
to be consistent with the SEA
application
12-1QT7T1P 12-1QT7T15 8.1.1.1
Within Service screen > Forms
> View Forms list applet, when
users click on the Form # column
to sort, the columns are no
longer visible
12-1QRQ65Y 12-1PYMH5M 8.1.1.1
When users add products to the
shopping cart, click on Check
Out, select the default
information in the Shipping
Details page, click Next, change
the billing account and profile for
the line item in the Billing Details
details page, click Cancel, check
out again, and click the View link
in the Bill To field for the line
item in the Review and Place
Order page, they receive an
error message
12-1SQXAVL 12-1SQXAQE 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
674
When users add products to the
shopping cart, click Check Out,
update shipping information,
click Next, modify the billing
account in the the header in the
billing page, line items to change
the billing information of line
items to a different account
other than in the header, click
Save, cancel checkout, and
navigate back to the Billing
page, the billing account and
address of the line item that was
updated still have the billing
account and address from the
header
12-1SQXANV 12-1SQXAM3 8.1.1.1
When users log in as B2B user,
add an item, check out, click the
Add button on the Shipping
Details page to create a new
contact, enter all the mandatory
fields and click Save, the contact
is saved and is displayed on the
Contact field, but when users
select the newly-added contact,
a null pointer exception error
message displays: Error1.JBO-
29000: Unexpected exception
caught:
java.lang.NullPointerException,
msg=null
2.java.lang.NullPointerException
12-1SGOEOJ 12-1SGOENZ 8.1.1.1
When users select a site, add an
item to the shopping cart, check
out, and select check as the
payment method in the Billing
Details page, click Add New, and
then click Cancel on the dialog
box, the application hangs
12-1SD92ZF 12-1SD92YV 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
When a large number of users
are running the application
concurrently, the Submit button
is unavailable when users try to
place an order
12-1S7Q7ST 12-1R84CM9 8.1.1.1
Region Meta data information is
missing in the region-metadata-
telco.xml file, so there is no no
meta data information displayed
in the log files
12-1S1XT6D 12-1S1XT5T 8.1.1.1
When users click the Submit
button on the Order Review
page, the order is placed but the
user is not navigated to the
Order Confirmation page
12-
1ROWYNK
12-1ROWYMN 8.1.1.1
When users log in as a B2B user,
add any product, check out, add
a new contact for the logged-in
user's account in the Ship To
page, complete the checkouts,
submit the order, add another
product to the cart, check out,
and then navigate to the Bill To
page, the Bill To contact
displayed is the contact that was
added in the last order, but the
contact should be defaulted to
the logged-in user's contact
12-1QZY3ZN 12-1QZY3YD 8.1.1.1
When users add a product into
the shopping cart, click on Check
Out, do not change the primary
address information in the
header or at the line-item level
in the Billing and Shipping page,
and click the Next button to
reach the Terms and Conditions
page, the Bill To address is
empty in Review and Place Order
page
12-1QX1W5J 12-1QX1W4A 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
676
When users add an item to the
shopping cart, check out, select
Yes for Multiple Location on the
Shipping page, select a line,
change the shipping information,
click the Search icon for a
contact, click Cancel in the
Selected Contact dialog box, and
then try to change the account
from the Account drop-down list,
the application hangs
12-1QJJD51 12-1QJJD3P 8.1.1.1
On the Review and Place Order
page and Order Confirmation
page, the fields are displayed in
the following order: Ship To, Bill
To, and Sold To, but on the Order
Details page, the order of these
fields is reversed
12-1QJ1VD0 12-1PFQ9UO 8.1.1.1
When users log in as a B2C user,
navigate to My Products >
Assets > Asset List page, select
an asset that is an Editable
Promotion with two simple
products and a customizable
product, modify the asset, add
child products, submit the order,
navigate to the Order Details
page, the price $0 for the child
products that were not changed
(and deleted) when the asset
was modified are shown under
the One Time Price column
instead of the Unit Price column
12-1QFSBOF 12-1Q9ID59 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
When a user registers a new B2C
user, adds an item to the
shopping cart and places an
order, the Bill To Address field is
populated, but when users
navigate to My Accounts >
Personal > Address Book, add an
address and mark it as the
primary, add an item to the
shopping car, and check out, the
Bill To Address field is empty on
the Review and Place Order,
Order Confirmation and Order
Details pages
12-1QE9Z1F 12-1QE9Z0V 8.1.1.1
In the Shipping Details page,
when a user selects a line item
and clicks the Change Shipping
Information for the Line Item
button, changes the request
date for the line item and then
clicks Save, the request date of
line item changes to the request
date -1
12-1QE9TXJ 12-1QE9TW8 8.1.1.1
When users add a configurable
item to the shopping cart,
expand the product and see that
One Tme Unit Price displays so
that users can see the prices for
child products, checks out and
clicks Next in the Shipping,
Billing, and Sold To pages, on the
Order Review page, One time
Unit Price does not display
12-1QDSIK3 12-1N3LCM7 8.1.1.1
When users log in as a Child B2B
user, add an item to the cart,
check out, select a secondary
user of the Parent Company
Account in Ship To, Bill To and
Sold To Account, because the
secondary user does not have an
address, the address is
refreshed to the primary account
address of the child account
12-1QDS136 12-1P562C5 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
678
When users log in as the B2B
primary user, navigate to the
Browse Products page, add a
product to the shopping cart,
click Check Out on the shopping
cart bin, click the Contact LOV
within the Shipping Details page,
wait for the session to time out,
and then click Select, the
application hangs
12-
1QDRWTF
12-1PCCTSH 8.1.1.1
Requested dates entered during
Asset Based Order checkout flow
are updated as the requested
date +1 in orders
12-1QBC634 12-1QBC61Q 8.1.1.1
Users cannot add products to the
Summary of Changes page
12-1QCSND4 12-1Q5L6DJ 8.1.1.1
navigate to the Products page,
add a product to the cart, click
the Check Out button in the
shopping cart bin, select Yes for
multiple locations on the
Shipping Details page, select a
line item and click on the Change
Line Shipping Information
button within the Order Lines
section to display the Change
Line Shipping Information dialog
box, and wait for the session to
time out, they receive a "This
page cannot be displayed" error
message
12-1PBY7W6 12-1PBY7UV 8.1.1.1
User Accounts
For a secondary B2B user, the
Add New button is disabled for
Account Address in the Shipping
Details page
12-1QDRH42 12-1Q9ICDR 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Within My Accounts > Company,
with one contact already existing
in the contacts list, when users
click on the Contacts tab under
MyAccounts > Company, and
click Edit, the Account
Assignment table is empty and
does not list the company
account and the user's individual
account
12-1QC7G4J 12-1QAY5O2 8.1.1.1
When a user completes
registration from the Check Out
page, the user is not directed
back to the Check Out page after
they have completed registration
12-1PZOA1P 12-1PZOA15 8.1.1.1
Siebel Email
Response
General
On Linux, within Siebel Email
Response, when users navigate
to any contact with valid email
id, select F9 to send an email,
draft text in the Send Email
applet, and click Spell Check,
they receive an error message.
This same issue occurs within All
Communication when users use
F9 when replying to an outbound
email as well.
12-1TUF2T5 12-1PLJFC3 8.1.1.1
> Communication > All
Communication or Admin -
Business Process > Workflow
Deployment, select the list view,
keep the cursor on any record
other than the first record, and
click Query to perform a query, a
blank record is created
12-1T5X07W 12-1T5X06E 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
680
When users create a contact with
an account and appropriate
email address, send an inbound
email to the same contact, reply
from the Communications
screen, send the email, and
navigate back to the Contacts
screen, they receive an incorrect
error message
12-1T5X03L 12-1QL02QT 8.1.1.1
Provides workflows in XML form
instead of as SIFs
12-1T03SKH 12-1T03SI7 8.1.1.1
Activities with an Unscheduled
status are not handled
appropriately
12-1SC99OY 12-1SC99NH 8.1.1.1
After the exchange server has
been shut down, when users
send an email using F9, the
email is queued, but after the
retry expiration interval is
completed and the activity is set
to Cancelled status, when users
navigate to the All
Communications view and click
the Resend button for this
activity, a blank screen appears
and the email's status remains
In-Progress
12-1SC99ME 12-1SC99KJ 8.1.1.1
When users navigate to the All
Communication view, select any
"inbound email not started"
email, click Forward, enter text,
associate more than two
attachments, and then click the
Save as Draft button, the applet
goes blank and the Resume
button is disabled
12-1SC9947 12-1SC992E 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Within the All Communications
screen, when users select any
record and click Reply, add some
text, send the email, and then
navigate back to the same email
and forward it, the text from the
previous email is lost, and so are
any attachments
12-1S1XVA8 12-1ONDKS9 8.1.1.1
Within the Communications
screen, when users click the
Reply button on a record, and
then click the Back button in the
browser, a new record with "In
Progress" is created and drillling
down on the new record yields
the SBL-DAT-00215 error
message
12-
1RB07WG
12-1O5H0SV 8.1.1.1
When users navigate to All
Communications, reply to an
email, save it as a draft, click the
Back button to view the draft
email, they are allowed to
associate or remove a contact,
and they are also allowed to do
the same for a sent email, but
the OK button on the pick
contact applet should be
disabled for drafted or sent
emails
12-1RB07W2 12-1PIM03P 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
682
Within Administration >
Catalogs, when users query for
KB catalog, create new
categories in KB catalogs,
associate the Active status
response template in each
category, navigate to All
Communication, select any
inbound email and hit Reply,
select the Go to Browse view,
navigate to KB Catalog >
Categories > Templates, select
any template to be associated
and click the Add button, no
template is associated with the
reply email
12-1RB07VO 12-1Q0OYZB 8.1.1.1
When users send an inbound
email, reply to the email in the
All Communication view, save
the email as a draft using the
Save As Draft button, navigate
to All Communication, draft
some text in the body of the
email, and perform a query in
the inbound email applet so that
the query retrieves different
records, the email is not saved
as a draft
12-1RB07VA 12-1Q3MVV7 8.1.1.1
When the Remain on Same View
After Send (Cancel) user
preference is set, when users
send an inbound email, reply to
the email, draft some text in the
body of the email and save the
email as a draft, resume the
drafted email and associate a SR
to it, send the email, reply to the
email, navigate to the SR using
Go to SR, and then navigate
back to the email, the reference
to the reply email is lost and the
email that was saved as a draft is
not referenced
12-1RB07UW 12-1Q3MVVZ 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Siebel Smart Answer
After ACR 367 has been
installed, when users perform a
find operation on any BC in the
Search Applet, (such as
Accounts) ,and select "Smart
Answer" category in the Search
Center, the Search "Look In"
displays "Smart Answer" but the
searchable fields correspond to
the previously selected FIND
Object instead of searchable
fields specific to Smart Answer
12-1T7V3ZK 12-1T7V3YV 8.1.1.1
ACR 476: Rebases Siebel Email
Response support for
SmartAnswer support
12-1U0ACK7 12-1U0ACJH 8.1.1.1
Users are unable to close the
Search applet
12-1T7V430 12-1T7V3ZT 8.1.1.1
ACR 476: Reenables the Smart
Answer component with the new
NLP engine
12-1T7HMTB 12-1T5W64T 8.1.1.1
ACR 476: After the Smart
Answer enhancement has been
set up, when users send out an
inbound email when Enable
Smart Answer =True in
Response group input
arguments, and then check the
status of the inbound email, its
status is initially Auto
Responded, but then it is
automatically changed to Done,
which should not happen until
the agent clicks Done
12-1T0ANU0 12-1T0ANT9 8.1.1.1
Siebel E-Support
Miscellaneous
A memory leak occurs during
Order Management scenarios
12-1R1VRQO 12-1R1VRQ3 8.1.1.1
Service Request
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
684
After solution types have been
created in Call Center, indexed,
and then searched for, when
users invoke the Self-Service
application, navigate to Support
> KM pages, and click on FAQ
under the Popular Support
Information section, they
message: "No solution is found
based on your search criteria"
12-
1U5UKMD
12-1U0DU1B 8.1.1.1
concurrently, users are not
allowed to upload large (1MB)
attachments, and the "Failed To
Transmit Data to Network" error
message appears
12-1QYISGE 12-1QYISFT 8.1.1.1
Siebel Self Service
Common
Deployment and
Packaging
The 811SelfService.ear data-
source.xml file has an entry for
Siebel Host that causes the
following error message: JBO-
30003: The application pool
(oracle.apps.ss.base.model.secu
rity.SessionAMLocal) failed to
checkout an application module
12-1RAJ02I 12-1RAJ01X 8.1.1.1
Miscellaneous
Users cannot navigate to the E-
Support tab in the Self-Service
Public Sector application
12-1T30KEU 12-1T30KE9 8.1.1.1
When users log in, select a site,
navigate to Payment Wallet,
select a payment profile, click
Edit, and then click Delete,
mandatory field valdiation
occurs
12-1SF7TYY 12-1SF7TXN 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
navigate to the Order Status
page, wait untill the session
times out, and then expand/
collapse the See All Search
Options bin, the system hangs
and displays an hourglass
instead of navigating the user to
the login page
12-1QDS1YB 12-1OMWFZH 8.1.1.1
User Accounts
Within the My Account >
Company > Contacts page,
users cannot add new contacts
by clicking the Add button
12-1T6EAI0 12-1T6EAGP 8.1.1.1
After a B2C user registers, the
application takes them to the
login page and not to the
confirmation page
12-1SD8ZCT 12-1SD8ZC9 8.1.1.1
When users perform searches
from the My Account page, there
is a discrepancy between the
search results for the searches
performed from the Orders
screen and the searches
performed from the Service
Request screen, but the search
specifications should be the
same for both searches
12-1MBQKPK 12-1M4C4IF 8.1.1.1
User Management
When users log in as a B2B
primary user, login as b2b
primary user, navigate to
Products > Order Status page,
select an account within the
Search dialog box, click the
Contact Name LOV to display the
Contact dialog box, they receive
Mandatory view criteria field(s)
Account Id missing in ContactVO
12-
1QDRWP8
12-1PBY7ZX 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
686
Travel &
Transportation
Other
ACR 488: When users create
multiple quotes for multiple
properties, they receive an error
message
12-1T5W51N 12-1T5W513 8.1.1.1
ACR 488: Prices added to menu
items are not preceded by $
signs until the record is saved
12-1T6DN88 12-1T6DN7O 8.1.1.1
ACR 488: When a Ctrl+B is done
on a locked record, the copied
record is also locked
12-1TENC2Y 12-1TDNULC 8.1.1.1
ACR 488: The Fixed Menu
Quantity field can be updated
even when it is listed under
Fixed Package
12-1TK4121 12-1TK411F 8.1.1.1
After the Event Template has
been applied to an opportunity,
the opportunity's name does not
appear in the Histories view
12-1TXC565 12-1TXC55L 8.1.1.1
Within Opportunities,
subfunctions and their
corresponding line items are not
reflected at the quote level
12-1U09B2J 12-1U09B19 8.1.1.1
When users check for copy
functionality when an arrival
date is less than the quote
arrival date, Internet Explorer
crashes
12-1U0BTMT 12-1U0B1E3 8.1.1.1
The administrator does not have
Edit Delete rights on the records
created by other users
12-1TXTI9W 12-1TXTI8S 8.1.1.1
System-generated records are
not read-only when viewed in
the Histories view
12-1TXC5DA 12-1TXC5B2 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Within Histories view > Quotes
applet, the Status field is not
read-only
12-1TXC57S 12-1TXC56O 8.1.1.1
When users try to copy a
function with an error number,
12-1TXC4ZH 12-1TXC4YX 8.1.1.1
ACR 450: Within Function Space
Diary, verifying line item
attributes fails
12-
1TUWYWS
12-1TUWYVC 8.1.1.1
When users navigate to the FSD
screen and click the Site Map
icon, the application crashes
12-1TS6LJ7 12-1TS6LIN 8.1.1.1
ACR 488: When users select
Quote > Apply Event Template,
the operation fails
12-1TK4H9V 12-1TK4H9B 8.1.1.1
ACR 488: Provides Histories and
Futures functionality
12-1TK3LUK 12-1QPT2Q7 8.1.1.1 Yes, see
Instructions for
ACR 488 on
page 310.
ACR 488: The Service End Time
field does not default to a
function's end time
12-1THO562 12-1THO555 8.1.1.1
ACR 450: The SR mapping
functionality only works for the
Contracted, Projected, and
Blocked fields
12-1THNM3U 12-1THNM2J 8.1.1.1
ACR 488: Within Opportunity >
Histories and Futures view >
Histories applet, Historical
Opportunities that have "Locked
Flag" = "Y" have the Delete
button disabled
12-1TG64N4 12-1TG64LV 8.1.1.1
ACR 488: Within the Quotes
screen, users are able to add
items to Fixed Packages
12-1TGNKZM 12-1TGNKY6 8.1.1.1
When users attempt to add
information into the Specific
Space field, they receive an error
message and a blank row is
inserted
12-1TG66FT 12-1TG66EJ 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
688
ACR 488: Billable Items are not
displayed in the Event Checks >
Guest Line items view
12-1TENSKV 12-1TENSDR 8.1.1.1
ACR 488: When users try to
enter information in the Function
Space field within the Function
list applet > Quote screen, they
12-1TE6G60 12-1TE6G47 8.1.1.1
ACR 488: Within the Histories
view, the application permits
users to check the locked field
for a Historical Opportunity
record even if they didnot create
the record
12-1TE6D2T 12-1TE6D1J 8.1.1.1
view > Quotes applet , the
Comments field does not have a
text box icon to allow users to
easily see the comments
12-1TE6CZD 12-1TE6CY3 8.1.1.1
Within the Room Blocks applet
within the Histories view, the
Actual vs Contracted and Actual
vs Blocked fields do not display
as percentages
12-1TE6CXE 12-1TE6CW4 8.1.1.1
ACR 488: The threadbar title
displays incorrectly for the
Histories and Futures views
12-1TE6CVQ 12-1TCP4Y8 8.1.1.1
opportunity and a quote for it,
create a function without adding
any function space, and then
navigate to the line items and
select Create Custom Menu/
Package from the menu, instead
of the Create Custom Menu/
Package dialog box, they receive
the following error message: :
Error message pop up "Method
ShowPopup is not allowed
here.(SBL-UIF-00348).
12-1TCP6GD 12-1TCP6F3 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
multiselect records from the pick
applets
12-1TARYRO 12-1TARYQC 8.1.1.1
ACR 488: Within the Quote >
Functions > Line Items view, the
Set System Allocation flag is
disabled
12-1TD6ZRH 12-1TD6ZQV 8.1.1.1
ACR 488: The System Allocation
flag should be read-only if the
package contain Split Menu
options
12-1TD67KR 12-1TD67JL 8.1.1.1
ACR488: Within Quote >
Function > Line Item screen,
users are able to add items to a
fixed menu
12-1TCOUBG 12-1TAR94G 8.1.1.1
ACR488: Columns are missing in
the Historical Opportunity applet
and Histories View applet
12-1TB8X2A 12-1TB8X0Y 8.1.1.1
screen, copy functionality is not
working properly
12-1TB9G5X 12-1TB9G4L 8.1.1.1
Within the Property Pricing
Admin screen, when users create
a record in the list applet and
then save the record, the Last
Updated By and Last Updated
Date fields are not updated
12-1T7VA8A 12-1T7VA71 8.1.1.1
ACR 488: The Split Pricing field
remains unchecked even when
Split Menu Price is added to the
product
12-1TAR8T1 12-1TAR8RB 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
690
When users try to add new menu
items or package items to
existing menus, they receive the
following error message: A
record that contains identical
values to the record you have
created already exists. If you
would like to enter a new record,
please ensure that the field
values are unique.(SBL-DAT-
00381)
12-1T9SIB5 12-1T9SIAL 8.1.1.1
ACR 488: The Histories check
box is missing in the Pick Event
Templates dialog box
12-1T7D8FX 12-1T7D8DP 8.1.1.1
multiselect records from pick
applets
12-1T7V61Y 12-1T7V60S 8.1.1.1
opportunity with Function Line
Items and Room Block Line
Items, navigate to the Capture
view, select the hotel in the
Properties applet, and click the
Create Quote button, they
12-1T5WR1X 12-1T3ZHD3 8.1.1.1
ACR 488: The setup style conflict
error message is not displayed
12-1T6EEB0 12-1T6EE9W 8.1.1.1
sort menus within the Menu list
applet by Course #, they receive
an error message
12-1T6DN7J 12-1T6DN5J 8.1.1.1
Within Opportunities, the
Number of Days field in the
Capture Dates view allows users
to enter departure dates that are
before the arrival dates
12-1SJ5UDK 12-1SJ5UC3 8.1.1.1
Improves the quality of Travel
and Transportation application
error messages
12-
1SJ5WWO
12-1SJ5WV9 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
When users add two functions in
a quote function list applet that
start at different times and that
have two different names, the
applet is sorted by function
name instead of by start time
12-1SG70W3 12-1SG70UT 8.1.1.1
Improves the usability of Travel
and Transportation application
error messages
12-1SF7RJM 12-1SF7RI9 8.1.1.1
ACR 450: The major header row
displays color for the first two
cells only instead of displaying
the weekend color for all cells
that display weekend
information
12-1S4TOQ9 12-1S2WL15 8.1.1.1
When a quote has a function,
subfunction, and complex line
items, the Copy Function
properly
12-1RXLGWP 12-1RXLGW1 8.1.1.1
There is no non-null value in
address attributes (such as Zip
code), so data cleansing does
not work
12-1RV6UXD 12-1KPTT57 8.1.1.1
ACR 450: Within the Quote
Function Line Items view, there
is no folder structure for menus
12-
1RHR32W
12-1RHR32C 8.1.1.1
Within eHospitality, when users
navigate to Property
Administration, query for TNT
Property, drill down on Property
Name to the Packages view,
create a new package, save the
record, and click the New button
in the Package Items view, the
popup window does not display
any items
12-1RNY5E7 12-1RNY5DN 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
692
to Property Administration,
query for TNT Property, drill
down on Property Name to
navigate to the Event Order/
Menu Items view, create new
products, save the record,
navigate to Opportunities and
back to to Property
Administration, query for TNT
Property, and drill down to the
Event Order/Menu Item view,
the newly-created records do not
display
12-1RNH7PA 12-1RNH7OG 8.1.1.1
enhancements:
Menus and Packages
Function Space Displays
Inventory Display
Enhancements
Sleeping Room Mapping
12-1R8LRF4 12-1QJJCQN 8.1.1.1 Yes, see
Instructions for
ACR 450 on
page 100.
ACR 488: Provides Histories and
Futures functionality for the
Siebel eHospitality application
12-1QPT2UA 12-1QPT2T1 8.1.1.1 Yes, see
Instructions for
ACR 488 on
page 310.
Universal
Customer Master
Other
ACR 437: The System
Registrations view does not have
UI validations
12-1TK4S6F 12-1RBI2FT 8.1.1.1
ACR 437: Seed data import fails
for JPN and NLD
12-1TK48IP 12-1T7V6FI 8.1.1.1
ACR 437: Incorrect capitalization
for the
OrganizationCrossReference
inbound Web Services causes
the operations to fail
12-1TK48HR 12-1T7D5IF 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
ACR 437: The GetCrossRef
operation fails for the
Organization, Person,
Household, and Financial Asset
Business Objects
12-1TK42MX 12-1T7V6JE 8.1.1.1
ACR 437: Survivorship is not
invoked correctly
12-1TJM79A 12-1TJM78P 8.1.1.1
Provides the following
enhancements to the
functionality provided in ACR
437:
Default values for Flag
columns for
BusinessComponent sifs
Adds missing LOVs
[CRMML,SOAP] and Web
service entries as seed data
Adds the Suffix and
HouseholdSize fields to
Integration Objects
Restructures the
ACR437_UCM.zip directory
12-1SX7UBH 12-1RZPUB1 8.1.1.1
ACR 437: The PersonService >
GetPerson method fails to return
multiple records
12-1SX7UAP 12-1SD8MX5 8.1.1.1
ACR437: Includes the new
cross-reference module in
fasvccif.dll instead of in
sscaucmxref.dll
12-1SX7UAC 12-1RVNYWA 8.1.1.1
ACR 437/MDM: When users
create a person, save the record,
and log into BPEL,
ProcessPersonUCMReqABCSImpl
(v. 1.0) fails with the following
error message:"ESB Dispatch
failed with error Response not
available from the
service"ProcessCustomerPartyLi
stRequestResponse"!
12-1SX7U9X 12-1SSU75R 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
694
ACR437: The IsPrimaryMVG flg
is not published for records
created/updated in UI in the
Acxiom flow
12-1SWGZJ4 12-1SSU76Z 8.1.1.1
Within Siebel 8.1.1 QF0001 for
ACR 437, the following two files
are missing from
ACR437_UCM.zip:
UCMMST811_seedimp_locale.in
p and seed_locale_NLD.dat
12-1SOZKT8 12-1RPF1Z9 8.1.1.1
ACR 437: Acxiom DLL does not
have the latest code
12-1SOZKS8 12-1RRCAHM 8.1.1.1
ACR 437: The
UCMBusinessComponents.sif file
is not current, so Account/
Contact merge does not work
12-1SOZKR6 12-1RR1O5N 8.1.1.1
ACR 437: The incorrect versions
of libraries for Pubsub and
Transaction Mgr were provided
12-1SOZKP4 12-1QK1GG2 8.1.1.1
ACR 437: Provides the ability to
expose CDI WebServices for all
CRUD operations on key entities
such as Account, Contact,
Household, Financial Account,
and so forth
12-1SJO2V0 12-1M4CI03 8.1.1.1 Yes, see
Instructions for
ACR 437 on
page 94.
ACR 437 error message strings
are not provided for languages
other than ENU
12-1RSS7TV 12-1RPEN89 8.1.1.1 Yes, see
Instructions for
ACR 437 on
page 94.
Publish/Subscribe
ACR 437: For Publish/Subscribe,
a crash occurs for multiple
thread workflows
12-1SX7UB4 12-1RZPUA5 8.1.1.1
ACR437: UNIX compilation fails
at fasvccifpubsub.cpp
12-
1SW1MC5
12-1RVNYUP 8.1.1.1
Publish/Subscribe fails to publish
messages to the AIA middleware
system when BDM workflows are
run
12-1SOZKQ4 12-1RBHO55 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
User Interface
Controls
Provides support for Internet
Explorer 8 on Windows Vista.
12-1RAJFVM 12-1RAJFUD 8.1.1.1.
Provides support for Internet
Explorer 8 on Windows XP SP3
12-1RAJFTT 12-1RAJFT5 8.1.1.1
Within Opportunities >
Opportunities List applet, when
users create a new Opportunity
Name, enter data in the Account
pick applet field, and press Tab,
the application opens the pick
applet, but when users close the
pick applet using the "X" button,
and query for the record that
they previously created, the
application does not launch the
Pick applet
12-1TE6ABF 12-1TE6AAV 8.1.1.1
Allows the Turkish i-dot
character to be handled correctly
in data queries (ACR 427)
12-1T4GEBF 12-1LEZF5Z 8.1.1.1
Querying with the Toggle applet
in base mode causes the
application to refresh
12-1SSCZU6 12-1PAWXSH 8.1.1.1
Adding a script causes the
calendar control to display dates
without quotes
12-1SJNTJ7 12-1N3J10T 8.1.1.1
application-level menus and
applet menus do not work
12-1R1W13D 12-1PMW7JX 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
696
enhancements:
Adds missing text for ALT
strings and other text read
by screen readers
Adds titles for views and
applets
Provides an announcement
of row and column identifiers
in list applets and allows the
column used for the row
identifier to be configurable
Fixes various loss-of-focus
defects
Fixes various tab-order
defects that are most often
encountered when users are
navigating between applets
Fixes various keyboard-
shortcut defects and extends
the list of available shortcuts
Adds help topics for
accessibility and updates the
keyboard shortcuts help
topics
12-1PFQEKX 12-1N3ZXFY 8.1.1.1 Yes, see
Instructions for
ACR 422 on
page 50.
Within list applets, the Show
Less and Show More icons
behave incorrectly
12-1SJ7NZM 12-1SJ7NYW 8.1.1.1
When users create a new Activity
and change its status to Done,
message: "We detected an Error
which may have occurred for one
or more of the following
reasons:An error happened
during restoring the context for
requested location(SBL-UIF-
00313)"
12-1SDQH8N 12-1EOTZ6O 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
In Standard Interactivity mode,
the RTC Editor does not appear
in application HTML email
messages
12-1QDSL8Y 12-1LSWNLF 8.1.1.1
When the AccessibleEnhanced
parameter for SI+ mode is
enabled, LOV values do not
appear, and screen readers
cannot read any values
12-1QDS835 12-1O5H1CL 8.1.1.1
Navigation
browser's Back and Forward
buttons do not work
12-1SD8N3Z 12-1RV6HKZ 8.1.1.1
Other
Querying on the Account applet
generates an extra query on the
Action Business Component
12-1U4HH59 12-1TK7X5V 8.1.1.1
> Administration Configuration
> Enterprise, navigate to
Component group, and perform
a query using the Query button,
message: Method
PositionOnRow is not allowed
here.(SBL-UIF-00348)
12-1T5X05W 12-1T5X04K 8.1.1.1
Within the eHospitality
application, when users create
an opportunity from the
Opportunity screen, click the
Arrival Date applet to select an
arrival date, they receive an
error message stating that UIF
cannot convert formatted strings
to the internal representation
12-1SI6D5V 12-1SI6D4D 8.1.1.1 Yes, see
Instructions for
ACR 456 on
page 102 and
Instructions for
ACR 488 on
page 310.
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
698
After navigating backwards
through a Task-Based User
Interface (TBUI) Task using the
"Previous" button, the "Created"
date field may show an incorrect
date
12-1S1Y0HJ 12-1RUP3LT 8.1.1.1
Accessibility: After users have
implemented ACR 422 for
accessibility enhancements, the
Sales application UI does not
display correctly
12-1RUPLSL 12-1OQCG6I 8.1.1.1
Accessibility: Header markups
are missing
12-1RUPLS7 12-1OXBCNG 8.1.1.1
ACR 422: The
Accessibility_Table.sif and
AdminScreen.sif files are
missing
12-1RUPLR7 12-1PG7MQ4 8.1.1.1
The Ctrl+Shift+B keyboard
shortcut does not open the
Column Displayed popup window
12-1RVO0Q4 12-1Q260FB 8.1.1.1
Within Siebel Sales, when users
navigate to the Account list
applet, drill down on any record
to reach the Account Entry
applet, tab through the applet
fields, open the Account Team
MVG, press OK to closethe MVG,
and then press the Tab key, the
focus moves to the Contact
applet instead of to Status
12-1RVO0PO 12-1PBVBQX 8.1.1.1
Accessibility: Within Siebel
Sales, when users navigate to
the Account list applet, press
Insert+F7, Previous Record Set
appears in Link List, but only
enabled links should display
12-1RVO0P8 12-1PBVBMR 8.1.1.1
Accessibility: The text
"Required" needs to display at
the end of field names that are
mandatory
12-1RVO0OS 12-1PAWFN5 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Accessibility: Corrects a defect
that caused screen readers to
read the incorrect word first
12-1RVO0OC 12-1PBDZME 8.1.1.1
Accessibility: In list applets, ">"
and "select check box" do not
have a column heading
12-
1RVO0NW
12-1PBDZK6 8.1.1.1
Accessibility: Only groups of
fields, lists, or tables should
have headers--tabs and menus
should not
12-1RVO0NG 12-1PAWFOJ 8.1.1.1
Accessibility: The Ctrl+Shift+K
keyboard shortcut opens
PlaceMarker List instead of the
Columns Displayed dialog box
12-1RVO0MI 12-1P9HAYP 8.1.1.1
Accessibility: The Ctrl+Alt+Z
keyboard shortcut does not
display View Name, View
Summary and Applet Name
12-1RVO0M2 12-1OXAV9N 8.1.1.1
Accessibility: Within Siebel Sales
> Projects > Notes, RTC Controls
are not displaying in the
Description field
12-1RVO0LK 12-1OUC5MI 8.1.1.1
Accessibility: Adjusts the color
contrast ratio for the "Remember
my User ID And Password"
dialog box
12-1RVO0KU 12-1OUC5LC 8.1.1.1
Accessibility: Within Siebel Sales
> Opportunities, when users
navigate to Revenue: Calculator
and press the Tab key to
navigate to ".", the screen
reader reads this text as "link"
instead of as "period
12-1RVO0KC 12-1OK1S1R 8.1.1.1
Accessibility: Adjusts the Color
Contrast Analyzer functionality
within Siebel Sales
12-1RU7S4M 12-1OD1CXK 8.1.1.1
Accessibility: Adjusts the color
contrast between the foreground
and the background within the
Service application
12-1RUPLQT 12-1OE44M7 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
700
Accessibility: There is no
keyboard shortcut to navigate to
third-level tabs
12-1RUPLQF 12-1OH39Y6 8.1.1.1
Accessibility: Within the Service
application > Service Explorer
view, when users launch the
screen reader, press Tab to move
to the Service Request Expand
link, and press Enter to expand
the link, the "Page load is
complete..." message displays,
but the focus is lost from the
Service application
12-1RUPLQ1 12-1OH39YW 8.1.1.1
to Service screen > All Service
Requests and press Ctrl+Alt+Z,
a dialog box displaying View
Name, View Summary and
Applet Name does not appear
12-1RUPLPN 12-1OXSNRF 8.1.1.1
Accessibility: After ACR 422 has
been implemented, when users
log into the application and then
click on any of the screen tabs,
message: Unable to create the
Business Service 'Chat UI
Business Service'(SBL-DAT-
00227)
12-1RUPLP9 12-1P56CN9 8.1.1.1
Accessibility: After ACR 422 has
been implemented, within the
Call Center application, when
users press Alt+Shift+M to go to
1st application level menu
listbox file, press Enter to set
forms mode on, and press Alt +
Down Arrow key to open the
menu listbox, the screen reader
reads blank entries because it
reads 1 of n entries for a
combobox depending on the
number of items in a combobox
12-1RV6IUD 12-1ODJYLT 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Accessibility: The color contrast
ratio is not sufficient for
toolbars, buttons, and icons
12-1RV6IU1 12-1ODLAXL 8.1.1.1
Accessibility: Page spacers are
not identified with an empty ALT
attribute (ALT=")
12-1RUPLOV 12-1PBVCGH 8.1.1.1
application > Communication
tab, the color contrast for the
tabs that are not active is not
sufficient
12-1RV6ITR 12-1OGCKDV 8.1.1.1
application > Home Page,
spacers are not specified with an
empty ALT attribute (ALT=")
12-1RUPLOH 12-1PBVCJQ 8.1.1.1
Accessibility: When users press
Ctrl+Alt+T to navigate to the
View tab, the focus moves to
screen applet rather than the
View tab
12-1RV6ITH 12-1OGLD07 8.1.1.1
application > Home Page screen,
empty ALT attribute (ALT=")
12-1RUPLO3 12-1PBVCOT 8.1.1.1
Accessibilty: Within CTI, when
users press Alt+Ctrl+M to
navigate to the application
menu, press Shift+F2 to
navigate to the CTI Toolbar, and
click inside the frame to set the
focus, when an inbound call
comes in, pressing Alt+Ctrl+M
does not move the focus to the
application menu, and pressing
Shift+F2 does not move the
focus to the CTI Toolbar. Instead,
the screen reader displays
"Frame."
12-1RV6IT4 12-1OQV78V 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
702
Accessibility: Within CTI, when
users press Alt+Ctrl+M to
navigate to the application
menu, press Shift+F2 to
navigate to the CTI Toolbar,
press Tab to focus on the CTI
Toolbar, and press Tab twice to
navigate to the 'Accept Work
button (the blinking telephone),
instead of displaying 'Accept
Work Item enabled link', the
screen reader reads 'Envoke
toolbar command left
parenthesis ... envoke command
Accept Work..... visited visited
visited visited visited....'
12-1RV6ISS 12-1OQV7BL 8.1.1.1
Accessibility: The Email Text edit
field is not available
12-1RV6ISI 12-1OTU6CJ 8.1.1.1
Accessibility: Within the My
Templates screen, the screen
reader reads the "HTML
Template" checkbox as the
"Public checkbox
12-1RV6IS8 12-1OUZSZS 8.1.1.1
Accessibility: Within the Call
Center application, when users
press Ctrl+Shift+T and Tab down
to the Communications screen
tab, select My Communications,
press Ctrl+Alt+] to focus on the
bottom applet, and tab down to
the body of the email, the screen
reader reads the content of the
email, but the keyboard
shortcuts no longer work
12-1RV6IRY 12-1PBEKVL 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
press Ctrl+Shift+T to move
down to Contacts, press
Ctrl+Alt+Q to query for a
contact, press Ctrl+Alt+1 to
display the Send Email Applet,
press Tab to move to the Send
Email: To link, press Enter to
open the Address book, and then
press Ctrl+Alt+Q, the Query
applet does not appear
12-1RV6IRO 12-1PBEKWS 8.1.1.1
navigate to the Accounts screen,
select All Contacts from the
Show combo box, select any
account and drill down on the
account name to reach the
Account form applet, and press
Ctrl+Alt+Q, the query appears,
but the focus is on the bottom
applet
12-1RV6IRE 12-1PBE210 8.1.1.1
Accessibility: The Help System is
not available
12-1RV6IR4 12-1PG7NRG 8.1.1.1
Accessibility: In Service >
Invoice, spacers are not
specified with an empty ALT
attribute (ALT="")
12-1RUPLNP 12-1PBVCQJ 8.1.1.1
navigate to Contacts > All
Contacts screen, bring the focus
to the All Contact list applet, and
press Ctrl+. (Ctrl+period), the
screen reader does not read the
keystroke but the focus is
changed to the next record. The
same issue occurs with the Ctrl+
shortcut.
12-1RV6IQI 12-1PI4IRN 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
704
Accessibility: When users
navigate to Service > All Service
Request > Invoice, initiate a
query, initiate the IE Developer
Toolbar, select Images > View Alt
Text in IE Developer Toolbar, all
decorative images, including
images used for spacers, do not
specify an empty ALT attribute
(ALT="")
12-1RUPLNB 12-1PBVCT3 8.1.1.1
Accessibility: The screen reader
reads ".....DFLT...." as a applet
summary
12-1RUPLMX 12-1PJ3BJ3 8.1.1.1
navigate to the Accounts screen,
select All Accounts from the
Show combo box, and highlight
the Account list applet, the
screen reader reads the applet
as Account Details Frame even
though it it a list applet
12-1RV6IQ8 12-1PJ2SAV 8.1.1.1
application, when users initiate
the IE Developer Toolbar from
within the Home Page, and
select Images > View Alt Text, all
empty ALT attribute (ALT="")
12-1RUPLMJ 12-1PMFGQP 8.1.1.1
Accessibility: Within any Siebel
to a view with a table, enter the
table using T or Ctrl + Insert +T,
turn the Forms mode ON by
pressing the Enter key, and tab
through the fields in the record,
the screen reader reads the
values in the fields and not the
column header
12-1RUPLM5 12-1Q0P7T3 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
tab down to the Accessibility link
on homepage, press Enter to
open the Introducing
Accessibility page, click on
"Getting Started: Using
Keyboard Shortcuts" to open the
Using Keyboard Shortcuts page,
and press Tab to navigate to
"Introducing Accessibility" under
the See Also section, the screen
reader reads Introducing and
Accessibility as different links
instead of one single link
12-1RV6IPX 12-1PJ2SCU 8.1.1.1
Accessibility: Within Siebel
Sales, when users navigate to
the Revenues screen, press
Ctrl+Shift+V to place the focus
on the Show combo box, press
Enter, and press Alt+ the down
arrow to open the combo box,
the menu is executed before the
user can press the down arrow to
focus on a menu item
12-1RU7S3L 12-1PYEFBL 8.1.1.1
Accessibility: Within the Siebel
Public Sector application, when
users navigate to Evidence >
Evidence list applet, create a
new record, press Tab to
navigate to the Evidence Parent
pick icon, press Enter, and
attempt to launch a query, they
12-1RUP2XC 12-1Q2MXXG 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
706
Service application, when users
navigate to Service > All Service
Requests > Charges view,
initiate the IE Developer Toolbar,
and select Images > View Alt
Text in IE Developer Toolbar, in
the View tab bar, all of the
empty ALT attribute (ALT="")
12-1RUP1FX 12-1PBVCN3 8.1.1.1
users navigate to Cases screen >
Cases list applet, and press
Ctrl+Alt+] to focus on the Cases
form applet, the screen reader
does not read the default
control's name
12-1RUP2W9 12-1OYTDIR 8.1.1.1
users navigate to Leads screen >
Leads form applet, press Tab to
navigate to the New button and
press Enter, press Tab to
navigate to the Team Member
MVG, press the New button
within the Team Member dialog
box, press Tab to navigate to the
Find dialog box, and press Alt +
the down arrow key to change
the selection, the Next/Previous
sets of records displays
12-1RUP2VU 12-1PILJI1 8.1.1.1
users navigate to Cases Screen
> Cases form applet, press
Ctrl+N or click the New button to
create a new record, cancel the
operation, and attempt to query,
the label for the required fields
displays "Required Required...:"
12-1RUP2VF 12-1PS5Z73 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
users navigate to Cases screen >
Cases list applet, press Alt+Q to
perform a query, delete a record,
and then attempt to undo the
operation using the ESC key, the
Alt+Q and ESC keyboard
shortcuts do not work
12-1RUP2V4 12-1Q25XIX 8.1.1.1
Accessiblity: Within the Siebel
Public Sector application, the
Query, Cancel, and Delete
buttons are missing from some
of the screens
12-1RUP2UP 12-1Q3N2WK 8.1.1.1
users navigate to the
Administration - Application >
View Attributes view, create a
new record with Attribute Type =
Summary and View Name =
"HLS All Case List View", change
the Attribute Value to "Changed
sum HLS All Case List View",
save the record, repeat the
previous steps for the "PUB All
Leads list view, and generate a
new XML file, the changes that
they have made are not reflected
in the new XML file
12-1RSAOI2 12-1Q905IV 8.1.1.1
Accessibility: For the Siebel
users attempt to import the SIF
files in the
REPPATCH\ACCESSIBILITY\sif
folder, the
AccessibilityXMLFileName
application-level user property is
not compiled into the SIF
12-
1RSAOHM
12-1QZY9D9 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
708
users navigate to Immigration
Contacts screen > Identities
view, and create a new record
under Identities form applet, an
additional Delete button
displays, and this button is not
necessary because there is a
Cancel button on the applet
12-1RSAOHD 12-1R0F1JX 8.1.1.1
Call Center SI+ application,
when users navigate to the
Contacts screen, open the IE
Developer toolbar, select Images
> View Alt Text in the IE
Developer toolbar, within the
Contact home page, the Recent
Record spacers are not specified
with an empty ALT attribute
(ALT="")
12-1RSANEG 12-1PI40XY 8.1.1.1
When users log into Siebel Sales
and navigate to Contacts Screen
tab > Contacts > Show Combo
box >Job Title Analysis >
Contact Chart View - Job Title
Analysis, they receive the
following error message: JAWS
Failed to read Error in Chart
Server connect string, or the
Chart Server is not started.
(SBL-CHT-00103)
12-1RSANCE 12-1OGKNKN 8.1.1.1
Accessibility: In Service
Requests, the spacers are not
specified with an empty ALT
attribute (ALT="").
12-1RSAN9A 12-1PBVCKS 8.1.1.1
Accessibility: Within the Comm
Inbound Item Body applet,
empty ALT attribute
12-1RSAN79 12-1PI40ZP 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Accessibility: In the My
Templates view, the spacers are
not specified with an empty ALT
attribute
12-1RSAN67 12-1PI4112 8.1.1.1
The <Accessibility>Page
download confirmation message
should be disabled by default
12-1ROFVKG 12-1ROFVJ1 8.1.1.1
Call Center SI+ application,
when users navigate to teps to
the Contact > All Contacts view,
select the Account MVG, press
Enter, and press Ctrl+Insert+T,
no table is listed
12-1ROFVIQ 12-1ROFVHH 8.1.1.1
If a user closes a tabbed
browsing window in Internet
Explorer 7 by clicking on the X,
then the window closes but the
Siebel session is not logged out
12-1R1VGKZ 12-1NCHOM7 8.1.1.1
attempting to Export Tab Layout
12-1QUO1AN 12-1QMXGFN 8.1.1.1
Popups/Pick Lists/
MVG/Shuttle
When users try to undo a query
after typing in a set of
characters, they receive the
folllowing error message:
"Method UndoRecord is not
allowed here. (SBL-UIF-00348)
12-1T6DTOD 12-1T6DTMX 8.1.1.1
Personalization rules do not work
on Association applets
12-1SZMOB5 12-1P5N6JM 8.1.1.1
users navigate to any views,
message:
'navigator.SWE_historyKeys.123
5411125328' is null or not an
object
12-1SF7XSB 12-1S99GIP 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
710
With Internet Explorer 8, the Ctrl
+ D shortcut opens "Add a
favorite" instead of deleting the
record in the Attachments applet
12-1SF7XRC 12-1SF7XQL 8.1.1.1
users navigate to Expense
Reports > Expense List, create a
new record, click on the
Opportunity pick applet in the
form applet, and then click on
the Account pick applet, the
application hangs
12-1S9RQYV 12-1RU7S2V 8.1.1.1
Within Internet Explorer 8,
within the Contact list applet,
when users click Send Page and
click the icon within Message
Body, the OK and Cancel buttons
display incorrect text
12-1SC3OFC 12-1SC3OEN 8.1.1.1
Minimizing or maximizing
Internet Explorer 7 when on a
Multi-Value Group causes the
12-1SC96ZX 12-1P19TU1 8.1.1.1
users launch the application,
navigate to the Account list
applet, press Ctrl+Shift+J, close
the Favorites tab, and then press
Ctrl+Shift+K, a new windows
tab opens, and when users press
Ctrl+N, a new browser window
displays
12-1SC95S7 12-1SC95RI 8.1.1.1
With Internet Explorer 8, using
the CTRL + L keyboard shortcut
opens the Open popup window
instead of the Correspondence
window
12-1SC95R6 12-1SC95PX 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
Instructions for FR 12-1ZFE3KR
Within My Oracle Support, navigate to the Knowledget tab, and search for Article ID 473945.1. Follow
the instructions in that document before you perform the procedure detailed below.
1 Within Siebel Tools, edit Signature Capture Applet ( in this case Order Signature Capture) to use
class as CSSFrameFSSign instead of CSSFrame.
2 Edit the corresponding BC to have Signature field. The name of the BC field introduced for
storing signature data must be Signature only.
The applet Browser script should refer to the Signature field to store/read the signatures from
the database table.
3 Run genbscript command to generate all java script for all browser script.
When duplicating a record in the
list applet, an error can be
generated. On Internet Explorer
6, the error message will go
away when acknowledged, and
focus can then be changed to the
form applet. On Internet
Explorer 7, the error message
does not go away.
12-1OK0ULQ 12-1OK0UL5 8.1.1.1
Web Service
Other
Within Siebel Tools, when users
navigate to File > New Object >
EAI tab > Web Service, and
display the WSDL Import Wizard
dialog box, when users select a
locked project, select the Adobe
LiveCycle 8.1 WSDL file, and
click Next, they receive the
following error message: There
are no web service definitions to
be generated.(SBL-EAI-04340)
12-1RH8IMZ 12-1PG7NLN 8.1.1.1
Integrating attachments does
not work when WS-Security is
used
12-1RH8IMO 12-1LTG2F6 8.1.1.1
Issue Addressed
Fix Request
ID
Change
Request ID
Fixed in
Version
Configuration
Instructions
712
4 To overcome the The specialized method StoreSignature' is not supported on Business
Component Order Entry - Orders' used by Business Object 'Order Entry (Sales)' error message,
use return (CancelOperation); instead of return (ContinueOperation); in the
WebApplet_PreCanInvokeMethod.
Instructions for FR 12-1YKOEQV
1 Within Siebel Tools, navigate to the LOY Members project, and lock it.
2 Within the Repository Objects panel, select Projects.
3 Query for the LOY Members project and lock it.
4 Within the Repository Objects panel, select Business Components, and add a new record with the
following details.
Name: LOY Merge Action
Table: S_EVT_ACT
Project: LOY Members
5 Save the Business Component.
6 In the Repository Object panel, select Business Components, select Fields, and add a new field
with the following details:
Name: LOY Member Id
Join: S_EVT_ACT_LOYX
Column:
Force Active: TRUE
Immediate Post Changes: TRUE
7 Compile the LOY Merge Action business component to the SRF.
8 Create a new link between the LOY Member business component and the LOY Merge Action
business component:
a In the Repository Object panel, select Link.
b Create a new record with the following details.
Parent BC: LOY Member
Child BC: LOY Merge Action
Source Filed: Id
Destination Field: LOY Member Id
Name: LOY Member/LOY Merge Action
Project- LOY Members
c Save the link and compile it link to the SRF.
9 Add the LOY Merge Action business component to the LOY Member business object:
a In the Repository Objects panel, select Business Objects.
b Query for the LOY Member business object and lock it.
c Add a new record in Business Object Components with the following details
Business Component: LOY Merge Action
Link: LOY member/LOY Merge Action
10 Save the business object and compile it to the SRF.
Instructions for FR 12-1XS21JF
2 Import 'LOY Redemption Voucher Reissue' Task UI.
3 Navigate to Administration > Business Process >Task Deployment.
4 Query for the LOY Redemption Voucher Reissue Task UI and activate it.
Instructions for FR 12-1XM93ST
1 Import "LOY Point Balances Project.sif" and compile it to the srf.
2 Select "LOY Member" under Business Object, add "LOY Member Point Balances VBC" as Business
Object Component (link is not required) and compile the SRF.
3 Select "LOY Member Services" under Business Service, add "CalMemPointBalances" to Business
Service Method (no input/output arguments required) and compile the SRF.
4 Under View, select "LOY All Member View", "LOY All Members Across Organization View", "LOY
Member Detail View" and "LOY My Member View", add "LOY Member Point Balances Task Group"
under View Task Group list and compile the SRF.
5 Navigate to Administration - Business Process > Task Deployment.
6 In the Published Tasks applet, query for the "LOY Member Point Balance" task flow and activate it.
7 Navigate to Administration - Application > Tasks.
8 In the Registered Tasks applet, click New and add "LOY Member Point Balance" task for Task
Name.
9 In the Responsibilites applet, click New, and add the Siebel Administrator and Loyalty
Administrator responsibilities.
Instructions for FR 12-1Z3ZZO2
Fix involves the following repository changes.
(I). Create 'LOY Merge Transaction' BC
2 Create a new business component with the following details:
714
Name: LOY Merge Transaction
Table: S_LOY_TXN
3 Add the following fields to this business component
Field Name : Member Id
Column: MEMBER_ID
Field Name : Voucher Id
Column: VOUCHER_ID
4 Query for the LOY Member business object and lock it.
5 Add a Business Object Component with the following details:
Bus Comp: LOY Merge Transaction
Instructions for FR 12-1P4ORNT
1 Within Siebel Tools, navigate to Object Explorer, and query for the LS Document Tracking
business component.
2 Lock the LS Clinical Enhancement project.
3 In the Field section of the LS Document Tracking business component, create a new record with
the following values:
Column Name: Login User
Calculated Field: Check
Calculated Column: LoginName()
Type Column: "DTYPE_TEXT".
Leave the rest of the entries in the default state.
4 Get the sif files from $TOOLS_PATH/REPPATCH/811x_FP_LS_Clinical_BIP_Reports.zip and lock
the LS Clinical Enhancements project.
5 Import the BIP LS Protocol Document Tracking.sif file and compile the SRF.
6 Within the Siebel application, navigate to Site Map >Administration - BI Publisher Reports >
Reports - Standard Templates.
7 Create a new report called Protocol Level Document Tracking and associate it with the
LS_Protocol_Document_Tracking.rtf template. Select Output type as "All".
8 In the XLIFF field, upload the LS_Protocol_Document_Tracking.xlf file.
9 In Report Standard Template Registration Admin View > Translations tab, create a new record
and pick the desired language and report name for which the translation is required.
10 In the Integrations Objects tab, navigate to the Integration Object Name field and query for "BIP
LS Protocol Document Tracking"
11 Naviate to Administration-BIP Report > View Association, and associate the report to the LS
Protocol Document Tracking View and the LS Protocol CRF Tracking View.
Instructions for FR 12-1P4ORN3
1 Within Siebel Tools, navigate to Object Explorer and query for the LS Document Tracking business
component.
3 In the Field section of the LS Document Tracking business component, create new record with
Calculated Field: Checked
Column Type: "DTYPE_TEXT"
the LS Clinical Enhancement project
5 Import the BIP LS Region Document Tracking.sif file and compile the SRF.
6 Within the Siebel application, navigate to Site Map > Administration - BI Publisher Reports >
7 Create a new report called Region Level Document Tracking and associate it with the
LS_Region_Document_Tracking.rtf template. Select Output type as all.
8 In the XLIFF field, upload the LS_Region_Document_Tracking.xlf file.
9 In the Translations tab, query for "BIP LS Region Document Tracking" in the Integration Object
name field and select it.
10 Within Report Standard Template Registration Admin View > Translations tab, create a new
record and pick the desired language and report name for which the translation is required.
11 Navigate to Administration-BIP Report > View Association and associate the report to the Clinical
Protocol Site List View.
Instructions for FR 12-1P4ORMQ
1 Within Siebel Tools, navigate to Object Explorer and query for the Clinical Protocol Site business
component.
2 Lock the LS Clinical Protocol Site project.
the LS Clinical Protocol Site project.
4 Unzip the zipped file, import "BIP LS Clinical Protocol Site.sif", and compile the SRF.
716
5 Within the Siebel application, navigat to Site Map >Administration - BI Publisher Reports->
6 Create a new report called Regional Document Tracking Across Sites and associate it with the
LS_Regional_Document_Tracking_Across_Sites.rtf template. Select Output type as All.
7 In the XLIFF field, upload the xliff file corresponding to the report.
8 Navigate to Report Standard Template Registration Admin view > Translation tab create a new
9 In the Integrations Objects tab, navigate to the Integration Object Name field and query for "BIP
LS Clinical Protocol Site".
10 Navigate to Administration - BIP Report > View Association, and associate the report to the
Clinical Protocol Site List View.
Instructions for FR 12-1P4ORMD
1 Within Siebel Tools, navigate to Object Explorer, and query for the Clinical Protocol Site business
component.
3 If the Login User field does not already exist, in the Field section of the Clinical Protocol Site
business component, create a new record with the following values:
Column Type: "DTYPE_TEXT"
4 Make the following changes for Indication Display:
a Within Object Browse, under Business Component navigate to Join and create a new record with
Table: S_CL_PGM_APP_LS
Alias: S_CL_PGM_APP_LS
b Navigate to Join Specification, and create a new record with the following values:
Name: Application Id
Source Field: Application Id
c Within Object Browse, under Business Component, navigate to Field, and create a new record
with the following values:
Name: Application Id
Join: S_CL_PTCL_LS
Column: PGM_APPLN_ID
d Within Object Browse, under Business Component, navigate to Field, and create a new record
Name: Protocol Program Indication
Join: S_CL_PGM_APP_LS
Column: INDICATOR_CD
PickList - Clinical Program Indication Picklist
5 If you do not want to perform the manual steps detailed above, do the following:
a Get the sif files from $TOOLS_PATH/REPPATCH/811x_FP_LS_Clinical_BIP_Reports.zip and lock
b Import Clinical Protocol Site.sif.
7 Unzip the zipped file and import "BIP LS Clinical Protocol Site.sif".
8 Compile the SRF.
9 Within the Siebel application, navigate to Site Map >Administration - BI Publisher Reports->
10 Create a new report called Protocol Document Tracking Across Sites and associate it with the
LS_Protocol_Document_Tracking_Across_Sites.rtf template. Select Output type as All.
11 In the XLIFF field, upload the LS_Protocol_Document_Tracking_Across_Sites.xlf file.
12 Within Report Standard Template Registration Admin View > Translations tab, create a new
13 In the Integrations Objects tab, within the Integration Object Name field, query for BIP LS
Clinical Protocol Site.
14 Navigate to Administration-BIP Report > View Association, and associate the report to the
Clinical Protocol Site List View, the Clinical Protocol Site Manager's List View, and the Clinical
Protocol Site All List View.
Instructions for FR 12-1P4ORM0
1 Within Siebel Tools, navigate to Object Explorer, and query for the Clinical Protocol Site business
component.
3 If the Login User field does not already exist, in the Field section of the Clinical Protocol Site
business component, create a new record with the following values:
718
Type Column: "DTYPE_TEXT"
the LS Clinical Protocol project.
5 Unzip the zipped file, import the BIP LS Site Enrollment Status.sif file, and compile the SRF.
7 Create a new report called Site Enrollment Status and associate it with the
LS_Site_Enrollment_Status.rtf template. Select Output type as All.
8 In the XLIFF field, upload the LS_Site_Enrollment_Status.xlf file.
9 Within Report Standard Template Registration Admin View > Translation tab, create a new record
and pick the desired language and report name for which the translation is required.
10 In the Integrations Objects tab, navigate to the Integration Object Name field, and query for BIP
LS Site Enrollment Status.
11 Navigate to Administration-BIP Report > View Association, and associate the report to the
Clinical Protocol Site View.
Instructions for FR 12-1YFTGBH
1 Within Siebel Tools, navigate to Object Explorer, and click the Projects tab.
2 Query for "LS Clinical Payments" and lock the project.
3 Within the Object Explorer, navigate to the Applet tab, query for "Clinical Protocol Site Payment
Exceptions List Applet", and lock it.
4 In the Object browser, under Applet, click Control, and query for "NewRecord".
5 Change the value of the Method Invoked field from "ShowPopup" to "NewRecord".
6 Save the record, and compile the SRF.
Instructions for FR 12-1YJ7X13
1 Within the Siebel application, navigate to Administration - BI Publisher Reports >Reports -
Custom Templates, and query for Report Name = MDV.
2 Update the Template path with the LS_MDV.rtf.
3 Update the Xlf file path with latest LS_MDV.xlf.
4 Click the Upload button to upload the template to the BIP server.
5 Generate the MDV report, and view it in the LS Medical Product Issues RR view.
6 Verify report for Telephone and Fax.
Instructions for FR 12-1P4ORNG
1 Within Siebel Tools, navigate to Object Explorer, and query for the LS Document Tracking
business component.
3 In the Field section of the LS Document Tracking business component, create a new record with
Calculated: LoginName()
Type Column: "DTYPE_TEXT".
4 Query for the Clinical Protocol Site business component.
the LS Clinical Protocol Site project
6 Unzip the zipped file, import BIP Site Initiation By Site.sif, and compile the SRF.
8 Create a new report called Site Document Tracking and associate it with the
LS_Site_Document_Tracking.rtf template. Select Output type as All.
9 In the XLIFF field, upload the LS_Site_Document_Tracking.xlf file.
10 Create a new report and associate it with the LS_Site_Document_Tracking.rtf template. Select
Output type as All.
11 In the Integration Object tab, query for "BIP Site Initiation By Site" in the Integration Object
name field and select it.
12 In the Translation tab, create a new record and pick the desired language and report name for
which the translation is required.
13 Navigate to Administration - BIP Report > View Association and associate the report with the LS
Site Document Tracking View and the LS Protocol Site CRF Tracking View.
Instructions for FR 12-1ZUS8M9
1 Within Siebel Tools, navigate to Object Explorer, and then navigate to Applet.
2 Querying for the Clinical Protocol List Applet * applet, and lock it.
3 In the Object Explorer under Applet, select "Drilldown Object" and locate the Protocol object.
4 Update the "Source Field" with the value "Id" as shown in the first table below.
5 Repeat the Step 3 and Step 4 for the Protocol With Regions object (set Source Field = "Id" as
shown in the second table below.)
720
6 Compile the LS Pharma Common object.
The Protocol Drilldown Object
The Protocol With Regions Drilldown Object
Instructions for FR 12-1ZYN9IP
1 Within Siebel Tools, navigate to Object Explorer, and then navigate to Project.
2 Query for the following projects and lock them:
LS Clinical Protocol
LS Pharma Common
LS Clinical Subject
LS Clinical Programs
LS Clinical Region
3 Within Object Explorer, navigate to Applet, and query for "Clinical Region List Applet".
4 In the Object Explorer under Applet, select List > List Column, and query for Field = Protocol
Title.
5 Update the "Display Name - String Reference" field from SBL_TITLE-1004225622-03M to
SBL_TITLE-1004225657-02U.
6 Repeat Step 3 through Step 5 for the following applets:
Clinical Program Protocol List Applet
Clinical Subjects Parent Visit Templates List Applet
Clinical Protocol List Applet
Clinical Protocol Admin List Applet
Clinical Protocol List Applet (LS Home)
7 Query for Clinical Protocol Admin Short Form Applet.
8 Under Applet, select Control, and query for "Field" = "Protocol Title".
9 Update the "Caption - String Reference" field from SBL_TITLE-1004225622-03M to SBL_TITLE-
1004225657-02U.
10 Repeat Step 7 through Step 9 for the following applets:
Name Protocol
Source Field Id
Name Protocol With Regions
Source Field Id
Clinical Protocol Admin Form Applet
Clinical Protocol Form Applet
Clinical Protocol Short Form Applet
11 Compile the locked objects.
Table 1: For List Applets- Applet > List > List Column
Table 2: For Form Applets- Applet > Control
Instructions for FR 12-1YZN89Z
Copy the jar file SiebelCustomXMLP_SIA.jar should be copied from \\...ses\siebsrvr\CLASSES to
\OraHome_2\oc4j_bi\j2ee\home\applications\xmlpserver\xmlpserver\WEB-INF\lib.
Instructions for FR 12-1YOK7QV
The Siebel applications user must have the read and write permission of the siebel client root
installation directory in order to use this Quick Start feature in Vista.
Instructions for FR 12-1UHQ1L9
2 Within Repository Objects panel, select Projects, query for the LOY Members project and lock it.
3 Create a new business component called LOY Merge Action
4 Within the Repository Objects Panel, select Business Components, and add a new record with the
following details:
Name: LOY Merge Action
Table: S_EVT_ACT
5 Save the Business Component.
6 Within the Repository Objects panel, within the Business Components section in the panel, select
field, and add a new field with the following details.
Name: LOY Member Id
Join: S_EVT_ACT_LOYX
Field Protocol Title
Display Name - String Reference SBL_TITLE-1004225657-02U
Field Protocol Title
Caption - String Reference SBL_TITLE-1004225657-02U
722
Column:
Force Active: TRUE
Immediate Post Changes: TRUE
7 Compile the LOY Merge Action business component to the SRF.
8 Create a new link between the LOY Member business component and the LOY Merge Action
business component:
a Select Link in the Repository Objects panel, and create a new record with the following details.
Parent BC: LOY Member
Child BC: LOY Merge Action
Source Filed: Id
Destination Field: LOY Member Id
Name: LOY Member/LOY Merge Action
Project- LOY Members
b Save the link and compile it to the SRF.
9 Add the LOY Merge Action business component to the LOY Member business object:
a Choose Business Objects in the Repository Objects panel.
b Query for the LOY Member Business object and lock it.
c Add a new record in Business Object Components with the following values
Business Component: LOY Merge Action
Link: LOY member/LOY Merge Action
d Save the business object and compile it to the SRF.
Instructions for FR 12-1XJDJYH
1 Within Siebel Tools, navigate to the Object Explorer, and expand Applet.
2 Search for the following applets
UMF Messages Popup List Applet
UMF Message List Applet - SI
3 Add a new applet user property with the following name and value:
Name: Active Row Size
Value: A number that should exceeds the maximum possible number of messages in the
product recommendation. For example, 100.
4 Compile the locally locked projects into the original SRF.
Instructions for FR 12-1TK90K2
The configuration changes are explained with an example.
This example assumes that youare interested in filtering out Products with Product Type: Technical.
The Product Type field is mapped to the column PROD_CD of the table S_PROD_INT and it is a
LOV field with LOV type PROD_CD.
You need to add the following fields in the Cfg ISS Obj Details business component:
Field Name Calculated Calculated Value Join Column Type Text Length
Prod Type From Prod N S_PROD_INT PROD_CD DTYPE_TEXT 30
Prod Type Y LookupName(PROD_CD, [Prod Type From Prod]) DTYPE_TEXT
Add a field user property to this field as follows
Field UP name Value
Cfg UI Field TRUE
The calculated field above is required only if you are excluding an LOV field.
It is important to set the Field User Property Cfg UI Field to TRUE for the field that you
want to exclude.
The S_PROD_INT join is already defined in the Cfg ISS Obj Details business component.
You need to add a User property to the ABO Bulk Request Action Component business component.
BC User Property Name User property value
Exclude:Prod Type:LOV:PROD_CD Technical
The format of the BC User Property Name Exclude:<Field Name>:LOV:<Field LOV Type>.
The User property value should specify the value that you would like to exclude. (In this case,
it is technical in this case. This is the value seen in the Siebel application.)
NOTE: The <Field Name> specified here should match exactly with the filed name (new field)
specified in the BC - Cfg ISS Obj Detailes (in our case it is Prod Type).
In case the field you are excluding is not an LOV, then the format of the BC User Propert y Name
is Exclude:<Field Name.
Compile the ABO Bulk Request Action Component and Cfg ISS Obj Details business components
to the .srf file.
After these changes the component pick applet should not show products of type Technical.
The following is an example for Excluding NON-LOV fields:
It assumes that you are interested in filtering out Products with Dummy Field1: Dummy Value1.
Assume that the Dummy Field1 field is mapped to the column DUMMY_COL of the table
S_PROD_INT .
You need to add the following fields in the Cfg ISS Obj Detailes business component:
724
Dummy Field1 N S_PROD_INT DUMMY_COL DTYPE_TEXT
Add a field user property to this field with the following values:
Field UP Name: Cfg UI Field
Value: TRUE
You need to add a user property to the ABO Bulk Request Action Component business component:
BC User Property Name User property value
Exclude:Dummy Field1 Dummy Value1
Instructions for FR 12-1Y902IR
1 Within Siebel Tools, navigate to the Cfg WebChannel project and lock it.
2 Query for the CfgInteractData integration object.
3 Navigate to the Attribute Value integration component, navigate to Integration Component
Fields, and add a new field with the following values:
Name: LIC Value
Data Type: DTYPE_TEXT
XML Style: Element
XML Tag: LICValue
4 Compile the changes and restart the application.
Instructions for FR 12-1X65SFB
1 Within Siebel Tools, query for the Cfg Web UI Service business service, and lock it.
2 Navigate Business Service User Properties and add a new property with the following values:
Name: Refresh Template Fields:X
NOTE: X represents a number as in Refresh Template Fields Refresh Template Fields:0,Refresh
Template Fields:1 etc. The format is as follows: TemplateName,field1,field2,field3,field4.
Value : SISOMeCfgControlRadioPrice.swt,Extended Quantity Requested
3 Complile the srf.
Instructions for FR 12-1ZD5KI4, FR 12-1YZMU0U, FR 12-1Z04AQ7,
and FR 12-1Z04AS3
For information about how to implement this fix, within My Oracle Support (https://
support.oracle.com), navigate to the Knowledge tab and search for Article ID 1157939.1.
Instructions for FR 12-1Z0MD73
To get results in Advance Search for HTML documents, the HTML file format needs to be included in
advance search. To accomplish this, add an LOV with the following values:
Type: SEARCH_FILEFORMATS
Display Value: HTML
LIC: HTML
Translate: True
Language Name: English-American
Active: True
Instructions for FR 12-1ZM2V2V
Use the instructions in the following procedures to implement this fix.
Preconfiguration Task
Before you begin your configurations, within Siebel Tools, query for the following projects and
lock them:
Asset Management
To modify the Asset Mgmt - Asset - Header business component
1 Within Siebel Tools > Object Explorer, select Business Component.
2 Query for the Asset Mgmt - Asset - Header business component.
3 Create the following join.
NOTE: Name, Destination Column, and Source Field are present in Join Specification.
4 Create the following field:
Table Alias
Outer
Join
Flag Name
Destination
Column Source Field
S_ORG_EXT Master
Account
Y Root Account Id ROW_ID Owner Account
Id
726

To modify the SI S OM PMT Service business service
1 Within Siebel Tools > Object Explorer, select Business Service.
2 Query for the SIS OM PMT Service business service.
3 Query for the Iterate Process For Selected Rows business service method.
4 Create the following business service method argument:
To modify the SI S OM Modify Products & Services Process workflow
1 Within Siebel Tools > Object Explorer, select Workflow Processes.
2 Query for the SIS OM Modify Products & Services Process workflow and revise the workflow.
3 In the revised workflow, select Edit Workflow Process from the menu.
4 Add the following process property:
5 Add the following output argument in the Get Account Details step.
6 Add the following input argument in the Edit Asset Selections step.
Name Join Column Length Type
Root Account Id Master Account MASTER_OU_ID 15 DTYPE_ID
Name Data Type Type Optional Storage Type
Search
Specification
String Input Y Property
Business
Object Data Type
Property Name Type
Business
Component Name
Business
Component Field
To modify the SI S OM Disconnect Products & Services Process workflow
2 Query for the SIS OM Disconnect Products & Services Process workflow and revise the workflow.
6 Add the following input argument in the Disconnect Promotion step.
To modify the I SS Promotion Disconnect I ntegration SubProcess workflow
2 Query for the ISS Promotion Disconnect Integration SubProcess workflow and revise the
workflow.
Input Argument Type Property Name
Search Specification Expression '[Root Account Id] = ' + '"' +
[&Root Account Id] + '"'
Business
Object Data Type
Property Name Type
Business
Component Name
Business
Component Field
728
5 Add the following input argument in the Disconnect Promotion Sub step.
To modify the I SS Promotion Disconnect Process workflow
2 Query for the ISS Promotion Disconnect Process workflow and revise the workflow.
5 Add the following input argument in the Edit Related Item step:
6 Add the following input argument in the Disconnect Promotion Self step:
Business
Object Data Type
Root Account Id Root Account Id In Account String
Business
Object Data Type
Root Account Id Root Account Id In Account String
Search Specification Expression '[Root Account Id] = ' + '"' +
[&Root Account Id] + '"'
To create the I SS Promotion Check Order I tem Sub Process workflow
2 Create a new workflow called ISS Promotion Check Order Item Sub Process with the following
details:
3 Select Edit Workflow Process from the menu.
5 Add a Start step to the workflow.
Search Specification Expression '[Root Account Id] = ' + '"' + [&Root
Account Id] + '"'
Name Project Business Object Workflow Mode Group
ISS Promotion
Check Order Item
Sub Process
ISS Promotion
Workflow
Order Entry
(Sales)
Interactive Flow Product
Promotions
Root Account Id Root Account Id In/Out Order Entry
(Sales)
String
Active Document
Id
Active Document
Id
In Order Entry
(Sales)
String
Integration Id Integration Id In Order Entry
(Sales)
String
730
6 Add a Siebel Operation step with the following details:
Workflow Step:
Search Spec Input Arguments:
Output Arguments:
7 Add a new connector from the Start step to the Query Order step.
Name Operation Business Component
Query Order Query Order Entry - Orders
Expression
Business
Component
Filter
Business
Order Entry -
Orders
Order Entry -
Orders
Expressio
n
'([Id] = "' + [&Active Document Id] + '")'
Property Name Type
Business
Compone
nt Name Business Component Field
Root Account Id Business
Component
Order
Entry -
Orders
Root Account Id
Workflow Step:
9 Add a new connector from the Query Order step to the Query Order Line Item step.
10 Add an End step to the workflow.
11 Add a new connector from the Query Order Line Item step to the End step.
To create the I SS Promotion Check Quote I tem Sub Process workflow
2 Create a new workflow called ISS Promotion Check Quote Item Sub Process with the following
details:
3 Select Edit Workflow Process from the menu.
Name Operation
Business
Component
Query Order Line Item Query Order Entry - Line
Items (Simple)
Expression
Business
Component
Filter
Business
Order Entry - Line
Items (Simple)
Order Entry -
Line Items
(Simple)
Expressio
n
'([Asset Integration Id] = "' + [&Integration
Id] + '") AND ([Action Code] <>
LookupValue
("ABO_BR_ACTION_CODE","Delete"))'
Name Project
Business
Object
Workflow
Mode Group
ISS Promotion
Check Quote Item
Sub Process
ISS
Promotion
Workflow
Quote Interactive
Flow
Product Promotions
732
5 Add a Start step to the workflow.
Workflow Step:
Output Arguments:
7 Add a connector from the Start step to the Query Quote step.
Workflow Step:
Name
Display
Name In/Out Business Object Data Type
Root Account Id Root Account
Id
In/Out Quote String
Active Document
Id
Active
Document Id
In Quote String
Integration Id Integration Id In Quote String
Name Operation
Business
Component
Query Quote Query Quote
Expression
Business
Component
Filter
Business
Compone
nt Type Search Specification
Quote Quote Expression '([Id] = "' + [&Active Document Id] + '")'
Property Name Type
Business
Compone
nt Name Business Component Field
Component
Quote Root Account Id
9 Add a connector from the Query Quote step to the Query Quote Line Item step.
10 Add an End step to the workflow.
11 Add a connector from the Query Quote Line Item step to the End step.
To modify the I SS Promotion Add To Promotion Process workflow
2 Query for the ISS Promotion Add To Promotion Process workflow and revise the workflow.
5 Add a Decision Point step called Is Target Document = Order?.
6 Add connectors from the Edit Product Asset step to the Is Target Document = Order? step and
from the Is Invoked from Asset? step to the Is Target Document = Order? step.
Name Operation
Business
Component
Query Quote Line Item Query Quote Item (Simple)
Expression
Business
Component
Filter
Business
Quote Item
(Simple)
Quote Item
(Simple)
Expression '([Asset Integration Id] = "' + [&Integration
Id] + '") AND ([Action Code] <>
LookupValue
("ABO_BR_ACTION_CODE","Delete"))'
Siebel Operation
Object Id
Siebel
Operation
Object Id
None Account String
734
7 Add a Sub Process step with the following details:
Workflow Step:
Input Arguments:
Output Arguments:
8 Add a Sub Process step with the following details:
Workflow Step:
Input Arguments:
Name Subprocess Name
Check for Promotion in Quote ISS Promotion Check Quote Item Sub
Process
Integration Id Process Property Integration Id
Active Document Id Process Property Active Document Id
Property Name Type Subprocess Output
Siebel Operation Object Id Output Argument Siebel Operation
Object Id
Root Account Id Output Argument Root Account Id
Name Subprocess Name
Check for Promotion in Order ISS Promotion Check Order Item Sub
Process
Output Arguments:
9 Add a connector from the Is Target Document = Order? step to the Check for Promotion in Quote
step, and set the type of the connector as Default.
10 Add a connector from the Is Target Document = Order? step to the Check for Promotion in Order
step, set the type of the connector as Condition, and the following condition to the connector.
11 Add a Decision Point step called Add Promotion to the Document?.
12 Add connectors from the Check for Promotion in Order step to the Add Promotion to the
Document? step and from the Check for Promotion in Quote step to the Add Promotion to the
Document? step.
13 Add a connector from the Add Promotion to the Document? step to the Load Promotion Related
Assets step, and set the type of the connector as Default.
14 Add a connector from the Add Promotion to the Document? step to the Edit Promotion Asset step,
set the type of the connector as Condition, and add the following condition to the connector:
15 Add the following input argument in the Edit Promotion Related Asset step:
Integration Id Process Property Integration Id
Active Document Id Process Property Active Document Id
Property Name Type Subprocess Output
Siebel Operation Object Id Output Argument Siebel Operation
Object Id
Root Account Id Output Argument Root Account Id
Compare To Operation Object Value
Process Property All Must Match (Ignore Case) Target
Document
Order
Compare To Operation Object
Process Property Is Null Siebel Operation
Object Id
736
To modify the I SS Promotion Upgrade Process workflow
2 Query for the ISS Promotion Upgrade Process workflow and revise the workflow.
To modify the I SS Promotion Split Process workflow
2 Query for the ISS Promotion Split Process workflow and revise the workflow.
Search Specification Expression '[Root Account Id] = '
+ '"' + [&Root
Account Id] + '"'
Id
In/Out Account String
Property Name Type Business Component Name
Business Component
Field
Component
Account Master Account Id
To modify the I SS Promotion Merge SubProcess workflow
2 Query for the ISS Promotion Merge SubProcess workflow and revise the workflow.
Id
Property Name Type Business Component Name
Business Component
Field
Component
Business
Object Data Type
Id
738
Postconfiguration Tasks
1 After activating all the workflows, reload the run time events.
2 Compile all the modified objects.
3 Restart the server.
Instructions for FR 12-1XANOHD
Whenever any change is made to the field-mapping xml files make sure that they are saved as UTF-
8 encoded files. To do so, open the file in Notepad, and save it as UTF-8 by selecting UTF-8 from the
Encoding drop-down list.
Instructions for FR 12-1VR5WEW
1 Locate the file jctrls.css in the SIEBEL_HOME\eapps\public\enu\files folder.
2 Open the file and add the following two entries under the clsJLCMain section for Vertical Lines in
List Applet:
COLOR-VERTICAL-GRID-LINE: #EFEFEF;
JWIDTH-VERTICAL-GRID-LINE: 1px;
You can change the color and width for the preceding values; Hex Color code information is
available on the Internet.
Instructions for FR 12-1WVIKCQ
1 Within Siebel Tools, navigate to the LOY Program business component.
2 Add the following values:
Property Name Type
Business
Component Name Business Component Field
Component
User Property: LOY Engine Activate Field 4
Value: Point Expiry Basis Field
Field: Point Expiry Basis Field
3 Set the Calculated Value to 'Transaction Date' for the point expiry to be based on the transaction
date and not the transaction process date.
Instructions for FR 12-1WUJ5W5
1 In the Campaign Recipient business component, create a new field with the following values:
Name: Control Group Flag
Column: CTRL_GRP_FLG
2 In the Campaign business component, add a new user property called Wave Id for Control Grp
and set the value as Y.
3 Within Siebel Analytics, log into Admin Tools.
4 In the physical layer, under the S_CAMP_CON table, right-click, select Add New Object > Physical
Column.add a new column with the following values:
Column Name: CTRL_GRP_FLG
Type: varchar
Nullable: True
5 In the physical layer, navigate to Campaign Promotion, and drag the new column added to the
business model and mapping layer (to OLTP Campaign Promotion).
6 Drag the new field in the business layer to the presentation layer (under Marketing Contacts >
Campaign History (Transactional Database)). You can add this new field to any target level.
7 Add this filter to the list export format used:
"Campaign History (Transaction Database)"."CTRL_GRP_FLG" IN ('@{controlGroupFlag}{'0'}')
Instructions for FR 12-1TQTU4C
2 Create new version of the LS Clinical - DeleteNonAppVisits Process workflow.
3 Navigate to Edit mode.
4 Select the Delete Non App Visits business service.
5 In the Multivalue Property window, select Tab Input arguments.
6 Change Property Name of the Input Argument VisitTemplateDate Field as follows:
from:
Input Argument: PropertyName
740
VisitTemplateDateFieldName: OriginalTemplateDateFieldName
to:
Input Argument:PropertyName
VisitTemplateDateFieldName: VisitTemplateDateFieldName
7 Save the workflow, and then publish and activate it.
Instructions for FR 12-1YDETC0
1 Navigate to Administration - Integration > Data Map Editor.
2 Query for "Clinical Protocol Position to Region Position Map1" in Integration Object Map.
3 Navigate to the Integration Field Map applet (the lower applet).
a Within Target Field Name, query for Region Position Assignment Type.
b Delete the record.
4 Query for "Clinical Protocol Position to Site Position Map1" in Integration Object Map.
a Navigate to the Integration Field Map applet (the lower applet).
b Within Target Field Name, query for Site Position Assignment Type.
c Delete the record.
5 Query for "Clinical Site Position to Protocol Position Map1" in Integration Object Map.
b Within Target Field Name, query for Protocol Position Assignment Type.
6 Query for "Clinical Site Position to Region Position Map1" in Integration Object Map.
b Within Target Field Name, query for Region Position Assignment Type.
7 Query for "Clinical Region Position to Protocol Position Map1" in Integration Object Map.
b Within Target Field Name, query for Protocol Position Assignment Type.
8 Query for "Clinical Region Position to Site Position Map1" in Integration Object Map.
b Within Target Field Name, query for Site Position Assignment Type.
9 Within Siebel Tools, select the following workflows
Clinical Assign Position From Protocol
Clinical Assign Position From Region Rolldown
Clinical Assign Position From Region
Clinical Assign Position From Site Rollup
Workflow Name: Clinical Assign Position From Protocol
Workflow Step: Query Protocol Position
Workflow Step Input/Output Arguments: Search Spec
Workflow Name: Clinical Assign Position From Region Rolldown
Workflow Step: Query Region Position
Workflow Step Input/Output Arguments: SearchSpec
Workflow Name: Clinical Assign Position From Region
Workflow Step: Query Region Position
New/
Modified? Value/Search Specification (Old)
Value/Search Specification
(New)
Modified [Clinical Protocol_Position.Sales Rep]
=' + '"' + [&SalesRep] + '"' + ' AND
[Clinical Protocol_Position.Protocol
Position Assignment Type] <> "Region
Position Rollup" AND [Clinical
Protocol_Position.Protocol Position
Assignment Type] <> "Site Position
Rollup" AND [Clinical
Protocol_Position.Position Id] =' + '"'
+ [&PositionId] +
'"'[Clinical Protocol_Position.Sales
Rep] =' + '"' + [&SalesRep] + '"' +
' AND [Clinical
Protocol_Position.Position Id] =' +
'"' + [&PositionId] + '"'
New/
Modified? Value/Search Specification (Old)
(New)
Modified [Clinical Region_Position.Sales Rep] ='
+ '"' + [&SalesRep] + '"' + ' AND
[Clinical Region_Position.Region
Position Assignment Type] <> "Protocol
Position Rolldown" AND [Clinical
Region_Position.Region Position
Assignment Type] <> "Site Position
Rollup" AND [Clinical
Region_Position.Position Id] =' + '"' +
[&PositionId] +
'"'[Clinical Region_Position.Sales
Rep] =' + '"' + [&SalesRep] + '"'
+ ' AND [Clinical
Region_Position.Position Id] =' +
'"' + [&PositionId] + '"'
742
Workflow Name: Clinical Assign Position From Site Rollup
Workflow Step: Query Site Position
10 Once you have performed the changes detailed in the preceding tables, publish and activate them
within Administration - Business Process > Repository Workflows.
Instructions for FR 12-1WWY5P4
The following tables contain information about how to implement this fix.
New/
Modified?
(Old) Value/Search Specification (New)
Modified [Clinical Region_Position.Sales
Rep] =' + '"' + [&SalesRep] + '"'
+ ' AND [Clinical
Assignment Type] <> "Protocol
Position Rolldown" AND [Clinical
Assignment Type] <> "Site
Position Rollup" AND [Clinical
Region_Position.Position Id] =' +
'"' + [&PositionId] +
'"'[Clinical Region_Position.Sales Rep]
=' + '"' + [&SalesRep] + '"' + ' AND
[Clinical Region_Position.Position Id]
=' + '"' + [&PositionId] + '"
New/
Modified Value/Search Specification (Old)
(New)
Modified [Clinical Protocol Site_Position.Sales
Rep] =' + '"' + [&SalesRep] + '"' + '
AND [Clinical Protocol
Site_Position.Site Position Assignment
Type] <> "Protocol Position Rolldown"
Site_Position.Site Position Assignment
Type] <> "Region Position Rolldown"
Site_Position.Position Id] =' + '"' +
[&PositionId] +
'"'[Clinical Protocol
Site_Position.Sales Rep] =' + '"' +
[&SalesRep] + '"' + ' AND [Clinical
Protocol Site_Position.Position Id]
=' + '"' + [&PositionId] + '"'
LS Pharma My Sample Lots List Business Component
Fields
Join
New/
Modified Search Specification (Old) Search Specification (New)
Modified [Is Product Allocation Type] = 'Y'
AND [Is Stock Employee Id -
Owned by Id] = 'Y' AND [Is Stop
Sampling Active Period Flag] = 'Y'
AND [Is Lot Product Type] = 'Y'
AND [Is Lot Stock] = 'Y' AND
[Inventory Audit Report Id] IS
NULL
[Is Product Allocation Type] = 'Y' AND
[Owned By Id] = LoginId() AND [Stop
Sampling Flag] =
LookupValue("BOOLEAN_VALUE","N") AND
(([Active Flag] = LookupValue
("BOOLEAN_VALUE","Y") and [Is Stock
Employee Id - Owned by Id] = 'Y' AND [Is
Lot Product Type] = 'Y' AND [Is Lot Stock] =
'Y' AND [Inventory Audit Report Id] IS NULL)
OR (([Inventory Flag] = 'N' OR [Inventory
Flag] IS NULL) AND ([Lot Flag] = 'N' OR [Lot
Flag] IS NULL)))
New/Modified? Name Join Column
New Inventory Flag Parent Sample INVENTORY_FLG
New Lot Flag Parent Sample LOT_ACTIVE_FLG
New Inventory Id S_STOCK_EMP ROW_ID
New/Modified? Name
Outer Join Flag
(Old)
Outer Join Flag
(New)
Modified S_STK_PERD_EMP N Y
Modified S_STOCK_EMP N Y
744
LS Pharma My Promotional Items List Business Component
Fields
Join
Instructions for FR 12-1X1S0P0
1 Log into Siebel Tools, and navigate to Object Explorer.
2 Query for the Clinical Subject project, and lock it.
3 Within Object Explorer, navigate to the Business Component tab, query for the Visit Plan Aux
business component, and lock it.
4 Query for the Priority field, and change the join and column to S_EVT_ACT_LSX and
S_PRRTY_SEQ.
5 Compile the SRF.
New/
Modified? Search Specification (Old) Search Specification (New)
Modified [Is Product Allocation Type] =
'Y' AND [Is Stock Employee Id -
Owned by Id] = 'Y' AND [Is
Stop Sampling Active Period
Flag] = 'Y' AND ([Inventory
Audit Report Id] IS NULL)
[Is Product Allocation Type] = 'Y' AND [Owned
By Id] = LoginId() AND [Stop Sampling Flag] =
LookupValue("BOOLEAN_VALUE","N") AND
(([Active Flag] = LookupValue
("BOOLEAN_VALUE","Y") and [Is Stock
Employee Id - Owned by Id] = 'Y' AND
[Inventory Audit Report Id] IS NULL) OR
(([Inventory Flag] = 'N' OR [Inventory Flag] IS
NULL)))
New/Modified? Name Join Column
New Inventory Flag S_PROD_INT INVENTORY_FLG
New Inventory Id S_STOCK_EMP ROW_ID
New/Modified? Name
Outer Join Flag
(Old)
Outer Join Flag
(New)
Modified S_STK_PERD_EMP N Y
Modified S_STOCK_EMP N Y
Instructions for FR 12-1N1KTE0
1 Set "OverwriteConfig = yes" in siebel.ini file under
..\<Build_Folder>\Release\Windows\Server\Siebel_Enterprise_Server folder and
..\<Build_Folder>\Release\Windows\Server\Siebel_Enterprise_Server\%Language% folder (in
both the siebel.ini file)
2 Append the following files in the same siebel.ini file, but in the
..\<Build_Folder>\Release\Windows\Server\Siebel_Enterprise_Server folder only.
NOTE: Add the new entries under [DeleteFiles.Windows], [DeleteFiles.Unix] and
[DeleteFiles.Unix.HP-UX].
3 Under the [DeleteFiles.Windows] in the siebel.ini file, append the following entry:
File%Number% = $(SiebelRoot)\siebsrvr\WEBMASTER\files\%LANGUAGE%\main.css
4 Under the [DeleteFiles.Unix] in the siebel.ini file append the following entry:
File%Number% = $(SiebelRoot)/siebsrvr/WEBMASTER/files/%LANGUAGE%/main.css
5 Under the [DeleteFiles.Unix.HP-UX] in the siebel.ini file, append the following entry:
File%Number% = $(SiebelRoot)/siebsrvr/WEBMASTER/files/%LANGUAGE%/main.css
NOTE: Replace %Number% and %Language% with the proper values.
To highlight list columns
1 Navigate to Site Map > Application - Data Administration > LOV Explorer.
2 Add the APPLET_HIGHLIGHT_CONTROL_TYPE LOV type within the List of Values-Type screen.
3 Navigate to Site Map > Application - Data Administration > List of Values.
4 Add a translation for the List Columns control type with the following values:
Type: APPLET_HIGHLIGHT_CONTROL_TYPE
Display Value: List Columns
Language-Independent Code: List Column
NOTE: This value must be List Column and not List Columns.
Language Name: English-American
Order: 1
Active: Checked
5 Log out and log back into the Siebel application.
Instructions for FR 12-1TK6TMD
To use the CIAI functionality (CIAI_UPPER) on the Mobile Web Client, set the
WATCOM_CIAI_FUNC = CIAI_UPPER parameter under [Siebel] section in the corresponding
application .cfg file (such as uagent.cfg, fins.cfg, and so on) on the Mobile Web Client after
reextracting the mobile user.
746
Instructions for FR 12-1Y90LL6
Set the ReportEngineType System Preference parameter to "ACTUATE".
Instructions for FR 12-1XIE4NT
Copy the RTF file from (Client installed location) > TEMP > XMLP to (Client installed location) >
XMLP > TEMP folder.
Instructions for FR 12-1X1AJME
Lock the Siebel Universal Agent and Siebel Sales Enterprise projects and compile the SRF.
Instructions for FR 12-1SG6W3F
Make sure that the search spec format for Primary IO or Secondary IO is
[IntegrationComponentName.FiledName] = 'ValueToBeTested',
Instructions for FR 12-1WLU29Y
1 Within the Siebel application, navigate to Tools > User Preference > User Profile > Time Zone
field, and note the time zone information.
2 Within Microsoft Outlook, navigate to Tools > Options, click Calendar Options, and click the Time
Zone tab.
3 Change the Time Zone information to make it the same as the Time Zone information in the
Siebel application.
4 Make a note of when the change from Standard Time to Daylight Savings Time (DST) occurs for
the current year.
5 Navigate to Administration - Data >Time Zone Administration view, and query for the time zone.
6 Modify the DST Start Ordinal, DST Start Day, DST Start Month, DST Start Time, DST End Ordinal,
DST End Day, DST End Month, and DST End Time fields in accordance with the current years
DST time change.
For example, using 2009 as the year, DST started on March 8 at 2 A.M. and ended on November
1 at 2 A.M. In this example, the values would be DST Start Ordinal=Second, DST Start
Day=Sunday, DST Start Month=March, DST Start Time=120, DST End Ordinal=First, DST End
Day=Sunday, DST End Month=November, DST End Time=120.
7 Bounce the services.
Instructions for FR 12-1YCX6CX
NOTE: Customers who have installed AIA2.0.1 must import and apply the schema changes provided
in the SIF file mentioned below.
The S_PRO_CFG_ITEM.sif file contains changes to the S_PRO_CFG_ITEM table.
NOTE: This file is located within the REPPATCH folder within your Siebel Tools installation folder.
1 Within Siebel Tools, navigate to the Table Promotions project, and lock it.
2 Use the Import from Archive function to read the S_PRO_CFG_ITEM.sif file and create the tables
in the repository. Use the Merge option when creating this file.
3 Within Siebel Tools, query for the list of tables that were imported into the repository by entering
the following values into the Apply Schema dialog box:
a Select Current Query from the Tables drop-down list.
b Enter your database information.
c Enter your database user password.
d Enter your ODBC data source information.
e Click Apply.
Instructions for FR 12-1XCMB0W
To implement the fix for this issue, apply the ACR480.zip file. This file is packaged within the
<Siebel Tools installation>\REPPATCH folder.
Instructions for FR 12-1WYEK8I
1 Within Siebel Tools, navigate to Workflow Process - Configurator, and query for the
ConfiguratorWebChannelBegin workflow.
2 Within the ConfiguratorWebChannelBegin workflow, insert the following two steps between the
ABO Enabled? and Extract Instance steps:
3 Add a decision step with the following values:
Name: Operation is LOAD
Parent Name: ConfiguratorWebChannelBeginConfig
NOTE: By default, the parent name is the same as the workflow name.
4 Make the No condition the default condition, and connect the Operation is Load step to the
Extract Instance step.
5 For the Yes condition, connect the Operation is LOAD step to the Load EAI step.
6 Add a Yes condition with the following values:
Compare To: Process Property
Object: InitInstance Operation
Operation: One Must Match (Ignore Case)
Values: LOAD
7 Add a Business Service step with the following values:
Name: LoadEAI
Business Service Method: LoadEAI
748
Business Service Name: Configurator Web Service
Parent Name: ConfiguratorWebChannelBeginConfig
NOTE: By default, the parent name is the same as the workflow name.
8 Add a connector to the No path of the previous decision step, Operation is LOAD.
9 Change the name of the Need Save? step to Need Save & not ABO?
10 Make the default value No, and the condition Save.
11 Add the following information to the existing Save condition:
Object: ABOFlag
Operation: None Can Match (Ignore Case)
Values: Y
12 Change the name of the Save Instance? step to Save & not ABO?, and set the following values:
Default: N
Condition: Y
13 Add to the following information to the existing Y condition:
Input Arguments
Input Argument Type Value Property Name
HeaderId Process Property HeaderId
InstanceCollectionName Process Property InstanceCollectionName
IntegrationObjectName Process Property IntegrationObjectName
RootId Process Property RootId
SearchSpec Expression '[Header.Id] = ' + '"' +
[&HeaderId] + '"' + '
AND [Line Item.Root
Id] = ' + '"' +
[&RootId] +
'"'
Output Arguments
Property Name Type Output Argument
Instance Output Argument SetInstanceInput
Object: ABOFlag
Operation: None Can Match (Ignore Case)
Values: Y
14 Change the name of the Is ABO? step to Is ABO & Save?, and set the following conditions:
Default: N
Condition: Yes
15 Add the following information to the existing Y condition:
Object: SaveInstanceFlag
Operation: All Must Match (Ignore Case)
Values: Y
Instructions for FR 12-1NQ7VRO
Changes for the CG SVP Product Baseline-Aux business component:
You can also create a custom column and can configure for aggregation of this custom column.
Use the following information to create a custom column for the CG SVP Product Baseline-Aux:
Business Component User
Properties Value Comments
Build Tree 3 Incremental Cases This property should already
exist
Build Tree Include Cat
Aggregation Info
Y Add this property if it does not
already exist
Category Aggregation Field 1 "Promotion Incremental Qty",
"Incremental Cases
Add this property if it does not
already exist
Build Tree n Target Field
In this case, "CalcTestStorage
Cases"
n is the next number of this
('Build Tree') property.
Users need to add this for the
new custom column.
750
Note the following information:
The "Source Field" value listed in the preceding table is a custom field in the "CG SVP Product
Baseline - Aux" business component and represents the value that the user wants to roll up.
The "Target Field" value listed in the preceding table is a custom field in the "CG SVP Product
Baseline - Aux" business component and is the field into which the rolled up value will be stored.
This should be a physical column of the table.
Instructions for FR 12-1VMB721 and FR 12-1X0C0IZ
NOTE: Make sure that the newly added user property and fields are added to the Admin Mobile,
especially if Business Component user properties have been defined for that Business Component in
Mobile Admin.
Schema Changes
Table: S_INVC_PAYMENT (Modified)
Columns:
Table: S_SRC_PAYMENT (Modified)
Columns:
Business Components
Name: FS Invoice
Build Tree Include Cat
Aggregation Info
Y Add this column if it does not
already exist.
Category Aggregation Field n "Source Field", "Target Field"
In this case, "CalcTest",
"CalcTestStorage Cases"
n is the next number of this
('Category Aggregation Field')
property.
Users need to add this value for
the new custom column.
New? Name User Name Default Physical Type Nullable Length Required
New? Name User Name Default Physical Type Nullable Length Required
New? Name User Name Default
Physic
al Type
Nullabl
e Length Required
Yes VOID_FLG Void Flag N Charact
er
No 1 Yes
Description:. Add a user property, which will be used to void the invoice and copy the fields.
BC User Property:
Name: FS Invoice Line Items
Description:. Add a user property, which will be used to void the invoice and copy the fields.
BC User Property:
Name: FS Invoice Line Item Details
New? Name Details
No FS Invoice
Name Details
Void Copy Field1 Account Id,N
Void Copy Field2 Type Code,N
Void Copy Field3 Total Amount,N
Void Copy Field4 Order Id,N
Void Copy Field5 Total Paid,N
Void Copy Field6 Order Number,Y
Void Copy Field7 Account Name,Y
Void Copy Field8 Price List,Y
Void Copy Field9 Price List Id,Y
Void Copy Field10 Tax List Id,Y
New? Name Details
No FS Invoice Line Items
Name Details
Void Copy Field1 Amount,N
Void Copy Field2 Invoice Id,N
Void Copy Field3 Line Number,N
Void Copy Field4 Order Id,N
752
Description: Add a user property, which will be used to void the invoice and copy the fields.
Name: FS Invoice Payments
Description: Add a flag for the voided status of these payments.
New? Name Details
No FS Invoice Line Item Details
Field:
New? Name Details
No Order Item Id Pick Map:
Field: Quantity
Picklist Field: Quantity
Inactive: T
Inactivate this pick map
BC User Property:
Name Details
Name Details
Void Copy Field1 Order Item Id,N
Void Copy Field2 Quantity,N
Void Copy Field3 Amount,N
Void Copy Field4 Product Name,Y
Void Copy Field5 Part Number,Y
Void Copy Field6 Product Status Code,Y
Void Copy Field7 Product Id,N
Void Copy Field8 Extended Tax,Y
Void Copy Field9 Extended Price,Y
Void Copy Field10 Total Price,Y
Void Copy Field11 CG Account Product,Y
New? Name Details
No FS Invoice Payments Table: S_INVC_PAYMENT
Name: CS HH FS Payments
Description: Add a flag for the voided status of these payments.
Applets
Name: SIS HH FS Invoice Form Applet - CE
Business Component: FS Invoice
Description: Enable the existing Void button.
Field:
New? Name Details
Yes Void Flag Column: VOID_FLG
Pre Default : N
Required :Y
Type:DTYPE_BOOL
New Name Details
No CS HH FS Payments Table: S_SRC_PAYMENT
Field:
New? Name? Details
Yes Void Flag Column: VOID_FLG
Pre Default: N
Required: Y
Type: DTYPE_BOOL
New? Name Details
No SIS HH FS Invoice Form Applet - CE
Column:
New? Name Details
No VoidInvoice Enable: Y
Minibutton
754
Name: CG Invoice Payments List Applet - CE
Business Component: FS Invoice Payments
Description: Add the newly added Void flag.
Name: HH CG Payment Entry Applet CE
Business Component: CS HH FS Payments
Description: Make the Apply to Invoice and Payment Total fields read-only.
Name: CS CG Invoice Form Applet
Business Component: FS Invoice
Description: Add the Void flag.
New? Name Details
No SIS HH FS Invoice Form Applet - CE
List Columns:
New? Name Details
Yes Void Flag Column: Void Flag
Runtime = Y
New? Name Details
No HH CG Payment Entry Applet CE
List Columns: Name Details
No NewAmount Caption: Apply To Invoice
Field: New Amount
ReadOnly =T
No Amount Caption: Payment Total
Field: Amount
ReadOnly: T
New? Name Details
No CS CG Invoice Form Applet
Name: CS CG Invoice Payments List Applet
Business Component: FS Invoice Payments
Description: Add the Void flag.
Name: HH CG Undeposited Payment List Applet CE
Description: Change the search specification of the applet.
Name: CS HH Invoice Pymt Reconcile List Applet - CE
Column:
New? Name Details
Yes Void Flag Type: CheckBox
Field: Void Flag
ReadOnly:T
New? Name Details
No CS CG Invoice Payments List
Applet
List Columns:
New? Name Details
Yes Void Flag Type: CheckBox
Field: Void Flag
ReadOnly:T
New? Name Details
No HH CG Undeposited
Payment List Applet CE
Search Specification : ([Void Flag] <> 'Y') AND ([Deposited Flag]
<> 'Y') AND ([Payment Method] <> LookupValue
("PAYMENT_METHOD_CODE", "Credit Memo") OR [Payment
Method] IS NULL)
756
Description: Change the search specification of the applet.
NOTE: Please add the Void flag wherever necessary. It is present in all Invoice and Payment Business
Components, so it can be added to any applets based on these Business Components as required.
Instructions for FR 12-1YOLHXJ
Add the UTCCanonicalFlag="Y" flag in the property set.
Instructions for FR 12-1TUEA6P
Use the following procedure to implement this fix:
1 Log into Siebel Tools, and within Object Explorer, navigate to Applet.
2 Select Search Advanced Search and lock the applet.
3 Add "FromDate" and "ToDate" user properties for the applet and enter valid date as values. The
date format should be mm/dd/yyyy.
4 Compile your changes to the repository.
Instructions for FR 12-1TK8BL1
Use the following procedure to implement this fix.
1 Within Siebel Tools, search for the "UMF Passive Message Virtual BusComp" Business Component.
2 Create a new field with the following values:
Name = Sequence
Text Length = 10
Type = DTYPE_TEXT
3 Compile the "UMF Passive Message Virtual BusComp" Business Component.
4 Apply the SRF.
Instructions for FR 12-1R3SFV9
Use the following instructions to implement this fix.
Add the following parameter under the eai_enu section in eapps.cfg file to make the fix work:
SWSENoSessInPref= true
New? Name Details
No CG Invoice Payments List Applet - CE Search Specification : [Created By] = LoginId ()
AND [Created] = Today () AND ([Void Flag] <> 'Y'
Instructions for FR 12-1U5UH3L
1 Log into the Mobile Client and launch Siebel Tools.
2 Lock the Order Entry project.
3 Navigate to Business component and query for the Order Item XA Business Component.
4 Navigate to Field and create a new field with the following values:
Name: "Attribute Id - Merged"
Calculated: Yes
Calculated Value: IIF([Attribute Id] IS NOT NULL, [Attribute Id], [Attribute Definition Id])
Force Active: No
5 Navigate to Applet and query for - Order Item XA List Applet.
6 Navigate to List > List Column, and create a new list column with the following values:
Name: Attribute Id - Merged
Field: Attribute Id - Merged
Display Name: Attribute Definition Id
Display Name String Reference: SBL_ATTRIBUTE_DEFINITION_ID-1009091646-1IT
7 Navigate to Applet Web Template, query for Edit List, right-click, and select Edit Web Layout.
8 Add Attribute Definition Id in the applet and change the field name to Attribute Id - Merged.
9 Compile the SRF.
Instructions for FR 12-1U0DJZN
1 Launch Siebel Tools, and lock the Quote and Order entry projects.
2 Query for the Business Component - Quote Item Business Component.
3 Navigate to Business Component User Props, and add a new entry with the following values:
Name: On Field Update Set 60
Value: "Unit Price", "Cfg State Code", "IIf ([Cfg State Code] =
LookupValue('CFG_ITEM_STATE_CD', 'Engine Picked Item'),
LookupValue('CFG_ITEM_STATE_CD', 'User Requested Item'), [Cfg State Code])"
4 Query for the Order Entry - Line Items Business Component, and add an entry with the same
values as listed in Step 3.
5 Compile the changes and restart the application.
758
Instructions for FR 12-1U0D4B3
Please note the following information that applies to indexing:
You must recreate the Business Component source in SES and reindex all Search categories in
the Siebel application.
Make sure that the Category names are unique when they are pointing to the same Business
Component across different definitions (such as Call Center, Sales, and so forth).
Within Siebel Tools, make sure that the Category Name field exists for the Search Results Body
Business Component. If it does not, add the Category Name field named Search Results Body
Business Component.
When users click the Refresh button after category in Search Index Settings, all other categories
(across all definitions) that point to the same Business Component will also be refreshed.
Refresh and incremental indexing will be performed only on the already-indexed categories.
The <link> tag for every Business Component in the field mappings file has been modified.
FR 12-1U0D4B3 fixes multiple categories on the same Business Component as well as other
known issues with refreshing or incremental indexing.
Use the Solution Business Component for indexing, and not the Solution Admin Business
Component.
You must add a new Business Service user property with Name=Solution Admin and
Value=Solution under the Content Service Business Service. This property is not already
available within the application. This instruction also applies to other Business Component pairs
like Solution and Solution Admin. For example, records could be modified only in the Admin BC
but drill-downs search results could be set to a view that corresponds to a non-Admin Business
Componentn. Adding the new user property in the Business Service will make sure that:
The Solution Business Component can be indexed.
If records are modified in Solution Admin Business Component, the index will be refreshed/
incremented with the changes.
Drill-down search results will be correct.
If you want to index the Solution Admin Business Component and not the Solution Business
Component, it is not necessary to add the new user property mentioned above. The view name
for that index category should be set to the Solution Admin Business Component view.
If indexing is done on Solution Admin and the view name that is used is for the Solution Business
Component, the search results will not be correct.
In search results, the Data Source column displays the Category Name and not the Business
Component name.
Instructions for FR 12-1V417JN
To access information about how to address this issue, from within My Oracle Support, search for
Instructions for FR 12-1V3K6BX
2 Within Object Explorer, navigate to Project, query for LS Clinical Protocol Site, and lock the
project.
3 Within Object Explorer, navigate to Business Component, query for the Clinical Trip Report
Business Component, and lock the object.
4 Click Multi Value Link, and for the Clinical Attendee Static multi-value link, select True for the No
Copy option.
5 Compile the selected object.
Instructions for FR 12-1UVNYZX
1 Log into Siebel Tools, and lock the LS Clinical Protocol Site project.
2 For the LS Clinical Site Visits Business Object, create a new Business Object Component with the
following values:
Business Component: Clinical Attendee Static
Link: Clinical Trip Report/Clinical Attendee Static
3 For the Clinical Protocol Site Business Object, create a new Business Object Component with the
following values:
Business Component: Clinical Attendee Static
Link: Clinical Trip Report/Clinical Attendee Static
4 Compile the locked/changed project.
Instructions for FR 12-1T2SVQ5
1 Within Siebel Tools, navigate to Business Object, and create a new record called FINS Approval
Stage.
2 Add the existing FINS Approval Stage Business Component as the primary Business Component.
3 Add the existing Contact Business Component. No link is needed.
4 Compile the new Business Object into the SRF and unlock the VEAI FINS Approval project.
5 Bounce the server.
Instructions for FR 12-1QK0UEL
1 Navigate to Administration Application > System Preferences, and add a new system preference
System Preference Name: Append Template to Email Body
System Preference Value: 1
760
[ Description: Value=1, Append template to email body; Value=0, Replace email body
with template ]
NOTE: If the New button on the System Preference applet is disabled, navigate to the System
Preference object within Business Components in Siebel Tools and uncheck the 'No Insert' option.
2 If System Preference Name is Read-Only, perform the following steps:
a Navigate to Tools/Applet and query for System Preferences Applet'.
b Right-click on the record , select 'Edit Web layout', and then change 'System Preference Name'
Read Only field to FALSE in Property Window.
3 Bounce the Siebel Server.
Instructions for FR 12-1TK4BEP
Add the following parameter under the eai_enu section in the eapps.cfg file:
SWSENoSessInPref=True
Instructions for FR 12-1N1Q81D
1 Query for "Correspondence Template Pick Applet" in the Applet Objects.
2 Edit the Search Specification property for this applet as [SalesFileExt]='doc' OR
[SalesFileExt]='lwp' OR [SalesFileExt]='LWP' OR [SalesFileExt]='DOC' OR
[SalesFileExt]='DOCX' OR [SalesFileExt]='docx'
3 Compile the srf.
Instructions for FR 12-1N1RDOP
Use the following procedures to implement this fix.
To set up workflows
1 Within Siebel Tools, select Workflow Process Object in OBLE.
2 Right-click, select Import Workflow Process, and import SIS OM Get Future Asset
SubProcess.xml.
3 Click Deploy to change the workflow status from In Progress to Complete.
If you are connected to the server data source, the completed workflow process is
available to be activated.
If you are connected to the local data source, check in the workflow process in order to
be able to activate it at run time.
To activate the SI S OM Get Future Asset Sub Process
1 Within the Siebel application, navigate to Site Map > Administration Business Process >
Workflow Deployment.
2 Query for SIS OM Get Future Asset SubProcess.
3 Select this record and click the Activate button.
4 Verify that SIS OM Get Future Asset SubProcess appears in the child applet with Deployment
Status = Active.
To set up the signal
1 Within the Siebel application, navigate to Site Map > Administration Order Management >
Signals.
2 Click New, and enter ABOGetFutureAsset as the signal name.
3 Drill down on Workspace Version in the child applet.
4 Verify that the middle applet is the Action view tab, click New, and enter the following values:
a Sequence = 1
b Service Type = Workflow
c Service Name = SIS OM Get Future Asset SubProcess
d Service Method = RunProcess
e Active = Checked
5 Navigate to the previous view by clicking Signals in the top view tab.
6 Select the record that you created in Step 2 and click the Release New Version button.
7 Select Menu > Clear Cache, and then log out of the application.
Instructions for FR 12-1P5O4RM
1 Log in to SES, and navigate to the Global Settings screen.
2 Click Clustering Configuration, and within the screen, check the Enable Clustering check box.
Instructions for FR 12-1Q35LZW
1 Navigate to the location in which you have installed the Mobile Web Client, navigate to
siebsrvr\XMLP\TEMPLATES, and open MOBUSRSUM.xsl.
762
2 Search for the following section:
TIP: Search for keyword= "Mobile User Name" to find the section.
<fo:table-cell padding-start="0.0pt" vertical-align="top" border-bottom="0.5pt solid
#c0c0c0" border-end-color="#c0c0c0" padding-top="0.0pt" border-end-style="solid"
border-start-color="#c0c0c0" padding-end="0.0pt" number-columns-spanned="3" border-
top="0.5pt solid #c0c0c0" border-start-style="solid" height="0.0pt" border-end-
width="0.5pt" padding-bottom="0.0pt" border-start-width="0.5pt" background-
color="#72a1c8">
<fo:block xdofo:in-table="1" orphans="2" widows="2" linefeed-treatment="preserve" text-
align="start" padding-bottom="0.0pt" end-indent="0.0pt" padding-top="0.0pt" start-
indent="3.6pt">
<fo:inline font-size="9.0pt" white-space-collapse="false" height="9.0pt" font-
family="Arial" font-weight="bold">Mobile User Name</fo:inline>
</fo:block>
</fo:table-cell>
color="#72a1c8">
indent="3.6pt">
family="Arial" font-weight="bold"></fo:inline>
</fo:block>
</fo:table-cell>
color="#72a1c8">
indent="3.6pt"
3 Replace the section with the following section:
color="#72a1c8">
indent="3.6pt">
family="Arial" font-weight="bold">Mobile User Name</fo:inline>
</fo:block>
</fo:table-cell>
color="#72a1c8">
indent="3.6pt">
764
4 Search for the following section:
TIP: Search for keyword=ssRouteGroupName.
width="0.5pt" padding-bottom="0.0pt" border-start-width="0.5pt">
<fo:block xdofo:in-table="1" xdofo:xliff-note="ssFirstNameX" orphans="2" widows="2"
linefeed-treatment="preserve" text-align="start" padding-bottom="0.0pt" end-
indent="0.0pt" padding-top="0.0pt" height="0.0pt" start-indent="3.6pt">
family="Arial">
<xsl:value-of select=".//ssFirstNamex" xdofo:field-name="ssFirstNamex"/>
</fo:inline>
</fo:block>
</fo:table-cell>
<fo:block xdofo:in-table="1" xdofo:xliff-note="ssRouteGroupName" orphans="2"
widows="2" linefeed-treatment="preserve" text-align="start" padding-bottom="0.0pt" end-
family="Arial">
<xsl:value-of select=".//ssRouteGroupName" xdofo:field-name="ssRouteGroupName"/>
5 Replace the section with the following section:
<fo:block xdofo:in-table="1" xdofo:xliff-note="ssFirstNameX" orphans="2" widows="2"
linefeed-treatment="preserve" text-align="start" padding-bottom="0.0pt" end-
family="Arial">
<xsl:value-of select=".//ssFirstNamex" xdofo:field-name="ssFirstNamex"/>
6 Log into the Mobile Web Client again.
Instructions for FR 12-1QNF55C
1 Within Siebel Tools, navigate to the Treatment Allocation Business Component.
2 Create the following fields:
Allocated Count (based on the ALLOCATED_CNT column)
Allocated Pct (based on the ALLOCATED_PCT column)
Control Group Pct (based on the CTRL_GRP_PCT column)
Instructions for FR 12-1QYI9VW
1 Within the Siebel Loyalty application, navigate to Site Map > Administration - BIP Reports >
Report Template Registration.
2 In the Report Name field, query for Loyalty Voucher*.
The Loyalty Voucher Cancellation Statement and Loyalty Voucher Issue Statement rows will
appear.
3 For each of the records do the following:
a In the Template column, click and browse for the saved .rtf file (packaged with the build), select
the corresponding .rtf file and save the record.
b Click the 'Generate Xliff' button.
Instructions for FR 12-1QYI9WB
1 Within Siebel Tools, navigate to the LOY Terms Business Component.
2 Within the LOY Terms BC, change the Calculated Value of the IsNotPrePaid' field to: IIF([Billing
Type] = LookUpValue("LOY_PRT_BILL_CD","Pre Paid"), "N","Y")
3 Within the Billing Type fields pickmap, change 'PickList Field' from 'Name' to 'Value'.
Instructions for FR 12-1RAJ7W8
1 Within Siebel Tools, query for the SIS OM Base Architecture project, and lock it.
2 Query for the SIS OM PMT Service Business Service.
3 Navigate to Business Service User Props and add a new field with the following values:
Name: strSetCfgStateCodeOnExplode
Value: Y
766
4 Add another new field with the following values:
Name: strCfgStateCodeOnExplodeValue
Value: User Requested Item (This value has to be a LanguageIndependentCode from the
values of LOV CFG_ITEM_STATE_CD.)
Instructions for FR 12-1RAJ8OH
1 Within Siebel Tools, lock the ISS Authoring Admin project.
2 In Object Explorer, select the Business Service object.
3 In the Business Services list, query for the ISS Authoring Import Export Service BS.
4 Navigate to View > Options > Object Explorer.
5 Uncheck and recheck the Business Service object and click OK.
6 From Object Explorer, expand the Business Service object, and select Business Service User Prop
from the list.
7 Select ISS Authoring Import Export Service from the Business Services applet on the right-
hand side.
8 Within the Business Service User Prop applet, add a new record with the following values:
Name = AutoProceed
Value = Y
9 Navigate to Tools > Compile Projects, select ISS Authoring Admin from the Projects list, and
select the Selected projects option if it is not already selected.
10 Make a backup copy of your existing siebel.srf (or siebel_sia.srf) file.
11 Browse to locate the original copy of siebel.srf (or siebel_sia.srf) at siebel\objects\enu\, and
make sure that this file is not being used by any application, because if it is being used,
compilation will fail.
12 Click Compile to compile your changes into a new .srf.
Instructions for FR 12-1RIPN17
1 Within the application, navigate to Administration Data Validation > Validation Message, and
create a validation message with the following values:
Message Code: 333
Message Label: Quote
Message Source: Quote
Message Text: Account is not null
2 Navigate to Administration Data Validation > Rule Set, and create a rule set with the following
values:
Name: MS
Business Component: Quote
Expression: [Account] IS NOT NULL
Message to display: Account is not null
ReturnCode: 333
Immediate Display = True
NOTE: The rule has Immediate Display set to TRUE which means that the message defined will
display if the expression evaluates to FALSE
3 Navigate to Administration Run Time Events > Action Sets, and create an action set with the
following values:
Name: Quote
Action Type: BusService
Business Service Name: Data Validation Manager
Business Service Method: Validate
Business Service Context: "Rule Set Name", "MS", "Enable Log", "Y"
Object Type: Bus Comp
Object Name: Quote
Event: PreWriteRecord
4 Reload the run time event from the header applet.
5 Log into to Siebel Web Server or launch the Siebel Web Client by connecting to the same
database to which the Siebel Server is connected.
6 From the Site Map, navigate to Administration > Run Time Events.
7 Click New on the top list applet to create a new action set with the following values:
Name: Set Catalog Id
Active: Checked
Enable Export: Checked
8 Click the New button on the middle list applet to create a new record with the following values:
Name: Set Catalog Id
Action Type: Attribute Set
Sequence: 1
Active: Checked
9 On the bottom form applet, set the following values:
Profile Attribute: StoredCatalogId
Set Operator: Set
768
Value: [Id]
10 Within the Administration Runtime Events tab, click the Events tab.
11 Click New on the list applet to create a new event with the following values:
Sequence: 1
Object Type: Applet
Object Name: Quote Catalog List Applet
Event: PreInvokeMethod
Subevent: PSPExecute
Action Set Name: Set Catalog Id
NOTE: This is the name of the action set created in Step 7.
12 Restart the Siebel server.
Instructions for FR 12-1S7PQRR
Use the following procedure to edit the Webtemplate file "CCAppletSearchFind.swt" to replace the
line <swe:form htmlAttr="onsubmit='SubmitFind(); return false;'"> with <swe:form
htmlAttr="onsubmit='return false;'">.
1 Connect to Siebel Tools, and select Commands in the Object Explorer.
2 Query for the "OpenSearch" command.
3 Change the Business Service from Invoke Search to Search Client Service.
4 Query for the ToggleSearch command and change the Business Service from Invoke Search to
Search Client Service.
5 Compile the changes to the srf.
Instructions for FR 12-1OVTT1V
1 Within the application, create a rule set with the following values:
Name: Account Validation
Business Component: Account
Business Object: Account
Expression: [Account Status] IS NOT NULL
Message to display: Account Status is null
2 Create an action set with the following values:
Action Type: Invoke Method
Method Name: ValidateAccountStatus
3 Create an event with the following values:
Object Type: Applet
Object Name: Account Pick Applet
Event: PreInvokeMethod
SubEvent: PickRecord
4 Within Siebel Tools, navigate to the Account Business Component, and add a user property with
[Name] = Named Method <number>
[Value] = "ValidateAccountStatus", "INVOKESVC", "Account", "Data Validation Manager",
"Validate", "'Rule Set Name'", "'Account Validation'", "'Active Object'", "'N'", "'BusObj'",
"'Account'", "'BusComp'", "'Account'", "'Enable Log'", "'Y'", "'Object Id'", "[Id]",
"'Component Id'", "[Id]"
NOTE: The first parameter of the [Value] should be same as the method given in 'Method Name'
of Action Set ('ValidateAccountStatus' in this case). The parameter after 'Rule Set Name' should
be the name of the Rule Set created ('Account Validation' in this case).
5 Compile the srf and start the application again.
Instructions for FR 12-1S2FFRD
1 Within Siebel Tools, navigate to Object Explorer > Class, and add a record with the following
values:
Name: CSSSegmentUpdateTreeService
Project: Segmentation
DLL: SSDBMSV
Object Type: Service
Super Class: CSSService
High Interactivity: 1
2 Navigate to Object Explorer > Business Service, and create a record with the following values:
Name: Mktg Segment Update Tree
Project: Segmentation
Class: CSSSegmentUpdateTreeService
State Management Type: Stateful
3 Navigate to Object Explorer > Business Service > Business Service Method, and create a record
called UpdateSegmentTreeTable.
Instructions for FR 12-1S5BJ6K
Use the following procedures to implement this fix:
770
Siebel Tools Changes
1 In Siebel Tools > Business Service, query for the LOY Processing Engine Business Service, and
add a new Business Service User Property with the following details:
Name: Cancelled Transaction BusComp Name
Value: LOY Cancelled Transaction
2 Query for the LOY Interactive Processing Engine Business Service, and add a new Business
Service User Property with the following details:
Name: Cancelled Transaction BusComp Name
Value: LOY Cancelled Transaction
3 Query for the LOY Cancelled Transaction Business Component, and add two new fields with the
following details:
Name: Amount
Type: DTYPE_NUMBER
Column: AMT_VAL
Name: Override Price Flag
Type: DTYPE_BOOL
Text Length: 1
Column: OVR_PRI_FLAG
4 Query for the 'LOY Corporate Transaction Business Component, and add two new fields with the
following details:
Name: Original Amount
Type: DTYPE_NUMBER
Column: ORIG_AMOUNT
Name: Original Points
Type: DTYPE_INTEGER
Column: ORIG_POINTS
5 Compile the above changes to your .srf file and restart the application.
Siebel Loyalty Application Changes
1 Lauch the Siebel Loyalty application, navigate to Loyalty Program Administration, drill down on
the program, query for Name = "Admin - Cancellation" within the Promotions tab, and deactivate
this promotion.
2 Drill down on the promotion number, add a new rule with an Appropriate name (such as: Invoke
Cancel Action Rule 1), ensure that this rule is the first rule under the promotion, and choose
Apply to = "Transactions".
3 Drill down on the rule name that you just created, and under Criteria Setup, enter the following
criteria:
Name: Check Txn Type
Type of Comparison: Compare to Values
Object: Transaction
Attribute: Transaction Type
Condition: Equals
Value: Redemption
Name: Check Override Price Flag
Type of Comparison: Compare to Values
Object: Transaction
Attribute: Override Price Flag
Condition: Equals
Value: Y
4 Under the "Actions" tab, create an action with the following values:
Name: Redeem Points
Type: Redeem Points
5 Leave the other existing rule under the Promotion tab unchanged and activate the promotion.
Instructions for FR 12-1SPXSIK
1 Log into Siebel Tools and query for the Assignment Rule Business Component.
2 Drill down to the Rule Type Code field.
3 Open the Properties window, copy the value of the Post Default Value property, and then set the
value to empty for this property.
4 Paste the copied value to the "Pre Default Value" property.
Instructions for FR 12-1SSUPF2
1 Within Siebel Tools, query for the Assignment Group-IO integration object.
2 Drill down to Integration Object User Property.
772
3 Query for the Csv Import By EAI user property, and add this property if it does not exist.
4 Set the value of this user property to FALSE.
Instructions for FR 12-1SSUPOB
1 Log into Siebel Tools, and query for the Skill Applet or Position-Skills-SkillItems applets.
2 Lock both applets.
3 Select Control in the applet, and query for the ImportSkillData control.
4 Delete the ImportSkillData control for both the Skill and the Position-Skills-SkillItems applets.
Instructions for FR 12-1SSCJTW
1 Log into Siebel Tools, query for the Synergy project, and lock it.
2 Query for a symbolic string with the following values: Name=SBL_ASG_*_POPUP and
Project=Synergy
3 Add a new record with the the following values:
Name: SBL_ASG_IMPORT_POPUP
Current String Value: Import Popup
Project: Synergy
Type: Conversion
Definition: Display as title for Import Popup Applet through which use initiates Import
Process
Translate: Check on
4 Query for applets with Project=Synergy.
5 Select the Position Skill Import Popup Applet record.
6 Modify the Position Skill Import Popup Applet as follows:
Title: Import Popup
Title - String Reference: SBL_ASG_IMPORT_POPUP
Comments: Display Popup to get Import file name and description for the Import Activity
Title - String Override: Remove the existing string.
Instructions for FR 12-1RB07UI
1 Import the EMR_UI.zip file located in the siebsrvr\bin directory.
2 Launch the dedicated client with the /editseeddata option.
3 Navigate to Application Admistration > Views.
4 Add a view called "Communication Detail View" with the following responsibilities:
Call Center Administrator
eMail Response Agent
eMail Response Manager
Call Center Manager
Test Siebel Administrator
Instructions for FR 12-1TSQ0BX
1 Within Siebel Tools, navigate to the SIA CS ADL Product Distribution List Applet > SIA CS Retail
Product - Authorized Distribution Business Component.
2 Change the fields used by these existing list columns of the applet:
a Change the Org Product Delist Date" field to "Delist Date".
b Change the Org Product Listing Date field to Listing Date.
Instructions for FR 12-1RVOKIA
Within Siebel Tools, navigate to the ABO Bulk Request Processing Service Business Service, and
add the following Business Service user property:
Name: BulkRequest BatchValidate Violation List
Value: Max Cardinality Violation = Y
Instructions for FR 12-1SJ56TJ
1 In File > Page Setup, select Print Background Colors and Images.
2 In Tools > Internet Options > Advanced > Printing, select Print Background Colors and Images.
Instructions for FR 12-1SJO29Z
1 Within Siebel Tools, check out the following projects:
BC [LS Pharma Response]
Link [LS Pharma Campaign Offer/LS Pharma Response]
774
Link [LS Pharma Campaign Offer/LS Pharma Response No Activity]
2 Make backup copies of these three projects.
3 Select Tools > Import from Archive.
4 Navigate to Tools\reppatch\FR_12-1SJO29Z.sif and import the .sif file.
NOTE: It is very important that you make sure to override the object definition in the repository.
5 If the objects have been customized before, compare the relevant object with the corresponding
archive created in Step 2 and use the shuttle arrow to import the customizations.
6 Compile the modified BC and the two modified links
7 Log into the application to test these changes.
Instructions for FR 12-1R75OOH
1 Log into Siebel Tools, and lock the LS Pharma Samples project.
2 Import the sif files located in the REPPATCH\SampleMgmt811DataMigrationQF.zip file
3 Publish the workflow.
4 Compile the srf.
Instructions for FR 12-1T7D8JJ
1 Within Siebel Tools, reate the LOY Merge Transaction Business Component.
2 Add the LOY Merge Transaction Business Component to LOY Member Business Object.
Instructions for FR 12-1R7NHCI
1 Log into Siebel Tools, and navigate to the LOY Engine Member Tier Business Component.
2 Change the value of the 'LOY Queue Manager user property SearchSpec: Batch' to [Active] = 'Y'
AND ([Process Date] IS NULL OR ([Member Last Txn Date] > [Process Date] AND ([Next
Assessment Date] IS NULL OR [Next Assessment Date] <= Timestamp())) OR [Tier End Date] <
Timestamp() OR ([Qual Period End Date] IS NOT NULL AND [Qual Period End Date] <
Timestamp()))
Instructions for FR 12-1QNF549
Use the following procedures to implement this fix:
To implement the mutual exclusion flag
1 Within Siebel Tools, in the S_SRC table, create a new column to capture the Mutual Exclusion
Option. The new column should be VARCHAR of size 1.
2 In the Campaign BC, create a new field called Mutually Exclusive Segment based on this column.
The type should be DTYPE_BOOL and the 'Force Active' property must be set to 'true'.
3 In the Campaign Execution Options Form Applet-Manager applet, create new control (type:
checkbox) for the mutual exclusion flag based on the Mutually Exclusive Segment field of the BC.
To pass the CPR contect during update count
1 Create new columns in the S_CALL_LST table for treatment channel, organization name, and
product name. (All these columns have type as VARCHAR and length 30.)
2 Create a new LOV type for treatment channel, and create new values for the required treatment
channel types (Email, fax and web).
3 Create a new picklist based on this LOV.
4 In the Mktg Campaign Segment Definition' BC, create the following user properties:
Field CPR Count: Set the value to the number of CPR fields that need to be implemented
Field CPR Field: 1 with value treatmentChannel
Field CPR Field: 2 with value organizationName
Field CPR Field: 3 with value productName
5 Create the following fields:
treatmentChannel: Set the Picklist value to the new picklist created.
organizationName: Use an appropriate picklist (such as Organization PickList).
productName: Use an appropriate picklist.
6 Create pick maps for these fields. If the field is based on LOV, then in the pickmap, 'Picklist Field'
should be 'value'.
7 In the Mktg Campaign Segment Definition List Applet, under list, create new list columns for
treatment channel, organization name and product name. For organization name and product
name, associate appropriate pick applets.
8 In the getCounts integration object, create new integration components called
segmentationOptions and govRules.
a In segmentationOptions, create IC fields named 'cachOverride', 'countOverride',
'removeCacheHits' and 'samplingFactor'. Set the IC field user properties and IC user properties.
b In govRules, create fields called 'name' and 'value' and set IC field user properties and IC user
properties.
9 In the Segments/Lists BC, create the CPR fields based on the corresponding columns in
S_CALL_LST table (same as in the Mktg Campaign Segment Definition BC but here there is no
need to associate pickmaps and picklists).
treatmentChannel
primaryOrganizationName
productName
776
10 In the Segments/Lists BC create the user properties for CPR fields (same as in the Mktg
Campaign Segment Definition business component).
Field CPR Count: Set the value to the number of CPR fields that need to be implemented.
Field CPR Field: 1 with value treatmentChannel
Field CPR Field: 2 with value organizationName
Field CPR Field: 3 with value productName
To configure more CPR fields
To configure more CPR fields, set the user property 'Field CPR Count' to the required value, create
new user properties 'Field CPR Field: n' with value as the new field name, corresponding new fields
in the Mktg Campaign Segment Definition BC, and the required number of columns in S_CALL_LST
table.
For example, to configure one more CPR field (such as organization) in addition to the ones
mentioned above, change the Field CPR Count user property to '4'. Create a new user property called
Field CPR Field: 4 and set the value as organization. Create a new business component field called
organization and associate a picklist or LOV as needed. Create a new column in S_CALL_LST for this
field with type as VARCHAR and length '30'. Create a list control in the Mktg Campaign Segment
Definition List Applet.
To make changes in load format
Add the following filter to the load format used:
'@{constrainingStageFlag}{N}' = 'N' OR "Campaign Contact"."Load Wave Id" IN
(@{constrainingWaveID}{'0'})
AND RANK(Contact.ROW_WID) <= @{allocationLimit_High}{1000000} AND
RANK(Contact.ROW_WID) >= @{allocationLimit_Low}{1000000}
This filter is needed only in case of mutual exclusion. In case of campaign load without mutual
exclusion, the original load format as mentioned in bookshelf can be used.
Note the following information about lower and higherlimits for allocation within BI Publisher: When
Update Count is done from Campaign > Design > Allocation, a job.xml file will be created on the BI
side as part of the fix. When loading the campaign, lower and higher limits for allocation will be
present in the xml file created on the BI side when mutual exclusion is selected.
Instructions for FR 12-1RBZC49
1 Within Siebel Tools, query for the Action BC.
2 Within Object Explorer, cliick on BC User Property and create new record with the following
values:
Name: Done Flag Status Update
Value: N
Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA Oracle Welcomes Your
Comments
3 Compile the srf and launch the application.
Instructions for FR 12-1T03IPL
In order to implement this fix, you need to install ACR 452. For information about how to implement
ACR 452, see the Siebel Search Administration Guide on the Siebel Bookshelf at http://
Oracle Welcomes Your Comments
To help us improve our products, we want to know about any corrections or clarifications to this guide
that you would find useful. Please include in your message:
The title and version of the guide (very important)
The name and version number of the Siebel application you are using
Your name, job title or functional area, company name, phone number, and email address
Contact us through regular mail or email at:
Oracle
Siebel Technical Publications Department
500 Oracle Parkway
Redwood Shores, CA 94065
Siebeldoc_ww@oracle.com
We appreciate your feedback.
Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA Oracle Welcomes Your
Comments
778

MR Guide 811x Rev AA

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MR Guide 811x Rev AA

Uploaded by

Copyright:

Available Formats

Siebel Maintenance

You might also like