SBL-BPR-00130: Runtime event '%1' ignored. Event business object '%2' does not match business object '%3' associated with process definition '%4'.

Applies to:

Siebel CRM - Version: 8.0.0.7 SIA [20426] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

On : 8.0.0.7 SIA [20426] version, Siebel EAI, MS Win

There are few runtime events which are working fine when user is updating the records from UI. There is an interface based on JMS receiver component which receives the xml message and pass the request to WF and in WF step siebel records are updated using EAI Siebel Adapter BS / Upsert method.

From UI when setting the activity type "Obtain M/L Approval" to Done invokes the runtime event and set the next activity "Revise Content" to Assigned. But with JMS Receiver comp when updating the same activity "Obtain M/L Approval" to Done it does not invoke the Runtime event and make the next activity "Revise Content" to Assigned.

There is not error from JMS while processing the message.

Cause

The issue seems to be caused due to some difference in the objects being used in the Runtime event definition versus the objects used in the workflow process.

The same error message was observed in a detailed JMSReceiver log file even after using either Business Object,  'Action' or 'Project' (defined for the RTE), in the WF process:

procinst.cpp (1021)) SBL-BPR-00130: Runtime event '1-JG1U3' ignored. Event business object 'Project' does not match business object 'Action' associated with process definition '1-PXYDC'.

Solution

Based on customer's confirmation, the IO used in the workflow is setting the context of the BO required in the Runtime event.

The solution is to change the Runtime event to call the actions asynchronously, so the the context of the IO in the workflow does not affect its execution.

After this modification, the issue was solved.

References

NOTE:509859.1 - Problem triggering runtime workflow

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.1 [18306] SVE Pub Sect
Database: Microsoft SQL Server 2000 SP3
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-1770061747.

Symptoms

Hello there.

Following on from SR: 38-1735100856. To recap:

We have a requirement to create an activity plan when a certain type of SR is created. This was achieved via a workflow.
The problem was that an SR can be inserted from either the Contacts or Service Request screen, based on the Contacts and Service Request business objects respectively. As workflows are based on business objects I created two workflows, one for Service Request and one for Contacts (which then calls the Service Request one). I created the Runtime Events and this functions correctly. This was solved in SR: 38-1735100856.

One addition to the screen shots is that the event is triggered on WriteRecordNew as opposed to WriteRecord.

The new problem:

During testing we’ve noticed errors in the log files. It appears that because both are events are triggered from the Service Request Business Component, it’s trying to run both Workflows. Obviously only one will work, the specific one for that Business Object.

The errors in the log file are:
ObjMgrLog    Error    1    0    2005-02-09 14:33:25    (procinst.cpp (930)) SBL-BPR-00130: Runtime event '1-6F9HU' ignored. Event business object 'Contact' does not match business object 'Service Request' associated with process definition '1-6DSU9'.

ObjMgrLog    Error    1    0    2005-02-09 14:45:53    (procinst.cpp (930)) SBL-BPR-00130: Runtime event '1-6F9HT' ignored. Event business object 'Service Request' does not match business object 'Contact' associated with process definition '1-6DSUK'.

We then tried setting the trigger against an applet rather than a business component (as different applets are used), but there’s no WriteRecordNew, just WriteRecord.

So my questions are:

1) If we use business components for the trigger, can we restrict which workflow is fired dependant on the business object?
2) If we use applets for the trigger, can we only fire the workflow on a new record creation?
3) Why is Siebel inconsistent in that workflows are base...

Solution

Message 1

For the benefit of other users, the customer created a workflow process based on the Service Request bus object and a workflow process based in the Contact bus object. The following runtime event was defined in both cases:

Event Object Type, Event, Event Object
BusComp, Service Request, WriteRecordNew

When a SR was added in the view based on the Service Request bus object the following error message was written to the client’s trace file:

procinst.cpp (930)) SBL-BPR-00130: Runtime event '1-6F9HT' ignored. Event business object 'Service Request' does not match business object 'Contact' associated with process definition '1-6DSUK'.

When a SR was added in the view based on the Contact bus object the following error message was written to the client’s trace file:

(procinst.cpp (930)) SBL-BPR-00130: Runtime event '1-6F9HU' ignored. Event business object 'Contact' does not match business object 'Service Request' associated with process definition '1-6DSU9'.

When a new SR was added only the workflow that matched the active view was actually executed. For example, when a SR was added in the view based on the Service Request bus object the workflow based on Service Request was executed but not the workflow based on Contact.

It appears that the error is benign and is provided for information. The customer had set log levels to 1 and did not want errors generated unnecessarily.

[Continued]

Message 2

[Continued]

CR 10494008 has been raised to request that an error is not generated if the event business object does not match the business object associated with a process. Please note that all requests are reviewed and prioritized for possible inclusion in a future release.

- Siebel Technical Support

Keywords: Workflow Process Runtime Event Business Object Component BusComp View Match

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.6 [16186]
Database: Oracle 9.2.0.4
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-1736984191.

Symptoms

SBL-BPR-00130

Hello,
We are trying to create a new workflow using runtime events instead of policies.
The wf process has to modify the column ASGN_DNRM_FLG (chante to "Y") of the service request,
when the user creates an activity with Type = "Enviar técnico" (TODO_CD)

I have created a workflow that I have tested with the simulator, and it seems to work fine.

Then I set the status of the WF to "Active" and go to Reload Personalization in Runtime Events Administration.(may be it's not necessary)

I start the application with dedicated client, and try to test in the custom service request activities view.

I perform the following test create a new activity with status = "Enviar técnico" and the save the record (pressing in other activity record).

When I go to see column ASGN_DNRM_FLG, I check that this column has not been updated.

I have activated runtime trace, and found the folowing lines related with the action performed:

Solution

Message 1

For the benefit of other users:

Customer observed the following error when they try to achieve runtime events.

“ObjMgrLog    Error    4    2005-02-03 17:37:40    (SBL-BPR-00130) Runtime event '1-36P3S' ignored. Event business object 'Service Request' does not match business object 'Action' associated with process definition '1-36P39'.”

In order to fire runtime events, Business Object on Workflow should match the Business Object associated with view running from. For example, if the user performing some action on Action Business Component in Service Request View (Business Object: Service Request), then business object on workflow must be set to Service Request. After changing the Business Object on workflow from Action to Service Request, it works fine.

Thank you,
Nagaraja Gundagathi
Siebel Technical Support

Keywords: Runtime event, SBL-BPR-00130

Applies to:

Siebel Workflow - Version: 7.0.4 [14068] to 8.1.1 [21112]   [Release: V7 to V8]
Information in this document applies to any platform.
Release(s):V7 (Enterprise)
Database(s):All Supported Databases
App Server OS(s):GENERIC (All Platforms)
Latest release tested against:V7 (Enterprise)

Purpose

Siebel Version 7 provides a simplified event mechanism for automating business processes using run-time events. Real-time monitoring of events is based on events that occur at the business object layer minimizing the need for custom scripting and workflow policy invocation. Run-time events can be specified in a Start step to invoke a workflow process or in a Wait step or User Interact step to resume a workflow process.

The following document provides steps on how to troubleshoot such behaviors, by giving an example workflow as illustration.

Last Review Date

February 19, 2009

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

To view the document(s), please click the link(s) below:

Attachment 473851.1:rd2