SBL-DAT-00464: Unable to find the parent buscomp of buscomp '%1', possibly because there is no active link at this time.

Applies to:

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

Symptoms

Using Siebel Tools:

Select Tools > Search Repository
Enter search string "abc" 
In "Types" select "Task Step IO Argument" 

> Search Now

The following error is shown:
"Unable to find the parent buscomp of buscomp 'Repository Task Step IO Argument', possibly because there is no active link at this time.(SBL-DAT-00464)"

Cause

Product Defect with similarity to Change request 12-O11LEP  (fixed in 8.0) as documented in "Repository Search; Error on object WF Step Branch (Doc ID 542402.1)" on Metalink3.

Solution

Change Request 12-1THO6X1 has been logged to address the error given when searching type: "Task Step IO Argument"

The search functionality does not work for Task Step IO Argument Types. De-select the Task Step IO Argument when doing a Repository Search and perform a manual search for this Type using the Flat Tab.

For more details to fix this defect please refer to Doc Id: 542402.1 (Repository Search; Error on object WF Step Branch)

References

NOTE:542402.1 - Repository Search; Error on object WF Step Branch

Applies to:

Siebel Tools - Version: 7.7.1 [18306] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

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

Symptoms

when doing a repository search in Tools on the object WF Step Branch I get the error "Uable to find the parent buscomp of buscomp 'Repository WF Step Branch', possible because ther is no active link at this time. (SBL-DAT-00464)".

I set the /s sql logging on Tools but wasn't unable to find the 'abc' I was quering on, on the object 'WF Step Branch'.
Something may have gone wrong during the Repository Merge when importing the old WF's. Could you advice on what next steps to take to diagnose this problem?

Cause

Can not search for WF Step Branch or WF Step I/O Argument in Siebel Tools

SYMPTOMS:

Select Tools > Search Repository
Enter search string "abc"
Select WF Step Branch or WF Step I/O Argument as type:
The following error is shown:
Unable to find the parent buscomp of buscomp 'Repository WF Step Branch', possibly because there is no active link at this time.(SBL-DAT-00464)
Unable to find the parent buscomp of buscomp 'Repository WF Step I/O Argument', possibly because there is no active link at this time.(SBL-DAT-00464)

Solution

SOLUTION:

Change Request 12-O11LEP has been logged to address this behavior.

Related Change Request 12-1THO6X1 has been logged to address the error given when searching type: "Task Step IO Argument" (Reference: Repository Search: "Unable to find the parent buscomp of buscomp 'Repository Task Step IO Argument', possibly because there is no active link at this time.(SBL-DAT-00464)" (Doc ID 833783.1))


Steps to fix this defect:

-CR 12-O11LEP for search "WF Step Branch" or "WF Step I/O Argument as type"
-CR 12-1THO6X1 for search "Task Step IO Argument"

1.Copy Siebel Tools SRF file from Tools\OBJECTS\(Language) directory.

Copy of siebel_sia.srf

(If using SEA then it will be Siebel.SRF)

2.Open Siebel Tools.

3.From Tools explorer > Go to Business Component

4.Search for “Repository Task Step IO Argument” BC from Business Component
(In case of CR 12-O11LEP - search for "WF Step Branch" or "WF Step I/O Argument as type")

5.From Tools explorer > Business Component > Field

6.Create new field

Field Name : Parent Type
Join: Parent Alias
Column: TYPE_CD

7.Create new field

Field Name : Parent Type Code
Calculated: Checked
Calculated Value: LookupName("TASK_STEP_TYPE_CD",[Parent Type])

8.Create new field
(Some of other version already exist this field then it is required to uncheck calculated value)

Field Name : Siebel Oper BC Name
Join: Parent Alias
Column: BUSCOMP_NAME

9.Add join for field “Parent Subtask Name”
Calculated: Unchecked
Calculated Value: Clear
Join: Parent Alias
Column: SUBTASK_NAME

10.Make sure to compile to copied SRF file. Tools\OBJECTS\(Language) \Copy of siebel_sia.srf

11.Close Siebel tools

12.Copy over Tools\OBJECTS\(Language) \Copy of siebel_sia.srf to Tools\OBJECTS\(Language) \ siebel_sia.srf

13. Start Siebel Tools then test.

Applies to:

Siebel Tools - Version: 7.7.2 SIA [18325] to 7.7.2.6 SIA [18372] - Release: V7 to V7
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.2.6 [18372]
Database: Microsoft SQL Server 2000 SP4
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-3090062471.

Symptoms

SBL-DAT-00464

After the upgrade to 7.7.2.6 we get the warning SBL-DAT-00464* as an "Error" on the GUI and the creation of the contact record is
interrupted/stopped. The error is reproducible with our current SRF running on 7.7.2.5. I.e. running 7.7.2.6 software but keeping
the SRF that was compiled for with 7.7.2.5 and that is now running on our production system. That to me clearly shows that this error is due
to the fact that we are trying to run 7.7.2.6. We have tried

1) spooling the SQL
2) running tools and client with enhanced logging (SET SIEBEL_LOG_EVENTS=5)
3) removing all scripts of the BC Contact
4) removing all audit trailing for BC Contact
5) making sure we don't have any state model up and running for BC Contact
6) checking for any runtime events on BC Contact
7) removing validation rules for BC Contact

When running enhanced logging we se that we have SBL-DAT-00464 warnings on BC Action and Service Request too, but
on those BC we don't get any warnings on the GUI and we can create records without any problems.

BC Contact:

1) We can do update on existing contact records without getting any error
2) We can create records on the tables S_USER, S_CONTACT, S_CONTACT_X, S_CONTACT_XM, S_PARTY,... when coming from another BC e.g. BC Employee

Please give us some feedback on where this is a known issue or some input on where we can look to track down this error.


*)
ObjMgrQueryLog    Warning    2    0    2006-07-10 10:48:56    (query.cpp (11135)) SBL-DAT-00464: Unable to find the parent buscomp of
buscomp 'Contact', possibly because there is no active link at this time.

Cause

After reviewing the configuration customer found that the only place where the field is used was as a predefault on another BC

Solution

After making the change to this field solved the problem.

ParentFieldValue("Id")

To:

IIF(ParentBCName() IS NOT NULL, ParentFieldValue("Id"), "")

Applies to:

Siebel Tools - Version: 7.5.2.214 SIA [16066] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.2.214 [16066] Fin Svcs
Database: Oracle 8.1.7.3
Application Server OS: Microsoft Windows 2000 Server
Database Server OS: HP-UX 11i

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

Symptoms

SBL-DAT-00464

We have requirement to set pre-default field values when a complaint record (part of Service Request) is created via smartscripts.

We have created runtime event PreInvokeMethod on the service request business component to set the profile attribute and call the smartscript

below is our configuration:
1. we set the link spec = TRUE on the fields on the contact business component (eg:Last Name)
2. in the ActionSet, I used created the following actions
     Name = WBC_Set_Last_Name
     Action Type = Attribute Set
     Profile Attribute = ActiveContactLastName
     Set Operator = Set
     Value = ParentFieldValue("Last Name")
3. on the Service Request business component field, i used the profile attribute value to pre-defaul the field.
4. compile the SRF
5. reloaded personalisation

We have experience the following error when the create complaint button is clicked on the customer view.
"Unable to find the parent buscomp of buscomp '', possibly because there is no active link at this time."

your urgent attention to this is required.

Cause

It has been observed that using ParentFieldValue function in Runtime Events causes the following error message:

"Unable to find the parent buscomp of buscomp '', possibly because there is no active link at this time."

BUG 12-L0RK3B has been logged to address this.

Solution

To achieve customer's requirement, customer has been advised to get Contact Last Name field from scripting by changing the action set to invoke a business service to set the profile attribute instead.

The behavior is also fixed in Version 8.0

Additional Keywords:
Personallization, ParentFieldValue