z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.2  CHS Com/Med
Database: Oracle 188.8.131.52
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: HP-UX 11i
This document was previously published as Siebel SR 38-1809575601.
"" Checked for Relevance on 09/11/2010 ""
I encounter a problem after adding a user property inside the SIS OM PMT Service "Delta Old Field 10" = my custom field name. The error is [No integration component field corresponding '' (SBL-EAI-04394)]. Normally it would give a field name but this one doesn't.
I think I have completed adding all the custom field in there. But not sure why it still not work.
I attach the log and the SIS OM PMT Service + IO to you.
CauseThe customer has added a user property to the SIS OM PMT Service business service. The user property used is the â€˜Delta Old Fieldâ€™ which is used to capture the old value of a line item field when the line item is change by a modify order. The customer had
For example, Delta Old Field user property is defined as
Name = Delta Old Field 6
Value = [Custom Field 1]:[Custom Field 2]
The custom fields has been added to the Quote Item, MACD Quote Item, Order Entry â€“ Line Items and MACD Order Entry â€“ Line Items. It has been added to the SIS OM Quote and SIS OM Order integration objects.
When the Customize button is used on an Order Line Item, and the Done button is the clicked, the following error is displayed â€“
[No integration component field corresponding '' (SBL-EAI-04394)].
Bug 10493629 - "Receive error after adding new 'Delta Old Field' user property to SIS OM PMT Service bus. service" to report the fact that no field name is included in the error message.
If you encounter this error, please verify that you have taken the configuration steps outlined as follows:
1. Ensure both fields (Custom Field 1 & Custom Field 2) are defined in the Quote Item & MACD Quote Item business components and SIS OM Quote > Line Item Integration Component
2. Ensure both fields are defined in the Order Enter - Line Items & MACD Order Entry - Line Items business components and the SIS OM Order > Line Item Integration Component
3. The first field as defined for the 'Delta Old Field' user property, so only 'Custom Field 1' from [Custom Field 1]:[ Custom Field 2]) also needs to be added to Asset Mgmt â€“ Asset business component and the SIS OM Asset Integration object.
4. Add following user props to SIS OM PMT Service:
SIS OM Quote.Line Item:SIS OM Order.Line Item Map n [Custom Field 1]:[ Custom Field 1]
SIS OM Quote.Line Item:SIS OM Order.Line Item Map n+1 [Custom Field 2]:[ Custom Field 2]
Further information regarding this user property please refer Bookshelf: Siebel Order Management Infrastructure Guide > PSP Engine > Configuring PSP Procedures > Configuring Eligibility, Compatibility, and Pricing > Configuring an Additional Field For Use in Eligibility, Compatibility, and Pricing
Applies to: Siebel CRM - Version: 8.0 SIA  and later [Release: V8 and later ]
Information in this document applies to any platform.
***Checked for relevance on 06-JAN-2011***
SymptomsAn error was reported as below while trying to create a new Integration Object by importing the attached xsd using EAI XSD Wizard.
ObjMgrLog Error 1 0000000249bf16f8:0 2009-03-17 13:26:45 (adptutils.cpp (4937)) SBL-EAI-04394: No integration component field corresponding to 'XML Literal Value'
EAISiebAdpt EAISiebAdptErr 1 0000000249bf16f8:0 2009-03-17 13:26:45  No integration component field corresponding to 'XML Literal Value'(SBL-EAI-04394) (0x23112a)
CauseThrough further testing, the reported behaviour was narrowed down to schema element "default" being specified for xml elements (xs:element) in the xsd that was being imported.
It seems to be a limitation of the Integration Object Builder that it is not able to process the "default" attribute for xml elements whereas it can process it well for xml attributes (xs:attributes).
Per Bookshelf: XML Reference: Siebel Enterprise Application Integration > XML
Integration Objects and the XSD Wizard > Supported XSD Elements and Attributes, the level of support for the schema elements â€œdefault: elementâ€ and â€œdefault: attributeâ€ is mentioned as "Mapped".
where Bookshelf defines Mapped as below:
Mapped. This level of support means that the information specified in a given element
or attribute is used in the integration object representation.â€
So no difference in the behaviour should be observed while importing the schema element â€œdefaultâ€ for xml elements and xml attributes.
Change Request# 12-1SJNU69 has been logged to address this behaviour in a future version of the Siebel product.
SolutionThe XSD could be imported successfully in Siebel Tools after ammending it to remove the "defaultâ€ attribute for the xsd elements while keeping it for xsd attributes .
Applies to: Product Release: V7 (Enterprise)
Version: 7.5.3  Com/Med
Database: Oracle 184.108.40.206
Application Server OS: Sun Solaris 5.8
Database Server OS: Sun Solaris 5.8
This document was previously published as Siebel SR 38-1157161477.
SymptomsSBL-ISS-00119, SBL-ISS-00120, SBL-CFG-00175, SBL-ORD-00141, SBL-DBC-00105, SBL-EAI-04394, SBL-BPR-00162, SBL-EAI-04421
eConfigurator Issues with siebel patch 753.
We have recently Installed siebel patch 753 and we are facing some of the issues with that.
1)All the Product attribute LOV's are appearing in red. Which were appearing fine before this installation.
2)Some of the eConfigurator rules are giving conflicts which were working fine before 753.
3)UI for the some of the product is not appearing as expected eg(on handsets tab Stocklevel field is not getting
expacted values and handsets are appearing in red and giving conflicts)
We have seen the similar SR (38-1059098781) on support web but this does not resolve the problem for us .
Please clarify the follwoing :
1)Is this an expected behaviour after applying the patch.
2)If so , Is there any workaround avalilable for them.
3)If not , Please suggest how to resolve them
We are already in contact with siebel DMO - Lisa Gill on this issue.
SolutionMessage 1For the benefit of other readers:
The customer recently Installed siebel patch 753 and found the following issue within their eConfigurator environment and found that all the Product attribute LOV's for a Customizable Product were appearing in red.This was not the case prior to the patch installation.
Technical Support tested the cusomter's Customizable Product against the standard Siebel configuration (vanilla srf) and sample database. Also used were the customer's customised web templates.
In V220.127.116.11, the attributes displayed after validating are in black.
In V7.5.3, the attributes displayed after validating are in red.
We also observed the same behaviour using the customer's local database against the vanilla srf files of both versions.
As a result Change Request # 12-J99C6K was raised to address this issue. For any customers encountering this issue please contact your Technical Account Manager and/or Technical Support for further guidance
Keywords: Customizable Product, Customisable, Product Administration, UI Designer, Web Template, Class Administration, Product Designer.
Siebel Technical Support.
IMPORT; INTEGRATION COMPONENT; XSD
SBL-EAI-04394; ERROR 1