Search This Blog

SBL-DAT-00470: This operation is not supported for business component '%1' because it is not the root of this cached update mode tree.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Oracle 9.2
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Sun Solaris 9

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

Symptoms

SBL-DAT-00470, SBL-DBC-00108

No users are not able to load a Campaign based on a List over 1,000 or more records regardless from whether the list was imported or internal. Campaigns based on Segments are not affected.
When a wave is loaded, the status changes to "Load Complete" however the number of contacts for a wave shows a 0. No Campaign Members are associated with the referenced Wave.
The ability to load a Campaign from an Internal List is one of major business requirements that our users have requested for this project.
This is our initial Rollout of the Campaign Functionality. We are supposed to launch the first campaign on Monday 11/7. This project has very high visibility by the management team at Oppenheimer and any issues of this extend may turn the project sucess into a failuire. We will attach several log files with increased logging level referring to Workflow Processes that failed.

Solution

Message 1

While loading Campaign with “Audit Trail Engine” enabled, may cause the following error in the Workflow Process Component log:
- This operation is not supported for business component 'Audit Trail Item 2' because it is not the root of this cached update mode tree (SBL-DAT-00470).

This error happens when loading Campaigns with lists - imported or internal -containing large volume of records (usually more then 1,000).

As consequence:
- Workflow process finishes with error and sometimes partially loading the records.
- Wave# is not populated in the Campaign list of Prospects/Contacts, so that wave cannot be purged.

Please note that Change Request Number 12-1936GPA was already logged to address this issue on future releases.

Best regards,

Siebel Technical Support


No comments:

Post a Comment