UpdateSalesOrderEbizReqABCSImpl Fails As Package XX_BPEL_GETSALESORDERLINESHIPP Is INVALID (Doc ID 1498622.1)

Last updated on MARCH 08, 2017

Applies to:

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

Symptoms

AIA PIP 3.1 - Order status update flow from EBiz to Siebel is failing as one of the adapter service ‘GetSalesOrderLineShippingDetailsEbizAdapter‘

Raw audit of UpdateSalesOrderEbizReqABCSImpl shows the following error

Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'GetSalesOrderLineShippingDetailsEbizAdapter' failed due to: Stored procedure invocation error.
Error while trying to prepare and execute the APPS.XX_BPEL_GETSALESORDERLINESHIPP.WSH_INTEGRATION$GET_DELIVERY_ API.
An error occurred while preparing and executing the APPS.XX_BPEL_GETSALESORDERLINESHIPP.WSH_INTEGRATION$GET_DELIVERY_ API. Cause: java.sql.SQLException: ORA-04063: package body "APPS.XX_BPEL_GETSALESORDERLINESHIPP" has errors
ORA-06508: PL/SQL: could not find program unit being called: "APPS.XX_BPEL_GETSALESORDERLINESHIPP"
ORA-06512: at line 1

Check to ensure that the API is defined in the database and that the parameters match the signature of the API. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-4063" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
".
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
ORA-04063: package body "APPS.XX_BPEL_GETSALESORDERLINESHIPP" has errors
ORA-06508: PL/SQL: could not find program unit being called: "APPS.XX_BPEL_GETSALESORDERLINESHIPP"
ORA-06512: at line 1

Cause

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