Sbl Errors 34633v

SBL-EAI-04451: Method '%1' of business component '%2' (integration component '%3') for record with search specification '%4' returned the following error:"%5" Applies to: Siebel CRM - Version: 8.0 [20405] and later [Release: V8 and later ] Siebel CRM - Version: 8.0 [20405] and later [Release: V8 and later] Information in this document applies to any platform.

SymptomsWhenever a service based on EAI Siebel Adapter or EAI UI Data Adapter business service run to insert a child record when there are already 10000 records associated to the parent, i.e. s for an Accout, t to a Responsibility, an error message is received as the following: "Method 'NextRecord' of business component '' (integration component '') for record with search specification '[ Name] = "[email protected]"' returned the following error:"There were more rows than could be returned. Please refine your query to bring back fewer rows(SBL-DAT-00500)"(SBL-EAI-04451)" "Method 'NextRecord' of business component '' (integration component 'Related ') for record with search specification '[Middle Name] = "Cont_MN" AND [Last Name] = "Cont_LN" AND [First Name] = "Cont_FN"' returned the following error:"There were more rows than could be returned. Please refine your query to bring back fewer rows(SBL-DAT-00500)"(SBL-EAI-04451)"

CauseThis behavior is expected as the default 'ForwardBackward' execution mode is used to limit fetched records from the Select statement needed in this kind of operations (as explained in Document 478896.1 – 'SBL-DAT-00500: There were more rows than could be returned. Please refine your query to bring back fewer rows'). In the context of EAI Siebel Adapter and EAI UI Data Adapter business service, the 'ExecutionMode' is a hidden input argument for Insert methods, and included in Bookshelf > Integration Platform Technolgies: Siebel Enterprise Application Integration > EAI Siebel Adpter Business Service > EAI Siebel Adapter Business Service Method Arguments, Table 23 and Table 24 with the following description:

"Used to set the direction of a query on a business component. Valid values are ForwardOnly and Bidirectional. The default is Bidirectional. ForwardOnly is more efficient than Bidirectional, and should be used in cases where you need to process a large number of records in the forward direction only (such as for report generation). For more information on executing queries, see the topic on the ExecuteQuery business component method in Siebel Object Interfaces Reference" As opposite to 'ForwardBackward' value, 'ForwardOnly' does not restrict the number of fetched records during the Select statement.

SolutionIn order to implement the 'ForwardOnly' execution Mode in EAI Siebel Adapter or EAI UI Data Adapter services, the argument 'ExecutionMode' has to be added in the method's arguments. For instance, using 'Siebel ' Business Service (based on EAI Siebel Adapter), InsertOrUpdate method to link s to an : a. From Siebel Tools, Business Services, select 'Siebel ' and expand it. b. From Business Service Method, select InsertOrUpdate. c. Select Business Service Method Arg. d. Add a new Argument with name 'ExecutionMode'. If needed, publish again your service (Web Service, JCA Code Generated). When invoking the service, set the value 'ForwardOnly' to argument 'ExecutionMode'. Repeat the required call. This will enable the option not to limit fetched records and allow the Insert operation for the child record. The CR # 10583262 was logged to improve the current information about this parameter in Bookshelf, so it will explicit indicate its use while fetching records in this type of solutions. Note The following situation was observed using this Mode. Using ExecutionMode=ForwardOnly there was an issue trying to change the primary of a MVG ex. IsPrimaryMVG="Y" on a Position of an . When siebel tried to update the parent record () it failed because the cursor is in ForwardOnly mode. So it could not get back to the parent record to update the

primary position returning the error: "An end of file error has occurred. Please continue or ask your systems to check your application configuration if the problem persists". So, when including MVG, this mode should not be used.

ReferencesBUG:10583262 - ISSUE WITH WEB SERVICE WHEN THERE ARE MORE THAN 10K RECORDS BUG:10470871 - DSMAXFETCHARRAYSIZE SHOULD BE A COMPONENT PARAMETER RATHER THAN AN ENTERPRISE PARAMETER NOTE:477558.1 - Setting the Parameter DSMaxFetchArraySize to -1 Could Cause Problems with Siebel Object Managers in Siebel 7 NOTE:478896.1 - SBL-DAT-00500: There were more rows than could be returned. Please refine your query to bring back fewer rows NOTE:524329.1 - SBL-DAT-00500: "There were more rows than could be returned" error received when running a BS Method

Applies to: Siebel System Software - Version: 7.8.2.1 [19216] and later [Release: V7 and later ] Oracle Solaris on SPARC (64-bit) Product Release: V7 (Enterprise) Version: 7.8.2.1 [19216] Database: NCR Teradata V2 R5.0 Application Server OS: Sun Solaris 10 Database Server OS: Sun Solaris 10 This document was previously published as Siebel SR 38-3278478425. """"Checked for relevance on 29-OCT-2010""""

SymptomsSBL-DAT-00523, SBL-EAI-04451 BACKGROUND:: data feeds are received every night and Siebel EAI Adapter is used to UPSERT all these records into Siebel. New and exising updates are sent as part of the feed. There are different types of s that are fed but we are using only one IO to load the data into siebel. We are multi-org, so wholesaler type of s would be promoted to Organization. The entities that are getting updated are , Organization, Position, Business Address, Bill to Address, Ship to Address. I am using CSV to property set BS and the property set to Siebel EAI

Adapter. An IO has been created based on Business Object as per following :IO : Io 1 IC : 2 IC : Internal Division 3 IC : _Business Address 4 IC : _Bill To Business Address 5 IC : _Ship To Business Address 6 IC : _Organization PROBLEM:: When creating a new in Siebel with the above IO, it works as long as there are no association entities that update Primary fields on (when only , Internal Division details are in the CSV). But when the feed inlcudes any of the _Organization OR _Position OR _Business Address OR _Bill To Business Address OR _Ship To Business Address, the EAI Siebel Adapter generates error :Error invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Upsert'.(SBLBPR-00162) Method 'WriteRecord' of business component '' (integration component '') for record with search specification '[Location] IS NULL AND [Name] = "Test Acc"' returned the following error:"The selected record has been modified by another since it was retrieved. Please continue.(SBL-DAT-00523)"(SBL-EAI04451) If these association entities are used for an existing in Siebel, it also works fine.

CauseIt was found that if the External Sequence of the Internal Division component was set higher than the External Sequence of the _Organization, then it worked as expected. However, this would not normally be recommended, per Integration Platform Technologies: Siebel Enterprise Application Integration > Integration Objects > About the Structure of Integration Objects > Setting Primaries Through Multivalue Links :“It is recommended that the EAI Siebel Adapter use the multivalue link only after it processes the component through the link; therefore, the link or the Association component has a smaller external sequence number than the related MVG or MVGAssociation component.” The error arising when the External Sequence of Internal Division component was lower than the the MVG component was re-produced, and change request 10526720

has been logged.

SolutionAfter setting the External Sequence of the Internal Division component higher than the External Sequence of the _Organization (the MVG component), the insert of the and the associations worked as expected. BUG: 10526720 has been logged, and this will be reviewed and prioritized by Product Marketing.

Applies to: Siebel Reports - Version: 8.1.1.1 [21211] and later [Release: V8 and later ] Information in this document applies to any platform.

SymptomsAs part of the installation and upgrade procedures for Siebel 8.1.1.1 or equivalent releases on other codelines, there is a requirement to import the PublicReportService_v11.wsdl which is generated from the Oracle BI Publisher Server. This .wsdl defines the Outbound Web Service which Siebel communicates with and through which various integration methods are exposed. The .wsdl itself is imported through Siebel Tools and creates a Proxy Business Service and multiple Integration Objects in the Siebel Repository in order to this integration. During the import the following error may be reported : ObjMgrBusCompLog Error 1 000000024b1620a8:0 2009-12-02 00:49:28 (buscomp.p (32085)) SBL-DAT-00225: The value entered in field Integration Object of buscomp Repository Business Service Method Arg does not match any value in the bounded pick list Repository PickList Integration Object. ObjMgrLog Error 1 000000024b1620a8:0 2009-12-02 00:49:28 (adptutils.p (5624)) SBL-EAI-04451: Method 'SetFieldValue' of business component 'Repository Business Service Method Arg' (integration component 'Repository Business Service Method Arg') for record with search specification '[Name] = "runReportRequest:parameters"' returned the following error:"The value entered in field Integration Object of buscomp Repository Business Service Method Arg does not match any value in the bounded pick list Repository PickList Integration Object.(SBL-DAT-00225)"

CauseThis behavior is caused because the import process does not check the Repository ID into which the Proxy Business Service and Integration Objects are being imported. If there are other repositories in the database which include one or

more copies of the objects being imported such as the PublicReportService then these errors will be reported during the import process.

SolutionIn order to resolve this behavior it is necessary that copies of the PublicReportService Business Service and Integration Objects from the 'XMLP Integration' project be deleted from these other repositories. Once these other instances have been deleted the performing the import should use the File > Open Repository option in Siebel Tools to switch to the correct Siebel Repository and then perform a fresh import of the PublicReportService_v11.wsdl. The following Change Requests exist for this behavior : CR #10531598 "WSDL Import Wizard fails to create Integration Objects, if they exist in another Siebel Repository" CR #10584271 "BIP Outbound WS fails to import when there are multiple Siebel Repositories in the database"

Applies to: Siebel CRM - Version: 8.1.1.1 SIA [21211] to 8.1.1.1 SIA [21211] Release: V8 to V8 Information in this document applies to any platform.

SymptomsStatement of Issue: ----------------------------The customer was using UCM 8.2 (8.1.1.1 + QF3103) and found an error occurring when two s are merged in istration - Universal Customer Master > Existing Duplicates Error: ------[1] Error invoking service 'UCM Source Data and History Service', method 'Store' in the step 'Store History'. (SBL-BPR-00162) [2] The method 'SetFieldValue' in BC 'UCM Source Data and History' (integration component ' ') for the record with the search term [Id] = "13EJBU" has returned the following error: 'Value too long for column' Merge Transaction Id '(maximum size: 30). (SBL-DAT00235) '(SBL-EAI-04451)

CauseThe cause of this issue is a mismatch between the business level and database level definitions. In the 'UCM Source Data and History' and 'UCM Source Data and History' business components, the 'Merge

Transaction Id' field is mapped to the TRANSACTION_ID column in the S_UCM_ and S_UCM_ORG_EXT tables respectively. The field length is 100, but the column length is 30. Hence when the application tries to write the 36 character generated Id into the column during a merge it fails with an error. The following change request was logged for this issue: Bug 10594551 - QF3103: Unmerge fails:TRANSACTION ID column in tables like S_UCM_ needs extension to 100

SolutionThe current ed methods to workaround this issue are: 1. Map the Merge Transaction Id field to two new columns for each of the business components affected, namely the 'UCM Source Data and History' and 'UCM Source Data and History' business components. 2. Get Oracle Expert Services to alter the standard column definition in the 'Expert Mode' of Siebel Tools. However, Oracle Expert Services is a billable service. Solution: The issue has been fixed in the branch quick fix 8.1.1.1 QF3104 and should be fixed in the 8.1.1.5 fix pack.

Applies to: Siebel CRM - Version: 8.0.0.8 SIA[20430] and later [Release: V8 and later ] Information in this document applies to any platform.

Symptoms === ODM Issue Clarification === On : 8.0.0.8 SIA[20430] version, Siebel EAI When attempting to export SWI related web services from the UAT environment and import them in the PROD environment. the following error occurs. ERROR ----------------------"Method 'SetFieldValue' of business component 'Operation' (integration component 'Operation') for record with search specification '[Operation Name] IS

NULL' returned the following error:"The value entered in field Method Name of buscomp Operation does not match any value in the bounded pick list PickList SRF Service Method - Bounded.(SBL-DAT-00225)"(SBL-EAI-04451)" STEPS ----------------------The issue can be reproduced at will with the following steps: 1. Use to export the web service from UAT. 2. In PROD, go to site map -> istration - web services -> inbound web services and import the web service BUSINESS IMPACT ----------------------The issue has the following business impact: Due to this issue, s cannot complete the PROD environment setup

Cause The business service referenced by the web service had been copied and renamed, but the display name was not changed. The import process fails when it finds 2 records with the same display name . In istration - web services -> inbound web services, select any existing web service, scroll down to service ports and add a new record. While creating this record click the gliph sign at the right side of the field "business service". In the popup applet titled "Inbound web service port type pick applet we query for the business service referenced by the web service. In this example business services SWI*. In this particular case none was found. Click the "New" button in the pick aplet to add the business service and notice it is listed twice . The reason is someone made a copy of the original business service and forgot to change the display name. This preventes the web service import wizard from working fine.

Solution Once the display names were made unique in Siebel Tools and a new SRF was compiled and used the import process run fine.

Applies to: Product Release: V7 (Enterprise) Version: 7.8.2 [19213]

Database: Oracle 9.2.0.5.0 Application Server OS: HP 9000 Series HP-UX Database Server OS: None - Not Implementing Web Server OS This document was previously published as Siebel SR 38-2712675981.

SymptomsSBL-DAT-00382, SBL-EAI-04451 We imported from the development enviroment to the test enviroment a Siebel Standard Woowkflow Process "Configurator Load". We modified this Workflow to adapt it to the business. The import failed and then we cancelled by tools the Workflow. We have traid again to performe the import but again we obtained the same result. Please see the message we got: "Method 'NewRecord' of business component 'Repository Workflow Process' (integration component 'Repository Workflow Process') returned the following error: "An internal error has occurred due to an invalid definition for id business component. Please ask your systems to check your application configuration. (SBL-DAT-00415)"(SBL-EAI-04376)" Could you please provide us with some instructions to solve this problem? Thank you in advance. Best Regard Rossana Mattera

SolutionMessage 1For the benefit of other readers, the following problem has been encountered. Export of the process “Configurator Load” works correctly however, the import generates the error below. [0] Method 'WriteRecord' of business component 'Repository WF Step I/O Argument' (integration component 'Repository WF Step I/O Argument') for record with search specification '[Input Flag] = "O" AND [Name] = "O:Load Instance2"' returned the following error:"The same values for 'GParent Name, Parent Name, Name' already exist. If you would like to enter a new record, please ensure that the field values are unique.(SBL-DAT-00382)"(SBL-EAI-04451) (0x561d) This could be reproduced against the server database but not against the sample database. The problem comes from the fact that the step "Load Instance" has 2 identical

output arguments setting the process property “MyRowId” with output argument “RootId”. The workaround is to edit the process, step "Load Instance", to remove one of the output argument record. Change request 12-19ESZTZ was logged to have this problem addressed in future version. Siebel E-Commerce - Version: 8.1.1 [21112] and later [Release: V8 and later ] Information in this document applies to any platform.

SymptomsAn error was thrown while trying to new Individual (B2C) in Siebel Self Service 8.1.1.1 Telco application. Error :-------------------EAISiebAdpt EAISiebAdptErr 1 000000b84c0e2498:0 2010-06-09 14:52:51 [0] Method 'SetFieldValue' of business component '' (integration component '') for record with search specification '[Id] = "1-22NND0"' returned the following error:"Cannot get value of business component field 'Organization Id' at step 'Get Employee data'.(SBL-BPR-00120)" (SBL-EAI-04451) (0x670078) ObjMgrLog Error 1 000000b84c0e2498:0 2010-06-09 14:52:51 (stepexec.p (1559)) SBL-BPR-00162: Error invoking service 'SelfService_SIA', method 'Execute' at step 'Create and '.

CausePer internal tests done, the behavior was not reproducible in house using standard siebel application using out of the box Telco Source code. Further investigation revealed that there was custom workflow that was getting triggered during the registration process and the error was raised from this custom workflow. After inactivating the custom workflow registration could be done without error.

SolutionDisable the custom workflow from which error is raised and again.

ReferencesSBL-EAI-04451 SBL-BPR-00162 SBL-BPR-00120

Applies to: Siebel System Software - Version: 7.7.1 [18306] and later [Release: V7 and later ] Oracle Solaris on SPARC (64-bit) Product Release: V7 (Enterprise) Version: 7.7.1 [18306] Database: Oracle 9.2.0.4 Application Server OS: Sun Solaris 8 Database Server OS: Sun Solaris 8 This document was previously published as Siebel SR 38-1448301541.

SymptomsHello, We are having a problem importing iHelp item definitions in Siebel 7.7.1 To test this I carried out the following steps: Connecting to the Client in a Vanilla instance of Siebel I navigated to istration > iHelp. There was one existing iHelp record called 'Create an iHelp item'. I copied this to create another record (right click Copy Record) and named the second record test1. Next I exported the 'test1' record by selecting the 'Export iHelp Item Definition' option from the menu. When this had successfully exported I deleted the 'test1' record from the GUI and then tried to import the test1.xml file using the 'Import iHelp Item Definition' option from the menu. On doing this I recieved an error "Method Write Record of business component Task Application (integration component Task Application) for record with search spec [Application] IS NULL returned the following error. An error has occurred writing to a record. Please continue or ask your Systems to check your application configuration if the problem persists." What should we be doing to stop this happening?

CauseSBL-DBC-00111, SBL-EAI-04451, SBL-EAI-04381 SolutionFor the benefit of the readers, Symptoms: Customer experienced a failed import of the copy of the seed iHelp "Create an iHelp Item”

Resolution: The error message SBL-EAI-04451 indicated a failed import due to a NULL value. By reviewing the data of the XML file generated, it appears that among the field Application Multi Value Group (MVG), none of the value of the seed data "Create an iHelp Item” matched the current Application Name. If a new record is created, you will notice that the current Application Name will be defaulted and by opening this MVG, you will notice that none of the value of the seed data "Create an iHelp Item" can be selected. It was verified that the export/import was working as expected on any other records. To circumvent this behavior, the XML was manually corrected. Change Request (12-O1WMXL) has been created to request the update of the seed data in a future release. Likelihood of Occurrence: 7.7.1

Applies to: Oracle Application Integration Architecture Foundation Pack Version: 2.5 and later [Release: No Release Description and later ] Oracle Product Master Data Management Integration - Version: 2.5 to 2.5 [Release: 2.5 to 2.5] Information in this document applies to any platform.

SymptomsAn error is returned after updating an obsoleted item (enabled_Flag = N in the mtl_system_items_b) description in PIM with 'Obsoleted Item' for example and then publishing to Siebel. SynroductSiebelProvABCSImpl resulted in the following error: - <details> - <![CDATA[

<part name="code">Server <part name="summary"><summary>Method 'WriteRecord' of business component 'SWI Internal Product VOD' (integration component 'SWI Internal Product VOD') for record with search specification '[Primary Organization Id] = "0-R9NH" AND [Part #] = "9940001"' returned the following error:"An error has occurred writing to a record. Please continue or ask your systems to check your application configuration if the problem persists.(SBL-DBC-00111)"(SBL-EAI04451) <part name="detail"><detail><detail>

ChangesThe only change was to inactive an item in PIM. CauseThe error is returned because in the InvokeSWIProductUpsertCallexecute, the following is noted: <xsdLocal:ActiveFlag /> Implying an empty value for the ActiveFlag field. The value of ActiveFlag is based on the Active_Flag_SEBL DVM. The payload for SyncItemListReqMsg shows: - Obsolete However the Active_Flag_SEBL DVM has been configured for the following: Active, Y Pending, N Inactive, N Closed, N

SolutionThe solution is to update the Active_Flag_SEBL DVM to include the status 'Obsolete' and set it to N.

Applies to: Siebel Server Sync - Microsoft Exchange Server - Version: 7.8.2 SIA [19213] and later [Release: V7 and later ] z*OBSOLETE: Microsoft Windows Server 2003 Product Release: V7 (Enterprise) Version: 7.8.2 [19213] Fin Svcs Database: Microsoft SQL Server 2000 SP3 Application Server OS: Microsoft Windows 2003 Server SP1 Database Server OS: Microsoft Windows 2003 Server SP1 This document was previously published as Siebel SR 38-2774141561.

SymptomsSBL-SIS-00181, SBL-EAI-04451 For the most part, I have SSSE working correctly. In our setup for Task synchronization, we use the value Completed instead of Done (which is the OOB value) for task status. In the LOV Translation tab I have changed the Value for Task Status from Done to Completed for the PIM Value of 2. When I change the value of the Status field in a task within Siebel, the task synchronizes to Exchange correctly. When I change the status in Outlook to Completed, I get an error in the Siebel Logs. (I have attached the logs to this request) I suspect I have missed something but I can't determine what it might be.

CauseThe configuration below will allow synchronization in both directions when an activity or task is marked with a status of "Completed" instead of "Done." Please review the steps below and compare with your environment. I would be happy to conduct a WebEx with you if the steps below do not allow proper synchronization. Errors: If done incorrectly, the following error in the PIMSIEng_##.log may appear: ObjMgrLog Error 1 0 2005-12-28 12:44:26 (adptutils.p (5137)) SBL-EAI-04451: Method 'SetFieldValue' of business component 'Action' (integration component 'Action') for record with search specification '[Id] = "X-XX"' returned the following error:"Either the status value you have selected is not applicable to this activity type, or you must submit this activity using the submit button.(SBL-SIS-00181)"

Solution1. to the SSSE environment via web client as S. 2. Navigate to Site Map > istration - Data > List of Values 3. Query for the following: Type = EVENT_STATUS Display Value = Done

4. It will return one record. (There are 21 values for Type=EVENT_STATUS in standard 7.8.2) Do not overwrite this record. 5. Create a new record in this list: Type: EVENT_STATUS Display Value: Completed Language-Independent Code: Completed Language Name: English-American Order: 23 Active: Y Translate: Y Replication Level: All 6. Save the record. 7. Then click the "Clear Cache" button 8. Now when you look in the Activities > Activity List view, the status field will have the LOV value "Completed" at the very bottom of the list. 9. Please note that in Microsoft Outlook, a Task can have several status values: Not Started In Progress Completed Waiting on Someone else Deferred 10. The "Completed" status in Outlook maps to the "Done" status in Siebel. 11. To make it map to our new Siebel status of "Completed", we navigate to Site Map > istration - PIM Server Integration > Configuration > LOV Translation 12. Run a query in the Name column: Task Status 13. In out-of-the-box Siebel 7.8.2, there will be seven records returned. We are concerned about the record whose Siebel Value = Done 14. Change the "Siebel Value" from "Done" to "Completed," which should now be visible in the picklist, since this field grabs it from the same LOV Type list. 15. Save the record and restart the Siebel Server service. 16. Now, when creating a "To Do" activity in Siebel with a status of "Completed" or a Task record in Outlook with a status of "Completed," a record will be created accordingly in the corresponding application.

Applies to: Siebel Server Sync - Microsoft Exchange Server - Version: 7.7.2.6 [18372] to 8.0.0.2 [20412] - Release: V7 to V8 Information in this document applies to any platform.

SymptomsCustomer reported that all s were failing to sync. ES was onsite and were assisting the customer with this issue to get it resolved faster. When new s were created the sync would work as it was designed to do. It was then determined that the issue only happened to s who were pre SSSE install.

CauseThe system could not find any of the s to sync them. The cause was found from this error: ObjMgrLog Error 1 0000000648511a00:79071 2008-06-12 10:46:38 (adptutils.p (5614)) SBL-EAI-04451: Method 'AssocCurrentRow' of business component 'Employee' (integration component 'Action_Employee') for record with search specification '[First Name] = "******" AND [Last Name] = "******" AND [ Name] = "****"' returned the following error:"The selected record has already been added to the list. Please add another record or close the pop-up list and continue.(SBL-DAT-00357)" EAISiebAdpt EAISiebAdptErr 1 0000000648511a00:79071 2008-06-12 10:46:38 [0] Method 'AssocCurrentRow' of business component 'Employee' (integration component 'Action_Employee') for record with search specification '[First Name] = "*****" AND [Last Name] = "******" AND [ Name] = "******"' returned the following error:"The selected record has already been added to the list. Please add another record or close the pop-up list and continue.(SBL-DAT00357)"(SBL-EAI-04451) (0x750165) This error above was coming up as it could not find the ids as they were not in the correct format. Siebel requires that the ids be in all cap format. So rather then having their ids be "AAAAAA" which is the correct format and will work all of their s were in the format of "aaaaaa". This was due to the fact that they added their s with the use of the EIM tool which therefore byed the validation check on the Employee BusComp that forced uppercase names. This is a behavior that should never be done the ID is the link for Siebel to use for everything not just SSSE. There could be many other parts of the application that could be broken as per the result of this behavior this was just the first one that was discovered.

SolutionThe solution was found in the way of checking the name entry in the Employee table. The name for each of the s was in a lowercase format. (Example being the query searched for 'AAAAAA' but the entry in the DB was 'aaaaaa') Once the change was done to make the name in all uppercase the system query no longer failed and it was able to find the s. The problem was not happening with new s due to the fact that they were creating them in Siebel and the system was running the validation check to make sure the format of the id was correct.

Applies to: Siebel Reports - Version: 8.1.1 SIA [21111] to 8.1.1 [21112] Release: V8 to V8 Information in this document applies to any platform.

SymptomsAfter applying 8.1.1.1 fix pack and trying to configure the new 'Siebel Security Model' to be used for Oracle BI Publisher reporting, the Siebel Inbound Webservice (BIPSiebelSecurityWS.xml) delivered with the fix pack fails to import with the below mentioned error message: Error Message

CauseThe issue is caused due a method named 'Authenticate' not found in the SRF/ Siebel Repository. The following error message is reported in the Siebel Application Object Manager log file (set to diagnostic event log level '5') during the import of the Web Service. Error Message

SolutionThe issue can be resolved by following the below mentioned steps: 1. As a part of 8.1.1.1 Fix Pack installation, it is mandatory to import a .SIF file named '8111FP_new_feature.sif'. Refer to Siebel Bookshelf > Siebel Reports Guide > Integrating Oracle BI Publisher with Siebel Business Applications > Process of Configuring the Siebel Application for Integration with Oracle BI Publisher > Importing an Archive File to Apply the New Siebel Reports Features

2. Once the above mentioned .SIF is imported successfully, compile a new SRF. 3. Import the Web Service using the SRF (from Step 2). The Web Service import can be done in the Siebel Web Client Or in the Siebel Dedicated Client (connected to the Server database). Refer to Siebel Bookshelf > Siebel Reports Guide > Integrating Oracle BI Publisher with Siebel Business Applications > Process of Securing Siebel Access to the Oracle BI Publisher Server > Configuring Security and Authentication Using the Siebel Security Model

Applies to: Siebel Reports - Version: 8.1 [21039] and later [Release: V8 and later ] Information in this document applies to any platform.

PurposeThis document applies to customers who are implementing integration between Siebel and Oracle BI Publisher as a Siebel Reporting Solution. The document applies to installations on the following releases : Siebel 8.1.1 and higher Siebel 8.0.0.8 and higher Siebel 7.8.2.14 and higher Siebel 7.7.2.12 and higher It is recommended that this document be used in conjunction with the Siebel Reports istration Guide. Issues Reported during Implementation or Upgrade For issues encountered during upgrades or initial implementations please review the document which provides links to historical copies of the Siebel Reports Guide. Please ensure that upgrades or implementations are performed using the version of the Siebel Reports Guide which is applicable to the FixPack being implemented. Failure to do so may result in errors when using reporting functionality due to mismatches between the applied FixPack and configuration : Document 1166559.1 - Links to Documentation for Using Siebel Reports If errors are still encountered following validation of the upgrade steps then proceed with a review of the later parts of this document.

The following topics are detailed in this Troubleshooting Steps document. Click on the related jumplink below to navigate to the topic you wish to review: Troubleshooting Steps How to enable logging on the XMLPReportServer componentHow to enable logging on an Object Manager componentHow to enable logging on the BI Publisher Server How to enable logging for BI Publisher reports run through a dedicated or mobile client Commonly Reported Errors 1) Mismatch between fields being queried on and fields included in the Integration Components 2) Generic HTTP Internal Server error 3) Generic error with content of SOAP message 4) Report error "Due to Report with Path xxxxx already exist" 5) Report or run report error due to "java.lang.SecurityException" 6) SetFieldValue error in Siebel Tools during import of the PublicReportService_v11.wsdl 7) CLASSPATH errors within the XMLPJvmSubsys 8) "No such operation" errors occurring during PublicReportService web service calls 9) Missing dataservice.wsdl 10) "Setup.exe has encountered an error..." during installation of Oracle BI Publisher 10.1.3.4.1 or higher 11) Configuring BI Publisher on a mobile or dedicated client results in errors at runtime 12) NullPointerException error in BI Publisher when running a scheduled report 13) After applying Siebel 8.1.1.3 FixPack Siebel BI Publisher reports fail to run

Last Review DateJanuary 20, 2010 Instructions for the Reader A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting DetailsThis section details some of the ways in which additional diagnostic information can be obtained from the various components used within the Siebel BI Publisher Integration. The specific logging required will depend on the scenario involved. How to enable logging on the XMLPReportServer component To set the log level for the XMLP Report Server server component using the Server Manager Command Line utility

1) Run the following command to connect to the Siebel Server Manager: srvrmgr /g /s <xmlp siebel server name> /e <enterprise> /u < name> /p <> where: gateway machine name:port number is the name of the physical computer on which the Siebel Gateway Name Server is running and the port number on which the Gateway Name Server is listening. NOTE: The colon and port number are optional and only required if using a port other than the default. xmlp siebel server name is the name of the server on which the XMLP Report Server component is enabled. name is the name of the . is the for the . For example, you might use the following command: srvrmgr /g :2330 /s <xmlp siebel server name> /e Siebel /u S /p xxxxx 2) Run the following command to change the event log level: change evtloglvl %=4 for comp XMLPReportServer This will increase the logging level for all events to 4 for the component in question. In some scenarios it may be more suitable to provide specific logging of particular events but this will be detailed where necessary. In general when debugging a relatively high logging level across all events will improve root cause identification. 3) Whilst the logging level change will take effect for some events immediately in order to provide comprehensive logging based on the changes the recommendation is to then perform a shutdown and restart to the XMLPReportServer component as follows : shutdown comp XMLPReportServer startup comp XMLPReportServer 4) Any XMLPReportServer tasks initiated after the restart should now include increased logging across all events. If additional detail is required for any reason then a logging level of 5 for all events can be set using the above procedure. How to enable logging on an Object Manager component In some scenarios it may be necessary to increase the logging level on the Object Manager from which a report request is being made to obtain additional diagnostics. The specific Object Manager which will need to be istered will depend on the environment and the applications being used by the end s but the information listed in the previous section for the XMLPReportServer component is equally applicable for the various Siebel Object Managers.

To increase logging on any Object Manager use the procedure detailed under 'How to enable logging on the XMLPReportServer component' replacing the 'XMLPReportServer' references with that of the Object Manager in question (e.g. SCCObjMgr_enu for the English Call Center Object Manager). NOTE : Restarts of the Object Manager components whilst s are logged on will result in their currently active sessions being disconnected. Any restart of the Object Managers should be done during a maintenance window so as to avoid impact on end s. How to enable logging on the BI Publisher Server In many of the potential error scenarios which could be encountered there is a benefit in having increased logging available on the BI Publisher Server following analysis of the Siebel-side logs. The following section details how to enable increased logging on the BI Publisher Server. 1) Identify the %ORACLE_HOME% directory into which BI Publisher is installed 2) Create a file called xdodebug.cfg at the following location - < %ORACLE_HOME>\jdk\jre\lib 3) Open the file using a text editor and copy and paste the following text into the file : LogLevel=STATEMENT LogDir=C:\OraHome_1\jdk\jre\lib\temp Note : Replace the 'C:\OraHome_1' text with the path identified in 1).4) Within the '<%ORACLE_HOME>\jdk\jre\lib' directory create a subdirectory (in this case the 'temp' directory) which will contain the resulting log files for the increased logging. 5) Shutdown and restart the BI Publisher Command Window Once BI Publisher has restarted attempt to perform the problematic operation again and a set of files will be created within the 'LogDir' directory set in the xdodebug.cfg. In most cases the most interesting log for debugging purposes will be the xdo.log which contains the command/console window contents along with other diagnostic information. For a succesful report completion there will be a number of other files created within this location which contain various aspects of the data from the report generation as can be seen in the following listing : 21/01/2010 15:30 . 21/01/2010 15:30 .. 21/01/2010 18:04 1,995,642 xdo.log 21/01/2010 18:03 0 xdo_012110_110322171_rtf_out.xsl 21/01/2010 18:03 0 xdo_012110_110322171_rtf_out_xliff.xml 21/01/2010 18:03 49,752 xdo_012110_110322171_rtf_template.rtf 21/01/2010 18:04 46,724 xdo_012110_110433171_rtf_out.xsl 21/01/2010 18:04 17,001 xdo_012110_110433171_rtf_out_xliff.xml 21/01/2010 18:04 49,752 xdo_012110_110433171_rtf_template.rtf 21/01/2010 18:04 47,065 xdo_012110_110436562_fo_data_11.xsl 21/01/2010 18:04 795 xdo_012110_110436562_fo_data_12.xml

21/01/2010 18:04 1,666 xdo_012110_110436562_fo_fo_14.fo 21/01/2010 18:04 3,888 xdo_012110_110436562_fo_out3.out How to enable logging for BI Publisher reports run through a dedicated or mobile client The same mechanism applies to enable debugging in dedicated clients as it does when enabling logging on the BI Publisher Server itself. In order to enable logging an xdodebug.cfg file must be created and contain the LogLevel and LogDir parameters. The difference when enabling logging for the dedicated or mobile clients is the location into which this must be placed. In these instances the xdodebug.cfg must be placed into the 'lib' dir of the jre installation being used by the client. This can be established through reviewing the PATH settings on the client. For example : C:\Program Files\Java\jre1.6.0_07\lib Once the file has been created, a suitable logging directory been made available, and the directory specified in the xdodebug.cfg then any subsequent runs of BI Publisher reports through the web client should formation as detailed above for the BI Publisher Server. Commonly Reported ErrorsThe sections below detail some of the more commonly reported error messages which can occur within a Siebel BI Publisher integration architecture. Along with each error message there are an explanation of the behavior and resolution details. 1) Mismatch between fields being queried on and fields included in the Integration Components SBL-EAI-04177: Information about integration component field 'As Of Date' not found. Check query specification and fields defined for integration component 'Order Entry - Orders' The error indicates that the query which is being ed to the Integration Component uses fields which it does not contain and therefore the query specification cannot be applied. As the query specification is constructed from a combination of elements in the UI it is necesssary to review the PDQ used on the view along with any custom query performed by the to establish the source of the error. The error message does include details of the problematic fields and the Integration Component in question and this information should aid the developers in making the necessary modifications. As a guideline developers should endeavour to include any fields on which a may query within the underlying Integration Component definition. These errors will appear with minimal logging in place on the XMLPReportServer component for the EAI Siebel Adapter and the Object Manager Business Service Logging events.

2) Generic HTTP Internal Server error SBL-EAI-04117: HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 500' SBL-EAI-04117: HTTP Request error during 'Submitting Data Send HTTP request': 'Status code - 500' These two error messages are commonly seen in a variety of scenarios and indicate that an error has occurred on the BI Publisher side of the integration. When encountering these errors within the XMLPReportServer log files a review should be made of the of the following trace which may provide details of specific issues in the integration. For further information in such scenarios it is recommended to review the contents of the BI Publisher console window and look to increase BI Publisher logging levels. If these errors are reported in isolation then it may be beneficial to introduce the following changes : 1. In Siebel Tools modify the vanilla 'EAI HTTP Transport' business service. 2. Right click on the name of the business service and select 'Edit Server Scripts'. 3. Copy paste the following script in the 'PreInvokeMethod' event: function Service_PreInvokeMethod (MethodName, Inputs, Outputs) { if (MethodName == "SendReceive" || MethodName == "Send") { Inputs.SetProperty("HDR.Connection","close"); } return (ContinueOperation); }4. Compile the modified business service and deploy the SRF to the Siebel server. These changes ensure that the HTTP connections are closed and re-opened when new requests are made to the BI Publisher Server thereby clearing any incomplete connections to the server. These error messages are reported with minimal logging in place for the Object Manager Logging event on the XMLPReportServer component 3) Generic error with content of SOAP message SBL-EAI-04304: Unknown Part ':oracle.apps.xdo.webservice.exception.InvalidParametersException' for operation 'Report' exists in SOAP message. The error message indicates that there are aspects of the SOAP message being returned from the BI Publisher Server which were unexpected and this is normally an indication that there have been errors which require further investigation. The recommendation in this scenario is to review subsequent error messages in the logs, commonly the 'SBL-EAI-04308' error messages, which will provide specifics on the

nature of the failure. 4) Report error "Due to Report with Path xxxxx already exist" SBL-EAI-04308: Operation 'Report' of Web Service 'http://xmlns.oracle.com/oxp/service/v11/PublicReportService.PublicReportServiceS ervice' at port 'PublicReportService_v11' failed with the following explanation: "oracle.apps.xdo.webservice.exception.InvalidParametersException: PublicReportService::executeReport Failure: Due to Report with Path [/SiebelCRMReports/Application Activity/Application Activity.xdo] already exist!". The error message indicates that the attempt to the report template (in this case 'Application Activity') failed because the BI Publisher Server already has a copy of the file ed. At present the Report method does not allow an to a new version of a report and automatically over-write the existing copy of the report on the BI Publisher Server. In order to workaround this behavior the needs to either rename or delete the folder for the existing instance of the report currently ed on the BI Publisher Server. The BI Publisher Server stores its report templates in the following location : <%ORACLE_HOME%>\xmlp\XMLP\Reports\SiebelCRMReports Once the existing report instance has been renamed or deleted a fresh of the report template should complete without error. A Change Request #12-1T66H "Unable to the updated Report template if already exists on to the BIP Server." exists for this behavior and is under investigation. 5) Report or run report error due to "java.lang.SecurityException" Report fails with the below error:SBL-EAI-04304: Unknown Part 'http://xml.apache.org/axis/:hostname' for operation 'Report' exists in SOAP message. SBL-EAI-04308: Operation 'Report' of Web Service 'http://xmlns.oracle.com/oxp/service/v11/PublicReportService.PublicReportServiceS ervice' at port 'PublicReportService_v11' failed with the following explanation: "java.lang.SecurityException: /SiebelCRMReports/ List/aclist.rtf". Running Report fails with the below error:ObjMgrBusServiceLog Error 1 00000bb04d9a0e8c:0 2011-04-05 04:13:14 (outdisp.p (214)) SBL-EAI-04308: Operation 'Report' of Web Service 'http://xmlns.oracle.com/oxp/service/v11/PublicReportService.PublicReportServiceS ervice' at port 'PublicReportService_v11' failed with the following explanation: "oracle.apps.xdo.webservice.exception.OperationFailedException: PublicReportService::executeReport Failure: Due to unable to create new Report as AbsolutePath [/SiebelCRMReports/ List/aclist.xdo] due to java.util.zip.ZipException: error in opening zip file".

This error message indicates that there was a Security issue with the of the Report Template in question to the BI Publisher Server. This implies that the performing the does not have permission to access the folder and/or file. This is normally caused by a failure to set the correct responsibilities for the in question within the Siebel application. The running the report needs to have XMLP_SIEBEL_GUEST responsibility. Further information on this error is detailed in the following document : Document 984953.1 Unable to pre-configured reports to Oracle BI Publisher 6) SetFieldValue error in Siebel Tools during import of the PublicReportService_v11.wsdl SBL-DAT-00225: The value entered in field Integration Object of buscomp Repository Business Service Method Arg does not match any value in the bounded pick list Repository PickList Integration Object. SBL-EAI-04451: Method 'SetFieldValue' of business component 'Repository Business Service Method Arg' (integration component 'Repository Business Service Method Arg') for record with search specification '[Name] = "runReportRequest:parameters"' returned the following error:"The value entered in field Integration Object of buscomp Repository Business Service Method Arg does not match any value in the bounded pick list Repository PickList Integration Object.(SBL-DAT-00225)" This error occurs when multiple repositories are present in the database and is caused by the import process not validating which repository is being used as the target for the import. Further information on this error is detailed in the following document : Document 1051121.1 - Why are SBL-EAI-04451 errors reported with the SetFieldValue method when the PublicReportService_v11.wsdl is imported ? 7) CLASSPATH errors within the XMLPJvmSubsys SBL-EAI-05010: Class name incorrect or does not extend SiebelBusinessService This error occurs when the CLASSPATH parameter is incorrectly defined or is incomplete and is indicative of the fact that the Java subsystem cannot resolve some of the classes for which methods are being called. Further information on this error is detailed in the following document : Document 989142.1 - What are the possible causes for the 'SBL-EAI-05010: Class name incorrect or does not extend SiebelBusinessService' error ? 8) "No such operation" errors occurring during PublicReportService web service calls

SBL-EAI-04304: Unknown Part 'http://xml.apache.org/axis/:hostname' for operation 'getTemplateParameters' exists in SOAP message. SBL-EAI-04308: Operation 'getTemplateParameters' of Web Service 'http://xmlns.oracle.com/oxp/service/v11/PublicReportService.PublicReportServiceS ervice' at port 'PublicReportService_v11' failed with the following explanation: "No such operation 'getTemplateParameters'". SBL-EAI-04308: Operation '>' of Web Service '>.>' at port '>' failed with the following explanation: ">". The error message occurs when the operation being called cannot be found on the server side within the target web service. In the case of a Siebel BI Publisher integration this is normally indicative of a mismatch within the definition of the Outbound Web Service where the Siebel installation is running on the Siebel 8.1.1.1 release but calls are being made to the earlier version of the PublicReportService web service available with Oracle BI Publisher 10.1.3.4.0. Further information on this error is detailed in the following document : Document 989112.1 - Why am I seeing 'No such operation xxxxx' returned in SOAP messages from the BI Publisher Server ? 9) Missing dataservice.wsdlWSDLException: faultCode=OTHER_ERROR: Unable to resolve imported document at 'dataservice.wsdl'.: This file was not found: file:/u01/obi/OracleBI/setup/dataservice.wsdl: java.io.FileNotFoundException: This file was not found: file:/u01/obi/OracleBI/setup/dataservice.wsdl. This behavior can occur during scheduling calls if there are access problems to the dataservice.wsdl. If this error is reported then please review the file permissions on the .jar files in the CLASSPATH and also ensure that the dataservice.wsdl file exists, has the correct permissions, and that the filename is all in lowercase. 10) "Setup.exe has encountered an error..." during installation of Oracle BI Publisher 10.1.3.4.1 or higher When running the installation for Oracle BI Publisher 10.1.3.4.1 or higher via setup.exe an error dialog may appear indicating that either : "Setup.exe has encountered a problem and needs to close." or "The instruction at <xxxxxx> referenced memory at <xxxxx>. The memory could not be 'read'" Both of these errors are caused by attempting to run the setup.exe from an installation directory which has a very long path name. When unpacking the 'bipublisher_windows_x86_101341.zip' file it unpacks to the following path by default : <xxx>\bipublisher_windows_x86_101341\Windows\Oracle_Business_Intelligence_P ublisher_Standalone\setup.exe

In order to resolve this behavior please unpack the .zip file so that it results in a shorter path to the setup.exe whereupon it will execute correctly. Further information on this error is detailed in the following document : Document 1054257.1 - Installing BI Publisher Enterprise Generates Error "Setup.exe has encountered a problem and needs to close" 11) Configuring BI Publisher on a mobile or dedicated client results in errors at runtime There are a number of corrections to the installation guide for mobile and dedicated clients which need to be considered. These result in either JVM subsystem errors or 'Class name incorrect or does not extend SiebelBusinessService' errors when running reports. Further information on these errors can be found in the following document : Document 1097758.1 - Configuring Mobile/Dedicated Clients to run BI Publisher reporting 12) NullPointerException error in BI Publisher when running a scheduled report In a number of scenarios when attempting to run a scheduled report for the first time the request may fail and the following error will appear within the BI Publisher console window or xdo.log if increased logging is enabled :This error will most likely be seen following an upgrade from Siebel 8.1.1 to Siebel 8.1.1.1 or higher and is caused by a lack of scheduling information being stored within the xdo file for the report in question within BI Publisher. In order for a report to be run in a schedule manner a number of additional items of information need to be stored within the .xdo file in BI Publisher. These are added to the .xdo file when the report is ed using the PublicReportService_v11 web service and therefore if an attempt is made to schedule a report which has not been ed with the aforementioned web service then the call stack above will be reported. In order to resolve this behavior it is recommended that following an upgrade from Siebel 8.1.1 to Siebel 8.1.1.1 or higher, all reports should be deleted from the BI Publisher server and ed again to ensure that their .xdo files are re-written with the additional information required for scheduling. 13) After applying Siebel 8.1.1.3 FixPack Siebel BI Publisher reports fail to run Following the application of the Siebel 8.1.1.3 FixPack to an environment using Siebel BI Publisher reporting reports may fail to run and the following error may be

reported : java.lang.NullPointerException at java.util.Hashtable.containsKey(Hashtable.java:314) at oracle.apps.xdo.servlet.ReportContextImplV11.getReportXMLData(ReportContext ImplV11.java:402) at oracle.apps.xdo.servlet.CoreProcessor.processScheduledRequest(CoreProcessor.jav a:420) at oracle.apps.xdo.servlet.CoreProcessor.generateScheduledDocument(CoreProcessor. java:115) at oracle.apps.xdo.servlet.ReportImpl.renderScheduledJob(ReportImpl.java:337) at oracle.apps.xdo.servlet.scheduler.XDOJob.generateReport(XDOJob.java:953) at oracle.apps.xdo.servlet.scheduler.XDOJob.execute(XDOJob.java:404) at org.quartz.core.JobRunShell.run(JobRunShell.java:195) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:52 0) An error has occurred creating business component '>' used by business object '>'. Please ask your systems to check your application configuration. (SBL-DAT-00222). Further information on these errors can be found in the following document : Document 1180903.1 - After applying Siebel 8.1.1.3 FixPack Siebel BI Publisher reports fail to run Related Products Siebel > Customer Relationship Management > CRM Enterprise Edition > Siebel Reports Keywords DEBUGGING; JAVA.LANG.SECURITYEXCEPTION; LOG FILE; PUBLISHER; SERVICES; WEB SERVICES; WSDL

: EAISiebAdpt EAISiebAdptTrcBusObj 4 000000094adf0e34:0 2009-10-21 13:34:27 Set business component field: 'Method Name', Value: 'Authenticate' EAISiebAdpt EAISiebAdptTrcBusObj 4 000000094adf0e34:0 2009-10-21 13:34:27

Get business component field: 'Method Name', Value: '' ObjMgrSqlObjLog Sort 5 000000094adf0e34:0 2009-10-21 13:34:27 Begin: SetSortSpec for SqlObj 'SRF Service Method' at 1b4a3548, Sort Spec: 'Name' ObjMgrSqlObjLog Sort 5 000000094adf0e34:0 2009-10-21 13:34:27 End: SetSortSpec for SqlObject at 1b4a3548 ObjMgrBusCompLog Error 1 000000094adf0e34:0 2009-10-21 13:34:27 (buscomp.p (32075)) SBL-DAT-00225: The value entered in field Method Name of buscomp Operation does not match any value in the bounded pick list PickList SRF Service Method - Bounded. ObjMgrLog Error 1 000000094adf0e34:0 2009-10-21 13:34:27 (adptutils.p (5634)) SBL-EAI-04451: Method 'SetFieldValue' of business component 'Operation' (integration component 'Operation') for record with search specification '[Operation Name] IS NULL' returned the following error:"The value entered in field Method Name of buscomp Operation does not match any value in the bounded pick list PickList SRF Service Method - Bounded.(SBL-DAT-00225)": Method 'SetFieldValue' of business component 'Operation' (integration component 'Operation') for record with search specification '[Operation Name] IS NULL' returned the following error:"The value entered in field Method Name of buscomp Operation does not match any value in the bounded pick list PickList SRF Service Method - Bounded.(SBL-DAT-00225)"(SBL-EAI-04451)