Idoc status error 66 - IDoc must be processed later; 000006 , IDoc no. 0000

Hi,
The following error appears when a particular Idoc is trying to get posted
Status 66 - IDoc is waiting for predecessor IDoc (serialization)
Message  - "IDoc must be processed later; 000006 , IDoc no. 000002 required."
What is this error all about? How do I find out which is the predecessor Idoc which has to be posted first. I can not find any other idoc numbers mentioned here.
Thanks in advance

Rhea,
What you have mentioned is clear for me too. But the question is how do I trace the predecessor idoc? 0002 or 0006 are not Idoc numbers. They are Idoc types.
Any way in which I can trace out the predecessor idoc?
Regards

Similar Messages

  • IDOC: Status (Error/Success/information)report to Sender system

    How would one send a message(error/success/information) to the sending(external) system to inform them of the statuses of the messages they've sent to our SAP system?

    Hi Baumann,
    you have an option called Audit reporting in which you can have the status of idoc at sender side.read the following.
    Setting Up Audit Reporting
    In the default behavior, after an IDoc is dispatched to a destination system, the sender does not know the state of the process on the destination system. You can configure the system, however, for cross-system reporting. You must model the ALEAUD message between the systems.
    Two programs enable cross-system reporting.
    1)RBDSTATE. This program is scheduled to run periodically on the destination system. It reports the status of incoming IDocs to the sending system, using the ALEAUD message and ALEAUD01 IDoc. This status information is recorded separately from IDoc status information in the audit logs.
    2)RBDAUD01. This program is executed on the sending system. It analyzes the audit log and displays the output as a report.
    The RBDSTATE program returns the following statuses, from the receiving to the sending system.
    RBDSTATE Is Run on the Receiving System
    Status of IDoc in receiving system     Status reported to sending system via ALEAUD
    53 (Application document posted.)     41 (Application document created in receiving system.)
    51 (Error: Application document not posted.)     Status 39 (IDoc is in the receiving system.) This status is repeated each time RBDSTATE is run, as long as the IDoc remains in status 51.
    68 (Error: No further processing.)     40 (Application document not created in receiving system.)
    reward points if helpful,

  • IDoc status error 51 : A company code cannot be determined for LS

    Hi,
    We are trying to post an Idoc into R/3 but getting the IDoc status code 51 :  A company code cannot be determined for LS
    What could be the possible reason?
    Should we use Party in Receiver IDoc scenarios?

    Hi,
    I have quite the same problem. I built an IDOC with WE19 and I have the message "A company code cannot be determined for LI 0000031004".
    As explained in note OSS 117808, the partner number (31004) and partner type (LI) are read from the control record of the IDOC. I enter this values in OBCA and OBCE customizing points, to determine the company code 'LC'. It doesn't work.
    PT Rao, what do you call "activate partner profile" ?
    Thanks in advance.
    Regards,
    Arnaud

  • Idoc Status error 29 for Out bound Idoc( Receiver of IDoc is its own logic)

    I try to create the Out bound Idoc with messag type WMMBXY ( basic Idoc type - WMMBID02 ).
    which is configured with the out put type XXXX in VT01N( shippment creation). But I am getting the error status 29 in the Idoc.
    Only I am passing the sender, receiver port , partner type and partner function to the communication structure.
    Could you please tell me , what is the issue with the partner type configuration .

    Hi,
    Error 29 occurs when there is an incomplete or no partner profile maintained.
    Check whether you have done the correct partner profile settings in WE20 outbound parameters.
    For the partner no defined in Idoc check whether there is an entry(under partner type LI, KU or LS)
    with correct message type WMMBXY  and Idoc type WMMBID02. Also check for message function code.
    Regards,
    Savitha

  • Idoc status error 37 in sender and 51 in recieving system

    i m new to ale idoc n created 2 clients 910(sender system) and 800(reciever system)
    all connections are well i got status message 03 and 30 and 01 but along with it i m getting one more idoc genersted and status as 37 . idoc no. 50 as 03 30 and 01 and idoc 51 as 37 . in sender system n inreciever system i m not getting idoc.after sumtim i m getting them n error status as 51 .two idocs are generated simultanously.
    does the port name we21 should be same i m using same port name currently .
    clnt910 --rfc800 destination client 800 (sender system).
    clnt800 --rfc800 destination client 910 (reciever system).
    when i m changing the port name i m getting error status as 29 .
    we20 both the partner profile are active

    Hi,
    You Outbound IDOC is not correctly formatted I think, check the segments whether they are correctly added or not.
    Thanks,
    Mahesh.

  • 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

  • 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

  • Idocs with errors added status-56 in file to idoc scenario- how to rectify

    hi ,
    in file to idoc scenario when i m sending the file from ftp server to IS Retail,  file is successfully getting processed but the idoc is showing error ,when we see using WE05 tcode or BD87 , pl sugggest how to rectify it to make the status 53

    Hi,
    Have you configured the partner profile details? check these steps..
    1. In the receiver system you must configure the partner profile for your sender system in WE20.
    2. Add the IDoc message type to inbound parameters of the partner profile and configure the appropriate process code.
    2. Fill the Logical system name for your senderservice-->Adapter Specific identifiers in ID.
    <a href="/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi File-to-IDOC Scenario</a> By Venugopalarao
    <a href="/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi Steps for Posting IDOC's</a> By Ravikumar Allampalam
    Regards
    San

  • IDoc to Soap, with BPM - Permanent error in BPE inbound processing

    Hi Experts,
    IDoc to Soap, with BPM - > Permanent error in BPE inbound processing
    How to rectify this any issue???
    Thanks-
    sk

    Hi,
    The inbound processing encountered a permanent error and the queue therefore stopped.
    The error message "Permanent error in BPE inbound processing" may be caused by the following:
    - At the start or when you process a process instance, the inbound processing encounters an exception that was not handled. This exception is triggered, for example, by a transformation step, a synchronous send step or a control step but it was not caught in an exception handler branch. If the exception that was not handled occurs in the first transaction of the started process instance, the system does not write the process instance to the database but it sets the queue that has this error message to the error status.
    Refer to the help in Note 1082099
    - The inbound processing triggers this error if the correlation evaluation shows that a message should be delivered to a process instance that has the status "error". Since delivery to process instances that contain errors is not permitted, the queue is stopped.
    Use the simulation of the message delivery in the detail view of the relevant queue LUW to determine the relevant process instance for the affected message and use transaction SXMB_MONI_BPE "Continue Process Following Error" (or transaction SWF_XI_SWPR) to continue. If you cannot continue the process instance, check whether you can logically delete the instance. In this case, use the method that is described in Note 807906 to logically delete a process instance.
    Check whether your system contains other process instances that have errors in order to detect similar problems. Use transaction SXMB_MONI_BPE "Continue Process Following Error" or transaction SWF_XI_SWPR.
    Use the report RSWF_CRL_MAINTAIN to check all of the correlation instances in question or the relevant process instances that you can reach using "Display Work Item".
    - Messages that cannot be delivered because no correlation instance can be found may lead to the error that is mentioned here. Check whether the causes that are outlined in Note 1094028 affect your case.
    Hope this will help you.
    Regards
    Aashish Sinha
    PS : reward points if helpful.

  • IDOC status 64 not getting processed.

    Hi Gurus,
          I have a problem where IDOC's with status 64 are not getting processed via background job. the IDOCs weere getting processed with the background job till today evening, but suddenly no changes were made and the processing of IDOC's with status 64 has stopped and they keep filling up, when i checked the log of the Background job it says finished, and the log has the following information,
    17.09.2009 19:05:23 Job started                                                                   00           516          S
    17.09.2009 19:05:23 Step 001 started (program RBDAPP01, variant POS_IDOCS, user ID SAPAUDIT)      00           550          S
    17.09.2009 19:05:25 No data could be selected.                                                    B1           083          I
    17.09.2009 19:05:25 Job finished                                                                  00           517          S
    Kindly advise on this.
    Regards,
    Riaz.

    When i process the IDOC's using BD87, they gets processed wiwth out aany issues no dump is displayed, idoc gets a status 53 after processing via BD87.
    There is another problem how ever there are other jobs scheduled to run in the background other than this background job which are getting cancelled and have two different error logs for different jobs they are as follows.
    1) 18.09.2009 02:00:06 Job started                                             00           516          S
    18.09.2009 02:00:06 Logon not possible (error in license check)             00           179          E
    18.09.2009 02:00:06 Job cancelled after system exception ERROR_MESSAGE      00           564          A
    2) 18.09.2009 00:55:27 Job started                                                          00           516          S
    18.09.2009 00:55:27 Step 001 started (program RSCOLL00, variant , user ID JGERARDO)      00           550          S
    18.09.2009 00:55:29 Clean_Plan:Gestartet von RSDBPREV                                   DB6PM         000          S
    18.09.2009 00:55:29 Clean_Plan:beendet                                                  DB6PM         000          S
    18.09.2009 01:00:52 ABAP/4 processor: DBIF_RSQL_SQL_ERROR                                00           671          A
    18.09.2009 01:00:52 Job cancelled                                                        00           518          A
    This is a production server and the Licence is valid till 31.12.9999, and has no issues with the license.

  • Error in Idoc (Status - 51Missing data - HRALX00_ORG315)

    Hi Experts,
    We are getting the below error (Status - 51(Missing data)) when we try to process the Inbound Idoc (SRM) from R/3 to SRM system
    "It has been determined that the employee 00108937 has been received for the first time. However, not all the data that is needed to create a business partner has been received. In this case, the infotype 1001 and the subtype A209 have not been entered for the employee."
    But when I check these Info type in table HRP1001 these values are maintained in R/3.
    Suggest us how to determine the Outbound Idoc for the particular employee in R/3 and the root cause for the error.
    Regards
    Paul

    Hi,
    He pls debugg the outbound IDOC .Below are the steps to be followed.
    1) Put the breakpoint in the FM
    2) Goto the application document repeat the output and save.
    3)Goto program RSNAST00 give the document number and execute.
    Hope this helps..
    Regards,
    Sharath

  • What is the Successfull processed IDOC status number?

    Hi Experts
    What is the Successfull processed IDOC status number?
    arjent Please.
    Thanks in advance
    Sekhar

    Hi Chandra,
    Below are IDoc Process Codes
    For outboud Idocs:
    1 IDoc created
    2 Error passing data to port
    3 Data passed to port OK
    4 Error within control information of EDI subsystem
    5 Error during translation
    6 Translation OK
    7 Error during syntax check
    8 Syntax check OK
    9 Error during interchange handling
    10 Interchange handling OK
    11 Error during dispatch
    12 Dispatch OK
    13 Retransmission OK
    14 Interchange Acknowledgement positive
    15 Interchange Acknowledgement negative
    16 Functional Acknowledgement positive
    17 Functional Acknowledgement negative
    18 Triggering EDI subsystem OK
    19 Data transfer for test OK
    20 Error triggering EDI subsystem
    21 Error passing data for test
    22 Dispatch OK, acknowledgement still due
    23 Error during retransmission
    24 Control information of EDI subsystem OK
    25 Processing despite syntax error (outbound)
    26 Error during syntax check of IDoc (outbound)
    27 Error in dispatch level (ALE service)
    28 Not used
    29 Error in ALE service
    30 IDoc ready for dispatch (ALE service)
    31 Error - no further processing
    32 IDoc was edited
    33 Original of an IDoc which was edited
    34 Error in control record of IDoc
    35 IDoc reloaded from archive
    36 Electronic signature not performed (timeout)
    37 IDoc added incorrectly
    38 IDoc archived
    39 IDoc is in the receiving system (ALE service)
    40 Application document not created in receiving system
    41 Application document created in receiving system
    42 IDoc was created by test transaction
    50 IDoc added
    For Inound Idocs
    51 Error: Application document not posted
    52 Application document not fully posted
    53 Application document posted
    54 Error during formal application check
    55 Formal application check OK
    56 IDoc with errors added
    57 Test IDoc: Error during application check
    58 IDoc-Copy from an R/2 connection
    59 Not used
    60 Error during syntax check of IDoc (inbound)
    61 Processing despite syntax error (inbound)
    62 IDoc passed to application
    63 Error passing IDoc to application
    64 IDoc ready to be transferred to application
    65 Error in ALE service
    66 IDoc is waiting for predecessor IDoc (serialization)
    67 Not used
    68 Error - no further processing
    69 IDoc was edited
    70 Original of an IDoc which was edited
    71 IDoc reloaded from archive
    72 Not used, only R/2
    73 IDoc archived
    74 IDoc was created by test transaction
    Regards,
    Satish

  • IDoc ?? must be processed before IDoc ??? can be

    Hi all,
    I am trying to run IDOC of message type VLCCPO, Basic type VEHCLE01
    I am getting the error "IDoc 123 must be processed before IDoc 456 can be" (VELO158)
    but my problem is that IDOC 123 is already deleted.
    anyone?????
    Thanks naama

    Implement the note 1450511 Error VELO158 in IDoc Processing (Basic type VEHICL

  • 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

Maybe you are looking for

  • DVI to s-video adpater for Power Mac G4?

    I'm attempting to view digitial photos on my Power Mac G4 on an HDTV with an s-video connection. I've tried Apple's "DVI to video adapter" for the Power Mac G5, but it doesn't work, even after clicking "Detect Displays". Is there a DVI to s-video ada

  • How to initialize Datamining Model in process chain ?

    Hello all, I need to launch an APD for datamining analysis but i need to initialize the model before each data loading. The only way to initialize the model is to write an abap program ? No standard process, report or transaction to schedule this ste

  • OS hang on permissions repair--help!

    Hi all- My Mac Pro started locking up the other day. The cursor still moved, but everything else frozen. It would happen consistently within about 5 minutes of finishing the booting process. There'd be some disk activity for about five minutes and th

  • IPad is stuck on Activate screen

    iPad is stuck on Activate iPad screen, the linked apple id is asking for a password which when entered wants reset as it been entered wrong three times. Can't reset as there are no security questions or email confirmation on account - have receipt to

  • Iphone 4S video play back has no sound

    when i play back the video it jus makes a hissing sound, but playing music is fine through the phone. Any 1 else this problem ?