on 09-14-2015 1:04 PM
Hi.
I am working on production server getting this type of errors when I monitor in SXMB_MONI.Is it I need to check in RWB also?
what is the solution for this type of errors.
Help would be appreciated...
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText/>
<SAP:Stack>No receiver could be determined </SAP:Stack>
Regards,
Shaik
Hi,
Recently i had the same issue in one interface (SOAP-to-RFC, Synchronous) but in my case it was due to wrong payload content being sent by the sender system thus mapping was failing on runtime.
You can check the trace in message monitoring in SXMB_MONI to get the better idea. Also check Qos must be Exactly Once.
Regards,
Dipen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dipen,
Please find below the error am getting when I monitor in SXMB_MONI.
<SAP:Category>XIServer</SAP:Category><SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/>
<SAP:AdditionalText/><SAP:Stack>No receiver could be determined </SAP:Stack><SAP:Retry>M</SAP:Retry>
</SAP:Error>
Regards,
Shaik
In detail traced message.
<?xml version="1.0" encoding="UTF-8" standalone="true"?>
<!-- Receiver Determination -->
-<SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace type="T" level="1">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace><Trace type="T" level="1">Party normalization: sender </Trace><Trace type="T" level="1">Determining the sender agreement </Trace><Trace type="B" level="1" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"/>
<!-- ************************************ -->
<Trace type="T" level="1">XMB was called with URL /sap/xi/engine/?type=entry</Trace><Trace type="T" level="1">User = PIAPPLUSER</Trace><Trace type="T" level="1">Work Process ID: 4660</Trace><Trace type="T" level="1">Message ID = E55B6A7850278BF1A90F005056900033</Trace>-<Trace type="B" level="1" name="CL_XMS_MAIN-ENTER_XMS"><Trace type="T" level="1">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace><Trace type="T" level="1">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace><Trace type="B" level="1" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV"> </Trace><Trace type="T" level="1">system-ID = MPP</Trace><Trace type="T" level="1">client = 500</Trace><Trace type="T" level="1">language = E</Trace><Trace type="T" level="1">user = PIAPPLUSER</Trace><Trace type="Timestamp" level="1">2015-09-15T05:27:41Z INDIA </Trace><Trace type="T" level="1">ACL Check is performed </Trace><Trace type="T" level="1">XML validation is executed </Trace></Trace><Trace type="B" level="1" name="CL_XMS_MAIN-CALL_UC_EXECUTE"/>
<!-- ************************************ -->
<Trace type="T" level="1">PLNAME = CENTRAL</Trace><Trace type="T" level="1">QOS = EO</Trace>-<Trace type="B" level="1" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC"><Trace type="T" level="1">Queue name : XBTI0000</Trace><Trace type="T" level="1">Going to persist message </Trace></Trace><Trace type="T" level="1">Generated prefixed queue name = </Trace><Trace type="T" level="1">Schedule message in qRFC environment </Trace><Trace type="T" level="1">Setup qRFC Scheduler OK! </Trace><Trace type="B" level="1" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"/>
<!-- ************************************ -->
<Trace type="T" level="1">--start determination of sender interface action </Trace><Trace type="T" level="1">select interface MaterialStockUpdate_ECC_Out_Multi </Trace><Trace type="T" level="1">select interface namespace http://www..com/his/mm </Trace><Trace type="B" level="1" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE"> </Trace><Trace type="T" level="1">Work Process ID: 620</Trace><Trace type="T" level="1">Exception from packaging: No messages for constructing a package available.</Trace><Trace type="T" level="1">Continue single processing </Trace><Trace type="T" level="1">Starting async processing with pipeline CENTRAL</Trace><Trace type="T" level="1">system-ID = MPP</Trace><Trace type="T" level="1">client = 500</Trace><Trace type="T" level="1">language = E</Trace><Trace type="T" level="1">user = PIAPPLUSER</Trace><Trace type="Timestamp" level="1">2015-09-15T05:27:41Z INDIA </Trace><Trace type="B" level="1" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"/>
<!-- ************************************ -->
<Trace type="T" level="1">>>>PID delete old pid determination coding </Trace>-<Trace type="B" level="1" name="PLSRV_XML_VALIDATION_RQ_INB">-<Trace type="B" level="1" name="CL_XMS_MAIN-CALL_PLSRV">-<Trace type="B" level="1" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">-<Trace type="B" level="1" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV"><Trace type="T" level="1">Reading sender agreement </Trace><Trace type="T" level="1">Message does not contain a sender agreement </Trace><Trace type="T" level="1">Inbound validation by Integration Engine does not take place </Trace></Trace></Trace></Trace></Trace><Trace type="B" level="1" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST"> </Trace><Trace type="B" level="1" name="PLSRV_RECEIVER_DETERMINATION"/>
<!-- ************************************ -->
-<Trace type="B" level="1" name="CL_XMS_MAIN-CALL_PLSRV"><Trace type="B" level="1" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"/>
<!-- ************************************ -->
-<Trace type="B" level="1" name="CL_RD_PLSRV-ENTER_PLSRV"><Trace type="T" level="1">R E C E I V E R - D E T E R M I N A T I O N </Trace><Trace type="T" level="1"> Cache Content is up to date </Trace></Trace></Trace><Trace type="System_Error" level="1">Error exception return from pipeline processing! </Trace><Trace type="B" level="1" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"/>
<!-- ************************************ -->
</SAP:Trace>
Hello Shaik ,
Check if there are any routing conditions in your interface for determining the receiver in ID.
Also try cache refresh.
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Shaik,
Check your receiver determination, you may be configured wrong or missing.
Regards,
Viana.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shaik,
Check your integration directory configuration. This can be wrong. Check in your monitoring what is your sender party, sender service and sender interface. Then you can check in the integration directory if you have defined correctly the receiver for those parameters (pay attention the names are case sensitive).
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey,
The problem might be that your message is being sent to the Integration Engine, not towards the Advanced Adapter Engine. You need to create the configuration in SXMSIF and SXMB_ADM.
You can find the whole description in this document:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.