Test IDoc data posted into application document correctly

Hi,
I'm new to IDocs.
I need to test some inbound idocs if the data is correctly posted as Application document(PO).
But currently the partner profile is not set in the system.
When i tried to process the idoc using RBDAPP01 i'm getting the status as 'Error passing IDoc to Application'
Is it possible to process idoc by any other way for testing, to create PO and data is populated correclty in PO.
Thanks in advance,
poornima.

Hello,
          You can go to the Transaction WE19 (Test Tool for IDoc) and select an Idoc based on the Idoc Type that you want to Test & Post. While Posting the IDoc from WE19, the Partner Profile Check will be ignored and it will not be a Fatal Error even if you've not maintained the Partner Profile for the Incoming IDoc.
Refer to the Following Link which contains Instructions about Testing an Inbound Interface using the Test Tool.
http://help.sap.com/saphelp_nw70/helpdata/en/dc/6b814443d711d1893e0000e8323c4f/frameset.htm
Hope it would be helpful.
Thanks and Regards,
Venkat Phani Prasad Konduri

Similar Messages

  • IDOC Number for a Application document

    Hi frinds,
    Using Idocs we create application documents like Sales orders(inbound),invoices, delivery etc (outbound) to create application document in some other system or used in case of B2B scenario.
    my requirement is can we get the Idoc # form the slaesorders number using some function module (to get the idoc #'s of huge number of sales orders). however we can find the sales order number form the Idoc number using WE05 i want the reverse way.
    Thanks,
    vin.

    Hi,
    If your requirement is like Xi generates an outbound idoc to R/3 which is different to inbound idoc number of R/3.
    USe SREL_GET_NEXT_NEIGHBORS  ,
    object-objkey = idoc num  object-objtyp = 'IDOC', max_hops = '99'.
    You can get the list of outbound,inbound idoc numbers and sales order .
    Thanks and Regards,
    P.Bharadwaj
    Edited by: Bharadwaj p on Jun 14, 2010 8:31 AM

  • Error "Application document not posted" when tried to receive an idoc

    Hi All,
    My scenario is File to IDOC. the idoc reaches the R/3, but when i check in the transaction we02, under Inbound IDOCS, i see my idoc in status 51 - Application document not posted.
    Does it mean idoc has reached R/3, but it didnt update the respective table in R/3? i'm sending idoc of type MATMAS05, its supposed to update table MAKT, but its not. Do i need to make any special settings for this? pls help me, its urgent.
    Thanks & Regards,
    Bhavana

    Hi,
    The IDOC is successfully coming from XI, but there is problem in R\3 end.
    Idoc status is 51 with "Application document not posted"
    This indicates that the logic for posting the application document is not coded properly in inbound function module. Verify the logic once again.
    Also you need to confirm that the data related or in application configuration is right. If the data values are not correct the above error get generated.
    refer blow link for the program
    http://help.sap.com/saphelp_nw04/helpdata/en/78/21760251ce11d189570000e829fbbd/frameset.htm
    Thanks
    Swarup
    Edited by: Swarup Sawant on Jan 28, 2008 11:13 AM

  • How to trace an Inbound R3 IDoc by seeing application document

    Hi all,
    How to trace an Inbound IDoc number by seeing application document in R3.
    sometimes 'Services from object' also we could'nt able to trace out the IDoc.
    'Services from object'  option sometimes appears in blank status with no IDoc.
    Any possible tracing options?

    HI Chitra,
    You can findout the Idoc number in R/3 System by using the  tr.code WE05 or WE02.
    Go throgh the following blog for message monitoring.
    /people/alessandro.guarneri/blog/2006/02/14/super-message-monitor-for-sap-xi
    Regards
    Goli Sridhar

  • Reg : IDOC data mapping

    Hi All,
    Which is the function module which Extracts the data from the application document ( Sales order or quotes ) and populates to the SAP message type Idoc segments.
    what are the SAP table involved in doing this mapping.
    Thanks & Regards.
    vijay

    Unfortunately the mapping is not in any table but in the source code as extracted here:
    e1cuins-class_type        cuins-class_type
    e1cuins-inst_id           cuins-inst_id
    e1cuins-obj_key           cuins-obj_key
    e1cuins-obj_txt           cuins-obj_txt
    e1cuins-obj_type          cuins-obj_type
    e1cuins-quantity          cuins-quantity
    e1cuprt-class_type        cuprt-class_type
    e1cuprt-inst_id           cuprt-inst_id
    e1cuprt-obj_key           cuprt-obj_key
    e1cuprt-obj_type          cuprt-obj_type
    e1cuprt-parent_id         cuprt-parent_id
    e1cuprt-part_of_no        cuprt-part_of_no
    e1cuval-author            cuval-author
    e1cuval-charc             cuval-charc
    e1cuval-charc_txt         cuval-charc_txt
    e1cuval-inst_id           cuval-inst_id
    e1cuval-value             cuval-value
    e1cuval-value_txt         cuval-value_txt
    e1edk01-autlf             xvbak-autlf
    e1edk01-belnr             ekko-ebeln
    e1edk01-bsart             ekko-bsart
    e1edk01-curcy             iso_waers
    e1edk01-kzabs             pekko-kzabs
    e1edk01-kzazu             xvbkd-kzazu
    e1edk01-lifsk             xvbak-lifsk
    e1edk01-recipnt_no        ekko-lifnr
    e1edk01-vsart             xvbak-vsbed
    e1edk01-zterm             ekko-zterm
    e1edk02-belnr             ekko-angnr
    e1edk02-belnr             ekko-ebeln
    e1edk02-belnr             ekko-konnr
    e1edk02-belnr             ekko-submi
    e1edk02-belnr             pekko-labnr
    e1edk02-datum             ekko-bedat
    e1edk02-uzeit             sy-uzeit
    e1edk03-datum             ekko-angdt
    e1edk03-datum             ekko-bedat
    e1edk03-datum             ekko-bnddt
    e1edk03-datum             ekko-bwbdt
    e1edk03-datum             ekko-ihran
    e1edk03-datum             ekko-kdatb
    e1edk03-datum             ekko-kdate
    e1edk03-datum             pekko-eindt
    e1edk03-datum             sy-datlo
    e1edk14-orgid             ekko-bsart
    e1edk14-orgid             ekko-bukrs
    e1edk14-orgid             ekko-ekgrp
    e1edk14-orgid             ekko-ekorg
    e1edk17-lkond             ekko-inco1
    e1edk17-lkond             xvbkd-inco1
    e1edk17-lktext            ekko-inco2
    e1edk17-lktext            xvbkd-inco2
    e1edk18-prznt             ekko-zbd1p
    e1edk18-prznt             ekko-zbd2p
    e1edk18-tage              ekko-zbd1t
    e1edk18-tage              ekko-zbd2t
    e1edk18-tage              ekko-zbd3t
    e1edka1-bname             ekko-verkf
    e1edka1-bname             t024-eknam
    e1edka1-ihrez             ekko-ihrez
    e1edka1-ihrez             ekko-unsez
    e1edka1-ilnnr             h_iln_vendor
    e1edka1-lifnr             h_pekko_werks
    e1edka1-lifnr             pekko-werks
    e1edka1-orgtx             t024e-ekotx
    e1edka1-pagru             ekko-ekgrp
    e1edka1-paorg             ekko-ekorg
    e1edka1-partn             ekko-lifnr
    e1edka1-partn             ekko-logsy
    e1edka1-partn             lfa1-lifnr
    e1edka1-partn             lfb1-eikto
    e1edka1-partn             pekko-kunnr
    e1edka1-partn             t000-logsys
    e1edka1-partn             xvbpa_we-kunnr
    e1edka1-parvw             'EZ'
    e1edka1-parvw             h_parvw
    e1edka1-parvw             'LF'
    e1edka1-parvw             'WE'
    e1edka1-spras             ekko-spras
    e1edka1-telf1             ekko-telf1
    e1edka1-telf1             t024-ektel
    e1edka1-telfx             t024-telfx
    e1edkd1-ekgrp             ekko-ekgrp
    e1edkd1-ekorg             ekko-ekorg
    e1edkp1-defpa             xekpa-defpa
    e1edkp1-ekorg             xekpa-ekorg
    e1edkp1-lifn2             xekpa-lifn2
    e1edkp1-ltsnr             xekpa-ltsnr
    e1edkp1-parvw             xekpa-parvw
    e1edkp1-werks             xekpa-werks
    e1edkt1-tdid              xt166a_del-tdid
    e1edkt1-tdid              xt166k_del-tdid
    e1edkt1-tsspras           ekko-spras
    e1edp01-abftz             ekpo-abftz
    e1edp01-antlf             xvbap-antlf
    e1edp01-bmng2             ekpo-ktmng
    e1edp01-bmng2             ekpo-menge
    e1edp01-bpumn             ekpo-bpumn
    e1edp01-bpumz             ekpo-bpumz
    e1edp01-brgew             e1edp01-menge*ekpo-brgew
    e1edp01-evers             ekpo-evers
    e1edp01-gewei             ekpo-gewei
    e1edp01-kzabs             ekpo-kzabs
    e1edp01-lgort             ekpo-lgort
    e1edp01-matkl             ekpo-matkl
    e1edp01-matnr             ekpo-matnr
    e1edp01-menee             ekpo-meins
    e1edp01-menge             ekpo-ktmng
    e1edp01-menge             ekpo-menge
    e1edp01-netwr             ekpo-netwr*cur_factor
    e1edp01-ntgew             e1edp01-menge*ekpo-ntgew
    e1edp01-peinh             ekpo-peinh
    e1edp01-pmene             ekpo-bprme
    e1edp01-posex             ekpo-ebelp
    e1edp01-posguid           xvbap-posguid
    e1edp01-pstyp             ekpo-pstyp
    e1edp01-uepos             ekpo-uebpo
    e1edp01-vprei             ekpo-netpr*cur_factor
    e1edp01-werks             ekpo-werks
    e1edp02-belnr             ekpo-aktnr
    e1edp02-belnr             ekpo-konnr
    e1edp02-belnr             ekpo-labnr
    e1edp02-belnr             h_xvbkd-bstkd_e
    e1edp02-belnr             xvbap-werks_ext
    e1edp02-belnr             xvbkd-bstkd_e
    e1edp02-bsark             h_xvbkd-bsark_e
    e1edp02-bsark             xvbkd-bsark_e
    e1edp02-ihrez             h_xvbkd-ihrez_e
    e1edp02-ihrez             xvbkd-ihrez_e
    e1edp02-zeile             ekpo-ktpnr
    e1edp02-zeile             h_xvbkd-posex_e
    e1edp02-zeile             xvbkd-posex_e
    e1edp03-datum             ekpo-abdat
    e1edp03-datum             ekpo-agdat
    e1edp17-lkond             ekpo-inco1
    e1edp17-lkond             xvbkd-inco1
    e1edp17-lktext            ekpo-inco2
    e1edp17-lktext            xvbkd-inco2
    e1edp19-idtnr             ekpo-ematn
    e1edp19-idtnr             ekpo-idnlf
    e1edp19-idtnr             ekpo-matnr
    e1edp19-ktext             ekpo-txz01
    e1edp20-ameng             xeket-ameng
    e1edp20-ameng             xeket-wemng
    e1edp20-edatu             xeket-eindt
    e1edp20-ezeit             xeket-uzeit
    e1edp20-wmeng             xeket-menge
    e1edpa1-partn             ekpo-kunnr
    e1edpa1-partn             xvbpa_we-kunnr
    e1edpd1-bednr             xekpo-bednr
    e1edpd1-bstae             xekpo-bstae
    e1edpd1-insmk             xekpo-insmk
    e1edpd1-knttp             xekpo-knttp
    e1edpd1-kzabs             xekpo-kzabs
    e1edpd1-labnr             xekpo-labnr
    e1edpd1-lgort             xekpo-lgort
    e1edpd1-mahn1             xekpo-mahn1
    e1edpd1-mahn2             xekpo-mahn2
    e1edpd1-mahn3             xekpo-mahn3
    e1edpd1-mwskz             xekpo-mwskz
    e1edpd1-prsdr             xekpo-prsdr
    e1edpd1-schpr             xekpo-schpr
    e1edpd1-spinf             xekpo-spinf
    e1edpd1-uebtk             xekpo-uebtk
    e1edpd1-uebto             xekpo-uebto
    e1edpd1-untto             xekpo-untto
    e1edpd1-webre             xekpo-webre
    e1edpd1-werks             xekpo-werks
    e1edpt1-tdid              xt166p_del-tdid
    e1edpt1-tsspras           ekko-spras
    e1eds01-summe             ekko-ktwrt*cur_factor
    e1eds01-summe             pekko-netwr*cur_factor
    e1eds01-sunit             iso_waers
    Whenever you have qualifiers, the segments appear multiple with diefferent fields.
    Regards,
    Clemens

  • Merging XML Data to make many documents

    Hello,
    Here's where I am at:
    I've used LifeCycle Designer to create a PDF with all the forms named. I have XML data for all my companys. The XML data merges into the document, and fills in the form perfectly.
    However, I'm looking to take this one step further, and automate the process. Meaning, Putting all the company data in one file, and importing the data to make PDF forms for each company.
    Similar to a mail merge. --Lots of different Companys, Fill in thier each individual page.
    What are the steps to do this?
    Thanks!
    --Jeff

    Yes.
    You can do one of the following:
    a) Build a custom application using the LiveCycle Forms api.
    b) Use the RenderForm QPAC within a workflow to convert the XML to a PDF.
    The RenderForm QPAC is a little obscure to use - read the documentation VERY carefully, and be very careful about the values you enter, otherwise it won't work. It does work perfectly if you get all the values right. In my experience, you do need to enter a username and password, even though these are not noted as mandatory fields.
    Howard
    http://www.avoka.com

  • Edit Idoc data and reprocess..?

    I have created one inboubd idoc this idoc is failed..
       i want to change some data in the idoc and reprocess the idoc ..how can i do this..?

    Hi,
    You can right click on the Idoc and then open the same in edit mode.
    Also in the menu tabs, you will find an option EDIT AND REPROCESS.
    This way you can process the idoc and post the same with correct values.
    PS: Not infront of SAP system so not able to tell the exact path. But do some R&D you will get the same.
    Hope this wud be of help!!!
    Regards,
    Lalit Kabra

  • Inbound idoc application document not posted

    Hi,
    idoc status is 51 i.e. application document not posted.. when im tyring to send the cm data to other system it is successfull and doing some modifications in that and the same is sent from the other non-sap system to sap system.
    During the sending from non-sap to sap system, the inbound idoc is getting the error as 51. and also providing some field name as kna1-cassd is not an input field.
    This field is not being provided with any value but still the idoc is getting error with this field.
    "Even i tried in the sap system itself, taking some sample data tested in we19 and executing with inbound idoc f.m:IDOC_INPUT_DEBITOR.. still the  idoc is getting error message as 51 (with the same field).
    Please provide your valuable suggestions to solve this problem.
    I had created one cm and tried but still the same message is comming.
    Awaiting your help.
    thanks
    rohith

    Thanks for all your suggestions..
    The problem is that im using the standard function module:IDOC_INPUT_DEBITOR..
    So, this function module cannot be modified which is not my requirement.
    My requirement is that i will send an outbound idoc to some non-sap system and now the non-sap system will make some modifications and resent to sap system (here in sap it is an inbound processing).
    So, during inbound processing the status is showing as 51 due to the field kna1-cassd..
    So i cannot make any customization but the inbound processing should be done and it should be saved into the db...
    Hope you have got a clear requirement.
    Waiting for your response.
    Thanks
    rohith

  • Inboun IDOC status 52--Application document not fully posted

    Hi,
    In Inbound IDOC, the status code is 52 ---> Application document is not fully posted(satus of the inbound idoc is in yello colour). I want to reprocess this idoc in BD87 t.code in order to convert the yellow colour to green colour. Before reprocessing the IDOC, i need to rectify the problem and then reprocess the idoc in bd87. am i correct? if yes, what i need to do to solve the error --->application document not fully posted. Please guide me friends.
    Thanks in advance.
    Regards,
    Sri

    I am attaching how we documented the process in our troubleshooting guide.  Graphics were not pasted.
    21.3       Manually run IDOCs reported as 52.
    It is possible that IDOCs are found in status 52 for the daily updates.   In principle IDOCs 52 can not be re-proceeed, but there is a way to push the appropriate data from a source system, e.g. ERP.    Following is the process.
    21.3.1     You find IDOCs in status 52 in WE02.
    21.3.1     Open table EDIDS.
    Perform 2 searches for parameter STAPA2 and STAPA1 in status 52 and download the entries for each column to an MS Excel file.
    21.3.2     Adjust the MS Excel file.
    The strings STAPA2 and STAPA1 have to be truncated and separated into 3 different fields for processing:  First 2 characters are the Plan Number, next 2 the Object Type, and next 8 the Object Number.
    21.3.3     Manually process the entries via transaction PFAL from the source system, e.g. ERP.
    The entries must be processed in the following order sorting by Object Name:
    u2022     STAPA2s first, then STAPA1s.  
    u2022     Each organized by O, S, P, C, and CP.
    21.3.3.1     Running individually for each entry.
    By running PFAL with the individual entries:  Plan number, Object Type, Object Number,  Update mode,  Target Logical System name  ... the respective IDOC will be passed to target system for processing.
    21.3.3.2     If there are many entries for processing.
    If there are many STAPA2 and STAPA1 for processing.
    u2022     Create a text file like the one below with the entries as mentioned above.
    u2022     Logon into the source system and make sure CATTs are allowed..
    u2022     Via SCAT, create a CATT that emulates the execution of PFAL entering Plan number, Object Type, Object Number, Update mode,  Target Logical System name  ... the respective IDOCs will be passed to the target system for processing.
    . Create the text file with the entries.
    .  Execute the CATT ... the respective IDOCs will be passed to target system for processing.

  • IDOC is created with status 51( application document not posted)

    Hi experts
    iam working on File-IDOC scenario, when i test the process the XML message is created with no errors and
    but the IDOC is created with status 51( application document not posted)
    the details error shows:
    An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
    during a synchronous update.
    The error was caused by the transaction VA01.
    previously i used same test data that time it was working fine,
    please tell me how can i fix the issue.
    regards
    vasavi

    Key in your Idoc number in BD87, execute
    select the error message and then follow the menu path :
    EDIT --> restrict and process  (Select)
    In the next screen UNCHECK the Bkgd Processing and execute
    Now EDIT --> Process --> foreground from error or in foreground mode.
    This will lead you the screen where it errored out.
    Thx
    PSR

  • Urgent: Error in idoc(Application document not posted)

    Hi experts,
    i am getting the error in R/3 side when i am extracting data from it.
    i checked with WE07 it's shows the error as follows
    "Application document not posted".
    it's been urgent how to resolve this issue. please through a light on it.
    Regards
    Harikrishna N

    Hi Hari,
    You start error processing by executing the corresponding work items in your Business Workplace. If a file read error could be corrected, for example, the IDocs which have not yet been read can be read and stored in the database manually, by starting report program RSEINB00.
    This could be the reason for ur error..
    IDoc could not be generated under MC
    EDIN: Evaluates the partner data from the MC record
    TS70008037
    No process code in the additional partner profile MC parameters; Error when writing the application data in the IDoc.
    this link givs u the req info
    [http://help.sap.com/saphelp_nw70/helpdata/EN/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm]
    Hope it helps U
    Regards,
    NR

  • Inbound IDOC error - status code 52- application document not fully posted

    Hi,
       In Inbound IDOC, the status code is 52 ---> Application document is not fully posted(satus of the inbound idoc is in yello colour). I want to reprocess this idoc in BD87 t.code in order to convert the yellow colour to green colour. Before reprocessing the IDOC, i need to rectify the problem and then reprocess the idoc in bd87. am i correct? if yes, what i need to do to solve the error --->application document not fully posted. Please guide me friends.
    Thanks in advance.
    Regards,
    Sri

    HI
    If you are FM to process the inbound  IDOC,
    possibilities are like below .
    Reason 1 :
    In partner profiles, check is it trigger immediately or not ? for particular partner profile which u r using .
    reason 2 :
    If you are using BDC code to update the data .if any screen contains error then also you will get the status in yellow .
    reason 3 :
    Have you tried with  TCODE  BD87 ,  might be it is processing error also .
    i have worked on same probelm so  if u r not solved with the issue after trying above 3 reasons .
    reply me back .

  • BI extraction error --  Application document not posted - IDOC Status 51

    Hi,
    I am getting the following error while extracting data from ECC to BI.
    'Application Document not posted'
    I went to BD87 in ECC and found that the Idoc Status is 51 and the message is
    'Request REQU_4C65QV...V9QRNZ2X9TV9QRNZ does not exist in target system N05CLNT100'.
    I have already checked partner profile parameters with Basis and they claim everything is okay.
    Do you have any ideas what might be the issue?
    Thanks,

    Hello Rajendra,
    You can review the note 417307 which contain information about the MAXSIZE of a  package size. This is a collective note which contain more notes to other extractors.
    417307 - Extractor package size: Collective note for applications
    549184 - FAQ: What is important for extraction
    157652 - Main memory requirement for extraction from R/3
    You can review the table ROIDOCPRMS and check if the parameter StatFrqu contains a 'X' or a number? You can set this option to 99.
    You can also review the correction note 1147326.
    Check as well if the user ALEREMOTE have the proper profiles configured in both source and target system, sometimes the user is missing the profiles, to check this, read the note 150315.
    I hope that the information can help you.
    Regards,
    Daniel

  • Idoc number have status  is   51     Error: Application document not posted

    hi friend
    i have error in idoc number status  51     Error: Application document not posted. basic type is  ORDERS05   Purchasing/Sales
    what i do for solve this issue
    with regards
    dinesh
    Edited by: code acess on Feb 9, 2011 4:35 AM

    Hi,
    {1.how i check in the delivery documents have idoc number ? }
    Go into the delivery, output. Check if any output has been triggered for EDI. If yes, then select the output and click on 'Process details' (it is the button just after communication where you give the print name). It will display the Idoc number.
    { what are the required for cofiguration of EDI. Pls Send me the configuration setting . i didnt have help here ..iam expecting configuration setting }
    Though it is difficult to share all the config settings in this thread, what I will do is to put in a few steps which are general settings. Only a few things vary.
    For EDI / ALE - Idoc the common settings are
    a. The port should be enabled for sending and receiving the data thru Idocs. Usually basis does this.
    b. Partner profile should be configured in WE20. Example if you are sending a sales order confirmation to ship to party then, You should set up a partner profile in WE20 for partner number in KU (Customer) folder. You can copy any of the existing customer. What you have to make sure is you have added the message type and the Basic Type in the outbound parameters of the partner in WE20. Also, you have to make sure that you are giving the output type and the process type as well.
    This is same even when you are receiving the Idocs from customer. Say for example customer PO. However, instead of outbound, you will add all these details in inbound. 
    Similarly, if you are sending PO to your vendos, then, you have to make changes in folder for partner LS. There are so many other folders as well.
    Check WE60/61 for the documentation for what is Basic types, Message types and segments. It is very important for you to know about these when you are dealing with Idocs. To start with, you can give Orders01 in Basic types in WE60 selection screen and read out the details.
    c. Once the partner profile is set up, there is a table called VOE4. This is the table where you can maintain the customer cross reference for incoming idocs.
    d. Output type should be set up for EDI trigger (Tcode NACE) . You can use the existing programs. You can Check BA00 which is normally set up for EDI trigger as well. You can try triggering that first. You may get some errors at first. But do not panic. Just read those errors and then search the form for errors. You will get to know the next step.
    e. Once you have the above settings, I think you are pretty much ready for EDI... you can try these. If you get struck in between, the form is there to help you...
    Hope this helps...
    Regards,
    Mukund S

  • Request IDoc : Application document not posted

    I am loading master data in the development system for the first time after the basline config. I am getting the following error.
    Request IDoc : Application document not posted

    Hi
    Recheck the Connectivity RFC & IDOC too. you may ask basis for help.
    verify the IDoc things no problem, connection and authorization between bw and r/3 established well.
    try check in monitoring - menu environment
    -> 'ale management' - in datawarehouse and in source system.
    take a look oss note 520012.
    Symptom
    RSINFO Idocs with status 51 are repeatedly sent to the top. IDOCs with status 51 (document not posted) queue for ALE inbound processing. This may slow down the system.
    Other terms
    IDoc RSINFO, status 51, bd87, we05, RSRQST, R3 013
    Reason and Prerequisites
    The requests are started periodically and cause a R3 013 error message; the message is sent to the BW system but the requests retain a status 51. You can display the IDOCs via transaction we05. Enter RS* in the 'Logical message type' field and execute the process. You can also display the IDOCs with transaction bd87.
    Solution
    IDOCs with status 51 can be selected for deletion by running the 'RBDMANIN' report; do not use the 'Import in the background' indicator (you must manually remove the indicator).
    Each relevant IDOC is then processed separately in the foreground and you can decide for each IDOC if you want to select it for deletion.
    Hope it helps

Maybe you are looking for