siebel-error: January 2011

Monday, January 31, 2011

SBL-DAT-00493: Text constant (%1) needs to be enclosed in single quotes.

Applies to:

Siebel Tools
IBM AIX on POWER Systems (64-bit)

Product Release: V8 (Enterprise)

Version: 8.0 [20405] FRA

Database: IBM DB2 8.1 FixPack 8

Application Server OS: IBM AIX 5L 5.2

Database Server OS: IBM AIX 5L 5.2

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

Symptoms

SBL-DAT-00493

Hi Support

We are currently trying to migrate our Siebel V7.5 Repository to
V8.0.

We had a customized BC with 2 Calculated Field.
Field A
- Calculated
Value=Number
- Type:DTYPE_TEXT
Field B
- Calculated Value=IIf([Field
A]>0,'OK','KO')
- Type:DTYPE_TEXT

In V7.5, there was no problem with this
configuration.

After V8.0 migration, we have a runtime error:
ObjMgrQueryLog Warning 2
0000000246640f64:0 2007-06-04 17:28:07 (query.cpp (984)) SBL-DAT-00493: La constante de texte (0)
doit �tre inscrite entre guillemets simples.
Veuillez continuer ou demander � l'administrateur
syst�me de v�rifier la configuration de l'application si le probl�me persiste.
ObjMgrLog
Warning 2 0000000246640f64:0 2007-06-04 17:28:07 (query.cpp (2600)) SBL-DAT-00501: Sp�cification
de recherche 'IIf([Test Calculated Value1]>0,'Y','N')' non valide.
Veuillez continuer ou
demander � l'administrateur syst�me de v�rifier la configuration de l'application si le probl�me
persiste.

I reproduced the problem in Vanilla V8.0 ( see the attached file Account.sif;
fields "Test Calculated*")

So it seems the field A has a Text type in V8.0 whereas it had
an Number type in V7.5.

I didn't find any documentation in bookshelf V7.5 that recommend
setting a specific type for calculated fields (The type was dynamically deduced).

In V8.0,
since Revision A (April 2007), in the bookshelf "Siebel Developer's Reference > Operators,
Expressions, and Conditions >Calculated Field Rules",
there has been this sentence:
"For
a calculated field whose calculated value is not of type DTYPE_TEXT, the field type must be
specified explicitly."

Is it a standard behaviour in V8.0?
If yes, is there any
documentation about how we can migrate all our existing calculated Fields?( we didn't find
anything in the Database Upgrade Guide)

Thanks in advance.

Solution

Message 1

For the benefit of other readers:

V8 has changed the way the calculated fields interact with other parts of the application.

Bookshelf states:

"Siebel Developer's Reference > Operators, Expressions, and Conditions >Calculated Field Rules",

"For a calculated field whose calculated value is not of type DTYPE_TEXT, the field type must be specified explicitly."

This caused the customer an issue as when upgrading the calculated fields gave a search error.

There were two ways in which this issue could be resolved.

1) After upgrading, navigate through the application and look for the error in the logs. This will then give the BC upon which the error occurs.

2) CR#12-1JPYP1L and CR#12-1JVI3Q3 have been raised for this issue; one to see if this can be added to the upgrade process and the other to see if the functionality of v7.x can be regressed for v8.

CR#12-1JVI3Q3 has been fixed in 8.0.0.3 Fix Pack.

Thank you,

Oracle | Siebel Technical Support

Applies to:

Product Release: V7 (Enterprise)

Version: 7.5.3.1 [16161]

Database: Oracle 9.2.0.2

Application Server OS: Microsoft Windows 2000 Advanced Server SP 3

Database Server OS: Sun Solaris 2.7

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

Symptoms

SBL-DAT-00493

Dear Support Team,

We have migrated from 7.5.2 to 7.5.3.1, in the forecast area before
migration, subordinates were able to submit their forecasts, but after migration they can't
submit their forecasts. When they try to submit their forecasts, the application crashes.
Attached you can find siebel log file in which SIEBEL_LOG_EVENTS was set to 4. I logged in as a
subordinate and then navigate to forecasts screen and then tried to change status field from
"Active" to "Submitted". In the log file this change starts from line 22025.
This thursday we
will go for production test, for that reason could you please advice us ASAP.

Solution

Message 1

For the benefit of other users:

Customer found that they were unable to submit forecasts and it crashed the Client application.

Turning on Client-side logging had the error ""ObjMgrLog Error 4 2003-10-21 16:14:02 (SBL-DAT-00493) Text constant (Y) needs to be enclosed in single quotes. Please continue or ask your systems administrator to check your application configuration if the problem persists." followed by a call stack.

This behavior was not reproducible with the Standard SRF and only with the custom SRF. The log indicated that the error occurred after an insertion into S_ACCNT_ATT table. Customer had a custom Business Component called "Forecast Attachment" and it was based on S_ACCNT_ATT table. In forecast submission Customer was generating forecast data (based on opportunities and products) into an excel file.

One of the custom user properties on Forecast 2000 -- Forecast Business Component, had a text constant (Y) without quotation marks. Customer fixed this User Property and they were able to successfully submit forecasts.

Applies to:

Product Release: V7 (Enterprise)

Version: 7.5.3.11 [16199] SVE Fin Svcs

Database: Microsoft SQL Server 2000 SP4

Application Server OS: Microsoft Windows 2000 Advanced Server SP 3

Database Server OS: Microsoft Windows 2000 Advanced Server SP 4

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

Symptoms

SBL-EXL-00145, SBL-DBC-00105, SBL-DAT-00398, SBL-DAT-00403, SBL-DAT-00493, SBL-DAT-00501

Hi

We have an X_ column that is defined to contain a MLOV field. That field is used as a
MVF and when a search spec is created on that field an sql error occurs.

Looking at the
sql it seems like the LANG_ID parameter is missing as input (there are three bind variables but
four parameters are needed for the query, the first beeing LANG_ID)

It is Bind variable 2
(Låna) below that is the MLOV field.

If we query on another field using the sam MVL it
works fine, also the sql works fine if all parameters are supplied

Any
suggestions?

Regards
Jonas

SELECT
      T1.CONFLICT_ID,
      CONVERT
(VARCHAR (10),T1.LAST_UPD, 101) + ' ' + CONVERT (VARCHAR (10),T1.LAST_UPD,
8),
      CONVERT (VARCHAR (10),T1.CREATED, 101) + ' ' + CONVERT
(VARCHAR (10),T1.CREATED,
8),
      T1.LAST_UPD_BY,
      T1.CREATED_BY,
      T1.MODIFICATION_NUM,
      T1.ROW_ID,
      T1.ACCNT_ID,
      T1.COMMENTS,
      T1.COMMIT_FLG,
      T1.CONTACT_ID,
      T1.COST_AMT,
      T1.REVN_AMT_CURCY_CD,
      CONVERT
(VARCHAR (10),T1.EFFECTIVE_DT, 101) + ' ' + CONVERT (VARCHAR (10),T1.EFFECTIVE_DT,
8),
      T1.PROD_DESC_TEXT,
      T1.DOWNSIDE_AMT,
      T1.MARGIN_AMT,
      T4.NAME,
      T1.X_EXTERNAL_USER,
      T1.X_ASSET_NUM,
      T10.ATTRIB_03,
      CONVERT
(VARCHAR (10),T1.EXPECT_DLVRY_DT, 101) + ' ' + CONVERT (VARCHAR (10),T1.EXPECT_DLVRY_DT,
8),
      T1.X_QUOTE_NUM,
      T11.LOGIN,
      T3.REF_NUMBER_2,
      T3.DETAIL_TYPE_CD,
      CONVERT
(VARCHAR (10),T1.X_ACCEPT_DT, 101) + ' ' + CONVERT (VARCHAR (10),T1.X_ACCEPT_DT,
8),
      T4.NAME,
      T1.OPTY_ID,
      T6.ROW_ID,
      T5.NAME,
      T3.PART_NUM,
      T1.NET_PRICE,
      T4.SUM_REVN_ITEM_ID,
      T3.NAME,
      T1.PROD_ID,
      T7.NAME,
      T1.PROD_LN_ID,
      T1.QTY,
      T1.REVN_AMT,
      T1.CLASS_CD,
      T1.REVN_ITEM_NUM,
      T1.TYPE_CD,
      T9.LOGIN,
      T8.NAME,

...

Solution

Message 1

...

   WHERE

      ((T1.SUMMARY_FLG = 'N') AND

      (T1.TMPL_ID IS NULL)) AND

      (T1.PROD_ID IN (

            SELECT SQ1_T2.PROD_ID

               FROM dbo.S_PROD_LN SQ1_T1 INNER JOIN dbo.S_PROD_LN_PROD SQ1_T2 ON SQ1_T2.PROD_LN_ID = SQ1_T1.ROW_ID INNER JOIN dbo.S_PROD_LN SQ1_T3 ON SQ1_T1.PAR_PROD_LN_ID = SQ1_T3.ROW_ID INNER JOIN dbo.S_LST_OF_VAL SQ1_T4 ON SQ1_T3.X_AREA_CATEGORY = SQ1_T4.NAME AND SQ1_T4.TYPE = 'LF_RM_AREA_CATEGORY' AND SQ1_T4.LANG_ID = ?

               WHERE

                  (SQ1_T1.X_QUOTE_FLG = ? OR SQ1_T1.X_QUOTE_FLG IS NULL) AND

                  (SQ1_T1.X_TYPE IS NULL OR SQ1_T1.X_TYPE = 'ProductGroup') AND

                  (SQ1_T4.VAL = ?))) AND

      (T1.OPTY_ID = ?)

   ORDER BY

      T1.OPTY_ID DESC, T1.CREATED DESC

(note 4 question marks for bind variables above, but just 3 bind variables below:)

Bind variable 1: N

Bind variable 2: Låna

Bind variable 3: 1-48EJ2

Message 2

For the benefit of other readers:

When querying on an MLOV enabled field in the customer's database with for example

EXISTS([LF Area Category] = Skydda)

this produces an SQL statement that has one bind variable missing,

resulting in the error message

"Not enough values for host variables"

This is reproducible in

7.5.3.11 [16199] SVE SIA (Fin Svcs)

Change Request

12-U4DBNJ

"Less bind variables available than requested by the SQL spool. This is related to MLOV config."

had been logged for this behavior

and this is fixed in

7.5.3.12 Fix Pack [16272]

(Fix request 12-UXRMM1)

After installing the 7.5.3.12 [16272] Maintenance Release,

the query completed successfully.

Regards,

Applies to:

Product Release: V7 (Enterprise)

Version: 7.5.2.7 [15058] Com/Med

Database: Oracle 9i

Application Server OS: Microsoft Windows 2000 Advanced Server SP 2

Database Server OS: Sun Solaris 8

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

Symptoms

SBL-DAT-00493

If we define a Detail BC as a Business Component which use MVL to call other calculated
fielda from a Main BC. (e.g. Account BC and Contact BC use MVL to call Field "A" which is a
calculated field from CUT Address BC)

The scenario is shown as follows

Detail BCs
cannot call any calculated field (e.g. Field "A") from a Main BC which contain a calcuated
formula as IIf([English Flag] = 'Y',1,0)

This leads to the error message, "Text constant
(Y) needs to be enclosed in single quotes", when the Siebel application is turned
on.

However, if Detail BCs are not use MVL to call Field "A", using the same formula in
Field "A" will not cause an error message

Solution

Message 1

For the benefit of other users,

The correct syntax is to place a "" (double quotes) around 'Y' (Y in single quotes) in the calculated formula, that is, IIF([English Flag] = "'Y'","1", "2").

As there are no documentation or information on the usage of the syntax of calculated value when used as a MVF, change request 12-DTTBTX has been logged to address this issue.

SBL-DAT-00496: Can not update Parent because this will introduce recursive reporting relationship or such relationship already exists for the given Pa

Applies to:

Product Release: V7 (Enterprise)

Version: 7.5.3.3 [16172] FIN Fin Svcs

Database: Microsoft SQL Server 2000 SP3

Application Server OS: Microsoft Windows 2000 Advanced Server SP 4

Database Server OS: Microsoft Windows 2000 Advanced Server SP 4

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

Symptoms

SBL-DAT-00496

Hi,

I'm trying to create a Siebel login / position for a new employee. The steps I follow
for creating this new employee are

1. User Administration -> Employees -> Select an
existing employee with a similar profile -> Ctrl + B to copy record.

2. Change Last
name, First name, UserID to correspond to the new user, step off the record to save it

3.
Go to Group Administration -> Positions -> Create a new position and make the new user the
primary employee on the position

4. Delete the new employee from the old position (that
got copied over when the employee was created).

5. Assign a parent position to the new
position created.

This step errors out with "Can not update Parent because this will
introduce recursive reporting relationship or such relationship already exists for the given
parent". A screen capture of the error message is attached.

Please let me know how this
problem can be resolved.

Thanks

Kumaresh Subramanian

Solution

Message 1

For the benefit of other readers:

Description

When we navigate to Group Administration >Positions and try to assign one of these positions, Seasons East, Seasons West, or Seasons Team, as the parent position to any other position, we receive the following message:

"Can not update Parent because this will introduce recursive reporting relationship or such relationship already exists for the given parent. (SBL-DAT-00496)"

When we try to assign Polaris East or Polaris West as a parent position though, it is successful.

Why does this happen?

Resolution

To reproduce in the customer's environment, navigate to Group Administration > Positions and query for last name = Luttman. Try to assign the parent position "Seasons East" to the record. From the applet menu choose "Save Record" and the error message above about recursive relationships is reproduced.

Now assign the parent position "Polaris East", save the record, and it is successful.

The difference between the records "Seasons East" and "Polaris East" in the S_POSTN table were the following:

A. Different organizations

B. Different ou_id

C. Different Parent Position Id

D. Different Primary Employee Id

E. Different Primary Position Id

1. Updating the Primary employee of Seasons East to the primary employee to Polaris East did not resolve the behavior.

(continued...)

Message 2

(continued...)

2. Updating the parent position of Seasons East to Polaris National (the parent of Polaris East) resolved the behavior so the hierarchy of the "Seasons" positions was identified as the cause.

The "Seasons Division" position was at the topmost position in this hierarchy. This position was the parent of the following positions (shown in the tree applet on the left of the view):

Seasons Division

Seasons Divisional Assistant

Seasons Team

Clicking on the "+" of the child Seasons Division made it show over and over and over again as a child to itself. This was the recursive relationship indicated in the error message.

Comparing the topmost position in the Seasons hierarchy, Seasons Division, to the topmost position in the Polaris hierarchy, Polaris Division, showed that the Polaris Division does not have a parent position defined but Seasons Division had itself defined as the parent.

Removing "Seasons Division" as the parent to itself resolved the behavior.

Applies to:

Siebel Finance Service - Version: 8.0.0.1 SIA [20408] - Release: V8

Information in this document applies to any platform.

Symptoms

Customer is having the following issue when they are trying to update the parent position

In the view "SiteMap -> Administration - Group -> Positions" when you try to update the parent position with different postion , it gives the following error

"Can not update Parent because this will introduce introduce recursive reporting relationship or such relationship already exists for given Parent SBL - DAT 00496"

Cause

"12-1LW16M5 - Changing position errors out" This CR has already been raised to find out the cause of this behavior.

In the CR # 12-1LW16M5, "Comments Summary " section it is mentioned that,

For A Hierarchy of the following pattern.

OLD
|
MGR
___|___
| |
A B

The following relations are created in the Table S_PARTY_RPT_REL for "OLD"

OLD - OLD (self)
OLD - MGR (direct)
OLD - A (in-direct)
OLD - B (in-direct)

When OLD is replaced with "NEW" for the first time the relationship status is as follows-

NEW-NEW (self)
NEW-MGR (direct)
NEW-A (indirect)
NEW-B (indirect)
OLD-OLD (self)
OLD-A (in-direct)
OLD-B (in-direct)

The indirect relationships corresponding to "OLD" should also be deleted from the DataBase as it is not happening , when we replace "NEW" with "OLD" again there is a conflict in the table.

On further research, the statement which deletes the records from "S_PARTY_RPT_REL" table is picking up the ROW_ID from S_DOCK_TXN_SET table -

DELETE FROM dbo.S_PARTY_RPT_REL WHERE ROW_ID IN (SELECT TARGET_ROW_ID
FROM dbo.S_DOCK_TXN_SET
WHERE
TXN_LOG_ID = ?)

On examining the table "S_DOCK_TXN_SET" . It is found that, it gets populated properly for the direct relationship whereas its not getting populated properly for the Indirect relationships. So, there could be some issue with the search spec.

Solution

After doing more research on this issue, we found that this is a known issue for 8.0 versions.

CR # 12-1LW16M5 has already been logged to address this issue.

This issue is fixed in the following version of 8.0 also.

FR # 12-1N2KYHJ -> 8.0.0.1 [20408]QF0140 BugID: SIA: 6795730

FR # 12-1OYXLP3 -> 8.0.0.2 [20412]QF0266 BugID: SBA: 7310611

FR # 12-1P4OEMC ->8.0.0.3 [20416]QF0314 BugID: SBA: 7247710

FR # 12-1N22RZ9 -> 8.0.0.5 Fix Pack

References

BUG:12-1LW16M5 - CHANGING POSITION ERRORS OUT

Applies to:

Siebel CRM - Version: 8.0 [20405] - Release: V8
Siebel Call Center - Version: 8.0.0.3 [20416] to 8.0.0.4 [20417] - Release: V8 to V8

Information in this document applies to any platform.

Symptoms

The issue occurs with Siebel version 8.0.0.3 or 8.0.0.4.
In Siebel standard application using the web-dedicated client connected to the server database when trying to change the parent organization of an organization that has children the following error messages appear:
[1] An error has occurred writing to a record. Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00111)
[2][Microsoft][SQL Native Client][SQL Server]Cannot insert duplicate key row in object 'dbo.S_PARTY_RPT_REL' with unique index 'S_PARTY_RPT_REL_U1'.
[3][Microsoft][SQL Native Client][SQL Server)The statement has been terminated.
[4][Microsoft][SQL Native Client][SQL Server]Cannot insert duplicate key row in object 'dbo.S_PARTY_RPT_REL' with unique index 'S_PARTY_RPT_REL_U1'.
[5][Microsoft][SQL Native Client][SQL Server)The statement has been terminated.

NOTE: If you try to reproduce the issue in Siebel standard application using the web-dedicated client and Sample database you will receive the error:
"Can not update Parent because this will introduce recursive reporting relationship or such relationship already exists for the given parent (SBL-DAT-00496)"

Cause

The mentioned behavior is caused by a product defect.

Oracle/Siebel Technical Support was able to reproduce the customer's issue with Siebel version 8.0.0.4 SIA and web-dedicated client connected to the server database (MS-SQL version 9.0).

Steps to reproduce with Siebel version 8.0.0.4 SIA and web-dedicated client connected to the server database (MS-SQL version 9.0 (2005)):
1.- Navigate to "Administration - Group" > "Organizations"
2.- Create the following organizations structure:
1 Organization without "parent organization" ("Org_A")
2 Organizations ("Org_B" and "Org_C") whose parent organization is the seeded "Default Organization" (Org_B and Org_C are "brothers")
1 Organization ("Org_D") whose parent organization is "Org_C" ("Org_D" is grandson of Default_Organization)
2 Organizations ("Org_E" and "Org_F") whose parent organization is "Org_D"
Graphically:
_Org_A
_Default Organization
____|_Org_B
____|_Org_C
________|_Org_D
____________|_Org_E
____________|_Org_F

3.- Click on "Org_D" and, in the right-down applet try to change his parent Organization from "Org_C" to "Org_B".
Click Ctrl+S to save the record. =-> The following error messages appear in a pop-up window:
[1] An error has occurred writing to a record. Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00111)
[2][Microsoft][SQL Native Client][SQL Server]Cannot insert duplicate key row in object 'dbo.S_PARTY_RPT_REL' with unique index 'S_PARTY_RPT_REL_U1'.
[3][Microsoft][SQL Native Client][SQL Server)The statement has been terminated.
[4][Microsoft][SQL Native Client][SQL Server]Cannot insert duplicate key row in object 'dbo.S_PARTY_RPT_REL' with unique index 'S_PARTY_RPT_REL_U1'.
[5][Microsoft][SQL Native Client][SQL Server)The statement has been terminated.

(Notice that Org_B and Org_C are under "Default Org")
4.- (Ctrl+U to discard last change)
5.- Click on "Org_F" and try to change his parent Organization from "Org_D" to "Org_B". Ctrl+S --> OK (notice that "Org_F" has no children)
6.- Click on "Org_D" (it still has 1 children, Org_E) and try to change his parent Organization from "Org_C" to "Org_A". Ctrl+S --> OK (Notice that Org_A is not under "Default Organization")

Product Defect 12-1R1VX4T (Unable to change the parent organization of an organization with children) was logged after Oracle/Siebel Technical Support has reproduced the issue.
The issue does not occur with Siebel version 8.0.0.5 SIA.

Solution

1) Workaround:
If you want to change the parent organization of an organization with children you have to deassociate the organization then its children and associate first the children and then the parent and then the grand-parent.

2) Solution:
To fix this behavior you will need to apply the Siebel 8.0.0.5 Fix Pack.

Applies to:

Product Release: V7 (Enterprise)

Version: 7.5.2.210 [16060] Com/Med

Database: Oracle 9.2.0.2

Application Server OS: Microsoft Windows 2000 Advanced Server SP 2

Database Server OS: Sun Solaris 2.8

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

Symptoms

SBL-DAT-00496

When we try to update the Parent Position on one of our Positions to any other Position, we get
the following error message:

Can not update Parent because this will introduce recursive
reporting relationship or such relationship already exists for the given Parent.

What does
this mean?

Solution

Message 1

For the benefit of other readers

The customer was getting the following error message on a record imported using EIM when trying to update a parent position:

“Can not update Parent because this will introduce recursive reporting relationship or such relationship already exists for the given Parent.”

Customer resolved the application behavior by looking at all the records on S_PARTY_RPT_REL table, where the party_id for the problem record was located; there was a related party that was repeated with a conflict id. When this sub party record was fixed, customer was able to select a parent for the problem record.

For further information on reporting relationships, Fallow the instruction in FAQ 1909 to ensure the reporting relation has been Synch.

Please review the following section in Siebel Bookshelf: - Importing Employees and Positions -> Siebel Enterprise Integration Manager Administration Guide.

Thank you,

Tuesday, January 25, 2011

Application Deployment

“In any collection of data, the figure most obviously correct, beyond all need of checking, is the error...”

Check, Double-Check, Recheck is the mantra while depolying on production in order to avoid any goofups. Despite any technique being used for deployment including ADM or EIM a thorough sanity should be done after deploying the artifacts on the production envirnoment. This becomes quintessential in multi-project environments where roll out is in phases. Every body has its own strategy based on the environment to perform a sanity check. However the one i have been using is to perform a count of records across the environment along with ADM to deploy artifacts. While ADM ensures that artifacts have been deployed successfully the count helps in confirming that nothing is missed from the source environment.

Here is sample query which can be customized based on the specific artifacts which gives us the count of records from multiple tables such as Personalization rules, runtime events, Views, Views/Responsibility, LOV's :

SELECT

(SELECT COUNT(*) FROM SIEBEL.S_RESP) S_RESP_COUNT, -- Count of Responsibilties

(SELECT COUNT(*) FROM SIEBEL.S_APP_VIEW) S_APP_VIEW_COUNT, -- Count of Views

(SELECT COUNT(*) FROM SIEBEL.S_APP_VIEW_RESP) S_APP_VIEW_RESP_COUNT, -- Count of Resp-View association

(SELECT COUNT(*) FROM SIEBEL.S_LST_OF_VAL) S_LST_OF_VAL_COUNT, -- Count of LOVs

(SELECT COUNT(*) FROM SIEBEL.S_CT_ACTION_SET) S_CT_ACTION_SET_COUNT, -- Count of Runtime Action sets

(SELECT COUNT(*) FROM SIEBEL.S_CT_RULE_SET) S_CT_RULE_SET_COUNT, -- Count of Personalization Action sets

(SELECT COUNT(*) FROM SIEBEL.S_SYS_PREF) S_SYS_PREF_COUNT, -- Count of System Preferences

(SELECT COUNT(*) FROM SIEBEL.S_VALDN_RL_SET) S_VALDN_RL_SET_COUNT -- Count of Validation Rules

FROM DUAL

This query should be run against source and destination databases and results should be compared. The output of this query looks like:

Happy crunching!!

Wednesday, January 19, 2011

SBL-BPR-00609: Copy-record operation is not allowed for single-record transient business components

Applies to:

Error Message Area:Business Processes/Workflow - BPR

Version:Siebel 8.1

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-BPR-00610: Invalid Context Id

Scope

This document is informational and intended for any user.

Monday, January 31, 2011

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Cause

Solution

References

Applies to:

Symptoms

Cause

Solution

Applies to:

Symptoms

Solution

Tuesday, January 25, 2011

Wednesday, January 19, 2011

Applies to:

Purpose

Scope

SBL-BPR-00610: Invalid Context Id

Applies to:

Purpose

Scope

SBL-BPR-00610: Invalid Context Id

Applies to:

Purpose

Scope

SBL-BPR-00608: Error while executing Upsert Siebel Operation without Searchspec.

Applies to:

Purpose

Scope

SBL-BPR-00606: An error has occurred while Post-Cancel event handler invoking workflow/business service.

Applies to:

Purpose

Scope

SBL-BPR-00607: An error has occurred while Post-Complete event handler invoking workflow/business service.

Applies to:

Purpose

Scope

SBL-BPR-00604: Error beginning task transaction with id '%1'.

Applies to:

Purpose

Scope

SBL-BPR-00602: There is no task instance that serves as a lock for the task transaction.

Applies to:

Purpose

Scope

SBL-BPR-00603: Error ending task transaction with id '%1'.

Applies to:

Purpose

Scope

SBL-BPR-00600: The attempt to acquire the lock on the task transaction has failed.

Applies to:

Purpose

Scope

SBL-BPR-00601: Validation failed. The current thread is not the owner of the task transaction.

Applies to:

Purpose

Scope

SBL-BPR-00599: Error loading process definition '%1'. It is not a task and has the special prcoess property TASKTEMPSTORAGESHARING defined, which is not a valid configuration.

Applies to:

Purpose

Scope

SBL-BPR-00596: Error loading process definition '%1'. It is not a 7.0 workflow and has a process property with the name WFSESSIONAFFINITY defined, which is not a valid configuration.

Applies to:

Purpose