Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R

  • 18,519 views
Uploaded on

Siebel Maintenance …

Siebel Maintenance
Release Guide
Version 8.1.1.x, Rev. R
February 2011

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
18,519
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
144
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Siebel MaintenanceRelease GuideVersion 8.1.1.x, Rev. RFebruary 2011
  • 2. Copyright © 2005, 2011 Oracle and/or its affiliates. All rights reserved.Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may betrademarks of their respective owners.This software and related documentation are provided under a license agreement containing restrictionson use and disclosure and are protected by intellectual property laws. Except as expressly permitted inyour 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 anymeans. Reverse engineering, disassembly, or decompilation of this software, unless required by law forinteroperability, 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 software or related documentation is delivered to the U.S. Government or anyone licensing it onbehalf of the U.S. Government, the following notice is applicable:U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technicaldata delivered to U.S. Government customers are "commercial computer software" or "commercialtechnical data" pursuant to the applicable Federal Acquisition Regulation and agency-specificsupplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shallbe subject to the restrictions and license terms set forth in the applicable Government contract, and, tothe extent applicable by the terms of the Government contract, the additional rights set forth in FAR52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 OracleParkway, Redwood City, CA 94065.This software is developed for general use in a variety of information management applications. It is notdeveloped or intended for use in any inherently dang erous applications, including applications which maycreate a risk of personal injury. If you use this software in dangerous applications, then you shall beresponsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safeuse of this software. Oracle Corporation and its affiliates disclaim any liability for any damages causedby use of this software in dangerous applications.The Programs may provide links to Web sites and access to content, products, and services from thirdparties. Oracle is not responsible for the availability of, or an content provided on, third-party Web sites. yYou bear all risks associated with the use of such content. If you choose to purchase any products orservices from a third party, the relationship is directly between you and the third party. Oracle is notresponsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms ofthe agreement with the third party, including delivery of products or services and warranty obligationsrelated to purchased products or services. Oracle is not responsible for any loss or damage of any sortthat you may incur from dealing with any third party.
  • 3. ContentsRelease Notes for the Siebel 8.1.1.4 Fix Pack 7What’s New in This Revision 9Quick Fixes Included in 8.1.1.x Fix Packs 11Enhancements and Updates in 8.1.1.x Fix Packs 33 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 36 Enhancements and Updates in Version 8.1.1.1 37Configuration Instructions for Enhancements and Updates 40 Instructions for ACR 358 42 Instructions for ACR 403 42 Instructions for ACR 422 46 Instructions for ACR 426 67 Instructions for ACR 437 90 Instructions for ACR 439 91 Instructions for ACR 439B 92 Instructions for ACR 450 95 Instructions for ACR 452 96 Instructions for ACR 456 98 Instructions for ACR 457 100 Instructions for ACR 463 104 Instructions for ACR 464 143 Instructions for ACR 467 151 Instructions for ACR 468 158 Instructions for ACR 471 160 Instructions for ACR 474 and ACR 508 160 Instructions for ACR 475 231 Importing Non-ENU Symbolic Strings 255 Importing the Seed Data in the ACR 475B_UCM_2.zip File 255 Instructions for ACR 476 277 Instructions for ACR 480 281 Instructions for ACR 488 292 Instructions for ACR 494 292 Instructions for ACR 499 292 Instructions for ACR 500 319 Instructions for ACR 502 345 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 3
  • 4. Contents n Instructions for ACR 508 357 Instructions for ACR 526 362 Instructions for ACR 539 363 Instructions for ACR 543 385 Instructions for ACR 562 388 Instructions for ACR 574 433 Instructions for ACR 623 439 Instructions for ACR 626 439 Instructions for BI Publisher Enhancements 442Siebel Fix Pack Installation Instructions 442 Siebel Fix Pack Installation Overview 442 About Installing Siebel Fix Packs 446 Installing the Siebel Fix Pack on Microsoft Windows 447 Installing the Siebel Fix Pack on UNIX 453 Configuring Slipstream Patch Installation 457 Postinstallation Task for the Siebel Server 459 Postinstallation Task for the Web Server 459 Postinstallation Tasks for High Interactivity Clients 460 Postinstallation Task for Supporting Additional Languages 460 Uninstalling Siebel Fix Packs 461Resolved Change Requests 463 Resolved Change Requests in the Siebel 8.1.1.4 Fix Pack 464 Analytics 464 Call Center 465 Comm Media Energy 467 Connectors/EAI 467 Consumer Sector 468 Customer Order Management 472 Data Quality 477 General 478 Life Sciences 488 Loyalty 490 Marketing 492 Mobile Solutions 496 Partner Relationship Management 498 Public Sector 498 Sales 498 Service 499 Siebel E-commerce for Comms 500 Siebel Self Service Common 500 Universal Customer Master 501 User Interface 5064 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 5. Contents nResolved Change Requests in the Siebel 8.1.1.3 Fix Pack 508Call Center 508Web Service 508Comm Media Energy 512Connectors/EAI 516Consumer Sector 517Customer Order Management 518Data Quality 521Financial Services 521General 522iHelp 537Life Sciences 537Loyalty 542Marketing 543Mobile Solutions 545Partner Relationship Management 547Public Sector 547Sales 547Service 548Siebel eMail Response 549Siebel Self Service eCommon 549User Interface 550Resolved Change Requests in the Siebel 8.1.1.2 Fix Pack 553Web Service 553Call Center 554Comm Media Energy 555Connectors/EAI 555Consumer Sector 556Customer Order Management 556Data Quality 558General 558iHelp 569Life Sciences 569Marketing 570Mobile Solutions 572Sales 573Service 574Siebel eMail Response 574Siebel Self-Service Common 574Travel & Transportation 575User Interface 575Resolved Change Requests in the Siebel 8.1.1.1 Fix Pack 578 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 5
  • 6. Contents n Call Center 578 Web Service 578 Comm Media Energy 580 Connectors / EAI 581 Consumer Sector 582 Customer Order Management 595 Data Quality 601 Financial Services 601 General 602 Life Sciences 630 Loyalty 632 Marketing 635 Mobile Solutions 639 Partner Relationship Management 640 Public Sector 641 Sales 641 Service 642 Siebel E-Commerce 643 Siebel E-Commerce for Comms 646 Siebel eMail Response 656 Siebel E-Support 661 Siebel Self Service Common 661 Travel & Transportation 663 Universal Customer Master 669 User Interface 672 Web Service 688Oracle Welcomes Your Comments 7396 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 7. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. RFebruary 2011This guide includes the following topics:■ What’s New in This Revision on page 9■ Quick Fixes Included in 8.1.1.x Fix Packs on page 11■ Enhancements and Updates in 8.1.1.x Fix Packs on page 33■ Configuration Instructions for Enhancements and Updates on page 40■ Siebel Fix Pack Installation Instructions on page 453■ Resolved Change Requests on page 463■ Oracle Welcomes Your Comments on page 739Release Notes for the Siebel 8.1.1.4 FixPackThe following section contains information about known issues with this Fix Pack and any availableworkaround information.Missing Repository Objects and Seed Data When Installing ACR 499,ACR 500 and ACR 502After ACR 499, ACR 500, and ACR 502 have been installed, an error occurs when submitting an bulkrequest. The status of the bulk request change to partially complete, but the following error displa s s yin the Exceptions link: “Error in synchronize step: Integration component type ‘Deleted item’ is nota valid child type for component type ‘Line item’ (SBL-EAI-04008)”.For more information about this error and for steps to resolve it, see Doc ID 1295924.1 on My OralceSupport.Dmutl2.exe Changes to Read-Only After Database InitializationCategory: RemoteSubcategory: DB InitProduct Version: 8.1.1.4Change Request: 12-1Y3OYFPThe dmutl2.exe file becomes read-only after database initialization. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 7
  • 8. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Release Notes for theSiebel 8.1.1.4 Fix PackUse the following workaround if you already have the Mobile Web Client installed.1 Install the 8.1.1.4 Fix Pack.2 Before you run dbxtract and dbinit, empty the mwc_8114> folder. For example, empty C:Siebel<mwc_8114>UPGRADE.3 Run dbxtract and dbinit. The dmutl2.exe file becomes writable. NOTE: You only need to empty the folder once.ADM Deployment Fails on AIXCategory: Application Deployment ManagerSubcategory: FrameworkProduct Version: 8.1.1.4Change Request: 12-210GXT7Use the following workaround to address this issue:1 Make sure that 8.1.1.4 Management Server uses JRE1.6.2 Make sure that 8.1.1.4 Management Agent uses JRE1.5.3 After applying the 8.1.1.4, patch bring down all the services, the Gateway Server, Siebel Server, and the agent.4 Get the workaround classes.tar file from 8.1.1.4SIA[21225]ReleaseAIXServerSiebel_Enterprise_Server and copy it to a temporary location on your enterprise machine.5 Execute the copyjar.ksh file as shown below (hence it can replace the respective jar files): copyjar.ksh </siebel_root> copyjar.ksh /export/home/qa1/21225/ses Once it executes successfully, it will display the copied info on the console.6 Restart all services and continue with deployments.8 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 9. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ What’s New in This RevisionWhat’s New in This RevisionTable 1 describes the changes in this version of the documentation.Table 1. What’s New in Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R Topic Description “Siebel Fix Pack Installation Updated this section. Instructions” on page 442 “Instructions for ACR 526” on page 362 Added section with cross-reference to My Oracle Support article with detailed information and configuration instructions for ACR 526 (Doc ID 1296984.1.) (Rev. Q) “Instructions for ACR 499” on page 292 Corrected Step 8 in procedures for modifying the ABO Bulk Request SIS OM Quote IO map and the ABO Bulk Request SIS OM Order map. (Rev. Q) “Release Notes for the Siebel 8.1.1.4 Fix Added cross-reference to known issue that affects ACR Pack” 499, ACR 500, and ACR 502. (Rev. Q) “Instructions for ACR 502” Revised this section. (Rev. Q) “Instructions for ACR 475” Revised this section. (Rev. P) “Release Notes for the Siebel 8.1.1.4 Fix Added information about CR 12-1Y3OYFP. (Rev. P) Pack” on page 7 “Instructions for ACR 500” on page 319 Added information about two known issues with ACR 500, and workaround information for these issues. (Rev. P) “Release Notes for the Siebel 8.1.1.4 Fix Added this section to describe known issues with the Pack” on page 7 8.1.1.4 release. (Rev.O) “Configuration Instructions for Updated these sections for the 8.1.1.4 GA release. (Rev. Enhancements and Updates” O) “Resolved Change Requests” “Configuration Instructions for Added a note to indicate that customers only need to Enhancements and Updates” perform the configuration changes if they are implementing the ACRs. (Rev. N) “Quick Fixes Included in 8.1.1.x Fix Updated these sections for the Siebel 8.1.1.4 Fix Pack Packs” prerelease. (Rev. N) “Configuration Instructions for Enhancements and Updates” “Resolved Change Requests” “Instructions for ACR 474 and ACR 508” Added two workflows. (Rev. M) “Instructions for ACR 474 and ACR 508” Added crucial “known issues” information and made a few corrections in the procedures. (Rev. L) Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 9
  • 10. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ What’s New in ThisRevisionTable 1. What’s New in Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R Topic Description “Enhancements and Updates in Version Added information about ACR 467 and how to configure 8.1.1.1” it. (Rev. K) “Instructions for ACR 467” “Resolved Change Requests in the Siebel 8.1.1.1 Fix Pack” “Configuration Instructions for Revised configuration instructions for ACR 500 to include Enhancements and Updates” procedures for importing seed data. (Rev. K) “Enhancements and Updates in 8.1.1.x Updated these sections for the Siebel 8.1.1.3 Fix Pack Fix Packs” release. (Rev. J) “Configuration Instructions for Enhancements and Updates” “Resolved Change Requests” “Quick Fixes Included in 8.1.1.x Fix Updated these sections for the Siebel 8.1.1.3 Fix Pack Packs” prerelease. (Rev. I) “Enhancements and Updates in 8.1.1.x Fix Packs” “Resolved Change Requests” “Resolved Change Requests” Removed FR 12-1UHQ1L9. This FR was not provided in the Siebel 8.1.1.2 Fix Pack. “Resolved Change Requests” Removed reference to FR 12-1VM75R7. This fix was not provided in the 8.1.1.2 Fix Pack. (Rev. H) “Resolved Change Requests” Removed reference to FR 12-1VE6WMU. This fix was not provided in the 8.1.1.2 Fix Pack. (Rev. H) “Instructions for ACR 480” Added instructions for importing seed data associated with this enhancement. (Rev. H) “Resolved Change Requests” Corrected configuration instructions for FR 12-1QK0UEL. (Rev. H) “Resolved Change Requests” Corrected link to configuration instructions for FR 12- 1SPXSHM. (Rev. H) “Resolved Change Requests” Corrected Fix Request ID for providing support for Internet Explorer 8 on Windows Vista. (Rev. H)How to Use This GuideThis document, Siebel Maintenance Release Guide, Version 8.1.1.x, lists the enhancements and fixesprovided in version 8.1.1.x releases of Oracle’s Siebel Business Applications.10 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 11. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in 8.1.1.x Fix PacksThis guide also provides information, instructions, and guidelines for installing Siebel BusinessApplications Siebel Fix Pack 8.1.1.x releases on top of version 8.1.1 or a prior 8.1.1.x release.Use this Siebel Maintenance Release Guide in conjunction with Siebel Bookshelf documents,particularly the Siebel Installation Guide for the operating system you are using.NOTE: This Siebel Maintenance Release Guide is updated to include the latest Siebel Fix Pack 8.1.1.xrelease. The latest Siebel Fix Pack 8.1.1.x release available at publication time is Siebel Fix Pack8.1.1.4. Verify the availability and applicability of all Fix Pack or Quick Fix rel ases with Oracle Global eCustomer Support before you install.The information contained herein supersedes, for warranty and other purposes, the contents of allother 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 how to install the maintenancerelease (Fix Pack release). It also contains the most current information on product configurationissues and workarounds for your application. Note that there may be references to functionality,products, platforms, and language support in this document that are not available as part of theproducts that your organization has licensed. Consult Oracle Global Customer Support on My OracleSupport with questions regarding theapplicability of Siebel Maintenance Release Guide items to yourdeployment.Additional DocumentationOracle reserves the right to modify the documentation for Siebel Business Applications at any time.For related Siebel documentation, see My Or acle Support (https://support.oracle.com) and Bookshelffor 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 8.1.1.x Fix PacksSiebel 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 fix esare typically rolled into the next available Fix Pack for wider distribution to the Siebel BusinessApplications customer base. Testing for Quick Fixes is focused and is usually limited to verifying thatthe fix works on the specific platforms that the affected customer is running.If you have installed a Quick Fix for any Siebel 8.1.1 or 8.1.1.x release prior to the latest 8.1.1.xrelease covered by this document, review Table 2 on page 12 to make sure that your Quick Fixnumber is listed. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 11
  • 12. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in8.1.1.x Fix PacksCAUTION: If you do not see your Quick Fix number in the table, do not install the latest 8.1.1.x FixPack. This list is updated as new F Packs are released. Wait until your Quick Fix appears in the table ixbefore applying the latest Fix Pack. If you have questions, contact Global Customer Support or yourOracle representative.Table 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1Q35A8A 12-1Q450JI [21107] 21107 8.1.1.4 12-1QVMO57 12-1QVMO5T [21112] 21112 8.1.1.4 12-1TK3VGV 12-1TK3VI7 8.1.1 [21112] QF0028 8.1.1.4 12-1TK4OZF 12-1TK4P0Q 8.1.1 [21112] QF0028 8.1.1.4 12-1TK9B70 12-1TK92RX 8.1.1 [21112] QF0028 8.1.1.4 12-1TKA4KE 12-1TKA4MZ 8.1.1 [21112] QF0028 8.1.1.4 12-1TPS15R 12-1TPS17B 8.1.1 [21112] QF0028 8.1.1.4 12-1TPS1BB 12-1TPS1CY 8.1.1 [21112] QF0028 8.1.1.4 12-1TPS1E1 12-1TPS1FI 8.1.1 [21112] QF0028 8.1.1.4 12-1TWTQPT 12-1TWTQR5 8.1.1 [21112] QF0028 8.1.1.4 12-1VH3RYD 12-1VI2I3J 8.1.1 [21112] QF0072 8.1.1.4 12-1VM6N5D 12-1VR58XF 8.1.1 [21112] QF0082 8.1.1.4 12-1WXWUIF 12-1WXWUIX 8.1.1 [21112] QF00AN 8.1.1.4 12-1QVMO57 12-1VHKVBD 8.1.1 [21112] QF00AO 8.1.1.4 12-1XZBSUD 12-1Y8IY97 8.1.1 [21112] QF00AV 8.1.1.4 12-1XO6UN9 12-1XOO9FM 8.1.1 [21112] QF00AW 8.1.1.4 12-1XUY3ZF 12-1XVFKIP 8.1.1 [21112] QF00AW 8.1.1.4 12-1VI06I9 12-1YFC5GX 8.1.1 [21112] QF00AY 8.1.1.4 12-1IBE8WR 12-1YM4XDT 8.1.1 [21112] QF00BD 8.1.1.4 12-1WLTVBV 12-1YMLXLT 8.1.1 [21112] QF00BG 8.1.1.4 12-1XF0G9H 12-1XMQKEZ 8.1.1 [21112] QF00BK 8.1.1.4 12-1YOMS98 12-1YOMSBW 8.1.1 [21112] QF00BO 8.1.1.4 12-1PZ4R7R 12-1XTIC0H 8.1.1 [21112] QF00BP 8.1.1.4 12-1YCG2PL 12-1Z6WBPB 8.1.1 [21112] QF00BU 8.1.1.4 12-1TGO7DJ 12-1U0BPJM 8.1.1 [21112] QF0028 8.1.1.4 12-1TJMH71 12-1TJMH8L 8.1.1 [21112] QF0028 8.1.1.412 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 13. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in 8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-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 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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 13
  • 14. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1Y6LBZN 12-1Y6LC0G 8.1.1 [21112] QF00AT 8.1.1.4 12-1VMCEBF 12-1VNJREX 8.1.1 [21112] QF00AW 8.1.1.4 12-1XT16PO 12-1XT16QR 8.1.1 [21112] QF00AW 8.1.1.4 12-1YIQQID 12-1YIQKSC 8.1.1 [21112] QF00AZ 8.1.1.4 12-1XWIYRL 12-1YCXRIV 8.1.1 [21112] QF00BA 8.1.1.4 12-1VDPBPF 12-1Y54A1B 8.1.1 [21112] QF00BF 8.1.1.4 12-1Z4YJPX 12-1Z4YJQJ 8.1.1 [21112] QF00BI 8.1.1.4 12-1XWEWDL 12-1XYCRU9 8.1.1 [21112] QF00BK 8.1.1.4 12-1YKOYUX 12-1YM4UWN 8.1.1 [21112] QF00BK 8.1.1.4 12-1XF0GC9 12-1XL4MPA 8.1.1 [21112] QF00BL 8.1.1.4 12-1WUJE2X 12-1WUJE3Y 8.1.1 [21112] QF00BR 8.1.1.4 12-1ZPH4ZU 12-1ZRVWP8 8.1.1 [21112] QF00BU 8.1.1.4 12-1YOKK4N 12-1Z7V33V 8.1.1 PDA [21112_10] 8.1.1 PDA 8.1.1.4 [21112_10] 12-1YOKGG5 12-1Z04TF7 8.1.1 PDA [21112_11] 8.1.1 PDA 8.1.1.4 [21112_11] 12-1YOK96H 12-1YOK97J 8.1.1 PDA [21112_8] 8.1.1 PDA 8.1.1.4 [21112_8] 12-1YOKK66 12-1YOKK9R 8.1.1 PDA [21112_8] 8.1.1 PDA 8.1.1.4 [21112_8] 12-1YOMS7P 12-1YOMS8H 8.1.1 PDA [21112_9] 8.1.1 PDA 8.1.1.4 [21112_9] 12-1JFQEZ6 12-1Z9RYA5 8.1.1 PDA [21112_9] 8.1.1 PDA 8.1.1.4 [21112_9] 12-1YGT6Q9 12-1YOMSAP 8.1.1 PDA [21112_9] 8.1.1 PDA 8.1.1.4 [21112_9] 12-1Z3IMD9 12-1Z3I799 8.1.1 PDA [21112_9] 8.1.1 PDA 8.1.1.4 [21112_9] 12-1TK4UBL 12-1XS216R 8.1.1.1 [21211] QF0191 8.1.1.4 12-1S1Y205 12-1X6RYEB 8.1.1.1 [21211] QF0192 8.1.1.4 12-1VH3RP7 12-1Y5LUYL 8.1.1.1 [21211] QF01AD 8.1.1.4 12-1XC7KQR 12-1YJP6YH 8.1.1.1 [21211] QF01AH 8.1.1.4 12-1PFQSZV 12-1YJPUAJ 8.1.1.1 [21211] QF01AN 8.1.1.414 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 15. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in 8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-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 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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 15
  • 16. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-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 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.416 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 17. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in 8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-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 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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 17
  • 18. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-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 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.418 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 19. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in 8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1QBCC09 12-1Z312WH 8.1.1.2 [21215] QF0296 8.1.1.4 12-1YOLS71 12-1YOMPKH 8.1.1.2 [21215] QF0298 8.1.1.4 12-1YZND55 12-1Z04EEK 8.1.1.2 [21215] QF0299 8.1.1.4 12-1Y3OXW9 12-1Y90EUX 8.1.1.2 [21215] QF02AB 8.1.1.4 12-1V9U49H 12-1Z0MDNB 8.1.1.2 [21215] QF02AC 8.1.1.4 12-1XRKKWD 12-1YAH25H 8.1.1.2 [21215] QF02AI 8.1.1.4 12-1YNLBB5 12-1Z7DTPM 8.1.1.2 [21215] QF02AI 8.1.1.4 12-1Z1KQM1 12-1ZF3CXL 8.1.1.2 [21215] QF02AI 8.1.1.4 12-1Z3IMBL 12-1ZOJCQH 8.1.1.2 [21215] QF02AI 8.1.1.4 12-1V418JR 12-1VOFQ3P 8.1.1.2 [21215] QF02AJ 8.1.1.4 12-1U0C8HX 12-1XM9N8Z 8.1.1.2 [21215] QF02AM 8.1.1.4 12-1TLCZVH 12-1Z9S46Z 8.1.1.2 [21215] QF02AN 8.1.1.4 12-1U5RB3V 12-203152F 8.1.1.2 [21215] QF02AN 8.1.1.4 12-1XIVMBZ 12-1XQ4T5X 8.1.1.2 [21215] QF02AQ 8.1.1.4 12-1Y9HK6T 12-1Y9HK8A 8.1.1.2 [21215] QF02AQ 8.1.1.4 12-1XBND23 12-1ZRW32R 8.1.1.2 [21215] QF02AR 8.1.1.4 12-1VMCEBF 12-1ZUS4MB 8.1.1.2 [21215] QF02AU 8.1.1.4 12-1SEPT2B 12-20F4VE5 8.1.1.2 [21215] QF02BK 8.1.1.4 12-1ZZMR15 12-202252X 8.1.1.2 [21215] QF02BL 8.1.1.4 12-1YGT6Q9 12-1YGT6R2 8.1.1.2 WM5 [21215_5] 8.1.1.2 WM 5 8.1.1.4 [21215_5] 12-1YOMS7P 12-1YV5IMZ 8.1.1.2 WM5 [21215_5] 8.1.1.2 WM 5 8.1.1.4 [21215_5] 12-1Z6VW9H 12-1Z6VWA6 8.1.1.2 WM5 [21215_6] 8.1.1.2 WM 5 8.1.1.4 [21215_6] 12-1JFQEZ6 12-1Y28CXL 8.1.1.2 WM5 [21215_5] 8.1.1.2 WM 5 8.1.1.4 [21215_5] 12-1Y2PC95 12-1YCFJSR 8.1.1.3 [21219] QF0302 8.1.1.4 12-1VMCEBF 12-1XYUAXZ 8.1.1.3 [21219] QF0303 8.1.1.4 12-1WTJXWZ 12-1X97V94 8.1.1.3 [21219] QF0303 8.1.1.4 12-1XF0G9H 12-1XMQKEJ 8.1.1.3 [21219] QF0303 8.1.1.4 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 19
  • 20. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1XOOC39 12-1XQ4AWP 8.1.1.3 [21219] QF0303 8.1.1.4 12-1U0C8HX 12-1Z0MB07 8.1.1.3 [21219] QF0305 8.1.1.4 12-1QTP7PD 12-1Y2PBV7 8.1.1.3 [21219] QF0306 8.1.1.4 12-1Y0AZPB 12-1Y0AZPY 8.1.1.3 [21219] QF0307 8.1.1.4 12-1YOKG0B 12-1YOKNO0 8.1.1.3 [21219] QF0310 8.1.1.4 12-1VM7S6L 12-1Z4YJJT 8.1.1.3 [21219] QF0311 8.1.1.4 12-1Z1KQM1 12-1Z04V45 8.1.1.3 [21219] QF0312 8.1.1.4 12-1YFU2BX 12-1YHAEXR 8.1.1.3 [21219] QF0313 8.1.1.4 12-1YQ37K5 12-1YVB42D 8.1.1.3 [21219] QF0313 8.1.1.4 12-1Z6VRLF 12-1Z6WCOG 8.1.1.3 [21219] QF0314 8.1.1.4 12-1Z3IMBL 12-1Z6PEQ9 8.1.1.3 [21219] QF0315 8.1.1.4 12-1XTIRJJ 12-1ZF3T8Z 8.1.1.3 [21219] QF0316 8.1.1.4 12-1Q7NVMV 12-1ZFBE8H 8.1.1.3 [21219] QF0317 8.1.1.4 12-1IKIU3B 12-1ZH9OLB 8.1.1.3 [21219] QF0318 8.1.1.4 12-1X65YA7 12-1ZFCYUM 8.1.1.3 [21219] QF0319 8.1.1.4 12-1ZFBCAH 12-1ZFBJ5Z 8.1.1.3 [21219] QF0320 8.1.1.4 12-1V4JH1X 12-1ZF3AMP 8.1.1.3 [21219] QF0321 8.1.1.4 12-1W6DOUA 12-1ZD5YHL 8.1.1.3 [21219] QF0323 8.1.1.4 12-1Y8J0H7 12-1ZF38WH 8.1.1.3 [21219] QF0326 8.1.1.4 12-1YCFMMF 12-1YFCA4P 8.1.1.3 [21219] QF0328 8.1.1.4 12-1PZ4R7R 12-1ZURZZ3 8.1.1.3 [21219] QF0334 8.1.1.4 12-1XBND23 12-1ZY61E5 8.1.1.3 [21219] QF0336 8.1.1.4 12-OVT1LK 12-201KB2F 8.1.1.3 [21219] QF0337 8.1.1.4 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.420 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 21. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in 8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1HCLBH7 12-1XYTSLP 8.1.1.3 [21219] QF304 8.1.1.4 12-1YOKK4N 12-1Z520FN 8.1.1.3 WM5 [21219_2] 8.1.1.3 WM5 8.1.1.4 [21219_2] 12-1VGM2U4 12-1Y641L8 Unspecified - 8.1.1.4 12-1VM72OT 12-1WLUTF3 7.7.2.2 [18356] QF7201 8.1.1.3 12-1U5SY53 12-1U5ULV5 8.1.1 [21112] QF0043 8.1.1.3 12-1UQ61Q1 12-1UQWPP0 8.1.1 [21112] QF0061 8.1.1.3 12-1V7WVM7 12-1V7WVNO 8.1.1 [21112] QF0062 8.1.1.3 12-1V0593H 12-1V3K66J 8.1.1 [21112] QF0068 8.1.1.3 12-1UH87LR 12-1UOUW8L 8.1.1 [21112] QF0080 8.1.1.3 12-1UJQNRZ 12-1UJQNTU 8.1.1 [21112] QF0080 8.1.1.3 12-1VH3RCZ 12-1VH3HYN 8.1.1 [21112] QF0080 8.1.1.3 12-1VKHEG7 12-1VKHEGV 8.1.1 [21112] QF0080 8.1.1.3 12-1UIB7XV 12-1UPTJSJ 8.1.1 [21112] QF0081 8.1.1.3 12-1V418GZ 12-1V418HK 8.1.1 [21112] QF0081 8.1.1.3 12-QND3G8 12-1VM7MNP 8.1.1 [21112] QF0083 8.1.1.3 12-1U5VI79 12-1VMAZDJ 8.1.1 [21112] QF0084 8.1.1.3 12-1VM8H57 12-1VM8H5Y 8.1.1 [21112] QF0085 8.1.1.3 12-1VR73HT 12-1VR73IR 8.1.1 [21112] QF0088 8.1.1.3 12-1VROIM3 12-1WE2T3K 8.1.1 [21112] QF0089 8.1.1.3 12-1U4NF3F 12-1WAL0Z9 8.1.1 [21112] QF0093 8.1.1.3 12-1VM6N4J 12-1WLTUS5 8.1.1 [21112] QF0095 8.1.1.3 12-1VMBL0Z 12-1WXXCZJ 8.1.1 [21112] QF0096 8.1.1.3 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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 21
  • 22. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1WXFOAB 12-1Y54TB7 8.1.1 [21112] QF00AU 8.1.1.3 12-1R3SHD7 12-1R3SHEV 8.1.1 [21112] QF1001 8.1.1.3 12-1UWODHL 12-1UWODIV 8.1.1 [21112] QF0059 8.1.1.3 12-1VHLD1H 12-1VJIBZ1 8.1.1 [21112] QF0078 8.1.1.3 12-1V41905 12-1V4190P 8.1.1 [21112] QF0079 8.1.1.3 12-1VCQAE7 12-1VABY2J 8.1.1 [21112] QF0080 8.1.1.3 12-1VMCEM9 12-1VNJB15 8.1.1 [21112] QF0082 8.1.1.3 12-1VM5K6V 12-1VM5OFZ 8.1.1 [21112] QF0086 8.1.1.3 12-1TK4DJP 12-1VR7XBB 8.1.1 [21112] QF0088 8.1.1.3 12-1NXS3RV 12-1VMB443 8.1.1 [21112] QF0090 8.1.1.3 12-1VCQVAZ 12-1VVFZX5 8.1.1 [21112] QF0091 8.1.1.3 12-1VMC9ID 12-1VMC9JC 8.1.1 [21112] QF0094 8.1.1.3 12-1VR43FP 12-1VR613R 8.1.1 [21112] QF0097 8.1.1.3 12-1WV0HS3 12-1WVIDDX 8.1.1 [21112] QF0098 8.1.1.3 12-1WXX8FJ 12-1WYEWC1 8.1.1 [21112] QF00AA 8.1.1.3 12-1SD8XW1 12-1XEBKOX 8.1.1 [21112] QF00AE 8.1.1.3 12-1T2IN2L 12-1U5RPCP 8.1.1 [21112] QF00AO 8.1.1.3 12-1U0AX75 12-1XM9M2R 8.1.1 [21112] QF00AO 8.1.1.3 12-1R3SHD7 12-1SCQC43 8.1.1 [21112] QF1001 8.1.1.3 12-1R3SHD7 12-1SSU185 8.1.1 [21112] QF1002 8.1.1.3 12-1VM6B55 12-1VM8H0R 8.1.1 [21112] QF1003 8.1.1.3 12-1LC1A2Z 12-1WF6BOH 8.1.1 [21112] QF0099 QF0099 8.1.1.3 12-1U5VI4H 12-1UH8O67 8.1.1 PDA [21112_1] 8.1.1 PDA 8.1.1.3 [21112_1] 12-1VR6T39 12-1VR6T42 8.1.1 PDA [21112_4] 8.1.1 PDA 8.1.1.3 _21112_4] 12-1VMBHFJ 12-1VMBHGE 8.1.1 PDA [21112_5] 8.1.1 PDA 8.1.1.3 [21112_5] 12-1VM6HI1 12-1WS4HGD 8.1.1 PDA [21112_6] 8.1.1 PDA 8.1.1.3 [21112_6] 12-1V418N3 12-1V7FOQ9 8.1.1.1 [21211] QF0114 8.1.1.322 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 23. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in 8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1VH3RGB 12-1VKYYB5 8.1.1.1 [21211] QF0114 8.1.1.3 12-1UI8TH3 12-1UI8THP 8.1.1.1 [21211] QF0115 8.1.1.3 12-1RAJ0I1 12-1VGLLEK 8.1.1.1 [21211] QF0121 8.1.1.3 12-1VE7EH7 12-1VE6TJ6 8.1.1.1 [21211] QF0124 8.1.1.3 12-1U5V32T 12-1U7CGKP 8.1.1.1 [21211] QF0125 8.1.1.3 12-1VEOU89 12-1VI2IE9 8.1.1.1 [21211] QF0130 8.1.1.3 12-1UWODHL 12-1VR3IU1 8.1.1.1 [21211] QF0133 8.1.1.3 12-1VR2PWN 12-1VR3NJZ 8.1.1.1 [21211] QF0134 8.1.1.3 12-1HWWAY4 12-1VM5IIV 8.1.1.1 [21211] QF0139 8.1.1.3 12-1VR2PUZ 12-1VR3L6U 8.1.1.1 [21211] QF0141 8.1.1.3 12-1TXBDIV 12-1VTSQMV 8.1.1.1 [21211] QF0146 8.1.1.3 12-1WF6P3J 12-1WF6HIG 8.1.1.1 [21211] QF0153 8.1.1.3 12-1VR5ZGB 12-1VR4O99 8.1.1.1 [21211] QF0154 8.1.1.3 12-1PVZS4R 12-1VR5PTN 8.1.1.1 [21211] QF0155 8.1.1.3 12-1X3RF25 12-1X3RF2X 8.1.1.1 [21211] QF0156 8.1.1.3 12-1VNJ8NI 12-1VR29OR 8.1.1.1 [21211] QF0157 8.1.1.3 12-1WF5ZQH 12-1WF5ZRW 8.1.1.1 [21211] QF0157 8.1.1.3 12-1WA5CGZ 12-1WEE4FN 8.1.1.1 [21211] QF0158 8.1.1.3 12-1WF6G1R 12-1WF6G2Q 8.1.1.1 [21211] QF0158 8.1.1.3 12-1WLTLED 12-1WLTLEY 8.1.1.1 [21211] QF0159 8.1.1.3 12-1UGQKS5 12-1VR5ORB 8.1.1.1 [21211] QF0160 8.1.1.3 12-1WF6PMP 12-1WK5MQ5 8.1.1.1 [21211] QF0161 8.1.1.3 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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 23
  • 24. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1TK6U03 12-1UIBBJV 8.1.1.1 [21211] QF1101 8.1.1.3 12-1UW5F8T 12-1UW5FA5 8.1.1.1 [21211] QF1102 8.1.1.3 12-1VM7OFB 12-1VM8AUM 8.1.1.1 [21211] QF1103 8.1.1.3 12-1VR2YCD 12-1VR2YD7 8.1.1.1 [21211] QF1104 8.1.1.3 12-1WA5CGZ 12-1WRAAA5 8.1.1.1 [21211] QF1105 8.1.1.3 12-1WF6G1R 12-1WRAAD1 8.1.1.1 [21211] QF1105 8.1.1.3 12-1X56KI9 12-1X56R61 8.1.1.1 [21211] QF1106 8.1.1.3 12-1VE7EQ3 12-1VG4DL9 8.1.1.1 [21211] QF2103 8.1.1.3 12-1UI8IN7 12-1VR7JA7 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VNJJZ2 12-1VNKHLQ 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VNJZ8L 12-1VNJUIQ 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR347X 12-1VR348W 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR398K 12-1VR399Z 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR4A7V 12-1VR4A8M 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR4FMB 12-1VR4FN2 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR6FWO 12-1VR60PC 8.1.1.1 [21211] QF4101 8.1.1.3 12-1UI8IN7 12-1WLTWCD 8.1.1.1 [21211] QF4102 8.1.1.3 12-1VR3957 12-1VR397S 8.1.1.1 [21211] QF4102 8.1.1.3 12-1WCP9WP 12-1WCP9XZ 8.1.1.1 [21211] QF4102 8.1.1.3 12-1WF73FF 12-1WF73IY 8.1.1.1 [21211] QF4102 8.1.1.3 12-1WFFM67 12-1WFFM6W 8.1.1.1 [21211] QF4102 8.1.1.3 12-1R3SHD7 12-1VR77JP 8.1.1.1 [21211] QF5101 8.1.1.3 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.324 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 25. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in 8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1REV4NL 12-1VDPAUL 8.1.1.1 [21211] QF0118 8.1.1.3 12-1SJ54EF 12-1VGLLFE 8.1.1.1 [21211] QF0121 8.1.1.3 12-1U5SY53 12-1VMAX0J 8.1.1.1 [21211] QF0126 8.1.1.3 12-1VNJ20P 12-1VR2KIF 8.1.1.1 [21211] QF0132 8.1.1.3 12-1VNJZD9 12-1VR3YPZ 8.1.1.1 [21211] QF0136 8.1.1.3 12-1VM81EJ 12-1VR3OK5 8.1.1.1 [21211] QF0137 8.1.1.3 12-1V418SN 12-1V418T8 8.1.1.1 [21211] QF0138 8.1.1.3 12-1VNKRB3 12-1VNKRC7 8.1.1.1 [21211] QF0140 8.1.1.3 12-1UJQNRZ 12-1VMCBXB 8.1.1.1 [21211] QF0143 8.1.1.3 12-1VROIM3 12-1VROIMY 8.1.1.1 [21211] QF0148 8.1.1.3 12-1V41905 12-1VR46VZ 8.1.1.1 [21211] QF0149 8.1.1.3 12-1VM6N0D 12-1VM6N0Y 8.1.1.1 [21211] QF0150 8.1.1.3 12-1T2II25 12-1WF6XDZ 8.1.1.1 [21211] QF0154 8.1.1.3 12-1QHN64C 12-1VM5JMC 8.1.1.1 [21211] QF0156 8.1.1.3 12-1VMAF2Z 12-1VMC0PF 8.1.1.1 [21211] QF0160 8.1.1.3 12-1W4M5S2 12-1WAWS42 8.1.1.1 [21211] QF0162 8.1.1.3 12-1RVO17F 12-1VR5GB0 8.1.1.1 [21211] QF0164 8.1.1.3 12-1VM83AX 12-1X5630E 8.1.1.1 [21211] QF0170 8.1.1.3 12-1VR66BT 12-1VR6WMR 8.1.1.1 [21211] QF0170 8.1.1.3 12-1VR4BZH 12-1WF6HRX 8.1.1.1 [21211] QF0172 8.1.1.3 12-1X3PRS9 12-1X3PRSZ 8.1.1.1 [21211] QF0173 8.1.1.3 12-1WXFOAB 12-1X1RZWH 8.1.1.1 [21211] QF0174 8.1.1.3 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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 25
  • 26. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1VMAEXZ 12-1VMBEH5 8.1.1.1 [21211] QF0190 8.1.1.3 12-1UH87LR 12-1Y72ZUH 8.1.1.1 [21211] QF01AF 8.1.1.3 12-1VR2NH1 12-1VR2NII 8.1.1.1 [21211] QF1104 8.1.1.3 12-1TXBDIV 12-1WLTK5Q 8.1.1.1 [21211] QF1105 8.1.1.3 12-1UW5DFF 12-1UW5DGH 8.1.1.1 [21211] QF1105 8.1.1.3 12-1W6PXXB 12-1W6PXY5 8.1.1.1 [21211] QF1105 8.1.1.3 12-1X56155 12-1X56KGK 8.1.1.1 [21211] QF1106 8.1.1.3 12-1X56KGX 12-1X56KHX 8.1.1.1 [21211] QF1106 8.1.1.3 12-1X65TKV 12-1XVG99R 8.1.1.1 [21211] QF1107 8.1.1.3 12-1UH87BR 12-1VPNBHD 8.1.1.1 [21211] QF2103 8.1.1.3 12-1VMJW4R 12-1VNJUJS 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VNJJXN 12-1VNKHMB 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VNJZ9H 12-1VNJUHZ 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR3GUN 12-1VR4LB3 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR4V1B 12-1VR4V22 8.1.1.1 [21211] QF4101 8.1.1.3 12-1VR6QRN 12-1VR6QT2 8.1.1.1 [21211] QF4101 8.1.1.3 12-1WF77PG 12-1WF77Q5 8.1.1.1 [21211] QF4102 8.1.1.3 12-1VM6N4J 12-1XQ49XF 8.1.1.1 [21211] QF5105 8.1.1.3 12-1VR2NH1 12-1WIXZ3T 8.1.1.1 [21211] QF7101 8.1.1.3 12-1X0C24K 12-1X0C26K 8.1.1.1 [21211] QF7102 8.1.1.3 12-1X56155 12-1XYCA25 8.1.1.1 [21211] QF7103 8.1.1.3 12-1X65TKV 12-1XWWVSZ 8.1.1.1 [21211] QF7103 8.1.1.3 12-1XVXEFP 12-1XWET8K 8.1.1.1 [21211] QF7103 8.1.1.3 12-1KXYCJ7 12-1VGLLDP 8.1.1.1 [21211] QF0121 QF0121 8.1.1.3 12-1VM81EJ 12-1VMATZX 8.1.1.2 [21215] QF0201 8.1.1.3 12-1VR4BF7 12-1VR3P8V 8.1.1.2 [21215] QF0201 8.1.1.3 12-1UI7QYZ 12-1V14JRA 8.1.1.2 [21215] QF0202 8.1.1.3 12-1W7XG07 12-1WF75UB 8.1.1.2 [21215] QF0205 8.1.1.3 12-1U4NF3F 12-1VKHKCF 8.1.1.2 [21215] QF0206 8.1.1.3 12-1VR4BT3 12-1VR50U7 8.1.1.2 [21215] QF0207 8.1.1.326 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 27. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in 8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1WF6PLV 12-1WHFPCJ 8.1.1.2 [21215] QF0207 8.1.1.3 12-1QG70K8 12-1VMBCSV 8.1.1.2 [21215] QF0208 8.1.1.3 12-1SJNUGJ 12-1WQ5VI3 8.1.1.2 [21215] QF0209 8.1.1.3 12-1VMAEXZ 12-1WLUFT3 8.1.1.2 [21215] QF0210 8.1.1.3 12-1DK2UO8 12-1WU19LH 8.1.1.2 [21215] QF0211 8.1.1.3 12-1U5V32T 12-1VR5ESF 8.1.1.2 [21215] QF0212 8.1.1.3 12-1QHN64C 12-1WYEYBP 8.1.1.2 [21215] QF0213 8.1.1.3 12-1JGY6HC 12-1WYWA9N 8.1.1.2 [21215] QF0216 8.1.1.3 12-1X6681L 12-1XCMB93 8.1.1.2 [21215] QF0216 8.1.1.3 12-1VR78HP 12-1VR7VHR 8.1.1.2 [21215] QF0217 8.1.1.3 12-1X1AZAL 12-1X65NWV 8.1.1.2 [21215] QF0218 8.1.1.3 12-1X3PH1V 12-1X4OYWX 8.1.1.2 [21215] QF0220 8.1.1.3 12-1VNKRB3 12-1X98CML 8.1.1.2 [21215] QF0221 8.1.1.3 12-1V418GZ 12-1WYEKN7 8.1.1.2 [21215] QF0222 8.1.1.3 12-1PPACL7 12-1VMB80D 8.1.1.2 [21215] QF0223 8.1.1.3 12-1VEOU89 12-1WF6MH3 8.1.1.2 [21215] QF0223 8.1.1.3 12-1WA5CGZ 12-1WEE4GH 8.1.1.2 [21215] QF0223 8.1.1.3 12-1WF6G1R 12-1WF7AUB 8.1.1.2 [21215] QF0223 8.1.1.3 12-1X65TKV 12-1X65TML 8.1.1.2 [21215] QF0223 8.1.1.3 12-1V418N3 12-1X1AS17 8.1.1.2 [21215] QF0225 8.1.1.3 12-1NSKPIL 12-1X8R0OX 8.1.1.2 [21215] QF0226 8.1.1.3 12-1S9QMWN 12-1VM55TX 8.1.1.2 [21215] QF0227 8.1.1.3 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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 27
  • 28. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1U0AX75 12-1VGLSEY 8.1.1.2 [21215] QF0238 8.1.1.3 12-1VNIMYR 12-1X663V7 8.1.1.2 [21215] QF0238 8.1.1.3 12-1X0BIZX 12-1X0BJ10 8.1.1.2 [21215] QF0239 8.1.1.3 12-1UH87LR 12-1WYVUF3 8.1.1.2 [21215] QF0240 8.1.1.3 12-1XC7L1L 12-1XC7L26 8.1.1.2 [21215] QF0241 8.1.1.3 12-1VMC9ID 12-1XT0PSF 8.1.1.2 [21215] QF0246 8.1.1.3 12-1VM7HW1 12-1XS1LZH 8.1.1.2 [21215] QF0251 8.1.1.3 12-1Q16OWB 12-1VMBP4R 8.1.1.2 [21215] QF0253 8.1.1.3 12-1VHLD1H 12-1Y2P00T 8.1.1.2 [21215] QF0254 8.1.1.3 12-1VMAF2Z 12-1YDEQQT 8.1.1.2 [21215] QF0256 8.1.1.3 12-1LC1A2Z 12-1Y54T99 8.1.1.2 [21215] QF0257 8.1.1.3 12-1VR43FP 12-1YK6TOR 8.1.1.2 [21215] QF0259 8.1.1.3 12-1V41SPV 12-1XEJIBF 8.1.1.2 [21215] QF1201 8.1.1.3 12-1VR4BVB 12-1VR5ATP 8.1.1.2 WM5 [21215_1] 8.1.1.2 8.1.1.3 [21215_1] 12-1V6XL7R 12-1V7WKHX 8.1.1.2 WM5 [21215_1] 8.1.1.2 WM5 8.1.1.3 [21215_1] 12-1VNJH0Z 12-1VNJH1R 8.1.1.2 WM5 [21215_1] 8.1.1.2 WM5 8.1.1.3 [21215_1] 12-1WCP7ZT 12-1WCP80M 8.1.1.2 WM5 [21215_1] 8.1.1.2 WM5 8.1.1.3 [21215_1] 12-1X1S03V 12-1X1GML7 8.1.1.2 WM5 [21215_2] 8.1.1.2 WM5 8.1.1.3 _21215_2] 12-1VNJY1R 12-1VR6P9H 8.1.1.2 WM5 [21215_3] 8.1.1.2 WM5 8.1.1.3 [21215_3] 12-1PBVORR 12-1SM2F17 8.1.1 [21112] QF0008 8.1.1.2 12-1SI5H61 12-1SI5H6M 8.1.1 [21112] QF0008 8.1.1.2 12-1TBLYYA 12-1TBLZ15 8.1.1 [21112] QF0015 8.1.1.2 12-1THO6OP 12-1TK476J 8.1.1 [21112] QF0016 8.1.1.2 12-1T7V4R7 12-1TBLYXR 8.1.1 [21112] QF0017 8.1.1.2 12-1TH5NV5 12-1THO2I5 8.1.1 [21112] QF0017 8.1.1.2 12-1SFPEAN 12-1TK3VLL 8.1.1 [21112] QF0019 8.1.1.228 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 29. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in 8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1TGO4RF 12-1TI66LP 8.1.1 [21112] QF0021 8.1.1.2 12-1OQD0BB 12-1TK8U26 8.1.1 [21112] QF0023 8.1.1.2 12-1STC0UB 12-1TK5L5F 8.1.1 [21112] QF0023 8.1.1.2 12-1TK6LZT 12-1TK85H4 8.1.1 [21112] QF0023 8.1.1.2 12-1TD6X31 12-1TDOVOJ 8.1.1 [21112] QF0024 8.1.1.2 12-1L3YVPO 12-1T5WKPM 8.1.1 [21112] QF0025 8.1.1.2 12-1QBCC2R 12-1TA9KB1 8.1.1 [21112] QF0026 8.1.1.2 12-1SJ5MIZ 12-1TS8XK5 8.1.1 [21112] QF0026 8.1.1.2 12-1T2J5H3 12-1TARVI6 8.1.1 [21112] QF0026 8.1.1.2 12-1SBRAKT 12-1TTI5LX 8.1.1 [21112] QF0031 8.1.1.2 12-1TK4CEL 12-1TK9IXL 8.1.1 [21112] QF0031 8.1.1.2 12-1QMX8LP 12-1U0DDZT 8.1.1 [21112] QF0033 8.1.1.2 12-1U0BPQZ 12-1U0BPSO 8.1.1 [21112] QF0034 8.1.1.2 12-1T7DG8H 12-1T7DG98 8.1.1 [21112] QF0035 8.1.1.2 12-1RHR0N1 12-1TARVQH 8.1.1 [21112] QF0037 8.1.1.2 12-1R6NUCR 12-1TDO7P7 8.1.1 [21112] QF0040 8.1.1.2 12-1TUVZQ9 12-1TXBVH1 8.1.1 [21112] QF0041 8.1.1.2 12-1U5RB3V 12-1U5RB5J 8.1.1 [21112] QF0041 8.1.1.2 12-1UHPV6B 12-1UHPV78 8.1.1 [21112] QF0042 8.1.1.2 12-1TXC3RL 12-1TXT92X 8.1.1 [21112] QF0044 8.1.1.2 12-1U4I7KV 12-1U5RZSJ 8.1.1 [21112] QF0044 8.1.1.2 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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 29
  • 30. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1UH87BR 12-1UH8JTX 8.1.1 [21112] QF0051 8.1.1.2 12-1KJP2WG 12-1UIA3SN 8.1.1 [21112] QF0053 8.1.1.2 12-1RRBFQ9 12-1UOWLB9 8.1.1 [21112] QF0054 8.1.1.2 12-1QPSY8J 12-1UIADXT 8.1.1 [21112] QF0055 8.1.1.2 12-1V0598R 12-1UZMXSH 8.1.1 [21112] QF0056 8.1.1.2 12-1SBRA31 12-1STC1G9 8.1.1 [21112] QF0058 8.1.1.2 12-1TGOA5B 12-1V41YTV 8.1.1 [21112] QF0060 8.1.1.2 12-1VH3J0H 12-1VH3J1D 8.1.1 [21112] QF0064 8.1.1.2 12-1UGQK67 12-1UG91VX 8.1.1 [21112] QF0065 8.1.1.2 12-1U8XCTD 12-1U8XCU7 8.1.1 [21112] QF0066 8.1.1.2 12-1T6DMLW 12-1VI33A5 8.1.1 [21112] QF0067 8.1.1.2 12-1UI8QNP 12-1VKHLAV 8.1.1 [21112] QF0068 8.1.1.2 12-1UU5KSH 12-1UX5VWV 8.1.1 [21112] QF0074 8.1.1.2 12-1RPD2ML 12-1VM83TH 8.1.1 [21112] QF0076 8.1.1.2 12-1OK0UBP 12-1VEOVOV 8.1.1 [21112] QF0081 8.1.1.2 12-1VM6N5D 12-1VR58XF 8.1.1 [21112] QF0082 8.1.1.2 12-1V6FY27 12-1V6FY31 8.1.1 PDA [21112_2] 8.1.1 PDA 8.1.1.2 [21112_2] 12-1SBRAKT 12-1UH8553 8.1.1.1 [21211] QF0101 8.1.1.2 12-1TGO4RF 12-1UI8E4P 8.1.1.1 [21211] QF0101 8.1.1.2 12-1OVCU5D 12-1UI8Y05 8.1.1.1 [21211] QF0103 8.1.1.2 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.230 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 31. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in 8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1SBRA31 12-1UW6491 8.1.1.1 [21211] QF0110 8.1.1.2 12-1UX6FHT 12-1UZD71U 8.1.1.1 [21211] QF0112 8.1.1.2 12-1R0X6NL 12-1V4108B 8.1.1.1 [21211] QF0113 8.1.1.2 12-1L3YVPO 12-1V9TQUZ 8.1.1.1 [21211] QF0116 8.1.1.2 12-1S1FXNF 12-1VBAHH9 8.1.1.1 [21211] QF0117 8.1.1.2 12-1VK09JB 12-1VK09K4 8.1.1.1 [21211] QF0119 8.1.1.2 12-1R6NUCR 12-1VM565P 8.1.1.1 [21211] QF0120 8.1.1.2 12-1TENCIJ 12-1VGLLFW 8.1.1.1 [21211] QF0121 8.1.1.2 12-1VM5K43 12-1VM585D 8.1.1.1 [21211] QF0122 8.1.1.2 12-OM5V6D 12-1VM8YSH 8.1.1.1 [21211] QF0123 8.1.1.2 12-1PBVORR 12-1VM6VS9 8.1.1.1 [21211] QF0127 8.1.1.2 12-1RRBFQ9 12-1VM9CT7 8.1.1.1 [21211] QF0128 8.1.1.2 12-1U5R7UV 12-1VNJ8VX 8.1.1.1 [21211] QF0129 8.1.1.2 12-1VM6N5D 12-1VM90VR 8.1.1.1 [21211] QF0131 8.1.1.2 12-1V0598R 12-1VR2KEB 8.1.1.1 [21211] QF0136 8.1.1.2 12-1VH3J0H 12-1VR2KGF 8.1.1.1 [21211] QF0136 8.1.1.2 12-1NSKL0N 12-1VABKYK 8.1.1.1 [21211] QF0142 8.1.1.2 12-1TUED13 12-1VR3YEY 8.1.1.1 [21211] QF0142 8.1.1.2 12-1TBLYYA 12-1WCVGL3 8.1.1.1 [21211] QF0147 8.1.1.2 12-1SF7E1F 12-1VR36YB 8.1.1.1 [21211] QF1104 8.1.1.2 12-1OVCU5D 12-1VCQE1C 8.1.1.1 [21211] QF2101 8.1.1.2 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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 31
  • 32. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Quick Fixes Included in8.1.1.x Fix PacksTable 2. Quick Fixes Included in Version 8.1.1.x Change Fix Request Quick Fix Merged Into Request ID ID Fix Pack Base Version Fix Pack 12-1RNH7ER 12-1RNH7G4 8.1.1 [21111] QF0001 8.1.1.1 12-1NLY66Z 12-1R7MK4U 8.1.1 [21111] QF0002 8.1.1.1 12-1KDK35I 12-1RBZBRA 8.1.1 [21111] QF0003 8.1.1.1 12-1S8QNHX 12-1S8QNIW 8.1.1 [21112] QF0004 8.1.1.1 12-1QT7XTB 12-1S20GWP 8.1.1 [21112] QF0005 8.1.1.1 12-1ONVDYP 12-1SGOF1D 8.1.1 [21112] QF0006 8.1.1.1 12-1RKLYHL 12-1RKLYIW 8.1.1 [21112] QF0006 8.1.1.1 12-1S8I5DB 12-1SGOF07 8.1.1 [21112] QF0006 8.1.1.1 12-1RAJ07R 12-1SD932B 8.1.1 [21112] QF0007 8.1.1.1 12-1KPTT57 12-1S4C6VJ 8.1.1 [21112] QF0009 8.1.1.1 12-1M4CI03 12-1M4CI1D 8.1.1 [21112] QF0009 8.1.1.1 12-1PCDF0P 12-1SB8AZ3 8.1.1 [21112] QF0009 8.1.1.1 12-1RPEN89 12-1ROX0RL 8.1.1 [21112] QF0009 8.1.1.1 12-1RVNYWA 12-1RXLAYA 8.1.1 [21112] QF0009 8.1.1.1 12-1SD8MX5 12-1SD8MYF 8.1.1 [21112] QF0009 8.1.1.1 12-1SSU76Z 12-1SSU77O 8.1.1 [21112] QF0009 8.1.1.1 12-1RVNYUP 12-1RVNYW3 8.1.1 [21112] QF0009 8.1.1.1 12-1RZPUA5 12-1S98C5N 8.1.1 [21112] QF0009 8.1.1.1 12-1RZPUB1 12-1S8R2S7 8.1.1 [21112] QF0009 8.1.1.1 12-1SSU75R 12-1SSU76Q 8.1.1 [21112] QF0009 8.1.1.1 12-1P5N6JM 12-1SLLJBD 8.1.1 [21112] QF0011 8.1.1.1 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.132 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 33. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Enhancements and Updates in 8.1.1.x Fix PacksEnhancements and Updates in 8.1.1.xFix PacksThis topic identifies the enhancements and updates provided in version 8.1.1.x releases.Enhancements in 8.1.1.x Fix Pack releases are cumulative. This topic contains the followingsubtopics:■ “Enhancements and Updates in Version 8.1.1.4” on page 33■ “Enhancements and Updates in Version 8.1.1.3” on page 34■ “Enhancements and Updates in Version 8.1.1.2” on page 36■ “Enhancements and Updates in Version 8.1.1.1” on page 37Enhancements and Updates in Version 8.1.1.4Table 3 lists the enhancements and updates provided in version 8.1.1.4.This topic is part of “Enhancements and Updates in 8.1.1.x Fix Packs” on page 33.Table 3. Enhancements and Updates in Version 8.1.1.4 Feature Enhancement or Certification Number Feature Enhancement or Certification Description ACR 475A Enhances UCM to support the Higher Education application. ACR 475B Enhances UCM to provide Data Governance, Data Quality, and usability enhancements. ACR 499 ACR 499 provides the following enhancements to the Bulk Orders functionality: ■ Bulk Promotion Upgrade and disconnect: Customers can apply promotions to products using bulk requests. ■ Bulk Quotes: Customers can create Bulk Quotes. ■ Agreement and Network Child Types in Action Set: Customers can add Network or Agreement Pro ducts in orders or quotesusing Bulk Requests. ■ Account Group Specification: C ustomers 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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 33
  • 34. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Enhancements andUpdates in 8.1.1.x Fix PacksTable 3. Enhancements and Updates in Version 8.1.1.4 Feature Enhancement or Certification Number Feature Enhancement or Certification Description ACR 502 ACR 502 provides the following Siebel Configurator enhancements: ■ The ability to defer an update within a scripting event to allow multiple attribute change even add/set attribute calls. ■ A new scripting event to get product attribute values. ■ The ability to show/hide UI controls based on user properties and the instance variable values.api method. ACR 526 Trade Promotions Management Quickstart ACR 543 Extends the Siebel web services framework to provide an endpoint through Oracle WLS. ACR 623 Intelligent-Offer Generation (IOG) and certification with RTD 3.0 ACR 626 Integration of Mobile Sales Assistant to the Siebel On-Premise application.Enhancements and Updates in Version 8.1.1.3Table 5 lists the enhancements and updates provided in version 8.1.1.3.34 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 35. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Enhancements and Updates in 8.1.1.x Fix PacksThis topic is part of “Enhancements and Updates in 8.1.1.x Fix Packs” on page 33.Table 4. Enhancements and Updates in Version 8.1.1.3 Feature Enhancement or Certification Number Feature Enhancement or Certification Description ACR 426 Adds electronic medical device reporting to the AECM module. ACR 463 ACR 463 provides the following enhancements: Order to Activate Enhancements: ■ Cancel Order header button ■ Cancellation affecting future dated orders: ■ Changes to support order revisions ■ Computing previous values on Submit ■ Dependency on follow-on orders ■ Due Date changes for Disconnect ■ Extending Sales Order EBO ■ Invalidate stale orders ■ Keep customer intent of submitted orders ■ Line item history ■ Non-paying accounts ■ Trouble Ticketing extensions ■ Order Update Business Web Service ■ Product Class/Attribute Sync Web Service ■ Product Import Web Service Product Extensions for O2A: ■ Verify future-dated orders (warning message on header) ■ Warning messages on assets for future-dated orders Order to Bill PIP Enhancements: ■ Support Friends and Family ■ Collections Flow ■ Map CRM discount to billing objects ■ Order validations Billing Management UI enhancements: ■ Adjust unbilled events and child account events ■ Display child account balance in Siebel Billing Management screen. ■ View promotion name on invoice. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 35
  • 36. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Enhancements andUpdates in 8.1.1.x Fix PacksTable 4. Enhancements and Updates in Version 8.1.1.3 Feature Enhancement or Certification Number Feature Enhancement or Certification Description ACR 474 Supports OSM Integration and 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. ACR 500 Enables effective bundling of products necessary in the communications, finance, media, and utilities industries, and enhances promotion capabilities for component-level commitment, eligibility in promotion upgrade, asset- based recommendations, and split/merge capabilities of promotions. ACR 508 Forward-ports the Order to Cash PIP to Siebel version 8.1.1 applications. ACR 529 Provides a single-step upgrade from Siebel Enterprise Applications to Siebel Industry Applications. ACR 539 Modifies the Siebel Clinical product to support the Study, Subject, and Visit Synchronization Process Integration Pack for Siebel Clinical and Oracle Clinical. This enhancement also provides a way to accurately track and respond to issues related to site performance and protocol adherence. ACR 562 ACR 562 extends the functionality previously provided by ACR 422, which was included in the Siebel 8.1.1.1 Fix Pack. ACR 422 provided the following functionality: ■ Added missing text for ALT strings and other text read by screen readers. ■ Added titles for views and applets. ■ Provided announcements of row and column identifiers in list applets and allows the column used for the row identifier to be configurable. ■ Fixed various "loss-of-focus" defects. ■ Fixed various tab-order defects that are most often encountered when users are navigating between applets. ■ Fixed various keyboard-shortcut defects and extends the set of available shortcuts. ■ Added helps topics for accessibility and updates the keyboard shortcuts help topics. ACR 574 Provides Lymba as the Smart Answer Engine.Enhancements and Updates in Version 8.1.1.2Table 6 lists the enhancements and updates provided in version 8.1.1.2.36 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 37. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Enhancements and Updates in 8.1.1.x Fix PacksThis topic is part of “Enhancements and Updates in 8.1.1.x Fix Packs” on page 33.Table 5. Enhancements and Updates in Version 8.1.1.2 Feature Enhancement or Certification Number Feature Enhancement or Certification Description ACR 444 ACR 444 provides the following enhancements: ■ Provides a utility for administrators to act on failing Store-and- Forward transactions. ■ Enhances logging capabilities (server). ACR 457 Provides cross-network validation and cascade delete enhancements for network ordering for Siebel Customer Order Management for SIA. ACR 464 Provides support for CRM Desktop for Outlook. ACR 468B Allows Siebel Client Sync to support Lotus Notes 8.0 and Microsoft Outlook 2007 with Intellisync 7.x SDK. ACR 492 Provides Web service access through the Mobile Web Client to other local desktop applications. ACR 494 Provides Event Check enhancements and BEO Report functionality for the Siebel Travel & Transportation application. ACR 544 Enhances the Siebel Remote utility and allows it to be integrated with the Siebel HA Upgrade solution.Enhancements and Updates in Version 8.1.1.1Table 6 lists the enhancements and updates provided in version 8.1.1.1. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 37
  • 38. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Enhancements andUpdates in 8.1.1.x Fix PacksThis topic is part of “Enhancements and Updates in 8.1.1.x Fix Packs” on page 33.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.38 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 39. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Enhancements and Updates in 8.1.1.x Fix PacksTable 6. Enhancements and Updates in Version 8.1.1.1 Feature Enhancement or Certification Number Feature Enhancement or Certification Description ACR 439 ACR 439 contains the following enhancements for Siebel Search ■ Activates the Advanced Search button only when a search engine has been configured. ■ Converts Saved Searches from an HTML list to a drop-down list. ■ Makes Recent Saved Searches only display when a search engine has been configured. ■ Implements Preview with Search functionality to match the functionality available with Siebel version 7 applications. ACR 439 provides a preview button in the Search results pane (left-pane search). When users click the preview button, the record details appear in a pop-up window. ■ Provides Attach functionality that is based on the parent applet. ACR 439 provides an Attach button in the Search results pane (left-pane search). When users click the Attach button, the record selected in the search pane is attached to the record on the right. For example, users can attach a contact to the opportunity record displayed on the right side of the screen. ■ Corrects a Search Definition dependency for the FIND function. FIND categories can now be defined irrespective of the search engine definition. ACR 450 ACR 450 provides the following enhancements: ■ Menus and Packages ■ Function Space Displays ■ Inventory Display Enhancements ■ Sleeping Room Mapping ACR 452 ACR 452 provides the following Oracle Secure Enterprise Search enhancements: ■ Remote Administration configuration ■ Auto keyword generation ■ Mixed operator search ■ Searching by file format ■ Dynamic weights Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 39
  • 40. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesTable 6. Enhancements and Updates in Version 8.1.1.1 Feature Enhancement or Certification Number Feature Enhancement or Certification Description ACR 456 Allows users to perform Assignment Manager bulk-data maintenance (CRUD on R ules, Positions, candidates and so forth) through client views and screens. ACR 467 Provides Siebel Financial Services Customer Order Management for Banking functionality. ACR 471 Bundles the Promotion and Product class relationship so that changing a promotion in a change order loads the default product. ACR 476 Rebases Siebel Email Response support for Smart Answer support. ACR 480 ACR 480 provides the following enhancements: ■ Resolves key connection gaps between core processes: marketing and trade management, trade management, and retail execution. ■ Provides key functional enhancements needed to fulfill Oracle Trade Management processes. ■ Significantly enhances usability across trade management in Siebel applications. ACR 481 ■ Provides the ability to ignore Outlook appointments/tasks based on the “Private” flag. ■ Addresses an issue where the Outlook Add-in can lock users out of their accounts after the password has been changed on the authenticating agent (such as Active Directory), but the users have not updated their Outlook Add-in passwords. ACR 488 Provides Histories and Futures functionality.Configuration Instructions forEnhancements and UpdatesThis topic contains configuration instructions for some of th enhancements and updates provided in eversion 8.1.1.x releases.NOTE: It is only necessary to perform the configurations in the following section if you want toimplement the ACRs that they are for.40 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 41. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesYou perform the instructions described in the subtopics that follow after y install the current Siebel ouFix Pack 8.1.1.x, as described in “Siebel Fix Pack Installation Instructions” on page 453.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 informationabout activities performed in the Siebel appli ation, see Siebel Applications Administration Guide and crelated 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 42■ “Instructions for ACR 403” on page 42■ “Instructions for ACR 422” on page 46■ “Instructions for ACR 426” on page 67■ “Instructions for ACR 437” on page 90■ “Instructions for ACR 439” on page 91■ “Instructions for ACR 452” on page 96■ “Instructions for ACR 456” on page 98■ “Instructions for ACR 457” on page 100■ “Instructions for ACR 463” on page 104■ “Instructions for ACR 464” on page 143■ “Instructions for ACR 467” on page 151■ “Instructions for ACR 468” on page 158■ “Instructions for ACR 471” on page 160■ “Instructions for ACR 474 and ACR 508” on page 160■ “Instructions for ACR 475” on page 231■ “Instructions for ACR 476” on page 277■ “Instructions for ACR 480” on page 281■ “Instructions for ACR 488” on page 292■ “Instructions for ACR 494” on page 292■ “Instructions for ACR 499” on page 292■ “Instructions for ACR 500” on page 319■ “Instructions for ACR 502” on page 345■ “Instructions for ACR 508” on page 357■ “Instructions for ACR 526” on page 362■ “Instructions for ACR 539” on page 363■ “Instructions for ACR 543” on page 385 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 41
  • 42. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates■ “Instructions for ACR 562” on page 388■ “Instructions for ACR 574” on page 433■ “Instructions for ACR 623” on page 439■ “Instructions for ACR 626” on page 439■ “Instructions for BI Publisher Enhancements” on page 442Instructions for ACR 358For information about how to implement ACR 358, within My Oracle Support, navigate to theKnowledge tab, and search for Doc ID 781368.1Instructions for ACR 403Use the instructions in the following section to configure ACR 403.Preinstallation InstructionsBefore you apply the Siebel 8.1.1.x Fix Pack, the local database needs to be extracted from theServer machine and initialized on the machine where Siebel Mobile Client will be installed.Use the following procedure to extract the local database from the server machine and initialize it onthe machine where the Siebel Mobile client will be installed.To extract the local database and initialize it1 Navigate to the Administration - Siebel Remote screen. a Query for HQ, and select APARKER as mobile client and MOBILE CLIENT - STANDARD as routing model. b Navigate to the Admin istration - 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 Logging2 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 synchmgr42 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 43. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates4 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=APARKER ■ list task <tasked ID> (Keep listing the task until the status changes to "Completed") ■ list advanced param portnumber for comp synchmgrInstallation Instructions1 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 ■ seed_disconn.inp3 Verify that the following files are present under <Siebel Tools loc>TOOLSREPPATCH: ■ discon_symbstring.sif ■ disconnected.sif4 In tools.cfg, make the following changes: SymStrPrefix = SBL_ (instead of X_) DockConnString = <Siebel Server Name>::<Synchmgr port> (For example, sdchs21n467::40400)5 Log into Siebel Tools as APARKER and point to the local database.6 Enter the password for APARKER (such as aparker1-2), click Continue, enter the Server password for APARKER at the prompt, and click Next. Siebel Tools starts initialization of all the tables and parameters for the local database. Once the initialization is done, Siebel Tools will automatically open and will connect to the local database.7 In the Tools ODBC entry, enter the UID/PWD for the local database. (For the local database, UID/ PWD should be DBA/SIEBEL12]8 Enter the encryption Key for the database and check for the database connection. It should show as successful once the UID/PWD and Encryption Key have been entered correctly. TIP: To get the encryption key, navigate to the Administration - Siebel Remote screen, and then the Mobile Clients view. Query for the HQ* and then query for the user APARKER. In the Additional Info column, query for RemLocSec:PlainKey. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 43
  • 44. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates9 Log into Siebel Tools (pointing to the local database). Navigate to Tools, and then Check Out. NOTE: If you receive the "Error connecting to Datasource" error message, then check the data source information. The source should be SSD default instance (UID/Server pwd) and Destination: SSD Local Db default instance.10 Click the Get button to get all the projects. Siebel Tools will get all the projects one by one. This will take two to five hours to complete.11 Open Siebel Tools (connecting to the local database) and lock the following projects one by one by selecting the project and setting the "Locked" flag to "true": ■ Fast Search ■ Service ■ Siebel Universal Agent ■ ERM Admin ■ New Search ■ Siebel Field Service Enterprise ■ Siebel Marketing Enterprise ■ Siebel Sales Enterprise ■ Siebel eChannel ■ Siebel Field Service Enterprise12 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 Definition16 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:44 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 45. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates a Copy the files seed_disconn.dat and seed_disconn.inp files from 4 to the Mobile Client machine (for example, D:FS Build4_Final.) b Navigate to <mobile client install loc>BIN> using the command prompt and run the following command. dataimp /u $USERNAME /p $PASSWORD /c "$Local ODBCDatasource" /f "seed_disconn.dat" /i "seed_disconn.inp" /d $Tableowner /Z Y /l implog.log For example: dataimp /u DBA /p SIEBEL12 /c "SEAW Local Db default instance" /f "D:FS Build4_Final seed_disconn.dat" /i "D:FSBuild4_Finalseed_disconn.inp" /d siebel /Z Y /l implog.log Once dataimp command is do ne, 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 databaseAdding the Mobile Search Administration ScreenYou 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 Centerapplication.To add the Mobile Search Administration screen1 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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 45
  • 46. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates7 Choose Edit, and then New Record, and use the following information to define the object properties: Property Description Screen This should be set to Search Mobile Admin View Screen. Sequence Use Screen View Sequence Editor to determine the sequence of views. Do not edit the Sequence property of the Screen View Object manually. See Configuring Siebel Business Applications for defining Sequence for Screen View Objects. Text - String This should be set to SBL_ADMINISTRATION_-_MOBILE_SEARCH. ReferenceFor more information about installing and configuring the Disconnected Search Module to enableSiebel Mobile Search, see Siebel Search Administration Guide on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.Instructions for ACR 422The following sections contain procedures for making the configuration changes needed in order toimplement ACR 422.For more information about accessibility enhancements, see Accessibility Guide for Siebel BusinessApplications 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 anapplication. 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 application1 Navigate to Object Explorer in Siebel Tools.2 Navigate to View > Options, and click the Object Explorer tab.3 Unselect Application Object, select it again to add all of the child objects to the Object Explorer, and click OK.4 Click Application, and query for the Application Names listed in the following table: New/ Application SIA SIF File HOR SIF File Changed Name User Property Value Name Name Changed Siebel Universal AccessibilityXMLF Accessibility_Callce Accessibility_Callce Accessibility_Callc Agent ileName nter.xml nter_SIA.sif enter_HOR.sif Changed Siebel AccessibilityXMLF Accessibility_eMark Accessibility_eMark Accessibility_eMa eMarketing ileName eting.xml eting_SIA.sif rketing_HOR.sif Changed Siebel eSales AccessibilityXMLF Accessibility_eSales Accessibility_eSale Accessibility_eSal ileName .xml s_SIA.sif es_HOR.sif46 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 47. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates New/ Application SIA SIF File HOR SIF File Changed Name User Property Value Name Name Changed Siebel eService AccessibilityXMLF Accessibility_eServi Accessibility_eServ Accessibility_eSer ileName ce.xml ice_SIA.sif vice_HOR.sif Changed Siebel Public AccessibilityXMLF Accessibility_Public Accessibility_Public Accessibility_Publi Sector ileName Sector.xml Sector_SIA.sif cSector_HOR.sif Changed Siebel Sales AccessibilityXMLF Accessibility_Sales. Accessibility_Sales Accessibility_Sale ileName xml _SIA.sif s_HOR.sif Changed Siebel Service AccessibilityXMLF Accessibility_Servic Accessibility_Servic Accessibility_Serv ileName e.xml e_SIA.sif ice_HOR.sif5 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 MVGUse the following procedure to enable screen readers to read out the MVG and Pick Applet forCalendar, Calculator, and MVG. After these changes have been made, screen readers will read out aCalendar Pick Applet as shown in the following example: Start Date: 25/07/2007 Calendar Icon.To enable screen readers to read out the MVG and Pick Applet for Calendar,Calculator, and MVG (Symbolic Strings)1 Navigate to Object Explorer in Siebel Tools.2 Navigate to View > Options, and click the Object Explorer tab.3 Select the Symbolic Strings Object and click OK to add the Symbolic Strings object to Object Explorer.4 Click on Symbolic Strings and query for Current String Value as Input.5 Lock the object.6 Make the following changes, as detailed in the following table: New/ HOR SIF File Changed Project Name Value SIA SIF File Name Name Changed Symbolic SBL_CALCULATOR_IC Calculator SymbolicStrings_SI SymbolicStrings_H Strings ON_ALT_TXT A.sif OR.sif Changed Symbolic SBL_CALENDAR_ICON Calendar SymbolicStrings_SI SymbolicStrings_H Strings _ALT_TXT A.sif OR.sif Changed Symbolic SBL_EDIT_ICON_ALT_ Pick Applet SymbolicStrings_SI SymbolicStrings_H Strings TXT A.sif OR.sif a For SBL_CALCULATOR_ICON_ALT_TXT, change Current String Value to Calculator. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 47
  • 48. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates b For SBL_CALENDAR_ICON_ALT_TXT, change Current String Value to Calendar. c Save the changes. d In Symbolic Strings, query for Current String Value as Select. e For SBL_EDIT_ICON_ALT_TXT, change Current String Value from Select to Pick Applet. f Save the changes.To enable screen readers to read out the MVG and Pick Applet for Calendar,Calculator, and MVG (Bitmaps)1 Navigate to Object Explorer in Siebel Tools.2 Click on Bitmap Category and query for HTML Control Icons.3 Lock the HTML Control Icons object.4 Navigate to Bitmap (child object) and query for CALENDAR_ ICON and CALCULATOR_ICON.5 Change the Alt Text value to Calendar and Calculator respectively, as shown in the following table: New / Bitmap Alt Text SIA SIF File HOR SIF File Changed Category Bitmap Value Description Name Name Changed HTML CALENDAR_ ICON Calendar Change the HTMLControlIcon HTMLControlIcon Control Alt text from s_SIA.sif s_HOR.sif Icons "Input" to Calendar. Changed HTML CALCULATOR_ICON Calculator Change the HTMLControlIcon HTMLControlIcon Control Alt text from s_SIA.sif s_HOR.sif Icons "Input" to Calculator. Changed HTML ICON_SELECT Pick Change the HTMLControlIcon HTMLControlIcon Control Applet Alt text from s_SIA.sif s_HOR.sif Icons "Select" to Pick Applet.6 Save the changes.7 In HTML Control Icons query for EDIT_ICON and change the Alt Value to Pick Applet as shown , in the preceding table.8 Save the changes.Creating Keyboard Shortcuts for NavigationUse 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.48 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 49. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates3 Select Symbolic Strings Object and click OK to add the Symbolic Strings object to Object Explorer.4 Lock the Symbolic Strings project.5 Right-click and click New Record.6 Add the new records listed in the following table: New/ Current Changed Project Name String Value SIA SIF File Name HOR SIF File Name New Symbolic SBL_CTRL_+_ALT_+_] Ctrl + Alt + ] SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif Strings New Symbolic SBL_CTRL_+_ALT_+_[ Ctrl + Alt + [ SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif Strings New Symbolic SBL_CTRL+SHIFT+B Ctrl+Shift+B symstr_columnsdisplay symstr_columnsdisplaye Strings ed_SIA.sif d_HOR.sif New Symbolic SBL_CTRL+, Ctrl+, SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif Strings New Symbolic SBL_CTRL+. Ctrl+. SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif Strings New Symbolic SBL_ALT_G ALT+G SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif Strings New Symbolic SBL_ALT_U ALT+U SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif Strings New Symbolic SBL_ALT_W ALT+W SymbolicStrings_SIA.sif SymbolicStrings_HOR.sif StringsTable 7 lists some of the keyboard shortcuts available with ACR 422, and the procedures in thesection that follows describe how to add these keyboard shortcuts.Table 7. Keyboard Shortcuts Command Action Accelerator Key Sequence Description SIA SIF File Name NextApplet Next Applet Ctrl + Alt + ] Ctrl+Alt+221 Shifts focus to the CmdNextApplet_SIA.sif first anchor of the next applet PrevApplet Previous Ctrl + Alt + [ Ctrl+Alt+219 Shifts focus to the CmdPreviousApplet_SIA.sif Applet first anchor of the previous applet Refine Query N/A Alt+G Alt+G N/A CmdRefineQuery_SIA.sif (SWE) First Page (SWE) N/A Alt+U Alt+U N/A CmdFirstPageSWE_SIA.sif Last Page (SWE) N/A Alt+W Alt+W N/A CmdLastPageSWE_SIA.sif Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 49
  • 50. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesTable 7. Keyboard Shortcuts Command Action Accelerator Key Sequence Description SIA SIF File Name Columns Displayed N/A Ctrl+Shift+B Ctrl+Shift+B N/A CmdColumnsDisplayed_SIA.sif (SWE) NextApplet Next Applet Ctrl + Alt + ] Ctrl+Alt+221 Shifts focus to the CmdNextApplet_SIA.sif first anchor of the next appletCreating Keyboard Shortcuts for CommandsUse the following procedures to provide keyboard shortcuts for commands.To provide a keyboard shortcut for the NextApplet command1 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 command1 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] command1 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.50 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 51. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates6 In the Key Sequence field, change the value to Alt+G.To provide a keyboard shortcut for the FirstPage command1 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) command1 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 35 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) command1 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 25 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) command1 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+,. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 51
  • 52. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesTo provide a keyboard shortcut for the Next Record (SWE) command1 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 CenterThe following section details the changes that are required for the search applet in order to providea 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 Search1 Navigate to Object Explorer in Siebel Tools.2 Navigate to Applet.3 Query for "Search lookin" and lock it.4 Enter "Search" in the Title field.5 Make sure that the proper Symbolic String has been selected. New / Changed Applet Name Title Description SIA SIF File Name HOR SIF File Name Changed Search lookin Search Provides a title AppletSearchlookin_SIA.sif AppletSearchlookin_HOR.sif to the applet for screen readers to read out.To add the DefaultFocus User Property1 Navigate to Object Explorer in Siebel Tools.2 Navigate to Applet.3 Query for "Search lookin".4 Navigate to Applet User Property.52 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 53. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates5 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 requiresa default focus. New / Applet User SIA SIF File Changed Applet Name Property Value Description Name HOR SIF File Name Changed Search lookin DefaultFocus SearchFor Added the user AppletSearchlo AppletSearchlookin_H property to setthe okin_SIA.sif OR.sif default focusCreating the View Info CommandThe following procedure explains how to create the View Info command.To create the View Info command1 Navigate to Object Explorer in Siebel Tools.2 Navigate to Command and lock the "Command" project.3 Create a New Command named "View Info" with project "Command" as the project, using the values detailed in the following table: ■ NAME="ViewInfo" ■ METHOD="ViewInfo" ■ TARGET="SI Plus" ■ DISPLAY_NAME_-_STRING_REFERENCE="SBL_DOES_NOT_MATTER-1004225828-03I" Key SIA SIF HOR SIF Command Project Action Accelerator Sequence Description File Name File Name View Info Command ViewInfo Ctrl + Alt + Z Ctrl + Alt A new shortcut CmdViewInf CmdViewInf +Z key that o_SIA.sif o_HOR.sif generates a dialog box that contains ViewName, View Summary and Applet Names Sub-View Tab SWE N/A Ctrl + Alt + V Ctrl +Alt N/A CmdSubVie CmdSubVie (SWE SI) +V wTab_SIA.si wTab_HOR.s f if4 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" Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 53
  • 54. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates ❏ KEY_SEQUENCE="Ctrl+Alt+Z"NOTE: Although it is not mandatory, it is important that you enter “Does not matter” as the valuefor 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 SiebelTools.Enabling Screen Readers to Read Out the Check Box “HTML Flag” as HTMLThe following procedure allows screen readers to read out the check box “HTML Flag” as HTML. Bydefault, it reads as Public. To make this change, you can also import theApplet_CommPackageResponse_SIA.sif file. For information about how to import .sif files, see“Importing SIF Files” on page 62.To enable screen readers to read out the check box "HTML Flag" as HTML1 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 box4 Change the control name from "Public" to "HTML Flag".Resolving an Error Generated When Creating New Records Within the Leads ScreenUse the following procedure to resolve an error message that occurs when users are creating newrecords under the Leads screen, so that users are not able to see any case records in the Pick CasesMVG. To make this change, y can also importthe PUBLeadListCaseMvgApplet.sif, PUBLeadsList.sif, ouPUBLeadsListApplet.sif, and CaseMvg.sif files. For information about how to import .sif files, see“Importing SIF Files” on page 62.To resolve an error message generated in the Leads screen1 Open Siebel Tools, and navigate to the "PUB Lead List Case Mvg Applet" applet.54 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 55. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates2 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 UsersThe following procedure makes the help system accessible for screen-reader users. It adds a topicto the Siebel iHelp system that describes accessibility features and how to use them, and it alsoensures that the iHelp system is available on each home page of the Siebel application. To makethese 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 abouthow to import .sif files, see “Importing SIF Files” on page 62.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 AppletsThe following changes need to be made for Gener ting HTML SUMMARY attributes for all list applets. aThe default tag text should be set to the applet header name. Add TITLE or LABEL for each tableentry (all HTML form elements). Row and column headers must be identified as required by OGHAGTABLE-1 and TABLE-2. Adding a row title for each row in data table (Suggestion: this could be thefirst displayed data column in the applet display. Ideally the customer can select which column canbe 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. Thefirst 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 apple The "RowId" t.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 firstcolumn for the list applet. The newly-selected column will become the rowid. Lock the particularapplet that needs to be changed. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 55
  • 56. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesProviding a New Key Combination for the Next and Previous Record CommandsTo provide key combinations for Next Record and Previous RecordNOTE: The tables that follow this procedure provide more information about the fields that you willbe changing.1 Navigate to Object Explorer in Siebel Tools.2 Navigate to View > Options, and click the Object Explorer tab.3 Select the Command object and click OK 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. Current New/ String Changed Project Name Value HOR SIF File Name SIA SIF File Name New Symbolic Strings SBL_ALT+, Alt+, symbolistring_Next_Prev_H symbolistring_Next_Prev_S OR.sif IA.sif New Symbolic Strings SBL_ALTL+. Alt+. symbolistring_Next_Prev_H symbolistring_Next_Prev_S OR.sif IA.sif Command Project Accelerator Key Sequence SIA SIF File Name HOR SIF File Name Next Record(SWE) Command Alt +. Alt+0xBE Next_Prev_SIA.sif Next_Prev_HOR.sif Previous Command Alt +, Alt+0xBC Next_Prev_HOR.sif Next_Prev_HOR.sif Record(SWE)56 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 57. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesProviding Alt Text for BulletsIn Recent Records, the bullets need to have alt text provided. To make this change, import theorangebullet_HOR or orangebullet_SIA.sif files as detailed in the following table. For informationabout how to import .sif files, see “Importing SIF Files” on page 62. New/ Current String Changed Project Name Value HOR SIF File Name SIA SIF File Name Changed Symbolic SBL__IMG_SRC__IMAGES/ <IMG orangebullet_HOR.sif orangebullet_SIA.sif Strings CHEVRON_SM.GIF__ALIGN SRC="images/ __RIGHT__BORDER__0 orange_bullet.gif" align="right" border="0" alt="" >Enabling or Disabling the Confirmation Message on Page RefreshThe procedure in the following section describes how to enable or disable the confirmation messageupon page refresh. To make this change, you can also import .sif files. To do so, importConfirmationMessage_SIA.sif and ConfirmationMessage_HOR.sif. For symbolic strings, importsymstr_confirmationmessage_SIA.sif and symstr_confirmationmessage_HOR.sif. For informationabout how to import .sif files, see “Importing SIF Files” on page 62. New/Changed Project Value Description New Symbolic Strings Accessibility Create a new Symbolic String for Accessibility Project for the "Confirmation Message" User Preference New Symbolic Strings Confirmation Create a new string for the Control MessageTo enable or disable the confirmation message upon page refresh1 Log into the application using /editseeddata (for thick client) for the local database or dedicated database (for the master database, the Add button is enabled by default).2 Navigate to Administration - Data > List Of Values Explorer, and add the new LOV types mentioned in the following table: Language Display Independent Type Value Translate Multilingual Code Order Language Name SWE_CONFIRMATION TRUE Yes Yes TRUE 1 English-American _MESSAGE SWE_CONFIRMATION FALSE Yes Yes FALSE 2 N/A _MESSAGE Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 57
  • 58. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates3 After you have added these changes, navigate to Screen > System Administration > List Of Values to view these changes in the repository. New/ Business Changed Name Project Component Static Type Field Type Value New Confirmation User Preference PickList Generic Yes Type SWE_CONFIRM_MESSAGE Message PicklistThe following changes have been made to the User Preferences Business Component. Name PickList Predefault Value Type SWE/Confirmation Message Confirmation Message TRUE DTYPE_TEXT PicklistThe following table describes the new User Profile Confirmation Message Parameter Applet that hasbeen added to support ACR 422. New/ Business Changed Name Project Component Class Title New User Profile User User Preferences CSSFrameBase Accessibility Confirmation Message Preferences Parameter AppletThe following table describes the applet controls changes that have been implemented to supportACR 422. Name Caption Field HTML Type Method Invoked Runtime Field Type Applet Title Accessibility N/A Text N/A N/A N/A ConfirmMssg Confirmation SWE/ Text N/A Yes BC Field Message Confirmation Message ExecuteQuery Go N/A MiniButtonQuery ExecuteQuery N/A N/A NewQuery Query N/A MiniButtonEdit NewQuery N/A N/A QueryAssistan Query N/A MiniButtonQuery ShowQueryAssistant N/A N/A t Assistant ResetRecord Reset N/A MiniButton ResetRecord N/A N/A SaveEditRecor Save N/A MiniButtonEditNe ExplicitWriteRecord N/A N/A d w UndoQuery Cancel N/A MiniButtonQuery UndoQuery N/A N/A WebEditTitle Accessibility N/A Label N/A N/A N/A58 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 59. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesThe following table describes the view changes that have been added to support ACR 422. Visibility Applet New/Changed Name Project Business Object Type New User Profile User Preferences User Preferences User Profile Confirmation Message Confirmation Message Parameter View Parameter AppletThe following table describes the User Profile screen changes that have been added to support ACR422. New/Changed Name View Type Visibility Applet Type New User Profile User Profile Aggregate View User Profile Confirmation Confirmation Message Confirmation Message Message Parameter Applet Parameter View Parameter ViewResolving an Error Message Within Under Diseases > Cases 3LNVUsers are receiving error messages while creating new records under Diseases > Cases 3LNV. Thisis specific to SIA.Use the following procedure to resolve this issue.To resolve an error message within Cases 3NLNV1 Add the Edit template to PUB Disease Case List Applet.2 Make sure that the Execute Query, WriteRecord, UndoQuery, UndoRecord, and Query Assistant controls are present on the applet template. NOTE: Edit template uses Applet List Edit (Edit/New/Query) as the web template. Web New/Changed Name Project Template SIF File New PUB Disease PUB HLS Bio Edit Disease_Case_SIA.sif Case List Applet TerrorismResolving an Error Where Commands Are Executed Before Users Click EnterUsers are encountering an issue where before they click Enter on a menu item in the Show dialogbox, the command is executed.To resolve an error in which commands are executed before users click Enter in theShow dialog box1 Navigate to Object Explorer in Siebel Tools.2 Navigate to View > Options, and click the Object Explorer tab. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 59
  • 60. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates3 Select the Symbolic Strings Object and click OK to add the Symbolic Strings object to Object Explorer.4 Lock the Symbolic Strings project.5 Right-click and select New Record.6 Add the new records mentioned in the following table. New/Changed Project Name Value New Symbolic Strings SBL_ALT+CTRL+Y Alt+Ctrl+Y New Symbolic Strings SBL_ALT+CTRL+L Alt+Ctrl+LTo implement the NextPage and PreviousPage commands1 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: 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 Page9 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.60 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 61. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesResolving an Error Encountered While Creating a New Record in the Identities Form AppletThe information in the following section resolves an issue where users encounter a problem withinthe Immigration contacts screen > Identities view when they try to create a new record under theIdentities form applet. To make this change, you can follow the procedure below, or you can importthe PublicSector_Controls.sif file. For information about how to import .sif files, see “Importing SIFFiles” on page 62.To resolve this error message, change the HTML Type property of the DeleteRecord control fromMiniButton to MiniButtonEdit for the PUB Immigration Identity Form Applet, the PUB Lead FormApplet, 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 foreach applet as a reference point.■ Applet: PUB Immigration Identity Form Applet■ Template: E dit■ Additions: UndoRecord and WriteRecord controls■ Applet: PUB Lead Form Applet■ Template: E dit■ 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: E dit■ Additions: WriteRecord control.■ Applet: HLS Medication Form Applet■ Template: E ditNOTE: 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 forthese applets, because they are also used by the FINS application.Resolving an Issue Where Users Are Unable to Query for Evidence Parent InformationThe following procedure resolves a problem where under Evidence screen> Evidence parent, usersare unable to query for User Parent, and they receive an error message. To make this change, youcan also import the PublicEvidencePickApplet_SIA.sif file. For information about how to import .siffiles, see “Importing SIF Files” on page 62.Add Popup Query template to the PUB Evidence Pick Applet with appropriate controls[ExecuteQuery and CancelQuery] placed on it. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 61
  • 62. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesImporting SIF FilesThe following procedure describes how to import .sif files.To import SIF files1 Lock the particular object /project that needs to be changed.2 Navigate to Tools > Import from Archive and select the related .sif file3 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 orCustomized AppletsThe following sections contain configuration changes that you must make to add the applet summaryfor new or customized applets. You must import .sif files for table changes, apply the DLL, importseed data, and import the Accessibility Project .sif files. The necessary changes are detailed in thefollowing sections:■ Importing SIF Files for Table Changes■ Applying the DDL■ Importing Seed Data■ Importing the Accessibility Project SIF FilesImporting SIF Files for Table ChangesThe procedure in the following section describes how to add the applet summary for customized ornew applets.To import the SIF file for table changes1 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.txt62 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 63. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesApplying the DDLThe procedure in the following section describes how to apply the DDL.To apply the DDL1 Select the table or tables you want to apply to the physical database and press Apply/DDL button (option > Apply).2 For a single table, select the current row option in Tables (Apply Schema Window).3 For more than one table, select the Choose Current Query option.4 For the Accessibility project, select the S_ACC_VIEW_APPL table and current row option.5 Make the following changes depending upon which database you are using: a For MSSQL, enter the database users, the database user password, and the correct ODBC data source. b For Oracle, enter the table space, the index space, the database user, the database user password, and the correct ODBC data source. c For IBM DB2, enter the table space, the 16K table space, the 32K table space, the index space, the database users, the database user password, and the correct ODBC data source.6 After entering in the database information, click the Apply button.7 Verify that the required changes have been applied by selecting count(*) from S_ACC_VIEW_APPL. The query should result in 0 records.Importing Seed DataThe procedure in the following section describes how to import seed data.To import seed data1 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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 63
  • 64. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates3 When prompted for the table name, enter S_ACC_VIEW_APPL.4 Check the log files for any errors, and check S_ACC_VIEW_APPL for the data imported.Importing the Accessibility Project SIF FilesThe following section describes how to import the Accessibility Project .sif files.To import the .sif files provided for ACR 4221 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 66.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 66.4 Add the following new LOV types and values: Type Value ACC_ATTRIB_TYPE Summary ACC_ATTRIB_TYPE Label ACC_LOCALE ENU5 Add the following views to the application and associate responsibility:■ Accessibility Applet Attributes View■ Accessibility View Attributes View6 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.64 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 65. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ❏ The following step applies only to the MSSQL database: After the following lines in app_tree.pl script: #Connect to DB ################################################# $dbh = DBI->connect("dbi:ODBC:$ODBCConnection", $userid, $passwd) || die $DBI::errstr; ################################################# Add the line $dbh->{odbc_SQL_ROWSET_SIZE} = 2; Execute the script with the following command: SYNTAX: perl genAccessibilityXML.pl "<Application Name>" <LOCALE_CODE> <CONNECTSTRING/TABLEOWNER> <USERID> <PASSWD> _________________________________________________________________________ ____ c Once the script is run an xml file will be generated, copy this xml in the following location: 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 AppletsYou 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 AccessibilityApplet 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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 65
  • 66. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates7 Drag and drop the GotoPreviousSet and GotoNextSet controls to their respective placeholders, and edit the properties using the values in the following table: Control Property Value GotoPreviousSet HTMLBitmap RECNAV_PREVSET_ON GotoPreviousSet HTML Disabled Bitmap RECNAV_PREVSET_OFF GotoNextSet HTML Bitmap RECNAV_PREVSET_ON GotoNextSet HTML Disabled Bitmap RECNAV_PREVSET_OFF8 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 422This section contains the list of changes to the .sif files provided for ACR 422.AccProject.sifThe AccProject.sif file contains the following new objects:Business Components:■ Accessibility Applet Attributes■ Accessibility View AttributesApplets:■ Accessibility Applet Attributes List Applet■ Accessibility Applet Attributes Form AppletBusiness Objects:■ Accessibility Applet Attributes■ Accessibility View AttributesViews:■ Accessibility Applet Attributes View■ Accessibility View Attributes ViewPicklists:■ Accessibility Applet Attribute PickList■ Accessibility View Attribute PickList66 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 67. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates■ Accessibility Locale PickListSymbolic Strings:■ Accessibility■ Applet Attributes■ Attribute Type■ View AttributesAdminScreen.sifThe AdminScreen.sif file contains the following changes:■ Accessibility Attributes (new category)■ Accessibility Applet Attributes View (new view)■ Accessibility View Attributes View (new view)Instructions for ACR 426This topic contains information about how to configure and install ACR 426.Preinstallation TasksBefore you begin your installation, change a parameter in tools.cfg file within Siebel Tools(Original: SymStrPrefix = X_) to SymStrPrefix = SBL_Repository Configurations1 Navigate to REPPATCH ACR426RepSeedFiles_v8113.zip and unzip to any location accessible by Siebel Tools.2 In Siebel Tools, lock the following projects: ❏ LS Medical Product Issue ❏ LS Medical Product Issue (SSE) ❏ Contact ❏ Audit Trail ❏ Table ProductComplaints ❏ LS Medical Report ❏ Product ❏ Symbolic Strings ❏ Bitmap Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 67
  • 68. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates ❏ EIM ProductComplaintsApplying Schema ChangesAs part of the ACR426 release, schema changes have been done on the database. TheUnziplocationACR426RepositoryTableBaseTables.sif file has all the changes for the following:ACR 426 contains changes to the following existing table:■ S_PRD_CMPLNT_LSACR 426 contains the following new table:■ S_EMDR_BATCHUse the following procedure to import tables.To import the Tables.sif file into the repository1 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 ChangesAs part of the ACR426 release, EIM changes have been performed on the database. TheUnziplocationACR426RepositoryTableEIMEIMTables.sif has all the changes for the following:EIMTables.sif contains the following new EIM table:■ EIM_EMDR_BATCHEIMTables.sif contains changes to the following existing table:■ EIM_PRD_CMP_LSUse the following procedure to import the EIMTables.sif file into the repository.To import the EIMTables.sif file into the repository1 Lock the EIM ProductComplaints project.2 Use the Import from Archive function within Siebel Tools to read this file and create the tables in the repository. Use the merge option while importing this file.3 Within Siebel tools, query for the list of tables that were imported into the repository.4 Click the Apply/DLL button to apply the changes to the physical database.Use the following procedure to import all of the SIF files.68 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 69. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesTo import all of the SIF filesNOTE: Use this option if you want Siebel Tools to merge the changes for all the existing componentsas well. However, if you have performed customizations, some user properties may clash.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 mported successfully, and reimport all of the objects that i 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 followingprocedure if you want to perform manually configure the existing objects.To import the SIF files manually1 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■ 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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 69
  • 70. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates■ 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■ Import UnziplocationACR426REPOSITORYViewLS Medical My Product Issues RR eMDR Report Attachment View.sif■ Import UnziplocationACR426REPOSITORYViewLS Medical My Product Issues RR eMDR Report Audit View.sif70 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 71. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates2 Manually add the following symbolic strings: Screen View New/ Current String Modified? Name Value Definition New SBL_LS_BATCH_# Batch # Batch # New SBL_LS_BATCH_AUDIT Batch Audit Batch Audit New SBL_LS_BATCH_DETAILS Batch Details Batch Details New SBL_LS_EMDR eMDR EMDR New SBL_LS_EMDR_BATCH eMDR Batch eMDR Batch New SBL_LS_EMDR_QUEUE eMDR Queue eMDR Queue New SBL_LS_EMDR_STATUS Transmission Status Transmission Status New SBL_LS_EMDR_SUB_STATUS eMDR Status eMDR Status New SBL_LS_FDA_STATUS FDA Status FDA Status New SBL_LS_INDIVIDUAL_TRANSMIT Individual Transmit Individual Transmit New SBL_LS_NOT_SELECTED Not Selected Not Selected New SBL_LS_REPORT_ATTACHMENTS Report Attachments Report Attachments New SBL_LS_REPORT_AUDIT Report Audit Report Audit New SBL_LS_TRANSMIT Transmit Transmit Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 71
  • 72. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates3 Do manual configuration for the existing "LS Medical Product Issue RR" Business Component: Single Value Fields New/Needs Calculate Immediate No Modification? Name Join Column d Value Type Post PickList Validation Copy New Area LIC LookupNa DTYPE_TEXT me("SR_A REA", [Area]) New Attach IIf DTYPE_BOOL (Count(At tachment) > 0, 1, 0) New Batch Id BATCH_I DTYPE_ID D New Batch eMDR BATCH_ DTYPE_TEXT Y LS Medical Number Batch NUMBER Picklist Product Issue eMDR Batch RR New FDA FDA_AC DTYPE_TEXT Y LS Medical Acknowl KNOWLE Picklist edgeme DGE_CD Product nt Issue eMDR Acknowled gement RR Modify Device >0 Age Modify Follow- Y Up Number New Follow- IIF ([Sub DTYPE_BOOL Y Up Report Number Type] = Read LookupVal Only ue("LS_M ED_CMPL NT_SUB_ REPORT_T YPE","Foll ow-up"), "N", "Y") New Individu IIf ([Batch DTYPE_BOOL al Number] Transmit IS NULL, 1, 0) Modify Parent Y Product Issue Report Num New Patient LookupNa DTYPE_TEXT Sex LIC me("FIN_ GENDER", [Patient Sex])72 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 73. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates Single Value Fields New/Needs Calculate Immediate No Modification? Name Join Column d Value Type Post PickList Validation Copy New Reopen [Status]= DTYPE_TEXT Flag LookupVal ue("LS_M ED_PI_ST ATUS_TYP E","Closed ") OR [Status]= LookupVal ue("LS_M ED_PI_ST ATUS_TYP E","Revie w Complete" ) Modify Report Y Number Modify Sub Y Report Type Modify Type o f Y Report - Follow- up Flag New Urgency IIF ( DTYPE_TEXT Flag [eMDR Status] = Transmitt ed AND [eMDR SubStatus ] <> Rejected , Green, IIF( (Today() + SystemPr eference(" eMDR Deadline Threshold Value")) < [Report Deadline Date], Yellow, Red)) New eMDR EMDR_S DTYPE_TEXT Y LS Medical Status TATUS_C Picklist D Product Issue eMDR Status RR New eMDR EMDR_S DTYPE_TEXT Y LS Medical SubStat UB_STAT Picklist us US_CD Product Issue eMDR SubStatus RR Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 73
  • 74. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates Pick Maps for the Batch Number Field New/Modified? Field Picklist Field New Batch Id Id New Batch Number Batch Number Pick Maps for the FDA Acknowledgement Field New/Modified? Field Picklist Field New FDA Acknowledgement Value Pick Maps for the eMDR Status Field New/Modified? Field Picklist Field New eMDR Status Value Pick Maps for the eMDR Substatus Field New/Modified? Field Picklist Field New eMDR SubStatus Value Join New/Needs Modification? Table Alias Outer Join Flag New S_EMDR_BATCH eMDR Batch Yes Join Specification for eMDR Batch New/Needs Modification? Name Source Field Destination Column New Join Batch Id ROW_ID Multi Value Link Destination Use New/Needs Business Primary Modification? Name Auto Primary Component Destination Link Join New Attachment Default LS Medical LS Medical Product Issue RR/ Y Product Issue LS Medical Product Issue Attachment Attachment74 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 75. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates Business Component User Properties New/Modified? Name Value Inactive New Field Read Only Field: Follow-Up Number Read Only N Follow-Up Number New Named Method 8 "EscalatePIToeMDRQueue", "SET", "N "RR Sub-Status", "LookupValue(LS_MED_RR_STATUS _CD, eMDR) New Named Method 9 "Transmit", "INVOKESVC", "LS "N Medical Product Issue RR", "Workflow Process Manager", "RunProcess", "ProcessName", "LS CRMIntegSEBLSIAProductIssueInser tOutboundFlow", "RowId", "[Id] New Named Method 10 "Transmit", "SET", "eMDR Status", "N "LookupValue(LS_MED_RR_TRANS_ STATUS, TRANSMITTED) New Named Method 11 "Transmit", "SET", "eMDR "N SubStatus", "LookupValue(LS_MED_RR_TRANS_ SUB_STATUS, NO RESPONSE) New Named Method 12 "UpdateeMDRStatus", "SET", "eMDR "N Status", "LookupValue(LS_MED_RR_TRANS_ STATUS, TRANSMITTED) New Named Method 13 "UpdateeMDRStatus", "SET", "eMDR "N SubStatus", "LookupValue(LS_MED_RR_TRANS_ SUB_STATUS, NO RESPONSE) New Named Method 14 "EscalatePIToeMDRQueue", "SET", "N "eMDR Status", "IIf ([eMDR Status] IS NULL, LookupValue(LS_MED_RR_TRANS_ STATUS, NOT TRANSMITTED), [eMDR Status]) New Named Method 15 "EscalatePIToeMDRQueue", "SET", "N "eMDR SubStatus", "IIf ([eMDR SubStatus] IS NULL, LookupValue(LS_MED_RR_TRANS_ SUB_STATUS, WORK IN PROGRESS), [eMDR SubStatus]) Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 75
  • 76. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates Business Component User Properties New/Modified? Name Value Inactive New Named Method 16 "Transmit", "SET", "FDA """"N Acknowledgement", New Named Method 17 "UpdateeMDRStatus", "SET", "FDA """"N Acknowledgement", New On Field Update Set 3 "Sub Report Type", "Follow-Up "N Number Read Only", "IIF ([Sub Report Type] = LookupValue(""LS_MED_CMPLNT_S UB_REPORT_TYPE"",""Follow-up""), ""N"", ""Y"") New On Field Update Set 4 "Sub Report Type", "Follow-Up "N Number", "IIF ([Sub Report Type] = LookupValue(""LS_MED_CMPLNT_S UB_REPORT_TYPE"",""Initial""), """", [Follow-Up Number]) New On Field Update Set 5 "Type of Report - Follow-up Flag", "N "Sub Report Type", "IIF ([Type of Report - Follow-up Flag]=Y, LookupValue(LS_MED_CMPLNT_SU B_REPORT_TYPE,Follow-up), LookupValue(LS_MED_CMPLNT_SU B_REPORT_TYPE,Initial)) New Status Locked Field 6 "eMDR Status", ""N New Status Locked Field 7 "eMDR SubStatus", ""N New Status Locked Field 8 "FDA Acknowledgement", ""N Modify Status Locked Field 2 "RR Status", "Submitted "N76 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 77. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates4 Perform manual configuration for the "LS Medical Product Issue" Business Component: Single Value Fields New/ Needs Calcul Modific ated Immediate Validati ation? Name Join Column Value Type Post PickList on No Copy New Area Lookup DTYPE_TEXT LIC Name(" SR_ARE A", [Area]) Modify FDA Y Reporta ble New Patient Lookup DTYPE_TEXT Sex LIC Name(" FIN_GE NDER", [Patient Sex]) New Sub- Lookup DTYPE_TEXT Area Name(" LIC SR_ARE A", [Sub- Area])5 Perform manual configuration for the existing "Contact" Business Component. Single Value Fields New/ Imm Needs edia Modificat Joi Colu Calculated te ion? Name n mn Value Type Post PickList Validation No Copy New Country LookupName( DTYPE_ LIC "COUNTRY",[ TEXT Country]) Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 77
  • 78. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates6 Perform manual configuration for the existing "LS Medical Product Issue RR" Business Object: Business Object Component New/Modified? Business Component Link New Contact LS Medical Product Issue RR/ Contact New LS Medical Product Issue RR LS Medical Product Issue RR/ eMDR Batch LS Medical Product Issue RR eMDR Batch7 Perform manual configuration for the existing "Audit Trail Engine" Business Service: Business Service User Props New/Needs Modification? Name Value Comment Modify Enable TRUE 12-CBU9V3: turned OFF on default for performance reasons8 Perform manual configuration for the existing "Field Value Icons" Bitmap Category: Bitmaps Alt Text String New/Modified? Name FileName Reference Alt Text New uncheck.gif uncheck.gif SBL_LS_NOT_SE Not Selected LECTED78 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 79. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates9 Perform manual configuration for the existing "LS Medical Product Issue RR F rm Applet" Applet: o Control New/ HTML Modified? Name Caption Caption String HTML Type Only New/Modify Name Caption Caption String HTML Type HTML Method Only Invoked New eMDRQueue eMDR Queue SBL_LS_EMDR_ MiniButtonEditN Y EscalatePIToeM QUEUE ew DRQueue Applet Web Template (Existing and Modify) Name Type Web Template Modify Edit Edit Applet Form Grid Layout Applet Web Template Items New/Needs Modification? Name Control Comments New eMDRQueue eMDRQueue In Edit Web Layout, drag and drop this control from Controls/ Columns onto the layout Applet User Properties New/Needs Modification Name Value New CanInvokeMethod: ([RR Sub-Status] <> eMDR EscalatePIToeMDRQueue OR [RR Sub-Status] IS NULL) AND [RR Status] = Submitted Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 79
  • 80. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates10 Perform manual configuration for the existing "LS Medical Product Issue RR Child List Applet" Applet: List Columns Display Name - New/Needs String Modification Name Field Reference Read Only HTML Icon Map New FDA Status FDA SBL_LS_FDA_ST Y Acknowledgeme ATUS nt New Flag Urgency Flag SBL_FLAG- LS_URGENCY_FLAG 1004224902- 05I New eMDR Status eMDR Status SBL_LS_EMDR_ Y STATUS New eMDR SubStatus eMDR SubStatus SBL_LS_EMDR_ Y SUB_STATUS Applet Web Template (Existing and Modify) New/Modify Name Type Web Template Modify Edit List Edit List Applet List (Base/ EditList) Applet Web Template Items New/Modify Name Fields Comments New FDA Status FDA Status In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout New Flag Flag In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout80 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 81. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates Applet Web Template Items New/Modify Name Fields Comments New eMDR Status eMDR Status In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout New eMDR SubStatus eMDR SubStatus In Edit Web Layout, drag and drop this List Column from Controls/Columns onto the layout11 Perform manual configuration for the existing "LS Medical Product Issues RR Screen" Screen: Screen View New/ Needs View Bar Text - Modificat Category Parent String Menu Text String ion? Name Name View Type Category Reference Reference New LS LS Detail eMDR SBL_LS_BATCH_ SBL_LS_BATCH_AUDIT Medical Medical View Batch AUDIT My My Product Produc Issues RR t eMDR Issues Batch RR Audit eMDR View Batch Audit View New LS LS Detail eMDR SBL_LS_BATCH_ SBL_LS_BATCH_DETAIL Medical Medical View Batch DETAILS S My My Product Produc Issues RR t eMDR Issues Batch RR Details eMDR View Batch Details View Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 81
  • 82. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates Screen View New/ Needs View Bar Text - Modificat Category Parent String Menu Text String ion? Name Name View Type Category Reference Reference New LS LS Detail eMDR SBL_LS_REPORT SBL_LS_REPORT_ATTAC Medical Medical View _ATTACHMENTS HMENTS My My Product Produc Issues RR t eMDR Issues Report RR Attachme eMDR nt View Report Attach ment View New eMDR eMDR Aggregate SBL_LS_EMDR SBL_LS_EMDR Category New eMDR eMDR Aggregate SBL_LS_EMDR_B SBL_LS_EMDR_BATCH Batch Batch Category ATCH12 In Siebel Tools, compile all of the locked and updated projects.Importing Seed Data1 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.82 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 83. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates3 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 language seed-data import. Use either Step 5 or Step 6 depending upon the language that you are installing.5 Use the following procedure to import ENU language seed data: a Run the following command after importing the ACR426_Seed.dat file. <Tools Install Directory>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 successfully6 Use the following procedure to import languages other than ENU: Run the following command after importing ACR426_Seed.dat file for importing the locale specific ACR426_Seed_Locale_XXX.dat, where XXX is the language code. <Tools Install Directory>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 <Tools Install Directory> - Replace with your Siebel Tools install directory <ODBC Source Name> - Replace with the relevant ODBC name7 Review the <Tools Install Directory>tempdataimp_seed.log file to make sure that the import completed successfully. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 83
  • 84. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesImporting Web Services DefinitionsUse the following procedure to import Web services definitions.To import Web services definitions1 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.) XML File to Import Web Service Name Direction LSeMDRTransmitFDS.xml LSeMDRTransmitFDA Outbound4 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.) XML File to Import Web Service Name Direction LSUpdateeMDRProductIssueS LSUpdateeMDRProductIssueS Inbound tatus.XML tatus9 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.xmlImporting Workflow DefinitionsUse the following procedure to import workflow definitions.84 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 85. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesTo import workflow definitions1 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. XML File to Import Workflow Name Project LS LS LS eMDR CRMIntegSEBLSIAProductIssueInsertOut CRMIntegSEBLSIAProductIssueIns boundFlow.xml ertOutboundFlow LS Siebel PI eMDR Batch.xml LS Siebel PI eMDR Batch LS eMDR5 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 DefinitionsUse the following procedure to activate workflow definitions.To activate workflow definitions1 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 PreferencesUse the following procedure to add system preferences.To add system preferences1 In the Site Map, navigate to Application Administration > System Preferences.2 Create a new record with the following details: Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 85
  • 86. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates ❏ System Preference Name: eMDR Deadline Threshold Value ❏ System Preference Value: 7 ❏ Description: The value is the number of days before the regulatory report deadline, and the system should highlight this value for the users. The urgency is indicated by having the urgency flag in the eMDR list turn from yellow to red.Enabling Component Groups■ Make sure that EAI Component Group is enabled. If it is not, enable it and bounce the Siebel Server.BPEL (Middle Tier) SetupThe procedures in the following section describe how to install Fusion Middleware software and howto 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 thefollowing transformation XSL:UnziplocationACR426BusinessProcessesRegulatoryReportLSeMDRTransmitFDAbpelFDAAcceptanceFormat.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 eMDRUpdateFDAAckbpelsample1.xsd) is used to capture data from BPEL console and the same is transformed to siebelschema using following XSL UnziplocationACR426BusinessProcessesRegulatoryReporteMDRUpdateFDAAckbpelTransformation_1.xsl.The Web service supports the same schema for all the three acknowledgements. Customization isrequired to transform the MDN message received from FDA for the first two acknowledgements toThe Siebel schema and call the Web service.Installing Fusion Middleware SoftwareUse 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.86 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 87. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ■ Oracle JDeveloper 10.1.3.1 (Studio Version) If desired, support for JDeveloper can be purchased separately. For information on installing Oracle JDeveloper, refer to OTN at http://www.oracle.com/technology/documentation/ index.html.Setting Up Canonical ObjectsCanonical 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 objects1 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 ProcessesUse the following procedure to configure BPEL processes.To configure BPEL processes1 Open the following file for editing: UnziplocationACR426SetUpCRMIntegProcessParameters.xml. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 87
  • 88. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates2 Modify its content until it matches the following: NOTE: Change the values in the lines that begin with "<property name="PARAMVALUE">. Replace the values with the relevant values from your environment. <?xml version="1.0" encoding="UTF-8" ?> <LISTOFBUILDPARAMETERS xmlns="http://www.siebel.com/uan/SiebelBIAs/ SharedComponents/CRMIntegProcessProperties"> <BUILDPARAMETER> <property name="PARAMNAME">http://sdc78212svod:8888/orabpel/default</property> <property name="PARAMVALUE">http://127.0.0.1:8888/orabpel/default</property> <property name="DESC">This Parameter is to capture BPEL domain URL information.Please specify your environment specific value for "PARAMVALUE" property. Here "http://127.0.0.1:8888" should be replaced with the HOST, PORT where the BPEL PM is running. "orabpel" should stay same. "default" is the name of domain where the bpel processes are to be deployed.</property> </BUILDPARAMETER> <BUILDPARAMETER> <property name="PARAMNAME">http://sdc78212svod:8888/orabpel/xmllib</property> <property name="PARAMVALUE">http://127.0.0.1:8888/orabpel/xmllib</property> <property name="DESC">This Parameter is to capture the XMLLIB url. Please specify your environment specific value for "PARAMVALUE" property. Here "http://127.0.0.1:8888" should be replaced with the HOST PORT where the BPEL PM is , running. "orabpel/xmllib" should stay same.</property> </BUILDPARAMETER> <BUILDPARAMETER> <property name="PARAMNAME">"http://sdc78212svod/eai_enu/ start.swe?SWEExtSource=WebService;SWEExtCmd=Execute;UserName=harikuma;Passwor d=harikuma"</property> <property name="PARAMVALUE">[SIEBEL SERVER LOCATION]</property> <property name="DESC">This Parameter is to capture the Siebel server url. Specify your environment-specific value for "PARAMVALUE" property (such as http:// xyz.siebel.com:8888</property> </BUILDPARAMETER> <BUILDPARAMETER> <property name="PARAMNAME">"c:temp"</property> <property name="PARAMVALUE">"c:test"</property>88 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 89. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates <property name="DESC">Ouput Directory where FDA eMDR XML files will be created </ property> </BUILDPARAMETER> </LISTOFBUILDPARAMETERS>3 After you have changed the parameter values, navigate to 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:tempUse 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 files1 Navigate to UnziplocationACR426BusinessProcesses RegulatoryReportLSeMDRTransmitFDAbpel, and edit WriteIntoFile.wsdl.2 Locate "PhysicalDirectory="c:temp"", and replace the value to the relevant value3 Locate "FileNamingConvention="FDAReport.xml"" and replace the value to relevant value, such as FDA_%yyMMddHHmmss%.xml.Setting Up an Application WorkspaceUse the following procedure to set up an application workspace.To set up an application workspace1 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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 89
  • 90. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates c Select a JPR file and click Open. This imports the process code into the application.Deploying Business Process Execution LanguageUse the following procedure to deploy BPEL processes.NOTE: Before you begin, make sure that the SOA Suite has been installed, and make sureJDeveloper has been installed and that the application server and integration server connection havebeen configured.To deploy BPEL processes1 Make sure that the SOA Suite has been started.2 From Oracle JDeveloper, select the LSeMDRTransmitFDA project.3 Right-click on the project name and choose Deploy > IntegrationServerName > Deploy to default domain.4 Ignore the warnings listed on the build output window.5 Select the eMDRUpdateFDAAck project.6 Right-click on the project name and choose Deploy > IntegrationServerName > Deploy to default domain.7 Ignore the warnings listed on the build output window. This compiles the SRC code and then deploys the BPEL process to the SOA Instance.Instructions for ACR 4371 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. ❏ SIFFiles90 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 91. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ❏ WFs As part of the O2C release, schema changes have been made within the database. The O2CMST80_S_USER.sif, VACR437_EIMFinal_81.sif and VACR437_TableFinal_81.sif files all contain changes, and the S_USER table has been changed as well.For information about how to im port .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 theGenerate Triggers component, how to reveal the Default Tasks parameter, how to start tasks forWorkflow Monitor Agent, and how to set up the integration user see Siebel CRM and UCM Integration ,Guide. To access this guide, search for Doc ID 763962.1 on My Oracle Support.Instructions for ACR 439This topic is part of “Configuration Instructions for Enhancements and Updates” on page 40.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 application1 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 hasoccurred creating business component ‘Consumer’ used by business object ‘Search Execution’.Please ask your systems administrator to check your application configuration. (SBL-DAT-00222).Use the following procedure to resolve this error.To resolve the SBL-DAT-00222 error message1 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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 91
  • 92. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesFor 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 TechnologyNetwork (OTN) at http://www.oracle.com/technology/documentation/siebel.html.Instructions for ACR 439BThe following sections contain information about how to configure and install ACR 439B.Importing SIF Files for ACR 439BUse the following procedure to import the .sif files for ACR 439B.To import the .sif files for ACR 439B1 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 ScreenSiebel Tools Changes for ACR 439BNOTE: Lock the Fast Search project before performing the changes detailed in this section.To add the GotoView=Search lookin Results view1 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 applet1 Connect to Siebel Tools.2 Query for the Search lookin applet.92 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 93. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates3 Navigate to Applet User Prop and add the two user properties listed in the following table: Name Value Description SamePage TRUE/ FALSE Having this value set to TRUE displays the Search Results on the left hand side of the screen. GotoResultsView Search lookin Results View Search lookin Results View4 Navigate to Control, query for Name= "Search", and update the Search property as detailed in the following table: Name Target View Frame Description Search empty The old value is "_sweview". The property needs to be set to empty.To add the GotoView user property to the Search Results Body applet1 Connect to Siebel Tools.2 Query for the Search Results Body applet.3 Navigate to Applet User Prop and add the following user property: Name Value Description GotoResultsView Search lookin Results View4 Navigate to Control, query for Name = "PositionOnRow", and update the following property: HTML Bitmap HTML Disabled Bitmap ROW_OFF ROW_ON5 Navigate to Applet Web Template Items and add the item detailed below: Item Identifier Name Control Parent Name Type 501 PositionOnRow PositionOnRow Base ControlSeed Data Changes for ACR 439BUse the following procedure to add the Search lookin Results view. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 93
  • 94. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesTo add the Search lookin Results View1 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 439BSiebel Web Templates (SWT) are a set of HTML files with embedded Siebel tags that determine howthe UI is rendered in a browser. The following SWT files need to be edited for ACR 439B:■ Search_ListBodySearchResults.swt■ SearchResults.swt■ SavedSearch.swtApply the changes listed below for each swt in order for ACR 439B to display the web templatescorrectly.To edit Search_ListBodySearchResults.swtPlace the text below between this line: <!------------ Begin Row ------------->and this line: <!------------ Display all Search Result Field ------------->Insert the following text: <tr class="swe:this.RowStyle"> <swe:control id="501"><!-- Select 501 --><td align="swe:this.TextAlignment" width="42" class="Row"><swe:this property="FormattedHtml" hintText="Selected Row" hintMapType="Control"/></td></swe:control> <swe:select-row><td align="swe:this.TextAlignment" width="42" class="Row"><swe:this property="FormattedHtml" /></td></swe:select-row>To edit SearchResults.swtPlace the following text after the line </b> for id ="3000": &nbsp; &nbsp;94 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 95. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates <b> <swe:control id="3001"> <!-- CR 12-1O4OT68 --> <swe:this property="FormattedHtml" hintMapType="Control" hintText="Attach"/> </swe:control> </b> <b> <swe:control id="3002"> <!-- CR 12-1O4OT91 --> <swe:this property="FormattedHtml" hintMapType="Control" hintText="Preview"/> </swe:control> </b>To edit SavedSearch.swtPlace the following text after the line </tr> for id="99": <!-- Begin of CR 12-1O4OTAF --> <tr> <td align="left"> <swe:control id="101"> <b><swe:this property="FormattedHtml" hintMapType="Control" hintText="Field"/></b> </swe:control> </td> </tr> <tr> <td align="left">&nbsp</td> </tr> <!-- End of CR 12-1O4OTAF -->Instructions for ACR 450For information about how to implement ACR 450, within My Oracle Support, navigate to theKnowledge tab and search for Doc ID 880612.1.For more information about the Siebel Hospitality application, see Siebel Hospitality Guide on theSiebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 95
  • 96. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesInstructions for ACR 452Use 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 data1 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.To edit Tools.cfg to import symbolic strings1 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 StringsTo import ACR 452.sif1 Open ToolsREPPATCHACR452_phaseArepositoryimport.bat, and edit the required import.bat parameters, using the following as an example: ❏ SET PCDTOOLSPATH= <Enter Tools path here>96 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 97. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ❏ SET PCDDATASRC= <Enter DataSrc name used by Tools.cfg. The value is the same as [ServerDataSrc] in the Tools.cfg> ❏ SET PCDUSERNAME=<Enter the username used to connect to the Siebel database, such as SADMIN> ❏ SET PCDPASSWORD==<Enter the password used to connect to the Siebel database, such as SADMIN> ❏ SET LANG==<Enter language code, such as ENU>2 Run import.bat3 In Siebel Tools, import the ToolsREPPATCHACR452_phaseABusiness Component.sif file.To install localization files1 (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 changes1 Within Siebel Tools, navigate to Compile Projects, select all projects, and then click Compile.2 Save the srf file3 Within Siebel Tools, unlock the following Search projects: ❏ Fast Search ❏ Search Execution ❏ Symbolic StringsTo edit Tools.cfg for customer changes1 Open Tools.cfg, search for the SymStrPrefix parameter, and change the value of the SymStrPrefix parameter from SBL_ to X_. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 97
  • 98. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesTo install the AdvancedSearch SWT file1 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, seethe Siebel Search Administration Guide on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.Instructions for ACR 456This topic is part of “Configuration Instructions for Enhancements and Updates” on page 40.Use the instructions in this topic to implement AC 456, which provides a user interface for exporting Rand importing assignment-related data.For more information about the enhancements provided by ACR 456 for version 8.1.1.1 and later,see Siebel Assignment Manager Administration Guide. The latest version of this gui e is available on dthe Siebel 8.1 Bookshelf on OTN at http://www.oracle.com/technology/documentation/siebel.html.Importing Archive Files for ACR 456To 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.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 ■ Admin8 Import the archive files (.sif) y previously extracted from ACR456.zip into Siebel Tools. Import ou the files in the order shown below: ■ AM-ImportExport.sif98 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 99. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ■ AM-ImportExport-SymbolicStrings.sif ■ AM-ImportExport-applet.sif ■ AM-ImportExport-buscomp.sif ■ AM-ImportExport-screen.sif9 Compile the changes into an u pdated repository file (SRF file). Copy the ne SRF file to the Siebel w 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 456To 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 Skill4 Associate suitable responsibilities to the new views.5 Add List of Values (LOV) data for U.S. English (ENU), as described below. NOTE: This example is for U.S. English (ENU) only. For other languages, see files in the compressed file ACR456.zip. Set Display Value appropriately for each non-ENU language. a Navigate to the Administration - Data screen, then the List of Values view. b For Type TODO_TYPE, add new records, where: ❏ Display Value is Import, and Language-Independent Code is Import. ❏ Display Value is Export, and Language-Independent Code is Export. c For Type EVENT_STATUS, add new records, where: ❏ Display Value is Success, and Language-Independent Code is Success. ❏ Display Value is Failed, and Language-Independent Code is Failed. d For Type ACTIVITY_DISPLAY_CODE, add new records, where: ❏ Display Value is Position and Activities, and Language-Independent Code is Position and Activity. ❏ Display Value is Assignment and Activities, and Language-Independent Code is Assignment and Activity. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 99
  • 100. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesActivating Workflow Process for ACR 456To 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 456After performing all the steps described earlier in this topic, restart the Siebel Server and log in tothe Siebel Server. Refer to the information about importing and exporting assignment-related datain the Siebel Assignment Manager Administration Guide. Validate that the user interface changes arevisible in the Administration - Assignment screen, and validate that the relevant functionalitydescribed in that book works as expected.Instructions for ACR 457The following sections contain information about how to implement ACR 457.For more information about Siebel Order Management, see Siebel Order Management Guide on theSiebel Bookshelf http://www.oracle.com/technology/documentation/siebel.html.1 Navigate to the Siebel T ools installation directory <Tools Install Directory>REPPATCH, and unzip the acr457.zip file. This will create the following directory structure: <Tools Install Directory>REPPATCHacr4572 In Siebel Tools, lock the following projects: ❏ VORD Compound Product Validation Engine ❏ VORD Network Order Entry3 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.sif5 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.100 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 101. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates7 Start the Siebel Server.8 Lock the SIS OM Base Architecture project,and import the workflows listed in the following table into the Siebel application. Workflow Name New/Modified Project VORD Validate (Order) Modified SIS OM Base Architecture VORD Validate (Quote) Modified SIS OM Base Architecture SIS OM Disconnect Products & Services Process Modified SIS OM Base Architecture a Select Workflow Process in Siebel Tools Object Explorer. b Right-click on the right-side pane called Workflow Processes and import the .xml file into Siebel Tools from the workflows folder. Refer to the list of workflows in the table above to know which projects these workflows need to be imported into. c Check the status of each workflow process. If it is In-Progress, then deploy the workflow to change its status to complete. Do not click the Deploy + Activate button, as doing so will yield an error message. Only click the Deploy button. NOTE: You may receive the "This is an invalid Workflow…" error message while deploying the modified workflows from the list. Ignore the error and click Yes. d Repeat Step b and Step c for of all the workflows in the folder. e Log in to the Siebel application as an administrator, and navigate to the Site Map. f Click on Administration - Business Process. g Navigate to Workflow Deployment > Repository Workflow Process. h Query for the workflow processes and activate them.9 Restart the Siebel Server.10 Launch the Siebel Communications application.Enabling Component GroupsUse the following procedure to enable component groups.To enable component groups1 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] Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 10 1
  • 102. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates ❏ Communications Management [Alias- CommMgmt] ❏ Workflow Management [Alias- Workflow] NOTE: You can also activate the component groups by running the Enable compgrp <Alias> command through the Srvrmgr command prompt.3 After enabling the necessary components, navigate to Site Map > Administration - Server Configuration > Enterprises > Synchronize, select all the records and click the Synchronize button.4 Bounce the server.5 Use the following procedure if you are a Windows customer: a Log in with system administrator credentials. b From Start > Run, type cmd. c Find the drive that the build is installed on. d Type <Build>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> 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 serv manger by running command inStep e and verify er 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.102 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 103. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates g Restart the services.Use the following procedure to delete Customer Order Management workflows.NOTE: Before you run the scripts in the following procedure, make sure the Workflow component isenabled and that the server has been restarted after the component groups have been enabled.To delete Customer Order Management workflows1 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 that has the Method Name as "DeleteDeploy" and click the Run button.Activating the Workflows Through ScriptsUse 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 serverhas been restarted after the component groups have been enabled.To activate Customer Order Management workflows1 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 - Defaultworkflow process.To manually enable the Pricing and Eligibility workflow process1 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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 10 3
  • 104. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates4 Log out and relogin in to Siebel eCommunications application. You can now create orders.Instructions for ACR 463The 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: If you have installed Siebel 8.1.1 QF1002 for ACR 463 or Siebel 8.1.1.1 QF5101 for ACR 463,you do not need to perform the repository changes detailed in the following sections, as the changesthat you performed when you installed the Quick Fixes were not overwritten. However, if you areinstalling ACR 463 for the first time, you do need to perform the repository changes detailed in thefollowing sections.1 Navigate to the Siebel Tools installation directory <Tools Install Directory>REPPATCH.2 Unzip the file ACR463.zip file. This will create the following directory structure: <Tools Install Directory>REPPATCHACR463.zip The ACR463.zip folder that you create will contain the following subfolders: ❏ DMGSchemaChanges ❏ EIM ❏ LMU ❏ SeedData ❏ SIFFiles ❏ WFsThe following instructions refer to the folders specified above.Applying Schema Changes to the DatabaseThe 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 database1 Lock the following projects before importing: ❏ EIM Asset ❏ EIM Common SIA ❏ EIM Invoice104 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 105. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ❏ EIM Order ❏ EIM Product ❏ EIM Quote ❏ EIM BulkRequest ❏ EIM Organization ❏ EIM Service Request ❏ Table A sset ❏ Table BulkRequest ❏ Table I nvoice ❏ Table Order ❏ Table Organization ❏ Table Product ❏ Table Q uote ❏ Table Service Request ❏ Table Special Rate List ❏ Table C IF ❏ Table P erson ❏ Table FleetManagement ❏ CUT Newtable2 Import the .sif files in the following sequence ❏ AIA24_schema_changes.sif ❏ AIA24_EIM_schema_changes.sif3 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 DatabaseUse the following procedure to create tables on the physical database.To create tables on the physical database1 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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 10 5
  • 106. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates3 From Object Explorer, select Table Object Definition.4 Query for the tables that have changed using the following criteria: Query Criteria: Changed = Yes5 Click on Apply/DDL.6 Select Apply DDL.7 Select Current Query from the Tables drop-down list.8 Enter the appropriate information for ODBC Data Source/ Database User and Database User Password.9 Click the Apply button. The "Changes Successfully Applied" message displays.Importing Seed DataUse the following procedure to import seed data.To import seed data1 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. 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 log106 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 107. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates 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 <T ools Install Directory>tempdataimp_seed.log file to mak sure that the e import completed successfully.Siebel Tools Changes for ACR 4631 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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 10 7
  • 108. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates ❏ CUT Trouble Ticket ❏ Contact ❏ Comm Manager ❏ Communication ❏ Eligibility Compatibility ❏ Fleet Management ❏ ISS Authoring Admin ❏ ISS Class Admin ❏ ISS Product Admin ❏ ISS Promotion Admin ❏ MACD Performance ❏ Order Entry ❏ Prepaid Service 8.1 ❏ Product ❏ Product (SSE) ❏ Product Integration ❏ Product Selection UI ❏ Quote (UI) ❏ Quote ❏ SIS OM Base Architecture ❏ Service ❏ Symbolic Strings ❏ UCM Privacy Management ❏ VEAI CUT Billing Integration ❏ VERT CUT Address ❏ VERT CUT Screens ❏ Web Channel Order Management ❏ Web Service Integration ❏ eService Billing ❏ eAuto Product108 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 109. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates3 Import the rest of the SIF files from the SIFFiles folder into Siebel Tools using the Import From Archive function. NOTE: If you have not locked the required projects, you may receive a warning error message. Make sure to choose Merge Option in Siebel Tools Import Wizard. Import the following SIF files: ❏ Modified Applets.sif ❏ Modified BCs.sif ❏ Modified Bitmaps.sif ❏ Modified BOs.sif ❏ Modified BSs.sif ❏ Modified Classes.sif ❏ Modified Commands.sif ❏ Modified IOs.sif ❏ Modified Links.sif ❏ Modified Picklists.sif ❏ Modified Screens.sif ❏ Modified Symbolic Strings.sif ❏ Modified Views.sif ❏ Modified Workflow Policy Columns.sif ❏ Modified Workflow Policy Objects.sif The following steps are only necessary for customers who are installing languages other than ENU:4 Import LMU Files for the specific language from the LMU folder into Siebel Tools. [Select menu Tools Utilities Locale Management]. a Select Source Language = English American Target Language = <Specific Language> b Click the Import tab > Browse to locate the LMU file you want to import and click Import. NOTE: If an error occurs while yo are importing theLMU file, open the file convert the language u , 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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 10 9
  • 110. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates7 Start the Siebel Server.8 Import the workflows listed in the following table into the Siebel application. NOTE: All of the existing workflows should be imported. In other words, the modified workflows should be imported into the corresponding projects. Workflow Name Project ABO Bulk Request - Validate Process ABO Bulk Request ABO Bulk Request Add Item Customize Process ABO Bulk Request ABO Bulk Request - Clear Exception Process Workflow ABO Bulk Request ABO Bulk Request - Parallel Sub Process Workflow ABO Bulk Request ABO Bulk Request - Prepare Action Set Sub-Process Workflow ABO Bulk Request ABO Bulk Request - Submit Process Workflow ABO Bulk Request Basic Pricing Procedure Cfg RTC CMU Credit Alert Status Sync Web Service Integration CMU SIA Submit Adjustment Request to External CMU Billing Integration CMUBalanceDetailsEventAdjustmentWF CMU Billing Integration CMUEventDetailsAdjustmentWF CMU Billing Integration CMUInvoiceAdjustmentWF CMU Billing Integration CMUItemChargeAdjustmentWF CMU Billing Integration CMUUnbilledEventAdjustmentWF Web Service Integration CMUUnbilledNonCurrencyEventAdjustmentWF Web Service Integration Dynamic Pricing Procedure Row Set Transformation Toolkit ISS Promotion Upgrade Process ISS Promotion Workflow Pricing Procedure - Calculate Net Price Row Set Transformation Toolkit SIS OM Disconnect Products & Services Process SIS OM Base Architecture SIS OM Edit Complex Asset Workflow SIS OM Base Architecture SIS OM Edit Service Order Line Item SIS OM Base Architecture SIS OM Modify Products & Services Process SIS OM Base Architecture SIS OM Order Line Item Update Main SIS OM Base Architecture SIS OM Suspend / Resume Asset Sub-Process SIS OM Base Architecture SIS OM Suspend / Resume Products & Services Process SIS OM Base Architecture SISOMBillingSubmitOrderWebService CMU Billing Integration SWI Account Update Workflow Web Service Integration SWI Address Update Workflow Web Service Integration110 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 111. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates Workflow Name Project SWI Billing Profile Update Workflow Web Service Integration SWI Cancel Sales Order Line Item Web Service Integration SWI Contact Update Workflow Web Service Integration SWICancel Sales Order Web Service Integration SWI Special Rating - Synchronize Process Web Service Integration SWIAdjustmentStatusUpdate Web Service Integration SWICopyOrder Web Service Integration SWIOrderUpsert Web Service Integration SWIValidateDependentOrders Web Service Integration Verify Header (Order) COM Workflows Verify Item (Order) COM Workflows a Select Workflow Process in Siebel Tools Object Explorer. b Right-click on the right-side pane Workflow Processes and import the .xml file into Siebel T ools from the WFs folder Refer to the list of workflows in the table above to know which project these . workflows need to be imported into. c Check the status of the Workflow process. If it is In-Progress, then make it complete by deploying the Workflow process (For version 8.0 and above, the "Publish/Activate" button changes the status to complete. To view this button, click the View menu > Tool Bar, and select WF/Task Editor.) NOTE: If this step throws an error message, note the workflows tht failed and manually activate a 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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 11 1
  • 112. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates d For this Action Set, in the bottom Form Applet, there is a control with the Business Service Context label. For this control, the current value previously was only "ISS Promotion Pricing Components", "ISS Promotion Pricing R ules Summary". Another new entry w added to this and as now the value for this control is "ISS Promotion Pricing Components", "ISS Promotion Pricing Rules Summary", and "Promotion Config Item". (Note that there should be a space after the comma.) e Navigate to the child applet. f Uncheck the Active flag for the Validate record.10 Release Variable Maps and Signals manually: a Navigate to Site Map > Admin - Order Management > Variable Maps. b Query for the following: ❏ Default Pricing Variable Map - Row Set - Basic ❏ Default Pricing Variable Map - Row Set ❏ Default Pricing Eligibility Variable Map - Row Set c Lock each Variable Map and release a new version of each of these maps. d Navigate to the Signals view, and query for “ReviseCopyOrder”. e Lock this signal and release a new version.Activating Validation Rulesets and Reloading Runtime EventsUse the following procedure to activate data validation ruleset.To activate the data validation ruleset1 Navigate to the Site Map, and query for Administration - Data Validation.2 Click the Ruleset View hyperlink.3 Query for the following rulesets in the Validation Ruleset applet: ❏ SWI Order Validation Rule Set ❏ SWI SRL Delete ❏ SWI SRL Item ❏ SWI SRL Modify4 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 events1 Within the Site Map, navigate to the Administration - Runtime Events screen.112 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 113. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates2 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 databa se-integrated messaging infrastructure in Oracledatabase. 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 areapplicable to the messages and queues in AQ. Standard database features such as backup andrecovery, security, and manageability are available to AQ.AQ has been implemented for the following outbound Web services in this release: ■ Special Rating List ■ Submit Order ■ AdjustmentThe following sections contain information about how to implement AQ in your Siebel application, aswell as more detailed information about the outbound Web services listed above.Special Rating ListThis service is used to synchronize the mod ified 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 Comm2.4 release. It is invoked through the Synchronize button, which is available in the Special Rating listapplet (Account screen > Profiles view > Special Rating Profile). The workflow contains the steps toquery for and synchronize the updated Special Rating List with BRM by calling the Proxy BusinessService, as detailed below.Start > (Connector 0) > Query Special Rating List > Synchronize > Update List Synch Date >Upadate Items Synch Date > End 0Note the following information about the SWISpecialRatingList outbound Web service: ■ It is a new Web service. ■ It is an asynchronous outbound Web service Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 11 3
  • 114. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates ■ Its namespace is http://siebel.com/asiThis Web service is used to send the Updated/Modified Special Rating List details to BRM forsynchronizing 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 outboundWeb service target address.Use the following procedure to update the target address.To update the target address1 Naviate to the Site Map > Administration - Web Services screen.2 Navigate to the Outbound Web Services aggregate view.3 Query for the "SWISpecialRatingList" service name.4 Change the following field values in the Service Port applet: ❏ Transport: J MS ❏ 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 ServiceThis outbound service is used to send the order details to AIA. The user initiates the service byclicking 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 service1 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 WorkflowThis is an existing workflow that submits an order from the Siebel CRM application to the billingapplication and creates a new account, if needed, in the billing application. Users initiate thisworkflow 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 service114 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 115. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ■ Its namespace is http://siebel.com/asiUse this Web service to submit orders into the queue. This AQ and connection factories are createdin 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 address1 Navigate to Site Map > Administration - Web Services screen.2 Navigate to the Outbound Web Services aggregate view.3 Query for the "SWISubmitOrder" service name.4 Change the following field values in the Service Port applet: ❏ Transport: J MS ❏ 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 ServiceThis outbound service is used to Submit an Adjust ent request to BRM. Users initiate the service by mclicking the Submit button on the SIA CUT Adjustment External Line Items view.To initiate the SWICreateAdjustment outbound Web service1 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 WorkflowThis 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 anoutbound Web service and changing the status of Adjustment Header to Submitted. Users initiatesthis 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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 11 5
  • 116. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates5 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 ServiceNote 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/asiUse this W service to Submit Adjustment R eb equest into the queue. This AQ and connection factoriesare created in FMW and the same URL should be used in outbound Web service target address.Use the following procedure to update the address.To update the address1 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: J MS ❏ 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 ServicesUse the following procedures to configure FMW URLs for Web services.To configure FMW URLs for the outbound Web services1 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)116 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 117. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesTo configure FMW URLs for inbound Web services1 In Administration - Web Services > Inbound Web Services, make sure the corresponding Web services are active. If they are not, change the status from "Inactive" to "Active", and click the Clear Cache button. NOTE: Query for these inbound web services: * ISS *; * Update Order *; * SWI Update *, SWI*2 Query for Name = SWI Account Update.3 In the middle Inbound Service Ports list applet, change the address port. Address: (example only) http://sdchs20n513.corp.siebel.com/eai_enu/ start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute&UserName=SADMIN&Pass word=MSSQL NOTE: Replace the string <web server>, <lang>, <UserName>, <Password> with correct data based on server information.4 Repeat the preceding steps for all inbound Web services.Setting Up Order CreationUse the following procedures to enable component groups.To enable compgrpsNOTE: Bounce the server after enabling the compgrp and synchronizing it. ■ Enable the following compgrps: ❏ Siebel CME [Alias- Communications] ❏ Siebel ISS [Alias- ISS] ❏ Workflow Management [Alias- Workflow] ❏ Communications Management [Alias CommMgmt] For more information about enabling compgrps, see “Enabling Compgrps” on page 142.Activating and Configuring ACR 463 WorkflowsThe procedures in the following sections describe how to activate and configure the ACR 463workflows.To activate workflowsUse 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* Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 11 7
  • 118. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates ■ Query for the following groups: Eligibility & Comp, Asset Based Ordering, Pricer, eSales, Product Promotions, Configurator, C/OM UI processes, CUT eSales (for SIA, not for HOR), Product Recommendation, and delete them manually after deactivating the processes. To deactivate these groups, select them all and then select Deactivate Process. You can check the Deployment Status as Inactive.3 Delete all the records.4 In the first applet, perform one of the following two actions: ■ Query for SIS*,Pri*,PSP*,ISS*,Elig*,eSales* ■ Query for the following groups: Eligibility & Comp, Asset Based Ordering, Pricer, eSales, Product Promotions, Configurator, C/OM UI Processes, CUT eSales (for SIA, not for HOR), Product Recommendations.5 Activate all of the workflows.Workflow Policy Setup and ConfigurationThe following sections describe how to set up and configure workflow policies.Siebel Components GroupsIn order to enable the workflow policies, the following components should be configured and runningon Siebel Server (in addition to the Application Object Manager component). Component Name Component Alias Component Group Enterprise Integration Mgr EIM EAI EAI Object Manager (ENU) EAIObjMgr_enu EAI Workflow Process Manager WfProcMgr Workflow Workflow Process Batch Manager WfProcBatchMgr Workflow Workflow Monitor Agent WorkMon Workflow Generate Triggers GenTrig WorkflowEnabling EAI and Workflow Component Groups in the Siebel Server will start all the requiredComponents 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.118 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 119. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates2 Click New and type "Generate Triggers" under Component/Job to create a job for the Generate Triggers c omponent.3 Define the job parameters with the following values: ❏ EXEC = TRUE ❏ Privileged User = SADMIN ❏ Privileged User Password = ******[Password for SADMIN] ❏ Remove = TRUE ❏ Trigger File Name: trigger.sql4 Start the job.5 Verify that the job was successful once it has completed.To generate the triggersNOTE: Make sure that the SADMIN user has the necessary privileges for generating triggers beforeperforming this procedure.1 Navigate to Administration > Server Management > Jobs.2 Click New and type "Generate Triggers" under Component/Job to create a job for the Gnereate Triggers c omponent.3 Define the job parameters with the following values: ❏ EXEC = TRUE ❏ Privileged User = SADMIN ❏ Privileged User Password = ******[Password for SADMIN] ❏ Trigger File Name: trigger.sql4 Start the job.5 Verify that the job was successful once the job has completed.Configuring Workflow Monitor AgentUse the following procedure to configure Workflow Monitor Agent.To configure Workflow Monitor Agent1 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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 11 9
  • 120. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates4 Under Component Parameters, query for "Group Name" and type the SWI Account Update Policy Grp under Value to change the Group Name to “SWI Customer Update Policy Grp” in the Component Parameter applet.5 Change the Action Interval to 5.6 Change the Sleep Time to 15. (Select the Advanced button.)7 Change the Default Task to 1. (Select the Advanced button.)8 Click the Activate button to change the status of the new component to "Active".9 Synchronize the components.Configuring Default Tasks for Workflow Monitor AgentServer Manager contains a parameter called Show Advanced Objects that controls the display of allthe objects that are marked for the advanced user.Workflow Monitor Agent has a parameter called Default Tasks which has been hidden and shouldonly be displayed or available to advanced users.Use the following procedure to reveal this hidden parameter.To display the Default Tasks parameter1 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 CustomerSynchronizationUse the following procedure to start tasks for the component that is online/enabled.To start tasks for Workflow Monitor Agent1 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.120 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 121. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates4 Start srvrmgr: srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u <userid> /p <password>.5 Start the task for the WorkMonSWI component.After about five minutes, check for log details for the task for the new workflow monitor component"Workflow Monitor Agent SWI" by navigating to Administration > Server Management > Task.If there are errors, check to see if all configurations have been properly performed. If not, repeatthe procedures detailed in “To generate the triggers” on page 119 after restarting the Siebel Server.Integration User SetupThis section describes the integration user setup process. User credentials need to be configured (onthe AIA side) for the Siebel Inbound Web Services call from the AIA side to avoid the boomerangeffect.To set up the integration user1 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 preferences1 Navigate to Administration - Application > System Preferences in the application, query for Enable AIA Comms in the System Preference Name field, and set theSystem 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 PricingCustomers with the Dynamic Pricer license will need to undertake the steps mentioned in thedocument to enable the execution of Dynamic Pricing Procedure. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 12 1
  • 122. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesIn order to leverage the dynamic pricing procedure, customers have to perform following changes tothe existing repository.The Siebel pricing module is available in multiple licensing modes and each mode is associated witheither the Basic Pricing Procedure or the Dynamic Pricing Procedure.Basic Pricing Procedure ■ This procedure mimics the basic Siebel Pricer functionality that was available in Siebel version 7.7 applications. ■ Basic Siebel Pricer functionality includes list price, volume discounts, and service pricing. ■ It leverages the variable maps that do not contain the XA child variable maps.Dynamic Pricing Procedure ■ This provides the complete pricing capabilities such as attribute pricing, promotions, aggregate discounts, and so forth. ■ It leverages the variable maps that contain the XA child variable maps. ■ It is available only to those customers that have the Dynamic Pricer license.To enable dynamic pricing■ If you are running Siebel applications version 8.1.1 or above, navigate to Administration - Pricing > Price Lists, and select Enable Dynamic Pricing from the applet-level menu in the Price List applet.■ If you are running Siebel applications versions earlier than 8.1.1, you must modify the signals mentioned in the following section manually.Modifying SignalsUse the following procedure to modify signals.To modify signals1 Navigate to Administration - Order Management > Signals, query for each signal mentioned in the following tables, and make the necessary modifications.Signal: CalculatePriceAndCheckEligibilityActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcess122 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 123. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesApplication Name: N/AMode: N/AInstance Type: N/AFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLAction: Y Name Value SubPSPPricingWFName Dynamic Pricing Procedure SubPSPWFName Pricing and Eligibility Procedure - Default Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Eligibility Variable Map - Row SetSignal: QuotesAndOrdersValidateActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: OrderInstance Type: HeaderFields: N/ACondition: N/AActive: Y Name Value SubPSPPricingWFName Dynamic Pricing Procedure SubPSPWFName Pricing and Eligibility Procedure - Default Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Eligibility Variable Map - Row SetMake similar changes to actions in this signal where: Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 12 3
  • 124. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesMode: Order, Instance Type: Line ItemMode: Quote, Instance Type: HeaderMode: Quote, Instance Type: Line ItemSignal: VerifyItemActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: AgreementInstance Type: HeaderFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: Y Name Value SubPSPPricingWFName Dynamic Pricing Procedure SubPSPWFName Pricing and Eligibility Procedure - Default Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Eligibility Variable Map - Row SetMake similar changes to actions in this signal where:Mode: Order, Instance Type: HeaderMode: Quote, Instance Type: HeaderSignal: Product Recommendation SignalActions and Parameters:Sequence: 1Service Type: WorkflowService Name: Product Recommendation Driver WorkflowService Method: RunProcess124 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 125. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesApplication Name: N/AMode: N/AInstance Type: Line ItemFields: N/ACondition: GetProfileAttr(Block Variable Map Operations)=N OR GetProfileAttr(Block Variable MapOperations) IS NULLActive: Y Name Value SubPSPPricingWFName Dynamic Pricing Procedure VariableMap 1 Default Product Recommendation Variable Map - ContextSignal: CalculatePriceExternalActions and Parameters:Sequence: 1Service Type: Business ServiceService Name: Pricing ManagerService Method: RunPricerWorkflowApplication Name: N/AMode: N/AInstance Type: N/AFields: N/ACondition: N/AActive: N/A Name Value SubPSPPricingWFName Dynamic Pricing ProcedureSignal: SpreadDiscount, SpreadDiscount - AllActions and Parameters:Sequence: 1Service Type: WorkflowService Name: Spread Discount Driver Workflow Process Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 12 5
  • 126. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesService Method: RunProcessApplication Name: N/AMode: N/AInstance Type: N/AFields: N/ACondition: N/AActive: Y Name Value SubPSPPricingWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Spread Discount Default Pricing Variable Map - Row SetSignal: ApproveItemActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Workflow Driver ProcessService Method: RunProcessApplication Name: N/AMode: AgreementInstance Type: HeaderFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetMake similar changes to actions in this signal where:Mode: Order, Instance Type: HeaderMode: Quote, Instance Type: Header126 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 127. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesSignal: CalculatePriceActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: N/AInstance Type: N/AFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetSignal: CalculatePriceAllActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: N/AInstance Type: Line ItemFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULL Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 12 7
  • 128. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesActive: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetSignal: CalculatePrice_eSalesActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: N/AInstance Type: N/AFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLY Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetSignal: CalculatePriceAll_eSalesActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: N/AInstance Type: LineFields: N/A128 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 129. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesCondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLAction: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetSignal: CalculatePrice_ConfiguratorActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: N/AInstance Type: N/AFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetSignal: CalculatePrice_AdvisorActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: N/A Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 12 9
  • 130. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesInstance Type: N/AFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetSignal: MergeIntoOnePackageActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: N/AInstance Type: Line ItemFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetSignal: OrderTemplateActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcess130 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 131. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesApplication Name: N/AMode: OrderInstance Type: HeaderFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetMake similar changes to actions in this signal where:Mode: Quote, Instance Type: HeaderSignal: OrderTemplateCopyActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: OrderInstance Type: HeaderFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: 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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 13 1
  • 132. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesSignal: OrderTemplateSelectItemsActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: OrderInstance Type: HeaderFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetSignal: QuoteTemplateCopyActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: QuoteInstance Type: HeaderFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULL132 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 133. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesActive: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetSignal: QuoteTemplateSelectItemsActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: QuoteInstance Type: HeaderFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetSignal: SetFieldValueActions and Parameters:Sequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: N/AInstance Type: Header Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 13 3
  • 134. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesFields: Discount; Price List; Currency CodeCondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetSequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: AgreementInstance Type: Line ItemFields: Product; Quantity Requested; Unit Price; Discount Amount; Discount Percent; CurrencyCode; Item Price List; Covered Product Net PriceCondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetSequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: OrderInstance Type: Line Item134 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 135. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesFields: Product; Quantity Requested; Unit Price; Discount Amount; Discount Percent; Prod PromName; CurrencyCondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetSequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: QuoteInstance Type: Line ItemFields: Product; Quantity Requested; Unit Price; Discount Amount; Discount Percent; Prod PromName; Currency Code; Item Price List; Covered Product Net PriceCondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context Default Pricing Variable Map - Context Variable Map - Row Set Default Pricing Variable Map - Row SetSignal: Get Config Item PriceSequence: 1Service Type: WorkflowService Name: Get Config Item Price - Driver WorkflowService Method: RunProcessApplication Name: N/A Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 13 5
  • 136. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesMode: N/AInstance Type: N/AFields: N/ACondition: N/AActive: Y Name Value SubPSPWFName Get Config Item Price - DynamicSignal: GetProdPriceSequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: N/AInstance Type: N/AFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: YName ValueSubPSPWFName Dynamic Pricing ProcedureVariable Map - Context Default Pricing Variable Map - ContextVariable Map - Row Set Product Pricing Variable Map - Row SetSignal: GetUserProdPriceSequence: 1Service Type: WorkflowService Name: PSP Driver Workflow ProcessService Method: RunProcessApplication Name: N/AMode: N/AInstance Type: N/A136 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 137. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesFields: N/ACondition: GetProfileAttr(SkipToEnd) = N OR GetProfileAttr(SkipToEnd) IS NULLActive: Y Name Value SubPSPWFName Dynamic Pricing Procedure Variable Map - Context User Product Pricing Variable Map - Context Variable Map - Row Set Product Pricing Variable Map - Row SetSignal: PDS GetPricingSequence: 1Service Type: WorkflowService Name: Dynamic Pricing ProcedureService Method: RunProcessApplication Name: N/AMode: N/AInstance Type: N/AFields: N/ACondition: N/AActive: YRunning EIM Data MigrationThis section defines the detailed steps to run the EIM jobs for Siebel applications as a part of theCreating 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 Alertsfrom BRM into the Siebel EIM tables. EIM scripts wi l be then executed to load the data into the SF l Abase 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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 13 7
  • 138. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesTo execute the EIM job1 Move the ProcessAlertsAndBillingProf.ifb file from <Tools Installation directory>/REPPATCH/ ACR463/EIM to <Siebel Installation Directory>/ses/siebsrvr/ADMIN.2 Run the EIM job with the ProcessAlertsAndBillingProf.ifb configuration file.3 Verify that the EIM job is successful.Runtime Configuration for Product Class and Attribute Definition SyncUse the procedures in the following sections to perform runtime configuration for Product Class andAttribute Definition Sync.User ListUse the following procedure to add users to the user list.To add users to the user list1 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 EventsAn email notification can be sent from product class definition, attribute definition and workspacedefinition.The following procedure describes how to add three runtime events to extract the email addressesfrom user lists in the PreInvoke method of Business Components.To add three runtime events to extract email addresses from users lists1 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:138 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 139. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates "SCE Users";"Email Address";"Account";"Account";"Contact" or "SCE Users";"EMail Addr";"User List";"User List";"User" The following table describes the three run time events that are added. Sequence Object Type Object Name Event SubEvent Action Set Name 1 BusComp Attribute VOD PreInvokeMethod SendEmail EmailNotify BusComp 2 BusComp ISS Class VOD PreInvokeMethod SendEmail EmailNotify BusComp 3 BusComp ISS oint J PreInvokeMethod SendEmail EmailNotify Workspace BusCompEmail TemplatesUse the following procedure to view the email templates that have been added.To view the added email templates1 Navigate to Administration- Communications > All Templates. The following table describes the four templates that have been added: Name Description Attribute Defn Template To send email from the Attribute Definition view Product Class Template To send email from the Product Class Definition view Workspace Attribute Defn Template To send attribute details from the Workspace view in emails Workspace Product Class Defn Template To send attributes from the Workspace view in emails2 To change the email body of the templates used to send emails from the workspace view, navigate to Administration Communication > All Templates > Template Items. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 13 9
  • 140. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesThe email templates detailed above are configured as user property values in the following BusinessComponents: Business Component User Property Template Name ISS Joint Workspace PackageNameList|Attribute Workspace Attribute Defn BusComp Definition Template ISS Joint Workspace PackageNameList|Product Workspace Product Class BusComp Class Definition Defn Template Attribute VOD BusComp PackageNameList Attribute Defn Template ISS Class VOD BusComp PackageNameList Product Class TemplateCommunication ProfileUse the following procedure to add From Email Address, POP server name, and SMTP server namein the communication profile.To add From Email Address, POP server name, and SMTP server name1 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: sscmmail3 Set the profile in the child applet as Default SMTP profile. For Example - Default SMTP profile4 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.com140 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 141. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ■ SMTP Server: rgmamersmtp.oraclecorp.com The communication profile has to set in the user property in the Business Components listed in the following table: Business Component User Property Template Name ISS Joint Workspace CommProfileOverride Default SMTP Profile BusComp Attribute VOD BusComp CommProfileOverride Default SMTP Profile ISS Class VOD BusComp CommProfileOverride Default SMTP ProfileRecipient GroupThe recipient group determines which Business Object is associated with the communicationtemplate. Only primary Business Component fields and their child Business Component fields areavailable to use in the template.Use the following procedure to add the recipient group.To add the recipient group1 Navigate to Administration - Data > List of Values.2 Query for "COMM_RECIP_GROUP" and add the recipient group.3 To set the recipient group, navigate to Administration - Communications > All Templates > Advanced and select the recipient group from the drop-down list. Name Recipient Group Attribute Defn Template AttributeDefnBC Product Class Template ProductClassDefnBC Workspace Attribute Defn Template WorkSpaceBC Workspace Product Class Defn Template WorkSpaceBC The LIC values of the recipie groups added in Step 2 are set inthe user property of the Business nt Components listed in the following table: Recipient Group(LIC Business Component User Property Value) ISS Joint Workspace RecipientGroup ISS Joint Workspace BusComp BusComp Attribute VOD BusComp RecipientGroup Attribute VOD BusComp ISS Class VOD BusComp RecipientGroup ISS Class VOD BusComp Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 14 1
  • 142. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesEnabling CompgrpsUse the following procedures to enable compgrps.To enable compgrps for the Windows machine1 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: 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 UNIX1 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.142 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 143. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesInstructions for ACR 464This 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 1432 Importing Changes to the Siebel Repository from SIF Files on page 1443 Applying Changes to the Siebel Database on page 1464 Importing Seed Data on page 147Importing Changes to the Siebel Repository from a Batch FileThis 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 file1 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 t SymStrPrefix parameter back to the original v he alue.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.txt7 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 th database, username, folder names, Siebel Tools e installation directories, and other information that is specific to your environment. The required parameters are documented in the file. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 14 3
  • 144. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates10 Close Siebel Tools.11 Open a DOS command line, and then run the Repository_import.bat file.12 Check the following log files in the <Siebel Tools installation>log directory to make sure that only insert operations were performed. ■ Applet.log ■ Business Component.log ■ Business Object.log ■ Business Service.log ■ Class.log ■ DLL.log ■ Integration Object.log ■ Link.log ■ Pick List.log ■ Screen.log ■ Symbolic String.log ■ Table.log ■ View.log If the log files indicate a problem, then create a service request (SR) on My Oracle Support. Alternatively, you can phone Global Customer Support directly to create a service request or get a status update on your current SR. Support phone numbers are listed on My Oracle Support. You can also contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracles Application Expert Services.Importing Changes to the Siebel Repository from SIF FilesThis section describes how to import schema changes into the Siebel Repository from sif files. Youmust import these files separately because each import might affect an object in a subsequentimport. The objects must be merged. The batch import feature does not merge objects.To import changes to the Siebel Repository from sif files1 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.sif144 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 145. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates c In the Import Wizard-Preview dialog box, make sure the following option is chosen, and then click Next: Merge the object definition from the archive file with the definition in the repository Siebel Tools displays the Import Wizard-Review Conflicts and Actions dialog box. d Wait until Siebel Tools finishes loading the sif file. You can view the status bar at the bottom of the dialog box to monitor progress. e If the Conflicting Objects window of the Import Wizard-Review Conflicts and Actions dialog box contains an item, then see “Resolving Conflicts” on page 145. Otherwise, continue to Step f. f In the confirmation dialog box, click Yes. g In the Import Wizard-Summary dialog box, click Finish.2 Repeat Step 1 for each of the following files: ■ Business ObjectBusinessObject-Update.sif ■ TablebaseTable-Update.sif ■ Business ComponentBusinessComponent-Update.sif3 Examine the following log file to make sure all imports executed successfully: Siebeltoolstempimportlog.txt4 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 143.6 Save the tools.cfg file.7 If Siebel Tools is open, then exit out of it, and then open it.Resolving Conflicts1 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 148.3 Do one of the following: a If the object appears in “Changes Made as a Result of Importing SIF Files” on page 148, 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 146. b If the object does not appear in “Changes Made as a Result of Importing SIF Files” on page 148, 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 146. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 14 5
  • 146. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates c If the object appears in “Changes Made as a Result of Importing SIF Files” on page 148, 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 146.4 If other objects appear in the Co nflicting 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 FileIn this situation, the object does not exist in the repository and Siebel Tools sets the Action to Fileby default. For example, the Siebel Universal Agent application includes a difference for the PIMClient Package screen in the Screen Menu Item object. There is no conflict because this is an intendedchange and the PIM Client Package screen does not exist in the repository.Example of Using the Value from the RepositoryWhen you import the Application.sif file, Siebel Tools displays 15 objects in the Conflicting Objectswindow. If you expand an object, then the Object Differences window displays the followingdifferences 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 donot appear in “Changes Made as a Result of Importing SIF Files” on page 148. Therefore, you must setAction to Repository for each of these objects in order to keep the current repository values.Example of a Conflict That Requires Additional AssistanceAssume you import the BusinessComponent-Update.sif and the ContactDBLastUpd field of theEmployee 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 anintended change and it appears in “Changes Made as a Result of Importing SIF Files” on page 148.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 astatus update on your current SR. Support phone numbers are listed on My Oracle Support. You canalso contact your Oracle sales representative for Oracle Advanced Customer Services to requestassistance from Oracles Application Expert Services.Applying Changes to the Siebel Database1 In the Object Explorer, click Table.2 In the Tables list, issue the following query in the Name property:146 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 147. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates S_EVT_ACT OR S_PIM_INT_PKG OR S_PIM_INT_FILE OR S_PIM_INT_PKGFL OR S_PIM_INTFL_DEF3 Click Apply/DDL.4 In the Choose option dialog box, make sure the Apply option is chosen, and then click OK. If the Warning dialog box appears, then click OK.5 In the Apply Schema dialog box, choose Current Query in the Tables drop-down list, and then enter the following information according to the type of database into which you are applying this schema change. These values might be different for your environment. Check with your database administrator if you are not sure about the correct values to enter. For more information, see Developing and Deploying Siebel Business Applications. Field MSSQL Oracle DB2 Tables Current Query Current Query Current Query Table s pace (Leave empty) DATA TBS_4K 16K table space (Leave empty) (Leave empty) TBS_4K 32K table space (Leave empty) (Leave empty) TBS_32K Index space (Leave empty) DATA TBS_4K Storage control file (Leave empty) (Leave empty) (Leave empty) Database user (User name) (User name) (User name) Database user password (User password) (User password) (User password) ODBC data source (Data source) (Data source) (Data source) DDL file (Leave empty) (Leave empty) (Leave empty)6 Click Apply.7 Compile and deploy the SRF.Importing Seed DataThe following procedure describes how to import seed data.To import seed data1 Open the following file in a text editor: ACR464-HOR8112Seed_import.bat2 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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 14 7
  • 148. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates4 Review the following files to make sure the import completed successfully: <SiebelTools installation directory>logACR464_seed.log <SiebelTools installation directory>logACR464_seed_<language>.log.Changes Made as a Result of Importing SIF FilesThis section describes changes that are made to the Siebel Repository as a result of importing SIFfiles.Changes Made as a Result of Importing the Application-Update.sif FileTable 8 describes changes made to applications as a result of importing the Application-Update.siffile.This sif file includes the new PIM Client Package screen of the screen menu item for theseapplications.Table 8. Changes Made as a Result of Importing the Application-Update.sif File Siebel Business Applications and Siebel Industry Applications Siebel Industry Applications The following applications are changed: The following applications are changed: ■ Siebel ERM Administration ■ Siebel Automotive ■ Siebel Field Service ■ Siebel Consumer Sector ■ Siebel Marketing Enterprise ■ Siebel Financial Services ■ Siebel Partner Manager ■ Siebel HTIM ■ Siebel Sales Enterprise ■ Siebel Hospitality ■ Siebel Universal Agent ■ Siebel Life Sciences ■ Siebel Loyalty ■ Siebel Power Communications ■ Siebel Public Sector148 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 149. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesChanges Made as a Result of Importing the BusinessObject-Update.sif FileTable 9 lists the new business object components that are added into business objects as a result ofimporting the BusinessObject-Update.sif file.Table 9. Changes Made as a Result of Importing the BusinessObject-Update.sif File Business Object Siebel Business Applications Siebel Industry Applications Account The following business object The following business object components are added: components are added: ■ Account Contact ■ Account Address ■ Account Industry ■ Account Industry ■ Account Organization ■ Account Organization ■ Account Position ■ Account Territory ■ Account Territory ■ Assignment Group ■ Industry Contact The following business object The following business object components are added: components are added: ■ Account Contact ■ Account Contact ■ Business Address ■ Contact Address ■ Contact Organization ■ Contact Organization ■ Opportunity Contact ■ Opportunity Contact ■ Organization ■ Position Employee The following business object components are added to Siebel Business Applications and Siebel Industry Applications: ■ Employee Position ■ Employee Responsibility Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 14 9
  • 150. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesTable 9. Changes Made as a Result of Importing the BusinessObject-Update.sif File Business Object Siebel Business Applications Siebel Industry Applications Opportunity The following business object components are added to Siebel Business Applications and Siebel Industry Applications: ■ Assignment Group ■ Opportunity AssignmentGroup ■ Opportunity Position Position The following business object components are added to Siebel Business Applications and Siebel Industry Applications: ■ Assignment Group ■ Assignment Group Position IntersectionChanges Made as a Result of Importing the Table-Update.sif FileTable 10 describes changes made to the S_EVT_ACT table as a result of importing the Table-Update.sif file.Table 10. Changes Made as a Result of Importing the Table-Update.sif File Siebel Business Applications Siebel Industry Applications Adds the following columns to the S_EVT_ACT Makes the following changes to the S_EVT_ACT table: table: ■ INTEGRATION_ID ■ Changes the length of the INTEGRA TION_ID column from 30 to 450 ■ INFO_SOURCE_CD ■ Adds the INFO_SOURCE_CD columnChanges Made as a Result of Importing the BusinessComponent-Update.sif FileTable 11 describes changes made to business components as a result of importing theBusinessComponent-Update.sif file. Note that these changes apply to Siebel Business Applicationsand 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 forSiebel Industry Applications.Table 11. Changes Made as a Result of Importing the BusinessComponent-Update.sif File Business Component Change to Business Component Field Action Adds the new CRMD Integration Id field. Employee Adds the new ContactDBLastUpd field. Changes the Text Length of the EMail Addr field from 50 to 100.150 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 151. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesTable 11. Changes Made as a Result of Importing the BusinessComponent-Update.sif File Business Component Change to Business Component Field Contact Changes the Text Length of the Email Address field from 50 to 100. Position Changes the Text Length of the Active Email field from 50 to 100. Business Address Changes the Text Length of the Email Address field from 50 to 100.Instructions for ACR 467Use the procedures in the following section to configure ACR 467.NOTE: For more information about ACR 467 and about Siebel Financial Services Customer OrderManagement for Banking functionality, see Siebel Order Management Guide Addendum for FinancialServices. To access this guide, from within My Oracle Support, navigate to the Knowledge tab andsearch for Doc ID 1171542.1.1 Navigate to <Tools installation folder>REPPATCHACR467.zip. The ACR 467 folder contains the following subfolders: ■ LMU ■ SeedData ■ REPOSITORY ■ WORKFLOWS ■ Schema2 Lock the following projects: ❏ Table A sset ❏ Table Closing Requirement Manager ❏ Table FinancialServices ❏ Table FinAccounts ❏ Table M arketing ❏ Table Order ❏ Table Q uote3 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.6 Choose the Current Query option. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 15 1
  • 152. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates7 In the Apply Schema dialog box, enter the appropriate values for your database platform. a For MSSQL, enter the app ropriate values in the Database user, Database user password, and the ODBC data source fields. b For Oracle, enter the appropriate values in the Table space, Index space, Database user, Database user password, and the ODBC data source fields. c For DB2, enter the appropriate values in the Table space, 16K table space, 32K table space, Index space, Database user, Database user password, and ODBC data source fields. d For DB2/390, enter storage control file information, as well as information in the Database user, Database user password, and ODBC data source fields. NOTE: If you are implementing ACR 467 on DB2, you need to generate the storage control file. For information aobut how to do this, see Implementing Siebel Business Applications on DB2 for z/OS. This guide is available on the Siebel Bookshelf at http://www.oracle.com/technetwork/ documentation/siebel-087898.html.8 Verify that the changes have been applied to the database.CAUTION: You must import the Table.sif file before you import the EIM.sif file.9 Lock the following projects: ❏ EIM Activity ❏ EIM Common SIA ❏ EIM Quote10 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 ❏ Contact152 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 153. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ❏ Contact (SSE) ❏ FINS Account Origination (Create this project if it does not already exist.) ❏ FINS Financial Services ❏ FINS Mortgage Application ❏ FINS Needs Analysis ❏ FINS Requirement Template ❏ FINS Retirement Planning ❏ Household ❏ LS Pharma Call ❏ LS Pharma Signature ❏ MACD Performance ❏ Oppty (SSE) ❏ Order Entry ❏ Product Selection UI ❏ Quote ❏ Quote (UI) ❏ SIS OM Base Architecture ❏ Symbolic Strings ❏ Corresp ❏ Account ❏ Mail Agent ❏ Accessibility ❏ FINS Captive Finance - Fin Acct ❏ LS Pharma Compliance ❏ PUB Case ❏ Schema ❏ Product Data Services15 Import the rest of the SIF files from the 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: ❏ Applet Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 15 3
  • 154. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates ❏ Application ❏ Business Component ❏ Business Object ❏ Business Service ❏ Integration Object ❏ Project ❏ Screen ❏ Symbolic String.Use the following procedure to perform batch import of the SIF files.154 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 155. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesTo 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" %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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 15 5
  • 156. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesTo import ACR 467 seed data1 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: 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 y /e n /t n /x R /n 100 /h log <Tools Install Directory> - Replace with your Siebel Tools install directory <ODBC Source Name> - Replace with ODBC name created in Step 1. b Review the <Tools Install Directory>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 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 1156 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 157. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates 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 <T able 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 <T ools 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.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>eappwebPUBLICenu10 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: New/ Process Name Modified? Project FINS AcctOrig Apply For Product - Account New FINS Account Origination FINS AcctOrig Apply For Product - Contact New FINS Account Origination FINS AcctOrig Apply For Product - Household New FINS Account Origination FINS AcctOrig AutoQuote New FINS Account Origination FINS AcctOrig Identity Check Process New FINS Account Origination FINS AcctOrig New Products & Services Process New FINS Account Origination FINS AcctOrig Profile Process - Order New FINS Account Origination FINS AcctOrig Set Applicant Group - Order Sub New FINS Account Origination Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 15 7
  • 158. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates New/ Process Name Modified? Project FINS AcctOrig Set Applicant Group - Order New FINS Account Origination FINS AcctOrig Set Applicant Group - Quote Sub New FINS Account Origination FINS AcctOrig Set Applicant Group - Quote New FINS Account Origination SIS OM Active Order Sub-Process - Contact Modify SIS OM Base Architecture SIS OM Disconnect Products & Services Proce - ss Modify SIS OM Base Architecture Contact SIS OM Modify Products & Services Process - Modify SIS OM Base Architecture Contact SIS OM New Products & Services Process - Modify SIS OM Base Architecture Contact SIS OM Suspend / Resume Products & Services Modify SIS OM Base Architecture Process - Contact a Select Workflow Process in Siebel Tools Object Explorer. b Right-click on Workflow Processes (the right-side pane) and import the .xml file into Siebel Tools from the Workflows folder. Refer to the list of workflows in the preceding table to know which project these workflows need to be imported into. c Check the status of the workflow process. If it In-Progress, then make it complete by deploying is the Workflow process. Do not click the Deploy + Activate button, as doing so will yield an error message. Click the Deploy button only. NOTE: You may receive the "This is an invalid Workflow…" error message while deploying the modified workflows from the list. Ignore the error and click Yes. d Repeat Step b through Step c for of all the workflows in the folder. e Log into the Siebel application as an administrator. f Navigate to Site Map > Administration - Business Process > Workflow Deployment > Repository Workflow Process. g Query for the workflow processes and activate them.Instructions for ACR 468The following section contains information about how to install ACR 468.For more information about Siebel Client Sync functionality, see Siebel Client Sync Guide on theSiebel Bookshelf http://www.oracle.com/technology/documentation/siebel.html.158 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 159. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesPrerequisites for ACR 468Before installing the Siebel Client Sync software, make sure that you have completed the followingtasks: ■ Before you install Client Sync SDK7.x, it is recommended that you unregister Intellisync SDK5.5 dlls if they are installed. ■ Client machine should have msxml 4.0 sp2 or higher version.The following files are associated with this ACR : ■ ENU_Installer.zip from <Siebel Tools path>REPPATCH which contains: ❏ vcredist_x86.exe ❏ setup.exe ❏ SiebelClientSync.msiBefore you begin your installation, copy the translation.txt file from the <New Client Sync>binenudirectory and replace the existing one under <Siebel Server Base>siebsrvrbinenu with the copy.Unregistering SDK 5.5 SDK1 Before installing the new Siebel Client Sync on top of Siebel Client Sync, unregister the dlls specific to Intellisync 5.5 SDK as mentioned below: The following examples show how to unregister each of the Intellisync connectors from the command line. In the examples, replace "$(SiebelRoot)" with the appropriate path to th Siebel e Client Sync product directory. ■ Microsoft Outlook ❏ regsvr32.exe /u "$(SiebelRoot)binconnectorsMS_Outlook_ConnectorilxolkCompanion.fil" ■ Lotus Notes ❏ regsvr32.exe /u "$(SiebelRoot)binconnectorsLotus_Notes_Connectorilxlnic.dll" ■ Palm OS handheld device ❏ regsvr32.exe /u "$(SiebelRoot)binconnectorsPilot_ConnectorPilotConnector.fil" ■ GroupWise ❏ regsvr32.exe /u "$(SiebelRoot)binconnectorsGroupwise_6.5.x_ConnectorGWEMAILCONN.dll" ❏ regsvr32.exe /u "$(SiebelRoot)binconnectorsGroupwise_6.5.x_ConnectorGWEMAILCONNApi.dll" Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 15 9
  • 160. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates2 Unregister the Siebel Client Sync COM servers by issuing the following commands from the command line: regsvr32 /u cxlserver.dll regsvr32 /u sscpumaconn.dll regsvr32 /u stcpumaapi.dllInstalling the Siebel Client Sync Software1 Within <Siebel Tools path>REPPATCH, unzip the ENU_Installer.zip file. NOTE: If you are installing a language other than ENU, select your language from the appropriate directory. For example, a customer who is installing the DEU application would use DEU_Installer within binDEU.2 Double-click on vcredist_x86.exe to install Microsoft Visual Studio 2005 redistributables.3 Double-click on setup.exe to install the new Siebel Client Sync application. When you are prompted to give the folder path for installing new Siebel Client Sync, accept the default path or give a path other than the original Siebel Sync 8.1.1.1 installation path. For example: If Siebel Sync 8.1.1.1 is installed in D:SiebelSync, then install ACR 468 for Siebel Sync in D:ACR468B.4 After the new Siebel Client Sync application is installed, double-click on the Siebel Client Sync shortcut that was created during the installation and provide the User ID, Password, and Connect String.Instructions for ACR 471For information about how to configure ACR 471, see Siebel Order Management Guide. This guide isavailable on the Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.Instructions for ACR 474 and ACR 508This section provides information, instructions, and guidelines for installing ACR 474 and ACR 508.CAUTION: Before you apply ACR 474, you must apply scehma changes and import seed data fromACR 463. Repository changes for ACR 474 include repository changes that were made in ACR 463.This section includes the following topics:■ Release Notes for ACR 474 and ACR 508Release Notes for ACR 474 and ACR 508The following section documents known issues with ACR 474 and ACR 508.160 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 161. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesUnable to Merge Contacts after Applying Siebel OnDemand/OnPremiseCategory: Data QualitySubcategory: DeduplicationProduct Version: 8.1.1.4Change Request: 12-204Y58XWhile 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 notpresent 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 HEADERFIELDCategory: Comm Media EnergySubcategory: Order ManagementProduct Version: 8.1.1.4Change Request: 12-1XTI4Q6MOVE 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_UTCDATETIME3 In MACD Quote, add a field with the following values: ❏ Name: As Of Date ❏ Column: STATUS_DT ❏ Type: DTYPE_UTCDATETIME Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 16 1
  • 162. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates4 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 CANCELORDERCategory: Comm Media EnergySubcategory: Billing ManagementProduct Version: 8.1.1.4Change Request: 12-1ZVR997CLEAR FULFILLMENT STATUS AND STATUS CONTEXT FOR CANCEL ORDER1 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 number3 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 Fie Argument tab in the Multi- alue Property Window for the Update Fulfillment ld V Mode and Status for Header operation step, add the following two new records to configure the input arguments: Field Name Type Value Fulfillment Status Code Literal Back Office Error Text Literal6 Add a new Siebel Operation Step between "Update Fulfillment Mode and Status for Header" (Siebel Operation Step) and "Submit" (Sub Process).162 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 163. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates7 Right-click, select View Properties Window and modify the properties of the Siebel Operation Step as follows: Business Component Order Entry - Line Items Business Component Order Entry - Line Items Operation Update Name Update Fulfillment Status and Status Context for Line Items8 Under the Input Field Argument tab in the Multi-Value Property Window for the preceding step, add the following new records to configure the input arguments: Field Name Type Value Fulfillment Status Code Literal Status Context Literal9 Under the Search Spec Input Arguments tab in the Multi-Value Property Window for the preceing step, add the following new records to configure the search specification:E xpression Business Filter Business Component Component Type Search Specification Order Entry - Orders Order Entry - Line Expression "[Order Header Id] =" Items + [&Object Id] + ""10 Save all of your cha nges and publish/activate the workflow.PROBLEM WITH ADJUSTMENT EFFECTIVE DATECategory: Comm Media EnergySubcategory: Billing ManagementProduct Version: 8.1.1.4Change Request: 12-1ZOI2LPThe Effective Adjustment field stores only the Date field not the time value.Use the following workaround to address this issue:Before you begin, within My Oracle Support, navigate to the Knowledge tab and search for Doc ID557191.1. Copy the FR_12-1ZV9SD1_AIA25_Invoice.sif file attached to the article.Table ChangesUse the following procedure to edit the S_INV_ADJ table. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 16 3
  • 164. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesTo edit the S_INVOICE_ADJ table1 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 ChangesTo edit the CMU Billing Invoice Adjustment BC1 Log into Siebel Tools, and query for the CMU Billing Invoice Adjustment business component.2 Change the following column for the Adjustment Effective Date field for the business component: Name Value Type DTYPE_UTCDATETIME3 Save the changes, and then compile them to the SRF.To edit the CMU Invoice Adjustment BC1 Log into Siebel Tools, and query for the CMU Invoice Adjustment business component.2 Change the following column for Adjustment Effective Date field: Name Value Type DTYPE_UTCDATETIME3 Save the changes, and then compile them to the SRF.To edit the FS Invoice Adjustment BC1 Log into Siebel Tools, and query for the FS Invoice Adjustment business component.2 Change the following column for the Adjustment Effective Date field: Name Value Type DTYPE_UTCDATETIME3 Save the changes, and then compile them to the SRF.164 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 165. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesTo edit the SIA Invoice Adjustment External Items BC1 Log into Siebel Tools, and query for the SIA Invoice Adjustment External Items business component.2 Change the following column for the Adjustment Effective Date field: Name Value Type DTYPE_UTCDATETIME3 Save the changes, and them compile them to the SRF.To edit the CMU Billing Invoice Adjustment External Items BC1 Log into Siebel Tools, and query for the CMU Billing Invoice Adjustment External Items business component.2 Change the following column for the Adjustment Effective Date field: Name Value Type DTYPE_UTCDATETIME3 Save your changes, and then compile them to the SRF.To edit the CMU SIA Invoice Adjustment External Items BC1 Log into Siebel Tools, and query for the CMU SIA Invoice Adjustment External Items business component.2 Change the following column for the Adjustment Effective Date field: Name Value Type DTYPE_UTCDATETIME3 Save the changes, and then compile them to the SRF.To edit the CMU Invoice Adjustment External Items BC1 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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 16 5
  • 166. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates3 Save your changes, and then compile them to the SRF.Integration Object ChangesTo edit the CMU Request Adjustment IO1 Log into Siebel Tools, and query for the CMU Request Adjustment integration object.2 Query for FS Invoice Adjustment integration component.3 Change the type for the Adjustment Effective Date integration component field: Name Value Data Type DTYPE_UTCDATETIME External Data Type DTYPE_UTCDATETIME4 Query for the SIA Invoice Adjustment External Items integration component.5 Change the following Data Type for the Adjustment Effective Date integration component field: Name Value Data Type DTYPE_UTCDATETIME External Data Type DTYPE_UTCDATETIME6 Save your changes, and then compile them to the SRF.To edit the CmuRequestAdjustmentIo IO1 Log into Siebel Tools, and query for the CmuRequestAdjustmentIo integration object.2 Query for the FS Invoice Adjustment integration component.3 Change the type for the Adjustment Effective Date integration component field: Name Value Data Type DTYPE_UTCDATETIME External Data Type DTYPE_UTCDATETIME4 Query for the SIA Invoice Adjustment External Items integration component.166 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 167. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates5 Change the Data Type for the "Adjustment Effective Date integration component field: Name Value Data Type DTYPE_UTCDATETIME External Data Type DTYPE_UTCDATETIME6 Save your changes, and then compile them to the SRF.PRODUCT SYNC FAILS FROM SIEBEL TO BRMArea: Comm/EnergySubarea: Order ManagementProduct Version: Siebel 8.1.1.3 Fix PackChange Request: 12-1YOWCOT/Bug # 9851535In 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-1YOWCOT1 From within the Siebel application, navigate to Site Map > Adm inistration 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 ReleasedArea: Comm/EnergySubarea: Order ManagementProduct Version: Siebel 8.1.1.3 Fix Pack Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 16 7
  • 168. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesChange Request: 12-1YK6RG0Use the following workaround to address this issue.To address CR 12-1YK6RG01 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 MemoryCategory: Comm Media EnergySubcategory: Order ManagementProduct Version: Siebel 8.1.1.1 QF7103Change Request: 12-1Y0AZBZSiebel workflow process manager leaks memory and crashes in performance, scalability, andreliability (PSR) testing after 20 hours of running with zero seconds of think time.Workaround: Enable memory-based recycling on workflow process manager. For information aboutconfiguring memory-based server component recycling, refer to Siebel System Administration Guideon the Siebel Bookshelf at http://www.oracle.com/technology/documentation/siebel.html.Error Messages Translated IncorrectlyCategory: Comm Media EnergySubcategory: Order ManagementProduct Version: Siebel 8.1.1.1 QF7103Change Request: 12-1VBS4SZ, 12-1VBS4UF, 12-1VBS4VLTo address CR 12-1VBS4SZ, CR 12-1VBS4VL, and CR 12-1VBS4VL1 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_QUOTE2 Add the missing translations in the Translations applet.168 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 169. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesFollow-On Orders Can Be Submitted Before Base OrdersCategory: Comm Media EnergySubcategory: Order ManagementProduct Version: Siebel 8.1.1.1 QF7103Change Request: 12-1XTI4LPNo error occurs when a Follow On order is submitted after the Base Order is cancelled.To address CR 12-1XTI4LP1 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 OrdersCategory: Comm Media EnergySubcategory: Order ManagementProduct Version: Siebel 8.1.1.1 QF7103Change Request: 12-1XTI4NOFollow-On orders can be submitted for Cancelled Base Order.To address CR 12-1XTI4NO1 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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 16 9
  • 170. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesSales Order Form Buttons Not Disabled After Cancel Order StartsCategory: Comm Media EnergySubcategory: Order ManagementProduct: Siebel 8.1.1.1 QF7103Change Request: 12-1XTI4UEAfter 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-1XTI4UE1 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 operator5 Compile the changes.COPY ORDER DOES NOT ASSIGN NEW ASSET INTEGRATION ID FORCOPIED ORDERSCategory: Comm Media EnergySubcategory: Order ManagementProduct Version: Siebel 8.1.1.1 QF7103Change Request: 12-1XVFM9RTo 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.170 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 171. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates■ CR 12-1TU8OYZ Description: The Discount Override fix is not working in MACD for Non-Residential Accounts (asset-quote). Workaround: Contact Technical Support for the workaround for this issue.■ CR 12-1TK6WV1 Description: Suspend/Resume and move charges are applied to Simple Service Bundles in Nested SBs after reprice. Workaround: Use Reprice to see all charges.■ Bug # 8979872/CR 12-1UPWTKJ Description: Error upon clicking the Revise button within Sales Order > Line Items tab. Workaround: Use the following procedure to address this issue.To address Bug #8979872/CR 12-1UPWTKJ1 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-1UVNZ651 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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 17 1
  • 172. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates■ CR 12-1UK1DKW Description: The Cancel Error Mode system preference default value should be 3. Workaround: Use the following workaround to address this issue.To address CR 12-1UK1DKW1 Within the Siebel application, navigate to Administration - Application > System Preferences.2 Within the System Preference Name field, query for “Cancel Error Mode” and set the v alue 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-1T03IG91 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 Records6 Activate the ruleset.7Unpacking the AIA251.zip File1 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.172 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 173. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ■ ACR474_Workaround. This file contains the Release Notes and workaround information. ■ 8113_Addendum.3 Unzip the ACR474.zip file. This will create the following directory structure: <Tools Install Directory>REPPATCHAIA251ACR474 The ACR474 folder that you create will contain the following subfolders: ■ DMGSchemaChanges ■ EIM ■ HTML ■ LMU ■ SeedData ■ SIFFiles ■ WebTemplates ■ WFsUse 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 DatabaseAs 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 andACR463_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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 17 3
  • 174. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates■ S_ORDER_ITEM■ S_ORG_EXT■ S_PROD_INT■ S_QUOTE_ITEM■ S_SRV_ORD_FAIL■ S_SRV_REQ■ S_SPL_RATE_ITEM■ S_SPL_RATE_LSTTo import the ACR463_Tables.sif file into the repository1 Lock the following projects before import: ❏ CUT Newtable ❏ Table A sset ❏ Table BulkRequest ❏ Table I nvoice ❏ Table Order ❏ Table Organization ❏ Table Product ❏ Table Q uote ❏ Table Service Request ❏ Table Special Rate List ❏ Table C IF ❏ Table FleetManagement ❏ Table P erson2 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 databaseThe tables have to be in the repository before creating this on the physical database. Use Siebel toolsand query for the list of tables that were imported into the repository. Use the "Apply/DDL" buttonto apply the changes to the physical database, and provide the correct database user (table ownername, password, and ODBC data source).The ACR463_EIMTables.sif file has all the changes for the following:Changes to existing tables:■ EIM_ASSET174 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 175. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates■ EIM_ASSET1■ EIM_ALERT_CUT■ EIM_INVOICE■ EIM_ORDER■ EIM_ORDER1■ EIM_ORDER_ITEM1■ EIM_PROD_INT1■ EIM_QUOTE■ EIM_QUOTE_IT1To import the ACR463_EIMTables.sif file into the repository1 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 Request2 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 ChangesAs part of the ACR474 release, schema changes have been done on the database. TheREPPATCHAIA251ACR474DMGSchemaChangesACR474_Tables.sif has all the changes for thefollowing:Changes to existing tables:■ S_ASSET■ S_CONTACT Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 17 5
  • 176. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates■ S_CONTACT_BU■ S_DOC_QUOTE■ S_OPTY■ S_OPTY_BU■ S_ORDER■ S_ORDER_ITEM■ S_ORDER_ITEM_OM■ S_ORDER_STOP■ S_ORDPART_MVMT■ S_ORG_BU■ S_ORG_EXT■ S_ORG_GROUP■ S_PRI_LST■ S_PRI_LST_ITEM■ S_PROD_INT■ S_PROD_INT_BU■ S_QUOTE_ITEM■ S_REVN■ S_UCM_ADDR_PER■ S_UCM_ASSET■ S_UCM_CONTACT■ S_UCM_ORGGRP■ S_UCM_ORG_EXT■ S_UCM_PRIVACYNew Tables:■ S_INTG_DEL_TXN■ S_ORG_GRP_UCMX■ S_PRD_USRDEFATRTo import the ACR_474_Tables.sif file into the repository1 Lock the following projects before import: ❏ Table A sset ❏ Table C IF176 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 177. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ❏ Table FieldService ❏ Table FleetManagement ❏ Table Forecast ❏ Table H ousehold ❏ Table NetworkOrderManagement ❏ Table OnPremise-OnDemand ❏ Table O pty ❏ Table Order ❏ Table Organization ❏ Table P erson ❏ Table PriceList ❏ Table Product ❏ Table Q uote2 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 databaseThe tables have to be in the repository before creating this on the physical database. Use Siebel toolsand query for the list of tables that were imported into the repository. Use the "Apply/DDL" buttonto apply the changes to the physical database.Applying EIM ChangesAs part of the ACR474 release, EIM changes have been done on the database. TheREPPATCHAIA251ACR474DMGSchemaChangesACR474_EIMTables.sif file has all the changes forthe following:Changes to existing tables:■ EIM_ACCOUNT■ EIM_ACCOUNT1■ EIM_ASSET1■ EIM_CONTACT■ EIM_CONTACT2■ EIM_GROUP■ EIM_GROUP_DTL■ EIM_OPTY■ EIM_OPTY_DTL Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 17 7
  • 178. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates■ EIM_ORDER1■ EIM_ORDER_FM■ EIM_ORDER_ITEM■ EIM_ORDER_ITEM1■ EIM_ORD_ITEM2■ EIM_ORG_BU■ EIM_ORG_INT■ EIM_PART_MVMT■ EIM_PRI_LST■ EIM_PROD_INT■ EIM_PROD_INT1■ EIM_PROD_INT_BU■ EIM_QUOTE1■ EIM_QUOTE_IT2■ EIM_REVN■ EIM_UCM_ADRPER■ EIM_UCM_ASSET■ EIM_UCM_CON■ EIM_UCM_ORG■ EIM_UCM_ORGGRP■ EIM_UCM_PRIVCYTo import the ACR_474_EIMTables.sif file into the repository1 Lock the following projects before import: ❏ EIM Asset ❏ EIM CIF ❏ EIM Common SIA ❏ EIM FieldService ❏ EIM FleetManagement ❏ EIM Forecast ❏ EIM Household ❏ EIM Opty ❏ EIM Order178 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 179. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ❏ EIM Organization ❏ EIM Person ❏ EIM PriceList ❏ EIM Product ❏ EIM Quote2 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 databaseThe tables have to be in the repository before creating this on the physical database. Use Siebel toolsand query for the list of tables that were imported into the repository. Use the "Apply/DDL" buttonto apply the changes to the physical database.Importing Seed Data for ACR 463NOTE: 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 either Step a or Step b depending upon the language that you are installing. a Use the following command to import mono-language seed data: <ToolsInstall Directory>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. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 17 9
  • 180. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates 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 4741 Create an ODBC entry for the database where you plan to import the seed data. a Navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC) > System DSN tab, and click Add. b Select the Siebel Oracle90 driver (from Datadirect Technologies). c Enter a data source name (such as DevelopmentDB). d Enter the server name to connect to: e For Oracle, enter the TNS service name that you created to connect Siebel Tools to the database. f Test your connection and click OK when tested successfully2 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 <T able 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 XX or Step XX.6 For ENU (English Language) customers:180 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 181. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates 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: 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 FilesAs part of the ACR474 release, the EIM files - eim45.sql and eim_export_lookup_bu_name.sql havebeen changed. The REPPATCHAIA251ACR474EIMeim45.sql andREPPATCHAIA251fACR474EIMeim_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 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 18 1
  • 182. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updateseim_export_lookup_bu_name.sql : <Installation Location>SERVERsiebsrvrADMINSiebel Tools Changes for ACR 4741 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 Ticket182 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 183. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ■ Contact ■ Contact (SSE) ■ Comm Manager ■ Communication ■ Division ■ Dock ■ Dock KDI ■ Docklog ■ Dockses ■ Eligibility Compatibility ■ EIM Asset ■ EIM CIF ■ EIM Household ■ EIM Organization ■ EIM Person ■ EIM Common SIA ■ EIM Invoice ■ EIM Order ■ EIM Product ■ EIM Quote ■ EIM BulkRequest ■ EIM Organization ■ EIM Service Request ■ Employee ■ FS Agreement ■ Fleet Management ■ ISS Authoring Admin ■ ISS Class Admin ■ ISS Context ■ ISS Order Management ■ ISS Product Admin ■ ISS Promotion Admin ■ ISS Promotion Integration Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 18 3
  • 184. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates ■ ISS Promotion Workflow ■ ISS VOD Import Export ■ ISS VOD Loader ■ LS DB Action ■ MACD Performance ■ Order Entry ■ Opportunity Management ■ Oppty ■ Oppty (SSE) ■ PMP ■ Prepaid Service 8.1 ■ Price List ■ Product ■ Product (SSE) ■ Product Integration ■ Product Selection UI ■ Quote (UI) ■ Quote ■ Row Set Transformation Toolkit ■ SIS OM Base Architecture ■ Service ■ Siebel Sales Enterprise ■ Siebel High Tech ■ Siebel Universal Agent ■ Srvagree ■ Srvagree (SSV) ■ Symbolic Strings ■ Template ( Order) ■ Table A sset ■ Table BulkRequest ■ Table Invoice ■ Table Order ■ Table Organization184 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 185. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ■ Table Product ■ Table Promotions ■ Table Quote ■ Table Service Request ■ Table Special Rate List ■ Table C IF ■ Table P erson ■ Table FleetManagement ■ Table FieldService ■ Table Forecast ■ Table H ousehold ■ Table NetworkOrderManagement ■ Table O pty ■ Table PriceList ■ Table OnPremise-OnDemand ■ UCM Privacy Management ■ UMSUI ■ VEAI CUT Billing Integration ■ VERT CUT Address ■ VERT CUT Common ■ VERT CUT Screens ■ Web Channel Order Management ■ Web Service Integration ■ Workflow Policy ■ eService Billing ■ eAuto Product NOTE: If you have implemented ACR 471, you must merge repository and workflow changes to make sure that ACR 471 and ACR 474 are compatible: ❏ Business Service - ISS Promotion Management Service.sif ❏ Workflow - ISS Promotion Upgrade Process.xml3 Import the rest of the SIF files from the SIFFiles folder into Siebel Tools: Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 18 5
  • 186. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates 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. 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 > Option > Scripting tab, and specify the following s path for the Browser script compilation folder. <Server IP address><SWE server Installed Location>eappwebPUBLICenu7 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 folderinto the SWE Server <SWEServer 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.186 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 187. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ■ Import the "SWISendQuote" workflow first and then import the "Submit Quote ASI" workflow. ■ Import the "Oracle Configurator Load" workflow first and then import the "SWI Configurator Load" workflow. ■ Import the "SWIOrderUpsertSubProcess" workflow first and then import "SWIOrderUpsert" workflow Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 18 7
  • 188. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates ■ Import the "SWISetTBOEndDate" workflow first and then import the "Dynamic Pricing Procedure" workflow. Workflow Name Project *SIS OM Disconnect Asset Sub-process SIS OM Base Architecture *SIS OM Move Process SIS OM Base Architecture ABO Bulk Request -Validate Process ABO Bulk Request ABO Bulk Request - Clear Exception Process Workflow ABO Bulk Request ABO Bulk Request - Parallel Sub Process Workflow ABO Bulk Request ABO Bulk Request - Prepare Action Set Sub-Process Workflow ABO Bulk Request ABO Bulk Request - Submit Process Workflow ABO Bulk Request ABO Bulk Request Add Item Customize Process ABO Bulk Request Account - New Order COM Workflows Basic Pricing Procedure Cfg RTC CMU Credit Alert Status Sync Web Service Integration CMU SIA Submit Adjustment Request to External CMU Billing Integration CMUBalanceDetailsEventAdjustmentWF CMU Billing Integration CMUEventDetailsAdjustmentWF CMU Billing Integration CMUInvoiceAdjustmentWF CMU Billing Integration CMUItemChargeAdjustmentWF CMU Billing Integration CMUUnbilledEventAdjustmentWF Web Service Integration CMUUnbilledNonCurrencyEventAdjustmentWF Web Service Integration CZ PSP Interface Web Service Integration CZ Return Web Service Integration Dynamic Pricing Procedure Row Set Transformation Toolkit ISS Promotion Disconnect Process ISS Promotion Workflow ISS Promotion Upgrade Process ISS Promotion Workflow Oracle Configurator Load Web Service Integration Oracle Verify Complex Product All (Order) Web Service Integration Oracle Verify Complex Product All (Quote) Web Service Integration Pricing Procedure - Calculate Net Price Row Set Transformation Toolkit SIA External Integration Process Prepaid Service 8.1 SIS OM Add Service Charge Order Sub-Process SIS OM Base Architecture SIS OM Add Service Charge Quote Sub-Process SIS OM Base Architecture188 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 189. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates Workflow Name Project SIS OM Add Service Charge Sub-Process SIS OM Base Architecture SIS OM Disconnect Products & Services Process SIS OM Base Architecture SIS OM Edit Complex Asset Workflow SIS OM Base Architecture SIS OM Edit Delta Quote Line Item SIS OM Base Architecture SIS OM Edit Service Order Line Item SIS OM Base Architecture SIS OM Modify Products & Services Process SIS OM Base Architecture SIS OM Order Line Item Update Main SIS OM Base Architecture SIS OM Submit Order Process SIS OM Base Architecture SIS OM Suspend / Resume Asset Sub-Process SIS OM Base Architecture SIS OM Suspend / Resume Products & Services Process SIS OM Base Architecture SISOMBillingSubmitOrderWebService CMU Billing Integration Submit Order ASI COM Workflows Submit Quote ASI COM Workflows SWI Account Update Workflow Web Service Integration SWI Address Update Workflow Web Service Integration SWI Asset Status Update CMU Billing Integration SWI Billing Profile Update Workflow Web Service Integration SWI Cancel Sales Order Line Item Web Service Integration SWI Cancel Sales Order_O2C Web Service Integration SWI Configurator Load Web Service Integration SWI Contact Update Workflow Web Service Integration SWI External Account Integration Process Web Service Integration SWI External Account Request Sync Process Web Service Integration SWI External Contact Integration Process Web Service Integration SWI External Contact Req Integration Process Web Service Integration SWI External Contact Request Sync Process Web Service Integration SWI External Customer Req Integration Process Web Service Integration SWI External Product Sync Workflow Web Service Integration SWI Initial Load Non CP Order Release Web Service Integration SWI Parent Order Web Service Integration SWI Special Rating - Synchronize Process Web Service Integration SWI TSQ Order Web Service Integration Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 18 9
  • 190. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates Workflow Name Project SWIAdjustmentStatusUpdate Web Service Integration SWICancel Sales Order Web Service Integration SWICopyOrder Web Service Integration SWIOrderUpsert Web Service Integration SWIOrderUpsert_O2C Web Service Integration SWIOrderUpsertSubProcess Web Service Integration SWIQuoteUpsert Web Service Integration SWIReviseOrderValidation Web Service Integration SWISendATPCheck Web Service Integration SWISendATPCheckLine Web Service Integration SWISendCalculateShippingCharge Web Service Integration SWISendCreditCheck Web Service Integration SWISendOrder Web Service Integration SWISendPaymentAuthorization Web Service Integration SWISendQuote Web Service Integration SWISetTBOEndDate CMU Billing Integration SWIValidateDependentOrders Web Service Integration Verify Header (Order) COM Workflows Verify Item (Order) COM WorkflowsNOTE: The asterisks denote workflows that were not modified for ACR 474. a Select Workflow Process in Siebel Tools Object Explorer. b Right-click on the right side pane called Workflow Processes and import the .xml file into Siebel Tools from the Workflows folder. Refer to the list of workflows in the table above to know which project these workflows need to be imported into. NOTE: The following step is required if you have installed AIA 2.5 IPS 1 or higher. Revise the following workflows, change the Process Property ‘UTCCanonical’ default value from ‘N’ to ‘Y’. Publish, and then activate. ❏ CMU Credit Alert Status Sync ❏ CMU SIA Submit Adjustment Request to External ❏ SISOMBillingSubmitOrderWebService ❏ SWI Account Update Workflow ❏ SWI Billing Profile Update Workflow190 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 191. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ❏ SWI Contact Update Workflow ❏ SWI Address Update Workflow ❏ SWI Cancel Sales Order_O2C ❏ SWI External Account Request Sync Process ❏ SWI External Contact Request Sync Process ❏ SWI Special Rating - Synchronize Process ❏ SWIAdjustmentStatusUpdate ❏ SWIOrderUpsert ❏ SWIOrderUpsert_O2C ❏ SWIOrderUpsertSubProcess ❏ SWIQuoteUpsert ❏ SWISendATPCheck ❏ SWISendATPCheckLine ❏ SWISendCalculateShippingCharge ❏ SWISendCreditCheck ❏ SWISendOrder ❏ SWISendPaymentAuthorization ❏ SWISendQuote c Check the status of the Workflow process. If it is In-Progress, then make it complete by deploying the Workflow process. For Siebel applications version 8.0 and above, the button to mark the workflow status complete is Publish/Activate. To view this button, navigate to View menu > Tool Bar > WF/ Task E ditor. NOTE: If any of the workflows fail to import, manually activate them within the application. d Repeat Step b and Step c for of all the workflows in the folder. e Log in to the Siebel application as an administrator. f Navigate to the Site Map, and click Administration - Business Process. g Navigate to Workflow Deployment > Repository Workflow Process. h Query for the workflow processes and activate them. NOTE: It is recommended that you reload the runtime events after activating the workflows. i Navigate to Administration - Runtime Events > Events screen, select all records and then select Reload Runtime Events from the drop-down menu. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 19 1
  • 192. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates13 Import the rest of the SIF files from the SIF Files 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.14 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.sif15 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.16 Import and activate the workflows listed in the following table from AIA251ACR474_WorkaroundWFs into Siebel Tools: New/ Process Name Modified Project Pricing Procedure - Calculate Net Price Toolkit Modified Row Set Transformation SIS OM Edit Service Order Line Item Modified SIS OM Base Architecture a Within Siebel Tools > Object Explorer, select Workflow Process. b Right-click on the right side pane ‘Workflow Processes’ and import the .xml file into Siebel Tools from the WFs folder. Refer to the list of workflows in the preceding table to know which project these workflows need to be imported into. c Activate the workflows by clicking on “Deploy+ Activate” button to activate the workflows. d Repeat Step b and Step c c for of all the workflows in the folder.17 Import the rest of the SIF files from the SIFFiles folder 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.sif192 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 193. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ■ . 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.sif18 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.19 If the Table Promotions project is not already locked, lock it.20 Within Siebel Tools, query for the S_PRO_CFG_ITEM table.21 Use the "Apply/DDL" button to apply the changes to the physical database.22 Import the workflows listed in the following table into Siebel Tools and then activate the workflows. Process Name New/Modified Project SWI External Account Integration Process Modified Web Service Integration SWI External Contact Integration Process Modified Web Service Integration SWI External Contact Req Integration Process Modified Web Service Integration SWI External Customer Req Integration Process Modified Web Service Integration a Within Siebel Tools > Object Explorer, select Workflow Process. b Right-click on the right-side pane ‘Workflow Processes’ and import the .xml file into Siebel T ools from the Workflows folder. Refer to the list of workflows in the preceding table to know which project these workflows need to be imported into. c Click the “Deploy+ Activate” button to activate the workflows. d Repeat Step b and Step c for of all the workflows in the folder.23 Modify the run time events for promotions: a Navigate to the Administration - Runtime Events screen. b Click the Action Sets view. Three applets appear. c In the first applet, Action Sets, search for the Cache Refresh BC - ISS Promotion Pricing Components List Applet Action Set. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 19 3
  • 194. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates d For this Action Set, in the bottom form applet, there is a control with the Business Service Context label. For this control, the previous value was only "IS Promotion Pricing Components", S "ISS Promotion Pricing Rules Summary". Another newentry was added to this and now the v alue for this control is "IS Promotion Pricing Components", "IS Promotion Pricing R S S ules Summary", "Promotion Config Item". Note that there should be a space after the comma. [This step needs to be performed only if it is required.]24 Release the variable maps: a Navigate to Site Map > Admin - Order Management > Variable Maps, and query for the following: ❏ Default Pricing Variable Map - Row Set - Basic ❏ Default Pricing Variable Map - Row Set ❏ Default Pricing Eligibility Variable Map - Row Set b Release a new version of each of the above objects and then bounce the server.25 Release the signal: a Navigate to Site Map > Admin - Order Management > Signal and query for the ReviseCopyOrder signal. b Release a new version of the above object and then bounce the server.26 Enable component groups for order creation. NOTE: Bounce the server after enabling the compgrp and synchronizing it. a Navigate to Administration - Server Configuration > Enterprises > Component Groups and query for each of the following Component Groups and, if Enable State = Disabled, click <Enable>: ❏ SIA ❏ Siebel CME [Alias- Communications] ❏ Siebel ISS [Alias- ISS] ❏ Workflow Management [Alias- Workflow] ❏ HTIM ❏ EAI *Note through Srvrmgr Command Prompt - Enable compgrp <Alias> b After enabling the necessary components, navigate to Administration - Server Configuration > Enterprises > Synchronize. Select all the records and then click Synchronize.27 Activate workflows. a Navigate to Site Map > Administration Business Process > Workflow Deployment > Active Workflow Processes and in the second applet, complete one of the following tasks: ❏ Query for SIS*,Pri*,PSP*,ISS*,Elig*,eSales*.194 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 195. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ❏ Query for the following groups: Eligibility & Comp, Asset Based Ordering, Pricer, eSales, Product Promotions, Configurator, C/OM UI processes, CUT eSales (only for SIA, not for SEA), and Product Recommendation, and delete the groups manually after deactivating the processes. To deactivate these groups, select them all and then select Deactivate Process. You can check the Deployment Status as Inactive. b Delete all the records. c In the first applet, complete one of the following tasks: ❏ Query for SIS*,Pri*,PSP*,ISS*,Elig*,eSales*. ❏ Query for the following groups: Eligibility & Comp, Asset Based Ordering, Pricer, eSales, Product Promotions, Configurator, C/OM UI Processes, CUT eSales (only for SIA, not for SEA), and Product Recommendations, and then activate all the workflows.28 Restart the Siebel Server.29 Launch the Siebel Communications application.30 Complete the following steps for defining the end point URL for ABS (Outbound Webservices) a Log into the Siebel application as an administrator and navigate to the Site Map. b Select Administration - Web Service > Outbound Web Services. c Query for "*JMS* OR *ABCS* OR *ESB* OR *ConfiguratorUserLangSiebelAdapter* OR SyncCustomerSiebelEventAggregator" on the Name field of the Web Services applet. ❏ AdjustmentSiebelCommsReqABCS ❏ CalculateShippingChargeSalesOrderSiebelReqABCSImpl ❏ CheckATPSalesOrderSiebelReqABCSImpl ❏ ConfiguratorUserLangSiebelAdapter ❏ CreditCheckSalesOrderSiebelReqABCSImpl ❏ ESB_AccountBalanceSiebelCommsReqABCS_Service ❏ ESB_ConfiguratorCopyConfigEbizAdapter_Service ❏ ESB_InvoiceSiebelCommsReqABCS_Service ❏ ESB_UnbilledUsageSiebelCommsReqABCS_Service ❏ FetchAccountSiebelReqABCSImpl ❏ FetchContactSiebelReqABCSImpl ❏ MatchAccountSiebelReqABCSImpl ❏ MatchContactSiebelReqABCSImpl ❏ PaymentAuthorizationSalesOrderSiebelReqABCSImpl ❏ PaymentSiebelCommsReqABCS ❏ ProcessSalesOrderSiebelCommsJMSProducer ❏ RequestProductStructureSiebelJMSProducer Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 19 5
  • 196. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates ❏ SyncCustomerSiebelEventAggregator ❏ SyncInstalledProductListSiebelCommsReqABCSImpl ❏ UpdateCreditAlertSiebelCommsReqABCSImpl d Change the Address field for each outbound Web service to point to http:// ap6039fems.us.oracle.com:7797. e For Inbound Web Services, navigate to Administration - Web Services > Inbound Web Services, and make sure that the corresponding Web Services are active. If th are not, changethe status ey from "Inactive" to "Active" and click the Clear Cache button. NOTE: Query for these inbound web services --- * ISS *; * Update Order *; * SWI Update *, SWI*.Setting Up and Configuring Workflow PoliciesIn order to enable the workflow policies, the following components should be configured and runningon Siebel Server (in addition to the Application Object Manager component).Table 12. Siebel Component Groups Component Name Component Alias Component Group Enterprise Integration Mgr EIM EAI EAI Object Manager (ENU) EAIObjMgr_enu EAI Workflow Process Manager WfProcMgr Workflow Workflow Process Batch Manager WfProcBatchMgr Workflow Workflow Monitor Agent WorkMon Workflow Generate Triggers GenTrig WorkflowNOTE: Enabling the EAI and Workflow Component Groups in the Siebel Server will start all therequired 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 = TRUE1 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:196 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 197. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates ■ EXEC = TRUE ■ Privileged User = <Table Owner> ■ Privileged User Password = <Table Owner> ■ Remove = TRUE ■ Trigger File Name: trigger.sql4 Start the job.NOTE: If the job parameters do not appear when you query for them, then search for them in theAdvanced or Hidden section.Configuring Workflow Monitor Agent1 Navigate to Administration - Server Configuration > Enterprises > Component Definitions, and query for WorkFlow*.2 Make a copy of the Workflow Monitor Agent in Administration - Server Configuration -> Component Definition and change the name to "Workflow Monitor Agent SWI".3 Change the Alias name to WorkMonSWI.4 Change the Group Name to "SWI Customer Update Policy Grp" in the component Parameter applet (down). (Under Component Parameters query for "Group Name" and type the SWI Customer Update Policy Grp under Value).5 Change the Action Interval to a value 5.6 Change the Sleep Time to a value 15.7 Change the Default Task to 1.8 Change the status of the new component to "Active" by clicking Activate.9 Synchronize the components.Configuring Default Task for Workflow Monitor AgentServer Manager Parameter named Show Advanced Objects controls the display of all the objects thatare marked for the advanced user.Workflow Monitor Agent has a parameter called Default Tasks which has been hidden and shouldonly be displayed or available to advanced users. In order to reveal this hidden parameter, completethe following steps.To reveal hidden Default Tasks parameter1 Navigate to Administration - Server Configuration > Servers.2 In the top Siebel Servers applet, select the server on which you want to modify the parameter. Under the Component subtab, query for the Server Manager component.3 Under the Parameters subtab, query for Show Advanced Objects. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 19 7
  • 198. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates4 Change the value to True. NOTE: You must log out from your current user session and log bac into the application in order k for the parameter to take effect.5 Change the Default Task parameter to 1.Starting the Tasks for Workflow Monitor Agent for CustomerSynchronizationThis section describes the steps to start tasks for the component that is online/enabled.1 Navigate to Administration - Server Management and select Tasks.2 Query for the Task "WorkMonSWI" and Start Task. Alternatively, use Server Manager to start task.3 Start srvrmgr. srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u <userid> /p <password>4 Start task for component WorkMonSWI.To restart the server1 Stop the Siebel Server.2 Rename the existing diccache.dat file in the path <Installed Directory> sessiebsrvrbin.3 Restart the Siebel Server.Generating the TriggerMake sure that the User SADMIN has the necessary privileges for generating triggers before runningthis procedure.To generate the trigger1 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.sql198 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 199. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates4 Start the job. NOTE: If the job parameters information does not appear when you query for it, th search for en 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 198 and “To generate the trigger” on page 198.Enabling Required System PreferencesUse the following procedure to enable required system preferences.To enable required system preferences1 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 ma not function y as expected.5 Restart the Siebel Server. Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 19 9
  • 200. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and UpdatesSetting Up the Integration UserThis section describes the integration user setup process. We have introduced a new flag to identifyan integration user (needed while integration testing). This user credential needs to be configured(at AIA side) for the Siebel Inbound Web services call from AIA side to avoid the boomerang effect.The following procedures describe the process of setting up the integration user: Steps Expected Result Login as SADMIN Navigate to Administration-User Employee view The list applet should contain the integration user flag Configure a new integration user by setting the integration user flag to Y for a specific user.Setting Order Priority for AQUse the following procedure to set order priority for AQ.1 Navigate to the Administration - Data > List Of Values view.2 Query for Type equals SWI_ORDER_JMS_PRIO_MAPPING.3 Change the values in the Language-Independent Code column to define the new mapping as per following table: Display Value Language-Independent Code Low 6 Medium 4 High 2 Urgent 04 Click Clear Cache to clear the cache.Advanced Queue Configuration1 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 <Sie Server bel installation directory>classes folder3 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.200 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 201. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and Updates5 Create a file with name ‘jndi.properties’ with following details in the path D:JMS: java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory java.naming.provider.url=opmn:ormi://<IP Address of the FMW server>:<OPMN Port No>:oc4j_soa java.naming.security.principal=anonymous For example: java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory java.naming.provider.url=opmn:ormi:// 152.68.240.154:6009:oc4j_soa java.naming.security.principal=anonymous Make sure that there are no extra spaces in the jndi.properties file.6 Create a Named Subsystem in the Siebel application through the server management. a Connect to the server manager from the command prompt from the bin directory of the Siebel installed folder with the following command. Srvrmgr /g <gatewayserver> /e <enterpriseserver> /s <siebelserver> /u <userid> /p <password> Example: srvrmgr /g sdc78198svqe:4330 /e siebel /s sdc78198svqe /u sadmin /p sadmin Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 20 1
  • 202. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates b Run the following command to create the named subsystem and add the jar file into the class path. Create named subsystem JAVA for subsystem JVMSubSys with DLL=C: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.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.202 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 203. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructions for Enhancements and UpdatesConfiguring Corresponding Web Services for Advanced Queue (AQ)The following section contains information about how to configure corresponding Web services forAQ. For more detailed information about AQ configuration, refer to the topic, “Proce of Configuring ssJMS Messaging Between Siebel Business Applications and Oracle SOA Suite Using Oracle AdvancedQueuing” section Transports and Interfaces: Siebel Enterprise Application Integration on the SiebelBookshelf.Use the following procedure to configure corresponding Web services for AQ.To configure corresponding Web services1 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/ QCF4 After changing the address, click Clear Cache.Required Tasks for the Order to Cash PIPNOTE: The following tasks are required if you are using Order to Cash PIP.Use the following procedure to disable Asset-Based Ordering.To disable Asset-Based Ordering1 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). Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R 20 3
  • 204. Siebel Maintenance Release Guide, Version 8.1.1.x, Rev. R ■ Configuration Instructionsfor Enhancements and Updates3 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 MigrationThis section describes how to run the EIM jobs for implementing the O2C PIP.Data Migration SequenceThe below entities should be executed in sequence to maintain the data integrity. This includes thepre-and post EIM activities, which need to be carried out manually. S.No Main Entities Task Type 1 Organization Manual 2 Inventory Location Manual 4 Products EIM 5 Post EIM Product Release Manual 5 Pricelist EIM 6 Customers EIM 7 Assets EIMBefore 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 co untry, make backup copies of the EIM logs, for status verification. These logs are located in the siebsrvr/logs directory.Checking EIM Component AvailabilityUse the following procedure to check EIM component availability.To check EIM component availability1 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.204 Siebel Maintenance Release Guide Version 8.1.1.x, Rev. R
  • 205. Siebel Maintenance Release Guide, Version 8.1.1.