Search This Blog

SBL-DAT-00517: Invalid operation when not in update mode. Please continue or ask your systems administrator to check your application configuration.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: IBM AIX 5L 5.1

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

Symptoms

SBL-DAT-00100, SBL-DAT-00517

Hi,

This is a follow up from SR 38-1737068061, using SR 38-1033111991.

As suggested, we tried to script the creation of a single activity for a correspondence, with all the recipients as contacts. The script is working well when there is only one contact to attach, it doesn't, however, attach several contacts to the activity. In this case the following error message is displayed:
----
Invalid operation when not in update mode.

Please continue or ask your systems administrator to check your application configuration if the problem persists.( SBL-DAT-00517)
----

Our script is basic, but we don't find any errors in it. Can you help up with the error message? Why it doesn't work with multiple recipients?

We are attaching the script on "WriteRecord" for BC Correspondence.

Regards

Solution

Message 1

For the benefit of other readers:

Issue:
====
This is a follow up from SR 38-1737068061, using SR 38-1033111991.

As suggested, we tried to script the creation of a single activity for a correspondence, with all the recipients as contacts. The script is working well when there is only one contact to attach, it doesn't, however, attach several contacts to the activity. In this case the following error message is displayed:
----
Invalid operation when not in update mode.

Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00517)
----

Our script is basic, but we don't find any errors in it. Can you help up with the error message? Why it doesn't work with multiple recipients?

Resolution:
====
This behavior occurred when the contacts involved had associated accounts. It was also reproduced when creating new activity records manually via the UI (e.g. in "My Activities" view). Indeed when a user tried to associate in one time 2 contacts via the "Add >" button in the Contacts shuttle applet an error like the following occurred:
----
[1] The 'Association' operation failed for the record with user key and value = 'PersonUId:2P-QKBT'.(SBL-DAT-00100)
[2] Invalid operation when not in update mode.

Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00517)
----

[...]

Message 2

[...]

This behavior was due to inappropriate custom pick maps defined for field 'Account Name' in BC 'Action':

Field: Contact First Name
Pick List Field:

Field: Contact Id
Pick List Field:

Field: Contact Last Name
Pick List Field:

The field 'Contact First Name', 'Contact Id' and 'Contact Last Name' are standard MVF, based on the 'Contact' MVL. In standard 'Action' BC the 'No Update' property of this MVL but in the customer environment it was set to FALSE.

The issue was resolved once the 3 custom pick maps were removed.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.2.3 [18361]
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-3098872691.

Symptoms

SBL-UIF-00269, SBL-DAT-00144, SBL-DAT-00517

YOu can now copy a quote line item but, if you reprice and try to revise it give you an error that it cannot update (see attachment).   If you change the products or change a product and save it. Then put it back you can reprice and revise the quote. Some kind of issue with the way the products are stored. This is in 7.7.2.6 and we are set to roll this out in 2 weeks.

Solution

Message 1

For the benefict of the other readers:

Behavior: Revise Quotes Error 'SBL-DAT-00517: Invalid operation when not in update mode' for custom products.

How to reproduce:

. Site Map -> Administrator Pricing -> Price Lists -> Master Price List -> Add the PCS 500S (customizable product) to this price list and define a price for this product.
. Quotes screen -> Quotes List -> create a new quote-> Associate this quote to 'Master Price List'.
. On Quote Line Item -> Add the Prod. 'PCS 500S'.
. Copy the PCS 500S line item and Reprice.
. Try to Revise the Quote.

You'll receive the error: SBL-DAT-00517: Invalid operation when not in update mode.

Noticed differences:

Using Local DB, the statement error happens during a insert on S_DOC_TXN_LOG.
Using Sample DB, the statement error happens during a insert on S_QUOTE_ITEM.

However, either on Local or Sample DB, this issue happens only for Customizable products.

Fix: The Change Request (12-1FGG6Z0) has been logged to address this behavior. Fixed by FR 12-1FGG72D.


Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.3 [16172] Cons Sec
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Server SP 2
Database Server OS: Microsoft Windows 2000 Advanced Server SP 2

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

Symptoms

SBL-DAT-00474, SBL-DAT-00517

Hello. Users are experiencing an error when making multiple updates to the lowest level baseline applet (CG SVP Category Baseline List Applet) in the SVP Hierarchy on the view CG SVP Account Baseline Hierarchical View. When the user makes an update to the CY Incremental Rev field and steps off the record, the field accepts the change. When the user steps back on that record, and makes a new change to the field, an error message appears that states: Invalid operation when not in update mode.

Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00517)

After closing the messagebox, the user then tries to hit the Refresh button, which brings up a different error (see screenshot). After closing this messagebox, the user can then click the Refresh button to make changes to the field.

There was no supporting information on support web for this. How do we resolve these errors? Screen shots are attached.

Thanks,
Kim

Solution

Message 1

For the benefit of other users, the customer reported that ‘No update mode error’ was generated when changing the Incremental Qty field multiple times under Sales Volume Planning view.

Resolution:

The reported behavior is reproducible against the standard Siebel Consumer Goods application with the following steps:

1. Go to SVP screen
2. Select an account from the account hierarchy
3. Go to the product level of the category/product hierarchy
4. Change the Incremental Qty for one period
5. Step off the record
6. Go back to the same period and change the Incremental Qty
7. Step off the record
8. Go back to the same period and change the Incremental Qty
9. The Not Update Mode error is generated

Change Request 12-QSXCJS has been logged to address the above product defect.

Thank you,

Siebel Technical Support

Applies to:

Siebel Tools - Version: 8.0.0.6 SIA [20423] - Release: V8
Information in this document applies to any platform.

Symptoms

When trying to copy a price list record which has price list items, the following error
is displayed
---
Invalid operation when not in update mode.

Please continue or ask your systems administrator to check your application configuration if the problem persists.( SBL-DAT-00517)
----

Cause

If following two conditions are met, the error occurs when the parent record is copied.

1. The business component has 'CSSBCPriceListItem' in Class property
2. A user property 'On Field Update Set N' is set to a field with No Copy = TRUE

As described in Bookshelf 'Configuring Siebel Business Applications' at
[Overview of Configuring Siebel Applications]->[About Object Reuse],
configuring specialized business components could cause unexpected behavior.

Solution

The issue can be workarounded by using eScript instead of using the user property.
For example, following sample code can be written in Price List Item business component
to avoid the error.

function BusComp_SetFieldValue (FieldName)
{
  if (FieldName == "field1") {
    this.SetFieldValue("field2", this.GetFieldValue("field1");
  }
}



No comments:

Post a Comment