SBL-DAT-00461: The operation is invalid when there are no rows available.

Applies to:

Siebel Tools - Version: 7.7.2 SIA [18325] to 8.1.1 SIA [21111] - Release: V7 to V8

Information in this document applies to any platform.

Goal

To know if it is possible to update MVG fields directly by typing in the values, like any other text field, without using MVG applet.

Solution

If MVG fields are updated directly without using MVG applet, it would sometimes raise errors like SBL-UIF-00299 and SBL-DAT-00461.

For example, if we try to update the Personal Address MVG fields like Street Address, City, State, Country etc, directly, without invoking the Personal Address MVG applet, then it would throw error messages like SBL-UIF-00299 and SBL-DAT-00461.

The reason is the records of the MVG are stored in a different table with a different business component. Hence updating a MVG fields directly could lead to unexpected errors. On updating the MVG fields through MVG applet, these kind of errors could be avoided.

Oracle does not support updating the MVG fields directly and supports using MVG applet only to update the MVG fields.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221] Life Sci
Database: Oracle 10.2.0.3
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9

This document was previously published as Siebel SR 38-3538739751.

Symptoms

While using create target list functionality (described in: Technical Note 600: Creating Target Lists Using Siebel Analytics Version 7.7.1) having national characters in filter we receive the following error: SBL-DAT-00461. The error does not appear when national characters are removed from the filter. Please assist.

Solution

Message 1

For the benefit of other users, the customer was encountering the error message: SBL-DAT-00461 while creating Target Lists with their national characters (umlaut character like Ö)

The customer was suggested to add a specific argument to every analytics symbolic URL that they use to generate the Target list. This argument is "Charset", it is a constant and the value is "UTF-8".

In order to add this argument to a symbolic URL, you will have to:
1- Navigate to Site Map > Integration Administration > WI Symbolic URL List
2- Select "Symbolic URL Administration" in the listbox of the applet
3- Query for an analytics symbolic URL that the customer is using (like for example: Name = SiebelAnswers)
4- Create a new record in the "Symbolic URL Argument" applet
5- Set the following colmuns:
    - Name = Charset
    - Required Argument = Yes
    - Argument Type = Constant
    - Argument Value = UTF-8
    - Append as Argument = Yes
    - Sequence # = <next sequence>
6- Repeat 3, 4, 5 for other analytics symbolic URL

Peforming the above sequence of steps has resolved the reported behavior.

Thank you.

Applies to:

Business Intelligence Suite Enterprise Edition - Version: 7.8.5.1 [AN 6927] and later   [Release: V7 and later ]
Information in this document applies to any platform.

Symptoms

Analytics 7.8.5.1 with Life Sciences 7.8.2.12 SIA [19247] ENU patch

Create Target List functionality does not work when Japanese characters are used in the request filter criteria (eg target list's logical query contains a japanese character).
but a request in answers with a filter on japanese characters runs fine.

This is the scenario:
* Open Siebel ePharma Web Client
* Navigate to Answers
* Create a logical Query with a japanese character in the filter
eg:
SELECT

Contacts.ROW_ID saw_0,

Contact."Last Name" saw_1,

Contact."Middle Name" saw_2

FROM "Campaign Load - Contacts"

WHERE Contact."Middle Name" = ' '日本最大' '

ORDER BY saw_0, saw_1, saw_2
* Add View > Click on Create Target List.
* Enter a name for the Target List and click OK.
* You should be taken to List Mgmt Lists View showing the new target list record.


But you get an error:
We detected an Error which may have occurred for one or more of the following reasons:
The operation is invalid when there are no rows available.(SBL-DAT-00461)

Charset is set to UTF-8 in the "Symbolic URL Administration" for Answers as per recommendation in CR 12-12ESASL.

Cause

The javascript call to the Siebel Business service contains the JP chars.
The Obj Mgr log contains the JP chars when processing the business service arguments.
The analytics query log which captures the ODBC query originating from the Siebel App Server contains ?? instead of the correct chars which causes the query to fail.


So the issue is not with the call from Analytics to Siebel (Javascript call to Siebel) but with the return call to Analytics via the ODBC driver.

Solution

You should be able to use Target Lists with filters containing japanese filters if the following 2 regional settings are set on the analytics server machine:

1. In Control Panel > Regional Settings > Languages > installed east asian languages

2. In Control Panel > Regional Settings > Advanced tab: "Language for non unicode program" set to Japanese, and Japanese selected in the code page conversion table.

Applies to:

Siebel Universal Customer Master - Version: 8.0.0.2 SIA [20412] - Release: V8

Information in this document applies to any platform.

Symptoms

When sending a crmml message into the UCM system, the message contains xml tag for PartyUid and Id.

When a new set of PartyUid and Id values are submitted into the UCM system, this creates a new account into the UCM system.

Then, another crmml message is sent to UCM system with a new PartyUid value but same Id value. In this case, the UCM workflow 'UCM Transaction Manager' business service should use the value from Id tag to query for a best version record. Since the new account created earlier has this Id value, it would have produced a match and performed an upsert using the crmml message in the 2nd request.

However, the problem is that the 'UCM Transaction Manager' business service is querying for the best version record using the value from the wrong xml tag. The query should be using the value from the incoming crmml message Id tag to find the best version record. Instead, the 'UCM Transaction Manager' is using the value from the PartyUid tag, the query using this value returns 0 rows, which then generates an error and causes the entire transaction to fail with the following messages:

ObjMgrBusCompLog Warning 2 0000001a4a48901c:0 2009-06-29 04:55:22 (sqlobj.cpp (26590)) SBL-DAT-00461: The operation is invalid when there are no rows available.

EAISiebAdpt EAISiebAdptWrn 2 0000001a4a48901c:0 2009-06-29 04:55:22 CIF Transaction Mgr Failed to find current record for incoming record with SDH Id User Key
ObjMgrBusServiceLog Error 1 0000001a4a48901c:0 2009-06-29 04:55:22 (fasvcciftransmgr.cpp (2467)) SBL-IAI-00462: CIF Transaction Mgr Failed to find current record for incoming record with SDH Id User Key
EAISiebAdpt EAISiebAdptWrn 2 0000001a4a48901c:0 2009-06-29 04:55:22 CIF Transaction Mgr service: Existing Account Best Version Record with RowId = 1-4QHSLF not found for System Id Siebel
ObjMgrBusServiceLog Error 1 0000001a4a48901c:0 2009-06-29 04:55:22 (fasvcciftransmgr.cpp (1787)) SBL-IAI-00502: CIF Transaction Mgr service: Existing Account Best Version Record with RowId = 1-4QHSLF not found for System Id Siebel

Cause

The cause of the incorrect query is due to a known existing product defect.

When the cross reference is found, the business service is using Id tag value to query for the best version record from table for history records, it's using party uid to do the query which is incorrect.

The error has been reproduced by Oracle Support, confirmed this is a known issue and has been addressed in a later release already.

The issue has been tracked by the following change request:

CR # 12-1U09AUL - "UCM Transaction Manager" queries for best version record using the with the wrong value

Solution

The above CR # 12-1U09AUL is fixed in FR # 12-1U09ZZO target for 8.0.0.2 [20412] QF02B4 and also in  Siebel 8.1.1 QF0001 for ACR 437.

The 8.0.0.2 [20412] QF02B4 can be downloaded from Metalink > Patches and Download area using patch number: 8705288

For the 8.0.0.2 Quickfix, there are some repository changes required, delivered through the QF's FR_12-1U09ZZO.zip file, which includes 4 Buscomp sif files:

BC - CIF Account Reference.sif
BC - CIF Contact Reference.sif
BC - CIF FINCORP Account Reference.sif
BC - CIF Household Reference.sif

These sifs need to be imported into the repository and compiled into the client and server srf files.

1.  Lock project VEAI UCM CIF UI in Siebel Tools.
2.  Make copies of the original versions of the above business components in your repository.
3.  Import SIF files provided in <tools>/REPPATCH/ FR_12-1U09ZZO.zip
4. Compile changed project(s) to client and server srf files.
5. Restart the Siebel Client and Siebel Server services.

References

BUG:12-1U09AUL - "UCM TRANSACTION MANAGER" QUERIES FOR BEST VERSION RECORD USING THE WITH THE WRONG VALUE