IDOC PROBLEM (STATUS - 51)

Hi Gurus,
I have two problems that we really need corrected as soon as possible.
1. Before the upgrade last friday night, outstanding IDOCs (51 error) were listed as IncomingInvoices. Now, they are being listed as zBUS2081.
Application document not posted 51
1.Goods Movement
2.zBUS2081
3.service entry
please change it from zBUS2081 back to IncomingInvoices.
2. We've been dealing with an annoying issue since the last major upgrade to SAP. That problem is refreshing. We'll be in transaction BD87, make a correction to an IDOC, back out of the IDOC, push the refresh button, and then we wait.....and wait.....and wait....until we go to the top left, and click the stop transaction option. Then we have to double click back on BD87, get our variant (again), resort the errors, then we're able to click on the edited IDOC option to process the corrected IDOC. Before the last major upgrade, we could make our changes, click the refresh button and BAM the screen would be updated immediately. This is the way it should be working. Would you please look into whatever is causing it to stall? It takes up quite a bit of time to stop the transaction, go back in, refetch the variant, etc. The extra work is unnecessary.
Provide the solution asap.
Regards,
Chiranjeevi.

Please stick to the Rules.
1. Post in the right forum - for IDOCs that will data transfer - now moved for you.
2. Do not say "ASAP" or otherwise express that you're in a hurry.  You maybe - we're not.  Any answers are made out of goodwill.  It is considered by many very rude to try to hurry people up.
3. Don't post the same question in more than one forum.  I've rejected the other one.
Did you copy and paste these issues out of your client/employers help desk?
matt

Similar Messages

  • IP Job in BW finished, but how can I check the IDoc receive status in BW ?

    Hi,experts
    After I execute a Infopackage with loading more than 200000 records data, the infopackage monitor show me yellow light, 186020 from 200000 records. this infomation still show me till now, seaval hours,it looks pause here.
    And I check the request in the R/3, the Job has finished. as you know it means the R/3 push the IDoc already finished.
    and how can I do now ? or how can I check the IDoc receive status in BW side?

    Hi,
    I too had the same problem, i executed the following to solve the proble, may be this will help you:
    1) Go to T-code SM58 and select TRFC and press F6,
    2) For manual push of I-Docs, GO to T-COde BD87 select perticular idoc and see the status if it is not executed properly then do the manual push by pressing Execute option,
    Thanks,

  • 5 IDOC with status 29 Error in ALE service

    hi there,
    im looking at this similar problem with less information on me the only info i got is this can anyone help me out pls
    IDOC Status Outbox:
    IDOC failure between 13/07/2008 to 14/07/2009
    1 IDOC with status 02 Error passing data to port
    5 IDOC with status 29 Error in ALE service
    IDOC Status InBox:
    88 IDOC with status 51 Application document not posted
    regards
    raju

    Hi,
    Check this thread.
    DB13-DBCHECK by saving log-throwing DUMP:TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
    Regards.

  • 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

  • Report RBDAPP01 not processing IDocs in status 51

    Hello guys,
    I have a problem with the execution of some Inbound Idocs using program RBDAPP01.
    Now the Idoc is executed in background with a job. Sometimes we have some locks because we receive idocs going to the same order, and then remain in status 51.
    In the variant of the job we filled to execute Idocs with status 64 and 51, but the idocs that remain in status 51 are not processed, at the end we have to do it manually.
    There is no parallel processo to avoid the locks.
    Do you know how we can solve it?
    Many thans in advance.
    Regards,
    Xavi.

    i do have the same problem. is there an solution to this?

  • Aleaud idoc in status 56

    hi i work in production support and new to idocs this is the problem given to me i have to solve it asap. when i check the idocs in we02 transaction it shows idocs in status 56 with a message ipartner profile inbound not available.
    DETAILED DESCRIPTION OF PROBLEM.
    inbound ALEAUD idocs that error with status 56.   These clog up & slow down
    workflow- as we are getting over 10,000 of these per month.     For example:
    when we work on inbound invoices that error, it's slower.  (using transaction
    SBWP)    I'm NOT saying ALEAUD idocs are related to inbound invoices, just
    saying that SBWP gives us access to variety of idocs and it's been running
    slower due to large amount of ALEAUD idocs erroring into workflow every day.
    Best I can tell- looks like for every PO & PO Change idoc we send to
    SupplySync, we get ALEAUD in response a few seconds/or a minute later.
    **See examples on attached Word document, for date of 9/27/05.
    Also I checked several different dates and the count/total number of:
    PO documents sent    VS   the inbound ALEAUD idocs recvd- always matches
    within a count of 1 or 2.
    Ex: on  9/27/05     PO docs sent = 663       ALEAUD recvd = 664
    Would like to have:
    A) ALEAUD idoc creation stopped- if not serving a purpose
    B) OR?- have them post successfully instead of erroring in workflow
    Or- have workflow purged periodically, if can't do A or B above.
    Regardless of how this is resolved- need backlog of ALEAUD purged from
    workflow.  
    any kind of help in solving this problem would be great
    thanks
    noor.

    Hi thanks for reply its very helpful if possible could you plz give more details about the oss notes 153205 it had a look at it talks about report RSWWCIDE to delete type c work items i also saw its selection screen
    The selection parameters of the report have the following meaning:
    id - ID of the work item -> please always restrict here !!!
    cd - creation date of the work item
    ct - creation time of the work item
    commitc - number of the ContainerItems to be deleted for each LUW
    del_log - also delete the history of the ContainerItems
    disp - only list selected ContainerItems
    does this report deletes the idocs does mean on id of work item i have to enter the idoc numbers which i want to delete and then all idocs nos i enter gets deleted is it so? can youplease give more details.
    thanks

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

  • Aggregated IDOC partly Status 51

    When dealing with aggregated inbound IDOCS the Status 51 can be seen about 10% of all Status- Sets for different reasons. The worst is: The Switchdoc is currently block by <TheRCFUser> (here having EDIFACT/UTILMD/E03)
    After that the complete Message won't be processed any further.
    Is there a way to easily restart this IDOC for those segments with Status 51 (or better: for all segments not having 53 so far).
    Maybe with the option to change the IDOC- Data before reprocessing (in case there is some stupid mistake like , instead of .)
    Anybody facing the some problem and having a solution?
    Regards, Daniel

    Dear Math,
    Have you got the solution for the above. If you get can you tell me please because even i got the same error message while processing the IDOC
    status 51 after status 53. Outbound delivery is updated but not the sales order.
    can you please help me

  • Idoc and status (68)

    Hello all,
    My customer gets sometimes inbound messages with status 51 that can't be processed automatically (with BD87 or other). For a few kinds of messages, my customer corrects the problem manually in the target business document => The relevant idoc won't have to be processed in the future.
    We would like to change the status of this idoc in order to identify it as an idoc that :
    - has never been processed => status <> 53
    - are never should never be be processed => status <> 51
    Status 68 seems to be defined for such a request.
    Is it the case ?
    How can I turn my Idoc status from 51 to 68 with a business transaction (without using RC1_IDOC_SET_STATUS). (I want an User action)
    Thanks a lot
    J.C.

    Hi JC,
    Yes, with status 68 the Idoc cannot be send to application again.
    If you need the user change the status manually, maybe you could generate a new transaction for this pourpose associated to a abap program that performs first a selection of Idocs with status 51, and later performs an user action that simply call IDOC_STATUS_WRITE_TO_DATABASE function module to change them to 68 .
    Regards,
    Roger

  • Reprocessing IDOCS with status 52

    Hi all,
    I facing a problem with IDOC status 52.
    After correcting the error it had given, I want to reprocess it again.
    Kindly tell me any report or transaction name for reprocessing IDOC with status 52.
    Regards,
    Rahul

    Hi Rahul,
    You can use the below Programs for IDocs Reprocessing:
    RBDMANI2 : Reprocess Idocs manually
    RBDMANIN : Posting of IDocs with Status 51
    RBDMOIND : Outbound Idocs status 03->12
    RSEOUT00 : For Processing 30 Status IDocs
    RBDAPP01 : For Processing 64 Status IDocs
    RBDAGAIN : Reprocess Incorrect Outbound IDocs
    RBDAGAI2 : Reprocessing of IDocs after ALE Input Error
    Regards
    Aneesh.

  • How to cancel an idoc in status 64

    How to cancel an idoc in status 64

    Hi Manju,
    If you have table updation access then
    Go to SE16 --> Table EDIDC --> Give your "IDoc number" -->  change the status from 64 to "73 IDoc archived".
    Or you can ask to your ABAPer to do that.
    Hope it helps,
    Regards,
    MT

  • STPPOD Idoc creation status : Error in ALE Service

    Experts,
    I am trying to send GR from MM to SUS in MM-SUS Classic Scenario on ECC 6.0 Server. I have also configured Goods REceipt Notifications Functionality to sending GR from MM to SUS.
    When i am trying to send GR Idoc is generated (STDPOD) but i am getting the Error whose status - 29 in WE02 t-code :
    Status Message for Selected IDoc
    Status Text:   IDoc: 0000000000211243 Status: Error in ALE service
    T100 Text:     Entry in outbound table not found
    While i have properly configured Partner Profile for  Message Type STPPOD :
    Partner Role          Basic Type     Receiver Port           Application     Output Mode
    LS        DELVRY03       A000000018 (XI port)           GRN               Transfer Idoc Immediately
    When i try WE19 t-code for this idoc, i found  the error "Port '' does not exist in the table of port descriptions"
    while  i have already defined port (A000000018)in WE21 t-code  and this port also working fine for other messages.
    Please suggest.
    Thanks.
    Regards,
    Pawan Keshwani

    Nikhil,
    Issue is resolved it was the wiered error. As i removed LS from the field  Partner Role in STPPOD message at  partner profile(WE20) for SUS Client in ECC. Now the message STPPOD outbound message working fine.
    Thanks.
    Regards,
    Pawan Keshwani

  • SAP IDOC shows status 03, but no file is written

    We have SAP configured to generate delivery IDOCs when the SAP Delivery document is posted/saved. The IDOC is initially created with status 30. There is batch job RSEOUT00 every 30 mins that collects the IDOCs in status 30 and converts to status 03. When we review the IDOC processing screen, even though they are in status 03 and successfully written outside of SAP to a folder, there is no file in the folder. We are missing IDOCs. There is no real time external system integration. We are simply trying to write IDOC files to a folder.
    Can you some please share your insights on how to resolve this issue?
    Thanks in advance
    Satish

    RFC destinations, Logical systems, and then Partner profiles needs to be maintained. and You need to create the Distribution model  in sender system.
    Partner profiles maintained in both the systems, soure Outbound properties
    Target Inbound properties.
    if you have two clients in system it will be easily you can check.

  • Idoc- can we sent already sended idoc if status is showing error message

    hi
    Idoc- can we sent already sended idoc if status is showing error message
    without making any changes.
    Thanks in advance.

    Hi raja,
    IN BD87.
    give the idoc number,its status,messagetype and partner system and resend it.
    Regards,
    nagaraj

  • Query on IDOC Ack (STATUS) config in XI for a specific partner comm.

    Hi Experts,
    Is it possible to configure the IDOC Ack (STATUS.SYSTAT01 message) in XI for a specific partner communication? We want to configure our system like ALEAUD but the message type should be STATUS.SYSTAT01 and the acknowledgment should be send to sender system for a specific partner only if XI receives any IDOC like (Orders) from that specific partner. For other partners (same sender system) we donu2019t want this acknowledgment settings and configuration. If possible please provide the configuration filters steps etc. Thanks for your valuable inputs in advance.
    Thanks,
    Satish
    Edited by: Satish Jaiswal on Jan 8, 2009 2:55 AM

    Hi Husain,
    I have the document you have mentioned. Please note my requirement is to filter the Ack while creating and sending to R/3 based on Partner and Message type. The document provides info only on Message type filter but not parner specific for same sender system!!! Any help appreciated. Also note: BPM and Alert is out of scope.
    Looking for  some ALE configuration tricks to achieve this.
    Thanks
    satish
    Edited by: Satish Jaiswal on Jan 9, 2009 2:40 AM

Maybe you are looking for