Last updated on MAY 05, 2016
Applies to:Siebel CRM Integration Pack for Oracle Order Management: Order to Cash - Version 2.5 to 2.5 [Release 2.5]
Information in this document applies to any platform.
The O2C 2.5 implementation guide mentions about an outbound webservice on Siebel side called 'ProcessSalesOrderSiebelJMSProducerV2' to submit order to EBS which is missing in Siebel.
The QF1102 mentions about different webservice 'SWISubmitOrder_o2c' webservice and which is also used by 'SWISendOrder' workflow to send order to EBS. I tried importing 'ProcessSalesOrderSiebelJMSProducerV2' WSDL from AIA in Siebel and observed that this is also uses 'SWIOrderIO' IO which is used by 'SWISubmitOrder_o2c' webservice.
Also, I observed that 'SWISubmitOrder_02c' uses JMS binding while 'ProcessSalesOrderSiebelJMSProducerV2'' uses http transport. Please confirm which is the right webservice to be used for submitting the new Sales order to EBS, is it 'ProcessSalesOrderSiebelJMSProducerV2' or 'SWISubmitOrder_o2c'?.
Which is corresponding webservice which is being used on the AIA side for supporting the SWISubmitOrder_o2c Siebel outbound webservice.
The earlier Siebel service 'ProcessSalesOrderSiebelJMSProducerV2' was using the same service on the middleware to enqueue the message.
Also, please help with the documentation which explains the new flow.
What is the use of ''SWISubmitOrder_O2c' webservice?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms