Reprocessing an idoc

Hello. i have an  inbound idoc. it has been transferred from SRM to SAP. In SRM it's status is 03. in SAP , status is 54. I wish to change the posting date and reprocess the idoc in SRM. I tried BD87 but we cannot modify the idoc in BD87. 
I do not want to use a new idoc(in WE19) only reprocess the old one.
Is this possible.Thx

try report RBDAGAIE

Similar Messages

  • Reprocess the IDOC without using BD87

    Can I  reprocess an idoc through a zreport in the background. can i use the program behind BD87 and use a submit statement?
    But BD87 genertes an output from which you have pick your idoc and reprocess it manually.
    Thanks,
    krishna.

    hi ,
    See the status of the record and process the below program using Submit report by passing Idoc number
    Program RBDMANI2 for status 51 & 52
    Program RBDAPP01 for status 64 ,66
    Program RBDAGAIE for status 32 and 69 (Edited IDocs)
    Program RBDSYNER for status 26
    Program RSEOUT00 for status 30
    re-process IDocs failing in 29 status, use program RBDAGAIN.
    Prabhudas

  • How to Reprocess Outbound Idocs in Status 02 (Errors)

    Hi,
        I have an urgent problem. How do I re-process an Outbound IDoc in Status '02' (Error Passing Data to Port)
        I have tried reprocessing this IDoc through BD87 using both the options Edit>Process and Edit>Restrict and Process, but it doesn't work
         Please help as we are migrating cutover data from SAP to another system
    Regards,
    Aditya

    Worth to have a look at this thread
    Error handling problem with outbound idoc status 02 and  XML HTTP Port
    Regards
    Vivek
    Reward points for all the useful answers

  • Which field is updated in case of Reprocessing an IDOC

    Hi,
    I have an IDOC with status '51'.
    When I reprocess my IDOC, i dont want to execute certain code.
    Is there any field in IDOC control record, through which I can know that the IDOC is in reprocessing mode?
    Regards,
    Sandeep.

    you have the answer in your question itself. When you are reprocessing in IDOC in error, the status code will be 51 in control record

  • Regarding reprocessing of idocs

    Whenever we re-process any idoc, a new idoc number is generated.I wrote a logic to update the number of times a idoc is processed.I used the counter field value in EDIDS table to show number of times the idoc is processed.But when Iam trying to run the logic in WE19 mode I find that the idoc number is changing to new number and iam unable to compare it.
    Points will be rewarded immediately for useful answers..

    Hi,
    When you reprocess the failed IDocs through the specific programs, new IDocs would not be generated, instead the status changes in the same IDoc. The various programs to reprocess failed IDocs are,
    RBDAGAI2 - to reprocess IDocs after ALE inbound error (with status 56, 61, 63, 65)
    RBDAGAIE - to reprocess edited IDocs (with status 32 / 69 )
    RBDAGAIN -  to reprocess IDocs with status 02 / 04 / 05 / 25 / 29
    RBDAPP01 - to reprocess IDocs with status 64 / 66 (inbound unprocessed IDocs / IDocs failing with serialization issue)
    RBDSYNER -  to reprocess IDocs with ssyntax error (with status 26 /60)
    RBDMANI2 - to reprocess failed IDocs (status 51)
    RSEOUT00 - to reprocess unprocessed outbound IDocs (status 30)
    Any IDoc edited using transaction WE19(test tool for IDoc processing) would generate a new IDoc and the newly generated IDoc would have the status (42 - outbound / 74 - inbound).
    ~ Bineah

  • Reprocess the IDOC

    Hi,
    I am devloping one report which will display some idocs.My requirnment is to reprocess (like BD87) those idoc which are there in  error state.So is there any function module or program which i can call in report to reprocess the idoc?Or is there any alternative way to perform the same operation.

    Check out function module IDOC_INPUT, which is pretty neat. Specify the IDocs that you want to process in table parameter UNPROCESSED_IDOCS and ignore the other tables parameters IDOC_DATA and IDOC_CONTROL (can be empty when calling the function).
    Cheers, harald
    p.s.: Problems with reports other than BD87 is that they usually only handle a specific set of IDoc status values (e.g. RBDAPP01 is only for unprocessed IDocs in status 64 or 66, RBDMANI2 for failed IDocs in status 51, RBDAGAIE for edited IDocs in status 69, etc.) - that's why I prefer to use the function module.

  • SAP T-code - What transaction for reprocessing inbound IDocs?

    Hello,
    From what I know, WE19 is used for reprocessing outbound IDocs...
    What is the transaction for reprocessing inbound IDocs?
    Thanks.
    Moderator message: Please use a meaningful subject for your questions.  I've edited it for you this time
    Edited by: Matt on Nov 6, 2008 1:39 PM

    Hi,
    We19 is used for testing the IDOC.
    We can fill the parnter details & idoc segmetns manually and can try to post it.
    This is a test tool for idoc processing manually. not specifically outbound or inbound.
    Regards
    Manasa

  • Reprocessing of Idoc

    Hi ,
    I want to reprocess some Idocs , so i can do it by using the program RSNAST00/RSEOUT00 .
    for the program RSNAST00  I need NAST -object_key which I can easily  get  but I can not use this program due to some tech. issues .
    Now I want to use the program RSEOUT00 so I need the Document No. for the previously found NAST -object_key  , so how I can get this DOC NO. for the IDOC .
    Actually to make it simple  anyone can please  explain the links betweem NAST & EDIDC .
    Thanks & Regards,
    Kashim Raja

    Hi,
    OBJECT LIKE NAST  --->contains documents key.
    CONTROL_RECORD_IN LIKE EDIDC  --> It contains the partailly filled control Records
    RSEOUT00  is used for ->Test Outbound Processing Tcode (we14)
    Process All Selected IDocs (EDI)
    Report for generation of files for EDI outbound processing.
    The report processes the IDocs available in the system with the status 'to be processed'. The IDocs are selected according to the selection options and parameters specified.
    It is important that you make sure that only test messages or productive messages are selected.
    The IDocs are processed in various files for various output modes and for various ports. The names of the files are created according to the naming definition for the outbound file. This definition is determined in the port definition.
    RSNAST00:
    Selection Program for Issuing Output
    Output program for output
    Purpose
    Issues output from all applications with send times 1 and 2.
    Selection
    Selection criteria:
    Application
    Object key
    Output type
    Transmission medium
    In addition to that, you can choose whether repeat processing is to take place. In this case, only output is selected that has already been processed and the processing program is called up for it. However, no output will be duplicated.
    Via printer default, an already existing printer can by overridden from the output.
    The field 'Suffix 2' has got the same effect: it sets this indicator in each selected output. In this way, a clear spool entry can be achieved.
    Please Try to get the  DOC NO. for the IDOC  using  Tables. tnapr,t681z,t685b.
    I hope this may helpfull.
    Thanks,
    AMS

  • Reprocessing the idoc

    hi ,
    i am not able to reprocess the idoc when the satus is 62 on the inbound side....
    how to reprocess the idoc.
    what is the program to reprocess the idoc....

    hi shyam,
       u can first test the inbound idoc using we19, which is a testing tool. To reprocess an idoc u have to go to BD87.
    first of all check status code of the idoc at different stages. so that u can track the problem.
    Regards...
    Arun.
    Reward points if useful.

  • Reprocessing of IDocs

    Hello Gurus,
    Kindly confirm how to reprocess the failed Idocs.
    Can I reprocess in SM35 transaction code to know where exactly it is failed and how to correct the data to successfully passed the IDoc or is there any other method.
    Please it is very urgent.
    Points will be rewarded.
    Thanks
    suresh

    Hi Suresh,
          you can reprocess the failed IDOC using the program RBDINPUT execute it select the status in which ur IDOC is then  execute it then in the following screen give the IDOC number and then execute it...............
         You can do the same using the WE19 where u will give the failed IDOC number and then modify the segments as per yht u want to give and then execute it but in this case it will generate a new IDOC..
    Reward points if this helps...........
    Regards,
    Ravi G

  • Reprocess failed Idoc: new Idoc number?

    Hi,
    I have a failed Idoc no 4711 with status 51.
    Now I want to reprocess the same Idoc because the Idoc content was correct opnly a customizing entry (country) was missing.
    Question:
    Will the system generate a new Idoc which will have status 53 after successful posting and the old idoc No 4711 remains in status 51 for ever? And if so, how can I link the new Idoc to the old failed Idoc in order to control that all faled Idocs have been re-processed successfully? LIKE OPTION A BELOW
    Or will the idoc No 4711 get a new status 53 after successful posting?
    LIKE OPTION B BELOW
    OPTION A:
    Idoc 4711:
    20.01.2010: status 51    error: country 'EN' missing
    Idoc 6767:
    23.01.2010: status 53:   successfully posted (this idoc is the re-processed idco 4711)
    OPTION B:
    Idoc 4711:
    20.01.2010: status 51    error: country 'EN' missing
    23.01.2010: status 53:   successfully posted
    Hope my question was understandable and would appreciate any answer and comment.
    Thanks,
    Thomas

    OR use the transaction code BD87 to reprocess the error IDocs.
    If you process the IDoc using WE19 transaction code a new IDoc number will be created and the status of old IDoc will be unchanged.
    Thanks,
    Bhanu

  • REPROCESSING AN IDOC WITH SAME NUMBER

    hi ppl,
    i hv sent an idoc to the inbound system with a  generated idoc number.
    and now i had added some fields fo the same idoc and have to resend  it to the same inbound system
    with the same IDOC NUMBER.
    how can we RESEND AN IDOC with SAME IDOC NUMBER.
    thanx very much...
    regards,
    RAVI.

    >
    ChakravarthiPonnam wrote:
    > with the same IDOC NUMBER.
    > how can we RESEND AN IDOC with SAME IDOC NUMBER.
    Was that IDOC ended with status 53? If so then I donu2019t think if you could able to edit the segments and reprocess straight forward.
    If that IDOC has been ended with Error then just edit this IDOC(WE02>Double click on segment then from menu "Data record>change") now the status has been change to 69. then just reprocess with BD87.
    NOW, if your IDOC has ended with 53 and you want to edit this then a minute work-around we have to do. Like first change the IDOC status from 53 to 69 then do the same like for error one,
    Cheers
    Amit.

  • Billing output to IDoc & reprocess the IDoc in same sys. to post FI entry

    I have a requirement to send the billing output to IDoc, read the same IDoc to post a FI entry but to another company code. Please suggest how can this be acheived, and is there any other alternative to acheive the above requirement.
    Thanks in advance.

    Hi Naga,
    I have to select the records in JDBC based on different conditions each time. For example I have to select based on company code '1000' and Employee claasification 'E1' and date range. After I post these records in SAP again I want to select other records for some other company code '2000' and different business area and different dates. Basically I want to extract data multiple times based on different conditions.
    -->
    Such requirements cant be handle through select query of the sender...but you can handle this in the message mapping area.....you can fire a select query in the database to pick up records in a batch of 10K (do not keep any condition on this except for sorting). After the records come into PI you can send the message to your target based on the unique combination of "Company code+ Employee clasification + date range" handling this in the message mapping.
    Another question is in the JDBC to IDOC scenario since the sender adapter is JDBC and the sender adapter polls depending on the duration of time ( say 60 secs ) in the adapter once after I extract the data based on a condition how do I control in such a way that the same data is not extracted again.
    You can use the N--> C logic
    The data records that you pick have a corresponding control table i assume. There should be a field STATUS where the initial status of record should be N.
    After you pick the records this status should be made C so that only those records present in the database with status = N are picked up.
    Mention the condition Status = N in the select query.
    Thanks
    Dhwani

  • IDOC - Delete unwanted segments and reprocess the IDOC by WE19

    HI all,
    I have an issue and wanted your help at this point of time.
    Case - Assume that an Idoc has been rejected by system due to few bad segments. Later i dentfied that in the Idoc few segments were bad and rest are good.
    If i use transaction WE19 for copying the Idoc and during selection of the segment if i delete the bad segments and copy the rest which are good. Will the Idoc be processed sucessfully with a new Idoc number so that the Bad segments i will fix it up manually in ERP. Kindly suggest. If possible let me know if any implication behind that or anything you like to add in the process to help me out.
    Kindly advice me.
    Regards,
    Pratap
    Edited by: pratap kumar on Dec 20, 2007 5:02 AM

    Hi Pratap,
    Which Idoc did you process. For each message type certain segments are Mandatory.
    for example in WPUBON01 -->following segments are mandatory
    Control Record --- Message type / Partner Type / Port / Server ID etc.....
    E1WPB01        --- Date / Time / Partner Number etc...
    E1WPB02        --- Article type / Article Number / Quantity etc...
    E1WPB03        --- Condition Type / Amount etc...
    E1WPB06        --- Payment method / Total Amount / card number etc...
    In control record we will have the  port / System ID etc.
    If other segments are not there leave it....it will process successfully.....
    To find out error segment refer  Table  EDID4 and correct the segment and post it.
    Regards,
    ManiKumaar

  • Reprocess Outbound Idocs

    Hi There
    The system has dispached several Idoc to the middleware software, actually all my Idoc have 07 status Error during syntax check, this means that something is wrong with the traslation. I would like to resend all of those messages again to the middleware. I tried trhoght BD87 but I cannot execute this process.
    The operation cannot be carried out with this node type
    Message no. B1891
    Thanks in advance
    Alexis Ramirez

    Hi,
    Set the IDOC status back to 30 using the program RC1_IDOC_SET_STATUS and execute the program RSEOUT00 for all those idoc's then they will be resent again.
    If you use WE19 transaction a new IDOC is going to be generated and moreover you shouldn't use the WE19 transaction in the production environment.
    Thanks,
    Mahesh.

Maybe you are looking for