IDOC to abap proxy- Receiver Service Cannot be con...

Dear all,

I have idoc to abap proxy -

R3 to SRM scenario.

I am getting the error Receiver service cannot be converted to ale logical system.

I have check the receiver bs SRM_BS , adapter specific attributes ... im getting the logical system ( this is not the problem)

i am using receiver XI adapter

with XI 3.0 as protocol

and http destination with /sap/xi/engine?type = receiver

i can see the data in the moni of receiver SRM system but it shows a red flag

pls help

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (1)

can you check the RFC destination program ID and other stuff and ensure they are the same in XI too..

Thanks

Kiran

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi kiran,

i have checked all the RFC destinations ... seems OK

problem is in SRM moni .. sender service and sender interface are not visible.

trace ::::

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

- <!-- Call Inbound Proxy

-->

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

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

-->

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

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

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

-->

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

-->

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

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

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

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

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

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

-->

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

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

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

-->

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

<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>

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

<Trace level="1" type="T">Generated prefixed queue name = XBTR0003</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="T">----

</Trace>

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

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

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

</Trace>

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

-->

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

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

<Trace level="1" type="T">select interface namespace</Trace>

<Trace level="1" type="T">no interface found</Trace>

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

<Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In*</Trace>

<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement</Trace>;

<Trace level="1" type="T">no interface found</Trace>

<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>

<Trace level="1" type="T">Hence set action to DEL</Trace>

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

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

-->

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

</Trace>

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

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

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

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

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

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

</Trace>

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

-->

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

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

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

-->

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

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

-->

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

-->

- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">

- <asx:values>

<CX_ERROR href="#o3314" />

</asx:values>

- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">

- <cls:CX_SY_NO_HANDLER id="o3314">

- <CX_ROOT>

<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>

- <INTERNAL_SOURCE_POS>

</INTERNAL_SOURCE_POS>

</CX_ROOT>

<CX_NO_CHECK />

- <CX_SY_NO_HANDLER>

<CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>

</CX_SY_NO_HANDLER>

</cls:CX_SY_NO_HANDLER>

- <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o3313">

- <CX_ROOT>

<KERNEL_ERRID />

- <INTERNAL_SOURCE_POS>

</INTERNAL_SOURCE_POS>

</CX_ROOT>

<CX_DYNAMIC_CHECK />

<CX_AI_APPLICATION_FAULT />

- <CX_BBPX1_STD_MESSAGE_FAULT>

<AUTOMATIC_RETRY />

<NO_RETRY />

- <STANDARD>

<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA_SUPPLIER:089 -Unable to determine logical system of sender; check your data Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>

<FAULT_URL />

<FAULT_DETAIL />

</STANDARD>

</CX_BBPX1_STD_MESSAGE_FAULT>

</cls:CX_BBPX1_STD_MESSAGE_FAULT>

</asx:heap>

</asx:abap>

</Trace>

<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>

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

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

-->

</SAP:Trace>

fault message says the sender is not having logical sys...but my sender sys is showing logical system in adapter specific attributes

pls help

points will be awarded

1.Check out your all ALE config steps.

2. Check if the Logical System Name in R/3 in poper forrmat and exactly matches(including the case) the one defined in XI-SLD.

Hi,

Your trace indicates message coming into the receiver system but there is a problem with converting sender system to ALE logical system.

Try check in R3.

Logical System of the client ..It must be in a proper format <SID>CLNT<CLNTNUMBER>. The same system should be maintain in the SLD R3 Business System Definition.

Once it is done try to refresh the SLD Cache from ID.

Try to check in R3 adapter specific attributes. Just check push button update business system from SLD.

Try to check in the SLD the client is defined or not.

Regards,

Rao.Mallikarjuna

Ask a Question

Top Q&A Solution Author

User

Count