Trigger inbound proxy from ABAP

Hi Experts,
We have a requirement to trigger inbound proxy from within an ABAP program. Is it possible to trigger an inbound proxy from ABAP if so please guide me on how to achieve this?
Thanks
Sanu

This requirement cant be achieved.

Similar Messages

Calling a proxy from ABAP Report

Hi All,
Can any one gimme some idea about calling a XI proxy from ABAP Report.
I need to gather data in my internal table and after that i need to trigger a proxy which is going to do a outbound processing.
Thanks in advance.
Tnx,
Joe.

Hi Meetjoe,
We have to design the required interface in PI ,that is used to hold the report data when tigerred a proxy and generate the proxy based on the interface if the Proxy is based on the Outbound side its called client proxy or if the proxy is genereated on Inbound interface we call it server proxy.
need to gather data in my internal table and after that i need to trigger a proxy which is going to do a outbound processing.
In your case its gonna be the client proxy refer the follwing links for your better understanding
For concepts on Proxies:
http://help.sap.com/saphelp_nw04/helpdata/en/02/265c3cf311070ae10000000a114084/content.htm
To enable Proxy connections:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50d69314-1be0-2b10-11ab-8045021f0c3a
Smaple scenarios on Proxy:
Proxysettings /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
ABAP Server Proxy /people/siva.maranani/blog/2005/04/03/abap-server-proxies
ABAP Client Proxy /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Thanks,
Ram.

Create a proxy from abap with 3 messages parts

Hi,
I am trying to create a proxy from a WSDL file with 3 messages parts:
<wsdl:message name="executeSoapIn">
    <wsdl:part name="farmName" type="s:string"></wsdl:part>
    <wsdl:part name="requestXML" type="s:string"></wsdl:part>
    <wsdl:part name="farmProps" type="s0:Map"></wsdl:part>
</wsdl:message>
This is not possible because it is not fulfilling the SOAP 1.1 standard, so when I try to create the proxy I am getting an error, so no proxy is created.
My question is: Is is possible to create a ABAP proxy manually so the proxy would have the 3 parameters of the messages part?
Thanks in advance.
Eduardo.
Message was edited by:
        Eduardo Martí

Hi,
The problem is that i need to create a proxy with 3 parameters in one of its methods, that is, the method SOAPEXECUTEIN will need the parameters (farmName, requestXML, farmProps), as shown in the piece of code of the WSDL file. I can not do it because the system did not allow me, it allows just one parameter.
Is it possible to create the proxy in some way that allows me the method with the three params?
Thanks Aamir.
Cheers.

How to Trigger a Workflow from ABAP Webdynpro

Hi All Gurus,
I have the following urgent requirement, my client is implementing HR and there is a requirement, where is a ABAP Webdynpro component in which we have integrated a Adobe Interactive Form. When the user calls this from through Portal and fills out the relevant data and submits it, a Workflow in the backend ECC system should lauch,
I am not familiar with, this concept although I have worked in Workflow this is the first time I am interfacind with ABAP Webdynpro and Adobe Interactive From.
Can you please let me know in steps what needs to be done to make the workflow trigger for my scenario and also the specific settings to be done in the bacckend.
Regards,
Pratima Jain

Hi,
If you are using HCM Processes and Forms, the Workflow and form are not directly related, thats true.
But the method in the task calls the corresponding webdynpro application which responds to the action triggered by the user in turn to trigger the workflow and update the data in the HR Master Data.
There are 3 layers 1. UI (webdynpro which launches Adobe Interactive form based on ISR Framework)
2. Workflow
3. Backend framework (used for retrieving F4 helps, default values, save data in the infotypes).
for more documentation, please refer it on help.sap.com.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/82/b6b94278560c31e10000000a1550b0/content.htm
hope this helps.
Best Regards,
Saujanya.

Trigger a workflow from ABAP Webdynpro

My Scenario:
Step 1: When a user hits the SAVE button on the webdynpro form, check if that data is consistent only and trigger a message(I have a BAPI to handle this check).
Step 2: If the data is consistent, then trigger a workflow to send an alert to an agent along with the data user entered on the form.
Step 3: AGENT shall review the data(Same form from step 1 should appear here) and will have the option to SUBMIT / POST or REJECT. If SUBMITTED, data will be posted to R/3(I have a 2nd BAPI to handle this). If REJECTED, send an alert back to the USER who entered data in step 1.
I checked lots of threads from the forum, none gave me a complete idea. Can any one give me a good documentation to trigger workflow from webdynpro to handle my requirement.
I am new to webdynpro.
I checked this blogs & articles also...
/people/ginger.gatling/blog/2005/12/14/create-new-uis-for-existing-workflow-tasks-with-abap-web-dynpro-and-universal-worklist
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/wd%20java/wdjava%20archive/using%20web%20dynpro%20java%20and%20web%20dynpro%20abap%20applications%20in%20universal%20work%20list.pdf
Thanks a lot in advance.
Best Regards,
Kiran

Hello Kiran,
I slightly misunderstood you requirement earlier. But if I am not wrong this time, here is what you need to do:
1) The Web dynpro form that you are creating is only for data entry purpose. But the agent who is going to review the data will need an access to this form. So this means that you need to save the content of this form to the database and provide a URL in the workflow workitem which the agent can use to open the web dynpro application with the form data on it.
2) To access the correct form, you need to save the form data in a Z-table with a GUID attached to it. Generate this GUID using GUID_CREATE function module. In the window controller of the Web dynpro component, there will be a handleDefault method where you can read the parameter'GUID' from the incoming request and use it to read the form data from the database to display the form.
3) You can use Object Oriented programming approach for creating Workflow. Check the following article to learn how to do that:
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0409e6c-d213-2d10-3cb6-c12d417626c1?quicklink=index&overridelayout=true]
4) Create a Z-class and use this class as object type in your workflow (instead of BOR object).
5) In the constructor of this class, pass a parameter GUID, which would be passed when you create an object of this class in the Web Dynpro forms "OnActionSave" method.
6) Create a method in this class which will do the task of calling the BAPI to save the Acct Document. This method will be used in a Background task in a workflow step (after the agent approves the workitem).
7) Create a method in the class which generates the URL to the webdynpro application with the GUID passed as parameter.
(for eg: http://urltoserver/appname?GUID='guidoftheform').
8) In your save method of WD application, call the method to raise event that triggers the workflow (using OO)
lv_guid    = '04AE4546EED7101DE10000000A424026'. "use GUID_CREATE
       lv_objtype = 'ZWFCLASS'. " create a Z-class of your own
   TRY.
      CALL METHOD cl_swf_evt_event=>raise
        EXPORTING
          im_objcateg = 'CL'
          im_objtype = lv_objtype
          im_event    = 'FORM_APPROVE' " this event needs to be defined in ZWFCLASS
          im_objkey   = lv_guid.
    CATCH: cx_swf_evt_exception.
ENDTRY.
Please read through the workflow using Object Oriented document in the URL that I have mentioned above before you read through these instructions.
There would be a way to do this using BOR objects, but this is the way that I have tried and tested to use trigger workflows from Web dynpro applications.
Best Regards,
Gaurav
Edited by: Gaurav Salkar on Apr 6, 2010 6:13 PM

Problem Calling a Client Proxy from ABAP which is based on an extension

I'm trying to create an Asset in Salesforce from SAP using ABAP.
I have exported the enterprise WSDL from Salesforce, generated a client proxy and have coded the login call and passed the session id to the create call.
The problem I am having is the create method references sobject however asset is an extension of this.
            <complexType name="Asset">
                <complexContent>
                    <extension base="ens:sObject">
                        <sequence>
                        <element name="Account" nillable="true" minOccurs="0" type="ens:Account"/>
                        <element name="AccountId" nillable="true" minOccurs="0" type="tns:ID"/>
                        <-- many more fields here -->
                        </sequence>
                    </extension>
                </complexContent>
            </complexType>
I need to pass something like this (tested and working using SOAPUI)
         <urn:sObjects xsi:type="urn:Asset"
                   xmlns:ns3="urn:sobject.enterprise.soap.sforce.com">
               <urn:AccountId>001A000000HoyKZ</urn:AccountId>
               <urn:Name>JWSOAPTEST Asset3</urn:Name>
                        <-- many more fields here -->
        </urn:sObjects>
I tried modifying the WSDL so sobject referrs to Asset
            
            <element name="create">
                <complexType>
                    <sequence>
                        
                       <element name="sObjects" type="ens:Asset" minOccurs="0" maxOccurs="unbounded"/>
                    </sequence>
                </complexType>
            </element>
            <element name="createResponse">
                <complexType>
                    <sequence>
                        <element name="result" type="tns:SaveResult" minOccurs="0" maxOccurs="unbounded"/>
                    </sequence>
                </complexType>
            </element>
However other types it referred to weren't populated.
The other approache may be to manually populate the xml similar to what I had to do in the header (this link gives a good overview on this Consume web service in ABAP proxy with SOAP header )
Any recommendations or advice would be appreciated.
Ideally some sample code if someone has done this or a recommendation on how to modify the WSDL.
Regards,
John

Hi John,
Calling SFDC.com from PI, is detailed out here. probably will give some tips:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50a76cfa-4966-2d10-aba7-da496d9b5bcf
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/802f8d03-9282-2d10-52b4-f9446e077099
Regards, Moorthy

Inbound proxy from XI or PI

> Is it possible that messages can be sent from XI or PI to the same SAP instance?
Yes, you can send messages from different PI system to the same SAP system.
This is valid for XI, RFC and IDoc adapter.
Regards
Stefan

We found the solution. By changing the connection (SM59, SLDAPICUST) on the SAP site, we were able to generate the PI proxies. and we could still send messages from XI to this SAP system. Proxy Runtime and Designtime are different.
Thanks,
Pieter

How to trigger MDM Workflow from ABAP Program.

HI
I have requriment to trigger MDM Workflow(Design in MDM) from My Module pool program. Suggest how to do it?
Thanks in Advance.
Regards,
Shyam Babu Sah.

Hi,
This question is for forum SAP Netweaver --> Workflow. There are functions and programmes that SAP delivers for this.
[Example here|Re: How can I trigger workflow from my report]

Error In Inbound Proxy

Hi
I have SRM Scenario were I am sending a Z_CREAMAS_SUSMM IDOC from ECC 6.0 to SRM 5.5 SUS via PI 7.0 . There are no errors on the XI side and the sxmb_moni of the SRM side .The message shows a successful flag on the XI as well as the SRM side . But however the functionality of the idoc does not work ie the vendor is not created in SRM SUS.
When we try to test the inbound proxy from sproxy by copying the payload from sxmb_moni of SRM and then testing it we get a short dump with the following contents .
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
     caught in
    procedure "SET_METHOD" "(METHOD)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component.
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "OBJECTS_OBJREF_NOT_ASSIGNED_NO" "CX_SY_REF_IS_INITIAL"
    "CL_PROXY_INBOUND_ADAPTER======CP" or "CL_PROXY_INBOUND_ADAPTER======CM00I"
    "SET_METHOD"
Can any one please tell me what the error could be .
regards
Nilesh Taunk

Hi,
You program raise an exception as''CX_SY_REF_IS_INITIAL'.
this is due to null value passing to the object.
i hope, u r using intialization event in the custom ABAP code.
please try to change it.
warm regards
mahesh.

Upload data from abap program to abap inbound proxy

Hi,
I have requirement to upload flat file data to an internal table and call Inbound proxy abap class and pass all the internal table data to tha proxy clas method structure.
So could any one help me how to send/pass data to class, Please give some e.g.
thanks
bobby
Edited by: Bobby G on Nov 18, 2009 4:35 AM

hi;
you may follow the following ways
1. create a report and by using GUI_upload, give the path as default , you can convert the flat file's data into internal table.
2. call that report in proxy method by returning parameter as a table, this table can use further in the proxy.
Another way, you have
1. Create a transparent table and by using the GUI_Upload in report, you may store the data.
2. from step 1, you may use data in the proxy.
Regards
Shashi

How to call BAPI from ABAP Inbound Proxy

Hi All
Can some one provide/giude a sample code on how to call a BAPI from generated Method (Inbound Proxy) and how are the table parameters passed from Proxy to BAPI.
Thanks
Ravi/

Hello Ravi,
In the proxy before calling the BAPI, construct the table, fill it with the appropiate values by lopping over the proxy request object. Now use this table for calling BAPI
Cheers,
Naveen

Message has Error status on outbound side - in ABAP inbound proxy !!

Hi All,
One interesting question for you guys. I have got one of the scenarios like File to ABAP inbound proxy. Message are going properly, no errors in receiving system. But on PI moni I can able in "outbound status" column in red colored flag. No all the messages couple of them with u201CMessage has Error status on outbound side ". Why please?
Regards
San

Hi ,
Please check whether the correct data is coming from sender side . and check the j2ee engine runtime parameters.
Cheers,
Meera
Edited by: MeeravaliDudekula on Oct 18, 2010 2:36 PM

ABAP Inbound Proxy Error !

Hi ,
I am forwarding Vendor Data from SRM EBP to SUS with the predifined proxies given by SAP, bu t i get below error when it reaches SUS System.Message processing both in SAP EBP and SAP XI is fine.
<?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_BBPX_TRADING_PARTNER_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>
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

Hi attached trace, kindly update wat could be the problem in case of EBP SUS Vendor replication
<?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=receiver</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 = SSR</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WIP-SRINUS</Trace>
<Trace level="1" type="Timestamp">2008-04-25T04:58:21Z 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 = DD128437FD4A75F193690017A4F3435A</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 : XBTR0001</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0001</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 = SSR</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WIP-SRINUS</Trace>
<Trace level="1" type="Timestamp">2008-04-25T04:58:24Z 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="#o97" />
</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="o97">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o96" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>297</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="o96">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>297</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:034 -Organizational unit 00000008 does not exist; check entries 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>

ABAP Inbound Proxy issue

Hi All,
I have a file to ABAP Inbound proxy scenario for creating vendor in SAP.
When I execute from SPROXY test tab, vendor is created in SAP.
But when i test end to end i.e by feeding the file adapter with the vendor file i don't see the vendor creating in SAP.
The message is successful in PI moni and in ABAP moni. Cant see any errors
Appreciate your inputs in this solving this please
Keerthi

>
Keerthika R wrote:
> The message is successful in PI moni and in ABAP moni. Cant see any errors
Hello Keerthi,
I was facing the same issue. I found that we can use SXMB_MONI and SMQ2 in the SAP side as well (Backend ABAP System where the Server Proxy is created). If you are able to see the messages in SXMB_MONI of the ERP system then your proxy is working fine however, have problems in ERP System. Follow through the error message it will be easy for you to perform error analysis.
You can ignore if you have already done it!
Thanks & Regards,
Anand Patil

Sync Async using proxies ( Calling Outbound proxy from Inbound proxy )

I'm trying to generate Asynchronous Outbound message from the Synchronous Inbound message message due to a requirement. My question is : is it really possible to develop such a scenario?. I'm getting weird error such as Kernal exception etc. Please let me know if you have developed such scenario and what should we do dfifferently in such scenarios?. Thank you for any suggestions.

Hi,
This error has has nothing to do with Calling Outbound Proxy from from Inbound Proxy. The scenario which you are telling is very much possible.
It looks like there is some problem in your proxy code while calling RFC from within there or something like that. Try catching the exception and see what is the exact error or put in debug mode and see the step where exactly your code is failing.
Use the following links for Catching Exception in Proxy
Inbound ABAP Proxy Trace and error handling
Handling Exceptions
ABAP Server Proxies - Fault Handling
Exception handling in integration processes
ABAP Proxy and fault messages
/people/bhanu.thirumala/blog/2006/02/07/abap-proxy--xml-to-abap-transformation
Thanks
Amit
Reward point if answer is helpful

Trigger inbound proxy from ABAP

Similar Messages

Maybe you are looking for