Applies to: Siebel System Software - Version: 7.5.3.2 SIA [16168] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.2 [16168] Pub Sect
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-1177864271.
""""Checked for relevance on 05-JAN-2011""""
Symptoms
"... SELECT ...
FROM dbo.S_LST_OF_VAL T1
INNER JOIN dbo.S_LST_OF_VAL T2 ON T1.PAR_ROW_ID = T2.ROW_ID
WHERE
((T1.ACTIVE_FLG = 'Y' OR T1.ACTIVE_FLG IS NULL) AND
(T2.VAL IS NOT NULL) AND
(T1.TYPE = 'WS_BINDING_PROTOCOL_CD' AND T2.VAL = 'OUTBOUND' )) AND
(T1.VAL LIKE 'SOAP[_]DOC%' )
ORDER BY
T2.VAL ..."
Whereas, normally, one data row should be returned (to allow 'Document' type binding in Outbound Web Service integration).
This means value "SOAP_DOC" was not active in the picklist
Solution
The reported behavior was solved by customer, by adding the missing LOV-entry (Type=' WS_BINDING_PROTOCOL_CD', Display Value/LIC=' OUTBOUND', Active='Y', ... ) on the 'List of Values View' Siebel Client view (View > Site Map > Application Administration > List of Values).
Applies to: Siebel System Software - Version: 7.5.2.211 [16061] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.2.211 [16061]
Database: Oracle 8.1.7.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: IBM AIX 4.3.3
This document was previously published as Siebel SR 38-1048962561.
***Checked for relevance on 07-JAN-2011***
Symptomsa Workflow Process was being called from the WriteRecord method, to send an email using the Outbound Communications Manager. This would work the first time it was called, but on subsequent calls, the error was generated :-
Method 'WriteRecord' of business component 'Service Request' (integration component 'Service Request') for record with search specification '[SR Number]="RM14040081"' returned the following error:"Invalid operation when not executed.(SBL-DAT-00471)"(SBL-EAI-04375)
Error invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Upsert into Siebel'.(SBL-BPR-00162)
CauseThe behaviour was re-produced, and change request 10466006 has been logged for this defect.
Solutions a workaround, instead of calling a Workflow Process from script to call the Outbound Communications Manager, the customer used a Workflow Policy. The Workflow Policy was able to monitor for the creation of the required rows on the database, and invoke the Workflow Process to send the email.
Applies to: Siebel System Software - Version: 7.5.3.2 [16168] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.2 [16168]
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Server
Database Server OS: Microsoft Windows 2000 Server
This document was previously published as Siebel SR 38-1206436891.
***Checked for relevance on 12-JAN-2011***
SymptomsA customer imported quote records from the external system using the EAI process.
The quote record came in an xml format.When the discount element had a very big number
(ex: 4.833333333339333) following error was raised
""Value too long for field 'Discount Percent' (maximum size 16).(SBL-DAT-00235)"(SBL-EAI-04375)
--
Error invoking service 'EAI Siebel Adapter', method 'Execute' at step 'Upsert, delete Quote In
Siebel'.(SBL-BPR-00162)"
CauseDiscount Percent field had the following property
Field Name: Discount Percent
Type: DTYPE_NUMBER
SCALE=7
Precision=22
and the error is expected.
SolutionTo be able to avoid the behavior on a high level we can introduce a custom Business Service as a step in the workflow that parses the data to retreieve the discountfield value and rounds the data to 2 decimal places.
The customer resolved the behavior by rounding the data to 2 decimal places in the external system.
Applies to: Siebel System Software - Version: 7.5.2 [15051] to 8.1.1 [21112] - Release: V7 to V8
All Platforms
This document was previously published as Siebel SR 38-3489326221.
SymptomsSBL-DAT-00225, SBL-EAI-04375
We are trying to import a wsdl of an Outbound Webservice into Siebel tools and during the import process the following error is raising up:
Method 'SetFieldValue' of business component 'Repository Business Service Method Arg' (integration component 'Repository Business Service Method Arg') for record with search specification '[Name]="demanderImpressionRequest:parameters"' returned the following error:"The value entered in field Integration Object of buscomp Repository Business Service Method Arg does not match any value in the bounded pick list Repository PickList Integration Object.(SBL-DAT-00225)"(SBL-EAI-04375)
We don't have the feeling that something is created on the local database, we can't find any integration object and any webservice.
You will find in attachment the detailed siebdev.log and the wsdl.
CauseProduct defect:
It was found this was related to the local database on which the wsdl was being imported. There was another repository present, already containing the Integration Objects which the wsdl wizard was trying to create. After removing the related Integration Objects from the second repository, the wsdl wizard could successfully create the objects in the Siebel Repository.
Solution
For the benefit of other readers, an error was encountered when importing a wsdl for an outbound web service (using Tools on a local database) :-
Method 'SetFieldValue' of business component 'Repository Business Service Method Arg' (integration component 'Repository Business Service Method Arg') for record with search specification '[Name]="demanderImpressionRequest:parameters"' returned the following error:"The value entered in field Integration Object of buscomp Repository Business Service Method Arg does not match any value in the bounded pick list Repository PickList Integration Object.(SBL-DAT-00225)"(SBL-EAI-04375)
Change request 12-1LTF1I0 has been logged to request that any presence of the objects in another repository should be ignored.
Current solution for local db, is to remove the objects from other Siebel Repositories.
Alternative workaround in Siebel Tools .SRF:
Change the .SRF file used by Siebel Tools compiling into it (you need to create an .SRF file copy in order to compile in this .SRF) , following modification of the "Repository Business Service Method Arg" Business Component:
Add an additional Pickmap entry to the "Integration Object" BC Field with following properties:
Field: Repository Id
Constrain: Y (checked!)
Picklist Field: Repository Id
Comments: TS Fix for the CR#10531598
NOTE: this change should correct the behavior of Siebel Tools, by constraining the selection of Int Objects to current Siebel Repository.
Applies to: Siebel Workflow - Version: 7.5.3.15 SIA [16279] - Release: V7
Information in this document applies to any platform.
GoalWe are getting an error when trying to import a number of workflows into one of our development environment. Other workflows import correctly, and the problem workflows import correctly on two other development machines.
For example with the attached workflow we get:
Method 'WriteRecord' of business component 'Workflow Step Input Arguments' (integration component 'Workflow Step Input Arguments') for record with search specification '[Name]="MS Extract Date" AND [Input Flag]="I"' returned the following error:"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)"(SBL-EAI-04375)
Re-extracting the workflow has no effect, nor does it matter if we use thick or thin client. I have attached a section of a log file from when I clicked the Import button.
We are to begin building on this environment this week but cannot until these workflows are imported. We don't have another spare environment to use.
Solution
The error turned out to be a problem with database space. Removing data from the transaction log tables and removing outdated workflows resolved the issue.
Applies to: Product Release: V7 (Enterprise)
Version: 7.5.3.4 [16180] Auto
Database: IBM DB2/UDB 7.2
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-1274129691.
SymptomsHi,
When I try to import a workflow I get the following error message:
We detected an Error which may have occurred for one or more of the following reasons:
Method 'WriteRecord' of business component 'Workflow Branch Criteria Value' (integration component 'Workflow Branch Criteria Value') for record with search specification '[Sequence]="3"' returned the following error:"Please ensure that the required information is specified.(SBL-APS-00175)"(SBL-EAI-04375)
The Workflow was exported from my local client and now after testing I want to import it on the server client.
Please advise.
SolutionMessage 1For the benefit of our readers.
The customer encountered the following error message while trying to import his workflow process.
Method 'WriteRecord' of business component 'Workflow Branch Criteria Value' (integration component 'Workflow Branch Criteria Value') for record with search specification '[Sequence]="3"' returned the following error:"Please ensure that the required information is specified.(SBL-APS-00175)"(SBL-EAI-04375)
The error message indicates that some branch criteria values, which are referencing LOVs, cannot be found in the LOVs in the DB. It is a common problem with workflow import. You need to inspect the branch criteria values, find out which LOVs they map to, and check the LOV entries to see if the criteria values in the .xml files match the LOV entries.
Suggestions:
1. Ensure that \\siebsrvr\object\SRF is the same as \\client\object\SRF.
2. If its not an SRF issue then identify the LOVs referenced in the workflow process and remove them in order to import your process.
Resolution:
The customer reported that both the server and client SRF are the same and removing the LOVs in their workflow allowed them to import their process.
Applies to: Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Oracle 9i
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8
This document was previously published as Siebel SR 38-1165548251.
SymptomsSBL-APS-00175, SBL-EAI-04451
Currently we are in the process of migrating from development to test environment. We need to export/import our workflows created in dev. When trying to import a particular workflow into test, we receive the following error:
Method 'WriteRecord' of business component 'Workflow Branch Criteria Value' (integration component 'Workflow Branch Criteria Value') for record with search specification '[Sequence]="1"' returned the following error:"Please ensure that the required information is specified.(SBL-APS-00175)"(SBL-EAI-04375)
I found the root of the problem. It is because within one of our decision points in the workflow, the decision point is looking for a value 'School'. Within our application, 'School' exists many times for the LOV type = 311_DOHMH_LOCATION_TYPE but have different Parent values (part of a constrained picklist).
I referred to SR#38-1029886811 which had the same problem. However, the work around was to make the value and LIC distinct. We cannot do this due to a business requirement. We need 'School' to be associated to different parent values.
Is there another work around for this issue?
I will attach the export of our workflow process in case you want to view it. The error is happening for the value 'School' which can be found in the 'Location Type 2' decision point.
Thank you
SolutionMessage 1For the benefit of other customers:
The workaround that worked was to make the Display Name unique. Change Request # 12-JGBOTO has been logged for this behavior. Another workaround is to remove the workflow steps using these LOVs and add them manually into the workflow process after import.
Thank you,
Products
Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel System Software
Errors
Import a WSDL in Siebel Tools WSDL Import Wizard successfully.
Get the runtime definition XML generated by the import process.
Log in to siebel client and go to Site Map > Web Services Administration > Outbound Web Services
Import the runtime definition XML
Observe the error :
"...Method 'SetFieldValue' of business component 'Port' (integration component 'Port') for record with search specification '[Name]="..."' returned the following error:"The value entered in field Protocol of buscomp Port does not match any value in the bounded pick list WebService Binding Protocol Picklist.(SBL-DAT-00225)"(SBL-EAI-04375)..."
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.2 [16168] Pub Sect
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-1177864271.
""""Checked for relevance on 05-JAN-2011""""
Symptoms
"... SELECT ...
FROM dbo.S_LST_OF_VAL T1
INNER JOIN dbo.S_LST_OF_VAL T2 ON T1.PAR_ROW_ID = T2.ROW_ID
WHERE
((T1.ACTIVE_FLG = 'Y' OR T1.ACTIVE_FLG IS NULL) AND
(T2.VAL IS NOT NULL) AND
(T1.TYPE = 'WS_BINDING_PROTOCOL_CD' AND T2.VAL = 'OUTBOUND' )) AND
(T1.VAL LIKE 'SOAP[_]DOC%' )
ORDER BY
T2.VAL ..."
Whereas, normally, one data row should be returned (to allow 'Document' type binding in Outbound Web Service integration).
This means value "SOAP_DOC" was not active in the picklist
Solution
The reported behavior was solved by customer, by adding the missing LOV-entry (Type=' WS_BINDING_PROTOCOL_CD', Display Value/LIC=' OUTBOUND', Active='Y', ... ) on the 'List of Values View' Siebel Client view (View > Site Map > Application Administration > List of Values).
Applies to: Siebel System Software - Version: 7.5.2.211 [16061] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.2.211 [16061]
Database: Oracle 8.1.7.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: IBM AIX 4.3.3
This document was previously published as Siebel SR 38-1048962561.
***Checked for relevance on 07-JAN-2011***
Symptomsa Workflow Process was being called from the WriteRecord method, to send an email using the Outbound Communications Manager. This would work the first time it was called, but on subsequent calls, the error was generated :-
Method 'WriteRecord' of business component 'Service Request' (integration component 'Service Request') for record with search specification '[SR Number]="RM14040081"' returned the following error:"Invalid operation when not executed.(SBL-DAT-00471)"(SBL-EAI-04375)
Error invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Upsert into Siebel'.(SBL-BPR-00162)
CauseThe behaviour was re-produced, and change request 10466006 has been logged for this defect.
Solutions a workaround, instead of calling a Workflow Process from script to call the Outbound Communications Manager, the customer used a Workflow Policy. The Workflow Policy was able to monitor for the creation of the required rows on the database, and invoke the Workflow Process to send the email.
Applies to: Siebel System Software - Version: 7.5.3.2 [16168] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.2 [16168]
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Server
Database Server OS: Microsoft Windows 2000 Server
This document was previously published as Siebel SR 38-1206436891.
***Checked for relevance on 12-JAN-2011***
SymptomsA customer imported quote records from the external system using the EAI process.
The quote record came in an xml format.When the discount element had a very big number
(ex: 4.833333333339333) following error was raised
""Value too long for field 'Discount Percent' (maximum size 16).(SBL-DAT-00235)"(SBL-EAI-04375)
--
Error invoking service 'EAI Siebel Adapter', method 'Execute' at step 'Upsert, delete Quote In
Siebel'.(SBL-BPR-00162)"
CauseDiscount Percent field had the following property
Field Name: Discount Percent
Type: DTYPE_NUMBER
SCALE=7
Precision=22
and the error is expected.
SolutionTo be able to avoid the behavior on a high level we can introduce a custom Business Service as a step in the workflow that parses the data to retreieve the discountfield value and rounds the data to 2 decimal places.
The customer resolved the behavior by rounding the data to 2 decimal places in the external system.
Applies to: Siebel System Software - Version: 7.5.2 [15051] to 8.1.1 [21112] - Release: V7 to V8
All Platforms
This document was previously published as Siebel SR 38-3489326221.
SymptomsSBL-DAT-00225, SBL-EAI-04375
We are trying to import a wsdl of an Outbound Webservice into Siebel tools and during the import process the following error is raising up:
Method 'SetFieldValue' of business component 'Repository Business Service Method Arg' (integration component 'Repository Business Service Method Arg') for record with search specification '[Name]="demanderImpressionRequest:parameters"' returned the following error:"The value entered in field Integration Object of buscomp Repository Business Service Method Arg does not match any value in the bounded pick list Repository PickList Integration Object.(SBL-DAT-00225)"(SBL-EAI-04375)
We don't have the feeling that something is created on the local database, we can't find any integration object and any webservice.
You will find in attachment the detailed siebdev.log and the wsdl.
CauseProduct defect:
It was found this was related to the local database on which the wsdl was being imported. There was another repository present, already containing the Integration Objects which the wsdl wizard was trying to create. After removing the related Integration Objects from the second repository, the wsdl wizard could successfully create the objects in the Siebel Repository.
Solution
For the benefit of other readers, an error was encountered when importing a wsdl for an outbound web service (using Tools on a local database) :-
Method 'SetFieldValue' of business component 'Repository Business Service Method Arg' (integration component 'Repository Business Service Method Arg') for record with search specification '[Name]="demanderImpressionRequest:parameters"' returned the following error:"The value entered in field Integration Object of buscomp Repository Business Service Method Arg does not match any value in the bounded pick list Repository PickList Integration Object.(SBL-DAT-00225)"(SBL-EAI-04375)
Change request 12-1LTF1I0 has been logged to request that any presence of the objects in another repository should be ignored.
Current solution for local db, is to remove the objects from other Siebel Repositories.
Alternative workaround in Siebel Tools .SRF:
Change the .SRF file used by Siebel Tools compiling into it (you need to create an .SRF file copy in order to compile in this .SRF) , following modification of the "Repository Business Service Method Arg" Business Component:
Add an additional Pickmap entry to the "Integration Object" BC Field with following properties:
Field: Repository Id
Constrain: Y (checked!)
Picklist Field: Repository Id
Comments: TS Fix for the CR#10531598
NOTE: this change should correct the behavior of Siebel Tools, by constraining the selection of Int Objects to current Siebel Repository.
Applies to: Siebel Workflow - Version: 7.5.3.15 SIA [16279] - Release: V7
Information in this document applies to any platform.
GoalWe are getting an error when trying to import a number of workflows into one of our development environment. Other workflows import correctly, and the problem workflows import correctly on two other development machines.
For example with the attached workflow we get:
Method 'WriteRecord' of business component 'Workflow Step Input Arguments' (integration component 'Workflow Step Input Arguments') for record with search specification '[Name]="MS Extract Date" AND [Input Flag]="I"' returned the following error:"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)"(SBL-EAI-04375)
Re-extracting the workflow has no effect, nor does it matter if we use thick or thin client. I have attached a section of a log file from when I clicked the Import button.
We are to begin building on this environment this week but cannot until these workflows are imported. We don't have another spare environment to use.
Solution
The error turned out to be a problem with database space. Removing data from the transaction log tables and removing outdated workflows resolved the issue.
Applies to: Product Release: V7 (Enterprise)
Version: 7.5.3.4 [16180] Auto
Database: IBM DB2/UDB 7.2
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-1274129691.
SymptomsHi,
When I try to import a workflow I get the following error message:
We detected an Error which may have occurred for one or more of the following reasons:
Method 'WriteRecord' of business component 'Workflow Branch Criteria Value' (integration component 'Workflow Branch Criteria Value') for record with search specification '[Sequence]="3"' returned the following error:"Please ensure that the required information is specified.(SBL-APS-00175)"(SBL-EAI-04375)
The Workflow was exported from my local client and now after testing I want to import it on the server client.
Please advise.
SolutionMessage 1For the benefit of our readers.
The customer encountered the following error message while trying to import his workflow process.
Method 'WriteRecord' of business component 'Workflow Branch Criteria Value' (integration component 'Workflow Branch Criteria Value') for record with search specification '[Sequence]="3"' returned the following error:"Please ensure that the required information is specified.(SBL-APS-00175)"(SBL-EAI-04375)
The error message indicates that some branch criteria values, which are referencing LOVs, cannot be found in the LOVs in the DB. It is a common problem with workflow import. You need to inspect the branch criteria values, find out which LOVs they map to, and check the LOV entries to see if the criteria values in the .xml files match the LOV entries.
Suggestions:
1. Ensure that \\siebsrvr\object\SRF is the same as \\client\object\SRF.
2. If its not an SRF issue then identify the LOVs referenced in the workflow process and remove them in order to import your process.
Resolution:
The customer reported that both the server and client SRF are the same and removing the LOVs in their workflow allowed them to import their process.
Applies to: Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Oracle 9i
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8
This document was previously published as Siebel SR 38-1165548251.
SymptomsSBL-APS-00175, SBL-EAI-04451
Currently we are in the process of migrating from development to test environment. We need to export/import our workflows created in dev. When trying to import a particular workflow into test, we receive the following error:
Method 'WriteRecord' of business component 'Workflow Branch Criteria Value' (integration component 'Workflow Branch Criteria Value') for record with search specification '[Sequence]="1"' returned the following error:"Please ensure that the required information is specified.(SBL-APS-00175)"(SBL-EAI-04375)
I found the root of the problem. It is because within one of our decision points in the workflow, the decision point is looking for a value 'School'. Within our application, 'School' exists many times for the LOV type = 311_DOHMH_LOCATION_TYPE but have different Parent values (part of a constrained picklist).
I referred to SR#38-1029886811 which had the same problem. However, the work around was to make the value and LIC distinct. We cannot do this due to a business requirement. We need 'School' to be associated to different parent values.
Is there another work around for this issue?
I will attach the export of our workflow process in case you want to view it. The error is happening for the value 'School' which can be found in the 'Location Type 2' decision point.
Thank you
SolutionMessage 1For the benefit of other customers:
The workaround that worked was to make the Display Name unique. Change Request # 12-JGBOTO has been logged for this behavior. Another workaround is to remove the workflow steps using these LOVs and add them manually into the workflow process after import.
Thank you,
Products
WSDL; WEB SERVICES; IMPORT PROCESSES; PICKLIST
|
Errors
SBL-DAT-00225; SBL-EAI-04375
|
Import a WSDL in Siebel Tools WSDL Import Wizard successfully.
Get the runtime definition XML generated by the import process.
Log in to siebel client and go to Site Map > Web Services Administration > Outbound Web Services
Import the runtime definition XML
Observe the error :
"...Method 'SetFieldValue' of business component 'Port' (integration component 'Port') for record with search specification '[Name]="..."' returned the following error:"The value entered in field Protocol of buscomp Port does not match any value in the bounded pick list WebService Binding Protocol Picklist.(SBL-DAT-00225)"(SBL-EAI-04375)..."
No comments:
Post a Comment