Asynchronous Inbound Proxy &  cl_proxy_fault= raise

Hi there.
I seem to be having difficulty passing the BAPIRET data from a bapi to my exception that I raise within my proxy. The sample code is below:
        CALL FUNCTION 'BAPI_ISUPARTNER_GETDETAIL'
          EXPORTING
            partner            = '12345'
          IMPORTING
            return              = lw_return.
        APPEND lw_return TO lt_return.
        CALL METHOD cl_proxy_fault=>raise
          EXPORTING
            exception_class_name   = 'ZZCX_ZTSX_BUPA_CRE_CHNG_EXCEPT'
            bapireturn_tab                = lt_return.
I purposely want this to fail and it does returning an error message to the lw_return structure. This is then passed to the raise method. However, the result (this is tested in sproxy) is as below, contains none of the bapireturn information:
- <cls:CX_XMS_SYSERR_APPLICATION id="o1208">
- <CX_ROOT>
  <TEXTID>4349F3B101039A42A05904CB12F7FA0E</TEXTID>
  <PREVIOUS />
  <KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
  <PROGID>212</PROGID>
  <CONTID>2597</CONTID>
  </INTERNAL_SOURCE_POS>
  </CX_ROOT>
  <CX_STATIC_CHECK />
- <CX_XMS_SYSTEM_ERROR>
  <ID>APPLICATION_ERROR</ID>
  <P1 />
  <P2 />
  <P3 />
  <P4 />
  <INFO />
  <CATEGORY />
  <AREA />
  <RETRY />
  </CX_XMS_SYSTEM_ERROR>
- <CX_XMS_SYSERR_APPLICATION>
  <RETRY_MODE>M</RETRY_MODE>
- <FAULT_MSG>
  <NAME>ZTSX_BUPA_CRE_CHNG.Exception<;/NAME>
  <NAMESPACE>urn:sap-com:document:sap:rfc:functions</NAMESPACE>
  </FAULT_MSG>
  </CX_XMS_SYSERR_APPLICATION>
  </cls:CX_XMS_SYSERR_APPLICATION>
  </asx:heap>
  </asx:abap>
Am I missing something here? I would appreciate any pointer on this please.
Thanks in advance.
Mick.

Hi,
Check the thread
File to Proxy
Thanks!

Similar Messages

  • Inbound Proxy created as Synchronous

    Hello,
    How do I determine the mode (synchronous/asynchronous) when I create a proxy?  I am trying to create an asynchronous inbound proxy and when I hit "generate" in SPROXY I get a synchronous proxy.
    Thanks,
    Matt

    Hi mathew ,
    How do I determine the mode (synchronous/asynchronous) when I create a proxy? I am trying to create an asynchronous inbound proxy and when I hit "generate" in SPROXY I get a synchronous proxy.
    ---> As per the requirement you have to create sync/async interfaces at ESR/IR in XI .Those interfaces only gets reflected in SPROXY at application server. So the type of interface you have created at XI according to that only you get the proxy in application server .
    Regards,

  • Extended xml handling in asynchronous inbound (server) proxy

    Hello,
    I want to activate extended xml handling on an asynchronous inbound server proxy.
    looking at online help:
    http://help.sap.com/saphelp_nwpi71/helpdata/en/73/3f5c3c3906b006e10000000a11402f/frameset.htm
    this should be the code:
      lo_server_context   = cl_proxy_access=>get_server_context( ).
      lo_payload_protocol ?= lo_server_context->get_protocol( if_wsprotocol=>payload ).
      CALL METHOD lo_payload_protocol->set_extended_xml_handling( abap_true ).
    However the controller tables remain empty when executing a scenario to the application system.
    Also adding a static attribute extended_xml_handling does not have the correct result.
    any suggestions???
    Regards,
    Emile

    Hello Emile,
    do you have a solution regarding your problem? If not, here is a good one.
    I think you have inserted the code inside the generated proxy method. Within this method it is a little bit tricky to get the controller structures filled. This could be done by parsing the input data once more... Here is an code example for this:
    ls_input_data-name = 'INPUT'.
    GET REFERENCE OF input INTO ls_input_data-value.
    APPEND ls_input_data TO lt_input_data.
    lo_server_context = cl_proxy_access=>get_server_context( ).
    lo_payload_protocol ?= lo_server_context->get_protocol( if_wsprotocol=>payload ).
    lo_payload_protocol->set_extended_xml_handling( extended_xml_handling = 'X' ).
    lo_payload_handler = lo_payload_protocol->get_payload_handler( '<Name of structure data element>' ).
    lo_payload_input = lo_payload_protocol->get_sent_request_payload( ).
    lo_payload_handler->get_request_data_from_payload(
      EXPORTING
        payload = lo_payload_input
      CHANGING
        request_data = ls_input_data ).
    But a much easier and better way is to insert the following coding within a constructor of the generated Proxy class.
    lo_server_context = cl_proxy_access=>get_server_context( ).
    lo_payload_protocol ?= lo_server_context->get_protocol( if_wsprotocol=>payload ).
    lo_payload_protocol->set_extended_xml_handling( extended_xml_handling = 'X' ).
    As in each standard ABAP class, you can insert your own constructor within proxy classes. If you do so and insert the code in it the controller table will be filled with the needed information.
    Best Regards,
    Lars

  • Fault message in asynchronous ABAP Proxy

    Hi,
    I have a question about fault messages in asynchronous ABAP proxy server.
    The configured scenario is SOAP – XI – ABAP Proxy. Between XI and the ABAP Proxy I have configured an inbound asynchronous interface with a fault message, and then I have generated all the classes and implemented some code for exception handling in the ABAP Proxy side successfully.
    When I tested negative cases, the exception raises and it is visible in the SXMB_MONI transaction in the R/3 side, but this exception is not displayed in the SXMB_MONI of XI it just displays a successful delivery to the ABAP Proxy message.
    According the XI documentation it says “<i>In the asynchronous case, you can see a fault message in the monitoring of the Exchange Infrastructure.</i>” But this is not working.
    Am I missing something?

    Hi,
    This parameters are form group RUNTIME.
    Please check it:
    http://help.sap.com/saphelp_nw04/helpdata/en/d6/49543b1e49bc1fe10000000a114084/content.htm
    Regards,
    Wojciech

  • 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" ?>
    - <!--  Call Inbound Proxy
      -->
    - <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" ?>
    - <!--  Call Inbound Proxy
      -->
    - <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>

  • Inbound proxy failed in ECC

    Hi All,
    Inbound proxy failed in ECC with below error Please help.
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProxy</SAP:Category>
      <SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
      <SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
      <SAP:P2>ZCL_P2F_IS_AGILE_TO_SAP</SAP:P2>
      <SAP:P3>P2F_IS_AGILE_TO_SAP</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error during proxy processing An exception with the type CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor declared in a RAISING clause The database returned a value containing an error</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Chaitanya Naru

    Hi Chaitanya,
    Looks like the ABAP code failed during a call to DB. You would have to sit with ABAPer fot this to debug and see where exactly the exception is being raised. Set a debug point in Proxy code and debug the message. You can use sproxy to test this.
    Regards,
    Sanjeev.

  • 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

  • Generated Class is not called by Inbound Proxy

    Uploading data to Ztable of ECC by using inbound proxy.
    The messages are tranfered to SAP ECC from SAP XI.
    Monitoring in SXMB_MONI in SAP XI DEV can see Success flag
    Monitoring in SXMB_MONI in SAP ECC can see inbound message stored in QUEUES only.
    I configured the Application Integration Engine as per the help document.
    In Reciever XI Adapter set the addressing type URL.
    Coding is correct in the method of the generated class.
    Let me know if any configurations yet to be done.
    Let me know how to proceed furthur.
    ThankYou in Advance.

    hi
    Go to SMQR of the ECC and register and activate the queues again.
    Also ensure that u are implementing the correct methods of the proxy
    EXECUTE-SYNCHRONOUS / EXECUTE-ASYNCHRONOUS
    rgds
    Arun

  • SAP Inbound Proxy Error

    Hi Experts,
    I am facing an issue when executing inbound proxy message. After the message completed, the message status end up with Error. The error says below details.
    "Information about the method parameters is missing
    for the interface INTERFACE_NAME
    (ABAP interface, request message MT_Fault, request
    message namespace....)"
    I am also raising Fault messages from ABAP Proxy message programming. In SXMB_MONI while expanding all the messages I can able to see the application message but also i am seeing the above mention errors.
    Any Idea why this error appears?
    Thank you
    Magesh.

    Hi Diptendu - I don't think it's an issue with URL.
    Did  you register the service?
    http://<host>:<port>/ProxyServer/register?ns=http://sap.com/xi/XI/System&interface=ValueMappingReplicati
    onOutSynchronous&bean=localejbs/sap.com/com.sap.xi.services/ValueMappingApplicationSynchronous&m
    ethod=ValueMappingReplicationOutSynchronous
    Reference :
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e07dd2ae-f783-2c10-9aa6-ca69f67dd20f?QuickLink=index&…
    what is your receiver channel?

  • 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.

  • Outbound proxy in Inbound proxy

    Hi Experts,
       I am doing two way interface. JDBC asyn - proxy-JDBC asyn
    I am calling outbound proxy in inbound proxy here.
    While i am calling it is giving HTTP connection error.
    So can i call outbound proxy in inbound proxy ????
    <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>

    Outbound proxy inside inbound proxy scenario usually works fine. But few suggestions,
    1. Check if the message is failing in request side of asynchronous scenario. If this is the case then I think the error which you are getting is probably due to improper channel configuration.
    2. If problem is not the one mentioned in point 1 above then, test the proxy in transaction SPROXY of ECC as to whether outbound proxy is called while inbound proxy is executed manually in transaction SPROXY . Once you execute the inbound proxy then go to transaction "SXMB_MONI" of ECC to check whether a message which outbound proxy is required to send to PI appears over there, if it appears there that means there is no issue on programming of proxy.
    Hope it might help in finding resolution.
    Thanks,
    Amit

  • Testing Inbound Proxy

    Hi,
    I hve created one inbound asynchronous proxy at my CRM end with a fault message type. NOw , I wanna test this proxy by sending message from XI (Test message in component moni in RWB).
    HOw can i do it?
    The appraoch I am following is  by creating an outbound I/f at XI Business system with HTTP Adapter in its CC.
    Plz help if anyone of you has worked on smthing like this.
    Thanks,
    Steffi

    yes you do. Any interface flow in XI needs to have an outbound interface and an inbound interface.
    Your Inbound proxy which you have implemented in your SAP system , how will the call start to it. Which is the application that triggers the call , in other words what is the sender system?
    Irrespctive of whether you want to test your configuration using a HTTP Client or the RWB you need to have the Outbound Message interafce in XI and also the entire Configuration in Integration Directory.
    If you just want to test yoyur Proxy code, then the blog by Michal should really help.
    Regards
    Bhavesh

  • Inbound Proxy Error - JDBC to PROXY Scenario

    Hi experts,
    I am getting the following error while activating Inbound Proxy.
    Error when creating service node. [unknown]You are not authorized to use function Netzwerkadministration
    Exception of class CX_SRT_WSP_ICF
    Regards,
    Sudheer

    Hi Experts,
    Thank you for your replys.....Problem got solved......:)
    Some authorisation was missing...Now it was fine and I can activate Inbound proxy......:)
    Once again Thank you for your replys.....:)
    Regards,
    Sudheer

  • Issue while inserting a BDC program in Inbound Proxy.JDBC-- PI-- SAP.

    The scenerio is jdbcsender-sappi-inboundproxy(ECC6.0).
    The issue is related to SAP Plant Maintenance Module where  We have a requirement for creating Maintenance item
    programmatically from (SQLDatabase)Legacy Data for one of the interface.
    since there are no standard BAPIS/Idocs or function modules available from SAP side for creating the maintenance item. So I
    have written BDC program and with the help of submit statement in inbound proxy program, I am calling BDC program for
    creation of the maintenance item.
    When I tested the program independently on proxy side  the Maintenance Item is getting created successfully but when I
    executed from end-to-end ie.  SQLDATABASE->SAP PI-->SAP. The message is getting strucked into the queue and queue  got stopped on SAP.
    ECC side and the status of the message is scheduled state  on SXMB_MONI  transaction of SAP ECC.
    As the message  is in scheduled state multiple number of Maintenance Items are getting created with the same values.
    Has any one of our SAP friends, encountered this type of issue while inserting a BDC program in inbound proxy, please help 
    in fixing this issue. FYI... I am using sap pi7.0 with service pack 24 and ecc6.0
    Waiting for your kind expert guidance...
    cheers,
    Ram

    Raj,
    Thanks for the reply. I have tried registering the queues but still the same problem. the message got stuck in the queue of ECC and showing below message in queue.
    function module                                    StatusText
    SXMS_ASYNC_EXEC                  connection closed (no data)
    I have checked in the forums especially  for this issue but no one has provided the answer for this.
    Thanks and Regards
    Ram

  • Special character " (quote) in inbound proxy

    Hi folks,
    We have a scenario in which inbound proxy is implemented on SAP side. I am getting following error:-
    Error during XML => ABAP conversion (Request Message; error ID: CX_ST_DESERIALIZATION_ERROR; (/1SAI/TXS9457077FA0DEC03F30D0 XML Bytepos.: 988 XML Path: MT_SLM_INT30_LUPReviewFromLUPS(1)Title(16) Error Text: Data loss occurred when converting PROPOSED 8" U/G HRDH & ROUTE Kernel ErrorId: CONVT_DATA_LOSS)) An error occurred when deserializing in the simple transformation program /1SAI/TXS9457077FA0DEC03F30D0 Data loss occurred when converting PROPOSED 8" U/G HRDH. KHUFF GAS WELL-1050 & COMMUNICATION ROUTE FOC TO HRDH RH-K6}
    Could you please suggest me what is wrong in the data PROPOSED 8" U/G HRDH & ROUTE. I guess it is due to the use of " in the data. Could you please help me in this?
    Regards,
    Sami.

    Hi,
    The problem was with the length of that field. That field was created in XI with max length 80. During proxy generation, corresponding abap field was created with 80 char. In the message, data for that field was 81 characters At runtime, when proxy runtime tried to map the xml to corresponding abap object, it failed.
    While testing in Sproxy transaction when tried to execute after removing quote(") it was successful, as length was reduced to 80. So i went under impression that it is not working because of quote(").
    Thanks for your rersponses.

Maybe you are looking for

  • Error Message in portal application.log

    Hi all, There are error messages continually been written to application.log. Here is the path. $ORACLE_HOME/j2ee/OC4J_Portal/application-deployments/portal/OC4J_Portal_default_island_1/application.log We couldn't find out what's wrong. Portal Versio

  • How do I get to a JPEG?

    Hi, I shot some photos with the camera set to save RAW & JPEG and imported them into LR, converting the RAW to DNG as it came in. The shots are just for mucking about with LR. The Library shows one photo. If I set the Library view to show photo (file

  • Macro not working for Word.

    My macro is not working for Microsoft word. Its showing some macro settings issue. Please help.

  • Using NetBeans and Eclipse to drag and drop forms, controls etc

    Hi, can you use NetBeans and Eclipse to drag and drop like say with C# in MS Visual Studio ? like forms and listboxes, textboxes etc ??

  • Am I supposed to have to Pair the Magic Mouse evertime?

    If I turn the MM off, I have to repair it to my MBP every time I turn the mouse on.  Is this right? Also, this new mouse doesn't sit flat on the table, it slightly rocks, so the runners on the bottom are not even.  I just got this today, and it may b