ABAP Proxy or IDOC Adapter?

Hi all,
In my project, we are using 3 system(SAP R/3(ECC 6.0), Oracle and VAN). Data has to synchronize between these systems.
1. Oracle ->PI ->SAP R/3
Oracle system is sending Material master data to SAP R/3 ECC 6.0. At sender side I am using JDBC Adapter but at receiver side shall i go for IDOC Adpter or ABAP proxy? If I go for ABAP server proxy I need to create message type for material master in IR and then I have to write code in abap to insert MM data into tables in R/3. Please suggest which one will be better IDOC adpter or ABAP Proxy?
2.VAN->PI->SAP R/3
VAN is sending Invoice data to SAP R/3. At sender side I am using Seeburger Adapter. At receiver shall i go for IDOC Adpter or ABAP proxy?
3.SAP->PI->VAN
Sap is sending PO data to VAN. At sender side Shall i go for IDoc Adapter or ABAP proxy?
Please suggest me which one is better in all the scenarios.
How to decide which is better for the above scenarios?
Thanks In advance
Venkatesh

>
venkatesh bs wrote:
> Hi all,
>
> In my project, we are using 3 system(SAP R/3(ECC 6.0), Oracle and VAN). Data has to synchronize between these systems.
>
> 1. Oracle ->PI ->SAP R/3
> Oracle system is sending Material master data to SAP R/3 ECC 6.0. At sender side I am using JDBC Adapter but at receiver side shall i go for IDOC Adpter or ABAP proxy? If I go for ABAP server proxy I need to create message type for material master in IR and then I have to write code in abap to insert MM data into tables in R/3. Please suggest which one will be better IDOC adpter or ABAP Proxy?
>
> 2.VAN->PI->SAP R/3
>
> VAN is sending Invoice data to SAP R/3. At sender side I am using Seeburger Adapter. At receiver shall i go for IDOC Adpter or ABAP proxy?
>
> 3.SAP->PI->VAN
> Sap is sending PO data to VAN. At sender side Shall i go for IDoc Adapter or ABAP proxy?
> Please suggest me which one is better in all the scenarios.
> How to decide which is better for the above scenarios?
>
> Thanks In advance
>
> Venkatesh
Material Master - MATMAS
Invoice - INVOIC01
PO - ORDERS
wouldnt the above IDoc suit you?

Similar Messages

Error while invoking the ABAP Proxy via SOAP Adapter

Hi,
My scenario involves SOAP Client invoking a webservice hosted in PI which in turn invokes the ABAP Proxy asyncronously.
SOAP Client -> PI -> ECC (ABAP Proxy) . This works fine.
Next , I have exposed the ECC Service Interface as webservice using SOA Manager transaction. Now, once the service is created using SOAManager, i replaced the XI Adapter with SOAP Adapter and provided the target URL as the URL provided by the SOAManager.
SOAP Client -> PI -> ECC (ABAP Proxy via SOAP Adapter)
With this approach, i am encountering the below error message
2009-05-29 12:17:55 Error Adapter Framework caught exception: null
2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
Any ideas on the above errror message? Any pointers or inputs will be appreciated.
Thanks,
Vinayak Kamath

> 2009-05-29 12:17:55 Error Adapter Framework caught exception: null
> 2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
This is a generic error message which does not have any information about the error which has occurred.
Do you see any error messages in the SOAP client?
Regards
Stefan

How do ABAP Proxy and XI adapter work?

Hi everybody,
I have a general question about the ABAP proxy and XI adapter.
In order to use the ABAP proxy and XI adapter, I must configure the HTTP Destination between the R/3 system and the XI server. I must also maintain the SLD.
After several hours configurations with our administrator, it failed. At least the HTTP Destinations on both servers don't work correctly. We got always HTTP error message. But a scenario with an ABAP Receiver proxy works! It is really strange and laughable. We're very happy about that but don't know why and what happened. Today we tested the ABAP Sender proxy, it doesn't work.
So we decide to ask the XI experts in this forum to give us a general lessen about the ABAP proxy: how it works, why we should create the HTTP destinations, how do the destinations work and so on.
Thanks a lot in advance!
With best regards
Xiang

Hi
Once you create the interface in XI, you generate the proxies on your R3 system.
Client Proxies -->
This is done for outbound interfaces. You generate the proxy and then write a report that fills in the proxy class with the data and pushes it to XI.
Server proxies -->
Generated for inbound interfaces. Generate the proxy and write the implementation for the exectue method that deals with the data sent from XI to the R3 system
Abap Proxy
ABAP Proxies in XI(Client Proxy)
Smarter Approach for coding ABAP Proxies
The specified item was not found.
ABAP Proxy - XML to ABAP Transformation
http://help.sap.com/saphelp_nw04/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
why we should create the HTTP destinations, how do the destinations work and so on.
we create http destiantio because in proxies , adapter is not use so who is goin to send the message to integration server ...by creating http destinatio we create integration engine which send messg to IS . then messg is routed .and all
error in HTTP to file scenario http to file
hope this help's you
Regard's,
Chetan Ahuja

ABAP Proxy Vs IDOC

What are all the advantages ABAP Proxy has over an IDOC?
When to go for an ABAP Proxy?

Pete,
Proxy and Idoc:
IDOC : After recieving the strucutred data It processes it using a Function Module associated with it. If you have a standard Idoc for your requirement then you should go with Idoc only.
Proxy : Proxy is a structure where there is no processing function module associated. You need to explicitly write the Business Logic/Call the subroutines here
This is my absolutely my view. Another guy has his own response. So first go through your requirements and then you can decide for what to go.
Also go through this urls which may help you:
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
RFC VS PROXY
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
Re: IDOC and RFC
Re: Proxy Vs IDOC
---Satish

ABAP Proxy without SOAP adapter in PI7.3

Hi All,
We have dual stack implementation of PI7.3 but we do not wish to use the SOAP adapter for configuring an ABAP proxy scenario.
Is this possible? Is the Javastack only configuration in NW Admin available for use in dual stack implementation also?
Thanks and Regards,
Diptee

Hi All,
So it essetially means that only the below 2 options are available for ABAP proxy scenarios in PI7.3 for a ABAP+Javastack installation
- use of SOAP adapter over XI protocol
- use of conventional proxy configuration of the ABAP Integration Server
And the only Javastack config cannot be used for a dual stack implementation.
Please confirm if above is correct.
Regards,
Diptee
Edited by: diptee s on Sep 21, 2011 4:48 PM

Call ABAP-Proxy with SOAP adapter?

Hi all,
for a PI7.1-scenario I would like to use the Lookup-API in mapping. As I know I can use either RFC or SOAP channels, however I would rather call an ABAP-Proxy in my backend system instead.
So my question is: Is it technically possible to use the SOAP-adapter to call an ABAP-Proxy?
Your help would be appreciated, best regards
David

Hi Stefan,
Interesting answer here and one that has got me curious. Hope you can help.
1. When you say it is going to be possible to call a ABAP proxy using a UDF in the mapping of XI ( Lookup ), would it be using the WS Adapter of PI 7.1?
2. If 1 is yes, is there a new API code to do this, or is it the same lookup code as used previously in XI 3.0 and PI 7.0 Days?
3. If 1 is no, can you explain maybe a little more on how this would be possible using the standard SOAP adapter of XI?
Thanks a bunch.
Regards
Bhavesh

Pipeline error for abap proxy to IDoc scenario

hi experts,
i am getting the following system error in moni for my proxy to idoc scenario.
In error it shows :
"Receiver service cannot be converted into an ALE logical system"
but i have checked adapter specific attributes of both receiver
and sender sys and they both have logical systems ( SO this is not the problem)
TRACE
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
pls suggest .
Appropriate points will be awarded

Hi,
Copy the payload from moni and test the mapping.
The error may be due to XML file generated by sender channel is not proper.
and also look at this blog
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Please reward points if it helps
Thanks
Vikranth

ABAP proxy - XI - IDOC

Hi,
I built a new interface: ECC ABAP proxy - XI - CRM IDOC and tested it in DEV systems(ECC, XI, CRM) - it works well. I transport it to QA systems(ECC, XI, CRM). Everything seems OK, but when I do Proxy test from ECC QA system, I don't see message in XI QA. I receive - Services Processed Without Error
This ECC QA client was copied from ECC PROD client.
What definition I have to check in ECC QA system?
Thank you, Natalia.

Hi,
to see where your message is going,
execute the transaction SXMB_ADM,
select Integrtion Engine Configuration and check the RFC details.
The role of business system should be application system
and below that you have the RFC destination for integration system.
Just check if this RFC destination is pointing to XI QA.
I think this solves your problem.
Regards
Pushkar Anand

RFC or IDOC or ABAP Proxy

Hi,
What is the best way(R3 Side) for standardization?
R3 <-> Legacy.
I've read all related article on sdn, but i am not still clear on which best way RFC or ABAP Proxy or IDOC in real life.
if you are, what is suggestion?
thanks
dennis

Ogawa,
There are advantages / disadvantages for RFC / Proxies / Idocs. So if I am in your position depending upon the requirement I will choose one. Some of the differences are:
RFC and Proxy:
RFC/BAPI has its own overhead of function call.
Proxies communicate with the XI server by means of native SOAP calls over HTTP .RFC does not, so you have to convert from SOAP to RFC calls and vice versa. So XML conversion is required.
ABAP Proxies uses Webservice and Http Protocols.
If you use ABAP Proxy , you can reduce the overhead calling the function again and again.
Proxy and Idoc:
IDOC : After recieving the strucutred data It processes it using a Function Module associated with it.
Proxy : Proxy is a structure where there is no processing function module associated. You need to explicitly write the Business Logic/Call the subroutines here
This is my absolutely my view. Another guy has his own response. So first go through your requirements and then you can decide for what to go.
Also go through this urls which may help you:
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
RFC VS PROXY
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
Re: IDOC and RFC
Re: Proxy Vs IDOC
---Satish

Wheh to use abap proxy and when to use idoc

Hi All,
Please provide some clarifications for the below points :
What is Sproxy?
2.     Why we are using Sproxy instead of Idocs
3.   When we are going Proxy ?
4.   What are the types of proxy ?
5.   How to Create to Proxy ?
6.   What the Difference between SProxy and Idocs
   7.   What is SOAP file? When we are using SOAP file ?
Thank you.
Regards,
Bharat

Hi Bharat,
You seem to have a range of Questions. I will try and answer as many as possible.
What is Sproxy?
SPROXY is a transaction [T-Code] on the SAP ECC/CRM etc side where you can see the objects designed in SAP PI ESR and develop its corresponding ABAP code. SPROXY T-Code displays the Service Interface. You can read more about it in the following site:
**************** - XI - ABAP Proxy communication
2.     Why we are using Sproxy instead of Idocs
For Certain implementations Standard IDocs may not be available and it is quite tedious to create a Z- IDoC and therefore it is advantageous to use Proxy. You can read more about this doubt in the following links:
Choosing to use IDOC standard or ABAP Proxy?
IDOC vs Proxy
ABAP Proxy Vs IDOC
3. When we are going Proxy ?
When there are no Standard IDocs available. Please refer above links to get an answer for this.
4.   What are the types of proxy ?
5.   How to Create to Proxy ?
Again the following link has the answers for both these questions:
**************** - XI - ABAP Proxy communication
6.   What the Difference between SProxy and Idocs
Difference is in the way the communication happens. Standard Idocs are already provided and you can use them directly while Proxy you will require to write the code on ECC side. You can refer the following link to understand more:
Advantage of ABAP proxy over BAPI
7. What is SOAP file? When we are using SOAP file ?
I have not heard of anything called SOAP file. SOAP is a protocol used for communication and you can send files as attachment in your SOAP to Any(file/idoc/Soap etc) or vice Versa Interfaces. Infact Proxy itself is SOAP based communication with XI 3.0 Protocol.
Please explore SCN to know more about the various scenarios. There are endless possibilities in SAP PI.
Hope this Helps.
Thanks & Regards,
Tejas Bisen

ABAP Proxy ABAP Mapping

Hi All,
The use of ABAP Proxy is nothing but the Adapterless implementation,as per my assumption.But is there any other reason for prefessing ABAP Proxy over the Adapter while the practical implenentation is done?
Also,for ABAP Mapping ,I have a qustion that when is ABAP Mapping preferred over other Mappings that is Graphical Mapping and Java Mapping while practical implementation?
Thanks and regards,
Amol

Hi Shweta,
To answer your first question, we prefer ABAP proxies over RFCs due to the reason that the communication happens directly between the Integration Engine of sender sap R/3 system and the IE of the XI system. It elimintes the need for Adapter Engine(On the sender side).
However, when there are standard IDOCs avaialble, then we use IDOCs instead of proxies due to the various other advantages of IDOCs like monitoring, reprocxesing etc.
But, in case the sender is not a SAP R/3 system, then obvious we can not use ABAP Proxy.
Refer this article to choose the best integration option amongst Proxy,RFC,Enterprise Services.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0e7ae66-be6d-2a10-d385-92e6e67dee10
Regarding your second question,
ABAP mapping is least preferred due to issues like Performance, Non-Portability (We cannot use the abap mapping in any other Open-source middleware).
The only time we go for it is if we have people with only ABAP skills..:)
Regards,
Ravi Kanth Talagana

BPM file to ABAP proxy

HI all
I´m developing a BPM, this has the following steps:
1º
Reciver Step: this is to read a file , comunication channel type file.
2º transformation Step: maps the MT of the file to a new MT
3º Send step: send syncronously the result of the the map.Using an ABAP proxy. XI adapter.
4ºSwitch step: compares de the value of the result of the syncronous call, with a constant.First branch Send Step to write a file
Second branch nothing.
My question is? Do i have to insert something before the switch. Because i cannot activate the BPM, In the SXI_CACHE i can see and error that says that the value that i´m using to compare the value it is not an object of the payload.
Any idea?
Many thanks
Noelia

Hi,
Last try...
salida_proxy./p1:MT_salidaproxy/row/valor = 0
In the condition editor:
When you do a f4 for the left operanfd text box:
The expression editor opens:
You need to click on the "Interface Variable" radio button and select your container salida_proxy and prove the correct xpath.
Make sure that the Type specified next to the xpath in the expression editor is String.
A f4 in the right operand text box opens a expression ediote, where:
You need to click on the constant radio button, and provide the constant 0.
Again make sure that the xsd trype is String.
In case all this has been done perfectly, then try deleting the switch and recreating it again. You never know, this might do the trick!
Regards,
Smitha.
Message was edited by:
Smitha Rao

Abap proxy for 2 PI server with 1 ERP server

Hi expert,
I have 2 production PI server that require abap proxy and RFC adapter communication with 1 production ERP server. In the ERP server sxmb_adm integration server configuration only 1 rfc destination that possible but i have 2 PI server. Is that anyway to set 2 rfc destination?
Thanks..

Hi
If you want to connect by proxies, then it will not be possible to connect 1 ECC to 2 PI systems.
Pls check replies from Mark Smyth & Amir from the following thread.
XI and PI
Regards
Abhijit

IDOC to abap proxy- Receiver Service Cannot be converted into ALE logical

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

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" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<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="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="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<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="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="Timestamp">2008-06-01T16:27:03Z 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 = DD2FF717DAE395F186DF001560A1C7CB</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</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">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<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="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<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">Loop 0000000001</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="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<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="Timestamp">2008-06-01T16:27:04Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <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="Inbound Framework" />
- 
- <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>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o3313" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1564</CONTID>
</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>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1738</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_DYNAMIC_CHECK />
<CX_AI_APPLICATION_FAULT />
- <CX_BBPX1_STD_MESSAGE_FAULT>
<AUTOMATIC_RETRY />
<CONTROLLER />
<NO_RETRY />
- <STANDARD>
<CONTROLLER />
<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="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<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" />
- 
</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

HTMLError in sxmb_moni, Idoc to ABAP Proxy Scenario

Hi Friends
I am trying to send data from R3 to SCMTM system(SAP System), via Idoc to ABAP Proxy Scenario ,I am getting the following under HTMLError in sxmb_moni
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Any ideas will be helpful.

Hi,
I faced similar problem. it was due to configuration problem in SXMB_ADM. corss check specific server confiration in SXMB_ADM.
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Regards,
Reyaz

ABAP Proxy or IDOC Adapter?

Similar Messages

Maybe you are looking for