No receiver could be determined while doing SAP ECC Integraion with MDM 7.1

[Former Member]

Dear All,

Can you please help me to resolve the following issue.

We are doing SAP ECC Integration with MDM 7.1 by using MDM PI Adapter.

Source side we are processing MATMAS.MATMAS05 IDoc and Receiver side we are using MDM PI Adapter to Connect the MDM System.

I have checked the Configuration by using Test Configuration Wizard, it showing every thing fine there.

Is it because of any network connection issue at the Target system (MDM) side?

Plz check the error message for your reference;

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--

Receiver Determination

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<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>

Thanks

Mahesh

Edited by: Mahesh Reddy on Dec 11, 2009 1:45 PM

[Former Member · Accepted solution]

Hi Mahesh,

If you created the Business System in the SLD, check whether it is having the Logical Name and it should be the in ID Business System --> Adapter Specific Identifiers.

If it matches with that value, then activate and do the full cache refresh by using the url

http://host:port/CPACache/refresh?mode=full

Regards

Sridhar Goli

[Former Member]

Hello Mahesh,

Check your receiver determination if the sender system is SAPDEV, check the adapter specific identifier in menu and verify it contains the correct logical system for the client you are using to trigger the IDocs.

Verify the service interface is MATMAS.MATMAS05

regards

[former_member200962]

Make some dummy changes to your existing receiver Determination --> Save --> Activate --> Check if cache updated properly.

The above error normally occurs in case:

1) Incorrect receiver name is maintained in RD

2) Cache is not updated.....this is the most common reason

3) Condition (if any in Receiver Determination) is not satisfied.

Regards,

Abhishek.

[Former Member]

Hi,

1.I have Maintained Correct Receiver Name in RD

2.Cache is also updated

3.There is no Condition Maintained in Receiver Determination.

4.Adapter specific Parameters also showing correctly.

THanks

Mahesh

Edited by: Mahesh Reddy on Dec 11, 2009 7:02 PM

[KennethEriksen]

Hi,

You can use the trace section from SXMB_MONI to verify what values PI use as sender system and interface during runtime. Then check this against your setup in Integration Directory. In some cases you would need to re-create the receiver determinations to make sure they are correct.

This error has nothing to do with network communication towards your MDM system, as the messages has not completed the pipeline in PI.

-Kenneth

[Former Member]

Hi,

Check if you have done conditional Receiver Determination and conditons are not getting true. Secondly make sure that you are using the correct name of receiver I mean it is case sensitive. So may be while creating the Receiver BS you made a mistake (very less chances of happening this but still make sure).

Regards,

Sarvesh

[rajasekhar_reddy14]

Hi Mahesh,

Check your receiver determination,its not correct,

Regards,

Raj

[Former Member]

Hi Raj & Sravesh,

Receiver Determinatin , Business System configured properly.

Plz Cehck this trace for reference;

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--

Receiver Determination

-->

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

<Trace level="1" type="B" name="IDX_INBOUND_XMB" />

- <!--

-->

<Trace level="1" type="T">User: </Trace>

<Trace level="1" type="T">Language: E</Trace>

<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>

<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>

<Trace level="1" type="T">Syntax-Check-Flag X</Trace>

<Trace level="1" type="T">IDoc-Tunnel-Flag X</Trace>

<Trace level="1" type="T">Queueid</Trace>

- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">

<Trace level="1" type="T">Docnum 0000000000356084</Trace>

<Trace level="1" type="T">Get the Metadata for port SAPDEV</Trace>

<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>

<Trace level="1" type="T">Make Syntax check of current IDoc</Trace>

</Trace>

<Trace level="1" type="T">Set Receiver Routing-object</Trace>

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-SET_IDOC" />

<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>

- <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA">

<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-ITAB_TO_BINARY" />

</Trace>

<Trace level="1" type="T">Message ID = 800B5DE06B881DDEB9C5671EAF3A8E8F</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">

<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>

<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>

<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />

<Trace level="1" type="T">system-ID = PID</Trace>

<Trace level="1" type="T">client = 555</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = </Trace>

<Trace level="1" type="Timestamp">2009-12-11T08:00:18Z CET</Trace>

<Trace level="1" type="T">ACL Check is performed</Trace>

<Trace level="1" type="T">XML validation is executed</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />

- <!--

-->

<Trace level="1" type="T">PLNAME = CENTRAL</Trace>

<Trace level="1" type="T">QOS = EO</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC">

<Trace level="1" type="T">Queue name : XBTI0001</Trace>

<Trace level="1" type="T">Going to persist message</Trace>

</Trace>

<Trace level="1" type="T">Generated prefixed queue name =</Trace>

<Trace level="1" type="T">Schedule message in qRFC environment</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!--

-->

<Trace level="1" type="T">--start determination of sender interface action</Trace>

<Trace level="1" type="T">select interface MATMAS.MATMAS05</Trace>

<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = PID</Trace>

<Trace level="1" type="T">client = 555</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = </Trace>

<Trace level="1" type="Timestamp">2009-12-11T08:00:18Z CET</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />

- <!--

-->

<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>

- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">

<Trace level="1" type="T">Reading sender agreement</Trace>

<Trace level="1" type="T">Message does not contain a sender agreement</Trace>

<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION" />

- <!--

-->

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

<Trace level="1" type="T">No Relation found - accept given Receivers.</Trace>

</Trace>

</Trace>

<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!--

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />

- <!--

-->

<Trace level="1" type="T">Persisting message with status ManualRestart, version: 000</Trace>

<Trace level="1" type="T">Manual Retry Number 1</Trace>

<Trace level="1" type="T">Log Number 002</Trace>

<Trace level="1" type="T">***************************************</Trace>

<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>

<Trace level="1" type="T">***************************************</Trace>

<Trace level="3" type="T">Manual Restart: increase Tracelevel to 3</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!--

-->

<Trace level="3" type="T">Persisting message Status = 016</Trace>

<Trace level="3" type="T">Message version 002</Trace>

<Trace level="3" type="T">Pipeline CENTRAL</Trace>

<Trace level="1" type="T">--start determination of sender interface action</Trace>

<Trace level="1" type="T">select interface MATMAS.MATMAS05</Trace>

<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">

<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>

<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>

</Trace>

<Trace level="3" type="T">message version successfully read from persist version= 002</Trace>

<Trace level="2" type="T">Increment log sequence to 003</Trace>

<Trace level="3" type="T">##### DG: 0</Trace>

<Trace level="3" type="T">##### TO: 3</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="3" type="T">system-ID = PID</Trace>

<Trace level="3" type="T">client = 555</Trace>

<Trace level="3" type="T">language = E</Trace>

<Trace level="3" type="T">user = </Trace>

<Trace level="1" type="Timestamp">2009-12-11T08:04:20Z CET</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />

- <!--

-->

<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>

<Trace level="3" type="T">Pipeline-Elements for pipeline SAP_CENTRAL</Trace>

<Trace level="3" type="T">0001 PLSRV_XML_VALIDATION_RQ_INB</Trace>

<Trace level="3" type="T">0002 PLSRV_RECEIVER_DETERMINATION</Trace>

<Trace level="3" type="T">0003 PLSRV_INTERFACE_DETERMINATION</Trace>

<Trace level="3" type="T">0004 PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>

<Trace level="3" type="T">0005 PLSRV_MAPPING_REQUEST</Trace>

<Trace level="3" type="T">0006 PLSRV_OUTBOUND_BINDING</Trace>

<Trace level="3" type="T">0007 PLSRV_XML_VALIDATION_RQ_OUT</Trace>

<Trace level="3" type="T">0008 PLSRV_CALL_ADAPTER</Trace>

<Trace level="3" type="T">0009 PLSRV_XML_VALIDATION_RS_INB</Trace>

<Trace level="3" type="T">0010 PLSRV_MAPPING_RESPONSE</Trace>

<Trace level="3" type="T">0011 PLSRV_XML_VALIDATION_RS_OUT</Trace>

<Trace level="1" type="Timestamp">2009-12-11T08:04:20Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>

- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">

<Trace level="1" type="Timestamp">2009-12-11T08:04:20Z CET Start of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

<Trace level="3" type="T">Calling pipeline service: PLSRV_XML_VALIDATION_RQ_INB</Trace>

<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>

<Trace level="3" type="T">PLSRVTYPE =</Trace>

<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>

<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_VALIDATION</Trace>

<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>

<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>

<Trace level="3" type="T" />

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />

- <!--

-->

- <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">

<Trace level="3" type="T">Pipeline Service = PLSRV_XML_VALIDATION_RQ_INB</Trace>

<Trace level="3" type="T">Skip Inbound Validation =</Trace>

<Trace level="3" type="T">Skip Outbound Validation =</Trace>

<Trace level="3" type="T">Area = XML_VALIDATION_INB</Trace>

<Trace level="1" type="T">Reading sender agreement</Trace>

<Trace level="1" type="T">Message does not contain a sender agreement</Trace>

<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="Timestamp">2009-12-11T08:04:20Z CET End of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>

</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">

<Trace level="3" type="T">No persisting of message after plsrv call, because of config</Trace>

</Trace>

<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION" />

- <!--

-->

<Trace level="1" type="Timestamp">2009-12-11T08:04:20Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>

<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>

<Trace level="3" type="T">PLSRVTYPE =</Trace>

<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>

<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>

<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>

<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>

<Trace level="3" type="T" />

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />

- <!--

-->

- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

<Trace level="2" type="T">Start without given receiver</Trace>

<Trace level="2" type="T">Using Receiver Determination 00000000000000000000000000000000</Trace>

<Trace level="1" type="T">No Relation found - accept given Receivers.</Trace>

<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>

<Trace level="3" type="T">...create rule engine</Trace>

<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>

</Trace>

</Trace>

<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!--

-->

<Trace level="3" type="T">Persisting message Status = 014</Trace>

<Trace level="3" type="T">Message version 001</Trace>

<Trace level="3" type="T">Pipeline CENTRAL</Trace>

</SAP:Trace>

Thanks

Mahesh;

[Former Member]

Actually it seems a problem of adapter specific identifires, because this the case of IDOC and when we create a new business system then very often we forget to update the adapter specific identifiers.

So just confirm it once.

Regards,

Sarvesh