7 0 4 Release Notes RevK

SIEBEL® eBUSINESS APPLICATIONS
RELEASE NOTES
SIEBEL eBUSINESS APPLICATIONS

VERSION 7.0.4+, REV. K
10PA1-RN10-070X0
AUGUST 2003
Siebel Systems, Inc., 2207 Bridgepointe Parkway, San Mateo, CA 94404
Copyright © 2002 Siebel Systems, Inc.
All rights reserved.
Printed in the United States of America.
No part of this publication may be stored in a retrieval system, transmitted, or reproduced in any way, including but not
limited to photocopy, photographic, magnetic, or other record, without the prior agreement and written permission of Siebel
Systems, Inc.
The full text search capabilities of Siebel eBusiness Applications include technology used under license from Fulcrum
Technologies, Inc. and are the copyright of Fulcrum Technologies, Inc. and/or its licensors.
Siebel, the Siebel logo, ActiveBriefing, TrickleSync, TSQ, Universal Agent, and other Siebel product names referenced
herein are trademarks of Siebel Systems, Inc., and may be registered in certain jurisdictions.
Other product names, designations, logos, and symbols may be trademarks or registered trademarks of their respective
owners.
U.S. GOVERNMENT RESTRICTED RIGHTS. Programs, Ancillary Programs and Documentation, delivered subject to the
Department of Defense Federal Acquisition Regulation Supplement, are “commercial computer software” as set forth in
DFARS 227.7202, Commercial Computer Software and Commercial Computer Software Documentation, and as such, any
use, duplication and disclosure of the Programs, Ancillary Programs and Documentation shall be subject to the restrictions
contained in the applicable Siebel license agreement. All other use, duplication and disclosure of the Programs, Ancillary
Programs and Documentation by the U.S. Government shall be subject to the applicable Siebel license agreement and the
restrictions contained in subsection (c) of FAR 52.227-19, Commercial Computer Software - Restricted Rights (June 1987),
or FAR 52.227-14, Rights in Data—General, including Alternative III (June 1987), as applicable. Contractor/licensor is
Siebel Systems, Inc., 2207 Bridgepointe Parkway, San Mateo, CA 94404.
Proprietary Information
Siebel Systems, Inc. considers information included in this documentation
and in Siebel eBusiness Applications Online Help to be Confidential
Information. Your access to and use of this Confidential Information are
subject to the terms and conditions of: (1) the applicable Siebel Systems
software license agreement, which has been executed and with which you
agree to comply; and (2) the proprietary and restricted rights notices
included in this documentation.
Contents
Chapter 1. Introduction
About This Document ................................................................................................................ 1-1
Guidance for Siebel CRM........................................................................................................... 1-2
Guidance for the MidMarket Edition......................................................................................... 1-3
Release Package Contents........................................................................................................ 1-5

Siebel eBusiness Applications ............................................................................................... 1-5
Documentation ....................................................................................................................... 1-6
Chapter 2. Sample Database and Responsibilities

Base Application Sample Database ......................................................................................... 2-1
To Connect to the Base Application Sample Database as a Default Demo User ................. 2-4
To Connect to the Base Application Sample Database as a Non-Standard Demo User ...... 2-4
To Connect to the Base Application Sample Database using Other Siebel Applications ..... 2-4
Base Application Predefined Responsibilities ........................................................................ 2-5
Siebel Financial Services Sample Database............................................................................ 2-9

To Connect to the Siebel Financial Services Sample Database ......................................... 2-16
To Connect to the Siebel Financial Services Sample Database using Other Siebel
Applications.......................................................................................................................... 2-16
Siebel Financial Services Predefined Responsibilities ........................................................ 2-17
Siebel Industry Solutions Sample Database ......................................................................... 2-19
Siebel Industry Solutions Predefined Responsibilities........................................................ 2-25
Siebel CRM Sample Database ................................................................................................. 2-30

To Connect to the Siebel eBusiness Applications, Siebel CRM Sample Database ............ 2-32
To Connect to the Siebel Sample Database using Other Siebel CRM Applications ........... 2-32
Siebel CRM Predefined Responsibilities ............................................................................... 2-33
Siebel Financial Services CRM Sample Database ................................................................ 2-35

To Connect to the Siebel Financial Services CRM Sample Database ................................ 2-36
To Connect to the Siebel Sample Database Using Other Siebel Financial Services CRM
Applications.......................................................................................................................... 2-37
Version 7.0.4+, Rev. K Release Notes iii

Contents
Siebel Financial Services CRM Predefined Responsibilities............................................... 2-38
Siebel MidMarket Edition Sample Database .......................................................................... 2-39

To Connect to the Siebel eBusiness Applications, MidMarket Edition Sample Database .. 2-41
To Connect to the Siebel Sample Database using Other Siebel MidMarket Edition
Applications.......................................................................................................................... 2-41
Siebel MidMarket Edition Predefined Responsibilities ........................................................ 2-42
Siebel Financial Services, MidMarket Edition Sample Database ........................................ 2-44

To Connect to the Siebel Financial Services, MidMarket Edition Sample Database .......... 2-49
To Connect to the Siebel Sample Database Using Other Siebel Financial Services,
MidMarket Edition Applications............................................................................................ 2-49
Siebel Financial Services, MidMarket Edition Predefined Responsibilities....................... 2-50
Chapter 3. Product and Platform Availability Updates

Product and Feature Availability .............................................................................................. 3-1
Chapter 4. Base Application Known Anomalies

General Options.......................................................................................................................... 4-1
Siebel Analytics ........................................................................................................................ 4-39

Marketing Analytics .............................................................................................................. 4-40
Siebel Analytic Applications ................................................................................................. 4-41
Siebel Analytic Charting for Windows NT/2000 Environments........................................... 4-44
Siebel Answers .................................................................................................................... 4-45
Siebel Data Warehouse ....................................................................................................... 4-45
Service Analytics.................................................................................................................. 4-56
Siebel Marketing Analytics................................................................................................... 4-56
Siebel Sales Analytics.......................................................................................................... 4-58
Siebel Anywhere....................................................................................................................... 4-60
Siebel Call Center ..................................................................................................................... 4-60
Siebel Campaigns..................................................................................................................... 4-64
Siebel Connector ...................................................................................................................... 4-66
Siebel Connector for Oracle Applications ............................................................................. 4-66
Siebel Connector for PeopleSoft ............................................................................................ 4-67
Siebel Connector for SAP/R3 .................................................................................................. 4-67
Siebel CTI .................................................................................................................................. 4-69
Siebel CTI Connect................................................................................................................... 4-70
Version 7.0.4+, Rev. K Release Notes iv

Contents
Siebel Data Quality Matching .................................................................................................. 4-71
Siebel Distance Learning......................................................................................................... 4-71
Siebel Dun & Bradstreet Integration Solution ....................................................................... 4-72
Siebel Employee Relationship Management ......................................................................... 4-74
Siebel Enterprise Selling Process .......................................................................................... 4-76
Siebel FirstLogic Connector.................................................................................................... 4-76
Siebel Forecasting.................................................................................................................... 4-76
Siebel Incentive Compensation .............................................................................................. 4-82
Siebel Marketing ....................................................................................................................... 4-83

Segments ............................................................................................................................. 4-85
Siebel Marketing Base / Campaigns.................................................................................... 4-87
Siebel Marketing Manager ................................................................................................... 4-89
Siebel Marketing Server....................................................................................................... 4-90
Siebel Professional Services Automation ............................................................................. 4-91
Siebel Proposals & Presentations .......................................................................................... 4-93
Siebel Quotes............................................................................................................................ 4-95
Siebel Remote ........................................................................................................................... 4-99
Siebel Reports Server and Siebel eReports Server ............................................................ 4-102
Siebel Sales Base Application .............................................................................................. 4-106
Siebel Service Base Application ........................................................................................... 4-110

Logistics Manager .............................................................................................................. 4-112
Siebel Scheduling .............................................................................................................. 4-113
Siebel SmartScript.................................................................................................................. 4-114
Siebel Sync.............................................................................................................................. 4-114
Siebel Time and Expense Reporting .................................................................................... 4-115
Siebel Tools............................................................................................................................. 4-115
Siebel Universal Queuing ...................................................................................................... 4-117
Siebel Wireless ....................................................................................................................... 4-119
Siebel Wireless Messaging.................................................................................................... 4-122
Siebel eAdvisor....................................................................................................................... 4-123
Siebel eAuction....................................................................................................................... 4-128
Siebel eBriefings .................................................................................................................... 4-129
Version 7.0.4+, Rev. K Release Notes v

Contents
Siebel Partner Relationship Mgmt (eChannel Partner Manager)....................................... 4-131
Siebel Partner Relationship Mgmt (eChannel Partner Portal) ........................................... 4-137

Siebel eChannel Partner Commerce ................................................................................. 4-141
Siebel eCollaboration............................................................................................................. 4-144
Siebel eConfigurator .............................................................................................................. 4-147
Siebel eContent Services....................................................................................................... 4-152
Siebel eEvents Manager ........................................................................................................ 4-152
Siebel eMail Response........................................................................................................... 4-153
Siebel eOrder .......................................................................................................................... 4-158
Siebel ePricer .......................................................................................................................... 4-159
Siebel eSales........................................................................................................................... 4-168

Siebel eCatalog.................................................................................................................. 4-173
Siebel eService ....................................................................................................................... 4-173
Siebel eTraining and Siebel eTraining Manager.................................................................. 4-176
Globalization ........................................................................................................................... 4-178

Internationalization ............................................................................................................. 4-178
Localization ........................................................................................................................ 4-179
Multilingual Deployment Support ....................................................................................... 4-185
Chapter 5. Siebel Financial Services Known Anomalies

Siebel eFinance .......................................................................................................................... 5-1
Siebel Call Reports ................................................................................................................ 5-1
Siebel Financial Accounts...................................................................................................... 5-2
Siebel Institutional Sales and Research ................................................................................ 5-3
Siebel Needs Analysis and Applications................................................................................ 5-4
Siebel Securities .................................................................................................................... 5-5
Siebel Teller ........................................................................................................................... 5-5
Siebel Employee Relationship Management ........................................................................... 5-7
Siebel ERM Options............................................................................................................... 5-7
General Product Options ........................................................................................................... 5-8
Siebel Anywhere .................................................................................................................. 5-14
Siebel Reports Server .......................................................................................................... 5-14
Siebel Sync .......................................................................................................................... 5-15
Siebel Financial Services Wireless Applications .................................................................. 5-15
Version 7.0.4+, Rev. K Release Notes vi

Contents
Siebel Wireless for eFinance ............................................................................................... 5-16

Siebel Wireless Banking and Brokerage ............................................................................. 5-16
Siebel eInsurance ..................................................................................................................... 5-17
Siebel Personal Lines Claims .............................................................................................. 5-17
Siebel eHealthcare.................................................................................................................... 5-17
Configuration for the All Members view on DB2 UDB for zSeries Platform......................... 5-17
Siebel Answers .................................................................................................................... 5-18
Siebel Analytic Charting for Windows NT/2000 Environments............................................ 5-19
Siebel eCustomer ..................................................................................................................... 5-19
Siebel eBanking ................................................................................................................... 5-19
Siebel eBrokerage................................................................................................................ 5-20
Siebel Interactive Selling Suite Related Options ................................................................. 5-20
Marketing Related Options .................................................................................................. 5-20
Web Service Related Options.............................................................................................. 5-22
Siebel eService .................................................................................................................... 5-23
Siebel Connectors .................................................................................................................... 5-24
Siebel Connector for SAP/R3 .............................................................................................. 5-24
Upgrade ..................................................................................................................................... 5-24
Globalization ............................................................................................................................. 5-24

Internationalization ............................................................................................................... 5-24
Localization .......................................................................................................................... 5-25
Chapter 6. Siebel eAutomotive Known Anomalies

General Options.......................................................................................................................... 6-1
Siebel Analytics .......................................................................................................................... 6-2

Data Warehouse .................................................................................................................... 6-2
Siebel Analytic Charting for Windows NT/2000 Environments............................................. 6-3
Siebel Partner Analytics......................................................................................................... 6-3
Siebel Sales Analytics............................................................................................................ 6-4
Siebel Call Center ....................................................................................................................... 6-4
Siebel eChannel.......................................................................................................................... 6-4
Siebel eDealer ............................................................................................................................. 6-4
Siebel eService ........................................................................................................................... 6-5
Version 7.0.4+, Rev. K Release Notes vii

Contents
Chapter 7. Siebel Consumer Sector Known Anomalies

General Options.......................................................................................................................... 7-1
Siebel Account Targeting for Disconnect Users..................................................................... 7-3

Data Warehouse .................................................................................................................... 7-3
Siebel Analytic Charting for Windows NT/2000 Environments.............................................. 7-4
Siebel Answers ...................................................................................................................... 7-4
eConsumer Goods Sales Analytics ....................................................................................... 7-5
Siebel Assortment Planning...................................................................................................... 7-5
Siebel eChannel.......................................................................................................................... 7-5

Siebel eChannel Partner Portal for Apparel & Footwear ....................................................... 7-5
Siebel eChannel Partner Portal for Consumer Goods........................................................... 7-6
Siebel eConsumer Goods Sales Handheld.............................................................................. 7-6
Siebel Sales Handheld for Windows CE................................................................................ 7-6
Siebel eEvents Manager...................................................................................................... 7-13
Siebel Sales Volume Planning ................................................................................................ 7-14
Siebel Trade Promotions ......................................................................................................... 7-14
Globalization ............................................................................................................................. 7-16

Localization .......................................................................................................................... 7-16
Chapter 8. Siebel Communications, Media and Energy Known Anomalies

General Options.......................................................................................................................... 8-1
Siebel Anywhere .................................................................................................................... 8-5
Siebel eAdvisor........................................................................................................................... 8-5

Data Warehouse .................................................................................................................... 8-6
Sales, Service and Marketing Analytics................................................................................. 8-7
Siebel eBusiness Data Warehouse ....................................................................................... 8-8
Siebel eChannel.......................................................................................................................... 8-9
Siebel eChannel Partner Commerce ..................................................................................... 8-9
Siebel ePricer .............................................................................................................................. 8-9
Siebel Complex Order Processing ......................................................................................... 8-10
Version 7.0.4+, Rev. K Release Notes viii

Contents
Siebel ePricer ............................................................................................................................ 8-10
Siebel Handheld and Wireless ................................................................................................ 8-11

Siebel Marketing Manager ................................................................................................... 8-11
Siebel Quotes............................................................................................................................ 8-12
Siebel eSales............................................................................................................................. 8-12
Siebel eService ......................................................................................................................... 8-15
Siebel Work Orders .................................................................................................................. 8-15
Globalization ............................................................................................................................. 8-16

Localization .......................................................................................................................... 8-16
Chapter 9. Siebel eHospitality Known Anomalies

Siebel eEvents Execution .......................................................................................................... 9-1
Chapter 10. Siebel Life Sciences Known Anomalies

General Options........................................................................................................................ 10-1

Data Warehouse .................................................................................................................. 10-3
Siebel Analytic Charting for Windows NT/2000 Environments........................................... 10-4
Siebel eClinical Manager ......................................................................................................... 10-4
Siebel eCommunity .................................................................................................................. 10-4
Siebel eClinical ......................................................................................................................... 10-5

Siebel Trip Reports .............................................................................................................. 10-5
Siebel ePharma and eMedical ................................................................................................. 10-5
Siebel ePharma Analytics........................................................................................................ 10-8

Siebel Rx Sales Analytics .................................................................................................... 10-8
Siebel ePharma Answers..................................................................................................... 10-8
Siebel Pharma ROI Analytics............................................................................................... 10-9
Siebel ePharma Handheld ..................................................................................................... 10-10
Siebel Sales Handheld for Windows CE............................................................................ 10-10
Siebel Signature Capture................................................................................................... 10-17
Samples ................................................................................................................................... 10-18
Version 7.0.4+, Rev. K Release Notes ix

Contents
Globalization ........................................................................................................................... 10-20

Localization ........................................................................................................................ 10-20
Version 7.0.4+, Rev. K Release Notes x

Introduction 1
About This Document
These Release Notes contain the most current information on known product anomalies and workarounds for Version 7.0.4+,
Rev. K of Siebel 7. The information contained in Siebel Release Notes supersedes the contents of all other documentation
accompanying this product. It is important that you thoroughly review the Release Notes prior to the installation and use of
the software to ensure a smooth installation and upgrade process.
For customers installing or upgrading to a Siebel Maintenance Release (MR) version, it is important to read the applicable
Siebel Maintenance Release Guide. For example, to deploy Siebel MR v7.0.5, please carefully review the Siebel
Maintenance Release Guide for v7.0.5 for information and instructions specific to that MR, such as:
• MR Installation Instructions and Supplemental Instructions;
• Usability Enhancements included in the MR;
• Resolved Change Requests and Open Issues.
Consult with your Siebel Technical Account Manager (TAM) and Siebel Technical Support to resolve any questions about
the cumulative effect of MRs in your environment.
Follow this step with a review of this general Release Notes document, applicable to the v7.0.4 and later7.0.x releases. (Note
that separate Release Notes documents exist for v7.0.2 and v7.0.3 releases.) The latest versions of these documents can be
found on Siebel SupportWeb (http://ebusiness.siebel.com/supportweb/). Additional known anomalies related to Global
deployment and Language Extensions of Siebel eBusiness Base and Industry Applications can be found in the Globalization
sections at the end of chapters 4 to 10.
Siebel 7 is comprised of Siebel eBusiness Applications, Siebel eBusiness Industry Solutions and Siebel Financial Services.
Table 1-1 lists the industry product lines for Siebel eBusiness Industry Solutions and Siebel Financial Services.
Table 1-1 Siebel Industry Solutions and Siebel Financial Services Product Lines
Siebel Industry Solutions Siebel Financial Services
Siebel eAutomotive Siebel eFinance
Siebel eCommunications Siebel eHealthcare
Siebel eCommunications for Wireless Siebel eInsurance
Siebel eEnergy
Siebel eMedia
Siebel eOil, Gas & Chemical
Siebel eConsumer Goods
Siebel eApparel & Footwear
Siebel eRetail
Siebel eHospitality
Version 7.0.4+, Rev. K Release Notes 1-1

Introduction
Guidance for Siebel CRM
Siebel eClinical
Siebel eMedical
Siebel ePharma
This document contains the following information:
Release Package Contents (in this Introduction, Chapter 1)
Sample Databases and Responsibilities (Chapter 2)
Product and Platform Availability Updates (Chapter 3)
Known Anomalies (Chapters 4 through 10)
Guidance for Siebel CRM

How to use this Release Notes document for the Siebel CRM product
This Release Notes document supports all Siebel products; however, not all anomalies discussed in this document are
applicable to the Siebel CRM application suite. Siebel CRM customers should only refer to Chapters 4, Base Application
Known Anomalies.
All anomalies documented in Chapter 4 are applicable to Siebel 7 CRM with the following exceptions:
Anomalies under sections listed in Table 1-2 are not applicable
Anomalies annotated with Not applicable to Siebel CRM
Anomalies annotated with Not applicable to Siebel CRM or Base MME
Anomalies annotated with Not applicable to Siebel CRM or Base MME or FINS MME
Table 1-2 Chapter 4 Sections Not Applicable to Siebel CRM
Chapter 4 Section Title
Executive Analytics
Marketing Analytics
Siebel eBusiness Data Warehouse
Siebel Marketing Analytics
Siebel Connector
Siebel Connector for Oracle Applications
Siebel Connector for SAP/R3
Siebel Distance Learning
Siebel Employee Relationship Management
Siebel Enterprise Selling Process

Introduction
Guidance for the MidMarket Edition
Siebel Incentive Compensation
Siebel Proposals & Presentations
Logistics Manager
Siebel Scheduling
Siebel Universal Queuing
Siebel Wireless
Siebel Wireless Messaging
Siebel eAdvisor
Siebel eAuction
Siebel eBriefings
Siebel eCollaboration
Siebel eContent Services
Siebel eEvents Manager
Siebel ePricer
Siebel eTraining/Siebel eTraining Manager
Siebel CRM Documentation
Please note that when documentation titles are referenced, Siebel CRM customers should use the Siebel CRM documentation
found on the Siebel 7 Bookshelf, Siebel CRM CD-ROM and the select Siebel CRM documents shipped in printed form with
the release package.

Siebel eBusiness Applications include Siebel 7 MidMarket Edition, an application suite that has been specifically designed to
meet the needs of small and medium-sized businesses. In addition, Siebel Financial Services includes Siebel Financial
Services 7, MidMarket Edition, an application suite available for small and medium-sized organizations in the financial
services industry.
How to use this Release Notes document for the MidMarket Editions
This Release Notes document supports all Siebel products; however, not all anomalies discussed in this document are
applicable to the MidMarket Edition application suite. MidMarket Edition customers should only refer to Chapters 4, Base
Application Known Anomalies, and Chapter 5, Siebel Financial Services Known Anomalies.
All anomalies documented in Chapter 4 are applicable to Siebel 7, MidMarket Edition and Siebel Financial Services,
MidMarket Edition with the following exceptions:

Introduction
Anomalies annotated with Not applicable to Base MME
Anomalies annotated with Not applicable to FINS CRM or to FINS MME.
Anomalies annotated with Not applicable to Base MME or FINS MME
Table 1-2 Chapter 4 Sections Not Applicable to Base or FINS MidMarket Editions
Siebel Analytics
Executive Analytics
Marketing Analytics
Partner Analytics
Siebel Answers
Service Analytics
Siebel Sales Analytics
Siebel Connector
Siebel Connector for PeopleSoft
Siebel Forecasting
Logistics Manager
Siebel Scheduling
Siebel Wireless
Siebel eAdvisor
Siebel eAuction
Siebel eBriefings

Introduction
Release Package Contents
Siebel ePricer
Siebel eTraining/Siebel eTraining Manager
All anomalies documented in Chapters 5 are applicable to Siebel Financial Services 7, MidMarket Edition except where
noted, as follows:
Anomalies annotated with the note Not applicable to FINS CRM or to FINS MME.
Table 1-3 Chapter 5 Sections not applicable to Financial Services MidMarket Edition

Siebel ERM Options
Siebel Financial Services Wireless Applications
Siebel Wireless for eFinance
Siebel Wireless Banking and Brokerage
Siebel Analytics
Siebel Answers
MidMarket Edition Documentation
Please note that when documentation titles are referenced, MidMarket Edition customers should use the MidMarket Edition
documentation found on the Siebel 7 Bookshelf, MidMarket Edition CD-ROM and the select MidMarket Edition documents
shipped in printed form with the release package.

Your Siebel 7.0.4 package includes Siebel eBusiness Applications CD-ROMs and documentation.
Siebel eBusiness Applications

The following categories of Siebel eBusiness Applications are shipped in your release package:
Siebel eBusiness Applications Web Client Programs.

Introduction
Siebel eBusiness Applications Server Programs. Siebel Systems provides separate server programs
CD-ROMs for different localized releases and for different server operating systems. Depending on
which localized product and server operating systems you have licensed, you may receive multiple
CD-ROMs in this category.
Siebel eBusiness Applications Siebel Tools and Web Client Ancillary Programs. A listing of Ancillary
Programs may be found in Siebel System Requirements and Supported Platforms.
Siebel eBusiness Applications Sample Database.
Siebel eBusiness Applications Server Ancillary Programs. A listing of Ancillary Programs may be
found in Siebel System Requirements and Supported Platforms.
Documentation
Most Siebel 7 product documentation is available on the Siebel 7 Bookshelf CD-ROM that shipped in your release package.
For your convenience, select documents are also shipped in printed form with the Siebel 7 package, including the Siebel Web
Client Administration Guide, Documentation Roadmap, QuickStart Guide, Quick Reference Card, Guide to Siebel Global
Services, and the appropriate Siebel Server Installation and Upgrade Guides for your system.
Siebel SupportWeb contains the latest updates to all product documentation. Siebel Release Notes (this document) and Siebel
System Requirements and Supported Platforms are available only on Siebel SupportWeb. When logging into Siebel
SupportWeb, you will be asked to enter the username and password provided to you by Siebel Support Services
(support@siebel.com).
Per your Software License and Services Agreement (SLSA) with Siebel Systems, Inc., you are permitted to print, at no
additional charge, up to three copies of the documentation that applies to programs you have licensed. Through Siebel Books
Online, you can purchase printed copies of Siebel product documentation and the Siebel Bookshelf CD-ROM. To set up your
account and begin using Siebel Books Online, go to http://ebusiness.siebel.com/booksonline/.

Sample Database and Responsibilities 2
Base Application Sample Database
This Siebel eBusiness Applications release includes a sample database for use in demonstrating or evaluating Siebel
eBusiness Applications and Siebel Tools. The sample database must be accessed with the Siebel Mobile Web Client (as
opposed to installed on a server and accessed using the zero footprint client). Your installation environment must meet
browser and OS requirements as described in Siebel System Requirements and Supported Platforms, available on
SupportWeb. For instructions on installing both the Siebel Mobile Web Client and the sample database, please refer to
Chapter 2 of the Siebel Web Client Administration Guide. To run the sample database, the browser and OS requirements
described in System Requirements and Supported Platforms documents must be met.
The sample database includes a number of demo user accounts (Table 2-1), each with a predefined responsibility that reflects
the demo user’s position within the organization. Based on a demo user’s responsibility, he or she is able to access certain
views within Siebel eBusiness Applications software. The table below lists the demo users (default users, defined as those
who are the users installed with the sample database shortcut icons, are marked with an asterisk).
Table 2-1. Siebel eBusiness Applications Demo Users
Username / Name/Title Application Primary Role

Password Responsibility
TSMYTHE* Terry Smythe Siebel Sales Field Sales Smythe uses Siebel Sales to manage all
Representative personal Sales and Forecast information.
District Manager
MSTERN Madison Stern Siebel Sales Sales Manager Stern uses Siebel Sales to manage all
personal and team Sales and Forecasting
Regional Manager
information.
NSACHS Nancy Sachs Siebel Sales Multi- Sachs uses Siebel Sales to manage personal,
Organizational team, and organizational Sales and
VP Sales, North America
Manager forecasting information. She also performs
analysis on revenue pipelines and forecast.
CANDREWS Catherine Andrews Siebel Sales Compensation Andrews creates compensation plans, tracks
Administrator transactions to be used for calculating
Compensation
compensation and calculates compensation.
Administrator
She also generates reports for executives on
total compensation paid out.
CCHENG* Casey Cheng Siebel Call Center Universal Agent Cheng handles service requests of all types:
emails, inbound calls, and Web
Universal Agent
collaboration session requests. In addition,
he executes outbound call campaigns.

Sample Database and Responsibilities

TARNOLD Ted Arnold Siebel Call Center Telesales Arnold primarily executes inbound and
Representative outbound telemarketing and telesales calls.
Telesales Representative
VTAYLOR Vic Taylor Siebel Call Center Call Center Taylor’s responsibilities for day-to-day
Manager operation of a Call Center make him a
VP Call Center
regular user of Siebel Call Center
Administration functions. He uses the
Siebel Analytics function to evaluate
performance and ROI and to make strategic
decisions based on the analyses.
JRUBIN* Jason Rubin Siebel Employee ERM Manager Rubin is an ERM super-user who has access
Relationship to all features in ERM.
Product Line Manager,
Management
ERM product line
BCOOK Bruno Cook Siebel ERM Content Manager Cook is responsible for posting company
news and events using ERM applications.
Content Manager
JKANE Jessica Kane Siebel ERM Training Manager Kane administers training classes and
schedules.
Training Administrator
MMARKS Melissa Marks Siebel ERM ERM User Marks is a user for the ERM product. She
has access to a subset of views that JRUBIN
Product Manager, ERM
can access.
MMAY* Marion May Siebel Marketing Marketing May uses Siebel Marketing to create and
Manager execute different types of marketing
Marketing Manager
campaigns.
BANDERS Brian Andersen Siebel Marketing Business Analyst Andersen uses Siebel Marketing to analyze
data for marketing campaigns.
Business Analyst
EMENDIS Ed Mendis Siebel eEvents Events Manager Mendis uses Siebel eEvents Management to
Management create and manage events for event-driven
Events Manager
marketing.
LAPPLE Linda Apple Siebel Marketing Marketing Analyst Apple uses Siebel Marketing to analyze
data for marketing campaigns.
Marketing Analyst
MMARINO Mary Marino Siebel eMarketing eMarketing Marino uses Siebel eMarketing to conduct
Manager email and Web campaigns.
eMarketing Manager
PMILLER Pat Miller Siebel Marketing Marketing Miller uses Siebel Marketing to monitor and
Manager analyze marketing campaigns and their
VP, Marketing
effectiveness.


EMODI Emily Modi Siebel Professional Consulting Modi is responsible for managing a
Services Manager consulting practice business, including
Engagement Manager
Automation opportunity management, client
relationships, contracts and agreements, as
well as financial reporting and management.
GABBO Gary Abboline Siebel Professional Consultant Abboline is responsible for managing day-
Services to-day project management, including
Information Technologist
staffing requests.
GCLARK Gary Clark Siebel Professional Consulting Clark is responsible for managing a
Services Manager consulting practice business.
Consultant
MCARLSON Mike Carlson Siebel eService Web Corporate Carlson works at Marriott International, a
User customer of Siebel Systems. He uses the
VP Lodging Services, Siebel eSales
Siebel online self-service products to
Marriott International
Siebel eCustomer answer questions, find solutions to his
problems, and gather information about
Siebel products Marriott has bought or is
considering buying.
JADAMS Jamie Adams Siebel eCustomer Web Corporate Adams uses Siebel eAdvisor to get
User guidance and advice online, Siebel eCatalog
VP Information
to navigate through product offerings,
Technology, Marriott
Siebel eConfigurator and ePricer to
International
configure and price orders, and Siebel
eSales to check out online sales
information.
CSUMMERS Clay Summers Siebel eCustomer eAuction Summers uses Siebel eAuction to bid for a
Registered Bidder consulting project from Marriott
Sales Representative -
International for Siebel implementation.
Kerry Consulting
DCOLLINS* Dana Collins Siebel Service Dispatcher Collins is responsible for addressing
customer issues when personnel must be
Dispatcher
sent on-site.
FROBERTS Fred Roberts Siebel Service Senior Field Roberts is a field service engineer working
Engineer for Siebel Systems Service Team. He is
Field Service Engineer
responsible for carrying out field repairs
and replacing defective parts.
RMARLOW Robin Marlow Siebel eChannel Partner Operations Marlow uses Siebel eChannel Partner Portal
Partner Portal Manager to work with Siebel Systems and to improve
Partner Relationship
the effectiveness of all interactions with her
Manager
customers, whether for marketing, sales or
service purposes.


CMORRIS* Colby Morris Siebel eChannel Channel Morris uses Siebel eChannel Partner
Partner Manager Operations Manager to manage the relationships with
Channel Partner Manager
Manager the reseller partners he is responsible for.
He drives marketing, sales and service
through the partner organization, and
assesses the overall performance of the
partner organization.
CMAX Chris Max Siebel eChannel Channel Marketing Max uses Siebel Partner Manager to
Partner Manager Manager manage relationships with consulting
Channel Marketing
partners.
Manager
CMALDEN Cathy Malden Siebel eChannel Channel Partner Malden (a Sales Manager with IBM) uses
Partner Portal Manager Partner Portal to work with Siebel Systems.
Web Registered User -
IBM Sales Manager
PMOSLEY Phil Mosley Siebel eChannel Channel Partner Mosley uses Partner Portal to work with
Partner Portal Manager Siebel Systems.
Web Registered User -
Deloitte Touche Sales
Manager
To Connect to the Base Application Sample Database as a Default Demo User

To log on as a demo user using the Siebel Mobile Web Client, double-click a shortcut icon in the Siebel Client program
group. Shortcut icons with the word Demo in the title will log you into the sample database as the default demo user for that
application. For example, Casey Cheng is the default demo user for the Siebel Call Center Demo.
To Connect to the Base Application Sample Database as a Non-Standard Demo

User
To connect to the sample database as a demo user other than the default demo user for a given application, double-click an
application shortcut icon without “Demo” in the title. In the login dialog box, enter a username and password from Table 2-1
and select the Sample data source.
To Connect to the Base Application Sample Database using Other Siebel

Applications
When you install the sample database as described in the Siebel Web Client Administration Guide, the installer will create
shortcut icons that connect you to the sample database for the following Siebel applications: Siebel Call Center, Siebel
eChannel Partner Manager, Siebel ERM, Siebel Marketing, Siebel Sales, and Siebel Service. It is possible to access the
sample database using other Siebel applications, too, such as Siebel eService, Siebel eCustomer, and the Siebel eChannel
Partner Portal. To set up shortcut icons to access the sample database using these other Siebel Applications, do the
following:

Base Application Predefined Responsibilities
1. Copy an existing Siebel Web Client shortcut icon (for example, Siebel Sales). Typically, these shortcut icons are located
under a <path>\Start Menu\Programs\ directory on the machine on which you installed the sample database.
2. Paste the copy of the shortcut icon into the same directory and name it after the Siebel application for which you are
developing a new shortcut (for example, Siebel eService).
3. Right-click on the new Siebel eService shortcut and select Properties.
4. In the Target field, enter the appropriate command line text from Table 2-2. Note that you must adjust the text as
necessary to reflect the actual directory path to your Siebel Mobile Web Client executable (siebel.exe) file and the .cfg
file.
5. Click OK.
Table 2-2. Target Fields for Alternate Siebel Applications
Siebel Application Target Field Value
Siebel eBriefings C:\sea704\client\BIN\siebel.exe /c C:\sea703\client\bin\ENU\ebriefings.cfg /d sample /u CCHENG

/p CCHENG
Siebel eCustomer C:\sea704\client\BIN\siebel.exe /c C:\sea703\client\bin\ENU\ecustomer.cfg /d sample /u MCARLSON
/p MCARLSON
Siebel eChannel Partner C:\sea704\client\BIN\siebel.exe /c C:\sea703\client\bin\ENU\scw.cfg /d sample /u RMARLOW
Portal /p RMARLOW
Siebel eEvents C:\sea704\client\BIN\siebel.exe /c C:\sea703\client\bin\ENU\eevents.cfg /d sample /u EMENDIS
Management /p EMENDIS
Siebel eMarketing C:\sea704\client\BIN\siebel.exe /c C:\sea703\client\bin\ENU\emarketing.cfg /d sample /u MMARINO
/p MMARINO
Siebel eSales C:\sea704\client\BIN\siebel.exe /c C:\sea703\client\bin\ENU\esales.cfg /d sample /u JADAMS
/p JADAMS
Siebel eService C:\sea704\client\BIN\siebel.exe /c C:\sea703\client\bin\ENU\eservice.cfg /d sample /u MCARLSON
/p MCARLSON
Siebel eTraining C:\sea704\client\BIN\siebel.exe /c C:\sea703\client\bin\ENU\etraining.cfg /d sample /u JRUBIN
/p JRUBIN
Siebel Field Service C:\sea704\client\BIN\siebel.exe /c C:\sea703\client\bin\ENU\sfs.cfg /d sample /u FROBERTS
/p FROBERTS
Siebel Professional C:\sea704\client\BIN\siebel.exe /c C:\sea703\client\bin\ENU\sfs.cfg /d sample /u EMODI /p EMODI
Services

A responsibility in Siebel applications consists of a collection of views. By defining responsibilities and associating users
with them, you limit user access to views and, therefore, to your Siebel application’s information and functions. For example,
the Siebel Administrator responsibility is composed of all views. A user assigned the Siebel Administrator responsibility will
be able to access all Siebel views and functions.

When defining your organization’s responsibilities, you might prefer to start with the predefined responsibilities (Table 2-3)
included in the Siebel application. Though the original predefined responsibilities cannot be edited, the responsibility records
(which include the associated views) can be copied, and the copied version can be customized by adding or deleting views.
For more information on defining responsibilities, see the Applications Administration Guide.
Table 2-3. Predefined Responsibilities
Responsibility Included Views
Call Center Administrator Communication administration, assignment manager, and scripting views, and views for campaign
authoring.
Call Center Knowledge Views for managing knowledgebase access and categorization.
Manager
Call Center Manager Views for a manager within a contact center.
Call Center Representative –

Views for Siebel Wireless users who provide service.
Wireless
All channel manager views, plus additional views suitable for an executive in the indirect channel
Channel Executive
organization.
Views for a manager responsible for marketing through the indirect channel. Includes pertinent
Channel Marketing Manager
administration views.
Views for a manager responsible for operations through the indirect channel. Includes pertinent
Channel Operations Manager
Views for a manager responsible for one or more partners in the indirect channel and pertinent
Company Events Manager Views from Siebel eEvents Management for managing company events.
Compensation Administrator Administration views for designing and managing compensation plans.
Consultant Views for a service consultant who monitors project assignments and enters time and expenses.
Consulting Manager Views for a business development manager who manages professional services projects.
Content Manager Views for managing company literature, broadcast messages, and catalog administration.
Contract Administrator Basic views for contract administration and management.
Customer Service
Views for an agent within a multi-channel contact center.
Representative
Customer Service
A streamlined set of views for an agent within a multi-channel contact center.
Representative – Simple
Dispatcher A limited set of views related to dispatching and scheduling.
eAuction Auction All lister and bidder views plus views for auction administration, catalog administration, invoicing
Administrator administration, fees administration, and reports views.
Catalog, auction, search and members area (Rate Lister, My Ratings, My Auctions, Auction Alert,
eAuction Registered Bidder
My Orders, Featured Auctions) views.
Catalog, auction, search and lister area (Rate Bidder, Create Auction Wizard, Edit Auctions, Repost
eAuction Registered Lister
Auctions, Edit Bids, My Invoices, Bulk Upload) views.

Portfolio admin, account tracking, competitor tracking, industry tracking, and ePortal (employee
eBriefings Manager
detail, opportunity detail and quotes detail) views.
Portfolio admin, account tracking, competitor tracking, industry tracking, and ePortal (employee
eBriefings User
detail, opportunity detail and quotes detail) views.
eChannel Representative –
Siebel eChannel views for wireless users.
Wireless
Views for creating templates, profiles, catalogs (Banter), and monitoring Communications Server for
eMail Response Administrator
outbound/inbound email issues.
eMail Response Agent My Inbound Items views.
eMail Response Manager Manager’s Inbound Items views.
eMarketing Manager Marketing Base, eMarketing, Marketing Analysis.
Activity, incentive compensation, employees across organization, projects, expense, accounts, and
ERM Manager
competitors views.
Activity, employee, training, projects, expense, accounts, and competitors views. This can be any
ERM User
member of the organization.
eService Representative –
Siebel eService views for wireless users.
Wireless
Events Manager Marketing and eEvents Manager views.
Field Engineer A streamlined set of service views for a mobile service person.
Field Sales Representative Accounts, contacts, opportunities, calendar, forecasting, and encyclopedia views.
Field Service Representative –

Field service views for wireless users.
Wireless
Field Technician Basic field service views for a mobile service person,
Helpdesk Agent Field service assets, defect charts, alert admin, service requests views.
Logistics Manager Majority of Siebel Field Service views including all Inventory and Logistics views.
Marketing Manager Marketing, marketing manager, eMarketing, eEvents Manager, and marketing analytics views.
Multi-Organizational Manager All views that span across many organizations.
All licensed Siebel eChannel Partner Portal views, including administration views that allow a
Partner Operations Manager
delegated administrator to add and modify eChannel users at the partner company.
HTML views to allow a channel partner employee to manage the relationship with the vendor
Partner Relationship Manager
company.
Partner Sales Manager HTML views available to a sales manager at a channel partner company.
Partner Sales Rep HTML views available to a sales representative at a channel partner company.
Partner Sales Representative –

Wireless Access to Siebel Wireless eChannel views.

Partner Service Manager HTML views available to a service manager at a channel partner company.
Partner Service Rep HTML views available to a service representative at a channel partner company.
All Pricer administration views including price lists, pricing books, pricing models, pricing factors,
Pricing Administrator decision flow, and catalog pricer. In addition, the responsibility should have read-only capabilities on
class and attribute views in product administration.
Product Administrator Product administration and eConfigurator administration views.
Product Manager Service and quality views for a manager responsible for product development.
The project mappings, project administration, and other views for a system manager responsible for
Project Administrator
data cleanliness.
Project Subcontractor Time, expenses, and project assignment views for a subcontractor.
Registered Customer - Wireless Access to wireless eService views.
Reports User All Reports Server views.
Resource Manager Views for a resource manager who manages resource searching and assignment
Sales Manager Field sales representative views plus my team’s views.
Sales Representative - Wireless Sales views for wireless users.
Self-registered Partner Agent Views available on the Partner Portal for partner users that register as individuals.
Senior Field Engineer Views used by field engineers such as account address and account activities.
Service Administrator Service, field service, scheduling, and agreements administration views.
Service Manager All Siebel Field Service views including Analysis, Sales and Marketing options.
Siebel Administrator All Siebel views (SADMIN).
TAS All views used to manage a sales opportunity.
Telesales Representative Views for an agent within a sales-based call center.
Telesales Representative –
A streamlined set of views for an agent within a sales-based call center.
Simple
Time & Expense Reporting All time sheet and expense reports views.
All views related to administering training courses and curriculums in the Employee Relationship
Management application.
Sales and service views for a call center agent-blends Telesales Representative and Customer Service
Universal Agent
Agent.
Unregistered Partner Agent Views available on the Partner Portal for users that have not registered for access to the portal.
Warehouse Clerk A limited set of Service views for inventory, logistics, and order processing.
Web Anonymous User Views that are available to any Interactive Selling Suite user not identified through a cookie or login.
Web Corporate User All Web consumer views plus Account level Quote, Order, and Address Book views.

Siebel Financial Services Sample Database
Views for creating and maintaining registered customer users of Interactive Selling Suite
Web Delegated Customer
Applications who are associated with administrator’s company. Does not include any eChannel
Administrator
views.
Web Purchasing Manager All Web corporate user views plus views for the Purchasing Approval process.
All Web Anonymous User views plus login-required views such as account info and checkout
Web Registered User
process views.
Wireless Administrator Access to Wireless Admin and Messaging Views.

The Siebel Financial Services 7 release includes a sample database for use in demonstrating or evaluating Siebel Financial
Services eBusiness Applications and Siebel Tools. The sample database must be accessed with the Siebel Mobile Web
Client. For instructions on installing both the Siebel Mobile Web Client and the sample database, please refer to Chapter 2 of
the Siebel Web Client Administration Guide.
The sample database includes a number of demo user accounts (Table 2-4). Demo users are assigned responsibilities that
reflect their position within the organization. Based on their responsibilities, users can access certain views within Siebel
Financial Services 7 software.
Table 2-4. Siebel Financial Services Applications Demo Users
Username / Name / Title Application Primary Responsibility Role

Password
SMILLER Simon Miller Siebel ERM, Siebel FINS Demo ERM Manager Simon uses Siebel ERM to view and
eTraining, Siebel approve company and departmental
Vice President,
Helpdesk, Siebel news, create, submit and approve
Private Client
Performance quarterly objectives, create new
Services
Management, Siebel training, review and register for
eContent Services, training, review alerts online and
Siebel Customer submit service requests, and lookup
Content customer information.
ESMITH Ellen Smith Siebel ERM, Siebel FINS Demo ERM User Ellen uses Siebel ERM to create and
eTraining, Siebel view company and departmental
Senior Financial
Helpdesk, Siebel news, create and submit quarterly
Advisor
Performance objectives, review and register for
Management, Siebel training, review alerts online and
eContent Services, submit service requests, and lookup
Siebel Customer customer information.
Content
BOTTMAR Bill Ottmar Siebel eInsurance FINS Demo Insurance Bill uses Siebel eInsurance Partner
Partner Manager Channel Manager Manager to manage revenues and
Vice President of
partner relationships for the overall
Sales, Insurance
insurance division of Golden Gate


Password
Financial Services.
VALONTO Victor Alonto Siebel eInsurance FINS Demo Insurance Victor uses Siebel eInsurance
Partner Manager Channel Manager Partner Manager to manage partner
Director of Sales,
relationships for the life and health
Life & Health
division of Golden Gate Financial
Services.
CCONWAY Chris Conway Siebel eInsurance Call FINS Demo Insurance Call Chris manages inbound sales and
Center, Personal Lines Center Agent service calls for many of Golden
Insurance Call
Policies, Personal Lines Gate’s lines of business.
Center Agent
Claims, Individual Life
& Annuities, Group
Health
CALLEN Cindy Allen Siebel Agent Portal FINS Demo Insurance Cindy manages sales and service
Captive Agent activities as an external agent to
Insurance Agent
Golden Gate.
IBROWN Ian Brown Siebel Agent Portal FINS Demo Insurance Ian manages sales and service
Independent L&H Agent activities for commercial lines of
Independent
business as an independent agent.
Insurance Broker
FROBERTS Fred Roberts Siebel eInsurance FINS Demo Insurance Field Fred is responsible for managing
Service, Personal Lines Claims Adjuster and settling personal lines claims.
Field Claims
Policies, Personal Lines
Adjuster
Claims
KMEYERS Ken Meyers Siebel Service, Personal FINS Demo Claims Ken is responsible for managing a
Lines Policies, Personal Manager department of personal lines claims
Client Service
Lines Claims adjusters.
Representative
MMANN Directory of Siebel eInsurance FINS Demo Insurance Michael manages partner
Sales, Property & Partner Manager Channel Manager relationships for the property and
Casualty casualty division of Golden Gate
Financial Services.
SJOHNSON Scott Johnson Siebel eCustomer, Registered Customer Scott is a customer with multiple
Siebel eService personal insurance policies at
Customer
Golden Gate.
MDONAHUE Michael Donahue Siebel eFinance Sales, FINS Demo Manager – Michael uses Siebel eFinance Sales
Siebel Business Investment Banking to manage investment banking client
Senior Managing
Relationship relationships, while adhering to
Director
Management, Siebel Chinese Wall security requirements.
Call Reports, Siebel He also performs analysis on
Institutional Sales and revenue pipelines and forecasting.
Research, Siebel


Password
Remote Client, Siebel

Sync, Siebel Reports
Server, Siebel Wireless
eFinance,
CBAXTER Charlie Baxter Siebel eFinance Sales, FINS Demo Banker – Charlie uses Siebel eFinance Sales
Siebel Commercial Commercial Banking to manage all personal contact,
Relationship
Banking Loan opportunity, loan requests, and
Manager
Approval, Siebel forecast information for commercial
Business Relationship banking.
Management, Siebel
Call Reports, Siebel
Financial Accounts
BKEMPER Bonnie Kemper Siebel eFinance Sales, FINS Demo Manager – Bonnie uses Siebel eFinance Sales
Siebel Commercial Commercial Banking to manage all personal and team
Director,
Banking Loan contact, opportunity, loan request,
Commercial
Approval, Siebel and Forecast information for
Banking
Business Relationship commercial banking.
Management, Siebel
Financial Accounts
IBARNES Ian Barnes Siebel eFinance Sales, FINS Demo Banker – Ian uses Siebel eFinance Sales to
Siebel Business Investment Banking manage all personal deals, forecasts,
Vice President
Relationship client, and event information for
Management, Siebel investment banking, while
Call Reports, Siebel respecting all Chinese Wall security
Institutional Sales and requirements.
Research, Siebel
Remote Client, Siebel
Sync, Siebel Reports
Server, Siebel Wireless
eFinance,
ISTONE Vice President Siebel eFinance Sales, FINS Demo Manager – Irene uses Siebel eFinance Sales to
Equity Sales Siebel Business Institutional Sales manage client relationships, sales,
Relationship and call list information for
Management, Siebel institutional sales.
Institutional Sales and
Research, Siebel
Financial Accounts,
Siebel eEvents
Manager, Siebel Sync,
Siebel Reports Server,
Siebel Wireless
eFinance,


Password
RADAMS Robert Adams Siebel eFinance Sales, FINS Demo Sales Rep – Adams uses Siebel eFinance Sales
Siebel Business Institutional to manage client relationships and to
Research Analyst
Relationship maintain and distribute research.
Management, Siebel
Research, Siebel
eEvents Manager,
Siebel Sync, Siebel
Reports Server, Siebel
Wireless eFinance,
EASPEN Eve Aspen Siebel eFinance Sales, FINS Demo Events Admin – Eve uses Siebel eEvents Manager
Siebel eEvents Manager Institutional Sales for Finance to plan and manage
Events
for Finance institutional marketing events.
Administrator
RBRANDON Richard Brandon Siebel eFinance Sales, FIND Demo Retail Broker Brandon uses Siebel eFinance Sales
Siebel Financial to manage all personal contact,
Retail Broker
Accounts, Siebel events, sales, and forecast
eEvents Manager for information for the retail brokerage
Finance, Siebel Needs division of Golden Gate Financial
Analysis and Services.
Applications, Siebel
eBriefings, Siebel
Research
PABBOTT Paul Abbot Siebel eService Registered Customer Paul is a retail brokerage and private
client services customer who uses
Customer
Siebel eService (eBrokerage) to
request trades, download research,
and track his interests.
FMILLER Fred Miller Siebel eFinance FINS Demo Analyst - Fred uses Siebel eFinance
Marketing, Siebel Marketing Marketing and Siebel Analytics to
Vice President
Marketing Manager, evaluate important business drivers
Marketing
Siebel Marketing and to determine what marketing
Analytics, Siebel Sales campaigns need to be created and
Analytics, Siebel executed. He works with his
Service Analytics marketing manager, Faye Morris to
create, execute, and evaluate
marketing campaigns.


Password
FMORRIS Faye Morris Siebel eFinance FINS Demo Manager - Faye uses Siebel Marketing
Marketing, Siebel Marketing Manager to create, manage, and
Marketing
Marketing Manager, execute a marketing campaign for
Manager
Siebel Marketing Golden Gate. She uses Siebel
Analytics, Siebel Sales Marketing Analytics to evaluate the
Analytics, Siebel success of the campaign based upon
Service Analytics responses and leads generated.
CMICHAEL Christine Siebel eFinance Call FINS Demo Manager – Christine manages an inbound and
Michaels Center, Incentive Contact Center outbound call center.
Compensation,
Manager
Campaigns, Forecasting
CABLE Carol Able Siebel eFinance Call FINS Demo Universal Agent Carol handles inbound consumer
Center, Credit – Contact Center service requests and is responsible
Call Center
Origination, Needs for cross selling and outbound
Agent
Analysis and telesales.
Applications, Financial
Accounts, Business
Relationship
Management
PAGEE Paul Agee Siebel eCustomer, Registered Customer Paul is a customer that has various
Siebel eService for relationships with his financial
Customer
Financial Services, institution, including insurance
Siebel Wireless policies and financial accounts.
Banking and Brokerage, Paul can access his information
Siebel Account using online and wireless banking
Aggregation, Siebel services.
Interactive Selling Suite
PBURNS Penny Burns Siebel eFinance Call FINS Demo Private Banker Penny uses Siebel eFinance to
Center, Account manage all relationship functions
Private Banker /
Aggregation, Business related to private banking and
Wealth Manager
Relationship wealth management across
Management, Call insurance, securities, and banking.
Reports, Financial
Accounts, Institutional
Sales and Research,
Needs Analysis and
Applications,
Securities, Service
Requests, Individual
Health Policies, Group
Policies, Individual Life
and Annuities, Personal


Password
Lines Claims, Personal

Lines Policies, D and B
Integration Solution,
eBriefings, Incentive
Compensation,
Proposals and
Presentations, Siebel
eEvents Manager for
Finance
EQUITY Erika Quity Siebel eFinance Call FINS Demo Credit Center Erika uses Siebel eFinance Call
Center, Credit Agent Center to handle consumer loan
Mortgage
Origination, Business requests such as mortgage, home
Specialist
Relationship equity, and credit card requests in a
Management, Financial call center.
Accounts, eMail
Response, Campaigns
UWINTER Uma Winter Siebel eFinance Sales, FINS Demo Credit Uma uses Siebel eFinance Call
Credit Origination, Originator Center to manage loan underwriting
Underwriter
Financial Accounts, in a loan center.
Business Relationship
Management
SBUTLER Stacey Butler Siebel eFinance Call FINS Demo Call Center Stacey uses Siebel eFinance Call
Center, Financial Agent–Small Business Center in a blended small business
Senior Call
Accounts, Business call center, handling both sales, and
Center Agent
Relationship service.
Management, Needs
Analysis and
Applications, Credit
Origination
RMOSS Robert Moss Siebel eFinance Call FINS Demo Relationship Robert uses Siebel eFinance Call
Center, Business Manager Center to jointly manage
Relationship
Relationship relationships with high net worth
Manager
Management, Call individuals and business owners,
Reports, Financial with the assistance of premier
Accounts, Institutional banking managers.
Sales and Research,
Needs Analysis and
Applications,
Securities, Service
Requests, D and B
Integration, eBriefings,
Proposals and
Presentations
BTELLER William Teller Siebel Teller (both as a FINS Demo Bank Teller Bill uses Siebel Teller’s


Password
Teller module Stand Alone functionality for eFinance. He can

and CRM) support customer maintenance,
inquiries, execute transactions, or
support a full CRM teller role in the
organization at the teller line.
ROD Ross David Siebel Teller Officer FINS Demo Bank Manager Ross uses Siebel Teller Officer to
(Stand Alone) oversee a branch and manage
Branch Manager
administrative responsibilities,
including adding new tellers,
determining their transaction limits,
and opening and closing a branch.
LANDREWS Louise Andrews Siebel eHealthcare FINS Demo Health Call Louise uses Siebel eHealthcare
Service, Siebel Center Agent Service to answer member and
Call Center
Healthcare Provider and provider service questions in her
Agent
Facilities, Siebel duties as a call center agent. Her
eEvents Manager for primary role is working in the
Finance member, service, provider, and
facilities screens.
WWU Wendy Wu Siebel Agent Portal, FINS Demo Health Broker Wendy is an independent broker
Siebel Life and Health who uses Siebel Agent Portal to
Health Insurance
Policies, Siebel Sales review opportunities and manage
Broker
Productivity deals in the sales process.
TWATSON Tom Watson Siebel eHealthcare FINS Demo Health Group Tom is employed by the health plan,
Sales, Siebel Group Sales Rep which uses the opportunity
Group Sales
Policies, Siebel management and plan design
Representative
Individual Health functionality of Siebel eHealthcare
Policies, Siebel eEvents Sales. Tom focuses on the
Manager for Finance opportunity, contacts, companies,
group policies, individual health
policies, and literature screen.
JJUDD Jerry Judd Siebel eService, Siebel Registered Customer Jerry resolves her healthcare
eHealthcare Member questions by contacting a call center
Health Plan
Enrollment Portal agent and uses Siebel eService to get
Member
accurate information at any hour.
Jerry can also enroll in group health
products by using the Siebel
eHealthcare Member Enrollment
Portal.


Password
POLSON Pete Olson Siebel eFinance Sales, FINS Demo Relationship Pete Olson is a relationship manager
Catalog, Products, Manager–Cross Divisional at a retail financial center. He walks
Relationship
Product Administration, customers through eAdvisor
Manager
Quote, Applications, sessions to get product
Individual Health recommendations. Pete then uses
Policies, Life and employee-facing screens to submit
Annuities Participants online applications for products.
To Connect to the Siebel Financial Services Sample Database

To log on as a demo user using the Siebel Mobile Web Client, double-click the appropriate shortcut icon in the Siebel Client
program group. See Table 2-1 for a list of available demo users. Using these icons allows you to select a user profile and
database for many uses, such as training.
Table 2-5. Program Group – Siebel Client 7.0.4
Siebel Financial Services - ENU C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\fins.cfg
Siebel Employee Relationship Management- ENU C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\finserm.cfg
Siebel Marketing - ENU C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\finsmarket.cfg
To Connect to the Siebel Financial Services Sample Database using Other Siebel
Applications
When you install the sample database as described in the Siebel Web Client Administration Guide, the installer sets up an
SQLAnywhere database with sample data.
Note: You may access the sample database using Siebel applications other than those described in Table 2-5 above, such as
Siebel eChannel for Finance, Siebel eCustomer, and Siebel eBanking. To set up shortcut icons to access the demo database
using these other Siebel Applications, do the following:
1. Copy an existing Siebel Web Client shortcut icon (such as Siebel eFinance Sales). For Windows machines, these
shortcut icons are usually located in the Start Menu\Programs\ directory of the machine on which you installed the
sample database.
2. Paste the copy of the shortcut icon into the same directory and change the name to the Siebel application for which
you are creating a new shortcut (for example, Siebel Finance eService).
3. Right-click on the new shortcut (for example, Siebel Finance eService) and select Properties.
4. In the Target field, enter the appropriate command line text from Table 2-5 or 2-6. Note that you must adjust the
command line text as necessary to reflect the actual directory path to your Siebel Mobile Web Client executable
(siebel.exe) file and the configuration (.cfg) file.
5. Click OK.

Siebel Financial Services Predefined Responsibilities
Table 2-6. Target Fields for Siebel Applications (Customer and Partner)
Siebel eChannel Partner C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\pmanager.cfg /d sample /u callen /p callen

Manager
Siebel eChannel for C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\finscw.cfg /d sample /u callen /p callen

Finance
Siebel eHealthcare C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\finseenrollment.cfg /d sample /u jjudd /p jjudd

Member Enrollment
Portal
Siebel Insurance and C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\inseservice.cfg /d sample /u sjohnson /p

Healthcare eService sjohnson
Siebel eBanking C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\finsebanking.cfg /d sample /u pagee /p pagee
Siebel eBrokerage C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\finsebrokerage.cfg /d sample /u pagee /p pagee
Siebel eCustomer C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\finsecustomer.cfg /d sample /u pagee /p pagee
Siebel eSales C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\finsesales.cfg /d sample /u caspen /p caspen
NOTE: The user logins given in the above table are primary or available login to that application. Other appropriate logins
may exist for that application if specified by a demonstration script.
Table 2-7. Target Fields for Siebel Applications (Employee)
Siebel eFinance C:\sea704\client\BIN\siebel.exe /c C:\sea703\client\bin\ENU\fins.cfg /d sample /u cable /p cable
Siebel Employee C:\sea704\client\BIN\siebel.exe /c C:\sea703\client\bin\ENU\finserm.cfg /d sample /u smiller /p smiller

Relationship
Management (ERM)
Siebel Marketing C:\sea704\client\BIN\siebel.exe /c C:\sea703\client\bin\ENU\finsmarket.cfg /d sample /u fmiller /p fmiller

In Siebel applications, a responsibility represents a collection of views. : Defining responsibilities and associating users with
responsibilities limits users access to views, and as a result, limits users access to information and functionality in your Siebel
application. For example, the Siebel Administrator responsibility is composed of all views. A user assigned the Siebel
Administrator responsibility will be able to access all Siebel views and functions.
When defining responsibilities for your organization, you could start by using the predefined seed responsibilities included
with the Siebel application (Table 2-8). Though the predefined responsibilities cannot be edited, the responsibility records
(including the associated views) can be copied and the copied version can then be customized by adding or deleting views.
The sample database contains additional responsibilities to help you define your organization’s responsibilities (Table 2-9).
For more information about defining responsibilities, see Siebel Applications Administration Guide.

Table 2-8. Pre-defined Seed Responsibilities
Responsibility Description
Claims Adjuster FINS Routing-Claims Adjuster
Claims Manager FINS Routing-laims Manager
Credit Originator FINS Routing-Credit Originator
Institutional Finance Analyst FINS Routing-Institutional Finance Analyst
Institutional Finance Sales Manager FINS Routing-Institutional Finance Sales Manager
Insurance Sales Agent FINS Routing-Insurance Sales Agent
Insurance Sales Manager FINS Routing-Insurance Sales Manager
FINS Analytics Administrator Views necessary for administering Siebel Analytics
Registered Customer - Wireless Banking Registered Customer-Wireless Banking
NOTE: Many of the additional Seed responsibilities available are inherited from the Core and Horizontal products. While
some of these responsibilities are administrative and may include views specific to Financial Services, most do not
include these views.
Table 2-9. Predefined Siebel Financial Services Sample Database Responsibilities
FINS Demo Analyst - Marketing FINS Demo Analyst-Marketing (FMILLER)
FINS Demo Bank Teller FINS Demo Bank Teller (BTELLER)
FINS Demo Bank Teller Officer FINS Demo Bank Teller Officer (ROD)
FINS Demo Banker - Commercial Banking FINS Demo Banker-Commercial Banking (CBAXTER)
FINS Demo Banker - Investment Banking FINS Demo Banker-Investment Banking (IBARNES)
FINS Demo Call Center Agent - Small Business FINS Demo Call Center Agent-Small Business (SBUTLER)
FINS Demo Channel Operations Manager FINS Demo Channel Operations Manager (eChannel)
FINS Demo Credit Center Agent FINS Demo Credit Center Agent (EQUITY)
FINS Demo Credit Originator FINS Demo Credit Originator (UWINTER)
FINS Demo ERM Manager FINS Demo ERM Manager (SMILLER)
FINS Demo ERM User FINS Demo ERM User (ESMITH / PCONNER / DLOGAN)
FINS Demo Events Admin - Institutional Sales FINS Demo Events Admin-Institutional Sales (EASPEN)
FINS Demo Health Broker FINS Demo Health Broker (WWU)
FINS Demo Health Call Center Agent FINS Demo Health Call Center Agent (LANDREWS)
FINS Demo Health Call Center Sales Manager FINS Demo Health Call Center Sales Manager (DLEE)

Siebel Industry Solutions Sample Database
FINS Demo Health Group Sales Rep FINS Demo Health Group Sales Rep (TWATSON)
FINS Demo Health Ind Health Telesales Rep FINS Demo Health Ind Health Telesales Rep (JDANIELS)
FINS Demo Health Medical Management FINS Demo Health Medical Management (CWHITE)
FINS Demo Health Underwriter FINS Demo Health Underwriter (SWALTERS)
FINS Demo Insurance Call Center Agent FINS Demo Insurance Call Center Agent (CCONWAY)
FINS Demo Insurance Captive Agent FINS Demo Insurance Captive Agent (CALLEN)
FINS Demo Insurance Captive P and C Life Agent FINS Demo Insurance Captive Pand C Life Agent
FINS Demo Insurance Channel Manager (BOTTMOR / MMANN /

FINS Demo Insurance Channel Manager
VALONTO)
FINS Demo Insurance Claims Manager FINS Demo Insurance Claims Manager (KMEYERS)
FINS Demo Insurance Field Claims Adjuster FINS Demo Insurance Field Claims Adjuster (FROBERTS)
FINS Demo Insurance Independent Land H Agent FINS Demo Insurance Independent Land H Agent (IBROWN)
FINS Demo Insurance P and C Life Agency Manager FINS Demo Insurance P and C Life Agency Manager
FINS Demo Insurance Sales Manager - Commercial FINS Demo Insurance Sales Manager-Commercial (SMANN)
FINS Demo Manager - Commercial Banking FINS Demo Manager-Commercial Banking (BKEMPER)
FINS Demo Manager - Contact Center FINS Demo Manager-Contact Center (CMICHAELS)
FINS Demo Manager - Institutional Sales FINS Demo Manager-Institutional Sales (ISTONE)
FINS Demo Manager - Investment Banking FINS Demo Manager-Investment Banking (MDONAHUE)
FINS Demo Private Banker FINS Demo Private Banker (PBURNS)
FINS Demo Relationship Manager FINS Demo Relationship Manager (RMOSS)
FINS Demo Relationship Manager - Cross Divisional FINS Demo Relationship Manager–Cross Divisional (POLSON)
FINS Demo Retail Broker FINS Demo Retail Broker (RBRANDON)
FINS Demo Universal Agent - Contact Center FINS Demo Universal Agent-Contact Center (CABLE)
FINS Demo Web Anonymous User FINS Demo Web Anonymous User
FINS Demo Web Delegated Customer Administrator FINS Demo Web Delegated Customer Administrator
FINS Demo Web Registered User FINS Demo Web Registered User

This Siebel Industry Solutions release includes a sample database for use in demonstrating or evaluating Siebel Industry
Solutions, industry applications and Siebel Tools. The sample database must be accessed with the Siebel Mobile Web Client.
For instructions on installing both the Siebel Mobile Web Client and the sample database, please refer to Chapter 2 of Siebel
Web Client Administration Guide.

The sample database includes a number of demo user accounts (Table 2-10), each with a predefined responsibility that
reflects the demo user’s position within the organization. Accessibility to certain views within Siebel Industry Solutions
software is based on a demo user’s responsibility.
Table 2-10. Siebel Industry Solutions Demo Users

Siebel eAutomotive
HABEL Henry Abel, Field Sales Siebel Auto Field Abel is an OEM employee who uses
Manager eAutomotive Manager Siebel eAutomotive to manage all
Partner Manager dealer relationships.
AALEXIS Andrea Alexis, Siebel Auto customer Alexis is an OEM employee who uses
Customer Service eAutomotive Call service Siebel eAutomotive to manage all
Representative Center representative customer relationships.
RMORRIS Russell Morris, Dealer Siebel eDealer Auto Dealer Morris uses Siebel eDealer to manage
General Manager General Manager OEM relationships, receive sales and
service leads, and administer users at
the dealership.
JNATHAN Joseph Nathan, Dealer Siebel eDealer Auto Dealer Nathan uses Siebel eDealer to receive
Sales Representative Sales sales leads from the OEM.
Representative
AFORBES Anette Forbes, Dealer Siebel eDealer Auto Dealer Forbes uses Siebel eDealer to receive
Service Representative Service service leads from the OEM.
representative
BATKINS Bill Atkins, Customer Siebel Customer Atkins uses Siebel eCustomer to
eCustomer/Siebel interact with OEM and dealerships.
eService
Siebel Communications, Media and Energy
CCORWIN Chris Corwin, Employee Siebel Sales, Communications Chris is an employee who uses Siebel
User Siebel Service, Customer Communications, Media and Energy to
Siebel Call Center Service Rep manage all customer relationships.
for Siebel
eCommunications
, eMedia or
eEnergy
NCOVERDA Nick Coverdale, Siebel IS Marketing Nick is a marketing manager who uses
LE Marketing User Marketing Executive Siebel SIS marketing to create and
manage all marketing programs and
events.
PCARR Peter Carr, Partner Siebel Partner Peter is a partnership manager who
Manager eCommunications Executive uses Siebel Communications, Media
Partner and Energy Partner Manager to manage
Relationship all partner relationships.
Management


MCAVILL Mike Cavill, Partner Siebel eChannel Partner Mike is a partner user who uses Siebel
User Operations Communications, Medial and Energy
Manager eChannel to interface with the brand
owner for every aspect of the
partnership.
KCARSON Kelly Carson, Customer Siebel eCustomer Web Registered Kelly is a customer who uses Siebel
User and eService Communication, Medial and Energy
User eCustomer to manage all her accounts
online or order new services.
Siebel eHospitality
SROSS Sandy Siebel eHospitality Sandy uses Siebel eHospitality to complete
Event Manager
Ross Sales, Siebel the detailed planning of the event and make
Event Manager eHospitality Call sure that it is executed correctly. She
Center coordinates operations activities with the
operations staff.
PHAYS Patricia Siebel eHospitality Patricia uses Siebel eHospitality to oversee
Event Director
Hays Sales, Siebel all events executed at her property. By
Event Director eHospitality Call supervising the execution of all events on
Center property, Patricia is able to make sure that
all the event managers reporting to her
provide excellent customer service. Patricia
also establishes the product and pricing
offering in addition to the tax and service
charge structure for her property.
MHAWK Mike Siebel eHospitality Operations Mike uses Siebel eHospitality to manage
Hawk Sales, Siebel Manager banquet and event technology operations.
Operations Manager eHospitality Call He works closely with the event managers
Center and becomes more involved after specific
products have been selected for the event.
Mike oversees the execution of the event on
the day it occurs.
EHART Emilia Siebel eHospitality Operations Emilia is a supervisor in the operations
Hart Sales, Siebel Manager groups. She relies on Siebel eHospitality to
Operations Supervisor eHospitality Call generate reports in order to execute specific
Center functions. Emilia also updates invoices after
the function is completed.
HOSADMIN Systems Admin Siebel eHospitality Siebel The Hospitality Administrator sets up the
Sales, Siebel Siebel eHospitality application and
eHospitality Call Administrator maintains product, pricing, property, tax
Center and other related information.
Siebel Life Sciences
CROSEN Chris Rosen, Clinical Siebel eClinical Clinical Director CROSEN uses Siebel eClinical Manager
Director and Clinical Project and Resource
Management to manage and track clinical
trials across all programs within the clinical
organization.
CSANDERS Cathy Sanders, Clinical Siebel eClinical Clinical CSANDERS uses Siebel eClinical Manager
Manager Manager and Clinical Project and Resource
Management module to manage her
assigned clinical trial projects.


CSTONE Cindy Stone, Clinical Siebel eClinical Clinical CSTONE uses Siebel eClinical Manager,
Research Associate Research Protocol Builder and Trip Report modules
Associate to manage her sites and record trip reports.
CWALKER Connie Walker, Clinical Siebel eClinical Clinical CWALKER uses Siebel eClinical Manager,
Research Associate Research Protocol Builder and Trip Report Modules
Associate to manage her sites and recording trip
reports.
CYOUNG Craig Young, Medical Siebel eClinical Delegated CYOUNG uses Siebel eClinical Call Center
Monitor Call Center Customer Admin to follow up on trial related service issues.
Site
ASIMON Anna Simon, Site Siebel eClinical - Delegated ASIMON administers and maintains the site
Administrator Site Portal Customer portal for clinical investigators and site
Administrator coordinators.
Site
JALBRIGHT Jill Albright, Site Siebel eClinical - Registered JALBRIGHT uses the site portal to screen,
Coordinator Site Portal Customer Site re-screen, and enroll subjects for clinical
trials.
LSILVER Leroy Silver, Marketing Siebel Marketing Marketing LSILVER uses Siebel Marketing to plan,
Manager Executive create and execute pharmaceutical Direct-
to-Consumer (DTC) marketing Campaigns.
LSOHN Lewis Sohn, Primary Sales Siebel ePharma LS - Pharma LSOHN uses Siebel ePharma to manage
Representative Sales Base Sales Contacts, Accounts, Activities, MedEd,
Samples, Calendar, Expense Reports, and
Time off Territory.
LSTEIN Lawrence Stein, Physician Siebel Professional Registered LSTEIN uses the Professional Portal to
Portal Customer order samples, research drug information,
Professional register for Med Ed events and view
interactive details.
LSHAY Leslie Shay, Web Siebel Professional Delegated LSHAY administers users directly from the
Administrator Portal Customer Professional Portal.
Administrator
Professional
LSTILLER Lincoln Stiller, Siebel Consumer Delegated LSTILLER administers users directly from
Web Administrator Portal Customer the Consumer Portal application.
Administrator
Consumer
PALLEN Paul Allen, Field Sales Siebel ePharma LS - PALLEN is able to manage his district reps
Manager Sales & Medical opportunities, forecasts, and performance.
Siebel eMedical District
Sales Sales
Manager
PMORALES Pablo Morales, Field Sales Siebel ePharma LS - Medical PMORALES is able to manage all personal
Rep Sales & Siebel Base Sales sales and forecast information using his
eMedical Sales Siebel application.
FROBERTS Fred Roberts, Field Service Siebel ePharma Field Engineer FROBERTS is able to execute and record
Engineer Service & Siebel all field services activities and review
eMedical Service relevant customer information.


PREED Pat Reed, Field Service Siebel ePharma LS - Medical PREED uses Siebel to manage customer
Customer Service Manager Service & Siebel service and field service representatives.
eMedical Service Customer
Service Manager
PCONWAY Peter Conway, Customer Siebel ePharma Call LS - Medical PCONWAY has the ability to manage
Service Representative Center & Siebel incoming service requests to the call center
eMedical Call Customer
and analyze incoming service requests.
Center Service
Representative
LSMITH Lisa Smith, Sales Siebel ePharma LS - Pharma LSMITH uses Siebel ePharma to manage
Representative Sales Contacts, Accounts, Activities, MedEd
Base Sales events, Samples, Calendar, Expense
Reports, and Time off Territory.
LSINCLAIR Larry Sinclair, District Siebel ePharma LS Sales Rep w/ LSINCLAIR uses Siebel ePharma to
Manager Sales manage Sales representatives that are part
Accounts and of his district.
Samples - CE
Siebel Consumer Sector
RMARKS Ross Marks Siebel eConsumer Handheld Handheld Administrator for retail sales
Goods Handheld Administrator users of handheld devices.
Handheld
Administrator
CSHARP Colette Sharp Siebel eConsumer Brand Manager Brand Marketing manager.
Goods Marketing
Brand Manager
CSTAMPS Colby Stamps Siebel eConsumer Customer Finance Manager with financial reps as
Goods Sales Financial Service direct reports.
Customer Financial Manager
Service Manager
CSANTO Cory Santo Siebel eConsumer Customer Rep who addresses customer finance
Goods Sales Financial Service issues, such as funding and deductions.
Customer Financial Rep
Service Rep
CNASO Charlie Naso Siebel eChannel Channel Manage relationships with
Partner Portal for Manager noncompany contacts.
CG Channel Manager CG
CUNGER Corinne Unger Siebel eConsumer Consumer User End customer user who purchases
manufacturer products in retail outlets.
CG Consumer User
CSNOW Connie Snow Siebel eConsumer Customer User Retail customer who purchases
products from manufacturer and uses
CG Customer User manufacturer system.
BPARKER Billy Parker Siebel eConsumer Deductions Responsible for resolving all
Goods Sales Agent deductions.
CG Deductions Agent
DLIVERY Del Livery Siebel eConsumer Deliver Retail sales rep who uses handheld
Goods Sales and Representative - device when in field.
CG Deliver Handheld CE


Representative - CE
FSTRONG Freddie Strong Siebel eConsumer Field Service Resolves maintenance issues at
Goods Service Engineer accounts, such as fixing vending
CG Field Service machines.
Engineer
CTRIPP Courtney Tripp Siebel eConsumer Key Account Develops account plans and promotions
Goods Sales and Manager to drive incremental volume at select
Key Account Manager Handheld accounts.
CSPEIER Christian Speier Siebel eChannel Partner User User with companies affiliated with
Partner Portal for manufacturer.
CG Partner User CG
ASHERRARD Andrew Sherrard Siebel eChannel Partner User Administrator for users with companies
Partner Portal for Admin affiliated with manufacturer.
CG Partner User CG
Admin
PSIMMS Pat Simms Siebel eConsumer Pre-Sales Retail pre-sales rep that uses handheld
Goods Sales and Representative - devices.
CG Pre-Sales Handheld CE
Representative - CE
JSMITH Julie Smith Siebel eConsumer Regional Sales Regional Sales Manager with direct
Goods Sales Manager reports including key account managers
Regional Sales and retail managers.
Manager
MROBINS Max Robins Siebel eConsumer Retail Retail merchandising rep at retail
Goods Sales and Merchandising accounts who uses handheld devices.
CG Retail Handheld Representative -
Merchandising CE
Representative - CE
RMARCKS Ricky Marcks Siebel eConsumer Retail Sales Retail sales manager with retail sales
Goods Sales Manager reps as direct reports.
CG Retail Sales
Manager
KDRESEL Kelly Dresel Siebel eConsumer Retail Sales Retail sales rep responsible for
Goods Sales Representative servicing retail stores.
Retail Sales
Representative
TWYNNE Tracy Wynne Siebel eConsumer Retail Sales Retail sales rep that uses handheld
Goods Sales and Representative - device.
CG Retail Sales Handheld CE
Representative - CE
VPRATT Vick Pratt Siebel eConsumer Sr. Vice Vice President over Sales, Marketing,
Goods Sales President Finance, and Operations.
CG Sr. Vice President
DMANNY Dannie Manny Siebel eChannel Store Buyer Retail store buyer using eChannel.
Partner Portal for (eChannel)
CG Store Buyer CG

Siebel Industry Solutions Predefined Responsibilities

(eChannel)
JROACH Justin Roach Siebel eChannel Store Manager Retail store manager using eChannel.
Partner Portal for (eChannel)
CG Store Manager CG
(eChannel)
CCARNEY Chris Carney Siebel eConsumer Universal Agent Customer service call center agent; also
Goods Call Center handles web inquiries.
Universal Agent
VSANDY Vernon Sandy Siebel eConsumer Van Sales Retail sales rep that delivers products to
Goods Sales and Representative - stores and uses handheld devices.
CG Van Sales Handheld CE
Representative - CE
BWONG Betty Wong Siebel eApparel TAF Buyer Apparel and Footwear Buyer.
and Footwear
TAF Buyer Sales
BYOUNG Brian Young Siebel eChannel TAF Buyer Buyer for Apparel and Footwear
Partner Portal for (eChannel) accounts.
TAF Buyer (eChannel) AF
TARNOLD Ted Arnold Siebel eApparel TAF Key Key Account Manager for Apparel and
and Footwear Account Footwear accounts.
TAF Key Account Sales Manager
Manager
MAUSTIN Mike Austin Siebel eApparel TAF Marketing Marketing Admin for Apparel &
and Footwear Administrator Footwear accounts.
TAF Marketing Sales
Administrator
SMOSS Sandy Moss Siebel eApparel TAF Sales Sales Manager for Apparel and
and Footwear Manager Footwear accounts.
TAF Sales Manager Sales

(which include the associated views) can be copied, and the copied version customized by adding or deleting views. The
predefined responsibilities found in table 2-11 supersede those found in the Table 2-3. For more information on defining
responsibilities, see the Applications Administration Guide.

Table 2-11. Siebel Industry Solutions Predefined Responsibilities
Auto Field Manager Views for an OEM employee who uses Siebel eAutomotive to manage all dealer relationships.
Auto Marketing Manager Views for an OEM Employee who uses Siebel eAutomotive to manage marketing related activities.
Auto Customer Service

Representative Views for an OEM employee who uses Siebel eAutomotive to manage all customer relationships.
Views for a Dealer employee who manages OEM relationships, manage sales and service leads and
Auto Dealer General Manager administers users at the dealership.
Auto Dealer Sales Manager Views for a Dealer employee who manages sales teams at the dealership.
Auto Dealer Sales

Representative Views for a Dealer employee who manages sales leads from OEM.
Auto Dealer Service

Representative Views for a Dealer employee who manages service leads from OEM.
Brand Manager Includes corporate promotions, retail objectives and other views for brand managers in a consumer
goods manufacturer, including analytics.
Call Center Administrator Communication administration, assignment manager, and scripting views and views for campaign
authoring.
Call Center Knowledge Views for managing knowledgebase access and categorization.
Manager
Channel Executive
organization.
Company Events Manager Views from eEvents for managing company events.
Compensation Administrator Administration views for designing and managing compensation plans.
Consumer User All views associated with a consumer user.
Content Manager Views for managing company literature, broadcast messages and catalog administration.
Customer Service
Views for an agent within a multi-channel contact center.
Representative

Customer Service
A streamlined set of views for an agent within a multi-channel contact center.
Representative - Simple
Customer User All views associated with a customer user.
Deductions Agent All views associated with deductions and funds.
All views associated with retail sales rep who finishes pre-sales activities. Views include Inventory,
Delivery Representative
Cycle Counting, Orders, and Invoices.
Dispatcher A limited set of views related to dispatching and scheduling.
eAuction Auction All lister and bidder views plus views for auction administration, catalog administration, invoicing
Administrator administration, fees administration and reports.
Catalog, auction, search and members area (Rate Lister, My Ratings, My Auctions, Auction Alert,
eAuction Registered Bidder
My Orders, Featured Auctions) views.
Catalog, auction, search and lister area (Rate Bidder, Create Auction Wizard, Edit Auctions, repost
eAuction Registered Lister
Auctions, Edit Bids, My Invoices, Bulk Upload) views.
Portfolio administration, account tracking, competitor tracking, industry tracking, and ePortal
eBriefings Manager
(employee detail, opportunity detail and quotes detail) views.
Portfolio administration, account tracking, competitor tracking, industry tracking, and ePortal
eBriefings User
(employee detail, opportunity detail and quotes detail) views.
Views for creating templates, catalogs (Banter), and monitoring communications server for
outbound/inbound email issues.
eMail Response Agent My Inbound Items views.
eMail Response Manager My Team, All inbound item views.
eMarketing Manager Marketing Base, eMarketing, Marketing Analysis.
Activity, incentive compensation, employees across organization, projects, expense, accounts and
ERM Manager
competitors views.
Activity, employee, training, projects, expense, accounts and competitors views. This can be any
ERM User
member of the organization.
Events Manager Marketing and eEvents Manager views.
Field Engineer A streamlined set of service views for a mobile service person.
Field Sales Representative Accounts, contacts, opportunities, calendar, forecasting, and encyclopedia views.
Field Service Representative - Includes access to Service Wireless views for a mobile service person, plus access to the Mobile
Wireless views in the web client.
Field Technician Basic field service views for a mobile service person.
All views associated with Handheld devices and Retail Execution, Inventory, Cycle Counting,
Handheld Administrator
Orders, and Invoices.
Helpdesk Agent Field service assets, defect charts, alert administration, service requests views.

Key Account Manager Includes Trade Promotions Management views for a Consumer Goods key account manager.
Logistics Manager Majority of Siebel Field Service views including all Inventory and Logistics views.
Marketing Manager Marketing, marketing manager, eMarketing, eEvents Manager, and marketing analytics views.
All licensed eChannel HTML views, including administration views that allow a delegated
administrator to add and modify eChannel users at the partner company.
company.
Partner Sales Representative - Includes access to eChannel Wireless views for partners, plus access to and from Mobile views in the
Wireless web client.
Partner User All views available to a sales representative at a channel partner company.
Partner User Administrator All views available to a sales representative administrator at a channel partner company.
All views associated with a retail sales rep that is involved in presales activities and uses a handheld
Pre-Sales Representative
device. Views include Retail Execution and Orders.
All Pricer administration views including price lists, pricing books, pricing models, pricing factors,
Pricing Administrator decision flow and catalog pricer. In addition, the responsibility should have READ-only capabilities
on class and attribute views in product administration.
Product Administrator Product administration and eConfigurator administration views.
Product Manager Service and quality views for a manager responsible for product development.
The project mappings, project administration, and other views for a system manager responsible for
Project Administrator
data cleanliness.
Project Subcontractor Time, expenses and project assignment views for a subcontractor.
Regional Sales Manager Includes views from Sales, Trade Promotions, Sales Volume Planning, and Deductions.
Registered Customer - Wireless Includes access to Self Service Wireless views for customers.
Resource Manager Views for a resource manager who manages resource searching and assignment.
Retail Sales Manager Includes Retail Sales Manager, Retail Objective Management and My Team’s views.
Retail Sales Representative Includes Retail Objective Execution and store visit views for Consumer Goods sales representatives.
Sales Representative - Wireless Includes access to Sales Wireless views for a mobile sales person, plus access to and from Mobile

views in the web client.
Self-registered Partner Agent Views available on the Partner Portal for partner users that register as individuals.
Senior Field Engineer Views used by field engineers such as account address and account activities.
Service Administrator Service, field service, scheduling and Agreements Administration views.
Service Manager All Siebel Field Service views including Analysis, Sales and Marketing options.
Siebel Administrator All Siebel views (SADMIN).
Store Buyer All views associated with a Store Buyer at an external company.
Store Manager All views associated with a Store Manager at an external company.
TAF Buyer Includes all views accessible to an Apparel and Footwear buyer.
TAF Buyer - eChannel Includes HTML views accessible to an Apparel and Footwear buyer at retail channel organization.
TAF Key Account Manager Includes key account manager views tailored for an Apparel and Footwear manufacturer.
TAF Marketing Administrator Includes all Siebel Marketing views specific to an Apparel and Footwear manufacturer.
Includes Field Sales Representative views plus My Team’s views for an Apparel and Footwear
TAF Sales Manager industry employee.
TAS All views used to mange a sales opportunity.
Telesales Representative –
Simple
Time & Expense Reporting All time sheet, expense reports, and communications (requests and packages) views.
All views related to administering training courses and curriculums in the Employee Relationship
Management application.
Sales and service views for a call center agent-blends telesales Representative and Customer Service
Universal Agent
Agent responsibilities.
Unregistered Partner Agent Views available on the Partner Portal for users that have not registered for access to the portal.
All views associated with a user that has both pre-sales and delivery responsibilities. Views include
Van Sales Representative
Retail Execution, Orders, Inventory, Cycle Counting, Orders, and Invoices.
Vice President of Sales Includes views from Sales, Trade Promotions, Sales Volume Planning, and Deductions.
Warehouse Clerk A limited set of Service views for inventory, logistics and order processing.
Views that are available to any ISS user who have not identified themselves through a cookie or
Web Anonymous User
login.
Web Corporate User All Web consumer views plus account level quote, order, and address book views.
Web Delegated Customer Views for creating and maintaining registered users of customer and partner applications who are
Administrator associated with administrator’s company. Does not include any eChannel views.
Web Purchasing Manager All Web corporate user views plus views for the Purchasing Approval process.

Siebel CRM Sample Database
Web Registered User
process views.
Wireless Administrator Includes access to Wireless and Wireless Messaging administrative views.

The Siebel eBusiness Applications, Siebel CRM release includes a sample database for use in demonstrating or evaluating
Siebel eBusiness Applications and Siebel Tools. The sample database must be accessed with the Siebel Mobile Web Client
(as opposed to installed on a server and accessed using the zero footprint client). For instructions on installing the Siebel
Mobile Web Client, please refer to Chapter 2 of the Siebel Web Client Administration Guide, Siebel CRM. To run the sample
database, the browser and OS requirements described in System Requirements and Supported Platforms documents available
on SupportWeb must be met.
The sample environment is not automatically installed with your application. To install and use the sample database, please
follow the instructions below. The license key associated with the sample database will expire approximately six months
after the initial shipment of this software.
NOTE: You must have installed the Siebel eBusiness Applications, Siebel CRM application before using these instructions.
Installing the Siebel CRM Sample Database
1. Insert the Siebel Sample Database for Siebel eBusiness Applications, Siebel CRM CD-ROM into the CD-ROM
drive on the computer where you have already installed the Siebel eBusiness Applications, Siebel CRM client
software. This will be referred to as the drive D:\ for the remainder of these instructions.
2. Copy the D:\SampleDB.zip file to C:\. This will only need to be a temporary location. Once you have
decompressed the file and the appropriate files have been copied into your client directory, you may remove the
SampleDB.zip file from C:\.
3. Double-click C:\SampleDB.zip. The WinZip applications window should appear.
4. Click the Extract icon. The Extract window should appear.

a. For the Extract to location choose your <client root>. <Client root> is often C:\sea704.
b. Under Files select All Files.
c. Uncheck Overwrite existing files
d. Uncheck skip older files.
e. Check Use folder name.
f. Click Extract
5. After the files have been extracted to your client location, you may delete C:\SampleDB.zip.

reflects the demo user’s position within the organization. Based on a demo user’s responsibility, he or she is able to access
certain views within Siebel eBusiness Applications, Siebel CRM software.
Table 2-12. Siebel eBusiness Applications, Siebel CRM Demo Users
Username / Name/Title Siebel CRM Primary Role

Password Application Responsibility
TSMYTHE Terry Smythe Siebel Sales Field Sales Smythe uses Siebel Sales to manage all
Representative personal Sales information.
District Manager
MSTERN Madison Stern Siebel Sales Stern uses Siebel Sales to manage all
personal and team Sales information.
Regional Manager Sales Manager
NSACHS Nancy Sachs Siebel Sales Multi-Organizational Sachs uses Siebel Sales to manage
Manager personal, team, and organizational Sales.
VP Sales, North
America
CCHENG Casey Cheng Siebel Call Universal Agent Cheng handles service requests. In
Center, Siebel addition, he executes outbound call
Universal Agent
eService campaigns.
TARNOLD Ted Arnold Siebel Call Telesales Arnold primarily executes inbound and
Center Representative outbound telemarketing and telesales calls.
Telesales
Representative
VTAYLOR Vic Taylor Siebel Call Call Center Manager Taylor’s responsibilities for day-to-day
Center operation of a Call Center make him a
VP Call Center
Administration functions.
MMAY Marion May Siebel Call Marketing Manager May uses Siebel Call Center (or Siebel
Center, Siebel Sales) with Siebel Campaigns to create
Marketing Manager
Sales, Siebel and execute different types of marketing
Campaigns campaigns.
EMODI Emily Modi Siebel Consulting Manager Modi is responsible for managing a
Consultant, consulting practice business, including
Engagement
Siebel Projects opportunity management and client
Manager
(log into Siebel relationships.
Sales)
GABBO Gary Abboline Siebel Consultant Abboline is responsible for managing day-
Consultant, to-day project management, including
Information
Siebel Projects staffing requests.
Techologist
(log into Siebel
Sales)
GCLARK Gary Clark Professional Consulting Manager Clark is responsible for managing a
Services consulting practice business.


Consultant
MCARLSON Mike Carlson Siebel eService No responsibility Carlson works at Marriott International, a
associated customer of Siebel Systems. He uses the
VP Lodging
Services, Marriott
answer questions, find solutions to his
International
problems and gather information about
Siebel products.
JADAMS Jamie Adams Siebel eSales No responsibility Adams uses Siebel online product catalog
associated to navigate through product offerings, and
VP Information
Siebel eSales to check out online sales
Technology,
information.
Marriott
International
RMARLOW Robin Marlow Siebel eChannel Partner Operations Marlow uses Siebel eChannel Partner
Partner Portal Manager Portal to manage the relationship with
Siebel and to improve the effectiveness of
Manager
all interactions with his customers,
whether for marketing, sales or service
purposes.
CMORRIS Colby Morris Siebel eChannel Channel Operations Morris uses Siebel eChannel Partner
Partner Portal Manager Manager (in conjunction with Sales or Call
Channel Partner
Center) to manage the relationships. He is
Manager
responsible for with the reseller partners.
through the partner organization and
CMAX Chris Max Siebel eChannel Channel Marketing Max uses Siebel eChannel Partner
Channel Marketing
Center)to manage relationships with
Manager
consulting partners.
To Connect to the Siebel eBusiness Applications, Siebel CRM Sample Database

To connect to the sample database as a demo user for a given application, double-click an application shortcut icon. In the
login dialog box, enter a username and password from Table 2-1 and select the Sample data source.
To Connect to the Siebel Sample Database using Other Siebel CRM Applications
When you install the sample database as described in the Siebel Web Client Administration Guide, Siebel CRM, the installer
will create shortcut icons that connect you to the sample database for the following Siebel applications: Siebel Call Center,
Siebel Sales, and Siebel Service (The application icons that appear for Marketing, ERM, and Partner Manager are not

Siebel CRM Predefined Responsibilities
applicable to Siebel CRM.) It is possible to access the sample database using other Siebel CRM Applications, such as Siebel
eService, Siebel eCustomer, and the Siebel eChannel Partner Portal. To set up shortcut icons to access the sample database
using these other Siebel CRM Applications, do the following:
1. Copy an existing Siebel Web Client shortcut icon (such as Siebel Sales). For Windows machines, these shortcut
icons are usually located in the Start Menu\Programs\ directory of the machine on which you installed the sample
database.
you are creating a new shortcut (for example, Siebel eService).
3. Right-click on the new shortcut (for example, Siebel eService) and select Properties.
4. In the Target field, enter the appropriate command line text from Table 2-13. Adjust the command line text as
necessary to reflect the actual directory path to your Siebel Mobile Web Client executable (siebel.exe) file and the
configuration (.cfg) file.
5. Click OK.
Table 2-13. Target Fields for Alternate Siebel CRM Applications
Siebel CRM Target Field Value

Application

/p MCARLSON
Portal /p RMARLOW
/p JADAMS
/p MCARLSON

(which include the associated views) can be copied, and the copied version customized by adding or deleting views. For more
information on defining responsibilities, see the Siebel Applications Administration Guide, Siebel CRM.
NOTE: Not all views found in the predefined responsibilities are available for use in your deployment. Views available to
end-users are restricted to the views available in the products you have licensed as part of the Siebel CRM product
line.

Call Center Administrator Communication administration, territory assignment manager, scripting views, and views for
campaign authoring.
Channel Executive
organization.
Content Manager Views for managing company literature and catalog administration.
Customer Service
Views for an agent within a multichannel contact center.
Representative
Customer Service
A streamlined set of views for an agent within a multichannel contact center.
Views for creating templates and monitoring communications server for outbound/inbound email
issues.
eMail Response Agent My Inbound Items views
email Response Manager My Team, All inbound item views
Field Sales Representative Accounts, contacts, opportunities, calendar, and encyclopedia views.
Helpdesk Agent Assets, defect charts, service requests views.
company.

Siebel Financial Services CRM Sample Database
Service Administrator Service and Agreements Administration views.
Siebel Administrator All available Siebel views (SADMIN).
TAS All views used to manage a sales opportunity using the Target Account Selling (TAS) methodology.
Telesales Representative -
Simple
Sales and service views for a call center agent -blends telesales Representative and Customer Service
Universal Agent
Agent
Views that are available to any eSales user that has not identified themselves through a cookie or
Web Anonymous User
login.
Web Delegated Customer Views for creating and maintaining registered customer users of .COM Applications who are
Web Purchasing Manager All Web corporate user views plus views for the purchasing approval process.
Web Registered User
process views.

The Siebel Financial Services CRM release includes a sample database for use in demonstrating or evaluating Siebel
Financial Services CRM and Siebel Tools. The sample database must be accessed with the Siebel Mobile Web Client (as
opposed to installed on a server and accessed using the zero footprint client). For instructions on installing the Siebel Mobile
Web Client, please refer to Chapter 2 of the Siebel Web Client Administration Guid. To run the sample database, the
browser and OS requirements described in System Requirements and Supported Platforms documents available on
SupportWeb must be met.
after the initial shipment of Siebel Financial Services CRM.
NOTE: You must have installed the Siebel Financial Services application before using these instructions.

Installing the Financial Services CRM Sample Database
1. Insert the Siebel Sample Database for Siebel Financial Services CRM CD-ROM into the CD-ROM drive on the
computer where you have already installed the Siebel Financial Services CRM client software. This will be referred
to as the drive D:\ for the remainder of these instructions.

c. Uncheck Overwrite existing files.
f. Click Extract
Financial Services CRM software.
Table 2-15. Siebel Financial Services CRM Applications Demo Users

Take from pdf Terry Smythe Siebel Sales Field Sales Smythe uses Siebel Sales to manage all
District Manager
To Connect to the Siebel Financial Services CRM Sample Database

To log on as a demo user using the Siebel Mobile Web Client, double-click the Siebel Financial Services-ENU shortcut icon
in the Siebel Client program group. See Table 2-15 for a list of available demo users. Using this icon allows you to select a
user profile and database for many uses, such as training.
Table 2-16. Program Group -- Siebel Client 7.0.4


To Connect to the Siebel Sample Database Using Other Siebel Financial Services
CRM Applications
When you install the sample database as described in the Siebel Web Client Administration Guide the installer sets up a SQL
Anywhere database with sample data.
NOTE: You may access the sample database using Siebel CRM Applications other than those described in Table 2-16
above, such as Siebel eCustomer, and Siebel eBanking.
To set up shortcut icons to access the demo database using these other Siebel CRM Applications, do the following:
sample database.
4. In the Target field, enter the appropriate command line text from Table 2-16 or 2-17. Adjust the command line text
as necessary to reflect the actual directory path to your Siebel Mobile Web Client executable (siebel.exe) file and the
5. Click OK.
Table 2-16. Target Fields for Siebel CRM Applications (Customer / Partner)
Siebel CRM Target Field Value

Application
Get from pdf C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\ecustomer.cfg /d sample /u MCARLSON

/p MCARLSON
NOTE: The user logins given in the above table are primary or available login to that application. Other appropriate logins
may exist for that application if specified by a demonstration script.
Table 2-17. Target Fields for Siebel CRM Applications (Employee)


Siebel Financial Services CRM Predefined Responsibilities
Siebel Financial Services CRM Predefined Responsibilities

In Siebel applications, a responsibility represents a collection of views. If you define responsibilities and associate users with
them, this limits user access to views and, as a result, to information and functionality in your Siebel application. For
example, the Siebel Administrator responsibility is composed of all views. A user who is assigned the Siebel Administrator
responsibility will be able to access all Siebel views and functions.
(including the associated views) can be copied, and the copied version can be customized by adding or deleting views. The
sample database contains additional responsibilities to help you define your organization.s responsibilities (Table 2-19). For
more information about defining responsibilities, see Siebel Applications Administration Guide.
NOTE: Not all views found in the predefined responsibilities are available for use in your deployment. Views available to
end-users are restricted to the views available in the products you have licensed as part of the Siebel CRM product
line.
Get from pdf Communication administration, territory assignment manager, scripting views, and
views for campaign authoring.
NOTE: Many of the additional Seed responsibilities available are inherited from the Core and Horizontal product. While
some of these responsibilities are administrative and may include views specific to Financial Services, most do not
include these views.
Table 2-19. Predefined Siebel Financial Services CRM Sample Database Responsibilities
Get from pdf Communication administration, territory assignment manager, scripting views, and
views for campaign authoring.

Siebel MidMarket Edition Sample Database

The Siebel eBusiness Applications, MidMarket Edition release includes a sample database for use in demonstrating or
evaluating Siebel eBusiness Applications and Siebel Tools. The sample database must be accessed with the Siebel Mobile
Web Client (as opposed to installed on a server and accessed using the zero footprint client). For instructions on installing
the Siebel Mobile Web Client, please refer to Chapter 2 of the Siebel Web Client Administration Guide, MidMarket Edition.
To run the sample database, the browser and OS requirements described in System Requirements and Supported Platforms
documents available on SupportWeb must be met.
after the initial shipment of this software.
NOTE: You must have installed the Siebel eBusiness Applications, MidMarket Edition application before
using these instructions.
Installing the MidMarket Edition Sample Database
1. Insert the Siebel Sample Database for Siebel eBusiness Applications, MidMarket Edition CD-ROM into the CD-
ROM drive on the computer where you have already installed the Siebel eBusiness Applications, MidMarket
Edition client software. This will be referred to as the drive D:\ for the remainder of these instructions.

c. Uncheck Overwrite existing files
f. Click Extract
reflects the demo user’s position within the organization. Based on a demo user’s responsibility, he or she is able to access
certain views within Siebel eBusiness Applications, MidMarket Edition software.
Table 2-20. Siebel eBusiness Applications, MidMarket Edition Demo Users
Username / Name/Title MidMarket Primary Role

Password Edition Responsibility
Application


Application
TSMYTHE Terry Smythe Siebel Sales Field Sales Smythe uses Siebel Sales to manage all
District Manager
MSTERN Madison Stern Siebel Sales Stern uses Siebel Sales to manage all
personal and team Sales information.
Regional Manager Sales Manager
NSACHS Nancy Sachs Siebel Sales Multi-Organizational Sachs uses Siebel Sales to manage
Manager personal, team, and organizational Sales.
VP Sales, North
America
CCHENG Casey Cheng Siebel Call Universal Agent Cheng handles service requests. In
Center, Siebel addition, he executes outbound call
Universal Agent
eService campaigns.
TARNOLD Ted Arnold Siebel Call Telesales Arnold primarily executes inbound and
Center Representative outbound telemarketing and telesales calls.
Telesales
Representative
VTAYLOR Vic Taylor Siebel Call Call Center Manager Taylor’s responsibilities for day-to-day
Center operation of a Call Center make him a
VP Call Center
Administration functions.
MMAY Marion May Siebel Call Marketing Manager May uses Siebel Call Center (or Siebel
Center, Siebel Sales) with Siebel Campaigns to create
Marketing Manager
Sales, Siebel and execute different types of marketing
Campaigns campaigns.
EMODI Emily Modi Siebel Consulting Manager Modi is responsible for managing a
Consultant, consulting practice business, including
Engagement
Siebel Projects opportunity management and client
Manager
(log into Siebel relationships.
Sales)
GABBO Gary Abboline Siebel Consultant Abboline is responsible for managing day-
Consultant, to-day project management, including
Information
Siebel Projects staffing requests.
Techologist
(log into Siebel
Sales)
GCLARK Gary Clark Professional Consulting Manager Clark is responsible for managing a
Services consulting practice business.
Consultant
MCARLSON Mike Carlson Siebel eService No responsibility Carlson works at Marriott International, a
associated customer of Siebel Systems. He uses the
VP Lodging


Application
Services, Marriott answer questions, find solutions to his

International problems and gather information about
Siebel products.
JADAMS Jamie Adams Siebel eSales No responsibility Adams uses Siebel online product catalog
associated to navigate through product offerings, and
VP Information
Siebel eSales to check out online sales
Technology,
information.
Marriott
International
RMARLOW Robin Marlow Siebel eChannel Partner Operations Marlow uses Siebel eChannel Partner
Partner Portal Manager Portal to manage the relationship with
Siebel and to improve the effectiveness of
Manager
all interactions with his customers,
whether for marketing, sales or service
purposes.
CMORRIS Colby Morris Siebel eChannel Channel Operations Morris uses Siebel eChannel Partner
Channel Partner
Center) to manage the relationships. He is
Manager
responsible for with the reseller partners.
through the partner organization and
CMAX Chris Max Siebel eChannel Channel Marketing Max uses Siebel eChannel Partner
Channel Marketing
Center)to manage relationships with
Manager
consulting partners.
To Connect to the Siebel eBusiness Applications, MidMarket Edition Sample

Database
To connect to the sample database as a demo user for a given application, double-click an application shortcut icon. In the
login dialog box, enter a username and password from Table 2-1 and select the Sample data source.
To Connect to the Siebel Sample Database using Other Siebel MidMarket Edition
Applications
When you install the sample database as described in the Siebel Web Client Administration Guide, MidMarket Edition, the
installer will create shortcut icons that connect you to the sample database for the following Siebel applications: Siebel Call
Center, Siebel Sales, and Siebel Service (The application icons that appear for Marketing, ERM, and Partner Manager are not
applicable to MidMarket Edition.) It is possible to access the sample database using other Siebel MidMarket Edition

Siebel MidMarket Edition Predefined Responsibilities
Applications, such as Siebel eService, Siebel eCustomer, and the Siebel eChannel Partner Portal. To set up shortcut icons to
access the sample database using these other Siebel MidMarket Edition Applications, do the following:
1. Copy an existing Siebel Web Client shortcut icon (such as Siebel Sales). For Windows machines, these shortcut
icons are usually located in the Start Menu\Programs\ directory of the machine on which you installed the sample
database.
you are creating a new shortcut (for example, Siebel eService).
3. Right-click on the new shortcut (for example, Siebel eService) and select Properties.
4. In the Target field, enter the appropriate command line text from Table 2-21. Adjust the command line text as
necessary to reflect the actual directory path to your Siebel Mobile Web Client executable (siebel.exe) file and the
5. Click OK.
Table 2-21. Target Fields for Alternate Siebel MidMarket Edition Applications
Siebel MidMarket Target Field Value

Edition Application

/p MCARLSON
Portal /p RMARLOW
/p JADAMS
/p MCARLSON

(which include the associated views) can be copied, and the copied version customized by adding or deleting views. For more
information on defining responsibilities, see the Siebel Applications Administration Guide, MidMarket Edition.
NOTE: Not all views found in the predefined responsibilities are available for use in your deployment.
Views available to end-users are restricted to the views available in the products you have licensed as part
of the MidMarket Edition product line.

Call Center Administrator Communication administration, territory assignment manager, scripting views, and views for
campaign authoring.
Channel Executive
organization.
Content Manager Views for managing company literature and catalog administration.
Customer Service
Views for an agent within a multichannel contact center.
Representative
Customer Service
A streamlined set of views for an agent within a multichannel contact center.
Views for creating templates and monitoring communications server for outbound/inbound email
issues.
eMail Response Agent My Inbound Items views
email Response Manager My Team, All inbound item views
Field Sales Representative Accounts, contacts, opportunities, calendar, and encyclopedia views.
Helpdesk Agent Assets, defect charts, service requests views.
company.

Siebel Financial Services, MidMarket Edition Sample Database
Service Administrator Service and Agreements Administration views.
Siebel Administrator All available Siebel views (SADMIN).
TAS All views used to manage a sales opportunity using the Target Account Selling (TAS) methodology.
Telesales Representative -
Simple
Sales and service views for a call center agent -blends telesales Representative and Customer Service
Universal Agent
Agent
Views that are available to any eSales user that has not identified themselves through a cookie or
Web Anonymous User
login.
Web Delegated Customer Views for creating and maintaining registered customer users of .COM Applications who are
Web Purchasing Manager All Web corporate user views plus views for the purchasing approval process.
All Web Anonymous User views plus loginrequired views such as account info and checkout process
Web Registered User
views.
Siebel Financial Services, MidMarket Edition Sample

Database
The Siebel Financial Services, MidMarket Edition release includes a sample database for use in demonstrating or evaluating
Siebel Financial Services, MidMarket Edition and Siebel Tools, MidMarket Edition. The sample database must be accessed
with the Siebel Mobile Web Client (as opposed to installed on a server and accessed using the zero footprint client). For
instructions on installing the Siebel Mobile Web Client, please refer to Chapter 2 of the Siebel Web Client Administration
Guide, MidMarket Edition. To run the sample database, the browser and OS requirements described in System Requirements
and Supported Platforms documents available on SupportWeb must be met.
after the initial shipment of Siebel Financial Services, MidMarket Edition.

NOTE: You must have installed the Siebel Financial Services, MidMarket Edition application before
using these instructions.
Installing the MidMarket Edition Sample Database
1. Insert the Siebel Sample Database for Siebel Financial Services, MidMarket Edition CD-ROM into the CD-ROM
drive on the computer where you have already installed the Siebel Financial Services, MidMarket Edition client
software. This will be referred to as the drive D:\ for the remainder of these instructions.

c. Uncheck Overwrite existing files.
f. Click Extract
Financial Services, MidMarket Edition software.
Table 2-23. Siebel Financial Services, MidMarket Edition Applications Demo Users
Username / Name / Title MidMarket Edition Primary Responsibility Role

Password Application
BOTTMAR Bill Ottmar Siebel eInsurance FINS Demo Insurance Bill uses Siebel eInsurance Partner
Partner Manager, (log Channel Manager Manager (in conjunction with
Vice President of
in through eInsurance eInsurance Sales or Call Center) to
Sales, Insurance
Sales or Call Center) manage revenues and partner
relationships for the overall
insurance division.
VALONTO Victor Alonto Siebel eInsurance FINS Demo Insurance Victor uses Siebel eInsurance
Partner Manager (log in Channel Manager Partner Manager (in conjunction
Director of Sales,
through eInsurance eInsurance with Sales or Call
Life & Health
Sales or Call Center) Center) to manage partner
relationships for the life & health
division.
CCONWAY Chris Conway Siebel eInsurance Call FINS Demo Insurance Call Chris manages inbound sales and


Insurance Call Center, Siebel Personal Center Agent service calls.

Center Agent Lines Policies, Siebel
Personal Lines Claims,
Siebel Individual Life
and Annuities, Siebel
Group Health
CALLEN Cindy Allen Siebel Agent Portal FINS Demo Insurance Cindy manages sales and service
Captive Agent activities as an external agent.
Insurance Agent
IBROWN Ian Brown Siebel Agent Portal FINS Demo Insurance Ian manages sales and service
Independent L and H Agent activities for commercial lines of
Independent
business as an independent agent.
Insurance Broker
KMEYERS Ken Meyers Siebel Service, Siebel FINS Demo Claims Ken is responsible for managing a
Personal Lines Policies, Manager department of personal lines claims
Client Service
Siebel Personal Lines adjusters.
Representative
Claims
MMANN Directory of Siebel eInsurance FINS Demo Insurance Michael manages partner
Sales, Property & Partner Manager (log in Channel Manager relationships for the property &
Casualty through eInsurance casualty division.
Sales or Call Center)
SJOHNSON Scott Johnson Siebel eCustomer, Registered Customer Scott is a customer with multiple
Siebel eService for personal insurance policies.
Customer
Financial Services
MDONAHUE Michael Donahue Siebel eFinance Sales, FINS Demo Manager– Michael uses Siebel eFinance Sales
Siebel Business Investment Banking to manage investment banking client
Senior Managing
Relationship relationships, while adhering to
Director
Management, Siebel Chinese Wall security requirements.
Call Reports, Siebel He also performs sophisticated
Institutional Sales and analysis on revenue pipelines and
Research, Siebel forecasting.
Reports Server
CBAXTER Charlie Baxter Siebel eFinance Sales, FINS Demo Banker– Charlie uses Siebel eFinance Sales
Siebel Commercial Commercial Banking to manage all personal contact,
Relationship
Banking Loan opportunity, loan requests, and
Manager
Approval, Siebel forecast information for commercial
Management, Siebel
Call Reports
BKEMPER Bonnie Kemper Siebel eFinance Sales, FINS Demo Manager – Bonnie uses Siebel eFinance Sales
Siebel Commercial Commercial Banking to manage all personal and team
Director,
Banking Loan contact, opportunity, and loan
Commercial


Banking Approval, Siebel request information for commercial

Management, Siebel
Call Reports
IBARNES Ian Barnes Siebel eFinance Sales, FINS Demo Banker – Ian uses Siebel eFinance Sales to
Siebel Business Investment Banking manage all personal deals, forecasts,
Vice President
Relationship client, and event information for
Management, Siebel investment banking, while
Call Reports, Siebel respecting all Chinese Wall security
Institutional Sales and requirements.
Research, Siebel
Reports Server
ISTONE Vice President Siebel eFinance Sales, FINS Demo Manager – Irene uses Siebel eFinance Sales to
Equity Sales Siebel Business Institutional Sales manage client relationships, sales,
Relationship and call list information for
Management, Siebel institutional sales.
Research, Siebel
Reports Server
RADAMS Robert Adams Siebel eFinance Sales, FINS Demo Sales Rep – Adams uses Siebel eFinance Sales
Siebel Business Institutional to manage client relationships and to
Research Analyst
Relationship maintain and distribute research.
Management, Siebel
Research, Siebel
Reports Server
PABBOTT Paul Abbot Siebel eService for Registered Customer Paul is a retail brokerage/private
Financial Services client services customer who uses
Customer
Siebel eService (eBrokerage) to
request trades, download research,
and track his interests.
CABLE Carol Able Siebel eFinance Call FINS Demo Universal Agent Carol handles inbound consumer
Center, Siebel Credit – Contact Center service requests and is responsible
Call Center
Origination, Siebel for crossselling and outbound
Agent
Business Relationship telesales.
Management, Siebel
Advanced Service
PAGEE Paul Agee Siebel eCustomer, Registered Customer Paul is a customer that has various
Siebel eService for relationships with his financial
Customer
Financial Services, institution, including insurance
Siebel Account policies and financial accounts.


Aggregation Paul can access his information by

using online banking services.
EQUITY Erika Quity Siebel eFinance Call FINS Demo Credit Center Erika uses Siebel eFinance Call
Center, Siebel Credit Agent Center to handle consumer loan
Mortgage
Origination, Siebel requests such as mortgage, home
Specialist
Business Relationship equity, and credit card requests in a
Management, Siebel call center.
eMail Response, Siebel
Campaigns
UWINTER Uma Winter Siebel eFinance Sales, FINS Demo Credit Uma uses Siebel eFinance Call
Siebel Credit Originator Center to manage loan underwriting
Underwriter
Origination, Siebel in a loan center.
Business Relationship
Management
SBUTLER Stacey Butler Siebel eFinance Call FINS Demo Call Center Stacey uses Siebel eFinance Call
Center, Siebel Business Agent – Small Business Center in a blended small business
Senior Call
Relationship call center, handling both sales and
Center Agent
Management, Siebel service.
Credit Origination,
Siebel Advanced
Service
RMOSS Robert Moss Siebel eFinance Call FINS Demo Relationship Robert uses Siebel eFinance Call
Center, Siebel Business Manager Center to jointly manage
Relationship
Relationship relationships with high net worth
Manager
Management, Siebel individuals and business owners,
Call Reports, Siebel with the assistance of premier
Institutional Sales and banking managers.
Research, Siebel
Securities, Siebel D&B
Integration, Siebel
Advanced Service
LANDREWS Louise Andrews Siebel eHealthcare FINS Demo Health Call Louise uses Siebel eHealthcare
Service, Siebel Center Agent Service to answer member and
Call Center
Healthcare Provider and provider service questions in her
Agent
Facilities duties as a call center agent. Her
primary role is working in the
member, service, provider, and
facilities screens.
WWU Wendy Wu Siebel Agent Portal, FINS Demo Health Broker Wendy is an independent broker
Siebel Individual Health who uses Siebel Agent Portal to
Health Insurance
Policies, Siebel Group review opportunities and manage
Broker
Policies, Siebel deals in the sales process.
Individual Life &


Annuities, Siebel Sales

Productivity
JJUDD Jerry Judd Siebel eService for Registered Customer Jerry resolves her healthcare
Financial Services, questions by contacting a call center
Health Plan
Siebel eHealthcare agent and uses Siebel eService to get
Member
Member Enrollment accurate information at any hour.
Portal Jerry can also enroll in group health
products via the Siebel eHealthcare
Member Enrollment Portal.
To Connect to the Siebel Financial Services, MidMarket Edition Sample Database

To log on as a demo user using the Siebel Mobile Web Client, double-click the Siebel Financial Services-ENU shortcut icon
in the Siebel Client program group. See Table 2-24 for a list of available demo users. Using this icon allows you to select a
user profile and database for many uses, such as training.
Table 2-24. Program Group – Siebel Client 7.0.4
To Connect to the Siebel Sample Database Using Other Siebel Financial

Services, MidMarket Edition Applications
When you install the sample database as described in the Siebel Web Client Administration Guide, MidMarket Edition the
installer sets up a SQL Anywhere database with sample data.
NOTE: You may access the sample database using Siebel MidMarket Edition Applications other than
those described in Table 2-16 above, such as Siebel eChannel for Finance, Siebel eCustomer, and Siebel
eBanking.
To set up shortcut icons to access the demo database using these other Siebel MidMarket Edition Applications, do the
following:
sample database.

Siebel Financial Services, MidMarket Edition Predefined Responsibilities
4. In the Target field, enter the appropriate command line text from Table 2-25 or 2-26. Adjust the command line text
as necessary to reflect the actual directory path to your Siebel Mobile Web Client executable (siebel.exe) file and the
5. Click OK.
Table 2-25. Target Fields for Siebel MidMarket Edition Applications (Customer / Partner)
Siebel MidMarket Target Field Value

Edition Application
Siebel eChannel Partner C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\pmanager.cfg /d sample /u callen /p callen

Manager for Financial
Services
Siebel eChannel for C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\finscw.cfg /d sample /u callen /p callen

Finance
Siebel eHealthcare C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\finseenrollment.cfg /d sample /u jjudd /p jjudd

Member Enrollment
Portal
Siebel Insurance / C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\inseservice.cfg /d sample /u sjohnson /p

Healthcare eService sjohnson
Siebel eBanking C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\finsebanking.cfg /d sample /u pagee /p pagee
Siebel eBrokerage C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\finsebrokerage.cfg /d sample /u pagee /p pagee
Siebel eCustomer C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\finsecustomer.cfg /d sample /u pagee /p pagee
Siebel eSales for C:\sea704\client\BIN\siebel.exe /c C:\sea704\client\bin\ENU\finsesales.cfg /d sample /u caspen /p caspen

Financial Services
NOTE: The user logins given in the above table are primary or available login to that application. Other
appropriate logins may exist for that application if specified by a demonstration script.
Table 2-26. Target Fields for Siebel MidMarket Edition Applications (Employee)
Siebel Financial Services, MidMarket Edition Predefined

Responsibilities
In Siebel applications, a responsibility represents a collection of views. If you define responsibilities and associate users with
them, this limits user access to views and, as a result, to information and functionality in your Siebel application. For
example, the Siebel Administrator responsibility is composed of all views. A user who is assigned the Siebel Administrator
responsibility will be able to access all Siebel views and functions.

Siebel Financial Services, MidMarket Edition Predefined Responsibilities
(including the associated views) can be copied, and the copied version can be customized by adding or deleting views.
The sample database contains additional responsibilities to help you define your organization’s responsibilities (Table 2-28).
For more information about defining responsibilities, see Siebel Applications Administration Guide, MidMarket Edition.
NOTE: Not all views found in the predefined responsibilities are available for use in your deployment.
Views available to end-users are restricted to the views available in the products you have licensed as part
of the MidMarket Edition product line.
Claims Adjuster FINS Routing-Claims Adjuster
Claims Manager FINS Routing-Claims Manager
Credit Originator FINS Routing-Credit Originator
Institutional Finance Analyst FINS Routing-Institutional Finance Analyst
Institutional Finance Sales Manager FINS Routing-Institutional Finance Sales Manager
Insurance Sales Agent FINS Routing-Insurance Sales Agent
Insurance Sales Manager FINS Routing-Insurance Sales Manager
NOTE: Many of the additional Seed responsibilities available are inherited from the Core and Horizontal
product. While some of these responsibilities are administrative and may include views specific to
Financial Services, most do not include these views.
Table 2-28. Predefined Siebel Financial Services, MidMarket Edition Sample Database Responsibilities
FINS Demo Banker - Commercial Banking FINS Demo Banker-Commercial Banking (CBAXTER)
FINS Demo Banker - Investment Banking FINS Demo Banker-Investment Banking (IBARNES)
FINS Demo Call Center Agent - Small Business FINS Demo Call Center Agent-Small Business (SBUTLER)
FINS Demo Channel Operations Manager FINS Demo Channel Operations Manager (eChannel)
FINS Demo Credit Center Agent FINS Demo Credit Center Agent (EQUITY)
FINS Demo Credit Originator FINS Demo Credit Originator (UWINTER)
FINS Demo Health Broker FINS Demo Health Broker (WWU)
FINS Demo Health Call Center Agent FINS Demo Health Call Center Agent (LANDREWS)
FINS Demo Health Call Center Sales Manager FINS Demo Health Call Center Sales Manager (DLEE)

FINS Demo Health Ind Health Telesales Rep FINS Demo Health Ind Health Telesales Rep (JDANIELS)
FINS Demo Health Medical Management FINS Demo Health Medical Management (CWHITE)
FINS Demo Health Underwriter FINS Demo Health Underwriter (SWALTERS)
FINS Demo Insurance Call Center Agent FINS Demo Insurance Call Center Agent (CCONWAY)
FINS Demo Insurance Captive Agent FINS Demo Insurance Captive Agent (CALLEN)
FINS Demo Insurance Captive P&C Life Agent FINS Demo Insurance Captive P&C Life Agent
FINS Demo Insurance Channel Manager (BOTTMOR / MMANN /

FINS Demo Insurance Channel Manager
VALONTO)
FINS Demo Insurance Claims Manager FINS Demo Insurance Claims Manager (KMEYERS)
FINS Demo Insurance Independent LandH Agent FINS Demo Insurance Independent LandH Agent (IBROWN)
FINS Demo Insurance PandC Life Agency Manager FINS Demo Insurance P and C Life Agency Manager
FINS Demo Insurance Sales Manager - Commercial FINS Demo Insurance Sales Manager-Commercial (SMANN)
FINS Demo Manager - Commercial Banking FINS Demo Manager-Commercial Banking (BKEMPER)
FINS Demo Manager - Institutional Sales FINS Demo Manager-Institutional Sales (ISTONE)
FINS Demo Manager - Investment Banking FINS Demo Manager-Investment Banking (MDONAHUE)
FINS Demo Relationship Manager FINS Demo Relationship Manager (RMOSS)
FINS Demo Retail Broker FINS Demo Retail Broker (RBRANDON)
FINS Demo Universal Agent - Contact Center FINS Demo Universal Agent-Contact Center (CABLE)
FINS Demo Web Anonymous User FINS Demo Web Anonymous User
FINS Demo Web Delegated Customer Administrator FINS Demo Web Delegated Customer Administrator
FINS Demo Web Registered User FINS Demo Web Registered User

Product and Platform Availability Updates 3
Product and Feature Availability
In some cases, Siebel products and features are not available in this release at all or are not available in certain operating
environments, such as databases, Siebel Enterprise Server operating systems, or Siebel international localizations. Many of
these limitations are due to third-party product support limitations. We distinguish between features and products. Products
are separately licensed and purchased entities. Features, on the other hand, are incorporated within products and are not
purchased separately. When a given feature is not available, the overarching product is generally still available.
Though Siebel supports operation of the Siebel environments on Windows platforms with Multilingual User Interface (MUI)
installed, Siebel does not support dynamic switching of input locale and code page during operation of Siebel. Only the
language of the Siebel Client installation is supported for any Siebel Client.
Product availability exceptions are listed in Table 3-1. Unavailable features are listed in Table 3-2.
Table 3-1. Product Availability Exceptions
Siebel Product Limitation Availability Issue Reason

Type
AOL and Netscape browsers Release Hebrew on AOL and Netscape browsers is not supported in Third party software.
this release.
Siebel Account Aggregation Language For Siebel eFinance, supported only on English due to third Third party software.
party software limitation (Yodlee Adapter).
Siebel Analytics Language Siebel Analytics is available on English, French, Spanish, Limited market demand.
German, Brazilian Portuguese, Italian, Swedish and
Japanese (only) for Siebel eBusiness Applications, Siebel
eBusiness Industry Solutions and Siebel Financial Services.
Siebel Barcode Release Not supported in this release. Siebel Barcode is not
supported in Siebel 7 due to
HTML limitations
surrounding web-enabling
the barcode toolbar.
Siebel Analytics Language Siebel Analytics is available on English, French, Spanish, Limited market demand
German, Brazilian Portuguese, Italian, Swedish and
Japanese only for Siebel eBusiness Applications and Siebel
eBusiness Industry Solutions.
Siebel Analytics Language Siebel Analytics does not support Unicode for AS/400. Third party software
Siebel Analytics Language Siebel Analytics Presentation Server does not provide Third party software
support for multiple multi-byte languages on a single
physical server.
Siebel Analytics Browser Siebel Analytics does not support Netscape. Third party software
Siebel Analytics Web Server Siebel Analytics only supports Apache Tomcat 3.3/4.0 Third party software.

Product and Platform Availability Updates

Type
(JDK 1.3.0) for presentation server on AIX. Websphere is

not currently supported but will likely be supported in next
release.
Siebel Analytics Web Server Siebel Analytics supports Apache Tomcat 3.3/4.0 (JDK Third party software
1.3.1) for presentation server on HP-UX.
Siebel Data Warehouse Language EBCDIC code page for Siebel Data Warehouse is not Third party software
supported.
Siebel Data Warehouse Web Server Informatica Mapping Reporter (IMR) only supports the Third party software
following web application servers: Weblogic 5.1 with DB2
UDB database running on Win NT 4.0, W2K, AIX;
Weblogic 5.1 with Oracle database running on Win NT 4.0,
W2K; Weblogic 5.1 with MS SQL Server database running
on Win NT 4.0, W2K; iPlanet 4.1 with Oracle database
running on Solaris
Siebel Connector for SAP R/3 Server OS Not supported with Siebel Server on AIX or Solaris. SAP does not have a thread-
Support available with affected server component running safe shared RFC library for
on Windows. AIX or Solaris (SAP R/3
version 4.6b).
Siebel Connector for Oracle Language Not available in Korean for Siebel eBusiness Applications Limited market demand and
and Siebel Financial Services. problems gaining access to
Oracle ERP environment.
Siebel CTI Connect Server OS The Dialogic CTI middleware components are supported The Dialogic CTI
on Win NT and Win 2000 and Dialogic CTI middleware is middleware components are
not supported with Siebel Server on AIX or Solaris. supported on Win NT and
Support available with affected server component running Win 2000.
on Windows.
Siebel Data Warehouse Database EBCDIC code page for Siebel Data Warehouse is not Third party software.
supported.
Siebel Distance Learning and Language Supported only on English due to third party software Third party software.
related products1 limitation (Pixion).
Siebel Distance Learning and Web Server Not supported on the IBM HTTP Server v2 (IHS) Third party software.
related products1
Siebel Distance Learning and Server OS Not supported with Siebel Server on AIX or Solaris due to Third party software.
related products1 third party software limitation (Pixion).
Siebel Distance Learning and Browser Not supported with AOL browsers due to third party Third party software.
related products1 software limitation (Pixion).
Siebel eAdvisor Standalone Server OS Not supported with Siebel Server on AIX. Limited market demand.
(Transact Server)
1
Includes Siebel eDetails and Siebel eCommunity, products available with the Siebel ePharma, Siebel eClinical, and Siebel
eMedical industry segments.


Type
Siebel eAdvisor Standalone Language Not available in Japanese. Product Defect 12-6W8J3T.
(Transact Server)
Siebel eAdvisor Browser Not supported on IE 6.0 due to third party limitation. Third Party Product defect
12-6Z5C07.
Siebel eBriefings Client OS Not supported on Mac OS 9. Product defect 12-8Y6UOJ.
Siebel eCollaboration Server Siebel eCollaboration is supported on Microsoft IIS Web Third party software.
OS/Web server running on a supported Microsoft Windows platform
Server OS only.
Siebel eCollaboration Language Not supported in Japanese, Korean, simplified Chinese or Third party software.
Brazilian Portuguese.
Siebel eCollaboration Browser Not supported with Netscape 4.7 browser. Not supported Netscape 4.7 not supported
with IE 5.0 browser on Mac OS due to third party software due to Product defect 12-
limitation (Microsoft). XXXXX. Mac IE browser is
not supported due to the lack
of live connect support for
that browser.
Siebel Employee Relationship Client OS Not supported on Mac OS 9. Product defects 12-8Y6UOJ,
Management 12-8Y6UOP.
Siebel Connector for Firstlogic Language Supported for U.S. addresses only. Not supported in Third party software.
Libraries localized versions due to third-party software limitation
(FirstLogic).
Siebel Handheld for Windows- Release Not available with Siebel eBusiness Applications and Sales and Service Handheld
Powered Devices Siebel Financial Services. to be released in 7.5.
Siebel Handheld for Windows- Language For Siebel ePharma and Siebel eConsumer Goods, Limited market demand.
Powered Devices available on English, French, Spanish, and Brazilian
Portuguese only.
Siebel Handheld for Windows- Server OS Not supported with Siebel Server on AIX or Solaris. Limited market demand.
Powered Devices Support available with affected server component running
on Windows.
Siebel ePharma Handheld for Database Not supported with iSeries. Product Defects 12-AX55EK
Windows Powered Devices and and 12-ASS55F.
Siebel eConsumer Goods Sales
Handheld for Windows Powered
Devices
Siebel Marketing Release Siebel Marketing server is not supported on iSeries for Product Defects 12-
Siebel eBusiness Applications, Siebel Industry Solutions AYRJPS, 12-AV6D7P,
and Siebel Financial Services. 12-AV6D8E.
Siebel Proposals and Server OS Not supported with Siebel Server on AIX or Solaris due to Third party software.
Presentations third party software limitation (Microsoft). Support
available with affected server component running on


Type
Windows.
Siebel Reports Server Web Server If running Siebel Reports Server using IBM HTTP Server, Third party software.
you will need to deploy Actuate ReportCast on a separate
machine with IBM HTTP Server v.1.3 and not Limited
Release v.2.0.
Siebel Reports Server Platform Due to third party software limitation (Actuate), not Third party software.
supported with Microsoft Internet Explorer version 6x
browser.
Siebel SmartAnswer Language Supported only on English, French, German, and Spanish Third party software.
due to third party software limitation (Banter).
Siebel Search and Siebel Language Due to third party software limitation (Fulcrum), Siebel Third party software.
Advanced Search Search does not support the following languages: Chinese,
Russian, Hebrew and Thai. Siebel Advanced Search does
not support the following languages: Chinese, Russian,
Hebrew, Thai, Czech, Greek , Japanese, Korean , and
Polish. There is partial Advanced Search support (synonym
only and no word stemming) for the following languages:
Finnish , Norwegian, Brazilian Portuguese, and Turkish.
Siebel Sync Language Supported only on English, German, French, Spanish, Third party software.
Italian, Dutch, Danish, Swedish, Brazilian Portuguese,
Chinese-Simplified, Korean and Japanese for Outlook and
Lotus Notes due to third party software limitation (Puma).
Siebel Universal Queuing Language Installer not available in Hebrew or Korean. Third party software.
Siebel Wireless Language Not supported on AIX and Solaris for Japanese, Korean, Product defect 12-B72KIN
and Simplified Chinese
Siebel Wireless Language, For Siebel eBusiness Applications and Siebel Financial Limited market demand.
Release Services, available on English, French, German, Spanish,
Italian, Danish, Dutch, Swedish, Brazilian Portuguese,
Japanese and Korean.
For Siebel Industry Solutions, available on English, French,

German, Spanish, Italian, Swedish, Japanese and Brazilian
Portuguese.
Siebel Wireless Messaging Language For Siebel eBusiness Applications and Siebel Financial Limited market demand
Services, available on English, French, German, Spanish, Third party software.
Italian, Danish, Dutch, Swedish, Brazilian Portuguese, and
Korean.
Note:
- Korean supported only for messaging through the
MobileSys Network.
- Not supported on Japanese due to third party

limitations.

Table 3-2. Feature Availability Exceptions
Feature (Associated Siebel Product) Limitation Availability Issue Reason

Type
ADSI Security Adapter Server OS Not supported with Siebel Server on AIX or Third party software.
Solaris due to third party software limitation Microsoft Active Directory
(Microsoft). doesn’t work on AIX or Solaris
platforms.
Bookmarking of records Release Not supported in this release. This is a core limitation of the
HTML browser infrastructure.
Case insensitive dictionary sort (Siebel Data Database Not supported with Siebel Database Server Informatica mappings not
Warehouse) running MS SQL Server 2000. developed to support case-
insensitive dictionary sort in
SQL Server.
Clustering of IIS4 with SWSE on Windows Server OS & This configuration is not supported due to Third party software.
NT 4.0 using MSCS Clustering third party software limitation (MSCS &
Software IIS4).
CORBA Object Manager for Iona Orbix Server OS Not supported with Siebel Server on Solaris. The reason is due to compiler
incompatibility.
Correspondence Server OS Not supported with Siebel Server on AIX or Third party software.
Solaris due to third party software limitation
(Microsoft). Support available with affected
server component running on Windows.
Drag and drop Release Not supported in this release. Fourth and fifth generation
browsers supply limited drag-
and-drop support. The level of
support offered could not
satisfy the expectations or
demands of our users.
Expense Reports (Sales) Language Regional support outside of the U.S. is not Reports have been localized
available. and require customization to
meet specific locale and legal
requirements per region.
Integration to Taxware for tax calculations Language NonEuropean characters not supported due Third party software.
(Siebel eSales) to third party software limitation (Taxware).
Integration to Taxware for tax calculations Language Siebel supports the Taxware integration for Third party software.
(Siebel eSales) the following languages only: English.
French. German, Spanish, Italian, Danish,
Dutch, Swedish, and Brazilian Portuguese
Marketing Visual Segmentation Server OS Not available on UNIX. Support available Will be supported in a future
with affected server component running on release.
Windows.
Marketing Visual Segmentation Database Not available for customers deploying DB2 Will be supported in a future

Feature (Associated Siebel Product) Limitation Availability Issue Reason

Type
UDB for OS/390 and zSeries. release.
Microsoft Project Integration (Siebel Server OS Not supported with Siebel Server on AIX or Third party software.
Professional Services Automation) Solaris due to third party software limitation
(Microsoft). Support available with affected
server component running on Windows.
MS Crypto Server OS Not supported with Siebel Server on AIX or Third party software. Microsoft
Solaris due to third party software limitation encryption code doesn’t run on
(Microsoft). AIX or Solaris platforms.
Right mouse click Release Not supported in this release. Fourth generation browsers do
not support right-click menus.
Fifth generation browser
support for right-click menus is
incomplete and prone to
producing errors.
Repository Compilation against IBM zSeries Server OS Siebel 7.0.4 does not support the compilation Third party software.
(DB2 / 390) EBCDIC of a Siebel Repository File (.srf) by a Tools
client running directly against an IBM
zSeries (DB2/390) database. Customers who
use a zSeries (DB2/390) database as
development server must import the
repository into an alternative database (e.g.,
SQL Anywhere) that can be used by Siebel
Tools for purposes of generating and
updating the .srf file.
Secure Socket Layer (SSL) Authentication Server Not supported on UNIX platforms. Third party software
between Siebel Enterprise and external LDAP Recommendations: (a) set up connection
server without SSL; or (b) use Windows platform
for Siebel Server.
Sending of non-English language pages Language Not supported in this release. TAP protocol for paging
(Siebel Paging) designed to support English
only.
Spell checking Language Due to third party software limitation Third party software. These are
(WinterTree), can only do spell checking in the only foreign language
the following languages: English, Brazilian dictionary files available for
Portuguese, Danish, Dutch, Finnish, French, licensing from Wintertree.
German, Italian, Norwegian, Polish,
Portuguese, Spanish, and Swedish.
Syndicated Data Loading and Routing (Siebel Server OS, Not supported with Siebel Server on AIX or Limited market demand.
Sales, Siebel Service, Siebel Call Center for Database Solaris. Not supported with Database Server Feature specifically designed
Siebel ePharma, Siebel eClinical, and Siebel running DB2. for Windows and Oracle.
eMedical)

In addition to Table 3-2, Table 3-3 lists additional feature availability exceptions that are applicable to Siebel CRM (also
Siebel Financial Services CRM). Siebel CRM does not support these features. Customers should use Siebel Tools to remove
these features from the views or applets they intend to deploy.
Table 3-3. Feature Availability Exceptions Applicable to Siebel CRM / Financial Services CRM Only
Feature MidMarket Views/Applets Affected

Application
Ask a Question Applet eCustomer, Home Page View (eService)

eService
Auction Applet eCustomer, Product Catalog Category Detail View (eSales)
eSales Product Catalog Category Detail View - Product Basic (eSales)
Branch Locator Applet eCustomer, Contact Us Communication Channel View
eSales,
eService
Broadcast Message Applet Service FS Home Page View
Contact Customer Care Representative eBanking, Contact Us Communication Channel View
Applet eCustomer, FINS eBanking Contact Us Communication Channel View
eSales,
eService FINS FSW Contact Us Communication Channel View
Featured Articles Applet Partner Portal Home Page View (SCW)

Map Search Applet Service FS Home Page View
My Compensation Applet Sales Sales Home Page View
My Sales Analysis Applet Sales Sales Home Page View
My Stocks Call Center, FS Home Page View
Sales, Service Home Page View (WCC)
Sales Home Page View
Need Advice Applet eCustomer, Home Page View (eCustomer)
eSales Home Page View (eSales)
Home Page View (SCW)
Product Catalog Category Detail View (eSales)
Product Catalog Category Detail View - Product Basic (eSales)
Product Catalog View (eSales)
Product Detail - Features View (eSales)
Our Company News Applet Call Center, Anonymous User Home Page View (SCW)
Sales, Service FS Home Page View
Home Page View (WWC)
Home Page View (WService)
Weather Applet Service FS Home Page View
Web Search Applet Service FS Home Page View


Application
Yellow Pages Applet Service FS Home Page View
Attribute Pricing Field Call Center, Price List Item Applet

Sales, Service
Price List Item Applet (Read Only)
Price List Item Form Applet
Auction Privilege Field Call Center, User Admin Detail Applet

Sales, Service
Auto Allocate, Auto Substitute, and Call Center, Product Entry Applet
Allocate Below Safety Fields Sales, Service
Product Form Applet
Allow Third Party Lister Field Call Center, Catalog Admin Detail - Detail Applet
Sales, Service
Branch Locator Hyperlink eService Contact Us Communication Channel Tiny Applet
Book/Cancel Appointment Buttons Call Center, Service Request Activity List Applet
Sales, Service
Compensable Field Call Center, Admin Class Product List Applet

Sales, Service
Product Entry Applet
Product List Applet
Create Auction Button Call Center, Product Form Applet

Sales, Service
Configuration File Field Call Center, Product Entry Applet

Sales, Service
Product Form Applet
Customize Button Call Center, Order Entry- Line Item List Applet
Sales, Service
Product Form Applet (eSales)
Product List Applet - Add to Cart (eSales)
Product XA Attributes Form Applet (eSales)
Quote Item List Applet
Customizable Field/Column Call Center, Price List Item Applet

Sales, Service
Product Form Applet
Product List Applet
DBM Field Call Center, Campaign Detail Applet

Sales, Service
Campaign Detail Applet - Admin


Application
Decision Issues, Auctions, Training, and Call Center, User Catalog Explorer Applet
Events Tree Nodes Partner Portal,
User Catalog Explorer Applet (SCW)
Sales, Service
Get Advice Button Call Center, Quote Form Applet

Sales, Service Quote List Applet
Quote List Applet (SCW)
Interactive Designer Project Field Call Center, Catalog Admin Catalog Detail Applet
Sales, Service
New User Hyperlink Partner Portal Login Applet
Pricing Model Field Call Center, Price List Form Applet

Sales, Service
Price List Form Applet - Child

Smart Answer Import Button, Catalog File Call Center, Catalog Admin Catalog Detail Applet
and Master File Fields Sales, Service
File > Send > Wireless Message Menu Item Call Center, FINS Generic Web Menu
Sales, Service
Generic Web Menu
In addition to Table 3-2, Table 3-4 lists additional feature availability exceptions that are applicable to MidMarket Edition
only. MidMarket Edition does not support these features. Customers should use Siebel Tools, MidMarket Edition to remove
these features from the views or applets they intend to deploy.
Table 3-4. Feature Availability Exceptions Applicable to MidMarket Edition Only

Application
Ask a Question Applet eCustomer, Home Page View (eService)

eService
Auction Applet eCustomer, Product Catalog Category Detail View (eSales)
eSales Product Catalog Category Detail View - Product Basic (eSales)
Branch Locator Applet eCustomer, Contact Us Communication Channel View
eSales,
eService
Broadcast Message Applet Service FS Home Page View
Contact Customer Care Representative eBanking, Contact Us Communication Channel View
Applet eCustomer, FINS eBanking Contact Us Communication Channel View
eSales,
eService FINS FSW Contact Us Communication Channel View


Application
Featured Articles Applet Partner Portal Home Page View (SCW)

Map Search Applet Service FS Home Page View
My Compensation Applet Sales Sales Home Page View
My Sales Analysis Applet Sales Sales Home Page View
My Stocks Call Center, FS Home Page View
Sales, Service Home Page View (WCC)
Need Advice Applet eCustomer, Home Page View (eCustomer)
eSales Home Page View (eSales)
Home Page View (SCW)
Product Catalog Category Detail View (eSales)
Product Catalog Category Detail View - Product Basic (eSales)
Product Catalog View (eSales)
Product Detail - Features View (eSales)
Our Company News Applet Call Center, Anonymous User Home Page View (SCW)
Sales, Service FS Home Page View
Home Page View (WWC)
Home Page View (WService)
Weather Applet Service FS Home Page View
Web Search Applet Service FS Home Page View
Yellow Pages Applet Service FS Home Page View
Attribute Pricing Field Call Center, Price List Item Applet
Sales, Service
Price List Item Applet (Read Only)
Auction Privilege Field Call Center, User Admin Detail Applet

Sales, Service
Auto Allocate, Auto Substitute, and Call Center, Product Entry Applet
Allocate Below Safety Fields Sales, Service
Product Form Applet
Allow Third Party Lister Field Call Center, Catalog Admin Detail - Detail Applet
Sales, Service
Branch Locator Hyperlink eService Contact Us Communication Channel Tiny Applet
Book/Cancel Appointment Buttons Call Center, Service Request Activity List Applet
Sales, Service


Application
Compensable Field Call Center, Admin Class Product List Applet

Sales, Service
Product List Applet
Create Auction Button Call Center, Product Form Applet

Sales, Service
Configuration File Field Call Center, Product Entry Applet
Sales, Service
Product Form Applet
Customize Button Call Center, Order Entry- Line Item List Applet
Sales, Service
Product Form Applet (eSales)
Product List Applet - Add to Cart (eSales)
Product XA Attributes Form Applet (eSales)
Quote Item List Applet
Customizable Field/Column Call Center, Price List Item Applet

Sales, Service
Product Form Applet
Product List Applet
DBM Field Call Center, Campaign Detail Applet

Sales, Service
Campaign Detail Applet - Admin
Decision Issues, Auctions, Training, and Call Center, User Catalog Explorer Applet
Events Tree Nodes Partner Portal,
User Catalog Explorer Applet (SCW)
Sales, Service
Get Advice Button Call Center, Quote Form Applet

Sales, Service Quote List Applet
Interactive Designer Project Field Call Center, Catalog Admin Catalog Detail Applet
Sales, Service
New User Hyperlink Partner Portal Login Applet
Pricing Model Field Call Center, Price List Form Applet

Sales, Service
Price List Form Applet - Child

Smart Answer Import Button, Catalog File Call Center, Catalog Admin Catalog Detail Applet
and Master File Fields Sales, Service


Application
File > Send > Wireless Message Menu Item Call Center, FINS Generic Web Menu
Sales, Service
Generic Web Menu

Base Application Known Anomalies 4
General Options
Access Control
InfoCenter
Navigating through catalog and category hierarchies in Infocenter, drilling down on a given catalog and getting to a category
view, under certain circumstances the Left hand-side navigation bar doesn’t show all the view tabs (Product, Literature,
Solution, Resolution,and so forth.) that contain data items, and therefore users won’t be able to access these data items under
this category for this particular data type (for example Product, Literature). The workaround is to associate another data item
(of the same type) into the category or to delete and reassociate an existing item. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-A6PFME)
Org vs. All Visibility Implementation on Views
Siebel 7 has implemented MultiOrg visibility in many places for business components that are Organizationvisibility enabled,
such as Accounts and Quotes. However, in the following views, All visibility is applied to these Account and Quote applets:
Contacts view (eService, Account applet), Saved Quotes View (eSales, Quote applet), Saved Quotes View – My Company
(eSales, Quote Applet), and Contact Us Addresses View (eService, Account applet). (12-5ERSI5)
Activities
Workaround for Slow All Activities view
Customers using Siebel 7.0.4 on Microsoft SQL Server will experience slow performance on All Activities view. Customer
who do not use HTML email feature can disable the EMAIL BODY field in the All Activity Applet to workaround the
performance problem. To apply the workaround the following steps need to be taken in Siebel Tools and a new srf file
generated:
1. Map Display Email Body Field to EMail Body in Comm Inbound Item Body Applet: HTML TextAreaMsgBody is a
control in Comm Inbound Item Body Applet. The value of the Field property for this control is Display Email
Body. Change this value to Email Body for the workaround
2. Map Display Email Body to Email Body in Comm Inbound Item Form Applet: set the Field value to Email Body
from Display Email Bodyfor control HTML TextAreaMsgBody in the Comm Inbound Item Form Applet.
3. Set Force Active to False for Email Body in Action BC
As a result of this workaround the Message Body in Inbound Item List View and Incoming Message in Communication
Detail-Response View will only display plain text. (12-B91BL3)

Base Application Known Anomalies
Streamline the manual reassignment of Activities
In base Siebel applications, users can reassign activities by navigating to the Calendar or Activity Detail view, opening the
Owned By MVG (labeled Employee in the Activity and Calendar Detail UI) for a given record, adding a new user to this
MVG, and making that user the primary. Customers can streamline this process by exposing the Primary Owned By field in
the Calendar and Activity Detail Views. The Primary Owned by field is a single value Employee Pick Applet that displays
the primary employee as designated in the Owned By MVG. If a new value is entered into the Primary Owned By field, this
value overwrites the old primary that was specified in the Owned By MVG. (12-9TFTXE)
Application Administration
Optional Indexes for increased Performance of the Communications Admin View (Oracle Only)
The following index change will improve performance of the Communications Admin View.
CREATE INDEX S_CM_USR_STATUS_T1 on S_CM_USR_STATUS (BUSY_FLG)
(12-AGDX6N)
Changing the default three-letter language code
The three-letter language code appears by default as ENUin the Industry Administration View in both applets. This is
defined in the Industry Business Component. To change the default language, do the following:
1. Connect with Tools to your development database.
2. In the explorer pane navigate to the Business Component Industry and the field Language Code.
3. Change the Pre Default Value to another language code. This language code must be available in the table
S_LANG. If it is not, you can add it through the Language Administration View in the System Administration
Screen.
4. Recompile the SRF for the Industry project.
5. Copy the new SRF to the server and restart the server.
(12-9NBPK9)
Assignment Manager
NOTE: Neither Base MME nor FINS MME includes Assignment Manager. However, they do offer the
Territory Assignment feature, to which some of the anomalies below apply.
Performance issue with DB2/390
To fix performance problem for many slow employee views and slow employee picklist, a search-spec of ([Last Name] like
“*”) should be added into Employee BusComp. The same search-spec should also be added into Person Admin List Applet to
fix the All Person Administration View, which is the default view of User Admin screen. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-B3IQAN)

Missing new Include All Matching LOV
The new Include All Matching inclusion method that has been introduced in the 7.0.4 release does not have a corresponding
LOV value in the seed data. In order to make this inclusion method visible and to use it, you need to add a new LOV as
follows:
1. Navigate to Site Map > Application Administration > List of Values
2. Add a new record with the following fields:
• Type: ASGN_INCLUSION_CD
• Display Value: Include All Matching
• Language Independent Code: Include All Matching
• Parent LIC: <leave blank>
• Order: 3
• Active: Y
• Translate: Y
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AXV3L1)
Assignment Rule Item List Applet Address Fields
The following issue is applicable for all nonAmerican English locales:
The order of address fields in international releases will appear as City, State, Country, and ZIP Code. The workaround is to
run Tools, navigate to Siebel Objects -> Assignment Criteria, query for "Account City State Country", expand to Assignment
Criteria Attribute, and change the Display Sequence property. Compile changes into the SRF file. (12-9AKB0V)
Bookmarks
Drag and Drop Siebel Bookmarks
The ability to drag a Siebel bookmark from the Siebel application to the desktop or document is not supported. (12-48T5XU)
Calendar
Error when reviewing Employee Availability creating business component 'Employee (MM)' used by business
object 'SI Employee'
This error occurs when the user drills down to the calendar from the homepage and tries to access the Employee Availability.
This can be corrected by adding the Employee(MM) Business Component to the SI Employee Business Object. (12-
H3Q7IR)

Making fields required in the Calendar Detail Form
Currently, type is the only field that is required in the Calendar Detail Form Applet. If customers wish to make other fields
required, they must predefault these fields. This is because, when users create a new record or drill into a record from the
calendar grid, an implicit save of the record is triggered. If certain fields are required but not predefaulted, their value will be
null when the implicit save is triggered. This will generate an error. (12-ABP6QG)
PM Symbol in a Japanese Deployment
The following issue is only applicable for the Japanese locale installed on Solaris. The PM symbol will not appear in the
calendar in a Solaris environment. To change this change the Japanese PM symbol to the English PM symbol in the WIN.INI
file. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9GTUJN)
Enhanced Printing for Calendar
Users of Microsoft Internet Explorer should do the following to enhance the look of calendars that they print: In IE, go to
Tools > Internet Options > Advanced > Print, and check the Print background color and images option. (12-8H0EBV)
Home Page Calendar Resizing
The home page calendar is dynamically sized. As more conflicting appointments are added to the calendar, the Home Page
Calendar will become wider to accommodate these appointments. As the Home Page Calendar becomes wider, any applets
to the left of the calendar become narrower. Depending on the number of conflicting appointments that occur at a given time,
the calendar may expand to such an extent that the applets to the left of the calendar become too narrow to read. To avoid
this, customers may choose to fix the widths of the applets to the left of the Home Page calendar. This can be done by
modifying the home page template in Siebel Tools. (12-8QF3C1)
Siebel Sync 6 Appointments Appear in the Siebel 7 Calendar Based on Sync Time
After upgrading from Siebel 6 to Siebel 7, customers will notice that appointments imported into the Siebel 6 calendar using
Siebel Sync 6 will appear on the Siebel 7 calendar based on the time they were imported into Siebel 6 rather than their true
start time. To rectify this, resync your PIM to Siebel 7 using Siebel Sync 7. After resyncing using Siebel Sync 7, Siebel
Sync 6 records will be displayed on the Siebel 7 calendar in duplicate—one appointment will be displayed based on the
Siebel Sync 6 sync time, and an identical record will be displayed based on the true start time. (12-6P7BA7)
Connection Brokering
ERM and Call Center Configurations for DB2 for iSeries
Due to limitation on the iSeries, the following configurations must be made for ERM and Call Center to prevent the
respective object managers from crashing.
ERM
MaxMTServers = 1 for 100 users
MaxSharedDBConns = 20 for 100 users
MinSharedDBConns = 20 for 100 users
MinTrxDBConns = 20 for 100 users
Call Center

MaxMTServers = 2 for 100 users
MaxSharedDBConns = 20 for 100 users
MinSharedDBConns = 20 for 100 users
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AYR5YV)
Content Center
Publishing changes to the same product in a single session
Dataset caching interferes with publishing changes to the same product (content object) multiple times within a single user
session. In order to prevent this situation the datasource associated with the content staging environment should be
configured without dataset caching. This can be done by setting the DSMaxCachedDatasets parameter to zero (0) for the
appropriate datasource subsystem. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
6QF4LA)
Publishing Categories and Sub-categories
When publishing a catalog category and a catalog subcategory in the same content project, the publish process will fail if the
content item referring to the subcategory is added to the project before the content item referring to the parent category. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-97O6PZ)
Product Content Object and Multiple Organizations
The Product Content Object publishes only the primary organization designation. If you use the multiorganizational feature
of Products, you will want to change the integration object definition as follows: under integration object Admin Product
Definition (Content Management), enable the integration component Internal Product_Organization. Only one field (Name)
under that integration component must be enabled. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-7T2FB7)
HTML Attachments cannot be loaded by URL
On the HTML Attachment View, adding a new HTML attachment by URL is not supported. Use the Browse button to load
the attachment from the local file system. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
5Z1XJF)
Correspondence
First Name, Last Name are in U.S. order
Japanese Last Name, First Name ordering can be set by dragging and dropping columns. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-8MUMRR)
EAI Server Components
Manipulating in memory XML hierarchies
To manipulate in memory XML hierarchies, such as to add new elements, attributes, or envelopes, work with XML
Hierarchy property sets. An XML Hierarchy property set can be converted to and from Integration Object property set using

EAI Integration Object to XML Hierarchy Converter. An XML Hierarchy property set can be converted to and from XML
document using XML Hierarchy Converter. ( 12-BEBNFR)
Using MQ Series Server Transport on AIX
On AIX platforms, MQSeries Server Transport service may fail with an error code 2059 (cannot connect to the queue
manager). This may happen because the MQ Series Queue manage uses shared memory segment 8 by default; although
Siebel does not rely on any specific memory segment, it is highly probable that Siebel server process gets segment number 8
from the operating system first and the MQ Series Queue manager can not get its segment.
To resolve this problem, configure MQ Series Queue manager to use a different shared memory segment
(IPCCBaseAddress). Possible legal values for IPCCBaseAddress are: 4, 5, 8, 9, 10, 11, and 12; 8 has been found to be
problematic. To specify a shared memory segment:
1. Shut down the MQ Series Queue managers which Siebel business service will connect to.
2. Edit the file /var/mqm/mqs.ini. In the QueueManager stanza, for each queue manager of interest, add an additional
line explicitly specifying the shared memory segment to use. For example:
QueueManager:
Name=myQueueManager
Prefix=/var/mqm
Directory=myQueueManager
IPCCBaseAddress=12
This example shows shared memory segment number 12 being used. It is possible to run into the 2059 error even with the
segment no. 12 if the operating system has nondeterministically allocated segment 12 to the Siebel process ahead of the
queue manager. In such an event, a different segment number may need to be specified. Legal values are 4, 5, 8, 9, 10, 11,
and 12.
3. Restart the queue managers.Using MQ Series Server Transport on AIX
NOTE: :This applies only to AIX and not to Solaris. A 2059 error on Solaris may be due to valid reasons
such as wrong queue manager name, queue manager not running, etc. (Not applicable to Siebel CRM or
Base MME) (12-B00PEE)
Using MQ Series Server Transport on AIX
On AIX platforms, MQSeries Server Transport business service may continue to fail to connect to a running queue manager
in spite of resolving the shared memory segment collision problem by configuring IPCCBaseAddress as documented in
release note (12-B00PEE). In such case, error code 2059 from MQSeries will be reported and a new FDC file will be
generated with a Probe Id of XY341019 and a component of RetryConnectToSharedSubpool.
To resolve this issue, configure AIX environment to run Siebel server with a smaller memory model using environment
variable LDR_CNTRL. Then specify a compatible value for IPCCBaseAddress as documented in release note (12-B00PEE).
To configure AIX environment to run Siebel server with a smaller memory model:
1. Shutdown the Siebel server.

2. In the shell which will be used to bring up Siebel server, set the environment variable LDR_CNTRL. Using csh:
setenv LDR_CNTRL MAXDATA=0x30000000
3. Restart the Siebel server with this environment variable.
(Not applicable to Siebel CRM or Base MME) (12-B39Y2R)
Sending xml data through AIC connecter of BizTalk
The following issue is only applicable for the Japanese locale. Set the language parameter to JPN for the connect string for
AIC/ configuration. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9BOAAR)
EAI HTTP Transport does not support import of Japanese UTF-8 XML file in Business Service Simulator
The following issue is only applicable for the Japanese locale. EAI HTTP Transport does not support import of Japanese
UTF-8 XML file in Business Service Simulator. Use workflow process for EAI HTTP transport. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-8UMK0B)
Exporting system fields such as ID
Integration Object fields marked as system" are not exported during a query operation. If it is desired to include such fields in
the exported message, change the Integration Component field type to Data. (12-9SLND0)
EAI HTTP Transport does not support import of Japanese UTF-8 XML file in Business Service Simulator
Please use the workflow process for EAI HTTP transport. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-8UMK0B)
Microsoft Access 2000 and XP do not allow Siebel OLE DB access
Microsoft Access 2000 allows only limited functionality through the Siebel OLE DB Provider. This includes querying
business objects and their directly related business components. Microsoft Access XP no longer allows direct third-party
OLE DB Provider access. The workaround is being investigated for future versions of Siebel OLE DB Provider. (12-
48ICLD)
Enterprise Integration Manager
EIMmerge must be executed in Row by Row on denormalized columns (AS/400 Only) (12-B5ACVA)
Potentially misleading Error Message
When executing an EIM Export process with children tables included in ONLY BASETABLES parameter. An error message
is reported for grandchildren of the base table. The task will continue and complete successfully. (12-AN20DS)
Additional Indexes for EIM Merge on DB2 UDB for zseries Platform
The following index change will improve performance of the EIM Merge for EIM_CONTACT.
CREATE INDEX SIEBEL.EIM_CONTACT_T26
ON SIEBEL.EIM_CONTACT

( IF_ROW_BATCH_NUM ASC ,
T_MERGED_ROW_ID ASC )
USING STOGROUP SIEBSG
PRIQTY 7200
SECQTY 14400
ERASE NO
FREEPAGE 0
PCTFREE 20
GBPCACHE CHANGED
BUFFERPOOL BP2
CLOSE YES
PIECESIZE 2 G
COPY NO
DEFINE YES
(12-B47KC7)
The following index change will improve performance of the EIM Merge for EIM_ACCOUNT:
CREATE INDEX SIEBEL.EIM_ACCOUNT_T19
ON SIEBEL.EIM_ACCOUNT
PRIQTY 720
SECQTY 14400
ERASE NO
FREEPAGE 0
PCTFREE 20
GBPCACHE CHANGED
BUFFERPOOL BP2

CLOSE YES
PIECESIZE 2 G
COPY NO
DEFINE YES
(12-B47KC7)
No index on EIM table for T_MERGED_ROW_ID
Creating a temporary index on any EIM table is recommended when you are running a MERGE process against it. The
temporary index should be based on T_MERGED_ROW_ID. (12-6H82RB)
Enterprise Server
Task Distribution across multiple AOM instances
When a server has multiple instance of Application Object Managers (such as Call Center) running, new client requests may
not distribute exactly evenly across these instances. The tasks are generally assigned to different instances with round-robin
scheduling. You may see this when there are very few tasks running. Generally when there are a lot of tasks and client
connections active, the load is fairly even, although it will not be exactly even. This should not pose performance issues. (12-
6GQ78N)
Memory and Semaphore Settings on Solaris
To achieve better performance in Siebel deployments with large numbers of users or deployments with multiple enterprises
on Solaris, users should change the default memory and semaphore settings on the machine where the Siebel server is
installed. These settings exist in /etc/system and require root privilege to change. The machine needs to be rebooted to get
the changed settings into effect. The optimal settings depend on the user load that the machine handles.
The following system settings are recommended for a user load that consumes 80% or more of CPU on an Enterprise 450
with four 400MHz processors and 4GB memory. Please consult Solaris administration and tuning documents for further
details on settings for a higher user load.
1. Shared memory:
shmsys:shminfo_shmmax - 0xffffffffffffffff
shmsys:shminfo_shmmni - 1024
shmsys:shminfo_shmseg - 1024
2. Semaphores
semsys:seminfo_semmap - 1024
semsys:seminfo_semmni - 4096
semsys:seminfo_semmns - 16384
semsys:seminfo_semmnu - 4096
semsys:seminfo_semume - 2500

semsys:seminfo_semmsl - 500
(Not applicable to Siebel CRM or Base MME.) (12-5L5ULU)
Executive Information System
Organizational Analysis Charts Warning Message Handling
Users must click Yes to the warning message that pops up the first time they access an organizational chart view. This
warning message asks users if they want to install and run Siebel Systems Inc. Users can select Always Trust Content from
Siebel Systems before clicking Yes to avoid seeing this warning message in the future. If users click No to this warning
message, the organizational analysis charts will be grayed out. (12-8UC1RN)
File System
SFSCLEANUP Utility missing on Unix Platforms
The SFSCLEANUP utility that removes orphaned files in the File System is not available on Unix installations of the Siebel
Server. It will be made available in the 7.5 release. The current workaround is to install the Siebel Server on a Windows
machine as well, and point the SFSCLEANUP utility to the correct File System location on Unix. A 3rd party directory
mapping software will have to be used to make the Unix directory visible to the Windows machine. (Not applicable to Siebel
CRM or Base MME) (12-B0HNTB)
SFSCLEANUP Utility missing on Unix Platforms
The Siebel utility, sfscleanup, is missing from distribution CD for 7.0.4. Contact Siebel Technical Support if you require this
utility. (Not applicable to Siebel CRM or Base MME.) (12-B6I86I)
HTML File Attachments open up in current browser window in Standard Interactivity
In the Standard Interactivity mode, when an HTML attachment is downloaded, it opens up in the same browser window as
the Siebel application. In order to open the file in a separate browser window or to save it onto disk, you have to perform the
following steps:
1. Let the file download into your current browser.
2. Right click on the document and select View Source from the pop-up menu
3. Save the HTML file using the editor that opens up.
4. You can then open the file in a separate window. (12-ACLW1V)
XML File Attachments do not download correctly
On certain browser versions, XML attachments may not download properly. On IE 5.01 and 5.5, for example, an empty
browser window may appear without any data. In the Standard Interactivity version of the Siebel application, the XML
document will open fine, but it may open within the current window and not in a separate window. Below are the
workarounds.
1. Empty window: Always choose save File to Disk instead of Open when the first popup window appears. Then,
when the document has finished downloading, choose the Open button. It should display the document correctly.

2. Opening in same window: For any IE browser with version 5.01 or above, perform the following steps:
a. Go to Folder Options in Windows Explorer.
a. Go to the File Types tab, select XML Document and press the Edit button.
b. Press the New button.
c. Add an Entry with the following parameters:
• Action -- OpenNew
• Application -- "<full path>/IEXPLORE.EXE" (you can use the Browse button to find the full path of
the executable; usually it is stored in "C:\Program Files\Plus!\Microsoft Internet" or "C:\Program
Files\Microsoft Internet")
d. Press OK.
e. Set the newly created entry as the default action using the set Default button. Then press the Close button
f. Close the window. (12-ABTA99)
File Download Problem on IE 5.5 SP 1
Microsoft IE version 5.5 SP 1 contains a bug that prevents users from downloading files from the Siebel File System. Instead
of downloading the intended file, the browser downloads unrelated HTML code. This problem has been fixed by Microsoft
and provided as a hot fix on their web site. It can be accessed at
http://support.microsoft.com/support/kb/articles/Q281/1/19.asp. This problem occurs only on IE 5.5 SP 1. (12-69ZJOS)
Problems uploading/downloading files larger than 100MB
Attempts at uploading or downloading files larger than 100MB may cause the process to time out. This can be prevented by
setting a system environment variable on the machine that runs the Web Server for the Siebel application. The purpose of the
variable is to break up a large data transfer into smaller packets, each of a size specified by the variable. It is called
SIEBEL_SISNAPI_SEGMENT_SIZE, and the value it is given is specified in KB. So a value of 100 means 100KB. The
minimum size it can have 32 KB. For a 100MB file, a good segment size may be 5MB. (12-5LNF9S)
Wrong Name for Downloaded Files
When downloading an attachment from the File System, the file name may be changed to start[ ].xxx. This happens only in
the Microsoft IE browser because of a Microsoft defect that is related to file decompression. For IE 5.01 and 5.5 sp2, the
problem can be fixed by installing a hot fix provided on the Microsoft Support web site. The full URL is
http://support.microsoft.com/support/kb/articles/q303/7/50.ASP. For IE 6.0, a fix will be made available by January 2002.
Alternatively, browser decompression can be turned off for an application. Then this problem no longer occurs, although
performance of file downloads may suffer as a result. For details on turning browser decompression on and off, please refer
to the Siebel Server Administration Guide. (12-9YS7OJ)
Saving small text files in IE 5.01 creates error
If you are using IE 5.01 with Standard Interactivity to run a Siebel application, trying to save a very small file attachment
directly to disk can cause an error. This error only occurs for files that are smaller than ~1KB. The workaround is to first
choose the "Open" option to open the file, and then save it to the disk. (12-9H9RMZ)

Problems uploading or downloading files larger than 100MB
Attempts at uploading or downloading files larger than 100MB may cause the process to time out. This can be prevented by
setting a system environment variable on the machine that runs the Web Server for the Siebel application. The purpose of the
variable is to break up a large data transfer into smaller packets, each of a size specified by the variable. It is called
SIEBEL_SISNAPI_SEGMENT_SIZE, and its value is specified in KB. (For instance, a value of 100 means 100KB.) The
minimum size is 32KB. For a 100MB file, a good segment size may be 5MB. (12-5LNF9S)
Global Time Zone
Connection to Siebel Database on Solaris
On occasion, when a Siebel Server is installed on Solaris in conjunction with Resonate Central Dispatch, the Siebel Server
may not connect to the Siebel Database immediately after the installation completes. The Siebel Server must be restarted in
order for the connection to the Siebel Database to succeed. (Not applicable to Siebel CRM or Base MME.) (12-5U3CFV)
Installation
Receive incorrect "service is already running" message from start_ns command after applying 7.0.5 patch
Steps to remedy this issue:

(1) Download ssrsss.chs file from Support web.
(2) Post Install, navigate to the <Siebel Root>\Siebsrvr\Locale\CHS folder
(3) Replace the ssrsss.chs file with the one downloaded from Support web.
(4) Restart the gateway and siebsrvr.
(12-FE0NZL)
Windows Only: Corba Object Manager patch installation
When applying a 7.0.4.X patch to the Siebel Corba Object Manager, the language files will not install correctly. Please
contact Siebel Technical Support for a script that will repair the Windows registry entries. (12-ER649B)
Database Server Installation (DB2/390 only)
The DDLimp generates all upper case values in schema.sql. The schema.sql file generated by the Siebel Applications install
and upgrade process contains all upper case characters. Although most of the file should beupper case, having all characters
in upper case is not correct because the Siebel Application schema has columns with defaults of both upper and lower case
characters. The schema.sql file must be manually updated with correct values before it can be executed. Below are the list of
default strings that need to be corrected:

from:
AGREE_NAME VARCHAR(50) DEFAULT 'X' NOT
to:
AGREE_NAME VARCHAR(50) DEFAULT 'x' NOT
All occurrences of X need to be updated to x (lowercase)
All occurrences of the upper case versions of the following strings to the mixed case versions:
HORIZONTAL
Default Organization
Associated
Manual
Appointment
Assessment
Active
Unclassified response
Affected
Indirect
Normal
System Add
Original
Include
Asc
Default
Component
Owner
Standard Subcontractor
Recurring
Abort
Payment
Active
Base
FINS
Same as Horizontal.
SIS
In addition to Horizontal, the following 3 must be changed:
Other
ContactPointUsage

NoMatchRowId
For table S_ORGGRP_POSTN, change default MANUAL to Manual (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-B8A9QR)
Configuring DB2 Connect EE Server on separate physical server results in a –519 SQL error. TheDB2 connect gateway fails
with a -519 SQL error when the DB2 Connect EE Server is configured on a separate physical server if PTF UQ62821 is not
installed. See APAR ii13012 Informational APAR for Siebel 7 for a list of required DB2/390 maintenance for Siebel 7 on
DB2/390. This APAR lists the Required Maintenance Level (RML) for Siebel 7 on DB2/390. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-B6R86W)
There is a SQL Error on S_DOCK_TXN_LOG when defined with CLOB. A SQL Error, “SQL0313N …” occurs when
performing an array insert into S_DOCK_TXN_LOG when this table is defined with CLOBs instead of LONG VARCHAR
for the LONG text field. This is due to a DB2 Connect defect.
The following tables should not be defined with CLOBs because of performance and storage characteristics:
S_DOCK_TXN_LOG
S_DOCK_TXN_LOGT
S_DOCK_TXN_SET
S_DOCK_TXN_SETT
S_ESCL_ACTN_REQ
S_ESCL_LOG
S_ESCL_REQ (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B457B3)
Defining LONG VARCHAR columns as CLOBs results in degraded performance. Siebel 7.0.4 provides the capability to
define LONG VARCHAR columns as CLOBs thereby allowing column lengths of up to 1Gb. This provides a solution to the
32K limitation of intermediate SQL results (see 12-5DY43A). Unfortunately the DB2 v7 implementation degrades
performance and can result in significant expansion of storage requirements. The recommendation is to use CLOBs only
where necessary to resolve functional issues. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.)
(12-B38ZTV)
The TargetDatabaseOwner is incorrect for automated DEV2PROD. The TargetDatabaseOwner parameter is not picked up in
DEV2PROD due to misspelling. The workaround is to run the following statements after DEV2PROD completes:
UPDATE S_APP_VER
SET CUSTOM_SCHEMA_VER = CHAR(INTEGER(CUSTOM_SCHEMA_VER) + 1)
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B790YM) 2
The DDLIMP fails because comma is used in European locales instead of period (DB2/390 only). The error listed below is
caused by DDLIMP not correctly handling the comma as a decimal point in European locales. This error will cause DDLIMP
to fail. Workaround: Replace libsslcdb.so, which is referenced by DDLIMP. The library module is available on SupportWeb.
DDLIMP-ERR-0005: SQLExecute: select nullif(0,0) TABLE_QUALIFIER,rtrim(x.creator) TABLE_OWNER, x.tbname

TABLE_NAME, CASE WHEN x.uniquerule =“D’tHEN 1 ELSE 0 END NON_UNIQUE, x.creator INDEX_QUALIFIER,
2
This defect has been fixed in the 7.0.4.10 maintenance release.

x.name INDEX_NAME, CASE x.clustering when “Y” then 1 ELSE 3 END TYPE, c.colseq SEQ_IN_INDEX, c.colname,
c.ordering COLLATION, nullif(0,0) CARDINALITY,nullif(0,0) PAGES from sysibm.sysindexes x, sysibm.syskeys c where
x.name = c.ixname and x.creator = c.ixcreator and x.creator = ? and x.tbname like ? escape “\” order by TABLE_OWNER,
TABLE_NAME, INDEX_NAME, SEQ_IN_INDEX (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-B9IEBW) 3
Modify the key ranges for partitioning databases with EBCDIC code pages. The partitioned index limitkey ranges in the
shipped storage.ctl are specified in ASCII order. This will not work for partitioned indexes in an EBCDIC database. Edit the
storage.ctl (either directly or dbconfig.xls) to reorder the limit key values.
ASCII Example
[Object 4777]
Type = IndexPart
Name = S_ACT_EMP_P99
Table = S_ACT_EMP
PartNum =1
LimitKey = “1”
[Object 4778]
Type = IndexPart
Table = S_ACT_EMP
PartNum =2
LimitKey = “2”
[Object 4779]
Type = IndexPart
Table = S_ACT_EMP
PartNum =3
LimitKey = “A”
[Object 4780]
Type = IndexPart
Table = S_ACT_EMP
3

PartNum =4
LimitKey = “B”
EBCDIC Example:
[Object 4777]
Type = IndexPart
Table = S_ACT_EMP
PartNum =1
LimitKey = “A”
[Object 4778]
Type = IndexPart
Table = S_ACT_EMP
PartNum =2
LimitKey = “B”
[Object 4779]
Type = IndexPart
Table = S_ACT_EMP
PartNum =3
LimitKey = “1”
[Object 4780]
Type = IndexPart
Table = S_ACT_EMP
PartNum =4
LimitKey = “2”
Templates for partitioning EBCDIC databases are available on SupportWeb. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-B7PYTF)
Siebel Systems recommends partitioning EIM tables. You will find guidelines and recommendations for EIM partitioning
strategies in the Implementing Siebel eBusiness Applications on DB2 for OS/390 and z/OS Guide. The supplied storage

templates do not have default partitioning for EIM tables. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-B7LFMY)
The repository upgrade requires RUNSTATS to be executed. Siebel Systems recommends executing RUNSTATS (rstats390)
prior to beginning Repository Upgrade (repos_upgrade.sql). Extremely long execution times are observed if RUNSTATS is
omitted. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B71AGB)
If the Typical Install option is selected on UNIX, only DB2 UDB and Sample file attachments are checked and installed. The
DB2/390 database is not installed. For a DB2/390 database install, there are two alternatives:
• Select Custom Install. or,
• Enter “No” when prompted "Would you like to select these options".
In this case, the Wizard goes back and prompts for each of the available options, including DB2/390. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B6CLIK)
While performing the manual install (the Generate DDL into files option), the Upgrade Wizard prompts twice:While
performing the install with the Generate DDL into Files option (so called “manual” install), the Upgrade Wizard prompts
twice:
1. The first prompt asks to create Siebel Schema, based on schema.sql file. Select Yes for this prompt.
2. The second prompt asks to create Siebel Views, based on ddlview.sql file. Select No for this prompt.
After resuming the installation, select Yes at the next prompt:the Siebel Upgrade Wizard was unable to apply upgrade to
continue the install. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AYOMPE, 12-
B5IS4M)
The log file, produced by the Upgrade Wizard, <siebsrvr_root>/bin/UpgWiz.log, does not contain all errors returned by the
utilities executed. Additional information about the configuration process can be found in sw_cfg_utl.log file. Also,
depending on the operation performed, there are other log files where errors are reflected: ddlimp.log, ddl_ctl.log,
ddldict.log, expschem.log, seed390.log, repimexp.log, imprep_prim.log. All of these files are located in <siebsrvr_root>/bin
directory.
In order to find additional operationspecific log files, open UpgWiz.log, and search for.log string. The result is the names of
log files, produced during the operation. For example, if Database Server Installation configuration fails, the UpgWiz.log
contains the following information:
GenericLog GenericError 1 2002-02-28 15:51:24 (err=1) was returned by application

(D:\sea704\siebsrvr\bin\ddlimp.exe ...<snipped out>)
GenericLog GenericError 1 2002-02-28 15:51:24 Execute file action failed (err=Launching the
application)
In such case, ddlimp.log file will contain the detailed error message:
DDLIMP-ERR-1071: Unable to build ddl statement "add col" (Open unloadtbl.jcl)
The htmlgenm utility builds an HTML file of a summary report for all steps performed by the Upgrade Wizard together with
the information on log files. There are three options for htmlgenm:
/M Master UCF file (Default: master.ucf)
/H Summary HTML file (Default: summary.htm)

/L Siebupg.exe LOG file (Default: UpgWiz.log)
For example, if the Upgrade Wizard performs database install, the command below will generate the summary.htm file into
the <siebsrvr_root>/bin directory:
htmlgenm /m master_install_mf.ucf
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AY72X3)
DBInit fails at end of Initialization process unless Thread Timeout (IDTHTOIN) is set to 3600 or higher. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AZEHEB)
The Siebel Schema Qualifier values have to be entered in upper case for each Siebel Schema Qualifier or TableOwner
prompt for the Upgrade Wizard. The Upgrade Wizard is the Siebel utility used to install, upgrade, and perform various
database manipulations. The wizard is launched by the Configurae DB Server Wizard. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-AYY7WJ)
The installation and upgrade .sql files are shipped with two different types of delimiters: slashes and semicolons. When
executing the .sql files on OS/390, the delimiter used in the particular file being executed must be specified as the delimiter.
Alternatively, customers may change one of the delimiters in .sql files so that the same delimiter is used in all .sql files. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AYXN0E)
EIM performance can be enhanced by adding indexes to the standard data model. The set of additional indexes are distributed
in a Siebel Interchange File (.sif) that is available on SupportWeb. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-AY77D5)
In order to execute the install from the beginning after a previous installation process has been already performed or started,
delete the driver_install_mf subdirectory from <siebsrvr_root>/upgrade directory. Example: When generating new DDL for
the Siebel Schema based on a new or modified storage control file. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-AUNE7Z)
The database installer does not create DLL output directory. When performing the install with the Generate DDL into Files
option, the default output directory is <siebel_root>/dbsrvr/db2390/dboutput/install directory. If another DDL output
directory is desired, the directory must be created externally and prior to executing this step. (Not applicable to Siebel CRM
or FINS CRM or Base MME or FINS MME.) (12-AOHUR3)
Acceptable DDLIMP errors in DDLIMP.log (DB2/390 only)
The following errors in DDLIMP.log are acceptable errors that are expected for certain database configurations, especially
database installation with a Japanese code page.
[IBM][CLI Driver][DB2] SQL0130N The ESCAPE clause is not a single character, or the pattern string
contains an invalid occurrence of the escape character. SQLSTATE=22019
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B3JVK7)
Ignore Oracle Database Choice in Mobile Web Client Installer
The Oracle 8i database client is not supported on the Windows XP platform. However, the Siebel Mobile Web Client
installer allows the user to choose Oracle as the platform of the Siebel Database. To work around this issue, select a non-
Oracle Database platform when installing this client type on this specific platform. (12-AYHHYT)

Null Port Number in Gateway Server Configuration
When configuring the Siebel Gateway Server, the user is prompted to enter a value for the port number. The default value is
null, but this is not a valid value and may cause an error condition even though no error message appears. To avoid
undesirable effects, enter a numeric value. (12-6WTVGB)
Must use root access to install and manage Siebel Enterprise when using automatic restart
If, during installation, you elected automatic restart of the Siebel Server or Siebel Gateway Server every time your system
starts, you must manage (for example start server, stop server,and so on.) Siebel Server and Gateway Server with superuser
(root) privilege. This only effects Unix platforms. (Not applicable to Siebel CRM or Base MME) (12-9PDI70)
SES - Database Server
This is only applicable for the Japanese locale. The imprep.ksh cannot start common api for mstrep_local.dat without ENU.
Make sure that SIEBEL_LANGUAGE is set to the correct language before running the upgrade or install. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5ICPY1)
Mobile Web Client exhibits installation problems related to Microsoft ODBC Access Driver
The following issue is only applicable for the Japanese locale. For Microsoft Windows 95 and Microsoft Windows NT 4
Workstation client platforms, if the Japanese language version of MDAC is used, the only supported version of Microsoft
Office is Office 2000. Office 97 with Word 98 can be used, but this requires that the English, and not the Japanese, version
be installed. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9ZZGMJ)
Language Pack Versions Must Match Base Applications
Before adding any Siebel Language Packs to a Siebel application, make sure their respective release versions are compatible.
or the application may not launch properly. (12-9WCFYO, 12-9WCFZ7)
Uninstallating Mobile Web Client
The Microsoft SQL Server Alias port number may be changed during installation of the Siebel (Mobile) Web Client. If this
happens, use the Alias tab of the SQL Server Client Network Utility to change the port number back to the desired value.
(12-9XPGBL)
French Language Pack Variable Not Expanded on AIX
When adding a French (FRA) Language Pack to a Siebel Gateway Server or Siebel Server in French, the language variable
may appear in the installer prompt unexpanded as the % character (rather than FRA, ENU, etc.).
The actual prompt text is: Voulez-vous ajouter la langue % à l”installation existante ? [O]
This translates in English to, "Would you like to add the French language to your existing installation?" This error is
harmless and will not affect the installation. (Not applicable to Siebel CRM or Base MME.) (12-9YAJ18)
Cannot Specify Blank Parameter Value
An ADM-00010 error may appear in the System Administration Enterprise Parameter view after modifying a Siebel
Enterprise parameter, stepping off the record, and then attempting to clear a parameter value. In order to avoid this anomaly,
no Enterprise parameters should be left blank. (12-9Z9FIP)

Self-Registration Error During Siebel Server Installation
If a user selects the Custom installation type and chooses not to install the Siebel Java Integrator during the installation of a
Siebel Server on Microsoft Windows, the following error message may appear:
the file {siebel server home}siebsrvr\bin\ssceosrv.dll did not self-register. The returned error code was 3.
This may only occur if the host machine has undergone configuration without recent reghosting. (12-9VRQFS)
Internet Addresses Must Be Changed Manually
The new parameter values may not take effect if the First Internet Address or the Alternate Address (of web server) are
modified using the Configure eApplications Server Utility after first being set at installation.. You can work around this by
setting these values manually in the respective .html files located in the public\{Lang} directory, and then saving the files.
These files include:
axcallcenter.html
axfieldservice.html
axmarketing.html
axpmanager.html
axsales.html
axservice.html
indexcallcenter.html
indexfieldservice.html
indexmarketing.html
indexpmanager.html
indexsales.html
indexservice.html
(12-9Y0G2F)
Specifying Alternate Internet Address on UNIX
When running the Siebel eApplications installer on UNIX platforms (AIX and Solaris), the following two prompts appear:
Please specify the First Internet Address of web server[]
Please specify the Alternate Internet Address of web server[]
If a port number other than 80 is used, the Alternate Address must include the port number appended to it. For example:
xyz.siebel.com:8000 (instead of xyz.siebel.com)
(Not applicable to Siebel CRM or Base MME.) (12-9Z9QP7)

Installation of MDAC
The Japanese version of MDAC (version number should be equal to or higher than the version specified for ENU) should be
installed before installing Siebel Applications. This applies only for the Japanese locale. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-963GCZ)
Installation Errors with DLLORA.SQL File on Oracle Database
If you use locally managed tablespaces with Siebel Databases on the Oracle platform, go to Siebel Support Web to obtain a
new version of ddlora.sql. (12-9NE8QB)
Creating a SelfExtracting Archive Using Packager on Window NT Host
When using the Siebel Packager to create a self-extracting archive (client) package on a clean Microsoft Windows NT-based
host machine, the following Dr. Watson for Microsoft Windows NT error message may appear:
An application error has occurred and an application error log is being generated. Mcshield.exe
(In this context of this Release Note, a clean host machine is one on which no Siebel software has ever been installed.
Although this error may appear to be caused by Siebel software, it is not.) Should this error appear, please perform the
following steps to work around this condition:
1. Attempt to recreate the Siebel package again. If this error does not reappear, the package was built correctly.
2. If the error reappears, disable the antivirus software and properly remove it from memory of the local host machine.
(12-9HCJJF)
Data Cleansing Directory Not Set in Heterogeneous Server Environment
The Siebel Server parameter DataCleansingDir is not set when adding a Siebel Server to an existing Siebel Enterprise when
all of the following conditions are true:
The new Siebel Server is being installed onto a UNIX-based (AIX or Solaris) host machine.
The Siebel Gateway Server for this Siebel Enterprise resides on a Microsoft Windows-based host machine (Microsoft
Windows NT or Microsoft Windows 2000).
FirstLogic DeDuplication or Data Cleansing is used for Siebel Data Quality.
To work around this issue, the following operations should be followed:
1. If FirstLogic DeDuplication is being used for Siebel Data Quality, use Server Manager to manually set the server
parameter DeDupTypeDir (Directory used for DeDuplication) to the location of the FirstLogic installation.
2. If FirstLogic Data Cleansing is being used for Siebel Data Quality, use Server Manager to manually set server
parameter DataCleansingDir (Directory used for Data Cleansing) to the location of the FirstLogic installation. (Not
applicable to Siebel CRM or Base MME.) (12-92D917)
remove Microsoft Windows Service Prompt when Uninstalling Gateway Server
When using Uninstall Manager to uninstall the Siebel Gateway Server on Microsoft Windows, a screen that prompts the user
to remove Microsoft Windows Service appears, accompanied by a checkbox. This checkbox is unchecked by default. The
user should always check this checkbox. Otherwise, an inoperative and uninstallable Siebel Gateway Server may remain on
the host machine. (12-6798XP)

Starting a Siebel Server upon Installation on UNIX
At the end of the Siebel Server installation on UNIX platforms (AIX and Solaris), the installers give the user the option to
start the Siebel Server now (Would you like to start the Siebel Server?). If the user chooses yes (Y) to this option, the Siebel
Server will then appear to start running properly, even though it may not be configured correctly.
To avoid this anomaly, the user should instead choose the no option (N) to not start the Siebel Server, then exit the installer,
and start the server manually. (Not applicable to Siebel CRM or Base MME.) (12-6V116V)
Siebel Database Platform Set Incorrectly
Under certain conditions, the Siebel Database Server database platform setting may not be set correctly when a Siebel Server
is added to an existing Siebel Enterprise. Specifically, this may occur when all of the following conditions are met:
The Siebel Server being added is installed onto a Microsoft Windows-based host machine
The Siebel Gateway Server services multiple Siebel Enterprises
The Siebel Enterprises running on these Siebel Database Server database platforms are mixed
From the Siebel Enterprise Server Installer or Software Configuration Utility, the user first supplies the name of an
existing Siebel Enterprise Server, then navigates backwards and changes this parameter to a different Enterprise Server.
To prevent this anomaly from occurring, the user should exit the Siebel Enterprise Server Installer or Software Configuration
Utility and relaunch it before attempting to specify a different Siebel Enterprise Server name. (12-6G4BQN)
Database Configuration Parameter Labels
Certain Siebel Database configuration parameter labels may appear incorrectly in some Siebel Software Configuration Utility
screens. These parameter labels should appear as follows:
Configure Database Options: SqlServer – should be Configure Database Options: Microsoft SQL Server
sqlServer – should be sQL Server Name
sqlDatabase – should be sQL Server Database Name (12-4SBJNV)
LDAP/ADSI Security Adapter
When configuring Siebel applications to work with LDAP or ADSI security adapter, in the application configuration (for
exampleeSales.cfg, eChannel.cfg,and so on.), provide ApplicationUser but provide no value for ApplicationPassword, Siebel
users can login, but the set user info functionality through user profile will fail because of the wrong configuration.
Customers should make sure to set ApplicationPassword in configuration file if they choose to use ApplicationUser. (12-
AXX419)
When configuring Siebel applications to work with Adapter Defined Username (for exampleuse user’s Work Phone Number
as the Login name, Change Username (that is change the work phone number in User Profile) does not work correctly – after
you have changed the username (Work Phone Number), the user will not be able to log in using the new value (the new Work
Phone Number). The workaround is to advise users not to change the value of the field that’s used for them to log into Siebel
application. (12-AP4ZE3)

User Login Through SSL
When customers want to implement SSL to encrypt the user login name and password when they are sent from the browser
client to the web server, they need to specify the Home Page as a Secure View. This can be done in Siebel Tools in the Siebel
View configuration. (12-959KA6)
User Registration Username and Password Length Limit
When using the Siebel user Self Registration function, system administrators should notify users that they should avoid
unduly long usernames/passwords (fewer than 50 characters are preferable). (12-8MVHK7)
Adapter Defined Username (that is, using a non-Siebel userID field as the login name of the user) does not work with the
User Self Registration module outofthebox. To enable this feature, the customer must modify the Self Registration workflow
to set the Login method input parameter to be the adapterdefined username (for example, the user’s email address), and add a
method (in the Self Registration workflow) that propagates the user’s Siebel username (User ID field in the user registration
UI) into the appropriate field in the LDAP directory. (12-6G1ALP)
When implementing Siebel applications in Single Sign On mode, if the trust tokens in eapps.cfg and the application cfg file
are different, when a user tries to log in (through a SSO service), an error is displayed: the request you submitted can not be
processed because of timing out of the connection. Please recreate the request and submit again. Sorry for the inconvenience.
This is a generic error that does not point out the real reason for failed login, but the system administrator can find the real
reason by looking at the eapps log file that distinguishes between the different login failures. (12-633NFV)
Outofthebox, the User Self Registration module does not support Password Syntax Check policies set in the external
directories (such as setting Password Length>=6 Chars in iPlanet LDAP directory). Customers, however, can configure the
registration workflow to capture the error message returned by the Siebel Security Adapter and direct the end user to an
appropriate solution. (12-5DBEBE)
When Siebel software is configured to run with Novell LDAP, and password expiration policy is set up in Novell, a user can
still log in after the password has expired. This is because the Novell LDAP directory provides a concept called Grace
Login–after a user’s password has expired. A number of Grace Logins are provided. The Siebel Web engine might be
enhanced to send the correct alert or warning message to the user when this scenario occurs. (12-6S2DAR)
Other
Workflow Monitor Performance for Send To Position Recipient
Workflow Monitor can exhibit performance problems for policies created with an action that sends an email. To prevent this,
perform the following steps:
1. Stop the Siebel Server.
2. Use a text editor to open the file escl.sql, located in the SQLTEMPL subdirectory of the Siebel Server installation
directory. For example, C:\sea704\siebsrvr\SQLTEMPL.
3. Locate the [DB2/400] section in escl.sql.
4. In the [DB2/400] section, locate the GET_POSITION_MSG_INFO qyery, which looks like this:
GET_POSITION_MSG_INFO =
SELECT pos.NAME, emp.EMAIL_ADDR,
emp.PAGER_PH_NUM, emp.PAGER_PIN, emp.PAGER_TYPE_CD, pg.PAGE_PH_NUM, pos.ROW_ID

FROM &Table_Owner.S_EMPLOYEE emp
INNER JOIN &Table_Owner.S_POSTN pos ON emp.ROW_ID = pos.PR_EMP_ID
LEFT OUTER JOIN &Table_Owner.S_PAGER_COMPANY pg ON emp.PAGER_COMPANY_ID =

pg.ROW_ID
WHERE pos.ROW_ID = ?
5. Insert two semicolons (;;) at the beginning of each line of the query, including the forward slash (/). The query
should then look like this:
;;GET_POSITION_MSG_INFO =
;; SELECT pos.NAME, emp.EMAIL_ADDR,
;; emp.PAGER_PH_NUM, emp.PAGER_PIN, emp.PAGER_TYPE_CD, pg.PAGE_PH_NUM, pos.ROW_ID
;; FROM &Table_Owner.S_EMPLOYEE emp
;; INNER JOIN &Table_Owner.S_POSTN pos ON emp.ROW_ID = pos.PR_EMP_ID
;; LEFT OUTER JOIN &Table_Owner.S_PAGER_COMPANY pg ON emp.PAGER_COMPANY_ID =

pg.ROW_ID
;; WHERE pos.ROW_ID = ?
;;/
6. Save and close escl.sql.
7. Restart the Siebel Server. (12-B15XQF)
eScripts and VB scripts do not process correctly with a DB2/390 database (DB2/390 only)
Customers who use Siebel VB, Siebel eScript, COM Automation Server, COM Data Server, ActiveX Application Control,
ActiveX Data Control, Java Data Bean, and CORBA Object Manager to read a set of BusComp records usingthe Object
Interface Scripting feature must review these scripts for the use of ExecuteQuery.make sure the program logic properly
handles the query limits imposed by cursor configuration parameters. A common usage that needs to be reviewed is to
provide summarized information in an applet, where the applet did not already provide the summarization.
Where the script requires all records, replace ExecuteQuery with ExecuteQuery2 setting the ignoreMaxCursorSize property
to TRUE. IMPORTANT NOTE: Indiscriminate use of ExecuteQuery2 with ignoreMaxCursorSize will result in elongated
response time for the users and excess system resource usage. (12-AURX6F)
Pre-Defined Queries (DB2/390 only)
Data missing in the object drop down list box in query form applet of predefined queries view. For example:
1. Navigate to sitemap >application administration >predefined queries view
2. Click on the query button
3. PreDefined Queries are missing for B to Z.

This is due to the operation of MaxCursorSize when attached to a DB2/390 database. The workaround for nonSiebel
Administrators is the following:
1. Logon to Siebel Tools
2. Go to the Admin Query List BusComp
3. Change BusComp properties: Maximum Cursor Size and Prefetch Size to an arbitrarily large number, for
example1,000.
NOTE: This number must be greater than the number of predefined queries (rows in S_APP_QUERY).
4. Recompile and distribute the SRF.
For Siebel Administrators, they should be using a .cfg which has MaxCursorSize and PreFetchSize set to –1. (12-ALDS9I,
12-B701MO)
Products
When using MSSQL, no image can be associated with a product
Currently, when using MSSQL, if the administrator uploads a graphic through the Document Administration screen, the
graphic will not appear in the Product Images LOV in the Product Administration Screen. To rectify this, the search spec for
the Product Images picklist should be modified accordingly: [LitFileExt]=“BMP” OR [LitFileExt]=“GIF” OR
[LitFileExt]=“JPG” OR [LitFileExt]=“JPEG”. (12-9RSCH3)
If LOV’s are modified after the default values for Class Attributes have been set, default values for Class
Attributes should be updated
If LOV’s are modified after Class Attribute Default values are set, the LOV’s for Class Attributes and their associated
defaults will be out of sync. Consequently, users will receive an error when they attempt to access products that use these
class attributes. To rectify this, administrators should update the default values for any Class Attributes that have been
modified that depend on the LOVs. (12-9TFTYR)
Replication Manager
All server requests and server component parameters in the S_SRM_ACT_PARAM table are fully replicated between the
HQ node and all other regional nodes. As result, data in the Component Requests view can be misleading. Also, if a
particular component exists only in the parent node and not in the child regional node, requests submitted to that component
will lead to an error. To make sure that component requests are routed appropriately, use a different enterprise name for each
enterprise within a Replication Manager implementation. Additionally, the default value of component parameters may be
incorrect. Specify them for each component request where appropriate. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-6EIELP)
The form applet in the Replication Servers view under Siebel Remote Administration contains a field called Database Users.
This field is not indicated as required even though it is a required field. When defining a regional node, please use this field
to specify users to be assigned to the regional node. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-7X7WN3)
When implementing a hierarchy of regional nodes, the Replication Server view does not prevent administrators from adding
users who do not exist on its parent regional node. Consequently, administrators should make sure that all users defined for a
regional node exist in its parent node. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
6G4DZ7)

Send Email
Send Email in Japanese on Solaris
The following issue is only applicable for the Japanese locale. Subject lines written in Japanese on emails for Policy
Manager on Solaris will be corrupted. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
9VU763)
Server Infrastructure
Configuring the IHS Web Server
Make sure the AIX environment is updated to the latest revision levels:
Siebel 7.0.4 requires that IHS is at ML09 for AIX
Runtime library–Requires at least 5.0.2.4
Java client–Requires v1.30
OS environment Settings on the IHS web server:
It is recommended that you set the following IHS Web server environment variables to the values listed below. These need
to be added to the startapa file. You can further tune these settings at your discretion to improve the performance of your
web server.
Recommended startapa additions
export AIXTHREAD_SCOPE=S
export AIXTHREAD_MNRATIO=1:1
export AIXTHREAD_MUTEX_DEBUG=OFF
export AIXTHREAD_RWLOCK_DEBUG=OFF
export AIXTHREAD_COND_DEBUG=OFF
export RT_GRQ=ON
export YIELDLOOPTIME=6
export SPINLOOPTIME=1000
export SIEBEL_ASSERT_MODE=0
export MALLOCOCMULTIHEAP=considersize,heaps:2
#rule heaps:<number of CPU on machine>
export LDR_CNTRL=LOADPUBLIC@MAXDATA=0x60000000
NOTE: You may consider reducing the logging level for IHS to conserve disk space.

Recommended httpd configuration changes
StartServers 1
ServerLimit 1
ThreadLimit 2560
MaxClients 2560
MinSpareThreads 1
MaxSpareThreads 2560
ThreadsPerChild 2560
MaxRequestsPerChild 0
(Not applicable to Siebel CRM or Base MME) (12-B013ZB)
Setting Value of Parameter MinMTServers
Setting the value of server component parameter MinMTServers to zero (0) will cause some server components to stop
running ungracefully. It is strongly suggested that users always set the value of this parameter to greater than or equal to 1.
(12-B4MEH1)
Enterprise Server Name Not Verified
Siebel Server Manager uses the Enterprise Server name from the dedicated web client .cfg file. However, no verification is
carried out to make sure that this is a valid Enterprise Server name. This may causes some component requests that have been
submitted to remain to remain in Queued state indefinitely. To work around this issue when using the Siebel mobile web
client or running siebel.exe, change the EnterpriseName in the Local datasource section to the name of the Enterprise Server
you have configured. To work around this issue when running the Siebel Object Manager (using a browser), perform the
following steps:
1. Navigate to the Server Administration|Enterprise Configuration|Enterprise Profile Configuration view.
2. In the top applet, click on the record Local, which will list its parameter.
3. Search for the Parameter Alias DSEnterpriseServer and change the value to the name of the Siebel Enterprise Server
you have configured. ( 12-B1IYIC)
Searching for Component Group Names
In the Server Administration|Enterprise Configuration view, using a wild card filter to search for Component Groups on the
Component Name field may not work properly. Instead, use the Component Alias field. (12-9AA2W9)
Verify that the language values for server and component language variables are set to JPN
This is only applicable for the Japanese locale. After installing Siebel Server, Make sure that language values for server and
components are set to the appropriate JPN values. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-5FG578)

Some eChannel Configuration Parameters Do Not Remain Set
Some configuration parameters manually set by modifying the [InfraShoppingService] section of the scw.cfg file may not
retain their set values after the host Siebel Server is restarted. These parameters include (but are not limited to) the following:
PersistentShoppingCart
AnonymousQuote
ShoppingCartView
ProductDetailView
In order to make sure that these parameters are properly set, navigate to the Server Administration / Components /
Component Parameters view and modify their values. When these (or any) parameters are modified in this manner, their
values will be preserved.
As a general rule, it is wise to verify that any configuration parameters manually set in application configuration files (that is,
of type .cfg) are actually updated by using the Component Parameters view. (12-A4W13V)
Shut Down Siebel Server(s) on UNIX
Always shut down Siebel servers by running stop_server first. If that fails to stop the servers completely, it will return a
message similar to not stopped: Error trying to stop service process (service may not have stopped). When this happens, run
stop_server -f to force shutdown. In the rare cases where stop_server -f also fails, run reset_server. (Not applicable to Siebel
CRM or Base MME.) (12-7WFH6J)
Securing Administration Scripts
Administration scripts can be passwordprotected by removing administrative credential information and replacing it with the
following to read credentials when executed:
echo Enter SRC_PSWD Password
read src_pswd
SRC_PSWD=$src_pswd
echo Enter EXP_PSWD Password
read exp_pswd
EXP_PSWD=$exp_pswd
This is the recommended approach to securing administrative scripts. (12-1BX98MJ)

Siebel Search
Incorrect Index Field mapping for Literature Search Index
In the original 7.0.4 configuration, in the Search index Literature, both Description field and LitFileName field are mapped to
Document Text. According to HB this is an incorrect field mapping. Please following the following procedure to change the
field mapping for Description from Document Text to Summary.
If you need to use Literature search index, you need to make one repository change in its Search Definition.
a. Launch Siebel Tools
b. Select Search Index Tools object
c. Select the index “Literature”
d. Select sub objects- Search Table - Search Index Field Map
e. Select the index field “Description”
f. Change the attribute Result Field from “Document Text” to “Summary”
g. Compile the srf
This configuration has been changed in Siebel 7.5 search configuration. (12-G41GJP)
Search Applet Address Fields
The order of address fields in international releases will appear as City, State, Country, and ZIP Code. (12-92MG7G)
Search Settings Names
The name used for Search Settings should not include parenthesis. (12-9LWBJ3)
Enabling the Product by PriceList Search Index
In order to enable the Product by PriceList search index, follow the steps below:
1. After creating all indices, modify the .DID file for this index stored in the <Siebel
Root>\Search\ServerDatasrc\Scripts directory as follows: COLUMN [database name].’s_PROD_INT"."ROW_ID"
STORE 200 KEY and COLUMN [database name].’s_PRI_LST_ITEM"."PRI_LST_ID" STORE 205 KEY.
2. Create an ODBC datasource for Fulcrum using the Search Server 4.0 Driver. Enter the full path of the search index
directory location in FULCREATE, the directory of the Fulcrum file FULTEXT.FTC in FULSEARCH, and a
temporary storage directory for FULTEMP.
3. Run the Fulcrum ExecSQL program. Select the datasource that you just created, by choosing File > Select Data
Source. Then run the command unprotect table FUL_PRPL; drop table FUL_PRPL; Open the FTE file
FUL_PRPL.fte file and run it.
4. In Siebel Tools, set the visibility applet type attribute for Product Detail - Features View (eSales) to All.
These steps only need to be done once at setup. Any updating of the index should be done using the Refresh button in Siebel
Search Administration. (12-8GSFU1)

Using system fields as Find fields
To access system fields through the Search Center, configure a new calculated field that uses the system field value and then
build a Find field associated with it. System fields cannot be used directly as fields for a Find objects. (12-6WNGAT)
Refreshing search indices
Search categories based on components of the Siebel file system such as Literature should be refreshed using the Refresh
function and not the Refresh All function. (12-6ZSP32)
Indexing filebased business components in UNIX
For filebased business components like Literature or Resolution documents, Siebel creates the index script, and then the user
manually executes it using Fulcrum’s ExecSql tool. Each filebased component should be completely indexed before
proceeding with the indexing process for the next filebased component. (Not applicable to Siebel CRM or Base MME.) (12-
6WNGAV)
Using the NOT operator
Use the NOT operator delete between two query terms to limit the results in a query to records that contain the first term but
not the second term. Indices are built with one field mapping to a SUMMARY column, and all other fields or document text
mapping to a DOCUMENT_TEXT column in the index. Queries with the NOT operator apply to both the Document Text
and Summary columns in the search index, and return records that satisfy the search criteria for both the name and summary
fields. (12-64OCD0)
Siebel Workflow – Workflow Processes
The user should go to the following BusComps and remove the search specification Message Type > “0”
Message Def
Message Translation Def
Message Map Def
Agreement
PS Subcontractor Agreement
Service Agreement Blanket
Household Agreement (read-only)
The user should then recompile a new srf file.
(12-B9570W)
After activating the workflow process, the Workflow Process DefinitionList Applet becomes empty with no process. This
defect occurs only in DB2/390 when the number of process rows fetched through a query is greater than 48. The workaround
is to set Maxcursonsize and Prefetch = -1 > (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.)
(12-AQXEWV)

After activating the workflow process, the Workflow Process DefinitionList Applet becomes empty with no process. This
defect occurs in DB2 - AS/400/390 when the number of process rows fetched through a query is greater than 48. (12-
B49CM3)
Filter Business Component behavior for Search Specifications
The Filter Business Component field defaults to the business component on which the database operation is being performed.
(12-5OW4MN)
Workflow process in the Japanese Locale
The following navigation path is not supported for workflow in Japanese language for Siebel Mobile Web Client: Workflow
Administration > Workflow Process Instance > Workflow Process. The alternative path is Workflow Administration >
Workflow Processes. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B5A5OX)
After activating the workflow process, the process does not appear in the Workflow Process DefinitionList Applet. This
defect occurs intermittently in Oracle/Solaris. On query, the process reappears. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-B6YMXF)
Instead of Japanese seed data, English seed data might mistakenly be imported
This is only applicable for the Japanese locale. The work around is to pick and save correct Japanese LOV values in cases
where English value seed data is incorrectly imported.
1. Start Call Center
2. Navigate to sitemap > Workflow Processes
3. Query for send Order Accepted Email (eSales)
4. Revise the process (do no activate yet) and drill down on it
5. Double-click on send Email business service on Process Designer
6. On Input Arguments applet, replace the value of recipient Group,Order Contact,and so on with their corresponding
Japanese translations.
7. Activate send Order Accepted Email (eSales)
This workflow should be modified to include the following:
In Workflow Process/Arguments, where LOVs are being referenced, we have to modify such Arguments as follows:
Type=Expression
Value=LookupValue(COMM_RECIP_SRC,'Order Contact')
Similarly we have to use LookupValue(COMM_PROCESS_MODE,"Remote")
The LookupValue function will return the translated value, when we query this workflow process. In the current release, the
Type=Literal so it expects a hardcoded ENU string or JPN string. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-9Z9Y9I)

Updating date fields using the Siebel Operation Step
When using the Siebel Operation Step to update date fields, the date format must be MM/DD/YYYY. (12-9H1AOF)
Viewing Subprocesses
Navigating to the subprocess design from the subprocess step detail view may not navigate to the correct subprocess if
multiple versions of the subprocess are defined. (12-5GHOCR)
Multiple Shifts not Supported with Wait Step
The use of multiple shifts within a single day in a schedule is not supported with the Wait Step. (12-7KJZ4Y)
Siebel Workflow – Workflow Policies
Conditions applet picklist is incomplete
There is an incomplete picklist for Opportunity in the Conditions applet. This defect occurs in DB2/390 where the default
cursor size is set to 48. The workaround is to use Maxcursorsize=-1> (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-AYR74J)
Default PDQ
This is only applicable for the Japanese locale. When initially navigating to the workflow administrator view, make sure that
the predefined query “*All Workflow Policies” is selected. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-9XI2C7)
Defining workflow policy action argument for first time
The first time an action argument is created for a workflow policy action, a pick applet will appear instead of a picklist.
Select the correct value from the pickapplet. The value will not appear in the field until the user steps onto another field. Do
not use Ctrl-S to save the record at this time. This work around is no longer needed once a picklist correctly appears. (12-
9W5933)
Conditions based on Opportunity Close Date not detected if default value is taken
A new opportunity created with close date set as default will not violate a policy with condition based on the Opportunity
Close Date component column. This does not cause a problem if you change the default close date when you first create an
opportunity, or later modify the close date after the opportunity is saved to the database. (12-8CB2Q7)
Send Campaign Email Program
The prospect’s job title substitution for the Send Campaign Email program does not populate the prospect’s job title
correctly. In order to populate the prospect’s job title, the program must be modified using Siebel Tools. (12-LU7TJ)
Creating Workflow Policy Conditions using Not Equal To
When creating a workflow policy condition using a Not Equal To (<>) comparison, make sure that the policy condition
allows for the proper handling of null values. Some database platforms may evaluate the Not Equal To operator as True
against a null value. (12-EE520)

Messaging Alerts in nonEnglish environments
Alerts are not available for Messaging Send Screen Pop to Activity Assignee and Messaging Send Screen Pop to Message
Assignee workflow actions in nonEnglish environments. The workaround is to repick the localized display value in the
Workflow Administration view. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5HQ784)
Text disappears after entry is made
Text added to the message template in the Workflow Email Action Argument Applet may disappear when you create or copy
a record in another applet in the same view. This does not affect functionality. The text reappears when the view is refreshed.
(12-8VSY8R)
Generate Triggers with parameter Mode=ASGN will remove workflow triggers
To delete only the Assignment Manager triggers, you must first run Generate Triggers with Mode=ASGN, Remove=TRUE,
then rerun Generate Triggers with Mode=WORK to recreate the Workflow Policies triggers. (12-5CHG3B)
Site Map
Query button is hidden
This is only applicable for the Japanese locale. In order to use the functionality of the query button, the user must use the
hotkey combination ALT+Q or the dropdown menu. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-97H2H2)
Upgrade
Acceptable error messages (DB2/390 only)
During an upgrade on IBM DB2/390, srvrupgwiz.log contains warningand error messages that are acceptable. Refer to the
errors.rtf on the Siebel Support Web for acceptable errors that are normal and do not indicate a problem. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B9QQ4J)
Upgrade from 6.2.3 to 7.0.4
While upgrading from 6.2.3 to 7.0.4, an error returns while merging repositories!!!Error:: A record that contains identical
values to the record you have created already exists. If you would like to enter a new record, please make sure that the field
values are unique. As a work around, customers should use binary sort order on SQL Server 2000 and use Prior Customer
Repository - 6.2.3 in order to support the merge of Siebel repositories during development upgrade to 7.0.4. For production
deployment, dictionary sort order can be used at the database level. Refer to the Technical Note posted on SupportWeb
(http://supportweb.siebel.com) for detailed instructions. (12-B9UF49)
Error Occurs During Development Upgrade
The following error can occur during the development upgrade process: A record that contains identical values to the record
you have created already exists. To avoid this error, perform the following steps prior to running the upgrade:
8. Using Client Access, open up a 5250 session using the Siebel tableowner profile.
9. From the iSeries command prompt, issue the command STRSQL to get into interactive SQL session.

10. From the SQL session command prompt, issue the following SQL statement. SELECT
MAX(LENGTH(ACTIVEX_PROPS)) from LIBRARY/S_CONTROL
11. Verify that the number coming back from that SELECT is less than 16000.
12. From the SQL session command prompt, issue the SQL statement alter table LIBRARY/s_control alter column
activex_props set data type varchar(16000). Select continue (C) when prompted about possible data loss.
13. Return to the normal Siebel upgrade process and run the repository merge.
14. After merge process is complete, Return to the Client Access 5250 session and complete the following:
From the SQL session command prompt, issue the following SQL statement: alter table LIBRARY/s_control alter
column activex_props set data type CLOB(32000). There will be no warnings for this statement.
NOTE: Replace the string LIBRARY with your Siebel library name. (12-B9HHY8)
This process must be followed upon installation of the Siebel server binaries and must be applied to the Siebel server that is
associated with the upgrade. A customer may install multiple Siebel servers.
NOTE: This procedure applies to Unix and NT midtiers.
1. Go to the directory siebsrvr\sqltempl.
2. Copy the file comdb39.sql and rename the copy as comdb39_org.sql.
3. Open the file comdb39.sql using an editor.
4. Search for the string CUST_CFG_UPG_UPD_JOIN_COL_AND_JOIN and locate the following SQL
CUST_CFG_UPG_UPD_JOIN_COL_AND_JOIN =
UPDATE &Table_Owner.S_FIELD
SET COL_NAME =?,
JOIN_NAME =(SELECT J.NAME
FROM &Table_Owner.S_JOIN J
WHERE J.BUSCOMP_ID=&Table_Owner.S_FIELD.BUSCOMP_ID
AND J.DEST_TBL_NAME=?),
LAST_UPD ={fn now()},
LAST_UPD_BY=?
WHERE JOIN_NAME IS NULL
AND MULTI_VALUED=“N”
AND CALCULATED=“N”
AND REPOSITORY_ID= ?
AND COL_NAME = ?
AND BUSCOMP_ID IN ( SELECT ROW_ID
FROM &Table_Owner.S_BUSCOMP
WHERE TABLE_NAME= ?)
/
5. Replace the above SQL statement with the following:
CUST_CFG_UPG_UPD_JOIN_COL_AND_JOIN =
UPDATE &Table_Owner.S_FIELD

SET COL_NAME =?,
JOIN_NAME =
( SELECT min(J.NAME)
FROM &Table_Owner.S_JOIN J
WHERE J.BUSCOMP_ID=&Table_Owner.S_FIELD.BUSCOMP_ID
AND J.DEST_TBL_NAME=?
AND exists
( select “c”
from &Table_Owner.S_JOIN_SPEC JS,
&Table_Owner.S_FIELD F
where JS.JOIN_ID = J.ROW_ID
and F.BUSCOMP_ID = J.BUSCOMP_ID
and JS.DEST_COL_NAME=“ROW_ID”
and JS.SRC_FLD_NAME = F.NAME
and F.COL_NAME in (“POSITION_ID”,”EMP_ID”)
),
LAST_UPD ={fn now()},
LAST_UPD_BY=?
WHERE JOIN_NAME IS NULL
AND MULTI_VALUED=“N”
AND CALCULATED=“N”
AND REPOSITORY_ID= ?
AND COL_NAME = ?
AND BUSCOMP_ID IN ( SELECT ROW_ID
FROM &Table_Owner.S_BUSCOMP
WHERE TABLE_NAME= ? )
6. Save comdb39.sql and exit. (12-B5C07B)

Incorrect Password Errors in Upgrade Wizard Log When Running DB Utilities.
When running database utilities that execute the Siebel Upgrade Wizard, such as the Char to Varchar conversion utility, the
Upgrade Wizard log file may contain an error indicating that an incorrect password was given for the table owner user. This
error is acceptable, as the Upgrade Wizard will successfully login on a second attempt using the correct password and
continue processing normally. (12-AWN02J)
DDLIMP always reports zero total errors
When validating the schema during Upgrade processing, the utility DDLIMP always produces a summary report showing 0
(zero) validation errors. However, any validation errors are listed in the log file. (12-B6PV3Z)
Upgrading Categories
Prior to running the upgrade, a script should be run to identify any categories that are not assigned to a catalog. These
unassigned categories will need to be associated to a catalog before the upgrade to Siebel 7 or else they will be lost and no
longer usable in Siebel 7. The name of the SQL script that should be run is FIND_UNASSIGNED_CATEGORIES.SQL;
itcan be found in the DbsrvrRootDir\DatabasePlatform\upgrade directory. Run it against the server database using your query
tool of choice; it will generate a list of categories that have not been assigned. It is advisable to run this script until no
unassigned categories are reported. (12-9T4KFJ)
eTraining Test Questions
During the upgrade to Siebel 7, the assumption is made that all records in S_CRSE_TST_QUES contain a not null value in
QUES_TYPE_CD. Prior to attempting the upgrade to Siebel 7, make sure that this column does not contain any null values.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9KNH93)
Production Upgrade with Siebel Anywhere on UNIX Platforms
During an upgrade of Mobile Web Client or Dedicated Web Client,, if a Client Customer Revisions kit is created to
accompany the Siebel Client Executables, users to Siebel 7 using Siebel Anywhere will be prompted to upgrade Siebel Client
Customer Revisions twice. Instruct them to choose to run the Upgrade Wizard both times they are asked. (Not applicable to
Siebel CRM or Base MME.) (12-6W7N52)
Organizational Visibility for Employees
During the standard Siebel Database Schema Upgrade, data residing in S_EMPLOYEE.BU_ID is automatically migrated to
S_CONTACT.BU_ID to make sure that established organizational visibility is maintained in Siebel 7. If the
S_EMPLOYEE.BU_ID column was not exposed through the User Interface in versions 6.x, the following SQL statement
should be run to populate the employee’s organization (S_CONTACT.BU_ID) using the data stored for the organization of
the employee’s primary position (S_POSTN.BU_ID):
update S_CONTACT
set BU_ID=
(select p.BU_ID
from S_EMPLOYEE e, S_POSTN p
where S_CONTACT.ROW_ID=e.ROW_ID
and e.PR_POSTN_ID=p.ROW_ID)

where exists
(select “x”
from S_EMPLOYEE e, S_POSTN p
where S_CONTACT.ROW_ID=e.ROW_ID
and e.PR_POSTN_ID=p.ROW_ID)
This statement should be run after the Upgrade Siebel Database Schema and Upgrade Custom Database Schema steps have
been successfully executed. (12-6WVJ3J)
Check duplicate rows before upgrading Assignment Manager
All customers who upgrade Assignment Manager from a previous version to version 7.0, need to run a script to check for
duplicate rows in the S_ASGN_ATTR_COL table. If there are any duplicate rows, they need to be deleted before the
upgrade is run. The script is available in the dbsrvr directory, and is called asgn_attr_col_chk.ksh. It runs as a Korn shell
program. (12-4SZNF1)
Siebel Upgrade Wizard
During execution of the Upgrade Siebel Database Schema and Upgrade Custom Database Schema portions of the upgrade
process, you may noticethat the globe spins continuously with no updates to the user interface. This behavior is expected for
certain portions of the upgrade and is not an indication of erroneous behavior. (12-44LOK3)
Canceling execution of the database upgrade
If you click the Cancel button on the Siebel Upgrade Wizard while certain SQL statements are executing, the wizard may not
respond. If you must cancel the upgrade at this time, seek assistance from Siebel Technical Services in order to make sure
that it is done safely. (12-47WYIV)
User Registration
When using Siebel User Registration the way it is provided out-ofthe-box, Work Phone # is not a required field. But if you
leave it blank during registration, when you later invoke the Forgotten Password process (from a Siebel application home
page, such as eChannel), you cannot retrieve your password. The work around is for customers to make the Work Phone #
field a required field. Instructions for this work around are available in the User Authentication and Access Control
Administration Guide, Siebel 7 Bookshelf. (12-B25UCC)
Web Framework
The mapping of business component data to feature and configuration tables, intermittently does not populate
field correctly
In certain scenarios, business component data mapped to feature and configuration table columns does not display the
mapped data correctly. It is advised that mapped column data for a given table be populated accurately after designing the
mapped columns before switching to another feature or configuration table. If the data does not appear properly, you can
delete the mapped column and recreate it to correct the problem. (12-B6WOHB)

iPlanet Performance Recommendations
The following steps help improve web server response times when using the iPlanet web server on Solaris.
1. Edit the <user-webserver-install-dir>/config/magnus.conf
2. Set RqThrottle to 1024
3. Add a new entry: MaxKeepAliveConnections 1000
4. Restart the iPlanet web server for these settings to take affect
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AGSP1V)
Environment variable needs to be changes before installing eApps on iPlanet (Solaris)
Thisis only applicable for the Japanese locale. The environment variable for the iPlanet HTTP server needs to be set before
installing eApps as indicated below:
setenv SIEBEL_CODEPAGE 932
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9UC037; 12-9Y3YP0)
When bookmarking Siebel applications, bookmark only the initial login page URL. For example, bookmarking
http://ebiz.siebel.com/callcenter/ . Bookmarking http://ebiz.siebel.com/callcenter/start.swe?... will have trouble loading. (Not
applicable to Siebel CRM or Base MME.) (12-5UNZQN)
Environment variable needs to be changes before installing eApps on iPlanet (Solaris)
This is only applicable for the Japanese locale. The environment variable for the iPlanet HTTP server needs to be set before
installing eApps as indicated below:
setenv SIEBEL_CODEPAGE 932
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9UC037; 12-9Y3YP0)
Avoiding application hangs due to exceptions in browser scripts
When the user introduces an applet browser script (for example, OnPreInvokeMethod) that causes an exception to be thrown,
the application hangs and may have to be restarted. The work around is to make sure that the script does not cause an explicit
exception. For example, the following lines would throw an exception because oMyObject is not valid. This following kind
of code should be avoided:
---------------------
var oMyObject = null;
oMyObject.WontWork(); // throws exception
---------------------
(12-6VF077)

Internet Explorer Settings
High Interactivity clients using Internet Explorer should have the Disable script debugging option set to TRUE. This is
Microsoft's default value for this setting. You can access this setting from Internet Explorer by choosing Tools > Internet
Options > Advanced > Browsing. If this option is not set to TRUE, users may experience performance degradation over the
course of a session. (12-9WYT4N)
Exporting large numbers of Records
While exporting a large number of records, Siebel applications break down the exported data into multiple files. The
maximum number of records that are put in a file is controlled by the configuration file parameter ExportMaxSegmentSize,
which is set under the [SWE] section. By default this value is set to 10,000. (12-6MIN79)
Siebel Analytics
Exception Reports incorrectly displays decimal places
Values resulting in a currency conversion in the OLTP environment and ETL'd to the data warehouse will be displayed
without decimal places or with decimal values of .00 when reviewed using the Siebel Analytics Exception report. To access
this report from Siebel Analytics, select Analytics Administration then Exception Report. This applies to all Siebel
applications and language packs when working with a DB2/390 data source. (Not applicable to Base MME or FINS MME.)
(12-B5IRKK)
Initialization Block on DB2 Must Include Fully Qualified Table Name
The initialization block in the SiebelAnalytics.rpd file must use fully qualified table names (including the table owner name)
when the Siebel Analytics Server is connecting to DB2 databases. (Not applicable to Base MME or FINS MME.) (12-
9YAMJ8)
Legend or Axis Labels Do Not Display

The charting engine employed in Siebel Analytics 7.0.3 has limited ability to display labels (particularly on the y-axis)
because it cannot display labels vertically–only horizontally. As a result, any set of labels where each label contains a
significant number of characters will result in none of the labels being visible. In addition, the chart does not display legends
if the charts are sized too large, for example, in order to make labels easier to read. The work around is to shorten the labels
in question, perhaps by truncating text labels or by dividing numerical labels by 1000. (Not applicable to Base MME or
FINS MME.) (12-A0KCF6)
Column total does not always add up to the total of line items listed in a table or pivot table
In some cases where filters are used in reports, column totals do not add up to the total of line items listed in the tables or
pivot tables in reports. Instead, the total includes data that are not included in the table. To make sure that the totals are
correct, follow these steps.
1. Copy the original report, X, and name it X - 2.
2. Remove the sum function from the X - 2 report.
3. Save X - 2.
4. Edit X report. Click on the Filter by Column icon for one of the nonmetric columns in this report.

5. Click on the Filter based on results of another query hyperlink.
6. Click on the select Request from Catalog hyperlink.
7. Find the X - 2 report in the catalog and select it.
8. Make sure that the Use values in Column field matches the Column field.
9. Verify that the report now aggregates properly.
10. Save the report.
(Not applicable to Base MME or FINS MME.) (12-A3EDNK)
Grand Totals on Tables include data not contained in the rows of the table
When a report contains a subset of records from a database table, grand totals may not sum to the detail records displayed in
the report. This is becausetwo totally separate queries are issued to get the detail and the grand total, and the way the data is
modeled (and/ the values in the data), records are dropped in the detail query (the detail query, by necessity, may include
another dimension table and a fact table that are not needed when doing the grand total query).
For example, the Grand Totals for the Pipeline Overview by Top 5 Verticals table reflect the Opportunity, Expected and
Closed revenue for ALL verticals, not just the top five. If this behavior is not desired, the work around is to filter the table
with the results of another report. To accomplish this, the report that serves as the filter should be identical to the report for
which the filter is used, except that it should not include the Grand Total function. A version of the Pipeline Overview by Top
5 Verticals report without grand totals could be saved as top 5 Verticals Filter Report. This new report could then be added
as a filter to the Industry Vertical column of the Pipeline Overview by Top 5 Verticals report. This addition then limits the
Industry Verticals included in the Grand Total function of the Pipeline Overview by Top 5 Verticals report to those that are
included in the Top 5 Verticals Filter Report. (Not applicable to Base MME or FINS MME.) (12-9ZX8ZV)
Some drills on tables initiate queries that are too restrictive and produce no results
Sometimes drilling on a single line item in a table, for example a single opportunity, yields no results because the drill
initiates a query that introduces new constraints and the associated new table joins. The workaround is to remove columns
from the query until the constraints are lifted and results can be found. (Not applicable to Base MME or FINS MME.) (12-
A2O5CL)
Marketing Analytics
Answers
The Program Summary report on the Programs tab in the Performance Dashboard may give an ODBC error on the Db2-AIX
platform combination. This is due to a large floating point division. To fix this problem the following changes need to be
made:
1. Remove the WHEN 0 THEN NULL portion for the following calculation:
Core.Facts."Aggregate ROI"
CASE Core.FACTS."Campaign Actual Marketing Costs" WHEN 0 THEN NULL ELSE (Core.FACTS."Total Order
Margin" - Core.FACTS."Campaign Actual Marketing Costs") / Core.FACTS."Campaign Actual Marketing Costs" END
2. Use the following as the definition for the W_CAMPAIGN_SA_VW view: (note the cast as double precision
change for CAMP_TGT_CALLS)

CREATE VIEW W_CAMPAIGN_SA_VW AS
SELECT DISTINCT CAMP_ID,CAMP_LANG,CAMP_NAME,CAMP_PROMO_NUM,CAMP_REGION,
CAMP_REGION_I,CAMP_SRC_NUM,CAMP_STATUS,CAMP_STATUS_I,CAMP_TYPE,
CAMP_TYPE_I,CAMP_BDGT,CAMP_CONT_PER_SALE,CAMP_CONV_RATE,CAMP_END_DT,
CAMP_FIXED_COST,CAMP_INB_COST,CAMP_OUTB_COST,CAMP_PRED_COST,
CAMP_PRED_REVN,CAMP_PRED_ROI,CAMP_RESP_RATE,CAMP_REVN_GOAL,
CAMP_REVN_GOAL_DT,CAMP_REVN_PER_SALE,CAMP_START_DT,
cast(CAMP_TGT_CALLS as double precision) as CAMP_TGT_CALLS,
CAMP_CALL_SCR,CAMP_DIVISION,CAMP_DNIS,PROG_ID, PROG_NAME,
PROG_PROMO_NUM,
PROG_REGION,PROG_REGION_I,PROG_SRC_NUM,PROG_STATUS,PROG_TYPE,PROG_END_DT,
PROG_START_DT, PROG_REVN_GOAL_DT,PROG_PRED_ROI,
PROG_REVN_GOAL,PROG_BDGT,
PROG_PRED_COST,PROG_PRED_REVN,PROG_CUST_HIER, PROG_CUST_HIER_LVL,
PROG_DIVISION,PROG_STATUS_I, PROG_TYPE_I
FROM [dbo].[W_PROGRAM_D]
WHERE CAMP_ID IS NOT NULL
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-BD2QGN)
The name of the metric Average # of days from Campaign in the Campaign Metrics folder is incorrect. It should be named
Average Response lag in Days. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9QH4Y3)
The responses per Responder metric in the Facts:Marketing folder, Response Metrics subfolder is incorrect. Please use
Contact Full Name along with # Responses to get to the same information. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-B369RE)
The Aggregate ROI Metric under Facts:Marketing à Campaign Metrics folder is off by two decimals. To fix this change the
display properties for this metric and remove the % sign Oror, in the Siebel Analytics Administration tool, Logical level,
under Core.FACTS, multiply the formula for Aggregate ROI by 100. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-AVOIQ5)
Reports on Marketing Executive dashboard like Current Quarter Order and Oppportunity Revenue and other reports like
Program Scorecard on Performance Dashboard will only be available in English in this release. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-9XM1JR)
Siebel Analytic Applications

Siebel Analytics 7.0.4 requires the use of W_STRINGS_NQ table-an additional table that can be loaded into your Data
Warehouse or on a separate database. This database should be a UTF8 Unicode, UCS2 Unicode, or a Japanese code page

database. However, Informatica can only load Japanese code page data using the standard instructions provided in the
Analytics Applications Installation Guide, and it does not load Unicode data. Check the DW Server guide for setting the
appropriate code page settings on DW Server to load into Japanese code page database. To load Unicode data, you can use
the database specific bulk loading mechanisms. For example, for Microsoft SQL Server, use Data Transformation Services to
load the text into the W_STRINGS_NQ table. (Not applicable to Base MME or FINS MME.) (12-A4WLV6)
Japanese characters in the Web Catalog
When Administrators login to the Analytical Applications and go to Manage Privileges, the subject areas show up in
Japanese. The permissions to the dashboards are controlled through the repository using the Siebel Analytics Administration
Tool, so Administrators should not need to change any permission in the web catalog. (Not applicable to Base MME or FINS
MME.) (12-BDI7Y8)
Chart drilling errors in Integrated Analytics on Unix
Integrated Analytics Dashboards within Siebel applications causes chart related drill down errors when the two applications
are running on separate machines. Running Siebel SWE apps and Analytics Web on the same machine will resolve this
problem (Not applicable to Base MME or FINS MME.) (12-BCYBWB)
Marketing Analytics Performance Dashboards
The chart that is displayed when drilling down on Contacts by Segment and Program report in the Segments page of the
Performance Dashboard appears compressed. Users can increase the vertical scale of this chart by clicking on Modify
Request and increasing the vertical scale of the chart. (Not applicable to Base MME or FINS MME.) (12-BBSLCN)
Initialization Strings in Analytics Applications documentation
When copying and pasting the initialization SQLs from the Analytics Applications Installation guide to the repository, the
quotes appear in a nonstandard form. This is because of the format of the Adobe Acrobat document. Make sure that the
quotes are correct and replace if necessary. (Not applicable to Base MME or FINS MME.) (12-BBC9K0)
NonEnglish Unix Web
When Analytics Web is running on a nonEnglish system of Unix, a new default.jsp file is required. This file is available on
support web and will also be part of the 7.0.4.10 maintenance release. (Not applicable to Base MME or FINS MME.) (12-
BAFQJZ)
Chart Errors on UNIX
If the Chart Server for Unix is running on a machine which has JDK 1.3.1, then some charts will not show up correctly.
Siebel Analytics Web can run on this machine with JDK 1.3.1, however the chart server should not. To have Chart Server
and Analytics Web on the same machine, install JDK 1.3.0 instead of JDK 1.3.1 (Not applicable to Base MME or FINS
MME.) (12-BA7BK5)
Integrated Analytics on Unix
If the Analytics Web Server is on Solaris, HP-UX, or AIX platforms, then Analytics Symbolic URLs in the Siebel
Application will need to be updated. To update, go to View > Site Map > Integration Administration screen. Go to Symbolic
URL Administration view. Query for *NQHOST* in the URL field to get all Analytics related Symbolic URL records. In the
URL Column, change the URL from http://NQHOST/nquireweb/nqwebapi.dll to http://NQHOST/nquireweb/nqwebapi. To

do this for all records, select the applet level menu and choose Select All. This will highlight all records. Then from the
applet menu, select Change Records. (Not applicable to Base MME or FINS MME.) (12-BA7I12)
508 Accessibility for Integrated Analytics
Siebel Analytics 7.0.4 does not support 508 Accessibility requirements. Integrated Analytics within Siebel application is not
supported for users that choose the Accessibility CSS. (Not applicable to Base MME or FINS MME.) (12-B0OR7Y)
DB2/AS400 connectivity
The Analytics Server can hang when DB2/AS400 connectivity is not configured correctly. The Server does not startup and
the service remains in starting mode. Check that the AS 400 CCSID is valid and verify connectivity to the database outside of
the Analytics application. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B3K3O9)
Using back button generates an error
Using the back button after clicking on properties generates an error. The browser back button is not generally not supported,
instead use the Finished or Cancel button. (Not applicable to Base MME or FINS MME.) (12-AX4LC1)
Integrated Security Synchronization
User Responsibility changes made in Siebel application are not effective until the user has ended the session within the Siebel
application and the Analytics Server has dropped the user session. This is because even though the user logs off from the
Siebel application, the Analytics Server still maintains a session for the user and will timeout the user. The responsibility
changes will then take effect after the user logs back in. (Not applicable to Base MME or FINS MME.) (12-B7FSTX)
Missing Admin and My Dashboard views
When the Siebel7Messages.xml file is copied into the SiebelAnalytics\Web\App\Res\Messages directory, it hides the Admin
and the My Dashboard link in Analytics Web. Siebel Applications do not have a view for accessing the Analytics Admin
(For Analytics Web only) and the My Dashboard dashboard. Thus, users cannot get to these two links. The two views will
have to be added to the Siebel application using Siebel Tools. A Technote on support web will be made available. (Not
applicable to Base MME or FINS MME.) (12-B6UIKB)
Analytical Responsibilities
Outofthebox, the user SADMIN does not have the analytical responsibilities assigned. The analytical views will not show up
for this user or any other user until the responsibilities are assigned. Users can be added to a responsibility using the
Responsibilities view in Application Administration screen or through the User Administration view. (Not applicable to Base
MME or FINS MME.) (12-B5H15J)
Analytical Dashboards Inside Siebel Application
Siebel eBusiness application does not maintain the session of the Analytical dashboards. This means that while the user is in
Siebel Answers or any other analytical dashboard, the application can lose session state and log out the user when Siebel
application times out. To avoid this issue, the timeout for the Siebel application should be set high enough. (Not applicable to
Base MME or FINS MME.) (12-A4WG2E)

Siebel Analytic Charting for Windows NT/2000 Environments

The Siebel Analytics charting engine enabled for Windows 2000 and NT OS environments processes data based on the
operating system active code page. For a chart to be correctly rendered, the server accessed must be running in a code page
that supports the text display.
If a environment is not correctly configured, for example a pie chart displaying Japanese data is rendered by a server running
in a Western European code page, the Japanese text will appear as “???”. This behavior is limited to displaying of the values
and in no way affects the processing of the data.
Multiple Siebel Analytics servers can be configuring to access the same data source. In a model where a site needs to render
Chinese, Japanese and Wrester European regional data as charts, three servers should be configured to access the same data
sources.
It is also recommended that cross regional charts are designed to use measures and facts in the Analytics metadata, rather
then display values taken directly from the data source. This will minimize, and in may cases remove, the impact of code
page processing on development and maintenances of the Analytics Applications. (Not applicable to Base MME or FINS
MME.) (12-BE3XFF)
Issue with displaying Japanese characters in charts
Issue with displaying Japanese characters in charts. This issue is applicable for Japanese language implementations. Please
do the following:
1. Stop the chart server.
2. Go to <chart installation dir>\server\\root\charts\siebel.chart, and open siebel.cdx using notepad. The contents of
this file should be as follows:
CDL
BottomTics = ("ON",black,"MS Mincho");
Header = ("ON",black,"MS Mincho");
DwellLabel = ("ON",black,"MS Mincho");
Footer = ("ON",black,"MS Mincho");
LeftAxisTitle =("ON",black,"MS Mincho");
3. Remove the last five lines so that the contents of this file are now:
CDL
4. Save this file
5. Clean up all the html files and graphic files under <chart installation dir>\server\\root\charts\siebel.chart
6. Restart the chart server again
(12-FMZVXZ)

Siebel Answers
When using the Analytics 6.3 to 7.0 ETL package, avoid using the Date column from the Order Date subfolder in the Orders
folder. Use the Order Date column from the Orders folder. The former will erroneously report no results. (Not applicable to
Base MME or FINS MME.) (12-ALEAE9)
Service
ODBC Error Occurs When Combining Person Geography with Other Person Attributes
When combining columns from Person Geography and Persons, ODBC errors may occur. This because both presentation
tables map to the W_PERSON_D dimension table. This dimension table maps to many fact tables. Since the query does not
contain any columns from related fact tables, the Analytics Server picks a fact table at random. In this case, the fact table
chosen is a fact table (W_FN_HOLDING_F) not in the database selected by the DSN for this user (it comes from the
Financial Services Database). This error may be resolved by removing the W_FN_HOLDING_F fact table from the
repository. (Not applicable to Base MME or FINS MME.) (12-9RPV77)
Employee Organization Name is not displaying correct data
When the column Employee Organization Name is picked from the Employee Organization folder in Answers, the data
returned is actually the Employee’s Division Name. To eliminate any confusion, do not use the Employee Organization
Name column. (Not applicable to Base MME or FINS MME.) (12-A3ZX19)
Siebel Data Warehouse
MKT_TRX_S_UNIT is not populated correctly in syndicated market aggregate table
The MKT_TRX_S_UNIT total from syndicated market aggregate table differes from the sum of W_SYND_MKT_F
syndicated market fact table itself. The sum of MKT_TRX_S_UNIT uses an incorrect column for the calculation. To fix the
problem, the expression calculation should should sum from the right port: IN_MKT_TRX_S_UNIT. (12-C6N0CN)
Improving ETL Performance on DB2/390
Performance is slow for DW on DB2/390 database due to the SQL access paths which results in database sort issue
(ReasonCode: 00C90084, 4K page size exceeded). To resolve, make the following changes to the Informatica repository and
to the OLAP database:
Add the syntax “OPTIMIZE FOR 1 ROW” to the slow running ETL sessions SQL statement. The table below lists the
horizontal and SIA sessions that should be modified. In addition to the sessions listed below, if you see similar problems in
custom built or other out-of-the-box sessions, similar modifications should be made. The step-by-step method to make these
changes to the sessions is outlined below.
Run the Following SQL to update the DB2 catalog statistics

UPDATE SYSIBM.SYSINDEXES SET CLUSTERRATIO = 95

WHERE NAME = 'S_POSTN_P1’ AND CREATOR = <OWNER>
UPDATE SYSIBM.SYSINDEXES SET CLUSTERRATIO = 100
WHERE NAME = 'W_REVN_F_F1’ AND CREATOR = <OWNER>
Sessions in the Horizontal Application
Session Name Restart Position Batch Name
Extract Batch
Sde_Activityfact1 Extract_RestartNextBatch10 Fact Staging 3
Sde_Servicerequestfact1 Extract_RestartNextBatch10 Fact Staging 3
Sde_Personfact_contactswithaccounts Extract_RestartNextBatch10 Fact Staging 3
Full Load Batch

Sil_Revenuefact1 Load_RestartNextBatch5 Fact 2
Sil_Assetfact1 Load_RestartNextBatch6 Fact 3
Sil_Orderitemfact1 Load_RestartNextBatch5 Fact 2
Sil_Servicerequestfact1 Load_RestartNextBatch6 Fact 3
Sil_Activityfact1 Load_RestartNextBatch6 Fact 3
Sil_Personfact1 Load_RestartNextBatch6 Fact 3
Sil_opportunitydimension_hierarchy1 Load_RestartNextBatch7 Load Hierarchy
Sil_organizationdimension_hierarchy1 Load_RestartNextBatch7 Load Hierarchy
Sil_georegiondimension_hierarchy1 Load_RestartNextBatch7 Load Hierarchy
Refresh Batch
Sil_opportunitydimension_hierarchy RestartNextBatch7 Hierarchy
Sil_organizationdimension_hierarchy RestartNextBatch7 Hierarchy
Sil_productdimension_hierarchy RestartNextBatch7 Hierarchy

Sessions in the Finance Application
Session Name Restart Position Batch Name
Extract Batch
Sde_Activityfact1 Extract_RestartNextBatch10 Fact Staging 3
Sde_Servicerequestfact1 Extract_RestartNextBatch10 Fact Staging 3
Sde_Personfact_contactswithaccounts Extract_RestartNextBatch10 Fact Staging 3
Full Load Batch

Sil_Revenuefact1 Load_RestartNextBatch5 Fact 2
Sil_Assetfact1 Load_RestartNextBatch6 Fact 3
Sil_Orderitemfact1 Load_RestartNextBatch5 Fact 2
Sil_Servicerequestfact1 Load_RestartNextBatch6 Fact 3
Sil_Activityfact1 Load_RestartNextBatch6 Fact 3
Sil_Personfact1 Load_RestartNextBatch6 Fact 3
Sil_ClaimFact1 Load_RestartNextBatch6 Fact 3
Sil_opportunitydimension_hierarchy1 Load_RestartNextBatch7 Load Hierarchy
Sil_organizationdimension_hierarchy1 Load_RestartNextBatch7 Load Hierarchy
Sil_georegiondimension_hierarchy1 Load_RestartNextBatch7 Load Hierarchy
Refresh Batch
Sil_opportunitydimension_hierarchy RestartNextBatch7 Hierarchy
Sil_organizationdimension_hierarchy RestartNextBatch7 Hierarchy
Sil_productdimension_hierarchy RestartNextBatch7 Hierarchy

Steps to make SQL changes to add the optimizer clause in the Session properties
1. Find to the Session that you want to modify by using its batch name and restart position from the above table.

2. Double Click on the Session name to open the session properties.

3. Navigate to the Transformation Tab

4. Find the Transformation “SQ_JOINER” and click on the Attribute Value to display the SQL,
5. Append the Following SQL “OPTIMIZE FOR 1 ROW” to the existing SQL
6. Click Ok to save the changes
7. Click Ok once again to close the Session properties window
(12-BODQUR)
Running Informatica using DB2 aliases
For Siebel 7.0.4, it is no longer a requirement that the table owner/qualifier is a valid user id on 390. In most cases a customer
will create a RACF group representing the table owner. Appropriate user ids will be included in this group to allow for
creation of the environment and to allow for processes to operate. Running the Informatica server requires that the user id
used to run this server is the same as the table owner and it must therefore be a valid user on the 390.
One option to resolve the issue is to continue having the table owner as a valid user id. For both Siebel and the Informatica
server. Another option is to define a DB2 alias on top of the existing Siebel table to allow for access through this alias. The
solution using the alias is described below. There are possibly other solutions involving using SET CURRENT SQLID
through CLI. This has, however, not been tested at this time.
A DB2 alias allows you to access a DB2 table through a different name and qualifier.
Example:

An alias SIEBEL.MY_TABLE could be created on table SIEBEL.S_APP_VER. A subsequent select on

SIEBEL.MY_TABLE would actually read SIEBEL.S_APP_VER.
An alias Q10E998.S_APP_VER could be defined on table SIEBEL.S_APP_VER. A select on Q10E998.S_APP_VER

would actually read SIEBEL.S_APP_VER.
If the Siebel tables are created with a qualifier of SIEBEL and this is also the name of a RACF group. Then it is not possible
to also use SIEBEL as a valid user id. To circumvent this problem an alias can be created for all the tables created with a
qualifier of SIEBEL. The aliases would need to be qualified with a value that was also created as a valid user id on the 390.
If INFOMA is created as a valid user id then the aliases can be created using this as the qualifier.
Example:
For table SIEBEL.S_ORG_EXT create alias INFOMA.S_ORG_EXT.
For table SIEBEL.S_APP_VER create alias INFOMA.S_APP_VER.
This setup would allow for the Informatica server to execute under user INFOMA.
For creating the where house tables there are two choices. Create them with the same qualifier as the Siebel tables, or create
them with the qualifier equal to the user used for Informatica.
If the tables were created with the same qualifier as the Siebel tables, aliases would also have to be created on these tables.
This setup depends on where the OLAP and the OLTP tables are defined. It also depends on the security setup needed
between the Siebel tables and the where house tables.
There are several known issues with this approach:
Aliases do not get dropped when tables are dropped.
Requirement that the Information qualifier is a valid user.
In the case of aliases the alias qualifier have to be a valid user.
How to create the aliases:
The aliases are created using the CREATE ALIASE SQL statement.
Example:
CREATE ALIAS Q10D990.W_PROGRAM_D
FOR Q102016.W_PROGRAM_D;
One method to create all the aliases is to create a REXX that reads in a list of tables and then create all the CREATE
ALIASES statements. The list of tables can be create running a SQL statement reading column NAME from
SYSIBM.SYSTABLES. The REXX below is a sample that can create all the statements:
/* REXX */
INPDS = "'JORNF.USER.EXEC(DW)'"
OUTPDS = "'JORNF.USER.SQL(DWALIAS)'"
"ALLOC FI(OUT01) DA("||OUTPDS||")"
"EXECIO 0 DISKW OUT01 (OPEN "

"ALLOC FI(IN01) DA("||INPDS||")"
"EXECIO 1 DISKR IN01 (STEM Y."
EOF = RC
DO WHILE RC = 0
PARSE VAR Y.1 TBNAME REST
OUTL.1 = 'CREATE ALIAS Q10D990.'||TBNAME
OUTL.2 = 'FOR Q102016.'||TBNAME||";"
"EXECIO 2 DISKW OUT01 (STEM OUTL. "
"EXECIO 1 DISKR IN01 (STEM Y."
EOF = RC
END
"EXECIO 0 DISKR IN01 (FINIS "
"FREE FI(IN01)"
"EXECIO 0 DISKW OUT01 (FINIS "
"FREE FI(OUT01)"
EXIT
(Not applicable to Base MME or FINS MME.) (12-B68ISZ)
Configuring Siebel Data Warehouse on MSSQL
During Siebel Analytics installation create a folder named log under <Install dir>\dwdb before selecting the options to Create
Informatica Repository, Configure Informatica Repository, Drop Siebel Data Warehouse tables, or Create Data Warehouse
tables. These options are visible under the Siebel Data Warehouse Configuration step of installing Siebel Analytics. Also,
ignore the [Microsoft][ODBC SQL Server Driver]Cursor type changed\ error messages in the ddlimp.log file. (Not applicable
to Base MME or FINS MME.) (12-B8UOP3)
EBCDIC code page for Siebel Data Warehouse
EBCDIC code page for Siebel Data Warehouse is not supported. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-B61RAB)
Siebel Analytics Server must be running on an 1252 code page
Siebel Analytics ETL server must be run on a 1252 code page OS. In addition, the ETL server must use a period (.) as the
decimal delimiter in order to assure uncompromised functionality. Note: though the ETL server must be on a 1252 code
page OS, the data source and target can be on any (including non-European and double-byte) Siebel-supported code page,
provided that the data source and data target code pages are the same. (Not applicable to Base MME or FINS MME.) (12-
72IOAF; 12-6VVHSN; 12-ASAKIF)

Column Name Change for W_STRINGS_NQ
The name of the column LOCALE in the table W_STRINGS_NQ has been changed to LOC in Siebel Analytics v7.0.4.
When upgrading the Analytics repository to 7.0.4, the table W_STRINGS_NQ should be dropped and recreated using the
ddl file Crt_Analytics_Tables.ctl. This fileis included on the Analytics Applications 7.0.4 installation CD under \Install\Data
Warehouse Initialization\ETL\ directory. Then the data will have to be reloaded using the supplemental ETLs. Alternatively,
customers can change the column name to LOC using Database specific utilities. (Not applicable to Base MME or FINS
MME.) (12-AQXKJN)
Installing Siebel Data Warehouse on DB2 OS/390 database
If the Siebel Data Warehouse is on DB2/390 database, make the following change on the eBusiness Data Warehouse Server
(Informatica server) machine. run regedt32 and go to the following path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PowerMart\Parameters\MiscInfo
Go to Edit > Add value as DB2Isolation, double click on it and set its value to 1. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-B7LQCQ)
DWDB Drop.sql
The DWDB Drop.sql does not contain drop statements for the following warehouse tables: W_STRINGS_NQ,
W_DAY_D_NQ, W_INDUSTRY_D_NQ, and W_CTRYREGN_D_NQ. These tables will need to be dropped manually in
case of recreating the Data Warehouse from scratch. (Not applicable to Base MME or FINS MME.) (12-B8AMEI)
Siebel Analytics Server must be running on an 1252 code page
Siebel Analytics ETL server must be run on a 1252 code page OS. In addition, the ETL server must use a period (.) as the
decimal delimiter in order to make sure of uncompromised functionality. Although the ETL server must be on a 1252 code
page OS, the data source and target can be on any (including nonEuropean and double-byte) Siebelsupported code page,
provided that the data source and data target code pages are the same. (Not applicable to Base MME or FINS MME.) (12-
72IOAF; 12-6VVHSN, 12-ASAKIF)
MSSqlSrver database
When using the Dictionary Sort option for a MSSqlSrver database, you must use CASE SENSITIVE sort order. Case
insensitive sort order will cause the ETL process to fail. (Not applicable to Base MME or FINS MME.) (12-4LUZ7M)
Install
When you install ODBC 3.5 from Informatica, you will be asked if you want to replace an older version of odbcp.dll. Do not
replace the older version. (Not applicable to Base MME or FINS MME.) (12-513Z6K)
Contacts in Revenue Star
There is no primary contact for an Opportunity. Hence contacts for the Revenue star are derived from the Siebel Revenue
view and are not necessarily based on the contacts shown in the Siebel Opportunity view. (Not applicable to Base MME or
FINS MME.) (12-6722ZX)

Oracle ODBC driver
While running the IMR you may encounter the following error: evaluation period for this Oracle ODBC driver has expired.
Rename or move ivodbc.lic and lvodbc.lic (if it exists) and lvdw.lic (if it exists). Make sure that you only have one license
file named ivdw.lic in winnt\system32. (Not applicable to Base MME or FINS MME.) (12-8K49HN)
Incremental Load
While executing the refresh_Siebel_DW batch, the Informatica server fails at SIL_Organization Dimension. This is a
random failure. The workaround is to simply restart the batch. (Not applicable to Base MME or FINS MME.) (12-6R17EV)
Performance Statistics
Some session mappings hang when running with performance statistics switched on. The work around is to increase the value
of the LMSharedMemory and MaxSessions variables in Informatica. The risk of increasing the LMSharedMemory too much
is that it may impact overall performance of the machine that the Informatica server is running. (Not applicable to Base MME
or FINS MME.) (12-3WAO28)
Net Price in Quote and Order line items
In Quotes and Orders customizable product line items, the Net Price in Siebel eBusiness Data Warehouse may not match the
Net Price shown on the Siebel Quotes and Orders line items. The Net Price for Quote and Order line items in the eBusiness
Data Warehouse is derived from the Discount Price, or computed as (Start Price – Discounts) from the customizable product
root line item. In order to keep eBusiness Data Warehouse Net Price in sync with Quotes and Orders, the root of a
customizable product should reflect all discounts given at its children line items. (Not applicable to Base MME or FINS
MME.) (12-6SPDDX)
Informatica Mapping Report (IMR)
The source-to-target dependency IMR does not show the expression transformation column consistently. This is a known
Informatica issue. (Not applicable to Base MME or FINS MME.) (12-6RV7IP)
Analytics Administration
In order to execute a new query in the Exception Reports view, use the menu or the shortcut keys. The Query button is not
functioning properly. (Not applicable to Base MME or FINS MME.) (12-75KFB5)
Post session email notification in Outlook 2000
An error occurs when you configure a session to send an email notification: the Informatica Server encounters an Extended
MAPI Error and does not send email. The workaround: after installing the Informatica Server on Microsoft Windows, copy
the file mapi32.dll from winnt\\ system32 to the bin directory where the Informatica Server is installed, overwriting the
existing mapi32.dll in that directory. Start the Informatica Server so that the Informatica Server can use the new mapi32.dll.
The error Extended MAPI Error. MAPILogonEx failed[2147746065] indicates that the logon is not configured correctly.
Please check the following three places:
1. Under Services > Informatica> Logon, make sure the login (domain\\username) and password are correct.
2. Under Control Panel > Mail (it may also be called Mail and Fax or Exchange) > Services > Show Profiles, make
sure the mail profile is correct.

3. Under Programs > Informatica Server > Informatica Server Setup > Miscellaneous, make sure the MS Exchange
profile is correct. (Not applicable to Base MME or FINS MME.) (12-8BRQW7)
Importing mappings through XML
You may receive the following error while importing mappings through XML: Warning: Unexpected condition at:
tsapfunc.cpp: 6837. When you encounter this error message, press Continue and your mapping will be imported. (Not
applicable to Base MME or FINS MME.) (12-8EWT17)
Informatica Post-session Email
Informatica closes the Outlook 2000 application when sending out a postsession email notification. The work around is:
1. Create a second profile in Outlook.
2. Add that profile name to the Informatica server setup.
(Not applicable to Base MME or FINS MME.) (12-8JZ4JD)
DataMart
In the Response Universe Account, the name is unspecified for Prospects. This is because prospects are not considered to be
assigned to an account. (Not applicable to Base MME or FINS MME.) (12-5EI752)
Service Analytics
The Total Order Revenue and Total Order Revenue Moving Avg metrics are incorrectly subtracting Freight amount and Tax
amount from the sums. (Not applicable to Base MME or FINS MME.) (12-B3A0MY)
Metrics that are moving averages, for example, # of Assets Moving Average, may occasionally have results that are incorrect
due to truncating of the results rather than rounding up. (Not applicable to Base MME or FINS MME.) (12-AQB659)
When using the IBM DB2 database platform and viewing the Activity Travel Time by Service Region report on the Field
Service page in Activity Analytics, a View Display Error would occur. This is due to an arithmetic calculation overflow
error. (Not applicable to Base MME or FINS MME.) (12-A52WYE)
The charting engine used in the Siebel Analytics Server for AIX 4.3.3 is not able to render combined charts that have
columns as well as a superimposed trend line. The affected reports are Activity Trends, Assets by Shipping Month, Assets
by Install Month, Assets by Registration Month. (Not applicable to Base MME or FINS MME.) (12-BDAB4B)
Loyalty Customer Groups (Years) Dropdown does not function properly
When selected, the Loyalty Customer Groups (Years) dropdown on the top of the Loyalty page causes charts to become
unreadable. This dropdown should not be used. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.)
(12-A4VFIJ)

Campaign Predicted Metric with ratios under Facts: Marketing/Financial Modeler Metrics do not aggregate
appropriately
The following metrics are aggregated incorrectly across campaign occurrences:
Campaign Predicted Response Rate
Campaign Predicted Conversion Rate
Campaign Predicted ROI
This is because they are using the avg() function in the Administration Tool Metadata. For example:
Campaign Predicted Response Rate is avg(W_CAMPAIGN_SA_VW.CAMP_RESP_RATE).
These calculations use weighted sum of Predicted # targeted and sum of Predicted # responded and then do the calculation as
sum(Predicted # Responded)/ sum(Predicted # Targeted) to get the accurate weighted average.
The corresponding Actual metrics:
Actual Response Rate
Opportunity to Order Conversion rate
Aggregate ROI
work correctly when aggregating across campaigns.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-A3GFS2)
Answers
The Closed Net Margin metric under Facts:Opportunity Level Folder does not work correctly. (Not applicable to Siebel CRM
or FINS CRM or Base MME or FINS MME.) (12-AQ9N36)
The metric % of Contacts Geo for All Accounts is incorrect. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-ARXBNR)
The Household name shows Household ROW-ID from the OLTP instead of name. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-AST928)
The metric Marketing Cost per Responder Variance under the Facts Marketing, Variance Metrics Folder in the Marketing
Subject Area is incorrect. To fix it, change the calculation for this metric in the logical level to Campaign Actual Marketing
Cost/ # Unique Responders – Campaign Predicted Cost/Campaign Predicted # of Responders. This fixed calculation will
only work at the campaign occurrence level. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.)
(12-ATAHHN)
Certain Segments may not be used alongside campaign occurrences to measure metrics like response rate, since segments are
joined to campaigns and not occurrences. Hence, a report containing a segment and campaign name will not work
appropriately when the campaign name is drilled upon to get to campaign occurrence name. (Not applicable to Siebel CRM
or FINS CRM or Base MME or FINS MME.) (12-ATG8MA)
The metric # Offers in the Facts: Marketing folder gives incorrect result. This information is typically obtained from the
Siebel Marketing Application. The Siebel Analytics application should not be used to get this information. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AU5L37)

The Household income metric under the Household folder in the Marketing subject is not calculated correctly. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AU9238)
Line Items Outstanding in Japanese
The Line Items Outstanding by Priority Details feature of the Order Analytics (Orders) has not been enabled for the Japanese
user interface in the Siebel 7.0.3 release. This feature is available by upgrading your analytics_localized_strings.txt available
through SupportWeb. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-A3NVGV)
ETL in nonEnglish Locales
The following issue is applicable to nonEnglish locales. The Informatica Server Manager uses a period (.)for extracting to
the database. For nonEnglish locales make sure that the decimal separator is a period (.)instead of a comma (,). (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9Y3KAR)
Performance
Closed Revenue Variance Metric in Facts: Marketing Variance Metric folder is incorrect
The Closed Revenue Variance Metric is currently as follows:
Core.FACTS."Closed Revenue" - Core.FACTS."Program Predicted Revenue"
To fix the problem see the metadata expression for Closed Revenue Variance
Change it from:
Core.FACTS."Closed Revenue" - Core.FACTS."Program Predicted Revenue"
to
Core.FACTS."Closed Revenue" - Core.FACTS."Campaign Predicted Revenue". (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-A2MFGB)
Revenue Distribution by Price List report
The chart displayed in the Revenue Distribution by Price List report is not large enough to display information. To increase
the size of the chart perform the following:
1. Click on modify request
2. Click on Results tab
3. Click the Customize View button within the results page
4. Edit chart properties by clicking the respective resizing buttons to increase the width and size of the chart.
5. Save the report. (Not applicable to Base MME or FINS MME.) (12-BBOBNF)

Quarter drills to Week instead of Month.
In the Sales Effectiveness dashboard Overview page, drilling into Average Deal Size by Quarter or Average Sales Cycle by
Quarter reveals the appropriate metric by Week, and not Month. The work around is to reconfigure the hierarchy in the
metadata to create the desired effect, or specify a Go Nav link in the chart that takes the user to the appropriate chart by
Month. (Not applicable to Base MME or FINS MME.) (12-9XKBVN)
Assessment metrics do not display meaningfully with Opportunity Revenue metrics.
Most Recent Opportunity Assessment Score % metric cannot be meaningfully displayed alongside Opportunity Revenue
metrics from the Opportunity Facts folders for a given opportunity. The Opportunity Revenue cannot be displayed by
Opportunity Assessment Score Quintile. (Not applicable to Base MME or FINS MME.) (12-9R9IMB)
Nulls sort first is OFF.
This makes reports that rank things from largest to smallest, such as a Top 10 report, show NULLs first. The work around is
to set system settings so NULLs sort first is ON, or add filters to the specific report that sort out all NULLs. (Not applicable
to Base MME or FINS MME.) (12-A51Q03)
RFM Quintile calculations use non-standard ranking algorithm
The RFM Quintile calculations performed during the ETL process can assign one rank to multiple recipients without
incrementing the rank of the next item an equivalent amount. For example, if 20 items were being ranked and 10 were all tied
for first, there would be 10 items with a rank of 1 and the 11th item would have a rank of 2, not 11. The work around is to
modify the ETL script to assign standard ranking metrics during the ETL process. (Not applicable to Base MME or FINS
MME.) (12-A51Q0J)
Universe: Household contains all active and inactive contacts
OLTP does not display contacts that have exited the household (that is, where END_DT_WID < SYSDATE) but OLAP
stores all household contacts (active and inactive) in the Household universe. (Not applicable to Base MME or FINS MME.)
(12-633402)
Pipeline Analytics
Missing physical columns and tables in the Sales Subject Area
Since the Sales subject area includes some metrics and tables unique to the Siebel Industry Applications, in addition to those
present in the base Siebel Sales application, users of the base Siebel Sales application may have some missing columns or
tables in their Sales Subject Area for those tables and columns that exist solely in the Siebel Industry Application. (Not
applicable to Base MME or FINS MME.) (12-AN47VB)
Filtering for any quarter or year in the Global Filter removes Default filters
All reports in Sales Analytics have a filter that defaults the report to the Current Quarter or the Current year. Filtering for any
quarter or year using a Global Filter will replace the default quarter or year with the selected quarter or year. Once the default
quarter is replaced, it cannot be recovered without leaving the page. The work around is to click to another page in the same
Dashboard and then click back. (Not applicable to Base MME or FINS MME.) (12-A0KCFK)

Siebel Anywhere
This error is encountered during the Upgrade Kit creation process using the Auto Create Wizard. When the user finishes the
last step of the Wizard, they may receive the following error message illustrated below. In order to avoid this issue, the user
will need to change the text in the Upgrade Kit Title field to less than 50 characters. (12-9XLW5B)
The Packager Utility does not properly package versioning files created on UNIX application servers
Versioning files such as the clntrev.cfg are not packaged properly by the Packager Utility if they are created on UNIX
application servers. For example, if the clntrev.cfg file contains the following item,
[Siebel] <something that looks like a "0">
Version = 1
only the first line will be included in the file that the Packager included in its package. The end-user will be prompted with
the message to perform an upgrade after he has installed the package. This defect affects the Siebel Client Customer
Revision component and all language based Siebel Client Customer Revision components.
There are two work arounds for this issue. One, the end-user can accept the upgrade as suggested by the message and the
process will continue without any issue. Two, the administrator can manually correct the content of the versioning file by
replacing the incorrect character with a <new line character>. Doing so will allow the Packager Utility to package these files
properly. (Not applicable to Siebel CRM or Base MME.) (12-B6OXWB)
Product Updates
When selecting optional upgrade kits from the Product Updates view, make sure that after selecting an Upgrade Component
and before choosing Upgrade Selected Components you do not scroll down the list. If you do, certain kits cannot be
retrieved. To retrieve these kits, reconnect and select the Upgrade Components which could not be selected previously. (12-
7JNPYD)
Downloads of Optional Upgrade Kits
At certain times, when a mobile user has chosen to apply an optional upgrade kit and at the same time a required upgrade kit
is distributed by the Siebel Administrator, the optional kit may not be downloaded and applied until the next synchronization
session. (12-7301G7)
Siebel Call Center

Configuration for Agreement-Primary Contact-Parent Agreement Field Popup screen on DB2 UDB for zseries
Platform
The performance of the Agreement-Primary Contact-Parent Agreement Field Popup screen can be improved by executing the
following work around: create an index on S_DOC_AGREE (SALES_REP_POSTN_ID, ROW_ID) and runstats on the new
index. The SQL Statements are:
CREATE INDEX SIEBEL.S_DOC_AGREE_TEMP
ON SIEBEL.S_DOC_AGREE
( SALES_REP_POSTN_ID ASC ,
ROW_ID ASC )

PRIQTY 720
SECQTY 14400
ERASE NO
FREEPAGE 0
PCTFREE 15
GBPCACHE CHANGED
BUFFERPOOL BP2
CLOSE YES
PIECESIZE 2 G
COPY NO
DEFINE YES
and
RUNSTATS INDEX (SIEBEL.S_DOC_AGREE_TEMP)
REPORT YES UPDATE ALL SHRLEVEL CHANGE (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-B3JB43)
Chart legends are missing for some Japanese reports
This is only applicable for the Japanese locale. Chart legends are missing for some Japanese reports. Maximizing the report
window will make these visible. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9YTT0F)
Consumers
User Interface
There is no More Info view tab for the Consumers screen. To navigate to the Consumers list applet when in the Consumers
Screen, go to the Show menu dropdown and select All Consumers. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-5UXXZV)
Communications Server
Application Menu View/Communications Commands
When selecting a Communications command from the View/Commands applications, the user will need to refresh the view
by using the Siebel History Back and Forward buttons. (12-AS3R08)

Slow view in Outbound Request Overview view
When querying on the Outbound Request Overview view, the query may run for a longer time than expected (> 5 seconds).
Users should wait for the query to complete as shown by data displayed on the user interface. (12-9VUBPZ)
Communications toolbar in multiple browser sessions
When using multiple browser sessions to access the Siebel application using the same login id, communications enabled
agents will have access to the communications toolbar in each browser session. This may cause confusion and unexpected
behavior for the agents. To manage this, the administrator should set the MaxCommToolbars parameter in the
communications configuration to one. Setting this to one will only enable the communications toolbar in the first browser
session and not in any other browser sessions opened. (12-9VBMFN)
Changing Not Ready State from the Menu Bar commands
When changing agent work mode using View->Communications->Work Mode, the Reason Code popup does not appear as it
does when clicking the Change ready state button on the Communications Toolbar. To enable the Reason Code pop-up, the
administrator should associate the NotReadyWithPopup command data with the AgentOtherWork command in the
Communications configuration. (12-9V1C7H)
Putting outbound work items on hold from communications toolbar
Agents can initiate outbound communications from the new multichannel communications toolbar. When initiating
outbound work items, agents should not put these items on hold. Agents are required to complete or release these work
items. (12-4ZTT6L)
Putting outbound work items on hold from communications toolbar
Agents can initiate outbound communications from the new multi-channel communications toolbar. When initiating
outbound work items, agents should not put these items on hold. Agents are required to complete or release these work
items. (12-4ZTT6L)
Customer Dashboard
Update Dashboard Business Service
In the Update Dashboard business service, the parameter, Buscomp Name, should be entered with two spaces between
Buscomp and Name. In 7.5 it will be corrected to one space. (12-BGI5ZJ)
Change to the Dashboard CTI Parameters
In 7.0.4 there is a new parameter, Serviceparam.Buscomp Name, which is used to specify the business component when
updating the dashboard from CTI. If this parameter is not included then it will default to the contact business component.(12-
9BSFF8)
When accepting a transferred call, the Agent receives a second screen pop, which replaces the initial screen pop.
In the CTI Definition file for Dialogic remove the following parameters for the command OnCallTransferred:

[EventResponse:OnCallTransferred]
QueryBusObj = "Contact"
QueryBusComp = "Contact"
QuerySpec = "“Work Phone #”=“{ANI}”"
SingleView = ‘service Contact Detail View"
MultiView = "All Contacts across Organizations"
Keep the parameters below.
; To update Dashboard
ServiceMethod = "Persistent Customer Dashboard.Update Dashboard from CTI"
ServiceParam.Field = "Work Phone #"
ServiceParam.Value = "{ANI}" (12-9CBTAF)
set Dashboard button in Search Center
The customer dashboard has been configured to populate for Contacts, Employees, and Consumers. For all other search
objects such as Accounts, when you click the set Dashboard button nothing occurs. Using Siebel Tools you may configure
the customer dashboard to populate for the other search objects. (12-91RIWF)
NOTE: The Consumers feature is not available in Base MME or FINS MME.
Displaying CTI ANI number in the Customer Dashboard
In Siebel 2000, displaying a caller’s ANI number in the dashboard when screen popping to a SmartScript was achieved
through the SmartScript [CTI.ANI] dashboard parameter. In Siebel 7, information associated with the caller, including the
caller’s telephone number, can be populated directly through CTI commands rather than managing parameters through
SmartScript. (12-8VDDD6)
Households
Defining Address for Contacts Within A Household
Households consist of one or more Contacts with each Contact having one or more primary addresses. For multiple contacts
in the same household (or at the same address), the address will need to be entered for each contact. (Not applicable to Siebel
CRM or Base MME.) (12-6CPO6G)
Reports
Chart legends are missing for some Japanese reports.
This is only applicable for the Japanese locale. Chart legends are missing for some Japanese reports. Maximizing the report
window will make these visible. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9YTT0F)

Outbound Requests
In this release, activities created from an Activity Plan cannot be deleted. (12-9BRP7R)
Siebel Campaigns
Campaigns Charts only display summary-level opportunity data
Note that the Opportunity Revenue Analysis and Opportunity Revenue Analysis by Employee charts show summary level
opportunity revenue only. In order to ensure that the revenue line items and summary revenues are in sync, navigate to the
Opportunity > Revenues view, go to the applet level menu in the child applet, and click on 'Update Opportunity.' (12-
EH4Y93)
Prospects added to list are not automatically included in the campaign
Prospects added to a list after the list is associated to a campaign will not automatically be included in that campaign. This is
because all prospects are associated to the campaign at the time that the list is first associated to the campaign. To make sure
any new prospects are included in the campaign, delete and reassociate the list to the campaign after the new prospects have
been added to the list. (12-AX7FVF)
Campaign Offers Views
The Campaign Offers views have been moved from the Campaign Administration screen to the Offers screen. (12-B5VBT5)
Campaign Charts
The Campaign charts will not be visible if the data set of My Campaigns is too large or if the Campaign names are too long.
(12-9X08CO)
User Interface
In the Campaign Administration screen, the view tabs appear floating. To fix this, make sure that there are no empty applet
placeholders between applets in the view template. (12-AJEYNC)
Contacts or prospects added to campaigns created in Siebel Marketing will not receive emails
Contacts or prospects that are added directly to campaigns that were originally created in Siebel Marketing will not have an
assigned campaign wave code. Since the Communications Server sends emails to Siebel Marketing campaigns by wave,
these new campaign members will not be included. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-69QPFB)
Attempting to copy an Order for a Response
In the All Responses - Orders View, copying an Order record produces an error. Use the New button or command and select
the Order from the pick applet. (12-8XKRGV)

View tab display in Campaign Administration Screen.
If the user’s responsibility allows access to the Campaign Administration Screen, but does not allow access to the Offers
views, the second level navigation in the Campaign Administration screen displays as tabs and not in the Show menu. Make
sure that the Administrator responsibility for the Call Center application includes both the Campaign Administration Views
and the Offers Views. (12-6XGCNR)
Parent Campaign picklist displays only My Campaigns in the Campaign Administration View
In the Campaign Administration View, the Parent Campaign picklist displays campaign records visible on the My Campaigns
view. To access other campaigns in this picklist, the user’s position should first be added to the campaign team for the
desired parent campaign. (12-6Y9GN2)
List Management
List Import will not generate a log file when running in EIM mode
When running in EIM mode, the List Import task will not generate a log file for the task. No file will be created in the Siebel
Server log directory and the Get Log File button in the List Import view will be unavailable. (12-5WQNGL)
List Import skips first record when FirstLogic files expire
List Import may not import the first record of an import file if FirstLogic is performing the match deduplication and the
FirstLogic directory files are within one month of expiring. (12-97MYTF)
List Import Update Mode does not support update of Additional Attribute values
List Import Update Mode does not support the update of Additional Attribute values for prospects during List Import.
Although the List Import Formats view may display a check under the Allow Updates column for the Import Format, the
update will not be performed. (12-6HGM1N)
Field labels in List Import Format applet cannot be modified
The field labels on each column heading in the List Import Format applet of the List Import view cannot be modified to
display a different value to the user. The display names are the Business Component fields and should not be modified. Any
change in the Business Component field name may impact other areas of the application. (12-4E94QE)
Prospects with an invalid DUNS cannot be promoted
If a prospect record contains an invalid DUNS Number, the prospect record will not be promoted. A DUNS number is
considered invalid if it does not match one of the existing values in the D&B tables within the Siebel Application
(S_DNB_ORG). If the DUNS Number field is empty on the prospect record, the promotion will execute without error. (12-
5QJL3M)

Siebel Connector
Siebel Connector may fail to rollback failed transaction>
Siebel Connector (using MQ or MSMQ as transport) may fail to rollback a failed transaction. To avoid this, make sure that
the queue has some global data before starting the S2SMQRcvr or S2SMSMQRcvr server component. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9Z5VAS)

Value Map Definitions
Siebel Connector for Oracle Applications provide a set of value map definitions that were made to map the corresponding
value in Siebel seed data and the Oracle Applications demo database. The definitions are not meant to be allinclusive, as
customers typically define their own ListofValues (LOVs, Siebel) and lookups (Oracle). A missing value map definition
typically manifests itself into improper functioning of data exchange between the two applications.
For example, the priority of the order may disappear if there is no mapping between a certain Siebel LOV and an Oracle
lookup. In other cases, an order may fail to be imported into Oracle Applications altogether. To fix the problem make sure
that all the LOVs in Siebel involved in transactions with Oracle Applications are mapped to their counterparts in Oracle. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-67OUFP, 12-607WN7, 12-6Z0J5Y, 12-4IJ5V6,
12-9H1G06)
Discount Percentage Truncation
Discount definitions accurate to more than two decimal places (for example, 10.2450) are truncated to two decimal places
accuracy in Siebel (10.24). Orders that are submitted with the truncated discount may fail the order interface. Make sure that
all definitions are two decimal places or fewer. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.)
(12-71S7A3)
OE_MSG_PUB.GET() Procedure Hangs in Some Messages
This is a bug in the ProcessOrder API of Oracle Applications 11i. The Oracle bug tracking number is 1722670. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-4OVVTC)
Improper Customer Import Behavior in Oracle Applications 10.7
Oracle Customer Import picks up records for Orgs other than those matching its Responsibility’s Org. Concurrent Program
customer import jobs should be set up accordingly to avoid this problem. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-5QOGUG)
Contacts Created in Oracle Applications are not Imported into Siebel
No alert is displayed when bringing newly created contacts from Oracle Applications into Siebel applications in the
connector’s integration flow definitions. This issue may be corrected in the field by adding an alert for the contact table in
Oracle Applications (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5X2R9F)

Integration with More Than a Single Oracle Applications Instance

Mixed Integration with both Oracle Applications and SAP R/3
Siebel Connector for Oracle Applications currently does not support integrating multiple instances of Oracle Applications
with a single instance of Siebel 7, or one or more instances of Oracle Applications and SAP R/3 with a single instance of
Siebel 7, if these multiple instances of the ERP applications share the same data objects. This is because each synchronized
data objects uses an integration id field to maintain cross reference information, and the field cannot hold the cross
referencing information for more than one instance of an ERP application integrated with Siebel. This limitation is common
to the Siebel Connector for Oracle Applications, and Siebel Connector for SAP R/3. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-9SLB88)
Siebel Connector for PeopleSoft

Synchronization of Integration Object fails if the data source is changed
If you use the database wizard to define an integration object, and the data source definition for that object is changed later on
(for example, the database is moved to a different machine), synchronization of integration fails. This is because the wizard
can no longer detect the data source automatically. (Not applicable to Base MME or FINS MME.) (12-68YWM0)

State code mismatch between Siebel and SAP for Account inbound/outbound
This is only applicable for the Japanese locale.
• Siebel
The state/region code of Siebel applications is maintained in the List of Values. To view and maintain state/region List Of
values, go to Application Administration then select List Of Values.
Menu Path:
View > Site Map > Application Administration > List Of Values
Query for STATE_ABBREV
The state/region mapping conversion between Siebel applications and SAP is maintained in Back Office Region EAI Value
Maps. To view and maintain Back Office Region, go to Integration Administration then select EAI Value Maps.
Menu Path:
View > Site Map > Integration Administration > EAI Value Maps
Query for Back Office Region
• SAP

The state/region in SAP is maintained as part of configuration under General settings section. To view state and region in
SAP (per country), go to Insert Region Option.
Menu Path:
Tools –> Accelerated SAP -> Customizing – Edit Project, the select/click SAP Reference IMG button
Expand General Settings -> Set Countries and select/click on Insert region options
Or
Use transaction code: OVK2
• Maintaining the Back Office Region
Be sure to maintain the Back Office Region in pair, one for Siebel Inbound and one for Siebel Outbound. The Language
Independent Code/Value is mapped against Siebel Value column in the Back Office Region, SAP’s Country and Region code
is mapped against External System column in the Back Office Region. The External System column format should be
Country Code _ (underscore), then Region Code. Example, for Country US and region/state CA (California), the format is
US_CA. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-8YLK03)
Order submission in nonEnglish environment
The order submission does not work out-of-the-box for the nonEnglish environment. To correct this problem, follow the
instructions given below:
1. Go to Siebel Workflow Administration > Workflow Process.
2. Search for Order - Create SAP 4x Order(SAP) Workflow.
3. Revise it.
4. Go to Process Designer and double click on the Update Integration Status step.
5. This will take you to Siebel Operations step. Go to the Second Applet and select the Back Office Process Statusfield,
change Type to Expression and put LookupValue(EAI_ORDER_SYNC_STATUS,Creating in Back Office) in the
value column.
6. Activate the Workflow.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9W7R1Z)
Importing an Account’s Orders from R/3
The Import button in the Account/Back Office Order History view overrides the Siebel Order Number value with the SAP
Order number, whether or not the order originated from SAP R/3. To rectify this problem, the mapping business service
associated with this button may be modified to prevent imports on existing orders. In order to avoid this scenario, the maps
executed should be modified to make sure that the map is not executed if the Integration ID field for the account in Siebel is
null or equal to the RowID. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-1F8RM3)

Single Contact Synchronization
A single contact associated with a Siebel Account/SAP customer when deleted from the source system is not automatically
deleted from the target system. The work around is to manually delete the contact in the target system. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-7IX4OZ)
BAPI Adapter
The BAPI adapter may crash if external sequence is not populated in the IntComp field definition for BAPI Integration
objects. The work around is to re-create the BAPI integration object using the Integration Object Wizard. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-8AZB1Z)
Siebel CTI
Copying Communications Drivers and Profiles
The copied View/Site Map / Communications Administration / Communications Drivers and Profiles should be saved by
stepping off the copied record prior to modifying the associated Profile Parameter Overrides. (12-GP0Y9O, 12-GYQDGN)
Transferring data with voice calls
When a voice call is transferred, the receiving agent may not have visibility to the view and the data is not transferred with
the voice call. The voice call is transferred successfully. (12-BB1JL6)
Multiple CTI-enabled simultaneous sessions
Multiple Siebel CTI-enabled sessions logged on with the same user login are not supported. (12-9VBMFN)
Initiating and transferring calls
A pop-up message window may appear when calls are made to or transferred to another agent who does not have access to
the screen or its contents. Click OK to continue. (12-5JZ8NI)
Creating multiple telesets with same extensions
The ability to create multiple telesets with the same extensions is not supported. (12-79XMEM)

Upgrading teleset information
When the teleset data is upgraded from Siebel 6.x to Siebel 7, the teleset names are concatenated with a plus sign (+)
followed by its database row id. This was intended to prevent duplicate teleset names in Siebel 7. Review the resulting
teleset names and their associated agents and extensions to resolve duplicate records. A script may then be developed to
delete the plus sign (+)and row id from the teleset name. The upgraded teleset names may be used asis if the teleset names are
acceptable. The Siebel 7 table name is: S_CM_TELESET and the column name is NAME. (12-6SF5YC)
Siebel CTI Connect

NOTE: In Base MME and FINS MME, Siebel CTI Connect is included in Siebel CTI Complete,
MidMarket Edition.
Coordinate Reason Codes with telephony switch
The following parameter changes are required to coordinate reason codes with the telephony switch: Change the
Param.Reason command data parameters for the NotReadyWithPopup command data from [Value] to [Name]. (12-
9WXHPS)
Disable automatic logout from the ACD
Administrators may choose to disable automatically logging out of the switch ACD when agents exit their Siebel sessionby
adding the Service:AutoLogout parameter with value of FALSE. When this parameter is set to FALSE, agents will need log
out of the ACD with the physical teleset. When is parameter is set to TRUE, agents are logged out of the switch ACD as
well as the Siebel application. (12-9O41AO)
Communications event response not supported
The InvokeMethodIfNoData2 event response is not supported. (12-6SF5Y8)
Reception elapsed time
The Elapsed Time displayed is the total time of the call starting from the first ring. (12-6XRSG9)
Exporting Communication Server configurations
The default file extension is .def.def.txt when exporting a configuration from the Communications Administration. When the
export has finished, rename the extension to .def. (12-6REYV0)

Siebel Data Quality Matching

Incorrect library name halts batch deduplication on AIX and Solaris platforms
For AIX and Solaris platforms, a batch deduplication task will not be able to initialize the Data Matching Service due to a
reference to an incorrect library file name. To fix, apply the following statement from the command line to change the library
name in the directory for each language (ENU, DEU,and so on.). For example, in the command line, Goto
$siebel_root/lib/enu, rename it as follows, n3sgsb.so to libn3sgsb.so. If you are using different language than ENU, rename
the library file for the appropriate directory. (Not applicable to Siebel CRM or Base MME.) (12-BAASPA)

Using CTRL-keys in Application Sharing
When using Application Sharing, customers will not be able to use CTRL key functions. For example, in Microsoft Word,
Application Sharing users will not be able to use CTRL-C to copy or CTRL-V to paste. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-65NE10)
Viewing Recorded Sessions
When you view a recorded session that is less than 30 seconds long, you can play the recorded session only once, and the
slide bars will not work since the sessions are handled in 30-second intervals. To replay the recorded session, exit the viewer
and click on the projector icon again. To avoid errors when users try to view a recorded session, Siebel Systems recommends
that customers use a short Breakout Room name (fewer than 8 characters) and a short Session Name (fewer than 10
characters) when setting up the sessions. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
9MOUZZ)
Follow-me Browsing on Macintosh
If you are joining a session using HTML Viewer on a Mac 9.0 OS, when the presenter initiates a Follow-me browsing
session, you will be disconnected from the session. If you are disconnected, join again, or alternatively, join from a
Microsoft Windows machine. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-719HZ7)
Pop-up windows in Follow-me Browsing mode
In Follow-me browsing mode, if the leader goes to a Web site that has a pop-up window, the attendees may see only the
content for the pop-up window in their browsers. If this happens, the attendees may be able to go to the right page by
clicking the Back button on their browsers. It is also likely that they will catch up as soon as you navigate to the next page.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-8KF32Q)
Turn Audio On Control
The audio icons may be grayed out when the moderator turns them on when the attendee has set Options > Preferences >
General Controls, and when the receiving moderator messages... as Always accept and execute,. To fix this problem set the
option to Prompt before executing. At the first prompt, the attendee can select Accept All to have the same behavior as
Always accept and execute. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-8KF330)

Chat History
In Distance Learning sessions, the history of the chat sessions is automatically saved on the server as an attachment on the
Attachments page. The user can delete the chat history with a special password = Admin. (Siebel Systems recommends that
users not delete the chat history while the session is in progress.) However, even though the chat history attachment has been
deleted, the Conference Center will still display the Attachments icon. When you click on the Attachments icon, the
Attachments Detail page will no longer display the chat history attachment. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-8MUPHX)
Providing Support Through Firewalls
The client software will try to use an HTTP Gateway connection to the server. If you receive a prompt that the connection
was unsuccessful, you may choose to join the session using the HTML Viewer. The software will not automatically try to
connect using the HTML Viewer. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6Q1J95)
Siebel Dun & Bradstreet Integration Solution

Multiple Account Promotion fails
This problem can be solved by modifying configuration with Siebel Tools.

1. Select BusObj "DNB Account"
2. Modify BusObj BusComp "Contact", change link value to blank.
(12-FDCXCV)
Siebel Dun & Bradstreet on EBCDIC code pages
The Siebel Dun & Bradstreet server components are not supported on DB2/390 databases with EBCDIC code pages due to
difference in sort sequence. Siebel Dun & Bradstreet is supported only on databases with ASCII code pages. (Not applicable
to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B8IG6R)
Running Dun & Bradstreet Components against a DB2 for iSeries Database
You must change the ODBC data source settings to use a sort sequence based on QSYS/QASCII prior to running any Dun &
Bradstreet components against a DB2 for iSeries database. To do this, follow these steps:
1. Open the ODBC Data Source Administrator.
2. Switch to the System DSN tab, and select the Siebel Server’s data source from the list, typically named
SiebSrvr_EnterpriseName, and click Configure.
3. Switch to the Language Tab.
4. Change the Sort Type field to sort based on specified table.
5. Enter the following in the Sort Library/Table Name field: QSYS/QASCII

6. Click OK.
After running the Dun & Bradstreet components, you must revert the ODBC data source back to its original settings. To do
this, perform steps 1 through 3 above followed by these steps:
7. Change the Sort Type field to sort based on HEX values.
8. Click OK. (12-ASW4Y3)
Navigation from Dun & Bradstreet Reports
In order to use the Siebel Navigational Buttons after a user has viewed a report from Dun & Bradstreet, the following steps
must be taken:
1. Go to Integration Admin > Host Administration

a. Find and Edit the record for www.dnb.com / Reports Server.
b. Remove the space from the Virtual Name column, making it ReportServer.
a. Save the record.
2. Go to Integration Admin > Symbolic URL Admin

a. Find and Edit the record for where Name = DNBReport
b. Change the URL from https://www.dnb.com/scripts/ProductRetriever to
https://ReportServer/scripts/ProductRetriever
c. Select www.dnb.com into the Host Name column .
d. Save the record.
3. Go to Integration Admin > Fixup Admin

a. Find and Edit the record for where Name = DNBReport
b. Change the Link Target column to be _blank (underscore blank)
c. Save the record. (12-9SFT2T)
Upgrading from Siebel 99.5 to Siebel 7
The data model has changed between Siebel 99.5 and Siebel7. In Version 99.5, all the Dun and Bradstreet data is stored in a
single table, even items that have a one to many relationship with accounts, for example there were separate fields in the
S_DNB_ORG table for Contact1, Contact2,and so on. In Siebel7, this type of information is stored in separate tables -
S_DNB_SIC - with a reference to the main S_DNB_ORG table through the DUNS number. The customer will need to copy
their data to the appropriate new tables before upgrading in order to avoid data loss in the Contact and SIC fields. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B7QY3A)


Prebuilt Distance Learning Sessions are not activated
The two sessions that come prebuilt with Siebel Distance Learning need to be activated. Use the following procedure after
installation the server to activate the sessions:
1. Rename the files that are associated with the two pre-built sessions:
The files are Sample Session.ptk and Getting Started.ptk and are located in the directory '<INSTALL_DIR>/PictureTalk/ptk-
apps/Meetings/Meetings'. Typically, the install directory is 'C:\DistanceLrn'. Replace the space with a underscore,for example
from Getting Started.ptk to Getting_Started.ptk.
2. Edit one line in the each of the above files :
Open the "Sample_Session.ptk" file in Notepad. Change the line that says "meeting=Sample Session" to
"meeting=Sample_Session". Now save the file. Do the same for the "Getting_Started.ptk" file; change the line
"meeting=Getting Started" to "meeting=Getting_Started". (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-BB1BFR)
HelpDesk
Area and Subarea list of values from the administrator screen do not match the new request
When creating a list of values to populate the area and subarea fields for a service request, you must create duplicate entries
for each value. Under the Parent License field of the value, one of the values should be marked as Internal while the duplicate
should be marked for External. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6WHM3L)
News Distribution
Creating Recommended Links and Web Clips
When creating recommended links, avoid choosing Window for the Web Display field of the Literature form in Literature
Administration. This precaution will prevent users from experiencing a Page Has Expired warning when they attempt to click
on the browser Back button after drilling down on the links. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-5UU5R6)
Performance Management
Page Item Administration for Corporate Objective View
The ERM Corporate Objective View has been created for posting corporate objectives. For the current release, several Page
Item administration controls that determine Page Item visibility on the ERM Corporate Objectives View are not operational.
These controls include Release Date, Expiration Date, and Status. In addition, the Sequence control on the Page Section
applet in the Page Layout screen is not operational for the ERM Corporate Objectives View.
The Page Item containing the corporate objectives should only be added to the ERM Corporate Objectives View Page
Section at the point when the page item is to become visible. Conversely, the Page Item containing the corporate objectives

should be removed from the ERM Corporate Objectives View Page Section at the point when the page item should no longer
be visible.
To display more than one Page Item on the ERM Corporate Objectives View in a specific order, add each Page Item to the
Page Section in the order desired, ignoring the Sequence field. In other words, the first Page Item added to the Page Section
will always appear on top. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9S98KZ)
Changing the position after starting Objective/Review generates multiple records for the same period
If an employee’s primary position is changed midperiod, the Administrator should first delete the existing review record for
that employee and period. The employee should complete a new review after the position has been changed. Problems arise
when two different review records exist for a given period for a given employee. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-8TWKQV)
Single Sign On
ReplaceResponseWith302 is not available as a COMMAND for Symbolic URL's configured to access other Siebel servers.
Instead, use ReplaceResponseWithForm in these instances. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-AUL1KO)
Training
Submitting Tests with DB2 390 Configuration
When tests are used within a DB2 390 configuration, the tests cannot be submitted due to an issue introduced by the
MaxCursorSize and MaxPrefetchSize Setting. Standard DSMaxCursorSize and DSPreFetchSize values are set to 48 by
default, and these values need to be changed to -1. If operating using TW Siebel, then change MaxCursorSize and
PrefetchSize both to -1. If operating using a zero foot-print client, then go to Server Administration, change these parameters
to -1 under ServerDataSrc, then reboot the server. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-BAYYMU)
De-activating Course Test Status
Tests are currently assigned a Status of Active, Inactive or Development. When setting up tests for a course, administrators
are not able to change the test status; therefore, tests can be associated to courses even if the Status is Inactive or
Development. To deactivate a test, disassociate the test from related courses by deleting the Associated Courses in the Tests
list applet. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-8EWUKR)
Courses do not become inactive automatically when expiration date passes
To deactivate a course whose expiration date has passed, Training Administrators should navigate to the Course
Administration List view, run a query for courses whose expiration date is earlier than today’s date and change the status to
Inactive. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6FJXTR)


Objectives
In the Objectives view, the Activity Type drilldown in the Action Plan applet needs to be changed in order to retrieve the
correct record. Specifically, the drilldown definition needs to be reconfigured using the following steps:
1. Click on the Applets Object in the Object Explorer in Siebel Tools.
2. Search for the Activity List Applet (ESP) applet.
3. Go to the Applets->Drilldown object on the Object Explorer.
4. Change the drilldown object named ActTp with the following parameters:
• Change Source Field from typeto Id
• Change Destination Field from ‘type” to “Id”
5. Compile the SRF to see changes.
The drilldown should work properly after this configuration. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-9LS6WZ)
Siebel FirstLogic Connector

Incorrect product name in Siebel Data Quality Documentation
The product name Siebel FirstLogic Connector that appears in the Siebel Data Quality Administration Guide is incorrect. The
correct name of this product is Siebel Connector for FirstLogic Libraries. (12-91IHBJ)
Siebel Forecasting
Opportunity Revenue Script does not populate automatically
If an Opportunity Sales Team member is removed from the Account Team then the Revenue Script is not usable on the
Revenue View. If this occurs then the users should add themselves back to the Account Team. (Not applicable to Base MME
or FINS MME.) (12-B65B42)
Export in Revenue or Forecast Spreadsheet view exports only one row at a time
If users wish to export multiple rows, then it is recommended that users switch from the spreadsheet to the List Views and
run export. If you would like to disable Export in the spreadsheet applets, create a new record in Applet > Method Menu
Item, with the following attributes:
Command: Export (SWE)
Menu Text: Export

Position: 40
Suppress Menu Item: TRUE
The affected applets in 7.0.4 are:
Account Revenue Schedule List Applet DC
Agreement Revenue Schedule List Applet DC
Opportunity Revenue Schedule List Applet DC
Forecast 2000 -- Forecast Item List Applet DC (ExecWS)
Forecast 2000 -- Forecast Summary List Applet DC (12-9XTAFF)
Revenue Script in select revenue views does is not enabled
In the following Screens, Campaign, Channel Partner, Contact, Product, Project, Quote, the Revenue Script from the
Revenues View is not enabled and will result in a system failure if invoked. To fix this, we recommend to:
1. Find all Business Objects with revenue as a component and not revenue DynCol as a component. Opportunity and
Account have both components and thus should not be touched.
2. For those Business Objects with revenue only as a component, identify the link to the Revenue BusComp in that
BusObj, copy the Link and leave all the copied attributes the same except for the Child Business Component.
Change the Child BusComp to revenue DynCol, as noted below.
Example: The Quote business object child Revenue component has a link Quote/Revenue. In the Link section, copy that link,
and add new attribute:
Name: Quote/Revenue DynCol
Parent BusComp: Quote
Child BusComp: Revenue DynCol
Source Field: Quote Number
Destination Field: Quote Number
Cascade Delete: None
3. Next, for the Business Object, create a new child Business Object Component with the below attributes:
BusComp: Revenue DynCol
Link: (Name of Copied link in step 2) (12-B8C94G)
Potential data confusion if user deletes and adds back an adjusted forecast detail
If a customer creates a forecast detail that is then adjusted by their manager and then that customer deletes and adds back that
same detail record, two records will appear in the manager’s forecast-- the original adjusted detail and the new unadjusted
detail. It is recommended that users do not delete records and add them back without proper communication with their

managers. Also, best practice is that subordinates submit forecasts prior to the manager making adjustments. (Not applicable
to Base MME or FINS MME.) (12-AUOK9N)
Users should not export revenue data having selected the Visible Columns choice, as this may result in an import
error
When users select the Visible Columnsonly selection when exporting data and then attempt to import that data back into the
Revenues Table they will encounter an error. The Export data selection of Visible columns may not map to the recommended
Import Default Predefined Mapping and thus will create an error. Users should instead export All Columns and import those
same All Columns when they wish to return data, as these map the Default Predefined Mapping. (Not applicable to Base
MME or FINS MME.) (12-9SGJ9N)
When Importing data into Revenues, a data field left blank will be left unchanged upon successful import
Data fields left blank will be interpreted as a no change in an import. Thus, if users want the blank records to be imported as
0 values then they should replace the blanks with 0’s. (Not applicable to Base MME or FINS MME.) (12-9SGJ9T)
Revenues disappear for positions with no primary employee record
Revenue records disappear if the position that they are related to has no primary employee record.. To avoid this issue,
customers can assign a new employee to that position, or can retain the old employee record, with some inactive designation
in the employee table. (Not applicable to Base MME or FINS MME.) (12-9B0AER)
Cannot add a Forecast Detail item if it is deleted and added back again two times
Users cannot delete a Forecast Detail item, add it back, delete it again, and then try to add it back again, all from the same
Forecast. If the user does delete the Forecast Detail item twice and wishes to re add the Forecast Detail, the user can delete
and re-create the Forecast, which will pull in all Forecast Details. If the Forecast Detail belongs to a subordinate, the user can
also simply delete the Subordinates Forecast from the Subordinate View and re-add it. (Not applicable to Base MME or FINS
MME.) (12-95XH5U)
New Spreadsheet Scrolling Buttons
Four new Scrolling Buttons have been added to the Forecast and Revenues Screens in the upper right corner of the
spreadsheet applet. These new scrolling buttons enhance spreadsheet navigation and allow users to view records with
multiple columns. There are two buttons with double arrows, one that points left and moves the columns backward, another
that points right and moves the columns forward. There are also two buttons with single arrows that point left and right.
These buttons control what date column, or dynamic columns, are viewed. The two double-arrow buttons allow the user to
move the date columns ahead a set number of columns.
The static columns found on the spreadsheet view, such as Opportunity, Product, Currency, and others found in the Columns
Displayed, are fixed and do not move when the date columns are scrolled. Likewise, persistent columns, such as the Total
column and any new columns that result from the Add Column function, will be retained as the user scrolls. Newly added
date columns persist until the next time the spreadsheet is refreshed, when they become dynamic like the other date columns.
Administrators can enable or disable the Scrolling Buttons and set the Set Size, which controls the Number of dynamic
columns to scroll at a time, and the Window Size, which controls the Number of dynamic columns to show on one screen.
Window Size, as defined, does not include static or persistent columns.
To configure the Scrolling Buttons, Administrators can set the correct values in Tools in the Applet > User Properties:
DC Scrolling: Enabled

DC Scrolling: Set Size (Default = 6)
DC Scrolling: Window Size (Default = 6)
Make the Set Size and the Window Size equal in order to make the functionality predictable to the user. If the Set Size is
greater than the Window Size, some records that the user might expect to see will not be displayed by default. For example,
if the SetSize = 8 and the WindowSize = 6, using the scroll One Page Rightbutton would cause the window to not display the
first two columns in the SetSize. The user would have to use scroll One Column Left button to see those columns. Likewise,
if the Set Size is less than the WindowSize, the window will display more records than the user might expect. For example, if
SetSize = 4, WindowSize = 6, using the scroll One Page Right button would display the next four records to be returned as
well as the last two columns of the existing window.
To configure the Scrolling Buttons to jump to the end or the beginning of the spreadsheet, the Administrator can set the
SetSize to a large enough number, for example, SetSize = 1000, that the scrolling button would go to the end (this assumes
that there are fewer than 1000 columns). The user would then use Scroll One Column Left to view earlier columns.
To inactivate the Scrolling Buttons, administrators should:
1. Find the Applets listed below:
Forecast 2000
Forecast Summary List Applet DC
Forecast 2000
Forecast Item List Applet DC (ExecWS)
Account Revenue Schedule List Applet DC
Opportunity Revenue Schedule List Applet DC
2. For each applet, inactivate these Applet > User Properties:
DC Scrolling: Enabled
DC Scrolling: Set Size
DC Scrolling: Window Size
3. For each applet, inactivate these Applet > Controls
GotoNextHorColumn
GotoNextHorSet
GotoPrevHorColumn
GotoPrevHorSet
4. For each applet, inactivate the corresponding Applet > Web Template > Web Template items.
Opportunity Revenue Schedule List Applet DC:
• GotoNextHorColumn (item identifier 150)
• GotoNextSet (item identifier 151)

• GotoPrevHorColumn (item identifier 164)
• GotoPrevSet (item identifier 163)
Account Revenue Schedule List Applet DC:
Forecast 2000 -- Forecast Summary List Applet DC:
Forecast 2000 -- Forecast Item List Applet DC (ExecWS)
(Not applicable to Base MME or FINS MME.) (12-8VUNWD)
Forecast Details View shows product line items that were deleted before creating Forecast
While it is unlikely that any best practice would include the deletion of an opportunity that included revenue estimates, the
ability to delete an opportunity is standard Siebel functionality. If a user deletes an opportunity, but does not delete the
associated revenues, then those revenues will be maintained, and will be included in the user’s next forecast. Users should
delete all revenues associated with the opportunity before deleting the opportunity if those revenues are not meant to be
forecasted. (Not applicable to Base MME or FINS MME.) (12-5EPYGL)
Revenues in the Opportunity-Revenues View do not show up in the Parent Account
Users will find that if they create an opportunity and assign revenues to it before they define the parent account, then those
revenues will not be associated with the Parent account. If users set the parent account in the opportunity first and then create
the revenues, the revenues will be correctly associated with the parent account. (Not applicable to Base MME or FINS
MME.) (12-6QYI72)
Forecast Creation Error
When creating a forecast a user may experience an error that says. " [1] An error occurred while creating your forecast.
Forecast may not include all revenues or subordinate details. Please check the log file or contact your system administrator

for details... ". To find the source of this problem, administrators should check the forecast log file on their server. These
files are typically located in the areas indicated below:
If the instance is a mobile client (siebel.exe) installation:
xxx: $install/log directory
yyy: siebel.log, or siebel_N.log, if the client has been run N times since the crash occurred. (The names of the logfiles
are incremented by one each run, for example, siebel.log is renamed to siebel_01.log, siebel01.log -> siebel02.log)
If the instance is a Microsoft Windows server:
xxx:$install/siebsrvr/log
yyy: SrvrComponent_ProcessId.log, e.g. SSEObjMgr_50231.log
If the instance is a UNIX server:
xxx: $install/siebsrvr/enterprises/$enterprise_name/$srvr_name/log
yyy: SrvrComponent_TaskId.log, e.g. SSEObjMgr_50231.log
A component can have many tasks running and generating logs. The location of log files is found in the Server
Administration instructions.
In the log file, you will find records like this:
FCSTLOG_EVENT Error 1 2001-10-30 16:16:02 <WW Sales, 10/01/2001, Product Line Manager-
00004456, BGROVES> Error occurred when setting field ‘revenue Class” to value “Backlog”
This error in this sample occurred on October 30th, 2001, when running a WW Sales forecast for a Regional Sales Manager
with the userid of MSTERN. The error occurred because a revenue record that was to be included in the forecast included an
invalid value for the Revenue Class picklist. In this example, the error can be corrected by adjusting the Revenue Class LOV
to include a value called BackLog, or by changing the Revenue Class on the offending record to a choice that is still valid.
(Most likely, in this case, the valid values for the Revenue Class field were changed and the old data was never cleaned up).
Once this issue is corrected, the forecast can be deleted and rerun, or the missing revenue record can be added manually.
(Not applicable to Base MME or FINS MME.) (12-8NCCKV)
Forecast server process must be stopped and restarted after changes to an existing forecast series.
Forecast series definitions are read into memory when forecasts are created. Forecast server processes must be stopped and
restarted before changes to the series will be used in the creation of new forecasts. (Not applicable to Base MME or FINS
MME.) (12-87ECOV)
Queries on the forecast detail view affect summary views
Queries run on the forecast details view will impact the information shown on the forecast summary view. End users may
have to requery in order to see all of the forecast summary records after running a query on the forecast details. (Not
applicable to Base MME or FINS MME.) (12-6LFHZT)
Currency symbols containing a period will cause truncation in forecasting reports
Currency symbols that contain a period symbol (.) will cause truncation of currency amounts in the Forecast Summary and
Forecast Detail reports. To avoid this issue, remove the period symbol (.) from your currency symbols. (Not applicable to
Base MME or FINS MME.) (12-6XI4ZJ)

MS IE 5.5 Busy Cursor Status During Export
For IE 5.5 users, when a request is sent from the Export popup window, before the response is sent back, the cursor will show
a busy status only when placed on the window title bar. (Not applicable to Base MME or FINS MME.) (12-6ASF3E)

Adding Plan Rules
Avoid adding the same Rule to a Plan more than once with nonoverlapping date ranges. This will cause failure for
calculation and copy plan functionality. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
B48AOX)
Cumulative Performance Measures
Revenue is accumulated incorrectly when evaluated against compensation rule with Cumulative Revenue or Cumulative %
Quota as performance measures and multiple Earned statuses (that is, Booked 50% and Billed 50%). (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9Z93NG)
Estimate Compensation
Compensation is not estimated correctly when there is an aggregate rule used as multiplier in any plan. (12-9YC8ZQ)
Compensation is estimated using the calculated value in the Revenue field if the Qty and Price are entered for the product on
an Opportunity in the Estimate Compensation tab. The estimated compensation is calculated correctly using manually entered
value in the Revenue field without Qty and Price value. If the calculated value in the Revenue field is manually overwritten
with the Qty and Price entered, the estimated compensation is not calculated correctly. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-9V0C3H)
Compensation is not estimated correctly when $0.0 is entered in the Revenue field of the Estimate Compensating tab in the
Opportunities screen. Users should leave the Revenue field blank for $0.0 revenue. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-9XG97R)
Groups
Compensation for the group members with different divisional currency compared to the plan currency is converted properly
and shown correctly in the Calculation Summary view, Totals field in the Calculation Details view, and Totals field in the
output views. The compensation is displayed incorrectly in the Plan Rule Payout view, the Calculation Workbook view, and
the form applet of the output views. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
9SAPQN)
Plan Participant
It is recommended that Compensable Positions in the Siebel Application should be end-dated and not deleted if they were
used as Plan Participants. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9SQVK6)
Tracking Views
To set the formatting for the proper Japanese date format, perform the following steps:

1. Open Siebel Tools
2. Go to Business Component, and query for Name=Incentive Compensation Txn Parameter
3. Select field Input Period SDate, and change property type to be DTYPE_DATE
4. Select field Input Period EDate, and change property type to be DTYPE_DATE. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-77WPPV)
Linkages
When two rules are linked, the Calculation field in the Rate table can have only Primary Performance Measure as part of the
formula. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-8VSZXX)
When linking two rules with different participant levels (that is, Group and Individual), the Individual rule must be the
primary rule and the Group can be linked to it. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.)
(12-6YX9HZ)
Adjustment field in Order is not reflected in Transaction
Changes made to the Order line items revenue in the Sales Order view, using the Adjustment field, will not be reflected in the
Transaction Workbook after importing the order. The revenue can be adjusted in the Transaction Workbook using Discount
Price, Discount Amount or Discount %. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
6WSXWI)
Reports
Position and Job Title fields are not shown in the Compensation Groups Report. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-6WVJK6)
Estimate Compensation
The Opportunities list applet in the Estimate Compensation screen shows total compensation from Commission and
nonaggregated rules. To view all compensation from nonaggregated and aggregated rules, go to the Estimate Details view
tab. If the compensation is calculated using only the aggregated rules then the total may be shown as $0. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6R2VR6)
Siebel Marketing
NOTE: There is no Siebel Marketing, for Siebel CRM and for the Siebel MidMarket Edition applications.
However, except where noted, the anomalies in this section are applicable to the Siebel CRM and to the
MidMarket Edition of eCampaigns.
Width field in Marketing Admin -> Output File Layout lower applet not automatically populated
The Width field in Marketing Admin -> Output File Layout lower applet is not automatically filled upon selecting the Type
field. Steps to solve problem:
1. In Siebel Tools object explorer, go to Business Component

2. Query for Business Component Name = “List Columns”

3. Go to Business Component Field
4. Query for Field Name = “Width”
5. Set Predefault Value to 50
6. Compile object.
(12-FCHBLY)
Home Page View (DBM) displays My Programs and Program Timeline applet even the user does not have the
Marketing Manager license key
The eMarketing product includes the home page view (Home Page View (DBM)) from the Marketing Base application,
which includes applets for My Programs and Program Timeline. If the user does have the license for Marketing Manager,
then the Program applets will display but remain empty since the user does not have access to the Programs screen. To
address this problem, remove these applets from the eMarketing home page view through configuration. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6HGM1S)
Marketing Administrator Configuration (DB2/390 only)
The Siebel Marketing Administrator must use a .cfg file which has the value of –1 for both Cursor Close Parameters,
MaxCursorSize and PreFetchSize. Without this setting, certain reports and operations will not be complete. This
recommendation assumes the Siebel Marketing Administrator is attached to the Siebel application usinga Connected Client.
If the Marketing Administrator is attached in a three-tier configuration, such as a Web Client, please refer to guidelines in the
“Configuring Cursor Close” section in the Implementing Siebel Applications on zSeries Guide. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-B47UG3)
Marketing queries and processes require CLOB columns
Due to the 32K limit for intermediate results in DB2/390, certain queries and SQL statements will fail with errors similar to:
SQLError: sqlstate 54010: [IBM][CLI Driver][DB2] SQL0670N The row length of the table exceeded a limit of ""
bytes. (Table space "".) SQLSTATE=54010
The solution is to redefine the LONG VARCHAR column to CLOB in the S_NOTE table. Please review the Release Note on
CLOBs prior to making this change. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
AX8GLN, 12-AV427Z, 12-AI4HCF, 12-AUJ6RA, 12-AO9HIN)
Forward button missing from Filter Detail view
The following issue is only applicable for the Japanese locale. The applet Filter Form Applet in Filters (DBM) project is
missing a control mapping for next record set and it requires following changes:
1. Edit web template and select Edit mode.
2. Map missing control”NextRecSet” and check all the properties are set properly.
3. Properties are
Caption: Next

HTML Bitmap: RECNAV_NEXT_ON
HTML Disabled Bitmap: RECNAV_NEXT_OFF
HTML Type: RecNavNxt
HTML Display Mode: EncodeData
Method Invoked: GotoNextSet
Name: GotoNextSet
Visible: TRUE (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
83IICR)
Marketing Analysis Categories Applet on the Marketing Homepage Not Functional
The Marketing Analysis Categories applet on the Siebel Marketing Homepage contains functionality no longer supported in
Siebel 7.0.3. This applet will not function. To eliminate any user confusion, disable the applet in Siebel Tools. The applet
name in Siebel Tools is Marketing Analysis Predefined Categories List Applet – Homepage. (Not applicable to Siebel CRM
or FINS CRM or Base MME or FINS MME.) (12-A441MD)
Segments
Creating Visual Segment
Visual Segmentation is not supported for criteria having one of the following:
NOT operator
Date Fields
Functions or formulae
LIKE operator
Prompted filters from Siebel Analytics
More than 1000 lines in the criteria.
To setup Visual Segmentation, please perform the following steps using the SIF file provided in the installation media. The
SIF files contain the recommended changes for Visual Segmentation and Prospects / Contacts changes for Release 7.0.4.
Click the apply Button once you have applied the SIF file for schema changes
marketing.sif: Visual Segmentation & Prospects vs. Contacts repository changes.
1. Connect Tools to your database.
2. Lock projects SME Integration and Server(DD) and New Table.
3. Import marketing.sif archives choosing the Merge option.
4. Compile the new srf and copy it over to the environment.

Marketing Person:
Schema:
Under Siebel Objects, go to Table > search and select S_DD_USER_KEY table > Click on Apply button > specify the
Server database connect information in the dialog box. This will apply the schema changes to the server database
Seed Data:
Navigate to Sitemap > Application Administration – List of Values and add the following two LOVs:
Type Display Value Language Language Parent LIC Active Translate

Independent Name
Code
EAI_USER_KEY_MAP Marketing Marketing English- Y Y

Person Person American
EAI_USER_KEY_MAP Contact Key Contact Key English- Marketing Y Y

American Person
Visual Segmentation:
Repository:
In Siebel Tools, increase the Bus Comp Field’s Text Length property to what is specified in the New Length for the
following BCs:
Project Name Business Component Field Name Old Length New Length
Name
Attributes (DBM) Attribute Families Name 46 146
Attributes (DBM) Attribute Levels Name 50 150
Attributes (DBM) Hierarchical Attributes Name 100 150
Attribute Structure Hierarchy (Fields) Hierarchical Attribute 50 150

(DBM) Name
Attribute Structure Hierarchy (Tree) Hierarchical Attribute 50 150

(DBM) Name
Attribute Structure Hierarchy Search Hierarchical Attribute 50 150

(DBM) (Fields) Name
Attribute Structure Hierarchy Search (Tree) Hierarchical Attribute 50 150

(DBM) Name
Data Dictionary (DBM) DD Field Reference Name 50 150
Data Dictionary (DBM) Fields One Level Reference Name 50 150
Data Dictionary DD Table Reference Name 50 150

(DBM)
Filters (DBM) Attribute Level Look Name 50 150

Up

Program Container Extract Name 50 150
Schema:
Under Siebel Objects, go to Table -> search and select S_DD_FIELD table > Click on Apply button > specify the Server
database connect information in the dialog box. This will apply the schema changes to the server database. Repeat the
same step for the following additional tables:
S_DD_ATTRFAM
S_DD_ATTRFAMLVL
S_DD_HIERATR
S_DD_DATA_OBJ
S_DD_EXTRACT
S_DD_EXTRACT_CL
Note: This will increase the length of the NAME column for the following tables to 150
S_DD_FIELD
S_DD_ATTRFAM
S_DD_ATTRFAMLVL
S_DD_HIERATR
S_DD_DATA_OBJ
S_DD_EXTRACT
And will increase the DB_TBL_NAME column for the S_DD_EXTRACT_CL table to 150.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AUEQER)
Siebel Marketing Base / Campaigns
List Import status message will not update when using EIM Mode for List Import
When starting List Import a task using EIM Mode, the List Import Results field in the List Mgmt Lists Import Form Applet
(View; List Mgmt Import View) will be displayed as 'Sent EIM Request' at all times. The status field text will not change
after the import is completed or encounters an error.test. (12-DRS5DF)
Making sure of complete and proper execution of email campaigns
When sending out large number of emails using the Communication Server’s multithreading functionality make sure that the
limitations of the SMTP/POP3 server are accommodated. The marketing server splits each wave, internally into a number of
simultaneous subwaves to send out messages in parallel. Each of these subwaves results in creation of an individual
communication server task. Each communication server task makes a unique connection into the SMTP/POP3 server. The

number of these connections should not exceed the maximum number of simultaneous connections allowable by the
SMTP/POP3 server. To make sure the number of connections does not exceed the maximum number of simultaneous
connections, please perform the following steps:
1. Go to the View > Site Map > Server Administration > Components.
2. Scroll to the Communications Outbound Manager component.
3. Click on the Component Parameters Tab.
4. Scroll to the Maximum Tasks parameter.
Set the value of this parameter to a value that is less than the maximum number of simultaneous connections that are
allowable by the SMTP/POP3 server. If you have more than one communication server that will be used for sending out
emails through one particular SMTP/POP3 server, make sure that the TOTAL number of communication tasks does not
exceed the maximum allowable simultaneous connections by the SMTP/POP3 server. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-79S3XX)
Campaign Hyperlinks on selected Contact, Prospect and Response Views
Campaign hyperlinks on the following views support drilldowns to the Campaign (DBM) Offers View on the Campaign
Management Screen.
• Contact Campaign View
• Contact Response View
• Prospect Campaign View
• Prospect Responses View
• Response View (SME)
• Response Detail View (SME)
• Response Detail View (SME) - More Info
Users of the Siebel Marketing Base Application that are not also users of Siebel Marketing Manager will probably want these
links reconfigured to drill down to the Campaign Administration List view on the Campaign Administration Screen. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6HGM1E)
No Activity Record Created for Prospects
When the Create Activity option is selected on the Email Offer view, an activity record is created for each recipient upon
campaign execution. This feature applies only to contact records. Since the data model does not support the creation of
Activity records for Prospects, Siebel Marketing and Siebel eCampaigns, for Siebel CRM and Siebel MidMarket Edition will
not generate Activity records for Prospects that are included in the email campaign.( 12-6HP5AD)
Making sure of complete and proper execution of email campaigns
When sending out a large number of emails using the Communication Server’s multithreading functionality, be sure to
observe the limitations of the SMTP/POP3 server. The Marketing Server splits each wave internally into a number of
simultaneous subwaves, to send out messages in parallel. Each of these subwaves results in the creation of an individual
Communication Server task. Each Communication Server task makes a unique connection to the SMTP/POP3 server. The

number of these connections should not exceed the maximum number of simultaneous connections allowable by the
SMTP/POP3 server. To make sure this:
1. Go to the View > Site Map > Server Administration > Components.
2. Scroll to the Communications Outbound Manager component.
3. Click the Component Parameters Tab.
4. Scroll to the Maximum Tasks parameter.
Set the value of this parameter to a value that is less than the maximum number of simultaneous connections that are
allowable by the SMTP/POP3 server. If you have more than one Communication Server that will be used for sending out
emails through one particular SMTP/POP3 server, make sure that the TOTAL number of communication tasks does not
exceed the maximum allowable simultaneous connections by the SMTP/POP3 server. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-79S3XX)
Using Microsoft Word to Embed Images in HTML Email
Images that are embedded in an HTML email template using Microsoft Word 2000 may not display properly when sent to
recipients using Siebel Marketing or Siebel eCampaigns for Siebel CRM and Siebel MidMarket Edition. When embedding
an image in an HTML email be sure to provide a URL reference to the image. The following is an example of a reference to
an image in HTML:
<img src="http://www.siebel.com/images/image.gif">. (12-1AN8WY)
Siebel Marketing Manager
Disable New, Copy, and Delete on Campaign applet in Program Explorer
In the Program Explorer view under the Programs screen, the New Record, Edit Record, Copy Record, and Delete Record
commands are displayed on the applet level menu, but will not perform any function.
To disable these commands for the Campaigns node of the Program Explorer tree perform the following steps:
1. Make a copy of Campaign (DBM) List Applet and rename it to Campaign (DBM) List Applet (Explorer)
2. Set No Insert, No Delete, No Update and No Merge to TRUE on Campaign (DBM) List Applet (Explorer)
3. Go to Program Tree Applet (DBM) >Tree Nodes and change the applet for the Campaigns node from Campaign
(DBM) List Applet to Campaign (DBM) List Applet (Explorer) (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-BAI8M5)
Creating Visual Segments
Visual Segmentation is not supported on a pure Unix platform. For this to work, the Siebel Marketing Server Component,
Siebel Workflow Manager, and the Siebel Communication server manager should be running on the supported Windows
platform. The remaining components of the Siebel eBusiness application may be running on the supported Unix platforms
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B3IF3E)

Web components of Siebel eBusiness Apps and Siebel Analytics should be on the same machine
The Siebel Web Server extension and the Web component of the Siebel Analytics server should be deployed on the same
machine for Visual Segmentation. Please refer to detailed documentation in the Siebel Marketing Guide. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AV6EXU)
Creating Visual Segments
When using Visual segmentation with multiple criterion that refer to the same table, which may contain multiple records for
the same customer, it is necessary to build attribute hierarchies in Siebel Marketing and use it in the Siebel Marketing
segment criteria (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-BC9LEA)
Clicking on the Create Segmenthyperlink while using Visual Segments always takes users to the All Segments view in
Marketing. If the user does not have access to this view, this would result in an error. (12-BC9LEZ)
Deleting a completed campaign occurrence from schedule can result in incorrect behavior
When the user deletes a completed occurrence on the Program Schedule view using CTRL+D or the Delete Record command
from the applet level menu, this may result in incorrect delete behavior. To avoid this issue, use the Delete This One or
Delete All commands from the applet level menu instead. To disable the applet level menu selection on the schedule applet,
perform the following repository fix:
1. Goto Siebel Tools > Applets
2. Select Program Calendar Detail Applet
3. Set No Delete property to TtRUE for this applet. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-AFHZ3V)
Analytic Adapter Target Group Names
Analytic Adapter target group names must be unique. If a user assigns a name that is already in use, the server will purge the
preexisting target group and load the new data. No warning message is provided, so users should assign target groups names
with care. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-699E0M)
Handling of Lists in Multistage Marketing Programs
If the user associates a list to Stage 1 of a marketing program flow, the members of that list are not available to be included in
following stages. This restriction is caused by the lack of an association between the Contact ID and the S_DD_USER_KEY
table. To make List Contacts and Prospects available for multiple stages, consider mapping the list management tables
(S_CALL_LST and S_CALL_LST_CON) under External Data Mapping. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-5MAZDZ)
Siebel Marketing Server
Simultaneous data retrievals cause deadlock error on OS/390
When Siebel Marketing Server is accessing a database running on OS/390, simultaneous data retrieval tasks can cause a
deadlock error, resulting in some failed retrieval tasks. To avoid this issue, schedule the data retrieval tasks with an interval
at least 2-3 seconds apart. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B791UN)

Snapshot builds fail when using a numeric measure or attribute in an inclusion criteria within a filter
The snapshot build will fail during the extraction step (reextract) when a numeric measure, field or attribute hierarchy has
been used as part of an inclusion criteria in the associated filter. To address the issue:
1. Go to Marketing Administration > Show: External Data Mapping > Tables
2. Query for the table from which the measure or attribute is mapped
3. Change the database field type for the field(s) used by the measure or attribute to Character
4. For Fields or Attributes, perform data retrieval again after the data type change is made (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-BAHQRZ) 4
Stopping the Siebel Service
Stopping the Siebel service does not terminate and remove all processes from the server. Should a user wish to discontinue
server processing, individual tasks may be stopped using Task Manager. (12-2IBO2J)
Sending Faxes Requires Configuration of the Fax Address Format
When sending fax packages, CommMgr retrieves the fax addresses of the recipients from the field specified by the Recipient
Fax Address Field user property on the recipient business component. This is usually a calculated field that constructs the
addresses appropriate to your installation. When the SMTP/POP3 adapter is used, these addresses should be in SMTP format
(for example, 6501112222@fax.company.com), and your fax server must be set up to handle these addresses. For details on
how to set up your fax server to work with SMTP addresses, consult the documentation of your fax server. Once the fax
server is set up properly, you should modify all the fields specified by recipient Fax Address Field user properties to
construct the correct addresses. (12-4XHG6F)
Siebel Professional Services Automation

Financial Profile’s Amount Billed
For customers installed on DB2 for OS/390 and z/OS, there exists a default query limit of 48 records returned. This may
affect queries calculating the amount billed for your projects. For a detailed discussion on the strategy and implications of
query limits with Siebel and DB2 for OS/390 and z/OS please consult the guide Implementing Siebel eBusiness Applications
on DB2 for OS/390 and z/OS. To ignore this limit you will need to change the properties in Siebel Tools to -1 for 1)
Maximum Cursor Size and 2) PreFetch Size. You should set these properties for the following Business Components:
Time Sheet Unassoc Daily Hours
Time Sheet Daily Hours
Expense Unassoc Item
Expense Item
FS Invoice Line Items
FS Invoice Line Item Details
4

PS Project Invoice (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B9PLXF)
Project Team Analysis
Selecting Project Team Analysis in Team Workbook produces a blank view or error message (if you have Display Every
Notification About Script Error option turned on in Microsoft Internet Explorer). To display the Project Team Analysis, click
on the Team Workbook tab again (if you encounter script errors, close script errors and then click on Team Workbook tab).
(12-B8H0OJ)
Find Resource Button Does Not Return Potential Resources List
After clicking on the Find Resource button on Resource Request Detail Applet, no results are returned in the PS Potential
Resources List Applet. After clicking on the Find Resource button on Resource Request Detail Applet, no results are returned
in the PS Potential Resources List Applet. The following steps can be used in Siebel Tools to address this issue:
How to fix PS Potential Resources List Applet to return qualified candidates after clicking on Find Resource button:
1. The project required in repository is PS Resource Assignment. Go to Object Explorer > Project, select and lock the
project.
2. In Object Explorer, under Siebel Objects, choose Business Component.
3. In Business Components applet, query for PS Potential Resource in Name field.
NOTE: If the record is read only, you need to click Tools > Lock Project to lock the project named PS
Resource Assignment.
4. In Object Explorer, click Field under Business Component.
5. Create a new record (right click and select New Record). Set the Name to be Availability Score Calc, check the
Calculated flag, set the Calculated Value to be IfNull([Availability Score], 0), check the Force Active flag, change
the Type from DTYPE_TEXT to DTYPE_NUMBER.
6. In Object Explorer, under Siebel Objects, choose Link.
7. In Link applet, query for PS Project Team/PS Potential Resource *Avail Filter*, and the record returned should be
named PS Project Team/PS Potential Resource (Avail Filter).
8. Replace the Search Specification with [Skill Score] >= ParentFieldValue (Min Skill Score) AND [Availability Score
Calc] >= ParentFieldValue (Min Availability Score).
9. Compile the project named PS Resource Assignment. (Not applicable to Siebel CRM or FINS CRM or Base MME
or FINS MME.) (12-B6AZDV)
Copying Project Agreements
When copying a project agreement with line items in Project Agreement List View, an error message will occur. To copy the
agreement record, drill down to the agreement record (FS Agreement Line Items View) and use the Copy Record command.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AK82KB)

Gantt Chart shows maximum of 4 assignments per resource
The resource availability Gantt chart displays a maximum of four project assignments per resource for the displayed period.
Additional project assignments are not displayed. This behavior has been identified as change request. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-4BAQ3K)
MS Project Import/Export
Exporting tasks to MS Project may result in inconsistencies between Duration, Start, and End fields. This occurs because
Siebel task dates begin at midnight (12:00 AM) and the Siebel work calendar defaults to 24 hours per day, 7 days per week
(as opposed to MS Project’s 8 hours per day, 5 days per week work calendar). To minimize data inconsistencies, define
mapping to export tasks and activities without end dates (export task and activity start date and duration). (12-9S7UQS)
MS Project Import/Export
MS Project Import and Export may fail (MS Project process is not terminated) when DocServer and Siebel Server are on the
same server. To maximize stability and performance, DocServer and Siebel Server should be run on separate servers. (12-
7ZT06W)
Invoicing Time & Expense Adjustments
When creating invoices in the Invoice screen, time and expense items include adjustments. Time and expense adjustments
cannot be invoiced individually. Thus, adjustments made to time and expense items that have already been billed cannot be
included on manually created invoices. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
6ZFBG6)
Required Project Mapping
The Project Mapping Name = resource Name must exist in the Project Resources Mapping Categories for the correct number
of resources to be exported from a Siebel application to Microsoft Project. (12-81X5RW)
Time and Expense Items Not Marked as Billed
Manual creation of invoices with time and expense items does not mark the items as billed. As a result, the amounts for such
items will display in the Unbilled Fees and Expenses fields in the Financial Profile view, rather than the Billed Fees and
Expenses fields. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6ZFBG1)

Cannot Insert Organizational Analysis Charts into Proposals and Presentations
In order to accomplish the much improved usability of the Organizational Analysis Chart in Siebel 7, a specialized Java
Applet was designed. However, the ability to store the Organization chart applet in the Siebel File System, which is required
for generating Proposals and Presentations, is currently not supported in Siebel 7. Thus, Siebel 7 will not support the
insertion of Organizational Analysis Charts into Proposals and Presentations in the 7.0 Release. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-6RN75Y)

Microsoft Office XP Hangs When Generating Remote Web Client Presentations
When using Office XP with Siebel Presentations in the Remote Web Client, PowerPoint hangs while generating a
presentation. To work around this problem, users can right-click and choose the Restore command on the PowerPoint
session from their task bar. Because this bug is found only in High Interactivity mode, in Siebel Tools you may switch the
Account Proposal Applet and Opportunity Proposal Applet to Standard Interactivity. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-5Q2UPM)
Missing "New" Button on applet
Currently just the Edit and Query buttons are displayed. To display the New button on the applet, perform the following
steps:
1.The applet displayed on the Screen is the Proposal Section Admin List Applet.
2.Go to Tools and select Applets in the Object Explorer.
3.Query for “Proposal Format Admin List Applet”.
4.Now for this Applet, Go to Applet Web Template and Select Base.
5.Next Go to Applet Web template Item and for this Base Web Template and select the
Item NewRecord.
6.Its Inactive property is Set to “TRUE”. Change it to “FALSE”.
7.Compile the SRF and run the Application.
If you want to Remove the Edit button, perform the following steps:
1.The applet displayed on the Screen is the Proposal Section Admin List Applet.
2.Go to Tools and select Applets in the Object Explorer.
3.Query for “Proposal Format Admin List Applet”.
4.Now for this Applet, Go to Applet Web Template and Select Base.
5.Next Go to Applet Web template Item and for this Base Web Template and select the
Item EditRecord.
6.Its Inactive property is Set to “FALSE”. Change it to “TRUE”.
7.Compile the SRF and run the Application.
(12-FKL5O2)

Siebel Quotes
Clicking Verify Button Before Creating a Package Item
Indenting a line item into a package may result in the following error: Error: Method Indent is not allowed here. This error
occurs only if the user had invoked the quote Verify functionality in the previous step. The workaround is to navigate to
another view and return to the Quote Item View. (12-BAID5J)
Tax Amount in Quote Terms View is Inconsistent with Total
The tax amount shown in the Tax field in the Quote Terms View may be inconsistent with the Total field in certain
situations. This will occur if there are line items of type Product and line items of type Service in the quote. The
inconsistency occurs because the Tax field (as exposed in the view), calculates tax only on Products, while the Total field
considers tax on all the line items, regardless of the type.
The work around is as follows. Internally, Siebel stores tax in two separate fields: Tax - Product and Tax. The Tax - Product
field is currently exposed in the application view. Replacing the Tax - Product field with the Tax field in the view, would
make the Total field consistent. This task should be performed in Siebel Tools as follows:
1. In Tools, go to the Applet Siebel Object and query for the applet Quote Totals Form Applet
2. Go to the controls for this applet and query for the name tax
3. Change the value of the Field column for this control from tax - Product to tax (12-B92ZJ2)
Clicking Service Button Yields No Records
Clicking on the Service button may yield no records even though the price list may contain service products. This happens
under the following conditions:
User applied query conditions in the Pick Product window when adding a product to quote.
User then clicked on Service button in order to pick a service product.
In this case, upon clicking the service button, the system applies the same query conditions when searching for service
products. The workaround is to hit the Go button in the service product pick list window when no records appear. This would
perform a query without conditions thus bringing all the service products. (12-B93BVY)
MaxCursorSize and MaxPrefetchSize Setting on DB2 390
MaxCursorSize and MaxPrefetchSize restrict the default number of rows that will be fetched by Object Manager for every
executed BusComp query. With these parameters set, Object Manager will fetch up to MaxCursorSize rows, and then Object
Manager will close the physical database cursor associated with the BusComp query. All pending results are discarded.
For example:
MaxCursorSize = 48
PrefetchSize = 48

Navigate to the All Accountsview and query for all accounts. Object Manager will execute the query, fetch 48 rows into
memory, and then close the database cursor. In the UI, the first 7 rows will be rendered once all 48 rows are fetched. The
user can now scroll down, but once she tries to scroll pass row 48, the following message box will appear:
Why we need to set these parameters for DB2 390:

Though DB2 390 can support up to hundreds of thousands of connections. However at any moment, DB2 390 can only
support 2000 active database connections. A database connection is classified as being active if there is currently a
transaction or if there are open cursors on the database connection.
Siebel’s Object Manager keeps database cursors open to allow users to scroll through data. As a result Siebel on DB2 390
cannot support thousands of concurrent Siebel users. To work around this, we used the MaxCursorSize/PrefetchSize feature
of Object Manager in Siebel 6.2.1 and 7.0.4.
How this affects views/applets:
With MaxCursorSize/PrefetchSize, views and applets, by default, can only return up to 48 rows. If a user wants to see more
data they will need to refine their query so that less rows are returned.
How these parameter are set out-of-the-box:
For all Siebel product installs, MaxCursorSize and PrefetchSize are both set to 48. For the Zero Foot Print Clients (SES),
these parameters are set on the NameSrvr under NamedSubsystems). For the Connected Clients, these parameters are set in
the CFG files.
The only exception is Siebel Tools, in which case MaxCursorSize and PrefetchSize are set to -1 since the number of Tools
users in a production environment should be very small.
How we over-ride the MaxCursorSize setting:
Of course the above behavior is not always desired and in fact will break functionality. For example, charts require that all
rows be returned; so all MaxCursorSize must be ignored.
NOTE: IMPORTANT: Before you consider over-riding MaxCursorSize, please consider whether it is
absolutely necessary! For example, Charts and Export, are absolutely necessary as these features are very
important. All Opportunities, My Accounts, and so on, are not. Lastly, remember the more views and
applets we override MaxCursorSize the less of the Siebel product gets on DB2 390.
There are 2 ways to override MaxCursorSize:

1. Direct Method - Using BusComp code:
ErrCode CSSBusComp::Execute (BOOL bForwardOnly,
BOOL bSetupOnly,
BOOL bIgnoreMaxCursorSize)

By passing TRUE to the third parameter of CSSBusComp::Execute, the value of MaxCursorSize is ignored.
2. Indirect Method - Usingsetting BusComp properties “Maximum Cursor Size” and “Prefetch Size” to a large number.
This is the preferred method if you have a business component that is guaranteed to return relatively few rows. This method
is for business components that are used primarily in picklists to make sure that the picklist contains all the choices. Choose
a value that is larger than the maximum number of rows that one can possibly fetch from the buscomp, such as 500. It is
essential to set both Maximum Cursor Size and Prefetch Size to the same value. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-AT1I6V)
Revise a Quote
Revising a quote may give an error Error writing a record). This error will occur if Multi-Value Links (MVL) have been
configured in Siebel Tools for the new Totals field. In such a case, make sure that, under the Quote business component
MVL properties, No Copy is set to Y. Failure to do so will cause Revise to create duplicate quote items, thus giving an error.
(12-9XQQON)
Attribute Selection Returns Error
The default values for attributes when defining them in a class are required to be in Siebel canonical format -- for date fields,
it needs to be MM/DD/YYYY; for number, XXX,XXX.XX; for integer, XX,XXX,XXX. This requires the display value of
LOV needs to be in this format as well. If the values are not in canonical format, an error (the selected value does not match
any pick list value), will result when selecting a value at runtime, in a Quote or Order for example. (12-9R8G47)
Manual and Automatic Discounts for Japanese Currency
For Japanese currency, there will be a discrepancy between manual and automatic adjustments. This is because the pricing
engine is carrying out the precision while manual discount is not. For JPY the extended scale is 0 (USD is 5). This means that
for JPY, the database will store 0 digits for all currency fields. To eliminate the discrepancy, the extended scale should be
changed to 5. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9YQIEZ)
Add Item button
If you try to add a product with default attributes that are not a valid attribute pricing combination, you will not be able to do
so. It will seem that the Add Item button is not working. Make sure that the product has default attributes that are a valid
attribute pricing combination. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9RTIAN)
Price Rounding in Catalog and Quotes
If the third decimal place of a price is 5, the display price in High Interactivity (HI) will be rounded down. But in Standard
Interactivity (SI), the display price will be rounded up. For example, on the Catalog, if the price ends up being 10.275, the
price will show up as 10.28 in Catalog but 10.27 in Quotes (HI). However, the value of 10.275 will be saved to the database
correctly. (12-6DEUHK)
Customizable Products and Manual Pricing
Note the following behavior when you perform the following steps:
1. Add a customizable product to quote. In this case, there are no pricing models or volume discounts.
2. Apply header level discount of 10%.

NOTE: You will see this discount applied to all products. (If there was an applicable pricing factor or volume discount
for a given line, the header level discount will not apply)
3. Apply line level (manual) discount of 13%.
NOTE: You will see the 13% discount applied to the line. However that discount is not reflected in the customizable
product (rolled up) net price. That is because the header level discount automatically sets the Keep Discount flag for the
root product of the customizable product. This Keep Discount flag at the root forces the entire customizable product to
take the root product’s discount, which is 10% in this case.
4. Uncheck the Keep Discount flag for the root product of the customizable product.
NOTE: Now you are saying disregard the discount stated at root product. Therefore, you are saying roll up all manually
applied discounts at the line level. The header level discount (10%) appears in the net discount percent field for the lines
that have not been individually adjusted. But the customizable product net price will only reflect the adjustments made
individually at the line level. To be sure, check the discount amount field to see which lines have adjustments that will
be rolled up into the customizable product net price.
General rules:
1. If there is a manual discount and there are no volume discounts or pricing factor discounts, the manual discount
always takes effect.
2. A header level discount automatically sets the keep discount flag for all products.
3. When there is a keep discount flag on the root and line level, the discount specified at the root takes precedence over
all line level discounts. Therefore, when the keep discount flag is true for the root product, the discount specified at
the root is the discount for the entire customizable product.
4. When the keep discount flag for the root product is not checked, the customizable product price will be based on the
rollup of line items. Look at the discount amount field for each line to determine what will be taken into account
during rollup. If the children do not have discounts and the root product has a discount (with keep discount flag
unchecked), then the discount of the root will take effect.
5. You can set a line level discount for the root product itself (should the root product have a price). (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6B7TIB)
Avoid Package Names for Simple Products
Avoid using Package names for Simple products. Package names may cause Quote reports to appear incorrectly by
associating incorrect products with Packages. (12-6R9TXL)
Quote Pricing Model Validation
Browse Catalog Button
The Browse Catalog button on the Quote Pricing Model Validation view is not supported. After clicking the Browse Catalog
button on the Quote Validation view, users will be able to return to the view only by selecting Pricing Model Validation
under Pricing Administration and querying for the quote used for testing. Clicking View Quote will not take the user back to
the quote being validated. This is because the Go to Cart button takes the users to quote related views and not to the quote
model validation view. This button will be disabled in a future release. To inactivate the button in the current release, copy
the applet that contains the quote header to a different applet. Replace the applet with the existing applet in the Quote Pricing
Model Validation view. Disable the Browse Catalog button in the new view. The workaround for this functionality is to

have the pricing administrators and other users come back to the Pricing Quote Model Validation view by navigating through
> Site Map > Pricing Administration > Pricing Model Validations. Users will then need to query for the quote initially used
for validation. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5S5CN8)
Browsing Catalog
When administrators navigate to catalogs from the Pricer Model Validation views, only the catalogs and associated products
for which the user has administrative privileges are displayed. To navigate to a set of products in the catalog while
performing pricing model validation, users need to make sure they have administrative privileges on the catalog. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5S5CM7)
Account-specific price book report
Account-specific price book reports can be invoked only from the regular Quotes views. Currently, this report is not
available in Quote Pricing Model Validation view. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-5SWTKT)
Siebel Remote
Five of the ten Routing Models defined in the seed data are filtered out by a search specification in the pick list of the Mobile
Client view.
Of the ten, seven are specialized models designed to reduce the amount of data being replicated down to mobile clients by
filtering out data that mobile users do not need. Please refer to the Siebel Remote and Replication Manager Administration
Guide for a detailed explanation and definition of these routing models.
Routing Model Siebel Responsibility Type Filtered

Analyst Business Analyst Specialized Yes
Consultant Consultant Specialized No
Field Engineer Field Engineer Specialized No
Field Sales Manager Standard Field Sales Representative Specialized Yes
Field Sales Representative Field Sales Representative Specialized Yes
Standard
Field Technician Field Technician Specialized Yes
Sr. Field Engineer Senior Field Engineer Specialized Yes
Executive Management Any responsibilities that do not have all objects, Generic No
all objects across Organizations, and Manager’s
Explorer views
MOBILE CLIENT – STANDARD Any responsibilities that do not have allobjects, Generic No
allobjects across Organizations, and Manager’s
Explorer views
MOBILE CLIENT - EXTRACT Any responsibilities that do not have Generic No
ONLY all objects,
all objects across Organizations, and Manager’s
Explorer views
Each of these models should be used with a specific Siebel Responsibility as indicated above. For majority of our customers,
using the MOBILE CLIENT – STANDARD, MOBILE CLIENT – EXTRACT ONLY, or the Executive Management
routing model is adequate. For customers that have a strong business requirement to reduce the amount of data being

replicated to mobile users, using one of the specialized routing models may be appropriate. Before deploying Siebel Remote
with any of these specialized routing models, Siebel strongly recommends that you discuss with a Siebel technical resource
about using it. Before using the specialized Siebel Routing Models, you would have to assess the impact of the following
tasks:
1. Analyze the mobile users usage pattern. Find out what data the users need and what they do not need when using
the application in the local mode.
2. Compare the usage pattern with the definition of each routing model. Note that each model was designed for a
specific class of mobile users.
3. Perform a review of your Siebel installation and answer the following questions:
a. Did you modify any of the views that have been assigned to the Siebel Responsibilities associated with the
specialized routing model (See table above)? What kind of modifications? Was MVG added to any fields?
b. Did you modify any of the Siebel Responsibilities listed above by adding new views and making them
accessible in local mode?
c. Have you assessed the impact of the routing model on the Transaction Router?
4. If the answer to any of the above questions was Yes, using any of the specialized Routing Models would be
inappropriate.
5. If the answer to all the above questions was No, then conduct a field test with a small group of representative users
using the chosen routing model and assess the impact of the specialized routing model on the transaction router.
During the test, make surethat the following behavior is observed:
a. Local database size and the amount of data being replicated should be reduced.
b. Mobile users can still perform business tasks;that is no data is missing that prevents the user from
completing a critical business process.
c. Synchronization time should be shorter.
d. All server transactions should be routed to the mobile client except for those that are explicitly excluded in
the routing models. If this is not the case, it could also be a case of the user responsibility not matching the
routing model.
e. All views that have data on the server should show the same data on the mobile client. If this is not case,
there is a strong possibility that the views were included erroneously in the user responsibilities.
6. If you had acceptable results from the field test, then you are ready to deploy the routing model to the appropriate
mobile users.
7. The following usage scenario is inappropriate and should be avoided when using specialized routing models:
- Adding other views to an out-of-the-box Siebeldefined Responsibility that is matched to a specialized routing
model.
Generally, views that contain data from limited visibility objects should have routing rules to support them. If a view is
added that does not have corresponding routing rules, then no data will be replicated for that specific view. If such a view
was added to a Siebel Responsibility and the implementation uses Client Wins for update conflict resolution, the following
erroneous situation could happen and should be avoided.
Step 1: Siebel user creates a new record using the newly added view on the Mobile Web Client

Step 2: Siebel mobile user synchronizes with the server
Step 3: Another user makes changes to the same record on the server
Step 4: Siebel mobile user synchronizes and does not see the updates to the record
Step 5: Siebel mobile user makes changes to the copy of the record in the mobile client
Step 6: Siebel mobile user synchronizes and overwrites the content of the record on the server
The result is that the mobile user could unintentionally overwrite the updates made by another user to the same record.
8. Exposing a custom foreign key in a Siebel view and business component.
A custom foreign key would likely not have any Siebel Remote routing support because routing rules are deactivated out-of-
the-box or no rule was created at all. As a result, no data will be routed to support the foreign key. If any base record
containing this foreign key is touched or updated by the mobile user in the local database, it may inadvertently reset the
reference to null and in turn, replicate this change to the server.
9. Modifying an out-of-the-box view assigned to a responsibility that is matched to a specialized routing model.
If an MVG field were added to an existing view, a mobile user could, by modifying any fields for a row or selecting the
MVG field, set the value of the MVG field to a No Match row-id. The reason is that no data for the MVG was downloaded
to mobile client. This action implicitly creates an update transaction to be replicated to the server on the next synchronization
session. Database integrity is compromised when the transaction is applied on the server. (12-9J1A8W)
Siebel Remote components will deadlock when running multiple instances
In order to run multiple instances of Siebel Remote components, including Dbextract and Transaction Merger, certain tables
must be set to Row Level Locking or these components will experience deadlocks. Contact Siebel zSeries Product Marketing
for additional details. (12-B3KCM4)
Dependency of dbextract on database sort order for nonEnglish deployments
Siebel dbextract expects data to be returned from the Siebel database using an English (ASCII) sort order, otherwise
dbextract will fail. In the database used by Siebel Software, set the default sort order to BINARY. This value is required
regardless of the language that the customer has chosen for the user interface. A side effect of this setting is that data
appearing in list applets may not be sorted in the appropriate order for nonEnglish users.
For example, using an Oracle database server on Microsoft Windows NT:
1. From the installation wizard for Oracle installation on NT, you are prompted for the default sort order. Choose
BINARY. On NT, you can confirm that the correct value has been set by checking the registry settings on the NT
database machine. The following registry entry should show a value of BINARY:
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\NLS_SORT
2. For the Siebel Remote client after the Siebel installation has completed, set the NLS_LANG environment variable
to AMERICAN_AMERICA.WE8MSWIN1252 on the Siebel Remote machine. This value is read by the database
connection software at runtime.
3. For third tier client installations after the Siebel Enterprise Server has been successfully installed, set the
NLS_LANG environment variable to AMERICAN_AMERICA.WE8MSWIN1252 on the machine running the
Enterprise Server. This value is read by the database connection software at runtime. (12-9QPPCP)

Database Extract in a Japanese Environment
This is only applicable for the Japanese locale. The parameter value of the Database template file name in the database
extract is set to enu_1252.dbf. For a Japanese locale the parameter value should be set at jpn_932.dbf. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6UJ525)
Campaigns are being replicated to mobile users who have the Field Sales Manager Standard or the Field Sales Representative
Standard routing models. Campaigns should not be routed for users with these routing models. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-6LSLLJ)
Using case sensitive search on the local database when using the Mobile Web Client can be slow. The work around is to use
case insensitive search for the local client. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
6TKI53)
Changing the user's local password will cause Siebel Anywhere schema upgrade kit to fail. The workaround is to maintain
the password that is set during the client initialization or keep the password of the Siebel account in-synch with the user's
password. This means that if there is process to the change user's local password, it should also change the Siebel accont's
password to the same value as well. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
6FA16R)
In the Mobile Clients view, clicking on the link of a newly defined mobile client will not work until the mobile client has
been extracted and initialized. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6DF29V)
Child objects such as an Expense Item of an Expense Report can be modified in the mobile client even when the parent
object is in a locked state. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-XH2OF)
In rare cases when the Transaction Merger component cannot delete dx files in the inbox of a mobile user, it will not report
any error messages. The dx files will remain there permanently. If you are certain that you have encountered this situation,
you may delete them manually. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-1OPLAQ)
Redialing on Microsoft Windows 95
On the Microsoft Windows 95 client platform, Siebel Remote may encounter an error when attempting to redial the network
connection after encountering a busy signal. The Microsoft executable that interfaces with the modem does not free itself
automatically, locking the modem and preventing a subsequent connection. To avoid this issue, users should connect to the
network manually through dialup networking before starting the Siebel Remote synchronization session. Alternatively, you
could provide a batch file that invokes siebsync.exe and stops the rnaapp.exe process upon exit. The rnaapp.exe process is the
Microsoft process that keeps the modem locked. (12-VWO01)
Siebel Reports Server and Siebel eReports Server

Updated Reports for Language Releases Available on Support Web
The following release note is applicable for all language pack releases. There are updates for the following reports on Siebel
SupportWeb.
Finance Commercial Banking Client Profile Report
Finance Investment Banking Client Profile Report
Life Policy by City Report

Finance Life Policy by Salesrep
Finance Life Quotes by Source
Finance Teller Customer Large Currency Transaction Report
Insurance Auto Policy Application Report
Finance Banking Credit Request Facility Report
After downloading the above reports from SupportWeb the following steps must be followed to replace the current installed
rox files.
1. Make sure that Reports Server has been installed.
2. Go to Actuate Administrator Desktop and open encyclopedia.
3. On left hand side will see folders, navigate to Siebel Reports Folder and then to Language folder
4. Right click on folder to add file, add the fixed rox, replacing existing rox.
5. When report has been successfully added, right click on report and go to Properties.
6. Go to the privileges tab and change privileges to Visible, Read, and Execute.
7. Run the new replaced report. (Not applicable to Siebel CRM or Base MME.) (12-B6KXL8, 12-B6V67U, 12-
AMC92V, 12-AN04UE, 12-AN37RD, 12-ATGZ2W, 12-B67E81)
Deploying Reports Server in Firewalls
The Reports Server can be successfully deployed in the firewall environment. However, the Siebel server host and web server
host containing Siebel Web Server Extensions may not be separated by a firewall. (12-A5G8HZ)
User Administration view with DB2/390 database
In DB2/390 deployments, the administrator can only synchronize the first 48 users with default configuration. To
synchronize all Siebel users, the administrator should set MaxCursorSize and PreFetchSize parameters to -1 in the
appropriate .cfg file. After restarting the Siebel server, the administrator should synchronize all Siebel users using
synchronize All button in Reports Server > User Administration view. The administrator should change these parameters
back to the default vales after synchronization is complete. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-BACM4V)
Viewing a Report in Mobile Web Client
Reports can be successfully generated interactively in the Mobile Web Client. However, the report viewer window is
automatically pushed to the background. The user should select the report viewer window in the task bar to view the contents
of the report. (12-BAYVIO)
Auto Resizing of Parameter Dialog
The parameter dialog is automatically resized depending on the number and size of the parameters while generating a
parameterized report. The administrator may choose not to resize the parameter dialog by creating a Control User property
DisableAutoResizeHide, and setting it to TRUE for the desired buttons on the pop-up applet. (12-AV17IM)

Deploying Reports Server in AIX
Using Siebel eBusiness applications in AIX platform, reports can be generated and viewed with Reports Server. However,
the Actuate ReportCast Agent must be installed in a separate machine with IBM HTTP Server 1.3.19, since Actuate 5 SP1
does not support IBM HTTP Server 2.0.3. Please note that Actuate ReportCast Server and Actuate eReporting Server can be
installed in the same machine as Actuate ReportCast Agent or a separate machine. (Not applicable to Siebel CRM or Base
MME.) (12-B39UIZ)
Generating Parameterized Reports
When generating a parameterized report interactively, the report is generated but the report viewer window is automatically
minimized. Therefore, the user needs to maximize the DHTML report viewer in the Windows taskbar to view the report. The
work around to generate and display a parameterized report is described below:
1. The reports administrator should identify the parameter applet for the parameterized report using the Report object
in Siebel Tools.
2. Identify the submit button on the parameter applet.
3. Add the following Control User Property to the Submit button:
Name: DisableAutoResizeHide
Value: True
4. Save changes and recompile the changes into an .SRF file. Save changes and recompile the changes into an .SRF
file> (12-B5DLZY)
Korean Package Quote Reports
This is applicable to the Korean locale. Certain Siebel Korean reports are updated and available rox files on Siebel
SupportWeb. Using the Actuate Administrator Desktop, follow the steps below to update the Korean Package Quote report.
1. In Actuate Administrator Desktop go to File >Administrator. User Name = Administrator, Password is left blank
and Volume is the name of your Reports Server.
2. In the Explorer View navigate to Siebel Reports>KOR.
3. Right click on the KOR folder, select Add, and navigate to the new quotepkg.rox file. A dialog box will appear with
text, “Do you want to replace or version the report. “ Click Replace.
4. When added, right click on the rox and select properties.
5. Select Privileges, and give the all users visible, read and execute privileges.
6. The report will now run successfully. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.)
(12-B1N7KJ)
Smart Report Pipeline for Language Release
The following is applicable to the nonENU locales. The Siebel report Smart Report Pipeline (pipeana.rox) has been updated
for all language releases. The updated rox can be downloaded as a zip file from Siebel SupportWeb. Query for the heading
Updated PIPANA.ROX for the zip file containing the ROX files.

For the Siebel mobile client, the customer should select the appropriate language rox and copy it to the report directory of the
client. For the zero footprint client (that is, eapps), first install the Actuate Administrator Desktop (ADT) and copy the rox to
the Reports Server. Before deployment, change the attribute to allow Visible (V), Readable (R), and Execute (E). (12-
9XXHGP)
Reports in More Info Tab
Users may navigate to a screen tab and run reports by selecting Reports from the View menu. However, the Reports menu
appears as grayed out if the More Info tab is selected from second level navigation. At this stage, the user should select the
screen tab again, and then select Reports from the View menu to run a report. (12-9U4FY8)
Inventory Cost Detail Report
Thisis applicable for Western European locales other than American English. Some columns will display Euro and Dollar
currency symbols. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9UM3IJ)
Exporting Report data
The search button in the DHTML report viewer allows searching for text and keywords in a report, and exporting the results
in Comma Delimited Data or Tab Delimited Data format. The results of a search can be exported in either format, but not
both, regardless of which format is chosen first. As a work around to exporting report data in the other format also, select
New Search and perform the same search again, and then export the results in the other format. (12-6QGKWM)
Report Navigation in Reports
With the Report Navigation button in the DHTML report viewer, users can navigate to different sections of a large report.
However, the report design should include the definition for Table of Contents (TOC) in order for the Report Navigation
button to work. While most reports include the TOC definition, some reports may not. (12-6B3NWQ)
Querying in the Reports Server views
While running a query in the Reports Server views, make sure that the query includes the complete text of a field in the view.
For example, enter the full text of “/Siebel Reports/ENU/OPDET.rox”. Entering partial text in the query may not display any
results. (12-6B3NWL)
Searching in Revenue Reports
After a DHTML report has been generated, a user can click on a Search button in the report viewer to initiate a text search of
specific fields. The Search button works in the Revenue Analysis Detail and Revenue Analysis Summary reports, except that
the search frame displays the Account field as thenTitle and totName, respectively. (12-6B3NVS)
Navigation in Incentive Compensation Plan Payout Report
The DHTML report viewer includes a report navigation button to facilitate navigation in a particularly large report. By
clicking on a report navigation button, a full table of contents is displayed in a frame adjacent to the DHTML report frame.
The user can then click on a hyperlink in the table of contents to view a specific section of the report. In the case of the
Incentive Compensation Plan Rule Payout report (INCOMPAY.roi), duplicate table of contents hyperlinks are displayed
when a user selects the report navigation button. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-68TBJO)

Emailing the Report in HTML format
After displaying a report in the dedicated Web client, the user may send the report in HTML format as an attachment in an
email, using the report viewer buttons. However, opening this report attachment prior to sending the email may cause the
dedicated Web client to crash. (12-65YF0O)
Status of Completed Requests
The Completed Request Notifications view displays the details of all scheduled requests and includes a hyperlink to the
report output. However, the name of a failed report is not displayed in the Completed Request Notifications view. (12-
65VT8T)
Access to Reports Encyclopedia
Due to an out-of-the box integration of Actuate e.Reporting Server with Siebel, the Reports Encyclopedia can be accessed
from the Reports Server views, eliminating the need to use Actuate ReportCast. Further, with Single Sign-On, Siebel users do
not have to remember the Reports Server logon parameters. Therefore, they cannot log in to Actuate ReportCast to access the
Reports Encyclopedia. (12-5RTV3Y)
Displaying bar charts and charts in Reports
Siebel Reports allow for the generation and display of graphs, bar and pie charts with formatted text. While most types of
graphs and charts are supported, the labels for certain bar graphs are not correctly displayed when the report is generated in
UNIX. The Call Center Volume report has been disabled in this release. (Not applicable to Siebel CRM or Base MME.) (12-
7KMV2M)
Saving Reports as .pdf
Reports can be saved as .pdf documents from the DHTML report viewer. Acrobat Reader 4.05 and 5.0 are supported for
viewing the reports in .pdf. However, Acrobat Reader 4.0 is not recommended for saving, because there can be data loss
while saving reports as .pdf. (12-8HCYYW)
Searching in the DHTML report viewer
The search function in the DHTML report viewer allows searching for text and keywords in a report and exporting the search
results to Excel or other spreadsheets. If the report contains multiple sections in which the search is performed, the results
may not be displayed at all. (12-8JUHZM)
Resynchronize reports users after database upgrade
After database upgrades, the administrator should re synchronize all the reports users in the Reports Server > User
Administration view to make sure that the passwords of reports users are in sync with Actuate eReporting Server.
Siebel Sales Base Application

Marketing Analysis Categories applet on the Sales Homepage not functional
The Marketing Analysis Categories applet on the Siebel Sales Homepage contains functionality no longer supported in Siebel
7.0.3. This applet will not function. To eliminate any user confusion, disable the applet in Siebel Tools. The applet name in

Siebel Tools is sales Analysis Predefined Categories List Applet – Homepage. (Not applicable to Siebel CRM or FINS CRM
or Base MME or FINS MME.) (12-A441LJ)
Contacts
Contact list views include contacts and employees
Contact views display contacts and employees in a single list applet. While contact records are generally editable, employee
records are not. To reduce confusion in this area, you may want to expose an Employee Flag field in the Contact buscomp as
a column or control on one of the Contact applets. (12-6Y6FR7)
Encyclopedia
Dynamic Columns in Competitors Require Manual Refresh
In order to complete the entry of a Competing Product Comparison, Administrators will need to click off and back on their
active record in the Competing Product Comparison applet to refresh the lower Product Comparison applet. A manual
refresh is required to generate the dynamic columns used in this applet. (12-4Q2KV6)
Export
Setting maximum number of records to export
The maximum number of records that can be exported per file is set by the administrative parameter ExportMaxSegmentSize
in the CFG file. The default value for this parameter is 10,000. In order to export more than 10,000 records into a single file,
the value of this parameter must be changed. (12-9BVDEA)
Exporting same query to multiple file formats
To export one group of records in two different file formats, users must perform two separate exports. (12-9JZYHR)
Users need MS IE5.5 SP2 in order to export data to tab-delimited file
Users who are running Internet Explorer 5.5 (in a version lower than Service Pack 2) must install IE 5.5 Service Pack 2 in
order to export data into a tab-delimited file format. (12-55CI8G)
Opportunities
Activate Charts “Opportunity Revenue Analysis”, “Opportunity Revenue Analysis by Employee”, “Lead Quality by
Responses” in Siebel Tools.
Under the Campaigns > Charts view, the Opportunity Revenue Analysis, Opportunity Revenue Analysis by Employee and
Lead Quality by Responses charts must be turned on in Siebel Tools in order to display data. To make these Siebel Tools
configurations, take the following steps in Tools:
1) To update the "Campaign Chart Applet - Revenue Analysis" applet, find the Applet object and query for
"Campaign Chart Applet - Revenue Analysis." Then, navigate to the Chart >Chart Element child object.
Select the "AxisLabel" record. Make sure that the 'Vertical' property on this record is set to "FALSE".
2) Create a new link by navigating to the Link object and creating a new link called: "Campaign Opportunity
(Chart - S_CAMP_CON)/Revenue". (If this record already exists, just check to make sure that the

properties are correct.) Input the following properties: Parent Buscomp = Campaign Opportunity (Chart -
S_CAMP_CON), Child Buscomp = Revenue, Source Field = Id, and Destination Field = Opportunity Id.
3) Update the "Campaign Opportunity (Chart - S_CAMP_CON)" business component by navigating to the
business component object, querying for “Campaign Opportunity (Chart – S_CAMP_CON), and
navigating to the Field child object. Create a new field record with the following properties: Name =
Primary Revenue Id and Column = SUM_REVN_ITEM_ID.
4) Create a new Multi Value Link by navigating to the Multi Value Link object and creating a new record
with the following values: Name = Revenue, Destination BC = Revenue, Destination Link = Campaign
Opportunity (Chart - S_CAMP_CON)/Revenue, Primary ID Field = Primary Revenue Id. Remove the old
MVL record entitled “Position”.
5) Navigate to the Multi Value Field object, remove the record entitled, "Close Date", and update the
following records. Find the “Revenue” multivalue link record and make sure the properties have the
following values: Field = Revenue and Multi Value Link = Revenue. Find the “Revenue Currency Code"
multivalue field record and make sure that the properties have the following values: Field = Currency Code
and Multi Value Link = Revenue. Find the "Revenue Exchange Date" multivalue field and make sure the
properties have the following values: Field = Date and Multi Value Link = Revenue. Stop the server,
compile and restart the server.
(12-EH4Y93, 12-EH3AOG)
Using Opportunities Explorer
A run time error results when a new activity record is created in the Opportunities Explorer view. This issue can be
addressed by the following steps:
1. In Siebel Tools, go to Opportunity Tree Applet, and navigate from Tree to Tree Node.
2. In the the node called Activity Node, change the applet field from Opportunity Activity Applet to Opportunity
Activity List Applet.
3. Go back to the Opportunity Tree Applet and navigate to Applet User Properties.
4. Change SWERHSMode:Opportunity Activity Applet to SWERHSMode:Opportunity Activity List Applet.
5. Recompile the SRF.
After the configuration change, the error should not appear. (12-BFZLFG)
Viewing Sales Pipeline Charts
The Sales Pipeline Analysis chart and the Sales Pipeline Phases Analysis chart only display % of Revenue Quota. The % of
Count Quota chart option that was in Siebel 6.x is not available in this release. As a result, the showand By fields do not have
values. To remove the fields, please follow the steps below.
In Siebel Tools:
1. Go to Siebel Objects >Applet
2. Query for Applet: Oppty Chart Applet - Sales Pipeline Analysis
3. Go to Applet Web Template >Applet Web Template Item

4. Check the Inactive checkbox column for the following web template items controls
ChartPickby
ChartPickfunction
ChartPicktype
Go
LabelBy:
LabelShow:
5. Repeat for Applet: Oppty Chart Applet - Sales Pipeline Phases Analysis
6. Recompile SRF (12-6B7XLI)
Associating Products
The Product Line Id is not copied by default when you copy an Opportunity Product. To automatically copy this field value,
please follow these steps:
1. Start Siebel Tools.
2. Choose Business Component in the Object Explorer window.
3. Query for Opportunity Product in the Business Component window.
4. Choose Field in the Object Explorer window.
5. Find Primary Product Line Id and Product Line in the Fields window.
6. For both Primary Product Line Id and Product Line fields, change the value of the column named No Copy to
FALSE.
7. Compile the Opportunity Product business component into your .srf file and restart the application.
(12-AZS2ZB)
Changing Sales Stage
An error is generated when the user creates a new opportunity and chooses a sales stage before entering the Name field. The
error only occurs when you are in an opportunity applet outside of the Opportunity screen. To correct the error, make the
Sales Stage field (in the Opportunity Business Component) read-only until the Name field has a value. This can be done
through the following steps:
In the Opportunity Business Component:
1. Set the Immediate Post Changes flag on the Name field to be true.
2. Create a new Calculated field with the following parameters:
Name: NameFieldBlankFlag
Calculated Value: [Name] is NULL

3. Create a new Buscomp User Property with the following parameters:
Name: Field Read Only Field: Sales Stage
Value: NameFieldBlankFlag
4. Compile the Opportunity Buscomp into your SRF. (12-AZEY7V)
Improving Performance on IBM DB2/390
The following steps will improve performance on the Opportunities screen when running IBM DB2/390:
1. Navigate to SiteMap >Application Administration > Predefined Queries
2. Query Objects column of list applet for Opportunity
3. Select * Current Opportunities
4. Change Query column from “Opportunity”.Search = "[Close Date] > Today () - 30"“Opportunity”.Sort = "Close
Date (ASCENDING)" to “Opportunity”.Search = "[Primary Revenue Close Date] > Today () -
30"“Opportunity”.Sort = "Close Date (DESCENDING)"
This will reduce the view load time to 0.1 seconds. Note that the change will increase the Oracle view to 0.2 – 0.3 seconds.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-ASPKMV)
Siebel Service Base Application

token not valid Error When Generating Preventative Maintenance Engine in Siebel Service
A syntax error in prevmnt.sql will cause the Preventative Maintenance engine to fail in Siebel Service. To fix this, perform
the following steps:
1. Shut down the Siebel server.
2. Use a text editor to open the file prevmnt.sql, located in the SQLTEMPL subdirectory of the Siebel Server home
directory (for example, C:\sea704\siebsrvr\sqltempl)
3. Locate the [DB2/400] section. In this section, locate the GET_CLIENT_IDS query, which looks like this:
SELECT tmp.ROW_ID
FROM &Table_Owner.S_INV_TEMP tmp
WHERE ((TIMESTAMPDIFF(16, CAST(TIMESTAMP(tmp.CREATED)-{fn now()} AS CHAR(22)))) > 90)
AND (tmp.SOURCE_PROG_ID = “FSPrevMnt”))
OR tmp.CLIENT_REQ_ID = ?
4. Add a left parenthesis (“(“) before the token TIMESTAMPDIFF but after the token WHERE. The correct query
should look like this:

SELECT tmp.ROW_ID
FROM &Table_Owner.S_INV_TEMP tmp
WHERE (((TIMESTAMPDIFF(16, CAST(TIMESTAMP(tmp.CREATED)-{fn now()} AS CHAR(22)))) > 90)
AND (tmp.SOURCE_PROG_ID = “FSPrevMnt”))
OR tmp.CLIENT_REQ_ID = ?
5. Save and close prevmnt.sql.
6. Start the Siebel server. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B8JPHZ)
Multilingual LOVs
The Fulfillment, Part Locator, Replenishment, Preventive Maintenance, Cycle Counting and Mobile Inventory Txn server
component processes must be configured to operate in one language where multiple language packs are installed. To
accomplish this, an administrator must set the Language Code parameter in the Server/Component/Parameter view. After
doing so, the Multilingual flag for the relevant LOVs should be enabled. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-81UHPL)
Importing Asset Readings
EIM cannot import data into Asset Readings tables (grandchild of assets) due to a limitation on join depths. (Not applicable
to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5R8083 )
Dispatch Board
The No Sooner Than and No Later Than time window for activities is not graphically displayed in the Dispatch Board. For
performance reasons, this feature has been inactivated in Siebel 7, as supporting it would require a screen refresh. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6RWN7P)
Invoices
Invoice Line Item sum displayed in USD currency by default
The line item total displays the sum of the line items in USD currency based on the applicable exchange rate by default. If
customers desire the local currency to be displayed, the total Currency Code needs to be set to the Invoice Currency Codein
Siebel Tools. The steps to do this are:
1. In Siebel Tools, open Object Explorer.
2. Query for FS Invoice Line Items List Applet in Applet under Object Explorer.
3. Expand Applet to List Column.
4. Query for Amount in the field column.
5. Add Currency Code to the total Currency Code Expression field.
6. Compile a new SRF.

(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9ZZI58)
Siebel Repair
Processing Repair Pick Tickets
Drilling down on a repair pick ticket in the All Pick Tickets, All Pending Pick Tickets, or My Pending Pick Tickets view
always takes you to the Pick Ticket view, instead of the Repair Pick Ticket view. To process repair pick tickets, search for
the pick ticket to be processed using the Repair Pick Ticket view. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-M059P)
Order
Updating Order Terms
Any updates done on the Order Terms view need to be synchronized since there are two different Business Components.
Press Alt Enter on the top applet of the Terms view, and the updates will be synchronized. This will mainly have an effect if
you have made changes to the Ship To address in Terms. By synchronizing updates, the changed address will be predefaulted
on the Order Items when you add a new Line Item. (12-5OHWFV)
Logistics Manager
Selecting invalid serial number for shipping
When a user selects an invalid asset for shipping from a location, the user is not allowed to change or delete the invalid
record. The user has to navigate to a different screen before they can change or delete the invalid serial number record on the
Shipping screen. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-ASZB3M)
System Preference for Fulfillment Engine
OrderTypeToBeFulfilled parameter in System Preference is not used to validate the Order Types to be fulfilled. However, it
should remain as it is entered because it is still being read when the engine is initiated. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-19A9BJ)
Replenishment Engine
When the same product is stored in multiple sublevel locations in a warehouse, the Replenishment Engine calculates
replenishment of a sufficient quantity to fill only the first sublevel location. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-1A8D6D)
Service Inventory
Inventory Location Tables - Table Mappings
EIM table mappings from interface table S_INVLOC_IF to base tables S_INVLOC_REL and S_INVLOC_ROLLUP have
been defined and deactivated. These should not be activated. Mapping data into these tables can result in corrupt inventory
location hierarchy definitions. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6T53JZ)

Inventory Location Tables - Updating Inventory Transactions
Do not update or delete inventory transactions by means of the interface table S_INV_TXN_IF. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-6T53KD)
Inventory Location Tables - Merging Inventory Locations
Do not merge inventory locations. Merging inventory locations through the interface table S_INVLOC_IF can result in the
deletion of inventory transaction records and in incorrect inventory levels. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-6T53K5)
Siebel Barcode
Viewing reports containing Barcodes
The barcode font needs to be available on the client machine where reports containing barcodes are viewed. The barcode font
can be obtained as follows:
1. Install the mobile web client.
2. Navigate to the siebel_root\fonts folder of the mobile web client installation.
3. Copy the file 39HITLHR.TTF to the System_Root\fonts folder of the client machines where the reports will be
viewed (for example, c:\winnt\fonts on Microsoft Windows 2000).
Now you should be able to see the barcodes in reports that are viewed from the web client (both DHTML and PDF formats).
No additional setup is required for the mobile web client since the barcode font is installed during the mobile web client
installation.
Note for report developers: If you are creating or modifying reports to include barcodes, the barcode font has to be available
on the machine when the report is compiled, that is, when the .ROX file is generated. This is required for the barcode fonts to
be displayed correctly in the report output.
The end user’s (client) browser needs to be on a Microsoft Windows platform. (Not applicable to Siebel CRM or FINS CRM
or Base MME or FINS MME.) (12-6Z1JXL)
Barcode Toolbar
The Barcode Toolbar will be reintroduced to the Field Service application in an upcoming point release. It is not part of
Siebel 7.0.2 or 7.0.3 or 7.0.4 releases. Barcode scanners can be used with the application in the 7.0 release, without the
toolbar functionality. The scanner must be connected directly to the PC and the cursor must be placed in the field where the
barcode will be entered or queried. No software setup is required. At this stage the barcode can be scanned and will appear in
the field where the cursor was placed. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
6SE4RM)
Siebel Scheduling
Overtime Breaks
Breaks are not supported in overtime or extended overtime rate types in Scheduling Administration. It is possible to specify
such breaks from the user interface, but these breaks in overtime are not allowed. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-6RPBSF)

Siebel SmartScript
Invoking the GetFieldValue command in SmartScripts on DB2/390
For VBScript/eScript programs in SmartScript on the DB2/390 platform, the ActivateField command must be explicitly
called on fields not associated with questions before invoking the GetFieldValue command. For example, to use the
AccountId field in the Contact business component, do the following:
.ActivateField("Account Id")
AccountID = .getFieldValue("Account Id") (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.)
(12-B5X93M)
Calendar applet has no time zone information
The following issue is only applicable for the Japanese locale. To switch to different time zones, manually adjust the date-
time value. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-7NZT5V)
Using SmartScript when browser has script debugging turned on
If the browser is set so script debugging is turned on, any SmartScripts run in High-Interactivity mode will give a JavaScript
error when invoked. This error can be cleared and the script will run normally. (12-9VUB9B)
Unique names required when converting Script Wizard Scripts
The name of the Script Wizard imported and converted must be unique from any previously imported or converted Script
Wizard Scripts. (12-8PBBIR)
Text Box Sizing for SmartScript Questions
In Netscape browsers, SmartScript only displays a text box of fixed size. (12-6FSM5C)
Guidelines for Naming SmartScript Export Files
Administrators should make sure that exported scripts are saved with an extension of.sss and that the save file setting is All
Files. (12-599QJP)
Siebel Sync
Screen Pop and Email Alert of Messages does not function
On IBM DB2 390 and IBM DB2 400, screen pop upon receipt of message and email alert upon receipt of message do not
work due to lack of support for LONGVARCHAR. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-B0IRN4)
Account and contact association remains when user deletes account data in PIM
If a user deletes an account from a contact record in the user’s PIM, the association between the account and the contact is
not removed from the Siebel application after subsequent synchronization. To remove an account from a contact record, the

user should delete the account from the contact record in the Siebel application, and run Siebel Sync again to make sure that
the change is reflected in the PIM. (12-809YLN)
GroupWise support is limited to Export Only for Personal and Business Contacts, Accounts, Employees
Support for GroupWise Synchronization is limited to Export Only for Personal and Business Contacts, Accounts, and
Employees. (12-86PMSR)
Contact Export malfunctions if more than 5000 records are exported to Lotus Notes
Contact Export malfunctions if more than 5000 records are exported to Lotus Notes. Users must limit the number of records
written using queries. (12-5ZWC1V)
Siebel Time and Expense Reporting

Missing Opportunities In Expense Report Header Record
When selecting an opportunity in expense report, select the account first and then the opportunity. The opportunity pick
applet in Expense Report filters opportunity based on the account field. When the account field is blank (null), only
opportunities without associated accounts are returned. (12-ABFUV0)
Siebel Tools
Import from Archive can associate multiple scripting languages to a single object definition
When importing an object definition using the 'Import from Archive' feature, it is possible to associate multiple scripting
languages to a single object definition. For example, when importing and merging the 'Account Contact' business component
from an archive file, it is possible to have server scripts associated with Siebel VB and eScript. As a result, when a user
attempts to edit a server script in Siebel Tools, the script editor will not be launched. To address this issue, delete the scripts
on one language (eScript or Siebel VB) such that there is a single server scripting language associated with the object
definition. (12-GN60PY)
Dev2prod generates extra GRANT statements (DB2/390 only)
DEV2PROD (from a DB2 UDB database to a DB2 / 390 database) generates a GRANT statement to schema.sql for every
table rather than just those tables where a GRANT statement is needed. This does not cause any issues. Each extra statement
returns the following message:
GRANT SELECT,INSERT,UPDATE,DELETE ON Q202023.X_DD_TRGTGRPMBR TO SSEROLE DSNT404I

SQLCODE = 562, WARNING: A GRANT OF A PRIVILEGE WAS IGNORED BECAUSE THE GRANTEE ALREADY
HAS THE PRIVILEGE FROM THE GRANTOR DSNT418I SQLSTATE = 01560 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNXA07 SQL PROCEDURE DETECTING ERROR DSNT416I
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B790XB)

Siebel Charts
The Chart object in Siebel Tools have certain properties, such as Picklist Functions, Picklist Types, and Picklist Periods, that
take multiple values in comma delimited format. For multi-byte language implementations, such as Korean, Japanese, and
Hebrew, the only supported separator is a comma with no spaces before or after it. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-B52O5U)
Acceptable dev2prod errors missing from errors.rtf (DB2/390 only)
Acceptable errors when running dev2prod_validate_rep.ksh are missing from the errors.rtf file. See the defect comments for
additional errors that may be ignored. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
5EVGCS)
Browser Script
SetProperty method
For the Siebel 7.0.x release, customers are advised not to use the SetProperty method on Control objects. This method has no
effect on the runtime properties of the controls. (12-6TT40Q)
Scripting of DOM events other than OnBlur and OnFocus on List Applets is not supported in applications that
operate in High Interactivity
Though scriptable DOM events are exposed in Siebel Tools for List Applets and its controls, at this time only the scripting of
the OnBlur and OnFocus events are supported. (12-9QTZCZ)
Database Extensibility
Apply Button (DB2/390 only)
There are several errors related to Apply processing. It is strongly recommended that automated Apply processing not be
used to propagate schema changes unless the Tools User is confident of that the DB2/390 alter operation will be successful.
This is because there are certain database alter limitations that can not be properly handled by Siebel Tools. For example,
creating a new column without the proper database security authority results in the following message:
UTLDbFileTbStRead390 Error
Instead, generate the DDL and apply it manually with DBA tools. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-AY2BDB)
Client returns SQL error after adding columns to base or extension tables (DB2/390 only)
Due to the DB2 DDL limitation for tables with LONG VARCHARs, certain operations extending these tables with additional
columns will fail with errors similar to:
SQLError: sqlstate 54010: [IBM][CLI Driver][DB2] SQL0670N The row length of the table exceeded a limit of "" bytes.
(Table space "".) SQLSTATE=54010
A possible solution is to redefine the LONG VARCHAR column to CLOB in the affected table. Review applicable IBM DB2
documentation on CLOB performance and storage requirements and the Release Notes on CLOB (12-B38ZTV) prior to
making this change. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5DY43A)

Object Interfaces
Use of Attach and Detach methods
When using the Attach and Detach methods with the Java Data Bean or COM Data Control, Resonate must be used. Failure
to use Resonate may result in connection errors. (12-9TQP7U)
CORBA Object Manager language startup parameter
When starting the CORBA Object Manager, the language parameter must be in all capitals. For example, to start the English
version of the CORBA Object Manage, the syntax would be the following: /l ENU. (12-9LWNER)
Siebel Java Data Bean implementation of the EAI Siebel Adapter missing the QueryPage method
In order to use the QueryPage method provided by the EAI Siebel Adapter, customers will need to generate the code for the
EAI Siebel Adapter. However, it is recommended that you use the generated code for the QueryPage method only. For the
remaining EAI Siebel Adapter operations (Query, Upsert, Delete, Synchronize), it is recommended that you use the
com.siebel.eai.service.siebel_eai_adapter class, provided in SiebelJI_Common.jar. (12-8RO9S3)
Repository Upgrade
Repository Upgrade and Web Client Migration (DB2/390 only)
The Repository upgrade and Web Client Migration Wizard requires AUTO COMMIT OFF. For DB2/390, the default
environment is Auto-Commit = ON. For Repository Upgrade and the Web Migration Wizard that are Siebel Tools batch
processes, the Auto-Commit setting needs to be overridden. When running these types of Siebel Tools batch processes, set
SIEBEL_DB2390_DISABLE_AUTOCOMMIT=Y as an operating system environment variable before starting the
processes. Reset to N or erase the variable after these processes complete.
NOTE: The SIEBEL_DB2390_DISABLE_AUTOCOMMIT=Y setting is only for these specific cases in

Siebel Tools. Otherwise, do not run with this setting. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-B3IXLZ)
Siebel eScript
Postquery operations such as Totals need to be in forward-only mode
There are a few cases in the Siebel Application (for example, Totals) where, after a query is run, some operations take place.
In such cases, it is recommended that your scripts query in ForwardOnly mode. Keep in mind that when queries are executed
in ForwardOnly mode, the records are not maintained in memory, and navigating backwards is not possible unless a complete
re-query is issued. (12-8GR5AZ)

Installation in Korean and Hebrew
Universal Queuing cannot be installed in Hebrew or Korean. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-AYK5VV)

Maintaining UQ Connection
An agent must be logged in at all times for work items (primarily emails because they do not require immediate response) to
arrive and stay in queue. A dummy agent can be logged in and set to unavailable overnight. (Not applicable to Siebel CRM
or FINS CRM or Base MME or FINS MME.) (12-AYGZP2)
Transferring Work Item
After an agent completes a transfer, the agent must change the availability state on the toolbar to available for each channel
that is different from the transferred work item. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-ARG6RF)
Not Ready Button and Sequential Assignment
In a sequential assignment configuration, the Not Ready button must be used when the agent is not working on any work
items. If an agent is handling a work item, the agent must push the Not Ready button after releasing the work item. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B1165H)
English values must be used for Media Type when the field Property Name is set to Media Type
This is only applicable for the Japanese locale. English values must be used for Media Type when the field Property Name
is set to Media Type.
1. Navigate to Site Map >Universal Queuing Administration>Route View
2. Select the record for which you want to set the route.
3. Create a new record for Property, and designate Media Type as the Property Name.
4. Enter “=“ or “~” in the related field
5. Depending on the desired Media, enter one of the following: “email”, “voice”, “Web Collaboration”, “Activity”, or
‘service Request”.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-8V0jPKV)
Voice Routing Pullback
Agent state is not set to not ready in the case of voice routing if the agent does not accept an incoming voice call. The agent
may remain in a ready state. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-964R4T)
Agent States after Fail Over
In a failure recovery situation, Universal Queuing saves and reinstates agent and work item states. Siebel UQ recovers the
overall state of the agent. If one of the channel states is ready, the agent is set to ready for all channels. If all states are not
ready, the agent’s overall state is set to not ready. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-8UQLJ7)
Creating dustore table for dual server configuration
In order to support the dual Universal Queuing server failure recovery, users will need to create a table for the purpose of
saving work item and agent state information. This table is not part of the Siebel database, so users will have to create the

database before the Universal Queuing installation. You can create the table in the same Siebel database or in a separate
database. Follow these steps:
1. Choose the appropriate database script for the database platform. The database scripts are in the Universal
Queue/Database Scripts directory.
a. For MSSQL, use dustore_mssql.sql
a. For DB2, use dustore_db2.sql
b. For Oracle, use dustore_oracle.sql.
2. Bring up an SQL tool that supports the database.
3. Either copy the database script or load the script into the SQL tools and execute the script.
4. The table dustore will be created with the proper indexes. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-6RE38A)
Use of SHTTP Transport
Siebel Universal Queuing routing engine and Siebel Server should be run inside the same firewall. Siebel Universal Queuing
uses HTTP as a transport, not SHTTP. This could have security implications if these components are run across firewalls.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6RE38M)
Siebel Wireless
Wireless Browser Applications
English Name for WAP V1.1 Communications Profile Required for Siebel Wireless Auto Registration Feature
The following issue is applicable for all non-American English locales. A Communications Profile with the English Name of
WAP V1.1 Profile must exist for the WAP V1.1 Communications Driver to enable the Siebel Wireless Auto Login Feature.
No Parameters are required for this Profile in order for the Auto Registration feature to function properly. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-72IL7T)
For Some Views, Siebel Wireless Displays Different Visibility than Other Siebel Applications
In some cases, Siebel Wireless applications may display different visibility for an object than is available to users in Siebel
applications. To change the visibility displayed in Siebel Wireless applications, modify the Visibility Applet and Visibility
Applet Type for the appropriate Siebel Wireless View as desired. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-6O536R)
Siebel Wireless Not Supported for Japanese and Korean Languages through XML Interface with Unix Operating
Systems
This is only applicable for the Japanese and Korean locales. Siebel Wireless is not supported for Japanese and Korean
languages through XML interface with Unix Operating Systems.(Not applicable to Siebel CRM or FINS CRM or Base MME
or FINS MME.) (12-B72KIN)

Errors Using Back and other Navigation Buttons with Some Wireless Browsers
When accessing Siebel Wireless applications with browsers that do not implement page caching, users may intermittently
receive errors indicating An error happened during restoring the context for this location or End of file error after clicking the
browser’s back button. Siebel Wireless applications provide a Main Menu link on error messages to allow users to continue.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-7M1XNK)
Digest Too Large Errors in Some Wireless Browsers
Some wireless gateways and browsers impose a limit on the number of bytes that may be sent to a wireless device in a WML
deck. When this limit is violated, users will encounter errors such as Digest Too Large or Entered Text Too Long, or the
browser may never finish downloading the deck. Siebel Wireless applications have been configured to minimize the chance
of these errors occurring, including returning only three records with each list by default. To address any such errors that
may occur, reduce the number of links or the amount of content included in Siebel Wireless Detail Views, or reduce the
number of links or records returned by Siebel Wireless Display Views. See configuring Siebel Wireless” in the Siebel
Wireless Administration Guide on the Siebel 7 Bookshelf for instructions on how to change the number of records returned
by Siebel Wireless lists. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6DXFS5)
Activity Description Text May Be Lost if Entered Before Activity Type when Entering New Activities
When entering new Activities into Siebel Wireless using some wireless browsers, text entered for Activity Description may
be lost if users select the type: link after entering this text. To avoid this problem, users should enter Activity Type first, and
then enter text for Activity Description. This problem may also occur for other configurations that include Pick Applets and
free-form text fields in New Entry Views. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
6DDA5Q)
Users Cannot Create Correspondence Requests Through XML Interface if Correspondence Templates Do Not
Have Supporting Documents in Siebel File System
If all Correspondence template records defined in the Siebel database do not reference existing template documents in the
Siebel File System, Siebel Wireless users will be unable to pick templates and create new Correspondence requests with
nonWML browsers supported by the Siebel XML Interface. Instead, they will receive an error message after attempting to
pick any template, including those for which existing document files have been defined in the File System. See the
Applications Administration Guide on the Siebel Bookshelf for additional details on creating Correspondence templates.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-A008HJ)
Host Name and Domain Name Must Be Included in Siebel Wireless URLs if Using Wireless In Conjunction With
Reports Server
When using Siebel Wireless in conjunction with the Siebel Reports Server, URLs used to access Siebel Wireless should
include the relevant host name and domain name. These URLs may be book marked in supporting browsers to expedite
access to Siebel Wireless. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6W9D3N)
CSMD Mobile Device Admin View included in Siebel Wireless Seed User Responsibilities
The CSMD Mobile Device Admin View is designed to allow Systems Administrators to view and update mobile device and
messaging address information for all employees, partners, and customers. This view has been included in the following
Siebel Wireless end-user seed responsibilities: Sales Representative – Wireless, Partner Sales Representative – Wireless, and
Registered Customer – Wireless. Remove the CSMD Mobile Device Admin View from these end-user responsibilities to
avoid giving end users access to other’s mobile device and messaging address information. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-6H9AIF)

Siebel Wireless Auto Login Feature Not Supported with WAP V1.1 alerts, if Enabled
The Siebel Wireless Auto Login feature is not supported with pushed WAP V1.1 alerts, if customers perform the additional
configuration required to enable WAP V1.1 alerts as described in the Siebel Wireless Administration Guide. After receiving
pushed WAP 1.1 alerts, users enter their user name and password into Siebel Wireless to view them. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6SDXWA)
HTML Attributes for Date Fields Should be Removed for non-English Versions of Wireless
The following issue is applicable for all nonAmerican English locales. Phone numbers input into Siebel Wireless are
automatically formatted for users, using format masks in the form of HTML Attributes that are applied to the relevant
controls in Siebel Tools. Specifically, phone number entries are forced to be numbers, except for the first digit, when input
using browsers that support these HTML attributes. These format masks are not localized to accommodate other date format
or phone number entry styles. The HTML Attributes affecting phone number fields may be removed by administrators to
support localized versions of Siebel Wireless and to avoid undesired formatting when entering phone numbers. See the
Siebel Tools Reference for details on modifying or removing HTML Attributes. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-64YO98)
HTML Attributes for Phone Numbers May be Removed for non-English Versions of Wireless
This is applicable for all nonAmerican English locales. Phone numbers input into Siebel Wireless are automatically
formatted for users, using format masks in the form of HTML Attributes that are applied to the relevant controls in Siebel
Tools. Specifically, phone number entries are forced to be numbers, except for the first digit, when input using browsers that
support these HTML attributes. These format masks are not localized to accommodate other date format or phone number
entry styles. The HTML Attributes affecting phone number fields may be removed by administrators to support localized
versions of Siebel Wireless to avoid undesired formatting when entering phone numbers. See the Siebel Tools Reference for
details on modifying or removing HTML Attributes. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-64YO98)
Default Country Should Be Removed from Service Locator Business Component to Enable Branch Locator
Searches for non-English Versions
This is applicable for all nonAmerican English locales. In the base configuration, the Siebel Self-Service Wireless Branch
Locator does not allow users to specify a country when performing searches. To allow Self-Service Wireless Branch Locator
searches for nonEnglish versions, no value should be specified for the Default CountryBusiness Component User Property of
the service Locator Business Component. Alternately, configure the ability for users to specify a Country when performing
searches using the Siebel Self-Service Wireless Branch Locator. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-6YHEZ4)
Mobile Screen
Anomalies When Sorting on Login Preference and Device Address in Siebel eChannel
When a user sorts multiple device records by Login Preference, or multiple device address records by Device Address in the
eWireless Mobile Device Personal Admin View in Siebel eChannel, an additional window will popup and the desired sort
may not take effect. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B41QGN)

Users May Not Auto Register Additional Devices if a Registered Device has a Priority of 6
If any device has already been assigned a Priority of 6 - Unranked for a particular user, the Siebel Wireless Auto Registration
feature will not register additional devices for that user. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-7487SR)

Length Limitation May Be Imposed on URLs for WAP Push
URLs pushed with WAP Push messages may be subject to length limitations, based on the characteristics of the wireless
gateway and browser through which the messages are pushed, or on restrictions imposed by wireless network operators.
Consult the relevant vendors and service providers to identify such limitations. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-6A3QSI)
WAP 1.2 Communications Driver not supported for nonEnglish Versions
This is applicable for all nonAmerican English locales. Sending WAP Push alerts through the WAP V1.2 Communications
Driver is not supported in the initial release of Siebel 7 for nonEnglish versions of Siebel eBusiness Applications. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-8Z6VOA)
Wireless Messaging Workflow Policy Condition Must Be Translated for Non-English Versions
This is applicable for all nonAmerican English locales. To make sure that Siebel Wireless Messaging Workflows function
properly in localized versions, the Value of the Activity Type parameter referenced in the Conditions for each Workflow
Action must be translated to the localized text for Wireless Message. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-9NGNDV)
Mobile Screen
English Search Specification Defined for Siebel Wireless Messaging Workflow Policies Displayed in the eWireless
Mobile Device Personal Admin Alert View
This is applicable for all nonAmerican English locales. Workflow policies are displayed to users in the eWireless Mobile
Device Personal Admin Alert View based on their Workflow Policy Group Name. A default search specification has been
defined to expose only Workflow Policies with the untranslated English names of sales and Svc Wireless Group, eChannel
Wireless Group, and eService Wireless Group in this view. To make sure that Workflow Policies are exposed in this view,
these Group Names must not be translated from English, or the search specification used to display Workflow policies in this
view must be modified. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5WGR7U)
Mobile Alerts Will Not Be Pushed to A User’s Device if the User Has Elected Not to Receive the Same Alert on
Another Device
If a user has created a record in the eWireless Mobile Device Personal Admin Alert View electing not to receive a particular
alert on a particular device, that alert will not be sent to any other devices defined for that user, even if the user has
specifically elected to receive the same alert on those other devices. Delete any negative entries for an alert in order to allow
users to receive the alert on other devices. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
8BPUGB)

Wireless Messaging Workflow Action Argument Parameter Must Be Translated for NonEnglish Versions
The following issue is applicable for all nonAmerican English locales. To make sure that Siebel Wireless Messaging
Workflows function properly in localized versions when users opt in and out of alerts using the eWireless Mobile Device
Personal Admin Alert View, the value of the WorkflowPolicyName parameter referenced in the Arguments for each
Workflow Action must be translated to exactly match the Name of the Workflow Policy to which each Action is related.
Currently, the names of the Workflow Policies are localized, but the value of the WorkflowPolicyNameparameters are set to
the non-localized name for the Workflow Policy. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-9JDC2G)
Siebel eAdvisor
Customize button from Orders Line Items applet does not invoke eAdvisor application
For items that are added to the quote using eAdvisor, and this quote is turned into an order, the Customize button will not
bring up eAdvisor for that item in Orders. Items that are added to the quote using eAdvisor should bring up eAdvisor, when
the Customized button is click for that item. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.)
(12-B82D0R)
After executing add to cart from eChannel Partner Portal in the Quotes view, eAdvisor will return you to the wrong
view
If you are running eAdvisor in the quotes view from eChannel Partner Portal and the user hits add to cart, the user will be
taken to the shopping cart view instead of the quotes view. Changes will be necessary for eChannel users who would like to
run eAdvisor through Quotes view from Siebel eChannel Partner Portal. Siebel eChannel Partner Portal offers users a way to
access the shopping cart and quotes within the same application. There is a defect in eAdvisor’s add to cart functionality
where it routes users to the shopping cart view after the user adds to the cart from the quote view. Administrator will need to
make the following repository changes through Siebel Tools to the Quote views so it routes the user to the proper Quote view
instead of the shopping cart view.
Applets that need to be changed:
Quote (SCW) Quote List Applet (SCW)
Quote (SCW) Quote List Applet for Customer (SCW)
Parameters in each applet that need to be added to the applet users properties:
ISSCDAHeaderBusCompName: The business component name for the shopping cart. The default value is Quote.
ISSCDAHeaderBusObjName: The business object name for the shopping cart. The default value is Catalog.
ISSCDAHeaderViewName: The view name the AddToCart function will switch to.This view name is also used after
exiting GotoConfigurator.
ISSCDAIntegrationObjName: The integration object name to be used by EAI to query, sync, or update to the
database. The default value is Quote.
ISSCDAListItemBusCompName: The business component at the item level. The default value is Quote Item.

ISSCDAListItemAttributeBusCompName: The business component name for item level attributes, like Quote Item
XAand so on.
ISSCDASSConfiguratorViewName: This view name the server-based eConfigurator will display.
Changing the applet user properties:
1. Find the applet in Siebel Tools
2. Expand the Applet Hierarchy to see the Applet User Prop.
3. Click on the Applet User Prop
4. You will see some of the user properties like:
5. Method|ShowCDA|Parameter 1 and Method|ShowCDA|Parameter 2 etc.
6. Change the line with name Method|ShowCDA|Parameter (#) and the value is End with a new value thatshould be
new a parameter as described above. Like ISSCDAHeaderBusCompName|Value|Quote
7. The last parameter must be terminated with an End record.
Applet User Properties
Update the following applet user properties as follows:

Method|ShowCDA|Parameter 1 QuoteId|Field|Id
ISSCDASSConfiguratorViewName|Value|Complex Product Runtime

Method|ShowCDA|Parameter 2
Instance View
Method|ShowCDA|Parameter 3 ISSCDAListItemAttributeBusCompName|Value|Quote Item XA
Method|ShowCDA|Parameter 4 ISSCDAHeaderBusObjName|Value|Quote
Method|ShowCDA|Parameter 5 ISSCDAHeaderBusCompName|Value|Quote
Method|ShowCDA|Parameter 6 ISSCDAIntegrationObjName|Value|Quote
Method|ShowCDA|Parameter 7 ISSCDAListItemBusCompName|Value|Quote Item
Method|ShowCDA|Parameter 8 ISSCDAHeaderViewName|Value|All Quote List View (SCW)
Method|ShowCDA|Parameter 9 End
Quote List Applet for Customer (SCW)

Method|ShowCDA|Parameter 1 QuoteId|Field|Id
ISSCDASSConfiguratorViewName|Value|Complex Product Runtime

Method|ShowCDA|Parameter 2
Instance View
Method|ShowCDA|Parameter 3 ISSCDAListItemAttributeBusCompName|Value|Quote Item XA
Method|ShowCDA|Parameter 4 ISSCDAHeaderBusObjName|Value|Quote

Method|ShowCDA|Parameter 5 ISSCDAHeaderBusCompName|Value|Quote
Method|ShowCDA|Parameter 6 ISSCDAIntegrationObjName|Value|Quote
Method|ShowCDA|Parameter 7 ISSCDAListItemBusCompName|Value|Quote Item
Method|ShowCDA|Parameter 8 ISSCDAHeaderViewName|Value|Quote List View (SCW)
Method|ShowCDA|Parameter 9 End
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AUB12S)
IE 6.0 browser defect causes eAdvisor to run improperly
Microsoft IE 6.0 has a defect (SRX020123604820) that corrupts the browser history causing eAdvisor to work incorrectly.
Microsoft has created a hot fix to resolve this issue - contact Microsoft support to obtain the hot fix. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-6Z5C07)
eAdvisor runtime behavior on Mac OS9
The runtime behavior of the following actions may not be as expected on a Mac OS9 client:
Link back to eAdvisor from Quotes
Launching eAdvisor from Get Advice buttons configured through Siebel Tools (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-9X187N)
Naming Default Project
The Default Project should be named exactly in case the database being used is case sensitive: DefaultProject. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-77QUZG)
Use of Post This API
Use Post This API to invoke a Business Service in conjunction with a switch View to change views and to avoid making
clients wait for a response from the server when none is coming. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-5ZTBER)
Configuring Get Advice button on any Applet
The Get Advice button may not work on applets not derived from CSSFrameListBase or CSSFrameBase classes. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6RDEE4)
Interactive Designer
Upgrading an eAdvisor project from 7.0.2 or 7.0.3 to 7.0.4
To update to the 7.0.4 eAdvisor engine for Interactive Designer projects, administrators will need to manually update the
engine file in the Siebel repository for each project. Perform the following steps to upgrade the engine files for an eAdvisor
project:
1. Backup the project you are planning to upgrade by using the Copy Project option under the applet menu.

2. With the project highlighted, delete the following engine files:
configenginecode.htm
pricing.htm
prodlist.htm
prodlistapi.js
prodlistui.htm
publicApi.js
3. A new parameter has been added to the app_config.js file. Update your app_config.js with the following
parameter:
// Calculate config tables not connected to MAIN
var APP_EVALUATE_ALL_TABLES = false;
Unless your using multivariable triggers, the value should be equal to false. After you have updated your app_config.js,
delete the app_config.js in the Siebel repository and insert the new app_config.js.
4. Insert the new engine files from the <SIEBEL_BUILD>\siebesvr\ISSTEMPL\enu\EngineSourceFiles directory for
server builds. For web dedicated client builds, retrieve the engine files from <SIEBEL
BUILD>\ISSTEMPL\enu\EngineSourceFiles directory. Use the New Record option under the applet menu to insert
the following new engine files – the directory of the engine files is in parentheses:
configenginecode.htm (cs)
pricing.htm (cs)
prodlist.htm (cs)
prodlistapi.js (cs)
prodlistui.htm (cs)
publicApi.js (cs)
triggersApi.js (cs)
triggersCode.htm (cs)
triggersEvents.js (jd)
app_config.js (custom)
5. Preview your project and validate that your application works correctly
6. Deploy your project. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B7D32R)
Product in linked table not recognized as child product of customizable product
The mapping of the customizable product is not being published correctly for linked tables. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-B7JGGR)

Application error after importing a project that was exported from a pre7.0.4 build
When importing a pre7.0.4 project from a 7.0.4 build, the import will run successfully, but the application will not be
formatted correctly. The workaround is as follows:
1. Edit the project XML file and remove all occurrences of:
<ListOfISSCDA_spcGeneric_spcProjects_undPosition>
<ListOfISSCDA_spcGeneric_spcPageset_undPosition>
2. Save the XML file
3. Reimport the project (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-8W9M37)
Maximum numbers of characters used in the Contents List noted field
In global deployments of Siebel Browser Based Applications, where double-byte data is used, the maximum number of
characters that can be entered in the Notes field of a Contents List is less then the 250 characters. This is the limit in the
English language deployments. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6DZVI8)
Use of previous and next buttons in project or pageset form applet in edit mode
Clicking on the next or previous buttons, available in the More Info tab, while editing a project or pageset results in the
cursor turning into an hourglass and remaining an hour glass even after the information for the next or previous record is
fetched. The work around for this problem is to switch to a different view within the Siebel application, and then come back
to the Interactive Designer views. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
6CKK4Z)
Browser times out when performing operations such as migrate and Import/Export
Depending on the size of the eAdvisor application, these processes can take a long time. If your browser times out, please
look at your Microsoft Windows Task Manager to see if the process is still running If it is still running, please allow the
process to be completed. The next time you invoke Siebel Interactive designer, you will see the results of the process. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5TGOJN)
Directory Structure letter case on UNIX Operating System
In UNIX Browser Based Application deployments, if the case of the project directories is altered manually to mixed or upper
case, the pagesets are not created during the migration process. The migration process expects the Browser Based Application
directories to be in lower case. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6WZ7T7)
Transact Server
Performance Problem with MS SQL 2000
In an environment with 300 concurrent users updating records, a database deadlock occurred in MS SQL 2000. Please ask
your DBA to finetune your database. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
5GO9KG)

Performance Problem with DB2
Transact Server stops the AddToCart function when there are more than 20 concurrent users. This is caused by a database
deadlock. Please ask your DBA to finetune your database. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-5Q5LNV)
Selecting Latin in WebLogic
When Latin1_general_bin collation is used in SQL Server, you will receive a WebLogic startup error. Please contact BEA
WebLogic support for the workaround. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
66PZEZ).
Siebel eAuction
Featured Auctions that are in Catalogs, which are inactive or have become inactive, will still show in the Featured Auctions
Applet. The Administrator will need to close and repost those auctions in active catalogs. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-B8REC8)
DB2/390 Maximum Cursor Size
DB2/390 has a default maxcursor setting equal to 48 records. This limits the number of records that can be displayed to 48
records in an applet. This setting can be changed through system settings or set to ignore the maxcursor setting entirely. The
setting can also be overridden on specific business components. The maxcursor setting limit may cause errors if a user tries
to act upon a record greater than the 48th record. However, if the system setting is changed to return a greater number of
records than 48, DB2/390 may drop connections if a large number of users are on the application. Siebel eAuction does not
recommend using DB2390. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B1QWAE)
Auction quotes for nonproduct auctions do not support drilldown in Siebel Sales
For auctions not created from products, quotes in Siebel Sales cannot be drilled down upon. The current drilldown behavior
is linked to the product detail, which is not applicable for nonproduct auctions. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-5R1UUN)
In the auction creation wizard Bid Decrement is labeled as Bid Increment for reverse auctions
In reverse auctions, the bidding amount decreases based on bid decrement. In the auction creation wizard page, the label for
bid decrement is actually bid increment. However, the number input into this field is used to specify bid decrement. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5SXSB2)
Auction detail screen does not include special fields for Dutch auction
The auction Detail screen for Dutch auction does not show special fields such as Terminal Price or the Time Between
Reductions. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-673TF0)
Dynamic close parameters are always available in the auction creation wizard
When the System Preference for DynamicCloseEnabled is set to false, dynamic close parameters are still available for entry
in the auction creation wizard. The lister can specify these parameters, but they have no effect because the system preference
is set to False. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-69XZVR)

Search results include expired auctions
When searching for an auction, search results include auctions with an expired autoclose date. Note that expired auctions that
were manually closed are not returned in search results. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-5088TI)
User sees positive Quantity Won when reserve price is not met
Because the reserve price is not disclosed to the end user, a successful bid shows up with a status of Winning and a positive
Quantity Won. However, unless the reserve price is met there is no order created. This is an intended feature of the bidding
logic. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-51MIJI)
Make eAuction Wizards faster by releasing SmartScripts
Release the eAuction SmartScripts by navigating to SmartScripts Administration/Scripts within Siebel Sales. Query for
Siebel eAuction scripts with eAuction*. Select the Release command from the script list applet menu. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6QU0H1)
Siebel eAuction as a stand-alone application
The Siebel eAuction license key includes views with applets that are not pertinent to Siebel eAuction in a stand-alone mode.
These applets apply when Siebel eAuction is deployed as a module to Siebel eSales. For stand-alone deployments, the views
containing these applets need to be configured. Refer to Siebel eAuction Guide for additional details on this topic. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-49WAZJ)
User Ratings can be deleted only at the database level
User ratings cannot be deleted from a graphical user interface. They can only be deleted directly at the database level. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-55VZ2Z)
Adding additional categories to auction created from products
Catalog and category information is automatically added when an auction is created from a product. To change this
information, the lister should edit the auction using the Update Auctions link. (Not applicable to Siebel CRM or FINS CRM
or Base MME or FINS MME.) (12-5SXSAT)
Siebel eBriefings
Viewing News Articles
Content in the Our Company in the News applet is not refreshed when user goes back to My Briefing after reading a news
article. To refresh the content, click on the Briefings screen tab. (Not applicable to Siebel CRM or FINS CRM or Base MME
or FINS MME.) (12-B81XWB)
Improving Performance in eBriefings
To improve performance in retrieving the Activity Briefing view, change the search specification in the Predefined Query to
the following:
1. Navigate to SiteMap > Application Administration > Predefined Queries
2. Query Objects column of list applet for ‘sI Employee” (this will retrieve the PDQ for My Briefing)

3. Remove "and [Created]>=(Today()-365)" from Contact.Search
4. Remove "and [Created]>=(Today()-1000)" from Account.Search
5. Change "[Row Status]= “Y”" to "[Row Status] <> “N”" from ContactSearch
6. Make the same change as in Step 5 for Account.Search
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B24T29)
Viewing News Articles
After reading news articles, use the Browser level Back button to return to the previous view. Do not use the Back arrow
within the Siebel application because it will go back two views. (Not applicable to Siebel CRM or FINS CRM or Base MME
or FINS MME.) (12-5RSJT5)
Using eBriefings in the eChannel Partner Portal
eBriefings is an option that can be added to the eChannel Partner Portal. However, some configuration in Siebel Tools is
required to allow drilldowns to detailed views for the Siebel data applets (for example, Opportunities) on the Account
Briefing and My Briefing pages. Specifically, add a drilldown object on the following applets to the corresponding
destination views:
Account Briefing
Applets Drilldown Views
ePortal Account Opportunity List Applet Opportunity Detail – Contacts View (SCW)
ePortal Account Service Request List Applet Service Request Detail View (SCW)
ePortal Account Contact List Applet Contact Detail View (SCW)
ePortal Account News Applet Account Detail – Contacts View (SCW)
ePortal Account Activity List Applet My Activity List View (SCW)
My Briefing
Applets Drilldown Views
ePortal Employee Opportunity List Applet Opportunity Detail – Contacts View (SCW)
ePortal Employee Service Request List Applet Service Request Detail View (SCW)
ePortal Employee Contact List Applet Contact Detail View (SCW)
ePortal Employee Account List Applet Account Detail – Contacts View (SCW) and Account Detail
– Contacts View
eCalendar Daily Applet Home Page eCalendar Detail View
Drilldowns to Service Agreements, Recommended Links, Expenses, Products and Literature on My Briefing and Account
Briefing are not supported. Drilldowns to Competing Product Comparisons on the Competitor Briefing are also not
supported at this time. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-7NF51B)
Creating Recommended Links and Web Clips
When creating recommended links, avoid choosing Window for the Web Display field of the Literature form in Document
Administration. This will prevent users from experiencing a Page Has Expired warning when they go back to the previous
view, since the recommended link will open in a new browser that can be closed. When creating Web clips, note that only
simple HTML is supported. For example, Web pages that have the HTML construct of <frameset> are not supported and

will not appear on the briefings. You can check the source code of the Web page by clicking on View in the browser menu
and then selecting Source from the dropdown menu. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-6F751D)
New Contacts on My Briefing
Once the user has viewed the contact information, it is no longer considered new and will not be displayed in the New
Contacts applet. The first record behaves differently, that is, it will continue to be displayed after viewing, but will not be
displayed the next time the user logs in. To make all the contacts continue to display after viewing, delete Row Status = Y
from the PDQ on the SI Employee business object. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-5MQK53)
Account Briefing
After you run an Account Briefing, only that account will appear in the All Accounts or My Accounts views. To refresh the
list of accounts in these views, click on a different view in the Show drop-down menu that does not have account information
(for example, All Competitors), and then return to the All Accounts or My Accounts views. This issue can also be avoided
by using the hyperlink threadbar on the Account Briefing to return to the previous view. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-6DC4KP)
The Account Briefing is not supported from the Opportunity screen. To view an Account Briefing, specify the account in the
Tracking Profile, and then drill down to get the Account Briefing. You may also click on an account from the Accounts
screen, and then click the Briefing view tab to access the account briefing. The DUNS number must be specified for the
account in order for any external content to appear on the briefing. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-6QJDGM)
Account Briefings can be accessed by choosing an account in the Accounts screen, and then clicking on the Briefing view
tab. However, if the last account record in the dataset is visible in the Account screen, then an incorrect account name
appears on the Account Briefing. The data in the Briefing will match the account selected, but the Briefing name will show
the name of the account at the top of the account list applet. This will also occur if a query is run and the last record is visible
in the list.
To avoid this problem, users can query on the exact account desired. When only one record is visible in the list, the correct
account name appears on the Briefing. Also, the problem will not occur if the last record in the dataset or query results is not
visible in the list. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-BCFX2K)
Siebel Partner Relationship Mgmt (eChannel Partner Manager)

Campaigns
Offers views are not available in Partner Manager
Currently, the Offers views are not available in Partner Manager. To give Marketing Managers the ability to create offers,
the following actions have to be performed in Siebel Tools:
1. Select the Application object and expand it
2. Expand the Screen Menu Item object
3. Query for the Offer Screen

4. Add Offers in the text column (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
AYHBVT)
Forecasting and Incentive Compensation
General Notes for Partner Compensation
See Release Notes on Siebel Incentive Compensation for additional notes. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-6SQT6J)
Other
Slow performance on Partner Administration, Partner Operations, and Partners Screens on Oracle Database
Server
When using an Oracle database, several views on the Partner Administration, Partner Operations, and Partners Screens may
perform slowly. The views include:
Channel Partner List View
Manager’s Channel Partner List View
Partner Operations List View
Partner Administration Partner Organization List View
This can be remedied by making the following changes in Siebel Tools:
1. Go to Siebel Tools
2. Select the Business Component object in the Object Explorer
3. Search for the Channel Partner business component
4. Change the Search Spec property of the Channel Partner business component from (Partner Flag = “Y”) to (Partner
Flag <>“N”)
5. Select the Pick List object in the Object Explorer
6. Search for the Channel Partner PickList
7. Change the Search Spec property to (Partner Flag = Y)
8. Recompile the objects (12-B62M2N)
Disabling local access to the All Partners Across Organizations view
The All Partners Across Organizations view should not be available on the mobile client. To disable local access, go to the
Application Administration screen, Views view. Find the All Partners Across Organizations view and uncheck the Local
Access flag. (12-77IPIS)

General Notes for Partner Training
See Release Notes on Siebel eTraining/Siebel eTraining Manager for additional notes. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-6SQT6P)
Some report data is truncated when the Reports Server is deployed on AIX or Solaris
Some fields in reports are truncated when the Reports Server is deployed on AIX or Solaris. This happens because Solaris
and AIX do not support text wrapping. (Not applicable to Siebel CRM or Base MME.) (12-84UR2Z)
When you log out of Partner Manager, the login page that is displayed is incorrect
When you choose File > Log Out in the Partner Manager application the page that is displayed is the Login page for Siebel
customer and partner applications, rather than the page typically used for employee applications. To change this, go the
Siebel Partner Manager application object in Siebel Tools. Change the Logoff Acknowledgement Web property to CC Login
Page (Login Only). (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-8VR3CJ)
The Challenge Question and Answer are not exposed in the Partner Manager application
The Challenge Question and Answer used for the Forgot Password process are not exposed in any employee application.
Therefore, channel managers, call center agents or other employees cannot view and change this data and there is no way for
users to change their own question and answer. To expose these fields in the User Administration > Users view, find the User
business component and add the following fields: Name = Challenge Question, Join = S_USER, Column =
CHALLENGE_QUESTION, Name = Challenge Answer, Join = S_USER, Column = CHALLENGE_ANSWER. Then, find
the User Admin Detail Applet and add controls for the same two fields. Finally, edit the web layout for this applet and add
the controls to the template and recompile the srf. (12-8VVS8Z)
Partner Administration
Adding the Parent Organization field to the Registered Partners view
Once the Parent Organization is selected for a partner organization, it can only be changed in the Group Administration
screen in the Organizations view. In order to provide the ability to change the parent organization from within the Partner
Administration screen, you must add the parent organization field to the Registered Partners view. Since the Partner
Organization Form Applet is shared among many views, you should add this column to the Partner Organization List
Applet.To copy the field to the applet:
1. In Siebel Tools, go to the Applet object and query for the Partner Administration Channel Partner List Applet and
the Partner Organization List Applet. Make sure that both projects are locked.
2. Select both applets (by using the CTRL key) and right click. Select Compare Objects and wait for the resulting
dialog box.
3. Expand the selected applet, the List object and then the List Column object.
4. Find the Parent Organization column in the Partner Administration Channel Partner List Applet and select it.
5. Click on the right arrow in order to copy that column over to the Partner Organization List Applet.
6. To map the list column to the Partner Organization List Applet:

a. Select the Partner Organization List Applet and select the Applet Web Template object.

a. Select the Edit List in the Applet Web Templates and in the Applet Web Template Items applet add a new
record with the following properties:
b. Name = Parent Organization,
c. Control = Parent Organization Name,
d. Item Identifier = 550.2.
e. Right click on the Edit record in the Applet Web Templates applet and select Edit Web Layout.
f. Add the Parent Organization column to the list applet.
g. Save and close the Web Layout.Note: See release note for 12-691FWL regarding the display name for this
column. (12-67AFZW)
Lower Case ASCII Names Only
This is only applicable for nonEnglish locales. When creating users, only use alphanumeric characters in the lower ASCII
characters. (12-9I7CVJ)
Parent Division field caption should be Parent Organization
In the Approved Partners view in the Partner Administration screen, when you click on the Register button you will see a
field called Parent Division. The caption of this field should be Parent Organization in order to more accurately reflect the
underlying field. To make this change:
1. Go to the Applet object in Siebel Tools and query for Partner Administration Channel Partner List Applet.
2. Click on the Control object for that applet and find the LabelParentDivision control.
3. Change the caption from Parent Division to Parent Organization. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-691FWL)
Adding Partner Territories field to the Channel Partner business component
Territories entered during registration do not get copied over to the Channel Partner business component when a prospective
partner is approved and a partner record is created. This is because the Territories multivalue field in the Channel Partner
business component is the same field used by the Account business component, and is populated using Assignment Manager.
In order to all for Territory values to be copied over to the Channel Partner business component, a new multivalue field
should be added to the Channel Partner business component that is based on the Partner Territory business component.
1. Create a new column in the table S_PRTNRAPP_REGN for PRTNR_ID
a. Start Siebel Tools with the “/extmode developer” parameter. Go to the Project object, find the New Table project
and lock the project in order to make changes to table repository definitions.
b. Navigate to the Table object and find the S_PRTNRAPP_REGN table. Go to the Column object and copy the
PRTNRAPPL_ID record. Rename the new column PRTNR_ID, and have the foreign key table point to
S_ORG_EXT.
c. Click the Apply button. If you’re connected to a local database, this will match up the table definitions with the
repository. If changes need to be made to the Server, check in the repository changes and follow the steps specified
in Siebel Tools Reference.
2 Go to the Business Component object in Siebel Tools. Find the Partner Contact business component. Navigate to the
Field object, and create a new record with the following properties:

Name = Channel Partner Id
Column = PRTNR_ID
3. Go to the Link object and create a new record with the following properties:
Name = Channel Partner/Partner Territory
Parent buscomp = Channel Partner
Child buscomp = Partner Territory
Destination Field = Channel Partner Id
4. Create a new column in the table S_ORG_EXT for PR_PRTNR_REGN_ID:
a. Start Siebel Tools with the “/extmode developer” parameter. Go to the Project object, find the New Table project
and lock the project in order to make changes to table repository definitions.
b. Navigate to the Table object and find the S_ORG_EXT table. Go to the Column object and copy the PR_ADDR_ID
record. Rename the new column PR_PRTNR_REGN_ID, and have the foreign key table point to
S_PRTNRAPP_REGN.
c. Click the Apply button. If you are connected to a local database, this will match up the table definitions with the
repository. If changes need to be made to the Server, check in the repository changes and follow the steps specified
in Siebel Tools Reference.
5. Navigate to the Business Component object in Tools and find the Channel Partner business component. Do the
following:
a. Go to the field object and create a new record with the following properties:
Name = Primary Partner Territory Id
Column = PR_PRTNR_REGN_ID
b. Go to the Multi Value Link object and create a new record with the same properties as the same multi value link in
the Prospect Partner business component with the following two changes:
Destination Link = Channel Partner/Partner Territory
Primary Id Field = Primary Partner Territory Id
c. Go to the multi-value field object and create a new record called Partner Territory. This should have the same
properties as the Territories field in the Prospect Partner business component.
6. Go to the Business Component object and find the Prospect Partner business component. Go to the Business Component
User Prop object and add a new record with the following properties:
Name = Promotion Map: Partner Territory-Territory
Value = Territories-Territory
7. To expose the Partner Territory field on the UI, copy the Territories control from the Prospect Partner Form Applet to an
applet based on the Channel Partner business component (for example, Channel Partner Form Applet). Change the name
and caption of the control from Territories to Partner Territory. Edit the layout of the applet to add the control to the UI.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5TGVW4)

Changing the field caption for consistency
In the Approved Partners view in the Partner Administration screen, the Account Team field is referred to as Account Team
on the New mode of the list applet, and Sales Team on the More Info applet. These can be made consistent by changing the
caption of one of the fields in Siebel Tools. To change the caption of the Account Team field:
1. Go to the Applet object in Siebel Tools and query for the Channel Partner Form Applet.
2. Go to the List Column object.
3. Find the Sales Rep field and change the Display Name to Sales Team from Account Team. (12-6141L3)
Partner Profile
Contacts must be removed from both Partner Contacts and Key Partner Contacts
On the Partners screen, if a Partner Contact is also a Key Partner Contact on the Partnership Contacts view tab and the
contact is disassociated from the Partner, the contact will still appear in the Key Partnership Contacts view. Users must also
disassociate the Contact from the Key Partner Contact view. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-4MUUYX)
Disabling the Copy Record feature in Partner Contacts
When you use the Copy Record function on the Contacts view in the Partners screen, you will get a message informing you
that the record is a duplicate. The Copy Record functionality should not be enabled on this applet. In order to disable the
Copy Record function, in Siebel Tools:
1. Go to the Applet object and find the Partner Contact List Applet.
2. Under Applet Method Menu Item object, add a new record with the following properties:
Command = Copy Record
Position =1
Menu Text = Copy Record
Suppress Menu Item =Y
(12-6VB9EV)
Partner Operations
Partner Ship-To Address
When you click the MVG icon in the Ship-To Address field in the More Info tab of the Partners screen, Bill-To/Ship-To
view, and try to enter a new Ship-To address, you will not be able to enter two address lines (Address Line 1 and Address
Line 2). As a work around, you can enter the new address under the Bill To Address section. It will then be available for
selection in the Ship To Address MVG pick applet as well. Alternatively, you can go through the following configuration
steps using Siebel Tools:
1. Select the Applet object type and query for the applet named Ship To Address Mvg Applet.
2. Expand the Applet object by clicking on the + sign and select List > List Column.

3. Under List Columns, copy the record named street Address, mapped to the field Street Address.
4. Change the field for the copied record to the field Street Address 2.
5. Enter Address Line 2 as the Display Name for the copied record .
6. Change the Display Name for the record with name street Address to Address Line 1.
7. Select the Applet Web Template object for the ship To Address Mvg Applet and select the Edit Web Template
under Applet Web Templates.
8. Right-click on the Edit record and select Edit Web Template.
9. Map the Address Line 2 column to the list applet through drag and drop.
10. Click Save.
11. Repeat the same steps for the Edit List Applet Web Template. (12-60AEAZ)
Siebel Partner Relationship Mgmt (eChannel Partner Portal)

Delegated Admin
Slow performance on Administration/Organization Administration view on Oracle Database Server with very large
number of positions
When using an Oracle database in a deployment with a very large number of positions, the Administration/Organization
Administration view under the Administration Screen in the Partner Portal may perform slowly. This can be remedied by
making the following changes in Siebel Tools. Go to the Applet Object in Siebel Tools. Search for the Position List Applet
(SCW). On the Search Spec property of the applet, add the following search specification: “[Name] >= “ “” (note: there is a
space between the single quotes). Finally, recompile the SRF. There are two indexes on the underlying table. The Oracle
Optimizer chooses the first index, which results in a sort that slows performance. By adding the search spec, the Optimizer
will pick the 2nd index, which does not result in a sort and thereby improves performance. (12-AZX98V)
Deleting users in delegated administration
If you delete a user in the Administration screen in eChannel Partner Portal, you will not be able to create a user with an
identical User Name to the deleted record. Entries in the LDAP directory are not deleted even when the database record is
deleted. (12-6CM4X4)
Forecasting and Incentive Compensation
The Forecast Explorer is not supported in the Partner Portal
The Forecast Explorer under the Forecast screen in Partner Portal is not supported in eChannel Partner Portal. Users can still
access all of the same functionality and data through the My Forecasts, My Team’s Forecasts, and All Forecasts views. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-BA8P36)

Opportunity Management
Sales Method Assist Mode is not available on Siebel eChannel Partner Portal Opportunity Form Applet (SCW)
When a user selects the sales stage for an opportunity under the More Info tab (Opportunity Form Applet (SCW)), the value
in the probability field does not automatically change to the associated probability. Therefore, the user should select the sales
stage for an opportunity in the Opportunity List Applet (SCW). To avoid confusion, customers can also use Siebel Tools to
remove the Sales Method, Sales Stage, and Probability controls from the Opportunity Form Applet (SCW) by taking the
following steps.
1. Complete the steps outlined in the release note ‘sales Method field is missing from the Opportunity List Applet
(SCW).
2. Go to the Applet object and locate the Opportunity Form Applet (SCW).
3. Go to the Applet > Control object and inactivate the SalesMethod, SalesStage, and Rep% controls.
4. Go to the Applet > Applet Web Template object and select the Base applet web template. Edit the web layout by
deleting the Sales Method, Sales Stage, and Probability % controls. Click on File > Save.
5. Repeat step 4 for the Edit applet Web template. (12-6ELKXX)
Other
Unable to see the currency code for new accounts and opportunities
When choosing a currency code for newly created accounts and opportunities, you may be unable to see the currency code on
the form applet before saving it. This can be remedied by making the following changes in Siebel Tools:
2. Select the Applet object in the Object Explorer
3. Search for the Account List Applet (SCW) applet
4. Find the Currency Code List Column
5. Change the HTML Type from ComboBox to Field
6. Recompile the objects (12-B7KZ8Z)
Cannot view charts when using an Mac OS based machine to access the Partner Portal
Charts are not supported when using a Mac OS-based machine to access the Partner Portal. Viewing a chart gives a
Microsoft JavaScript runtime error. (12-8UBF07, 12-9LVUEB)
Some report data is truncated when the Reports Server is deployed on AIX or Solaris
Some fields in reports are truncated when the Reports Server is deployed on AIX or Solaris. This happens because Solaris
and AIX do not support text wrapping. (Not applicable to Siebel CRM or Base MME.) (12-84UR2Z)

Enabling Catalog visibility on eMarketing Web Offers literature download view
For customers using Siebel CRM or Siebel MidMarket Edition of eMarketing Web Offers or eCampaigns Web Offers with
eChannel Partner Portal, the literature download view uses Organization visibility. This view can be converted to support
Catalog visibility and leverage Access Control by making a small change in Siebel Tools. Search for the Literature View
(eMarketing), under the View object in Siebel Tools, and change the Visibility Applet Type property from Organization to
Catalog (12-64SP7W)
Change Records on Partner Portal changes all records in the current query set
Choosing Change Records from the applet level menu on Partner Portal will apply the specified changes to all records in the
current query set. (12-6RNW0U)
Order Management
When creating an order, unable to enter Payment Terms
When creating new orders in Partner Portal, after selecting a payment term from the pop-up pick list, the Payment Term is
not entered into the order record. This can be remedied by making the following changes in Siebel Tools:
2. Select the Applet object in the Object Explorer
3. Search for the Order List Applet (SCW)
4. Navigate to List, List Columns in the Object Explorer
5. Locate the Payment Term record
6. Change the Show In List value to FALSE
7. Navigate to Applet, Applet Web Template
8. Edit Web Layout
9. Map the Payment Term list column to the Base and Edit List mode applet
(12-B7MZNI)
Registration
Company Site is a required field when Register Self, but not a required field when Register as company
In New User Registration, Company Site is a required field when you register yourself, but not when you register your
company. To make the Company Site not required for self registration, in Siebel Tools, find the User Registration Company
Information Form - Individual (SCW) applet. Go to the Applet User Prop property and find the user property with the name
Show Required 2 and the value CompanySite. Make the user property inactive. (Not applicable to Siebel CRM or FINS CRM
or Base MME or FINS MME.) (12-7FZGLR)

Service Management
Assigning a service request to the brand owner organization
By default, Siebel eChannel Partner Portal is set up in such a way that partners are not allowed to assign service requests to
the Brand Owner organization. If you want to change this behavior and allow partners to reassign a service request to the
Brand Owner organization or other partner organizations, you can do so by using Assignment Manager, or by giving your
partners the flexibility to select the organization they want to assign it to. You can do so through the following steps in
Siebel Tools:
1. Select the Applet object and query for the Service Request Detail Applet.
2. Expand the Applet object and select the Applet Web Template object. Expand the Applet Web Template object and
select the Applet Web Template Item object.
3. Under Applet Web Templates Items, query for the item with Name Organization.
4. In the Expression column, remove the expression, NOT Siebel eChannel, for the Organization item. As a result, the
Organization control will show on the Service Request Detail Applet.
5. Go back to the Applet object type and query for the Organization Pick Applet.
6. Under the Class column, change the class to CSSSWEFrameListVisibilityPick.
7. Expand the Applet object type and select the Applet User Prop object.
8. Under Applet User Properties, create a new record., and Iin the Name column, enter Override Visibility: Siebel
eChannel.
9. Under the Value column, enter the value All. This will show all organizations in the pick applet. However, all
Organization pick applets in Siebel eChannel will now show all organizations, across screens (that is, not only under
the Service screen). (12-6EY891)
Missing Save Button on Contact Picklist
When creating a Service Request on Partner Portal, the save button is missing from the contact picklist. This can be
remedied by:
1) Log in to Siebel Tools
2) Select Applet, find the "SR Contact Pick Applet"
3) Select the "Applet Web Template" -> Edit -> "Applet Web Template Item"
4) Find the record name = "WriteRecord".
5) In "Control" properties, change from blank to "WriteRecord". And "Item Identifier" = 152.
6) Compile srf and test it.
(12-FMEQ1T)

Siebel eChannel Partner Commerce
Checking out without a contact specified
Partners cannot proceed through the Checkout process on the Shopping Cart unless the shopping cart has a contact specified.
If a contact is not specified on the shopping cart, the user will be taken back to the Shopping Cart view. However, users are
not presented with a message informing them that they must specify a contact. An error message can be added by modifying
the eSales - Checkout Process in Siebel Workflow Administration. On the No branch of the Associated with a Contact?
decision step, add a step that calls the eSales - Display Error Process as a subprocess and passes a literal input argument Error
Message with the desired error message. Next, the user must be redirected to the shopping cart, Current Quote View
(eSales), with a User Interact step. The user interact step should then go to the End step. (12-BIUCTY)
Cannot use the Fulfill All button in Customer Orders Screen
The Fulfill All button is active when you drill down on a Service Order from the Customer Orders Screen. However, this
button is not a supported feature in eChannel Partner Portal. The status of the Service Order can be changed using the
picklist for the Service Order field. (12-9SGF3L)
Unable to check out of shopping cart when account does not have an address
When shopping on behalf of customers, users may encounter difficulty when attempting to check out of the shopping cart if
the account selected does not have an address. This can be addressed with the following modifications:
1. The first part of the fix is done in Tools. Open Tools and query for "Quote Account Shipping Form Applet (eSales)"
and go to the Applet Web Template Items for the edit mode of this applet. Create the following control mappings
(name can be same as the control name):
a. Control = AccountShipToCity, Item Identifier = 1310
b. Control = AccountShipToCountry, Item Identifier = 1314
c. Control = AccountShipToState, Item Identifier = 1311
d. Control = AccountShipToZip, Item Identifier = 1312
2. Find web template item AccountShipToCityStateZip and delete it. Do the same for UndoQuery-1.
3. Find the AccountShipToCountryDisplay web template item and delete that record.
4. Go to the controls for the applet and find AccountShipToStreetAddress control. Set Pick Applet to "Business
Address Pick Applet (eChannel)"
5. Make the following controls read only:
a. AccountShipToCity
b. AccountShipToCountry
c. AccountShipToState
d. AccountShipToStreetAddress2
e. AccountShipToZip
6. Compile the applet to your srf.
7. The next part of the fix is done through the application (in any application that has the Siebel Workflow
Administration screen such as CallCenter, Partner Manager, or Sales).
8. Go to Siebel Workflow Administration > Workflow Processes. Create a new workflow called "eSales - Save
Account Shipping Address" where Business Object is set to "Account".
9. Add new Start step called "Start".

10. Add new Siebel Operation called "Saving Account Address" and add a connector from "Start" to "Saving Account
Address".
11. Add new End step called "Start" and add a connector from "Saving Account Address" and "End". Also add an
exception from "Saving Account Address" to "End" and label it "Error Saving Address".
12. Add the following Process Properties to the workflow (where Data Type = String):
a. Name = City
b. Name = Country
c. Name = Postal Code
d. Name = State
e. Name = Street Address
f. Name = Street Address 2
13. Go to "Saving Account Address" step detail and set Operation = Insert and Business Component = Business
Address. And add the following fields to the field applet (where Type = Process Property):
a. Field Name = Account Id, Property Name = Object Id
b. Field Name = City, Property Name = City
c. Field Name = Country, Property Name = Country
d. Field Name = Postal Code, Property Name = Postal Code
e. Field Name = State, Property Name = State
f. Field Name = Street Address, Property Name = Street Address
g. Field Name = Street Address 2, Property Name = Street Address 2
14. Navigate to the All Processes tab and Activate the newly created workflow.
15. The final part of the fix involves modification of an existing workflow. Query for "eSales - Enter Shipping Details
Process". Find the latest version of the workflow and push the revise button. This will create a new version of the
workflow where you can put the modifications.
16. In branch step "Address Already Selected?", add another condition to the "yes" branch such that:
a. Compare to = Expression
b. Operation = One Must Match (Ignore Case)
c. Business Component Name = Quote
17. For the condition, create a new value: [Contact Id] = LoginId().
18. Create a new Siebel Operation step in the workflow and move the "No" branch from the "Use Account Primary
Address" branch to point to this new step. For the new step, set the following:
a. Name = # of Account Addresses
b. Operation = Query
c. Business Component = Business Address
19. Next set the search spec for the query operation by associating a field with the following values:
a. Field Name = Account Id
b. Type = Business Component
c. Business Component Name = Quote
d. Business Component Field = Account Id
20. Create a new Decision Point step called "Account Address Book Empty?" and add a connector from "# of Account
Addresses" to this new branch step. Add a branch from this new branch step to "Select Account Address View"
step. Label the branch "1 or more addresses".
21. Create a new User Interact step called "Account Shipping View" and add a branch between "Account Address Book
Empty?" and this new step. Add the label "Empty" to the branch.
22. Add a new Business Service step called "Set Flag" and add a connector between "Account Shipping View" step and
the "Set Flag" step and label it "Continue". Then add a connector between "Set Flag" and "Address Required?" step.

23. Go to the "Account Address Book Empty?" step details. For the "1 or more addresses" branch, make sure the Type
is set to Default. For the "Empty" branch set Type = Condition. Then in the Conditions applet add a new condition:
a. Compare to = Process Property
b. Operation = Is Null
c. Property Name = Siebel Operation Object Id
24. Go to the "Account Shipping View" step details and set the view to "Quote Account Shipping View (eSales)". For
the next step branch labeled "Continue", set the following:
a. Type = Condition
b. Event Object Type = Applet
c. Event = InvokeMethod
d. Event Object = Quote Account Shipping Form Applet (eSales)
e. Subevent = WriteRecord
25. Add a new process property to the workflow:
a. Name = No Account Address
b. Data Type = String
c. Default String = FALSE
26. Go to the "Set Flag" step details and set the Business Service to "Workflow Utilities" and the Method to "Return
Property Values". For this method, add a new Input Argument:
a. Input Argument = Flag
b. Type = Literal
c. Value = TRUE
And also add the following Output Argument to the method:
a. Property Name = No Account Address
b. Type = Output Argument
c. Output Argument = Flag
27. Add a new Decision Point step called "Save Account Address?" and move the "yes" branch from "Account User?"
to point to "Save Account Address?". Then create a new connector from "Save Account Address?" to "Set Primary
Account Address" and label it "No".
28. Add a new Sub Process step called "Save Account Shipping Address" and create a new branch from "Save Account
Address?" to the new step and label it "yes". Add a connector from "Save Account Shipping Address" to "Set
Primary Account Address".
29. Go to the "Save Account Address?" step details and make sure "no" branch type is Default. For "yes" branch make
the type to Condition and add condition to the branch:
a. Compare to = Process Property
b. Operation = One Must Match (Ignore Case)
c. Property Name = No Account Address
Then in the values applet add "TRUE".
30. Go to "Save Account Shipping Address" step details and set Subprocess to "eSales - Save Account Shipping
Address". Then add the following input arguments (where the type is set to Business Component, and Business
Component is set to Quote):
a. Subprocess Input = City, Business Component Field = Account Ship To City
b. Subprocess Input = Country, Business Component Field = Account Ship To Country
c. Subprocess Input = Object Id, Business Component Field = Account Id
d. Subprocess Input = Postal Code, Business Component Field = Account Ship To Postal Code
e. Subprocess Input = State, Business Component Field = Account Ship To State
f. Subprocess Input = Street Address, Business Component Field = Account Ship To Street Address
g. Subprocess Input = Street Address 2, Business Component Field = Account Ship To Street Address 2
31. Navigate to the All Processes tab and activate your new version of the workflow.
32. Restart the eChannelObjectManager for your workflow changes to take effect.

(12-EGFT07)
Views to add to Customer Quotes and Customer Orders screens
There are several views that customers may want to add to both the Customer Quotes screen and the Customer Orders screen.
These views allow users to enter Billing & Shipping information, Order Terms, and Payment Terms in Quote and Order child
tabs. Currently, this information can only be specified in the More Info applet on the Customer Quotes and Customer Orders
screens. In Siebel Tools, add the Quote Terms View and the Quote Bill To/Ship To View to the Quote Screen (SCW). Also,
add the Order Entry – Order Terms View (Sales), Order Entry – Payment View (Sales), Order Entry – Order Terms View,
and Order Entry – Payment View views to the Orders Detail Screen (SCW). Finally, add the views to the appropriate
responsibilities. (12-6FC03O)
Ending an eCollaboration session
When a customer, or an agent, clicks on an end session button in the co browser, an additional browser icon entitled Logout
will appear on your windows task bar. This window will not close on its own; however, the window does not affect your
current or future eCollaboration sessions. To close this browser, right click on the browser window icon in your windows
task bar, and select close. This will close the logout browser windows. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-B165X8)
Resynchronizing\ CoBrowsing Sessions Text
If a cobrowsing session no longer synchronizes the agent and caller browsers, both the caller and agent must use their refresh
buttons on their cobrowsers to resynchronize the session. Cobrowsers may lose synchronization if the agent and customer
simultaneously click on different links. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
8Z59YI)
Browser Support for Siebel eCollaboration
Siebel eCollaboration supports only the call back option for Netscape 4.7x, AOL browsers, and Internet Explorer browsers on
the Macintosh operating system. Siebel eCollaboration autodetects these customer browsers and presents only the call back
option on the Siebel eCollaboration customer request template. Cobrowsing, text chat, Voice over IP, and desktop
collaboration are not supported on Netscape 4.7x, AOL browsers, or Internet Explorer browsers on the Macintosh operating
system. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6ARDAF, 12-6DYICU, 12-
6DYICW, 12-6GPB80, 12-6AQMRH)
Initial CoBrowsing Page
When an eCollaboration session has been initiated, the initial page that appears in both cobrowsers is the last page the Web
customer was on prior to clicking on the Contact Us link. If a Web customer drilled down to the detail of a record (such as
the details of a service request or an order), the initial Web page that appears may be the detail of the first record of the list
applet in which the original record appears. In addition, when a Web customer has just logged into a SWE session because
the Web customer was timed out, the Web customer is taken to the drilldown the Web customer has performed. However, if
the Web customer then chooses to click on Contact Us, the initial Web page that appears in both cobrowsers may be the
home page of the application the customer was using, or the Contact Us page (Not applicable to Siebel CRM or FINS CRM
or Base MME or FINS MME.) (12-635YUR)

Follow-Me Browsing
If an agent and caller click on different links simultaneously, or within 0.5 seconds of each other, their followme browsing
session may diverge. The agent will be on a different page than the customer. To resynchronize the followme browsing
session, the caller and agent must click the refresh button on their cobrowsers. (Not applicable to Siebel CRM or FINS CRM
or Base MME or FINS MME.) (12-8Z59YI)
Netscape
Many eCollaboration features, such as web chat, followme browsing, and desktop collaboration, do not work using Netscape
browsers. In the Live Assistance Web page, there is code that prevents a user from selecting any collaborative features.
Callers will only be able to choose call back. It is expected that some Netscape browsers will work with the GA release of
eCollaboration. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6ARDAF, 12-6DYICU,
12-6DYICW, 12-6GPB80, 12-6AQMRH)
Viewing Documents in a CoBrowsing Session
To view attachments during a cobrowsing session, Siebel Systems recommends that the agent or customer save the file to
their local hard drive, launch the file in the appropriate application (for example, Microsoft Word), and use the desktop
collaboration mode to share the document with the other party. Launching the attachment during the cobrowsing session
may display unformatted text for one of the parties in the cobrowsing session. (Not applicable to Siebel CRM or FINS CRM
or Base MME or FINS MME.) (12-6EJJRB)
Network Address Translation
If you employ NAT (Network Address Translation), several changes have to be made manually to the eCollaboration Server
configuration.
1. Choose Start > Programs > Siebel eCollaboration > ecollab Server, and then select Configure Meeting Manager. This
opens the ptkgmgr.ini file. This file needs to contain several netmask and hnetmask entries to make sure that the
Meeting Manager communicates the proper IP address to clients based on the client’s network addresses.
In a NAT deployment example, the eCollaboration server is on a server that has two different IP addresses:
192.168.5.12, for machines in the DMZ and INSIDE the firewall, and 206.154.116.227 for machines OUTSIDE the
firewall. The corresponding lines in the ptkgmgr.ini file are as follows:
netmask = 192.168.5.0 255.255.255.0 192.168.5.12

netmask = 10.22.35.0 255.255.255.0 192.168.5.12
netmask = 0.0.0.0 0.0.0.0 206.154.116.227
These three lines say that machines with IP addresses of 192.168.5.xxx and 10.22.35.xxx will connect to the meeting
using IP 192.168.5.12, and everyone else will connect using IP 206.154.116.227.
hnetmask = 192.16.5.0 255.255.255.0 192.168.5.12

hnetmask = 10.22.35.0 255.255.255.0 192.168.5.12
hnetmask = 0.0.0.0 0.0.0.0 206.154.116.227
These three lines specify the same netmasks as above, for the purpose of telling clients where to connect to the HTTP
Gateway, if necessary.
Make sure there is a carriage return at the end of the ptkgmgr.ini file. Save the changes and close the file.

2. Choose Start > Programs>Siebel eCollaboration>ecollab Server, and then select Configure CSS Manager. This opens
the ptklmgr.ini file. There is a line in that file that starts:
ptkhttpd_opts =
At the end of that line, add the following flag:
-f<internal_ip_address>
This forces the HTTP Gateway to connect to the meeting using the internal IP address, even if the client thinks it wants
the external address.
For example, if your internal IP address is 192.168.5.12, change the line to:
ptkhttpd_opts = -I192.168.5.12 -p8329 -H192.168.5.12 -P80 -f192.168.5.12
Save the changes and close the file.
3. In addition,the server machine must be recognized by the same NAME for all users, internal and external.
4. Under the eCollaboration server install directory, using a text editor, open the file PictureTalk\ptk-
apps\java\htdocs.ptk\layout_applet_.
There is a line in that file that looks like:
hlines +="“http://<ip_address>:<http_gateway_port>/ptkgw/ecollab/ptk-apps/java/framewrk” "
Replace <ip_address> with <server_name>. Save the change and close the file.
5. Under the same directory, use a text editor to open the file framewrk.template.
There is a line in that file that looks like:
hserver_addr=<ip_address>
Change that line to:
hserver_addr=<server_name>
In the same file, near the bottom, there is a line that looks like:
user_icon=http://<ip_address>:<http_gateway_port>/ptkgw/ecollab/ptk-apps/java/bitmaps/coffeemug.bmp
Change that line to:
user_icon=http://<server_name>:<http_gateway_port>/ptkgw/ecollab/ptk-apps/java/bitmaps/coffeemug.bmp
Save the changes and close the file.
6. Restart the ecollab CSS Manager and ecollab Meeting Manager services. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-6NOC3N)

Siebel eConfigurator
Methods of business service "Cfg Object Broker" are listed under eConfigurator API for 7.0.x
In Bookshelf > Product Administration Guide > Technical Reference > eConfigurator API the methods "GetProdStruct" and
"DeltaQuote" are listed for the "Cfg Object Broker" business service. At the beginning of this section the following is
mentioned "This section is intended to summarize the available API to the Siebel eConfigurator, version 7.0.x. However, the
business service "Cfg Object Broker" is not available for 7.0.x - these methods are only available for 7.5.x. (12-GQGZEG)
Attribute value display
When administering display values of attributes, the expected Siebel formatted values should be entered, otherwise the
configurator may generate conflicts on instantiating saved configurations. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-B8VGH5)
Server Parameter: eProdCfgMaxNumbOfWorkerReuses
When using the snap shot mode for deploying configurator, the server parameter, eProdCfgMaxNumbOfWorkerReuses,
should normally be set to ten or less to avoid any memory accumulation. By default the value of the parameter is 10 (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B0G3HJ)
Behavior of Finish It during Validation
If any changes are made to the configuration after invoking Finish It during validation, it is possible that all selections made
to Finish It will be removed from the configuration (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-ATJEV3)
Different behaviors of Finish It in Quotes and Validation
Invoking Finish It during validation completes the configuration, but does not exit the configuration session. While
configuring in the Quote, Order or Agreement, invoking Finish It will complete the configuration and take the user back to
the Line Item (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-ASSVB3)
Adding rules on products with unbounded integer attributes
When rules are written on unbounded attributes (not associated with List of Values) of products, the performance would
improve if additional rules are written to bound the attribute. This is done by setting a lower and upper bound to the values
these attributes can take. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-ARYU23)
Verify button functionality
Invoking the Verify button in Quotes does not verify the validity of customizable products within the quote. (Not applicable
to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AHSGKY)
Import Class Product
Import full structure of a Class Product does not function. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-9R5RH0)

Delta Quote: Customizing Assets
Trying to customize an asset, that was created by copying an existing asset record, may fail to launch Configurator. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9W5IT3)
Constrain rules on AIX
On AIX, inserting a compound logic function to a constraint rule may generate errors. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-9XJ62V).
Attribute values for multiple instances of the same nested customizable product.
When an attribute value of a nested customizable product is selected, the second instance of the same product will pick up
that attribute value. A user will not be able to pick different values for the attribute. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-9Y9I83).
Errors when creating a new Pageset in the Pageset Detail Form Applet when locked checkbox is unchecked
When a new Pageset is created using Pageset Detail Form Applet, if the Locked checkbox is unchecked without saving the
newly created Pageset, error messages are displayed. When these error messages are displayed, choose Undo Record from
the JavaScript Applet menu to clear the errors. The Pageset is created and can be used to enter data. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-9XRE2B)
LOV deletion of an Attribute
Deleting an LOV value of an attribute will not immediately be reflected by its default value. (Not applicable to Siebel CRM
or FINS CRM or Base MME or FINS MME.) (12-9RSO4J)
Import of customizable product
When defining an attribute value within an LOV, using a different value for the languageindependent code and the value
itself, may generate some errors. These errors can occur when importing a customizable product, and when this product or
one of its component is part of a class to which this attribute is attached. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-9BS8L1)
Attribute inheritance
Renaming an attribute at a parent class will create a new attribute that will be inherited and will make the old attribute
definition incomplete at the child level. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
772VEF)
Using wrong data type
When you have defined a rule and assigned a value to an attribute, using an incorrect data type, such as string instead of time
or date, behavior at runtime may be adversely affected. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-67KIQZ)
Defaults remain unless maximum cardinality reached
Defaults specified for a relationship will remain as part of the solution until the maximum cardinality is reached. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9NFXAV)

Instances created automatically to satisfy constraints
In certain cases, rather than prevent the user from deselecting an item, additional instances of an item may be created when
the user removes the item. If this behavior is not desired, oftentimes, the logic can be expressed differently to achieve the
desired behavior (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-7JNZFS)
Attribute values changed automatically
In certain cases, if two attribute values are mutually exclusive, the engine may change one of these values so that the solution
is valid and a conflict is not generated. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
81AHFI)
Next button within Wizard product theme
When using a wizard product theme with only one UI group, the Next button at the top of the applet will be grayed out. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6QD67N)
Explanation Icon does not appear next to excluded item
An Explanation Icon does not appear next to an excluded item, but only next to a selected site. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-6LJI7M)
User might have to logout and login to see class name change affected
When the user changes the name of a class, a logoutand login action will be necessary to see the change reflected. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6HQNIB)
Setting Read-Only flag without setting a value.
Setting an empty dynamic attribute value within Product Administration to read-only is not prohibited. Nevertheless, it will
not have any effect on the run-time and will still let the end user select a value within the attribute domain. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6XMM3I)
Read Only flag needs to be checked manually for consistent behavior
When making an attribute read–only,it is recommended to check the flag manually when saving a value of a dynamic
attribute within product administration. Do not rely on the flag being check automatically. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-6W5FTM)
Adding a product as a component of itself.
It is not prohibited to add a product as a component of itself using the Product Designer view, even though this will not be
possible. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6UPER4)
Script Designer Language selection.
When selecting a root product within Script Designer, the language selected may revert to Blank. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-6QDXJ2)

Set Initial Attribute and Provide rule are available only for Root product
The rule template Set Initial Attribute and Provide can only apply to the root product, and not to an attribute of a relationship
within a customizable product. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6M6UMZ)
Excluded Items in Netscape Browser
The excluded items or attribute values are not grayed out in Netscape browsers, although the exclude function still works.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-8GIF9F)
User will have to refresh workspace to see new translations entered
If the user creates new translations for descriptions, the workspace will have to be refreshed in order to see the changes
reflected in the runtime view. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-82JAAR)
Enabling Multilingual Data for Attributes
After enabling multilingual data for the attribute name, the attribute definition must be updated for it to be displayed at run
time. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-67SKRN)
Copy a Class
When the user copies a class, the attributes of the class don’t get copied. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-86WO4A)
Hot Keys in UI Designer View
Most keyboard hot keys, for example Ctrl-S for Save Record, do not work in Product UI Designer and UI Property Designer
view. Use the menu items or buttons instead. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.)
(12-8G7ZYU)
Mutual Requires Rule might be missing advanced attribute value selection
The Mutual Require Rule might be missing the Advanced Attribute value to allow users to fill in: [an attribute] [=] [a value]
(for [all] items). (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-7G3XMZ)
Global Paths
Global Paths are not supported in the initial Siebel 7 release. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-81FLDJ)
Delta Quote: Creating Customizable Assets
Customizable Assets should be created only from the Customizable Assets View. Trying to create Customizable Assets from
All Assets View may result in errors and unexpected behavior, since it is not supported. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-874ILN)

Interactive Designer
Errors when creating a new Pageset in the Pageset Detail Form Applet and unlocking the pageset
When a new Pageset is created using Pageset Detail Form Applet, if the Locked checkbox is unchecked without saving the
newly created Pageset, error messages are displayed. To clear the errors, choose Undo Record from the JavaScript Applet
menu. The Pageset is created and can be used to enter data. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-9XRE2B)
Use of previous and next buttons in project or pageset form applet in edit mode
Clicking on next or previous buttons available in the More Info tab, while editing a project or pageset, results in the cursor
turning into an hourglass. The cursor remains as an hourglass even after the information for the next or previous record is
fetched. The work around is to switch to a different view within the Siebel application and then come back to the Interactive
Designer views. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6CKK4Z)
Setup for Preview and Deploy operations in Heterogeneous Environments
In Environments where the Application Server and Web Server are on different operating systems, setting up the
WebClientSiteDir variable alone is not sufficient for the Deploy and Preview operations to work. System Administrators are
expected to use third-party tools and processes to make Preview and Deploy functionalities work. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-69E1WS)
Deleting an existing project and creating another project with the same name
When an existing project is deleted and the user clicks on Migrate, Deploy, Preview, or Validate without clicking on any
other control in an applet, the deleted project record still remains in the database. If the user attempts to create or migrate a
project with the same name, an error is displayed that the project name already exists. The work around is to click on a
control other than the buttons. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5S34TZ)
Browser Times out when performing operations such as migrate and Import/Export
Depending on the size of the eAdvisor application, these processes can take a long time. If your browser times out, look at
your the Microsoft Windows Task Manager to see if the process is still running. If it is still running, allow the process to be
completed. The next time you invoke Siebel Interactive Designer, you will see the results of the process. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5TGOJN)
Directory Structure letter case on UNIX Operating System
In UNIX Browser Based Application deployments, if the case of the project directories is altered manually to mixed or upper
case, the pagesets are not created during the migration process. The migration process expects the Browser Based Application
directories to be in lower case. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6WZ7T7)
Maximum numbers of characters used in the Contents List noted field
In global deployments of Siebel Browser Based Applications, where double-byte data is used, the maximum number of
characters that can be entered in the Notes field of a Contents List is less than the 250-character limit in English language
deployments. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6DZVI8)


Browser Times out when performing operations such as Migrate and Import/Export
Depending on the size of the eAdvisor application, these processes can take a long time. If your browser times out, look at
your Microsoft Windows Task Manager to see if the process is still running. If it is still running, allow the process to be
completed. The next time you invoke Siebel Interactive Designer, you will see the results of the process. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5TGOJN)

Registration Note
To implement the work around, perform the following steps:
1. In Siebel Tools, from Object Explorer go to Workflow Policy Object and select eEvents Event Registration record.
2. Go to Workflow Policy Component and select eEvents Details record.
3. Go to Workflow Policy Component Column and add new a record by specifying Training Class Waiting List Count
as column. In the alias specify Event Waitlist Count (optional). (If they don’t specify alias, then while using it will
appear as Training Class Waiting List Count.)
4. In Siebel Marketing Application, Siebel Workflow Admin Screen - Workflow Policies View, select eEvents Event
Waitlisted Email, and add the condition Event Waitlist Count >1. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-9W5GVN)
Registration Note
If the Administrator selects the Remember my User Id and Password option during login to any of the enterprise applications
(for exampleMarketing, Sales, Call Center) and then accesses the application in later session, the administrator will be taken
to the Application home page without asking for the Username and Password.
If the administrator tries to register users during this session (eEvents: Events > Registrations, eTraining: Course >Add
Enrollments, Class-Add Enrollments), the user will experience an error during Check-out process stating, "View Login
View" not accessible.To avoid this issue, the administrator should login explicitly to perform admin enrollments. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9XQ1RF)
Registration Note
In Siebel Tools, add Workflow Policy column Training Class Waiting List Count to Workflow Policy Object eEvent Event
Registration > Workflow Policy Component eEvents Details with alias name : Event Waitlist Count. In Siebel Marketing
Application, Siebel Workflow Admin Screen - Workflow Policies View, select eEvents Event Waitlisted Email, add the
condition Event Waitlist Count > 1. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
9W5GVN)

Activating Session Calendar View
In order to view the Session Calendar details for a specific event, the user should explicitly type the start date of the event or
the first session into the date field in the Session Calendar view. (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-528A6N)
Registration Note
A user cannot register more than once for an event from the Web site; however, a user may register once from the Web site
and again from the employee application’s Administrative Registration View. (Not applicable to Siebel CRM or FINS CRM
or Base MME or FINS MME.) (12-5YAFMZ)
Siebel eMail Response

When sending emails using Send Email/Lotus Notes integration, users may not be able to re-login into Lotus
Notes
This is a known defect with IBM when working with Lotus Notes 5.0.5. A defect has been filed with IBM: SPR #
JPOS4K5NW5 reports the problem of leftover processes preventing restart of Notes R5. There are two
workarounds available:
1. Go to http://www.cassetica.com/cassetica/notesmedic.asp and run the the NotesMedic program
2. Use nsd -kill and that will terminate all Notes processes associated with a data directory and cleanup files.
Nsd must be run from the data directory or with -ini <path_to_ini> file.
(12-EFXS5V)
When the user sends an email using F9 from the Service screen, an activity record is not created
When using Send Email with Lotus Notes integration, an activity record does not get created. This behavior only occurs
when the user preference is set to HTML and the user sends an email from the Service screen. (12-BMY9MT)
A warning message appears every time the user selects Send when executing Send Email on ActiveX Thin
Client.
When using Send Email with Lotus Notes integration, a security warning message will appear: "Authenticode signature not
found" or an ActiveX Thin Client warning message will appear: "An Active X control on this page might be unsafe to
interact with other parts of the page. Do you want to allow this interaction?" These error messages will appear every time the
user clicks the Send button to send the message. The user should click “Yes” to all warning messages. (12-BMY9MD)
Two attachment records are saved in Siebel when integrating Send Email with Lotus Notes.
When using Send Email with Lotus Notes integration, a duplicate attachment record may be created and stored in Siebel.
This behavior may occur when the user selects the Attachment tab for any screen, such as Activities and then clicks the F9
key. The attached record in the email should be received by the recipient without any problems. (12-BN6SVE)
Email addresses and aliases in To and From fields are cleared when clicking Send button using Send Email from
the Service screen when Siebel Server is running on AIX or Solaris
When Send Email functionality is used from the Service screen, the To and From fields may be cleared out once the Send
button is pressed. The user may see the following error message, The selected record has been modified by another user

since it was retrieved. Please continue. The work around is to click OK on the error message and reenter the addresses or
aliases in the To and From fields on the Send Email applet. This only occurs when running the Siebel Server on AIX or
Solaris. (Not applicable to Siebel CRM or Base MME) (12-BDRQ2S)
Ignore HTML Tags user preference option does not work
When the spelling user preference Ignore HTML Tag is set, spell checker does not ignore text contained within HTML tags.
(12-B90A9E)
Doublebyte character set email messages will show non-displayable characters in the Inbound Communication
view
When receiving double-byte character set (DBCS) email messages, the message text in the Inbound Communications view
will show non-displayable characters. The work around is available on Siebel Support Web. (Not applicable to Siebel CRM
or FINS CRM or Base MME or FINS MME.) (12-B7OE0F)
Email addresses and aliases in To and From fields are cleared when clicking Send button using Send Email from
the Service screen when Siebel Server is running on AIX or Solaris
When Send Email functionality is used from the Service screen, the To and From fields may be cleared out once the Send
button is pressed. The user may see the following error message, The selected record has been modified by another user
since it was retrieved. Please continue. The work around is to click OK on the error message and reenter the addresses or
aliases in the To and From fields on the Send Email applet. This only occurs when running the Siebel Server on AIX or
Solaris. (Not applicable to Siebel CRM or Base MME.) (12-B6WQSN)
User must reset the cursor for the next formatting action to take effect
When an eMail Response user is working with HTML formatting controls, he will need to reposition the cursor should he
desire to use more than one formatting feature. For example, if the cursor is on a specific area of text and the text is already
underlined, the user will have to reset the cursor on the same text is he wishes to add additional formatting to the text, such as
bold or italics. (12-B3ANHK)
When replying to an HTML email with the user preference set to Plain Text, the original message will contain
&nbsp at the end of each paragraph
When the user preference is Plain Text and the email sent is HTML, the original HTML message that gets attached to the
outgoing message will contain &nbsp at the end of each paragraph. The &nbsp characters can be removed by the user from
the end of each paragraph. (12-B23CWY)
Plain text email messages are missing carriage returns when Plain Text User Preference is set
Incoming email messages received by eMail Response will not include carriage returns within the body of the email when the
Plain Text user preference is defined for eMail Response. Incoming emails containing multiple paragraphs separated by
carriage returns will appear as single paragraph. A work around that allows incoming emails to properly display carriage
returns is available on Siebel Support Web. (12-B23CWB)
Clear HTML Tags button clears HTML from message body applet
The Clear HTML Tags button clears HTML from message body applet. Any HTML tags removed from the message body
applet will continue to be included within the body of the mail sent to the Communications Server for outbound processing.
(12-B3A8L1)

Unable to set eMail Response Default Message format
Values for the eMail Response Default Message Format user preference are missing from the pick list field. To provide the
values, configure a list of values for COMM_EMAIL_FORMAT that contain the following display values: HTML and Plain
Text. Detailed instructions for adding the list of values are provided on Siebel Support Web. (12-ASWXLR)
Selecting a template when using Send Email may cause the application to exit abnormally when running the
Siebel Server on Solaris
When working with Siebel Send Email functionality (F9), the application may exit abnormally once the user selects a
template from the Body field. To correct this abnormal behavior, restart the Call Center Object Manager. (Fixed in 7.0.4.10)
(12-B9HO3N)
Template Administration editor is plain text only
In order to format HTML templates you must use a thirdparty HTML editing tool or HTML editor to build the HTML
template text and formatting. Once the formatting and text are complete, copy the source HTML code from the thirdparty
tool to the Template Text field under the Template Administration View in Siebel Software. (12-AUOLOJ)
Provides the ability to use HTML control features when creating templates
The ability to create Siebel templates using HTML control features is not available. The work around is to create an HTML
file with the desired formatting using a third party HTML editor. The user can copy the HTML source from the third party
application and paste it into the Template Text field. The user will be able to select the template and view the desired
formatting on the template text once the template is inserted into the body of the outgoing email. (12-ANNUFQ)
Siebel sample database is missing the XML files used for testing workflow in simulation mode
The XML files used for running eMail Response workflow processes in simulation mode are missing from the Call Center
Demo application that uses the sample database. The necessary XML files are available from the SupportWeb. (12-ABTF26)
Siebel eMail Response may process email messages more than once resulting in duplicate activity records for a
single email
If the email server or the Siebel server exits abnormally, a duplicate activity record may be created in the Siebel application
for the email message stored in the mail server when the mail server or Siebel server process were interrupted. To protect
against this potential behavior, set the Communication Inbound Manager polling interval parameter to a value smaller than
the mail server timeout value. (12-AX5CQB)
Selecting a closing Template does not display as a new paragraph
When selecting a new closing template in the eMail Response screen, the application will not start a new paragraph. The user
will have to put the cursor at the beginning of the closing template text and press the Enter key to have the closing template
display as a new paragraph. (12-ASZVE5)
Send Email window displays text texthtml1 in the attachment field when working with Siebel Mobile Web client
application
When working in the Siebel Mobile web client application, the Send Email window will display an attachment with the name
of texthtml1, even though the user has not attached any documents to the outgoing message. The recipient of the email
message will not receive the attachment with the name of texthtml1. (12-AS1204)

Reply to an HTML message should be Plain Text when user preference is set to Plain Text
If the user preference is set to Plain Text, original HTML message contained in the replied email will be displayed as HTML
and not Plain Text. (12-AOPOB7)
eMail Response Default Message Format user preference does not contain values in the pick list field.
Values for the eMail Response Default Message Format user preference are missing from the pick list field. To provide the
values, configure a list of values that contain the following values: HTML and Plain Text. (12-AMJ3RF)
Prefix re: is hard coded in the eMail Response - Response WF
When replying to an email message the subject field will display the prefix re. This prefix is hard coded. To display the re in
different languages to support global customers processing email messages in different languages, the eMail Response –
Response workflow process should be modified. (12-AK4GEC)
Email messages sent from Internet email applications will display &NBSP in the body of the mail
When Rich Text Formatting is turnedon and a message is sent from an Internet email application, the email body will contain
&NBSP characters. (12-AK0353)
Missing Send Email Default Message Format in Outbound Communication User Preference
Send Email Default Message Format field in Outbound Communication User Preference is missing. To set the message
formatting for Send Email functionality use eMail Response Message Formatting field instead. Setting the message
formatting under eMail Response will take effect for both eMail Response and Send Email. (12-AIGPZN)
Subject line does not get displayed when replying to a message processed by the eMail Response – Process
Service Request workflow.
When replying to an email message processed by the eMail Response – Process Service Request workflow, the subject line
does not contain the original subject header. Only re: will be displayed in the subject line of the replied message. (12-
9ZA3QV)
Closing Spell Checker in Send Mail
When using Send Email (F9), closing the Spell Check window by clicking the X button in the upper right corner causes not
only the Spell Check window to close, but the Send Email (F9) window to close as well. (12-9LL4EB)
Manually Associating Contacts with Incoming Emails using the Communications Detail – Response View
When replying to an email and adding a new contact or associating the email to an existing contact in the Communications
Detail – Response View, the contact last name and first name does not persist when viewing that same email in the
Communications List View. However, the contact name associated with the email can still be viewed in the Communications
Detail – Response View. (12-9HGQIG)
Browse View for Templates
The Templates applet in the Browse View displays the description field from the All Templates view. (12-9HGQGU)

Send Email using Email Aliases as Recipients
Using Send Email (F9) with aliases in the recipient fields (for example, jsmith instead of jsmith@xyz.com), results in
recipient values not being displayed in the email when it is received by each of the parties to whom it was sent. Use the full
email address and domain name (for example, jsmith@xyz.com) to make sure that the full list of recipients is listed on all
emails sent using Send Email (F9). (12-925ISJ)
Querying on to, CC, and BCC in Address Book is not supported.
Querying on to, CC, and BCC in Address Book is not supported. (12-8G9UD6)
Smart Answer Log Error Message when stopping Siebel Server
Stopping Siebel Server while Smart Answer Manager server component is running will cause an error message to be
generated in the Smart Answer log file. These error messages will not disrupt Smart Answer functionality and Smart Answer
will continue to work correctly when Siebel Server is restarted. (Not applicable to Siebel CRM or FINS CRM or Base MME
or FINS MME.) (12-8N5DF7)
Setting Always Check Spelling Before Sending user preference for Send Email
The user preference Always Check Spelling Before Sending is not available for Send Email (F9). To perform spell checking
on messages sent using Send Email, click on the Check Spelling button. (12-66S23V)
Fail to receive incoming attachment in Process Service Request using the keyword Update
When submitting an update to an existing service request record using the Update keyword, the application will not update
the service request record with the newly sent email information. To correct this behavior, the eMail Response – Process
Service Request workflow will have to be modified. Refer to Siebel Support Web for an alert that provides detailed
instructions on how to modify the workflow. (12-9X02CF)
Smart Answer catalog import
The Siebel Smart Answer catalog import must be done from a connected client. Catalog import cannot be performed from a
mobile client. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-7F3NMB)
Implementing Email Routing and Queuing with Assignment Manager
Siebel eMail Response includes an out-of-the-box Assignment Manager rule called eMail Response Agent Assignment. This
rule can be used to assign incoming emails that are entered into the Siebel database as activity records to various Siebel users
using Assignment Manager. To use this rule to assign email activities to Siebel users, make the following modifications prior
to releasing the rule: Change Assignees from Rule to One, Random; Update the Expiration field to null; Change Inclusion
for all three Criteria to Include;and Required to Never. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-6SIDGL)
Routing Emails to Last Respondent
To allow the eMail Response Send to Owner route to route subsequent email replies from customers to the contact center
agent who responded to their initial email inquiry, the following escalation rule needs to be added as the first escalation step
for the route: Escalation Name = ‘send to Owner”; Time Out = “15”. The Escalation Rules for this step should be defined as
follows: Skill Name = “AgentID”; Relation set to “=”; and Skill Item = “%CustSvcRepId%”. You also need to change the
Time Out for the previously existing ‘tier One” Escalation step to 15 minutes after adding the new escalation step and change

the order of the previously existing escalation steps from 1, 2, 3, and 4 to 2, 3, 4, and 5 respectively. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-9ATOOJ)
eMail Response Route Email Workflow Process
The eMail Response Route Email workflow process is designed to forward incoming emails to Siebel UQ for real time
routing to agents. When using the Route to Owner UQ route provided with eMail Response in cases where customers send
emails in response to a previous reply from a contact center agent, the Route Email workflow process provides input
arguments, including Agent ID. This Agent ID information is used by the Route to Owner Route to route the email. When
processing emails as Service Requests, the Route Email workflow process correctly sends this Agent ID information to UQ.
However, when processing emails as Activities, it is necessary to create an additional operation within the Route Email
workflow process that routes Activity Owner ID to Siebel UQ. (Not applicable to Siebel CRM or FINS CRM or Base MME
or FINS MME.) (12-8WAR29)
Status keyword in Process Service Request workflow will only return Service Request information by default
When a user sends an email with the status keyword in the email subject, eMail Response will reply with an email that
contains service request information. Activities associated with the service request record are not included as part of the
email response. To allow activities associated with service requests to be returned as part of the outgoing email response,
modify the eMail Response - SR Status template as follows: Set the Iteration Child BC field to Action and check the
Substitute Values and Message Body fields. (12-9KGSCV)
SQL Error in Communications Inbound Manager Log File
The Communications Inbound Manager log files may occasionally list a SQL error similar to the following DB2 example,
sQLError: sqlstate 42S22: [IBM][CLI Driver][DB2/6000] SQL0206N ‘SIEBEL.S_PARTY.ROW_ID" is not valid in the
context where it is used. SQLSTATE=42703. This error message indicates an issue that is harmless to customer data. No
action is necessary to address this issue. The messages may be ignored. (12-9B7R3L)
Siebel eOrder
Order Total Refresh issue
1. Start up Siebel Tools
2. Choose Applet item in the Object Explorer
3. Search for the applet named Order Entry - Order SubTotal Form Applet
4. Expand the Applet item in the Object Explorer
5. Choose Control item under Applet in the Object Explorer
6. Create a new control with the following attributes
Name : BRefreshRecord
Caption : Refresh
HTML Type : MiniButton

Method Invoked : RefreshRecord
7. Save the control by advancing to the next record
8. Select Applet Web Template item under the Applet item in the Object Explorer
9. Select the record that is named Edit
10. Right Click and select the Edit Web Layout menu item
11. This will bring up the controls window and the weblayout window. If the controls window does not show up, right
click the mouse button and select View Controls Window"
12. Select the BRefreshRecord control in the controls window, drag it and place it into one of the colored boxes marked
with an x in the Web Layout window.
13. Select tools menu from the top level menu and select Compile Projects to compile the changes and generate a new
.srf file (12-B93NS8)
Add New Contacts to the Order Header
Users cannot create and add new contacts to the order from the order header contacts pop-up due to a grayed-out save button.
The work around is that an implicit save from the pop-up applet allows the user to close the window and search for the newly
created contact. This will add the new contact to the order". (12-B47CY8)
Directory Out of Date Error
Users will see the following error message when adding Zip Codes on an Order, Error occurred in initializing data cleansing.
[DIRECTORY OUT OF DATE. The specified ZIP+4 directory has expired.]. The user can click on OK to proceed". (12-
B47CXN)
Orders Merge is not available in Siebel 7.0
Merge Order capabilities are not available in Siebel 7.0. (12-6RX1FO)
Siebel ePricer
Enforcing Minimum and Maximum Price When Providing Manual Discounts
1. In order to allow the Check Min and Max Manual Discount functionality, the user needs to set the value of the user
property Check Minimum and Maximum Price to Y on the line item Buscomp.
2. In Siebel Tools, choose Business Service from the Object Explorer.
3. Query for Pricing Manager. Expand on the Object Explorer. Query for GetProductListPrice on Business Service
Method.
4. Create two records in Business Service Method Arg.

Name Data Type Type Storage Type

Min Sale Price String Output Property
Max Sale Price String Output Property
5. Go Back to Business Service, right click on Pricing Manager to bring up the menu, and choose Edit Server Scripts.
6. Choose service -> Service_InvokeMethod.

7. Paste the Script from script - Check Min and Max for manual Discount.txt on the right windows as indicated above.
function Service_InvokeMethod (MethodName, Inputs, Outputs)
{
if (MethodName == "GetProductListPrice")
{var currentPrice;
var minPrice = -Number.MAX_VALUE;
var maxPrice = Number.MAX_VALUE;
currentPrice = Outputs.GetProperty("Current Price");
if(currentPrice == "")
{
Outputs.SetProperty ("Min Sale Price", minPrice);
Outputs.SetProperty ("Max Sale Price", maxPrice);
}
}
}
8. Save and Compile the project Pricer. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.)
(12-A3I3VV)

Deals and Checkout
When you enter eSales as an anonymous user, the prices you see come from the default price list. During your eSales
session, you could login as another user with a different price list and potentially different products. If a product is on one
price list and not another, you will see inconsistent behavior. For example, you may be able to select a deal and checkout as
an anonymous user. But when you login as another user (with a different associated price list) and select the same deal, you
will get an error upon checkout, all within the same eSales session (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-6SDX4B)
Promoted Products and Deals
In Account Promotion Administration, you can create identical products with identical deals. This flexibility is supported in
the data model. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9SDC9F)
Changing organizations for a price list
Entering an organization name instead of picking from an existing list will attempt to create a new organization. The work
around is to click the icon to pop-up the edit list and change the organization in the edit list. (Not applicable to Siebel CRM
or FINS CRM or Base MME or FINS MME.) (12-8LLI8F)
Service Price Details
When defining service price details in the price list view, the New button is grayedout in the Service Price Pricing Details
applet:
1. In the Pricing Admin screen, create a new price list.
2. Click on the Service Details tab and create a new record in the middle applet.
The New button is grayed out in the bottom applet (Service Pricing Details).
This is reproducible only in newly created records. The work around is to add price list line items, then go to a different price
list and then come back. This reenables the New button in the Service Price Details applet. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-7G7PIX)
Pricing Factor Designer
Pricing Model Report does not have Model Name and Created By Name. (Not applicable to Siebel CRM or FINS CRM or
Base MME or FINS MME.) (12-62YR9J)
Price List Transform Failure due to MS Word quotations in the search specification
Price list transformation can fail with no error messages and a log file not generated if the search specification in Pricing
Mapping Definitions contains smart quotes (for example, if it is copied from MS Word). (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-7IZD13)

Pricing Administration
When changing the effective dates of an Attribute Price table, be sure to sign off and sign back on before testing the effects of
the changes. This is necessary in order to refresh the cache that supports that Attribute Price Table. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-6SI7TO)
Removing Attribute Effects on Pricing
If the Administrator deletes an attribute, the attribute pricing that references that attribute may display misleading error
messages. The key is that whenever an attribute is deleted or changed, the administrator must check all related attribute
pricing, and delete and recreate attribute pricing based on new versions of the class or attribute. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-7SD7ZO)
Pricing Factor Evaluation
When creating a pricing factor-based Product Line, the factor will fire only if the product line in question is the first one in
the MVG. For example, if the pricing factor is Quote Item.Product Line = Business Computers, and then, if product Hard
Drive 30 has more than one product line defined, the pricing factor will be true only if Business Computers was the first
value in the list of Product Lines for this product. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-6DEAF3)
Pricing Model Manager
When defining Pricing Factor Field Value> Text=< In the Pricing Factor form applet, the Field Value field is limited to 50
characters. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5OJJME)
Matrix Pricing with Header Level Discount
For Agreements, if a discount percent exists on the header, then the line item prices cannot be adjusted by matrix-based price
factors even if the user nulls the Keep Discount flag. The work around is to blank out the discount % field and null out the
Keep Discount flag. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-8VZBN7)
If you have a pricing model with Start, Single, and Exit type factors, then you change the type of the Single type factor to
Aggregate, you will end up with two Aggregate Start type factors in the Pricing Factor Flow Chart Designer. The pricing
engine will not be able to process such a flow.
The work around is to check that Pricing Flow Chart has only one of each of the pricing factor types: Single, Aggregate, and
Exit. If you have a Pricing Flow Chart, you should not casually change the pricing factor types within the Pricing Factor
Designer. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5X53G8)
Negative quantities for the Bundle Type Factor
The Pricer does not handle negative quantities for the bundle type factor. It does not make sense in the business context of
bundling rules. Users should not enter negative quantities for the bundling type factors. (Not applicable to Siebel CRM or
FINS CRM or Base MME or FINS MME.) (12-6WZDWN)
Repricing a Customizable Product with manual discounts
Performing a Reprice or Reprice All function on a quote containing a customizable product with manually applied discounts
will not wipe out the discount shown at the component level. This is because the header level discount automatically sets the

Keep Discount flag for the root product of the customizable product. Setting the Keep Discount flag at the root forces the
entire customizable product to take the root product’s discount. The following are general rules when pricing a customizable
product:
If there is a manual discount and there are no volume discounts or pricing factor discounts, the manual discount always
takes effect.
The header level discount automatically sets the Keep Discount flag for all products.
When there is a Keep Discount flag on the root and line level, the discount specified at the root takes precedence over all
line level discounts. Therefore, when the Keep Discount flag is true for the root product, the discount specified at the
root is the discount for the entire customizable product.
When the Keep Discount flag for the root product is not checked, the customizable product price will be based on the
rollup of line items. Look at the discount amount field for each line to determine what will be taken into account during
rollup. If the children do not have discounts and the root product has a discount (with Keep Discount flag unchecked) the
discount of the root will take effect.
You can set a line level discount for the root product itself (should the root product have a price).
See the release note related to product defect 12-6B7TIB for related information. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-6B7TII)
Percentage-based Bundle Factors exclude preceding Bundle Type factors
For Price Models that adjust Customizable Products, if a bundle discount is set to affect the root product in a way that is a
percentage of the current net price, that current net price includes the List Price plus any single factor adjustments.
An example of this would be where the Root Price is adjusted by 15% based on single factors and then subsequently adjusted
by two or more Bundle Type factors. In this example, the Bundle Type discounts are calculated based on the current net
price, which includes the 15% single factor discounts. However, the discount formula does not include the effects of any of
the Bundle Type discounts. The Bundle Type discounts are evaluated and calculated independently. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6YK7Z4)
Customizable Product Pricing
The Customizable product pricing models associated to the children of a customizable product will not fire. (Not applicable
to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6OWS3N)
Defining Pricing Factors
In the Pricing Factor form applet, the Field Value is a text field. As a result, the user can enter any text and this entry is not
validated. For example, if the Business Component Field is Account, the entry in the Field Value is not checked to be a valid
account name. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-36KSZA)
Factor conditions that reference Date and Time fields should evaluate only the date portion of the field
Single factors can have conditions that are based on the date of a quote or order. For example, If Quote.Date Ordered <
01/15/2001 then add a 10% handling fee. Quote.Date Ordered is actually a field that stores the date and the time the quote
was placed. The pricing condition should be written in a way that evaluates only the date portion of the field. The time
portion of the Date Ordered field (although visible) should be disregarded for purposes of pricing conditions. (Not applicable
to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6P3TF8)

Bundle Type Factors
Specifying a Buy One, Get One Free rule requires a special setup. When using the Bundle Type factor to create a Buy One,
Get One Free rule, the setup should include only one line item in the Bundle Type factor. The rule should just reference the
Buy Item with a quantity of 2 and the Receive side of the rule should say 50% off. In this way you are selling two for the
price of one, which is the Buy One, Get One Free scenario. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-6R72IV)
Customizable Products
When defining Item Price for a customizable product component in the Pricing Designer applet, the value is updated only
upon saving the record and not after selecting the Adjustment Type and Value. (Not applicable to Siebel CRM or FINS CRM
or Base MME or FINS MME.) (12-6GGF6N)
Object Sequencing in the Input Property Set of a Business Service
The order in which objects are sent to script-based pricing factors is not guaranteed. Within each business service, make sure
there are validation steps that validate the sequencing of incoming property sets such as quotes and quote items. For
example, the sample database contains scripts that validate the input property set for Quote and Quote Item:
I=0
While (I<Inputs.GetChildCount())
BusComp = Inputs.GetChild(I).GetProperty("__BusComp Name__")
If (BusComp = "Quote") then
Account_Name = Inputs.GetChild(I).GetProperty("Account")
End If
If (BusComp = "Quote Item") then
Qty = Val(Inputs.GetChild(I).GetProperty("Quantity Requested"))
End If
I=I+1
Wend
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-69AKLU)
The Pricing factor will not fire correctly if AM or PM is the Field Value of the factor. For example, if the Field Value for
Date Time is set to 10/30/2001 1:00:00 PM, the factor will not fire if that condition is true.
The work around is to always set the Date Time for the Field Value in military time (24-hour clock). In the above example,
you would set the Date Time to 10/30/2001 13:00:00. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-8CRW4N)

Attribute Pricing
History bar
Attribute pricing views show up as Price Book in the history bar. This needs to be configured if the history bar has to show
Attribute Pricing related views instead. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
6DSOD1)
Search specification
If incorrect search specifications are entered in the attribute pricing views, the search will return a record in cases where there
is no match. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6DPWK6)
Error messaging
When invalid attribute names are entered manually, the error message displayed may not be accurate in description. Correct
the error message if system administrators use this functionality. (Not applicable to Siebel CRM or FINS CRM or Base MME
or FINS MME.) (12-6EYH9B)
Columns Displayed for Attribute Pricing with Multiple Attributes
In the Items applet in the Price Book Items Admin View, the displayed fields are the attributes that affect pricing, Adjustment
Type, Adjustment Value, and Description. If the user selects Columns Displayed, there will be additional fields that start
with Attr Val. These are hidden fields that do not affect the user and that the user does not see. These hidden fields must
remain in the Selected Columns for the Attribute Pricing to work properly. Therefore, the user should not remove these
hidden fields from the Selected Columns. Because these fields are hidden from the user (except in the Columns Displayed)
view, these fields should not be touched by the user. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS
MME.) (12-6V1CRR)
Pricing Model
Pricing Factor with attributes
Pricing model and pricing factor reports that contain pricing factors on product attributes will not display the attribute column
that contains the attribute name. These columns will have to be added in Actuate reports if attribute names are required in the
reports. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6P8589)
Inserting Pricing Model With Duplicate Names
Siebel ePricer checks that pricing model records are unique by the Name field only. This could present an issue wherein two
administrators are using the same repository and with limited visibility to each other’s data (they may belong to different
organizations, for example), may try to create pricing models with the same name. In this case, the application would indicate
that the pricing model name already exists. A work around is to develop a naming convention that makes certain there is
uniqueness when multiple pricing administrators are working on the same repository. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-6ASI3V)
Import of Pricing Models Using Workflow XML
An error occurs when using a workflow process XML to import a pricing model. The error can be reproduced as follows:
1. Create a workflow process XML import.

2. Generate a pricing model.
3. Execute the workflow process simulator.
4. An error occurs indicating lack of update privilege on Pricing Model fields ("EAISiebAdpt EAISiebAdptWrn 2
2001-09-11 16:19:09 --Update permission on the field Name is not granted for the business component Acta -
Pricing Model").
The work around is:
1. Insert the tag <Locked>Y</Locked> in the pricing model XML.
2. Delete all empty IDs.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6NFH74)
Promotion
Quantity for Promotion inside Packages
If a promoted product is added to a package, its quantity can be selected out of the Minimum and Maximum range set by the
promoted product’s associated deal. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
6B16XE)
Quote
Reprice All
Manual price adjustments are wiped out during reprice All. (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-6LLXH3)
Effect of Attributes on Quote Item Price
Attribute-based pricing does not take effect until the user clicks the Reprice button, when in Quotes, Orders, Quote Pricing
Model Validation, or Order Pricing Model Validation views. This is done to balance ease of use and performance. However,
you can configure the application using Siebel Tools to invoke the method: CalculatePrice to reprice automatically (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6AK9QJ)
Script Based Pricing Factor
Configurable product attributes
Product attributes are passed to script based rules as a peer of the quote item not as children. (Not applicable to Siebel CRM
or FINS CRM or Base MME or FINS MME.) (12-69AKLW)
Adjustment Items Display When Creating Attribute Pricing Table
The Adjustment Items applet may show an Attribute Name even though that attribute has not been selected. This problem
occurs when:
The user is on the Adjustment Items applet, then clicks the More Info tab to create a new table.

The user creates a new table based on a class different than in the previous table.
The user clicks on the Adjustment Items tab before specifying the attributes from the Attributes tab.
The Adjustment Items applet then displays attributes even though none have been specified. This is only a display issue. As a
work around, the user should specify the attributes relevant for the table being created before clicking the Adjustment Items
tab. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6160HV)
Pricing Factors Based on Class Attributes
Pricing factors defined on an attribute, whose data type is Integer and whose Language Independent Code (LIC) is a Text
string, may not fire. As an example, consider:
1. Class shoes has one attribute: Size.
2. Size is defined as an Integer data type.
3. The following values are defined in the List of Values for Size:
LIC Display Value in
Quote/Order
Small 5
Medium 10
Large 15
A pricing factor on Size is defined such that when the user selects a Size of 5 for a shoe, in a Quote, the user is given a 10%
discount. At runtime this factor is evaluated against the LIC (not the Display Value). Now, the LIC (small, in this example),
cannot be converted to an integer. Hence, the factor will not fire. As a best practice, use the following rules:
1. Define attributes as Text, to avoid the issue described above.
2. If the attribute must be specified as Number for properly comparing numeric values, make sure that both the LIC and the
Display value are numbers.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-60KU2Z)
Thread Bar
The thread bar labels between the customizable product pricing, pricing factor designer, and the run time instance may vary
slightly between views. Make sure they are consistent if users follow a certain navigation paradigm. (Not applicable to
Siebel CRM or Base MME or FNS MME.) (12-6G6E57)
Siebel eSales
In eSales using Netscape 6.2.1, eAdvisor presents a blank screen and the application will not work, when the reload button is
clicked. When running eAdvisor in eSales and the user hits reload, a blank screen is presented within the Siebel frame and
the application tabs will not work. Users will need to click on the flyover link to continue with the application. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B8RG4T)

Encryption when using IBM DB2 AS/400 and IBM DB2/390 Databases
On IBM DB2 AS/400 and IBM DB2/390 (when EBCDIC encoding is used) databases, the algorithm used by the Standard
Encryptor service to encrypt data can generate characters that cannot be stored in the database, leading to data corruption.
Therefore, if you are using AS/400 or 390, you must use RSA encryption, specifically the RC2 Encryptor service, instead of
the Standard Encryptor service to encrypt data. Siebel recommends that all customers, regardless of the underlying database
being used, use RSA encryption.
Out-of the box, Siebel eSales encrypts three fields using the Standard Encryptor service:
Account Number field on the Personal Payment Profile business component. This field maps to the PAY_ACCT_NUM
column on the S_PER_PAY_PRFL table.
Credit Card Number field on the Quote business component. This field maps to the CC_NUMBER column on the
S_DOC_ORDER table.
Credit Card Number field on the Order Entry - Orders business component. This field maps to the CC_NUMBER
column on the S_ORDER table.
For additional fields in other Siebel applications that use the Standard Encryptor service for encryption, refer to the Upgrade
Guide for Microsoft Windows or the Upgrade Guide for UNIX. Documentation on the Siebel Bookshelf provides
instructions on how to use RSA encryption. For an important overview of how the RC2 Encryptor service works, refer to the
Siebel Server Administration Guide.. If you have data encrypted using the Standard Encryptor service that needs to be
encrypted using the RC2 Encryptor service, follow the upgrade instructions in the Upgrade Guide for Microsoft Windows or
the Upgrade Guide for UNIX. The Encryption Upgrade Utility is delivered with Release 7.0. For a reference on the business
component user properties used for encryption, refer to the Siebel Tools Reference.. Encryption can be controlled from the
business component Field user properties: Encrypted, Encrypt Key Field, Encrypt Service Name, and Encrypt Source Field.
(12-B8V2FO)

Email Templates
The links in eSales emails do not return the user to the correct place in the application. To modify the links, navigate to Site
Map > Communications Administration > All Templates. In the Name field, query for the following: Order Shipped Email
Package*, Order Failed Email Package*, Order Awaiting Approval Email Package*, Order Rejected Email Package*, or
Order Accepted Email Package*.
Under the Template Items tab, edit footer4, the file in the Attachment Name field. Modify the links as detailed below. Be
sure to replace the reference to netvistaiss2 within the link to the name of your server.
Order Accepted Email Package (eSales):
http://netvistaiss2/eSales/start.swe?SWECmd=GotoView&SWEView=Order+History+Summary+View+(eSales)&SWEPost
nApplet=Order+Form+Applet+-+Summary+(eSales)&SWEPostnRowId=[Order Entry - Orders.Id]
Order Rejected Email Package (eSales):
Order Awaiting Approval Email Package (eSales):
http://netvistaiss2/eSales/start.swe?SWECmd=GotoView&SWEView=Order+Approval+View+(eSales)&SWEPostnApplet=
Order+Form+Applet+-+Approval+(eSales)&SWEPostnRowId=[Order Entry - Orders.Id]
Order Failed Email Package (eSales):
Order Shipped Email Package (eSales):
nApplet=Order+Form+Applet+-+Summary+(eSales)&SWEPostnRowId=[Order Entry - Orders.Id] (12-9W5Z5Z)
eSales - Approve Order Process
The eSales - Approve Order Process workflow process has been renamed eSales - User* in the application. Documentation
refers to the eSales - Approve Order Process. As the workflows are not referenced by name, the runtime functionality is not
affected. (12-9TTII3)
Tax Calculation for Service and Auction Products
To make sure the tax amount is included in the Grand Total, change the Quote Total field’s Calculated Value on the Quote
business component to [Current Quote Total Net Price] + [Tax] + [Freight Total].
To set Taxware’s service indicator, edit the Business Service script for taxware Adapter Service. In CallTaxware method, at
the end of line 113, add the following code:

else if (propName == "IsService")
if (propVal == "Y")
SetBuffer(taxinbuffer, ‘sERVIND", ‘s", curRecord);
NOTE: Base MME and FINS MME support eSales, but not eAuction.
(12-9K0V1Z)
Calculating Tax and Shipping for Auction Orders Created Automatically
To calculate shipping and tax for auction orders created by the Silent Authorized Order Process, modify this workflow to
include the Calculate Shipping subprocess and Calculate Taxes business service. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-9UZX9Z)
Order Rejected Email Package (eSales)
The header4 template item in the Order Rejected Email Package (eSales) template should be modified. Replace, the order
you created on [Order Entry - Orders.Created] has been denied by [Order Entry - Orders.Approved By - Emp Login], with,
the order you created on [Order Entry - Orders.Created] has been denied by a purchasing manager in your company, or
another custom message. (12-9SDU5V)
Rapidly Clicking Buttons Can Cause Error
Rapidly clicking the Finish button in the user registration process can cause errors. (12-65IZLO)
Empty Shopping Cart when User Exits eConfigurator
If a user exits a configuration session by clicking on a button or hyperlink that is not part of the eConfigurator runtime user
interface, an empty shopping cart will be created for the user. (12-5WKU5I)
Favorites
Products are added to the Favorites List with their default attribute values. (12-4X5ATZ)
The Primary Indicator for a Credit Card or Shipping Address
Once the Primary indicator is set for a credit card or shipping address, the indicator cannot be deselected. It is possible to
indicate that another credit card or shipping address is the Primary. If the Primary credit card or shipping address is deleted,
another credit card or shipping address entry, if one exists. will be set as the Primary. (12-5WNROW)
Naming Restrictions for Quotes and Templates
You cannot have two quotes with the same name if the Organization, Account, and Revision Number are the same or empty.
(12-5V2VJP)

Saving Primary Shipping Addresses and Credit Cards
The Save button must be clicked two times under the following circumstances: address or credit card information is entered,
the Primary indicator is set, and the Save button is immediately clicked without stepping off the checkbox. (12-8GN6C3)
Verbal Authorization Codes and the CyberSource Integration
In order to process verbal authorization codes provided by the bank, CyberSource requires that the auth_type field be set to
verbal when a settlement request is made. The current integration does not pass a value for the auth_type field. To support
processing of verbal authorizations from Siebel Systems, a new field must be added that will set the auth_type field to verbal.
In addition, this field must be added to the integration and passed to CyberSource. (12-7XJ9G1)
Reset Button Clears Values in Dropdown Fields
Clicking the Reset button after editing a form clears the values for drop-down fields, instead of restoring their previous
values. (12-6Z9CM9)
Required Payment Field Error Message
When more than one required field is missing a value, the error message displayed does not necessarily indicate the first field
in the form that is missing the value. (12-5SIB7L)
Required Payment Field
On the Quote Personal Payment View, no fields appear to be required. To indicate which fields are required, implement
browser-side checking or require that credit card entries be entered and selected from a list of stored credit cards. (12-
5LCW2X)
Dropdown Selections Are Blank After Clicking Browser Back Button
When using the browser Back button after filling out a form with drop-down values, the selected values are not saved. For
example, the values selected for the Type, Expiration Month, Expiration Year, Billing State, and Billing Country fields for
credit cards are blank after clicking the browser Back button. (12-7TBDJB)
Add to Cart for a promoted product
Currently, the application does not restrict adding to cart a product with a promotion deal applied on it. As a result, a product
could be added to cart with the same promotion deal applied on it as many times as the user desires. This essentially negates
the min/max limitation that may be specified on a promotion deal. To see this behavior:
3. Go to a promoted product, and click Browse Deals.
4. Select deals with valid quantity and apply the deal. Prices change to reflect the deal adjustment.
5. Click Add to Cart.
6. The screen refreshes and the product detail page shows the product with deal adjusted price, not the original list and
your prices.
7. Repeat steps 2 and 3 as many times as desired..
(12-8BZS95)

Formatting of Quote Item Detail View is Incorrect
The formatting of the Quote Item Form Applet is incorrect. The display should match the layout of the Product Detail Form
Applet. (12-61M9B3)
Simultaneously Confirming and Canceling an Order Causes Error

In the eSales checkout process, if a user confirms an order and then immediately cancels it before the confirmation page
appears, an error will result. Companies can prevent this behavior at deployment time by adding a page that indicates the
order is in process. This new view should not have a Cancel button. (12-5UOKY9)
Setting EnableCDA parameter to TRUE impacts performance of eSales

Setting this parameter to TRUE interacts with the Siebel Web Engine to degrade the performance of the Siebel eSales
application. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-67QCG7)
Siebel eCatalog
Parametric Search screen does not refresh correctly on Mac OS
When clicking Back from the Product Comparison page to return to Parametric Search, the screen is not refreshed correctly.
(12-6Y8CCT)
Number of products found is not displayed on the Parametric Search page

The application as delivered does not display the total number of results found. Customers can configure the application to
display this information. (12-9STWHO)
Threadbar is not displayed on Parametric Search page
The application as delivered does not display a threadbar on the Parametric Search page. (12-7T1E1O)
Siebel eService
Siebel Administrator’s phonetic name representation is automatically replaced with that of a new user’s
This is only applicable for the Japanese locale. In order to prevent the Siebel Administrator’s phonetic name representation
to be replaced with that of a new user’s, please do the following:
1. Open Siebel Tools and go to Business Component.
2. Select User Registration and go to Field.
3. Lock Project and create a new field with following attributes.
Name: VAlias
Calculated: Y
Type: DTYPE_TEXT

Use Default Sensitivity: Y
4. Go to Applet and select User Registration Initial Form Applet.
5. Go to Control and select Alias.
6. Change the following attributes.
Field: VAlias
HTML Display Mode: EncodeData
HTML Row Sensitive: Y
HTML Type: Text
Sort: Y
7. Compile srf and copy it into siebsrvr\objects\jpn\
8. Launch Callcenter with new srf.
9. Go to Workflow Administration>Workflow Processes.
10. Select User Registration SubProcess and click revise button.
11. Click Process Property tab.
12. Create a new property with following values.
Name: VAlias
Data Type: String
Business Component: User Registration
Virtual Field: VAlias
13. Click Process Designer tab, find Commit User Profile Data, and double click.
14. At the second level Applet (Field), create a new field with following values.
Field Name: Alias
Type: Process Property
Property Name: VAlias
15. Go back to Workflow Administration>Workflow Processes.
16. Select User Registration Process and click revise button.
17. Click Process Property tab and create a new property with following values.
Name: VAlias
Data Type: String
18. Click Process Designer and double click Insert New User.

19. Create a new field with following values.
Field Name: Alias
20. Go back to Process Designer and double click Insert New eAuction User.
21. Create a new field with following values.
Field Name: Alias
22. Go back to Process Designer and double click Update eAuction User.
23. Create a new Input Argument with following values.
Input Argument: Alias -- type manually, not from pick applet
24. Go back to Process Designer and double click Update Existing User.
25. Create a new Input Argument with following values.
Input Argument: Alias -- type manually, not from pick applet
26. Go back to Process Designer and double click registration SubProcess.
27. At the third level applet (Sub Process Output Argument), create a new output argument with following values.
Type: Output Argument
Sub Process Output: VAlias
28. Go back to Workflow Administration>Workflow Processes.
29. Activate two modified workflow processes.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9NDRZT)
Branch Locator
For Branch Locator deployment outside the U.S., we recommend the following two configurations:

1. Change the Default Country user property of the Service Locator Buscomp from USA to XXX (that is your country
of choice) in Siebel Tools. With that change, Branch Locator will search your newly specified default country (for
exampleFrance) if end users do not manually select a different country value.
2. If the state field entry is not required for your country, set the State Value Required user property of the Service
Locator Buscomp to FALSE and remove the mapping of the State field in Siebel Tools. This will allow the end
users to enter just the City, ZIP, and Country fields as the required fields. (Not applicable to Siebel CRM or Base
MME.) (12-6VS1C4, 12-AW2XXB)
Siebel Branch Locator does not include non-US geocode data
Because Siebel does not ship non-US geocode data, no branch location can be set up in the non-US regions in the application
as delivered. To set up branch locator functionality for non-US regions, you must import ZIP code-level geocode data for
your desired country (for example, Germany) before a branch location query can be processed. (Not applicable to Siebel
CRM or Base MME.)
Smart Answer in eService requires Smart Answer option in eMail Response
Smart Answer in eService requires that the Smart Answer option in eMail Response is also used. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-6SEWPI)
Siebel eTraining and Siebel eTraining Manager

Using eTraining’s shopping cart within Base Applications other than Sales, Call Center, and Marketing
Customers who are using Siebel eTraining in conjunction with Siebel Base Applications other than Sales, Call Center, and
Marketing (shopping cart is enabled out of the box for these three applications) will not be able to use eTraining’s shopping
cart functionality out of the box. In cases where the shopping cart is not enabled, when a training administrator clicks on the
Add User button in the Training Register Course Applet or the Training Register Class Applet and then clicks on the Save
button, the registrant will be enrolled in the course or class automatically if seats are available. The system will not use
shopping cart functionality to charge for the active course or class. Customers can enable the shopping cart functionality by
taking the following steps:
1. Use Siebel Tools to add the eSales Orders Screen, the eSales Quotes Screen, and the eSales Shopping Cart Screen
(With Screen Caption as Shopping Cart ) to the Siebel Base Application as Page Tabs or Screen Menu Items.
2. In Siebel Tools, find the Current Quote View (eSales) View and then find the Quote Form Applet - Current (eSales).
Map an Edit button on this applet for the appropriate Base Application. This will allow Admin to add the
appropriate Account and Contact Name on the Quote created in Shopping Cart during the Check-Out process.
3. If the Base Application is eChannel Partner Manager, go to the Field object and locate the eSales Integration Flag
field. Change the Calculated Value from If (GetProfileAttr(ApplicationName) = "Siebel Partner Manager",
"N","Y")” to “Y.”
4. Using the Base Application, go to the Runtime Events Admin screen. Under the Event Alias tab, create a new
record where Name = Base Application, Object Type = Application, Object Name = Base Application, and Event =
WebSessionStart.
5. Under the Events tab, create a new record where Name = Base Application, Sequence = 1, Action Set = eSales Web
Session Start Action Set.

6. Go to Application Administration > Responsibilities to add the following views to the appropriate responsibilities:
Current Quote View (eSales), Edit Quote Confirmation Popup View, Quote Item Detail View (eSales), Save Cart,
Confirmation View (eSales), Save Cart View (eSales), Saved Quote Detail View (eSales), Saved Quotes View
(eSales), Saved Quotes View - My Company (eSales), Select Account Address View (eSales), Select Payment View
(eSales), and Select Personal Address View (eSales).
7. Go to Workflow Administration/Workflow Process View, and locate the Workflow process called eSales - Enter
Shipping Details Process. Identify the step called Address Required,and add the name of the Base application to
this step.
8. Finally, make sure that the contacts that you are trying to register have a primary address (which would be located
in the Contact/Address View), and a primary account (which would be located in the Contact/Account View), and
that the account bill to/ship to addresses are filled in.
9. Disable the following PDQ’s by adding them to the SWE section of the CFG file:
• PDQDisabledView0 = "Order History View (eSales)"
• PDQDisabledView1 = "Order History View - My Company (eSales)"
• PDQDisabledView2 = "Order History Summary View (eSales)"
• PDQDisabledView3 = "Order Confirmation View (eSales)"
• PDQDisabledView4 = "Order Approval View (eSales)"
• PDQDisabledView5 = "Saved Quotes View (eSales)"
• PDQDisabledView6 = "Saved Quotes View - My Company (eSales)"
• PDQDisabledView7 = "Saved Quote Detail View (eSales)"
• PDQDisabledView8 = "Quote Summary View (eSales)" (Not applicable to Siebel CRM or FINS CRM or Base
MME or FINS MME.) (12-6QGAC6)
Deactivating Course Test Status
Tests are currently assigned a Status of Active, Inactive, or Development. When setting up tests for a course, administrators
are not able to deactivate the test status; therefore, tests can be associated to courses even if the Status is Inactive or
Development. To deactivate a test, disassociate the test from related courses by deleting the Associated Courses in the Tests
list applet. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-8EWUKR)
Courses do not become inactive automatically when expiration date passes
To de activate a course whose expiration date has passed, Training Administrators should navigate to the Course
Administration List view, run a query for courses whose expiration date is earlier than today’s date, and change the status to
Inactive. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6FJXTR)
eTraining Upgrade of Instructor Email Address
The Instructor Email field used in 6.x versions of eTraining is no longer exposed by default on the Courses or Class Views.
To expose the Siebel 6.x Instructor Email field in the Siebel 7 UI , expose the S_Party table in the Contacts business
component. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-5MZP46)

Globalization
In a Global Deployment environment, Event Status field does not pick up translated values.
In multilingual deployments (with more than one language per database), the Event Status field only displays the English
status values, even though the translation LOVs are provided. This is applicable to the German, Italian, Spanish, Brazilian
Portuguese releases. This is because the Event Status field is mapped to a column that is shared by Campaigns, which uses a
different LOV, hence the Event LOV could not be MLOV enabled.
To fix this problem, you can use Siebel Tools to define a new table column, and map the Event status field to it. Then make
the Event status MLOV enabled. (12-FKRM7L)
Internationalization
Additional Installation for Hebrew Release
This release note is applicable to the Hebrew release. After installing the Hebrew server it is necessary to also install the
Mobile Web Client with the Hebrew language pack. Copy the images (*_d.*) in the sea704\client\public\heb\images
directory to sea704\siebsrvr\webmaster\images\heb. After this step the mobile client can be removed. (Not applicable to
Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B3I3UJ)
Appointments in Calendars in Hebrew environment
BIDI - Run Time errors are seen when creating new appointment in Calendars in Low Interactivity (example: Employee
Relationship Management).
1. Click on Calendar and view the monthly Calendar.
2. Click on NEW to create new appointment
3. A run time error appears as follows:
A runtime error has occurred
Do you wish to debug ?
Line: 13
Error: Expected “)”
A script, 12-B1M8XE_timezone_fix.zip, is available on SupportWeb. Extract this script and execute it against the database
to resolve. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B1M8XE)
Call Center Homepage
This release note is applicable to the Korean locale. The win.ini file for a Korean homepage must be modified to display the
time and date. Download an updated Korean win.ini file from Siebel SupportWeb. (Not applicable to Siebel CRM or FINS
CRM or Base MME or FINS MME.) (12-B5A6P9)

String Length Limitation for Japanese User Interface
This release note is applicable to the Japanese locale. The maximum input length for any field in the Japanese user interface
is 100 characters. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B06HF7)
Campaign and Program Timeline in Simplified Chinese Release
The following is applicable the Simplified Chinese release. The date format will appear as Month/Day/Year. (Not applicable
to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AXMG05)
Message Column Sort
The following applies for non-English locales. In the Communications Administration Message Broadcasts view the
message column does not support sorting. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
1DSQ2V)
Validation Fields in Error Messages appear in English
Validation fields in error messages will appear in English; for example, End and Start validation fields in an error message.
(12-1QM2SR)
Currencies
Currency symbols in CHS and HEB language versions
Due to the underlying technical limitations of the supported operating systems and databases for the Chinese Simplified
(CHS), and Hebrew (HEB) versions of Siebel eBusiness Applications, the following currency symbols are being used. In the
CHS version of Siebel, the currency symbol for Israeli New Shekel, currency code ILS, has been changed to ILS. Also, the
currency symbol for the Austrian Schilling, currency code ATS, has been changed to oS. In the HEB version of Siebel, the
currency symbol for the Chinese Yuan Renminbi, currency code CNY, has been changed to CHS. (Not applicable to Siebel
CRM or FINS CRM or Base MME or FINS MME.) (12-B72LAF)
Localization
Automatic start up script (siebel_server) doesn't fuction on Sun Solaris enviroment.
This is applicable to Siebel eBusiness Applications releases for all languages including English. The example solution below
applies to Japanese. Please change the LC_CTYPE to your own language code.
1. Edit the startup file as follows:

Change [export] syntax without return code in siebenv.s
from:
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${SIEBEL_ROOT}/lib/odbc/merant
export LD_LIBRARY_PATH
to:
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${SIEBEL_ROOT}/lib/odbc/merant;export
LD_LIBRARY_PATH

2. LC_CTYPE=ja_JP.PCK;export LC_CTYPE into siebel_server file.
(12-DVQRMR)
Partner Profile Report
This is only applicable for the Japanese locale. Some strings in the Partner Profile (partpro.rox) report are illegible. Remove
the font fact name from the corresponding illegible labels and allow for the font face to inherit from the parent. (Not
applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-6V2J1R)
The Save\download screen in a report is displaying incorrect characters
This release note is applicable to the Hebrew, Korean and Chinese Simplified releases. The Save and download screen in a
report displays incorrect characters and unlocalized text. To fix perform the following work around steps:
The file saveas.achtml is loaded while importing Siebel template files when installing Reports Server. It is contained in
rptcast_nt_server.zip which is unzipped during Reports Server installation.
1. Request the file saveas.achtml from Siebel Support Web.
2. Copy the file saveas.achtml into the \Actuate5\ReportCast Server\default\standard folder.
3. Stop ISS or Netscape Web Server service and then restart it.
4. Access the Report cast Channel Administration page by typing the URL
http://reportcastname/acweb/reportserver_name.
5. Click on Administration Link.
6. Click on Report Cast Administration Link.
7. Click on the Reload Templates Link.
8. A confirmation message will appear if the templates reload successfully.
NOTE: If a confirmation page does not appear, verify that the connection to the web server is still active.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B07OYH)
Upgrade Kit Wizard Popup Applet Text in Japanese Release
The following is applicable for the Japanese release. There additional Japanese translations that are needed in the Upgrade
Kit Wizard Popup applet in the Project: Software Upgrade. For the three controls in the Upgrade Kit Wizard Popup Applet;
Schema Qualifier, Privileged User ID, and Privileged User Password Japanese translations can be copied from
IDS_ERR_ADMN_ODBC* keys in S_MSG table (belongs to admnstt.rc2). Complete the following:
1. Get the translations from the next related S_MSG keys:
IDS_ERR_ADMN_ODBC_SCHEMA_QUA_FIELD
IDS_ERR_ADMN_ODBC_TBL_OWNER_FIELD
IDS_ERR_ADMN_ODBC_TBL_OWNER_PASS_FIELD

2. Create the JPN control locale records for the Applet: Upgrade Kit Wizard Popup Applet
Required Control Locale Records:
• Schema Qualifier - Privileged User ID - Privileged User Password
Translations need to be copied in the Caption Property.
3. Compile a new SRF. Project: Software Upgrade (Not applicable to Siebel CRM or FINS CRM or Base MME or
FINS MME.) (12-BAAW67)
Brazilian Portuguese text may appear in error messages, prompts, confirmations,and so on. in Swedish release
This release note is applicable to the Swedish release. Certain splash screens, prompts, confirmations, and error messages
appear in Brazilian Portuguese for database server installation and configuration.
To remedy this complete the following.
When installing the DB server for AIX and Solaris, select English as the installer language. If Swedish is chosen as the
installer language, Brazilian Portuguese may appear in some options, help, promptsand so on. (Not applicable to Siebel
CRM or Base MME.) (12-B8XJ37)
Error message appears when trying to search report data in report viewer
This release note is applicable to the Italian release. To remedy this complete the following.
1. Please submit a Service Request to Siebel Technical Support for the following file: searchrequest.achtml.
2. Copy this file to the \Actuate5\ReportCast Server\default\standard folder.
3. Stop ISS or Netscape Web Server service and then restart.
4. Access the Report Cast Channel Administration page by typing the following URL
http://reportcastname/acweb/reportserver_name.
5. Click on Administration link.
6. Click on Report Cast Administration link.
7. Click on the Reload Templates link.
8. A confirmation message will appear if the templates reload successfully. If a confirmation page does not appear,
verify that the connection to the web server is still active.
(12-B22KUD)
UI missing fields in User Registration in Partner Relationship Management and eService
This release note is applicable to the Korean release. The Complete Address Info form has omissions: Address Line 1 and
Country fields.
To Fix:
User Registration Contact Information Form Applet > Applet Web Template > Edit
Item Identifiers - Language override needs to be changed from -

User Registration Contact Information Form Applet
zip 1,300 to 1,300
country 1,302 1,301
state 1,302 1,302
addressline1 1,304 1,303
city 1,304 1,304
User Registration Contact Information Form Applet (SCW) > Applet Web Template > Edit
Item Identifiers - Language override needs to be changed from -
User Registration Contact Information Form Applet (SCW)
zip 1,305 to 1,305
country 1,307 1,306
state 1,307 1,307
city 1,309 1,309
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B98A7E)
Adding Text to Blank Buttons on Product Pick Applet
The following is applicable to the Spanish and Brazilian Portuguese language pack releases. Text for buttons on the Product
Pick Applet are blank. These buttons function correctly, though there is no text. Follow the following steps to add text to
these buttons.
1. In Tools, go to Applet.
2. Query for Inventory Location Product Pick Applet CE.
3. Go to Control.
4. For controls GotoNextSet, GotoPreviousSet, and NewQuery, go to Control Locale, copy the English record and add
Spanish and Portuguese translations.
5. Recompile a new srf. (12-B2UKLW, 12-B2UKMS)
In the Site Map, Project has been translated as Quality
This release note is applicable to the Korean release. To change the translation:

1. In Siebel Tools, go to Flat Search.
2. Select screen Menu Item Locale.
3. Under Parent Screen Menu Item field, query for Projects Screen (ePS).
4. In the text field, change the KOR translation from Quality to Projects. (Not applicable to Siebel CRM or FINS CRM
or Base MME or FINS MME.) (12-B5QKTN)
The record count is reversed.
This release note is applicable to the Korean release. The formats of the Record Counter fields are incorrect in five cases. To
remedy this, go to Siebel Support Web download the file. 12-B689SG_record_counter.zip, extract the file, and run it against
the database. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B689SG)
Range of Records Display in Hebrew Locale
The following is applicable for the Hebrew or a bi-di locale. In the Hebrew or a bi-di locale the display of the range of
records, for example, 1 of 9, will not be in bi-di mode. This does not affect the functionality of the application, except that
the UI looks different from expected. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-
AF5PNN)
Order Entry - Line Items View and Order Entry - Line Item Form Applet
Clicking on Line Items (Detalles in ESN) tab under Orders (Pedidos in ESN) Screen tab inCall Center, results in two tabs
Totals(Totales in ESN) , Line Details(Detalles in ESN) highlighted in the third level navigation tab bar. The reason for this is
that the Menu Text and Viewbar Text of Line Details (Detalles in ESN) tab in the third level navigation tab bar is the same as
Line Items (Detalles in ESN) tab in the second level navigation tab bar. Though two tabs are highlighted, this does not affect
the functionality of the application except that the UI looks different from normal. (12-AOL950)
Default Currency in the Korean Language Pack Release
The default currency in the Korean Language Pack release will be the U.S. Dollar. This can be changed to the Korean Won
by following:
Make a change in the S_MSG table.
2. Navigate to Screens > System Administration-->Screens
3. Query for MSG_LEVEL=S_ORG_EXT, MSG_TYPE=BASE_CURCY_CD, MSG_NUM=0-R9NH
4. Change the MSG_TEXT from USD to KRW
The default currency can also be changed at the application level.
1. Open the Siebel Call Center Application
2. Navigate to Sitemap > Group Administration--Divisions
3. Query for Default Organization
4. Change the Currency Code from USD to KRW (via the MVG Popup) (Not applicable to Siebel CRM or FINS CRM
or Base MME or FINS MME.) (12-AWZ99V)

LOV Strings for Hebrew and Korean
This release note is applicable to the Korean and Hebrew locale. There are LOV strings that will be too long for Hebrew and
duplicates in the Korean locale. This results in some LOVs that cannot be displayed in the Hebrew and Korean locales.
These can updated by going to Siebel SupportWeb and downloading the file 12-B4G6R7.zip. This zip file contains two files
which are work around scripts for Hebrew and Korean. For a Hebrew environment, run the file 12-
B4G6R7_toolong_HEB.txt against your database. For the Korean environment, run the file 12-B4G6R7_duplicate_KOR.txt
against your database. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B4G6R7)
Oracle Connector in the Korean Locale
This release note is applicable to the Korean locale. The Oracle connector for Siebel is not supported in the Korean release.
(Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-AZBJDQ)
Predefined Queries in the Calendar Screen
This release note is applicable to the French locale. Predefined Queries in the Calendar Screen will appear as English. (12-
AY1GRV)
Maximize or Minimize Buttons in Korean Release
The following is applicable for the Korean release. The minimize and maximize buttons in Business Service Administration
view are unavailable. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-B5QKV3)
Translated Error Messages in the Spanish, Swedish, and German Releases
This release note is applicable to the Spanish, Swedish, and German releases. There are certain error messages in the
Spanish, Swedish, and German releases with incorrect translations. These translations can be changed by following the
below actions.
For the Spanish Release:
1. ESN (STR_MRG_UFN_UPDATE_CONF)
2. Go to the LOCALE folder on your installations, for example client\locale, siebsrvr\locale
3. Open file ssrmrg.esn
4. Search for string: Conflictos de actualización. Actualizado por 1%. Vuelva a especificar estos valores si aún desea
actualizar estos ítems:
5. Replace with string: Conflictos de actualización. Actualizado por %1. Vuelva a especificar estos valores si aún
desea actualizar estos ítems:
For the Swedish Release:
1. SVE (INF_PME_SCHED_PM)
3. Open file ssrpme.sve
4. Search for string: schemalägger PM-plan “%1” för tillgång %2.
5. Replace with string: Schemalägger PM-plan “%1” för tillgång %2 på %3.

NOTE: Base MME does not support a Swedish release.
For the German Release:
1. DEU (ERR_SRS_NOT_IMPLEMENTED)
3. Open file ssrcso.deu
4. Search for string: Intern: Die Funktion %1 ist nicht implementiert.
5. Replace with string: Intern: Die Funktion ist nicht implementiert.
(12-AI7ZQO)
Predefined Queries in Japanese Release
The following issue is only applicable for the Japanese locale. Service Request records are not displayed in eBriefings
because the Predefined Query is missing a Lookup Value statement. To display the Service Requests, change the Predefined
Query as follows:
1. Launch Siebel Sales/ERM Application as the administrator.
2. Using Sitemap, access Predefined Queries.
3. Query the PDQ for Object SI Employee.
4. Change the SI Service Request as follows:
5. ‘sI Service Request”.Search = "([Status] = LookupValue(‘sR_STATUS”,”Open”)) or ([Status] =

LookupValue(‘sR_STATUS”,”Pending”)) and [Created]>=(Today()-365). The Service Requests should display
after this is changed. (Not applicable to Siebel CRM or FINS CRM or Base MME or FINS MME.) (12-9NIK7J)
Multilingual Deployment Support
Multilingual List of Values (MLOV) in Siebel Applications
Contact Siebel Technical Support for a list of known List of Values that require modification for a multilingual deployment.
(12-B9ISG9)
Documentation Server in a Multilingual Deployment
The Siebel 7.0 Documentation Server can only be configured for one locale per enterprise for connected clients. In a
multilingual environment a customer or administrator should decide which local setting and which language the document
server component will use. Based on this decision all requests, independent from the language Object Manager in which they
originate, will be handled in the language and local of the Document Server Component. For additional language support, the
configuration must be altered iteratively for the enterprise or a dedicated web client must be used. (12-B9GI4Z)

Product and Feature Limitations for Multilingual Environments
The following products or features have limitations in a multilingual5 development or production environments.
eMarketing
A Multilingual List of Values (MLOV) environment is not supported.
NOTE: This limitation applies also to eCampaigns, Siebel CRM and Siebel MidMarket Edition.
Campaigns
Email campaigns can only operate in one language.
Actuate Reports Server
One Actuate Reports Server is required for each locale or language.
List Manager - Data Quality
When using an MLOV-enabled database, the Language Independent Code (LIC) is required when importing.
5
A multilingual environment is one that includes more than one Siebel localization operating against the same application
database.

Siebel Financial Services Known Anomalies 5
This chapter provides information on known anomalies and work arounds specific to the Siebel Financial Services eBusiness
Applications, which include eFinance, eHealthcare, and eInsurance.
Siebel eFinance
Drilling Down on Opportunity Loan Participants
Values in the Institution column in the Loan Participants list applet on the Opportunity Detail, Lending Syndicate view are
displayed as links (blue text). However the drilldown is not activated in this applet because drilling down on the Institution
column will generate an error. (12-AC4H5U)
Drilling Down on Activities from the Opportunity Summary View
The Call Report column in the Activities list applet on the Opportunity Summary view displays a Y or N, indicating whether
the activity is associated to a call report. The value is displayed as a link (blue text), however the drill down is not activated
in this appletbecause drilling down on the Call Report column will generate an error. (12-AC4H53)
Assigning Employees to Opportunity Activities
When adding or modifying activities in the Activities list applet on the Opportunity Summary view, the Assigned To column
is read-only and displays the primary Employee currently assigned to the activity. To add or delete Employees from an
activity, use the Opportunity Activities view. (12-AC4H4G)
Siebel Call Reports
Cannot Create New Contact in Action Items for a Call Report
Cannot create a new contact in the Action Items applet in the FINCORP Call Report, Action Items view. Create a Contact in
the Contact screen. Select Contact in FINCORP Call Report, Action Items view. Disable the New button in the pop-up
applet. (12-AGGZ88)
Using Auto Call Report for Multiple Contacts or Employees
When using the Auto Call Report button on the Activities screen to create a new call report, only the primary contact and
primary employee are automatically added to the call report. Add the other parties in the appropriate Employee Participants
or Contact Participants applets. (12-9W05DZ)
Call Report with Same Value for Planned Start and Contact
User cannot create a call report with the same value for Contact and Planned Start Date. To create the second call report,
make sure the Planned Start Date does not have the same exact time as the first call report. (12-5VF97N)

Siebel Financial Services Known Anomalies
More Info View missing on Call Reports Screen
The More Info third-level-Navigation tab is missing from the Call Reports Screen. To add this view, add the “FINCORP
Call Report More Info View” view to the Responsibilities of the Users that need access. See the Siebel Administration Guide
for detailed instructions. (12-9VYA5R)
Call Report Email Template is in English Only
The following issue is applicable for all non-English locales. The template file used to populate the Send Email dialog is only
in English. The file itself uses a series of smart links to determine what data should be populated to the template, so there are
very few words that will not be translated. To avoid this issue, translate those words that are not in the smart links to the
appropriate language.
NOTE: The CallReportMail.txt file name is the only Call Report Email Template supported. The file must
be named CallReportMail.txt to allow emailing of Call Reports to function, and there must be only one file
by that name. (12-9L9R9G)
Rendering Error in Activity Items View
When expanding the Status, or Activity Type field in the Call Reports Screen, Action Items view, the dialog will not render
correctly. The drop box (fourth level navigation) on the Action Items view will still be visible through the LOV or Calendar
pop-up. (12-9PVBOT)
Siebel Financial Accounts
Error when creating product type Retirement
An error is received after picking product type retirement in the Financial Accounts Screen, if you have checked the Display
a notification for every script error setting from internet option menu. Click on the Financial Accounts screen, and create a
new record in the Financial Accounts List applet. When creating a new record, select retirement for the Type field, and an
error is generated. The work around for this is to click the No button from Do you want debug dialog box. In the list applet
highlight another account, then highlight back to original account, and you will be able to continue to fill in the information
for the other fields. Please note that if the option Display a notification for every script error is unchecked, then the fields
will not allow proper entry, therefore the work around will need to be used with the option Display a notification for every
script error checked from the internet option menu. (12-B8ALUV)
Account Analysis Totals do not sum when Leaving Field
Charge and Required Balance fields in the Account Analysis View do not sum automatically when stepping off a record.
The work around is to sort by any column or select a field in another applet. (12-9U0ZY8)
Creating New Service Requests
In the Financial Accounts list, for financial accounts of type Account Analysis, users cannot create a new service request
when selecting All Service Request or Bill Pay SignUp from the New Service Request drop-down list. The work around is to
create two new LOV entries. For instructions, see Siebel Applications Administration Guide.
To create two new LOV entries, use the following values:

• Type: INS_SR_AREA
• Display Value: All Service Requests

• Language Independent Code: All Service Requests

• Parent LIC: Bank
• Type: INS_SR_AREA
• Display Value: Bill Pay SignUp
• Language Independent Code: Bill Pay SignUp
• Parent LIC: Bank
Note that the text is Bill Pay SignUp, not Bill Pay Sign Up. (12-9NKXMJ)
Difficulty in Setting Numeric Values From Certain LOVs
Values cannot be modified for certain LOVs in financial accounts. When leaving the control, the Pick List will drop down to
force the selection of the value again. Examples of these occurrences are the Grace Period on the CD form applet or the Limit
and POS limit on the ATM Administration view. The Type property for these fields in the respective Business Components is
set to DTYPE_NUMBER. Change the Type to DTYPE_INTEGER to solve this problem. (12-9WAFLK,12-9Y4G5C,12-
AM272Y, 12-AMXW9J, 12-AZCEAN)
Facility Financial Account Form Applet has no Values in the New Service Request Drop Down
Add the values by adding the appropriate List of Value records of type FINCORP_PROD_ADMIN_CLASS_MLOV. See
other List of Value records of the same type for an example of what to specify. (12-9NRDYR)
Financial Account Views in the Financial Administration Screen
The Site Map > Finance Administration > Financial Account views are not identical to the views in the Financial Accounts
screen. Use Siebel Tools to configure any applets that your organization requires to be identical in these two screens. (12-
6WZAXJ)
Parent Routing Number Does not Show the Correct Value for the Trust Account Detail Applet
To show the correct value in the FINS Trust Account Detail Form Agent Applet, the Text22 Control should use Field=Parent
Account Branch ABA, not Parent ABA Number. (12-9NXK3)
Holdings and Interests
Canceling the Selection of a Security Symbol
In both the Holdings and the Interests views, the Query form launched from the Security Symbol Pick applet has no Cancel
button. Click the X at the top right of the form to cancel the operation. (Not applicable to FINS CRM or to FINS MME.) (12-
9AJHPB)
Siebel Institutional Sales and Research
Receive SQL Error when drilling on Access Exceptions by Employee Chart
From the Access Exceptions Screen, if you select the Access Exceptions by Employee third level navigation tab, then drill on
one of the graph bars, the Access Exceptions list applet will not filter correctly. Navigating to any third level navigation tab
will then cause the error, An error has occurred executing a Sql statement. Please continue or ask your systems administrator

to check your application configuration if the problem persists. If you receive this error, selecting the Access Exceptions
Screen tab will refresh the Access Exceptions screen without incident. To work around this anomaly, after you have selected
the Access Exceptions by Employee third level navigation tab, query for the employee name you wish to filter for in the
Access Exceptions List Applet. You can view a filtered list by that employee. (12-BAIF9K)
Investor Profile Fields not Painted Correctly on Expansion
While in the Profile view of an Investor, expanding the Year Established or Employees fields on the Business Profile, or the
Fiscal Year End field on the Financial Profile, causes a painting issue. The pop-up Calendars and Calculator will not cover
the fourth level navigation Applet Toggle (the field where you select Business, Financial, or Management). To avoid this
issue, scroll down to the bottom of the screen before expanding these fields. (12-9SXCBW)
Siebel Needs Analysis and Applications
Applications
When creating a record in the Application Administration screen for Sales Methods, the record is not displayed in the
Applications form applet.
1. Go to Application Administration from the Site Map, click on the Sales Methods link.
2. Create a new record in the Sales Methods list applet, make sure to enter Applications in the description field.
3. Create a record in the Sales Stages as well.
4. To check the status, click on the Applications screen tab, and review the information create in the Method field in
the form applet. The value that you just created may not be displayed.
The work around for this is as follows:
1. Create a record
2. Go to Application Administration > List of Values
3. In the List of Values list applet, click on the menu and then select Clear LOV Cache
4. Go to the Applications screen. The new method will be displayed appropriately in the Applications Screen in the
Method field. (12-B7EXS6)
To activate the Auto Application button, certain administration steps need to be completed. The Auto Application button
functionality is created using two administration tools, Siebel Workflow and the Data Transfer Utility Predefined business
service. Using these two tools, the administrator can administer and set up the Auto Application button by activating the Auto
Application Workflow process, and by using the Data Transfer Utility to map the appropriate data transfer. For more
information about using Siebel Workflow and the Data Transfer Utility see Siebel Workflow Administration Guide for
Financial Services, v. 7.0. on SupportWeb. In addition, the sample data contains an example of the workflow and Data
Transfer Utility for the Auto Application button. (12-B6TFCQ)

Auto Application Button
Using the Auto Application for a Selected Product
The Product field may not appear to contain data in the following cases:
When using the Auto Application button in the Contacts or Companies screen
When a product has been chosen in the Application screen Apply field
In these cases, users can click on the Product name field to verify that the product is included in the application record. (12-
9YJKRT)
Needs Analysis Script
SmartScript for Needs Analysis Views
When a user is completing a Needs Analysis for a customer, she may use a script to assist with the Needs Analysis session.
When the script session is completed, and the user clicks on the Finish button to return to the Needs Analysis view, she may
not be returned to the record that she was editing. However, she can return to the record by using the History menu to select
the appropriate view and record. (12-9YJKSA)
Siebel Securities
Associating a List with a Security
You can associate a list of clients with a security. In the Securities screen, find the Security with which you want to associate
a list of clients and click the Lists view tab. In the Lists applet, click New. In the Add Lists dialog box, select the name of the
client list you want to associate with the security and click OK. Fill in the other relevant fields. Save the record by choosing
the Save Record from the applet-level menu button or by using the shortcut keys. Do not step off the record to save it, or an
incomplete data record may result. (12-9PP9Y3)
Securities; Financial Administration
Adding a Market Entry Info Record
When adding a new security, add details by clicking New in the Market Entry Info applet. The first time a new Market Entry
Info record is created and there are no other Market Entry Info records for any of the Securities in the list, the new record
does not appear to be saved. Click the All Securities tab to refresh the screen before adding the first Market Entry Info record
and explicitly save that record using the Save menu option. (Not applicable to FINS CRM or to FINS MME.) (12-9PAL2U)
Siebel Teller
Using the Go button on the Contact Financial Accounts Summary Teller List Applet, without first choosing a transaction in
the adjacent combo box, results in an error. The work around is to modify the FINS Teller Start session by adding a decision
point that checks the value of the SR Sub Type field. If it is null, then it should be set to a default value, for example00 –
Deposit. (12-B000EB)

Navigating to the Branch Administration | Settlement view generates an error. The error message reads, Error running sub-
process “FINS Teller VBC Connector.... To workaround this error, enable the integration workflows as documented in the
Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide. (12-BA8BZC)
Using the FINS IFX XML Connector results in XML Parser errors on the AIX platforms
If you are getting XML parser errors on the AIX application server, then perform the following steps.
1. Check that the case of the ifx101.dtd file is lowercase - not uppercase.
2. Check that line 32 in the teller.dtd file reads <!ENTITY % IFX SYSTEM "ifx101.dtd"> not <!ENTITY % IFX
SYSTEM "IFX101.dtd">.
3. Check the <!DOCTYPE> directive being used specificies the .dtd file on the local file system - not using a URL.
This is set in the FINS IFX XML Outoing workflow.
4. Make sure the case of the directories where the .dtd file is stored are all lowercase (Not applicable to FINS CRM or
to FINS MME.) (12-B2417H)
Integration messages initiated from the Teller Drawers screen fails when the user does not have a teller position
When the user navigates to the FINS Teller Drawers screen, an integration message is automatically sent. If that user is not a
valid teller (that is, assigned to a position that has a position type of Teller, Teller Supervisor, or Branch Manager), then this
error is generated. To work around this error, assign the user a valid teller position. (Not applicable to FINS CRM or to FINS
MME.) (12-AZWH5R)
Multilingual Deployment Support
The following is applicable to the non-English locales. Multilingual List of Values (MLOV) is not supported for Siebel
Teller. However, standard translated List of Values is supported. (Not applicable to FINS CRM or to FINS MME.) (12-
9YBTNP, 12-9YBTO5, 12-9YQXMH, 12-9YQXNI)
When Multi-lingual LOV’s are Enabled, Error Messages Occur Stating That List of Values do not Exist
The following user actions appear to not return the correct data:
Clicking the Go button in the Contacts Teller Summary view
Clicking the Teller Session button in the Contacts Teller Summary view
Clicking the Walkup Session button in the Contacts More Info view
Creating a new customer session in the Teller Activities screen
Note that these issues only exist when multilingual LOVs are enabled. By default, multilingual LOVs are not enabled in the
Siebel eFinance application.
The fix for this in Siebel Tools is:
BC FINS Teller Batch:
1. Change search spec to [Type] = LookupValue(‘tODO_TYPE”,’teller”) and [Sub

Type]=LookupValue(‘tODO_TYPE”,”Batch”).
2. Change predefault value for field Type to Expr: “LookupValue(‘tODO_TYPE",’teller").”

BC FINS Teller Customer Session:
1. Change search spec to [Type] = LookupValue(‘tODO_TYPE”,’teller”).
BC FINS Teller Drawer Settlement:
1. Change search spec to [Type] = LookupValue(‘tODO_TYPE”,’teller”) and [Sub

Type]=LookupValue(‘tODO_TYPE”,”Drawer Settle”).
Workflow FINS Teller Session Connector:
1. Change step Create End Of Day Activity, field type to LookupValue(‘tODO_TYPE”,’teller”).
Seed Data:
1. Add list of value entries for Teller in all supported languages to the LOV type TODO_TYPE. The language
independent value for all supported languages must be teller. (Not applicable to FINS CRM or to FINS MME.) (12-
9WYCPJ)
Siebel ERM Options
Catalog Administration
Adding Solutions
In the Site Map > Catalog Administration > Solutions view tab, a situation may occur where Solutions cannot be added. This
is because the Solution descriptions are very long and the OK button is not accessible from the window, To avoid this
problem, be sure the Solution name is not a long name. (Not applicable to FINS CRM or to FINS MME.) (12-9U7N3N)
Data Administration
Cannot Edit Contact Coverage Role
In the Site Map > Data Administration > Contacts screen, you cannot change the Coverage Role for your organization’s
contacts using Siebel ERM. However, you can change the Coverage Role associated with a contact in Companies > Coverage
Team > Coverage Role field in any Siebel high interactivity application. These applications include Siebel eFinance, Siebel
eInsurance, or Siebel eHealthcare. (Not applicable to FINS CRM or to FINS MME.) (12-9WTTRA)

Siebel eTraining
Deleting Enrollments in Training Administration
You cannot delete Enrollments records in the Site Map > Training Administration > Enrollments screen. However, you can
delete Enrollments in the Site Map > Training Administration > Courses > Current Enrollments view tab. (Not applicable to
FINS CRM or to FINS MME.) (12-9TLL8Q)
General Product Options

Access Exceptions
Adding a Contact with Basic Access to a Premium List
A Contact with a Basic Access Level can be added to a list that is restricted to Premium Contacts. If you query for a contact
immediately after adding it, the contact will not appear in the list. Trying to add it again generates the following prompt
message: The selected Contact has already been added to the list. This prompt prevents duplicate entries from being added to
the list. (12-9PHLP2)
Activities
Adding Messages to an Activity
Before creating or modifying a message in the Messages view of the Activities screen, click Show More in the top Activities
applet to make all fields available. (12-9SCOCC)
Multilingual Environment in Activities
The Time and the Expenses views in Activities screen are not supported in a multilingual environment.. If your Siebel
Financial Services applications are running in a multilingual environment, your organization’s users will have full unilingual
support for the Time and the Expenses views in the Activities screen, but will not be able to create records in these views.
(Not applicable to FINS CRM or to FINS MME.) (12-9Y9VL1 and 12-9Y9VLZ)
Auto Application Button
Activating the Auto Application Button
To activate the Auto Application button, certain administration steps need to be completed. The Auto Application button
functionality is created using two administration tools, Siebel Workflow and the Data Transfer Utility Predefined business
service. Using these two tools, the administrator can administer and set up the Auto Application button by activating the Auto
Application Workflow process, and by using the Data Transfer Utility to map the appropriate data transfer. For more
information about using Siebel Workflow and the Data Transfer Utility (including an example of how to set up the Auto
Application button), seeSiebel Business Process Designer Administration Guide for Financial Services. In addition, the
sample data contains an example of the workflow and Data Transfer Utility for the Auto Application button

Calendar
Adding Users to Recurring Activities - DB2/390
In certain circumstances, adding employees to a recurring activity will generate an error message. While the error does not
interfere with the adding of an employee, it does require using the Close window button at the top of the dialog (X) to close
the Employees MVG. The OK and Cancel buttons cannot be used to dismiss the dialog. This behavior has only been seen in
DB2/390 environments. (12-BAJIX6)
Contacts
When adding an opportunity in the Opportunities view tab, an error message may occur when setting the Sales Cycle field.
To make sure the value of the record is saved, close the error message, and step off the record. Go back to the record, reselect
the value for the Sales Cycle field, and then step off the field to the next column. The record is saved. (12-B24Q20)
Receive Error when Copying a Record in Contacts-Enforce View
Trying to copy a record from the Contacts-Enforce view in the List Management Screen will generate an error. This anomaly
only occurs in NLD. (Not applicable to FINS CRM or to FINS MME.) (12-B6IHWU)
Contacts Manager Explorer View on Oracle
Drop and recreate the following index in the S_POSTN_CON table. This may be implemented to improve response time in
the Manager’s Explorer View, in the Contact screen, if performance is slow. S_POSTN_CON_M1 (POSTN_ID,
CON_LAST_NAME, CON_FST_NAME). (12-AX6HDR)
Companies
Choosing Company Activity Plan Templates
The Activity Plan Templates available for selection in the Template field on the Companies screen, Activity Plans view tab,
are templates with a type value of Account, not a type value of Company. These templates can be added and modified on the
Siebel Assistant Administration screen, Activity Plan Templates view. (12-9NRDAO)
Correspondence
Sorting Correspondence Requests
The Advanced Sort feature is not available in the My Correspondence Requests view > Requests list applet. Only the last sort
criteria will be applied if a user attempts to use this feature. (12-9OP4P5)
Coverage Management
Deleting the Primary Team Member
You can use Ctrl+D to delete the primary team member from the Contact or Company Coverage Team views. To disable this
deletion capability, set the No Delete property on the Contact or Company Coverage Team view applets to TRUE. (12-
9T80CP, 12-9T80CR)

Enterprise Integration Manager
The following index change will improve performance of the EIM Merge for EIM_ACCOUNT.
CREATE INDEX SIEBEL.EIM_ACCOUNT_T19
ON SIEBEL.EIM_ACCOUNT
PRIQTY 720
SECQTY 14400
ERASE NO
FREEPAGE 0
PCTFREE 20
GBPCACHE CHANGED
BUFFERPOOL BP2
CLOSE YES
PIECESIZE 2 G
COPY NO
DEFINE YES
(Not applicable to FINS CRM or to FINS MME.) (12-B46FLJ)
The following index change will improve performance of the EIM Merge for EIM_CONTACT.
CREATE INDEX SIEBEL.EIM_CONTACT_T26
ON SIEBEL.EIM_CONTACT
PRIQTY 7200
SECQTY 14400

ERASE NO
FREEPAGE 0
PCTFREE 20
GBPCACHE CHANGED
BUFFERPOOL BP2
CLOSE YES
PIECESIZE 2 G
COPY NO
DEFINE YES
(Not applicable to FINS CRM or to FINS MME.) (12-B4T23S)
List Manager
Receive Error when Copying a Record in Contacts-Enforce View
Trying to copy a record from the Contacts-Enforce view in the List Management Screen will generate an error. This anomaly
only occurs in NLD. (Not applicable to FINS CRM or to FINS MME.) (12-B6IHWU)
Literature
Copy Category dialog does not have an OK button
When copying a Category on a Literature Item, a dialog will appear prompting you to enter a value for the copied category.
This dialog is missing an OK button. To work around this issue, instead of copying categories, create new ones by selecting
the New button on the Category List Applet. (12-B343R7)
Cannot Remove Symbol from Literature Items
Once a security symbol, or Ticker, has been associated with a piece of literature, that association cannot be revoked. This is
because the Delete button is missing from the Symbol Pick Applet. (12-B33MP3)
Adding an Attachment
When adding an attachment from a non-Siebel application to a Siebel record, you must use the Browse button to locate and
select the attachment file. (12-9PHM5T)
Emailing Multiple Pieces of Literature
You can attach multiple pieces of literature to an email message. The field that displays the name of the attached files
displays only the last item attached, not the complete list. (12-9PBAV6)

Opportunities
Generating report for FINS Investment Deal Pipeline - Primary Rep yields report.
This report contains several subreports that incorporate data from other business components. Therefore, in order to generate
this report, create Equity and Syndicate data for the opportunity first by doing the following. In the Opportunity Screen >
Opportunity Detail view, select Equity from the forth level navigation. In the Equity and Syndicate applets, create a new
record. The report will generate properly. (Not applicable to FINS CRM or to FINS MME.) (12-AMAL1R)
Opportunities Filter
The persistent filters previously offered out of the box in Siebel 7.0.3 have been turned off by default. This provides
customers with a faster response time when visiting the Opportunity views. Customers wishing to use the persistent filters are
required to activate these applets prior to deploying. (Not applicable to FINS CRM or to FINS MME.) (12-AST95R)
Administering Secure Opportunities
The Opportunities Administration view, located in the Data Administration screen, does not list secure opportunities unless
the logged-in administrator is a member of the opportunity sales team. There is no view, administrative or otherwise,
available in the application where the logged-in user can view secure opportunities for which the user is not a member of the
sales team. (12-9UY28B)
Changing Opportunity Chart Types
When selecting a chart type on some Opportunities charts, the selected type may not match the type displayed. All the listed
types are available, however, they may not match the selected value. (12-9W0N8Z)
Deleting Opportunities
Deleting opportunity records from the Site Map >Data Administration > Opportunities Administration view tab when using
an Oracle database may cause an error that prevents the record from being deleted. The reason is that the SQL being
generated for this command is not correct because the Primary Position Id is a joined field. To eliminate the error message
when deleting opportunity records in Site Map > Data Administration > Opportunities Administration view tab, remove the
User Property: Deep Delete/Opportunity Attachment from the Opportunity Business Component. Although this eliminates
the error, it also causes any attachment files associated to the deleted opportunity record to remain on the file system, even
after the opportunity record is deleted. You can run a script on the file system to remove these stray files. (12-9VXW9U)
Drilling Down on Opportunities
After drilling down on an opportunity record from the Opportunities screen, and then returning to the Opportunities screen
using the thread bar or history, the opportunity records may be displayed in an order that is different from the original order.
(12-4U3UK7)
Modifying the Opportunity Sales Team
In some instances, after adding or deleting records in the Opportunities screen > Sales Team view tab, the list of Sales Team
members visible in the list applet differs from the list shown in the Opportunity Sales Team list dialog box (opened by
clicking the Sales Team field icon on the Opportunity form applet). Leaving the Opportunities screen, and then returning to
the Opportunity Sales Team view, will synchronize the two lists. (12-8JCR27)

Navigating to Opportunities Using History
When attempting to navigate back to the Opportunities screen > More Info view tab from other screens using History, the
user may not always be returned to the More Info view tab. The user may be returned to the My Opportunities view. To
return to the view, the user must select the More Info view tab again. (12-973LDO)
Viewing Opportunity Industries
In some instances, the Industry field on an opportunity record may be blank, even though there are one or more industries
associated with the opportunity. This field will be filled once the select button in the field is selected, opening the
Opportunity Industries association dialog box. (12-8TEX3R)
Persistent Filters
Last-Run Filters
When the user selects an existing Persistent Filter, clicks Go, and then modifies any field, the last-run filter remains in the
Select Filter dropdown. This is consistent with the manner in which PDQs operate in Siebel 7.0. (Not applicable to FINS
CRM or to FINS MME.) (12-69D2NW)
Product Administration
User Administration - Employee
When using the copy function for the creation of a new employee, within User Administration, the following error occurs
when stepping off the newly copied record, You have attempted to insert the value for column “FST_NAME in table
‘s_CONTACT” twice in the same statement. The user should selectUndue Record from the menu and proceed with adding a
new record. (12-AROUAW)
Start and End Dates in Product News List Applet
In the Product Administration > Product News list, the Start and End date fields do not contain an icon for the calendar pop-
up. To use the calendar pop-up, navigate to the Product Administration screen and, in the Show drop-down list, select
Product News. In the Product News form, click the select button in the Start and End fields. (12-9VVOID)
Sales Assistant
Setting up Sales Stages
When adding Sales Stage records to a Sales Method on the Siebel Assistant Administration screen, make sure the Sales Stage
field is not longer than 30 characters. The text field accepts strings up to 50 characters long, but this conflicts with the field
length in other areas of the application. If the field is longer than 30 characters, you may get the following error message:
Data value for field FINS Sales Stage is larger than the limit 30 defined in the database. Please type fewer characters to make
sure that your data is saved in the database. (12-9N2GYU)

Siebel Anywhere
Version Mismatch for Siebel Anywhere component Siebel Client Executables
1. Connect to Server.
2. Go to Siebel Anywhere Admin Screen.
3. Create new Configuration for Siebel Financial Services.
4. Create upgrade kit for fins cfg. Activate and apply the upgrade kit.
5. Distribute the FINS configuration.
6. Connect with other client to the same database. It should upgrade Fins cfg component, but it gives a version
mismatch error message, siebel Client Executables Actual Version 7.0.4 FINS [14065], Version Minimum 7.0.4
FINS [14067].
7. This is due to seed data not generated for Build 14067.
A simple workaround is to change the Min Version to the current build number 7.0.4 FINS [XXXX] and it works fine.
Applicable for all Languages. (12-B94FSR)
Siebel Reports Server

When doing Smart Search on an agreement number in a generated report use quotation marks such as "1-74" around the
agreement to complete an accurate search. (12-AK8M8S)
Currency Format and Total Calculation in Receipt of Payment Report
The following issues are only applicable for the German locale. In the Receipt of Payment report, the currency is displayed in
$, not euros; also, the Total amount is miscalculated in the Zahlung (Total) column. (12-9Z6H6R)
Date Format for Non-ENU Actuate Reports
The following issue is applicable for all non-American English locales. Some dates in non-ENU Actuate reports are
formatted as mm-dd-yyyy. (12-9PXMV0)
Importing Siebel Financial Services Reports to the Reports Server
Siebel Financial Services offers several reports tailored for financial services customers. Before these specialized reports can
be viewed, they must be imported to the Reports Server. For instructions, see Siebel Server Installation Guide for UNIX
version 7.0.2. To import Siebel Financial Services reports, change the Siebel Reports Server files procedure in Siebel Server
Installation Guide for UNIX version 7.0.2. Add the following instructions after step 2 on page 12-9:
• Navigate to SIEBEL_HOME and at the command prompt, type:
• ACTUATE_HOME/bin/acimport -home ACTUATE_HOME -if \’siebel Reports/ language" -force -input

reports/reports_fins.acf
NOTE: You can import standard Siebel reports and specialized Siebel Financial Services Reports.

Search Alias in French Actuate Reports
The following Actuate reports in the French release have search aliases in English:
FINS Call Report Detail
FINS Call Report Summary
FINS Commercial Banking Client Profile
FINS Demo Health Providers by Product - Healthcare
FINS Demo Health Providers by Specialty - Healthcare
FINS Investment Deal Pipeline - Primary Rep
Opportunities - By Product Line
FINS Portfolio Roll-Up - Relationship
FINS Investment Banking Client Profile
(12-9WCHD1)
Siebel Sync
Recurring Items Edits do not Synchronize Correctly
When you create a recurring item in Outlook, and synchronize with Siebel Systems, the item synchronizes properly as a
recurring item. If you edit the start date of one of these items in Outlook and perform another synchronization, the items no
longer appear as recurring items in Siebel Systems. Instead, they are stored as separate calendar items. (12-9NRI4T)
Switching from Synchronization to Import
Do not change synchronization direction while using Siebel Sync. The synchronization engine does not support changing the
direction of sync after an initial synchronization has been completed using one direction. If the synchronization direction is
changed, duplicate records may be generated. If the synchronization direction must be changed, contact Siebel Professional
Services. (12-9OT3WJ)
Siebel Financial Services Wireless Applications

Digest Too Large Errors Received for Some Wireless Browsers
Some wireless gateways and browsers impose a limit on the number of bytes that may be sent to a wireless device in a WML
deck. When this limit is violated, users encounter error messages such as Digest Too Large or Entered Text Too Long, or the
browser may never finish downloading the deck. To address such errors, reduce the number of links or the amount of content
included in Siebel Wireless Details views, or reduce the number of links or records returned by Siebel Wireless Display
views. Siebel Wireless applications have been configured to return only three records with each list to minimize the chance of
these errors occurring. For instructions about how to change the number of records returned by Siebel Wireless lists, see
configuring Siebel Wireless in Siebel Wireless Administration Guide. (Not applicable to FINS CRM or to FINS MME.) (12-
6DXFS5)

Siebel Wireless for eFinance
Dutch Employee Facing Wireless Translates the Word Submit Differently
The following issue is only applicable for the Dutch locale. The word submit is translated in two ways, Indienen and Start.
This translation issue does not affect functionality, performance, or data. (Not applicable to FINS CRM or to FINS MME.)
(12-9WCM89)
Receive Unwarranted Error When Drilling Down on a Contacts Work Number
You will see the following error message if you select a Calendar item, select its Company, view the Contacts in that
Company, create a brand new Contact, and select the Work Number link for that Contact: This record has been modified by
another user. Please Continue. When the user presses OK, a compile error appears on the wireless device. The first error is
unwarranted and the second error (the compile error) will not cause any data or session issues. When you receive the compile
error, go back to the previous view using the appropriate Back function for your device, and then select the Main Menu. The
Main Menu appears and the contact is saved. At this point, you can add a Work Number to the contact. (Not applicable to
FINS CRM or to FINS MME.) (12-9WCM7J)
Unable to create a New Calendar item in Oracle, French
The following issue is only applicable for the French locale. This issue only affects users on Oracle. When creating a new
Calendar item, if a user clicks Submit, an error message is received. To avoid this error, Siebel administrators should use the
following work around:
Change the following PDQ:
PDADef_Uncompleted Activities
for the Object: Action from:
“Action”.Search = "[Status] <> ""Done"""
to:
“Action”.Search = “[Status] <> LookupValue(“”EVENT_STATUS””, “”DONE””) OR [Status] IS NULL” (Not

applicable to FINS CRM or to FINS MME.) (12-9UAAX0)
Siebel Wireless Banking and Brokerage
Automatic Login not Supported
The Siebel Wireless Banking and Brokerage application supports two login permission levels:
1. User Name and Password. Wireless users must enter their full user name and password to access Siebel Wireless
Banking and Brokerage.
2. Password Only. Wireless users must enter only their password to access Siebel Wireless Banking and Brokerage.
Their user name is granted automatically and need not be entered on the wireless device when logging in.
Siebel Wireless Banking and Brokerage does not support the Automatic Login permission level. Auto Login allows a
Wireless user’s username and password to be granted automatically when that user accesses the Siebel Server, and then that

user is taken directly to the appropriate Siebel Wireless Main Menu without logging in manually. (Not applicable to FINS
CRM or to FINS MME.)
Siebel eInsurance
Configuration for the All Agent view on DB2 UDB for zSeries Platform
The following configuration change may improve performance for the All Agents view. In Siebel Tools, query on FINS AG
All Agents List Applet, delete the search specification, [Is Agent] = “Y”, and then compile a new .SRF file. (12-B4CQ81)
Configuration for the All Providers view on DB2 UDB for zSeries Platform
The following configuration change may improve performance for the All Provides view. In Siebel Tools, query on FINS
Health Provider List Applet, delete the search specification, [Provider Flag] = Y', and then compile a new .SRF file. (12-
B4CQ81)
Service Providers
Adding New Contacts in Referrals
If a new referral also involves adding a new contact, add the new contact from the Contacts screen before entering the
referral. Adding a new contact directly in the Contacts MVG in the Referrals view is not supported. (12-99VRJB)
Siebel Personal Lines Claims
INS Claims Insured Property View
The view, INS Claims Insured Property View, needs to be compiled into the Financial Services application. Log in to Siebel
Tools and navigate to Views. Query for the view named INS Claims Insured Property View. Copy the record and give the
view a new name. Add the new view to the INS Claims Screen under the Screen object, and recompile the .srf file. (12-
BBBI5F)
Siebel eHealthcare
Configuration for the All Providers view on DB2 UDB for zSeries Platform
The following configuration change may improve performance for the All Provides view. In Siebel Tools, query on FINS
Health Provider List Applet, delete the search specification, [Provider Flag] = Y', and then compile a new .SRF file. (12-
B4CQ81)
Configuration for the All Members view on DB2 UDB for zSeries Platform
The following configuration change may improve performance for the All Members view. In Siebel Tools, query on FINS
Member List Applet, delete the search specification, [Member Flag] = Y', and then compile a new .SRF file. (12-B4CQ81)

Audit Trail
Enabling PCP History on 390
Workaround 1: Use Mvg instead of Join for New and Old PCP. Change the configuration so that it uses MVG instead of join
to retrieve the old pcp name and new pcp name. From SQL point of view, it will generate three separate SQLs to retrieve the
information, which will avoid the usage of predicate over New_VAL and OLD_VAL column. Here are the details:
1. Create two new links from FINS Member PCP History to Contact. The source field of the link will be New Value or
Old Value, the dest field of the link will be Id.
2. In FINS Member PCP History Buscomp, delete the joins of Old PCP and New PCP, and create two multiple value
link using the above two new links. You need to specify New Value or Old Value as the source field of the multiple
value link respectively.
3. In FINS Member PCP History Buscomp, change the field of Old PCP Last Name, Old PCP First Name, New PCP
Last Name, and New PCP First Name to be a MVF instead of join field. Note: Siebel Tools will not allow you to
change a field from SVF to MVF directly, you need to delete them and create them again. Pros: this will have
minimal modification and impact on the applications. Cons: It will generate 2 extra SQLs for each history record.
It also won't allow you to search on the old and new PCP on UI.
Workaround 2: Add columns with shorter width to S_AUDIT_ITEM table. This needs to test out before adopting this
approach.
1. Create 2 new columns of length 250 in S_AUDIT_ITEM table call SNEW_VAL, SOLD_VAL.
2. Add these two columns in Audit Trail Item 2 buscomp for the two new columns.
3. Specify the post default value of these two new fields to be left([New Val], 250) or Left([Old Val], 250).
4. In the FINS Member PCP History buscomp , add these two new columns. Change the join spec to use these two new
columns instead of the NEW_VAL and OLD_VAL. Pros: good performance, maintain the same functionality as
other platform. Cons: Making changes to general audit trial modules may create upgrade issues later. (Not
applicable to FINS CRM or to FINS MME.) (12-AVUQPY)
Siebel Analytics
Siebel Answers
Financial Services Sales, Financial Services Service and Financial Services Marketing
Marketing Analysis Categories Applet on the Marketing Homepage Not Functional
The Marketing Analysis Categories applet on the Siebel Marketing Homepage contains functionality no longer supported in
Siebel 7.0.3. This applet will not function. To eliminate any user confusion, disable the applet in Siebel Tools. The applet
name in Siebel Tools is Marketing Analysis Predefined Categories List Applet – Homepage. (Not applicable to FINS MME.)
(12-A441L5)

Company Claim Frequency
The measure Company Claim Frequency is inaccurately named as Company Contact Frequency under the Claim Facts
folder. The steps to fix this are given below:
1. Launch the Siebel Analytics Administration Tool.
2. Open the Siebel Analytics Repository file and open the Financial Services Sales folder.
3. Open the Claims folder and then the Facts: Claim subfolder.
4. Double-click the measure Company Contact Frequency and rename it as Company Claim Frequency. (Not
applicable to FINS MME.) (12-ARC38B)

If an environment is not correctly configured, for example a pie chart displaying Japanese data is rendered by a server
running in a Western European code page, the Japanese text will appear as???. This behavior is limited to the displaying of
the values and in no way affects the processing of the data.
Multiple Siebel Analytics servers can be configuring to access the same data source. In the model, where a site needs to
render Chinese, Japanese, and Western European regional data as charts, three servers should be configured to access the
same data sources.
page processing on development and maintenances of the Analytics Applications. (Not applicable to FINS MME.) (12-
BE3XFF)
Siebel eCustomer
Siebel eBanking
Calendar Pop-up is not Fully Localized
The following issue is applicable for all non-American English locales. In eBanking, some payment requests allow
the user to specify a date. A calendar pop-up is provided to assist the user in selecting a date, and if applicable, a
time for the request. Note that the time and time zone selection controls are not localized in Siebel eBanking.

Siebel eBrokerage
eBrokerage views are not exposed out of the box for the eCustomer application
Currently, eCustomer ships with the eBrokerage views available, but unexposed. Customers wishing to use the eBrokerage
views are required to first add the appropriate screens (for example Relationship and Trades), and then add the respective
eBrokerage views to the screens in Siebel Tools (12-B90MYZ)
Siebel Interactive Selling Suite Related Options

Siebel eSales
The Get Advice Link in eCatalog
If an eAdvisor project is associated with a catalog (in Catalog Administration) and is deleted from Interactive Designer, the
Get Advice link next to the Catalog still exists. Clicking on the link will launch the default project or return an error message.
Work around solution: delete the Interactive Designer Project field of the catalog in Catalog Administration before deleting a
project from Interactive Designer. (Not applicable to FINS CRM or to FINS MME.) (12-9SDJG9)
Marketing Related Options

Siebel eEvents Manager for Finance

Adding Partner Records
When adding new Partner records to a SubEvent in the Partners view, there is no currency control associated with the Value
field. Users can add a number to this field, and the fields can be used in calculations within the Partners view. However, this
will be a limitation if users need to add different partner value fields in different currencies. If necessary, administrators can
configure a solution by adding an extension table with a currency column, and then exposing a currency selection to the user
interface. This will allow users to store and associate different currencies with different partner records. (Not applicable to
FINS CRM or to FINS MME.) (12-7WOG3X)
Adding Vendor Billing Records
When adding new billing records to a vendor in the Sub-Events screen > Vendors view, users will note that there is no
currency control associated with the Rate field. Users can add a number to this field, and the fields can be used in calculations
within the Billing view. However, this will be a limitation if users need to add different billing items in different currencies.
If necessary, administrators can configure a solution by adding an extension table with a currency column, and then exposing
a currency selection to the user interface. This will allow users to store and associate different currencies with different
billing records. (Not applicable to FINS CRM or to FINS MME.) (12-84BMIJ)
Displaying Additional Columns in SubEvents-> Collateral
When choosing the Columns Displayed option from the applet level menu in the Collateral view, users may note two
columns available for display, Local and Request. These columns reflect data that exists at the database level, but are not
required to be displayed to the user because they are not Read and Write views. Therefore, even though users may see these
columns, they will not appear on the Collateral list applet. (Not applicable to FINS CRM or to FINS MME.) (12-9Q0LGF)
Duplicate Registration Records
It is possible to create duplicate registration records for the same contact. The system will not warn a user if a contact has
already been added to the registration record. The system will allow the user to add the contact a second time, creating a
duplicate registration record. Administrators may be able to configure a work around by adding a search specification to the
Choose Contact dialog box. (This dialog box appears when you select the name for the contact you wish to add). The search
specification should filter out contacts that have been added as registrants for that event and show only contacts who are not
currently registered for the event. Users could not choose the same contact twice to register for the same event. (Not
applicable to FINS CRM or to FINS MME.) (12-7R4GPV)
Navigating with Default Filters
When users have a default filter applied to either the Events > Sub-Events screen or Events > Sessions screen, navigating
away from the More Info view, and then returning to it, causes the application to lose its context. Users will have to reselect
their desired record when they return to the More Info view with a default filter applied. (Not applicable to FINS CRM or to
FINS MME.) (12-9YJY07)
Preparing for an Event
In the Sub-Events screen > Partners view, users can associate partner companies with the event. However, only one record
per partner can be created within this view. Each partner can only be listed once as having a single role with respect to each
event. (Not applicable to FINS CRM or to FINS MME.) (12-6RMZB9)
Registering a Company
The system will not warn the user about creating duplicate registration records for the same company. Therefore, users
should exercise caution when creating registration records, and may want to check the existing Company Attendees view to

see if the company is already registered before creating a registration record for that company. (Not applicable to FINS CRM
or to FINS MME.) (12-9ULA1M)
Registering a Contact
When adding new Contacts or Employees as Registrants in any of the Events screens, users must explicitly save each new
record by choosing the Save button. Records, in which users only implicitly save by stepping off the record, will not be
saved. Therefore, the following steps are required:
1. Navigate to the appropriate event-level screen (Parent Events, Sub-Events, or Sessions).
2. Click the Registration view tab.
3. Click New.
4. Click Select in the Last Name field, select a Contact Name from the Pick Contact dialog box, and click OK.
5. Click Save.
NOTE: You must save the record by stepping off the record, using the keyboard shortcut, or clicking the
Save button before you register another contact. If you click New before you save the contact, the record
will not be saved. (Not applicable to FINS CRM or to FINS MME.) (12-9STNTB)
Tracking Vendor Billing
Billing records for Vendors currently do not have a currency code associated with the Billing Rate field. Therefore, users can
only track billing records in a single currency. If desired, administrators can use an extension table to add a currency column
to the database. Through configuration, this column can then be exposed in the user interface. (Not applicable to FINS CRM
or to FINS MME.) (12-84BMIF)
Viewing the Session Calendar
Navigating to the Sub-Events screen > Session Calendar view shows this calendar with the current date highlighted. To see
the Sessions for that sub event shown in the calendar display, users have to explicitly choose the date of the sub event from
the date controls. (Not applicable to FINS CRM or to FINS MME.) (12-9W9EMP)
Web Service Related Options
Seed Responsibilities for Customer Applications
When you install Siebel eBusiness Applications, you are provided seed data that is related to user registration, authentication,
and user access to Siebel applications. Responsibility records are provided as part of the seed data to help define user
responsibilities specific to your implementation, see Table B-3 of the Authentication and Access Control Administration
Guide for more information. The following seed responsibilities are provided for the Siebel Financial Services Customer
Applications.
Name Description Used by These Applications
Unregistered Visitor Views provided for anonymous Customer applications

browsing

Registered Customer Views provided for a typical user Customer applications
Registered Customer – Wireless Views provided for a registered Wireless Banking and Brokerage
Banking Wireless Banking and Brokerage user
on a wireless device
The Web Anonymous User, Web Registered User, and Web Delegated Customer Administrator seed responsibilities are not
applicable for the Siebel Financial Services Customer Applications. (#12-9TQE8I)
Siebel eService
List of Values
Contact Us in eBrokerage
The following issue is only applicable to the French locale. In the List of Values, the translation of Contact Us to French
must be consistent in the following two List of Values; ACCOUNT_TYPE and FINS_ACCT_BUS_TYPE_MLOV. (12-
AZECGJ)
Trade Validation
Trade Validation in eBrokerage
eBrokerage ships with simple validation rules, such as requiring a source or target account and type of trade. For more
complex rules, the Siebel Administrator can define rules using Siebel Tools Reference, the Events and Methods applet, and
Business Component Events and Methods in Siebel Object Interfaces Reference. (12-5M5E7E, 12-2OSIBU)
Workflow
Add Interest Workflow Generates Activity not Visible in eBrokerage
When a customer adds an interest to the Relationship - Interests view in eBrokerage, an activity is created, but cannot be seen
in the Relationship Activities View. In order to correct this, the Siebel administrator must make a change in Siebel Tools. The
administrator must change the link (named Contact/Action Contact Company Activities Web Link) used by the Action
Contact Company Activities Web business component from a one-to-many relationship to a many-to-many relationship. The
link’s Source and Destination fields need to be removed, and the S_ACT_CONTACT intersection table should be used, with
the Inter parent field=CON_ID and Inter child field=ACTIVITY_ID. This fix has no data model change. (12-6Z18JV)
New Interest andHolding Notification in eBrokerage
Currently, there are two workflow processes that create an activity notifying a user that a customer has updated their interests
or holdings profile. These workflow processes are not translated, and will not operate as expected in language builds other
than ENU. To localize these workflows, the Siebel Administrator must navigate to Workflow Administration and locate both
the Holdings Workflow and Interests Workflow. The following example outlines the steps to correct the Holdings workflow,
but the same steps are applicable to the Interests workflow.
The user must then make modifications to five steps in the Workflow Process view. The user must drill down on each of
these steps and translate the text in the Value fields as follows:
New Holding Alert

Edit Holding Alert
For New Holding and Edit Holding, the following fields must be translated: Category, Duration, Priority, Target, and Unit
Type.
New Interest Workflow
New Holding Activity
Edit Holding Activity
For New Interest Workflow, New Holding Activity, and Edit Holding Activity, the following fields must be translated:
Priority, Status, and Type. (12-9UOJXV)
Siebel Connectors
LOV Values missing
In FINS_UNIT_OF_MEASURE_MLOV, many Values are not activated which are required for SAP Connector to work
properly. Also some of the UNIT_OF_MEASURE values are also missing. Those missing are "Bag", "Case", "Dollar",
"Dozen", "Gram", ‘thousand", "Foot", "Hour," and "PC". These can be added by connecting to the application as a connected
client and adding to the Siebel repository. Once connected, choose Site Map, and proceed to Application Administration and
then choose List of Values View. Add the missing values for UNIT_OF_MEASURE as well as activate the
FINS_UNIT_OF_MEASURE_MLOV to make it work. This was not done in Siebel 7.0.4, as no repository changes were
allowed and this will be fixed in Siebel 7.5 (Not applicable to FINS CRM or to FINS MME.) (12-B1SFAV)
Upgrade
During the upgrade process data stored in S_ORG_INT_SERV from prior releases is not migrated to FINS 7.0.4. Check
Siebel Support Web to obtain proper script for migrating this data. (12-B6QWUB)
Globalization
Internationalization
Date Display format
The following is applicable for the Brazilian Portuguese and Danish release. The display format will appear as
Month/Day/Year. This does not affect functionality or data storage. (12-AK6L59, 12-ALF2DT)
NOTE: FINS MME does not support a Danish release.

Environment Variable in non-1252 Code page Environments
The following is applicable for all non-1252 code page environments. It is required to set the environment variable
SIEBEL_CODEPAGE to the correct code page when starting the Siebel webserver plug in. For example, for a Japanese
environment the setting should be, SIEBEL_CODEPAGE=932. (Not applicable to FINS CRM or to FINS MME.) (12-
B3MNMZ, 12-B347LF)
Multilingual Environment in Activities
The Time and the Expenses views in Activities screen are not supported in a multilingual environment. If your Siebel
Financial Services applications are running in a multilingual environment, your organization’s users will have full unilingual
support for the Time and the Expenses views in the Activities screen, but will not be able to create records in these views.
(12-9Y9VL1 and 12-9Y9VLZ)
No MultiLingual Environment for Siebel eEvents
Siebel Financial Services 7.0.4 does not support multilingual deployments for eEvents Manager for Finance and for eEvents
for Finance. Any individual language is supported in isolation, but multilingual Siebel deployments are not supported in
Siebel 7.0.4 for the aforementioned modules. (Not applicable to FINS CRM or to FINS MME.) (12-9XP6FW, 12-
9WWURM, 12-9WUHHI, 12-9WUHFZ, 12-9WB5N1, 12-9WB5LJ)
Localization
Category string translated as P3 in Danish Release
The following is applicable to the Danish language pack release. When a user navigates to Finance Administration >
Financial Accounts and creates a new record, and after clicking on the Product field, the Category column in the pop-up
applet is displayed as P3.
To remedy this complete the following:
1. Open Siebel Tools and select the FINCORP Account - Internal Product Pick Applet applet.
2. Select the List Column Sub Type Code and change the DAN caption for the List Column Locale from P3 to
Kategori.
3. Compile a new SRF. (Not applicable to FINS CRM or to FINS MME.) (12-B5FLTZ)
Currency in Siebel Finance Danish Release
The following release note is applicable for the Siebel Finance Danish release. In the Auto Policies Report the currency will
be displayed in $ instead of the locale currency symbol. (Not applicable to FINS CRM or to FINS MME.) (12-AOS47W)
Financial Services / My Calendar View
When creating an appointment in My Calendar view, appointments do not show in this view. This is applicable to Siebel
Industry Applications French release. To fix:
• Connect to Siebel OLTP database through an SQL Querying tool.
• Run the following SQL:

update siebel.S_APP_QUERY set DESC_TEXT = 'PDADef_Uncompleted Activités', LAST_UPD =

'17/12/02', CREATED = '17/12/02' where ROW_ID = '0-3O1S6'
commit
(12-EI0T67)
Zip Code and Country Field in Japanese Address Applet
The following release note is applicable for the Siebel Finance Japanese release. The Zip Code and country field in the
address applet can be added by completing the following:
1. In Siebel Tools > Go to Applet in the Object Explorer.
2. Search for FINS eBanking Personal Address List Applet.
3. Go to Applet Web Template > New.
4. Correct the sequence of the columns under the column Item Identifier - Language Override in order for all fields to
appear.
5. Compile the project and create a new srf. (Not applicable to FINS CRM or to FINS MME.) (12-B7FBJT)
Message in Finance ERM after login
The following is applicable to the Siebel Finance Korean release. An error message may occurs after logging into the
Finance ERM application. To remedy this complete the following.
In Siebel Application:
1. Log in as an administrator.
2. Go to Personalization Administration - Rule Sets.
3. Find the Rule associated with ERM salutation.
4. In the More Info applet change the value in the field Include Expression.
5. The text includes GetProfileAttr(FullName) . FullName, or AccountName is translated to Korean. Change the
translations back to English. The server may need to be bounced in order to see the changes. (Not applicable to
FINS CRM or to FINS MME.) (12-B9KE5R)
Events Calendar in English for Danish Release
This release note is applicable to the Danish release. The Events Calendar banner will appear in English. To remedy this do
the following.
1. In Siebel Tools add and modify user property for HI Calendar Applet
Modify - Name: Field1 Value: Event Type
Add - Name: Field6 Value: Event Type LIC

2. Modify applet_hi_calendar_applet.js
function DayDiff(startDate, endDate)
{
var dayInMilliseconds;
dayInMilliseconds = Date.parse(endDate) - Date.parse(startDate);
return (dayInMilliseconds / 86400000) // convert back to number of day

}
function GetAppropriateIcon(status, created, lastmodified)
{
var today = new Date()
if (status == "Cancelled")
return "<IMG SRC=“images/" + "ind_cancelled.gif” width=“12” height=“12”>"
else if (created == lastmodified && (DayDiff(created, today) < 1))
return "<IMG SRC=“images/" + "ind_new.gif” width=“12” height=“12”>"
else if (created != lastmodified && (DayDiff(lastmodified, today) < 7))
return "<IMG SRC=“images/" + "ind_rescheduled.gif” width=“12” height=“12”>"
else
return ""
}
function HI_Calendar_Applet_Applet_PreInvokeMethod (name, inputPropSet)
{
if (name == ‘renderCalendar_Week_Month" )
{
var oDoc;
var desc;
var tempDate;
var y;
var bt = true;
var sBannerHTML;
var sDateBucket;
var xArrayLen = SCHED_PARAMS.dateRange.length
var sSchedCell = new Array(xArrayLen);
var SCHEDDATE = new Array(xArrayLen)
var defaultlink = oPropset.GetProperty("DefaultLink");
// optimize toDateString slow call

for (x=0;x < xArrayLen; x++)
{
sSchedCell[x] = new Array()
SCHEDDATE[x] = SCHED_PARAMS.dateRange[x].toDateString("mm/dd/yyyy")
}
// Property 6 - Status
// Property 7 - Created Date
// Property 8 - Last Modified
while ((oDoc = oPropset.EnumChildren(bt)) != null)

{
bt = false;
desc = (oDoc.GetProperty("4") == "") ? "(no description)" : oDoc.GetProperty("4");
tempDate = new Date(oDoc.GetProperty("0"));

sHTML = "<DIV STYLE=“padding-top:3px;padding-left:3px”>" +

GetAppropriateIcon(oDoc.GetProperty("6"), oDoc.GetProperty("7"), oDoc.GetProperty("8")) +
"&nbsp" +
"<A HREF=“" + getDrillDownLink(defaultlink, oDoc.GetProperty("RowIds")) + "“>" +
oDoc.GetProperty("5") + "</A>" +
"</DIV>";
sDateBucket = tempDate.toDateString("mm/dd/yyyy")
for (y = 0; y < xArrayLen; y++)

{
if (sDateBucket == SCHEDDATE[y])
sSchedCell[y][sSchedCell[y].length] = new CellATT(oDoc.GetProperty("4") +
oDoc.GetProperty("5"),oDoc.GetProperty("4"), sHTML, oDoc.GetProperty("9"));
}
}
// put in the HTML

for (y = 0; y < SCHED_PARAMS.dateRange.length; y++)
{
if (sSchedCell[y] != null && sSchedCell[y].length > 0)
{
sSchedCell[y].sort(DoSortX);
for (z=0; z < sSchedCell[y].length;z++)
{
sBannerHTML = "<DIV STYLE=“padding-top:3px;padding-
left:3px;background-color:" + GetBannerColor(sSchedCell[y][z].EventTypeLIC) + ";color:white”>" +
sSchedCell[y][z].EventType + "</DIV>";
if (SCHED_PARAMS.dateRangeData[y] == null)
SCHED_PARAMS.dateRangeData[y] = sBannerHTML +
sSchedCell[y][z].sHTML
else if (sSchedCell[y][z].EventType != sSchedCell[y][z-1].EventType && z >0)
SCHED_PARAMS.dateRangeData[y] += sBannerHTML +
sSchedCell[y][z].sHTML
else
SCHED_PARAMS.dateRangeData[y] += sSchedCell[y][z].sHTML
}
}
}
return ("CancelOperation");
}
else if (name == ‘renderCalendar_Daily_Today")
{
// CODE TO OVER-RIDE TIME SLOTS, no slots custom html day view as per FINS Evt Cal
var oDoc;
var desc;
var tempDate;
var y;
var bt = true;
var xArrayLen = 1
var sSchedCell = new Array();
var sBannerHTML;

var defaultlink = oPropset.GetProperty("DefaultLink");

var sHTML
var dayHTML = ""
//Event Type = oDoc.GetProperty("4")

//Event Name = oDoc.GetProperty("5")
//Status = oDoc.GetProperty("6")
//Created = oDoc.GetProperty("7")
//Updated = oDoc.GetProperty("8")
//Event Type LIC = oDoc.GetProperty("9")
while ((oDoc = oPropset.EnumChildren(bt)) != null)

{
bt = false;
desc = (oDoc.GetProperty("4") == "") ? "(no description)" : oDoc.GetProperty("4");
tempDate = new Date(oDoc.GetProperty("0"));
sHTML = "<DIV STYLE=“padding-top:3px;padding-left:7px;background-color:#FFFFFF”>" +

GetAppropriateIcon(oDoc.GetProperty("6"), oDoc.GetProperty("7"), oDoc.GetProperty("8")) +
"&nbsp" +
"<A HREF=“" + getDrillDownLink(defaultlink, oDoc.GetProperty("RowIds")) + "“>" +
oDoc.GetProperty("5") + "</A>" +
"</DIV>";
sSchedCell[sSchedCell.length] = new CellATT(oDoc.GetProperty("4") +

oDoc.GetProperty("5"),oDoc.GetProperty("4"), sHTML, oDoc.GetProperty("9"));
}
// put in the HTML

sSchedCell.sort(DoSortX);
for (z=0; z < sSchedCell.length;z++)
{
sBannerHTML = "<DIV STYLE=“padding-top:3px;padding-left:3px;background-color:" +
GetBannerColor(sSchedCell[z].EventTypeLIC) + ";color:white”>" + sSchedCell[z].EventType + "</DIV>";
if (dayHTML == "")
dayHTML = sBannerHTML + sSchedCell[z].sHTML
else if (sSchedCell[z].EventType != sSchedCell[z-1].EventType && z >0)
dayHTML += sBannerHTML + sSchedCell[z].sHTML
else
dayHTML += sSchedCell[z].sHTML
}
appletObj.document.getElementById("dvInfo0").innerHTML = "<DIV style=“margin-

top:20px;width=100%;height=100%;background-color:#f5f5f5”>" + dayHTML + "</DIV>"
appletObj.document.getElementById("dvInfo0").style.overflow = "hidden"
return ("CancelOperation");
}
else
{
return ("ContinueOperation");
}
}

function DoSortX(A, B)
{
if (A.IndexType > B.IndexType)
return 1;
else if (A.IndexType < B.IndexType)
return -1;
else
return 0;
}
function CellATT(IndexType, EventType, sHTML, EventTypeLIC)

{
this.IndexType = IndexType;
this.sHTML = sHTML;
this.EventType = EventType;
this.EventTypeLIC = EventTypeLIC;
}
function GetBannerColor(name)
{
if (name == "Auction")
return "#B2E5B2";
else if (name == "Benefit")
return "#7AB8F6";
else if (name == "Conference")
return "#CC66FF";
else if (name == "Cultural")
return "#FF0066";
else if (name == "Demonstration")
return "#F1E87D";
else if (name == "Fundraiser")
return "#FF6633";
else if (name == "Meeting")
return "#99CCCC";
else if (name == "Presentation")
return "#9999FF";
else if (name == ‘recreation")
return "#FF6633";
else if (name == ‘restricted")
return "#339933";
else if (name == ‘seminar")
return "#3366CC";
else if (name == ‘trade Show")
return "#9900CC";
else if (name == "Investor Briefing")
return "#CC0066";
else if (name == "Analyst Conference Call")
return "#CC9933";
else if (name == "Analyst Marketing")
return "#CC3300";
else if (name == "Analyst Visit")
return "#339999";
else if (name == "Company Marketing")
return "#6666CC";

else if (name == "Video Conference")

return "#006600";
else if (name == "Deal RoadShow")
return "#003399";
else if (name == "Non-Deal Roadshow")
return "#993300";
else if (name == "Public Holiday")
return "#666699";
else
return "black";
}
function HI_Calendar_Applet_Applet (applet)
{
if (applet != null)
{
this._applet = applet;
applet.shadow = this;
}
this.OnPreInvokeMethod = HI_Calendar_Applet_Applet_PreInvokeMethod;
}
new HI_Calendar_Applet_Applet (null);
HI_Calendar_Applet_Applet.prototype = new top._swescript.JSSAppletShadow ();
3. Add 1 parameter “EventTypeLIC” to CellATT function and add one line:

function CellATT(IndexType, EventType, sHTML, EventTypeLIC)
{
this.IndexType = IndexType;
this.sHTML = sHTML;
this.EventType = EventType;
this.EventTypeLIC = EventTypeLIC
}
4. Add "oDoc.GetProperty("9")" as the last argument in 2 places where called "new CellATT(.....,
oDoc.GetProperty("9"))"
5. Replace 2 places where "GetBannerColor" function use EventType, change it to EventTypeLIC
GetBannerColor(sSchedCell[z].EventTypeLIC)
GetBannerColor(sSchedCell[y][z].EventTypeLIC)
(Not applicable to FINS CRM or to FINS MME.) (12-B5EOTI)
Last and First Name fields in Japanese Finance Release
The following is applicable in the Japanese Finance Release. The first name and last name field identifiers are swapped with
their label item identifiers, this causes the labels to be repeated in the text boxes. To remedy this, do the following.
1. Open Siebel Tools.
2. Select the FINS Contact Summary Form Applet applet.

3. Select the Edit Applet Web Template and then change the following Applet Web Template Items by removing their
JPN locale entries; FirstName, LabelFirstName, LabelLastName and LastName.
4. Compile a new SRF. (Not applicable to FINS CRM or to FINS MME.) (12-B82BQD)
Installation of the Japanese version on AIX platform
This release note is applicable to all locales except the Japanese locale. Installation of the Gateway Server and the Siebel
Server in the same directory is not supported. (Not applicable to FINS CRM or to FINS MME.) (12-AZTXFH)
Opportunity Records in the All Opportunities Across My Organization View
In the Bedrijven (Companies) > Activiteiten (Activities) view, while creating a new record in the list applet, before entering a
value in the Voltooid (Completed) field and moving to another field make sure that the Status field is set first. (12-B111U0)
Query Button in Response Details Applet
The following is applicable for the Japanese release. The query button is not available in the Response Details Applet. To
make a query use the menu or short cut key ALT + Q. (Not applicable to FINS CRM or to FINS MME.) (12-B6YD2K)
Chart view in Swedish release
When navigating from the Kampanjer (campaigns) to Intakter (reveues) chart view some options may not be available. To
remedy this follow the below steps.
1. In Siebel Tools, select Screen and query for Campaigns Screen
2. Under Screen View query for view Campaign Revenue Schedule Chart View
3. Change Menu Text from &Intäkter to & plus the correct Swedish translation for revenue Chart
4. Query for view Campaign Revenue Schedule View
5. Change Menu Text from &Intäkter to & plus the correct Swedish translation for revenue List
6. Compile new SRF. (12-B59MH7)
City Column in the Dutch release
This release note is applicable to Dutch locale. When navigating to Subgebeurtenissen (Sub-Events) >
Investeringsmaatschappij (Investing Company) > the City column is unavailable, only the Name and Country columns are
available. (Not applicable to FINS CRM or to FINS MME.) (12-B5ZKPC)
Opportunity Records in the All Opportunities Across My Organization View
This release note is applicable to all locales except the English locale. For some language versions, the All Opportunities
Across My Organizations view does not display all the opportunity records. Records not visible on this view are visible in
other Opportunities views, such as My Opportunities, All Opportunities, or All Opportunities Across All Organizations. (12-
B4P57J)

LOV Strings Length for French Locale
This release note is applicable to the French locale. There are LOV strings in that will be too long for the French locale.
This results in some LOVs that cannot be displayed in the French locales. In the Transfer Assets view after submitting in the
Transfer All field that the value for Sell Shares/Transfer cash will be blank. The French translation for sell Shares/Transfer
Cash is Vendre les actions/transférer les liquidités, which is greater than 30 characters. This needs to be shortened to less than
30 characters. This can be done by adding a new record for LOV type FINS_SR_SECURITIES_TYPE under Application
Administration / List of Values. (12-AYH9XP)
eCollaboration Link Applet in the Japanese Release
This release note is applicable to the Japanese release. To enable the eCollaboration Link Applet in the Japanese locale the
following must be done.
1. Navigate to the Application Administration Screen > List of Values View
2. Search for LOV Type as FINS_DEAL_EVENT_STATUS_MLOV or EVENT_STATUS with Language

Independent Code as requested
3. Change the Value of FINS_DEAL_EVENT_STATUS_MLOV to be the same as EVENT_STATUS
(Not applicable to FINS CRM or to FINS MME.) (12-B5KUF6)
Unsupported Characters in Queries
This release note is applicable to the Finance Japanese release. Using the hyphen character (-) is not supported for queries.
(Not applicable to FINS CRM or to FINS MME.) (12-B61631)
Printing the Call Report in Brazilian Portuguese Release
This release note is applicable to the Finance Portuguese release. Printing the Call Report is not supported. (12-B62U9K)
Tax Bracket List of Value
This release note is applicable to the Danish release. In the Consumer Profile form applet (Navigate to Contacts (Relaties) >
Consumer Profile (Consumentprofiel) in the Consumer Profile) the Tax Bracket (Tariefgroep) field can not be populated. To
remedy this do the following:
1. Navigate to Application Administration --> List of Value Screen
2. Select FIN_CON_TAX_BRACKETS as type For each entry in this type Change the following
3. Translate Flag from “Y” to “N”
4. Language From Target Language to English-American
5. Value from existing Value to the Value in the Language Independent Code Value
(Not applicable to FINS CRM or to FINS MME.) (12-B68XS7, 12-B3VP3N)
Cancel Button in Finance Application
This release note is applicable to the all locales. If you wish to cancel a query after clicking the query button, use the menu to
access cancel. (12-B7X1RM)

Additional Configuration for List of Values for Siebel Finance
This release note is applicable to the all language releases except Japanese and Korean for the Siebel Finance release. In the
Finance eBanking application Inform Problems applet there are no List of Values. To remedy this follow the below.
1. A seed list of values record needs to be added with Type = FINS_SR_AREA_NB, Name = Bank, Value = Bank,
Translate = N and Active = Y.
2. Then go to each other FINS_SR_AREA_NB record within List of Values and pick the newly created Bank record as
Parent Language Independant Code.
3. You must restart the server in order for the new values to be visible withing the application.
(12-B7KMLW, 12-B7KMLI)

Siebel eAutomotive Known Anomalies 6
General Options
Contacts
Vehicle
Vehicle Pick list in Service Requests has Primary Contact or Primary Employee visibility
The Vehicle Pick list in Service Requests has a Primary Contact orPrimary Employee visibility constraint. This means that
the user will only see those vehicles in this pick applet where she is the primary contact or the primary employee of the
vehicle. The user interface does not display the primary employee field. For a work around, see the tech note on SupportWeb.
(12-9U4JZJ)
Fields take values outside of List of Values
Some fields will take values outside of the List of Values displayed in the application. The following fields will display this
behavior – UoM, Relationship, Location, Body Style, Build Plant, Regulatory Certifications, Exterior Color, Interior Color,
Build Plant, and Regulatory Certification. For the work around, please see the SupportWeb. (12-9CVRR5)
Dealers
Visibility in Dealer Operations Screen is based on position only
The only visibility that Dealer Operations Screen has is the position visibility. It does not have any organization visibility.
This means that the user sees only those dealers for which he is on the sales team. (12-9U4JZ8)
Views missing from Auto Field Manager’s responsibility
The Auto Field Manager (Login: Henry Abel) does not have home page view in his responsibility. The work around is to put
the view – Home Page View (WCC) – in the responsibility called Auto Field Manager. (12-9UNDW3)
Auto Field Manager’s responsibility does not contain some default views. This may cause some erroneous User Interface
behavior. The work around is to put the default view of every screen in Auto Field Manager’s responsibility. The default
view of every screen can be found in properties of screens in Siebel Tools. For example to avoid erroneous User Interface
behavior, put the Account List View, which is the default view for Account Screen, and Visible Contact List View, which is
the default view for Contact screen, in Auto Field Manager’s responsibility. (12-9UWVV6)
Auto Field Manager’s responsibility has Marketing Segment view missing which is a required view
This may cause some erroneous User Interface behavior. The work around is to put the view – Partner Administration Market
Segment List View in the responsibility of Auto Field Manager. (12-9UWVV6)

Siebel eAutomotive Known Anomalies
Other
Automotive Tools Inventory Search View’s Back button does not work as intended
On Search results view, if the user drills down on any vehicle found in inventory to go to vehicle detail form applet, and then
clicks the BACK button, the application takes the user back to the inventory search view,Not to the search results view.
On Search results view, if user drills down on any dealer related to a vehicle found in inventory to go to dealer detail form
applet, and then clicks the BACK button, the application takes the user back to the dealer locator view. Not to the search
results view. (12-90C15M)
Siebel Analytics
Data Warehouse
ETL Deadlocks During Parallel Sessions
While running Refresh_Siebel_DW batch for SIS Data Warehouse, Informatica sessions in MSSQL may get deadlocked and
eventually fail. If dropping the indexes on the OPB_OBJECT_LOCKS repository does not resolve the problem (refer to the
troubleshooting Hints in the Siebel Data Warehouse Installation and Administration Guide), then convert the sessions to run
in sequential mode. The problem may be occurring due to several parallel sessions in the batch. To convert the batches from
running in sequential, perform the following:
1. In Informatica Server Manager, double click on the batches listed below in the folder
refresh_Seibel_DW_dimension and refresh_Siebel_DW_fact
2. Uncheck the Concurrent Option
3. Click on the OK button once you are done
Batches: RATES, DIMENSIONS(A-H), DIMENSIONS(I-O), DIMENSIONS(P), DIMENSIONS(Q-Sa), DIMENSIONS(Se-

Z), CS_DIMENSIONS, LS_DIMENSIONS(A-M), HIERARCHY, SIS_HIERARCHY, FACTS(A-H), FACTS(O-Q),
FACTS(R-S), AT_CS_FACTS, LS_FACTS, ActivityProductStaging, LOAD_FACT, AGGREGATE, LS_AGGREGATE,
LS_SYND_DATA_AGG(PERIODIC).
(12-BAF2R7)
ETL truncates Account city names greater than ten characters long
Account city names greater then ten characters long are truncated by the ETL process. The work around is as follows:
1. Open Informatica Designer.
2. Open mapping SIS_SIL_OrganizationDimension.
3. Navigate to transformation EXP_GATHER.
4. Change following port precision.
lv_CITY change from 10 to 50

lv_OUT_CITY change from 10 to 50
OUT_CITY change from 10 to 50
lv_ZIPCODE change from 10 to 30
lv_OUT_ZIPCODE change from 10 to 30
OUT_ZIPCODE change from 10 to 30
lv_COUNTRY change from 10 to 30 (12-B7G1ID)

in a Western European code page, the Japanese text will appear as???. This behavior is limited to displaying the values and in
no way affects the processing of the data.
Multiple Siebel Analytics servers can be configuring to access the same data source. In the model where a site needs to
same data sources.
page processing on development and maintenances of the Analytics Applications. (12-BE3XFF)
Siebel Partner Analytics
Dealer Analytics Screen in eAutomotive
When the user clicks on Dealer Analytics screen in eAutomotive, the user will get a message. The work around is as follows
1. Open Application
2. Log in as SADMIN/SADMIN
3. Go to View>Site Map>Integration Administration > Symbolic URL Administration
4. In Symbolic URL applet, search for Name sISMATPartnerDashboard1
5. In symbolic URL Arguments applet, search for Name replaceResponseWithForm, then change its Argument Value
to replaceResponseWithForm (12-B452DO)

Accessing Sales Analytics View in eAutomotive
When the user logs in from within Automotive client, the user is asked to log into the nQuire client as well. Having logged in,
the user sees all the dashboards as opposed to the dashboards that the user should see based on permission. The work around
to fix this is as follows: 1) Open application 2) Log in as SADMIN/SADMIN 3) Go to View>Site Map>Integration
Administration>Symbolic URL Administration 4) In Symbolic URL applet, search for Name sISMATSalesDashboard1 5) In
symbolic the URL Arguments applet, search for Name nqPassword, then change its Argument Value to
“UseSiebelLoginPassword” (12-B452E0)
Siebel Call Center

Adding a Vehicle in Vehicle Administration on DB2/OS390 platform
The user is not able to add a new vehicle in vehicle administration screen. The work around to fix this is as follows
1. Launch the Siebel Tools, check out project or lock the project Auto Vehicle.
2. Do a query on the business component for Name =““Auto Vehicle (Admin)”.
3. Click to extend Business Component, click on the field. Query for field name Model Year (Denorm).
4. Change the Type of the field from DTYPE_TEXT to DTYPE_INTEGER.
5. Compile Auto Vehicle (Admin) to the location of siebel_sis.srf of the client. (12-AY6KOR)
Siebel eChannel
Accessing Auto All Dealer List View on DB2/390
Customers deploying Siebel eAutomotive on DB2/390 platform may experience slow response time when accesing the Auto
All Dealer List View. Customers can alleviate the slow response time by adding the following clause to the Channel Partner
search specs: ORDER BY T7.BU_ID, T7.ORG_PRTNR_FLG, T7.ORG_NAME, T7.ORG_LOC (12-AREWPP)
Siebel eDealer
Shopping Cart
Quantity Field not editable
Shopping cart View does not have Quantity field as editable and there are no Save Cart and Edit buttons. (12-9RTPV9)

Shopping cart check-out process

Refer to release notes in Chapter 3 for eChannel regarding work arounds for this process.
Contacts
Homepage
Dealer Center applet has a missing link
The Homepage does not have Check my Service Requests link in the Dealer Center applet. The work around is to put the view
– Contact Service Request List View (eService) – in responsibilities that are used for the eDealer application. (12-9UXRNX)
Opportunities
View missing from responsibility for Revenue Script
The script in the Opportunities Revenue View does not work. The work around is to include the following view in eDealer
related responsibilities – Revenue Schedule Script Player View (eApps) (12-9UXROL)
Other
Some views in eDealer will not work in standard interactivity
eDealer has borrowed the following screens from eAutomotive – Contacts, Service Requests, Opportunities, Vehicles,
Products, Households, Sales History, Service History, and Vehicle Administration. Only certain views from these screens
are tested to work in eDealer, which runs in standard interactivity. See the Tech note on SupportWeb for the list of views that
will work in standard interactivity. (12-9U4JZ6)
Briefings View does not exist in eDealer related responsibilities
If the user drills down from home page welcome applet’s link, click here to view personalized briefings, the drill down does
not work because the view, SI My Briefing View (eApps), is not in the responsibility of logged in user. The work around is to
add the view to the appropriate user’s responsibility. (12-9W9Q4Z)
Siebel eService
Contact Us
Contact Us buttons are duplicated for Siebel Administrator responsibility

The Contact Us buttons are duplicated in eService when the user logs in as Siebel Administrator. The work around is to
remove the view - Contact Us Communication Channel View – from the responsibility of Siebel Administrator. (12-9U4JZC)

Homepage
Tech Notes: Homepage for eAutomotive is not available out-of-the-box with the application
Tech Notes are available on the SupportWeb on how to configure the eService Home Page for Automotive customers.
Tech Note is available on the SupportWeb on how to change the eService home page Welcome applet link of View Important
Information to go to My Vehicles view, instead of My Products view. (12-9TISYS)
Logging in as Web Registered user gives an error message
When the user logs in as Bill Atkins, who is the web-registered user, the user gets an error message that the operation is not
allowed when there are no records displayed. The user can continue to use the application after getting this error. For work
around so as not to get an error, see the tech note on the support web. (12-A02LTK)
Unregistered Home Page has missing links in My Account applet
The missing links are Register New Vehicles, Check Status of service requests, My Registered Vehicles, and My Service
History. (12-9WA7OY)
The work around is to add the following views to the responsibility called Unregistered Visitor:
o eAuto Service Request List View (eService)
o eAuto My Vehicle View (eService)
o eAuto Vehicle Registration VIN Form View
o eAuto Service History List View (eService)
Dealer Locator
Back Button does not take user back by one screen
The Dealer Locator back button does not take the user back by one screen. If the user clicks BACK button on the message
box, Please re-enter a valid city and state or zip code to locate your nearby branches , and then clicks the CANCEL button
on the dealer locator view, the application takes the user back to the message box instead of to the screen from where she
came to Dealer locator. (12-7SINIE)

Siebel Consumer Sector Known Anomalies 7
This chapter provides information on known anomalies and work arounds specific to the Siebel eConsumer Goods, Siebel
eApparel and Footwear, and Siebel eRetail applications.
General Options
Advanced Search
Error message may appear when creating search indices

When creating search indices through the Search Administration view, an error message may appear after creating multiple
records that states the index status will not be updated. This is erroneous and the previously created indices do appear once
the application is restarted. (12-9WWSAX)
Document ID Administration
Missing Go and Cancel buttons on query applets

In the Document Id Mask and Document Id Administration views, users may run queries for specific records by pressing
ALT+Q. However, the query applets that appear do not display the Go or Cancel buttons on the query applet. To execute a
query, enter in the appropriate parameters and then press ALT+ENTER. To cancel, run a blank query by pressing
ALT+ENTER with no parameters specified. (12-9OP58X)
Invoice Date not defaulting to current time

The Invoice Date field is a Date/Time field, which defaults to the current date, but the default time is 12:00AM. This is
configurable by specifying that both date and time should be defaulted to the current timestamp. (12-9Q0R4F)
Sequence # does not autoincrement

The Sequence # for the mask component represents its position within the mask. For example, if the Sequence # is 1, it is the
first component in the mask. This field does not autoincrement when a new record created, so a user must manually enter a
value. If the user skips a number, the application continues to place the components in sequential order without skipping a
position. (12-96SAYD)
Orders
Next Record Set and Previous Record Set buttons are not visible.
Orders > Line Item Details > Order Entry - Line Item List Applet (Sales). The user can navigate through each Line Item
record from the Line Item Details view by activating the Order Entry - Line Item List Applet (Sales) applet, and using the
keyboard shortcut [CTRL] + [SHIFT] + [.]. (12-9MLS47)

Siebel Consumer Sector Known Anomalies
Pick Applet Titles
HTTP address in pickapplet titles

In several pickapplets, the title heading is replaced by the HTTP address of the target applet. (12-9PYQAB, 12-9N4722, 12-
9U7AEV)
Products
Product images cannot be added to products after they are assigned a type of CS or AF
Product images (in .jpg, .gif, or other format) must be added before products are assigned product type CS or AF. Product
images can be changed or updated to existing CS or AF products by removing the product type, adding the image, and
assigning CS or AF to the product type. (12-9M91SA)
Quotes
Undoing a change in the Quote List view does not automatically refresh the form applet
Undoing a quote name change in the Quote List view does not automatically refresh the form applet. The user must step off
the record to see the name revert to its original value. (12-9RU420).
Size Spreads
Certain LOV types cannot be enabled within an MLOV-enabled environment

The Size Spread picklist is implemented to emulate a hierarchical picklist. There is a business component based on
S_LOV_REL on which the pick-list for the Size Run Detail business component is based. This picklist relies on the Value of
the SIZE_RUN_TYPE LOV chosen in the Parent Size Run business component. There are sets of LOV types used in Siebel
Consumer Sector that cannot be enabled for MLOVs (multilingual list of values). This is because they are hierarchical and
used in hierarchical picklists. (12-9RRL0A)
Upgrade
Trade Funds/Upgrade
After upgrade, funds created prior to release 7.x will have null value for S_MDF.FUND_CD.
Funds are stored in the S_MDF table. In 6.x, only one type of fund existed. In 7.x, S_MDF.FUND_CD, a new column, was
added to differentiate among three types of fund records stored in the table. The three types are Account Fund, Fund Group,
and Fund Participant. Funds created prior to release 7.x should be designated as Account Fund after the upgrade, but are not
designated as such as part of the upgrade. Therefore, an additional step is necessary to properly complete the upgrade.
Immediately following the upgrade process, the customer needs to connect to the native database client (for exampleSqlPlus
for Oracle, Query Analyzer for MSSQL), and run the following SQL statements:
update S_MDF set FUND_CD=“Account Fund”;

commit;
It is imperative that these statements are run before any new fund records are created.

Siebel Account Targeting for Disconnect Users

Persistent Query Results in Account Lists for Targeting
Users are able to query the saved accounts for a particular account list using the target account applet in the Targeting
Account List View. This is particularly useful when a list is large, and the user wants to verify that specific accounts are
included in the list. When the user steps off the record or changes views , the list does not automatically refresh. The results
of the query will persist in this applet until the user refreshes the applet by running another query without any criteria. (12-
9PYSAN)
Order Item and Order Quantity Fields

Targeting provides the building blocks for creating complex lists of accounts for sales reps to target. In one of the query
views called Orders, Order Item and Order Quantity do not yield the expected results. The criteria entered in these fields are
not restricting the query. (12-9S8SZN)
Siebel Analytics
Data Warehouse
Troubleshooting Hints in the Siebel Data Warehouse Installation and Administration Guide), then convert the sessions to be
run in sequential mode. The problem may be occurring due to several parallel sessions in the batch. To convert the batches
from running in sequential, perform the following:
refresh_Seibel_DW_dimension and ‘refresh_Siebel_DW_fact”
3. Click on the OK button once you are done.

LS_SYND_DATA_AGG(PERIODIC). (12-BAF2Q7)
ETL truncates Account city names greater than 10 characters long

lv_COUNTRY change from 10 to 30 (12-B69ANR)
Position Id not populated in the Promotion Fact Table

The position id is properly populated in the Retail Audit fact table, but not populated in the Promotion Fact table. This means
end users will be able to use the position hierarchy for analyzing retail audit data, but not to across promotions. (12-9U1KMJ)
Exception Report Business Rule is misleading

Exception reports for the category product hierarchy is generated according to the rule titled Depth>10. This implies that all
category levels greater than ten will generate an exception report. However, given that the Category Product hierarchy
supports nine levels of categories and one level of products, an exception report is generated for all category levels greater
than nine. So a more accurate title of this rule is Depth>9. (12-9X787R)

in a Western European code page, the Japanese text will appear as???. This behavior is limited to displaying the values and in
no way affects the processing of the data.
same data sources.
Siebel Answers
Plan Period is not populated in the eBusiness Data Warehouse

Plan Period requires an additional dimension in the Promotion star schema in the Siebel eBusiness Data warehouse in order
to be fully supported in Siebel Analytics. We recommend customers remove this field from the presentation layer to avoid
any end user confusion (12-9W83E1).

Fixed Category Hierarchy Level has limited applicability

The fixed category hierarchy has limited applicability because it does not pull category names. In general, hierarchy levels
designate which level of the hierarchy an attribute is associated. For example, this works well for the account hierarchy
because at every level you can assign an account name. The Category-Product Hierarchy is slightly different becauseit is a
hierarchy of categories with product names at the base of it. This means that the hierarchy level will pull product names at
each level, instead of category names, and since product name is the lowest level of the hierarchy, all products are aggregated
across all levels of the category (12-9VT5J8).
eConsumer Goods Sales Analytics
Funds Dashboard
Drilling is not supported on the Fund Hierarchy Report

Siebel Analytics for Consumer Sector supports a ten level fund hierarchy that aggregates transfers, adjustments, allocations,
and payments. However, original amount and subtotal should not aggregate in this situation. For this reason, individual
reports need to be created for each level, with resulting measures specific to each level of the hierarchy. Users should not
depend on the inferred drilldown to lower levels in the fund hierarchy. The report appears to be able to drilldown , but the
results will not be true measures. (12-A3NZZ)
Siebel Assortment Planning
Category Targets for Units and Amounts share the Spread flag, and manual changes to Dynamic Columns for the
same record can be overridden.
Users will need to incorporate their manual changes (if desired) in Category Targets as one of the last steps they perform in
the Category Targets view. It is possible that the user could override their manual changes if navigating to the inverse view
(Amounts > from Units, or Units > from Amounts), and then clicking the Spread button. If the Spread button is not clicked,
while the Spread flag is selected for that record, the manual changes will be maintained. (12-9XRH8F)
Siebel eChannel
Siebel eChannel Partner Portal for Apparel & Footwear
Quotes do not maintain context detail in certain scenarios

Context detail is lost when backnavigating after drilling down on second (or greater) ship-to hyperlinks in the Quote Ship-To
list. This anomaly exists only when there are multiple ship-to destinations in the quote. In order to maintain proper context
with the second (or greater) ship-to destination, the user must navigate to the quote header, and click through the appropriate
hyperlinks to view additional levels of Quote Item detail. (12-9Q0C38)
Advanced search in eChannel for Apparel & Footwear is not supported.

The Advanced Search option for eChannel for Apparel & Footwear is not supported. (12-9WWSBW)

Siebel eChannel Partner Portal for Consumer Goods
Error message appears after selecting the Advanced Search icon

After clicking on the Advanced Search binoculars icon, the following error message appears: Frame search cannot be found.
Users can continue to use advanced search after the error is cleared. (12-9WWSBA)
Siebel eConsumer Goods Sales Handheld
Siebel Sales Handheld for Windows CE
Cycle Counting
The Representative ID field is improperly labeled as Van in the Cycle Count printed document. (12-9RP1KT)
Editing Logging Parameters in the Setup.ini File
There are two logging parameters in the setup.ini file that need to be reset before you deploy your application. The
parameters and their default values are:
[Logging]
LogSqlStmts = Y
LogSSAErrors = Y
The LogSQLStmts and LogSSAErrors parameters log messages to the sql_stmt_log.txt and ssa_errors_log.txt files,
respectively. You may want to use the defaults for debugging while you are developing your application. However, once you
are ready to deploy your application, reset the values of both parameters to N. Caution: If the LogSQLStmts and
LogSSAErrors parameters are set to Y, then the log files will get very large and use up the available memory on the handheld
device. (12-BCYKBD)
Accounts
Available Credit is not assigned to an order if the order is created in the Accounts Orders view
When an order is created in Accounts>Orders view, the account’s Available Credit is not populated. To populate Available
Credit for new orders, users should create orders directly in the Orders screen or in the Outlet Visits screen using the Prepare
Visit button for Retail Order activities. (12-B17BWE)
Warranty Start or Warranty End fields are not Date type fields in Accounts Assets view
The Warranty Start and Warranty End fields can be configured to be Date type using Siebel Tools. (12-9GZ3J3)
Type Hyperlink on in Activities view sometimes gives error
The error message, You can’t drill down to ‘CPG HH Order Entry – Line Items View (Sales) CE’ because there is no source
entry to drill down from, is displayed when the hyperlink is supposed to navigate to an order that was not synchronized to the

handheld. To circumvent this problem, when possible, activities such as Retail Order should be filtered from the handheld.
(12-9ZE216)
Billings
Credit Memo # not populated in the Invoice Payments list applet when a Credit Memo payment is selected from
the Payment pick applet
When a Credit Memo payment is selected from the Payment pick applet, the Credit Memo # field is not populated in the
Invoice Payments list applet. This can be configured by making the Credit Memo # field a calculated field whereby it is
populated with the payment row id when the Method =Credit Memo. (12-BAK41X)
Extended Price, Extended Tax, and Total are blank or set to 0.00 after synchronization
For invoices created upon order fulfillment on the handheld, the Extended Price, Extended Tax, and Total fields on the
Invoice Line Items list applet are set to NULL, NULL, and 0.00, respectively. In order to keep the synchronization of these
fields in tact, the following Business Component User Properties should be added to Order Entry – Line Items (12-BAJRC6):
User Property Value
On Field Update Set 51 Tax Var1, "Stored Extended Tax", "[Item Tax]"
On Field Update Set 55 Quantity Requested, "Stored Extended Tax", "[Item Tax]"
On Field Update Set 56 Unit Price, "Stored Extended Price", "[CG Line Total]"
On Field Update Set 57 Base Price, "Stored Extended Price", "[CG Line Total]"
On Field Update Set 58 Discount Percent, "Stored Extended Price", "[CG Line Total]"
On Field Update Set 59 Discount, "Stored Extended Price", "[CG Line Total]"
On Field Update Set 60 Discount Amount, "Stored Extended Price", "[CG Line Total]"
Synchronizing after canceling an invoice results in conflict errors
When an order is cancelled, the status of the order is updated to Open. In addition, the As of Date field, which records when
the last date or time the Status is updated, is updated both by a User Property and code. In order to avoid the conflict, the On
Field Update Set 6 UserProperty should be set to Inactive for the Order Entry – Orders business component. The updates to
the field already occur by the C++ code on the server. (12-BAZQA5) 6
Payment Date does not appear in the Find drop down in the Payments Pick Applet in Invoice Payments view
The Payment Date field cannot be queried on in the Payments Pick Applet in Invoice Payments view because is does not
appear in the Find drop down list. (12-AN4I28)
6

Toggle button should not be enabled in the Invoice Payments view
The toggle button should only be enabled for views with two or more applets. The Invoice Payments view is a two-applet
view, so the toggle button should be disabled. To disable the toggle button in the view, the size of the print applet should be
changed to 0x0. (12-B3V7TY)
Payment Pick Applet displays payments whose Remaining Amount equals zero or null
The Payment Pick applet on the Invoice Payments view should only display those payments that have Remaining Amounts
greater than zero. The configuration is set up to manage meet this requirement, however there appears to be a core anomaly
that does not detect this search spec. (12-B7GPE3)
Incorrect value for Sum Qty is printed for Invoice documents
The Sum Qty at the bottom of the invoice document printout should display the total quantity requested (for an Invoice or
Note of Sale) or total quantity returned (for Credit Note). Instead, it displays the total quantity requested plus the total bonus
quantity. This can be corrected through configuration to display the intended sum on the print applet. (12-B4ONMX)
Invoice Totals update independently of currency type
In the Billings > Invoice Payments view, payments may be created in the Payments Pick Applet with different currency
types. Because multi-currency is not supported on the handheld, the exchange rate is assumed to be 1 when calculations are
executed for the payment, such as updating totals on the invoice. It is recommended that the currency type fields be made
read-only in the application in order to avoid user confusion. (12-B1H4BG)
Static title on printed Invoice Line Items print template misrepresents Credit Notes and other Invoice types
The title on the print template on the Invoice Line Items view is misleading because it is static and always displays Invoice.
regardless of what type of document is being printed. Instead, the title should be configured to be dynamic so that it is based
on the Sub-Type field on the invoice record. As a result, if the Sub-Type is a Credit Note, then the value Credit Note will be
printed on the document. (12-9XRKGW)
Calendar
Cannot add Contact to calendar appointment
Users may create appointments in the Calendar screen, but are currently unable to associate contacts to the appointment. The
solution is to configure a Calendar > Contacts view, which could be accessed for each appointment scheduled. (12-
AGM31Q)
Imposing required fields on the Calendar Business component causes difficulties with recurring appointments
Using Siebel Tools to set fields within the Calendar Business Component as required may create synchronization errors if the
user subsequently deletes one appointment in a series of recurring appointments. (12-8MP8V7)

Configuration
Use of ampersand (&)character in Business Component name causes synchronization and database errors
When customers configure the Siebel Handheld application, using the ampersand (&)(Shift-7) character in the Business
Component name will cause errors during database import, the final phase of synchronization. Configurators should avoid
the use of this character in Business Component names. (12-AFV20N)
Cycle Counting
Possible to insert duplicate product record
There is no restriction on the Cycle Count Products view to prevent users from creating the same product record with the
same status in the Products List Applet. If the same product is added, and both are used to reconcile inventory, the inventory
will be updated based on the last record of the same product in the list. This is equivalent to creating multiple cycle counts
for the same product. (12-ABU7IN)
Printing: Representative ID field is incorrectly labeled as Van
The Rep ID field is improperly labeled as Van in the Cycle Count printed document. (12-9RP1KT)
Installation
Unnecessary Configuration files created on server
Two extra .cfg files are created in ...\siebsrvr\BIN\ENU. These files are cgce.cfg. They may be safely deleted. (12-
9Z6WLE)
Navigation
Pressing Back Arrow Sometimes Results in Error Message
Sometimes, when user presses the back arrow, the following error message appears: An error has occurred finding your place
in the system. Please try a new query. This occurs when the user attempts to return to a view where the record no longer
meets the search criteria of the active predefined query in the Favorites drop down. For example, if the predefined query on
My Outlet Visits view is Today Not Started, the view will only display today’s visits that have a status of Not Started. When
the user presses the Start button, the user is navigated to the Visit Activities view, and status of the visit changes to In
Progress, no longer meeting the constraints of the My Outlet Visits view. When the user attempts to return to the My Outlet
Visits view using the back arrow, the application cannot find the selected record in that view because the visit record has
been filtered from the view. To avoid this scenario, a PDQ should be created to be specific enough to extract a reasonable
amount of data on synchronization, but general enough to accommodate such changes during application use. For example,
in the above scenario, the query would best be defined as Today, making the view display records independent of Status,
which changes during application use. (12-ACV7RT)

Orders
Entering Qty greater than 999 will result in errors
The field is configured to accept numbers less than 1000. This can be changed by modifying the validation on Quantity
Requested to be >= 0 AND < 1000. This will prevent a user from entering values greater than 999. If there is a need to enter
Orders for a line item greater than 999, multiple instances of the line item have to be created. (12-BAI7D7)
Misleading error message when data is not entered in all required fields
If a User creates a new record in Order Line Items and steps off the record without entering data in the Product field or
SKU/UPC field, the following error message appears Product ID is a required field. Users should enter a value in the
Product field or the SKU/UPC field. (12-9PZY2X)
Discount % does not update the Net Price on order line items until the order header is refreshed
In the Order Line Items view, updates to the Discount % field on the order header does not update the Net Price on the order
line items until the view is fully refreshed. Users may refresh the view two ways: (1) Run a blank query on the Order Form
Applet on the Order Line Items view by pressing the New Query followed by the Execute query buttons on the toolbar, or (2)
Navigate off of the view (for example to the My Orders View from the Show dropdown list) and then return to the Order
Line Items view. Users will find that the Net Price in the third applet on the Order Line Items view will be updated after the
refresh. (12-B0YWBM)
Outlet Visits and Visit Activities
A synchronization error is received when an Outlet Visit is synchronized with no account
Account is not a required field on the In Store Visit business component, which allows users to create outlet visits without
assigning them accounts. If a user forgets to assign an account to a visit, completes the visit, and synchronizes the visit, an
End of File… error message is issued during synchronization. To avoid this, make Account a required field on the In Store
Visit business component. (12-B5HB93)
A synchronization error is received when a retail audit is conducted for the same account, for the same product,
on the same day
If a retail audit is executed for the same account, product, and day, a synchronization conflict error will occur. Resolve this is
by changing through configuration the audit date to a date/time field, rather than date. (12-B8ICMZ)
Product Movement
Asset Number is misspelled as Asset Numer
The Asset Number is misspelled and can be configured in Siebel Tools. (12-9WQEOL)
Product Movement records cannot be updated on the server after synchronization from the handheld
Once a product movement record is committed on the handheld and synchronized to the server, the administrator should not
attempt to edit the record. Doing so will launch error messages, such as Unable to generate inventory transaction. The
selected value does not match any picklist value, or Cannot find trunk inventory location for the activity owner. (12-
AWV92R)

Updating Source and Destination fields require the use of a third dummy value
Source and Destination are each designed to have only one of two values, Customer or Trunk. They are currently defaulted
to Trunk and Customer, respectively, to represent a product movement out of the van. If the user is required to record a
product movement for the reverse, then the values must be switched. The current configuration does not allow the two fields
at anytime to have the same values. As a result, the user must change the values using the following procedure:
1. Destination should first be changed to Service Order
2. Source should next be changed to Customer
3. Destination should then be changed to Trunk. Service Order is an intermediate value that used only for this purpose.
(12-ABSNYQ)
RMAs
Available Credit field is not a currency field type in the RMA Line Items form applet
The Avail. Credit field on the RMA Line Items parent form applet is a number field. It can be changed to a currency field
using Siebel Tools. (12-93VUFD)
List Price and List Tax are not refreshed when a line item that does not exist in the Price or Tax List is selected
If a line item is changed, the List Price and List Tax will not be refreshed to $0.00 if it does not exist in the Price List or Tax
List, respectively. As a result, if the List Price and List Tax fields are already populated prior to the change, then those same
values will appear after the change. (12-B2YOJL)
Confusing error message is displayed when Credit is pressed on an RMA with no account
When the Credit button is pressed for an RMA with not account, the following error message is displayed: is a required field.
Please enter a value for the field. The error message should indicate that crediting cannot occur because no account is been
assigned to the RMA. (12-AN2MK5)
The Credit button displays a confusing error message when the RMA total is negative and continues to create a
Credit Note each time it is pressed
RMAs may be created with a negative total (discounts applied are greater than the List Price). When the Credit button is
pressed, the following error message is displayed: The value for “ for field ‘%2’ is required to be ‘%3’. Please enter a value
of ‘%4’. The Credit button is still enabled and can be pressed multiple times, each time creating a new credit note. The
discount fields can be configured to be read-only to prevent entry of amounts greater than the List Price. (12-B25V54)
Product names do not wrap on RMA printouts
Long product names do not wrap to next line on the RMA printout. This can be configured by setting the Wrap parameter to
True in the RMA print template. (12-B8QSNZ)
Routes
Routes > My Routes, Toggle options are the same name
If a User selects the View>Toggle menu, both Applets have the same Applet Title. Customers can use Siebel Tools to
change the Applet Title for either applet. (12-92AYPP)

Synchronization/Database
List Price and List Tax are lost during sync if Qty = 1
If the user enters a value of one into the Qty field, the List Price and List Tax are lost after synchronization. To fix this, add
the following UserProperties to the Order Entry – Line Items BC :
Name: On Field Update Invoke 19
Value: CG Account Product, Order Entry - Line Items, ClearPrice
Name: On Field Update Invoke 20
Value: CG Account Product, Order Entry - Line Items, CalculatePrice
Make CG Account Product field Inactive from Product PickMap. Make Quantity Requested field predefaulted to 0. (12-
BDQ430)
Synchronization filters available for screens not in the User’s responsibility
When Users log into the Handheld Synchronization client and choose select Filters, they may see names of screens in the
Filters dropdown list that they have no access to. (12-9H2HTM)
Synchronization conflict errors sometimes occur when a predefault value for a column exists at the table level
Synchronization conflict errors occur sometimes because of tablelevel predefaults. The following table contains a list of
business components and respective fields that currently cause conflict errors.
Buscomp Field Table Column Default
CG Retail Product Order Flag S_ORG_PROD ORDER_FLG N
CPG Account Merchandising Product Retail Audit Flag S_PROD_INVLOC CG_RTL_AUDIT_FLG Y
CPG Store Conditions in Retail Audit OOS S_STORE_COND OUT_OF_STOCK_FLG N
Reset STOCK_RESET_FLG N
Rotated STOCK_ROTATED_FLG N
Void STOCK_VOID_FLG N
Retail Audit Product Active S_ORG_PROD DSTRBN_ACTV_FLG N
Order Flag ORDER_FLG N
As a general rule for handheld configuration, if there is a predefault value for a column at the table level, all the business
component fields that are mapped to that column should meet one of the following two criteria:
The field is required on the business component, or
The field should have a predefault value of its own at the business component level (this predefault value can be different
from the value at the table level) (12-BAK436)

Updates to Account Assessments result in conflict errors upon synchronization
When Account Assessment attributes are updated on the handheld and synchronized to the server, conflict errors arise
because both a server code and the handheld transaction record both attempt to update the assessment total score. The end
result is that the score gets updated correctly, but synchronization errors appear. The user may bypass these errors by
pressing OK on each error. (12-BAI98O) 7
Direct Server Synchronization PDQ Filter Administration
With Direct Server Synchronization deployments in Siebel v7.0.4, the administrator must stop and restart the Handheld Sync
Object Manager process in order to make new or revised PDQ Sync Filters available to users. The PDQ Sync Filters that are
available to the Handheld Sync users are extracted once per server process, when the first user syncs only. The PDQs are not
updated for subsequent sync users andsessions. In addition, the use of Private PDQ Sync Filters, which allow user-specific
PDQ Sync Filters, is not supported. All subsequent sync users will see, if any exist, the first sync user's Private filters. They
will not see their own Private filters. (12-B8YX37)
Certain Parent Business Component QBE filters are not being correctly applied to Child Business Components
During synchronization, the Parent Business Component QBE filters are not being correctly applied to the Child Business
Components. To correct this, make sure that any QBE filter on the parent business component is transferred to the first
default PDQ to make sure of lower extraction times. (12-B7R8MV)
Siebel Marketing
Shopping cart check-out process

The checkout process of user registration and order confirmation for a shopping cart is not supported. To enable the checkout
process for these orders make the following modifications in Siebel Tools:
1. For the CUT Current Quote View (eSales),

• replace CUT Quote Item List Applet (eSales) with Quote Item List Applet (eSales)
2. For the CUT Saved Quote Detail View (eSales):

• Replace CUT Saved Quote Item List Applet (eSales) with Saved Quote Item List Applet (eSales)
• Replace CUT Quote Totals Form Applet - Summary (eSales) with Quote Totals Form Applet - Summary
(eSales)
3. For the CUT Quote Summary View (eSales):

• Replace CUT Quote Item ReadOnly List Applet (eSales) with Quote Item ReadOnly List Applet (eSales)
• Replace CUT Quote Totals Form Applet - Summary (eSales) with Quote Totals Form Applet - Summary
(eSales)
7

4. For the CUT Quote Form Applet - Current (eSales):

• Make the following Applet Web template Items inactive.
1. ButtonUngroup
2. Current Quote Total Base Price
3. Current Quote Total Base Price MRC
4. Current Quote Total Item Discount
5. Current Quote Total Item Discount MRC
6. ButtonMyProducts
• Expose the following controls in the Applet Base template
1. TotalDiscount
2. TotalNetPrice
5. For the CUT Order Confirmation View (eSales):

• Replace CUT Order Confirmation Item List Applet (eSales) with Order Item List Applet (eSales)
• Replace CUT Order Totals Form Applet - Confirmation (eSales) with Order Totals Form Applet - Confirmation
(eSales)
6. For the CUT Order History Summary View (eSales):

• Replace CUT Order Item List Applet (eSales) with Order Item List Applet (eSales)
(eSales)
7. For the CUT Order Approval View (eSales):

• Replace CUT Order Approval Item List Applet (eSales) with Order Approval Item List Applet (eSales)
(eSales)
(12-9SGMPI)
Siebel Sales Volume Planning

Deleting SVP Categories through Catalog Administration
When defining catalogs and categories and Sales Volume Planning (SVP) categories, do not associate an SVP category to a
catalog. Please note, erasing an SVP category from the catalog category administration screens will remove the category from
SVP. (12-9X2Z7F)
Siebel Trade Promotions

Account Plans and Promotions
Rollup of baseline and shipment records for a plan
When promotions belong to a plan, the baseline and shipment records associated to a promoted product are rolledup to the
promotion, and in turn to the plan. The rollup of baseline and shipment records for a plan do account for baseline or

shipment records that have been associated multiple times. This may cause the baseline and shipment for the plan to be
overstated. (12-AB2FQ9)
Changing a Promotion’s Account to one without a Promotion Profile

In the Promotions screen, if the account of a promotion is changed from one with a primary promotion profile to one without
a primary promotion profile, the promotion, shipment, and consumption dates are not automatically adjusted based on the
period. (12-9Q06IX)
Account Promotion view titles are not displayed in the History window
Some views in the Promotions screen will not display a title in the history menu. (12-9T9B1D)
Funds
Loss of context when Navigating from Accounts Funds views to the Accounts Funds More Info view
When navigating from any view in Accounts > Funds to the Accounts Funds More Info view, the highlighted record is not
maintained. Instead, the first record is highlighted. The user can then reselect the fund. (12-9NF7AZ)
Updating a Fund’s Unallocated value after creating Child Funds.

After creating a child fund in Data Administration > Funds > Child Funds, the user must click the Refresh button to update
the Unallocated field in Data Administration > Funds > More Info view. (12-9NF7B3)
Closed Promotion Deals accept new payments

Promotions > Deals. When a deal has a status of Closed, new payments are still allowed. (12-9TLX7N)
Release Commitments functionality is not supported for committed Deals associated with Accepted Promotions
Data Administration > Fund Deals. Currently, Release Commitments functionality is not supported for deals with a status of
Committed and associated with a promotion with the status of Accepted. The user will receive an error message. It is
advisable to use Presented instead of Accepted for the promotion status if Release Commitments is necessary. Using the
Presented status will trigger the same behavior as Accepted, except records will not be turned to read-only and thus, updates,
such as those invoked by releasing commitments, will still be allowed. (12-9V0BMP)
The total amount of Child Funds can exceed the parent Fund amount if modified in nonstandard views
Data Administration > Funds > Child Funds. In this view, there is a validation between the sum of the child amount and the
parent amount. However, this validation can be avoided if the child amount is updated in another view. (12-8CFUVH)
Promoted Products
Lift % column is not applicable

Promoted Products > Baseline. The view contains a column labeled Lift % that is not applicable to the applet. (12-9OT5DE)
Promotion Gantt Charts
Plan Gantt chart defaults to period with no Promotions
Plans > Promotions > Promotion Summary and Corporate Promotions > Calendar. When navigating to both Gantt charts, the
default may not display any records or bars in the chart until the user navigates to a period that contains records. (12-
9PYFQ6)

Globalization
Localization
Additional List of Values Required for Consumer Sector
The following is applicable for German (DEU), Italian (ITA), Brazilian Portuguese (PTB), Swedish (SVE), and Japanese
(JPN) language packs. The following table of List of Values (LOVs) need to be added for German (DEU), Italian (ITA),
Brazilian Portuguese (PTB), Swedish (SVE), and Japanese (JPN), to be able to select Presented status after Approved-
Pending Review status, from the Plan or Promotion Status field.
LOV_TYPE VAL NAME LANG_ID
PROMOTION_STATUS Presented Presented ENU
PROMOTION_STATUS Präsentiert Presented DEU
PROMOTION_STATUS Presentato Presented ITA
PROMOTION_STATUS Apresentado Presented PTB
PROMOTION_STATUS Visade Presented SVE
PROMOTION_STATUS Presented JPN
(12-B5O8VD)
Siebel Assortment Planning - Spread Quantity in Category Targets
The following applies for German, Spanish, French, and Swedish language releases. To be able to use Spread Quality
function in Category Targets, users need to change following LOV values from old to new values as indicated below:
1) German
Language
Independent
NEW VALUE
Type OLD VALUE Code Language Name
DEL_PERIOD_TYPE Wöchentlich Woche Week Deutsch
2) Spanish
Language
Independent
Type OLD VALUE NEW VALUE Code Language Name
DEL_PERIOD_TYPE Semestr Semestre Half-Year Español (moderno)
DEL_PERIOD_TYPE Saison Temporada Season Español (moderno)
DEL_PERIOD_TYPE Semestre Año Year Español (moderno)
3) French
Language
Independent
NEW VALUE
DEL_PERIOD_TYPE Year Ann. Year Français

4) Swedish
Language
Independent
NEW VALUE
DEL_PERIOD_TYPE Trimestre Kvartal Quarter Svenska
DEL_PERIOD_TYPE Semestr Halvår Half-Year Svenska
DEL_PERIOD_TYPE Year År Year Svenska

Siebel Communications, Media and Energy Known
Anomalies
8
The chapter provides information on known anomalies and work arounds specific to the Siebel eCommunications, Siebel
eCommunications for Wireless, Siebel Energy, Siebel eMedia, and Siebel eOil, Gas and Chemical applications.
General Options
Account Management
Accessing Account Address View in Mobile Web Client
When accessing Account Address View from a Mobile Web Client, the user may experience a long delay. Users can
alleviate this problem by making the following configuration changes:
Existing Business Component: Account
Existing MVLink: Bill To Contact
Destination buscomp: SIS Contact (Perf)
Destination link: Account/SIS Contact (Perf)
Existing MVLink: Ship To Contact
Existing MVLink: Primary Contact
(12-B5ZYH2)
Accessing Account Profile View
When accessing Account Profile View from a Mobile Web Client, the user may experience a delay. User can alleviate this
problem by making the following configuration changes:
1. Modify the Applet Account Contact List Applet – Grandchild
2. Change Properties:
Buscomp: SIS Contact (Perf)
(12-B5ZYHU)

Siebel Communications, Media and Energy Known Anomalies
Account Hierarchy Drag and Drop Functionality
On the Account Hierarchy view in the Accounts screen, a user can move an account around the account hierarchy diagram by
selecting the desired account and dragging it to another location. Users must be careful when using this feature since accounts
can be separated from the rest of the account hierarchy. If a user disassociates an account from its hierarchy in this view, the
relationships previously specified will be disassociated across the application. (12-9PTCDX)
Navigation
On the Account Hierarchy & Account Profile views in the Accounts screen the user will not have use of Previous & Next
navigation arrows on the account list applets. (12-9T40RT, 12-9P4276)
Activities
Workaround for Slow All Activities view
Customers using Siebel 7.0.4 on Microsoft SQL Server will experience slow performance on All Activities view.
Customerswho do not use HTML email feature can disable the EMAIL BODY field in the All Activity Applet to work
around the performance problem. To apply the work around the following steps need to be taken in Siebel Tools and a new
srf file generated:
3. Map Display Email Body Field to EMail Body in Comm Inbound Item Body Applet: HTML TextAreaMsgBody is a
control in Comm Inbound Item Body Applet. The value of the Field property for this control is Display Email
Body. Change this value to Email Body for the workaround
4. Map Display Email Body to Email Body in Comm Inbound Item Form Applet by setting the Field value to Email
Body from Display Email Body for control HTML TextAreaMsgBody in the Comm Inbound Item Form
Applet.
5. Set Force Active to False for Email Body in Action BC
As a result of this work around the Message Body in Inbound Item List View and Incoming Message in Communication
Detail - Response View will only display plain text. (12-B91BL3)
Integration
Error Using CUT Sample Fraud Alert IO with OS/390
The number of joins required for the out of box CUT Sample Fraud Alert IO integration object causes an error when running
against IBM OS/390. It is recommended to mark extra, unnecessary fields inactive in order to bring the total number of joins
to less than 30. (12-B59LUZ)
Loyalty Profile
Loyalty Profile for eMedia
The Loyalty Profile – Communications view is used in the eMedia product, rather than a separate Loyalty Profile – Media
view. (12-6VQ4NY)
Primary Contact
The Primary Contact field of the Account applet displays the Primary Contact’s last name only. (12-74LL1R, 12-77RHTM)

Orders
Copying Order Line Item Erroneously Copies Field
The “Asset Integration Id” field is erroneously copied when you copy an order line item (e.g. by pressing [CTRL] B). This
causes downstream processing to merge the two line items and is likely to result in data loss or corruption. To fix this issue,
use Siebel Tools to set the “No Copy” flag to “Y” in the “Asset Integration Id” field of the “Order Entry - Line Items”
business component. (12-DIMOQ3)
eService: Billing Statement History: Statement Comment, Taxes & Surcharges field does not reflect updates
A billing statement created in Siebel eCommunications does not reflect the correct values for the Taxes, Surcharges and
Comments fields when viewed in eService My Accounts,/Billing Statement History for that statement (12-B72893)
Inability to add Product to Work Order Line Items
When the user adds a product to Work Order Line Items Applet, he may encounter the following error message: An error has
occurred in executing a SQL Statement. Please continue or ask your systems administrator to check your application
configuration if the problem persists. This behavior will be experienced only in the DB2/S90 platform. This is caused by too
many fields in the pick map for the product field in the business component Com Work Order - Line Items. To correct this,
customers can reduce the number of fields being pick mapped. (12-B4V71A)
The action on a root customizable product is changed to Update when a child product is added during the Modify
order.
Users may find that when any existing components are modified (or) new components are added, the action on a root
customizable product is changed to Update from Existing (-)during a Modify order. While this behavior will not impact the
order processing workflows in any way, this can be corrected through applying the following changes in Siebel Tools.
Inactivate the following user properties in the Order Entry - Line Items business component:
Refresh Price Pre Method Invoke 0: ClearPrice
SIS OM On Field Update Set 4: "Adjusted List Price", "Action Code", "IIf ([Action Code] = LookupValue
('DELTA_ACTION_CODE', 'Existing'), LookupValue ('DELTA_ACTION_CODE', 'Modified'), [Action Code])"
SIS OM On Field Update Set 7: "Pricing Comments", "Action Code", "IIf ([Action Code] = LookupValue
('DELTA_ACTION_CODE', 'Existing'), LookupValue ('DELTA_ACTION_CODE', 'Modified'), [Action Code])”. (12-
B92X5B)
Cannot add an Account to an Order after updating Bill to/Ship to
Consider the following user scenario:
User navigates to Orders > All Service Orders.
1. User finds an order with an existing account that does not have Bill to/Ship to information.
2. User adds Bill to/Ship to addresses to that account
3. User goes back to the order and repicks the same account. The following error message is shown:
Extension Field 'Primary Ship To Address' cannot be updated unless it

has been activated

To overcome this, customers can create a new list column in Siebel Tools and map it to the field Primary Ship To Address in
the Order Entry - Order List Applet. (12-B61A8L)
The work around for this Oracle performance defect is to change portion of searchspec from (AND Name LIKE “*”) to
(AND Name >= “ “) in “PickList Price List”. Note that there is a space in quotes. It cuts down SQL time from over 1 second
to 0.1 seconds. (12-B45W2R)
Other
Accessing Agreement Contact Detail View from Mobile Web Client
Users may experience slow response time when accessing Agreement Contact Detail View in a Mobile Web Client
environment. The response time can be improved by making the following configuration changes:
In BC Service Agreement
MVLink Bill To Contact
MVLink Ship To Contact
MVLink Legal Contact
Change Destination buscomp from Contact to SIS Contact (Perf)
Change Destination link from Account/Contact to Account/SIS Contact (Perf)
Link Service Agreement/Special Contact
Clone into Service Agreement/Special SIS Contact (Perf)
(12-B5ZYIJ)
Service Requests and Trouble Tickets
Verifying Entitlements
Within the Agreements screens, an Entitlement can be built for a specific Account, Contact and Product combination. This
Entitlement should appear when a Trouble Ticket is entered for the aforementioned Account, Contact and Product
combination, and the Verify button is pressed. Currently, the Entitlement is not appearing correctly. This feature can be
corrected through basic configuration in Siebel Tools. (12-BAI6QZ)
Account Number Refresh
After creating a new Service Request and picking an Account Name for the Account field, the Account Number would only
be populated in the Account # field after user goes to a different screen or does a query and then come back to the record.
(12-9T4ENH)
Service Items and Type field Labels
The Product selected from the Service Item pick applet will populate the Type field, and the corresponding Service ID value
will populate the Service Item field. This may present some confusion initially, however it can be corrected by relabeling the
Type field to another name, for example Product Name or Service Item. The Service Item field can be relabeled as Service ID
field. To make sure that you get the appropriate list of Service Items in the pick applet, the Account field needs to be
populated. (12-9P1RVG)

Products field is not restricted based on Account and Service Item
The Products field is a Multivalued field that allows the user to pick additional products that are one or more levels below the
Product chosen in Service Item. The Products pick applet will present the user with all the possible Products and is not
restricted by the Account and Service Item values. The user needs to take extra care to pick a value that is applicable to the
customer. (12-9BS0VS)
Service Point Field Display
For some companies, such as Energy and Utility companies, the user may want to display the Service Point information on
the Trouble Tickets applet, especially when the service point is the service item identifier. Out of the box, the field is not
being exposed, but can be configured to have it exposed on the applet. (12-9NLOVL)
Related Service Requests and Related Trouble Tickets View Naming
The naming of Related Service Requests and Related Trouble Tickets view may confuse the user. The Related Service
Requests view allows the user to relate a trouble ticket to one or more trouble tickets. The Related Trouble Tickets view
provides a list of Children tickets, in which the top form applet shows the Parent ticket and the bottom list applets show its
children tickets. The inverse relationship can be viewed in the Parent Trouble Tickets view. (12-9NMALJ)
Ability to update Activities
Under Activity Plans view, be aware that when you change the template of a previously created Activity Plan, the Activities
associated with the new Activity Plan template will not be reflected in the Activities list applet. However, they will be added
to the list of activities (while the old activities for the old template remain) and they can be found under the Activities view.
To avoid this, do not change the template of a previously created Activity Plan. Instead, delete the old Plan and create a new
one. (12-9C7J5P)
Siebel Release Manager
Test Plan in Release Manager
The Test Plan Administration and Test Strategy Administration views are not supported in this release. (12-9VWZK5)
Siebel Anywhere
Upgrading from Siebel Horizontal Applications 7.0.4 to Siebel Vertical Applications 7.0.4
When using the Siebel Mobile Web Client to access Siebel applications, after a production upgrade with Siebel Anywhere
from Siebel Horizontal Applications 7.0.4 to Siebel Vertical Applications 7.0.4, the user will receive a pop-up message
indicating a new version of software is required. This pop-up message will occur every time the upgraded installation is
accessed. A patch will be made available to correct this problem. (12-B4ZECG)
Siebel eAdvisor
MRC and NRC totals in GetPrice function
The Get Price function does not include the final MRC and NRC totals of the selected product. (12-9VTLKB)

Siebel Analytics
Data Warehouse
Troubleshooting Hints in the Siebel Data Warehouse Installation and Administration Guide) convert the sessions to be run in
sequential mode. The problem may be occurring due to several parallel sessions in the batch.
To convert the batches from running in sequential, perform the following:
refresh_Seibel_DW_dimension and refresh_Siebel_DW_fact

LS_SYND_DATA_AGG(PERIODIC). (12-B80ZIB)
Account city names greater then ten characters long are truncated by the ETL process. The workaround is as follows:
lv_COUNTRY change from 10 to 30 (12-B7G1GZ)

Sales, Service and Marketing Analytics
Geography Charts Do Not Include All Accounts
Within the Loyalty Management dashboard, the Churn Score Category by Geography chart, and the Customer Value
Category by Geography chart, include only Accounts with an associated record in the Revenue fact table (W_REV_F) and
Account Geography dimension (W_GEO_D). These reports obtain Account Geography information by joining the Account
dimension (W_ORG_D) to the Account Geographical dimension (W_GEO_D) through the Revenue fact table (W_REV_F).
If no record in the Revenue fact table is available to join the Account dimension to the Account Geographical dimension, no
Account Geography information will be captured. A join from the Account dimension to the Account Geographic dimension
can be obtained by assuring that each Account in the Account dimension contains at least one record in the Revenue fact
table, which also has an associated record in the Account Geographical dimension. Alternatively, Account Geographical
analysis can be performed within another star. (12-B0TVS7)
Customer Analytics Dashboard
Error Message Displays When Attempting to View Dashboard
When selecting the Customer Satisfaction Analytics dashboard within the Service Analytics screen, an error message appears
stating that the page cannot be displayed. To correct this, make the following configuration changes:
1. Open application
2. Login with a User ID that has modify access to Integration Administration > Symbolic URL Administration;
3. In Symbolic URL applet, search for Name sISMCMServiceDashboard6
4. In symbolic URL Arguments applet, search for Name Cmd, then change its Argument Value to PortalPages (12-
B570YJ)
Error Message Displays When Viewing Dashboard
When displaying the Customer Analytics dashboard within the Sales Analytics screen, error messages appear, referencing
symUrlArgCmd, which prevent charts and reports from displaying. To correct this issue, make the following configuration
changes:
1. Open application
2. Login with a User ID that has modify access to Integration Administration > Symbolic URL Administration
3. In Symbolic URL applet, search for Name sISMCMSalesDashboard4
4. In symbolic URL Arguments applet, search for Name replaceResponseWithForm, then change its Argument Value
to replaceResponseWithForm (12-B4VZTN)
Loyalty Management Dashboard
Key Performance Indicator Metrics Displayed Inconsistent With Corresponding Metrics In Fact Table
The Actual Churn page, embedded within the Loyalty Management dashboard, contains two charts that use metrics
originating from the Key Performance Indicator (KPI) star. These charts are the Number of New and Churned Accounts
chart, and Churn-to-New Account Ratio chart. Metrics displayed in these charts may be inconsistent with the corresponding

metrics they map to within the KPI star fact table. These inconsistencies may also be reflected in reports run off of KPI star
metrics using Siebel Answers. (12-B0U1SY)
Revenue Management Dashboard
Incorrect Scale Displayed on Graph Axis
The Conversion Rate by Service Type report displays incorrect percentage figures on the y-axis scale. The percentage figures
are displayed in the thousands, while each should be less than one hundred.(12-A3JSOR)
Account Management Dashboard
Additional Filter Attributes Appear During Report Drill Down
When drilling into a bar on the Trouble Tickets By Customer Value report, within the Customer Value page, Account Name is
added to the resulting filter title. Account names are also appended on the Customer Value items in the LOV. (12-
9WGRUD)

in a Western European codepage, the Japanese text will appear as question marks(???). This behavior is limited to displaying
Multiple Siebel Analytics servers can be configured to access the same data source. In the model where a site needs to render
Chinese, Japanese, and Western European regional data as charts, three servers should be configured to access the same data
sources.
Packaged Product Support (Not applicable to Siebel ePharma Analytics)
Packaged products are not supported in the eBusiness Data Warehouse. (12-6W8MPN).

Siebel eChannel
Siebel eChannel Partner Commerce
Customer Portal Thread Bar
Users may encounter a situation where the view they are taken to when drilling down on a service item in the Account
Customer Portal view does not match the name indicated in the thread bar. (12-9RMZYN)
Ability to Go Back to Customer Quotes from Products Catalog
Users working on a quote can navigate to the Product Catalog from a Quote, using the Browse Catalog button available in the
Customer Quotes view. However, users may find that once they have entered into the Product Catalog, they cannot add their
selected products to the original quote. Any product selection that users make will be written on a new shopping cart, and
from this point, users will have to checkout to be able to order their product selection.
You can create quotes for products selected from the Product Catalog using the following procedure:
1. Add your product selection to a new shopping cart.
2. Assign the Account and Account Contact you want to assign the quote to by using the Edit button available on the
Shopping cart view.
3. Save your product selections as a new quote using the Save Cart feature available in the Shopping Cart.
4. Go to Customer Quotes and query for the quote you previously created and continue the quoting process.
The success of this approach depends on the user starting the quote process from the product catalog, saving the shopping
cart as a quote, and finishing the quote definition from the customer’s set of assets. (12-9N6484)
Navigation During Order Revision
When users are revising an order from My Saved Orders, they may find the following behavior: After clicking Done in the
Product Configurator Runtime session they will be taken to the Customer Orders Line Items view. While this behavior does
not disrupt the ordering flow, it may be an issue if the user does not have the Customer Orders Line Items view under their
responsibilities. Therefore, Web Registered Customers should not have access to the Revise button in My Saves Orders,
Order Detail view. (12-9T4JZF)
Organization field in eChannel Customer Quotes
In Customer Quotes, upon Drill down or New quote, customers may consider hiding organization field if they choose not to
share this info across partners. (12-9NKE58)
Siebel ePricer
Prices shown in Configurator
An observation that the user may have is when he increases the quantity of an existing asset in the configurator, there will be
no changes to the totals of the complex product within the configurator. Instead, when he returns to quotes, the quote line
item will show the added product with the correct price and totals. (12-9V4DXG)

Manual adjustments and discount reason in Totals
For this release, when the user enters manual adjustments and discount reason in the Totals applet of a Quote, these
adjustments will not be transferred automatically from the quote to the order. Instead, the user will need to reenter them in the
Orders view. (12-9T0I24)
Siebel Complex Order Processing

Summary template themes in Configuration UI designer do not show MRC/NRC
The summary template does not display MRC or NRC totals. The standard summary theme templates can be modified to
display MRC/ NRC Totals as well as any order management specific fields such as UoM, Service Id and so on. (12-9SQ5UI)
Order header &and Order line items do not have due dates calculated on submit
Due dates on the Order header and line items are not calculated automatically on the basis of standard lead times. The due
date is defaulted to Current Day + 30 and users can manually change it on Order Header/and Line Items. (12-82QBM9)
Cancel and Save buttons are disabled within a configuration session
The Cancel and Save buttons are disabled within a configuration session. Users can exit the Configuration session by clicking
Done. (12-9SQUZN)
Transfer of Service on AIX
The Required Delivery Dates within the Add quote line items generated by the move or transfer of service workflow have to
be manually verified. The verification is required only if running the server on an AIX environment. (12-9YXS57)
Siebel ePricer
Adjustment MRC/NRC after Reprice All
When Reprice All is pressed or whenever Pricer is called the Manual Adjustment MRC in the Totals applet of a Quote or
Order will not be cleared while Adjustment NRC will be cleared..
It is good practice to always reenter the Adjustments NRC and MRC after pressing the Reprice All button. (12-9SZGEL)
Tax % and Shipping Charges in Orders
The fields Tax % and Shipping charges in the Orders view, Terms applet, has currently no link to the fields Tax for NRC, and
Shipping for NRC, in the Orders view, Payments-Totals applet. This is because most customers will customize the Tax and
Shipping algorithm, rather than apply the simple tax calculation supplied.
Nevertheless, the Tax % and Shipping charges fields in the Quotes view, Terms&Totals-Terms applet, does have an effect on
the fields Tax for NRC, Shipping for NRC, in the same Quotes view, Terms&Totals-Totals applet. Therefore, it is
recommended that the user set the tax rate and shipping charges in quotes, and use the quote-to-order workflow to transfer
them to orders. (12-9Q1C1B)

Product Total MRC in Quotes view, Terms & Totals applet represents both non-service and service products
The Product Total MRC field in the Quotes view, Terms&Totals applet represents both nonservice and service products,
while the Product Total NRC field represents only nonservice products.
For service products NRC, there is an additional field Service Total NRC, while there is currently no such field for MRC.
(12-986JIV)
Factors on the root of the complex product
Factors on the root of the complex product in a price list pricing model will fire and change the net price, but have currently
no effect on the MRC/NRC subtotals. The Totals will be re priced and refreshed.
The MRC/NRC Subtotals will remain unchanged by the factors and will not sum up to the Totals. To avoid this situation, it is
recommended that the user not write a factor in a price list pricing model for the root of a complex product. Instead, the factor
for this product should be written using the customizable pricing model.
In addition, if there exists a nonproduct specific factor in the price list pricing model, for example an account specific factor,
the user will need to put in a condition using the designer flowchart to request Pricer to ignore the root complex products in
its firing routine. (12-9UA8L3)
Volume Discount
Volume discounts on the root of a complex product will fire and change the net price, but have currently no effect on the
MRC/NRC subtotals. The Totals will be re priced and refreshed.
Volume discounts, as stated in the Bookshelf for Pricing Administration, was not designed to work for components of a
complex product. It is recommended that the user do not give any volume discounts to complex products. Volume discounts
to simple products is fine. (12-9VSXHN)
Siebel Handheld and Wireless

Adding a product to a Service Request
Users can use the wireless application to create Service Requests (SR) and associate products to the SR, however, when
looking up the SR in the Zero Footprint client using a browser they will not see the associated product. This is because the
relationship between SR and Product is many-to-many in Siebel eService and this relationship achieved by a Link. In the
Siebel eBusiness Applications, Product and SR’s relationship is one-to-many and this relationship is made by join. (12-
9RJJ1H)
Siebel Marketing
Siebel Marketing Manager
Volume Discount
Volume discounts on the root of a complex product will fire and change the net price, but have currently no effect on the
MRC/NRC subtotals. The Totals will be re priced and refreshed.

Volume discounts, as stated in the Bookshelf for Pricing Administration, was not designed to work for components of a
complex product. It is recommended that the user do not give any volume discounts to complex products. Volume discounts
to simple products is fine. (12-9VSXHN)
Siebel Quotes
Ending Configurator Runtime Session Takes User to Shopping Cart
In this release, users customizing products from the product catalog will be taken to the shopping cart after clicking Done
during the Product Configurator runtime session, instead of the quote line items. To correct this behavior you can apply the
following procedure in Siebel Tools:
• Launch Siebel Tools and navigate to Business Service in the Object Explorer.
• Query for shopping Service in the Name field.
• Expand the Business Service object and navigate to Business Service User Prop, and query for Customize Return
View*. Two user properties will be returned: Customize Return View and Customize Return View - Horz.
• Rename Customize Return View to Customize Return View - Old and make it Inactive.
• Rename Customize Return View - Horz to Customize Return View and make it Active.
• Recompile SRF file and launch the application. (12-A0K7RR)
Siebel eSales
Adding New Shipping Addresses
A web corporate user, who is attempting to add a shipping address by selecting the Add button on the Shipping Address
applet, will experience the following message:
Error: Applet: %1 does not have the %2 template file specified.
This can be overcome by completing the following:
1. Launch Siebel Tools
2. Navigate to Applet object in the Applet Explorer
3. Query for Quote Business Address List Applet (eSales)
4. Navigate to Applet Web Templates and in the Name field, query for Edit template.
5. Change value of property Inactive from FALSE to TRUE
6. Recompile the srf. (12-B7HKN3)

Orders placed by Delegated Customer Admin
The order status will default to Awaiting Approval on orders a user with the Delegated Customer Administration
responsibilities purchases on eSales. This may present some confusion because users may expect the order to register as
automatically approved since the user is a Delegated Customer Admin. To make sure that the order is automatically approved
upon order processing one can make the following modification
1. Launch application Siebel eCommunications and log in as an administrator.
2. Navigate to Siebel Workflow Administration screen and Workflow Processes view.
3. Query for workflow CUT eSales – Set Order Status and navigate to Designer view.
4. Drilldown on step User Type? and set focus on branch Power User.
5. In the Values applet change value of the first record as follows:
Original: [User Type] = LookupValue("CONTACT_USER_TYPE", "Web Delegated Customer Admin")
New: [User Type] = LookupValue("CONTACT_USER_TYPE", " Web Delegated Customer Administrator")

(12-B6ONGE).
Adding products from Siebel eMarketing and Siebel eSales to the Shopping Cart
When products from the eMarketing and eSales applications are added to the same Shopping Cart, unexpected pricing, quote
and order information may be displayed. (12-5SUODI, 12-5R2CIR, 12-5LW0CB)
Editing Billing Account in check out process
After selecting a Billing Account in the checkout process, users will not be able to edit the Billing Account. (12-9SQ5U9)
Simple Products in Supplemental Orders
For this release, users will not be able to change product attributes of a simple product on a supplemental order. (12-
8VWF97)
Supplemental orders with orders waiting for approval
Users may create orders that require approval by another individual in their organization. In this release, users will not be
able to create a supplemental order for orders that have status awaiting approval. (12-9SCU2M)
Other
Address Line 2 is not Available
During the definition of a new Bill to Address in the checkout process, users will not have Address Line 2 available. (12-
9T4JZB)
Drill downs available on Quote Summary (eSales) and Quote Summary 2 views.
Users are allowed to drill down on any given product listed in the Order Summary -Quote Summary (eSales), and Account
Verification view -Quote Summary 2 (eSales). Drilling down on a product will bring the user to the Product Detail view, but
the user will not be able to view some details of the product such as product attributes. In addition, if the user clicks the OK
button in this view, she will be taken to back to the Shopping Cart view. To prevent this behavior, Administrators can remove

the drill down definition for these list applets on these views. In Siebel Tools, Administrators need to identify the CUT Quote
Item Read-Only List Applet (eSales) applet for the Quote Summary (eSales) view, and set its drill down object flag to
Inactive. The same procedure needs to be completed to CUT Quote Item List Applet - Summary (eSales) applet for the CUT
Quote Summary 2 (eSales) view. (12-9T4JZ7)
Reorder Functionality
For this release, the ability to reorder a previously created order is not available. (12-9TTYH3)
Adding contacts to an account
Users cannot add new contacts to an account. (12-6PKCEN)
MRC/NRC totals on views
MRC and NRC totals are not exposed in some views such as the Persistent Shopping Cart in the Home Page, My Orders, My
Quotes, My Company’s Orders, My Company’s Quotes, and so on. (12-926AYF)
Quantity Column in Order Summary
The quantity field is not exposed in the Account Verification view -Quote Summary 2. This can be configured with Siebel
Tools. (12-9BY12J).
ZIP Code in Bill Me Address
During the eSales check out process, if the user selects the bill me option, the application requires a ZIP Code to continue the
check out process. (12-9NLVTA)
Cancel an Order
For this release, the ability to cancel a previously created order in My Orders is not available. (12-9UYDC7)
Web Purchasing Manager able to create new accounts
A user with Web Purchasing Manager responsibility is currently able to add new accounts in Account Management. A user
with this type of responsibility should not have this ability. (12-8STD3M)
Calculations for Shipping Charges
In this release, every item in the shopping cart is used to calculate shipping charges. Only items with the ship to flag checked
should have shipping charges calculated. (12-9SQ5UB)

Siebel eService
Service Request
Enabling Siebel Communications, Media, and Energy Home Page for eService and eCustomer
The eService and eCustomer application for CME have a specific home page designed to reduce the number of clicks needed
to execute most common tasks specific to the Communications, Media or Energy industries (that is accessing billing
information). Enabling both home pages requires the modifications detailed below.
For eService and eCustomer, in Siebel Toolsselect the Application object type and look for the Siebel eService application.
Change the Acknowledgement Web View to CUT eService Home Page View (eService). Expand the Application object type
and select Page Tab. Drill on the Screen named service Request Screen (eService). Change the default view to CUT eService
Home Page View (eService).
For eCustomer only, in Siebel Tools select the Application object type and look for the Siebel eCustomer application. Change
the Acknowledgement Web View to CUT Home Page View (eCustomer). Expand the Application object type and select
Page Tab. Drill on the screen named eCustomer Home Screen. Change the default view to CUT Home Page View
(eCustomer).
In X:\..\ SWEApp\Bin directory edit eapps.cfg and apply the following changes:
For eService: in [/eservice] section, set StartCommand = CUT+eService+Home+Page+View+(eService)
For eCustomer: in [/ecustomer] section, set StartCommand = CUT+Home+Page+View+(eCustomer)
(12-9TISYS)
Siebel Work Orders

Work Order does not auto populate line item due date
Users creating a New record in the Work Orders>Line Item Actions list applet will find that the Due Date field does not get
automatically populated, even when this field has been filled out previously for the Work Order. (12-9R45I2)
No drilldown Available on Product Field in Line Item View
Users creating a New record in the Work Orders >Line Items view, will find that once they have added a new product to the
Product field there is no drill down available to see the details of the product. (12-9NG3S9)

Globalization
Localization
Postal Code Field
The following is applicable for the German Siebel Industry Solutions release. In the My Company Address Book
Administration view, the postal code or zip code field is not available when creating a new record. (12-B6ONG6)

Siebel eHospitality Known Anomalies 9
Siebel Analytics

in a Western European code page, the Japanese text will appear as question marks(???). This behavior is limited to displaying
same data sources.
It is also recommended that cross regional charts are designed to use measures and facts in the Analytics metadata rather then
display values taken directly from the data source. This will minimize, and in may cases remove, the impact of code page
processing on development and maintenances of the Analytics Applications. (12-BE3XFF)
Siebel eEvents Execution

Functions & Function Line Items
AutoBook
Critical assets are not automatically booked when they are part of a complex product. Use AutoBook button to reserve these
items. (12-B3ZFTN)
Adding New Line Items
When adding a new products, users should create a new line item rather than choosing a new product for an existing line
item. Following the latter course of actions results in the original product’s price being used for the new product. (12-
BAA1RR)
Charge Flags
Flags for Svg Chg Inclusive, Tax Inclusive, Waived and Complimentary are unique to the parent product and do not transfer
to its child products in function line items. (12-9BUSPN)

Siebel eHospitality Known Anomalies
Copying Functions
The Siebel back arrow will not return the user to the appropriate screen after copying a function, drilling down on the
function type or name, and then clicking on the Siebel back arrow. (12-9NYASU)
Expired Child Products
Menus or packages with expired child products cannot be added to function line items. (12-9RJSXF)
Orders
Notes
Notes appended to an order are not automatically sorted by sequence number. (12-9CGP7S)
Properties
Property Team
The pop-up window that appears in the More Info view when adding members to a property team should be labeled Property
Team rather than Account Team. (12-9R0EJ7)
Reports
Contact
Adding a contact to an order suppresses the printing of an account’s mailing address in the BEO report. (12-B4A4XJ)
Date Field
The date field in an invoice does not contain enough space to show the year when days with long names (such as Wednesday)
are present. (12-9UQ0KP)
Dollar Signs
Dollar signs should be added next to the dollar amounts in reports. (12-9XMBNN)
Decimal Places and Line Items in an AIX Environment
Reports run on a Reports Server using the AIX operating system show five decimal places.Some line item may be included in
the functions section. (12-B8Y42R)

Siebel Life Sciences Known Anomalies 10
This chapter provides information on known anomalies and work arounds that are specific to the Siebel ePharma, Siebel
eClinical, and Siebel eMedical applications.
General Options
Reports
Samples - Inventory Adjustments report
The Lot # column does not appear on the Samples Inventory Adjustments report. (12-6YQZCT)
Meeting Profile report
The Start Date for activities does not appear on the Meeting Profile report. (12-9PEXMU)
Product Data Missing from Clinical Reports
The Product field does not list any data in the following reports: Planned versus Actual Visits; Actual Visits, and Site
Initiation\Document Tracking. (12-9PEOZJ, 12-9PEXMQ, 12-9PGZRE)
Upgrade
Siebel Anywhere
When upgrading from prior releases of Siebel Life Sciences, the configuration file needs to be copied and renamed. From the
Siebel\BIN\ directory, copy the pharma.cfg file and rename it to epharma.cfg.
Actual Cost Values in Medical Education events
Cost Allocation applied to Products and the MedEd Team fields on Pharma ME Event List View, now has percentages
instead of decimals. In order to migrate existing data from prior versions on Siebel ePharma, the following script needs to be
applied: (12-9OYX47)
update S_ME_EVT_POS_LS set COST_ALLOC = COST_ALLOC * 100

where (COST_ALLOC >= 0 and COST_ALLOC <= 1)
/
update S_ME_EVT_PRD_LS set COST_ALLOC = COST_ALLOC * 100
where (COST_ALLOC >= 0 and COST_ALLOC <= 1)
/

Siebel Life Sciences Known Anomalies
Cost Roll Up
In order for costs to roll up correctly to the project level, every cost item needs to have an associated currency code. In order
to migrate the data from prior versions on Siebel eClinical, which did not support currency code for clinical payments, the
following scripts needs to be applied after the upgrade is run: (12-8XGNQA)
update S_PTCL_SITE_LS
set AMT_CURCY_CD = “USD”
WHERE AMT_CURCY_CD IS NULL
;
update S_SRC_PAYMENT
SET AMT_CURCY_CD = “USD”
WHERE AMT_CURCY_CD IS NULL
AND PTCL_SITE_ID IS NOT NULL
;
update S_EVT_ACT
where AMT_CURCY_CD IS NULL
and CL_PYMNT_ID IS NOT NULL
;
update S_CL_PTCL_LS
where AMT_CURCY_CD is null
;
commit
;
Meeting Activities Start Dates
When upgrading from prior releases to Siebel Life Sciences 7.0.3, the following script needs to be applied in order to
preserve the data in the Start Date field on the Pharma Meeting Activities View when using the Back button: (12-9ZA4M)
update S_ACT_EMP
set (ACT_TODO_PLNSTRTDT
, ACT_APPT_START_DT
, ACT_TODO_PLNEND_DT
) = ( select
a.TODO_PLAN_START_DT
, a.APPT_START_DT
, a.TODO_PLAN_END_DT
from S_EVT_ACT a
where S_ACT_EMP.ACTIVITY_ID = a.ROW_ID
and a.SUBTYPE_CD = “Meeting Activity”
)
where exists ( select “x”
from S_EVT_ACT a
where S_ACT_EMP.ACTIVITY_ID = a.ROW_ID
and a.SUBTYPE_CD = “Meeting Activity”
)
;
commit
;

Other
Activities in Activity Plans Require Manual Refresh
Changes made to Activities in the Activity Plan Action Applet need to be manually refreshed. (12-9OQGCQ)
Unsupported Views from Formulary Opportunity Management
The following views from prior Siebel releases are not supported in this release: (12-4W0HMB, 12-69L5GJ)
Pharma Contracts List View
Pharma All Contracts List View
Pharma Contracts Explorer View
Pharma Price Groups And Accounts View
Pharma Price Groups Non-Product Fee View
Pharma Price Groups Product Fees View
Pharma Contracts Payments View
Pharma Account Contracts View
Siebel Analytics
Data Warehouse
lv_COUNTRY change from 10 to 30 (12-B69ANR)


in a Western European code page, the Japanese text will appear as question marks(???). This behavior is limited to displaying
Multiple Siebel Analytics servers can be configuring to access the same data source. In the model where a site need to render
Chinese, Japanese, and Western European regional data as charts, three servers should be configured to access the same data
sources.
Siebel eClinical Manager

Copying Subject Visit Templates
When copying a visit template in the Clinical Subjects Parent Visit Templates List Applet, the record needs to be manually
refreshed. (12-8GMLAB)
Project Costs
In the Project Costs View, the total amount is not displayed in the Project Cost Activity List applet or the Project Item Cost
List applet. All costs roll up correctly to the Project Entry applet. (12-9TUUCL)
Siebel eCommunity
Siebel eCommunity for the Site Portal and the Consumer Portal
The Discussion area is not accessible in Siebel eCommunity for deployments of the Site Portal (Siebel eService for Clinical -
eSitesClinical) or the Consumer Portal (Siebel eService for Pharma-eConsumerPharma). The Discussion area is supported in
the Professional Portal (Siebel eService for Pharma-eProfessionalPharma). (12-9Y7KBF)
Chat Registration in Non-English Languages is not Supported
Registration for Chat sessions in Siebel eCommunity is only supported in English. (12-9Y7KBF)

Siebel eClinical
Siebel Trip Reports
Clinical Site Visits
Site Visit records created in the Clinical Trip Report view are displayed on the calendar of the Principal Investigator of the
Site, and are based the date created . To display the Site Visits based on their Start Dates, map the Start Date field to the
Planned field in the Action Business Component. (12-AYL2VE)
Siebel ePharma and eMedical

Adding a new account address from Data Administration View
When creating a new address for an account using the Data Administration View (Account Administration View), the State
field on the Account Address pick applet incorrectly maps to the Address Name field. In order to add a new address to an
account, users should populate the Address Name field with a value other than the value in the State field or add the new
address using the All Accounts View (All Accounts List View). (12-B6SO6V)
Distribute Cost Button on Meetings
When distributing meeting costs across attendees using the Distribute Cost button, the cost for each attendee on the Pharma
Meeting Attendee List Applet and the total cost on the Pharma Meeting Form Applet incorrectly read as zero on the Spanish,
German, Italian, French, Swedish, Japanese, and Brazilian Portuguese versions. (12-B5FR8R)
New Contact Calls and Account Calls using New Call button
New Contact Calls, and Account Calls created using the New Call button on the Contact and Account screens, incorrectly
show the duration as 60 minutes on the Daily Calendar View (eCalendar Daily View – My), regardless of the duration
specified while creating the call. (12-B6RXW7)
New Account Calls using Schedule button
New Account Calls created using the Schedule button on the Account screen incorrectly show the duration as 60 minutes on
the Daily Calendar View (eCalendar Daily View – My), regardless of the duration specified while creating the call. (12-
B1OYH8)

Accounts
Attendee Calls with Samples
The ability to submit an account call detail with samples disbursed to attendees may cause an error indicating that the Due
Date or Transaction Date is a required field. To correct this behavior, a new list column for the Start Date field should be
added to the Pharma Attendee Call List Applet. (12-BAT2C7)
[Brick]Rep can add Brick from Account View
End users should not be allowed to update Account Brick information. In order to prevent users from being able to update
Account Brick information, the following workaround needs to be applied:
1. Lock project 'Com Account'
2. Query for applet 'SIS Account Entry Applet'
3. For applet control 'Brick' set Read Only property to True
4. Compile applet
5. Unlock project
(12-FN5XNK)
Objectives
Objectives Activities view is not supported
The Objectives Activities view (CPG Retail Objective Activity View) is not supported in this release. (12-BBCO4J)
Other
Assignment by Brick
While setting assignment criteria to Account Brick or Contact Brick on the Assignment Rules View, dynamic column names
do not appear on Assignment Rule Item List Applet. In order to make dynamic column names appear , the following work
around needs to be applied using Siebel Tools:
2. Lock the projects Assignment (SSE) and Pharma Assignment
3. Navigate to Assignment Criteria, find record with Name Account Brick

4. Navigate to Assignment Criteria Attribute, set column Display Name to Account Brick on the lone record
5. Navigate to Assignment Criteria, find record with Name Contact Brick
6. Navigate to Assignment Criteria Attribute, set column Display Name to Contact Brick on the lone record
7. Compile the 2 projects and use the new srf file in the application (12-BF9XMH)
Syndicated Data
DB2 390 requires that all view names be less than 18 charters in length. The s_EXTDATA_NODE_VIEW used in the
Syndicated Data loading process exceeds this requirement. To correct this behavior, the view name in Siebel Tools should be
modified to be less than 18 characters in length, and the Synexp.cpp file should be updated to reflect the new view name.
This file can be found in the following directory: \server\dbutil\tabexp\synexp.cpp. This modification only affects customers
using DB2 390. (12-AV31BZ)
Performance
New Contact Calls
The New button located on the Pharma Professional Call Form Applet may have sub optimal response time when connected .
To remedy this situation, the default search specification and a new user property on the Pharma Professional Call Business
Component needs to be modified as follows.
Change Existing Search Specification to:
([Category] =LookupValue(‘tODO_TYPE","Professional Call") or [Category] =LookupValue(‘tODO_TYPE","Attendee

Call")) AND [Category] > “0”
Add New User Property:
Name: All Mode Sort
Value: False
NOTE: These settings only affect Oracle users. (12-9W7PIF)
New Call Button
The New Call button located on the Pharma Professional Form Applet may have sub optimal response time. To remedy this
situation, the default setting for the mobile web client SWX and SWP cache size needs to be modified. The default sizes for
these caches can be modified in the epharma.cfg file. Increasing the cache values may increase the memory consumption on
the client machine. Note, these settings only affect the mobile web client. (12-B3WW5Z)

Siebel ePharma Analytics

Troubleshooting Hints in the Siebel Data Warehouse Installation and Administration Guide), convert the sessions to run in
sequential mode. The problem may be occurring due to several parallel sessions in the batch. To convert the batches from
running in sequential, perform the following:
refresh_Seibel_DW_dimension and refresh_Siebel_DW_fact”;

LS_SYND_DATA_AGG(PERIODIC). (12-BAF2S7)
Siebel Rx Sales Analytics
Slow performance when building aggregate measures in the eBusiness Data Warehouse
Customers have experienced slow performance when building aggregate measure (MAT, YTD, TTD, TTDLY) in
W_SYND_DATA_F with large data sets (over 100 million records). (12-9TTLIG)
Siebel ePharma Answers
Clicking on Answers gives an error message and the user must log in again to see screen contents
Customers will experience an error when accessing Answers Analytics screen. Clicking on answers gives an error message
and theuser must log in again to see screen contents. This is due to misspelling the Symbolic URL. The work around is as
follows:
1. Open the application
3. Go to View>Site Map>Integration Administration>Symbolic URL Administration
4. In Symbolic URL applet, search for Name sISMLSSiebelDelivers
5. In symbolic URL Arguments applet, search for Name nqUser, then change its Argument Value to UseSiebelLoginId
6. In symbolic URL Arguments applet, search for Name nqPassword, then change its Argument Value to
UseSiebelLoginPassword (12-B5710A)

Clicking on Answers gives an error message and user must log in again to see screen contents
Customers will experience an error when accessing the Answers Analytics screen. Clicking on answers gives an error
message and the user must log in again to see screen contents. This is due to misspelling the Symbolic URL. The work
around is as follows:
1. Open the application
3. Go to View>Site Map>Integration Administration>Symbolic URL Administration
4. In Symbolic URL applet, search for Name sISMLSSiebelAnswers
5. In symbolic URL Arguments applet, search for Name nqUser, then change its Argument Value to UseSiebelLoginId
(12-B452EF)
MedEd Rx Sales
Inability to Combine Rx Sales measures and MedEd measures on a single report
MedEd and Rx Sales measures in the MedEd Rx Sales subject area cannot be combined in a single report. There are two
MedEd measures (NRx before the event and NRx after the event) that can be used to create reports that show prescription
trends for event attendees. (12-B4TLC5)
Siebel Pharma ROI Analytics
Pharma ROI Analytics View Returns Error Message
Using the following ETL to build aggregate measures has slow performance > TEXT=<. Customers will experience an error
when accessing the Pharma ROI Analytics Screen. This is due to misspelling the Symbolic URL. The work around is as
follows:
1. Login as SADMIN/SADMIN
2. View>Site Map >Integration Administration>Symbolic URL
3. Search for Name sISMATSalesDashboard1
4. Change Argument Value of Argument Name SISMLSePharmaROIDashboard1 from resplaceResponseWithForm to

replaceResponseWithForm (12-B570ZK)> RNEND

Siebel ePharma Handheld
Siebel Sales Handheld for Windows CE
Adding City in Account > Address causes sync errors
Adding a value in the City field for an Account > Address causes sync errors. To remedy, make the following configuration
changes in Siebel Tools:
Make the following changes in CUT Address - CE

1. Go to Business Component User Properties
2. Create a new record with the following values -
Name: Propagate Address Fields To Parent BC
Value: City|City CE,Postal Code|Postal Code CE,State|State CE,Street Address|Street Address
CE,Country|Country CE
Comments: Value should contain a comma separated string of source and destination fields that needs to be
propagated to the parent bc. Example: "City|Account City" City is the source field in this BC to copy into the
destination field Account City in the parent BC.
Make the following changes in Pharma Address

1. Go to Business Component User Properties
2. Create a new record with the following values -
Name: Propagate Address Fields To Parent BC
Value: City|City,Postal Code|Postal Code,State|State,Street Address|Street Address,Country|Country
Comments: Value should contain a comma separated string of source and destination fields that needs to be
propagated to the parent bc. Example: "City|Account City" City is the source field in this BC to copy into the
destination field Account City in the parent BC.
(12-F8937D)
Displaying all available accounts in the My Accounts List Applet
To permit displaying of all available accounts in the My Accounts List Applet, take the following steps in Siebel Tools:
1. Go to Pharma Account List Applet - CE
2. Go to the Drilldown Object named Original
3. Clear the Source Field, Business Component and Destination Field properties.
(12-FODVVL)

Deleting or Undoing a line item in Expense Reports
To remedy, make these changes to the "phce.cfg" configuration text file:
DefaultFields8=Expense Item|Exchange Rate|Mileage Rate|ROControl|Mileage Amount|Sum Hotel Total

Reimbursable Amount|Expense Hotel Item|Hotel Item Count|Start Date|Start Date|Is In Progress
(12-FN2FUB)
Primary flag for Account Address deleted incorrectly after sync
The Primary flag for Account Address is getting lost after sync. To remedy, make this configuration change in Siebel Tools:
1. Go to Account BC
2. Go to Multi Value Link in the Object Explorer.
3. Query for Business Address and CUT Address - CE in the Name field.
4. Set the 'Check No Match' property to true.
(12-F8A0KF)
Auto Call inoperative in Account Call/Attendee view for auto-call-created account call
The solution is to set the status of an attendee call to Planned if the parent account call is Auto-Created. To do this, create
two new calculated fields:
Name = Calc Parent Call Status
Calculated Value = IIf (ParentBCName () = 'Pharma Account Call - CE', ParentFieldValue ('Call Status'), '')
Name = Calc Call Status
Calculated Value = IIf ([Calc Parent Call Status] = LookupValue("EVENT_STATUS","Auto-Created"),
LookupValue("EVENT_STATUS","Planned"), [Calc Parent Call Status])
Change the calculated value for Call Status Literal to:

IIf (ParentBCName () = 'Pharma Account Call - CE', [Calc Call Status],
LookupValue("EVENT_STATUS","Planned"))
C++ file fix:

File: pda\ce\src\clients\pharma\fr\frsubmit.cpp
Merged into integration branch: int_7.0.4.320_handheld_mps
(12-FHCNJH)
Updating the Activities view correctly after contact call activities have been synchronized
To remedy, make these changes in Siebel Tools:

1. Go to the Action business component

2. Add Business Component User Prop

Name Value
Update Status To Synchronized Y
(12-FKEC2B)
User Property: SRE Reference Number Required
The User Property SRE Reference Number Required should be set to Y for Handheld implementations. (12-BBQN23)
Sample Reference Numbers
Sample reference numbers should be required for all contact calls. The user property, Paper Reference Number Required
should be set to Y for all handheld implementations. (12-BBK56W)
Predefault Values
As a general rule for the handheld configuration, if there is a predefault value for a column at the table level, all the BusComp
fields that are mapped to that column should meet one of the following two criteria:
Be a required field on the BusComp. or
Have a predefault value of its own (this predefault value can be different from the value at the table level)
This methodology prevents conflict errors during synchronization. Life Sciences business components that require this
update are:
BusComp Field Table Column Default
Account Contact Affiliation Direct Rel Flag S_PARTY_PER DIRECT_REL_FLG N
Contact Account Affiliation Direct Rel Flag S_PARTY_PER DIRECT_REL_FLG N
(12-BAHSS7)
Updates to User Responsibilities
For handheld deployments using Companion Synchronization, administrators should make sure that updates to user
responsibilities should also be accompanied by an update to the PHCE.CFG file on the user's laptop. (12-B8WY6F)
Predefault Values
As a general rule for the handheld configuration, if there is a predefault value for a column at the table level, all the
BusComp fields that are mapped to that column should meet one of the following two criteria:
Be a required field on the BusComp. or
Have a predefault value of its own (this predefault value can be different from the value at the table level).

This methodology prevents conflict errors during synchronization. Life Sciences business components that require this
update are:
BusComp Field Table Column Default
Account Contact Affiliation Direct Rel Flag S_PARTY_PER DIRECT_REL_FLG N
Contact Account Affiliation Direct Rel Flag S_PARTY_PER DIRECT_REL_FLG N
(12-BAK436)
Account Addresses
Edits to existing account addresses from the handheld device will result in synchronization errors. (12-BAI7AF)
Synchronization User Interface
Endusers are advised not to excessively invoke the user interface of the Synchronization dialog on the laptop device during
synchronization or the error reporting process. Doing so may cause errors in the desktop operating system. (12-BAIK7J) 8
Changing the Account during an Account Call Results in Conflict Errors During Synchronization
Changing the account name during an account call results in conflict errors during synchronization. To prevent this situation,
a configuration change should be made using Siebel Tools:
1. Go to Pharma Account Call - CE Business Component.
2. Go to Account Name field.
3. Check the Link Specification flag to true.
4. Go to Pharma Professional Call - CE Component.
5. Go to Account Name field.
6. Add the following in the pre default value field - Parent: Pharma Account Call - CE.Account Name. (12-BAK1ZF)
Editing Logging Parameters in the Setup.ini File
There are two logging parameters in the setup.ini file that need to be reset before you deploy your application. The
parameters and their default values are:
[Logging]
LogSqlStmts = Y
LogSSAErrors = Y
The LogSQLStmts and LogSSAErrors parameters log messages to the sql_stmt_log.txt and ssa_errors_log.txt files,
respectively. You may want to use the defaults for debugging while you are developing your application. However, once you
are ready to deploy your application, reset the values of both parameters to N. Caution: If the LogSQLStmts and
LogSSAErrors parameters are set to Y, then the log files will get very large and use up the available memory on the handheld
device. (12-BCV5RQ)
8

Direct Server Synchronization PDQ Filter Administration
With Direct Server Synchronization deployments in Siebel v7.0.4, the administrator must stop and restart the Handheld Sync
Object Manager process in order to make new or revised PDQ Sync Filters available to users. The PDQ Sync Filters that are
available to the Handheld Sync users are extracted once per server process, when the first user syncs only. The PDQs are not
updated for subsequent sync users orsessions. In addition, the use of Private PDQ Sync Filters, which allow user-specific
PDQ Sync Filters, is not supported. All subsequent sync users will see, if any exist, the first sync user’s private filters. They
will not see their own private filters. Note that these limitations do not apply to Companion Synchronization. (12-B8YX37)
Certain Parent Business Component QBE filters are not being correctly applied to Child Business Components
During synchronization, the Parent Business Component (Pharma Professional Call – CE) QBE filters are not being correctly
applied to the Child Business Components. To correct this, make sure that any QBE filter on the parent business component
is transferred to the first default PDQ to allow lower extraction times. (12-B7R8MV)
A synchronization error will occur if users add themselves as an Employee Participant to a Calendar Activity
If users add themselves as an employee participant to a calendar activity, the following synch error appears: the selected
record has already been added to the list. In order to prevent the user from adding themselves, a search specification should
be added to the Employee Associate Applet in Siebel Tools:
1. Go to Employee Assoc Applet
2. Copy the applet and name it Employee Assoc Applet – CE
3. Add a Search Specification - [Id] <> LoginId() to this applet
4. Go to SHCE Sales Employee (MM) List Applet and change the Associate Applet to Employee Assoc Applet – CE
(12-B6Z1QR)
Activity Synchronization
In a case where two activities have identical information in the Activity Type and Due Date/ Time field, the second activity
will not be synchronized up to the client (12-BAHRNQ)
Samples of Other Unreconciled Inventory Periods get Updated After a Sample Adjustment
Submitting a sample adjustment will have an impact on other unreconciled inventory periods, in addition to the active
inventory period. This condition can be resolved by changing the Pharma Inventory Period - CE business component sort
specification to Start Date. (12-B89KLA)
Users may experience a few minutes of slight degradation in their client (laptop) performance immediately after
exiting from Companion Synchronization
The syncmanager program does not exit immediately after the synchronization dialog has exited. Syncmanager retains a
portion of client memory (from one to ten minutes) after completing the synchronization of the handheld device with that
client. As a result, the user may see a slight degradation in client performance immediately after synchronization has
completed. (12-B7B6S3)
Executing a Query on the Comments field of My Activities will return an error
Attempting to query for an Activity record in the My Activities Screen will generate an error. The user should close out of
the error to resume navigation. (12-B34WC7)

New account addresses are not being propagated in the Accounts - More Info View
The Primary Address of a New Account is not being displayed in the More Information View. To correct this, reconfigurate
in Siebel Tools:
1. Go to applet SHCE Sales Account Entry Applet
2. Go to Applet Web Template Item for this applet
3. Copy the City record and name the new record as City CE
4. On the City CE record, change the control from City to City CE
5. Add Siebel ePharma CE in the expression field for City CE
6. Add NOT Siebel ePharma CE in the expression field for City
7. Repeat steps 3 through 6 for the following fields -
Country
PostalCode
State
StreetAddress (12-B4K5B2)
Account and Contact calls will reflect a primary address change made on the server
Users should refrain from changing the primary address of an account or contact on the server until after calls are
synchronized. Failure to do so will result in newly synchronized contact and account calls recorded on the handheld device
reflecting the address change made on the server. (12-B6THFN)
Selecting the More Info view for an Activity will not show the selected record
The More Information view will default to the first Activity record instead of the selected activity record. The solution is to
remove OR ([Is Call]= “Y”) from the search specification of the Applet sIS HH Activity Entry Applet - CE” in Siebel Tools.
This condition is not required. (12-B4W559)
Accounts without Addresses will show a default address of two commas (“, )
Accounts without addresses added to them will show a value of two commas(, ,) as a default. (12-B4MAWU)
Indications for Details in Contact Calls will prepopulate with Other
Contact Call Details will automatically show an indication of Other. (12-B3G04U)
One of the default filters should be removed from the Action Business Object
There are two default filters on the Action Business Object (PDADef_All Calendar Activities and PDADef_Uncompleted
Activities). One should be removed before synchronization. (12-AJA9GK)

Error message for incorrect DSSURL parameter is ineffective
If the DSSURL parameter specified in the setup.ini file contains errors, users will receive the following error message when
attempting to synchronize: siebel-Message-Type 1. (12-9SYH53)
Find does not function correctly for Samples Dropped
The Find feature does not include Samples Dropped. Customers wishing to add Find for Samples Dropped may do so
through configuration with Siebel Tools. (12-9UBPAE)
Synchronization filters available for screens not in the User’s responsibility
When users log into the Handheld Synchronization client and choose select Filters, they may see names of screens in the
Filters drop-down list to which they have no access. (12-9H2HTM)
Missing Formulary Fields
The Accounts > Formulary view is currently missing the products, competitor flag, and status fields. Customers that wish to
add these fields may do so through configuration with Siebel Tools. (12-9L4VC6)
Comment Field Autopopulates with product description
Users may observe that the Comments field of the Sample Adjustments view auto-populates with the product description.
They may delete this information and add their own comments, as required. (12-9F9YCR)
Use of the ampersand (&)character in Business Component names causes synchronization and database errors
When customers configure the Siebel Handheld application, use of the ampersand (&)(Shift-7) character in the business
component name will cause errors during database import, the final phase of synchronization. Configurators should avoid
the use of this character in business component names. (12-AFV20N)
Calls of Professionals who are shared by multiple owners become Read-Only after Synchronization
Calls recorded for professionals who have more than one employee owner become read-only after synchronization. (12-
56JXYM)
Imposing required fields on the Calendar Business Component will cause difficulties with recurring appointments
Setting fields within the Calendar business component, as required through the use of Siebel Tools, may create
Synchronization errors if the user subsequently deletes one appointment in a series of recurring appointments. (12-8MP8V7)
Shared Notes May Be Deleted
It is possible for an individual who did not create a given shared note to delete it from the handheld client. (12-490GB1)

Siebel Signature Capture
Activating Predefaulting of DEA# and DEA Expiration fields for Contacts> Calls view
1. Make the following changes in Contact buscomp:
Set Link Specification property to true for DEA Expr and DEA# fields.
2. In the Pharma Professional Call – CE buscomp for the fields DEA Expiry Date and DEA# add the following pre default
values:
Field Pre Default Value
DEA# Parent: 'Contact.DEA#'
DEA Expiry Date Parent: 'Contact.DEA Expr'
(12-FIMWKJ)
Pharma Signature Administration Report and Pharma Sample Receipt Report
Signatures do not appear on the Sample Receipts Report under Pharma Signature Audit Administration View and the
Signature Audit Report under Pharma Sample Event Administration View. In order to make signatures appear, the following
work around needs to be applied. The procedure for Siebel Application Servers running Microsoft Windows 2000 is as
follows:
1. After the installation of the Siebel Server and the Reports Server, go to Start->Settings->Control Panel->System
2. Click on the Advanced tab
3. Click on the Environment Variables button
4. Under System Variables, highlight the CLASSPATH variable and click on Edit
5. Append;<root directory>\siebsrvr\REPORTS\ENU\InkToolsLib.jar to the end of the variable value
6. Click OK three times to exit the System Properties
7. Go to Start->Programs->Administrative Tools->Services
8. Stop the following services:
Actuate Administration Server 5
Actuate Persistent Object Server 5
Actuate ReportCast Server 5
Actuate Request Server 5
NobleNet Portmapper for TCP
9. Start all of the above five services
The procedure for Siebel Application Servers running Microsoft Windows NT is as follows:

1. After the installation of the Siebel Server and the Reports Server, go to Start->Settings->Control Panel->System
2. Click on the Environment tab
3. Click on the Environment Variables button
4. Under System Variables, highlight the CLASSPATH variable
5. Append;<root directory>\siebsrvr\REPORTS\ENU\InkToolsLib.jar to the end of the variable value
6. Click the Set button
7. Click OK to exit the System Properties
8. Go to Start->Settings->Control Panel->Services
9. Stop the following services:
Actuate Administration Server 5
Actuate Persistent Object Server 5
Actuate ReportCast Server 5
Actuate Request Server 5
NobleNet Portmapper for TCP
10. · Start all of the above five services
NOTE: This work around is only applicable for the English version of Siebel ePharma 7.0.4, running a
Siebel Application Server on Microsoft Windows operating systems, and Oracle database platforms.
Signatures do not appear on the Sample Receipts Report and the Signature Audit Report for the Spanish,
German, Italian, French, Swedish, Japanese, and Brazilian Portuguese versions. (12-B6O0ZV)
Samples
Created By field not automatically populated
Created By field is not automatically populated when creating Sample Adjustment. To remedy, modify the business
component in Siebel Tools:
1. In Siebel Tools object explorer, go to Business Component
2. Query for Business Component Name = “Pharma Sample Order And Adjustment”
3. Go to Business Component --> Field
4. Query for Field Name = “Owner Last Name”
5. Set Predefault Value = System: LastName
6. Compile object
(12-FJTEAB)

Enforcing synchronization before closing an Inventory Period

1. Add Pharma Sample Transactions as Business Component Object to Pharma Samples Business Object
2. a. Create a new Join in S_ACT_SIGN in Pharma Professional Call buscomp
Table : S_ACT_SIGN
Alias : S_ACT_SIGN
b. Join Spec
Name : Id
Destination Column : ACTIVITY_ID
Source Field : Id
3. Create a new field in Pharma Professional Call buscomp
Name : Signature Date
Join: S_ACT_SIGN
Column: CREATED
Force Active : Y
This is optional, If the customer wants Inventory Closure Validation and wants to set Acceptable Period to Complete sync
4. Create 2 user properties in Pharma Inventory Period buscomp
Name Value
Acceptable Period to Complete Synchronization 30
Inventory Closure Validation Y
Signature verification fails depending on the order Samples dropped are recorded

1. Go to the Pharma Call Sample Dropped - CE business component
2. Change the Sort Spec to Product Id, Lot Id
(12-FJMUIF)

Globalization
Localization
Clinical Trip Report has Truncated Characters
The Trip Report on the Site Management tab will have truncated characters in the footer. This report requires the
regeneration of the .rol and recompilation, which can be performed by following the steps below:
1. Start Siebel Tools and go to Reports Object
2. Query for LS_FOUPRE as the Access Base DB Name
3. Go to Tools -> Utilities -> Generate Actuate Report
4. Use generated LS_FOUPRE.rol to recompile report
5. Open c:\siebdev\rptsrc\deu\standard\LS_FOUPRE.rod
6. Shift F8 to recompile the report
7. Add c:\siebdev\rptsrc\deu\standard\LS_FOUPRE.rox to client and Reports Server installations (12-9YQ9XF)

7 0 4 Release Notes RevK

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

7 0 4 Release Notes RevK

Uploaded by

Copyright:

Available Formats

SIEBEL® eBUSINESS APPLICATIONS

SIEBEL eBUSINESS APPLICATIONS

Guidance for Siebel CRM........................................................................................................... 1-2

Guidance for the MidMarket Edition......................................................................................... 1-3

Release Package Contents........................................................................................................ 1-5

Chapter 2. Sample Database and Responsibilities

Siebel Financial Services Sample Database............................................................................ 2-9

Siebel Industry Solutions Sample Database ......................................................................... 2-19

Siebel Industry Solutions Predefined Responsibilities........................................................ 2-25

Siebel CRM Sample Database ................................................................................................. 2-30

Siebel Financial Services CRM Sample Database ................................................................ 2-35

Version 7.0.4+, Rev. K Release Notes iii

Siebel Financial Services CRM Predefined Responsibilities............................................... 2-38

Siebel MidMarket Edition Sample Database .......................................................................... 2-39

Siebel Financial Services, MidMarket Edition Sample Database ........................................ 2-44

Chapter 3. Product and Platform Availability Updates

Chapter 4. Base Application Known Anomalies

Siebel Analytics ........................................................................................................................ 4-39

Siebel Call Center ..................................................................................................................... 4-60

Siebel Campaigns..................................................................................................................... 4-64

Siebel Connector ...................................................................................................................... 4-66

Siebel Connector for Oracle Applications ............................................................................. 4-66

Siebel Connector for PeopleSoft ............................................................................................ 4-67

Siebel Connector for SAP/R3 .................................................................................................. 4-67

Siebel CTI .................................................................................................................................. 4-69

Siebel CTI Connect................................................................................................................... 4-70

Version 7.0.4+, Rev. K Release Notes iv

Siebel Data Quality Matching .................................................................................................. 4-71

Siebel Distance Learning......................................................................................................... 4-71

Siebel Dun & Bradstreet Integration Solution ....................................................................... 4-72

Siebel Employee Relationship Management ......................................................................... 4-74

Siebel Enterprise Selling Process .......................................................................................... 4-76

Siebel FirstLogic Connector.................................................................................................... 4-76

Siebel Forecasting.................................................................................................................... 4-76

Siebel Incentive Compensation .............................................................................................. 4-82

Siebel Marketing ....................................................................................................................... 4-83

Siebel Proposals & Presentations .......................................................................................... 4-93

Siebel Quotes............................................................................................................................ 4-95

Siebel Remote ........................................................................................................................... 4-99

Siebel Reports Server and Siebel eReports Server ............................................................ 4-102

Siebel Sales Base Application .............................................................................................. 4-106

Siebel Service Base Application ........................................................................................... 4-110

Siebel Sync.............................................................................................................................. 4-114

Siebel Time and Expense Reporting .................................................................................... 4-115

Siebel Tools............................................................................................................................. 4-115

Siebel Universal Queuing ...................................................................................................... 4-117

Siebel Wireless ....................................................................................................................... 4-119

Siebel Wireless Messaging.................................................................................................... 4-122

Siebel eAdvisor....................................................................................................................... 4-123

Siebel eAuction....................................................................................................................... 4-128

Siebel eBriefings .................................................................................................................... 4-129

Version 7.0.4+, Rev. K Release Notes v

Siebel Partner Relationship Mgmt (eChannel Partner Manager)....................................... 4-131

Siebel Partner Relationship Mgmt (eChannel Partner Portal) ........................................... 4-137

Siebel eConfigurator .............................................................................................................. 4-147

Siebel eContent Services....................................................................................................... 4-152

Siebel eEvents Manager ........................................................................................................ 4-152

Siebel eMail Response........................................................................................................... 4-153

Siebel eOrder .......................................................................................................................... 4-158

Siebel ePricer .......................................................................................................................... 4-159

Siebel eSales........................................................................................................................... 4-168

Siebel eTraining and Siebel eTraining Manager.................................................................. 4-176

Globalization ........................................................................................................................... 4-178

Release Package Contents (in this Introduction, Chapter 1)

Sample Databases and Responsibilities (Chapter 2)

Product and Platform Availability Updates (Chapter 3)

Known Anomalies (Chapters 4 through 10)

Anomalies under sections listed in Table 1-2 are not applicable

Anomalies annotated with Not applicable to Siebel CRM

Anomalies annotated with Not applicable to Siebel CRM or Base MME