SBL-BPR-00187: Error updating business component at step '%1'.
Applies to:
Siebel Tools - Version: 8.1.1 [21112]
Information in this document applies to any platform.
Symptoms
The customer had a problem with a custom External Business Component. When a workflow executed the step to write in this EBC it exited with the error below:
- - -
SBL-EXL-00151: Error sending Trouble Ticket to TTM. Error updating business component at step Write XMLDoc In Table Ex .(SBL-BPR-00187)
- - -
Cause
The error mentioned appeared well in the log file provided but before this one the following errors were also found:
- - -
…
ObjMgrSqlLog Detail 4 0000122b4bed0ea0:0 2010-05-20 18:30:40 Incorrect SQLSTYLE 0 SQLOBJECT NOT cached.
ObjMgrBusCompLog Error 1 0000122b4bed0ea0:0 2010-05-20 18:30:40 (sqlobj.cpp (10497)) SBL-DAT-00175: Database connection was lost, please retry.
…
ObjMgrSqlLog Detail 4 0000122b4bed0ea0:0 2010-05-20 18:30:40 Incorrect SQLSTYLE 0 SQLOBJECT NOT cached.
…
- - -
This revealed that the DSSQLStyle profile parameter was not (or at least not correctly) set for the Data Source of the custom EBC.
Note that DSSQLStyle is one of the profile parameters to be set when configuring the data source definition for an EBC. This parameter and the supported SQL Styles are discussed in the Bookshelf:
Integration Platform Technologies: Siebel Enterprise Application Integration
External Business Components
Process of Configuring External Business Components
Specifying Run-Time Parameters
For example, "Oracle" and "OracleCBO" are the SQL Type used for Oracle databases. "OracleCBO" is for Oracle databases with cost based optimization, namely for Oracle database version 9i (or later).
Solution
It was suggested to set the DSSQLStyle profile parameter as mentioned in the Bookshelf and restart the Siebel server. This suggestion resolved the customer issue.
References
NOTE:535105.1 - External Business Component - Database connection was lost, please retry.(SBL-DAT-00175)
Applies to:
Siebel Workflow - Version: 7.7.2 SIA [18325]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325] Fin Svcs
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Server
Database Server OS: Microsoft Windows 2000 Server
This document was previously published as Siebel SR 38-1712881391.
Symptoms
SBL-DAT-00292, SBL-DAT-00498, SBL-BPR-00100, SBL-BPR-00187
We have the following business scenario and are finding it difficult to find a
technical solution. Could you please help.
We have a Case entity (based on HLS Case)
exposed through a partner portal. Whenever a partner makes a change to the status of the case we
want to create an activity, associated with the modified case, which would notify an internal
employee to review the case and make further changes if required. For the internal person to
update the activity, they need to be the owner of the activity, as otherwise the activity is
read-only for them. The person to whom this activity needs to be assigned is the primary employee
for a Case Team Leader position. This person would then manually delegate out the activity to
their subordinates (employees in positions Case Team Worker 1, Case Team Worker 2,
etc).
We have done further testing and find that when we set the Primary Owned By field on the activity to a specific owner e.g. SADMIN, the owner of the activity is changed successfully but the primary employee is not, but only if we change the BC Class to CSSBCBase. If the class is CSSBCFINSActivity we get the following error.
Error: SiebelError: Error updating business component at step 'Change Activity Owner'.(SBL-BPR-00187)This error is returned when the workflow is executing the Siebel Operation business service.(SBL-BPR-00100)
An error has occurred picking the current row. Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00292)
'Action (Unconstrained).Display' is a required field. Please enter a value for the field. (SBL-DAT-00498)
1. Using assignment manager.
This would involve a significant amount of configuration if we are to implement exactly as per
requirement. We could either add some skill to the team leader and use dynamic assignment or use
static assignment. If we were to use static assignment, every time the team leader would change,
we would also need to update Employee Candidates. We have not implemented Assignment Manager for
the current release and are will probably not be able to, due to time constraints.
2. Use
Workflow to determine the primary employee for the position and set the Primary Owned By field to
that. We are having problems with being able to prototype this. We first create an activity in a
Siebel Operation step and then try to update the activity in another Siebel Operation step by
setting Primary Owned By field to a specific login for now. However this operation fails. We have
tried setting it to an employee that normally appears in the activity Owner picklist (to make
sure Popup visibility does not affect our test), but with no success.
Changes
Cause
CSSBCFINSActivity class
Solution
We've successfully implemented the functionality we desired. This involved using a copy of the Action BC. To achieve this we had to perform the following:
1. Create a Link Action/Employee(no organization bound)
2. Change the Employee MVL on the cloned Action BC to use the child BC and Link from step 1.
3. Inactivate some MV fields (AMS User STOI, AMS User CL) on cloned Action BC that come from Employee MVL as these caused problems.
4. Changed Picklist property of Owned By, Primary Owned By and Primary Owner Id to PickList Employee(no organization bound)
5. Added extra field record to the Insert Siebel Operation step in our workflow, which sets Primary Owned By to a value which is a login of a user (in our case this is derived from a subprocess.)
Thanks.
Applies to:
Product Release: V7 (Enterprise)
Version: 7.5.3.3 [16172]
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-2609823707.
Symptoms
SBL-BPR-00187
I am trying to set up Partner self-reg in the prmportal_enu application and when I get to the
step where I click "Register Company" or "Register Self" clicking it give me this
error:
Error updating business component at step 'Commit Partner Profile
Data'.(SBL-BPR-00187)
And I see this error in the eChannel log
file:
Error Error 1 2005-10-25
18:14:50 SQLError: [23000],[Microsoft][ODBC SQL Server Driver][SQL
Server]Cannot insert the value NULL into column 'POSTN_ID', table 'svsiebdb.dbo.S_POSTN_CON';
column does not allow nulls. INSERT fails.
We are using LDAP for authentication and I have
the Application User set to a user who can read/write to the LDAP database. What could be causing
this error?
Solution
Message 1
For the benefit of other readers:
The behavior that the customer encountered was because the OM - Proxye Employee value was set to GUESTCP instead of PROXYE.
Thanks,
Siebel Support
Keywords: SBL-BPR-00187, 23000, self register, register self, register company
Applies to:
Siebel Loyalty Customer Portal - Version: 8.1.1 SIA [21111] - Release: V8
Information in this document applies to any platform.
Symptoms
e-Loyalty portal: encountered problem in points transfer. Please see attached file "e-Loyalty Point transfer error.zip" for snapshots. Navigation: Membership details--> Points Transfer
Error
------
Erro updating BC at step 'Create ABB trasaction"(SBL-BPR-00187).
and In log file - you can see
PrcExec PropSet 4 000001db4a2c3e10:0 2009-06-08 14:43:20 Error updating business component at step 'Create ABB Transaction'.(SBL-BPR-00187)
--
This error is returned when the workflow/task is executing the Siebel Operation business service.(SBL-BPR-00100)
--
'Product Id' is a required field. Please enter a value for the field.(SBL-DAT-00498)
Cause
This is a Defect.I have raised CR # 10570188 for this issue.
Solution
I have raised CR # 10570188 for this issue and CR has been attached to SR.
Engineering team has given suggestion on this that -Need to define a Product with Part # = 'PTTXN' similar to how we do in case of 'Action Based Bonus' & 'Referral Bonus' (at the time of Enrolment).
Applies to:
Siebel Workflow - Version: 7.7.2.7 SIA [18376] to 8.1.1 SIA [21111] - Release: V7 to V8
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise) V8 (Enterprise)
This document was previously published as Siebel SR 38-3283449341.
Symptoms
In a Siebel Workflow Process, Siebel Operation step, Customer was trying to construct a query expression which uses a date calculation.
User is trying to find Service Requests that were created for a contact in the past 180 days. My expression looks something like this:
"[Contact Id] = '" + [&ContactId] + "' AND [Status] = 'Accepted' AND [Created] > (Timestamp() - 180)"
The below error when User run this statement, and discovered it was due to the "- 180" portion.
Error updating business component at step 'Query SR'.(SBL-BPR-00187)
Missing quotes around the search criteria or unnecessary punctuation will often cause an error.(SBL-DAT-00403)
After searching for "SBL-DAT-00403" , it was discovered that a Change Request 10465817 was logged for this behavior.
Cause
In expression - The minus Sign is not correctly interpreted, so the parsing fails and raises an error.
Solution
The case exposed here is due to the use of minus sign in operation
Timestamp() – 180
The minus is not correctly interpreted, so the parsing fails and raises an error.
Please, refer In a workflow process condition expression, what is the format of the argument, provided to an arithmetic operation involving a ‘Timestamp ()’ function? (Doc ID 476582.1)
The workaround exposed in the above document, which is to reverse the direction of comparison operator in order to avoid the use of the minus sign does not work.
In the current case, the last expression should look like the following:
([Created] + 180) < Timestamp()
Problem implementing this workaround is that workflow does not correctly interpret the field name and error stating that “Created + 180” is not a known field.
Complete error message:
Error updating business component at step 'Query SR'.(SBL-BPR-00187)
--
This error is returned when the workflow is executing the Siebel Operation business service.(SBL-BPR-00100)
--
No field matches identifier 'Created + 180'.
Change Request number 12-1IE6NIS was logged for addressing this unexpected behavior.In 8.0 version status is WIll not fix and the workaround is However using double quotes around the query text works fine.
This CR has referred another CR# 10446393 [Calculation in QBE for date/time fields not possible, if field is not in UI.] for similar issue which is a Enhancement Request.
CR# 10446393 details -Enter the following QBE in one field:
"[Updated] < (Timestamp() -0.01)"
This will generate the following error:
An error has occurred due to an invalid search for field 'Description'. The invalid expression was '[Updated] < (Timestamp() -0.01)'.
This has not fixed in any version , still pointing to Future release. Whenever an Enhancement Request has been created, the request will be reviewed by Siebel Product marketing and Siebel Engineering teams and prioritized and implemented in the future release.
Final workaround was to add a previous Workflow step for computing the Timestamp()-180 expression and set a Process Property, then use it in the Search Spec.
Here are steps for achieving this implementation:
1) Add a Process Property:
Name: Timestamp-180
Data Type : String
2) Insert a new Workflow Step in the Workflow chain before the “Query SR” step:
Name: Compute Timestamp-180
BS Name: Workflow Utilities
BS Method: Echo
3) Add an Output Argument in this Workflow Step:
Property Name: Timestamp-180
Type: Expression
Value: Timestamp() - 180
4) Modify the Search Specification of the “Query SR” Workflow Step:
Search Specification: "[Created] > '" + [&Timestamp-180] + "'"
תגובות
הוסף רשומת תגובה