SBL-DAT-00471: Invalid operation when not executed.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.6 [16186] Fin Svcs
Database: Oracle 9i
Application Server OS: IBM AIX 5L 5.1
Database Server OS: IBM AIX 5L 5.1

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

Symptoms

SBL-UIF-00299, SBL-DAT-00468, SBL-DAT-00471, SBL-UIF-00162

Hi,

Encountered error when changing the primary in the Sales Team view.

[1]Wrong field values or value types detected in field Primary.Please re-enter your field values.If you need to the documentation[SBL-UIF-00299]
[2]Invalid operation when not executed[SBL-DAT-00471]

Steps on how the error been thrown out(Please refer to the screenshot doc):
1.Changed the primary in the Assigned To from "Administrator" to "ARM".Succcesful.
2.Go to the Sales Team tab to create new assignee.Created BIUSF1 and change the primary
from "ARM" to B1USF1."Failed".Thrown out abovementioned error.

What's the caused of that error?For your information,this only happen on the batch loaded records.Meaning all this records loaded via EIM.I already cross reference the value populated and it was exactly like UI created record.All the columns populated accordingly except CRDT_POSTN_ID where for UI created it was auto populated but for batch loaded,it only populated when i changed to the new primary but i already did my testing by manually populated this column,somehow i still got the same error.(Please refer the zip folder).So,i dont think it's the caused of this error.

Another testing have been done by changing the primary on the Assigned To field in the sales team view.Same steps have been applied and there's no error.What's teh different with this view then?

Please advice.

Zuraida.

Solution

Message 1

For the benefit of other readers:

The customer had added a business component User Property :'MVG Set Primary Restricted: Position'.

The customer received the following error attempting to change the Primary Position in the Opportunity's Sales Team tab having previously changed it in the Opportunity List Applet:

[1]Wrong field values or value types detected in field Primary.Please re-enter your field values.If you need to the documentation[SBL-UIF-00299]
[2]Invalid operation when not executed[SBL-DAT-00471]

This was initially reported with records imported using EIM and only occurred when changing the Primary first in the List Applet, then in the Sales Team Tab.

This behavior was NOT Change Request 12-GS8XVF (see: Service Request #: 38-1013808209, Abstract: Error Changing Primary Position on Sales Team for Copied Opportunity Records)

Technical Support was able to re-produce the customer's reported behavior using a standard srf with Opportunities created via the UI (hence eliminating EIM as a factor).
The reproducible case was very specific requiring the creation of two Opportunities as follows:
1. Create Opty 1 (supply only Name)
2. Create Opty 2 (supply Name only)
3. Select Opty 1 - add a Position in List Applet and make it Primary
4. Navigate to the Sales Team Tab - add Position and make it Primary.
5. Error occurs

The behavior did not occur if only one Opportunity was created.

Message 2

I have raised Change Request 12-VDOTDZ as a Product Defect, summarized as "[SBL-UIF-00299] and [SBL-DAT-00471] errors when changing Primary Position of Opportunity."

The workaround is to only change the Primary Position in the List Applet.

Best Regards

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 7.5.3

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00471: Invalid operation when not executed.

Scope

This document is informational and intended for any user.

SBL-DAT-00471: Invalid operation when not executed.

Explanation

This error may occur when:

1. Creating records, the execution might be interrupted by another operation at the business object layer. Possible causes are customizations (copy, modification or deactivation) of the underlying business component. A common example is the Recipients business component used by the correspondence functionality (Generate button).

2. A workflow process called from a script or business service that in turn calls a server component, for example Outbound Communications Manager.

3. A user performs erratic actions in the application, for example, clicking multiple times on a Calendar Activity hyperlink or the New button.

Corrective Action

1. Test the creation of a record against a standard object (not modified). If the error does not occur against a standard object, check the business component configuration.

2. Use a workflow policy as opposed to workflow process or call the workflow process from one of the following:

- Workflow Process Manager (Server Request) business service

- MQSeries Receiver component

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

3. Allow the screen view to refresh before performing the next user action.

Change Request 12-HUW7GT has been logged to address a product defect related to the Calendar Activity hyperlink and has been fixed in Maintenance Release 7.5.3.4 and 7.7.1.

Change Request 12-HMCCUD has been logged to address a product defect related to the New button in the Calendar applets and has been fixed in Siebel version 7.7.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.8.2.4 [19224]
Database: Oracle 10.2.0.2
Application Server OS: Sun Solaris 10
Database Server OS: Sun Solaris 10

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

Symptoms

Upon invoking a SmartScript, we are getting the error "Invalid operation not executed (SBL-DAT-00471).

We tested if this was class related by changing the "Order Entry - Line Items" class from "CSSBCOrderMgmtOrderItem" to "CSSBCLineItem" but it did not help.

If we remove the BC value from the question then we do not get the error but we need BC to pop the Pick Applet "Product Pick Applet - No Insert"

I looked into the Support web with the error "SBL-DAT-00471" didn't find anything related to the SS or "Order Entry" but it did not provide an answer.

Please let us know what we can do to avoid this error, but maintain the data we need in the SmartScripts.

Solution

Message 1

For the benefit of other users:

Issue:
IE browser was crashing when a Pick List Applet was invoked during the SmartScripts execution from SmartScripts player applet.

Steps to reproduce:
1. Execute script from SmartScripts player view
2. Open pick list applet in the first question (question was based on the Product field, configured with “Order Entry - Line Items” BusComp and “Order Entry - Line Item Product Pick Applet”).
3. Select any record in the pick list applet and click on OK button.
Actual result: IE browser will crash.

Resolution:
Root cause of this issue was in the SmartScripts configuration.
Order Entry - Line Items BusComp and Pick Applet configured in the SmartScripts Questions view were causing the crash.

To address this issue, we have logged new Change Request 12-1JFSGO9.

Workaround:
As a workaround, customer was suggested to make the following configuration changes.

The main idea of the workaround is to change SmartScript question field:
1) To use pick applet of "Product Pick Applet" instead of “Order Entry - Line Item Product Pick Applet”
2) To use "Order Entry - Line Items (Simple)" BusComp instead of "Order Entry - Line Items"

cont..

Message 2

Configuration steps:

1) Log into Siebel Tools.
2) Select Business Components in the Object Explorer.
3) Query for "Order Entry - Line Items (Simple)" and "Order Entry - Line Item" records.
5) Select both records. (Before making any changes make a backup copy of Order Entry - Line Items (Simple))
6) Right mouse click > Compare Objects > Selected
7) Compare 2 selected objects and add field "Product" in the Order Entry - Line Items (Simple).
8) Right click and run validation on "Order Entry - Line Items (Simple)"
9) Disable invalid Pick Maps of Product field on the above validation
10). Compile SRF and run script.

Thank you,
Oracle Support

Keywords: “Order Entry - Line Items and SmartScripts”, “SBL-DAT-00471”

Applies to:

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

Symptoms

Siebel Version: 8.1.1 SIA

Statement Of Issue: When trying to drilldown from Calendar Activity on Home page facing error. The same is working fine if the destination view has already been navigated to.

Error Thrown: SBL-DAT-00471: Invalid operation when not executed.

Steps to Reproduce:
1. Login to Application.
2. On the Home pagescreen > My Calendar drilldown on an activity.
3. Error is thrown.

Cause

The error is reproduced in standard environment also when drilldown from Calendar on Home Page view.

Bug 12-1ZD6245 (Error SBL-DAT-00471 thrown when drilldown from Calendar on Home page.) has been raised to report the issue.

Solution

Fix Request for version 8.1.1.2 has been raised and has not fixed yet.

References

BUG:12-1ZD6245 - ERROR SBL-DAT-00471 THROWN WHEN DRILLDOWN FROM CALENDAR ON HOME PAGE AFTER APPLYING QF0244.

Applies to:

Siebel Data Quality - Version: 7.7.2.7 [18376] to 8.1.1.2[21215] - Release: V7 to V8
Information in this document applies to any platform.

Symptoms

=== ODM Issue Clarification ===

On : 8.0.0.5 [20420] version, Client Functionality

When attempting to merge two accounts together (that were identified as duplicates via Data Quality) in the Administration - Data Quality > Duplicate Accounts > Duplicate Account Resolution view the following error occurs.

ERROR
-----------------------
Invalid operation when not executed.(SBL-DAT-00471). Additionally, the following is seen in the log file:
SBL-DBC-00105: An error has occurred executing a Sql statement
[Microsoft][SQL Native Client][SQL Server]Internal Query Processor Error: The query processor could not produce a query plan.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Load or create new accounts in Siebel
2. Run a batch deduplication job via Administration - Server Management > Jobs
3. View the duplicate accounts via Administration - Data Quality > Duplicate Accounts
4. Drilldown onto the appropriate account
5. Enter sequenced numbers as appropriate and click the Merge button

Cause

=== ODM Cause Determination ===

The issue is caused due to a SQL Server 2005 Service Pack 2 bug. The bug affects queries that return many columns and join many tables. The Microsoft explanation of this bug is:

"This issue occurs because the query runs under the execution context of the sp_cursoropen stored procedure. The SQL Server 2005 Database Engine generates an exception when SQL Server 2005 tries to create an execution plan."

=== ODM Cause Justification ===

The following justifies how the issue is related to this specific customer:

EVIDENCE OF CAUSE
---------------
The customer confirmed the following:
The log file for the thick client contains the following errors:
SBL-DBC-00105: An error has occurred executing a Sql statement
[Microsoft][SQL Native Client][SQL Server]Internal Query Processor Error: The query processor could not produce a query plan.

SUPPORT OF CONCLUSION
---------------
Examining the SQL Select statement causing the problem, there are many columns and joins to tables.

REFERENCES
---------------
FIX: Error message when you run a query that selects many columns and that joins many tables in SQL Server 2005 Service Pack 2: "The query processor could not produce a query plan"
http://support.microsoft.com/kb/940371/

Solution

=== ODM Solution /Action Plan ===

To implement the solution, please execute the following steps:

1. Download one of the following three patches (this depends on the customer's requirements and language availability):
- Microsoft SQL Server 2005 Service Pack 3
OR
- Microsoft SQL Server 2005 Service Pack 2 Cumulative Update 17 (latest Cumulative Update for Service Pack 2)
OR
- Microsoft SQL Server 2005 Service Pack 2 Cumulative Update 3

The Microsoft recommendation would be to apply the latest patch, namely SQL Server 2005 Service Pack 3, which is available here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=ae7387c3-348c-4faa-8ae5-949fdfbe59c4

Alternatively, the following articles provide instructions to download the Cumulative Updates:
Microsoft SQL Server 2005 Service Pack 2 Cumulative Update 17
(http://support.microsoft.com/kb/976952/)
OR
Microsoft SQL Server 2005 Service Pack 2 Cumulative Update 3
(http://support.microsoft.com/kb/939537)

2. Backup the database prior to applying the patch.

3. Apply the patch

4. Ensure that the patch has been installed successfully.

5. Retest the behaviour of merging duplicate accounts with custom SRF.

REFERENCES
---------------
List of the bugs that are fixed in SQL Server 2005 Service Pack 3 - http://support.microsoft.com/kb/955706/

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.13 [16275] PTG Com/Med
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Sun Solaris 5.8

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

Symptoms

SBL-DAT-00471

Hello

We are finding an Error in Smartscripts when performing tests in v 7.5.3.13. They work fine in v 7.5.3.3.

Sometimes when we press the button "Cancelar" (Cancel) it opens the Cancel SS, and then it goes to a view with the button "Retomar" (Return) but instead of going back to the Main Script it gives the following error.

Operação inválida quando não executada.(SBL-DAT-00471)


Is this a know issue in v 7.5.3.13 ?

Solution

Message 1

Resolution:

For the benefit of other readers:

I have logged Change Request 12-1B20OTT for Product Defect.

A patch is in process of delivery.

Thanks & regards,