ABAP Proxy - Error situation

I am developing inbound ABAP proxy. Using fault message and raise exception, I can safely fail the ABAP proxy without blocking the queues.
If I want to configure ALERT message to be sent to a email id in this scenario, how do I achieve this? Can this be done using Alert configuration? or do we need to use BPM? IF BPM is the only alternative, can anybody indicate the BPM steps?

Hi,
if you want to raise an alert from BPM
have a look at my weblog:
/people/michal.krawczyk2/blog/2005/03/13/alerts-with-variables-from-the-messages-payload-xi--updated
but if you want to send a mail from BPM
use mail adapter then you'll be able to
configure it very easily (even html mails):
/people/michal.krawczyk2/blog/2005/11/23/xi-html-e-mails-from-the-receiver-mail-adapter
- if you want you can also send mail from SAP
(when you catch the exception)
- you can also catch the excetpiton and
send the error to the XI and use the mail adapter from
there - without the BPM
there are many possibilities:)
Regards,
michal

Similar Messages

ABAP Proxy error during runtime but success for manuall test ?

Hi,
I got scenario using inbound ABAP proxy. The problem is when i test the inbound proxy manually, it was sucessfully, but then if i run directly from sender got problem :
Error during proxy processing An exception with the type CX_SY_DYN_CALL_ILLEGAL_TYPE occurred, but was neither handled locally, nor declared in a RAISING clause The function call of ZPSCD_CTRACCOMOBJECT_CREA failed; a field may have been assigned to the parameter ZCOM_COMPDHDR whose type is not compatible with this parameter
Please help
Regards

Fernand,
As stated in the exception, there is a compatibility issue between source and target fields, but without further details (msg definitions etc), we can't tell you exactly what's wrong ...
What's the ABAP type of ZCOM_COMPDHDR field in your RFC function module ?
Rgds
Chris
PS : also check the msg content to make sure generated field is compatible with the expected type (manual test was successful because you set it to the suitable value, whereas in "real" situation there is discrepancy)
Edited by: Christophe PFERTZEL on Apr 28, 2008 1:22 PM

ABAP Proxy: Error calling Proxy

Hi guys,
Here I am with another amazing mistake.....
After searching the forum, reading some suggestions, notes, I'm a little bit lost on how to figure out what is wrong...
I've created a receiver ABAP Proxy. XI should call this proxy and receive the consequent response.....
I've tested the ABAP Proxy, everything is working fine...I've encountered some errors but was able to bypass them... But this one is getting hard...I've found one or two similar threads, or with the same error description but I had no luck in overcoming the error....
So, what is the problem....:
When XI is calling the ABAP Proxy I get:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">EXCHANGE_PROFILE_ACCESS</SAP:Code>
<SAP:Stack>Error while reading exchange profile for system DEV and client 100</SAP:Stack>
I've searched the exchange profile but everything seems ok...
The user has all (and more) the authorizations needed....
Can you guys give me some hints? Or suggest any attempt....?

Kumar,
as I said before, in SPROXY i can test the interface with no errors....
In the Application System the sldcheck returns no errors and the RFC Destinations return no errors on the connection tests...
I really can't understand what this problem might be...
Problem solved
What was it? Well, I'm really not sure...Like most of the threads related to this topic it's quite an awkward problem....I've tested some RFC connections which were created, changed some parameters, restarted the system and voila....
Thanks
Message was edited by:
Gonçalo Mouro Vaz

[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

Abap Proxy Errors

Hi Experts,
My scenario R/3->XI(ABAP Proxy)--->SUS Systems
Getting the following error in SUS system.XI system it doesn't throw any error in moni.
I am new to proxy concepts.Also please let me know any related blogs or suggestions in this regards.
<?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>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>CL_BBPX1_SUSIV_IN</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
Sudhansu

Hi Behera,
Can you debug your proxy using this blog:
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/502a7f0e-e5d9-2910-5aa2-976a8ed8384f&overridelayout=true
Also please check few solutions given in this threads for the same issue:
Re: Messages waiting in SUS Moni
Re: ABAP Inbound Proxy Error !
Regards,
---Satish

FILE TO INBOUND ABAP PROXY - error

Hi,
Getting the following Error in FILE TO INBOUND ABAP PROXY which is updating a Database table in R/3.
Error:
com.sap.aii.utilxi.misc.api.BaseRuntimeException
thrown during application mapping
com/sap/xi/tf/_file2proxy_mm_: RuntimeException in
Message-Mapping transformatio~
How to rectify the error...
Ravi

Hi,
The error mentioned is indicating about the Message Mapping error.
I think you need to test your Message Mapping with test tab.
Here Goto SXMB_Moni and select the related message and double click on it.
It will show you the various steps in Message flow.
Take the Inbound Message and look for Payload in it. Open it in right side window and right click on it to see source code.
Copy it in Message Mapping and test it
Thanks
swarup

Client ABAP proxy error handling. Please help!

Hi Experts,
   I have following scenario:
   SAP ECC (ABAP Client Proxy) -> PI(XI)-->(SOAP) Third party web service System
   This is Asynchronous.
   What will happen when ABAP client Proxy in ECC sends data to PI but PI is down?
   Will the message be queued in ECC? Can the queued message be processed automatically when PI is UP later?
   Please help.
Thanks & Regards
Gopal

Hello Gopal,
Correct, it should be an automatic entry into the queue!
refer below for a detailed understanding!
/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies     XI: Reliable Messaging u2013 EOIO in ABAP Proxies
/people/krishna.moorthyp/blog/2005/12/23/monitoring-for-processed-xml-messages-in-abap-proxy     Monitoring for Processed XML messages in ABAP Proxy
Weblog to send Response from RFC to File in Asyn Mode Using Proxy [original link is broken]     Weblog to send Response from RFC to File in Asyn Mode Using Proxy
/people/michal.krawczyk2/blog/2009/06/20/pixi-abap-proxies-say-goodbye-to-executeasynchronous-method     PI/XI: ABAP Proxies say goodbye to Execute_Asynchronous method
/people/krishnakumar.ramamoorthy3/blog/2008/11/02/error-handling-framework-for-abap-proxies--part-1     Error handling framework for ABAP proxies - Part 1
/people/krishnakumar.ramamoorthy3/blog/2008/12/19/error-handling-framework-for-abap-proxies--part-2     Error handling framework for ABAP proxies - Part 2
Regards,
Jilan

ABAP Proxy Error - Integration Builder address not maintained

I intend to use ABAP proxy between R/3 (ECC 6.0) and XI (PI 7.0).
On configuring the relevant connections, I run SPROXY and get the following error:
Integration Builder address is not maintained in the Exchange profile (Connections)
I have created the connx LCRSAPRFC & SAPSLDAPI from R/3 to PI but the connectivity does not work.
On running the reports
SPROX_CHECK_IFR_RESPONSE
SPROX_CHECK_HTTP_COMMUNICATION
SPROX_CHECK_IFR_ADDRESS
SPROX_CHECK_IFR_CONNECTION
My question is:
What is the Program to be used in LCRSAPRFC & SAPSLDAPI? I have used LCRSAPRFC_<sys id of XI server>
and SAPSLDAPI_<sys id of XI server>
Should the XI Integration Builder address be maintained in R/3?
If yes, is there any place where IB address can be maintained in R/3 (I believe there is no such thing as exchange profile in R/3. then how can IB address be maintained in R/3??...pls correct if I am wrong)
If IB address of XI has to be maintained in R/3 then can anyone pls tell me how to do it?

Just recheck the steps with this and come up with doubts then
How do you activate ABAP Proxies?
Regards,
Prateek

ABAP Proxy error

Dear Friends,
I am facing a problem when i use a ABAP client proxy (asynchronously)
An error is raised during proxy method call-
<CODE>SERIALIZE_APPLICATION_DATA</CODE>
 <ERRORTEXT>Conversion error ABAP => XML (Request Message; error ID: CX_ST_INVALID_XML;
(/1SAI/TAS00000000000000000005 XML Bytepos.: 0 XML Path:
Error Text: Executing the operation '&OPERATION&' leads to an invalid XML document) )</ERRORTEXT>
The same proxy runs fine in upstream system (dev) but doesnot run in downstream system (QA) even though all proxy objects have been transferred.
This proxy & another proxy from the same calling report program is serialized in a queue.The first proxy is raising this error, but the second proxy call is successful.
Can someone help,
Thanks
Prasenjit

Hi Guru,
All the fields in the data type have string - also this roxy works fine in devpt. system- but it doesnt work in downstream QA system.
Other proxy interfaces in the QA system work fine.
The error message when i single test the proxy is as follows-
- <CX_XMS_SYSTEM_ERROR>
<ID>SERIALIZE_APPLICATION_DATA</ID>
<P1>Request Message</P1>
<P2>CX_ST_INVALID_XML</P2>
<P3>/1SAI/TAS00000000000000000005</P3>
<P4>XML Bytepos.: 0 XML Path: Error Text: Executing the operation '&OPERATION&' leads to an invalid XML document</P4>
<INFO />
<CATEGORY>XIProxy</CATEGORY>
<AREA>ABAP</AREA>
<CX_ST_ERROR>
<ST_PROGNAME>/1SAI/TAS00000000000000000005</ST_PROGNAME>
<X-ML_OFFSET>0</X-ML_OFFSET>
<X-ML_PATH />
<ST_IC>2</ST_IC>
<ST_TIMESTAMP>20070907163313</ST_TIMESTAMP>
</CX_ST_ERROR>
Any other possible solutions ?
thanks
Prasenjit

ABAP Proxy error due to ICF

Hi All,
I am calling a custom RFC inside Synchronous ABAP server proxy.The problem is that I am getting HTTP Response code not OK error in XI callAdapter Pipeline step when RFC is returning application error (Return type of RFC Message is E ).
Error: The termination type was: ERROR_MESSAGE_STATE
I found note 568528 which says
"TH_RES_FREE or ERROR_MESSAGE_STATE
either the application or the task handler has processed an error
message.Either the "E" message type was used in the application for the "MESSAGE" ABAP language element here or an action was executed in the application, which is not allowed within the framework ofthe ICF.Among other things, outputting a screen (for example,screen or list output) or eliminating the current mode using the"SUBMIT" ABAP language element, for example, are part of the actions".
What should be done to overcome this error?
Note: When i use XI RFC adapter directly to call the RFC, it is working fine and application error of RFC is getting populated in custom error structure perfectly.
Regards,
Sudharshan N A

Hi Sudh..
Into your RFC, do you have an authoritycheck ?
Because that could explain the difference between your own RFC running and this one of XI: user are not the same.
Remind: authority check are based on user profiles. That could explain that an error message is generated by SAP in some cases, and not for another one.
Regards.
Mickael
Edited by: Mickael Huchet on Apr 14, 2008 1:18 PM

ABAP Proxy error in SAP XI

H All,
I have a problem with my proxies that I receive from ECC, 95% of the time the proxy works perfectly, but then the other 5% it fails. When the Message exits ECC it only has one message in the payload, but when it reaches XI it has multiple payloads see pics attached. Any help will be appreciated.
SAP ECC.
SAP XI.
We are using SAP ECC 6 Ehp6 SP08 and SAP XI 3.0.
Regards,
CJ Bester

Hi
The screen shot you have provided for XI, is the payload after XI message mapping. I think you are using multi mapping in XI and hence the payload contains sub payload.
If you check the payload under inbound message in SAP XI, you will see only one payload.
Click on the error and you will see the actual error message in XI and then try to find out the reason for it.
Hope this is clear.

ABAP Proxy error : GET_BUSINESS_SYSTEM_ERROR

Hi All,
I am working on Proxy to File Scenario. In this, while executing a proxy program in Sender system I get the following error:
- <CX_AI_SYSTEM_FAULT>
<CODECONTEXT>Local</CODECONTEXT>
<CODE>GET_BUSINESS_SYSTEM_ERROR</CODE>
<ERRORTEXT>An error occurred when determining the business system (LD_ERROR)</ERRORTEXT>
<LANGUAGE />
</CX_AI_SYSTEM_FAULT>
</cls:CX_AI_SYSTEM_FAULT>
Can anybody please guide me on this.
Thanks,
Chandravadan

Hi Sudharshan,
>>> First check the RFC Destination SAPSLDAPI in ur application system and check if SLD of XI is running fine..
This RFC Destination in Application System is working & SLD of XI is running fine.
>>>Have u pointed to the SLD of XI in transaction SLDAPICUST of application system. It should point to XI SLD. Make sure that u give the host,port,user,password(XI's) correctly there.
It is pointing to SLD of XI & the user I am using is XIAPPLUSER.
>>>Check whether u are executing the proxy in the right client, which is configured as Business system in SLD of XI.
Yes, I am executing proxy in right client which I have defined in SLD as Business Syetem. I am using ECC 5.0 as Sender system.
>>>Also in SXMB_ADM of the application system, check if u have maintained a HTTP Destination to XI and it tests fine.
Yes, I have maintained HTTP destination in Application system & it is also working fine.
Thanks,
Chandravadan

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

Error Handling for ABAP Proxy sender

Hello Everyone,
I am trying out a scenario of SAP R/3 to Oracle database (ABAP Proxy to JDBC).
I have the following code and it works fine.
CALL METHOD prxy->execute_asynchronous
      EXPORTING
        output = it.
     commit work
CATCH cx_ai_system_fault .
    DATA fault TYPE REF TO cx_ai_system_fault .
    CREATE OBJECT fault.
    WRITE :/ fault->errortext.
I know that the above Catch block would be used to handle system errors on the sender side.
Please tell me what kind of errors could these be and what I can do to test these errors. ie. I want to create error situations explicitely and see how they are handled.
Thanks and Regards,
Ashwin

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

Error while activating ABAP proxy object

Hello,
I can see all the interfaces of PI7.0 in my ECC6.0 system.
I am able to create abap proxy object of a interface.
But when I try to activate that I am getting error as
"RFC system error for destination GTADIR_SERVER".
Pl can you suggest. appreciate quick help in this.
thanks in advance,
Sharada

Hi,
For more details take a look at note: [1063482 - Creating Dictionary objects - RFC error GTADIR_SERVER|https://service.sap.com/sap/support/notes/1063482]
It is written that: Message SGSUB 104 is not an error message, but is merely irrelevant information for customers. You can continue to create objects nevertheless.
To get rid of this annoying error you have to implement the corresponding support package.
Regards,
Jakub

ABAP Proxy - Error situation

Similar Messages

Maybe you are looking for