Inbound Proxy synchronous implementation

Hi Experts,
I am newbie to ABAP proxy implemenation.I have to implement Inbound Synchronous ABAP Proxy. The preface looks like below.
              (a-> DT_Sender_Req)                   (b-> DT_Receiver_Req)
.Net App -
>   SAP PI7.1 -
>   SAP ECC6.0
              (<-d DT_Sender_Resp)                  (<-c DT_Receiver_Resp)
.Net application will send the purchase order and will fetch the PO details from SAP ECC6.0.The response will be send back to .Net application.To implement this , synchronous message is to be configured. I have query regarding the XI scenario configuration. Please guide on the following.
1. For .Net application, I have to get the message structure i.e. WSDL from the respective team.What all
   details I have to get from .Net team?
2. Which adapter I can use for message exchange with SAP-PI?
3. Do I have to create 4 data types(DT)
   (a) : DT_sender_Request
   (b) : DT_Receiver_Request
   (c) : DT_Receiver_Response
   (d) : DT_Sender_Response
   Should message in flow (a) and (b) have the same message structure
4. For catching the exception in SAP ECC6.0, what would be the Fault Exception structure in (c)?
Request experts to post the answers making reference to the question numbers i.e. 1,2,3,4 etc
Regards
Alice Rebecca

Alice@xi wrote:
Hi Experts,
>
>
> I am newbie to ABAP proxy implemenation.I have to implement Inbound Synchronous ABAP Proxy. The preface looks like below.
>
>               (a-> DT_Sender_Req)                   (b-> DT_Receiver_Req)
> .Net App -
>   SAP PI7.1 -
>   SAP ECC6.0
>               (<-d DT_Sender_Resp)                  (<-c DT_Receiver_Resp)
>
>
> .Net application will send the purchase order and will fetch the PO details from SAP ECC6.0.The response will be send back to .Net application.To implement this , synchronous message is to be configured. I have query regarding the XI scenario configuration. Please guide on the following.
>
> 1. For .Net application, I have to get the message structure i.e. WSDL from the respective team.What all
>    details I have to get from .Net team?
You will need to understand the data structure and thus create a sync. outbound interface and then share the WSDL with them
>
> 2. Which adapter I can use for message exchange with SAP-PI?
>
This will be a SOAP to Proxy scenario so use the SOAp adapter at the sender side and XI adapter at receiver
> 3. Do I have to create 4 data types(DT)
>    (a) : DT_sender_Request
>    (b) : DT_Receiver_Request
>    (c) : DT_Receiver_Response
>    (d) : DT_Sender_Response
yes 4 DT
>    Should message in flow (a) and (b) have the same message structure
Depends. If they are different, you mapping can handle the transformation.
> 4. For catching the exception in SAP ECC6.0, what would be the Fault Exception structure in (c)?
>
> Request experts to post the answers making reference to the question numbers i.e. 1,2,3,4 etc
>
> Regards
> Alice Rebecca
Yes use fault messages.
Additional references:
Walkthrough - SOAP  XI  RFC/BAPI
Fault messages -
Fault Message Types - A Demo (Part 1)
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI

Similar Messages

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

  • Synchronous Inbound Proxy: Request Responce Type

    Hi,
    I am new to ABAP and i have to work on a inbound proxy which is synchronous
    ie a request-responce scenario has to be implemented.
    Can some one guide me how to initiate.
    Regards,
    vickey
    Any replys will be highly appreciated and rewarded.

    hi
    check with this wiki page:
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/09/19/request-responseSCENARIOININBOUNDPROXY 
    If there is a scenario in which the request coming from the other system and based on that request, a response is to be send from ABAP to that system, inbound proxy with Synchronous method is used.
    The class is created by the XI and in the method execute_synchronous, the ABAP code is written.
    The XI provides the input and output structures.
    The ABAP side receives the request from the input structure and sends back the response to the output structure. We will go through these steps one by one. If clearly understood the whole concept is very easy.
    Step1: To declare the internal table/work area of the type of input structure:
            wa_input like input-mt_get_notification-message_payload.
    (Here we have given the whole path as highlighted through ovals in the figure above)
    Step2:  To move the data coming from the input structure to the defined workarea/internal table:
           move input-mt_get_notification-message_payload to wa_input.
    Now the input data is in the desired internal table /work area which can be used to fetch the desired values and send the result back to XI through output structure.
    2) To send the data to XI through output structure.
    Step1: Like input structure, the naming convention for output structure also follows the
    whole path
    call method me->get_notif_or_task_details
            exporting
              p_input         = wa_input
            importing
              p_output        =
           output-mt_notification_response-message_payload-sapresponse
            changing
              it_l_bapiret2   = it_bapiret2
            exceptions
              errors_occurred = 1
              others          = 2
          if sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
               WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          endif.
    (Code Snippet for Method)
    Here this method fetches the required data in the table p_output and assign it to the internal table
    SAPRESPONCE of the output structure which goes to XI.
    In this way, the synchronous method can be used for inbound proxy in case of request-response scenario.
    regards
    Manish

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

  • 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

  • RFC - Java Proxy (Synchronous) invoking method

    Hi,
    I have problems to call my inbound java proxy.
    My scenario consist of send RFC -> Java Proxy (Synchronous)
    Proxy this registered
    http://hcp095.intra.csc.es:50100/ProxyServer/register?ns=http://csc.es/xi/rca&interface=Z_RCA_SCS&bean=ZRCASCS_PortTypeBean&method=zRCASCS
    ejb-jar.xml:
    <ejb-jar>
        <description>EJB JAR description</description>
        <display-name>EJB JAR</display-name>
        <enterprise-beans>
            <session>
                <ejb-name>ZRCASCS_PortTypeBean</ejb-name>
                <home>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundHome4</home>
                <remote>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundRemote4</remote>
                <local-home>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocalHome4</local-home>
                <local>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocal4</local>
                <ejb-class>es.csc.xi.rca.ZRCASCS_PortTypeBean</ejb-class>
                <session-type>Stateless</session-type>
                <transaction-type>Container</transaction-type>
            </session>
        </enterprise-beans>
    </ejb-jar>
    Class Impl:
    package es.csc.xi.rca;
    public class ZRCASCS_PortTypeImpl extends AbstractProxy implements ZRCASCS_PortType {
    public ZRCASCSResponse_Type zRCASCS(ZRCASCS_Type parameters) throws ZRCASCSException_Message_Exception, SystemFaultException,  ApplicationFaultException{
            //throw new RuntimeException();
            Rca_ws a = new Rca_ws();
            return a.zRCASCS(parameters);
    Error: XI_Monitor 
    <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error invoking method zRCASCS of proxy bean $Proxy305: cannot assign instance of com.sap.guid.GUID to field com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl.guid of type com.sap.guid.IGUID in instance of com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method zRCASCS of proxy bean $Proxy305: cannot assign instance of com.sap.guid.GUID to field com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl.guid of type com.sap.guid.IGUID in instance of com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
    Error: defaultTrace
    #hcp095.intra.csc_XID_19271950#ANGUZMAN#ec20b7f019f611de98340011259e6830#
    SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain##
    #com.sap.aii.proxy.xiruntime.core.XmlProxyException: Error invoking method zRCASCS of proxy bean $Proxy366:
    cannot assign instance of com.sap.guid.GUID to field com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl.guid
    of type com.sap.guid.IGUID in instance of com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl
         at com.sap.aii.proxy.xiruntime.core.XmlProxyJ2EE.call(XmlProxyJ2EE.java:192)
         at com.sap.aii.proxy.xiruntime.core.XmlProxy$ProxyBeanCaller.call(XmlProxy.java:225)
         at com.sap.aii.proxy.xiruntime.core.XmlProxy.processRequest(XmlProxy.java:194)
         at com.sap.aii.proxy.xiruntime.core.XmlInbound.processRequestMessage(XmlInbound.java:126)
         at com.sap.aii.proxy.xiruntime.core.XmlInbound.processMessage(XmlInbound.java:83)
         at com.sap.aii.proxy.xiruntime.sbeans.JPRBean.onMessage(JPRBean.java:158)
         at com.sap.aii.proxy.xiruntime.sbeans.JPRLocalLocalObjectImpl0_0.onMessage(JPRLocalLocalObjectImpl0_0.java:175)
         at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:276)
         at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1049)
         at com.sap.aii.af.ra.ms.impl.core.queue.RequestConsumer.onMessage(RequestConsumer.java:119)
         at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:850)
         at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:180)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    If somebody can help me.
    Thank you very much

    Solved!!!
    to assign library references to the project application-j2eeengine.xml
    com.sap.aii.proxy.xiruntime
    com.sap.aii.messaging.runtime
    com.sap.xi.util.misc
    com.sap.guid

  • Urgent: Error in Inbound Proxy in SCM system

    Hi All
    Please give your inputs to solve following problem I am facing. I am working on XI first time so please help me out to solve the following problem. Please let me know if you need any more info.
    Thanks a lot for your help guys.
    I am sending ORDERS.ORDER05 from R/3(ECC6.0) to SCM (5.0) through XI. I am using standard message interface ReplenishmentOrderNotification_In to send data to ICH configured on SAP SCM System.
    I am using XI adapter at receiver end. My message successfully going to SCM. SXMB_MONI, its giving error. After clicking on error flag it displays a table with 3 entries, please find them below.
    1. Start of inbound processing: ReplenishmentOrderNotification (ID 0000000000202027) 032(/SCMB/ORDER)
    2. TST 20080429202851 (type MessageCreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
    3. Partner key(s) not found 042(/SCMB/MDL_BASIC)
    Please find the XML message from ERROR node from Inbound Proxy
    <?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>Application</SAP:Category>
      <SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="http://sap.com/xi/SCMBasis/Global">ReplenishmentOrderNotificationFault</SAP:ApplicationFaultMessage>
      <SAP:Stack>Application has thrown an exception</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Please find contents of Trace XML message from Inbound proxy
    <?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 = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T01:31:18Z 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 = 48165647672B03B5E10080000A0C640C</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 : XBTR0003</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTR0003</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 ReplenishmentOrderNotification_In*</Trace>
      <Trace level="1" type="T">select interface namespace http://sap.com/xi/SCMBasis/Global</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 = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T16:19:34Z 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" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</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">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 000</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <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 = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T20:52:28Z 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" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</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">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 002</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <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 = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = RAJARANGA</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T22:34:19Z 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" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</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">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 004</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <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 = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = RAJARANGA</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T22:35:19Z 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" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</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">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 006</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <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 = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = RAJARANGA</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T22:41: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" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</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">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 008</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <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 = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-05-01T00:07:18Z 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" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</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">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 010</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <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 = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-05-01T00:30:07Z 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="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" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 012</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <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 = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-05-01T00:53:39Z 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" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</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">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 014</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <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 = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-05-01T01:04:22Z 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" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</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">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
    Regards
    Amol

    Hi All
    Thanks for your inputs, we are a step ahead now. We applied few notes I will be posting details soon. At the moment we stuck at one poin, its giving a configuration related error.  Please find the process log from SXMB_MONI from SCM system. It is saying Buyer missing in fact we have configured BP01 in SCM system and same we are getting from ECC system.
    Hope to hear from you soon. Thanks a lot for your inputs.
    ReplenishmentOrderNotificationFault
    Proxy Class (Generated)
    Detailed Information
    Start of inbound processing: ReplenishmentOrderNotification (ID 0000000000202043) 032(/SCMB/ORDER)
    The active implementation of BAdI '/SCMB/BIF_I_REPLORD' 'BEFORE_CONVERSION' has been run  080(/SCMB/BIF_COMMON)
    TST 20080508141414 (type MessageCreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
    The active implementation of BAdI '/SCMB/BIF_MI_PARTYID' 'BEFORE_MASTER_DATA_ACCESS' has been run  080(/SCMB/BIF_COMMON)
    Start generic process type determination 000(/SCMB/BIF_CU)
    Process type could not be determined - search for standard process type 002(/SCMB/BIF_CU)
    Standard process type (ICH) determined successfully 013(/SCMB/BIF_CU)
    Start action determination for addresses 070(/SCMB/BIF_CU)
    No Customizing found; standard action is 'map all addresses' 072(/SCMB/BIF_CU)
    End of action determination for addresses 071(/SCMB/BIF_CU)
    Start partner role determination 060(/SCMB/BIF_CU)
    Partner role is 'buyer (sold-to party)' 063(/SCMB/BIF_CU)
    Partner role determination completed successfully 061(/SCMB/BIF_CU)
    TST 20080508000000 (type CreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
    The active implementation of BAdI '/SCMB/BIF_MI_ITMBPRT' 'BEFORE_MASTER_DATA_ACCESS' has been run  080(/SCMB/BIF_COMMON)
    The active implementation of BAdI '/SCMB/BIF_MI_PRODID' 'BEFORE_MASTER_DATA_ACCESS' has been run  080(/SCMB/BIF_COMMON)
    TST 20081027000000 (type DeliveryPeriodStartDateTime, item 00010, sched. line 1) is local, interpret. as UTC 024(/SCMB/BIF_MI)
    Order 4500000105 item 00010: 'DeliveryPeriodEndDateTime' missing in schedule line 1 090(/SCMB/ORDER)
    The active implementation of BAdI '/SCMB/BIF_I_REPLORD' 'AFTER_CONVERSION' has been run  080(/SCMB/BIF_COMMON)
    BOL processing started for object /SCA/CL_SVORDER process name REPLORDER 006(/SCMB/DM_BOL)
    Start: read ODM order 250(/SCMB/ORDER)
    End: read ODM order 251(/SCMB/ORDER)
    Start: validation framework 254(/SCMB/ORDER)
    Validation started for validation profile POC1 (ICH - REPLORDER - HEADER) 606(/SCMB/DM_BOL)
    Business partner 'buyer' is missing in order 4500000105 021(/SCMB/ORDER)
    Validation for val. prof. POC1 (ICH, REPLORDER, HEADER) ended with errors and warnings 608(/SCMB/DM_BOL)
    End: validation framework 255(/SCMB/ORDER)
    Start alert notification for application ALEN - time 08.05.2008 19:15:18 - process mode F 504(/SCMB/ANOT)
    End of alert notification for application ALEN - time 08.05.2008 19:15:18 - process mode F 525(/SCMB/ANOT)
    Start: write ODM order 252(/SCMB/ORDER)
    End: write ODM order 253(/SCMB/ORDER)
    BOL processing ended for object /SCA/CL_SVORDER process name REPLORDER 007(/SCMB/DM_BOL)
    End inb. proc.: ReplenishmentOrderNotification (ReplenishmentOrder ID ) 033(/SCMB/ORDER)

  • Can I supress BPM for Asyn outbound and syn inbound proxy interface

    Hi all,
    Is there any other alternate to remove the BPM at asyn outbound and syn inbound proxy interface. Reason because I can create another outbound proxy interface at the receiver. But at receiver side we already invested huge code to develop the sync server proxy. So the intension is, with out disturbing the code Can I make the message flow with out BPM?
    Because the reason of removing BPM is for a simple interface like this I don't want to use BPM. souce is JDBC and receiver is ECC 6.0. I know with out BPM it can not be achieved but in PI 7.1 EHP 1 by any chance can we do?
    I mean during response mapping from server proxy shall we use look up function to achieve?

    This bean I have to use at sender channel right?
    Yes
    I mean is it is limited to JMS adapter?
    No
    You can find more information in the Wiki which deals with FILE  to RFC synchronous...using the above Module

  • 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

  • PI inbound proxy

    Dear All,
    We are planning build one proxy to recieve the file from thirdy party to SAP though PI system . So I have couple of questions in this regard.
    1)  How is this proxy in ABAP side trigger to run ? Do we need to schedule any background job run this in ECC side or PI will trigger the program to run ?
    2) Can we put the files in apllication server using ABAP inbound proxy ?
    3) Can we include selection screens to the inbound ABAP proxy program ?
    4) Is there any options in proxy to handle DATA errors in the file ( Like in IDoc we can see 51 status if any failure and we can reprocess )
    5) Can emails sent from proxy for any processing errors and data mismatch ( send and receive ) .
    6) How can we monitor and reprocess the proxy ( sxmb_mony ? any )
    Thanks all,
    Vinay.

    Hi Vinay,
    1) How is this proxy in ABAP side trigger to run ? Do we need to schedule any background job run this in ECC side or PI will trigger the program to run ?
    Ans: When your File Communication channel picks a file, a process will start and once the message has been transformed in PI, PI will automaticall trigger the inbound Proxy.
    2) Can we put the files in apllication server using ABAP inbound proxy ?
    Ans: What do you mean by this? Are asking if the ABAP inbound proxy can save the message as a file in the application server? If yes, it is possible. You just need to modify the implemented class of your Inbound proxy to save a file in the app server.
    3) Can we include selection screens to the inbound ABAP proxy program ?
    Ans: Yes, you may add codes in your implemented class to call and use a selection screen.
    4) Is there any options in proxy to handle DATA errors in the file ( Like in IDoc we can see 51 status if any failure and we can reprocess )
    Ans: Yes, you may validate the incoming message of your inbound proxy and apply exception handling if error occured.
    5) Can emails sent from proxy for any processing errors and data mismatch ( send and receive ) .
    Ans: I think this is possible in ABAP coding. But if you wanted to send notification emails when transformation error occurs during mapping, you can do it using Alert Configuration.
    6) How can we monitor and reprocess the proxy ( sxmb_mony ? any )
    Ans: Since your scenario is File to ABAP proxy, the only way to reprocess is to send/place another file on the source directory to trigger the inbound proxy.
    Let me know if this helps.
    Regards,
    Jenny

  • Inbound proxy code

    Hi All,
    I have created one inbound proxy. I implemented the class used and i regenrated it.
    But method name was different before and after.
    My code is gone. Is there any way to retrieve it again??
    Thanks,
    Archana

    Hi,
    The issue is resolved. i did not save the changes to class method and created new implementation with my old method.
    So, i could retrieve my code.
    Thanks,
    Archana

  • CANNOT_READ_PALOAD error with SOAP to PROXY Synchronous interface

    Hi,
       Problem with SOAP to PROXY Synchronous interface.
    In Production client, some times we are getting the below shown error in SXMB_MONI. There is no Inbound payload also.
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Unable to read payload from the message object</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Please suggest me to resolve this.
    Thanks in advance,
    Hari.

    Hi Hari,
    In your case, check SAP Notes: 1082111 and  1060723.
    Regards,
    P.Rajesh

  • Synchronos inbound ( proxy ) configuratin issue ?

    Hello Friends,
    I have designed a Synchronos inboud interface where 2 parameters are comming in as request and response is a str with 10 fields. I could have easily done this using RFC,but thought to give a try to proxies...
    I have creaed server proxy ( inbound interface ) it has let me created classes and etc. Now my problem is how I can configure the things in integration builder ?
    on my search I went to following artical.... seems too much similar what I need:
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50b63e8f-a4bb-2a10-e9b1-ba803fd06739&overridelayout=true
    My problem starts with : Configuring a Service Provider
    I cant find t-code SOAMANAGER  ( I am  having PI 3.0 )............. so could anyone please guide me how I can configure the senario , to get the WSDL ?
    I  went to following thread too: Re: werb services to proxy- synchronous scenario
    where Abhishek is mentioning to have 2 MI's ? but in artical above , he only create one SI ??
    Regards,
    Edited by: Shah H on Nov 26, 2009 2:22 PM

    Hello,
    I am facing a bit problem in doing configuration, ( I successfuly did few for Asynchro, but this is my first sycnhro-- so not sure what I am doing wrong )
    As I said I have two MI's
    1- MI_Stock_In ( syncro inbound interface ) this I use to create server proxy
    2- MI_Stock_Out ( synchro- outbound interface ) this is the interface which I connect or expose to External system.
    So in Reciver Determination:
    Sender:
    Service = External_System
    Interface = MI_Stock_Out
    namespace = xyz.....
    Reciever Agrement:
    Sender:
    Service = External_System
    Reciver:
    Service = r3system
    Interface = MI_Stock_In
    namespace = xyz.....
    and CC ( adapter type XI )
    Interface Determination:
    Sender:
    Service = External_System
    Interface = MI_Stock_Out
    namespace = xyz.....
    Reciver:
    Service = r3system
    Configure inbound interface:
    name = MI_StockCompare
    name space= xyz....
    I have left blank interface mapping, as no mapping is define....
    but when colleuge consume the wsdl, he is getting error, reciver is not known ....
    Any tip idea what I am doing wrong ?
    Thanks and regards,
    I am having also confusion,, as its synchro---- it means my sender ( external_system ) is at the same time reciver..... so do I need to have r3system as reciver ??
    is there any example tutorail for this ( synchro.... inbound interface and sychrou outbound interface ) ??
    Edited by: Shah H on Nov 27, 2009 11:05 AM
    Edited by: Shah H on Nov 27, 2009 11:06 AM

  • 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

Maybe you are looking for

  • Need help getting music off ipod

    I used to have 2 libraries on my itunes (mine & hubby's). Now it only shows hubby's music library - no classical. How do I get the missing music that is on my ipod back in the itunes library so I can sync my new ipod and get all the music?

  • Duplicate photo albums on my phone??

    When I create an album for my photos to go on my iphone, why does the phone create a duplicate album?

  • 500: Registration failed. Check Mobile user and activation code

    Hi all, I am currently implementing SAP's customer financial fact sheet in our landscape. I have tested the service and it is working and creation application and application connections are also done. However, when I tried to log in using the applic

  • Modding 5200 to 5500 it damaged tvout

    I have a problem. I changed the bios of my video card and now the TVOUT does not work. how can i do to repair this problem? my video card is: ms-8911- fx5200 td128. tv+dvi+svideo. I install the bios original but "tvout" not signal.. Posting in Spanis

  • Possible to Clean this up?

    I have ran trhough the basic cleanup steps and I can get the background noises gone but then the guy's voice sounds robotic.(Which I expected) I am wondering if there is a series of steps I can do to get the audio cleanup so the end result is not so