SBL-EAI-04388: Invalid value '%1' defined for the property '%2'

Applies to: Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite - Version: 2.5 to 2.5 - Release: 2.5 to 2.5
Information in this document applies to any platform.

SymptomsRun the UpgradeCustomerAccountProcess as per requirement in the ' Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite 2.5 - Upgrade Guide Release 2.5 Part No. E18939-01' with the following parameters:

LoopCount = 500;
PageSize = 10;
Ebis_Host_Id = EBIZ_01,
Crmod_Host_Id = CRMOD_01
Though the setting does not make a difference to the error.

The raw xml audit of UpgradeCustomerAccountProcess shows:

<fault><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>Invalid value '' defined for the property 'IncludeSubBooks'(SBL-EAI-04388)</summary>

CauseClearing the WSDL cache and redeploying the BPEL fixed the issue.

SolutionThe solution is to:
1) ensure standard wsdls were in place in $ORACLE_HOME/Apache/Apache/htdocs/AIAComponents/ApplicationObjectLibrary/CRMOD/ODR15/wsdls
2)Undeploy UpgradeCustomerAccountProcess
3)Clear wsdl cache
4)Restart iAS
5)Deploy UpgradeCustomerAccountProcess

References

Related Products Application Integration Architecture > Pre-built Integrations > Pre-built Integrations > Oracle Lead to Order Integration Pack for Oracle CRM On Demand and Oracle E-Business Suite Errors
SBL-EAI-04388

SBL-EAI-04383: Insert operation on integration component '%1' failed because a matching record in business component '%2' with search specification '%3' was found.

Applies to: Siebel Financial Accounts - Version: 7.8.2.6 SIA [19230] and later [Release: V7 and later ]
Information in this document applies to any platform.

Symptoms
The following behavior was reproduced on 7.8.2.14 standard siebel application with CSY web client:

Method Insert of EAI Siebel Adapter will throw the following error if you try to insert a currency record for which a matching records is found:

---------------------------
Siebel
---------------------------
Insert operation on integration component 'Currency' failed because a matching record in business component 'Currency' with search specification '[Currency Code] = "ATS"' was found.(SBL-EAI-04383)

When running the same test with CSY web client, the error is:

---------------------------
Siebel
---------------------------
Vkládací operace na integrační komponentě Currency se nezdařila, protože na základě specifikací hledání [Currency Code] = "ATS" nebyl v obchodní komponentě Currency nalezen žádný odpovídající záznam.(SBL-EAI-04383)


The error message in CSY is wrong translated. It means: Insert operation on integration component Currency failed because no matching record in business component Currency with search specification [Currency Code] = "ATS" was found.(SBL-EAI-04383)

Correct error message is: Insert operation on integration component 'Currency' failed because a matching record in business component 'Currency' with search specification '[Currency Code] = "ATS"' was found.(SBL-EAI-04383)



Cause
Behavior represents a product defect.


SolutionBug 11799003 was logged to address this issue.

Behavior is also reproducible with latest 7.8.2.16 fix pack.
No workaround was found.

ReferencesBUG:11799003 - INCORRECT IDS_ERR_EAI_SA_INSERT_MATCH_FOUND WITH CSY LOCALIZATION




















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

Symptoms
After adding a number of products to a promotion in an order, the following issue arose in a customer environment:
If you click on the Configure button in applet "ISS Promotion Edit UI Detail List Applet" for a customizable product, the eConfigurator UI is not started. However it seems to be started in the background and therefore produce a lot of follow-up issues:
On subsequent attempts to start the product configurator in applet "ISS Promotion Edit UI Detail List Applet",

- either the product configurator produces error messages when the user tries to save the configuration, such as
---
Error invoking service 'SIS OM PMT Service', method 'GetInstance' at step 'Get Instance'(SBL-BPR-00162)
Complex Object instance is not loaded.(SBL-CFG-00156)
---
Error invoking service 'CUT eSales Order Entry Toolkit Service', method 'Gotoview' at step 'Go to Orders View'(SBL-BPR-00162)
Invalid operation when not executed.(SBL-DAT-00471)
---
Error invoking service 'SIS OM PMT Service', method 'Synchronize' at step 'Sync Order Line Item'(SBL-BPR-00162)
Insert operation on integration component 'Line Item' failed because a matching record in business component 'MACD Order Entry - Line Items' with search specification '[Integration Id] = "1-1V38T"| was found.(SBL-EAI-04383)
---
Cannot load active Business Component.(SBL-ORD-00116)
---

- or the product configurator doesn't start at all and there is an error triangle in the bottom left-hand corner of the MS Internet Explorer window; double clicking the error triangle will pop up the following error details:
---
Line: 1
Char: 2
Error: The object does not support this property or method.
URL: http://…/ecommunications_deu/start.swe/SWECmd=GetViewLayout&SWEView=ISS%20Promotion%20Edit%20UI%20View%20-%20Order%20Sales/SWEVI=&SWEVLC=0-1Siebel%2bPower%2bCommunications_43%257c1268352033%257c0_0_21215_000_L
---

Cause
The error was caused by the following custom script on applet "ISS Promotion Edit UI Detail List Applet":

function WebApplet_ShowControl (ControlName, Property, Mode, &HTML)
{
if (ControlName == "Service Id")
{
HTML = this.BusComp().GetFieldValue("Item Id");
}
}

The reason is that function WebApplet_ShowControl is only supported for the Standard Interactivity interface, while applet "ISS Promotion Edit UI Detail List Applet" is displayed in High Interactivity mode.

-> For more information on this function please refer to the following documentation:
Siebel Object Interfaces Reference > Interfaces Reference > Applet Events > WebApplet_ShowControl Event
This event allows scripts to modify the HTML generated by the Siebel Web Engine to render a control on a Web page in an application running in standard interactivity mode.

SolutionTo fix the issue, please do the following:
Log into Siebel Tools.
Eliminate the WebApplet_ShowControl script from applet "ISS Promotion Edit UI Detail List Applet".
Compile the change.

ReferencesBUG:10585711 - AFTER ADDING > 5 ORDER LINE ITEMS, ISS PROMOTION EDIT UI DETAIL LIST APPLET LOSES LIST ITEMS
BUG:10588791 - MODIFY INSTALLED ASSETS DOES NOT WORK FOR PROMOTION WITH 10 TO 19 ASSETS
NOTE:1076550.1 - After adding > 5 order line items, ISS Promotion Edit UI Detail List Applet loses list items




















Applies to: Product Release: V7 (Enterprise)
Version: 7.7.2.5 [18368] ESN Fin Svcs
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: HP-UX 11i

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

SymptomsHi :

We're getting the following error when we generate automatic quote for opportunities with related products.

"Insert operation on integration component 'Quote Item' failed because a matching record in business component 'MACD Quote Item' with search specification '[Integration Id] = &quot;32-1V43&quot;' was found. (SBL-EAI-04383)"

The problem is when we add to the opportunity a bundle with a customizable product.
Here are the steps to reproduce the behavior:

1) Create a Customizable Product with at least one rule.
2) Add this Customizable Product to a Product Bundle.
3) Convert the Bundle to a Regular Customizable Product.
4) Create an opportunity for a contact.
5) Add the Product to the Opportunity (Opportunity Detail - Products View)
6) Press the button in "Opportunity Quote View" to generate automatic quote.

Can you help us to find out a possible solution?
Thanks!

SolutionMessage 1For the benefit of other users:
The behavior described on this Service Request has been reproduced in house thus the Change Request# 12-1EKUI2L has been raised to address it.

Even tough the error message is displayed, the quote is created just fine and you are able to proceed. Please note that the error message is only displayed if the customizable product contains at least one rule. If no rule is associated with the customizable product then the error message is not displayed.

As the error message is not preventing from continuing with the process please take this approach as a workaround for the time being.

SBL-EAI-04382: Cannot find picklist based on the field '%1'

Applies to: Siebel Workflow - Version: 8.1.1 [21112] and later [Release: V8 and later ]
Information in this document applies to any platform.

SymptomsWe have a workflow process which updates 'Ticket Type' field in Service Request business component. After we removed the value in PickList property for the 'Ticket Type' field, the workflow process generates the following error:

Cannot find picklist based on the field 'Ticket Type' SBL-EAI-04382

CauseThe workflow process uses 'EAI Siebel Adapter' business service to update the 'Ticket Type' field. Since the EAI Siebel Adapter uses Integration Object to update a business component field, the corresponding Integration Component field needs to be changed if the business component field is changed. The Integration Component Field corresponding to 'Ticket Type' field had a user property PICKLIST = Y and it causes the error.

SolutionThe issue was resolved by following steps below:

(1) In Siebel Tools, go to [Integration Object] object list and select a record which the workflow process is using to update the 'Ticket Type'.
(2) Go to [Integration Object]->[Integration Component] and select a record which has 'Service Request' in 'External Name' property.
(3) Go to [Integration Object]->[Integration Component]->[Integration Component Field] and select a record which has 'Ticket Type' in 'External Name' property
(4) Go to [Integration Object]->[Integration Component]->[Integration Component Field]->[Integration Component Field User Prop] and delete 'PICKLIST' user property or deactivate it.

Related Products Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Workflow Errors
SBL-EAI-04382; 04382 ERROR

SBL-EAI-04381: For instance of Integration Component '%1', using user key '%2', a record with identical values already exists in the Siebel database

Applies to: Siebel System Software - Version: 7.8.2.3 [19221] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221]
Database: Microsoft SQL Server 2000
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1

This document was previously published as Siebel SR 38-3440380493.
***Checked for relevance on 25-FEB-2011***

SymptomsSBL-EAI-04381

The EAI Siebel Adapter, Upsert method, is called via in inbound web service. While updating some records, an error is sometimes (intermittently) reported saying that the record already exists, and no inserts are allowed. This is not expected behaviour as the upsert method in this case should do an update of the record. The log files gives us the following errors:

DBCLog DBCLogError SQLError: [23000],[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot insert duplicate key row in object 'dbo.S_ORG_EXT' with unique index 'S_ORG_EXT_U1'.

ObjMgrLog Error (adptutils.cpp (5137)) SBL-EAI-04381: For instance of Integration Component 'Account For TEAM', using user key '[CSN] = "10017918"', a record with identical values already exists in the Siebel database.

CauseThe user key was the CSN field, and the value 10017918 did already exist. With detailed logging, the SQL used by the EAI Siebel Adapter to check for the presence of the Account was seen to include an inner join from S_ADDR_ORG.ROW_ID to S_ORG_EXT.PR_ADDR_ID :

INNER JOIN dbo.S_ADDR_ORG T3 ON T2.PR_ADDR_ID = T3.ROW_ID

This was due to the configuration of the custom Business Component ('Account For TEAM'), where a join to S_ADDR_ORG was indeed set as a inner join (so if no address was present, no row could be returned for the BusComp).

SolutionWith the join marked as an outer join, the query generated through the EAI Siebel Adapter could return a row, and the existing Account could be updated.


















Applies to: Siebel Call Center - Version: 8.1.1.2 and later [Release: V8 and later ]
Information in this document applies to any platform.

SymptomsThe EAI Siebel Adapter is used to upsert Account / Address data. The user key field (Street Address) of the child component (Account_Business Address) includes special characters, like hex 0A (linefeed) or 0C (carriage return).

In the first call of the EAI Siebel Adapter upsert, IO is Account > Account_Business Address, and the user key on Account_Business Address includes a field (e.g. Street Address), which may contain hex 0A, all data in created fine.

On second call (upsert) with exactly the same data, EAI Siebel Adapter does not recognize that the address already exists, and tries to create again. So it fails, because the address already exists, with error :-

SBL-DAT-00381: A record that contains identical values to the record you have created already exists.

If you would like to enter a new record, please ensure that the field values are unique.

SBL-EAI-04381: For instance of Integration Component 'Account_Business Address', using user key '[Street Address] = "1234 Bognor Street" AND [City] = "Bognor" AND [State] = "CA"', a record with identical values already exists in the Siebel database.

Please ensure that the field values in the input message are unique.

CauseThis is due to presence of special characters in user key fields (EAI Siebel Adapter is not recognizing the same values exist, and tries to re-create).

The following change request is logged :-

Bug 10600277 - SBL-EAI-04381 when user key contains special character (e.g. linefeed hex 0A)

SolutionTo avoid this situation, ensure the user key fields do not contain these special characters.


















Applies to: Siebel System Software - Version: 7.5.3.5 SIA [16183] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.5 [16183] SVE Fin Svcs
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Microsoft Windows 2000 Server SP 3

This document was previously published as Siebel SR 38-1618255191.
***Checked for relevance on 11-JAN-20111***

SymptomsWhile trying to create a new Integration Object in Siebel Tools,the following errors are seen:


Error occurred during wizard processing. Please press the "Next Error" button to determine the cause of failure.(SBL-DEV-00380)

For instance of Integration Component 'Repository Integration Component Field', using user key '[External Name]="Id"', a record with identical values already exists in the Siebel database.

Please ensure that the field values in the input message are unique.(SBL-EAI-04381)


CauseIt was possible to create the Integration Object on the Server database and it was also possible in Sample using the same Business Object definition.

This meant the local database was somehow corrupt.

SolutionGenerate a new local database to get rid of the corruption and successfully create the integration object.


















Applies to: Siebel Campaigns - Version: 7.8.2 SIA [19213] to 8.0.0.9 SIA[20433] - Release: V7 to V8
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213]
Database: IBM DB2 8.2
Application Server OS: Microsoft Windows 2000 Server SP 2
Database Server OS: IBM AIX 5L 5.3

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

SymptomsSBL-DAT-00382, SBL-EAI-04451

The following error shows when we importing "Marketing Campaign Load" workflow after adding a wait step :

*******
Error Message:
For instance of Integration Component 'Repository WF Step I/O Argument', using user key '[Input Flag] = "O" AND [Name] = "O:Update Schedule Activity1'", a record with identical values already exists in the Siebel database.

Please ensure that the field values in the input message are unique. (SBL-EAI-04381).
*******


CauseOutput argument "Recurring Request" at step "Update Schedule Activity" is defined twice. On deleting the duplicate argument import process is ran successfully.

SolutionMessage 1For the benefit of other users:
This behavior is experienced when using Siebel Industry Applications.

The defect was identified in the standard workflow process (WFP) in Siebel Tools for v7.8.2.x SIA, and v8.0.x.x SIA connected to Sample DB v7.8.2.2 SIA:
WFP: Marketing Campaign Load
WF Step: Update Schedule Activity
WF Step I/O Arguments:
Campaign Id (Process Property)
O:Update Schedule Activity1 (Output Argument: Recurring Request)
O:Update Schedule Activity2 (Output Argument: Recurring Request)
Activity Id (Process Property)

A similar configuration exists in the following standard workflow process:
WFP: Marketing Stage Execution
WF Step: Update Schedule Activity
WF Step I/O Arguments:
Stage Id (Process Property)
O:Update Schedule Activity1 (Output Argument: Recurring Request)
O:Update Schedule Activity2 (Output Argument: Recurring Request)
Activity Id (Process Property)

Change Request 12-1L4KJYZ has been created to request that these two WFPs be changed in a future version of the Siebel application.

The solution fr this issue is to delete the duplicate argument.

Additional Keywords: workflow process step I/O argument, BS: Campaign Execution, Stage Execution, Method: UpdateActivity


















Applies to: Siebel CRM - Version: 8.1.1.1 [21211] and later [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms
Comments
--------
error when importing PublicReportService_v11.wsdl

For instance of Integration Component 'Repository Operation', using user key '[Operation Name] = "impersonate", a record with identical values already exists in the Siebel database.

Please enure that the field values in the input message are unique. (SBL-EAI-04381)

Cause
It was verified that during the WSDL file import process the INSERT operation on the S_WS_OPERATION table violated the INDEX (SIEBEL.S_WS_OPERATION_U1)

Error message:

(oracon.cpp (3211)) SBL-DBC-00111: An error has occurred writing to a record.

ORA-00001: unique constraint (SIEBEL.S_WS_OPERATION_U1) violated
ORA-06512: at line 6

SBL-DAT-00381: A record that contains identical values to the record you have created already exists.

SBL-DAT-00382: The same values for 'Operation Name, ProxyName' already exist.

SBL-EAI-04381: For instance of Integration Component 'Repository Operation', using user key '[Operation Name] = "impersonate"', a record with identical values already exists in the Siebel database.

Please ensure that the field values in the input message are unique.



SolutionIn order to avoid this issue:


1) Delete the business service PublicReportService and all related integration objects prior to running the WSDL wizard per Reports Bookshelf

Using Siebel Tools, delete the PublicReportService outbound Web service and related integrated objects by doing the following:

a Log in to Siebel Tools.
b Query for the PublicReportService business service, and then remove this object.
c Select Integration Object, query for the XMLP Integration project, and then remove all selected objects.

2) Also delete the old PublicReportService web service declaration in the Siebel GUI (Outbound Web Services) and importing the new one from the xml file generated in Tools.

3) The following SQL example can be used to identify orphaned records in the DB.


SELECT
T4.ROW_ID
T4.NAME ,
T4.INBOUND_FLG

FROM

SIEBEL.S_WS_PORT_OPER T1,
SIEBEL.S_WS_OPERATION T2,
SIEBEL.S_WS_PORT T3,
SIEBEL.S_WS_WEBSERVICE T4
WHERE
T1.OPERATION_ID = T2.ROW_ID AND T1.PORT_ID = T3.ROW_ID AND T3.WEB_SERVICE_ID = T4.ROW_ID AND
(T2.NAME = 'impersonate' AND T2.PROXY_NAME ='PublicReportService');


After deleting the old objects the WSDL was imported.




















Applies to: Siebel System Software - Version: 7.7.1 [18306] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9.2.0.4
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8

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

SymptomsHello,

We are having a problem importing iHelp item definitions in Siebel 7.7.1

To test this I carried out the following steps:

Connecting to the Client in a Vanilla instance of Siebel I navigated to Administration > iHelp.
There was one existing iHelp record called 'Create an iHelp item'. I copied this to create another record (right click Copy Record) and named the second record test1.

Next I exported the 'test1' record by selecting the 'Export iHelp Item Definition' option from the menu. When this had successfully exported I deleted the 'test1' record from the GUI and then tried to import the test1.xml file using the 'Import iHelp Item Definition' option from the menu.

On doing this I recieved an error "Method Write Record of business component Task Application (integration component Task Application) for record with search spec [Application] IS NULL 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."

What should we be doing to stop this happening?

CauseSBL-DBC-00111, SBL-EAI-04451, SBL-EAI-04381

SolutionFor the benefit of the readers,

Symptoms:

Customer experienced a failed import of the copy of the seed iHelp "Create an iHelp Item”

Resolution:

The error message SBL-EAI-04451 indicated a failed import due to a NULL value.

By reviewing the data of the XML file generated, it appears that among the field Application Multi Value Group (MVG), none of the value of the seed data "Create an iHelp Item” matched the current Application Name.

If a new record is created, you will notice that the current Application Name will be defaulted and by opening this MVG, you will notice that none of the value of the seed data "Create an iHelp Item" can be selected.

It was verified that the export/import was working as expected on any other records.

To circumvent this behavior, the XML was manually corrected.

Change Request (12-O1WMXL) has been created to request the update of the seed data in a future release.


Likelihood of Occurrence:
7.7.1






















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

GoalDuring Link & Update operations by data stewards in the Incoming Duplicates screen in Siebel UCM (on the same records, simultaneously), following errors occurred :-

SBL-DAT-00523 - The selected record has been modified by another user since it was retrieved.
SBL-EAI-04381 - For instance of Integration Component 'Contact_INS_Personal_Address' using user key "xxxx", a record with identical values already exists in the Siebel database.
Simularly, when two users simultaneously click Create New button on the same record, one user receives an error :-

SBL-IAI-00449 - UCM BC Dedup Search failed to return results from no rows from UCM Contact Source Data and History
How can these errors be avoided ?

SolutionCurrently, there is no provided functionality to avoid these errors if multiple data stewards are processing the same records simultaneously. Therefore, an enhancement change request has been logged :-

BUG 10602140 - UCM - Incoming Duplicates, Link and Update, Create New, conflict with other users

Aside from ensuring no two data stewards are accessing the same record at the same time, one possibility would be custom logic through configuration and scripting, to allow a data steward to 'lock' a target record before the link or create operation.

ReferencesBUG:10602140 - UCM - INCOMING DUPLICATES, LINK AND UPDATE, CREATE NEW, CONFLICT WITH OTHER USERS


















Applies to: Product Release: V7 (Enterprise)
Version: 7.7.2 [18325] Com/Med
Database: Oracle 9.2.0.5
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: IBM AIX 5L 5.2

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

SymptomsSBL-EAI-04381

We have a production environment where an order is raised against a billing account.Once the order is sucessfully submitted to EAI after that we receive a inbound message from EAI.The inbound process involves creation of Asset against the service account.

The creation of Asset is happening using the siebel OOB workflow "SIS OM Apply Completed Service Order Line Item to Service Profile".

The step in the WF "Sync Asset" is giving an error "For instance of Integration Component 'Line Item', using user key '[Integration Id] = "1-NZ5O1Y"', a record with identical values already exists in the Siebel database." We tried searching the database with the above integration id but there were no records found in the S_ASSET table.

We tried simulating the WF by giving the inputs Asset Integration Id(Root Order Item's Integration Id),Order Header Id(Order Row Id),Object Id(Root Order Line Item Id),Root Id(Root Order Item Id) but we encountered the same error.

We tried changing the User Key:2 for the integration object "SIS OM Asset" for Integration Component "Asset Mgmt - Asset" from Integration Id to Id and Integration Id to Order Integration Id but could not get rid of the error, hence we have reverted back.

The SQL Log while simulating the WF and the screen shot are attached with this SR.
The sample XML message before the step SYNCH asset is also attached with this mail.

Regards

SolutionMessage 1For the benefits of other user:

The issue was determined with some of the triggers, generated for the workflow policies. After inactivating these policy, this issue does not occur.

Keywords: EAI, EAI Siebel Adapter, Execute

Related Products Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Workflow Errors SBL-IAI-00449; SBL-DAT-00523; SBL-EAI-04381

SBL-EAI-04378: No rows retrieved corresponding to the business component '%1'

Applies to: Siebel System Software - Version: 7.7.2 SIA [18325] and later [Release: V7 and later ]
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325] Travel
Database: IBM DB2 8.1 FixPack 5
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-2449000491.
***Checked for relevance on 14-JAN-2010***

Symptoms1st, try with EAI Siebel Adapter and Sample Account integration object

“No rows retrieved corresponding to the business component 'Account'(SBL-EAI-04378)”
Looking at the log file it can be seen the Where clause in the select statement used to retrieve the records to delete included all of the fields and values included in the XML document.
As a result, as account name was NOT specified in the XML, the query included the criteria “S_ORG_EXT.NAME = NULL” and obviously no records were returned.

Set the input argument DeleteByUserKey to “true” for the Siebel Adapter and this time only the user key (Integration Id) was included in the Where clause and a record was returned and deleted.

The above demonstrates how DeleteByUserKey works.

2nd, try with ASI Siebel Account:

Activate and compile business service Siebel Account to the SRF and publish it as a web service and generate a WSDL for it.

Import it in a 3rd party tools such as SOAPUI.

Set a value for Integration Id and invoke the Delete method.

Looking at the log file for the EAI Object Manager task one can see the Delete method was invoked but the “No rows retrieved” error message was returned.

Set DeleteByUserKey to “true” when invoking the ASI web service by specifying DeleteByUserKey as an input argument for the Siebel Account business service.

Reviewing the logs it is noticed it has no effect.

CauseThe reason is although the functionality of EAI Siebel Adapter and ASI business services is similarit is not exactly the same.
They are implemented with different specialized C++ classes and therefore have a slightly different behavior.
DeleteByUserKey has no effect on ASI.

Solution

On a related note, this customer also wanted to be able delete child instances only.
The following information is provided in Integration Platform Technologies: Siebel Enterprise Application Integration > EAI Siebel Adapter Business Service > EAI Siebel Adapter Business Service Methods >Delete Method

“Any child contacts that once belonged to the account will still remain in the database, but will not be associated with this Account.”

Therefore, it appeared that it was not possible to delete only child instances of a root integration component instance using the Delete method.

Options are to create nn integration object for each child integration component where the child was the parent but this seems time consuming.
Or to invoke the Synchronize method instead.




















Applies to: Siebel Universal Customer Master - Version: 7.8.1.1 [19044] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.8.1.1 [19044]
Database: Oracle 10g
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9

This document was previously published as Siebel SR 38-2989014511.
***Checked for relevance on 10-NOV-2010***

SymptomsThe workflow process 'UCM Account Batch Data Management Workflow' is erroring out with the following error message in the logs

[0] No rows retrieved corresponding to the business component 'DeDuplication - SSA Account Key'(SBL-EAI-04378) (IDS_ERR_EAI_SA_BC_NO_DATA)

CauseData quality was not enabled.

8,789 4/3/2006 20:18 1 (ucmsvccdm.cpp (428)) SBL-IAI-00443: UCM Data Quality Manager Found no match

For each record processed, this path was executed:

Instantiating step definition 'Process NoMatch'.
Invoking method 'HandleMatchCase' on business service 'UCM Batch Manager'

In this step rows are being inserted/updated on various tables such as ACCNT_POSTN, S_ORG_BU, S_PARTY, S_ORG_EXT, etc.

And when inserting into S_PARTY this error occurs:


20,456 4/3/2006 20:18 4 BEGIN INSERT INTO UCMBASE.S_PARTY ( CONFLICT_ID, LAST_UPD, CREATED, LAST_UPD_BY, CREATED_BY, MODIFICATION_NUM, ROW_ID, GROUP_TYPE_CD, NAME, PARTY_TYPE_CD, PARTY_UID) VALUES

(query.cpp (5066)) SBL-DAT-00416: No field matches identifier 'ADL Status'. Please ask your systems administrator to check your application configuration.

20,590 4/3/2006 20:18 3 Executing process definition 'UCM Key ReGenerate Workflow'.
20,612 4/3/2006 20:18 4 Invoking method 'Delete' on business service 'EAI Siebel Adapter'.
20,613 4/3/2006 20:18 4 Input: @0*0*2*0*0*0*10*SearchSpec56*[DeDuplication - SSA Account Key.Account ID] = '1-1625J'13*IntObjectName31*DeDuplication - SSA Account Key
20,625 4/3/2006 20:18 2 (physmod.cpp (3673)) SBL-DAT-00511: A transaction is already in progress
20,637 4/3/2006 20:18 1 [0] No rows retrieved corresponding to the business component 'DeDuplication - SSA Account Key'(SBL-EAI-04378) (IDS_ERR_EAI_SA_BC_NO_DATA)20,640 4/3/2006 20:18 1 (stepexec.cpp (803)) SBL-BPR-00162: Error invoking service 'EAI Siebel Adapter', method 'Delete' at step 'Delete Key'.
20,665 4/3/2006 20:18 1 (adptutils.cpp (5113)) SBL-EAI-04451: Method 'WriteRecord' of business component 'Account' (integration component 'Account') for record with search specification '[Party UId] = "A6520ED9-CA9D-4221-880A-0FA8152FA895"' returned the following error:"Err
20,666 4/3/2006 20:18 4 EndTransaction (ABORT) was called on DB connection 140c2bc8


SolutionEnable data quality as per bookshelf


















Applies to: Siebel System Software - Version: 7.8.2 [19213] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213]
Database: Oracle 10g
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: SUSE Linux 8

This document was previously published as Siebel SR 38-3044021771.
***Checked for relevance on 18-Nov-2010***

SymptomsWhile sending a child objects with delete operations (for an execute method) it was expected the adapter would delete them if they exist, and ignore them if they don't.

Instead, if one of the records doesn't exist, the following error is observed:

"End of File"

The whole transaction is rolled back.

CauseThe "End of File" error described by customer is due to EAI Siebel Adapter attempting to delete a row that no longer exists in the database. The EAI Siebel Adapter errorring out in this situation is expected. However, the error message "End of File" is not very descriptive.

SolutionA change request 12-186TCP4 has been logged to enhance the error message to be more descriptive.

In Siebel 7.8 version, this scenario will return the following error message instead:

"No rows retrieved corresponding to the business component 'Contact'(SBL-EAI-04378)"

If you do not wish the 'EAI Siebel Adapter' method 'Execute' to error if the to-be-deleted record does not exist in the Siebel database, then you can do the following:

1. The Execute method has an input argument called ErrorOnNonExistingDelete (Error If Record Not Found). When the to-be-deleted record does not exist, then the business service will return an error. This occurs when the ErrorOnNonExistingDelete is not specified for the Execute method, or if it is set to the value of 'true'.

When 'ErrorOnNonExistingDelete' = false, no error occurs.

Please set input argument 'ErrorOnNonExistingDelete' = false

2. Or, instead of using the Execute method, you can use the 'EAI Siebel Adapter' bus service 'Synchronize' method.
















Applies to: Siebel Sales Web Channel - Version: 7.8.2.3 [19221] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
***Checked for relevance on 15-OCT-2010***

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

SymptomsIn standard Siebel DDK generated code, the Delete function in the service.java does not handle the exception of Null Row Id being passed for delete operation. This could be fatal as it deletes all the records in the table.

Even though 'Null' Id check can be put in the code, there could be a better solution to prevent the such delete from happening.


Causeproduct enhancement request.

Solution
When invoking Delete method of EAI Siebel Adapter (or DeleteLeaves of EAI UI Data Adapter), an integration object instance is provided as input argument and it is used to make query condition to find out buscomp records deleted. Here if the integration object contains integration component element as well as integration component field with no value specified (null value), the adapter searches for the buscom record with ‘NULL’ value in the field corresponding to the integration component field. When no record is found, it throws the following error:

No rows retrieved corresponding to the business component 'Service Request'(SBL-EAI-04378)

However, if integration component is provided but no integration component field is provided at all, the adapter queries out all buscomp records and deletes all the buscomp records. That is expected behavior by current design of EAI Siebel Adapter and EAI UI Data Adapter.

In this case, the SOAP request message, which is sent from external java application based on DDK generate code, contains Service Request integration component but does not contain any integration component field. That is why EAI UI Data Adapter queries out all Service Request records and deletes all the buscomp records.

It might be able to cause an unexpected behavior when no row_id is provided but no record should be deleted.

So BUG : 10513096 has been logged to address the product enhancement request (Please add an input argument to prevent Siebel Adapter from deleting all records with Delete method).


ReferencesBUG:10513096 - PLEASE ADD AN INPUT ARGUMENT TO PREVENT SIEBEL ADAPTER FROM DELETING ALL RECORDS WITH DELETE METHOD

Related Products Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Sales Web Channel Keywords
QUERY; EAI SIEBEL ADAPTER; EAI UI DATA ADAPTER
Errors
SBL-EAI-04378

In WfProcMgr log it starts with this:

A possible solution is to create an integration object that only includes the integration components and user key fields that are required to identify the record(s) to be deleted.

For example, create a copy of the Account Interface and Internal Account Interface integration objects that include only the Account integration component and the Integration Id field and referenced them in Siebel Account business service.

Integration Id will then be the only field included in the WSDL and when the web service is invoked the record with the specified Integration Id will be correctly deleted.

Another possibility was to have a web service that is based on a workflow that invokes the Delete Method on the EAI Siebel Adapter and sets DeleteByUserKey to “true”.
The advantage of this approach is that any non-user key fields included in the incoming XML would not be included in the select statement used to retrieve the record or records to be deleted.

Create a workflow process that reads from a file a Siebel XML document based on the Sample Account integration object, converts it to a hierarchy and calls the Delete method on the EAI Siebel Adapter.
User Key: 1 references the field Integration Id.
The XML document included an Integration Id but all of the other field tags were empty.

When executed the following error is seen :

SBL-EAI-04376: Method '%1' of business component '%2' (integration component '%3') returned the following error:"%4"

Applies to: Siebel System Software - Version: 7.8.2 SIA [19213] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213] CHS Com/Med
Database: Oracle 9.2.0.7
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1

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

SymptomsIn the Sample Database of Siebel ,Create an integration object (IO) named 'Product Definition to Background System'
Include integration components (ICs) :

'Internal Product - ISS Admin'

'ISS Product Attribute VBC'

'Price List Item'

'Cost List Item' In Business Service Simulator simulate Business Service(BS) EAI Siebel Adapter using method Query to get Product information out.

The following error is observed :

Method 'Execute' of business component 'ISS Product Attribute VBC' (integration component 'ISS Product Attribute VBC') returned the following error:"Field 'VOD Object Num' does not exist in definition for business component 'ISS Product VOD BusComp'.
Please ask your systems administrator to check your application configuration.(SBL-DAT-00398)"(SBL-EAI-04376) (0x562f)

CauseEAI cannot be used to retrieve versioned seed data information.
Enhancement Request 12-17911AG has been logged to include information on this.

SolutionEAI cannot be used to retrieve versioned seed data information.
Enhancement Request 12-17911AG has been logged to include information on this.

To retrieve them, please use the provided Import/Export functionality in the workspace product.

For details on the use of Import/Export functionalities, please refer to Product Administration Guide > Releasing Products and Other Versioned Objects > Migrating Products Among Environments.


ReferencesBUG:10502756 - EAI CANNOT BE USED TO RETRIEVE PRODUCT VERSIONED DATA

















Applies to: Siebel System Software - Version: 7.8.2 SIA [19213] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213] Fin Svcs
Database: Microsoft SQL Server 2000 SP4
Application Server OS: Microsoft Windows 2000 Professional
Database Server OS: Microsoft Windows 2000 Professional

This document was previously published as Siebel SR 38-3136795571.
""""Checked for relevance on 19-NOV-2010""""

SymptomsCreate an Integration Object based on Contact to synchronize external data with Siebel using XML. Call the "Synchronize" method from the "EAI Siebel Adapter" business service.

When there were Accounts to disassociate from a Contact (integration component Contact_Account) on the XML, Siebel raised the following error:

Error Code: (SBL-BPR-00162)--(SBL-DAT-00511)
Error Message: Error invoking service 'EAI Siebel Adapter', method 'Synchronize' at step 'Sync'.(SBL-BPR-00162)
--
Method 'DeleteRecord' of business component 'Account' (integration component 'Contact_Account') returned the following error:
"A transaction is already in progress(SBL-DAT-00511)"(SBL-EAI-04376)




Cause
This behavior was reproducible on the workflow and business service simulator on Siebel 7.8.2.3 [19221] SIA and SEA and with the Synchronize and Update methods from the EAI Siebel Adapter.

After further researches the behavior was found to be a product defect and the Change Request 10512335 has been created regarding this issue.

Solution
As a workaround, please do not use operations on MVG associations and, instead, create a new child BC based on the intersection table to achieve the functionality .
It gives full control on all EAI operations that happens.
It requires a new BO and new IO as well.

ReferencesBUG:10512335 - ERROR WHILE DOING A SYNCHRONIZE WITH THE EAI SIEBEL ADAPTER














Applies to: Siebel System Software - Version: 7.5.3.12 [16272] and later [Release: V7 and later ]
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.3.12 [16272]
Database: IBM DB2 for zOS and OS/390 v7
Application Server OS: IBM AIX 5L 5.1
Database Server OS: IBM zOS

This document was previously published as Siebel SR 38-2653099651.
***Checked for relevance on 02-DEC-2010***

SymptomsWhen attempting to import a data map to another environment, the following error message was generated:


"Method 'Execute' of business component 'EAI DTE Integration Field'(integration component '') returned the following error: "An error has occurred executing a Sql statement. Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00105)"(SBL-EAI-04376)"


CauseThe behavior is related to the referencing of picklist 'EAI DTE Source Field PickList' in the Source Expression field of EAI Field Map business component.

To explain further, when the data map is import, it is going through the EAI Data Map integration object. In the EAI Field Map integration component(corresponding to the EAI Field Map business component), the Source Field Expression integration component field has the PICKLIST user property defined and its value is set to 'Y'. This indicates to the system that it is a picklist. Thus, when importing the data map, the system will try to check the value of the Source Expression against NAME column of the picklist business component 'EAI DTE Integration Field'. As this business component is based on S_INT_FIELD table, this resulted in the SQL statement searching against S_INT_FIELD.NAME column.


However, if the record is entered via the user interface, as the picklist is not a bounded picklist, no query against the picklist is performed and thus the similar SQL statement will not be generated, thus avoiding the error message encountered.

The encountered error message is related to the behavior reported in Change Request 12-LV264P. In the Change Request, it is reported that if a query is using a query criteria which is longer than the defined field length, the 'CLI0109E String data right truncation' error will be encountered. The error message also seems to be specific to when connected to the DB2 database.

Solution

To possibly workaround the behavior, either of the below options may be considered:

1) In EAI Data Map integration object, EAI Field Map integration component, Source Field Expression integration component field, modify the value of the PICKLIST integration component field user property from 'Y' to 'N'. Compile the change and test if the import of the data map still gives the error.

2) Prior to the import, in the XML, modify the Source Expression to contain a shorter string. Then import the data map, and after the import, in the user interface, update to Source Expression to contain the actual string.

ReferencesBUG:10476882 - ERROR: [2][IBM][CLIDRIVER]CLI0109E


















Applies to: Siebel eConfigurator - Version: 8.1.1 [21112] and later [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms
The following error message is displayed when migrating promotions from source to target environment:

[1] Partial Import: ; [1] Method 'Execute' of business component
'Product Promotions Relationship VBC' (integration component 'Product
Promotions Relationship VBC') returned the following error: "An active
version can not be found; Type ISS_PROD_DEF; Name Price for Life
Unlimited MRC; Time stamp 04/06/2010
12:57:01(SBL-ISS-00121)"(SBL-EAI-04376); Data will be skipped ; [1]
Method 'Execute' of business component 'Product Promotions Relationship
VBC' (integration component 'Product Promotions Relationship VBC')
returned the following error: "An active version can not be found; Type
ISS_PROD_DEF; Name Price for Life Unlimited MRC; Time stamp 04/07/2010
09:01:15(SBL-ISS-00121)"(SBL-EAI-04376); Data will be skipped ; [1]
Method 'Execute' of business component 'Product Promotions Relationship
VBC' (integration component 'Product Promotions Relationship VBC')
returned the following error: "An active version can not be found; Type
ISS_PROD_DEF; Name Price for Life Unlimited MRC; Time stamp 04/07/2010
13:27:48(SBL-ISS-00121)"(SBL-EAI-04376); Data will be skipped ;


Steps to reproduce it:

1-) Create a Customizable Product with 1 child Product in the source environment

Root Product SF
Child Product SF 1

No Min or Default cardinality defined in the product. Max was set to 999 by default.

2-) Create a Promotion with Root Product SF

Promotion
Root Product (Min =1, Default =1 , Max =1)
Child Product

No promotions constraints or cardinality were set to the child products

3-) Export the promotion export using Full Structure

4-) Import in the target environment and release all objects

5-) In the source environment, add a new child Product to the Root Product

Root Product SF
Child Product SF 1
Child Product SF 2

No Min or Default cardinality defined in the product. Max was set to 999 by default.

6-) Check the Promotion and you will see that the Child Product SF 2 is now part of it.

7-) Re-export the promotion using Objects Only

8-) Import the Promotion in the target

=> We get the following error message:

Import: Partial; ; [1] Method 'Execute' of business component 'Product Promotions Relationship VBC' (integration component 'Product Promotions Relationship VBC') returned the following error:
"An active version can not be found; Type ISS_PROD_DEF; Name Child Product SF 1; Time stamp 04/30/2010 11:47:11(SBL-ISS-00121)"(SBL-EAI-04376); Data will be skipped

9-) Re-export the Promotion using Full Structure and import in the target environment

=> We get the same error message:

Import: Partial; ; [1] Method 'Execute' of business component 'Product Promotions Relationship VBC' (integration component 'Product Promotions Relationship VBC') returned the following error:
"An active version can not be found; Type ISS_PROD_DEF; Name Child Product SF 2; Time stamp 04/30/2010 11:47:11(SBL-ISS-00121)"(SBL-EAI-04376); Data will be skipped

In version 7.8, the object gets imported as expected with no error messages using the same scenario.

Note: the error message is displayed even after applying the workaround provided on
Bug 10583814 "Getting the error SBL-EAI-04421, when importing a product promotion from one environment of 8.1.1 to other environment"

CausePer engineering analysis, the unexpected behavior is caused by the new Virtual Business Component "Product Promotions Relationship VBC". This VBC was added as part of AIA 2.1. (ACR 474) for a feature called "Component Level Adjustment" and subsequently merged into 8.1.1.1. That feature has no correlation with workspace project import/export but they happen to use the same "ISS Promotion" integration object.

SolutionWe have logged Change Request Bug 10591941 "Receiving an error message when migrating promotions" and there is a quick fix available for version 8.1.1.1.

Bug ID: 9749955
Base Required: Fix Pack 8.1.1.1[21211]
Patch Abstract: 8.1.1.1 21211 SBA QF0196 SEBL_ARU

In case you are facing this issue and there is no quick fix available for your Siebel Application Version, please log a Service Request.

















Applies to: Siebel Product and Price Administrator - Version: 8.1.1.2 and later [Release: V8 and later ]
Information in this document applies to any platform.

SymptomsWhen attempting to export a promotion after there is a change to an attribute of one of the Component Products then the following error occurs:

Method 'Execute' of business component 'Product Promotions Relationship VBC' (integration component 'Product Promotions Relationship VBC') returned the following error: "Set of related Objects (Dynamic Model) Object Type ISS_PROD_DEF Name Version 1 [1] Extended Attribute - Attribute 2; The Item can not be found"(SBL-EAI-04376)

Steps to reproduce:
1) Log onto Siebel Call Center as SADMIN\SADMIN
2) Create an attribute GG_Attribute_1 and release
3) Create a Product Class GG_Class_1 and add GG_Attribute_1 as the attribute definition
4) Create a new Product GG_Component_1 with class GG_Class_1
5) Create a new Product GG_Root_Product add a relationship with the product GG_Component_1
6) Create a new Bundled Promotion GG_Promotion_1 and check Show in Catalog
7) Add GG_Root_Product with MIN=MAX=1
8) Add pricing adjustment - Drilldown on product name, create new adjustment with Adjustment Type=% Discount and Value =20
9) Release new version - Clear Cache
10) Create a new Workspace Project and add GG_Promotion_1
11) Export the workspace and note no errors
12) Create a new attribute GG_Attribute_2
13) Create a new Class GG_Class_2 and add GG_Attribute_2 - release
14) Create a new Product GG_Component_2 with class GG_Class_2, set the attribute Required flag to True
15) Add GG_Component_2 TO GG_Root_Product - release
16) Change GG_Class_2 to remove the GG_Attribute_2 and add the Attribute again but with a new name - Release
17) Change GG_Component_2 to remove the old attribute reference and leave the new one with required flag not checked
18) Navigate to Workspace Projects and try to export the Promotion again
19) See the following error:

We detected an Error which may have occurred for one or more of the following reasons:

Method 'Execute' of business component 'Product Promotions Relationship VBC' (integration component 'Product Promotions Relationship VBC') returned the following error: "Set of related Objects (Dynamic Model) Object Type ISS_PROD_DEF Name Version 1 [1] Extended Attribute - Attribute 2; The Item can not be found"(SBL-EAI-04376)



CauseThis issue is due to a product defect.

SolutionThis issue was logged as product defect CR 10595928.

The quickfix QF0310 was created for product version 8.1.1.3. This can be downloaded from using the following patch id: Patch 10007524


When available, download 8.1.1.4 Fix Pack to resolve this issue.
Note that this patch was not available at the time of writing this document (September 2010).

ReferencesBUG:10595928 - ERROR SBL-EAI-04376 OCCURRING WHEN EXPORT A PROMOTION WHERE AN ATTRIBUTE HAS BEEN CHANGED
PATCH:10007524 - 8.1.1.3 21219 SBA QF0310 SEBL_ARU




















Applies to: Siebel SmartScript - Version: 8.0.0.5 SIA [20420] and later [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms
Comments
--------
=== ODM Issue Clarification ===

The customer was using ADM to import SmartScripts into Production. The process works correctly for simple SmartScripts but you encounter the following error when trying to import more complex ones:

SBL-EAI-04376: Method 'WriteRecord' of business component 'ADM Smart Script Answer' (integration component '') returned the following error:
"An error has occurred writing to a record.

"ObjMgrBusCompLog Error 1 0000000f4bd72dc4:0 2010-04-28 01:54:41 (oracon.cpp (3202)) SBL-DBC-00111: An error has occurred writing to a record.
Please continue or ask your systems administrator to check your application configuration if the problem persists.
SQLParseAndExecute Execute 5 0000000f4bd72dc4:0 2010-04-28 01:54:41 ORA-01400: cannot insert NULL into ("SIEBEL"."S_CS_ANSWR"."ORDER_BY")"



Cause
=== ODM Cause Determination ===

The the field "Number" of the business component "ADM Smart Script Answer" did not have property "Predefault Value" and "Post Default Value" to "1".




Solution
=== ODM Solution / Action Plan ===

1) Open Siebel Tools and navigate to the BusComp object type.
2) Search for "ADM Smart Script Answer".
3) Find the field "Number" of the business component "ADM Smart Script Answer".
4) Set the property "Predefault Value" and "Post Default Value" to "1".
5) Compile these changes to the SRF file and test again the ADM import.
















Applies to: Siebel CRM - Version: 8.1.1.1 [21211] and later [Release: V8 and later ]
Information in this document applies to any platform.

SymptomsAn error occurred while submitting a new order from Sales Order > Line Items applet in Siebel to AIA 2.5.

---
ObjMgrLog Error 1 000000044bf60a48:0 2010-05-21 15:57:41 (oracon.cpp (3211)) SBL-DBC-00108: An error has occurred preparing a Sql statement.
Please continue or ask your systems administrator to check your application configuration if the problem persists.
SQLParseAndExecute Execute 5 000000044bf60a48:0 2010-05-21 15:57:41 ORA-00942: table or view does not exist
----

Siebel version use was 8.1.1.1 SIA [21111] with QF1102 related to ACR 474 and ACR 508 for supporting AIA 2.5.


CauseFrom analysis of the log level 5 component log files, the cause of the error was traced down to missing tables/fields in the siebel schema . Due to this, the underlying SQL referencing those tables failed.

SolutionFrom the QF1102 install guide, it is seen that the QF introduces schema changes to the database for some existing tables. These schema changes need to applied in the underlying physical database by clicking "Apply/DDL" button in Siebel Tools.

While this seem to be done for the affected tables listed in the QF install guide, still the error was not resolved. Apparently there could be some other table(s) for which the changes needed to be applied, however, this could not be determined in absence of further information.

Documentation Defect # 12-1YBWHXZ was raised requesting to provide further information if there could be other table (other than the ones listed in the QF install guide) for which DDLSync needs to be done

In this case, the issue was resolved by doing "Apply/DLL" for all existing tables in the siebel repository
















Applies to: Siebel eCommunications - Version: 7.7.2.6 SIA [18372] - Release: V7
Information in this document applies to any platform.

SymptomsWhile executing 'Query' method of 'EAI Siebel Adapter', an error is thrown as below:-.

------------------
ObjMgrLog Error 1 0 2010-01-28 15:13:40 (oracon.cpp (3050)) SBL-DBC-00108: An error has occurred preparing a Sql statement. Please continue or ask your systems administrator to check your application configuration if the problem persists.
SQLParseAndExecute Execute 5 0 2010-01-28 15:13:40 ORA-01747: invalid user.table.column, table.column, or column specification
...
ObjMgrLog Error 1 0 2010-01-28 15:13:40 (siebadpt.h (1876)) SBL-EAI-04376: Method
'Execute' of business component 'VIV Contact for Billing Account' (integration component 'VIV Contact for Billing Account') returned the following error: "An error has occurred preparing a Sql statement.
--------------------

CauseFrom analysis of the detailed log, it was seen that the missing column name was for a field of the buscomp 'VIV Contact for Billing Account' which was joined to 'LANG_CD' column of 'S_LANG' table using outer join.

-------------------------
EAISiebAdpt EAISiebAdptTrcDebug 5 0 2010-01-28 15:13:38 Setting SearchSpec '' on Business Component 'VIV Contact for Billing Account'
...
SELECT /*+ ALL_ROWS */
....
SIEBEL.S_LANG T6,
SIEBEL.S_PARTY T19,
WHERE
T19. = T6.LANG_CD (+) AND
--------------------

Analyzing the joins configured on the buscomp ''VIV Contact for Billing Account' to 'S_LANG' table, it was found that the field 'ACS Invoice Language Integration Code' was used as the 'Source Field' in the Join Specification for the join to 'LANG_CD' column of 'S_LANG' table through. However, the field 'ACS Invoice Language Integration Code' is defined as a calculated field on the buscomp.

Per Bookshelf documentation at link :- http://download.oracle.com/docs/cd/E05553_01/books/OTR/OTRObjTypesList131.html#wp143951

Calculated fields cannot be used in the 'Source Field' property of the Join Specification'. 'Source Field' should always contain a field that is mapped to a physical table column.

SolutionAfter making necessary modification to the buscomp and IO definition, the error was resolved.

ReferencesSBL-DBC-00108
SBL-EAI-04376
ORA-01747

Related Products Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel eCommunications Errors
SBL-EAI-04376; SBL-DBC-00108; ORA-1747

SBL-EAI-04375: The source expression (%1) specified selecting a unique component instance for the map.

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

CauseUpon investigation of the detailed Siebel Dedicated Client log ('SIEBEL_LOG_EVENTS' environment variable was set to '5'), produced on the customer's site, it was found what the following SQL-select statement delivers no record:

"... 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 Keywords

---

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)..."