SIEBEL ERROR CODES: SBL-DAT-00467: Unable to find value for parent field '%1.%2'. Make sure LinkSpec = TRUE is used on the parent field.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.2.216 [16084] FRA Fin Svcs
Database: Oracle 8.1.7.4
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: IBM AIX 4.3.3

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

Symptoms

SBL-DAT-00467

Navigating into the application leads to a crash of Internet Explorer.

The steps in our application to reproduce the crash are:
- Log into the application
- Click on Contacts screen tab
- Drill down on the first contact
- Drill down on the only offer shown
- Drill down on the contact record
- Click on the Siebel Back arrow
- Drill down another time on the contact
At this stage a crash occurs.

Note that script are used in this part of the application and without the script, the crash is not encountered.

Solution

Message 1

A specific navigation using their custom application leads to a crash of the Internet Explorer with a call stack like:
ieop_aui_0fb8024f_ade2_4c40_9a54_8582bffb9348!CSSJannaList::FireEvent+0x11e
ieop_aui_0fb8024f_ade2_4c40_9a54_8582bffb9348!CSSJannaList::CallOnClickLink+0x163
ieop_aui_0fb8024f_ade2_4c40_9a54_8582bffb9348!CSSJannaList::OnLButtonUP+0x417
ieop_aui_0fb8024f_ade2_4c40_9a54_8582bffb9348!CSSJannaList::ProcessWindowMessage+0x109
ieop_aui_0fb8024f_ade2_4c40_9a54_8582bffb9348!ATL::CDialogImplBaseT<ATL::CWindow>::DialogProc+0x4d
USER32!DefDlgProcWorker+0x6f

The navigation that lead to the crash was mainly a drilldown with a script being invoke in the applet invoke method. This script callled a server method which was in this case: TheApplication().GetProfileAttr().

The crash has been reproduced and Change Request 12-J6FNYU has been raised.

At the moment, the only recommendation to be made is to not have calls to the server from an Invoke event especially when these invoke events are call by methods that need a refresh of the view like DrillDown, GotoView ...

Thank you.

Applies to:

Siebel Tools - Version: 7.5.3.7 [16190] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.4 [16180]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Microsoft Windows 2000 Advanced Server SP 4

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

""Checked for Relevance on 21-May-2010""

Symptoms

We get an error when I click on the "New" button on the Opportunity applet. The error message is attached. The error message is:

"An Error Occurred calculating the Default value for Field "Opportunity Close Date" in business component 'Opportunity-SalesRep-VisMvgSqlBcDef (SBL-DAT-00412)."

I have checked the application and there is no BC with "VisMvgSqlBcDef". Please let me know the reason for this error. I have looked up the SupportWeb but could not find anything helpful to our situation.

We get this error in a new Dev environment (Dev 5) which has Patch 11 installed. We do not get this error in the Dev 3 environment. The only difference between the two environments is the Patch 11.

Cause

Solution

The behavior described by the customer is reproducible with a standard Siebel environment version 7.5.3.7 or higher by performing the steps below:

# Using Tools:

1. Change the pre-default value of field 'Opportunity Close Date' in Business Component (BC) 'Position' to:

Expr: "IIf ( ParentBCName () = 'Opportunity' , IfNull(ParentFieldValue ('Default Close Date') , Today ()), Today () )"

2. Add the following calculated field in BC 'Opportunity':

Name: Default Close Date
Calculated Value: Today() +2 (For example)
Link Specification: TRUE

# Using Siebel application:

1. Navigate to "My Opportunities" view
2. Create a new record:
> The following errors will occur:
- - -
[1] An error occurred calculating the default value for field 'Opportunity Close Date' in business component 'Opportunity-SalesRep-VisMvgSqlBcDef'.(SBL-DAT-00412).
[2] Could not evaluate expression 'Expr: "IIf ( ParentBCName () = 'Opportunity' , IfNull(ParentFieldValue ('Default Close Date') , Today()), Today() )"'' for field 'Opportunity Close Date' in business component 'Opportunity - Sales Rep - VisMvgSqlBCDef'.(SBL-DAT-00394)
[3] Unable to find value for parent field 'Opportunity.Default Close Date'. Make sure LinkSpec = TRUE is used on the parent field.(SBL-DAT-00467)
- - -

This issue is not reproducible with version 7.5.3.6 or below and with version 7.7 either.

Bug 12-VS5MUH has been logged to address this product defect.

Note that the issue occurs only if you try to use the ParentFieldValue function to pre-default an intersection field in a child BC with the value of a field in the parent BC. In the customer case the field 'Opportunity Close Date' in BC 'Position' is indeed based on column FCST_CLS_DT in table S_OPTY_POSTN. This table is an intersection table used by the M:M link between BC 'Opportunity' and BC 'Position'.

Moreover it occurs only when a child record is also created at the same time as the parent record. In the customer case the child position record is automatically created because of the visibility settings of BC 'Opportunity'. This BC has indeed the following BusComp View Mode:
- - -
Name: Sales Rep
Owner Type: Position
Visibility MVField: Sales Rep
Visibility MVLink: Position
- - -

For the customer the suggestion to pre-default the field 'Opportunity Close Date' using the value of a field in BC 'Opportunity' was to use scripting in the BusComp_NewRecord event of BC 'Opportunity'. The steps are the following:

(a) Instantiate the MVG BC associated to the MVF 'Sales Rep' in the current BC.
(b) Query the MVG BC to retrieve the position record automatically created.
(c) Set the value of field 'Opportunity Close Date' with the value wished (e.g. the value of the field 'Default Close Date' in the current BC.
(d) Destroy the instance of the MVG BC.

For further information about the programming possibilities and Siebel interface events and methods, please refer to the Bookshelf:

# Siebel Object Interfaces Reference
- Programming
- Interfaces Reference

# Siebel VB Language Reference
# Siebel eScript Language Reference

References

BUG:12-VS5MUH - ISSUE WHEN PARENTFIELDVALUE FUNCTION IS USED TO PRE-DEFAULT A FIELD BASED ON AN INTERSECTION COLUMN

Applies to:

Product Release: V7 (Enterprise)
Version: 7.8.2.4 [19224]
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: HP-UX 11.11

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

Symptoms

Users are getting the attached error when they try to set the activity status to 'Done'.

Here are the steps to reproduce the problem in vanilla siebel:

1) Go to the Projects / Activities screen
2) Create a new activity and set the 'Type' field to 'Information Needed'
3) Drill down into the Activity
4) Click on the Service screen tab
5) Click the back button of the browser
6) Set the Status to "Done"
7) You get the error message: SBL-UIF-00299 and SBL-DAT-00467

Please let us know if there is anything we can do in tools to fix this error?

Solution

Message 1

For the benefit of other readers:

Hello Curtis,

The behavior reported has been determined as a Product Defect.

At present the workaround is to go back to the first screen (Projects / Activities) and then change the Status.

Change Request 12-1KD8YKF has been logged to address this product defect.

Regards,

Oracle | Siebel Technical Support.

SIEBEL ERROR CODES

Search This Blog

SBL-DAT-00467: Unable to find value for parent field '%1.%2'. Make sure LinkSpec = TRUE is used on the parent field.

Applies to:

Symptoms

Solution

Message 1

Applies to:

Symptoms

Cause

Solution

References

Applies to:

Symptoms

Solution

Message 1

Applies to:

Symptoms

Solution

Message 1

No comments:

Post a Comment