Calling an abap proxy on PI itself

We have a situation where we maintain tables in PI for logging etc... and we want to be able to update these from an inbound message. My plan was to create a proxy on PI itself map to it and call it via the XI adapter, but I get
Loop in message flow found: system is.00.sappi-dev-d1, pipeline CENTRAL with inbound adapter XI already processed
because of course it is trying to put the same message id back in the pipeline for processing
So, is this not possible? Should I just use the RFC adapter and create a function in abap?
thanks for ideas.
regards,
chris

Hi,
>>>So, is this not possible? Should I just use the RFC adapter and create a function in abap?
no it's not possible unless you create a seperate client on PI which can be used for proxies then
Regards,
Michal Krawczyk

Similar Messages

How can I call a ABAP proxy class from BADI? PLease help

hi Experts,
    I have a scenario where I have to call a ABAP proxy class from a BADI. How can I do this? Does anybody has sample code for the same?
Please help.
Thanks
Gopal

Hi,
   You can call a method of a class from BADI. Here are the steps.
   1) In the BADI implementation create a object for the proxy class.
   2) Call the Execute_Synchronous method.
    You can define a BADI by using SE18 and you can implement it by using SE19.
Sample code...
================================================
METHOD ZIF_EX_VBADI~CONVERTUPPER.
DATA: OBJ TYPE REF TO ZTESTCLASS.
DATA: IT_DATA TYPE ZIN_MT,
            IT_RES   TYPE ZOUT_MT,
            SEXCEPTION TYPE REF TO CX_AI_SYSTEM_FAULT.
TRY.
      CREATE OBJECT OBJ
         EXPORTING
             LOGICAL_PORT_NAME = 'TESTPORT'.
CATCH CX_AI_SYSTEM_FAULT INTO SEXCEPTION.
ENDTRY.
ENDMETHOD.
================================================
Thanks,
Vivek LR

How to call a ABAP proxy class from a BADI? Please help!

hi Experts,
    I have a scenario where I have to call a ABAP proxy class from a BADI. How can I do this? Does anybody has sample code for the same?
Please help.
Thanks
Gopal

Hi Gopal,
Check this out
DATA: ref_obj    TYPE REF TO zmfg_production_ord.----> BADI
* Instantiate the proxy class
    CREATE OBJECT ref_obj.
    TRY.
        CALL METHOD ref_obj->execute_asynchronous
          EXPORTING
            output = it_output.     "Output Structure
        COMMIT WORK.
      CATCH cx_ai_system_fault INTO ref_sysexception.
    ENDTRY.
    IF ref_sysexception IS INITIAL.
      WRITE : / 'Error Message'.
    ENDIF.
Edited by: Raj on May 28, 2008 4:52 PM

Bapi call in abap proxy reaching dialog timeout in async scenario

Hi all,
We have an XI interface to create sales orders. Legacy app sends a soap message async to XI with a group of orders. XI sends this group of orders to an Abap proxy async on ECC side. Into this Abap proxy we have a loop to process each order received in the group with BAPI_SALESORDER_CREATEFROMDAT2. Ending the loop, abap proxy start another async process to send the response to XI with an outbound abap proxy, and the response is redirected by XI to Legacy app.
The problem is, this group of orders can have two or two thousand orders... so, the async process guarantee that no timeout limit will be reached. This is working for the whole process. But when this BAPI is creating an order, the time out of BAPIs execution seems to be the same as the timeout of dialog processes (now set to 10 minutes). This is our problem. Some orders spend more than 10 minutes to process (orders with five hundreds items, for example)... when this occurs, BAPI throws a time out reached error and the async process stops on the inbound queue with status sysfail.
We are now trying to understand why this timeout is been triggered by the BAPI. As it is running into an Async process, it should execute without any kind of timeout limits...
If anybody has any idea, please, help us.
Thank you.
regards.
roberti

May be I was not so clear... the total spent time in the process can be many many hours, days, etc... no timeout is reached. I can post 10.000 orders, no timeout is reached. The problem is that if the processing of only one order with BAPI_SALESORDER_CREATEFROMDAT2 takes longer than 10 minutes, then the timeout is reached. This is the strange part. The processing of the bapi seems to get the same timeout of dialog processes, we already tested increasing the dialog process timeout and the timeout of bapi execution was the same...
We already monitor on SE66 to see if it opens a dialog process to execute the bapi call function, but it does not.
If anyone has any tip, please, provide us.
Thanks!
roberti

Double call of abap proxy client

Hi expert,
I have a scenario which an abap program will send a data to third party web service via sender abap proxy. I notice some of the message was double in sxmb_moni which should be called 1 time. Any idea why this happen? Abaper said that the abap program only call my proxy client 1 time. Thanks.

Hi,
Any possible the abap proxy send double message?
There is no way for this to happen.
Either your report for proxy ran twice consecutively or the proxy call method is in loop in report.
Sice u said that only 1 time it happened, i think th proxy call method is not in loop , and may be report ran twice.
Please check the ABAP code if any loop is there or proxy called twice in the report..
Babu

Parallel processing of webservice calls in ABAP Proxy

Within an ABAP Proxy I want to call multiple services in parallel. My thougth was to encapsulate the webservice calls in RFC function modules and then to use "CALL FUNCTION STARTING NEW TASK ..." but anyhow I am wondering if it is possible to use a form within ABAP proxy to collect the RECEIVE data from the modules.

The Problem was caused by the response of the external AXIS WebService which contains a multiRef element in the SOAP
body which is not supported by SAP simple transformation.
The multiRef was switched off on AXIS.

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

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

Exception when calling ABAP Proxy modelled in SAP PI: CL_SOAP_RUNTIME_ROOT

Hi,
We have a scenario where we:
1. Modell an interface in SAP PI
This interface contains a complex type from a different namespace
2. Use it to create an ABAP proxy in backend system
3. Configure it with SOAManager
4. Call the ABAP proxy ws directly from a third-party system (biztalk)
We're currently testing calling the ABAP proxy from soapUI, but get a strange exception thrown by the SOAP framework in ABAP backend.
The test in soapUI is setup by importing the WSDL acquired from SOAMANAGER.
The error message we in the SOAP response is:
CX_SY_REF_IS_INITIAL:Exception CX_SOAP_ROOT occurred
(program: CL_SOAP_RUNTIME_ROOT==========CP, include: CL_SOAP_RUNTIME_ROOT==========CM004, line: 130)..
An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally,
nor declared in a RAISING clause.Dereferencing of the NULL reference
It is a very low level error from the CL_SOAP_RUNTIME_ROOT program and not a descriptive error message at all.
We've checked the user and the authorizations it has, we've redone the SOAManager config but the problem persists.
We find no dumps in the ABAP proxy since the request never reaches it.
For a limited time I'll make WSDL and SOAP response available
WSDL (some values anonymized) available at http://dl.dropbox.com/u/4379928/SOAP/project.wsdl
Complete SOAP response is available at http://dl.dropbox.com/u/4379928/SOAP/soap_data.xml
Any ideas on where to look?

Hi,
We've now managed to implement a workaround.
The workaround was to create the endpoint in PI as well.
So that the traffic goes from third-party solution->PI-> WS-enabled ABAP Proxy
When we did this initially, we got some errors related to the asynch method of this call, but this was resolved by changing the channel from "best effort" to "Guaranteed delivery".
Still we don't know what the root cause of the initial problem was, but we assume it is related to the asynch nature of the service (though we have other asynch proxies that work without problems).
Regards
Dagfinn

SAP PI 7.4 SOAP - ABAP Proxy Synchronous Webservice

Hi Everyone,
I am developing the following scenario:
3rd party makes a SOAP call to SAP (via PI) to determine whether a vendor exists or not in the SAP system. The link for the call is provided by us from the Integrated Configuration.
The request comes in, calls an ABAP Proxy to check if a vendor exists and sends a response back to the SOAP call with a 'Y' or an 'N'.
I've read a lot about various scenarios but I'm having trouble connecting the dots as I'm fairly new to PI. I'd appreciate any help.
I've made the following set-up based on assuming I need separate Service Interfaces for the SOAP Request & Proxy Response
ESR
1. Message Types
     SOAP (MT_SOAP_REQ & MT_SOAP_RESP) - PROXY (MT_PRXY_REQ & MT_PRXY_REQ)
2. Message Mappings
     MM_REQUEST    which maps MT_SOAP_REQ   to MT_PRXY_REQ)
     MM_RESPONSE which maps MT_PRXY_RESP   to MT_SOAP_RESP)
3. Service Interfaces (Synchronous)
    (SOAP Request)
    SI_IN (Inbound Interface)       with Request = MT_SOAP_REQ and Response = MT_SOAP_RESP
   (Proxy Response)
    SI_OUT (Outbound Interface) with Request = MT_PRXY_REQ and Response = MT_PRXY_RESP
4. Operation Mapping
    OM_LOOKUP which maps SI_IN to SI_OUT with Request    (MT_SOAP_REQ to MT_PRXY_REQ)
                                                                    and Response (MT_SOAP_RESP to MT_PRXY_RESP)
I create the ABAP Proxies for each Service Interface. SI_IN contains the required coded method to check if there is a vendor.
I create the webservice and binding for SI_IN in SOAMANAGER
At this point I'm somewhat unsure - what do I need to do for SI_OUT ? Do I need to create a logical port ? how is SI_OUT associated to SI_IN (apart from the Operation) to get the response.
ID
In the Integration Directory I've created a SOAP_SENDER communication channel for System A and SOAP_RECEIVER channel for SAP. For the SOAP Receiver I need to specify a URL - what should this be ? Is it meant to point to the web service for SI_IN in SICF or just to the generic http://host:8000/sap/xi/engine?type=entry
Do I need to use the HTTP_AAE adapter for the receiver instead of SOAP ?
I created an Integrated Configuration for the SI_IN Service Interface with comm channel SOAP_SENDER from System A and SOAP_RECEIVER for SAP backend. I then got the WSDL for this to provide to the 3rd Party to test (via SOAP UI) . Again my concern is how is the SI_IN linked to the SI_OUT to achieve the response ?
I appreciate you taking the time to go through this . Any help is greatly appreciated.
Thanks very much
Gary

I create the webservice and binding for SI_IN in SOAMANAGER
At this point I'm somewhat unsure - what do I need to do for SI_OUT ? Do I need to create a logical port ? how is SI_OUT associated to SI_IN (apart from the Operation) to get the response.
>>>>No need to do anything in SOAMANAGER
Do I need to use the HTTP_AAE adapter for the receiver instead of SOAP ?
>>> No. Soap adapter is fine. Configure your receiver channel as explianed in the below blog (section 4.3)
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b?overridelayout=t…
Again my concern is how is the SI_IN linked to the SI_OUT to achieve the response ?
>>>>Your receiver determination and interface determination takes care of this.(receiver interface & outbound processing tabs in ICo)

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,

How to handle exceptions in sender ABAP Proxy

Hi Experts,
   I have a synchronous scenario.
   SAP R/3 System A -ABAP Proxy <-> PI <-----> SOAP< ---> Webservice
   In system 'A', a function module calls the ABAP Proxy method.
   My requirement is that if there is an exception in PI ( for example: timeout or ABAP engine error) then I want to get the exception details in the calling function module.
For example:
Exception in PI:
<SAP:Error xmlns:SAP="XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1/><SAP:P2/>
<SAP:P3/><SAP:P4/>
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace=""/>
<SAP:Stack/>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In the calling function module:
Try
Call to proxy-> method
Catch cx_ai_system_fault INTO v_o_fault.
       v_err_msg1 = v_o_fault->GET_TEXT( ).
       v_err_msg2 = v_o_fault->errortext.
       v_err_msg3 = v_o_fault->code.
Endtry.
Here I get value "MESSAGE.GENERAL" for v_err_msg1 and v_err_msg3. v_err_msg2 is blank.
I want to capture the info available under <SAP:AdditionalText>. How to get that?
Please help!
Thanks & Regards
Gopal

>
gopalkrishna baliga wrote:
> Hi Experts,
>
>    I have a synchronous scenario.
>
>    SAP R/3 System A -ABAP Proxy <-> PI <-----> SOAP< ---> Webservice
>
>    In system 'A', a function module calls the ABAP Proxy method.
>
>    My requirement is that if there is an exception in PI ( for example: timeout or ABAP engine error) then I want to get the exception details in the calling function module.
>
> For example:
>
> Exception in PI:
>
>   <SAP:Error xmlns:SAP="XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
> <SAP:Category>XIAdapterFramework</SAP:Category>
> <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
> <SAP:P1/><SAP:P2/>
> <SAP:P3/><SAP:P4/>
> <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect</SAP:AdditionalText>
> <SAP:ApplicationFaultMessage namespace=""/>
> <SAP:Stack/>
> <SAP:Retry>M</SAP:Retry>
> </SAP:Error>
>
> In the calling function module:
> Try
> Call to proxy-> method
>
> Catch cx_ai_system_fault INTO v_o_fault.
>        v_err_msg1 = v_o_fault->GET_TEXT( ).
>        v_err_msg2 = v_o_fault->errortext.
>        v_err_msg3 = v_o_fault->code.
> Endtry.
>
> Here I get value "MESSAGE.GENERAL" for v_err_msg1 and v_err_msg3. v_err_msg2 is blank.
>
> I want to capture the info available under <SAP:AdditionalText>. How to get that?
>
> Please help!
>
> Thanks & Regards
> Gopal
Hi Gopal,
Maybe the exception is CX_SY_APPLICATION_FAULT, or you can catch by BPM in PI and send back to proxy like a message response.

Timeout in ABAP Proxy

Hi!
In my scenario messages on CRM are created by a BADI calling an ABAP proxy class on the local Integraton Engine which then forwards the messages to the XI Integration Server and vice versa.
We recently had the problem that the SAPSLDAPI SM59 destinations on XI and CRM ran into a timeout because the SAPSLDAPI service in the JCo RFC Provider Service of the J2EE Admin Tool was not working properly.
While we experienced the SAPSLDAPI timeout problem in the XI Integration Server all messages which XI was supposed to forward to CRM failed in the Call Adapter step in SXMB_MONI with error status 500 (timeout).
I would have assumed that the same happens also on the CRM side when the local Integration Engine was supposed to send messages to XI. However, there was a timeout when pressing the save button in the IC Web Client. The XML messages were not created at all and not visible in SXMB_MONI. Thus in production a call center agent would have not been able to update any customer or product information.
If such a problem arises in my opinion the messages should always be created and queued up by the Integration Engine so that they can be reprocessed once the problem is solved. Does anybody have any idea why this did not happen on the CRM side and do you have any feedback how this problem could be resolved?
Regards, Tanja

Hi!
> Please can you check in the SXMB_MONI of the CRM
> system if there are any messages stcuk there if you
> cannot see the same in the XI SXMB_MONI.
There was a timeout when pressing the save button in the IC Web Client. Thus the XML messages were not created at all and not visible in SXMB_MONI on CRM.
Regards, Tanja

Dynamic Configuration from Client ABAP Proxy

Hello Experts,
Is it possible somehow to set Dynamic Configuration values to Message Header when calling Client ABAP Proxy from SAP system?
Best Regards

I managed to get the dynamic header configuration at least with inbound proxies:
    DATA:
        server_context TYPE REF TO if_ws_server_context,
        proxy_framework TYPE REF TO if_proxy_framework,
        internal_protocol TYPE REF TO if_wsprotocol_internal,
        lo_inb_pxy TYPE REF TO cl_xms_inbound_proxy_plsrv,
        lo_dyn_header TYPE REF TO if_xms_msghdr30_dynamic.
      server_context = cl_proxy_access=>get_server_context( ).
      internal_protocol ?= server_context->get_protocol( 'INTERNAL' ).
      lo_inb_pxy ?= internal_protocol->get_framework( ).
      lo_dyn_header ?= lo_inb_pxy->xmb_message->get_dynamic_header( ).

XI - ABAP Proxy

Hi,
is there a way to make XI/PI to call an ABAP proxy sync in some interval (let's say every 5 min)?
I don't want to do this on ABAP side with sceduling some BGD job/report......
thx
mario

Hi mslopar
/people/siva.maranani/blog/2005/05/22/schedule-your-bpm
Regards
Abhishek
***Please reward points If helpful**

Calling an abap proxy on PI itself

Similar Messages

Maybe you are looking for