XI protocol error occurred in abap proxy scenario- plz

Scenario is asynchronous
Http -> XI ->R/3(abap server proxy)
sender: Through http client
receiver is abap server proxy
Repository objects:
Sender: sender_DT, sender_MT, sender_MI(outbound asynchronous)
Receiver: imported RFC from R/3 client 550, receiver_MI(which has message type refered to the imported RFC)
Interface mapping: source=sender_MI, receiver_MI.
Proxy generated on R/3 client 550 for receiver_MI.
Configuartion objects:
Sender: business service, no comm channel since http sender.
receiver: R/3 business system
Comm channel: receiver_cc type of XI.
transport protocol: http
message protocol : XI 3.0, since both XI and R/3 on webas 6.4
addressing type: URL
target host: diamond
service number: 8005
path: /sap/xi/engine?type=entry
Authentiction data:
user name: user22
passwrod; correct
logon client: 400 which is the same client I developed ll the design and config objects.
Recevr determinaion, interface determination and recevr agrrement looks fine.
The error iam getting is:
<?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="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">LOOP_IN_MESSAGE_ROUTING</SAP:Code>
<SAP:P1>is.05.diamond</SAP:P1>
<SAP:P2>IS</SAP:P2>
<SAP:P3>XI</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XI protocol error occurred</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Please reply , your help is appreciated.
Thanks
KK

Stefan thanks,
I tried as you suggesetd putting the info of R/3 for
server: diamond
port: 8005
client: 550
user id: user05
pwd: correct
But I get the below error, suggest me what permission should this userid have?
<?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">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><!DOCTYPE html PUBLIC"-//W3C//DTD HTML 4.01Transitional//EN"><html><head><title>Logon Error

Similar Messages

Configure XI adapter for abap proxy scenario- plz help

Hi,
Pleas help me in configureing the XI adpater in abap server proxy scenario, answer the one in bold in below
Scenario is asynchronous
Http -> XI ->R/3(abap server proxy)
sender: Through http client
receiver is abap server proxy
Repository objects:
Sender: sender_DT, sender_MT, sender_MI(outbound asynchronous)
Receiver: receiver_MI
Interface mapping: source=sender_MI, receiver_MI.
Proxy generated on R/3 client 550 for receiver_MI.
this proxy internally calls an RFC which inturn updates a table.
Configuartion objects:
Sender: business service, no comm channel since http sender.
receiver: R/3 business system
Comm channel: receiver_cc type of XI.
transport protocol: http
message protocol : XI 3.0, since both XI and R/3 on webas 6.4
addressing type: URL
target host: ??? where can I find this
service number: ?? where can I find this
path: /sap/xi/engine?type=entry i guess the path is correct for XI 3.0
My system details: XI - client 400, R/3 client 550.
Authentiction data:
user name: this user suppossed to be from R/3 or XI?,
passwrod; proper password
logon client: the client supposed to be of R/3 or XI?
Recevr determinaion, interface determination and recevr agrrement looks fine.
Please reply , your help is appreciated.
Thanks
KK

Hi,
>>>target host: ??? where can I find this
Your R/3 host number you can find System->Status
>>>service number: ?? where can I find this
You can find in SMICM in services
>>>user name: this user suppossed to be from R/3 or XI?,
passwrod; proper password
logon client: the client supposed to be of R/3 or XI?
R/3 logon details.
Thanks,
Prakash

FTP to ABAP Proxy Scenario - getting error CO_TXT_CHANNEL_PASSWORD_ERROR

We have transported PI and EP data from development server to respective production, every thing is running fine except the abap proxy scenarios i.e. PI reads file from ftp location and calls the abap proxy but we are getting following errors:
<?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="OUTBINDING">CO_TXT_CHANNEL_PASSWORD_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to read user password from communication channel of type Error when accessing the secure store (access ID = FD768D4A8772DB50E1000000AC10041E) Error while reading from the secure store: ERROR_UNKNOWN: Cannot find entry in secure store (SECSTORE,023)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any solution?
Please note that I have searched and applied solutions given on SDN forums but didn't get any success. So I am looking for new suggestions.
Regards,
Jawed Ali

Jawed ,
Please test the HTTP destination of your receiver comm channel.
Which is the RFC connection to your R3 system.
Transaction SM59 and check the logon parameter for the connection you are using.
Regards,

File to ABAP Proxy Scenario

Hi All,
I am doing File-to-ABAP Proxy Scenario, in the sender side side it is picking the file, but in sxmb_moni it is giving the error:
*<?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="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">DUPLICATE_DETECTED</SAP:Code>
<SAP:P1>4CFF4691EEE211DC85E30019D1522982</SAP:P1>
<SAP:P2>CENTRAL</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message ID 4CFF4691EEE211DC85E30019D1522982 already exists in called system (pipeline CENTRAL)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Can u plz tell me why this error is occurring and how we can resolve this error.
Thanks & Regards,
Vikas

Hi Vikas
make a dummy change and activate your object then make a full refresh
you can make it through in 3 ways
1) tcode SXI_CACHE
2) go to ID -> environment and make a full cache refresh
3) http://<host>:5<sys#>00/CPACache/refresh?mode=full Full CPA cache refresh
when you do the developement then these are stored in ABAP data dictionary table which can be refreshed by delta cache
while full cache will delete this temporary object and make this cahe into runtime
hope this will help you
thanks
sandeep
if helpful reward points

INTERNAL - AMF_ERROR in XML -- ABAP proxy scenario

Hi Experts,
Can any one help me to solve this following issue please, it is happening while I am executing the scenario between XML File to ABAP Proxy scenario.
<?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">AMF_ERROR</SAP:Code>
<SAP:P1>1</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error when processing message number 1 in package No object type found for the message. Check that the corresponding process is activated An exception has occurred.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>.
This XML message has got 5 Lines Header and more than 100 Lin Items, this kind of Header and Lin item message 3 to 4 in one XML, I am using multi mapping. Message mapping shows working fine, OM also shows working fine. BPM is splitting messages to send messages to ABAP Proxy on SNC 7.0. After I have done all with SDN experts support, still I am having the above issue. can any one experties might help to resolve this?
I will appreciate your support.
Thanks & Regards
San

Can you please explain the solution.
Regards,
Rashi

Issue in Iodc- abap proxy scenario

Hi all
I have a idoc to abap proxy scenario. The issue is ,
when we send the idoc to client A of target system, it works ifne.
But when we send the saem mesage to Client B, we find a error message in sxmb_moni of Target system. the mesage is Application_fault.
Is it because of any error in XI configuration or somethin else.

hi all
thanks for all your responses.
I forgot to mention that based on a particualr field value in the idoc , it will be routed to eihter Client 100 or 200 .
I gave the conditions in Receiver Determination.
Same Server Proxy is used in both the target business sytems.
I have done all the Configuration Steps ,( Created two separate business systems also )
Also I have checked wiht all the system settings to be made in the target system B.
When i trigger the idoc to Client 100, it goes to XI and then reaches Client 100 of System B
without any problem. I get the desired result from proxy code.
When i send the saem idoc to Client 200, it reaches the target system and routed to client 200. But getting this error message in
the Call Inbound PRoxy step. (from sxmb_moni)
<SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
Since it reaches the target system correctly, i guess there is nothing wrong in the XI configuration side.
But if its Application fault, how come the same data is processed successfully in one client whereas it thorws error in another.

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

Configure ABAP Proxy scenario in PI7.3

Hello Experts,
Can someone please let me know if we have somewhere step by step procedure to configure an ABAP Proxy scenario in PI7.3, I couldn't find How-to guide related to this on SDN.
Thanks a lot.
Best Regards,
Shweta

I dont know abt your installation whether you have java stack alone or both java stack and abap stack.
AAE or local processing:
You can do using soap adapter as transport protocol and message protocol as XI for proxy. This way you can use local processing using AAE. I dont see documents in SDN as of now. But it is pretty simple. Just follow the steps what I mentioned.
Classical processing or abap engine:
Still the same as previous versions.

ABAP proxy scenario file - PI7.1- ECC NO_MAPPINGPROGRAM_FOUND

Hello Experts,
I have ABAP proxy scenario file -> PI7.1->ECC . I am getting an error for communication between PI and ECC system. the error is NO_MAPPINGPROGRAM_FOUND and pointing to operation mapping in the software component.
What i found in TCODE SXMB_MONI is 2 adaptor call one from one below the other out of which one is in error.
Also when a file is passed from the file server to the SAP PI I see 2 entries in SXMB_MONI for the same Payload one from source system to target system and one from target system to source system ( ie. from business component as sender and ECC as receiver system and one entry for ECC system as receiver and business system for file as receiver ) is this how it should be
one more thing i would like to specify is that my service interface is Point to point enabled . Is it happening because of that
Request you help on urgent basics
BR Heth

Hi,
1. in PI, by hazard, your Service Interface (SI) does not the mode "synchronous"?
2. or does this SI was declared firstly with "synchronous" mode and the proxy generated with this mode, and then you decided to put "Asynchronous"... without to regenerate the proxy in ECC?
If it's the case, in ECC, select your SI, do a right-click and regenarete the proxy.
3. for the 2nd message (returned by ECC to PI), have you seen the Payload content and SOAP Header?
Could you please also check the Pipeline (e.g CENTRAL, CENTRAL_BACK) ?
4. In SXMB_MONI of ECC, how many messages have you: one ? or two ?
Regards
Mickael

Creation of package structure for ABAP proxy scenario

Hi All,
I have a doubt on package structure used for ABAP proxy scenario. What is the specific reason to create a four level package structure? Can some one please explain? Thanks in advance.
Regards,
Sudheer.

Hi Sudheer,
Can you pls clarify what do you mean by 'four level package structure' ?
Are you referring to the ABAP structures that get created during creating the proxy by SPROXY transaction ? These structures get automatically created. We simply have to write the code using these structures.
Or do you mean the 'package' which is mandatory to create a transportable ABAP object ? i.e. transport from Development to Staging and then Production.
Regards,

Error in synchronous( abap proxy to soap)scenario

Hi experts,
My scenario is synchronous abap proxy to sysnchronous soap. for proxy I am using business system name as ERDCLNT220 and soap business system name as BS_HRS_DEV
configuration steps are
1. only client proxy to soap scenario I have done.
communication channels: only receiver soap adapter. no proxy sender communication channel for client proxy.
Already we have RFC destination connection and connection type H for proxy to xi.
1.Is it required RFC destination connection for xi to server proxy.
2.Is it required receiver proxy communication channel for server proxy?.
i HAVE TESTED THIS INTERFACE. I am able to send the request. But I am not able to receive the response from soap webservice message .
error is:
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
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: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson. Setting message to status failed.
Kindly help me.
advance thanks
thanks and regards
elton
Edited by: eltonsaranya on May 9, 2011 10:27 AM

Your exception message shows problem at the webservice side.
Check the following:
a) you need two mappings one for proxy req to soap request and other soap response to proxy response
b) You need to create service interfaces both sender and receiver synchronous .
c) communication channel QOS is best effort for both sender and receiver
d) I dont see problem in soap configuration. Bcuz you are able to ping and while getting response from the method getPerson it fails.
f) See your SOAP response structure matches with WSDL provided.
g) You can also test outside PI.. I meant testing via soap client tool like SOAPUI for that web service. So that you know whether problem exists on the target system or not.
Hope that helps.

Error while usinjg the JDBC to ABAP Proxy Scenario

Hello Rocks,
This is my scenario like JDBC --- Pi --- ABAP Proxy
while i am given a sender side jdbc XSD structure is like this
VWENTITYAGGREMENT
Row             1-unbound occurence
      POOL_ID   0-1 occurence
      CUST_ID
      AGREEMENT
       PRODUCT_ID
        CONTRACT_TYPE
        CONTRACT_TYPE_DESCR
        AGRMNT_STATUS
        STATUS_DESCR
          EFFDT
         TERMINATION_DT
         ADD_DT
         ADD_TM
while i am writing a select query in Sender JDBC CC is like this
SELECT POOL_ID,CUST_ID,AGREEMENT,PRODUCT_ID,CONTRACT_TYPE,CONTRACT_TYPE_DESCR,AGRMNT_STATUS,STATUS_DESCR,EFFDT,TERMINATION_DT,ADD_DT,ADD_TM FROM vwEntityAgreement.
Here i am getting this Error message like this :
Error Description: Database-level error reported by JDBC driver while executing statement 'SELECT POOL_ID,CUST_ID,AGREEMENT,PRODUCT_ID,CONTRACT_TYPE,CONTRACT_TYPE_DESCR,AGRMNT_STATUS,STATUS_DESCR,EFFDT,TERMINATION_DT,ADD_DT,ADD_TM FROM vwEntityAgreement'. The JDBC driver returned the following error message: 'com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'POOL_ID'.'. For details, contact your database server vendor.
So please give me your valuable inputs !
Regards,
Ravi.

Invalid column name 'POOL_ID'.'. For details, contact your database server vendor.
Did you confirmed the name POOL_ID as suggested?
Why is the tablename different (check the case) in the query that you make and in the XSD structure that you mentioned......check if this is causing the problem.
Regards,
Abhishek.
Edited by: abhishek salvi on Jun 4, 2010 10:24 AM

Error handling in abap proxy

Hi,
In my scenario, I have written code in the execute_synchronous method of the abap proxy in ECC. I want to capture all possible errors that might occur here and for all of them i want to capture the message id and the text and send it out. what kind of possible errors/exceptions can occur and how to handle them. My proxy class simply selects data from multiple tables in ECC and returns the same.
thks

Hi,
for outbound proxies the error handling should be done within R3 itself and there is no need to send errors to XI or receiving system for that matter. You would want someone from R3 side to take a note of it.
For Inbound proxies, you will have to implement the Fault messages
Fault message types are designed for application-specific errors that occur on the inbound side and that are reported back to the sender or persisted in monitoring.
· In the synchronous case, when an application-specific error occurs on the inbound side, instead of sending a response message back to the sender, the application can send a fault message to handle the error.
· The fault message of the application for an asynchronous ABAP server proxy is persisted for monitoring. In the case asynchronous of Java server proxies, the fault message is part of a negative application acknowledgement (see Acknowledgments).
Application-specific means that the application on the inbound side triggers the error itself because, for example, the request message did not contain sufficient information.
For more information on the same.
http://help.sap.com/saphelp_nw04s/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
In your case, since you said that you are selecting data from some tables, the possibility is that an entry is not found in the DB tables you will have to simply populate the fault message data and raise an expection CX_FM. It also depends on what error handling requirements from the Business .
regards,
Advait.

Catch an error in inbound ABAP Proxy

Hi,
I'm using an ABAP Proxy to file->PI->ECC(proxy) scenario and I found an error in my sxi_monitor on ECC side:
<SAP:Stack>Error during proxy processing An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause</SAP:Stack>
I actually solved the error, but I still don't know how to pass to the MONI the message error catching the exception instead of that "standard" error that y pasted.
How can I get the exception error and then RAISE it to the MONI?
Edited by: Marshal on Jun 9, 2009 12:37 PM

Ok, I'm talking about PI 7.1, I'm not sure if it's the same for older versions:
1 - Create a Fault Message Type (with standard error data types that PI generates automatically when you create the Fault MT) and add it to your inbound Service Interface (or Message Interface in previous PI versions).
2 - Regenerate the proxy.
3 - Now in the proxy class method related to your SI there is an exception you have to possible kind of errors to catch, the 1st one is a short dump than you can catch with a TRY. CATCH. ENDTRY structure, the 2nd one is a situation that isn't a dump but you want the proxy to return an error.
3.1 - Catch Short dump code:
DATA: lo_cx_root TYPE REF TO CX_ROOT,
 l_pi_fault_data TYPE ZPI_EXCHANGE_FAULT_DATA. "Exception message
TRY.
***********YOUR PROXY CODE
CATCH cx_root INTO lo_cx_root.
* GET ERROR TEXT
 lo_cx_root->if_message~get_longtext(
 RECEIVING result = l_pi_fault_data-fault_text ).
* GENERATE ERROR THAT YOU WILL SEE ON SXI_MONITOR (IN ECC!!)
 RAISE EXCEPTION TYPE "YOUR_EXEPCTION_MESSAGE_TYPE"
 EXPORTING standard = l_pi_fault_data.
ENDTRY.
3.2 Raise an error when you found an error situation for example an error message after BAPI calll:
 DATA: lt_return TYPE STANDARD TABLE OF bapiret2.
* Call any BAPI function....always return bapiret2 table with messages
 CALL FUNCTION 'BAPI_XXXXX'
 TABLES lt_retun.
* Look for an Error message
 READ TABLE lt_return INTO lwa_return WITH KEY type = 'E'.
 IF sy-subrc = 0.
 CALL METHOD cl_proxy_fault=>raise
 EXPORTING
 exception_class_name = 'YOUR_EXCEPTION_MESSAGE_TYPE'
 bapireturn_tab = lt_return.
 ENDIF.
I hope it helps

[MESSAGE.GENERAL] How can take the actual error text for ABAP proxy error?

Hi...
I'm a ABAPer.
I got to create outbound abap proxy for synchronous server proxy and described below.
My problem is program can not catch the actual error message when occurred error during send data to XI.
The return message is just 'MESSAGE.GENERAL'.
But according to the XI part, 'Key error' is actual reason.
So... how can i take the actual error text like 'Key error'?
* Only MESSAGE.GENERAL is return message for all kind of errors.
Thanks.
Below----
TRY.
 CREATE OBJECT abap_proxy.
 CALL METHOD abap_proxy->execute_synchronous
 EXPORTING
 output = gs_out
 IMPORTING
 input = gs_in.
Exception Handling
 CATCH cx_ai_system_fault INTO go_sys_exception.
 g_sys_result = go_sys_exception->get_text( ).
 CATCH cx_ai_application_fault INTO go_app_exception.
 g_app_result = go_app_exception->get_text( ).
ENDTRY.
COMMIT WORK.
Return status 'D' is succeeded.
if gs_in-sales_group_rer_sap-xstat <> 'D'.
 WRITE:/ 'System Error Message :', g_sys_result.
 WRITE:/ 'Application Error Message :', g_app_result.
endif.
*--Result--
System Error Message : MESSAGE.GENERAL
Application Error Message :
Message was edited by: Miju cho
Message was edited by: Miju cho

Thanks guys, this was useful.
My scenario is for Asynchronous communication.
I guess Fault messages are used in case of Synchronous communication for handling application errors. So if there was something wrong at the JDBC end then I could use the fault messages.
Have i got this right?
I also came across this piece on Acknowledgements. But is says that they can be used with the following Receivers:
The following receivers support acknowledgments:
ABAP and Java proxies (XI 3.0 SP1 for the latter)
Integration processes
IDocs (note that IDocs only return acknowledgments when they have been configured using the ALE audit)
Receiver adapters support system acknowledgments but not application acknowledgments
My Receiver is JDBC. So I guess I cannot use acknowledgements either.
Hence, I need to know what I can do to replicate the system errors eg. failed server etc...so that I can get catch these errors during sending.
I'll tell you abt what happened earlier.
My XI server was down. I executed the code for the sender ABAP Proxy and it did not catch the error. In SXMB_MONI in the R/3 system, I could see the messages queued up. When the XI server started, the messages were transferred to XI.
I need to handle such errors...ie. If the server is down or message did not reach XI then my ABAP program that sends data via ABAP proxy needs to know that something went wrong.
Thanks and Regards,
Ashwin

XI protocol error occurred in abap proxy scenario- plz

Similar Messages

Maybe you are looking for