Applies to:
Siebel E-Support - Version: 8.1.1 SIA [21111] - Release: V8Information in this document applies to any platform.
Symptoms
Solutions are created in Siebel CRM and associated with Catalog/Category. Next solution items (Solutions and Resolution Documents), were re indexed in Siebel. The solution items can be searched fine by logging into Oracle Secure Enterprise Search. However, these solutions were NOT visible in Siebel E-Support application under Support tab > Technical Support.The following errors are noted in CustomAppObjMgr and Oracle Application Server log:-
--------------
WebSvcInbound WSInboundTrace 3 0000018f4b9016f8:0 2010-03-04 20:54:52 Executing web service operation 'SearchSolution' by calling method 'SearchSolution' of business service 'Search Solution Service'Executing Operation '&1' by calling method '&2' of business service '&3'.
...
ObjMgrBusServiceLog Error 1 0000018f4b9016f8:0 2010-03-04 20:55:13 (xmlcnvsv.cpp (548)) SBL-EAI-00246: XML Hierarchy Converter error - empty input message, expecting an XML document in
...
EAITransport EAITransportWarning 2 0000018f4b9016f8:0 2010-03-04 20:55:13 Dispatch Service: 'Web Service Inbound Dispatcher', Method: 'Dispatch' failed
EAITransport EAITransportWarning 2 0000018f4b9016f8:0 2010-03-04 20:55:13 [0] XML Hierarchy Converter error - empty input message, expecting an XML document in
----------------
Cause
Investigating further into the issue and consulting with engineering team, it was learn 't that there are known issues around using OSES functionality with Siebel CRM and Siebel Self Service. These issues are addressed in siebel version 8.1.1.1 with ACR 452 configured (as per the Maintenance release guide at link :-.https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=880452.1&h=Y). This requires installing OSES version 10.1.8.4 and above.Since, in this case, OSES 10.1.8.4 was not installed, the functionality did not work as expected due to the known issues.
Solution
The issue was resolved by installing OSES version 10.1.8.4.Applies to:
Siebel Universal Customer Master - Version: 8.1.1 SIA [21111]Siebel CRM - Version: 8.1.1 SIA [21111] and later [Release: V8 and later]
Information in this document applies to any platform.
***Checked for relevance on 11-JAN-20111***
Symptoms
The "The host/address 'adc60120fems.us.oracle.com' could not be resolved(SBL-EAI-00247)" error message is raised by Siebel Tools WSDL Import Wizard during import of the Oracle AIA MDM .WSDLs: SyncOrganizationUCMJMSProducer.wsdl and SyncPersonUCMJMSProducer.wsdlThe installation task, outlined in the "Creating the Proxy Business Service" section of the "Process for Configuring Data Enrichment" section of the "Siebel UCM Data Enrichment
Web Services" chapter of the "Siebel UCM and CRM Integration Guide" document can not be completed.
Cause
The "adc60120fems.us.oracle.com" Oracle sample host name, as well the "7818" standard port value are provided as only as place holders in the schema include statements in the delivered .WSDL files.
The "include" statement in the being imported .WSDL file should not point to the "adc60120fems.us.oracle.com" site, but to a local SOA (OC4J) Instance with the AIA MDM installation. Similarly the actual port value should be corrected if it differs from the standard one.
Solution
Before running WSDL Import in Siebel Tools, please correct the .WSDL files for host and port name of actual SOA (OC4J) instance.
Alternatively, if the standard port value can be used, one could temporary (until the WSDL Import step is complete) add the host name "adc60120fems.us.oracle.com" entry in the "hosts" file of the Siebel Tools Windows machine, located in the "\Windows\System32\drivers\etc" system folder). The entry should assigning the name to the IP address to the actual SOA (OC4J) instance.
The Change Request Bug 10567675 has been logged to ask for accordant note in the of the "Siebel UCM Data Enrichment Web Services" chapter of the "Siebel UCM and CRM Integration Guide" document can not be completed.
References
BUG:10567675 - [CR#12-1THO69P][FR#12-1THO6AB] UCM AND CRM INTEGRATION GUIDE SHOULD ADDRESS HOSTApplies to:
Siebel CRM - Version: 8.0.0.5 [20420]Information in this document applies to any platform.
Goal
Customer has inbound integration, where if incoming data is ISO-8859-1, UTF-8 or UTF-16, the process works fine.But when using ISO-8859-15, the EAI XML Converter (method XMLDocToIntObjHier) fails with :-
The XML Document cannot be converted to an XML Hierarchy.(SBL-EAI-04110)
Fatal Error in XML Parser at line 1, column 45: An exception occurred! Type:TranscodingException, Message:Could not create a converter for encoding: ISO-8859-15(SBL-EAI-00247)
This only occurs on Linux platform (seems to work fine on Windows, Solaris).
Solution
Change request is now created and associated to the SR :-BUG 10589812 - On Linux :- Could not create a converter for encoding: ISO-8859-15
At time of writing, the change request is still open, and it is noted there that this is a limitation of the version of the Linux Xerces parser included in the Siebel product.
References
BUG:10589812 - ON LINUX :- COULD NOT CREATE A CONVERTER FOR ENCODING: ISO-8859-15Applies to:
Siebel Marketing - Version: 8.1.1 SIA [21111]Information in this document applies to any platform.
Symptoms
Comments
--------
=== ODM Issue Clarification ===
From Landing Site screen, in Landing Page view , while doing preview getting this error.
Also Same error is encountered in Preview and Deploy in View.
Error from UI
---------------------------
Siebel
---------------------------
HTTP Request error during 'Submitting Data Send HTTP request': 'Status code - 500'(SBL-EAI-04117)
---------------------------
OK
---------------------------
Error in ObjMgr Log
____Object Mgr Log __________
ObjMgrLog Error 1 0000066a4b8e0c6c:0 2010-03-04 11:32:37 (httptransport.cpp (1631)) SBL-EAI-04117: HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 500'
ObjMgrLog Error 1 0000066a4b8e0c6c:0 2010-03-04 11:32:37 (httptransport.cpp (981)) SBL-EAI-04117: HTTP Request error during 'Submitting Data Send HTTP request': 'Status code - 500'
ObjMgrLog Error 1 0000066a4b8e0c6c:0 2010-03-04 11:32:37 (xmlcnv.cpp (1727)) SBL-EAI-00247: Fatal Error in XML Parser at line 28, column 188: Expected end of tag 'HR'
Cause
Comments
--------
=== ODM Cause Determination ===
Wrong parameter setting in properties file:
WebSurveyHandlerClassName = oracle.apps.sem.wsd.runtime.queueing.MBQQueueHandle
Comments
--------
=== ODM Cause Justification ===
Verified against working instance where it is:
WebSurveyHandlerClassName = oracle.apps.sem.wsd.runtime.queueing.MBQQueueHandler
Solution
Comments
--------
=== ODM Solution / Action Plan ===
In Siebel Marketing Installation and Administration Guide Version 8.1 > Setting Up Web Marketing > Setting Up Siebel Web Marketing > To configure the Web Survey Daemon > step 4 it says 'MBQQueueHandle', but it needs to be 'MBQQueueHandler' (note the 'r' at the end).
Documentation defect (#12-1XF0FNJ 'Typo in documentation regarding MBQQueueHandler') has been logged to address this.
References
BUG:10588695 - TYPO IN DOCUMENTATION REGARDING MBQQUEUEHANDLERNOTE:785710.1 - 'Submit' button not showing on a deployed Survey on version 8.1.1
Applies to:
Siebel CRM - Version: 8.0.0.5 SIA [20420]Information in this document applies to any platform.
***Checked for relevance on 04-Jan-2011***
Symptoms
When I try to import a WSDL File, I'm getting following errors.Project: CM Interface
WSDL file to import: C:\Documents and Settings\Edgar\Escritorio\Interfaces\BPEL_CAMB_DOMICILIOS\BPEL_CAMB_DOMICILIOS.wsdl
Run-time configuration data file: C:\Documents and Settings\Edgar\Escritorio\Interfaces\BPEL_CAMB_DOMICILIOS\BPEL_CAMB_DOMICILIOS.xml
Log File: C:\Documents and Settings\Edgar\Escritorio\Interfaces\BPEL_CAMB_DOMICILIOS\BPEL_CAMB_DOMICILIOS.log
Errors during processing:
There are no web service definitions to be generated.(SBL-EAI-04340)
Following are warnings generated in the process:
Service 'BPEL_CAMB_DOMICILIOS' can not be imported, because none of its ports could be imported.(SBL-EAI-04333)
Port 'BPEL_CAMB_DOMICILIOSPort' can not be imported. PortType 'BPEL_CAMB_DOMICILIOS' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'process' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'SBLCambioDomiciliosRequest' in 'http://www.cablemas.com/SBLCambioDomicilios'(SBL-EAI-08009)
Cannot find schema with targetNamespace: 'http://www.server.com/SBLCambioDomicilios'(SBL-EAI-09002)
.(SBL-EAI-04331)
Cause
Increasing the Tools Client log the additional information was collected.
a) Instructions to increase Tools Client log.
You have to set the following System Environment Variables:
SIEBEL_LOG_EVENTS=5
To set up environment variables perform the following steps:
Start > Settings > Control Panel > System.
Click on the Advanced tab and then click on the Environment Variables button.
Under the System variables view, click the New button and add the variable names and values mentioned above. Click the Ok button when finished. After that, you have to restart the Tools Client.
The detailed siebdev.log file should be generated.
b) In the siebdev.log file
WebSvcDesign XSDImpWarning 2 000000024a520670:0 2009-07-06 17:53:49 [0] Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=file:///C:\Shared\WSDL2\INT-210-BPEL-CAMB_DOMICILIOS.xsd(SBL-EAI-00247) (IDS_XMLCNV_ERR_FTLPARSE)
ObjMgrLog Error 1 000000024a520670:0 2009-07-06 17:53:49 (xsdcontext.cpp (693)) SBL-EAI-09004: XML Schema document located at 'INT-210-BPEL-CAMB_DOMICILIOS.xsd' could not be parsed.
ObjMgrLog Error 1 000000024a520670:0 2009-07-06 17:53:49 (wsimpwiz.cpp (2163)) SBL-EAI-04331: PortType 'BPEL_CAMB_DOMICILIOS' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'process' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'SBLCambioDomiciliosRequest' in 'http://www.server.com/SBLCambioDomicilios'(SBL-EAI-08009)
Cannot find schema with targetNamespace: 'http://www.server.com/SBLCambioDomicilios'(SBL-EAI-09002)
c) As the error log indicated the WSDL file points to an xsd file that could not be imported because it does not exist in the same directory where the WSDL file is located.
The following import instruction in the WSDL file triggers this event.
<import namespace="http://www.server.com/SBLCambioDomicilios" schemaLocation="INT-210-BPEL-CAMB_DOMICILIOS.xsd"/>
Solution
Please move the XSD file to the same directory where the WSDL file is located.Best Regards
Oracle Support
References
NOTE:1076251.1 - Master Note for Siebel Web ServicesApplies to:
Siebel CRM Integration Pack for Oracle Order Management: Order to Cash - Version: 2.4 to 2.4 - Release: 2.4 to 2.4Information in this document applies to any platform.
Siebel CRM Integration Pack for Oracle Order Management - Version: 2.4 to 2.4
Purpose
This note provides access to Known Issues and Workarounds for Siebel CRM Integration Pack for Oracle Order Management: Order to Cash 2.4.Known Issues and Workarounds for Siebel CRM Integration Pack for Oracle Order Management: Order to Cash 2.4
Bug Number |
PIP Component Impacted |
Participating Application(s) Impacted |
Known Issue Description |
Workaround |
| Order Management | Siebel | SIEBEL ERROR ON COPYING SUBMITTED COMPLEX ORDER There is an error message in Siebel when trying to copy a submitted order for a configured product:"Fatal Error in XML Parser at line 1, column 422: Invalid character (Unicode:0x0)(SBL-EAI-00247)(SBL-EXL-00151) |
The workaround steps are:
|
|
| 7031383 | Asset Management | AIA | INITIAL LOAD ERRORS WHEN VALUE OF QUANTITY FIELD IN EBIZ IS TOO LARGE The value of the Quantity field in Oracle Item Instance for certain records may be very large value (viz. E+29, in csi_asset_integration_v). ODI is unable to create a temporary table since this value exceeded the allowed limit for the target field. |
The fulfillment system may be marking the quantity very high (E+29) just to indicate very high levels, though physically this much quantity may not exist. Thus, the recommendation is before importing the data to Siebel, this significantly high number should be set to a number that can be put on the Siebel quantity attribute. In Siebel, the max value the Asset quantity field may hold is E+11. |
| 7115559 | Order Management | Siebel | DISPLAY OF INCLUDED ITEMS IN SIEBEL ORDER IS NOT CORRECT When an order with included items is updated in EBS, included items are synched to Siebel CRM. These included items are not displayed correctly in Siebel. It is appearing as a separate order line item in Siebel. It should be shown under the parent model/option class. |
There is no workaround available. |
| 7151408 | Order Management | AIA | ONLY HEADER LEVEL HOLD/RELEASE IS SUPPORTED In EBS you can apply mutiple holds at the order and header and line items. Only a single order header hold is supported out-of-the-box |
No workaround is required. |
| 7688344 | Order Management | AIA | FRIEGHT_TERMS_CODE HAS TO BE MAPPED INSTEAD OF When order is submitted to Oracle eBusiness Suite, mapping should be done to "FREIGHT_TERMS_CODE", instead of "FREIGHT_TERMS". |
The workaround steps are:
|
| 7828524 | Product Management | Siebel | BOM UPDATE - PARENT PRODUCT VERSION IS NOT GETTING UPDATED IN SIEBEL After syncing a multilevel BOM from PIM to Siebel, when user tries to update the BOM by adding additional components as a part of “Option class’, after syncing to siebel user is not able to create a new version for parent product. The expected behavior is New version should get created for parent product after updating option classes. |
There is no workaround available. |
| 7044029 | Product Management | Siebel | DELETION OF PRODUCT IN A BOM IN EBS NOT IN SYNC WITH SIEBEL For Complex Product/Item if an item from already existing BOM is deleted, and then sync is requested from Siebel. Upon sync, in the updated structure of the BOM in Siebel, the deleted Item is still present. |
No workaround is required. |
--- |
Payment Authorization | AIA | Payment Auth rejects payment with current month and year as card expiration date In the Payment Auth flow, the Expiration Month and Year for the Credit Card Expiry details is passed from Siebel. But since Ebiz requires a day of the month as well, the MM/YYYY date from Siebel is formatted to YYYY-MM-DD in Ebiz, where DD is set as '01' always to denote the first of the month. The issue with this approach is that the Credit Card will not be authenticated in cases where the current month/year is same as the expiry month/year and current date is beyond the 1st of the month. |
There is no workaround available. |
| 8257636 | Upgrade | AIA | UPGRADE FROM 2.2 TO 2.3: PIP VERSION NOT UPDATED IN DEPLOY.PROPERTIES As part of the O2C PIP Upgrade from 2.2 to 2.3 (released as part of O2C in AIA 2.3), once the upgrade completes, the PIP version in the deploy.properties file is not set to 2.3. This should be done manually for now. If this is not done, then further upgrades will not be possible for the PIP. There will not be any impact on the current PIP or the upgrade from 2.2 to 2.3 because of this. |
The steps for manual fix to overcome this issue, and enable upgrades from 2.3 to higher versions are:
|
| 8460643 | Order Management | AIA | FAULTED GETITEMVALIDATION ORGANIZATION EBIZADAPTER CONNECTION ERROR CODE The Order Status flow from Oracle EBS to Siebel fails. It is because the wsdl GetItemValidationOrganizationEbizAdapter.wsdl has a hardcoded value on the jca binding section: |
The workaround steps are:
|
| 8496685 | Customer Management | AIA | AIACONFIG PROPERTY NAME INCORRECTLY DEPLOYED FOR SYNCCONTACT SIEBEL REQ ABCSIMPL In the Edit_AIAServiceConf.xsl file for SyncContactSiebelReqABCSImpl service, the AIAConfig property name 'Contact.ProcessUpdateEventsOnly' is set based on whether O2C or MDM is being deployed. Currently, this property name is incorrectly set as 'Account.ProcessUpdateEventsOnly'. It should be set as "Contact.ProcessUpdateEventsOnly". |
The workaround steps are:
|
| 8452452 | Order Management | Oracle eBusiness Suite | ORDER HOLD STATUS NOT BEING SYNCHED TO SIEBEL When Credit Hold checkbox is checked in Oracle EBS form, the orders for that customer go on Credit hold. |
This has been in fixed in eBusiness Suite patch 8459502 |
| 8449618 | Order Management | AIA | UPDATE WITH ATLEAST TWO NEW LINE ITEMS NOT VISIBLE IN SIEBEL UI If an Order line is split into multiple lines (more than two), the new lines beyond second line do not show up in Siebel UI. |
The workaround is:
|
| 8406173 | Product Management | Oracle eBusiness Suite | UNABLE TO BULK LOAD PRODUCTS SINCE ITEM VALIDATION ORG IS NOT A ITEM MASTER ORG The view EGO_ITEM_SYNC_OP_V has join condition, that is prohibiting the correct records to returned. Earlier the validation org is same as Master-org, but the Validation org can be any organization. The join condition needs to be changed. |
This has been fixed in a Patch # 8441572. |
| 8403718 | Order Management | AIA | PAYMENT TYPE FIELD EMPTY FOR CREDIT CARD DETAILS ON SYNCHED ORDER Payment Type field in Ebiz Sales Order form (Others tab) should have "Credit Card" |
No workaround is required. |
| Bug Number | PIP Component Impacted | Participating Application(s) Impacted | Known Issue Description | Workaround |
| Date | Description |
|---|---|
| 13/05/09 | Initial posting. |
Applies to:
Siebel CRM - Version: 8.0.0.7 SIA [20426]Information in this document applies to any platform.
Symptoms
When a JMS Transport parameter 'Impersonate' is set to TRUE, you can run a workflow process with other user account than SADMIN according to eaiusername/eaipassword attibutes. But the Impersonate functionality causes the JMSReceiver processing incoming messages in different way and show the following results:(1) If the incoming message is UTF-16,
- Impersonate functionality works as expected.
(2) If the incoming message is UTF-8 and is sent as a binary message,
- Impersonate functionality works as expected.
(3) If the incoming message is UTF-8 and is sent as a text message,
- JMSReceiver shows the following error and the Impersonate functionality does not work.
-------------
SBL-EAI-00247: Fatal Error in XML Parser at line 1, column 40: Expected an element name
-------------
If Impersonate is not used, UTF-8 incoming message is processed with no problem even though it is sent ad a text message.
Cause
When Impersonate functionality is used, JMSReceiver has to analyze the incoming message to find eaiusername/eaipassword attributes in the message and it can not handle UTF-8 message if it's sent as a text message because text string in Siebel application is UTF-16. If Impersonate functionality is not used, JMSReceiver just passes the incoming message to a workflow process and no error occurs.Solution
When Impersonate parameter is true, please use UTF-16 if the incoming message is sent as a text message or configure the external system to send a UTF-8 message as a binary message.A enhancement request 12-204GKF9 was created so UTF-8 inbound message can be sent as a text message with Impertonate functionality.
No comments:
Post a Comment