O2C 2.5 : SWISubmitOrder, Created From Transfer Services Fails (Doc ID 1298715.1)

Last updated on MAY 05, 2016

Applies to:

Siebel CRM Integration Pack for Oracle Order Management: Order to Cash - Version 2.5 and later
Information in this document applies to any platform.

Goal


Transfer Service creates a quote and from there an order with 2 line items for the same service, one for Delete and the old service point ( address) and one with Add for the new service point.
This would normally result in the following:
The old asset will be set inactive and the new one will be added with different row id and asset integration id.
The Service Id would remain the same.
It has been verified with 8.1.1.3 and 7.8.2.7 so it's the intended behavior.

For this order following is reported:

The siebel web service SWISubmitOrder that sends the order to a JMS Queue is used.

On the AIA platform, this message is picked by the queue consumer and processed by the ProcessSalesOrderFulfillmentSiebelCommsReqABCSImpl service, which then orchestrates the order trough the billing system. The error between AIA and BRM happens on the service ProcessFulfillmentOrderBillingBRMCommsUpdateSubProcess.

0.0.0.1 /account 8300864 0 0.0.0.1 /product 162361 0 Barcelona OM Integration 39 file:/oracle/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_ProcessFulfillmentOrderBillingBRMCommsUpdateSubProcess_1.0_543de9ec8a93662e92d1abd0ba7cf1f8.tmp/BRMSubscriptionServiceRef.wsdl [ BRMSUBSCRIPTIONService_ptt::PCM_OP_SUBSCRIPTION_SET_PRODINFO(PCM_OP_SUBSCRIPTION_SET_PRODINFO_inputFlist,PCM_OP_SUBSCRIPTION_SET_PRODINFO_outputFlist) ] - WSIF JCA Execute of operation 'PCM_OP_SUBSCRIPTION_SET_PRODINFO' failed due to: Location=Unknown Resource for key:pin.loc.3 ErrMsg=ERR_NULL_PTR ErrStr=ERR_NULL_PTR Field=PIN_FLD_POID RecID=0 ; nested exception is: ORABPEL-00000 Location=Unknown Resource for key:pin.loc.3 ErrMsg=ERR_NULL_PTR ErrStr=ERR_NULL_PTR Field=PIN_FLD_POID RecID=0 BRM-ERR_NULL_PTR


About the error on the ProcessFulfillmentOrderBillingBRMCommsUpdateSubProcess, is caused because there is no value on <brm:OFFERING_OBJ/>. From AIA it was analysed and concluded that this happens because the asset integration id is not known by the AIA Xref.

Solution

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