SBL-BPR-00193: Siebel Operation failed because the Object ID %1 passed in cannot be found in primary business component %2.

Applies to:

Error Message Area:Business Processes/Workflow - BPR
Version:Siebel 7.5.3

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-BPR-00193: Siebel Operation failed because the Object ID %1 passed in cannot be found in primary business component %2. An invalid "Object ID" or row ID was passed to the process, the "Object ID" does not match any existing row IDs for the specified primary business component. Make sure the specified "Object ID" does exist in the primary business component, and that there are no search specifications or visibility settings that restrict access to the record.

Scope

This document is informational and intended for any user.

SBL-BPR-00193: Siebel Operation failed because the Object ID %1 passed in cannot be found in primary business component %2. An invalid "Object ID" or row ID was passed to the process, the "Object ID" does not match any existing row IDs for the specif...

Explanation

An invalid "Object ID" or row ID was passed to the process. The "Object ID" does not match any existing row IDs for the specified primary business component.

Corrective Action

Make sure the specified "Object ID" does exist in the primary business component, and that there are no search specifications or visibility settings that restrict access to the record.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.4 [16180]
Database: Microsoft SQL Server 2000 SP 2
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Microsoft Windows 2000 Server SP 3

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

Symptoms

Hi,

After multiple attempts to resolve a workflow problem I am having, I would appreciate some guidance on the following issue:

I have developed a workflow process that involves the Opportunity BC. Once started, the worflow process encounters a decision point involving values on the Opportunity BC. If these conditions are met, it advances to a sub-process involving a subordinate BC, Opportunity Product. In this sub-process the desire is to identify any records, related to the Parent Opportunity that have a Product Line Type field LIKE 'HDW*' . If yes, an activity is generated. If not, the process ends. When I execute the process in the simulator, it fails indicating that the Object Id value does not exist for the Opportunity Product BC. I have tried re-assigning the Object ID from the parent process (Opportunity) to an Input argument for the sub-process, but with the same result. Ultimately, my question is this, can two objects (Opportunity and Opportunity Product) related via a link, be evaluated within a single workflow process? If so, how is the Object ID from the Workflow Process (Opportunity) passed to the workflow sub-process (Opportunity Product) as a query criteria instead of an Object ID? I appreciate any guidance you can provide on this issue.

Regards

Solution

Message 1

For the benefit of our readers.

I have taken ownership of your SR. Your current configuration is a main process using Opportunity BO which has a sub process call to the Opportunity Product BO so you would like to know if you can change this configuration where this is all done using 1 process. Additionally, while testing your configuration you're running into the following error message;

"Object Id value does not exist for the Opportunity Product BC"

I checked Tools and found that Opportunity business object has relationship to Opportunity Product business component. Navigate to Tools > expand Business Object > select Opportunity > click Business Object Component and you'll see all the child BC related to your object.

So to answer your question, yes you can query the parent BO and update the child BC all within 1 workflow process. You would change your configuration where the next step after the decision step is a siebel operation step and remove your sub process step.

Siebel Operation:
Operation = Update
Business Component = Opportunity Product (basically any BC you see, you can use)
Fields applet = set the field (s) you want to update on the Opportunity Product BC
Search Specifications applet = you would use the following syntax as per following,

"[Product] LIKE 'C*'"

I've created a simple process "Update Opty Product.xml", with most of your requirements and attached this to your SR. My configuration is based on vanilla

...continued...

Message 2

...2/2...

functionality so any config changes to your buscomp and LOVs may cause import to fail. After importing my test process, edit the Search Specification and Object Id in order to test for your requirements. NOTE, test using the object Id from your primary business component which is Opportunity.

Please reference the following documentation in Siebel Bookshelf v7.5.x:

Siebel Tools Reference v > Business Objects Layer > Business Components > Search Specification Property

Siebel Business Process Designer Administration Guide > Designing Workflow Processes > Working with Siebel Operation Steps

Siebel Business Process Designer Administration Guide > Designing Workflow Processes > Working with Siebel Operation Steps > Defining a Siebel Operation Step

Additionally, SupportWeb has published resolved SRs issues so using the keywords, "child and parent and siebel operation and update", I was able return several SRs with related to your requirements. I also found the following document that will help explain the issue you have while testing.

"Siebel Error Message SBL-BPR-00193: Siebel Operation failed because the Object ID %1 passed in cannot be found in primary business component %2."

Please let me know if my suggestion help resolve your issue.

Thanks,

Siebel Technical Support