Vous êtes sur la page 1sur 732

Siebel Maintenance Release

Guide, Version 8.1.1.x, Rev. P

January 2011
This guide includes the following topics:

■ What’s New in This Revision on page 8

■ Quick Fixes Included in 8.1.1.x Fix Packs on page 11

■ Enhancements and Updates in 8.1.1.x Fix Packs on page 32

■ Configuration Instructions for Enhancements and Updates on page 39

■ Siebel Fix Pack Installation Instructions on page 441

■ Resolved Change Requests on page 462

■ Oracle Welcomes Your Comments on page 738

Release Notes for the Siebel 8.1.1.4 Fix


Pack
The following section contains information about known issues with this Fix Pack and any available
workaround information.

Dmutl2.exe Changes to Read-Only After Database Initialization


Category: Remote

Subcategory: DB Init

Product Version: 8.1.1.4

Change Request: 12-1Y3OYFP

The dmutl2.exe file becomes read-only after database initialization.

Use the following workaround if you already have the Mobile Web Client installed.

1 Install the 8.1.1.4 Fix Pack.

2 Before you run dbxtract and dbinit, empty the mwc_8114> folder. For example, empty
C:\Siebel\<mwc_8114>\UPGRADE.

3 Run dbxtract and dbinit.

The dmutl2.exe file becomes writable.

NOTE: You only need to empty the folder once.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ What’s New in This
Revision

ADM Deployment Fails on AIX


Category: Application Deployment Manager

Subcategory: Framework

Product Version: 8.1.1.4

Change Request: 12-210GXT7

Use the following workaround to address this issue:

1 Make sure that 8.1.1.4 'Management Server' uses JRE1.6.

2 Make sure that 8.1.1.4 'Management Agent' uses JRE1.5.


3 After applying the 8.1.1.4, patch bring down all the services, the Gateway Server, Siebel Server,
and the agent.

4 Get the workaround 'classes.tar' file from


8.1.1.4SIA[21225]\Release\AIX\Server\Siebel_Enterprise_Server and copy it to a temporary
location on your enterprise machine.

5 Execute the copyjar.ksh file as shown below (hence it can replace the respective jar files):

copyjar.ksh </siebel_root>

copyjar.ksh /export/home/qa1/21225/ses

Once it executes successfully, it will display the copied info on the console.

6 Restart all services and continue with deployments.

What’s New in This Revision


Table 1 describes the changes in this version of the documentation.

Table 1. What’s New in Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P

Topic Description

“Instructions for ACR 475” Revised this section.

“Release Notes for the Siebel 8.1.1.4 Fix Added information about CR 12-1Y3OYFP.
Pack” on page 7

“Instructions for ACR 500” on page 318 Added information about two known issues with ACR 500,
and workaround information for these issues.

“Release Notes for the Siebel 8.1.1.4 Fix Added this section to describe known issues with the
Pack” on page 7 8.1.1.4 release. (Rev.O)

“Configuration Instructions for Updated these sections for the 8.1.1.4 GA release. (Rev.
Enhancements and Updates” O)

“Resolved Change Requests”

8 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ What’s New in This
Revision

Table 1. What’s New in Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P

Topic Description

“Configuration Instructions for Added a note to indicate that customers only need to
Enhancements and Updates” perform the configuration changes if they are
implementing the ACRs. (Rev. N)

“Quick Fixes Included in 8.1.1.x Fix Updated these sections for the Siebel 8.1.1.4 Fix Pack
Packs” prerelease. (Rev. N)

“Configuration Instructions for


Enhancements and Updates”

“Resolved Change Requests”

“Instructions for ACR 474 and ACR 508” Added two workflows. (Rev. M)

“Instructions for ACR 474 and ACR 508” Added crucial “known issues” information and made a few
corrections in the procedures. (Rev. L)

“Enhancements and Updates in Version Added information about ACR 467 and how to configure
8.1.1.1” it. (Rev. K)

“Instructions for ACR 467”

“Resolved Change Requests in the


Siebel 8.1.1.1 Fix Pack”

“Configuration Instructions for Revised configuration instructions for ACR 500 to include
Enhancements and Updates” procedures for importing seed data. (Rev. K)

“Enhancements and Updates in 8.1.1.x Updated these sections for the Siebel 8.1.1.3 Fix Pack
Fix Packs” release. (Rev. J)

“Configuration Instructions for


Enhancements and Updates”

“Resolved Change Requests”

“Quick Fixes Included in 8.1.1.x Fix Updated these sections for the Siebel 8.1.1.3 Fix Pack
Packs” prerelease. (Rev. I)

“Enhancements and Updates in 8.1.1.x


Fix Packs”

“Resolved Change Requests”

“Resolved Change Requests” Removed FR 12-1UHQ1L9. This FR was not provided in


the Siebel 8.1.1.2 Fix Pack.

“Resolved Change Requests” Removed reference to FR 12-1VM75R7. This fix was not
provided in the 8.1.1.2 Fix Pack. (Rev. H)

“Resolved Change Requests” Removed reference to FR 12-1VE6WMU. This fix was not
provided in the 8.1.1.2 Fix Pack. (Rev. H)

“Instructions for ACR 480” Added instructions for importing seed data associated
with this enhancement. (Rev. H)

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ What’s New in This
Revision

Table 1. What’s New in Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P

Topic Description

“Resolved Change Requests” Corrected configuration instructions for FR 12-1QK0UEL.


(Rev. H)

“Resolved Change Requests” Corrected link to configuration instructions for FR 12-


1SPXSHM. (Rev. H)

“Resolved Change Requests” Corrected Fix Request ID for providing support for
Internet Explorer 8 on Windows Vista. (Rev. H)

How to Use This Guide


This document, Siebel Maintenance Release Guide, Version 8.1.1.x, lists the enhancements and fixes
provided in version 8.1.1.x releases of Oracle’s Siebel Business Applications.

This guide also provides information, instructions, and guidelines for installing Siebel Business
Applications Siebel Fix Pack 8.1.1.x releases on top of version 8.1.1 or a prior 8.1.1.x release.

Use this Siebel Maintenance Release Guide in conjunction with Siebel Bookshelf documents,
particularly the Siebel Installation Guide for the operating system you are using.

NOTE: This Siebel Maintenance Release Guide is updated to include the latest Siebel Fix Pack 8.1.1.x
release. The latest Siebel Fix Pack 8.1.1.x release available at publication time is Siebel Fix Pack
8.1.1.3. 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:

■ OracleMetaLink 3 (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 how to install the maintenance
release (Fix Pack release). It also contains the most current information on product configuration
issues and workarounds for your application. Note that 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
OracleMetaLink 3 with questions regarding the applicability of Siebel Maintenance Release Guide
items to your deployment.

Additional Documentation
Oracle reserves the right to modify the documentation for Siebel Business Applications at any time.

For related Siebel documentation, see OracleMetaLink 3 (https://support.oracle.com) and Bookshelf


for Oracle’s Siebel Business Applications Version 8.1 (http://www.oracle.com/technology/
documentation/siebel.html) on Oracle Technology Network (OTN).

10 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Quick Fixes Included in 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.

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 Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version 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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 11


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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-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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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

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 8.1.1.4


[21112_10]

12-1YOKGG5 12-1Z04TF7 8.1.1 PDA [21112_11] 8.1.1 PDA 8.1.1.4


[21112_11]

12-1YOK96H 12-1YOK97J 8.1.1 PDA [21112_8] 8.1.1 PDA 8.1.1.4


[21112_8]

12-1YOKK66 12-1YOKK9R 8.1.1 PDA [21112_8] 8.1.1 PDA 8.1.1.4


[21112_8]

12-1YOMS7P 12-1YOMS8H 8.1.1 PDA [21112_9] 8.1.1 PDA 8.1.1.4


[21112_9]

12-1JFQEZ6 12-1Z9RYA5 8.1.1 PDA [21112_9] 8.1.1 PDA 8.1.1.4


[21112_9]

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 13


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

12-1YGT6Q9 12-1YOMSAP 8.1.1 PDA [21112_9] 8.1.1 PDA 8.1.1.4


[21112_9]

12-1Z3IMD9 12-1Z3I799 8.1.1 PDA [21112_9] 8.1.1 PDA 8.1.1.4


[21112_9]

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

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

14 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 15


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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

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

16 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 17


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

12-1YAH4TL 12-1YBWHO9 8.1.1.2 [21215] QF0284 8.1.1.4

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 8.1.1.4


[21215_5]

12-1YOMS7P 12-1YV5IMZ 8.1.1.2 WM5 [21215_5] 8.1.1.2 WM 5 8.1.1.4


[21215_5]

18 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

12-1Z6VW9H 12-1Z6VWA6 8.1.1.2 WM5 [21215_6] 8.1.1.2 WM 5 8.1.1.4


[21215_6]

12-1JFQEZ6 12-1Y28CXL 8.1.1.2 WM5 [21215_5] 8.1.1.2 WM 5 8.1.1.4


[21215_5]

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

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 19


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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-1HCLBH7 12-1XYTSLP 8.1.1.3 [21219] QF304 8.1.1.4

12-1YOKK4N 12-1Z520FN 8.1.1.3 WM5 [21219_2] 8.1.1.3 WM5 8.1.1.4


[21219_2]

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

12-1VMBL0Z 12-1WXXCZJ 8.1.1 [21112] QF0096 8.1.1.3

20 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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

12-1LC1A2Z 12-1WF6BOH 8.1.1 [21112] QF0099 QF0099 8.1.1.3

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 21


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

12-1U5VI4H 12-1UH8O67 8.1.1 PDA [21112_1] 8.1.1 PDA 8.1.1.3


[21112_1]

12-1VR6T39 12-1VR6T42 8.1.1 PDA [21112_4] 8.1.1 PDA 8.1.1.3


_21112_4]

12-1VMBHFJ 12-1VMBHGE 8.1.1 PDA [21112_5] 8.1.1 PDA 8.1.1.3


[21112_5]

12-1VM6HI1 12-1WS4HGD 8.1.1 PDA [21112_6] 8.1.1 PDA 8.1.1.3


[21112_6]

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

12-1WF6PMP 12-1WK5MQ5 8.1.1.1 [21211] QF0161 8.1.1.3

22 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 23


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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

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

24 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 25


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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

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

26 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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

12-1VR4BVB 12-1VR5ATP 8.1.1.2 WM5 [21215_1] 8.1.1.2 8.1.1.3


[21215_1]

12-1V6XL7R 12-1V7WKHX 8.1.1.2 WM5 [21215_1] 8.1.1.2 WM5 8.1.1.3


[21215_1]

12-1VNJH0Z 12-1VNJH1R 8.1.1.2 WM5 [21215_1] 8.1.1.2 WM5 8.1.1.3


[21215_1]

12-1WCP7ZT 12-1WCP80M 8.1.1.2 WM5 [21215_1] 8.1.1.2 WM5 8.1.1.3


[21215_1]

12-1X1S03V 12-1X1GML7 8.1.1.2 WM5 [21215_2] 8.1.1.2 WM5 8.1.1.3


_21215_2]

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 27


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

12-1VNJY1R 12-1VR6P9H 8.1.1.2 WM5 [21215_3] 8.1.1.2 WM5 8.1.1.3


[21215_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

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

28 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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

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 8.1.1.2


[21112_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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 29


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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

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

30 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Quick Fixes Included in
8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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


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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 31


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Enhancements and
Updates in 8.1.1.x Fix Packs

Table 2. Quick Fixes Included in Version 8.1.1.x

Change Fix Request Quick Fix Merged Into


Request ID ID Fix Pack Base Version Fix Pack

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

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 in 8.1.1.x Fix Pack releases are cumulative. This topic contains the following
subtopics:

■ “Enhancements and Updates in Version 8.1.1.4” on page 32

■ “Enhancements and Updates in Version 8.1.1.3” on page 33

■ “Enhancements and Updates in Version 8.1.1.2” on page 35

■ “Enhancements and Updates in Version 8.1.1.1” on page 36

Enhancements and Updates in Version 8.1.1.4


Table 3 lists the enhancements and updates provided in 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.

ACR 475B Enhances UCM to provide Data Governance, Data Quality, and
usability enhancements.

32 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Enhancements and
Updates in 8.1.1.x Fix Packs

Table 3. Enhancements and Updates in Version 8.1.1.4

Feature Enhancement
or Certification Number Feature Enhancement or Certification Description

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

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.

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.

Enhancements and Updates in Version 8.1.1.3


Table 5 lists the enhancements and updates provided in version 8.1.1.3.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 33


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Enhancements and
Updates in 8.1.1.x Fix Packs

This topic is part of “Enhancements and Updates in 8.1.1.x Fix Packs” on page 32.

Table 4. Enhancements and Updates in Version 8.1.1.3

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.

34 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Enhancements and
Updates in 8.1.1.x Fix Packs

Table 4. Enhancements and Updates in Version 8.1.1.3

Feature
Enhancement or
Certification
Number Feature Enhancement or Certification Description

ACR 474 Supports OSM Integration and he 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.

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 Enterprise Applications to Siebel
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.

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 allows 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 extends the set of


available shortcuts.

■ Added helps topics for accessibility and updates the keyboard


shortcuts help topics.

ACR 574 Provides Lymba as the Smart Answer Engine.

Enhancements and Updates in Version 8.1.1.2


Table 6 lists the enhancements and updates provided in version 8.1.1.2.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 35


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Enhancements and
Updates in 8.1.1.x Fix Packs

This topic is part of “Enhancements and Updates in 8.1.1.x Fix Packs” on page 32.

Table 5. Enhancements and Updates in Version 8.1.1.2

Feature Enhancement
or Certification Number Feature Enhancement or Certification Description

ACR 444 ACR 444 provides the following enhancements:

■ 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 468B Allows Siebel Client Sync to support Lotus Notes 8.0 and Microsoft
Outlook 2007 with Intellisync 7.x SDK.

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.

Enhancements and Updates in Version 8.1.1.1


Table 6 lists the enhancements and updates provided in version 8.1.1.1.

36 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Enhancements and
Updates in 8.1.1.x Fix Packs

This topic is part of “Enhancements and Updates in 8.1.1.x Fix Packs” on page 32.

Table 6. Enhancements and Updates in Version 8.1.1.1

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 37


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Enhancements and
Updates in 8.1.1.x Fix Packs

Table 6. Enhancements and Updates in Version 8.1.1.1

Feature Enhancement or
Certification Number Feature Enhancement or Certification Description

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.

ACR 450 ACR 450 provides the following enhancements:

■ 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

38 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Table 6. Enhancements and Updates in Version 8.1.1.1

Feature Enhancement or
Certification Number Feature Enhancement or Certification Description

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.

ACR 480 ACR 480 provides the following 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 processes.

■ Significantly enhances usability across trade management in


Siebel applications.

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.

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 39


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

You perform the instructions described in the subtopics that follow after you install the current Siebel
Fix Pack 8.1.1.x, as described in “Siebel Fix Pack Installation Instructions” on page 441.

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 41

■ “Instructions for ACR 403” on page 41


■ “Instructions for ACR 422” on page 45

■ “Instructions for ACR 426” on page 66

■ “Instructions for ACR 437” on page 89

■ “Instructions for ACR 439” on page 90

■ “Instructions for ACR 452” on page 95

■ “Instructions for ACR 456” on page 97

■ “Instructions for ACR 457” on page 99

■ “Instructions for ACR 463” on page 103

■ “Instructions for ACR 464” on page 142

■ “Instructions for ACR 467” on page 150

■ “Instructions for ACR 468” on page 157

■ “Instructions for ACR 471” on page 159

■ “Instructions for ACR 474 and ACR 508” on page 159

■ “Instructions for ACR 475” on page 230

■ “Instructions for ACR 476” on page 276

■ “Instructions for ACR 480” on page 280

■ “Instructions for ACR 488” on page 291

■ “Instructions for ACR 494” on page 291

■ “Instructions for ACR 499” on page 291

■ “Instructions for ACR 500” on page 318


■ “Instructions for ACR 502” on page 344

■ “Instructions for ACR 508” on page 356

■ “Instructions for ACR 539” on page 361

■ “Instructions for ACR 543” on page 384

■ “Instructions for ACR 562” on page 387

40 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ “Instructions for ACR 574” on page 432

■ “Instructions for ACR 623” on page 438

■ “Instructions for ACR 626” on page 438

■ “Instructions for BI Publisher Enhancements” on page 441

Instructions for ACR 358


For information about how to implement ACR 358, within My Oracle Support, navigate to the
Knowledge tab, and search for Doc ID 781368.1

Instructions for ACR 403


Use the instructions in the following section to configure ACR 403.

Preinstallation Instructions
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 APARKER 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 the following
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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 41


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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=APARKER

■ 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 APARKER and point to the local database.
6 Enter the password for APARKER (such as aparker1-2), click Continue, enter the Server password
for APARKER 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 user APARKER. In the
Additional Info column, query for RemLocSec:PlainKey.

42 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 43


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

44 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

7 Choose Edit, and then New Record, and use the following information to define the object
properties:

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 This should be set to SBL_ADMINISTRATION_-_MOBILE_SEARCH.


Reference

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://
www.oracle.com/technology/documentation/siebel.html.

Instructions for ACR 422


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:

New/ Application SIA SIF File HOR SIF File


Changed Name User Property Value Name Name

Changed Siebel Universal AccessibilityXMLF Accessibility_Callce Accessibility_Callce Accessibility_Callc


Agent ileName nter.xml nter_SIA.sif enter_HOR.sif

Changed Siebel AccessibilityXMLF Accessibility_eMark Accessibility_eMark Accessibility_eMa


eMarketing ileName eting.xml eting_SIA.sif rketing_HOR.sif

Changed Siebel eSales AccessibilityXMLF Accessibility_eSales Accessibility_eSale Accessibility_eSal


ileName .xml s_SIA.sif es_HOR.sif

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 45


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

New/ Application SIA SIF File HOR SIF File


Changed Name User Property Value Name Name

Changed Siebel eService AccessibilityXMLF Accessibility_eServi Accessibility_eServ Accessibility_eSer


ileName ce.xml ice_SIA.sif vice_HOR.sif

Changed Siebel Public AccessibilityXMLF Accessibility_Public Accessibility_Public Accessibility_Publi


Sector ileName Sector.xml Sector_SIA.sif cSector_HOR.sif

Changed Siebel Sales AccessibilityXMLF Accessibility_Sales. Accessibility_Sales Accessibility_Sale


ileName xml _SIA.sif s_HOR.sif

Changed Siebel Service AccessibilityXMLF Accessibility_Servic Accessibility_Servic Accessibility_Serv


ileName e.xml e_SIA.sif ice_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)
1 Navigate to Object Explorer in Siebel Tools.

2 Navigate to View > Options, and click the Object Explorer tab.

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:

New/ HOR SIF File


Changed Project Name Value SIA SIF File Name Name

Changed Symbolic SBL_CALCULATOR_IC Calculator SymbolicStrings_SI SymbolicStrings_H


Strings ON_ALT_TXT A.sif OR.sif

Changed Symbolic SBL_CALENDAR_ICON Calendar SymbolicStrings_SI SymbolicStrings_H


Strings _ALT_TXT A.sif OR.sif

Changed Symbolic SBL_EDIT_ICON_ALT_ Pick Applet SymbolicStrings_SI SymbolicStrings_H


Strings TXT A.sif OR.sif

a For SBL_CALCULATOR_ICON_ALT_TXT, change 'Current String Value' to 'Calculator'.

46 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

To enable screen readers to read out the MVG and Pick Applet for Calendar,
Calculator, and MVG (Bitmaps)
1 Navigate to Object Explorer in Siebel Tools.

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:

New / Bitmap Alt Text SIA SIF File HOR SIF File
Changed Category Bitmap Value Description Name Name

Changed HTML CALENDAR_ ICON Calendar Change the HTMLControlIcon HTMLControlIcon


Control Alt text from s_SIA.sif s_HOR.sif
Icons "Input" to
Calendar.

Changed HTML CALCULATOR_ICON Calculator Change the HTMLControlIcon HTMLControlIcon


Control Alt text from s_SIA.sif s_HOR.sif
Icons "Input" to
Calculator.

Changed HTML ICON_SELECT Pick Change the HTMLControlIcon HTMLControlIcon


Control Applet Alt text from s_SIA.sif s_HOR.sif
Icons "Select" to
Pick Applet.

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)


1 Navigate to Object Explorer in Siebel Tools.

2 Navigate to View > Options, and click the Object Explorer tab.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 47


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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:

New/ Current
Changed Project Name String Value SIA SIF File Name HOR SIF File Name

New Symbolic SBL_CTRL_+_ALT_+_] Ctrl + Alt + ] SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif


Strings

New Symbolic SBL_CTRL_+_ALT_+_[ Ctrl + Alt + [ SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif


Strings

New Symbolic SBL_CTRL+SHIFT+B Ctrl+Shift+B symstr_columnsdisplay symstr_columnsdisplaye


Strings ed_SIA.sif d_HOR.sif

New Symbolic SBL_CTRL+, Ctrl+, SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif


Strings

New Symbolic SBL_CTRL+. Ctrl+. SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif


Strings

New Symbolic SBL_ALT_G ALT+G SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif


Strings

New Symbolic SBL_ALT_U ALT+U SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif


Strings

New Symbolic SBL_ALT_W ALT+W SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif


Strings

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.

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 CmdNextApplet_SIA.sif
first anchor of the
next applet

PrevApplet Previous Ctrl + Alt + [ Ctrl+Alt+219 Shifts focus to the CmdPreviousApplet_SIA.sif


Applet first anchor of the
previous applet

Refine Query N/A Alt+G Alt+G N/A CmdRefineQuery_SIA.sif


(SWE)

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

48 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Table 7. Keyboard Shortcuts


Command Action Accelerator Key Sequence Description SIA SIF File Name

Columns Displayed N/A Ctrl+Shift+B Ctrl+Shift+B N/A CmdColumnsDisplayed_SIA.sif


(SWE)

NextApplet Next Applet Ctrl + Alt + ] Ctrl+Alt+221 Shifts focus to the CmdNextApplet_SIA.sif
first anchor of the
next applet

Creating Keyboard Shortcuts for Commands


Use the following procedures to provide keyboard shortcuts for commands.

To provide a keyboard shortcut for the NextApplet command


1 Navigate to Object Explorer in Siebel Tools.

2 Navigate to View > Options, and click the Object Explorer tab.

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.

3 Click the '+' sign in Object Explorer and choose 'Accelerator'.

4 In the Display Name - String Reference' field, enter the newly created Symbolic String or in the
Display Name field, enter 'Ctrl + Alt + ['.

5 In the 'Key Sequence' field, change the value to 'Ctrl+Alt+219'.

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.

3 Click the '+' 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+G'.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 49


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

3 Click the '+' 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+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.

3 Click on '+' sign in Object Explorer and choose 'Accelerator'.


4 Copy the Record Name '1'. Name the New Record '2'
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.

3 Click on '+' sign in Object Explorer and choose 'Accelerator'.

4 Copy the Record Name '2'. Name the New Record '3'.

5 In Display Name field, enter 'Ctrl+,'.

6 In the Key Sequence field, change the value to 'Ctrl+,'.

50 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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


1 Navigate to Object Explorer in Siebel Tools.

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.

New /
Changed Applet Name Title Description SIA SIF File Name HOR SIF File Name

Changed Search lookin Search Provides a title AppletSearchlookin_SIA.sif AppletSearchlookin_HOR.sif


to the applet
for screen
readers to
read out.

To add the DefaultFocus User Property


1 Navigate to Object Explorer in Siebel Tools.

2 Navigate to Applet.

3 Query for "Search lookin".

4 Navigate to Applet User Property.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 51


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

New / Applet User SIA SIF File


Changed Applet Name Property Value Description Name HOR SIF File Name

Changed Search lookin DefaultFocus SearchFor Added the user AppletSearchlo AppletSearchlookin_H
property to set the okin_SIA.sif OR.sif
default focus

Creating the View Info Command


The following procedure explains how to create the View Info command.

To create the View Info command


1 Navigate to Object Explorer in Siebel Tools.

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"

Key SIA SIF HOR SIF


Command Project Action Accelerator Sequence Description File Name File Name

View Info Command ViewInfo Ctrl + Alt + Z Ctrl + Alt A new shortcut CmdViewInf CmdViewInf
+Z key that o_SIA.sif o_HOR.sif
generates a
dialog box that
contains
ViewName, View
Summary and
Applet Names

Sub-View Tab SWE N/A Ctrl + Alt + V Ctrl +Alt N/A CmdSubVie CmdSubVie
(SWE SI) +V wTab_SIA.si wTab_HOR.s
f if

4 Add a new Accelerator to the Command for the required Key Combination with the following
values:

■ NAME="1"
■ BROWSER_PLATFORM="All"

■ DISPLAY_NAME_-_STRING_REFERENCE="SBL_DOES_NOT_MATTER-1004225828-03I"

■ INACTIVE="N"

52 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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
“Importing SIF Files” on page 61.

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 53


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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.

54 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Providing a New Key Combination for the Next and Previous Record Commands

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.

1 Navigate to Object Explorer in Siebel Tools.

2 Navigate to View > Options, and click the Object Explorer tab.

3 Select the 'Command' object and click OK to add the Command Strings object to Object Explorer.

4 Within Object Explorer, click the Command object and query for 'Previous Record(SWE)'
Command.

5 Lock the object.

6 Click the '+' sign in Object Explorer and choose 'Accelerator'.

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.


11 Click the '+' sign in Object Explorer and choose 'Accelerator'.
12 Change 'Display Name' from 'Ctrl+.' to 'Alt +.'
13 In the 'Key Sequence' field, change the value to Alt+0xBE.

Current
New/ String
Changed Project Name Value HOR SIF File Name SIA SIF File Name

New Symbolic Strings SBL_ALT+, Alt+, symbolistring_Next_Prev_H symbolistring_Next_Prev_S


OR.sif IA.sif

New Symbolic Strings SBL_ALTL+. Alt+. symbolistring_Next_Prev_H symbolistring_Next_Prev_S


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 Command Alt +, Alt+0xBC Next_Prev_HOR.sif Next_Prev_HOR.sif


Record(SWE)

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 55


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

New/ Current String


Changed Project Name Value HOR SIF File Name SIA SIF File Name

Changed Symbolic SBL__IMG_SRC__IMAGES/ <IMG orangebullet_HOR.sif orangebullet_SIA.sif


Strings CHEVRON_SM.GIF__ALIGN SRC="images/
__RIGHT__BORDER__0 orange_bullet.gif"
align="right"
border="0" alt="" >

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
about how to import .sif files, see “Importing SIF Files” on page 61.

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 Create a new string for the Control
Message

To enable or disable the confirmation message upon page refresh


1 Log into the application using /editseeddata (for thick 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:

Language
Display Independent
Type Value Translate Multilingual Code Order Language Name

SWE_CONFIRMATION TRUE Yes Yes TRUE 1 English-American


_MESSAGE

SWE_CONFIRMATION FALSE Yes Yes FALSE 2 N/A


_MESSAGE

56 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 After you have added these changes, navigate to Screen > System Administration > List Of
Values to view these changes in the repository.

New/ Business
Changed Name Project Component Static Type Field Type Value

New Confirmation User Preference PickList Generic Yes Type SWE_CONFIRM_MESSAGE


Message
Picklist

The following changes have been made to the User Preferences Business Component.

Name PickList Predefault Value Type

SWE/Confirmation Message Confirmation Message TRUE DTYPE_TEXT


Picklist

The following table describes the new User Profile Confirmation Message Parameter Applet that has
been added to support ACR 422.

New/ Business
Changed Name Project Component Class Title

New User Profile User User Preferences CSSFrameBase Accessibility


Confirmation Message Preferences
Parameter Applet

The following table describes the applet controls changes that have been implemented to support
ACR 422.

Name Caption Field HTML Type Method Invoked Runtime Field Type

Applet Title Accessibility N/A Text N/A N/A N/A

ConfirmMssg Confirmation SWE/ Text N/A Yes BC Field


Message Confirmation
Message

ExecuteQuery Go N/A MiniButtonQuery ExecuteQuery N/A N/A

NewQuery Query N/A MiniButtonEdit NewQuery N/A N/A

QueryAssistan Query N/A MiniButtonQuery ShowQueryAssistant N/A N/A


t Assistant

ResetRecord Reset N/A MiniButton ResetRecord N/A N/A

SaveEditRecor Save N/A MiniButtonEditNe ExplicitWriteRecord N/A N/A


d w

UndoQuery Cancel N/A MiniButtonQuery UndoQuery N/A N/A

WebEditTitle Accessibility N/A Label N/A N/A N/A

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 57


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

The following table describes the view changes that have been added to support ACR 422.

Visibility Applet
New/Changed Name Project Business Object Type

New User Profile User Preferences User Preferences User Profile


Confirmation Message Confirmation Message
Parameter View Parameter Applet

The following table describes the User Profile screen changes that have been added to support ACR
422.

New/Changed Name View Type Visibility Applet Type

New User Profile User Profile Aggregate View User Profile Confirmation
Confirmation Message Confirmation Message Message Parameter Applet
Parameter View Parameter View

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.

Web
New/Changed Name Project Template SIF File

New PUB Disease PUB HLS Bio Edit Disease_Case_SIA.sif


Case List Applet Terrorism

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
1 Navigate to Object Explorer in Siebel Tools.

2 Navigate to View > Options, and click the Object Explorer tab.

58 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 Select the 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 select 'New Record'.

6 Add the new records mentioned in the following table.

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

To implement the NextPage and PreviousPage commands


1 Navigate to Object Explorer in Siebel Tools.

2 Navigate to View > Options, and click the Object Explorer tab.

3 Select the 'Command' object and click OK to add the Command Strings object to Object Explorer.

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:

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

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'.
12 For 'Browser Platform' - Extended, in 'Display Name - String Reference', provide the newly
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'.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 59


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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

Add 'Popup Query' template to the 'PUB Evidence Pick Applet' with appropriate controls
[ExecuteQuery and CancelQuery] placed on it.

60 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Importing SIF Files


The following procedure describes how to import .sif files.

To import SIF 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

Importing SIF Files for Table Changes


The procedure in the following section describes how to add the applet summary for customized or
new applets.

To import the SIF 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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 61


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

62 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Importing the Accessibility Project SIF Files


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

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

4 Add the following new LOV types and values:

Type Value

ACC_ATTRIB_TYPE Summary

ACC_ATTRIB_TYPE Label

ACC_LOCALE ENU

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 63


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ 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” control’s properties by entering “ROW_OFF” for HTML Bitmap and
“ROW_ON” for HTML Disabled Bitmap.

6 Save the applet.

64 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

7 Drag and drop the GotoPreviousSet and GotoNextSet controls to their respective placeholders,
and edit the properties using the values in the following table:

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

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:

■ Accessibility Applet Attributes

■ Accessibility View Attributes

Views:

■ Accessibility Applet Attributes View

■ Accessibility View Attributes View

Picklists:

■ Accessibility Applet Attribute PickList

■ Accessibility View Attribute PickList

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 65


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Instructions for ACR 426


This topic contains information about how to configure and install ACR 426.

Preinstallation Tasks
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

❏ Bitmap

66 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 67


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

To import all of the SIF files


NOTE: Use this 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.

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 imported 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 SIF files manually


1 Import the following new objects:

■ Import Unziplocation\ACR426\REPOSITORY\Pick List\LS Medical Picklist Product Issue eMDR


Acknowledgement RR.sif

■ Import Unziplocation\ACR426\REPOSITORY\Pick List\LS Medical Picklist Product Issue eMDR


Batch RR.sif

■ Import Unziplocation\ACR426\REPOSITORY\Pick List\LS Medical Picklist Product Issue eMDR


Status RR.sif

■ Import Unziplocation\ACR426\REPOSITORY\Pick List\LS Medical Picklist Product Issue eMDR


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

■ 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

68 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ Import Unziplocation\ACR426\REPOSITORY\Link \LS Medical Product Issue RR eMDR_LS Medical


PI Product.sif

■ Import Unziplocation\ACR426\REPOSITORY\Link \LS Medical Product Issue RR eMDR_LS 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
■ Import Unziplocation\ACR426\REPOSITORY\Integration
Object\CRMIntegSEBLSIALSClinicalFaultMessage.sif

■ Import Unziplocation\ACR426\REPOSITORY\Integration
Object\CRMIOSEBLSIALSProductIssueInternal.sif

■ Import Unziplocation\ACR426\REPOSITORY\Applet\LS Medical Product Issue RR eMDR Batch


Details List Applet.sif

■ Import Unziplocation\ACR426\REPOSITORY\Applet\LS Medical Product Issue RR eMDR Batch List


Applet.sif

■ Import Unziplocation\ACR426\REPOSITORY\Applet\LS Medical Product Issue RR eMDR Batch


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

■ Import Unziplocation\ACR426\REPOSITORY\View\LS Medical My Product Issues RR eMDR Batch


Details View.sif

■ Import Unziplocation\ACR426\REPOSITORY\View\LS Medical My Product Issues RR eMDR Report


Attachment View.sif

■ Import Unziplocation\ACR426\REPOSITORY\View\LS Medical My Product Issues RR eMDR Report


Audit View.sif

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 69


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

2 Manually add the following symbolic strings:

Screen
View

New/ Current String


Modified? Name 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

70 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 Do manual configuration for the existing "LS Medical Product Issue RR" Business Component:

Single Value
Fields

New/Needs Calculate Immediate No


Modification? Name Join Column d Value Type Post PickList Validation Copy

New Area LIC LookupNa DTYPE_TEXT


me("SR_A
REA",
[Area])

New Attach IIf DTYPE_BOOL


(Count(At
tachment)
> 0, 1, 0)

New Batch Id BATCH_I DTYPE_ID


D

New Batch eMDR BATCH_ DTYPE_TEXT Y LS Medical


Number Batch NUMBER Picklist
Product
Issue
eMDR
Batch RR

New FDA FDA_AC DTYPE_TEXT Y LS Medical


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

Modify Device >0


Age

Modify Follow- Y
Up
Number

New Follow- IIF ([Sub DTYPE_BOOL Y


Up Report
Number Type] =
Read LookupVal
Only ue("LS_M
ED_CMPL
NT_SUB_
REPORT_T
YPE","Foll
ow-up"),
"N", "Y")

New Individu IIf ([Batch DTYPE_BOOL


al Number]
Transmit IS NULL,
1, 0)

Modify Parent Y
Product
Issue
Report
Num

New Patient LookupNa DTYPE_TEXT


Sex LIC me("FIN_
GENDER",
[Patient
Sex])

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 71


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Single Value
Fields

New/Needs Calculate Immediate No


Modification? Name Join Column d Value Type Post PickList Validation Copy

New Reopen [Status]= DTYPE_TEXT


Flag 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"
)

Modify Report Y
Number

Modify Sub Y
Report
Type

Modify Type of Y
Report -
Follow-
up Flag

New Urgency IIF ( DTYPE_TEXT


Flag [eMDR
Status] =
'Transmitt
ed' AND
[eMDR
SubStatus
] <>
'Rejected'
, Green,
IIF(
(Today()
+
SystemPr
eference("
eMDR
Deadline
Threshold
Value")) <
[Report
Deadline
Date],
Yellow,
Red))

New eMDR EMDR_S DTYPE_TEXT Y LS Medical


Status TATUS_C Picklist
D Product
Issue
eMDR
Status RR

New eMDR EMDR_S DTYPE_TEXT Y LS Medical


SubStat UB_STAT Picklist
us US_CD Product
Issue
eMDR
SubStatus
RR

72 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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/Modified? Field Picklist Field

New FDA Acknowledgement Value

Pick Maps for the eMDR Status Field

New/Modified? Field Picklist Field

New eMDR Status Value

Pick Maps for the eMDR Substatus Field

New/Modified? Field Picklist 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

Destination Use
New/Needs Business Primary
Modification? Name Auto Primary Component Destination Link Join

New Attachment Default LS Medical LS Medical Product Issue RR/ Y


Product Issue LS Medical Product Issue
Attachment Attachment

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 73


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Business
Component
User Properties

New/Modified? Name Value Inactive

New Field Read Only Field: Follow-Up Number Read Only N


Follow-Up Number

New Named Method 8 "EscalatePIToeMDRQueue", "SET", "N


"RR Sub-Status",
"LookupValue('LS_MED_RR_STATUS
_CD', 'eMDR')

New Named Method 9 "Transmit", "INVOKESVC", "LS "N


Medical Product Issue RR",
"Workflow Process Manager",
"RunProcess", "'ProcessName'", "LS
CRMIntegSEBLSIAProductIssueInser
tOutboundFlow", "'RowId'", "[Id]

New Named Method 10 "Transmit", "SET", "eMDR Status", "N


"LookupValue('LS_MED_RR_TRANS_
STATUS', 'TRANSMITTED')

New Named Method 11 "Transmit", "SET", "eMDR "N


SubStatus",
"LookupValue('LS_MED_RR_TRANS_
SUB_STATUS', 'NO RESPONSE')

New Named Method 12 "UpdateeMDRStatus", "SET", "eMDR "N


Status",
"LookupValue('LS_MED_RR_TRANS_
STATUS', 'TRANSMITTED')

New Named Method 13 "UpdateeMDRStatus", "SET", "eMDR "N


SubStatus",
"LookupValue('LS_MED_RR_TRANS_
SUB_STATUS', 'NO RESPONSE')

New Named Method 14 "EscalatePIToeMDRQueue", "SET", "N


"eMDR Status", "IIf ([eMDR Status]
IS NULL,
LookupValue('LS_MED_RR_TRANS_
STATUS', 'NOT TRANSMITTED'),
[eMDR Status])

New Named Method 15 "EscalatePIToeMDRQueue", "SET", "N


"eMDR SubStatus", "IIf ([eMDR
SubStatus] IS NULL,
LookupValue('LS_MED_RR_TRANS_
SUB_STATUS', 'WORK IN
PROGRESS'), [eMDR SubStatus])

74 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Business
Component
User Properties

New/Modified? Name Value Inactive

New Named Method 16 "Transmit", "SET", "FDA """"N


Acknowledgement",

New Named Method 17 "UpdateeMDRStatus", "SET", "FDA """"N


Acknowledgement",

New On Field Update Set 3 "Sub Report Type", "Follow-Up "N


Number Read Only", "IIF ([Sub
Report Type] =
LookupValue(""LS_MED_CMPLNT_S
UB_REPORT_TYPE"",""Follow-up""),
""N"", ""Y"")

New On Field Update Set 4 "Sub Report Type", "Follow-Up "N


Number", "IIF ([Sub Report Type] =
LookupValue(""LS_MED_CMPLNT_S
UB_REPORT_TYPE"",""Initial""),
"""", [Follow-Up Number])

New On Field Update Set 5 "Type of Report - Follow-up Flag", "N


"Sub Report Type", "IIF ([Type of
Report - Follow-up Flag]='Y',
LookupValue('LS_MED_CMPLNT_SU
B_REPORT_TYPE','Follow-up'),
LookupValue('LS_MED_CMPLNT_SU
B_REPORT_TYPE','Initial'))

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 75


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

4 Perform manual configuration for the "LS Medical Product Issue" Business Component:

Single
Value
Fields

New/
Needs Calcul
Modific ated Immediate Validati
ation? Name Join Column Value Type Post PickList on No Copy

New Area Lookup DTYPE_TEXT


LIC Name("
SR_ARE
A",
[Area])

Modify FDA Y
Reporta
ble

New Patient Lookup DTYPE_TEXT


Sex LIC Name("
FIN_GE
NDER",
[Patient
Sex])

New Sub- Lookup DTYPE_TEXT


Area Name("
LIC SR_ARE
A",
[Sub-
Area])

5 Perform manual configuration for the existing "Contact" Business Component.

Single
Value
Fields

New/ Imm
Needs edia
Modificat Joi Colu Calculated te
ion? Name n mn Value Type Post PickList Validation No Copy

New Country LookupName( DTYPE_


LIC "COUNTRY",[ TEXT
Country])

76 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

6 Perform manual configuration for the existing "LS Medical Product Issue RR" Business Object:

Business Object
Component

New/Modified? Business Component Link

New Contact LS Medical Product Issue RR/


Contact

New LS Medical Product Issue RR LS Medical Product Issue RR/


eMDR Batch LS Medical Product Issue RR
eMDR Batch

7 Perform manual configuration for the existing "Audit Trail Engine" Business Service:

Business Service
User Props

New/Needs
Modification? Name Value Comment

Modify Enable TRUE 12-CBU9V3: turned


OFF on default for
performance reasons

8 Perform manual configuration for the existing "Field Value Icons" Bitmap Category:

Bitmaps

Alt Text String


New/Modified? Name FileName Reference Alt Text

New uncheck.gif uncheck.gif SBL_LS_NOT_SE Not Selected


LECTED

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 77


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

9 Perform manual configuration for the existing "LS Medical Product Issue RR Form Applet" Applet:

Control

New/ HTML
Modified? Name Caption Caption String HTML Type Only

New/Modify Name Caption Caption String HTML Type HTML Method


Only Invoked

New eMDRQueue eMDR Queue SBL_LS_EMDR_ MiniButtonEditN Y EscalatePIToeM


QUEUE ew 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: ([RR Sub-Status] <> 'eMDR'


EscalatePIToeMDRQueue OR [RR Sub-Status] IS NULL)
AND [RR Status] =
'Submitted'

78 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

10 Perform manual configuration for the existing "LS Medical Product Issue RR Child List Applet"
Applet:

List Columns

Display Name -
New/Needs String
Modification Name Field Reference Read Only HTML Icon Map

New FDA Status FDA SBL_LS_FDA_ST Y


Acknowledgeme ATUS
nt

New Flag Urgency Flag SBL_FLAG- LS_URGENCY_FLAG


1004224902-
05I

New eMDR Status eMDR Status SBL_LS_EMDR_ Y


STATUS

New eMDR SubStatus eMDR SubStatus SBL_LS_EMDR_ Y


SUB_STATUS

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 79


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Applet Web
Template Items

New/Modify Name Fields Comments

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

11 Perform manual configuration for the existing "LS Medical Product Issues RR Screen" Screen:

Screen
View

New/
Needs View Bar Text -
Modificat Category Parent String Menu Text String
ion? Name Name View Type Category Reference Reference

New LS LS Detail eMDR SBL_LS_BATCH_ SBL_LS_BATCH_AUDIT


Medical Medical View Batch AUDIT
My My
Product Produc
Issues RR t
eMDR Issues
Batch RR
Audit eMDR
View Batch
Audit
View

New LS LS Detail eMDR SBL_LS_BATCH_ SBL_LS_BATCH_DETAIL


Medical Medical View Batch DETAILS S
My My
Product Produc
Issues RR t
eMDR Issues
Batch RR
Details eMDR
View Batch
Details
View

80 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Screen
View

New/
Needs View Bar Text -
Modificat Category Parent String Menu Text String
ion? Name Name View Type Category Reference Reference

New LS LS Detail eMDR SBL_LS_REPORT SBL_LS_REPORT_ATTAC


Medical Medical View _ATTACHMENTS HMENTS
My My
Product Produc
Issues RR t
eMDR Issues
Report RR
Attachme eMDR
nt View Report
Attach
ment
View

New eMDR eMDR Aggregate SBL_LS_EMDR SBL_LS_EMDR


Category

New eMDR eMDR Aggregate SBL_LS_EMDR_B SBL_LS_EMDR_BATCH


Batch Batch Category ATCH

12 In Siebel Tools, compile all of the locked and updated projects.

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 81


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f


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

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

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:

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.

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f


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

<Tools Install Directory> - Replace with your Siebel Tools install directory

<ODBC Source Name> - Replace with the relevant ODBC name

7 Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.

82 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

XML File to Import Web Service Name Direction

LSeMDRTransmitFDS.xml LSeMDRTransmitFDA Outbound

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.

6 Log into the Siebel application.

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

XML File to Import Web Service Name Direction

LSUpdateeMDRProductIssueS LSUpdateeMDRProductIssueS Inbound


tatus.XML tatus

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 83


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

XML File to Import Workflow Name Project

LS LS LS eMDR
CRMIntegSEBLSIAProductIssueInsertOut CRMIntegSEBLSIAProductIssueIns
boundFlow.xml ertOutboundFlow

LS Siebel PI eMDR Batch.xml LS Siebel PI eMDR Batch LS eMDR

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


1 Log into the Siebel application.

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:

84 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 85


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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


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.

86 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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;Passwor
d=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>

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 87


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

java -jar EditParam.jar -i Unziplocation\ACR426\BusinessProcesses -f


Unziplocation\ACR426\Setup\CRMIntegProcessParameters.xml -verbose -t D:\temp

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.

88 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Instructions for ACR 437


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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 89


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

For information about 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, and how to set up the integration user, see Siebel CRM and UCM Integration
Guide. To access this guide, search for Doc ID 763962.1 on My Oracle Support.

Instructions for ACR 439


This topic is part of “Configuration Instructions for Enhancements and Updates” on page 39.

After installing ACR 439, you must make sure that Find objects are visible in the application.

To make sure that Find objects are visible in the application


1 Connect to Siebel Tools.

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.

To resolve the SBL-DAT-00222 error message


1 Connect to Siebel Tools.

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.

90 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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


1 Connect to Siebel Tools.

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


1 Connect to Siebel Tools.

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
1 Connect to Siebel Tools.

2 Query for the Search lookin applet.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 91


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 Navigate to Applet User Prop and add the two user properties listed in the following table:

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

4 Navigate to Control, query for Name= "Search", and update the Search property as detailed in
the following table:

Name Target View Frame Description

Search empty The old value is "_sweview".


The property needs to be set
to empty.

To add the GotoView user property to the Search Results Body applet
1 Connect to Siebel Tools.

2 Query for the Search Results Body applet.

3 Navigate to Applet User Prop and add the following user property:

Name Value Description

GotoResultsView Search lookin Results View

4 Navigate to Control, query for Name = "PositionOnRow", and update the following property:

HTML Bitmap HTML Disabled Bitmap

ROW_OFF ROW_ON

5 Navigate to Applet Web Template Items and add the item detailed below:

Item Identifier Name Control Parent Name Type

501 PositionOnRow PositionOnRow Base Control

Seed Data Changes for ACR 439B


Use the following procedure to add the Search lookin Results view.

92 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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
Place the text below between this line:

<!------------ Begin Row ------------->

and this line:

<!------------ Display all Search Result Field ------------->

Insert the following text:

<tr class="swe:this.RowStyle">

<swe:control id="501"><!-- Select 501 --><td align="swe:this.TextAlignment"


width="42" class="Row"><swe:this property="FormattedHtml" hintText="Selected Row"
hintMapType="Control"/></td></swe:control>

<swe:select-row><td align="swe:this.TextAlignment" width="42" class="Row"><swe:this


property="FormattedHtml" /></td></swe:select-row>

To edit SearchResults.swt
Place the following text after the line </b> for id ="3000":

&nbsp; &nbsp;

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 93


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

<b>

<swe:control id="3001"> <!-- CR 12-1O4OT68 -->

<swe:this property="FormattedHtml" hintMapType="Control" hintText="Attach"/>

</swe:control>

</b>

<b>

<swe:control id="3002"> <!-- CR 12-1O4OT91 -->

<swe:this property="FormattedHtml" hintMapType="Control" hintText="Preview"/>

</swe:control>

</b>

To edit SavedSearch.swt
Place the following text after the line </tr> for id="99":

<!-- Begin of CR 12-1O4OTAF -->

<tr>

<td align="left">

<swe:control id="101">

<b><swe:this property="FormattedHtml" hintMapType="Control" hintText="Field"/></b>

</swe:control>

</td>

</tr>

<tr>

<td align="left">&nbsp</td>

</tr>

<!-- End of CR 12-1O4OTAF -->

Instructions for ACR 450


For information about how to implement ACR 450, within My Oracle Support, navigate to the
Knowledge tab and search for Doc 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.

94 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Instructions for ACR 452


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>

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 95


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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


1 Open Tools.cfg, search for the SymStrPrefix parameter, and change the value of the SymStrPrefix
parameter from SBL_ to X_.

96 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Instructions for ACR 456


This topic is part of “Configuration Instructions for Enhancements and Updates” on page 39.

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 97


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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.

98 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Instructions for ACR 457


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.

This will create the following directory structure:

<Tools Install Directory>\REPPATCH\acr457\

2 In Siebel Tools, lock the following projects:

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 99


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

7 Start the Siebel Server.

8 Lock the SIS OM Base Architecture project, and import the workflows listed in the following table
into the Siebel application.

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

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.

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]

100 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Enable compgrp <Alias>

f Verify that the command executed successfully, and then run the Exit command.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 10 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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.

102 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

4 Log out and relogin in to Siebel eCommunications application.

You can now create orders.

Instructions for ACR 463


The following sections contain information about how to install and configure ACR 463.

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.

This will create the following directory structure:

<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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 10 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ EIM Product

❏ EIM Quote

❏ EIM BulkRequest

❏ EIM Organization

❏ EIM Service Request

❏ Table Asset

❏ Table BulkRequest

❏ Table Invoice

❏ Table Order

❏ Table Organization

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

104 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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


1 Create an ODBC entry for the database where you plan to import the 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.

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 10 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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

106 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ 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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 10 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 Import the rest of the SIF files from the SIFFiles folder into Siebel Tools using the Import From
Archive function.

NOTE: If you have not locked the required projects, you may receive a warning error message.

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

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

5 Stop Siebel Server, if it is running.

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.

108 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

7 Start the 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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 10 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Workflow Name Project

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


SWIValidateDependentOrders Web Service Integration

Verify Header (Order) COM Workflows

Verify Item (Order) COM Workflows

a Select Workflow Process in Siebel Tools Object Explorer.

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.

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.

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

110 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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:

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

3 Query for the following rulesets in the Validation Ruleset applet:

❏ SWI Order Validation Rule Set

❏ SWI SRL Delete

❏ SWI SRL Item

❏ SWI SRL Modify

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 11 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

■ 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

112 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ 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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 11 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ Its namespace is http://siebel.com/asi

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.

2 Navigate to the Outbound Web Services aggregate view.

3 Query for the "SWISubmitOrder" 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_SALESORDERJMSQUEUE@java:comp/resource/
CommsJmsRP1/QueueConnectionFactories/QCF)

5 Save the record and click the Clear Cache button.

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

114 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

■ Its namespace is http://siebel.com/asi

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.

2 Navigate to the Outbound Web Services aggregate view.

3 Query for the "SWICreateAdjustment" 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_CMUREQADJIOJMSQUEUE@java:comp/resource/
CommsJmsRP1/QueueConnectionFactories/QCF)

5 Save the record and click the Clear Cache button.

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)

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 11 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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
NOTE: Bounce the server after enabling the compgrp and synchronizing it.

■ Enable the following compgrps:

❏ Siebel CME [Alias- Communications]

❏ Siebel ISS [Alias- ISS]

❏ Workflow Management [Alias- Workflow]


❏ Communications Management [Alias CommMgmt]

For more information about enabling compgrps, see “Enabling Compgrps” on page 141.

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*

116 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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

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

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 11 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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]

❏ Remove = TRUE

❏ Trigger File Name: trigger.sql

4 Start the job.

5 Verify that the job was successful once it has completed.

To generate the triggers


NOTE: Make sure that the SADMIN user has the necessary privileges for generating triggers before
performing this procedure.

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]

❏ Trigger File Name: trigger.sql

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

118 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 11 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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

120 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 12 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Application Name: N/A

Mode: N/A

Instance Type: N/A

Fields: N/A

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL


Action: Y

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

Signal: QuotesAndOrdersValidate
Actions and Parameters:

Sequence: 1

Service Type: Workflow

Service Name: PSP Driver Workflow Process

Service Method: RunProcess

Application Name: N/A

Mode: Order

Instance Type: Header

Fields: N/A

Condition: N/A

Active: Y

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

Make similar changes to actions in this signal where:

122 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Mode: Order, Instance Type: Line Item

Mode: Quote, Instance Type: Header

Mode: Quote, Instance Type: Line Item

Signal: VerifyItem
Actions and Parameters:

Sequence: 1

Service Type: Workflow

Service Name: PSP Driver Workflow Process

Service Method: RunProcess

Application Name: N/A

Mode: Agreement

Instance Type: Header

Fields: N/A

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

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

Make similar changes to actions in this signal where:

Mode: Order, Instance Type: Header

Mode: Quote, Instance Type: Header

Signal: Product Recommendation Signal


Actions and Parameters:

Sequence: 1

Service Type: Workflow

Service Name: Product Recommendation Driver Workflow

Service Method: RunProcess

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 12 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Application Name: N/A

Mode: N/A

Instance Type: Line Item

Fields: N/A

Condition: GetProfileAttr('Block Variable Map Operations')='N' OR GetProfileAttr('Block Variable Map


Operations') IS NULL

Active: Y

Name Value

SubPSPPricingWFName Dynamic Pricing Procedure

VariableMap 1 Default Product Recommendation Variable


Map - Context

Signal: CalculatePriceExternal
Actions and Parameters:

Sequence: 1

Service Type: Business Service

Service Name: Pricing Manager

Service Method: RunPricerWorkflow

Application Name: N/A

Mode: N/A

Instance Type: N/A

Fields: N/A

Condition: N/A

Active: N/A

Name Value

SubPSPPricingWFName Dynamic Pricing Procedure

Signal: SpreadDiscount, SpreadDiscount - All


Actions and Parameters:

Sequence: 1

Service Type: Workflow

Service Name: Spread Discount Driver Workflow Process

124 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Service Method: RunProcess

Application Name: N/A

Mode: N/A

Instance Type: N/A

Fields: N/A

Condition: N/A

Active: Y

Name Value

SubPSPPricingWFName Dynamic Pricing Procedure

Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Spread Discount Default Pricing Variable Map - Row Set

Signal: ApproveItem
Actions and Parameters:

Sequence: 1

Service Type: Workflow

Service Name: PSP Workflow Driver Process

Service Method: RunProcess

Application Name: N/A

Mode: Agreement

Instance Type: Header

Fields: N/A

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure

Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

Make similar changes to actions in this signal where:

Mode: Order, Instance Type: Header

Mode: Quote, Instance Type: Header

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 12 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Signal: CalculatePrice
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

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure

Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

Signal: CalculatePriceAll
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: Line Item

Fields: N/A

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

126 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Active: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure

Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

Signal: CalculatePrice_eSales
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

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULLY

Name Value

SubPSPWFName Dynamic Pricing Procedure

Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

Signal: CalculatePriceAll_eSales
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: Line

Fields: N/A

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 12 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Action: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure

Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

Signal: CalculatePrice_Configurator
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

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

Name Value
SubPSPWFName Dynamic Pricing Procedure

Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

Signal: CalculatePrice_Advisor
Actions and Parameters:

Sequence: 1

Service Type: Workflow

Service Name: PSP Driver Workflow Process

Service Method: RunProcess

Application Name: N/A

Mode: N/A

128 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Instance Type: N/A

Fields: N/A

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure

Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

Signal: MergeIntoOnePackage
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: Line Item

Fields: N/A

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure

Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

Signal: OrderTemplate
Actions and Parameters:

Sequence: 1

Service Type: Workflow

Service Name: PSP Driver Workflow Process

Service Method: RunProcess

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 12 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Application Name: N/A

Mode: Order

Instance Type: Header

Fields: N/A

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure

Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

Make similar changes to actions in this signal where:

Mode: Quote, Instance Type: Header

Signal: OrderTemplateCopy
Actions and Parameters:

Sequence: 1

Service Type: Workflow

Service Name: PSP Driver Workflow Process

Service Method: RunProcess

Application Name: N/A

Mode: Order

Instance Type: Header

Fields: N/A

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure

Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

130 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Signal: OrderTemplateSelectItems
Actions and Parameters:

Sequence: 1

Service Type: Workflow

Service Name: PSP Driver Workflow Process

Service Method: RunProcess

Application Name: N/A

Mode: Order

Instance Type: Header

Fields: N/A

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure

Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

Signal: QuoteTemplateCopy
Actions and Parameters:

Sequence: 1

Service Type: Workflow

Service Name: PSP Driver Workflow Process

Service Method: RunProcess

Application Name: N/A

Mode: Quote

Instance Type: Header

Fields: N/A

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 13 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Active: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure

Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

Signal: QuoteTemplateSelectItems
Actions and Parameters:

Sequence: 1

Service Type: Workflow

Service Name: PSP Driver Workflow Process

Service Method: RunProcess

Application Name: N/A

Mode: Quote

Instance Type: Header

Fields: N/A

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure


Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

Signal: SetFieldValue
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: Header

132 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Fields: Discount; Price List; Currency Code

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure

Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

Sequence: 1

Service Type: Workflow

Service Name: PSP Driver Workflow Process

Service Method: RunProcess

Application Name: N/A

Mode: Agreement

Instance Type: Line Item

Fields: Product; Quantity Requested; Unit Price; Discount Amount; Discount Percent; Currency
Code; Item Price List; Covered Product Net Price

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure


Variable Map - Context Default Pricing Variable Map - Context
Variable Map - Row Set Default Pricing Variable Map - Row Set

Sequence: 1

Service Type: Workflow

Service Name: PSP Driver Workflow Process

Service Method: RunProcess

Application Name: N/A

Mode: Order

Instance Type: Line Item

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 13 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Fields: Product; Quantity Requested; Unit Price; Discount Amount; Discount Percent; Prod Prom
Name; Currency

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure

Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

Sequence: 1

Service Type: Workflow

Service Name: PSP Driver Workflow Process

Service Method: RunProcess

Application Name: N/A

Mode: Quote

Instance Type: Line Item

Fields: Product; Quantity Requested; Unit Price; Discount Amount; Discount Percent; Prod Prom
Name; Currency Code; Item Price List; Covered Product Net Price

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure


Variable Map - Context Default Pricing Variable Map - Context

Variable Map - Row Set Default Pricing Variable Map - Row Set

Signal: Get Config Item Price


Sequence: 1

Service Type: Workflow

Service Name: Get Config Item Price - Driver Workflow

Service Method: RunProcess

Application Name: N/A

134 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Mode: N/A

Instance Type: N/A

Fields: N/A

Condition: N/A

Active: Y

Name Value

SubPSPWFName Get Config Item Price - Dynamic

Signal: GetProdPrice
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

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

Name Value
SubPSPWFName Dynamic Pricing Procedure
Variable Map - Context Default Pricing Variable Map - Context
Variable Map - Row Set Product Pricing Variable Map - Row Set

Signal: GetUserProdPrice
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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 13 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Fields: N/A

Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL

Active: Y

Name Value

SubPSPWFName Dynamic Pricing Procedure

Variable Map - Context User Product Pricing Variable Map - Context

Variable Map - Row Set Product Pricing Variable Map - Row Set

Signal: PDS GetPricing


Sequence: 1

Service Type: Workflow

Service Name: Dynamic Pricing Procedure

Service Method: RunProcess

Application Name: N/A

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.

136 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

To execute the EIM job


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:

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 13 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

"SCE Users";"Email Address";"Account";"Account";"Contact"

or

"SCE Users";"EMail Addr";"User List";"User List";"User"

The following table describes the three run time events that are added.

Sequence Object Type Object Name Event SubEvent Action Set Name

1 BusComp Attribute VOD PreInvokeMethod SendEmail EmailNotify


BusComp

2 BusComp ISS Class VOD PreInvokeMethod SendEmail EmailNotify


BusComp

3 BusComp ISS Joint PreInvokeMethod SendEmail EmailNotify


Workspace
BusComp

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:

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

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.

138 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

The email templates detailed above are configured as user property values in the following Business
Components:

Business Component User Property Template Name

ISS Joint Workspace PackageNameList|Attribute Workspace Attribute Defn


BusComp Definition Template

ISS Joint Workspace PackageNameList|Product Workspace Product Class


BusComp Class Definition Defn Template

Attribute VOD BusComp PackageNameList Attribute Defn Template

ISS Class VOD BusComp PackageNameList Product Class 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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 13 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ SMTP Server: rgmamersmtp.oraclecorp.com

The communication profile has to set in the user property in the Business Components listed in
the following table:

Business Component User Property Template Name

ISS Joint Workspace CommProfileOverride Default SMTP Profile


BusComp

Attribute VOD BusComp CommProfileOverride Default SMTP Profile

ISS Class VOD BusComp CommProfileOverride Default SMTP Profile

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.

Name Recipient Group

Attribute Defn Template AttributeDefnBC

Product Class Template ProductClassDefnBC

Workspace Attribute Defn Template WorkSpaceBC

Workspace Product Class Defn Template WorkSpaceBC

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:

Recipient Group(LIC
Business Component User Property Value)

ISS Joint Workspace RecipientGroup ISS Joint Workspace


BusComp BusComp
Attribute VOD BusComp RecipientGroup Attribute VOD BusComp

ISS Class VOD BusComp RecipientGroup ISS Class VOD BusComp

140 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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:

srvrmgr /e SIEBEL /s sdchs21n110 /g sdchs21n110:4330 /u SADMIN /p MSSQL <enter>

6 Run the command to verify how many components are enabled as "list compgrp".

7 Run the following command to enable the components group:

Enable compgrp <Alias>

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 UNIX


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:

Enable compgrp <Alias>

6 Verify that the command ran successfully.

7 After verifying that the command ran successfully, exit the application.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 14 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Instructions for ACR 464


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 142

2 Importing Changes to the Siebel Repository from SIF Files on page 143

3 Applying Changes to the Siebel Database on page 145

4 Importing Seed Data on page 146

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:

SymStrPrefix = 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\repository\projects_to_lock.txt

■ For a Siebel Industry Application, open the following file:

ACR464-SIA8112\repository\projects_to_lock.txt

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.

142 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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 <Siebel Tools installation>\log 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:

Application\Application-Update.sif

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 14 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

■ Business Object\BusinessObject-Update.sif

■ Table\base\Table-Update.sif

■ Business Component\BusinessComponent-Update.sif

3 Examine the following log file to make sure all imports executed successfully:

Siebel\tools\temp\importlog.txt

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

6 Save the tools.cfg 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 147.

3 Do one of the following:

a If the object appears in “Changes Made as a Result of Importing SIF Files” on page 147, 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 145.

b If the object does not appear in “Changes Made as a Result of Importing SIF Files” on page 147,
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 145.

144 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

c If the object appears in “Changes Made as a Result of Importing SIF Files” on page 147, and if
there is a conflict, then create a service request (SR) on OracleMetaLink 3.

For more information, see “Example of a Conflict That Requires Additional Assistance” on
page 145.

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

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:

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 14 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

S_EVT_ACT OR S_PIM_INT_PKG OR S_PIM_INT_FILE OR S_PIM_INT_PKGFL OR


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

Field MSSQL Oracle DB2

Tables Current Query Current Query Current Query

Table space (Leave empty) DATA TBS_4K

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)

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

146 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

4 Review the following files to make sure the import completed successfully:

<SiebelTools installation directory>\log\ACR464_seed.log

<SiebelTools installation directory>\log\ACR464_seed_<language>.log.

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.

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: The following applications are changed:

■ Siebel ERM Administration ■ Siebel Automotive

■ Siebel Field Service ■ Siebel Consumer Sector

■ Siebel Marketing Enterprise ■ Siebel Financial Services

■ Siebel Partner Manager ■ Siebel HTIM

■ Siebel Sales Enterprise ■ Siebel Hospitality

■ Siebel Universal Agent ■ Siebel Life Sciences


■ Siebel Loyalty

■ Siebel Power Communications

■ Siebel Public Sector

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 14 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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 The following business object


components are added: components are added:

■ Account Contact ■ Account Address

■ Account Industry ■ Account Industry

■ Account Organization ■ Account Organization

■ Account Position ■ Account Territory

■ Account Territory

■ Assignment Group

■ Industry

Contact The following business object The following business object


components are added: components are added:

■ Account Contact ■ Account Contact

■ Business Address ■ Contact Address

■ Contact Organization ■ Contact Organization

■ Opportunity Contact ■ Opportunity Contact

■ Organization

■ Position

Employee The following business object components are added to Siebel Business
Applications and Siebel Industry Applications:

■ Employee Position

■ Employee Responsibility

148 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Table 9. Changes Made as a Result of Importing the BusinessObject-Update.sif File

Business Object Siebel Business Applications Siebel Industry Applications

Opportunity The following business object components are added to Siebel Business
Applications and Siebel Industry Applications:

■ Assignment Group

■ Opportunity AssignmentGroup

■ Opportunity Position

Position The following business object components are added to Siebel Business
Applications and Siebel Industry Applications:

■ Assignment Group

■ Assignment Group Position Intersection

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.

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 Makes the following changes to the S_EVT_ACT
table: table:

■ INTEGRATION_ID ■ Changes the length of the INTEGRATION_ID


column from 30 to 450
■ INFO_SOURCE_CD
■ Adds the INFO_SOURCE_CD column

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.

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 14 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Table 11. Changes Made as a Result of Importing the BusinessComponent-Update.sif File

Business Component Change to Business Component Field

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.

Instructions for ACR 467


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
search for Doc ID 1171542.1.

1 Navigate to <Tools installation folder>\REPPATCH\ACR467.zip.

The ACR 467 folder contains the following subfolders:

■ \LMU

■ \SeedData

■ \REPOSITORY

■ \WORKFLOWS

■ \Schema

2 Lock the following projects:

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

6 Choose the Current Query option.

150 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

9 Lock the following projects:

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

……..

14 In Siebel Tools, lock all the following projects:


❏ Account

❏ Account (SSE)

❏ Asset Management

❏ Cfg JS

❏ Contact

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 15 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ 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

❏ Product Selection UI

❏ Quote

❏ Quote (UI)

❏ SIS OM Base Architecture

❏ 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

152 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 15 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

To perform batch import for ACR 467


■ Run the following command:

SET PCDTOOLSPATH=..\..\..

SET PCDDATASRC=ServerDataSrc

SET PCDUSERNAME=<LOGIN>

SET PCDPASSWORD=<PWD>

%PCDTOOLSPATH%\bin\siebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p


%PCDPASSWORD% /batchimport "Siebel Repository" merge ".\Applet" ".\Log\AppletImp.log"

%PCDTOOLSPATH%\bin\siebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p


%PCDPASSWORD% /batchimport "Siebel Repository" merge ".\Application"
".\Log\ApplicationImp.log"

%PCDTOOLSPATH%\bin\siebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p


%PCDPASSWORD% /batchimport "Siebel Repository" merge ".\Business Component"
".\Log\BusCompImp.log"

%PCDTOOLSPATH%\bin\siebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p


%PCDPASSWORD% /batchimport "Siebel Repository" merge ".\Business Object"
".\Log\BusObjImp.log"

%PCDTOOLSPATH%\bin\siebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p


%PCDPASSWORD% /batchimport "Siebel Repository" merge ".\Business Service"
".\Log\BusSvcImp.log"

%PCDTOOLSPATH%\bin\siebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p


%PCDPASSWORD% /batchimport "Siebel Repository" merge ".\Integration Object"
".\Log\IntObjImp.log"

%PCDTOOLSPATH%\bin\siebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p


%PCDPASSWORD% /batchimport "Siebel Repository" merge ".\Link" ".\Log\ Link.log"

%PCDTOOLSPATH%\bin\siebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p


%PCDPASSWORD% /batchimport "Siebel Repository" merge ".\Pick List" ".\Log\PickListImp.log"

%PCDTOOLSPATH%\bin\siebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p


%PCDPASSWORD% /batchimport "Siebel Repository" merge ".\Screen" ".\Log\ScreenImp.log"

%PCDTOOLSPATH%\bin\siebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p


%PCDPASSWORD% /batchimport "Siebel Repository" merge ".\Symbolic String" ".\Log\
SymStrImp.log"

%PCDTOOLSPATH%\bin\siebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p


%PCDPASSWORD% /batchimport "Siebel Repository" merge ".\View" ".\Log\ ViewImp.log"

%PCDTOOLSPATH%\bin\siebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p


%PCDPASSWORD% /batchimport "Siebel Repository" merge ".\EIM" ".\Log\ EIMImp.log"

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

154 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

To import ACR 467 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:

❏ For Oracle, enter the TNS service name that you created to connect Siebel Tools to the
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.

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

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 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 ODBC name created in Step 1.

b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
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:

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


Directory>\REPATCH\ACR467\SeedData\Seed_ACR467.dat/l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools
Install Directory>\REPATCH\ACR451\SeedData\ ACR467_seedimp.inp /q -1 /w y /e n /t n /x
R /n 100 /h log

<Tools Install Directory> - Replace with your Siebel Tools install directory

<ODBC Source Name> - Replace with the ODBC name created in Step 1

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 15 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

b Select Source Language = English American

Target Language = <Specific Language>

c Click the Import tab, browse to locate the LMU file you want to import, and click Import.

8 Stop the Siebel Server, if it is running.

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.

11 Start the Siebel Server.


12 Import the workflows listed in the following table into the Siebel application:

New/
Process Name 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

156 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

New/
Process Name Modified? Project

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 - Modify SIS OM Base Architecture
Contact

SIS OM Modify Products & Services Process - Modify SIS OM Base Architecture
Contact

SIS OM New Products & Services Process - Modify SIS OM Base Architecture
Contact

SIS OM Suspend / Resume Products & Services Modify SIS OM Base Architecture
Process - Contact

a Select Workflow Process in Siebel Tools Object Explorer.

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.

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.

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

Instructions for ACR 468


The following section contains information about how to install ACR 468.

For more information about Siebel Client Sync functionality, see Siebel Client Sync Guide on the
Siebel Bookshelf http://www.oracle.com/technology/documentation/siebel.html.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 15 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Prerequisites for ACR 468


Before installing the Siebel Client Sync software, make sure that you have completed the following
tasks:

■ Before you install Client Sync SDK7.x, it is recommended that you unregister Intellisync
SDK5.5 dlls if they are installed.

■ Client machine should have msxml 4.0 sp2 or higher version.

The following files are associated with this ACR :

■ ENU_Installer.zip from <Siebel Tools path>\REPPATCH\ which contains:

❏ vcredist_x86.exe

❏ setup.exe

❏ SiebelClientSync.msi

Before you begin your installation, copy the translation.txt file from the <New Client Sync>\bin\enu
directory and replace the existing one under <Siebel Server Base>\siebsrvr\bin\enu with the copy.

Unregistering SDK 5.5 SDK


1 Before installing the new Siebel Client Sync on top of Siebel Client Sync, unregister the dlls
specific to Intellisync 5.5 SDK as mentioned below:

The following examples show how to unregister each of the Intellisync connectors from the
command line. In the examples, replace "$(SiebelRoot)" with the appropriate path to the Siebel
Client Sync product directory.

■ Microsoft Outlook

❏ regsvr32.exe /u
"$(SiebelRoot)\bin\connectors\MS_Outlook_Connector\ilxolkCompanion.fil"

■ Lotus Notes
❏ regsvr32.exe /u "$(SiebelRoot)\bin\connectors\Lotus_Notes_Connector\ilxlnic.dll"

■ Palm OS handheld device


❏ regsvr32.exe /u "$(SiebelRoot)\bin\connectors\Pilot_Connector\PilotConnector.fil"

■ GroupWise

❏ regsvr32.exe /u
"$(SiebelRoot)\bin\connectors\Groupwise_6.5.x_Connector\GWEMAILCONN.dll"

❏ regsvr32.exe /u
"$(SiebelRoot)\bin\connectors\Groupwise_6.5.x_Connector\GWEMAILCONNApi.dll"

158 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

2 Unregister the Siebel Client Sync COM servers by issuing the following commands from the
command line:

regsvr32 /u cxlserver.dll

regsvr32 /u sscpumaconn.dll

regsvr32 /u stcpumaapi.dll

Installing the Siebel Client Sync Software


1 Within <Siebel Tools path>\REPPATCH, unzip the ENU_Installer.zip file.

NOTE: If you are installing a language other than ENU, select your language from the
appropriate directory. For example, a customer who is installing the DEU application would use
DEU_Installer within bin\DEU.

2 Double-click on vcredist_x86.exe to install Microsoft Visual Studio 2005 redistributables.

3 Double-click on setup.exe to install the new Siebel Client Sync application. When you are
prompted to give the folder path for installing new Siebel Client Sync, accept the default path or
give a path other than the original Siebel Sync 8.1.1.1 installation path.

For example: If Siebel Sync 8.1.1.1 is installed in D:\SiebelSync, then install ACR 468 for Siebel
Sync in D:\ACR468B.

4 After the new Siebel Client Sync application is installed, double-click on the Siebel Client Sync
shortcut that was created during the installation and provide the User ID, Password, and Connect
String.

Instructions for ACR 471


For information about how to configure ACR 471, see Siebel Order Management Guide. This guide is
available on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.

Instructions for ACR 474 and ACR 508


This section provides information, instructions, and guidelines for installing ACR 474 and ACR 508.

This section includes the following topics:

■ Release Notes for ACR 474 and ACR 508

Release Notes for ACR 474 and ACR 508


The following section documents known issues with ACR 474 and ACR 508.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 15 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Product Version: 8.1.1.4

Change Request: 12-1XTI4Q6

MOVE ORDER TRANSFER RESULTS IN EMPTY STATUS AS OF HEADER FIELD.

Use the following workaround to address this issue:

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

❏ Column: STATUS_DT

❏ Type: DTYPE_UTCDATETIME

160 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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
Category: Comm Media Energy

Subcategory: Billing Management

Product Version: 8.1.1.4

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:

Field Name Type Value

Fulfillment Status Code Literal

Back Office Error Text Literal

6 Add a new Siebel Operation Step between "Update Fulfillment Mode and Status for Header"
(Siebel Operation Step) and "Submit" (Sub Process).

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 16 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

7 Right-click, select View Properties Window and modify the properties of the Siebel Operation Step
as follows:

Business Component Order Entry - Line Items

Business Component Order Entry - Line Items

Operation Update

Name Update Fulfillment Status and Status Context for Line Items

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:

Field Name Type Value

Fulfillment Status Code Literal

Status Context Literal

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

xpression Business Filter Business


Component Component Type Search Specification

Order Entry - Orders Order Entry - Line Expression "[Order Header Id] ='"
Items + [&Object Id] + "'"

10 Save all of your cha nges and publish/activate the workflow.

PROBLEM WITH ADJUSTMENT EFFECTIVE DATE


Category: Comm Media Energy

Subcategory: Billing Management

Product Version: 8.1.1.4

Change Request: 12-1ZOI2LP

The Effective Adjustment field stores only the Date field not the time value.

Use the following workaround to address this issue:

Before you begin, within My Oracle Support, navigate to the Knowledge tab and search for Doc 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.

162 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

To edit the S_INVOICE_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 Invoice Adjustment 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:

Name Value

Type DTYPE_UTCDATETIME

3 Save the changes, and then compile them to the SRF.

To edit the CMU Invoice Adjustment 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:

Name Value

Type DTYPE_UTCDATETIME

3 Save the changes, and then compile them to the SRF.

To edit the FS Invoice Adjustment 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

3 Save the changes, and then compile them to the SRF.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 16 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

To edit the SIA Invoice Adjustment External Items BC


1 Log into Siebel Tools, and query for the SIA Invoice Adjustment External Items business
component.

2 Change the following column for the Adjustment Effective Date field:

Name Value

Type DTYPE_UTCDATETIME

3 Save the changes, and them compile them to the SRF.

To edit the CMU Billing Invoice Adjustment External Items BC


1 Log into Siebel Tools, and query for the CMU Billing Invoice Adjustment External Items business
component.

2 Change the following column for the Adjustment Effective Date field:

Name Value

Type DTYPE_UTCDATETIME

3 Save your changes, and then compile them to the SRF.

To edit the CMU SIA Invoice Adjustment External Items BC


1 Log into Siebel Tools, and query for the CMU SIA Invoice Adjustment External Items business
component.

2 Change the following column for the Adjustment Effective Date field:

Name Value

Type DTYPE_UTCDATETIME

3 Save the changes, and then compile them to the SRF.

To edit the CMU Invoice Adjustment External Items BC


1 Log into Siebel Tools, and query for the CMU Invoice Adjustment External Items business
component.

2 Change the following column for the Adjustment Effective Date field:

Name Value

Type DTYPE_UTCDATETIME

164 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 Save your changes, and then compile them to the SRF.

Integration Object Changes

To edit the CMU Request Adjustment IO


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:

Name Value

Data Type DTYPE_UTCDATETIME

External Data Type DTYPE_UTCDATETIME

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:

Name Value

Data Type DTYPE_UTCDATETIME

External Data Type DTYPE_UTCDATETIME

6 Save your changes, and then compile them to the SRF.

To edit the CmuRequestAdjustmentIo IO


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:

Name Value

Data Type DTYPE_UTCDATETIME

External Data Type DTYPE_UTCDATETIME

4 Query for the SIA Invoice Adjustment External Items integration component.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 16 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

5 Change the Data Type for the "Adjustment Effective Date integration component field:

Name Value

Data Type DTYPE_UTCDATETIME

External Data Type DTYPE_UTCDATETIME

6 Save your changes, and then compile them to the SRF.

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.

Use the following workaround to address this issue.

To address Bug 9851535/CR 12-1YOWCOT


1 From within the Siebel application, navigate to Site Map > Administration Integration > Data Map
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

Product Version: Siebel 8.1.1.3 Fix Pack

166 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Change Request: 12-1YK6RG0

Use the following workaround to address this issue.

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


Category: Comm Media Energy

Subcategory: Order Management

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


Category: Comm Media Energy

Subcategory: Order Management

Product Version: Siebel 8.1.1.1 QF7103

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 16 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Follow-On Orders Can Be Submitted Before Base Orders


Category: Comm Media Energy

Subcategory: Order Management

Product Version: Siebel 8.1.1.1 QF7103

Change Request: 12-1XTI4LP

No error occurs when a Follow On order is submitted after the Base Order is cancelled.

To address CR 12-1XTI4LP
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


Category: Comm Media Energy

Subcategory: Order Management

Product Version: Siebel 8.1.1.1 QF7103

Change Request: 12-1XTI4NO

Follow-On orders can be submitted for Cancelled Base Order.

To address CR 12-1XTI4NO
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.

168 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Sales Order Form Buttons Not Disabled After Cancel Order Starts
Category: Comm Media Energy

Subcategory: Order Management

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-1XTI4UE
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
Category: Comm Media Energy

Subcategory: Order Management

Product Version: Siebel 8.1.1.1 QF7103

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 16 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ 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


1 Log into Siebel Tools.

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.

170 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ CR 12-1UK1DKW

Description: The Cancel Error Mode system preference default value should be '3'.

Workaround: Use the following workaround to address this issue.

To address CR 12-1UK1DKW
1 Within the Siebel application, navigate to Administration - Application > System Preferences.

2 Within the System Preference Name field, query for “Cancel Error Mode” and set the value of the
System Preference field to 3.

3 Restart the Siebel Server.

■ CR 12-1T03IG9

Description: When the due date of a root product in a Customizable Product is nullified, order
validation does not occur.

Workaround: Use the following workaround to address this issue.

To address CR 12-1T03IG9
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.

This will create the following directory structure:

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 17 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ \ACR474_Workaround. This file contains the Release Notes and workaround information.

■ \8113_Addendum.

3 Unzip the ACR474.zip file.

This will create the following directory structure:

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

Applying Schema Changes to the Database


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

172 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ 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

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 Service Request

❏ Table Special Rate List


❏ Table CIF

❏ Table FleetManagement

❏ Table Person

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

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 17 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ 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_EIMTables.sif file into the repository


1 Lock the following projects before import:

❏ 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

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

Applying ACR 474 Schema Changes


As part of the ACR474 release, schema changes have been done on the database. The
REPPATCH\AIA251\ACR474\DMGSchemaChanges\ACR474_Tables.sif has all the changes for the
following:

Changes to existing tables:

■ S_ASSET

■ S_CONTACT

174 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ 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

■ 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


1 Lock the following projects before import:

❏ Table Asset

❏ Table CIF

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 17 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ Table FieldService

❏ Table FleetManagement

❏ Table Forecast

❏ Table Household

❏ Table NetworkOrderManagement

❏ Table OnPremise-OnDemand

❏ Table Opty

❏ Table Order

❏ Table Organization

❏ Table Person

❏ Table PriceList

❏ Table Product

❏ Table Quote

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

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.

Applying EIM Changes


As part of the ACR474 release, EIM changes have been done on the database. The
REPPATCH\AIA251\ACR474\DMGSchemaChanges\ACR474_EIMTables.sif file has all the changes for
the following:

Changes to existing tables:

■ EIM_ACCOUNT

■ EIM_ACCOUNT1

■ EIM_ASSET1

■ EIM_CONTACT

■ EIM_CONTACT2

■ EIM_GROUP

■ EIM_GROUP_DTL

■ EIM_OPTY

■ EIM_OPTY_DTL

176 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ 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

■ 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_EIMTables.sif file into the repository


1 Lock the following projects before import:

❏ EIM Asset

❏ EIM CIF

❏ EIM Common SIA

❏ EIM FieldService

❏ EIM FleetManagement

❏ EIM Forecast

❏ EIM Household

❏ EIM Opty

❏ EIM Order

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 17 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ 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
repository. The "merge" option should be used while importing this file.

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.

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.

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:

❏ For Oracle, enter the TNS service name that you created to connect Siebel Tools to the
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\AIA251\ACR474\SeedData\ACR463_SEED.

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

4 Seed data import includes mono-language seed-data import and language seed-data import. Use
either Step a or Step b 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.

178 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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
import completed successfully.

Importing Seed Data for ACR 474


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

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

4 Run the following command:


<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install
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

<Tools Install Directory> - Replace with your Siebel Tools install directory

<ODBC Source Name> - Replace with the ODBC name created in Step 1

<Database Platform> - Replace with the database platform (ORACLE, DB2UDB or MSSQL)

5 Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
Depending upon the language that you are installing, complete either Step XX or Step XX.

6 For ENU (English Language) customers:

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 17 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

a Run the following command after importing the ACR474_Seed.dat file.

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


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

<Tools Install Directory> - Replace with your Siebel Tools install directory

<ODBC Source Name> - Replace with the ODBC name created in Step 1

<Database Platform> - Replace with your database platform (ORACLE, DB2UDB or MSSQL)

b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
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.

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


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

<Tools Install Directory> - Replace with your Siebel Tools install directory

<ODBC Source Name> - Replace with the ODBC name created in Step 1

b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.

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.

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


Directory>\REPATCH\AIA251\ACR474_SEED\AIA251_seed_locale_XXX.dat /l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q -1 /w n
/e y /t n /x R /n 100 /h log

<Tools Install Directory> - Replace with your Siebel Tools install directory

<ODBC Source Name> - Replace with the ODBC name created in Step 1

d Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.

Updating ACR 474 EIM Files


As part of the ACR474 release, the EIM files - eim45.sql and eim_export_lookup_bu_name.sql have
been changed. The REPPATCH\AIA251\ACR474\EIM\eim45.sql and
REPPATCH\AIA251\fACR474\EIM\eim_export_lookup_bu_name.sql have all the changes required.
You must merge these files with the existing files in the Siebel Server directory:

eim45.sql: <Installation Location>\SERVER\siebsrvr\SQLTEMPL

180 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

eim_export_lookup_bu_name.sql : <Installation Location>\SERVER\siebsrvr\ADMIN

Siebel Tools Changes for ACR 474


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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 18 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ 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 Promotion Integration

182 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ ISS Promotion Workflow

■ ISS VOD Import Export

■ 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

■ Product Selection UI

■ Quote (UI)

■ Quote

■ Row Set Transformation Toolkit

■ SIS OM Base Architecture

■ Service

■ Siebel Sales Enterprise


■ Siebel High Tech
■ Siebel Universal Agent

■ Srvagree

■ Srvagree (SSV)

■ Symbolic Strings

■ Template (Order)

■ Table Asset

■ Table BulkRequest

■ Table Invoice

■ Table Order

■ Table Organization

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 18 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ Table Product

■ Table Promotions

■ Table Quote

■ Table Service Request

■ Table Special Rate List

■ Table CIF

■ Table Person

■ Table FleetManagement

■ Table FieldService

■ Table Forecast

■ Table Household

■ Table NetworkOrderManagement

■ Table Opty

■ Table PriceList

■ Table OnPremise-OnDemand

■ UCM Privacy Management

■ UMSUI

■ VEAI CUT Billing Integration

■ VERT CUT Address

■ VERT CUT Common

■ VERT CUT Screens

■ Web Channel Order Management


■ Web Service Integration
■ 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:

184 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.
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.
b Select Source Language = English American

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.

5 Stop Siebel Server, if it is running.

6 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

7 Compile all of the projects using the Compile Projects > All Locked Projects option and save the
SRF file to the <Siebel Server Install folder>\objects\ENU\siebel_sia.srf folder on the installed
Siebel server.

8 Copy the Web Template file CZConfigurator.swt and CZView.swt from the WebTemplate folder
into Siebel Server <Siebel Server Install folder >\WEBTEMPL.

9 Copy the CZReturn.html 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.

11 Start the Siebel Server.


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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 18 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ 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

186 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ Import the "SWISetTBOEndDate" workflow first and then import the "Dynamic Pricing
Procedure" workflow.

Workflow Name Project

*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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 18 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Workflow Name Project

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

188 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Workflow Name Project

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

NOTE: The asterisks denote workflows that were not modified for ACR 474.

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

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 18 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ 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

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

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.

f Navigate to the Site Map, and click Administration - Business Process.

g Navigate to Workflow Deployment > Repository Workflow Process.

h Query for the workflow processes and activate them.

NOTE: It is recommended that you reload the runtime events after activating the workflows.

i Navigate to Administration - Runtime Events > Events screen, select all records and then select
Reload Runtime Events from the drop-down menu.

190 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

14 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

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

16 Import and activate the workflows listed in the following table from
\AIA251\ACR474_Workaround\WFs into Siebel Tools:

New/
Process Name Modified Project

Pricing Procedure - Calculate Net Price Toolkit Modified Row Set Transformation

SIS OM Edit Service Order Line Item Modified SIS OM Base Architecture

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.

d Repeat Step b and Step c c for of all the workflows in the folder.

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

If you have not locked the required projects, you may receive a warning error message.

Make sure to choose Merge Option in Siebel Tools Import Wizard.

Import the following SIF files:

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 19 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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

19 If the Table Promotions project is not already locked, lock it.


20 Within Siebel Tools, query for the S_PRO_CFG_ITEM table.
21 Use the "Apply/DDL" button to apply the changes to the physical database.
22 Import the workflows listed in the following table into Siebel Tools and then activate the
workflows.

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

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

d Repeat Step b and Step c for of all the workflows in the folder.

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

192 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

24 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

❏ Default Pricing Variable Map - Row Set

❏ Default Pricing Eligibility Variable Map - Row Set

b Release a new version of each of the above objects and then bounce the server.

25 Release the signal:


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.

26 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>:
❏ SIA

❏ Siebel CME [Alias- Communications]

❏ Siebel ISS [Alias- ISS]


❏ Workflow Management [Alias- Workflow]

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 19 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ Query for the following groups: Eligibility & Comp, Asset Based Ordering, Pricer, 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*.

❏ Query for the following groups: Eligibility & Comp, Asset Based Ordering, Pricer, 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.

28 Restart the Siebel Server.


29 Launch the Siebel Communications application.
30 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

194 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ SyncCustomerSiebelEventAggregator

❏ SyncInstalledProductListSiebelCommsReqABCSImpl

❏ UpdateCreditAlertSiebelCommsReqABCSImpl

d Change the Address field for each outbound Web service to point to 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*.

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

Table 12. Siebel Component Groups

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

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:

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 19 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ EXEC = TRUE

■ Privileged User = <Table Owner>

■ Privileged User Password = <Table Owner>

■ Remove = TRUE

■ Trigger File Name: trigger.sql

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

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


Server Manager Parameter named Show Advanced Objects 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. In order to reveal this hidden parameter, complete
the following steps.

To reveal 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.
Under the Component subtab, query for the Server Manager component.

3 Under the Parameters subtab, query for Show Advanced Objects.

196 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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.

3 Restart the Siebel Server.

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>

■ Trigger File Name: trigger.sql

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 19 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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 197 and “To generate the trigger” on page 197.

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.

5 Restart the Siebel Server.

198 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Setting Order Priority for AQ


Use the following procedure to set order priority for AQ.

1 Navigate to the Administration - Data > List Of Values view.

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:

Display Value Language-Independent Code

Low 6

Medium 4

High 2
Urgent 0

4 Click Clear Cache to clear the cache.

Advanced Queue Configuration


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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 19 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory

java.naming.provider.url=opmn:ormi:// 152.68.240.154:6009:oc4j_soa

java.naming.security.principal=anonymous

Make sure that there are no extra spaces in the jndi.properties file.

6 Create a Named Subsystem in the Siebel application through the server management.

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

200 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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:

Create named subsystem JAVA for subsystem JVMSubSys with


DLL= /usr/jdk1.5.0_06/jre/lib/sparc/client/libjvm.so, CLASSPATH = /export/home/qa1/
JMS:/export/home/qa1/JMS/Siebel.jar:/export/home/qa1/JMS/rdbms/jlib/aqapi.jar:/
export/home/qa1/JMS/jdbc/lib/ocrs12.jar:/export/home/qa1/JMS/jdbc/lib/
ojdbc14dms.jar:/export/home/qa1/JMS/jdbc/lib/orai18n.jar:/export/home/qa1/JMS/
SiebelJI_enu.jar:/export/home/qa1/JMS/j2ee/home/lib/adminclient.jar:/export/home/qa1/
JMS/j2ee/home/lib/jndi.jar:/export/home/qa1/JMS/j2ee/home/lib/jta.jar:/export/home/
qa1/JMS/j2ee/home/oc4jclient.jar:/export/home/qa1/JMS/j2ee/home/lib/bcel.jar:/export/
home/qa1/JMS/j2ee/home/lib/jms.jar:/export/home/qa1/JMS/j2ee/home/lib/javax77.jar:/
export/home/qa1/JMS/lib/dms.jar:/export/home/qa1/JMS/opmn/lib/optic.jar:/export/
home/qa1/JMS/j2ee/home/lib/ejb.jar:., VMOPTIONS= /export/home/qa2/JMS/log/jms.log

Make sure that the path is correct for all the files and that the CLASSPATH ends with a . (dot).
Here qa2 should be replaced with the appropriate folder name.

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.

8 Restart the Siebel Server.

NOTE: For more information, see the Siebel Enterprise Application Integration (EAI)
documentation on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/
siebel.html.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 20 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Required Tasks for the Order to Cash PIP


NOTE: The following tasks are required if you are using 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).

202 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 Query for the ‘Order Management - Enable Asset Based Ordering’ parameter in the parameter
list for the component, and set the value to False.

4 Restart the Siebel Server.

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

5 Pricelist EIM

6 Customers EIM

7 Assets EIM

Before you begin the EIM import, note the following:

■ Make sure that the Siebel Server is running.

■ Make sure that the Siebel EIM component is online and is running properly. (To check this,
navigate to the Administration - Server Configuration or Administration - Server Management
screens.)
■ To avoid data loss, do not restart the Siebel Server while the EIM job is running.

■ After you have completed the data load for one country, make backup copies of the EIM logs, for
status verification. These logs are located in the siebsrvr/logs directory.

Checking EIM Component Availability


Use the following procedure to check EIM component availability.

To check EIM component availability


1 Navigate to the Administration - Server Management screen, then Servers, and then the
Component Groups view. Make sure that the component group Enterprise Application Integration
is active and online.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 20 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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 EIM job


1 Place the respective IFB file on the server machine using the Siebsrvr/Admin file path, as shown
in the following example:

Component IFB File

Product Product.ifb

Pricelist Pricelist.ifb

Customer Customer.ifb

Asset Asset.ifb

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:

204 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

UPDATE ORA19111.EIM_ACCOUNT SET OU_NUM = T_ORG_EXT__RID WHERE


IF_ROW_BATCH_NUM=100

where ORA19111 is the working instance.

Also, the same should be considered for the [UPDATE INTEGRATION ID] section of the Pricelist.ifb
file:

SESSION SQL = "UPDATE ORA19111.EIM_PRI_LST SET PL_INTEGRATION_ID = NULL WHERE


PL_INTEGRATION_ID IS NOT NULL"

For Pricelist.ifb, comment the second process using a terminate symbol (so that it becomes
inactive and only the first process is executed), like this:

[IMPORT ALL PRICELISTS]

TYPE = SHELL

INCLUDE = "IMPORT PRICELIST"

;INCLUDE = "UPDATE INTEGRATION ID"

Once EIM imports all of the pricelist data and the Integration Id is populated, the administrator
needs to run another ODI API to populate the cross-reference database. Then, the administrator
needs to run EIM again to nullify integ_id. The format of the IFB file for the second run will look
like:

[IMPORT ALL PRICELISTS]

TYPE = SHELL

;INCLUDE = "IMPORT PRICELIST"

INCLUDE = "UPDATE INTEGRATION ID"

All the job parameters should remain the same for both of the runs.

3 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 column displays
“Success” for the jobs that you have executed.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 20 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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(*),IF_ROW_STAT FROM EIM_PROD_INT

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT

Product Details:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_PROD_INT1

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT

Product-Inventory Locations:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_PRODINVLOC

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT

Pricelists
In this case since the same set of records are processed twice by the two separate sections of the
IFB file: one meant for importing the Pricelist Records and other meant for updating the Integration
Id to NULL, you will get the DUP_REC_EXISTS status in the EIM tables.

SELECT COUNT(*),IF_ROW_STAT FROM EIM_PRI_LST

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT

Customers
Address:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_ADDR_PER

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT

Account:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_ACCOUNT

WHERE IF_ROW_BATCH_NUM = '100'

206 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

GROUP BY IF_ROW_STAT

Account Details:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_FN_ACCNT1

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT

Customer:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_CONTACT

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT

Assets
There are two sections in the IFB file: For Importing Assets and For Updating the Parent Assets.

Hence the status will show DUP_REC_EXISTS

SELECT COUNT(*),IF_ROW_STAT,IF_ROW_BATCH_NUM FROM EIM_ASSET

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT,IF_ROW_BATCH_NUM

Use the following procedure to check the EIM log.

To check the EIM log


1 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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 20 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ 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 joint workspace Row ID


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

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”

208 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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


The following runtime configuration changes need to be done before you can launch Oracle
configurator.

1 Login to 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 imported above and activate them.

b Make sure they are in active state by querying in the bottom applet.

3 Navigate to Site Map > Administation Order Management > Signals.

a Query for the Signal "Customize".

b Lock the signal record and click on Workspace.

c Change the service name to SWI Configurator Load.


d Navigate back to Signals view and click the "Release New Version" button to release a new
version of the signal.
e Query for the Signal "QuotesAndOrdersValidate".
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)"

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 20 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

4 Navigate to Administration Runtime Events > Events and click Menu > Reload Runtime Events.

5 Navigate to Administration - Application > Views.

a Click New to create 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 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 From the top applet use the drop-down menu (bold highlighted menu) and select Host
Administration.
b Add a new host entry:

❏ 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 new record in the top applet.

❏ Name: OracleCfgURL (Note: This symbolic name is very important because server side
business component code relies on this name)

❏ URL: http://OracleConfigurator/OA_HTML/CfgSebl.jsp

❏ Choose the host name: for example qapache.us.oracle.com:3710


❏ Fixup Name: Default

❏ SSO Disposition: IFRAME

d In the bottom applet, add arguments to the URL:

Create a new record with the following values:

❏ Name: InitMessage

❏ Req Arg: checked

❏ Argument Type: Profile Attribute

❏ Argument Value: CZInitMessage

❏ Append as argument: checked

Add another new row:

❏ Name: PostRequest

❏ Required Arg: Checked

210 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ Argument Type: Command

❏ Argument Value: PostRequest

❏ Append as argument: Not-Checked

Complete the following two steps to set up the "SSO" login into Oracle Apps. The "SSO" login
is the preferred style to access Oracle. If "SSO" login is not set up, then the Siebel end user
will have to know and enter Oracle login credentials at the login page.

e 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 current Siebel User. Putting anything else in will require that you log into
an Oracle Applications for Configurator session.
f Continue to add arguments to the same URL.

❏ Name: username

❏ Required Arg: Checked

❏ Argument Type: Command

❏ Argument Value : UserLoginId

❏ Append as argument: Checked

g Add the final argument

❏ Name: password

❏ Required Arg: Checked

❏ Argument Type: Command

❏ Argument Value: UserLoginPassword

❏ Append as argument: Checked

h 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

i In the bottom applet "SSO System Users" add records for the Siebel users that will be invoking
Oracle configurator. The Siebel usernames will be paired with Oracle login credentials. For
example:
❏ Siebel Login Name: sadmin

❏ Login Name: operations

❏ Password: welcome

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 21 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

7 Navigate to Administration - Server Configuration > Components Select "eCommunications


Object Manager (ENU)" Component and select "Order Management - Enable Asset Based
Ordering" Parameter and set this value to False to call Oracle configurator instead calling Siebel
Configurator.

"HTIM Object Manager (ENU)" Component and select "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 would need to be activated for Configurator to work. Note that these are
not workflows that were introduced as part of Oracle Configurator integration, but are existing
ones.

■ 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 Siebel.
These custom applications are used during the publication phase of Oracle Configurator Model
development cycle.

To add Siebel Custom Applications to Oracle Applications


1 Log in to Oracle Applications with credentials that have the Sys Administrator privilege.

2 Choose Application > Register.

Forms will start up.

3 The form page for Applications > Register should be displayed. If not, navigate to the form.

4 Create three new entries each 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

212 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

5 Change responsibility to Configurator Administrator.

6 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 the entire process of developing 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 above
Web Services.

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: 'External Configurator Reference 1','External
Configurator Reference 2', 'External Configurator Reference 3' to both the Source and the
Destination Column in 'Data Map Field' section for the 'Data Map Component' specified in the
paranthesis below.

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 21 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ ReviseQuote(Data Map Component Name:Line Item)

■ TemplateToOrder(Data Map Component Name:Line Item)

■ TemplateToQuote(Data Map Component Name:Line Item)

DoCompression Parameter Setup


1 Stop the Siebel Server.

2 Backup the file D:\19924\eappweb\bin\eapps.cfg.

NOTE: The folder D:\19924 has been suggested here, but if you have installed the application
someplace else, please make sure that you refer to the eapps.cfg file in your installation.

3 Edit D:\19924\eappweb\bin\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: Restarting the Siebel Server will not be enough.

Applying Changes for the Signal


1 Navigate to Administration - Order Management > Signal.

2 Change the following Signal sequences if required. By locking the signal and click the Workspace,
do the following Sequence changes and release the signal by clicking the Release button.

Service Name Service Type Sequence Condition Active Mode

SWISendCalculateShippingCha Workflow 1 SystemPreference("Enable Yes Order


rge AIA OrderToCash")="TRUE

ISS Tax Calculation Service Business Service 2 Yes Order

ISS Shipping Calculation Business Service 3 No Order


Service

ISS Tax Calculation Service Business Service 2 Yes Quote

ISS Shipping Calculation Business Service 3 Yes Quote


Service

Service
Service Name Type Sequence Condition Active Mode

SWISendPaymentAuthorization Workflow 1 SystemPreference("Enable AIA Yes Payment


OrderToCash")="TRUE”

ISS Credit Card Transaction Business 2 Yes Payment


Service Service

ISS Credit Card Transaction Business 2 Yes Quote


Service Service

214 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Service Name Service Type Sequence Condition Active Mode

SWISendCreditCheck Workflow 1 SystemPreference("En Yes Payment


able AIA
OrderToCash")="TRUE

ISS Credit Check Service Business 2 Yes


Service

Service Name Service Type Sequence Condition Active Mode

SWISendATPCheckLine Workflow 1 SystemPreference("Enable Yes Order


AIA OrderToCash")="TRUE”

ISS ATP Service BusinessService 2 Yes

Service Name Service Type Sequence Condition Active Mode

SWISendATPCheck Workflow 1 SystemPreference("E Yes Order


nable AIA
OrderToCash")="TRU
E

ISS ATP Service Business Service 2 Yes

Service
Service Name Type Sequence Condition Active Mode

SWI Configurator Workflow 1 SystemPreference("Enable Yes


Load AIA OrderToCash")="TRUE”

Service
Service Name Type Sequence Condition Active Mode

PSP Driver Workflow 1 Yes Order


Workflow Process

PSP Driver Workflow 1 Yes Order


Workflow Process

Verify Header Workflow 2 SystemPreference("Enable Yes Order


(Order) AIA OrderToCash")<>"TRUE”

Oracle Verify Workflow 2 SystemPreference("Enable Yes Order


Header (Order) AIA OrderToCash")="TRUE”

Verify Item Workflow 2 SystemPreference("Enable Yes Order


(Order) AIA OrderToCash")<>"TRUE”

Oracle Verify Item Workflow 2 SystemPreference("Enable Yes Order


(Order) AIA OrderToCash")="TRUE”

PSP Driver Workflow 1 Yes Quote


Workflow Process

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 21 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Service
Service Name Type Sequence Condition Active Mode

PSP Driver Workflow 1 Yes Quote


Workflow Process

Verify Item Workflow 2 SystemPreference("Enable Yes Quote


(Quote) AIA OrderToCash")<>"TRUE”

Oracle Verify Item Workflow 2 SystemPreference("Enable Yes Quote


(Quote) AIA OrderToCash")="TRUE”

Verify Header Workflow 2 SystemPreference("Enable Yes Quote


(Quote) AIA OrderToCash")<>"TRUE”

Oracle Verify Workflow 2 SystemPreference("Enable Yes Quote


Header (Quote) AIA OrderToCash")="TRUE”

Fixing State Model for Quote Status


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

Other Order to Cash Configuration Steps


1 Inactivate the field map.

a Navigate to Administration - Application > Data Map Administration and query for Data Map
Object 'ReviseOrder' and Data Map Component 'Header' and Data Map Field 'Back Office Process
Status'.
b Inactive this field map by selecting the Inactive Check box.
2 Change/Activate data validation rules.

a 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

216 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 Activate these five rule sets by clicking the Activate button on the top applet.

Business Apply Return


Rule Name Expression Sequence Component To Code

Account (SystemPreference("E 1 PDS Simplified Current O2C-Order-


nable AIA Order Entry - Record 002
OrderToCash")="FALS Orders
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))

Status (SystemPreference("E 2 PDS Simplified Current O2C-Order-


nable AIA Order Entry - Record 002
OrderToCash")="FALS Orders
E") OR ([Status] =
LookupValue("FS_OR
DER_STATUS","Booke
d"))

Resubmit (SystemPreference("E 3 PDS Simplified Current O2C-Order-


nable AIA Order Entry - Record 003
OrderToCash")="FALS Orders
E") OR (([Back Office
Process Status] IS
NULL) OR ([Back
Office Process Status]
=
LookupValue("EAI_OR
DER_SYNC_STATUS",
"Error on Creating")))

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 21 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Business Apply Return


Rule Name Expression Sequence Component To Code

Payment ((SystemPreference(" 4 Payments All O2C-Order-


Enable AIA Records 004
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)))

Credit Hold (SystemPreference("E 5 PDS Simplified Current O2C-Order-


nable AIA Order Entry - Record 005
OrderToCash")="FALS Orders
E") OR ([Hold Flag]
="N" )

Cancel NOT(SystemPreferenc 6 PDS Simplified All SWI_CANCE


Reason not e("Enable AIA Order Entry - Records L_ORDER_0
empty OrderToCash")="TRU Line Items 02
E" AND ([Request To
Cancel] = "Y" AND
[Cancel Reason] IS
NULL))

218 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Rule Business
Name Expression Sequence Component Apply To Return Code

Card (SystemPreference( 1 Payments Current O2C-Order-006


Filled "Enable AIA Record
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")

Business Return
Rule Name Expression Sequence Component Apply To Code

O2C Account (SystemPreferen 1 PDS Current O2C-Quote-


ce("Enable AIA Simplified Record 002
OrderToCash")=" Quote
FALSE")OR
([Account Id] IS
NOT NULL )

O2C Ship (SystemPreferen 2 PDS Current O2C-Quote-


Address ce("Enable AIA Simplified Record 004
OrderToCash")=" Quote
FALSE") OR
([Ship To
Address] IS NOT
NULL)

O2C Bill ((SystemPrefere 3 PDS Current O2C-Quote-


Address nce("Enable AIA Simplified Record 003
OrderToCash")=" Quote
FALSE") OR ([Bill
To Address] IS
NOT NULL ))

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 21 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Business Return
Rule Name Expression Sequence Component Apply To Code

O2C Already (SystemPreferen 4 PDS Current O2C-Quote-


Processed ce("Enable AIA Simplified Record 005
OrderToCash")=" Quote
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"))

O2C Quote (SystemPreferen 5 PDS Current O2C-Quote-


Status ce("Enable AIA Simplified Record 001
OrderToCash")=" Quote
FALSE") OR
([Status] =
LookupValue("Q
UOTE_STATUS","
Approved"))

220 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Business Return
Rule Name Expression Sequence Component Apply To Code

SWI Active (SystemPreferenc 1 PDS Simplified Current SWI Order


Check e("Enable AIA Order Entry - Record Revise 001
OrderToCash")="F Orders
ALSE")OR
([Account Id] IS
NOT NULL )

SWI Revise (SystemPreferenc 2 PDS Simplified Current SWI Order


Order e("Enable AIA Order Entry - Record Revise 002
OrderToCash")="F Orders
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"))))

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 22 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Business Return
Rule Name Expression Sequence Component Apply To Code

SWI Revise (SystemPreferenc 3 PDS Simplified All SWI Order


Order Line e("Enable AIA Order Entry - Records Revise 003
OrderToCash")="F Orders
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"))))

SWI Back (SystemPreferenc 4 PDS Simplified Current SWI Order


Office Check e("Enable AIA Order Entry - Record Revise 002
OrderToCash")="F Orders
ALSE") OR ([Back
Office Process
Status] =
"Created in Back
Office")

222 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Business
Rule Name Expression Sequence Component Apply To Return Code

PONR Not NOT(SystemPref 1 PDS Simplified All Records SWI_CANCEL


Reached erence("Enable Order Entry - _ORDER_001
AIA Line Items
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')))

Cancel NOT(SystemPref 2 PDS Simplified Current SWI_CANCEL


Reason not erence("Enable Order Entry - Record _ORDER_002
empty AIA Line Items
OrderToCash")="
TRUE" AND
([Cancel Reason]
IS NULL))

4 Restart the Siebel Server.

5 Launch the Siebel Communications application.

Required Tasks for the COMM PIP


NOTE: The following tasks are required if you are using the COMM PIP.

To activate the rule sets for Comms


1 Query for the “Order Validation” rule set.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 22 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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 procedure
detailed above.

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 EIM job 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 has to be set to False.

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.

Enabling Dynamic Pricing (Customer Order Management)


The pricing module is available in multiple licensing modes and each mode is associated with either
the 'Basic Pricing Procedure' or the 'Dynamic Pricing Procedure'. Below is the definition of both:

224 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Dynamic Pricing
■ This provides the complete 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 those customers that have the 'Dynamic Pricer' license.

■ Dynamic Pricing can also be enabled by selecting "Enable Dynamic Pricing" from Admin - Pricing
> Price List > In Applet Level Menu dropdown select "Enable Dynamic Pricing".

■ This is a new implementation in 8.1.1. On selecting "Enable Dynamic Pricing", all the necessary
changes will be done.

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.

5 Query for the "SCE Users" user list. If it does not appear, create it.

6 Add the users created in the user list.

The user list created above 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.
2 Query for the "EmailNotify" action set.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 22 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 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 three run-time events use the action set described above.

Sequence Object Type Object Name Event Subevent Action Set


Name

1 BusComp Attribute VOD PreInvokeMethod SendEmail EmailNotify


BusComp

2 BusComp ISS Class VOD PreInvokeMethod SendEmail EmailNotify


BusComp

3 BusComp ISS Joint PreInvokeMethod SendEmail EmailNotify


Workspace
BusComp

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/edit other
templates.

To edit/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]

3 Navigate to Administration - Communication > All Templates > Template Items.

226 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

6 Navigate to Administration - Communication > All Templates > Template Items.

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 BCs listed in the
following table.

Business Component User Property Template Name

ISS Joint Workspace PackageNameList|Attribute Workspace Attribute Defn


BusComp Definition Template

ISS Joint Workspace PackageNameList|Product Workspace Product Class Defn


BusComp Class Definition Template

Attribute VOD BusComp PackageNameList Attribute Defn Template

ISS Class VOD BusComp PackageNameList Product Class Template

The SMTP Server name, From Email Address, and POP server details are added in the a
Communication profile. Use the following procedure to add the SMTP server name, From Email
Address, and POP server details.

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, then
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 child applet. If it does not exist, then 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

■ POP3 Account Name: support

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 22 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ 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 BCs listed in the following table:

Business Component User Property Template Name

ISS Joint Workspace CommProfileOverride Default SMTP Profile


BusComp

Attribute VOD BusComp CommProfileOverride Default SMTP Profile

ISS Class VOD BusComp CommProfileOverride Default SMTP Profile

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 above three attributes.

NOTE: The Class attributes names and the attribute definition names must be identical.

c For the TBO Discount products synced from BRM. Change the Structure type to ‘Customizable’
and Product Type should be “Time Based Offer” and associate the above TBO class to this
product.
2 Create Job to Inactive Assets.
a Navigate to Server Management, and then 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 parameters.


c Select Name “Workflow Process Name” and specify the Value = “SWI Asset Status Update”.

d Select Name as “Search Specification” and specify the Value if necessary.

3 Create Revision Data Maps.

a Navigate to Administration – Application, and then Data Map Administration.

228 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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)”, then go to
its parameters and query for Name = “Business Service Query Access List” and add Value = “CMU
External Integration Service”. Then, the server component should be restarted to take effect
after the change in the component parameter value.

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 Eligibility Variable Map - Row Set

❏ Default Pricing Variable Map - Row Set

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

4 Generate the Triggers.

5 Restart Siebel Services.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 22 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Instructions for ACR 475


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.

230 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Querying for New Prospects Causes Error


Category: Data Quality

Subcategory: ODQ Connector

Product Version: 8.1.1.4

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

Product: Siebel 8.1.1.1 QF3101

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

Product: Siebel 8.1.1.1 QF3103

The Back button navigates incorrectly when tabs are present in the DGM screen.

Workaround: None

Initial Load Process Does Not Support Cross-Database Pull


Change Request: 12-1VJIM79

Product: Siebel 8.1.1.1 QF3103

The Initial Load process does not support cross-database (platform) data pull.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 23 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.1
Fix Pack + 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, and ACR475B_UCM_4.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
Doc 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 233.

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.

8 Unzip the ACR475B_UCM_3.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.

9 Unzip the ACR475B_UCM_4.zip file from <Tools Install Directory>\REPPATCH and perform the
required configuration changes.

232 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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 Doc ID 880452.1. For information
about how to install ACR 475A, see “Configuration Instructions for ACR 475A” on page 233.

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 Oracle MetaLink 3.
To access the guide, navigate to the Knowledge tab and search for Doc 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 233

Both the Match and Fetch Web service are set up with the following tasks. If you need to manually
configure the Web services, see Doc ID 763962.1 on Oracle MetaLink 3.

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 233

■ “Compiling the SRF and Restarting the Siebel Server” on page 236

■ “Importing Seed Data” on page 237

Importing the SIF Files


This task is a step in “Process for Configuring Oracle Higher Education Constituent Hub Web Services”
on page 233.

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

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 23 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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: SymStrPrefix = SBL_.

■ SymbolicStrings.sif

■ Views.sif

4 After verifying that the .sif files are all present, log on to Siebel Tools.

5 Lock the following projects:

■ 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

■ Web Service Integration

■ EIM CIF
■ EIM Person

234 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 23 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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


This task is a step in “Process for Configuring Oracle Higher Education Constituent Hub Web Services”
on page 233.

The Siebel repository:


siebel_sia.srf
is located at:
<ServerInstallLocation>\ses\siebsrvr\objects\enu\siebel_sia.srf.
Compile the business object changes you made in the preceding steps for the changes to take effect.

To compile and restart the Siebel Server


1 Stop 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 Higher Education


■ UCM SDH

■ VEAI UCM CIF

■ VEAI UCM CIF UI

■ Web Service Integration

■ 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

236 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ 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


This task is a step in “Process for Configuring Oracle Higher Education Constituent Hub Web Services”
on page 233.

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 your tools
to the Oracle Database.

5 Navigate to <Tools Install Directory>\REPPATCH\ACR475A.

6 Before executing the next step make sure dataimp.exe exists in the <Tools Install
directory>\bin directory.

Importing Seed Data For ENU Implementations


ENU implementations require you to import two .dat files which contain seed data. Instructions are
as follows:

To import required .dat files


1 Run the following command to import the seed.dat file:

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 23 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


Directory>\REPPATCH\ACR475A_UCM\SeedData\ACR475A_Seed.dat /l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools
Install Directory>\REPPATCH\ACR475A_UCM\SeedData\<Database
Platform>\ACR475A_Seed.inp /e n /h log

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:

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


Directory>\REPPATCH\ACR475A_UCM\SeedData\ENU\ACR475A_Seed_Locale_ENU.dat /l <Tools
Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i
<Tools Install Directory>\REPPATCH\ACR475A_UCM\SeedData\<Database
Platform>\ACR475A_seed_locale_ENU.inp /e n /h log.

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

3 Review the Siebel Tools Install Directory>\temp\dataimp_seed.log file to make sure that
the import was 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. Instructions are as follows:

To import required .dat files


1 Run the following command to import the seed.dat file:

238 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


Directory>\REPPPATCH\ACR475A_UCM\SeedData\ENU\ACR475A_Seed_Locale_ENU.dat /l
<Tools Install Directory>\temp\dataimp_Seed.log /c <ODBC Source Name> /d <Table
Owner> /i <Tools Install Directory>\REPPATCH\ACR475A_UCM\SeedData\<Database
Platform>\ACR475A_seed_LOCALE_ENU.inp /e n /h log

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.

■ 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 seed_locale_XXX.dat file:

<Tools Install Directory>\bin\dataimp /u SADMIN /p sadmin /f <Tools Install


Directory>\REPATCH\ACR475A_UCM\SeedData\<LANG>\ACR475A_seed_locale_xxx.dat /l
<Tools Install Directory>\temp\dataimp_seed_lang.log /c <ODBC Source Name> /d <Table
Owner> /e n /h log.

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


3 Review the Siebel Tools Install Directory>\temp\Seed.log file to make sure that the import
was completed successfully.

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 Doc ID 880452.1. For information about how to install ACR 475A, see “Configuration
Instructions for ACR 475A” on page 233.

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 23 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

To import the SIFs 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

❏ BusinessComponents.sif

❏ BusinessObjects.sif

❏ BusinessServices.sif

❏ Classes.sif

❏ Command.sif

❏ Dlls.sif

❏ EBCTable.sif

❏ EIMTables.sif

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

240 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ 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 Higher Education

❏ UCM Merge

❏ UCM Privacy Management

❏ UCM SDH
❏ UCM Survivorship
❏ UCM Task UI

❏ UCM Unmerge

❏ VEAI UCM Account ASI

❏ VEAI UCM CIF

❏ VEAI UCM CIF UI

❏ VERT CUT Address

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 24 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ Web Service Integration

Use the following query to get the list of projects to lock/unlock:

i."Table Organization" OR "Table Party" OR "Table Person" OR "UCM CDM Child" OR "UCM Data
Management" OR "UCM Hierarchy Management" OR "UCM Higher Education"OR "UCM Merge" OR
"UCM Privacy Management" OR "UCM SDH" OR "UCM Survivorship" OR "UCM Task UI" OR "UCM
Unmerge" OR "VEAI UCM Account ASI" OR "VEAI UCM CIF" OR "VEAI UCM CIF UI" OR "VERT CUT
Address" OR "Web Service Integration"

ii."Account" OR "Account (SSE)" OR "Account Hierarchy" OR "Comm Manager" OR "Common


Components" OR "Contact" OR "DNB Data" OR "DQ ISS Integration" OR "DeDuplication" OR
"Household" OR "LOY Profiles" OR "Menu" OR "Server Components - Object Manager" OR "Siebel
Workflows - Seed" OR "Symbolic Strings" OR "Table CIF"}

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

242 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

To compile the SRF and restart the server


Use the following procedure to compile the SRF and restart the server.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 24 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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

244 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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

■ BusinessComponents.sif

■ Account

■ Contact

■ UCM Account Source Data and History

■ UCM Contact Source Data and History

■ BusinessObjects.sif
■ Merged Account
■ Merged Contact

■ BusinessServices.sif

■ DQ Sync Services

■ ISS System Services

■ UCM Data Quality Manager

■ UCM Merge Service

■ UCM Source Data and History Service

■ IntegrationObjects.sif

■ CIFContact

■ SwiOrganizationMatchInputIO

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 24 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ SwiOrganizationMatchOutputIO

■ SwiPersonMatchInputIO

■ SwiPersonMatchOutputIO

■ SyncAccount

■ SyncContact

■ SyncProspect

■ UCMAccountSourceDataAndHistory

■ UCMAccountTaskUIMerge

■ UCMContactSourceDataAndHistory

■ UCMContactTaskUIMerge

■ Tables.sif

■ EIM_UCM_ADRPER

■ EIM_UCM_ASSET

■ EIM_UCM_CON

■ EIM_UCM_HRCHY

■ EIM_UCM_ORG

■ EIM_UCM_ORGGRP

■ 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

■ UCM Process Merge Request

246 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

2 Log into Siebel Tools, and lock the following projects:

■ Account

■ Contact

■ DQ ISS Integration

■ EIM CIF

■ Employee

■ Siebel Workflows - Seed

■ Table CIF

■ Table UCM DRM Integration

■ UCM Data Management

■ UCM Higher Education

■ UCM Merge Task UI

■ UCM SDH

■ UCM Unmerge

■ VEAI UCM CIF

■ VEAI UCM CIF UI

■ Web Service Integration

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

Importing the SIF Files in the ACR475B_UCM_3.zip File


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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 24 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

To import the ACR475B_UCM_3.zip file


1 Log into Siebel Tools, and lock the following projects:

❏ Account Hierarchy

❏ UCM Hierarchy Management

❏ VEAI UCM CIF UI

2 Import all of the SIFs to the server database using the Merge option.

3 Stop the relevant server.

4 Lock the following projects:

❏ Account Hierarchy

❏ UCM Hierarchy Management

❏ VEAI UCM CIF UI

5 Compile all of the locked projects.

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

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

248 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Importing the SIF Files in the ACR475B_UCM_4.zip File


Use the following procedure to import the ACR475B_UCM_4.zip file.

To import the ACR475B_UCM_4.zip file


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

BusinessComponents.sif

■ Contact

■ UCM HE Constituent Affiliation Source Data and History

BusinessServices.sif

■ DQ Sync Services

■ UCM Utility Service

IntegrationObjects.sif

■ CIFContact

■ CIFContactInsert

■ CIFContactInsertRs

■ CIFContactUpdate

■ CIFContactUpdateRs

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 24 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ CIFContactUpsert

■ CIFContactUpsertRs

■ SwiPersonIO

■ SwiPersonPublishIO

■ UCMContactSourceDataAndHistory

Views.sif

■ Hierarchy Selection View

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

■ UCM Process Merge Request

2 Within Siebel Tools, lock the following projects:

❏ Comm Manager

❏ Contact

❏ DQ ISS Integration
❏ LOY Profiles
❏ Siebel Workflows - Seed

❏ UCM Data Decay Management

❏ UCM Hierarchy Management

❏ UCM Higher Education

❏ UCM SDH

❏ VEAI UCM CIF

❏ Web Service Integration

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.

250 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

5 For each of the changed integration objects, right-click, select Undeploy, select Refresh, right-
click, and select Deploy to Runtime Database.

The server repository- siebel_sia.srf located in


<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


1 Stop the relevant server.

2 Lock the projects that were modified in this release:

❏ Comm Manager

❏ Contact

❏ DQ ISS Integration

❏ LOY Profiles

❏ Siebel Workflows - Seed

❏ UCM Data Decay Management

❏ UCM Hierarchy Management

❏ UCM Higher Education

❏ UCM SDH

❏ VEAI UCM CIF

❏ Web Service Integration

3 Compile all of the locked projects.

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.

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 25 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Applying the EIM Changes in the ACR475B_UCM_2.zip File


As part of the ACR475B release, EIM changes have been done on the database. The
REPPATCH\ACR475B_UCM_2\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

252 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ 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 EIMTables.sif into the repository:


1 Lock the following projects:

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 25 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Eim45.sql: <Installation Location>\SERVER\siebsrvr\SQLTEMPL

eim_export_lookup_bu_name.sql : <Installation Location>\SERVER\siebsrvr\ADMIN

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 and ACR475B_UCM_4.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 239 to
bring the categories into the testing target database.

Importing the Seed Data in the ACR 475B_UCM_2.zip


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

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

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

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

d Enter the server name to connect to:


❏ For Oracle enter the TNS service name that you created to connect Siebel Tools to the
database.

e Test your connection and click OK when tested successfully.

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.

254 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

4 Run the following command:

<Tools Install Directory\bin>dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


Directory>\REPPATCH\ACR475B\ACR475B_UCM\SeedData\ACR475B_Seed.dat /l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner>/i <Tools Install
Directory>\REPPATCH\ACR475B
\ACR475B_UCM\SeedData\ACR475B_SeedInp_Files\<Database Platform>\ACR475B_Seed.inp /
q -1 /w y /e n /t n /x R /n 100 /h log

<Tools Install Directory> - Replace with the Siebel Tools install directory

<ODBC Source Name> - Replace with ODBC name created in Step 1.

<Database Platform> - Replace with the database platform (ORACLE, DB2UDB, or MSSQL)

5 Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the
import completed successfully.

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:

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install

Directory>\REPPATCH\ACR475B\ACR475B_UCM\SeedData\ACR475B_Seed_Locale_ENU.dat
/l <Tools Install directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table
Owner> /i Owner>/i <Tools Install
Directory>\REPPATCH\ACR475B\ACR475B_UCM\SeedData\ACR475B_SeedInp_Files\<Data
base Platform>\ACR475B_seed_locale_ENU.inp /q -1 /w n /e y /t n /x R /n 100 /h log

<Tools Install Directory> - Replace with the Siebel Tools install directory

<ODBC Source Name> - Replace with ODBC name created in Step 1.

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

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


Directory>\REPPATCH\ACR475B\ACR475B_UCM\SeedData\ACR475B_NON_ENU_Seed_Loca
le\seed_locale_XXX.dat /l <Tools Install directory>\temp\dataimp_seed.log /c <ODBC
Source Name> /d <Table Owner> /q -1 /w n /e y /t n /x R /n 100 /h log

<Tools Install Directory> - Replace with the Siebel Tools install directory

<ODBC Source Name> - Replace with ODBC name created in Step 1.

7 Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the
import completed successfully.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 25 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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.

Use the following procedure to compile the server repository.

256 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

To compile the server repository


1 Stop the relevant server.

2 Lock the projects that were modified in this release:

■ Account

■ Contact

■ DQ ISS Integration

■ EIM CIF

■ Employee

■ Table CIF

■ Table UCM DRM Integration

■ UCM Data Management

■ UCM Higher Education

■ UCM Merge Task UI

■ UCM SDH

■ UCM Unmerge

■ VEAI UCM CIF

■ VEAI UCM CIF UI

■ Web Service Integration

■ UCM SDH

■ UCM Merge

3 Compile all of the locked projects.

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>

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 25 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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=false 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”.

Configuring NetChart Server


Chart server needs to be installed from any release location with default settings—it 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.

258 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 25 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

4 Restart the Siebel Server.

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.

260 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 26 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Business Component Field Mapped Field

Name Account.Name

262 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Contact Business Component

Business Component Field Mapped Field

First Name Contact.First Name

Last Name Contact.Last Name

Middle Name Contact.Middle Name

List Mgmt Prospective Contact Business Component

Business Component Field Mapped Field

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

CUT Address Business Component

Business Component Field Mapped Field

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

Personal Address Business Component

Business Component Field Mapped Field

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 26 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Vendor Parameter
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

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 version="1.0" encoding="UTF-8"?>


<Data>
<Parameter>
<iss_host>HostName</iss_host>
</Parameter>
<Parameter>
<iss_port>1666</iss_port>
</Parameter>
<Parameter>
<datacleanse_mapping>
<mapping>
<field>BC Field</field>
<ssafield>ASM Field</ssafield>
<std_operation>Operation</std_operation>
</mapping>
</datacleanse_mapping>
</parameter>
</data>

264 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 26 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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.

266 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

To configure the DQ-ISS 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 Doc 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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 26 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

To configure Object Managers for ISS 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


1 Navigate to Site Map > Administration - Data Quality > Data Quality Settings.

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 Doc ID
1282393.1.

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


1 Navigate to Site Map > Administration - Data Quality > Data Quality Settings.

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:

268 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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 Doc ID 1282393.1.

Configuring List Import


These are the new system preferences used in List Import:

Name Value

UCM Import: Enable Validation True/False

UCM Import: Enable Launch BDM True/False

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.

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:

Name Value
Map:[Object].[Field] [SDH buscomp Name].[Buscomp Field Name]

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 26 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

For example, in "UCM Account Source Data and History,” there are the following Business Component
user properties:

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

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

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 is a Java-based application; it can run on any mainstream Windows, Linux, or
Unix system.

■ Siebel UCM application: In this release of DGM, Siebel UCM is the only supported master hub.
For information about how to install and configure the 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>.

270 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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.

Installing JDeveloper
Use the following procedure to install JDeveloper.

To install JDeveloper
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.

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 27 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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.

272 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Entry Name Description

host Weblogic server address

port weblogic server listening port

username

password weblogic server credential

target.server The default value is AdminServer

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&amp;SWEExtCmd=Execute&amp;UserName=SADMIN&a
mp;Password=MSSQL&amp;

NOTE: The endpoint information will be kept in xml files, so escape '&' to '&amp;'.

11 Click Install to start the install process.


12 Click Exit to finish the installation.

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 27 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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 23 This configuration will


specify how many records
paginate_cache_size
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.

274 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Entry Name Default Value Description

cleanse_thresh_value 0.33,0.66,1.0 This configuration will


specify the color for the
cleanse_thresh_color #d62800,#ffcf21,#84ae31
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 [name, location, mainPhoneNumber] The default fields


combination used to
SrcAccount [name, loc, mainPhoneNumber]
query completeness info.
HubContact [firstName, lastName]

SrcContact [firstName, lastName]

min_date_format MM/dd/yyyy HH:mm:ss When choosing the query


criteria of "From"
min_date_value 09/13/1990 00:00:00
calendar selector, the
oldest time users can
specify.

collectionsClassPath com/oracle/mdm/view/collections.xml These are the internally-


used configurations. Do
loggingClassPath logging.properties
not modify them.

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:

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 27 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Instructions for ACR 476


This topic is part of “Configuration Instructions for Enhancements and Updates” on page 39.

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

3 Lock the following projects:

■ 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

■ 03_sma_dll.sif

276 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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

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 fs, then the resulting directory structure is
similar to that shown below.

fs
smartanswer
export
import

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 27 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

b Click New, and then add the following values:

❏ 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.
b Click New, and then add the following values:

❏ 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&amp;SWEExtCmd=Execute&amp;UserName=
USERNAME&amp;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.
b Click New to create new operations using the values shown in the following table.

Name Method Display Name Authentication Type

Import Import None

Export Export None

278 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Name Method Display Name Authentication Type

Feedback Feedback None

Lookup Lookup None

RefreshKB Refresh None

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 Email Response,
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.

4 Lock the following projects:

■ Mail Agent
■ eMail Response

5 Import the SIF files you extracted in Step 2 on page 279 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

■ EMR_UI_Webtemplate.sif

■ EMR_UI_WF.sif

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 27 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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

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

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

Instructions for ACR 480


The following sections contain information about how to work with the seed data provided with ACR
480.

280 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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 Siebel Administrator, CG Key Account Manager
View

CS CG All High Level Planning List View Siebel Administrator, CG Key Account Manager

CS CG All Across Organizations High Level Siebel Administrator


Planning List View

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 Siebel Administrator, CG Key Account Manager


Admin View - SIS

CS CG Promotion Literature List View Siebel Administrator, CG Key Account Manager

CS CG Corporate Promotion Attachments Siebel Administrator, CG Key Account Manager


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 Siebel Administrator, CG Key Account Manager
View

SIA CS ADL Authorized Product View Siebel Administrator, CG Key Account Manager
CG Account Merchandising Location Product Siebel Administrator, CG Key Account Manager
View

CS Fund Transfer Admin View Siebel Administrator, CG Key Account Manager

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 28 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

View Responsibility

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

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:

New or
Needs LOV Type Language-
Modification? Code Display Value Independent Code Comments
New SVP Source Baseline PY Baseline PY Currency Order = 7
Currency

New SVP Source Baseline PY Baseline PY Cases Order = 8


Qty

New SVP Source Baseline Baseline Target Order = 9


Target Currency
Currency

New SVP Source Baseline Baseline Target Cases Order = 10


Target Qty

Modify SVP Source Incremental Baseline Incremental Change Order =


Qty Cases 11

Modify SVP Source Incremental Baseline Incremental Change Order =


Currency Currency 12

282 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

New or
Needs LOV Type Language-
Modification? Code Display Value Independent Code Comments

Modify SVP Source Consumed Qty Consumption Change Order =


Consumed Cases 13

Modify SVP Source Shipped Qty Shipments Shipped Change Order =


Cases 14

Modify SVP Source Target Basis Target Basis Currency Change Order =
Currency 15

Modify SVP Source Target Basis Target Basis Cases Change Order =
Qty 16

Modify SVP Source Target Target Planning Change Order =


Planning Currency 17
Currency

Modify SVP Source Target Target Planning Cases Change Order =


Planning Qty 18

Modify SVP Source Target Target Baseline Change Order =


Currency Currency 19

Modify SVP Source Target Qty Target Baseline Cases Change Order =
20

New CAMP_EXEC_S In Progress In Progress Translate = Y


TATUS

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 28 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

New or
Needs LOV Type Language-
Modification? Code Display Value Independent Code Comments

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 Reduction Reduction Amount Order = 1


ION_SIZE Amount

New PRICE_REDUCT Reduction % Reduction % Order = 2


ION_SIZE

New PRICE_REDUCT Reduced Price Reduced Price Order = 3


ION_SIZE

New PRICE_ TPR TPR Order = 1


REDUCTION_T
YPE

New PRICE_ Special Pack Special Pack Order = 2


REDUCTION_T
YPE

New PRICE_ BOGO BOGO Order = 3


REDUCTION_T
YPE

New PRICE_ EDLP/EDLC EDLP/EDLC Order = 4


REDUCTION_T
YPE

New PRICE_ Coupon Coupon Order = 5


REDUCTION_T
YPE

284 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

New or
Needs LOV Type Language-
Modification? Code Display Value Independent Code Comments

New FD_SLOTFEE_P Bill Back Bill Back Order = 1


AY_MTH

New FD_SLOTFEE_P Deduction Deduction Order = 2


AY_MTH

New FD_SLOTFEE_P Check Check Order = 3


AY_MTH

New OTHER_FD_SP Bill Back Bill Back Order = 1


ND_PAY_MTH

New OTHER_FD_SP Deduction Deduction Order = 2


ND_PAY_MTH

New OTHER_FD_SP Check Check Order = 3


ND_PAY_MTH

New SH_VAR_SPEN Bill Back Bill Back Order = 1


D_MTH

New SH_VAR_SPEN Deduction Deduction Order = 2


D_MTH

New SH_VAR_SPEN Off-Invoice Off-Invoice Order = 3


D_MTH

New TACTICS_TYPE Display & TPR Display & TPR 10%


10%

New TACTICS_TYPE Display & TPR Display & TPR 15%


15%

New TACTICS_TYPE Display & TPR Display & TPR 5%


5%

New TACTICS_TYPE F&D F&D


New TACTICS_TYPE F&D 10% F&D 10%

New TACTICS_TYPE F&D 15% F&D 15%

New TACTICS_TYPE F&D 5% F&D 5%

New TACTICS_TYPE Feature & TPR Feature & TPR 10%


10%

New TACTICS_TYPE Feature & TPR Feature & TPR 15%


15%

New TACTICS_TYPE Feature & TPR Feature & TPR 5%


5%

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 28 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

New or
Needs LOV Type Language-
Modification? Code Display Value Independent Code Comments

Modify PAYMENT_MET Claim Claim Order = 23


HOD_CODE

Modify PAYMENT_TYPE Claim Claim


_CODE

3 Click the Clear Cache button.

State Model
Use the following procedure to add State Models.

To add State Models


1 Connect to the Siebel application.

2 Navigate to Site Map > Administration - Application > State Models.

New? State Model Name Business Component Field

New CS Claim Status CS Claims Payment Status

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:

Transition From Transition To


Resolved Closed

5 Add new states for the State Models in the following table:

New or Needs
Modification? State Model Name Business Component Field

Modified CS CG Promo CS CG Promotion Category Deal Payment Status


Category Payment Payment
Status

Modified CS Check Payment CPG Check Payment Payment Status


Status

Modified CS Deduction CPG Deduction Resolution - Payment Status


Payment Status Payment

286 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

New or Needs
Modification? State Model Name Business Component Field

Modified CS Promo Payment CPG Promo Deal Payment Payment Status


Status

Modified CS Promoted Product CG Promo Product Fund Payment Payment Status


Payment Status

New CS Claim Payment CS Claim Payments Payment Status


Status

6 Add the new states for the State Models: Requested, Approved, and Rejected.

7 Add or modify the transactions for the State Models:

Transition From Transition To

Pending Requested

Pending Cancelled

Requested Cancelled

Approved Cancelled

Approved Submitted

Rejected Pending

Rejected Requested

Rejected Cancelled

Submitted Paid

Submitted Cancelled
Paid Voided

8 Add new states for the following State Model:

New? State Model Name Business Component Field

New CS CG Deal Payment Status CS CG Deal Payment Approval Payment Status

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:

Transition From Transition To

Requested Approved

Requested Rejected

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 28 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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


1 Connect to the Siebel application.

2 Navigate to Site Map > Administration - Audit Trail > and create new Audit Trails with the
information in the following tables:

Audit Trail Business


New? 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

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)

288 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

7 Connect to the Siebel application.

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 13 contains details about the SVPFilterYear profile variable, Table 14 contains information about
the SVP Current Year Filter rule set, and Table 15 contains information about the Current Filter rule.

Table 13. 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 14. 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 15. 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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 28 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

290 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Instructions for ACR 488


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

For information about how to implement ACR 488, within My Oracle Support, navigate to the
Knowledge tab and search for Doc ID 880604.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.

Instructions for ACR 494


For instructions about how to implement ACR 494, within My Oracle Support, navigate to the
Knowledge tab and search for Doc ID 1061483.1.

Instructions for ACR 499


The following sections contain detailed information about the functionality provided by ACR 499, as
well as instructions for implementing the ACR.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 29 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Release Notes for ACR 499


The following section contains information about known issues with ACR 499, as well as any
applicable workaround information.

OK Button Disabled
Category: Quotes and Orders

Subcategory: Asset-Based Ordering

Product Version: 8.1.1.4

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

Product Version: 8.1.1.4

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.

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.

4 In Siebel Tools, lock all of the following projects:

❏ ABO Bulk Request

❏ ABO Bulk Request UI

❏ Asset Management

❏ Contact

292 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ ISS Product Loader

❏ ISS Promotion Admin

❏ ISS Promotion Integration

❏ List Mgmt (UI)

❏ Order Entry

❏ Product

❏ Product Selection UI

❏ Quote

❏ Quote (UI)

❏ SIS OM Base Architecture

❏ Srvagree

❏ Symbolic Strings

❏ VORD Compound Product Validation Engine

❏ VORD Network Order Entry

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

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 29 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ Applets

❏ Views

❏ Screens

NOTE: If you have not locked the required projects, you may receive a warning error message.
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


1 Log into Siebel Tools.

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.

294 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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 projects


1 Stop the Siebel Server, if it is running.

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.

4 Start the Siebel Server.

Importing Seed Data for ACR 499


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

To import the seed data for ACR 499


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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 29 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 Run the following command:

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


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

<Tools Install Directory> - Replace with your Siebel Tools install directory

<ODBC Source Name> - Replace with the 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 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:

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


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

<Tools Install Directory> - Replace with your Siebel Tools install directory

<ODBC Source Name> - Replace with the ODBC name

<Database Platform> - Replace with your database platform (ORACLE, DB2UDB or MSSQL)

b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.

7 If you are installing a language other than ENU, perform the following steps:

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

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


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

<Tools Install Directory> - Replace with your Siebel Tools install directory

<ODBC Source Name> - Replace with the ODBC name

xxx - Replace with your language name

296 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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


1 Navigate to Administration - Application > Views.

2 Verify the following views.

Default
Local
View Name Description Access

ABO Bulk Request Action Set Quotes View ABO Bulk Request Action Set Quotes Y
View

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 Y
Exceptions View

To verify the List of Values


1 Navigate to Administration - Data > LOV Explorer and verify the following values:

Type Translate

ABO_BR_ACTSET_TEMPLTE_TYPE Y

ABO_BR_TEMPLTE_INSTANCE_SCOPE Y

ABO_BR_TEMPLTE_INSTANCE_TYPE Y

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 29 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Display Replication
Type Value LIC Language Name Order Active Translate Level

QUOTE_TYPE Bulk Request Bulk English-American 52 Y Y All


Template Request
Quote Template
Quote

QUOTE_TYPE Bulk Request Bulk English-American 53 Y Y All


Explode Request
Quote Explode
Quote

ABO_BR_INSTAN Network Id Network English-American 3 Y Y All


CE_TYPE Id

ABO_BR_INSTAN Agreement Agreeme English-American 4 Y Y All


CE_TYPE Id nt Id

LISTMGMT_LIST_ Assets Assets English-American 3 Y Y All


TYPE

SLM_FIELD_DISP Assets Assets English-American - Y Y All


LAY

SLM_LST_CATEG Assets SLM List English-American - Y N All


ORY Member -
Asset

ABO_BR_SUBMIT Processing Processin English-American 5 Y Y All


_STATUS g

ABO_BR_SUBMIT Queued Queued English-American 6 Y Y All


_STATUS

WF_GROUP_CD ABO Bulk ABO Bulk English-American 1 Y Y All


Request Request

ABO_BR_ACTSET New New English-American 1 Y Y All


_TEMPLTE_TYPE

ABO_BR_ACTSET Modify Modify English-American 2 Y Y All


_TEMPLTE_TYPE

ABO_BR_ACTSET Upgrade Upgrade English-American 3 Y Y All


_TEMPLTE_TYPE

ABO_BR_TEMPLT All All English-American 1 Y Y All


E_INSTANCE_SCO
PE

ABO_BR_TEMPLT Include Include English-American 2 Y Y All


E_INSTANCE_SCO
PE

ABO_BR_TEMPLT Exclude Exclude English-American 3 Y Y All


E_INSTANCE_SCO
PE

ABO_BR_HEADER Explode Fault Explode English-American 9 Y Y All


_STATUS Fault

298 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Display Replication
Type Value LIC Language Name Order Active Translate Level

ABO_BR_HEADER Exploded Exploded English-American 10 Y Y All


_STATUS

ABO_BR_HEADER Exploding Explodin English-American 11 Y Y All


_STATUS g

FS_ORDER_TYPE Bulk Request Bulk English-American 18 Y Y All


Explode Request
Order Explode
Order

ABO_BR_ACTION Replace Replace English-American 7 Y Y All


_CODE

ABO_BR_TEMPLT Contact Id Contact English-American 1 Y Y All


E_INSTANCE_TYP Id
E

ABO_BR_TEMPLT Service Id Service English-American 2 Y Y All


E_INSTANCE_TYP Id
E

ABO_BR_EXCEPTI E&C E&C English-American 1 Y Y All


ON_TYPE

ABO_BR_EXCEPTI Explode Explode English-American 6 Y Y All


ON_TYPE Error Error

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

To verify the ABOBulkRequestCheckEligibility signal


1 Navigate to Administration - Order Management -> Signals.

2 In the Signals list view, confirm that the signal ABOBulkRequestCheckEligibility 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.

Sequence Service Type Service Name Service Method

1 Workflow PSP Driver Workflow Process RunProcess

5 In the Parameters list view, verify the following.

Name Value

CPScope Whole

Pick Mode Post-Pick

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 29 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Name Value

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

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.

In/ On
Name Out Type Null Path Mode Source Type

Account Id In ID Ignore $Current/Header/Account Any Instance


Id

Action Code In Text Ignore $Current/Line Item/Action Any Instance


Code

City In Text Ignore $Current/Header/City Any Instance

Class Id In ID Ignore $Current/Line Item/Class Any Instance


Id

Country In Text Ignore $Current/Header/Country Any Instance

Covered In ID Ignore $Current/Line Item/ Agreement Instance


Asset Covered Asset Product Id
Product Id Order
$Current/Line Item/
Covered Asset Product Id Quote

$Current/Line Item/
Covered Asset Product Id

Covered Line In ID Ignore $Current/Line Item/ Agreement Instance


Item Id Covered Line Item Id

$Current/Line Item/ Order


Covered Line Item Id

$Current/Line Item/ Quote


Covered Line Item Id

300 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

In/ On
Name Out Type Null Path Mode Source Type

Covered In ID Ignore $Current/Line Item/ Any Instance


Product Id Covered Product Id

Eligibility In/Out Text Ignore $Current/Line Item/ Any Instance


Reason Eligibility Reason

Eligibility In/Out Text Ignore $Current/Line Item/ Any Instance


Status Eligibility Status

Exclude In/Out Boole Ignore $Current/Line Item/ Any Instance


Pricing Flag an Exclude Pricing Flag

Id In ID Ignore $Current/Line Item/Id Any Instance

Inclusive In Boole Ignore $Current/Line Item/ Any Instance


Eligibility an Inclusive Eligibility Flag
Flag

Name In Text Ignore $Current/Line Item/Name Any Instance

Parent Item In ID Ignore $Current/Line Item/Parent Any Instance


Id Id

Post Pick In Text Ignore $Current/Line Item/Post Any Instance


Pick CD

Postal Code In Text Ignore $Current/Header/Postal Any Instance


Code

Pre Pick In Boole Ignore $Current/Line Item/Pre Any Instance


an Pick CD

Pricelist Id In ID Ignore $Current/Line Item/Item Agreement Instance


Price List Id

$Current/Line Item/Item Config


Price List Id

$Current/Line Item/Item Order


Price List Id

$Current/Line Item/Item Quote


Price List Id

Prod Prom Id In ID Ignore $Current/Line Item/Prod Any Instance


Prom Id

Product Id In ID Ignore $Current/Line Item/ Any Instance


Product Id

Product Line In ID Ignore $Current/Line Item/ Any Instance


Id Product Line Id

Product Port In ID Ignore $Current/Line Item/Port Any Instance


Id Item Id

Promotion In Boole Ignore $Current/Line Item/ Quote Instance


Item Flag an Promotion Item Flag

Quantity In Integ Ignore $Current/Line Item/ Any Instance


er Quantity

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 30 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

In/ On
Name Out Type Null Path Mode Source Type

Root Bundle In Boole Ignore $Current/Line Item/Root Agreement Instance


Flag an Bundle Flag

$Current/Line Item/Root Order


Bundle Flag

$Current/Line Item/Root Quote


Bundle Flag

Sales In Boole Ignore $Current/Line Item/Sales Agreement Instance


Service Flag an Service Flag

$Current/Line Item/Sales Order


Service Flag

$Current/Line Item/Sales Quote


Service Flag

State In Text Ignore $Current/Header/State Any Instance

Usage Asset In ID Ignore $Current/Line Item/Usage Any Instance


Product Id Asset Product Id

$Current/Line Item/ Order


Covered Asset Id

$Current/Line Item/Usage Quote


Asset Product Id

5 In the Modes view, verify the following.

Mode Object

Any Line Item

Data Maps
Use the following procedures to verify the ACR 499 data maps.

To verify the ABO Bulk Request Action Set Agreement Inbound Map
1 Navigate to Administration Integration > Data Map Editor.

302 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Source Target Source


Name Component Component 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

To verify the ABO Bulk Request Action Set Asset Inbound Map
1 Navigate to Administration Integration > Data Map Editor.

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.

Source
Name 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

To verify the ABO Bulk Request Action Set Contact Inbound Map
1 Navigate to Administration Integration > Data Map Editor.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 30 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Target
Name Source Component Component Source Expression Target Field Name

Action Set Account Action Set [Name] Customer Account

[Account Id] Customer Account Id

Instance Related Contact Instance [Email Address] Email Address

[Contact Id] Unique Id

To verify the ABO Bulk Request Action Set Network Inbound Map
1 Navigate to Administration Integration > Data Map Editor.

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.

Integration Target
Name Component Component Source Expression Target Field Name

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

To verify the ABO Bulk Request All Contact Inbound Map


1 Navigate to Administration Integration > Data Map Editor.

304 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Source Target
Name Component Component Source Expression Target Field Name

Action Set Account Header [Name] Customer Account

[Account Id] Customer Account Id

Instance Related Contact Line Item [Email Address] Email Address

[Contact Id] Unique Id

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 30 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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 New ABO Bulk Request


Process

2 ABO Bulk Request - Modify Promotion New ABO Bulk Request


Products & Services Process

3 ABO Bulk Request - Edit Iterate Process New ABO Bulk Request

4 ABO Bulk Request - Disconnect Iterate Modified ABO Bulk Request


Process

5 ABO Bulk Request - Cancel Process Modified ABO Bulk Request


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 New ABO Bulk Request


Workflow

9 ABO Bulk Request - Promotion Disconnect New ABO Bulk Request


Sub Process

10 ABO Bulk Request - Edit Complex Asset New ABO Bulk Request
Workflow

11 ABO Bulk Request - Promotion Disconnect New ABO Bulk Request


Integration SubProcess

12 ABO Bulk Request - Disconnect Asset Sub- New ABO Bulk Request
process

13 ABO Bulk Request - Edit Promotion Related New ABO Bulk Request
Asset Workflow

14 ABO Bulk Request - Promotion - Update New ABO Bulk Request


Matched Items Sub Process

15 ABO Bulk Request - Promotion - Add Missed New ABO Bulk Request
Items Sub Process

16 ABO Bulk Request - Add Sub-Process Modified ABO Bulk Request


Workflow

17 ABO Bulk Request - ApplyProductPromotion New ABO Bulk Request

18 ABO Bulk Request - All Instances Sub Modified ABO Bulk Request
Process

306 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Sequence Workflow Name New/Modified Project

19 ABO Bulk Request - Modify Sub-Process Modified ABO Bulk Request


Workflow

20 ABO Bulk Request - Delete Sub-Process Modified ABO Bulk Request


Workflow

21 ABO Bulk Request - Upgrade Sub-Process Modified ABO Bulk Request


Workflow

22 ABO Bulk Request - Suspend_Resume Sub- Modified ABO Bulk Request


Process Workflow.xml

23 ABO Bulk Request - ModifyWebService- New ABO Bulk Request


Order

24 ABO Bulk Request - Check Eligibility & New ABO Bulk Request
Compatibility

25 ABO Bulk Request - Process Action Sub- Modified ABO Bulk Request
Process Workflow

26 ABO Bulk Request - Disconnect Products & New ABO Bulk Request
Services Process

27 ABO Bulk Request - Inclusive Process Modified ABO Bulk Request


Action Sub-Process Workflow

28 ABO Bulk Request - All Exclusive Process Modified ABO Bulk Request
Action Sub-Process Workflow

29 ABO Bulk Request - Prepare Action Set Sub- Modified ABO Bulk Request
Process Workflow

30 ABO Bulk Request - Sub Process Workflow Modified ABO Bulk Request

31 ABO Bulk Request - Parallel Sub Process Modified ABO Bulk Request
Workflow

32 ABO Bulk Request - Submit Process Modified ABO Bulk Request


Workflow

33 ABO Bulk Request - Submit Driver Process Modified ABO Bulk Request
Workflow

34 ABO Bulk Request Add Item Customize Modified ABO Bulk Request
SubProcess Quotes

35 ABO Bulk Request Add Item Customize Modified ABO Bulk Request
Process

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 30 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

308 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Sequence Workflow Name

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

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.

Default
Local
View Name Description Access

ABO Bulk Request Action Set Quotes View ABO Bulk Request Action Set Y
Quotes View

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 - Y
All

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 Y
Exceptions View

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 30 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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


1 Navigate to Administration - Order Management > Variable Maps.

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.

NOTE: The Path, Mode, and Source Type fields are shown in the Variable Sources view.

Name In/Out Type On Null Path Mode Source Type


Account Id In ID Ignore $Current/Header/ Bulk Request Instance
Customer Account Id

$Current/ActionSet/ External Bulk


Customer Account Id Request

5 In the Modes view, create records as shown in the following table.

Mode Object Name

Bulk Request Header

External Bulk Request ActionSet

310 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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
1 Navigate to Administration - Order Management > Variable Maps.

2 Query for the Variable Product Eligibility Variable Map - Row Set 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.

NOTE: The Path, Mode, and Source Type fields are shown in the Variable Sources view.

Source
Name In/Out Type On Null Path Mode Type

Account Id In ID Ignore $Current/Line Item/ External Instance


Account Id Bulk
Request

Agreement Id In ID Ignore $Current/Instance/ External Instance


Agreement Id Bulk
Request

Asset Id In ID Ignore $Current/Instance/Asset External Instance


Id Bulk
Request

Compound In Text Ignore $Current/Instance/ External Instance


Product Compound Product Bulk
Number Number Request

Email Address In Text Ignore $Current/Instance/Email External Instance


Address Bulk
Request

Product Name In Text Ignore $Current/Instance/ External Instance


Product Name Bulk
Request

Root Asset Id In ID Ignore $Current/Instance/Root External Instance


Asset Id Bulk
Request

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 31 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Source
Name In/Out Type On Null Path Mode Type

Service Id In ID Ignore $Current/Instance/ External Instance


Service Id Bulk
Request

Unique Id In ID Ignore $Current/Instance/ External Instance


Unique Id Bulk
Request

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.

7 Click Release New Version and select Menu > Clear Cache.

To modify the Cfg Eligibility Variable Map - Context variable map


1 Navigate to Administration - Order Management > Variable Maps.

2 Query for the Cfg Eligibility Variable Map - Context variable map and lock the object.

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

NOTE: The Path, Mode, and Source Type fields are shown in the Variable Sources view.

Source
Name In/Out Type On Null Path Mode Type

Account Id In ID Ignore $Current/Header/ Bulk Request Instance


Customer Account Id
External Bulk
Request

5 In the Modes view, create records as shown in the following table:

Mode Object Name

Bulk Request Header

Any Header

6 Navigate back to the Variable Maps link and query for Cfg Eligibility Variable Map - Context again.

7 Click Release New Version and select Menu > Clear Cache.

312 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

To modify the Default Eligibility Variable Map - Context variable map


1 Navigate to Administration - Order Management > Variable Maps.

2 Query for the Default 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.

NOTE: The Path, Mode, and Source Type fields are shown in the Variable Sources view.

Source
Name In/Out Type On Null Path Mode Type

Account Id In ID Ignore $Current/Header/ Bulk Request Instance


Customer Account Id

$Current/ActionSet/ External Bulk


Customer Account Id Request

5 In the Modes view, create records as shown in the following table:

Mode Object Name

Bulk Request Header

External Bulk Request ActionSet

6 Navigate back to the Variable Maps link and query for Default Eligibility Variable Map - Context
again.

7 Click Release New Version and select Menu > Clear Cache.

To modify the Default Pricing Eligibility Variable Map - Row Set variable map
1 Navigate to Administration - Order Management > Variable Maps.

2 Query for the Default Pricing Eligibility Variable Map - Row Set variable map and lock the object.

3 Click the Work Space link.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 31 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

NOTE: The Path, Mode, and Source Type fields are shown in the Variable Sources view.

Source
Name In/Out Type On Null Path Mode Type

Action In/Out Text Ignore $Current/Line Item/Action External Instanc


Code Code Bulk e
Request

Prod In/Out ID Ignore $Current/Line Item/Prod External Instanc


Prom Id Prom Id Bulk e
Request

Prod In/Out ID Ignore $Current/Line Item/Prod External Instanc


Prom Prom Instance Id Bulk e
Instance Request
Id

Prod In/Out ID Ignore $Current/Line Item/Prod External Instanc


Prom Rule Prom Rule Id Bulk e
Id Request

5 In the Modes view, create a record with the following values:

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

7 Click Release New Version and select Menu > Clear Cache.

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 IO Map


1 Navigate to Administration Integration > Data Map Editor.

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.

314 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

5 Verify the following records in the Integration Component Map Applet.

Name Source Component Target Component

Header_to_Header Header Header

Line Item_to_Line Item Line Item Line Item

XA_to_XA XA XA

To modify the Bulk Request Quote IO Map


1 Navigate to Administration Integration > Data Map Editor.

2 Query for Bulk Request Quote IO Map.

3 Delete all the records from Integration Component Map Applet.

4 In the Integration Object Map Applet, click on Auto-Map.

5 Verify the following records in the Integration Component Map Applet.

Name Source Component Target Component

Header_to_Header Header Header

Line Item_to_Line Item Line Item Line Item

XA_to_XA XA XA

To modify the ABO Bulk Request SIS OM Order IO Map


1 Navigate to Administration Integration > Data Map Editor.

2 Query for ABO Bulk Request SIS OM Order IO Map.


3 Delete all the records from Integration Component Map Applet.

4 In the Integration Object Map Applet, click on Auto-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 three Integration
Component Maps.

Source Expression Target Field Name


[Created] Created

[Created By] Created By

[Id] Id

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 31 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Source Expression Target Field Name

[Mod Id] Mod Id

[Updated] Updated

[Updated By] Updated By

[Conflict Id] Conflict Id

9 Delete the following fields from Integration Field Map Applet, corresponding to the
Header_to_Header mappings.

Source Expression Target Field Name

[Revision Number] Revision Number

[Order Number] Order Number

[Quote Number] Quote Number

10 Delete the following fields from Integration Field Map Applet, corresponding to the XA_to_XA
mappings.

Source Expression Target Field Name

[Parent Id] Parent Id

To modify the ABO Bulk Request SIS OM Quote IO Map


1 Navigate to Administration Integration > Data Map Editor.

2 Query for the ABO Bulk Request SIS OM Quote IO Map.

3 Delete all the records from Integration Component Map Applet.


4 In the Integration Object Map Applet, click on Auto-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 three Integration
Component Maps.

Source Expression Target Field Name

[Created] Created

[Created By] Created By

[Id] Id

316 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Source Expression Target Field Name

[Mod Id] Mod Id

[Updated] Updated

[Updated By] Updated By

[Conflict Id] Conflict Id

9 Delete the following fields from Integration Field Map Applet, corresponding to the
Header_to_Header mappings.

Source Expression Target Field Name

[Parent Quote Id] Parent Quote Id

[Revision] Revision

[Quote Number] Quote Number

10 Delete the following fields from Integration Field Map Applet, corresponding to the Line
Item_to_Line Item mappings.

Source Expression Target Field Name

[Parent Id] Parent Id

11 Delete the following fields from Integration Field Map Applet, corresponding to the XA_to_XA
mappings.

Source Expression Target Field Name

[Parent Id] Parent Id

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:

Replic
Language ation
Type Display Value LIC Name Order Active Translate Level

LOV_TYPE UINBOX_INBOX UINBOX_IN English- - Y Y All


_TYPE BOX_TYPE American

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 31 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

2 Navigate to Inbox Administration > All Inbox Types and verify that the records listed in the
following table exist.

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

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:

Language Display Name

English-American Bulk Request Exception

Instructions for ACR 500


The following sections contain information about how to apply and configure ACR 500.

Release Notes for ACR 500


The following section contains information about known issues with ACR 500, as well as any
applicable workarounds.

Wrong Display Mode in Message Type


Category: Order Administration

Subcategory: Unified Messaging

Product Version: 8.1.1.4

Change Request: 12-1YMMELB

In the DEU application, the display mode in message type is ENU, not DEU.

Use the following workaround to address this issue:

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

❏ Promotion - Broken Commitment Error - Debundle

❏ Promotion - Component Commitment Penalty

❏ Promotion - Bottomup Recommendation For Assets

318 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Message Type Display Mode (ENU) Display Mode (DEU)

Promotion - Multiple Commitment Broken Active Aktiv


Message - Debundle

Promotion - Broken Commitment Error - Active Aktiv


Debundle

Promotion - Component Commitment Penalty Passive Passiv

Promotion - Bottomup Recommendation For Active List Aktive Liste


Assets

Promotion - No Promotion Recommendations Active Aktiv

Promotion - Multiple Commitment Broken Active Aktiv


Message - Components

Promotion - Broken Component Commitment Active Aktiv


Error

3 For each of the message types mentioned above, select Menu > Clear Cache.

Error Messages Occur When Debundling Promotions


Category: Product Promotions

Subcategory: Administration

Product Version: 8.1.1.4

Change Request: 12-20JI6NQ

In the DEU application, users receive an error message when they try to debundle promotions.

Use the following workaround to address this issue:

NOTE: Before you begin the following procedures, within Siebel Tools, query for the ISS Promotion
Workflow project, and lock it.

To edit the ISS 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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 31 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 In the revised workflow, select Edit Workflow Process from the menu, and add the following
Process Property.

Name Display Name In/Out Business Object Data Type

Root Account Id Root Account Id In/Out Account String

4 Add the following output argument in the Get Account Details step:

Business Business
Property Name Type Component Name Component Field

Root Account Id Business Component Account Master Account Id

5 Add the following input argument in the Disconnect Old Promotion step:

Subprocess Input Type Property Name

Root Account Id Process Property Root Account Id

6 Publish and activate the workflow.

To edit the ISS Promotion Split Process workflow


1 Within Siebel Tools, navigate to Object Explorer, and select Workflow Processes.

2 Query for the ISS Promotion Split Process workflow and revise the workflow.

3 In the revised workflow, select Edit Workflow Process from the menu, and add the following
process property:

Name Display Name In/Out Business Object Data Type

Root Account Id Root Account Id In/Out Account String

4 Add the following output argument in the Get Account Details step:

Business Business
Property Name Type Component Name Component Field

Root Account Id Business Component Account Master Account Id

5 Add the following input argument in the Disconnect Old Promotion step.

Subprocess Input Type Property Name

Root Account Id Process Property Root Account Id

320 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

6 Publish and activate the workflow.

To edit the ISS 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.

Name Display Name In/Out Business Object Data Type


Root Account Id Root Account Id In/Out Account String

4 Add the following output argument in the Get Account Details step:

Business Business Component


Property Name Type Component Name Field

Root Account Id Business Component Account Master Account Id

5 Add the following input argument in the Disconnect Old Promotion step:

Subprocess Input Type Property Name

Root Account Id Process Property Root Account Id

6 Publish and activate the workflow.

To edit the ISS Promotion Debundle Integration SubProcess workflow


1 Within Siebel Tools, navigate to Object Explorer, and select Workflow Processes.

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.

Business
Name Display Name In/Out Object Data Type

Root Account Id Root Account Id In/Out Account String

4 Add the following input argument in the Disconnect SubProcess step:

Subprocess Input Type Property Name

Root Account Id Process Property Root Account Id

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 32 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

5 Publish and activate the workflow.

To edit the ISS Promotion Debundle Process workflow


1 Within Siebel Tools, navigate to Object Explorer, and select Workflow Processes.

2 Query for the ISS Promotion Debundle Process workflow and revise the workflow.

3 In the revised workflow, select Edit Workflow Process from the menu, and add the following
process property:

Name Display Name In/Out Business Object Data Type


Root Account Id Root Account Id In/Out Account String

4 Add the following output argument in the Get Account Details step:

Business Business Component


Property Name Type Component Name Field

Root Account Id Business Component Account Master Account Id

5 Add the following input argument in the Debundle Sub-process step:

Subprocess Input Type Property Name

Root Account Id Process Property Root Account Id

6 Publish and activate the workflow.

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.

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.

4 In Siebel Tools, lock all of the following projects:

■ Account

322 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ Asset Management

■ Cfg RTC

■ FS Agreement

■ ISS Authoring Admin

■ ISS Promotion Admin

■ ISS Promotion Integration

■ ISS Promotion Split Merge

■ ISS Promotion Workflow

■ MACD Performance

■ Order Entry

■ Product Selection UI

■ Quote

■ Quote (UI)

■ SIS OM Base Architecture

■ Symbolic Strings

■ Table Order

■ Table Product

■ Table ProductPromotion

■ Table Quote

■ UMSUI

■ VORD Compound Product Validation Engine

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 32 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ Links.sif

■ Business Objects.sif

■ Integration Objects.sif

■ Applets.sif

■ Views.sif

■ Screens.sif

NOTE: If you have not locked the required projects, you may receive a warning error message.
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:

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

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.

11 Start the Siebel Server.


12 Select Workflow Process Object in OBLE.

324 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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 New ISS Promotion Workflow


Component Penalty Charges
SubProcess

2 ISS Promotion Calculate Related New ISS Promotion Workflow


Objects Penalty Charges
SubProcess

3 ISS Promotion Disconnect New ISS Promotion Workflow


Component SubProcess

4 ISS Promotion Disconnect Process Modified ISS Promotion Workflow

5 ISS Promotion Disconnect Modified ISS Promotion Workflow


Integration SubProcess

6 ISS Promotion Upgrade Charge New ISS Promotion Workflow


Proration SubProcess

7 ISS Promotion Create Agreement Modified ISS Promotion Workflow


Details

8 ISS Promotion Agreement Modified ISS Promotion Workflow


Management Sub Process

9 ISS Promotion Upgrade Check New ISS Promotion Workflow


Agreement SubProcess

10 SIS OM Edit Service Order Line Modified SIS OM Base Architecture


Item

11 ISS Promotion Debundle New ISS Promotion Workflow


Integration SubProcess

12 ISS Promotion Debundle Process New ISS Promotion Workflow

13 ISS Promotion Recommendation New ISS Promotion Workflow


For Assets

14 ISS Add To Promotion Sub Process New ISS Promotion Workflow

15 ISS Promotion Check Order Item New ISS Promotion Workflow


Sub Process

16 ISS Promotion Check Quote Item New ISS Promotion Workflow


Sub Process

17 ISS Promotion Add To Promotion New ISS Promotion Workflow


Process

18 ISS Promotion Commitment Modified ISS Promotion Workflow


Compliance Check SubProcess

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 32 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Sequence Workflow Name New/Modified? Project

19 ISS Promotion Disconnect Process Modified ISS Promotion Workflow


- for Verify

20 ISS Promotion Edit Integration Modified ISS Promotion Workflow


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 & Modified SIS OM Base Architecture


Services Process

27 SIS OM Disconnect Asset Sub- Modified SIS OM Base Architecture


process

28 SIS OM Edit Complex Asset Modified SIS OM Base Architecture


Workflow

29 SIS OM Edit Delta Quote Line Item Modified SIS OM Base Architecture

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:

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

326 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Sequence Workflow

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

17 Navigate to Administration - Runtime Events, and choose to reload runtime events for each
event.

Importing Seed Data for ACR 500


1 Navigate to the directory in which you installed Siebel Tools and change the directory to
REPATCH\ACR500.

NOTE: Before you perform the following step, make sure that the dataimp.exe file exists in the
<Tools Install Directory>/bin directory.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 32 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

2 Run the following command:

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


Directory>\REPATCH\ACR500\SeedData\ACR500_Seed.dat /l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <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

<Tools Install Directory> - Replace with your Siebel Tools install directory

<ODBC Source Name> - Replace with your ODBC name

<Database Platform> - Replace with your database platform (ORACLE, DB2UDB or MSSQL)

3 Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.

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.

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


Directory>\REPATCH\ ACR500\SeedData\ENU\seed_locale_ENU.dat /l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools
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

<Tools Install Directory> - Replace with your Siebel Tools install directory

<ODBC Source Name> - Replace with the ODBC name

<Database Platform> - Replace with the database platform (ORACLE, DB2UDB or MSSQL)

b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.
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 332.
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.

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


Directory>\REPATCH\ ACR500\SeedData\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

<Tools Install Directory> - Replace with your Siebel Tools install directory

<ODBC Source Name> - Replace with the ODBC name

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

328 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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.

4 Enter the directory path and name of the file you are going to import.

5 Click the Import button to import the data.

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:

Default
Local
View Name Description 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

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 32 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

2 Modify the values listed in the following table:

Display Language Replicati


Type Value LIC Name Order Active Translate on Level

PROMO_UPGRADE_ Original Original English- 1 Y Y All


START_CD Start Start American

PROMO_UPGRADE_ Original Original English- 2 Y Y All


START_CD End End American

PROMO_UPGRADE_ Now Now English- 3 Y Y All


START_CD American

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


1 Navigate to Administration - Order Management > Variable Maps.

2 Query for the Variable map Default Eligibility Variable Map - Context and lock the object.

3 Click on the Work Space link.

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

Name In/Out Type On Null Path Mode Source Type

Account In Boolean Ignore $Current/ AccountHeader Instance


Contracted AccountHeader/Use
Products Only Contracted Products
Flag Only Flag

Account Id In ID Ignore $Current/ AccountHeader Instance


AccountHeader/Id

Account Type In Text Ignore $Current/ AccountHeader Instance


AccountHeader/Type

City In Text Ignore $Current/ AccountHeader Instance


AccountHeader/
Primary Account City

Country In Text Ignore $Current/ AccountHeader Instance


AccountHeader/
Primary Account
Country

330 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Name In/Out Type On Null Path Mode Source Type

Postal Code In Text Ignore $Current/ AccountHeader Instance


AccountHeader/
Primary Account
Postal Code

State In Text Ignore $Current/ AccountHeader Instance


AccountHeader/
Primary Account State

5 In the Modes view, create a record with the following values:

Mode Object Name

AccountHeader AccountHeader

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


1 Navigate to Administration - Order Management > Variable Maps.

2 Query for the Variable map Default Eligibility Variable Map - Row Set ProdProm and lock the
object.

3 Click on the Work Space link.

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

Name In/Out Type On Null Path Mode Source Type

City In Text Ignore $Current/ AccountHeader Instance


AccountHeader/
Primary Account
City

Country In Text Ignore $Current/ AccountHeader Instance


AccountHeader/
Primary Account
Country

Postal Code In Text Ignore $Current/ AccountHeader Instance


AccountHeader/
Primary Account
Postal Code

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 33 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Name In/Out Type On Null Path Mode Source Type

State In Text Ignore $Current/ AccountHeader Instance


AccountHeader/
Primary Account
State

Price List Id In ID Ignore $Current/ AccountHeader Instance


AccountHeader/
Price List Id

5 In the Modes view, create a record with the following values:

Mode Object Name

AccountHeader ProdProm Line Item

6 Navigate back to the Variable Maps link and query for Default Eligibility Variable Map - Row Set
ProdProm again.

7 Click Release New Version and select Menu > Clear Cache.

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:

System
Preference
System Preference Name Value Description

All Assets Y ACR500: Asset Based Promotions


Recommendation and Apply

Promotion Component Commitment Y ACR 500

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


1 Navigate to Administration - Application > Views.

332 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

2 Verify the following views.

Default
Local
View Name Description 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

To verify the Lists of Values for ACR 500


1 Navigate to Administration - Data > LOV Explorer and verify the following values:

Type Translate

PROMO_AGGREGATE_DURATION Y

PROMO_OPER_TYPE Y

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 are the same. The Language Name is English-American for all the LOV values.

Display Language Replication


Type Value LIC Name Order Active Translate Level

PROMO_OPER_TYPE Merge MERGE English- 1 Y Y All


American

PROMO_OPER_TYPE Split SPLIT English- 2 Y Y All


American

PROMO_OPER_TYPE Upgrade UPGRADE English- 3 Y Y All


American

PROMO_AGGREGATE_D New New English- 1 Y Y All


URATION Duration Duration American

PROMO_AGGREGATE_D Original - Original - English- 2 Y Y All


URATION Maximum Maximum American

PROMO_AGGREGATE_D Original - Original - English- 3 Y Y All


URATION Minimum Minimum American

PROMO_UPGRADE_STA Earliest Earliest English- 4 Y Y All


RT_CD Start Start American

PROMO_UPGRADE_STA Earliest End Earliest End English- 5 Y Y All


RT_CD American

PROMO_UPGRADE_STA Latest Start Latest Start English- 6 Y Y All


RT_CD American

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 33 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Display Language Replication


Type Value LIC Name Order Active Translate Level

PROMO_UPGRADE_STA Latest End Latest End English- 7 Y Y All


RT_CD American

UMS_DISPLAY_MODE Active List Active List English- 3 Y Y All


American

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.

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:

Sequence Service Type Service Name Service Method

1 Business Service ISS Promotion Edit UI Service ShowPopup

5 In the Parameters list view, verify the following:

Name Value

Applet ISS Promotion Split Popup Applet

6 In the Properties list view, verify the following:

Name Value

CanInvoke:Any [Product Type]=LookupValue('PROD_CD','Promotion')

To verify the MergePromotion signal


1 Navigate to Administration - Order Management > Signals.

2 In the Signals list view, confirm that the signal MergePromotion 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:

Sequence Service Type Service Name Service Method

1 Business Service ISS Promotion Management Service GetMergePromotion

334 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

5 In the Properties list view, verify the following:

Name Value

CanInvoke:Any [Product Type]=LookupValue('PROD_CD','Promotion')

To verify the AddToPromotion signal


1 Navigate to Administration - Order Management > Signals.

2 In the Signals list view, confirm that the signal AddToPromotion 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:

Sequence Service Type Service Name Service Method

1 Business Service ISS Promotion Edit UI Service ShowPopup

5 In the Parameters list view, verify the following:

Name Value

Applet ISS Promotion Add To Promotion Popup Applet

To verify the AddToPromotionBilling signal


1 Navigate to Administration - Order Management > Signals.

2 In the Signals list view, confirm that the signal AddToPromotionBilling 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:

Sequence Service Type Service Name Service Method


1 Business Service ISS Promotion Edit UI Service ShowPopup

5 In the Parameters list view, verify the following:

Name Value

Applet ISS Promotion Add to Promotion Popup Applet (Billing)

To verify the GetPromoUpgradeEligibility signal


1 Navigate to Administration - Order Management > Signals.

2 In the Signals list view, confirm that the signal GetPromoUpgradeEligibility has been created.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 33 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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:

Sequenc Service Service Service


e Type Name Method Condition

1 Workflow PSP Driver RunProcess GetProfileAttr('SkipToEnd') = 'N' OR


Workflow GetProfileAttr('SkipToEnd') IS NULL
Process

5 In the Parameters list view, verify the following:

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

To verify the GetAgreementConditionalCharge signal


1 Navigate to Administration - Order Management > Signals.

2 In the Signals list view, confirm that the signal GetAgreementConditionalCharge 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:

Sequence Service Type Service Name Service Method

1 Business Service ISS Promotion GetAgreementConditionalCharge


Management Service

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
1 Navigate to Administration - Order Management > Variable Maps.
2 Verify that the variable map Promotion Upgrade Eligibility Variable Map - Context has been
created.

3 Click on the Work Space link.

336 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

4 In the Variable Definition view, verify the following:

NOTE: The Path, Mode and Source Type fields are shown in the Variable Sources view.

Name In/Out Type On Null Path Mode Source Type

Account In Boolean Ignore $Current/AccountHeader/Use Any Instance


Contracted Contracted Products Only Flag
Products Only
Flag

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 In Integer Ignore PARAM_PSP_ELIGIBILITY_DISPL_MO Any Server Parameter


Mode DE

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

5 In the Modes view, verify the following:

Mode Object Name

Any AccountHeader

To verify the Promotion Upgrade Eligibility Variable Map - Row Set variable map
1 Navigate to Administration - Order Management > Variable Maps.

2 Verify that the variable map Promotion Upgrade Eligibility Variable Map - Row Set 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.

Name In/Out Type On Null Path Mode Source Type

Account Id In ID Ignore $Current/AssetLineItem/ AssetLineItem Instance


Root Asset Service Account
Id

Class Id In ID Ignore $Current/Product/Class Id Any Instance

Effective From In Date Ignore $Current/Product/Effective Any Instance


From

Effective To In Date Ignore $Current/Product/Effective Any Instance


To

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 33 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Name In/Out Type On Null Path Mode Source Type

Eligibility Reason Out Text Ignore $Current/Product/Eligibility Any Instance


Reason

Eligibility Status Out Text Ignore $Current/Product/Eligibility Any Instance


Status

Inclusive Eligibility Flag In Boolean Ignore $Current/Product/Inclusive Any Instance


Eligibility Flag

Pre Pick In Boolean Ignore $Current/Product/Pre Pick Any Instance


CD

Product Id In ID Ignore $Current/Product/Id Any Instance

Product Line Id In ID Ignore $Current/Product/Product Any Instance


Line Id

5 In the Modes view, verify the following:

Mode Object Name

Any Product

AssetLineItem AssetLineItem

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.

338 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

2 In the Message Type List view, verify that the Message Type Promotion - Multiple Commitment
Broken Message - Debundle has been created.

Display
Name Mode Group Title Short Text Full Text

Promotion - Active Promotion Promotion - Commitment has Commitment has


Multiple Multiple been broken for the been broken for the
Commitment Commitment following following
Broken Broken promotions: promotions:
Message - Message [Promotion [Promotion
Debundle Message] and Message] and
promotion promotion
components: components:
[Promotion [Promotion
Component Component
Message] Please Message] Please
debundle each debundle each
promotion promotion
component component
individually to view individually to view
the specific terms. the specific terms.

3 In the Responses list view, verify the following:

Response Suppress
Sequence Name Type Log Repetition Business Service Method

1 Skip Respondent N N ISS Promotion MsgResponse


Interested Management
Service

2 Cancel Respondent N N ISS Promotion MsgResponse


Interested Management
Service

4 In the Payload list view, verify the following:

Payload Field

Promotion Message

Promotion Component Message

To verify the Promotion - Broken Commitment Error - Debundle message type


1 Navigate to Administration - Order Management > Message Types.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 33 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

2 In the Message Type list view, verify that the Message Type Promotion - Broken Commitment
Error - Debundle has been created.

Display
Name Mode Group Title Short Text Full Text

Promotion - Active Promotion Broken Commitment Commitment has


Broken Commitment broken for been broken for
Commitment promotion promotion
Error - Debundle component component
'[Prod Prom '[Prod Prom
Name]'. 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.

3 In the Responses list view, verify the following:

Response Suppress
Sequence Name Type Log Repetition Business Service Method

1 Accept Respondent N N ISS Promotion MsgResponse


Interested Management
Service

2 Skip Respondent N N ISS Promotion MsgResponse


Interested Management
Service

3 Cancel Respondent N N ISS Promotion MsgResponse


Interested Management
Service

340 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

4 In the Payload list view, verify the following:

Payload Field

Prod Prom Name

Commitment End Date

Penalty

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.

Display
Name Mode Group Title Short Text Full Text

Promotion - Passive Promotion Component A penalty of A penalty of


Component Commitment [Penalty] for [Penalty] for
Commitment Penalty removing [Name] removing [Name]
Penalty with Integration with Integration
Id = [Integration Id = [Integration
Id] is triggered. Id] is triggered.
Please click Please click
Cancel to avoid Cancel to avoid
the penalty. the penalty.

3 In the Payload list view, verify the following:

Payload Field

Integration Id

Name

Penalty

To verify the Promotion - Bottomup Recommendation For Assets message type


1 Navigate to Administration - Order Management -> Message Types.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 34 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

2 In the Message Type list view, verify that the Message Type Promotion - Bottomup
Recommendation For Assets has been created.

Display
Name Mode Group Title Short Text Full Text

Promotion - Active List Promotion Promotion Recommend Recommend


Bottomup Recommendation [Prod Prom promotion
Recommendation Name] '[Prod Prom
For Assets Name]':
[Promotion
Description].

3 In the Responses list view, verify the following:

Suppress
Sequence Name Response Type Log Repetition Field Business Service Method

1 Accept Respondent Y N ISS Promotion MsgResponse


Interested Management Service

2 Reject No Interest Y Y Account Id ISS Promotion MsgResponse


Management Service

4 In the Payload list view, verify the following:

Payload Field Response Field

Account Id Account Id

To verify the Promotion - No Promotion Recommendations message type


1 Navigate to Administration - Order Management -> Message Types.

2 In the Message Type list view, verify that the Message Type Promotion - No Promotion
Recommendations has been created.

Display
Name Mode Group Title Short Text Full Text

Promotion - No Active Promotion Recommendations There are no There are no


Promotion Promotion Promotion
Recommendations Recommendations for Recommendations for
this account. this account.

To verify the Promotion - Multiple Commitment Broken Message - Components


message type
1 Navigate to Administration - Order Management -> Message Types.

342 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

2 In the Message Type list view, verify that the Message Type Promotion - Multiple Commitment
Broken Message - Components has been created.

Display
Name Mode Group Title Short Text Full Text

Promotion - Active Promotion Promotion - Commitment has Commitment has


Multiple Multiple been broken for been broken for
Commitment Commitment the following the following
Broken Message Broken Message assets: assets:
- Components [Message]
[Message]

Please
disconnect each
asset individually
to view the
specific terms.

3 In the Payload list view, verify the following:

Payload Field

Message

To verify the Promotion - Broken Component Commitment Error message type


1 Navigate to Administration - Order Management -> Message Types.

2 In the Message Type list view, verify that the Message Type Promotion - Broken Component
Commitment Error has been created.

Display
Name Mode Group Title Short Text Full Text

Promotion - Active Promotion Broken Commitment 'A commitment


Broken Commitment broken for has been broken
Component promotion for promotion
Commitment component component '[Prod
Error '[Prod Prom Prom Name]'.
Name] Customer must
keep this product
until
[Commitment
End Date] or pay
a penalty of
[Penalty].

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 34 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 In the Responses list view, verify the following:

Suppress
Sequence Name Response Type Log Repetition Business Service Method

1 Accept Respondent N N ISS Promotion MsgResponse


Interested Management Service

2 Reject Respondent N N ISS Promotion MsgResponse


Interested Management Service

4 In the Payload list view, verify the following:

Payload Field

Prod Prom Name

Commitment End
Date

Penalty

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:

Sequence XML File


1 CreatePromotionAgreementCoveredAssets

2 CreatePromotionItemAgreement

Instructions for ACR 502


The following section contains information about how to install and configure ACR 502.

Installing ACR 502


1 In Siebel Tools, lock the following projects:

❏ EIM Asset

❏ EIM Order

❏ EIM Quote

❏ Table Asset

344 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ Table Order

❏ Table Quote

❏ Web Channel Order Management

❏ Row Set Transformation Toolkit

❏ Cfg RTC

❏ ISS Order Management

❏ Cfg JS

❏ SIS OM Base Architecture

❏ 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

❏ Symbolic String.sif

NOTE: If you have not locked the required projects, you may receive a warning error message.
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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 34 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

8 Start the Siebel Server.

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.

10 Select Workflow Process Object in OBLE.


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:

Workflow Name New/Modified Project

Check Eligibility & Compatibility - Modified ISS Order Management


Default

Product Eligibility & Compatibility - Modified Row Set Transformation Toolkit


Default

Product Compatibility - Default Modified Row Set Transformation Toolkit

Configurator Eligibility Compatibility Modified Cfg RTC


Workflow

Web Channel Product Eligibility & Modified Web Channel Order Management
Compatibility Driver Workflow

SIS OM Apply Completed Service Modified SIS OM Base Architecture


Order Line Item to Service Profile

SIS OM Move Process Modified SIS OM Base Architecture

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.

346 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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:

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

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.

Importing Seed Data for ACR 502


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

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

a Navigate to Start > Setting > 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:

❏ For Oracle, enter the TNS service name that you created to connect Siebel Tools to the
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 either
REPPATCH\VACR502 if you are an SIA customer or to REPPATCH\HACR502 if you are an SEA
customer.

NOTE: Before you perform the following step, make sure that the dataimp.exe file exists in the
<Tools Install Directory>/bin directory.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 34 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 Run the following command:

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


Directory>\REPATCH\VACR502\SeedData\ENU\VACR502_Seed.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.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 the ODBC name created in Step 1.

<Database Platform> - Replace with the 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.

5 Depending upon the language that you are installing, complete either Step 6 or Step 7.

6 For ENU only, do the following:

a Run the following command after importing the VACR502_Seed.dat file.

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


Directory>\REPATCH\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

<Tools Install Directory> - Replace with your Tools install directory.

<ODBC Source Name> - Replace with the ODBC name created in Step 1.

<Database Platform> - Replace with the database platform (ORACLE, DB2UDB or MSSQL).

7 For languages other than ENU, do the following:

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

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


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

<Tools Install Directory> - Replace with your Tools install directory.

<ODBC Source Name> - Replace with the ODBC name created in Step 1.

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.

The Locale Management dialog box appears.

2 In the Options tab, under Languages, select a source language and a target language.

348 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 Click the Import tab, and enter the following directory path: ACR502\LMU\XXX\lmu\lmu_crm.slf,
where XXX is the language code.

4 Click the Import button to import the data.

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
1 Navigate to Administration - Order Management > Signals.

2 In the Signals list view, confirm that the PrepareEnableEngine signal was created.

3 In the Versions list view, click on the latest version of the signal to drill down to the Actions list
view.

4 In the Actions list view, verify the following:

Sequence Service Type Service Name Service Method

1 Business Service Remote Complex Object Instance Service PrepareEnableEngine

ReEnableiLogForQuickEdit
1 Navigate to Administration - Order Management > Signals.

2 In the Signals list view, confirm that the ReEnableiLogForQuickEdit signal was created.
3 In the Versions list view, click on the latest version of the signal to drill down to the Actions list
view.

4 In the Actions list view, verify the following:

Sequence Service Type Service Name Service Method

1 Business Service Remote Complex Object Instance Service ReEnableiLogForQuickEdit

UpdateUIForQuickEdit
1 Navigate to Administration - Order Management > Signals.

2 In the Signals list view, confirm that the UpdateUIForQuick Edit signal was created.
3 In the Versions list view, click on the latest version of the signal to drill down to the Actions list
view.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 34 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

4 In the Actions list view, verify the following:

Sequence Service Type Service Name Service Method

1 Business Service Remote Complex Object Instance Service UpdateUIForQuickEdit

PrepareDisableEngine
1 Navigate to Administration - Order Management > Signals.

2 In the Signals list view, confirm that the PrepareDisableEngine signal was created.

3 In the Versions list view, click on the latest version of the signal to drill down to the Actions list
view.

4 In the Actions list view, verify the following:

Sequence Service Type Service Name Service Method

1 Business Service Remote Complex Object Instance Service PrepareDisableEngine

Product Eligibility Variable Map - Context


1 Navigate to Administration - Order Management > Variable Maps.

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:

NOTE: The Path, Mode and Source Type fields are shown in the Variable Sources view.

Name In/Out Type On Null Default Value


Pre Pick Compatibility In Boolean Ignore

5 In the Modes view, create a record as shown in the following table:

Mode Path Source Type

Any PARAM_OM_PRODCFG_PREPICKCOMP Server Parameter

6 In the Variable Definition view, verify the following records:

NOTE: The Path, Mode and Source Type fields are shown in the Variable Sources view.

Name In/Out Type On Null Default Value

Pre Pick Mode In Text Ignore

350 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

7 In the Modes view, create a record as shown in the following table:

Mode Path Source Type

Any $Current/Header/Pre Pick Mode Instance

8 Release the variable map and clear the cache.

Cfg Eligibility Variable Map - Context


1 Navigate to Administration - Order Management > Variable Maps.

2 Query to find the variable map "Product Eligibility Variable Map - Context".

3 Click on the latest version of the variable map.

4 In the Variable Definition view, verify the following records:

NOTE: The Path, Mode and Source Type fields are shown in the Variable Sources view.

Name In/Out Type On Null Default Value

Pre Pick Compatibility In Boolean Ignore

5 In the Modes view, create a record as shown in the following table:

Mode Path Source Type

Any PARAM_OM_PRODCFG_PREPICKCOMP Server Parameter

6 In the Variable Definition view, verify the following records:

NOTE: The Path, Mode and Source Type fields are shown in the Variable Sources view.

Name In/Out Type On Null Default Value


Pre Pick Mode In Text Ignore

7 In the Modes view, create a record as shown in the following table:

Mode Path Source Type

Any $Current/Header/Pre Pick Mode Instance

8 Release the variable map and clear the cache.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 35 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

List of Values
1 In the Siebel application, navigate to Administration - Data > LOV Explorer and verify that the
following LOV types have been created:

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:

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.

Display Language Replication


Type Value LIC Name Order Active Translate Level

CFG_QUICKEDIT_BTN_TYPE Turn On Cfg ON English - 1 Y Y All


Quick-Edit American

CFG_QUICKEDIT_BTN_TYPE Turn Off Cfg OFF English - 1 Y Y All


Quick-Edit American

Server Parameter
1 Navigate to the Administration - Server Configuration screen > Servers and Parameters view.

2 Verify that the following server parameter has been created:

Name Value Value on Restart

EnablePrePickCompatibility False False

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

352 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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:

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 35 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

354 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 Within the file, search for the <swe: control> tag and edit it to ForceRefresh="Y".

<!-- Template Start: eCfgControlComboAddPriceJS.swt -->

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


CfgHtmlType="CfgLabel"/>';

var sComboAddQtyLabel = '<swe:control id="Quantity" CfgUIControl="lblQuantity"


CfgHtmlType="CfgLabel"/>';

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 35 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

<!-- Template End: eCfgControlComboAddPriceJS.swt -->

4 Within Internet Explorer, navigate to Tools > Internet Options > General tab, delete all of the
temporary files and log into the Siebel application.

Instructions for ACR 508


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 159, 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 356.)

❏ \SeedData (For more information, see “Importing Seed Data for ACR 508” on page 357.)
❏ \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

■ EIM_ORDER_ITEM

356 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ 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_EIMTables.sif files into the repository
1 Lock the following projects before import:

■ Table FieldService

■ Table NetworkOrderManagement

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

Importing Seed Data for ACR 508


Use the following procedure to import seed data.

To import seed data for ACR 508


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

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 35 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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
Install Directory>/bin directory.

3 Run the following command:

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


Directory>\REPPATCH\ACR508\SeedData\ACR508_Seed.dat /l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <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).

4 Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the
import completed successfully.

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.

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


Directory>\REPPATCH\ACR508\SeedData\ACR508_Seed_Locale_ENU.dat /l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools
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

<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 this with your database platform (ORACLE, DB2UDB or
MSSQL).

358 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


Directory>\REPPATCH\ACR508\SeedData\ACR508_Seed_Locale_XXX.dat /l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q -1 /w n
/e y /t n /x R /n 100 /h log

<Tools Install Directory> - Replace 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.

NOTE: Step 6 applies to both customers who are using ENU and customers who are using
languages other than ENU.

6 Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.

Siebel Tools Changes for ACR 508


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

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.
4 In Siebel Tools, lock all the following projects:

❏ Web Service Integration

❏ Order Entry

❏ Web Channel Order Management

❏ Symbolic Strings

❏ Product Selection UI

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 35 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

5 Import the rest of the SIF files from the SIFFiles folder into Siebel Tools using the Tools > Import
from Archive function.

If you have not locked the required projects, you may receive a warning error message.

Make sure to choose Merge Option in Siebel Tools Import Wizard.

Import the following SIF files:

■ 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.
b Select Source Language = English American

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.

10 Start the Siebel Server.


11 Import the workflows listed in the following table into the Siebel application.

Process Name New/Modified Project

SWISendOrder Modified Web Service Integration

360 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Process Name New/Modified Project

SWIReviseOrderValidation New Web Service Integration

SWI Cancel Sales Order New Web Service Integration

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

NOTE: You may receive the "This is an invalid Workflow…" error message while deploying the
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.
16 Restart the Siebel Server.
17 Launch the Siebel Communications application.

Instructions for ACR 539


The following section contains information about how to configure and install ACR 539.

Preinstallation Tasks
■ Before you begin your installation, change a parameter in tools.cfg file within Siebel Tools
(Original: SymStrPrefix = X_) to SymStrPrefix = SBL_

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 36 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Repository Configurations
1 Get $ReleaseRoot\release\redist\repatch\ACR539.zip and unzip to any location accessible by
Siebel Tools.

2 In Siebel Tools, lock the following projects:

■ 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 Tools details with the username "SADMIN".

4 Create a log folder in Unziplocation\ACR539\REPOSITORY.

5 Run the import.bat file to import.

6 In Siebel Tools, compile all of the locked and updated projects.

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 (Please refer to Schema Changes Section on how to apply the
changes)

8 Import the Workflow Processes into Siebel Repository. See "Importing Workflow Definitions" for
more information.

362 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Schema Changes
Use the instructions below to apply the schema changes.

Applying Schema Changes to the Database


As part of the ACR539 release, schema changes have been done on the database. The
REPPATCH\ACR539\REPOSITORY\Tables\Tables.sif has all the changes for the following:

Changes to existing tables:

■ 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. The "merge" option should be used while importing this file.

3 Use Siebel Tools to query for the list of tables that were imported into the repository.

4 Use the Apply/DDL button to apply the changes to the physical database.

Applying Links Changes


Import the "Clinical Protocol Site_Clinical Protocol.sif" to apply the changes.

Applying PickList Changes


Import the "PickList Clinical Protocol Site Primary Addresses.sif" to apply the changes.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 36 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Applying Business Service Changes


Import the "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
Update the existing Business Component "Clinical Protocol" Business Component by adding new
fields as shown below:

Project LS Clinical Protocol

Table S_CL_PTCL_LS

Single
Value
Fields

New/ Name Column Type Calculated Text Pre


Modified? Value Length Default

New Synchronize SYNC_SITES_FLG DTYPE_BOO 1 N


Active Sites L
Flag

New CDMS Study CDMS_STUDY_CODE DTYPE_TEXT 50


ID

New Is CDMS null IIF(([CDMS


Study ID] IS
NULL), "Y",
"N")

Field User Properties

Parent Field User Property Name Value

CDMS Study ID Text Length Override 15

364 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Business Component User Properties

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"

2 Clinical Protocol Site


Update the existing Business Component "Clinical Protocol Site" Business Component by adding new
fields as shown below:

Project LS Medical Product Issue

Project LS Clinical Protocol Site

Table S_ PTCL_SITE_LS

JOINS

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

Join Specification

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 36 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

BUSINESS COMPONENT USER PROPERTY

Name Value

Field Read Only Field: Activate Synchronization Flag Require Active Flag Check

New/
Modified Calculated Pre
? Name Join Column Type Value PickList Default

New Field Activate ACTIVATE_ DTYPE_BOOL N


Synchronizat SYNC_FLG
ion Flag

New Field Address Line Primary Address ADDR DTYPE_TEXT PickList


1 Clinical
Protocol
Site
Primary
Addresses

New Field Address S_CL_ST_ADDR_LS ADDR_ORG DTYPE_ID


RowId _ID

New Field Address Type S_CL_ST_ADDR_LS SITE_ADDR DTYPE_TEXT


_TYPE

New Field CDMS Site DTYPE_TEXT [Account


Id]+":"+[Ad
dress RowId]

New Field CDMS Study DTYPE_TEXT [Account


Site Id]+":"+[Ad
dress RowId]

New Field Description S_CL_ST_ADDR_LS DESC_TEXT DTYPE_TEXT

New Field Primary PR_ADDR_I DTYPE_TEXT


Address Id D

New Field Prev CDMS AIA_INTEG DTYPE_TEXT


Site _ID

New Field Primary S_CL_ST_ADDR_LS ADDR_ORG DTYPE_ID


Address _ID

New Field Protocol S_CL_PTCL_LS SYNC_SITE DTYPE_BOOL


Active Sync S_FLG
Flag

New Field Require IIF(([Protoco


Active Flag l Active Sync
Check Flag] = 'Y'
AND [Street
Address] IS
NOT NULL ),
"N", "Y")

New Field Site Last LAST_UPD DTYPE_UTCDATETIME


Updated

366 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ For the Address Line 1 field, add the following record in the Pickmap:

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

3 Visit Template Activities


Update the existing Visit Template Activities Business Component by adding new fields as shown
below:

Project LS Clinical Subject

Table S_EVT_ACT

Single Value Fields

New/ Text
Modify Name Join Column Type Length

New Clinical Item S_EVT_ACT_LSX CLINICAL_ITEM_ DTYPE_TEXT 255


Field VAL

New Parent Activity TEMPLATE_ID DTYPE_ID 15


Field Template RowId

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 36 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

4 Action (No Owner Lock)


Update the existing Action (No Owner Lock) Business Component by adding new fields as shown
below:

Project LS Clinical
Subject

Table S_EVT_ACT

New/ Text
Modified Name Join Column Type Length

New Field Activity S_EVT_ACT_LSX CLINICAL_ITEM_VAL DTYPE_TEXT 255


Clinical Item

New Field Visit Clinical Parent Template CLINICAL_ITEM_VAL DTYPE_TEXT 255


Item

5 Subject Visit Templates


Update the existing Subject Visit Templates Business Component by adding new fields as shown
below:

Project LS Clinical Subject

Table S_TMPL_PLANITEM

Single Value Fields

New/Modify Name Column Type Text Length


New Field Clinical Item CLINICAL_ITEM_VAL DTYPE_TEXT 255

368 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

6 Visit Plan
Update the existing Visit Plan Business Component by adding new fields as shown below:

Project LS Clinical Subject

Table S_EVT_ACT

New/ Text
Modify Name Join Column Type Length

New Field Clinical Item Parent CLINICAL_ITEM_VAL DTYPE_TEXT 255


Template

Modified Priority EVT_PRIORITY_CD DTYPE_TEXT 30


Field

7 Visit Plan Action


Update the existing Visit Plan Action Business Component by adding new fields as shown below:

Project LS Clinical Subject

Table S_EVT_ACT

Table Alias Outer Join

S_EVT_ACT_LSX Clinical Item Activity TRUE

Parent Table Destinatio


Name Name Source Field n Column

S_EVT_ACT_LSX ClinicalItemActivity Parent Activity Template ROW_ID


RowId

New/ Text
Modified Name Join Column Type Length

New Field Clinical Item Clinical Item CLINICAL_ITEM_VAL DTYPE_TEXT 255


Activity

New Field Parent Activity TEMPLATE_ID DTYPE_ID 15


Template
RowId

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 36 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

8 Clinical Account Investigator Role


Update the existing Clinical Account Investigator Role Business Component by adding new fields as
shown below:

Project LS Clinical Investigators

Table S_PTL_ST_CON_LS

New/Modify Name Link Specification

Modified Field Site Id TRUE

9 Clinical Subject
Update the existing Clinical Subject Business Component by adding new fields as shown below:

Project LS Clinical Subject

Table S_CL_SUBJ_LS

New/Modified Name PickList

Modified Field Protocol Site Id LS Clinical Protocol Site Picklist

For the ProtocolSiteId field, add the following record in the pickmap:

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

370 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Applying Business Object Changes


Import the "Clinical Protocol Site New.sif" file 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. Also need to add the new controls to the Applet Web
Template.

Clinical Protocol Admin Form Applet (Modify)

BusComp Clinical Protocol

Project LS Clinical Protocol

HTML
New/ Icon
Modified Name String Reference Caption Field Map HTML Type

New CDMS Study SBL_CDMS_STUDY_ID CDMS Study CDMS Study Text


ID ID ID

New Synchronize SBL_SYNC_STUDY_SITES Synchronize Synchronize Checkbox


Active Sites Active Study Active Sites
Sites Flag

New Label SBL_INTEGRATION- Integration FormSection


Integration 1004224521-0XI

■ In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout.

■ Clinical Protocol Form Applet

Clinical Protocol Form Applet (Modify)

BusComp Clinical Protocol

Project LS Clinical Protocol

HTML
New/ String Icon
Modified Name Reference Caption Field Map HTML Type

New CDMS SBL_CDMS CDMS CDMS Text


Study ID _STUDY_ID Study ID Study ID

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 37 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

HTML
New/ String Icon
Modified Name Reference Caption Field Map HTML Type

New Synchronize SBL_SYNC_ Synchronize Synchronize Checkbox


Active Sites STUDY_SIT Active Active Sites
ES Study Sites Flag

New Label SBL_INTEG Integration FormSection


Integration RATION-
100422452
1-0XI

In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout.

■ Clinical Protocol Site Entry Applet

Clinical Protocol Site Entry Applet (Modify)

BusComp Clinical Protocol Site

Project LS Clinical Protocol Site

New/ String
Modified Name Reference Caption Field PickList HTML Type

New Primary Site SBL_PRIMA Primary Site Address PickList Text


Address Y_SITE_AD Address Line 1 Clinical
DRESS Protocol
Site Primary
Addresses

New Activate for SBL_ACTIV Activate for Activate for Checkbox


Synchroniza ATE_FOR_S Synchroniza Synchroniza
tion YNC tion tion

New Label SBL_INTEG Integration FormSectio


Integration RATION- n
100422452
1-0XI

In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout.

372 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ Clinical Visit Template Activities

Clinical Visit Template Activities (Modify)

BusComp Visit Template Activities

Project LS Clinical Subject

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

Clinical Subjects Visit Templates List Applet (Modify)

BusComp Subject Visit Templates

Project LS Clinical Subject

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)

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 37 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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 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 of the SIF file import. This list is provided for
reference only.

New/ Current
Existing Name StringValue Definition

New SBL_ACTIVATE_FOR_SYNC Activate for An indicator that determines


Synchronization 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 An indicator that determines


Study Sites 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

Importing Workflow Definitions


Use the following procedure to import workflow definitions.

To import workflow definitions


1 Log in to Siebel Tools.

NOTE: Siebel Tools has to connect to the same database as the Siebel application server.

2 From Object Explorer, navigate to Workflow Process.

374 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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 .

New/
Modified Xml File to Import Workflow Name Project

New LS ClinicalProtocolSite LS ClinicalProtocolSite LS Clinical Activity


Outbound - NewSite.xml Outbound - NewSite

New LS ClinicalProtocolSite LS ClinicalProtocolSite LS Clinical Activity


Outbound-UpdatedSite.xml Outbound-UpdatedSite

New SWI LS Clinical Subject SWI LS Clinical Subject LS Clinical Subject


Inbound.xml Inbound

New SWI LS Clinical Subject SWI LS Clinical Subject LS Clinical Subject


Inbound - Subject.xml Inbound - Subject

New SWI LS Clinical Subject SWI LS Clinical Subject LS Clinical Subject


Inbound - Activity.xml Inbound - Activity

New SWI Protocol Number SWI Protocol Number LS Clinical Subject


Lookup.xml Lookup

Modified LS Clinical - LS Clinical - LS Clinical


DeleteNonAppVisits DeleteNonAppVisits Enhancement
Process.xml Process

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 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 you are deploying the workflow, ignore the error message.

To update "LS Clinical - DeleteNonAppVisits Process" workflow


NOTE: The procedures in this section are an alternative to importing xml file. Use the following
procedure if you want to perform manual configuration because this is an existing Workflow.

1 Log into Siebel Tools.

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 37 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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:

Input Argument Type Value

Refresh All Literal Y

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


1 Log into the Siebel application.
2 Navigate to the Administration - Web Services > Inbound Web Services view.

3 Import the ClinicalSubject.xml file. The file is located in


Unziplocation\ACR539\REPOSITORY\WebServices folder that you extracted from the zip file.

XML File to Import Web Service Name Direction

ClinicalSubject.XML Clinical Subject Inbound

4 Query for the "Clinical Subject" Web Service.

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>&Password=<p
assword>

6 Change the webserver to the webserver host name.

376 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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

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.

Seed Data
Use the following procedure to import the seed data for ACR 539.

To import 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).

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.

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 37 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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
Install Directory>/bin directory.

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.

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

3 Run the following command:

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install


irectory>\REPATCH\ACR539\SeedData\ENU\ACR539_Seed.dat /l <Tools Install
Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools
Install Directory>\REPATCH\ACR539\SeedData\<Database Platform>\ACR539_Seed.inp /q -
1 /w y /e n /t n /x R /n 100 /h log

<Tools Install Directory> - Replace with your Siebel Tools install directory

<ODBC Source Name> - Replace with the ODBC name created in the previous procedure.

<Database Platform> - Replace with your database platform information (ORACLE, DB2UDB or
MSSQL)

4 Review the log file in <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the
import completed successfully.

5 Depending upon the language that you are installing, follow Step 6 or Step 7.

6 For ENU (English Language) customers:


a Run the following command after importing the ACR539_Seed.dat file.

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools


Install Directory>\REPATCH\ACR539\SeedData\ENU\ACR539_Seed_Locale_ENU.dat /l
<Tools Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table
Owner> /i <Tools Install Directory>\REPATCH\ACR539\SeedData\<Database Platform>\
ACR539_Seed_Locale_ENU.inp /q -1 /w y /e n /t n /x R /n 100 /h log

<Tools Install Directory> - Replace with your Siebel Tools install directory

<ODBC Source Name> - Replace with the ODBC name created in Step 1 of the previous
procedure.

<Database Platform> - Replace with your database platform (ORACLE, DB2UDB or MSSQL)

b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.

7 If you are installing languages other than ENU, perform the following steps:

378 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

<Tools Install Directory>\bin\dataimp /u <USERNAME> /p <PASSWORD> /f <Tools


Install Directory>\REPATCH\ACR539\SeedData\XXX\ACR539_Seed_Locale_XXX.dat /l
<Tools Install Directory>\temp\dataimp_seed.log /c <ODBC Source Name> /d <Table
Owner> /q -1 /w n /e y /t n /x R /n 100 /h log

<Tools Install Directory> - Replace with your Siebel Tools install directory.

<ODBC Source Name> - Replace with the ODBC name created in Step 1 of the previous
procedure.

b Review the <Tools Install Directory>\temp\dataimp_seed.log file to make sure that the import
completed successfully.

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 37 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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 requiring 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. Enter the Table Owner In the Value field.

7 In the Job Parameter list, click New.

8 In the Job Parameter list, click the name field select button to query for and select the Privilege
User record, and click OK. Enter the Table Owner in the Value field.

9 In the Job Detail form applet, click Menu and choose Start Job.

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

380 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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:

Srvrmgr / e <Enterprise name> /s <siebel server name> /g <gateway name

server> /u <sadmin> /p <password>

2 Type the following:

start task for comp workmon


withtableownpass='<password>',Actionagent='false',Groupname='LS Clinical Rollup'

3 In Application, Navigate to the Administration - Server Management screen > Tasks >
Parameters view.

4 In Server Task List Applet, Query in Component Field for 'Workflow Monitor Agent'.

5 In Server Task-Parameter List Applet, query in Parameter field for 'Action interval' , it will have
default value as 3600, i.e, 3600 seconds, 1 hr. Set it to lower value, even 5 is fine.

Enabling Component Groups


Make sure that "EAI" and "Workflow" Component Group is enabled, if not enable the same and
bounce the Siebel Server.

Configuring the Siebel Application to Write to the JMS Queue on the


SOA Server
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 say D:\JMS
folder.

3 Copy Siebel.jar and SiebelJI_enu to D:\JMS folder, these jar files can be found in Siebel installed
directory.

4 Copy jndi.jar file to D:\JMS\j2ee\home\lib folder. This file can be found 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. Note that when you extract the file you should check include folder information so that
JCAProperties.class is created under D:\JMS\com\evermind\util\ not under D:\JMS.

6 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>:<Posrt


No>:oc4j_soa

■ java.naming.security.principal=anonymous

For example:

■ java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 38 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ java.naming.provider.url=opmn:ormi://adc60120fems.us.oracle.com:6009:oc4j_soa

■ java.naming.security.principal=sadmin

7 Create a Named Subsystem in the Siebel application through the server management. Connect
to the server manager from command prompt from the bin directory of the Siebel installed folder
with the command.

a Srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u <userid> /p


<password>

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\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:\JMS\j2ee\home\oc4jclient.
jar;D:\JMS\j2ee\home\lib\bcel.jar;D:\JMS\j2ee\home\lib\jms.jar;D:\JMS\j2ee\home\lib\ja
vax77.jar;D:\JMS\jdbc\lib\ojdbc14dms.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

8 Login 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 Edit the value of VMOPTIONS to -Djms.log=D:\JMS\log\jms.log.

9 Restart the Siebel Server.

10 On the SOA server, log into Entreprise Manager and create a user called sadmin that is part of
the users role. For information about how to create the users, see the Enterprise Manager
documentation.

11 Login to the Siebel application and navigate to Site Map > Administration - Business Service >
Simulator.

12 Click New and provide the following parameters:


■ Service Name = EAI JMS Transport

■ Method Name = Check CLASSPATH

13 Change the Method Name to CheckJNDIContext with the following input arguments in the
home\lib folder.

a SendUsername = sadmin

b SendPassword = <put password for sadmin user created in Enterprise Manager>

c ConnectionFactory = java:comp/resource/UpdateClinicalStudySEBLRP/
QueueConnectionFactories/QCF

d SendQueue = java:comp/resource/UpdateClinicalStudySEBLRP/Queues/AIA_CLINICALSTUDYQ

14 Change the Method Name to Send.


15 Log into Siebel Tools and click on Workflow Processes.

382 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

17 Perform Step a through Step h for the LS ClinicalProtocolSite Outbound - UpdatedSite workflow
process.

18 Log into the Siebel application and navigate to Administration - Business Processes.
19 Click on Workflow Deployment.
20 Query for the LS ClinicalProtocolSite Outbound - NewSite workflow and click the Activate button.
21 Query for the LS ClinicalProtocolSite Outbound - UpdatedSite workflow and click the Activate
button.

22 Log into Siebel Tools and click on Workflow Processes.


23 Query for the LS ClinicalProtocolSite Outbound - NewSite workflow process.
a Click on 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.

24 Perform Step a through Step h for the LS ClinicalProtocolSite Outbound - UpdatedSite workflow
process.

25 Log into the Siebel application and navigate to Administration - Business Processes.
26 Click on Workflow Deployment.
27 Query for workflow LS ClinicalProtocolSite Outbound - NewSite and click the Activate button.
28 Query for workflow LS ClinicalProtocolSite Outbound - UpdatedSite and click the Activate button.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 38 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Instructions for ACR 543


Use the instructions in this topic to implement ACR 543. It includes the following topics:

■ About ACR 543 on page 384

■ Requirements for ACR 543 on page 384

■ Applying ACR 543 on page 385

■ Importing Archive Files for ACR 543 on page 385

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.

384 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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
SIEBEL_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: SIEBEL_TOOLS_ROOT\bin\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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 38 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

6 Lock the following projects:

■ EAI Business Services

■ Server Components - Infrastructure

■ Server Components - EAI

■ SAI EAI Outbound Services

■ SAI Base Integration Objects

NOTE: If projects and objects are not locked when you import SIF files, a message appears
indicating which object or project you must lock. In such a case, lock the project or object, and
then import the SIF file again.

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 SIEBEL_TOOLS_ROOT\tools\bin directory to import the
preconfigured base integration objects:

NOTE: This process can take some time; wait until the process completes.

siebdev.exe /c tools.cfg /d sample /u sadmin /p sadmin /batchimport "repository


name" merge directory_name import.log

where:

■ /c is the configuration file name and location

386 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ /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”)

■ directory_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 SIEBEL_TOOLS_ROOT\tools\bin 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 SIEBSRVR_ROOT\objects\enu.

12 Restart the Siebel Server.


You are now ready to deploy SAI for Oracle Fusion Middleware. For more information, see Siebel
Application Integration for Oracle Fusion Middleware Guide.

Instructions for ACR 562


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.

Preinstallation Tasks for ACR 562


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.


b Change the value of OverWriteConfig=Yes in the following files:

❏ Siebel_Enterprise_Server/enu/siebel.ini

❏ Siebel_Enterprise_Server/siebel.ini

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 38 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

388 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 38 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

390 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

File105 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_33_66.swt

File106 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_50_50.swt

File107 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_66_33.swt

File108 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCView_Search.swt

File109 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewAdmin1.swt

File110 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewbar_Tabs.swt

File111 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewbarAll_Tabs.swt

File112 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewBasic.swt

File113 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewCatalog.swt

File114 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail.swt

File115 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail2.swt

File116 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail2_ParentPntr.swt

File117 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail3.swt

File118 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail3MultiChild.swt

File119 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail_GrndchldIndnt.swt

File120 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetail_ParentPntr.swt

File121 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewDetailMultiChild.swt

File122 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewTree.swt

File123 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCViewTree2.swt

File124 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCAppletForm1Col.swt

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 39 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

392 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 39 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

File198 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_50_50.swt

File199 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_66_33.swt

File200 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_75_25.swt

File201 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCView_Basic.swt

File202 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCViewAdmin1.swt

File203 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCViewbar_Tabs.swt

File204 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCViewDetail.swt

File205 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCViewDetail2.swt

File206 = $(SiebelRoot)\siebsrvr\WEBTEMPL\dCCViewDetailMultiChild.swt

File207 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAttributeComboBox.swt

File208 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgAttributeList.swt

File209 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgBasketBox.swt

File210 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgClassNode.swt

File211 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCompAttributeEdit.swt

File212 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNav.swt

File213 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNav_UiPicker.swt

File214 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavAttributes.swt

File215 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavClasses.swt

File216 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavConnectedProducts.swt

File217 = $(SiebelRoot)\siebsrvr\WEBTEMPL\eCfgCxProdNavLinks.swt

394 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 39 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

396 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 39 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

398 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 39 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

400 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 40 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

402 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 40 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

404 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 40 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

406 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 40 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

408 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 40 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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:

❏ Siebel_Enterprise_Server/enu/siebel.ini

❏ Siebel_Enterprise_Server/siebel.ini

5 Append the following accessibility files information in the Siebel_Enterprise_Server/siebel.ini


file, under [DeleteFiles.Windows]:

File2 = $(SiebelRoot)\siebsrvr\WEBTEMPL\FINSFrameViewbar.swt

File3 = $(SiebelRoot)\siebsrvr\WEBTEMPL\FINSPageContainer.swt

File4 = $(SiebelRoot)\siebsrvr\WEBTEMPL\FINSDBLogin.swt

File5 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCAppletDashboard.swt

File6 = $(SiebelRoot)\siebsrvr\WEBTEMPL\CCFrameMsgbar.swt

File7 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespFormInBoundNew.swt

File8 = $(SiebelRoot)\siebsrvr\WEBTEMPL\EmailRespFormOutBoundNew.swt

Installing ACR 562


The following sections contain procedures for making the configuration changes needed in order to
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

410 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ DisableSITabIndex = TRUE

❏ EnableSIFocusTracking = TRUE

Configuration Changes for ACR 422


The following sections contain procedures for making the configuration changes needed in order to
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
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:

New/ Application SIA SIF File HOR SIF File


Changed Name User Property Value Name Name

Changed Siebel Universal AccessibilityXMLF Accessibility_Callce Accessibility_Callce Accessibility_Callce


Agent ileName nter.xml nter_SIA.sif nter_HOR.sif

Changed Siebel AccessibilityXMLF Accessibility_eMark Accessibility_eMark Accessibility_eMark


eMarketing ileName eting.xml eting_SIA.sif eting_HOR.sif

Changed Siebel eSales AccessibilityXMLF Accessibility_eSales Accessibility_eSale Accessibility_eSales


ileName .xml s_SIA.sif _HOR.sif

Changed Siebel eService AccessibilityXMLF Accessibility_eServi Accessibility_eServ Accessibility_eServi


ileName ce.xml ice_SIA.sif ce_HOR.sif

Changed Siebel Public AccessibilityXMLF Accessibility_Public Accessibility_Public Accessibility_Public


Sector ileName Sector.xml Sector_SIA.sif Sector_HOR.sif

Changed Siebel Sales AccessibilityXMLF Accessibility_Sales. Accessibility_Sales Accessibility_Sales_


ileName xml _SIA.sif HOR.sif

Changed Siebel Service AccessibilityXMLF Accessibility_Servic Accessibility_Servic Accessibility_Servic


ileName e.xml e_SIA.sif e_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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 41 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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)
1 Navigate to Object Explorer in Siebel Tools.

2 Navigate to View > Options, and click the Object Explorer tab.

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:

New/ HOR SIF File


Changed Project Name Value SIA SIF File Name Name

Changed Symbolic SBL_CALCULATOR_IC Calculator SymbolicStrings_SI SymbolicStrings_H


Strings ON_ALT_TXT A.sif OR.sif

Changed Symbolic SBL_CALENDAR_ICON Calendar SymbolicStrings_SI SymbolicStrings_H


Strings _ALT_TXT A.sif OR.sif

Changed Symbolic SBL_EDIT_ICON_ALT_ Pick Applet SymbolicStrings_SI SymbolicStrings_H


Strings TXT A.sif OR.sif

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.

To enable screen readers to read out the MVG and Pick Applet for Calendar,
Calculator, and MVG (Bitmaps)
1 Navigate to Object Explorer in Siebel Tools.

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.

412 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

5 Change the 'Alt Text' value to 'Calendar' and 'Calculator' respectively, as shown in the following
table:

New / Bitmap Alt Text SIA SIF File HOR SIF File
Changed Category Bitmap Value Description Name Name

Changed HTML CALENDAR_ ICON Calendar Change the HTMLControlIcon HTMLControlIcon


Control Alt text from s_SIA.sif s_HOR.sif
Icons "Input" to
Calendar.

Changed HTML CALCULATOR_ICON Calculator Change the HTMLControlIcon HTMLControlIcon


Control Alt text from s_SIA.sif s_HOR.sif
Icons "Input" to
Calculator.

Changed HTML ICON_SELECT Pick Change the HTMLControlIcon HTMLControlIcon


Control Applet Alt text from s_SIA.sif s_HOR.sif
Icons "Select" to
Pick Applet.

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)


1 Navigate to Object Explorer in Siebel Tools.
2 Navigate to View > Options, and click the Object Explorer tab.

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:

New/ Current
Changed Project Name String Value SIA SIF File Name HOR SIF File Name

New Symbolic SBL_CTRL_+_ALT_+_] Ctrl + Alt + ] SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif


Strings

New Symbolic SBL_CTRL_+_ALT_+_[ Ctrl + Alt + [ SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif


Strings

New Symbolic SBL_CTRL+SHIFT+B Ctrl+Shift+B symstr_columnsdisplay symstr_columnsdisplaye


Strings ed_SIA.sif d_HOR.sif

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 41 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

New/ Current
Changed Project Name String Value SIA SIF File Name HOR SIF File Name

New Symbolic SBL_CTRL+, Ctrl+, SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif


Strings

New Symbolic SBL_CTRL+. Ctrl+. SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif


Strings

New Symbolic SBL_ALT_G ALT+G SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif


Strings

New Symbolic SBL_ALT_U ALT+U SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif


Strings

New Symbolic SBL_ALT_W ALT+W SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif


Strings

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.

Key
Command Action Accelerator Sequence Description SIA SIF File Name

NextApplet Next Ctrl + Alt + ] Ctrl+Alt+221 Shifts focus CmdNextApplet_SIA.sif


Applet to the first
anchor of
the next
applet

PrevApplet Previous Ctrl + Alt + [ Ctrl+Alt+219 Shifts focus CmdPreviousApplet_SIA.


Applet to the first sif
anchor of
the previous
applet

Refine Query N/A Alt+G Alt+G N/A CmdRefineQuery_SIA.sif


(SWE)

First Page N/A Alt+U Alt+U N/A CmdFirstPageSWE_SIA.si


(SWE) f

Last Page N/A Alt+W Alt+W N/A CmdLastPageSWE_SIA.si


(SWE) f

Columns N/A Ctrl+Shift+B Ctrl+Shift+B N/A CmdColumnsDisplayed_S


Displayed IA.sif
(SWE)

NextApplet Next Ctrl + Alt + ] Ctrl+Alt+221 Shifts focus CmdNextApplet_SIA.sif


Applet to the first
anchor of
the next
applet

414 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

Creating Keyboard Shortcuts for Commands


Use the following procedures to provide keyboard shortcuts for commands.

To provide a keyboard shortcut for the NextApplet command


1 Navigate to Object Explorer in Siebel Tools.

2 Navigate to View > Options, and click the Object Explorer tab.

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.

3 Click the '+' sign in Object Explorer and choose 'Accelerator'.

4 In the Display Name - String Reference' field, enter the newly created Symbolic String or in the
Display Name field, enter 'Ctrl + Alt + ['.

5 In the 'Key Sequence' field, change the value to 'Ctrl+Alt+219'.

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.

3 Click the '+' 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+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.

3 Click the '+' sign in Object Explorer and choose 'Accelerator'.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 41 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

4 Copy the Record Name '2'. Name the New Record '3'.

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.

3 Click on '+' sign in Object Explorer and choose 'Accelerator'.

4 Copy the Record Name '1'. Name the New Record '2'

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.
3 Click on '+' sign in Object Explorer and choose 'Accelerator'.

4 Copy the Record Name '2'. Name the New Record '3'.

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.

3 Click on '+' sign in Object Explorer and choose 'Accelerator'.

4 Copy the Record Name '2'. Name the New Record '3'.

416 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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


1 Navigate to Object Explorer in Siebel Tools.

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.

New /
Changed Applet Name Title Description SIA SIF File Name HOR SIF File Name

Changed Search lookin Search Provides a title AppletSearchlookin_SIA.sif AppletSearchlookin_HOR.sif


to the applet
for screen
readers to
read out.

To add the DefaultFocus User Property


1 Navigate to Object Explorer in Siebel Tools.
2 Navigate to Applet.

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.

New / Applet User SIA SIF File


Changed Applet Name Property Value Description Name HOR SIF File Name

Changed Search lookin DefaultFocus SearchFor Added the user AppletSearchlo AppletSearchlookin_HOR.sif
property to set the okin_SIA.sif
default focus

Creating the View Info Command


The following procedure explains how to create the View Info command.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 41 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

To create the View Info command


1 Navigate to Object Explorer in Siebel Tools.

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"

Key SIA SIF HOR SIF


Command Project Action Accelerator Sequence Description File Name File Name

View Info Command ViewInfo Ctrl + Alt + Z Ctrl + Alt A new shortcut CmdViewInf CmdViewInf
+Z key that o_SIA.sif o_HOR.sif
generates a
dialog box that
contains
ViewName, View
Summary and
Applet Names

Sub-View Tab SWE N/A Ctrl + Alt + V Ctrl +Alt N/A CmdSubVie CmdSubVie
(SWE SI) +V wTab_SIA.si wTab_HOR.s
f if

4 Add a new Accelerator to the Command for the required Key Combination with the following
values:

■ NAME="1"

■ BROWSER_PLATFORM="All"
■ DISPLAY_NAME_-_STRING_REFERENCE="SBL_DOES_NOT_MATTER-1004225828-03I"

■ 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 uses Generic Web Menu.)

■ Name="Hidden-View Info

■ Position=8.39

418 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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
“Importing SIF Files” on page 61.

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 41 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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.

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.

420 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

1 Navigate to Object Explorer in Siebel Tools.

2 Navigate to View > Options, and click the Object Explorer tab.

3 Select the 'Command' object and click OK to add the Command Strings object to Object Explorer.

4 Within Object Explorer, click the Command object and query for 'Previous Record(SWE)'
Command.

5 Lock the object.

6 Click the '+' sign in Object Explorer and choose 'Accelerator'.

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.


11 Click the '+' sign in Object Explorer and choose 'Accelerator'.
12 Change 'Display Name' from 'Ctrl+.' to 'Alt +.'
13 In the 'Key Sequence' field, change the value to Alt+0xBE.

Current
New/ String
Changed Project Name Value HOR SIF File Name SIA SIF File Name

New Symbolic Strings SBL_ALT+, Alt+, symbolistring_Next_Prev_H symbolistring_Next_Prev_S


OR.sif IA.sif

New Symbolic Strings SBL_ALTL+. Alt+. symbolistring_Next_Prev_H symbolistring_Next_Prev_S


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 Command Alt +, Alt+0xBC Next_Prev_HOR.sif Next_Prev_HOR.sif


Record(SWE)

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

New/
Changed Project Name Current String Value HOR SIF File Name SIA SIF File Name

Changed Symbolic SBL__IMG_SRC__IMA <IMG SRC="images/ orangebullet_HOR.sif orangebullet_SIA.sif


Strings GES/ orange_bullet.gif"
CHEVRON_SM.GIF__ align="right" border="0"
ALIGN__RIGHT__BOR alt="" >
DER__0

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 42 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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
about how to import .sif files, see “Importing SIF Files” on page 61.

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 Create a new string for the Control
Message

To enable or disable the confirmation message upon page refresh


1 Log into the application using /editseeddata (for thick 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:

Language
Display Independent
Type Value Translate Multilingual Code Order Language Name

SWE_CONFIRMATION TRUE Yes Yes TRUE 1 English-American


_MESSAGE

SWE_CONFIRMATION FALSE Yes Yes FALSE 2 N/A


_MESSAGE

3 After you have added these changes, navigate to Screen > System Administration > List Of
Values to view these changes in the repository.

New/ Business
Changed Name Project Component Static Type Field Type Value

New Confirmation User Preference PickList Generic Yes Type SWE_CONFIRM_MESSAGE


Message
Picklist

The following changes have been made to the User Preferences Business Component.

Name PickList Predefault Value Type

SWE/Confirmation Message Confirmation Message TRUE DTYPE_TEXT


Picklist

422 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

The following table describes the new User Profile Confirmation Message Parameter Applet that has
been added to support ACR 422.

New/ Business
Changed Name Project Component Class Title

New User Profile User User Preferences CSSFrameBase Accessibility


Confirmation Message Preferences
Parameter Applet

The following table describes the applet controls changes that have been implemented to support
ACR 422.

Name Caption Field HTML Type Method Invoked Runtime Field Type

Applet Title Accessibility N/A Text N/A N/A N/A

ConfirmMssg Confirmation SWE/ Text N/A Yes BC Field


Message Confirmation
Message

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.

Visibility Applet
New/Changed Name Project Business Object Type

New User Profile User Preferences User Preferences User Profile


Confirmation Message Confirmation Message
Parameter View Parameter Applet

The following table describes the User Profile screen changes that have been added to support ACR
422.

Visibility Applet
New/Changed Name View Type Type

New User Profile User Profile Aggregate View User Profile


Confirmation Message Confirmation Message Confirmation Message
Parameter View Parameter View Parameter Applet

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 42 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

New/ Web
Changed Name Project Template SIF File

New PUB Disease Case PUB HLS Bio Terrorism Edit Disease_Case_SIA.sif
List Applet

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
1 Navigate to Object Explorer in Siebel Tools.

2 Navigate to View > Options, and click the Object Explorer tab.

3 Select the 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 select 'New Record'.

6 Add the new records mentioned in the following table.

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

To implement the NextPage and PreviousPage commands


1 Navigate to Object Explorer in Siebel Tools.

2 Navigate to View > Options, and click the Object Explorer tab.

424 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

3 Select the 'Command' object and click OK to add the Command Strings object to Object Explorer.

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:

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

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'.
12 For 'Browser Platform' - Extended, in 'Display Name - String Reference', provide the newly
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'.

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

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 42 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

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.

To import SIF 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.

426 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Importing SIF Files for Table Changes


The procedure in the following section describes how to add the applet summary for customized or
new applets.

To import the SIF 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:

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 42 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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.

Importing the Accessibility Project SIF Files


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

428 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

4 Add the following new LOV types and values:

Type Value

ACC_ATTRIB_TYPE Summary

ACC_ATTRIB_TYPE Label

ACC_LOCALE ENU

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 42 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

430 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

5 Edit the “Position on Row” control’s 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:

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

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:

■ Accessibility Applet Attributes

■ Accessibility View Attributes

Applets:

■ Accessibility Applet Attributes List Applet

■ Accessibility Applet Attributes Form Applet

Business Objects:

■ Accessibility Applet Attributes

■ Accessibility View Attributes

Views:

■ Accessibility Applet Attributes View

■ Accessibility View Attributes View

Picklists:

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 43 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Instructions for ACR 574


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

❏ sscashsv.dll

432 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 43 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ eCatalog Admin

❏ eMail Response

4 Compile all of the locked projects.

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:

❏ Siebel Administrator
❏ Call Center Administrator

❏ eMail Response Agent

❏ eMail Response Manager

434 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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

❏ EMR_UI_WF.sif

3 Upon successful import, within Siebel Tools, make sure the following projects are locked:

❏ Mail Agent

❏ eMail Response

4 Compile all of the locked projects.

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:

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 43 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

■ 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


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

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.

436 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

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.

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 43 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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.

Instructions for ACR 623


For information about how to configure the IOG integration, see Real-Time Decisions (RTD) for Siebel
Intelligent Offer Generation (IOG) Installation and Reference Guide. To access this guide, within My
Oracle Support, navigate to the Knowledge tab, and search for Doc ID 1169164.1.

Instructions for ACR 626

Supported Devices for Oracle Mobile Sales Assistant


The following are the supported versions for different components for ACR 626:

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

Release Notes for ACR 626


The following section contains information about known issues with ACR 626.

438 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

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


Category: Mobile Solutions

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


Category: Mobile Solutions

Subcategory: Other

Change Request: 12-20W3J8R

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 the ones 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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 43 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Configuration Instructions
for Enhancements and Updates

❏ Division

❏ Web Service Integration

❏ 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

8 Restart the Siebel Server.

9 Navigate to Site Map > Web Service Administration > Inbound Web Services, and import the
following files:

❏ "SWIAccountNoteServices.XML"

❏ "SWIAccountServices.XML"

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

440 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

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 Fix Pack Installation Instructions


This topic includes the following subtopics:

■ “Siebel Fix Pack Installation Overview” on page 441

■ “About Installing Siebel Fix Packs” on page 445

■ “Installing the Siebel Fix Pack on Microsoft Windows” on page 446

■ “Installing the Siebel Fix Pack on UNIX” on page 452

■ “Configuring Slipstream Patch Installation” on page 456

■ “Postinstallation Task for the Siebel Server” on page 458

■ “Postinstallation Task for the Web Server” on page 458

■ “Postinstallation Tasks for High Interactivity Clients” on page 459

■ “Postinstallation Task for Supporting Additional Languages” on page 459

■ “Uninstalling Siebel Fix Packs” on page 460

Siebel Fix Pack Installation Overview


This topic is part of “Siebel Fix Pack Installation Instructions” on page 441.

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 44 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

NOTE: This Siebel Maintenance Release Guide includes information for the latest Siebel Fix Pack
8.1.1.x release. Each Fix Pack is cumulative and includes all fixes included in previous Siebel Fix Pack
8.1.1.x releases (where applicable). You can install the latest Siebel Fix Pack 8.1.1.x release on top
of version 8.1.1 or any prior version 8.1.1.x release.

Before installing this Fix Pack, it is strongly recommended to read all the information in the topics in
this section (“Siebel Fix Pack Installation Instructions” on page 441). See also “How to Use This Guide”
on page 10.

This document describes Fix Pack installation and related tasks for several key products, but not for
all Siebel Business Applications products that may apply to your deployment. Fix Pack installation
tasks for products not covered here are generally similar to those described here.

This topic includes the following subtopics:

■ “Installation Scenarios Described in This Guide” on page 442

■ “Applicable Base Releases” on page 443

■ “About Running Siebel Image Creator” on page 444

■ “About Installing Additional Languages” on page 444

■ “About Installing Siebel Quick Fix Releases” on page 445

Installation Scenarios Described in This Guide


This topic is part of “Siebel Fix Pack Installation Overview” on page 441.

Installation instructions in this guide apply in the following scenarios:

■ Performing new full installation of version 8.1.1, with Siebel Fix Pack 8.1.1.x. If you are
installing version 8.1.1 (a new full installation), follow the installation instructions in the Siebel
Installation Guide for the operating system you are using. Also follow the instructions in this
Siebel Maintenance Release Guide for installing the latest Siebel Fix Pack 8.1.1.x release on top
of version 8.1.1.

Optionally, you can install 8.1 and 8.1.1.x together by configuring slipstream patch installation
for server-based Siebel modules. For details, see “Configuring Slipstream Patch Installation” on
page 456.

For the most recent version of the Siebel Installation Guide for the operating system you are
using, see the latest version 8.1 Siebel Bookshelf.

For more information about installing Siebel Fix Pack 8.1.1.x, see “About Installing Siebel Fix
Packs” on page 445.

442 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

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

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

■ Adding languages. When you perform a new version 8.1.1 installation of Siebel Business
Applications, it is recommended to include any supported languages (language packs) you
require or expect to require. You can also add languages to an existing installation; some
additional steps are required in this case.

For more information, see “About Installing Additional Languages” on page 444.

Applicable Base Releases


This topic is part of “Siebel Fix Pack Installation Overview” on page 441.

In general, each Siebel Fix Pack can be installed on top of an existing Siebel installation of the same
product suite that is at a valid base version level for this Fix Pack.

Installing any Fix Pack requires an existing installation of a qualified base release to install into. Here,
base release means the current version of the existing installation, including version 8.1.1 software
and optionally including any installed Siebel Fix Pack 8.1.1.x or other patch releases.

Here are the base releases and Siebel Business Applications product suites for installing the latest
Siebel Fix Pack 8.1.1.x release:

■ Siebel Industry Applications, version 8.1.1 or version 8.1.1.x

■ Siebel Cross-Industry Applications, version 8.1.1 or version 8.1.1.x

Do not install a Fix Pack for one product suite on top of a base installation for another product suite.
Such combinations are incompatible.

Siebel Industry Applications are composed of multiple industry product groups (vertical
applications). For a detailed listing of the industry products contained in each group, see Siebel
System Requirements and Supported Platforms on Oracle Technology Network.

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 44 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

About Running Siebel Image Creator


This topic is part of “Siebel Fix Pack Installation Overview” on page 441.

The Siebel Image Creator utility is used to create an installation image (sometimes called a network
image) for version 8.1.1 or any Siebel Fix Pack 8.1.1.x release. The image can include any Siebel
installable product and language provided as part of this product release.

You can also add products or languages to an existing installation image of the same version, for
products or languages that were not previously included.

Installing any Siebel Business Applications release, including a new installation of version 8.1.1, an
installation of a Siebel Fix Pack 8.1.1.x release, or the addition of one or more languages, must be
done from an installation image created using Image Creator.

NOTE: Always use the version of Siebel Image Creator provided with the Siebel release for which
you are creating the installation image.

Information about using Siebel Image Creator is provided in the Siebel Installation Guide for the
operating system you are using, on the version 8.1 Siebel Bookshelf.

About Installing Additional Languages


This topic is part of “Siebel Fix Pack Installation Overview” on page 441.

Include or add all languages you will require in your Siebel version 8.1.1 installation image (network
image), which you create using the Siebel Image Creator utility. Then install the software with the
languages you require. When you configure each installed Siebel Server and Siebel Web Server
Extension, you also specify which installed languages you are deploying.

Optionally, you can add languages to an existing installation. Some postinstallation tasks are
required in order to deploy a language you added after initial product installation and configuration:

■ If you add a language after you have configured an installed Siebel Server, launch the Siebel
Server Configuration Wizard and run the configuration task Add Language Support for the Siebel
Server. (It is not necessary to reconfigure the Siebel Server.)

■ If you add a language after you have configured an installed Siebel Web Server Extension
(SWSE), launch the SWSE Configuration Wizard and run the configuration task Add Language
Support for the SWSE Configuration. (It is not necessary to reconfigure the SWSE.)

After adding a language to your installed software, you must add the language to the Siebel
Database, import Siebel Repository data into the database for this language, and run the MLOV
(multilingual LOV) conversion utility. It is recommended to perform database-related tasks after
installing applicable Fix Packs or other patch releases.

NOTE: If you are adding languages to an existing installation, do so before you install the latest
Siebel Fix Pack 8.1.1.x release. It is possible to add a language after a Fix Pack has been installed.
However, for each component for which you add a language, you must reinstall the Fix Pack to bring
the language pack files up to the current release level. (Because Fix Packs are cumulative, you can
install just the latest Siebel Fix Pack 8.1.1.x release, even if you previously installed a prior Fix Pack
before adding the language.)

If you are not adding languages, you only need to install the latest Siebel Fix Pack 8.1.1.x release,
as described in this guide.

444 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

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 Task for Supporting Additional Languages” on page 459.

About Installing Siebel Quick Fix Releases


This topic is part of “Siebel Fix Pack Installation Overview” on page 441.

After installing version 8.1.1 and a Siebel Fix Pack 8.1.1.x release as described in this guide, you can
also install any applicable Siebel Quick Fix releases on top of version 8.1.1.x. When you install a
Quick Fix, installed languages may also be patched, depending on the content of the Quick Fix
release.

NOTE: Installing Quick Fixes may entail restrictions about which subsequent Fix Packs can be
installed.

For detailed information about a particular Quick Fix, see the documentation that is provided
separately with the Quick Fix.

“Quick Fixes Included in 8.1.1.x Fix Packs” on page 11 identifies fixes from previous Quick Fix releases
that are included in specific Siebel Fix Pack 8.1.1.x releases.

About Installing Siebel Fix Packs


This topic is part of “Siebel Fix Pack Installation Instructions” on page 441.

For each Siebel Business Applications product module, installing the latest Siebel Fix Pack 8.1.1.x
release on top of an existing base installation replaces existing executable files and provides new
files in addition to the base installation.

For supported base releases, see “Siebel Fix Pack Installation Overview” on page 441.

Installing a Fix Pack does not replace any customer-modified files (for example, application
configuration files like siebel.cfg) that govern program execution. When you install a Fix Pack, any
installed languages may also be patched, depending on the content of the Fix Pack.

NOTE: References in this guide to Siebel Fix Pack 8.1.1.x releases apply to the current Fix Pack
release. However, you must verify the availability, characteristics, and requirements of any future Fix
Pack releases, including Siebel Fix Pack 8.1.1.x releases. Installation tasks and requirements for all
future releases are subject to change, and will be covered by updated documentation.

If you plan to install any additional Siebel language packs, review “Siebel Fix Pack Installation
Overview” on page 441 (in particular, “About Installing Additional Languages” on page 444) before you
install any Fix Pack.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 44 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

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

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. For more information, see also
“Postinstallation Task for the Web Server” on page 458.

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

For information about uninstallation and Fix Packs, see “Uninstalling Siebel Fix Packs” on page 460.

For instructions for installing Siebel Fix Pack 8.1.1.x for your operating system platform, see:

■ “Installing the Siebel Fix Pack on Microsoft Windows” on page 446

■ “Installing the Siebel Fix Pack on UNIX” on page 452

Installing the Siebel Fix Pack on Microsoft Windows


This topic is part of “Siebel Fix Pack Installation Instructions” on page 441.

Procedures for installing Siebel Fix Pack 8.1.1.x for products on Microsoft Windows are detailed
below. Follow these instructions to install each product over the existing base installation for the
same product. Perform the steps that apply for the Fix Pack you are installing, in the general
sequence presented here.

Before you install the Fix Pack, review all applicable information in “Siebel Fix Pack Installation
Overview” on page 441 and “About Installing Siebel Fix Packs” on page 445.

Instructions generally assume that Fix Pack installers are launched in GUI mode. Alternatively, the
installers for server-based products can be launched in console or unattended mode. The Fix Pack
installation runs silently.

NOTE: If you installed version 8.1.1 Siebel software using the Siebel FastTrack Wizard, use the Fix
Pack installers for Siebel Enterprise Server and Siebel Web Server Extension to patch any installed
instances of these modules. The FastTrack Wizard is provided for small to medium businesses (SMB).
For more information, see Siebel Installation Guide for Microsoft Windows.

This topic has the following subtopics:

■ “Installing the Fix Pack for Siebel Enterprise Server on Windows” on page 447

■ “Installing the Fix Pack for Siebel Web Server Extension on Windows” on page 447

■ “Installing the Fix Pack for Siebel Management Agent and Siebel Management Server on Windows”
on page 448

■ “Installing the Fix Pack for Siebel Mobile Web Client, Siebel Tools, Siebel Sample Database, or Siebel
Client Sync on Windows” on page 449

446 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

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

Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any machine where a Siebel
Enterprise Server component is installed, including Siebel Server, Siebel Gateway Name Server, and
Database Configuration Utilities (formerly known as Siebel Database Server).

The Fix Pack installer for Siebel Enterprise Server also patches any instance of Siebel Management
Agent that was 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 448.

To install the Fix Pack for Siebel Enterprise Server components


1 Shut down the Siebel Business Applications product component to be updated. For example, stop
the service for the Siebel Server or Siebel Gateway Name Server. Also shut down any running
instances of the Siebel Server Manager (srvrmgr).

2 If you are patching an instance of Siebel Management Agent that was previously installed with a
Siebel Server, also stop the service for the Management Agent.

3 In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For Siebel Enterprise Server, navigate to
Siebel_Image\Windows\Server\Siebel_Enterprise_Server, where:

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

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

5 Select an instance of version 8.1.1 or version 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 machine 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
This topic is part of “Installing the Siebel Fix Pack on Microsoft Windows” on page 446.

Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any machine where a Siebel
Web Server Extension (SWSE) component is installed.

NOTE: Before you install any Fix Pack release for SWSE, refer to Siebel System Requirements and
Supported Platforms on Oracle Technology Network 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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 44 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

To install the Fix Pack for Siebel Web Server Extension


1 Stop the Web server.

2 In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For SWSE, navigate to
Siebel_Image\Windows\Server\Siebel_Web_Server_Extension, where:

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

3 Double-click setup.exe to launch the SWSE installer for version 8.1.1.x.

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

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

6 Repeat these steps on each machine 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 Task for the Web Server” on page 458.

Installing the Fix Pack for Siebel Management Agent and Siebel
Management Server on Windows
This topic is part of “Installing the Siebel Fix Pack on Microsoft Windows” on page 446.

Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on machines where Siebel
Management Agent or Siebel Management Server are installed.

NOTE: Instructions for installing Siebel Management Agent assume that Management Agent was
installed separately. If your instances of Management Agent were installed as part of Siebel Server
installation, follow the instructions in “Installing the Fix Pack for Siebel Enterprise Server on Windows”
on page 447. See also the Siebel Installation Guide for the operating system you are using.

When you install a Fix Pack for an instance of Siebel Management Agent, the Siebel Management
Server will be unable to connect to it. It is not necessary to shut down the Management Server while
you install the Fix Pack for the Management Agents. After you install the Fix Pack for all instances of
Management Agent, shut down the Siebel Management Server, then install the Fix Pack for
Management Server. After you restart Management Server, it automatically reconnects to each
instance of Management Agent. Newly patched instances of Management Agent will not be
operational until Management Server has also been patched.

To install the Fix Pack for Siebel Management Agent (where Management Agent was
installed separately)
1 Stop the Siebel Management Agent service.

448 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

2 In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For Siebel Management Agent, navigate to
Siebel_Image\Windows\Server\Siebel_Management_Agent, where:

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

3 Double-click setup.exe to launch the Siebel Management Agent installer for version 8.1.1.x.

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

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

6 Restart the Management Agent service.

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

To install the Fix Pack for Siebel Management Server


1 Stop the Siebel Management Server service.

2 In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For Siebel Management Server, navigate to
Siebel_Image\Windows\Server\Siebel_Management_Server, where:

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

3 Double-click setup.exe to launch the Siebel Management Server installer for version 8.1.1.x.

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

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


6 Restart the Management Server service.

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

Installing the Fix Pack for Siebel Mobile Web Client, Siebel Tools,
Siebel Sample Database, or Siebel Client Sync on Windows
This topic is part of “Installing the Siebel Fix Pack on Microsoft Windows” on page 446.

Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on machines where Siebel Mobile
Web Client, Siebel Tools, Siebel Sample Database, or Siebel Client Sync are installed. (Most of the
information for Siebel Mobile Web Client also applies to Siebel Developer Web Client.)

NOTE: As of version 8.1.1, the installer programs for Siebel Mobile Web Client and Siebel Tools are
based on the Oracle Universal Installer (OUI) framework, and have many differences from installers
for previous releases. For a detailed summary of installer changes, see the Siebel Installation Guide
for the operating system you are using.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 44 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

To install the Fix Pack for Siebel Mobile Web Client or Siebel Tools
1 Exit any Siebel software on the client machine where you are installing the Fix Pack.

NOTE: For a Siebel Mobile Web Client using the Siebel QuickStart feature, you must also exit the
QuickStart agent, if it is running. To do this, right-click the QuickStart icon in the system tray,
then choose Exit. For more information about using Siebel QuickStart with the Mobile Web Client,
see the Siebel Installation Guide for the operating system you are using.

2 In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located.

■ For Siebel Mobile Web Client, navigate to


Siebel_Image\Windows\Client\Siebel_Web_Client\Disk1\install

■ For Siebel Tools, navigate to Siebel_Image\Windows\Client\Siebel_Tools\Disk1\install

where:

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

3 Double-click oui.exe to launch 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 version
8.1.1.x to patch, from the list of detected Siebel installations.

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

6 Repeat these steps on each machine with an applicable Siebel client or Siebel Tools installation
to be patched.

NOTE: The machine may require a restart at the end of the installation.

To install the Fix Pack for Siebel Sample Database


1 Exit any Siebel software on the client machine where you are installing the Fix Pack.
2 Before you install the Fix Pack for the Siebel Sample Database, perform the following steps on
the Siebel Mobile Web Client or Siebel Tools machine where you previously installed version 8.1.1
of the Sample Database.

CAUTION: If you do not perform these steps, an error will occur when you try to install the Fix
Pack for the Sample Database, and installation will not complete.

a Create a text file called upgrade.txt.

b Add text to this file similar to the following:

INSTALLED : 8.1.1.1 : : Wed Jul 22 02:23:26 MDT 2009

The version number should reflect the actual version of the Siebel Fix Pack 8.1.1.x release
you are installing.

c Save the file.

d Place a copy of the file in the folder SIEBEL_CLIENT_ROOT or SIEBEL_TOOLS_ROOT, depending


on where you originally installed the Sample Database.

450 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

e Make a copy of the file for each installed language, named upgrade_lang.txt, such as
upgrade_enu.txt for U.S. English (ENU).
f Place each language-specific copy of the file in the folder SIEBEL_CLIENT_ROOT or
SIEBEL_TOOLS_ROOT.

NOTE: If you install a future Siebel Fix Pack 8.1.1.x release for the Mobile Web Client or Siebel
Tools, update all applicable upgrade.txt and upgrade_lang.txt files again to reflect the new
version number. Do this before you install the new Fix Pack for the Sample Database.

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 Sample Database, navigate to
Siebel_Image\Windows\Client\Siebel_Sample Database, where:

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

4 Double-click install.exe to launch the Siebel Sample Database client installer for version 8.1.1.x.

5 Select an instance of version 8.1.1 or version 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 machine with an applicable Siebel Sample Database installation to
be patched.

NOTE: The machine may require a restart at the end of the installation.

To install the Fix Pack for Siebel Client Sync


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

2 In Windows Explorer, navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For Siebel Client Sync, navigate to
Siebel_Image\Windows\Client\Siebel_Client_Sync, where:

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

3 Double-click install.exe to launch the Siebel Client Sync client installer for version 8.1.1.x.
4 Select an instance of version 8.1.1 or version 8.1.1.x to patch, from the list of detected Siebel
installations.

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

6 Repeat these steps on each machine with an applicable Siebel Client Sync installation to be
patched.

NOTE: The machine may require a restart at the end of the installation.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 45 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

Installing the Siebel Fix Pack on UNIX


This topic is part of “Siebel Fix Pack Installation Instructions” on page 441.

Procedures for installing Siebel Fix Pack 8.1.1.x for products on supported UNIX and Linux platforms
are detailed below. Follow these instructions to install each product over the existing base installation
for the same product. Perform the steps that apply for the Fix Pack you are installing, in the general
sequence presented here.

Before you install the Fix Pack, review all applicable information in “Siebel Fix Pack Installation
Overview” on page 441 and “About Installing Siebel Fix Packs” on page 445.

Instructions generally assume that Fix Pack installers are launched in GUI mode. Alternatively, the
installers for server-based products can be launched in console or unattended mode. The Fix Pack
installation runs silently.

NOTE: Some Siebel Business Applications products can only be installed on Windows, such as Siebel
Management Server, Siebel Mobile Web Client, Siebel Tools, or Siebel Client Sync. For more
information, see “Installing the Siebel Fix Pack on Microsoft Windows” on page 446.

This topic has the following subtopics:

■ “Installing the Fix Pack for Siebel Enterprise Server on UNIX” on page 452

■ “Installing the Fix Pack for Siebel Web Server Extension on UNIX” on page 453

■ “Installing the Fix Pack for Siebel Management Agent on UNIX” on page 455

Installing the Fix Pack for Siebel Enterprise Server on UNIX


This topic is part of “Installing the Siebel Fix Pack on UNIX” on page 452.

Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any machine where a Siebel
Enterprise Server component is installed, including Siebel Server, Siebel Gateway Name Server, and
Database Configuration Utilities (formerly known as Siebel Database Server).

The Fix Pack installer for Siebel Enterprise Server also patches any instance of Siebel Management
Agent that was installed with a Siebel Server you are patching. See also “Installing the Fix Pack for
Siebel Management Agent on UNIX” on page 455.

To install the Fix Pack for Siebel Enterprise Server components


1 Stop all running Siebel Servers by running the command stop_server on each applicable server
machine. (See Siebel System Administration Guide for details on how to use this command.) Also
shut down any running instances of the Siebel Server Manager (srvrmgr).

2 If you are patching an instance of Siebel Management Agent that was previously installed with a
Siebel Server, also stop the service for the Management Agent.

3 Unload libraries from the system cache by running the command reset_server all on each
applicable server machine. (See Siebel System Administration Guide for details on how to use
this command.)

4 Stop the Siebel Gateway Name Server by running the command stop_ns. (See Siebel System
Administration Guide for details on how to use this command.)

452 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

5 (AIX only) Verify that the login ID performing installation has permission to run slibclean by
asking the administrator to change the permission as follows:

chmod 6555 /usr/sbin/slibclean

6 (AIX only) Execute slibclean, as follows:

/usr/sbin/slibclean

7 Open a new shell and navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For Siebel Enterprise Server, navigate to Siebel_Image/
UNIX_OS/Server/Siebel_Enterprise_Server, where:

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

■ UNIX_OS is your UNIX operating system, such as AIX, HPUX (HP-UX), Linux, or Solaris.

8 (For GUI mode) Run setupUNIX_OS to launch the Siebel Enterprise Server installer in GUI mode
for version 8.1.1.x, where:

■ UNIX_OS is your UNIX operating system, such as aix (AIX), hp (HP-UX), linux (Linux), or sol
(Solaris).

Go to Step 10 on page 453.

9 (For console mode) Enter the following command to launch the Siebel Enterprise Server installer
in console mode for version 8.1.1.x:

setupUNIX_OS –is:javaconsole -console

where:

■ UNIX_OS is your UNIX operating system, such as aix (AIX), hp (HP-UX), linux (Linux), or sol
(Solaris).

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

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


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

13 Restart all applicable Siebel Business Applications product components at the end of all Fix Pack
or other patch release installation for server-based products.

Installing the Fix Pack for Siebel Web Server Extension on UNIX
This topic is part of “Installing the Siebel Fix Pack on UNIX” on page 452.

Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on any machine where a Siebel
Web Server Extension (SWSE) component is installed.

NOTE: Before you install any Fix Pack for SWSE, refer to Siebel System Requirements and Supported
Platforms on Oracle Technology Network to verify that the Web server version is correct for the Siebel
Business Applications release. If you need to update the Web server, do so before you install the Fix
Pack for SWSE.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 45 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

To install the Fix Pack for Siebel Web Server Extension


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

■ ompmnctl stopall - for Oracle HTTP Server (on supported Linux platforms)

■ stopapa – for other Apache-based Web servers (on AIX, HP-UX, or supported Linux platforms)

■ stop – for Sun Java System Web Server (on Sun Solaris)

2 Log on to the server using the Web server owner account.

3 (AIX only) Verify that the login ID performing installation has permission to run slibclean by
asking the administrator to change the permission as follows:

chmod 6555 /usr/sbin/slibclean

4 (AIX only) Execute slibclean, as follows:

/usr/sbin/slibclean

5 Open a new shell and navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For SWSE, navigate to Siebel_Image/UNIX_OS/Server/
Siebel_Web_Server_Extension, where:

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

■ UNIX_OS is your UNIX operating system, such as AIX, HPUX (HP-UX), Linux, or Solaris.

6 (For GUI mode) Run setupUNIX_OS to launch the SWSE 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 8 on page 454.

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

setupUNIX_OS –is:javaconsole -console

where:

■ UNIX_OS is your UNIX operating system, such as aix (AIX), hp (HP-UX), linux (Linux), or sol
(Solaris).

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

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

10 Repeat these steps on each machine 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 Task for the Web Server” on page 458.

454 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

Installing the Fix Pack for Siebel Management Agent on UNIX


This topic is part of “Installing the Siebel Fix Pack on UNIX” on page 452.

Use the instructions that follow for installing Siebel Fix Pack 8.1.1.x on machines where Siebel
Management Agent is installed.

NOTE: Instructions for installing Siebel Management Agent assume that Management Agent was
installed separately. If your instances of Management Agent were installed as part of Siebel Server
installation, follow the instructions in “Installing the Fix Pack for Siebel Enterprise Server on UNIX” on
page 452 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 448.

When you install a Fix Pack for an instance of Siebel Management Agent, the Siebel Management
Server will be unable to connect to it. It is not necessary to shut down the Management Server while
you install the Fix Pack for the Management Agents. After you install the Fix Pack for all instances of
Management Agent, shut down the Siebel Management Server, then install the Fix Pack for
Management Server. After you restart Management Server, it automatically reconnects to each
instance of Management Agent. Newly patched instances of Management Agent will not be
operational until Management Server has also been patched.

To install the Fix Pack for Siebel Management Agent (where Management Agent was
installed separately)
1 Stop the service for the Siebel Management Agent.

2 (AIX only) Verify that the login ID performing installation has permission to run slibclean by
asking the administrator to change the permission as follows:

chmod 6555 /usr/sbin/slibclean

3 (AIX only) Execute slibclean, as follows:

/usr/sbin/slibclean

4 Open a new shell and navigate to the Siebel image location for version 8.1.1.x, then to the
directory where the installer is located. For Siebel Management Agent, navigate to Siebel_Image/
UNIX_OS/Server/Siebel_Management_Agent, where:

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

■ UNIX_OS is your UNIX operating system, such as AIX, HPUX (HP-UX), Linux, or Solaris.

5 (For GUI mode) Run setupUNIX_OS to launch the Siebel Management Agent 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 7 on page 456.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 45 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

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

setupUNIX_OS –is:javaconsole -console

where:

■ UNIX_OS is your UNIX operating system, such as aix (AIX), hp (HP-UX), linux (Linux), or sol
(Solaris).

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

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

9 Restart the Management Agent service.

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

Configuring Slipstream Patch Installation


This topic is part of “Siebel Fix Pack Installation Instructions” on page 441.

Slipstream patch installation is the ability to configure installer behavior so that an installer process
(for full installation or Fix Pack installation) automatically invokes one or more patch installations for
the same product. The main installation can be performed in applicable installer modes (GUI,
console, or unattended mode). The Fix Pack or other patch installation runs silently.

NOTE: As noted in the Siebel Installation Guide for the operating system you are using, slipstream
patch installation applies only to installations of server-based Siebel modules. As of version 8.1.1,
installers for Siebel client modules are based on Oracle Universal Installer technology (and do not
use siebel.ini files) and do not support slipstream patch installation.

Where slipstream patch installation is invoked by a full installation rather than by another patch
installation, the patch installation executes after language packs are installed. After all installations
are complete, the Siebel Configuration Wizard launches, for applicable products.

As noted in “Siebel Fix Pack Installation Overview” on page 441, slipstream patch installation may
apply in multiple installation scenarios. Applicable scenarios for the current product releases include:

■ Full installation plus patch installation. Performing a version 8.1.1 full installation plus a
Siebel Fix Pack 8.1.1.x installation. This scenario may optionally also include a Quick Fix release
for version 8.1.1.x (where applicable).

■ Multiple patch installations. Performing a Siebel Fix Pack 8.1.1.x installation plus a Quick Fix
release for version 8.1.1.x (where applicable).

NOTE: If you are adding languages to an existing version 8.1.1 or 8.1.1.x installation, slipstream
installation does not apply for the installation session for installing the languages. However,
slipstream installation can be used when subsequently installing Siebel Fix Pack 8.1.1.x and Quick
Fix releases. For more information about installing languages, see “About Installing Additional
Languages” on page 444.

456 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

You configure slipstream patch installation by modifying the base siebel.ini files for each applicable
Siebel module in the version 8.1.1 or version 8.1.1.x installation image, according to your install
scenario.

The siebel.ini files are also modified in installation scenarios described in the chapter about
unattended and console mode installations, in the Siebel Installation Guide for the operating system
you are using.

To support slipstream patch installation, where a version 8.1.1 full installation automatically invokes
a Siebel Fix Pack 8.1.1.x installation, modify the siebel.ini file for each applicable product for version
8.1.1, as shown below. Examples for setting Execute for different modules follow.

[Slipstream]
Install1 = yes

[Install1]
Execute = full_path_to_Siebel_product_installer_executable
Arg = arg_argument

where:

■ full_path_to_Siebel_product_installer_executable is the full path to the installer executable


program, located in the installation image for the release that will be installed using slipstream
patch installation.

■ arg_argument is the following value for a server installation:

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

Examples for Specifying Execute Parameter


To configure slipstream patch installation for Siebel Enterprise Server version 8.1.1.x on AIX, the
value for Execute might be as shown below. (The actual path would show the specific Siebel Fix Pack
8.1.1.x version.)

Execute = /Siebel_Image/8.1.1.x/AIX/Server/Siebel_Enterprise_Server/setupaix

To configure slipstream patch installation for Siebel Web Server Extension 8.1.1.x on Windows, the
value for Execute might be as shown below:

Execute =
D:\Siebel_Image\8.1.1.x\Windows\Server\Siebel_Web_Server_Extension\setup.exe

Configuring Multiple Slipstream Installations


If, when installing version 8.1.1, you use slipstream installation to install both version 8.1.1.x and a
Quick Fix release for version 8.1.1.x, you must configure multiple entries in the version 8.1.1
siebel.ini files.

To include the Quick Fix release in the slipstream patching sequence, add Install2 = yes under the
last entry in the [Slipstream] section, then configure an [Install2] section for the Quick Fix
release. Configure the [Install2] section so it resembles the [Install1] section you configured for
the Siebel Fix Pack 8.1.1.x, but points to the Quick Fix release instead.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 45 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

Postinstallation Task for the Siebel Server


This topic is part of “Siebel Fix Pack Installation Instructions” on page 441.

If you are using a security adapter, then you might need to update the value of the CRC parameter
after installing Siebel Fix Pack 8.1.1.x. The value must reflect the checksum value applicable to the
security adapter library file, such as a DLL file on Windows.

This task may be necessary if you previously determined to use checksum validation for your security
adapter deployment, and set the value of the CRC parameter. If a Fix Pack you installed later included
an updated security adapter library file, the checksum validation will fail and Siebel Web Clients
might not launch, unless the value of the CRC parameter is updated.

For detailed information about this task, see the topic about configuring checksum validation in
Siebel Security Guide.

Postinstallation Task for the Web Server


This topic is part of “Siebel Fix Pack Installation Instructions” on page 441.

The Web server must be restarted after you have finished installing Siebel Fix Pack 8.1.1.x on all
server-based components: Siebel Server, Siebel Gateway Name Server, Siebel Web Server Extension
(SWSE), and so on.

The restart is required because the Web server must be able to create a folder to contain static files
required for the current version of the Siebel application (corresponding to the latest Fix Pack
release). This folder is created as SWSE_ROOT/public/lang_code/build_number, where:

■ SWSE_ROOT is the location where the SWSE is installed

■ lang_code is each installed language (such as ENU for U.S. English)

■ build_number is the current build number of the installed Siebel software (the build number
comes from the content of the base.txt file on the SWSE installation)

The folder described above and other folders are created on the first SWSE request after installing
any Siebel Business Applications release. This folder is populated with static files copied from the
Siebel Server directory SIEBSRVR_ROOT/webmaster/siebel_build. The contents of these folders are
refreshed each time the Web server restarts, or when an administrator enters a Web update
command in the browser. After a build-specific folder is created on the SWSE, folders representing
earlier builds are no longer used.

For more information, see the Siebel Installation Guide for the operating system you are using and
Siebel Security Guide, both on 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.

458 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

Postinstallation Tasks for High Interactivity Clients


This topic is part of “Siebel Fix Pack Installation Instructions” on page 441.

After installing a new version of a Siebel application, including a Siebel Fix Pack, new versions of
applicable ActiveX controls for the high interactivity client will be downloaded onto your users’ client
computers when they run the Siebel application within the Internet Explorer browser. Alternatively,
updated versions of the ActiveX controls you require can be predeployed to the client machines.

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 may need to be cleared on
the client machine. To clear this data, choose Start, then Settings, then Control Panel, and then Java
Plug-In. Click the Cache tab, then click Reset.

After a new Siebel software version is installed, is also recommended that users clear their browser
cache. To do this in Internet Explorer, choose Tools, then Internet Options, and then choose Delete
Files from the General tab.

For the minimum supported version of the Sun Java Runtime Environment, see Siebel System
Requirements and Supported Platforms on Oracle Technology Network. The Sun JRE can be
downloaded automatically to your machines. As described in 475457.1 (Doc ID) on OracleMetaLink
3, some configuration may be required in order to download the correct version.

Postinstallation Task for Supporting Additional


Languages
This topic is part of “Siebel Fix Pack Installation Instructions” on page 441.

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

Importing Locale-Specific Data into the Repository


Sometimes it is necessary to update the text strings held in the repository for a particular language
or for multiple languages. These text strings are held in the Symbolic String Model (SSM) table, and
appear on-screen as labels for tabs, fields, and so on, across all Siebel Business Applications
products.

Updates may be needed either because a string has been incorrectly translated for a particular
language, or because installing a patch has caused a new string or message to appear for all
languages for which Oracle ships language packs for Siebel Business Applications.

NOTE: These instructions are provided for use with any releases to which they apply, and might not
apply for any particular version 8.1.1.x release or any particular language.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 45 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

The procedure below uses the Locale Management Utility (LMU), which is part of Siebel Tools, to
import an LMU file. An LMU file may contain strings in just one language or in multiple languages.
When running the Locale Management Utility, you can choose to import only the strings for the
languages you are actually using in your installation.

In the procedure below, when you are prompted for the file to import, specify the name of the LMU
file provided for the applicable language.

NOTE: Install any applicable Siebel Fix Pack before you run the Locale Management Utility.

For more information about using the Locale Management Utility, see Using Siebel Tools and Siebel
Global Deployment Guide.

To import strings and other locale-specific attributes into the repository


1 In Siebel Tools, choose Tools, then Utilities, and then Locale Management.

The Locale Management Utility appears.

2 Select a source language and a target language.

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

3 Click the Import tab.

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

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

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

When the import occurs, the LMU compares the source language records in the repository with
the source language records in the import file. If the records in the repository have changed since
the export occurred, they are marked with the Redo flag. This flag helps you identify records that
may 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 is part of “Siebel Fix Pack Installation Instructions” on page 441.

This topic describes how to uninstall Siebel Fix Pack 8.1.1.x releases for Microsoft Windows and for
supported UNIX and Linux platforms.

460 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Siebel Fix Pack
Installation Instructions

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, Siebel
Tools, or Siebel Sample Database. 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 461

■ “Instructions for Uninstalling a Siebel Fix Pack” on page 461

■ “Guidelines and Limitations for Siebel Fix Pack Uninstallation” on page 462

Scenarios for Uninstalling a Siebel Fix Pack


This topic is part of “Uninstalling Siebel Fix Packs” on page 460.

In some circumstances, you may need to, or choose to, uninstall a Siebel Fix Pack 8.1.1.x release
and revert to the base installation (version 8.1.1). For example:

■ You may decide to uninstall an existing installed Siebel Fix Pack 8.1.1.x release before installing
a later Fix Pack. (This is optional.)

■ If issues are encountered in your deployment, you may decide to uninstall an existing installed
Siebel Fix Pack 8.1.1.x release and revert to version 8.1.1. Subsequently (where multiple Fix
Packs have been released), you may decide to install a lower-level Fix Pack.

CAUTION: If you revert to the version 8.1.1 base installation, change request fixes and new
functionality added in any or all Siebel Fix Pack 8.1.1.x releases are no longer available, until an
applicable Fix Pack has been installed. You will also need to take steps described later in this topic,
under guidelines and limitations. See also “Enhancements and Updates in 8.1.1.x Fix Packs” on
page 32 and “Resolved Change Requests” on page 462.

Instructions for Uninstalling a Siebel Fix Pack


This topic is part of “Uninstalling Siebel Fix Packs” on page 460.

Follow the instructions below to uninstall the installed Siebel Fix Pack 8.1.1.x release and revert to
the version 8.1.1 base installation.

For more information about running uninstaller programs and about uninstalling Siebel base
installations, see the Siebel Installation Guide for the operating system you are using.

See also “Enhancements and Updates in 8.1.1.x Fix Packs” on page 32.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 46 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

To uninstall the Siebel Fix Pack on Microsoft Windows


1 To uninstall a Fix Pack on Windows, use the Add/Remove Programs utility to run the uninstaller.

NOTE: For applicable server-based modules, You can also invoke the uninstaller by running
SIEBEL_ROOT\_uninst\product\uninstaller.exe, where product is one of the following values: ses
(for Siebel Enterprise Server components) or eappweb (for SWSE).

2 At the prompt, select Maintenance Release Uninstall.

To uninstall the Siebel Fix Pack on supported UNIX or Linux platforms


1 To uninstall a Fix Pack on UNIX or Linux, run the following command:

$SIEBEL_ROOT/_uninst/product/uninstaller optional_arguments

where:

■ product is one of the following values: ses (for Siebel Enterprise Server components) or
eappweb (for SWSE)

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

2 At the prompt, select Maintenance Release Uninstall.

Guidelines and Limitations for Siebel Fix Pack Uninstallation


This topic is part of “Uninstalling Siebel Fix Packs” on page 460.

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, Siebel Tools,
and Siebel Sample Database. Only the full uninstallation option is possible for these modules.
(For Siebel Sample Database, this limitation is due to the module being dependent on either
Siebel Mobile Web Client or Siebel Tools.)

■ If a Fix Pack installation fails, it is recommended that the administrator attempt to uninstall and
then reinstall the Fix Pack. If the uninstaller for the Fix Pack is not available, proceed with
reinstalling the Fix Pack. If these steps are omitted, future attempts to uninstall the Fix Pack may
fail.

■ If you made any repository or configuration changes related to a Fix Pack you have installed,
then, before uninstalling the Fix Pack, the repository or configuration must be restored to the
state when the Fix Pack was first installed.

Resolved Change Requests


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

462 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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.

■ Fix Request ID. The tracking number for the fix request associated to the product defect.

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

■ Config Changes. 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. These configuration changes are described in detail in the linked document.

■ Quick Fix Information. If you have installed a Quick Fix, please review “Quick Fixes Included in
8.1.1.x Fix Packs” on page 11.

This topic contains the following subtopics:

■ “Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack” on page 463

■ “Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack” on page 507

■ “Resolved Change Requests in the Siebel 8.1.1.2 Fix Pack” on page 552

■ “Resolved Change Requests in the Siebel 8.1.1.1 Fix Pack” on page 577

Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack


This topic is part of “Resolved Change Requests” on page 462.

Table 16 lists the Change Request that were resolved in the 8.1.1.4 Fix Pack.

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Analytics
RTD
ACR 623: IOG Enhancements 12-1YM4H1Q 12-1YM4GZ9 8.1.1.4 Yes, see
and Certification with RTD 3.0 “Instructions for
ACR 623” on
page 438.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 46 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Call Center
CTI
Within OSES > Advanced Search 12-1VMB8J9 12-1V418VF 8.1.1.4
view, pressing Enter to execute
searches does not work

Other
When users press Alt F9 (Send 12-1YKOA8M 12-1XVFQ3H 8.1.1.4
Mail Wireless with SMS
Template), an activity is created
and then deleted

Oracle SES 12-1WUJ5UX 12-1WQ5PD9 8.1.1.4


CreateIncrementalIndex
overwrites feed files

Updates the Smart Answer 12-1Y72XTM 12-1XWEYTD 8.1.1.4


Admin Tool

With Siebel Chat, when a chat 12-1Z6EQIH 12-1YOLS71 8.1.1.4


contains a percentage sign (%),
the information after the
percentage sign is not sent

Functionality is not available to 12-1T4H0BC 12-1HE1XTL 8.1.1.4


set the owner for Created Email
Outbound Record to the user
who clicked the button

When users attempt to wrap up 12-1VK04GN 12-1VGM2U4 8.1.1.4


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

When users close a window 12-1VM6ZRB 12-1VE77T9 8.1.1.4


using the Close (x) icon, the
application hangs

Within OSES, when users click 12-1VR72Q7 12-1VNK8MB 8.1.1.4


the Search Results link in the
Search view, they receive an
error message

464 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

With OSES, Search Result 12-1XANOHD 12-1X65Y3T 8.1.1.4 Yes, see


Teasers display garbled “Instructions for
characters with the non-enu FR 12-
content of the UI name 1XANOHD” on
parameter page 701.

For outbound requests, when 12-1XYU5LR 12-1XCM26P 8.1.1.4


users press F9 to send an email
and then navigate to Send
HTML emails > Activity
Comments, the contents are
displaysed without any HTML
tags

Users can select separators in 12-1Y9ZMQB 12-1XM980D 8.1.1.4


Search drop-down lists

For activities, the Owned By 12-1TH3VYL 12-1SW8N2H 8.1.1.4


field does not get updated
correctly

The Lookin drop-down list loses 12-1Y5LXIO 12-1W7XG6V 8.1.1.4


selections after consecutive
searches on parent categories

With OSES, searching does not 12-1YJ7WRD 12-1XM987B 8.1.1.4


work with partial values

The All option does not search 12-1Z0MD73 12-1XM986H 8.1.1.4 Yes, see
on Web datasources “Instructions for
FR 12-
1Z0MD73” on
page 701.

With Advanced Search, the 12-1Z7DR3K 12-1YAH4TL 8.1.1.4


Modified Between Dates option
appears to be caching values
between users

It is not possible to search using 12-1ZAR9M8 12-1Z1KQY9 8.1.1.4


exact phrases

Even after QA0150 has been 12-1ZB8WZG 12-1YOKFU7 8.1.1.4


applied, when users press F9
within the Members List screen,
Internet Explorer hangs

When users accept incoming 12-1ZBPWC2 12-1YAH55T 8.1.1.4


chats, Siebel Chat displays the
incorrect SR number

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 46 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Comm Media
Energy
Assets
Modifying two assets generates 12-1ZM2V2V 12-1ZFBCAH 8.1.1.4
a query with full table scan on
S_ASSET table.

Connectors/EAI
EAI Server
Components
Extends the Siebel web services 12-1XKSPJH 12-1VMAPI0 8.1.1.4
framework to provide an
endpoint through Oracle WLS
(ACR 543)

EAI HTTP Transport hangs when 12-1YR2YDT 12-1YKOJJJ 8.1.1.4


SOAP response includes special
characters

When the EAI Siebel Adapter 12-1Y642Q1 12-1Y28AMJ 8.1.1.4


cache is released, a crash occurs

Siebel EAI queries for all 12-1XP5RAA 12-1XLAL87 8.1.1.4


existing child records when a
new child record is added

EAI Adapter is unable to process 12-1Y285PL 12-1VMAEWV 8.1.1.4


child integration components
that use the same user key

Users experience performance 12-1YDWEYX 12-1Y8J059 8.1.1.4


degradation when using the XML
Hierarchy Converter/ DocToHier
method to convert XML
messages with escaped
characters

In version 8.0.0.9, Inbound 12-1YFC9TW 12-1XRKKTV 8.1.1.4


requests to the EAI Object
Manager crash during EAI task
logout/cleanup

Crashes occur when processing 12-1YN3U39 12-1YIQP2P 8.1.1.4


large attachments (~115) using
EAI

466 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

The "UseFormattedValues" user 12-1YOKV2S 12-1QPSYL1 8.1.1.4


property for Integration Objects
with DTE causes unexpected
results

In version 8.1.1.1. when any 12-1XQ4SDJ 12-1WXWV2P 8.1.1.4


Inbound Web Service is used,
when the response is greater
than 51k, the charset-type is
removed from the content-type
HTTP header parameter

Other
When EAI Siebel Adapter is used 12-1ZOZ5CJ 12-1XBND23 8.1.1.4
with Query or QueryPage
methods, the SBL-DAT-60180
error message appears

There is no support for 12-1UI9FGG 12-1GCFOY0 8.1.1.4


homogeneous hierarchies in the
code generator

After 8.1.1 QF00AA has been 12-1XOOB5F 12-1XIVKJJ 8.1.1.4


applied, problems occur with the
cardinality of child products

ACR 480: Deduction Totals are 12-1ZZ4S3U 12-1V0596T 8.1.1.4


not updated when payments are
changed under a promotion

Consumer Sector
Handheld
Users are unable to print voided 12-1ZD5KI4 12-1Z3IMD9 8.1.1.4 Yes, see
invoices “Instructions for
FR 12-1ZD5KI4,
FR 12-
1YZMU0U, FR
12-1Z04AQ7,
and FR 12-
1Z04AS3” on
page 701.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 46 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

In the Consumer Sector 12-1N1QA5V 12-1JFQEZ6 8.1.1.4


Handheld application, with
certain records in "FS InvLoc
Product", the InstantiateProduct
method hangs

Provides the Void button 12-1YZMU0U 12-1YOMS98 8.1.1.4 Yes, see


functionality for version 8.x that “Instructions for
was available in version 7.7 of FR 12-1ZD5KI4,
the application (server) FR 12-
1YZMU0U, FR
12-1Z04AQ7,
and FR 12-
1Z04AS3” on
page 701.

Provides the Void button 12-1Z04AQ7 12-1YGT6Q9 8.1.1.4 Yes, see


functionality for version 8.x that “Instructions for
was available in version 7.7 of FR 12-1ZD5KI4,
the application FR 12-
1YZMU0U, FR
12-1Z04AQ7,
and FR 12-
1Z04AS3” on
page 701.

When users void an invoice that 12-1Z04AS3 12-1YOMS7P 8.1.1.4 Yes, see
was paid using a credit memo, “Instructions for
the amount of the credit memo FR 12-1ZD5KI4,
is not adjusted properly FR 12-
1YZMU0U, FR
12-1Z04AQ7,
and FR 12-
1Z04AS3” on
page 701.

Other
Trade Promotions Management 12-1ZVR7XG 12-1ZVR7O5 8.1.1.4
Quickstart (ACR 526)

Within the Target list applet, the 12-1T9SFNB 12-1TA9LJD 8.1.1.4


Copy ADL function sometimes
does not work properly

468 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

The following views are missing 12-1Q7K1G9 12-1P0S6GP 8.1.1.4


from Consumer Goods Base
options: Catalog Admin Detail
View – Products FINS Approval
Administration View

ACR480 : Improper error 12-1ZZ4SCG 12-1RVOKYD 8.1.1.4


messages display when users
try to submit funds to
themselves for approval

Improves the quality of the error 12-1ZZ4SDS 12-1UH86P4 8.1.1.4


messages for the CHS version of
the application

Improves the quality of the error 12-1ZZ4SF4 12-1UWOE37 8.1.1.4


messages for the CHS version of
the application

The Volume Planning Type 12-20BQPV1 12-20BQPTP 8.1.1.4


default value is not set for
promotions that do not have
plans associated to them.

The Warehouse WIthdrawal 12-205S6GS 12-204H02Q 8.1.1.4


Units and Forward Buy Units
values do not autospread from
the promotion level

UOM conversion does not 12-205S6GJ 12-204H021 8.1.1.4


happen for Forward Buy Cases/
Units and Warehouse withdrawal
cases/units

Retail Objectives
With Internet Explorer, when 12-1XF0XUJ 12-1XF0FX9 8.1.1.4
users drill down on an objective
target account and then click the
Back button, context is lost

Route Management

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 46 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

In the Routes screen, when 12-1YDWAOE 12-1K5IH9Q 8.1.1.4


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)

Sales Volume
Planning
Performing a Mass Change 12-1UFAJ7B 12-1U5SBU1 8.1.1.4
causes an infinite loop during
category aggregation

Executing the Mass Change 12-1YCFLBK 12-1XC7KQR 8.1.1.4


function on Category Baseline
records for a subcategory
causes the application to hang

Intra-allocation does not work 12-1YJPBKN 12-1YGUPJV 8.1.1.4


as expected and drops the
remainder value during
allocation

Query Assistant returns all 12-1YOMDX9 12-1BV2Y2P 8.1.1.4


records, regardless of the query
conditions

Trade Promotions
ACR 358: Accounts are visible in 12-1ZZ4S5N 12-1K2K8F5 8.1.1.4
the Funds screen even though
the Fund Eligible check box is
not selected

ACR 358: When users change 12-1ZZ4S6Z 12-1KC4OQB 8.1.1.4


the chargeback resolution status
to void, they receive an error
message that contains no
details

ACR 358: When users copy a 12-1ZZ4S8E 12-1KEJDM8 8.1.1.4


deduction that has a resolution
record associated with it, they
receive an error message

470 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

ACR480: The From and Amount 12-1ZZ4S9T 12-1RVOL2V 8.1.1.4


fields are still editible even after
a Funds Transfer has been
approved

When users attempt to create 12-1ZZ4SB8 12-1JUZ3ZD 8.1.1.4


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)

Customer Order
Management
Configurator
After users apply 8.1.1 QF00BQ, 12-1ZQWHRQ 12-1ZPH4ZU 8.1.1.4
they receive an error message
when they attempt the
BeginConfiguration step

ACR 502 provides the following 12-205G4TZ 12-1LNHQJJ 8.1.1.4 Yes, see
Siebel Configurator “Instructions for
enhancements: ACR 502” on
page 344.
■ 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.

An incorrect refresh occurs for 12-1X65SFB 12-1VM9GO3 8.1.1.4 Yes, see


user-added business component “Instructions for
fields within eCfg-UI in SI mode FR 12-1X65SFB”
on page 701.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 47 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

If RaiseErrorText is called within 12-1XS1NKP 12-1XO6UN9 8.1.1.4


an eCfg script like on
Cfg_InstInitialize, an error
message should appear in the
response of the calling
webservice

The ProductConfigurator 12-1XYUA5E 12-1XUY3ZF 8.1.1.4


BeginConfig Load web service
gets no response with two or
more grandchild products

The BeginConfiguration Web 12-1Y2PFJH 12-1Q7NVMV 8.1.1.4


Service should return
<Excluded>true</Excluded>
for component products that
violate product constraints and
eligibility rules

Within Product Configurator, the 12-1Y72XPE 12-1XQ4S1X 8.1.1.4


Summary tab does not display
products that break eligibility
rules

It is not possible to display an 12-1Y902IR 12-1XT16PO 8.1.1.4 Yes, see


attribute value's language “Instructions for
independent code (LIC value) in FR 12-1Y902IR”
the product configurator web on page 700.
service response message.

When a constraint that uses 12-1YK7CKM 12-1VR7NH8 8.1.1.4


"Constrain conditionally"
template fails, the explanation
does not contain the proper
information

CfgEval expressions that use 12-1YOJV1Z 12-1XWEWDL 8.1.1.4


"$Cur" in PickSpec UI Properties
do not work correctly for three-
level product hierarchies

The Product Configurator Load 12-1Z04TNB 12-1Y2PC95 8.1.1.4


operation web service response
has an empty <Item/> tag for
grandchild records

Attributes cannot be set using 12-1Z3ZZMT 12-1YZNDJB 8.1.1.4


the VBC applet

472 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

When users translate 12-1ZM3DNU 12-1Z6VRLF 8.1.1.4


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

Remote configurator is not 12-1ZZMA8H 12-1WYW4B2 8.1.1.4


working after patch upgrade

ACR502 :Summary theme is not 12-1ZZMA9H 12-1VNIMC9 8.1.1.4


coming with products with Quick
edit theme with Tabproduct
theme

ACR502:Explain button is not 12-1ZZMAAJ 12-1VNJNK9 8.1.1.4


throwing any error for
cardinality violation

eSales
When users select filtered 12-1Z6EUT7 12-1Z4YJPX 8.1.1.4
products and click OK, the
application crashes

Order Management
Product Promotion does not 12-1XJD2O9 12-1XIVLVL 8.1.1.4
maintain defaults for products
from parent classes

After QF0E16 has been installed, 12-1ZA4LHW 12-1YM4QX1 8.1.1.4


users receive an error message
when validating products

Querying in the Promotion 12-20OTD3P 12-206F3XH 8.1.1.4


popup applet does not work

There is no filtering capability in 12-1TK90K2 12-1SEPT2B 8.1.1.4 Yes, see


the Bulk Order Action “Instructions for
component pick applet FR 12-1TK90K2”
on page 699.

Inefficient SQL select 12-1U3KD9O 12-1T2IWYD 8.1.1.4


statements are created during
ApplyPromotion

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 47 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

When users modify assets, they 12-1VM8C3T 12-1VM7S6L 8.1.1.4


recieve the SBL-BPR-00183,
SBL-BPR-00162, and SBL-ISS-
00121 error messages

Bulk Requests that include the 12-1VR61KE 12-1VR26EP 8.1.1.4


Replace action cause orders to
be generated with incorrect
action codes

UMS UI applet does not refresh/ 12-1X1B3C6 12-1WUJE2X 8.1.1.4


display all buttons

The Suspend and Resume 12-1XJDJYH 12-1X5627A 8.1.1.4 Yes, see


workflows add unwanted line “Instructions for
items FR 12-1XJDJYH”
on page 699.

Promotion Upgrade does not 12-1Y4N1FU 12-1XTBN8V 8.1.1.4


work as expected with ACR 471

Users receive an error message 12-1YCFL9K 12-1Y0AHAJ 8.1.1.4


when migrating promotions

With Bulk Orders, selected 12-1YCXTST 12-1Y3OY73 8.1.1.4


records are not copied or
displayed on the Instances
applet

The AutoMatch function 12-1YDWCXG 12-1Y63UOX 8.1.1.4


incorrectly adds products to
orders

QF00AW on 8.1.1 has changed 12-1YQ4NCA 12-1YKOYUX 8.1.1.4


response for web service
AssetManagementComplex
QF00BK Un Installation on WIN
is not reverting back the dll Time
Stamp.

When promotions are imported 12-1Z3152J 12-1YFU2BX 8.1.1.4


twice, the same price
adjustment is created twice for
subcomponents with the same
data

The SQL Delete of an Attribute 12-1Z7DBBN 12-1YOKG0B 8.1.1.4


from a Class is not removing all
support records from the entity
relationships diagram.

474 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Promotions Export/Import does 12-1ZD654T 12-1YQ37K5 8.1.1.4


not work for Pricing Adjustments
at the Component Level

Remote configurator is not 12-1ZY61K5 12-1XBNFD5 8.1.1.4


working after patch upgrade

Orders
ACR 499 provides the following 12-1ZUS8XP 12-1ZUS8W7 8.1.1.4 Yes, see
enhancements to the Bulk “Instructions for
Orders functionality: ACR 499” on
page 291.
■ 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.

Products
When users edit product 12-1YJ7WX1 12-1YDFAIF 8.1.1.4
component relationships, they
receive an error message

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 47 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

When products are released for 12-1X3PGV5 12-1X1SG5R 8.1.1.4


two concurrently logged-in
users, the SBL-ISS-00121 error
message occurs

Data Quality
Cleansing
Service requests, activities, and 12-1UHQ1L9 12-1U5RB3V 8.1.1.4 Yes, see
statements are not moved from “Instructions for
a merged member to a surviving FR 12-
member during member merge 1UHQ1L9” on
page 698.

Address cleansing returns 12-1ZFCRF7 12-1YOLRSL 8.1.1.4


addresses in single parameters
rather than in multiple
parameters

Deduplication
ACR 475: Incorrect match 12-1VNJME1 12-1VNJC3T 8.1.1.4
results occur for accounts and
contacts when EAI is used

ACR 475: The batch task does 12-1VR6B4G 12-1VR2BBP 8.1.1.4


not end when accounts with
multiple addresses are inserted
using the BDM workflow

ACR 475: Incorrect matches 12-1VR6B74 12-1VR3SGC 8.1.1.4


occur when an address is
removed from one country and
another country is added

ACR 475: Changing the primary 12-1VR6B9Q 12-1VR4QK5 8.1.1.4


address to a different country
does not create the record in the
new population

ACR475: Changing the primary 12-1VR6BB1 12-1VR4QM7 8.1.1.4


contact for an account causes an
error message to appear

476 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

When users run the Batch Data 12-20GLHEH 12-1ZZMR15 8.1.1.4


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

Other
ACR 475, QF3101: IIR crashes 12-1VR228F 12-1VNJDR2 8.1.1.4
when posting contacts through
EAI

Provides a parameter to turn off 12-1VM7P1D 12-1VH3RP7 8.1.1.4


the UCM Data Quality workflows
for ACR 437

QF3103: The synchronizer 12-1ZE4T14 12-1ZE4SZN 8.1.1.4


architecture does not support
the MSSQL and DB2 UDB
databases

QF3104: When Data Decay 12-1ZD61KI 12-1Z6ER6J 8.1.1.4


runtime events are on,
associating contacts with
accounts causes an error
message

General
Activities
Employee MVG applet data is 12-1Y9ZLKQ 12-1XHFA1T 8.1.1.4
erased when changing the
primary employee

When an Activity is deleted, 12-1YAYCT1 12-1YAH4YV 8.1.1.4


under Activity Templates, the
Action business component does
not refresh

Cost and Price are not converted 12-1XLROYV 12-1IKIU3B 8.1.1.4


on tracker level when the
activity comes from an activity
plan

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 47 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Application
Deployment Manager
Field 'XliffFileAutoUpdflg' 12-1YOKK0R 12-1YOKGBZ 8.1.1.4
missing when migrating BIP
Report Template Registration
ADM Data Type

Assignment Manager
Multi-Tier Assignment 12-1NTJ04W 12-1M4UP57 8.1.1.4
functionality is missing in Siebel
version 7.8 applications

Audit Trail
The Audit Trail does not capture 12-1Y9Z1NN 12-1XSJG29 8.1.1.4
cascade deletes on the HLS Case
business component

Within the Detail view, the 12-1YOK7PR 12-1YKOK4N 8.1.1.4


associate information for the
object being audited is missing

Business Rules
When calling Haley Expert Rules 12-1Y9HL5B 12-1XZBSUD 8.1.1.4
knowledge bases, a runtime
error (top-level business
component not configured)
occurs

Calendar
Daylight Savings Time (DST) 12-1N1KSBQ 12-1MAMEI5 8.1.1.4
changes do not occur for
repeating appointments

Double-border appears around 12-1ZM2UY9 12-1YTS6AX 8.1.1.4


meetings on 5-day calendar
screen

Events (eEvents) appear in 12-1NUHDPR 12-1NKJK2V 8.1.1.4


backwards chronological order
on the monthly event calendar
when events cross multiple days

Within the Participant 12-1PSNEO1 12-1MFY3XO 8.1.1.4


Availability form applet, the Go
button is not translated

478 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

When creating or editing a 12-1YKOARK 12-1Y3OYE1 8.1.1.4


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

The Monthly calendar does not 12-1Z4YXGN 12-1YQ37AZ 8.1.1.4


respect the First Day of the
Week user property

Correspondence
When generating a 12-1OK0VKH 12-1OD185U 8.1.1.4
correspondence document, the
SIEBEL.HTML document
contains non-standard spaces
that appear incorrect in the
generated correspondence
document

CRM Desktop
The LOV is missing for the Lotus 12-1WTKAOZ 12-1WTKAOF 8.1.1.4
meta data file the
"ln_package_res.xml" file

Improves the quality of error 12-1Y28CO5 12-1WLULD1 8.1.1.4


messages

File System
Large attachments fail to open 12-1XJDI01 12-1WEU3RJ 8.1.1.4
on Linux with multiple
filesystems

Modified dates of attachments 12-1YAGYUB 12-1DRKC6T 8.1.1.4


are updated even if the applet
runtime property is equal to
True in WinXP FAT

Global/Multilingual
LOV
Strings for icons in Russian 12-1YOMKFA 12-1YOLRNV 8.1.1.4
(RUS) are missing in 8.1.1

Installation

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 47 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

The dmutl2.exe file cannot be 12-1YUTSZZ 12-1YUTSZ6 8.1.1.4


accessed

Siebel Tools Online Help files 12-1ZV9SEZ 12-1Q35A8A 8.1.1.4


were not updated for Siebel
8.1.1

Other
Passing arguments by reference 12-1VEOXOD 12-1U4I7J7 8.1.1.4
from within a with block in
escript in the new ST engine
gives incorrect results

In version 8.0.0.9, there was a 12-1XUY70M 12-1XP5AGR 8.1.1.4


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

When instantiating an excel 12-1YFTLB8 12-1XWIYRL 8.1.1.4


applicaiton using
COMCreateObject in escript with
the ST engine turned on, the
process does not quit even
though the method
Application.Quit is called

The escript method 12-1YN3WIP 12-1XRKKWD 8.1.1.4


Date.fromSystem() returns the
incorrect time in Linux

Business service escript is 12-1YOOQQR 12-1YAH50J 8.1.1.4


allowing the custom method to
fall through to C++ code
producing an error.

The Thin Client cannot retrieve 12-1YUWFO2 12-1YOLLSB 8.1.1.4


the entire string contained in a
profile attribute

Calling server script from 12-1Z30P3H 12-1Z1KQM1 8.1.1.4


browser script in a single
business service causes an error

Creating a new buffer where the 12-1ZFBL3U 12-1YNLBB5 8.1.1.4


input is > 90K causes the
application to hang

480 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Business service invocation in 12-1ZJG9IJ 12-1Z3IMBL 8.1.1.4


the Application_Start event
using the old escript engine (the
T engine) causes an error

View Tabs ignore dynamic rules 12-1N1Q7FN 12-1GRZD9P 8.1.1.4

Error messages are not thrown 12-1QJ1VFB 12-1QJ1VZN 8.1.1.4


in eaisiebel.js in the
EAIExecuteMap()

Script in the 12-1VR236Y 12-1V059J1 8.1.1.4


WebApplet_PreCanInvokeMetho
d event can cause memory use
to increase

When an error message is 12-1XOOB8H 12-1XIVYP9 8.1.1.4


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

WebApplet_Load event causes 12-1ZO0KN8 12-1Y3OXW9 8.1.1.4


WriteRecord to occur after it
completes

Values that follow an ampersand 12-1YOOQSY 12-1BDKMON 8.1.1.4


(&) in a URL argument value are
truncated

PIM Server
Integration
The PIMSI Engine crashes when 12-1XTI77K 12-1TK463D 8.1.1.4
trying to sync more than 100
users

The "MultipleEntry" feature does 12-1V7F7Y9 12-1TGNL4T 8.1.1.4


not work as expected

Users are unable to sync 12-1X8ID6D 12-1VMABYH 8.1.1.4


appointments that were created
by non-Exchange users

The user extract start date 12-1XPNABN 12-1VNJMW6 8.1.1.4


feature does not work properly

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 48 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Outbound appointments are not 12-1XOOA50 12-1VR2GS3 8.1.1.4


retried after a failure

The Outlook Add-in does not 12-1TYSGWK 12-1TYAXPJ 8.1.1.4


respect the PIMSI Domain
"Category" setting

Warnings are incorrectly called 12-1VM60MM 12-1VM60LR 8.1.1.4


errors in the PIMSI Engine log

Remote
Database initialization still fails 12-1YR2YPR 12-1SM2JSV 8.1.1.4
after QF06AH has been installed

Internet Explorer cannot display 12-1Q2N41G 12-1PWMKKV 8.1.1.4


web page errors on Vista

Quick start does not work for 12-1VKZHLM 12-1VKZHKI 8.1.1.4


non-administrator users on XP
and Vista

Frequent dbxtract, dbinit and 12-1VM6ZSU 12-1QVMO57 8.1.1.4


synchronization leads to
TxnMerger failing on HOR

ACR 402: Users are unable to 12-1VMAK2L 12-1QFPANA 8.1.1.4


log into the Mobile Web Client
they have rebooted with Quick
Start enabled

Ports QuickStart applications 12-1YOK7QV 12-1X5R8TQ 8.1.1.4 Yes, see


“Instructions for
FR 12-
1YOK7QV” on
page 698.

On Vista, with Quick Start 12-1YOK7S3 12-1NZ7889 8.1.1.4


enabled, users are unable to log
into the Mobile Web Client after
they restart a machine

With Quick Start enabled, when 12-1YOK7TT 12-1VKYX0H 8.1.1.4


the File > Sync DB option is used
after rebooting, the Sync Dialog
box is not visible

The Quick Start function does 12-1YOK7UR 12-1JNDF6J 8.1.1.4


not work on Microsoft Vista

482 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

During Mobile Web Client 12-1WF6Q84 12-1VDPBPF 8.1.1.4


synchronization, the SBL-DAT-
00369: Error with the connector
DLL '<?>' has occurred
_SSACreateSqlObj@12 error
message occurs

Reports Server
Errors occur when running 12-1VNKJIP 12-1V418JR 8.1.1.4
reports in SI applications (such
as eService, eCustomer)

BI Publisher reports show 12-1YK7EER 12-1XIVLOD 8.1.1.4


incorrect output when executing
a PDQ and refining the query

BI Publisher report Output type 12-1V4JIO9 12-1S1Y205 8.1.1.4


not visible due to Read Only
View settings

Executing a BI Publisher report 12-1VR3YGT 12-1VNJ7BV 8.1.1.4


in Split Calendar View does not
display any data.

Reports do not work correctly in 12-1YCG5VU 12-1YCG2PL 8.1.1.4


disconnected mode

Siebel Reports Scheduling does 12-1YFC2CA 12-1XLALJV 8.1.1.4


not work when the locale date is
changed

BI Publisher reports with 12-1YZN89Z 12-1XF0GC9 8.1.1.4 Yes, see


signature display (LS_RECIPT & “Instructions for
LS_SIGNAD) do not display FR 12-
signatures correctly on the 1YZN89Z” on
mobile client. page 697.

Error when executing BI 12-1XLRL99 12-1VM6MO5 8.1.1.4


Publisher report with Oracle
database
NLS_CHARACTERSET=JA16SJIS

Search
Certifies Oracle Secure 12-20CQ1B0 12-20CQ19Q 8.1.1.4
Enterprise Search (SES) on the
Oracle 11g platform

Security

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 48 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Using AES 256 encryption on 12-1N22I4I 12-1J1ZOUE 8.1.1.4


7.8.2.5 SIA causes the Object
Manager to crash

Using email addresses to 12-1U0CXTI 12-1TK4UBL 8.1.1.4


register new ADSI users will
sometimes fail

Name fields allow scripts to be 12-1YAGOEH 12-1WUJGPN 8.1.1.4


executed, which permits
possible XSS attacks

The Active Directory "Force 12-1YOMH3G 12-1YNKWFD 8.1.1.4


password change at next login"
feature yields an error message

Server Infrastructure
It is necessary to recompile the 12-1Y63UTG 12-1U5UGI1 8.1.1.4
SRF to execute scripts for
debugging environment

SmartScript
After 8.1.1.2 has been installed, 12-1XB5ZLZ 12-1X65YA7 8.1.1.4
SmartScript buttons do not
allow keyboard clicks

Importing SmartScripts in 12-1YDEPAU 12-1Y8J0H7 8.1.1.4


update mode adds records
instead of updating existing
records

System Operation &


Diagnostics
When a cached business service 12-1VASVI5 12-1UX6FPL 8.1.1.4
is called by another business
service through script, the
instance is not correctly
reclaimed and upon logout, a
runtime error may occur

With the standard SRF, the 12-1XRKLEH 12-1XRKLDV 8.1.1.4


ePharma ENU application
crashes when Siebel 8.1.1.2 is
installed

The Object Manager crashes in 12-1XUYPKV 12-1XOOC8J 8.1.1.4


version 8.1.1

484 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

After the AES 256 Encryptor has 12-1XVXX9N 12-1XP5AVL 8.1.1.4


been enabled, the Siebel Object
Manager crashes

Custom joins to s_audit_item 12-1U5VBII 12-1U0C8KF 8.1.1.4


cause the SBL-DBC-00105 error
message to appear

"Last Updated Source" and "Last 12-1VUZHOZ 12-1VUZHM8 8.1.1.4


Updated On" are not populated
in the UI in the About Record
window

New servers can not be added to 12-1Y36YRO 12-1Y0AZPB 8.1.1.4


the enterprise.

When users log into an Object 12-1YIQJZD 12-1NWCZMB 8.1.1.4


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

SCBroker crash in 8.1.1.1 on 12-1YOLTT3 12-1XTIRJJ 8.1.1.4


RHL 5.2

Task UI
When a transient business 12-1X46YC9 12-1V9U49H 8.1.1.4
component is accessed across
two different TBUI views, the
application may not function
properly

When multiple languages are 12-1X3PH49 12-1X3PPT4 8.1.1.4


used in TBUI Tasks, even though
the language of Task Name can
be overriden, this does not work
with symbolic strings

Chapter names are not 12-1X3PH4Y 12-1X3PQB1 8.1.1.4


displaying in the user interface
for a task

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 48 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

When users step through 12-1ZFBL2R 12-1VJZTJ7 8.1.1.4


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

Tools/Configuration
Siebel Tools sometimes hangs 12-1SLL0QL 12-1PEQLIL 8.1.1.4
when applying schema changes
(such as a new extension
column)

Functions require an extra 12-1XS1M33 12-1MSV4EV 8.1.1.4


leading { in front of the function
body to behave properly

After 8.0.0.2 QF0220 has been 12-1XUY6Y9 12-1RSS5TX 8.1.1.4


applied, the Web_Applet_Load
events are fired twice each time
the user navigates to a view

Checkboxes in the first column 12-1Y63IC7 12-1Y3OY5F 8.1.1.4


of list applets do not work
correctly

After 8.0.0.2 QF0220 has been 12-1ZIM652 12-1UIA11Z 8.1.1.4


applied, the Web_Applet_Load
events are fired twice each time
the user navigates to a view

The Opportunity Form URL 12-1N1KLVX 12-1KBLS9L 8.1.1.4


Display Applet displays correctly
when it is placed in a view, but
when it exists as a toggle applet,
the system crashes

Dynamic Applet Toggle moves 12-1WVI20Z 12-1VR32TN 8.1.1.4


focus to the bottom applet
instead of the parent applet
after toggle

Upgrade

486 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

The repository is not in sync 12-1YVVM4G 12-1W6DOUA 8.1.1.4


with physical implementation
after an upgrade to a new
database version with LONG
support

There is no Database 12-1Y3EOKX 12-1Y37CQ3 8.1.1.4


Configuration Wizard support for
the z/Os database in version
8.1.1.3

After users upgrade, revenue 12-1YCFLEM 12-1Y3OXVF 8.1.1.4


history data is missing

Workflow
Workflow policies triggered on 12-1R1VXOW 12-1QBCC09 8.1.1.4
extension tables do not fire
actions

Calling asynchronous workflow 12-1Y54SUX 12-1XTIR2L 8.1.1.4


processes from scripts causes
runtime errors when logging out
of the application

Life Sciences
Clinical Account
Profiles
Within Administration - Clinical 12-1ZYN9IP 12-1TK3LHO 8.1.1.4 Yes, see
(Administração - Clínica) > “Instructions for
Protocol List (Lista de FR 12-1ZYN9IP”
protocolos), the title of Cargo is on page 696.
not correct.

Clinical Profiles
Within the Clinical Protocol 12-1ZUS8M9 12-1VM8M3T 8.1.1.4 Yes, see
Regions View, when users click “1Instructions
on subtabs (such as for FR 12-
Attachments or Contacts), the 1ZUS8M9” on
application refreshes and page 696.
displays a different Protocol
Number value than the one that
the users selected

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 48 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Subject Visit Templates does not 12-1VM6ZU4 12-1T2ILPP 8.1.1.4


keep the Required flag set for
activities

PTCL Region & Site become 12-1YFU2M8 12-1YFU2LN 8.1.1.4


invisible if the position that is
removed from the protocol is the
primary at the region or site of
that protocol

List Management
Within Events > Resources > 12-1Y902JY 12-1WF6IYP 8.1.1.4
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

Other
Converts the Site Initiation By 12-1P4ORNG 12-1OQUM19 8.1.1.4 Yes, see
Site Actuate report (LS_INBSIT) “Instructions for
to BI Publisher FR 12-
1P4ORNG” on
page 695.

BIP report - Telephone and Fax 12-1YJ7X13 12-1QCS8LG 8.1.1.4 Yes, see
Numbers are not displayed in “Instructions for
the expected format FR 12-1YJ7X13”
on page 695.

Payments
The Payments Exception Query 12-1YFTGBH 12-1Y0B1UK 8.1.1.4 Yes, see
button does not work properly “Instructions for
FR 12-
1YFTGBH” on
page 694.

Protocol Builder
BIP: Pharma Site Enrollment 12-1P4ORM0 12-1OQUM7F 8.1.1.4 Yes, see
Status By Protocol - “Instructions for
LS_SITENRL FR 12-
1P4ORM0” on
page 694.

488 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Converts the Site Initiation By 12-1P4ORMD 12-1OQUM5W 8.1.1.4 Yes, see


Protocol Actuate report “Instructions for
(LS_INBPRO) to BI Publisher FR 12-
1P4ORMD” on
page 692.

Converts the LS Site Initiation 12-1P4ORMQ 12-1OQUM4D 8.1.1.4 Yes, see


By Region Actuate report “Instructions for
(LS_INBREG) to BI Publisher FR 12-
1P4ORMQ” on
page 691.

Converts the LS Region 12-1P4ORN3 12-1OQUM2S 8.1.1.4 Yes, see


Document Tracking Actuate “Instructions for
report (LS_TRBREG) to BI FR 12-
Publisher 1P4ORN3” on
page 691.

BI Publisher reports are 12-1P4ORNT 12-1OQULZQ 8.1.1.4 Yes, see


unavailable for the LS Protocol “Instructions for
Document Tracking Actuate FR 12-
report (LS_TRBPRO) to BI 1P4ORNT” on
Publisher. page 690.

Non-applicable visits do not get 12-1UI92I9 12-1TK4CFP 8.1.1.4


deleted when the SVT version is
changed

Position Rolldown shows the 12-1Z5203P 12-1R7MY7D 8.1.1.4


error message: Error SBL-BPR-
00162 fo 'EAI Siebel Adapter'.

Loyalty
Loyalty Customer
Portal
When transactions are moved 12-1Z3ZZO2 12-1TLCZVH 8.1.1.4 Yes, see
between members, accrual “Instructions for
records are not moved FR 12-
1Z3ZZO2” on
page 689.

Loyalty Engine
The LoyaltyEngineInteractive 12-1WB4GPH 12-1VI06M8 8.1.1.4
Object Manager has a memory
leak of around 88 KB

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 48 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

The LoyaltyEngineRealtime 12-1WB4GPV 12-1VI06I9 8.1.1.4


Object Manager has a memory
leak of around 240KB

The Loyalty Interactive Engine 12-1XKTALR 12-1XLAL2N 8.1.1.4


crashes while processing
redemption transactions

During transaction processing, 12-1YFC6E8 12-1SW8L6P 8.1.1.4


the number of open SQL cursors
starts increasing rapidly and
reaches the maximum number
possible

When point block optimization is 12-1YKOEPX 12-1SK5J9J 8.1.1.4


used, the Batch Engine fails
while being shut down

Slow SQL occurs during the 12-1VGM3O1 12-1VGM3N7 8.1.1.4


Real-Time Loyalty Accrual
scenario

Redemption Cancellation task- 12-1Y90J9T 12-1Y6LBZN 8.1.1.4


based UI performance is slow

Enhancement to accrual 12-1YDWAPR 12-1XF0FUR 8.1.1.4


webservice

Loyalty Manager
When users query within the 12-1XM93ST 12-1XHDRIJ 8.1.1.4 Yes, see
Points Balance view, rows “Instructions for
appear that should not be FR 12-
displayed 1XM93ST” on
page 689.

The LOY Member Service Issue 12-1VM75R7 12-1VM6N5D 8.1.1.4


> Override pay flag does not
allow the Business Service to
continue without the credit card
details being in the service

The Reissue Voucher task-based 12-1XS21JF 12-1XHF9F1 8.1.1.4 Yes, see


UI takes too long to process “Instructions for
transactions FR 12-1XS21JF”
on page 689.

490 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

The LOY Batch Enrollment 12-1YJPCOB 12-1YIQQID 8.1.1.4


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

After two members are merged, 12-1YKOEQV 12-1TUEX22 8.1.1.4 Yes, see
the survivor member cannot “Instructions for
redeem points from the merged FR 12-
member points 1YKOEQV” on
page 688.

Marketing
Campaigns
Campaign repeating tasks may 12-1TKAALE 12-1THO6QN 8.1.1.4
repeat unexpectedly if record
contention occurs

The system allows users to 12-1U5U3TC 12-1TDX5HX 8.1.1.4


associate a promoted prospect
to a new list

Campaign launch fails when 12-1VKZCM4 12-1V4JH1X 8.1.1.4


using an internal list with no
prospects

Queries on My Leads and My 12-1W7RMKA 12-1VMCEBF 8.1.1.4


Team's Leads views return all
leads

In the Campaign Members view, 12-1XEJEWF 12-G9NBE5 8.1.1.4


when users select a prospect
and click the Create Opportunity
button, they receive an error
message

When users chose segments, 12-1XVXFA2 12-1XIVMBZ 8.1.1.4


the user folder offered is always
the administrator's rather than
the user's

User cannot see segments or 12-1YSNB9N 12-1Y9HK6T 8.1.1.4


lists that were created by other
users in the same group

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 49 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

On UNIX-based platforms, one 12-1QNF4T7 12-1PZ4R7R 8.1.1.4


contact gets missed during 1st
campaign wave assignment

Offer Treatments are not copied 12-1S0YVDC 12-1KTY061 8.1.1.4


with Campaign Template is
applied

When contacts are manually 12-1T03JW2 12-1S5BL5P 8.1.1.4


added, Campaign Launch
functionality defaults to a null
wave number

Email and Web


Marketing
Certifies Ektron version 5.2 12-1ZB8X4V 12-1YKOJKX 8.1.1.4

When multiple lists are used, the 12-1XHX8U6 12-1WF6ZG1 8.1.1.4


wrong emails are sent to
contacts

Trackable URLs are not created 12-1YR9X61 12-1WLUTXP 8.1.1.4


correctly if the links include <br.
(Solaris-specific issue)

Many temporary files are 12-1YNLA4P 12-1O75I6F 8.1.1.4


created in the siebsrvr/TEMP
directory when editing mail
templates

Events
An error occurs if two users try 12-1XQ4DQQ 12-1X1RY8J 8.1.1.4
to confirm an event attendee
concurrently

Waitlist count is incremented 12-1YIQBXE 12-1XZBYDT 8.1.1.4


when the Allow Waitlist flag is
set to N

Users receive an error message 12-1US5UG8 12-1S8Q8RN 8.1.1.4


when they click quickly on the
Invite on Event Registration list

Add to List button on Contact 12-1UZ5SCZ 12-1UI8TSH 8.1.1.4


Category view adds empty
record to list

492 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Waitlist count does not decrease 12-1VR235E 12-1VH3S01 8.1.1.4


when the participants who are
waitlisted are cancelled

Within eEvents version 8.1.1.1, 12-1Y36UO3 12-1XC4GYV 8.1.1.4


creating a session takes longer
than in previous versions of the
application

Changes to the Event Plan 12-1URKHKE 12-1UGQKG7 8.1.1.4


Status field automatically
update the event status field

Marketing Server
Campaign load will reject some 12-1UW60OB 12-1UH8JVF 8.1.1.4
rows as errors if the same
contact is targeted with more
than one treatment

The Campaign Load/Campaign 12-1X5R8D6 12-1VMC65K 8.1.1.4


Launch process exits if
Segmentation Engine does not
respond

Other
RTD 3.0: Within the Realtime 12-1YOMJX3 12-1YOMJWJ 8.1.1.4
Details view, the Sync button,
Last Sync Date field, and the
Need To Sync field should be
disabled

RTD 3.0: The Campaign field 12-1YOMN8C 12-1YOMN72 8.1.1.4


should be required for all RTD
offers

RTD 3.0: Stage information 12-1YOMN6R 12-1YOMN57 8.1.1.4


should only include enabled
offers in the eligible offers group

RTD 3.0: Within the Retention 12-1YQGG5W 12-1YQGG4M 8.1.1.4


Action view, the Offer Response
buttons should not be enabled

RTD 3.0: Within Call Center, the 12-1YQGG94 12-1YQGG7U 8.1.1.4


Offer Details view is not
consistent with the display of
attributes

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 49 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

RTD 3.0: The Reason field is not 12-1YQGGAZ 12-1YQGG9F 8.1.1.4


displayed in the Responses
screen

RTD 3.0: For intelligent offers, "12-1YQGGEF 12-1YQGGD5 8.1.1.4


the Reason field should not
record responses with "tell me
more

Positions added to the Lead 12-1YOWCFE 12-1XF0G9H 8.1.1.4


Sales Team MVG are also added
to the last saved Lead record

In Siebel 8.1.1, the My Leads 12-1ZB8X0J 12-1XC7L43 8.1.1.4


view returns an EOF error
message when the owner of a
record is changed

With RTD 3.0, after users import 12-1ZG57E3 12-1ZHAMQF 8.1.1.4


SIF files and compile them, the
Contact screen does not display

Within the Response screen, 12-1ZOZ4CB 12-1ZOZ4A7 8.1.1.4


when users click the Campaign
hyperlink, they receive an error
message

Within the Retention Action 12-1YQZ29F 12-1YQZ267 8.1.1.4


view, when users click the No
Thank You button, the
application displays a Reason
dialog box .

RTD 3.0: Within Decision Center, 12-1YQGGG0 12-1YQGGEQ 8.1.1.4


Offers should be listed as Offers
Name

Within the List Import tab, 12-1Z04TPQ 12-1Y54UZR 8.1.1.4


importing a large file creates
garbage characters

494 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

When users click the Reject Lead 12-1Z30OQR 12-1WTJXWZ 8.1.1.4


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.

Modifying a lead record 12-1Z30OS2 12-1XOOC39 8.1.1.4


overwrites the Lead Rejected
Time value

Within List Management > Lists, 12-1ZYN2ZW 12-1YCFMMF 8.1.1.4


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.

Response forms that are added 12-1XHWSY8 12-1XHWSXH 8.1.1.4


to the treatment template in
default task-based UI tasks are
not converted to HTMLwhen
they are sent

Programs
Marketing Object Manager may 12-1VR268K 12-1VM5KMF 8.1.1.4
fail when two users delete a
campaign list at the same time

Mobile Solutions
Handheld for Windows

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 49 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

When the Order Signature 12-1ZFE3KR 12-1YZND55 8.1.1.4 Yes, see


Capture applet class is “Instructions for
CSSFrameFSSign, when users FR 12-1ZFE3KR”
create a new signature and click on page 687.
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)'.

Handheld: GetCount TAG from 12-1Z6W895 12-1YOK96H 8.1.1.4


print tagging language delivers
wrong value

Handheld: GetTotal TAG from 12-1Z6W8AC 12-1YOKK66 8.1.1.4


print tagging language delivers
wrong value

When users navigate in the 12-1ZFBR93 12-1YOKK4N 8.1.1.4


Billings screen and use the
Signature function, the device
freezes

The Screen drop-down list does 12-1ZFBLOZ 12-1Z6VW9H 8.1.1.4


not appear on the Samsung
Saga device

Handheld synchronization loops 12-1ZL9LBT 12-1YOKGG5 8.1.1.4


if the compressed siebel.rml.z
file on the server is bigger than
250000 bytes (244KB)

Other
The Mobile Web Client crashes 12-1Y289R5 12-1K501OP 8.1.1.4
when script is added to the
Docking Service Business
Service

Wireless
Integration of Mobile Sales 12-1TXT8U0 12-1RCXQ1N 8.1.1.4 Yes, see
Assistant to the Siebel On- “Instructions for
Premise application (ACR 626) ACR 626” on
page 438.

496 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Partner
Relationship
Management
Other
If the PRM ANI Utility Service of 12-1X0BIRS 12-1QTP7PD 8.1.1.4
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

Public Sector
Other
Customers can not access 12-1ZW8OVR 12-1ZW8OV7 8.1.1.4
Incidents-related views because
of a license-key issue

Sales
Forecasting
Senior levels in forecasting 12-1XVG7QX 12-1XM98B7 8.1.1.4
hierarchy not able to generate
forecasts

After users delete a forecast and 12-1YN3TX3 12-1YCXQYB 8.1.1.4


then drill down on another
forecast, they receive the SBL-
DAT-00393 "end of file" error
message

Other
The Relationship Hierarchy view 12-1YOMKPD 12-1T2ILHX 8.1.1.4
allows access to all accounts
across all organizations

The Next arrow for the "Bill To" 12-1ZL9LEQ 12-1YNLB8N 8.1.1.4
Relationship Hierarchy Tree
Applet does not work

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 49 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Territory Management
Geo-Zone-based rules for 12-1U3BTSP 12-1U0C8HX 8.1.1.4 Yes
accounts do not give expected
results

Service
Other
If a manager has more than one 12-1PQPP5B 12-1PFQSZV 8.1.1.4
expense report to be approved,
when the manager clicks the
approve button for a expense
report gets approved 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. Please
continue or ask your system
administrator to check your
application configuration if the
problem persists. (SBL-DAT'-
00393)".

The Activity Plan Copy 12-1Y37FF1 12-1XZYBNJ 8.1.1.4


functionality does not work
properly after case insensitivity
has been implemented

Preventive
Maintenance
The Preventive Maintenance 12-1QR9B1Y 12-1Q0IVOB 8.1.1.4
Engine does not release the
database open cursors, which
creates a memory leak

Scheduling
GanttChart AX Applet does not 12-1RAJ8PX 12-1Q0IVS7 8.1.1.4
work in multilingual
environments

498 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Holiday API Service - 12-1V6GM1C 12-1UIBDO9 8.1.1.4


IsHoliday() is not working
properly when Exceptions are
used in the Schedule

SR broker tasks increase when 12-1Z7DAAJ 12-1YOLS7V 8.1.1.4


invoking booking appointments
that integrate with Asgnsrvr

Updating an activity does not 12-1ZFB9X9 12-1YOKGHT 8.1.1.4


generate an update in the FS
Activity Cache Sync business
component

Within the Dispatch Board, the 12-1ZFBA2F 12-1YJP6FL 8.1.1.4


Refresh command switches off
the cache

Siebel E-
commerce for
Comms
Miscellaneous
Child products under a default 12-1YBWJSS 12-1VCQTQ1 8.1.1.4
CP in an upgraded promotion
are not shown in the Summary
of Changes page

Within sales order, the request 12-1ZOI4IM 12-1ZOI4H7 8.1.1.4


dates for line items are being
saved as the request date minus
one

Siebel Self
Service Common
Miscellaneous
Users are unable to launch the 12-1Z3HSYD 12-1YOJTGX 8.1.1.4
Self-Service URL

With different ship-to 12-1YBWKB5 12-1V3JPQB 8.1.1.4


information for line items, the
MultipleShipto column shows
"No' in the Review and Submit
page

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 49 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Universal
Customer Master
Data Management
QF3104: When users unmerge 12-1ZQWVG8 12-1Z7DQZ9 8.1.1.4
contacts from accounts, the
association is not retrieved

QF3103: The Initial Load 12-1YNL8YQ 12-1Y9HZTV 8.1.1.4


process is not available for
MSSQL DB Type

ACR 475: When multi-lang is 12-1ZYNASE 12-1ZNIRZH 8.1.1.4


enabled, when users associate a
contact to an account through
the UI, an error message occurs

QF3103: The Initial Load 12-1YNL8XJ 12-1Y9HZWG 8.1.1.4


process is not available for IBM
DB2 UDB Type

EAI
ACR 437: With EAI, when 12-1VM871M 12-1VH3RYD 8.1.1.4
IsPrimaryMVG is set to Y,
records are not updated as
primary

Integration
The 'UCM Batch Manager' 12-1U0AQT7 12-1IBE8WR 8.1.1.4
Business Service
'ExecutePropSets' method
crashes when querying for an
account produces 0 rows

AIA responses back to the Siebel 12-1Z7UTPT 12-1Z6VRAB 8.1.1.4


application return the entire
XML to the Siebel UI

Other
ACR 475: When trying to select 12-205XKI9 12-205XKGR 8.1.1.4
a DnB Account to export to DRM
from UCM, an error message
occurs

500 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

ACR 475, Higher Education: The 12-1U5RGGN 12-1TJMH71 8.1.1.4


EIM tables are missing some
data

ACR 475, Higher Education: 12-1U5RGIV 12-1TK3VIM 8.1.1.4


There is no text box for the Date
of Birth field

ACR 475, Higher Education: 12-1U5RGM3 12-1TK4OZF 8.1.1.4


Data cannot be posted in the
SOAP UI

ACR 475, Higher Education: The 12-1U5RGQC 12-1TK962G 8.1.1.4


Phone and Email tabs do not
contain a Delete Record button

ACR 475, Higher Education: The 12-1U5RH22 12-1TPS1E1 8.1.1.4


Country field is missing from the
Constituent main view

ACR 475, Higher Education: 12-1U5RH34 12-1TUWQ23 8.1.1.4


Email changes are not reflected
in Email History for constituents

ACR 475, Higher Education: 12-1U5RH46 12-1TUW8FW 8.1.1.4


Phone Number changes are not
reflected within Phone History
for constituents

ACR 475, Higher Education: The 12-1U5RH58 12-1TUW8IF 8.1.1.4


system accepts any phone num
type that is sent in from a web
service call

ACR 475, Higher Education: 12-1U5RIPU 12-1TWTQPT 8.1.1.4


Users are unable to enter data in
the Personal Address field

ACR 475, Higher Education: 12-1U5RIR3 12-1TWTQRK 8.1.1.4


Users are unable to create a
record for affiliation

ACR 475, Higher Education: 12-1U5RITI 12-1U0A72A 8.1.1.4


During BDM, the institution is
not populated for the Affiliation
integration component

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 50 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

ACR 475, DQ: Synchronizer 12-1VR2CAU 12-1VNJ8DR 8.1.1.4


stops after a few addresses are
selected within Accounts and
Contacts

ACR 475: Data matching does 12-1VR5FB1 12-1VNJKCG 8.1.1.4


not work for account and
contact records posted through
EAI

ACR 475: Users are unable to 12-1VR5FCC 12-1VNJ8G2 8.1.1.4


ipmort WSDLs from the build
location

ACR 475, QF3101: Sessions are 12-1VR6B35 12-1VR1NO3 8.1.1.4


restarted/the Object Manager
crashes consistently

ACR 475: Users receive an error 12-1VR6B5T 12-1VR3RJX 8.1.1.4


message when creating records
through the UI

ACR 475, DQ: Using EAI, the 12-1VR6B8F 12-1VR4VCC 8.1.1.4


Update and Upsert of address
information for contacts does
not occur

ACR 475: Users are unable to 12-1VR6BCC 12-1VR4VUQ 8.1.1.4


post household data through
EAI

Enhances UCM to provide Data 12-1X1S0L7 12-1TK672L 8.1.1.4 Yes, see


Governance, Data Quality and “Instructions for
Usability enhancements (ACR ACR 475” on
475) page 230.

QF3105: Within the UCM 12-1ZQWVF9 12-1ZA9UNJ 8.1.1.4


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

ACR 475: UCM session log off 12-1ZW8S4J 12-1ZW8S1B 8.1.1.4


when trying to save changes
made in DRM (such as adding a
new hierarchy to an existing
version)

502 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

ACR 475: The Communication 12-1ZYNARN 12-1Z6WB8N 8.1.1.4


Address User Key is not
enforced for data inserted in
realtime (UI/WSI)

ACR475B: The login for DRM is 12-205G5OJ 12-205G5MC 8.1.1.4


hard-coded

ACR 475: Data loss occurs 12-207UHWR 12-207UHVB 8.1.1.4


during multi-session scenarios

ACR 475, Higher Education: ID 12-1U5RGHR 12-1TK3VGV 8.1.1.4


Type Label is missing

ACR 475, Higher Education: The 12-1U5RGJZ 12-1TK3VKD 8.1.1.4


Street Address field does not
contain a MVG

ACR 475, Higher Education: The 12-1U5RGL1 12-1TK4OXO 8.1.1.4


Streeet Address3 and Street
Addres4 fields cannot be located

ACR 475, Higher Education: The 12-1U5RGN5 12-1TK9ENW 8.1.1.4


Constituent list applet can only
display four records at a time

ACR 475, Higher Education: The 12-1U5RGO7 12-1TK9B70 8.1.1.4


columns meant to be flag
columns for selecting primary
entities are incorrectly named

ACR 475, Higher Education: 12-1U5RGP9 12-1TK9B1B 8.1.1.4


Affiliate Institute ID is displayed
instead of Institution Name

ACR 475, Higher Education: The 12-1U5RGRE 12-1TKA445 8.1.1.4


External Constituent ID view is
not designed correctly

ACR 475, Higher Education: The 12-1U5RGSI 12-1TKA4GE 8.1.1.4


Street Address field and several
other filds are not editable

ACR 475, Higher Education: 12-1U5RGTK 12-1TKA4KE 8.1.1.4


Importing data to the LOY
Profiles and Comm Manager
projects fails

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 50 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

ACR 475, Higher Education: The 12-1U5RGUM 12-1TPS1HM 8.1.1.4


Start/End Date columns should
be named Effective Start/End
Date

ACR 475, Higher Education: The 12-1U5RGVO 12-1TKA9BK 8.1.1.4


Class Year field does not have
UI-level validations

ACR 475, Higher Education: 12-1U5RGWQ 12-1TK9ZE3 8.1.1.4


Effective Start Date is populated
to the current date for ID,
Affiliations, Name, and Address

ACR 475: The Constituent Main 12-1U5RGYU 12-1TPS15R 8.1.1.4


view design is not in accordance
with the design of the rest of the
application

ACR 475, Higher Education: Not 12-1U5RGZY 12-1TPS192 8.1.1.4


all fields are editable in the
Personal Address Selection
applet

ACR 475, Higher Education: The 12-1U5RH10 12-1TPS1BB 8.1.1.4


textbox sizes are not standard
within the Constituent view

ACR 475, Higher Education: The 12-1U5RIUN 12-1U0AR67 8.1.1.4


UCM Batch task errors out

ACR475B: When the Hierarchy 12-205G433 12-204Y7UB 8.1.1.4


Name information for an orphan
account is changed, the change
is not reflected in the UI

ACR475B: If the hierarchy 12-205G43L 12-205FPWT 8.1.1.4


contains special characters, an
error occurs while trying to
launch DRM

Enhances UCM to support the 12-1U0DSWL 12-1TGO7DJ 8.1.1.4 Yes, see


Higher Education application “Instructions for
(ACR 475A) ACR 475” on
page 230.

504 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

The Relationship Hierarchy View 12-1XYCTT8 12-1WXWUIF 8.1.1.4


crashes when the number of
records is greater than or equal
to the MaxCursorSize and
PrefetchSize values

Publish/Subscribe
ACR 475, Higher Education: 12-1U5RIS6 12-1U0AEGZ 8.1.1.4
Publish fails for constituent data

Survivorship
ACR 475: Survivorship is not 12-1VR5FDN 12-1VNKG5Z 8.1.1.4
invoked in transaction manager

User Interface
Controls
Within the calculator function, 12-1XS1MGK 12-1XS1MG0 8.1.1.4
when users press the Enter
button, results do not display

Extra queries are executed when 12-1Y731MN 12-1V4JFKL 8.1.1.4


users click the Back and Forward
browser buttons

The Display_Applet event 12-1NMWHFR 12-1MMQK8H 8.1.1.4


causes screens not to display
correctly

Queries with invalid day 12-1VR3S08 12-1VR3RZJ 8.1.1.4


numbers are accepted

When an HTML form is attached 12-1XBN94Z 12-1WLTVBV 8.1.1.4


to a field, an initial save in the
field will work, but subsequent
attempts to modify the field
contents do not work

History/Back/Refresh
After users click the Back 12-1VR2ZJV 12-OVT1LK 8.1.1.4
button, applets are displayed as
form applets instead of as list
applets

Layout and Rendering

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 50 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

When personalization is used, 12-1VHLJA2 12-1UK0QN1 8.1.1.4


form applet field labels do not
appear the first time

When using run-time events and 12-1ZM340L 12-1NVVH71 8.1.1.4


personalization rules to drive
toggle applet selection, the first
time that the toggle applet
displays results in an incomplete
display

List applets show "hidden" list 12-1XPMTE7 12-1XC7L61 8.1.1.4


column when users create a new
record

Resizing the screen causes one 12-1RB0A83 12-1R4A19T 8.1.1.4


applet to be painted on top of
another

Toggle applets become 12-1V9U9X3 12-1U5V2W5 8.1.1.4


corrupted when a
personalization rule is specified

Navigation
With Internet Explorer 7, when 12-1YMM6I5 12-1Y54CNH 8.1.1.4
users drill down on a link, the
application crashes

Other
Within Server Reporting, 12-1ZARFCK 12-1YO2RKX 8.1.1.4
predefined queries that contain
umlauts do not perform well

ACR 600: Three shortcut keys 12-20QA1DI 12-20QA1AR 8.1.1.4


were removed, so the SIF file
does not import properly

Popups/Pick Lists/
MVG/Shuttle
With Auto-hide on, closing an 12-1XTI9RZ 12-1XRKL8L 8.1.1.4
MVG results in a minimized
window

Toolbars/Menus/
Keyboard

506 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 16. Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack

Fix Request Change Fixed in Special


Issue Addressed ID Request ID Version Instructions

Pressing the TAB key causes the 12-1SC970H 12-1HCLBH7 8.1.1.4


focus to jump to the next applet,
not the next field

Screen menus stop working 12-1YOKUKR 12-1YOKG15 8.1.1.4


after MVG operations are
cancelled

Web Service
Other
The Siebel application expires 12-20M5KBU 12-20M5KB3 8.1.1.4
the session token when
SiebelSessionTimeOut value is
less than the
SessionTokenTimeout value

Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack


This topic is part of “Resolved Change Requests” on page 462.

Table 17 lists the Change Requests that were resolved in the 8.1.1.3 Fix Pack

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Call Center
CTI
After 7.8.2.3 QFJ316 has been 12-1RRBR7O 12-1REPWYN 8.1.1.3
applied, CTI toolbar worker
threads loop infinitely

The Communications toolbar 12-1S0YVAJ 12-1RXY8FA 8.1.1.3


freezes if it receives an HTTP
message that contains no
content after a push connection
request

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 50 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

A crash occurs with 12-1VR7RHL 12-1VNKRB3 8.1.1.3


SCCObjMgr_enu on use of
invoking method for invoking a
command on Communication
Session Manager (CSM)

ACR 574: If the application is 12- 12-1WFFM67 8.1.1.3


idle for a few hours, users 1WMU5BW
cannot connect to Smart Answer
Server for KB

When users send email using the 12-1XZTJ3V 12-1XSTNYN 8.1.1.3


F9 command, the "To" field is
not being populated

Other
Searchable fields in the search 12-1PILI7W 12-1ONVDPT 8.1.1.3
results view are not being shown

RaiseErrorText in PreLeave 12- 12-1PSNSBZ 8.1.1.3


prevents SaveUserParameter 1QGOBD8
from working

When users query in the All 12-1SSCGFN 12-1SPY0IE 8.1.1.3


Communications view, the HTML
toolbar is displayed

Users are not able to change a 12-1TUEA6P 12-1SFP9CV 8.1.1.3 Yes, see
default date for Advanced “Instructions for
Search FR 12-1TUEA6P”
on page 717.

Error SBL-SVR-00006 occurs in 12-1U0BJHL 12-1TD6WP5 8.1.1.3


workflows that call Outbound
Communications Manager

When Search/Find is closed 12- 12-1OFLUA5 8.1.1.3


using the "X" button, the 1U5QXWD
application navigates to the
login page

After indexing certain business 12-1UIAGQE 12-1RKLPVN 8.1.1.3


components for mobile search,
the datasource is shown as
"buscomp".

Field values are erased out after 12-1US5UAP 12-1FJKS6A 8.1.1.3


users cancel the F9 send mail
command

508 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Within the eChannel application, 12-1UX632W 12-1UGQKS5 8.1.1.3


the Find function is not working

When users navigate to the All 12-1VM90QP 12-1T7D4XN 8.1.1.3


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

When users select and use a 12-1VMB73K 12-1VHLD1H 8.1.1.3


Simple Email Template that
belongs to a different language,
the Web Client caches that
language

With service requests that have 12-1VNJLI3 12-1VM81EJ 8.1.1.3


more than one attachment,
when users select a different
attachment than the one that is
defaulted to and press F9, the
application hangs

ACR 574: Provides Lymba as the 12-1WB70VJ 12-1UI8IN7 8.1.1.3 Yes, see
Smart Answer Engine “Instructions for
ACR 574” on
page 432.

ACR 574: When an inbound 12- 12-1VR6FWO 8.1.1.3


email is sent that does not 1WB70WQ
contain a matching string, the
customer does not receive an
acknowledgement email

ACR 574: Provides a Refresh 12-1WB70Z8 12-1VMJW4R 8.1.1.3


button on the Administration
Catalog screen to allow users to
synchronize the catalog

ACR 574: Enables error- 12-1WB710H 12-1VNJJXN 8.1.1.3


handling and logging in Siebel
Smart Answer Connector

ACR 574: Users cannot send the 12-1WEE3SH 12-1VNJJZ2 8.1.1.3


Catalog Name to the Lymba
Adapter with an API call

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 50 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

ACR 574: Search Center closes 12-1WEE3TP 12-1VNJZ8L 8.1.1.3


when users click the Smart
Answer button

ACR 574: Smart Answer: Users 12- 12-1VNJZ9H 8.1.1.3


are unable to close Search 1WEE3UU
Center using the X icon in
certain scenarios

ACR 574: Smart Answer: Users 12-1WEE3VZ 12-1VR398K 8.1.1.3


are unable to import language
XML files into the
Knowledgebase catalog within
the Siebel application

ACR 574: AutoResponse exits 12-1WEE3XE 12-1VR4FMB 8.1.1.3


with an error and no
autoresponse is sent to the
client

ACR 574: For some instances of 12-1WEE3YJ 12-1VR4V1B 8.1.1.3


the Smart Answer process, file
reading fails because of
concurrent access

ACR 574: The Smart Answer 12-1WEE3ZV 12-1VR4A7V 8.1.1.3


Synchronize button is not
translated

ACR 574: Auto Response 12-1WEE410 12-1VR3GUN 8.1.1.3


behavior is inconsistent

ACR 574: Lymba Smart Answer: 12-1WEE425 12-1VR6QRN 8.1.1.3


The Siebel application does not
call the SM component when
agents choose Yes or No for
feedback

With ACR 439 installed and with 12-1WLTQ3L 12-1VE7EQ3 8.1.1.3


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

510 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Object Manager crashes when 12- 12-1UH87BR 8.1.1.3


indexing 1,000,000 employee 1WLUWSV
records

ACR 574: If users perform blank 12- 12-1WCP9WP 8.1.1.3


summary queries on Service 1WMU59O
Requests or from Search Center,
they recieve the "Smart Answer
component unavailable" error
message

ACR 574: When Port 1099 is 12- 12-1WF73FF 8.1.1.3


used, Lymba Smart Answer 1WMU5A0
server immediately shuts down
with an "unable to connect"
exception

ACR 574: When multiple emails 12- 12-1WF77PG 8.1.1.3


are sent or requests are made to 1WMU5AY
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

Within the eChannel application, 12-1X6DJB3 12-1WTJXYN 8.1.1.3


Binocular Search does not work

Within CRM Chat, the Spell 12-1Y36UV1 12-1Y2PWNA 8.1.1.3


Check button does not work

Comm Media
Energy
Order Management
Provides support for the OSM 12-1UJS4WK 12-1TK6U03 8.1.1.3 Yes, see
Integration and new Order to “Instructions for
Activate PIP, and forward-ports ACR 474 and ACR
MDM for customer and PIM, and 508” on
Order to Cash enhancements page 159.
from 8.x to 8.1.1. (ACR 474/
AIACOMS 2.5)

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 51 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Provides support for the OSM 12-1UZ5YMC 12-1UW5DFF 8.1.1.3 Yes, see
Integration and new Order to “Instructions for
Activate PIP, and forward-ports ACR 474 and ACR
MDM for customer and PIM, and 508” on
Order to Cash enhancements page 159.
from 8.x to 8.1.1.x (ACR 474/
AIACOMS 2.5)

Provides Order to Activate and 12- 12-1R3SHD7 8.1.1.3 Yes, see


Order to Bill PIP enhancements 1RDW596 “Instructions for
(ACR 463/AIACOMS 2.4) ACR 463” on
page 103.

Provides an OSM Integration and 12-1VM9314 12-1VM7OFB 8.1.1.3 Yes, see


the new Order to Activate PIP “Instructions for
and forward- ports MDM, PIM, ACR 474 and ACR
and Order to Cash 508” on page 159
enhancements from version 8.x
to version 8.1.1.x (ACR 474/
AIACOMS 2.5.1)

Supports OSM Integration and 12-1VR3ZSJ 12-1VR2NH1 8.1.1.3 Yes, see


the Order to Activate PIP, and “Instructions for
forward-ports MDM for customer ACR 474 and ACR
and PIM, O2C Enhancements 508” on page 159
from 8.x to 8.1.1.x (ACR 474/
AIACOMS 2.5.1)

Provides Order to Activate and 12-1W6062R 12-1R3SHD7 8.1.1.3 Yes, see


Order to Bill PIP enhancements “Instructions for
(ACR 474/AIACOMS 2.4) ACR 463” on
page 103.

ACR 474: When users create a 12-1X5NNA5 12-1X56KI9 8.1.1.3


Follow On order, an error
message displays

ACR 474: Within the Sales Order 12-1X5NXC8 12-1X56155 8.1.1.3


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

512 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

ACR 474: Within the Sales Order 12-1X5NXEM 12-1X56KGX 8.1.1.3


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.

Enables effective bundling of 12-1XHX8VP 12-1V41SPV 8.1.1.3 Yes, see


products necessary in “Instructions for
communications, finance, ACR 500” on
media, and utiltities industries page 318.
to enhance promotion
capabilities for component-level
commitment, eligibility in
promotion upgrade, asset-based
recommendations, and split/
merge capabilities of promotions
(ACR 500).

When users create a new sales 12-1XTI4WC 12-1X0C24K 8.1.1.3 Yes, see
order, add a TBO product to the “Instructions for
order, click Customize, and then ACR 474 and ACR
click Done, within Sales Order 508” on
line items, the Service Start page 159.
Date field is blank

Promotional discounts for items 12-1Y3OPD3 12-1XSJPP1 8.1.1.3 Yes, see


are not being applied to BRM “Instructions for
ACR 474 and ACR
508” on
page 159.

Customer service 12-1Y36V3X 12-1Y0B1ZJ 8.1.1.3 Yes, see


representatives can delete root “Instructions for
customizable products that have ACR 474 and ACR
components that have reached 508” on
the "point of no return" in page 159.
revised orders

ACR 474: The bar on the line 12-1Y3OPDC 12-1XTI4RH 8.1.1.3 Yes, see
items view shows a cancelled “Instructions for
status ACR 474 and ACR
508” on
page 159.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 51 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

ACR 474: Revised orders copy 12-1Y3OPDM 12-1XTI4OQ 8.1.1.3 Yes, see
fulfillment status and status “Instructions for
context from the base order ACR 474 and ACR
508” on
page 159.

When Manual Price Override is '12-1Y6LFEF 12-1XVFMBA 8.1.1.3 Yes, see


updated on a modified order, the “Instructions for
action code is not changed to ACR 474 and ACR
'Update 508” on
page 159.

Users cannot modify orders to 12-1Y6LFEP 12-1XSJPMM 8.1.1.3 Yes, see


customize a Service Bundle “Instructions for
ACR 474 and ACR
508” on
page 159.

Errors occur when updating the 12-1Y6LLL2 12-1Y6LLKD 8.1.1.3 Yes, see
Part# or inserting a record with “Instructions for
the Part # field populated in the ACR 474 and ACR
line 508” on
page 159.

When users modify orders, the 12-1Y6LLLG 12-1XVXEFP 8.1.1.3


Siebel Server crashes

ACR 474: Users do not get an 12-1YIQMGO 12-1U0ATEW 8.1.1.3


error message in the SOAP
response when they enter the
class release date as DD/MM/YY
format

ACR 474: EAI Data 12-1YIQMHB 12-1U0BPB9 8.1.1.3


Transformation Engine creates
an empty container in the output

ACR 474: The application 12-1YK6THT 12-1U089B9 8.1.1.3 Yes, see


crashes when users drill down on “Instructions for
a copied order that was created ACR 474 and ACR
using the CTRL+B shortcut 508” on
page 159.

Other

514 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

ACR 474: Date-time data that is 12-1YIQMEE 12-1VR2YCD 8.1.1.3


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

Connectors/EAI
Application Svc
Interface/ASI
EAIHttpRespStatus code is set to 12-1RXY7ZA 12-1QNEH19 8.1.1.3
the incorrect value on Itanium
systems

EAI Server
Components
After 8.0.0.2 QF2207 has been 12-1UI8D5R 12-1U5R29R 8.1.1.3
applied, the 'signature' error still
occurs with a SWSE timeout

An error occurs during base64 12-1VNJD5G 12-1UX6FV5 8.1.1.3


attachment conversion
(IntObjPS to XMLDoc)

MQ Receiver Logs contain 12-1VR5P25 12-1RAJ0L3 8.1.1.3


unnecessary entries

Other
Date-time data passed in 12-1YOLHXJ 12-1YOLHWR 8.1.1.3 Yes, see
payloads in UTC canonical “Instructions for
format (such as '2009-08- FR 12-1YOLHXJ”
14T03:09:01Z') throws the on page 717.
"cannot convert the value to
Date-Time" error message

If a Web service SOAP response 12-1SBR7MX 12-1KXYCJ7 8.1.1.3


contains a character length
greater than 100 K, then the
Web service errors out

EAI HTTP requests should not 12-1U0BRC3 12-1TD6XBN 8.1.1.3


send BOM in UTF-16 XML with
byte endian information in the
encoding

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 51 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

XML Convertor does not 12-1VR4PJL 12-1VNJ4JJ 8.1.1.3


correctly convert property
names that start with a number

VBC-based CSSFABCVRec class 12-1VR4ZV9 12-1VR2PWN 8.1.1.3


only works for alternate calls

EAI Siebel Adapter ignores IC 12-1WIYSJ4 12-1VR2PRN 8.1.1.3


Field Precision and Scale
settings

EAI UI Date Adapter does not 12-1WV14V4 12-1WVI3Q5 8.1.1.3


return error messages without
error codes

Consumer Sector
Handheld
The Cancel Invoice function does 12-1VMB721 12-1VM6HI1 8.1.1.3 Yes, see
not allow invoices to be marked “Instructions for
for deletion/voided FR 12-1VMB721
and FR 12-
1X0C0IZ” on
page 711.

The Book, Cancel, Deliver, 12-1Y4N2FP 12-1Y4N2E7 8.1.1.3


Invoice, and List Product buttons
are disabled

Other
While processing accrual 12-1TPUQPM 12-1TGOA74 8.1.1.3
records, the addition is not
correct for the update to the
S_MDF_ACCRUAL.REVENUE_AM
T field

Customers are not able to void 12-1X0C0IZ 12-1VMBL0Z 8.1.1.3 Yes, see
faulty invoices and undo “Instructions for
payments and delivery for the FR 12-1VMB721
faulty invoices and FR 12-
1X0C0IZ” on
page 711

Objectives
Error messages that occur 12-1WHFTJD 12-1WF6PQV 8.1.1.3
during field validation do not
display correctly

516 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Sales Volume Planning


Category Aggregation Fields are 12- 12-1KGMH5V 8.1.1.3 Yes, see
not properly populated prior to 1NQ7VRQ “Instructions for
aggregation FR 12-1NQ7VRO”
on page 710.

Export functionality on CG SVP 12-1VK07NT 12-1U09RY5 8.1.1.3


Catalog Category Product
results in error-SBL-UIF-00146

Trade Promotions
ACR 480: Within Corporate 12- 12-1VR4BZH 8.1.1.3 Yes, see
Promotions, the Apply Updates 1XCMB0W “Instructions for
function pushes products to the FR 12-1XCMB0W”
wrong category on page 710.

Customer Order
Management
Configurator
Applying FR 12-1N7B0OP causes 12-1VNJ53G 12-1VM83AX 8.1.1.3
action codes to be incorrect

With Asset-Based Ordering 12-1WYEK8I 12-1VM6N4J 8.1.1.3


enabled, the BeginConfiguration
Web service throws an error
message when loading quotes
from modified assets

The LineItemICField user 12-1XC4G9C 12-1VR66BT 8.1.1.3


property does not work for
nested products

Order Management
Enhances the AIA Order-to-Cash 12-1UZ5YP2 12-1UW5F8T 8.1.1.3 Yes, see
PIP to provide the ability to “Instructions for
change data on the Siebel Order ACR 508” on
screen and send the order to E- page 356.
Business Suite for processing
(ACR 508)

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 51 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Enhances the AIA Order-to-Cash 12-1V2K3L1 12-1V0MXXD 8.1.1.3 Yes, see


PIP to provide the ability to “Instructions for
change data on the Siebel Order ACR 508” on
screen and send the order to E- page 356.
Business Suite for processing
(ACR 508)

The default cardinalities of 12-1VG4IQP 12-1STC0L5 8.1.1.3


promotion components are not
properly enforced for grandchild
products

Signal Conditions do not 12-1VLO03W 12-1VDPX7V 8.1.1.3


function appropriately

Promotion Product Defect: 12-1VR1Q8I 12-1VNJ20P 8.1.1.3


Conditional Constraint does not
resolve properly with Promotion
Attribute Domain Filter

With Promotions, a default 12-1VR5DVQ 12-1VNJZD9 8.1.1.3


attribute values cause an
unresolvable error

When a promotion has a 12- 12-1VM6B55 8.1.1.3


modified relationship domain, 1VR4WHT
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'.”

Batch Validate evalutes 12-1VR7NMF 12-1VNJ8NI 8.1.1.3


Attributes with Action Code =
Delete, which results in a Batch
Validate error message

With promotions, there is an 12-1WF6JAZ 12-1WF5ZQH 8.1.1.3


issue where the constraint and
promotion defintions have
contrasting constraints, and
users receive an error message

Bulk Orders: Addresses an issue 12-1X0SXWT 12-1VR43FP 8.1.1.3


where BatchValidate is not
implementing a requires rule.

518 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

The SBL-DAT-00500 error 12-1X5NSWF 12-1WXFOAB 8.1.1.3


message occurs when the VORD
CPVE Validation business service
is invoked

Verification of Product 12-1XT0Z2X 12-1XT180B 8.1.1.3


Promotions fails the max
cardinality rules due to
disconnected assets

Upgrade Promotion does not 12-1YAH2Q9 12-1RYJL7R 8.1.1.3


update Action Codes
appropriately nor does it upsert
components appropriately. This
patch address child components
that do exist in the destination
but not the source promotion

Within Promotions, Precision/ 12-1YCX6CX 12-1XRKKYV 8.1.1.3 Yes, see


Scale deficiencies occur in “Instructions for
Component-Based Pricing FR 12-1YCX6CX”
on page 709.

Orders
If a CP has lot of rules with 12-1V7FE0H 12-1UWODHL 8.1.1.3
required attributes and the
attributes are not selected,
clicking Verify yields the
following error message: Value
too long for field 'Return
Message' (maximum size
1000).(SBL-DAT-00235)

Users receive an error message 12-1XTBMZ0 12-1XTBMYB 8.1.1.3


when they add a customizable
product to an order, customize
the order, and then click the
Done button

Other
Users receive an error message 12-1X5NS4E 12-1X47HF9 8.1.1.3
when they upgrade promotions
from Service Account Installed
Assets

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 51 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Within Bundled Promotions, 12-1X65MC7 12-1X3PH1V 8.1.1.3


defaults via a promotion's
cardinality are not enforced for
Class Product definitions

Pricer
When users invoke the Pricing 12-1X5NXAL 12-1W6PXXB 8.1.1.3
Waterfall pick applet, the
application hangs

Sales Catalog
An error occurs when users 12-1YFTLDP 12-1XB55W9 8.1.1.3
disconnect a promotion after a
component of the promotion has
been disconnected

Data Quality
Deduplication
In the Polish (PLK) v8.1.1 12- 12-1UQ61Q1 8.1.1.3
version of the application, an 1VGM2UG
error occurs while running the
SSA Name3 library (n3sgsb)

If the Deduplication popup 12-1VR7B29 12-1TXBDIV 8.1.1.3


applet is the first popup window
for the current session, the
browser hangs

Other
Using ISS with Siebel 8.0 results 12-1U0CY1S 12-1STC0TH 8.1.1.3
in the SBL-DAT-00381 error
message

Financial Services
Other
Within Claims > Loss Details, 12-1Y5LSOW 12-1Y5LSL2 8.1.1.3
the Create Reserves button is
disabled in the Coverages list
applet

Within Claims> Financials, the 12- 12-1Y5W0GX 8.1.1.3


New button is disabled in the 1Y5W0HO
Payments list applet

520 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

General
Activities
When users attempt to update 12-1R1BTR7 12-1QJ1W43 8.1.1.3
the Planned Date and Due Date
fields using the Action Business
component through workflow
processes, the inserted values
are not saved to the database

Application
Administration
If users do not have the Siebel 12- 12-1XZMHAN 8.1.1.3
administrator privileges/ 1XZMHBG
responsibilities for their
Contacts and Responsibilities,
login fails

Assignment Manager
ACR 456: Formats of exported 12-1TWTYTF 12-1TWTYSQ 8.1.1.3
and imported files should be the
same

Audit Trail
The Audit Trail button behaves 12-1SPH0YN 12-1S5B2VD 8.1.1.3
inconsistently

The Audit Trail does not work for 12-1SWPT3X 12-1SD8XW1 8.1.1.3
the "FINS Claims Reserve Code
Admin" Business Component

Audit Trail About Record shows 12-1TK7QD5 12-1T6EFZV 8.1.1.3


wrong or null data

When Audit Trail is enabled for a 12- 12-1V41905 8.1.1.3


Long or CLOB column in an 1V7X3WH
extension table, the delete
operation fails

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 52 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Within the Position BC, the audit 12-1VBRSC2 12-1VBRSBI 8.1.1.3


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

Calendar
The Send Email function is 12-1N1KL71 12-1K4ZTWH 8.1.1.3
unavailable

Within 7.7x, 7.8.x, 8.0.x, and 12- 12-1UMN79T 8.1.1.3


8.1.x applications, when users 1UMN7BM
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.

Toggling applets on the LS 12- 12-1CANJO7 8.1.1.3


Pharma HI Activity Calendar 1N0KW3X
View causes a view refresh

Incorrect background colors on 12-1N1KBEQ 12-1IU58IV 8.1.1.3


Currency/Calendar popup

Changes made to Calendar 12-1N1KBVR 12-1EA3KYL 8.1.1.3


dates are not reflected in
Attendee Activities

The Alarm Manager can be 12- 12-1GK2GR8 8.1.1.3


disabled by editing a text field 1N1KHWC

For repeating appointments, 12-1N1KLLH 12-1K8JU30 8.1.1.3


when users click the Delete This
Appointment button, all of the
appointments are deleted

When users click the New button 12-1O9NHG3 12-1NJLF4A 8.1.1.3


in the Calendar applet in the
Home Page view, an 'End of File'
error is generated

An appointment created by User 12- 12-1NJLF3J 8.1.1.3


A on User B's shared calendar 1P5O1MW
also appears on User A's
calendar

522 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Events that cross a day 12-1Q3MZVP 12-1OTU3FT 8.1.1.3


boundary are not shown on the
second day

When users change the start/ 12-1QU6RIC 12-1QNF2NB 8.1.1.3


end time for an appointment on
a Calendar Detail applet, the
selected time is not saved
correctly

Adding employees on Calendar 12-1TG5AM6 12-1LPLAB7 8.1.1.3


GanttChart AX Applet is ignored
by screen navigation

Users are allowed to set 12-1TK63CO 12-1SF7VWH 8.1.1.3


Type=NULL on existing
appointments

When users navigate to Site Map 12-1U5U0M0 12-1U5U0KT 8.1.1.3


> Calendar view and click the
New Contact Call or the New
Account Call button, the
application hangs

After users create a new call in 12-1VJZVMV 12-1V418GZ 8.1.1.3


ePharma version 8.1.1, the call
detail fields are greyed out and
uneditable

Duplicate records are displayed 12-1VM67Y1 12-1THO6TP 8.1.1.3


on calendars in the Brasilia time
zone

Within the JPN application, the 12- 12-1VR5EY9 8.1.1.3


weekly calendar view is partially 1VR7CWB
cut off

Within the Portuguese-Brazilian 12-1VR77QR 12-1VM5K6V 8.1.1.3


version of the application, the
week abbreviations display
incorrectly in the calendar popup

Incorrect abbreviation for 12-1VR77RQ 12-1VR2PUZ 8.1.1.3


Saturday in ESN calendar

When users add new contacts or 12-1YM4R1Q 12-1YM4R0X 8.1.1.3


employees to the calendar, the
application crashes

Content Management

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 52 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

When users click the Back 12-1P5O1KL 12-1I1GBT5 8.1.1.3


button from within a microsite
within the eCustomer
application, they receive an
error message

Correspondence
Correspondence documents 12-1T2SVNQ 12-1SJNUGJ 8.1.1.3
contain additional space
characters

CRM Desktop
CRM Desktop: Improves the 12-1Y27VNT 12-1Y27VMJ 8.1.1.3
quality of the 'SBL-DOI-00006'
and 'SBL-DOI-00007' error
messages

CRM Desktop: The text in the 12-1Y28BQJ 12-1XHWPV2 8.1.1.3


"SBL-DOI-00007" error message
is not clear

The Import button does not 12- 12-1VNKOUR 8.1.1.3


work on CRM Desktop Admin 1VNKOWM
Views

File System
File System cleanup fails with 12-1UK14LM 12-1UI9S1Q 8.1.1.3
the "Failed to open the iterator"
error message

Installation
In 8.1.1.2, some files related to 12-1WR7UFE 12-1WR7UEP 8.1.1.3
siebel_sample_database are
missing

Siebel Web Client Patchset 12-1X663ED 12-1VR46RP 8.1.1.3


8.1.1.1 PTG language is not
applied correctly over 8.1.1 SIA

Other
Records obtained using the 12-1SCRGIB 12-1QV5W97 8.1.1.3
Access drop-down list display in
Base mode instead of in Edit
mode

524 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

COMCreateObject causes error 12-1TJM70N 12-1T12HLZ 8.1.1.3


when object instance set to null
in eScript with Deduce Types set
to True

After 8.0.0.5 QF05AB has been 12-1U5UH1R 12-1U5RO9P 8.1.1.3


applied, a scripting error occurs
when calling a method on a
business component

Comparing disparate data types 12-1UGZRFB 12-1U0CP53 8.1.1.3


such as a string to an integer in
eScript using the >, <, >=, <=,
== logical operators causes the
script to exit.

Scripts in the WriteRecord event 12- 12-1U5VHQV 8.1.1.3


of attachment business 1UW5AWW
components show inconsistent
error message behavior

When using the business service 12-1V0ND11 12-1UZMXMX 8.1.1.3


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

RaiseErrorText in SVB when 12-1VCQU0V 12-1V418N3 8.1.1.3


populated with the Error$
function does not recognize the
return from the Error$ function
and the error message is not
displayed correctly

DisableSearch functionality 12-1VEOXTT 12-1UI8TH3 8.1.1.3


allows searching on fields

With 8.1.1.1, calling methods in 12- 12-1VH3RGB 8.1.1.3


objects scripted in Siebel Visual 1VH3RGW
Basic fails with a runtime error

Dynamic drilldowns do not work 12-1VMCEOI 12-1VMCENX 8.1.1.3


when the value of the drilldown
field is changed

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 52 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

The Object Manager crashes 12-1VR2MU3 12-1DK2UO8 8.1.1.3


when users generate reports
using Actuate

Business services are not found 12-1VR3RGV 12-1VM7TM9 8.1.1.3


if they are first called in server
script, and then called in
browser script

The eScript GetMonth method 12-1VR6F3U 12-1VR5H23 8.1.1.3


displays the wrong value on
months with 30 days or more

The ToggleTo SWE method 12- 12-1WLTLED 8.1.1.3


causes applet runtime error 1WQVBBB

The traditional eScript engine 12- 12-1WF6PMP 8.1.1.3


has a runtime error when calling 1WRMDVP
business service methods from
application object events such
as Application_Start

Scripts that placed in the 12- 12-FH9TL9 8.1.1.3


general declaration sections of 1WU1SDA
business services only fire once
instead of running once for each
iteration

RaiseErrorText does not pass 12-1X1AZTH 12-1WV0HS3 8.1.1.3


back Error Code or Error
Message to workflow processes
or log files

The script in the 12-1Y27TNJ 12-1XC7L1L 8.1.1.3


Application_Start event is not
firing

The Data Transformation Engine 12-1YOLHYY 12-1YOLHXV 8.1.1.3


does not handle error messages
for invalid dates

Personalization
It is not possible to use 12-1RV70SJ 12-1JJTA87 8.1.1.3
personalization rules to hide
views dynamically in Siebel 8.0

Hiding an applet with 12-1VMAFZA 12-1VMAFY3 8.1.1.3


Personalization causes a corrupt
user interface

526 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

PIM Server
Integration
If an attendee is added to an 12- 12-1V9UFL1 8.1.1.3
Outlook/Exchange calendar item 1VM9ZON
after the initial sync, the data is
not pushed to the Siebel
database

When a non-sync enabled user 12-1SPYM2L 12-1S8Q8A5 8.1.1.3


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

Allows resizing of the Outlook 12-1UI8PUU 12-1S0YE6N 8.1.1.3


Add-in Window

Removes the 12-1VM60QY 12-1VM60PT 8.1.1.3


"ForceAttendeeLowerCase"
parameter from the SSSE
product

After 8.0.0.5 QF0581 has been 12-1VM8LG0 12-1VH3ELT 8.1.1.3


installed, user-level extract start
date functionality does not work

Only the first contact invited to a 12-1VR7GA3 12-1VR6AAV 8.1.1.3


meeting is synchronized

Appointments that start before 12-1WLU29Y 12-1SG6WNZ 8.1.1.3 Yes, see


and end after a Daylight Savings “Instructions for
Time transition are not FR 12-1WLU29Y”
synchronized appropriately on page 709.

If an external organizer invites 12-1X8ID8R 12-1VNK3XP 8.1.1.3


two users to a meeting, and one
accepts, then declines before
the second user accepts, a
duplicate meeting is created

Remote
File System cleanup deletes files 12-1UQ47CQ 12-1UJQWRB 8.1.1.3
that are referenced

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 52 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

After QF05AB has been applied, 12- 12-1U0AX75 8.1.1.3


when the application is 1URKHHM
restarted, TxnProc starts
reprocessing previously routed
transactions

The solution to CR# 12- 12- 12-1VNIMYR 8.1.1.3


1U0AX75 caused the following 1VNK25W
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

The ScanAPI.dll fails to load 12-1WFVVYB 12-1VR6T39 8.1.1.3


error messages on the Motorola
SYMBOL scanner

After Siebel 8 Web Client has 12-1WLUUYX 12-1U5R7RT 8.1.1.3


been installed on an XP
machine, the machine hangs for
five minutes

Transaction Processor becomes 12- 12-1T2IN2L 8.1.1.3


slow when it processes large 1WYEWYD
set-based transactions logged
by EIM

Reports Server
Users are not able to add a 12-1QCSJZ4 12-1QCSJXR 8.1.1.3
sequence number to the Reports
applet in View Association

Adds default output type to User 12-1QG70TR 12-1QG70RX 8.1.1.3


Preferences > Report
Parameters

When users run a report, the 12- 12-1Q16OWB 8.1.1.3


Applet Search specification is 1RDWNBK
not applied

Not possible to run multiple 12-1SD8MFS 12-1IERLJL 8.1.1.3


language reports on a single
object manager

528 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

The Search Specification field is 12-1SG6W3F 12-1PVLXKZ 8.1.1.3 Yes, see


read-only for the Primary IO in “Instructions for
the Report Template Integration FR 12-1SG6W3F”
Objects view on page 709.

It is not possible to run a BI 12-1SJN8HF 12-1QG70K8 8.1.1.3


Publisher report for a current
highlighted record or records

Reports are not visible by 12-1SZ541H 12-1PBVOVN 8.1.1.3


position in "My Reports" and
Reports cannot be shared

Users are unable to upload a 12-1TK644R 12-1TCP66H 8.1.1.3


updated report template if the
template already exists on the
BIP Server

With parameterized reports, 12-1UG999N 12-1UAZJSL 8.1.1.3


when users do not select a
report output type in the
Parameter applet, they receive
an error message

Users cannot schedule both 12-1UIBFZN 12-1UIBFXT 8.1.1.3


Actuate and BI Publisher reports

When users schedule a report to 12-1VE7GVE 12-1VE7DPF 8.1.1.3


run once, it fails if the month is
set to 10, 11, or 12

Integration Object Name does 12-1VLO3PN 12-1V7X8ZB 8.1.1.3


not validate with LOV values

When users execute Parent/ 12-1VMA29T 12-1UH87LR 8.1.1.3


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)

When users execute Parent/ 12- 12-1VKHEG7 8.1.1.3


Child reports from a My...view, 1VMA2BM
the reports display only
position-based visibility rather
than displaying all child records
associated to the parent record
(Report component)

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 52 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

The 'BIP Report Wait Time' 12- 12-1QHN64C 8.1.1.3


parameter has no effect 1VMAKQX

Modifies the Report Output 12-1VNIO88 12-1VNIO6N 8.1.1.3


applet to allow users to query on
output type

Allows uers to run multiple 12- 12-1VWTRU1 8.1.1.3


language reports on a single 1VWTRVD
Object Manager for XMLP
reports

When more than one report is 12- 12-1VR5SGX 8.1.1.3


executed in the same session, 1WCP9GB
only the first report is displayed

Enables query and delete on 12- 12-1QD9UWH 8.1.1.3


additional fields in the Purge 1WHOAH7
Reports view

BI Publisher views are not 12-1WUJ0OL 12-1WQ5P93 8.1.1.3


displayed based on the Siebel
user language defaults or Object
Manager language/location

It is not possible to perform date 12- 12-1WV0H8I 8.1.1.3


calculations in BIP templates 1WV0HA1
unless the date fields are in
canonical format

It is not possible to schedule 12-1X0BJ1E 12-1X0BIZX 8.1.1.3


reports after the Siebel Reports
Adapter has been applied

Corrects instances of BIP to BI 12-1X1AJME 12-1P90KAL 8.1.1.3


Publisher throughout the
interface

The XMLP Report Schedule 12-1X1AJS9 12-1VNJS6Z 8.1.1.3


Applet is missing German string
values

Actuate Report scheduling fails 12-1X1ADBJ 12-1WTJXQV 8.1.1.3

When the BIP Report Wait Time 12-1XANNSX 12-1X3RF25 8.1.1.3


threshold is exceeded, the
popup window that displays is
not in focus

530 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

When users set a default value 12-1XIE4NT 12-1X29VEW 8.1.1.3 Yes, see
for an LOV parameter in the RTF “Instructions for
template, the default value that FR 12-1XIE4NT”
they set does not appear as the on page 709.
default value in the popup list
applet

For non-reporting deployments, 12-1XOOCIT 12-1XM9LA9 8.1.1.3


sets the system preference
ReportEngineType system
preference to ACTUATE

Report Administration screen 12-1XWFG3I 12-1XWFG1Z 8.1.1.3


names display incorrectly

Within Administration - BI 12-1YN3MMI 12-1YN3MLR 8.1.1.3


Publisher, when users click the
Generate Sample XML button,
an error message appears

Search
Fields of type DTYPE_PHONE are 12-1SPY7BZ 12-1S9QMMD 8.1.1.3
not searchable

Incremental Index jobs crash 12-1XFIDCF 12-1XFIDB5 8.1.1.3


while creating feed files

The Administration - Search 12-1Y90LL6 12-1Y90LJM 8.1.1.3 Yes, see


screen is not accessible “Instructions for
FR 12-1Y90LL6”
on page 709.

Security
eService permits users to log in 12-1TI62O9 12-1T2II25 8.1.1.3
with expired LDAP passwords

Send Email
When users cancel the F9 Send 12-1U93HR1 12-1TSQ0MP 8.1.1.3
Mail command, list applets
become unresponsive

Server Infrastructure
The default values of compiler 12-1O9NH16 12-SNUGZT 8.1.1.3
define FD_SETSIZE on Solaris
and HP-UX are set too low

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 53 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

The 'list stats' and 'list stats for 12-1RHA25T 12-1QXJF75 8.1.1.3
comp SCCObjMgr_enu' srvrmgr
commands produce an invalid
value-INF-for the CPUTime
statistic

Business service instances may 12-1RZIYCN 12-1QZYA5Z 8.1.1.3


not be deleted from memory
whether the cache flag is set to
True (checked) or False
(unchecked)

Object Mananger exits with an 12-1TH3VV7 12-1MANTCD 8.1.1.3


error message when users
cancel the send email or fax
functions

The SiebelAdmin RoleName 12-1U08CUZ 12-1U08DIB 8.1.1.3


parameter cannot be changed
using the Server Manager
command line command

Siebel Object Managers fail 12-1VNJ4VA 12-1VMCEHT 8.1.1.3


when querying on sessions using
the Server Manager UI

Server Manager List Tasks 12-1XIQSKH 12-1S9QMWN 8.1.1.3


command performs slowly

Siebel Sync
After version 7.7.2.10 has been 12-1X980QT 12-1Q5L7W9 8.1.1.3
installed, the Lotus Notes Action
button disappears at the second
synchronization

SmartScript
ACR 574: Users are not able to 12-1WB70Y1 12-1VR347X 8.1.1.3
import different files using the
Smart Answer import button

ACR 574: Error message 'SBL- 12- 12-1VR3957 8.1.1.3


SMA-00153' is not translated 1WMU59B
into German

532 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Within Admin - Catalog, when 12-1XFZXT4 12-1XFZXSB 8.1.1.3


users select the KB category and
click the Smart Answer
Synchronize button, they
receive an error message

After users click the Next button 12-1Y72XA6 12-1Y72X9F 8.1.1.3


on the last page of a script, and
then click the Finish/Finish Later
button, the application crashes

State Models
State Models with "No Delete" 12-1SK4YF1 12-1S5B2PJ 8.1.1.3
set do not allow UndoRecord and
cause an error

System Operation &


Diagnostics
A Siebel Gateway memory leak 12-1UI8B4J 12-1U5V32T 8.1.1.3
occurs with the DataDirect
ODBC driver on the AIX platform

Stress-testing Web services on 12-1UK0UG9 12-1TVDWRD 8.1.1.3


Unix causes communications
failures

The delete confirmation dialog 12-1VM9XBG 12-1VM9XAP 8.1.1.3


box prompt displays incorrectly

When the system tries to write 12-1VR55QL 12-1VM6N8P 8.1.1.3


log files or FDRs larger than 2GB
to the Linux filesystem, a crash
occurs

Within the LS Pharma 12- 12-1WF6PLV 8.1.1.3


Promotional Items Dropped list 1WWY5NH
applet, when users click Add, no
data appears on the popup
applet, and the Object Manager
crashes

Task UI
Validation of a Transient 12-1QFPEOP 12-1PPACL7 8.1.1.3
Business Component does not
function correctly

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 53 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

When users attempt to activate 12- 12-1U5VI79 8.1.1.3


a TBUI task within Siebel Tools 1VR5WGT
when the language is set to JPN,
an error may occur to indicate
that the value is too long for the
current field

After QF4703 has been applied, 12-1X3PA99 12-1WTJXVV 8.1.1.3


the Siebel client may hang
indefinitely when an invalid
account type is entered in a
TBUI task

Tools/Configuration
If script that raises an error 12-1QR9AYR 12-1PLG9OF 8.1.1.3
using RaiseErrorText is placed in
the WebApplet_Load event of
some applets, the error is not
displayed, but the entire script is
displayed

Querying against the "Client - 12- 12-1NSKPIL 8.1.1.3


Mobile" business component 1OEM3OM
fails

The BACKSPACE key does not 12-1R1VXR7 12-1Q71PG5 8.1.1.3


work in the Association applet

Attempting to pick a database 12-1TK6TMD 12-1TK5I7B 8.1.1.3 Yes, see


column for a business “Instructions for
component field in 8.0.0.7 FR 12-1TK6TMD”
causes an SQL error on page 708.

External business component 12-1U5TVBL 12-1GXKO5H 8.1.1.3


joins cause Object Manager
errors

Object Manager crashes when 12-1YJP5VU 12-1OQDGRJ 8.1.1.3


trying to run the
ValidateBuscompCalcExprs
method

Upgrade
ACR 529: Provides a single-step 12-1T5W181 12-1SW8HKB 8.1.1.3
upgrade from Siebel Enterprise
Applications to Siebel Industry
Applications

534 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Web Framework
The ShowPopup method cannot 12- 12-1VH3RNJ 8.1.1.3
be invoked by a keyboard 1VM6NOB
accelerator

Workflow
Workflow Simulator crashes at 12-1RKM7V7 12-1ISLMDM 8.1.1.3
the LoadInstance (RCOIS BS)
step

Names with spaces get lost 12-1SFPEXO 12-1IBWHCH 8.1.1.3


when concurrent tasks are run
on the same MT Server

When an exception branch leads 12-1VM96AX 12-1VCQVAZ 8.1.1.3


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

Workflow process on the 12-1VMA5PJ 12-1VEOU89 8.1.1.3


SetFieldValue event are not
working correctly

Submitting orders through 12- 12-1UI7QYZ 8.1.1.3


workflow processes causes 1VR3C6W
runtime errors, and the orders
have to be reset to Pending
status in order to be able to be
resubmitted

After QF0119 has been applied, 12- 12-1WA5CGZ 8.1.1.3


some steps in workflow 1WHMZ4P
processes display errors about
steps without providing detailed
information about what the error
is

After QF0119 has been installed, 12- 12-1WF6G1R 8.1.1.3


custom error messages do not 1WHMZ5N
display for Stop steps in
workflow processes

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 53 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

When a workflow is revised and 12-1WVIPO5 12-1VR789D 8.1.1.3


then deployed and activated
using the Publish/Activate
button, Workflow Process
Manager does not recognize the
revised version.

Runtime error messages contain 12-1X8QYGX 12-1X65TKV 8.1.1.3


insufficient information

iHelp
Other
In Siebel applications version 12-1N1KTE0 12-1L1J856 8.1.1.3 Yes, see
8.0, the New button is not “Instructions for
highlighted FR 12-1N1KTE0”
on page 708.

Life Sciences
Activity
Samples do not display when 12- 12-1VR4BT3 8.1.1.3 Yes, see
using the Inventory field, the Lot 1WWY5P4 “Instructions for
# Tracking field, and the FR 12-1WWY5P4”
Inventory by Lot field on page 706.

Created activities do not appear 12- 12-1VR4BVB 8.1.1.3


in the calendar 1WXFSD8

Clinical Account
Profiles
ACR 539: Modified Protocol site 12-1Y901CQ 12-1Y901B7 8.1.1.3 Yes, see
addresses in the Siebel “Instructions for
application are not getting ACR 539” on
updated in Oracle Clinical page 361.

Clinical Manager
Applying an Activity Template 12-1VR3QRB 12-1VM8H57 8.1.1.3
across multiple sites does not
work properly

536 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

ACR 539: When the "LS Clinical 12-1VUZHHE 12-1VR6AOT 8.1.1.3


-ApplyTemplates Process"
workflow is run through
Workflow Process Manager, an
exception occurs

ACR 539: Visit Sequence does 12-1X1S0P0 12-1OOD149 8.1.1.3 Yes, see
not get copied over from the “Instructions for
Subject visit template ACR 539” on
page 361.

Clinical Profiles
ACR 539: When the 12- 12-1VR73HT 8.1.1.3 Yes, see
ApplyTemplate workflow is 1WB70O1 “Instructions for
triggered through the UI, ACR 539” on
refresh does not occur page 361.

ACR 539: Search Center should 12-1X1S02N 12-1X0BGMO 8.1.1.3 Yes, see
accept incoming ICDs from “Instructions for
Order to Cash and default only ACR 539” on
when the date is unavailable page 361.

ACR 539: The Primary Site 12-1X4OYJB 12-1WF73ZD 8.1.1.3 Yes, see
Address pick applet field accepts “Instructions for
arbitrary values ACR 539” on
page 361.

Modifies the Siebel Clinical 12- 12-1TK4DJP 8.1.1.3 Yes, see


product to support the Study, 1WB70MX “Instructions for
Subject, and Visit ACR 539” on
Synchronization Process page 361.
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)

The SWI LS Clinical Subject 12-1Y6LNZN 12-1Y54O9K 8.1.1.3 Yes, see


Inbound - Subject" workflow “Instructions for
does not work when the ACR 539” on
<clin:InformedConsentSignedD page 361.
ate></
clin:InformedConsentSignedDat
e> tag does not exist in the
WSDL

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 53 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

ACR 539: Incoming NULL ICDs 12-1Y6LO7Y 12-1Y54O8F 8.1.1.3 Yes, see
from Oracle Clinical update valid “Instructions for
existing ICDs for subjects in ACR 539” on
Siebel Clinical page 361.

ACR 539: The status of subjects 12-1Y8IUF9 12-1Y8IUEI 8.1.1.3 Yes, see
still displays as Screened after “Instructions for
the enrollment date has been ACR 539” on
entered page 361.

eMedEd
Adds electronic medical device 12-1X0TENB 12-1OJC7XR 8.1.1.3 Yes, see
reporting to the AECM module “Instructions for
(ACR 426). ACR 426” on
page 66.

ACR 426: After ACR 426 has 12-1Y3OEAS 12-1Y36V4H 8.1.1.3 Yes, see
been installed and configured, “Instructions for
the Transmit button is disabled ACR 426” on
page 66.

Medical Education
ACR 426: B2 values are not 12-1XF0LI1 12-1R851IL 8.1.1.3 Yes, see
displayed in XML “Instructions for
ACR 426” on
page 66.

Other
ACR 426: The flag for 12-1S987UE 12-1R8LVJT 8.1.1.3 Yes, see
Transmitted-Rejected does not “Instructions for
display ACR 426” on
page 66.

ACR 426: The Reg Report view 12- 12-1S99GKY 8.1.1.3 Yes, see
displays eMDR status for an RR 1U5D3W7 “Instructions for
that is not in the eMDR queue ACR 426” on
yet page 66.

ACR 426: When existing 12-1U5D3ZB 12-1SFOTGX 8.1.1.3 Yes, see


Regulatory Reports are “Instructions for
escalated to the eMDR queue ACR 426” on
after eMDR has been installed, page 66.
the Transmission Status & eMDR
Status fields for those records is
blank

538 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

ACR 426: Phone numbers of 12-1U5D45C 12-1TBJW6J 8.1.1.3 Yes, see


manufacturers or distributors do “Instructions for
not display in accordance with ACR 426” on
the XML path given page 66.

ACR 426: Manufacturer 12-1VNIPV7 12-1VKYUHX 8.1.1.3 Yes, see


telephone numbers are not “Instructions for
displayed in the (xxx) xxx-xxxx ACR 426” on
format page 66.

ACR 426: The FDA Status field is 12-1VNIQ18 12-1U5TKPH 8.1.1.3 Yes, see
not being updated correctly “Instructions for
ACR 426” on
page 66.

ACR 426: Manufacturer 12-1VNIQ4C 12-1U5U51Y 8.1.1.3 Yes, see


telephone numbers entered into “Instructions for
the screen are not displayed in ACR 426” on
the XML page 66.

ACR 426: It is not possible to 12-1VNJ2JW 12-1R8M1X4 8.1.1.3 Yes, see


trace the path for the fields in “Instructions for
XML ACR 426” on
page 66.

Within Site Management > 12-1XOOAJ7 12-1XOO8RJ 8.1.1.3


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

ACR 426: The eMDR LOV is 12-1XF0LCT 12-1R6NTLT 8.1.1.3 Yes, see
missing and there is a typo “Instructions for
within Accepted; LOV Type = ACR 426” on
LS_MED_RR_TRANS_SUB_STAT page 66.
US

ACR 426: The F10 values are not 12-1XF0LJ2 12-1R9TWH2 8.1.1.3 Yes, see
found in the path for patient “Instructions for
code in the XML, and the F11 ACR 426” on
values are not present in the page 66.
XML

ACR 426: Provides batch files for 12-1XF0LD4 12-1R6NTMI 8.1.1.3 Yes, see
importing .sif files and seed data “Instructions for
for ACR 426 and for ACR 372 as ACR 426” on
well page 66.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 53 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

ACR 426: When a record is 12-1XF0LE3 12-1R6NTPL 8.1.1.3 Yes, see


selected in the Siebel application “Instructions for
and the FDA sends an ACR 426” on
acknowledgement, the page 66.
Transmission status is not
updated

ACR 426: The F13 value is not 12-1XF0LG3 12-1R8LVMN 8.1.1.3 Yes, see
populated in the XML “Instructions for
ACR 426” on
page 66.

ACR426: The B1 Code for the AE 12-1XF0LH2 12-1R8LVO2 8.1.1.3 Yes, see
Drug event type is not displayed “Instructions for
in XML ACR 426” on
page 66.

ACR 426: If the Regulatory 12-1XF0LL7 12-1S0YLCP 8.1.1.3 Yes, see


Report View already contains “Instructions for
records of type 3500A, when ACR 426” on
eMDR patch is applied, the same page 66.
records cannot be transmitted
because the Transmit button is
disabled

ACR426: If multiple 12-1XF0LN5 12-1S0YLFX 8.1.1.3 Yes, see


Concomitant Product codes are “Instructions for
selected, the corresponding ACR 426” on
values are not displayed page 66.

Site Management: Users receive 12-1XONPTL 12-1XIE5IH 8.1.1.3


an error message when
selecting an account to create a
new site

Assigning/Autodelete 12-1YDETC0 12-1XYC96B 8.1.1.3 Yes, see


functionality for Team members “Instructions for
does not work as expected FR 12-1YDETC0”
on page 703.

Within Call Activity, when users 12-1YJ865O 12-1YIQ3XG 8.1.1.3


create a new call, and then click
the Add button in the Sample
Drop applet, they receive an
error message

Pharma Handheld for


Windows

540 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

The Busy icon is sometimes not 12- 12-1V6XL7R 8.1.1.3


cleared even though the 1WXFSAM
application is ready for the next
steps

Protocol Builder
Users are unable to apply a new 12-1TQTU4C 12-1NWCZ7B 8.1.1.3 Yes, see
subject visit template in order to “Instructions for
create subject visits. FR 12-1TQTU4C”
on page 702.

Regulatory Reports
Adds electronic medical device 12-1U5D3P7 12-1U0ASU4 8.1.1.3 Yes, see
reporting to the AECM module “Instructions for
(ACR 426) ACR 426” on
page 66.

Trip Reports
In the Trip Report Details view, 12-1VR2857 12-1UIB7XV 8.1.1.3
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

Loyalty
Loyalty Customer
Portal
An error occurs while generating 12-1VR4PXA 12-1VMCEM9 8.1.1.3
statements for post-paid
partners

Loyalty Engine
When the LOY Batch Enrollment 12-1VM86N5 12-1VM72OT 8.1.1.3
Service is used, cursors are not
being released

Enrollment Web services fail 12-1VMA8YH 12-1VE7EH7 8.1.1.3


when the number of concurrent
users is above 30

Accrual Template Validation on 12-1WAYNKL 12-1VMAEXZ 8.1.1.3


using Workflow/EAI Adapter

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 54 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

The Loyalty Batch Engine task 12-1WF753R 12-1VROIM3 8.1.1.3


exits with Error ORA-01000:
maximum open cursors
exceeded

Custom Attributes are not 12- 12-1WF6P3J 8.1.1.3


recalculated correctly 1WLU9WG

There is no user property to 12-1WVIKCQ 12-1WVIKB5 8.1.1.3 Yes, see


control point expiry based on “Instructions for
transaction date instead of the FR 12-1WVIKCQ”
processing date on page 702.

The Redemption Services Get 12-1X65TII 12-1WXX8FJ 8.1.1.3


Quote method crashes

Loyalty Manager
The Voucher validity business 12-1VMBCJG 12-1VMAXQF 8.1.1.3
service does not return a failed
verification when a voucher is
used or expired

Marketing
Campaigns
Stage Execution fails with the 12-1SX7SLV 12-1STTN3F 8.1.1.3
error that the record has been
modified by another user

List Import of the Prospect 12-1VM5JXR 12-1VCQAE7 8.1.1.3


object on Siebel 8.1.1 exhibits a
memory leak on the Workflow
Process Manager component

Deleted segments and segment 12-1VM7HXI 12-1VM7HW1 8.1.1.3


trees are still being used in
allocations

Wave Numbers are not assigned 12- 12-1VMC9ID 8.1.1.3 Yes, see
to Control Group records 1WUJ5W5 “Instructions for
FR 12-1WUJ5W5”
on page 702.

Campaign launch fails 12-1XSJLCF 12-1XSJLAV 8.1.1.3

Email and Web


Marketing

542 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Database cursors left open after 12-1OK5WI5 12-1MM7CTD 8.1.1.3


launching email campaigns can
result in "ORA-1000" errors

The Test Email feature does not 12-1VOEV3S 12-1VNJHQ0 8.1.1.3


use the delivery profile of the
email treatment

Saving the HTML template for an 12-1WF61M1 12-1W4M5S2 8.1.1.3


email treatment incorrectly
modifies links that include the
<style> attribute

Saving the HTML template for an 12-1WVI96L 12-1W4M5R5 8.1.1.3


email treatment incorrectly
modifies links that include target
information

Marketing Server
Campaign load rejects some 12- 12-1RVO17F 8.1.1.3
rows as errors if same contact is 1SSCMNU
targeted with more than one
treatment

Repeating list import jobs try to 12-1UZ5H5D 12-1UU5KV9 8.1.1.3


repeat with the same start date
as previous job

List Import Exception Files do 12-1V6XLVX 12-1UJQNRZ 8.1.1.3


not provide business-user-
friendly error messages

Allocation of internal lists across 12-1VHLD6X 12-1V7WVM7 8.1.1.3


multiple treatments in a single
row yields the wrong results

Users are unable to create a lead 12-1VR2F30 12-1VH3RCZ 8.1.1.3


with a prospect using the default
Siebel 8.1 LeadService
:CreateLead Web

Token numbers are not 12-1VR3DQV 12-1VMBTV1 8.1.1.3


generated correctly when Allow
Repeated Contacts Within Load
is checked

List Import does not allow you to 12-1XPMR57 12-1XCM9RR 8.1.1.3


select an existing mapping

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 54 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Other
A lead is still associated to a 12-1VM6EMK 12-1VM6ELV 8.1.1.3
prospect after the prospect is
promoted

The Lead Import process hangs 12-1WYVV8E 12-1WYVV7P 8.1.1.3


when there are exceptions in the
import file

Mobile Solutions
Handheld for Windows
Handheld PatchAgent fails when 12-1Q0MF5H 12-1PPAE9M 8.1.1.3
UserDefinedLang=Y and the
userstr.txt file exists on the PDA
device

After users perform a Full Sync 12-1RAJ8KY 12-1NG9XVD 8.1.1.3


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.

Handheld, Store-and-Forward 12-1VM5JWF 12-1VBATI1 8.1.1.3


messages on the PDA appear
only in ENU, regardless of the
the Siebel language on the PDA

Handheld: When an activity is 12-1VNJY2K 12-1VNJY1R 8.1.1.3


created using the calendar, the
PreDefault value for the Type
field is ignored

Within Handheld tree applets, 12-1VR5Q6M 12-1VMBHFJ 8.1.1.3


occasionally the context gets
lost

544 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

After the 7.8.2.13 Fix Pack has 12-1WVI1ZR 12-1WQNSKV 8.1.1.3


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

Handheld with VGA-style 12-1WXFSBX 12-1VNJH0Z 8.1.1.3


resolutions: Users cannot select
the time in the Calendar popup
window

Handheld daily calendar: when 12-1WXFSEJ 12-1WCP7ZT 8.1.1.3


users change the month or the
year in Date popup window, an
exception occurs

With Windows Mobile 6.1.4, the 12-1X46WK5 12-1X1S03V 8.1.1.3


Setting Filters drop-down list
does not open during
synchronization

Tree Applet Recursive 12-1XC6WS4 12-1U5VI4H 8.1.1.3


functionality does not work

Parent applets are not being 12-1XRK5TV 12-1XRK5SR 8.1.1.3


refreshed

When users perform the SMQ set 12-1XS220M 12-1XS21ZV 8.1.1.3


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

Other
Case Insensitivity and Accent 12-1Q06NYO 12-1JNWG6G 8.1.1.3
Insensitivity (CIAI) does not
work on the local database

Store-and-Forward
Messaging
Handheld, Store-and-Forward 12-1VMBFQI 12-1U5TD5N 8.1.1.3
messages on the PDA appear
only in ENU, regardless of the
Siebel language on the PDA

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 54 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

When QF0682 has been applied, 12-1VR24OB 12-1TK9JRL 8.1.1.3


when the Handheld Object
Manager is unavailable, SMQ
messages are lost

Partner
Relationship
Management
Partner Manager
After users register a partner, no 12-1X668T1 12-1WF6FQC 8.1.1.3
records display in the Qualified
Partners view

Public Sector
Other
After an application has been 12-1Y5OQS8 12-1Y5MGFN 8.1.1.3
submitted, the Upload button is
still enabled

Section 508/
Accessibility
ACR 562: Provides Accessibility 12-1WU188L 12-1W6DOPP 8.1.1.3 Yes, see
enhancements for Siebel version “Instructions for
8.1.1.x applications. ACR 562” on
page 387.
For more detailed information
about what ACR 562 provides,
see “Enhancements and Updates
in Version 8.1.1.3” on page 33.

Sales
Forecasting

546 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

When users apply ACR 448, 12-1S0YV7A 12-1RXL8ET 8.1.1.3


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

Supports the Spreadsheet view 12-1S6AJ9P 12-1M5CV1E 8.1.1.3


under the Summary tab

In the Forecast Series 12-1XCLVSZ 12-1X3PRS9 8.1.1.3


Organization view, if
participants are not added, the
functionality does not work

After QF0215 or QF0173 has 12-1XRKN34 12-1XRKN1L 8.1.1.3


been applied, forecast
generation takes longer than
expected

Opportunities
Numeric and picklist fields 12-1XIVK5N 12-1JD9K31 8.1.1.3
temporarily blank out after
Siebel 7.7.2.8 has been applied

Service
Contracts
Auto entitlements does not 12-1SZMNL2 12-1RPRACV 8.1.1.3
apply the template information
to all line items

Other
Within eService > Advanced 12-1VR5LU1 12-1VMAF2Z 8.1.1.3
Search, searching with the All
option does not work

Within the eSales application > 12-1VR7KJC 12-1HWWAY4 8.1.1.3


OSES > the Results per Page
preference does not work when
it is set as 15, 20, or 25

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 54 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

The hour unit does not work for 12-1X65BT0 12-1WXXADT 8.1.1.3
any start time for the
GetElapsed method

Preventive
Maintenance
The Preventive Maintenance 12-1VBATMM 12-1TAR4ZP 8.1.1.3
Engine crashes

Scheduling
The "Load ABS" function does 12-1U5RX6U 12-1REV4NL 8.1.1.3
not work correctly right after the
Siebel Server service has been
restarted

The Book Appointment Process 12-1VR7Q81 12-1V418SN 8.1.1.3


is terminated

Siebel eMail
Response
General
Provides an addtional output 12-1S1XENY 12-1JGY6HC 8.1.1.3
argument from the
CreateRequest method from the
Outbound Communications
Manager BS to return the
activity id of the outbound email
activity generated automatically
by the CreateRequest method

With Internet Explorer 7, when 12-1UIB3AO 12-1U0COUJ 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

The Communication Detail - 12-1XF0MTB 12-1X6681L 8.1.1.3


Response view is read-only

Siebel Self
Service eCommon
Miscellaneous

548 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Users cannot configure a CP in a 12-1Y55X9A 12-1Y55X7M 8.1.1.3


promotion

User Interface
Controls
Form Redirect uses POST as the 12-1QKI632 12-1O2IS17 8.1.1.3
default and not GET

When using script to set the 12- 12-1DNMXIW 8.1.1.3


properties of a control's label 1QMFHYW
using the SetLabelProperty
method and when navigating to
the Show More view, the
"Cannot bind to source" error
message is encountered

The Siebel PRINT function 12-1VABVRY 12-1UZO2A9 8.1.1.3


executes Javascript or other
code that is part of the data
being printed

Provides an option to either 12-1WYEFRX 12-5PSXQ8 8.1.1.3


suppress or display the leading
zero on telephone numbers

With Internet Explorer 8, the 12-1XANXNP 12-1X1AZAL 8.1.1.3


application hangs if a popup
window or MVG is invoked
multiple times

The Site Map and controls in the 12- 12-1XQLNN9 8.1.1.3


toolbars are not visible 1XQLNOO

Spell Check does not work 12-1YAH2YE 12-1XZBT2P 8.1.1.3

History/Back/Refresh
Thread bar navigation does not 12-1TJM5Y1 12-1NXS3RV 8.1.1.3
work when view names contain
special characters

Layout and Rendering


When users click F9 and open an 12-1N1L2OD 12-1LC1A2Z 8.1.1.3
email, the text that is copied and
pasted into the email window
gets truncated

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 54 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Declaring a regional phone 12- 12-1RAJ08L 8.1.1.3


number format does not work in 1S7PQSW
Siebel 8.0.0.5

Error messages in SI mode are 12-1UAGKY7 12-1U5SY53 8.1.1.3


written into the Siebel toolbar

When users press CTRL+N, a 12-1VR2MJO 12-1VM6N0D 8.1.1.3


new record is added, but the
focus remains on the last field
selected in the previous record

Vertical separator lines in list 12- 12-QND3G8 8.1.1.3 Yes, see


applets that appeared in Siebel 1VR5WEW “Instructions for
version 7.x applications do not FR 12-
display in version 8.0.x or 1VR5WEW” on
8.1.1.x applications page 701.

In version 8.1, users have to 12- 12-1VR5ZGB 8.1.1.3


click the Query button twice to 1WEE4BO
enter query mode

Other
The GetCalendarData method is 12-1QL06QH 12-1IHL5T5 8.1.1.3
missing a WHERE clause, so SQL
retrieves all of the activities in
the Activity HI Calendar applet

Random hangs and crashes 12- 12-1PVZS4R 8.1.1.3


occur when new sessions are 1WLUYOC
started

Popups/Pick Lists/
MVG/Shuttle
Using pick applets causes 12-1RXL8O6 12-1REVDKP 8.1.1.3
Internet Explorer 7 and Vista to
crash

When selecting two entries in a 12-1SCRGLU 12-1P81NOT 8.1.1.3


shuttle applet, nothing shows up
in the detail applet until the
record is saved

550 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

If no value is supplied for a 12-1SGSZN3 12-1RSS41H 8.1.1.3


required field, users receive an
error message, but even after
they have entered the required
information, the error message
continues to appear

Removing a required entry in an 12-1U5VCA3 12-1U4NF3F 8.1.1.3


MVG query applet causes crash

With Internet Explorer 7, when 12-1US5U9H 12-1SPYNHD 8.1.1.3


performing validations within
eScript, if an error message
occurs and users click anywhere
but on the error message, the
browser crashes

The Back button inside an error 12-1VUZHE0 12-1PT60C3 8.1.1.3


message popup in SI mode is
disabled

When SecureLogin=True and 12- 12-1V0593H 8.1.1.3


SecureBrowser=False, if users 1WAJZZW
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

Custom drilldowns do not work 12- 12-1W7XG07 8.1.1.3


on Universal Inbox Item List 1WLUVWX
Applet

With Internet Explorer 7 and 12- 12-1WQ5PN9 8.1.1.3


Internet Explorer 8, querying in 1WRMXID
list applets on picklist fields
causes queries to fail

CTRL+SHIFT+3 (Record Count) 12-1WVI24O 12-1VR4BF7 8.1.1.3


hangs upon display

When users click the Calculator 12-1X13K22 12-1VR78HP 8.1.1.3


icon, they receive the following
error message: "Error: Object
doesn't support this property or
method."

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 55 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 17. Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Keyboard accelerator does not 12-1VM6N6S 12-1VM6N67 8.1.1.3


work in standard interactivity
mode

Web Service
Other
The EAI UI Data Adapter service 12-1SSCIPY 12-1RAJ0I1 8.1.1.3
search specifications <> and <
operators do not work and
generate an XML parsing error

If a call to WS 12-1SX7TJO 12-1SJ54EF 8.1.1.3


WC_Opportunity_BS fails,
subsequent calls to other ports
at the same session fail

The SoapOperation %1 does not 12-1U5SP9R 12-1TYAWKZ 8.1.1.3


have either an input or output
SoapBody child.WSDL with input
header

The Type field is not mapped 12-1XS25LG 12-1XHF6N5 8.1.1.3


correctly in in the Product
Integration data map

Rule Ids that are unique 12-1XS25UX 12-1V32N5L 8.1.1.3


identifiers for compatibilty
records are not mapped in the
SWI Promotion data map

The List Price field is not being 12-1XS25VI 12-1UGQO8Z 8.1.1.3


updated in the Siebel UI because
it is not mapped in the Product
data map

The IO SWI Promotion Internal 12-1XS25VT 12-1VM8W85 8.1.1.3


to External data map is incorrect

The Pricing Commit Type and 12-1YM4QNJ 12-1XWWFPF 8.1.1.3


Dynamic Discount Method data
maps are not correct

Resolved Change Requests in the Siebel 8.1.1.2 Fix Pack


This topic is part of “Resolved Change Requests” on page 462.

552 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18 lists the Change Requests that were resolved in the 8.1.1.2 Fix Pack.

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Call Center
CTI
In Siebel 8.1.1, when users query 12-1U5RK5A 12-1TK4CEL 8.1.1.2
in a case-insensitive column, BI
Publisher report data does not
appear

The CCA Driver Transfer 12-1U5V6K0 12-1U0B3EH 8.1.1.2


command is disabled

The CTI toolbar hangs 12-1P90BO1 12-1OUTTE9 8.1.1.2

When the CTI Toolbar is enabled, 12-1RC0739 12-1QQ9XCT 8.1.1.2


sending SWE commands to
Internet Explorer causes Internet
Explorer to hang

When users update the Text Input 12-1TUEN5V 12-1ADDD6B 8.1.1.2


field by pasting in text with
CTRL+V but leave the mouse on
the Make Call button, the wrong
number is dialed

Other
Assignment Manager does not 12-1U0A7S1 12-1T12HUL 8.1.1.2
assign incidents

Assignment Manager sets the 12-1UXNSIN 12-1THO6BX 8.1.1.2


Service Request Assigned Date
(ASGN_DT) incorrectly

Drilling down on a Service 12-1RXY84H 12-1P56A4F 8.1.1.2


Request within search results
generates an error message

F9 Send Email with MS Outlook 12-1TDOU48 12-1SUB033 8.1.1.2


Integration – Siebel activity
created but instantly deleted

Object Manager crashes when 12-1UX5JI7 12-1UH87BR 8.1.1.2


indexing 1,000,000 employee
records

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 55 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Comm Media
Energy
Order Management
Accepting product 12-1TK8BL1 12-1TB8YRV 8.1.1.2 Yes, see
recommendations add wrong “Instructions for
product to quote or order. FR 12-1TK8BL1”
on page 717.

ACR 471: Users cannot disable 12-1TK3LQM 12-1THNL1J 8.1.1.2


the Promotion Automatch feature

Connectors/EAI
EAI Server
Components
Automatic relogin does not occur 12-1R3SFV9 12-1R1EH5L 8.1.1.2 Yes, see
for Stateless SessionType “Instructions for
FR 12-1R3SFV9”
on page 717.

When a customer creates an 12-1SN1XBS 12-1S7SIFT 8.1.1.2


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.
Please continue or ask your
systems administrator to check
your application configuration if
the problem persists.

EAI Object Manager returns a 12-1TD5M65 12-1T2IL37 8.1.1.2


"server busy" error message

Other
AnonUserPool requires SWSE 12-1TTL0L1 12-1TK6KJB 8.1.1.2
Server restart to recover from
Siebel EAI OM Component
outage.

554 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Empty XML elements are not 12-1SW8EBY 12-1SW8EB7 8.1.1.2


stripped from outbound
messages

Intermittent login issues occur 12-1VP4GAQ 12-1QJJ9VL 8.1.1.2


while connecting to EAI object
manager

Poor performance occurs when 12-1OOD0QL 12-1NZODFZ 8.1.1.2


XML Hierarchy Converter
processes escaped characters

The UTC Date Time Format for a 12-1V0NBIX 12-1OUCG3F 8.1.1.2


date field in the UI Data Web
Service does not match the
industry standard

VBC cache does not work for the 12-1TENTWD 12-1T6DMLW 8.1.1.2
CSSFABCVRec specialized class

Web Services sessions with 12-1U09JKK 12-1TENCIJ 8.1.1.2


SessionType=None are not closed
in Siebel Server

Consumer Sector
Handheld
Sync locks the application if there 12-1U0CC0E 12-1TYBGYE 8.1.1.2
has been a sync exception
because of an incomplete
transaction

Customer Order
Management
Configurator
<ListofLinkedItems> tag is not 12-1UI92KZ 12-1TXC3RL 8.1.1.2
working correctly in web services

GetCPInstance does not return 12-1TWTOV8 12-1SFPEAN 8.1.1.2


anything

If an attribute LOV domain is 12-1V3VLX3 12-1V0598R 8.1.1.2


updated, with values removed,
an error is encountered when
modifying the asset

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 55 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

On the AIX platform, the Ilog 12-1TG6EAP 12-1SG6A0Z 8.1.1.2


engine crashes for more than 500
child products and a single
constraint

Remote Configurator Object 12-1TK530Y 12-1S1FVNR 8.1.1.2


Manager hangs when customizing
complex products

There is no way to join the 12-1U5UH3L 12-1T7DG8H 8.1.1.2 Yes, see


Attribute ID stored at Quote Item “Instructions for
XA.ATTR_ID to S_VOD FR 12-1U5UH3L”
on page 718.

When users modify a price, the 12-1UIA0LH 12-1UI8TEV 8.1.1.2


currency symbol is lost

When users navigate outside of 12-1VM568P 12-1U8XCTD 8.1.1.2


Configurator without clicking
Done/Cancel, the application
crashes

Within the Web client, when child 12-1TK6P9Z 12-1T12HW9 8.1.1.2


and grandchild attributes are
configured through a product
hierarchy using a constraint
popup applet, the attributes are
rendered incorrectly

Order Management
A crash occurs in ABO cycles 12-1VM5GQ5 12-1VM5K43 8.1.1.2
when AutoMatch is called

ACR 457: Provides cross-network 12-1N22K2E 12-1MAMCSM 8.1.1.2 Yes, see


validation and cascade delete “Instructions for
enhancements for network ACR 457” on
ordering for Siebel Customer page 99.
Order Management for SIA

Cursors are not closed as 12-1OOE5F3 12-1ONEBTJ 8.1.1.2


expected when querying
specialized Business Components
like "Order Entry - Orders” and
"Order Entry - Line Items”

556 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

If an LOV value is removed from 12-1VH410I 12-1VH3J0H 8.1.1.2


the Attribute domain and the
component product containing
this attribute is unselected as
part of the ABO process, an error
is encountered

The constraint definition UI for 12-1UIA3G7 12-1TGOA5B 8.1.1.2


customizable products does not
work correctly

Other
Promotions: The default 12-1U0DJZN 12-1TUVZQ9 8.1.1.2 Yes, see
cardinality of a relationship in a “Instructions for
CP is ignored when it is 0. Any FR 12-1U0DJZN”
relationship default cardinality in on page 718.
a promotion greater than 0
works. This FR addresses the 0
default scenario.

The application crashes when 12-1R6O99P 12-1QR99W7 8.1.1.2


upsell/cross sell messages are
still queued

Pricer
Manual price overrides are lost 12-1TYSJWU 12-1T2J5H3 8.1.1.2
when quantities are changed
using rules

Data Quality
Deduplication
Functional anomalies are found 12-1UIB3HP 12-1TK6K87 8.1.1.2
within Data Quality Self-Service
Applications matching

Other
The batch data cleansing 12-1UHQ1IM 12-1R6NUCR 8.1.1.2
algorithm for UDQ is missing the
sdq_close_session call

General
Accounts

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 55 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Displaying a record in Print 12-1TK47ZP 12-1TK4BU1 8.1.1.2


Preview mode prints the record
three times

Application
Deployment Manager
Adds the ability to sequence 12-1VJIAVE 12-1QR8NKV 8.1.1.2
database deployment units in a
package

Users are unable to specify 12-1UI7XPK 12-1TK6KG9 8.1.1.2


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

When ADM is used for attribute 12-1U3KDHG 12-1SBRAKT 8.1.1.2


adjustment import, the values of
the fields are populated
incorrectly

Audit Trail
After FRA users upgrade to 8.1.1, 12-1TYSS6S 12-1TD6X31 8.1.1.2
the Audit Trail language remains
ENU

Users are unable to track DELETE 12-1SC3OC1 12-1R0X1G3 8.1.1.2


operations using Audit Trail on
the Account Business Component

When trying to merge two 12-1US5UEV 12-1UI7QQX 8.1.1.2


accounts, the Merge Record
process fails and yields an error
message

Within the Audit Trail screen, 12-1RBHPQ3 12-1PBVORR 8.1.1.2


when users query for the Id field,
they receive the "Invalid
operation when not executed"
error message

Business Rules

558 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Applet_ChangeFieldValue does 12-1UI9URN 12-1MSUXR3 8.1.1.2


not trigger for fields that only
display in Show More mode for
Internet Explorer 7

Exporting rule modules from the 12-1U5RUZN 12-1QMX8LP 8.1.1.2


Siebel user interfaces generates
a file that is not able to be
imported into another Siebel
instance

Calendar
If users make changes to a 12-1US5U74 12-1SFP9PD 8.1.1.2
calendar item on the HI Calendar
views and click the browser's
Back button, the changes are not
saved

On the LS Pharma HI Activity 12-1UK0V2R 12-1UGQKAX 8.1.1.2


Calendar View, when the user
switches from the contact list to
the activity list, the date is reset
to the current date rather than
that previously selected by the
user

The Siebel 8.1.1 SIA FRA popup 12-1U0DVDN 12-1U0BYHX 8.1.1.2


version of the calendar displays
Saturday (Samedi) incorrectly

When users create or edit a 12-1US5UC0 12-1T6T4CF 8.1.1.2


calendar item and then close the
brower with the "X" close button,
the record is not saved and an
error message appears

When users drag a contact record 12-1UIA8WC 12-1UGQK67 8.1.1.2


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

Correspondence

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 55 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Cursors exceeded during 12-1Q2558J 12-1PLH0GL 8.1.1.2


proposal generation when
multiple proposals are generated
during a single user session

Installation
On the Linux platform, URLs do 12-1WF6D7D 12-1WF6D6N 8.1.1.2
not come up after 8.1.1.1 SIA has
been applied on 8.1.1 SIA

Siebel Tools Online Help files 12-1SW89YF 12-1Q35A8A 8.1.1.2


were not updated for Siebel 8.1.1

Other
"Maximum open cursors" error 12-1TXT8PN 12-1T12H8N 8.1.1.2
received when generating large
number of Proposal drafts

Provides support for CRM 12- 12-1UWOAPI 8.1.1.2 Yes, see


Desktop for Outlook (ACR 464). 1UWOAQL “Instructions for
ACR 464” on
page 142.

Calling a business service method 12-1V9U8A5 12-1UX6FHT 8.1.1.2


written in Siebel Visual Basic
causes the error: SBL-DAT-00323
after the first invocation.

Deleting position for an employee 12-1U0CC80 12-1SNJLOF 8.1.1.2


using java data bean causes
runtime error

Incorrect repository object 12- 12-1TTI51Q 8.1.1.2


naming 1UWOARN

It is not possible to sync a contact 12-1VLGHMD 12-1UT7XJH 8.1.1.2


whose email address contains
more than fifty characters

Large temporary files created 12-1VM6K61 12-1OUD1RP 8.1.1.2


during EAI processing are not
always deleted

MakeFile.dep does not get 12-1UJQLUG 12-1UIAVXD 8.1.1.2


created when the flag
NoDepent=t is removed from the
makefile.dcl file

560 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Opening a pick applet fires the 12-1TK89IV 12-1T9B2VI 8.1.1.2


WriteRecord method on the
underlying business component

Querying for records in the 12-1TK9WIQ 12-1TDX57D 8.1.1.2


Inbound Calls applet causes a
memory leak

RaiseErrorText in the JPN 12-1VABKXZ 12-1TUED13 8.1.1.2


language appends a character to
the message box

Users are not able to apply 12-1TK92JL 12-1T135UF 8.1.1.2


different view modes to parent or
child integration components of
an integration object

Users cannot deassociate 12- 12-1V6FUML 8.1.1.2


multiple association records in an 1VCQUHG
MVG at the same time

With 8.0.0.6 QF1605 installed, 12-1UI92G1 12-1U5TMPJ 8.1.1.2


when users query within the top
applet of the Contact Detail View
(within Contacts Screen
>Activities), the application
crashes

With the Siebel 8.0.0.3 Fix Pack, 12-1SSUR6E 12-1SM2KAX 8.1.1.2


runtime errors occur because of
the ST eScript engine

Performance
Double parsing without bind peek 12-1ORCIOH 12-1OQD0BB 8.1.1.2
in Oracle Connector causes
performance degradation

Personalization
If an association applet is 12-1TK8BFY 12-1THO6OP 8.1.1.2
assigned a rule set for
personalization that uses an
include expression to act as a
search specification, the include
expression is ignored

PIM Server Integration

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 56 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Add-in does not respect "PIMSI 12-1U5RVL3 12-1U5RIY5 8.1.1.2


Category" setting

After users apply the Outlook 12-1TQNB3M 12-1TK9Z8J 8.1.1.2


Addin Quick Fix to support SSO
(8.0.0.3[20416] - QF[0347] )
their passwords are overwritten

Attendees are not properly 12-1UI7XSW 12-1UGR5SJ 8.1.1.2


synched when there is a
combination of sync-enabled and
non-sync invitees

Outlook Add-in fails on non- 12-1TK4K9Y 12-1TBJVXL 8.1.1.2


Windows servers

Outlook Add-in illustrates 12-1R84XM5 12-1QXJF7Z 8.1.1.2


incorrect behavior with SSO
enabled

Outlook Add-in Toolbar 12-1UI8TXL 12-1U0B955 8.1.1.2


disappears

The SSSE engine crashes when 12-1UAFDX6 12-1T6T4DJ 8.1.1.2


QF8501 is installed on top of
QF0581

The SSSE Outlook Add-in sorts 12-1VI15ZT 12-1UH87KX 8.1.1.2


incorrectly when searching in the
Link dialog box

Valid Category value overwritten 12-1TH5KDI 12-1RW60U6 8.1.1.2


by default

Remote
ACR 544: Enhances the Siebel 12-1UZ5TVC 12-1SW8HHD 8.1.1.2
Remote utility and allows it to be
intergrated with the Siebel HA
Upgrade solution

After a failed database 12-1UJQTMH 12-1U5RF2V 8.1.1.2


initialization, users can cancel,
and then log in again and add
data, but the synchronization to
the server fails, and the data is
lost

Lock on S_DOCK_SESSION with 12-1RV74GM 12-1QXJVFB 8.1.1.2


MS SQL Server 2005

562 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

On the Tablet PC device, when 12- 12-1NALW8B 8.1.1.2


Quick Start is enabled, when 1PCUMWS
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

Quick start not working using 12-1THNI2Z 12-1QKIPCK 8.1.1.2


non-admin user on Win XP and
Vista

SynchMgr does not close file 12-1U5SIB2 12-1U08IXL 8.1.1.2


handles for dropped sessions, so
when a user whose session has
been dropped attempts a new
session, another file handle is
used

The apply_thrd function fails with 12-1T7DDJT 12-1SZLZ9R 8.1.1.2


the Index 'S_EVT_ACT_X_U1' for
table 'S_EVT_ACT_X' would not
be unique" error

The Help button on the 12-1TK3QXJ 12-1JAR0YF 8.1.1.2


Synchronization window does not
work

The Siebel application crashes 12-1V3JRDF 12-1U4I7Q5 8.1.1.2


when it is opened twice using
Quick Start

Transaction Merger fails because 12-1PKZD0S 12-1NWLI7J 8.1.1.2


single byte ROW_ID is duplicated

Under heavy routing conditions 12-1SING9C 12-1RPD2ML 8.1.1.2


(such as with EIM) and large
remote environments (over 400
users), after some time of
working normally, multiple
Txnrouter tasks fail with errors

Within the txnmerge log file, 12-1UK0UHZ 12-1TUWRGV 8.1.1.2


pTableName is NULL or empty

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 56 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

After users create a report and 12-1WLUFQ1 12-1WLUFOF 8.1.1.2


associate it to a view, the report
does not show up in the BIP
Reports drop-down menu

Search
ACR 439: Search Center does not 12-1P1OP6D 12-1NZODJL 8.1.1.2
remember terms and results after
it has been closed

ACR 439: When users search, the 12-1P1OPJ6 12-1OQU6GN 8.1.1.2


Field Name is used rather than
the Field Display name

After indexing certain business 12-1UIAGQE 12-1RKLPVN 8.1.1.2


components for mobile search,
the datasource is shown as
"buscomp".

Binocular Search does not work 12-1U09BK1 12-1NZO98B 8.1.1.2


with special characters

Binocular search yields the 12-1U0CXZG 12-1S7PQXV 8.1.1.2


previous search's data when
users do not enter the search
criteria a second time

Drilling down on a Service 12-1RXY84H 12-1P56A4F 8.1.1.2


Request within search results
generates an error message

For Search, the Context 12-1SXP5U8 12-1S8Q8CN 8.1.1.2


Sensitivity preference does not
work when invoked from the
Opportunity, Solutions, or
Literature screens

Incremental indexing with OSES 12-1U0D4B3 12-1T6T4GB 8.1.1.2 Yes, see


does not work for SR, Contact, “Instructions for
Account FR 12-1U0D4B3”
on page 719.

OSES- Search: Simultaneous 12- 12-1HTFNR3 8.1.1.2


incremental indexing results in 1RXL8MW
leaving some newly created
records

OSES: Records Visibility in OSES 12-1SC8YE5 12-1QV5WFV 8.1.1.2


for an eService user

564 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

OSES: Schedule ID parameter in 12-1TAA6HJ 12-1SJ5C83 8.1.1.2


Engine Settings

Search: When users try to index 12-1RYK4D8 12-1QR8N6F 8.1.1.2


a category for a Business
Component that has a begin
parenthesis in the name, they
receive the following error
message: SBL-DAT-00222: An
error has occurred creating
business component '<?>' used
by business object '<?>'.

The "Look In" drop-down list still 12- 12-1NVVH4J 8.1.1.2


contains values even after those 1NZQW39
values have been removed from
the user's responsibilities

When a Search Category is 12-1QH55SS 12-1OVCU5D 8.1.1.2


indexed, the old indexes are not
removed

When advanced search is 12-1V7WJSN 12-1V7F8AT 8.1.1.2


performed, search results from
multiple search categories based
on the same BC are displayed
even if only one category was
selected.

When Search Center is opened 12-1S7SIQX 12-1S0YDZ5 8.1.1.2


from within CTI, users cannot use
Enter for submitting FIND criteria

When users enter special 12-1TK6OSU 12-1RV73Z9 8.1.1.2


characters, the FIND feature does
not fetch results with the correct
criteria

ACR 452: When users run a blank 12-1U5V2FD 12-1U5V2EN 8.1.1.2


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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 56 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

After users have set Context- 12-1TDNZTL 12-1QXJYZI 8.1.1.2


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

Drilling down on keywords does 12-1VGM8F2 12-1VD87WA 8.1.1.2


not refine the results

Queries show + instead of AND 12-1VGM8I5 12-1VGM8AG 8.1.1.2


when users drill down on
keywords

Users are unable to set the 12-1UJQSQT 12-1UJQSQ1 8.1.1.2


default flag for search definitions

Security
SWEU parameter should ignore 12-1N22J3V 12-1IYN1VD 8.1.1.2
hostnames to prevent phishing

User can change their privileges 12-1UGR0BD 12-1U0CPDF 8.1.1.2


to that of another user (such as
an administrator) by entering a
Javascript command

Server Infrastructure
Addresses a problem with ACR 12-1QK1GVJ 12-1PLGZW1 8.1.1.2
405 where Dynamic MQ Reply
Queue does not work

Cannot add MLOV entry with 12-1V417JN 12-1R0X6NL 8.1.1.2


same display value, even when
LIC code is different

The Siebel application 12-1NTIUTF 12-1N3J0WN 8.1.1.2


experiences non-reproducible
random crashes

When users attempt to print, the 12-1N22LHT 12-1K51E4X 8.1.1.2


application fails and displays an
error message

Siebel Sync

566 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

ACR 468B: Allows Siebel Client 12-1UZNMA7 12-1S4ZI88 8.1.1.2 Yes, see
Sync to support Lotus Notes 8.0 “Instructions for
and Microsoft Outlook 2007 with ACR 468” on
Intellisync 7.x SDK. page 157.

After version 7.7.2.10 has been 12-1RBI3CD 12-1Q5L7W9 8.1.1.2


installed, the Lotus Notes Action
button disappears at the second
synchronization

PIMSI Dispatcher does not filter 12-1MQCB8J 12-1MIVDVK 8.1.1.2


by user group

SmartScripts
Smartscripts are causing Internet 12-1V0N8EM 12-1UQ62AL 8.1.1.2
Explorer to crash after installing
the 8.1.1.1 patch

System Operation &


Diagnostics
The Siebel 8.1.1 Gateway Server 12-1U5VCBL 12-1U5R7UV 8.1.1.2
crashes on Microsoft Cluster 2008

Task UI
Invoking the binocular search 12-1V7F9GQ 12-1V3JQI3 8.1.1.2
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

TBUI task statuses do not reflect 12-1TK7ABX 12-1TGO4RF 8.1.1.2


the correct values

The license key is missing for the 12-1TYSIXQ 12-1TK6LZT 8.1.1.2


Task Pane view in Siebel
Professional Edition (SPE) is not
available

Tools/Configuration
An error occurs with the global 12-1N1RBJY 12-1M81JE0 8.1.1.2
variable of type property set
initialization in the global section
of Business Services

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 56 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

NoRefreshOnDynamicTogg in 12-1TUEN4I 12-1TA9WD7 8.1.1.2


8.0.0.6 corrupts applets in Query
mode

Siebel Tools sessions end without 12-1U5SZNL 12-1TK9JCV 8.1.1.2


a warning or error message when
processing WSDL

Upgrade
The Symbolic String Conversion 12-1STTIXO 12-1SI5H61 8.1.1.2
utility (consoleapp.exe) fails in
Siebel 8.1.1

Web Framework
Exporting from browsers that are 12-1QTPRGH 12-1J1X6NA 8.1.1.2
running Windows 2000 SP1 or
Windows XP SP2 causes session
timeouts from Siebel 7.7.2.6
onwards

Workflow
Business services that do not 12-1SSCMJ3 12-1SBRA31 8.1.1.2
initialize and return Output
Arguments to workflow steps tat
are expecting them cause a
runtime error

Workflow processes edited in 12-1VM6SF3 12-1VK09JB 8.1.1.2


Siebel Tools fail to validate in
8.1.1.1

iHelp
Other
Related iHelp does not navigate 12-1SX7TI5 12-1SJ5MIZ 8.1.1.2
correctly

The title "Additional iHelp Topics" 12-1U0DSQ7 12-1TK4UOX 8.1.1.2


in the iHelp pane is not in the
local language

Life Sciences
Activity

568 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

A memory and cursor leak error 12-1UUNN76 12-1UGQKF3 8.1.1.2


message occurs when Smart Call
functionality is used

Users are unable to submit calls 12-1VKHIB7 12-1V6FY27 8.1.1.2


created on the current day from
Handheld

Clinical Manager
Position Rollup does not always 12-1VAT6K9 12-1OK0UBP 8.1.1.2
function properly

Trip report status does not 12-1UX5E8Z 12-1PCUB4Z 8.1.1.2


automatically change to In
Progress

Undo record in Clinical Trial 12-1UG9MN3 12-1U5RQB1 8.1.1.2


Report Detail View

Users cannot undo records after 12-1UU4KQ7 12-1P2RV9L 8.1.1.2


selecting a template in the Trip
Report Details view

Users are unable to copy Site 12-1V3K6BX 12-1K824E1 8.1.1.2 Yes, see
Vists records “Instructions for
FR 12-1V3K6BX”
on page 719.

Trip Reports
Users are unable to change the 12-1UVNYZX 12-1NVVH35 8.1.1.2 Yes, see
Trip Report Status field in the “Instructions for
Clinical Trip Report view FR 12-1UVNYZX”
on page 720.

Marketing
Campaigns
Prospect import does not check 12-1TK666M 12-1TK665T 8.1.1.2
for matches against existing
contacts

Prospect promotion on Leads 12-1UI92JW 12-1U4I7KV 8.1.1.2


screen gives error when matches
are ignored

Response import does not use all 12- 12-1UIB7Z9 8.1.1.2


selected Exact Match fields to 1UXNWE8
check for matches

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 56 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

When uers create a treatment 12-1TK96TH 12-1T7V4R7 8.1.1.2


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

While running the 'Response to 12-1UI8DMO 12-1UHPV6B 8.1.1.2


Lead' conversion, users receive a
maximum cursors error message

Within the Campaign Segment 12-1TK9WGJ 12-1TBLYYA 8.1.1.2


Allocation view, users are unable
to see lists created by other users

Email and Web


Marketing
After Siebel 8.1.1 QF0034 has 12-1UIB3EZ 12-1UI81Z5 8.1.1.2
been applied, when users edit
text email templates, the
changes they make disappear

Error messages appear when 12-1U0D8SV 12-1U0BPQZ 8.1.1.2


userse add URLs to an email
HTML body

Events
When users navigate to Site Map 12-1S2F1F1 12-1RRBFQ9 8.1.1.2
> 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

Marketing Server
Integration to Marketing 12-1TK47RK 12-1KJP2WG 8.1.1.2
Outbound Web Services does not
support enterprise SSO

Other

570 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

When users create a Landing 12-1TPUQJB 12-1TH5NV5 8.1.1.2


Site, add a footer within the Site
Details tab, navigate to the
Preview and Deploy tab, and click
Preview, the footer does not
display

Mobile Solutions
Handheld for Windows
During Handheld 12-1TXTR5T 12-1THO6UJ 8.1.1.2
synchronization, the logging of
URLs exposes username/
password combinations in web
server logs

For Handheld batch sync, the Exit 12-1VGMVZT 12-1U0CP6R 8.1.1.2


and Next buttons that were
available with Siebel version
7.5.x are not available in later
releases

In Handheld daily calendar, the 12-1VHL8BW 12-1UOF62N 8.1.1.2


calendar popup window for the
Date field corrupts the display
when resolution = VGA

PDA DSS Batchsync loses data if 12-1UZO7F7 12-1UH87ET 8.1.1.2


you select "Download" without
first uploading

The application hangs when the 12-1UG9MQI 12-1ROXJHT 8.1.1.2


barcode for the second item
listed in a picklist is scanned

When users attempt to run "12- 12-1RSS5V1 8.1.1.2


Companion Sync, they receive 1SWPT87
the following error message:
"Error detected while
communicating with the device

When users attempt to 12-1S9RUXX 12-1RVORD3 8.1.1.2


synchronize a PDA device with a
machine running Vista, the
synchronization fails

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 57 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

With WM5 and WM6 devices, 12-1SIO0R1 12-1SC9C45 8.1.1.2


when certain characters are
extracted into dbfile.txt, the
dbimport synchronization step
fails

Within the Handheld dbimport 12-1QL04RJ 12-1QFPJ7Z 8.1.1.2


logging file, information about
non-database-related steps such
as file creation or file deletion is
missing

Other
The DB_LAST_UPD and 12-1S1Y0MZ 12-1L0YDDK 8.1.1.2
DB_LAST_UPD_SRC columns are
listed twice in the update
statement

Store-and-Forward
Messaging
ACR 444 provides the following 12-1U087M8 12-1O2HQ4R 8.1.1.2
enhancements: Provides a utility
for administrators to act on
failing Store and Forward
transactions. Enhances logging
capabilities. (Server)

SMQReceiver component look at 12-1TKABND 12-1SI5H9N 8.1.1.2


all server requests and not just
those for which it is responsible.

The "SMQ Process User Queue" 12-1RRTKGX 12-1QR98KH 8.1.1.2


workflow can create duplicate
records in case of MQe problems

Users are unable to remove 12-1TGOAM3 12-1SFP9NP 8.1.1.2


reassigned messages

Sales
Other
Manually-created revenue items 12-1U0A7J0 12-1SW88FV 8.1.1.2
within accounts are not updated
when the account is changed by a
user who has not created the
revenue item

572 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Service
Logistic Manager
Error invoking service 'Inventory 12-1V7FE6F 12-1UH87R1 8.1.1.2
Transaction', method
'SetTxnDetailsFromTxnSet’

Siebel eMail
Response
General
For draft emails, the status can 12-1U5TWJC 12-1U5TWIL 8.1.1.2
be changed to any value and
contacts can be removed or
added

Siebel Automated Quote Approval 12-1T2SVQ5 12-1SSTZQV 8.1.1.2 Yes, see


Email not being sent “Instructions for
FR 12-1T2SVQ5”
on page 720.

When users are sending an 12-1TK99NV 12-1TK99KZ 8.1.1.2


outbound email, resolution
documents cannot be seen in the
Attachment field

When users send an outbound 12-1TYT3N8 12-1TZR995 8.1.1.2


email to duplicate email
accounts, duplicate emails are
received in the mail client

With templates, the subject line 12-1QK0UEL 12-1FCL4BH 8.1.1.2 Yes, see
and body text are not replaced “Instructions for
according to the template FR 12-1QK0UEL”
selected on page 720.

Siebel Self-Service
Common
Miscellaneous

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 57 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

The following error message 12-1TK4BEP 12-1R7V0XR 8.1.1.2 Yes, see


occurs when trying to invoke Web “Instructions for
services: "Error Code: 10944642 FR 12-1TK4BEP”
Error Message: Error: Inbound on page 721.
SOAP Message - Session Token is
missing or invalid or has expired”

Travel &
Transportation
Events Execution
ACR 494: Provides Event Check 12-1S9QL59 12-1S9QL3Z 8.1.1.2 Yes, see
enhancements and BEO Report “Instructions for
functionality for the Siebel Travel ACR 494” on
& Transportation application page 291.

Other
For ACR 450 and ACR 488, the 12-1UI8ZAR 12-1UI8Z9H 8.1.1.2
sia_options.txt file is missing
several views for licensing

Provides more technical content 12-1T6VXUH 12-1T6VXSP 8.1.1.2


for the Travel and Transportation
application error messages

Selecting the output type as ALL 12-1WIXYWB 12-1WIXYVR 8.1.1.2


for Report Name in
Administration > BIP Report
does not work as expected

When users click on the 12-1V41X13 12-1V41X0M 8.1.1.2


Functional Space Diary, they
receive an error message

User Interface
Administration
Successful login does not reset 12-1UQU5DX 12-1U5V2WZ 8.1.1.2
IsStandaloneWebClient Profile
Attribute

Controls
After 8.1.1 QF0025 has been 12-1UW60LO 12-1UI8T7X 8.1.1.2
applied, the implicit save function
does not work on form applets

574 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

Browser script causes error 12-1V421BE 12-1QPSY8J 8.1.1.2


message on picklist auto-
selection

IE crash when triggering 12-1UGR21U 12-1U0866H 8.1.1.2


Smartscript from client-side
script

Provides the ability to 12-1UGQZS5 12-IVNITD 8.1.1.2


programmatically suppress error
messages

Translated error messages have 12-1VHLBL9 12-1NSKL0N 8.1.1.2


extra Japanese characters in
them

UI shows only 32K of data 12-1UFAJ40 12-1RHR0N1 8.1.1.2


onscreen from CLOB field

Users should be able to query on 12-1O7OFOV 12-OM5V6D 8.1.1.2


fields in a view even if the Read
Only View flag is set to TRUE

With Internet Explorer 7, Siebel 12-1QKI678 12-1PE98Y5 8.1.1.2


Calendar crashes, hangs, does
not load, or fails with a script
error

With Internet Explorer 7, the 12- 12-1PE98W7 8.1.1.2


Siebel Calendar control does not 1QNW677
work

Layout and Rendering


When using run-time events and 12-1QQACIH 12-1NVVH71 8.1.1.2
personalization rules to drive
toggle applet selection, the first
time that the toggle applet
displays results in an incomplete
display

Navigation
If users enter a query of more 12-1SC96YJ 12-1OA585D 8.1.1.2
than two characters, when they
press the TAB key, the focus does
not move to the GO button

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 57 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

New query in child form applet 12-1U0A7PV 12-1TGO4VB 8.1.1.2


does not switch from edit to
query mode

When the Immediate Post 12-1VM6K6Y 12-1O6OCKJ 8.1.1.2


Change property has been set, a
second click is required to
navigate

With Internet Explorer 7, 12-1SC96ZD 12-1ME9N7W 8.1.1.2


navigating to the next applet
without completing the required
fields causes an endless loop

Other
Exporting results from queries 12-1V3VLLZ 12-1UU5KSH 8.1.1.2
that use calculated fields omits
valid records

Launching a TBUI Task while it is 12-1RZ1P11 12-1RQUGN3 8.1.1.2


running and then opening Search
Center (using the binoculars
icon) may cause the application
to hang and an error message to
appear

Quickprint of a toggle applet 12-1SCQKBZ 12-1L3YVPO 8.1.1.2


prints the record twice

Refine query on Account team 12-1TG65R2 12-1TG65Q3 8.1.1.2


generates error message

'Select Field' string for Query 12-1U0BDIC 12-1U0A9KV 8.1.1.2


Assistant is not translated

Using Query Assistant for LOV "12- 12-1UI8QNP 8.1.1.2


entry gives error "The value 1VKHWBE
entered in Field does not match
any value in the bounded picklist

Popups/Pick Lists/
MVG/Shuttle
Internet Explorer 7 crashes when 12-1UI7VQC 12-1UGQKML 8.1.1.2
users open a popup window on
top of an MVG

Minimize/restore window with 12-1TYSS1V 12-1QBCC2R 8.1.1.2


unsaved changes causes IE crash

576 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 18. Resolved Change Requests in the 8.1.1.2 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Changes

When a toggle applet is 12- 12-1S8Q8EL 8.1.1.2


configured, running a query by 1VM6K4W
hitting the Enter key causes the
application to crash

With Internet Explorer 7, when 12-1S9RBEG 12-1S1FXNF 8.1.1.2


users close a popup window using
the X, the application hangs

Web Service
Other
Provides Web service access 12- 12-1STBMTB 8.1.1.2
through the Mobile Web Client to 1STBMWW
other local desktop applications
(ACR 492)

The "all" XSD element is treated 12-1TK86GJ 12-1STC0UB 8.1.1.2


as sequence

The EAI UI Data Adapter does not 12-1TK5S8P 12-1TK4C5P 8.1.1.2


work for paging child integration
components

The Impersonate feature does 12-1U09CUR 12-1TYAWK5 8.1.1.2


not consider time zones

Resolved Change Requests in the Siebel 8.1.1.1 Fix Pack


This topic is part of “Resolved Change Requests” on page 462.

Table 19 lists the Change Requests that were resolved in the 8.1.1.1 Fix Pack.

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Call Center
CTI
The Chat transfer command 12-1S99AEF 12-1S99ADV 8.1.1.1
defined in multichannelC.def is
incorrect

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 57 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Accessiblity: CTI does not take 12-1RV6IUZ 12-1ME9KRG 8.1.1.1


any input from the toolbar
editbox after the application has
been converted for Section 508
compliance

Accessibility: After CTI has been 12-1RV6IUP 12-1MEBPT5 8.1.1.1


configured for Section 508
compliance, the screen reader
reads every underlying
command for CTI controls from
the CTI toolbar

Within CCA, when an invalid 12-1R8MHX2 12-1PJ2S1Z 8.1.1.1


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

When two driver profiles have 12-1R6NUYJ 12-1R58N93 8.1.1.1


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 C

Provides Hoteling-Hotdesking 12-1QXO3LS 12-1QK0QNF 8.1.1.1


support for Call Center
Anywhere

When there are multiple CCA 12- 12-1QDA9FX 8.1.1.1


driver instances running, users 1QTPMTW
receive the "Could not find the
matched SVC for session..."
error message

CCA: If the "MaxAgentNumber" 12-1QTPMTH 12-1QBCUYH 8.1.1.1


parameter does not exist, a new
login creates a new driver
instance

578 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Updates CRM Chat to use the 12-1QR9BRG 12-1Q2MZRN 8.1.1.1


latest Java file content

When users create two 12-1NQ7VT4 12-1NKJF4T 8.1.1.1


simultaneous outbound
requests, the requests hang and
CommOutboundMgr logs show
errors SBL-CMO-00169 and SBL-
SRM-053021

Other
Redesigns the Email Response UI 12-1RB07UI 12-1RB07T9 8.1.1.1 Yes, see
so that replying to an incoming “Instructions for
email and forwarding a sent FR 12-1RB07UI”
email display in the same format on page 733.

With the Find feature, when 12-1RA1T6W 12-1QNWAIL 8.1.1.1


values have special characters,
records are not returned in the
Destination Results view

The CCA Driver does not retrieve 12-1QQ9XSR 12-1QUOFMN 8.1.1.1


all of the records in the CCA
library

After 8.0 [20405] QF1009 has 12-1QR8PCO 12-1LSX5J6 8.1.1.1


been applied, spell check does
not work on Linux servers

Users receive the SBL-DAT- 12-1QL05SF 12-1Q9I2QJ 8.1.1.1


00457 error message when
searching on a Multi Value Field
that is mapped to another Multi
Value Field

Comm Media
Energy
Order Management

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 57 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 471: If headless 12-1SZ4WPA 12-1SXN45J 8.1.1.1


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

Within the Sales Order screen, 12-1S1Y0R1 12-1R75AA5 8.1.1.1


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

Other
Users are unable to add a 12-1O05GRF 12-1M6UUMK 8.1.1.1
promotion to the Shopping Cart
with default options selected

Connectors / EAI
Other
All messages sent to JMS go as 12-1SBSPDP 12-1RAJ07R 8.1.1.1
BytesMessage, regardless of
whether the data is String/
Binary

After 8.0.0.5 QF506 has been 12-1RGSQ98 12-1R0X6P9 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

580 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Object Manager tasks are not 12-1QUOILO 12-1OI2RO5 8.1.1.1


reused when a Siebel exception
occurs using JCA/Siebel
Resource Adapter

When setting 12-1Q3NJU1 12-1JZ28HA 8.1.1.1


HDR.connection=close on some
W eb servers, response is
delayed

The EAI Data Transformation 12-1N1QM7X 12-1MNQ3BZ 8.1.1.1


Engine outputs the target
instance when the source search
specification is not met

Consumer Sector
Deductions
ACR 480: Claim Resolution time 12-1SPXYJS 12-1SPXYHT 8.1.1.1 Yes, see
value changes after the record is “Instructions for
refreshed ACR 480” on
page 280.

Other
When users create a new plan, 12-1TXTRDT 12-1TXTR4J 8.1.1.1
the application crashes

ACR 480: Delist dates are not 12-1TSQ0BX 12-1TSQ0AH 8.1.1.1 Yes, see
being updated in the ADL applet “Instructions for
FR 12-1TSQ0BX”
on page 734.

Improves the quality of the 12-1TGNFMK 12-1TGNFL1 8.1.1.1


Consumer Sector application
error messages

ACR 480: Provides translations 12-1TG5FLS 12-1TG5FKD 8.1.1.1 Yes, see


for error messages related to “Instructions for
ACR 480 ACR 480” on
page 280.

ACR 480: The Seed.inp file is 12-1TAR916 12-1T9S0ZN 8.1.1.1 Yes, see
missing for seed data import on “Instructions for
JPN ACR 480” on
page 280.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 58 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Improves the quality of 12-1T6VXL6 12-1T6VXJQ 8.1.1.1


Consumer Sector application
error messages

ACR 480: Flags (A/O/P) should 12-1SOZJYK 12-1SOZJUX 8.1.1.1 Yes, see
retain their values if the Account “Instructions for
Distribution record exists (ADL) ACR 480” on
page 280.

ACR480: Users are unable to 12-1SN1W5R 12-1SN1W4H 8.1.1.1


import seed_locale_JPN.dat for
LOV seed data

Consumer Sector error message 12-1SJ5WTI 12-1SJ5WS3 8.1.1.1


content is not useful

Improves the quality of 12-1SF7RMM 12-1SF7RL9 8.1.1.1


Consumer Sector error
messages

ACR 480: Users are able to save 12-1S87KF6 12-1S87KDR 8.1.1.1 Yes, see
Delist date > Product end date “Instructions for
in Authorized Category Product ACR 480” on
(ADL), but they should receive page 280.
an error message and be
preventing from doing this

ACR 480: List Date and Delist 12-1S87KBC 12-1S87K9X 8.1.1.1 Yes, see
date do not get updated in the “Instructions for
Authorized Categories Product ACR 480” on
middle applet (ADL) page 280.

ACR 480: The List and Delist 12-1RYK5JX 12-1RYK5II 8.1.1.1 Yes, see
dates are not being populated in “Instructions for
the ADL applet ACR 480” on
page 280.

ACR480: The Auditable, 12-1RYK5I2 12-1RYK5GS 8.1.1.1 Yes, see


Orderable, and Promotable flags “Instructions for
are always checked as True in ACR 480” on
the ADL applet page 280.

582 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 358: Provides support for 12-1RV6IE1 12-1JGEFDN 8.1.1.1 Yes, see
the new out-of-the-box “Instructions for
integration between Siebel and ACR 358” on
EBS OTM. Integration points page 41.
include account, products,
pricing, funding (accruals),
shipments, promotions,
deductions, and payments.

ACR 480: Within Administration 12-1RSAYUA 12-1RSAYSV 8.1.1.1


- 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

ACR 480: When users navigate 12-1RSAYQS 12-1RSAYPD 8.1.1.1 Yes, see
to Site Map > Adminstration - “Instructions for
Authorized Distribution List, click ACR 480” on
on the 2LNV detail list, navigate page 280.
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

Retail Objectives
ACR 480: When users navigate 12-1SN1X8G 12-1SMKW6N 8.1.1.1
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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 58 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 480: Within Accounts, when 12-1RUPL7F 12-1RUPL60 8.1.1.1 Yes, see
users select a account that has “Instructions for
distribution added, navigate to ACR 480” on
Merchandising Location > Create page 280.
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

Sales Volume Planning


ACR 480: For leaf-level 12-1SEPR7S 12-1SEPR65 8.1.1.1
accounts, Aggregated Quantity
should not equal Promotion
Incremental Quantity

ACR 480: Within the SVP > 12-1S2WET4 12-1S1GHXS 8.1.1.1


Baseline - Flat view, the All Years
button is missing

The cursors are left open during 12-1RSB0UE 12-1ONVDYP 8.1.1.1


the Aggregation and Allocation
processes

Trade Promotions
ACR 480: Provides a system 12-1TXBBQB 12-1TXBBP1 8.1.1.1 Yes, see
reference called "Trade “Instructions for
Promotion Extended" to allow ACR 480” on
customers to implement the new page 280.
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

ACR 480: Provides the following 12-1SG67VF 12-1SEPND9 8.1.1.1


EIM import files: eim45.sql and
eim_export_bu_look_up_name.
sql

584 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 480: Includes translated 12-1SD8PE4 12-1SD8PCN 8.1.1.1


error message files

ACR 480: Some fields are not 12-1SCRGQE 12-1SCRGO9 8.1.1.1


copied from the Corporate
Promotion header to the Account
Promotion header

ACR 480: Within Corporate 12-1SCRGO0 12-1SCRGNB 8.1.1.1


Promotions, the Target Child
Account applet is not refreshed
properly

ACR 480: When users click the 12-1SC7RS9 12-1SC7RRJ 8.1.1.1


Products button within Corporate
Promotions, they receive an
error message

ACR 480: When users create a 12-1SB91B5 12-1SB919Q 8.1.1.1


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

ACR480: Category Pick applet is 12-1S9R960 12-1S9R95B 8.1.1.1


not refreshed in CPG Plan
Account Promotion List Applet

ACR480: Within Account 12-1S9R952 12-1S9R94D 8.1.1.1


Promotions > Pick Plan applet,
the Go button is unavailable

ACR 480: Clicking the Products 12-1S9AHQ9 12-1S8I5DB 8.1.1.1


button on CG Promotion Form
Applet Non-Corporate retrieves
inactive products

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 58 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 480: Within the Corporate 12-1S87Q2L 12-1S87Q0F 8.1.1.1


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.

ACR 480: Includes the translated 12-1S8I5CG 12-1S8I5B5 8.1.1.1


error message files

ACR 480: Spend Values are not 12-1S7SICW 12-1S7SIBE 8.1.1.1


being rolled up

ACR 480: An error message 12-1S6A181 12-1S6A16Q 8.1.1.1 Yes, see


appears when users create a “Instructions for
promotion ACR 480” on
page 280.

ACR 480: The Team field is blank 12-1S6A16E 12-1S6A14X 8.1.1.1 Yes, see
for a new plan “Instructions for
ACR 480” on
page 280.

ACR 480: In the Promotion 12-1S35CMR 12-1S35CLB 8.1.1.1 Yes, see


screen, clicking the Shipment “Instructions for
button yields an error message ACR 480” on
page 280.

ACR 480: Adds the the following 12-1S1GHXJ 12-1S1GHUK 8.1.1.1


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

586 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 480: Within Plan Promotion, 12-1S29NQA 12-1S29NOZ 8.1.1.1


Category pick applet data is
incorrect when a plan has a
category

ACR 480: Within Object Explorer, 12-1S2EV5J 12-1S2EV2Z 8.1.1.1 Yes, see
when users query for the CPG “Instructions for
Plan Account Plan Team, ACR 480” on
navigate to User Properties, page 280.
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

ACR 480: Changing an account 12-1S2EV2Q 12-1S2EV11 8.1.1.1 Yes, see


does not update the Plan Team “Instructions for
information accordingly ACR 480” on
page 280.

ACR 480: When users create an 12-1S2EUXT 12-1S2EUVJ 8.1.1.1 Yes, see
account with team and “Instructions for
organization information, ACR 480” on
navigate to Plan and create a page 280.
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.

ACR 480: Makes the Deal Id field 12-1RVOP62 12-1RVOP5D 8.1.1.1


mandatory for claim resolution
records

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 58 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 480: When a claim 12-1S0YT2N 12-1S0YT1Y 8.1.1.1


resolution is canceled, the
amount at the claim leve is not
updated accordingly

ACR 480: Users are allowed to 12-1S0YT0Q 12-1S0YSZZ 8.1.1.1


create a claim resolution with a
zero or negative rate

ACR 480: Users are allowed to 12-1S0YSZQ 12-1S0YSZ1 8.1.1.1


create a claim resolution with a
zero or negative rate

ACR 480: When users create 12-1S0YSW4 12-1S0YSV5 8.1.1.1


claims, the application ignores
the decimal value of the rate
during calculation

ACR 480: Within the Target 12-1RY2D5T 12-1RY2D54 8.1.1.1


Accounts tab, the New button is
enabled in the Committed Target
account applet

ACR 480: Within Promotion > 12-1RY2D4S 12-1RY2D2P 8.1.1.1


Corporate Promotions, when
users attempt to create account
promotions from the Target
Account tab, they receive an
error message

ACR 480: Within the Authorized 12-1RYK5LL 12-1RYK5K6 8.1.1.1 Yes, see
Category Product tab, the “Instructions for
product is not bounded ACR 480” on
page 280.

ACR 480: When users copy an 12-1RYK5G3 12-1RYK5EO 8.1.1.1 Yes, see
account in the Authorized “Instructions for
Account applet, the Primary flag ACR 480” on
is not checked for Account Team page 280.

ACR 480: After a payment is 12-1RYK3YO 12-1RYK3WU 8.1.1.1


approved or rejected, the
Approve and Reject buttons are
not disabled

588 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 480: When users create a 12-1RXY8AU 12-1RXY89D 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)

ACR 480: Within the Payment 12-1RYJINX 12-1RXLDGI 8.1.1.1


Approval view, the Amount field
in Credit Memo Payment applet
displays more than two decimal
places

ACR 480: Within Promotion > 12-1RVOL6Y 12-1RVOL5H 8.1.1.1


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

ACR 480: Within the Promotion 12-1RXLGQL 12-1RXLGP5 8.1.1.1 Yes, see
screen > Category pick applet, “Instructions for
the Query button does not work ACR 480” on
page 280.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 58 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 480: When users create an 12-1RV785V 12-1RV784G 8.1.1.1 Yes, see
account, log out of the “Instructions for
application, log back in, navigate ACR 480” on
to the Plan screen, click the New page 280.
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

ACR 480: When users create an 12-1RV782J 12-1RV7811 8.1.1.1 Yes, see
account with two members as “Instructions for
the Plan Team (for example, ACR 480” on
CTRIPP and RMARCKS, log out of page 280.
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

ACR 480: Changing the plan 12-1RVO4UE 12-1RVO4TP 8.1.1.1


information within the
Promotions screen does not
update Plan fields accordingly

ACR 480: Deleting a plan from a 12-1RVO4TB 12-1RVO4SL 8.1.1.1


promotion does not update the
Plan fields accordingly

ACR 480: Within Promotion > 12-1RVO4S2 12-1RVO4QT 8.1.1.1


Plan pick list, the OK button is
not available

ACR 480: When a plan has a 12-1RVO4QI 12-1RVO4PT 8.1.1.1


category with Private Flag set to
Y, baseline values are not
updated

590 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 480: Within Promotions > 12-1RUPMUC 12-1RUPMSM 8.1.1.1


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

ACR 480: Within Promotions > 12-1RUPMSB 12-1RUPMQC 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

ACR 480: Within Promotions > 12-1RU7ZTM 12-1RU7ZSX 8.1.1.1


Promoted Category applet, the
Tactics field is not available

ACR 480: The values in the PY 12-1RV0XWF 12-1RV0XRV 8.1.1.1


Baseline Revenue and Target
Baseline Revenue fields are
calculated incorrectly

ACR 480: Within Promotions, 12-1RV6FVL 12-1RV6FUV 8.1.1.1


users are not able to add
products to the Promoted
Product applet

ACR 480: Provides a button on 12-1RSSAP2 12-1RSSANR 8.1.1.1


the SVP Flat view to navigate to
Previous, Next, and Current SVP
periods

ACR 480: Within Plan List > High 12-1RUOZX8 12-1RUOZWH 8.1.1.1
Level Planning, when users
create a plan and click Simulate,
they receive an error message

ACR 480: Moves the High Leve 12-1RSB0SK 12-1RSB0R9 8.1.1.1


Planning view under Plan List
within the Plans screen

ACR 480: The PY Revenue and 12-1RU81XF 12-1RU81VZ 8.1.1.1


Target Revenue fields should be
copied from Product Baseline

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 59 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 480: Provides Claim 12-1RUPJ1P 12-1RQU8CD 8.1.1.1


Management functionality within
Settlements > Claim List

ACR 480: Within Admin - Data > 12-1RSB6PK 12-1RSB6OV 8.1.1.1


Account Product > Baseline
view, the PY Baseline Qty and
Target Qty fields are read-only

ACR 480: Within Account screen 12-1RT9Z51 12-1RT9Z3C 8.1.1.1 Yes, see
> Distribution applet, the “Instructions for
Distribution Code, Sequence ACR 480” on
Code, and Retail Order fields are page 280.
missing

ACR 480: Delist date is updated 12-1RT9Z31 12-1RT9Z1M 8.1.1.1 TYes, see
with the effective end date of the “Instructions for
product ACR 480” on
page 280.

ACR 480: Within Account screen 12-1RT9Z16 12-1RT9YZW 8.1.1.1 Yes, see
> Distribution applet, the “Instructions for
Auditable and List Date fields are ACR 480” on
missing page 280.

ACR 480: Within Adminstration - 12-1RT9YZI 12-1RT9YWF 8.1.1.1 Yes, see


Product > Product applet, when “Instructions for
users select a product, update ACR 480” on
the Effective End Date field, and page 280.
click the Update Delist Date
button, they receive an error
message

ACR 480: The Auditable and List 12-1RT9YW4 12-1RT9YUP 8.1.1.1 Yes, see
Date fields are missing from the “Instructions for
ADL applet ACR 480” on
page 280.

ACR 480: The Update Delist Date 12-1RT9YU6 12-1RT9YSN 8.1.1.1 Yes, see
button should be read-only in “Instructions for
Query mode in Product ACR 480” on
Administration screen page 280.

ACR 480: Within the Target list 12-1RT9YSE 12-1RT9YQZ 8.1.1.1 Yes, see
applet, Copy ADL functionality “Instructions for
does not work properly ACR 480” on
page 280.

592 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 480: When users navigate 12-1RSS2IC 12-1RSS2HN 8.1.1.1


to Site Map > Promotion >
Corporate Promotion List, click
New, enter Promotion, Period,
and Parent Account information,
and save the record, they
receive the following error
message: "Promotion id
required, please enter the value"

ACR 480: Within Administration 12-1RRTIA6 12-1RRTI9H 8.1.1.1


- 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
receive an error message

ACR 480: Within Adminstration - 12-1RSAYSM 12-1RSAYR6 8.1.1.1 Yes, see


Authorized Distribution List > “Instructions for
2LNV detail list > Account ACR 480” on
product applet, the following page 280.
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

ACR 480: Within > 12-1RSAYP2 12-1RSAYNN 8.1.1.1 Yes, see


Adminstration - Authorized “Instructions for
Distribution List, when users ACR 480” on
click on the 2LNV detail list, page 280.
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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 59 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 480: Within Adminstration - 12-1RQU5AA 12-1RQU57X 8.1.1.1 Yes, see


Authorized Distribution List, “Instructions for
when users click on the 2LNV ACR 480” on
detail list, navigate to the page 280.
Account Product applet, click the
New button, and select the
Product pick applet, the applet
opens in query mode

ACR 480: Some fields within 12-1RRI4MW 12-1RRI4LT 8.1.1.1


High Level Category are not
copied to Promoted Category

ACR 480: Within Accounts > 12-1RRI4LI 12-1RRI4KT 8.1.1.1


High Level Planning, the Account
field is not defaulted to the
parent account

ACR 480 provides the following 12-1RHR1SG 12-1RKLYHL 8.1.1.1 Yes, see
enhancements: “Instructions for
ACR 480” on
■ Resolves key connection
page 280.
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.

Customer Order
Management
Configurator

594 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

On the AIX platform, when users 12-1TYASEC 12-1QUOKCX 8.1.1.1


configure a product and
encounter an error message,
clicking the Explanation button
on the error page causes the
application to crash

RaiseErrorText does not work 12-1T03JT6 12-1SWPR8F 8.1.1.1


properly within Customizable
Products script

When users modify an installed 12-1T03XIC 12-1SFOTK9 8.1.1.1


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

The Begin Configuration Web 12-1SQFLCT 12-1S1GFK5 8.1.1.1


service does not add the default
product to the instance

AutoMatch Promotion 12-1SM2Y98 12-1SB8JB4 8.1.1.1


functionality does not work in
Remote Configurator

After Siebel 8.0.0.5 QF6501 has 12-1SMKVHR 12-1SINAW9 8.1.1.1


been applied, child product
scripts in eConfigurator are not
run, and the scripts on the root
are run instead

BatchValidate returns the wrong 12-1SJ5CJI 12-1SFPA4D 8.1.1.1


status on modified quotes

Configurator crashes when 12-1RZ1HIB 12-1LG27LD 8.1.1.1


invoking the 'CopyXA' method

Product Configurator :Scripting 12-1RY2OPU 12-1RNYSBH 8.1.1.1


the Attribute_Changed event
impacts performance on UNIX

Constraints on product quantity 12-1RAJ7W8 12-1PI44DB 8.1.1.1 Yes, see


do not calculate correctly when “Instructions for
products are exploded FR 12-1RAJ7W8”
on page 726.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 59 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Batch Validate should set the 12-1R8LSHO 12-1R1VGAZ 8.1.1.1


status to invalid and populate
the error message when
validating a missing required
attribute

Within the Configurator UI, 12-1QH5LLS 12-1Q25XGN 8.1.1.1


existing but ineligible items are
not visible

The Customize icon should not 12-1Q2NGYC 12-1GVJ1I5 8.1.1.1


appear within a Configurator
session for child items that have
product type marked as 'non
structure’

Changing a promotion or an 12-1PLH1UO 12-1PILEIJ 8.1.1.1


upgrade promotion on an order
line item does not update
products correctly

After users upgrade, all UI 12-1PLGJCL 12-1P55Q2H 8.1.1.1


values that are attached to
attribute display values are
missing

In Configurator, an attribute pick 12-1PILI4L 12-1J9GEWZ 8.1.1.1


list cannot be filtered by a value
of a hidden attribute

Custom rules cause the Object 12-1OTUXFZ 12-1MFCJ25 8.1.1.1


Manager to crash

BatchValidate does not create 12- 12-1NCHH5Z 8.1.1.1


child items 1OOWDM5

Component-based routing can 12- 12-1O139AX 8.1.1.1


fail if the components are not 1OMWL5M
enabled in all of the servers after
Siebel Server has attempted
routing five times

596 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

After users have applied Siebel 12- 12-1NWD809 8.1.1.1


8.0.0.2 QF0218, they receive the 1O7OYPW
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)

When users upgrade, some 12-1NXSFEU 12-1NKJKRL 8.1.1.1


product constraint rules cause
attribute values to display in red

Within eConfigurator running on 12-1NTIUSH 12-1N3J0OL 8.1.1.1


a Standard Interactivity client,
when users click quickly on
attributes and then click the
Done button, the application
hangs

A Object Manager memory leak 12- 12-1N03OFF 8.1.1.1


occurs when users perform the 1NNUXWO
Done operation within
Configurator

Promotion policy enforcement 12-1N22KA2 12-1LVX3H3 8.1.1.1


results in incorrect behavior
upon the first promotion policy
violation 'undo' operation

Eligibility Display mode 2 is not 12-1N22K77 12-1MGHHF6 8.1.1.1


hiding in eligible products

Global variables do not work in 12-1N22K4B 12-1MBQUCS 8.1.1.1


eScript within Configurator

Wrong validation results occur 12-1N1RDOP 12-1LY4CD9 8.1.1.1 Yes, see


with promotions and “Instructions for
Customizable Products FR 12-1N1RDOP”
on page 721.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 59 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Invalid workers are not 12-1MJW3F9 12-1L9C3FT 8.1.1.1


immediately inactivated or
dropped to avoid their being
used by other Configurator
sessions

Smartpart numbers based on 12- 12-1M0PGMJ 8.1.1.1


Attribute Matrix do not update 1M0PGOQ
the smart part number correctly
for child components when
customized twice

Order Management
Batch Validate does not give 12-1TK9032 12-1T7DFU1 8.1.1.1
expected output for incomplete
quotes or orders

This FR will fix the problem that 12-1SM2HO1 12-1SI5HGB 8.1.1.1


occurs upon insert of the Auto
Contract from an Order. Error '
the value for column
'CCNUM_ENCRPKEY_REF'in table
'S_AGREE_TERMS'twice in the
same statement'.

When users create a bulk order 12-1SJO2TA 12-1S7POKB 8.1.1.1


of type Modify and try to update
Start Date in the action set, the
start date on the order is not
updated

Bundles the Promotion and 12-1S8QOEL 12-1P81O39 8.1.1.1 Yes, see


Product class relationship so that “Instructions for
changing a promotion in a ACR 471” on
change order loads the default page 159.
product (ACR 471)

Enforces Max and Min cardinality 12-1RVOKIA 12-1QL0MPH 8.1.1.1 Yes,


for Bulk Orders functionality see“Instructions
for FR 12-
1RVOKIA” on
page 734.

Cursors remain open after a 12-1RNYLCO 12-1QZXUMT 8.1.1.1


promotion creates an agreement

598 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When users click on Product 12-1RIPN17 12-1ORVK5E 8.1.1.1 Yes, see


Category in the Quotes screen “Instructions for
after DVM, they receive Siebel FR 12-1RIPN17”
error message SBL-DAT_00309 on page 727.

Date calculation in Row Set 12-1RHA20H 12-1P9YKJD 8.1.1.1


Transformation Toolkit does not
work consistently

A validation problem occurs with 12- 12-1PQ8RSX 8.1.1.1


inserting and associating a 1QQ9WQW
record from an MVG applet

Users are unable to update 12-1OUUFYF 12-1OJ22KN 8.1.1.1


payment profiles it the profile
has been created using special
characters (such as
apostrophes)

Orders
The SIS OM PMT Service's 12-1QMFLED 12-1QL0ID7 8.1.1.1
Synchronize method leaves
rogue cursors open, which
consumes system resources

When adding Customizable 12- 12-1NZNRV3 8.1.1.1


Products or promotions using 1OK5WH7
Web Services, only Customizable
Products are added, not the
default components in a Sales
Order

Application Deployment Manager 12-1RAJ8OH 12-1PT60R3 8.1.1.1 Yes, see


Workspace file import fails “Instructions for
FR 12-1RAJ8OH”
on page 727.

Pricer
When users accept an upsell 12-1SF7G9Z 12-1RZJE8H 8.1.1.1
recommendation product on an
order, the following error
message appears: Error invoking
service '<?>', method '<?>' at
step '<?>' (SBL-BPR-00162)

Products

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 59 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 471: The system crashes 12-1TYASDV 12-1TK3Z1X 8.1.1.1


while executing iLog Rule Test
case

The Upgrade Promotion function 12-1NT21HP 12-1N3J0VT 8.1.1.1


does not correctly apply
constraints

Data Quality
Other
In Siebel 8.1.1, Data Quality 12-1STTNB0 12-1PCDF0P 8.1.1.1
does not work as expected if
both DeDup and DataCleansing
are enabled

Data Validation Manager: Non- 12-1RSRZYQ 12-1QV5W5B 8.1.1.1


active fields are activated by the
DVM engine

Financial Services
Other

600 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Adds the following views in FINS 12-1R3SH2T 12-1QCSQ49 8.1.1.1


(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

The 'FINS CEM Calculation' 12-1QDA84B 12-1ORDCF9 8.1.1.1


Business Service 'Calculate'
method does not work after
users drill down

Other-Retail Finance
Provides Siebel Financial 12-1S987PV 12-1QT7XTB 8.1.1.1 Yes, see
Services Customer Order “Instructions for
Management for Banking ACR 467” on
functionality (ACR 467). page 150.

General
Access Control

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 60 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Prevents users from opening 12- 12-1L89B79 8.1.1.1


multiple sessions on the Mobile 1O4OGQ1
Web Client (ACR 432)

Application
Deployment Manager
HTTP deployment of the Rules 12-1QODT6O 12-1PZOO3C 8.1.1.1
engine data type fails

ACR456: Allows users to perform 12-1Q2NT7U 12-1ORUZ7R 8.1.1.1 Yes, see


Assignment Manager bulk-data “Instructions for
maintenance (CRUD on Rules, ACR 456” on
Positions, candidates and so page 97.
forth) through client views and
screens

ACR 456: Within the transaction 12-1TXC0BL 12-1TXC0A2 8.1.1.1 Yes, see
log, the time stamp is not correct “Instructions for
for imported and exported files ACR 456” on
(Linux-specific error) page 97.

ACR 456:When users navigate to 12-1TKAELA 12-1TKAEJI 8.1.1.1 Yes, see


Admin Group > Positions, drill “Instructions for
down on a position, and click ACR 456” on
Export, the following session page 97.
warning error message appears:
The server you are trying to
access is either busy or
experiencing difficulties. Please
close the Web

ACR 456: The default value for 12-1TETVRS 12-1TE65KB 8.1.1.1


export operations should be
Upsert

ACR 456: When users attempt to 12-1TETVPG 12-1TETVNL 8.1.1.1 Yes, see
import an empty csv file, they do “Instructions for
not receive an error message ACR 456” on
page 97.

ACR 456: If exported data 12-1TETVMR 12-1TETVL9 8.1.1.1


contains a percentage sign, the
import fails

ACR 456: Improves the quality 12-1SZ4I4Z 12-1SZ4I3F 8.1.1.1


of Assignment Manager error
messages related to ACR 456

602 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 456: When users attempt to 12-1SUAR8D 12-1SREMIN 8.1.1.1 Yes, see
export an Assignment Rule that “Instructions for
does not contain data in the child ACR 456” on
applet, they should receive an page 97.
error message

ACR 456: Within the Admin- 12-1SSUPOB 12-1SSUPNP 8.1.1.1 Yes, see
Group > Skill view, the Import “Instructions for
Data Skill button is not required FR 12-1SSUPOB”
on page 733.

ACR 456: When users attempt to 12-1SSUPFB 12-1SSUPCK 8.1.1.1 Yes, see
import a csv file that does not “Instructions for
contain names or locatios in the ACR 456” on
Import dialob box, the incorrect page 97.
error message displays

ACR456: Deleting a missing 12-1SSUPF2 12-1SSUPD9 8.1.1.1 Yes, see


portion of an input record does “Instructions for
not yield an error message FR 12-1SSUPF2”
on page 732.

ACR456: When users omit skill 12-1SSUPET 12-1SSUPE3 8.1.1.1 Yes, see
information from a csv file, they “Instructions for
do not receive an error message ACR 456” on
when they attempt to import the page 97.
csv file

ACR 456: The dialog box name 12-1SSCJTW 12-1SSCJQY 8.1.1.1 Yes, see
for Import displays as Position “Instructions for
Skill Export but it should be FR 12-1SSCJTW”
Position Skill Import on page 733.

ACR456: When the server is 12-1SREMH3 12-1SREMB7 8.1.1.1 Yes, see


bounced, the ServerDataSrc “Instructions for
folder in the log directory is ACR 456” on
deleted page 97.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 60 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 456: When the Siebel 12-1SREMAH 12-1SREM9V 8.1.1.1 Yes, see
Server and the Call Center “Instructions for
application reside on different ACR 456” on
servers, users receive the page 97.
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)

ACR 456: When users export 12-1SPXSIK 12-1SPXSI3 8.1.1.1 Yes, see
rules that have had some criteria “Instructions for
and criteria values added to FR 12-1SPXSIK”
them, enter numeric values for on page 732.
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

ACR 456: The status of imports 12-1SPXSHM 12-1SPXSGV 8.1.1.1 Yes, see
does not change, regardless of “Instructions for
whether the import succeeded or ACR 456” on
failed page 97.

Audit Trail
The audit trail is not in sync with 12-1TE6CIJ 12-1TE6CHR 8.1.1.1
server from mobile client

Running EIM with 12-1RQUQEX 12-1M0WC9R 8.1.1.1


EnableEimAuditing set to TRUE
leads to an error message

Business Rules
Only one 12-1TARV4S 12-1SW8CMD 8.1.1.1
knowledgebase:module
combination at a time is active

604 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

The application may stop 12- 12-1QL06E5 8.1.1.1


functioning when calling Haley 1QODHWT
Rules from runtime events

Data Validation Manager opens 12-1QAH5TF 12-1PLG9R7 8.1.1.1


database cursors and forgets to
close them

The Data Validation Engine is not 12-1OVTT1V 12-1NJKYC7 8.1.1.1 Yes, see
called correctly on the “Instructions for
PickRecord event, and rules are FR 12-1OVTT1V”
fired incorrectly on page 729.

Calendar
With Internet Explorer 8, a 12-1SJ56UP 12-1SJ56TU 8.1.1.1
double border appears around
calendar appointments

With Internet Explorer 8, within 12-1SJ56TJ 12-1SJ56SC 8.1.1.1 Yes, see


Call Center, when users navigate “Instructions for
to Calendar, click the Daily tab FR 12-1SJ56TJ”
after verifying that there are on page 734.
existing appointments, click
Print, select Today’s 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

ACR 435 resolves the following 12-1QFPE7F 12-WXG93N 8.1.1.1


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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 60 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

The Contact icon is not available 12-1PZO53U 12-1OFLU7D 8.1.1.1


when drilldown has been
configured

Within the ePharma application, 12-1PZO52G 12-1OB4JHF 8.1.1.1


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

A user is able to delete an 12-1PZ4Q5K 12-1N31LWO 8.1.1.1


appointment in another user's
calendar even with read-only
access

When users click the Query 12-1PSNEQB 12-1JN9R0J 8.1.1.1


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

Correspondence
Custom Contact / Proposal 12-1QMG1J3 12-1P81NR1 8.1.1.1
objects do not generate properly

Global/Multilingual
LOV
Adds translations for features 12-1S5T3K5 12-1S5T3JL 8.1.1.1
and fixes in the Siebel 8.1.1.1
Fix Pack

Installation
Siebel Enterprise Server patch 12-1U0CAEA 12-1TARCGM 8.1.1.1
installation is blocked on the
Linux platform

606 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Network Image Creator does not 12- 12-1SDQHGF 8.1.1.1


expose both the SEA and the SIA 1SDQHGZ
options

For the Siebel Web Client, 12-1SCQCYI 12-1SCQCXT 8.1.1.1


incorrect text appears in the
base.txt file

After a new Gateway Name 12-1RZ1JB1 12-1RNH59T 8.1.1.1


Server has been created, the
installer crashes when
navigating back to the main
menu

Provides an OPatch to allow 12-1R7SLGL 12-1R7SLG1 8.1.1.1


customers to install or uninstall
8.1.1 Quick Fixes for Siebel Tools
or Siebel Mobile Web Client

The “Publish product information 12-1QH5ECK 12-1QDRA0T 8.1.1.1


to Siebel Update Server” option
in Network Image Creator is
obsolete and should not display

Users are unable to install 12-1N22JTR 12-1LQUP21 8.1.1.1


multiple languages using the
Unattended Configuration
function

Office
Provides support for Microsoft 12-1N1Q81D 12-1IDNOO9 8.1.1.1 Yes, see
Office 2007 with Document “Instructions for
Server and Siebel Search (ACR FR 12-1N1Q81D”
409) on page 721.

Other
After Siebel 8.0.0.2 QFA205 has 12-1TK99SO 12-1SM30JX 8.1.1.1
been apllied, the Dedicated
Client crashes when the
Business Service Invoke method
is called

Changes the default value for 12-1TS5GM7 12-1S5BJ8W 8.1.1.1


"allow reverse scans" for DB2 v9

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 60 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When string variables containing 12-1TK99Q5 12-1TAR58L 8.1.1.1


the empty string are used in
boolean expressions they fail to
evaluate correctly and the script
will abort bypassing catch and
finally clauses

Improves the quality of error 12-1SXOQ2S 12-1SXP5CT 8.1.1.1


messages related to integrations

The DBinit function fails on the 12-1SUB0QJ 12-1SUAZVN 8.1.1.1


mobile client

When calling object scripts 12-1SSUEYF 12-1SSCEWB 8.1.1.1


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)

If a script references an object 12- 12-1RVOMWT 8.1.1.1


using "with" so that methods do 1SBQM0M
not have to repeatedly use the
object reference, the script fails

After QF6501 has been applied, 12-1S7SIUA 12-1S1FXDF 8.1.1.1


using Find functionality causes a
runtime error

Replacement of OCIStmtFetch 12-1S2JFXL 12-1S2JFWV 8.1.1.1


with OCIStmtFetch2 for Oracle
10g support

Calling GetService in 12-1RGSQ74 12-1R1VZN3 8.1.1.1


eConfigurator scripts queries all
available services, not just the
one specified in the function's
argument, which can cause
performance degradation

Provides Next Step capability for 12-1REDG33 12-1REDG1H 8.1.1.1


TASK UI

The Gateway Server cannot 12-1RAJFNC 12-1PBDVO1 8.1.1.1


connect to the database

608 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Invoking methods in .NET COM 12-1RDFC53 12-1QER4G3 8.1.1.1


dlls sometimes fails in eScript

Tags Object-Manager-generated 12-1R84Y40 12-1R4AL4P 8.1.1.1


SQL with user session
information to allow the
administrator to trace any slow
or bad SQL back to its
originating Object-Manager-
based task

Having only a single line of script 12-1QXJDNV 12-1Q7IUCR 8.1.1.1


in ST engine causes a runtime
error

Within eScript, when variables 12-1QXJDMR 12-1Q9Z7W1 8.1.1.1


used in "with" blocks are
declared outside of the "with"
block, they are not recognized

When certain scripts are used in 12-1QODT7F 12-1PMW6OI 8.1.1.1


the new scripting engine, cursor
leaks occur

When attach certs using 12- 12-1OQU1KJ 8.1.1.1


mwcontrol are installed, EAI 1QODWZU
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

During upgrade attempts, the 12-1NU063L 12-1NTZMQP 8.1.1.1


Development database DDLIMP
fails while attempting to recreate
existing indexes

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 60 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

PIM Server
Integration
If a PIMSI share is unavailable at 12- 12-1MQCFNM 8.1.1.1
startup, the PIMSI Engine 1MQCM12
component dies

When an Exchange calendar 12-1S2WDXF 12-1RW60TB 8.1.1.1


item includes
"mailto:address@domain.com"
(as opposed to
"address@domain.com"), the
item is not parsed properly
during inbound synchronization

There is no email notification 12-1RPHOHG 12-1RPHO7U 8.1.1.1


when a record is not processed
by Exchange Connector

System-wide configurations 12-1R7MVJZ 12-1L51WBF 8.1.1.1


performed for UserMailBoxID are
not reflected in the logs

SSSE skips record-level failures 12-1QUOI8I 12-1QT8EZN 8.1.1.1


of any kind during integration

Contact categories other than 12-1QTPBL0 12-XLYU4T 8.1.1.1


"Siebel Contact" are not
preserved during outbound
contact sync

When synching, an error 12-1QL0MAF 12-1QJJA4H 8.1.1.1


indicating a duplicate attendee is
shown in the attendee cache

If the "Category Field" for the 12-1QDR9DV 12-1QBCIEN 8.1.1.1


contact domain is changed from
the default "Category," contact
matching fails during
synchronization

Provides support for Outlook 12-1P1AWIT 12-1OXSN8J 8.1.1.1


2007 Embedded Outlook
Calendar (ACR 369)

ACR 481: Provides the ability to 12-1MX8ZG9 12-1LY4V61 8.1.1.1


ignore Outlook appointments/
tasks based on "Private" flag

610 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 481: Addresses an issue 12-1MQCFG3 12-1MBR3N7 8.1.1.1


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

Platforms
Applications do not switch from 12-1TK84BZ 12-HFIYXK 8.1.1.1
http to https when
SecureBrowse = TRUE, HTTPS

The Mainwin version command 12-1T8C7B4 12-1T8C79H 8.1.1.1


("mwversion") does not display
the version and patch level

On Solaris, after Siebel 8.1.1.1 12-1T6VFL8 12-1T6VFKJ 8.1.1.1


has been installed, the Call
Center application is unavailable

Remote
ACR432: A blank Error message 12-1U087L1 12-1S7PRXF 8.1.1.1
displays when users try to
launch multiple Mobile Web
Client Sessions

Transaction Processor becomes 12-1TK4ZPR 12-1T2IN2L 8.1.1.1


slow when it processes large set-
based transactions logged by
EIM

On the local database, manager 12-1SPGXZK 12-1S4C8GR 8.1.1.1


visibility is not changed after
subordinates have been
removed

If you have more than one case- 12-1SC3OLN 12-1S8QNHX 8.1.1.1


insensitive indexed column on a
table, GennewDb fails

Repagent fails with the following 12-1R1VGZM 12-1R1VGYV 8.1.1.1


error message: ORA-01400:
cannot insert NULL into
("ORA05299"."S_AUDIT_ITEM".
"BUSCOMP_NAME

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 61 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

MLOV-enabled fields display 12-1QU74G4 12-1NWCZ8F 8.1.1.1


incorrect values after applying
CIAI table changes to database

Applying database schema kits 12-1QODYE6 12-1Q71PB5 8.1.1.1


fails if CIAI is enabled on
S_USER

When the initialization process is 12-1Q25ZLO 12-1EFZ3Q9 8.1.1.1


attempted on the Siebel Mobile
Web Client, users receive the
following error message: "An
Unsupported Operation was
attempted.”

Login lockout time is expressed 12- 12-1H2HO3L 8.1.1.1


in days instead of minutes and 1HMLBHM
the value can only be an integer

Report Designer
The BI Publisher Report applet 12-1SQFISM 12-1SQFIRV 8.1.1.1
cannot be closed using the X icon

Provides the following 12-1SFP3WR 12-1SFP3UM 8.1.1.1 Yes, see


enhancements for BI Publisher: “Instructions for
BI Publisher
■ Enables reports with
Enhancements”
parameters.
on page 441.
■ Enables scheduling.

■ Provides a new Web service


to support the new BI
Publisher security model.

Users are unable to update the 12-1RAJ9OJ 12-1Q353O9 8.1.1.1


rtf template in the Report
Template Registration view for
existing records

Reports Server
Within the Schedule a Report 12-1TCP6D1 12-1TCP6BM 8.1.1.1
dialog box, when users click the
Cancel button, the window does
not close

When users click the BIP icon > 12-1U5S3EF 12-1U5S3DL 8.1.1.1
Account List Report link, the
application crashes

612 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

BI Publisher: Users are unable to 12-1TH5MF4 12-1TH5MDM 8.1.1.1


choose a different report format
once they have run a report
using the default method

BI Publisher: Clicking the Close 12-1TH5MDA 12-1TH5MBQ 8.1.1.1


button does not close the Report
window

The BIPDataService.xml and 12-1TG6D0Q 12-1TG6D01 8.1.1.1


BIPSiebelSecurityWS.xml files
are missing from the patch
installer

BI Publisher: The SiebelXMLP.jar 12-1TG5CZR 12-1TG5CZ2 8.1.1.1


file is outdated

The path of dataservice.wsdl is 12-1TG5CYT 12-1TG5CY4 8.1.1.1


hardcoded to a absolute path

BI Publisher: The XMLP Driver 12-1TG5EFC 12-1TG5EED 8.1.1.1


Service Business Service is
missing the GetAllRoles method

Error messages display behind 12-1TE6GDE 12-1TE6FZ1 8.1.1.1


the active window and users
must minimize the application
window to be able to see the
error messages

Within the application, when 12-1TE6GD3 12-1TE6G7O 8.1.1.1


users navigate to Account >
Account List > BIP icon, and click
Account List Report, the picklist
spelling is incorrect in the
Reports Run dialog box

Users who do not have the 12-1TDOSFC 12-1TDOSDX 8.1.1.1


appropriate responsibility can
see the Schedule Reports menu

When users download a 12-1TCP6DA 12-1TCP6A6 8.1.1.1


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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 61 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When users click the BIP icon 12-1TCP6A1 12-1TCP68R 8.1.1.1


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

When users run a report, close 12-1TB8SBT 12-1TAREQG 8.1.1.1


the parameterized report
window, and then navigate to
BIP Report Menu > Account List,
the Schedule Report and
Parameterized Report dialog
boxes open together

When users schedule reports 12-1TB8S9I 12-1TAREOW 8.1.1.1


using the Run Immediately
option in PDF format, and then
click the Schedule button, the
Schedule Report window resizes

When users schedule reports 12-1TB8S8G 12-1TARENH 8.1.1.1


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

614 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Provides the following fixes and 12-1SW88PJ 12-1SW88O5 8.1.1.1 Yes, see
enhancements for BI Publisher: “Instructions for
BI Publisher
■ Corrects an issue where
Enhancements”
different users receive the
on page 441.
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

Provides XMLP Integration - 12-1SFP3X0 12-1SFP3TR 8.1.1.1 Yes, see


Schedule Reports functionality “Instructions for
BI Publisher
Enhancements”
on page 441.

Provides XMLP Integration - User 12-1SFP3W8 12-1SFP3VD 8.1.1.1


Management, and new Web
services for BI Publisher's new
Security Model

When generating a report from a 12-1QJJWDF 12-1Q37ZF9 8.1.1.1


view where the primary applet
has a search specification, this
expression is not passed as part
of the report query

Within Siebel Tools > Object 12-1QDRPN2 12-1PS529D 8.1.1.1


Explorer, the Reports option
should not display

Missing Method Input Arguments 12- 12-1PW3PQ9 8.1.1.1


for XMLP Driver Service Business 1QDRNNC
Service

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 61 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Corrects instances of BIP to BI 12-1QCSJWS 12-1P90KAL 8.1.1.1


Publisher throughout the
interface

BI Publisher: The "Routing 12-1Q35LZW 12-1Q06K23 8.1.1.1 Yes, see


Model" field is not populated in “Instructions for
Mobile User Summary Report FR 12-1Q35LZW”
on page 722.

Search
ACR 403: Users cannot open the 12-1RBZCK1 12-1NCHNGC 8.1.1.1 Yes, see
search center from the All “Instructions for
Opportunities page ACR 403” on
page 41.

ACR403: Drilldown on Search 12-1S1XV7D 12-1NGQQVD 8.1.1.1 Yes, see


results does not work “Instructions for
ACR 403” on
page 41.

Provides Disconnected Search 12-1L9AXI2 12-1L8TZWR 8.1.1.1 Yes, see


for Siebel Mobile Client (ACR “Instructions for
403) ACR 403” on
page 41.

ACR439: Provides the ability to 12-1M7YTQL 12-1M7YTKT 8.1.1.1 Yes, see


show Search results in the left “Instructions for
pane. ACR 439” on
page 90.

ACR 439: After Search Center is 12-1S7PQRR 12-1R49VTZ 8.1.1.1 Yes, see
closed, Last Find and its search “Instructions for
criteria are not retained FR 12-1S7PQRR”
on page 729.

Prepopulates Search terms and 12-1RBZCM1 12-1NCHP85 8.1.1.1 Yes, see


sets defaults in the search task “Instructions for
pane (ACR 439) ACR 439” on
page 90.

616 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 452: After ACR 452 has 12-1TARBRC 12-1TARBQD 8.1.1.1 Yes, see
been set up, when users launch “Instructions for
Call Center, navigate to ACR 452” on
Administration - Search > page 95.
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'

ACR 452: Provides Siebel Search 12-1TARYMD 12-1T0KYST 8.1.1.1 Yes, see
support for languages other than “Instructions for
ENU ACR 452” on
page 95.

ACR452: OSES Integration 12-1P5O4RM 12-1OQD10Y 8.1.1.1 Yes, see


uptake: Auto keyword “Instructions for
generation FR 12-1P5O4RM”
on page 722.

ACR452: OSES integration 12-1P5O4MN 12-1OQD13S 8.1.1.1 Yes, see


uptake: Search by file format “Instructions for
ACR 452” on
page 95.

ACR452: OSES integration 12-1P56B8M 12-1ORBTGJ 8.1.1.1 Yes, see


uptake: Mixed Operator Search “Instructions for
ACR 452” on
page 95.

ACR452: OSES integration 12-1ORBTNH 12-1ORBTM7 8.1.1.1 Yes, see


uptake: Dynamic Weights “Instructions for
ACR 452” on
page 95.

The Administration - Mobile 12-1S1XV5H 12-1OXSZ78 8.1.1.1


Search > Search Index Settings
> SCC FTP Location field label is
incorrect

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 61 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When configuring the Find 12-1RPEVGE 12-1QJ1W1B 8.1.1.1


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

With Siebel 8.0.0.5, using Siebel 12-1RH9JAH 12-1R4A1BH 8.1.1.1


Find to drill down into records
and then clicking the Back
button results in the SBL-UIF-
00335 error message

With Oracle SES, when searches 12-1RGSQ4A 12-1PBVDYL 8.1.1.1


contain quotation marks, the
queries fail

Allows customers to toggle 12-1RBZCO1 12-1N3J0NR 8.1.1.1 Yes, see


between views (ACR 439) “Instructions for
ACR 439” on
page 90.

The sequence in the Look In 12-1RBZCN1 12-1NABW5J 8.1.1.1


drop-down list does not change
even after the sequence has
been changed in Siebel Tools
(ACR 439)

(ACR403): Does not contain/ 12-1RBZCJ1 12-1NFSUUI 8.1.1.1


Exact Phase/with exact phase is
not working properly

Allows Find and Attach 12-1RBZCI0 12-1O4OT5J 8.1.1.1 Yes, see


functionality to have the parent “Instructions for
relationship be based on the ACR 439” on
parent applet (ACR 439) page 90.

ACR 439: Associates button 12-1RBZCH0 12-1O4OT68 8.1.1.1 Yes, see


availability based on the parent “Instructions for
applet, as with Siebel ACR 439” on
applications version 7.8 page 90.

618 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Implements Preview with Find, 12-1RBZCFZ 12-1O4OT7M 8.1.1.1 Yes, see


as in Siebel 7.x applications. “Instructions for
With this enhancement, when ACR 439” on
users click the Binoculars icon, page 90.
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)

ACR439: Implements Preview 12-1RBZCEZ 12-1O4OT91 8.1.1.1 Yes, see


with Search functionality to “Instructions for
match the behavior that was ACR 439” on
available with Siebel applications page 90.
version 7.x

ACR439: Converts "Saved 12-1RBZCDZ 12-1O4OTAF 8.1.1.1 Yes, see


Searches" from an HTML list to a “Instructions for
drop-down pick list ACR 439” on
page 90.

ACR439: The Advanced Search 12-1RBZCCX 12-1O4OTBW 8.1.1.1


button should only be activated
when a search engine has been
configured

ACR 439: Blank records are 12- 12-1P55M4B 8.1.1.1


yielded when users perform the 1RBZCBW
Find operation

After ACR 439 has been applied, 12-1RBZCAU 12-1P55M5L 8.1.1.1


Previous Search criteria are lost

There should not be a Search 12-1RBZC9U 12-1PG7SQT 8.1.1.1


Definition dependency for the
FIND function

Makes "Recent Saved Searches" 12-1RBZC8U 12-1PLXUCJ 8.1.1.1


only appear when a search
engine has been configured

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 61 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When Windows Desktop Search 12-1RBI95M 12-1PZ42DC 8.1.1.1


is not installed, Basic Search
unexpectedly closes the Mobile
Client.

ACR 452: Exact Search with 12-1TAA6DH 12-1SZEIXA 8.1.1.1


quotes replaces delimeters with
&quote:

ACR 403: Indexing is not 12-1STT0AE 12-1STT095 8.1.1.1


working on the Mobile Web Client

ACR 452: Data import using 12-1STTMYT 12-1STTMY4 8.1.1.1


import.bat fails

ACR 452: Auto Keyword 12-1TYARO5 12-1TYARMF 8.1.1.1


Generation is not refining the
Search

ACR 452: Searching for strings 12-1TUW2TZ 12-1TUW2RV 8.1.1.1


with double quotes or "None of
These Words" yields an error
message

ACR 452: Searching using a 12-1TUW2PA 12-1TUW2IJ 8.1.1.1


wildcard or a single letter
followed by a wildcard should
yield an error message but it
does not

ACR 452: Within the 12-1THOE42 12-1THOE3D 8.1.1.1 Yes, see


Administration Search - Search “Instructions for
Connector Setting page, ACR 452” on
changes the labels of the Deploy page 95.
and Undeploy buttons to Create
Source and Delete Source,
respectively

620 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 452: Within the Call Center 12-1TD6T75 12-1TD6T55 8.1.1.1


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

ACR 452: After ACR 452 has 12-1TAA6DT 12-1SZEIZE 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.

ACR 452: Adds the following text 12-1SX7AHU 12-1SX7AGD 8.1.1.1 Yes, see
boxes for Siebel Search: “Instructions for
ACR 439” on
■ All these words
page 90.
■ Any of these words

■ Exact Phrase

■ None of these words

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 62 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When users log in to Call Center, 12-1SX7AF4 12-1SW7MFH 8.1.1.1


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
detected an Error which may
have occurred for one or more of
the following reasons: The
selected search result cannot be
found.(SBL-SRH-00167)"

ACR 452: Exact Phrase search 12- 12-1SW7MAD 8.1.1.1


does not work 1SW7MBM

ACR 403: After a Business 12-1SVPBQO 12-1SVPBOZ 8.1.1.1


Component has been indexed,
users are unable to drill down on
search results, and the Mobile
Web Client must be restarted

ACR 452: Packages the 12-1STTMVR 12-1STTMUS 8.1.1.1


Search_Engine_Config.xml and
ACR452_Seed_Import.dat files
for the 8.1.1.1 Fix Pack

ACR 452: Searching on 12-1SN2A27 12-1SINAGI 8.1.1.1


filesystem records (Filesystem
connector configured through
Remote Administration) yields
no results

ACR452: SES Integration 12- 12-1S0YCKL 8.1.1.1 Yes, see


uptake: Remote Administration 1SMKDVD “Instructions for
configuration ACR 452” on
page 95.

The application hangs when 12-1SJ62UA 12-1OUTTD2 8.1.1.1


users click the Advanced Search
link in the Search pane

After ACR 403 has been 12-1SJ62U0 12-1R4A0N4 8.1.1.1


installed, users are unable to
find the 'Admin-Mobile Search'
screen after running the dataimp
utility

622 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Within Call Center, when users 12-1SLL019 12-1SLL00K 8.1.1.1


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

Improves the usability of the 12-1SF7RL4 12-1SF7RJR 8.1.1.1


'SBL-SRH-50049' error message

ACR 403: The 12-1S78VAI 12-1QR8QLH 8.1.1.1


discon_symbstring.sif and
Disconnected.sif files are
missing from TOOLS\REPPATCH

ACR 439: The ACR439.sif folder 12-1S5T74H 12-1S5T73Q 8.1.1.1


is missing from Tools\REPPATCH

Within the Server_Manager 12-1S5B5AV 12-1S5B5AB 8.1.1.1


prompt, Component Search
displays as unavailable

Resolves a problem where the 12-1S1XV6F 12-1NK1UOB 8.1.1.1


Save Search button does not
work (ACR 403)

Incremental Index Processor 12-1RFD4GC 12-1ISHFB1 8.1.1.1


gives error SBL-OMS-00203
when there are no records to
process

(ACR403): Users are not able to 12-1RBZCL1 12-1NCHNBI 8.1.1.1


search for date ranges from the
Advance Search page

Within the application (on the 12-1RBZC7U 12-1PZ4263 8.1.1.1


Dedicated Client), when users
navigate to Administration -
Mobile Search > Search Index
Settings, select Solution (Call
Center) and click on Index, the
client crashes

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 62 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

After ACR 403 has been applied, 12-1RBI96O 12-1PZ42BP 8.1.1.1


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

After ACR 403 has been applied, 12-1RBI94M 12-1PZ42F9 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

After ACR 403 has been applied, 12-1RBI93M 12-1PZ42NW 8.1.1.1


using the Index All function
throws the error message
"Unable to load message
0x1(SBL-GEN-00001)

Searching on SR Attachments 12-1RBI92C 12-1PX52N2 8.1.1.1


does not work correctly

The seed_disconn files are not 12-1RBI919 12-1Q06HNN 8.1.1.1


getting created after the ACR403
patch for JPN has been applied

Refresh Indexing Search Objects 12-1QH55SI 12-1Q0IVZ5 8.1.1.1


for Oracle SES crashes the
Object Manager.

Security

624 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Include Mainwin 5.0.4 patch to 12-1T03XZ8 12-1SK50OF 8.1.1.1


enable certificates to work on
Unix

Port ACR329 Support of Security 12-1ROFZHA 12-1RDWN1J 8.1.1.1


Certificates in Mainwin

The AUTOCOMPLETE attribute is 12-1R1VGML 12-1PX49PY 8.1.1.1


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

Corrects a cross-site scripting 12-1R1VGM2 12-1LEFWYP 8.1.1.1


(XSS) vulnerability found with
default drilldown fields in the
high-interactivity application

LDAP Security adapter crashes 12-1QYIC79 12-1PE9R2X 8.1.1.1


when used with Global Catalog
parameters

Security Certificates with key 12-1Q35S5Q 12-1P56BSF 8.1.1.1


size larger than 4096 bits fail on
Unix

Mainwin fails to verify valid 12-1PI44YE 12-1PCDHM6 8.1.1.1


intermediate certificates

Server Infrastructure
Within Admin - Server 12-1TB8XS8 12-1TB8XQI 8.1.1.1
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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 62 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Connection requests disappear 12-1SN6XG9 12-1QXJEX5 8.1.1.1


between SCBroker and the
Object Manager

A SRProc crash/timeout occurs 12-1RAJ7XO 12-1QTP7FD 8.1.1.1


on server startup, and jobs
remain in the "Queued" state

Addresses a memory leak 12-1R759QW 12-1R759QB 8.1.1.1


related to Siebel Self-Service
Applications

Customappobjmgr tasks are 12-1R4AO4X 12-1R4AO4B 8.1.1.1


timing out and sessions are not
closed

The garbage collector crashes 12-1P4OFB1 12-1OVC1X9 8.1.1.1


during logoff when CTI is
enabled

Siebel Sync
SSSE Embedded Outlook 12-1QYIVKD 12-1NSKQ0N 8.1.1.1
Calendar fails on IE7

When a Siebel contact is enabled 12-1Q06AUV 12-1OFLUNH 8.1.1.1


for synchronization, and the
matching contact (first name,
last name, email address) exists
in Outlook, the existing contact
is not matched

ACR 369: Updates the 12-1O3Y6VC 12-1O1KGDB 8.1.1.1


permissions script to grant
permissions using Exchange
Shell

Provides the ability to use 12-1N1QJYA 12-1LTGS5B 8.1.1.1


Exchange as system of record for
calendar attendees

Task UI

626 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Pausing a task-based UI task 12-1R3BC6V 12-1Q5L8AP 8.1.1.1


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)

Manually populating certain 12-1QODIO5 12-1OH2I5T 8.1.1.1


columns in the Siebel S_PARTY
table may prevent some paused
Task UI items from appearing in
the Inbox

Tools / Configuration
Using the Edit Web Layout menu 12-1U57ONN 12-1TYAW7D 8.1.1.1
command in Siebel Tools causes
Siebel Tools to exit

Siebel Tools crashes while 12-1TK99PA 12-1THNFAT 8.1.1.1


compiling Siebel 8.0.0.5 QF0593

With the ST Engine turned on, 12-1QY0ZK6 12-1OJJKWB 8.1.1.1


the "with" statement does not
behave as expected

When script in an applet uses the 12-1QQAF3Y 12-1QBCBPP 8.1.1.1


this.InvokeMethod("WriteRecord
") syntax and an error occurs,
the event name displays instead
of an error message

The SetProperty control method 12-1QDRNTS 12-1PT56EL 8.1.1.1


with the Visible property can
only hide a control, regardless of
whether or not the value is True
or False

During LMU import, Siebel Tools 12-1Q4577F 12-1PPRMZF 8.1.1.1


stops and displays an error
message, and the user has to
click OK to terminate the
instance that is running

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 62 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Users experience problems when 12-1Q4576Z 12-1PPRMYV 8.1.1.1


running multiple sessions of
Siebel Tools on the same
machine while running LMU
imports

Code in PreInvokeMethod and in 12-1N1KM7F 12-1KDK35I 8.1.1.1


Declarations of Browser Script
causes popup applets not to
open

Upgrade
The datachk - Codepage tool 12-1RA1UL7 12-1RA1UJN 8.1.1.1
cannot handle multiple
repositories

When users run an upgrade 12-1RAKHWJ 12-1Q355KL 8.1.1.1


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

Upgrading from Siebel 8.1.1 SEA 12-1QRRBVH 12-1QT8DS1 8.1.1.1


to Siebel 8.1.1 SIA fails with the
following error message:
[DataDirect][ODBC Oracle
driver][Oracle]ORA-02296:
cannot enable (ORA17120.) -
null values found

Web Framework
Client-side logging does not 12-1Q3N50U 12-HPOMO0 8.1.1.1
perform correctly

Workflow
Upgrading or editing worflow 12-1TYBITJ 12-1PILZD3 8.1.1.1
processes resets properties for
other steps in the process

When workflow calls a sub- 12-1S9RQQJ 12-1P56A6N 8.1.1.1


process workflow which includes
an Siebel Operation to set field
values, an error is encountered

628 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When a subtask is called from a 12-1S3DS71 12-1NQOD87 8.1.1.1


main task, the application
crashes

Workflow processes based on 12-1RF7CDZ 12-1PE9QNX 8.1.1.1


runtime events may not pick up
lists of values

Life Sciences
Activity
When users try capture 12-1T9SI6C 12-1T9SI5L 8.1.1.1
signatures more than once in a
particular session, the
application crashes

Users are unable to multi-select 12-1OBLK4C 12-1NQ7LNP 8.1.1.1


and add multiple attendees to a
meeting

Data Migration
Incorrect transaction status is 12-1R75OVY 12-1Q72AR6 8.1.1.1
displayed in the sender's "Sent
Samples" view for records
migrated from previous Siebel
Life Sciences application
releases

Duplicate records display in the 12- 12-1Q72APO 8.1.1.1


Sample Pick Applet when users 1R75OUW
try to add a Line Items for In-
Progress Transactions from
Siebel Life Science application
versions prior to version 8.1.1

The system displays an error 12-1R75OTU 12-1Q72AO5 8.1.1.1


message when users try to
adjust "Processed" transactions
from previous Siebel Life Science
application releases

An error message displays when 12-1R75OSS 12-1Q72AMN 8.1.1.1


users try to acknowledge "In
Transit" transactions in Samples
> Received Samples

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 62 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Shipped Quantity for the 12-1R75ORL 12-1Q72AL7 8.1.1.1


"Processed with Discrepancies"
records in the Received Samples
does not show up correctly

The transactions for "Processed 12-1R75OQK 12-1Q72AJR 8.1.1.1


with Descrepancies" records do
not update to Processed status

When transactions are adjusted 12-1R75OPJ 12-1Q72AJ1 8.1.1.1


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

Other
Adds all of the 8.1.1 views to the 12-1TENX5R 12-1TENX4H 8.1.1.1
sia_options.txt file

Users are unable to save 12-1SJO29Z 12-1I3ER4T 8.1.1.1 Yes, see


campaign responses in the “Instructions for
Contact Call Detail view FR 12-1SJO29Z”
on page 734.

The Data Migration service 12-1R75OOH 12-1Q25Q6M 8.1.1.1 Yes, see


returns an error when executed “Instructions for
from a Workflow FR 12-1R75OOH”
on page 735.

Samples
Within the Pharma application 12-1TS6L62 12-1TS6L3P 8.1.1.1
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

No records display for Samples, 12-1R75OZ4 12-1Q8JEWD 8.1.1.1


Promotion Items, or Product
Details within the Sample
Management > Allocations and
Call Activities > Product Focus
screens

630 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Users are able to drop controlled 12-1R75OY2 12-1Q7IP1X 8.1.1.1


substances to an SRE exception
Contact Type for a State

Samples for Handheld


Inbox items are not created for 12-1R75P18 12-1QAH3KW 8.1.1.1
sample transactions that have
Disbursement Adjustment as the
type

Loyalty
Loyalty Customer
Portal
Updates Siebel Loyalty error 12-1QYIA05 12-1QDFKTJ 8.1.1.1
messages to provide more
detailed information about the
errors

Loyalty Engine
If accrual transactions with 12-1U5SIWR 12-1U5SIW7 8.1.1.1
expired points are canceled, the
point balance goes negative

When a member has a negative 12-1TUEX0T 12-1Q5L7UL 8.1.1.1


balance, when a member
redemption transaction is
cancelled, the point balance is
not updated correctly

Within the Loyalty Member 12- 12-1TDOGV5 8.1.1.1


screen, when users query for a 1TDOGWU
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

Accrual cancellation leads to 12-1T9RYZS 12-1T9RYZ1 8.1.1.1


used points having values
greater than their accrued value

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 63 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When users attempt to merge 12-1T7D8JJ 12-1T7D8HQ 8.1.1.1 Yes, see


two members in a Redemption/ “Instructions for
Accrual Cancellation Transaction, FR 12-1T7D8JJ”
they receive an error message on page 735.

Redemption Cancelation 12-1T7D8HE 12-1T7D8F3 8.1.1.1


Transactions with vouchers are
rejected in both the Transaction
UI and the Task UI

Improves the quality of Loyalty 12-1T6VXJE 12-1T6VXHT 8.1.1.1


application error messages

When users create a member, 12-1T6DMP5 12-1T6DMOL 8.1.1.1


navigate to Tier, and click
Process Tier Change, the
member is not promoted to a
new tier

Within the Loyalty application, 12-1SJ5HRQ 12-1SJ5HQ6 8.1.1.1


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)

Redemption cancellation overide 12-1S5BJ6K 12-1S5BJ59 8.1.1.1 Yes, see


points functionality should not “Instructions for
redeem extra points FR 12-1S5BJ6K”
on page 730.

Duplicate processing of objects 12-1R84WIL 12-1R8LQY9 8.1.1.1


by loyalty batch engine

Improves the overall 12-1R7NHCI 12-1QUO2ZN 8.1.1.1 Yes, see


performance of Batch Tier “Instructions for
processing FR 12-1R7NHCI”
on page 735,

632 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Duplicate tier processing occurs 12- 12-1QK0TP5 8.1.1.1


on the Linux platform 1R0WC2Q

When users configure a simple 12- 12-1QU76SD 8.1.1.1


frequency promotion and click 1R0WC2D
the Process button, they receive
the following error message:
Error invoking service 'LOY
Processing Engine', method
'SubmitObjectForProcessing' at
step
'InvokeSubmitObject':(SBL-
BPR-00162)

When a user has not performed 12-1QYI9WX 12-1Q3NKNZ 8.1.1.1


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

Loyalty Batch Engine processes 12-1QXAZCF 12-1P2S23P 8.1.1.1


records twice

There is a discrepancy between 12-1QK1D4H 12-1P18LL9 8.1.1.1


the point expiration date and
accrual cancellation process

Loyalty Manager
If accrued points have already 12-1RVNZS9 12-1RVNZQZ 8.1.1.1
been consumed, the transaction
cancellation should take the next
available accrual points

Provides a Web service to serve 12- 12-1PV3QSH 8.1.1.1


as a wrapper for Accrual 1R0WV7D
simulation calls

Auto creation of point blocks for 12-1QYI9WB 12-1Q3NIC7 8.1.1.1 Yes, see
prepaid partner is not working “Instructions for
FR 12-1QYI9WB”
on page 726.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 63 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Provides RTF template changes 12-1QYI9VW 12-1Q5L30R 8.1.1.1 Yes, see


to fix an issue where Voucher “Instructions for
Statements (VoucherIssue, FR 12-1QYI9VW”
Cancellation) are not displaying on page 726.
Issue Date & Expiration Date
correctly

An error message displays 12-1QYI9U5 12-1Q71LSD 8.1.1.1


whenever the 'Raise Dispute'
functionality is invoked for a
transaction

Language transalation issue and 12-1QYI9TU 12-1Q7IR96 8.1.1.1


requires code fix

Marketing
Campaigns
When upgrading from Siebel 12-1S2FFRD 12-1S2FFQT 8.1.1.1 Yes, see
application versions prior to “Instructions for
8.1.1 to Siebel 8.1.1 the FR 12-1S2FFRD”
segment trees that are more on page 730.
than one level deep with splits
are distorted

Changing a node on a segment 12-1QNF55C 12-1OD2S71 8.1.1.1 Yes, see


tree clears all of the allocation “Instructions for
information FR 12-1QNF55C”
on page 726.

Campaign Allocation applet does 12-1QAH5RH 12-1PV3ANX 8.1.1.1


not show correct counts when
segments are changed and
Refresh Tree is used

"Token Number" is corrupted 12-1ORVNY9 12-1O2HRQ9 8.1.1.1


when "Allow Repeated Contacts
Within Load" is checked

Email and Web


Marketing
Batch triggers do not pass the 12-1TYBKSS 12-1TYBKRT 8.1.1.1
correct set of customer IDs as
segmentation prompts

634 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Responses are not being 12-1TXC0I6 12-1TXC0GS 8.1.1.1


generated for automatic
trackable URLs

URL detector replaces image 12-1TVEKTK 12-1TVEKS3 8.1.1.1


source paths for all of the
graphics in the body of an email,
so the graphics are broken when
users save

HTML Editor incorrectly appends 12-1T30JMR 12-1NP9FJ9 8.1.1.1


HTTP prefix to links

Response loading is using first 12-1RNH75K 12-1NWCQ7S 8.1.1.1


name only to determine if the
contact exists

When users create a campaign 12-1RBI8H4 12-1R75VHI 8.1.1.1


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

When users create an offer and 12- 12-1QNF5R9 8.1.1.1


an email treatment, create a 1QVMOSS
campaign, attach the offer and
email treatment to the
campaign, and click Test
Treatment, they receive an error
message

Provides a mechanism to 12- 12-1M6V1A0 8.1.1.1


autogenerate Form HTML that 1QODWTG
can be embedded in custom
page

Not all URLs appear in the Verify 12-1QNF521 12-1P0SCHD 8.1.1.1


and Preview window

URLs are not automatically 12- 12-1NQ7TYV 8.1.1.1


trackable 1NQOGCK

Survey responses are not linked 12-1NQP3ON 12-1NLY66Z 8.1.1.1


to campaigns

Events

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 63 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Confirm Registration fails when 12- 12-1NC0KKJ 8.1.1.1


contacts were added to events 1NGQSNW
through campaign load

Marketing Server
Waves are assigned a single 12-1QY0YIW 12-1P81NNZ 8.1.1.1
record if the first wave setting
has 0% allocation

When contact planning rules are 12-1QNF549 12-1OD2S8L 8.1.1.1 Yes, see
defined for treatment channels, “Instructions for
mutual exclusion cannot be FR 12-1QNF549”
guaranteed completely on page 735.

SOAP arguments must be 12- 12-1K3ZEIQ 8.1.1.1


configured when using 1QMX8WH
Campaign Load to external
tables

Campaign Launch does not 12-1QMXRDI 12-1K3ZEFN 8.1.1.1


attempt to generate a list file
when there are zero contacts in
a Wave

Campaign Load not updating 12-1QMXR8X 12-1K1EYLP 8.1.1.1


Load Count when loading
external tables

The 'Date Scheduled' field for 12- 12-1H8HPIW 8.1.1.1


Campaign Wave does not 1QNEGM0
populate when a future date is
selected

Other
When users create an import 12-1R84VR3 12-1R7N6Z2 8.1.1.1
job, activate it, and then click
the Deactivate button while
processing is occurring, they
receive the following error
message: The selected record
has been modified by another
user since it was retrieved.
Please continue.(SBL-DAT-
00523)

636 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When no Prospect ID is passed in 12-1R7N6XZ 12-1R7N6O0 8.1.1.1


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’

During lead import, while trying 12-1QZXLZJ 12-1QZXLY0 8.1.1.1


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’”

Data mapping is not performed 12-1QZXLWZ 12-1QZXLVJ 8.1.1.1


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

When list import is performed 12-1QY0ZJ0 12-1NMF0K5 8.1.1.1


with a prospect ID that does not
exist, a new prospect is created

Event Trigger Execution results 12- 12-1QWLCMH 8.1.1.1


in huge memory consumption for 1QWLCO2
Workflow Process Manager

Programs
When users create a campaign 12-1S99AJC 12-1S99AIB 8.1.1.1
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'

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 63 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Within the Marketing application, 12-1RA4BEH 12-1OA5PY7 8.1.1.1


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

When users create a program 12-1QNF56F 12-1OA5UMP 8.1.1.1


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

Mobile Solutions
Handheld for Windows
Siebel application does not 12-1SW7Q25 12-1SREMMN 8.1.1.1
install on WM 6.1.4 devices, and
users receive an error message
stating that there are not
sufficient system permissions

Applying the Siebel Anywhere 12-1P2RFO0 12-1P2RFND 8.1.1.1


SRF upgrade kit causes
Handheld three-way sync to
hang

When a database is extracted 12-1QYI7IR 12-1IZLKDL 8.1.1.1


with the BCP file type, scripts
containing "\n" are wrongly
imported on the local database

Other
Wireless
When users create line items 12-1Q06NX7 12-1JJHDHH 8.1.1.1
within sales orders, duplicate
records are added

638 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Partner
Relationship
Management
Other
Users receive error messags 12-1SJNT7T 12-1SEQDDV 8.1.1.1
when they try to qualify a
prospective partner in the
Administrator Partner screen

Partner Manager
'Expertise' values are removed 12-1RAJ7UZ 12-1QZYA3H 8.1.1.1
after qualifying the Prospective
Partner

Partner Portal
Within the PRM Manager 12-1S8QDC7 12-1S8QDAZ 8.1.1.1
application, when users click
Shopping Cart, they receive the
following error message: We
detected an Error which may
have occurred for one or more of
the following reasons:
Unterminated value for attribute
'' in XML tag ''.(SBL-UIF

When users click the Shopping 12-1RIPG3X 12-1RIPG2H 8.1.1.1


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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 63 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When a cart is transferred, the 12-1RIPG1L 12-1RIPG01 8.1.1.1


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

When users attempt to transfer 12-1R8LV71 12-1L0FANB 8.1.1.1


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’”

Public Sector
Case Management
Under Verification Items list 12-1QRQ64V 12-1PLGBAO 8.1.1.1
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

Session warning error messages 12-1QCBH4O 12-1QCBH37 8.1.1.1


occur when users try to submit a
benefit case for approval

Other
Creates a source code .jar file 12-1TXC3HB 12-1T30JOF 8.1.1.1

Within the Public Sector Self- 12-1RNDGN5 12-1RGOB9N 8.1.1.1


Service application Suppor t>
Knowledge Base view, Search
functionality does not work

Sales
Forecasting

640 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

On the Forecast Details tab, the 12-1SCRNIJ 12-1S87JC1 8.1.1.1


AutoAdjust functionality is
greyed out on for the eleventh
record onwards while using the
single arrow on the vertical scroll
bar

Internet Explorer 7 crashes if the 12-1S1Y0WJ 12-1QMWX5R 8.1.1.1


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

On viewing subordinates' 12-1REV2P1 12-1PLH0DT 8.1.1.1


submitted forecasts from "My
Teams forecast" view, managers
cannot see data aggregated by
defined aggregation levels

Adjustment of subordinate 12-1Q626J5 12-1PE9QN3 8.1.1.1


forecasts (summary) with
percentages is not possible when
aggregation has been added

Opportunities
When users use the scroll bar to 12-1REV098 12-1QMFJR1 8.1.1.1
navigate to records within
Opportunity Record, data is not
saved in Revenue Line Items

Service
Other
The Action Business Component 12-1RBZC49 12-JX5I6Z 8.1.1.1 Yes, see
is hard coded to set the status of “Instructions for
an activity to Done when the FR 12-1RBZC49”
Done flag is checked or set to on page 737.
True

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 64 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Within the FRA Call Center 12-1QV5YIV 12-1PLGZZ3 8.1.1.1


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
the following error message:
“Unable to load message”

Dates in Activity Plans are not 12-1QTPTZT 12-1H6LL9V 8.1.1.1


being updated when the date is
edited

Within Field Service, the 12- 12-19VLZT3 8.1.1.1


isHoliday Business Service does 1QQ9WWM
not return the correct outputs

When users create an address 12-1QDRS0L 12-1POB949 8.1.1.1


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

Scheduling
GetElapsedBusinessTime API 12- 12-1DR0EUR 8.1.1.1
returns an incorrect result when 1Q2NN4M
there are multiple time zone
entries

Siebel E-
Commerce
Assets
Shipping and tax amounts are 12-1SW8FCN 12-1SW8FBB 8.1.1.1
not included in the Open Order
Total field

642 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

On the Asset Details page for 12-1QDSJ0J 12-1NVVGDB 8.1.1.1


Individual Accounts, the Bill To
Address field is not populated
correctly

Browse and Select


Within the Catalog page, when 12-1T03IPL 12-1SXP6NF 8.1.1.1 Yes, see
users navigate to Computer & “Instructions for
Office > Computers & Add-Ons > FR 12-1T03IPL”
Computer Software, provide a on page 738.
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."

Configurator
With a large number of users 12- 12-1RNY6ZZ 8.1.1.1
running the application 1ROWYK3
concurrently, users receive an
error message when they try to
configure the product

With a large number of users 12-1R3AUZS 12-1R1EKMX 8.1.1.1


running the application
concurrently, when users add
products to a car, configure
products, return to promotions,
or try to submit orders, they
receive the following error
message:
#{ConfigHandler.performAction
}:javax.el.Eval

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 64 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When users log in as B2B users, 12-1QKI5Z0 12-1QH5LF3 8.1.1.1


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

Provides a more useful error 12-1QGO85X 12-1QGO85B 8.1.1.1


message for minimum
cardinality violation errors

Miscellaneous
Self-Service Applications: Users 12-1T3ZEBN 12-1T3ZEAB 8.1.1.1
receive an error message when
they try to compile the
ErrorPageDirector.jsp file

Possible application error after a 12-1QDRWVI 12-1PBEJY2 8.1.1.1


session timeout in E-Commerce

Shopping Cart and


Checkout
The line-level Ship To account is 12-1TD34QN 12-1TD34PB 8.1.1.1
not updated when user selects
the Bill To and Sold To account

At Checkout, on the Shipping 12- 12-1L3YXAQ 8.1.1.1


and Billing page, session may 1QDSO0O
hang after session time-out.

644 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When users navigate to My 12- 12-1MQC54B 8.1.1.1


Account > Modify Service, drill 1QDSKCD
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

When a user creates a Shopping 12-1QDRVIG 12-1PEQUVR 8.1.1.1


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

The application can fail if the 12-1QDRIUP 12-1Q62WPC 8.1.1.1


Cart line amount exceeds
9,999,999.99 in the local
currency

Siebel E-
Commerce for
Comms
Assets
Within the Self-Service 12-1SSD2GO 12-1SSD2F8 8.1.1.1
application, Contact and Address
information is not refreshed
according to the account
selected in the Shipping Details
page

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 64 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Users cannot add promotions to 12-1S87JBI 12-1S87JA7 8.1.1.1


ABO-Shopping cart with default
selected products

The Address Line 2 field for the 12-1QFOVBV 12-1QFOVAJ 8.1.1.1


Bill To address of a secondary
user is incorrectly displayed as
the Address Line 2 field of the
parent record's Primary address

When users navigate to My 12-1QDS1DK 12-1P2RG2P 8.1.1.1


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

Browse and Select


Users cannot add a promotion to 12-1SMKT33 12-1SMKT1I 8.1.1.1
the shopping cart if they select a
Customizable Product without
having configured it first

Expand By Price does not display 12-1QDSJKB 12-1NSG9IG 8.1.1.1


the correct results

Configurator
A memory leak occurs 12-1SEPN3K 12-1SEPN2D 8.1.1.1

Miscellaneous
Provides a source code jar file to 12-1SXPC2R 12-1SXPC27 8.1.1.1
allow for overwrites

A memory leak occurs when "12- 12-1TXBUEZ 8.1.1.1


calling the "PSTOIntObjHier" 1TXBUGN
method of EAI Integration
Object to XML Hierarchy
Converter

646 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

The build XML does not include 12-1T5Q38F 12-1T5Q375 8.1.1.1


the "createsourcearchive"
target

With a large number of users and 12-1STSZ9X 12-1STSZ9B 8.1.1.1


both Product Promotion and
Customizable Product scenarios,
the application crashes

Within My Accounts > Modify 12-1QJ20GR 12-1QJ20FH 8.1.1.1


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

Within Packages > Configurable 12-1QDSK6D 12-1MV7OIM 8.1.1.1


Promotions, when users drill
down on the Millenium Max 500
Packages field, the "Make Your
Selection" option does not
appear

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 64 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When users navigate to the My 12-1NA4XY1 12-1MGRVT8 8.1.1.1


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

New Service
In new service activation (CP) 12-1QJ2KKN 12-1QJ2KJA 8.1.1.1
scenario, within the Products
page, the Gallery view should
display but the List view displays
instead

Users receive an error message 12-1QDRT9N 12-1PLH7MB 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

Order Status
When users upgrade from one 12-1REVTLR 12-1REVTL7 8.1.1.1
promotion to another, the data in
the order is incorrect

When users navigate to Order 12-1QKIA6G 12-1QKIA53 8.1.1.1


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

648 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Within the Review and Submit 12-1QJ2EH3 12-1QJ2EG6 8.1.1.1


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

Shopping Cart and


Checkout
When users navigate to Products 12-1TGNL80 12-1TGNL6P 8.1.1.1
> 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

When users log in, add a few 12-1T7V47Y 12-1T7V46N 8.1.1.1


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

Provides the web.xml file to 12-1QT7T1P 12-1QT7T15 8.1.1.1


synchronize the SIA application
to be consistent with the SEA
application

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 64 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Within Service screen > Forms 12-1QRQ65Y 12-1PYMH5M 8.1.1.1


> View Forms list applet, when
users click on the Form # column
to sort, the columns are no
longer visible

When users add products to the 12-1SQXAVL 12-1SQXAQE 8.1.1.1


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

When users add products to the 12-1SQXANV 12-1SQXAM3 8.1.1.1


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

650 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When users log in as B2B user, 12-1SGOEOJ 12-1SGOENZ 8.1.1.1


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

When users select a site, add an 12-1SD92ZF 12-1SD92YV 8.1.1.1


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

When a large number of users 12-1S7Q7ST 12-1R84CM9 8.1.1.1


are running the application
concurrently, the Submit button
is unavailable when users try to
place an order

Region Meta data information is 12-1S1XT6D 12-1S1XT5T 8.1.1.1


missing in the region-metadata-
telco.xml file, so there is no no
meta data information displayed
in the log files

When users click the Submit 12- 12-1ROWYMN 8.1.1.1


button on the Order Review 1ROWYNK
page, the order is placed but the
user is not navigated to the
Order Confirmation page

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 65 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When users log in as a B2B user, 12-1QZY3ZN 12-1QZY3YD 8.1.1.1


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

When users add a product into 12-1QX1W5J 12-1QX1W4A 8.1.1.1


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

When users add an item to the 12-1QJJD51 12-1QJJD3P 8.1.1.1


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

On the Review and Place Order 12-1QJ1VD0 12-1PFQ9UO 8.1.1.1


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

652 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When users log in as a B2C user, 12-1QFSBOF 12-1Q9ID59 8.1.1.1


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

When a user registers a new B2C 12-1QE9Z1F 12-1QE9Z0V 8.1.1.1


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

In the Shipping Details page, 12-1QE9TXJ 12-1QE9TW8 8.1.1.1


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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 65 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When users add a configurable 12-1QDSIK3 12-1N3LCM7 8.1.1.1


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

When users log in as a Child B2B 12-1QDS136 12-1P562C5 8.1.1.1


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

When users log in as the B2B 12- 12-1PCCTSH 8.1.1.1


primary user, navigate to the 1QDRWTF
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

Requested dates entered during 12-1QBC634 12-1QBC61Q 8.1.1.1


Asset Based Order checkout flow
are updated as the requested
date +1 in orders

Cannot add products to 12-1QCSND4 12-1Q5L6DJ 8.1.1.1


summary of changes page

654 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When users log in as B2B users, 12-1PBY7W6 12-1PBY7UV 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

User Accounts
For a secondary B2B user, the 12-1QDRH42 12-1Q9ICDR 8.1.1.1
Add New button is disabled for
Account Address in the Shipping
Details page

Within My Accounts > Company, 12-1QC7G4J 12-1QAY5O2 8.1.1.1


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

When a user completes 12-1PZOA1P 12-1PZOA15 8.1.1.1


registration from the Check Out
page, the user is not directed
back to the Check Out page after
they have completed registration

Siebel eMail
Response
General

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 65 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

On Linux, within Siebel eMail 12-1TUF2T5 12-1PLJFC3 8.1.1.1


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.

When users navigate to Site Map 12-1T5X07W 12-1T5X06E 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

When users create a contact with 12-1T5X03L 12-1QL02QT 8.1.1.1


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

Provides workflows in XML form 12-1T03SKH 12-1T03SI7 8.1.1.1


instead of as SIFs

Activities with Unscheduled 12-1SC99OY 12-1SC99NH 8.1.1.1


status are not handled
appropriately

656 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

After the exchange server has 12-1SC99ME 12-1SC99KJ 8.1.1.1


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

When users navigate to the All 12-1SC9947 12-1SC992E 8.1.1.1


Communication view, select any
"inbound email not started"
email, click Forward, draft text,
associate more than two
attachments, and then click the
Save as Draft button, the applet
goes blank and the Resume
button is disabled

Within the All Communications 12-1S1XVA8 12-1ONDKS9 8.1.1.1


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

Within the Communications 12- 12-1O5H0SV 8.1.1.1


screen, when users click the 1RB07WG
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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 65 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When users navigate to All 12-1RB07W2 12-1PIM03P 8.1.1.1


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

Within Administration > 12-1RB07VO 12-1Q0OYZB 8.1.1.1


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

When users send an inbound 12-1RB07VA 12-1Q3MVV7 8.1.1.1


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

658 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When the Remain on Same View 12-1RB07UW 12-1Q3MVVZ 8.1.1.1


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

Siebel Smart Answer


After ACR 367 has been 12-1T7V3ZK 12-1T7V3YV 8.1.1.1
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

ACR 476: Rebases Siebel eMail 12-1U0ACK7 12-1U0ACJH 8.1.1.1


Response support for
SmartAnswer support

Users are unable to close the 12-1T7V430 12-1T7V3ZT 8.1.1.1


Search applet

ACR 476: Reenables the Smart 12-1T7HMTB 12-1T5W64T 8.1.1.1


Answer component with the new
NLP engine

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 65 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 476: After the Smart 12-1T0ANU0 12-1T0ANT9 8.1.1.1


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

Siebel E-Support
Miscellaneous
A memory leak occurs during 12-1R1VRQO 12-1R1VRQ3 8.1.1.1
Order Management scenarios

Service Request
After solution types have been 12- 12-1U0DU1B 8.1.1.1
created in Call Center, indexed, 1U5UKMD
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
receive the following error
message: "No solution is found
based on your search criteria"

With a large number of users 12-1QYISGE 12-1QYISFT 8.1.1.1


running the application
concurrently, users are not
allowed to upload large (1MB)
attachments, and the "Failed To
Transmit Data to Network" error
message appears

Siebel Self Service


Common

660 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Deployment and
Packaging
The 811SelfService.ear data- 12-1RAJ02I 12-1RAJ01X 8.1.1.1
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

Miscellaneous
Users cannot navigate to the E- 12-1T30KEU 12-1T30KE9 8.1.1.1
Support tab in the Self-Service
Public Sector application

When users log in, select a site, 12-1SF7TYY 12-1SF7TXN 8.1.1.1


navigate to Payment Wallet,
select a payment profile, click
Edit, and then click Delete,
mandatory field valdiation
occurs

When users log in as B2B users, 12-1QDS1YB 12-1OMWFZH 8.1.1.1


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

User Accounts
Within the My Account > 12-1T6EAI0 12-1T6EAGP 8.1.1.1
Company > Contacts page,
users cannot add new contacts
by clicking the Add button

After a B2C user registers, the 12-1SD8ZCT 12-1SD8ZC9 8.1.1.1


application takes them to the
login page and not to the
confirmation page

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 66 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When users perform searches 12-1MBQKPK 12-1M4C4IF 8.1.1.1


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

User Management
When users log in as a B2B 12- 12-1PBY7ZX 8.1.1.1
primary user, login as b2b 1QDRWP8
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
the following error message:
Mandatory view criteria field(s)
Account Id missing in ContactVO

Travel &
Transportation
Other
ACR 488: When users create 12-1T5W51N 12-1T5W513 8.1.1.1
multiple quotes for multiple
properties, they receive an error
message

ACR 488: Prices added to menu 12-1T6DN88 12-1T6DN7O 8.1.1.1


items are not preceded by $
signs until the record is saved

ACR 488: When a Ctrl+B is done 12-1TENC2Y 12-1TDNULC 8.1.1.1


on a locked record, the copied
record is also locked

ACR 488: The Fixed Menu 12-1TK4121 12-1TK411F 8.1.1.1


Quantity field can be updated
even when it is listed under
Fixed Package

662 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

After the Event Template has 12-1TXC565 12-1TXC55L 8.1.1.1


been applied to an opportunity,
the opportunity's name does not
appear in the Histories view

Within Opportunities, 12-1U09B2J 12-1U09B19 8.1.1.1


subfunctions and their
corresponding line items are not
reflected at the quote level

When users check for copy 12-1U0BTMT 12-1U0B1E3 8.1.1.1


functionality when an arrival
date is less than the quote
arrival date, Internet Explorer
crashes

The administrator does not have 12-1TXTI9W 12-1TXTI8S 8.1.1.1


Edit Delete rights on the records
created by other users

System-generated records are 12-1TXC5DA 12-1TXC5B2 8.1.1.1


not read-only when viewed in
the Histories view

Within Histories view > Quotes 12-1TXC57S 12-1TXC56O 8.1.1.1


applet, the Status field is not
read-only

When users try to copy a 12-1TXC4ZH 12-1TXC4YX 8.1.1.1


function with an error number,
they receive an error message

ACR 450: Within Function Space 12- 12-1TUWYVC 8.1.1.1


Diary, verifying line item 1TUWYWS
attributes is failing

When users navigate to the FSD 12-1TS6LJ7 12-1TS6LIN 8.1.1.1


screen and click the Site Map
icon, the application crashes

ACR 488: When users select 12-1TK4H9V 12-1TK4H9B 8.1.1.1


Quote > Apply Event Template,
the operation fails

ACR 488: Provides Histories and 12-1TK3LUK 12-1QPT2Q7 8.1.1.1 Yes, see
Futures functionality “Instructions for
ACR 488” on
page 291.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 66 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 488: The Service End Time 12-1THO562 12-1THO555 8.1.1.1


field does not default to a
function's end time

ACR 450: The SR mapping 12-1THNM3U 12-1THNM2J 8.1.1.1


functionality only works for the
Contracted, Projected, and
Blocked fields

ACR 488: Within Opportunity > 12-1TG64N4 12-1TG64LV 8.1.1.1


Histories and Futures view >
Histories applet, Historical
Opportunities that have "Locked
Flag" = "Y" have the Delete
button disabled

ACR 488: Within the Quotes 12-1TGNKZM 12-1TGNKY6 8.1.1.1


screen, users are able to add
items to Fixed Packages

When users attempt to add 12-1TG66FT 12-1TG66EJ 8.1.1.1


information into the Specific
Space field, they receive an error
message and a blank row is
inserted

ACR 488: Billable Items are not 12-1TENSKV 12-1TENSDR 8.1.1.1


displayed in the Event Checks >
Guest Line items view

ACR 488: When users try to 12-1TE6G60 12-1TE6G47 8.1.1.1


enter information in the Function
Space field within the Function
list applet > Quote screen, they
receive an error message

ACR 488: Within the Histories 12-1TE6D2T 12-1TE6D1J 8.1.1.1


view, the application permits
users to check the locked field
for a Historical Opportunity
record, even if they are not the
creator of the record

ACR 488: Within the Histories 12-1TE6CZD 12-1TE6CY3 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

664 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Within the Room Blocks applet 12-1TE6CXE 12-1TE6CW4 8.1.1.1


within the Histories view, the
Actual vs Contracted and Actual
vs Blocked fields do not display
as percentages

ACR 488: The threadbar title 12-1TE6CVQ 12-1TCP4Y8 8.1.1.1


displays incorrectly for the
Histories and Futures views

ACR 488: When users create an 12-1TCP6GD 12-1TCP6F3 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).

ACR 488: Users are unable to 12-1TARYRO 12-1TARYQC 8.1.1.1


multiselect records from the pick
applets

ACR 488: Within the Quote > 12-1TD6ZRH 12-1TD6ZQV 8.1.1.1


Functions > Line Items view, the
Set System Allocation flag is
disabled

ACR 488: The System Allocation 12-1TD67KR 12-1TD67JL 8.1.1.1


flag should be read-only if the
package contain Split Menu
options

ACR488: Within Quote > 12-1TCOUBG 12-1TAR94G 8.1.1.1


Function > Line Item screen,
users are able to add items to a
fixed menu

ACR488: Columns are missing in 12-1TB8X2A 12-1TB8X0Y 8.1.1.1


the Historical Opportunity applet
and Histories View applet

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 66 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 488: Within the Histories 12-1TB9G5X 12-1TB9G4L 8.1.1.1


screen, copy functionality is not
working properly

Within the Property Pricing 12-1T7VA8A 12-1T7VA71 8.1.1.1


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

ACR 488: The Split Pricing field 12-1TAR8T1 12-1TAR8RB 8.1.1.1


remains unchecked even when
Split Menu Price is added to the
product

When users try to add new menu 12-1T9SIB5 12-1T9SIAL 8.1.1.1


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)

ACR 488: The "Histories" 12-1T7D8FX 12-1T7D8DP 8.1.1.1


checkbox is missing in the "Pick
Event Templates" dialog box

ACR 488: Users are unable to 12-1T7V61Y 12-1T7V60S 8.1.1.1


multiselect records from pick
applets

ACR 488: When users create an 12-1T5WR1X 12-1T3ZHD3 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
receive an error message

ACR 488: The setup style conflict 12-1T6EEB0 12-1T6EE9W 8.1.1.1


error message is not displayed

666 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 488: When users attempt to 12-1T6DN7J 12-1T6DN5J 8.1.1.1


sort menus within the Menu list
applet by Course #, they receive
an error message

Within Opportunities, the 12-1SJ5UDK 12-1SJ5UC3 8.1.1.1


Number of Days field in the
Capture Dates view allows users
to enter departure dates that are
before the arrival dates

Improves the quality of Travel 12- 12-1SJ5WV9 8.1.1.1


and Transportation application 1SJ5WWO
error message

When users add two functions in 12-1SG70W3 12-1SG70UT 8.1.1.1


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

Improves the usability of Travel 12-1SF7RJM 12-1SF7RI9 8.1.1.1


and Transportation application
error messages

ACR 450: The major header row 12-1S4TOQ9 12-1S2WL15 8.1.1.1


displays color for the first two
cells only instead of displaying
the weekend color for all cells
that display weekend
information

When a quote has a function, 12-1RXLGWP 12-1RXLGW1 8.1.1.1


subfunction, and complex line
items, the Copy Function
functionality does not work
properly

There is no non-null value in 12-1RV6UXD 12-1KPTT57 8.1.1.1


address attributes (such as Zip
code), so data cleansing does
not work

ACR 450: Within the Quote 12- 12-1RHR32C 8.1.1.1


Function Line Items view, there 1RHR32W
is no folder structure for menus

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 66 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Within eHospitality, when users 12-1RNY5E7 12-1RNY5DN 8.1.1.1


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

ACR 450: When users navigate 12-1RNH7PA 12-1RNH7OG 8.1.1.1


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

ACR 450 provides the following 12-1R8LRF4 12-1QJJCQN 8.1.1.1 Yes, see
enhancements: “Instructions for
ACR 456” on
■ Menus and Packages
page 97.
■ Function Space Displays

■ Inventory Display
Enhancements

■ Sleeping Room Mapping

ACR 488: Provides Histories and 12-1QPT2UA 12-1QPT2T1 8.1.1.1 Yes, see
Futures functionality for the “Instructions for
Siebel eHospitality application ACR 488” on
page 291.

Universal
Customer Master
Other

668 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 437: The System 12-1TK4S6F 12-1RBI2FT 8.1.1.1


Registrations view does not have
UI validations

ACR 437: Seed data import fails 12-1TK48IP 12-1T7V6FI 8.1.1.1


for JPN and NLD

ACR 437: Incorrect capitalization 12-1TK48HR 12-1T7D5IF 8.1.1.1


for the
OrganizationCrossReference
inbound Web Services causes
the operations to fail

ACR 437: The GetCrossRef 12-1TK42MX 12-1T7V6JE 8.1.1.1


operation fails for the
Organization, Person,
Household, and Financial Asset
Business Objects

ACR 437: Survivorship is not 12-1TJM79A 12-1TJM78P 8.1.1.1


invoked correctly

Provides the following 12-1SX7UBH 12-1RZPUB1 8.1.1.1


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

ACR 437: The PersonService > 12-1SX7UAP 12-1SD8MX5 8.1.1.1


GetPerson method fails to return
multiple records

ACR437: Includes the new 12-1SX7UAC 12-1RVNYWA 8.1.1.1


cross-reference module in
fasvccif.dll instead of in
sscaucmxref.dll

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 66 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 437/MDM: When users 12-1SX7U9X 12-1SSU75R 8.1.1.1


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

ACR437: The IsPrimaryMVG flg 12-1SWGZJ4 12-1SSU76Z 8.1.1.1


is not published for records
created/updated in UI in the
Acxiom flow

Within Siebel 8.1.1 QF0001 for 12-1SOZKT8 12-1RPF1Z9 8.1.1.1


ACR 437, the following two files
are missing from
ACR437_UCM.zip:
UCMMST811_seedimp_locale.in
p and seed_locale_NLD.dat

ACR 437: Acxiom DLL does not 12-1SOZKS8 12-1RRCAHM 8.1.1.1


have the latest code

ACR 437: The 12-1SOZKR6 12-1RR1O5N 8.1.1.1


UCMBusinessComponents.sif file
is not current, so Account/
Contact merge does not work

ACR 437: The incorrect versions 12-1SOZKP4 12-1QK1GG2 8.1.1.1


of libraries for Pubsub and
Transaction Mgr were provided

ACR 437: Provides the ability to 12-1SJO2V0 12-1M4CI03 8.1.1.1 Yes, see
expose CDI WebServices for all “Instructions for
CRUD operations on key entities ACR 437” on
such as Account, Contact, page 89.
Household, Financial Account,
and so forth

ACR 437 error message strings 12-1RSS7TV 12-1RPEN89 8.1.1.1 Yes, see
are not provided for languages “Instructions for
other than ENU ACR 437” on
page 89.

Publish/Subscribe

670 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 437: For Publish/Subscribe, 12-1SX7UB4 12-1RZPUA5 8.1.1.1


a crash occurs for multiple
thread workflows

ACR437: UNIX compilation fails 12- 12-1RVNYUP 8.1.1.1


at fasvccifpubsub.cpp 1SW1MC5

Publish/Subscribe fails to publish 12-1SOZKQ4 12-1RBHO55 8.1.1.1


messages to the AIA middleware
system when BDM workflows are
run

User Interface
Controls
Provides support for Internet 12-1RAJFVM 12-1RAJFUD 8.1.1.1.
Explorer 8 on Windows Vista.

Provides support for Internet 12-1RAJFTT 12-1RAJFT5 8.1.1.1


Explorer 8 on Windows XP SP3

Within Opportunities > 12-1TE6ABF 12-1TE6AAV 8.1.1.1


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

Allows the Turkish i-dot 12-1T4GEBF 12-1LEZF5Z 8.1.1.1


character to be handled correctly
in data queries (ACR 427)

Querying with the Toggle applet 12-1SSCZU6 12-1PAWXSH 8.1.1.1


in base mode causes the
application to refresh

Adding a script causes the 12-1SJNTJ7 12-1N3J10T 8.1.1.1


calendar control to display dates
without quotes

With Internet Explorer 8, the 12-1R1W13D 12-1PMW7JX 8.1.1.1


application-level menus and
applet menus do not work

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 67 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

ACR 422 provides the following 12-1PFQEKX 12-1N3ZXFY 8.1.1.1 Yes, see
enhancements: “Instructions for
ACR 422” on
■ Adds missing text for ALT
page 45.
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

Layout and Rendering


Within list applets, the Show 12-1SJ7NZM 12-1SJ7NYW 8.1.1.1
Less and Show More icons
behave incorrectly

When users create a new Activity 12-1SDQH8N 12-1EOTZ6O 8.1.1.1


and change its status to Done,
they receive the following error
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)"

672 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

In Standard Interactivity mode, 12-1QDSL8Y 12-1LSWNLF 8.1.1.1


the RTC Editor does not appear
in application HTML email
messages

When the AccessibleEnhanced 12-1QDS835 12-1O5H1CL 8.1.1.1


parameter for SI+ mode is
enabled, LOV values do not
appear, and screen readers
cannot read any values

Navigation
With Internet Explorer 8, the 12-1SD8N3Z 12-1RV6HKZ 8.1.1.1
browser's Back and Forward
buttons do not work

Other
Querying on the Account applet 12-1U4HH59 12-1TK7X5V 8.1.1.1
generates an extra query on the
Action Business Component

When users navigate to Site Map 12-1T5X05W 12-1T5X04K 8.1.1.1


> Administration Configuration
> Enterprise, navigate to
Component group, and perform
a query using the Query button,
they receive the following error
message: Method
PositionOnRow is not allowed
here.(SBL-UIF-00348)

Within the eHospitality 12-1SI6D5V 12-1SI6D4D 8.1.1.1 Yes, see


application, when users create “Instructions for
an opportunity from the ACR 456” on
Opportunity screen, click the page 97 and
Arrival Date applet to select an “Instructions for
arrival date, they receive an ACR 488” on
error message stating that UIF page 291.
cannot convert formatted strings
to the internal representation

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 67 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

After navigating backwards 12-1S1Y0HJ 12-1RUP3LT 8.1.1.1


through a Task-Based User
Interface (TBUI) Task using the
"Previous" button, the "Created"
date field may show an incorrect
date

Accessibility: After users have 12-1RUPLSL 12-1OQCG6I 8.1.1.1


implemented ACR 422 for
accessibility enhancements, the
Sales application UI does not
display correctly

Accessibility: Header markups 12-1RUPLS7 12-1OXBCNG 8.1.1.1


are missing

ACR 422: The 12-1RUPLR7 12-1PG7MQ4 8.1.1.1


Accessibility_Table.sif and
AdminScreen.sif files are
missing

The Ctrl+Shift+B keyboard 12-1RVO0Q4 12-1Q260FB 8.1.1.1


shortcut does not open the
Column Displayed popup window

Within Siebel Sales, when users 12-1RVO0PO 12-1PBVBQX 8.1.1.1


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 close the MVG,
and then press the Tab key, the
focus moves to the Contact
applet instead of to Status

Accessibility: Within Siebel 12-1RVO0P8 12-1PBVBMR 8.1.1.1


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

Accessibility:The text "Required" 12-1RVO0OS 12-1PAWFN5 8.1.1.1


needs to display at the end of
field names that are mandatory

674 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Accessibility: Corrects a defect 12-1RVO0OC 12-1PBDZME 8.1.1.1


that caused screen readers to
read the incorrect word first

Accessibility: In list applets, ">" 12- 12-1PBDZK6 8.1.1.1


and "select check box" do not 1RVO0NW
have a column heading

Accessibility: Only groups of 12-1RVO0NG 12-1PAWFOJ 8.1.1.1


fields, lists, or tables should
have headers--tabs and menus
should not

Accessibility: The Ctrl+Shift+K 12-1RVO0MI 12-1P9HAYP 8.1.1.1


keyboard shortcut opens
PlaceMarker List instead of the
Columns Displayed dialog box

Accessibility: The Ctrl+Alt+Z 12-1RVO0M2 12-1OXAV9N 8.1.1.1


keyboard shortcut does not
display View Name, View
Summary and Applet Name

Accessibility: Within Siebel Sales 12-1RVO0LK 12-1OUC5MI 8.1.1.1


> Projects > Notes, RTC Controls
are not displaying in the
Description field

Accessibility: Adjusts the color 12-1RVO0KU 12-1OUC5LC 8.1.1.1


contrast ratio for the "Remember
my User ID And Password"
dialog box

Accessibility: Within Siebel Sales "12- 12-1OK1S1R 8.1.1.1


> Opportunities, when users 1RVO0KC
navigate to Revenue: Calculator
and press the Tab key to
navigate to ".", the screen
reader reads this text as "link"
instead of as "period”

Accessibility: Adjusts the Color 12-1RU7S4M 12-1OD1CXK 8.1.1.1


Contrast Analyzer functionality
within Siebel Sales

Accessibility: Adjusts the color 12-1RUPLQT 12-1OE44M7 8.1.1.1


contrast between the foreground
and the background within the
Service application

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 67 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Accessibility: There is no 12-1RUPLQF 12-1OH39Y6 8.1.1.1


keyboard shortcut to navigate to
third-level tabs

Accessibility: Within the Service 12-1RUPLQ1 12-1OH39YW 8.1.1.1


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

Accessibility: Within the Service 12-1RUPLPN 12-1OXSNRF 8.1.1.1


application, when users navigate
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

Accessibility: After ACR 422 has 12-1RUPLP9 12-1P56CN9 8.1.1.1


been implemented, when users
log into the application and then
click on any of the screen tabs,
they receive the following error
message: Unable to create the
Business Service 'Chat UI
Business Service'(SBL-DAT-
00227)

Accessibility: After ACR 422 has 12-1RV6IUD 12-1ODJYLT 8.1.1.1


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

676 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Accessibility: The color contrast 12-1RV6IU1 12-1ODLAXL 8.1.1.1


ratio is not sufficient for
toolbars, buttons, and icons

Accessibility: Page spacers are 12-1RUPLOV 12-1PBVCGH 8.1.1.1


not identified with an empty ALT
attribute (ALT=")

Accessibility: Within the Service 12-1RV6ITR 12-1OGCKDV 8.1.1.1


application > Communication
tab, the color contrast for the
tabs that are not active is not
sufficient

Accessibility: Within the Service 12-1RUPLOH 12-1PBVCJQ 8.1.1.1


application > Home Page,
spacers are not specified with an
empty ALT attribute (ALT=")

Accessibility: When users press 12-1RV6ITH 12-1OGLD07 8.1.1.1


Ctrl+Alt+T to navigate to the
View tab, the focus moves to
screen applet rather than the
View tab

Accessibility: Within the Service 12-1RUPLO3 12-1PBVCOT 8.1.1.1


application > Home Page screen,
spacers are not specified with an
empty ALT attribute (ALT=")

Accessibilty: Within CTI, when 12-1RV6IT4 12-1OQV78V 8.1.1.1


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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 67 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Accessibility: Within CTI, when 12-1RV6ISS 12-1OQV7BL 8.1.1.1


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

Accessibility: The Email Text edit 12-1RV6ISI 12-1OTU6CJ 8.1.1.1


field is not available

Accessibility: Within the My 12-1RV6IS8 12-1OUZSZS 8.1.1.1


Templates screen, the screen
reader reads the "HTML
Template" checkbox as the
"Public checkbox”

Accessibility: Within the Call 12-1RV6IRY 12-1PBEKVL 8.1.1.1


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

678 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Accessibility: Within the Call 12-1RV6IRO 12-1PBEKWS 8.1.1.1


Center application, when users
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

Accessibility: Within the Call 12-1RV6IRE 12-1PBE210 8.1.1.1


Center application, when users
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

Accessibility: The Help System is 12-1RV6IR4 12-1PG7NRG 8.1.1.1


not available

Accessibility: In Service > 12-1RUPLNP 12-1PBVCQJ 8.1.1.1


Invoice, spacers are not
specified with an empty ALT
attribute (ALT="")

Accessibility: Within the Call 12-1RV6IQI 12-1PI4IRN 8.1.1.1


Center application, when users
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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 67 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Accessibility: When users 12-1RUPLNB 12-1PBVCT3 8.1.1.1


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="")

Accessibility: The screen reader 12-1RUPLMX 12-1PJ3BJ3 8.1.1.1


reads ".....DFLT...." as a applet
summary

Accessibility: Within the Call 12-1RV6IQ8 12-1PJ2SAV 8.1.1.1


Center application, when users
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

Accessibility: Within the Service 12-1RUPLMJ 12-1PMFGQP 8.1.1.1


application, when users initiate
the IE Developer Toolbar from
within the Home Page, and
select Images > View Alt Text, all
spacers are not specified with an
empty ALT attribute (ALT="")

Accessibility: Within any Siebel 12-1RUPLM5 12-1Q0P7T3 8.1.1.1


application, when users navigate
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

680 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Accessibility: Within the Call 12-1RV6IPX 12-1PJ2SCU 8.1.1.1


Center application, when users
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

Accessibility: Within Siebel 12-1RU7S3L 12-1PYEFBL 8.1.1.1


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

Accessibility: Within the Siebel 12-1RUP2XC 12-1Q2MXXG 8.1.1.1


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
receive an error message

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 68 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Accessibility: Within the Siebel 12-1RUP1FX 12-1PBVCN3 8.1.1.1


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
spacers are not specified with an
empty ALT attribute (ALT="")

Accessibility: Within the Siebel 12-1RUP2W9 12-1OYTDIR 8.1.1.1


Public Sector application, when
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

Accessibility: Within the Siebel 12-1RUP2VU 12-1PILJI1 8.1.1.1


Public Sector application, when
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

Accessibility: Within the Siebel 12-1RUP2VF 12-1PS5Z73 8.1.1.1


Public Sector application, when
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...:"

682 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Accessibility: Within the Siebel 12-1RUP2V4 12-1Q25XIX 8.1.1.1


Public Sector application, when
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

Accessiblity: Within the Siebel 12-1RUP2UP 12-1Q3N2WK 8.1.1.1


Public Sector application, the
Query, Cancel, and Delete
buttons are missing from some
of the screens

Accessibility: Within the Siebel 12-1RSAOI2 12-1Q905IV 8.1.1.1


Public Sector application, when
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

Accessibility: For the Siebel 12- 12-1QZY9D9 8.1.1.1


Public Sector application, when 1RSAOHM
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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 68 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Accessibility: Within the Siebel 12-1RSAOHD 12-1R0F1JX 8.1.1.1


Public Sector application, when
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

Accessibility: Within the Siebel 12-1RSANEG 12-1PI40XY 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="")

When users log into Siebel Sales 12-1RSANCE 12-1OGKNKN 8.1.1.1


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)

Accessibility: In Service 12-1RSAN9A 12-1PBVCKS 8.1.1.1


Requests, the spacers are not
specified with an empty ALT
attribute (ALT="").

Accessibility: Within the Comm 12-1RSAN79 12-1PI40ZP 8.1.1.1


Inbound Item Body applet,
spacers are not specified with an
empty ALT attribute

684 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

Accessibility: In the My 12-1RSAN67 12-1PI4112 8.1.1.1


Templates view, the spacers are
not specified with an empty ALT
attribute

The <Accessibility>Page 12-1ROFVKG 12-1ROFVJ1 8.1.1.1


download confirmation message
should be disabled by default

Accessibility: Within the Siebel 12-1ROFVIQ 12-1ROFVHH 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

If a user closes a tabbed 12-1R1VGKZ 12-1NCHOM7 8.1.1.1


browsing window in Internet
Explorer 7 by clicking on the X,
then the window closes but the
Siebel session is not logged out

Object Manager crashes when 12-1QUO1AN 12-1QMXGFN 8.1.1.1


attempting to Export Tab Layout

Popups/Pick Lists/
MVG/Shuttle
When users try to undo a query 12-1T6DTOD 12-1T6DTMX 8.1.1.1
after typing in a set of
characters, they receive the
folllowing error message:
"Method UndoRecord is not
allowed here. (SBL-UIF-00348)”

Personalization rules do not work 12-1SZMOB5 12-1P5N6JM 8.1.1.1


on Association applets

With Internet Explorer 8, when 12-1SF7XSB 12-1S99GIP 8.1.1.1


users navigate to any views,
they receive the following error
message:
'navigator.SWE_historyKeys.123
5411125328' is null or not an
object

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 68 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

With Internet Explorer 8, the Ctrl 12-1SF7XRC 12-1SF7XQL 8.1.1.1


+ D shortcut opens "Add a
favorite" instead of deleting the
record in the Attachments applet

With Internet Explorer 8, when 12-1S9RQYV 12-1RU7S2V 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

Within Internet Explorer 8, 12-1SC3OFC 12-1SC3OEN 8.1.1.1


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

Minimizing or maximizing 12-1SC96ZX 12-1P19TU1 8.1.1.1


Internet Explorer 7 when on a
Multi-Value Group causes the
application to crash

With Internet Explorer 8, when 12-1SC95S7 12-1SC95RI 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

With Internet Explorer 8, using 12-1SC95R6 12-1SC95PX 8.1.1.1


the CTRL + L keyboard shortcut
opens the Open popup window
instead of the Correspondence
window

686 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Table 19. Resolved Change Requests in the 8.1.1.1 Fix Pack

Fix Request Change Fixed in Configuration


Issue Addressed ID Request ID Version Instructions

When duplicating a record in the 12-1OK0ULQ 12-1OK0UL5 8.1.1.1


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.

Web Service
Other
Within Siebel Tools, when users 12-1RH8IMZ 12-1PG7NLN 8.1.1.1
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)

Integrating attachments does 12-1RH8IMO 12-1LTG2F6 8.1.1.1


not work when WS-Security is
used

Instructions for FR 12-1ZFE3KR


Within My Oracle Support, navigate to the Knowledget tab, and search for Doc 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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 68 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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:

688 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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


1 Within Siebel Tools, navigate to the LOY Members project, and lock it.

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

1 Within Siebel Tools, navigate to the LOY Members project, and lock it.

2 Create a new business component with the following details:

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 68 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

❏ Name: LOY Merge Transaction

❏ Project: LOY Members

❏ 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 BIP_LS_Protocol_Document_Tracking.sif 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 wcalled Protocol Level Document Tracking and associate it with the template
(.rtf file) available for that report. Select Output type as "All".

8 In the XLIFF field, upload the xliff file corresponding to the report.

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.

690 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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 view where you want to
see the report.

Instructions for FR 12-1P4ORN3


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 new record with
the following values:

❏ Column Name: Login User

❏ Calculated Field: Checked

❏ Calculated Column: LoginName()

❏ Column Type: "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 Enhancement project

5 Import BIP_LS_Region_Document_Tracking.sif 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 and associate it with the template (.rtf file) available for that report. Select
Output type as all.

8 In the XLIFF field, und upload the xliff file corresponding to the report.

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 view where you want
to see the report.

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.

3 If the field "Login User field does not already exist, within the Field section of the LS Document
Tracking business component, create a new record with the following values:

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 69 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

❏ Column Name: Login User

❏ Calculated Field: Checked

❏ Calculated Column: LoginUser()

❏ Column Type: "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 Protocol Site project.

5 Unzip the zipped file, import "BIP LS Clinical Protocol Site.sif", and compile the SRF.

6 Within the Siebel application, navigat to Site Map >Administration - BI Publisher Reports->
Reports - Standard Templates.

7 Create a new report and associate it with the template (.rtf file) available for that report. Select
Output type as all.

8 In the XLIFF field, upload the xliff file corresponding to the report.

9 Navigate to 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 Clinical Protocol Site".

11 Navigate to Administration - BIP Report > View Association, and associate the view where you
want to see the report.

Instructions for FR 12-1P4ORMD


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.

3 If the Login User field does not already exist, 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: Checked

❏ Calculated Column: LoginName()

❏ Column Type: "DTYPE_TEXT"

Leave the rest of the entries in the default state.

4 Make the following changes for Indication Display:


a Within Object Browse, under Business Component navigate to Join and create a new record with
the following values:
❏ Table: S_CL_PGM_APP_LS

❏ Alias: S_CL_PGM_APP_LS

692 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

b Navigate to Join Specification, and create a new record with the following values:

❏ Name: Application Id

❏ Source Field: Application Id

c Save the record.

d 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

e Save the record.

f Within Object Browse, under Business Component, navigate to Field, and create a new record
with the following values:

❏ Name: Protocol Program Indication

❏ Join: S_CL_PGM_APP_LS

❏ Column: INDICATOR_CD

❏ PickList - Clinical Program Indication Picklist

g Save the record.

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


the LS Clinical Protocol Site project.
b Import Clinical Protocol Site.sif.

6 Get the sif files from $TOOLS_PATH/REPPATCH/811x_FP_LS_Clinical_BIP_Reports.zip and lock


the LS Clinical Protocol Site project.

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->
Reports - Standard Templates.

10 Create a new report and associate it with the template (.rtf file) available for that report. Select
Output type as all.

11 In the XLIFF field, upload the xliff file corresponding to the report.
12 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.

13 In the Integrations Objects tab, within the Integration Object Name field, query for BIP LS
Clinical Protocol Site.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 69 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

14 Navigate to Administration-BIP Report > View Association, and associate the view where you
want to see the report. Here we want to see the report in "Clinical Protocol Site List View",
"Clinical Protocol Site Manager's List View", and "Clinical Protocol Site All List View". So we
associate this view here.

Instructions for FR 12-1P4ORM0


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.

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 Name: Login User

❏ Calculated Field: Checked

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

5 Unzip the zipped file, import the BIP_LS_Site_Enrollment_Status.sif, and compile the SRF.

6 Witin the Siebel application, navigate to Site Map > Administration - BI Publisher Reports >
Reports - Standard Templates.

7 Create a new report and associate it with the template hat with Template (.rtf file) available for
that report. Select Output type as all.

8 In the XLIFF field, click and upload the xliff file corresponding to the report.
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 view where you want
to see the report.

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

694 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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.

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

❏ Calculated: LoginName()

❏ Type Column: "DTYPE_TEXT".

Leave the rest of the entries in the default state.

4 Query for the Clinical Protocol Site business component.

5 Lock the LS Clinical Protocol Site project.

6 If the Login User field does not already exist, create a new record with the following values in
the Field section of the Clinical Protocol Site business component:

❏ Column Name: Login User

❏ Calculated Field: Checked

❏ Calculated: LoginName()

❏ Type Column: "DTYPE_TEXT".

Leave the rest of the entries in the default state.

7 Get the sif files from $TOOLS_PATH/REPPATCH/811x_FP_LS_Clinical_BIP_Reports.zip and lock


the LS Clinical Protocol Site project

8 Unzip the zipped file, import BIP Site Initiation By Site.sif, and compile the SRF.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 69 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

9 Within the Siebel application, navigate to Site Map > Administration - BI Publisher Reports >
Reports - Standard Templates.

10 In the XLIFF field, click and upload the xliff file corresponding to the report.
11 Create a new report and associate that with the template (.rtf file) available for that report.
Select Output type as all.

12 In the Translations tab, query for "BIP Site Initiation By Site" in the Integration Object name field
and select it.

13 In the Translation tab, create a new record and pick the desired language and report name for
which the translation is required.

14 Navigate to Administration - BIP Report > View Association and associate the view where you
want to see the report.

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

6 Compile the LS Pharma Common object.

The Protocol Drilldown Object

Name Protocol
Source Field Id

The Protocol With Regions Drilldown Object

Name Protocol With Regions

Source Field Id

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

696 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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


■ 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

Field Protocol Title

Display Name - String Reference SBL_TITLE-1004225657-02U

Table 2: For Form Applets- Applet > Control

Field Protocol Title

Caption - String Reference SBL_TITLE-1004225657-02U

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 69 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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


1 Within Siebel Tools, navigate to the LOY Members project, and lock it.

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

❏ Project: LOY Members

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

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

698 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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 you are 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

Field Name Calculated Calculated Value Join Column Type Text Length

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 69 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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

IMPORTANT: 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 Property 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:

Field Name Calculated Calculated Value Join Column Type Text Length

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

700 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

❏ 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 Doc 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-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:

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 70 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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

■ 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


1 Log into Siebel Tools.

702 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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

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.

a Navigate to the Integration Field Map applet (the lower applet).

b Within Target Field Name, query for Protocol Position Assignment Type.

c Delete the record.

6 Query for "Clinical Site Position to Region Position Map1" in Integration Object Map.

a Navigate to the Integration Field Map applet (the lower applet).

b Within Target Field Name, query for Region Position Assignment Type.

c Delete the record.

7 Query for "Clinical Region Position to Protocol Position Map1" in Integration Object Map.

a Navigate to the Integration Field Map applet (the lower applet).

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 70 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

b Within Target Field Name, query for Protocol Position Assignment Type.

c Delete the record.

8 Query for "Clinical Region 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.

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

New/ Value/Search Specification


Modified? Value/Search Specification (Old) (New)

Modified [Clinical Protocol_Position.Sales Rep] '"'[Clinical Protocol_Position.Sales


=' + '"' + [&SalesRep] + '"' + ' AND Rep] =' + '"' + [&SalesRep] + '"' +
[Clinical Protocol_Position.Protocol ' AND [Clinical
Position Assignment Type] <> "Region Protocol_Position.Position Id] =' +
Position Rollup" AND [Clinical '"' + [&PositionId] + '"'
Protocol_Position.Protocol Position
Assignment Type] <> "Site Position
Rollup" AND [Clinical
Protocol_Position.Position Id] =' + '"'
+ [&PositionId] +

■ Workflow Name: Clinical Assign Position From Region Rolldown

■ Workflow Step: Query Region Position

704 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

■ Workflow Step Input/Output Arguments: SearchSpec

New/ Value/Search Specification


Modified? Value/Search Specification (Old) (New)

Modified [Clinical Region_Position.Sales Rep] =' '"'[Clinical Region_Position.Sales


+ '"' + [&SalesRep] + '"' + ' AND Rep] =' + '"' + [&SalesRep] + '"'
[Clinical Region_Position.Region + ' AND [Clinical
Position Assignment Type] <> "Protocol Region_Position.Position Id] =' +
Position Rolldown" AND [Clinical '"' + [&PositionId] + '"'
Region_Position.Region Position
Assignment Type] <> "Site Position
Rollup" AND [Clinical
Region_Position.Position Id] =' + '"' +
[&PositionId] +

■ Workflow Name: Clinical Assign Position From Region

■ Workflow Step: Query Region Position

■ Workflow Step Input/Output Arguments: SearchSpec

New/ Value/Search Specification


Modified? (Old) Value/Search Specification (New)

Modified [Clinical Region_Position.Sales '"'[Clinical Region_Position.Sales Rep]


Rep] =' + '"' + [&SalesRep] + '"' =' + '"' + [&SalesRep] + '"' + ' AND
+ ' AND [Clinical [Clinical Region_Position.Position Id]
Region_Position.Region Position =' + '"' + [&PositionId] + '"
Assignment Type] <> "Protocol
Position Rolldown" AND [Clinical
Region_Position.Region Position
Assignment Type] <> "Site
Position Rollup" AND [Clinical
Region_Position.Position Id] =' +
'"' + [&PositionId] +

■ Workflow Name: Clinical Assign Position From Site Rollup

■ Workflow Step: Query Site Position

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 70 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

■ Workflow Step Input/Output Arguments: SearchSpec

New/ Value/Search Specification


Modified Value/Search Specification (Old) (New)

Modified [Clinical Protocol Site_Position.Sales '"'[Clinical Protocol


Rep] =' + '"' + [&SalesRep] + '"' + ' Site_Position.Sales Rep] =' + '"' +
AND [Clinical Protocol [&SalesRep] + '"' + ' AND [Clinical
Site_Position.Site Position Assignment Protocol Site_Position.Position Id]
Type] <> "Protocol Position Rolldown" =' + '"' + [&PositionId] + '"'
AND [Clinical Protocol
Site_Position.Site Position Assignment
Type] <> "Region Position Rolldown"
AND [Clinical Protocol
Site_Position.Position Id] =' + '"' +
[&PositionId] +

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.

LS Pharma My Sample Lots List Business Component

New/
Modified Search Specification (Old) Search Specification (New)

Modified [Is Product Allocation Type] = 'Y' [Is Product Allocation Type] = 'Y' AND
AND [Is Stock Employee Id - [Owned By Id] = LoginId() AND [Stop
Owned by Id] = 'Y' AND [Is Stop Sampling Flag] =
Sampling Active Period Flag] = 'Y' LookupValue("BOOLEAN_VALUE","N") AND
AND [Is Lot Product Type] = 'Y' (([Active Flag] = LookupValue
AND [Is Lot Stock] = 'Y' AND ("BOOLEAN_VALUE","Y") and [Is Stock
[Inventory Audit Report Id] IS Employee Id - Owned by Id] = 'Y' AND [Is
NULL 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)))

706 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Fields

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

Join

Outer Join Flag Outer Join Flag


New/Modified? Name (Old) (New)

Modified S_STK_PERD_EMP N Y

Modified S_STOCK_EMP N Y

LS Pharma My Promotional Items List Business Component

New/
Modified? Search Specification (Old) Search Specification (New)

Modified [Is Product Allocation Type] = [Is Product Allocation Type] = 'Y' AND [Owned
'Y' AND [Is Stock Employee Id - By Id] = LoginId() AND [Stop Sampling Flag] =
Owned by Id] = 'Y' AND [Is LookupValue("BOOLEAN_VALUE","N") AND
Stop Sampling Active Period (([Active Flag] = LookupValue
Flag] = 'Y' AND ([Inventory ("BOOLEAN_VALUE","Y") and [Is Stock
Audit Report Id] IS NULL) Employee Id - Owned by Id] = 'Y' AND
[Inventory Audit Report Id] IS NULL) OR
(([Inventory Flag] = 'N' OR [Inventory Flag] IS
NULL)))

Fields

New/Modified? Name Join Column

New Inventory Flag S_PROD_INT INVENTORY_FLG

New Inventory Id S_STOCK_EMP ROW_ID

Join

Outer Join Flag Outer Join Flag


New/Modified? Name (Old) (New)

Modified S_STK_PERD_EMP N Y

Modified S_STOCK_EMP N Y

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 70 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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.

708 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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 year’s
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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 70 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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


Changes for the CG SVP Product Baseline-Aux business component:

Business Component User


Properties Value Comments

Build Tree 3 Incremental Cases This property should already


exist

Build Tree Include Cat Y Add this property if it does not


Aggregation Info already exist

Category Aggregation Field 1 "Promotion Incremental Qty", Add this property if it does not
"Incremental Cases” already exist

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 n Target Field n is the next number of this


('Build Tree') property.
In this case, "CalcTestStorage
Cases" Users need to add this for the
new custom column.

710 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Business Component User


Properties Value Comments

Build Tree Include Cat Y Add this column if it does not


Aggregation Info already exist.

Category Aggregation Field n "Source Field", "Target Field" n is the next number of this
('Category Aggregation Field')
In this case, "CalcTest",
property.
"CalcTestStorage Cases"
Users need to add this value for
the new custom column.

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:

New? Name User Name Default Physical Type Nullable Length Required

New? Name User Name Default Physical Type Nullable Length Required

Table: S_SRC_PAYMENT (Modified)

Columns:

Physic Nullabl
New? Name User Name Default al Type e Length Required

Yes VOID_FLG Void Flag N Charact No 1 Yes


er

Business Components
Name: FS Invoice

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 71 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Description:. Add a user property, which will be used to void the invoice and copy the fields.

New? Name Details

No FS Invoice

BC User Property:

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

Name: FS Invoice Line Items

Description:. Add a user property, which will be used to void the invoice and copy the fields.

New? Name Details


No FS Invoice Line Items

BC User Property:

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

Name: FS Invoice Line Item Details

712 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Description: Add a user property, which will be used to void the invoice and copy the fields.

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

Name: FS Invoice Payments

Description: Add a flag for the voided status of these payments.

New? Name Details

No FS Invoice Payments Table: S_INVC_PAYMENT

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 71 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Field:

New? Name Details

Yes Void Flag Column: VOID_FLG

Pre Default : N

Required :Y

Type:DTYPE_BOOL

Name: CS HH FS Payments

Description: Add a flag for the voided status of these payments.

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

Applets
Name: SIS HH FS Invoice Form Applet - CE

Business Component: FS Invoice

Description: Enable the existing Void button.

New? Name Details

No SIS HH FS Invoice Form Applet - CE

Column:

New? Name Details

No VoidInvoice Enable: Y

Minibutton

714 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Name: CG Invoice Payments List Applet - CE

Business Component: FS Invoice Payments

Description: Add the newly added 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

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.

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

Name: CS CG Invoice Form Applet

Business Component: FS Invoice

Description: Add the Void flag.

New? Name Details

No CS CG Invoice Form Applet

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 71 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Column:

New? Name Details

Yes Void Flag Type: CheckBox

Field: Void Flag

ReadOnly:T

Name: CS CG Invoice Payments List Applet

Business Component: FS Invoice Payments

Description: Add the Void flag.

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

Name: HH CG Undeposited Payment List Applet CE

Business Component: CS HH FS Payments

Description: Change the search specification of the applet.

New? Name Details

No HH CG Undeposited Search Specification : ([Void Flag] <> 'Y') AND ([Deposited Flag]
Payment List Applet CE <> 'Y') AND ([Payment Method] <> LookupValue
("PAYMENT_METHOD_CODE", "Credit Memo") OR [Payment
Method] IS NULL)

Name: CS HH Invoice Pymt Reconcile List Applet - CE

Business Component: CS HH FS Payments

716 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Description: Change the search specification of the applet.

New? Name Details

No CG Invoice Payments List Applet - CE Search Specification : [Created By] = LoginId ()


AND [Created] = Today () AND ([Void Flag] <> 'Y'

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 71 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

Instructions for FR 12-1U5UH3L


Use the following procedure to implement this fix:

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


Use the following procedure to implement this fix.

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.

718 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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


1 Log into Siebel Tools.

2 Within Object Explorer, navigate to Project, query for LS Clinical Protocol Site, and lock the
project.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 71 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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
with the following values:

❏ System Preference Name: Append Template to Email Body

❏ System Preference Value: 1

❏ [ 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:

720 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 72 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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


Use the following procedure to implement this fix:

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


Use the following procedure to implement this fix:

1 Navigate to the location in which you have installed the Mobile Web Client, navigate to
siebsrvr\XMLP\TEMPLATES, and open MOBUSRSUM.xsl.

722 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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>

<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="1" 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"></fo:inline>

</fo:block>

</fo:table-cell>

<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="1" 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"

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 72 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

3 Replace the section with the following 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="4" 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>

<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="1" 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">

724 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

4 Search for the following section:

TIP: Search for keyword=ssRouteGroupName.

<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="2" 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">

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

<fo:inline font-size="9.0pt" white-space-collapse="false" height="9.0pt" font-


family="Arial">

<xsl:value-of select=".//ssFirstNamex" xdofo:field-name="ssFirstNamex"/>

</fo:inline>

</fo:block>

</fo:table-cell>

<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="1" 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">

<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-
indent="0.0pt" padding-top="0.0pt" height="0.0pt" start-indent="3.6pt">

<fo:inline font-size="9.0pt" white-space-collapse="false" height="9.0pt" font-


family="Arial">

<xsl:value-of select=".//ssRouteGroupName" xdofo:field-name="ssRouteGroupName"/>

5 Replace the section with the following 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">

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

<fo:inline font-size="9.0pt" white-space-collapse="false" height="9.0pt" font-


family="Arial">

<xsl:value-of select=".//ssFirstNamex" xdofo:field-name="ssFirstNamex"/>

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 72 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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


Use the following procedure to implement this fix.

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


Use the following procedure to implement this fix.

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 field’s pickmap, change 'PickList Field' from 'Name' to 'Value'.

Instructions for FR 12-1RAJ7W8


Use the following procedure to implement this fix.

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

726 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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


Use the following procedure to implement this fix.

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:

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 72 7


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

❏ 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: ?

❏ Enable Export: ?

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

9 On the bottom form applet, set the following values:

❏ Profile Attribute: StoredCatalogId

❏ Set Operator: Set

728 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

❏ 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 on page 728.

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:

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 72 9


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

❏ 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
the following values:

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


Use the following procedure to implement this fix.

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:

730 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 73 1


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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


Use the following procedure to implement this fix:

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


Use the following procedure to implement this fix:

1 Within Siebel Tools, query for the Assignment Group-IO integration object.

2 Drill down to Integration Object User Property.

732 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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


Use the following procedure to implement this fix:

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


Use the following procedure to implement this fix:

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


Use the following procedure to implement this fix.

1 Import the EMR_UI.zip file located in the siebsrvr\bin directory.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 73 3


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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:

■ Siebel Administrator

■ Call Center Administrator

■ eMail Response Agent

■ eMail Response Manager

■ Call Center Manager

■ Test Siebel Administrator

Instructions for FR 12-1TSQ0BX


Use the following procedure to implement this fix:

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


Use the following procedure to implement this fix:

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


Use the following procedure to implement this fix:

1 Within Siebel Tools, check out the following projects:

❏ BC [LS Pharma Response]

❏ Link [LS Pharma Campaign Offer/LS Pharma Response]

734 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

❏ 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


Use the following procedure to implement this fix.

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.

Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O 73 5


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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

736 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ Resolved Change
Requests

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 higher limits 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


Use the following procedure to implement this fix:

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


Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. P ■ 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://
www.oracle.com/technology/documentation/siebel.html.

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.

738 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. O

Vous aimerez peut-être aussi