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

Similar Messages

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

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

  • 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

  • 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

  • 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

  • Aysnch Proxy calling from Inbound Proxy

    Hello Experts,
    My scenario:-
    Legacy sending File to Inbound proxy and from Inbound proxy I am calling the outbound proxy method to send the data back to Legacy system.
    Its like File request -Inbound Proxy- Outbound Proxy Response- File.
    FileRequest-Inbound Proxy----message in R3 as well in XI moni is successful.
    File Outbound response-File-----message in R3 is coming as empty and because of this the message fails in Xi moni.
    I tried to debug the scenario using test tab with the moni payload, I am able to see the data populated in debugging mode, But after the Outbound method is called the response message is coming is empty. commit work is also used inside outbound method.
    I tried every possible ways,but not getting any clue.
    chirag

    Hi,
    Just check...........in the inbound proxy code, the structure of the response msg is updated as the current structure of response msg.......may be you are filling the data in the old structure of response msg and then asssinging it in the outbound proxy call.......you need to fill the data in the new structure of response msg in your inbound proxy code.
    Regards,
    Rajeev Gupta

  • Calling Outboud Proxy from inbound proxy

    Hi friends,
    We have a scenarion where we need to call an Outbound proxy from an inbound proxy. I can see the payload after the successful execution of the proxy and is exactly the same that we want. But when i check it in the sxmb_moni for the status of message, it is 'InProcess' with Q.Status as STOP.
    Can any body suggest what could be the possible reasons. We are using file adapter.
    Thanks,
    Kulwant

    Hi,
    This might help you
    /people/krishna.moorthyp/blog/2005/12/23/monitoring-for-processed-xml-messages-in-abap-proxy
    Check whethere the  communication http, http service are  mentioned correctly.
    The following thread might help you
    Calling Outbound ABAP Proxies:
    Regards
    Agasthuri Doss

  • Inconsistency in receiveing the messages in inbound Proxy in SAP  from XI

    Hi All,
    We have a Scenario where our Source System is Websphere MQ and target system is SAP Deposit Management System.
    To post the data in SAP DM we are using inbound  ABAP Proxy
    There is an inconsistency in receiveing the messages in inbound Proxy.
    eg  When multiple messages are put into a MQ Queue only few of them are being picked up by Inbound Proxy.
    Thanks in Advance

    Hi Amit,
    This problem can be found only by analysing it in RWB. Just analuse via RWB or MONI and check the payload at sender side and receiver side then you can find the problem.
    I think in the sender communication channel it has the problem. if it is there in Sender side payload then there would be missing in the mapping also. Just check that the top parent of target is gettting generated with some messages which are missing.
    Warm Regards,
    Vijay

  • Error while calling secured OSB proxy from BPEL

    Hi,
    I have a OSB Proxy service to which I have applied OWSM Policy:
    oracle/wss_username_token_service_policy
    In the Setting:
    Process WS-Security Header is set to Yes
    While calling this Proxy from BPEL I tried to append binding properties, I tried the following options:
    option1:
    wsseHeaders=credentials
    wssePassword=welcome1
    wsseUsername=weblogic
    option2:
    oracle.webservices.auth.password=welcome1
    oracle.webservices.auth.username=weblogic
    But neither of them work and I get the following error:
    <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
    <con:errorCode>BEA-386200</con:errorCode>
    <con:reason>General web service security error</con:reason>
    <con:location>
    <con:path>request-pipeline</con:path>
    </con:location>
    </con:fault>
    <Sep 21, 2010 9:49:30 AM PDT> <Error> <OSB Security> <BEA-387022> <An error ocur
    red during web service security inbound request processing [error-code: Security
    HeaderUnmarshallingError, message-id: 3659922647318344420--645cdd1d.12b2fe0c158.
    -7e45, proxy: OSBTest/Proxy Services/PrivatePersonnelDB_PS, operation: null]
    --- Error message:
    oracle.wsm.security.SecurityException: WSM-00069 : The security header is missin
    g.
    at oracle.wsm.security.policy.scenario.processor.UsernameTokenProcessor.
    verify(UsernameTokenProcessor.java:218)
    at oracle.wsm.security.policy.scenario.executor.WssUsernameTokenScenario
    Executor.receiveRequest(WssUsernameTokenScenarioExecutor.java:123)
    at oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor
    .execute(SecurityScenarioExecutor.java:530)
    at oracle.wsm.policyengine.impl.runtime.AssertionExecutor.execute(Assert
    ionExecutor.java:41)
    at oracle.wsm.policyengine.impl.runtime.WSPolicyRuntimeExecutor.executeS
    impleAssertion(WSPolicyRuntimeExecutor.java:608)
    Truncated. see log file for complete stacktrace
    I have even tried to enable HTTP basic Authentication for the service, but did not work.
    Any help is highly appreciated.
    Thanks.

    Hi,
    I have applied oracle/wss_username_token_service_policy for my proxy service and trying to test that from OSB Test Console. I am getting below error,
    "[OSB Security - OWSM:387253]Failed to initialize Owsm Credential Manager. Please validate the Keystore Configuration"
    When i have launched Test Console for this proxy, i have observed in Security part, oracle/wss_username_token_client_policy is appearing. I am not sure why oracle/wss_username_token_client_policy is appearing there when i applied oracle/wss_username_token_service_policy to my proxy service.
    Also do i have to need to configure any Keystore for oracle/wss_username_token_service_policy, If so please tell me the process.
    If no key store is required where will the credentials be stored.
    Thanks
    Rajesh

  • 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

  • Data is not showing in R/3 ztable whlie creating XI inbound proxy.

    Hi experts,
        I am creating an XI inbound proxy for zxx_stockyard_price_ib_dt ,
    I created Ztable(this structure contains both filename and data structure)  in R/3 and i am writing  a code in sproxy to fetch the data from XI to R/3, R/3  is to fill and store the data in a ztabe .
    XI data file is ok, however , when executed ,the input file of XI is not reflecting in the R/3 Ztable,
    I need a help in this scenario,
    here is the peice of  code,
    METHOD zxx_ii_stockyard_price_ib_mi~stockyard_price_ib_mi.
      DATA : it_zxx_stockyard_price_ib_dt        TYPE  table of zxx_stockyard_price_ib_dt ,   " input batches from file
             wa_zxx_stockyard_price_ib_dt        TYPE zxx_stockyard_price_ib_dt         ,
             i_zrva_trv_interfa                  TYPE  TABLE OF zrva_trv_interfa ,
             wa_zrva_trv_interfa                 TYPE  zrva_trv_interfa.
    ******fill input internal table from XI
      wa_zxx_stockyard_price_ib_dt = input-stockyard_price_ib_mt.
    *fetch the records from XI.
      LOOP AT it_zxx_stockyard_price_ib_dt INTO wa_zxx_stockyard_price_ib_dt.     " looping input data of XI nd moving the data to R3.
        MOVE-CORRESPONDING wa_zxx_stockyard_price_ib_dt TO wa_zrva_trv_interfa.
        APPEND wa_zrva_trv_interfa TO i_zrva_trv_interfa.
       Modify zrva_trv_interfa FROM WA_zrva_trv_interfa.
      ENDLOOP .
      IF NOT i_zrva_trv_interfa IS INITIAL.
        LOOP AT i_zrva_trv_interfa INTO wa_zrva_trv_interfa.
          MODIFY zrva_trv_interfa FROM wa_zrva_trv_interfa.
          CLEAR wa_zrva_trv_interfa.
        ENDLOOP.
      ENDIF.
      FREE i_zrva_trv_interfa.
    ENDMETHOD.
    when execute and debugged i found the values are not showing in internal table i_zrva_trv_interfa (loop at i_zrva_trv_interfa), where i am going wrong?

    > here is the peice of  code,
    >
    > METHOD zxx_ii_stockyard_price_ib_mi~stockyard_price_ib_mi.
    >   DATA : it_zxx_stockyard_price_ib_dt        TYPE  table of zxx_stockyard_price_ib_dt ,   " input batches from file
    >          wa_zxx_stockyard_price_ib_dt        TYPE zxx_stockyard_price_ib_dt         ,
    >          i_zrva_trv_interfa                  TYPE  TABLE OF zrva_trv_interfa ,
    >          wa_zrva_trv_interfa                 TYPE  zrva_trv_interfa.
    >
    > ******fill input internal table from XI
    >   wa_zxx_stockyard_price_ib_dt = input-stockyard_price_ib_mt.
    >  
    I think here at this place you have problem. As per your code you have moved the input-stockyard_price_ib_mt to wa_zxx_stockyard_price_ib_dt BUT you have not appended to the internal table it_zxx_stockyard_price_ib_dt.
    If I am wrong then make sure it_zxx_stockyard_price_ib_dt is filled correctly before you loop on it.
    also add the below check befor looping.
    IF NOT it_zxx_stockyard_price_ib_dt is INITIAL.
    > *fetch the records from XI.
    >   LOOP AT it_zxx_stockyard_price_ib_dt INTO wa_zxx_stockyard_price_ib_dt.     " looping input data of XI nd moving the data to R3.
    >     MOVE-CORRESPONDING wa_zxx_stockyard_price_ib_dt TO wa_zrva_trv_interfa.
    >     APPEND wa_zrva_trv_interfa TO i_zrva_trv_interfa.
    > *    Modify zrva_trv_interfa FROM WA_zrva_trv_interfa.
    >   ENDLOOP .
    ENDIF.    "IF NOT it_zxx_stockyard_price_ib_dt is INITIAL.
    >
    >   IF NOT i_zrva_trv_interfa IS INITIAL.
    >     LOOP AT i_zrva_trv_interfa INTO wa_zrva_trv_interfa.
    >       MODIFY zrva_trv_interfa FROM wa_zrva_trv_interfa.
    >       CLEAR wa_zrva_trv_interfa.
    >     ENDLOOP.
    >
    >   ENDIF.
    >
    >   FREE i_zrva_trv_interfa.
    >
    > ENDMETHOD.
    >
    >
    > when execute and debugged i found the values are not showing in internal table i_zrva_trv_interfa (loop at i_zrva_trv_interfa), where i am going wrong?
    Regards,
    Sarvesh

  • Program code for inbound proxy

    Hello,
    I would like to ask for your help. I am creating an abap program for an inbound proxy to update tables.
    It doesn't get the value listed in the file. In the method section, I have created the following codes:
    DATA:  receipt TYPE zgiserdata-receipt,
                material_slip TYPE zgiserdata-matslip,
                plant TYPE zgiserdata-plant,
                material_number TYPE zgiserdata-matno,
                new_serial TYPE zgiserdata-new_serial,
                old_serial TYPE zgiserdata-old_serial,
                warrex_date TYPE zgiserdata-warrexdate,
                posting_date TYPE zgiserdata-postdate.
    Convert input parameters
      receipt = input-GOODS_ISSUE_SERIALIZED_CREATE-GOODS_ISSUE-reciept.
      material_slip = input-GOODS_ISSUE_SERIALIZED_CREATE-GOODS_ISSUE-material_slip.
      plant = input-GOODS_ISSUE_SERIALIZED_CREATE-GOODS_ISSUE-plant.
      material_number = input-GOODS_ISSUE_SERIALIZED_CREATE-GOODS_ISSUE-material_number.
      new_serial = input-GOODS_ISSUE_SERIALIZED_CREATE-GOODS_ISSUE-new_serial.
      old_serial = input-GOODS_ISSUE_SERIALIZED_CREATE-GOODS_ISSUE-old_serial.
      warrex_date = input-GOODS_ISSUE_SERIALIZED_CREATE-GOODS_ISSUE-warrex_date.
      posting_date = input-GOODS_ISSUE_SERIALIZED_CREATE-GOODS_ISSUE-posting_date.
    Debugged on 'receipt', the value I got is 'This is a string 1' instead of the record that is in the file.
    'This is a string 2' for 'material_slip', so on and so forth.
    Checked on the XI side that the records in the file is being transmitted without any errors. I tested this through SPROXY. Got the message that is executed with no errors, however, I got the values mentioned above instead of the values in the file being sent to XI.
    Can you please help me what needs to be checked in order to have the values that are in the file being sent to XI?
    Thank you.

    Hi Jho,
    >>>Debugged on 'receipt',
    How did you try to debug the proxy? I belive you tried debugging the proxy using SPROXY transaction code. If you use SPROXY transaction code by default the values are filled as 'This is a string 1 .. n so on..
    I would suggest you to copy the xml payload from XI and then in SPROXY transaction code paste the payload and then trigger the proxy in debugging mode.
    Or search in sdn how to debug proxy. You can use that guide to debug proxy real time. Guide is also available in some SAP Note. Dont remember the Note number.
    If there is anything else you want to know let us know.
    Regards,
    Sumit

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

  • Automating Cash Journal Posting using inbound proxy interface and upload program

    Hi Experts,
    I have a requirement where in cash journal posting needs to be carried out automatically by an inbound interface on a periodic basis and at the start during cut over an upload program needs to be used to upload beg balance data . For this purpose I have used BAPI_CASHJOURNALDOC_CREATE to save cash journal entries along with BAPI TRANSACTION COMMIT.
    Once the Data is successfully saved I am using FM FCJ_GET_DATA_FOR_SCREEN to get prerequisite data for the FM FCJ_POST_ALL which is used by the Standard cash journal program internally to post the saved data. ( I got this by debugging the standard transaction and both FMs are not yet released )
    The issues I am facing is that the the FM FCJ_POST_ALL does not always post the data it behaves in random fashion i.e some times it posts the entries where as sometimes it does not post the entries.
    I have tried using commit work after the FM but that also does not result in consistent behavior of the program. One more issue is the i am not allowed to use commit work in a an inbound proxy so how do i proceed ?
    I am attaching the code for further analysis:
    DATA: LIT_TCJ_TRANS_NAMES TYPE TABLE OF TCJ_TRANS_NAMES,
             LWA_TCJ_TRANS_NAMES TYPE TCJ_TRANS_NAMES,
             LV_WAIT             TYPE BAPITA-WAIT VALUE '1',
             LV_RECORD_NO        TYPE SY-TABIX.
       DATA : LIT_POSTING        TYPE STANDARD TABLE OF ISCJ_POSTINGS,
              LIT_WTAX_ITEMS     TYPE STANDARD TABLE OF TCJ_WTAX_ITEMS,
              LIT_SPLIT_POSTINGS TYPE STANDARD TABLE OF ISCJ_POSTINGS,
              LIT_CPD            TYPE STANDARD TABLE OF TCJ_CPD.
       DATA: LV_BEG_BALANCE      TYPE CJAMOUNT,
             LV_TOTAL_RECEIPTS   TYPE CJAMOUNT,
             LV_TOTAL_PAYMENTS   TYPE CJAMOUNT,
             LV_TOTAL_CHECKS     TYPE CJAMOUNT,
             LV_RUN_BALANCE      TYPE CJAMOUNT,
             LV_RUN_CASH_BALANCE TYPE CJAMOUNT,
             LV_NUMB_OF_REC      TYPE I,
             LV_NUMB_OF_PAYM     TYPE I,
             LV_NUMB_OF_CHECKS   TYPE I.
       DESCRIBE TABLE GIT_CJ LINES GV_TOTAL_RECORDS.
       SELECT MANDT COMP_CODE TRANSACT_NUMBER LANGU TRANSACT_NAME LONG_TEXT
          FROM TCJ_TRANS_NAMES
          INTO TABLE LIT_TCJ_TRANS_NAMES
          WHERE LANGU = GC_EN.
       IF SY-SUBRC <> 0.
         MESSAGE 'No Business Transaction maintained for Company Code in this client'(016) TYPE GC_I.
         LEAVE LIST-PROCESSING.
       ENDIF.
       DESCRIBE TABLE GIT_CJ LINES GV_TOTAL_RECORDS.
       LOOP AT GIT_CJ INTO GWA_CJ.
         LV_RECORD_NO = SY-TABIX.
         CLEAR: GS_HEADER_BAPI,
                GS_CJ_KEY,
                GWA_ITEMS.
         REFRESH: GIT_ITEMS,
                  GIT_RETURN.
         GS_HEADER_BAPI-COMP_CODE    = GWA_CJ-BUKRS.
         GS_HEADER_BAPI-CAJO_NUMBER  = GWA_CJ-CJNR.
         GS_HEADER_BAPI-CURRENCY     = GC_PHP.
         CLEAR LWA_TCJ_TRANS_NAMES.
         READ TABLE LIT_TCJ_TRANS_NAMES INTO LWA_TCJ_TRANS_NAMES WITH KEY COMP_CODE     = GWA_CJ-BUKRS
                                                                          LANGU         = GC_EN
                                                                          TRANSACT_NAME = GWA_CJ-BTNAM.
         IF SY-SUBRC = 0.
           GWA_ITEMS-TRANSACT_NUMBER = LWA_TCJ_TRANS_NAMES-TRANSACT_NUMBER.
           GWA_ITEMS-P_RECEIPTS        = GWA_CJ-CJRAT.
           GWA_ITEMS-TAX_CODE          = GWA_CJ-TXCOD.
           GS_HEADER_BAPI-BP_NAME      = GWA_CJ-BPNAM.
           GWA_ITEMS-POSITION_TEXT     = GWA_CJ-POTXT.
           CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
               INPUT  = GWA_CJ-LIFNR
             IMPORTING
               OUTPUT = GWA_ITEMS-VENDOR_NO.
           CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
               INPUT  = GWA_CJ-KUNNR
             IMPORTING
               OUTPUT = GWA_ITEMS-CUSTOMER.
           PERFORM SUB_DATE_FROMAT_BAPI  CHANGING  GWA_CJ-BLDAT
                                                   GS_HEADER_BAPI-DOC_DATE.
           PERFORM SUB_DATE_FROMAT_BAPI  CHANGING   GWA_CJ-BUDAT
                                                    GS_HEADER_BAPI-PSTNG_DATE.
           GS_HEADER_BAPI-REF_DOC_NO   = GWA_CJ-XBLNR.
           GS_HEADER_BAPI-ALLOC_NMBR   = GWA_CJ-ALLNO.
           CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
               INPUT  = GWA_CJ-KOSTL
             IMPORTING
               OUTPUT = GWA_ITEMS-COSTCENTER.
           CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
               INPUT  = GWA_CJ-PRCTR
             IMPORTING
               OUTPUT = GWA_ITEMS-PROFIT_CTR.
           APPEND GWA_ITEMS TO GIT_ITEMS.
           CALL FUNCTION 'BAPI_CASHJOURNALDOC_CREATE'
             EXPORTING
               HEADER              = GS_HEADER_BAPI
             IMPORTING
               COMPANY_CODE        = GS_CJ_KEY-COMP_CODE
               CASH_JOURNAL_NUMBER = GS_CJ_KEY-CAJO_NUMBER
               FISCAL_YEAR         = GS_CJ_KEY-FISC_YEAR
               CASH_JOURNAL_DOC_NO = GS_CJ_KEY-POSTING_NUMBER
             TABLES
               ITEMS               = GIT_ITEMS
               RETURN              = GIT_RETURN.
           IF GIT_RETURN IS NOT INITIAL.
             READ TABLE GIT_RETURN INTO GWA_RETURN WITH KEY TYPE = GC_E.
             IF SY-SUBRC <> 0.
               CLEAR GWA_CJ_S.
               MOVE-CORRESPONDING GS_CJ_KEY TO GWA_CJ_S.
               CLEAR GWA_RETURN.
               READ TABLE GIT_RETURN INTO GWA_RETURN WITH KEY TYPE = GC_S.
               IF SY-SUBRC = 0.
                 MOVE GWA_RETURN-MESSAGE TO GWA_CJ_S-MSG.
                 CLEAR GWA_RETURN.
                 READ TABLE GIT_RETURN INTO GWA_RETURN WITH KEY TYPE = GC_I.
                 IF SY-SUBRC = 0.
                   CLEAR GWA_CJ_E.
                   CONCATENATE GWA_RETURN-MESSAGE GWA_CJ_S-MSG INTO GWA_CJ_E-MSG SEPARATED BY GC_PIPE_FORMAT.
                   MOVE-CORRESPONDING GS_HEADER_BAPI TO GWA_CJ_E.
                   GWA_CJ_E-POSTING_NUMBER = LV_RECORD_NO.
                   APPEND GWA_CJ_E TO GIT_CJ_E.
                   GV_ERROR_RECORDS = GV_ERROR_RECORDS + GC_1.
                 ELSE.
                   IF P_TEST NE GC_X.
                     CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
                       EXPORTING
                         WAIT = LV_WAIT.
                     REFRESH:LIT_POSTING        ,
                             LIT_WTAX_ITEMS     ,
                             LIT_SPLIT_POSTINGS ,
                             LIT_CPD            .
                     CLEAR: LV_BEG_BALANCE      ,
                            LV_TOTAL_RECEIPTS   ,
                            LV_TOTAL_PAYMENTS   ,
                            LV_TOTAL_CHECKS     ,
                            LV_RUN_BALANCE      ,
                            LV_RUN_CASH_BALANCE ,
                            LV_NUMB_OF_REC      ,
                            LV_NUMB_OF_PAYM     ,
                            LV_NUMB_OF_CHECKS   .
                     CALL FUNCTION 'FCJ_GET_DATA_FOR_SCREEN'
                       EXPORTING
                         I_COMP_CODE            = GS_CJ_KEY-COMP_CODE
                         I_CAJO_NUMBER          = GS_CJ_KEY-CAJO_NUMBER
                         I_DISPLAY_PERIOD_LO    = GS_HEADER_BAPI-PSTNG_DATE
                         I_DISPLAY_PERIOD_HI    = GS_HEADER_BAPI-PSTNG_DATE
                       IMPORTING
                         E_BEGINNING_BALANCE    = LV_BEG_BALANCE
                         E_RUNNING_BALANCE      = LV_RUN_BALANCE
                         E_RUNNING_CASH_BALANCE = LV_RUN_CASH_BALANCE
                         E_TOTAL_RECEIPTS       = LV_TOTAL_RECEIPTS
                         E_TOTAL_REC_NUMBER     = LV_NUMB_OF_REC
                         E_TOTAL_PAYMENTS       = LV_TOTAL_PAYMENTS
                         E_TOTAL_PAYM_NUMBER    = LV_NUMB_OF_PAYM
                         E_TOTAL_CHECKS         = LV_TOTAL_CHECKS
                         E_TOTAL_CHECKS_NUMBER  = LV_NUMB_OF_CHECKS
                       TABLES
                         E_POSTINGS             = LIT_POSTING
                         E_WTAX_ITEMS           = LIT_WTAX_ITEMS
                         E_SPLIT_POSTINGS       = LIT_SPLIT_POSTINGS
                         E_CPD                  = LIT_CPD.
                     CALL FUNCTION 'FCJ_POST_ALL'
                       EXPORTING
                         I_COMP_CODE               = GS_CJ_KEY-COMP_CODE
                         I_CAJO_NUMBER             = GS_CJ_KEY-CAJO_NUMBER
                         I_CURRENCY                = GS_HEADER_BAPI-CURRENCY
                         I_TYP                     = 'R'
                         I_DISPLAY_PERIOD_LO       = GS_HEADER_BAPI-PSTNG_DATE
                         I_DISPLAY_PERIOD_HI       = GS_HEADER_BAPI-PSTNG_DATE
    *              IMPORTING
    *                E_ERROR_NUMBER            =
                       TABLES
                         ITCJ_POSTINGS             = LIT_POSTING
                         ITCJ_WTAX_ITEMS           = LIT_WTAX_ITEMS
                         ITCJ_SPLIT_POSTINGS       = LIT_SPLIT_POSTINGS
                         ITCJ_CPD                  = LIT_CPD
                       CHANGING
                         P_BEG_BALANCE             = LV_BEG_BALANCE
                         P_TOTAL_RECEIPTS          = LV_TOTAL_RECEIPTS
                         P_TOTAL_PAYMENTS          = LV_TOTAL_PAYMENTS
                         P_TOTAL_CHECKS            = LV_TOTAL_CHECKS
                         P_RUN_BALANCE             = LV_RUN_BALANCE
                         P_RUN_CASH_BALANCE        = LV_RUN_CASH_BALANCE
                         P_NUMB_OF_REC             = LV_NUMB_OF_REC
                         P_NUMB_OF_PAYM            = LV_NUMB_OF_PAYM
                         P_NUMB_OF_CHECKS          = LV_NUMB_OF_CHECKS.
                     COMMIT WORK.
                   ENDIF.
                   APPEND GWA_CJ_S TO GIT_CJ_S.
                   GV_SUCCESS_RECORDS = GV_SUCCESS_RECORDS + GC_1.
                   CLEAR GWA_CJ_S.
                 ENDIF.
               ENDIF.
             ELSE.
               CLEAR GWA_CJ_E.
               MOVE-CORRESPONDING GS_HEADER_BAPI TO GWA_CJ_E.
               MOVE GWA_RETURN-MESSAGE TO GWA_CJ_E-MSG.
               GWA_CJ_E-POSTING_NUMBER = LV_RECORD_NO.
               APPEND GWA_CJ_E TO GIT_CJ_E.
               GV_ERROR_RECORDS = GV_ERROR_RECORDS + GC_1.
             ENDIF.
           ENDIF.
         ELSE.
           GWA_RETURN-MESSAGE = 'Transaction Name does not correspond to any Transaction Number'(017).
           CLEAR GWA_CJ_E.
           MOVE-CORRESPONDING GS_HEADER_BAPI TO GWA_CJ_E.
           MOVE GWA_RETURN-MESSAGE TO GWA_CJ_E-MSG.
           GWA_CJ_E-POSTING_NUMBER = LV_RECORD_NO.
           APPEND GWA_CJ_E TO GIT_CJ_E.
           GV_ERROR_RECORDS = GV_ERROR_RECORDS + GC_1.
         ENDIF.
       ENDLOOP.
    ENDFORM.                    " SUB_BAPI_CALL

    Hi Experts,
    I have a requirement where in cash journal posting needs to be carried out automatically by an inbound interface on a periodic basis and at the start during cut over an upload program needs to be used to upload beg balance data . For this purpose I have used BAPI_CASHJOURNALDOC_CREATE to save cash journal entries along with BAPI TRANSACTION COMMIT.
    Once the Data is successfully saved I am using FM FCJ_GET_DATA_FOR_SCREEN to get prerequisite data for the FM FCJ_POST_ALL which is used by the Standard cash journal program internally to post the saved data. ( I got this by debugging the standard transaction and both FMs are not yet released )
    The issues I am facing is that the the FM FCJ_POST_ALL does not always post the data it behaves in random fashion i.e some times it posts the entries where as sometimes it does not post the entries.
    I have tried using commit work after the FM but that also does not result in consistent behavior of the program. One more issue is the i am not allowed to use commit work in a an inbound proxy so how do i proceed ?
    I am attaching the code for further analysis:
    DATA: LIT_TCJ_TRANS_NAMES TYPE TABLE OF TCJ_TRANS_NAMES,
             LWA_TCJ_TRANS_NAMES TYPE TCJ_TRANS_NAMES,
             LV_WAIT             TYPE BAPITA-WAIT VALUE '1',
             LV_RECORD_NO        TYPE SY-TABIX.
       DATA : LIT_POSTING        TYPE STANDARD TABLE OF ISCJ_POSTINGS,
              LIT_WTAX_ITEMS     TYPE STANDARD TABLE OF TCJ_WTAX_ITEMS,
              LIT_SPLIT_POSTINGS TYPE STANDARD TABLE OF ISCJ_POSTINGS,
              LIT_CPD            TYPE STANDARD TABLE OF TCJ_CPD.
       DATA: LV_BEG_BALANCE      TYPE CJAMOUNT,
             LV_TOTAL_RECEIPTS   TYPE CJAMOUNT,
             LV_TOTAL_PAYMENTS   TYPE CJAMOUNT,
             LV_TOTAL_CHECKS     TYPE CJAMOUNT,
             LV_RUN_BALANCE      TYPE CJAMOUNT,
             LV_RUN_CASH_BALANCE TYPE CJAMOUNT,
             LV_NUMB_OF_REC      TYPE I,
             LV_NUMB_OF_PAYM     TYPE I,
             LV_NUMB_OF_CHECKS   TYPE I.
       DESCRIBE TABLE GIT_CJ LINES GV_TOTAL_RECORDS.
       SELECT MANDT COMP_CODE TRANSACT_NUMBER LANGU TRANSACT_NAME LONG_TEXT
          FROM TCJ_TRANS_NAMES
          INTO TABLE LIT_TCJ_TRANS_NAMES
          WHERE LANGU = GC_EN.
       IF SY-SUBRC <> 0.
         MESSAGE 'No Business Transaction maintained for Company Code in this client'(016) TYPE GC_I.
         LEAVE LIST-PROCESSING.
       ENDIF.
       DESCRIBE TABLE GIT_CJ LINES GV_TOTAL_RECORDS.
       LOOP AT GIT_CJ INTO GWA_CJ.
         LV_RECORD_NO = SY-TABIX.
         CLEAR: GS_HEADER_BAPI,
                GS_CJ_KEY,
                GWA_ITEMS.
         REFRESH: GIT_ITEMS,
                  GIT_RETURN.
         GS_HEADER_BAPI-COMP_CODE    = GWA_CJ-BUKRS.
         GS_HEADER_BAPI-CAJO_NUMBER  = GWA_CJ-CJNR.
         GS_HEADER_BAPI-CURRENCY     = GC_PHP.
         CLEAR LWA_TCJ_TRANS_NAMES.
         READ TABLE LIT_TCJ_TRANS_NAMES INTO LWA_TCJ_TRANS_NAMES WITH KEY COMP_CODE     = GWA_CJ-BUKRS
                                                                          LANGU         = GC_EN
                                                                          TRANSACT_NAME = GWA_CJ-BTNAM.
         IF SY-SUBRC = 0.
           GWA_ITEMS-TRANSACT_NUMBER = LWA_TCJ_TRANS_NAMES-TRANSACT_NUMBER.
           GWA_ITEMS-P_RECEIPTS        = GWA_CJ-CJRAT.
           GWA_ITEMS-TAX_CODE          = GWA_CJ-TXCOD.
           GS_HEADER_BAPI-BP_NAME      = GWA_CJ-BPNAM.
           GWA_ITEMS-POSITION_TEXT     = GWA_CJ-POTXT.
           CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
               INPUT  = GWA_CJ-LIFNR
             IMPORTING
               OUTPUT = GWA_ITEMS-VENDOR_NO.
           CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
               INPUT  = GWA_CJ-KUNNR
             IMPORTING
               OUTPUT = GWA_ITEMS-CUSTOMER.
           PERFORM SUB_DATE_FROMAT_BAPI  CHANGING  GWA_CJ-BLDAT
                                                   GS_HEADER_BAPI-DOC_DATE.
           PERFORM SUB_DATE_FROMAT_BAPI  CHANGING   GWA_CJ-BUDAT
                                                    GS_HEADER_BAPI-PSTNG_DATE.
           GS_HEADER_BAPI-REF_DOC_NO   = GWA_CJ-XBLNR.
           GS_HEADER_BAPI-ALLOC_NMBR   = GWA_CJ-ALLNO.
           CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
               INPUT  = GWA_CJ-KOSTL
             IMPORTING
               OUTPUT = GWA_ITEMS-COSTCENTER.
           CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
               INPUT  = GWA_CJ-PRCTR
             IMPORTING
               OUTPUT = GWA_ITEMS-PROFIT_CTR.
           APPEND GWA_ITEMS TO GIT_ITEMS.
           CALL FUNCTION 'BAPI_CASHJOURNALDOC_CREATE'
             EXPORTING
               HEADER              = GS_HEADER_BAPI
             IMPORTING
               COMPANY_CODE        = GS_CJ_KEY-COMP_CODE
               CASH_JOURNAL_NUMBER = GS_CJ_KEY-CAJO_NUMBER
               FISCAL_YEAR         = GS_CJ_KEY-FISC_YEAR
               CASH_JOURNAL_DOC_NO = GS_CJ_KEY-POSTING_NUMBER
             TABLES
               ITEMS               = GIT_ITEMS
               RETURN              = GIT_RETURN.
           IF GIT_RETURN IS NOT INITIAL.
             READ TABLE GIT_RETURN INTO GWA_RETURN WITH KEY TYPE = GC_E.
             IF SY-SUBRC <> 0.
               CLEAR GWA_CJ_S.
               MOVE-CORRESPONDING GS_CJ_KEY TO GWA_CJ_S.
               CLEAR GWA_RETURN.
               READ TABLE GIT_RETURN INTO GWA_RETURN WITH KEY TYPE = GC_S.
               IF SY-SUBRC = 0.
                 MOVE GWA_RETURN-MESSAGE TO GWA_CJ_S-MSG.
                 CLEAR GWA_RETURN.
                 READ TABLE GIT_RETURN INTO GWA_RETURN WITH KEY TYPE = GC_I.
                 IF SY-SUBRC = 0.
                   CLEAR GWA_CJ_E.
                   CONCATENATE GWA_RETURN-MESSAGE GWA_CJ_S-MSG INTO GWA_CJ_E-MSG SEPARATED BY GC_PIPE_FORMAT.
                   MOVE-CORRESPONDING GS_HEADER_BAPI TO GWA_CJ_E.
                   GWA_CJ_E-POSTING_NUMBER = LV_RECORD_NO.
                   APPEND GWA_CJ_E TO GIT_CJ_E.
                   GV_ERROR_RECORDS = GV_ERROR_RECORDS + GC_1.
                 ELSE.
                   IF P_TEST NE GC_X.
                     CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
                       EXPORTING
                         WAIT = LV_WAIT.
                     REFRESH:LIT_POSTING        ,
                             LIT_WTAX_ITEMS     ,
                             LIT_SPLIT_POSTINGS ,
                             LIT_CPD            .
                     CLEAR: LV_BEG_BALANCE      ,
                            LV_TOTAL_RECEIPTS   ,
                            LV_TOTAL_PAYMENTS   ,
                            LV_TOTAL_CHECKS     ,
                            LV_RUN_BALANCE      ,
                            LV_RUN_CASH_BALANCE ,
                            LV_NUMB_OF_REC      ,
                            LV_NUMB_OF_PAYM     ,
                            LV_NUMB_OF_CHECKS   .
                     CALL FUNCTION 'FCJ_GET_DATA_FOR_SCREEN'
                       EXPORTING
                         I_COMP_CODE            = GS_CJ_KEY-COMP_CODE
                         I_CAJO_NUMBER          = GS_CJ_KEY-CAJO_NUMBER
                         I_DISPLAY_PERIOD_LO    = GS_HEADER_BAPI-PSTNG_DATE
                         I_DISPLAY_PERIOD_HI    = GS_HEADER_BAPI-PSTNG_DATE
                       IMPORTING
                         E_BEGINNING_BALANCE    = LV_BEG_BALANCE
                         E_RUNNING_BALANCE      = LV_RUN_BALANCE
                         E_RUNNING_CASH_BALANCE = LV_RUN_CASH_BALANCE
                         E_TOTAL_RECEIPTS       = LV_TOTAL_RECEIPTS
                         E_TOTAL_REC_NUMBER     = LV_NUMB_OF_REC
                         E_TOTAL_PAYMENTS       = LV_TOTAL_PAYMENTS
                         E_TOTAL_PAYM_NUMBER    = LV_NUMB_OF_PAYM
                         E_TOTAL_CHECKS         = LV_TOTAL_CHECKS
                         E_TOTAL_CHECKS_NUMBER  = LV_NUMB_OF_CHECKS
                       TABLES
                         E_POSTINGS             = LIT_POSTING
                         E_WTAX_ITEMS           = LIT_WTAX_ITEMS
                         E_SPLIT_POSTINGS       = LIT_SPLIT_POSTINGS
                         E_CPD                  = LIT_CPD.
                     CALL FUNCTION 'FCJ_POST_ALL'
                       EXPORTING
                         I_COMP_CODE               = GS_CJ_KEY-COMP_CODE
                         I_CAJO_NUMBER             = GS_CJ_KEY-CAJO_NUMBER
                         I_CURRENCY                = GS_HEADER_BAPI-CURRENCY
                         I_TYP                     = 'R'
                         I_DISPLAY_PERIOD_LO       = GS_HEADER_BAPI-PSTNG_DATE
                         I_DISPLAY_PERIOD_HI       = GS_HEADER_BAPI-PSTNG_DATE
    *              IMPORTING
    *                E_ERROR_NUMBER            =
                       TABLES
                         ITCJ_POSTINGS             = LIT_POSTING
                         ITCJ_WTAX_ITEMS           = LIT_WTAX_ITEMS
                         ITCJ_SPLIT_POSTINGS       = LIT_SPLIT_POSTINGS
                         ITCJ_CPD                  = LIT_CPD
                       CHANGING
                         P_BEG_BALANCE             = LV_BEG_BALANCE
                         P_TOTAL_RECEIPTS          = LV_TOTAL_RECEIPTS
                         P_TOTAL_PAYMENTS          = LV_TOTAL_PAYMENTS
                         P_TOTAL_CHECKS            = LV_TOTAL_CHECKS
                         P_RUN_BALANCE             = LV_RUN_BALANCE
                         P_RUN_CASH_BALANCE        = LV_RUN_CASH_BALANCE
                         P_NUMB_OF_REC             = LV_NUMB_OF_REC
                         P_NUMB_OF_PAYM            = LV_NUMB_OF_PAYM
                         P_NUMB_OF_CHECKS          = LV_NUMB_OF_CHECKS.
                     COMMIT WORK.
                   ENDIF.
                   APPEND GWA_CJ_S TO GIT_CJ_S.
                   GV_SUCCESS_RECORDS = GV_SUCCESS_RECORDS + GC_1.
                   CLEAR GWA_CJ_S.
                 ENDIF.
               ENDIF.
             ELSE.
               CLEAR GWA_CJ_E.
               MOVE-CORRESPONDING GS_HEADER_BAPI TO GWA_CJ_E.
               MOVE GWA_RETURN-MESSAGE TO GWA_CJ_E-MSG.
               GWA_CJ_E-POSTING_NUMBER = LV_RECORD_NO.
               APPEND GWA_CJ_E TO GIT_CJ_E.
               GV_ERROR_RECORDS = GV_ERROR_RECORDS + GC_1.
             ENDIF.
           ENDIF.
         ELSE.
           GWA_RETURN-MESSAGE = 'Transaction Name does not correspond to any Transaction Number'(017).
           CLEAR GWA_CJ_E.
           MOVE-CORRESPONDING GS_HEADER_BAPI TO GWA_CJ_E.
           MOVE GWA_RETURN-MESSAGE TO GWA_CJ_E-MSG.
           GWA_CJ_E-POSTING_NUMBER = LV_RECORD_NO.
           APPEND GWA_CJ_E TO GIT_CJ_E.
           GV_ERROR_RECORDS = GV_ERROR_RECORDS + GC_1.
         ENDIF.
       ENDLOOP.
    ENDFORM.                    " SUB_BAPI_CALL

Maybe you are looking for

  • Cover Art Too Small

    Hi, strange thing. I have used the cover print functionality of itunes multiple times without any problems. But suddenly the covers are printed much too small. About half the size. The scaling in the page setup dialog is set to 100% and the page size

  • Forms & Reports 11gR2 installation - Can't create domain

    Hi, I try to install Forms & Reports 11gR2 (version 11.1.2.2.0) on a Windows 7 64 bits machine. Here is that I try : Installation of JDK 1.7.0.51 for Windows 7 64 bits Installation of WebLogic 10.3.6 "Generic" bits (java -Xmx1024m -jar wls1036-generi

  • Help with identifying the Model of a Toshiba satellite

    I have a Toshiba Satellite I believe this is a A105, but don't know the full model number. I ran Belarc Advisor. It did not give the full model. Thanks, Bob

  • Using FLash Text & Buttons Links

    They have worked fine in the past, but my web pages that use Flash buttons or text now require two mouse clicks to make the links work work. This problem occurred some months ago and is applicable to all my web pages, some made years ago and some ver

  • Can I forward IPs without Server.app?

    I want to forward a local IP range (the gateway that a virtual machine uses, Parallels Desktop 8 with host-only networking) to an IP (that a VPN connection of mine uses). By the time I figured out how it should (?) work using the modern tools of rece