SBL-DAT-00607: Join '%1' in business component '%2' has the multi-valued field '%3' as the source field.

Applies to:

Siebel Tools - Version: 8.1.1 [21112] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

After upgrading a customized Siebel application from 7.5.3 to 8.1.1.2, when the user opened a view containing a configured business component, an error message occurred:

Join 'Vis Owner Employee Position Inter Table Join Alias' in business component 'XYZ Service Plan' has the multi-valued field 'Owner Id' as the source field. (SBL-DAT-00607)

However, the join that this message refers to does not exist in the definition of the business component.

Cause

View modes result in additional, dynamically generated joins in the SQL statement for restricting visibility as desired. The error message refers to such a dynamically created join, which is why a join of that name does not occur in the business component definition.

In this particular case, the issue has been caused by a custom BusComp View Mode. The view mode's Visibility Field was set to "Owner Id". However, field "Owner Id" is a multi-value field and thus must not be specified in the Visibility Field property.

Solution

First, determine which kind of visibility you need to implement.

If you need to implement single-party visibility, select an single-value field that refers to an appropriate party ID.

1. Open Siebel Tools, navigate to Business Component > BusComp View Mode, and select the view mode with the wrong Visibility Field value.
2. Change Visibility Field property to a suitable field, such as, for example, "Primary Owner Id".
3. Save and compile the changes.

If you need to implement team-based visibility, clear the Visibility Field property and use the properties Visibility MVField and Visibility MVLink instead.

1. Open Siebel Tools, navigate to Business Component > BusComp View Mode, and select the view mode with the wrong Visibility Field value.
2. Clear the value of the Visibility Field property.
3. Set the property Visibility MVField to your MVField; for example, "Owner Id".
4. Set the property Visibility MVLink to the related Multi-Value Link; for example, "Owner".
5. Save and compile the changes.

See also:

Bookshelf 8.1 > Siebel Security Guide > Configuring Access Control > Viewing Business Component View Modes

Applies to:

Siebel Tools - Version: 7.5.3.11 [16199] - Release: V7
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.11 [16199]
Database: Microsoft SQL Server 7.0 SP 3
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Microsoft Windows 2000 Server SP 4

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

Symptoms

SBL-SCR-00141, SBL-DAT-00292, SBL-DAT-00322, SBL-DAT-00607, SBL-BPR-00162

Behavior 1:
After the upgrade to Siebel 7.8. We have issue with tab of Accounts -> Note/SRs. It give use a error of:

We detected an Error which may have occurred for one or more of the following reasons:

Join 'S_SRV_REGN' in business component 'Service Request' has the multi-valued field 'Service Region Id' as the source field. (SBL-DAT-00607)

I checked that the the 'Service Region Id' field's multi-valued is check in the prior upgrade and it also checked after the upgrade of 7.8.


Behavior 2:
When we try to add a product to the Quote, we get the Error message of (SBL-DAT-00322). In fact it is getting the following error messages:

[1] An error has occurred picking the current row.

Please continue or ask your systems administrator to check your application configuration if the problem persists. (SBL-DAT-00292)

[2] Siebel eScript runtime error occurred in procedure ‘InvokeMethod’ of BusComp [Quote Item]:

Error: SiebelError: The specialized method 'ClearPrice' is not supported on Business Component 'Quote Item' used by Business Object 'Quote’. (SBL-DAT-00322)
(SBL-SCR-00141)

[3]Stack trace:
BusComp [QuoteItem].InvokeMethod(), Built-in function
BusComp [QuoteItem].BusComp_SetFieldValue(), Line: 463


Under Siebel 7.5.3, the same server side script working, but break down under 7.8

Cause

n/a

Solution

Message 1

For the benefit of others:

Behavior 1)

Customer upgraded from 7.5 to 7.8 and was receiving the following message:

Join 'S_SRV_REGN' in business component 'Service Request' has the multi-valued field 'Service Region Id' as the source field. (SBL-DAT-00607)

7.8 is an enhancement and this validation was added since 7.7. Actually joins with multi-valued field specified as the source field are not supported. This is also not supported for 7.5, but this was not validated in the release that the customer was using.

To solve this, the usual approach is to use the Primary Id Field of the Multi Value Link (that is related to the MVF) as the Source Field of the Joins Specification object type.

Message 2

Behavior 2)

On Quote Screen, when associating Products as Line Items by clicking on a customized button, it was getting the following error:

The specialized method 'ClearPrice' is not supported on Business Component 'Quote Item' used by Business Object 'Quote’. (SBL-DAT-00322)

“ClearPrice” method is used to first clear out the values from all the price columns when adding a new product.

In Standard Siebel there is an user property in “Quote Item” BC called “On Field Update Invoke”. It is defined as following: "Product", "Quote Item", "ClearPrice". This User Property means when the field Product is changed, the method ClearPrice is invoked.

The customer was using the following code to replace “On Field Update Invoke” BC User Property in 7.5:

this.InvokeMethod("ClearPrice");

However in 7.8 this user property is inactivated in Standard Siebel. And ‘ClearPrice’ specialized method is obsolete in 7.8.

7.8 the pricing functionality has completely changed. In 7.5.3.x all pricing logic was inside the BC classes. In earlier releases, Siebel order management functions and function calls were hard coded. Then in 7.8 this logic has being removed from the class in order to allow some flexibility to the users.

There is a new feature called Signals which will trigger pricing (Sitemap -> Administration - Order Management -> Signals).

Message 3

It was found that ‘SetFieldValue’ Signal has the feature ‘ClearPrice’ method had. It is necessary to execute the following steps before call this signal by scripting:

1) Go to Siebel Tools: In the Workflow Process object type, Revise and Deploy all workflows belonging to the bellow groups. Then, in Workflow Process enter query for group:

[Group] = "Configurator" OR [Group] = "Asset Based Ordering" OR [Group] = "Eligibility & Compatibility" OR [Group] = "eAdvisor" OR [Group] = "eSales" OR [Group] = "Compound Product Validation" OR [Group] = "Product Recommendation" OR [Group] = "Product Promotions" OR [Group] = "Pricer" OR [Group] = "C/OM UI Processes" OR [Group] = "Application Deployment Manager" OR [Group] = "User Registration"

2) Then start the Siebel Application and go to Administration - Business Process > Workflow Deployment view and activate (by clicking on the Activate button) all the workflows that was revised in Siebel Tools.

3) After conclude the step 2, please go to Administration > Runtime Events > Events and choose Reload Runtime Events from the menu.

For more information how to invoke the ‘SetFieldValue’ signal, please refer to ‘Siebel Order Management Infrastructure Guide > Signals > Invoking Signals from Controls and Custom Script’ for more information.


Siebel Technical Support

Applies to:

Product Release: V7 (Enterprise)
Version: 7.8.2.2 [19219]
Database: Oracle 9.2.0.4
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 2.8

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

Symptoms

Hi,

We are having an issue with deploying the workflow. We have migrated from 7.53 to 7.82 and have modified some of our workflows. It was deployed in Siebel Tools and activate in the thin client. We observer that the workflow process screen does not reflect the latest workflow that as the process properties still reflect the old values.

We are having an issue with executing a workflow process. We have migrated from 7.53 to 7.82. We are having a workflow that works in our 7.53 env but throws up the following error.

"Object manager error: ([0] Join 'Organization Reporting Relationship Table Join Alias' in business component 'CSC Product Defect' has the multi-valued field 'Organization' as the source field"

On verification this join does not exist in our BC or our repository.

Detailed log file enclosed.
Also enclosed is the sif file of the CSC Product Defect and the workflow process.

Thx,
Mohan

Solution

Message 1

This publication is for the benefit of our readers.

Here is the error extracted from WfProcMgr_33030.log 7.8.2.3 [19221] ENU:

ObjMgrLog    Error    1    0    2006-08-24 15:15:07    (objdef.cpp (14773)) SBL-DAT-00607: Join 'Organization Reporting Relationship Table Join Alias' in business component 'CSC Product Defect' has the multi-valued field 'Organization' as the source field.

This error is configuration related. Since workflow process instantiates business component configuration and runs like a client, it will error out if there ir a configuration problem.

To help find out if this is configuration related independent from workflow process, if possible, can you log in to client application, manually perform the step(s) that workflow process is intended to do, and see if you can reproduce the same error. If so, then it is a configuration issue, whether it is from your custom configuration or configuration specific to 7.8 upgrade.

Thanks,

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Sun Solaris 8

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

Symptoms

SBL-DAT-00326

We are in the process of upgrading our Siebel 7.0.4 application to Siebel 7.7.2. After the sucessful upgrade and the repository merge, I ran the Phys. schema upgrade and it finished successfully.

I compiled the SRF (selecting all the objects) and placed it in the Siebsrvr\Objects\ENU directory with the name Premier.srf. Also, placed the scripts under the SWEApp\Public\ENU directory. Then changed the repository file name in the uagent.cfg in the Siebsrvr\Bin\ENU directory with Premier.srf.

Now, after I restarting the services (IIS, App Srvr and Gateway Srvr), am not getting any views at all. I got the following error message.

"We detected an Error which may have occurred for one or more of the following reasons:

View Map is not initialized.(SBL-DAT-00326)"

I tried to use this SRF with the dedicated client and it works fine.

Solution

Message 1

For the benefit of the reader:

Customer upgraded from Siebel Application Version 7.0.4 to Siebel 7.7.2. After the successful upgrade a new SRF file was compiled. Using this file user log into Dedicated Client and was able to use the application. With the same srf and database when user try to connect login using thin client it failed with following error.


View Map is not initialized.(SBL-DAT-00326)"

Following steps were taken to resolve this issue.

a) Customer was suggested to enable following tracing using Server Manager command :

Change evtloglvl %=5 for comp <AliasNameOfObjectManager>

This will increase required level of tracing for Object manager that user uses to connect.

b) After above tracing was enabled, user logged in and got the same error as above. The object manager log for this user session was provided to Siebel Technical Support.

c)    In the object manager log had following error

            *******

ObjMgrLog    Error    1    0    2005-01-14 12:33:08    (objdef.cpp (14625)) SBL-DAT-00607: Join 'S_PERIOD' in business component 'Opportunity' has the multi-valued field 'Quarter' as the source field.

ObjMgrSessionLog    Error    1    0    2005-01-14 12:33:08    (model.cpp (608)) SBL-DAT-00326: View Map is not initialized.
            ********
After customer corrected the Join property in the Opportunity buscomp, the application works fine.

Thanks