IDOC status back

Hi Friends,
    Think the scenario like : GR IDOC ==> SOAP,  STATUS IDOC <== GR IDOC  both sides asynchronous. When i update the status back, IDOC status is updating properly like the xml sent or not .  for that case i did one logic in receiver determination & interface determination. It is working fine as i followed some sceanrios. But how i am getting response back if it SOAP side asynchronous method.  So it should be getting resposse from XI/PI. how ?
Deva

So it should be getting resposse from XI/PI. how ?
if you need to update the status of the IDOC saying that XML message (SOAP) was sent or not then you can configure it in a BPM.
Receive (Async_IDOC) --> Transformation(if required) --> (:Block Step to catch any exception during send Send (Async_SOAP....with Transport Acknowledgement set ) --> Send (Async_IDOC)
/people/michal.krawczyk2/blog/2006/06/22/xi-playing-with-the-file-adapters-acknowledgments

Similar Messages

  • IDOC Ack status back to XI/BPM ?

    Hi
    i have done File to Idoc scenario, and want to get acknowledgemnents inside XI/BPM.
    i hv proivded port,client,message type and selected 'Request acknowledgement' tab and executed report 'IDX_NOALE'. but im not getting any acknowledgement status in moni. please suggest hw could i get Idoc acknowledgements in XI.
    1.Do i need to import ALEAUD Idoc into XI ? and Is any configuration required in ID for ALEAUD?
    2.Is it possible to map Idoc status back into BPM? if yes, please explain how BPM should design?
    3.once Idoc ack status received inside XI, is it possible to send same status to the back end sender system?
    appreciate your help..
    Regards,
    Rajesh

    hi
    1.Do i need to import ALEAUD Idoc into XI ? and Is any configuration required in ID for ALEAUD?
    By default, audit idocs will come and get tagged to the IDoc. If you want to send it to the file system, all configurations must be done for IDoc to file scenario for the audit IDoc.
    2.Is it possible to map Idoc status back into BPM? if yes, please explain how BPM should design?
    Yes, it can be done. But won't be reqd in ur case.
    3.once Idoc ack status received inside XI, is it possible to send same status to the back end sender system?
    Yes, Q1
    Check this document on handling IDOC acknowledgements.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    rgds,
    Arun

  • How to Send Idoc Acknowledgements back to Http sender (Http to Idoc)

    Hi
    I have scenario: Http To Idoc
    first requirment:
    i need to map xml file come from HTTP Sender to Idoc (SAP system), and need to send Idoc acknowledgements/status back to Http sender.
    second requirment:
    while mapping COM Xml file come from Http to COMMAT04 idoc into SAP system i need to to check whether corresponding material already exist in R/3 or not, if material is not exist, process should be cancelled and alert should be raised. ( i mean to say before sending COMMAT04 idoc into SAP, corresponding material should be exist already, if not alert should be send to  http sender)
    please thrown some inputs, if sombody has already done with htis....
    Thanks in Advance, and help would be appreciated..
    Thanks and Regards
    Rajesh Babu

    Just providing the specifics that Suhail has intended.
    How to handle IDOC Acknowledgements in XI.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    RFC Mapping Lookups:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a03e7b02-eea4-2910-089f-8214c6d1b439
    Regards,
    Ravi
    Edited by: Ravi Kanth Talagana on Jul 7, 2008 3:32 PM

  • How to find Correct IDoc Status in SAP

    Hi All,
    I need some help on IDoc scenario, I have custom program to create Idoc and as well it will send IDoc to XI. I want to know idoc staus in the program to update custom table whether idoc sent successfully or not but idoc giving status as 03 (Data passed to port OK) irrespective of idoc send or not, actually idoc not sent to xi when I check SM58 showing error.
    Please advice me how to find correct idoc status inside program itself.
    **-----Create IDoc
      CALL FUNCTION 'IDOC_OUTBOUND_WRITE_TO_DB'
        TABLES
          int_edidd      = i_edidd
        CHANGING
          int_edidc      = wa_int_edidc
        EXCEPTIONS
          idoc_not_saved = 1
          OTHERS         = 2.
      COMMIT WORK.
      i_edidc = wa_int_edidc.
      APPEND i_edidc.
      REFRESH i_edidd.
    **-----Send Idoc
      CLEAR i_edidd.
    **-------Send Idoc to XI
      CALL FUNCTION 'EDI_OUTPUT_NEW'
        EXPORTING
          onl_option = 'B'
          error_flag = ' '
        TABLES
          i_edidc    = i_edidc
          i_edidd    = i_edidd.
      COMMIT WORK.
      READ TABLE i_edidc INDEX 1.
    **-----Update Dispatch order status based on Idoc status.
      IF sy-subrc =  0 AND i_edidc-status ='03'.
        znxi01_update c_03 i_edidc-docnum.
        gw_success_record = gw_success_record + 1.
      ELSE.               " Error in Data Transfer
        znxi01_update c_02 i_edidc-docnum.
        gw_fail_record = gw_fail_record + 1.
      ENDIF.

    Hi Anil,
    for setting IDOC Status you can send back a IDOC of type <i>ALEAUD01</i>.
    The function IDOC_INPUT_ALEAUD takes automatically this IDOC and writes the status to the origin IDOC.
    Regards Mario

  • IDOC status 62 -  IDOC passed to application

    Hello Experts,
    Am posting a inbound sales order custom/extended IDOC into the system from WE19, but, when I saw it in WE02/05, its showing status 62 - IDOC passed to application, i checked ST22 run time error. there is no error and also checked triggering timings, its trigger IMMEDIATELY in WE20 fo rthat partner!!
    Pls. let me kniow the reasona and fixing idea.
    Thank you

    I think you're going to want to debug through the process code (set a breakpoint in that function) and determine if you get a clean exit from there.  If so, you should see a new status in your control record and in your status table as you exit the function call.  It sounds like you've got an abnormal termination/exit from the process code, in which case the IDOC status is falling back to the last recorded status.  If this is not the case, then perhaps you've got a commit handling issue where an explicit commit is expected to finish the process but never happens.

  • How to send IDOC Status confirmation

    HI,
    I would like to know an STANDARD way of sending the IDOC status to XI system.
    The scenario is as follows:
    INVOIC01 reception: EDI -> XI/PI -> SAP
    (using WE20 EDI partners LI)
    I need to send the IDOC INVOIC01 status back to XI/PI.
    The RBDSTATE program just works with LS partners.
    Any idea to solve that?
    Please remember that just using the SAP standard functionalities. Not developing any kind of "Z" program.
    Thanks a lot!
    Demétrius

    Hi,
    Even though the acknowledgment is sent by your vendor it is going to come to your XI system, so from the XI system you send the status idoc and then post in SAP.
    Your XI system can be registered as an Logical system to your SAP system and your problem is solved.
    Thansk,
    Mahesh.

  • Inconsistent IDOC status some partner getting status 30 randomly ?

    Hi,
    I have developed customize IDOC and distribute to around 100+ receiver partner type KU. There is always idoc with status 30 in between randomly (not always the same KU).
    I have implemented below code :
    COMMIT WORK.
          CALL FUNCTION 'DEQUEUE_ALL'.
    Base on note Note 150202 - ALE: IDoc outbound - IDocs remain in status 30
    One possible cause of this is a lock that is released too late:
    First, you execute the COMMIT WORK and then a DEQUEUE ALL or EDI_DOCUMENT_DEQUEUE_LATER.
    However, when you execute the COMMIT, the asynchronous processes are started that must first lock the IDoc again.
    Some forum mention using code below:
    IDoc status as 30
    Used
    CALL FUNCTION 'DB_COMMIT'.
    CALL FUNCTION 'DEQUEUE_ALL'.
    After FM 'MASTER_IDOC_DISTRIBUTE' and before COMMIT WORK.
    Please advise ? is that the process is to fast ?
    Thank you in advance
    Fernand

    Hi Vinay parakala
    Schedule back ground job to program RSEOUT00 regularly to process the 30 status idoc....
    Your program generates the idoc ... and RSEOUT00 will process you idocs which are in 30 status...
    i hope  above info helps you
    Note: enter Message type BOMMAT in  program RSEOUT00
    Thanks
    Ramesh

  • User-Exit for IDoc status

    Hello all!
    I'm trying to send a message with the status of an IDoc that has been processed, but I can't find an exit right after the status of the IDoc has been set, do you have any idea on what can I do for this?
    Regards!

    This is the exit where we have the control of setting idoc status. If there no scope of this idoc status.
    Then try to find out an exit which will be triggered before this exit with idoc status ( with value ). Then export this to memory and get back the same from memory in Vijay's suggested exit.
    Also if you could able to find the exit after THIS exit you won't have option to set custom idoc status.
    Regds
    Manohar

  • IDOC status at 30, but in we05 it is 03

    Hello Gurus!!
    My program generates an IDOC and as soon as the idoc is generated it the status is 03 then i have todo something else.
    Within the program when i am cheking the status is 30 but actually in transaction we05 the status is 03.
    I have cheked the partner profiles and transfer_idocs_immeadiately has already been selected.
    I have already gone thru the forum but no valid solution was given,
    There is no need to change any ALE configurations / port configurations because everything just work fine. It is only that within the program i am not able to catch the status 03. the proram is not waiting untill the idoc status is 03. it is capturing only the status 30.
    Is there any thing that i can do within the program? should i capture the idoc number and then check the idoc status from EDID4?
    Please answer o this questions ASAP.
    Regards.

    Initially when you create the outbound idocs then status is 30. then you have to run the program RSEOUT00 to process the idoc then after the processing the status changes to 03.
    But the Program RSEOUT00 is optional. In the partner profile (WE20) If you select the option  'Collect Idocs', then you have to schedule the program RSEOUT00 to process the Idocs otherwise if you have choose the option 'Transfer idoc immediately', you don't need to do anything.
    Thanks,
    Srinivas

  • Is it possible to create a custom IDOC status?

    Is it possible to create a custom idoc status on table TEDS1?
    I have looked through customising and cannot seem to find a way to create a new idoc status.
    Has anybody done this?

    Hello Chester..
    hope this link will be helpful,
    Re: IDOC status
    *********Please reward points ,if found useful

  • IDoc status 53 in employee replication from SAP HR

    Hi experts,
    We are having some problems in CRM BP creation with role employee.
    We are using CRM 5.0 and SAP ECC 6.0 and we are trying to replicate employee’s information to CRM from HR.
    After read the notes 934372, 615896, 550055, 363187, 312090 we made the next configuration steps in our systems:
    R/3:
    - Creation of connection port (trans. WE21)
    - Creation of logical system (trans. WE20) and assignment of outbound message HRMD_ABA
    - Creation of distribution model (trans. BD64) with all filters indicated in note 312090
    CRM
    - Creation of logical system (trans. WE20) and assignment of inbound message HRMD_ABA
    - Creation of conversion between basic types HRMD_A05 and HRMD_ABA01 (trans. WE70) as described in note 312090
    - Creation of conversion between message types HRMD_A and HRMD_ABA (trans. WE73) as described in note 312090
    - Creation of external number range “ZE” from HR01200001 to HR01299999 (using PA04 in R3 we found the number range between 01200001 and 01299999)
    - Creation of BP Grouping with the same name of number range (“ZE”) checked to be external too
    - Update of table T77S0 (using SM30):
    HRALX HRAC X
    HRALX PBPON OFF
    HRALX PBPHR ON
    HRALX PBPON ON
    HRALX PNUMB 3
    HRALX PPROL BUP003
    HRALX PSUBG ZE
    PLOGI PLOGI MV
    We know we should have the same value in R3 and CRM for PLOGI/PLOGI, so we created in CRM MV because that is the plan version used in R3. To create it, we just manually add a new row in table T778P and then selected it in table T77S0. Is this the correct way to create a plan version?
    After these steps, in R3 we execute program RHALEINI with parameters:
    - Plan version = MV
    - Object type = P
    - Object ID = an active employee
    - Reporting period = all
    - Transfer mode = Insert
    - Receiving system:
    Receiving partner No = DCRCLNT300 (logical system created in WE20)
    Message type = HRMD_ABA
    And everything looks fine in R3.
    In CRM, using trans. WE05, we can see that the iDoc is created, apparently without problems with status 53 - "Applicaton document posted" but the business partner is never created.
    Did we miss some configuration steps?
    Should we do something more after see the iDoc in CRM to create BP?
    Thanks in advance.
    Alda

    hi pratk bhai,
    ya i have done the same setting what Ada has mentioned eariler,
    and as of your suggestion to maintatin the mandatory infotype, i have even done tht,
    after running RHALEINI in R3, the status is all green here.
    when i run the tcode BD87  to check the Idoc status its showing fine (Error free).
    now, through tcode se38 the report CRMHRALE_CENTRAL_PERSON shows all the employees as status green,,
    but the partner number is not getting generated. ( i have used HRALX-PNUMB= 3 (Prefeexing the number range coming from R3)).
    kindly advice me what should be done in order to generate a BP number for the replicated HR Employee.
    best regards,
    Madhup

  • IDoc Status 02 ( Could not find code page for receiving system )

    Hi All,
    I am getting Idoc status 02 when I am trying to send IDocs from ECC to PI system ( Production ).
    Error description.
    Could not find code page for receiving system
    Message no. E0266
    Diagnosis
    For the logical destination PIP001, you want to determine the code page in which the data is sent with RFC. However, this is not currently possible, and the IDoc cannot yet be dispatched.
    Procedure for System Administration
    Possible causes are:
    1. The entry no longer exists in the table of logical destinations.
    2. The target system could not be accessed at runtime.
    3. The logon language is not installed in the target system.
    4. In the destination system, no logon language is maintained
    Please help.
    Thanks - Vinay.

    Hi Vinay,
    Status 02 occurs when data is not passed to port suceessfully. Check the RFC desination  is working fine and your able to connect to target system and also check correct port is assigned.
    Regards,
    Vinod.

  • IDOC  STATUS 29 to 68

    Hi all,
    Customer request is change idoc status from 29 to 68.
    68 = no further processing inbound side
    31 = no further processing outbound side
    if i change status of idoc from 29 to 68 using Fn module IDOC_STATUS_WRITE_TO_DATABASE
    Data of idoc is vanishing.
    I observed that if i change status of idoc from 29 to 31 then there is no data loss in idoc with same Fn module.
    Is there any way to change idoc status from 29 to 68 without losing the Idoc data.
    anyway for both 68 & 31 meanings are same , but customer requires 29 to 68.
    if u have any idea please suggest me.

    Hi Suneel,
    If the program does't exits then try this ...
    DATA: L_EDIDC_TAB       LIKE EDIDC      OCCURS 1 WITH HEADER LINE,
          L_IDOC_STATUS_TAB LIKE BDIDOCSTAT OCCURS 1 WITH HEADERLINE,
          L_IDOC_CONTROL    LIKE EDIDC.
        L_IDOC_STATUS_TAB-DOCNUM = <your IDoc number>.
        L_IDOC_STATUS_TAB-STATUS = '68'.
        APPEND L_IDOC_STATUS_TAB.
        CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
             EXPORTING
                  IDOC_NUMBER               = L_EDIDC_TAB-DOCNUM
             IMPORTING
                  IDOC_CONTROL              = L_IDOC_CONTROL
             TABLES
                  IDOC_STATUS               = L_IDOC_STATUS_TAB
             EXCEPTIONS
                  IDOC_FOREIGN_LOCK         = 1
                  IDOC_NOT_FOUND            = 2
                  IDOC_STATUS_RECORDS_EMPTY = 3
                  IDOC_STATUS_INVALID       = 4
                  DB_ERROR                  = 5
                  OTHERS                    = 6.
    Regards,
    Ferry Lianto

  • Idoc Status 53 but Applicaton document not posted message type PORDCR

    Hi,
    Need your help. I am using message type PORDCR and Basic type PORDCR04 to create Purchase order through inbound Idocs. I am getting correct status '53' Application document posted along with the new Purchase order number. When I am trying to see it in EKKO / or ME23N  I could not see this purchase order.
    Can anyone please let me know what could be the possible reason for document is not getting posted in in database but Idoc status is correct.?
    Thanks in advance.
    Regards,
    Deepak

    check SM13 and ST22 to see if there are any errors there

  • IDoc status is not coming to '03'

    Hi,
    When I run my program, it is giving IDoc status as 30. When I go and see in WE05, it is showing same status. It's not getting 03 status.
    I know that we can bring the status to 03 by executing the program RSEOUT00. But I want this to come from my program where I have used MASTER_IDOC_DISTRIBUTE function module.
    Generally, even though I get status 30 in the program, when I go and see in WE05, 03 status is displayed. But I don't know what happend this time, it is showing 30 status even in WE05 also.
    Please tell me what could be the reason.
    Regards,
    Suman.

    Hello,
    Check if there are any dumps in the system
    Or
    if there are any authorization issues.
    IF there are dumps, then the system usually stops autoprocessing the idocs and you might need to schedule the program at periodic intervals to get the idoc in status 03.
    Thanks,
    Sushil Joshi

Maybe you are looking for