Receiver

[Former Member]

I have a prob;em with my receiver identification...

I have an RFC to RFC scenario.

In my design I imported first from the sender system the sender RFC structure then I changed the parameters for import in my swcv so that I could import my target rfc structure from the receiver system... This shouldnt be a problem right?

OK so then I did all of my mapping etc...

NOW in thhe Integration directory I configured my scenario... Where I think the problem lies is within the systems...

I specified a sender R/3 system no problem.... Then when I went to define my target system which is actually the abap stack of the XI we are using no system was available....

I think this could be because XI is defined as an integration server is that right?

Well instead I defined a business service and had an RFC comm channel in here.

So the problem is that in SXMB_MONI it keeps failing at the Receiver Identification step but all the other configuration is correct...

Does this have something to do with me trying to call the XI abap stack through an RFC adapter and on top of that I have defined it as a business service... Could this be an issue?

Is there a way to use the integration server as a business system?

Can you have an RFC call to the abap stack of XI...

Why is no receiver being found?

[Former Member]

But if the function module is getting into the pipeline then it must be XI as someone just pointed out....

That is why I asked if the Function Module could be the reason for the receiver identification step faiuling and I was told no way.... So why should I check the function module.

In my scenario I just configured it again and it still doesnt work but I know my XI configuration must be coirrect...

By the way in SXMB_MONI i get 2 messages each time I execute the function module on the r/3 system.....

[Former Member]

their is nolinek between you fucntin module and XI.

reciver determination it failing because your reciver system details are not configure properly. I am not sure who you configured XI Abap stack correctly to get the Business System

Regards

Sreeram.G.Reddy

[Former Member]

INTEGRATION_DIRECTORY_HMI whether this RFC configured or not in your system

Regards

Sreeram.G.reddy

[Former Member]

i dont follow... what do you mean are not working because the receiver system details are not configured properly.... What do I need to do in the XI Abap stack?

I though nothing needs to be done in XI abap stack for RFC's?

[Former Member]

this is configured in the xi ABAP STACK... It is there I just checked...

I dont know whether it is configured correctly though...

Any major things that should be present?

Message was edited by:

SAP XI

[bhavesh_kantilal]

Hi,

INTEGRATION_DIRECTORY_HMI is a HTTP connection maintained in SM59.

This is used to refresh the cache and get data from the SLD during Runtime.

Looks like this Connection is not working as expected.

Go to Sm59 --> and try a Test Connection, If the Connection is working fine then you will have a HTTP response code of 500.

if you get someother value, then you wil need to lookinto this guide and check your cache status,

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a7930...

Regards

Bhavesh

[Former Member]

check the connection as ponted by bhavesh and let us know if works propely

Regards

Sreeram.G.Reddy

[Former Member]

Thanks Bhavesh... In XI ABAP Stack SM59.... when I test that connection I get the 500 response code?????

But the status text says that there is an internal server error??? I am really confused at how this could effect my receiver identification...

Could you please explain to me so I understand why this would effect it

[Former Member]

is it possible for an error in the code of a function module to cause an error in the pipeline like the receiver identification?

[Former Member]

No it is not possible . their is no link betwen two.

[Former Member]

Then I do not understand what is going on because I have alll of my mappings, sender agreements, receiver determinations configured correctly... so does it fail at receiver identification?

[prabhu_s2]

any logical eros then yes. if not no way

[prabhu_s2]

just take the help of abaper and debug the f/n mod. this will give u an idea of whats goin wrong

[Former Member]

No need to worry thats fun wroking with XI what is the error you are getting in SXMB_MONI paste here we will help you.

Regards

Sreeram.G.Reddy

[Former Member]

for the first message I get

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

- <!-- Receiver Identification

-->

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

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="XICACHE">UPDATE</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>Error when reading HTTP destination: INTEGRATION_DIRECTORY_HMI.</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error while refreshing the XI runtime cache</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

and for the second message I get

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

- <!-- Receiver Identification

-->

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

- <SOAP:Header>

- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">

<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>

<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>

<SAP:MessageId>BE8433F0-C7FD-11DB-C6AE-00306E0359E9</SAP:MessageId>

<SAP:TimeSent>2007-03-01T14:04:17Z</SAP:TimeSent>

- <SAP:Sender>

<SAP:Service>MEA</SAP:Service>

<SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">Z_ALERT_NOTIFICATION</SAP:Interface>

</SAP:Sender>

- <SAP:Receiver>

<SAP:Party agency="" scheme="" />

<SAP:Service />

<SAP:Interface namespace="" />

</SAP:Receiver>

<SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">Z_ALERT_NOTIFICATION</SAP:Interface>

</SAP:Main>

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

<SAP:QualityOfService>BestEffort</SAP:QualityOfService>

</SAP:ReliableMessaging>

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

- <SAP:Hop timeStamp="2007-03-01T14:04:17Z" wasRead="false">

<SAP:Engine type="AE">af.mxa.mxavie0</SAP:Engine>

<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>

<SAP:MessageId>BE8433F0-C7FD-11DB-C6AE-00306E0359E9</SAP:MessageId>

<SAP:Info />

</SAP:Hop>

- <SAP:Hop timeStamp="2007-03-01T14:04:22Z" wasRead="false">

<SAP:Engine type="IS">is.68.mxavie0</SAP:Engine>

<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>

<SAP:MessageId>BE8433F0-C7FD-11DB-C6AE-00306E0359E9</SAP:MessageId>

<SAP:Info>3.0</SAP:Info>

</SAP:Hop>

</SAP:HopList>

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

<SAP:Date>20070301</SAP:Date>

<SAP:Time>150422</SAP:Time>

<SAP:Host>mxavie0</SAP:Host>

<SAP:SystemId>MXA</SAP:SystemId>

<SAP:SystemNr>68</SAP:SystemNr>

<SAP:OS>HP-UX</SAP:OS>

<SAP:DB>ORACLE</SAP:DB>

<SAP:Language />

<SAP:ProcStatus>023</SAP:ProcStatus>

<SAP:AdapterStatus>000</SAP:AdapterStatus>

<SAP:User>XIAFUSER</SAP:User>

<SAP:TraceLevel>3</SAP:TraceLevel>

<SAP:Logging>1</SAP:Logging>

<SAP:LogSeqNbr>001</SAP:LogSeqNbr>

<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>

<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>

<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>

<SAP:PipelineElementId>5BC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>

<SAP:PipelineService>PLSRV_RECEIVER_DETERMINATION</SAP:PipelineService>

<SAP:QIdInternal />

<SAP:CommitActor>X</SAP:CommitActor>

<SAP:SplitNumber>0</SAP:SplitNumber>

<SAP:NumberOfRetries>0</SAP:NumberOfRetries>

<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>

<SAP:TypeOfEngine client="001">CENTRAL</SAP:TypeOfEngine>

<SAP:PlsrvExceptionCode />

<SAP:EOReferenceRuntime type="TID" />

<SAP:EOReferenceInbound type="TID" />

<SAP:EOReferenceOutbound type="TID" />

<SAP:MessageSizePayload>172</SAP:MessageSizePayload>

<SAP:MessageSizeTotal>2651</SAP:MessageSizeTotal>

<SAP:PayloadSizeRequest>172</SAP:PayloadSizeRequest>

<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>

<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>

<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>

<SAP:Reorganization>INI</SAP:Reorganization>

<SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>

<SAP:InterfaceAction>INIT</SAP:InterfaceAction>

<SAP:RandomNumber>51</SAP:RandomNumber>

<SAP:AckStatus>000</SAP:AckStatus>

<SAP:SkipReceiverDetermination />

<SAP:Sender_Agreement_GUID>7C15167B1A303C8484A5B1DF5A95FC07</SAP:Sender_Agreement_GUID>

</SAP:RunTime>

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

- <SAP:RunTimeItem>

<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>

<SAP:Timestamp type="begin" host="mxavie0">20070301140421.994431</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>

<SAP:Timestamp type="end" host="mxavie0">20070301140422.049873</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>

<SAP:Timestamp type="begin" host="mxavie0">20070301140422.051332</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>

<SAP:Timestamp type="end" host="mxavie0">20070301140422.072875</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>

<SAP:Timestamp type="begin" host="mxavie0">20070301140422.19733</SAP:Timestamp>

</SAP:RunTimeItem>

</SAP:PerformanceHeader>

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

<SAP:TraceLevel>Information</SAP:TraceLevel>

<SAP:Logging>Off</SAP:Logging>

</SAP:Diagnostic>

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

<Trace level="1" type="T">Party normalization: sender</Trace>

<Trace level="1" type="T">Sender scheme external = XIParty</Trace>

<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>;

<Trace level="1" type="T">Sender party external =</Trace>

<Trace level="1" type="T">Sender party normalized =</Trace>

<Trace level="1" type="T">Party normalization: receiver</Trace>

<Trace level="1" type="T">Receiver scheme external = XIParty</Trace>

<Trace level="1" type="T">Receiver agency external = http://sap.com/xi/XI</Trace>;

<Trace level="1" type="T">Receiver party external =</Trace>

<Trace level="1" type="T">Receiver party normalized =</Trace>

<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />

- <!-- ************************************

-->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>

<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>

<Trace level="2" type="T">Host = mxavie0.eu.airbus.corp:8068</Trace>

<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>

<Trace level="2" type="T">Remote address = 152.9.114.111</Trace>

<Trace level="1" type="T">COMMIT is done by XMB !</Trace>

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

- <!-- ************************************

-->

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

- <!-- ************************************

-->

<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>

<Trace level="3" type="T">Getting type of XMB...</Trace>

<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />

<Trace level="2" type="T">XMB kind = CENTRAL</Trace>

<Trace level="3" type="T">Start pipeline found</Trace>

<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>

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

<Trace level="3" type="T">No triggers found. OK.</Trace>

</Trace>

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

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

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

<Trace level="1" type="T">XMB entry processing</Trace>

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

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

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

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

<Trace level="1" type="Timestamp">2007-03-01T14:04:22Z CET</Trace>

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

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

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

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

- <!-- ************************************

-->

<Trace level="1" type="T">Message-GUID = BE8433F0C7FD11DBC6AE00306E0359E9</Trace>

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

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

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

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

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

<Trace level="3" type="T">External PLID = CENTRAL</Trace>

<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>

</Trace>

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<Trace level="2" type="T">Persisting original message</Trace>

<Trace level="3" type="T">Message-Version = 000</Trace>

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

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

</Trace>

<Trace level="1" type="Timestamp">2007-03-01T14:04:22Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>

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

- <!-- ************************************

-->

<Trace level="1" type="Timestamp">2007-03-01T14:04:22Z 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" />

<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>

<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</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">FL_LOG =</Trace>

<Trace level="3" type="T">FL_DUMMY = 0</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>

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

- <!-- ************************************

-->

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

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

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

</SAP:Trace>

</SOAP:Header>

- <SOAP:Body>

- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">

- <SAP:Payload xlink:href="cid:payload-be8c9860c7fd11dbacb000306e0359e9@sap.com">

<SAP:Name>MainDocument</SAP:Name>

<SAP:Description />

<SAP:Type>Application</SAP:Type>

</SAP:Payload>

</SAP:Manifest>

</SOAP:Body>

</SOAP:Envelope>

[Former Member]

All of it seems correct...

when I go to the function module where I execute in the sender system i get the following message

"The current abap had to be termintaed because one of the statements could not be executed.

The error occurred in an RFC call to another system"

This sounds like its my function modules issue... But then why is it gettting into XI in the first place and failing there?

[Former Member]

Hi,

in SLD, you will have a TS for your XI system...create a BS for it with type WebAsABAP.........

Now in receiver determination, give this BS as your receiver system.....now again reprocess your msg in SXMB_MONI......

go to SE37 in XI....take your function module......go to test it......take the input data of your RFC msg......Now see if your RFC is getting executed properly.

Thanks,

Rajeev Gupta

Message was edited by:

RAJEEV GUPTA

[Former Member]

im not an abaper Rajeev I dont understand what you are asking me to do?

[prabhu_s2]

u may need to take the help of an abbaper to check this kinda error. can u recheck by generating and activating the f/n module from the transaction code se37

[Former Member]

Hi,

Then ask an ABAPer to test your Function Module in SE37. See my above posting again.

Thanks,

Rajeev Gupta

[Former Member]

In my design I imported first from the sender system the sender RFC structure then I changed the parameters for import in my swcv so that I could import my target rfc structure from the receiver system... This shouldnt be a problem right?

Should not be a problem.

you can use XI ABAP stack as business service not an issuse but I am not sure

whether your receving XI stack can accomdate the data sentfrom R/3.

Regards

Sreeram.G.Reddy

[bhavesh_kantilal]

><i>In my design I imported first from the sender system the sender RFC structure then I changed the parameters for import in my swcv so that I could import my target rfc structure from the receiver system... This shouldnt be a problem right?</i>

Wouldnt be a problem.

><i>Does this have something to do with me trying to call the XI abap stack through an RFC adapter and on top of that I have defined it as a business service... Could this be an issue?</i>

Not at all. I have called a RFC residing on XI itself and I used a Business Service in that case as well.

Make sure that the Receievr Determination is correct.

Loon into your message in SXMB_MONI and see what the vakues for Sender Interface, Sender Service and Sender Namespace are. is this the values for which you have created the Receiver Determiantion.

Regards

Bhavesh