Resolution:
Description:
============
SAP Adapter throws AER3-950012 exception like following:

Error [RequestResponseInvocation] AER3-950012 Request Response Invocation error. Request Response Invocation service ZSD_PRI_MODELN_GET_PRICEClient with subject ABT.AES_E01.ZSD_PRI_MODELN_GET_PRICEClient received error while processing reply message. Error Unexpected reply received: tracking=#-0Y--C--GvnRgEuc-/400ic3I-k7Y#SAPAdapter.AES_E01ZSD_PRI_MODELN_GET_PRICE#


Environment:
===========
SAP Adapter 5.x and 6.x


Symptoms:
========
Request Response Invocation service is used in SAP Adapter configuration. When BW sends reply message to the adapter, the adapter throws an AER3-950012 exception like following:

Error [RequestResponseInvocation] AER3-950012 Request Response Invocation error. Request Response Invocation service ZSD_PRI_MODELN_GET_PRICEClient with subject ABT.AES_E01.ZSD_PRI_MODELN_GET_PRICEClient received error while processing reply message. Error Unexpected reply received: tracking=#-0Y--C--GvnRgEuc-/400ic3I-k7Y#SAPAdapter.AES_E01ZSD_PRI_MODELN_GET_PRICE#


Cause:
=====
Usually the error “ER3-950012 Request Response Invocation error… Error Unexpected reply received” occurs when a message from BW doesn’t match the message schema expected by the SAP Adapter. This mismatch may be in terms of structure of the reply message or data type mismatch of individual elements in the structure.


Resolution:
==========
Refresh or recreate the BW process, check the related adapter activities in the BW process to assure the message sent to the adapter comply with the adapter message schema.

For TIBCO ActiveMatrix (R) Adapter for SAP, how to resolve the issue that an AER3-950012 exception occurs when a message from TIBCO BusinessWorks doesn’t match the message schema?