ABAP Proxy - AAE Synchronous message problem.

Hi,
We are using ABAP Proxy -> PI 7.11-> JDBC stored procedure. We are using AAE.
The problem we are facing is identical to the one mentioned in the thread below:
[Re: <SAP:Code area="PARSING">GENERAL</SAP:Code> - Error;]
That is the first call is ok.. and the second call results into exception. When we switch to normal config without AAE, it is working fine.
Any help on this matter would be much appreciated.
PS: Also please note that similar scenario is running for a different customer without trouble...
Thanks and Regards,
Himadri
Edited by: Himadri Chakraborty on Dec 20, 2010 8:45 PM

The link you gave does not open.
Also please note that similar scenario is running for a different customer without trouble...
Compare the SP level of both the systems.....if configuration is perfect, then ensure that SP level of ABAP and JAVA is at same level.
@Baskar: Proxy supports AAE communication from PI7.11....no need to wait for 7.3....more information is available
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b?quicklink=index&overridelayout=true
Regards,
Abhishek.

Similar Messages

Interface ABAP Proxy - File - Synchronous - (Is it possible???)

Hi Experts,
I want execute ABAP Proxy which will create File in FTP. On final, i need return "OK" information to the ABAP Proxy.
Is it possible? ABAP Proxy <-> File Synchronous? Without BPM and Custom Module Adapter. Just using RequestResponseBean???
Tks in advance.

Hi Raj,
Tks. I implemented the Acknowledgements Request and changed the ABAP Proxy to Async. But the Ack returns to the ECC with the error and is not saved in the Message. The error follows below:
<?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="PERSIST">REQUEST_MESSAGE_NOT_FOUND</SAP:Code>
<SAP:P1>4EE24DEB4EA60650E10080000A09071E</SAP:P1>
<SAP:P2>CENTRAL</SAP:P2>
<SAP:P3></SAP:P3>
<SAP:P4></SAP:P4>
<SAP:AdditionalText></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace=""></SAP:ApplicationFaultMessage>
<SAP:Stack>Requisição mensagem 4EE24DEB4EA60650E10080000A09071E pipeline CENTRAL versão desconhecida</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Any Idea about this error?
Tks in advance.

ABAP Proxy Exception / Fault Message

Hi All,
I have got a requirement to raise an exception from existing ABAP Proxy depending on condition. XI consultant created a fault messge type and attached to the inbound interface message type. I have regenerated the ABAP proxy but I cant find any thing in excpetion tab to raise exception.
Please let me know the solution for this.
reward points are available.
-Venkat

Hi Venkat,
The following link will guide you ..
http://help.sap.com/saphelp_nw04s/helpdata/en/c9/7a1041ebf0f06fe10000000a1550b0/frameset.htm
I dont think we need to do any changes in Exchange Profile for proxy communication.
Changing the RFC Destinations (in your R/3 system)- LCRSAPRFC & SAPSLDAPI should solve your problem.
Regards,
Sumit

File to Abap Proxy Scenario : No message log in SXMB_MONI

I have a PI Scenario in which a FTP server is polled every 5 minutes, and when it receives any file, file is archieved and abap proxy is called. Few days back it was running perfectly fine. But For last couple of days I am facing strange error.
My File is archived but abap proxy isnot called, neither I get any message in SXMB_MONI.
any guesses what should I do?
Jawed Ali

Hi Jawed,
HOLD means you have given QoS as EOIO in sender channel and the first message got failed and hence all messages are waiting..
Check this thread
Re: PI 7.1 Messages stuck into the Queue of the Adapter Engine
Try resending the messages through runtime workbench->message monitoring->adapter engine
Regards
Suraj

SAP ABAP Proxy - recursive data structure problem

Hi,
For our customer we try to bind SAP with GW Calendar using GW Web Services. We tried to generate ABAP Proxy from groupwise.wsdl file but there are problems: GW uses recursive data structures what ABAP Proxy can not use. Is there any simple solution to this problem?
Best regards
Pawel

At least I don't have a clue about ABAP Proxy.
You are pretty much on your own unless someone
else has tried it.
Preston
>>> On Tuesday, August 03, 2010 at 8:26 AM,
pawelnowicki<[email protected]> wrote:
> Hi,
>
> For our customer we try to bind SAP with GW Calendar using GW Web
> Services. We tried to generate ABAP Proxy from groupwise.wsdl file but
> there are problems: GW uses recursive data structures what ABAP Proxy
> can not use. Is there any simple solution to this problem?
>
> Best regards
> Pawel

Abap proxy call : synchronous / background ?

Hi,
I use currently abap proxy call to send data from ECC to XI, and it works fine ! But... I would like to know two points :
1. Is it possible to execute SYNCHRONOUSLY this call abap proxy and not only in asynchronous...
2. Is it possible to execute in BACKGROUND this call abap proxy, because it seems it use a dialog process, even if the call is inside an abap program executed in background
I will appreciate your feedbacks on these both points ?
Regards.
Mickael

Hi,
Yes, we can do Sysnchronous call in Proxy.
and we can do the Background job schedule also in Proxy .
Reffer this help file
http://help.sap.com/saphelp_nw04/helpdata/en/86/58cd3b11571962e10000000a11402f/content.htm
Reffer this BLOG also
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
Regards
Seshagiri
Edited by: N V Seshagiri on Feb 12, 2008 11:19 AM

Problem in ABAP Proxy(sometimes XML Messages are not being created)

Hi,
I am trying to send the data from ECC to CRM when post goods issue is done for a delivery from ECC side. I called my proxy method in BADI : DELIVERY_PUBLISH.
And after calling the method, I used commit work also.
But the problem is, some times it is working fine. and some times the XML messages are not getting created. When I go in debug, looks everything is fine.
I am unable to understand why this inconsistency.
Could you please help me out, do I need to take any more precautions.
Thanks,
Sandeep

You mean you can't find any message in SXMB_MONI of your ECC or is it XI where you can't see message?
If you have not checked in SXMB_MONI of ECC then may be messages are created but they are going into error and that's why you are not able to see any message in XI.

ABAP Proxy and fault messages

I am calling a Outbound proxy (Asynchronous) from R/3. Should I catch fault after the call?
When I don't catch fault, I get the following warning message. What should i do about these warning message?
The exception CX_AI_SYSTEM_FAULT is neither caught nor is it declared in the RAISING clause of "EXECUTE_ASYNCHRONOUS". 
Any ideas?

Hi SSG,
Check this
Proxy framework: Catch CX_AI_SYSTEM_FAULT
cheers
Prashanth
P.S Please mark helpful answers

Error handling using fault message type in outbound synchronous ABAP proxy

Hi,
We've a scenario, outbound synchronous ABAP proxy to synchronous SOAP receiver. The requirement is to send multiple records in a single rquest and get response for all the records sent (in the same response message).
Say if I send 10 records from ECC, I should get 10 records as response from SOAP to ECC. But the problem here is, there could be some invalid requests, for which an invalid error status code should be sent as part of response.
Source Structure
Req_Proxy
    req (0..unbounded, string)
Response Structure
Resp_SOAP
Resp (0..Unbounded)
       respString (0..1, String) (carries the actaul response message)
      status code (0..1, String) (carries the status of the response, for ex, 001 (successful), 002 (error))
And now we are planning to make use of Fault Message Type, to track the errors from SOAP (status code 002). But, we are not sure on how to track this for all the requested records. Is it possible to track the errors for all the requested records in a singe call using fault message type? For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8 for valid and 2 for invalid accordingly.
Please calrify.
Thanks.
Rohit

For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8
for valid and 2 for invalid accordingly.
Check if you can modify the WSDL structure to include an error node that would get populated incase of invalid entries....this would mean that you get the success and failure details in the single message....also at the proxy-end make the necessary change in your DT.....may be then you do not need to use the fault message...
Regards,
Abhishek.

[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

Missing asyn abap proxy client message in ECC

Hi,
I have a asyn scenario which an abap program will send data from ECC to PI using abap proxy client. My problem is i notice some of the message was no send to PI. Checked in PI SXMB_MONI no message was found. Any idea where the message was stuck? I check on smq1 in ECC also found nothing in the queue.
Thanks.

Hi ,
KIndly check with the abap program if its thrwing any dump . If every thing is fine with ABAP program then might be its issue of RFC destination . check with transaction SPROXY are u able to connect and your sender interface is reflecting there if yes then double click on your interface open the proxy andthen click on GOto and click on connection test if nay issue is in connection then it will display the error here .might be some rfc DESTINATION is missing or authnetication error .
Regards,
Saurabh

Problems in ABAP Proxy Generation

Hi All,
I tried to generate an ABAP proxy for outbound message interface "Interface_ABC", which is under software component "DEF".
In our development system, I had successfully created ordinary function modules and structures under the package "/XYZ/UVW" using the prefix "/XYZ/".
When I began the proxy generation, the system asked me to specify the package and prefix. So I specified the package to be "/XYZ/UVW" and prefix to be "/XYZ/".
Then a warning window pops up. It reads "Package /XYZ/UVW does not belong to DEF". I clicked "OK". The "Create Proxy" screen shows up. Then I clicked the "Save" button. This time an error window pops up. It reads "Cannot extend package /XYZ/UVW". The action is thus cancelled by the system.
Does anybody know what is the reason for this problem and how to solve it?
Best Regards
Jerome

Please check the properties of the package in which you are tyring to save the PROXY.
In your case it looks like the property PACKAGE NOT EXTENDABLE is switched on. Once you uncheck you should be able to save the proxy in that package.
Regards,
Ravi
Note : Please reward points if you find the answer useful.

Build delay in messages to abap proxy without BPM / mapping

Hi everyone,
The abap proxy is receiving messages from PI, is having errors when receiving big loads of messages via PI.
The proxy lock's a table causing the next message to run in error.
The interface is not using BPM or a mapping.
My question is:
What are the possibilities to configure a delay in PI ? (not using a mapping or BPM process)
The abap proxy need some time to process a message before it receives the next one.
Br,
Roy

Hi,
>>>The proxy lock's a table causing the next message to run in error.
if you use async messages with fault messages correcty you can
restart those abap proxies just like IDOCs - and you can schedulerestarting that too
so this is nothing bad - just schedule the restarting and they will get processed
Regards,
Michal Krawczyk

ABAP proxy exception to SOAP fault and vice versa not getting mapped

Hi there,
I have these scenario's: ABAP proxy to SOAP (AXIS framework) and the other way around, synchronous, using AAE.
When declaring the Synchronous Service interfaces we also defined error message types in order to pass system and application exceptions back to the service consumers.
The behavior we are observing is as follows;
When an exception is generated on the ABAP proxy, the error message type is correct generated and filled with the corresponding values in the ABAP proxy runtime. However, when the response arrives at the service consumer, it only contains a SOAP fault filled with some kind of generic PI mapping exception information.
1. Why is the original ABAP proxy exception not mapped/passed into the SOAP response?
2. What can we do in order to change that situation?
3. Does it has to do with the use of the AAE - Advanced Adapter Engine or the AXIS framework?
PS: We have performed a test of the Operation Mapping - OM using the ABAP exception as input and it did work correctly, so the error structure seems to be Ok.
Many thanks for your replies.
Edited by: Roberto Viana on Jul 26, 2010 8:30 PM

Problem was caused by some differences in namespaces between source and target.

Outbound Client ABAP Proxy Timeout Error

Hello everybody we have the next scenario:
R/3 Client Synchronous ABAP Proxy->XI-> Synchronous RFC
and we are having problems cause the Sender R/3 is not waiting for the RFC in the Receiver system to process so XI is in log status fot this messages, is there a parameter to increase the time for R/3 Sender to wait for the Call method sentence to complete succesfully??????, thanks in advance.
Regards,
Raul Alvarado

Hi,
do changes as below
In SXMB_ADM
go to Configure Integration server
in change specific identifiers Set Runtime parameter: HTTP_TIMEOUT and then restart XI server, changes will be updated.
Regards,
Sukarna.

ABAP Proxy - AAE Synchronous message problem.

Similar Messages

Maybe you are looking for