• Save
Siebel Maintenance Release Guide
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Siebel Maintenance Release Guide

on

  • 1,746 views

 

Statistics

Views

Total Views
1,746
Views on SlideShare
1,746
Embed Views
0

Actions

Likes
1
Downloads
0
Comments
1

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • This is chandra, i have been into siebel CRm for 7 years, if you need Training or technical support or guidence on siebel interviews , please feel free to contact me @ +919035705781 or mail me @ chandarsekharr391@gmail.com
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Siebel Maintenance Release Guide Document Transcript

  • 1. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA November 2012
  • 2. Copyright © 2005, 2012 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error- free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo aretrademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates arenot responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
  • 3. Release Notes for the Siebel 8.1.1.x Fix Pack 7 What’s New in This Revision 9 Quick Fixes Included in Siebel 8.1.1.x Fix Packs 10 Enhancements and Updates in 8.1.1.x Fix Packs 32 Enhancements and Updates in Version 8.1.1.4 33 Enhancements and Updates in Version 8.1.1.3 34 Enhancements and Updates in Version 8.1.1.2 39 Enhancements and Updates in Version 8.1.1.1 40 Configuration Instructions for Enhancements and Updates 44 Instructions for ACR 358 45 Instructions for ACR 403 45 Instructions for ACR 422 50 Instructions for ACR 426 71 Instructions for ACR 437 94 Instructions for ACR 439 95 Instructions for ACR 439B 96 Instructions for ACR 450 100 Instructions for ACR 452 100 Instructions for ACR 456 102 Instructions for ACR 457 104 Instructions for ACR 463 108 Instructions for ACR 464 147 Instructions for ACR 467 156 Instructions for ACR 471 163 Instructions for ACR 474 and ACR 508 169 Instructions for ACR 475 248 Instructions for ACR 476 295 Contents
  • 4. Instructions for ACR 480 299 Instructions for ACR 488 310 Instructions for ACR 494 310 Instructions for ACR 499 311 Instructions for ACR 500 337 Instructions for ACR 502 364 Instructions for ACR 508 377 Instructions for ACR 526 382 Instructions for ACR 539 383 Instructions for ACR 543 408 Instructions for ACR 562 412 Instructions for ACR 574 457 Instructions for ACR 623 463 Instructions for ACR 626 463 Instructions for BI Publisher Enhancements 466 Siebel Fix Pack Installation Instructions 467 Siebel Fix Pack Installation Overview 467 Installing the Siebel Fix Pack on Microsoft Windows 471 Installing the Siebel Fix Pack on UNIX 476 Configuring Slipstream Patch Installation 480 Postinstallation Tasks for the Siebel Server 482 Postinstallation Tasks for the Web Server 482 Postinstallation Tasks for High Interactivity Clients 483 Postinstallation Tasks for Supporting Additional Languages 483 Uninstalling Siebel Fix Packs 485 Resolved Change Requests 487 . . . . . . . . . . . . . . Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack 488 Analytics 488 Call Center 488 Comm Media Energy 490 Connectors/EAI 490 Consumer Sector 492 Customer Order Management 495 Data Quality 500 General 502 Life Sciences 512 Loyalty 514 Marketing 516 Mobile Solutions 520 Partner Relationship Management 521 Public Sector 521
  • 5. Sales 522 Service 522 Siebel E-Commerce for Comms 524 Siebel Self Service Common 524 Universal Customer Master 524 User Interface 529 Web Service 531 Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack 532 Call Center 532 Comm Media Energy 536 Connectors/EAI 539 Consumer Sector 541 Customer Order Management 542 Data Quality 545 Financial Services 545 General 545 iHelp 560 Life Sciences 561 Loyalty 566 Marketing 567 Mobile Solutions 569 Partner Relationship Management 571 Public Sector 571 Sales 571 Service 572 Siebel Email Response 573 Siebel Self Service eCommon 573 User Interface 573 Web Service 576 Resolved Change Requests in the Siebel 8.1.1.2 Fix Pack 577 Call Center 577 Comm Media Energy 578 Connectors/EAI 579 Consumer Sector 580 Customer Order Management 580 Data Quality 582 General 582 iHelp 593 Life Sciences 593 Marketing 594 Mobile Solutions 595 Sales 597
  • 6. Service 597 Siebel Email Response 598 Siebel Self-Service Common 598 Travel & Transportation 598 User Interface 599 Web Service 601 Resolved Change Requests in the Siebel 8.1.1.1 Fix Pack 602 Call Center 602 Comm Media Energy 604 Connectors / EAI 605 Consumer Sector 606 Customer Order Management 619 Data Quality 624 Financial Services 625 General 626 Life Sciences 652 Loyalty 654 Marketing 658 Mobile Solutions 662 Partner Relationship Management 662 Public Sector 664 Sales 664 Service 665 Siebel E-Commerce 666 Siebel E-Commerce for Comms 669 Siebel Email Response 679 Siebel E-Support 683 Siebel Self Service Common 684 Travel & Transportation 686 Universal Customer Master 692 User Interface 695 Web Service 711 Oracle Welcomes Your Comments 777
  • 7. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 7 Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA November 2012 NOTE: This guide documents the Quick Fixes, enhancements, instructions for enhancements, and bugs fixed in the Siebel 8.1.1.1 through Siebel 8.1.1.4 Fix Packs. As of the Siebel 8.1.1.5 Fix Pack, Fix Pack documentation is provided in a release-specific Siebel Maintenance Release Guide. For information about what was provided in the Siebel 8.1.1.5 and Siebel 8.1.1.6 Fix Packs, see Siebel Maintenance Release Guide, Version 8.1.1.5 and Siebel Maintenance Release Guide, Version 8.1.1.6. To access these guides, from within My Oracle Support, navigate to the Knowledge tab, and search for Article ID 880452.1. This guide includes the following topics: ■ Release Notes for the Siebel 8.1.1.x Fix Pack on page 7 ■ What’s New in This Revision on page 9 ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs on page 10 ■ Enhancements and Updates in 8.1.1.x Fix Packs on page 32 ■ Configuration Instructions for Enhancements and Updates on page 44 ■ Siebel Fix Pack Installation Instructions on page 467 ■ Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack on page 488 ■ Resolved Change Requests in the Siebel 8.1.1.3 Fix Pack on page 532 ■ Resolved Change Requests in the Siebel 8.1.1.2 Fix Pack on page 577 ■ Resolved Change Requests in the Siebel 8.1.1.1 Fix Pack on page 602 ■ Oracle Welcomes Your Comments on page 777 NOTE: If you are installing ACR474, please note that there are known issues, which are documented in this section. Also, for instructions about how to implement and configure ACR 474, see Siebel Maintenance Release Guide, Version 8.1.1.x on My Oracle Support. To access this guide, from within My Oracle Support, navigate to the Knowledge tab and search for Article ID 880452.1. Release Notes for the Siebel 8.1.1.x Fix Pack The following sections describes known issues with the Siebel 8.1.1.x Fix Packs, as well as any applicable workaround information.
  • 8. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Release Notes for the Siebel 8.1.1.x Fix Pack 8 No Records Display in Sample Compliance > Employee Based Tracking > My Team's Employee View Category: Siebel Life Sciences Subcategory: Samples - Compliance Product Version: Siebel 8.1.1.3 Bug ID: 12371899 All reporting employees should be displayed within Sample Compliance > Employee Based Tracking > My Team's Employee view, but no records are displayed. Use the following workaround to address this issue: 1 Log into Siebel Tools, and query for the LS Pharma Compliance Employee business component. 2 Select the Sales Rep business component view mode. 3 Change the Visibility MVLink property from Sales Team to Position 4 Change the Visibility MVField property from Sales Team to Position. 5 Compile the object into the SRF and restart the server. LS Pharma Data Migration Service Returns Error Category: Siebel Life Sciences Subcategory: Samples Product Version: Siebel 8.1.1.x Bug ID: 10556780 When users create a server job using the Worfklow Process Manager component to run the LS Pharma Data Migration for Life Sciences Pharma version 8.1.1, the process terminates with an error. This issue applies to customers who are upgrading from Siebel Life Sciences customers who are upgrading to Siebel 8.1.1.x from Siebel 8.0 or prior versions. For workaround information, from within My Oracle Support, navigate to the Knowledge tab and search for Article ID 1310515.1.
  • 9. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ What’s New in This Revision Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 9 What’s New in This Revision Table 1 describes the changes in this version of the documentation. How To Use This Guide This document, Siebel Maintenance Release Guide, Version 8.1.1.x, lists the enhancements and fixes provided in the Siebel 8.1.1.1 through Siebel 8.1.1.4 Fix Packs. This guide also provides information, instructions, and guidelines for installing Siebel Business Applications Siebel Fix Pack 8.1.1.x releases on top of version 8.1.1 or a prior 8.1.1.x release. Use this Siebel Maintenance Release Guide in conjunction with Siebel Bookshelf documents, particularly the Siebel Installation Guide for the operating system you are using. NOTE: Verify the availability and applicability of all Fix Pack or Quick Fix releases with Oracle Global Customer Support before you install. The information contained herein supersedes, for warranty and other purposes, the contents of all other documentation that may accompany this product, including the following: ■ My Oracle Support (https://support.oracle.com) ■ Siebel System Requirements and Supported Platforms on Oracle Technology Network (http://download.oracle.com/docs/cd/E11886_01/srsphomepage.html) This Siebel Maintenance Release Guide contains information about the following: ■ How to install the maintenance (Fix Pack) release ■ Product configuration issues and workarounds for your application NOTE: There may be references to functionality, products, platforms, and language support in this document that are not available as part of the products that your organization has licensed. Consult Oracle Global Customer Support on My Oracle Support with questions regarding the applicability of Siebel Maintenance Release Guide items to your deployment. Additional Documentation Oracle reserves the right to modify the documentation for Siebel Business Applications at any time. Table 1. What’s New in Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA Topic Description “Instructions for ACR 474 and ACR 508” on page 169 Revised this section. “Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack” on page 488 Added FR 12-1ZM2V2V and configuration instructions for it. “Instructions for ACR 574” on page 457 Added tips under the Installing ACR 574 heading.
  • 10. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs 10 For related Siebel documentation, see the following: ■ My Oracle Support (https://support.oracle.com) (requires valid customer account) ■ Siebel System Requirements and Supported Platforms on Oracle Technology Network (http:// download.oracle.com/docs/cd/E11886_01/srsphomepage.html) ■ Siebel Bookshelf for Oracle’s Siebel Business Applications, Version 8.1 (http://www.oracle.com/ technology/documentation/siebel.html) on Oracle Technology Network (OTN) Quick Fixes Included in Siebel 8.1.1.x Fix Packs Siebel Quick Fix releases are developed to address immediate critical issues for specific customers, and can be installed on top of Fix Packs. Quick Fixes address a small number of defects, and the fixes are typically rolled into the next available Fix Pack for wider distribution to the Siebel Business Applications customer base. Testing for Quick Fixes is focused and is usually limited toverifying that the fix works on the specific platforms that the affected customer is running. NOTE: If you have installed a Quick Fix for any Siebel 8.1.1 or 8.1.1.x release prior to the latest 8.1.1.x release covered by this document, review Table 2 on page 11 to make sure that your Quick Fix number is listed.
  • 11. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 11 CAUTION: If you do not see your Quick Fix number in the table, do not install the latest 8.1.1.x Fix Pack. This list is updated as new Fix Packs are released. Wait until your Quick Fix appears in the table before applying the latest Fix Pack. If you have questions, contact Global Customer Support or your Oracle representative. Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack 12-1Q35A8A 12-1Q450JI [21107] 21107 8.1.1.4 12-1QVMO57 12-1QVMO5T [21112] 21112 8.1.1.4 12-1TK3VGV 12-1TK3VI7 8.1.1 [21112] QF0028 8.1.1.4 12-1TK4OZF 12-1TK4P0Q 8.1.1 [21112] QF0028 8.1.1.4 12-1TK9B70 12-1TK92RX 8.1.1 [21112] QF0028 8.1.1.4 12-1TKA4KE 12-1TKA4MZ 8.1.1 [21112] QF0028 8.1.1.4 12-1TPS15R 12-1TPS17B 8.1.1 [21112] QF0028 8.1.1.4 12-1TPS1BB 12-1TPS1CY 8.1.1 [21112] QF0028 8.1.1.4 12-1TPS1E1 12-1TPS1FI 8.1.1 [21112] QF0028 8.1.1.4 12-1TWTQPT 12-1TWTQR5 8.1.1 [21112] QF0028 8.1.1.4 12-1VH3RYD 12-1VI2I3J 8.1.1 [21112] QF0072 8.1.1.4 12-1VM6N5D 12-1VR58XF 8.1.1 [21112] QF0082 8.1.1.4 12-1WXWUIF 12-1WXWUIX 8.1.1 [21112] QF00AN 8.1.1.4 12-1QVMO57 12-1VHKVBD 8.1.1 [21112] QF00AO 8.1.1.4 12-1XZBSUD 12-1Y8IY97 8.1.1 [21112] QF00AV 8.1.1.4 12-1XO6UN9 12-1XOO9FM 8.1.1 [21112] QF00AW 8.1.1.4 12-1XUY3ZF 12-1XVFKIP 8.1.1 [21112] QF00AW 8.1.1.4 12-1VI06I9 12-1YFC5GX 8.1.1 [21112] QF00AY 8.1.1.4 12-1IBE8WR 12-1YM4XDT 8.1.1 [21112] QF00BD 8.1.1.4 12-1WLTVBV 12-1YMLXLT 8.1.1 [21112] QF00BG 8.1.1.4 12-1XF0G9H 12-1XMQKEZ 8.1.1 [21112] QF00BK 8.1.1.4 12-1YOMS98 12-1YOMSBW 8.1.1 [21112] QF00BO 8.1.1.4 12-1PZ4R7R 12-1XTIC0H 8.1.1 [21112] QF00BP 8.1.1.4 12-1YCG2PL 12-1Z6WBPB 8.1.1 [21112] QF00BU 8.1.1.4 12-1TGO7DJ 12-1U0BPJM 8.1.1 [21112] QF0028 8.1.1.4
  • 12. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs 12 12-1TJMH71 12-1TJMH8L 8.1.1 [21112] QF0028 8.1.1.4 12-1TK3VIM 12-1TK3VJY 8.1.1 [21112] QF0028 8.1.1.4 12-1TK3VKD 12-1TK4OX9 8.1.1 [21112] QF0028 8.1.1.4 12-1TK4OXO 12-1TK4OZ0 8.1.1 [21112] QF0028 8.1.1.4 12-1TK962G 12-1TK964K 8.1.1 [21112] QF0028 8.1.1.4 12-1TK9B1B 12-1TK92TB 8.1.1 [21112] QF0028 8.1.1.4 12-1TK9ENW 12-1TK9EP6 8.1.1 [21112] QF0028 8.1.1.4 12-1TK9ZE3 12-1TK9ZFM 8.1.1 [21112] QF0028 8.1.1.4 12-1TKA445 12-1TKA45M 8.1.1 [21112] QF0028 8.1.1.4 12-1TKA4GE 12-1TKA4J7 8.1.1 [21112] QF0028 8.1.1.4 12-1TKA4NA 12-1TK9ZGP 8.1.1 [21112] QF0028 8.1.1.4 12-1TKA9BK 12-1TKA9D4 8.1.1 [21112] QF0028 8.1.1.4 12-1TPS192 12-1TPS1B0 8.1.1 [21112] QF0028 8.1.1.4 12-1TPS1HM 12-1TKA9AH 8.1.1 [21112] QF0028 8.1.1.4 12-1TUW8FW 12-1TUW8HC 8.1.1 [21112] QF0028 8.1.1.4 12-1TUW8IF 12-1TUW8JX 8.1.1 [21112] QF0028 8.1.1.4 12-1TUWQ23 12-1TUW8ET 8.1.1 [21112] QF0028 8.1.1.4 12-1TWTQRK 12-1TWTQSU 8.1.1 [21112] QF0028 8.1.1.4 12-1U0AEGZ 12-1U0AEIY 8.1.1 [21112] QF0028 8.1.1.4 12-1U0AR67 12-1U0AR7L 8.1.1 [21112] QF0028 8.1.1.4 12-1U5RB3V 12-1U5RB5J 8.1.1 [21112] QF0041 8.1.1.4 12-1VH3RP7 12-1VH3X9H 8.1.1 [21112] QF0072 8.1.1.4 12-1VM7S6L 12-1VM7S7C 8.1.1 [21112] QF0075 8.1.1.4 12-1VM6MO5 12-1VM6040 8.1.1 [21112] QF00AH 8.1.1.4 12-1XHDRIJ 12-1XHX6IZ 8.1.1 [21112] QF00AI 8.1.1.4 12-1XIVKJJ 12-1XIVKK8 8.1.1 [21112] QF00AJ 8.1.1.4 12-1XLAL2N 12-1XP58OF 8.1.1 [21112] QF00AJ 8.1.1.4 12-1XHF9F1 12-1XKSPM0 8.1.1 [21112] QF00AM 8.1.1.4 12-1XP5AVL 12-1XQM2DJ 8.1.1 [21112] QF00AQ 8.1.1.4 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 13. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 13 12-1XCM26P 12-1XCM27D 8.1.1 [21112] QF00AR 8.1.1.4 12-1WF6ZG1 12-1WR5BMI 8.1.1 [21112] QF00AS 8.1.1.4 12-1Y6LBZN 12-1Y6LC0G 8.1.1 [21112] QF00AT 8.1.1.4 12-1VMCEBF 12-1VNJREX 8.1.1 [21112] QF00AW 8.1.1.4 12-1XT16PO 12-1XT16QR 8.1.1 [21112] QF00AW 8.1.1.4 12-1YIQQID 12-1YIQKSC 8.1.1 [21112] QF00AZ 8.1.1.4 12-1XWIYRL 12-1YCXRIV 8.1.1 [21112] QF00BA 8.1.1.4 12-1VDPBPF 12-1Y54A1B 8.1.1 [21112] QF00BF 8.1.1.4 12-1Z4YJPX 12-1Z4YJQJ 8.1.1 [21112] QF00BI 8.1.1.4 12-1XWEWDL 12-1XYCRU9 8.1.1 [21112] QF00BK 8.1.1.4 12-1YKOYUX 12-1YM4UWN 8.1.1 [21112] QF00BK 8.1.1.4 12-1XF0GC9 12-1XL4MPA 8.1.1 [21112] QF00BL 8.1.1.4 12-1WUJE2X 12-1WUJE3Y 8.1.1 [21112] QF00BR 8.1.1.4 12-1ZPH4ZU 12-1ZRVWP8 8.1.1 [21112] QF00BU 8.1.1.4 12-1YOKK4N 12-1Z7V33V 8.1.1 PDA [21112_10] 8.1.1 PDA [21112_10] 8.1.1.4 12-1YOKGG5 12-1Z04TF7 8.1.1 PDA [21112_11] 8.1.1 PDA [21112_11] 8.1.1.4 12-1YOK96H 12-1YOK97J 8.1.1 PDA [21112_8] 8.1.1 PDA [21112_8] 8.1.1.4 12-1YOKK66 12-1YOKK9R 8.1.1 PDA [21112_8] 8.1.1 PDA [21112_8] 8.1.1.4 12-1YOMS7P 12-1YOMS8H 8.1.1 PDA [21112_9] 8.1.1 PDA [21112_9] 8.1.1.4 12-1JFQEZ6 12-1Z9RYA5 8.1.1 PDA [21112_9] 8.1.1 PDA [21112_9] 8.1.1.4 12-1YGT6Q9 12-1YOMSAP 8.1.1 PDA [21112_9] 8.1.1 PDA [21112_9] 8.1.1.4 12-1Z3IMD9 12-1Z3I799 8.1.1 PDA [21112_9] 8.1.1 PDA [21112_9] 8.1.1.4 12-1TK4UBL 12-1XS216R 8.1.1.1 [21211] QF0191 8.1.1.4 12-1S1Y205 12-1X6RYEB 8.1.1.1 [21211] QF0192 8.1.1.4 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 14. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs 14 12-1VH3RP7 12-1Y5LUYL 8.1.1.1 [21211] QF01AD 8.1.1.4 12-1XC7KQR 12-1YJP6YH 8.1.1.1 [21211] QF01AH 8.1.1.4 12-1PFQSZV 12-1YJPUAJ 8.1.1.1 [21211] QF01AN 8.1.1.4 12-1Y9HK6T 12-1YIQPLL 8.1.1.1 [21211] QF01AS 8.1.1.4 12-1YIQP2P 12-1YIQP3X 8.1.1.1 [21211] QF01AY 8.1.1.4 12-1Z1KQM1 12-1ZFBVG7 8.1.1.1 [21211] QF01BF 8.1.1.4 12-1YNLB8N 12-1YO2D6J 8.1.1.1 [21211] QF01BH 8.1.1.4 12-OVT1LK 12-1XJDH9J 8.1.1.1 [21211] QF01BK 8.1.1.4 12-1BDKMON 12-1YOLF2T 8.1.1.1 [21211] QF1109 8.1.1.4 12-1VNJDR2 12-1VNJDUK 8.1.1.1 [21211] QF3102 8.1.1.4 12-1VR4QM7 12-1VR4QMW 8.1.1.1 [21211] QF3103 8.1.1.4 12-1Z6VRAB 12-1Z4YK31 8.1.1.1 [21211] QF7106 8.1.1.4 12-1VM6N5D 12-1VM90VR 8.1.1.1 [21211] QF0131 8.1.1.4 12-1VM7S6L 12-1VR2KHF 8.1.1.1 [21211] QF0132 8.1.1.4 12-1WEU3RJ 12-1WFJXIH 8.1.1.1 [21211] QF0179 8.1.1.4 12-1X5627A 12-1X5628Q 8.1.1.1 [21211] QF0180 8.1.1.4 12-1U5RB3V 12-1U5RB56 8.1.1.1 [21211] QF0185 8.1.1.4 12-1U0C8HX 12-1XQLOAP 8.1.1.1 [21211] QF0187 8.1.1.4 12-1WF6IYP 12-1WF6SRH 8.1.1.1 [21211] QF0194 8.1.1.4 12-1Y0AHAJ 12-1Y0B0CN 8.1.1.1 [21211] QF0196 8.1.1.4 12-1XCM26P 12-1Y8ID43 8.1.1.1 [21211] QF0197 8.1.1.4 12-1WXWV2P 12-1XZBJGV 8.1.1.1 [21211] QF0198 8.1.1.4 12-1Y63UOX 12-1Y63KCJ 8.1.1.1 [21211] QF0199 8.1.1.4 12-1XF0FUR 12-1Y37HAT 8.1.1.1 [21211] QF01AA 8.1.1.4 12-1KBLS9L 12-1XHF8MP 8.1.1.1 [21211] QF01AC 8.1.1.4 12-1V418JR 12-1XSKD01 8.1.1.1 [21211] QF01AD 8.1.1.4 12-1UH8JVF 12-1YFCJ1B 8.1.1.1 [21211] QF01AE 8.1.1.4 12-1XLALJV 12-1XPMVCR 8.1.1.1 [21211] QF01AG 8.1.1.4 12-1VE77T9 12-1YCX4WP 8.1.1.1 [21211] QF01AI 8.1.1.4 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 15. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 15 12-1Y3OYE1 12-1Y5MADB 8.1.1.1 [21211] QF01AM 8.1.1.4 12-1BV2Y2P 12-1Y6LKPJ 8.1.1.1 [21211] QF01AO 8.1.1.4 12-1WLUTXP 12-1XHF5O1 8.1.1.1 [21211] QF01AP 8.1.1.4 12-1J1ZOUE 12-1YDESND 8.1.1.1 [21211] QF01AQ 8.1.1.4 12-1TLCZVH 12-1Z04WCR 8.1.1.1 [21211] QF01AV 8.1.1.4 12-1YQ37AZ 12-1YOMUG9 8.1.1.1 [21211] QF01AX 8.1.1.4 12-1W6DOUA 12-1WXF8N2 8.1.1.1 [21211] QF01BA 8.1.1.4 12-1XQ4S1X 12-1Z3IAW7 8.1.1.1 [21211] QF01BB 8.1.1.4 12-1XC7L43 12-1XC7L4O 8.1.1.1 [21211] QF01BC 8.1.1.4 12-1YOKFU7 12-1YOKNFT 8.1.1.1 [21211] QF01BC 8.1.1.4 12-1XTIR2L 12-1Z04WDL 8.1.1.1 [21211] QF01BF 8.1.1.4 12-1Y28AMJ 12-1Z04UJ7 8.1.1.1 [21211] QF01BF 8.1.1.4 12-1YOLRSL 12-1YOM3YD 8.1.1.1 [21211] QF01BG 8.1.1.4 12-1YOLS7V 12-1YOMC6N 8.1.1.1 [21211] QF01BI 8.1.1.4 12-1WXWUIF 12-1Y90L0B 8.1.1.1 [21211] QF01BO 8.1.1.4 12-1XIVYP9 12-1ZSUWJJ 8.1.1.1 [21211] QF01BU 8.1.1.4 12-1WF6ZG1 12-206EOPP 8.1.1.1 [21211] QF01CE 8.1.1.4 12-1XM98B7 12-1XQ4PLV 8.1.1.1 [21211] QF1107 8.1.1.4 12-1XTBN8V 12-1XTBN9M 8.1.1.1 [21211] QF1108 8.1.1.4 12-1TK672L 12-1VM54KD 8.1.1.1 [21211] QF3101 8.1.1.4 12-1VH3RP7 12-1VM7VPD 8.1.1.1 [21211] QF3101 8.1.1.4 12-1VH3RYD 12-1VM7VQC 8.1.1.1 [21211] QF3101 8.1.1.4 12-1VNJ8G2 12-1VNJ8HJ 8.1.1.1 [21211] QF3101 8.1.1.4 12-1VNJ8DR 12-1VNJ8F6 8.1.1.1 [21211] QF3102 8.1.1.4 12-1VNJC3T 12-1VNJC4I 8.1.1.1 [21211] QF3102 8.1.1.4 12-1VNJKCG 12-1VNIZ0Z 8.1.1.1 [21211] QF3103 8.1.1.4 12-1VNKG5Z 12-1VNKG7I 8.1.1.1 [21211] QF3103 8.1.1.4 12-1VR1NO3 12-1VR1NPM 8.1.1.1 [21211] QF3103 8.1.1.4 12-1VR2BBP 12-1VR38XI 8.1.1.1 [21211] QF3103 8.1.1.4 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 16. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs 16 12-1VR3RJX 12-1VR3RLH 8.1.1.1 [21211] QF3103 8.1.1.4 12-1VR3SGC 12-1VR3SIF 8.1.1.1 [21211] QF3103 8.1.1.4 12-1VR4QK5 12-1VR4QL4 8.1.1.1 [21211] QF3103 8.1.1.4 12-1VR4VCC 12-1VR4VE1 8.1.1.1 [21211] QF3103 8.1.1.4 12-1VR4VUQ 12-1VR4VW7 8.1.1.1 [21211] QF3103 8.1.1.4 12-1X56AT7 12-1X660OB 8.1.1.1 [21211] QF3104 8.1.1.4 12-1Z6ER6J 12-1Z7UTG8 8.1.1.1 [21211] QF3106 8.1.1.4 12-1XWEYTD 12-1XWEYU7 8.1.1.1 [21211] QF4103 8.1.1.4 12-1WUJGPN 12-1YCFW5J 8.1.1.1 [21211] QF5105 8.1.1.4 12-1Q7NVMV 12-1XJD1PB 8.1.1.1 [21211] QF7104 8.1.1.4 12-1V4JH1X 12-1YL5W2L 8.1.1.1 [21211] QF7105 8.1.1.4 12-1XTIRJJ 12-1XWEU4W 8.1.1.1 [21211] QF7106 8.1.1.4 12-1S1Y205 12-1YFTTGZ 8.1.1.2 [ 21215] QF0264 8.1.1.4 12-1VR32TN 12-1VR32VC 8.1.1.2 [21215] QF0201 8.1.1.4 12-1IKIU3B 12-1XLRN7L 8.1.1.2 [21215] QF0229 8.1.1.4 12-1XIVLVL 12-1XJD2N6 8.1.1.2 [21215] QF0236 8.1.1.4 12-1WXWV2P 12-1X3PWGR 8.1.1.2 [21215] QF0237 8.1.1.4 12-1V418VF 12-1XF0ZKU 8.1.1.2 [21215] QF0242 8.1.1.4 12-1X65YA7 12-1XF0ZCF 8.1.1.2 [21215] QF0243 8.1.1.4 12-1XIVYP9 12-1XKTAIF 8.1.1.2 [21215] QF0244 8.1.1.4 12-1W7XG6V 12-1WA3IG1 8.1.1.2 [21215] QF0245 8.1.1.4 12-1XC4GYV 12-1XC4UGA 8.1.1.2 [21215] QF0247 8.1.1.4 12-1R4A19T 12-1XVG8MP 8.1.1.2 [21215] QF0248 8.1.1.4 12-1VNK8MB 12-1XF0ZM4 8.1.1.2 [21215] QF0249 8.1.1.4 12-1XZBSUD 12-1XZXNT7 8.1.1.2 [21215] QF0250 8.1.1.4 12-1XC7KQR 12-1XFILLH 8.1.1.2 [21215] QF0252 8.1.1.4 12-1Y3OXVF 12-1Y54EHL 8.1.1.2 [21215] QF0252 8.1.1.4 12-1WQ5PD9 12-1Y9R4SN 8.1.1.2 [21215] QF0256 8.1.1.4 12-1HE1XTL 12-1XIW0S1 8.1.1.2 [21215] QF0258 8.1.1.4 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 17. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 17 12-1VR26EP 12-1YK6TPN 8.1.1.2 [21215] QF0259 8.1.1.4 12-1XM987B 12-1XQ4AG0 8.1.1.2 [21215] QF0261 8.1.1.4 12-1Y3OY73 12-1Y5M9YK 8.1.1.2 [21215] QF0263 8.1.1.4 12-1QPSYL1 12-1XVG5E1 8.1.1.2 [21215] QF0266 8.1.1.4 12-1X3PQB1 12-1X3P5C7 8.1.1.2 [21215] QF0268 8.1.1.4 12-1XSJG29 12-1XSYA2D 8.1.1.2 [21215] QF0269 8.1.1.4 12-1YCXQYB 12-1YDWOIW 8.1.1.2 [21215] QF0270 8.1.1.4 12-1YNKWFD 12-1YO29DX 8.1.1.2 [21215] QF0272 8.1.1.4 12-1VM7S6L 12-1YNL9FN 8.1.1.2 [21215] QF0274 8.1.1.4 12-1YOLRNV 12-1YOLGB9 8.1.1.2 [21215] QF0275 8.1.1.4 12-1XF0GC9 12-1YN3T0B 8.1.1.2 [21215] QF0276 8.1.1.4 12-1YOMS98 12-1YSM0JM 8.1.1.2 [21215] QF0277 8.1.1.4 12-1XIVLOD 12-1XJDJVF 8.1.1.2 [21215] QF0279 8.1.1.4 12-1XM986H 12-1XQ4AF7 8.1.1.2 [21215] QF0280 8.1.1.4 12-1YM4GZ9 12-1YM4H07 8.1.1.2 [21215] QF0281 8.1.1.4 12-1YOMJWJ 12-1YSN3X1 8.1.1.2 [21215] QF0281 8.1.1.4 12-1YOMN57 12-1YSN3WN 8.1.1.2 [21215] QF0281 8.1.1.4 12-1YOMN72 12-1YSN3W9 8.1.1.2 [21215] QF0281 8.1.1.4 12-1YQGG4M 12-1YSN3VH 8.1.1.2 [21215] QF0281 8.1.1.4 12-1YQGG7U 12-1YOMPJT 8.1.1.2 [21215] QF0281 8.1.1.4 12-1YQGG9F 12-1YOMPJF 8.1.1.2 [21215] QF0281 8.1.1.4 12-1YQGGD5 12-1YOMPIN 8.1.1.2 [21215] QF0281 8.1.1.4 12-1YQGGEQ 12-1YOMPI9 8.1.1.2 [21215] QF0281 8.1.1.4 12-1YQZ267 12-1YQZ29Q 8.1.1.2 [21215] QF0281 8.1.1.4 12-1SW8L6P 12-1Y2PUMT 8.1.1.2 [21215] QF0282 8.1.1.4 12-1Y6LBZN 12-1YR2YWB 8.1.1.2 [21215] QF0282 8.1.1.4 12-1Y28AMJ 12-1Y28AN4 8.1.1.2 [21215] QF0283 8.1.1.4 12-1YAH50J 12-1YBWTK1 8.1.1.2 [21215] QF0283 8.1.1.4 12-1YAH4TL 12-1YBWHO9 8.1.1.2 [21215] QF0284 8.1.1.4 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 18. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs 18 12-1VNJ7BV 12-1VNJBI3 8.1.1.2 [21215] QF0285 8.1.1.4 12-1XF0FX9 12-1YUNVWZ 8.1.1.2 [21215] QF0286 8.1.1.4 12-1YO2RKX 12-1YO2RLM 8.1.1.2 [21215] QF0287 8.1.1.4 12-1Z1KQY9 12-1Z3IALD 8.1.1.2 [21215] QF0288 8.1.1.4 12-1NWCZMB 12-1Y54DN1 8.1.1.2 [21215] QF0289 8.1.1.4 12-1YAH55T 12-1YCFIBF 8.1.1.2 [21215] QF0290 8.1.1.4 12-1VJZTJ7 12-1YOKQLH 8.1.1.2 [21215] QF0294 8.1.1.4 12-1QBCC09 12-1Z312WH 8.1.1.2 [21215] QF0296 8.1.1.4 12-1YOLS71 12-1YOMPKH 8.1.1.2 [21215] QF0298 8.1.1.4 12-1YZND55 12-1Z04EEK 8.1.1.2 [21215] QF0299 8.1.1.4 12-1Y3OXW9 12-1Y90EUX 8.1.1.2 [21215] QF02AB 8.1.1.4 12-1V9U49H 12-1Z0MDNB 8.1.1.2 [21215] QF02AC 8.1.1.4 12-1XRKKWD 12-1YAH25H 8.1.1.2 [21215] QF02AI 8.1.1.4 12-1YNLBB5 12-1Z7DTPM 8.1.1.2 [21215] QF02AI 8.1.1.4 12-1Z1KQM1 12-1ZF3CXL 8.1.1.2 [21215] QF02AI 8.1.1.4 12-1Z3IMBL 12-1ZOJCQH 8.1.1.2 [21215] QF02AI 8.1.1.4 12-1V418JR 12-1VOFQ3P 8.1.1.2 [21215] QF02AJ 8.1.1.4 12-1U0C8HX 12-1XM9N8Z 8.1.1.2 [21215] QF02AM 8.1.1.4 12-1TLCZVH 12-1Z9S46Z 8.1.1.2 [21215] QF02AN 8.1.1.4 12-1U5RB3V 12-203152F 8.1.1.2 [21215] QF02AN 8.1.1.4 12-1XIVMBZ 12-1XQ4T5X 8.1.1.2 [21215] QF02AQ 8.1.1.4 12-1Y9HK6T 12-1Y9HK8A 8.1.1.2 [21215] QF02AQ 8.1.1.4 12-1XBND23 12-1ZRW32R 8.1.1.2 [21215] QF02AR 8.1.1.4 12-1VMCEBF 12-1ZUS4MB 8.1.1.2 [21215] QF02AU 8.1.1.4 12-1SEPT2B 12-20F4VE5 8.1.1.2 [21215] QF02BK 8.1.1.4 12-1ZZMR15 12-202252X 8.1.1.2 [21215] QF02BL 8.1.1.4 12-1YGT6Q9 12-1YGT6R2 8.1.1.2 WM5 [21215_5] 8.1.1.2 WM 5 [21215_5] 8.1.1.4 12-1YOMS7P 12-1YV5IMZ 8.1.1.2 WM5 [21215_5] 8.1.1.2 WM 5 [21215_5] 8.1.1.4 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 19. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 19 12-1Z6VW9H 12-1Z6VWA6 8.1.1.2 WM5 [21215_6] 8.1.1.2 WM 5 [21215_6] 8.1.1.4 12-1JFQEZ6 12-1Y28CXL 8.1.1.2 WM5 [21215_5] 8.1.1.2 WM 5 [21215_5] 8.1.1.4 12-1Y2PC95 12-1YCFJSR 8.1.1.3 [21219] QF0302 8.1.1.4 12-1VMCEBF 12-1XYUAXZ 8.1.1.3 [21219] QF0303 8.1.1.4 12-1WTJXWZ 12-1X97V94 8.1.1.3 [21219] QF0303 8.1.1.4 12-1XF0G9H 12-1XMQKEJ 8.1.1.3 [21219] QF0303 8.1.1.4 12-1XOOC39 12-1XQ4AWP 8.1.1.3 [21219] QF0303 8.1.1.4 12-1HCLBH7 12-1XYTSLP 8.1.1.3 [21219] QF0304 8.1.1.4 12-1U0C8HX 12-1Z0MB07 8.1.1.3 [21219] QF0305 8.1.1.4 12-1QTP7PD 12-1Y2PBV7 8.1.1.3 [21219] QF0306 8.1.1.4 12-1Y0AZPB 12-1Y0AZPY 8.1.1.3 [21219] QF0307 8.1.1.4 12-1YOKG0B 12-1YOKNO0 8.1.1.3 [21219] QF0310 8.1.1.4 12-1VM7S6L 12-1Z4YJJT 8.1.1.3 [21219] QF0311 8.1.1.4 12-1Z1KQM1 12-1Z04V45 8.1.1.3 [21219] QF0312 8.1.1.4 12-1YFU2BX 12-1YHAEXR 8.1.1.3 [21219] QF0313 8.1.1.4 12-1YQ37K5 12-1YVB42D 8.1.1.3 [21219] QF0313 8.1.1.4 12-1Z6VRLF 12-1Z6WCOG 8.1.1.3 [21219] QF0314 8.1.1.4 12-1Z3IMBL 12-1Z6PEQ9 8.1.1.3 [21219] QF0315 8.1.1.4 12-1XTIRJJ 12-1ZF3T8Z 8.1.1.3 [21219] QF0316 8.1.1.4 12-1Q7NVMV 12-1ZFBE8H 8.1.1.3 [21219] QF0317 8.1.1.4 12-1IKIU3B 12-1ZH9OLB 8.1.1.3 [21219] QF0318 8.1.1.4 12-1X65YA7 12-1ZFCYUM 8.1.1.3 [21219] QF0319 8.1.1.4 12-1ZFBCAH 12-1ZFBJ5Z 8.1.1.3 [21219] QF0320 8.1.1.4 12-1V4JH1X 12-1ZF3AMP 8.1.1.3 [21219] QF0321 8.1.1.4 12-1W6DOUA 12-1ZD5YHL 8.1.1.3 [21219] QF0323 8.1.1.4 12-1Y8J0H7 12-1ZF38WH 8.1.1.3 [21219] QF0326 8.1.1.4 12-1YCFMMF 12-1YFCA4P 8.1.1.3 [21219] QF0328 8.1.1.4 12-1PZ4R7R 12-1ZURZZ3 8.1.1.3 [21219] QF0334 8.1.1.4 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 20. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs 20 12-1XBND23 12-1ZY61E5 8.1.1.3 [21219] QF0336 8.1.1.4 12-OVT1LK 12-201KB2F 8.1.1.3 [21219] QF0337 8.1.1.4 12-1YOLS7V 12-1ZXOMPB 8.1.1.3 [21219] QF0341 8.1.1.4 12-1XTBN8V 12-1ZPH5PX 8.1.1.3 [21219] QF0342 8.1.1.4 12-1XIVMBZ 12-20MEJOF 8.1.1.3 [21219] QF0351 8.1.1.4 12-1VM6MO5 12-20IJAD1 8.1.1.3 [21219] QF0352 8.1.1.4 12-206F3XH 12-209BHN9 8.1.1.3 [21219] QF0355 8.1.1.4 12-1V418JR 12-1ZNIQFX 8.1.1.3 [21219] QF0357 8.1.1.4 12-1YCG2PL 12-20GLG4R 8.1.1.3 [21219] QF0357 8.1.1.4 12-1YOKK4N 12-1Z520FN 8.1.1.3 WM5 [21219_2] 8.1.1.3 WM5 [21219_2] 8.1.1.4 12-1VGM2U4 12-1Y641L8 Unspecified - 8.1.1.4 12-1VM72OT 12-1WLUTF3 7.7.2.2 [18356] QF7201 8.1.1.3 12-1U5SY53 12-1U5ULV5 8.1.1 [21112] QF0043 8.1.1.3 12-1UQ61Q1 12-1UQWPP0 8.1.1 [21112] QF0061 8.1.1.3 12-1V7WVM7 12-1V7WVNO 8.1.1 [21112] QF0062 8.1.1.3 12-1V0593H 12-1V3K66J 8.1.1 [21112] QF0068 8.1.1.3 12-1UH87LR 12-1UOUW8L 8.1.1 [21112] QF0080 8.1.1.3 12-1UJQNRZ 12-1UJQNTU 8.1.1 [21112] QF0080 8.1.1.3 12-1VH3RCZ 12-1VH3HYN 8.1.1 [21112] QF0080 8.1.1.3 12-1VKHEG7 12-1VKHEGV 8.1.1 [21112] QF0080 8.1.1.3 12-1UIB7XV 12-1UPTJSJ 8.1.1 [21112] QF0081 8.1.1.3 12-1V418GZ 12-1V418HK 8.1.1 [21112] QF0081 8.1.1.3 12-QND3G8 12-1VM7MNP 8.1.1 [21112] QF0083 8.1.1.3 12-1U5VI79 12-1VMAZDJ 8.1.1 [21112] QF0084 8.1.1.3 12-1VM8H57 12-1VM8H5Y 8.1.1 [21112] QF0085 8.1.1.3 12-1VR73HT 12-1VR73IR 8.1.1 [21112] QF0088 8.1.1.3 12-1VROIM3 12-1WE2T3K 8.1.1 [21112] QF0089 8.1.1.3 12-1U4NF3F 12-1WAL0Z9 8.1.1 [21112] QF0093 8.1.1.3 12-1VM6N4J 12-1WLTUS5 8.1.1 [21112] QF0095 8.1.1.3 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 21. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 21 12-1VMBL0Z 12-1WXXCZJ 8.1.1 [21112] QF0096 8.1.1.3 12-1WVI3Q5 12-1WV14UH 8.1.1 [21112] QF00AA 8.1.1.3 12-1VR5SGX 12-1VR7CDZ 8.1.1 [21112] QF00AB 8.1.1.3 12-1WF6FQC 12-1WLTV3T 8.1.1 [21112] QF00AC 8.1.1.3 12-1WF6P3J 12-1X56312 8.1.1 [21112] QF00AF 8.1.1.3 12-1VR4BZH 12-1XFIKC2 8.1.1 [21112] QF00AG 8.1.1.3 12-1X65TKV 12-1XS24V7 8.1.1 [21112] QF00AK 8.1.1.3 12-1VNIMYR 12-1XM9M42 8.1.1 [21112] QF00AO 8.1.1.3 12-1WXFOAB 12-1Y54TB7 8.1.1 [21112] QF00AU 8.1.1.3 12-1R3SHD7 12-1R3SHEV 8.1.1 [21112] QF1001 8.1.1.3 12-1UWODHL 12-1UWODIV 8.1.1 [21112] QF0059 8.1.1.3 12-1VHLD1H 12-1VJIBZ1 8.1.1 [21112] QF0078 8.1.1.3 12-1V41905 12-1V4190P 8.1.1 [21112] QF0079 8.1.1.3 12-1VCQAE7 12-1VABY2J 8.1.1 [21112] QF0080 8.1.1.3 12-1VMCEM9 12-1VNJB15 8.1.1 [21112] QF0082 8.1.1.3 12-1VM5K6V 12-1VM5OFZ 8.1.1 [21112] QF0086 8.1.1.3 12-1TK4DJP 12-1VR7XBB 8.1.1 [21112] QF0088 8.1.1.3 12-1NXS3RV 12-1VMB443 8.1.1 [21112] QF0090 8.1.1.3 12-1VCQVAZ 12-1VVFZX5 8.1.1 [21112] QF0091 8.1.1.3 12-1VMC9ID 12-1VMC9JC 8.1.1 [21112] QF0094 8.1.1.3 12-1VR43FP 12-1VR613R 8.1.1 [21112] QF0097 8.1.1.3 12-1WV0HS3 12-1WVIDDX 8.1.1 [21112] QF0098 8.1.1.3 12-1WXX8FJ 12-1WYEWC1 8.1.1 [21112] QF00AA 8.1.1.3 12-1SD8XW1 12-1XEBKOX 8.1.1 [21112] QF00AE 8.1.1.3 12-1T2IN2L 12-1U5RPCP 8.1.1 [21112] QF00AO 8.1.1.3 12-1U0AX75 12-1XM9M2R 8.1.1 [21112] QF00AO 8.1.1.3 12-1R3SHD7 12-1SCQC43 8.1.1 [21112] QF1001 8.1.1.3 12-1R3SHD7 12-1SSU185 8.1.1 [21112] QF1002 8.1.1.3 12-1VM6B55 12-1VM8H0R 8.1.1 [21112] QF1003 8.1.1.3 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 22. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs 22 12-1LC1A2Z 12-1WF6BOH 8.1.1 [21112] QF0099 QF0099 8.1.1.3 12-1U5VI4H 12-1UH8O67 8.1.1 PDA [21112_1] 8.1.1 PDA [21112_1] 8.1.1.3 12-1VR6T39 12-1VR6T42 8.1.1 PDA [21112_4] 8.1.1 PDA _21112_4] 8.1.1.3 12-1VMBHFJ 12-1VMBHGE 8.1.1 PDA [21112_5] 8.1.1 PDA [21112_5] 8.1.1.3 12-1VM6HI1 12-1WS4HGD 8.1.1 PDA [21112_6] 8.1.1 PDA [21112_6] 8.1.1.3 12-1V418N3 12-1V7FOQ9 8.1.1.1 [21211] QF0114 8.1.1.3 12-1VH3RGB 12-1VKYYB5 8.1.1.1 [21211] QF0114 8.1.1.3 12-1UI8TH3 12-1UI8THP 8.1.1.1 [21211] QF0115 8.1.1.3 12-1RAJ0I1 12-1VGLLEK 8.1.1.1 [21211] QF0121 8.1.1.3 12-1VE7EH7 12-1VE6TJ6 8.1.1.1 [21211] QF0124 8.1.1.3 12-1U5V32T 12-1U7CGKP 8.1.1.1 [21211] QF0125 8.1.1.3 12-1VEOU89 12-1VI2IE9 8.1.1.1 [21211] QF0130 8.1.1.3 12-1UWODHL 12-1VR3IU1 8.1.1.1 [21211] QF0133 8.1.1.3 12-1VR2PWN 12-1VR3NJZ 8.1.1.1 [21211] QF0134 8.1.1.3 12-1HWWAY4 12-1VM5IIV 8.1.1.1 [21211] QF0139 8.1.1.3 12-1VR2PUZ 12-1VR3L6U 8.1.1.1 [21211] QF0141 8.1.1.3 12-1TXBDIV 12-1VTSQMV 8.1.1.1 [21211] QF0146 8.1.1.3 12-1WF6P3J 12-1WF6HIG 8.1.1.1 [21211] QF0153 8.1.1.3 12-1VR5ZGB 12-1VR4O99 8.1.1.1 [21211] QF0154 8.1.1.3 12-1PVZS4R 12-1VR5PTN 8.1.1.1 [21211] QF0155 8.1.1.3 12-1X3RF25 12-1X3RF2X 8.1.1.1 [21211] QF0156 8.1.1.3 12-1VNJ8NI 12-1VR29OR 8.1.1.1 [21211] QF0157 8.1.1.3 12-1WF5ZQH 12-1WF5ZRW 8.1.1.1 [21211] QF0157 8.1.1.3 12-1WA5CGZ 12-1WEE4FN 8.1.1.1 [21211] QF0158 8.1.1.3 12-1WF6G1R 12-1WF6G2Q 8.1.1.1 [21211] QF0158 8.1.1.3 12-1WLTLED 12-1WLTLEY 8.1.1.1 [21211] QF0159 8.1.1.3 12-1UGQKS5 12-1VR5ORB 8.1.1.1 [21211] QF0160 8.1.1.3 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 23. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 23 12-1WF6PMP 12-1WK5MQ5 8.1.1.1 [21211] QF0161 8.1.1.3 12-1W4M5R5 12-1WERWGT 8.1.1.1 [21211] QF0162 8.1.1.3 12-1VMCEHT 12-1VNJ4VP 8.1.1.1 [21211] QF0165 8.1.1.3 12-1QG70K8 12-1X1AK5N 8.1.1.1 [21211] QF0167 8.1.1.3 12-1WVIKB5 12-1WWYDEF 8.1.1.1 [21211] QF0169 8.1.1.3 12-1O2IS17 12-1X65R0B 8.1.1.1 [21211] QF0171 8.1.1.3 12-1WTJXYN 12-1WTJXZ8 8.1.1.1 [21211] QF0176 8.1.1.3 12-1VHLD1H 12-1YCG7H4 8.1.1.1 [21211] QF01AB 8.1.1.3 12-1VKHEG7 12-1YFTGHB 8.1.1.1 [21211] QF01AG 8.1.1.3 12-1TK6U03 12-1UIBBJV 8.1.1.1 [21211] QF1101 8.1.1.3 12-1UW5F8T 12-1UW5FA5 8.1.1.1 [21211] QF1102 8.1.1.3 12-1VM7OFB 12-1VM8AUM 8.1.1.1 [21211] QF1103 8.1.1.3 12-1VR2YCD 12-1VR2YD7 8.1.1.1 [21211] QF1104 8.1.1.3 12-1WA5CGZ 12-1WRAAA5 8.1.1.1 [21211] QF1105 8.1.1.3 12-1WF6G1R 12-1WRAAD1 8.1.1.1 [21211] QF1105 8.1.1.3 12-1X56KI9 12-1X56R61 8.1.1.1 [21211] QF1106 8.1.1.3 12-1VE7EQ3 12-1VG4DL9 8.1.1.1 [21211] QF2103 8.1.1.3 12-1UI8IN7 12-1VR7JA7 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VNJJZ2 12-1VNKHLQ 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VNJZ8L 12-1VNJUIQ 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR347X 12-1VR348W 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR398K 12-1VR399Z 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR4A7V 12-1VR4A8M 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR4FMB 12-1VR4FN2 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR6FWO 12-1VR60PC 8.1.1.1 [21211] QF4101 8.1.1.3 12-1UI8IN7 12-1WLTWCD 8.1.1.1 [21211] QF4102 8.1.1.3 12-1VR3957 12-1VR397S 8.1.1.1 [21211] QF4102 8.1.1.3 12-1WCP9WP 12-1WCP9XZ 8.1.1.1 [21211] QF4102 8.1.1.3 12-1WF73FF 12-1WF73IY 8.1.1.1 [21211] QF4102 8.1.1.3 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 24. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs 24 12-1WFFM67 12-1WFFM6W 8.1.1.1 [21211] QF4102 8.1.1.3 12-1R3SHD7 12-1VR77JP 8.1.1.1 [21211] QF5101 8.1.1.3 12-1W6DOPP 12-1W6DOQT 8.1.1.1 [21211] QF6101 8.1.1.3 12-1TXBDIV 12-1WV0RNH 8.1.1.1 [21211] QF7101 8.1.1.3 12-1W6PXXB 12-1WV0ROK 8.1.1.1 [21211] QF7101 8.1.1.3 12-1WA5CGZ 12-1XWWVON 8.1.1.1 [21211] QF7103 8.1.1.3 12-1WF6G1R 12-1XWWVPV 8.1.1.1 [21211] QF7103 8.1.1.3 12-1X56KGX 12-1XWWVQT 8.1.1.1 [21211] QF7103 8.1.1.3 12-1X56KI9 12-1XWWVRR 8.1.1.1 [21211] QF7103 8.1.1.3 12-1VR46RP 12-1VR46SJ 8.1.1.1 [21211] QF0100 8.1.1.3 12-1REV4NL 12-1VDPAUL 8.1.1.1 [21211] QF0118 8.1.1.3 12-1SJ54EF 12-1VGLLFE 8.1.1.1 [21211] QF0121 8.1.1.3 12-1U5SY53 12-1VMAX0J 8.1.1.1 [21211] QF0126 8.1.1.3 12-1VNJ20P 12-1VR2KIF 8.1.1.1 [21211] QF0132 8.1.1.3 12-1VNJZD9 12-1VR3YPZ 8.1.1.1 [21211] QF0136 8.1.1.3 12-1VM81EJ 12-1VR3OK5 8.1.1.1 [21211] QF0137 8.1.1.3 12-1V418SN 12-1V418T8 8.1.1.1 [21211] QF0138 8.1.1.3 12-1VNKRB3 12-1VNKRC7 8.1.1.1 [21211] QF0140 8.1.1.3 12-1UJQNRZ 12-1VMCBXB 8.1.1.1 [21211] QF0143 8.1.1.3 12-1VROIM3 12-1VROIMY 8.1.1.1 [21211] QF0148 8.1.1.3 12-1V41905 12-1VR46VZ 8.1.1.1 [21211] QF0149 8.1.1.3 12-1VM6N0D 12-1VM6N0Y 8.1.1.1 [21211] QF0150 8.1.1.3 12-1T2II25 12-1WF6XDZ 8.1.1.1 [21211] QF0154 8.1.1.3 12-1QHN64C 12-1VM5JMC 8.1.1.1 [21211] QF0156 8.1.1.3 12-1VMAF2Z 12-1VMC0PF 8.1.1.1 [21211] QF0160 8.1.1.3 12-1W4M5S2 12-1WAWS42 8.1.1.1 [21211] QF0162 8.1.1.3 12-1RVO17F 12-1VR5GB0 8.1.1.1 [21211] QF0164 8.1.1.3 12-1VM83AX 12-1X5630E 8.1.1.1 [21211] QF0170 8.1.1.3 12-1VR66BT 12-1VR6WMR 8.1.1.1 [21211] QF0170 8.1.1.3 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 25. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 25 12-1VR4BZH 12-1WF6HRX 8.1.1.1 [21211] QF0172 8.1.1.3 12-1X3PRS9 12-1X3PRSZ 8.1.1.1 [21211] QF0173 8.1.1.3 12-1WXFOAB 12-1X1RZWH 8.1.1.1 [21211] QF0174 8.1.1.3 12-1UH87BR 12-1WF6V8X 8.1.1.1 [21211] QF0176 8.1.1.3 12-1XFIDB5 12-1XHFCTH 8.1.1.1 [21211] QF0176 8.1.1.3 12-1X65TKV 12-1XKSUW0 8.1.1.1 [21211] QF0181 8.1.1.3 12-1S9QMWN 12-1XPN62V 8.1.1.1 [21211] QF0186 8.1.1.3 12-1VM6N8P 12-1VM7TE6 8.1.1.1 [21211] QF0186 8.1.1.3 12-1LC1A2Z 12-1XVG87F 8.1.1.1 [21211] QF0188 8.1.1.3 12-1Q16OWB 12-1X4CYI9 8.1.1.1 [21211] QF0189 8.1.1.3 12-1VM72OT 12-1XP58ZT 8.1.1.1 [21211] QF0190 8.1.1.3 12-1VMAEXZ 12-1VMBEH5 8.1.1.1 [21211] QF0190 8.1.1.3 12-1UH87LR 12-1Y72ZUH 8.1.1.1 [21211] QF01AF 8.1.1.3 12-1VR2NH1 12-1VR2NII 8.1.1.1 [21211] QF1104 8.1.1.3 12-1TXBDIV 12-1WLTK5Q 8.1.1.1 [21211] QF1105 8.1.1.3 12-1UW5DFF 12-1UW5DGH 8.1.1.1 [21211] QF1105 8.1.1.3 12-1W6PXXB 12-1W6PXY5 8.1.1.1 [21211] QF1105 8.1.1.3 12-1X56155 12-1X56KGK 8.1.1.1 [21211] QF1106 8.1.1.3 12-1X56KGX 12-1X56KHX 8.1.1.1 [21211] QF1106 8.1.1.3 12-1X65TKV 12-1XVG99R 8.1.1.1 [21211] QF1107 8.1.1.3 12-1UH87BR 12-1VPNBHD 8.1.1.1 [21211] QF2103 8.1.1.3 12-1VMJW4R 12-1VNJUJS 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VNJJXN 12-1VNKHMB 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VNJZ9H 12-1VNJUHZ 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR3GUN 12-1VR4LB3 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR4V1B 12-1VR4V22 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR6QRN 12-1VR6QT2 8.1.1.1 [21211] QF4101 8.1.1.3 12-1WF77PG 12-1WF77Q5 8.1.1.1 [21211] QF4102 8.1.1.3 12-1VM6N4J 12-1XQ49XF 8.1.1.1 [21211] QF5105 8.1.1.3 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 26. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs 26 12-1VR2NH1 12-1WIXZ3T 8.1.1.1 [21211] QF7101 8.1.1.3 12-1X0C24K 12-1X0C26K 8.1.1.1 [21211] QF7102 8.1.1.3 12-1X56155 12-1XYCA25 8.1.1.1 [21211] QF7103 8.1.1.3 12-1X65TKV 12-1XWWVSZ 8.1.1.1 [21211] QF7103 8.1.1.3 12-1XVXEFP 12-1XWET8K 8.1.1.1 [21211] QF7103 8.1.1.3 12-1KXYCJ7 12-1VGLLDP 8.1.1.1 [21211] QF0121 QF0121 8.1.1.3 12-1U089B9 12-1U089CS 8.1.1.1[21210] QFACR474_DEV3 ENU Don't think that this s/b 8.1.1.3 12-1U0ATEW 12-1U0ATGA 8.1.1.1[21210] QFACR474_DEV3 ENU Don't think that this s/b 8.1.1.3 12-1VM81EJ 12-1VMATZX 8.1.1.2 [21215] QF0201 8.1.1.3 12-1VR4BF7 12-1VR3P8V 8.1.1.2 [21215] QF0201 8.1.1.3 12-1UI7QYZ 12-1V14JRA 8.1.1.2 [21215] QF0202 8.1.1.3 12-1W7XG07 12-1WF75UB 8.1.1.2 [21215] QF0205 8.1.1.3 12-1U4NF3F 12-1VKHKCF 8.1.1.2 [21215] QF0206 8.1.1.3 12-1VR4BT3 12-1VR50U7 8.1.1.2 [21215] QF0207 8.1.1.3 12-1WF6PLV 12-1WHFPCJ 8.1.1.2 [21215] QF0207 8.1.1.3 12-1QG70K8 12-1VMBCSV 8.1.1.2 [21215] QF0208 8.1.1.3 12-1SJNUGJ 12-1WQ5VI3 8.1.1.2 [21215] QF0209 8.1.1.3 12-1VMAEXZ 12-1WLUFT3 8.1.1.2 [21215] QF0210 8.1.1.3 12-1DK2UO8 12-1WU19LH 8.1.1.2 [21215] QF0211 8.1.1.3 12-1U5V32T 12-1VR5ESF 8.1.1.2 [21215] QF0212 8.1.1.3 12-1QHN64C 12-1WYEYBP 8.1.1.2 [21215] QF0213 8.1.1.3 12-1JGY6HC 12-1WYWA9N 8.1.1.2 [21215] QF0216 8.1.1.3 12-1X6681L 12-1XCMB93 8.1.1.2 [21215] QF0216 8.1.1.3 12-1VR78HP 12-1VR7VHR 8.1.1.2 [21215] QF0217 8.1.1.3 12-1X1AZAL 12-1X65NWV 8.1.1.2 [21215] QF0218 8.1.1.3 12-1X3PH1V 12-1X4OYWX 8.1.1.2 [21215] QF0220 8.1.1.3 12-1VNKRB3 12-1X98CML 8.1.1.2 [21215] QF0221 8.1.1.3 12-1V418GZ 12-1WYEKN7 8.1.1.2 [21215] QF0222 8.1.1.3 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 27. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 27 12-1PPACL7 12-1VMB80D 8.1.1.2 [21215] QF0223 8.1.1.3 12-1VEOU89 12-1WF6MH3 8.1.1.2 [21215] QF0223 8.1.1.3 12-1WA5CGZ 12-1WEE4GH 8.1.1.2 [21215] QF0223 8.1.1.3 12-1WF6G1R 12-1WF7AUB 8.1.1.2 [21215] QF0223 8.1.1.3 12-1X65TKV 12-1X65TML 8.1.1.2 [21215] QF0223 8.1.1.3 12-1V418N3 12-1X1AS17 8.1.1.2 [21215] QF0225 8.1.1.3 12-1NSKPIL 12-1X8R0OX 8.1.1.2 [21215] QF0226 8.1.1.3 12-1S9QMWN 12-1VM55TX 8.1.1.2 [21215] QF0227 8.1.1.3 12-1STC0L5 12-1XHX1P1 8.1.1.2 [21215] QF0230 8.1.1.3 12-1UH87BR 12-1WXFIOE 8.1.1.2 [21215] QF0231 8.1.1.3 12-1XFIDB5 12-1XHFCUG 8.1.1.2 [21215] QF0231 8.1.1.3 12-1UJQNRZ 12-1X0SZC7 8.1.1.2 [21215] QF0232 8.1.1.3 12-1W4M5R5 12-1XC4U97 8.1.1.2 [21215] QF0232 8.1.1.3 12-1W4M5S2 12-1XC4UA1 8.1.1.2 [21215] QF0232 8.1.1.3 12-1XCM9RR 12-1XEJ0CQ 8.1.1.2 [21215] QF0233 8.1.1.3 12-1T2IN2L 12-1TK4R41 8.1.1.2 [21215] QF0238 8.1.1.3 12-1U0AX75 12-1VGLSEY 8.1.1.2 [21215] QF0238 8.1.1.3 12-1VNIMYR 12-1X663V7 8.1.1.2 [21215] QF0238 8.1.1.3 12-1X0BIZX 12-1X0BJ10 8.1.1.2 [21215] QF0239 8.1.1.3 12-1UH87LR 12-1WYVUF3 8.1.1.2 [21215] QF0240 8.1.1.3 12-1XC7L1L 12-1XC7L26 8.1.1.2 [21215] QF0241 8.1.1.3 12-1VMC9ID 12-1XT0PSF 8.1.1.2 [21215] QF0246 8.1.1.3 12-1VM7HW1 12-1XS1LZH 8.1.1.2 [21215] QF0251 8.1.1.3 12-1Q16OWB 12-1VMBP4R 8.1.1.2 [21215] QF0253 8.1.1.3 12-1VHLD1H 12-1Y2P00T 8.1.1.2 [21215] QF0254 8.1.1.3 12-1VMAF2Z 12-1YDEQQT 8.1.1.2 [21215] QF0256 8.1.1.3 12-1LC1A2Z 12-1Y54T99 8.1.1.2 [21215] QF0257 8.1.1.3 12-1VR43FP 12-1YK6TOR 8.1.1.2 [21215] QF0259 8.1.1.3 12-1V41SPV 12-1XEJIBF 8.1.1.2 [21215] QF1201 8.1.1.3 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 28. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs 28 12-1VR4BVB 12-1VR5ATP 8.1.1.2 WM5 [21215_1] 8.1.1.2 [21215_1] 8.1.1.3 12-1V6XL7R 12-1V7WKHX 8.1.1.2 WM5 [21215_1] 8.1.1.2 WM5 [21215_1] 8.1.1.3 12-1VNJH0Z 12-1VNJH1R 8.1.1.2 WM5 [21215_1] 8.1.1.2 WM5 [21215_1] 8.1.1.3 12-1WCP7ZT 12-1WCP80M 8.1.1.2 WM5 [21215_1] 8.1.1.2 WM5 [21215_1] 8.1.1.3 12-1X1S03V 12-1X1GML7 8.1.1.2 WM5 [21215_2] 8.1.1.2 WM5 _21215_2] 8.1.1.3 12-1VNJY1R 12-1VR6P9H 8.1.1.2 WM5 [21215_3] 8.1.1.2 WM5 [21215_3] 8.1.1.3 12-1OOD149 12-1WQNMNT Unspecified ??? 8.1.1.3 12-1PBVORR 12-1SM2F17 8.1.1 [21112] QF0008 8.1.1.2 12-1SI5H61 12-1SI5H6M 8.1.1 [21112] QF0008 8.1.1.2 12-1TBLYYA 12-1TBLZ15 8.1.1 [21112] QF0015 8.1.1.2 12-1THO6OP 12-1TK476J 8.1.1 [21112] QF0016 8.1.1.2 12-1T7V4R7 12-1TBLYXR 8.1.1 [21112] QF0017 8.1.1.2 12-1TH5NV5 12-1THO2I5 8.1.1 [21112] QF0017 8.1.1.2 12-1SFPEAN 12-1TK3VLL 8.1.1 [21112] QF0019 8.1.1.2 12-1TGO4RF 12-1TI66LP 8.1.1 [21112] QF0021 8.1.1.2 12-1OQD0BB 12-1TK8U26 8.1.1 [21112] QF0023 8.1.1.2 12-1STC0UB 12-1TK5L5F 8.1.1 [21112] QF0023 8.1.1.2 12-1TK6LZT 12-1TK85H4 8.1.1 [21112] QF0023 8.1.1.2 12-1TD6X31 12-1TDOVOJ 8.1.1 [21112] QF0024 8.1.1.2 12-1L3YVPO 12-1T5WKPM 8.1.1 [21112] QF0025 8.1.1.2 12-1QBCC2R 12-1TA9KB1 8.1.1 [21112] QF0026 8.1.1.2 12-1SJ5MIZ 12-1TS8XK5 8.1.1 [21112] QF0026 8.1.1.2 12-1T2J5H3 12-1TARVI6 8.1.1 [21112] QF0026 8.1.1.2 12-1SBRAKT 12-1TTI5LX 8.1.1 [21112] QF0031 8.1.1.2 12-1TK4CEL 12-1TK9IXL 8.1.1 [21112] QF0031 8.1.1.2 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 29. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 29 12-1QMX8LP 12-1U0DDZT 8.1.1 [21112] QF0033 8.1.1.2 12-1U0BPQZ 12-1U0BPSO 8.1.1 [21112] QF0034 8.1.1.2 12-1T7DG8H 12-1T7DG98 8.1.1 [21112] QF0035 8.1.1.2 12-1RHR0N1 12-1TARVQH 8.1.1 [21112] QF0037 8.1.1.2 12-1R6NUCR 12-1TDO7P7 8.1.1 [21112] QF0040 8.1.1.2 12-1TUVZQ9 12-1TXBVH1 8.1.1 [21112] QF0041 8.1.1.2 12-1U5RB3V 12-1U5RB5J 8.1.1 [21112] QF0041 8.1.1.2 12-1UHPV6B 12-1UHPV78 8.1.1 [21112] QF0042 8.1.1.2 12-1TXC3RL 12-1TXT92X 8.1.1 [21112] QF0044 8.1.1.2 12-1U4I7KV 12-1U5RZSJ 8.1.1 [21112] QF0044 8.1.1.2 12-1TK9JCV 12-1U0AHDE 8.1.1 [21112] QF0045 8.1.1.2 12-1UI81Z5 12-1UI820R 8.1.1 [21112] QF0046 8.1.1.2 12-1ME9N7W 12-1U8SE0P 8.1.1 [21112] QF0048 8.1.1.2 12-1U0866H 12-1U09KKL 8.1.1 [21112] QF0048 8.1.1.2 12-1UI8T7X 12-1UFS6HJ 8.1.1 [21112] QF0048 8.1.1.2 12-IVNITD 12-1U5RJ4P 8.1.1 [21112] QF0048 8.1.1.2 12-OM5V6D 12-1TDOR8T 8.1.1 [21112] QF0048 8.1.1.2 12-1UIB7Z9 12-1UMPRTK 8.1.1 [21112] QF0049 8.1.1.2 12-1SSTZQV 12-1UJQL8W 8.1.1 [21112] QF0050 8.1.1.2 12-1UH87BR 12-1UH8JTX 8.1.1 [21112] QF0051 8.1.1.2 12-1KJP2WG 12-1UIA3SN 8.1.1 [21112] QF0053 8.1.1.2 12-1RRBFQ9 12-1UOWLB9 8.1.1 [21112] QF0054 8.1.1.2 12-1QPSY8J 12-1UIADXT 8.1.1 [21112] QF0055 8.1.1.2 12-1V0598R 12-1UZMXSH 8.1.1 [21112] QF0056 8.1.1.2 12-1SBRA31 12-1STC1G9 8.1.1 [21112] QF0058 8.1.1.2 12-1TGOA5B 12-1V41YTV 8.1.1 [21112] QF0060 8.1.1.2 12-1VH3J0H 12-1VH3J1D 8.1.1 [21112] QF0064 8.1.1.2 12-1UGQK67 12-1UG91VX 8.1.1 [21112] QF0065 8.1.1.2 12-1U8XCTD 12-1U8XCU7 8.1.1 [21112] QF0066 8.1.1.2 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 30. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs 30 12-1T6DMLW 12-1VI33A5 8.1.1 [21112] QF0067 8.1.1.2 12-1UI8QNP 12-1VKHLAV 8.1.1 [21112] QF0068 8.1.1.2 12-1UU5KSH 12-1UX5VWV 8.1.1 [21112] QF0074 8.1.1.2 12-1RPD2ML 12-1VM83TH 8.1.1 [21112] QF0076 8.1.1.2 12-1OK0UBP 12-1VEOVOV 8.1.1 [21112] QF0081 8.1.1.2 12-1VM6N5D 12-1VR58XF 8.1.1 [21112] QF0082 8.1.1.2 12-1V6FY27 12-1V6FY31 8.1.1 PDA [21112_2] 8.1.1 PDA [21112_2] 8.1.1.2 12-1SBRAKT 12-1UH8553 8.1.1.1 [21211] QF0101 8.1.1.2 12-1TGO4RF 12-1UI8E4P 8.1.1.1 [21211] QF0101 8.1.1.2 12-1OVCU5D 12-1UI8Y05 8.1.1.1 [21211] QF0103 8.1.1.2 12-1UQ62AL 12-1UX6LM3 8.1.1.1 [21211] QF0104 8.1.1.2 12-1TK9JCV 12-1UZ5U7X 8.1.1.1 [21211] QF0105 8.1.1.2 12-1THO6OP 12-1UX5DMT 8.1.1.1 [21211] QF0106 8.1.1.2 12-1UGQKML 12-1UI7VPC 8.1.1.1 [21211] QF0106 8.1.1.2 12-IVNITD 12-1UIBF3Z 8.1.1.1 [21211] QF0106 8.1.1.2 12-1TK4UOX 12-1U0F4EH 8.1.1.1 [21211] QF0107 8.1.1.2 12-1U0A9KV 12-1UIA7EN 8.1.1.1 [21211] QF0107 8.1.1.2 12-1QMX8LP 12-1UXMXVV 8.1.1.1 [21211] QF0108 8.1.1.2 12-1V3JQI3 12-1V3JQIN 8.1.1.1 [21211] QF0109 8.1.1.2 12-1SBRA31 12-1UW6491 8.1.1.1 [21211] QF0110 8.1.1.2 12-1UX6FHT 12-1UZD71U 8.1.1.1 [21211] QF0112 8.1.1.2 12-1R0X6NL 12-1V4108B 8.1.1.1 [21211] QF0113 8.1.1.2 12-1L3YVPO 12-1V9TQUZ 8.1.1.1 [21211] QF0116 8.1.1.2 12-1S1FXNF 12-1VBAHH9 8.1.1.1 [21211] QF0117 8.1.1.2 12-1VK09JB 12-1VK09K4 8.1.1.1 [21211] QF0119 8.1.1.2 12-1R6NUCR 12-1VM565P 8.1.1.1 [21211] QF0120 8.1.1.2 12-1TENCIJ 12-1VGLLFW 8.1.1.1 [21211] QF0121 8.1.1.2 12-1VM5K43 12-1VM585D 8.1.1.1 [21211] QF0122 8.1.1.2 12-OM5V6D 12-1VM8YSH 8.1.1.1 [21211] QF0123 8.1.1.2 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 31. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Quick Fixes Included in Siebel 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 31 12-1PBVORR 12-1VM6VS9 8.1.1.1 [21211] QF0127 8.1.1.2 12-1RRBFQ9 12-1VM9CT7 8.1.1.1 [21211] QF0128 8.1.1.2 12-1U5R7UV 12-1VNJ8VX 8.1.1.1 [21211] QF0129 8.1.1.2 12-1VM6N5D 12-1VM90VR 8.1.1.1 [21211] QF0131 8.1.1.2 12-1V0598R 12-1VR2KEB 8.1.1.1 [21211] QF0136 8.1.1.2 12-1VH3J0H 12-1VR2KGF 8.1.1.1 [21211] QF0136 8.1.1.2 12-1NSKL0N 12-1VABKYK 8.1.1.1 [21211] QF0142 8.1.1.2 12-1TUED13 12-1VR3YEY 8.1.1.1 [21211] QF0142 8.1.1.2 12-1TBLYYA 12-1WCVGL3 8.1.1.1 [21211] QF0147 8.1.1.2 12-1SF7E1F 12-1VR36YB 8.1.1.1 [21211] QF1104 8.1.1.2 12-1OVCU5D 12-1VCQE1C 8.1.1.1 [21211] QF2101 8.1.1.2 12-1UQ62AL 12-1VCQE0E 8.1.1.1 [21211] QF2101 8.1.1.2 12-1UX5Q36 12-1UX5Q4K 8.1.1.1 [21211] QF2101 8.1.1.2 12-1UX6LOB 12-1UX6LQ5 8.1.1.1 [21211] QF2101 8.1.1.2 12-1UX5RJV 12-1VR5MSB 8.1.1.1 [21211] QF4101 8.1.1.2 12-1QK1GG2 12-1QK1GGU 8.1.1 [21111] QF0001 8.1.1.1 12-1RBHO55 12-1RBHO6F 8.1.1 [21111] QF0001 8.1.1.1 12-1RPF1Z9 12-1RPF20H 8.1.1 [21111] QF0001 8.1.1.1 12-1RR1O5N 12-1RRCAHA 8.1.1 [21111] QF0001 8.1.1.1 12-1RRCAHM 12-1RRCAIV 8.1.1 [21111] QF0001 8.1.1.1 12-1RNH7ER 12-1RNH7G4 8.1.1 [21111] QF0001 8.1.1.1 12-1NLY66Z 12-1R7MK4U 8.1.1 [21111] QF0002 8.1.1.1 12-1KDK35I 12-1RBZBRA 8.1.1 [21111] QF0003 8.1.1.1 12-1S8QNHX 12-1S8QNIW 8.1.1 [21112] QF0004 8.1.1.1 12-1QT7XTB 12-1S20GWP 8.1.1 [21112] QF0005 8.1.1.1 12-1ONVDYP 12-1SGOF1D 8.1.1 [21112] QF0006 8.1.1.1 12-1RKLYHL 12-1RKLYIW 8.1.1 [21112] QF0006 8.1.1.1 12-1S8I5DB 12-1SGOF07 8.1.1 [21112] QF0006 8.1.1.1 12-1RAJ07R 12-1SD932B 8.1.1 [21112] QF0007 8.1.1.1 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 32. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Enhancements and Updates in 8.1.1.x Fix Packs 32 Enhancements and Updates in 8.1.1.x Fix Packs This topic identifies the enhancements and updates provided in version 8.1.1.x releases. Enhancements are cumulative, inclusive of the previous 8.1.1.x Fix Pack releases. This topic contains the following subtopics: ■ “Enhancements and Updates in Version 8.1.1.4” on page 33 ■ “Enhancements and Updates in Version 8.1.1.3” on page 34 12-1KPTT57 12-1S4C6VJ 8.1.1 [21112] QF0009 8.1.1.1 12-1M4CI03 12-1M4CI1D 8.1.1 [21112] QF0009 8.1.1.1 12-1PCDF0P 12-1SB8AZ3 8.1.1 [21112] QF0009 8.1.1.1 12-1RPEN89 12-1ROX0RL 8.1.1 [21112] QF0009 8.1.1.1 12-1RVNYWA 12-1RXLAYA 8.1.1 [21112] QF0009 8.1.1.1 12-1SD8MX5 12-1SD8MYF 8.1.1 [21112] QF0009 8.1.1.1 12-1SSU76Z 12-1SSU77O 8.1.1 [21112] QF0009 8.1.1.1 12-1RVNYUP 12-1RVNYW3 8.1.1 [21112] QF0009 8.1.1.1 12-1RZPUA5 12-1S98C5N 8.1.1 [21112] QF0009 8.1.1.1 12-1RZPUB1 12-1S8R2S7 8.1.1 [21112] QF0009 8.1.1.1 12-1SSU75R 12-1SSU76Q 8.1.1 [21112] QF0009 8.1.1.1 12-1P5N6JM 12-1SLLJBD 8.1.1 [21112] QF0011 8.1.1.1 12-1OUTTD2 12-1T30LUT 8.1.1 [21112] QF0012 8.1.1.1 12-1SW8CMD 12-1T12EQ1 8.1.1 [21112] QF0013 8.1.1.1 12-1SK50OF 12-1SZMHS5 8.1.1 [21112] QF0014 8.1.1.1 12-1Q25Q6M 12-1TB9J4X 8.1.1 [21112] QF0018 8.1.1.1 12-1TK7X5V 12-1TKA88F 8.1.1 [21112] QF0030 8.1.1.1 12-1N3J10T 12-1TXT2GX 8.1.1 [21112] QF0032 8.1.1.1 12-1RAJ07R 12-1SINFF1 8.1.1 [21112] QF1001 8.1.1.1 Table 2. Quick Fixes Included in Version 8.1.1.x Change Request ID/ Base Bug ID Fix Request ID/Bug ID Fix Pack Base Quick Fix Version Merged Into Fix Pack
  • 33. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Enhancements and Updates in 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 33 ■ “Enhancements and Updates in Version 8.1.1.2” on page 39 ■ “Enhancements and Updates in Version 8.1.1.1” on page 40 Enhancements and Updates in Version 8.1.1.4 Table 3 lists the enhancements and updates provided in Fix Pack version 8.1.1.4. This topic is part of “Enhancements and Updates in 8.1.1.x Fix Packs” on page 32. Table 3. Enhancements and Updates in Version 8.1.1.4 Feature Enhancement or Certification Number Feature Enhancement or Certification Description ACR 475A Enhances UCM to support the Higher Education application. Instructions for ACR 475 ACR 475B Enhances UCM to provide Data Governance, Data Quality, and usability enhancements. Instructions for ACR 475 ACR 499 ACR 499 provides the following enhancements to the Bulk Orders functionality: ■ Bulk Promotion Upgrade and Disconnect: Customers can apply promotions to products using bulk requests. ■ Bulk Quotes: Customers can create bulk quotes. ■ Agreement and Network Child Types in Action Sets: Customers can add Network or Agreement products in orders or quotes using bulk requests. ■ Account Group Specification: Customers can use existing account, contact, or assets lists to create bulk requests. ■ Submit Bulk Orders: Bulk orders can be submitted to the back office in a single click from the Bulk Request screen. Instructions for ACR 499 ACR 502 ACR 502 provides the following Siebel Configurator enhancements: ■ The ability to defer an update within a scripting event to allow multiple attribute change even add/set attribute calls. ■ A new scripting event to get product attribute values. ■ The ability to show/hide UI controls based on user properties and the instance variable values.api method. Instructions for ACR 502
  • 34. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Enhancements and Updates in 8.1.1.x Fix Packs 34 Enhancements and Updates in Version 8.1.1.3 Table 5 lists the enhancements and updates provided in Fix Pack version 8.1.1.3. This topic is part of “Enhancements and Updates in 8.1.1.x Fix Packs” on page 32. ACR 526 Trade Promotions Management Quickstart Instructions for ACR 526 ACR 543 Extends the Siebel web services framework to provide an endpoint through Oracle WLS. Instructions for ACR 543 ACR 623 Intelligent-Offer Generation (IOG) and certification with RTD 3.0 Instructions for ACR 623 ACR 626 Integration of Mobile Sales Assistant to the Siebel On-Premise application. Instructions for ACR 626 Table 3. Enhancements and Updates in Version 8.1.1.4 Feature Enhancement or Certification Number Feature Enhancement or Certification Description
  • 35. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Enhancements and Updates in 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 35
  • 36. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Enhancements and Updates in 8.1.1.x Fix Packs 36 Table 4. Enhancements and Updates in Version 8.1.1.3 Feature Enhancement or Certification Number Feature Enhancement or Certification Description ACR 426 Adds electronic medical device reporting to the AECM module. Instructions for ACR 426
  • 37. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Enhancements and Updates in 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 37 ACR 463 ACR 463 provides the following enhancements: Order to Activate Enhancements: ■ Cancel Order header button ■ Cancellation affecting future dated orders: ■ Changes to support order revisions ■ Computing previous values on Submit ■ Dependency on follow-on orders ■ Due Date changes for Disconnect ■ Extending Sales Order EBO ■ Invalidate stale orders ■ Keep customer intent of submitted orders ■ Line item history ■ Non-paying accounts ■ Trouble Ticketing extensions ■ Order Update Business Web Service ■ Product Class/Attribute Sync Web Service ■ Product Import Web Service Product Extensions for O2A: ■ Verify future-dated orders (warning message on header) ■ Warning messages on assets for future-dated orders Order to Bill PIP Enhancements: ■ Support Friends and Family ■ Collections Flow ■ Map CRM discount to billing objects ■ Order validations Billing Management UI enhancements: ■ Adjust unbilled events and child account events ■ Display child account balance in Siebel Billing Management screen. ■ View promotion name on invoice. Instructions for ACR 463 Table 4. Enhancements and Updates in Version 8.1.1.3 Feature Enhancement or Certification Number Feature Enhancement or Certification Description
  • 38. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Enhancements and Updates in 8.1.1.x Fix Packs 38 ACR 474 Supports OSM Integration and the Order to Activate PIP, and forward-ports MDM, PIM, and Order to Cash enhancements from Siebel 8.x to Siebel 8.1.1.x applications. Instructions for ACR 474 and ACR 508 ACR 500 Enables effective bundling of products necessary in the communications, finance, media, and utilities industries, and enhances promotion capabilities for component-level commitment, eligibility in promotion upgrade, asset- based recommendations, and split/merge capabilities of promotions. Instructions for ACR 500 ACR 508 Forward-ports the Order to Cash PIP to Siebel version 8.1.1 applications. Instructions for ACR 508 ACR 529 Provides a single-step upgrade from Siebel Business Applications to Siebel Cross-Industry Applications. ACR 539 Modifies the Siebel Clinical product to support the Study, Subject, and Visit Synchronization Process Integration Pack for Siebel Clinical and Oracle Clinical. This enhancement also provides a way to accurately track and respond to issues related to site performance and protocol adherence. Instructions for ACR 539 Table 4. Enhancements and Updates in Version 8.1.1.3 Feature Enhancement or Certification Number Feature Enhancement or Certification Description
  • 39. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Enhancements and Updates in 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 39 Enhancements and Updates in Version 8.1.1.2 Table 5 lists the enhancements and updates provided in version 8.1.1.2. ACR 562 ACR 562 extends the functionality previously provided by ACR 422, which was included in the Siebel 8.1.1.1 Fix Pack. ACR 422 provided the following functionality: ■ Added missing text for ALT strings and other text read by screen readers. ■ Added titles for views and applets. ■ Provided announcements of row and column identifiers in list applets and allowed the column used for the row identifier to be configurable. ■ Fixed various loss-of-focus defects. ■ Fixed various tab-order defects that are most often encountered when users are navigating between applets. ■ Fixed various keyboard-shortcut defects and extended the set of available shortcuts. ■ Added help topics for accessibility and updated the keyboard shortcuts help topics. Instructions for ACR 562 ACR 574 Enhances the Smart Answer Server. Instructions for ACR 574 Table 4. Enhancements and Updates in Version 8.1.1.3 Feature Enhancement or Certification Number Feature Enhancement or Certification Description
  • 40. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Enhancements and Updates in 8.1.1.x Fix Packs 40 This topic is part of “Enhancements and Updates in 8.1.1.x Fix Packs” on page 32. Enhancements and Updates in Version 8.1.1.1 Table 6 lists the enhancements and updates provided in version 8.1.1.1. This topic is part of “Enhancements and Updates in 8.1.1.x Fix Packs” on page 32. Table 5. Enhancements and Updates in Version 8.1.1.2 Feature Enhancement or Certification Number Feature Enhancement or Certification Description ACR 444 ACR 444 provides the following enhancements: ■ Provides a utility for administrators to act on failing Store-and-Forward transactions. ■ Enhances logging capabilities (server). ACR 457 Provides cross-network validation and cascade delete enhancements for network ordering for Siebel Customer Order Management for SIA. Instructions for ACR 457 ACR 464 Provides support for CRM Desktop for Outlook. Instructions for ACR 464 ACR 492 Provides Web service access through the Mobile Web Client to other local desktop applications. ACR 494 Provides Event Check enhancements and BEO Report functionality for the Siebel Travel & Transportation application. Instructions for ACR 494 ACR 544 Enhances the Siebel Remote utility and allows it to be integrated with the Siebel HA Upgrade solution.
  • 41. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Enhancements and Updates in 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 41 Table 6. Enhancements and Updates in Version 8.1.1.1 Feature Enhancement or Certification Number Feature Enhancement or Certification Description ACR 432 Prevents users from opening multiple sessions on the Mobile Web Client. ACR 435 ACR 435 resolves the following issues with the printed version of the 5 Day Weekly HTML Calendar: ■ The calendar only shows appointments that are scheduled within the 8 a.m. to 5 p.m. workday. ■ The default page orientation for most printers is set to Portrait. ■ Changing the display intervals on the Calendar results in sporadic results. ■ Contact Name, Primary Phone, and Description should be displayed on the 5 Day Weekly Calendar for each appointment. ACR 437 Provides the ability to expose CDI WebServices for all CRUD operations on key entities such as Account, Contact, Household, Financial Account, and so forth. Instructions for ACR 437
  • 42. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Enhancements and Updates in 8.1.1.x Fix Packs 42 ACR 439 ACR 439 contains the following enhancements for Siebel Search ■ Activates the Advanced Search button only when a search engine has been configured. ■ Converts Saved Searches from an HTML list to a drop-down list. ■ Makes Recent Saved Searches only display when a search engine has been configured. ■ Implements Preview with Search functionality to match the functionality available with Siebel version 7 applications. ACR 439 provides a preview button in the Search results pane (left-pane search). When users click the preview button, the record details appear in a pop-up window. ■ Provides Attach functionality that is based on the parent applet. ACR 439 provides an Attach button in the Search results pane (left-pane search). When usersclick the Attach button, the record selected in the search pane is attached to the record on the right. For example, users can attach a contact tothe opportunity record displayed on the right side of the screen. ■ Corrects a Search Definition dependency for the FIND function. FIND categories can now be defined irrespective of the search engine definition. Instructions for ACR 439 Instructions for ACR 439B ACR 450 ACR 450 provides the following enhancements: ■ Menus and Packages ■ Function Space Displays ■ Inventory Display Enhancements ■ Sleeping Room Mapping Instructions for ACR 450 Table 6. Enhancements and Updates in Version 8.1.1.1 Feature Enhancement or Certification Number Feature Enhancement or Certification Description
  • 43. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Enhancements and Updates in 8.1.1.x Fix Packs Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 43 ACR 452 ACR 452 provides the following Oracle Secure Enterprise Search enhancements: ■ Remote Administration configuration ■ Auto keyword generation ■ Mixed operator search ■ Searching by file format ■ Dynamic weights Instructions for ACR 452 ACR 456 Allows users to perform Assignment Manager bulk-data maintenance (CRUD on Rules, Positions, candidates and so forth) through client views and screens. Instructions for ACR 456 ACR 467 Provides Siebel Financial Services Customer Order Management for Banking functionality. Instructions for ACR 467 ACR 471 Bundles the Promotion and Product class relationship so that changing a promotion in a change order loads the default product. Instructions for ACR 471 ACR 476 Rebases Siebel Email Response support for Smart Answer support. Instructions for ACR 476 ACR 480 ACR 480 provides the following enhancements: ■ Resolves key connection gaps between core processes: marketing and trade management, trade management, and retail execution. ■ Provides key functional enhancements needed to fulfill Oracle Trade Management processes. ■ Significantly enhances usability across trade management in Siebel applications. Instructions for ACR 480 Table 6. Enhancements and Updates in Version 8.1.1.1 Feature Enhancement or Certification Number Feature Enhancement or Certification Description
  • 44. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 44 Configuration Instructions for Enhancements and Updates This topic contains configuration instructions for some of the enhancements and updates provided in version 8.1.1.x releases. NOTE: It is only necessary to perform the configurations in the following section if you want to implement the ACRs that they are for. Perform the instructions described in the subtopics listed below after you install the current Siebel Fix Pack, as described in “Siebel Fix Pack Installation Instructions” on page 467. NOTE: For more information about activities performed in Siebel Tools, including importing archive (.sif) files, see Using Siebel Tools and Configuring Siebel Business Applications. For more information about activities performed in the Siebel application, see Siebel Applications Administration Guide and related books. These guides are available on the Siebel 8.1 Bookshelf on OTN at http:// www.oracle.com/technology/documentation/siebel.html. This topic contains the following subtopics: ■ “Instructions for ACR 358” on page 45 ■ “Instructions for ACR 403” on page 45 ■ “Instructions for ACR 422” on page 50 ■ “Instructions for ACR 426” on page 71 ■ “Instructions for ACR 437” on page 94 ■ “Instructions for ACR 439” on page 95 ■ “Instructions for ACR 450” on page 100 ■ “Instructions for ACR 452” on page 100 ■ “Instructions for ACR 456” on page 102 ■ “Instructions for ACR 457” on page 104 ACR 481 ■ Provides the ability to ignore Outlook appointments/tasks based on the “Private” flag. ■ Addresses an issue where the Outlook Add-in can lock users out of their accounts after the password has been changed on the authenticating agent (such as Active Directory), but the users have not updated their Outlook Add-in passwords. ACR 488 Provides Histories and Futures functionality. Instructions for ACR 488 Table 6. Enhancements and Updates in Version 8.1.1.1 Feature Enhancement or Certification Number Feature Enhancement or Certification Description
  • 45. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 45 ■ “Instructions for ACR 463” on page 108 ■ “Instructions for ACR 464” on page 147 ■ “Instructions for ACR 467” on page 156 ■ “Instructions for ACR 471” on page 163 ■ “Instructions for ACR 474 and ACR 508” on page 169 ■ “Instructions for ACR 475” on page 248 ■ “Instructions for ACR 476” on page 295 ■ “Instructions for ACR 480” on page 299 ■ “Instructions for ACR 488” on page 310 ■ “Instructions for ACR 494” on page 310 ■ “Instructions for ACR 499” on page 311 ■ “Instructions for ACR 508” on page 377 ■ “Instructions for ACR 502” on page 364 ■ “Instructions for ACR 508” on page 377 ■ “Instructions for ACR 526” on page 382 ■ “Instructions for ACR 539” on page 383 ■ “Instructions for ACR 543” on page 408 ■ “Instructions for ACR 562” on page 412 ■ “Instructions for ACR 574” on page 457 ■ “Instructions for ACR 623” on page 463 ■ “Instructions for ACR 626” on page 463 ■ “Instructions for BI Publisher Enhancements” on page 466 Instructions for ACR 358 For information about how to implement ACR 358, within My Oracle Support, navigate to the Knowledge tab, and search for Article ID 781368.1 Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 403 Use the instructions in the following section to configure ACR 403.
  • 46. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 46 Preinstallation Instructions for ACR 403 Before you apply the Siebel 8.1.1.x Fix Pack, the local database needs to be extracted from the Server machine and initialized on the machine where Siebel Mobile Client will be installed. Use the following procedure to extract the local database from the server machine and initialize iton the machine where the Siebel Mobile client will be installed. To extract the local database and initialize it 1 Navigate to the Administration - Siebel Remote screen. a Query for HQ, and select a sample user in your system as mobile client and MOBILE CLIENT - STANDARD as routing model. b Navigate to the Administration - Siebel Remote screen, and then the Remote System Preferences view. Uncheck the following parameters: ❏ Enable Mobile Password Expiration ❏ Enable Mobile Password Syntax Check ❏ Optimized Visibility Check ❏ Check Enable Transaction Logging 2 Enable Siebel Remote Component Group. 3 From the Server Manager command line utility, connect to the Siebel Server and run thefollowing commands: ■ change param authentication=none for comp synchmgr ■ list advanced param authentication for comp synchmgr 4 Verify that the authentication parameter has been configured correctly. 5 Using the Server Manager Command line utility, run the jobs-Generate New Database and db extract as follows: ■ start task for comp gennewdb with sleeptime = 10 ■ list task <tasked ID> (Keep listing the task until the status changes to "Completed") ■ start task for comp dbxtract with client=a sample user in your system ■ list task <tasked ID> (Keep listing the task until the status changes to "Completed") ■ list advanced param portnumber for comp synchmgr Installation Instructions 1 Apply 8.1.1.x on Siebel Tools and Siebel Enterprise Server. (The patch for Siebel Enterprise Server automatically patches the "Siebel Server, Siebel Gateway Server, and Siebel Database Server components.) 2 Verify that the following files are present under DBSRVRENU ■ seed_disconn.dat
  • 47. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 47 ■ seed_disconn.inp 3 Verify that the following files are present under <Siebel Tools loc>TOOLSREPPATCH: ■ discon_symbstring.sif ■ disconnected.sif 4 In tools.cfg, make the following changes: SymStrPrefix = SBL_ (instead of X_) DockConnString = <Siebel Server Name>::<Synchmgr port> (For example, sdchs21n467::40400) 5 Log into Siebel Tools as a sample user in your system and point to the local database. 6 Enter the password for the sample user, click Continue, enter the Server password for the sample user at the prompt, and click Next. Siebel Tools starts initialization of all the tables and parameters for the local database. Once the initialization is done, Siebel Tools will automatically open and will connect to the local database. 7 In the Tools ODBC entry, enter the UID/PWD for the local database. (For the local database, UID/ PWD should be DBA/SIEBEL12] 8 Enter the encryption Key for the database and check for the database connection. It should show as successful once the UID/PWD and Encryption Key have been entered correctly. TIP: To get the encryption key, navigate to the Administration - Siebel Remote screen, and then the Mobile Clients view. Query for the HQ* and then query for the sample user. In the Additional Info column, query for RemLocSec:PlainKey. 9 Log into Siebel Tools (pointing to the local database). Navigate to Tools, and then Check Out. NOTE: If you receive the "Error connecting to Datasource" error message, then check the data source information. The source should be SSD default instance (UID/Server pwd) and Destination: SSD Local Db default instance. 10 Click the Get button to get all the projects. Siebel Tools will get all the projects one by one. This will take two to five hours to complete. 11 Open Siebel Tools (connecting to the local database) and lock the following projects one by one by selecting the project and setting the "Locked" flag to "true": ■ Fast Search ■ Service ■ Siebel Universal Agent ■ ERM Admin ■ New Search ■ Siebel Field Service Enterprise ■ Siebel Marketing Enterprise ■ Siebel Sales Enterprise
  • 48. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 48 ■ Siebel eChannel ■ Siebel Field Service Enterprise 12 Import the discon_symbstring.sif and Disconnected.sif files (mentioned in Step 3) by clicking on Tools> Import from Archive and selecting the .sif files one by one. Complete the following steps: a Click the Next button in "Import Wizard - Preview". Once import is successful, the number of objects imported and updated will display. Click OK. b Click Finish in "Import Wizard - Summary" to finish the import. 13 Install Mobile Client (MWC) on a Microsoft Windows XP machine (An XP machine is needed to start the DSM listener and .net 2.0 should be installed on that machine. 14 Make a copy of your existing siebel.srf (or siebel_sia.srf for SIA) and compile the imported changes mentioned in Step 12 to the siebel.srf (or siebel_sia.srf). 15 In MWC Application.cfg (such as uagent.cfg for Siebel Call Center Application) make the following changes: ■ DockConnString = <machine name of the Siebel server machine from where the local database is imported>::<Synch Mgr Port> (This is applicable only if this is a fresh installation.) For example, DockConnString = sdcp1952i017::40400 ■ SearchDefName = Mobile Client Search Definition 16 Apply Siebel 8.1.1.x on the Mobile Web Client to create the dsm.zip file under <mobile client install loc>BIN>. Unzip the dsm.zip file to create the dsm folder under <mobile client install loc>BIN>. 17 Run the dataimp command as follows: a Copy the files seed_disconn.dat and seed_disconn.inp files from 4 to the Mobile Client machine (for example, D:FS Build4_Final.)
  • 49. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 49 b Navigate to <mobile client install loc>BIN> using the command prompt and run the following command. dataimp /u $USERNAME /p $PASSWORD /c "$Local ODBCDatasource" /f "seed_disconn.dat" /i "seed_disconn.inp" /d $Tableowner /Z Y /l implog.log For example: dataimp /u DBA /p SIEBEL12 /c "SEAW Local Db default instance" /f "D:FS Build4_Final seed_disconn.dat" /i "D:FSBuild4_Finalseed_disconn.inp" /d siebel /Z Y /l implog.log Once dataimp command is done, a message will be displayed in the following format showing the details of the tables and rows that were affected: TOTAL TABLES: 39 TOTAL ROWS PROCESSED: 167 TOTAL ROWS FAILED: 0 TOTAL ROWS SUCCEEDED: 167 ELAPSED TIME: 2.219s Disconnecting from the database Adding the Mobile Search Administration Screen You must add the Mobile Search Administration screen for each application project in Siebel Tools. NOTE: The Mobile Search Administration screen has already been added for the Siebel Call Center application. To add the Mobile Search Administration screen 1 Connect to Siebel Tools. 2 From the Object Explorer, expand the Application object type. 3 Select the application in the Object Explorer, and note the project to which the application belongs. 4 Lock the application project. 5 From the Object Explorer, expand the Application object type. 6 Select Screen Menu Item.
  • 50. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 50 7 Choose Edit, and then New Record, and use the following information to define the object properties: For more information about installing and configuring the Disconnected Search Module to enable Siebel Mobile Search, see Siebel Search Administration Guide on the Siebel Bookshelf at http:// www.oracle.com/technology/documentation/siebel.html. Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 422 The following sections contain procedures for making the configuration changes needed in order to implement ACR 422. For more information about accessibility enhancements, see Accessibility Guide for Siebel Business Applications on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html. Use the following procedure to enable screen readers to read out the applet summary for an application. This is a user property based on the respective XML for an application. To allow screen readers to read out the applet summary for an application 1 Navigate to Object Explorer in Siebel Tools. 2 Navigate to View > Options, and click the Object Explorer tab. 3 Unselect Application Object, select it again to add all of the child objects to the Object Explorer, and click OK. 4 Click Application, and query for the Application Names listed in the following table: Property Description Screen This should be set to Search Mobile Admin View Screen. Sequence Use Screen View Sequence Editor to determine the sequence of views. Do not edit the Sequence property of the Screen View Object manually. See Configuring Siebel Business Applications for defining Sequence for Screen View Objects. Text - String Reference This should be set to SBL_ADMINISTRATION_-_MOBILE_SEARCH. New/ Changed Name Application User Property Value SIA SIF File Name HOR SIF File Name Changed Siebel Universal Agent AccessibilityXMLF ileName Accessibility_Callce nter.xml Accessibility_Callce nter_SIA.sif Accessibility_Callc enter_HOR.sif Changed Siebel eMarketing AccessibilityXMLF ileName Accessibility_eMark eting.xml Accessibility_eMark eting_SIA.sif Accessibility_eMa rketing_HOR.sif Changed Siebel eSales AccessibilityXMLF ileName Accessibility_eSales .xml Accessibility_eSale s_SIA.sif Accessibility_eSal es_HOR.sif
  • 51. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 51 5 Click the '+' sign and select 'Application User Property'. 6 Lock the object, right-click and select New Record. 7 Add the User Properties listed in the preceding table. 8 Save the changes. Enabling Screen Readers to Read MVGs and Pick Applets for Calendar, Calculator, and MVG Use the following procedure to enable screen readers to read out the MVG and Pick Applet for Calendar, Calculator, and MVG. After these changes have been made, screen readers will read out a Calendar Pick Applet as shown in the following example: Start Date: 25/07/2007 Calendar Icon. To enable screen readers to read out the MVG and Pick Applet for Calendar, Calculator, and MVG (Symbolic Strings) 1 Navigate to Object Explorer in Siebel Tools. 2 Navigate to View > Options, and click the Object Explorer tab. 3 Select the Symbolic Strings Object and click OK to add the Symbolic Strings object to Object Explorer. 4 Click on Symbolic Strings and query for 'Current String Value' as 'Input'. 5 Lock the object. 6 Make the following changes, as detailed in the following table: a For SBL_CALCULATOR_ICON_ALT_TXT, change 'Current String Value' to 'Calculator'. Changed Siebel eService AccessibilityXMLF ileName Accessibility_eServi ce.xml Accessibility_eServ ice_SIA.sif Accessibility_eSer vice_HOR.sif Changed Siebel Public Sector AccessibilityXMLF ileName Accessibility_Public Sector.xml Accessibility_Public Sector_SIA.sif Accessibility_Publi cSector_HOR.sif Changed Siebel Sales AccessibilityXMLF ileName Accessibility_Sales. xml Accessibility_Sales _SIA.sif Accessibility_Sale s_HOR.sif Changed Siebel Service AccessibilityXMLF ileName Accessibility_Servic e.xml Accessibility_Servic e_SIA.sif Accessibility_Serv ice_HOR.sif New/ Changed Project Name Value SIA SIF File Name HOR SIF File Name Changed Symbolic Strings SBL_CALCULATOR_IC ON_ALT_TXT Calculator SymbolicStrings_SI A.sif SymbolicStrings_H OR.sif Changed Symbolic Strings SBL_CALENDAR_ICON _ALT_TXT Calendar SymbolicStrings_SI A.sif SymbolicStrings_H OR.sif Changed Symbolic Strings SBL_EDIT_ICON_ALT_ TXT Pick Applet SymbolicStrings_SI A.sif SymbolicStrings_H OR.sif New/ Changed Name Application User Property Value SIA SIF File Name HOR SIF File Name
  • 52. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 52 b For SBL_CALENDAR_ICON_ALT_TXT, change 'Current String Value' to 'Calendar'. c Save the changes. d In Symbolic Strings, query for 'Current String Value' as 'Select'. e For SBL_EDIT_ICON_ALT_TXT, change 'Current String Value' from Select to 'Pick Applet'. f Save the changes. To enable screen readers to read out the MVG and Pick Applet for Calendar, Calculator, and MVG (Bitmaps) 1 Navigate to Object Explorer in Siebel Tools. 2 Click on Bitmap Category and query for 'HTML Control Icons'. 3 Lock the HTML Control Icons object. 4 Navigate to Bitmap (child object) and query for 'CALENDAR_ ICON' and CALCULATOR_ICON. 5 Change the 'Alt Text' value to 'Calendar' and 'Calculator' respectively, as shown in the following table: 6 Save the changes. 7 In HTML Control Icons query for ' EDIT_ICON' and change the Alt Value to 'Pick Applet', as shown in the preceding table. 8 Save the changes. Creating Keyboard Shortcuts for Navigation Use the following procedures to provide shortcut keys for navigation. To provide shortcut keys for navigation (symbolic strings) 1 Navigate to Object Explorer in Siebel Tools. 2 Navigate to View > Options, and click the Object Explorer tab. New / Changed Bitmap Category Bitmap Alt Text Value Description SIA SIF File Name HOR SIF File Name Changed HTML Control Icons CALENDAR_ ICON Calendar Change the Alt text from "Input" to Calendar. HTMLControlIcon s_SIA.sif HTMLControlIcon s_HOR.sif Changed HTML Control Icons CALCULATOR_ICON Calculator Change the Alt text from "Input" to Calculator. HTMLControlIcon s_SIA.sif HTMLControlIcon s_HOR.sif Changed HTML Control Icons ICON_SELECT Pick Applet Change the Alt text from "Select" to Pick Applet. HTMLControlIcon s_SIA.sif HTMLControlIcon s_HOR.sif
  • 53. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 53 3 Select Symbolic Strings Object and click OK to add the Symbolic Strings object to Object Explorer. 4 Lock the 'Symbolic Strings' project. 5 Right-click and click New Record. 6 Add the new records listed in the following table: Table 7 lists some of the keyboard shortcuts available with ACR 422, and the procedures in the section that follows describe how to add these keyboard shortcuts. New/ Changed Project Name Current String Value SIA SIF File Name HOR SIF File Name New Symbolic Strings SBL_CTRL_+_ALT_+_] Ctrl + Alt + ] SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif New Symbolic Strings SBL_CTRL_+_ALT_+_[ Ctrl + Alt + [ SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif New Symbolic Strings SBL_CTRL+SHIFT+B Ctrl+Shift+B symstr_columnsdisplay ed_SIA.sif symstr_columnsdisplaye d_HOR.sif New Symbolic Strings SBL_CTRL+, Ctrl+, SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif New Symbolic Strings SBL_CTRL+. Ctrl+. SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif New Symbolic Strings SBL_ALT_G ALT+G SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif New Symbolic Strings SBL_ALT_U ALT+U SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif New Symbolic Strings SBL_ALT_W ALT+W SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif Table 7. Keyboard Shortcuts Command Action Accelerator Key Sequence Description SIA SIF File Name NextApplet Next Applet Ctrl + Alt + ] Ctrl+Alt+221 Shifts focus to the first anchor of the next applet CmdNextApplet_SIA.sif PrevApplet Previous Applet Ctrl + Alt + [ Ctrl+Alt+219 Shifts focus to the first anchor of the previous applet CmdPreviousApplet_SIA.sif Refine Query (SWE) N/A Alt+G Alt+G N/A CmdRefineQuery_SIA.sif First Page (SWE) N/A Alt+U Alt+U N/A CmdFirstPageSWE_SIA.sif Last Page (SWE) N/A Alt+W Alt+W N/A CmdLastPageSWE_SIA.sif
  • 54. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 54 Creating Keyboard Shortcuts for Commands Use the following procedures to provide keyboard shortcuts for commands. To provide a keyboard shortcut for the NextApplet command 1 Navigate to Object Explorer in Siebel Tools. 2 Navigate to View > Options, and click the Object Explorer tab. 3 Select the 'Command' object and click OK toadd the Command Strings object to Object Explorer. 4 Click the Command object on Object Explorer and query for the 'NextApplet' command. 5 Lock the object. 6 Click the '+' sign in Object Explorer and choose 'Accelerator'. 7 In 'Display Name - String Reference', provide the newly created Symbolic String or in 'Display Name' provide 'Ctrl + Alt + ]'. 8 In the 'Key Sequence' field, change the value to 'Ctrl+Alt+221'. To provide a keyboard shortcut for the PrevApplet command 1 Click the Command object on Object Explorer and query for the PrevApplet command. 2 Lock the object. 3 Click the '+' sign in Object Explorer and choose 'Accelerator'. 4 In the Display Name - String Reference' field, enter the newly created Symbolic String or in the Display Name field, enter 'Ctrl + Alt + ['. 5 In the 'Key Sequence' field, change the value to 'Ctrl+Alt+219'. To provide a keyboard shortcut for the RefineQuery[SWE] command 1 Click the Command object in Object Explorer and query for the Refine Query[SWE] command. 2 Lock the object. 3 Click the '+' sign in Object Explorer and choose 'Accelerator'. 4 Copy the Record Name '2'. Name the New Record '3'. 5 In the Display Name field, enter 'Alt+G'. Columns Displayed (SWE) N/A Ctrl+Shift+B Ctrl+Shift+B N/A CmdColumnsDisplayed_SIA.sif NextApplet Next Applet Ctrl + Alt + ] Ctrl+Alt+221 Shifts focus to the first anchor of the next applet CmdNextApplet_SIA.sif Table 7. Keyboard Shortcuts Command Action Accelerator Key Sequence Description SIA SIF File Name
  • 55. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 55 6 In the Key Sequence field, change the value to 'Alt+G'. To provide a keyboard shortcut for the FirstPage command 1 Click on Command object in Object Explorer and query for the First Page (SWE) command. 2 Lock the object. 3 Click the '+' sign in Object Explorer and choose 'Accelerator'. 4 Copy the Record Name '2'. Name the New Record '3'. 5 In the Display Name field, enter 'Alt+U'. 6 In the Key Sequence field, change the value to 'Alt+U'. To provide a keyboard shortcut for the LastPage (SWE) command 1 Click on Command object in Object Explorer and query for 'Last Page (SWE)' Command. 2 Lock the object. 3 Click on '+' sign in Object Explorer and choose 'Accelerator'. 4 Copy the Record Name '2'. Name the New Record '3' 5 In the Display Name field, enter 'Alt+W'. 6 In the Key Sequence field, change the value to 'Alt+W'. To provide a keyboard shortcut for the Columns Displayed (SWE) command 1 Click on Command object on Object Explorer and query for 'Columns Displayed (SWE)' Command. 2 Lock the object. 3 Click on '+' sign in Object Explorer and choose 'Accelerator'. 4 Copy the Record Name '1'. Name the New Record '2' 5 In the Display Name field, enter 'Ctrl+Shift+B'. 6 In the Key Sequence field, change the value to 'Ctrl+Shift+B'. To provide a keyboard shortcut for the Previous Record (SWE) command 1 Click on Command object on Object Explorer and query for 'Previous Record (SWE)' Command. 2 Lock the object. 3 Click on '+' sign in Object Explorer and choose 'Accelerator'. 4 Copy the Record Name '2'. Name the New Record '3'. 5 In Display Name field, enter 'Ctrl+,'. 6 In the Key Sequence field, change the value to 'Ctrl+,'.
  • 56. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 56 To provide a keyboard shortcut for the Next Record (SWE) command 1 Click on Command object on Object Explorer and query for 'Next Record (SWE)' Command. 2 Lock the object. 3 Click on '+' sign in Object Explorer and choose 'Accelerator'. 4 Copy the Record Name '2'. Name the New Record '3'. 5 In the Display Name field, enter 'Ctrl+.' 6 In the Key Sequence field, change the value to 'Ctrl+.' Providing Default Focus for Search Center The following section details the changes that are required for the search applet in order to provide a default focus for the "Search" option provided in the Siebel application. Use the following procedure to provide a default focus for Search. To provide a default focus for Search 1 Navigate to Object Explorer in Siebel Tools. 2 Navigate to Applet. 3 Query for "Search lookin" and lock it. 4 Enter "Search" in the Title field. 5 Make sure that the proper Symbolic String has been selected. To add the DefaultFocus User Property 1 Navigate to Object Explorer in Siebel Tools. 2 Navigate to Applet. 3 Query for "Search lookin". 4 Navigate to Applet User Property. New / Changed Applet Name Title Description SIA SIF File Name HOR SIF File Name Changed Search lookin Search Provides a title to the applet for screen readers to read out. AppletSearchlookin_SIA.sif AppletSearchlookin_HOR.sif
  • 57. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 57 5 Add the DefaultFocus user property, as described in the following table. NOTE: The DefaultFocus user property can be applied for any form applet where the user requires a default focus. Creating the View Info Command The following procedure explains how to create the View Info command. To create the View Info command 1 Navigate to Object Explorer in Siebel Tools. 2 Navigate to Command and lock the "Command" project. 3 Create a New Command named "View Info" with project "Command" as the project, using the values detailed in the following table: ■ NAME="ViewInfo" ■ METHOD="ViewInfo" ■ TARGET="SI Plus" ■ DISPLAY_NAME_-_STRING_REFERENCE="SBL_DOES_NOT_MATTER-1004225828-03I" 4 Add a new Accelerator to the Command for the required Key Combination with the following values: ■ NAME="1" ■ BROWSER_PLATFORM="All" ■ DISPLAY_NAME_-_STRING_REFERENCE="SBL_DOES_NOT_MATTER-1004225828-03I" ■ INACTIVE="N" New / Changed Applet Name Applet User Property Value Description SIA SIF File Name HOR SIF File Name Changed Search lookin DefaultFocus SearchFor Added the user property to setthe default focus AppletSearchlo okin_SIA.sif AppletSearchlookin_H OR.sif Command Project Action Accelerator Key Sequence Description SIA SIF File Name HOR SIF File Name View Info Command ViewInfo Ctrl + Alt + Z Ctrl + Alt +Z A new shortcut key that generates a dialog box that contains ViewName, View Summary and Applet Names CmdViewInf o_SIA.sif CmdViewInf o_HOR.sif Sub-View Tab (SWE SI) SWE N/A Ctrl + Alt + V Ctrl +Alt +V N/A CmdSubVie wTab_SIA.si f CmdSubVie wTab_HOR.s if
  • 58. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 58 ■ KEY_SEQUENCE="Ctrl+Alt+Z" NOTE: Although it is not mandatory, it is important that you enter“Does not matter” as the value for the Display Name or Caption field. 5 Add a new Symbolic String if required. 6 Add the required Key Combination. 7 Navigate to Menu, and create a new Menu Item (Hidden) under the menu used by your application, using the following values: (For example, Siebel Universal Agent uses Generic Web Menu.) ■ Name="Hidden-View Info ■ Position=8.39 ■ Command = "ViewInfo" ■ Caption="Does not matter" 8 Associate this menu item to the newly created command object. For more information about shortcuts, refer to other shortcuts such as NextApplet within Siebel Tools. Enabling Screen Readers to Read Out the Check Box “HTML Flag” as HTML The following procedure allows screen readers to read out the check box “HTML Flag” as HTML. By default, it reads as Public. To make this change, you can also import the Applet_CommPackageResponse_SIA.sif file. For information about how to import .sif files, see “Importing SIF Files” on page 65. To enable screen readers to read out the check box "HTML Flag" as HTML 1 Open Siebel Tools, and navigate to applet "Comm Package Response Form Applet". 2 Right-click, and select the "Edit web layout" menu item. 3 Focus on the HTML template check box 4 Change the control name from "Public" to "HTML Flag". Resolving an Error Generated When Creating New Records Within the Leads Screen Use the following procedure to resolve an error message that occurs when users are creating new records under the Leads screen, so that users are not able to see any case records in the Pick Cases MVG. To make this change, you can also importthe PUBLeadListCaseMvgApplet.sif, PUBLeadsList.sif, PUBLeadsListApplet.sif, and CaseMvg.sif files. For information about how to import .sif files, see “Importing SIF Files” on page 65. To resolve an error message generated in the Leads screen 1 Open Siebel Tools, and navigate to the "PUB Lead List Case Mvg Applet" applet.
  • 59. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 59 2 Lock the object. 3 Navigate to Applet Web Template. 4 Add one more Web Template Item for Base. 5 Navigate to the "PUB Leads List Applet" applet and lock it. 6 Click Edit to create a web template and add the necessary controls, along with SAVE and CANCEL buttons. Making the Help System Accessible for Screen-Reader Users The following procedure makes the help system accessible for screen-reader users. It adds a topic to the Siebel iHelp system that describes accessibility features and how to use them, and it also ensures that the iHelp system is available on each home page of the Siebel application. To make these changes, you can also import the Accessibility_symbolicString.sif, CCLoginPage_HOR.sif, CCLoginPage_SIA.sif, DotComPage_HOR.sif, and DotComPage_SIA.sif files. For information about how to import .sif files, see “Importing SIF Files” on page 65. 1 Add a symbolic string called SBL_ACCESSIBILITY. 2 Add a web page item called AccessibilityButton in the Web Page: DotCom Page Container eService (Framed), locking the project "eApp". 3 Add another web page item called AccessibilityButton in the Web Page: CC Login Page (Login Only). Generating HTML Summary Attributes for All List Applets The following changes need to be made for Generating HTML SUMMARY attributes for all list applets. The default tag text should be set to the applet header name. Add TITLE or LABEL for each table entry (all HTML form elements). Row and column headers must be identified as required by OGHAG TABLE-1 and TABLE-2. Adding a row title for each row in data table (Suggestion: this could be the first displayed data column in the applet display. Ideally the customer can select which column can be used as the index for the row title through configuration). NOTE: The list applet row ids are not available out of the box. Users can add them if they want. The first data column will be used as the default rowid when there is no row id provided in the "RowId" applet user property. There are two options available to users to select different rowid. Option 1: Users need to contact the administrator to define the "RowId" user property. To do this, a new applet user property called "RowId" has to be added for the list applet. The "RowId" value should be equal to one of the displayed column name. For example, in the Contact list applet, if 'Last Name' has been selected as the row header, the user property value has to be set to "RowId = Last Name". Here "Last Name" is the list column name. Option 2: Users can select the column displayed window and select some other column as the first column for the list applet. The newly-selected column will become the rowid. Lock the particular applet that needs to be changed.
  • 60. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 60 Providing a New Key Combination for the Next and Previous Record Commands NOTE: The tables that follow this procedure provide more information about the fields that you are changing. To provide key combinations for Next Record and Previous Record 1 Navigate to Object Explorer in Siebel Tools. 2 Navigate to View > Options, and click the Object Explorer tab. 3 Select the 'Command' object and click OK toadd the Command Strings object to Object Explorer. 4 Within Object Explorer, click the Command object and query for 'Previous Record(SWE)' Command. 5 Lock the object. 6 Click the '+' sign in Object Explorer and choose 'Accelerator'. 7 Change the 'Display Name' from 'Ctrl+,' to 'Alt+,' 8 In the 'Key Sequence' field, change the value to Alt+0xBC. 9 Within Object Explorer, click the Command object and query for 'Next Record(SWE)' Command. 10 Lock the object. 11 Click the '+' sign in Object Explorer and choose 'Accelerator'. 12 Change 'Display Name' from 'Ctrl+.' to 'Alt +.' 13 In the 'Key Sequence' field, change the value to Alt+0xBE. New/ Changed Project Name Current String Value HOR SIF File Name SIA SIF File Name New Symbolic Strings SBL_ALT+, Alt+, symbolistring_Next_Prev_H OR.sif symbolistring_Next_Prev_S IA.sif New Symbolic Strings SBL_ALTL+. Alt+. symbolistring_Next_Prev_H OR.sif symbolistring_Next_Prev_S IA.sif Command Project Accelerator Key Sequence SIA SIF File Name HOR SIF File Name Next Record(SWE) Command Alt +. Alt+0xBE Next_Prev_SIA.sif Next_Prev_HOR.sif Previous Record(SWE) Command Alt +, Alt+0xBC Next_Prev_HOR.sif Next_Prev_HOR.sif
  • 61. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 61 Providing Alt Text for Bullets In Recent Records, the bullets need to have alt text provided. To make this change, import the orangebullet_HOR or orangebullet_SIA.sif files as detailed in the following table. For information about how to import .sif files, see “Importing SIF Files” on page 65. Enabling or Disabling the Confirmation Message on Page Refresh The procedure in the following section describes how to enable or disable the confirmation message upon page refresh. To make this change, you can also import .sif files. To do so, import ConfirmationMessage_SIA.sif and ConfirmationMessage_HOR.sif. For symbolic strings, import symstr_confirmationmessage_SIA.sif and symstr_confirmationmessage_HOR.sif. For information about how to import .sif files, see “Importing SIF Files” on page 65. To enable or disable the confirmation message upon page refresh 1 Log into the application using /editseeddata (for Siebel Developer Web Client) for the local database or dedicated database (for the master database, the Add button is enabled by default). 2 Navigate to Administration - Data > List Of Values Explorer, and add the new LOV types mentioned in the following table: New/ Changed Project Name Current String Value HOR SIF File Name SIA SIF File Name Changed Symbolic Strings SBL__IMG_SRC__IMAGES/ CHEVRON_SM.GIF__ALIGN __RIGHT__BORDER__0 <IMG SRC="images/ orange_bullet.gif" align="right" border="0" alt="" > orangebullet_HOR.sif orangebullet_SIA.sif New/Changed Project Value Description New Symbolic Strings Accessibility Create a new Symbolic String for Accessibility Project for the "Confirmation Message" User Preference New Symbolic Strings Confirmation Message Create a new string for the Control Type Display Value Translate Multilingual Language Independent Code Order Language Name SWE_CONFIRMATION _MESSAGE TRUE Yes Yes TRUE 1 English-American SWE_CONFIRMATION _MESSAGE FALSE Yes Yes FALSE 2 N/A
  • 62. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 62 3 After you have added these changes, navigate to Screen > System Administration > List Of Values to view these changes in the repository. The following changes have been made to the User Preferences Business Component. The following table describes the new User Profile Confirmation Message Parameter Applet that has been added to support ACR 422. The following table describes the applet controls changes that have been implemented to support ACR 422. New/ Changed Name Project Business Component Static Type Field Type Value New Confirmation Message Picklist User Preference PickList Generic Yes Type SWE_CONFIRM_MESSAGE Name PickList Predefault Value Type SWE/Confirmation Message Confirmation Message Picklist TRUE DTYPE_TEXT New/ Changed Name Project Business Component Class Title New User Profile Confirmation Message Parameter Applet User Preferences User Preferences CSSFrameBase Accessibility Name Caption Field HTML Type Method Invoked Runtime Field Type Applet Title Accessibility N/A Text N/A N/A N/A ConfirmMssg Confirmation Message SWE/ Confirmation Message Text N/A Yes BC Field ExecuteQuery Go N/A MiniButtonQuery ExecuteQuery N/A N/A NewQuery Query N/A MiniButtonEdit NewQuery N/A N/A QueryAssistan t Query Assistant N/A MiniButtonQuery ShowQueryAssistant N/A N/A ResetRecord Reset N/A MiniButton ResetRecord N/A N/A SaveEditRecor d Save N/A MiniButtonEditNe w ExplicitWriteRecord N/A N/A UndoQuery Cancel N/A MiniButtonQuery UndoQuery N/A N/A WebEditTitle Accessibility N/A Label N/A N/A N/A
  • 63. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 63 The following table describes the view changes that have been added to support ACR 422. The following table describes the User Profile screen changes that have been added to support ACR 422. Resolving an Error Message Within Under Diseases > Cases 3LNV Users are receiving error messages while creating new records under Diseases > Cases 3LNV. This is specific to SIA. Use the following procedure to resolve this issue. To resolve an error message within Cases 3NLNV 1 Add the 'Edit' template to 'PUB Disease Case List Applet'. 2 Make sure that the Execute Query, WriteRecord, UndoQuery, UndoRecord, and Query Assistant controls are present on the applet template. NOTE: Edit template uses 'Applet List Edit (Edit/New/Query)' as the web template. Resolving an Error Where Commands Are Executed Before Users Click Enter Users are encountering an issue where before they click Enter on a menu item in the Show dialog box, the command is executed. To resolve an error in which commands are executed before users click Enter in the Show dialog box 1 Navigate to Object Explorer in Siebel Tools. 2 Navigate to View > Options, and click the Object Explorer tab. New/Changed Name Project Business Object Visibility Applet Type New User Profile Confirmation Message Parameter View User Preferences User Preferences User Profile Confirmation Message Parameter Applet New/Changed Name View Type Visibility Applet Type New User Profile Confirmation Message Parameter View User Profile Confirmation Message Parameter View Aggregate View User Profile Confirmation Message Parameter Applet New/Changed Name Project Web Template SIF File New PUB Disease Case List Applet PUB HLS Bio Terrorism Edit Disease_Case_SIA.sif
  • 64. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 64 3 Select the Symbolic Strings Object and click OK to add the Symbolic Strings object to Object Explorer. 4 Lock the 'Symbolic Strings' project. 5 Right-click and select 'New Record'. 6 Add the new records mentioned in the following table. To implement the NextPage and PreviousPage commands 1 Navigate to Object Explorer in Siebel Tools. 2 Navigate to View > Options, and click the Object Explorer tab. 3 Select the 'Command' object and click OK toadd the Command Strings object to Object Explorer. 4 Within Object Explorer, click the Command object and query for the 'NextPage' command. 5 Lock the object. 6 Within Object Explorer, click the '+' sign and choose 'Accelerator'. 7 For 'Browser Platform' - Extended, in 'Display Name - String Reference', provide the newly created Symbolic String or in 'Display Name' provide 'SBL_ALT+CTRL+DOWN'. 8 In the 'Key Sequence' field, change the value to 'Alt+Ctrl+Y', as shown in the following table: 9 Within Object Explorer, click the Command object and query for the 'PreviousPage' command. 10 Lock the object. 11 Within Object Explorer, click the '+' sign in and choose 'Accelerator'. 12 For 'Browser Platform' - Extended, in 'Display Name - String Reference', provide the newly created Symbolic String or in 'Display Name' provide 'SBL_ALT+CTRL+UP'. 13 In the 'Key Sequence' field, change the value to 'Alt+Ctrl+L'. New/Changed Project Name Value New Symbolic Strings SBL_ALT+CTRL+Y Alt+Ctrl+Y New Symbolic Strings SBL_ALT+CTRL+L Alt+Ctrl+L Command Action Accelerator Key Sequence Description NextPage Next Page Alt + Ctrl + Y Alt+Ctrl+Y Navigate to the Next Page PreviousPage Previous Page Alt + Ctrl + L Alt+Ctrl+L Navigate to the Previous Page
  • 65. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 65 Resolving an Error Encountered While Creating a New Record in the Identities Form Applet The information in the following section resolves an issue where users encounter a problem within the Immigration contacts screen > Identities view when they try to create a new record under the Identities form applet. To make this change, you can follow the procedure below, or you can import the PublicSector_Controls.sif file. For information about how to import .sif files, see “Importing SIF Files” on page 65. To resolve this error message, change the HTML Type property of the DeleteRecord control from MiniButton to MiniButtonEdit for the PUB Immigration Identity Form Applet, the PUB Lead Form Applet, the HLS Group Form Applet, the Disease Form Applet, the FINS Application Entry Applet — ACAPS, and the HLS Medication Form Applet. Use the following bulleted list information group for each applet as a reference point. ■ Applet: 'PUB Immigration Identity Form Applet' ■ Template: Edit ■ Additions: UndoRecord and WriteRecord controls ■ Applet: PUB Lead Form Applet ■ Template: Edit ■ Additions: WriteRecord (save) control. UndoRecord (cancel) does not need to be added as the 'DeleteRecord' control is already present on the template. ■ Applet: "HLS Group Form Applet", "Disease Form Applet" and "FINS Application Entry Applet - ACAPS" ■ Template: Edit ■ Additions: 'WriteRecord' control. ■ Applet: HLS Medication Form Applet ■ Template: Edit NOTE: For the HLS Group Form Applet, Disease Form Applet, and FINS Application Entry Applet, access these applets from under the Application screen and not from the BCM Applications screen. The necessary changes need to be made under the configuration context of Siebel Public Sector for these applets, because they are also used by the FINS application. Resolving an Issue Where Users Are Unable to Query for Evidence Parent Information The following procedure resolves a problem where under Evidence screen> Evidence parent, users are unable to query for User Parent, and they receive an error message. To make this change, you can also import the PublicEvidencePickApplet_SIA.sif file. For information about how to import .sif files, see “Importing SIF Files” on page 65. Add 'Popup Query' template to the 'PUB Evidence Pick Applet' with appropriate controls [ExecuteQuery and CancelQuery] placed on it. Importing SIF Files The following procedure describes how to import .sif files.
  • 66. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 66 To import SIF files 1 Lock the particular object /project that needs to be changed. 2 Navigate to Tools > Import from Archive and select the related .sif file 3 Click OK, and follow the instructions in the wizard to implement the changes. 4 Stop the servers, compile the objects or projects into respective .sif file and then restart the servers. Configuration Changes for Adding the Applet Summary for New or Customized Applets The following sections contain configuration changes that you must make to add the applet summary for new or customized applets. You must import .sif files for table changes, apply the DLL, import seed data, and import the Accessibility Project .sif files. The necessary changes are detailed in the following sections: ■ Importing SIF Files for Table Changes ■ Applying the DDL ■ Importing Seed Data ■ Importing the Accessibility Project SIF Files Importing SIF Files for Table Changes The procedure in the following section describes how to add the applet summary for customized or new applets. To import the SIF file for table changes 1 Lock the (Table Common) project by navigating to the Project Tab and checking the "Locked" check box. 2 Import the Table archive file "Accessibility_Table.sif" table archive file. 3 Click Yes when the dialog box displays and asks “This operation should only be performed while connected to your local database. Would you like to continue anyway?” 4 Select the "Accessibility_Table.sif" file. 5 Select the first option "Overwrite the object definition in the repository" in the Conflict resolution section of the import wizard view. 6 Review the conflicting objects to see if the new or modified columns appear. The import log is stored at Siebeltoolstempimportlog.txt Applying the DDL The procedure in the following section describes how to apply the DDL.
  • 67. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 67 To apply the DDL 1 Select the table or tablesyou want to apply tothe physical database and press Apply/DDL button (option > Apply). 2 For a single table, select the current row option in Tables (Apply Schema Window). 3 For more than one table, select the Choose Current Query option. 4 For the Accessibility project, select the S_ACC_VIEW_APPL table and current row option. 5 Make the following changes depending upon which database you are using: a For MSSQL, enter the database users, the database user password, and the correct ODBC data source. b For Oracle, enter the table space, the index space, the database user, the database user password, and the correct ODBC data source. c For IBM DB2, enter the table space, the 16K table space, the 32K table space, the index space, the database users, the database user password, and the correct ODBC data source. 6 After entering in the database information, click the Apply button. 7 Verify that the required changes have been applied by selecting count(*) from S_ACC_VIEW_APPL. The query should result in 0 records. Importing Seed Data The procedure in the following section describes how to import seed data. To import seed data 1 Copy dat files into a work-area folder. 2 Run the following command for importing seed data: (For HOR applications, use the HOR .dat file.) siebsrvrrootBINdataimp /u <UID> /p <PWD> /f <HOR DAT file> /l dataimp_HORseed.log /c <ODBC > /d <TABLEOWNER > /q -1 /e n /t n /x R /n 100 /h log (For SIA applications, use the SIA .dat file.) siebsrvrrootBINdataimp /u <UID > /p <PWD> /f <SIA DAT file> /l dataimp_SIAseed.log /c <ODBC > /d <TABLEOWNER > /q -1 /e n /t n /x R /n 100 /h log For example: C:21011siebsrvrBINdataimp /u MMRAO /p ****** /f HACR422.dat /l dataimp_ORA21013.log /c ORA21013 /d ORA21013 /q -1 /e n /t n /x R /n 100 /h log 3 When prompted for the table name, enter S_ACC_VIEW_APPL. 4 Check the log files for any errors, and check S_ACC_VIEW_APPL for the data imported.
  • 68. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 68 Importing the Accessibility Project SIF Files The following section describes how to import the Accessibility Project .sif files. To import the .sif files provided for ACR 422 1 Create the “Accessibility” project and import the .sif. 2 Import AccProject.sif. For a list of files that this .sif contains, see “Changes to SIF Files in ACR 422” on page 70. 3 Import AdminScreen.sif and merge the file. The AdminScreen.sif file contains the modified System Administration Screen. For the list of changes to this screen, see “Changes to SIF Files in ACR 422” on page 70. 4 Add the following new LOV types and values: 5 Add the following views to the application and associate responsibility: ■ Accessibility Applet Attributes View ■ Accessibility View Attributes View 6 Run the perl script using the procedures detailed in Step a through Step c. Note the following prerequisites for running the perl script: ■ Perl 5.8 or higher (http://www.activestate.com/Products/activeperl/index.mhtml) ■ Perl module: DBI (http://dbi.perl.org/) ■ Perl module: XML: Generator (http://search.cpan.org/~bholzman/XML-Generator-1.01/ Generator.pm). Install Perl modules: DBI (DBD::ODBC) and XML::Generator from PPM (Perl Package Manager). a Open a command line window and navigate to the folder where the three scripts reside (genAccessibilityXML.pl, app_tree.pl, sqlstmt.pl). b Execute the script with the following command: ❏ For all databases, change Oracle in DBI->Connect(“ “) in app_tree.pl and genAccessibilityXML.pl to ODBC. Type Value ACC_ATTRIB_TYPE Summary ACC_ATTRIB_TYPE Label ACC_LOCALE ENU
  • 69. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 69 ❏ The following step applies only to the MSSQL database: After the following lines in app_tree.pl script: #Connect to DB ################################################# $dbh = DBI->connect("dbi:ODBC:$ODBCConnection", $userid, $passwd) || die $DBI::errstr; ################################################# Add the line $dbh->{odbc_SQL_ROWSET_SIZE} = 2; Execute the script with the following command: SYNTAX: perl genAccessibilityXML.pl "<Application Name>" <LOCALE_CODE> <CONNECTSTRING/TABLEOWNER> <USERID> <PASSWD> c Once the script is run an xml file will be generated, copy this xml in the following location: SiebelsessiebsrvrbinLANG_FOLDER folder. The LANG_FOLDER should be substituted by ENU for English, and so forth. The name of the XML File should be same as the value mentioned for the Application user property 'AccessibilityXMLFileName' for that application. NOTE: The preceding steps help the users provide the summary for a new or a customized applet. A UI will be created in which the user has to enter the summary for a particular applet. This in turn will be placed into the xml file that will be generated after the perl script is run. Users can use this xml file to allow screen readers to read out the applet summary. Workaround for Accessibility Applets You must perform the following workaround procedure in order to be able to implement ACR 422. These changes must be made to the Accessibility Applet Attributes List Applet and the Accessibility Applet Attributes Form Applet. This workaround has been added to address CR 12-1Q8YZDL, CR 12- 1Q6XXPY, and CR 12-1Q6XXOX. For both of these applets, use the following procedure: 1 Right-click, and select Applet > Edit Web Layout. 2 In the Controls/Column Pane, select EditList. 3 Uncheck the “Show mapped controls only” check box. 4 Drag and drop the “Position on Row” control. 5 Edit the “Position on Row” control’s properties by entering “ROW_OFF” for HTML Bitmap and “ROW_ON” for HTML Disabled Bitmap. 6 Save the applet.
  • 70. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 70 7 Drag and drop the GotoPreviousSet and GotoNextSet controls to their respective placeholders, and edit the properties using the values in the following table: 8 Save the applet. 9 From the drop-down list, select Edit. 10 Drag and drop the Save and Cancel buttons to their respective placeholders. 11 Save the applet. Changes to SIF Files in ACR 422 This section contains the list of changes to the .sif files provided for ACR 422. AccProject.sif The AccProject.sif file contains the following new objects: Business Components: ■ Accessibility Applet Attributes ■ Accessibility View Attributes Applets: ■ Accessibility Applet Attributes List Applet ■ Accessibility Applet Attributes Form Applet Business Objects: ■ Accessibility Applet Attributes ■ Accessibility View Attributes Views: ■ Accessibility Applet Attributes View ■ Accessibility View Attributes View Picklists: ■ Accessibility Applet Attribute PickList ■ Accessibility View Attribute PickList Control Property Value GotoPreviousSet HTMLBitmap RECNAV_PREVSET_ON GotoPreviousSet HTML Disabled Bitmap RECNAV_PREVSET_OFF GotoNextSet HTML Bitmap RECNAV_PREVSET_ON GotoNextSet HTML Disabled Bitmap RECNAV_PREVSET_OFF
  • 71. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 71 ■ Accessibility Locale PickList Symbolic Strings: ■ Accessibility ■ Applet Attributes ■ Attribute Type ■ View Attributes AdminScreen.sif The AdminScreen.sif file contains the following changes: ■ Accessibility Attributes (new category) ■ Accessibility Applet Attributes View (new view) ■ Accessibility View Attributes View (new view) Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 426 This topic contains information about how to configure and install ACR 426. Preinstallation Instructions for ACR 426 Before you begin your installation, change a parameter in tools.cfg file within Siebel Tools (Original: SymStrPrefix = X_) to SymStrPrefix = SBL_ Repository Configurations 1 Navigate to REPPATCH ACR426RepSeedFiles_v8113.zip and unzip to any location accessible by Siebel Tools. 2 In Siebel Tools, lock the following projects: ■ LS Medical Product Issue ■ LS Medical Product Issue (SSE) ■ Contact ■ Audit Trail ■ Table ProductComplaints ■ LS Medical Report ■ Product ■ Symbolic Strings
  • 72. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 72 ■ Bitmap ■ EIM ProductComplaints Applying Schema Changes As part of the ACR426 release, schema changes have been done on the database. The UnziplocationACR426RepositoryTableBaseTables.sif file has all the changes for the following: ACR 426 contains changes to the following existing table: ■ S_PRD_CMPLNT_LS ACR 426 contains the following new table: ■ S_EMDR_BATCH Use the following procedure to import tables. To import the Tables.sif file into the repository 1 Lock the Table ProductComplaints table. 2 Use the Import from Archive function within Siebel Tools to read this file and create the tables in the repository. Use the merge option while importing this file. 3 The tables have to be in the repository before creating this on the physical database. 4 Within Siebel Tools and query for the list of tables that were imported into the repository. 5 Click the Apply/DLL button to apply the changes to the physical database. Applying EIM Changes As part of the ACR426 release, EIM changes have been performed on the database. The UnziplocationACR426RepositoryTableEIMEIMTables.sif has all the changes for the following: EIMTables.sif contains the following new EIM table: ■ EIM_EMDR_BATCH EIMTables.sif contains changes to the following existing table: ■ EIM_PRD_CMP_LS Use the following procedure to import the EIMTables.sif file into the repository. To import the EIMTables.sif file into the repository 1 Lock the EIM ProductComplaints project. 2 Use the Import from Archive function within Siebel Tools to read this file and create the tables in the repository. Use the merge option while importing this file. 3 Within Siebel tools, query for the list of tables that were imported into the repository. 4 Click the Apply/DLL button to apply the changes to the physical database.
  • 73. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 73 Use the following procedure to import all of the SIF files. NOTE: Use the following option if you want Siebel Tools to merge the changes for all the existing components as well. However, if you have performed customizations, some user properties may clash. To import all of the SIF files 1 Rename UnziplocationACR426REPOSITORYimport.txt to import.bat, edit the file, and change the first four parameters related to database and Siebel Tools details. 2 Create a log folder in UnziplocationACR426REPOSITORY. 3 Run the import.bat file to import. 4 Check the logs to see if all of the files imported successfully, and reimport all of the objects that did not import successfully. 5 In Siebel Tools, compile all of the locked and updated projects. NOTE: The following procedure is an alternative to importing the SIF files. Use the following procedure if you want to perform manually configure the existing objects. To import the SIF files manually 1 Import the following new objects: ■ Import UnziplocationACR426REPOSITORYPick ListLS Medical Picklist Product Issue eMDR Acknowledgement RR.sif ■ Import UnziplocationACR426REPOSITORYPick ListLS Medical Picklist Product Issue eMDR Batch RR.sif ■ Import UnziplocationACR426REPOSITORYPick ListLS Medical Picklist Product Issue eMDR Status RR.sif ■ Import UnziplocationACR426REPOSITORYPick ListLS Medical Picklist Product Issue eMDR SubStatus RR.sif ■ Import UnziplocationACR426REPOSITORYBusiness ComponentLS Medical Product Issue RR eMDR Batch.sif ■ Import UnziplocationACR426REPOSITORYBusiness ComponentLS Medical Product Issue RR eMDR.sif ■ Import UnziplocationACR426REPOSITORYLinkLS Medical Product Issue RR eMDR Batch_Audit Trail Item 2.sif ■ Import UnziplocationACR426REPOSITORYLinkLS Medical Product Issue RR eMDR Batch_LS Medical Product Issue RR.sif ■ Import UnziplocationACR426REPOSITORYLinkLS Medical Product Issue RR_Contact.sif ■ Import UnziplocationACR426REPOSITORYLinkLS Medical Product Issue RR_LS Medical Product Issue RR eMDR Batch.sif
  • 74. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 74 ■ Import UnziplocationACR426REPOSITORYLink LS Medical Product Issue RR eMDR_LS Medical Product Issue RR eMDR Batch.sif ■ Import UnziplocationACR426REPOSITORYLink LS Medical Product Issue RR eMDR_Audit Trail Item 2.sif ■ Import UnziplocationACR426REPOSITORYLink LS Medical Product Issue RR eMDR_LS Medical PI Product.sif ■ Import UnziplocationACR426REPOSITORYLink LS Medical Product Issue RR eMDR_LS Medical Product Issue Attachment.sif ■ Import UnziplocationACR426REPOSITORYBusiness ObjectLS Medical Product Issue RR eMDR.sif ■ Import UnziplocationACR426REPOSITORYBusiness ObjectLS Medical Product Issue RR eMDR Batch.sif ■ Import UnziplocationACR426REPOSITORYBusiness ServiceCRMIntegCreatePISEBL782ToAERSSync.sif ■ Import UnziplocationACR426REPOSITORYBusiness ServiceGenesis Error Handler.sif ■ Import UnziplocationACR426REPOSITORYBusiness ServiceLS Siebel Product Issue.sif ■ Import UnziplocationACR426REPOSITORY Bitmap Category Urgency Flag Values.sif ■ Import UnziplocationACR426REPOSITORY Icon MapLS_ATTACHMENT.sif ■ Import UnziplocationACR426REPOSITORY Icon Map LS_CHECK.sif ■ Import UnziplocationACR426REPOSITORY Icon Map LS_URGENCY_FLAG.sif ■ Import UnziplocationACR426REPOSITORYIntegration ObjectsCRMIntegSEBLSIALSProductIssueInterface.sif ■ Import UnziplocationACR426REPOSITORYIntegration ObjectCRMIntegSEBLSIALSClinicalFaultMessage.sif ■ Import UnziplocationACR426REPOSITORYIntegration ObjectCRMIOSEBLSIALSProductIssueInternal.sif ■ Import UnziplocationACR426REPOSITORYAppletLS Medical Product Issue RR eMDR Batch Details List Applet.sif ■ Import UnziplocationACR426REPOSITORYAppletLS Medical Product Issue RR eMDR Batch List Applet.sif ■ Import UnziplocationACR426REPOSITORYAppletLS Medical Product Issue RR eMDR Batch Pick Applet.sif ■ Import UnziplocationACR426REPOSITORYAppletLS Medical Product Issue RR eMDR Report List Applet.sif ■ Import UnziplocationACR426REPOSITORYViewLS Medical My Product Issues RR eMDR Batch Audit View.sif ■ Import UnziplocationACR426REPOSITORYViewLS Medical My Product Issues RR eMDR Batch Details View.sif
  • 75. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 75 ■ Import UnziplocationACR426REPOSITORYViewLS Medical My Product Issues RR eMDR Report Attachment View.sif ■ Import UnziplocationACR426REPOSITORYViewLS Medical My Product Issues RR eMDR Report Audit View.sif 2 Manually add the following symbolic strings: Screen View New/ Modified? Name Current String Value Definition New SBL_LS_BATCH_# Batch # Batch # New SBL_LS_BATCH_AUDIT Batch Audit Batch Audit New SBL_LS_BATCH_DETAILS Batch Details Batch Details New SBL_LS_EMDR eMDR EMDR New SBL_LS_EMDR_BATCH eMDR Batch eMDR Batch New SBL_LS_EMDR_QUEUE eMDR Queue eMDR Queue New SBL_LS_EMDR_STATUS Transmission Status Transmission Status New SBL_LS_EMDR_SUB_STATUS eMDR Status eMDR Status New SBL_LS_FDA_STATUS FDA Status FDA Status New SBL_LS_INDIVIDUAL_TRANSMIT Individual Transmit Individual Transmit New SBL_LS_NOT_SELECTED Not Selected Not Selected New SBL_LS_REPORT_ATTACHMENTS Report Attachments Report Attachments New SBL_LS_REPORT_AUDIT Report Audit Report Audit New SBL_LS_TRANSMIT Transmit Transmit
  • 76. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 76 3 Do manual configuration for the existing "LS Medical Product Issue RR" Business Component: Single Value Fields New/Needs Modification? Name Join Column Calculate d Value Type Immediate Post PickList Validation No Copy New Area LIC LookupNa me("SR_A REA", [Area]) DTYPE_TEXT New Attach IIf (Count(At tachment) > 0, 1, 0) DTYPE_BOOL New Batch Id BATCH_I D DTYPE_ID New Batch Number eMDR Batch BATCH_ NUMBER DTYPE_TEXT Y LS Medical Picklist Product Issue eMDR Batch RR New FDA Acknowl edgeme nt FDA_AC KNOWLE DGE_CD DTYPE_TEXT Y LS Medical Picklist Product Issue eMDR Acknowled gement RR Modify Device Age >0 Modify Follow- Up Number Y New Follow- Up Number Read Only IIF ([Sub Report Type] = LookupVal ue("LS_M ED_CMPL NT_SUB_ REPORT_T YPE","Foll ow-up"), "N", "Y") DTYPE_BOOL Y New Individu al Transmit IIf ([Batch Number] IS NULL, 1, 0) DTYPE_BOOL Modify Parent Product Issue Report Num Y New Patient Sex LIC LookupNa me("FIN_ GENDER", [Patient Sex]) DTYPE_TEXT
  • 77. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 77 New Reopen Flag [Status]= LookupVal ue("LS_M ED_PI_ST ATUS_TYP E","Closed ") OR [Status]= LookupVal ue("LS_M ED_PI_ST ATUS_TYP E","Revie w Complete" ) DTYPE_TEXT Modify Report Number Y Modify Sub Report Type Y Modify Type of Report - Follow- up Flag Y New Urgency Flag IIF ( [eMDR Status] = 'Transmitt ed' AND [eMDR SubStatus ] <> 'Rejected' , Green, IIF( (Today() + SystemPr eference(" eMDR Deadline Threshold Value")) < [Report Deadline Date], Yellow, Red)) DTYPE_TEXT New eMDR Status EMDR_S TATUS_C D DTYPE_TEXT Y LS Medical Picklist Product Issue eMDR Status RR New eMDR SubStat us EMDR_S UB_STAT US_CD DTYPE_TEXT Y LS Medical Picklist Product Issue eMDR SubStatus RR Single Value Fields New/Needs Modification? Name Join Column Calculate d Value Type Immediate Post PickList Validation No Copy
  • 78. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 78 Pick Maps for the Batch Number Field New/Modified? Field Picklist Field New Batch Id Id New Batch Number Batch Number Pick Maps for the FDA Acknowledgement Field New/Modified? Field Picklist Field New FDA Acknowledgement Value Pick Maps for the eMDR Status Field New/Modified? Field Picklist Field New eMDR Status Value Pick Maps for the eMDR Substatus Field New/Modified? Field Picklist Field New eMDR SubStatus Value Join New/Needs Modification? Table Alias Outer Join Flag New S_EMDR_BATCH eMDR Batch Yes Join Specification for 'eMDR Batch' New/Needs Modification? Name Source Field Destination Column New Join Batch Id ROW_ID Multi Value Link New/Needs Modification? Name Auto Primary Destination Business Component Destination Link Use Primary Join New Attachment Default LS Medical Product Issue Attachment LS Medical Product Issue RR/ LS Medical Product Issue Attachment Y
  • 79. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 79 Business Component User Properties New/ Modified? Name Value Inactive New Field Read Only Field: Follow-Up Number Follow-Up Number Read Only N New Named Method 8 "EscalatePIToeMDRQueue", "SET", "RR Sub-Status", "LookupValue('LS_MED_RR_STATUS_CD', 'eMDR') "N New Named Method 9 "Transmit", "INVOKESVC", "LS Medical Product Issue RR", "Workflow Process Manager", "RunProcess", "'ProcessName'", "LS CRMIntegSEBLSIAProductIssueInsertOutbo undFlow", "'RowId'", "[Id] "N New Named Method 10 "Transmit", "SET", "eMDR Status", "LookupValue('LS_MED_RR_TRANS_STATU S', 'TRANSMITTED') "N New Named Method 11 "Transmit", "SET", "eMDR SubStatus", "LookupValue('LS_MED_RR_TRANS_SUB_S TATUS', 'NO RESPONSE') "N New Named Method 12 "UpdateeMDRStatus", "SET", "eMDR Status", "LookupValue('LS_MED_RR_TRANS_STATU S', 'TRANSMITTED') "N New Named Method 13 "UpdateeMDRStatus", "SET", "eMDR SubStatus", "LookupValue('LS_MED_RR_TRANS_SUB_S TATUS', 'NO RESPONSE') "N New Named Method 14 "EscalatePIToeMDRQueue", "SET", "eMDR Status", "IIf ([eMDR Status] IS NULL, LookupValue('LS_MED_RR_TRANS_STATUS ', 'NOT TRANSMITTED'), [eMDR Status]) "N New Named Method 15 "EscalatePIToeMDRQueue", "SET", "eMDR SubStatus", "IIf ([eMDR SubStatus] IS NULL, LookupValue('LS_MED_RR_TRANS_SUB_S TATUS', 'WORK IN PROGRESS'), [eMDR SubStatus]) "N
  • 80. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 80 New Named Method 16 "Transmit", "SET", "FDA Acknowledgement", """"N New Named Method 17 "UpdateeMDRStatus", "SET", "FDA Acknowledgement", """"N New On Field Update Set 3 "Sub Report Type", "Follow-Up Number Read Only", "IIF ([Sub Report Type] = LookupValue(""LS_MED_CMPLNT_SUB_REP ORT_TYPE"",""Follow-up""), ""N"", ""Y"") "N New On Field Update Set 4 "Sub Report Type", "Follow-Up Number", "IIF ([Sub Report Type] = LookupValue(""LS_MED_CMPLNT_SUB_REP ORT_TYPE"",""Initial""), """", [Follow-Up Number]) "N New On Field Update Set 5 "Type of Report - Follow-up Flag", "Sub Report Type", "IIF ([Type of Report - Follow- up Flag]='Y', LookupValue('LS_MED_CMPLNT_SUB_REP ORT_TYPE','Follow-up'), LookupValue('LS_MED_CMPLNT_SUB_REP ORT_TYPE','Initial')) "N New Status Locked Field 6 "eMDR Status", ""N New Status Locked Field 7 "eMDR SubStatus", ""N New Status Locked Field 8 "FDA Acknowledgement", ""N Modify Status Locked Field 2 "RR Status", "Submitted "N Business Component User Properties New/ Modified? Name Value Inactive
  • 81. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 81 4 Perform manual configuration for the "LS Medical Product Issue" Business Component: 5 Perform manual configuration for the existing "Contact" Business Component. Single Value Fields New/ Needs Modific ation? Name Join Column Calcul ated Value Type Immediate Post PickList Validati on No Copy New Area LIC Lookup Name(" SR_ARE A", [Area]) DTYPE_TEXT Modify FDA Reporta ble Y New Patient Sex LIC Lookup Name(" FIN_GE NDER", [Patient Sex]) DTYPE_TEXT New Sub- Area LIC Lookup Name(" SR_ARE A", [Sub- Area]) DTYPE_TEXT Single Value Fields New/ Needs Modificat ion? Name Joi n Colu mn Calculated Value Type Imm edia te Post PickList Validation No Copy New Country LIC LookupName( "COUNTRY",[ Country]) DTYPE_ TEXT
  • 82. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 82 6 Perform manual configuration for the existing "LS Medical Product Issue RR" Business Object: 7 Perform manual configuration for the existing "Audit Trail Engine" Business Service: 8 Perform manual configuration for the existing "Field Value Icons" Bitmap Category: Business Object Component New/Modified? Business Component Link New Contact LS Medical Product Issue RR/ Contact New LS Medical Product Issue RR eMDR Batch LS Medical Product Issue RR/ LS Medical Product Issue RR eMDR Batch Business Service User Props New/Needs Modification? Name Value Comment Modify Enable TRUE 12-CBU9V3: turned OFF on default for performance reasons Bitmaps New/Modified? Name FileName Alt Text String Reference Alt Text New uncheck.gif uncheck.gif SBL_LS_NOT_SE LECTED Not Selected
  • 83. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 83 9 Perform manual configuration for the existing "LS Medical Product Issue RR Form Applet" Applet: Control New/ Modified? Name Caption Caption String HTML Type HTML Only New/Modify Name Caption Caption String HTML Type HTML Only Method Invoked New eMDRQueue eMDR Queue SBL_LS_EMDR_ QUEUE MiniButtonEditN ew Y EscalatePIToeM DRQueue Applet Web Template (Existing and Modify) Name Type Web Template Modify Edit Edit Applet Form Grid Layout Applet Web Template Items New/Needs Modification? Name Control Comments New eMDRQueue eMDRQueue In Edit Web Layout, drag and drop this control from Controls/ Columns onto the layout Applet User Properties New/Needs Modification Name Value New CanInvokeMethod: EscalatePIToeMDRQueue ([RR Sub-Status] <> 'eMDR' OR [RR Sub-Status] IS NULL) AND [RR Status] = 'Submitted'
  • 84. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 84 10 Perform manual configuration for the existing "LS Medical Product Issue RR Child List Applet" Applet: List Columns New/Needs Modification Name Field Display Name - String Reference Read Only HTML Icon Map New FDA Status FDA Acknowledgeme nt SBL_LS_FDA_ST ATUS Y New Flag Urgency Flag SBL_FLAG- 1004224902- 05I LS_URGENCY_FLAG New eMDR Status eMDR Status SBL_LS_EMDR_ STATUS Y New eMDR SubStatus eMDR SubStatus SBL_LS_EMDR_ SUB_STATUS Y Applet Web Template (Existing and Modify) New/Modify Name Type Web Template Modify Edit List Edit List Applet List (Base/ EditList) Applet Web Template Items New/Modify Name Fields Comments New FDA Status FDA Status In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout New Flag Flag In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout
  • 85. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 85 11 Perform manual configuration for the existing "LS Medical Product Issues RR Screen" Screen: New eMDR Status eMDR Status In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout New eMDR SubStatus eMDR SubStatus In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout Screen View New/ Needs Modificat ion? Name Category Name View Type Parent Category View Bar Text - String Reference Menu Text String Reference New LS Medical My Product Issues RR eMDR Batch Audit View LS Medical My Produc t Issues RR eMDR Batch Audit View Detail View eMDR Batch SBL_LS_BATCH_ AUDIT SBL_LS_BATCH_AUDIT New LS Medical My Product Issues RR eMDR Batch Details View LS Medical My Produc t Issues RR eMDR Batch Details View Detail View eMDR Batch SBL_LS_BATCH_ DETAILS SBL_LS_BATCH_DETAIL S Applet Web Template Items New/Modify Name Fields Comments
  • 86. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 86 12 In Siebel Tools, compile all of the locked and updated projects. Importing Seed Data 1 Create an ODBC entry for the database where you plan to import the seed data: a Navigate to Start > Settings > Control Panel > Administrative Tools> Data Sources (ODBC), navigate to the System DSN tab, and click Add. b Select the "Siebel Oracle90" driver (from Datadirect Technologies). c Enter a data source name (such as DevelopmentDB) d Enter the server name to connect to: e For Oracle, enter the TNS service name that you created to connect Siebel Tools to the database. f Test your connection and click OK when tested successfully. 2 Before executing the next step, make sure that the dataimp.exe file exists in the <Tools Install Directory>/bin directory. New LS Medical My Product Issues RR eMDR Report Attachme nt View LS Medical My Produc t Issues RR eMDR Report Attach ment View Detail View eMDR SBL_LS_REPORT _ATTACHMENTS SBL_LS_REPORT_ATTAC HMENTS New eMDR eMDR Aggregate Category SBL_LS_EMDR SBL_LS_EMDR New eMDR Batch eMDR Batch Aggregate Category SBL_LS_EMDR_B ATCH SBL_LS_EMDR_BATCH Screen View New/ Needs Modificat ion? Name Category Name View Type Parent Category View Bar Text - String Reference Menu Text String Reference
  • 87. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 87 3 Run the following command: <Tools Install Directory>bindataimp /u <USERNAME> /p <PASSWORD> /f UnziplocationACR426SEED_DATAACR426_Seed.dat /l <Tools Install Directory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i UnziplocationACR426SEED_DATA ACR426_SeedInp<Database Platform>ACR426_seed.inp /q -1 /w y /e n /t n /x R /n 100 /h log <Tools Install Directory> - Replace with your Siebel Tools install directory <ODBC Source Name> - Replace with the relevant ODBC name <Database Platform> - Replace with your database platform (ORACLE, DB2UDB or MSSQL) 4 Review the <Tools Install Directory>tempdataimp_seed.log file to make sure that the import completed successfully. Seed data import includes mono-language seed data import and languageseed-data import. Use either Step 5 or Step 6 depending upon the language that you are installing. 5 Use the following procedure to import ENU language seed data: a Run the following command after importing the ACR426_Seed.dat file. <Tools Install Directory>bindataimp /u <USERNAME> /p <PASSWORD> /f UnziplocationACR426SEED_DATAACR426_Seed_Locale_ENU.dat /l <Tools Install Directory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i UnziplocationACR426SEED_DATA ACR426_SeedInp<Database Platform>ACR426_Seed_Locale_ENU.inp /q -1 /w y /e n /t n /x R /n 100 /h log <Tools Install Directory> - Replace with your Siebel Tools install directory <ODBC Source Name> - Replace with the relevant ODBC name <Database Platform> - Replace with your database platform (ORACLE, DB2UDB or MSSQL) b Review the <Tools Install Directory>tempdataimp_seed.log file to make sure import completed successfully 6 Use the following procedure to import languages other than ENU: a Run the following command after importing ACR426_Seed.dat file for importing the locale specific ACR426_Seed_Locale_XXX.dat, where XXX is the language code. <Tools Install Directory>bindataimp /u <USERNAME> /p <PASSWORD> /f UnziplocationACR426SEED_DATALMUXXXACR426_Seed_Locale_XXX.dat /l <Tools Install Directory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q - 1 /w n /e y /t n /x R /n 100 /h log b <Tools Install Directory> - Replace with your Siebel Tools install directory c <ODBC Source Name> - Replace with the relevant ODBC name 7 Review the <Tools Install Directory>tempdataimp_seed.log file to make sure that the import completed successfully.
  • 88. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 88 Importing Web Services Definitions Use the following procedure to import Web services definitions. To import Web services definitions 1 Log into the Siebel application. 2 Navigate to the Administration - Web Services > Outbound Web Services view. 3 Import the LSeMDRTransmitFDA.XML file. (This file is located in ApplicationChangesWebServices folder within the extracted zip file.) 4 Query for the LSeMDRTransmitFDA Web service. 5 On the Service Port applet, update the address to point to your BPEL server location. By default, it looks like http://localhost:8888/orabpel/default/LSeMDRTransmitFDA/1.0, so change the localhost to the SOA host name and change 8888 to the proper port number. 6 Log into the Siebel application. 7 Navigate to the Administration - Web Services > Inbound Web Services view. 8 Import the LSUpdateeMDRProductIssueStatus.XML file. (The file is located in the ApplicationChangesWebServices folder within the extracted zip file.) 9 Query for the LSUpdateeMDRProductIssueStatus Web service. 10 On the Service Ports applet, update the address to point to your Siebel server location. By default, it will look like http://sdc78212/eai_enu/ start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&UserName=harikuma&Password =harikuma by default, so change the host name, user name, and password values. For more information about inbound Web services, refer to the sample acknowledgement message: UnziplocationACR426SampleLSUpdateeMDRProductIssueStatus Sample Input.xml Importing Workflow Definitions Use the following procedure to import workflow definitions. XML File to Import Web Service Name Direction LSeMDRTransmitFDS.xml LSeMDRTransmitFDA Outbound XML File to Import Web Service Name Direction LSUpdateeMDRProductIssueStatus.XML LSUpdateeMDRProductIssueStatus Inbound
  • 89. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 89 To import workflow definitions 1 Log into Siebel Tools. NOTE: NOTE: Siebel Tools must be connected to the same database that the Siebel application server is connected to. 2 From Object Explorer, navigate to Workflow Process. 3 From the list applet, right-click and choose Import Workflow Process. 4 Browse to UnziplocationACR426REPOSITORYWorkflows, and choose LS CRMIntegSEBLSIAProductIssueInsertOutboundFlow.xml. 5 After import, query for the LS CRMIntegSEBLSIAProductIssueInsertOutboundFlow workflow process. 6 Withink Lock Projects view > Workflow process, focus on the record and then click the Deploy button on top of the applet to deploy the workflows. 7 Repeat the preceding steps for the LS Siebel PI eMDR Batch workflow. Activating Workflow Definitions Use the following procedure to activate workflow definitions. To activate workflow definitions 1 Log into the Siebel application. 2 Navigate to the Administration - Business Process > Workflow Deployment view. 3 On the Repository Workflow Processes applet, query for the LS CRMIntegSEBLSIAProductIssueInsertOutboundFlow and LS Siebel PI eMDR Batch workflows, focus on each record and click the Activate button to activate the workflow. Adding System Preferences Use the following procedure to add system preferences. To add system preferences 1 In the Site Map, navigate to Application Administration > System Preferences. 2 Create a new record with the following details: XML File to Import Workflow Name Project LS CRMIntegSEBLSIAProductIssueInsertOut boundFlow.xml LS CRMIntegSEBLSIAProductIssueInsertO utboundFlow LS eMDR LS Siebel PI eMDR Batch.xml LS Siebel PI eMDR Batch LS eMDR
  • 90. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 90 ■ System Preference Name: eMDR Deadline Threshold Value ■ System Preference Value: 7 ■ Description: The value is the number of days before the regulatory report deadline, and the system should highlight this value for the users. The urgency is indicated by having the urgency flag in the eMDR list turn from yellow to red. To enable Component Groups ■ Make sure that EAI Component Group is enabled. If it is not, enable it and bounce the Siebel Server. BPEL (Middle Tier) Setup The procedures in the following topic describe how to install Fusion Middleware software and how to set up Canonical Objects. NOTE: Enhancements are required in the BPEL processes delivered to integrate with FDA. For Outbound Web services, the Siebel message is transformed to an HL7 message using the following transformation XSL: UnziplocationACR426BusinessProcessesRegulatoryReportLSeMDRTransmitFDAbpel FDAAcceptanceFormat.xsl and written to a XML file. Enhancements are required to send this xml file to FDA. For Inbound Web services, a sample schema (UnziplocationACR426BusinessProcessesRegulatoryReport eMDRUpdateFDAAckbpel sample1.xsd) is used to capture data from BPEL console and the same is transformed to siebel schema using following XSL UnziplocationACR426BusinessProcessesRegulatoryReport eMDRUpdateFDAAckbpelTransformation_1.xsl. The Web service supports the same schema for all the three acknowledgements. Customization is required to transform the MDN message received from FDA for the first two acknowledgements to The Siebel schema and call the Web service. Installing Fusion Middleware Software Use the following procedure to install Fusion Middleware software. To install Fusion Middlware components ■ Install the following Fusion Middleware components: ■ SOA Suite 10g 10.1.3.1 For information on installing Oracle SOA Suite, refer to the Oracle Application Server Documentation Library. The library is available on Oracle Technology Network (OTN) at http:/ /www.oracle.com/technology/documentation/index.html. To access the documentation, click the Oracle Application Server 10g Release 3 (10.1.3.1) link.
  • 91. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 91 ■ Oracle JDeveloper 10.1.3.1 (Studio Version) If desired, support for JDeveloper can be purchased separately. For information on installing Oracle JDeveloper, refer to OTN at http://www.oracle.com/technology/documentation/ index.html. Setting Up Canonical Objects Canonical Objects are useful in error handling for both business logic and runtime errors. Use the following procedure to set up Canonical Objects. To set up canonical objects 1 Copy the following folder: UnziplocationACR426BusinessProcessesxmllib SEBLLSeMDRFDA and place it into the xmllib folder for your SOA installation (such as: <SOA_HOME>bpelsystemxmllib). 2 Verify that the schema can be accessed by opening a browser and typing in the following URL: http://<SOA Host Name:BPEL Console port number>/orabpel/xmllib/ SEBLLSeMDRFDA / CanonicalObjects/coCommon.xsd For example: http://127.0.0.1:8888/orabpel/xmllib/SEBLLSeMDRFDA/CanonicalObjects/ coCommon.xsd The CoCommon schema should open correctly. If there is a problem in opening the file, restart the SOA suite. Configuring Business Processes Execution Language Processes Use the following procedure to configure BPEL processes. To configure BPEL processes 1 Open the following file for editing: UnziplocationACR426SetUpCRMIntegProcessParameters.xml.
  • 92. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 92 2 Modify its content until it matches the following: NOTE: Change the values in the lines that begin with "<property name="PARAMVALUE">. Replace the values with the relevant values from your environment. <?xml version="1.0" encoding="UTF-8" ?> <LISTOFBUILDPARAMETERS xmlns="http://www.siebel.com/uan/SiebelBIAs/ SharedComponents/CRMIntegProcessProperties"> <BUILDPARAMETER> <property name="PARAMNAME">http://sdc78212svod:8888/orabpel/default</property> <property name="PARAMVALUE">http://127.0.0.1:8888/orabpel/default</property> <property name="DESC">This Parameter is to capture BPEL domain URL information.Please specify your environment specific value for "PARAMVALUE" property. Here "http://127.0.0.1:8888" should be replaced with the HOST, PORT where the BPEL PM is running. "orabpel" should stay same. "default" is the name of domain where the bpel processes are to be deployed.</property> </BUILDPARAMETER> <BUILDPARAMETER> <property name="PARAMNAME">http://sdc78212svod:8888/orabpel/xmllib</property> <property name="PARAMVALUE">http://127.0.0.1:8888/orabpel/xmllib</property> <property name="DESC">This Parameter is to capture the XMLLIB url. Please specify your environment specific value for "PARAMVALUE" property. Here "http://127.0.0.1:8888" should be replaced with the HOST, PORT where the BPEL PM is running. "orabpel/xmllib" should stay same.</property> </BUILDPARAMETER> <BUILDPARAMETER> <property name="PARAMNAME">"http://sdc78212svod/eai_enu/ start.swe?SWEExtSource=WebService;SWEExtCmd=Execute;UserName=harikuma;Password= harikuma"</property> <property name="PARAMVALUE">[SIEBEL SERVER LOCATION]</property> <property name="DESC">This Parameter is to capture the Siebel server url. Specify your environment-specific value for "PARAMVALUE" property (such as http://xyz.siebel.com:8888</ property> </BUILDPARAMETER> <BUILDPARAMETER> <property name="PARAMNAME">"c:temp"</property> <property name="PARAMVALUE">"c:test"</property>
  • 93. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 93 <property name="DESC">Ouput Directory where FDA eMDR XML files will be created </ property> </BUILDPARAMETER> </LISTOFBUILDPARAMETERS> 3 After you have changed the parameter values, navigate to UnziplocationACR426SetUpscripts and run the following command for the BPEL projects in the Compound project: java -jar EditParam.jar -i UnziplocationACR426BusinessProcesses -f UnziplocationACR426SetupCRMIntegProcessParameters.xml -verbose -t D:temp Use the following procedure to set the output directory for storing FDA Report XML files. To set the output directory for storing the FDA report XML files 1 Navigate to UnziplocationACR426BusinessProcesses RegulatoryReportLSeMDRTransmitFDAbpel, and edit WriteIntoFile.wsdl. 2 Locate "PhysicalDirectory="c:temp"", and replace the value to the relevant value 3 Locate "FileNamingConvention="FDAReport.xml"" and replace the value to relevant value, such as 'FDA_%yyMMddHHmmss%.xml'. Setting Up an Application Workspace Use the following procedure to set up an application workspace. To set up an application workspace 1 Start Oracle JDeveloper. 2 Click the Applications Navigator tab. 3 Right-click the Applications icon. 4 Choose New and specify the type as Application. 5 Specify eMDR as the name for the application. 6 Specify a directory name where the BPEL processes are stored (for example:UnziplocationACR426BusinessProcesses). 7 In the Create Project popup, click Cancel. 8 Repeat the following steps for each of the following JPR files: ■ UnziplocationACR426BusinessProcessesRegulatoryReporteMDRUpdateFDAAckeMDRUpdat eFDAAck.jpr ■ UnziplocationACR426BusinessProcessesRegulatoryReport LSeMDRTransmitFDALSeMDRTransmitFDA.jpr a Select the eMDR application. b Right-click and choose Add to eMDR.jws.
  • 94. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 94 c Select a JPR file and click Open. This imports the process code into the application. Deploying Business Process Execution Language Use the following procedure to deploy BPEL processes. NOTE: Before you begin, make sure that the SOA Suite has been installed, and make sure JDeveloper has been installed and that the application server and integration server connection have been configured. To deploy BPEL processes 1 Make sure that the SOA Suite has been started. 2 From Oracle JDeveloper, select the LSeMDRTransmitFDA project. 3 Right-click on the project name and choose Deploy > IntegrationServerName > Deploy to default domain. 4 Ignore the warnings listed on the build output window. 5 Select the eMDRUpdateFDAAck project. 6 Right-click on the project name and choose Deploy > IntegrationServerName > Deploy to default domain. 7 Ignore the warnings listed on the build output window. This compiles the SRC code and then deploys the BPEL process to the SOA Instance. Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 437 1 Go to the Siebel Tools installation directory <Tools Install Directory>REPPATCH. 2 Unzip the file ACR437.zip file. This will create the following directory structure: <Path of the Unzipped Folder>REPPATCH The above ACR437 folder will have the following subfolders: ■ DMGSchemaChanges (refer to the information about how to import .sif files in Siebel CRM and UCM Integration Guide on My Oracle Support. ■ LMU ■ SeedData (refer to the information about how to import seed data in Siebel CRM and UCM Integration Guide on My Oracle Support. ■ SIFFiles
  • 95. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 95 ■ WFs As part of the O2C release, schema changes have been made within the database. The O2CMST80_S_USER.sif, VACR437_EIMFinal_81.sif and VACR437_TableFinal_81.sif files all contain changes, and the S_USER table has been changed as well. More Information See Siebel CRM and UCM Integration Guide on My Oracle Support (Article ID 763962.1) for information about the following topics: ■ How to import .sif files into the repository ■ How to create tables on the physical database ■ How to import seed data ■ How to set up the workflow policy ■ How to create a job for the Generate Triggers component ■ How to reveal the Default Tasks parameter ■ How to start tasks for Workflow Monitor Agent ■ How to set up the integration user. Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 439 This topic is part of “Configuration Instructions for Enhancements and Updates” on page 44. After installing ACR 439, you must make sure that Find objects are visible in the application. To make sure that Find objects are visible in the application 1 Connect to Siebel Tools. 2 Select the application from Object Explorer, and search for the relevant Application Name. 3 Navigate to Application Find in the Object Explorer, and activate the Find names that you want to display for the application. 4 Make sure that the relevant Business Components are part of the Search Execution Business Object. 5 Compile your changes to the SRF. You may receive the following error message after you have installed ACR 439: “An error has occurred creating business component ‘Consumer’ used by business object ‘Search Execution’. Please ask your systems administrator to check your application configuration. (SBL-DAT-00222). Use the following procedure to resolve this error.
  • 96. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 96 To resolve the SBL-DAT-00222 error message 1 Connect to Siebel Tools. 2 Within the Object Explorer, select Business Object. 3 Query for “Search Execution,” right-click the access the submenu, and select “Unlock Object.” 4 Navigate to the Object Business Component. 5 Click New Record and add the required Business Component (such as “Consumer”). 6 Compile the changes to the SRF. For more information about ACR 439 and for information about how to implement this enhancement, see Siebel Search Administration Guide on the Siebel Bookshelf, available on Oracle Technology Network (OTN) at http://www.oracle.com/technology/documentation/siebel.html. Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 439B The following sections contain information about how to configure and install ACR 439B. Importing SIF Files for ACR 439B Use the following procedure to import the .sif files for ACR 439B. To import the .sif files for ACR 439B 1 Connect to Siebel Tools. 2 Navigate to the Fast Search project and lock it. 3 Uncompress the file ACR439_sif.zip file, which is located under ToolsREPPATCH. 4 Import the .sif files you extracted from the .zip file. 5 Compile the project. Importing the sif files creates the following objects: ■ Applet: Search lookin Results Body, Search lookin Results Header, Recent Saved Searches Applet ■ View: Search lookin Results View ■ Web Template: Lookin Results View ■ Screen: Search View Dummy Screen Siebel Tools Changes for ACR 439B NOTE: Lock the Fast Search project before performing the changes detailed in this section.
  • 97. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 97 To add the GotoView=Search lookin Results view 1 Connect to Siebel Tools. 2 Within Applet Search lookin Results Header, add the user property GotoView= Search lookin Results View. 3 Compile the project. To add the SamePage and GotoView user properties to the Search lookin applet 1 Connect to Siebel Tools. 2 Query for the Search lookin applet. 3 Navigate to Applet User Prop and add the two user properties listed in the following table: 4 Navigate to Control, query for Name= "Search", and update the Search property as detailed in the following table: To add the GotoView user property to the Search Results Body applet 1 Connect to Siebel Tools. 2 Query for the Search Results Body applet. 3 Navigate to Applet User Prop and add the following user property: 4 Navigate to Control, query for Name = "PositionOnRow", and update the following property: Name Value Description SamePage TRUE/ FALSE Having this value set to TRUE displays the Search Results on the left hand side of the screen. GotoResultsView Search lookin Results View Search lookin Results View Name Target View Frame Description Search empty The old value is "_sweview". The property needs to be set to empty. Name Value Description GotoResultsView Search lookin Results View HTML Bitmap HTML Disabled Bitmap ROW_OFF ROW_ON
  • 98. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 98 5 Navigate to Applet Web Template Items and add the item detailed below: Seed Data Changes for ACR 439B Use the following procedure to add the Search lookin Results view. To add the Search lookin Results View 1 Navigate to the Administration - Application screen, and then the Views view. 2 Click New and add "Search lookin Results View" with the following values: ■ View Name = "Search lookin Results View" ■ Description = "Search lookin Results View" ■ Default Local Access = "true" 3 To give the administrator responsibility to the view, navigate to the Administration - Application screen, and then the Responsibilities view. Query for the administrator. 4 In the view applet, add "Search lookin Results View". SWT Changes for ACR 439B Siebel Web Templates (SWT) are a set of HTML files with embedded Siebel tags that determine how the UI is rendered in a browser. The following SWT files need to be edited for ACR 439B: ■ Search_ListBodySearchResults.swt ■ SearchResults.swt ■ SavedSearch.swt Apply the changes listed below for each swt in order for ACR 439B to display the web templates correctly. To edit Search_ListBodySearchResults.swt 1 Place the text below between this line: <!------------ Begin Row -------------> and this line: <!------------ Display all Search Result Field -------------> 2 Insert the following text: <tr class="swe:this.RowStyle"> Item Identifier Name Control Parent Name Type 501 PositionOnRow PositionOnRow Base Control
  • 99. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 99 <swe:control id="501"><!-- Select 501 --><td align="swe:this.TextAlignment" width="42" class="Row"><swe:this property="FormattedHtml" hintText="Selected Row" hintMapType="Control"/></td></swe:control> <swe:select-row><td align="swe:this.TextAlignment" width="42" class="Row"><swe:this property="FormattedHtml" /></td></swe:select-row> To edit SearchResults.swt ■ Place the following text after the line </b> for id ="3000": &nbsp; &nbsp; <b> <swe:control id="3001"> <!-- CR 12-1O4OT68 --> <swe:this property="FormattedHtml" hintMapType="Control" hintText="Attach"/> </swe:control> </b> <b> <swe:control id="3002"> <!-- CR 12-1O4OT91 --> <swe:this property="FormattedHtml" hintMapType="Control" hintText="Preview"/> </swe:control> </b> To edit SavedSearch.swt ■ Place the following text after the line </tr> for id="99": <!-- Begin of CR 12-1O4OTAF --> <tr> <td align="left"> <swe:control id="101"> <b><swe:this property="FormattedHtml" hintMapType="Control" hintText="Field"/></b> </swe:control> </td> </tr> <tr> <td align="left">&nbsp</td>
  • 100. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 100 </tr> <!-- End of CR 12-1O4OTAF --> Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 450 For information about how to implement ACR 450, within My Oracle Support, navigate to the Knowledge tab and search for Article ID 880612.1. For more information about the Siebel Hospitality application, see Siebel Hospitality Guide on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html. Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 452 Use the following procedure to install ACR 452 for the Siebel 8.1.1.1 Fix Pack. NOTE: Oracle Secure Enterprise Search patch 10.1.8.4 or higher is required for ACR 452. To install ACR 452 ■ Extract the ToolsREPPATCH ACR452_phaseA.zip file to ToolsREPPATCH. This creates the following directory structure: ToolsREPPATCHACR452_phaseA. To import ACR 452 seed data 1 Open ToolsREPPATCHACR452_phaseASEED_DATA import.bat and edit the required import.bat parameters, using the following as an example: ■ SET TOOLSPATH= <Enter Tools path here> ■ SET DATASRC= <Enter Source name used by Siebel Tools for ODBC DSN. The value is the same as that used for ConnectString in the [ServerDataSrc] section of Tools.cfg> ■ SET TBLOWNER=<Enter table owner name used by Siebel Tools for connecting to the server database. The value is the same as that used for TableOwner in the [ServerDataSrc] section of Tools.cfg> ■ SET USERNAME=<Enter the username used to connect to the Siebel database, such as SADMIN> ■ SET PASSWORD=<Enter the password used to connect to the Siebel database, such as SADMIN> 2 Run import.bat.
  • 101. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 101 To edit Tools.cfg to import symbolic strings 1 Open Tools.cfg, search for the SymStrPrefix parameter, and change the value of the SymStrPrefix parameter from X_ to SBL_. 2 Within Siebel Tools, lock the following Search projects: ■ Fast Search ■ Search Execution ■ Symbolic Strings To import ACR 452.sif 1 Open ToolsREPPATCHACR452_phaseArepositoryimport.bat, and edit the required import.bat parameters, using the following as an example: ■ SET PCDTOOLSPATH= <Enter Tools path here> ■ SET PCDDATASRC= <Enter DataSrc name used by Tools.cfg. The value is the same as [ServerDataSrc] in the Tools.cfg> ■ SET PCDUSERNAME=<Enter the username used to connect to the Siebel database, such as SADMIN> ■ SET PCDPASSWORD==<Enter the password used to connect to the Siebel database, suchas SADMIN> ■ SET LANG==<Enter language code, such as ENU> 2 Run import.bat 3 In Siebel Tools, import the ToolsREPPATCHACR452_phaseABusiness Component.sif file. To install localization files 1 (Optional) The following step only applies only to customers who are installing languages other than ENU. If you are installing languages other than ENU: a Navigate to Tools > Utilities > Locale Management to import LMU files for the specific language from the ToolsREPPATCH_ACR452_phaseALMU folder into Siebel Tools. b Select Source Language = English American c Target Language = <Select Language> d Click the Import tab, click Browse to locate the LMU file you want to import, and then click Import. 2 Stop the Siebel Server, if it is running. 3 To change the language to the specific language that you just imported, navigate to View > Options > Language. To compile and save the Siebel Tools changes 1 Within Siebel Tools, navigate to Compile Projects, select all projects, and then click Compile.
  • 102. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 102 2 Save the srf file 3 Within Siebel Tools, unlock the following Search projects: ■ Fast Search ■ Search Execution ■ Symbolic Strings To edit Tools.cfg for customer changes ■ Open Tools.cfg, search for the SymStrPrefix parameter, and change the value of the SymStrPrefix parameter from SBL_ to X_. To install the AdvancedSearch SWT file 1 On the Siebel Sever, replace the sessiebsrvrWEBTEMPLAdvancedSearch.swt file with the ToolsREPPATCHACR452_phaseArepositoryWeb Template AdvancedSearch.swt file . 2 Start the Siebel Server. 3 Navigate to Administration – Search > Search Engine Settings to confirm that the Connect and Disconnect buttons have been added. For information on installing Search_Engine_Config.xml, and configuring Search for ACR 452, see the Siebel Search Administration Guide on the Siebel Bookshelf at http://www.oracle.com/technology/ documentation/siebel.html. Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 456 This topic is part of “Configuration Instructions for Enhancements and Updates” on page 44. Use the instructions in this topic to implement ACR 456, which provides a user interface for exporting and importing assignment-related data. For more information about the enhancements provided by ACR 456 for version 8.1.1.1 and later, see Siebel Assignment Manager Administration Guide. The latest version of this guide is available on the Siebel 8.1 Bookshelf on OTN at http://www.oracle.com/technology/documentation/siebel.html. Importing Archive Files for ACR 456 To implement this ACR, you must import archive files (.sif) in Siebel Tools. 1 On the machine where you installed Siebel Tools, locate the file ACR456.zip in the folder SIEBEL_TOOLS_ROOTREPPATCH. 2 Uncompress this .zip file and extract the archive files (.sif) it contains. 3 Navigate to SIEBEL_TOOLS_ROOTbinenu. 4 Open the file tools.cfg in an editor like Notepad.
  • 103. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 103 5 Change the value of the SymStrPrefix parameter to SBL_. (After performing the steps described in this topic, change this parameter back to its original value of X_.) Save the tools.cfg file. 6 Launch Siebel Tools. 7 Lock the following projects: ■ Symbolic Strings ■ Assignment ■ Orgchart ■ Admin 8 Import the archive files (.sif) you previously extracted from ACR456.zip into Siebel Tools. Import the files in the order shown below: ■ AM-ImportExport.sif ■ AM-ImportExport-SymbolicStrings.sif ■ AM-ImportExport-applet.sif ■ AM-ImportExport-buscomp.sif ■ AM-ImportExport-screen.sif 9 Compile the changes into an updated repository file (SRF file). Copy the new SRF file to the Siebel Server installation, under SIEBSRVR_ROOTobjectsenu. 10 In the tools.cfg file, change the value of the SymStrPrefix parameter back to X_. Save the tools.cfg file. Adding Seed Data for ACR 456 To implement this ACR, you must add views and other seed data to the Siebel application. 1 Launch the Siebel application, such as Siebel Call Center. 2 Navigate to the Administration - Application screen, and then the Views view. 3 Add the following views: ■ Transaction Log View ■ Transaction Log View - All ■ Transaction Log View - Manager ■ Position Export View by Skill 4 Associate suitable responsibilities to the new views. 5 Add List of Values (LOV) data for U.S. English (ENU), as described below. NOTE: This example is for U.S. English (ENU) only. For other languages, see files in the compressed file ACR456.zip. Set Display Value appropriately for each non-ENU language. a Navigate to the Administration - Data screen, then the List of Values view.
  • 104. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 104 b For Type TODO_TYPE, add new records, where: ❏ Display Value is Import, and Language-Independent Code is Import. ❏ Display Value is Export, and Language-Independent Code is Export. c For Type EVENT_STATUS, add new records, where: ❏ Display Value is Success, and Language-Independent Code is Success. ❏ Display Value is Failed, and Language-Independent Code is Failed. d For Type ACTIVITY_DISPLAY_CODE, add new records, where: ❏ Display Value is Position and Activities, and Language-Independent Code is Position and Activity. ❏ Display Value is Assignment and Activities, and Language-Independent Code is Assignment and Activity. Activating Workflow Process for ACR 456 To implement this ACR, you must activate a new workflow process in Siebel Tools. 1 Launch Siebel Tools. 2 In the Object Explorer, click Workflow Process. 3 Select the workflow process Export Assignment Data. (This workflow was added when you imported the file AM-ImportExport.sif.) 4 Publish and activate the selected workflow process. Validating Configuration Steps for ACR 456 After performing all the steps described earlier in this topic, restart the Siebel Server and log in to the Siebel Server. Refer to the information about importing and exporting assignment-related data in the Siebel Assignment Manager Administration Guide. Validate that the user interface changes are visible in the Administration - Assignment screen, and validate that the relevant functionality described in that book works as expected. Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 457 The following sections contain information about how to implement ACR 457. For more information about Siebel Order Management, see Siebel Order Management Guide on the Siebel Bookshelf http://www.oracle.com/technology/documentation/siebel.html.
  • 105. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 105 1 Navigate to the Siebel Tools installation directory <Tools Install Directory>REPPATCH, and unzip the acr457.zip file. This will create the following directory structure: <Tools Install Directory>REPPATCHacr457 2 In Siebel Tools, lock the following projects: ■ VORD Compound Product Validation Engine ■ VORD Network Order Entry 3 Import the SIF files from the ObjectsSIFs folder into Siebel Tools using the Import From Archive function. Make sure to choose Merge Option in the Siebel Tools import wizard. NOTE: If you have not locked the required projects, you may receive a warning error message. 4 Import the following SIF files: ■ VORD CPVE Validation Service.sif ■ VORD Network Node.sif 5 Stop Siebel Server, if it is running. 6 Compile all the projects using Compile Projects function, and select either the All Projects option or the Locked Projects option. Save the srf file to the <Siebel Server Install folder>objectsENUsiebel_sia.srf directory on the installed Siebel Server. 7 Start the Siebel Server. 8 Lock the SIS OM Base Architecture project,and import the workflows listed in the following table into the Siebel application. a Select Workflow Process in Siebel Tools Object Explorer. b Right-click on the right-side pane called Workflow Processes and import the .xml file into Siebel Tools from the workflows folder. Refer to the list of workflows in the table above to know which projects these workflows need to be imported into. c Check the status of each workflow process. If it is In-Progress, then deploy the workflow to change its status to complete. Do not click the Deploy + Activate button, as doing so will yield an error message. Only click the Deploy button. NOTE: You may receive the "This is an invalid Workflow…" error message while deploying the modified workflows from the list. Ignore the error and click Yes. d Repeat Step b and Step c for of all the workflows in the folder. e Log in to the Siebel application as an administrator, and navigate to the Site Map. Workflow Name New/Modified Project VORD Validate (Order) Modified SIS OM Base Architecture VORD Validate (Quote) Modified SIS OM Base Architecture SIS OM Disconnect Products & Services Process Modified SIS OM Base Architecture
  • 106. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 106 f Click on Administration - Business Process. g Navigate to Workflow Deployment > Repository Workflow Process. h Query for the workflow processes and activate them. 9 Restart the Siebel Server. 10 Launch the Siebel Communications application. Enabling Component Groups Use the following procedure to enable component groups. To enable component groups 1 Navigate to Site Map > Administration - Server Configuration > Enterprises > Component Groups. 2 Query for each of the following component groups and if Enable State = Disabled, click <Enable>: SIA ■ Siebel CME [Alias- Communications] ■ Siebel ISS [Alias- ISS] ■ Communications Management [Alias- CommMgmt] ■ Workflow Management [Alias- Workflow] NOTE: You can also activate the component groups by running the Enable compgrp <Alias> command through the Srvrmgr command prompt. 3 After enabling the necessary components, navigate to Site Map > Administration - Server Configuration > Enterprises > Synchronize, select all the records and click the Synchronize button. 4 Bounce the server. 5 Use the following procedure if you are a Windows customer: a Log in with system administrator credentials. b From Start > Run, type cmd. c Find the drive that the build is installed on. d Type <Build>sessiebsrvrbin. e Execute the following command: srvrmgr /e SIEBEL /s server name:portnum /u SADMIN /p MSSQL <enter> f Run the command to verify that the components were successfully enabled. g Run the following command to enable the component group: Enable compgrp <Alias>
  • 107. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 107 h Verify that the command executed successfully, and then run the Exit command. i Restart the services. j After the machine is up, than connect to server manger by running command inStep e and verify the enabled components groups by running the "list of compgrp" command. 6 Use the following procedure if you are a UNIX customer: a From the local machine click on Stat - Run- type telnet <Machine name> (such as telnet sdcpi43). b Log in with administrator credentials. c Navigate to <Build>sessiebsrvrbin. d Run the following commands: smgr <enter> set server <machine name> <enter> list compgroup <enter> e Run the following command to enable components group: Enable compgrp <Alias> f Verify that the command executed successfully, and then run the Exit command. g Restart the services. Use the following procedure to delete Customer Order Management workflows. NOTE: Before you run the scripts in the following procedure, make sure the Workflow component is enabled and that the server has been restarted after the component groups have been enabled. To delete Customer Order Management workflows 1 Navigate to Site Map > Administration Business Service > Simulator. 2 Click the Load from File button and load the "COM_Workflow Admin Service Delete.xml" file. 3 On the Input Arguments tab, click the Load from File button and loadthe "COM_Workflow Admin Service Input.xml" file. 4 On the Simulator Applet, select the record thathas the Method Name as "DeleteDeploy" and click the Run button. Activating the Workflows Through Scripts Use the following procedure to activate Customer Order Management workflows. NOTE: Before you run the script, make sure the Workflow component is enabled and that the server has been restarted after the component groups have been enabled.
  • 108. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 108 To activate Customer Order Management workflows 1 Navigate to Site Map > Administration Business Service > Simulator. 2 Click the Load from File button and load the "COM_Workflow Admin Service Activate.xml" file. 3 On the Input Arguments tab, click the Load from File button and loadthe "COM_Workflow Admin Service Input.xml" file. 4 On the Simulator Applet, select the record that has the Method Name as "Activate" and click the Run button. A record displaying the number of workflows activated will display. 5 Log out of the eCommunications application and then log back in. This will allow you to begin creating orders. Use the following procedure to manually activate the Pricing and Eligibility Procedure - Default workflow process. To manually enable the Pricing and Eligibility workflow process 1 Click on Administration - Business Process. 2 Navigate to Workflow Deployment > Repository Workflow Process. 3 Query for the Pricing and Eligibility Procedure - Default workflow process and activate it. 4 Log out and relogin in to Siebel eCommunications application. You can now create orders. Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 463 The following sections contain information about how to install and configure ACR 463. CAUTION: ACR 463 does not include all of the Web services for MDM/PIM. NOTE: This ACR is for Siebel Industry Applications only. NOTE: If you have installed Siebel 8.1.1 QF1002 for ACR 463 or Siebel 8.1.1.1 QF5101 for ACR 463, you do not need toperform the repository changes detailed in the following sections, as the changes that you performed when you installed the Quick Fixes were not overwritten. However, if you are installing ACR 463 for the first time, you do need to perform the repository changes detailed in the following sections. 1 Navigate to the Siebel Tools installation directory <Tools Install Directory>REPPATCH.
  • 109. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 109 2 Unzip the file ACR463.zip file. This will create the following directory structure: <Tools Install Directory>REPPATCHACR463.zip The ACR463.zip folder that you create will contain the following subfolders: ■ DMGSchemaChanges ■ EIM ■ LMU ■ SeedData ■ SIFFiles ■ WFs The following instructions refer to the folders specified above. Applying Schema Changes to the Database The information in the following section describes how to apply schema changes to the database, and also provides information about which tables were changed. Use the following procedure to import the schema into the database. To import the schema into the database 1 Lock the following projects before importing: ■ EIM Asset ■ EIM Common SIA ■ EIM Invoice ■ EIM Order ■ EIM Product ■ EIM Quote ■ EIM BulkRequest ■ EIM Organization ■ EIM Service Request ■ Table Asset ■ Table BulkRequest ■ Table Invoice ■ Table Order ■ Table Organization
  • 110. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 110 ■ Table Product ■ Table Quote ■ Table Service Request ■ Table Special Rate List ■ Table CIF ■ Table Person ■ Table FleetManagement ■ CUT Newtable 2 Import the .sif files in the following sequence ■ AIA24_schema_changes.sif ■ AIA24_EIM_schema_changes.sif 3 Use the Siebel Tools Import from Archive function to read this file and create the tables in the repository. The "merge" option should be used while importing this file. Creating Tables on the Physical Database Use the following procedure to create tables on the physical database. To create tables on the physical database 1 Use Siebel Tools to query for the list of tables that were imported into the repository, and then use the "Apply/DDL" button to apply the changes to the physical database. 2 Use privileged database userpass word in the Database user Database user password column in the Apply Schema dialog box. NOTE: Make sure to create the ODBC data source for the database to which you want to apply the schema changes. 3 From Object Explorer, select Table Object Definition. 4 Query for the tables that have changed using the following criteria: Query Criteria: Changed = Yes 5 Click on Apply/DDL. 6 Select Apply DDL. 7 Select Current Query from the Tables drop-down list. 8 Enter the appropriate information for ODBC Data Source/ Database User and Database User Password. 9 Click the Apply button. The "Changes Successfully Applied" message displays.
  • 111. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 111 Importing Seed Data Use the following procedure to import seed data. To import seed data 1 Create an ODBC entry for the database where you plan to import the seed data: a Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC). b Navigate to the System DSN tab. c Click Add. d Select "Siebel Oracle90" driver (from Datadirect Technologies). e Enter a data source name (such as DevelopmentDB). f Enter the server name to connect to: For Oracle, enter the TNS service name that you created to connect Siebel Tools to the database. g Test the connection and click OK after you have verified the connection. 2 Navigate to the directory where you installed Siebel Tools and change it to the REPATCHACR463 directory. NOTE: Before you perform the following step, make sure that the dataimp.exe file exists in the <Tools Install Directory>/bin directory. 3 Seed data import includes mono-language seed-data import and language seed-data import. NOTE: Use the /Z option flag to ignore duplicates during import. a Use the following command to import mono-language seed data: <Tools Install Directory>bindataimp /u sadmin /p sadmin /f <Tools InstallDirectory>REPATCH ACR463SeedDataSeed_aiacom24.dat /l <Tools InstallDirectory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q - 1 /w n /e y /t n /x R /n 100 /h log b Use the following command to import the language seed data: <Tools Install Directory>bindataimp /u sadmin /p sadmin /f <Tools InstallDirectory>REPATCH ACR463SeedDataseed_locale_<language>.dat /l <Tools InstallDirectory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q - 1 /w n /e y /t n /x R /n 100 /h log <Tools Install Directory> - Replace with your Tools install directory. <ODBC Source Name> - Replace with ODBC name created in Step 1. 4 Review the log file in <Tools Install Directory>tempdataimp_seed.log file to make sure that the import completed successfully.
  • 112. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 112 Siebel Tools Changes for ACR 463 1 Open tools.cfg from <Tools Install Directory>BinEnu and verify the [Siebel] section. Make sure that the SymStrPrefix entry has been set to SBL_ [Siebel] …….. SymStrPrefix parameter needs to be X_ for Siebel Customers. SymStrPrefix = SBL_ …….. NOTE: After changing the tools.cfg file, make sure to log out of Siebel Tools and log in again to apply the changes. 2 In Siebel Tools, lock all the following projects: ■ ABO Bulk Request ■ Account ■ Account (SSE) ■ Assignment (SSE) ■ Asset Management ■ Bitmap ■ CMU Billing BC ■ CMU Billing Product ■ CMU Billing UI ■ CMU Billing Integration ■ CUT Admin - External Data ■ CUT Billing ■ CUT Credit Alert ■ CUT Profile ■ CUT Trouble Ticket ■ Contact ■ Comm Manager ■ Communication ■ Eligibility Compatibility ■ Fleet Management ■ ISS Authoring Admin ■ ISS Class Admin
  • 113. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 113 ■ ISS Product Admin ■ ISS Promotion Admin ■ MACD Performance ■ Order Entry ■ Prepaid Service 8.1 ■ Product ■ Product (SSE) ■ Product Integration ■ Product Selection UI ■ Quote (UI) ■ Quote ■ SIS OM Base Architecture ■ Service ■ Symbolic Strings ■ UCM Privacy Management ■ VEAI CUT Billing Integration ■ VERT CUT Address ■ VERT CUT Screens ■ Web Channel Order Management ■ Web Service Integration ■ eService Billing ■ eAuto Product 3 Import the rest of the SIF files from the SIFFiles folder into Siebel Tools using the Import From Archive function. NOTE: If you have not locked the required projects, you may receive a warning error message. Make sure to choose Merge Option in Siebel Tools Import Wizard. Import the following SIF files: ■ Modified Applets.sif ■ Modified BCs.sif ■ Modified Bitmaps.sif ■ Modified BOs.sif ■ Modified BSs.sif ■ Modified Classes.sif
  • 114. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 114 ■ Modified Commands.sif ■ Modified IOs.sif ■ Modified Links.sif ■ Modified Picklists.sif ■ Modified Screens.sif ■ Modified Symbolic Strings.sif ■ Modified Views.sif ■ Modified Workflow Policy Columns.sif ■ Modified Workflow Policy Objects.sif The following steps are only necessary for customers who are installing languages other than ENU: 4 Import LMU Files for the specific language from the LMU folder into Siebel Tools. [Select menu Tools ' Utilities ' Locale Management]. a Select Source Language = English American Target Language = <Specific Language> b Click the Import tab > Browse to locate the LMU file you want to import and click Import. NOTE: If an error occurs while you are importing the LMU file, open the file, convert the language value for Source into the corresponding language. For example, do the following for NLD: Source (Language,Application) : (Engels-Amerikaans,STD - Standard) Target (Language,Application) : (Dutch,STD - Standard) 5 Stop Siebel Server, if it is running. 6 Compile all the projects using Tools > Compile Projects and selecting the "All Projects" option. Save the srf file to location <Siebel Server Install folder>objectsENUsiebel_sia.srf on the installed Siebel server. 7 Start the Siebel Server. 8 Import the workflows listed in the following table into the Siebel application. NOTE: All of the existing workflows should be imported. In other words, the modified workflows should be imported into the corresponding projects. Workflow Name Project ABO Bulk Request - Validate Process ABO Bulk Request ABO Bulk Request Add Item Customize Process ABO Bulk Request ABO Bulk Request - Clear Exception Process Workflow ABO Bulk Request ABO Bulk Request - Parallel Sub Process Workflow ABO Bulk Request
  • 115. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 115 ABO Bulk Request - Prepare Action Set Sub-Process Workflow ABO Bulk Request ABO Bulk Request - Submit Process Workflow ABO Bulk Request Basic Pricing Procedure Cfg RTC CMU Credit Alert Status Sync Web Service Integration CMU SIA Submit Adjustment Request to External CMU Billing Integration CMUBalanceDetailsEventAdjustmentWF CMU Billing Integration CMUEventDetailsAdjustmentWF CMU Billing Integration CMUInvoiceAdjustmentWF CMU Billing Integration CMUItemChargeAdjustmentWF CMU Billing Integration CMUUnbilledEventAdjustmentWF Web Service Integration CMUUnbilledNonCurrencyEventAdjustmentWF Web Service Integration Dynamic Pricing Procedure Row Set Transformation Toolkit ISS Promotion Upgrade Process ISS Promotion Workflow Pricing Procedure - Calculate Net Price Row Set Transformation Toolkit SIS OM Disconnect Products & Services Process SIS OM Base Architecture SIS OM Edit Complex Asset Workflow SIS OM Base Architecture SIS OM Edit Service Order Line Item SIS OM Base Architecture SIS OM Modify Products & Services Process SIS OM Base Architecture SIS OM Order Line Item Update Main SIS OM Base Architecture SIS OM Suspend / Resume Asset Sub-Process SIS OM Base Architecture SIS OM Suspend / Resume Products & Services Process SIS OM Base Architecture SISOMBillingSubmitOrderWebService CMU Billing Integration SWI Account Update Workflow Web Service Integration SWI Address Update Workflow Web Service Integration SWI Billing Profile Update Workflow Web Service Integration SWI Cancel Sales Order Line Item Web Service Integration SWI Contact Update Workflow Web Service Integration SWICancel Sales Order Web Service Integration SWI Special Rating - Synchronize Process Web Service Integration SWIAdjustmentStatusUpdate Web Service Integration SWICopyOrder Web Service Integration SWIOrderUpsert Web Service Integration Workflow Name Project
  • 116. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 116 a Select Workflow Process in Siebel Tools Object Explorer. b Right-click on the right-side pane 'Workflow Processes' and import the .xml file into Siebel Tools from the WFs folder. Refer to the list of workflows inthe table above to know which project these workflows need to be imported into. c Check the status of the Workflow process. If it is In-Progress, then make it complete by deploying the Workflow process (For version 8.0 and above, the "Publish/Activate" button changes the status to complete. To view this button, click the View menu > Tool Bar, and select WF/Task Editor.) NOTE: If this step throws an error message, note the workflows that failed and manually activate them within the application. d Repeat Step b and Step c for of all the workflows in the folder. e Log in to the Siebel application as an administrator. f Navigate to the Site Map. g Click on Administration - Business Process. h Go to Workflow Deployment > Repository Workflow Process. i Query for the workflow processes and activate them. 9 Modify the run time events for promotions: a Navigate to the Administration - Runtime Events screen. b Click on the 'Action Sets' view. This shows three applets. c In the first applet, called 'Action Sets', search for the Action Set 'Cache Refresh BC - ISS Promotion Pricing Components List Applet'. d For this Action Set, in the bottom Form Applet, there is a control with the 'Business Service Context' label. For this control, the current value previously was only "ISS Promotion Pricing Components", "ISS Promotion Pricing Rules Summary". Another new entry was added to thisand now the value for this control is "ISS Promotion Pricing Components", "ISS Promotion Pricing Rules Summary", and "Promotion Config Item". (Note that there should be a space after the comma.) e Navigate to the child applet. f Uncheck the Active flag for the Validate record. 10 Release Variable Maps and Signals manually: a Navigate to Site Map > Admin - Order Management > Variable Maps. b Query for the following: SWIValidateDependentOrders Web Service Integration Verify Header (Order) COM Workflows Verify Item (Order) COM Workflows Workflow Name Project
  • 117. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 117 ❏ Default Pricing Variable Map - Row Set - Basic ❏ Default Pricing Variable Map - Row Set ❏ Default Pricing Eligibility Variable Map - Row Set c Lock each Variable Map and release a new version of each of these maps. d Navigate to the Signals view, and query for “ReviseCopyOrder”. e Lock this signal and release a new version. Activating Validation Rulesets and Reloading Runtime Events Use the following procedure to activate data validation ruleset. To activate the data validation ruleset 1 Navigate to the Site Map, and query for Administration - Data Validation. 2 Click the Ruleset View hyperlink. ■ Query for the following rulesets in the Validation Ruleset applet: ■ SWI Order Validation Rule Set ■ SWI SRL Delete ■ SWI SRL Item ■ SWI SRL Modify 3 Click the Activate button to activate the rulesets. After you activate the rulesets, you need to reload the runtime events. Use the following procedure to reload the runtime events. To reload the runtime events 1 Within the Site Map, navigate to the Administration - Runtime Events screen. 2 Click the Events view hyperlink. 3 Within the Events list applet, click the Menu button, and select Reload Runtime Events. Oracle Advanced Queuing (AQ) Oracle Streams Advanced Queuing (AQ) is a database-integrated messaging infrastructure in Oracle database. AQ uses the functionality of the Oracle database to store messages in persistent queues. All operational benefits of the Oracle database such as high availability, scalability, and reliability are applicable to the messages and queues in AQ. Standard database features such as backup and recovery, security, and manageability are available to AQ. AQ has been implemented for the following outbound Web services in this release: ■ Special Rating List
  • 118. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 118 ■ Submit Order ■ Adjustment The following sections contain information about how to implement AQ in your Siebel application, as well as more detailed information about the outbound Web services listed above. Special Rating List This service is used to synchronize the modified friends and family list with the external BRM system. It is invoked through the Synchronize button in the Special Rating list applet. Use the following procedure to sync the modified list. 1 Navigate to Accounts > Account List view. 2 Query for the Target Account from the list. 3 Drill down on the account name. 4 Navigate to the Profiles view, and click on the Special Rating Profile subview. 5 Query for the target special rating list and click the Synchronize button. The Synchronize button invokes the "SWI Special Rating List - Synchronize Process" workflow using the Named Method Business Component user property. The SWI Special Rating - Synchronize Process workflow is a new workflow created for the AIA Comm 2.4 release. It is invoked through the Synchronize button, which is available in the Special Rating list applet (Account screen > Profiles view > Special Rating Profile). The workflow contains the steps to query for and synchronize the updated Special Rating List with BRM by calling the Proxy Business Service, as detailed below. Start > (Connector 0) > Query Special Rating List > Synchronize > Update List Synch Date > Upadate Items Synch Date > End 0 Note the following information about the SWISpecialRatingList outbound Web service: ■ It is a new Web service. ■ It is an asynchronous outbound Web service ■ Its namespace is http://siebel.com/asi This Web service is used to send the Updated/Modified Special Rating List details to BRM for synchronizing when the user clicks the Synchronize button in the Special Rating list applet. This AQ and connection factories are created in FMW and the same URI should be used in outbound Web service target address. Use the following procedure to update the target address. To update the target address 1 Naviate to the Site Map > Administration - Web Services screen. 2 Navigate to the Outbound Web Services aggregate view.
  • 119. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 119 3 Query for the "SWISpecialRatingList" service name. 4 Change the following field values in the Service Port applet: ■ Transport: JMS ■ Address: <Give the AQ URL in FMW> (for example, jms://java:comp/resource/ CommsJmsRP1/Queues/AIA_SPECIALRATINGJMSQ@java:comp/resource/CommsJmsRP1/ QueueConnectionFactories/QCF) 5 Save the record and click the Clear Cache button. Submit Order Outbound Web Service This outbound service is used to send the order details to AIA. The user initiates the service by clicking the Submit button on the order header form in the Order Entry view. Use the following procedure to initiate the Submit Order outbound service. To initiate the Submit Order outbound service 1 Navigate to the Sales Order screen > Order List view. 2 Query for the Target Sales Order. 3 Drill down on the Order #. 4 Click the Submit button. SISOMBillingSubmitOrder Web Service Workflow This is an existing workflow that submits an order from the Siebel CRM application to the billing application and creates a new account, if needed, in the billing application. Users initiate this workflow by clicking the Submit button on the order header form in the Order Entry view. Note the following information about the SWISubmitOrder outbound Web service: ■ It is a new Web service ■ It is an outbound Web service ■ Its namespace is http://siebel.com/asi Use this Web service to submit orders into the queue. This AQ and connection factories are created in FMW and the same URI should be used in outbound Web service target address. Use the following procedure to update the address: To update the address 1 Navigate to Site Map > Administration - Web Services screen. 2 Navigate to the Outbound Web Services aggregate view. 3 Query for the "SWISubmitOrder" service name. 4 Change the following field values in the Service Port applet:
  • 120. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 120 ■ Transport: JMS ■ Address: <Give the AQ URL in FMW> (for example, jms://java:comp/resource/ CommsJmsRP1/Queues/AIA_SALESORDERJMSQUEUE@java:comp/resource/ CommsJmsRP1/QueueConnectionFactories/QCF) 5 Save the record and click the Clear Cache button. SWICreateAdjustment Outbound Web Service This outbound service is used to Submit an Adjustment request to BRM. Users initiate the service by clicking the Submit button on the SIA CUT Adjustment External Line Items view. To initiate the SWICreateAdjustment outbound Web service 1 Navigate to the Billing Adjustments screen > SIA CUT Adjustment External Line Items view. 2 Query for the particular adjustment. 3 Click the Submit button. CMU SIA Submit Adjustment Request to External Workflow This workflow has been modified as part of the "Adjustment Revenue Leakage Enhancement" feature. This workflow submits the Adjustment Request to the external system by invoking an outbound Web service and changing the status of Adjustment Header to Submitted. Users initiates this workflow by clicking the Submit button in the Billing Adjustments screen. This workflow does the following: 1 Queries the adjustment request. 2 If the adjustment request is not approved, it changes the status of the request to Pending, and terminates. 3 If the adjustment request is approved, it reads the enterprise details, such as the enterprise server name, language, and locale. 4 Sets the enterprise details as part of the request message. 5 Makes an outbound call to the AQ. 6 Updates the Siebel database for the Adjustment Record to reflect the status as Submitted. SWICreateAdjustment Outbound Web Service Note the following information about the SWICreateAdjustment outbound Web service: ■ It is a new Web service ■ It is an outbound Web service ■ Its namespace is http://siebel.com/asi Use this Web service to Submit Adjustment Request into the queue. This AQ and connection factories are created in FMW and the same URL should be used in outbound Web service target address.
  • 121. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 121 Use the following procedure to update the address. To update the address 1 Navigate to Site Map > Administration - Web Services screen. 2 Navigate to the Outbound Web Services aggregate view. 3 Query for the "SWICreateAdjustment" service name. 4 Change the following field values in the Service Port applet. ■ Transport: JMS ■ Address: <Give the AQ URL in FMW> (for example, jms://java:comp/resource/ CommsJmsRP1/Queues/AIA_CMUREQADJIOJMSQUEUE@java:comp/resource/ CommsJmsRP1/QueueConnectionFactories/QCF) 5 Save the record and click the Clear Cache button. Configuring FMW URLs for Web Services Use the following procedures to configure FMW URLs for Web services. To configure FMW URLs for the outbound Web services 1 Log into the Siebel application as an administrator. 2 Navigate to the Site Map. 3 Click on Administration - Web Service > Outbound Web Services. 4 Query for the Name= *ABCS*. 5 Navigate to the Service Ports list applet and change the URI given by the ABS team. 6 Query for *JMS* and *Sync* and change the URI. (For example, http://ap6039fems.us.oracle.com:7797) To configure FMW URLs for inbound Web services 1 In Administration - Web Services > Inbound Web Services, make sure the corresponding Web services are active. If they are not, change the status from "Inactive" to "Active", and click the Clear Cache button. NOTE: Query for these inbound web services: * ISS *; * Update Order *; * SWI Update *, SWI* 2 Query for Name = SWI Account Update.
  • 122. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 122 3 In the middle Inbound Service Ports list applet, change the address port. Address: (example only) http://sdchs20n513.corp.siebel.com/eai_enu/ start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute&UserName=SADMIN&Pass word=MSSQL NOTE: Replace the string <web server>, <lang>, <UserName>, <Password> with correct data based on server information. 4 Repeat the preceding steps for all inbound Web services. Setting Up Order Creation Use the following procedures to enable component groups. To enable compgrps 1 Bounce the server after enabling the compgrp and synchronizing it. 2 Enable the following compgrps: ■ Siebel CME [Alias- Communications] ■ Siebel ISS [Alias- ISS] ■ Workflow Management [Alias- Workflow] ■ Communications Management [Alias CommMgmt] For more information about enabling compgrps, see “Enabling Compgrps” on page 146. Activating and Configuring ACR 463 Workflows The procedures in the following sections describe how to activate and configure the ACR 463 workflows. To activate workflows Use the following steps to activate all C/OM workflows. 1 Navigate to Site Map > Administration Business Process -> Workflow Deployment > Active Workflow Processes. 2 In the second applet, perform one of the two following actions: ■ Query for SIS*,Pri*,PSP*,ISS*,Elig*,eSales* ■ Query for the following groups: Eligibility & Comp, Asset Based Ordering, Pricer, eSales, Product Promotions, Configurator, C/OM UI processes, CUT eSales (for SIA, not for HOR), Product Recommendation, and delete them manually after deactivating the processes. To deactivate these groups, select them all and then select Deactivate Process. You can check the Deployment Status as Inactive. 3 Delete all the records. 4 In the first applet, perform one of the following two actions:
  • 123. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 123 ■ Query for SIS*,Pri*,PSP*,ISS*,Elig*,eSales* ■ Query for the following groups: Eligibility & Comp, Asset Based Ordering, Pricer, eSales, Product Promotions, Configurator, C/OM UI Processes, CUT eSales (for SIA, not for HOR), Product Recommendations. 5 Activate all of the workflows. Workflow Policy Setup and Configuration The following sections describe how to set up and configure workflow policies. Siebel Components Groups In order to enable the workflow policies, the following components should be configured and running on Siebel Server (in addition to the Application Object Manager component). Enabling EAI and Workflow Component Groups in the Siebel Server will start all the required Components stated above for transaction logging. To set the workflow component group ■ Navigate to Site Map > Administration > Server Management > Components, and query for Workflow* to check that the Workflow Management component and its components are enabled. To remove the existing triggers (if any) 1 Navigate to Administration > Server Management > Jobs. 2 Click New and type "Generate Triggers" under Component/Job to create a job for the Generate Triggers component. 3 Define the job parameters with the following values: ■ EXEC = TRUE ■ Privileged User = SADMIN ■ Privileged User Password = ******[Password for SADMIN] Component Name Component Alias Component Group Enterprise Integration Mgr EIM EAI EAI Object Manager (ENU) EAIObjMgr_enu EAI Workflow Process Manager WfProcMgr Workflow Workflow Process Batch Manager WfProcBatchMgr Workflow Workflow Monitor Agent WorkMon Workflow Generate Triggers GenTrig Workflow
  • 124. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 124 ■ Remove = TRUE ■ Trigger File Name: trigger.sql 4 Start the job. 5 Verify that the job was successful once it has completed. NOTE: Make sure that the SADMIN user has the necessary privileges for generating triggers before performing the following procedure. To generate the triggers 1 Navigate to Administration > Server Management > Jobs. 2 Click New and type "Generate Triggers" under Component/Job to create a job for the Gnereate Triggers component. 3 Define the job parameters with the following values: ■ EXEC = TRUE ■ Privileged User = SADMIN ■ Privileged User Password = ******[Password for SADMIN] ■ Trigger File Name: trigger.sql 4 Start the job. 5 Verify that the job was successful once the job has completed. Configuring Workflow Monitor Agent Use the following procedure to configure Workflow Monitor Agent. To configure Workflow Monitor Agent 1 Navigate to Site Map > Administration - Server Configuration > Enterprises > Component Definitions, and query for Workflow*. 2 Make a copy of the Workflow Monitor Agent in Administration - Server Configuration > Component Definition and change the name to "Workflow Monitor Agent SWI". 3 Change the Alias name to 'WorkMonSWI'. 4 Under Component Parameters, query for "Group Name" and type the SWI Account Update Policy Grp under Value to change the Group Name to “SWI Customer Update Policy Grp” in the Component Parameter applet. 5 Change the Action Interval to 5. 6 Change the Sleep Time to 15. (Select the Advanced button.) 7 Change the Default Task to 1. (Select the Advanced button.) 8 Click the Activate button to change the status of the new component to "Active".
  • 125. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 125 9 Synchronize the components. Configuring Default Tasks for Workflow Monitor Agent Server Manager contains a parameter called 'Show Advanced Objects' that controls the display of all the objects that are marked for the advanced user. Workflow Monitor Agent has a parameter called 'Default Tasks' which has been hidden and should only be displayed or available to advanced users. Use the following procedure to reveal this hidden parameter. To display the Default Tasks parameter 1 Navigate to Site Map > Administration - Server Configuration > Servers. 2 In the top Siebel Servers applet, select the server on which you want to modify the parameter. 3 Under the Component subtab, query for the Server Manager component. 4 Under the Component Parameter subtab, query for 'Show Advanced Objects'. 5 Change the value to 'True'. 6 Change the Default Task parameter to 1 (Select the Advanced button.) NOTE: You must log out from the current user session and log back into the application in order for the parameter to take effect. 7 Rename the existing diccache.dat file in the path <Installed Directory> sessiebsrvrbin. Starting Tasks for Workflow Monitor Agent for Customer Synchronization Use the following procedure to start tasks for the component that is online/enabled. To start tasks for Workflow Monitor Agent 1 Navigate to Site Map > Administration - Server Management. 2 Select "Tasks". 3 Query for the "WorkMonSWI" task and start it. You can also use Server Manager to start the task. 4 Start srvrmgr: srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u <userid> /p <password>. 5 Start the task for the WorkMonSWI component. After about five minutes, check for log details for the task for the new workflow monitor component "Workflow Monitor Agent SWI" by navigating to Administration > Server Management > Task.
  • 126. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 126 If there are errors, check to see if all configurations have been properly performed. If not, repeat the procedures detailed in “To generate the triggers” on page 124 after restarting the Siebel Server. Integration User Setup This section describes the integration user setup process. User credentials need to be configured (on the AIA side) for the Siebel Inbound Web Services call from the AIA side to avoid the boomerang effect. To set up the integration user 1 Log in as SADMIN. 2 Navigate to Administration-User > Employee view. The list applet should contain the integration user flag. 3 Configure a new integration user by setting the integration user flag to Y for a specific user. NOTE: The flag name is “Integration User Flag”. To set up and configure system preferences 1 Navigate to Administration - Application > System Preferences in the application, query for 'Enable AIA Comms' in the 'System Preference Name' field, and set the'System Preference Value' to 'TRUE'. 2 Set "Enable AIA Testing" to "TRUE". 3 Set "AIA Order Backup Path" to <the path where the xml files will be createdon the Siebel Server machine>/ For example, for Windows, this would be D:/. For Unix, this would be /export/home/qa1/orderbackup/ 4 Query for 'Validate Due Date' in the 'System Preference Name' field and set the 'System Preference Value' to 3. 5 Query for 'Cancel Error Mode' in the 'System Preference Name' field and set the 'System Preference Value' to 2. Enabling Dynamic Pricing Customers with the 'Dynamic Pricer' license will need to undertake the steps mentioned in the document to enable the execution of 'Dynamic Pricing Procedure'. In order to leverage the dynamic pricing procedure, customers have to perform following changes to the existing repository. The Siebel pricing module is available in multiple licensing modes and each mode is associated with either the 'Basic Pricing Procedure' or the 'Dynamic Pricing Procedure'.
  • 127. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 127 Basic Pricing Procedure ■ This procedure mimics the basic Siebel Pricer functionality that was available in Siebel version 7.7 applications. ■ Basic Siebel Pricer functionality includes list price, volume discounts, and service pricing. ■ It leverages the variable maps that do not contain the XA child variable maps. Dynamic Pricing Procedure ■ This provides the complete pricing capabilities such as attribute pricing, promotions, aggregate discounts, and so forth. ■ It leverages the variable maps that contain the XA child variable maps. ■ It is available only to those customers that have the 'Dynamic Pricer' license. To enable dynamic pricing ■ If you are running Siebel applications version 8.1.1 or above, navigate to Administration - Pricing > Price Lists, and select Enable Dynamic Pricing from the applet-level menu in the Price List applet. ■ If you are running Siebel applications versions earlier than 8.1.1, you must modify the signals mentioned in the following section manually. Modifying Signals Use the following procedure to modify signals. To modify signals ■ Navigate to Administration - Order Management > Signals, query for each signal mentioned in the following tables, and make the necessary modifications. Signal: CalculatePriceAndCheckEligibility Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: N/A Instance Type: N/A Fields: N/A
  • 128. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 128 Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Action: Y Signal: QuotesAndOrdersValidate Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: Order Instance Type: Header Fields: N/A Condition: N/A Active: Y Make similar changes to actions in this signal where: Mode: Order, Instance Type: Line Item Mode: Quote, Instance Type: Header Mode: Quote, Instance Type: Line Item Name Value SubPSPPricingWFName Dynamic Pricing Procedure SubPSPWFName Pricing and Eligibility Procedure - Default Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Eligibility Variable Map - Row Set Name Value SubPSPPricingWFName Dynamic Pricing Procedure SubPSPWFName Pricing and Eligibility Procedure - Default Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Eligibility Variable Map - Row Set
  • 129. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 129 Signal: VerifyItem Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: Agreement Instance Type: Header Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Make similar changes to actions in this signal where: Mode: Order, Instance Type: Header Mode: Quote, Instance Type: Header Signal: Product Recommendation Signal Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: Product Recommendation Driver Workflow Service Method: RunProcess Application Name: N/A Mode: N/A Instance Type: Line Item Fields: N/A Name Value SubPSPPricingWFName Dynamic Pricing Procedure SubPSPWFName Pricing and Eligibility Procedure - Default Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Eligibility Variable Map - Row Set
  • 130. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 130 Condition: GetProfileAttr('Block Variable Map Operations')='N' OR GetProfileAttr('Block Variable Map Operations') IS NULL Active: Y Signal: CalculatePriceExternal Actions and Parameters: Sequence: 1 Service Type: Business Service Service Name: Pricing Manager Service Method: RunPricerWorkflow Application Name: N/A Mode: N/A Instance Type: N/A Fields: N/A Condition: N/A Active: N/A Signal: SpreadDiscount, SpreadDiscount - All Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: Spread Discount Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: N/A Instance Type: N/A Name Value SubPSPPricingWFName Dynamic Pricing Procedure VariableMap 1 Default Product Recommendation Variable Map - Context Name Value SubPSPPricingWFName Dynamic Pricing Procedure
  • 131. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 131 Fields: N/A Condition: N/A Active: Y Signal: ApproveItem Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: PSP Workflow Driver Process Service Method: RunProcess Application Name: N/A Mode: Agreement Instance Type: Header Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Make similar changes to actions in this signal where: Mode: Order, Instance Type: Header Mode: Quote, Instance Type: Header Signal: CalculatePrice Actions and Parameters: Sequence: 1 Name Value SubPSPPricingWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Spread Discount Default Pricing Variable Map - Row Set Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set
  • 132. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 132 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: N/A Instance Type: N/A Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Signal: CalculatePriceAll Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: N/A Instance Type: Line Item Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set
  • 133. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 133 Signal: CalculatePrice_eSales Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: N/A Instance Type: N/A Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULLY Signal: CalculatePriceAll_eSales Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: N/A Instance Type: Line Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Action: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set Name Value SubPSPWFName Dynamic Pricing Procedure
  • 134. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 134 Signal: CalculatePrice_Configurator Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: N/A Instance Type: N/A Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Signal: CalculatePrice_Advisor Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: N/A Instance Type: N/A Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set Name Value
  • 135. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 135 Active: Y Signal: MergeIntoOnePackage Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: N/A Instance Type: Line Item Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Signal: OrderTemplate Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: Order Instance Type: Header Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set
  • 136. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 136 Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Make similar changes to actions in this signal where: Mode: Quote, Instance Type: Header Signal: OrderTemplateCopy Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: Order Instance Type: Header Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Signal: OrderTemplateSelectItems Actions and Parameters: Sequence: 1 Service Type: Workflow Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set
  • 137. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 137 Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: Order Instance Type: Header Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Signal: QuoteTemplateCopy Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: Quote Instance Type: Header Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Signal: QuoteTemplateSelectItems Actions and Parameters: Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set
  • 138. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 138 Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: Quote Instance Type: Header Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Signal: SetFieldValue Actions and Parameters: Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: N/A Instance Type: Header Fields: Discount; Price List; Currency Code Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set
  • 139. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 139 Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: Agreement Instance Type: Line Item Fields: Product; Quantity Requested; Unit Price; Discount Amount; Discount Percent; Currency Code; Item Price List; Covered Product Net Price Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: Order Instance Type: Line Item Fields: Product; Quantity Requested; Unit Price; Discount Amount; Discount Percent; Prod Prom Name; Currency Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set
  • 140. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 140 Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: Quote Instance Type: Line Item Fields: Product; Quantity Requested; Unit Price; Discount Amount; Discount Percent; Prod Prom Name; Currency Code; Item Price List; Covered Product Net Price Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Signal: Get Config Item Price Sequence: 1 Service Type: Workflow Service Name: Get Config Item Price - Driver Workflow Service Method: RunProcess Application Name: N/A Mode: N/A Instance Type: N/A Fields: N/A Condition: N/A Active: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row Set Name Value SubPSPWFName Get Config Item Price - Dynamic
  • 141. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 141 Signal: GetProdPrice Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: N/A Instance Type: N/A Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Signal: GetUserProdPrice Sequence: 1 Service Type: Workflow Service Name: PSP Driver Workflow Process Service Method: RunProcess Application Name: N/A Mode: N/A Instance Type: N/A Fields: N/A Condition: GetProfileAttr('SkipToEnd') = 'N' OR GetProfileAttr('SkipToEnd') IS NULL Active: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Product Pricing Variable Map - Row Set Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context User Product Pricing Variable Map - Context Variable Map - Row Set Product Pricing Variable Map - Row Set
  • 142. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 142 Signal: PDS GetPricing Sequence: 1 Service Type: Workflow Service Name: Dynamic Pricing Procedure Service Method: RunProcess Application Name: N/A Mode: N/A Instance Type: N/A Fields: N/A Condition: N/A Active: Y Running EIM Data Migration This section defines the detailed steps to run the EIM jobs for Siebel applications as a part of the Creating and Updating Credit Alerts for Collection Flows in AIA -Com 2.4. The ODI interface will be triggered to transport the required data for creating/updating Credit Alerts from BRM into the Siebel EIM tables. EIM scripts will be then executed to load the data into the SFA base tables. Before you begin your import, do the following: 1 Make sure that the Siebel Server is up and running. 2 Make sure that the Siebel EIM component is online and running properly. (Check this from the Administration - Server Configuration and Administration - Server Management screens.) 3 To avoid data loss, do not restart the Siebel server while the EIM job is running. 4 After you have completed loading data for one country, make a backup copy of the EIM logs for status verification. (These logs are located under siebsrvr/logs.) Use the following procedure to execute the EIM job. To execute the EIM job 1 Move the ProcessAlertsAndBillingProf.ifb file from <Tools Installation directory>/REPPATCH/ ACR463/EIM to <Siebel Installation Directory>/ses/siebsrvr/ADMIN. 2 Run the EIM job with the ProcessAlertsAndBillingProf.ifb configuration file. 3 Verify that the EIM job is successful.
  • 143. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 143 Runtime Configuration for Product Class and Attribute Definition Sync Use the procedures in the following sections to perform runtime configuration for Product Class and Attribute Definition Sync. User List Use the following procedure to add users to the user list. To add users to the user list 1 Navigate to Administration - Users > Users. 2 Add user name, User ID, and choose the "Siebel Administrator" responsibility. 3 Add email address in the contact information in the child applet. 4 Navigate to Administration -Group > User Lists. 5 Create a User List and add the users in the child applet. The "SCE Users" user list is created for the product class/attribute sync feature. You can add the users in the same user list. If the “SCE Users” list does not appear, create the list and add the users in the same user list. Run Time Events An email notification can be sent from product class definition, attribute definition and workspace definition. The following procedure describes how to add three runtime events to extract the email addresses from user lists in the PreInvoke method of Business Components. To add three runtime events to extract email addresses from users lists 1 Navigate to Administration - Run Time Events > Action Set. 2 Query for “EmailNotify”. Action 'GetEmailAddr' is added to get the email addresses from the user list. The Business Service context syntax is as follows "Parent BC Record Name";"Field Name in Child BC ";"BO Name ";"Parent BC";"Child BC" For instance: "SCE Users";"Email Address";"Account";"Account";"Contact" or
  • 144. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 144 "SCE Users";"EMail Addr";"User List";"User List";"User" The following table describes the three run time events that are added. Email Templates Use the following procedure to view the email templates that have been added. To view the added email templates 1 Navigate to Administration- Communications > All Templates. The following table describes the four templates that have been added: 2 To change the email body of the templates used to send emails from the workspace view, navigate to Administration Communication > All Templates > Template Items. The email templates detailed above are configured as user property values in the following Business Components: Sequence Object Type Object Name Event SubEvent Action Set Name 1 BusComp Attribute VOD BusComp PreInvokeMethod SendEmail EmailNotify 2 BusComp ISS Class VOD BusComp PreInvokeMethod SendEmail EmailNotify 3 BusComp ISS Joint Workspace BusComp PreInvokeMethod SendEmail EmailNotify Name Description Attribute Defn Template To send email from the Attribute Definition view Product Class Template To send email from the Product Class Definition view Workspace Attribute Defn Template To send attribute details from the Workspace view in emails Workspace Product Class Defn Template To send attributes from the Workspace view in emails Business Component User Property Template Name ISS Joint Workspace BusComp PackageNameList|Attribute Definition Workspace Attribute Defn Template ISS Joint Workspace BusComp PackageNameList|Product Class Definition Workspace Product Class Defn Template
  • 145. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 145 Communication Profile Use the following procedure to add From Email Address, POP server name, and SMTP server name in the communication profile. To add From Email Address, POP server name, and SMTP server name 1 Navigate to Administration - Communications > Communications Drivers and Profiles. 2 Create a new driver using the following values as an example: ■ Name: Internet SMTP/POP3 Server ■ Channel Type: Email ■ Inbound: Yes ■ Outbound: Yes ■ Channel String: POP3SMTP ■ Library Name: sscmmail 3 Set the profile in the child applet as Default SMTP profile. For Example - Default SMTP profile 4 Set the profile parameters in the grandchild Business Component using the following values as an example: ■ From Address: siebel.product.admin@demohost.siebel.com ■ POP3 Account Name: support ■ POP3 Account Password: support ■ POP3 Server: demohost.siebel.com ■ SMTP Server: rgmamersmtp.oraclecorp.com The communication profile has to set in the user property in the Business Components listed in the following table: Attribute VOD BusComp PackageNameList Attribute Defn Template ISS Class VOD BusComp PackageNameList Product Class Template Business Component User Property Template Name ISS Joint Workspace BusComp CommProfileOverride Default SMTP Profile Attribute VOD BusComp CommProfileOverride Default SMTP Profile ISS Class VOD BusComp CommProfileOverride Default SMTP Profile Business Component User Property Template Name
  • 146. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 146 Recipient Group The recipient group determines which Business Object is associated with the communication template. Only primary Business Component fields and their child Business Component fields are available to use in the template. Use the following procedure to add the recipient group. To add the recipient group 1 Navigate to Administration - Data > List of Values. 2 Query for "COMM_RECIP_GROUP" and add the recipient group. 3 To set the recipient group, navigate to Administration - Communications > All Templates > Advanced and select the recipient group from the drop-down list. The LIC values of the recipient groups added in Step 2 are set inthe user property of the Business Components listed in the following table: Enabling Compgrps Use the following procedures to enable compgrps. To enable compgrps for the Windows machine 1 Log in with system administrator credentials. 2 From Start > Run, type cmd. 3 Find the build-installed drive. 4 Type <Build>sessiebsrvrbin. 5 Execute the following command: Name Recipient Group Attribute Defn Template AttributeDefnBC Product Class Template ProductClassDefnBC Workspace Attribute Defn Template WorkSpaceBC Workspace Product Class Defn Template WorkSpaceBC Business Component User Property Recipient Group(LIC Value) ISS Joint Workspace BusComp RecipientGroup ISS Joint Workspace BusComp Attribute VOD BusComp RecipientGroup Attribute VOD BusComp ISS Class VOD BusComp RecipientGroup ISS Class VOD BusComp
  • 147. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 147 srvrmgr /e SIEBEL /s sdchs21n110 /g sdchs21n110:4330 /u SADMIN /p MSSQL <enter> 6 Run the command to verify how many components are enabled as "list compgrp". 7 Run the following command to enable the components group: Enable compgrp <Alias> 8 Verify that the command ran successfully. 9 After verifying that the command ran successfully, exit the application. 10 Restart the server. 11 After the machine is up, connect to server manger by running the command in Step 5 and verify enabled components groups by running the command " list compgrp ". To enable compgrps for UNIX 1 From the local machine, click Start > Run, and type telnet <Machine name> ex:telnet sdcpi43. 2 Log in with the instance and pwd: resource. NOTE: The instance is located in the URL. For example, if the URL contains 16661 = qa1, 16662 = qa2 instance and so on.) 3 Navigate to <Build>sessiebsrvrbin. 4 Run the following commands: smgr <enter> set server <machine name> <enter> list compgroup <enter> 5 Type the following command to enable the components group: Enable compgrp <Alias> 6 Verify that the command ran successfully. 7 After verifying that the command ran successfully, exit the application. Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 464 This section describes how to prepare the Siebel Server for CRM Desktop for ACR 464. To prepare the Siebel Server for CRM Desktop, perform the following tasks: 1 Importing Changes to the Siebel Repository from a Batch File on page 148 2 Importing Changes to the Siebel Repository from SIF Files on page 149 3 Applying Changes to the Siebel Database on page 151 4 Importing Seed Data on page 152
  • 148. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 148 Importing Changes to the Siebel Repository from a Batch File This section describes how to import schema changes into the Siebel Repository from a batch file. To import changes to the Siebel Repository from a batch file 1 On the computer where Siebel Tools is installed, open the tools.cfg file in a text editor. For more information, see Using Siebel Tools. 2 Make a note of the value that is set for the SymStrPrefix parameter. Keep this note. You will need it later to set the SymStrPrefix parameter back to the original value. 3 Set the SymStrPrefix parameter to the following value: SymStrPrefix = SBL_ 4 Save the tools.cfg file. 5 If Siebel Tools is open, then exit out of it, and then open it. 6 In Windows Explorer, open one of the following files in a text editor: ■ For a Siebel Business Application, open the following file: ACR464-HOR8112repositoryprojects_to_lock.txt ■ For a Siebel Industry Application, open the following file: ACR464-SIA8112repositoryprojects_to_lock.txt 7 In Siebel Tools, click Project in the Object Explorer. 8 In the Projects list, make sure the Locked property contains a check mark for each project that is listed in the projects_to_lock.txt file. It is recommended that you check these projects out to your local database, perform the configuration, and then check them back into the server database after you complete the configuration. 9 Edit the repository_import.bat file to reflect the database, username, folder names, Siebel Tools installation directories, and other information that is specific to your environment. The required parameters are documented in the file. 10 Close Siebel Tools. 11 Open a DOS command line, and then run the Repository_import.bat file. 12 Check the following log files in the <Siebel Tools installation>log directory to make sure that only insert operations were performed. ■ Applet.log ■ Business Component.log ■ Business Object.log ■ Business Service.log
  • 149. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 149 ■ Class.log ■ DLL.log ■ Integration Object.log ■ Link.log ■ Pick List.log ■ Screen.log ■ Symbolic String.log ■ Table.log ■ View.log If the log files indicate a problem, then create a service request (SR) on My Oracle Support. Alternatively, you can phone Global Customer Support directly to create a service request or get a status update on your current SR. Support phone numbers are listed on My Oracle Support. You can also contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services. Importing Changes to the Siebel Repository from SIF Files This section describes how to import schema changes into the Siebel Repository from sif files. You must import these files separately because each import might affect an object in a subsequent import. The objects must be merged. The batch import feature does not merge objects. To import changes to the Siebel Repository from sif files 1 Import the changes: a Open Siebel Tools, choose the Tools menu, and then the Import From Archive menu item. b In the Select Archive to Import dialog box, open the following file: ApplicationApplication-Update.sif c In the Import Wizard-Preview dialog box, make sure the following option is chosen, and then click Next: Merge the object definition from the archive file with the definition in the repository Siebel Tools displays the Import Wizard-Review Conflicts and Actions dialog box. d Wait until Siebel Tools finishes loading the sif file. You can view the status bar at the bottom of the dialog box to monitor progress. e If the Conflicting Objects window of the Import Wizard-Review Conflicts and Actions dialog box contains an item, then see “Resolving Conflicts” on page 150. Otherwise, continue to Step f. f In the confirmation dialog box, click Yes. g In the Import Wizard-Summary dialog box, click Finish. 2 Repeat Step 1 for each of the following files:
  • 150. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 150 ■ Business ObjectBusinessObject-Update.sif ■ TablebaseTable-Update.sif ■ Business ComponentBusinessComponent-Update.sif 3 Examine the following log file to make sure all imports executed successfully: Siebeltoolstempimportlog.txt 4 Compile all locked projects. 5 Set the SymStrPrefix parameter in the tools.cfg file to the original value you noted in Step 2 on page 148. 6 Save the tools.cfg file. 7 If Siebel Tools is open, then exit out of it, and then open it. Resolving Conflicts 1 In the Import Wizard-Review Conflicts and Actions dialog box, expand the tree and then click an object so that the Object Differences window populates. 2 Compare the object that appears in the Object Differences window to the child objects that are described in “Changes Made as a Result of Importing SIF Files” on page 152. 3 Do one of the following: a If the object appears in “Changes Made as a Result of Importing SIF Files” on page 152, and if there is no conflict, then do not adjust the default setting that Siebel Tools makes. For more information, see “Example of Using the Value from the SIF File” on page 150. b If the object does not appear in “Changes Made as a Result of Importing SIF Files” on page 152, then right-click the object in the Object Differences window, and then choose Repository. For more information, see “Example of Using the Value from the Repository” on page 151. c If the object appears in “Changes Made as a Result of Importing SIF Files” on page 152, and if there is a conflict, then create a service request (SR) on My Oracle Support. For more information, see “Example of a Conflict That Requires Additional Assistance” on page 151. 4 If other objects appear in the Conflicting Objects window, then repeat Step 3 for each object until all conflicts are addressed. 5 Click Next. Example of Using the Value from the SIF File In this situation, the object does not exist in the repository and Siebel Tools sets the Action to File by default. For example, the Siebel Universal Agent application includes a difference for the PIM Client Package screen in the Screen Menu Item object. There is no conflict because this is an intended change and the PIM Client Package screen does not exist in the repository.
  • 151. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 151 Example of Using the Value from the Repository When you import the Application.sif file, Siebel Tools displays 15 objects in the Conflicting Objects window. If you expand an object, then the Object Differences window displays the following differences for the Siebel Universal Agent application: ■ Some differences for the Page Tab object ■ Some differences for the Screen Menu Item object, including different Text for the Account Screen object and a different Sequence for the Activities Screen object. These differences are not intended. The Page Tab, Account Screen, and Activities Screen objects do not appear in “Changes Made as a Result of Importing SIF Files” on page 152. Therefore, you must set Action to Repository for each of these objects in order to keep the current repository values. Example of a Conflict That Requires Additional Assistance Assume you import the BusinessComponent-Update.sif and the ContactDBLastUpd field of the Employee business component includes a conflict because the field already exists in the repository. In this situation, it is likely that the field was created earlier for a customization. This field is an intended change and it appears in “Changes Made as a Result of Importing SIF Files” on page 152. In this situation, it is recommended that you create a service request (SR) on My Oracle Support. Alternatively, you can phone Global Customer Support directly to create a service request or get a status update on your current SR. Support phone numbers are listed on My Oracle Support. You can also contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services. Applying Changes to the Siebel Database 1 In the Object Explorer, click Table. 2 In the Tables list, issue the following query in the Name property: S_EVT_ACT OR S_PIM_INT_PKG OR S_PIM_INT_FILE OR S_PIM_INT_PKGFL OR S_PIM_INTFL_DEF 3 Click Apply/DDL. 4 In the Choose option dialog box, make sure the Apply option is chosen, and then click OK. If the Warning dialog box appears, then click OK. 5 In the Apply Schema dialog box, choose Current Query in the Tables drop-down list, and then enter the following information according to the type of database into which you are applying this schema change. These values might be different for your environment. Check with your database administrator if you are not sure about the correct values to enter. For more information, see Developing and Deploying Siebel Business Applicationson the Siebel Bookshelf 8.1 on Oracle Technology Network (OTN). Field MSSQL Oracle DB2 Tables Current Query Current Query Current Query Table space (Leave empty) DATA TBS_4K
  • 152. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 152 6 Click Apply. 7 Compile and deploy the SRF. Importing Seed Data The following procedure describes how to import seed data. To import seed data 1 Open the following file in a text editor: ACR464-HOR8112Seed_import.bat 2 Edit the Seed_import.bat file to reflect the database, username, folder names, Siebel Tools installation directories, and other information that is specific to your environment. The required parameters are documented in the file. 3 Open a DOS command line and then run the Seed_import.bat file. Changes Made as a Result of Importing SIF Files This section describes changes that are made to the Siebel Repository as a result of importing SIF files. 16K table space (Leave empty) (Leave empty) TBS_4K 32K table space (Leave empty) (Leave empty) TBS_32K Index space (Leave empty) DATA TBS_4K Storage control file (Leave empty) (Leave empty) (Leave empty) Database user (User name) (User name) (User name) Database user password (User password) (User password) (User password) ODBC data source (Data source) (Data source) (Data source) DDL file (Leave empty) (Leave empty) (Leave empty) Field MSSQL Oracle DB2
  • 153. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 153 Changes Made as a Result of Importing the Application-Update.sif File Table 8 describes changes made to applications as a result of importing the Application-Update.sif file.This sif file includes the new PIM Client Package screen of the screen menu item for these applications. Table 8. Changes Made as a Result of Importing the Application-Update.sif File Siebel Business Applications and Siebel Industry Applications Siebel Industry Applications The following applications are changed: ■ Siebel ERM Administration ■ Siebel Field Service ■ Siebel Marketing Enterprise ■ Siebel Partner Manager ■ Siebel Sales Enterprise ■ Siebel Universal Agent The following applications are changed: ■ Siebel Automotive ■ Siebel Consumer Sector ■ Siebel Financial Services ■ Siebel HTIM ■ Siebel Hospitality ■ Siebel Life Sciences ■ Siebel Loyalty ■ Siebel Power Communications ■ Siebel Public Sector
  • 154. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 154 Changes Made as a Result of Importing the BusinessObject-Update.sif File Table 9 lists the new business object components that are added into business objects as a result of importing the BusinessObject-Update.sif file. Table 9. Changes Made as a Result of Importing the BusinessObject-Update.sif File Business Object Siebel Business Applications Siebel Industry Applications Account The following business object components are added: ■ Account Contact ■ Account Industry ■ Account Organization ■ Account Position ■ Account Territory ■ Assignment Group ■ Industry The following business object components are added: ■ Account Address ■ Account Industry ■ Account Organization ■ Account Territory Contact The following business object components are added: ■ Account Contact ■ Business Address ■ Contact Organization ■ Opportunity Contact ■ Organization ■ Position The following business object components are added: ■ Account Contact ■ Contact Address ■ Contact Organization ■ Opportunity Contact Employee The following business object components are added to Siebel Business Applications and Siebel Industry Applications: ■ Employee Position ■ Employee Responsibility
  • 155. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 155 Changes Made as a Result of Importing the Table-Update.sif File Table 10 describes changes made to the S_EVT_ACT table as a result of importing the Table- Update.sif file. Changes Made as a Result of Importing the BusinessComponent-Update.sif File Table 11 describes changes made to business components as a result of importing the BusinessComponent-Update.sif file. Note that these changes apply to Siebel Business Applications and Siebel Industry Applications except for the change to the Business Address business component. The change to the Business Address business component described in Table 11 does not apply for Siebel Industry Applications. Opportunity The following business object components are added to Siebel Business Applications and Siebel Industry Applications: ■ Assignment Group ■ Opportunity AssignmentGroup ■ Opportunity Position Position The following business object components are added to Siebel Business Applications and Siebel Industry Applications: ■ Assignment Group ■ Assignment Group Position Intersection Table 10. Changes Made as a Result of Importing the Table-Update.sif File Siebel Business Applications Siebel Industry Applications Adds the following columns to the S_EVT_ACT table: ■ INTEGRATION_ID ■ INFO_SOURCE_CD Makes the following changes to the S_EVT_ACT table: ■ Changes the length of the INTEGRATION_ID column from 30 to 450 ■ Adds the INFO_SOURCE_CD column Table 11. Changes Made as a Result of Importing the BusinessComponent-Update.sif File Business Component Change to Business Component Field Action Adds the new CRMD Integration Id field. Employee Adds the new ContactDBLastUpd field. Changes the Text Length of the EMail Addr field from 50 to 100. Table 9. Changes Made as a Result of Importing the BusinessObject-Update.sif File Business Object Siebel Business Applications Siebel Industry Applications
  • 156. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 156 Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 467 Use the procedures in the following section to configure ACR 467. NOTE: For more information about ACR 467 and about Siebel Financial Services Customer Order Management for Banking functionality, see Siebel Order Management Guide Addendum for Financial Services. To access this guide, from within My Oracle Support, navigate to the Knowledge tab and search for Article ID 1171542.1. 1 Navigate to <Tools installation folder>REPPATCHACR467.zip. The ACR 467 folder contains the following subfolders: ■ LMU ■ SeedData ■ REPOSITORY ■ WORKFLOWS ■ Schema 2 Lock the following projects: ■ Table Asset ■ Table Closing Requirement Manager ■ Table FinancialServices ■ Table FinAccounts ■ Table Marketing ■ Table Order ■ Table Quote 3 Navigate to Tools > Import from Archive, and import the Table.sif file. NOTE: Use the Merge option within the Import Wizard. 4 Navigate to the Siebeltoolstempimportlog.txt file to verify that the objects imported correctly. 5 Select the table or tables that you want to apply to the physical database, click the Apply/DDL button, and select Apply. Contact Changes the Text Length of the Email Address field from 50 to 100. Position Changes the Text Length of the Active Email field from 50 to 100. Business Address Changes the Text Length of the Email Address field from 50 to 100. Table 11. Changes Made as a Result of Importing the BusinessComponent-Update.sif File Business Component Change to Business Component Field
  • 157. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 157 6 Choose the Current Query option. 7 In the Apply Schema dialog box, enter the appropriate values for your database platform. a For MSSQL, enter the appropriate values in the Database user, Database user password, and the ODBC data source fields. b For Oracle, enter the appropriate values in the Table space, Index space, Database user, Database user password, and the ODBC data source fields. c For DB2, enter the appropriate values in the Table space, 16K table space, 32K table space, Index space, Database user, Database user password, and ODBC data source fields. d For DB2/390, enter storage control file information, as well as information in the Database user, Database user password, and ODBC data source fields. NOTE: If you are implementing ACR 467 on DB2, you need to generate the storage control file. For information aobut how to do this, see Implementing Siebel Business Applications on DB2 for z/OS. This guide is available on the Siebel Bookshelf 8.1at http://www.oracle.com/technetwork/ documentation/siebel-087898.html. 8 Verify that the changes have been applied to the database. CAUTION: You must import the Table.sif file before you import the EIM.sif file. 9 Lock the following projects: ■ EIM Activity ■ EIM Common SIA ■ EIM Quote 10 Importing the EIM.sif file using the Tools > Import from Archive function. Use the Merge option within the Import Wizard. 11 Navigate to the Siebeltoolstempimportlog.txt file to verify that the objects imported correctly. 12 Repeat Step 5 through Step 7 to apply the DDL for EIM.sif. 13 Open tools.cfg from <Tools Install Directory>BinEnu and verify the [Siebel] section. Make sure that the SymStrPrefix entry has been set to SBL_ [Siebel] …….. .; SymStrPrefix parameter needs to be X_ for Siebel customers. SymStrPrefix = SBL_ …….. 14 In Siebel Tools, lock all the following projects: ■ Account ■ Account (SSE) ■ Asset Management ■ Cfg JS
  • 158. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 158 ■ Contact ■ Contact (SSE) ■ FINS Account Origination (Create this project if it does not already exist.) ■ FINS Financial Services ■ FINS Mortgage Application ■ FINS Needs Analysis ■ FINS Requirement Template ■ FINS Retirement Planning ■ Household ■ LS Pharma Call ■ LS Pharma Signature ■ MACD Performance ■ Oppty (SSE) ■ Order Entry ■ Product Selection UI ■ Quote ■ Quote (UI) ■ SIS OM Base Architecture ■ Symbolic Strings ■ Corresp ■ Account ■ Mail Agent ■ Accessibility ■ FINS Captive Finance - Fin Acct ■ LS Pharma Compliance ■ PUB Case ■ Schema ■ Product Data Services 15 Import the rest of the SIF files fromthe REPPATCHACR467REPOSITORY folder into Siebel Tools using the Import from Archive function. If you have not locked the required projects, you may receive a warning error message. Use the Overwrite option. 16 Import the SIF files from the following subfolders under the REPPATCHACR467REPOSITORY folder:
  • 159. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 159 ■ Applet ■ Application ■ Business Component ■ Business Object ■ Business Service ■ Integration Object ■ Project ■ Screen ■ Symbolic String . Use the following procedure to perform batch import of the SIF files. To perform batch import for ACR 467 ■ Run the following command: SET PCDTOOLSPATH=...... SET PCDDATASRC=ServerDataSrc SET PCDUSERNAME=<LOGIN> SET PCDPASSWORD=<PWD> %PCDTOOLSPATH%binsiebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p %PCDPASSWORD% /batchimport "Siebel Repository" merge ".Applet" ".LogAppletImp.log" %PCDTOOLSPATH%binsiebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p %PCDPASSWORD% /batchimport "Siebel Repository" merge ".Application" ".LogApplicationImp.log" %PCDTOOLSPATH%binsiebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p %PCDPASSWORD% /batchimport "Siebel Repository" merge ".Business Component" ".LogBusCompImp.log" %PCDTOOLSPATH%binsiebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p %PCDPASSWORD% /batchimport "Siebel Repository" merge ".Business Object" ".LogBusObjImp.log" %PCDTOOLSPATH%binsiebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p %PCDPASSWORD% /batchimport "Siebel Repository" merge ".Business Service" ".LogBusSvcImp.log" %PCDTOOLSPATH%binsiebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p %PCDPASSWORD% /batchimport "Siebel Repository" merge ".Integration Object" ".LogIntObjImp.log"
  • 160. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 160 %PCDTOOLSPATH%binsiebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p %PCDPASSWORD% /batchimport "Siebel Repository" merge ".Link" ".Log Link.log" %PCDTOOLSPATH%binsiebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p %PCDPASSWORD% /batchimport "Siebel Repository" merge ".Pick List" ".LogPickListImp.log" %PCDTOOLSPATH%binsiebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p %PCDPASSWORD% /batchimport "Siebel Repository" merge ".Screen" ".LogScreenImp.log" %PCDTOOLSPATH%binsiebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p %PCDPASSWORD% /batchimport "Siebel Repository" merge ".Symbolic String" ".Log SymStrImp.log" %PCDTOOLSPATH%binsiebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p %PCDPASSWORD% /batchimport "Siebel Repository" merge ".View" ".Log ViewImp.log" %PCDTOOLSPATH%binsiebdev.exe /c tools.cfg /d %PCDDATASRC% /u %PCDUSERNAME% /p %PCDPASSWORD% /batchimport "Siebel Repository" merge ".EIM" ".Log EIMImp.log" Use the following procedure to import the seed data for ACR 467. To import ACR 467 seed data 1 Create an ODBC entry for the database where you plan to import the seed data: a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC), navigate to the System DSN tab, and click Add. b Select the "Siebel Oracle90" driver (from Datadirect Technologies). c Enter a data source name (such as DevelopmentDB). d Enter the server name to connect to: For Oracle, enter the TNS service name that you created to connect Siebel Tools to the database. e Test your connection and click OK when tested successfully. 2 Navigate to the directory where you installed Siebel Tools and change the directory to REPPATCHACR467. 3 Before executing the next step, make sure that the dataimp.exe file exists in the <Tools Install Directory>/bin directory. 4 Depending upon the language that you are installing, complete either Step 5 or Step 6. 5 For ENU customers:
  • 161. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 161 a Run the following command: <Tools Install Directory>bindataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>REPATCHACR467SeedDataENUSeed_ACR467.dat/l <Tools Install Directory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools Install Directory>REPATCHACR467SeedDataENUACR467_seedimp.inp /q -1 /w n /en /t n /x R /n 100 /h log <Tools Install Directory> - Replace with your Siebel Tools install directory <ODBC Source Name> - Replace with ODBC name created in Step 1. b Review the <Tools Install Directory>tempdataimp_seed.log file to make sure that the import completed successfully. 6 For languages other than ENU, complete the following: Customers who are installing languages other than ENU need to import two .dat files - the base ENU seed.dat and the locale specific seed_locale_XXX.dat, where XXX is the language code. a Run the following command for seed.dat: <Tools Install Directory>bindataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>REPATCHACR467SeedDataSeed_ACR467.dat/l <Tools Install Directory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools Install Directory>REPATCHACR451SeedData ACR467_seedimp.inp /q -1 /w n /e n /t n / x R /n 100 /h log <Tools Install Directory> - Replace with your Siebel Tools install directory <ODBC Source Name> - Replace with the ODBC name created in Step 1 b Run the following command for seed_locale_XXX.dat: <Tools Install Directory>bindataimp /u SADMIN /p sadmin /f <Tools Install Directory>REPATCHACR467SeedDataLocal<LANG>seed_locale_xxx.dat /l <Tools Install Directory>tempdataimp_seed_lang.log /c <ODBC Source Name> /d <Table Owner> /i <Tools Install Directory>REPATCHACR467SeedDataENUkzhou.inp /q -1 /w y /e n /t n /x R /n 100 /h log <Tools Install Directory> - Replace with your Tools install directory <ODBC Source Name> - Replace with ODBC name created in Step 1 c Review the <Tools Install Directory>tempdataimp_seed.log file to make sure import completed successfully. 7 The following steps are only necessary for customers who are installing languages other than ENU: a Within Siebel Tools, navigate to Tools > Utilities > Locale Management to import LMU files for the specific language from the LMU folder into Siebel Tools. b Select Source Language = English American Target Language = <Specific Language> c Click the Import tab, browse to locate the LMU file you want to import, and click Import.
  • 162. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 162 8 Stop the Siebel Server, if it is running. 9 Within Siebel Tools, navigate to Menu > View >Options, select the Scripting tab, and specify the following path for the browser script compilation folder.: <Server IP address><SWE server Installed Location>eappwebPUBLICenu 10 Navigate to Tools > Compile Projects > All Projects option, compile the projects, and save the SRF file to <Siebel Server Install folder>objectsENUsiebel_sia.srf on the installed Siebel Server. 11 Start the Siebel Server. 12 Import the workflows listed in the following table into the Siebel application: a Select Workflow Process in Siebel Tools Object Explorer. b Right-click on Workflow Processes (the right-side pane) and import the .xmlfile into Siebel Tools from the Workflows folder. Refer to the list of workflows in the preceding table to know which project these workflows need to be imported into. Process Name New/ Modified? Project FINS AcctOrig Apply For Product - Account New FINS Account Origination FINS AcctOrig Apply For Product - Contact New FINS Account Origination FINS AcctOrig Apply For Product - Household New FINS Account Origination FINS AcctOrig AutoQuote New FINS Account Origination FINS AcctOrig Identity Check Process New FINS Account Origination FINS AcctOrig New Products & Services Process New FINS Account Origination FINS AcctOrig Profile Process - Order New FINS Account Origination FINS AcctOrig Set Applicant Group - Order Sub New FINS Account Origination FINS AcctOrig Set Applicant Group - Order New FINS Account Origination FINS AcctOrig Set Applicant Group - Quote Sub New FINS Account Origination FINS AcctOrig Set Applicant Group - Quote New FINS Account Origination SIS OM Active Order Sub-Process - Contact Modify SIS OM Base Architecture SIS OM Disconnect Products & Services Process - Contact Modify SIS OM Base Architecture SIS OM Modify Products & Services Process - Contact Modify SIS OM Base Architecture SIS OM New Products & Services Process - Contact Modify SIS OM Base Architecture SIS OM Suspend / Resume Products & Services Process - Contact Modify SIS OM Base Architecture
  • 163. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 163 c Check the status of the workflow process. If itis In-Progress, then make it complete by deploying the Workflow process. Do not click the Deploy + Activate button, as doing so will yield an error message. Click the Deploy button only. NOTE: You may receive the "This is an invalid Workflow…" error message while deploying the modified workflows from the list. Ignore the error and click Yes. d Repeat Step b through Step c for of all the workflows in the folder. e Log into the Siebel application as an administrator. f Navigate to Site Map > Administration - Business Process > Workflow Deployment > Repository Workflow Process. g Query for the workflow processes and activate them. Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 471 Use the instructions in the following sections to install and configure ACR 471. Installing ACR 471 1 Launch Siebel Tools connected to the server data source. 2 Navigate to Projects in the Object Explorer, and lock the following projects: ■ SIS OM Base Architecture ■ ISS Promotion Integration ■ Symbolic Strings ■ ISS Promotion Admin ■ UMSUI ■ ISS Promotion Workflow 3 Create a repository project called Headless Configuration. 4 In the tools.cfg file, change the SymStrPrefix = X_ parameter to SymStrPrefix = SBL_. 5 In Object Explorer, navigate to Symbolic String and create new records with the following values: ■ Name = SBL_PROM_AUTOMATCH ■ Current String Value = Promotion Automatch ■ Translate Flag = TRUE ■ Type = Conversion NOTE: You may need to expose this object type. To do so, navigate to View > Options. In the Object Explorer tab, check the checkbox for Symbolic Strings. ■ Name = SBL_APPLY_PROM_DEF
  • 164. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 164 ■ Current String Value = Apply Promotion Defaults ■ Translate Flag = TRUE ■ Type = Conversion ■ Project = Symbolic Strings ■ Name = SBL_LOG_HDLS_ERR ■ Current String Value = Log Error ■ Translate Flag = TRUE ■ Type = Conversion ■ Project = Symbolic Strings 6 Use the following steps to import the CSSHeadlessCfgService class: a Navigate to Tools > Import From Archive, and import the Class - CSSHeadlessCfgService.sif file. NOTE: If the "This operation should only be performed while connected to your local database" message appears, click Yes. b Choose the Merge option in the Conflict Resolution dialog box, and follow the steps to complete the import. 7 Import the Business Service - Headless Configuration Service.sif file using the steps in Step 6. 8 Import the Business Service - ISS Promotion Management Service.sif file using the steps in Step 6. 9 Import the Applet - UMF Message List SI.sif file using the steps in Step 6. 10 In Object Explorer, navigate to Workflow Process and import the workflow files inthe order given by the table below: a Right-click on the workspace and select Import Workflow Process. b Choose the <workflow_name>.xml file you want to import, and add it to its corresponding project. c Click Publish/Activate to change each workflow’s status from In Progress to Complete. 11 Within Object Explorer, navigate to Business Component, and search for the ISS Promotion Item Attribute Value business component. SI Workflow File Project 1) SIS OM Get Future Asset SubProcess.xml SIS OM Base Architecture 2) SIS OM Sync Delta SubProcess.xml SIS OM Base Architecture 3) ISS Promotion Upgrade Process.xml ISS Promotion Workflow 4) Headless Configuration Web Service.xml Headless Configuration
  • 165. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 165 12 Set the Sort Specification value to Created. 13 Compile the following locked projects into an SRF file: ■ ISS Promotion Integration ■ Headless Configuration ■ Symbolic Strings ■ ISS Promotion Admin ■ UMSUI 14 Unlock all projects, and log out of Siebel Tools. Setting Up the Application 1 Launch the application connected to the server data source and refer to the SRF that you compiled in Step 13 as a Siebel administrator. 2 Navigate to Administration - Business Processes > Workflow Deployment. 3 In the Repository Workflow Processes applet, query for the following workflows and activate them: ■ SIS OM Get Future Asset SubProcess ■ SIS OM Sync Delta SubProcess ■ ISS Promotion Upgrade Process Seed Data Signals Signal Name Action Sequence Type Service Name Service Method Sequence Type Service Name Service Method HdlsCfgSvcLoad 1 Business Service ISS Copy Service LoadEAI HdlsCfgSvcLoad ABO 1 Workflow SIS OM Get Future Asset SubProcess RunProcess
  • 166. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 166 Adding System Preferences ■ Navigate to Administration - Application > System Preferences and add a new system preference called Promotion Automatch with System Preference Value = "Y" Setting Up UMF Use the following procedure to set up UMF. To set up UMF 1 Navigate to view Administration - Order Management > Message Types, navigate to the All Message Types applet, and in the All Messages type applet, add new records with the values in the following table: HdlsCfgSvcSync 1 Business Service Remote Complex Object Instance Service SyncInstance HdlsCfgSvcSync ABO 1 Workflow SIS OM Sync Delta SubProcess 7.8 [SIS OM Sync Delta SubProcess] 8.1 [SIS OM Sync Delta SubProcess] Run Process Signal Name Action Sequence Type Service Name Service Method
  • 167. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 167 2 For the Headless Configuration Message record, in the Payload view tab, add four new records, with the following values for 'Payload Field' ■ Error Text ■ Id ■ Product Name ■ Promotion Instance Id 3 For the Headless Configuration Message record, in the Responses view tab, add two new records with the values in the following table: Adding Web Services Use the following procedure to add web services. To add web services 1 Navigate to Administration - Web Services > Inbound Web Services, and add a web service with the following details: Name Display Mode Group Title Full Text Headless Configuration Message Passive Promotion Product Structure Changed Product [Product Name] ([Id]) associated to promotion [Promotion Instance Id] has changed: [Error Text] Headless Configuration Error Message Passive Promotion Undo Apply Promotion A non- proceedable error was detected during processing of your last request. Your last request was rolled back. Sequence Name 1 Accept 2 Reject
  • 168. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 168 2 Click Clear Cache. For information about the process of enabling the automatic configuration of customizable products, see Siebel Order Management Guide. Back to Configuration Instructions for Enhancements and Updates Inbound Web Service Namespace Name Status http://siebel.com/OrderManagement/ HeadlessConfiguration HeadlessConfigurationWS Active Service Ports Name Type Business Service/ Business Process Name Transport Address Binding HeadlessConfigurationPort Workflow Process Headless Configuration Web Service HTTP http://<webserver>/ eai_<lang>/ start.swe?SWEExtSou rce=SecureWebServic e&SWEExtCmd=Exec ute&UserName=<Use rName>&Password= <Password> For example, http:// sdc78187svod/ eai_enu/ start.swe?SWEExtSou rce=SecureWebServic e&SWEExtCmd=Exec ute&UserName=SAD MIN&Password=SAD MIN SOAP_DOC_LITERAL SOAP_DOC_LITERAL Operations Name Method Display Name Authentication Type HeadlessConfiguration RunProcess None
  • 169. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 169 Instructions for ACR 474 and ACR 508 This section provides information, instructions, and guidelines for installing ACR 474 and ACR 508. CAUTION: Before you apply ACR 474, you must apply schema changes and import seed data from ACR 463. Repository changes for ACR 474 include repository changes that were made in ACR 463. For information about how to configure ACR 463, see “Instructions for ACR 463” on page 108. Release Notes for ACR 474 and ACR 508 The following topic documents known issues with ACR 474 and ACR 508. NOTE: For known issues that affect the installation of AIA 11.1, see Siebel Maintenance Release Guide, Version 8.1.1.6 on My Oracle Support. To access this guide, from within the Knowledge tab, search for Article ID 880452.1. USERS CAN ASSOCIATE PRODUCTS THAT ARE NOT RELEASED WITH NEW PRODUCTS WITH ACTIVEWORKSPACE Category: Web Service Subcategory: Other Product Version: AIA 11.1 Bug ID: 12396630 When users import the generated WSDL file into SOAP UI, create a product using SWIProductImportUpsert, and then create a product by associating it with products that are not yet released but that are under the same workspace and specify the ActiveWorkspaceFlag as 'N', the script does not throw an error stating that the products have not been released yet. 1 From within the Siebel application, navigate to Site Map > Administration Integration > Data Map Editor, and query for the SWI Product Structure object map. 2 In the bottom applet, query for the SWI ISS Product Structure Admin BusComp component map. 3 Within the Integration Field Map applet, click New, and enter "Product Name" in the Target Field Name field. 4 In the Source Expression Field Name, enter value [Component Product Name] and save the record. 5 From within the Siebel application, navigate to Site Map > Administration Integration > Data Map Editor, and query for the SWI Admin ISS Product Class Structure object map. 6 In the bottom applet, query for the SWI Structure Admin component map. 7 Within the Integration Field Map applet, click New, and enter Product Name in the Target Field Name field. 8 In Source Expression Field Name, enter value [Component Product Name]. 9 Save the record and log out of the Siebel application.
  • 170. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 170 ERROR IN IMPORTING AN XML FILE WITH EXPRESSION IN THE SOURCE FIELD Category: Application Deployment Manager Subcategory: Data Transformation (EAI) Product Version: AIA 11.1 Bug ID: 12952312 Use the following workaround to address this issue: 1 Navigate to Site Map > Administration-Integration > Data Map Editor. 2 Import the XML file from <Tools>/REPPATCH/AIA11.1/Xml folder. 3 Within the Integration Object Map applet, query for .SWI Asset Integration. 4 Within the Integration Component Map applet, query for Line_Item_to_Line_Item. 5 Click New, and add a record in the Integration Field Map applet with the following values: ■ Source Expression: "insert" ■ Target Field Name: operation 6 Query for the Status field and change the source expression: Source Expression: IIF([Status] IS NULL, LookupValue ("IMPL_PHASE", "Active"),[Status]) Target Field Name : Status Source Expression: "insert" Target Field Name: operation PROMOTION SYNC: PERIOD, GRACE PERIOD AND THEIR UOM ARE NOT SYNCHED TO SIEBEL Category: Web Service Subcategory: Other Product Version: AIA 11.1 Bug ID: 12651202 Sync BillofMaterial changes the values of Period, Period UOM and Grace UOM to the default values. Use the following workaround to address this issue 1 From within the Siebel application, navigate to Site Map > Administration Integration > Data Map Editor, and query for the SWI Promotion integration object map. 2 In the bottom applet, query for the SWI Promotion Header component map. 3 Within the Integration Field Map applet, click Query, and enter Grace Period UOM in the Target Field Name field. 4 In Source Expression Field Name, change the value from IIF([Grace Period UOM] IS NULL,LookupValue("PROMO_PERIOD_CD", "Days"),[Grace Period UOM]) to [Grace Period UOM], and save the record.
  • 171. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 171 5 Within the Integration Field Map applet, click Query, and enter "NRC Qty" in Target Field Name. 6 In Source Expression Field Name, change the value from IIF([NRC Qty] IS NULL,"1",[NRC Qty]) to [NRC Qty], save the record, and log out of the Siebel application. 7 Within the Integration Field Map applet, click Query, and enter Period in Target Field Name. 8 In Source Expression Field Name, change the value from IIF([Period] IS NULL,"1",[Period])to [Period], save the record, and log out of the Siebel application. 9 Within the Integration Field Map applet, click Query, and enter Period UoM in Target Field Name. 10 In Source Expression Field Name, change the value from IIF([Period UOM] IS NULL,LookupValue("PROMO_PERIOD_CD", "Years"),[Period UOM])to [Period UoM], save the record, and log out of the Siebel application. 251D ST2: NOTIFICATION TO SCE FROM SIEBEL MUST INCLUDE THE EFFECTIVE DATES Category: Oracle Order to Activate Integration Product Version: AIA 11.1 Bug ID: 9471608 Whenever a product class is created in the Siebel application, a notification is sent to the SCE "product to service mapping specialist". The notification must consist of effective dates of the product class. The notification sent by the Siebel application does not have the effective dates. Use the procedures in the following section to address this issue. Product Class Email Notification Use the following procedure to change the business object name. To change the LOV values for Product Class Definition 1 Navigate to the Administration - Data > List Of Values view. 2 Query for Type equals COMM_RECIP_SRC and Display Value equals Product Class Defn BC. 3 Change the values in the Language-Independent Code column to SWI ISS Class VOD BusComp (Notify). 4 Click Clear Cache to clear the cache. 5 Navigate to the Administration - Data > List Of Values view. 6 Query for Type equals COMM_RECIP_SRC and Display Value equals Product Class Defn BO. 7 Change the values in the Language-Independent Code column to SWI Admin ISS Class Definition 8 Click Clear Cache to clear the cache. Use the following procedure to edit/configure email template text.
  • 172. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 172 To edit/configure email template text 1 Create a notepad file called "Attribute_Version_Template.txt" and add the following values: Attribute Version Details ======================== ________________________________________ | Effective Start Date: [Required Start Date] | | Effective End Date: [Required End Date] | | VOD Version Number: [Version] ________________________________________ 2 Navigate to Administration - Communication > All Templates > Template Items. 3 Query for "Attribute Defn Template" and click on the Template Items View. 4 Attach the "Attribute_Version_Template.txt" file created in Step 1 in the template item. 5 Change the Iteration Child Business Component to "SWI Attribute Versions BusComp (Notify)" and check Substitute Values and Message Body. To change the LOV values 1 Navigate to the Administration - Data > List Of Values view. 2 Query for Type equals COMM_RECIP_SRC and Display Value equals Attribute Defn BC. 3 Change the values in the Language-Independent Code column to SWI Attribute VOD BusComp (Notify). 4 Click Clear Cache to clear the cache. 5 Navigate to the Administration - Data > List Of Values view. 6 Query for Type equals COMM_RECIP_SRC and Display Value equals Attribute Defn BO. 7 Change the values in the Language-Independent Code column to SWI Admin Attribute VOD Definition. 8 Click Clear Cache to clear the cache. Use the following procedure to change the LOV values for Product Class Email Notification. Attribute Details Email Notification Use the following procedure to change the business object.
  • 173. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 173 To change the BO name to communication template 1 Navigate to Administration - Communication > All Templates > Templates. 2 Query for "Product Class Template" and click on Simple View. 3 In Pick Available Substitutions change the object to "SWI Admin ISS Class Definition". Use the following procedure to edit/configure email template text. To edit/configure email template text 1 Create a notepad file called "Class_Version_Template.txt" and add the following values: Product Class Version Details ============================= _____________________________________________________ | Effective Start Date: [Required Start Date] | | Effective End Date: [Required End Date] | | VOD Version Number: [Version] ______________________________________________________ 2 Navigate to Administration - Communication > All Templates > Template Items. 3 Query for "Product Class Template" and click on Template Items View. 4 Attach the "Class_Version_Template.txt" file created in Step 1 in the template item. 5 Change the Iteration Child Business Component to"SWI ISS Product Versions BusComp (Notify)" and check Substitue Values and Message Body. Use the following procedure to change the LOV values for Attribute Email Notification. To change the LOV values 1 Navigate to the Administration - Data > List Of Values view. 2 Query for Type equals COMM_RECIP_SRC and Display Value equals Product Class Defn BC. 3 Change the values in the Language-Independent Code column to SWI ISS Class VOD BusComp (Notify). 4 Click Clear Cache to clear the cache. 5 Navigate to the Administration - Data > List Of Values view. 6 Query for Type equals COMM_RECIP_SRC and Display Value equals Product Class Defn BO. 7 Change the values in the Language-Independent Code column to SWI Admin ISS Class Definition 8 Click Clear Cache to clear the cache.
  • 174. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 174 SET PRICING COMMIT TYPE AND DYNAMIC DISCOUNT METHOD Category: Web Service Subcategory: Other Product Version: Siebel 8.1.1.3 Bug ID: 11724422 This bug enhances the Product/Promotion Web Service to support more attributes. Use the following workaround to address this issue. To address Bug 11724422 1 Within the Siebel application, navigate to Site Map > Administration Integration > Data Map Editor. 2 Query for the "SWI Promotion" integration object map. 3 Query for "SWI Promotion Header" integration component map in the bottom applet. 4 Click New in the Integration Field Map Applet, and enter the following values: a Enter "Pricing Commit Type" in Target Field Name. b In the Source Expression field name enter "IIF([Pricing Commit Type] IS NULL,LookupValue("PRICE_OVERRIDE_TYPE", "Dynamic"),[Pricing Commit Type])" 5 Save the record. 6 Click New in the Integration Field Map Applet, and enter the following values: a Enter "Dynamic Discount Method" in Target Field Name b In the Source Expression field name enter "IIF([Dynamic Discount Method] IS NULL , LookupValue("DISCOUNT_OVERRIDE_TYPE", "Amount") ,[Dynamic Discount Method])" 7 Save the record and close the Siebel application. ERROR UPDATING A PROMOTION IN SIEBEL WITH SYNCCHILD FLAG SET AS 'Y' Category: Web Service Subcategory: Other Product Version: Siebel 8.1.1.3 Bug ID: 11842102 To address Bug 11842102 1 Within the Siebel application, navigate to Site Map > Administration Integration > Data Map Editor. 2 Query for the "SWI Promotion Override Internal to External" integration object map. 3 Query for "Product Components" integration component map in the bottom applet.
  • 175. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 175 4 Change the Source Componenet Map to SWI ISS Promotion Product Component Override from SWI ISS Promotion Product Components 5 Save the record and close the Siebel application. Unable to Merge Contacts after Applying Siebel OnDemand/OnPremise Category: Data Quality Subcategory: Deduplication Product Version: 8.1.1.4 Change Request: 12-204Y58X While merging two contacts, an error is thrown:Could not find 'Class' Named 'Merge Service ODOP'. This object is inactive or non-existent. (SBL-DAT-00144) The MergeAction runtime event refers to the the Merge Service ODOP business service, which is not present in the repository. To avoid this error, inactivate the MergeAction runtime event: 1 Log into the Siebel application, and navigate to Administation - Runtime Events > Action Sets. 2 Query for the MergeAction action set. 3 Uncheck the Active check box to inactivate this action set. 4 Navigate to the Events view, and from the applet menu, select the Reload Runtime Events menu option. MOVE ORDER TRANSFER RESULTS IN EMPTY STATUS AS OF HEADER FIELD Category: Comm Media Energy Subcategory: Order Management Product Version: 8.1.1.4 Change Request: 12-1XTI4Q6 MOVE ORDER TRANSFER RESULTS IN EMPTY STATUS AS OF HEADER FIELD. Use the following workaround to address this issue: 1 Within Siebel Tools, navigate to Business Component and query for MACD Order Entry - Orders or MACD Quote. 2 In MACD Order Entry - Orders add a field with the following values: ■ Name: As Of Date ■ Column: STATUS_DT ■ Type: DTYPE_UTCDATETIME 3 In MACD Quote, add a field with the following values: ■ Name: As Of Date
  • 176. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 176 ■ Column: STATUS_DT ■ Type: DTYPE_UTCDATETIME 4 Navigate to Integration Object, and query for SIS OM Order or SIS OM Quote. 5 Add the Status As Of Date field to IC MACD Quote, and add the As Of Date field to IC MACD Order Entry - Orders. 6 Navigate to Business Service, and query for "SIS OM PMT Service". 7 Navigate to Business Service User Properties, and add a new user property with the following values: ■ Name "SIS OM Quote.Header:SIS OM Order.Header Map 302" ■ Value: "[Status As Of Date]:[As Of Date]" 8 Compile the changes to the SRF. CLEAR FULFILLMENT STATUS AND STATUS CONTEXT FOR CANCEL ORDER Category: Comm Media Energy Subcategory: Billing Management Product Version: 8.1.1.4 Change Request: 12-1ZVR997 CLEAR FULFILLMENT STATUS AND STATUS CONTEXT FOR CANCEL ORDER 1 Log into Siebel Tool, and query for the SWICancel Sales Order workflow. 2 Click Revise in the WF/Task Editor Toolbar to create a new version of the completed workflow and increment the version number 3 Right-click SWICancel Sales Order (the one with status In Progress) and select Edit Workflow Process. 4 In the Workflow Designer, select the Siebel Operation Step called "Update Fulfillment Mode and Status for Header". 5 Under the Input Field Argument tab in the Multi-Value Property Window for the Update Fulfillment Mode and Status for Header operation step, add the following two new records to configure the input arguments: 6 Add a new Siebel Operation Step between "Update Fulfillment Mode and Status for Header" (Siebel Operation Step) and "Submit" (Sub Process). Field Name Type Value Fulfillment Status Code Literal Back Office Error Text Literal
  • 177. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 177 7 Right-click, select View Properties Window and modify the properties of the Siebel Operation Step as follows: 8 Under the Input Field Argument tab in the Multi-Value Property Window for the preceding step, add the following new records to configure the input arguments: 9 Under the Search Spec Input Arguments tab in the Multi-Value Property Window for the preceing step, add the following new records to configure the search specification: 10 Save all of your changes and publish/activate the workflow. PROBLEM WITH ADJUSTMENT EFFECTIVE DATE Category: Comm Media Energy Subcategory: Billing Management Product Version: 8.1.1.4 Change Request: 12-1ZOI2LP The Effective Adjustment field stores only the Date field not the time value. Use the following workaround to address this issue: Before you begin, within My Oracle Support, navigate to the Knowledge tab and search for Article ID 557191.1. Copy the FR_12-1ZV9SD1_AIA25_Invoice.sif file attached to the article. Table Changes Use the following procedure to edit the S_INV_ADJ table. Business Component Order Entry - Line Items Business Component Order Entry - Line Items Operation Update Name Update Fulfillment Status and Status Context for Line Items Field Name Type Value Fulfillment Status Code Literal Status Context Literal xpression Business Component Filter Business Component Type Search Specification Order Entry - Orders Order Entry - Line Items Expression "[Order Header Id] ='" + [&Object Id] + "'"
  • 178. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 178 To edit the S_INVOICE_ADJ table 1 Log into Siebel Tools, and from the menu bar, select Import from Archive. 2 Import the "FR_12-1ZV9SD1_AIA25_Invoice.sif " file using merge as the Conflict Resolution Option. 3 Query for the 'S_INVOICE_ADJ' OR 'S_INVC_ADJ_ITEM' tables. 4 Select the rows and click the Apply/DDL button. 5 Compile the changes to the srf. Business Component Changes To edit the CMU Billing Invoice Adjustment BC 1 Log into Siebel Tools, and query for the CMU Billing Invoice Adjustment business component. 2 Change the following column for the Adjustment Effective Date field for the business component: 3 Save the changes, and then compile them to the SRF. To edit the CMU Invoice Adjustment BC 1 Log into Siebel Tools, and query for the CMU Invoice Adjustment business component. 2 Change the following column for Adjustment Effective Date field: 3 Save the changes, and then compile them to the SRF. To edit the FS Invoice Adjustment BC 1 Log into Siebel Tools, and query for the FS Invoice Adjustment business component. 2 Change the following column for the Adjustment Effective Date field: 3 Save the changes, and then compile them to the SRF. Name Value Type DTYPE_UTCDATETIME Name Value Type DTYPE_UTCDATETIME Name Value Type DTYPE_UTCDATETIME
  • 179. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 179 To edit the SIA Invoice Adjustment External Items BC 1 Log into Siebel Tools, and query for the SIA Invoice Adjustment External Items business component. 2 Change the following column for the Adjustment Effective Date field: 3 Save the changes, and them compile them to the SRF. To edit the CMU Billing Invoice Adjustment External Items BC 1 Log into Siebel Tools, and query for the CMU Billing Invoice Adjustment External Items business component. 2 Change the following column for the Adjustment Effective Date field: 3 Save your changes, and then compile them to the SRF. To edit the CMU SIA Invoice Adjustment External Items BC 1 Log into Siebel Tools, and query for the CMU SIA Invoice Adjustment External Items business component. 2 Change the following column for the Adjustment Effective Date field: 3 Save the changes, and then compile them to the SRF. To edit the CMU Invoice Adjustment External Items BC 1 Log into Siebel Tools, and query for the CMU Invoice Adjustment External Items business component. 2 Change the following column for the Adjustment Effective Date field: Name Value Type DTYPE_UTCDATETIME Name Value Type DTYPE_UTCDATETIME Name Value Type DTYPE_UTCDATETIME Name Value Type DTYPE_UTCDATETIME
  • 180. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 180 3 Save your changes, and then compile them to the SRF. Integration Object Changes To edit the CMU Request Adjustment IO 1 Log into Siebel Tools, and query for the CMU Request Adjustment integration object. 2 Query for FS Invoice Adjustment integration component. 3 Change the type for the Adjustment Effective Date integration component field: 4 Query for the SIA Invoice Adjustment External Items integration component. 5 Change the following Data Type for the Adjustment Effective Date integration component field: 6 Save your changes, and then compile them to the SRF. To edit the CmuRequestAdjustmentIo IO 1 Log into Siebel Tools, and query for the CmuRequestAdjustmentIo integration object. 2 Query for the FS Invoice Adjustment integration component. 3 Change the type for the Adjustment Effective Date integration component field: 4 Query for the SIA Invoice Adjustment External Items integration component. Name Value Data Type DTYPE_UTCDATETIME External Data Type DTYPE_UTCDATETIME Name Value Data Type DTYPE_UTCDATETIME External Data Type DTYPE_UTCDATETIME Name Value Data Type DTYPE_UTCDATETIME External Data Type DTYPE_UTCDATETIME
  • 181. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 181 5 Change the Data Type for the "Adjustment Effective Date integration component field: 6 Save your changes, and then compile them to the SRF. PRODUCT SYNC FAILS FROM SIEBEL TO BRM Area: Comm/Energy Subarea: Order Management Product Version: Siebel 8.1.1.3 Fix Pack Change Request: 12-1YOWCOT/Bug # 9851535 In Siebel 8.1.1.3, product synchronization between the Siebel application and BRM fails. Use the following workaround to address this issue. To address Bug 9851535/CR 12-1YOWCOT 1 From within the Siebel application, navigate to Site Map > Administration Integration > Data Map Editor, and query for the Product Integration integration object map. 2 In the bottom applet, query for the Product integration component map from the bottom applet. 3 Within the Integration Field Map applet, click Query, and enter “Pricing Commit Type” in the Target Field Name field. 4 In Source Expression Field Name, enter "IIF([Pricing Commit Type] IS NULL,LookupValue("PRICE_OVERRIDE_TYPE", "Dynamic"),[Pricing Commit Type])". 5 Save the record. 6 Within the Integration Field Map applet, click Query, and enter "Dynamic Discount Method" in Target Field Name. 7 In Source Expression Field Name, enter "IIF([Dynamic Discount Method] IS NULL , LookupValue("DISCOUNT_OVERRIDE_TYPE", "Amount") ,[Dynamic Discount Method])". 8 Save the record and log out of the Siebel application. Error Message Occurs When Variable Maps Released Area: Comm/Energy Subarea: Order Management Product Version: Siebel 8.1.1.3 Fix Pack Change Request: 12-1YK6RG0 Name Value Data Type DTYPE_UTCDATETIME External Data Type DTYPE_UTCDATETIME
  • 182. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 182 Use the following workaround to address this issue. To address CR 12-1YK6RG0 1 From within the Siebel application, navigate to Site Map > Administration - Order Management > Variable Maps and query for the"Default Pricing Variable Map - Row Set" variable map. 2 Rename the variable map to "Default Pricing Variable Map - Row Set - original". 3 Copy the variable map from the applet-level menu, and rename it as "Default Pricing Variable Map - Row Set". 4 Lock the variable map and then release it. 5 Follow Step 1 through Step 4 for the "Default Pricing Eligibility Variable Map - Row Set" variable map. Siebel Workflow Process Manager Leaks Memory Category: Comm Media Energy Subcategory: Order Management Product Version: Siebel 8.1.1.1 QF7103 Change Request: 12-1Y0AZBZ Siebel workflow process manager leaks memory and crashes in performance, scalability, and reliability (PSR) testing after 20 hours of running with zero seconds of think time. Workaround: Enable memory-based recycling on workflow process manager. For information about configuring memory-based server component recycling, refer to Siebel System Administration Guide on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html. Error Messages Translated Incorrectly Category: Comm Media Energy Subcategory: Order Management Product Version: Siebel 8.1.1.1 QF7103 Change Request: 12-1VBS4SZ, 12-1VBS4UF, 12-1VBS4VL To address CR 12-1VBS4SZ, CR 12-1VBS4VL, and CR 12-1VBS4VL 1 Navigate to Administration - Data Validation > Validation Messages screen and query for the following Message Code: SWI_PROD_VAL_ASSET or SWI_PROD_VAL_ORDER or SWI_PROD_VAL_QUOTE 2 Add the missing translations in the Translations applet.
  • 183. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 183 Follow-On Orders Can Be Submitted Before Base Orders Category: Comm Media Energy Subcategory: Order Management Product Version: Siebel 8.1.1.1 QF7103 Change Request: 12-1XTI4LP No error occurs when a Follow On order is submitted after the Base Order is cancelled. To address CR 12-1XTI4LP 1 Within the Siebel application, edit the Change the Submit Order workflow (SISOMBillingSubmitOrderWebService) to add this logic: a For each root line item, check if it has Base Order Line Item Id. b Get the Order Id of the Base Order Line Item Id. c Check if the status of the order is Pending. If it is Pending, the base order was not submitted. Enter an error message saying, 'Submit base order %1 before follow-on order'. NOTE: Implement this logic only if you are using follow-on orders, as this logic will affect the time that it takes to submit an order. Follow-On Orders Can Be Submitted Before Base Orders Category: Comm Media Energy Subcategory: Order Management Product Version: Siebel 8.1.1.1 QF7103 Change Request: 12-1XTI4NO Follow-On orders can be submitted for Cancelled Base Order. To address CR 12-1XTI4NO 1 Within the Siebel application, edit the Change the Submit Order workflow (SISOMBillingSubmitOrderWebService) to add this logic: a For each root line item, check if it has Base Order Line Item Id. b Get the Order Id of the Base Order Line Item Id. c Check if the status of the order is Pending. If it is Pending, the base order was not submitted. Enter an error message saying, 'Submit base order %1 before follow-on order'. NOTE: Implement this logic only if you are using follow-on orders, as this logic will affect the time that it takes to submit an order. Sales Order Form Buttons Not Disabled After Cancel Order Starts Category: Comm Media Energy
  • 184. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 184 Subcategory: Order Management Product: Siebel 8.1.1.1 QF7103 Change Request: 12-1XTI4UE After clicking the Cancel Order button, all other buttons on the Sales Order form are not disabled, so users can press buttons to interfere with cancel processing. To address CR 12-1XTI4UE 1 Navigate to Siebel Tools > Applets and query for "Order Entry - Order Form Applet Dashboard (Sales)". 2 Navigate to Applet User Properties. 3 Query for CanInvokeMethod*, and verify that all of the buttons that need to be disabled are present. If they are not present, you need to create CanInvokeMethod:Method name value IIf([Active],IIf(([Status] = LookupValue('FS_ORDER_STATUS','Cancel pending')) OR ([Status] = LookupValue('FS_ORDER_STATUS','Cancelled')) OR ([Status] = LookupValue('FS_ORDER_STATUS','Pending Cancel')), 'FALSE','TRUE'),'FALSE') 4 For existing CanInvokeMethod*, append the value "IIf(([Status] = LookupValue('FS_ORDER_STATUS','Cancel pending')) OR ([Status] = LookupValue('FS_ORDER_STATUS','Cancelled')) OR ([Status] = LookupValue('FS_ORDER_STATUS','Pending Cancel')), 'FALSE','TRUE'),'FALSE')" with logical OR operator 5 Compile the changes. COPY ORDER DOES NOT ASSIGN NEW ASSET INTEGRATION ID FOR COPIED ORDERS Category: Comm Media Energy Subcategory: Order Management Product Version: Siebel 8.1.1.1 QF7103 Change Request: 12-1XVFM9R To address CR 12-1XVFM9R ■ It is recommended that you use the Favorites menu option instead of the Copy Orders menu option for Asset-Based Ordering (ABO) flows. This is because copying AssetIntegrationId does not work for new orders, and Modify or Delete orders should not generate new AssetIntegrationIds. ■ CR 12-1TU8OYZ Description: The Discount Override fix is not working in MACD for Non-Residential Accounts (asset-quote). Workaround: Contact Technical Support for the workaround for this issue.
  • 185. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 185 ■ CR 12-1TK6WV1 Description: Suspend/Resume and move charges are applied to Simple Service Bundles in Nested SBs after reprice. Workaround: Use Reprice to see all charges. ■ Bug # 8979872/CR 12-1UPWTKJ Description: Error upon clicking the Revise button within Sales Order > Line Items tab. Workaround: Use the following procedure to address this issue. To address Bug #8979872/CR 12-1UPWTKJ 1 Log into Siebel Tools. 2 Within the Object Explorer, select Applet. 3 Query for the Order Entry - Order Form Applet Dashboard (Sales) applet. 4 Modify the applet user property sequence to: ■ Name: Named Method 1: Revise Order ■ Value: ‘INVOKE’, ‘ReviseCopyOrder’ ■ Name: Named Method: ReviseOrder ■ Value: 'INVOKESVC', 'Workflow Process Manager', 'RunProcess', '"ProcessName"', '"SWIReviseOrderValidation"', '"RowId"', '[Id]' 5 Save the changes and compile the applet to the SRF. ■ CR 12-1UVNZ65 Description: Net Price is carried forward for One-Time Products in MACD Operation. Workaround: Use the following workaround to address this issue. To address CR 12-1UVNZ65 1 Within the Siebel application, navigate to the Sales Order screen. 2 Click the List link and navigate to the Sales Order Details screen. 3 Drill down on the Order # and navigate to the Line Items view. 4 Within the Line Items list applet, select Reprice All from the menu. ■ CR 12-1UK1DKW Description: The Cancel Error Mode system preference default value should be '3'. Workaround: Use the following workaround to address this issue. To address CR 12-1UK1DKW 1 Within the Siebel application, navigate to Administration - Application > System Preferences.
  • 186. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 186 2 Within the System Preference Name field, query for “Cancel Error Mode” and set the value of the System Preference field to 3. 3 Restart the Siebel Server. ■ CR 12-1T03IG9 Description: When the due date of a root product in a Customizable Product is nullified, order validation does not occur. Workaround: Use the following workaround to address this issue. To address CR 12-1T03IG9 1 Within the Siebel application, navigate to Site Map > Administration - Data Validation. 2 Click the Ruleset hyperlink, and query for ‘SWI Order Validation Rule Set’ in the Ruleset applet. 3 Click Revise to revise the ruleset. 4 Click the ‘SWI Order Validation Rule Set’ hyperlink, and query for ‘SWI Validate Due Date’ in the Rules applet. 5 Modify the rules property as follows: ■ Apply To: All Records 6 Activate the ruleset. Unpacking the AIA251.zip File 1 Navigate to the Siebel Tools installation directory <Tools Install Directory>REPPATCH. 2 Unzip the AIA251.zip file. This will create the following directory structure: <Tools Install Directory>REPPATCHAIA251 The AIA251 folder that you create will contain the following subfolders and files: ■ ACR474.zip. This file contains the repository changes. ■ ACR474_SEED. This file contains the seed data changes. ■ ACR474_Workaround. This file contains the Release Notes and workaround information. ■ 8113_Addendum. 3 Unzip the ACR474.zip file. This will create the following directory structure: <Tools Install Directory>REPPATCHAIA251ACR474 The ACR474 folder that you create will contain the following subfolders: ■ DMGSchemaChanges ■ EIM
  • 187. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 187 ■ HTML ■ LMU ■ SeedData ■ SIFFiles ■ WebTemplates ■ WFs Use the following procedure to apply the schema changes to the server database. NOTE: The following instructions refer to the folders specified in Step 2 in the previous task. Applying Schema Changes to the Database As part of the AIA 2.5 release, schema changes have been done on the database. The following two procedures describe how to import the ACR463_Tables.sif and ACR463_EIMTables.sif files into the repository. The ACR463_Tables.sif file has all the changes for the following changes to existing tables: ■ S_ALERT_CUT ■ S_ADDR_PER ■ S_ADDR_PER_UCMX ■ S_ASSET ■ S_BULK_REQ ■ S_CONTACT ■ S_CON_ADDR ■ S_INV_PROF ■ S_INVOICE_ADJ ■ S_ORDER ■ S_ORDER_ITEM ■ S_ORG_EXT ■ S_PROD_INT ■ S_QUOTE_ITEM ■ S_SRV_ORD_FAIL ■ S_SRV_REQ ■ S_SPL_RATE_ITEM ■ S_SPL_RATE_LST
  • 188. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 188 To import the ACR463_Tables.sif file into the repository 1 Lock the following projects before import: ■ CUT Newtable ■ Table Asset ■ Table BulkRequest ■ Table Invoice ■ Table Order ■ Table Organization ■ Table Product ■ Table Quote ■ Table Service Request ■ Table Special Rate List ■ Table CIF ■ Table FleetManagement ■ Table Person 2 Use the Siebel Tools Import from Archive function to read this file and create the tables in the repository. The "merge" option should be used while importing this file. To create this table on the physical database ■ The tables have to be in the repository before creating this on the physical database. Use Siebel tools and query for the list of tables that were imported into the repository. Use the "Apply/DDL" button to apply the changes to the physical database, and provide the correct database user (table owner name, password, and ODBC data source). The ACR463_EIMTables.sif file has all the changes for the following: Changes to existing tables: ■ EIM_ASSET ■ EIM_ASSET1 ■ EIM_ALERT_CUT ■ EIM_INVOICE ■ EIM_ORDER ■ EIM_ORDER1 ■ EIM_ORDER_ITEM1 ■ EIM_PROD_INT1 ■ EIM_QUOTE ■ EIM_QUOTE_IT1
  • 189. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 189 To import the ACR463_EIMTables.sif file into the repository 1 Lock the following projects before import: ■ EIM Asset ■ EIM Common SIA ■ EIM Invoice ■ EIM Order ■ EIM Product ■ EIM Quote ■ EIM BulkRequest ■ EIM CIF ■ EIM FleetManagement ■ EIM Organization ■ EIM Person ■ EIM Service Request 2 Use the Siebel Tools Import from Archive function to read this file and create the tables in the repository. The "merge" option should be used while importing this file. Applying ACR 474 Schema Changes As part of the ACR474 release, schema changes have been done on the database. The REPPATCHAIA251ACR474DMGSchemaChangesACR474_Tables.sif has all the changes for the following: Changes to existing tables: ■ S_ASSET ■ S_CONTACT ■ S_CONTACT_BU ■ S_DOC_QUOTE ■ S_OPTY ■ S_OPTY_BU ■ S_ORDER ■ S_ORDER_ITEM ■ S_ORDER_ITEM_OM ■ S_ORDER_STOP ■ S_ORDPART_MVMT ■ S_ORG_BU
  • 190. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 190 ■ S_ORG_EXT ■ S_ORG_GROUP ■ S_PRI_LST ■ S_PRI_LST_ITEM ■ S_PROD_INT ■ S_PROD_INT_BU ■ S_QUOTE_ITEM ■ S_REVN ■ S_UCM_ADDR_PER ■ S_UCM_ASSET ■ S_UCM_CONTACT ■ S_UCM_ORGGRP ■ S_UCM_ORG_EXT ■ S_UCM_PRIVACY New Tables: ■ S_INTG_DEL_TXN ■ S_ORG_GRP_UCMX ■ S_PRD_USRDEFATR To import the ACR_474_Tables.sif file into the repository 1 Lock the following projects before import: ■ Table Asset ■ Table CIF ■ Table FieldService ■ Table FleetManagement ■ Table Forecast ■ Table Household ■ Table NetworkOrderManagement ■ Table OnPremise-OnDemand ■ Table Opty ■ Table Order ■ Table Organization ■ Table Person
  • 191. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 191 ■ Table PriceList ■ Table Product ■ Table Quote 2 Use the Siebel Tools Import from Archive function to read this file and create the tables in the repository. The "merge" option should be used while importing this file. To create this table on the physical database ■ The tables have to be in the repository before creating this on the physical database. Use Siebel tools and query for the list of tables that were imported into the repository. Use the "Apply/DDL" button to apply the changes to the physical database. Applying EIM Changes As part of the ACR474 release, EIM changes have been done on the database. The REPPATCHAIA251ACR474DMGSchemaChangesACR474_EIMTables.sif file contains all the changes for the following existing tables: ■ EIM_ACCOUNT ■ EIM_ACCOUNT1 ■ EIM_ASSET1 ■ EIM_CONTACT ■ EIM_CONTACT2 ■ EIM_GROUP ■ EIM_GROUP_DTL ■ EIM_OPTY ■ EIM_OPTY_DTL ■ EIM_ORDER1 ■ EIM_ORDER_FM ■ EIM_ORDER_ITEM ■ EIM_ORDER_ITEM1 ■ EIM_ORD_ITEM2 ■ EIM_ORG_BU ■ EIM_ORG_INT ■ EIM_PART_MVMT ■ EIM_PRI_LST ■ EIM_PROD_INT ■ EIM_PROD_INT1
  • 192. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 192 ■ EIM_PROD_INT_BU ■ EIM_QUOTE1 ■ EIM_QUOTE_IT2 ■ EIM_REVN ■ EIM_UCM_ADRPER ■ EIM_UCM_ASSET ■ EIM_UCM_CON ■ EIM_UCM_ORG ■ EIM_UCM_ORGGRP ■ EIM_UCM_PRIVCY To import the ACR_474_EIMTables.sif file into the repository 1 Lock the following projects before import: ■ EIM Asset ■ EIM CIF ■ EIM Common SIA ■ EIM FieldService ■ EIM FleetManagement ■ EIM Forecast ■ EIM Household ■ EIM Opty ■ EIM Order ■ EIM Organization ■ EIM Person ■ EIM PriceList ■ EIM Product ■ EIM Quote 2 Use Siebel Tools Import from Archive function to read this file and create the tables in the repository. The "merge" option should be used while importing this file. To create this table on the physical database The tables have to be in the repository before creating this on the physical database. Use Siebel tools and query for the list of tables that were imported into the repository. Use the "Apply/DDL" button to apply the changes to the physical database.
  • 193. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 193 Importing Seed Data for ACR 463 NOTE: As stated earlier, ACR 463 provided the AIA COM 2.4 release. 1 Create an ODBC entry for the database where you plan to import the seed data. a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC), navigate to the System DSN tab, and click Add. b Select the "Siebel Oracle90" driver (from Datadirect Technologies). c Enter a data source name (such as DevelopmentDB). d Enter the server name to connect to: ❏ For Oracle, enter the TNS service name that you created to connect Siebel Tools to the database. e Test your connection and click OK when tested successfully. 2 Navigate to the directory where you installed Siebel Tools and change the directory to REPPATCHAIA251ACR474SeedDataACR463_SEED. 3 Before executing the next step, make sure that the dataimp.exe file exists in the <Tools Install Directory>/bin directory. 4 Seed data import includes mono-language seed-data import and language seed-data import. Use Step a or Step b or both steps depending upon the language that you are installing. a Use the following command to import mono-language seed data: <ToolsInstall Directory>bindataimp /u sadmin /p sadmin /f <ToolsInstallDirectory>REPPATCHAIA251ACR474SeedDataACR463_SEEDSeed_aiacom 24.dat /l <ToolsInstallDirectory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q -1 /w n /e y /t n /x R /n 100 /h log Review the log filein <Tools Install Directory>tempdataimp_seed.log file to make sure that the import completed successfully. b Use the following command to import the language seed data: <Tools Install Directory>bindataimp /u sadmin /p sadmin /f <ToolsInstallDirectory>REPPATCHAIA251ACR474SeedDataACR463_SEEDseed_locale_ <language>.dat /l <ToolsInstallDirectory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q -1 /w n /e y /t n /x R /n 100 /h log <Tools Install Directory> - Replace with your Siebel Tools install directory. <ODBC Source Name> - Replace with the ODBC name created in Step 1. c Review the log filein <Tools Install Directory>tempdataimp_seed.log file to make sure that the import completed successfully. Importing Seed Data for ACR 474 1 Create an ODBC entry for the database where you plan to import the seed data. a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC) > System DSN tab, and click Add.
  • 194. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 194 b Select the Siebel Oracle90 driver (from Datadirect Technologies). c Enter a data source name (such as DevelopmentDB). d Enter the server name to connect to: e For Oracle, enter the TNS service name that you created to connect Siebel Tools to the database. f Test your connection and click OK when tested successfully 2 Navigate to the directory where you installed Siebel Tools and change the directory to REPPATCHACR474. 3 Before executing the next step, make sure that the dataimp.exe file exists in the <Tools Install Directory>/bin directory. 4 Run the following command: <Tools Install Directory>bindataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>REPATCHAIA251ACR474_SEEDACR474_8113FP_Seed.dat /l <Tools Install Directory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools Install Directory>>REPATCHAIA251ACR474_SEED<Database Platform> ACR474_8113FP_Seed.inp /q -1 /w y /e n /t n /x R /n 100 /h log <Tools Install Directory> - Replace with your Siebel Tools install directory <ODBC Source Name> - Replace with the ODBC name created in Step 1 <Database Platform> - Replace with the database platform (ORACLE, DB2UDB or MSSQL) 5 Review the <Tools Install Directory>tempdataimp_seed.log file to make sure that the import completed successfully. Depending upon the language that you are installing, complete either Step 6or Step 7. 6 For ENU (English Language) customers: a Run the following command after importing the ACR474_Seed.dat file. <Tools Install Directory>bindataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>REPATCHAIA251ACR474_SEEDACR474_8113FP_Seed_Locale_ENU.dat /l <Tools Install Directory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools Install Directory>REPATCHAIA251ACR474_SEED <Database Platform>ACR474_8113FP_Seed_Locale_ENU.inp /q -1 /w y /e n /t n /x R /n 100 /h log <Tools Install Directory> - Replace with your Siebel Tools install directory <ODBC Source Name> - Replace with the ODBC name created in Step 1 <Database Platform> - Replace with your database platform (ORACLE, DB2UDB or MSSQL) b Review the <Tools Install Directory>tempdataimp_seed.log file to make sure that the import completed successfully. 7 For customers using languages other than ENU:
  • 195. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 195 a Run the following commands after importing the ACR474_Seed.dat file for importing the locale specific seed_locale_XXX.dat, where XXX is the language code. <Tools Install Directory>bindataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>REPATCHAIA251ACR474_SEEDseed_locale_XXX.dat /l <Tools Install Directory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q -1 /w n /e y /t n /x R /n 100 /h log <Tools Install Directory> - Replace with your Siebel Tools install directory <ODBC Source Name> - Replace with the ODBC name created in Step 1 b Review the <Tools Install Directory>tempdataimp_seed.log file to make sure that the import completed successfully. c Run the following commands after importing seed_locale_XXX.dat file for importing the locale specific AIA251_seed_locale_XXX.dat, where XXX is the language code. <Tools Install Directory>bindataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>REPATCHAIA251ACR474_SEEDAIA251_seed_locale_XXX.dat /l <Tools Install Directory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /q -1 /w n /e y /t n /x R /n 100 /h log <Tools Install Directory> - Replace with your Siebel Tools install directory <ODBC Source Name> - Replace with the ODBC name created in Step 1 d Review the <Tools Install Directory>tempdataimp_seed.log file to make sure that the import completed successfully. Updating ACR 474 EIM Files As part of the ACR474 release, the EIM files - eim45.sql and eim_export_lookup_bu_name.sql have been changed. The REPPATCHAIA251ACR474EIMeim45.sql and REPPATCHAIA251fACR474EIMeim_export_lookup_bu_name.sql have all the changes required. You must merge these files with the existing files in the Siebel Server directory: eim45.sql: <Installation Location>SERVERsiebsrvrSQLTEMPL eim_export_lookup_bu_name.sql : <Installation Location>SERVERsiebsrvrADMIN
  • 196. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 196 Siebel Tools Changes for ACR 474 1 Open tools.cfg from <Tools Install Directory>BinEnu and verify the [Siebel] section. Make sure that the SymStrPrefix entry has been set to SBL_. [Siebel] …….. SymStrPrefix parameter needs to be X_ for Siebel customers. SymStrPrefix = SBL_ …….. NOTE: After changing the tools.cfg file, make sure to log out of Siebel Tools and log in again to apply the changes. 2 In Siebel Tools, lock all of the following projects: ■ ABO Bulk Request ■ ATP ■ Account ■ Account (SSE) ■ Assignment (SSE) ■ Asset Management ■ Bitmap ■ Cfg RTC ■ CMU Billing BC ■ CMU Billing Product ■ CMU Billing UI ■ CMU Billing Integration ■ COM Workflows ■ CUT Admin - External Data ■ CUT Billing ■ CUT Credit Alert ■ CUT Profile ■ CUT Newtable ■ CUT Siebel Communications ■ CUT Trouble Ticket ■ Contact ■ Contact (SSE)
  • 197. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 197 ■ Comm Manager ■ Communication ■ Division ■ Dock ■ Dock KDI ■ Docklog ■ Dockses ■ Eligibility Compatibility ■ EIM Asset ■ EIM CIF ■ EIM Household ■ EIM Organization ■ EIM Person ■ EIM Common SIA ■ EIM Invoice ■ EIM Order ■ EIM Product ■ EIM Quote ■ EIM BulkRequest ■ EIM Organization ■ EIM Service Request ■ Employee ■ FS Agreement ■ Fleet Management ■ ISS Authoring Admin ■ ISS Class Admin ■ ISS Context ■ ISS Order Management ■ ISS Product Admin ■ ISS Promotion Admin ■ ISS Promotion Integration ■ ISS Promotion Workflow ■ ISS VOD Import Export
  • 198. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 198 ■ ISS VOD Loader ■ LS DB Action ■ MACD Performance ■ Order Entry ■ Opportunity Management ■ Oppty ■ Oppty (SSE) ■ PMP ■ Prepaid Service 8.1 ■ Price List ■ Product ■ Product (SSE) ■ Product Integration ■ Product Selection UI ■ Quote (UI) ■ Quote ■ Row Set Transformation Toolkit ■ SIS OM Base Architecture ■ Service ■ Siebel Sales Enterprise ■ Siebel High Tech ■ Siebel Universal Agent ■ Srvagree ■ Srvagree (SSV) ■ Symbolic Strings ■ Template (Order) ■ Table Asset ■ Table BulkRequest ■ Table Invoice ■ Table Order ■ Table Organization ■ Table Product ■ Table Promotions
  • 199. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 199 ■ Table Quote ■ Table Service Request ■ Table Special Rate List ■ Table CIF ■ Table Person ■ Table FleetManagement ■ Table FieldService ■ Table Forecast ■ Table Household ■ Table NetworkOrderManagement ■ Table Opty ■ Table PriceList ■ Table OnPremise-OnDemand ■ UCM Privacy Management ■ UMSUI ■ VEAI CUT Billing Integration ■ VERT CUT Address ■ VERT CUT Common ■ VERT CUT Screens ■ VORD Network Order Entry ■ Web Channel Order Management ■ Web Service Integration ■ Workflow Policy ■ eService Billing ■ eAuto Product NOTE: If you have implemented ACR 471, you must merge repository and workflow changes to make sure that ACR 471 and ACR 474 are compatible: ■ Business Service - ISS Promotion Management Service.sif ■ Workflow - ISS Promotion Upgrade Process.xml 3 Import the rest of the SIF files from the SIFFiles folder into Siebel Tools: a Place the BatchImportAcr474.bat file in <Tools Install Directory>/bin, edit the file to replace “REPPATCHACR474” with “REPPATCHAIA251ACR474,” save the file, and then execute it. For further information on batch import, see the topic, “Importing Objects from an Archive File Using the Command-Line Interface” in Using Siebel Tools on the Siebel Bookshelf library.
  • 200. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 200 b Check the logs in <Tools Install Directory>/importLogsAcr474 directory. c If you have not locked the required projects, you might receive a warning error message. Create the projects and lock them the projects are not available by default. d The Fleet Management and Table OnPremise-OnDemand projects are not available by default. You must create them before you execute the BatchImportAcr474.bat file. NOTE: The following steps apply only to customers who are installing languages other than ENU. 4 (Optional) If you are installing languages other than ENU: a Navigate to Select > Tools > Utilities > Locale Management to import LMU files for the specific language from the LMU folder into Siebel Tools. b Select Source Language = English American c Target Language = <Specific Language> d Click the Import tab and then Browse to locate the LMU file you want to import and click Import. 5 Stop Siebel Server, if it is running. 6 Within Siebel Tools, navigate to Menu > View > Options > Scripting tab, and specify the following path for the Browser script compilation folder. <Server IP address><SWE server Installed Location>eappwebPUBLICenu 7 Compile all of the projects using the Compile Projects > All Locked Projects option and save the SRF file to the <Siebel Server Install folder>objectsENUsiebel_sia.srf folder on the installed Siebel server. 8 Copy the Web Template file CZConfigurator.swt and CZView.swt from the WebTemplate folder into Siebel Server <Siebel Server Install folder >WEBTEMPL. 9 Copy the CZReturn.html file from the HTML folder into the SWE Server <SWE Server Install folder >eappwebPUBLICenu. 10 From the EIM folder, copy the files with extension "ifb" in Siebel Server <Siebel Server Install folder >ADMIN. 11 Start the Siebel Server. 12 Import the workflows listed in the following table into the Siebel application. NOTE: All of the existing workflows should be imported. In other words, the modified workflows should be imported into the corresponding projects. Note the following dependencies before you begin importing the files: ■ Import the "SWIOrderUpsert_O2C" workflow first and then import the "SWIOrderUpsert" workflow. ■ Import the "SWISendOrder" workflow first and then import the "Submit Order ASI" workflow. ■ Import the "SWISendQuote" workflow first and then import the "Submit Quote ASI" workflow. ■ Import the "Oracle Configurator Load" workflow first and then import the "SWI Configurator Load" workflow.
  • 201. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 201 ■ Import the "SWIOrderUpsertSubProcess" workflow first and then import "SWIOrderUpsert" workflow
  • 202. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 202 ■ Import the "SWISetTBOEndDate" workflow first and then import the "Dynamic Pricing Procedure" workflow. Workflow Name Project *SIS OM Disconnect Asset Sub-process SIS OM Base Architecture *SIS OM Move Process SIS OM Base Architecture ABO Bulk Request -Validate Process ABO Bulk Request ABO Bulk Request - Clear Exception Process Workflow ABO Bulk Request ABO Bulk Request - Parallel Sub Process Workflow ABO Bulk Request ABO Bulk Request - Prepare Action Set Sub-Process Workflow ABO Bulk Request ABO Bulk Request - Submit Process Workflow ABO Bulk Request ABO Bulk Request Add Item Customize Process ABO Bulk Request Account - New Order COM Workflows Basic Pricing Procedure Cfg RTC CMU Credit Alert Status Sync Web Service Integration CMU SIA Submit Adjustment Request to External CMU Billing Integration CMUBalanceDetailsEventAdjustmentWF CMU Billing Integration CMUEventDetailsAdjustmentWF CMU Billing Integration CMUInvoiceAdjustmentWF CMU Billing Integration CMUItemChargeAdjustmentWF CMU Billing Integration CMUUnbilledEventAdjustmentWF Web Service Integration CMUUnbilledNonCurrencyEventAdjustmentWF Web Service Integration CZ PSP Interface Web Service Integration CZ Return Web Service Integration Dynamic Pricing Procedure Row Set Transformation Toolkit ISS Promotion Disconnect Process ISS Promotion Workflow ISS Promotion Upgrade Process ISS Promotion Workflow Oracle Configurator Load Web Service Integration Oracle Verify Complex Product All (Order) Web Service Integration Oracle Verify Complex Product All (Quote) Web Service Integration Pricing Procedure - Calculate Net Price Row Set Transformation Toolkit SIA External Integration Process Prepaid Service 8.1 SIS OM Add Service Charge Order Sub-Process SIS OM Base Architecture SIS OM Add Service Charge Quote Sub-Process SIS OM Base Architecture
  • 203. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 203 SIS OM Add Service Charge Sub-Process SIS OM Base Architecture SIS OM Disconnect Products & Services Process SIS OM Base Architecture SIS OM Edit Complex Asset Workflow SIS OM Base Architecture SIS OM Edit Delta Quote Line Item SIS OM Base Architecture SIS OM Edit Service Order Line Item SIS OM Base Architecture SIS OM Modify Products & Services Process SIS OM Base Architecture SIS OM Order Line Item Update Main SIS OM Base Architecture SIS OM Submit Order Process SIS OM Base Architecture SIS OM Suspend / Resume Asset Sub-Process SIS OM Base Architecture SIS OM Suspend / Resume Products & Services Process SIS OM Base Architecture SISOMBillingSubmitOrderWebService CMU Billing Integration Submit Order ASI COM Workflows Submit Quote ASI COM Workflows SWI Account Update Workflow Web Service Integration SWI Address Update Workflow Web Service Integration SWI Asset Status Update CMU Billing Integration SWI Billing Profile Update Workflow Web Service Integration SWI Cancel Sales Order Line Item Web Service Integration SWI Cancel Sales Order_O2C Web Service Integration SWI Configurator Load Web Service Integration SWI Contact Update Workflow Web Service Integration SWI External Account Integration Process Web Service Integration SWI External Account Request Sync Process Web Service Integration SWI External Contact Integration Process Web Service Integration SWI External Contact Req Integration Process Web Service Integration SWI External Contact Request Sync Process Web Service Integration SWI External Customer Req Integration Process Web Service Integration SWI External Product Sync Workflow Web Service Integration SWI Initial Load Non CP Order Release Web Service Integration SWI Parent Order Web Service Integration SWI Special Rating - Synchronize Process Web Service Integration SWI TSQ Order Web Service Integration Workflow Name Project
  • 204. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 204 NOTE: The asterisks denote workflows that were not modified for ACR 474. a Select Workflow Process in Siebel Tools Object Explorer. b Right-click on the right side pane called Workflow Processes and import the .xml file into Siebel Tools from the Workflows folder. Refer to the list of workflows in the table above to know which project these workflows need to be imported into. NOTE: The following step is required if you have installed AIA 2.5 IPS 1 or higher. 13 Revise the following workflows, change the Process Property ‘UTCCanonical’ default value from ‘N’ to ‘Y’. Publish, and then activate. ■ CMU Credit Alert Status Sync ■ CMU SIA Submit Adjustment Request to External ■ SISOMBillingSubmitOrderWebService ■ SWI Account Update Workflow ■ SWI Billing Profile Update Workflow SWIAdjustmentStatusUpdate Web Service Integration SWICancel Sales Order Web Service Integration SWICopyOrder Web Service Integration SWIOrderUpsert Web Service Integration SWIOrderUpsert_O2C Web Service Integration SWIOrderUpsertSubProcess Web Service Integration SWIQuoteUpsert Web Service Integration SWIReviseOrderValidation Web Service Integration SWISendATPCheck Web Service Integration SWISendATPCheckLine Web Service Integration SWISendCalculateShippingCharge Web Service Integration SWISendCreditCheck Web Service Integration SWISendOrder Web Service Integration SWISendPaymentAuthorization Web Service Integration SWISendQuote Web Service Integration SWISetTBOEndDate CMU Billing Integration SWIValidateDependentOrders Web Service Integration Verify Header (Order) COM Workflows Verify Item (Order) COM Workflows Workflow Name Project
  • 205. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 205 ■ SWI Contact Update Workflow ■ SWI Address Update Workflow ■ SWI Cancel Sales Order_O2C ■ SWI External Account Request Sync Process ■ SWI External Contact Request Sync Process ■ SWI Special Rating - Synchronize Process ■ SWIAdjustmentStatusUpdate ■ SWIOrderUpsert ■ SWIOrderUpsert_O2C ■ SWIOrderUpsertSubProcess ■ SWIQuoteUpsert ■ SWISendATPCheck ■ SWISendATPCheckLine ■ SWISendCalculateShippingCharge ■ SWISendCreditCheck ■ SWISendOrder ■ SWISendPaymentAuthorization ■ SWISendQuote Check the status of theWorkflow process. If it is In-Progress, then make it complete by deploying the Workflow process. For Siebel applications version 8.0 and above, the button to mark the workflow status complete is Publish/Activate. To view this button, navigate to View menu > Tool Bar > WF/Task Editor. NOTE: If any of the workflows fail to import, manually activate them within the application. a Repeat Step b and Step c of “Siebel Tools Changes for ACR 474” on page 196 for of all the workflows in the folder. b Log in to the Siebel application as an administrator. c Navigate to the Site Map, and click Administration - Business Process. d Navigate to Workflow Deployment > Repository Workflow Process. e Query for the workflow processes and activate them. NOTE: It is recommended that you reload the runtime events after activating the workflows. f Navigate to Administration - Runtime Events > Events screen, select all records and then select Reload Runtime Events from the drop-down menu.
  • 206. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 206 14 Import the rest of the SIF files from the SIFFiles folder AIA251ACR474_Workaround into Siebel Tools using the Import from Archive function. If you have not locked the required projects, you may receive a warning error message. Make sure to choose the Merge Option in Siebel Tools Import Wizard. 15 Import the following SIF files: ■ .AIA251ACR474_WorkaroundAppletOrder Entry - Line Item List Applet (Sales).sif ■ .AIA251ACR474_WorkaroundBitmap CategoryOrder Status.sif ■ .AIA251ACR474_WorkaroundBusiness ComponentOrder Entry - Line Items.sif ■ .AIA251ACR474_WorkaroundBusiness ServiceSIS OM PMT Service.sif ■ .AIA251ACR474_WorkaroundIcon MapGraphical indicator - Order Status.sif ■ .AIA251ACR474_WorkaroundIntegration ObjectISS Order.sif 16 Compile all of the objects listed above using the Compile Selected Object option and save the SRF file to the <Siebel Server Install folder>objectsENUsiebel_sia.srf folder on the installed Siebel server. 17 Import and activate the workflows listed in the following table from AIA251ACR474_WorkaroundWFs into Siebel Tools: a Within Siebel Tools > Object Explorer, select Workflow Process. b Right-click on the right side pane ‘Workflow Processes’ and import the .xml file into Siebel Tools from the WFs folder. Refer to the list of workflows in the preceding table to know which project these workflows need to be imported into. c Activate the workflows by clicking on “Deploy+ Activate” button to activate the workflows. d Repeat Step b and Step c for of all the workflows in the folder. 18 Import the rest of the SIF files from the SIFFiles folder AIA2518113_Addendum into Siebel Tools using the Siebel Tools > Import from Archive function. If you have not locked the required projects, you may receive a warning error message. Make sure to choose Merge Option in Siebel Tools Import Wizard. Import the following SIF files: ■ . AIA2518113_AddendumBusiness ComponentSWI Internal Product VOD.sif ■ .AIA2518113_AddendumBusiness ComponentSWI Match Account VBC.sif ■ . AIA2518113_AddendumBusiness ComponentSWI Match Contact VBC.sif Process Name New/ Modified Project Pricing Procedure - Calculate Net Price Toolkit Modified Row Set Transformation SIS OM Edit Service Order Line Item Modified SIS OM Base Architecture
  • 207. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 207 ■ . AIA2518113_AddendumBusiness ComponentUMF Passive Message Virtual BusComp.sif ■ .AIA2518113_AddendumBusiness Service MatchAccountSiebelReqABCSImplService.sif ■ .AIA2518113_AddendumBusiness Service MatchContactSiebelReqABCSImplService.sif ■ .AIA2518113_AddendumDMGSchemaChangesS_PRO_CFG_ITEM.sif ■ .AIA2518113_AddendumIntegration ObjectSWIOrderIO.sif 19 Compile all of the preceding objects using the Compile Selected Object option and save the SRF file to the <Siebel Server Install folder>objectsENUsiebel_sia.srf folder on the installed Siebel server. 20 If the Table Promotions project is not already locked, lock it. 21 Within Siebel Tools, query for the S_PRO_CFG_ITEM table. 22 Click the Apply/DDL button to apply the changes to the physical database. 23 Import the workflows listed in the following table into Siebel Tools and then activate the workflows. a Within Siebel Tools > Object Explorer, select Workflow Process. b Right-click on the right-side pane called Workflow Processes and import the .xml file into Siebel Tools from the Workflows folder. Refer to the list of workflows in the preceding table to know which project these workflows need to be imported into. c Click the Deploy+ Activate button to activate the workflows. d Repeat Step b and Step c for of all the workflows in the folder. Applying Incremental Fixes for AIA 11.1 1 Unzip the AIA11.1.zip file to create the following directory structure: <Tools Install Directory>REPPATCHAIA11.1 The AIA11.1 folder will contain the following subfolders: ■ DMGSchemaChanges ■ SIFFiles ■ WFs ■ Xml Process Name New/Modified Project SWI External Account Integration Process Modified Web Service Integration SWI External Contact Integration Process Modified Web Service Integration SWI External Contact Req Integration Process Modified Web Service Integration SWI External Customer Req Integration Process Modified Web Service Integration
  • 208. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 208 2 Import the SIF files fromDMGSchemaChanges using the Merge option within Siebel Tools Import Wizard. 3 Within Siebel Tools, query for the tables S_INVC_ADJ_ITEM or S_INVOICE_ADJ tables, and click Apply/DLL to apply the changes to the physical database. 4 Import the SIF files from SIFFiles using the Merge option in Siebel Tools Import Wizard. 5 Compile all of the preceding objects using the Compile Selected Object option and save the SRF file to the <Siebel Server Install folder>objectsENUsiebel_sia.srf folder on the installed Siebel server. 6 Import the workflows listed in the following table into Siebel Tools and then activate them: 7 Within Siebel Tools > Object Explorer, select Workflow Process. 8 Right-click on the right-side pane (Workflow Processes) and import the .xml file into Siebel Tools from the Workflows folder. NOTE: Refer to the listof workflows in the preceding table to know which project these workflows need to be imported into. 9 Click Deploy+ Activate button to activate the workflows. 10 Repeat Step 8 and Step 9 for of all the workflows in the folder. 11 Launch the Siebel communications application, and navigate to Site Map > Administration- Integration > Data Map Editor. Process Name New/Modified Project ABO Bulk Request - Prepare Action Set Sub-Process Workflow Modified ABO Bulk Request ABO Bulk Request - Submit Process Workflow Modified ABO Bulk Request CMUBalanceDetailsEventAdjust mentWF Modified CMU Billing Integration CMUInvoiceAdjustmentWF Modified CMU Billing Integration CMUItemChargeAdjustmentWF Modified CMU Billing Integration SIS OM Apply Completed Service Order Line Item to Service Profile Modified SIS OM Base Architecture SISOMBillingSubmitOrderWeb Service Modified CMU Billing Integration SWI Configurator Load Modified Web Service Integration SWICancel Sales Order Modified Web Service Integration SWIOrderUpsert Modified Web Service Integration
  • 209. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 209 12 Import the "SWI_Asset_Integration.XML" file from <Tools folder>REPPATCHAIA11.1Xml. 13 In the Integration Object Map applet, query for SWI Asset Integration. 14 In the Integration Component Map applet, query for Line_Item_to_Line_Item. 15 In the Integration Field Map applet, click New and add a new record with the following values: 16 Query for the Status field and change the source expression as follows: 17 Modify the run time events for promotions: a Navigate to the Administration - Runtime Events screen. b Click the Action Sets view. Three applets appear. c In the first applet, Action Sets, search for the 'Cache Refresh BC - ISS Promotion Pricing Components List Applet' Action Set. d For this Action Set, in the bottom form applet, there is a control with the 'Business Service Context' label. For this control,the previous value was only "ISS Promotion Pricing Components", "ISS Promotion Pricing Rules Summary". Another newentry was added to this and now the value for this control is "ISS Promotion Pricing Components", "ISS Promotion Pricing Rules Summary", "Promotion Config Item". Note that there should be a space after the comma. [This step needs to be performed only if it is required.] 18 Release the variable maps: a Navigate to Site Map > Admin - Order Management > Variable Maps, and query for the following: ❏ Default Pricing Variable Map - Row Set - Basic ❏ Default Pricing Variable Map - Row Set ❏ Default Pricing Eligibility Variable Map - Row Set b Release a new version of each of the above objects and then bounce the server. 19 Release the signal: Source Expression Target Field Name insert operation Source Expression Target Field Name IIF([Status] IS NULL, LookupValue ("IMPL_PHASE", "Active"),[Status]) Status
  • 210. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 210 a Navigate to Site Map > Admin - Order Management > Signal and query for the ReviseCopyOrder signal. b Release a new version of the above object and then bounce the server. 20 Enable component groups for order creation: NOTE: Bounce the server after enabling the compgrp and synchronizing it. a Navigate to Administration - Server Configuration > Enterprises> Component Groups and query for each of the following Component Groups and, if Enable State = Disabled, click <Enable>: ❏ Siebel CME [Alias- Communications] ❏ Siebel ISS [Alias- ISS] ❏ Workflow Management [Alias- Workflow] ❏ HTIM ❏ EAI *Note through Srvrmgr Command Prompt - Enable compgrp <Alias> b After enabling the necessary components, navigate to Administration - Server Configuration > Enterprises > Synchronize. Select all the records and then click Synchronize. 21 Activate workflows. a Navigate to Site Map > Administration Business Process > Workflow Deployment > Active Workflow Processes and in the second applet, complete one of the following tasks: ❏ Query for SIS*,Pri*,PSP*,ISS*,Elig*,eSales*. ❏ Query for the following groups: Eligibility & Comp, Asset Based Ordering, Pricer, eSales, Product Promotions, Configurator, C/OM UI processes, CUT eSales (only for SIA, not for SEA), and Product Recommendation, and delete the groups manually after deactivating the processes. To deactivate these groups, select them all and then select Deactivate Process. You can check the Deployment Status as Inactive. b Delete all the records. c In the first applet, complete one of the following tasks: ❏ Query for SIS*,Pri*,PSP*,ISS*,Elig*,eSales*. ❏ Query for the following groups: Eligibility & Comp, Asset Based Ordering, Pricer, eSales, Product Promotions, Configurator, C/OM UI Processes, CUT eSales (only for SIA, not for SEA), and Product Recommendations, and then activate all the workflows. 22 Restart the Siebel Server. 23 Launch the Siebel Communications application. 24 Complete the following steps for defining the end point URL for ABS (Outbound Webservices) a Log into the Siebel application as an administrator and navigate to the Site Map. b Select Administration - Web Service > Outbound Web Services. c Query for "*JMS* OR *ABCS* OR *ESB* OR *ConfiguratorUserLangSiebelAdapter* OR SyncCustomerSiebelEventAggregator" on the Name field of the Web Services applet.
  • 211. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 211 ❏ AdjustmentSiebelCommsReqABCS ❏ CalculateShippingChargeSalesOrderSiebelReqABCSImpl ❏ CheckATPSalesOrderSiebelReqABCSImpl ❏ ConfiguratorUserLangSiebelAdapter ❏ CreditCheckSalesOrderSiebelReqABCSImpl ❏ ESB_AccountBalanceSiebelCommsReqABCS_Service ❏ ESB_ConfiguratorCopyConfigEbizAdapter_Service ❏ ESB_InvoiceSiebelCommsReqABCS_Service ❏ ESB_UnbilledUsageSiebelCommsReqABCS_Service ❏ FetchAccountSiebelReqABCSImpl ❏ FetchContactSiebelReqABCSImpl ❏ MatchAccountSiebelReqABCSImpl ❏ MatchContactSiebelReqABCSImpl ❏ PaymentAuthorizationSalesOrderSiebelReqABCSImpl ❏ PaymentSiebelCommsReqABCS ❏ ProcessSalesOrderSiebelCommsJMSProducer ❏ RequestProductStructureSiebelJMSProducer ❏ SyncCustomerSiebelEventAggregator ❏ SyncInstalledProductListSiebelCommsReqABCSImpl ❏ UpdateCreditAlertSiebelCommsReqABCSImpl d Change the Address field for each outbound Web service to point to http:// <HostName>:<PortNumber> (such as http://ap6039fems.us.oracle.com:7797). e For Inbound Web Services, navigate to Administration - Web Services > Inbound Web Services, and make sure thatthe corresponding Web Services are active. If they are not, changethe status from "Inactive" to "Active" and click the Clear Cache button. NOTE: Query for these inbound web services --- * ISS *; * Update Order *; * SWI Update *, SWI*.
  • 212. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 212 Setting Up and Configuring Workflow Policies In order to enable the workflow policies, the following components should be configured and running on Siebel Server (in addition to the Application Object Manager component). NOTE: Enabling the EAI and Workflow Component Groups in the Siebel Server will start all the required components stated above for transaction logging. To set the Workflow Management component group ■ Check that the Workflow Management component group is enabled with its components by navigating to Administration > Server Management > Components, and then querying for Workflow*. To generate trigger with parameter Remove = TRUE 1 Navigate to Administration -> Server management -> Jobs) to generate trigger. 2 Create a Job for Component Generate Triggers by clicking New and typing Generate Triggers under Component/Job. 3 Define the Job Parameters with the following values: ■ EXEC = TRUE ■ Privileged User = <Table Owner> ■ Privileged User Password = <Table Owner> ■ Remove = TRUE ■ Trigger File Name: trigger.sql 4 Start the job. NOTE: If the job parameters do not appear when you query for them, then search for them in the Advanced or Hidden section. Configuring Workflow Monitor Agent 1 Navigate to Administration - Server Configuration > Enterprises > Component Definitions, and query for WorkFlow*. Component Name Component Alias Component Group Enterprise Integration Mgr EIM EAI EAI Object Manager (ENU) EAIObjMgr_enu EAI Workflow Process Manager WfProcMgr Workflow Workflow Process Batch Manager WfProcBatchMgr Workflow Workflow Monitor Agent WorkMon Workflow Generate Triggers GenTrig Workflow
  • 213. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 213 2 Make a copy of the Workflow Monitor Agent in Administration - Server Configuration -> Component Definition and change the name to "Workflow Monitor Agent SWI". 3 Change the Alias name to 'WorkMonSWI'. 4 Change the Group Name to "SWI Customer Update Policy Grp" in the component Parameter applet (down). (Under Component Parameters query for "Group Name" and type the SWI Customer Update Policy Grp under Value). 5 Change the Action Interval to a value 5. 6 Change the Sleep Time to a value 15. 7 Change the Default Task to 1. 8 Change the status of the new component to "Active" by clicking Activate. 9 Synchronize the components. Configuring Default Task for Workflow Monitor Agent The Show Advanced Objects Server Manager parameter controls the display of all the objects that are marked for the advanced user. Workflow Monitor Agent has a parameter called 'Default Tasks' that is hidden and should only be displayed or available to advanced users. Use the following procedure to reveal the hidden Default Tasks parameter, complete the following steps. To reveal the hidden Default Tasks parameter 1 Navigate to Administration - Server Configuration > Servers. 2 In the top Siebel Servers applet, select the server on which you want to modify the parameter, and under the Component subtab, query for the Server Manager component. 3 Under the Parameters subtab, query for Show Advanced Objects. 4 Change the value to 'True'. NOTE: You must log out fromyour current user session and log back into the application in order for the parameter to take effect. 5 Change the Default Task parameter to 1. Starting the Tasks for Workflow Monitor Agent for Customer Synchronization This section describes the steps to start tasks for the component that is online/enabled. 1 Navigate to Administration - Server Management and select Tasks. 2 Query for the Task "WorkMonSWI" and Start Task. Alternatively, use Server Manager to start task.
  • 214. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 214 3 Start srvrmgr. srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u <userid> /p <password> 4 Start task for component WorkMonSWI. To restart the server 1 Stop the Siebel Server. 2 Rename the existing diccache.dat file in the path <Installed Directory> sessiebsrvrbin. 3 Restart the Siebel Server. Generating the Trigger Make sure that the User SADMIN has the necessary privileges for generating triggers before running this procedure. To generate the trigger 1 Navigate to Administration > Server management > Jobs. 2 Create a job for the "Generate Triggers" component by clicking New and typing "Generate Triggers" under Component/Job. 3 Define the Job Parameters with the following values: ■ EXEC = TRUE ■ Privileged User = <Table Owner> ■ Privileged User Password = <Table Owner> ■ Trigger File Name: trigger.sql 4 Start the job. NOTE: If the job parameters information does not appear when you query for it, then search for it in Advanced or Hidden section. 5 After about five minutes, check for log details for the task for the new workflow monitor component "Workflow Monitor Agent SWI" by navigating to Administration > Server Management > Tasks. 6 If errors occur, check whether all configurations have been done properly and then repeat “To restart the server” on page 214 and “To generate the trigger” on page 214. Enabling Required System Preferences Use the following procedure to enable required system preferences.
  • 215. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 215 To enable required system preferences 1 Navigate to Administration - Application > System Preferences in the application, query for the following list of PIPs, and set the value to TRUE: ■ Enable AIA Comms ■ Enable AIA MDM ■ Enable AIA OrderToCash ■ Enable AIA Testing CAUTION: Set the system preference to TRUE only for the required PIPs. The AIA Comms PIP and the AIA OrderToCash PIP cannot coexist. 2 Query for 'Validate Due Date' in the 'System Preference Name' field and set the 'System Preference Value' to 2. If querying for this preference does not yield any results, create this value. 3 Query for 'Cancel Error Mode' in the 'System Preference Name' field and set the 'System Preference Value' to 3 (the default value). 4 Update the AIA Version system preference according to the AIA version that you are using. The following versions are available: ■ 2.0.1 ■ 2.4 ■ 2.5 ■ 2.5.1 NOTE: If you select any values other than the ones listed above, the application may not function as expected. Also, you must select 2.5.1 for 11g. 5 Restart the Siebel Server. Setting Up the Integration User This section describes the integration user setup process. We have introduced a new flag to identify an integration user (needed while integration testing). This user credential needs to be configured (at AIA side) for the Siebel Inbound Web services call from AIA side to avoid the boomerang effect. The following procedures describe the process of setting up the integration user: Steps Expected Result Login as SADMIN Navigate to Administration-User ' Employee view The list applet should contain the integration user flag Configure a new integration user by setting the integration user flag to Y for a specific user.
  • 216. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 216 Setting Order Priority for AQ Use the following procedure to set order priority for AQ. 1 Navigate to the Administration - Data > List Of Values view. 2 Query for Type equals SWI_ORDER_JMS_PRIO_MAPPING. 3 Change the values in the Language-Independent Code column to define the new mapping asper following table: 4 Click Clear Cache to clear the cache. Advanced Queue Configuration NOTE: Advanced queue configuration is only required for the 10g client. 1 Extract oc4j-extended.zip from http://download.oracle.com/otn/java/oc4j/101330/ oc4j_extended_101330.zip to a folder in a machine where the Siebel server is installed, such as D:JMS folder. 2 Copy Siebel.jar and SiebelJI_enu to D:JMS folder, these jar files can be found in <Siebel Server installation directory>classes folder 3 Copy jndi.jar file from FMW to D:JMSj2eehomelib folder. 4 Copy "com/evermind/util/JCAProperties.class" from the oc4j-internal.jar file to the D:JMS folder. 5 Create a file with name ‘jndi.properties’ with following details in the path D:JMS: java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory java.naming.provider.url=opmn:ormi://<IP Address of the FMW server>:<OPMN Port No>:oc4j_soa java.naming.security.principal=anonymous For example: java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory java.naming.provider.url=opmn:ormi:// 152.68.240.154:6009:oc4j_soa java.naming.security.principal=anonymous Make sure that there are no extra spaces in the jndi.properties file. 6 Create a Named Subsystem in the Siebel application through the server management. Display Value Language-Independent Code Low 6 Medium 4 High 2 Urgent 0
  • 217. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 217 a Connect to the server manager from the command prompt from the bin directory of the Siebel installed folder with the following command. Srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u <userid> /p <password> Example: srvrmgr /g sdc78198svqe:4330 /e siebel /s sdc78198svqe /u sadmin /p sadmin b Run the following command to create the named subsystem and add the jar file into the class path. Create named subsystem JAVA for subsystem JVMSubSys with DLL=C:SunSDKjdkjrebinserverjvm.dll, CLASSPATH = D:JMS;D:JMSSiebel.jar;D:JMSrdbmsjlibaqapi.jar;D:JMSjdbclibocrs12.jar;D:JMS jdbclibojdbc14dms.jar;D:JMSjdbcliborai18n.jar;D:JMSSiebelJI_enu.jar;D:JMSj2ee homelibadminclient.jar;D:JMSj2eehomelibjndi.jar;D:JMSj2eehomelibjta.jar;D:J MSj2eehomeoc4jclient.jar;D:JMSj2eehomelibbcel.jar;D:JMSj2eehomelibjms.jar ;D:JMSj2eehomelibjavax77.jar;D:JMSlibdms.jar;D:JMSopmnliboptic.jar;D:JMS j2eehomelibejb.jar;., VMOPTIONS= D:JMSlogjms.log For Unix Environment the CLASSPATH should be separated by : (colon) while for windows it should be ; (semicolon). So, the above command for Unix environment has to be the following: Create named subsystem JAVA for subsystem JVMSubSys with DLL= /usr/jdk1.5.0_06/jre/lib/sparc/client/libjvm.so, CLASSPATH = /export/home/qa1/ JMS:/export/home/qa1/JMS/Siebel.jar:/export/home/qa1/JMS/rdbms/jlib/aqapi.jar:/ export/home/qa1/JMS/jdbc/lib/ocrs12.jar:/export/home/qa1/JMS/jdbc/lib/ ojdbc14dms.jar:/export/home/qa1/JMS/jdbc/lib/orai18n.jar:/export/home/qa1/JMS/ SiebelJI_enu.jar:/export/home/qa1/JMS/j2ee/home/lib/adminclient.jar:/export/home/qa1/ JMS/j2ee/home/lib/jndi.jar:/export/home/qa1/JMS/j2ee/home/lib/jta.jar:/export/home/ qa1/JMS/j2ee/home/oc4jclient.jar:/export/home/qa1/JMS/j2ee/home/lib/bcel.jar:/export/ home/qa1/JMS/j2ee/home/lib/jms.jar:/export/home/qa1/JMS/j2ee/home/lib/javax77.jar:/ export/home/qa1/JMS/lib/dms.jar:/export/home/qa1/JMS/opmn/lib/optic.jar:/export/ home/qa1/JMS/j2ee/home/lib/ejb.jar:., VMOPTIONS= /export/home/qa2/JMS/log/jms.log Make sure that the path is correct for all the files and that the CLASSPATH ends with a . (dot). Here qa2 should be replaced with the appropriate folder name. 7 Log into the Siebel application and navigate to Site Map > Administration Server Configuration > Profile Configuration. a Query for the Profile with Alias Name ‘JAVA’ in the profile list and make sure the parameters are correct. b For the Windows environment, edit the value of VMOPTIONS to -Djms.log=D:JMSlogjms.log. c For the Solaris environment, edit the value of VMOPTIONS to -Xusealtsigs -Xrs -Djms.log=/ export/home/qa2/JMS/log/jms.log. Make sure that the JMS/log folder exists and has the write permission.
  • 218. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 218 8 Restart the Siebel Server. NOTE: For more information, see the Siebel Enterprise Application Integration (EAI) documentation on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/ siebel.html. Configuring Corresponding Web Services for Advanced Queue (AQ) The following section contains information about how to configure corresponding Web services for AQ. For more detailed information about AQ configuration, refer to the topic, “Process of Configuring JMS Messaging Between Siebel Business Applications and Oracle SOA Suite Using Oracle Advanced Queuing” section Transports and Interfaces: Siebel Enterprise Application Integration on the Siebel Bookshelf. Use the following procedure to configure corresponding Web services for AQ. To configure corresponding Web services 1 Navigate to Site Map > Administration - Web Services > Outbound Web Services and query for SWI*. 2 Change the transport to JMS and address as: jms://<queue name>@<connection factory> <queue name> will be in the below format: java:comp/resource/ <Resource Provider Name as configured >/Queues/<queue name> <connection factory> will be in the below format: java:comp/resource/<Resource Provider Name as configured>/QueueConnectionFactories/ QCF Queues must have been created as part of AIA installation. Please refer the same queue name here. 3 To locate the Connection Factory Name, log into Application Server control, and navigate to oc4j_soa ' Administration > Database Persistence. Here you can find the Resource Provider Name if it is configured. Example: jms://java:comp/resource/AIA_JMS_RP/Queues/ AIA_SALESORDERJMSQUEUE@java:comp/resource/AIA_JMS_RP/QueueConnectionFactories/ QCF 4 After changing the address, click Clear Cache. Setting Session Pool Manager The Session Pool Manager (SPM) is a service in the SOA Web server that manages a pool of Web server session tokens that are reused among BPEL flows. If SPM is enabled in AIA, use the following procedure to set Session Pool Manager values.
  • 219. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 219 To set Session Pool Manager values 1 Navigate to <siebel installation folder>/eappweb/bin, and make a backup copy of the eapps.cfg file. 2 Open eapps.cfg, and search for /eai_enu 3 Add the following parameters: ■ SessionTimeout = 300 ■ SessionTokenTimeout = 15 ■ SessionTokenMaxAge = 2880 ■ SWSENoSessInPref = TRUE 4 Restart the Siebel Web Server. Configuring Java Subsystem for Fusion Middleware 11g Integration In addition to performing the setup tasks for integrating Fusion Middleware in the Siebel installation guide, perform the following procedure. NOTE: The paths in this procedure assume you are running the Siebel server on the Windows operating system. They must be modified if the Siebel server is running on a UNIX operating system. Use the following procedure to confiugre Java subsystem for Fusion Middleware 11g Integration. To configure Java subsystem for Fusion Middleware 11g Integration 1 Get the wlfullclient.jar file from the FMW/AIA team. If you cannot get this file, perform the following steps to create wlfullclient.jar in the FMW server: a WinScp to the SOA server . b Change directories to the server/lib directory. (For example, go to WL_HOME/server/lib.) c Execute the java -jar wljarbuilder.jar command. The wlfullclient.jar file is created. 2 Remotely log into the Siebel installed server. 3 3. Get the files Siebel.jar and SiebelJI_enu.jar files from the <siebelinstallation>sessiebsrvrclasses folder. 4 Copy the wlfullclient.jar, Siebel.jar and SiebelJI_enu.jar files to the D:JMS directory. If this directory does not exist, create it.
  • 220. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 220 5 Prepare the jndi.properties file with the following values: java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory java.naming.provider.url=t3://<FMW_HOST>:<SOA_PORT> java.naming.security.principal=<UserName> java.naming.security.credentials=<Password> NOTE: If AIA is running on a clustered environment and a proxy host has been set up, then jndi.properties will have following URL: java.naming.provider.url=http:// <FMW_HOST>:<PROXY_PORT>. 6 Create the JAVA Subsystem using the Siebel Web application: 7 Connect to the server manager from the bin directory of the Siebel installed folder by entering the following command from the command prompt: Srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u <userid> /p <password> Example: srvrmgr /g sdc78198svqe:4330 /e siebel /s sdc78198svqe /u sadmin /p sadmin 8 Enter the following command to create the named subsystem: Create named subsystem JAVA for subsystem JVMSubSys 9 Add the following parameters with the aliases CLASSPATH, DLL and VMOPTIONs: 10 Create the Simulator (with the service name:EAI JMS Transport and Method name: CheckAll). Name Alias Data Type Value Scope Type Description Visibility JVM Classpath CLASSPATH String D:JMS;D:JMSSie bel.jar;D:JMSSieb elJI_enu.jar;D:JMS wlfullclient.jar;. Subsystem JVM Configuration Subsystem JVM Classpath Basic JVM DLL Name DLL String C:SunSDKjdkjre binserverjvm.dll Name Subsystem JVM Configuration Subsystem JVM DLL Name Basic JVM Options VMOPTION S String - Djms.log=D:JMSlo gjms.log Subsystem JVM Configuration Subsystem JVM Options Basic
  • 221. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 221 11 In the Input Argument Section create Test Case 1 with following values: Type: PropertySet Properties : PropertyName: ConnectionFactory PropertyValue: jms/TestQueueCF PropertyName: SendQueue PropertyValue: jms/TestQueue 12 Click Run to verify the setup in the simulator. It should not display any error messages after the run. Required Tasks for the Order to Cash PIP NOTE: The following tasks are required if you are using the Order to Cash PIP. Use the following procedure to disable Asset-Based Ordering. To disable Asset-Based Ordering 1 Log into the Siebel application, and navigate to Site Map > Administration - Server Configuration > Servers > Parameters. 2 Query for the corresponding object manager for the application (such as htimObjMgr_enu for application HTIM). 3 Query for the ‘Order Management - Enable Asset Based Ordering’ parameter in the parameter list for the component, and set the value to False. 4 Restart the Siebel Server. Running EIM Data Migration This section describes how to run the EIM jobs for implementing the O2C PIP. Data Migration Sequence The below entities should be executed in sequence to maintain the data integrity. This includes the pre-and post EIM activities, which need to be carried out manually. S.No Main Entities Task Type 1 Organization Manual 2 Inventory Location Manual 4 Products EIM 5 Post EIM Product Release Manual
  • 222. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 222 Before you begin the EIM import, note the following: ■ Make sure that the Siebel Server is running. ■ Make sure that the Siebel EIM component is online and is running properly. (To check this, navigate to the Administration - Server Configuration or Administration - Server Management screens.) ■ To avoid data loss, do not restart the Siebel Server while the EIM job is running. ■ After you have completed the data load for one country, make backup copies of the EIM logs, for status verification. These logs are located in the siebsrvr/logs directory. Checking EIM Component Availability Use the following procedure to check EIM component availability. To check EIM component availability 1 Navigate to the Administration - Server Management screen, then Servers, and then the Component Groups view. Make sure that the component group Enterprise Application Integration is active and online. 2 Make sure that the Enterprise Integration Manager component within the Workflow Management component group is also active and online. 3 Navigate to the Administration - Server Configuration screen, then Enterprise, then Component Groups, and then the Components Group Assignments view. 4 Make sure that the Enterprise Application Integration Component Group is enabled. Setting Up Organizations and Inventory Locations Use the following procedure to set up organizations and inventory locations. To set up organizations 1 Navigate to the Administration - Group screen, and then the Organizations view. 2 Create the required organizations. NOTE: Enter information into the Organization Name field but leave the Site field blank. 5 Pricelist EIM 6 Customers EIM 7 Assets EIM S.No Main Entities Task Type
  • 223. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 223 To set up inventory locations 1 Navigate to the Administration - Data screen, and then the Inventory Locations view. 2 Create inventory locations. NOTE: Make sure that the inventory location is associated with the correct location. Executing the EIM Job Use the following procedure to execute the EIM job. To execute the EIM job 1 Place the respective IFB file on the server machine using the Siebsrvr/Admin file path, as shown in the following example: 2 Make sure that the SESSION SQL statement of the [UPDATE ACCOUNT NUMBER] section of the Customer Ifb file is modified in order to reflect the working instance: UPDATE ORA19111.EIM_ACCOUNT SET OU_NUM = T_ORG_EXT__RID WHERE IF_ROW_BATCH_NUM=100 where ORA19111 is the working instance. Also, the same should be considered for the [UPDATE INTEGRATION ID] section of the Pricelist.ifb file: SESSION SQL = "UPDATE ORA19111.EIM_PRI_LST SET PL_INTEGRATION_ID = NULL WHERE PL_INTEGRATION_ID IS NOT NULL" For Pricelist.ifb, comment the second process using a terminate symbol (so that it becomes inactive and only the first process is executed), like this: [IMPORT ALL PRICELISTS] TYPE = SHELL INCLUDE = "IMPORT PRICELIST" Component IFB File Product Product.ifb Pricelist Pricelist.ifb Customer Customer.ifb Asset Asset.ifb
  • 224. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 224 ;INCLUDE = "UPDATE INTEGRATION ID" Once EIM imports all of the pricelist data and the Integration Id is populated, the administrator needs to run another ODI API to populate the cross-reference database. Then, the administrator needs to run EIM again to nullify integ_id. The format of the IFB file for the second run will look like: [IMPORT ALL PRICELISTS] TYPE = SHELL ;INCLUDE = "IMPORT PRICELIST" INCLUDE = "UPDATE INTEGRATION ID" All the job parameters should remain the same for both of the runs. 3 Log into the application with administrator credentials in order to be able to access the Server Management screen. 4 Navigate to the Administration - Server Management screen, and then the Jobs view. 5 Click New and select "Enterprise Integration Mgr" in the Component/Job tab. 6 In the "Job Parameters" applet, fill in the following parameters: ■ Configuration file = .Ifb File name ■ Error Flags = 1 ■ SQL Trace Flags = 8 ■ Trace Flags = 1 7 After passing parameters, click Submit Job. 8 In the Jobs view, for each job that you have executed, make sure that the Status columndisplays “Success” for the jobs that you have executed. 9 Check the status in the EIM table by executing the SQL statements in the following section. In each case, make sure that the status is IMPORTED. Products Product Header: SELECT COUNT(*),IF_ROW_STAT FROM EIM_PROD_INT WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT Product Details: SELECT COUNT(*),IF_ROW_STAT FROM EIM_PROD_INT1 WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT
  • 225. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 225 Product-Inventory Locations: SELECT COUNT(*),IF_ROW_STAT FROM EIM_PRODINVLOC WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT Pricelists In this case since the same set of records are processed twice by the two separate sections of the IFB file: one meant for importing the Pricelist Records and other meant for updating the Integration Id to NULL, you will get the DUP_REC_EXISTS status in the EIM tables. SELECT COUNT(*),IF_ROW_STAT FROM EIM_PRI_LST WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT Customers Address: SELECT COUNT(*),IF_ROW_STAT FROM EIM_ADDR_PER WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT Account: SELECT COUNT(*),IF_ROW_STAT FROM EIM_ACCOUNT WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT Account Details: SELECT COUNT(*),IF_ROW_STAT FROM EIM_FN_ACCNT1 WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT Customer: SELECT COUNT(*),IF_ROW_STAT FROM EIM_CONTACT WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT Assets There are two sections in the IFB file: For Importing Assets and For Updating the Parent Assets.
  • 226. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 226 Hence the status will show DUP_REC_EXISTS SELECT COUNT(*),IF_ROW_STAT,IF_ROW_BATCH_NUM FROM EIM_ASSET WHERE IF_ROW_BATCH_NUM = '100' GROUP BY IF_ROW_STAT,IF_ROW_BATCH_NUM Use the following procedure to check the EIM log. To check the EIM log 1 From the Jobs view in the Administration - Server Management screen, navigate to the Tasks View in the same screen. 2 Get the Task Number from the Task field. 3 Navigate to the Siebsrvrlog directory and query for the locate the log file using the Task #. The log file contains details about of every level of processing, as well as information about any errors. Postinstallation Tasks You must perform the tasks listed in this section. NOTE: These postinstallation tasks only apply to the Order to Cash PIP. To release the products 1 Navigate to the Administration - Business Service screen. 2 In the top applet, create a new record with the following values: ■ Service Name: ISS Authoring Import Export Service ■ Method Name: Post_EIM_Upgrade 3 In the bottom applet, create the Input Argument by creating pop up icons on the Property Name Field, using the following values: ■ Property Name: ReportOnly ■ Value: FALSE ■ Property Name: RootObjectType ■ Value: ISS_JWS ■ Property Name: RootObjectName ■ Value: Staging Mode 1 NOTE: The RootObjectName should be any meaningful name for the Joint Workspace Project. This will be created automatically after the Business Service is executed from the simulator. 4 Click the Run button in the top applet and wait until the job ends.
  • 227. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 227 To get the joint workspace Row ID 1 Navigate to the Administration - Product screen, and then the Workspace Projects view. 2 Query for the value provided for the RootObjectName input parameter given while running the ISS Authoring Import Export Service (as in Step 4 of “To release the products” on page 226). 3 Go to the Menu option and click the About Record method or use the keyboard shortcut (CTRL + ALT + K) while on the active record. 4 Make a note of the Row # value displayed in the pop-up applet, as you will need this value to provide the input argument to the workflow process. To release the noncustomizable and orderable products 1 Navigate to the Administration - Business Process screen, then Workflow Deployment, and then the Repository Workflow Processes view. 2 In the "Active Workflow Processes" view, search for the "SWI Initial Load Non CP Order Release" workflow to make sure that the active version of the workflow is present in the repository. 3 If this record is not present, query for the “SWI Initial Load Non CP Order Release” workflow in the “Repository Workflow Processes" applet, and click Activate after you locate the record. 4 If the workflow is not present in either of the previous applets, within the Active Workflow Processes applet, select Menu, select the Import Processes functionality, and choose the SWI Initial Load Non CP Order Release -WF.xml file from the Browse window. 5 Navigate to the Administration - Server Management screen, and then the Jobs view. 6 Click the New button on the top applet to create a new job, and enter "Workflow Process Batch Manager" as the value for “Component/Job”. 7 Navigate to the "Job Parameters" applet and create the following two new values: ■ Name= “Workflow Process Name” ■ Value = “SWI Initial Load Non CP Order Release” ■ Name “Search Specification” ■ Value = [Par JWS Id] = '6SIA-4HVMH' AND [Orderable Flag] = 'Y' AND [Product Def Type Code] <> LookupValue ("PROD_TYPE_CD", "Customizable") NOTE: The Parent Joint Workspace Id value is the same as the one in Step 5 of “To get the joint workspace Row ID” on page 227. 8 Click the "Submit" button and wait until the job ends successfully. Configuring Oracle Configurator Use the following instructions to apply the run changes for the configuration to the database. To apply runtime Siebel configuration changes You must perform the following runtimeconfiguration changes before you launch Oracle configurator.
  • 228. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 228 1 Log into the eCommunications/HTIM application from a browser. 2 Navigate to Site Map > Administation Business process > Repository workflow process. a In the top applet, query for the workflows that you imported previously and activate them. b In the bottom applet, query for the workflows to make sure that they are in an active state. 3 Navigate to Site Map > Administation Order Management > Signals. a Query for the Customize signal. b Lock the signal record and click on Workspace. c Change the service name to SWI Configurator Load. d Navigate back to the Signals view and click the Release New Version button to release a new version of the signal. e Query for the QuotesAndOrdersValidate signal. f Lock the signal record and click on Workspace. g Replace the Siebel Verification with Oracle Batch Validate'. Change all four records with sequence #2. ❏ Mode = Quote, Instance Type = Line Item - Change Service Name column to "Oracle Verify Item (Quote)" ❏ Mode = Order, Instance Type = Line Item - Change Service Name column to "Oracle Verify Item (Order)" ❏ Mode = Quote, Instance Type = Header - Change Service Name column to "Oracle Verify Header (Quote)" ❏ Mode = Order, Instance Type = Header - Change Service Name column to "Oracle Verify Header (Quote)" 4 Navigate to Administration Runtime Events > Events and click Menu > Reload Runtime Events. 5 Navigate to Administration - Application > Views. a Verify the following new views: ❏ CZRuntimeInstanceView (JS) ❏ CZRuntimeInstanceView (JS) - Agreement ❏ CZRuntimeInstanceView (JS) - Order (Sales) ❏ CZRuntimeInstanceView (JS) - Favorites b For each view, assign the appropriate responsibility so that the user with that responsibility can navigate to this view. This is part of seed data. It should be done when exporting the seed data. 6 Navigate to Administration - Integration > WI Symbolic URL List. a In the top applet, from the drop-down menu (bold highlighted menu), select Host Administration. b Add a new host entry with the following values:
  • 229. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 229 ❏ Host Name: <Oracle EBIZ host name:port number> for example qapache.us.oracle.com:3710 ❏ Virtual Name: OracleConfigurator c Select Symbolic URL Administration and add a new record in the top applet. ❏ Name: OracleCfgURL (Note: This symbolic name is very important because the server- side business component code relies on this name.) ❏ URL: http://OracleConfigurator/OA_HTML/CfgSebl.jsp ❏ Choose the host name (such as qapache.us.oracle.com:3710) ❏ Fixup Name: Default ❏ SSO Disposition: IFRAME d In the bottom applet, add arguments to the URL by creating a new record with the following values: ❏ Name: InitMessage ❏ Req Arg: checked ❏ Argument Type: Profile Attribute ❏ Argument Value: CZInitMessage ❏ Append as argument: checked e Add another new row: ❏ Name: PostRequest ❏ Required Arg: Checked ❏ Argument Type: Command ❏ Argument Value: PostRequest ❏ Append as argument: Not-Checked f Complete the following two steps to set up the SSO login into Oracle applications: NOTE: The SSO login is the preferred method for accessing Oracle applications. If you do not set up the SSO login, the Siebel end user must enter Oracle login credentials at the login page. g For the next two arguments enter the values for Argument Value as specified. UserLoginId and UserLoginPassword are function names used by Siebel SSO. These functions look up the Oracle login credentials for the Siebel application user. If the user enters other values, they will be required to log into an Oracle Applications for Configurator session. h Continue to add arguments to the same URL: ❏ Name: username ❏ Required Arg: Checked ❏ Argument Type: Command ❏ Argument Value : UserLoginId
  • 230. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 230 ❏ Append as argument: Checked i Add the final argument: ❏ Name: password ❏ Required Arg: Checked ❏ Argument Type: Command ❏ Argument Value: UserLoginPassword ❏ Append as argument: Checked j Select "SSO Systems Admin List" and add a record in the top applet. ❏ System Name: OracleConfigSSO ❏ Symbolic URL Name: OracleCfgURL ❏ Description: Logs in to the Oracle Configurator k In the bottom applet "SSO System Users" add records for the Siebel users that will be invoking Oracle Configurator. The Siebel user names will be paired with Oracle login credentials. For example: ❏ Siebel Login Name: sadmin ❏ Login Name: operations ❏ Password: welcome 7 Navigate to Administration - Server Configuration > Components, select the "eCommunications Object Manager (ENU)" component, select the "Order Management - Enable Asset Based Ordering" parameter and set this value to False to call Oracle Configurator instead of calling Siebel Configurator. 8 Navigate to the "HTIM Object Manager (ENU)" component, select the "Order Management - Enable Asset Based Ordering" parameter, and set this value to False to call Oracle Configurator instead of calling Siebel Configurator. The following workflows need to be activated for Configurator to work. Note that these are not workflows that were introduced as part of the Oracle Configurator integration; they already existed. ■ Account - New Quote ■ Account - New Order ■ Goto* ■ PSP* ■ Product Compatibility* ■ Product Eligibility* ■ Product Reco* ■ *Pric* ■ Compatibility Multiple Popup Workflow
  • 231. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 231 ■ Config* ■ Check* Adding Siebel Custom Applications to Oracle Applications Several custom Oracle applications need to be created to allow models to be accessed from the Siebel application. These custom applications are used during the publication phase of the Oracle Configurator Model development cycle. To add Siebel Custom Applications to Oracle Applications 1 Log in to Oracle Applications with system administrator credentials, and navigate to Application > Register. 2 If the form page does not display, navigate to the form. 3 Create three new entries with four values: ■ Siebel Quote Integration |SEBLQ | DUMMY_TOP |Provides integration between Siebel Quote and Oracle Configurator ■ Siebel Order Entry Integration | SEBLO | DUMMY_TOP | Provides integration between Siebel Order Entry and Oracle Configurator ■ Siebel Agreement Integration | SEBLA | DUMMY_TOP | Provides integration between Siebel Agreement and Oracle Configurator The new applications now must be added to Oracle Configurator Publication Applicability list. 4 Change the responsibility to Configurator Administrator. 5 Choose Application to Publication Applicability List and add the applications. This step runs a concurrent program. Once the program runs, these new applications will be available during model publication. Refer to Oracle documentation for Configurator for information about how to develop models for calling applications. Copy Config Web Service Setup 1 Log in to the eCommunications/HTIM application from a browser. 2 Navigate to Administation Web Services > Outbound Web Services. 3 Click Import to import 'ESB_ConfiguratorCopyConfigEbizAdapter_Service.XML'. 4 Click Import to import 'ConfiguratorUserLangSiebelAdapter.XML'. NOTE: Step 1 through 4 is part of seed data. It should be done when exporting the seed data. 5 After importing, change the IP Address on the Service Ports (middle applet) for each of the preceding web services.
  • 232. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 232 Copy Config Data Map Setup 1 Log in to eCommunications/HTIM application from a browser and navigate to Administration - Application > Data Map Administration. 2 For the following data maps, add three columns named 'External Configurator Reference 1','External Configurator Reference 2', and 'External Configurator Reference 3' to both the Source and the Destination Column in the Data Map Field section for the data map component specified in the parentheses: ■ AutoAgreement (Data Map Component:Line Item) ■ AutoAgreeFromOrder (Data Map Component Name:Line Items) ■ CopyOrder (Data Map Component Name:Line Item) ■ CopyQuote (Data Map Component Name:Line Item) ■ OrderToTemplate (Data Map Component Name:Line Item) ■ QuoteToSalesOrder (Data Map Component Name:Line Item) ■ QuoteToServiceOrder (Data Map Component Name:Line Item) ■ QuoteToTemplate (Data Map Component Name:Line Item) ■ ReviseAgreement (Data Map Component Name:Line Item) ■ ReviseOrder (Data Map Component Name:Line Item) ■ ReviseQuote (Data Map Component Name:Line Item) ■ TemplateToOrder (Data Map Component Name:Line Item) ■ TemplateToQuote (Data Map Component Name:Line Item) DoCompression Parameter Setup 1 Stop the Siebel Server. 2 Back up the eapps.cfg file, which is located in the eappwebbin folder within your installation directory. 3 Edit eapps.cfg using Notepad. CAUTION: Do not use Wordpad, as this will cause incorrect characters to be added to the file. 4 Reset the DoCompression parameter in the [defaults] section. It should now be DoCompression=FALSE. 5 Restart the machine. NOTE: You must restart the machine. Restarting only the Siebel Server will not make your changes take effect. Applying Changes for the Signal 1 Navigate to Administration - Order Management > Signal.
  • 233. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 233 2 To change the signal sequence (if required), lock the signal, click the workspace, make the sequence changes described in the following tables, and click the Release button to release the signal. Table 12. CalculateShippingAndTax Signal Service Name Service Type Sequence Condition Active Mode SWISendCalculateShippingCha rge Workflow 1 SystemPreference("Enable AIA OrderToCash")="TRUE Yes Order ISS Tax Calculation Service Business Service 2 Yes Order ISS Shipping Calculation Service Business Service 3 No Order ISS Tax Calculation Service Business Service 2 Yes Quote ISS Shipping Calculation Service Business Service 3 Yes Quote Table 13. CreditCardAuthentication Signal Service Name Service Type Sequence Condition Active Mode SWISendPaymentAuthorization Workflow 1 SystemPreference("Enable AIA OrderToCash")="TRUE” Yes Payment ISS Credit Card Transaction Service Business Service 2 Yes Payment ISS Credit Card Transaction Service Business Service 2 Yes Quote Table 14. RunCreditCheck Signal Service Name Service Type Sequence Condition Active Mode SWISendCreditCheck Workflow 1 SystemPreference("E nable AIA OrderToCash")="TRU E” Yes Payment ISS Credit Check Service Business Service 2 Yes Table 15. ATPInquire Signal Service Name Service Type Sequence Condition Active Mode SWISendATPCheckLine Workflow 1 SystemPreference("Enable AIA OrderToCash")="TRUE” Yes Order ISS ATP Service BusinessService 2 Yes
  • 234. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 234 Fixing State Model for Quote Status Use the following procedure to extend the state model To make Quote Status work, you can extend the related State Model activation date. 1 Navigate to Administration - Application > State Model and search for "TNT SHM Quote Status". 2 Extend its activation date until 2020 (leave day and month as sysdate). Table 16. ATPInquireAll Signal Service Name Service Type Sequence Condition Active Mode SWISendATPCheck Workflow 1 SystemPreference("E nable AIA OrderToCash")="TRU E Yes Order ISS ATP Service Business Service 2 Yes Table 17. Customize Signal Service Name Service Type Sequence Condition Active Mode SWI Configurator Load Workflow 1 SystemPreference("Enable AIA OrderToCash")="TRUE” Yes Table 18. QuotesAndOrdersValidate Signal Service Name Service Type Sequence Condition Active Mode PSP Driver Workflow Process Workflow 1 Yes Order PSP Driver Workflow Process Workflow 1 Yes Order Oracle Verify Header (Order) Workflow 2 SystemPreference("Enable AIA OrderToCash")="TRUE” Yes Order Oracle Verify Item (Order) Workflow 2 SystemPreference("Enable AIA OrderToCash")="TRUE” Yes Order PSP Driver Workflow Process Workflow 1 Yes Quote PSP Driver Workflow Process Workflow 1 Yes Quote Oracle Verify Item (Quote) Workflow 2 SystemPreference("Enable AIA OrderToCash")="TRUE” Yes Quote Oracle Verify Header (Quote) Workflow 2 SystemPreference("Enable AIA OrderToCash")="TRUE” Yes Quote
  • 235. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 235 Other Order to Cash Configuration Steps 1 Navigate to Administration - Application > Data Map Administration and query for the ReviseOrder data map object, the Header data map component, and the Back Office Process Status data map field. 2 Select the Inactive check box to inactivate the Back Office Process Status data map field. 3 Navigate to Administrator > Data Validation > Rule Sets and query for the following rule sets: ❏ O2C Order Validation ❏ O2C Payment Authorization ❏ O2C Quote Validation ❏ O2C Cancel Order Validation ❏ SWI Revise Order Validation 4 Activate these five rule sets by clicking the Activate button on the top applet. Rule Name Expression Sequence Business Component Apply To Return Code Account (SystemPreference("E nable AIA OrderToCash")="FALS E") OR (([Account Id] IS NOT NULL AND [Bill To Account Id] IS NOT NULL AND [Bill To Address Id] IS NOT NULL AND [Ship To Account Id] IS NOT NULL AND [Ship To Address Id] IS NOT NULL)) 1 PDS Simplified Order Entry - Orders Current Record O2C-Order- 002 Status (SystemPreference("E nable AIA OrderToCash")="FALS E") OR ([Status] = LookupValue("FS_OR DER_STATUS","Booke d")) 2 PDS Simplified Order Entry - Orders Current Record O2C-Order- 002
  • 236. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 236 Resubmit (SystemPreference("E nable AIA OrderToCash")="FALS E") OR (([Back Office Process Status] IS NULL) OR ([Back Office Process Status] = LookupValue("EAI_OR DER_SYNC_STATUS", "Error on Creating"))) 3 PDS Simplified Order Entry - Orders Current Record O2C-Order- 003 Payment ((SystemPreference(" Enable AIA OrderToCash")="FALS E") OR ((([Payment Method] =LookupValue("PAYM ENT_METHOD_CODE" ,"Credit Card") OR [Payment Method] = LookupValue("PAYME NT_METHOD_CODE"," Purchase Order")) AND [Payment Status] = LookupValue("FUNDR Q_STATUS","Approve d")) OR ([Payment Method] NOT LIKE LookupValue("PAYME NT_METHOD_CODE"," Credit Card") AND [Payment Method] NOT LIKE LookupValue("PAYME NT_METHOD_CODE"," Purchase Order")) OR ([Payment Method] IS NULL))) 4 Payments All Records O2C-Order- 004 Rule Name Expression Sequence Business Component Apply To Return Code
  • 237. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 237 Credit Hold (SystemPreference("E nable AIA OrderToCash")="FALS E") OR ([Hold Flag] ="N" ) 5 PDS Simplified Order Entry - Orders Current Record O2C-Order- 005 Cancel Reason not empty NOT(SystemPreferenc e("Enable AIA OrderToCash")="TRU E" AND ([Request To Cancel] = "Y" AND [Cancel Reason] IS NULL)) 6 PDS Simplified Order Entry - Line Items All Records SWI_CANCE L_ORDER_0 02 Rule Name Expression Sequence Business Component Apply To Return Code Card Filled (SystemPreference( "Enable AIA OrderToCash")="FA LSE") OR (([Payment Method] =LookupValue("PAY MENT_METHOD_CO DE","Credit Card") AND [Credit Card Number - Display] IS NOT NULL) OR [Payment Method] <> "Credit Card") 1 Payments Current Record O2C-Order-006 Rule Name Expression Sequence Business Component Apply To Return Code
  • 238. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 238 Rule Name Expression Sequence Business Component Apply To Return Code O2C Account (SystemPreferen ce("Enable AIA OrderToCash")=" FALSE")OR ([Account Id] IS NOT NULL ) 1 PDS Simplified Quote Current Record O2C-Quote- 002 O2C Ship Address (SystemPreferen ce("Enable AIA OrderToCash")=" FALSE") OR ([Ship To Address] IS NOT NULL) 2 PDS Simplified Quote Current Record O2C-Quote- 004 O2C Bill Address ((SystemPrefere nce("Enable AIA OrderToCash")=" FALSE") OR ([Bill To Address] IS NOT NULL )) 3 PDS Simplified Quote Current Record O2C-Quote- 003 O2C Already Processed (SystemPreferen ce("Enable AIA OrderToCash")=" FALSE") OR ([EAI Status] IS NULL OR [EAI Status] = LookupValue("EA I_ORDER_SYNC_ STATUS","Error on Creating") or [EAI Status] = LookupValue("EA I_ORDER_SYNC_ STATUS","Creati ng in Back Office")) 4 PDS Simplified Quote Current Record O2C-Quote- 005 O2C Quote Status (SystemPreferen ce("Enable AIA OrderToCash")=" FALSE") OR ([Status] = LookupValue("Q UOTE_STATUS"," Approved")) 5 PDS Simplified Quote Current Record O2C-Quote- 001
  • 239. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 239 Rule Name Expression Sequence Business Component Apply To Return Code SWI Active Check (SystemPreferenc e("Enable AIA OrderToCash")="F ALSE")OR ([Account Id] IS NOT NULL ) 1 PDS Simplified Order Entry - Orders Current Record SWI Order Revise 001 SWI Revise Order (SystemPreferenc e("Enable AIA OrderToCash")="F ALSE") OR (([Back Office Process Status] = LookupValue("EAI _ORDER_SYNC_S TATUS","Created in Back Office")) OR (([Status] = LookupValue("FS_ ORDER_STATUS", "Booked"))) AND (([Status] <> LookupValue("FS_ ORDER_STATUS", "Shipped")) AND ([Status] <> LookupValue("FS_ ORDER_STATUS", "Closed")))) 2 PDS Simplified Order Entry - Orders Current Record SWI Order Revise 002
  • 240. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 240 SWI Revise Order Line (SystemPreferenc e("Enable AIA OrderToCash")="F ALSE") OR((([Status] = LookupValue("FS_ ORDER_STATUS", "Booked")) OR ([Status] = LookupValue("FS_ ORDER_STATUS", "Picked")) OR ([Status] = LookupValue("FS_ ORDER_STATUS", "Cancelled")) OR ([Status] = LookupValue("FS_ ORDER_STATUS", "Pending")) OR ([Status] = LookupValue("FS_ ORDER_STATUS", "Shipped")) OR ([Status] = LookupValue("FS_ ORDER_STATUS", "Closed")) OR ([Status] = LookupValue("FS_ ORDER_STATUS", "Configured Item created")))) 3 PDS Simplified Order Entry - Orders All Records SWI Order Revise 003 SWI Back Office Check (SystemPreferenc e("Enable AIA OrderToCash")="F ALSE") OR ([Back Office Process Status] = "Created in Back Office") 4 PDS Simplified Order Entry - Orders Current Record SWI Order Revise 002 Rule Name Expression Sequence Business Component Apply To Return Code
  • 241. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 241 5 Restart the Siebel Server. 6 Launch the Siebel Communications application. Required Tasks for the COMM PIP NOTE: If you are implementing the Communications Order to Cash Integration Pack for Siebel CRM, you must perform the tasks in this topic. To activate the rule sets for Comms 1 Query for the Order Validation rule set. Rule Name Expression Sequence Business Component Apply To Return Code PONR Not Reached NOT(SystemPref erence("Enable AIA OrderToCash")=" TRUE" AND ([Status] = LookupValue ('FS_ORDER_ST ATUS', 'Shipped')) or ([Status] = LookupValue ('FS_ORDER_ST ATUS', 'Closed')) or ([Status] = LookupValue ('FS_ORDER_ST ATUS', 'Fulfilled')) or ([Status] = LookupValue ('FS_ORDER_ST ATUS', 'Supply Eligible'))) 1 PDS Simplified Order Entry - Line Items All Records SWI_CANCEL _ORDER_001 Cancel Reason not empty NOT(SystemPref erence("Enable AIA OrderToCash")=" TRUE" AND ([Cancel Reason] IS NULL)) 2 PDS Simplified Order Entry - Line Items Current Record SWI_CANCEL _ORDER_002
  • 242. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 242 2 If two versions are displayed as active, select the earliest version. For example, if the active versions are 5 and 6, select version 5. 3 Select Deactivate Rule Set from the submenu. 4 Navigate to Administration - Runtime Events > Events screen, and select Reload Runtime Events from the drop-down list. NOTE: If two active versions are displayed for “SWI Order Validation Rule Set”, use the previous procedure. Running EIM Data Migration for Comms This section defines the detailed steps to run the EIM jobs for Siebel applications as a part of the Creating and Updating Credit Alerts for Collection Flows functionality in AIA COM 2.5. The ODI interface will be triggered totransport the required data for creating/updating Credit Alerts from BRM into the Siebel EIM tables. EIM scripts will bethen executed to load the data into the SFA base tables. Before you begin your import, do the following: ■ Make sure that the Siebel Server is up and running. ■ Make sure that the Siebel EIM component is online and running properly. To check this, navigate to the Administration - Server Configuration and Administration - Server Management screens. ■ To avoid data loss, do not restart the Siebel server while the EIM job is running. ■ After you have completed loading data for one country, make a backup copy of the EIM logs for status verification. (These logs are located under siebsrvr/logs.) Use the following procedure to execute the EIM job to create and update credit alerts. To execute the EIM job to create and update credit alerts 1 Move the ProcessAlertsAndBillingProf.ifb file from <Tools Installation directory>/REPPATCH/ ACR474/EIM to <Siebel Installation Directory>/ses/siebsrvr/ADMIN. 2 Run the EIM job with the ProcessAlertsAndBillingProf.ifb configuration file. 3 Verify that the EIM job is successful. NOTE: If the Order to Cash PIP is enabled, the Asset-Based Ordering parameter for the corresponding object manager for the application must be set to False. This section describes the integration user setup process. A new flag has been introduced to identify an integration user (needed while integration testing). This user credential must be configured (on the AIA side) for the Siebel Inbound Web services call from the AIA side to avoid the boomerang effect. Enabling Dynamic Pricing (Customer Order Management) The pricing module is available in multiple licensing modes.
  • 243. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 243 Dynamic Pricing Mode ■ This mode provides pricing capabilities such as attribute pricing, promotions, aggregate discounts, and so on. ■ It leverages the variable maps that contain the XA child variable maps. ■ It is available only to users who have the Dynamic Pricer license. ■ Dynamic Pricing can also be enabled by navigating to Admin - Pricing > Price List, and selecting Enable Dynamic Pricing from the applet-level menu. ■ This is a new implementation in Siebel version 8.1.1 applications. After you select Enable Dynamic Pricing, all the necessary changes will be performed. Configuring the Email Notification for the Product Class and Attribute Query Feature Users to whom emails need to be sent need to be added to the user list. To add/change the email addresses for the user list 1 Navigate to Administration - Users > Users. 2 Add user name and user ID. 3 Add the email address in the contact information of the child applet. 4 Navigate to Administration - Group > User Lists and query for the SCE Users user list. NOTE: If this list does not appear, create it. 5 Add the users created in the user list. The user list created in the previous procedure is passed in the run time events. Use the following procedure to add the changed user list. To change the BO/BC/Field name to extract the email addresses 1 Navigate to Administration - Run Time Events > Action Set, and query for the EmailNotify action set.
  • 244. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 244 2 Query for the 'GetEmailAddr' action in the child applet The following is the business service context syntax- "Parent BC Record Name";"Field Name in Child BC ";"BO Name ";"Parent BC";"Child BC" For instance- "SCE Users";"Email Address";"Account";"Account";"Contact" or "SCE Users";"EMail Addr";"User List";"User List";"User" The following run-time events use the action set described above. Four communications templates are used to send email messages. The Attribute Defn and Product Class templates are already configured. Use the following procedure to configure or edit other templates. To edit or configure email template text 1 Create a notepad file called "Attribute_Template.txt" and add the following values: ■ Attribute Name: [Name] ■ Description: [Description] ■ Type: [Type] ■ Object Number: [Object Number] ■ XRef Class Name: [XRef Class Name] 2 Create a notepad file called "Class_Template.txt" and add the following values: ■ Class Name: [Name] ■ Description: [Description] ■ Type: [Type] ■ Object Number: [Object Number] Sequence Object Type Object Name Event Subevent Action Set Name 1 BusComp Attribute VOD BusComp PreInvokeMethod SendEmail EmailNotify 2 BusComp ISS Class VOD BusComp PreInvokeMethod SendEmail EmailNotify 3 BusComp ISS Joint Workspace BusComp PreInvokeMethod SendEmail EmailNotify
  • 245. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 245 3 Navigate to Administration - Communication > All Templates > Template Items. 4 Query for Workspace Attribute Defn Template and click on Template Items View. 5 Attach the "Attribute_Template.txt" file created in Step 1 in the template item. 6 Navigate to Administration - Communication > All Templates > Template Items. 7 Query for "Workspace Product Class Defn Template" and click on Template Items View. 8 Attach the "Class_Template.txt" file created in Step 2 in the template item. 9 Make sure that "ISS Joint Workspace VOD Pick BucComp" is selected in the iteration child business component for above two template items. The communication template names are added in the user properties of the business components listed in the following table. The SMTP Server name, From Email Address, and POP server details are added in the a Communication profile. Use the following procedure to add the SMTP server name, From Email Address, and POP server details. To change the SMTP Server name, From Email Address, and POP server details 1 Navigate to Administration - Communications > Communications Drivers and Profiles. 2 Query for the Internet SMTP/POP3 Server communication driver, and if it does not exist, create it using the following values: ■ Name: Internet SMTP/IMAP Server ■ Channel Type: Email ■ Channel String: POP3SMTP ■ Library Name: sscmmail ■ Outbound: Yes 3 Query for Default SMTP in the child applet, and if it does not exist, create it. 4 Change the SMTP and POP Server details in the grandchild applet, using the following values: ■ From Address: siebel.product.admin@demohost.siebel.com Business Component User Property Template Name ISS Joint Workspace BusComp PackageNameList|Attribute Definition Workspace Attribute Defn Template ISS Joint Workspace BusComp PackageNameList|Product Class Definition Workspace Product Class Defn Template Attribute VOD BusComp PackageNameList Attribute Defn Template ISS Class VOD BusComp PackageNameList Product Class Template
  • 246. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 246 ■ POP3 Account Name: support ■ POP3 Account Password: support ■ POP3 Server: demohost.siebel.com ■ SMTP Server: rgmamersmtp.oraclecorp.com The communication profile is added the in the user properties of the business components listed in the following table: To set up the Time-Based Offering feature 1 Create Product Master Data. a Create three attributes: ❏ Duration (Number/Enumerated, values 1, 2,3, … 31) ❏ DurationUnitOfMeasure (Text/Enumerated values: Days, Months, Years) ❏ DurationValidityStart (Text/Enumerated Values: Original Start, Now, Original End) b Create a class with the preceding three attributes. NOTE: The class attribute names and the attribute definition names must be identical. c For the TBO Discount products synced from BRM, change the structure type to Customizable, change the product type to Time Based Offer, and associate the preceding TBO class to this product. 2 Create Job to Inactive Assets. a Navigate to Server Management > Jobs, and create a new job. ❏ Select Component as “Workflow Process Batch Manager”. ❏ Select Repeating as “Y”. ❏ Select Requested Server as the Siebel Server. ❏ Select Repeat Unit as “Days”. ❏ Select Repeat Interval as “1”. ❏ Select Repeat From as “Scheduled Start”. b Navigate to Job Parameters and create a new parameter. c Select Workflow Process Name as the name and specify SWI Asset Status Update as the value. d Select Search Specification as the name and specify the value if necessary. Business Component User Property Template Name ISS Joint Workspace BusComp CommProfileOverride Default SMTP Profile Attribute VOD BusComp CommProfileOverride Default SMTP Profile ISS Class VOD BusComp CommProfileOverride Default SMTP Profile
  • 247. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 247 3 Create Revision Data Maps. a Navigate to Administration – Application, and then Data Map Administration. b In Data Map Object, query for Name = “Revise Order” or “ReviseQuote”. c In Data Map Component, query for Name = “Line Item”. d In Data Map Field, add the fields that needs to be copied during revision (such as Service End / Service Start Date/Due Date). 4 Configure the business service. The business service name must be specified asthe value for the “Business Service Query Access List” server component parameter. For example, if the server component is “eCommunications Object Manager (ENU)”, navigate to its parameters, query for Name = “Business Service Query Access List”, add Value = “CMU External Integration Service”, and restart the server component so that the change to the component parameter value takes effect. 5 Release the data maps: a Navigate to Site Map > Administration- Order Management > Variable Maps. b In Variable Map, query for the following: ❏ Default Pricing Eligibility Variable Map - Row Set ❏ Default Pricing Variable Map - Row Set ❏ Default Pricing Variable Map – XA c Lock the preceding variable maps and release a new version. Tasks Required for the MDM PIP The following tasks are required if you are using the MDM PIP. To activate the workflow policies 1 Navigate to Administration - Business Process Screen, and then Workflow Policies view. 2 Query for the following workflow policies and remove the expiration date: ■ SWI Account Address Sync Policy ■ SWI Account Contact Sync Policy ■ SWI Account Sync Policy ■ SWI Address Sync Policy ■ SWI Contact Address Sync Policy ■ SWI Contact Sync Policy 3 Remove the existing triggers, and then generate the triggers.
  • 248. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 248 4 Restart Siebel Services. NOTE: By default, the Workspace Release Flag user preference is set to N. Ifyou want to release products into the Siebel application automatically, you must change this preference. To customize the Workspace Release flag 1 Navigate to Site Map > Administration - Application > System Preferences. 2 Query for 'Workspace Release Flag', set the value to N, and restart the server. Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 475 Use the procedures in the following section to configure ACR 475. System Requirements for ACR 475 The following section contains information about the supported databases and operating systems for ACR 475. System Requirements for DRM DRM version 11.1.2.0.3 is certified with Siebel 8.1.1.4. The following operating systems are supported: ■ Microsoft Windows 2003 and 2008 The following database is supported: ■ Oracle 10g/11g The following homogenous operating system/database combinations are certified: NOTE: Both Oracle and IIR servers are on the same operating system and both the Oracle database and the IIR database are on the same database. ■ Microsoft Windows 2003/Oracle 11g NOTE: Hyperion Data Relationship Management is only supported on the Windows platform. Software Version Description ADF 11.1.1.54.7 Oracle framework for the Java application ANT 1.6 A Java-based build tool JDK 1.6 Provides runtime for the Java application Weblogic 10gR3 Java application server
  • 249. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 249 Release Notes for ACR 475 The following section contains information about known issues with ACR 475. Querying for New Prospects Causes Error Category: Data Quality Subcategory: ODQ Connector Product Version: 8.1.1.4 Change Request: 12-215L8J5 When users query for a newly-created prospect, they receive an error message. ■ Within Prospect Mapping, do the following: ■ Change the Vendor Mapping Id to Row Id. ■ Within Siebel Tools, navigate to the List Mgmt Prospective Contact business component, add a new field called RowId, and map it to Id. Installer Does Not Overwrite Customer Version of CCHtmlType.swf Change Request: 12-1TK672L Product: Siebel 8.1.1.1 QF3101 The installer does not automatically overwrite the customer version of the CCHtmlType.swf file. The UI-related fixes will not take effect unless the configuration files are delivered by the installer. To receive the updated configuration files, users must set the Overwrite flag to “Y” in the Siebel.ini file. 1 Copy the patch installer onto the local machine. 2 Change the value of OverWriteConfig=Yes in the following files: ❏ Siebel_Enterprise_Server/enu/siebel.ini ❏ Siebel_Enterprise_Server/siebel.ini ❏ Siebel_Web_Server_Extension/enu/siebel.ini ❏ Siebel_Web_Server_Extension/siebel.ini 3 Install the base release and the patch. Back Button Navigates Incorrectly When Tabs Present Change Request: 12-1UTNLYY Product: Siebel 8.1.1.1 QF3103 The Back button navigates incorrectly when tabs are present in the DGM screen. Workaround: None
  • 250. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 250 Initial Load Process Does Not Support Cross-Database Pull Change Request: 12-1VJIM79 Product: Siebel 8.1.1.1 QF3103 The Initial Load process does not support cross-database (platform) data pull. Workaround: Have the same database type for Siebel and IIR. Installation Overview for ACR 475 The following section contains an overview of the different builds that you must install to be able to implement ACR 475. Installation Sequence for ACR 475 The installation sequence for ACR 475 for UCM 8.2 is as follows: Siebel 8.1.1. SIA + Siebel 8.1.1.4 Fix Pack. Zip Files for ACR 475 ■ The ACR437_UCM.zip file. This file is packaged with the Siebel 8.1.1.1 Fix Pack. ■ The ACR475A_UCM.zip, ACR475B_UCM.zip, ACR475B_UCM_1.zip, ACR475B_UCM_2.zip, ACR475B_UCM_3.zip, ACR475B_UCM_4.zip and ACR475B_UCM_5.zip files. The following is an overview of the installation process. 1 Install the Siebel Tools build and connect to the server database. 2 Navigate to the Siebel Tools installation directory <Tools Install Director>REPPATCH folder. 3 Unzip the ACR437_UCM.zip file from <Tools Install Directory>REPPATCH and configure ACR 437 using the instructions provided in the Siebel Maintenance Release Guide, Version 8.1.1.x. To access this guide, from within My Oracle Support, navigate to the Knowledge tab and search for Article ID 880452.1. 4 Unzip the ACR475A_UCM.zip file from <Tools Install Directory>REPPATCH and import the seed data for ACR 475A. For instructions, see “Configuration Instructions for ACR 475A” on page 251. 5 Complete the ACR 437 and ACR 475A setup, including applying the Base Tables and EIM Table schemas. CAUTION: It is important that you complete the entire setup for ACR 437 and ACR 475A before you make the repository changes for ACR 475B. 6 Unzip the ACR475B_UCM.zip and ACR475_UCM_1.zip files from <Tools Install Directory>REPPATCH and perform the required configuration changes. 7 Unzip the ACR475B_UCM_2.zip file from <Tools Install Directory>REPPATCH and perform the required configuration changes. 8 Unzip the ACR475B_UCM_3.zip file from <Tools Install Directory>REPPATCH and perform the required configuration changes. CAUTION: If you want to use DRM, do not unzip the UCM_3.zip file.
  • 251. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 251 9 Unzip the ACR475B_UCM_4.zip file from <Tools Install Directory>REPPATCH and perform the required configuration changes. 10 Unzip the ACR475B_UCM_5.zip file from <Tools Install Directory>REPPATCH and perform the required configuration changes. Configuration Instructions for ACR 475A Use the procedures in the following sections to install and configure ACR 475A. CAUTION: In order to implement ACR 475B, you must already have installed ACR 437 and ACR 475A. ACR 437 was included in the Siebel 8.1.1.1 Fix Pack. For information about how to install and configure ACR 437, see the Siebel 8.1.1.x Maintenance Release Guide on My Oracle Support. To access this guide, navigate to the Knowledge tab, and search for Article ID 880452.1. For information about how to install ACR 475A, see “Configuration Instructions for ACR 475A” on page 251. Configuration Instructions for ACR 475A The following section contains information about how to install and configure ACR 475A. NOTE: For more information about what functionality ACR 475A provides, see Oracle Universal Customer Master for Higher Education Constituent Hub Administration Guide on My Oracle Support. To access the guide, navigate to the Knowledge tab and search for Article ID 863982.1. This section includes information on how to set up and configure Oracle Higher Education Constituent Hub Web services. The following topic is included: “Process for Configuring Oracle Higher Education Constituent Hub Web Services” on page 251 Both the Match and Fetch Web service are set up with the following tasks. If you need to manually configure the Web services, see Article ID 763962.1 on My Oracle Support. Process for Configuring Oracle Higher Education Constituent Hub Web Services You must set up and configure the Web Services. To set up Oracle Higher Education Constituent Hub Web services for ACR 475A, perform the following tasks: ■ “Importing the SIF Files” on page 251 ■ “Compiling the SRF and Restarting the Siebel Server” on page 254 ■ “Importing Seed Data” on page 255 Importing the SIF Files This task is a step in “Process for Configuring Oracle Higher Education Constituent Hub Web Services” on page 251. SIF files contain Siebel object definitions that can be imported into Siebel Tools to replace existing definitions. Following successful application of ACR 475A, you will then locateand import the SIF files that came with the Quick Fix into Siebel Tools. This SIF file contains object definitions that are different from those contained in your present repository.
  • 252. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 252 To import the .sif files 1 Navigate to the Siebel Tools installation directory <Siebel Tools Install Directory>REPPATCH. 2 Unzip the .sif files from the ToolsACR475A_UCM.zip file. 3 Open the Sifs folder, and verify that the following .sif files are present: ■ Tables.sif NOTE: Be sure to import Tables.sif before EIMtables.sif. ■ Applets.sif ■ BusinessComponents.sif ■ BusinessObjects.sif ■ BusinessService.sif ■ EIMTables.sif ■ IntegrationObjects.sif ■ Links.sif ■ PickList.sif ■ Screen.sif NOTE: Before importing the SymbolicStrings.sif file, make sure the following parameter value is set in tools.cfg file: SymStrPrefix = SBL_. ■ SymbolicStrings.sif ■ Views.sif 4 After verifying that the .sif files are all present, log on to Siebel Tools. 5 Lock the following projects: ■ Contact ■ Symbolic Strings ■ Table CIF ■ Table Person ■ UCM CDM Child ■ UCM Data Management ■ UCM Higher Education ■ UCM SDH ■ VEAI UCM CIF ■ VEAI UCM CIF UI ■ Web Service Integration ■ EIM CIF
  • 253. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 253 ■ EIM Person ■ LOY Profiles TIP: Use the following query to get the list of projects to lock or unlock: {Contact or Symbolic Strings OR Table CIF OR Table Person OR UCM CDM Child OR UCM Data Management OR UCM Higher Education OR UCM SDH OR VEAI UCM CIF OR VEAI UCM CIF UI OR Web Service Integration OR EIM CIF OR EIM Person OR LOY Profiles}. 6 From the Tools menu, choose Import from Archive. 7 Import the first SIF file, using the Merge option. 8 Repeat Step 6 and Step 7 for the remaining SIF files. 9 In the Object Explorer, query for tables that have been modified, by using the Changed flag. 10 Make sure that the query returns the following values: ■ S_CONTACT ■ S_CONTACT_NAME ■ S_CONTACT_UCMX ■ S_CON_IDNTY_DOC ■ S_UCM_ADDR_PER ■ S_UCM_CONTACT ■ S_UCM_CON_CHILD ■ S_UCM_ORG_EXT ■ EIM_UCM_ADRPER ■ EIM_UCM_CON ■ EIM_UCM_CONCHLD ■ EIM_UCM_ORG ■ EIM_CONTACT3 11 Select a modified table, then click the Apply/DLL button. The Choose Option window appears. 12 Choose Apply, then click OK. A prompt appears requiring login credentials. 13 Enter the required information for your database, including the exact ODBC name for your database. 14 Click Apply. The modification process may take a moment. 15 Once the process is finished, click OK to finish the table schema changes.
  • 254. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 254 16 Repeat Step 11 through Step 15 until all required tables have been modified. TIP: You can apply the schema changes to all the tables in one pass by selecting the Current Query in the Tables drop-down in the Apply Schema window. To perform this you have to have executed a query with changed flag set. Compiling the SRF and Restarting the Siebel Server This task is a step in “Process for Configuring Oracle Higher Education Constituent Hub Web Services” on page 251. The Siebel repository: siebel_sia.srf is located at: <ServerInstallLocation>sessiebsrvrobjectsenusiebel_sia.srf. Compile the business object changes youmade in the preceding steps for the changes to take effect. To compile and restart the Siebel Server 1 Stop the Siebel Server. 2 In Siebel Tools, compile the following projects: ■ Contact ■ Symbolic Strings ■ Table CIF ■ Table Person ■ UCM CDM Child ■ UCM Data Management ■ UCM Higher Education ■ UCM SDH ■ VEAI UCM CIF ■ VEAI UCM CIF UI ■ Web Service Integration ■ EIM CIF ■ EIM Person ■ LOY Profiles 3 In the Object Explorer, navigate to integration objects. 4 Query for the Integration Objects that were imported from the .sif files. The following Integration Objects were modified for ACR 475A: ■ SwiPersonIO ■ SwiPersonPublishIO
  • 255. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 255 ■ CIFContact ■ CIFContactInsert ■ CIFContactInsertRs ■ CIFContactUpdate ■ CIFContactUpdateRs ■ CIFContactUpsert ■ CIFContactUpsertRs ■ UCMContactSourceDataAndHistory 5 For each of the Integration Objects that were imported, choose Undeploy from the right-click menu, then step off the record to retain changes. 6 From the right-click menu, choose Deploy to Runtime database. 7 Start the Siebel Server using the newly compiled SRF. Importing Seed Data This task is a step in “Process for Configuring Oracle Higher Education Constituent Hub Web Services” on page 251. To import seed data 1 From the Windows Start menu, select Control Panel, Administrative Tools, then Data Sources ODBC. 2 Click the System DSN tab. 3 Click Add, then choose the Siebel Oracle90 driver. 4 Enter a data source name, and the name of the server you will be connecting to. TIP: For an Oracle database, enter the TNS service name that you created to connect Siebel Tools to the Oracle database. 5 Navigate to <Tools Install Directory>REPPATCHACR475A. 6 Before executing the next step, make sure that the dataimp.exe file exists in the<Tools Install directory>bin directory. Importing Seed Data For ENU Implementations ENU implementations require you to import two .dat files which contain seed data. To import required .dat files 1 Run the following command to import the seed.dat file:
  • 256. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 256 <Tools Install Directory>bindataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>REPPATCHACR475A_UCMSeedDataACR475A_Seed.dat /l <Tools Install Directory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools Install Directory>REPPATCHACR475A_UCMSeedData<Database Platform>ACR475A_Seed.inp /e n /h log NOTE: The /e n switch enforces the dataimp process to only look at tables in the imp file. To track unique constraint violations, see the /h log file. ■ Replace Tools Install Directory with your Siebel Tools installation directory. ■ Replace ODBC Source Name with the ODBC you created in Step 3 of the “To import seed data” procedure. ■ Replace Database Platform with your database platform, (for example: Oracle, MSSQL, and so on). ■ Replace username with your database user Id. ■ Replace password with your database password. 2 Run the following command to import the ENU seed.dat file: <Tools Install Directory>bindataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>REPPATCHACR475A_UCMSeedDataENUACR475A_Seed_Locale_ENU.dat /l <Tools Install Directory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools Install Directory>REPPATCHACR475A_UCMSeedData<Database Platform>ACR475A_seed_locale_ENU.inp /e n /h log. ■ Replace Tools Install Directory with your Siebel Tools installation directory. ■ Replace ODBC Source Name with the ODBC you created in Step 3 of the “To import seed data” procedure. ■ Replace Database Platform with your database platform, (for example: Oracle, MSSQL, and so on). ■ Replace username with your database user ID. ■ Replace password with your database password. 3 Review the Siebel Tools Install Directory>tempdataimp_seed.log file to make sure that the import completed successfully. Importing Seed Data For Non-ENU Implementations Non-ENU implementations require you to import two .dat files: the base ENU seed.dat and the locale specific, seed_locale_XXX.dat, where XXX is the language code. To import required .dat files 1 Run the following command to import the seed.dat file:
  • 257. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 257 <Tools Install Directory>bindataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>REPPPATCHACR475A_UCMSeedDataENUACR475A_Seed_Locale_ENU.dat /l <Tools Install Directory>tempdataimp_Seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools Install Directory>REPPATCHACR475A_UCMSeedData<Database Platform>ACR475A_seed_LOCALE_ENU.inp /e n /h log NOTE: The /e n file enforces the dataimp process to only look at tables in the imp file. To track unique constraint violations, see the /h log file. ■ Replace Tools Install Directory with your Siebel Tools installation directory. ■ Replace ODBC Source Name with the ODBC you created in Step 3 of the “To import seed data” procedure. ■ Replace Database Platform with your database platform, (for example: Oracle, MSSQL, and so on). ■ Replace username with your database user Id. ■ Replace password with your database password. 2 Run the following command to import the seed_locale_XXX.dat file: <Tools Install Directory>bindataimp /u SADMIN /p sadmin /f <Tools Install Directory>REPATCHACR475A_UCMSeedData<LANG>ACR475A_seed_locale_xxx.dat /l <Tools Install Directory>tempdataimp_seed_lang.log /c <ODBC Source Name> /d <Table Owner> /e n /h log. ■ Replace Tools Install Directory with your Siebel Tools installation directory. ■ Replace ODBC Source Name with the ODBC you created in Step 3 of the “To import seed data” procedure. ■ Replace Database Platform with your database platform, (for example: Oracle, MSSQL, and so on). ■ Replace username with your database user Id. ■ Replace password with your database password. 3 Review the Siebel Tools Install Directory>tempSeed.log file to make sure that the import completed successfully. Configuration Instructions for ACR 475B NOTE: You must have installed the Siebel 8.1.1.1 Fix Pack, ACR 437, and ACR 475A before you can install ACR 475B. For information about how to install ACR 437, see Siebel Maintenance Release Guide Version 8.1.1.x on My Oracle Support. To access this guide, navigate to the Knowledge tab, and search for Article ID 880452.1. For information about how to install ACR 475A, see “Configuration Instructions for ACR 475A” on page 251. Importing the SIFs and Workflows in the ACR 475B_UCM.zip File Use the following procedure to import the SIFs and workflows packaged in the ACR 475B_UCM.zip file.
  • 258. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 258 To import the SIFs and workflows for ACR 475B 1 Verify that the Sifs folder within the ACR475B_UCM.zip file contains the following .sif files: ■ Applets.sif ■ Applications.sif ■ BusinessComponents.sif ■ BusinessObjects.sif ■ BusinessServices.sif ■ Classes.sif ■ Command.sif ■ Dlls.sif ■ EBCTable.sif ■ EIMTables.sif ■ IntegrationObjects.sif ■ Links.sif ■ Menu.sif ■ PickList.sif ■ Screens.sif ■ SymbolicStrings.sif ■ Tasks.sif ■ Tables.sif ■ Views ■ WebTemplates.sif ■ Workflows.sif NOTE: The Tables.sif file should be imported before you apply the EIM changes. Apply this table in merge mode. 2 Verify that the SIFs folder within the ACR475B_UCM_1.zip file contains the following .sif files: ■ BS_UCM_DataQualityManager.sif ■ WF_UCMBatchProcess.sif 3 Log into Siebel Tools, and lock the following projects: ■ Account ■ Account (SSE) ■ Account Hierarchy ■ Comm Manager
  • 259. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 259 ■ Common Components ■ Contact ■ DNB Data ■ DQ ISS Integration ■ DeDuplication ■ Household ■ LOY Profiles ■ Menu ■ Server Components - Object Manager ■ Siebel Workflows - Seed ■ Symbolic Strings ■ Table CIF ■ Table Organization ■ Table Party ■ Table Person ■ UCM CDM Child ■ UCM Data Management ■ UCM Hierarchy Management ■ UCM Higher Education ■ UCM Merge ■ UCM Privacy Management ■ UCM SDH ■ UCM Survivorship ■ UCM Task UI ■ UCM Unmerge ■ VEAI UCM Account ASI ■ VEAI UCM CIF ■ VEAI UCM CIF UI ■ VERT CUT Address
  • 260. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 260 ■ Web Service Integration Use the following query to get the list of projects to lock/unlock: { i."Table Organization" OR "Table Party" OR "Table Person" OR "UCM CDM Child" OR "UCM Data Management" OR "UCM Hierarchy Management" OR "UCM Higher Education"OR "UCM Merge" OR "UCM Privacy Management" OR "UCM SDH" OR "UCM Survivorship" OR "UCM Task UI" OR "UCM Unmerge" OR "VEAI UCM Account ASI" OR "VEAI UCM CIF" OR "VEAI UCM CIF UI" OR "VERT CUT Address" OR "Web Service Integration" ii."Account" OR "Account (SSE)" OR "Account Hierarchy" OR "Comm Manager" OR "Common Components" OR "Contact" OR "DNB Data" OR "DQ ISS Integration" OR "DeDuplication" OR "Household" OR "LOY Profiles" OR "Menu" OR "Server Components - Object Manager" OR "Siebel Workflows - Seed" OR "Symbolic Strings" OR "Table CIF"} 4 Before importing the SymbolicStrings.sif file, make sure that the SymStrPrefix=SBL parameter exists in the tools.cfg file. 5 Import all of the .sifs except EIMTables.sif to the server database using the merge mode. Import the .sifs from ACR475B_UCM.zip before you import the .sifs from ACR475B_UCM_1.zip. 6 Within Object Explorer, navigate to Tables, and query for tables that have changed by selecting the query with the Changed flag set. The query will give you the following list of tables: ■ S_ADDR_PER ■ S_CONTACT ■ S_CONTACT_NAME ■ S_CONTACT_UCMX ■ S_CON_ADDR ■ S_CON_IDNTY_DOC ■ S_DYN_HRCHY ■ S_DYN_HRCHY_REL ■ S_PARTY_REL ■ S_PARTY_UCMX ■ S_UCMIMPORT_TSK ■ S_UCMIMPTSK_ARG ■ S_UCMIMPTSK_LOG ■ S_UCMSRVTSK_MSG ■ S_UCM_ADDR_PER ■ S_UCM_ATGP_RULE ■ S_UCM_CONTACT
  • 261. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 261 ■ S_UCM_CON_CHILD ■ S_UCM_CON_DECAY ■ S_UCM_HRCHY ■ S_UCM_HRCHY_REL ■ S_UCM_IMPMP_ITM ■ S_UCM_IMPRT_MAP ■ S_UCM_MERGE_REQ ■ S_UCM_MRG_ASSOC ■ S_UCM_OGP_CHILD ■ S_UCM_ORGRP_MRG ■ S_UCM_ORG_CHILD ■ S_UCM_ORG_DECAY ■ S_UCM_ORG_EXT ■ S_UCM_RULE_SET ■ S_UCM_SRVR_TSK 7 With the query result, perform the following steps to extend the schema: a Click the Apply/DLL button. The Choose Option window displays. b Choose Apply and click OK. c In the window for login credentials and database information, enter the database administrator password. d From the Tables drop-down list, select Current Query. e For ODBC data source, enter the exact ODBC name of the database, and click Apply. f Wait until the process is finished and the tables are modified, and then click OK to finish the schema changes for the tables. 8 Within Object Explorer, navigate to Integration Objects. 9 On the right pane, query for the Integration Objects that changed during the sif file import. 10 Select all changed Integration Objects, right-click and select Undeploy, and then refresh. 11 Right-click and selct Deploy to deploy the changes to the runtime database. The server repository- siebel_sia.srf located in <ServerInstallLocation>sessiebsrvrobjectsenusiebel_sia.srf should be compiled for the changes in the above .sif files to take effect.
  • 262. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 262 Applying the EIM Changes in the ACR475B_UCM.zip File As part of the ACR475B release, EIM changes have been done on the database. The REPPATCHACR475B_UCMSifsEIMTables.sif file contains these changes. NOTE: Import the Tables.sif file before you proceed with the EIM changes. The EIMTables.sif file contains changes to the following existing tables: ■ EIM_ADDR_PER ■ EIM_CONTACT1 ■ EIM_ACCOUNT2 ■ EIM_ACCOUNT3 ■ EIM_CONTACT3 ■ EIM_UCM_CON ■ EIM_UCM_ORG ■ EIM_UCM_CONCHLD ■ EIM_UCM_ORGCHLD ■ EIM_UCM_OGPCHD ■ EIM_PTYUCM_DTL The EIMTables.sif file contains the following new EIM tables: ■ EIM_UCM_MRGREQ ■ EIM_UCM_ORGDCY ■ EIM_UCM_CONDCY ■ EIM_UCM_IMPTSK ■ EIM_UCM_SRVTSK ■ EIM_UCM_IMPMAP ■ EIM_UCM_HRCHY Use the following procedure to import the EIMTables.sif file into the repository. To import EIMTables.sif into the repository: 1 Lock the following projects: ■ EIM Organization ■ EIM Person ■ EIM CIF 2 Within Siebel Tools, use the Import from Archive function to read this file and create the tables in the repository. The "merge" option should be used while importing this file.
  • 263. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 263 To apply the EIMTables.sif file 1 Within Siebel Tools, query for the list of tables that were imported into the repository. 2 Use the "Apply/DDL" button to apply the changes to the physical database. 3 Unzip the ACR475B_UCM.zip file from <Tools Install Directory>REPPATCH. NOTE: If you have previously installed ACR 475B QFs, note that the ACR475B_UCM file has been replaced by the ACR475B_UCM_2.zip file. The unzipped ACR475B_UCM folder contains the following structure: ■ EIM_Files ■ Knowledgebases ■ Non-ENU Symbolic Strings ■ Schemas ■ SeedData ■ Sifs ■ WebServices_XML Updating the EIM Files As part of the ACR475B release, the EIM files - eim45.sql and eim_export_lookup_bu_name.sql have undergone a change. The REPPATCHACR475BRepositoryTableEIMeim45.sql and REPPATCHACR475BRepositoryTableEIMeim_export_lookup_bu_name.sql files have all of the changes required for the ACR and should replace the files in the following locations in the Siebel server directory: Eim45.sql: <Installation Location>SERVERsiebsrvrSQLTEMPL eim_export_lookup_bu_name.sql : <Installation Location>SERVERsiebsrvrADMIN To compile the SRF and restart the server Use the following procedure to compile the SRF and restart the server. 1 Stop the relevant server 2 Lock the projects that were newly added in this release. ■ UCM Merge Task UI ■ UCM List Import ■ UCM Data Decay Management ■ Table UCM DRM Integration ■ Table UCM Import ■ DqSync NOTE: If you have customized projects, lock these projects as well.
  • 264. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 264 3 Compile all of the locked projects. 4 Start the server using this newly-compiled srf. Use the following procedure to activate the workflows for ACR 475B. To activate the workflows for ACR 475B 1 Navigate to Site Map > Administration Business Process > Workflow Deployment. 2 In the Workflow Deployment screen, click the Active Workflow Process tab. 3 In the top Repository Workflow Processes applet, query for the workflows, select them, and click the Activate button. 4 In the bottom Active Workflow Processes applet, query for the workflows that you just activated and verify that the Activation Date/Time and Expiry Date/Time are valid. 5 Repeat Step 1 through Step 4 for the workflows listed below. NOTE: You can use the following query for query for all of the workflows: UCM*Batch Data Management Workflow OR UCM*Data Decay Process OR UCM Batch Process* OR UCM*SOAP Process OR UCM Import File Processing OR UCM Master List Import Process OR UCM Process Merge Request OR UCM SOAP Customer Profile Integration Process. The ISS workflows: ISS Delete Record Sync OR ISS Launch Pre*Sync OR ISS Launch Write Record Sync OR ISS Write Record Sync OR ISSGetOldCountry should only be activated if you want to use the xml sync server to sync records with the IIR Server. ■ UCM Account Batch Data Management Workflow ■ UCM Account Data Decay Process ■ UCM Batch Process - Single Step ■ UCM Batch Process ■ UCM Contact Batch Data Management Workflow ■ UCM Contact Data Decay Process ■ UCM Financial Asset Customer Profile Integration SOAP Process ■ UCM Group Customer Profile Integration SOAP Process ■ UCM Import File Processing ■ UCM Master List Import Process ■ UCM Organization Customer Profile Integration SOAP Process ■ UCM Organization Hierarchy Management Integration SOAP Process ■ UCM Person Customer Profile Integration SOAP Process ■ UCM Process Merge Request ■ UCM SOAP Customer Profile Integration Process
  • 265. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 265 Importing the SIF Files in the ACR475B_UCM_2.zip File Use the following procedure to import the ACR475B_UCM_2.zip file. (This file is packaged with the build.) CAUTION: You must import the Tables.sif file before you import the EIMTables.sif file. 1 Verify that the ACR475B_UCM_2.zip file contains the following SIF files: ■ Applets.sif ❏ Contact Personal Address Mvg Applet ❏ UCM Account Source Data and History List Applet ❏ UCM Contact Source Data and History List Applet ❏ UCM HE Constituent Address Source Data and History List Applet ■ BusinessComponents.sif ❏ Account ❏ Contact ❏ UCM Account Source Data and History ❏ UCM Contact Source Data and History ■ BusinessObjects.sif ❏ Merged Account ❏ Merged Contact ■ BusinessServices.sif ❏ DQ Sync Services ❏ ISS System Services ❏ UCM Data Quality Manager ❏ UCM Merge Service ❏ UCM Source Data and History Service ■ EIMTables.sif ❏ EIM_UCM_ADRPER ❏ EIM_UCM_ASSET ❏ EIM_UCM_CON ❏ EIM_UCM_HRCHY ❏ EIM_UCM_ORG ❏ EIM_UCM_ORGGRP ■ IntegrationObjects.sif ❏ CIFContact ❏ SwiOrganizationMatchInputIO
  • 266. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 266 ❏ SwiOrganizationMatchOutputIO ❏ SwiPersonMatchInputIO ❏ SwiPersonMatchOutputIO ❏ SyncAccount ❏ SyncContact ❏ SyncProspect ❏ UCMAccountSourceDataAndHistory ❏ UCMAccountTaskUIMerge ❏ UCMContactSourceDataAndHistory ❏ UCMContactTaskUIMerge ■ Tables.sif ❏ S_UCM_ADDR_PER ❏ S_UCM_ASSET ❏ S_UCM_CONTACT ❏ S_UCM_ORGGRP ❏ S_UCM_HRCHY ❏ S_UCM_HRCHY_REL ❏ S_UCM_ORG_EXT ■ Views.sif ❏ UCM Account UnMerge View ❏ UCM Contact UnMerge View ■ Workflows.sif ❏ UCM Account Batch Data Management ❏ UCM Batch Process ❏ UCM Batch Process - Single Step ❏ UCM Contact Batch Data Management ❏ UCM Process Merge Request 2 Log into Siebel Tools, and lock the following projects: ■ Account ■ Contact ■ DQ ISS Integration ■ EIM CIF ■ Employee
  • 267. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 267 ■ Siebel Workflows - Seed ■ Table CIF ■ Table UCM DRM Integration ■ UCM Data Management ■ UCM Higher Education ■ UCM Merge Task UI ■ UCM SDH ■ UCM Unmerge ■ VEAI UCM CIF ■ VEAI UCM CIF UI ■ Web Service Integration ■ UCM SDH ■ UCM Merge 3 Import the SIF files to the server database using the Merge mode. 4 In the Object Explorer, navigate to Integration Objects, and in the right pane, query for the Integration Objects that changed during the sif file import. 5 For each of the changed Integration Objects, right-click, select Undeploy, refresh, right-click again, and select Deploy to Runtime Database. Importing the SIF Files in the ACR475B_UCM_3.zip File The file ACR475B_UCM_3.zip file contains the following SIF files in the SIFs folder: ■ Applets.sif ■ Dynamic Hierarchy Admin List Applet ■ Screens.sif ■ CIF Administration Screen ■ Views.sif ■ DRM Web Client View ■ Hierarchy Selection View ■ UCM Hierarchy History Flat List View Use the following procedure to import the ACR475B_UCM_3.zip file. CAUTION: The ACR475B_UCM_3.zip file inactivates DRM. If you want to use DRM functionality, do not import the ACR475B_UCM_3 file.
  • 268. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 268 To import the ACR475B_UCM_3.zip file 1 Log into Siebel Tools, and lock the following projects: ■ Account Hierarchy ■ UCM Hierarchy Management ■ VEAI UCM CIF UI 2 Import all of the SIFs to the server database using the Merge option. 3 Stop the relevant server. 4 Lock the following projects: ■ Account Hierarchy ■ UCM Hierarchy Management ■ VEAI UCM CIF UI 5 Compile all of the locked projects. 6 Start the server using the newly-compiled SRF. If you have imported the SIF files from UCM_3.zip, and you want to use DRM, use the following procedure to revert the changes and to manually enable DRM. To manually enable Oracle Hyperion Data Relationship Management for Oracle Customer Hub 1 In the Siebel Tools Object Explorer, click View, and then query for the following views: ■ UCM Hierarchy History Flat List View ■ DRM Web Client View ■ Hierarchy Selection View 2 In the Properties window, change the Inactive value for each view from TRUE to FALSE. 3 In the Object Explorer, click Applet, then query for Dynamic Hierarchy Admin List Applet, and then change the following properties: a In the Object Explorer click Control, query for Advanced Hierarchy, and then in the Properties window, change the Inactive value from TRUE to FALSE. b In the Object Explorer, click Applet Web Template, click Applet Web Template Item, and query for Advanced Hierarchy. c In the Properties window, change the Inactive value from TRUE to FALSE for both the Base and Edit List Applet Web Templates. 4 In the Object Explorer, click Screen, and then query for CIF Administration Screen. 5 In the Object Explorer, click Screen View, query for UCM Hierarchy History Flat List View, and in the Properties window, change the Inactive value from TRUE to FALSE. 6 Compile the objects into the SRF, and restart the Siebel Server.
  • 269. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 269 Importing the SIF Files in the ACR475B_UCM_4.zip File Use the following procedure to import the ACR475B_UCM_4.zip file. To import the ACR475B_UCM_4.zip file 1 Verify that the following .sif files exist: Applets.sif ■ Alternate Phone MVG Applet ■ Communication Address MVG Applet ■ LOY Communication Email List Applet ■ LOY Communication Phone List Applet ■ UCM HE Communication Email Source Data and History List Applet ■ UCM HE Communication Phone Source Data and History List Applet ■ UCM HE Constituent Affiliation Source Data and History List Applet ■ UCM HE Constituent Name MVG Applet ■ UCM HE Constituent Source Data and History List Applet ■ UCM HE Personal Address Pick Applet BusinessComponents.sif ■ Contact ■ UCM HE Constituent Affiliation Source Data and History BusinessServices.sif ■ DQ Sync Services ■ UCM Utility Service IntegrationObjects.sif ■ CIFContact ■ CIFContactInsert ■ CIFContactInsertRs ■ CIFContactUpdate ■ CIFContactUpdateRs ■ CIFContactUpsert ■ CIFContactUpsertRs ■ SwiPersonIO ■ SwiPersonPublishIO
  • 270. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 270 ■ UCMContactSourceDataAndHistory Views.sif ■ Hierarchy Selection View WebTemplates.sif ■ View 50 50 50 Framed Workflows.sif ■ UCM Account Batch Data Management Workflow ■ UCM Contact Batch Data Management Workflow ■ UCM Financial Asset Customer Profile Integration SOAP Process ■ UCM Group Customer Profile Integration SOAP Process ■ UCM Organization Customer Profile Integration SOAP Process ■ UCM Organization Hierarchy Management Integration SOAP Process ■ UCM Person Customer Profile Integration SOAP Process ■ UCM Process Merge Request 2 Within Siebel Tools, lock the following projects: ■ Comm Manager ■ Contact ■ DQ ISS Integration ■ LOY Profiles ■ Siebel Workflows - Seed ■ UCM Data Decay Management ■ UCM Hierarchy Management ■ UCM Higher Education ■ UCM SDH ■ VEAI UCM CIF ■ Web Service Integration 3 Import all the SIFs to the server database using Merge mode. 4 Within Object Explorer, navigate to Integration Objects, and query for the integration objects that changed during the SIF file import. 5 For each of the changed integration objects, right-click, select Undeploy, select Refresh, right- click, and select Deploy to Runtime Database. The server repository- siebel_sia.srf located in <ServerInstallLocation>sessiebsrvrobjectsenusiebel_sia.srf needs to be compiled for the changes in the preceding .sif files to take effect.
  • 271. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 271 Use the following procedure to compile the server repository. To compile the server repository 1 Stop the relevant server. 2 Lock the projects that were modified in this release: ■ Comm Manager ■ Contact ■ DQ ISS Integration ■ LOY Profiles ■ Siebel Workflows - Seed ■ UCM Data Decay Management ■ UCM Hierarchy Management ■ UCM Higher Education ■ UCM SDH ■ VEAI UCM CIF ■ Web Service Integration 3 Compile all of the locked projects. Use the following procedure to deploy the UCM workflows. To deploy the UCM workflows 1 In Siebel Tools, select the changed workflows, set appropriate workflow process properties, and then click the Publish/Activate button. 2 In the Siebel application, navigate to Site Map > Administration - Business Process > Workflow Deployment, and query for the changed workflows in the Repository Workflow Processes applet. 3 Click the Activate button to activate workflows that have not already been activated. 4 Within the Active Workflow Processes applet, verify that the workflows are active. Importing the SIF Files in the ACR475B_UCM_5.zip File Use the following procedure to import the ACR475B_UCM_5.zip file. To import the ACR475B_UCM_5.zip file 1 Verify that the following .sif files exist: ■ Applets.sif ❏ UCM Account Address Source Data and History List Applet
  • 272. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 272 ❏ UCM Contact Address Source Data and History List Applet ❏ CIF Systems List Applet ■ BusinessServices.sif ❏ DataEnrichment ❏ UCM Data Quality Manager 2 Within Siebel Tools, lock the following projects: ■ DeDuplication ■ UCM Data Management ■ UCM SDH ■ VEAI UCM CIF UI 3 Import all the SIFs to the server database using Merge mode. The server repository- siebel_sia.srf located in <ServerInstallLocation>sessiebsrvrobjectsenusiebel_sia.srf needs to be compiled for the changes in the preceding .sif files to take effect. Use the following procedure to compile the server repository. To compile the server repository 1 Stop the relevant server. 2 Lock the following projects that were modified in this release: ■ DeDuplication ■ UCM Data Management ■ UCM SDH ■ VEAI UCM CIF UI 3 Compile all of the locked projects. Applying the Table Definition Use the following procedure to apply the table definition for the tables that were changed during the ACR475B_UCM_2.zip file import. To apply the table definition 1 In Object Explorer, navigate to Tables, and query for the tables that were changed. (Select the queries that have the Changed flag.) 2 With the query results, perform the following tasks to extend the schema: a Click the Apply/DLL button. The Choose Option dialog displays.
  • 273. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 273 b Choose Apply and click OK. The login credentials and database information dialog box appears. c Enter the dba password for login credentials. d In the Tables drop-down list, select Current Query. e ODBC data source, enter the ODBC name, and click Apply. f Wait until the process is finished and the tables are modified. g When the process has finished, click OK to complete the schema changes for the tables. Importing Non-ENU Symbolic Strings ■ For languages other than ENU, open the Non-ENUSymbolicStrings folder and import the non-enu symbolic strings to the database. NOTE: This folder exists in both the ACR475B_UCM.zip, ACR475B_UCM_4.zip, and ACR475B_UCM_5.zip files. These folders also include a document with instructions for importing non-ENU symbolic strings. ■ For the "Knowledgebases" and "Sifs" categories and feature-specific setup instructions, use the instructions in “Importing the SIFs and Workflows in the ACR 475B_UCM.zip File” on page 257 to bring the categories into the testing target database. Importing the Seed Data in the ACR475B_UCM_2.zip and ACR475B_UCM_5.zip Files NOTE: If you are an existing customer who has already installed QF3101, QF3102, or QF3103, you do still need to import the ACR475B_UCM_2.zip file, as this file contains necessary fixes. 1 Create an ODBC entry for the database where you plan to import the seed data. a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC), b Select the "Siebel Oracle90" driver (from Datadirect Technologies). c Enter a data source name (such as DevelopmentDB). d Enter the server name to connect to: ❏ For Oracle enter the TNS service name that you created to connect Siebel Tools to the database. e Test your connection and click OK when tested successfully. 2 In the command prompt, navigate to the directory where you installed Siebel ToolsBIN. NOTE: Make a note of the directory where the seed data is extracted to - [REPPATCHACR475B ACR475B_UCM_2SeedData ]. 3 Before you import ACR475B_Seed.dat, make sure that the dataimp.exe file exists in the <Tools Install Directory>/bin directory.
  • 274. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 274 4 Run the following command: <Tools Install Directorybin>dataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>REPPATCHACR475BACR475B_UCM_2SeedDataACR475B_Seed.dat /l <Tools Install Directory>tempdataimp_seed.log /c <ODBC Source Name> /d <Table Owner>/i <Tools Install Directory>REPPATCHACR475B ACR475B_UCM_2SeedDataACR475B_SeedInp_Files<Database Platform>ACR475B_Seed.inp /q -1 /w y /e n /t n /x R /n 100 /h log <Tools Install Directory> - Replace with the Siebel Tools install directory <ODBC Source Name> - Replace with ODBC name created in Step 1. <Database Platform> - Replace with the database platform (ORACLE, DB2UDB, or MSSQL) 5 Review the log file in <Tools Install Directory>tempdataimp_seed.log file to make sure that the import completed successfully. 6 Seed data import includes mono-language seed data import and language seed-data import. If you are an ENU (English Language) customer, do the following: a To import ACR475B_Seed_Locale_ENU.dat, run the following command after importing the ACR475B_Seed.dat file: <Tools Install Directory>bindataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>REPPATCHACR475BACR475B_UCM_2SeedDataACR475B_Seed_Locale_ENU. dat /l <Tools Install directory>tempdataimp_seed_locale_ENU.log /c <ODBC Source Name> /d <Table Owner> /i Owner>/i <Tools Install Directory>REPPATCHACR475BACR475B_UCM_2SeedDataACR475B_SeedInp_Files<Da tabase Platform>ACR475B_seed_locale_ENU.inp /q -1 /w n /e y /t n /x R /n 100 /h log <Tools Install Directory> - Replace with the Siebel Tools install directory <ODBC Source Name> - Replace with the ODBC name created in Step 1. <Database Platform> - Replace with Database Platform (ORACLE, DB2UDB, or MSSQL) b To import seed_locale_XXX.dat for languages other than ENU, run the following command after importing ACR475B_Seed.dat file for importing the locale specific seed_locale_XXX.dat, where XXX is the language code. <Tools Install Directory>bindataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>REPPATCHACR475BACR475B_UCM_2SeedDataACR475B_NON_ENU_Seed_Lo caleseed_locale_XXX.dat /l <Tools Install directory>tempdataimp_seed_locale_XXX1.log /c <ODBC Source Name> /d <Table Owner> /q -1 /w n /e y /t n /x R /n 100 /h log <Tools Install Directory> - Replace with the Siebel Tools install directory <ODBC Source Name> - Replace with ODBC name created in Step 1. c Run the following command for additional seed_locale_XXX.dat in the ACR475B_UCM_5.zip, extracted to REPPATCHACR475BACR475B_UCM_5SeedData, where XXX is the language code: <Tools Install Directory>bindataimp /u <USERNAME> /p <PASSWORD> /f <Tools Install Directory>REPPATCHACR475BACR475B_UCM_5SeedDataACR475B_NON_ENU_Seed_Lo caleseed_locale_XXX.dat /l <Tools Install directory>tempdataimp_seed_locale_XXX2.log /c <ODBC Source Name> /d <Table Owner> /q -1 /w n /e y /t n /x R /n 100 /h log
  • 275. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 275 7 Review the log file in <Tools Install Directory>temp to make sure that the import completed successfully. Schemas and WebServices_XML The ACR475B_UCM.zip, ACR475B_UCM_1.zip, and ACR475B_UCM_4.zip files contain schemas. Use the later version in case of conflicts. Copying ISS DLLs Use the following procedure to unzip ISSdlls, which contains the ISS DLLs for all platforms. The ISS connector DLLs are available within the bin folder within the IIR Installation folder. To unzip ISSdlls 1 Select the respective dll for the platform required. The dlls modified are ssadqsea.dll, ssadqasm.dll and ssasec.dll. 2 Place these in the bin or lib folder under the Siebel Server installation directory, depending upon the platform chosen. These files contain the session pooling fix to be used in ISS 2.8.7. NOTE: You can also pick up these DLLs from the IIR Server (located in the bin folder if IIR is running on the same OS. Installing Siebel Haley You must install Siebel Haley before you install and activate knowledgebases and any rule-related tasks. Importing Knowledgebases In the Knowledgebases folder provided in ACR475B_UCM.zip, you must bring the ucmdatadecay.xml and ucmsurvivorshiprules.xml files into the target database to test Survivorship and Decay rules. Use the following procedure to import knowledgebases for ACR 475B. To import knowledgebases for ACR 475B 1 Navigate to Administration - Business Rules > Business Rule Knowledge Base. 2 Select Import Knowledge Base from the menu and and navigate to REPPATCHACR475B_UCMKnowledgebases to access the ucmdatadecay.xml and ucmsurvivorshiprules.xml files, and import them. 3 Once the import is done, click the Activate button. NOTE: The Activate button is no longer active after the import has completed.
  • 276. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 276 Compiling the SRF File The server repository- siebel_sia.srf file located in <ServerInstallLocation>sessiebsrvrobjectsenusiebel_sia.srf should be compiled for the changes in the preceding SIF files to take effect. Use the following procedure to compile the server repository. To compile the server repository 1 Stop the relevant server. 2 Lock the projects that were modified in this release: ■ Account ■ Contact ■ DQ ISS Integration ■ EIM CIF ■ Employee ■ Table CIF ■ Table UCM DRM Integration ■ UCM Data Management ■ UCM Higher Education ■ UCM Merge Task UI ■ UCM SDH ■ UCM Unmerge ■ VEAI UCM CIF ■ VEAI UCM CIF UI ■ Web Service Integration ■ UCM SDH ■ UCM Merge 3 Compile all of the locked projects. Configuring the UCM Batch Process Server Component for Single Threading Use the following procedure to compile the server components and start the server. NOTE: You must stop and restart both the Siebel Server and the Gateway Server for the changes in the following procedure to take effect. Execute the commands in the following procedure for the UCMBatchProcess component to run in single-threaded mode. Make sure that there are no errors when you execute the following procedure.
  • 277. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 277 To configure the server component and start the server 1 While the server is stopped, execute the following srvrmgr utility and connect to the gateway but not to the server. Run srvrmgr as: srvrmgr /g <Gateway> /e <Enterprisename> /u <UserName> /p <Password> 2 Execute the following commands for UCMBatchProcess component to run in single-threaded mode. Make sure that there are no errors when executing the following sequence of steps. ■ srvrmgr> reconfig compdef UCMBatchProcess ■ srvrmgr> change param Threaded=true for compdef UCMBatchProcess ■ srvrmgr> commit reconfig compdef UCMBatchProcess 3 Start the server using the newly-compiled SRF. Deploying the UCM Batch Process Workflow Use the following procedure to deploy the UCM Batch Process workflow. To deploy the UCM Batch Process workflow 1 In Siebel Tools, select the changed workflows, and click the Publish/Activate button. 2 Within the Siebel application, navigate to Site Map > Administration - Business Process > Workflow Deployment. 3 In the Repository Workflow Processes applet, query for UCM Batch Process and UCM Process Merge Request. 4 If the workflows are not already activated, click the Activate button. 5 In the Active Workflow Processes applet, verify that the workflows are active. Configuring Data Decay Runtime Events You must manually configure the seed data to enable the Data Decay runtime events. NOTE: These action sets are disabled by default, so you must enable them. Do not use quotes when you query for the action sets. 1 Navigate to Site Map > Administration - Runtime Events > Events, and query for Action Set Name=*Decay*. 2 For the events with Action Set Name=”UCM Account Decay New Record” OR “UCM Account Decay Update Record”, change the Conditional Expression value to: GetProfileAttr(‘UCMDecayFieldUpdated:Account’)=”Y”. 3 For the events with Action Set Name=”UCM Contact Decay Record” OR “UCM Contact Decay Update Record”, change the Conditional Expression value to: “GetProfileAttr(‘UCMDecayFieldUpdated:Contact’)=”Y”.
  • 278. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 278 Configuring NetChart Server Chart server needs to be installed from any release location with default settings—it is usually in Server_AncillaryVisual_Mining_Netcharts_Server. Use the following procedure to configure NetChart Server 4.6 Siebel Edition. Use the following procedure to configure NetChart Server. To configure NetChart Server 4.6 Siebel Edition 1 Create a folder called "Siebel.chart" under the C:Program FilesVisual MiningNetCharts Server 4.6 Siebel EditionServerrootprojects directory. Note that there needs to be a dot between Siebel and chart. 2 Copy over the Siebel.cdx file into the directory created in Step 1. 3 In ucm.cfg used by the Siebel Developer Web Client, under the specific datasource that you use to connect to DB, add the following lines:. ChartServer = localhost:8001 ChartImageFormat = png Localhost is the name of the machine that is running chart server and 8001 is the port number of chart server. 4 Navigate to Administration - Server Configuration > Profile Configuration, query for Alias as ServerDataSrc, and change the DSChartServer and DSChartImageFormat parameters. 5 Start NetCharts Server 4.6 Siebel Edition from Control Panel > Services. 6 In Windows Explorer, navigate to your installation directory for Siebel Charts (such as D:Program FilesVisual MiningNetCharts Server 4.6 Siebel EditionServerrootprojects). 7 Create a new subdirectory called Siebel.chart. 8 Within the new Siebel.chart subdirectory, create a new file, using Windows Notepad, and type the following three characters in uppercase but without a paragraph return: CDL 9 Save the file as Siebel.cdx. 10 Make sure that the DefaultChartFont parameter in your configuration file and theApplication Default Chart parameter for your Application Object Manager component are set to a font that is available on your machine. Configuring Survivorship to Use Haley Knowledgebase Use the following procedure to configure survivorship to use Haley for rules evaluation. To configure survivorship engine to use Haley for rules evaluation 1 Navigate to Administration - Universal Customer Master > Survivorship Rules.
  • 279. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 279 2 Configure the Comparison Rule to "External", select "Business Rule Service" for "Business Service Name", "RunRules" for "Business Service Method", and then select the individual "Rule Module Name" for each testing purpose. Use the following procedure to test task-based UI for merge. Activating Tasks for the Task-Based UI Use the following procedure to activate tasks to test the task-based UI for merge. To activate tasks to test the task-based UI for merge 1 Navigate to Administration- Business Process > Task Deployment >Active Tasks. 2 In the Published Tasks applet, query for 'UCM*'. 3 Activate all four of the UCM MergeTasks returned: UCM Merge Account Task; UCM Merge Contact Task; UCM Merge Account Request Task; UCM Merge Contact Request Task. 4 Restart the Siebel Server. Enabling Data Quality in SOAP Workflows Use the following procedure to enable Data Quality in SOAP workflows. 1 Within Siebel Tools, navigate to Workflow Process, and query for the UCM Organization Customer Profile Integration SOAP Process. 2 Select the workflow and then select Revise from the Workflow/Task Editor toolbar. 3 Set the workflow properties as follows: ■ Turn On CDM Cleans = true ■ Turn On CDM Exact Match = true ■ Turn On CDM Match = true ■ Turn On Survivorship = true 4 Navigate to the Workflow list view and select Publish/Activate from the Workflow/Task Editor toolbar. 5 Repeat Step 1 through Step 4 for the UCM Person Customer Profile Integration SOAP Process. Configuring Data Quality 1 Install IIR 2.8.07. using the instructions provided in the IIR Installation guide ( IS_2807_IIR_02_Installation.pdf) provided with the installer for completing this activity. There is a single installer for both ISS and ASM, so make sure that you have the license for both.
  • 280. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 280 2 Apply the hot fixes on top of thebase installer. After the patch installation, check the IIR Version. It should be on Patch level 141 or higher. You can verify using the command "version" command for Windows. For other platforms, use $SABIN/cevers. Example: C:InformaticaIRbin>version SSA-NAME3 v2.8.07 (FixL106) SSA-NAME3 Extensions v2.8.07 (FixL106) Data Clustering Engine v2.8.07 (FixL106) Informatica Identity Resolution v2.8.07 (FixL106 + FixL113 + FixL114 + FixL120 + FixL123 + FixL124 + FixL125 + FixL126 + FixL127 + FixL134 + FixL136 + FixL140 + FixL141) 3 Place the configuration files required for both matching and cleansing in the SDQConnector folders on Siebel Server. ssadq_cfg.xml ssadq_cfgasm.xml 4 Make sure that the country files and the key files exist in the location where ASM is installed. If any one of the country files is missing, ASM will not perform cleansing for that country. The location of these files will be: <drive>InformaticaIRssaasadaddb. NOTE: If AD5 is used, the location of the country database files and key file would be <drive>InformaticaIRssaasad5addb. Configuring ASM for Data Cleansing Use the following procedure to configure ASM for data cleansing. To configure ASM 1 Navigate to Administration - Server Configuration > Enterprise Explorer. 2 In the Explorer view, navigate to Component Definitions > Data Quality Manager > Parameters. 3 Within the Parameters list applet, query to verify the state of the following parameters. ■ Data Cleansing Enable Flag: True ■ Data Cleansing Type: ASM 4 Navigate to Administration - Server Configuration > Enterprise Explorer. 5 In the Explorer view, navigate to Component Definitions > Application Object Manager > Call Center Object Manager (ENU) > Parameters. NOTE: You can replace the Call Center Object Manager with another Object Manager, depending upon the application that you are running.
  • 281. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 281 6 Within the Parameters list applet, query to verify the state of following parameters: ■ Data Cleansing Enable Flag: True ■ Data Cleansing Type: ASM Use the following procedure to set client-level settings. To set client-level settings 1 Use any text editor to open uagent.cfg for the Siebel Call Center application, and ucm.cfg for UCM located in the siebsrver/BIN/<LANG> directory. 2 Within the cfg file, change the Enable parameter to TRUE ■ [DataCleansing] ■ Enable = TRUE ■ Type = ASM 3 Save the file and then launch the Call Center application 4 Navigate to Administration - Data Quality > Data Quality Settings, and verify that Enable DataCleansing is set to Yes. 5 Navigate to User Preferences > Data Quality, and verify that Enable DataCleansing is set to Yes. If the entries are blank, do not change anything. 6 Navigate to <Navigation> and verify if a vendor named ASM with the DLL namessadqasm exists. If this field does not exist, then create it, using the information in “Field Mappings for ASM.” Field Mappings for ASM Make sure that the following vendor mappings are set for ASM. NOTE: The mappings are imported as part of seed data import. Account Business Component Contact Business Component Business Component Field Mapped Field Name Account.Name Business Component Field Mapped Field First Name Contact.First Name Last Name Contact.Last Name Middle Name Contact.Middle Name
  • 282. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 282 List Mgmt Prospective Contact Business Component CUT Address Business Component Personal Address Business Component Business Component Field Mapped Field First Name List Mgmt Prospective Contact.First Name Job Title List Mgmt Prospective Contact.Job Title Last Name List Mgmt Prospective Contact.Last Name Middle Name List Mgmt Prospective Contact.Middle Name Business Component Field Mapped Field City Business Address.City Country Business Address.Country Postal Code Business Address.Postal Code State Business Address.State Street Address Business Address.Street Address Street Address 2 Business Address.Street Address 2 Business Component Field Mapped Field City Business Address.City Country Business Address.Country Postal Code Business Address.Postal Code State Business Address.State Street Address Business Address.Street Address Street Address 2 Business Address.Street Address 2
  • 283. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 283 Vendor Parameter NOTE: The ASM High Deliverability Return Code parameter is optional and applies only if the value for the DQ Cleanse High Deliverable Address parameter is set to Yes. Please set the values based on the requirements. The ssadq_cfgasm.xml file mentioned above in Vendor Parameter needs to be placed in the SDQ Connector folder where the Siebel application is installed. <?xml version="1.0" encoding="UTF-8"?> <Data> <Parameter> <iss_host>HostName</iss_host> </Parameter> <Parameter> <iss_port>1666</iss_port> </Parameter> <Parameter> <datacleanse_mapping> <mapping> <field>BC Field</field> <ssafield>ASM Field</ssafield> <std_operation>Operation</std_operation> Name Value Account DataCleanse Record Type Account Contact DataCleanse Record Type Contact List Mgmt Prospective Contact DataCleanse Record Type Prospect Personal Address DataCleanse Record Type Business Address CUT Address DataCleanse Record Type Business Address DQ Send Empty Field To Third Party Vendor Yes DQ Cleanse High Deliverable Address No Parameter 1 "global", "iss-config-file", "ssadq_cfgasm.xml" ASM Country Database Return Code 16,17,18,32,33 ASM High Deliverability Return Code 0,1,2
  • 284. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 284 </mapping> </datacleanse_mapping> </parameter> </data> The <field> tag mentioned above represents Siebel Fields. <ssafield> represents fields used by ASM. The fields used by ASM can only be the ones from the following table: Data_Types and Standardization_Operations supported by the connector are: Data_Type Meaning Organization Organization Name Department Department Name Nobility (e.g. Lord) Title (e.g. Mr, Dr) FName MName LName Function (e.g. Manager) Building SubBuilding HouseNumber Street1 Street2 POBox DepLocality (e.g. URB, Colonia) Locality (e.g. County) Province (e.g. State) Zip Zip / Postal Code Country Std_Op Meaning Upper Convert text to upper case Lower Convert text to lower case Camel Convert text to camel case (first letter is upper-cased, remainder are lower-cased)
  • 285. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 285 The connector is not able to cleanse any other field types. Money, Date and other types of data will remain unchanged if they are passed to the connector. The Country database used for ASM can be obtained from Technical Support. See the Siebel Data Quality Administration Guide for information about the sample XML file. Additional Seed Data Changes for ASM 1 If you are using ASM as the third-party vendor for data cleansing, then add UNITED STATES in the COUNTRY List of Values using the following steps: a Navigate to Site Map > Administration - Data > LOV Explorer. b Query for List of Values - Type: "COUNTRY". c In the LOV Explorer panel, click on the + sign to expand the node and navigate to the values for COUNTRY. d Add a new entry for 'UNITED STATES'. 2 Add 'DQ Cleanse High Delivery Address' in ASM - Vendor Parameter. The "DQ Cleanse High Delivery Address" vendor parameter is optional. If you want to revert back to the old address and do not want to cleanse if deliverability is low, set the parameter to "Yes". By default, the value is "No". This feature may only be required if the Country Database files provided by Informatica are not the updated ones. Additional Seed Data Changes for ISS 1 Change DLL Name for ISS as follows: a Navigate to Site Map > Administration - Data Quality > Third Party Administration. b In the Vendor applet, select ISS, and change the DLL Name value to ssadqsea. 2 If you are using UCM Batch Process and ISS as the third-party data quality vendor, you need to change the BC field mappings for the Contact - DeDuplication business component: a Navigate to Site Map > Administration - Data Quality > Third Party Administration b In the Vendor applet, select ISS. c In BC Vendor Field Mapping, select Contact - Deduplication. d In the Field Mappings applet, make the following changes: ❏ Change the name of the Primary Street Address field to Primary Personal Street Address. ❏ Change the name of the Primary City field to Primary Personal City ❏ Change the name of the Primary State field to Primary Personal State. ❏ Change the name of the Primary Postal Code field to Primary Personal Postal Code. ❏ Change the name of the Primary Country field to Primary Personal Country.
  • 286. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 286 Configuring ISS for Deduplication The following sections contain information about how to configure ISS for deduplication. Configuring the Siebel Application for the ISS Synchronizer Process You must perform the following procedure if you want to use the DQ-ISS synchronizer process to bypass XML Sync Server to insert records directly into the NSA table. To configure the DQ-ISS Synchronizer Process 1 Navigate to Site Map > Administration - Data Quality > Data Quality Settings. 2 Add a new entry called Enable DQ Sync, and set the value for this property to Yes. 3 Use the following steps to activate the DQ Sync action sets: a Navigate to Site Map > Administration - Runtime Events > Action Sets. b Query for the DQ Sync action sets, and click on the Active field to activate them. c Click the Menu button on the Action Sets applet, and select Reload Runtime Events to reload the runtime events. If you customize the SDF file, you must make sure that the value in the Record Length user property matches the value for the Total Field Length user property in the new SDF file. For more information, see Data Quality Guide for Oracle Customer Hub. To access this guide, within My Oracle Support, navigate to the Knowledge tab and search for Article ID 1282393.1. Configuring the EBC Table (for Data Sync) Use the following procedure to configure the data source definition required to synchronize data between the Siebel application and IIR. To configure the data source definition 1 Navigate to Administration - Server Configuration > Enterprises > Profile Configuration. 2 Copy an existing InfraDatasources named subsystem type. 3 Change the Profile and Alias properties to the Data Source name configured in Siebel Tools (ISSDataSrc). 4 Update the profile parameters to correspond to the external RDBMS: ■ DSConnectString = data source connect string ❏ For the Microsoft SQL Server or the IBM DB2 databases, create an ODBC or equivalent connection and input the name of this in the parameter. ❏ For an Oracle RDBMS, this value should specify the TNS name associated with the database and not an ODBC or other entry. ■ DSSQLStyle = database SQL type (Click Advanced to see this parameter.) ■ DSDLLName = DLL Name corresponding to the SQL type
  • 287. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 287 ■ DSTableOwner = data source table owner (Click Advanced to see this parameter.) ■ DSUsername = default user name used for connections ■ DSPassword = default password used for connections Configuring Object Managers for ISS Data Source (for Data Sync) Use the following procedure to configure Object Managers for ISS Data Source. To configure Object Managers for ISS Data Source 1 Navigate to Administration - Server Configuration > Enterprises > Component Definitions. 2 Query for the components used with UCM (such as UCM, DQ, EAI, and Workflow components). 3 Select a component, and then select Start Reconfiguration from the main menu. 4 In the lower applet, query for the OM - Named Data Source parameter. NOTE: The value for this parameter is similiar to “ServerDataSrc,GatewayDataSrc”. 5 Add a comma after the lastdata source, and add the ISS data source created in the “To configure the data source definition” procedure. The default name is ISSDataSrc. 6 Save the record and select Commit Reconfiguration from the main menu. 7 Repeat Step 3 through Step 7 for all required Object Managers. 8 Click Synchronize to save the changes into the Gateway configuration file. 9 Bounce the Gateway Server and the Siebel Server. Configuring Deduplication for Multiple Addresses Use the following procedure if you want to use matching with multiple addresses instead of with the primary address. To configure deduplication for multiple addresses 1 Navigate to Site Map > Administration - Data Quality > Data Quality Settings. 2 Add a new entry called Enable DQ Multiple Addresses and set the value for this property to Yes. 3 Add a new entry called Account Match Against and set the value for this property to All Address. 4 Add a new entry called Contact Match Against and set the value for this property to All Address. For more information about configuring multiple addresses, see the Configuring Deduplication Against Multiple Addresses section in the Data Quality Guide for Oracle Customer Hub (UCM) To access this guide, within My Oracle Support, navigate to the Knowledge tab and search for Article ID 1282393.1.
  • 288. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 288 Configuring Support for Multiple Languages Use the following procedure if you want to use matching with multiple languages using different population files. To configure multiple-language support 1 Navigate to Site Map > Administration - Data Quality > Data Quality Settings. 2 Add a new entry called Enable DQ Multiple Languages and set the value for this property to Yes. 3 Navigate to Site Map > Administration - Data Quality > Third Party Administration, select ISS in the Vendor applet, click on Vendor Parameter in the child applet, and do the following: a Add a new entry called Append Account Record Type Field 1 and set the value for this property to Primary Account Country. b Add a new entry called Append Contact Record Type Field 1 and set the value for this property to Primary Personal Country. c Add a new entry called Batch Append Account Record Type Field 1 and set the value for this property to Primary Account Country. d Add a new entry called Batch Append Contact Record Type Field 1 and set the value for this property to Primary Personal Country. For more information about configuring support for multiple languages, see the Configuring Multiple Language Support section in the Data Quality Guide for Oracle Customer Hub (UCM). To access this guide, within My Oracle Support, navigate to the Knowledge tab and search for Article ID 1282393.1. Configuring List Import These are the new system preferences used in List Import: Enable Validation - [Optional step in the List Import Process] If this System Preference is turned on, the validation process will automatically be run after records are imported into UCM (SDH tables). The validation process will check if any required fields specify in the Import Mapping are missing in the imported records. Any records that fail validation will have their 'UCM Type Code' changed from 'Batch' to 'Incomplete' and the validation status will be inserted in the 'Error Message' field. Enable Launch BDM - [Optional step in the List Import Process] If this System Preference is turn on, the UCM Batch Process will automatically be run after records are imported into staging tables (SDH tables). This is an existing UCM process to move records in staging to base tables. Users can kick off the UCM Batch Process as a server task outside of List Import. Name Value UCM Import: Enable Validation True/False UCM Import: Enable Launch BDM True/False
  • 289. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 289 Configuring Import Field Mapping When creating the Import Mapping, the list of fields displayed in the popup dialog for user selection is configured in the Business Component User Prop for Accout/Contact SDH Business Component. sers can include additional fields that they want to support in these Business Component User Properties. The format for these Business Component User Properties is as follows: For example, in "UCM Account Source Data and History,” there are the following Business Component user properties: Configuring Additional Child Objects for Import Assume that users already configure additional SDH child objects, and they want to import these child objects along with the account/contact SDH parent record. These are the additional configuration steps for List Import: 1 In the child SDH Business Component, add a business component user prop: "Parent SDH Id Field Name", the value is the field that contains its parent SDH ID. 2 In the parent SDH Business Component, add the additional field mapping for the child object (see the example of field mapping configuration above). 3 In the "UCM Account Import" or "UCM Contact Import" Business Object, add the new child SDH Business Component and the corresponding link to the parent SDH Business Component. 4 In the “UCM File Manager Service" Business Service, add a new Business Service user property for the new child SDH buscomp. For example: ■ Account Import Staging Child Buscomp 1 => UCM Account Address Source Data and History ■ Account Import Staging Child Buscomp 2 => UCM Contact Source Data and History Installing Data Governance Management The following section contains information about how to install Data Governance Management (DGM). Name Value Map:[Object].[Field] [SDH buscomp Name].[Buscomp Field Name] Name Value Map:Account.Name UCM Account Source Data and History.Name Map:Address.City UCM Account Address Source Data and History.City Map:Contact.Job Title UCM Contact Source Data and History.Job Title
  • 290. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 290 Overview of DGM and Prerequisites Data Governance Management (DGM) tool is software built on Java technology, and Oracle ADF framework are introduced. This section describes how to install DGM. ■ OS System: DGM can only be run on the Windows platform. ■ DGM is a Java-based application. ■ Siebel UCM application: In this release of DGM, Siebel UCM is the only supported master hub. For information about how to install and configurethe Siebel application, refer to the Siebel UCM DGM web service document. ■ DGM source code: The installer will extract DGM source code and install package to a directory. Within this section, this directory will be referred to as <dgm_home>. Deployment of DGM application is a process of customizing the DGM system and then transferring it to the application server. You must preinstall and configure several software programs. Here is the guideline for the whole installation process. ■ Application Server Installation and Configuration: The Java application will run inside Java application server. In this section, Weblogic is the target application server. ■ ADF runtime Installation and Configuration: The DGM application uses functionality provided by the Oracle ADF framework, so the target Weblogic domain should have the ADF runtime extension installed. ■ DGM Configuration and Deployment: External environments parameters should be set correctly before DGM is deployed. After that, DGM can be deployed to Weblogic server. Required Software The following table describes the required software for DGM. Installing JDeveloper Use the following procedure to install JDeveloper. To install JDeveloper 1 Click Next within the Welcome screen to begin the installation. 2 Accept the default value as the middleware home directory. NOTE: Within this section, <mw_install_dir> will be used to represent the Middleware Home directory. Software Name Version Description JDK 1.6 Providing runtime for java application. Weblogic 10gR3 Java application server. ADF 11.1.1.54.7 Oracle framework for java application. ANT 1.6 A Java-based build tool.
  • 291. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 291 3 Select Complete Install. The Complete Installation will install Oracle JDeveloper Studio, the ADF Runtime, and WebLogic Server. 4 Confirm the product intstallation directories, and click Next to continue with the installation. 5 Select the Start Menu folder where you want to place your shortcuts. This step applies for the Windows platform only. 6 Display the installation summary info, and start the installation. 7 Select Run Quickstart to open the Quickstart window once the installation process has ended. Quickstart enables you to easily launch installed components and access online documentation. 8 Click Done to complete the installation. Creating the Weblogic Domain A weblogic domain should be created to accept the ADF-based DGM application. Use the following procedure to create the Weblogic domain. To create the Weblogic domain 1 Choose Configure Domains for Oracle ADF from the Quickstart window to display the Oracle Weblogic Configuration Wizard. 2 Select Create a New WebLogic Domain and click Next. 3 Select Generate a domain configured automatically to support the following products, select Oracle JRF - 11.1.1.0 [jdeveloper] and click Next. The option Base WebLogic Server Domain - 10.3.1.0 [wlserver_10.3]* is already selected. 4 Enter the name and location for the domain if the default values are not correct, and then click Next. 5 Enter the user name and password and click Next. 6 Select Production Mode in Weblogic Domain Startup Mode window, and click Next. 7 Click Next to ignore optional configuration. 8 Review the domain configuration, and click Create. 9 Click Done when the domain has been created. 10 Select User Projects < (domainName) > Start > All Programs > Oracle Fusion Middleware 11.1.1.1.0 > User Projects > base_domain > Start Admin Server for Weblogic Server Domain. 11 When the DOS window prompts for the username and password, enter userName and passWord if asked to do so. When the window displays message like "Server started in RUNNING mode", the Weblogic server has started up.
  • 292. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 292 Installing DGM Use the following procedure to install DGM. To install DGM 1 Navigate to Disk1install, and click setup.exe, and click Next. 2 Specify the home where DGM applications and source code will be installed, and click Next. 3 Choose Copy Application to copy the application and source code to home directory without deployment— otherwise, the DGM application will be deployed after file copy. If you choose Copy Application, go to Summary. Otherwise, go to the next step. 4 Browse to specify the JDK path. You can also use JDK installed with Oracle Middleware, which can be found within the Oracle/Middleware/JDK_1.x.xx folder. 5 Browse to specify the ant path. In a default Oracle Middleware installation, the ant path is found in the Oracle/Middleware/jdeveloper/ant folder. 6 Browse to specify the Weblogic 10gR3 installation path. You must select the root directory of WLserver installation. 7 Specify the Weblogic configurations according to your environment. 8 Specify the URL for Siebel server login, such as http://serverName:webPort/eai_enu/ start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute. 9 Specify the URL for Hierarchy Management, such as http://serverName:webPort/eai_enu/ start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute. 10 Specify the endpoint information of the DGM Web service according to your environment: For example, specify http://sdc60005qe:16662/eai_enu start.swe?SWEExtSource=WebService&amp;SWEExtCmd=Execute&amp;UserName=SADMIN&a mp;Password=MSSQL&amp; NOTE: The endpoint information will be kept in xml files, so escape '&' to '&amp;'. 11 Click Install to start the install process. 12 Click Exit to finish the installation. Entry Name Description host Weblogic server address port weblogic server listening port username password weblogic server credential target.server The default value is AdminServer
  • 293. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 293 Manually Installing or Redeploying DGM The src directory contains the source code for DGM application, and the build directory contains the script and configuration files you can use to manually deploy the DGM application. The install.cmd is the script for DGMinstallation. Edit the file, change the weblogic_home, jdk_home, ant_home according to your environment. DGM configurations are kept in <dgm_home>/build/deploy.properties. The configuration entries in this file are list in the following table. Entry Name Default Value Description dgm_web_service_end_point N/A This configuration MUST be changed to the endpoints of DGM web service siebel_login_url N/A This configuration MUST be changed to the url used for login into Siebel. govern_hier_url N/A The url of hierarchy explorer batch_preview_page_size 23 Specify how many records in a page when previewing imported batch. paginate_page_size paginate_cache_size 23 This configuration will specify how many records will be displayed in a page. #Note: For now, please keep the paginate_page_size and paginate_cache_size having same setting. batch_job_size 1000 When importing batch file, this configuration will specify how many records will be sent in a single request.
  • 294. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 294 After editing the install.cmd and deploy.properties according to your environment, open a dos window and run install.cmd to deploy the application. Accessing DGM Open browser, and access the following URL to visit DGM: cleanse_thresh_value cleanse_thresh_color 0.33,0.66,1.0 #d62800,#ffcf21,#84ae31 This configuration will specify the color for the healthy status of hub and source systems. cleanse_thresh_value are the threshhold values, and cleanse_thresh_color are colors used for representing different status. For example: cleanse_thresh_value=0. 33,0.66,1.0 cleanse_thresh_color=#d 62800,#ffcf21,#84ae31 When the healthy is below 33%(0.33), the node of corresponding system will be marked with color of #d62800; if healthy is between 33% and 66%, color of #ffcf21 is used; when above 66%, #84ae31 will be used. HubAccount SrcAccount HubContact SrcContact [name, location, mainPhoneNumber] [name, loc, mainPhoneNumber] [firstName, lastName] [firstName, lastName] The default fields combination used to query completeness info. min_date_format min_date_value MM/dd/yyyy HH:mm:ss 09/13/1990 00:00:00 When choosing the query criteria of "From" calendar selector, the oldest time users can specify. collectionsClassPath loggingClassPath com/oracle/mdm/view/collections.xml logging.properties These are the internally- used configurations. Do not modify them. Entry Name Default Value Description
  • 295. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 295 http://<ServerAddress>:<ServerPort>/dgm/ For example, navigate to http://130.35.79.111:7001/dgm/ NOTE: Java script and Active Control should be permitted to display the page. Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 476 This topic is part of “Configuration Instructions for Enhancements and Updates” on page 44. Use the instructions in this topic to implement ACR 476, which provides the new product Siebel Smart Answer Connector. For more information about the enhancements provided by ACR 476 for version 8.1.1.1 and later, see Siebel Smart Answer Connector Guide. This new guide is available on the Siebel 8.1 Bookshelf on OTN at http://www.oracle.com/technology/documentation/siebel.html. Updating Repository Objects for Siebel Smart Answer Connector To deploy Siebel Smart Answer Connector, you must update repository objects in Siebel Tools. To update repository object for Siebel Smart Answer Connector 1 Extract all archive files (*.sif) from SIEBEL_TOOLS_ROOT/REPPATCH/ACR476.zip into a temporary location. 2 Log in to Siebel Tools with administrator privileges. 3 Lock the following projects: ■ Smart Answer 8.x ■ Smart Answer ■ Banter eService ■ Service (SSV) ■ Symbolic Strings ■ eCatalog Admin ■ Email Response NOTE: If projects and objects are not locked when you import SIF files, a message appears indicating which object or project is to be locked. In such a case, lock the project or object, and then import the SIF file again. 4 Import the SIF files you extracted in Step 1 in the order shown below: ■ 01_sma_project.sif ■ 02_sma_classes.sif
  • 296. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 296 ■ 03_sma_dll.sif ■ 04_sma_bussvc.sif ■ 05_sma_io.sif ■ 06_sma_ss.sif ■ 07_sma_applets.sif ■ 08_sma_sct.sif ■ 09_sma_view.sif ■ 10_emr_bussvc.sif NOTE: SIF files are written in XML format. Their structure is a hierarchy of the objects archived, listing all of their properties and including any associated scripts: Repository, then Project, then Object, and then Child Objects. 5 Compile the changes into an updated repository file (SRF file). Copy the new SRF file to the Siebel Server installation, under SIEBSRVR_ROOTobjectsenu. 6 Start the Siebel Server (or servers) using the newly compiled SRF. For more information about starting Siebel Servers, see Siebel System Administration Guide. 7 Update the file SAConfig.xml by performing the following: a Navigate to the SIEBSRVR_ROOTsmartanswer directory, and then open the SAConfig.xml file with a text editor. b Replace the value for NLPAdapterDLLName with the correct location and filename. c Verify the value for the FacadeName property. The value depends on the third-party product you are using with Siebel Smart Answer. 8 Create a new smartanswer directory and subdirectories under the Siebel File System. a Make sure the File System location is correct, accessible, and writable. b In the smartanswer directory, create two subdirectories: import and export. For example, if you map your File System to fs, then the resulting directory structure is similar to that shown below. fs smartanswer export import Adding Seed Data for Siebel Smart Answer Connector To deploy Siebel Smart Answer Connector, you must add seed data for Siebel Smart Answer Connector. Seed data is required for product operation.
  • 297. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 297 To add seed data for Siebel Smart Answer Connector 1 Add a new LOV (List of Values) by doing the following: a Navigate to the Administration - Data screen, and then the List of Values view. b Click New, and then add the following values: ❏ Type = SEARCH_SMART_ANSWER ❏ Display Value = Smart Answer ❏ Language = English American 2 Add a new inbound Web service by doing the following: a Navigate to the Administration – Web Services screen, then the Inbound Web Services view. b Click New, and then add the following values: ❏ Namespace = http://siebel.com/asi/ ❏ Name = SmartAnswerService ❏ Status = Active ❏ Comment = Smart Answer Service 3 Add a service port to the newly created Inbound Web Service. a Navigate to the Administration – Web Services screen, then Inbound Web Services, and then the Service Ports view. b Click New, and then add the following values: ❏ Name = Default ❏ Type = Business Service ❏ Business Service/Business Process name = Smart Answer External Business Service ❏ Transport = HTTP ❏ Address = http://130.35.27.238/eai_enu/ start.swe?SWEExtSource=WebService&amp;SWEExtCmd=Execute&amp;UserName= USERNAME&amp;Password=PASSWORD where: USERNAME is a valid Siebel user name PASSWORD is the corresponding password. ❏ Binding = SOAP_RPC_LITERAL 4 Add operations for the newly created service port. a Navigate to the Administration – Web Services screen, Inbound Web Services, Service Ports, and then the Operations view.
  • 298. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 298 b Click New to create new operations using the values shown in the following table. Setting Up Siebel Email Response for Use with Siebel Smart Answer Connector To make the Siebel Smart Answer Connector functionality available for use in Siebel EmailResponse, you must set up the Siebel Email Response user interface. To set up Siebel Email Response for use with Siebel Smart Answer Connector 1 Verify the following DLLs are available in the SIEBSRVR_ROOTbin directory: ■ swcommfr.dll ■ sscommsv.dll ■ sscmclnt.dll ■ sscacabc.dll ■ swcacafr.dll 2 Extract all archive files (*.sif) from SIEBEL_TOOLS_ROOTREPPATCHEMRUI_New.zip into a temporary location. 3 Log in to Siebel Tools with administrator privileges. 4 Lock the following projects: ■ Mail Agent ■ Email Response 5 Import the SIF files you extracted in Step 2 on page 298 in the order shown below: ■ EMR_UI_Applets.sif ■ EMR_UI_BC.sif ■ EMR_UI_BO.sif ■ EMR_UI_BS.sif ■ EMR_UI_Class.sif ■ EMR_UI_Screen.sif ■ EMR_UI_View.sif Name Method Display Name Authentication Type Import Import None Export Export None Feedback Feedback None Lookup Lookup None RefreshKB Refresh None
  • 299. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 299 ■ EMR_UI_Webtemplate.sif NOTE: If projects and objects are not locked when you import SIF files, a message appears indicating which object or project is to be locked. In such a case, lock the project or object, and then import the SIF file again. 6 Compile the changes into an updated repository file (SRF file). Copy the new SRF file to the Siebel Server installation, under SIEBSRVR_ROOTobjectsenu. 7 Start the Siebel Server (or servers) using the newly compiled SRF. For more information about starting Siebel Servers, see Siebel System Administration Guide. 8 Import the following workflows: ■ Email Response - Analyze Message.xml ■ Email Response - Client Send Email.xml ■ Email Response - Create Activity.xml ■ Email Response - Process Message.xml ■ Email Response - Response Workflow.xml ■ Email Response - Send Auto Response.xml ■ Email Response - Set Parent Activity Status.xml For information about working with workflows, see Siebel Business Process Framework: Workflow Guide. 9 Activate the workflows you imported in Step 8 on page 299. 10 Add seed data by doing the following: a Launch the Siebel Developer Web Client with the /editseeddata command-line option. For more information about launching this client type, see the Siebel Installation Guide for the operating system you are using. b Navigate to the Administration - Application screen, and then Views. c Click New to create a new view and add the following values: ❏ View Name = Communication Detail View ❏ Description = Drill down View ❏ Default Local Access = Yes ❏ Responsibilities = Siebel Administrator, Call Center Administrator, Email Response Agent, Email Response Manager, and Call Center Manager Back to Configuration Instructions for Enhancements and Updates Instructions for ACR 480 The following sections contain information about how to work with the seed data provided with ACR 480.
  • 300. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 300 Views and Responsibilities The following procedure details how to add the views and responsiblities for ACR 480. To add views/responsibilities 1 Connect to the Siebel application with /editseeddata switch. 2 Navigate to Site Map > Administration Application > Views, and add the views and responsibilities listed in the following table: View Responsibility CS CG My High Level Planning List View Siebel Administrator, CG Key Account Manager CS CG My Team's High Level Planning List View Siebel Administrator, CG Key Account Manager CS CG All High Level Planning List View Siebel Administrator, CG Key Account Manager CS CG All Across Organizations High Level Planning List View Siebel Administrator CPG Plan High Level Planning View Siebel Administrator, CG Key Account Manager CPG Account High Level Planning View Siebel Administrator, CG Key Account Manager CPG Promotion List View Siebel Administrator, CG Key Account Manager CPG Promotion Literature List View Siebel Administrator, CG Key Account Manager CPG Promotion Product Performance View Siebel Administrator, CG Key Account Manager CS CG All Promotion List View Siebel Administrator, CG Key Account Manager CS CG Corporate Promotion Category List Admin View - SIS Siebel Administrator, CG Key Account Manager CS CG Promotion Literature List View Siebel Administrator, CG Key Account Manager CS CG Corporate Promotion Attachments View Siebel Administrator, CG Key Account Manager SIA CS Target Account View Siebel Administrator, CG Key Account Manager SIS CS Corporate Promotions Target View Siebel Administrator, CG Key Account Manager CS CG Deal Payment Approval View Siebel Administrator, CG Key Account Manager, Super User - SIS 7.7, Super User - SIS SIA CS ADL Authorized Category Product View Siebel Administrator, CG Key Account Manager SIA CS ADL Authorized Product View Siebel Administrator, CG Key Account Manager CG Account Merchandising Location Product View Siebel Administrator, CG Key Account Manager CS Fund Transfer Admin View Siebel Administrator, CG Key Account Manager
  • 301. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 301 Lists of Values The following section details how to add the LOVs provided in ACR 480. To add LOVs 1 Connect to the Siebel application. 2 Navigate to Site Map > Administration Data > List of Values Explorer (for List of Values Type) and List of Values (for LOV type values), and create or modify the following LOV Type/LOVs with Translate = Y for all the values: CS Plan Account Promotion Audit Trail View Siebel Administrator, CG Key Account Manager CS Plan Audit Trail View Siebel Administrator, CG Key Account Manager CS Visit Parent Account Promotions View Siebel Administrator, CG Key Account Manager CS Claim My Claims View Siebel Administrator, CG Key Account Manager CS Claim My Team's Claims View Siebel Administrator, CG Key Account Manager CS Claim All Claims View Siebel Administrator, CG Key Account Manager CS Claim All Across Orgs Claims View Siebel Administrator, CG Key Account Manager CS Claim Attachments View Siebel Administrator, CG Key Account Manager CS Claim Resolution View Siebel Administrator, CG Key Account Manager New or Needs Modification? LOV Type Code Display Value Language- Independent Code Comments New SVP Source Baseline PY Currency Baseline PY Currency Order = 7 New SVP Source Baseline PY Qty Baseline PY Cases Order = 8 New SVP Source Baseline Target Currency Baseline Target Currency Order = 9 New SVP Source Baseline Target Qty Baseline Target Cases Order = 10 Modify SVP Source Incremental Qty Baseline Incremental Cases Change Order = 11 Modify SVP Source Incremental Currency Baseline Incremental Currency Change Order = 12 View Responsibility
  • 302. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 302 Modify SVP Source Consumed Qty Consumption Consumed Cases Change Order = 13 Modify SVP Source Shipped Qty Shipments Shipped Cases Change Order = 14 Modify SVP Source Target Basis Currency Target Basis Currency Change Order = 15 Modify SVP Source Target Basis Qty Target Basis Cases Change Order = 16 Modify SVP Source Target Planning Currency Target Planning Currency Change Order = 17 Modify SVP Source Target Planning Qty Target Planning Cases Change Order = 18 Modify SVP Source Target Currency Target Baseline Currency Change Order = 19 Modify SVP Source Target Qty Target Baseline Cases Change Order = 20 New CAMP_EXEC_S TATUS In Progress In Progress Translate = Y New DISPLAY_LOC Shelf Shelf Order = 1 New DISPLAY_LOC Off-Shelf Off-Shelf Order = 2 New DISPLAY_LOC Secondary Secondary Order = 3 New DISPLAY_LOC End-of-Isle End-of-Isle Order = 4 New DISPLAY_LOC Checkout Checkout Order = 5 New DISPLAY_LOC Multiple Multiple Order = 6 New DISPLAY_SIZE Small Small Order = 1 New DISPLAY_SIZE Medium Medium Order = 2 New DISPLAY_SIZE Large Large Order = 3 New DISPLAY_TYPE Literature Literature Order = 1 New DISPLAY_TYPE Merchandise Merchandise Order = 2 New DISPLAY_TYPE Sweepstakes Sweepstakes Order = 3 New DISPLAY_TYPE Audio Audio Order = 4 New DISPLAY_TYPE Multi-Media Multi-Media Order = 5 New DISPLAY_TYPE Promoter Promoter Order = 6 New or Needs Modification? LOV Type Code Display Value Language- Independent Code Comments
  • 303. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 303 New ADV_LOC Premium Premium Order = 1 New ADV_LOC Secondary Secondary Order = 2 New ADV_LOC Tertiary Tertiary Order = 3 New ADV_SIZE Postage Stamp Postage Stamp Order = 1 New ADV_SIZE Quarter Page Quarter Page Order = 2 New ADV_SIZE Half Page Half Page Order = 3 New ADV_SIZE Full Page Full Page Order = 4 New ADV_SIZE Not Applicable Not Applicable Order = 5 New ADV_TYPE Flyer Flyer Order = 1 New ADV_TYPE Newspaper Newspaper Order = 2 New ADV_TYPE TV TV Order = 3 New ADV_TYPE Radio Radio Order = 4 New ADV_TYPE Direct Mail Direct Mail Order = 5 New ADV_TYPE Internet Internet Order = 6 New PRICE_REDUCT ION_SIZE Reduction Amount Reduction Amount Order = 1 New PRICE_REDUCT ION_SIZE Reduction % Reduction % Order = 2 New PRICE_REDUCT ION_SIZE Reduced Price Reduced Price Order = 3 New PRICE_ REDUCTION_T YPE TPR TPR Order = 1 New PRICE_ REDUCTION_T YPE Special Pack Special Pack Order = 2 New PRICE_ REDUCTION_T YPE BOGO BOGO Order = 3 New PRICE_ REDUCTION_T YPE EDLP/EDLC EDLP/EDLC Order = 4 New PRICE_ REDUCTION_T YPE Coupon Coupon Order = 5 New or Needs Modification? LOV Type Code Display Value Language- Independent Code Comments
  • 304. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 304 New FD_SLOTFEE_P AY_MTH Bill Back Bill Back Order = 1 New FD_SLOTFEE_P AY_MTH Deduction Deduction Order = 2 New FD_SLOTFEE_P AY_MTH Check Check Order = 3 New OTHER_FD_SP ND_PAY_MTH Bill Back Bill Back Order = 1 New OTHER_FD_SP ND_PAY_MTH Deduction Deduction Order = 2 New OTHER_FD_SP ND_PAY_MTH Check Check Order = 3 New SH_VAR_SPEN D_MTH Bill Back Bill Back Order = 1 New SH_VAR_SPEN D_MTH Deduction Deduction Order = 2 New SH_VAR_SPEN D_MTH Off-Invoice Off-Invoice Order = 3 New TACTICS_TYPE Display & TPR 10% Display & TPR 10% New TACTICS_TYPE Display & TPR 15% Display & TPR 15% New TACTICS_TYPE Display & TPR 5% Display & TPR 5% New TACTICS_TYPE F&D F&D New TACTICS_TYPE F&D 10% F&D 10% New TACTICS_TYPE F&D 15% F&D 15% New TACTICS_TYPE F&D 5% F&D 5% New TACTICS_TYPE Feature & TPR 10% Feature & TPR 10% New TACTICS_TYPE Feature & TPR 15% Feature & TPR 15% New TACTICS_TYPE Feature & TPR 5% Feature & TPR 5% New or Needs Modification? LOV Type Code Display Value Language- Independent Code Comments
  • 305. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 305 3 Click the Clear Cache button. State Model Use the following procedure to add State Models. To add State Models 1 Connect to the Siebel application. 2 Navigate to Site Map > Administration - Application > State Models. 3 Add the following new states for the CS Claim Status State Model: Closed, In Progress, Inactive, Open (Default), Resolved. 4 Add the transactions described in the following tables for the CS Claim Status State Model: 5 Add new states for the State Models in the following table: Modify PAYMENT_MET HOD_CODE Claim Claim Order = 23 Modify PAYMENT_TYPE _CODE Claim Claim New? State Model Name Business Component Field New CS Claim Status CS Claims Payment Status Transition From Transition To Resolved Closed New or Needs Modification? State Model Name Business Component Field Modified CS CG Promo Category Payment Status CS CG Promotion Category Deal Payment Payment Status Modified CS Check Payment Status CPG Check Payment Payment Status Modified CS Deduction Payment Status CPG Deduction Resolution - Payment Payment Status New or Needs Modification? LOV Type Code Display Value Language- Independent Code Comments
  • 306. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 306 6 Add the new states for the State Models: Requested, Approved, and Rejected. 7 Add or modify the transactions for the State Models: 8 Add new states for the following State Model: 9 Add the following new states for the State Models: Requested (Default), Approved, and Rejected. 10 Add the transactions listed in the following table for the State Models: Modified CS Promo Payment Status CPG Promo Deal Payment Payment Status Modified CS Promoted Product Payment Status CG Promo Product Fund Payment Payment Status New CS Claim Payment Status CS Claim Payments Payment Status Transition From Transition To Pending Requested Pending Cancelled Requested Cancelled Approved Cancelled Approved Submitted Rejected Pending Rejected Requested Rejected Cancelled Submitted Paid Submitted Cancelled Paid Voided New? State Model Name Business Component Field New CS CG Deal Payment Status CS CG Deal Payment Approval Payment Status Transition From Transition To Requested Approved Requested Rejected New or Needs Modification? State Model Name Business Component Field
  • 307. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 307 11 Log out of the Siebel application and bounce the Siebel Server. Audit Trail Use the following procedure to create new Audit Trails. To create new Audit Trails 1 Connect to the Siebel application. 2 Navigate to Site Map > Administration - Audit Trail > and create new Audit Trails with the information in the following tables: 3 Click the Update Audit Cache button. Workflows The following procedure details how to add the workflows that are associated with ACR 480. To add the ACR 480 workflows 1 Connect to Siebel Tools and navigate to Object Explorer. 2 In Object Explorer, select Project, and lock the CPG Plan, CPG Corporate Promotion, and ADL Enhancement projects. 3 Select Workflow Process in the Object Explorer, select Import Workflow Process from the right- click menu in the list view pane, and import the following workflow xml files: ■ CG Apply Corporate Promotion Process (Project = CPG Corporate Promotion) New? Audit Trail Business Component Base Table Update Delete Insert Assoc New CPG Plan Account S_SRC Y Y Y Y New? Field Table Name Column Name New Account Promotion Status S_SRC STATUS_CD New? Audit Trail Buscomp Base Table Update Delete Insert Assoc New CPG Plan Account Promotion S_SRC Y Y Y Y New? Field Table Name Column Name New Account Promotion Status S_SRC STATUS_CD
  • 308. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates 308 ■ CS CG Account Plan Update Process (Project = CPG Plan) ■ SIA CS ADL Service Workflow (Project = ADL Enhancement) ■ SIA CS Update Product Status (Project = ADL Enhancement) 4 Navigate to View > Toolbars, and make sure that the WF/Task Editor toolbar is checked. 5 Click the Publish/Activate button to deploy all of the workflows. 6 Log out of Siebel Tools. 7 Connect to the Siebel application. 8 Navigate to Site Map > Administration - Business Process > Workflow Deployment , and verify that all the workflows show up in the Active Workflow Processes List at the bottom. About Rules in the Personalization Screen The following section contains information about Rules in the Administration > Personalization screen. Table 19 contains details about the SVPFilterYear profile variable, Table 20 contains information about the SVP Current Year Filter rule set, and Table 21 contains information about the Current Filter rule. Table 19. Values of SVPFilterYear Value of SVPFilterYear Description CurrentSVPYear Profile Variable value for Current Year NextSVPYear Profile Variable value for Next Year PriorSVPYear Profile Variable value for Prior Year AllSVPYears Profile Variable value for All Years Table 20. SVP Current Year Filter Rule Set Rule Set Name Active Start Date End Date Description SVP Current Year Filter Y Select today's date SVP Current Year Filter Table 21. Current Filter Rule Rules Name Rule Type Seq Active Start Date End Date Description Current Filter Expression 1 Y Select today's date Filter for current year
  • 309. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. AA ■ Configuration Instructions for Enhancements and Updates Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA 309 Note the following information about working with rule sets: ■ You need to set different rule sets for different filters. ■ Make sure that the "SVPFilterYear" Profile Variable contains the proper values before you associate these rules to the applet. ■ When setting rules and when associating the rules with the applets, remember touse the "Reload Personalization Rules" menu option. Changing Visibility The following procedure details how to change visibility for the Plan Team and Promotion Team Business Components. To change visibility for the Plan Team and Promotion Team Business Components 1 In Object Explorer, navigate to Business Component. 2 For the Plan Team Business Component, query for Name = CPG Plan Account , and lock the project using the right-click menu. 3 For the Promotion Team Business Component, query for Name = CPG Plan Account Promotion, and lock the object using the right-click menu. 4 In Object Explorer, navigate to the Business Component View Modes for each Business Component. 5 Query for for Sales Rep in Business Component View Modes. 6 Change the value of the Visibility MVL from Account Position to Position. 7 Change the value of the Visibility MVF from Account Sales Rep to Sales 8 Compile the Business Components. Changing the User Properties for the Plan Team and Promotion Team Business Components The following procedure details how to change the user properties for the Plan Team and Promotion Team Business Components. To change the user properties for the Plan Team and Promotion Team Business Components 1 In Object Explorer, navigate to Business Component. 2 For the Plan Team Business Component, query for Name = CPG Plan Account, and lock theobject using the right-click menu. 3 For the Promotion Team Business Component, query for Name = CPG Plan Account Promotion, and lock the object using the right-click menu. 4 In Object Explorer, navigate to Business Component User Properties for each Business Component.
  • 310. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. AA Siebel Maintenance Release Guide, Version 8.1.1.x,