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) :
'ISS Product Attribute VBC'
'Price List Item'
'Cost List Item'
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 | |
תגובות
הוסף רשומת תגובה